Ok. guys, i took some time to consider this.

1. There must be no content echoed before (setcookie(), session_start(), header(), etc.) otherwise there will be an error.
2.  its perfectly valid syntax to not have the closing tag ?> in PHP. PHP is not HTML.
3. not close my <?php tag at the end of any file which is - or might become - an include file, would probably be better should it be an include file, so when we do not ever have to worry about an extraneous newline (or other white-space character) after the closing tag causing problems with anything that sends headers (setcookie(), session_start(), header(), etc.).

With that, I will roll back.


How does it suffer from that?


We have the plan direction: (2, 3, 6), distance: 1. So the distance from (3, 4, 5) is theorically |2*3+3*4+6*5 + 1| / sqrt(2*2 + 3*3 + 6*6) = 9.099 and with normalized direction (2/7, 3/7, 6/7), distance 1. -> |(2/7)*3+(3/7)*3+(6/7)*5 + 1| = 7.4285


Body Mass Index Calculator

In order to calculate your Body Mass Index using shiny application, you should insert your mass in kilograms and height in metres (left part of the application). The result of this calculation is given on the right side.


Ok


Quick-answer: we can't. The RTSS won't start without it. It's an ogre bug AFAIK.


I think this change should be reverted. `gii\Module` should NOT be coupled with any particular generator.


If you want to enhance the model generator, then changes should be made to model generator only.


OK, this time I'll try to remember :-)


True. Design speaking it will be much cleaner. I'll have a look and propose something.


:( I am really against supporting php 5.2.


Sorry, seems I misunderstand this part. Should be removed at some other place. Just ignore this for now.


Suggest renaming `config()` to `configure()`.


@Lenchik, поддерживает. Достаточно заставить его поставить нужные пакеты и подтянуть ещё кое-какие ресурсы.

@tonkonogov, некоторые пакеты, хорошо работающие в обычном `pdflatex`, могут поломать сборку в `xelatex`. В значительной степени это касается шрифтов и их вариациями, конечно.


I got that much working last night, but i couldnt add in a new plist file to read. it didnt recognize it


Ok, I request it there for a moment. I'm adding that to visually read what went into the function, whenever i get syntax error when injecting string or arrays into query, it's problematic to rewrite all over again, rather just add a ,1 and hit refresh.

Of course, when we end this development, we can remove it.


Note that I updated the readme to say `+no-false-attribs` just to reflect the content of the current `LICENSE` file.


eyes bleeding


This should never happen since we call getversion ourselves.


Why is your "direction" not a normal vector? I think you are making a mistake on "what is the normal and what is the distance".

I've looked through some other engine's code and they do the same as I did:
ODE: https://github.com/vancegroup-mirrors/open-dynamics-engine-svnmirror/blob/master/ode/src/plane.cpp#L141
OGRE3D: https://bitbucket.org/sinbad/ogre/src/5ee010d450fd064007b61442124222bfb3d57a58/OgreMain/src/OgrePlane.cpp?at=default#cl-69

I'm gonna run some visual tests, brb.


Maybe keep the `IF DEFINED` part otherwise `IF NOT EXIST` will not work IIRC.


Since the server runs in a different thread, client-side functions should preferably not access it. Maybe things could be designed in a different way rather than having to query this everywhere.


...I mean, in the case the define isn't there at all.


Would it be better to simply return an empty mana cost in permanent.getManaCost() if the permanent is face-down?


`ctmp[np.take(neighborhoods, candidates, axis=0)] = 1`?


It can if getversion fails to extract hash for whatever reason. I think it is better to check.


I don't agree. If that ever happens, we should check in build.bat getversion, not here.


It's ancient, I know, I was just browsing through the code for the sake of it. And the only way to comment on a line of code is by commenting on the commit when it was created.

And I thought the brackets are misplaced in that line.


I don′t know why it changes )


I stumbled upon an interesting blog post that explains through what hoops one has to jump to distribute a CFFI project that uses `verify()`: https://caremad.io/2014/11/distributing-a-cffi-project/

Much of this may be overkill (I don't know), but using `dlopen()` is no doubt much simpler.


I said registered, not licensed. If you call licensing just dumping a license with a set of code, then yes you can legally license something. REGISTERING, which everyone seems to mix with licensing, is when you actually register the product with someone

> I won't piublic domain stuff if you are trying to do that okay.

I have made it very clear in the past that IDGAF what license anyone uses, don't know why you think I would be trying to do that.


Thanks for making this.  This would be a useful merge.  Hope it gets merged in.


Map is a reserved function in Python, would be better to rename it to avoid collisions.


Thx, I :green_heart: :snake:!


Of course for performance reason you want first to check for depth <= 2 and then for the costly see....


I think this could be designed. Maybe for Curtiss? :)


CC @mdo in case you find this useful; no need for hiding stuff anymore.


yes


IF NOT EXIST will work unless you have "%COV_PATH%" file in the same directory. Which you shouldn't have.


Ok


Sometimes, there is a 4th field, like root@localhost.
This commit breaks this kind of file.
That problem also occurs above in process_record


This commit message confuses me D:


Just a heads up, this will conflict with a recent change where CellRef::load was split into loadId and loadData (which may also make the ignoreRefNum parameter unnecessary)


@GrahamCampbell I don't know if this would make Parsedown Extra work on php 5.2. I did not add 5.2 to the travis config. I made this commit primarily because I think it makes the code a bit easier to read.


In vim at least, you could write this as (see ```curly-braces-names```)
```vim
unlet s:man_tag_buf_{s:man_tag_depth}
```
I don't know if it would be preferable or not.


questa è ok, praticamente le build function possono essere N e vengono richiamate consecutivamente per buildare in serie....(il core code è rimsto quello di prima...)


@kasper93
Dunno, but maybe ``set -o igncr`` would work? Like https://github.com/mpc-hc/mpc-hc/blob/develop/contrib/pre-commit.sh#L49.


No, this is the parent (summary) tag table (tags) used to tag the current model's tagging-table (user_tags). Only way to make it optional would be to default it to 'Tag'.


Same reasons we talked about lately. Using TS via files has multiple pros: better maintainability, search your config, conversioning, simpler upgrades, ...


This assignment appeared to be easy while comparing the same to Assignment #1. It will certainly help us using the cache memory for a series of functions to apply instead of a single one.


There is a hasMany relationship, I believe. Maybe that is what I should be using. I'll check.


Take a look at the link I've posted before. We use formatting (code and notices) in this documentation, perhaps its helpful: https://github.com/fnagel/beautyofcode/tree/master/Documentation


It's not for display purposes. It's for query performance reasons.


Thanks for hinting at ... unfortunately, it seems to be a very bad idea for SF.


TESTS FAILED
 Mr.roboto url : http://jenkins.plone.org/roboto/get_info?push=681f5b0a6401428da57131c79f11f12d
 plone-4.3-python-2.6 [FAILURE]
plone-4.3-python-2.7 [SUCCESS]


TESTS FAILED
 Mr.roboto url : http://jenkins.plone.org/roboto/get_info?push=f22a156dd4004607921e7caa6eec86cc
 plone-5.0-python-2.7 [FAILURE]


add oil


gives "IndexError: arrays used as indices must be of integer (or boolean) type". The result appears to be a python array of numpy integer arrays. So "idx" isn't a single index; it is the neighborhood of a point.


That syntax is deprecated


还真的把github当成日记来用了么:joy:


wow


Good catch. Thanks.


I dunno. This command publishes both a migration and a model...


Not in the latest documentation branch.


I dont like this


This fails and produces http:../pagename or  http:./pagename


Joer, mcostalba meant that the following would be doing the exact same thing, but would be more efficient.

if (givesCheck && (depth <= 2 * ONE_PLY || pos.see_sign(move) >= VALUE_ZERO ))


Hello there


Thanks for your thoughts.  We'll definitely look into this.

More helpful than code, though, would be what exactly you are testing and the environment that you're in.


@alexmarsev: In fact I was about to try it.


> Environment variable -o igncr not defined


I don't see the difference with the previous one.


da ist irgendwo ein fehler


ドキュメントありがとうございます。

シャープ3つで、ブロックコメントを書くこともできるかも？


function fecha_ymd (f){
			return f.substring(6,10)+'-'+f.substring(3,5)+'-'+f.substring(0,2);
}
	var validarFecha = function(fecha){
	var fechaArr = fecha.split('-');
 	var aho = fechaArr[0];
 	var mes = fechaArr[1];
 	var dia = fechaArr[2];

 	var plantilla = new Date(aho, mes - 1, dia);//mes empieza de cero Enero = 0
	//alert(plantilla.getFullYear()+'-'+plantilla.getMonth()+'-'+plantilla.getDate());

 	if(plantilla && plantilla.getFullYear() == aho && plantilla.getMonth() == mes -1 && plantilla.getDate() == dia){
 		return true;
 		}else{
 	return false;
 	}
}


r+


That's true for NaN (and _only_ NaN).  NaN is not equal to anything... including itself.

Try compiling this C program and checking for yourself:

```c
#include <stdio.h>

int main() {

    double nan = 0 / 0.;

    if (nan != nan)
        printf("nan is not equal to itself\n");
    else
        printf("nan is equal to itself... should not happen\n");

    return 0;
}
```

NaN is unique in this way, which makes this a common test for NaN.  (Numerous threads on StackOverflow are devoted to this -- NaN != NaN, but Inf == Inf, and -Inf == -Inf).

Another way that I've typically seen used for NaN tests is `isnan` defined in the `math.h` C header file.


@Rocky640 Yes, I understand. Though on my machine, it makes no measurable difference.
However, patch didn't pass.


I seem to remember istream creating tons of sentry locks for every operation on osx and linux. Our original libLAS code read much like https://github.com/PDAL/PDAL/commit/b50b29845f37536fd0fb074a23d69c16b77e9fe6#diff-47f13bfb03dcf13cb93a370a789cf636L546 but we moved away from it due to our inability to get the stream to quit making tons of locks for every little operation.


Msys, I would guess. Thought it was doing something similar by default, but maybe it doesn't. Anyway, it was worth a shot ;)


Yes, QDateTime() has a 'null' value, I will change.


saw approval from jdm
at https://github.com/Ms2ger/servo/commit/dfbf83a8aca8e68ec39bf013ca3bc0385dc3b108


merging Ms2ger/servo/transmute = dfbf83a8 into auto


Ms2ger/servo/transmute = dfbf83a8 merged ok, testing candidate = 4c9d7ce5


In this case we're talking about a character though. I wanted to avoid Cartesian plane terminology because points identify a location in "typewriter space", where legal positions depend on content and line breaks.


#4

Google page speed record increated

68 / 100 => Mobile
85 / 100 => Desktop


Sorry, I intended to create a new related project. New to this!


@Raynos, while "this project isn't actively worked on", would you still be open to PR's? Would you consider making new releases if the PR's are meaningful?


game specific settings :P


