IMHO it is certainly prudent to switch to a minimum of java 7, but we should also all be aware that Oracle stopped making public updates to java 7 as of April 2015. See http://www.oracle.com/technetwork/java/eol-135779.html


done https://github.com/SpacePossum/PHP-CS-Fixer/commit/5e5f095c5e421287996a4737e6c8fae0559ae2d8


OK, I don't have a problem with this


In theory the factory should have the minimal passable object by validation, so the rest of the params is handled in `lets`.It's briefly mentioned in this railscast: http://railscasts.com/episodes/158-factories-not-fixtures. I would find an article where the rule is explained but I can't remember in which one it was :)


seems like it does not work, test run exceeds 50 minutes.
https://travis-ci.org/tdhock/animint/builds/78456282#L1872

I am inclined to re-disable the shiny tests on travis. What do you think?

On Wed, Sep 2, 2015 at 3:19 PM, Carson <notifications@github.com> wrote:

> @tdhock <https://github.com/tdhock> nice! Maybe we should remove the if
> (Sys.getenv("TRAVIS") == "true") { bit now?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/tdhock/animint/commit/ef0292a7807b1824721a06f7801d48eff6cbc3f5#commitcomment-13031537>
> .
>


r+, good catch!

BTW: what is "SC"?


Answer to [this comment](https://github.com/haf/suave-presentation.2015-09-03/commit/037422a38b4d528b1e5e7acb7319809ed9edf028#commitcomment-13043991) by @VesaKarvonen – this still responds with all previously seen values; is it because there exists some other stream that has called `tap`? Should I pipe this to `Stream.values` and await on the Alt instead?


just as a hint maybe for proper prenthesis `(!arc.electrodes[i])?("electrode"+(i+1)):("");` as you want to encapsule every "atmoic" item, the "!" at the beginning will still be recognized as part of the condition, but who knows, it's more readable imho and i do not want to start a shitstorm about good coding style but when you use parentheses, use them more precisely :)

PS: same goes for line 53 and several other Cond ? True : False construct you used, i just wanted to notice


https://github.com/html5lib/html5lib-tests/issues/54#issuecomment-74119067 is the important part of that thread (nostrademons' comment on Feb 12).

As far as I'm aware, nothing was ever *removed* from the WHATWG spec — it was simply never added to it. Essentially you want to implement the WHATWG spec but with the addition of Ruby stuff from the W3C spec — which is what ever browser implements and is what html5lib/html5lib-tests targets.


Fixes #993


Yes, this is just throwaway `val` from [here](https://github.com/kernc/orange3/commit/f6e5ad69918427d78ebe20cc8deb8b224e6dd55a#diff-8fc32ad6a8ac706482fe82637339979aR41), so that the final `isinstance()` call below passes.
But again, see the commit following this one as it is much clearer, I think. If all will prove fine eventually, I'd most like to squash these two commits.


Whoops; i thought they were only a temporary thing to test the server while developing the code. Anyway, i didn't use them, so they also probably needs to be updated in order to work. Having some automated testng would be cool!


Typo


Looks good


1: M111 unrecognized component name: babel


23:1: I201 Missing newline before sections or imports.
24:1: I201 Missing newline before sections or imports.
26:1: I100 Imports statements are in the wrong order. from babel should be before import six
27:1: I100 Imports statements are in the wrong order. from contextlib should be before from babel
27:1: I201 Missing newline before sections or imports.
28:1: I101 Imported names are in the wrong order. Should be _request_ctx_stack, current_app, g
28:1: I201 Missing newline before sections or imports.
29:1: I201 Missing newline before sections or imports.
32:1: I201 Missing newline before sections or imports.
33:1: I100 Imports statements are in the wrong order. from .errors should be before from .selectors
90:5: E266 too many leading '#' for block comment


Ruby developers would have extracted this piece to an external micro service :)


Fair enough.


Hy,

and some strings are not availabe at companion at all languages
At Heli menü  you see allways only Long cyc and Later cycl. there at all languaes


r+

this is a vestige of code that was used to test ECCs after all ciphersuites were detected, now we test for curves with every ciphersuite so it's not necessary


The #ifdefs are a little bit invasive, but we are on the right track.
I'll think if we can reduce a bit the number of #ifdefs and get back to you.


That is just great. Thank you very much. I'll add this tomorrow, unless you can make a pull-request for it sooner ;-)


the addition is redundant because of the check before


add underscore (_) before the date in filename


@mondain That problem is only against which JDK version the library can compile. But yeah, would be nice if we could go to 1.8 directly. See the comments further above...


This test has been removed: https://github.com/JetBrains/kotlin/commit/86b89ca06c9c7de24f52b1ea20c6ad3c1c506a26


If `save_after` was a variant with meaningful values, or maybe just a labelled parameter, it would be easier to see what a call to `access_table` is doing.


1: M111 unrecognized component name: manage


This means that those strings are not wrapped with a `tr()` function which provides translations. I bet there are many more strings like that.


What is the story with this?


@edmistj Shouldn't that be "led by"?


My next action after finishing my existing PR is to get cmake set up to produce a `make test` and launch googletest, and one simple test case just instantiating a class.


I think so, let me read up on the specifics.


Error message should be `argument provided to order() must either be a Hash, an Array, a Symbol or a String` -- forgot to add the Hash case after implementing it.. sorry


Extra whitespace after table (same below)


Ah, I missed the fact keyword highlighting is generated automatically, good to know. Regarding the arguments: arguments are highlighted as strings in current plugin managers because** that is what they are**: VimL strings that are `eval`ed into something else. Arguments for a first class Vim command are something else entirely; they should be highlighted as command arguments, like other Ex commands, unless one wants to break the semantics of syntax highlighting in VimL.


We don't want to write copyright?


Nah, screw that, I'm fixing it up. Please see revised.


I'm not sure whether this was such a good idea.

This will always throw when an actors meets all these conditions
 - has `BodyOrientation` (obviously), yet
 - has no sprite body
 - has no `QuantizeFacingsFromSequence`
 - has no custom `QuantizedFacings`

But `BodyOrientation` on its own wouldn't do any harm if it wasn't for this throw, so I think this is a bit harsh. In my opinion, if the above conditions are all met, it should simply do nothing, like it used to.

Alternatively, we should update this throw message to account for the possibility that this trait should rather be removed if the actor has no render traits.


my next test was removing these from the manifest, to see if they'd still work internally.


@otaviobp do you mean to use ```@c value and @c ping``` instead? I meant to mention the argument anyways.


I'm now thinking *transformers* are no more an appropriate name; how about *processors*?


Still INSTALL_FAILED_CONFLICTING_PROVIDER. Looking at it.


What is the interest to have a null value for 'logcount' ?


Run `$ cd X` to switch to your project directory and continue working there. Once in the project root, you can run `$ appbuilder add-view` or `$ appbuilder add-dataprovider`.

(Is there a way to get the project name :D Also, this is applicable to `create|*default` as well. =)


fixes #1


I think you should remove the #define's too as that was one of the reasons for using #pragma once to avoid unnecessary #defines.


 #[zstack Test Bot Report] P A S S
 Integration Test Result:
Test Summary:

 TestSuite|TestCase | Pass | Fail | Timeout | Skip
 ---------|---------| ---- | ---- | ------- | ----
 basic_test|__suite_setup__|0|1|0|0
basic_test|_basic/test_create_vm_|0|0|0|1
basic_test|_basic/test_stop_vm_|0|0|0|1
basic_test|_basic/test_start_vm_|0|0|0|1
basic_test|_basic/test_reboot_vm_|0|0|0|1
basic_test|_basic/test_add_volume_|0|0|0|1
basic_test|_basic/test_add_vol_to_stopvm_|0|0|0|1
basic_test|_basic/test_add_volume_reboot_vm_|0|0|0|1
basic_test|_basic/test_add_multi_volumes_|0|0|0|1
basic_test|_basic/test_add_volume_negative_|0|0|0|1
basic_test|_basic/test_crt_temp_from_volume_|0|0|0|1
basic_test|_basic/test_crt_vm_with_volume_|0|0|0|1
basic_test|_basic/test_vm_securitygroup_|0|0|0|1
basic_test|_basic/test_create_iso_vm_|0|0|0|1
basic_test|_account/test_crt_vm_by_normal_account_|0|0|0|1
basic_test|_account/test_crt_vm_by_normal_account2_|0|0|0|1
basic_test|_account/test_vm_ops_by_normal_account_|0|0|0|1
basic_test|_account/test_multi_accounts_vm_ops_|0|0|0|1
basic_test|_suite_teardown_|0|0|0|1
virtual_router_test|__suite_setup__|0|1|0|0
virtual_router_test|_host/test_reconnect_host_|0|0|0|1
virtual_router_test|_account/test_vm_ops_by_normal_account_|0|0|0|1
virtual_router_test|_account/test_multi_accounts_vm_ops_|0|0|0|1
virtual_router_test|_novlan/test_create_vm_|0|0|0|1
virtual_router_test|_novlan/test_reboot_vm_|0|0|0|1
virtual_router_test|_novlan/test_ping_vms_|0|0|0|1
virtual_router_test|_host/test_reconnect_host_|0|0|0|1
virtual_router_test|_vlan/test_create_vm_|0|0|0|1
virtual_router_test|_vlan/test_reboot_vm_|0|0|0|1
virtual_router_test|_vlan/test_snat_create_|0|0|0|1
virtual_router_test|_vlan/test_dnat_reboot_|0|0|0|1
virtual_router_test|_vlan/test_ping_vms_|0|0|0|1
virtual_router_test|_vlan/test_create_3vms_|0|0|0|1
virtual_router_test|_vlan/test_start_vm_|0|0|0|1
virtual_router_test|_vlan/test_3l3s_vm_|0|0|0|1
virtual_router_test|_vlan/test_remove_dhcp_|0|0|0|1
virtual_router_test|_vlan/test_2l3_vm_|0|0|0|1
virtual_router_test|_vlan/test_crt_vms_with_limited_ips_|0|0|0|1
virtual_router_test|_vlan/test_crt_vms_with_limited_ips2.0_|0|0|0|1
virtual_router_test|_vlan/test_crt_vms_with_limited_ips2.1_|0|0|0|1
virtual_router_test|_vlan/test_start_vms_simultaneously_|0|0|0|1
virtual_router_test|_vlan/test_crt_static_ip_vm_|0|0|0|1
virtual_router_test|_vlan/test_crt_vm_with_hostname_|0|0|0|1
virtual_router_test|_vlan/test_attach_nic_|0|0|0|1
virtual_router_test|_vlan/test_attach_nic_stopped_vm_|0|0|0|1
virtual_router_test|_vlan/test_attach_nic_reboot_vm_|0|0|0|1
virtual_router_test|_vlan/test_chg_static_ip_vm_|0|0|0|1
virtual_router_test|_vlan/test_attach_nic_with_static_ip_|0|0|0|1
virtual_router_test|_volume/test_add_volume_|0|0|0|1
virtual_router_test|_volume/test_add_m_vols_|0|0|0|1
virtual_router_test|_volume/test_add_volume_vr_|0|0|0|1
virtual_router_test|_volume/test_crt_vm_volume_|0|0|0|1
virtual_router_test|_volume/test_crt_vm_2_volumes_|0|0|0|1
virtual_router_test|_volume/test_crt_vm_24_volumes_|0|0|0|1
virtual_router_test|_volume/test_volume_ops_on_stopped_vm_|0|0|0|1
virtual_router_test|_volume/test_crt_vm_from_dvt_|0|0|0|1
virtual_router_test|_template_image/test_crt_temp_image_|0|0|0|1
virtual_router_test|_template_image/test_del_temp_image_|0|0|0|1
virtual_router_test|_sg/test_ingress_|0|0|0|1
virtual_router_test|_sg/test_egress_|0|0|0|1
virtual_router_test|_sg/test_icmp_|0|0|0|1
virtual_router_test|_sg/test_udp_|0|0|0|1
virtual_router_test|_sg/test_stopped_vm_|0|0|0|1
virtual_router_test|_sg/test_vm_ops_|0|0|0|1
virtual_router_test|_sg/test_2vm_egress_|0|0|0|1
virtual_router_test|_sg/test_2vm_ingress_|0|0|0|1
virtual_router_test|_sg/test_4vm_complx_|0|0|0|1
virtual_router_test|_sg/test_detach_l3_|0|0|0|1
virtual_router_test|_pf/test_2l3s_pfs_|0|0|0|1
virtual_router_test|_pf/test_attach_pf_|0|0|0|1
virtual_router_test|_pf/test_delete_pf_after_destroy_vm_|0|0|0|1
virtual_router_test|_pf/test_del_vip_before_add_pf_to_vm_|0|0|0|1
virtual_router_test|_pf/test_multi_pfs_sg_tcp_|0|0|0|1
virtual_router_test|_pf/test_multi_rules_|0|0|0|1
virtual_router_test|_pf/test_pf_after_destroy_vm_|0|0|0|1
virtual_router_test|_pf/test_pf_sg_tcp_|0|0|0|1
virtual_router_test|_pf/test_pfs_tcp_udp_same_vip_ports_|0|0|0|1
virtual_router_test|_pf/test_pfs_tcp_with_same_vip_|0|0|0|1
virtual_router_test|_pf/test_tcp_|0|0|0|1
virtual_router_test|_pf/test_udp_|0|0|0|1
virtual_router_test|_pf/test_vm_ops_|0|0|0|1
virtual_router_test|_eip/test_2_eips_|0|0|0|1
virtual_router_test|_eip/test_2l3s_eip_pf_|0|0|0|1
virtual_router_test|_eip/test_2l3s_eips_|0|0|0|1
virtual_router_test|_eip/test_attach_eip_|0|0|0|1
virtual_router_test|_eip/test_create_eip_vm_|0|0|0|1
virtual_router_test|_eip/test_del_vip_before_add_eip_to_vm_|0|0|0|1
virtual_router_test|_eip/test_eip_sg_tcp_|0|0|0|1
virtual_router_test|_eip/test_pf_eip_attach_|0|0|0|1
virtual_router_test|_eip/test_vm_ops_|0|0|0|1
virtual_router_test|_eip/test_vm_ops2_|0|0|0|1
virtual_router_test|_lb/test_create_lb_alone_vr_|0|0|0|1
virtual_router_test|_lb/test_create_lb_source_|0|0|0|1
virtual_router_test|_lb/test_create_lb_|0|0|0|1
virtual_router_test|_lb/test_lb_health_check_|0|0|0|1
virtual_router_test|_snapshot/test_create_snapshot_|0|0|0|1
virtual_router_test|_snapshot/test_create_sp_after_delete_|0|0|0|1
virtual_router_test|_snapshot/test_create_image_by_snapshot_|0|0|0|1
virtual_router_test|_snapshot/test_crt_sp_for_both_root_..._|0|0|0|1
virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm2_|0|0|0|1
virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm3_|0|0|0|1
virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm_|0|0|0|1
virtual_router_test|_snapshot/test_delete_snapshot_on_ru..._|0|0|0|1
virtual_router_test|_snapshot/test_crt_sp_in_live_vm_|0|0|0|1
virtual_router_test|_snapshot/test_crt_sp_from_vol_crt_f..._|0|0|0|1
virtual_router_test|_snapshot/test_change_max_sp_depth_l..._|0|0|0|1
virtual_router_test|_regression/delete_sg_with_2_attache..._|0|0|0|1
virtual_router_test|_regression/rm_nic_sg_on_stopped_vm_|0|0|0|1
virtual_router_test|_regression/test_data_volume_with_vm..._|0|0|0|1
virtual_router_test|_vr/test_ping_vms_reboot_vr_|0|0|0|1
virtual_router_test|_vr/test_reconnect_vr_|0|0|0|1
virtual_router_test|_vr/test_start_vrs_simultaneously_|0|0|0|1
virtual_router_test|_host/test_reconnect_host_|0|0|0|1
virtual_router_test|_suite_teardown_|0|0|0|1
local_ps_virtual_router_test|__suite_setup__|0|1|0|0
local_ps_virtual_router_test|_host/test_reconnect_host_|0|0|0|1
local_ps_virtual_router_test|_account/test_vm_ops_by_normal_account_|0|0|0|1
local_ps_virtual_router_test|_account/test_multi_accounts_vm_ops_|0|0|0|1
local_ps_virtual_router_test|_novlan/test_create_vm_|0|0|0|1
local_ps_virtual_router_test|_novlan/test_reboot_vm_|0|0|0|1
local_ps_virtual_router_test|_novlan/test_ping_vms_|0|0|0|1
local_ps_virtual_router_test|_host/test_reconnect_host_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_create_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_reboot_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_snat_create_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_dnat_reboot_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_ping_vms_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_create_3vms_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_start_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_3l3s_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_remove_dhcp_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_2l3_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_crt_vms_with_limited_ips_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_crt_vms_with_limited_ips2.0_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_crt_vms_with_limited_ips2.1_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_start_vms_simultaneously_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_crt_static_ip_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_crt_vm_with_hostname_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_attach_nic_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_attach_nic_stopped_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_attach_nic_reboot_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_chg_static_ip_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_attach_nic_with_static_ip_|0|0|0|1
local_ps_virtual_router_test|_volume/test_add_volume_|0|0|0|1
local_ps_virtual_router_test|_volume/test_add_m_vols_|0|0|0|1
local_ps_virtual_router_test|_volume/test_add_volume_vr_|0|0|0|1
local_ps_virtual_router_test|_volume/test_crt_vm_volume_|0|0|0|1
local_ps_virtual_router_test|_volume/test_crt_vm_2_volumes_|0|0|0|1
local_ps_virtual_router_test|_volume/test_crt_vm_24_volumes_|0|0|0|1
local_ps_virtual_router_test|_volume/test_volume_ops_on_stopped_vm_|0|0|0|1
local_ps_virtual_router_test|_volume/test_crt_vm_from_dvt_|0|0|0|1
local_ps_virtual_router_test|_template_image/test_crt_temp_image_|0|0|0|1
local_ps_virtual_router_test|_template_image/test_del_temp_image_|0|0|0|1
local_ps_virtual_router_test|_sg/test_ingress_|0|0|0|1
local_ps_virtual_router_test|_sg/test_egress_|0|0|0|1
local_ps_virtual_router_test|_sg/test_icmp_|0|0|0|1
local_ps_virtual_router_test|_sg/test_udp_|0|0|0|1
local_ps_virtual_router_test|_sg/test_stopped_vm_|0|0|0|1
local_ps_virtual_router_test|_sg/test_vm_ops_|0|0|0|1
local_ps_virtual_router_test|_sg/test_2vm_egress_|0|0|0|1
local_ps_virtual_router_test|_sg/test_2vm_ingress_|0|0|0|1
local_ps_virtual_router_test|_sg/test_4vm_complx_|0|0|0|1
local_ps_virtual_router_test|_sg/test_detach_l3_|0|0|0|1
local_ps_virtual_router_test|_pf/test_2l3s_pfs_|0|0|0|1
local_ps_virtual_router_test|_pf/test_attach_pf_|0|0|0|1
local_ps_virtual_router_test|_pf/test_delete_pf_after_destroy_vm_|0|0|0|1
local_ps_virtual_router_test|_pf/test_del_vip_before_add_pf_to_vm_|0|0|0|1
local_ps_virtual_router_test|_pf/test_multi_pfs_sg_tcp_|0|0|0|1
local_ps_virtual_router_test|_pf/test_multi_rules_|0|0|0|1
local_ps_virtual_router_test|_pf/test_pf_after_destroy_vm_|0|0|0|1
local_ps_virtual_router_test|_pf/test_pf_sg_tcp_|0|0|0|1
local_ps_virtual_router_test|_pf/test_pfs_tcp_udp_same_vip_ports_|0|0|0|1
local_ps_virtual_router_test|_pf/test_pfs_tcp_with_same_vip_|0|0|0|1
local_ps_virtual_router_test|_pf/test_tcp_|0|0|0|1
local_ps_virtual_router_test|_pf/test_udp_|0|0|0|1
local_ps_virtual_router_test|_pf/test_vm_ops_|0|0|0|1
local_ps_virtual_router_test|_eip/test_2_eips_|0|0|0|1
local_ps_virtual_router_test|_eip/test_2l3s_eip_pf_|0|0|0|1
local_ps_virtual_router_test|_eip/test_2l3s_eips_|0|0|0|1
local_ps_virtual_router_test|_eip/test_attach_eip_|0|0|0|1
local_ps_virtual_router_test|_eip/test_create_eip_vm_|0|0|0|1
local_ps_virtual_router_test|_eip/test_del_vip_before_add_eip_to_vm_|0|0|0|1
local_ps_virtual_router_test|_eip/test_eip_sg_tcp_|0|0|0|1
local_ps_virtual_router_test|_eip/test_pf_eip_attach_|0|0|0|1
local_ps_virtual_router_test|_eip/test_vm_ops_|0|0|0|1
local_ps_virtual_router_test|_eip/test_vm_ops2_|0|0|0|1
local_ps_virtual_router_test|_lb/test_create_lb_alone_vr_|0|0|0|1
local_ps_virtual_router_test|_lb/test_create_lb_source_|0|0|0|1
local_ps_virtual_router_test|_lb/test_create_lb_|0|0|0|1
local_ps_virtual_router_test|_lb/test_lb_health_check_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_create_snapshot_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_create_sp_after_delete_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_create_image_by_snapshot_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_crt_sp_for_both_root_..._|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm2_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm3_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_delete_snapshot_on_ru..._|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_crt_sp_in_live_vm_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_crt_sp_from_vol_crt_f..._|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_change_max_sp_depth_l..._|0|0|0|1
local_ps_virtual_router_test|_regression/delete_sg_with_2_attache..._|0|0|0|1
local_ps_virtual_router_test|_regression/rm_nic_sg_on_stopped_vm_|0|0|0|1
local_ps_virtual_router_test|_regression/test_data_volume_with_vm..._|0|0|0|1
local_ps_virtual_router_test|_vr/test_ping_vms_reboot_vr_|0|0|0|1
local_ps_virtual_router_test|_vr/test_reconnect_vr_|0|0|0|1
local_ps_virtual_router_test|_vr/test_start_vrs_simultaneously_|0|0|0|1
local_ps_virtual_router_test|_host/test_reconnect_host_|0|0|0|1
local_ps_virtual_router_test|_suite_teardown_|0|0|0|1
local_nfs_virtual_router_test|__suite_setup__|0|1|0|0
local_nfs_virtual_router_test|_host/test_reconnect_host_|0|0|0|1
local_nfs_virtual_router_test|_account/test_vm_ops_by_normal_account_|0|0|0|1
local_nfs_virtual_router_test|_account/test_multi_accounts_vm_ops_|0|0|0|1
local_nfs_virtual_router_test|_novlan/test_create_vm_|0|0|0|1
local_nfs_virtual_router_test|_novlan/test_reboot_vm_|0|0|0|1
local_nfs_virtual_router_test|_novlan/test_ping_vms_|0|0|0|1
local_nfs_virtual_router_test|_host/test_reconnect_host_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_create_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_reboot_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_snat_create_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_dnat_reboot_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_ping_vms_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_create_3vms_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_start_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_3l3s_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_remove_dhcp_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_2l3_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_crt_vms_with_limited_ips_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_crt_vms_with_limited_ips2.0_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_crt_vms_with_limited_ips2.1_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_start_vms_simultaneously_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_crt_static_ip_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_crt_vm_with_hostname_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_attach_nic_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_attach_nic_stopped_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_attach_nic_reboot_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_chg_static_ip_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_attach_nic_with_static_ip_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_add_volume_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_add_m_vols_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_add_volume_vr_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_crt_vm_volume_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_crt_vm_2_volumes_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_crt_vm_24_volumes_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_volume_ops_on_stopped_vm_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_crt_vm_from_dvt_|0|0|0|1
local_nfs_virtual_router_test|_template_image/test_crt_temp_image_|0|0|0|1
local_nfs_virtual_router_test|_template_image/test_del_temp_image_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_ingress_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_egress_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_icmp_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_udp_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_stopped_vm_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_vm_ops_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_2vm_egress_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_2vm_ingress_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_4vm_complx_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_detach_l3_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_2l3s_pfs_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_attach_pf_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_delete_pf_after_destroy_vm_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_del_vip_before_add_pf_to_vm_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_multi_pfs_sg_tcp_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_multi_rules_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_pf_after_destroy_vm_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_pf_sg_tcp_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_pfs_tcp_udp_same_vip_ports_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_pfs_tcp_with_same_vip_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_tcp_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_udp_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_vm_ops_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_2_eips_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_2l3s_eip_pf_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_2l3s_eips_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_attach_eip_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_create_eip_vm_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_del_vip_before_add_eip_to_vm_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_eip_sg_tcp_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_pf_eip_attach_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_vm_ops_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_vm_ops2_|0|0|0|1
local_nfs_virtual_router_test|_lb/test_create_lb_alone_vr_|0|0|0|1
local_nfs_virtual_router_test|_lb/test_create_lb_source_|0|0|0|1
local_nfs_virtual_router_test|_lb/test_create_lb_|0|0|0|1
local_nfs_virtual_router_test|_lb/test_lb_health_check_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_create_snapshot_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_create_sp_after_delete_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_create_image_by_snapshot_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_crt_sp_for_both_root_..._|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm2_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm3_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_delete_snapshot_on_ru..._|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_crt_sp_in_live_vm_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_crt_sp_from_vol_crt_f..._|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_change_max_sp_depth_l..._|0|0|0|1
local_nfs_virtual_router_test|_regression/delete_sg_with_2_attache..._|0|0|0|1
local_nfs_virtual_router_test|_regression/rm_nic_sg_on_stopped_vm_|0|0|0|1
local_nfs_virtual_router_test|_regression/test_data_volume_with_vm..._|0|0|0|1
local_nfs_virtual_router_test|_vr/test_ping_vms_reboot_vr_|0|0|0|1
local_nfs_virtual_router_test|_vr/test_reconnect_vr_|0|0|0|1
local_nfs_virtual_router_test|_vr/test_start_vrs_simultaneously_|0|0|0|1
local_nfs_virtual_router_test|_host/test_reconnect_host_|0|0|0|1
local_nfs_virtual_router_test|_suite_teardown_|0|0|0|1
Total|304|0|4|0|300


You can now another view by running `$ appbuilder add-view`.


BWL in 3.3.5? o.O


Great catch, thanks @khakiout!


This might need to be `#!/bin/bash` because `pushd` and `popd` are bash functions.


Why we can not have 'null' value for 'logindate' ?
If a user has never been logged in.


type_flag is not continuous in this branch (see the next comment)


If type_flag was not in ContinuousVariable.TYPE_HEADERS above, if wont be here either.


http://wowwiki.wikia.com/wiki/Blackwing_Lair Patch 1.6


To som povodne chcel pouzit, ale zatial to nepouzivam. Nechal som si to vsak ten kod lebo je to celkom uzitocna funkcia, ktoru asi pouzijem neskor.


The semantics of syntax highlighting in VimL are already broken as far as I can tell, since it doesn't handle correctly path-like strings in arguments. See for example the highlighting of:
~~~
edit ~/made-up-dir/path.ext
~~~
where the `-`s are highlighted as `vimOper`, which certainly is invalid. The whole argument here should be treated as a single token, which is what I tried to apply to the `:plug` argument highlighting.


102497980-Improve-waste-heat-function-handling-for-CoilCoolingDXMultiSpeed-and-CoilHeatingDXMultiSpeed-#5162 (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1289 of 1289 tests passed)

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


what the f2ck ?


You can now add authentication and authorization capabilities or add a list view by running `$ appbuilder add-authentication` or `$ appbuilder add-list`, respectively.


Apparently your editor has entered a tab here. This happens often; please try to find a way to not do it. Check your changes with `git diff` before committing them and your commits with `git show` before making pull requests. Also see http://who-t.blogspot.gr/2009/12/on-commit-messages.html on unrelated white space changes.


1: M111 unrecognized component name: manage


You could remove the #ifdef around AUTH_TYPE_RAW_NTLM, if necessary. I included it to detect possible references to the non-existing array entry early. You could also interleave the #defines into the array to reduce the amount of #ifdefs by one.

Another idea would be to stuff the other parts into several functions, which you #ifdef to dummy implementations in one block.


stratified_tank_docfix (nmerket) - Win64-Windows-7-VisualStudio-12: OK (1818 of 1818 tests passed)

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


console.debug does not exist in Node and hence this throws an 'Undefined is not a function' exception


Another possibility could also be documented here:
````
@example SELECT * WHERE { ?s ?p ?o . } ORDER BY ASC(?o) DESC(?p)
query.select.where([:s, :p, :o]).order_by([:o, :asc], [:p, :desc])
````
Although, in fact, I think this syntax could be removed in favour of the hash syntax (implemented in query.rb:398-408)


You can now add another field by running `$ appbuilder add-view`.


So typically, this code should not have the loop in it. It should only contain the code necessary to render one post.


Same here - you want to just have the code to render one topic.


yes. fixed.


Solves issue https://github.com/ErasmusMC-Bioinformatics/edger_galaxy_wrapper/issues/5


@brew thanks, can you have it print the resource_fields for datasets too?


It was in docverter but it wasn't working. It wouldn't increment because it would break before, causing it to loop forever.


If you do what I say regarding rendering one topic in the partial, then you can do this and let Rails loop for you:

```
<%= render @topics %>
```

That tells rails to loop over the topic objects in the collection, and render that partial for each one. It does this through introspection, so it's actually smart enough to know which partial to render based on the contents of the collection. It can even call different partials for different objects without you doing a thing.


You can now add a data provider, a form, or an about page to your project by running `$ appbuilder add-dataprovider`, `$ appbuilder add-form`, or `$ appbuilder add-about`, respectively.


Fixed in https://github.com/xbmc/xbmc/commit/954ad3f8686abeb55f492331ac1e49ffde6c1b5b


See my comments on the loop above. You would call it like this:

```
<%= render @topic.posts %>
```


What is the interest of 'modifdate' filed ?


Finally, you could get rid of the `oid = discard_const(&gss_mech_ntlmssp);` part, if the gss_mechs were an array of `struct { const char * , gss_OID_desc }`, you would just have to walk through.


rax retry tests


```
System.InvalidOperationException was unhandled by user code
  HResult=-2146233079
  Message=Sequence contains no elements
  Source=System.Core
  StackTrace:
       at System.Linq.Enumerable.First[TSource](IEnumerable`1 source)
       at SonarLint.Rules.StringFormatArgumentNumberMismatch.<>c.<Initialize>b__10_0(SyntaxNodeAnalysisContext c) in C:\Users\dinesh\Desktop\sonarsource\sonarlint-vs\src\SonarLint\Rules\StringFormatArgumentNumberMismatch.cs:line 114
       at SonarLint.Helpers.DiagnosticAnalyzerContextHelper.<>c__DisplayClass0_0`1.<RegisterSyntaxNodeActionInNonGenerated>b__0(SyntaxNodeAnalysisContext c) in C:\Users\dinesh\Desktop\sonarsource\sonarlint-vs\src\SonarLint\Helpers\DiagnosticAnalyzerContextHelper.cs:line 43
       at Microsoft.CodeAnalysis.Diagnostics.AnalyzerExecutor.<>c__DisplayClass35_0`1.<ExecuteSyntaxNodeAction>b__1()
       at Microsoft.CodeAnalysis.Diagnostics.AnalyzerExecutor.ExecuteAndCatchIfThrows_NoLock(DiagnosticAnalyzer analyzer, Action analyze)
  InnerException:
```

when doing `string.Format("")` and removing the `""`


For add-about, add-authentication and add-list:
You can now add another view by running `$ appbuilder add-view`.


Are you sure that's needed? There's a `ignore-errors` a little above. Explicitly handling this return value might be better, but then the question is whether we still need the `ignore-errors`. I use that because that's how Gnus uses this function too.


yes


Summary based on http://opensource.com/life/15/8/happy-24th-birthday-linux-kernel


This also needs some coloring for the commands :)


TeamCity Xbim :: Xbim Geometry :: XbimGeometry [Build 46](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=142&buildTypeId=Xbim_XbimGeometry_XbimGeometry) is now running


Dude...stop submitting already submitted tests.


FourPipeBeamAirTerminal (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (764 of 764 tests passed)

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


d'oh


だめ


I never would have thought this is how basic branching works. Fixed with:
```py
if type_flag in DiscreteVariable.TYPE_HEADERS:
    coltype = DiscreteVariable  # without any values
# else just leave as is (StringVariable, likely)
```


I would use only "scope[s]" instead of section


I was going to propose 'plugins' :) Although adapters are also a sort of plugins.


Oops!


I would use "scope[s]" instead of "section"


OK. Just that it might be harder to pull that out later ;-)


CRYPTO_zalloc have same number with X509_get_extension_flags?


This helps me tremendously. Thank you! Is this change effective in the next version of OS or can I utilize it now? Thanks!


by this comment, do you mean using ```sol_util_strerrora()``` or alikes?


Should we really allow `Tuple{1, 2}`?

Only solution I can think of so far is to use `(Row, Col)` to represent the size of both `FixedArray` and `FixedMatrix`.


Done.


dehumidifier-fixup (kbenne) - i386-Windows-7-VisualStudio-12: OK (2307 of 2332 tests passed)

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


@mosra The second code snippet works.


This was actually a fix for inherited/merged state data, not array.find as the comment would suggest ;-)


The call to `subscribe` and subsequently to `tap` is not delayed to the point the request is made.  Look at the call site of `subscribe` and body of `subscribe`.


Should be in singular: `JobBoardExtension`


Good idea. I think I had it as a labelled argument at one point during my many iterations...I'll put it back.


Yeah, I dunno. It can get confusing I guess if we treat similar things differently. In fairness, perhaps `urls` is better, and we just adopt that everywhere and assume a list everywhere. I guess for a job or an institution there may be cases for multiple URLs. What do you think?


Well done :)


Service name should be simple (mostly if you have only 1 bundle).
`form.job_type`


:exclamation: :exclamation: :exclamation: MODULO BIAS DETECTED :exclamation: :exclamation: :exclamation:

This makes the generator vulnerable to [modulo bias](http://stackoverflow.com/questions/10984974/why-do-people-say-there-is-modulo-bias-when-using-a-random-number-generator).

Compare result of the following script with previous implementation:

~~~php
$s = Nette\Utils\Random::generate(1e7, "\x01-\xFF");
$freq = count_chars($s);
asort($freq);
print_r($freq);
~~~


Checkmarx scan results 03 Sep 2015 16:41 UTC +03:00

High
Medium
Low
Info

New
1
0
0
0

Recurrent
0
0
0
0

Fixed
0
0
0
0

 Open Viewer
Included commits

Commit ID	Owner

1e6db40957da8a680b26fa003325c70e7e6fd5a2	@dortal


README.md


READMEfefef.md


`JobBoardExtension` without `s`


> The whole argument here should be treated as a single token, which is what I tried to apply to the `:plug` argument highlighting.

Totally agree with that! It’s just the linking to `String` I object to.


I think it's a copy-paste error on my part, actually. Sorry about that.


Si


Gaah, of course, you're completely correct. This is a thing I'm teaching later today, even! Shame on me!

And kudos for you for making a nice library! ;)


I guess the type definitions were based on the UCI data description: https://archive.ics.uci.edu/ml/datasets/Auto+MPG

I am not sure if we should change them, even if our heuristic would give them different types. (this probably applies to all dataset changes)


@jcfr understood, I will update this. For some reason in my use case I was accessing the component # 0 of an array with 3 components (default in DoubleArray), which therefore was creating a tuple array that could contain only 1 component, and I got no warning or error.


Why change this?


Done


Sure! I thought about using Directory for this, but it looks kinda awful
with the default colorschemes. Suggestions are appreciated ;)

El jue, sep 3, 2015 10:54 AM, Martin Kopischke <notifications@github.com>
escribió:

> The whole argument here should be treated as a single token, which is what
> I tried to apply to the :plug argument highlighting.
>
> Totally agree with that! It’s just the linking to String I object to.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/fmoralesc/neovim/commit/d17f6b680db1e6a11a583a4b49bdfce4e81aaba2#commitcomment-13047630>
> .
>


develop (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1291 of 1291 tests passed)

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


For comparing extensions you can use:
```c++
file_path_.MatchesExtension(FILE_PATH_LITERAL(".lnk"))
```
The result will be the same, but it's a bit more expressive IMO. This is also true for line 196 (`.svgz` test)


DUDE GET GIT BASH


Well as I point out it does not work for the typealias, which is pretty substantial to do all kind of things...Also it fails for TypeVar, which makes these kind of things impossible:
```Julia
row{R, T}(a::Mat{R, 1, T}, j::Int) = (a.(1)[1][j],)
```


If you create a service with an external class, don't name it `job_board. ...`
Like `html_purifier.form. html_purifier_transformer ` for example.


I'm following what we did for the dir_handle_command_get function as it is quite large and has many branches. Test file is around 500 lines already and just ~25% of the function has been covered.


Typo, `cartesian`.


It will be in 1.8.5 and higher


1.8.5 comes out next week


ack


s/confg/config/ here and in the .erb file.


nope, at least there is nothing saying that, i also have seen checking if it's null inside the microhttpd code.

Just going to add this check. Thanks for pointing it


The quoting on the `only` variant name should be done only with `'`. And the phrasing should be `"'only' filters"`


Je regarde ça en rentrant. C'est la solution d'y tu m'as parlé hier ?

On Thu, Sep 3, 2015, 3:32 PM Cesar Leblic <notifications@github.com> wrote:

> kine vs kine crash resolved. @herpec-j check that
>
> ---
> Reply to this email directly or view it on GitHub:
>
> https://github.com/Another-Game-Engine/AGE/commit/39354369664ae7ea4bce3f341013b7a164e369aa
>
--

Mr. HERPÊCHE Jonathan
Software Engineer at Agueris
+33 (0)6 20 05 13 72


There's more 0/NULL initializing below here (can't comment on the correct row on this commit since it ain't touched)


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


Fixed.


Alright! No problems, I'll let you know. Thanks to you too!


can you remove the dest= argument ? it will becaome simply "options.launch".


> I don't remember exactly but I think `am` can apply such patches.

Not as far as I know, because it doesn't have any of the metadata to
create the commit.  It's just that 'git apply' can use format-patch
patches.


Without "^{commit}", rev-parse only checks that the rev is valid, not
that it exists.


This commit is meaningless. There is no "right editor". You are using Markdown, and remember that.


That's fixed in a later commit.


`it can invoke itself`.


BTW, instead of commenting out every line, you should wrap the entire file in `#if false`.

This makes diffs much cleaner.


r+


I would say:

```
Specifies the root directory for Docker metadata and volumes.  If
the devicemapper backend is in use, containers and images will
be stored in a dedicated LVM thin pool.  If the overlayfs
backend is in use, containers and images will also be stored
in this directory.
```


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


Hmm, I don't know, but here is the error I get.

```
Debugger entered--Lisp error: (wrong-type-argument sequencep error)
  append(error (:ascent center :relief 1))
  (cons (append image (quote (:ascent center :relief 1))) (quote ((slice 0.0 0.0 1.0 0.5))))
  (propertize " " (quote display) (cons (append image (quote (:ascent center :relief 1))) (quote ((slice 0.0 0.0 1.0 0.5)))))
  (insert (propertize " " (quote display) (cons (append image (quote (:ascent center :relief 1))) (quote ((slice 0.0 0.0 1.0 0.5))))))
  (lambda (image offset align-to) (insert (propertize " " (quote display) (cons (append image (quote (:ascent center :relief 1))) (quote ((slice 0.0 0.0 1.0 0.5)))))) (insert (propertize " " (quote display) (list (list (quote space) (quote :align-to) align-to)))) (forward-line) (forward-char offset) (insert (propertize " " (quote display) (cons (append image (quote (:ascent center :relief 1))) (quote ((slice 0.0 0.5 1.0 1.0)))))) (insert (propertize " " (quote display) (list (list (quote space) (quote :align-to) align-to)))))(error 12 16)
  apply((lambda (image offset align-to) (insert (propertize " " (quote display) (cons (append image (quote (:ascent center :relief 1))) (quote ((slice 0.0 0.0 1.0 0.5)))))) (insert (propertize " " (quote display) (list (list (quote space) (quote :align-to) align-to)))) (forward-line) (forward-char offset) (insert (propertize " " (quote display) (cons (append image (quote (:ascent center :relief 1))) (quote ((slice 0.0 0.5 1.0 1.0)))))) (insert (propertize " " (quote display) (list (list (quote space) (quote :align-to) align-to))))) error (12 16))
  gravatar-retrieved((:error (error http 404)) (lambda (image offset align-to) (insert (propertize " " (quote display) (cons (append image (quote (:ascent center :relief 1))) (quote ((slice 0.0 0.0 1.0 0.5)))))) (insert (propertize " " (quote display) (list (list (quote space) (quote :align-to) align-to)))) (forward-line) (forward-char offset) (insert (propertize " " (quote display) (cons (append image (quote (:ascent center :relief 1))) (quote ((slice 0.0 0.5 1.0 1.0)))))) (insert (propertize " " (quote display) (list (list (quote space) (quote :align-to) align-to))))) (12 16))
  apply(gravatar-retrieved ((:error (error http 404)) (lambda (image offset align-to) (insert (propertize " " (quote display) (cons (append image (quote (:ascent center :relief 1))) (quote ((slice 0.0 0.0 1.0 0.5)))))) (insert (propertize " " (quote display) (list (list (quote space) (quote :align-to) align-to)))) (forward-line) (forward-char offset) (insert (propertize " " (quote display) (cons (append image (quote (:ascent center :relief 1))) (quote ((slice 0.0 0.5 1.0 1.0)))))) (insert (propertize " " (quote display) (list (list (quote space) (quote :align-to) align-to))))) (12 16)))
  url-http-activate-callback()
  url-http-content-length-after-change-function(445 459 14)
  url-http-wait-for-headers-change-function(1 473 472)
  url-http-generic-filter(#<process www.gravatar.com<1>> "HTTP/1.1 404 Not Found
\nAccept-Ranges: bytes
\nAccess-Control-Allow-Origin: *
\nCache-Control: max-age=300
\nContent-Type: text/html; charset=utf-8
\nDate: Thu, 03 Sep 2015 02:07:34 GMT
\nExpires: Thu, 03 Sep 2015 02:12:34 GMT
\nLast-Modified: Wed, 11 Jan 1984 08:00:00 GMT
\nLink: <http://www.gravatar.com/avatar/541cdd3bdd8389a1d50da430da5ff337?d=404&r=g&s=28>; rel=\"canonical\"
\nServer: nginx
\nVia: 1.1 varnish
\nX-Varnish: 42252895 42252872
\nContent-Length: 13
\n
\n404 Not Found")
```


I think you should do a try/except around parse_date. It can raise DateFormatError, https://github.com/mozilla/mozregression/blob/master/mozregression/errors.py#L34


Missing space around operators. I wonder how this ever passed Continuous integration.


What if we add more than one? To me:

- There should be only a single possible id generator per collection; that's where I'm getting a little uncomfortable reusing `use` for this, though with a proper error raised if you try to add many, it's probably okay;
- The validation implementation should be provided by the class itself — thing `if (processor.validate())`.

Thoughts?


Missing space around operators.


Yes,
some Strings are
not at the companion languages files
and are not at openTx languages files

think these are only 5-10 stings


Native depends are build depends that are compiled for the host machine(the one that does the compilation), so they are not cross compiled. Example: cmake, texturepacker
target depends are built for the _target_ architecture, which is the platform the final binary will _run_ on. Those are cross compiled.

So the question is: Is bson used at kodi runtime? If yes it must be a target depend.

As for using cmake for bson: Don't worry about windows, it doesn't use unified depends at all. We'll have to build bson for win seperately.


r+ and a Thank You :)


