@bukka generally we don't put news into master, true. But right now master is our PHP7 base, so any fixes, if they apply to PHP7 as well (no empty merge) should be added there. So looks like @cmb69's NEWS entry was correct in master. It is the same how it's being done earlier say if you push a fix into 5.5 which is same in 5.6 - both branches NEWS should be updated.

Soon there'll be PHP-7.0 branch, so then the NEWS should be updated there. When the 7.0 branch is there, master will turn to the unstable again (as base for 7.1 and further), so should become only the entries that apply to master only. There'll be a notification on the list as soon as PHP-7.0 branch was created.

Thanks.


This is a good idea. Possibly in `ImageOpener`, explaining that this is modified, and here, pointing to `ImageOpener` docs?


Tempted to suggest to check that this isn't already in the list, but .. I don't think it's worth the effort (especially for testing)

Also, this makes a hard declaration that `Openers` are only relevant in "alternate" image extensions. Again, I think that's fine... just thinking out loud.

I am good with all this.


Hi, @xrow. This release doesn't contain any changes affecting alignment. I plan refactoring code base which is responsible for alignment, but all the changes are in `develop` branch. What kind of issues do you experience?


Has this been implemented? Smeargle seems to be getting around this check, if so.


Yup!


Sounds good to me.


Yes!

Thank you. for this. A dynamic maxblocksize makes much more sense. Nobody knows when Bitcoin will go viral... so system must be able to adapt, same as with the difficulty level.


Regarding the escaped unicode, I used to call `ascii2uni -a U filename` too convert to UTF-8. But then I stopped worrying about it since deserializers seem to handle it transparently. It seems to be pretty standard (the spec say any character can be escaped like that but most don't need to be, so it does inflate the file size unnecessarily).


@vadz With your refactorizations the vertical scrolling is now inverted, and doesn't work as intended. Scrolling up should move into the past as it does in both of the native calendar controls.


아오 힘들었다...


I don't understand. Maybe the word "toggle" is misleading but the behaviour is always enabled.


Yes. I was a bit lazy to make an other pull request just for that. I did not think it was big deal since it doest not change the layout much.


Oh, that disadvantage is a very good point. It's too bad there's not a way to import the code that makes up a method (with no arguments) as a left-indented block of code that looks like a script, for read the docs purposes.

(or is there?)


endpoint


@knuesel So, I am not sure: which one (JSON vs CSV) is the more accurate?

@Giovanni1085 I will do it :) I currently cannot.

@douglas-watson Can you activate *Issues* for this repository?


OK but I like the idea of having access to the full comments. Otherwise you still have to take an other software to be able to read them ...


Why you need to filter values in line 1399? What is the bug?


I think I disagree on the hard declaration. It indicates that `Openers` *may* add new extensions, which seems true.


habe gehackt:
68916e05b648867b1c79e26f9bd162977273640c
5e1dd31e5c94ffae1bcaf6e0effaba71b1a80d3a


TODO: get default properies from ```defaultProperties``` field


Yeah, or perhaps more conservative (from a "we should test most things" perspective) would be to special-case / decorate tests that should not be run for certain solvers (such as expensive tests).


Doesn't the line of code always add a new extension to `alternate_exts`? So if you use the decorator, it adds a new extension. Maybe I should just say, the *decorator* is only relevant for "alternate" image extensions.


rm


Oi, what about the maximum amount of time a lockdown can be initiated for? Will you do it aswell?


moved to https://github.com/convexopt/gpkit/issues/396


Oops, I didn't notice the checks were in the opposite direction, sorry, I didn't change this intentionally and will fix it now.


This should still be one line above I think.


No added functionality. Seems to be a local VS extension. --rejected.


There was a problem in the UHD sink GRC wrapper, where opening old flowgraphs would cause a "template error" in the generated Python.  I'm not familiar enough with the changes to debug it, so I reverted it and was waiting to get a hold of you :-)


Sure, but if it adds a duplicate extension, that makes zero difference to anything, except make `is_valid_extension` take slightly longer to return `False`.


@knuesel OK, no problem then.

Hack tip for getting a working CSV file until the bug is corrected:
`sed '$d' items-full-final-with-bio.csv > items-full-final-with-bio_2.csv`


:dancers:


@pires How would one go about attaching persistent storage to the elastic search cluster, the example looks very flimsy to me for the basis of a production quality setup


Indeed. Should have been more careful.


Kind of hard to find satisfying colors for this, feel free to tweak more.


@pafonta as far as I can tell the JSON is 100% correct. The CSV files are truncated due to a missing flush() in csv_converter. I am regenerating the files, should be uploaded in 30 minutes or so.


Should brial be made to depend explicitly on `automake-1.5`? Here in prefix I get
```
WARNING: 'automake-1.15' is missing on your system.
         You should only need it if you modified 'Makefile.am' or
         'configure.ac' or m4 files included by 'configure.ac'.
         The 'automake' program is part of the GNU Automake package:
         <http://www.gnu.org/software/automake>
         It also requires GNU Autoconf, GNU m4 and Perl in order to run:
         <http://www.gnu.org/software/autoconf>
         <http://www.gnu.org/software/m4/>
         <http://www.perl.org/>
Makefile:424: recipe for target '/storage/strogdon/gentoo-redlizard/var/tmp/portage/sci-mathematics/brial-0.8.4.3/work/brial-0.8.4.3/Makefile.in' failed
```
and there doesn't appear to be anything in my world file that would require building the newest automake.


I see. I'm fine with this.


@pfalcon @dpgeorge for some reason this test fails on the WiPy. The warning message is not printed...
Any idea why?


Hm. Now I know why a couple of key bindings didn't work for me in git. I'm a user that finds the extrastereo and karaoke filters useful.

I enjoy listening to music using the extrastereo and karaoke filters because it changes the perspective of the music and gives me a different listening experience. Additionally, the extrastereo filter is especially useful for when a video has the audio reversed by mistake and is not corrected by the video producer. I can listen to the video the way it was intended without altering it.

A key reason I use mpv is due to the filter options that are available. In my previous media setup, Audacious was the only program that had the karaoke filter and VLC was the only player that had the reverse stereo filter. My main player didn't have those filters so my listening experience was fragmented. Mpv changed that by providing those filters in one program instead of rotating between three.

Personally, I think most audio filters should remain; and that includes video filters too if that comes up in the future. They give many options for tinkering with multimedia files.

I think of them like tools in a toolbox. What tools are useful depends on what you use them for. It's sensible to remove or replace obsolete/broken tools, but the uncommonly used ones can still have a place. I'm sure there are users that make use of filters that may seem unnecessary.


@knuesel Thx!


shellx64_v2.efi won't do
I think the easiest solution is bundle the systemd-bootx64.efi in manjaro-tools and copy that.
If we use refind I think we will need to redo the config files because the ones we use now are for gummiboot.


No, that should be left up to the players in the server. Any maximum amount is bound to piss off someone somewhere.


I am talking purely in-terms of underlying data/index.


Thanks! Looks good.


RAS


As per #93


There are lots of situations where a 12 year old Mayor, Fuhrer, President or whatever (depends on the server) makes a lockdown and it goes on forever until an admin intervenes (which is rare on most servers).
But it's your will and I won't argue with it. I guess I will have to do the maximum time as a script on my own server, cheerio.


Note to self: this worked on OS X, but caused trouble on Ubuntu.


I would change the config, I just have no clue where eg grub gets the binary from.

Another question is, if this systemd binary is techniclly the same gummiboot provides?

I am more or less against the systemd-binary if we can use a neutral one. We could make systemd use that binary.


comment