TeamCity MonoGame :: Develop (Win) [Build 3.3.0.1965](http://teamcity.monogame.net/viewLog.html?buildId=5069&buildTypeId=MonoGame_DevelopWin&guest=1) is now running


Thanks JJ, this is awesome!

Is there anyway to hook into the rstudio save function to automatically lint the current file when it is saved  (This is the way the `vim` linting works), or when the file is modified (the emacs linting does this)?


I made a small error.  It's a link to whatever happens to be in the cellar, whether the think in the cellar is `brew link`ed into place or not.  Nevertheless, I think this is the right choice.  Strangeness would only arise if one has multiple bash versions brewed AND wants to be using the older one.  But in this situation, the new symlink isn't any worse than the old one.


Visual Studio's C standard library implementation is pretty awful sometimes. Well, at any rate, this works because the DLL would be taking care of the I/O for you. Man, I'm glad libpng has so many commands now; even if the documentation is all over the place.

Support for different raw formats other than RGBA is available with 'save_to_file_safe', however, it's not perfect (It should get the job done, though). Depth is more or less the same way; it can be either 8 or 16, but this implementation may use 8-bit color for the final image, anyway. Explicit interlacing options, explicit compression, and explicit filtering is not "safe" with Visual Studio DLLs.

And as always, MinGW/GCC is untested; I'll get around to it at some point.


Such version jump !_!


Ah yes, adding :)


./configure --prefix=/usr --sysconfdir=/etc   --with-dbus


There are two ways to write it: (function(a,b){ ... }(1,2)) or (function(a,b){ ... })(1,2). Jslint prefers the latter. But it should not matter


in this case is better we use impl file:

Interface:

https://github.com/retf/Boost.Application/blob/master/include/boost/application/aspects/wait_for_termination_request.hpp#L21

IMPL WIN:

https://github.com/retf/Boost.Application/blob/master/include/boost/application/detail/windows/wait_for_termination_request_impl.hpp

IMPL POSIX (LINUX, MACOS):
https://github.com/retf/Boost.Application/blob/master/include/boost/application/detail/posix/wait_for_termination_request_impl.hpp#L27


Your problem lies somewhere else most likely, i dont get any errors. maybe cached js?


If possible, I'd rather call one sole function doing the dirty work about whether we are in editor mode while being on server or client side.
WDYT?
Any idea of where I could place such a function? In the gamemap object?


> allows different modules within your app communicate without requiring each other directly

allows different modules within your app **to** communicate without requiring each other directly


@XhmikosR: I don't remember, do you want to keep 7zip part? For fallback when tar is not found?


Are you sure this is correct?  Don't we need separate functions for "native" vs "standard" typecode?  CPython defines "i" type to be 4 bytes in standard case (ie without "@" specifier).  On a machine with sizeof(int)=2, will `struct.pack('i', 1)` and `unpack` still work?


Shouldn't this line still be there?


this is now included with merge conflicts solved, I think, and with Jeremy's extra suggestion of basing the class on new python `object` class


just to say I managed to use glXCreateContextAttribsARB() instead of glXCreateContext()
my changes are really hackish and copied from https://www.opengl.org/wiki/Tutorial:_OpenGL_3.0_Context_Creation_(GLX)
Now an opengl context version 3.3 is created (even though I required 3.1...?!) but I only get the same black screen than when calling your version with "MESA_GL_VERSION_OVERRIDE=3.3 ./reicast.elf" :
```
Home dir is: /home/sheepdestroyer/.reicast/
Linux paging: 00001000 00001000 00000FFF
evdev open: No such file or directory
MAP 00800000 w/ 25165824
MAP 20000000 w/ 25165824
MAP 04000000 w/ 16777216
MAP 06000000 w/ 16777216
MAP 0C000000 w/ 0
A8
vmem reserve: base: B4570000, aram: d4570000, vram: B8570000, ram: C0570000
Resetting mem
Mem alloc successful!
libwebsockets test server - (C) Copyright 2010-2013 Andy Green <andy@warmcat.com> - licensed under LGPL2.1
Initial logging level 7
Library version: 1.3 c11b847
IPV6 not compiled in
libev support not compiled in
 static allocation: 4488 + (16 x 1024 fds) = 20872 bytes
 canonical_hostname = sheepora
 per-conn mem: 184 + 1554 headers + protocol rx buf
 Listening on port 5678
Getting matching framebuffer configs
Found 4 matching FB configs.
Getting XVisualInfos
  Matching fbconfig 0, visual ID 0x20: SAMPLE_BUFFERS = 0, SAMPLES = 0
  Matching fbconfig 1, visual ID 0x71: SAMPLE_BUFFERS = 0, SAMPLES = 0
  Matching fbconfig 2, visual ID 0x9b: SAMPLE_BUFFERS = 1, SAMPLES = 4
  Matching fbconfig 3, visual ID 0x99: SAMPLE_BUFFERS = 0, SAMPLES = 0
Chosen visual ID = 0x9b
Creating colormap
Creating window
Mapping window
Creating context
Created GL context
Direct GLX rendering context obtained
Making context current
swap buffer
Loaded /home/sheepdestroyer/.reicast/data/dc_boot.bin as bootrom

Loaded /home/sheepdestroyer/.reicast/data/dc_flash.bin as nvram

Using Interpreter

GDI : 3 tracks
file[1] "track01.bin": FAD:0, CTRL:4, SSIZE:2352, OFFSET:0
file[2] "track02.raw": FAD:450, CTRL:0, SSIZE:2352, OFFSET:0
file[3] "track03.bin": FAD:45000, CTRL:4, SSIZE:2352, OFFSET:0
gdrom: Opened image "/home/sheepdestroyer/.reicast/discs/game.gdi"
Initialising empty vmu...
Initialising empty vmu...
Sh4 Reset
Sh4: i-cache invalidation A0000020
GL context version: 3.3
OSD: 6
Error opening /home/sheepdestroyer/.reicast/data/buttons.pngInvalid GD-DMA start, SB_GDEN=0.Ingoring it.
VREG = 03 ARMRST 00
VREG = 03 ARMRST 01
VREG = 03 ARMRST 00
SPI : unknown ? [0x70]
SPI : unknown ? [0x71]
sh4io: Invalid read access @@ 00000030
Sh4: i-cache invalidation 8C00DD84
Invalid GD-DMA start, SB_GDEN=0.Ingoring it.
Sh4: i-cache invalidation 8C09E6B2
Sh4: i-cache invalidation AC09D99E
VREG = 03 ARMRST 00
new tactx
new tactx
VREG = 03 ARMRST 01
VREG = 03 ARMRST 01
VREG = 03 ARMRST 00
FOG TABLE Curve match: maxdev: 0.00 cents
new tactx
Render > Extended time slice ...
Render > Extended time slice ...
Render > Extended time slice ...
...
...

```


Atrac3p improve https://github.com/hrydgard/ppsspp/pull/6959
and Simulate UMD delays https://github.com/hrydgard/ppsspp/pull/7227
Those help a lot of games from hangs to playable.


テストコードでは、引数を書くようにしましょう！


ok, done https://github.com/scrawl/openmw/commit/8b5effe3e06eb628ac3c12f6fec39052ef26a79b


これは、beforeEachに、pageと同じようにresultを入れるようにしたいです。


ppsspp seplugins suport please


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


You got the idea of how to define and use classes down, which is great. Various notes:

1) In this particular case, it doesn't need to inherit from QObject, even though almost everything else in the code base does (if you had some functions that you wanted to hook up to [Qt's `connect` infrastructure](http://doc.qt.io/qt-5/signalsandslots.html), then it would need to.) (Also note that the Q_OBJECT macro is a Qt specific thing, it isn't a general feature of C++.)

2) In this particular case, it doesn't even need to be a class at all. Classes and object orientation are meant for handling *context*, which in this case (parsing a string for URLs and HTMLizing them) there isn't any.

Instead, I would make this a static method (i.e., regular ole function) of the class that's most related to all the places where it's needed, which is probably the ChatForm class indeed. (Another very reasonable option would be to make it a static method of the Widget class, which is kind of the "main" class that hooks all of qTox together.)

That's the major points. One possible minor point is that I would consider passing the string by reference rather than by value, since the code that already exists does it in place.


@LUModder https://www.youtube.com/watch?v=Cq5Z53q_Se8


@fatiado this is about was has already been done not another way for requests


don't format BC api...


オッケーだと思います！


ありがとう。

関数名から引数の意味が分かりそうな時は、入れなくてもOKにしましょう。


I think the start pos also ought to be range checked (this one `>= 0 && < 128`.)  But, hopefully it won't matter.

-[Unknown]


@Mhwan 커밋할때 뭐 수정한건지 적어주시죠


I don’t think this will work, since each instance of a `Twitter::Cursor` will have its own `Mutex` but Twitter’s rate limit is enforced across multiple cursors.


In order to address this, it's really more important to know:

1) The compiler and environment
2) The test that's problematic
3) Whether or not the test is representative of the kind of work that people generally do.

I'm not going to comment on the "fix" or the problem until I know more.


Lol, looks legit :P


@andyshinn great to see that `mini/base` code was of inspiration.

Since you're copying `mkimage-alpine.sh` almost verbatim from uggedal's version, at least you should state that in the LICENSE file (when you add one), similar to what I did:

- https://github.com/mini-containers/base/blob/master/rootfs/mkimage.sh#L3-L4
- https://github.com/mini-containers/base/blob/master/rootfs/LICENSE


refs #89


see also #2193


> 手滑了而已，别见怪

星光君如是说道


all tests pass:
success: http://build.servo.org/builders/linux1/builds/596
success: http://build.servo.org/builders/linux2/builds/595
success: http://build.servo.org/builders/android/builds/631
success: http://build.servo.org/builders/mac1/builds/812
success: http://build.servo.org/builders/mac2/builds/812


TESTS PASSED
 Mr.Roboto url : http://jenkins.plone.org/roboto/get_info?push=de712a1303d6403995b97fbde58951c3
 plone-5.0-python-2.7 [SUCCESS]


To można w ogóle zakomentować


Ideally, the mode ougt to be passed in as a parameter where it's needed.


Ah. Ok.


Is it stable? Would you mind adding a tag?


good


not destory


why did you add this? it does nothing.


Ahh jeebus... Can't believe i forgot those... Haha

On Sat, Jan 24, 2015, 1:10 AM Athanasios Kostopoulos <
notifications@github.com> wrote:

> It needs year and copyright holders
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/pki-io/pki.io/commit/283f80d0345f9aba474e0457b272c6d76d2f3e8e#commitcomment-9427340>
> .
>


I tried that and got a bunch of:
was not declared in this scope
errors.


well right now I have to figure out how to force overwrite / cancel the changes in my own fork so it can sync.