I've never tested this, but I've always been curious of what the performance impact of reading an environment variable per transaction is.


Yep
Basé la dessus que j'ai lu en diagonale hahah
https://devtalk.nvidia.com/default/topic/672713/run-time-warning-message-in-px-3-3-between-character-controllers/

2015-09-03 10:00 GMT-04:00 Jonathan Herpêche <notifications@github.com>:

> Je regarde ça en rentrant. C'est la solution d'y tu m'as parlé hier ?
>
> On Thu, Sep 3, 2015, 3:32 PM Cesar Leblic <notifications@github.com>
> wrote:
>
> > kine vs kine crash resolved. @herpec-j check that
> >
> > ---
> > Reply to this email directly or view it on GitHub:
> >
> >
> https://github.com/Another-Game-Engine/AGE/commit/39354369664ae7ea4bce3f341013b7a164e369aa
> >
> --
>
> Mr. HERPÊCHE Jonathan
> Software Engineer at Agueris
> +33 (0)6 20 05 13 72
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Another-Game-Engine/AGE/commit/39354369664ae7ea4bce3f341013b7a164e369aa#commitcomment-13047810>
> .
>

--
[image: dancing frog animation][image: dancing frog animation][image:
dancing frog animation][image: dancing frog animation][image: dancing frog
animation][image: dancing frog animation][image: dancing frog animation][image:
dancing frog animation][image: dancing frog animation][image: dancing frog
animation][image: dancing frog animation][image: dancing frog animation][image:
dancing frog animation][image: dancing frog animation]


