> On 23. jun. 2015, at 16.05, DJ Dekker <notifications@github.com> wrote:
>
> Concerning 2):
> Some DGT boards have lettering a-h and 1-8 on them.

The bluetooth boards, yes.

> When the player is playing White, he will have the USB connector on the left side, next to square A2.
>
>

Yes, internally, this is the "normal" orientation of every DGT board, I believe. The side with the USB connector is White. We can follow this convention too.

-
Jonas Žnidaršič
jonas@jonas.si


my bt board has this. But the usb is ALWAYS left to me. In normal mode, the W pawns move away from me, whereas i use the "reversed" they move towards me.


I think this should be an enum to allow for other congestion control algorithms. This is conceivable given sender and receiver based algorithms using different signalling and feedback.


Use `lite = (not (args.full or args.quasar_catalog))` ?


We might let the "Install Recommended for Already Installed Packages" in menu but do not store it (see my comment on <https://github.com/yast/yast-packager/pull/127).


typeaheadLoading


Thinking about it: Cargo has fingerprint files, which would be a perfect place to attempt to hold a lock on.
If locking is not implemented using `O_EXCL`, the deletion of the file is not relevant. Probably it would be better to not enforce opening the file instead, and operate on a file-descriptor instead. That way, there is no doubt you have to tend for your own file.


This and the next line deal with #11


inverse this and meld ifs


@levicole You could set the image to nil prior to downloading it - that would let you 'see' it happen. This feature is hard to show in action otherwise.


Why is it necessary to implement `eq`, `hash`, etc methods for these classes?
I would have expected only `nonzero` and `to_json`.


:ok:


Re Patch 2015-06-22 (23/06/2015 )


one new day


Remove the `readonly` and Xcode will autosynthetize the setter for you, the `setBufferSize:` method is not needed.


ok done, I've updated the readme.md accordingly


They should probably go in `public.numenta.com/resources` - they aren't yum related at all, strictly speaking.


Good remark. But use issues for questions like this.


In this case it's probably ok but for something to keep in mind - read the warning bit: http://www.rubydoc.info/github/rspec/rspec-mocks/RSpec/Mocks/ExampleMethods:receive_message_chain


@smashwilson This should accomplish what you were trying to do in #1 but give us the flexibility to manage a queue of filters as we need more. I'm going to close #1 but if you see a mistake in the way I implemented your post-processing [here](https://github.com/ktbartholomew/presenter/commit/54f1adaca276c6da3370c6d30230e755f1877d12#diff-281eecb22112c9621ee6d8c53536642fR212), please send another PR.


Please, use the dot notation for this property!


Do we need the `@feed.id` here, would `webfeeds-widget` suffice?


complete new start


Lux measures illuminance, https://en.wikipedia.org/wiki/Illuminance, so I'd say that the raw values would relate to that. If pedantic, what we do measure here is resistance.


@levicole DWMR. Nice work here. Adding gestures like this makes me wonder what easter eggs might exist in apps, or what we could add that would be a fun discovery. Press on!


why $rootScope?


They should still be publicly readable - if someone else wants to let us log into their server, we don't care.


@aslakhellesoy I need your help at this point. I'm trying to port https://github.com/cucumber-ltd/cucumber-school-ruby/commit/fca9490f4738e83fad4f38784c50f369bce67472 to Java.

I am stuck on two fronts:

1) How do I write unit tests for a Spark server? I can't see anything in their docs...

2) I need to inject the Map of people into the `shouty.web.Server`, but because `WebShoutSupport` is already constructed by PicoContainer before Stepdefs is constructed, I don't see how to do that.

Related to (2) is that, as @jbpros pointed out, the `if` statement in the constructor of Stepdefs to choose the right support strategy is really a factory concern, and ideally would be pushed out into the DI wiring. Is there any way to do that?


<html></html>


yep, sure. thanks.


You can make use of existing ErrorResponse class


Should we also make it a function of time? In the future we may want something like Lamport signature, which  public key and signature will be 16kB and 8kB respectively. With only 100kB/tx, a tx could not have more than 4 signatures.

By the way, isn't CPU denial-of-service attack prevented by the overall sigop cap?


I agree with you in that docstrings are for APIs, and comments are for implementation details. But what I'm really wondering is if it is ok to start sending you guys PR, to add docstrings to undocumented functions?

> wait until the syntax has been used for documentation of Base for å while.

I can help hasten that!


Agreed


:thumbsup:


ack


colon : has to be removed, it is already in the language string.


10000 is the resistor resistance. The other are related, as an approximation to a non-linear ratio - so, yes, they are related to the sensor, but I believe that exposing them is moot, as another sensor may not even have the same formula - if any formula at all.


ACK


這個 method 好像是 genphp 的 flavor 用的，也把它獨立成一個 ActionTemplate 繼承 `CodeGenActionTemplate` 即可，就叫做 SampleActionTemplate，他是用來產生範例 Action 用的，然後這個 method 就可以拿掉。 ( ͡° ͜ʖ ͡°)


But the player can also set up white pieces on the opposite side (and thus notation will be wrong) and Picochess will then treat this as "normal". In other words, "normal" is dependent on initial setup of the pieces. This can be confusing when setting up custom positions (one has to remember what was "normal" the last time one played a game)

> On 23. jun. 2015, at 16.05, DJ Dekker <notifications@github.com> wrote:
>
> When the player is playing White, he will have the USB connector on the left side

-
Jonas Žnidaršič
jonas@jonas.si


Yeah, my bad :(


right...therefore i think, the text should express "w moves up", "b moves up"...something like this (all in 6 chars)


will implement this for dragging out NP chunks from xml response


TeamCity Jarvis :: Jarvis.DocumentStore :: Debug / Test / Release [Build 561](http://build.prxm.it:8811/viewLog.html?buildId=3157&buildTypeId=Jarvis_DocumentStore_CI) is now running


10 and 1 are the default values for those parameters :)


why __super is "bad" ?


This safe to build or is there much more before its ready? I am loving your new kernel btw...


@larsac07 Maybe we should remove 2008 now to keep roughly the same data density that we had?


I changed the order to highlight that the preferred way is using an extension as well as clearly stating that the chromeMediaSource constraints is for development purposes only. Also removed the Opera statement.


I see that you've moved the variable declaration up to the top, but convention is to have it in the `for` statement.

It makes no difference right now, so don't bother changing it back - but it will make a difference in ES6, and it's a good idea to establish habits that will continue to be valid in the future.


Return a **gboolean** rather than `void`, remove the `exit` call, and call the exit() in the calling function


Fixes #357


Yep, thanks for the ping.  Just uploaded it.


Io non l'ho applicata la tua Patch per diversi motivi ....

1° perche non funziona bene Getchannel con il Sat 19.2° ... oltre che manca il getchannel.conf ...

2° Ti da Errore al Punto "x1 e x2"  ... Errore in ""--output $SRC/getchannels/output/channels13.conf;""
Direcrory Corretta e' -> --output $SRC/setting/getchannels/output/channels13.conf;

3° Aspetto aggiornamenti da Armando Basile per nuova Release di Getchannel
con le modifiche suggerite per effettuare ricerche su altri Satelliti e con possibilita' di fare il Multi-Sat ...
Correzione errori in ricerca Canali;Provider ....


Oh, I see. But why not simply test for `mingw64\bin\git.exe`, then for `mingw32\bin\git.exe`, then `bin\git.exe`?


propagate the error status with a **bool** here too


you fixed a typo right above this, and then follow with a typo :)

"it 'should only the views...'" missing the word _select_ I assume.


In Ember 1.13.2 this will throw a deprecation error, so IMO we should either change the key to `@identity`, which is the new key (change it for both `@guid` and `@index`), or just remove the key altogether.


ack


Probably hold on a bit, I'm wanting to fix the kernel read_ahead not setting. It defaults to 128 for whatever reason, and my attempts to set it in the ramdisk are not working.

Unless you're not bothered about flashing again alter, then knock yourself out :D


// TODO: Check for input, make sure it is a valid gitlab hook, check repo and branch are correct


$model->servers; // FIXME: Surely we can use append


why nocover?


Till now this installer didn't work neither, however this is the current installation for that user:

**FW Installed on D:\FrostWire 6**
**Saved Downloads on E:\ **
______________________________

*I made the suggestions you had given and changed the download files to the D:\, but there is no change in my issue.. Although I had installed to the D:\, the From Device and Torrent Data have been default stored to C:\Users\FrostWire without specifying them.. *

Now he will test installing FW on C:\ to check if this is the cause of the problem.


We always pass O_CLOEXEC, even though in this case we close the fd without ever execing so it is in fact a noop.


you can't just nocover anything you don't like :P


@cfitz - Do you happen to recall what prompted this change?


That works too.


fixed #1755


