+  - automatic metrics for specified function in backend modules [#412]((https://github.com/esl/MongooseIM/pull/412)

=> remove one opening parenthesis: "[#412]((https://github..."


@pmitros thanks. Could you please create a PR with the commit so it can go through reviews?


an* error message


@RKJS689 please remove any commented out code that you're not using


No GitHubPage.groovy teve algum problema de codificação. que o ponto mudou ali, isso vai fazer o teste falhar.


Thanks Peter. I'll fix it next push. And thanks for the hint!


same error as line 47


For future consideration -- the validity periods feels like they should be configurable, especially if make negative tests for these.


kenapa semua bikinny dsini wakakaka
cma gavan ama ricky yng bkinny bner pke branch ama pull request :v


Prefer one line comments to look like this `// Initial page startup`. Comments is good, but not necessary for code that speak for it self. Don't want your code to be flooded with comment. In the case of `window.onload = () => {` . We know it is the `Initial page startup` :)


Should be determined by the screen size


forgetting to define EMBEDLY_KEY raises an error. This is expected behaviour in previous wagtail versions. However, we now want to raise an error if ``WAGTAILEMBEDS_EMBEDLY_KEY`` is not set with no ``EMBEDLY_KEY`` to fall back on (but still telling the developer to set ``WAGTAILEMBEDS_EMBEDLY_KEY``).

Something maybe this might work:

```python
    # Get embedly key
    if key is None:
        try:
            key = settings.WAGTAILEMBEDS_EMBEDLY_KEY
        except AttributeError as e:
            try:
                key = settings.EMBEDLY_KEY
                warnings.warn(
                    "EMBEDLY_KEY has been deprecated - use WAGTAILEMBEDS_EMBEDLY_KEY instead",
                    RemovedInWagtail13Warning)
            except AttributeError:
                # Reraise original exception from when we tried WAGTAILEMBEDS_EMBEDLY_KEY
                six.reraise(e)
```


Könnte sehr erfolgreich werden, gerade in Kombination mit deiner Welt / dem Buch. Ich bin gespannt!


Oops, thanks for the warning, added by mistake.


It does not actually fix #259 and #245 The commit was originally in another github repository and those numbers referenced the PR on that repository. When the commit ended in odoo repository, github automatically tried to match the numbers in the commit message with the PR from this repository which leads to an error.


LGTM


> except for the hardware/software mode trigger f9 that can effect gsdx settings. But I guess nobody will die if he has to look to the end to be sure which mode he is currently using.

Agreed on both. Also, currently the HW/SW is part of the "section" which GSdx provides as a single unit - which includes the mode, resolution and deinterlace mode, so for now, I can't move just the HW/SW mode to a different place without moving the entire GSdx "unit".

> So maybe it is correct as it is. I would rather move savestates to the log console though.

The slot is already displayed at the console. So your suggestion is to completely remove it from the title?


mod_offline_stub module to prevent service-unavailabe errors #429

=> service-unavailable, with an "l"


But not in a single statement. The loop is per statement.


The tail command is only for container not to exit, and not to accces log. Indeed `qserv-start.sh` returns 0 and then `docker run` exit, so qserv stop. Adding `tail -F` prevent this unwanted behaviour (We could also wait for xrootd process PID).

Are you ok with that?


I don't think there's any reason to store the drmModeModeInfo. Just add the required fields to Videomode, and fill in the data from drmModeModeInfo in the constructor.

I think the same should be done for the crtc, encoder, etc. also, but that's a different topic.


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


Thanks for the hint.

Use case is described at the new documentation available at
https://manual.limesurvey.org/QS:CSS_Class

I will also add this to all question type documentation pages.

Best regards
Marcel

Am 07.10.2015 um 11:09 schrieb olleharstedt:
>
> What's the use-case for this feature?
>
> New features should be documented somewhere, no?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/LimeSurvey/LimeSurvey/commit/b9536e41ad325ddc9e697325f78b2bc60cb350b4#commitcomment-13633768>.
>


Cierra issue https://github.com/InspectorIncognito/androidApp/issues/26


If only they were all that easy :)

Thanks for finding.


Interesting issue here, but I don't have a solution.  We now have a dependency on the name of the resource endpoint and the name of the type for the certificate resource, baked into common code that shouldn't have knowledge of them.  If someone refactors that resource type name, it could take awhile to discover why CRL started failing. I wonder if this knowledge can be "pushed" in from the Bridge somehow.  Ideas welcome, but don't block the PR on it.


Don't forget `pfs_dispatch64.cc` as well.


thanks for the tips but i am not a Windows user, i run it on Debian


grrrr thanks


> I guess I should've make that change earlier, since it's sold out.