just do an else here. changesets can be between 8 and 40 chars. (well even less than 8 maybe)


The project is written using C++. You should at least provide a Makefile.


@Carl-Chinatomby it works


This still misses `$` sign.


:+1:  La agregaré a SessionRepository


Wow!


It has already been tested? I'm sorry I didn't knew, I did searched the history oif tests to see if it had been done before. Can you link me to the test? Thank you.


GJ guys keep on!


docker commands should probably have `#` sign or?


nope, just in PC, i wont


The title should be **Docker Compose** probably.


If we set to open, and initialize with the base info values, shouldn't we also set validated and accepted to false?


Here you should make a *h1* headline, can be same as *title*.


Since chardet is not optional, I would also include it in INSTALL_REQUIRES in setup.py.


I have done the changes. Hopefully this is correct? What is the next step?


you should define self.action, not options.launch_action, see https://github.com/MikeLing/mozregression/commit/161cf83746a422d300688b945832ee5665c317fd#diff-a753870fc2c6fa4864480ab7b1c1cd57R403

Also it should be just before https://github.com/MikeLing/mozregression/commit/161cf83746a422d300688b945832ee5665c317fd#diff-a753870fc2c6fa4864480ab7b1c1cd57R403
(if options.launch -> set self.action = 'launch'), and replace the if options.first_bad_revision or options.last_good_revision: by elif