My understanding is that you will be extremely busy with Arraymageddon and complicated stuff like that and I can't help you with those yet, so I can at least help with documentation (in all aspects) and testing instead.

But I wanted to know if it's ok to start doing this beforehand, else I can keep helping with whatever else is more useful.


This commit also moved the source code file into /src


this function is damn long... could you make it simpler?


I was a bit worried about this change, but as no test failed I went ahead.


This will break ubuntu machines. You should custom load a var file for centos that overrides defaults


This fix produces a bug w.r.t. non-determinsitic transitions. Will fix it.


We always check for "r < 0", even though the function never actually returns "r > 0" (so the function can be extended in the future without changing all the callers). Also please do "r != 0", if you really want to test for r being not zero, the only exception to this rule is to pointers, we allow "p" or "!p" instead of "p != NULL" or "p == NULL".


BTW do you build with Windows or Linux? I may end up breaking Windows building because of adding the kernel to the build (I.E, you build the ROM, it builds the kernel with it - needs Windows for this I'm pretty sure)


Interestingly, merging some ksm commits upstream and your fixes for linux-3.10 has fixed oops and panics(at least for now).

Now my only complaint would be that generic C implementation.
My C coding skills seemingly aren't great enough to use find_next_bit on pksm code, as all of my attempts has failed.

May I ask you to look into that stuffs?
I still think using in-RAM memory savings would be better than relying on non-RAM, internal memory swap method with zswap or vnswap.


s/itself/themselves/


haha, low on coffee - ill fix that.


@SabihaMajumder
Thanks!


Please use the safe_ato* equivalents there (and check the return values).


Same as above.


Code compiles in both amalgated and not amalgated mode; AddNodes service shows the expected behavior, namely:
* Fail for ns==0
* Create a unique ID for namespace ns=x,i=0|x>0
* Attempt to use the literal nodeId when ns=x;i=y|x>0 and y>0 is requested


I think we should omit `__location.endTag` in this cases. Which will be semantically correct, since these elements don't have end tags in their source representation.


wondering what people think on this.  if I am in a filtered context, should it include what i filtered on, and the children and grandchildren, or just the children and grandchildren etc..


Can we call it "message" instead of "mess"?


Hey, thanks for the contribution!


Thanks! I'm not ignoring you advice. I'm only gradually gluing together the several inputs you provided. Sorry.


Sweet, I dumped the system.img from the latest samsung verizon build and double checked most of the verizon specific stuff against whats in the repo and its all the same... FYI the interface.apk Host setting does not set the net.hostname variable in the build.prop but it looks Kernel Auditor does this as well...

I build on windows but I have a linux vm setup. I prefer building in windows because its so damn easy and quick though ;)


wat


TeamCity Jarvis :: Jarvis.DocumentStore :: Debug / Test / Release [Build 561](http://build.prxm.it:8811/viewLog.html?buildId=3157&buildTypeId=Jarvis_DocumentStore_CI) outcome was **FAILURE**
Summary: Tests failed: 1 (1 new), passed: 238 Build time: 00:08:41
### Failed tests
```
Jarvis.DocumentStore.Tests.dll: Jarvis.DocumentStore.Tests.SelfHostIntegratonTests.integration_out_of_process_html_to_pdf.verify_htmlToPdf_old: <no details avaliable>

```


Try `font-family: Georgia;` on line 13. `font` is not the correct property name.


This is so hardcore... O_O


@smizell seems same as removed part except describe and context(?)


I prefer `h3`s in readmes actually...


Ok, cool. Keep it on :-)


I agree that docstrings aren't really going to be a first class feature until they're used in Base Julia. And I would very much like to have built-in language support for them – i.e. strings in top-level void context would be parsed as doc strings. I've said several times, however, and I know that @JeffBezanson agrees, that we will not be doing markdown parsing while parsing Julia code – having a markdown parser as a dependency of the Julia parser is simply a non-starter – it is *never* going to happen. However, @one-more-minute seems disinclined to change the way docstrings work so that markdown parsing can happen at render time instead of at parse time. Given that, we seem to be at an impasse. Thus, docstrings are stuck in limbo as a clever macro hack rather than a first class language feature.


tak jadi order ke bos?


Kernel auditor uses the build.prop? I think I use setprop hostname = "things here". I could do both if need be. It usually sticks for me, but if i need to add more that's not an issue


_LW would only be for warn log messages


Woah, whats with all these crazy comment blocks? Is this how webpack outputs?


"Up" and "down" depends on where the player is sitting, no? This will always be confusing ... I suggest having the USB connector as a reference point (and point it out in documentation).

Let's simply call the side with the connector "normal White".

Or simply have a command in the menus "Reverse sides", without "normal". If user is unhappy with orientation, he should simply reverse the sides. (User doesn't care what is normal.)

> On 23. jun. 2015, at 16.33, Jürgen Précour <notifications@github.com> wrote:
>
> right...therefore i think, the text should express "w moves up", "b moves up"...something like this (all in 6 chars)
>
>

-
Jonas Žnidaršič
jonas@jonas.si


some clue now :)


Could I suggest to add also:

```
else if (hasPrefix(format, "%tC")) return HAVEN_DATETIME;
else if (hasPrefix(format, "%tc")) return HAVEN_DATETIME;
```


This function is too long and crazy really.

I don't remember what it does. A few smaller function might be better, but thats a nit really.


Because for normal operations we need to use the wrapper ;) Only for the hooks, which are not executed by git.exe but libgit2 we need to have the path set up as the wrapper does (i.e., usr\bin needs to be on the path for the case people call these files in their hooks, like openssl)...


`hasPrefix` could also be used for `%tc` and `%tC`


someone needs more sleep :)


typo


when custom resolution is selected, native resolution is grayed out, so user's couldn't enable it in the first place :)


Huh? zswap and vnswap are still in-RAM mechanisms. Zswap uses in-kernel memory and uses vnswap as a backing swap device, which is also a simple ramdisk.


@erik90mx ~ Can you please add some more exported variables, so they will show up in the inspector?


TeamCity Wordpress :: CorpSite :: CorpSite-Staging :: Launch Environment [Build 1](https://bsr.ict.je-labs.com/viewLog.html?buildId=29429&buildTypeId=Wordpress_CorpSite_CorpSiteStaging_LaunchEnvironment) is now running


teste


Argh, now testing...


Kernel audiror has the ability to change the net.hostname under Misc Controls... I changed it by hand in the build prop and it reflects the correct info in kernel auditior so I assume it is updating the build.prop, plus it has a build.prop editor built in as well :) I like the app...

So are you saying I need to get my linux vm setup and updated again to continue building after the kernel changes?