I was wondering how it would handle that case - I guess it's failing somewhere, but it's leaving the desired text (which is now what's in the HTML itself: "Get on the waitlist") in place, so we're all good.


type parameter is unused


Why public?


Come on man this is random choose our goal to be specific :D


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


This is a public project and it needs also to be fully compatible with pure ruby. Let's remove Rollbar and replace with some kind of exception block


assertNotIn would be better.


Looks good, updated.
Thank you.


Thanks for the updates!
RFC2616 is obsolete, but at times, it provides useful context for the newer RFCs' phrasing.


Alright, thanks.


 #[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


This is the difference:

![schermata 2015-10-07 alle 15 26 43](https://cloud.githubusercontent.com/assets/779534/10338878/b38875a6-6d08-11e5-9280-b6723035e967.png)

The CollectionDecorator of AutoPresenter check that is a Collection and, if not, it doesn't decorate model's attributes: https://github.com/laravel-auto-presenter/laravel-auto-presenter/blob/42c1dac02ac88a21cdd015cdf6d940898b4b7b97/src/Decorators/CollectionDecorator.php#L18


According to web inspector it wasn't applying, so not sure if it's within that class.

Even just on the img tag should be fine.


ia_na1 is not in camelCase ... and I think "camelCase with first lowercase letter" naming for variables should be respected


No problem, you're welcome!


Id keep first letter of local variables lowercase


A better name than "active" might be "supported".


Yes, in a single statement:

```diff
@@ -618,16 +613,18 @@ class FileLoader(TestLoader):
                     continue

                 if test_import:
-                    base_ids = [base.id for base in statement.bases]
+                    base_ids = [base.id for base in statement.bases
+                                if hasattr(base, 'id')]
                     # Looking for a 'class FooTest(Test):'
                     if test_import_name in base_ids:
                         functions = [st.name for st in statement.body if
                                      isinstance(st, ast.FunctionDef) and
                                      st.name.startswith('test')]
                         result[statement.name] = functions
+                        continue

                 # Looking for a 'class FooTest(avocado.Test):'
-                elif mod_import:
+                if mod_import:
                     for base in statement.bases:
                         module = base.value.id
                         klass = base.attr

```

to test it use:
```python
from avocado import Test
import avocado
import fmaslkfdsaf

class First(Test):
    """
    :avocado: disable
    """
    def test(self):
        class Third(Test):
            """
            :avocado: enable
            """
            def test_2(self):
                pass
        class Fourth(Second):
            """
            :avocado: enable
            """
            def test_3(self):
                pass
        pass
    # Looking for a 'class FooTest(avocado.Test):'
-                elif mod_import:
+                if mod_import:
                     for base in statement.bases:
                         module = base.value.id
                         klass = base.attr

```

to test it use:
```python
from avocado import Test
import avocado

class Second(avocado.Test):
    def test_1(self):
        pass
```


Fixed, thanks!


<!DOCTYPE html>

<title>
Events Photographer and Video Recorder
</title>

<meta name="description" content="Events Photographer.
We are who you need for your events">

<meta name="Keywords" content="Hochzeit Photos,
Brauut Paar Photos">

 IBM-SOFT Pro

---Production---

     IBM-SOFT Pro Production  Photography offers distinctive

 portrait photography services for those who want to find

 outstanding "Casual Lifestyle Photography".

If you are looking for family portraits, senior portraits,

birthdays, anniversaries, engagements & weddings, showcase your

home for sale, business & products, we will "Catch The Moment",

preserving memories at events or even a simple walk in the

park. We take the time to personalize and customize your

photography with just the right setting and position.

We have the tools and talent to produce pictures to your

satisfaction. After working with  IBM-SOFT Pro Production

Photography, you will have images that reflect that special

personality, emotion and character.

 Leistung

Vorname
Name
Studiengang
MatrikulNummer

 Igor
  Master
  Informatik
  11234

  Marcell
  Kirby
  Medieninformatik
  10324

  Thomas
  Smits
  Informatik
  11111

<form action="demo_form.asp">
  <input type="checkbox" name="vehicle" value="Bike"> I have a bike

  <input type="checkbox" name="vehicle" value="Car" checked> I have a car

  <input type="submit" value="Submit">
</form>

Contact us for that special moment.

 ibmsoft@yahoo.fr

 New Price  Old Price

Members of:

Justard Dollar

 Welcome to   IBM-SOFT Pro  Production

 IBM-SOFT Pro


`PER_LINUX_32BIT` is not the same as `PER_LINUX32`. Do you know the difference Ben? I couldn't find a useful doc from quick googling.


I could not understand the meaning of the first part of the sentence.


TeamCity Xbim :: Xbim Exchange :: XbimExchange [Build 51](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=264&buildTypeId=Xbim_XbimExchange_XbimExchange) is now running


residue should be set to 0 otherwise who knows what value it will initially have.


Thanks for the notion of the error and the proposed fix! Clearly, if `V` is initialized as identity matrix and if `t_keep != n_dp1`, then only the first several points are used for the first calculation of `W` (I admit I always wondered why this version of the code gave different (= worse) results than an independent implementation using covariance matrices explicilty instead, turns out it wasn't the explicite use of covariance matrices ...)

Accordingly, for the array t_keep I agree with the updated definition. For s_keep, however, we might start with a reduced set of spatial filters, because W is not initialized as identity matrix but is a properly derived filter matrix.

I suggest:

    s_keep = _np.hstack([
        [int(s_keep)] * 5,
        _np.linspace(6, n_ch1-1, num_iter-5).astype(int)
        ])[::-1]

Thanks for your help (it's good that people indeed notice the effort you put into sharing this code!)


Looking at the generated code, it definitely leaks.

It looks like using a boost::shared_ptr\<std::vector\<int> > it should behave the same way and not leak.


Can't you use sol_buffer_get_slice here and them you won't need to re_init it later? And you won't need to set all memory to '\0' using calloc or memset, or even worry about terminating the string with null.


TeamCity Xbim :: Xbim Exchange :: XbimExchange [Build 51](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=264&buildTypeId=Xbim_XbimExchange_XbimExchange) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:01:12


messageType parameter missed


Looks good, just a couple cosmetic issues regarding variable naming + 2 missed parameters in utility methods


Oh, we also need to split the `mod_import_name`...


Nit/Optional: maybe add some comments why 64-bits for certs but 7-bits for CRL, etc.

Question: is it possible for this method to be re-entered if tests run concurrently?


Forgot these?
* DB cleanup after node death
* Memory footprint optimisations
* Supported XEPs are now documented
* Dialyzer fixes & additions
* Experimental Docker image
?


This isn't correct -- it shows "1.8.4" as the previous LTS. See https://github.com/django/djangoproject.com/commit/313eb71d7051f4b51107850577a6ef25d25d9257#diff-a6184808754cab4aba1e4ee1be3577f5R28 for the version I had written prior to reverting.


Since every release is deleted by one function in Releases.php, why don't we just left join that table on guid instead of modifying the triggers?


What is happening with this empty catch?  When does an exception occur?  Is it worth reporting, at least via a Trace or Console?


On avait pas parlé de constructeur sans argument ? Comme ça on peut faire un instantiate sans récupérer le constructeur avec arg. C'est d'ailleurs pour ça qu'on avait le setFile.


The default prompt has a question mark followed by a period.


@djberg96

Why this change?


I might add a `zone_position` attribute to be consistent with Hearthstone. Right now that logic is in kettle.


this change looks fine to me.


I am a nice comment


Maybe, but I'm not sure about not ``memset``-ing it (there might be cases where we end up with trash).


Because the first element is now the subscription_id.


That's why I asked the team to review the changelog :)
Feel free to edit the file and push your changes to my branch :)


não encontrei erro


Si très juste, un oubli de ma part


I'll have to update the documentation of the format, I missed that.


Eu mesmo cometi um erro aqui. Esqueci de editar essa parte "CreateHarvestSolicitationTestDataAndOperations''. Teria que ser ''SolicitacaoColetaTestDataAndOperations'', pois mudei depois o nome, e esqueci de alterar nos steps.


Neato :+1:


Sure, if by "merge" you mean "cherry-pick" :-)


I don't think you even need the $success variable. I think you can just do:

```php
if (commerce_payment_example_simulate_failure($donation)) {
   ... do the failure stuff
}
else {
  ... do the success stuff
}
```


This is an @ToDo, not what the program is actually doing ;)


But shouldn't you also execute it? ;p


This is required because this file is loaded on tools-clean


That's one way of doing it but why do we get the recursion in the first place?


Shouldn't need to do this at all?
The point is that IS_JSONS3() already has the db-specifics encapsulated inside it...so no need to do any db-weirdness here (it's a little more complex than this simple test & no need to repeat the test - DRY/encapsulate within IS_JSONS3()


== ?
Just one =


Top !


Need more flair...

![More flair](https://s-media-cache-ak0.pinimg.com/236x/bc/37/64/bc37642d484dacb6984a7d83056940c3.jpg)


Need to add more context like the adapter name and tenant
Else we don't know which adapter is doing this


should merge


 > I think I'm on recent KTp stack, but in strange fact, this is not
required for my setup.

It should, at least on master. See line 125 of:

https://quickgit.kde.org/?p=ktp-common-internals.git&a=blob&h=e498724fc5f88ff220da15eb1d2a393bc1d54cca&hb=bec14805a01ab6a63d1f80239844a81fee41683d&f=KTp%2Fcontact.cpp


How did you derive the 600ms vs 6s? Also, this comment should say exactly what the expected default settings are, or it's likely to become incorrect in the future.


Why "%s" % style ?
json.dumps() would be the preferred solution to convert to JSON string


I have canceled my changes in read_options.cc. I type git pull, before pushing my changes, but I am not sure why read_options was changed. Recently, I have transferred to a new mac book and may be git config options was not properly set. I hope everything is okay now.


Remember #248 ?


But that's ok, because ViTables is our data viewer, where we even provide a plugin for. To me that's a valid requirenment. To use pybar without ViTables is difficult.


There's an annoying issue with this.  Any time the mouse moves over the text area, it scrolls the window to the bottom.  Fixing...


Talvez no CreateHarvestSolicitationTestDataAndOperations e na Page tu devesse ter criado os métodos de enviar e-mail e elementos visuais (e o que precisasse mesmo que não tivesse funcionando totalmente) só para completar o teste, porque acho que vai ter que criar isso no model ainda, certo? Mas pelo que eu vi só isso mesmo :D


If calc_only == true *col will always be 0 and return will always be CUR_POS. Why are you using it?


I raised https://mambucom.jira.com/browse/MBU-10590, feel free to modify or comment on it in Jira.


Done in https://github.com/NixOS/nixpkgs/commit/b7d0730f66fa15be8ec09508100be112459dfe84 and https://github.com/NixOS/nixpkgs/commit/8db98ceb010e550ebc3a6cae475bf7723c691c37


Hey guys it  the requirement study due date is closing in on us. Are we still meeting up? @ecomitz
@MatthewM39
@MilesBenetDyson


お、早速やってますね！
ただ、共同で開発をするときに直接masterにcommit/pushをすると
同時に更新したときにmergeが大変になります。

そのときのための commit/merge ルールがあるのですが、
slackで紹介した github flowをお勧めします。試してみてください。


Question (maybe an invitation for comments in the code): so the programming model here is that the PUT can specify in the name/value pairs the thumbprint of a cert to revoke before creating the CRL Uri? Is there a chance for an exception if it has been revoked by another test first?


l'air de rien c'était un gros morceau !

	Gil DELUERMOZ
Chargé de mission développement web et bases de données

Parc national des Écrins
Tél : +33 (0)4 92 21 08 49
www.ecrins-parcnational.fr
----- Mail original -----

De: "Camille Monchicourt" <notifications@github.com>
À: "PnEcrins/Police" <Police@noreply.github.com>
Cc: "gildeluermoz" <gil.deluermoz@ecrins-parcnational.fr>
Envoyé: Mercredi 7 Octobre 2015 15:45:14
Objet: Re: [Police] close #2 - lien recherche export xls (9417e59)

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


@aiminy this commit reverts changes you made to affiliated sites because this should go in the yambase repo


Yeah, great!


You really commit!


I don't see the use of outputting the a string representation of the neutral element instead of the neutral element itself. Also it should suffice to set this->e while testing for the existence.


@carlosagsmendes thanks I've added https://github.com/systemjs/builder/commit/c798beaf8a98bf220e4e767cf40bf319b4e49614 let me know if that helps.


Great suggestions! I'll do them right away :-)


1st line commit


While this passes the test, there is a way to build the string without using `replaceCharactersInRange:withString:`


Hi @tkaitchuck

I think that you forgot to update the comments in the MapperPipeline class in order to add the base_path argument after the list of args.

Thank you!


Perfect, thanks!


thanks! :smile:


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


@eneim I have a few more questions. Could you plesa give me an answer on that?

1. When I remove items from the list do I just have to call:

  ```
                serviceCardDtos.remove(0);
                arrayAdapter.notifyDataSetChanged();
 ````
2. When I change the lists do I have to call

    ```
   mFlingView.refresh();
   arrayAdapter.notifyDataSetChanged();
   ```
  or
    ```
   arrayAdapter.notifyDataSetChanged();
   mFlingView.refresh();
   ```
 or only
    ```
   mFlingView.refresh();
   ```


I avoid multi-line logs when it's possible. However, the config is so big, and it's convenient to read such logs using text viewer.
Grepping multi-line logs is not a problem -- simple perl one-liner will solve the problem.


I know, but all the existing documentation was not requiring it. Also the command given in step-by-step guide  ("pip install <lots of packages> <link to vitables>") didn't work. Thats why I removed it from the requirements.

In my opinion, a working documentation is necessary before updating the requirements.


I think this will fail for buckets that have a period in the name.


Shouldn't this check be `argv[i].indexOf('--app=') === 0`? What if a user does `electron blahblah--app=path/to/app`? That should fail.

Also, how does this work with paths with spaces in them? (`/Applications/Dev Apps/Electron/....`)


You've mastered using string ranges, I'd like to see you use some of the other methods on NSString. We'll take a look at the documentation browser today if you don't already know about it.


Yep, misprinted.


What did you connect to this serial port?


Mesma coisa que Rafael tinha me mostrado, no meu na página GithubPage.groovy a codificação foi mudada aí pode dar erro aí :D aconteceu exatamente a mesma coisa comigo. Não tenho nada a criticar tudo certo.


Note: it looks like this (or a related change) broke other consensus tests:

https://ci.omni.foundation/job/omni-mainnet-consensus/213/

And for some reason this build appears to stall:

https://ci.omni.foundation/job/omni-mainnet-consensus/214/


Makes sense.


My bad, the second ``calc_only`` if should be inside the row checking if. ``CUR_POS`` will be affected because the row changes.


Same comment as above. We'll talk about using string formats for building strings instead of replacing characters in a given range.


This will apparently NPE if you don't set brokerSecurity.. Where did you set the default?


Just for future reference: I would like to avoid this kind of binpack, if one of us finds an option for that.


please leave `src/javascripts/__tests__/exclamify.test.js` and `src/javascripts/exclaimify.js`


Missing trailing #. Should be <http://www.w3.org/2001/XMLSchema#>


IIRC, the reason at the time was that the flag includes things other than just cpus - i.e., setting "whole_system" was required in order to get other system details. If that was a misunderstanding and the only thing it does is bring in the offline/not allowed cpus, then we shouldn't set it - I can't think of any use for that information.


I love the explicitness of this method, but you don't need a conditional here.


For XML schema types, add # to namespace or even better, use namespace prefix defined on line 34.


Same as above.


Ahem, this is about ps-tuebingen/handin-config#5.


We don't use boost anymore. And, as I already said, ```std::shared_ptr<std::vector<int>>``` gives an
```error : Syntax error in input(3).```


Question only: if this method is re-entered after the lock is released but before the response is prepared, is it possible for s_createdCertsBy* dictionaries to be different than what they were inside the lock?  It might be safer to prepare the response under the same lock to prevent hard to diagnose issues if this is a possibility.


@ldoktor Travis CI will be there to check your assumptions, so there's an extra safety net.


This is already defined in this file.


Forgot to add that I've added std:: to the template and boost:: also yields this error.


Is there already a good definition that can replace [20]?


You'd better use ``"``quotes on your ``echo`` arguments.


Done!


Just `img` may become quite annoying if (hypothetically) someday we'll add some images w/o wanting them being limited and then you're forced to solve a problem you don't remember of at all (i.e. "doh! why *all* images were set up this way?" :), so I think some moderate specialization never harms.


will be fixed soon :wink:


TeamCity Dirigo Edge :: Pull Request Smoke Tests [Build 87](http://teamcity/viewLog.html?buildId=1238&buildTypeId=DirigoEdge_PullRequestFullChain) outcome was **FAILURE**
Summary: Compilation error: DirigoEdge.sln Build time: 00:00:06


@tampakis Yes, please do so!  We are currently doing some link checking in the catalog but have to hunt for them.  If you have a targeted list of known bad links that would be great!


why is there that tmp.txt file?


This variable is used but has not been renamed: https://github.com/lewfish/raster-foundry/blob/b7113316e3c7c14ba8d9046420061d76f7143665/src/rf/rf/settings/base.py#L282


Great work here. Is there another way you can solve this without using compound logic statements in the if clauses?


Done

From: Vineet Gupta [mailto:notifications@github.com]
Sent: Wednesday, October 07, 2015 9:34 AM
To: EZchip/linux
Cc: Noam Camus
Subject: Re: [linux] tracing: Fix for non-continuous cpu ids (c58ee43)

IMO this patch can posted to mailing list seperately - now as well !

—
Reply to this email directly or view it on GitHub<https://github.com/EZchip/linux/commit/c58ee43eb1dd871146deca401d3fdbf46292d57d#commitcomment-13631502>.


You are probably right, that's quick fix code for my personal use. Please check it


@astrofrog You could refer to it here https://github.com/vispy/vispy/tree/master/vispy/visuals/transforms
It seems the last update of this module is 3 months ago and they really did some modification to `MatrixTransform ` so I am not sure if your version is older than it or not.

This also reminds us again of the about different version of Vispy problem, any advice about it ?


No problem. We will let you know when the migration is done so you can check that everything's ok.


Why not move it into the ansible config?


I got this error in analytics: Uncaught TypeError: Cannot read property 'moves' of undefined at file:///android_asset/www/app.js [6486, 10]

Is it related as `data.game` is now undefined?


Than the documentation should be updated, since documentation followes code and not vice versa... ;-)


Actually, it is already there. https://github.com/lewfish/raster-foundry/blob/b7113316e3c7c14ba8d9046420061d76f7143665/deployment/ansible/group_vars/all#L4


Oh, that definitely shouldn't be there. Oops.


Create function do to the getRequest. The function should return success or error. If Error, the user should be notified that the request has failed.


Yes. But that might be my personal preference. In principle the same is valid for other elements as limiter and deinterlacing mode as well. I have the feeling that quasi static information belongs to the console and not to the title bar where only frequent changing information can be displayed in-place.

I would actually only show the gsdx version (for troubleshooting), fps counter and cpu times for threads in the titlebar and move everything else into the console and preferably show it (not implemented in gsdx) as well as HUD element on the screen on change events. If you like you can have a look into zerogs. Titlebar is quite clean. All quasi-static information is in the console and as HUD element available.


> Using out parameters rather than return value makes your code less clear for a reader.

But that's just plain not true.


I presume this is verbatim from LCA, correct?
Is .txt the proper file extension for this (or do we even have a choice)?
Do any of the other repo's have a pattern for this already (e.g. the name of the file, its location, etc.)?
Should we link to this page from the README?


You forget to pass the object to the `$this->admin->isGranted`
Fixed here : https://github.com/sonata-project/SonataAdminBundle/pull/3343


Indeed. It seems that PER_LINUX32 is for arm processors. I'll remove
it, and just have the previous flag PER_LINUX.

On Wed, Oct 7, 2015 at 9:37 AM, Patrick Donnelly
<notifications@github.com> wrote:
> PER_LINUX_32BIT is not the same as PER_LINUX32. Do you know the difference
> Ben? I couldn't find a useful doc from quick googling.
>
> —
> Reply to this email directly or view it on GitHub.


Better idea: Search by Series Title and another info instead of Id.


but a missing vitables is not breaking anything. Documentation was clearly broken.

what is sphinx for?


All these scripts lack license preamble


Nit: Probably want to remove the BeforeBuild message, or if necessary to keep it, remove $$$.


btw conda delivers mock and sphinx. no need to do pip install.


That comes from the view, that the user really just implement the Element.cpp, and then compile and run the application and then just use the command line. Here we need a string getE()

We could also provide this as a library, where the user implement main.cpp. That would require more advanced users, but they can do more with the library, in this case getE() should return a reference to an ElementWrapper


Close #18


This is just a precaution measure because downtime interval can only be set
while migration is running so I wanted to give some time for migration
process to start and make sure it will catch it during its run

On Oct 7, 2015 11:02 AM, "Dejan Muhamedagic" <notifications@github.com>
wrote:
>
> What is this sleep for?
>
> —
> Reply to this email directly or view it on GitHub.


unused variable


Sphinx is needed for ViTables. I tested the pip command and it was working. Where did it fail?


Check the style of these c files, too.


Linux machine. copy&paste didn't worked.


This seems a bit excessive.


Figures; I should have thought of that.


if you don't want to recreate this for every test, you could just create it once in setup


Instead of changing the interface here, you could use the SENS_BOARD_ROT param in QGCS and rotate the imu as required.


Note: The logs are written to system database even if OpenMappedContext set to a valid db name.  It wasn't like that 2 weeks ago. Can't tell why..


shouldn't we be waiting for this to complete?


see my comment about waiting for this to be complete


of course you are right. fixed it


On 07/10/15 14:21, Martin Raifer wrote:
> @/Globale ID/-Änderungen: Müssen wir jetzt in OSM die ganzen
> entsprechenden |ref:IFOPT| tags updaten, oder?

Hi!

Gute Frage - am besten auf talk-at fragen?

lg, Michi


Yes, it will NPE.  I'll fix that and push -f.


Snapshot: https://oss.sonatype.org/content/repositories/snapshots/com/mandrillapp/wrapper/lutung/lutung/0.0.6-SNAPSHOT/

release coming tonite.


Also, if you need to wait for both the cache volume removed events and the purgecache stuff to complete you can do

yield [purgeCache(worker, cacheName), waitForEvent(worker, 'cache volume removed')]


This wraps the native Android ViewPager which is a container that allows
to flip left and right between child views. A typical thing you can build with
this is e.g. a horizontally scrolling gallery.

Long term, we might want to unify this with `<ScrollView paginated={true}>`
which works on iOS thanks the the native iOS ScrollView having support
for pagination.

A proposal for a unified API is can be found under [Knows Issues](https://facebook.github.io/react-native/docs/known-issues.html#platform-parity) in the docs.


The debian package produced by authn-ldap should already include the dependency gems.


ok my fault, now it works. I will revert.


@devbharat True, thanks!


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


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


Works well, good job :+1:


Just as an added check, I would probably set some boolean to say that this purge event happened, and then assert that in the test to make sure that "task run" ran and the purge event happened.  For issues like when the worker ends unexpectedly and then task run never got called, and since the task didn't run the directory you're checking might not exist.  I don't know, might be paranoia but seems like a good check.


no uczę się zabawy z gitem-githubem-pullrequestami
- sorki za takie śmieciowe commity - poprawię się w przyszłości :)


This commit breaks many things

For example in async.waterfall callback
- forces developer to extend Error,
- does not permit returning multiple result from last task

```js
async.waterfall([
    function(next) {
        next(new CustomErrorThatDoesNotExtendError(), 'one', 'two')
    }
], function(e:CustomErrorThatDoesNotExtendError, a, b) {
///
})
```


We're not renaming every function that has a prime in the name. The alternative fix is to put the __IMPOSSIBLE__ on the next line.


@vilchik-elena hm..I see what you mean. When using ``amespaceName.name().text()`` it means that we want the "unqualified" name that why it is separated from the namspaces. Also the interface also have [NamespaceTree#fullName()](https://github.com/SonarCommunity/sonar-php/blob/master/php-frontend/src/main/java/org/sonar/plugins/php/api/tree/declaration/NamespaceNameTree.java#L40) which return the "fully qualified class name" so maybe in this case it might be a documentation issue? WDY?


It seems like it should be possible to write the license text directly to the file, rather than to an intermediate buffer (i.e. by not using the `file` function defined in this module).


Whoops! That was probably my fault, must've missed it in the manual conflict fix.


e 的类型就是 string 不是什么 object, 而且数据内容就是 json 格式的。应该是 binding.node 那部分抛出的错误都是这种格式。

> On Sep 30, 2015, at 4:01 PM, 张云龙 <notifications@github.com> wrote:
>
> @2betop <https://github.com/2betop> 这里不应该JSON.parse(e)吧
>
> —
> Reply to this email directly or view it on GitHub <https://github.com/fex-team/fis-parser-node-sass/commit/bbd0005ff2bbffbd7d3c20ee98722cebd72b153b#commitcomment-13510817>.
>


You're inheriting from cisco_vlan, of which most of the parent methods should be re-useable here. Why do you need to rewrite them here?


Other way would be to modify the .sdf file and rotate the IMU on the physical model there.


Lol


Perfect!


It seems we don't even need the doPrivileged() as we expect callers to have sufficient permissions.


The code added here looks good. However, it can be made easier for a reviewer to read.

Specifically, separating out the renaming/refactoring of things from the adding of new functionality.

The `This commit also includes` bit in your commit message is a good way to spot that you might want to do this.


Trocado Apenas para que Algum colega de classe mal intencionado venha querer a usar o meu Código.


Oh, sorry U_U. That was a crazy merge, I won't ever collect such a big PR :(


might be useful to explain what “scripts” are at this point


Indeed. I'll fix and add a test.


Indeed.


### 相机应用说明
![](http://ww3.sinaimg.cn/bmiddle/00679RpAgw1ewswxnd1htg30a006ohdt.gif)
----------
###用到的类库
  photoview（可以将图片按手势放大缩小的类库,类似微博的图片） https://github.com/chrisbanes/PhotoView
  overscrollview(完全重写了安卓的scrollview，我改了一下手势监听事件，因为要和水平滑动listview共用) https://github.com/EverythingMe/OverScrollView
  swipelistview（可以实现各种左划右划，不过比较复杂，简单点可以用github的swipemenulistview）https://github.com/47deg/android-swipelistview
   还有个豌豆荚的广告sdk就不说了


Regarding your WIP comment:  if you're looking for early feedback on your coding approach that's fine, but please be aware that we won't merge any WIP code. Thanks.


@devbharat Have you got the IRIS flying well? Can you try and setup a mission and see if it works?


copy edit suggestion: …to a module


i theory, where text has been changed, that should be an improvement, but maybe that's not always the case.

> On Oct 7, 2015, at 06:35, Andrei Neculau <notifications@github.com> wrote:
> Thanks for the updates!
> RFC2616 is obsolete, but at times, it provides useful context for the newer RFCs' phrasing.
>


Updated with a more "from the start" explanation. (Latest commit: https://github.com/hoodiehq/hoodie-css/blob/006f3090204371f0cd5925e771cc7bfb6a70d2c3/DEVELOPMENT.md)


more than? :)


添加类库


You have for loops down, as a challenge can you do this with a single while loop?


It seems there is a mix of xmc-2go and xmc1100-bk boards:
- boards/xmc1100-bk/include/board.h: This describes the LEDs of xmc-2go


Die Idee finde ich mega gut :P


“we run the command from ” -> maybe more like “the command from predev:sass gets run automatically for us”, just to make sure that we don’t have to run the pre-task ourselves.


The hurrier I go, the behinder I get


Ah, I must have told @metamatik it wasn't needed back then. I just assumed it was compatible because of this reference to six. Leave it there.


Should plafonds really be `round`ed rather than `ciel`ed or `floor`ed?


TeamCity Dirigo Edge :: Pull Request Smoke Tests [Build 88](http://teamcity/viewLog.html?buildId=1244&buildTypeId=DirigoEdge_PullRequestFullChain) outcome was **SUCCESS**
Summary: Tests passed: 4 Build time: 00:00:44


I was thinking to let the user to change this value in runtime. Sometimes depending on the user's connection, it will process slower or faster each batch...


Nice one.


You should return a copy of this array. Returning mutable variants is generally bad practice.


s/publish/develop and publish/?


Can you explain better what the change in CMakeLists.txt does?


@asmecher Thanks!


Have you been able to run the SIFO tests on this branch? Since SIFO doesn't follow PSR-0/PSR-4 for namespaces, composer autoload doesn't work, and we should use the own SIFO autoloader. The problem here is that we should assign an instance to Bootstrap before launching Bootstrap::autoload(), so... :-1: I'm loosing something here.


Did you try the make sitl_quad_gazebo  ? It had the right SENS_BOARD_ROT param in it, also gains pretty decently tuned. I also did alt hold and missions on it. I've not worked on iris for a while now, but it should work!


> These are installed with

You can install more of these with…


Does anyone have any suggestions on how to make this better? I can provide the file for the permits if needed


Coding standards. Class braces "{" should be on a new line.


I changed this now to not use any timeout. This way, the repo-client and its user don't have to know about the refresh interval of the server.

Having this timeout parameter was actually a remnant of a previous implementation where the response['needsMetadataUpdate'] was not yet available. This meant you could hit the race condition mentioned in this commit, even if everything was working perfectly.


I am not aware of any definition that can replace it. I checked elsewhere in the code, where the same procedure to get _mptcp_hash_mac_ is used, and no definition is adopted there either: https://github.com/multipath-tcp/mptcp_net-next/blob/mptcp_security/net/mptcp/mptcp_ctrl.c#L2228.


This should be first (if user ask for help, don't do anything else)


What if the array is empty? Accessing the 0th item will cause an out of range exception.


which is indeed better because it avoids the case when the .path method is not available. And also pretty much what was in my origin PR. Thanks!


Good question! We'll discuss this on Friday.


I favor renaming these auto generated migrations to have a more meaningful name.


yep yep :)


Removed $$$


I wounder where to implement the user interface (the actual programm)
If we do that seperately (outside the class), which I consider advisable, we may want to move this getE() over there. Since the calculation of the neutral element is done upon initialisation of the group the other function would not be requiered anymore.


Returning a mutable dictionary is bad practice. We'll discuss why in a future meeting.


Shouldn't this be

    T.oneOfType([ T.object, T.oneOf([false]) ])

to be precise?


No, this branch was a work in progress. The only passing branch is `sifo3-beta` :(

@lombartec Do you have any news?


Where is that icon located?


Done.


webserver? https://github.com/airdcpp/airdcpp-core/commit/0b8196f04198502024dd1c6421cb7d5c004fe2dd#diff-4d0fd35f4e18a4e404e0385b0b83edfc


I am not sure I understand that hop-stuff  either -- that's some confusing stuff...


Sometimes, timeseries id starts from 1. In this case, we have to collect the right offset index for ```openBytes()```.


Yep.

Thanks for the pull request! Instead of trying to resolve the merge conflict .. I just copied your code over.


I forgot to add tests for this, will do.


1.Dalam permainan block breaker, pada object bola semakin besar velocitynya maka kecepatan pada pantulan object bola juga semakin besar. (T)
2.Dalam permainan Pong, move speed pada object musuh = move speed object player.(F)
3.Flappy Bird, gravitasi pada object bird selalu konstan. (T)
4.Dota2, player movement tiap" karakter pada dota berbeda-beda.(T)
5.COC, kalkulasi damage base disesuaikan dengan jumlah hit yang diterima, semakin banyak hit, maka Hp pada base akan semakin berkurang
6.Plant vs Zombie, posisi spawn pada object matahari adalah random. (T)


@vilchik-elena indeed!


#7 Some more tests added around the new controller. Mocked out StatusApi and also ISettings<T>


Why aren't you using the version from GitHub?


Trying it now


401630297 資管4B 柯名哲


#7 Added tests around the FontAwesome icon helper


Im assuming you needed a different interface because with the SHELL spawner you dont call a script?


Actually, it turned out that using --wait on a repository that has NO scheduled metadata update will just cause the repoclient to hang/report an error. Since the creator of a build job cannot always know how the repo is configured, this behaviour is problematic. I'll open a ticket to discuss this.


Looks yummy!


good!


This is done by writing few NPS registers.
The common way to achieve that is from external host by control plane application.
An alternative is to do so using our DPL driver (mmap) by data plane application.
DPL driver patch is part of this set.

From: Vineet Gupta [mailto:notifications@github.com]
Sent: Wednesday, October 07, 2015 9:40 AM
To: EZchip/linux
Cc: Noam Camus
Subject: Re: [linux] ARC: [plat-eznps] Use dedicated user stack top (2f3380e)

So where is the kernel code which does this mapping ?

—
Reply to this email directly or view it on GitHub<https://github.com/EZchip/linux/commit/2f3380e0c44de7b4fe0f3d9eb3ccdd2e0e38760e#commitcomment-13631573>.


@PennyQ - I think that for now we should make sure that what we do in the plugin works with the latest stable release of vispy in anaconda (0.4) but maybe that just means that for now we keep the simple axes, then you work on the better solution here, and once conda includes a more recent version of vispy, we can move the solution here to the plugin? Basically, we want to make sure the plugin always works without having to install vispy from git.


Coding standards. Variables should be camelCase instead of underscore-separated. Method braces `{` should be on a new line. Documentation relating to a method should be in a docblock (`/** ... **/`).


Done.


There's no statement on the proper extension, and there is no pattern for this in any other repo I can find that's .NET Foundation-owned. This filename was given by LCA, so I stuck with it. I think we can get away with not having an extension.

Note that this isn't necessarily the final version, as this was compiled from the JSON.NET third party notice (which we didn't use) and the correct licence for BC. However, this notice was needed before I PRed so I made this mostly-correct one up for now.


iniciando Readme.md, directorio IMG y DATOS


Looks good!


Yes, I had fixed it on your latest commit and branched again, so you
wouldn't have to resolve that first Pull Request. I believe that is the way
forward to contributing. Too bad my commit isn't in the tree now, but hey,
it works! Thanks for fixing.

D.

On 7 October 2015 at 16:24, Mishbah Razzaque <notifications@github.com>
wrote:

> Yep.
>
> Thanks for the pull request! Instead of trying to resolve the merge
> conflict .. I just copied your code over.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/mishbahr/djangocms-forms/commit/dedd03ed014ef8d445aac153966ddf7133eae72e#commitcomment-13639765>
> .
>

--
Dries Desmet

*URGA | creatieve communicatie*

Zuiderlaan 69
8790 Waregem
t 056 61 41 94
m 0477 19 41 13
dries@urga.be
www.urga.be


Don't worry about it. You did good work! :paw_prints:


The user interfaces should be implemented in the main() function.
The class Gruppe provides a method to print the neutral Element on the console, when the user want it.
We can declare the check*() functions as private, that is right.
But I think we should really speak about this, maybe this evening.


README.MD


Maybe I was not clear enough. I'm not talking about the local variable residue in xilinx_tx_status() but about the member residue in struct dma_tx_state. Which part of the code will set it to 0 when the dma reaches DMA_COMPLETE after a transfer? This code (with multiple bugs IMHO) accumulates all the differences (hw->control - hw->status) for all segments in a channel. hw->control contains the number of bytes requested for each segment and hw->status the number of bytes actually transfered. After a transfer is complete they need not be identical for a xilinx axidma s2mm and thus the difference not zero.

Or were you saying that when the dma is in DMA_COMPLETE the desc->segments list is always empty?

Then here is the other bug I see apart from the infinite loop:
- The pointer desc is not even initialized when it enters the infinite loop.

This makes me wonder if anyone even tested this code before the patch was posted and also if it was examined before it was applied and committed.


faudra le virer du coup :)


My libGDX test many moons ago had a scrolling view with stationary UI bits.
As I recall it was pretty easy to set up. And very awesome as a feature.
On Oct 7, 2015 2:34 AM, "Tommy Ettinger" <notifications@github.com> wrote:

> If you don't implement them, I will! [image: :smile:] I think it should
> actually be relatively simple if you only need to worry about LibGDX, since
> the LibGDX implementation has a few ways to trim down an item's area and
> display two graphical things next to each other. Everything in the LibGDX
> implementation uses Scene2D (a libGDX GUI thing), so it shouldn't be too
> hard to just stick two SquidPanel or SquidLayer objects at different
> locations on one Stage (the parent of all Scene2D widgets), or in one Group
> that gets put on the Stage as one item. More interesting to me is the
> part-of-a-cell-offset for SquidPanels. I've considered using two additional
> panels over a normal SquidLayers, one offset a half-cell vertically and the
> other a half-cell horizontally, along with box-drawing characters to handle
> thin walls (occupying the edge betwe en cells instead of a full cell).
> Panning the visible subset of a map also seems handy, and it seems to be a
> very, very common feature in newer tile-based games; I think only some
> roguelikes and some puzzle games routinely get by without it.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/SquidPony/SquidLib/commit/902d8d95e9212fd1e63f3ce179908c4ac2876570#commitcomment-13634319>
> .
>


@devbharat Indeed, works really well. Didn't expect the default gains to suck that badly :-)


Coding standards. All variables in this class (and all classes) should be camelCase not underscore-separated.


On Wed, Oct 07, 2015 at 07:05:42AM -0700, psyhomb wrote:
> This is just a precaution measure because downtime interval can only be set
> while migration is running so I wanted to give some time for migration
> process to start and make sure it will catch it during its run

OK, but sleeping for 2 seconds seems like an ad-hoc measure. How
can we be sure that the migration is going to get started withing
2 seconds?  Is there perhaps a better way?


Context:

The current touch targeting system has the following problem: tap on a text
input that will be covered by the keyboard when it gets focused. Tapping on it
again will send the touch event to another component above. It turns out that
the scrolling offset set by the system when the keyboard pops up is not taken
into account by getGlobalVisibleRect.
This commit fixes this by using the same touch targeting system that ViewGroup
uses.


Jawoll, ich bin begeistert. Ich hoffe doch es wird verschiedene Handlungszweige geben, je nach dem ob es sich hier um eine überglückliche Demeter Kuh handelt oder eine von McDonald's. Entkommt die Kuh den grausamen Fängen der Milchindustrie? Wir dürfen gespannt sein...


This commit created more merge conflicts than it fixed...


Changed to count; done.


@certificate doesn't change while working, so why doing .split(//).last(65).join for every line of log?


Hi @ace20022, this seems to work (well, compile anyway): https://github.com/jimfcarroll/xbmc/commit/4cf52d76c63e3b28bff5cf7fc39bce6250129f90


(ee336bb) The title of the commit doesn't respect guideline ("type(scope): title (refs #<number>[, ...])")


It is executed. :) The rest of the code is in the previous commit. In the HTML async event


Does this fix the issue with the purple rested becoming skinny or fat at random times?


#11 Started


Now I don't get the idea.


The XMC microcontrollers provide set, clear and toggle functions for the port output pins:
 63  +#define LED_1_ON              (PORT1->OMR = LED_1_PIN)
 64  +#define LED_1_OFF             (PORT1->OMR = (LED_1_PIN << 16) )
 65  +#define LED_1_TOGGLE          (PORT1->OMR = (LED_1_PIN | (LED_1_PIN << 16) ) )


Ok, i'll add something like "register_exception_logger", that will get Rollbar as argument


No worries, I understand that it was unintentionally. Easy to fix :)


@vilchik-elena indeed! Nice catch!!


DEFAULT_TEMPLATE isn't defined either.

I think you have to define both of these templates before using the method.


Sounds good.  I looked at stringByReplacingOccurancesOfString:textToRemove:  but couldn’t get it to work.

> On Oct 7, 2015, at 7:53 AM, Brandon Alexander <notifications@github.com> wrote:
>
> Same comment as above. We'll talk about using string formats for building strings instead of replacing characters in a given range.
>
> —
> Reply to this email directly or view it on GitHub <https://github.com/Mountainbrussells/ios-exercises/commit/210b72676d0b365f1ad98a3412984525c239f7ab#commitcomment-13639017>.
>


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


Removed both.


Yea, `fn file` was also removed in a recent commit, along with a couple other changes that have made this PR unmergeable, so I am refactoring a bit and hope to push an update later today.


mangler ";"


I don't see under which circumstances `data.game` could be undefined. The round API always returns a `game` object.

I removed theses lines because I couldn't find an occurence of "\.moves" in the entire project.


"whole_system" is only about disallowed cpus and NUMA nodes.


Going roughly back to the original topic. I think I prefer it with the capital, the small letter looks a bit odd to me as it is essentially the start of the sentence where "Speed" would be the header", they are not directly connected.

As for what it displays I think the headings should be

Unlimited > Max
"" > Capped (or Limited)
then Slowmo and Turbo as they are.

That will keep the amount of space taken up down a little and be descriptive of what mode it is in.

In regards to the save slot, yeh remove it from the title, I don't think people really want it there for when they are using full screen it is useless anyway.  What people really want is like ZeroGS where you get a temporary message pop up in the GS window telling you if you are cycling states or saving/loading.

GSdx version isn't much use as it rarely changes, especially during development if people are using GIT builds, just saying "GSdx" at the top is fine.  so the way I see the bar it should be

GSdx OGL/HW | Speed: 100 (60.00) | Limit: Capped | EE 100% | GS 100% | VU 100%

and that's it, nothing else is needed up top.


no, @connections array is essential for add_connection and get_connection, they can work without push method.


Got it.  Thanks!


Mm, not sure here. From a user POV, I'd like the buffer to *not* end with nul if I ask it to. Can you try to do that instead? Here we end up with ``used`` pointing past the nul byte, the right thing would be not to include that. Also, do the comparison in the test with ``sol_str_slice_eq()``, creating a slice with that content to compare.


fixed


Maybe add `'inplace'` to `__props__`, so that comparisons and printing still work.


Can you extract this into a dedicated private function? It seems a bit too syntax heavy to be a function variable without using any data from the enclosing function


i guess that's the only bit missing now


@okms How can we handle this better?


Yep. With the modified boot.img from here it works: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344 - and SuperSU 2.50 of course.


Please use router: Ember.inject.service('router'),


Lit Forms cannot be checked in.


Nitpick: capitalized Avocado, Python, etc.


This looks wrong


Ceci est un commentaire


See also ramdisk mod for random write/read on boot.


I've got it running in a tmux pane `sudo bin/watchnotifyd`, since yesterday. It's killed notifyd a few times, tmux hasn't gotten unusably slow, and my mac hasn't frozen.


LGTM!


This is really lame.


Just testing :-)


@ace20022 I'm not sure exactly what problem you're seeing when compiling but if you're trying to compile:

```
std::shared_ptr<std::vector<int>>
```
Then the compiler is interpreting the trailing '>>' as a right shift operator. You need to put a space between the two '>' when using templates. See my link above. I can submit it as a PR if you guys want.


I'm unsure if we should, besides that text, pollute the diagram with the tags conditions. @ldoktor, what do you think?


If you specify an invalid BigInteger, you'll end up in the exception block. I can Trace out, but this won't be (and shouldn't be) reported to the client - given that all reasonably valid PUTs return with a 200.

We might want to consider allowing the return value to be something other than 200 in the RequestResponse to report such errors. But this would be a large-ish change for another day.


Got a better solution here @okms?

They're loading f.ListItemAllFields.ParentList.ForceCheckout, but not using it.
https://github.com/olemp/PnP-Sites-Core/blob/master/Core/OfficeDevPnP.Core/Framework/Provisioning/ObjectHandlers/ObjectFiles.cs#L132

Also, f.ListItemAllFields.ParentList.ForceCheckout isn't properly loaded for some pages.


open issue to be fixed


@phirefly does this comment apply only to the BA60 Approved, or to all Approved (including BA61 and BA80)?


So you've been born the year 2015?


I want to track activity inside the app after sign in as well.


The docs say: "Do not access the Android UI toolkit from outside the UI thread". Calling setText/setCursorVisible outside the UI thread can cause exceptions to be thrown depending on Android version.


Also, `GpuGemv` and co. need to inherit from `Op` at some point, so that they can be correctly identified in the `@local_optimizer` decorators for instance.
Currently, they do not, since neither `HideC` nor `BlasOp` inherit from `Op`.


Good job!


fixes #233


Yeah good question. About 15 lines below here, the only place this function is called, it's called in `while True` loop that catches `ResourceConflict` and retries until it doesn't fail, intentionally using couch's `ResourceConflict` behavior as synchronization mechanism to make updates incrementing/fetching ids atomic. (This function was in the `try` even though it previously couldn't raise a `ResourceConflict`.


NICE!!


I see your point. It (Tags, inheritance, detection and all that) feels like a tripping point that might come up, though.


Thanks, I'll submit a fix


Hey @dpobel,

Thanks for your contribution! Let's think a bit more before add a new config property. What do we want to achieve at the end of the ends? We want to instruct the toolbar to show itself or not - nothing more, nothing less, correct?
By design, this decision should be taken depending on the selection, i.e., if there is a selection, which matches, the toolbar shows with the corresponding buttons, otherwise it doesn't. Isn't that exactly your case? If so, isn't it possible to add a new selection with your custom buttons? [Here](https://github.com/liferay/alloy-editor/blob/c10ff830cc9c5b835ba148aa4b42e3b637d05963/src/ui/react/src/selections/selections.js) are the selections we currently recognize, together with their buttons and test functions. They are inside an array, part of AlloyEditor's namespace. I think it should be possible for you to add a custom selection with your buttons. How do you feel about this option?

Thanks,
Iliyan


Really, this operation should be a POST, not a PUT.

The code has changed since this comment, but basically revocation operates on *serial numbers* rather than by *thumbprint*. So we blindly accept any (valid) serial number and stuff it into the list of revoked certificates since we don't keep track of serial numbers yet. There is also no particular harm in having a CRL contain an entry for a serial number that has never been generated.

Each PUT to put in more serial numbers changes the CRL, so the CRL is re-generated on every GET.

We do a check that the CRL doesn't contain the value already prior to re-adding in RevokeCertificateBySerialNumber (name supersedes RevokeCertificateByThumbprint in the next rev)


Missing space before "loaded".

There isn't necessarily an hardware to be accessed. What about: "no access to the real subsystem."?


Looks like this was fixed in https://github.com/facebook/react-native/commit/8251f1c9056667aca13ffff0adc7be72ce3da427


Was about to say that. Templates are there, they just aren't mapped. Also, should be unique_ptr. it's not shared.


Since the builder lives inside Soletta's repo, why not use the source there (even if with git export) instead of cloning again?


@lmr, yep it could feel like copying, pasting all the code there and doing a little transformation into pseudo code! :)

I believe this simplistic view, with the text that follows, hits the right spots. The diagram covers the obvious for the vast majority of users, and the text directs those that need the extras to the right place.


Use a space between the methods and the strings, like so:
````
puts "How many hours/weeks do you work?"
````


This should be it.  test type 4 is 'generic'. It simply looks for hex strings in the input hash that are 'known' sizes. So if there is a 24 byte (or 32, 48, 64, etc), that is pure hex, and ALL of a single case and not pure digits, then that buffer is case mangled, and the bug is searched for.  So ALL formats should now work.

There are a couple of white lists currently. The bcrypt has some hashes with the salts 'looking' like hex, such as CCCCCCCCCCCCCCC (etc).  But the format does not have the bug, it is just a FP that needs a white list.   I also have ```@dynmaic=``` hash white listed now. It does have the bug, but it will NOT be trivial to get it 100% correct, so I have just postponed it.


PS @jimfcarroll the shift/template conflict is ancient history. Pre c++11


Wow


This commit breaks the display of the Search administration section.


I do not understand about what speech Google Translat translation is not clear :(


Great job!


AIS: Header file for adder class


Unfortunately work will keep me away from this for a few days.

Might be faster if someone else checks :(
What is preventing you from compiling? (not questioning whether you can or not) Maybe we can figure it out and get it so you can compile and test which makes development much easier.


^^ because worst case is:

```
from avocado import Test as ATest
import avocado as avocado2

class Second(avocado2.Test):
    def test(self):
        pass

class Third(ATest):
    def test(self):
        pass
```


n分割のnはユーザーが指定するってなってた気がしますが、(i * 20)で大丈夫ですか？


this is the name we use in the Gemfile, I think we should restore the previous name because the following line does not follow the convention
```
gem "Vigilion"
```


Je me suis basé sur [ce document] (http://cache.media.education.gouv.fr/file/06_-_juin/86/2/Annexe_2_Bareme_bourses_de_colleges_2015-2016_442862.pdf).

- Pour 1 enfant, taux 1 :
    - Plafond non arrondi : `11 228 * 1.3 = 14674.4`
    - Plafond retenu : `14 674`
    Donc pas de `ceil`
- Pour 2 enfants, taux 1 :
    - Plafond non arrondi : `11288*1.6 = 18060.8`
    - Plafond retenu : `18 061`
    Donc pas de `floor`

Le round est le seul qui marche :)


Feito! :wink:


I found out that the `to_i` method strips the new line, so we don't really need the `chomp` method!


**** !== 2015


I'm no expert on gems. Here are my steps.
1. Start the container, configure it
2. Step inside, wget the deb pkg, install it
3. `su conjur` `cd ~` # /opt/conjur
4. ./scripts/conjur authn-ldap
bundler: command not found: puma
Install missing gem executables with `bundle install`
5. find authn-ldap/current/vendor |grep puma
vendor/ruby/2.0.0/gems/puma-2.12.2/... #many puma files
6. ls -l /authn-ldap/current/vendor/ruby/2.0.0/gems/
drwxr-xr-x 7 root root 4096 Oct  7 14:43 puma-2.12.2


这里这个L。。。？


Put spaces on each side of the assignment operator when assigning variables, like so:
````
money = gets.to_i
````


fixing file names for windows naming conventions


@levackt Can you remove TODOs from the master branch and add these as the #210 instead?


Not necessary to check `err` before using `.message` as it uses child_process which will always return an actual error on failure.


Why did you add only a year and not a specific date?


Nice job overall - just a few readability issues to correct.
10/10 :+1:


:gob


Is a goto really necessary here?
Couldn't you just use a break

with goto
http://play.golang.org/p/FUvMQrKkr7
without goto
http://play.golang.org/p/dmDjv3O9w9


ugh. fix this! (paraphrased from @simonjbeaumont)


Might be good to mention the module in the name.


I find it a bit redundant. What else are they if not *general*? I would simply skip the title.


I think we should get to know each other a little first.


I think having one fieldset without a title and one with a title looks a bit ugly.


I think this is fine.

GETs by definition do not modify state of the system (I don't think I've done that here, correct me if I'm wrong). We are thus reporting the state of the system at the time the GET was requested.

If a PUT happens concurrently here, then yes, the s_certsCreatedBy* dictionaries would be modified but the operations that read should be protected under the locks.


It'd be better to use something other than `Backbone.Model`, since that's what it defaults to.


quick review, looks OK, hopefully all provided examples work... Sorry for being so picky, but there are really lots of details in this area...


Extra space in the ``{{ url }}``


This number is pretty arbitrary. We simply use 64 here so there's less chance of clashes.


Where do these upstream linux commits originate? Wondering why so many are just makefile changes.


Slipped my mind. Thanks.


<!-- This Source Code Form is subject to the terms of the Mozilla Public
   - License, v. 2.0. If a copy of the MPL was not distributed with this
   - file, You can obtain one at http://mozilla.org/MPL/2.0/. -->

<SearchPlugin xmlns="http://www.mozilla.org/2006/browser/search/">
<ShortName>Twitter</ShortName>
<Description>Realtime Twitter Search</Description>
<InputEncoding>UTF-8</InputEncoding>
<Image width="16" height="16">data:image/x-icon;base64,AAABAAIAEBAAAAAAAAALAgAAJgAAACAgAAAAAAAAQQQAADECAACJUE5HDQoaCgAAAA1JSERSAAAAEAAAABAIBgAAAB/z/2EAAAHSSURBVDjLfVO/axRREP6SS0ihlv4FQpoYWxHyHxgCsUxhmToBS4tF7NLZWaiIEHLv7d5dJNEQ0tgYEAmIjeAfYC57++7MGbzLjxu/Nxt27zZrBoadnZnvm3kz7wEqMpZqmdAfBBMIZBzGVGCkorbXq4kFp/yPtBgPZCJzZvYQuNZ+jKhVo75G2LyHVz9uoeFmc6bILaHaepv9v/w6iRcypXbonmNPBB9OBbv82tYfmPgn7NHTnKAaP8E+g8Ztot68k/nXDm8ooNEVhHEP1vXROBbUf/M/Wc0Jwl8zsEkHOxcMtE6Y+A42nodpLtLfR9QWRMmA9jm2eh78aXQY4eF9VvjCgKDWEewM2PIZQc4nD9Sf6hk+sohNqorzW0kN91BBdYKtO9dE/00JZITA50XxsxTHlWarqMYBh/O3UPGqrednx7ox3o+UhbIRT7O1BO9PfIsXI5V9J34WvrqN94buwFi+b3N0k0nrCjAFAp1+Nz1Czd3N2y8Tm6ywYk9JTHKqk/cD9cM17YW89WExbo6Ja1zhvgK3+4Itql+rt8PkO1f6oBysBN3brLrMVhs84wHJvpHoMwnf8CI9ygZd3nbJgymrMvxeSoLjmlCsIJf+a17lP6juZmUWkMzvAAAAAElFTkSuQmCCiVBORw0KGgoAAAANSUhEUgAAACAAAAAgCAYAAABzenr0AAAECElEQVRYw+1XS2gTURS9ia0/EMSCCC4siCIKrly4UVwIrgRR3KgbXQmCCiIiCha7EQRR6cIupHShSeZjf6lttdWFgqBRBPGDKIqF1mQ+1Wp/SZvnvXfmTWfMpJ3U0pUPHplJ3rv33HO/Afi/5nPViTjuKm8rYlFlAoSI8a500R1SGLYUZRH+Hvee6+qqygvxW1KJ1XLd+74aUuY+0OzjoHw/BElj4zQQHxv0HDBUvjR9WQlNYmnJhSjK9dxFUC0LOsYE3M8LSI8LUKw8AmoG5ecqPtP8vgZ04zKeO+jqjUtBDi2qWY+71xPaKKpnpF0uzUpCnxDQOixQ+BSo9iR/3vsh4CF+r5of8D3F75r9udQAKUwx++AJXkhZCe9QBkGEuUSC1swTjhK0VrUmEYzw7SKCyUPrLwEP8IxufQN9aCfKPwCJwdq/lCPluvUG2n4jhQW8bD6Hu+amABvSd/LOTbEENOMjdIyicLuA1om/ADhbMqIZn/DMOMq+7iqPBanUzWfQOUGUjUFnnj5H0WdnQOlfFoxssdix3tjGgnWbrCuGKvdA4LmuSQJ6s9SN0zFwg6lS7Qmms+WngK4pEvAVg+w83MltCAAhAHSGFMwEgGQRq2quwZe2cShJkaYvtey39hEHMfsQL7cjxd1F4dBnPWUKVeMwaLmTkRggGd1oiJI9GxLcLg2NA8s5DTXzCKePbjtBJAVoVoGjmFxEwsgiCi5tFuoDDFinHcb9xWg6CBcjpS9ReReCeF9GOL5TsCEYhRkSs26HmSLXh2R2f8DlJS7Q7BZOwyhWzeZ3P2hijtJRG9wSXuQkIj27m1OKKKPUiQIiCv1ptF4x33rUh/Yb+aVqN8BjIf07HwDy0EPFzU2/ck0rgCpln8MgtOcBgOOiFizRSWt7aQCWA0GHdesSBuOAm+fFOQIoOFXVeBRqaGnvlsGIed5LwWiO/LP11KASg7tmt97fnRoz1Xj5NXc4WQP0Sliw6d4EN6mUdStyew8cbB6uQWGdXL+pPHMrjQLCVe40tHdo1NJoQ47X5XBnfKUykduBQ0U9+jEbKR5IOTc0IwfJb+tnjvwoq+3DCmxEV1iwvzyHtlzbSTnVHMRKuTm6crK8AcelDrGc/a/0r4WUsRcF3ebWzC4YCqt8Rbdo5XmO4IZj9IGSW+PFUuSVyu7BeeABIrdZMNFIfiSrCQQFouwDNHxQLyBQdK6nSPOfgftUSXWtaOlD67BkXkCLXrFV1IYJBAUifcpnspQHFjyjmi+4y8nBs6KIL1cJuRZkt6K1xzCYrvFAqdtptDCNz3dxX8V91Gsufqvn8r/CByJemd/kvJiprui/RAQkMaZR/r1i4W6a0rP/N/gXi6OvmDvBLoiyBV1/AN29Cs9hVFoUAAAAAElFTkSuQmCC</Image>
<Image width="65" height="26">data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAEEAAAAaCAYAAADovjFxAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAyNpVFh0WE1MOmNvbS5hZG9iZS54bXAAAAAAADw/eHBhY2tldCBiZWdpbj0i77u/IiBpZD0iVzVNME1wQ2VoaUh6cmVTek5UY3prYzlkIj8+IDx4OnhtcG1ldGEgeG1sbnM6eD0iYWRvYmU6bnM6bWV0YS8iIHg6eG1wdGs9IkFkb2JlIFhNUCBDb3JlIDUuNS1jMDIxIDc5LjE1NDkxMSwgMjAxMy8xMC8yOS0xMTo0NzoxNiAgICAgICAgIj4gPHJkZjpSREYgeG1sbnM6cmRmPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5LzAyLzIyLXJkZi1zeW50YXgtbnMjIj4gPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIgeG1sbnM6eG1wPSJodHRwOi8vbnMuYWRvYmUuY29tL3hhcC8xLjAvIiB4bWxuczp4bXBNTT0iaHR0cDovL25zLmFkb2JlLmNvbS94YXAvMS4wL21tLyIgeG1sbnM6c3RSZWY9Imh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC9zVHlwZS9SZXNvdXJjZVJlZiMiIHhtcDpDcmVhdG9yVG9vbD0iQWRvYmUgUGhvdG9zaG9wIENDIChNYWNpbnRvc2gpIiB4bXBNTTpJbnN0YW5jZUlEPSJ4bXAuaWlkOjQ0MDYxRTY0QjUyNTExRTNCNzdEOTU4N0NCMjI3MEFDIiB4bXBNTTpEb2N1bWVudElEPSJ4bXAuZGlkOjQ0MDYxRTY1QjUyNTExRTNCNzdEOTU4N0NCMjI3MEFDIj4gPHhtcE1NOkRlcml2ZWRGcm9tIHN0UmVmOmluc3RhbmNlSUQ9InhtcC5paWQ6MDcyQzJENkJCNTI1MTFFM0I3N0Q5NTg3Q0IyMjcwQUMiIHN0UmVmOmRvY3VtZW50SUQ9InhtcC5kaWQ6MDcyQzJENkNCNTI1MTFFM0I3N0Q5NTg3Q0IyMjcwQUMiLz4gPC9yZGY6RGVzY3JpcHRpb24+IDwvcmRmOlJERj4gPC94OnhtcG1ldGE+IDw/eHBhY2tldCBlbmQ9InIiPz4/Os9TAAADvUlEQVR42uyYWWxNURSGz723OiotMbU1N25jKNImIhENfSAh8SDxQgQP7QPxQhAVU1DihYjxwRBCCAktaohZE6EkNIqUmtJWq0LV2On6V/OfZNnO6RXJfXJW8uXuffc9Z5/9r7XX2uf6QqGQ9b+bzxPBE8ETwRPBE+F3i8q+bwXxuRhcAmciJTbYBmaDXWA16AMKwGOw1+GaANgAosEK0BKxSMgqC73G5wD200B1BOYZCcqNBR4Ds9ifAEqNa5aBLWyvA2sjJYJfCSA2MELz1IPPbIsYsgcz1Phwh2v0dxmR3A4iQpPql0dQhCSQCzIpQkCNP3W45rtqv4poTjD6a8Bb7mGhDZSASi5gDjgMrqprZoJp3Otl6vuFIIv7ugqMAWPBG/Cc97Ytj2MBjp8yRJjIvCXjX8Ah0MyxrmAuyGb+qAHF4JbDehPAFNCf95J7nJScIGGa2IlQX8EwcIVh2Qh6chF9QS1/9wKksx1U3j0OFvA+Yh9AbwqZ4zLndD7obpfx62ASf3OXz2HaAc5r21RwkAlZW7X/L6IlgaHcyn40sbgY2+JUu59qy297qb54LsbwtGmDwoyn8LNECVABzoF37M8HK1VOKXEQQCzV3A5lzBE+9kNUVCbooSLDPlw0GxFj20/V/qEEtBjOZk6o4MP7uR33cGvaJiH+jOPfQD631wiO17H8vuTWPMI1SEXZBJYb67zJSG6XuaKMvJCrsrhleDOG7TYuzFxsi4sIfiWqLazPEEEWddvF2xbDuMAYX6TaySyx8RTZnq8LGKWqizhtslmO/cqrYuNcwq+dN7Q4kVMG7+YiQpQxh5+CaWEyHebU0TPapbLpw1i82m62Sb5oUFum1uE80vGAD8F49o+CreCTqhAVDJ8aLlSS6D6wHyxR90pjCF8G69X3ku3fq34sF1jB5Ca2mXmjjp6UcL7ICLEY4jLnA14rz3kBLFUleAZ4Qof5+Gk7IynciVEuPh0mOQ7l4aX4H8pwOhfXpLaTbK3BLL1OJiVwHj3nlPmreN9HPI2K3WNOa2GUtPI4XkknJPM0nOYkgsVElN/JQlaBjSxNOS7bxanS7GB9DxoHokR6XB+Nnd43gi4HKV2Z6jt5bkmUQyhIgJER+8dLSkpex5H8LPjIZBRHNZtJJcO7gQmqO70jW0neOwopYAyv9/EwVKgyfCM9IKVvJzjP70vp1RSW4lZGjIh+h2cKealLZUiHuJAicIL3LWJJtsft5/5O596g6JIct4Nr3qu093+CJ4IngieCJ0J4+yXAANopCw9hh0hVAAAAAElFTkSuQmCC</Image>
<Image width="130" height="52">data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAIIAAAA0CAYAAABGkOCVAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAyNpVFh0WE1MOmNvbS5hZG9iZS54bXAAAAAAADw/eHBhY2tldCBiZWdpbj0i77u/IiBpZD0iVzVNME1wQ2VoaUh6cmVTek5UY3prYzlkIj8+IDx4OnhtcG1ldGEgeG1sbnM6eD0iYWRvYmU6bnM6bWV0YS8iIHg6eG1wdGs9IkFkb2JlIFhNUCBDb3JlIDUuNS1jMDIxIDc5LjE1NDkxMSwgMjAxMy8xMC8yOS0xMTo0NzoxNiAgICAgICAgIj4gPHJkZjpSREYgeG1sbnM6cmRmPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5LzAyLzIyLXJkZi1zeW50YXgtbnMjIj4gPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIgeG1sbnM6eG1wPSJodHRwOi8vbnMuYWRvYmUuY29tL3hhcC8xLjAvIiB4bWxuczp4bXBNTT0iaHR0cDovL25zLmFkb2JlLmNvbS94YXAvMS4wL21tLyIgeG1sbnM6c3RSZWY9Imh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC9zVHlwZS9SZXNvdXJjZVJlZiMiIHhtcDpDcmVhdG9yVG9vbD0iQWRvYmUgUGhvdG9zaG9wIENDIChNYWNpbnRvc2gpIiB4bXBNTTpJbnN0YW5jZUlEPSJ4bXAuaWlkOjg5QzlEREI0QjUyNjExRTNCNzdEOTU4N0NCMjI3MEFDIiB4bXBNTTpEb2N1bWVudElEPSJ4bXAuZGlkOjg5QzlEREI1QjUyNjExRTNCNzdEOTU4N0NCMjI3MEFDIj4gPHhtcE1NOkRlcml2ZWRGcm9tIHN0UmVmOmluc3RhbmNlSUQ9InhtcC5paWQ6ODlDOUREQjJCNTI2MTFFM0I3N0Q5NTg3Q0IyMjcwQUMiIHN0UmVmOmRvY3VtZW50SUQ9InhtcC5kaWQ6ODlDOUREQjNCNTI2MTFFM0I3N0Q5NTg3Q0IyMjcwQUMiLz4gPC9yZGY6RGVzY3JpcHRpb24+IDwvcmRmOlJERj4gPC94OnhtcG1ldGE+IDw/eHBhY2tldCBlbmQ9InIiPz5Ln/UEAAAHKElEQVR42uxca2wVRRTe2wdULUVARDQIkqCmARGKhQBqeBsCKkiImmiML0xUFEs0BImIaDQSH2gQlB9iQlQQUAHFF5QWQbDiI4oIiBCgIE9BaAv03us59rsyjjOzO7s3mC3zJV/a7szszsx+c+acswOJdDrtOTjkuClwcEJwcEJwcEJwcEJwcEJwcEJwcEJwcEJwcEJwcEJwcEJwiIC8Ht/883tXYhFxPfFYzMc1jXgXsY44g/iUok47YgfiVuKukM8pJeYS1zQWi7CI+B2xAhNzTYzHNI9YRjyXeAFxikIIz2GcPN7fiJMtn3EhcS24mriZ2CnOQkiUVKV5kh6Xrh/HYA/GbDy9iV8qrqdh7Y4SRxPfVdQZRlwa8DlfE3tI17YRLyWejKtFeERxvSlxUAzHc5lO8BAC43ZNnTsDPqOjQgQetpnucd4a8jVlBTEcT6Xm+l7iHvye0tTJD/iMFoayc+IshDpNWRxN3BbiWMX1ewQB6MZVH/AZpnon4yqEvEYYCb1C3EQcSkwS5wf06s/oM3smIeyL8bg+AW1Qk4Xn7mmMQigh7kacrHPAThA3aNpmnK85xHU+/RhCHEE8QJyNkM4EzhH0JP5MfFFR3o84Cqb6LeRG/NCW2FkaL4+xlvhLwPnsC0c7V2ifgkD2+rRl/+Jq9KE98Ty04WjkJ+KqCGLlCLAl3nda6FsNrOff4eMR+tksgpi24sWUCy91mUVoxnH+JCl0LcHgVVgKsy+GcgOJR/D3/cRXpTbDiUvw+wLiSMsxcr7gerwY7luVZftaCHaioqw15mAUXr7JQi8kPk3cEeCZFxPHEQcjrNUteg63R2RDCB4sQ3M4nvwCi6XyzeiMjPZQvIz3YSFkDCB+rrg+gfgs8RIIUxU1tMXqDCOEjOBKEaJuDDlPY4ivC39fjgXUxuIeRyHsckOdkbCEQaOYZdn61tAEpprRSlHeSrPFFBvUrEIXn/xBqab8fJ/VFgRXeQ3Zyh0R7iHmKgohrjaW9+B2K4h9NOUTIXabUPa6bH50+lMwgzLqLEOxGsvw7Dh+Jg0RQW4WxlgP0YfFMcnqFUa41xfY90X0J04Nca9UtoSwUXDI0hahWcoylEv5XE8aylMRx/gmzHK7CPd4RnAqB2jq8NZ3I7bSbsSHsfXKYKf0SenaeyH7Nd0UNfC+etjgZCSwQtejs3HHMURJORhbZoxszT4lPoRrpgxkNaxZriRqjhqexypm6NLcy73/pvb5Y+BK4reK+nyf8bCIN3vmrOdOjCVXiog+JpaZhMADf+cMyqksg+fuh6ShbLSn/uglo6fmOvtSr3mnvotknqfbEovgN1Xh2brt9DYk1lKmPELC4J02RiR8/Aw/5ATwk0xoanCGu4I2aI2fnTXlg2BRfAeVb+hwGORonKykxeSfsHxZORH751k4kyZf46yAQmiSRWFvF6yDjF+DiCAzKbqM161ZXHGtNNfzDOGejThTFv2q1ZT3Cji+Q4ayawP6Itmytuw3bDBsWYeC3ohfxDqNJ8xJiXulBEgQ7FOYvkI4S+Ol62WGfEE/xMsi7tPU3+1j9sUVr0sGcXJruqf+eik7XXs1YuUMKZ9YWuXjY+zUtGdnkjOgzX3GwthGfFsYmyrSyrcRAocrN2nKZ6FsJQaQUEzufoQtBwSVlijuVYY9dC5MIx+IGWbo22dew+fjSkwaHy+7QlN3taVTOFlT9qDXkJKdj1WbiSC2o98Z61OpmbNClC2EA5fCHNfheuabC5d111i2l/4Xx6mkKl2EMDEKDsIT3gLzWH4ax8AvqSMmka3YAs0q5BWfOaTKH7U6WD7ne6/hm8Z+WKvlIfo6FVajm6f/ELYJQvwR7yUhLcAErO5aaUHyPFyk6POVQX0E/tbwRMSXwRmumfidrccPp1EID4RIFt0d4jnszU/D7ys0gvMDnw0thtVcpKnDiaSJMPsfeQ0f2ZYIXEz8Cu3PztYkZjzoKV6wT7Um9BX24RGnSQSLvVNfFRkFBv8gT9qLJ4V43kDhd845/B7iHjcIPlh1hLFz9nGCjz/QxFYIjP4BkyE6HBFW5lZ0tN6ive1BmDUKwe2y8PbZTM+wfOYf0t99QrzMaqn9zghz3kPY+vKjhNVixcNY1bNCduplyXP9AE7jlgBtK7DPDw8Y8vBhl96KkKnCUx9Lm+2dOq8ggs8uPOoFP/DxgiJOZwc26Gmoo3AkRc+/i2d/mioDsd08RflcG2dRdb0UeYReeEEFPpaAH/iYQWzs/Q/FPttSCPnWIuL4UKjfQqjP/2ikGSzLdtSf45nPIBagzhC044kf45nPJPI/hLkDbTopkjN7IIKZPtvGLRB/O2mF1iOyGW8IX/thzkvR3pT+r4EPMU6KAN+AlUzinYwNLAT3/yw6WO0hDk4IDk4IDk4IDk4IDk4IDk4IDk4IDk4IbgocnBAcnBAc/o2/BBgAWu+TFRGzndoAAAAASUVORK5CYII=</Image>
<Url type="text/html" method="GET" template="https://twitter.com/search" rel="searchform">
  <Param name="q" value="{searchTerms}"/>
  <Param name="partner" value="Firefox"/>
  <Param name="source" value="desktop-search"/>
</Url>
</SearchPlugin>


ACK to the concept, but it'd be more in line with everything else if the tests/Makefile.am handled its EXTRA_DIST, and the same for scripts/Makefile.am.


Alright, but maybe document this fact in the json? "This will issue a new output packet, if the value is different than the accumulator's current state at the time".


@Fishrock123 Thanks for the feedback. I think I've got it fixed.


yes, you're right.


Aren't you missing the gas constant here?


Ack, but maybe add tests for that :)


This throw should have a comment, it tools me a while to figure out why it is here.


Your preferred way of creating elements and attributes is likely easier to read than mine, isn't it? However, I think you're missing some quotes in here, wouldn't it be:  <span class="{'omission'}">


Hi, I am working on it. I had to nuke parts of the public PCMSolver repository and I guessed that's what caused all the trouble. The new version and interface with PSI4 should be ready soon. Sorry for the trouble!


I don't think so if it's the first one. First, you have the general stuff, and then the specific under its fieldset title.


better: System.out.println(vol+"m");


This change is already merged to phpnode/YiiRedis repo, but yours is way out of date. I've replaced your implementation with the vendor's code. You can delete this fork repo now.


Couldn't get it running with the router-service, due to some missing exposed properties.
I added them already. Latest commit resolves this.


Hey @Buckmarble - the upstream linux commits originate from www.kernel.org (Linus Torvalds and his maintainers).


That's a lot of merging Alvin.


kkkk


Is there an option to hide or disable the XMB icon only (without deleting Webman)


@levackt Can you move the artifact version definition to the BOM?


gvg,


(ee336bb) The title of the commit doesn't respect guideline ("type(scope): title (refs #<number>[, ...])")


Not a concern.

By design, callers to CertificateGeneator should lock and be responsible for caching certificates, if necessary. CertificateGenerator keeps a copy of the authority and its keypair only, and does not keep state of each generated cert.

Hence, you may enter here twice with the same subject and get two certs, but it's not this class' problem if that happens.


@vilchik-elena indeed, I will rename to ``importedGenericExceptions ``.


Попробуй сделать так чтобы не нужно было еще раз передавать диалог.


Спасибо, тронуло)


Way to go! Your first commit on this project!


that's right


@WHPODOO we try to be as close as the summernote code and avoid doing refactoring for the sake of cleaningness. The point of this commit is not to refactor so we keep a minimal diff, easier to review.


Need because Vapor on death cast aura Saronite Vapor(fix in core, thanks @Reamer)


sir plz send thi codes


I'm on the fence about having this functionality in Lumen—I'll think about it. If I were going to restore it, the previous implementation was more robust: these forms worked as expected `x.0`, `x.a.b`, `x.a.0.b.2`, for example. I would probably restore it from the git history.


I'll hope, what Animus start MoveChase after delay.


Outdated always false. Doesn't seems right.


I do not like this test. The ticket was about forwarding errors from the plugin, but the test check only require.js error. We should check if require.js forward errors from tests. Otherwise, if all errors are change to require.js error, this forwarding does not makes sense at all.


Spell spawn animation not working in Cata - replace on HandleEmote.


Add, because should destroy all blue dragon on wipe.


Kalec should speech only after KJ speech.


Lol sorry, I wasn't commenting on your message but the commit, I should have said "residue should be set to 0 on line 460". But it looks like the code has been cleaned up since this commit: https://github.com/Xilinx/linux-xlnx/blob/master/drivers/dma/xilinx/xilinx_dma.c#L499


First of all, 200% agreed that some of the info would be so much nicer as HUD or temporary OSD. Once we have a system for that, I agree we should redo the title bar.

However, for now we don't have HUD or OSD, so let's focus on what we can do with the title as long as that's the case.

In general, I think the guidelines for what we put title are:
- Stuff which could be useful to have at the title, ordered by importance for most users.
- But we have a length limitation so we can't put there everything.
- As long as we still have room left at the title, I don't think we should remove items just because they're not useful to some. If we're running out of room, then remove the items which are least useful to most people.

Specifically for the suggestions:
- removing save slot: I would miss it a lot at the title. I save/load and switch slots often, and it's much easier to observe at the title IMO. In fullscreen the title is invisible anyway, so it doesn't hurt anyone that it's there. But I'd be fine with moving it back to the end of bar. Also, if other than me no one finds it useful at the title and we're running out of room, sure, let's remove it.
- The output+deinterlace modes (the output is e.g. `Interlaced (Frame)` and the deinterlace mode if e.g. `bob bff`) are highly tied together and also really important when the content is actually interlaced and requires deinterlacing (especially when one has to cycle few deinterlace modes to find a proper one). As I mentioned earlier, I want to combine them in a useful way[*], but since some of the info is at PCSX2 and some of it is at GSdx, I still didn't do that. I do have plans though. For now, I suggest we keep it as is.
- limiter: restore to its own "section" as before but replace "None" with "Capped", well, I think it's important to know the "mode" only when it's not in "normal" mode. But sure, go ahead and restore it.

[*] A possible approach, for instance, would be to add `p` or `i` to the GSdx resolution, and if `i` then also add the deinterlace mode. E.g. `640x480p` or `64ox480i (top bff)`


I don't understand, why SummonTimer should be = 35000. I see in official server, what Kalec spawn simultaneously with Kil'jaeden.


Ouch... Other implementation are not affected?


Schema changes similar to this need to be placed in an update script in order to keep everything synced up. The case and quote changes are ok, but we should be using ALTER statements in an upgrade script in order to keep in sync and keep a clear change history on the schema. We also have the install/odm.php that should contain the same schema as the database.sql file.


it is good that you refracted the init and especially the run method. these are now a lot more easy to understand thanks to the refracting.


merging!


Also I guess it would be useful to store the inverse elements for each element just when they are calculated anyway during the group initialisation. I believe they will be useful for all further operations on the group.


@vilchik-elena indeed much better that way!


Oh, I forgot to tell you that, for development reasons, I just begun by writing a stylesheet that would deal with one file at a time, so I'm sorry if the document variables are annoying. I run them against Southey.
I'm going to redo my transformations so @setriplette can see them (since yours rewrote some of mine and they had some things missing).


:+1:, great, thanks.


@tamland heh. Guess my age is showing. :-)  ... I couldn't think of another reason for a compile error.


I don't follow, it's in the BOM at line 185.
Please clarify.
I just fixed the formatting in the POM to match the rest.

On Wed, Oct 7, 2015 at 4:56 PM, Henryk Konsek <notifications@github.com>
wrote:

> @levackt <https://github.com/levackt> Can you move the artifact version
> definition to the BOM?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/rhiot/rhiot/commit/c2ae9c392e9adf102bf4cf123b7f25a351df18c5#commitcomment-13640711>
> .
>


@levackt Can you sort the dependencies alphabetically? By groupId, then by artifactId.


@levackt Can you move this dependency to the non-test section?


Worth fixing these up for the new home on GitHub?