A mix of ghetto french, italian and mexican :dancer:


A function defined inside a for loop? This is asking for trouble. This should be moved to a scope outside of numerous for loops...


Your code is indented using \tab, which is ugly. Better option is to follow the Google C++ style guide:https://google-styleguide.googlecode.com/svn/trunk/cppguide.html


not teçhiat, it is "teçhizat" . My bad


This remains a few bugs, mainly lies in the error that cannot use the inline-assembly to read parameter stored in variable, to store EAX as well as EDX vice versa.


Good point. I'll use `$charlist[(ord($bytes[$i]) + $i) % $chLen];`


Since this is in an init function I assume nano/millisecond performance doesn't matter; so my suggestion would be to change it to OPENSSL_zalloc here instead and remove the 0/NULL initializers below. (Just my personal opinion that zero initialized is better if not super important for performance to avoid potential garbage data bugs).


r+


Maybe this function should work the same way batctl does (i.e. iterate over all interfaces in `/sys/class/net` and see if the content of `batman_adv/mesh_iface` equals the meshif name). I'm not really sure actually... with current kernels, the lower_* links are certainly more efficient, so I guess it is fine like this...


Why does this ctor take a raw pointer?


97215920---Fill-Gaps-in-HVAC-Components---Initial-Code (rraustad) - x86_64-MacOS-10.9-clang: OK (1809 of 1810 tests passed)

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