`count` comes from `GetIssuesParamsSupport.computeCount()` that already clamped the value up to `GetIssuesParamsSupport.ISSUE_COUNT` it is returning always 1 loop and request `GetIssuesParamsSupport.ISSUE_COUNT` issues even if the user specifies more in the spinner.  Maybe this condition needs to compare the value of Math.min(maxIssueCount, allIssuesCount) > maxCount` to determine if multiple loops are needed.


In theory is the same binary provided by gummiboot, maybe some updates, but I don't think there is anything that ties the .efi file to systemd.


Rubisk is right. It's better to use a separate branch to separate working code from code under development. This way you don't litter your codebase with dead, unused code, and it's easier to find out when other changes have broken either your working code or your in-development code.

> Stripping code will make it unavailable

No, that's the entire point of version control. The code your stripped is still available in the past revisions.


Well, systemd history proves otherwise, and its the same naughty strategy that windows uses.
I bet there is or will be somewhere a show stopper for non systemd with this.


This needs a revbump afais, otherwise people don't get the missing files.


 | 元のコード | 後のコード | 欲しかったもの
--- | ------ | ------ | ------
`17 % 3` | 2 | 2 | 2
`17 % -3` | 2 | -2 | -1
`-17 % 3` | -2 | 2 | 1
`-17 % -3` | -2 | -2 | -2


Reverted with 6b9e7a59bc1ac5958282201fe68efb315446da53

I honestly don't get what you want so I wait until you explain me further :)


This is great. We also need to update the GI links for use with swissprot


I wrote a comment before here but got no answers, so i opened a separate github "issue".
Anyway, i completely agree with you.


TeamCity ReOpenLDAP :: devel-2.4 [Build 190](https://binbug.bigbrother-matrix.ru/teamcity/viewLog.html?buildId=443&buildTypeId=ReOpenLDAP_Devel24&guest=1) is now running


Hey Ryan, not sure if you found an answer to this question yet. Yes, the
recent work on complete_r_script.R was to incorporate SEUS (spring,
summer, and fall) to OceanAdapt.
Jim

> add updated Data_Vis
>
> needed one that contained SEUS for complete_r_script.R to run properly
> @mpinsky @JWMorley I assume this is what you guys have been doing locally?
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/mpinsky/OceanAdapt/commit/67bcaf8c16a75ab4c7473c4168769f73ac7f0e28
>


The problem is that is makes this gem incompatible with Rails 4.1


The use of `empty-state` here means that this will only expand core macros. It won't work for required macro namespaces that have affected the analysis environment.


I justed pushed the [feature/l16-encoder](https://github.com/masmu/pulseaudio-dlna/tree/feature/l16-encoder) branch. You can try it out to test the L16 encoder.


What was the warning?


Instead of using `cljs.js` and its async API, `cljs.analyzer/macroexpand-1` can be built upon to achieve a synchronous solution. (But, the trick, as above with `empty-state` would be to somehow gain access to the analysis environment.)


I couldn't find one. :(


@fabienwang I think you replaced some of our custom textures, that's something you **don't** make fun of with him.


There is an of missing here.


i think it's better to not pass the api key over a query param. see for example https://blog.httpwatch.com/2009/02/20/how-secure-are-query-strings-over-https/. Let's use the authorization header or a custom one.
yes, we love you security :)


That's why I added the `fasttests` script, so that we could make the tests more expensive and run the full suite only on Jenkins / just before pushing.


Looks like I already found that typo some days ago :D.
However - please change that in the src-directory and compile the script.
I will accept the PR when this is done


@noaneo That's doesn't have anything to do with *Twenty Fourteen for EDD*. It's just a child theme that adds Easy Digital Downloads components. The layout of the theme itself is specific to Twenty Fourteen's CSS.


Removed this clause, because AFAIK you can't be a team's supervisor without a team.


Enlace a Github


Didn't know that.


Fixes #6


@pafonta the non-truncated CSV files are on master, sorry for the trouble... (now let's see what the next problem is :) )


Placemarker for ongoing review/integration is here.


I added the systemd efi file to manjaro-tools, can you check if this works with openrc?


I will check it, about to build iso.
I will be slightly angry, if the systemd voodoo throws errors. :)


Ok cool. Fixed in https://github.com/php/php-src/commit/22e23e7cb8ca9aa134d138b5fed031af6c842b44


Did you try calling `input.open()` before add an event listener? C.f. [webaudio.github.io](https://webaudio.github.io/web-midi-api/#widl-MIDIPort-open-Promise-MIDIPort):

> [...] some underlying implementations may not be able to support shared access to MIDI devices, so using explicit open() and close() calls will enable MIDI applications to predictably control this exclusive access to devices.

```javascript
input.open().then(function () {
  input.addEventListener('midimessage', function (e) {
    trigger(MIDI, e);
  })
});
```


Works perfectly fine for me @zfrenchee. I created a template in Mailchimp and sent that over to my connected mandrill account. The merge vars were created in the Mailchimp template editor using the *|VARNAME|* syntax.


Acid part:
http://paste2.org/H9YYKCw8


unavailable :)


Strange. It didn't work for me, but I switched over to the {{handlebars}} syntax and ended up getting merge vars to work that way. I think I might open a PR for global_merge_vars as well.


> it goes on forever until an admin intervenes

Does nobody use the demote system?


Thanks @Thecrazyskull  :) I will try and report ;)


@dx486 Hi

>> sudo install -m 0600 -o root -g root rules.conf /etc/usbguard/rules.conf
>
>I created /etc/usbguard/rules.conf by using mkdir and cp commands but it seems that I cannot start the >service.
>
>> sudo systemctl start usbguard.service
>
>command returns
>
>> Failed to start usbguard.service: Unit usbguard.service failed to load: No such file or directory.

You'll have to install the usbguard.service file to /etc/systemd/system/ and the daemon configuration file. Try the following steps:

```
$ cd your_git_repo_clone/
$ sudo usbguard-generate-policy > rules.conf
(edit your policy)
$ sudo mkdir -p /etc/usbguard
$ sudo cp dist/usbguard-daemon.conf /etc/usbguard/usbguard-daemon.conf
(edit IPCAllowedGroups or IPCAllowedUsers settings)
$ sudo cp rules.conf /etc/usbguard/rules.conf
$ sudo cp dist/usbguard.service /etc/systemd/system
$ sudo chown -R root:root /etc/usbguard
$ sudo chmod 0700 /etc/usbguard
$ sudo chmod 0600 /etc/usbguard/*
$ sudo systemctl start usbguard.service
```

>> "Inactive. No IPC connection."
>
>message on its "status bar". What does it mean? Is the service active?
>
>I am not sure if the service runs or not. I suspect it does not.

The service is not running. If you don't want to install the usbguard.service file and run the daemon manually instead, just start the /usr/sbin/usbguard-daemon binary from the command-line (as root). Use the `-d` and `-k` options to enable debugging messages:

```
$ sudo usbguard-daemon -d -k
```

After you start the daemon, the applet should automatically connect.

I'll try to update the How-To with the correct list of packages to install. And I'll probably add an option to the configure script to install the systemd service file on make install.

Thanks for the feedback! Don't hesitate to use the issue tracker to report bugs anywhere in usbguard (https://github.com/dkopecek/usbguard/issues).


nah, I moved m_sampleOfSilence to a ptr instead of auto-create in header. Dealing with include madness and wanted to forward declare it. AE has many circular include issues.
I tend to forward declare as much as I can to limit include scope. Nothing worse than spewing includes all over the place.


The icons are still misplaced...?


make two files
1. todoService.js
2. todoController.js


You did a lot of work there and the code looks perfect. I just came back from holiday, i need some days to sort out my mails and customer requirements, but then your improvements will definitly be in the next release.


rename this to .getAllTodos
and must be a function


= TodoService.getAllTodos();


commit de creacion del repositorio


what is searchtwo, name it properly


ja, ist besser so. negierung verneinen, und bessere lesbarkeit.

+1


same as abouve searchfour?


Nobody actually.


So basically, if a player who doesnt have the permission prism.parameters.action.required (which should be everyone because of the default setting in plugin.yml) he should be able to do rollbacks without the action defined?


should just be todos not todos.list


wire in the add button


warum sind bei der deklaration mal semikolen und mal nicht? fehler oder feature?


From what I've noticed, people only use it for people they don't like or for reasons that are against server rules. Nobody even roleplays properly nowadays sadlu.


102817062_MultiSpeedFan (Nigusse) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

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


What's that ```show``` method?


local show = ply:EntIndex() == 0 and print or fp{DarkRP.notify, ply, 1, 4}


Ok making above changes


102817062_MultiSpeedFan (Nigusse) - x86_64-MacOS-10.9-clang: OK (1822 of 1824 tests passed)

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


This line seems a typo/pasto, because the RHS still contains the Scala thingy!


STM32F4 and STM32L1 targets only. Other STM targets are infected with the same bug.

Minimal changes to rtc_api.c file to avoid resetting the RTC time registers during a nRST also during a power down if a backup cell has been fitted.
Tests for ISR register reset value (Dec 7) to force a full RTC reset. Any other value leaves the RTC time registers unchanged and continue running. Tested on the Nucleo F401RE and L152RE both with and without backup cell connected to vBAT (link SB45 removed).


To be sure: can you retest the bug you reported on the ML after fixing this?


Should we drop StringBuilderClass (and the actual class definition) altogether?


I would like to compile the script, but it's not working (as it should)
```[user@host svg.js]$ gulp unify
[20:32:21] Using gulpfile ~/tmp/svg.js/gulpfile.js
[20:32:21] Starting 'clean'...
[user@host svg.js]


I get a Nullpointexception at this Point. If I comment Line 28-30 out then everything is working as expected (also the Broadcast Message is Received in my Receiver).
For what is this good?


For telegram's bot @learn_quran_bot.


Full PHPDocs are recommended for types declarations (@var String).


Are you missing `defer` on this line?


@tsg Where does this image come from? I don't see it on docker hub. I suspect it needs to be built and tagged locally from https://github.com/tsg/xgo?


@CeytiX thanks, now I understand this (:


Always have the name of enumerations first ex. FIELD_IDGEN for smarter autocompleting.


@kt10aan
Which environmental variables you'd like to add? I'm not a fan of environmental variables.

For example, for the open file I rather set the directory in the open dialog to be the last one opened (maybe starting in the home directory),


Ура


Do you even need for local variable if you do not use it anywhere than the next line?


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


If this local variable is used only within the if..else block - declare it within this block ex. file_exists(($filename = static ...))


You don't need to do that. Just check that after using the hero power, the hero is still at 30 health.


I'm curious. Is this truly the only way? `pre-command-hook` makes me pretty nervous. Could we instead advice important functions with `before`?


s/int avail/size_t avail/


This is causing a deadlock at startup on one of my OS X machines (OS X 10.8). It is not entirely related to one part (shared QMLEngine) vs. another (synchronous metadata loading).


Nullpointerexception to above comment:

    09-06 20:32:10.299  20600-20600/com.develapp.meetfriends E/AndroidRuntime﹕ FATAL EXCEPTION:    main
    Process: com.develapp.meetfriends, PID: 20600
    java.lang.RuntimeException: Unable to instantiate service      com.cowbell.cordova.geofence.ReceiveTransitionsIntentService: java.lang.NullPointerException
            at android.app.ActivityThread.handleCreateService(ActivityThread.java:2576)
            at android.app.ActivityThread.access$1800(ActivityThread.java:145)
            at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1288)
            at android.os.Handler.dispatchMessage(Handler.java:102)
            at android.os.Looper.loop(Looper.java:136)
            at android.app.ActivityThread.main(ActivityThread.java:5081)
            at java.lang.reflect.Method.invokeNative(Native Method)
            at java.lang.reflect.Method.invoke(Method.java:515)
            at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:781)
            at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
            at dalvik.system.NativeStart.main(Native Method)
     Caused by: java.lang.NullPointerException
            at android.content.ContextWrapper.getSystemService(ContextWrapper.java:540)
            at com.cowbell.cordova.geofence.ReceiveTransitionsIntentService.<init>    (ReceiveTransitionsIntentService.java:29)
            at java.lang.Class.newInstanceImpl(Native Method)
            at java.lang.Class.newInstance(Class.java:1208)
            at android.app.ActivityThread.handleCreateService(ActivityThread.java:2573)
            at android.app.ActivityThread.access$1800(ActivityThread.java:145)
            at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1288)
            at android.os.Handler.dispatchMessage(Handler.java:102)
            at android.os.Looper.loop(Looper.java:136)
            at android.app.ActivityThread.main(ActivityThread.java:5081)
            at java.lang.reflect.Method.invokeNative(Native Method)
            at java.lang.reflect.Method.invoke(Method.java:515)
            at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:781)
            at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
            at dalvik.system.NativeStart.main(Native Method)


:+1: You're right. That condition is never `true`. Thanks for catching it!


Please help us, your excellent application is no longer backing up SMS messages to Gmail. I have 2 phones using your app and both stopped working approximately 1 day ago


s/-W/-Wextra/


@leofeyer what do you think=


ID starts with 0 - it is probably not supposed to. There's default 0 initialization and here is a post-incrementation of the class field.


**gummiboot** got renamed to [systemd-boot](https://wiki.archlinux.org/index.php/Systemd-boot). So the simplest solution would be to provide this file in a different package also for **openrc**. Currently it is part of the **systemd** package. A configuration change might not be needed, as it is the same software.


@s3r1alpari4h
please do. i used that gitversion.exe (which just calls a bunch of GIT commands) because the make script didn't want to execute them... i'd prefer it if it was an actual script though... (hence the bat that also didn't work... )


I think you should add a `\grenobreak` here, otherwise, line might break at a bad place, with a bad penalty


reviewed, thanks for contribution


Maybe after -r tofix.csv to add the path to the -r still_hardcoded.csv to restore the original hardcoded?
Or something.


I think you should use a kern here


Isn't even needed anymore after 9484816.


Is the function declared in line 15 called anywhere in the code?
Session.get("hideCompleted") is called in line 7 directly


I like that you used this before we covered this topic!


I don't know actually! We discussed raising the minimum in https://github.com/contao/core-bundle/issues/113 but then it was reverted again in https://github.com/contao/core-bundle/commit/eb8e26e83cf22df5785ce78c22a798ae3d27dc3e.
Maybe @leofeyer can tell the correct requirements for Contao 4.0?


Thank you very much for your quick helpful reply. I followed the instructions you have just gave me and they worked, except I had to use

> sudo chmod 0600 /etc/usbguard/usbguard-daemon.conf
> sudo chmod 0600 /etc/usbguard/rules.conf

instead of

> sudo chmod 0600 /etc/usbguard/*

as it returned:

> chmod: cannot access ‘/etc/usbguard/*’: No such file or directory

> I'll try to update the How-To with the correct list of packages to install. And I'll probably add an option > to the configure script to install the systemd service file on make install.

These would be awesome.

Thank you for this great tool. It fills an important security gap.


This is not good. We should provide a separate package for openrc here. Simply extract the efi file from **systemd** and repack it for example to **openrc-loader-efi**


I know, kept it there for intrafunction consistency and general laziness.


@CeytiX I recommend and insist using *reference* to `std::string` so we will save more memory, even though it doesn't save much (:


ss has been made unsigned, so max_inv needn't be cast signed.


Else we can bundle it here and update it if needed. Depends ...


Also, you shift -eolshift twice, I think one of the the shifts must be have its `-` removed. There is certainly a missing hbox too. The diff is quite difficult to read, and the fact that it does many different things at a time (compute -> calculate for instance) doesn't help... A little documentation here would be welcome too as, as you've seen, this is a quite intricate mechanism...


Do not need to check for its value - there is no possibility to have a 'false' there.


die Semikolon's machen es moeglich mehrere variablenzuweisungen hintereinander zu schreiben und *kein* leerzeichen drinne zu haben. also folgendes

VAR1=bla;VAR2=blubb VAR1=hi;VAR2=du VAR1=hier;VAR2=jetzt

auch wenn es nicht so aussieht, so ist es doch eine kommaseparierte liste.
es geht also:

for ELEMENT in $LIST; do
  echo $ELEMENT
done

ausgabe:
VAR1=bla;VAR2=blubb
VAR1=hi;VAR2=du
VAR1=hier;VAR2=jetzt

und deswegen geht auch:
eval $( _list random_element "$TABLE" )


But there is no npcs?


@CeytiX how many items can be stored in the player's inventory?


FYI: I needed to get all metadata as well as whitespace/comments aware parser. Basically I wanted to build a replacement for rewrite-cljs based on tools.reader without patches. It seems that it is possible to hijack log-source* and implement that functionality without changes to tools.reader itself.

Here’s my whack at it:
https://github.com/darwin/tools.reader/commit/2080678198027b2ff3d37c47d6f1d71738b56aac


I like how you did two of the cases as ASCII numbers. I ran the code on my netbeans and it worked well!


Do you even need to check whether a class is to be saved? That 'false' seems not to be used anywhere else.


Are you sure you need to use it? Won't it be called twice (once here and once in the same way as other syllables)?


I don't think so.


seems this is intended :O


Looks like this one was actually just an accidental change based on the actual commit that changed it.  But its good that it got caught before it went to far :)


no spawns doesn't mean that other fixes can't be done..


@daspilker great new feature! Do you have an idea when the next release is coming? Want to start using it :)


r has been made unsigned, so trace_regs needn't be cast signed.
Can k be made unsigned?


This separate package would only be used to build isos, I don't see much point to make a package that only manjaro-tools/buildiso will use.


Two aggregate nodes at the coordinator without a view
select distinct max(P_D2), P_D1 + 3 from P where P_D1 + 3 > 0 group by P_D1 order by P_D1 + 3
RETURN RESULTS TO STORED PROCEDURE
 Hash AGGREGATION ops
  ORDER BY (SORT)
   Hash AGGREGATION ops: MAX(VOLT_TEMP_TABLE.column#0)
    RECEIVE FROM ALL PARTITIONS
     SEND PARTITION RESULTS TO COORDINATOR
      INDEX SCAN of "P" using "P_D1PLUS3_IDX"
      range-scan covering from ((P_D1 + 3) > 0) to end
       inline Hash AGGREGATION ops: MAX(P.P_D2)

The partition result is ordered because of P_D1 + 3 is an index expression. The optimization is The optimization is impossible for two reasons:
   GROUP BY and ORDER BY columns don't overlap preventing the hash aggregate to be converted to Serial/Partial aggr
  Two aggregate nodes at the coordinator


Thanks for this code @sucksido

I see you have only added one field filter. Remember I mentioned that we need to filter on all fields displayed on this invoice listing.
Please add filters on Date, Invoice Number, Description, and Amount

NOTE: For Date and Amount you can put ranges e.g.

User should be able to search for Invoices where the invoice date is between 2015-08-01 and 2015-09-01  AND invoice amount is is between R5,000 and R10,000 for example.

![image](https://cloud.githubusercontent.com/assets/5468546/9706042/4b872b24-54d9-11e5-84ad-255e49aafd89.png)


Hi, would you care to merge it back in with a PR? thanks!


Do we care here for unicode characters and other stuff?


@CeytiX I can't get the idea of that line.
Could you explain me please in details what is done here?


Note that before it looped over a *copy* of the array, which I believe is necessary in order to avoid a `ConcurrentModificationException`


Good info phil.

So please lets rename that ugly systemd name to something neutral to avoid confusion.


Even here you mention that this array is to store only true's - why do you want to store false's then?


@offlinehacker: meta.description should not include package name and not end with a dot.


Coole sache! Ich teste gleich mal! Dann reverte ich das `shuf`. Danke!


I am with kirek here,
I also see no point to have separate packe, We just provide it with manjaro-tools-iso pkg.
But lets rename the binary please.


the the


@htgoebel Where should I add 'datas'/'binaries' into GUTS? In the 'Analysis' guts there are already 'datas/binaries' for 'self.binaries', 'self.datas'.  Or should GUTS for 'datas'/binaries' rather call function `_check_guts_eq`?


Leave a line note


102817062_MultiSpeedFan (Nigusse) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (766 of 768 tests passed)

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


102817062_MultiSpeedFan (Nigusse) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1828 of 1830 tests passed)

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


Should maybe be freebsd.sh here?


4: L102 copyright year is outdated, expected 2015 but got 2014
37:5: E128 continuation line under-indented for visual indent
40:5: E128 continuation line under-indented for visual indent


4: L102 copyright year is outdated, expected 2015 but got 2013
24:1: E402 module level import not at top of file
25:1: I201 Missing newline before sections or imports.
25:1: E402 module level import not at top of file
26:1: I100 Imports statements are in the wrong order. import shutil should be before import pkg_resources
26:1: I201 Missing newline before sections or imports.
26:1: E402 module level import not at top of file
27:1: E402 module level import not at top of file
28:1: E402 module level import not at top of file
29:1: I201 Missing newline before sections or imports.
29:1: E402 module level import not at top of file
30:1: E402 module level import not at top of file
31:1: E402 module level import not at top of file
33:1: E402 module level import not at top of file
73:1: E302 expected 2 blank lines, found 1
83:13: E266 too many leading '#' for block comment
86:13: E266 too many leading '#' for block comment
185:25: E251 unexpected spaces around keyword / parameter equals
215:25: E225 missing whitespace around operator
215:51: E225 missing whitespace around operator
227:1: E302 expected 2 blank lines, found 1
272:25: E251 unexpected spaces around keyword / parameter equals
277:22: E261 at least two spaces before inline comment
385:1: E303 too many blank lines (3)
394:45: E251 unexpected spaces around keyword / parameter equals
394:47: E251 unexpected spaces around keyword / parameter equals
395:46: E251 unexpected spaces around keyword / parameter equals
395:48: E251 unexpected spaces around keyword / parameter equals
395:63: E251 unexpected spaces around keyword / parameter equals
395:65: E251 unexpected spaces around keyword / parameter equals
396:43: E251 unexpected spaces around keyword / parameter equals
396:45: E251 unexpected spaces around keyword / parameter equals
398:45: E251 unexpected spaces around keyword / parameter equals
398:47: E251 unexpected spaces around keyword / parameter equals
399:46: E251 unexpected spaces around keyword / parameter equals
399:48: E251 unexpected spaces around keyword / parameter equals
399:63: E251 unexpected spaces around keyword / parameter equals
399:65: E251 unexpected spaces around keyword / parameter equals
400:43: E251 unexpected spaces around keyword / parameter equals
400:45: E251 unexpected spaces around keyword / parameter equals
407:42: E251 unexpected spaces around keyword / parameter equals
407:44: E251 unexpected spaces around keyword / parameter equals
407:59: E251 unexpected spaces around keyword / parameter equals
407:61: E251 unexpected spaces around keyword / parameter equals
408:40: E251 unexpected spaces around keyword / parameter equals
408:42: E251 unexpected spaces around keyword / parameter equals
408:66: E251 unexpected spaces around keyword / parameter equals
408:68: E251 unexpected spaces around keyword / parameter equals
409:43: E251 unexpected spaces around keyword / parameter equals
409:45: E251 unexpected spaces around keyword / parameter equals
411:42: E251 unexpected spaces around keyword / parameter equals
411:44: E251 unexpected spaces around keyword / parameter equals
411:59: E251 unexpected spaces around keyword / parameter equals
411:61: E251 unexpected spaces around keyword / parameter equals
412:40: E251 unexpected spaces around keyword / parameter equals
412:42: E251 unexpected spaces around keyword / parameter equals
412:66: E251 unexpected spaces around keyword / parameter equals
412:68: E251 unexpected spaces around keyword / parameter equals
413:43: E251 unexpected spaces around keyword / parameter equals
413:45: E251 unexpected spaces around keyword / parameter equals
423:51: E251 unexpected spaces around keyword / parameter equals
423:53: E251 unexpected spaces around keyword / parameter equals
424:35: E128 continuation line under-indented for visual indent
424:46: E251 unexpected spaces around keyword / parameter equals
424:48: E251 unexpected spaces around keyword / parameter equals
424:63: E251 unexpected spaces around keyword / parameter equals
424:65: E251 unexpected spaces around keyword / parameter equals
425:35: E128 continuation line under-indented for visual indent
425:43: E251 unexpected spaces around keyword / parameter equals
425:45: E251 unexpected spaces around keyword / parameter equals
427:51: E251 unexpected spaces around keyword / parameter equals
427:53: E251 unexpected spaces around keyword / parameter equals
428:35: E128 continuation line under-indented for visual indent
428:46: E251 unexpected spaces around keyword / parameter equals
428:48: E251 unexpected spaces around keyword / parameter equals
428:63: E251 unexpected spaces around keyword / parameter equals
428:65: E251 unexpected spaces around keyword / parameter equals
429:35: E128 continuation line under-indented for visual indent
429:43: E251 unexpected spaces around keyword / parameter equals
429:45: E251 unexpected spaces around keyword / parameter equals
437:1: E302 expected 2 blank lines, found 1
467:54: E203 whitespace before ','
469:59: E203 whitespace before ','
504:1: E302 expected 2 blank lines, found 1
524:1: E302 expected 2 blank lines, found 1
532:1: E302 expected 2 blank lines, found 1
537:35: E251 unexpected spaces around keyword / parameter equals
537:37: E251 unexpected spaces around keyword / parameter equals
540:65: E203 whitespace before ':'
540:69: E201 whitespace after '{'
540:74: E203 whitespace before ':'
540:36: E251 unexpected spaces around keyword / parameter equals
540:38: E251 unexpected spaces around keyword / parameter equals
540:56: E251 unexpected spaces around keyword / parameter equals
540:58: E251 unexpected spaces around keyword / parameter equals
545:36: E251 unexpected spaces around keyword / parameter equals
545:38: E251 unexpected spaces around keyword / parameter equals
555:35: E251 unexpected spaces around keyword / parameter equals
555:37: E251 unexpected spaces around keyword / parameter equals
558:36: E251 unexpected spaces around keyword / parameter equals
558:38: E251 unexpected spaces around keyword / parameter equals
576:28: E251 unexpected spaces around keyword / parameter equals
576:30: E251 unexpected spaces around keyword / parameter equals
576:43: E251 unexpected spaces around keyword / parameter equals
576:45: E251 unexpected spaces around keyword / parameter equals
576:60: E251 unexpected spaces around keyword / parameter equals
576:62: E251 unexpected spaces around keyword / parameter equals
577:28: E251 unexpected spaces around keyword / parameter equals
577:30: E251 unexpected spaces around keyword / parameter equals
577:43: E251 unexpected spaces around keyword / parameter equals
577:45: E251 unexpected spaces around keyword / parameter equals
577:61: E251 unexpected spaces around keyword / parameter equals
577:63: E251 unexpected spaces around keyword / parameter equals
577:70: E261 at least two spaces before inline comment
579:42: E231 missing whitespace after ','
580:42: E231 missing whitespace after ','
584:28: E251 unexpected spaces around keyword / parameter equals
584:30: E251 unexpected spaces around keyword / parameter equals
584:43: E251 unexpected spaces around keyword / parameter equals
584:45: E251 unexpected spaces around keyword / parameter equals
585:28: E251 unexpected spaces around keyword / parameter equals
585:30: E251 unexpected spaces around keyword / parameter equals
585:43: E251 unexpected spaces around keyword / parameter equals
585:45: E251 unexpected spaces around keyword / parameter equals
585:49: E261 at least two spaces before inline comment
586:43: E231 missing whitespace after ','
587:43: E231 missing whitespace after ','
590:43: E231 missing whitespace after ','
591:43: E231 missing whitespace after ','
591:65: E261 at least two spaces before inline comment
612:5: E303 too many blank lines (2)
637:14: E261 at least two spaces before inline comment
637:15: E262 inline comment should start with '# '


4: L102 copyright year is outdated, expected 2015 but got 2013
26:1: E402 module level import not at top of file
27:1: E402 module level import not at top of file
28:1: E402 module level import not at top of file
30:1: I100 Imports statements are in the wrong order. import os should be before import re
30:1: E402 module level import not at top of file
31:1: E402 module level import not at top of file
32:1: E402 module level import not at top of file
33:1: E402 module level import not at top of file
35:1: E402 module level import not at top of file
36:1: E402 module level import not at top of file
38:1: I100 Imports statements are in the wrong order. from urllib should be before from zlib
38:1: E402 module level import not at top of file
39:1: E402 module level import not at top of file
41:1: E402 module level import not at top of file
42:1: E402 module level import not at top of file
43:1: I100 Imports statements are in the wrong order. from invenio.testsuite should be before from invenio.utils.json
43:1: E402 module level import not at top of file
45:1: I100 Imports statements are in the wrong order. from invenio.base.wrappers should be before from invenio.testsuite
45:1: E402 module level import not at top of file
46:1: E402 module level import not at top of file
47:1: E402 module level import not at top of file
80:17: E127 continuation line over-indented for visual indent
82:10: E261 at least two spaces before inline comment
83:13: E116 unexpected indentation (comment)
84:13: E116 unexpected indentation (comment)
85:13: E116 unexpected indentation (comment)
107:33: E127 continuation line over-indented for visual indent
118:14: E261 at least two spaces before inline comment
123:1: E302 expected 2 blank lines, found 1
130:1: E302 expected 2 blank lines, found 1
155:5: E303 too many blank lines (2)
160:1: E302 expected 2 blank lines, found 1
167:1: E302 expected 2 blank lines, found 1
202:1: E302 expected 2 blank lines, found 1
223:62: E502 the backslash is redundant between brackets
224:57: E502 the backslash is redundant between brackets
225:74: E502 the backslash is redundant between brackets
226:72: E502 the backslash is redundant between brackets
228:25: E128 continuation line under-indented for visual indent
248:13: E128 continuation line under-indented for visual indent
364:27: E261 at least two spaces before inline comment
364:28: E262 inline comment should start with '# '
403:43: E128 continuation line under-indented for visual indent
404:93: E261 at least two spaces before inline comment
439:9: E266 too many leading '#' for block comment
502:9: E266 too many leading '#' for block comment
537:9: E266 too many leading '#' for block comment
570:9: E266 too many leading '#' for block comment
574:1: E302 expected 2 blank lines, found 1
607:43: E128 continuation line under-indented for visual indent
608:93: E261 at least two spaces before inline comment
639:110: E261 at least two spaces before inline comment
656:110: E261 at least two spaces before inline comment
660:5: E303 too many blank lines (2)
685:113: E261 at least two spaces before inline comment
686:132: E261 at least two spaces before inline comment
702:113: E261 at least two spaces before inline comment
703:132: E261 at least two spaces before inline comment
766:14: E261 at least two spaces before inline comment
766:15: E262 inline comment should start with '# '
779:1: E302 expected 2 blank lines, found 1
807:29: E203 whitespace before ':'
812:22: E222 multiple spaces after operator
835:27: E203 whitespace before ':'
835:59: E203 whitespace before ':'
858:29: E222 multiple spaces after operator
875:19: E201 whitespace after '{'
875:28: E203 whitespace before ':'
877:34: E203 whitespace before ':'
879:35: E203 whitespace before ':'
899:22: E222 multiple spaces after operator
916:27: E203 whitespace before ':'
917:20: E127 continuation line over-indented for visual indent
917:34: E203 whitespace before ':'
918:35: E203 whitespace before ':'
922:9: F841 local variable '_' is assigned to but never used
939:22: E222 multiple spaces after operator
956:19: E201 whitespace after '{'
956:28: E203 whitespace before ':'
957:34: E203 whitespace before ':'
958:35: E203 whitespace before ':'
962:9: F841 local variable '_' is assigned to but never used
1010:29: E203 whitespace before ':'
1010:67: E203 whitespace before ':'
1012:33: E222 multiple spaces after operator
1027:9: E303 too many blank lines (2)
1034:87: E203 whitespace before ','
1034:65: E231 missing whitespace after ','
1034:67: E231 missing whitespace after ','
1034:69: E231 missing whitespace after ','
1045:21: E222 multiple spaces after operator
1056:33: E203 whitespace before ':'
1060:9: E303 too many blank lines (3)
1063:33: E251 unexpected spaces around keyword / parameter equals
1063:35: E251 unexpected spaces around keyword / parameter equals
1072:87: E203 whitespace before ','
1072:65: E231 missing whitespace after ','
1072:67: E231 missing whitespace after ','
1072:69: E231 missing whitespace after ','
1085:21: E222 multiple spaces after operator
1096:33: E203 whitespace before ':'
1100:33: E251 unexpected spaces around keyword / parameter equals
1100:35: E251 unexpected spaces around keyword / parameter equals
1109:67: E203 whitespace before ','
1114:1: E302 expected 2 blank lines, found 1
1117:50: E251 unexpected spaces around keyword / parameter equals
1117:52: E251 unexpected spaces around keyword / parameter equals
1127:129: E502 the backslash is redundant between brackets
1128:38: E127 continuation line over-indented for visual indent
1134:113: E502 the backslash is redundant between brackets
1135:41: E127 continuation line over-indented for visual indent
1137:126: E502 the backslash is redundant between brackets
1138:41: E127 continuation line over-indented for visual indent
1141:168: E502 the backslash is redundant between brackets
1142:42: E127 continuation line over-indented for visual indent
1143:5: E301 expected 1 blank line, found 0
1146:52: E251 unexpected spaces around keyword / parameter equals
1146:54: E251 unexpected spaces around keyword / parameter equals
1146:69: E251 unexpected spaces around keyword / parameter equals
1146:71: E251 unexpected spaces around keyword / parameter equals
1146:84: E251 unexpected spaces around keyword / parameter equals
1146:86: E251 unexpected spaces around keyword / parameter equals
1163:51: E203 whitespace before ':'
1163:66: E203 whitespace before ':'
1164:35: E203 whitespace before ':'
1164:43: E203 whitespace before ':'
1164:72: E231 missing whitespace after ':'
1164:81: E231 missing whitespace after ','
1164:83: E231 missing whitespace after ','
1171:52: E251 unexpected spaces around keyword / parameter equals
1171:54: E251 unexpected spaces around keyword / parameter equals
1171:69: E251 unexpected spaces around keyword / parameter equals
1171:71: E251 unexpected spaces around keyword / parameter equals
1171:84: E251 unexpected spaces around keyword / parameter equals
1171:86: E251 unexpected spaces around keyword / parameter equals
1181:63: E231 missing whitespace after ','
1181:65: E231 missing whitespace after ','
1229:66: E203 whitespace before ':'
1232:66: E203 whitespace before ':'
1235:66: E203 whitespace before ':'
1238:66: E203 whitespace before ':'
1240:69: E203 whitespace before ':'
1248:32: E251 unexpected spaces around keyword / parameter equals
1248:34: E251 unexpected spaces around keyword / parameter equals
1249:36: E251 unexpected spaces around keyword / parameter equals
1249:38: E251 unexpected spaces around keyword / parameter equals
1249:53: E251 unexpected spaces around keyword / parameter equals
1249:55: E251 unexpected spaces around keyword / parameter equals
1250:40: E251 unexpected spaces around keyword / parameter equals
1250:42: E251 unexpected spaces around keyword / parameter equals
1250:57: E251 unexpected spaces around keyword / parameter equals
1250:59: E251 unexpected spaces around keyword / parameter equals
1251:36: E251 unexpected spaces around keyword / parameter equals
1251:38: E251 unexpected spaces around keyword / parameter equals
1252:46: E203 whitespace before ':'
1253:48: E261 at least two spaces before inline comment
1254:46: E203 whitespace before ':'
1256:46: E203 whitespace before ':'
1257:21: E126 continuation line over-indented for hanging indent
1258:28: E126 continuation line over-indented for hanging indent
1259:46: E203 whitespace before ':'
1263:9: E301 expected 1 blank line, found 0
1273:49: E203 whitespace before ','
1274:20: E714 test for object identity should be 'is not'
1275:80: E502 the backslash is redundant between brackets
1276:42: E127 continuation line over-indented for visual indent
1285:53: E251 unexpected spaces around keyword / parameter equals
1285:55: E251 unexpected spaces around keyword / parameter equals
1285:67: E251 unexpected spaces around keyword / parameter equals
1285:69: E251 unexpected spaces around keyword / parameter equals
1286:40: E127 continuation line over-indented for visual indent
1286:64: E203 whitespace before ':'
1286:45: E251 unexpected spaces around keyword / parameter equals
1287:61: E231 missing whitespace after ':'
1287:68: E231 missing whitespace after ':'
1290:28: E251 unexpected spaces around keyword / parameter equals
1290:30: E251 unexpected spaces around keyword / parameter equals
1290:45: E251 unexpected spaces around keyword / parameter equals
1290:47: E251 unexpected spaces around keyword / parameter equals
1293:17: E126 continuation line over-indented for hanging indent
1293:34: E203 whitespace before ':'
1294:51: E231 missing whitespace after ':'
1294:58: E231 missing whitespace after ':'
1299:22: E203 whitespace before ':'
1300:32: E203 whitespace before ':'
1300:41: E203 whitespace before ':'
1301:53: E251 unexpected spaces around keyword / parameter equals
1301:55: E251 unexpected spaces around keyword / parameter equals
1301:67: E251 unexpected spaces around keyword / parameter equals
1301:69: E251 unexpected spaces around keyword / parameter equals
1302:40: E127 continuation line over-indented for visual indent
1302:45: E251 unexpected spaces around keyword / parameter equals
1305:28: E251 unexpected spaces around keyword / parameter equals
1305:30: E251 unexpected spaces around keyword / parameter equals
1305:45: E251 unexpected spaces around keyword / parameter equals
1305:47: E251 unexpected spaces around keyword / parameter equals
1310:53: E251 unexpected spaces around keyword / parameter equals
1310:55: E251 unexpected spaces around keyword / parameter equals
1310:67: E251 unexpected spaces around keyword / parameter equals
1310:69: E251 unexpected spaces around keyword / parameter equals
1311:40: E127 continuation line over-indented for visual indent
1311:60: E203 whitespace before ':'
1311:45: E251 unexpected spaces around keyword / parameter equals
1314:28: E251 unexpected spaces around keyword / parameter equals
1314:30: E251 unexpected spaces around keyword / parameter equals
1314:45: E251 unexpected spaces around keyword / parameter equals
1314:47: E251 unexpected spaces around keyword / parameter equals
1315:28: E201 whitespace after '('
1315:35: E203 whitespace before ':'
1315:39: E201 whitespace after '{'
1316:17: E128 continuation line under-indented for visual indent
1316:32: E203 whitespace before ':'
1316:41: E203 whitespace before ':'
1319:53: E251 unexpected spaces around keyword / parameter equals
1319:55: E251 unexpected spaces around keyword / parameter equals
1319:67: E251 unexpected spaces around keyword / parameter equals
1319:69: E251 unexpected spaces around keyword / parameter equals
1320:40: E127 continuation line over-indented for visual indent
1320:63: E203 whitespace before ':'
1320:45: E251 unexpected spaces around keyword / parameter equals
1323:28: E251 unexpected spaces around keyword / parameter equals
1323:30: E251 unexpected spaces around keyword / parameter equals
1323:45: E251 unexpected spaces around keyword / parameter equals
1323:47: E251 unexpected spaces around keyword / parameter equals
1324:28: E201 whitespace after '('
1324:35: E203 whitespace before ':'
1324:39: E201 whitespace after '{'
1324:78: E203 whitespace before ':'
1325:17: E128 continuation line under-indented for visual indent
1325:32: E203 whitespace before ':'
1325:41: E203 whitespace before ':'
1435:43: E128 continuation line under-indented for visual indent
1437:43: E128 continuation line under-indented for visual indent
1454:1: E302 expected 2 blank lines, found 1
1503:25: E222 multiple spaces after operator
1571:14: E222 multiple spaces after operator
1572:45: E231 missing whitespace after ','
1572:72: E231 missing whitespace after ','
1572:78: E231 missing whitespace after ','
1572:81: E231 missing whitespace after ','
1574:1: E302 expected 2 blank lines, found 1
1689:1: E302 expected 2 blank lines, found 1
1877:51: E127 continuation line over-indented for visual indent
2116:85: E502 the backslash is redundant between brackets
2117:29: E127 continuation line over-indented for visual indent
2118:85: E502 the backslash is redundant between brackets
2119:29: E127 continuation line over-indented for visual indent
2152:85: E502 the backslash is redundant between brackets
2153:29: E127 continuation line over-indented for visual indent
2154:85: E502 the backslash is redundant between brackets
2155:29: E127 continuation line over-indented for visual indent
2177:85: E502 the backslash is redundant between brackets
2178:29: E127 continuation line over-indented for visual indent
2179:85: E502 the backslash is redundant between brackets
2180:29: E127 continuation line over-indented for visual indent
2214:85: E502 the backslash is redundant between brackets
2215:29: E127 continuation line over-indented for visual indent
2216:85: E502 the backslash is redundant between brackets
2217:29: E127 continuation line over-indented for visual indent
2247:27: E222 multiple spaces after operator
2248:27: E222 multiple spaces after operator
2262:27: E222 multiple spaces after operator
2263:27: E222 multiple spaces after operator
2289:27: E222 multiple spaces after operator
2290:27: E222 multiple spaces after operator
2294:43: E128 continuation line under-indented for visual indent
2298:13: E128 continuation line under-indented for visual indent
2304:35: E222 multiple spaces after operator
2305:35: E222 multiple spaces after operator
2307:43: E128 continuation line under-indented for visual indent
2309:43: E128 continuation line under-indented for visual indent
2327:27: E222 multiple spaces after operator
2328:27: E222 multiple spaces after operator
2342:1: E302 expected 2 blank lines, found 1
2372:88: E502 the backslash is redundant between brackets
2373:29: E127 continuation line over-indented for visual indent
2374:88: E502 the backslash is redundant between brackets
2375:29: E127 continuation line over-indented for visual indent
2377:39: E203 whitespace before ':'
2390:39: E203 whitespace before ':'
2411:88: E502 the backslash is redundant between brackets
2412:29: E127 continuation line over-indented for visual indent
2413:88: E502 the backslash is redundant between brackets
2414:29: E127 continuation line over-indented for visual indent
2416:39: E203 whitespace before ':'
2438:88: E502 the backslash is redundant between brackets
2439:29: E127 continuation line over-indented for visual indent
2440:88: E502 the backslash is redundant between brackets
2441:29: E127 continuation line over-indented for visual indent
2443:39: E203 whitespace before ':'
2456:39: E203 whitespace before ':'
2478:88: E502 the backslash is redundant between brackets
2479:29: E127 continuation line over-indented for visual indent
2480:88: E502 the backslash is redundant between brackets
2481:29: E127 continuation line over-indented for visual indent
2483:39: E203 whitespace before ':'
2496:39: E203 whitespace before ':'
2513:27: E222 multiple spaces after operator
2514:27: E222 multiple spaces after operator
2528:27: E222 multiple spaces after operator
2529:27: E222 multiple spaces after operator
2555:27: E222 multiple spaces after operator
2556:27: E222 multiple spaces after operator
2560:43: E128 continuation line under-indented for visual indent
2569:35: E222 multiple spaces after operator
2570:35: E222 multiple spaces after operator
2572:43: E128 continuation line under-indented for visual indent
2574:43: E128 continuation line under-indented for visual indent
2592:27: E222 multiple spaces after operator
2593:27: E222 multiple spaces after operator
2607:1: E302 expected 2 blank lines, found 1
2635:67: E502 the backslash is redundant between brackets
2636:27: E127 continuation line over-indented for visual indent
2637:67: E502 the backslash is redundant between brackets
2638:27: E127 continuation line over-indented for visual indent
2671:67: E502 the backslash is redundant between brackets
2672:27: E127 continuation line over-indented for visual indent
2673:67: E502 the backslash is redundant between brackets
2674:27: E127 continuation line over-indented for visual indent
2696:67: E502 the backslash is redundant between brackets
2697:27: E127 continuation line over-indented for visual indent
2698:67: E502 the backslash is redundant between brackets
2699:27: E127 continuation line over-indented for visual indent
2733:67: E502 the backslash is redundant between brackets
2734:27: E127 continuation line over-indented for visual indent
2735:67: E502 the backslash is redundant between brackets
2736:27: E127 continuation line over-indented for visual indent
2763:27: E222 multiple spaces after operator
2764:27: E222 multiple spaces after operator
2778:27: E222 multiple spaces after operator
2779:27: E222 multiple spaces after operator
2801:27: E222 multiple spaces after operator
2802:27: E222 multiple spaces after operator
2815:35: E222 multiple spaces after operator
2816:35: E222 multiple spaces after operator
2818:43: E128 continuation line under-indented for visual indent
2820:43: E128 continuation line under-indented for visual indent
2833:27: E222 multiple spaces after operator
2834:27: E222 multiple spaces after operator
2846:1: E302 expected 2 blank lines, found 1
3101:27: E222 multiple spaces after operator
3102:27: E222 multiple spaces after operator
3206:43: E128 continuation line under-indented for visual indent
3208:43: E128 continuation line under-indented for visual indent
3221:27: E222 multiple spaces after operator
3222:27: E222 multiple spaces after operator
3238:43: E128 continuation line under-indented for visual indent
3240:43: E128 continuation line under-indented for visual indent
3347:1: E302 expected 2 blank lines, found 1
3392:43: E128 continuation line under-indented for visual indent
3394:43: E128 continuation line under-indented for visual indent
3404:43: E128 continuation line under-indented for visual indent
3406:43: E128 continuation line under-indented for visual indent
3408:1: E302 expected 2 blank lines, found 1
3460:43: E128 continuation line under-indented for visual indent
3462:43: E128 continuation line under-indented for visual indent
3464:43: E128 continuation line under-indented for visual indent
3466:43: E128 continuation line under-indented for visual indent
3677:1: E302 expected 2 blank lines, found 1
3758:1: E302 expected 2 blank lines, found 1
3818:16: E128 continuation line under-indented for visual indent
3818:88: E502 the backslash is redundant between brackets
3819:29: E128 continuation line under-indented for visual indent
3820:16: E128 continuation line under-indented for visual indent
3820:88: E502 the backslash is redundant between brackets
3821:29: E128 continuation line under-indented for visual indent
3822:16: E128 continuation line under-indented for visual indent
3823:16: E128 continuation line under-indented for visual indent
3824:13: E124 closing bracket does not match visual indentation
3834:1: E302 expected 2 blank lines, found 1
3895:59: E128 continuation line under-indented for visual indent
3900:43: E128 continuation line under-indented for visual indent
3902:43: E128 continuation line under-indented for visual indent
3957:59: E128 continuation line under-indented for visual indent
3962:43: E128 continuation line under-indented for visual indent
3964:43: E128 continuation line under-indented for visual indent
4027:59: E128 continuation line under-indented for visual indent
4032:43: E128 continuation line under-indented for visual indent
4034:43: E128 continuation line under-indented for visual indent
4094:13: E128 continuation line under-indented for visual indent
4095:13: E128 continuation line under-indented for visual indent
4096:13: E128 continuation line under-indented for visual indent
4097:13: E128 continuation line under-indented for visual indent
4098:13: E128 continuation line under-indented for visual indent
4107:13: E128 continuation line under-indented for visual indent
4108:13: E128 continuation line under-indented for visual indent
4109:13: E128 continuation line under-indented for visual indent
4110:13: E128 continuation line under-indented for visual indent
4111:13: E128 continuation line under-indented for visual indent
4113:16: E127 continuation line over-indented for visual indent
4115:16: E127 continuation line over-indented for visual indent
4122:59: E127 continuation line over-indented for visual indent
4128:59: E128 continuation line under-indented for visual indent
4130:59: E128 continuation line under-indented for visual indent
4138:43: E128 continuation line under-indented for visual indent
4140:43: E128 continuation line under-indented for visual indent
4145:5: E303 too many blank lines (2)
4178:5: E303 too many blank lines (2)
4246:59: E128 continuation line under-indented for visual indent
4248:59: E128 continuation line under-indented for visual indent
4253:43: E128 continuation line under-indented for visual indent
4255:43: E128 continuation line under-indented for visual indent
4260:5: E303 too many blank lines (2)
4288:13: E128 continuation line under-indented for visual indent
4289:13: E128 continuation line under-indented for visual indent
4290:13: E128 continuation line under-indented for visual indent
4291:13: E128 continuation line under-indented for visual indent
4316:13: E128 continuation line under-indented for visual indent
4317:13: E128 continuation line under-indented for visual indent
4318:13: E128 continuation line under-indented for visual indent
4319:13: E128 continuation line under-indented for visual indent
4320:13: E128 continuation line under-indented for visual indent
4331:13: E128 continuation line under-indented for visual indent
4332:13: E128 continuation line under-indented for visual indent
4333:13: E128 continuation line under-indented for visual indent
4334:13: E128 continuation line under-indented for visual indent
4335:13: E128 continuation line under-indented for visual indent
4350:59: E128 continuation line under-indented for visual indent
4352:59: E128 continuation line under-indented for visual indent
4357:43: E128 continuation line under-indented for visual indent
4359:43: E128 continuation line under-indented for visual indent
4427:59: E128 continuation line under-indented for visual indent
4429:59: E128 continuation line under-indented for visual indent
4434:43: E128 continuation line under-indented for visual indent
4436:43: E128 continuation line under-indented for visual indent
4490:16: E201 whitespace after '{'
4499:16: E201 whitespace after '{'
4503:114: E203 whitespace before ':'
4503:188: E203 whitespace before ':'
4514:114: E203 whitespace before ':'
4514:188: E203 whitespace before ':'
4514:205: E203 whitespace before ':'
4520:43: E128 continuation line under-indented for visual indent
4522:43: E128 continuation line under-indented for visual indent
4572:16: E201 whitespace after '{'
4578:16: E201 whitespace after '{'
4591:59: E128 continuation line under-indented for visual indent
4593:59: E127 continuation line over-indented for visual indent
4604:43: E128 continuation line under-indented for visual indent
4606:43: E128 continuation line under-indented for visual indent
4697:16: E201 whitespace after '{'
4707:16: E201 whitespace after '{'
4728:59: E128 continuation line under-indented for visual indent
4730:59: E128 continuation line under-indented for visual indent
4732:59: E128 continuation line under-indented for visual indent
4734:59: E128 continuation line under-indented for visual indent
4736:59: E128 continuation line under-indented for visual indent
4738:59: E127 continuation line over-indented for visual indent
4753:43: E128 continuation line under-indented for visual indent
4755:43: E128 continuation line under-indented for visual indent
4774:15: E126 continuation line over-indented for hanging indent
4795:16: E201 whitespace after '{'
4812:43: E128 continuation line under-indented for visual indent
4869:16: E201 whitespace after '{'
4876:16: E201 whitespace after '{'
4891:59: E128 continuation line under-indented for visual indent
4893:59: E127 continuation line over-indented for visual indent
4905:43: E128 continuation line under-indented for visual indent
4907:43: E128 continuation line under-indented for visual indent
4910:5: E303 too many blank lines (2)
4942:16: E201 whitespace after '{'
4975:59: E127 continuation line over-indented for visual indent
4988:43: E128 continuation line under-indented for visual indent
4990:43: E128 continuation line under-indented for visual indent
5030:16: E201 whitespace after '{'
5040:16: E201 whitespace after '{'
5053:59: E128 continuation line under-indented for visual indent
5055:59: E127 continuation line over-indented for visual indent
5066:43: E128 continuation line under-indented for visual indent
5068:43: E128 continuation line under-indented for visual indent
5077:5: E303 too many blank lines (2)
5128:16: E201 whitespace after '{'
5134:16: E201 whitespace after '{'
5150:59: E128 continuation line under-indented for visual indent
5153:59: E127 continuation line over-indented for visual indent
5165:43: E128 continuation line under-indented for visual indent
5168:43: E128 continuation line under-indented for visual indent
5218:16: E201 whitespace after '{'
5224:16: E201 whitespace after '{'
5239:59: E128 continuation line under-indented for visual indent
5242:59: E127 continuation line over-indented for visual indent
5254:43: E128 continuation line under-indented for visual indent
5256:43: E128 continuation line under-indented for visual indent
5297:16: E201 whitespace after '{'
5303:16: E201 whitespace after '{'
5318:59: E128 continuation line under-indented for visual indent
5321:59: E127 continuation line over-indented for visual indent
5333:43: E128 continuation line under-indented for visual indent
5335:43: E128 continuation line under-indented for visual indent
5340:5: E303 too many blank lines (2)
5395:16: E201 whitespace after '{'
5401:16: E201 whitespace after '{'
5416:59: E128 continuation line under-indented for visual indent
5419:59: E127 continuation line over-indented for visual indent
5431:43: E128 continuation line under-indented for visual indent
5433:43: E128 continuation line under-indented for visual indent
5494:16: E201 whitespace after '{'
5501:16: E201 whitespace after '{'
5502:99: E201 whitespace after '{'
5514:59: E128 continuation line under-indented for visual indent
5516:59: E127 continuation line over-indented for visual indent
5518:59: E127 continuation line over-indented for visual indent
5530:9: E303 too many blank lines (2)
5535:43: E128 continuation line under-indented for visual indent
5537:43: E128 continuation line under-indented for visual indent
5607:13: E128 continuation line under-indented for visual indent
5608:13: E128 continuation line under-indented for visual indent
5609:13: E128 continuation line under-indented for visual indent
5610:13: E128 continuation line under-indented for visual indent
5611:13: E128 continuation line under-indented for visual indent
5619:13: E128 continuation line under-indented for visual indent
5620:13: E128 continuation line under-indented for visual indent
5621:13: E128 continuation line under-indented for visual indent
5622:13: E128 continuation line under-indented for visual indent
5623:13: E128 continuation line under-indented for visual indent
5624:99: E201 whitespace after '{'
5636:59: E128 continuation line under-indented for visual indent
5638:59: E127 continuation line over-indented for visual indent
5640:59: E127 continuation line over-indented for visual indent
5652:9: E303 too many blank lines (2)
5657:43: E128 continuation line under-indented for visual indent
5659:43: E128 continuation line under-indented for visual indent
5672:5: E303 too many blank lines (2)
5696:13: E128 continuation line under-indented for visual indent
5697:13: E128 continuation line under-indented for visual indent
5698:13: E128 continuation line under-indented for visual indent
5699:13: E128 continuation line under-indented for visual indent
5717:13: E128 continuation line under-indented for visual indent
5718:13: E128 continuation line under-indented for visual indent
5719:13: E128 continuation line under-indented for visual indent
5720:13: E128 continuation line under-indented for visual indent
5738:14: E126 continuation line over-indented for hanging indent
5739:13: E131 continuation line unaligned for hanging indent
5758:94: E201 whitespace after '{'
5770:59: E128 continuation line under-indented for visual indent
5772:59: E127 continuation line over-indented for visual indent
5783:43: E128 continuation line under-indented for visual indent
5785:43: E128 continuation line under-indented for visual indent
5793:5: E303 too many blank lines (2)
5851:59: E128 continuation line under-indented for visual indent
5853:59: E128 continuation line under-indented for visual indent
5858:43: E128 continuation line under-indented for visual indent
5860:43: E128 continuation line under-indented for visual indent
5866:5: E303 too many blank lines (2)
5908:59: E128 continuation line under-indented for visual indent
5953:59: E128 continuation line under-indented for visual indent
5955:59: E127 continuation line over-indented for visual indent


4: L102 copyright year is outdated, expected 2015 but got 2013
24:1: F401 'socket' imported but unused
24:1: E402 module level import not at top of file
25:1: E402 module level import not at top of file
26:1: I100 Imports statements are in the wrong order. import cgi should be before import time
26:1: E402 module level import not at top of file
28:1: E402 module level import not at top of file
29:1: I101 Imported names are in the wrong order. Should be urlencode, urlopen
29:1: I100 Imports statements are in the wrong order. from urllib should be before from urlparse
29:1: E402 module level import not at top of file
31:1: E402 module level import not at top of file
32:1: I101 Imported names are in the wrong order. Should be InvenioTestCase, get_authenticated_mechanize_browser, make_test_suite, merge_error_messages, run_test_suite, test_web_page_content
32:1: E402 module level import not at top of file
33:31: E126 continuation line over-indented for hanging indent
36:1: I100 Imports statements are in the wrong order. from invenio.base.wrappers should be before from invenio.testsuite
36:1: E402 module level import not at top of file
57:71: E251 unexpected spaces around keyword / parameter equals
86:1: E302 expected 2 blank lines, found 1
98:13: E128 continuation line under-indented for visual indent
99:13: E128 continuation line under-indented for visual indent
116:1: E302 expected 2 blank lines, found 1
130:10: E261 at least two spaces before inline comment
130:11: E262 inline comment should start with '# '
162:13: F401 'load_robot_keys' imported but unused
165:13: F401 'update_robot_key' imported but unused
167:17: E116 unexpected indentation (comment)
168:13: F401 'load_robot_keys' imported but unused
271:21: E266 too many leading '#' for block comment
294:21: E266 too many leading '#' for block comment
296:21: E266 too many leading '#' for block comment
297:21: E266 too many leading '#' for block comment
301:21: E266 too many leading '#' for block comment
303:21: E266 too many leading '#' for block comment
304:21: E266 too many leading '#' for block comment
311:5: E303 too many blank lines (2)
312:33: E128 continuation line under-indented for visual indent
313:33: E128 continuation line under-indented for visual indent
314:33: E128 continuation line under-indented for visual indent
317:33: E128 continuation line under-indented for visual indent
318:33: E128 continuation line under-indented for visual indent


That is... good to be aware of.


I've been hacked returning my account back to its balance  as I been a victim of identity theft framework abused etc bahiga chahrouk


Сделайте же наконец вместо `#de-win-cfg input[type="button"] { padding: 0 2px; margin: 0 1px; height: 24px; }\`
`#de-win-cfg input[type="button"], #de-win-hid input[type="button"], #de-win-fav input[type="button"] { padding: 0 2px; margin: 0 1px; height: 24px; }\`!


wenns klappt nicht vergessen `shuf` wieder rauszunehmen, speicherplatz sparen und so ;)


Why rename? This way its obvious where it comes from.


Not used apart from deleting and storing - no way to set this field so maybe it is to be removed?


It will be called twice, but the second time the shifts will be at the beginning of the next line and thus ignored by TeX.


Neat! So herum ist es besser!


Let use old name, revert changes, and just integrate the renamed binary in manjaro-tools source, so only source patch changes.
I see no reason why we should name it systemd specific, I helps to avoid confusion I think.


@shurcooL Keep in mind that it's a guess. I mean, could be a bug in Go lib, but I haven't looked into it. For me depending on DNS lookup performance is bad anyway as the tool is not supposed to be used over the network.


Is the 21 missing? Or it was there before?


It does seem to work for me. This method is both run after each test in `ServerConnectionTest` and with the `exit` command. Under which circumstances would it raise `ConcurrentModificationException`?


lol
why


Maybe just straight macros, using `&env` to get at the analysis environment, like such:

```clojure
(defmacro macroexpand-1'
  [form]
  `(cljs.analyzer/macroexpand-1 &env ~form))

(defmacro macroexpand'
  [form]
  `(loop [form# ~form form'# (cljs.analyzer/macroexpand-1 &env ~form)]
    (if-not (identical? form# form'#)
      (recur form'# (cljs.analyzer/macroexpand-1 &env form'#))
      form'#)))
```


(͡° ͜ʖ ͡°)


good enough :)


**manjaro-tools** already will rename it to **loader.efi**. I also don't think a rename would help here. I still suggest to package it for openrc with the systemd-naming of the file and folder-structure. Why a separate package? Well, if systemd updates it, we have also to update our package. As we store it as a binary in git we might blow up our **.git** folder due this. It is not recommended to maintain binaries in git. @udeved: I'm really sorry that **gummiboot** was also taken by **systemd** and got renamed. Life goes on. As long as it works ...


`test` → `Gitter channel`


I don't think this is correct. You can include other elements than modules, too. For example content elements :)


It is still MySQL 5.0.3 I think.


Never mind, that will happen if another thread is adding a client at the same time, right?


Since the `cider-buffer-connection` variable is no longer being used, can I axe it?
Looks like it has the same effect as locally setting `cider-connections` to a single buffer.


Systemd octopus, its really really annoying.

Ok, reagrding efi binaries, why not a manjaro-tools-efi package, with uefi shells and gummiboot binary?


I meant I have patched it for 0x94 too, something like `(nv_device(parent)->chipset == 0xa0 || nv_device(parent)->chipset == 0x94)` on my local copy (http://cgit.freedesktop.org/~airlied/linux/log/?h=drm-next cloned a few days before 4.2 release).
Sure it's not all, but a little better than before:
```
$ cat /sys/class/graphics/fb0/device/pstate
0f: core 675 MHz shader 1650 MHz memory 900 MHz
AC: core 500 MHz shader 1250 MHz memory 499 MHz
```
But `675 MHz shader 1650 MHz memory 900 MHz` looks like Zotac's GF9600GT (not AMP! version) normal frequencies.
Unigine Valley Benchmark gave me ~20% fps boost, for example.

I can provide you more info/tests/debug/... for this card, if you need.


Param $object should be of a class \JSONStorage or \JSONSimpleStorage ?


Sure.

On Sunday, September 6, 2015, Artur Malabarba <notifications@github.com>
wrote:

> Since the cider-buffer-connection variable is no longer being used, can I
> axe it?
> Looks like it has the same effect as locally setting cider-connections to
> a single buffer.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/clojure-emacs/cider/commit/d29e5f1dd6cc0180b27271ee0166f5fb55a5d8a1#commitcomment-13087421>
> .
>

--
Best Regards,
Bozhidar Batsov

http://www.batsov.com


Add a line to the end of the file


All four static calls of \JSONStorage or \JSONSimpleStorage ?


Actually, I think the `\hbox{}` is unnecessary, and indeed counter productive, in this application.  It's necessary for the bolshifts, because you need to signal to TeX where to stop ignoring spaces should they occur at the beginning of a new line.  However, since these shifts occur at the end of a syllable, they should never be ignored.  Indeed, there is just one case where they need to be ignored: if we just had a manual line break.  In this instance these shifts will appear at the beginning of a line but we don't want them to have any effect.  Adding an `\hbox{}` in between would make them act like bolshifts where one has an effect and the other doesn't.  Further, this would break the bolshifts as then both would occur after an `\hbox{}` and thus have an effect.


What does this line mean?


This is misnamed, and we have perl-File-Slurp-Tiny already.


i like it!


Callbacks should have a parameter, as proposed [here](https://github.com/brutaldesign/swipebox/pull/196) for the open/close callbacks


Auras set on the event 11 are removed on evade, better use 25.


I think the idea is to move all the filter code out of mpv and implement the useful stuff in libavfilter instead.


To be clear, this function (`\gre@newlinecommon`) imposes the line breaking penalty as its last step and thus the line break occurs before TeX gets to the normal shifting code.  This is why this code is necessary here: to make sure it happens before the end of the line.  We can then rely on the fact that TeX ignores shifts at the beginning of lines until we hit the first character (the `\hbox{}` command which separates the bolshifts) to prevent the second instance of these shifts from showing up.


Fixed in new commit.


Hey @jbmartinez were the semi colons causing issues?


Yeah, it makes sense for `gocode` to use the ip rather than hostname regardless, but if it is a bug/regression in Go 1.5, that's worth resolving upstream.


WAY better, thank!


TeamCity LabkeyTrunk :: Git postgres 9.4 [Build 528](https://teamcity.labkey.org/viewLog.html?buildId=270548&buildTypeId=LabkeyTrunk_GitPostgres) outcome was **FAILURE**
Summary: Tests failed: 28, passed: 9 Build time: 00:21:14
### Failed tests
```
org.labkey.test.tests.CDSMeasureStoreTest.testDemoMeasureStore: <no details avaliable>

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

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

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

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

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

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

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

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

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

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

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


RE: `\kern` vs. `\gre@hskip`
I switched to `\gre@hskip` because `\gre@skip@syllablefinalskip` used `\gre@hskip`.  I thus assumed that this block of code might end up inside a discretionary and would need to switch back and forth.  However, a quick reread tells me that it's `\hskip` that has problems inside the discretionary, not `\kern`.  I'll change it back.


Do we have the possibility to host a source package for efi binaries?

I almost finished a package, integrated in manjaro-tools PKGBUILD... manjaro-tools-efi
manjaro-tools-iso depends on the former.


This class should be private final class


Missing Java docs


Well, it doesn't matter were we pack it. I only not recommending storing binaries in our git.


Define a Builder Class for this class and make the constructor private


Yes, I understood, hence my question, to get the binaries off git, into a hosted tar ball.


From SDK:

//
// MessageId: DBG_PRINTEXCEPTION_WIDE_C
//
// MessageText:
//
// Debugger printed exception on control C.
//
#define DBG_PRINTEXCEPTION_WIDE_C        ((NTSTATUS)0x4001000AL)    // winnt


One thing, did you test it in openrc?


I built the iso, but have got to test it yet.
efi strangely doesn't work in vbox for me, or did I miss some setting besides obvious efi checkbox?


I assume that you've tested the ROM without VoiceWakeup and it runs fine?


This attribute should be final


I was under the impression that `client.close();` removed the client from the `clients` collection, that's why I expected it. Perhaps that occasion is taken care of by the concurrent hash map though.


last time I used virtualbox + efi that was enough


Since we're modifying an existing changeset, I'm guessing that it hasn't run yet on QA?


Arggh, one moment, I got to recompile vbox host module for my kernel...


I did `forEach` on a copy anyway in the next commit.


E should be an element that implements Comparator


Java doc


Well, we can take the systemd binary package and extract there the file. Take a look at [lib32-mesa](https://github.com/manjaro/packages-multilib/blob/master/lib32-mesa/PKGBUILD).


array_merge may silently overwrite the data that is stored in this object with the data coming from relation. Is it how it supposed to be? In addition - maybe a recursive merge should be applied here. Consider that option.


jep: https://github.com/wout/svg.js#building


UGH SO GOOD.
LOVE IT.
I LOVE THIS COMMIT SO MUCH.
IT'S SO GOOD.
:fire: :heart: :+1: :banana:


This would still leave uefi shells in our source.
So I am for a uefi package.


Consider array_replace instead of array_merge. Data coming from the relation may be silently overwritten with the data stored within this object.


True. Fixed in 345d2a8, I think, by disabling this on Windows. I'm also not sure what a better binding would be.


Завтра в обед сделаю pull request, вряд ли сегодня успею

воскресенье, 6 сентября 2015 г. пользователь Andrey Urusov написал:

> Ура
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/AlexChernov/rdo_studio/commit/f1b90c3d4e2fec5203a8ca88f7bd6fa3f6cf0637#commitcomment-13087279>
> .
>


Does this really need to be `Dynamic`? :/


Or we can grab them from here at build time...
https://github.com/manjaro/manjaro-tools/blob/devel/lib/util-iso-boot.sh#L13


rm


It broke syntax highlighting. https://github.com/elixir-lang/elixir-tmbundle/pull/34#issuecomment-77144368


Ugly I think, to depend on a url to be up always.

I would just tar the 3 binaries and upload it to somewhere, so our PKGBUILD can get the tarball and make efi package.


blocking chunk generation, the config in freebuild does the tb gen stuff


Damn this line :)


Looks good


No idea. This script have been fixed and changed by random people for years, so some comments are unknown. Not all of them are correct and some may be old.


wouldn't this be `program.php`


`program.php`


Could you create other PR to revert this change?


Well if that files are not up, we cant build manjaro-tools either, all of them are in github...


размеры в dimens желательно


Can't we host them on the repo server?


``` SQL
('1863402','18634','30','5','100','7','5','18708','0','0','11','33335','10','0','0','0','0','0','0','0','0','0','Cabal Summoner - Cast Shadow Bolt on Receive AI Event.(Phase1)'),
AND
('1863902','18639','30','5','100','7','5','18708','0','0','11','33335','10','0','0','0','0','0','0','0','0','0','Cabal Spellbinder - Cast Shadow Bolt on Receive AI Event.(Phase1)'),
```
Should repeatable. On Current state cannot be inmplemented, because EVENT_T_RECEIVE_AI_EVENT not have uint32 RepeatMin, RepeatMax.
Solutions.
1) On Receive Ai Event add addtional UNIT_FLAG_IN_COMBAT,If the NPC is not in combat, it immediately happens script Reset and Event_T_RECEIVE_EVENT also be reset, which solves the problem with repeatability.
2) Write SD2 - bad idea,
3) ADD action CALL_SCRIPT_RESET)


These are not used anywhere, are they?


Hi, you need to commit the same on drupal.org repo, then only it will be listed on my page under "Projects".


When I say build time I meant when we build the package, not the iso


If I've got my maths straight, this will cause issues with file systems that doesn't support larger files.
With the worst case scenario being in 2036: `8192MB per block * 128 = 1024TB block files`.
Is this intentional, betting on people upgrading their file systems in time?
Otherwise a more conservative splitting scheme might be in order.


yeah, but that would apply to any package we build from source.


You're getting way closer.


btw, it's an error, not a line, so I don't think it should start uppercased


For this problem, you won't need instance variables. Everything can be done with local variables inside the reverse() method.


We can host those things on sourceforge.net. However we have them in a package anyway. Here a PKGBUILD I recommend. Then we have it in that package. Those other efi-files we always download on runtime should be also packaged.

```
# $Id$
# Maintainer: Philip Müller <philm_at_manjaro_dot_org>

pkgname=('openrc-loader-efi')
pkgver=225
pkgrel=1
arch=('x86_64')
url="http://www.freedesktop.org/wiki/Software/systemd"
license=('GPL2' 'LGPL2.1')
source=($pkgname-$pkgver-$pkgrel.tar.xz::http://arch.localmsp.org/arch/pool/packages/systemd-$pkgver-$pkgrel-x86_64.pkg.tar.xz)
sha256sums=('b75425b63584b1e5400556a2e60009f41ead5d35b2ed7de7bdf36ce1bb5f1b9e')

package_openrc-loader-efi() {
  pkgdesc="efi shell for openrc"
  conflicts=('systemd')

  install -Dm644 usr/lib/systemd/boot/efi/systemd-bootx64.efi ${pkgdir}/usr/lib/systemd/boot/efi/systemd-bootx64.efi
}
```
Please adopt it to a package then. How we name it, I don't care ...


TeamCity ReOpenLDAP :: devel-2.4 [Build 190](https://binbug.bigbrother-matrix.ru/teamcity/viewLog.html?buildId=443&buildTypeId=ReOpenLDAP_Devel24&guest=1) outcome was **SUCCESS**
Summary: Tests passed Build time: 01:44:11


TeamCity ReOpenLDAP :: master [Build 20](https://binbug.bigbrother-matrix.ru/teamcity/viewLog.html?buildId=444&buildTypeId=ReOpenLDAP_Master&guest=1) is now running


Nice call getting rid of the public static void main(String[] args) method.


I'm glad that you tried this direct idea.
I would never think it would go that far !

I thought the main problem of facing the e4/h4 config was the lack of space for his minor pieces.

e3/h4, e4/h4 and e3/h3 cannot be bad too !

This test shows that it could help if we add one more column to StormDanger, and one more row to ShelterWeakness


![yes yes excellent](https://cloud.githubusercontent.com/assets/1189392/9706267/64cdb15a-5495-11e5-83aa-e9fc0389d47e.jpg)


But why make it openrc specific? We would need to separate copy commands because the systemd variant, the same file, come from a different source path.
Lets just unify the path by providing the 3 binaries in a package.
This should work, assuming the systemd guys don't fiddle with the one gummiboot binary constantly.


I understand that I'm being a shitty open source community member here. But writing good bug report takes time and I decided to ignore that part. If you feel like figuring out what's wrong, do so.


Yes, my approach has been to unzip data_vis locally, point the script
there, and then run it.

On Sunday, September 6, 2015, JWMorley <notifications@github.com> wrote:

> Hey Ryan, not sure if you found an answer to this question yet. Yes, the
> recent work on complete_r_script.R was to incorporate SEUS (spring,
> summer, and fall) to OceanAdapt.
> Jim
>
>
> > add updated Data_Vis
> >
> > needed one that contained SEUS for complete_r_script.R to run properly
> > @mpinsky @JWMorley I assume this is what you guys have been doing
> locally?
> >
> > ---
> > Reply to this email directly or view it on GitHub:
> >
> https://github.com/mpinsky/OceanAdapt/commit/67bcaf8c16a75ab4c7473c4168769f73ac7f0e28
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/mpinsky/OceanAdapt/commit/67bcaf8c16a75ab4c7473c4168769f73ac7f0e28#commitcomment-13087145>
> .
>

--
Please excuse, sent from a device with tiny keys...


maybe work with the automatic variable to avoid repeating the lists of prerequisites.
why isn't there a mmix.w module?


This is intentional; file systems 20 years from now will almost certainly be able to handle petabyte files.

If they can't, the code will have to change-- but it will almost certainly change before then, anyway.

--
Gavin Andresen

> On Sep 6, 2015, at 3:43 PM, Robin van Boven <notifications@github.com> wrote:
>
> If I've got my maths straight, this will cause issues with file systems that doesn't support larger files.
> With the worst case scenario being in 2036: 8192MB per block * 128 = 1024TB block files.
> Is this intentional, betting on people upgrading their file systems in time?
> Otherwise a more conservative splitting scheme might be in order.
>
> —
> Reply to this email directly or view it on GitHub.
>


As that gives 20 years to figure out if that's too aggressive, I think
by then a new version will be out that could adjust the max size.  Of
course we all may either be using alien technology or be back to the
stoneage by then.  20 years is a long time in tech.

On 09/06/2015 12:43 PM, Robin van Boven wrote:
>
> If I've got my maths straight, this will cause issues with file
> systems that doesn't support larger files.
> With the worst case scenario being in 2036: |8192MB per block * 128 =
> 1024TB block files|.
> Is this intentional, betting on people upgrading their file systems in
> time?
> Otherwise a more conservative splitting scheme might be in order.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/bitcoinxt/bitcoinxt/commit/946e3ba8c7806a66c2b834d3817ff0c986c0811b#commitcomment-13087566>.
>

--
Jerry Durand, Durand Interstellar, Inc.  www.interstellar.com
tel: +1 408 356-3886, USA toll free: 1 866 356-3886
Skype:  jerrydurand


@ranma Do we have to add gbhw_setiocallback to libgbs.def, too?


This one is kind of sketchy to me because you have both local data for a given ID and a relational data under possibly different Foreign ID. To me a field should either has its local data or relational data - not both at once.


No worries, I wasn't trying to guilt trip you into spending time and resolving this issue upstream. I just meant it'd be nice. I'm also busy and probably don't have the bandwidth to do this.

Also, I don't have Windows readily accessible and can't test it easily. I'm sure someone else out there cares about Windows more and would want to step up. :) This repo has 169 watchers so fingers crossed. (Also, it might turn out this is already a reported/known issue.)


@chaffeqa no problem, more to come.


Часто наблюдал, как `Избранное` открывается с глюком - на долю секунды появляется пустое маленькое окно без содержимого, а только потом уже нормальное. Думаю, избавился от этого.


Would it be useful if you could ignore whole directories in XO?

```
"test/fixtures",
"examples"
```


Почему добавили пол? Быстро Убрать!


I admit I don't understand your first comment... especially "since these shifts occur at the end of a syllable, they should never be ignored" -> why?

But maybe you refer to the normal shift at the end of syllable? I admit I didn't take them into account... The first idea I have to deal with them is to transfort the algorithm in the following:

- \kern -\eolshift
- \grenobreak (not ignored if break at end of syllable)
- \hbox{}
- \gre@hskip \eolshift+\thenormalskipatendofsyllable (ignored if break at end of syllable, if not we get a normal space)
- \grepenalty -\therelevantvalue

What do you think?


done already


add-ing


Don't know. What are your suggestions?


Why not just remove this instead of leaving it commented out?
We have version control.


There should be a `P_smoov[:,:,n] = P[:,:,n]` here as well, I think.


mmm magic numbers


あ、失礼しました…。検討する的な意味合いだとすると Study of unit testing components とかそういう感じですかねー。


This line should include`P[:, :, 1] + J`, not `P[:, :, 1] * J`


mmm memory leaks


Didn't you already set this to true in line 239?


The last part of this line should just be `P_smoov`, not `P_smoov[:,:,end]`


develop (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)


帅


没有，抱歉


It is as you said. I'm using a version older than 3.874.
`Verilator 3.872 2015-04-05 rev verilator_3_870-14-g793c974`

I will try to update it and see if the errors go off.


Where is the brew files located?


I suggest to use C++ 11 smart pointer rather than the raw delete operators.


FYI, this broke backwards compatibility.


Remove these two methods is not safe, will it affect `(CC_USE_3D_PHYSICS && CC_ENABLE_BULLET_INTEGRATION)` ?


Still need to:
* add button on Category page to go back to home page
* look up and display field definition for each field on the Category page
* web_spec tests for the revised home page and for the new category page


Does every scene should own a PhysicsManager or just a PhysicWorld?


shouldn't this be #ifdef


Okay, changed to signed tinyint.


10~11行目まで
app.rbで既にrequireされているので，ここでrequireしなくても動く


固定値は定数にしておくほうが良いと思う


don't need name or user_id


TeamCity ReOpenLDAP :: devel-2.4 [Build 188](https://binbug.bigbrother-matrix.ru/teamcity/viewLog.html?buildId=420&buildTypeId=ReOpenLDAP_Devel24&guest=1) outcome was **SUCCESS**
Summary: Tests passed Build time: 01:45:07


`params = { 'keyid' => @keyid, 'freeword' => freeword, 'format' => @format }`

個人的にはkey => valueはシンボルを使うのが好みなんですがどうでしょう！？

`params = { keyid: @keyid, freeword: freeword, format: @format }`


同上

`{:params => params}`

`{params: params}`


testing comment


nice


OK. No error for version 3.876.


Which files are you looking for?


This will basically be reverted, since this query is only for the title. Here's where the money is:
https://github.com/ensoftek/openemr/blob/db115ce8cbe57c06f50546b2d99cf33b91bf31bb/interface/super/rules/library/RuleManager.php#L432


You are every where @Jan-E :)

Thanks for this! So I don't know the *right* way to solve this issue (I used a C feature that isn't supported by some compilers) so need to rethink that code.

Thanks for helping out, I will be banging on this branch for a couple hours tonight and hopefully have all this cleaned up


yep, revert this. The cr.* in the select should bring in your new columns


revert


thanks!!!


OK. Verilator 3.872 can build it.


そう書けるのですね！修正します！


any more you want to point out please fill free to do so I insist it really won't hurt my feelings in the least 8^)
      From: Brady Miller <notifications@github.com>
 To: ensoftek/openemr <openemr@noreply.github.com>
Cc: teryhill <teryhill@yahoo.com>
 Sent: Saturday, September 5, 2015 10:35 PM
 Subject: Re: [openemr] ensoftek_mu2_170.314.a8: Clinical Decision Support (db115ce)

This will basically be reverted, since this query is only for the title. Here's where the money is:
https://github.com/ensoftek/openemr/blob/db115ce8cbe57c06f50546b2d99cf33b91bf31bb/interface/super/rules/library/RuleManager.php#L432—
Reply to this email directly or view it on GitHub.


The problem is that addslashes() is not escaping the html. If the vulnerability is saying the $d is not being escaped, then need to dig deeper in the code where the $d variable is being built and then escape the variables there. Here's the function that's needs to be converted (this will be a good exercise on converting a block of code):
https://github.com/robertogagliotta/openemr/blob/2afd854f628836db2ebcc3ede7eec507e5c719a5/controllers/C_Prescription.class.php#L477-L500


i hate to say this @h2o64 seems this OC means nothing, used several bench-marking apps, all end points show same result whether with OC or Stock clock.


Please don't close the program from random places. This makes it hard to properly tear down everything.

Replaced by
```
ret = -1;
goto end;
```


Same here.


As far as I understand, the first sorting place endpoints with hardcoded uri before the parametrized endpoints.
The second sorting, sort all endpoints in a lexicographically way for basically place the hardcoded endpoints in order.

http://www.quickmeme.com/img/14/140b5483695386641c948708752a0663ef0e2f500d6cdab6175c881d626a5a60.jpg


yay, finally... thought it would never compatible with pi 2 because lack of peripheral docs


Rubyは一文字目を大文字で書くと定数になるので，constはいらないかと！


well actually it seems that it is based on song timings:
```
53130,-117.647058823529,4,2,2,70,0,0
53797,-100,4,1,1,70,0,1
```
The last value is for Kiai timers i think
I will check the wikis for more info (hopefully they have the infos we need)


so they are both based on 0.2.97.30 or has my documentation been mixed up the whole time and really the first lr-fba we had was based on 0.2.97.24 rather than 0.2.97.30?


102687702-Schedule-Unit-Tests (jasondegraw) - Win64-Windows-7-VisualStudio-12: Tests Failed

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


Was it intended for this to be making the `$userdata` parameter required?


jsonもapp.rbで`sinatra/json`がロードされているので必要ないかと!


If I remember correctly the signature changed from "fz" (callback and user data required) to callback, timeout, user_data


@poettering , I suppose that the `patterns` array contain very few elements (typically one): `systemd-analyze dot '*.service'`. Am I wrong?


Perfect use of Optional with functional style

![image](https://cloud.githubusercontent.com/assets/9658700/9702204/fc9756fe-5453-11e5-87a1-bffa5003a90f.png)