TeamCity xBIM :: XbimExchange :: Build [Build 352](http://ncl-xbim.hq.4projects.com:8080/viewLog.html?buildId=1911&buildTypeId=XBIM_XbimExchange_Build) is now running


if you reduce the host count numbers a bit, things should speed up in this test.


Google Auth


Can this be reused?


Last time I saw, vnswap scans around internal memory and locates free block
and marks them all together to be used as a swap device.
They apparently even had experimental code to discard when swap is
destroyed.
Am I mistaken.. and whole zswap + vnswap is essentially the same thing as
zram?
On Jun 23, 2015 11:45 PM, "Andrei F." <notifications@github.com> wrote:

> Huh? zswap and vnswap are still in-RAM mechanisms. Zswap uses in-kernel
> memory and uses vnswap as a backing swap device, which is also a simple
> ramdisk.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/AndreiLux/ref-3.10/commit/45da1f3dda0bfc190f717887054118ef079bf279#commitcomment-11818065>
> .
>


so we should remove like 260 and 261 if you merge this, that will reduce the test run to a sensible length, with any luck.


might be an advantage, depends if i cna get cygwin building a kernel. I'm sure it can


Sweet!


This was changed in https://github.com/18F/govt-wide-patternlibrary/commit/e4cccf5f5dcbd69cc9c4db9f4d26bd0ad85dc06f


That's about as far as the build gets, yeah.  It either is missing a common repo or more likely just needs some additional headers exported from the kernel. I didn't bother looking at it though because I'd rather get everything working in recovery first (adb is broken) because that will make debugging the full build WAAAAY easier.


My paddle bounce algorithm might be not so clear. So I'll explain it a bit here.

## Idea
I wanted to do something like the original pong: the bouncing angle depending on where the ball hit the paddle (so nothing to do with a real bounce), but without the *arbitrary* vectorial speed change for the ball.

## Code

#### Before this commit
* I was using the new position of the ball (inside or behind the paddle) to determine the ordinate of a *virtual* impact point for calculating the new angle.
* The distance between the paddle and the ball was fixed at how much the ball goes in (or through) the paddle.
* And other standard bouncing stuff (like refreshing the speed or slightly improving the vectorial speed).

It worked, but the new abscissa and ordinate of the ball were false. Especially for a big angle change.

#### After this commit
* I calculate the exact impact point (but with the center of the ball)
* I calculate then the new angle.
* I calculate then the new position of the ball (abscissa and ordinate) after a bounce with this *particular* angle.
* And I update the speed.

So now it works better. (Except if there are some typo or copy/paste errors).

*Remarq: a collision or bounce is when the center of the ball is inside or behind the paddle. At high speed the ball can go completely through the paddle in one frame*


It is an O(n^2) attack, where n is the number of bytes in the transaction. The attack is caused by the way the signature hash is computed-- all n bytes of the transaction must be hashed for every signature operation. The sigop helps, but isn't enough to prevent the problem.

Increasing both the sigop limit (as IS being done, along with the block size, at 40% per year) and the max transaction size would mean a potential attacker had an increasing advantage.

RE: Lamport signatures: there are schemes to make them smaller, see https://en.wikipedia.org/wiki/Lamport_signature.  Before then, we're likely to switch to one of the Schnorr signature variants Greg Maxwell has been busy working on, which are very small.


Maybe add some documentation on force_reload and caching behavior?


ok


_version.h_ is generated and only wants to be included from one place (so only bamtk.o needs rebuilding when it is regenerated).  Instead include _samtools.h_ and use `samtools_version()` below.


TeamCity xBIM :: XbimExchange :: Build [Build 352](http://ncl-xbim.hq.4projects.com:8080/viewLog.html?buildId=1911&buildTypeId=XBIM_XbimExchange_Build) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:02:26


we don't translate debug logs any more either.

I suspect I made this log.warn at some point, and didn't revert the translation thing.


setprop hostname = "things here" works in interface until you reboot then it defaults back to android-123123213123bullshit..... Plus it does not renew the dhcp lease and update the device name on the network. I have to disconnect wifi and reconnect after making the change in interface.... If I add net.hostname = myphone in build.prop it stays across reboots etc, but still requires a reboot first to take...


kkljlkjlkjlkjlkkl


mlklmkklm


Looks good. Thanks for doing that ^^


hgfhfhfhfhfghfhfh


VNSwap is just a dumb ramdisk driver from Samsung, it doesn't do scans or anything like that.

zswap + vnswap are replacements for zram, yes. The advantage over zram is that they're faster because zswap lies closer to the kernel's memory management. Pages will only go through "swap" in the very worst case. vnswap generally just has <10MB of pages in it but is required for zswap to work.


Hey everyone, just to let you know that I am helping my friend @gsolat get up to speed on static development in GeoNode. I am the one who has been pushing a couple of commits related to documentation about grunt with his help.


This makes the service fail when using relative VCL includes with `vcl_dir` defined in `DAEMON_OPTS`.


Maybe "You need a config file first. Please run a config target, e.g.: make menuconfig"?


Haha, I don't know if I know more advanced git stuff, it gets weird pretty
fast, but I can show you what I know. Dude, totally! I'm gonna have to have
a couple work days on our trip, maybe we can find some cool coworking space
to hang out in for a couple days?

On Mon, Jun 22, 2015 at 4:06 PM, jxcache <notifications@github.com> wrote:

> if I give you a data primer will you teach me about P5 and some more
> advanced github stuff?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/botbotbotbot/spaceII/commit/a29620b97c83dcbb6a5ab7ad2667c8fb2a908e06#commitcomment-11802430>
> .
>

--
latest Vidcode:
*Vidcode in Intel
<http://iq.intel.com/inside-programming-tool-designed-get-girls-coding/>*
*Vidcode in Fast Company
<http://www.fastcompany.com/3036097/strong-female-lead/a-learn-to-code-startup-for-instagram-loving-teenage-girls>*

*Leandra Tejedor, *Designer and Front-end Developer

*vidcode.io <http://www.vidcode.io/> / @vidcode
<https://twitter.com/vidcode>* / *Insta*
<https://instagram.com/vidcode>* /** FB
<https://www.facebook.com/myvidcode>*


TeamCity Wordpress :: CorpSite :: CorpSite-Staging :: Launch Environment [Build 1](https://bsr.ict.je-labs.com/viewLog.html?buildId=29429&buildTypeId=Wordpress_CorpSite_CorpSiteStaging_LaunchEnvironment) outcome was **FAILURE**
Summary: Exception Thrown; error message is logged Build time: 00:06:54


aaa


https://play.google.com/store/apps/details?id=com.developersinfo.android.dns.changer does the same thing except it renews the lease after changing the host name requiring no reboot, but its the same thing, once you reboot it defualts back to the android hostname... He probably uses the same method. Maybe something has changed in 5+... IDK


Did you think about move it to common place?


An idea:

Picochess internally always knows what the orientation is and always displays times correctly in normal game mode. I propose not to bother with what internal representation is, on setup it should simply display

W         B
or
B          W

on the clock, thus displaying current orientation. Then user only needs one command in menus: "Reverse!"  (No need for normal.)

> On 23. jun. 2015, at 16.43, Jonas Žnidaršič <jonas@jonas.si> wrote:
>
> Or simply have a command in the menus "Reverse sides", without "normal". If user is unhappy with orientation, he should simply reverse the sides. (User doesn't care what is normal.)

-
Jonas Žnidaršič
jonas@jonas.si


Funny to have kernel listed on our help, but no big deal, I guess.


I have the nes30 pro controllers, for what you did, the key distribution isn't the same on both, i'm going to post a nes30_pro_to_icade key mapping, and maybe we should create a proxy between the nes30 and nes30 pro (and whatever other icade device) to a standard controller, what you think about it?


https://github.com/blog/831-issues-2-0-the-next-generation
Please have a look to "Commits + issues"


I'll have a look at all this. AT the least, the reboot would release your Wifi DHCP lease, but ill see if i can do that


The grafana setting `graphite_url` expects a url, not a host:port pair.
Though Bosun does not yet support it, users should be able to specify the protocol and path for the graphite server. Bosun currently hard codes these to `http` and `/render/` respectively.

But, yes until Bosun accepts a full url, we should include the at least the port when building this header.


Got the `.gitignore` file working and taking the `codeception.yml` out of the Git commits.
Did these commands:
```
git rm -r --cached .
git add .
git commit -m "fixed untracked files"
```
Here's the [Source](http://stackoverflow.com/questions/11451535/gitignore-not-working).

Now I can use `codeception.yml` to store my server name and database name etc. and they will not be sent here to Github.


Hey Vlad,

Do we have meeting today ?
On Jun 23, 2015 10:19 AM, "Vladimir Diaz" <notifications@github.com> wrote:

> Should we check for more specific exceptions (e.g., IOError)?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/BingCanXu/Python-Dependency-Resolution/commit/c3fd6cd04a00e77f1e63082ebed35fa65052992e#commitcomment-11817446>
> .
>


Tell me if you ever see this `alert`.
It could (or should) happen so I used this to be noticed when it happens.

It can happen because of my detect collision algorithm: I wanted to make him a bit permissive to avoid situations where the player think there is a "hitbox bug".
And if it doesn't happen, then maybe is my algorithm not permissive enough.


We probably need to support `$WithDomain` option, as that's used [upstream](https://github.com/vanilla/vanilla/blob/fd534663270327d5a78fc4173e07fd0215cd844a/library/core/functions.render.php#L591).


lgtm


change the code to do only "view_i.get(r)" inside the while. This is faster. accessing an element of a class take some "small" time, but doing it in a loop isn't useful.


I know they couldn't but it still took the values from the custom boxes which defaulted to 1024x1024, which would never have worked with Baldurs Gate.

There is still the same bug in here in the setscaling function, but ill fix it when im home :P


There is a scope called ```none``` that every ActiveRecord model has. You can actually call this here:

```
scope.none
```

To achieve the same result. It's a bit more meaningful. No need to change, more of an FYI. You're doing great.


Sorry, the increased indentation hides the new delay on line 55.


Wow. I was mistaken about vnswap for over a year. ROFL

So compressing/decompressing with LZO uses less CPU cycle than pksm, I guess?


I mean write something like:
`` `Kotlin.isTypeOf(calleeArgument)(argument)` -> `typeOf argument === calleeArgument` ``


klopt niets van


:smile:


The next line targets exactly that.
`p` doesn't have a closing tag but the function is called with </td> as the next tag.
The condition `element.tagName === endTagToken.tagName` fails hence no `endTag` is set.


These custom build steps are needed for generating AWS credentials for the tests. Probably this feature can be integrated to sbt nice settings.


Why not use [`parse_url`](http://3v4l.org/6HQHI) instead of string gymnastics?


would it be easy to add an option for the user to chose?


TeamCity DNN JavaScript Libraries :: CI [Build 7](http://teamcity.engagesoftware.com/viewLog.html?buildId=274&buildTypeId=DnnJavaScriptLibraries_Ci) is now running


TeamCity DNN JavaScript Libraries :: CI [Build 7](http://teamcity.engagesoftware.com/viewLog.html?buildId=274&buildTypeId=DnnJavaScriptLibraries_Ci) outcome was **SUCCESS**
Summary: Running Build time: 0:0:7


TeamCity Jarvis :: Jarvis.DocumentStore :: Debug / Test / Release [Build 562](http://build.prxm.it:8811/viewLog.html?buildId=3160&buildTypeId=Jarvis_DocumentStore_CI) is now running


TeamCity DNN JavaScript Libraries :: CI [Build 8](http://teamcity.engagesoftware.com/viewLog.html?buildId=275&buildTypeId=DnnJavaScriptLibraries_Ci) is now running


And looking at this further, the port is already passed.

net/url.Parse() returns a reference to a URL struct.  Within this struct, the Host field contains both the host and port.
https://golang.org/pkg/net/url/#URL


TeamCity DNN JavaScript Libraries :: CI [Build 8](http://teamcity.engagesoftware.com/viewLog.html?buildId=275&buildTypeId=DnnJavaScriptLibraries_Ci) outcome was **SUCCESS**
Summary: Running Build time: 0:0:5


TeamCity DNN JavaScript Libraries :: CI [Build 9](http://teamcity.engagesoftware.com/viewLog.html?buildId=276&buildTypeId=DnnJavaScriptLibraries_Ci) is now running


TeamCity DNN JavaScript Libraries :: CI [Build 9](http://teamcity.engagesoftware.com/viewLog.html?buildId=276&buildTypeId=DnnJavaScriptLibraries_Ci) outcome was **SUCCESS**
Summary: Running Build time: 0:0:4


Ohhh

T
A
B
S


You can also inline add_impact. Can you add some comment here about the 3 function that you have inlined? Just to not loose too much documentation.


If you're just targeting this sensor, why bother exposing the thersmistor constant and such at all?


TeamCity Wordpress :: CorpSite :: CorpSite-Staging :: Launch Environment [Build 1](https://bsr.ict.je-labs.com/viewLog.html?buildId=29433&buildTypeId=Wordpress_CorpSite_CorpSiteStaging_LaunchEnvironment) is now running


This is left over from a while back. We hope to be able to incorporate it back in at some point.


Because it was from a library I wrote. It worked fine when you subclassed a class, but when you subclassed a subclassed class, it would not work correctly. Removing it for now until we get it figured out..


Do we really need battery level?


Thank You, it works like a charm! :-)


Thank you for confirmation, Hound.


nit: i would preffer named objects/exports


Estuve intentando arreglar esto pero no terminé, quedó empezado.


здесь нужно использовать form.cleaned_data


Brilliant idea Jonas! It's very effective and easy to understand for the user.

I think there should also be a way to show the current orientation ('B W' or 'W B') without changing it. So, not only a "Reverse!" command, but also something like "Current orientation" command. Perhaps this can be done with the same button: press it once to show the current orientation, press again to flip (and again to flip again etc.).


Pylint makes you have a docstring for every class and method. For docstring styling check out https://github.com/edx/edx-platform/wiki/Python-Guidelines.


That is probably not a big deal.  When you rename a file, git will very likely think it is a new file and then it will notice that your old file will become your new file.


neat :)


Yes, the advantage is that it will use CPU cycles only when compressing/decompressing, meaning when there's memory pressure and the kernel wants to swap out an unused page.

PKSM will try to hash every page that gets allocated in the kernel on top of the daemon doing scans in already allocated pages. PKSM is great for when you don't care about power but in mobile it just is too much overhead in my experience.


используй относительные пути чтобы не толкьо у тебя на машине работало


je vois tout


и почему у тебя проект лежит в папке с виртуальным окружением пайтона?


Please use the following code style:

    - (void) addLayer: (CALayer *)layer;

See, for example, https://github.com/gnustep/back/blob/master/Source/x11/XIMInputServer.m#L62


oh yeah, no big deal on the reboot... so if you update the net.hostname in the build.prop and issue the terminal command 'netcfg wlan0 down' the device kills the wifi and automatically brings it back up with the updated hosname fyi...


No, it was fine.  It's just not how I do things.


How about splitting on ` _`? To ensure that you get the first class starting with `_`. I could see classes with underscores in them being added in here and messing up your parsing.


... so why not add `bin;usr\bin;mingw64\bin;mingw32\bin` to the `PATH` and be done with it? :smiley_cat:


There should be only single write server, otherwise test is not deterministic.


тут не может быть этого исключения


You have created a retain cycle here: renderer retains the layer which retains renderer. Please use `@property (assign)`.


Done.


get_queryset всегда должен возвращать Queryset


Ah, that one is tricky.  It's so you can change them.  Otherwise you're getting back a *copy* of the vector.


To keep up with upstream changes.


Ahhhhh, Thank you.  I stared at the code in hooks.js for quite a while, but I think without a good understanding of the async library's calling semantics I was doomed :)   I see now - in this hook I'm calling the callback to satisfy async.every's need...but all hooks aren't necessarily called through the runDynamicAsyncEvery function.

I'll withdraw the PR.  Hopefully there will be a day where I can write up some more explanatory comments, but I'm not knowledgable enough now to try to "start fixing things I don't understand".  In the interim, I will be publishing my plugin, which will give future folks an example that they can follow.

Thanks!!


I know you've already gone back and forth on this, but instead of using a class name, we should probably use a data attr like "data-term" or something. That's the [intended use case of data attrs](https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Using_data_attributes) where a classname is supposed to be more for dom hooks.


Sorry. I didn't write this with the intent of comparability though, so I will rectify that (and a few other things that I know are currently incompatable)


As suggested by @mmusich the path ALCA:MuAlCalIsolatedMu is removed from Cosmics and Beamhalo entries in the relval matrix.


:ok: :1234:


waw, you're hyperactive!


TeamCity Jarvis :: Jarvis.DocumentStore :: Debug / Test / Release [Build 562](http://build.prxm.it:8811/viewLog.html?buildId=3160&buildTypeId=Jarvis_DocumentStore_CI) outcome was **SUCCESS**
Summary: Tests passed: 284 Build time: 00:11:31


@Aeusman Remove this commit asap please. We cannot have passwords on github.


TeamCity Wordpress :: CorpSite :: CorpSite-Staging :: Launch Environment [Build 1](https://bsr.ict.je-labs.com/viewLog.html?buildId=29433&buildTypeId=Wordpress_CorpSite_CorpSiteStaging_LaunchEnvironment) outcome was **FAILURE**
Summary: Exception Thrown; error message is logged Build time: 00:10:02


No worries.  It is an insidious type of bug.


To clarify, I was suggesting splitting on space-underscore.


`NSMutableArray` and `NSArray` retain their methods. You have thus created a retain cycle: layer retains the animation, which retains the layer.

`@property (retain)` is correct here, but `NSPointerArray`   would be more appropriate otherwise. (GNUstep documentation)

Please use `weakObjectsPointerArray` to initialize it.


But @jimmynotjim's idea is good, too.


You're right! I'm used to deal always with ObjC pointers!


Bueno, ahora creo que ya está mejor. Salud compa!


_layers = [[NSPointerArray weakObjectsPointerArray] retain];


Talked about in Slack. Leaving for the time being.


Is this needed for any specific reason?


instructions on the google that explain how to purge.

Best,
Will

On Tue, Jun 23, 2015 at 11:10 AM, Kunal L <notifications@github.com> wrote:

> @Aeusman <https://github.com/Aeusman> Remove this commit asap please. We
> cannot have passwords on github.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/openconnectome/open-connectome/commit/4c9b0d5e1f2fc7824a0a8cafb2b8c1e994fba370#commitcomment-11818747>
> .
>


Then I don't understand what's going on.

I am not in favor of the solution on your pull request as it drags in C++11 code that would need to be enabled conditionally.

As a workaround for now we could change those problematic lines to
<pre>
DataPtr childSelected = NULL;
</pre>


Very nice..
Thanks for all the info, great learning :)

Time to go disable pksm on my kernel and give vnswap a one more shot..


I think there's an api call for splitting lines in ST?


Is this 1.13 or 2.0?


Since you need to switch to `NSPointerArray` so objects don't get retained when added into the array, this comment does not apply, but usually you would simplify the need for checks by using `NSMutableSet`.

Also, is it correct to limit adding same animation to the same layer multiple times? I'd say the user has made a bug. Please add:

    // TODO(fzelic): throw exception when animation is added multiple times to same layer


I think we should leave Luna at m2e 1.5. Each m2e release is related to an Eclipse release, and Luna's friend is m2e 1.5. Also, since Luna, m2e is part of the Eclipse standard distribution. So people do not have to install it separately, and if they stick to Luna, they probably will not update m2e either. Lastly, if we update Luna target to m2e 1.6, we won't test 1.5 at all.


I think package.json also needs to exist for npm to resolve this dependency correctly


Why not set the raw value and resolve & coerce at read time?

The resolve timeouts seem to be arbitrarily chosen - I've seen 50ms at other places. Better use a global constant instead?


I think there's a `col_at` function in Vintageous that simplifies this.


Please rename to `handleAddedToLayer:`.

Please do not use internal data type `GSCALayer` directly; this type only exists on OS X to avoid conflicting with Apple's implementation.

Please correct code style.


Please correct code style.

    - (void) setBeginTime: (CFTimeInterval)beginTime


`in a clean way` is more appropriate here.


but `r = _r` is needed to record the previous value, or do you mean to use the `try...expect...` ?


Don't newlines need to be included for substitutions? What does Vim do?


Side note (no action required): there was no real need to add `nonatomic` here, right?


var width ...
var height ...

Would make more sense here as 'w' is defined below. Differentiating variables by only casing seems like a bad idea.


ok.


FacilityTabGridView (evanweaver) - x86_64-MacOS-10.9-clang: Tests Failed

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


Is `addRenderer:` necessary and appropriate? I'd say that the setter generated by `@synthesize` is quite enough.

Also, this should not be public API.


Fixed. Stupid me!


Okay @Saurutobi the login is now working it was having some issues due to the authorization tag in the web.config. However there is a parse error when redirecting to the main page, which is what I'm going to work on next. My goal is to have that done and be able to navigate to all pages before merging this branch back up to dev


Confused by the 'dashboard' and 'dashboard-editor' roles.  Should 'dashboard' be replaced by 'dashboard-editor'?


Prevent GitHub from thinking the documentation is a Jekyll site


Oh, I see now.


TODO: move index.php to public dir


Umm why is this commit not applied to the 3.3.5 branch?


@valib Does it work for you? It does for me :+1:


Would it be fine to clean that up in my patch? Since it was already existing, I thought it would be better off as a single patch.
@chriscool


This does not seem like it should be public API. Please move it into class extension:

    @interface CALayer ()
    .....
    @property (retain)                   CARenderer *renderer;
    ......
    @end

This way it will only be visible to `CALayer`.

If it needs to be visible to more than `CALayer` (e.g. `CARenderer`), which I think it might, please add it to appropriate class category (`CALayer+FrameworkPrivate.h`).


https://github.com/bosun-monitor/bosun/blob/master/graphite/graphite.go#L59-L62
bosun supports customizing proto (but it looks like i still have to update the Godep to match). currently path is still hardcoded indeed. (i can do a bosun PR to fix)

I missed that port is indeed part of the Host field. never mind, the bug I thought there was is not there.

that said, since bosun does take a url and will parse it, we should probably just feed it the url instead of just the Host field. that will allow bosun to set the scheme (and path, once i fix that)


Wha't s the actual error Vim shows in this case?


Should we also leave storm_nimbus_enabled in the when as well? What is that is set to false and storm_ui_enables is set to true will we have any issue?


Doesn't seem to agree with the rest of the comment.


This seems like framework-internal API. Please move it to be private.


Awesome.  I've gotten a few.  I like the way this is headed.


JavaDocs don't know about type variables, I thought?


@moy This is exactly why i wanted to have a second look, thanks :)


This seems to be a framework-internal API. Please move appropriately.


coemtando


Please use full names for variables.


I think the pre-Luna targets use m2e 1.5.


Source/Project64/N64 System/Mips/Memory Virtual Mem.cpp

I was wondering if StartVaddr is %08X, maybe EndVaddr should be %08X?


ws


Please fix code style.


Maybe W  B could be displayed immediately after the board is scanned? Before making first move user can then reverse it if needed  ...

> On 23. jun. 2015, at 17.04, DJ Dekker <notifications@github.com> wrote:
>
> I think there should also be a way to show the current orientation ('B W' or 'W B') without changing it

-
Jonas Žnidaršič
jonas@jonas.si


Use require here to load the namespace in browser.


Was a mistake while re-writing, will change.


They are using 1.4.1, which is correct i think.


Better to use os.path.join


If it's an already existing issue, maybe you can add a patch to clean this up before your patch.


split task2


`-addLayer:` is not called anywhere. Please clarify its purpose.


rec is mis-named.


What's the error Vim shows in this case?


One of the main points of this project :D


don't inline statement here


You should be more explicit that people should use serial numbers and not /dev/ttyUSBX or COM ports.


Yes! xstrdup would be better, cause without this, the code wont function


At least catch IOError?


Duplicate with L130 ^^


what's the error vim shows in this case?


bitwise shift right by 1 equal to divide by 2.
Use binary search.


Note to other developers:

As part of Google Summer of Code 2015, I've told Filip to send me pull requests so we can make use of code review tools on GitHub. As soon as a pull request is reviewed, the code will be submitted upstream.

There is no need to merge or worry about merging: pull request is here solely for the purpose of code review.


šlo byto posunout až na řádek 46?


Your version seems neater, thanks


Sweet !

> On Jun 23, 2015, at 08:19, hollywoodheinz <notifications@github.com> wrote:
>
> Okay @Saurutobi the login is now working it was having some issues due to the authorization tag in the web.config. However there is a parse error when redirecting to the main page, which is what I'm going to work on next. My goal is to have that done and be able to navigate to all pages before merging this branch back up to dev
>
> —
> Reply to this email directly or view it on GitHub.
>


doh!


Looks good


You really should have a description (not to mention, license, authors, homepage, repo etc), if you want people to choose your bower package over the other non-official ones, see the example I put in #41 for you...


also, probably better to use mode 'rt'.


Yes, Thanks :)


I'm fairly sure this isn't necessary - we're going through gulp now, so running `npm install` will get everything you need :+1:


This commit was done in 20 Jan 2012. There was no 6.x branch at that time, only 3.3.5.


commit makes sense!


Nope. Those backslashes are escaped in the header, so the string is `"\\r\\n"` (which is what it would look like in triple-double-quotes.)

I tried to add a note to the README about this double escaping, and just managed to confused myself so I decided it wasn't worth going into. Since they show up in the `Content-Type` by default, I figure it's self-documenting.


Nice!


Rgr! Will look into grabbing the latest for next alpha :)


If they run `npm run watch-css`, the browser sync code will start a local server and open their default browser by default to like `localhost:3000`. We might want to include some literature about that process


// FIXME: Handle the failure as it is unclear what went wrong


s/`lien`/`line`.


@take-cheeze is there a way `MRuby::CrossBuild` could supply the `--host`?


Apart from the typo, this looks good.


Sure, that's fair.


One proposed fix for issue #52


wouldn't it be simplear to `.read()` the file?


it seems for some people it's high math :D


Fix in https://github.com/rapid7/metasploit-framework/pull/5584. Thanks @erwanlr


probably better to catch some specific error.


what's the error vim shows here?


But at the moment the issue is still present on the 3.3.5 branch and the code above is not there. Am I being too stupid or something?


@aclark4life any objections to adding a setup.cfg with project-specific flake8 rules? I am ignoring W391 in my syntastic/vim/flake8 setup, so I did not see this issue (vim inserts extra newline, and I often forget).  I am specifically thinking of this in a setup.cfg:
```
[flake8]
ignore = W293,W391,E123,E133,E265
max-line-length = 80
```


well if we leave this off then by default the user can choose by simply appending `.and_self` - im starting to think that is fine, that we only want what is contained inside - similar to how rmq.all works today (it give everything in the root, but not the root...)

so maybe it really should be just `self.find` and if I have a need for including the thing that I also queried on - then it should be on me to include `and_self`


wrap all the reading part in a `with` would be cleaner.


It was weird writing code this way too, The whole point was to not have a single jump to ref-filter.
And although this deviates a little from directly porting tag.c. It made it easier to port.
Only way we could avoid this is by merging it with the next commit, But I'd rather not do that.
So I guess I'll explain a little more in the commit message?
@moy


Sure. We might have to come up with some sort of standardization in the future, but this is an excellent reminder of the status quo.


The code added in this commit doesn't seem to exist in either 3.3.5 or 6.x branches.


slo, ok


s/`on how to write plugin`/`on how to write a plugin`


Nice!


The else part should not be necessary, because that's the default behaviour.


[Deployment available online](https://s.brightspace.com/lib/ifrau/0.1.0/host.js)


Is there a default 'light blue' color that could be used?


I don't think that's entirely fair – the last thing I want is to hold things back, and I'm actually working on making the various parts lazier right now so that we can do a full transition.

The main reason I haven't had lazy markdown parsing high on the priority list is that I didn't realise it was blocking anything. If the parser simply treats `"foo"` as `@doc doc"foo" ->`, the only hard dependency is the `@doc` macro, and thanks to the [bootstrapping code](https://github.com/JuliaLang/julia/blob/681061b1d737eebea0698e9dcb839eefbfe47ff3/base/docs/bootstrap.jl#L11-L13) `@doc` doesn't even depend on the doc system, let alone the markdown parser – making changes to `@doc` (e.g. adding laziness) shouldn't affect parsing at all.

So lazy markdown and/or taking Markdown.jl out of Base is fine, but it seems orthogonal to the parser changes, and if it's not likely to cause problems later on I'm not sure why we'd prioritise it over other issues. (Unless there's something I'm missing?)


Yeah I know. And I am asking why? Is there something wrong with it?


Why do you need this function? I don't like it that you mix native (WP) code with Unity code.


Avoid magic constants. Define a constant `_STDOUT_FILENO` at the top level.


It's not necessary to call that here as it is invoked by the Interactor anyway after each update. You can delete that row.


Dit geeft alleen maar ellende, nu heb je ineens alle alumni aangepast


https://github.com/TrinityCore/TrinityCore/commit/112bc49c9a22a6998a9829940a72bfb3b4778bb9 removed the calls.


@wuethrich44 How about using this instead of loading directly, you might want to do this and this is consistant with heroku and CF generators
```
try {
    var aws= require("aws-sdk");
} catch(e) {
    this.log.error('You don\'t have the AWS SDK installed. ' +
            'Install it by running `npm install -g aws-sdk');
            this.abort = true;
    process.exit(e.code);
}
```


Noted. I'll put a fix for this in the next version. Thanks for the heads up!


This is keeping me from saving data changes.


Themed menu was nice :+1: Would You include that in new build?


Minor outsider nitpick: why does line 427 not use the `_shell_escape`? Seems kind of useless, considering it's only used once.


Alle leden die al lid af waren krijgen nu een andere datum mee


Вынес отправку почты в отдельную функцию.


Why?


For uninitialised variables I prefer a value that is not possible, like -1.
Even though it might never happen, 10000 is a possible cell.

Also, the name might be a little bit optimisable. Maybe something like 'lastWinningOption' or 'lastHighlightedCellIndex'. I think I'd go for the last one.


Should be:  "by the time they return..."


Rename the function to `redirect_stdout` and remove `source`. We need to use `fflush(stdout)` from C to ensure that the C `stdout` is properly flushed.


same here ...
All these "if UNITY_WP8" needs to be removed. There's a function that creates items from JSONObject. I'm sure you can make that JSONObject and use it to create an instance of classes.


That might be clearer as a for loop


Misschien moeten we denken aan een 'student tot' of een 'student af' vinkje naast 'afgestudeerd'. Wat denk jij @jgadelange?


Now I'm getting mad


Didn't work for me, due to tag string was too large.


Exposed as separate method, due to it is also used in test.


Thanks - done!


This only starts the storm_ui not nimbus so I think it is fine with just storm_ui_enabled. Right now the only thing that triggers this is found in a task file that you can only get to if storm_nimbus is enabled so they both need to be enabled but having just storm_ui is still right even if we some day break that dependency.


> Should be: "by the time they return..."

Fixed locally, along with the anaconda commit I pasted this into


TeamCity Jarvis :: Jarvis.DocumentStore :: Debug / Test / Release [Build 563](http://build.prxm.it:8811/viewLog.html?buildId=3162&buildTypeId=Jarvis_DocumentStore_CI) is now running


Volgens mij hebben we leden ipv gebruikers


Yeah sorry, arch_build changed semantically out of necessity, and I had
only fixed-up the packages in mono-mac-release (I don't quite know which
ones are deprecated, there are many).

We do need to change error handling so internal errors such as this one
float out.

On Tue, Jun 23, 2015 at 9:45 AM, Andres G. Aragoneses <
notifications@github.com> wrote:

> Actually, the problem was in the arch_build() method, which was
> highlighted by bockbuild as a warning. As soon as I fixed the warning, the
> build error appeared in the next bockbuild run :-m .
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/mono/bockbuild/commit/bb7c16ecd8c0ada63784fb973ec170df7c16c7c7#commitcomment-11816711>
> .
>


I think that we can hardcode the file mode here. `'w'` should be good enough.


Sorry got it this time, should be fixed now


Sure, works for me, thanks

Sent from my iPhone

> On Jun 23, 2015, at 11:29 AM, Sean Upton <notifications@github.com> wrote:
>
> @aclark4life any objections to adding a setup.cfg with project-specific flake8 rules? I am ignoring W391 in my syntastic/vim/flake8 setup, so I did not see this issue (vim inserts extra newline, and I often forget). I am specifically thinking of this in a setup.cfg:
>
> [flake8]
> ignore = W293,W391,E123,E133,E265
> max-line-length = 80
> —
> Reply to this email directly or view it on GitHub.
>


i guess you can grab DB type and set the same for RDS if DB is SQL as mysql, posgres and Oracle is supported by both and for NoSQL throw an error in console and return


Matt, not 100% on this but being that build.prop has been moved to overlay/system/build.prop you might want to take a look at JFLTE-GPE/install/default_network.sh for us verizon guys ;) I didn't look through the installer script and I am sure this is ran last after it has been moved but this here looks problem some.

sed -i "s/ro.telephony.default_network=9/ro.telephony.default_network=8/g" "/system/build.prop"

Also I reviewed the build.prop from I545_OC1 and things have changed a little. Network mode should now be 10...

sed -i "s/ro.telephony.default_network=9/ro.telephony.default_network=10/g" "/system/build.prop"

I changed this and it is working great... Below is the build.prop from I545_OC1 if you like to compare. If you need anything else from that dump just let me know.

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LRX22C
ro.build.display.id=LRX22C.I545VRUGOC1
ro.build.version.incremental=I545VRUGOC1
ro.build.version.sdk=21
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.0.1
ro.build.date=Mon Mar 30 17:43:04 KST 2015
ro.build.date.utc=1427704984
ro.build.type=user
ro.build.user=dpi
ro.build.host=SWDD6302
ro.build.tags=release-keys
ro.product.model=SCH-I545
ro.product.brand=Verizon
ro.product.name=jfltevzw
ro.product.device=jfltevzw
ro.product.board=MSM8960
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8960
# ro.build.product is obsolete; use ro.product.device
ro.build.product=jfltevzw
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=jfltevzw-user 5.0.1 LRX22C I545VRUGOC1 release-keys
ro.build.fingerprint=Verizon/jfltevzw/jfltevzw:5.0.1/LRX22C/I545VRUGOC1:user/release-keys
ro.build.characteristics=verizon
# Samsung Specific Properties
ro.build.PDA=I545VRUGOC1
ro.build.hidden_ver=I545VRUGOC1c
ro.build.changelist=4584173
ro.product_ship=true
ro.chipname=apq8064
persist.sys.storage_preload=1
# end build properties

#
# HWUI_BUILD_PROPERTIES
#
ro.hwui.texture_cache_size=50
ro.hwui.layer_cache_size=34
ro.hwui.path_cache_size=10
ro.hwui.shape_cache_size=4
ro.hwui.gradient_cache_size=2
ro.hwui.drop_shadow_cache_size=6
ro.hwui.r_buffer_cache_size=4
ro.hwui.text_small_cache_width=2048
ro.hwui.text_small_cache_height=2048
ro.hwui.text_large_cache_width=4096
ro.hwui.text_large_cache_height=4096
#
# from device/samsung/jfltevzw/system.prop
#
#
# system.prop for surf
#

# LCD Density
ro.sf.lcd_density=480

# Evolution RIL (8xxx)
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1

debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=gpu
dalvik.vm.heapsize=36m
debug.enable.wl_log=1
persist.hwc.mdpcomp.enable=true
debug.mdpcomp.logs=0

#
# system props for the cne module
#
#persist.cne.feature=1

ro.hdmi.enable=true
lpa.decode=false
tunnel.decode=true
tunnel.audiovideo.decode=false
lpa.use-stagefright=true
qcom.hw.aac.encoder=true

#system props for the MM modules
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true
media.aac_51_output_enabled=true
#33395 is sum of supported format flags in AAL
#Formats: AVI AC3 ASF AAC QCP DTS 3G2
mm.enable.qcom_parser=33395

# System props for audio
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=digital
persist.audio.lowlatency.rec=false

# System prop to select audio resampler quality
af.resampler.quality=255
# System prop to select MPQAudioPlayer by default on mpq8064
mpq.audio.decode=true

#
# system prop for opengles version
#
# 196608 is decimal for 0x30000 to report version 3
ro.opengles.version=196608

# system prop for requesting Master role in incoming Bluetooth connection.
#
ro.bluetooth.request.master=true
#
# system prop for Bluetooth Auto connect for remote initated connections
#
ro.bluetooth.remote.autoconnect=true
# system property for Bluetooth discoverability time out in seconds
# 0: Always discoverable
#debug.bt.discoverable_time=0

# System prop to disable a2dp sink which is enabled by default
bluetooth.a2dp.sink.enabled=false

#system prop for switching gps driver to qmi
persist.gps.qmienabled=true

# System property for cabl
ro.qualcomm.cabl=1

# System prop for sending transmit power request to RIL during WiFi hotspot on/off
#
ro.ril.transmitpower=true

#
#Simulate sdcard on /data/media
#
persist.fuse_sdcard=true
ro.hwui.text_cache_width=2048

#
# Supports warmboot capabilities
#
ro.warmboot.capability=1

#
#snapdragon value add features
#
ro.qc.sdk.audio.ssr=false
##fluencetype can be "fluence" or "fluencepro" or "none"
ro.qc.sdk.audio.fluencetype=none
ro.qc.sdk.camera.facialproc=true
ro.qc.sdk.gestures.camera=false
ro.qc.sdk.sensors.gestures=false
#property to check if dynamic resolution change is  supported in framework
ro.streaming.video.drs=true
#property to enable user to access Google WFD settings.
persist.debug.wfd.enable=1
#property to choose between virtual/external wfd display
persist.sys.wfd.virtual=0

#system prop for setting rmnet mux mode
persist.rmnet.mux=disabled

#disable gapless mode by default
audio.gapless.playback.disable=true

# Enable time services daemon
persist.timed.enable=true

# Keep SIM state on LPM mode
persist.radio.apm_sim_not_pwdn=1

# Don't wait the card state for RADIO POWER request
persist.radio.no_wait_for_card=1

# For sys info indication
persist.radio.add_power_save=1

# Snapshot setting
persist.radio.snapshot_enabled=1
persist.radio.snapshot_timer=22

# Control EONS (true = EONS enabled, false = EONS disabled)
persist.eons.enabled=false

# Use CP SE13 Table
persist.radio.use_se_table_only=1

# Default ECCList
ro.ril.ecclist=911,#911,*911

# Use CDMALTE Phone (For 4G model)
telephony.lteOnCdmaDevice=1

# Support Global Mode (For global mode model)
ro.config.multimode_cdma=1

# Data modules (For evolution RIL model)
ro.use_data_netmgrd=false
persist.data.netmgrd.qos.enable=false

# Use data service state for signal display (Except USC CS model)
ro.config.combined_signal=true

# Retry Timer (VZW)
ro.gsm.data_retry_config=max_retries=infinite,5000,5000,60000,120000,480000,900000

# Default Network Mode (For 4G / Global model)
ro.telephony.default_network=10

# Restore delay of the default network - 30 mins (VZW)
android.telephony.apn-restore=1800000

# Restore delay of VZW Apps APN - 1 min (VZW)
vzw.telephony.appsapn-restore=60000

# Default Data Roaming
ro.com.android.dataroaming=false
#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.security.icd.flagmode=single
ro.vendor.extension_library=libqti-perfd-client.so
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
ro.hdcp2.rx=tz
ro.secwvk=144
ro.securestorage.support=true
ro.build.scafe=americano
ro.build.scafe.size=short
ro.build.scafe.shot=single
ro.build.scafe.cream=white
#security.mdpp=None
ro.security.mdpp.ver=1.0
ro.security.mdpp.release=4
ro.security.vpnpp.ver=1.4
ro.security.vpnpp.release=4
security.mdpp.result=None
ro.sec.fle.encryption=true
ro.error.receiver.default=com.samsung.receiver.error
config.disable_atlas=true
ro.config.alarm_alert=Morning_flower.ogg
ro.config.ringtone=Verizon_Airwaves_1.ogg
ro.config.notification_sound=Verizon_Alert.ogg
ro.config.vc_call_vol_steps=7
ro.security.mdpp.ux=Enabled
ro.security.reactive.active=2
ro.security.reactive.storage=param
ro.setupwizard.mode=OPTIONAL
ro.com.google.clientidbase=android-samsung
ro.com.google.clientidbase.ms=android-verizon
ro.com.google.clientidbase.am=android-verizon
ro.com.google.clientidbase.yt=android-verizon
ro.com.google.clientidbase.gmm=android-samsung
ro.com.google.gmsversion=5.0_r1
ro.HorizontalVVM=true
persist.sys.dalvik.vm.lib.2=libart.so
ro.kernel.qemu=0
ro.build.selinux=1
dalvik.vm.isa.arm.features=div
ro.config.knox=v30
ro.config.tima=1
ro.config.timaversion=2.0
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
persist.gps.qc_nlp_in_use=1
persist.loc.nlp_name=com.qualcomm.location
ro.gps.agps_provider=1
ro.pip.gated=0
ro.build.version.sdl=2101


Zijn er mensen waarbij deze regel geprint wordt? Dit mag in principe nooit voorkomen: een oud-lid heeft nog steeds `person.member`. Waarschijnlijk is er dan ooit iets fout gegaan bij invoer.


Thanks, done in 3ff767252b814d28f2e34f21d6ed5fdae3b99434


@schonfeld,

Here as well, you changed the default value. Now this equals to 200 hours, despite the old behaviour was only 12 hours. This might affect all the other users of this river.

Mariam


I'm pretty sure that it'll ignore the symlink... won't it?


I think moduleChooser should be excluded from aligned elements because it is splited into two lines. Otherwise we have too much blank space between label and text field


My original intent here was to solve that `all` in a filtered context returns the full context all, and thus is confusing - I think it might read better if i were to make `rmq(:view).descendants` as that would be clear that it is all descendants of the view without self, but that doesnt solve the `all` confusion - so I will update this to not return self.

Unless my blabbering has changed someone else's view on what it should return, I think I have convinced myself that returning the same as find fixes the confusion for `all` without adding some additional restrictions that you may not want, and may not be obvious, and the solution for those that want the container to be included can chain `and_self` onto it.


Super, das ist nice. Danke.

Ich will ja den Vim auch richtig auf dem Obst benutzen.

Robert

----- Am 23. Jun 2015 um 17:41 schrieb Alexander Wagner notifications@github.com:

> Add a more readable font for the fruits as requested by @rthieledesy
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/aw-bib/vim/commit/a9599e2cfe6f302b1df7f79a6343d18c0044d2ef

--
------------------------------------------------------------------------------
Dr. Robert Thiele
Library and documentation
Deutsches Elektronen-Synchrotron DESY
Building 01d Room OG1.442
phone:  +49-40-8998-1927                                         Notkestr. 85
fax:    +49-40-8998-4440                                         22607 Hamburg
e-mail: robert.thiele@desy.de                                    Germany
------------------------------------------------------------------------------


Is this `Array#delete_if`?


Good catch!


I guess this was wrong already, but don't you have to close ``<li>`` tags?


TeamCity Wordpress :: CorpSite :: CorpSite-Staging :: Launch Environment [Build 1](https://bsr.ict.je-labs.com/viewLog.html?buildId=29441&buildTypeId=Wordpress_CorpSite_CorpSiteStaging_LaunchEnvironment) is now running


Fix proposed upstream at: https://bitbucket.org/dhellmann/virtualenvwrapper/pull-request/34


Agreed.


Für das gits kei schöni annotation? Isch hald bitz heikel, wenn en ganze klassepfad imene xml fix dine isch..


TeamCity Jarvis :: Jarvis.DocumentStore :: Debug / Test / Release [Build 563](http://build.prxm.it:8811/viewLog.html?buildId=3162&buildTypeId=Jarvis_DocumentStore_CI) outcome was **SUCCESS**
Summary: Tests passed: 239 Build time: 00:08:00


Converted it to a single-line component, like it's currently done in IDEA for Java.


Really appreciate y'all working to get the current version of meld supported in Homebrew! However, after updating, I get this:

```
$ meld
Couldn't bind the translation domain. Some translations won't work.
'module' object has no attribute 'bindtextdomain'
2015-06-23 09:31:56.962 Python[3135:3781521] *** WARNING: Method userSpaceScaleFactor in class NSView is deprecated on 10.7 and later. It should not be used in new applications. Use convertRectToBacking: instead.
/usr/local/lib/python2.7/site-packages/meld/meldwindow.py:191: Warning: The property GtkSettings:gtk-menu-images is deprecated and shouldn't be used anymore. It will be removed in a future version.
  self.menubar = self.ui.get_widget('/Menubar')

(meld:3135): Gtk-WARNING **: Could not find the icon 'document-new'. The 'hicolor' theme
was not found either, perhaps you need to install it.
You can get a copy from:
	http://icon-theme.freedesktop.org/releases

(meld:3135): Gtk-WARNING **: Error loading theme icon 'document-new' for stock: Icon 'document-new' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita
/usr/local/lib/python2.7/site-packages/meld/meldapp.py:69: Warning: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
  self.get_active_window().present()

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
/usr/local/lib/python2.7/site-packages/meld/meldapp.py:69: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  self.get_active_window().present()

(meld:3135): Gtk-WARNING **: Error loading theme icon 'go-up' for stock: Icon 'go-up' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(meld:3135): Gtk-WARNING **: Error loading theme icon 'go-down' for stock: Icon 'go-down' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(meld:3135): Gtk-WARNING **: Error loading theme icon 'process-stop' for stock: Icon 'process-stop' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
/usr/local/lib/python2.7/site-packages/meld/ui/gnomeglade.py:45: Warning: The property GtkAlignment:yalign is deprecated and shouldn't be used anymore. It will be removed in a future version.
  self.builder.add_objects_from_file(filename, objects)
/usr/local/lib/python2.7/site-packages/meld/ui/gnomeglade.py:45: Warning: The property GtkAlignment:xscale is deprecated and shouldn't be used anymore. It will be removed in a future version.
  self.builder.add_objects_from_file(filename, objects)
/usr/local/lib/python2.7/site-packages/meld/ui/gnomeglade.py:45: Warning: The property GtkAlignment:yscale is deprecated and shouldn't be used anymore. It will be removed in a future version.
  self.builder.add_objects_from_file(filename, objects)
/usr/local/lib/python2.7/site-packages/meld/ui/gnomeglade.py:45: Warning: The property GtkAlignment:left-padding is deprecated and shouldn't be used anymore. It will be removed in a future version.
  self.builder.add_objects_from_file(filename, objects)
/usr/local/lib/python2.7/site-packages/meld/ui/gnomeglade.py:45: Warning: The property GtkImage:stock is deprecated and shouldn't be used anymore. It will be removed in a future version.
  self.builder.add_objects_from_file(filename, objects)
/usr/local/lib/python2.7/site-packages/meld/ui/gnomeglade.py:45: Warning: The property GtkButton:use-stock is deprecated and shouldn't be used anymore. It will be removed in a future version.
  self.builder.add_objects_from_file(filename, objects)
/usr/local/lib/python2.7/site-packages/meld/ui/gnomeglade.py:45: Warning: The property GtkSettings:gtk-button-images is deprecated and shouldn't be used anymore. It will be removed in a future version.
  self.builder.add_objects_from_file(filename, objects)

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita
/usr/local/lib/python2.7/site-packages/meld/meldwindow.py:600: Warning: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
  self.notebook.append_page(page.widget, nbl)

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkButton': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkToolButton': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkToolbar': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkApplicationWindow': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: Error loading theme icon 'document-new' for stock: Icon 'document-new' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita
/usr/local/bin/meld:274: Warning: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
  status = meld.meldapp.app.run(sys.argv)

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
/usr/local/bin/meld:274: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  status = meld.meldapp.app.run(sys.argv)

(meld:3135): Gtk-WARNING **: Error loading theme icon 'folder' for stock: Icon 'folder' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'go-up' for stock: Icon 'go-up' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(meld:3135): Gtk-WARNING **: Error loading theme icon 'go-down' for stock: Icon 'go-down' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(meld:3135): Gtk-WARNING **: Error loading theme icon 'process-stop' for stock: Icon 'process-stop' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(meld:3135): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: Error loading theme icon 'image-missing' for stock: Icon 'image-missing' not present in theme Adwaita

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkButton': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkToolButton': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkToolbar': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkApplicationWindow': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkToggleButton': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkHBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkAlignment': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkAlignment': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkNotebook': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkApplicationWindow': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkToggleButton': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkHBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkAlignment': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkAlignment': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkNotebook': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkApplicationWindow': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkToggleButton': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkHBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkAlignment': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkAlignment': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkNotebook': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkApplicationWindow': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkToggleButton': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkHBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkAlignment': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkAlignment': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkNotebook': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkApplicationWindow': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkToggleButton': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkHBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkAlignment': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkAlignment': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkNotebook': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkApplicationWindow': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkToggleButton': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkHBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkAlignment': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkAlignment': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkNotebook': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkApplicationWindow': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkImage': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkToggleButton': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkHBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkAlignment': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkAlignment': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkNotebook': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkVBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.)

(meld:3135): Gtk-WARNING **: drawing failure for widget `GtkApplicationWindow': invalid value (typically too big) for the size of the input (surface, pattern, etc.)
```

And things kinda hobble along and don't really work. I've tried uninstalling and reinstalling all the gtk-based dependencies but it didn't help. Any ideas?


Another good catch.


No, this commit is fine and will work as-is.


This has inadvertently exposed hidden petitions to the front-end search.  We need to have a think about how to expose facets as right now all facets are exposed in all searches, and we really don't want hidden ones on the frontend, but at the same time it doesn't feel like the model/facet should be in charge of what does/doesn't appear on the frontend/backend.


I am afraid we have some misunderstanding.

1. You formula:
gmul = grange/(2 ** resolution)

is incorrect, because in this case gmul is unsigned. Then you take xyz unsigned values and perform signing operation on them which reduces their absolute range by half, then you multiply signed values on gmul which is still in the unsigned range.

to have correct values of xyz you have to either multiply xyz on gmul and only then sign them or (I believe it is simpler) just divide the gmul range by half. Therefor the correct formula for gmul must be:

gmul = grange / (2**(resolution - 1))

2. Since the whole applications/algorithms/mathematics world is used to acceleration related to gravity to be measured in m/s^^2, so it is better that the interface to accelerometer will do all necessary transformations to return the acceleration values in convenient and familiar units. That is why I have suggested to use

gmul = 9.80665 * grange/(2 ** (resolution -1))

formula.

3. It is a little unclear that in order to change the G range I have to call standby() before and then activate() after methods for set_g_range() to take an effect. I believe that those calls must be encapsulated within set_g_range() method.


See next commit, forgot to add those files.


Since this feature had never once used, @efg decide to remove this feature.


@albanm can you test if this branch works for your libxslt module
https://github.com/polotek/libxmljs/commit/c95f43b70410675dc3ae473369387e3275e7594c

Basically, this is no longer building in iojs latest on osx using current master and something needs to be fixed. Either `shared_library` needs to be removed or some other logic added so that we can go back to having this work on linux and osx. I certainly don't want to break your module from doing what it is doing so would appreciate the testing since you are most familiar with how your module uses these features.


Er is trouwens [`member.current_member`](https://github.com/WISVCH/dienst2/blob/4da3c95b22de1b1c71491e2bfe5d0bf4a761160a/ldb/models.py#L251-L254) om te checken of iemand lid is. Weet niet helemaal of we bij LvV'ers de `data_to` willen invullen (wordt in deze versie wel gedaan), kan op zich geen kwaad. Buitengewone leden zijn nog een apart geval (Hebben we die dit jaar? Zo ja, dan gaat dat hier ook fout), zie ook #51.


@magiconair yah that's def a typo. Surely I meant "12 * 60 * 60" (h * m * s) ... Oops :)


I'd like to use Webmachine on Yaws.  Would this branch be appropriate to use as a starting point, based on the assumption that it will be merged sometime in the future?

-TimS


:+1: to what @one-more-minute said.  I haven't seen him disinclined at all, I imagine, like all of us, he's rather busy, and he has already done some very nice improvements to `Docile.jl` that just need to be factored correctly into (and out of) Base.


that's wrong. revert https://github.com/airlessproject/android_device_sony_common/commit/801830614602f8b4602c75f8704eb19c0cf1fd9d, then dogo will no longer need a separate branch.


bot user js


Saving scenes is important thing! :laughing:


So I reckon we document 8.5.5.6 and then we can always add additional (and more confusing) instructions for an earlier version if necessary.


Can you add javadocs what this represents?


Sorry, @one-more-minute, I'm not trying to pick on you – just to push this forward since I *really* want docstrings in the language. Let's continue discussion over here: https://github.com/JuliaLang/julia/issues/8965.


Verder goed bezig trouwens, een grote schoonmaak van de database is long overdue.


Also, not neccessarily a problem with this commit, but it has exposed it.  If we hit `http://localhost:3000/petitions?state=monkey` then we end up with a `ActionView::MissingTemplate` which isn't great (it's looking for `search/petitions/_petition_result_for_facet_monkey.html.erb`).  We might want to sanitize the state param before we use it.

Perhaps solving this and the above comment about exposing the facet should be a separate bug?


@naktb do not change this line


TeamCity Wordpress :: CorpSite :: CorpSite-Staging :: Launch Environment [Build 1](https://bsr.ict.je-labs.com/viewLog.html?buildId=29441&buildTypeId=Wordpress_CorpSite_CorpSiteStaging_LaunchEnvironment) outcome was **FAILURE**
Summary: Exception Thrown; error message is logged Build time: 00:09:15


@one-more-minute What about documenting type/immutable members, like Doxygen does?
I find that incredibly useful, it would be nice if a void string (or a ## say) after a member could be added to the documentation (with the info on type name, member name, type, file name/line number).
[this isn't about Doxygen at all, just about saving the metadata for later processing]


Hmm, why not use totem..?