Using the `babel-loader` will transpile our ES6 and JSX to browser compatible ES5.


Doh! Thanks :-)


Note: this name is two characters too long for pylint, but I wanted to keep it consistent with `course_team_post_save_callback`.


Inheritance is deprecated in later puppet versions, so that line should go.


Checkmarx scan results 03 Sep 2015 16:59 UTC +03:00

High
Medium
Low
Info

New
0
0
0
0

Recurrent
1
0
0
0

Fixed
0
0
0
0

 Open Viewer
Included commits

Commit ID	Owner

9e8e0287bf758ed123b85bed1b106af23cc01c99	@dortal

6ac48c3ad90ffd84be29ebf8bd4859e06a19965e	@dortal


I'm not convinced that I should allow this. Why do you have `tests-variants.cfg` in the first place?


I think so too. I will add `.eslintrc` file :)


Yes, I changed it now, so that is the IdSchema goes in `this._idSchema` on the collection, see https://github.com/Kinto/kinto.js/pull/143


Cherry-picked to release-15.09 (e2ebe9199104115fd419b9efea6330ef49065f5b).


I am thinking about the wording/introduction here....perhaps something like

`docker-compose` is bla.. and bla... Here is an example of building a Django app backed by PostgreSQL.... [and then] What will we have to do?


See that know FaceViewSellection => FaceViewSelection


Yeah, but the coding style is broken. Well, if this is a quick fix and you plan to bring $proceed if statement back, keep it as it is, but it looks a bit dirty ;)


Ok, will do.


No sir, savedefconfig do not use MB but simple HEX number


r+


If you make a h1 headline "Docker Compose" then this is redundant.


I'd probably just check that the return value (`$?`) is 0 or 1, but that should work just as well so leave it as it.

but I would add output of the command to the error message, if the path is incorrect or the binary is not executable, it will be inside the `OPENSSLBINHELP`


哈哈，注意劳逸结合，这样可以更高效的学习/工作。

Abstract Operator <notifications@github.com>于2015年9月3日周四 下午8:12写道：

> @andytimes <https://github.com/andytimes> [image: :weary:] 可怜我等苦命少年还在撸代码
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/racaljk/hosts/commit/ccfbdeed2aa404c95fab96b323275eb534f4901e#commitcomment-13045635>
> .
>
--
Andy


Could you add fabric.properties.dist here too?


Did you "make translations"? That needs to be done to update the translations file with the new items in the source.


django -> Django
- we'll -> we will


After looking at it in more detail it has been shown unrelated, it was introduced in https://github.com/jenkinsci/analysis-core-plugin/commit/c90a666255b447b6374158e678bc398f7fd7d2e7.

I already fixed it: https://github.com/jenkinsci/analysis-core-plugin/commit/bfcc3322f53abfe5f7fc1ee93eb9561bde864b1d


What does this function do? You need to improve the documentation. Such as
```
// This function substract each column element using the column-wise maximum element.
// 'params' is a pointer to the beginning of the matrix, and should be allocated as a
// 'array_n' times 'array_m' array before calling.
```


Isn't it a really small change?


add tools to split feat and target, which have been used in script steps/nnet/train_scheduler.sh


effect


Yes.  Definitely the wrong assertion.


I don't have such issue. I can close a tab and make another call without crash but I had to patch WebRTC code (https://github.com/sarandogou/webrtc-everywhere/blob/master/webrtc_win.patch).
I have to check your patch.


chkdsked up hhhhhhhhhhhhhhhhhhhhh


:+1: Absolutely fine with me, for whatever my +1 counts for.


More here


@marzig76 sorry that I wasn't clear. I did not mean the 1Mb floor, but the floating limit: "dropping bottom 20% and top 20%, and then the most common floor (minimum) is chosen." If we choose 20th percentile as the max size, then why do we need to "drop top 20%"? To me it seems that top 20% does not affect the bottom 20%.


Checkmarx scan results 03 Sep 2015 17:04 UTC +03:00

High
Medium
Low
Info

New
1
0
0
0

Recurrent
0
0
0
0

Fixed
0
3
17
0

 Open Viewer
Included commits

Commit ID	Owner

a4a6f4e1d4f5f6b5ff1a814bd1381e25acf97714	@dortal

f044ce39220d068d05ad9cdb43c17f8832ccc058	@dortal


Will fix.


@LionNatsu because it fscks up.


Django with capital D. I would use small *d* only when talking about the binary (and use back-tics).


"assert($(\"div\").length > 4, 'Add a div element with the class well inside each of your div class=\"col-xs-6\" elements')",


Could you elaborate the "mishaps" @slyness?
I was stuck on 3.4.16 for a while because `berks update` already resolved openssl-4.4.0 before and I had to manually set

```ruby
cookbook 'postgresql', '>= 3.4.20'
```

in my Berksfile to solve this. Was quite a hassle to find why it wouldn't update :(


wtf


That seems like it should depend on whether or not overlayfs is in use.  If you're using devicemapper, then images/containers go on the thin LV, and don't take up space here.

Or hm, does it work out so with devmapper, we take 40%, and then the root volume is 40% of *that*?


s/==/=/


actually, a combination of subset-feats and the Unix split command can do this... didnt' need to rewrite one from scratch..


@acheetham, forgot to add hover state styling for contrast themes, will do that now


<TextView
    android:id="@+id/my_textview"
    android:layout_width="wrap_content"
    android:layout_height="wrap_content"
    android:text="@string/next"
    android:background="@color/white"
    android:elevation="5dp" />


fscks up hhhhhhhhhhhhhhhhhhhhhhhhhh


Can this assert use zero?


Thanks. Makes sense. For `car_name`, the link says `string`, so the change is orderly.
While time has inherent sorting order, what do you propose for `model_year`?


Removed in https://github.com/JuliaOpt/CoinOptServices.jl/commit/20961a351f1ec3d65163cae5202526876eac01ae


Octree (DeadParrot) - Win64-Windows-7-VisualStudio-12: OK (1818 of 1818 tests passed)

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


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


I'd fixup this commit with the previous one


@biergaizi @MingcongBai has been using fsck for the f-word for a while, are you on ~~LSB~~ LSD?


no problem.


@udalov Please have a look


that's a very good suggestion


The companion object part is suspicious. Why is this change needed?


I tried to find a similar test, the closest one is this :
http://tests.stockfishchess.org/tests/view/541a04fe0ebc597b2960e639

I stopped the test for the moment, let me know if you find an identical test, I don't want to waste the framework ressources!


cocos2d库，自己填充，默认为3.5


No. There was allways a space since the beginning. Not having it like this breaks the seatmap renderer. Trust me


on LSD? Maybe on BSD, somehow both things are from Berkeley.


@biergaizi BSD hhhhhhhh


Is this test needed?


I'd fixup this with the previous one


I think we'll need to make this configurable down the line.  There are a *lot* of mkfs options which AIUI can be important when optimizing for performance.


And fixup this with the previous one


I wonder if this would be better now with a global method to call, e.g. `dunya.set_collections(collections)`, and then we send this header every time that we send a request. What do you think?


Checkmarx scan results 03 Sep 2015 17:11 UTC +03:00

High
Medium
Low
Info

New
0
0
0
0

Recurrent
1
0
0
0

Fixed
0
0
0
0

 Open Viewer
Included commits

Commit ID	Owner

b8b9a07a0df4777bbb0e82d08c7b986dde3a3265	@dortal

0b9228037aca732fceee599d80d3f239ac56e2e6	@dortal


It's a bad idea to write all the code in one cpp file, even if it's only hundreds of lines. Learn how to use header file, structure your code, and make it reader-friendly.


The other errors don't end with a `.` - maybe drop it for consistency?


I'd say "must be specified" to avoid double negatives.


Nice. :+1:


This LSM303D driver comes from AP_InertialSensor/AP_InertialSensor_LSM303D.cpp
which I haven't found it used in any boards.


Ok, I see this is systemic. So skipping the heuristic if type is explicitly provided seems the best option.


@nrc

> Why the pun? Could you just add an Undecided terminator instead?

Just so that later code doesn't have to deal with it.


This should work:

```
abstract D{x, rest}
abstract Nil

typealias FixedMatrix{Row, Column, T} FixedArray{T, 2, D{Row, D{Column, Nil}}}
```

Maybe I should allow `Tuple{2}` again to minimize breakage. I'm not sure it's a good idea though.


had to make this commit because of some bug with github pages hosting service. it did not seem to like the underscore before my partial template name.


The database should probably be deleted in that case as otherwise we get a ghost database linked to no descriptor.


We create root volume first and then thin pool. So if devicemapper driver is in use, then 40% of free space will be used for docker root volume and then 40% of remaining will be used for thin pool.

If I make these calculations driver dependent, then I can't export the defaults in a file. I personally think that user should pass in good values for DOCKER_ROOT_VOLUME_SIZE depending on what they are trying to do.


Yeah, do not criticize my coding style. I won't change. x3


you need to make this call if self.conf.use_external_dhcp


By the way, where do you check the ICRC on incoming packets?


Consider the following instead:
  auto clInfo = m_ledgerMaster.getCurrentLedger ()->info();


But what if I want to call my meshif `lower_foo`? ;) Just adding an $ at the end should be enough to make the match robust.


In general, I prefer continuous features for time related data, but for this specific data set, I would keep the attribute discrete, as this is how the author of the dataset specified it.


No problems here :+1:


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