I would have gladly appended a second commit to save you the time there, or you could have done it if you had accepted the PR.  1 commit could be the basic algorithm fix, 1 more commit for getting rid of unused/unneeded variable.  Just seemed more organized I guess.  It's not really that much of a issue I guess (beyond my personal feelings/ego/attitude); it just means I have to learn more about how to use Git to adapt to semi-declined pull requests.


Why not do what Go does and just use "pki.io authors" as the entity?

On Sat, Jan 24, 2015, 7:35 AM Jon Bonazza <jonbonazza@gmail.com> wrote:

> Ahh jeebus... Can't believe i forgot those... Haha
>
> On Sat, Jan 24, 2015, 1:10 AM Athanasios Kostopoulos <
> notifications@github.com> wrote:
>
>> It needs year and copyright holders
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/pki-io/pki.io/commit/283f80d0345f9aba474e0457b272c6d76d2f3e8e#commitcomment-9427340>
>> .
>>
>


@kasper93: yeah.


fast-forwarding master to auto = 4c9d7ce5


![i37 cimgpsh_orig](https://cloud.githubusercontent.com/assets/3002461/5887824/c146e49e-a3e5-11e4-90c0-ff410bca529a.png)
![i38 cimgpsh_orig](https://cloud.githubusercontent.com/assets/3002461/5887825/c65bee02-a3e5-11e4-8e1b-459a18a4ea27.png)
Here are some tests, I set up a mathematical plane (depicted by a graphics one) and got it's distance to a point, then I used a Ray (depicted by the red line) to intersect with the plane (btw, I had to fix this method first: dd82370c5db9b4562ed08fccce40080d64b32c3b). Both are giving me the very same distance (and unless Vector3::Distance is bugged, it's the right one).


Also, make sure the archive is actually accepted by coverity before merging this.


that looked good...


Hm, right. Can't be bothered now, heh.


Sorry for wasting your time, no errors, just my IDE complaining


More like it :)


Cleanup failure, has added it on begin to look what is usable on it and I forgot to remove.


ok :)


Of course, I will.


Just double checking ;)


Looks good, thanks for your contribution.


r+


To snip a piece of a comment...

https://github.com/MassiveCraft/Factions/commit/c81d7d8794d80846cfc8d11cfe1df98367c868d5#commitcomment-9427151
>These developers didn't get any benefit from using maven, I actually just got issues.
>
>By reading these unnecessary comments I still see no reason to use maven. Maybe excepts for wasting time.

Please explain what issues you had.

The magic of Maven (or Gradle, or hell even ant to some extent) is that your repo is now instantly buildable by anybody, just by having Maven installed. They aren't forced to shove it into an IDE just to compile it. For instance, getting the latest version of a plugin is as simple as this (if you use Maven):

```
git clone git://github.com/MassiveCraft/Factions
cd Factions
mvn clean package
cp target/factions.jar ~/myserver/plugins
```
No mucking around with a GUI, or (S)FTP required. The magic of command line.

Removing the pom.xml without any explanation of why, since its presence certainly didn't harm anything, only makes it harder for users as well as developers.

Back when Bukkit was still alive I used to go around helping folks with reported troubles in their plugin code. One of the things I would frequently do is clone their repo, fix the bugs, and PR them back. As part of that process, I would also mavenize their repo so that it was substantially easier to build, and would teach the benefits to the user.

I'll do that now, since you claim none of these comments show you any reason to use it.

**Benefits of using Maven with your plugin**
-----
* **Universal building via commandline**. As I mentioned earlier, with a pom.xml outlining your precise dependencies and build requirements, your plugin is now buildable from any system with Maven installed (with installation being just a click away).
    * Specify the *version* of Java against which your plugin should build. No more guessing!
    * Maven's job is to acquire the dependencies of your project, so nobody has to go dig around for them.
* **IDE Integration**. The popular IDEs come with Maven integration, often built-in. Eclipse does this, Intellij IDEA does this, NetBeans does this. This way, using one single file you have now added support for all these IDEs to automatically detect how to handle your plugin's file structure and build process. No more having to manually edit the build paths in Eclipse!
* **Continuous Integration**. With Maven, you (or users of your plugin) can utilize a continuous integration (CI) server such as Jenkins or TeamCity. Every time you push your code to GitHub your CI server can automatically build that code into a web-accessible jar ready to download. Save yourself the time of compiling and uploading!
    * On a personal note, with the combination of Github and a CI I've been able to do development work on massive plugins from the crappiest of Internet connections while still being able to make the jar available to everyone immediately.
    * In addition to using a CI server for making files available you can use [Travis CI](http://docs.travis-ci.com/user/getting-started/) for confirming all your code works, *including the code folks submit in pull requests*. Test a PR's compilation without making any effort yourself!
* **Lower the barrier of development, attracting new contributors**. The easier it is to build your plugin, the more likely it is for a potential contributor to help. Folks get scared off the more work they need to perform before being able to even get your plugin to compile.

This is a non-exhaustive list, but I hope it at least resolves your concern with this comment thread not currently providing reasons to use Maven :)


Changed to enum for clarity


saw approval from jdm
at https://github.com/Ms2ger/servo/commit/801949556d1a697fe93495cd2417707e54e49c7e


merging Ms2ger/servo/unsafe_get-const = 80194955 into auto


Ms2ger/servo/unsafe_get-const = 80194955 merged ok, testing candidate = ff8cbff8


I can't quite remember why I did this change... Let me test for a while...


Wait, but the code itself for the sub-repo will still be contained in the parent repo right?

Where are you at now with it, i.e. what's the workflow presently? Giternal has become an essential part of my dev. Much preferred to "Pods" for iOS.


@SubJunk What was the issue here? The ```value``` arg is either an ```int``` or a ```bool```, never a ```String```, so you'll get errors from the 2 invocations of ```.valueOf((String)``` below. Code here should be same as in the master branch.


Set import to only allow preferences with ```extensions.classicthemerestorer.``` to be imported.


A function may be polymorphic, but once we actually apply that function to something, the type must be concrete, I think. Consider what would happen if we rewrote the mergeTerm in this way, which should be equivalent:

```haskell
v' = case v of
  Va _ -> asSubstitution v :: ContextTerm
  Ev _ -> asSubstitution v :: ValueTerm
mergeTerm = substitute (unwrap term1) v' term2
```

We would want this v' to have type ValidSubstitution a => a, but the compiler complains that it can't make sense of a value that can be either a ContextTerm or a ValueTerm. To solve this, we would wrap it in a data type that can encompass both, but then we're back at the NodeTerm that was to be unwrapped in the first place... So, sorry, I gave misguided advice, haha.

A quickfix would be to make explicit the types that we expect the unwrapping to give to us. In the process, it becomes clear why the compiler couldn't handle that on its own:

```haskell
merge :: Subnet -> Subnet -> NodeTerm -> Subnet
merge net1 net2 v = Subnet allNodes mergeTerm mergeCommand mergeCotensor mergeMu where
  (Subnet nodes1 term1 command1 cotensor1 mu1) = net1
  (Subnet nodes2 term2 command2 cotensor2 mu2) = net2
  mergeTerm = case (term1, v) of
    (V term1', Va v') -> substitute (unwrap term1 :: ValueTerm) (asSubstitution v :: ValueTerm) term2
    (E term1', Ev v') -> substitute (unwrap term1 :: ContextTerm) (asSubstitution v :: ContextTerm) term2
    _ -> error "This is why the compiler could't make sense of it"
  allNodes = Set.union nodes1 nodes2
  mergeCommand = Set.union command1 command2
  mergeCotensor = Set.union cotensor1 cotensor2
  mergeMu = Set.union mu1 mu2
```

There's still some issues to be fixed, but the compiler won't complain about this particular one anymore.

Hope that helps.


@lesander Goed punt!


And related https://github.com/alexmarsev/mpc-hc/commit/6960b487a6dedc6b6158fc83bafc9aae313da49b and https://github.com/alexmarsev/mpc-hc/commit/865f2363259c87b1e75595269337bff448d56dec

@XhmikosR
I need untouched vanilla upstream soundtouch codebase for audio renderer. We can do it submodule way or the current way. In case of submodule, we will need to manage soundtouch repo on github with https://github.com/nirvdrum/svn2git, really easy. Your opinion on how should I approach it?


Als in valentie elektronen?


You can still do `maintainers = with maintainers; [ kkallio henrytill ];`


Thanks!