TeamCity Xbim :: Xbim Geometry :: XbimGeometry [Build 47](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=143&buildTypeId=Xbim_XbimGeometry_XbimGeometry) is now running


these 2 lines are not needed


Would be really nice if you change the subject to be <= 50 chars


A basic collection of potential methods to be used in the final program


Uhmm mostly `" {image_name} "` or `"[[:space:]]{image_name}[[:space:]]"`


I mean here it should be just "if enable_metadata:"


delete comments please


Seems like for no good reason. :flushed:


@nrc

> BasicBlock is an index into a graph of BasicBlockData

Yes.

> I assume this is just to avoid the borrowing issues with graphs?

Do you mean as opposed to using a pointer or an arena or something? I tend to prefer the index solution, both because it obviates the need for a lifetime and because the data is kept compact in a vector. In particular, I envision us editing the MIR in place, in which case having a vector is nice because it can be resized (grown, shrunk) as needed, as long as you keep all the indices updated.

> But you have NodeIndexs too - I don't understand the difference between those and BasicBlocks...

This comes from re-using the `Graph` abstraction -- there is basically a 1-to-1 relationship between a basic block index and a node index. I've been thinking though it doesn't add much and I might just stop re-using `Graph`. It'd probably be nicer to make a trait for graphs and write generic algorithms over the trait instead.


delete me .... delete me :)


You're right with `Django`, thanks. What's the story behind `we'll`?


delete me


React components are trees of one or more React components.  This means React components are composable.  In this case our parent node is the only React component in the tree.

While it looks like we have a DOM template embedded in our JS, it is important to note that this is not DOM, it is JSX representation for the Virtual DOM in React.  JSX is transpiled into nested JS functions.

So something like:
```js
<div data="test" moreData="hi">
  <h1>
    <MyTitleComponent />
  </h1>
</div>
```

will become a set of nested JS functions:
```js
React.createElement('div', {data: 'test', moreData: 'hi'},
  React.createElement('h1', null,
    React.createElement(MyTitleComponent, null)
  )
);
```

If you are opposed to JSX feel free to write your Virtual DOM representation with `React.createElement`, which is in the form:
```js
ReactElement createElement(
  string/ReactClass type,
  [object props],
  [children ...]
);
```

Don't worry about props right now, we will get to them later in this tutorial.

I also want to emphasize that the JSX represents the Virtual DOM, not the DOM itself.  JSX is not a 1 to 1 mapping with the DOM as some components will not actually render DOM, but other React components (that might then render other React components, DOM, or a combination).


@mkaluza I've just pushed the changes if you want to review them, thanks!


The click on the image is indirectly also a click on the <a> which is the only relevant part as the <a> has the `href` reference to the image that needs to be displayed.

> Op 3 sep. 2015, om 07:51 heeft Alexander Pilz <notifications@github.com> het volgende geschreven:
>
> Ok, this is not that easy. The current pat-gallery concentrates on pulling up the gallery on click on one of the images. We need a separate section for the case where there are no images :(
>
> > Am 03.09.2015 um 07:42 schrieb Alexander Pilz <pilz@syslab.com>:
> >
> >
> >> Am 02.09.2015 um 19:40 schrieb Cornelis G. A. Kolbach <notifications@github.com>:
> >>
> >> Photoswipe styling
> >>
> >> @pysailor, @pilz, This should be the styling for pat-gallery. Once the
> >> modified .js is in place, this should work.
> >
> > Is it correct that we basically should “just” change the pattern to trigger on
> >
> > trigger: ".pat-gallery:has(a)”
> >
> > instead of has(a img)? I guess we try that out first and then also on that place where it is used in OiRA (@pysailor?). Are there other places where pat-gallery may break?
> >
> >
> >>
> >> ---
> >> Reply to this email directly or view it on GitHub:
> >> https://github.com/ploneintranet/ploneintranet.prototype/commit/2bf6825e9afc45503e5cbad2336fffbd82407ee1
> >
> > --
> > Alexander Pilz
> > SYSLAB.COM GmbH, Landwehrstrasse 60-62, 80336 Munich, Germany
> > Tel: +49 89 3063589-0 - Fax: +49 89 3063589-9
> > http://www.syslab.com - Amtsgericht Muenchen, HRB 135057
> > Steuernummer 143/184/50154 - Ust.-ID: DE212842815
> >
>
> --
> Alexander Pilz
> SYSLAB.COM GmbH, Landwehrstrasse 60-62, 80336 Munich, Germany
> Tel: +49 89 3063589-0 - Fax: +49 89 3063589-9
> http://www.syslab.com - Amtsgericht Muenchen, HRB 135057
> Steuernummer 143/184/50154 - Ust.-ID: DE212842815
>
> —
> Reply to this email directly or view it on GitHub.
>


I don't think so. It's a crap templating "system". I think if there's more need for templating in other parts of the userbase, we should switch to a real templating system.


Makes sense. Will change.


Ah, you are right, both versions are valid, only the combination created by cherry-pick fails. Anyway, the test is there and extended regidx api.


if your user is in `docker` group (and therefore `/run/docker.sock` is group-owned by `docker` group), you don't need `root`


Ok, will drop "."


@rec is me... so I get an email each time you write it!  :-)


소켓 허용은 코드단에서 결정되는 것이 아니라서 언급하지 않아도 좋을 것 같네요


@BuzzBumbleBee Where do you set DELTA_RADIUS_TRIM_TOWER_X? Should they not be in the delta configuration files?


This commit sets up the build process such that we can write code in ES6, use JSX, and run a web server (via `webpack-dev-server`) that has hot reloading so we do not have to hit refresh as we modify code.

It also renders a basic React component to the page.


The index here is a string value from the option. e.g. `<option value="1">Firefox</option>`.


agreed. We can just introduce another knob DOCKER_ROOT_MOUNT_OPTS in future if need be to allow passing in fs mount options.


공유가 불가능한 건 아닙니다.
대신에 lock을 잡고 사용해야 하는데, 그러면 코드가 깔끔하지 않아서 사용을 피한 것...


That's is better, but the bias is still there, just a bit more hidden (slightly different for each character). The security (against modulo bias) now relies mostly on (insecure) `str_shuffle`.


Thanks


I’ll have to take a look next time I’m at my machine… but basically, I think we need to be consistent with other Ex commands taking a path spec as their argument, hoovered awful that might look by default (better don’t get me started on that – I’ve got a whole, sprawling, private plugin that does nothing but try to fix the biggest inanities in default highlighting and colour schemes ;)).


Now we are rendering our App component, which is the top level of our tree.


My bad--the JS code is rougher than the Python code. Looks like I didn't take out "todo" comments and `console.log` calls and finish commenting.

Generally, though, is this JS code decent? Are there better ways to do what it's doing here?


It worked?


Just to clarify: `django` and Django e.g. back-ticks for command.

About we'll -> we put that in our guidelines, it's a common practice for more formal texts.


Ah, I wasn't sure if Lua supported $ (and somehow was too lazy too look it up or something). Will fix.


https://archive.ics.uci.edu/ml/datasets/Flags

According to the dataset specification, many more attributes should be numeric. And we could use names for discrete features, to make them more meaningful, but I am not sure if we want to go into this as a part of this pull request.


コメントのテスト


this is not the right place, it should be in neutron/agent/dhcp_agent.py like the other config values


+1 :)


Curly braces in JSX are for interpolation.  It is important to note things like `if` and `for` do not work in JSX.  Instead you can call a function in the curly braces, and that function can contain your logic and return the value you wish to render (it can also return JSX).


전체적으로 문체가 클라이언트 때랑은 달리 대화하는 느낌으로 바뀐 것 같은데,
개인적으로는 클라이언트처럼 좀 드라이한 느낌이 더 좋은 것 같아요.


:smile: my pleasure


增加了鼠标点击时的效果，考虑这部分的实现问题


@xc-racer99 mind sending me a hangout at anaskarbila@gmail.com ? (appriciate it :D )


Yup, there is [std::iota](http://en.cppreference.com/w/cpp/algorithm/iota) to fill a container with consecutive integers, though it expects that memory is already allocated.


@nrc

> you are pointing in to the middle of a block, right? Or are you constraining to point only to the end of a block?

Yes, the whole point is to point possibly in the middle of a block. I will update the comment with something like this, perhaps this makes it more clear?

    BBx:
                          <--- statement == 0
        STMT[0]
                          <--- statement == 1
        STMT[1]
        ...
                          <--- statement == k-1
        STMT[k-1]
                          <--- statement == k


Rust의 주제에서 벗어나는 이슈라서 언급 안 해도 될 것 같아요.


OK. J'ai regardé, c'est la meilleure façon de faire je pense. Je ne peux pas tester pour l'instant, mais ça m'a l'air correct. :)


Yes, I know. But $USER is not by default in `docker` group. Even if we (rightly so) explain here how to add yourself there, some might not have done it (perhaps for security reasons or they didn't do it *yet*). `#` just means on clean install, you will need admin rights.


This method should be marked as **const**.


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


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


**const** again


Here we are creating our first React component.  We are using the ES6 method of creating a React component.  you can also create your React components with ES5:

```js
React.createClass({
  render() {
    // ...
  }
});
```


[test]ソース上にコメントを記載


발송하는 기능도 같이 언급하는 게 좋을 듯
어떻게 보면 이벤트(클라이언트 접속, 채팅 발송 등) 처리하는 스레드


The commit should say: missing instead of mission


@nrc

> Why combine field access and pointer deref? I guess the borrow checker sees them similarly, but trans won't.

They also just have similar structure (mostly that they each have a `base`). And there is indexing too.


The one method that all React components need to implement is `render`.  This function returns the Virtual DOM representation of the component. Returning `null` or `false` will cause nothing to be rendered to the DOM.


The second argument to `parse` is used to build error messages if when using source files. I think it would be best to build the error message further upwards when pattern matching the parse result:
https://github.com/kRITZCREEK/psc-ide/blob/master/server/Main.hs#L70


please address this TODO....

if not self.conf.use_external_dhcp:
    self.spawn_process()


Here we create our first custom React component, `App` and learn how to interpolate variables/functions inside of JSX.


@nrc

> what are these used for?

Just a shorthand for a projection as it appears in an lvalue, vs projections as they appear in constants (below).


This revert has done a lot more than just reinstate the footer-widgets code.


Done


27/08/2015 Cambios realizados aquel día.


this change shouldn't be here


위에서 언급한 것처럼 서버에서 발생하는 모든 이벤트(클라이언트의 접속, 접속해제, 채팅 발송 등)은 모두 이벤트를 처리하는 스레드에서 처리합니다.
하지만 각각의 이벤트는 다른 스레드들에서 발생하는데, 이를 이벤트 처리 스레드로 전달할 필요가 생깁니다. 이를 위해서 사용하는 것이 채널.
이벤트 스레드가 채널을 만들면, 다른 스레드들을 해당 채널로 처리가 필요한 이벤트를 전송.
이벤트 처리 스레드는 해당 채널에 처리할 이벤트가 발생하면, 꺼내서 처리를 반복


Yes Sir, I realised that later. I had already started from form. Next time, I will read the questions carefully.


31/08/2015 Cambios realizados aquel día.


ditto


That seems verbose and makes it hard to work with arbitrary dimensioned arrays. Is it that bad to have `Tuple{2}` ?


@nrc

> Why B, maybe I is better (similar to F32, F64)

Yeah, I chose `B` for bits because I thought `I` suggested signed (i.e., the type `i32`), but... or maybe I should make `FloatBits` use `B` too.


엄밀히 따지면 2, 3 순서가 바뀌어야 할 듯
코드 상에서도 확인 필요할 것 같네요.


This change ignores destinationPage.getFolderPath(). I think this line needs to be:

```java
String path = destinationPage.isFolder() ? destinationPage.getFolderPath() : destinationPage.getJarPath();
```


01/09/2015 Cambios realizados aquel día.


02/09/2015 Cambios realizados aquel día.


Yep, it's just temporary.


yea, that sounds fine


Got it. Is there a good reason `INSTALL_REQUIRES` aren't parsed from requirements.txt like `LONG_DESCRIPTION` is from README.md?


:+1: thanks!


What does this change? Removing this line:
      $_SERVER['REMOTE_USER'] = '_'.$this->username.'_';
causes that next "checklock" reports no lock because lock is held by the same user. But in this code it assumes it returns that file is locked correctly.


I don't get it, why is this needed? These properties are not supposed to be used outside of this module


This should be called `EnableVisualEffects` to follow the pattern of preference keys.


Done


:-)
Sorry! I'll avoid using this term in commit messages...


develop (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (762 of 762 tests passed)

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


Here we add the ability to handle styles via Sass in our webpack config.


@nwhite89 Added is-active attr and model back. I can squash the two commits if required?


I don't think there is. Maybe we should just specify all requirements in setup.py and abandon the requirements.txt file.


Are start and end supposed to be the same value?


I'll just change the parser to honor the specified type, if any.


We add another loader to handle `scss` files (Sass files).  If you want to use `css` instead, change `scss` to `css` and remove the `sass-loader` from the list of loaders.

Loaders are executed from right to left.  So the `sass-loader` converts the Sass to CSS, which is then passed to the `postcss-loader` that is only using the `autoprefixer` plugin right now (adds our browser prefixes for us), which is then passed to the `css-loader` that handles the CSS itself, and finally to the `style-loader` that appends the CSS into style tags in the document. (There is the [extract text plugin](https://github.com/webpack/extract-text-webpack-plugin) if you want the styles to be generated as CSS files instead of using style tags).


Checkmarx scan results 03 Sep 2015 17:29 UTC +03:00

High
Medium
Low
Info

New
1
0
0
0

Recurrent
0
0
0
0

Fixed
0
0
0
0

 Open Viewer
Included commits

Commit ID	Owner

b8b9a07a0df4777bbb0e82d08c7b986dde3a3265	@dortal


(Alphabetical)


So how about if the guide says that we expect users to go through docker setup (which the docker guide says) and it expects that user is able to access docker daemon.


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


@miguelportilla To prevent confusion with special members


I don't know much about the expectations of `self$required_aes` and `self$default_aes`, but are they capable of containing `"group"`? In that case, does using `c` rather than `union` give the desired effect?

```r
> c(union(c("group", "bar"), c("bar", "baz")), "group")
[1] "group" "bar"   "baz"   "group"
```

Note the duplication of `"group"`. If it's not an issue, feel free to ignore this remark.


`raw_group` is a dict. I suggest to use `get` method instead of using and `if/else` block. Moreover, `description` attribute should be `None` and not an empty string.

```
group.description = raw_group.get('description', None)
```


If things work on 10.9 and later using the official API then it should be used so the alternate implementation would need to be 10.8 only:
```
if (kCFCoreFoundationVersionNumber >= kCFCoreFoundationVersionNumber10_9) {
  // 10.9 and later
} else {
  // alternate for 10.8
}
```


Another proof of concept – the following reconstructs `$charlist` used by `generate` after `str_shuffle` which should be impossible.

~~~php
$s = Nette\Utils\Random::generate1e7, "\x01-\xFF");

for ($j = 0; $j < 255; $j++) {
	$freq = array_fill_keys(range(0, 255), 0);
	$max = 0;
	for ($i = $j; $i < strlen($s); $i += 255) {
		$ord = ord($s[$i]);
		$freq[$ord]++;
		if ($freq[$ord] > $freq[$max]) {
			$max = $ord;
		}
	}
	$res[$j] = chr($max);
}

echo bin2hex(implode('', $res)), "\n";
~~~


summarize


The top level `App` component now has a child component, `Game`.


Yes. It's used to create a link to the dashboard showing a single day.


unless you're trying to give the header flip-flops and sunscreen >:)


I think using `if ( false !== strpos( 'srcset="', $atts ) ) { ... } ` instead of `preg_match` here would be more performant.


We need to hook in our `scss` file so webpack hits it from our index entry point into webpack


new println


Sure, that all makes sense. Looks good.


test


The function has to be named `walkDecls()` because that one comes from `postcss`. But as I said, you can name the function that you pass through `walkDecls()` anything you'd like, which in this case is `transformDeclars()`.


@Wackerbarth Now that the @BuzzBumbleBee trim codes are merged, can we document it and discuss how it should be properly used?

For instance, where I set DELTA_RADIUS_TRIM_TOWER_X and DELTA_DIAGONAL_ROD_TRIM_TOWER_X? I thought I could change these settings in the deltas configurations files.


Make sure to remove all the commented code.


added comments


Perhaps this line should be removed since it is just commented out?


Sure. it was useful when I was developing the test, but I can live without it.


Thanks for getting the docs changes added in.


@miguelportilla No, we don't need to set `validated` or `accepted`, since those fields only have meaning for closed ledgers. See:
https://github.com/ripple/rippled/blob/2f5e04a3b322ca6f2900441cd8da09a1d997d54b/src/ripple/ledger/ReadView.h#L68


Oh, it's no problem, and I learned a little Lua!


done


![image](https://cloud.githubusercontent.com/assets/10685845/9661459/a2088a92-527c-11e5-8f2c-7bd8304195a7.png)

This is now happening after this commit...


As you can see you passed `lolPropertiesTest()` as the function, but you named it `lolcatPropertiesTest()`. Same for Values below


Sure! Tests are a "must have".
In this case there is an easy way to do stress testing:
1. Implement **ThreeStdStacks** using 3 **std::stack**'s.
2. Do some random operations in parallel on **ThreeStacks** and **ThreeStdStacks** (hello, Crazy/Chaos Monkey!)
3. Verify that **top** and **empty** operations yield the same results.


I think this looks pretty good. I'd rather see real templating than the dedented pile of strings here. I'd rather see less jQuery, but it should be fine. Using jQuery to manipulate the DOM makes sense. Things like $.map and jQuery's Promise implementation seem more gratuitous (Array.map exists, for example).

Also, ES6 and React have spoiled me, but we've talked about how it isn't reasonable to have those here.


OK, nice and clean.


I am getting tired of wxWidgets...


No, this function called from rxe_udp_encap_recv callback and the pkt->mask is initialized there.


Not sure if 'SECTION' is still being used.


I am not sure I understand what you are trying to achieve with this commit.


OK


newline between SECTION and LICENSE


I forgot about Array.map--I'll switch to that. Not using jquery's promise gets a little difficult since it's wrapped up with the ajax stuff. I'm open to how to restructure that, though.


Great!


For consistency should `[[elevation]]` be wrapped in quotes too? We quote it over in `paper-button`: https://github.com/PolymerElements/paper-button/blob/master/paper-button.html#L132

LGTM otherwise!


Even @byteandahalf, listen to Senpai.


We need to bind `renderCards` function to `this` so that `this` is pointing to the `Game` component instance inside of `renderCards`. (this is where we see that JS classes are syntactic sugar on top of JS' prototypal nature).

We want to have access to `this` so we can get some of the things React provides such as `setState`, as well as the ability to call any other functions defined on our component off of `this`.

* note that there are other methods to ensure `renderCards` has the correct context, this is just one technique


Checkmarx scan results 03 Sep 2015 17:36 UTC +03:00

High
Medium
Low
Info

New
0
0
0
0

Recurrent
1
0
0
0

Fixed
0
0
0
0

 Open Viewer
Included commits

Commit ID	Owner

8cfede6bc3df42bc8710190e99182599315cb5f2	@dortal

b14508143175c4f19f9438826de043e351e28b6b	@dortal


Formatting


I'm not sure, but you might be able to use ${KERNELVERSION} here, instead of PV. That makes it match with 'uname -r' and other kernel related files in deploy.


@clefranc yes they should, the addition in Marlin/Marlin.h makes sure that current configs dont break.


@martin1cerny this may be WIP but it seems to have broken the normals

![image](https://cloud.githubusercontent.com/assets/923699/9661560/27f09f84-5253-11e5-9fea-2a432a86a857.png)

Left image is 0.2.23-prerelease from develop while Right is after this change


Remove parent is slower than ng-if displays the other input
say if I switch from phone input to email input, I'll first see two inputs:
email: ____
phone:____
then the phone input get removed.
so I hide it first.


Това TODO и другото на 57ми ред някак много си приличат :D


You can remove these type of comments.


why do we need this?


_boundingToMapping.use_count() and _boundingFromMapping.use_count()) are both zero. Thus calling -> isProjectionMapping() segfaults, also wenn mapping is NN, i.e. no projection mapping.


gotta say stuff


Some magic constants are floating around... :)
Try to use some constant, e.g. STACK_BOTTOM.


ship it


+  si x très petit on retourne x


Wtf I had the bool dualWield for a reason


fonction


Agreed, I'll do it.


FourPipeBeamAirTerminal (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1293 of 1294 tests passed)

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


I assume that some error message will be added into the response at line 1197 if the exitCode != 0. Is that correct?


I made the internal version skip the assert because it is used in cuda_newkernel() and the tag that the assert looks for is only added at the end of cuda_newkernel() so it would crash when erroring in the middle.

I can probably rename both functions and use the "internal" one only in _newkernel()


Check: https://github.com/boto/boto/pull/2794 you have to update your local boto installation to support this.
I described this in my pull request: https://github.com/saltstack/salt/pull/21476


test


answerIsYes can only return 2 states according to its name: true and false. So you'll require another function to check for no: answerIsNo. Having 2 functions that basically do the same thing is a code smell as it violates the DRY principle. Therefore I recommend having only one function with slightly different semantics that gives you both in one: getAnswer. Some(true) for answerIsYes, Some(false) for answerIsNo and None for no answer. This way you can always just check for the answer you'd like to have without mixing up 2 methods that do the same or needing to unit test them


No, I would not say that is an advantage of HoTT. The point of the book was
to show how we can use HoTT as a foundation for its *other* advantages, but
still write in the informal style that is standard in mathematics, and this
sort of thing is never notated in ordinary category theory.
On Sep 3, 2015 3:05 AM, "Henry Story" <notifications@github.com> wrote:

> @mikeshulman <https://github.com/mikeshulman> I don't agree. The
> advantage of HoTT is the strong typing and how it makes these types of
> issues very explicit. It requires more work, but you are more certain to
> have got the thing right as a result, which is exactly the argument
> Vladimir Voevodsky used in favour of HoTT.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/mikeshulman/book/commit/62e7478e020953be3c4b830fabc5d0549c382898#commitcomment-13043504>
> .
>


While React provides [lifecycle](https://facebook.github.io/react/docs/component-specs.html#lifecycle-methods) functions we can hook into like `render`, `componentDidMount`, `componentWillReceiveProps`, etc, we can also define our own functions on the component as well.


I agree - very impressive!


Laurent, est-ce que ceci est la solution pour la bogue dans Chrome et IE que le menu mobile (hamburger menu) ne s'ouvre pas sauf en naviguant l'extrême haut de la page?  Dans firefox ça marche bien toujours n'importe comment (14.0x ) mais j'ai tombé sur une ennuyeuse bogue dans Chrome et IE.  Pourquoi ce titre est écrit "fixed the mobmenu ajax files" dont aucun code jQuery ni JavaScript est là dedans.


and bld.env['BUILD_DRIVER_IOAUDIO'] ?  It appears we define that in our build.


Consider retriableTxs


Hi @s1monw,

1.  Does this mean that I will always have to annotate my Failing Test classes as a result of memory leaks detected by Lucenes' `<RandomizedRunner>` with :

    `<@ThreadLeakScope(ThreadLeakScope.Scope.NONE) // Which is "Highly discouraged" >`?

2.  Or is there another work around?

**PS:** currently using `<@ThreadLeakScope(ThreadLeakScope.Scope.NONE)>` on staging and I will like to find an alternative before going live


@oleganza No problem.  I believe we're all in agreement.  Check out pull req #2.  It's been merged:

https://github.com/jgarzik/bip100/pull/2/files


At some point, avocado can be installed on a venv and then the functional tests can run without the basedir hack. This is a nice start though.


Great!


защото целия for e копиран и после малко s///g :P


We could use an apiary-owned domain. The heart of the matter is getting credentials (APIARY_API_KEY) to anyone who runs the tests. Part of my change was to embed credentials in the test script; what would you think of embedding credentials for apiaryclienttest instead of testingapiaryclitestingapiarycli?


No... It is not that easy...
With the help of @ddo I designed the solution :
 - Introduce a ClientProviderProducer interface with a default implementation that reads configuration, annotated with @ImplementedBy.
 - Implement it in test, using embedded ES connection
 - Code a module that @Provides the Test ClientProviderProducer
 - Allow Cassandra James server to take additionnal modules.
 - In tests load the additionnal module for Embedded ElasticSearch.


Arrumar


Remover


Sure, nice.


oder so, super :)


checked!


I think not using jQuery's promise would mean not using their Ajax. It isn't hard to write a small wrapper around the native XHR to use real Promises, but it is more complexity than is probably needed. And then there are some hand wavey things you could do with future APIs and polyfills, like using the Fetch api.


Try to be consistent, in all this cases you should either use exceptions or asserts, not both.
And in this case exception is more appropriate.

Feel the difference:
1. Assert - check for some situation that should never ever happen in your program. It should indicate some breakdown in internal logic of your program after which proceeding further doesn't make sense. For example you calculate distance between two geometric points and it appears to be negative.
2. Exception - you get to the situation that can be reached using some unusual conditions in the environment, e.g. invalid user input or missing connection to web server. In this situations you can catch the error and show the error message to user or send an email to administrator about bad network. Those are usually non-critical errors that can be handled.


`key` is a special type of `prop` that React requires on elements of a list.  This is a unique identifier to help React's VDOM diffing so it can tell if an element has moved in the list or if it is an entirely new element.

`className` is the `prop` for adding classes to a DOM element.  Note that this will only work on divs and React elements that translate directly to DOM elements.

We will look at props in more detail in the next commit.


@BuzzBumbleBee I saw them in Marlin.h, but they're missing in the deltas configurations files.


@clefranc this is correct, you set these after both delta radius and rod lengths in your configuration file i.e.

```
// Center-to-center distance of the holes in the diagonal push rods.
#define DELTA_DIAGONAL_ROD 163.0 // mm

// Trims for the diagonal push rods (small adustments to take out per axis size errror
#define DELTA_DIAGONAL_ROD_TRIM_TOWER_1 0.60 //mm
#define DELTA_DIAGONAL_ROD_TRIM_TOWER_2 -0.50 //mm
#define DELTA_DIAGONAL_ROD_TRIM_TOWER_3 -1.1 //mm
```

I find the best way to calibrate the rod lengths is the following :-

1) Print a circle of 50mm diameter (can be whatever you want)
2) Measure a the circle in the plane of each rod X/Y/Z
3) Calculate errror
4) Process trim from this error