Hi @zeke, hi @dashie,
the repository worked when I installed it using the following steps:
```shell
git clone https://github.com/dashie/fontcustom
cd fontcustom
gem build fontcustom.gemspec
gem install fontcustom-1.3.3.gem
```
Ligatures however only worked after applying this [patch](https://gist.github.com/danieljb/3a64c3a227a68337a675#file-generate-patch).


@Optimusprimeums @SubJunk see [here](https://github.com/UniversalMediaServer/UniversalMediaServer/commit/70bc9893594797f2f42d038ebefa150fcaba287f#commitcomment-9428488).


fixed #6
#6 はこちらで管理しましょう。


Avisame si te llegó el pull request!!

Excelentes las correcciones. Sigo insistiendo con el ArrayList en vez del List, soy terrible.

Pensé en usar la LinkedHashList pero el problema es que para la funcionalidad que se queria, obtener el primero no era lo mas intuitivo con la API. Se podría haber usado un LikedMap que tiene la funcionalidad de agarrar el primero y el ultimo, pero opté por el viejo conocido ArrayList.

El siguiente error:

High: in ted you must cover success and fails, in this case you must add some test for "abc.d", "123.", etc.

Entiendo lo que queres decir. Pero justo en este caso como no permito ni String ni null, no se los puedo pasar por parámetros. Pero en algún otro caso se tienen que ver los casos en los que los parámetros son incorrectos. Esta bien esta conclusión?

Otra corrección:
Medium: use map.

No se si te referis al código o al test. Aún así, en ninguno de los dos puedo usar map porque necesito una funcionalidad especifica del TreeMap que es floorKey(). Probé hacerlo genérico, pero como esa función no esta en Map, no anda.

La corrección de la exception es la que me generó mas dudas. Cree la Clase NumberTooBigException, pero no se si tengo que devolver un mensaje, o que tire la excepción o que hacer. Fue la única que no pude resolver completamente.

A seguirle metiendo!! El de services parece complicado. Hoy voy a hacer un poco y ver si mañana lo termino.

Gracias por las correcciones!

Saludos

Iñaki.

> On Jan 24, 2015, at 8:55 AM, juanpablopizarro <notifications@github.com> wrote:
>
> Genial Iñaki, pocos High. Porfa revisa los High y hacete un pull request asi me llega el email.
> El pull request lo tenes que hacer desde un branch en tu fork al master de tu fork.
>
> Falta aun para hacer TDD puro, pero arrancaste muy bien el proceso :D, no te va a tomar mucho dominar tdd.
>
> —
> Reply to this email directly or view it on GitHub <https://github.com/iberras/java-bootcamp/commit/bc0a5abbecb3f18a36d38716bdf04818aac59fdf#commitcomment-9427795>.
>


Yes, that helps. Thank you!


This seems more try to me. I also like that the `constrain` and `layout` calls specifically mention the group whose constraints are being replaced, e.g.:

```swift
constrain(button, avatar, replace: groupForAnimations) {
    // …
}

UIView.animateWithDuration(0.5, animations: view.layoutIfNeeded)
```


fixed #5


Hey, when you merge something, you get all updates and put in only one?
Why this's necessary?


sollte vllt mal die neue hochladen :D


Hi Seb,

patience....

On 2015-01-24 5:48 AM, Sebastian Sastre wrote:
>
> Hey @HeSe <https://github.com/HeSe> nice!
> I think that more than a branch, the GemStone flow should have it's
> own repo.
> What do you think?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/flow-stack/flow/commit/e1ab61fc6892811c232a0a76fe1b752678d09ca4#commitcomment-9428092>.
>


@siniida 見直しながら思ったのですが、ここに出てくるkafka_spout()はkafka_spout2()に一括置換すべきでしょうか。


Hello,

On Sat, 24 Jan 2015 07:19:15 -0800
Damien George <notifications@github.com> wrote:

> Are you sure this is correct?

Yup. Wasn't big issue for 32 bit, but with funny LP64 model it is
(especially that I find arrays the best way to pass values by ref via
FFI).

> Don't we need separate functions for
> "native" vs "standard" typecode?  CPython defines "i" type to be 4
> bytes in standard case (ie without "@" specifier).  On a machine with
> sizeof(int)=2, will `struct.pack('i', 1)` and `unpack` still work?

As you can see, this patch applies to *_array() accessors, which are
used only for arrays. (Well, need to check uctypes!)

And yep, Python should have arrays of stdint's, but doesn't:
http://bugs.python.org/issue9066
http://bugs.python.org/issue17345

--
Best regards,
 Paul                          mailto:pmiscml@gmail.com


Shouldn't they be QtBlockingQueued or whatever it was? Or is that not necessary...? Hmm maybe it isn't


That's a little redundant


Why not use TextExpander or something similar to fix these?

On Saturday, January 24, 2015, Michal Zwolinski <notifications@github.com>
wrote:

> +cmd = program.command('console');
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/balderdashy/sails/commit/fefae948c214491397dc298c434e7945f28654fa#commitcomment-9427985>
> .
>

--

--
Kevin Burke
phone: 925.271.7005 | twentymilliseconds.com


My bad, you are right if the normal is normalized (quite obvious).


Well... More work needed over the $TARGET thingy... if $TARGET is empty then it returns -gcc, terrible. @lmy441900


Or should we use i686-w64-mingw by default so nothing goes wrong (if Windows uses the same host notation)? @lmy441900


whoops, I was gonna test it but.. I got distracted Dx


Możesz użyć `token` z URLa i w ogóle pozbyć się tokenu z formularzy.


My script execution end with error on this line. Your's running fine?


Yeeaaahh, I was doing these at school and I forgot to update aura :<


trying to revert design changes


Nie wszystkie rzeczy można brać: np. te które są już wzięte powinniśmy odfiltrować.


all tests pass:
success: http://build.servo.org/builders/linux1/builds/597
success: http://build.servo.org/builders/linux2/builds/596
success: http://build.servo.org/builders/android/builds/632
success: http://build.servo.org/builders/mac1/builds/813
success: http://build.servo.org/builders/mac2/builds/813


What do you mean? o.o


Przydałaby się jakaś paginacja.


this is test just


Do kontekstu bym wrzucił obiekt obecnego `Taker`a.


I love this.


I actually just copied and modified the one from the Docker repo at https://github.com/docker/docker/blob/master/contrib/mkimage-alpine.sh. But I'll add some notes on both of your repositories inspirations as they helped guide ideas.


Yep. We changed seats in my computer class ._.


Można użyć skróconej notacji `redirect(name, *args, **kwargs)`.


Only the `qpClone` part has anything to do with quote previews.  This function pauses thumbnails that are offscreen and plays thumbnails that are onscreen.  The equivalent function in `ImageExpand` is called `playVideos`.


fast-forwarding master to auto = ff8cbff8


I agree with @lluchs that this should be pushed up to Sequence. That means you'll want to use the iterator protocol instead of indexing, but that should be pretty simple. Something like:

```dart
var first = true
for (element in this) {
  if (!first) result = result + separator
  first = false
  result = result + element.toString
}
```


Well, I just redid these two and used kristell as reference. Thats why default is gone too


An overload that doesn't require a separator (and uses `""` instead) would be nice too.


@siniida FROM内のJOINでは、外部＝REST(Tuple)受け（内部＝ストリーム）となっている一方、FROM内でないJOIN(言い方があれですが)では、外部＝Mongo他システム、となっていて用語がイマイチなことに今気がつきました。。


i don't think it's a good idea to put this kind of files at the root of the repository. Perhaps we could have a `nounification` folder (at the root) with all the databases + the code of `demo/...` using conceptnet


PS:
(5) The "Search Favorites" screen is now not directly linked from the Dashboard any more, and the "Search Public Transport" screen has completely disappeared.  On purpose, or mistakenly?


I've never used them. Every time I've logged an npc their face is always normal, so why change it?


Albo nawet: `redirect(thing)`: https://docs.djangoproject.com/en/1.7/topics/http/shortcuts/#redirect


Gayan: I think it would better to use a specific List type here: may be List<String>.


@andyshinn ah!

Seems that the file was contributed by the same author, but didn't get updated afterwards:

Original import:

- https://github.com/uggedal/docker-alpine/commit/0685a571c9e076c5b8c3536951d9405852666188
- https://github.com/docker/docker/commit/6a2bdc6eb769ffd1d8438f321953dde8b341b783

But that file has been updated since:

https://github.com/uggedal/docker-alpine/blob/master/mkimage-alpine.sh

Specially to avoid one of the steps fail due previous one resulting in error.

I was only concerned about `mkimage.sh` copyright/license, but after reading ISC vs MIT, no attribution is required so ¯\_(ツ)_/¯

If you don't mind will love to peek into your CircleCI setup and get *inspiration* from it :wink:


まず、単純に置き換えました。この後、もうちょっと改変してます


Hmm, I still would prefer patching it like discussed on IRC


NO PLAYでも、段位認定でスコアが残るかも？と思ったので変えました。


Same applies here, users may not know which type of a list to set.


I take it back, hasMany is not a many-to-many relationship. There is also a hasManyThrough, but that requires the table you are going through to be a Model, which in this case we do not have one. So I think the best bet is to stick with the belongsToMany.


`score_arr = ['0', '0', '0', '']`みたいになってて何か美しくなかったので直しました。


I'm about to merge the CircleCI and build script to `master`. I'd be happy to open a PR for mini-containers if it looks good. It will be a way to just automatically build rootfs without need to worry about Automated Builds.


I'm 1000% sure that this commite caused the problem.

In FFmpeg 2.5.3 it works fine. I get the above error "Error parsing AAC extradata, unable to determine samplerate." and because it isn't a warning, but an ERROR it stops.


要らないので削除。後でPirodxHelperに移動しています。


Sorry for my late response.

This is only adding the hyperlink.
It might be removed accidentally, so I fix it now.


下の方は、不要な関数を削って、

dj_level_to_numberは、「あれ？別に連想配列でよくない？」って思ったので、
1行で書きました。


uhm


fixes


https://golang.org/dl/ has a different sha1 value.

Currently brew is reporting a mismatch:
/linuxbrew$ brew install go
==> Downloading https://storage.googleapis.com/golang/go1.4.1.src.tar.gz
Already downloaded: /opt/boxen/cache/homebrew/go-1.4.1.tar.gz
Error: SHA1 mismatch
Expected: d77dbbb06d7a005966ced0b837bc6c97d541210f
Actual: c7a683e8d39b835e333199d68d0c0baefcd24a68
Archive: /opt/boxen/cache/homebrew/go-1.4.1.tar.gz
To retry an incomplete download, remove the file above.


不要なrequireを削除したのと、PirodxHelperというのを作りました。

ひとまずは、viewでclear_lampを変換したりする関数を入れます。
他にも何か、便利関数的なのはここに入れます。


Please remove the noise in the lines here :)


Now it looks better! :D


Do we actually need try-catch?


Ja zwykle sprawdzam jeszcze, czy `status_code` to 200.


Bad change


単純に値だけで比較できるようになったので、そうしました。
dj_level_target, dj_level_diffの場合は、
「スコアが更新されていたら更新する」で良いかな、と思ったので、そうしました。

まだテストはしていません。します。


Można by użyć `select_related`, żeby nie było drugiego zapytania po `Taker`.


Sorry for nitpicking, but the defaultAudioDSP.png is using parts of our temporary logo and does the amplitude have a phallus touch or is it just me :) Not a dealbreaker though. I'd like to help, but I'm not sure if I can find the time to create an new one in time, so if anybody else would like to help out, be my guest.

Sidenote: the text in mentioned image is a little close to the edge as well - a litte more padding might be nice. But as said - not a dealbreaker


Wydaje mi się, że `assertRedirects` jest lepsze.


@andyshinn that will be excellent!, appreciate it.

As I was telling @progrium on mini-containers/base#3 that I had the feeling that automated builds were *better* for users, but seems not (not even the *official* ones are automated)

Looking forward any improvements in the project!.

Cheers.


> Ideally, the mode ougt to be passed in as a parameter where it's needed.

That's what I've done when I had to but I have to say that updateActivespots is used in every trap/room so that will mean many changes...

If we are to do a function, I guess the most easy would be to put that in the gamemap (to check only once if server gamemap and to access corresponding source).

In any case, whatever our choice is, I think we should try to stick with this. For example, if we choose to access the gamemap, it would be nice to change GameEntity::tryPickup and all thoses functions that uses the editor mode as a parameter.
For my part, I don't mind about using a parameter or a function for this as it is a pretty static parameter...


result = require('./result_loader.coffee')
を意味していました。


That's weird I can't either... Hm, I can't find anyone else with a similar problem


rest in peace tti


Nice :+1:


Are you sure you want to use `$TARGET` instead of `$HOST`?
Google "build host target" for more information.


build time x3 :(


Aslında güzel fikir yakında güncelledim.


`button_code` jest nieużywany.


I think we should use core data, there a tutorial that even uses collection cells here http://www.raywenderlich.com/85578/first-core-data-app-using-swift


thanks!


Completes Issue #3 and begins to address Issue #2


I do not agree with the implementation of the survey bypasser (also you should put a comment in my opinion)..
As I explained in my post in #641, you should set a random IP otherwise Linkbucks might ban this address, because too many users use it. This is why you should in my opinion use a truly invalid IP in the form of [256-999]-[256-999]-[256-999]-[256-999].


Oh true... I was putting some random variables for demonstration. Let me change that real quick.

-----原始邮件-----
发件人: "Star Brilliant" <notifications@github.com>
发送时间: 2015/1/24 9:39
收件人: "AOSC-Dev/Anthon-Starter" <Anthon-Starter@noreply.github.com>
抄送: "Jeff Bai" <jeffbaichina@members.fsf.org>
主题: Re: [Anthon-Starter] fix Makefile, ready to build cross-platform(9bbf36f)

Are you sure you want to use $TARGET instead of $HOST?
Google "build host target" for more information.
—
Reply to this email directly or view it on GitHub.


Ten test sprawdza tylko HTML. Ciągle możliwe jest wysłanie `POST`a i ten post zadziała.


Wow that was quick! The additional file `test_10964.cpp` wasn't included in this commit or the prior one.

Two questions (which I will test later, don't have time now):
- What about when the continuation function returns a `future<T>`? It looks like it will automatically create a ready future, even though the inner future may not be ready.
- What about the case where the value is set after `unwrap().then(...)`? I _think_ the first continuation will notify `future_unwrap_shared_state`, but this has a default `launch_continuation` implementation (do nothing). Should `future_unwrap_shared_state` overload `launch_continuation` by calling `this->mark_finished_internal()` ?


Ten widok powinien być dostępny tylko dla tego `Taker`a, który sobie zarezerwował ten przedmiot.


great job :100: !!


La bourde traditionnelle x)


You can get it from another branch in this repository too. This is temporary until I find a better way to resolve it (see #7)


check_disk still hangs indefinitely when there is a problem with network mounts such as nfs. For example, if you were to run df -t nfs and it hangs, this plugin would also hang. This is at least true for Linux (RHWS 3,4, RHEL 5,6) but I imagine for other *nix'es as well.


Może jednak `give_to` powinien zaprotestować, gdy rzecz jest już oddana komuś innemu.


data share repo


Is this actually needed?


These help strings are read by the Transifex translation system and cross references are not easily visible, so it's better to have the contextual string on each label. So could you please add something like the following line as contextual help string to each DSP types?
#. Name of a class/preset for audio DSP


Sure


What, like in the comments?


Eh sure. Doesn't really matter to me.


I'm liking these answers without the merge conflicts Paul. Good work.


you could look at https://github.com/r-type/mame/commit/435961f765a5fc1b20182b2642ef1c9715d39f80
i had
```
#ifndef WIN32
#include <sys/mman.h>
+#else
+#define WIN32_LEAN_AND_MEAN
+#include <windows.h>
+#include <mmsystem.h>
```
and i had also to add -lws2_32 for libflac stuff.
win 64 build fine and works for me,
but i always have some
Error: attempt to free untracked memory 0x.... in (null)(0)!
Ignoring MAME exception: Error: attempt to free untracked memory
in log so there must an error somewhere in osd code


hmm, would it be wise to make label 12376 "Set as default for all videos" more generic and reuse it?


Like, how can they make the mistake not to return one of the 5 commands? I vote if they return something that doesnt make sense they essentially pass their move. I was thinking of making a 6th command PASS anyway.


Thats clever. <3


Without having them inlined: If one of the headers is multiple included, the template specializations are defined several times, because they don't depend on any template type anymore. So moving them into *.cpp files would be the right way. But this leads to another problem: The unspecialized template method is always associated instead of the specialized one.
Inlining all specialized template methods fixed this.


I did. Didn't commit yet


@KAMAELUA там есть комментарий с пояснением и примерами


can't labels 15049-15051 be combined? It's a PITA to translate when split. GUI text controls should be able to autowrap these days @ronie @BigNoid ?


This isn't the rumor keyword o_o

![img](http://puu.sh/eXMIl/0f573653ea.png)


could label 14070 "Apply changes now" be reused here?


please add a contextual help here - "close" can have several meanings


if these labels are used in one of these dialogs they can be combined:
- select
- ok
- yesno
all three use a textbox these days


If you want to make it working you have to change back

#ifdef CONFIG_MACH_TREBON
ret = ath6kl_fetch_mac_file(ar);

in

#ifdef CONFIG_MACH_JENA
ret = ath6kl_fetch_mac_file(ar);

So it will work ;)


this line can go


Hi ailon,

In lines 235-238: Why don't you just simly write...
result.CanonicalManufacturer = manufacturer;
...?

And in line 219:
CanonicalManufacturer = manufacturer,

From the switch/case statement in lines 25-26, the variable "manufacturer" is always filled with the respective manufacturer name (either Nokia or Microsoft). This would make the code easier and would also prevent an implementation of redundant Information, such as "CanonicalManufacturer="MICROSOFT" (see lines 522-525).

What do you think?

Best regards,
Patrick


merge with line 6949


Haha. My editor was drunk I guess.


It's there... o_o

![img](http://puu.sh/eXNkv/f8a740f4d3.png)


could label 21444 "Audio channels" be used as well? Ofc only if the context it's used is simmilar.


oublié le </head>


Fixed: https://github.com/ProjetPP/PPP-QuestionParsing-Grammatical/commit/c804264fc0d1eba95c357427415065c9ace41b52


Did you got the data finally? I'm still away from git

El sáb., 24 de enero de 2015 9:39, Juan Julián Merelo Guervós <
notifications@github.com> escribió:

> Incorporating @javacasm data
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/geneura-papers/github-ranking/commit/
> 5e5c124e93f6591bf99945849a63faec7658629e
>


Tough part is tokenizing the authentication if we're going to allow auth with one account on multiple platforms.


would label 416 "Not available" also work? I mean we don't need a wall of text when it's obvious to the user


Your solution is cleaner for sure ;).


Thank you for pointing out this issue.

I moved 'nivo-slider' repo from https://github.com/kraksoft/nivo-slider/ to https://github.com/kedrap/nivo-slider/ some time ago, but it wasn't a good decision. So I reverted it now and updated it with latest commits by the way.


Ohh, that was supposed to be changed to Give instead of Add xD


Did you not copy this line to `tools/depends/xbmc-addons.include` on purpose? It looks like on android we currently install built dependencies into `$(BUILD_DIR)/depends` which is `$(BUILDDIR)/$(PLATFORM)/build/depends`.


```
// Resolver with linking
Explorer101Resolver: Resolver
Explorer101Resolver = "superball.Explorer101"

//@Base "http://101companies.org/resources/devchannel/"
//Explorer102Resolver: Resolver
//Explorer102Resolver = "superball.Explorer101"
```
Is resolving `ROR ["Ruby on Rails"]: Technology` to `.../technologies/Ruby_on_Rails`


Does anyone have a similar example using Mongoid? Mongoid doesn't have find_in_batches


Well, this was simply for testing purposes. Here is the flow I was thinking:

var engine = new GameEngine(); // init
engine.init(); // Get bot code from db
engine.roundRobin(n); // n games

Then within roundRobin, it loops n times doing:

generateGameState();

for each pair of bots...{
var results = runMatch(bots, gameState)
put results in db
}

within runMatch we run 2 games each with them getting to go first.

var results1 = runGame(bot[0], bot[1], gameState);
var results2 = runGame(bot[1], bot[0], gameState);

Then return something like {game1:results1, game2:results2} idk.
We can decide the structure of data and everything for the database later whenwe talk in person

Does this make sense?
So long term, the only call the server will need to make is once again,
var engine = new GameEngine();
engine.init();
engine.roundRobin(n);

And it will run the simulation and put everything in the database. Make sense? Am I crazy?


No, I'm afraid not.


## This is a markdown file


##this is a markdown file


but why was it _randomly_ not working?
if this was the cause it would have never worked, but it did just not always


Found BROKEN by quick.
_nlpsolver_knitro.so
[ 75%] Built target casadi_nlpsolver_knitro
Scanning dependencies of target casadi_linearsolver_csparse
[ 75%] Building CXX object casadi/interfaces/csparse/CMakeFiles/casadi_linearsolver_csparse.dir/csparse_interface.cpp.o
[ 75%] Building CXX object casadi/interfaces/cplex/CMakeFiles/casadi_qpsolver_cplex.dir/cplex_interface_meta.cpp.o
Scanning dependencies of target casadi_linearsolver_csparsecholesky
[ 75%] Building CXX object casadi/interfaces/csparse/CMakeFiles/casadi_linearsolver_csparsecholesky.dir/csparse_cholesky_internal.cpp.o
Linking CXX shared library ../../../lib/libcasadi_nlpsolver_ipopt.so
[ 75%] Built target casadi_nlpsolver_ipopt
Scanning dependencies of target casadi_sdpsolver_dsdp
[ 75%] Building CXX object casadi/interfaces/dsdp/CMakeFiles/casadi_sdpsolver_dsdp.dir/dsdp_interface.cpp.o
Linking CXX shared library ../../../lib/libcasadi_qpsolver_cplex.so
[ 75%] Built target casadi_qpsolver_cplex
Scanning dependencies of target casadi_qpsolver_ooqp
[ 75%] Building CXX object casadi/interfaces/ooqp/CMakeFiles/casadi_qpsolver_ooqp.dir/ooqp_interface.cpp.o
[ 75%] Building CXX object casadi/interfaces/csparse/CMakeFiles/casadi_linearsolver_csparse.dir/csparse_interface_meta.cpp.o
[ 76%] Building CXX object casadi/interfaces/csparse/CMakeFiles/casadi_linearsolver_csparsecholesky.dir/csparse_cholesky_internal_meta.cpp.o
[ 76%] Building CXX object casadi/interfaces/dsdp/CMakeFiles/casadi_sdpsolver_dsdp.dir/dsdp_interface_meta.cpp.o
Linking CXX shared library ../../../lib/libcasadi_linearsolver_csparse.so
[ 76%] Built target casadi_linearsolver_csparse
Scanning dependencies of target casadi_nlpsolver_worhp
[ 76%] Building CXX object casadi/interfaces/worhp/CMakeFiles/casadi_nlpsolver_worhp.dir/worhp_interface.cpp.o
Linking CXX shared library ../../../lib/libcasadi_linearsolver_csparsecholesky.so
[ 76%] Built target casadi_linearsolver_csparsecholesky
[ 76%] Building CXX object casadi/interfaces/worhp/CMakeFiles/casadi_nlpsolver_worhp.dir/worhp_interface_meta.cpp.o
Linking CXX shared library ../../../lib/libcasadi_sdpsolver_dsdp.so
[ 76%] Built target casadi_sdpsolver_dsdp
Scanning dependencies of target casadi_nlpsolver_snopt
[ 78%] Building CXX object casadi/interfaces/snopt/CMakeFiles/casadi_nlpsolver_snopt.dir/snopt_interface.cpp.o
[ 78%] Building CXX object casadi/interfaces/ooqp/CMakeFiles/casadi_qpsolver_ooqp.dir/ooqp_interface_meta.cpp.o
[ 78%] Building CXX object casadi/interfaces/snopt/CMakeFiles/casadi_nlpsolver_snopt.dir/snopt_interface_meta.cpp.o
Linking CXX shared library ../../../lib/libcasadi_qpsolver_ooqp.so
[ 78%] Built target casadi_qpsolver_ooqp
Scanning dependencies of target casadi_dplesolver_slicot
[ 78%] Building CXX object casadi/interfaces/slicot/CMakeFiles/casadi_dplesolver_slicot.dir/psd_indef_dple_internal.cpp.o
[ 78%] Building CXX object casadi/interfaces/slicot/CMakeFiles/casadi_dplesolver_slicot.dir/psd_indef_dple_internal_meta.cpp.o
In file included from /home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/slicot/psd_indef_dple_internal.hpp:30:0,
                 from /home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/slicot/psd_indef_dple_internal.cpp:26:
/home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/slicot/../../core/function/dense_io.hpp: In instantiation of ‘void casadi::DenseIO<Derived>::init() [with Derived = casadi::PsdIndefDpleInternal]’:
/home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/slicot/psd_indef_dple_internal.cpp:109:14:   required from here
/home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/slicot/../../core/function/dense_io.hpp:73:43: error: ‘dense’ was not declared in this scope
       dense_inputs_[i] = dense(d->input(i));
                                           ^
/home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/slicot/../../core/function/dense_io.hpp:78:45: error: ‘dense’ was not declared in this scope
       dense_outputs_[i] = dense(d->output(i));
                                             ^
make[2]: *** [casadi/interfaces/slicot/CMakeFiles/casadi_dplesolver_slicot.dir/psd_indef_dple_internal.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
Scanning dependencies of target casadi_xmlfile_tinyxml
[ 78%] Building CXX object casadi/interfaces/tinyxml/CMakeFiles/casadi_xmlfile_tinyxml.dir/tinyxml_interface.cpp.o
make[1]: *** [casadi/interfaces/slicot/CMakeFiles/casadi_dplesolver_slicot.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 78%] Building CXX object casadi/interfaces/tinyxml/CMakeFiles/casadi_xmlfile_tinyxml.dir/tinyxml_interface_meta.cpp.o
Linking CXX shared library ../../../lib/libcasadi_nlpsolver_worhp.so
[ 78%] Built target casadi_nlpsolver_worhp
Linking CXX shared library ../../../lib/libcasadi_nlpsolver_snopt.so
[ 78%] Built target casadi_nlpsolver_snopt
Linking CXX shared library ../../../lib/libcasadi_xmlfile_tinyxml.so
[ 78%] Built target casadi_xmlfile_tinyxml
make: *** [all] Error 2

```


The documentation guarantees that we'll call it with a queued connection (not blocking queued) since it's in another thread.
So it'll be in the right thread, but executed asynchronously. That's OK since it's just the saving function, it doesn't have to be synchronous.


this and other systemd changes were not intended to end up in 5.0 branch. yet..


@jjd-uk - mind reviewing labels as a native speaker?
@AlwinEsch minid adding contextual help strings to all labels? (like describing where or in which context the label is used). Also please see my comments regarding simmilar labels that could be used only as suggestion - I only had a look at the labels themselves and couldn't see them in use (no test build). If you need help on the English stuff simply send me the strings in German and I'll prepare everything


Found BROKEN by quick.
olver_cplex.dir/cplex_interface.cpp.o
Linking CXX shared library ../../../lib/libcasadi_nlpsolver_ipopt.so
[ 75%] Built target casadi_nlpsolver_ipopt
Scanning dependencies of target casadi_linearsolver_csparse
[ 75%] Building CXX object casadi/interfaces/csparse/CMakeFiles/casadi_linearsolver_csparse.dir/csparse_interface.cpp.o
Scanning dependencies of target casadi_linearsolver_csparsecholesky
[ 75%] Building CXX object casadi/interfaces/csparse/CMakeFiles/casadi_linearsolver_csparsecholesky.dir/csparse_cholesky_internal.cpp.o
[ 75%] Building CXX object casadi/interfaces/cplex/CMakeFiles/casadi_qpsolver_cplex.dir/cplex_interface_meta.cpp.o
Linking CXX shared library ../../../lib/libcasadi_nlpsolver_knitro.so
[ 75%] Built target casadi_nlpsolver_knitro
Scanning dependencies of target casadi_sdpsolver_dsdp
[ 75%] [ 75%] Building CXX object casadi/interfaces/csparse/CMakeFiles/casadi_linearsolver_csparse.dir/csparse_interface_meta.cpp.o
Building CXX object casadi/interfaces/dsdp/CMakeFiles/casadi_sdpsolver_dsdp.dir/dsdp_interface.cpp.o
Linking CXX shared library ../../../lib/libcasadi_qpsolver_cplex.so
[ 75%] Built target casadi_qpsolver_cplex
Scanning dependencies of target casadi_qpsolver_ooqp
[ 75%] Building CXX object casadi/interfaces/ooqp/CMakeFiles/casadi_qpsolver_ooqp.dir/ooqp_interface.cpp.o
[ 76%] Building CXX object casadi/interfaces/csparse/CMakeFiles/casadi_linearsolver_csparsecholesky.dir/csparse_cholesky_internal_meta.cpp.o
Linking CXX shared library ../../../lib/libcasadi_linearsolver_csparse.so
[ 76%] Built target casadi_linearsolver_csparse
[ 76%] Building CXX object casadi/interfaces/ooqp/CMakeFiles/casadi_qpsolver_ooqp.dir/ooqp_interface_meta.cpp.o
Linking CXX shared library ../../../lib/libcasadi_linearsolver_csparsecholesky.so
[ 76%] Built target casadi_linearsolver_csparsecholesky
Scanning dependencies of target casadi_nlpsolver_worhp
[ 76%] Building CXX object casadi/interfaces/worhp/CMakeFiles/casadi_nlpsolver_worhp.dir/worhp_interface.cpp.o
[ 76%] Building CXX object casadi/interfaces/dsdp/CMakeFiles/casadi_sdpsolver_dsdp.dir/dsdp_interface_meta.cpp.o
Scanning dependencies of target casadi_nlpsolver_snopt
[ 78%] Building CXX object casadi/interfaces/snopt/CMakeFiles/casadi_nlpsolver_snopt.dir/snopt_interface.cpp.o
Linking CXX shared library ../../../lib/libcasadi_sdpsolver_dsdp.so
Linking CXX shared library ../../../lib/libcasadi_qpsolver_ooqp.so
[ 78%] Built target casadi_sdpsolver_dsdp
[ 78%] Building CXX object casadi/interfaces/worhp/CMakeFiles/casadi_nlpsolver_worhp.dir/worhp_interface_meta.cpp.o
/home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/snopt/snopt_interface.cpp: In member function ‘virtual void casadi::SnoptInterface::init()’:
/home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/snopt/snopt_interface.cpp:417:17: error: ‘sparse’ was not declared in this scope
     d = sparse(d);
                 ^
[ 78%] Built target casadi_qpsolver_ooqp
Scanning dependencies of target casadi_dplesolver_slicot
[ 78%] Building CXX object casadi/interfaces/slicot/CMakeFiles/casadi_dplesolver_slicot.dir/psd_indef_dple_internal.cpp.o
make[2]: *** [casadi/interfaces/snopt/CMakeFiles/casadi_nlpsolver_snopt.dir/snopt_interface.cpp.o] Error 1
make[1]: *** [casadi/interfaces/snopt/CMakeFiles/casadi_nlpsolver_snopt.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 78%] Building CXX object casadi/interfaces/slicot/CMakeFiles/casadi_dplesolver_slicot.dir/psd_indef_dple_internal_meta.cpp.o
In file included from /home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/slicot/psd_indef_dple_internal.hpp:30:0,
                 from /home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/slicot/psd_indef_dple_internal.cpp:26:
/home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/slicot/../../core/function/dense_io.hpp: In instantiation of ‘void casadi::DenseIO<Derived>::init() [with Derived = casadi::PsdIndefDpleInternal]’:
/home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/slicot/psd_indef_dple_internal.cpp:109:14:   required from here
/home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/slicot/../../core/function/dense_io.hpp:73:43: error: ‘dense’ was not declared in this scope
       dense_inputs_[i] = dense(d->input(i));
                                           ^
/home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/slicot/../../core/function/dense_io.hpp:78:45: error: ‘dense’ was not declared in this scope
       dense_outputs_[i] = dense(d->output(i));
                                             ^
make[2]: *** [casadi/interfaces/slicot/CMakeFiles/casadi_dplesolver_slicot.dir/psd_indef_dple_internal.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [casadi/interfaces/slicot/CMakeFiles/casadi_dplesolver_slicot.dir/all] Error 2
Linking CXX shared library ../../../lib/libcasadi_nlpsolver_worhp.so
[ 78%] Built target casadi_nlpsolver_worhp
make: *** [all] Error 2

```


Unfortunately this can't work because we don't know how people ran the tests in the first place. It could be through rake, or they may have even added -I flags to Ruby.

Since minitest doesn't know how it's run, it can't say how to run again. We have to use external tools (like auto test or something)

--
Aaron Patterson
http://tenderlovemaking.com/
I'm on an iPhone so I apologize for top posting.

> On Jan 24, 27 Heisei, at 4:14 AM, Jakub Jirutka <notifications@github.com> wrote:
>
> Print command that runs a single test for each of the failed tests
>
> Make @tenderlove (and his cat) happier with the Minitest. :smiley_cat:
> http://tenderlovemaking.com/2015/01/23/my-experience-with-minitest-and-rspec.html
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/jirutka/minitest/commit/61f4b6bc710d10a2e7f064d1da21afc4dbe457fe


@dharmaxbum1 \
#! correct = syntax {}
user \
# should be:
user.name
<\>>


I tested individually srtp srtp_init 10000times is ok。I don’t knowwant iswrong。

原始邮件
发件人:puyidepuyide@gmail.com
收件人:pristineio/webrtc-build-scriptswebrtc-build-scripts@noreply.github.com; pristineio/webrtc-build-scriptsreply@reply.github.com
发送时间:2015年1月24日(周六) 20:57
主题:Re: [webrtc-build-scripts] New libWebRTC_objc target gets injectedinto the libjingle_examples.gyp file after doing a gclient sync after callingan update2Revision. Don't ask for code_signing unless you are buildingAppRTCDemo (ipa needs to be code signed) (8d863e4)

Imade in r8136. r8135Alwayscrash inSRTP
Error(srtpfilter.cc:706): Failed to init SRTP, err=2
Warning(channel.cc:852): DTLS-SRTP key installation failed
Error(common.cc:59): ../../webrtc/base/thread.cc(347): ASSERT FAILED: !current || current-blocking_calls_allowed_ @ AssertBlockingIsAllowedOnCurrentThread

my environmentXcode 6.1 sdk 8.1
run on iphone6

原始邮件
发件人:Ryan C. Paynenotifications@github.com
收件人:pristineio/webrtc-build-scriptswebrtc-build-scripts@noreply.github.com
抄送:pupuyide@gmail.com
发送时间:2015年1月24日(周六) 02:38
主题:Re: [webrtc-build-scripts] New libWebRTC_objc target gets injectedinto the libjingle_examples.gyp file after doing a gclient sync after callingan update2Revision. Don't ask for code_signing unless you are buildingAppRTCDemo (ipa needs to be code signed) (8d863e4)

The crash I am seeing is related to the changes they made in r8136. r8135 works...
From what I can tell this approach is working fine for building just the library.
—
Reply to this email directly or view it on GitHub.


this (and config_coredump) was not intended to end up in stables. it requires changes to kodi.service and a wrapper script. and maybe more. now you have a big fat problem. please revert.


This is actually still quite broken. We keep running into a condition where the gun will not fire with a right click.

There is a fundamental problem going on here. What you want is a countdown timer for when it is OK to fire the next round of the gun. Tick.timer is a constantly moving target that wraps. You have no idea what it's value will be the next time you look at it.

Do you have any ideas to fix it, or should I push back the original code?


Does this connect from all databases or just the default one? In my case I have two database connections.


With regards the import, I've only just now noticed that the import does not appear to actually restore the settings that the backup goes to the trouble of saving?


this was not indended to end up in stables. and was not tested at all witn 5.0/older systemd. same for backup/restore and factoryr eset. please revert all.


The same applies to rspec, it says to run `rspec` even when I’ve run it through rake. This isn’t a big deal IMHO.


It should ( the code is there) but it doesn't propagate these settings to
SettingsService. I'll add a refresh for that, nicely spotted!

On Sat, Jan 24, 2015 at 6:15 PM, garfield69 <notifications@github.com>
wrote:

> With regards the import, I've only just now noticed that the import does
> not appear to actually restore the settings that the backup goes to the
> trouble of saving?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/SchizoDuckie/DuckieTV/commit/87c08c8ef8bf2cc1fe012650b220938abbcd0b47#commitcomment-9428772>
> .
>


Yeah I will. Once again, just for testing.


Found BROKEN by quick.
Here's the log file for step 'all':
```
[  0%] Built target casadi_tinyxml
[  3%] Built target casadi_qpoases
[ 16%] Built target casadi_csparse
[ 28%] Built target casadi_sundials
[ 28%] Built target casadi_runtime_embedded
[ 29%] Built target profilereport
[ 44%] Built target casadi_dsdp
Scanning dependencies of target casadi
[ 44%] Building CXX object casadi/core/CMakeFiles/casadi.dir/__/__/casadi_meta.cpp.o
Linking CXX shared library ../../lib/libcasadi.so
[ 70%] Built target casadi
Linking CXX shared library ../../lib/libcasadi_qcqpsolver_socp.so
Linking CXX shared library ../../../lib/libcasadi_sundials_common.so
Linking CXX shared library ../../../lib/libcasadi_linearsolver_lapacklu.so
Linking CXX shared library ../../../lib/libcasadi_linearsolver_lapackqr.so
[ 70%] Built target casadi_linearsolver_lapacklu
[ 70%] Built target casadi_qcqpsolver_socp
[ 71%] Built target casadi_sundials_common
[ 71%] Built target casadi_linearsolver_lapackqr
Linking CXX shared library ../../../lib/libcasadi_implicitfunction_kinsol.so
Linking CXX shared library ../../../lib/libcasadi_nlpsolver_ipopt.so
Linking CXX shared library ../../../lib/libcasadi_qpsolver_qpoases.so
Linking CXX shared library ../../../lib/libcasadi_nlpsolver_knitro.so
[ 73%] Built target casadi_implicitfunction_kinsol
[ 74%] Built target casadi_qpsolver_qpoases
[ 75%] Built target casadi_nlpsolver_ipopt
Linking CXX shared library ../../../lib/libcasadi_qpsolver_cplex.so
[ 75%] Built target casadi_nlpsolver_knitro
Linking CXX shared library ../../../lib/libcasadi_linearsolver_csparse.so
Linking CXX shared library ../../../lib/libcasadi_linearsolver_csparsecholesky.so
Linking CXX shared library ../../../lib/libcasadi_sdpsolver_dsdp.so
[ 76%] Built target casadi_linearsolver_csparsecholesky
[ 76%] Built target casadi_linearsolver_csparse
Linking CXX shared library ../../../lib/libcasadi_qpsolver_ooqp.so
Linking CXX shared library ../../../lib/libcasadi_nlpsolver_worhp.so
[ 76%] Built target casadi_sdpsolver_dsdp
Scanning dependencies of target casadi_nlpsolver_snopt
[ 78%] Building CXX object casadi/interfaces/snopt/CMakeFiles/casadi_nlpsolver_snopt.dir/snopt_interface.cpp.o
[ 78%] Built target casadi_qpsolver_ooqp
[ 78%] Built target casadi_nlpsolver_worhp
[ 78%] Scanning dependencies of target casadi_xmlfile_tinyxml
Building CXX object casadi/interfaces/slicot/CMakeFiles/casadi_dplesolver_slicot.dir/psd_indef_dple_internal.cpp.o
[ 78%] Building CXX object casadi/interfaces/tinyxml/CMakeFiles/casadi_xmlfile_tinyxml.dir/tinyxml_interface.cpp.o
[ 78%] Built target casadi_qpsolver_cplex
Scanning dependencies of target casadi_integrators
[ 79%] Building CXX object casadi/solvers/CMakeFiles/casadi_integrators.dir/fixed_step_integrator.cpp.o
In file included from /home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/slicot/psd_indef_dple_internal.hpp:30:0,
                 from /home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/slicot/psd_indef_dple_internal.cpp:26:
/home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/slicot/../../core/function/dense_io.hpp: In instantiation of ‘void casadi::DenseIO<Derived>::init() [with Derived = casadi::PsdIndefDpleInternal]’:
/home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/slicot/psd_indef_dple_internal.cpp:109:14:   required from here
/home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/slicot/../../core/function/dense_io.hpp:73:43: error: ‘dense’ was not declared in this scope
       dense_inputs_[i] = dense(d->input(i));
                                           ^
/home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/slicot/../../core/function/dense_io.hpp:78:45: error: ‘dense’ was not declared in this scope
       dense_outputs_[i] = dense(d->output(i));
                                             ^
make[2]: *** [casadi/interfaces/slicot/CMakeFiles/casadi_dplesolver_slicot.dir/psd_indef_dple_internal.cpp.o] Error 1
make[1]: *** [casadi/interfaces/slicot/CMakeFiles/casadi_dplesolver_slicot.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 79%] Building CXX object casadi/interfaces/snopt/CMakeFiles/casadi_nlpsolver_snopt.dir/snopt_interface_meta.cpp.o
[ 79%] Building CXX object casadi/interfaces/tinyxml/CMakeFiles/casadi_xmlfile_tinyxml.dir/tinyxml_interface_meta.cpp.o
[ 79%] Building CXX object casadi/solvers/CMakeFiles/casadi_integrators.dir/implicit_fixed_step_integrator.cpp.o
Linking CXX shared library ../../../lib/libcasadi_xmlfile_tinyxml.so
[ 79%] Built target casadi_xmlfile_tinyxml
Linking CXX shared library ../../lib/libcasadi_integrators.so
[ 79%] Built target casadi_integrators
Linking CXX shared library ../../../lib/libcasadi_nlpsolver_snopt.so
[ 79%] Built target casadi_nlpsolver_snopt
make: *** [all] Error 2

```


Ok, this is a trivial readme PR. If anyone cares he can post-review it.


:+1: much better!


the system tag is deprecated and can be removed.


HVACSizingSim_CoincidentPlant (EnergyArchmage) - x86_64-MacOS-10.9-clang: Tests Failed

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


This is going to be problematic.  We have a lot of state in global variables.

Is there no way to force retrace process to quit?


Well, We may use the engine later not JUST for running bots but use some of the functionality only knowing gameState or something. Discuss this in person later.


there's no control with id="1" in this dialog


I have a console.log in setBotFunc. And the ai worked, so it works.


Eh, later. We will discuss exactly we should init.


Please Revert - those are for testing only!

RenderCapture is still missing, so people with boblight won't be happy.


:+1:  These look great! :grinning:


It's not supporting a full OData - just a subset of the query language.


combining two labels won't usually work very well in several other languages.


very nice. :8ball:


Found BROKEN by quick.
t
Scanning dependencies of target casadi_linearsolver_csparse
[ 75%] Building CXX object casadi/interfaces/csparse/CMakeFiles/casadi_linearsolver_csparse.dir/csparse_interface.cpp.o
Linking CXX shared library ../../../lib/libcasadi_qpsolver_qpoases.so
[ 75%] Built target casadi_qpsolver_qpoases
[ 75%] Building CXX object casadi/interfaces/knitro/CMakeFiles/casadi_nlpsolver_knitro.dir/knitro_interface_meta.cpp.o
Scanning dependencies of target casadi_linearsolver_csparsecholesky
[ 75%] [ 75%] Building CXX object casadi/interfaces/csparse/CMakeFiles/casadi_linearsolver_csparsecholesky.dir/csparse_cholesky_internal.cpp.o
Building CXX object casadi/interfaces/cplex/CMakeFiles/casadi_qpsolver_cplex.dir/cplex_interface_meta.cpp.o
Linking CXX shared library ../../../lib/libcasadi_nlpsolver_knitro.so
[ 75%] Built target casadi_nlpsolver_knitro
[ 76%] Building CXX object casadi/interfaces/csparse/CMakeFiles/casadi_linearsolver_csparsecholesky.dir/csparse_cholesky_internal_meta.cpp.o
[ 76%] Building CXX object casadi/interfaces/csparse/CMakeFiles/casadi_linearsolver_csparse.dir/csparse_interface_meta.cpp.o
Linking CXX shared library ../../../lib/libcasadi_qpsolver_cplex.so
[ 76%] Built target casadi_qpsolver_cplex
Scanning dependencies of target casadi_sdpsolver_dsdp
[ 76%] Building CXX object casadi/interfaces/dsdp/CMakeFiles/casadi_sdpsolver_dsdp.dir/dsdp_interface.cpp.o
[ 76%] Building CXX object casadi/interfaces/dsdp/CMakeFiles/casadi_sdpsolver_dsdp.dir/dsdp_interface_meta.cpp.o
Linking CXX shared library ../../../lib/libcasadi_linearsolver_csparse.so
[ 76%] Built target casadi_linearsolver_csparse
Scanning dependencies of target casadi_qpsolver_ooqp
[ 76%] Building CXX object casadi/interfaces/ooqp/CMakeFiles/casadi_qpsolver_ooqp.dir/ooqp_interface.cpp.o
Linking CXX shared library ../../../lib/libcasadi_linearsolver_csparsecholesky.so
[ 76%] Built target casadi_linearsolver_csparsecholesky
Scanning dependencies of target casadi_nlpsolver_worhp
[ 76%] Building CXX object casadi/interfaces/worhp/CMakeFiles/casadi_nlpsolver_worhp.dir/worhp_interface.cpp.o
[ 76%] Building CXX object casadi/interfaces/ooqp/CMakeFiles/casadi_qpsolver_ooqp.dir/ooqp_interface_meta.cpp.o
Linking CXX shared library ../../../lib/libcasadi_sdpsolver_dsdp.so
[ 76%] Built target casadi_sdpsolver_dsdp
Scanning dependencies of target casadi_nlpsolver_snopt
[ 78%] Scanning dependencies of target casadi_dplesolver_slicot
Building CXX object casadi/interfaces/snopt/CMakeFiles/casadi_nlpsolver_snopt.dir/snopt_interface.cpp.o
[ 78%] Building CXX object casadi/interfaces/slicot/CMakeFiles/casadi_dplesolver_slicot.dir/psd_indef_dple_internal.cpp.o
Linking CXX shared library ../../../lib/libcasadi_qpsolver_ooqp.so
In file included from /home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/slicot/psd_indef_dple_internal.hpp:30:0,
                 from /home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/slicot/psd_indef_dple_internal.cpp:26:
/home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/slicot/../../core/function/dense_io.hpp: In instantiation of ‘void casadi::DenseIO<Derived>::init() [with Derived = casadi::PsdIndefDpleInternal]’:
/home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/slicot/psd_indef_dple_internal.cpp:109:14:   required from here
/home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/slicot/../../core/function/dense_io.hpp:73:43: error: ‘dense’ was not declared in this scope
       dense_inputs_[i] = dense(d->input(i));
                                           ^
/home/casadibot/slaves/linuxbot/quick/source/casadi/interfaces/slicot/../../core/function/dense_io.hpp:78:45: error: ‘dense’ was not declared in this scope
       dense_outputs_[i] = dense(d->output(i));
                                             ^
[ 78%] Built target casadi_qpsolver_ooqp
Scanning dependencies of target casadi_xmlfile_tinyxml
[ 78%] Building CXX object casadi/interfaces/tinyxml/CMakeFiles/casadi_xmlfile_tinyxml.dir/tinyxml_interface.cpp.o
make[2]: *** [casadi/interfaces/slicot/CMakeFiles/casadi_dplesolver_slicot.dir/psd_indef_dple_internal.cpp.o] Error 1
make[1]: *** [casadi/interfaces/slicot/CMakeFiles/casadi_dplesolver_slicot.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 78%] Building CXX object casadi/interfaces/worhp/CMakeFiles/casadi_nlpsolver_worhp.dir/worhp_interface_meta.cpp.o
[ 78%] Building CXX object casadi/interfaces/snopt/CMakeFiles/casadi_nlpsolver_snopt.dir/snopt_interface_meta.cpp.o
Linking CXX shared library ../../../lib/libcasadi_nlpsolver_worhp.so
[ 78%] Built target casadi_nlpsolver_worhp
[ 78%] Building CXX object casadi/interfaces/tinyxml/CMakeFiles/casadi_xmlfile_tinyxml.dir/tinyxml_interface_meta.cpp.o
Linking CXX shared library ../../../lib/libcasadi_xmlfile_tinyxml.so
[ 78%] Built target casadi_xmlfile_tinyxml
Linking CXX shared library ../../../lib/libcasadi_nlpsolver_snopt.so
[ 78%] Built target casadi_nlpsolver_snopt
make: *** [all] Error 2

```


same here


Container can be expected to be always set because it is done in Yii.php file. Application however is null by default. This is basically resetting it to default.


TESTS FAILED
 Mr.roboto url : http://jenkins.plone.org/roboto/get_info?push=0b71e938b8704e9292334e88211a2e4c
 plone-4.3-python-2.6 [FAILURE]
plone-4.3-python-2.7 [SUCCESS]


system tag can go


you can't navigate to a label control


Hi @da-anda,

my girlfriend and I did the defaultAudioDSP.png. In february we will do a new one.
No it's a sin(x)/x function ;-), one of the known fourier transform pair (rectangle <---> sin(x)/x, http://en.wikipedia.org/wiki/Sinc_filter). Very common in signal processing :-D.


Great news! I'm happy.
So let me know how to proceed.


It already quites.

This is the first step to use it many times. But if you don't like it, I can remove this patch.


Yee


About your patch @danieljb on which platform did you try it?


Can you just use etcd.genericRegistry from Kubernetes?

Should save you a lot of code here.


there's no 'addon' window in kodi.


same


HVACSizingSim_CoincidentPlant (EnergyArchmage) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: Tests Failed

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


Here it exists the application.


Is it legit to just remove this rule?  I imagine it's in here on purpose which I ponder if it would make something else break...


use tabs for indenting


I *thought* there was a change to RESTStorage that you can optionally implement a method, and if you do not implement it, the swagger stuff does the right thing.  Right now, this is confusing for Create/Update because Godoc claims the action is supported, but code will always error.


World events? Just a blind guess.


Since this local function has access to `self` I dont think you need to pass this in. This will make the function name a bit clearer `findCdByAlbumName(albumName)`


D'oh!


Is it a fix?


I was confused at first who was calling this, but maybe a Godoc explaining why this is needed?


Nice!

I think there is also an even cooler underscore helper.

Something like:

```
_.findWhere(storedCds, { album: oldAlbume });
```


Yes. Both are defined. Also keep in mind that clang on MSVC also defines _MSC_VER, see:
https://github.com/bkaradzic/bx/blob/master/include/bx/platform.h#L51


What were the conditions of you not being able to fire it? It had worked fine for me. Yes, it constantly moving, but it predictably increases by 1 every tick. Also, the timer only resets to 0 after almost an hour and a half.


Probably you should have added this to the oe-a fork ...


`if (randomN & 1) {`

>&

>mcq nem eram de 50% porque confundi **%** com **&**


Doesn't the cd already know the artist?


This is wrong, like all the wl_shell_surface_*() calls below. You don't have a wl_shell_surface here, but a xdg_surface. Use xdg_surface_send_configure and the like.


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

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


I can see myself stealing these tests for quite a few other Mirage libraries!


vo te bani depois dessa


I wouldn't couple the storage mechanism in the name of the method. What if you wanted to update this to session storage? Or when testing inMemory? Or maybe direct ajax calls to a server to persist?

This module should encapsulate such "details".


If you use Composer in Travis CI, you could just remove the 5.2 from the CI and say it's not tested/supported.


@Vdeub idem c'est mieux en objets. Ca sera plus simple quand on voudra récupérer ça depuis un API endpoint


HelloWorld.md
## This is a markdown file


Close #3


Nice.


Thanks a million @eldilibra !!


Hmm, I just force-pushed an amended version of this commit (thinking it would be safe as it's not a branch anybody would've checked out) only to find GitHub didn't update the diff.


Closes #1


A server runs 24/7 so there are many hour and a half windows.

Say the last time I used a gun the counter was 50,000. I logged off and back on again the next day and tick is now 42. I have to wait till it is > 50,000 before I can fire the next round.


Can you push these to the template repo? Would be nice to have a folder
with ores we an pick and choose from for new mods.
On Jan 24, 2015 12:21 PM, "Scott Killen" <notifications@github.com> wrote:

> [image: :+1:] These look great! [image: :grinning:]
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/John-Smith-Modded/JSTR-1.7.x/commit/4d0bf049e5b4fd53f2641687b391d02fca877b01#commitcomment-9428792>
> .
>


Should bump the major version number for this changeset...


Fetch st-helens.las or some other 400+mb LAS file http://www.liblas.org/samples/st-helens.las

```
$ time las2las st-helens.las output.las
real	0m3.488s
user	0m2.662s
sys	0m0.682s
```

Using PDAL
```
/Volumes/hobu-ssd-backup/pdal/mtsthelens/st-helens.las
[hobu@pyro local (master)]$ time ~/dev/git/pdal/bin/pdal translate mtsthelens/st-helens.las junk.las
mtsthelens/st-helens.las: Found invalid value of '0' for point's return number.
mtsthelens/st-helens.las: Found invalid value of '0' for point's number of returns.
.......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
real	0m17.961s
user	0m17.052s
```


Hi @emichael - this link's broken


It is not in the CI. This is a `temp` branch. It is not in use.


https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/apiserver/handlers.go#L219

Can you just use the referenced method, and then determine the verb from req.Method and proxy/redirect/watch from the supplied parts?


I know, I've just checked the Travis CI build for the `temp` branch.


I would rename this to collection. This way you don't couple the implementation with the interface.

Basically the collection interface is any object that holds the cd's.

Same for when you save.

This seems to work well with the name you use in local storage.
For you app, the UI layer will implement a collection by creating a UI object that will have the in memory representations.


Valeu @luizfonseca, agora eu tenho certeza que não tem forma fácil de fazer isso :D


May find this later, but who calls this and ensures it always exists in the repository?


Yeah! Now we only need to define a data structure for the keypoint, keep an
array with one entry per frame, and update when playing (or interpolate)...
sigh :P

On Sat, Jan 24, 2015 at 3:17 AM, Umang Gupta <notifications@github.com>
wrote:

> Thanks .. I was looking for something like this.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/jltmtz/image-annotator/commit/fb65eb0b4a7db052c0e37dd1d25fc51a19186486#commitcomment-9427668>
> .
>

--
Julieta


Thanks


Eu estou meio tonto, isso deveria ser um `<=` ou um `>=`?


Hmm. What if it was something like:

if(Ticker.tick <= (canShootTick - counter*4) || Ticker.tick >= canShootTick) {


Which role corresponds to a user that can create a new project/namespace?  If this is it, can you let me know what Policy should be inserted in a namespace/project that is newly provisioned?  Maybe have a method that expresses that in a future PR, just keeping some notes as I go through this.


The mode intentionally only watches directories instead of the files. That way we don't have to keep track of files that are newly added or removed. It also significantly cuts down on the number of watch handles for large projects.


excellent, looks great.


Or set canShootTick to 0 when a player joins


cleaned up formatting


Está certo assim. Se for >= você deixaria ele com 80% de chance de sair o lewd text.


Not good enough. I play for hours at a time...


So what does

```lisp
(when (this-always-returns-non-nil regardless-of-argument)
   ...)
```

have to do with that? Why not just

```lisp
...
```


Sure, I didn't really have anything planned for this though. Anything you
would like to see? Feel free to contribute whatever you like.

On Thu, Jan 8, 2015 at 8:02 AM, Frozen Mage <notifications@github.com>
wrote:

> Could you please continue? I think this will be a nice example of file
> I/O. Can I contribute with whatever I can? I'm beginner but have some
> experience.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/gmrple/fileIO/commit/691adf34becd97332640ad27b0ad64df4c675544#commitcomment-9202056>
> .
>


the slide anim can be removed. it's not needed to reposition buttons within a grouplist.


Jugar bien! ;-)