fix issue #15


wow, comments! :D


develop (macumber) - x86_64-Linux-Ubuntu-14.04-clang-3.5: OK (2294 of 2332 tests passed)

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


ok


code looks good :)


@clefranc yeah they are optional configuration (see my comment in marlin dev for example)


haha :D


@marzig76 :+1:


this class is getting quite long.. Can you think of a way to break it into multiple classes? particularly the contest method list sorter is long and repetitive


:) thanks @pranav01
@akhilnarang here lol


When was http://engineering.widen.com/2015/08/27/AWS-Lambda-Runtime-Configuration/ ever a valid URL? The original, AFAIK, contain `/blog/`


There is news tests in `DTLSConnectorTest` about session resumption now :) (commit fcf2739ca1bd480e6ad007c20a86aaf92b8de8c5)


Oh no...
The message was meant for a new user Conde7.  He kept resubmitting people's tests.
See:  http://tests.stockfishchess.org/actions
I should had clarify that...


Might want to update the comments to replace ALSA with io-audio


Having a requirements file (:+1:) will allow for `pip install git+...`.
Or we could abuse [this dark magic](https://caremad.io/2013/07/setup-vs-requirement/#developing-reusable-things-or-how-not-to-repeat-yourself:51559528e9a0774382db1482b1572f0b) (:-1:).


:+1: @dethi


Jennifer Boudreaux username: "jlb151" //same as my student email.


I can't believe it's that hard.
Anyway, I don't see how @ImplementedBy solves anything


Figured there was a better way to do that!


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


Thank you!


Commented out code.


@nrc

>  Can this only occur in END_BLOCK or can you return from any block?

Only in `END_BLOCK`. This is just by convention right now, but I imagine sooner or later it'll be convenient to have known end points.


Haha yeah...

https://jkanime.net/stream/jkmedia/606d9515f52339eefdda527fb7b23a45/6ee0218e84b123c0c84e98310176fdfc/1/66007b3327c3e6f3be931a90239b585b/

Anyway I thought of a better way to fix this.


Non ceci affecte seulement la generation du code HTML et ne devrait pas etre relié a ce bogue. Pourrais-tu oouvrir un Issue pour ce probleme?


Checkmarx scan results 03 Sep 2015 17:50 UTC +03:00

High
Medium
Low
Info

New
0
0
0
0

Recurrent
1
0
0
0

Fixed
0
0
0
0

 Open Viewer
Included commits

Commit ID	Owner

d3d1c0b068aa21a2aa829d5411ca63fda694392a	@dortal

947c939d71ea103f3df5a1a745c829b33afc7302	@dortal


Should we turn on ES7 decorators to do `@connect` ? I can't seem to tell what the status is of this feature.


은정님 폭풍 머징!!!


Wouldn't it make sense to pass buffer size as a parameter to constructor?


well, config file and vmlinux seems to be use KERNEL_VERSION, but Image, zImage which are in deploy folder seems to be using PV, e.g

KERNEL_IMAGE_BASE_NAME ?= "${KERNEL_IMAGETYPE}-${PKGE}-${PKGV}-${PKGR}-${MACHINE}-${DATETIME}"

So, in my deploy folder I am getting:

Image--4.0.0+git0+f8a46972ba-r0-apq8016-sbc-20150831211906.dtb
and the corresponding:
boot-4.0.0+gitAUTOINC+f8a46972ba-r0-dragonboard-410c-20150831211906.img

so i probably just need to change PV by PKGV, no?


Muito bom Ricardo.


If this condition evaluates to false, `run` is going to be executed nevertheless, right? This check appears useless. Is it what you meant?


this commit looks funky to me...


well it's everywhere else.. so i will keep it ..


These test files aren't doing anything.  Should they be in a separate patch with test cases filled out?


Need to remove the mClockView. at line 436


The issue with the Linux build turns out to be unrelated to the bindings: it's simply a linking error.  You'd have to supply `-custom` to `ocamlc`, otherwise it will attempt to link with the shared library version.  Since the correct one is obviously not in your LD_LIBRARY_PATH, it will look it up in the system default (wherever e.g. OPAM puts packages) and find the old, broken one.

Concerning Windows: it's possible that the issue is the same as above.  It's interesting that `ocaml` works on Linux when supplied with the right include path.  Maybe it also looks for shared libraries there then, but doesn't do that on Windows.

I'll make a new release, which will surely be a great improvement to everyone else.  If the Windows problem persists, I'd appreciate it if someone could come up with a solution, because I don't have access to any Windows installation right now.


Saw this when resolving a merge. `stepDefaultOptions` is deprecated. David removed it when upgrading to Symfony 2.7 (see @7a9a64c2c5f9fa3d91f8dd05f585ae17986df008). Defaults should be added to the `configureOptions` method. Same for all form types.


ugh...the platform specific "bugs" heavily suck... i'll revert it. thx for the info


also remove the mClockView. on line 428


@BuzzBumbleBee Can you give me a link to your comment, so I can understand why these parameters are not defined in deltas configurations files.


ok, j'ouvrirai un issue quand je comprend mieux le problème, je roule présentement quelques tests, mon dernier test me dit que le problème pourrait être dû à mon code ou un conflit entre wetboew et mon code.  Firefox marche toujours bien peu importe.  C'est chrome et IE que me cause des ennuies.

...à suivre


Hm, do we need to put "Armrest" here again? We're already scoped under "Armrest". Writing Azure::Armrest::Exception is easier, and looks nicer.


Explaining how to register additional test-only EPackages is fine, but please without those confusing references to your latest experiences. ;-) The bit about registering extra ecore models should go where we describe the 'import' ecore mechanism (and it should not have the comment about not using 'init').


The change to editlist.php looks to be wrong. Now the checkbox is checked when the list is not active.
What was the reason for using empty()? From what I can see in the code $list['active']  always exists, so empty() isn't then really any different from what was there before.


Ah, my bad. I thought the original did not include that. Looking back at our [post to twitter](https://twitter.com/WidenDev/status/637337161034006528) I can see that it definitely did. :+1:


More to the point: what doesn't it do?!!!!


develop (macumber) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

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


Same here, we're already scoped under "Azure". I guess I feel that it's redundant.


go fmt


@BuzzBumbleBee Do you mind if I create a PR with the trim #defines in the deltas configuration files?


Cool lol
Why on such an old random commit though haha


What is the use ?


TeamCity Xbim :: Xbim Geometry :: XbimGeometry [Build 47](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=143&buildTypeId=Xbim_XbimGeometry_XbimGeometry) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:40:24


TeamCity Xbim :: Xbim Web UI :: Xbim Web UI [Build 9](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=144&buildTypeId=Xbim_XbimWebUi_XbimWebUi) is now running


TeamCity Xbim :: Xbim Web UI :: Xbim Web UI [Build 9](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=144&buildTypeId=Xbim_XbimWebUi_XbimWebUi) outcome was **FAILURE**
Summary: Cannot start build runner Build time: 00:00:09


Well maybe not better, similiar...


The reference here addresses a branch I started. Thanks.


Go for it.

The logic in my mind was that a perfect delta (if there is such a thing) would not need these trims defined at all. So by default i didnt add any ;)


Minor quibble, but I think "cause_exception" can just be reduced to "cause".


could you explain how to use your universal target. I can't move the sources into my own project because they are always with mistakes and it is independent from the target and simulator/device.


Nice Job!


Hi Hồng,
Sr A review trể cái này nha.
Phần implement thì ok rồi, tuy nhiên còn 1 chỗ chưa clear
1. Nếu người dùng tự viết và tự run 1 đoạn ajax để gọi hàm saveNote trong HomeController. Thì nếu có password hay không thì cũng override có đúng không?


We still want to limit our ext to these "english speaking" countries.


Could do it's stage 1 (proposal) .  https://github.com/wycats/javascript-decorators + https://babeljs.io/docs/usage/experimental/


Cool, it was about time to eat some :cake:


yeah


Totally supportive of changing syntax when appropriate. Rock on, vega-lite team!