```
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

The Terraform execution plan has been generated and is shown below.
Resources are shown in alphabetical order for quick scanning. Green resources
will be created (or destroyed and then created if an existing resource
exists), yellow resources are being changed in-place, and red resources
will be destroyed. Cyan entries are data sources to be read.

Your plan was also saved to the path below. Call the "apply" subcommand
with this plan file and Terraform will exactly execute this execution
plan.

Path: /tmp/plan

+ aws_alb.ecs-example
    arn:                        "<computed>"
    arn_suffix:                 "<computed>"
    dns_name:                   "<computed>"
    enable_deletion_protection: "false"
    idle_timeout:               "60"
    internal:                   "true"
    name:                       "ecs-example"
    security_groups.#:          "1"
    security_groups.2512795270: "sg-f4706c8b"
    subnets.#:                  "2"
    subnets.1066062178:         "subnet-df46e097"
    subnets.2741754388:         "subnet-4bda2e67"
    vpc_id:                     "<computed>"
    zone_id:                    "<computed>"

+ aws_alb_listener.front_end
    arn:                               "<computed>"
    default_action.#:                  "1"
    default_action.0.target_group_arn: "${aws_alb_target_group.web-service.id}"
    default_action.0.type:             "forward"
    load_balancer_arn:                 "${aws_alb.ecs-example.id}"
    port:                              "80"
    protocol:                          "HTTP"
    ssl_policy:                        "<computed>"

+ aws_alb_listener_rule.product-service
    action.#:                  "1"
    action.0.target_group_arn: "${aws_alb_target_group.product-service.arn}"
    action.0.type:             "forward"
    arn:                       "<computed>"
    condition.#:               "1"
    condition.0.field:         "path-pattern"
    condition.0.values.#:      "1"
    condition.0.values.0:      "/products"
    listener_arn:              "${aws_alb_listener.front_end.arn}"
    priority:                  "2"

+ aws_alb_listener_rule.web-service
    action.#:                  "1"
    action.0.target_group_arn: "${aws_alb_target_group.web-service.arn}"
    action.0.type:             "forward"
    arn:                       "<computed>"
    condition.#:               "1"
    condition.0.field:         "path-pattern"
    condition.0.values.#:      "1"
    condition.0.values.0:      "/"
    listener_arn:              "${aws_alb_listener.front_end.arn}"
    priority:                  "1"

+ aws_alb_target_group.product-service
    arn:                                "<computed>"
    arn_suffix:                         "<computed>"
    deregistration_delay:               "300"
    health_check.#:                     "1"
    health_check.0.healthy_threshold:   "2"
    health_check.0.interval:            "30"
    health_check.0.matcher:             "200-299"
    health_check.0.path:                "/"
    health_check.0.port:                "traffic-port"
    health_check.0.protocol:            "HTTP"
    health_check.0.timeout:             "3"
    health_check.0.unhealthy_threshold: "2"
    name:                               "product-service"
    port:                               "80"
    protocol:                           "HTTP"
    vpc_id:                             "vpc-86d1cde0"

+ aws_alb_target_group.web-service
    arn:                                "<computed>"
    arn_suffix:                         "<computed>"
    deregistration_delay:               "300"
    health_check.#:                     "1"
    health_check.0.healthy_threshold:   "2"
    health_check.0.interval:            "30"
    health_check.0.matcher:             "200-299"
    health_check.0.path:                "/"
    health_check.0.port:                "traffic-port"
    health_check.0.protocol:            "HTTP"
    health_check.0.timeout:             "3"
    health_check.0.unhealthy_threshold: "2"
    name:                               "web-service"
    port:                               "80"
    protocol:                           "HTTP"
    vpc_id:                             "vpc-86d1cde0"

+ aws_autoscaling_group.ecs-cluster
    arn:                            "<computed>"
    availability_zones.#:           "<computed>"
    default_cooldown:               "<computed>"
    desired_capacity:               "3"
    force_delete:                   "false"
    health_check_grace_period:      "300"
    health_check_type:              "<computed>"
    launch_configuration:           "ecs-test-cluster"
    load_balancers.#:               "<computed>"
    max_size:                       "6"
    metrics_granularity:            "1Minute"
    min_size:                       "2"
    name:                           "ecs-test-cluster"
    protect_from_scale_in:          "false"
    target_group_arns.#:            "<computed>"
    vpc_zone_identifier.#:          "2"
    vpc_zone_identifier.1819431864: "subnet-547adc1c"
    vpc_zone_identifier.4228271568: "subnet-a3db2f8f"
    wait_for_capacity_timeout:      "10m"
    wait_for_elb_capacity:          "2"

+ aws_cloudwatch_log_group.ecs
    arn:               "<computed>"
    name:              "tf-ecs-group/ecs-agent"
    retention_in_days: "0"

+ aws_cloudwatch_log_group.product-service
    arn:               "<computed>"
    name:              "tf-ecs-group/product-service"
    retention_in_days: "0"

+ aws_cloudwatch_log_group.web-service
    arn:               "<computed>"
    name:              "tf-ecs-group/web-service"
    retention_in_days: "0"

+ aws_ecs_cluster.ecs-example
    name: "ecs-example"

+ aws_ecs_service.product-service
    cluster:                                    "${aws_ecs_cluster.ecs-example.id}"
    deployment_maximum_percent:                 "200"
    deployment_minimum_healthy_percent:         "100"
    desired_count:                              "3"
    iam_role:                                   "ecs-service-scheduler"
    load_balancer.#:                            "1"
    load_balancer.~2984810988.container_name:   "product-service"
    load_balancer.~2984810988.container_port:   "80"
    load_balancer.~2984810988.elb_name:         ""
    load_balancer.~2984810988.target_group_arn: "${aws_alb_target_group.product-service.id}"
    name:                                       "product-service"
    task_definition:                            "${aws_ecs_task_definition.product-service.arn}"

+ aws_ecs_service.web-service
    cluster:                                    "${aws_ecs_cluster.ecs-example.id}"
    deployment_maximum_percent:                 "200"
    deployment_minimum_healthy_percent:         "100"
    desired_count:                              "3"
    iam_role:                                   "ecs-service-scheduler"
    load_balancer.#:                            "1"
    load_balancer.~1218272944.container_name:   "web-service"
    load_balancer.~1218272944.container_port:   "80"
    load_balancer.~1218272944.elb_name:         ""
    load_balancer.~1218272944.target_group_arn: "${aws_alb_target_group.web-service.id}"
    name:                                       "web-service"
    task_definition:                            "${aws_ecs_task_definition.web-service.arn}"

+ aws_ecs_task_definition.product-service
    arn:                   "<computed>"
    container_definitions: "8261d357702502ac50c8e4ba0ad7dbee2ed7cc9a"
    family:                "product-service"
    network_mode:          "<computed>"
    revision:              "<computed>"

+ aws_ecs_task_definition.web-service
    arn:                   "<computed>"
    container_definitions: "c753c738e6a118fc26a6844755d30ae72a9ffb77"
    family:                "web-service"
    network_mode:          "<computed>"
    revision:              "<computed>"

+ aws_iam_instance_profile.ecs-container-instance
    arn:             "<computed>"
    create_date:     "<computed>"
    name:            "ecs-container-instance"
    path:            "/"
    roles.#:         "1"
    roles.990854494: "ecs-container-instance"
    unique_id:       "<computed>"

+ aws_iam_role.ecs-container-instance
    arn:                "<computed>"
    assume_role_policy: "{\n  \"Version\": \"2008-10-17\",\n  \"Statement\": [\n    {\n      \"Sid\": \"\",\n      \"Effect\": \"Allow\",\n      \"Principal\": {\n        \"Service\": \"ec2.amazonaws.com\"\n      },\n      \"Action\": \"sts:AssumeRole\"\n    }\n  ]\n}\n"
    create_date:        "<computed>"
    name:               "ecs-container-instance"
    path:               "/"
    unique_id:          "<computed>"

+ aws_iam_role.ecs-container-servicetask
    arn:                "<computed>"
    assume_role_policy: "{\n  \"Version\": \"2012-10-17\",\n  \"Statement\": [\n    {\n      \"Sid\": \"\",\n      \"Effect\": \"Allow\",\n      \"Principal\": {\n        \"Service\": \"ecs-tasks.amazonaws.com\"\n      },\n      \"Action\": \"sts:AssumeRole\"\n    }\n  ]\n}\n"
    create_date:        "<computed>"
    name:               "ecs-container-servicetask"
    path:               "/"
    unique_id:          "<computed>"

+ aws_iam_role.ecs-service-scheduler
    arn:                "<computed>"
    assume_role_policy: "{\n  \"Version\": \"2008-10-17\",\n  \"Statement\": [\n    {\n      \"Sid\": \"\",\n      \"Effect\": \"Allow\",\n      \"Principal\": {\n        \"Service\": \"ecs.amazonaws.com\"\n      },\n      \"Action\": \"sts:AssumeRole\"\n    }\n  ]\n}\n"
    create_date:        "<computed>"
    name:               "ecs-service-scheduler"
    path:               "/"
    unique_id:          "<computed>"

+ aws_iam_role_policy.ecs-container-instance
    name:   "ecs-container-instance"
    policy: "{\n  \"Version\": \"2012-10-17\",\n  \"Statement\": [\n    {\n      \"Effect\": \"Allow\",\n      \"Action\": [\n        \"ecs:CreateCluster\",\n        \"ecs:DeregisterContainerInstance\",\n        \"ecs:DiscoverPollEndpoint\",\n        \"ecs:Poll\",\n        \"ecs:RegisterContainerInstance\",\n        \"ecs:StartTelemetrySession\",\n        \"ecs:Submit*\",\n        \"ecr:GetAuthorizationToken\",\n        \"ecr:BatchCheckLayerAvailability\",\n        \"ecr:GetDownloadUrlForLayer\",\n        \"ecr:BatchGetImage\",\n        \"logs:CreateLogStream\",\n        \"logs:PutLogEvents\"\n      ],\n      \"Resource\": \"*\"\n    }\n  ]\n}\n"
    role:   "ecs-container-instance"

+ aws_iam_role_policy.ecs-service-scheduler
    name:   "ecs-service-scheduler"
    policy: "{\n  \"Version\": \"2012-10-17\",\n  \"Statement\": [\n    {\n      \"Effect\": \"Allow\",\n      \"Action\": [\n        \"ec2:AuthorizeSecurityGroupIngress\",\n        \"ec2:Describe*\",\n        \"elasticloadbalancing:DeregisterInstancesFromLoadBalancer\",\n        \"elasticloadbalancing:DeregisterTargets\",\n        \"elasticloadbalancing:Describe*\",\n        \"elasticloadbalancing:RegisterInstancesWithLoadBalancer\",\n        \"elasticloadbalancing:RegisterTargets\"\n      ],\n      \"Resource\": \"*\"\n    }\n  ]\n}\n"
    role:   "ecs-service-scheduler"

+ aws_launch_configuration.ecs-cluster
    associate_public_ip_address: "false"
    ebs_block_device.#:          "<computed>"
    ebs_optimized:               "<computed>"
    enable_monitoring:           "true"
    iam_instance_profile:        "ecs-container-instance"
    image_id:                    "ami-b2df2ca4)"
    instance_type:               "m4.large"
    key_name:                    "dev2"
    name:                        "ecs-test-cluster"
    root_block_device.#:         "<computed>"
    security_groups.#:           "1"
    security_groups.4001654439:  "sg-7d6c7002"
    user_data:                   "94cea30671c9d7e6d361fd5960ad1dbbfcd629a9"

<= data.template_file.cloud_config
    rendered:                "<computed>"
    template:                "#cloud-config\ncoreos:\n  units:\n   - name: update-engine.service\n     command: stop\n   - name: amazon-ecs-agent.service\n     command: start\n     runtime: true\n     content: |\n       [Unit]\n       Description=AWS ECS Agent\n       Documentation=https://docs.aws.amazon.com/AmazonECS/latest/developerguide/\n       Requires=docker.socket\n       After=docker.socket\n\n       [Service]\n       Environment=ECS_CLUSTER=${ecs_cluster_name}\n       Environment=ECS_LOGLEVEL=${ecs_log_level}\n       Environment=ECS_VERSION=${ecs_agent_version}\n       Restart=on-failure\n       RestartSec=30\n       RestartPreventExitStatus=5\n       SyslogIdentifier=ecs-agent\n       ExecStartPre=-/bin/mkdir -p /var/log/ecs /var/ecs-data /etc/ecs\n       ExecStartPre=-/usr/bin/docker kill ecs-agent\n       ExecStartPre=-/usr/bin/docker rm ecs-agent\n       ExecStartPre=/usr/bin/docker pull amazon/amazon-ecs-agent:$${ECS_VERSION}\n       ExecStart=/usr/bin/docker run --name ecs-agent \\\n                                     --volume=/var/run/docker.sock:/var/run/docker.sock \\\n                                     --volume=/var/log/ecs:/log \\\n                                     --volume=/var/ecs-data:/data \\\n                                     --volume=/sys/fs/cgroup:/sys/fs/cgroup:ro \\\n                                     --volume=/run/docker/execdriver/native:/var/lib/docker/execdriver/native:ro \\\n                                     --publish=127.0.0.1:51678:51678 \\\n                                     --env=ECS_LOGFILE=/log/ecs-agent.log \\\n                                     --env=ECS_LOGLEVEL=$${ECS_LOGLEVEL} \\\n                                     --env=ECS_DATADIR=/data \\\n                                     --env=ECS_CLUSTER=$${ECS_CLUSTER} \\\n                                     --env=ECS_AVAILABLE_LOGGING_DRIVERS=["awslogs"] \\\n                                     --log-driver=awslogs \\\n                                     --log-opt awslogs-region=${aws_region} \\\n                                     --log-opt awslogs-group=${ecs_log_group_name} \\\n                                     amazon/amazon-ecs-agent:$${ECS_VERSION}\n"
    vars.%:                  "5"
    vars.aws_region:         "us-east-1"
    vars.ecs_agent_version:  "latest"
    vars.ecs_cluster_name:   "ecs-example"
    vars.ecs_log_group_name: "tf-ecs-group/ecs-agent"
    vars.ecs_log_level:      "info"

<= data.template_file.task_definition_product_service
    rendered:              "<computed>"
    template:              "[\n  {\n    \"cpu\": 256,\n    \"essential\": true,\n    \"image\": \"${image_url}\",\n    \"memory\": 512,\n    \"name\": \"${container_name}\",\n    \"portMappings\": [\n      {\n        \"containerPort\": 8001,\n        \"hostPort\": 80\n      }\n    ],\n    \"logConfiguration\": {\n        \"logDriver\": \"awslogs\",\n        \"options\": {\n            \"awslogs-group\": \"${log_group_name}\",\n            \"awslogs-region\": \"${log_group_region}\"\n        }\n    }\n  }\n]\n"
    vars.%:                "4"
    vars.container_name:   "product-service"
    vars.image_url:        "275396840892.dkr.ecr.us-east-1.amazonaws.com/ecs-refarch-cloudformation/product-service:1.0.0"
    vars.log_group_name:   "tf-ecs-group/product-service"
    vars.log_group_region: "us-east-1"

<= data.template_file.task_definition_web_service
    rendered:              "<computed>"
    template:              "[\n  {\n    \"cpu\": 256,\n    \"essential\": true,\n    \"image\": \"${image_url}\",\n    \"memory\": 512,\n    \"name\": \"${container_name}\",\n    \"portMappings\": [\n      {\n        \"containerPort\": 8000,\n        \"hostPort\": 80\n      }\n    ],\n    \"logConfiguration\": {\n        \"logDriver\": \"awslogs\",\n        \"options\": {\n            \"awslogs-group\": \"${log_group_name}\",\n            \"awslogs-region\": \"${log_group_region}\"\n        }\n    }\n  }\n]"
    vars.%:                "4"
    vars.container_name:   "web-service"
    vars.image_url:        "275396840892.dkr.ecr.us-east-1.amazonaws.com/ecs-refarch-cloudformation/website-service:1.0.0"
    vars.log_group_name:   "tf-ecs-group/web-service"
    vars.log_group_region: "us-east-1"

Plan: 22 to add, 0 to change, 0 to destroy.
```


直接把*写成EventBus会报错


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/7ed4cb41-88dd-483f-8e88-33fb84d3d981 "ProfesorCognitivo"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/3b3c2a6c-fa90-4e9f-b037-3ceaa7548b49 "ProfesorCognitivo") deployed [ProfesorCognitivo](https://github.com/krlaguilar02/ProfesorCognitivo/releases/tag/deploy-ibm-yp-us-south-bjalpizar-dev-20170427-043619 "deploy-ibm-yp-us-south-bjalpizar-dev-20170427-043619") to [dev](https://console.ng.bluemix.net/apps/71e71400-bd03-476c-8e94-8fc8a5f09470 "ibm:yp:us-south:bjalpizar:dev"), including this commit


hahaha was trying how to upload a file


Except we need to make sure that the supplies `$attachment_id` is not `0`.


@ruchern

Sometimes you may need to.
I want my build files to be stored in ```public/build``` folder
```
public/build/js/app.js
public/build/css/app.css
public/build/fonts/
public/mix-manifest.json
```
I have disabled the ```processCssUrls``` and processing a customised version of ```bootstrap-sass```
So i have to copy font files from ```node_modules/bootstrap-sass/fonts/``` to ```public/build/fonts```
same goes for font-awesome.
Since v0.11.2 the ```mix.copy()``` started behaving differently.
The ```copy()``` method should have option to preserve folder structure.


circumventing CORS/ACAO response by using Allow-Control-Allow-Origin extension for Chrome


nice job. Please contact me, i am dealing some business with Apple Co. Plz join my Asis Super Developer Team


FWIW I was under the impression Netlify had instant cache invalidation. That's the best practice they propose on their [JAMstack site](https://github.com/jamstack/jamstack.org). In other words, cached assets should no longer require fingerprinting for cache busting as the CDN should use expires headers or ETags to do that work outside the Webapp and in the deployment pipeline (where it should be done).

I bring this up because I have a strong negative bias against Webpack. My controversial opinion but one shared by others and written about in more detail here:

https://medium.com/@jhabdas/webpack-is-your-achilles-heel-d3cd80821a4f

Cheers.


Hmm...still, maybe best to use it instead of the `strok()` part as I imagine some mime types might get misreported or may need to be filtered later on (e.g., SVGs).


Part A = good job
Part B = great job
Part C-Hand calculating odds ratios = excellent!
Part C-Analysis using statsmodels = looks good, but interpretation of odds ratio is not there yet
Something along these lines is what you need:
If you went to an undergraduate school with prestige = 2, you're 51% less likely to be admitted than a user with an undergraduate school of prestige = 1.
Similar story for odds ratio GPA
Questions 19 and 20 = see solutions.

Summary
Great work overall. Consider working on question 19 and 20, you are almost there.
There are parts of your code that prints output that doesn't seem to be relevant (or maybe it is relevant), to avoid this add comments to your code, or pass the output into a data frame (see solutions for question 19 and 20)


Printing this twice?


https://github.com/LineageOS/android_device_asus_msm8916-common/commit/ebf02f2e8fdc74ebcf2a2b15693affadd0b72a0f

original author of this commit :|


Thanks, @pharprecht! This thing, will help me a lot! Was going to add German locale, but stuck with rendering stuff. Anyway, thanks again!


yijghj


Hi Greg,

This library can be used to solve the inverse kinematics for a non-chain kinematic structure. This means it can put the humanoid robot body into arbitrary positions to achieve specific locations for both arms and legs (or other morphology).

This project was in collaboration with JSK Lab at U. Tokyo but it was never fully completed. I would be excited to have funding to cleanup this IK solver and to customize it to your needs. For more information about my professional services: http://picknik.io/


Yeah, it occurred to me shortly after I pushed that commit that I was actually dealing with a separate issue in my local dev environment. I hadn't gotten around to reverting it, but I should do that now.


@smortex Ah, I think I meant `$trusted['certname']`!
 https://docs.puppet.com/puppet/4.10/lang_facts_and_builtin_vars.html#examples


Or just open an issue for tracking. :D


The constructor now is very big. We should introduce some kind of builder which builds the CommunicationPanel - i will show you :)


Why not constants as the SIZE_INCREMENTER


Cooool. But don't do it again.


Esse rapaz é meio tonto, mas aprende Git sim.


No reason to--it only took a minute :P


Nicee but it could be a constant and if it is just for testing then it could go to the tests :)


Removed styles dir from last check in


lol :v i know


Overall the CommunicationPanel will get better with an Builder pattern


Part A = good job
Part B = great job
Question 4. Why are we doing this? In general, we create dummy variables to control for every possible value assigned to a column, therefore we can see the effect of each category on our output.
Part C. Hand calculating odds ratios
Question 10, Write this finding in a sentence.
Applicants who attend a #1 ranked college are 3.07x more likely to be admitted to grad school.

Question 11. You need something like this:
pd.crosstab(df.prestige_4,df.admit)
12/55
114/216
.52/.22 = 2.3636363636363638
Students who go to an undergraduate school ranked w/ the lowest prestige are 2.36x less likely than all other applicants to be admitted to UCLA.

Part C. Analysis using statsmodels
Question 15, the interpretation is something like this
If you went to an undergraduate school with prestige = 2, you're 50% less likely to be admitted than a user with an undergraduate school of prestige = 1.
Question 16, same as question 15

Summary:
Overall good work. Give yourself some time to understand odds ratio and the interpretation.
Your code looked clean, and it looks like you are ready to begin defining functions to make your work more effective.


```
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

The Terraform execution plan has been generated and is shown below.
Resources are shown in alphabetical order for quick scanning. Green resources
will be created (or destroyed and then created if an existing resource
exists), yellow resources are being changed in-place, and red resources
will be destroyed. Cyan entries are data sources to be read.

Your plan was also saved to the path below. Call the "apply" subcommand
with this plan file and Terraform will exactly execute this execution
plan.

Path: /tmp/plan

+ aws_alb.ecs-example
    arn:                        "<computed>"
    arn_suffix:                 "<computed>"
    dns_name:                   "<computed>"
    enable_deletion_protection: "false"
    idle_timeout:               "60"
    internal:                   "true"
    name:                       "ecs-example"
    security_groups.#:          "1"
    security_groups.2512795270: "sg-f4706c8b"
    subnets.#:                  "2"
    subnets.1066062178:         "subnet-df46e097"
    subnets.2741754388:         "subnet-4bda2e67"
    vpc_id:                     "<computed>"
    zone_id:                    "<computed>"

+ aws_alb_listener.front_end
    arn:                               "<computed>"
    default_action.#:                  "1"
    default_action.0.target_group_arn: "${aws_alb_target_group.web-service2.id}"
    default_action.0.type:             "forward"
    load_balancer_arn:                 "${aws_alb.ecs-example.id}"
    port:                              "80"
    protocol:                          "HTTP"
    ssl_policy:                        "<computed>"

+ aws_alb_listener_rule.product-service2
    action.#:                  "1"
    action.0.target_group_arn: "${aws_alb_target_group.product-service2.arn}"
    action.0.type:             "forward"
    arn:                       "<computed>"
    condition.#:               "1"
    condition.0.field:         "path-pattern"
    condition.0.values.#:      "1"
    condition.0.values.0:      "/products"
    listener_arn:              "${aws_alb_listener.front_end.arn}"
    priority:                  "2"

+ aws_alb_listener_rule.web-service2
    action.#:                  "1"
    action.0.target_group_arn: "${aws_alb_target_group.web-service2.arn}"
    action.0.type:             "forward"
    arn:                       "<computed>"
    condition.#:               "1"
    condition.0.field:         "path-pattern"
    condition.0.values.#:      "1"
    condition.0.values.0:      "/"
    listener_arn:              "${aws_alb_listener.front_end.arn}"
    priority:                  "1"

+ aws_alb_target_group.product-service2
    arn:                                "<computed>"
    arn_suffix:                         "<computed>"
    deregistration_delay:               "300"
    health_check.#:                     "1"
    health_check.0.healthy_threshold:   "2"
    health_check.0.interval:            "30"
    health_check.0.matcher:             "200-299"
    health_check.0.path:                "/"
    health_check.0.port:                "traffic-port"
    health_check.0.protocol:            "HTTP"
    health_check.0.timeout:             "3"
    health_check.0.unhealthy_threshold: "2"
    name:                               "product-service2"
    port:                               "80"
    protocol:                           "HTTP"
    vpc_id:                             "vpc-86d1cde0"

+ aws_alb_target_group.web-service2
    arn:                                "<computed>"
    arn_suffix:                         "<computed>"
    deregistration_delay:               "300"
    health_check.#:                     "1"
    health_check.0.healthy_threshold:   "2"
    health_check.0.interval:            "30"
    health_check.0.matcher:             "200-299"
    health_check.0.path:                "/"
    health_check.0.port:                "traffic-port"
    health_check.0.protocol:            "HTTP"
    health_check.0.timeout:             "3"
    health_check.0.unhealthy_threshold: "2"
    name:                               "web-service2"
    port:                               "80"
    protocol:                           "HTTP"
    vpc_id:                             "vpc-86d1cde0"

+ aws_autoscaling_group.ecs-cluster
    arn:                            "<computed>"
    availability_zones.#:           "<computed>"
    default_cooldown:               "<computed>"
    desired_capacity:               "3"
    force_delete:                   "false"
    health_check_grace_period:      "300"
    health_check_type:              "<computed>"
    launch_configuration:           "ecs-test-cluster"
    load_balancers.#:               "<computed>"
    max_size:                       "6"
    metrics_granularity:            "1Minute"
    min_size:                       "2"
    name:                           "ecs-test-cluster"
    protect_from_scale_in:          "false"
    target_group_arns.#:            "<computed>"
    vpc_zone_identifier.#:          "2"
    vpc_zone_identifier.1819431864: "subnet-547adc1c"
    vpc_zone_identifier.4228271568: "subnet-a3db2f8f"
    wait_for_capacity_timeout:      "10m"
    wait_for_elb_capacity:          "2"

+ aws_cloudwatch_log_group.ecs
    arn:               "<computed>"
    name:              "tf-ecs-group/ecs-agent"
    retention_in_days: "0"

+ aws_cloudwatch_log_group.product-service2
    arn:               "<computed>"
    name:              "tf-ecs-group/product-service2"
    retention_in_days: "0"

+ aws_cloudwatch_log_group.web-service2
    arn:               "<computed>"
    name:              "tf-ecs-group/web-service2"
    retention_in_days: "0"

+ aws_ecs_cluster.ecs-example
    name: "ecs-example"

+ aws_ecs_service.product-service2
    cluster:                                    "${aws_ecs_cluster.ecs-example.id}"
    deployment_maximum_percent:                 "200"
    deployment_minimum_healthy_percent:         "100"
    desired_count:                              "3"
    iam_role:                                   "ecs-service-scheduler"
    load_balancer.#:                            "1"
    load_balancer.~1255698280.container_name:   "product-service2"
    load_balancer.~1255698280.container_port:   "80"
    load_balancer.~1255698280.elb_name:         ""
    load_balancer.~1255698280.target_group_arn: "${aws_alb_target_group.product-service2.id}"
    name:                                       "product-service2"
    task_definition:                            "${aws_ecs_task_definition.product-service2.arn}"

+ aws_ecs_service.web-service2
    cluster:                                   "${aws_ecs_cluster.ecs-example.id}"
    deployment_maximum_percent:                "200"
    deployment_minimum_healthy_percent:        "100"
    desired_count:                             "3"
    iam_role:                                  "ecs-service-scheduler"
    load_balancer.#:                           "1"
    load_balancer.~687605616.container_name:   "web-service2"
    load_balancer.~687605616.container_port:   "80"
    load_balancer.~687605616.elb_name:         ""
    load_balancer.~687605616.target_group_arn: "${aws_alb_target_group.web-service2.id}"
    name:                                      "web-service2"
    task_definition:                           "${aws_ecs_task_definition.web-service2.arn}"

+ aws_ecs_task_definition.product-service2
    arn:                   "<computed>"
    container_definitions: "50fed009fe488437b7a7a1646080dc632c8d1920"
    family:                "product-service2"
    network_mode:          "<computed>"
    revision:              "<computed>"

+ aws_ecs_task_definition.web-service2
    arn:                   "<computed>"
    container_definitions: "3defe563d85bb1299efc8330cc18e914961209c8"
    family:                "web-service2"
    network_mode:          "<computed>"
    revision:              "<computed>"

+ aws_iam_instance_profile.ecs-container-instance
    arn:             "<computed>"
    create_date:     "<computed>"
    name:            "ecs-container-instance"
    path:            "/"
    roles.#:         "1"
    roles.990854494: "ecs-container-instance"
    unique_id:       "<computed>"

+ aws_iam_role.ecs-container-instance
    arn:                "<computed>"
    assume_role_policy: "{\n  \"Version\": \"2008-10-17\",\n  \"Statement\": [\n    {\n      \"Sid\": \"\",\n      \"Effect\": \"Allow\",\n      \"Principal\": {\n        \"Service\": \"ec2.amazonaws.com\"\n      },\n      \"Action\": \"sts:AssumeRole\"\n    }\n  ]\n}\n"
    create_date:        "<computed>"
    name:               "ecs-container-instance"
    path:               "/"
    unique_id:          "<computed>"

+ aws_iam_role.ecs-container-servicetask
    arn:                "<computed>"
    assume_role_policy: "{\n  \"Version\": \"2012-10-17\",\n  \"Statement\": [\n    {\n      \"Sid\": \"\",\n      \"Effect\": \"Allow\",\n      \"Principal\": {\n        \"Service\": \"ecs-tasks.amazonaws.com\"\n      },\n      \"Action\": \"sts:AssumeRole\"\n    }\n  ]\n}\n"
    create_date:        "<computed>"
    name:               "ecs-container-servicetask"
    path:               "/"
    unique_id:          "<computed>"

+ aws_iam_role.ecs-service-scheduler
    arn:                "<computed>"
    assume_role_policy: "{\n  \"Version\": \"2008-10-17\",\n  \"Statement\": [\n    {\n      \"Sid\": \"\",\n      \"Effect\": \"Allow\",\n      \"Principal\": {\n        \"Service\": \"ecs.amazonaws.com\"\n      },\n      \"Action\": \"sts:AssumeRole\"\n    }\n  ]\n}\n"
    create_date:        "<computed>"
    name:               "ecs-service-scheduler"
    path:               "/"
    unique_id:          "<computed>"

+ aws_iam_role_policy.ecs-container-instance
    name:   "ecs-container-instance"
    policy: "{\n  \"Version\": \"2012-10-17\",\n  \"Statement\": [\n    {\n      \"Effect\": \"Allow\",\n      \"Action\": [\n        \"ecs:CreateCluster\",\n        \"ecs:DeregisterContainerInstance\",\n        \"ecs:DiscoverPollEndpoint\",\n        \"ecs:Poll\",\n        \"ecs:RegisterContainerInstance\",\n        \"ecs:StartTelemetrySession\",\n        \"ecs:Submit*\",\n        \"ecr:GetAuthorizationToken\",\n        \"ecr:BatchCheckLayerAvailability\",\n        \"ecr:GetDownloadUrlForLayer\",\n        \"ecr:BatchGetImage\",\n        \"logs:CreateLogStream\",\n        \"logs:PutLogEvents\"\n      ],\n      \"Resource\": \"*\"\n    }\n  ]\n}\n"
    role:   "ecs-container-instance"

+ aws_iam_role_policy.ecs-service-scheduler
    name:   "ecs-service-scheduler"
    policy: "{\n  \"Version\": \"2012-10-17\",\n  \"Statement\": [\n    {\n      \"Effect\": \"Allow\",\n      \"Action\": [\n        \"ec2:AuthorizeSecurityGroupIngress\",\n        \"ec2:Describe*\",\n        \"elasticloadbalancing:DeregisterInstancesFromLoadBalancer\",\n        \"elasticloadbalancing:DeregisterTargets\",\n        \"elasticloadbalancing:Describe*\",\n        \"elasticloadbalancing:RegisterInstancesWithLoadBalancer\",\n        \"elasticloadbalancing:RegisterTargets\"\n      ],\n      \"Resource\": \"*\"\n    }\n  ]\n}\n"
    role:   "ecs-service-scheduler"

+ aws_launch_configuration.ecs-cluster
    associate_public_ip_address: "false"
    ebs_block_device.#:          "<computed>"
    ebs_optimized:               "<computed>"
    enable_monitoring:           "true"
    iam_instance_profile:        "ecs-container-instance"
    image_id:                    "ami-b2df2ca4)"
    instance_type:               "m4.large"
    key_name:                    "dev2"
    name:                        "ecs-test-cluster"
    root_block_device.#:         "<computed>"
    security_groups.#:           "1"
    security_groups.4001654439:  "sg-7d6c7002"
    user_data:                   "94cea30671c9d7e6d361fd5960ad1dbbfcd629a9"

<= data.template_file.cloud_config
    rendered:                "<computed>"
    template:                "#cloud-config\ncoreos:\n  units:\n   - name: update-engine.service\n     command: stop\n   - name: amazon-ecs-agent.service\n     command: start\n     runtime: true\n     content: |\n       [Unit]\n       Description=AWS ECS Agent\n       Documentation=https://docs.aws.amazon.com/AmazonECS/latest/developerguide/\n       Requires=docker.socket\n       After=docker.socket\n\n       [Service]\n       Environment=ECS_CLUSTER=${ecs_cluster_name}\n       Environment=ECS_LOGLEVEL=${ecs_log_level}\n       Environment=ECS_VERSION=${ecs_agent_version}\n       Restart=on-failure\n       RestartSec=30\n       RestartPreventExitStatus=5\n       SyslogIdentifier=ecs-agent\n       ExecStartPre=-/bin/mkdir -p /var/log/ecs /var/ecs-data /etc/ecs\n       ExecStartPre=-/usr/bin/docker kill ecs-agent\n       ExecStartPre=-/usr/bin/docker rm ecs-agent\n       ExecStartPre=/usr/bin/docker pull amazon/amazon-ecs-agent:$${ECS_VERSION}\n       ExecStart=/usr/bin/docker run --name ecs-agent \\\n                                     --volume=/var/run/docker.sock:/var/run/docker.sock \\\n                                     --volume=/var/log/ecs:/log \\\n                                     --volume=/var/ecs-data:/data \\\n                                     --volume=/sys/fs/cgroup:/sys/fs/cgroup:ro \\\n                                     --volume=/run/docker/execdriver/native:/var/lib/docker/execdriver/native:ro \\\n                                     --publish=127.0.0.1:51678:51678 \\\n                                     --env=ECS_LOGFILE=/log/ecs-agent.log \\\n                                     --env=ECS_LOGLEVEL=$${ECS_LOGLEVEL} \\\n                                     --env=ECS_DATADIR=/data \\\n                                     --env=ECS_CLUSTER=$${ECS_CLUSTER} \\\n                                     --env=ECS_AVAILABLE_LOGGING_DRIVERS=["awslogs"] \\\n                                     --log-driver=awslogs \\\n                                     --log-opt awslogs-region=${aws_region} \\\n                                     --log-opt awslogs-group=${ecs_log_group_name} \\\n                                     amazon/amazon-ecs-agent:$${ECS_VERSION}\n"
    vars.%:                  "5"
    vars.aws_region:         "us-east-1"
    vars.ecs_agent_version:  "latest"
    vars.ecs_cluster_name:   "ecs-example"
    vars.ecs_log_group_name: "tf-ecs-group/ecs-agent"
    vars.ecs_log_level:      "info"

<= data.template_file.task_definition_product_service2
    rendered:              "<computed>"
    template:              "[\n  {\n    \"cpu\": 256,\n    \"essential\": true,\n    \"image\": \"275396840892.dkr.ecr.us-east-1.amazonaws.com/ecs-refarch-cloudformation/product-service:1.0.0\",\n    \"memory\": 512,\n    \"name\": \"product-service\",\n    \"portMappings\": [\n      {\n        \"containerPort\": 8001,\n        \"hostPort\": 80\n      }\n    ],\n    \"logConfiguration\": {\n        \"logDriver\": \"awslogs\",\n        \"options\": {\n            \"awslogs-group\": \"${log_group_name}\",\n            \"awslogs-region\": \"${log_group_region}\"\n        }\n    }\n  }\n]\n"
    vars.%:                "2"
    vars.log_group_name:   "tf-ecs-group/product-service2"
    vars.log_group_region: "us-east-1"

<= data.template_file.task_definition_web_service2
    rendered:              "<computed>"
    template:              "[\n  {\n    \"cpu\": 256,\n    \"essential\": true,\n    \"image\": \"275396840892.dkr.ecr.us-east-1.amazonaws.com/ecs-refarch-cloudformation/website-service:1.0.0\",\n    \"memory\": 512,\n    \"name\": \"web-service\",\n    \"portMappings\": [\n      {\n        \"containerPort\": 8000,\n        \"hostPort\": 80\n      }\n    ],\n    \"logConfiguration\": {\n        \"logDriver\": \"awslogs\",\n        \"options\": {\n            \"awslogs-group\": \"${log_group_name}\",\n            \"awslogs-region\": \"${log_group_region}\"\n        }\n    }\n  }\n]"
    vars.%:                "2"
    vars.log_group_name:   "tf-ecs-group/web-service2"
    vars.log_group_region: "us-east-1"

Plan: 22 to add, 0 to change, 0 to destroy.
```


I'm on a DrupalCon sleep schedule, so I'm totally sleep-deprived and can't think straight... did I install the wrong version of the role or something?


Another good approach is to separate the commits of refactoring and the new implementation. In that way we will be more sure where to find the problems if there are such


Works and compiles well with the Catalyst driver (AMD) and with a recent NVIDIA driver.

OpenCL still needs to be activated for RGB color scaling in tonecurve.c:commit_params() (reverting c7c3323269811db4a5691792f1c1fcff8ebdf6c8)


i know


@ankurk91 Sorry for not putting myself in a clearer manner because the `sass-loader` already does the work for you. I do run `Bootstrap-sass` too and I see the fonts got copied out into the `public/` directory with the proper directory structure too. Hence, I thought this was not necessary.


why would it? if there are no changes it doesn't do anything


I don't think this is necessary, as there is already an override that adds this keyword.


probably a good thing to have in the update command, imagine we make changes on the backend that affect the db, if authors don't run makemigrations then they are going to get errors saying that there are "unapplied db changes" (or some error of the like, can't remember it off the top of my head)


I'm no QML expert, but I was curious as many that uses QML do seem to look/work more nicely...for example [Orion](https://github.com/alamminsalo/orion) (a twitch.tv client) and also [bomi](https://github.com/xylosper/bomi/commits/master) uses(/used) some QML code for the player theme/skin.

also I wouldn't say that QtQuick Controls 2 is for mobile only maybe the first one was more, the v2.x is more for all but oc leans more towards touch screen experience.

I do like idea that QML is for UI and c++ for backend stuff.
QML is like JS on steroids and it's great for UI stuff...as many do find QML to be better for UI than C++ ... KDE remade their plasma desktop to use QML instead of C++ as it was more slower..

anyway I wouldnt think it could hurt to at least check out how/what you could do with QML, I don't say u need remake the whole UI with QML (like orion) maybe just some parts like bomi has.

PS. have u heard about [OVD](http://developer.amd.com/tools-and-sdks/opencl-zone/amd-accelerated-parallel-processing-app-sdk/) (Open Video Decode): Another API from AMD Graphics, designed to be a platform agnostic method for software developers to leverage the Universal Video Decode (UVD) hardware inside AMD Radeon graphics cards. ...it seems that only for Windows and Linux but no MAC


Practice


That would only be a problem if we didn't commit migration files, which hopefully wouldn't happen.

I haven't been able to think of it causing any new issues on top of how we use it, so it should be safe.


ty


towards #3.


Sorry to bother @Shevchik, but this looks like a server-side mod, why does it need compatibility with protocolsupport?


@vincentchabannes we should probably also have an interface in json for Fit ! it would be very useful in models to have that


only one l usefull -> useful


Awesome!


[Your benchmark job](https://github.com/JuliaLang/julia/commit/67fdcf2f101bc4d7e657615c817c59e626299ed9#commitcomment-21926759) has completed - possible performance regressions were detected. A full report can be found [here](https://github.com/JuliaCI/BaseBenchmarkReports/blob/49c11a932a23388c0091f63874123b1e2fde734a/daily_2017_4_27/report.md). cc @jrevels


That's not an objective. That's what you are going to do to reach an objective. An objective can't be something like "choosing something" that can be said to succeed by just choosing it. An objective has to be in the problem domain: "Find a method that increases by 10% the current accuracy of methods". This is an intermediate task you have to undertake to reach your objective. It's obvious that you have to choose the best technique; on the other hand, soft computing and machine learning are not mutually exclusive, and machine learning is what you do to learn with a machine, so anything you test is going to be machine learning.
Baseline is: change this to a subobjective, and choose very well the words you use so that they are precise, non redudant, and don't overlap with each other.


chạy python validate.py của a trung để hoàn thành Synopsis và option nhá


You need to rebase and create a pull request.


Accidentally created branch from cartFunctionalityBranch, not master.

Both branches were at the same state, so no adverse effects.


@actuariat would you mind filing a feature request at https://iterm2.com/bugs?


Resolves #36


"Describe" something is not an objective. An objective has to be measurable. *Characterize* would be an objective, but it is not measurable either. And, as I have said before, this is a task you have to do to reach your objective. If you don't characterize your environment you can barely solve the problem.
Ditto for the second one. "Defining" is not measurable. The metrics are probably there and you just get to choose them. And it is also a task you have to do to solve your problem.
I spent quite a lot of time with @fergunet defining the objectives. It's something you have to do, it is very important, and it is not as easy as it would seem... It's probably better to have an issue and not comments in the text, also.


Так ведь через `has_many :tickets` ассоциируется сколько угодно билетов по станцией, разве нет?


Hi @DivineFrancis, unfortunately I don't fully understand French. It sounds like this is a script error, not a plugin error. Please only report errors related to the brackets-to-photoshop plugin. Thanks!


Good point!


`private display_context_proxy<game_board>` - since the versions you removed were private too.


Nice work, thanks for reading a lot of my crappy code ^^


Oh wait, some were and some weren't... huh... well, you could do private inheritance and then publicize them with a using-declaration, I suppose.


I guess it's not a big deal to publicize units() though.


Congrats!


They are not friends.


can it be that this commit is causing CEC issues as described here? https://github.com/Pulse-Eight/libcec/issues/342 and here https://github.com/Pulse-Eight/libcec/issues/343


Does it mean that if I create a collection of datasets which are derived from others, URLs will point to remote URLs and not relative ones as it would do if I install into a dataset? If so - "not sure"


Don't give up, you're so close.

Take a closer look at pswdhash and how it's created vs say any other code that calls sha1 ;)


![](https://github.trello.services/images/mini-trello-icon.png) [Swag page](https://trello.com/c/IwslvSPh/34-swag-page)


add README file


Hey @andey ,

I Forked this and noticed you did as well.

I've been having some intermittent issues where i get "invalid username" on some calls, and they never make it to NMI. I'm wondering if there is some sort of thread safety issue with the way this gem handles authentication. Do you mind explaining what passing in username and password here does? And how are you implementing it in your code? I'm curious if this will fix my issue.

Thanks!


Just attaching
https://www.nikhef.nl/~form/forum/viewtopic.php?f=3&t=155
and
https://www.nikhef.nl/~form/forum/viewtopic.php?f=4&t=185&p=556
to this commit for future reference.


@ZeroZeroOne bug已经fix，可以用了现在。
另外， 以后遇到问题请开issue，别在某次提交里面进行评论。


can remove `stop_event` from here (and same for others)


@dsommers, @selvanair, this is squashed version, please check it. If the code is fine, I'll arrange comments and doxygen.


can also remove `stop_event` here


Sorry. I had a real shitty day yesterday in real life.

Every little change that I add in can cause a ton of problems because this addon is so complicated. It was probably the most complicated addon in Kodi when it was the original TV Guide. Now it is a monster.

There are so many tricks and hacks to get around the limitations of the kodi api that I don't always understand what the consequences of adding something will be until someone turns on a setting I have forgotten about and everything falls apart in a smelly heap.

Until you have spent a week of hard debugging trying to find out what you did wrong and then find out it was someone else's code that you added in, you won't understand my position.

This is never going to be a tidy project. There is a lot of hurriedly copy and pasted code that should go in functions and libraries. Every time I do try a clean up it breaks something else that I have forgotten about.

It also takes a ton of time which I just don't have or have the energy for.

I spend a long time trying to work out why Krypton was so slow with hls streams recently. Eventually it turned out the videoplayer developer had deliberately "tidied up" the hls code and fucked it up expecting the ffmpeg team to pick up the mess. They do work in their spare time too and don't have their own criteria for how their software works which is different that kodi's.
http://trac.kodi.tv/ticket/17422

Here is part of an earlier conversation I had about a skin developer that started going the same way which is why I already have a high level of anxiety about all these new changes. It ended up with him forking.
https://github.com/primaeval/script.tvguide.fullscreen/pull/60#issuecomment-244541887

I don't like change for the sake of change only if it makes life better. Windows7 is still better than Windows10 ad-infested bloatware. Nokia phones are more reliable and longer lasting than iPhones. Paper is still more detailed for capturing a drawing than any computer input device. Jarvis is better than Krypton. Confluence is better than Estuary.


解决了就好   这只是一个非常简单的demo


Fixes https://github.com/MetaMask/metamask-plugin/pull/1347 and https://github.com/MetaMask/eth-block-tracker/issues/8


Sweet - just got off the phone, so my hotspot is back.

Thx for the hint, will attack that in a sec. Should be fine from here by the sound of it.


[plugin.video.edltv] 1.0.0


argh that was an accidental addition :scream:

How bad of me.

No objections at all against 19.3, will make a PR


costa/setPass.exp


@jludvice check Rachel's comment to sum up the discussion we had yesterday about looped callbacks.

@kahboom thanks for the explanation 👍


[Oral Questionnaire for building an online procurement System for Egerton University.docx](https://github.com/procurement-developers/Procurement/files/960592/Oral.Questionnaire.for.building.an.online.procurement.System.for.Egerton.University.docx)


yes, exactly, all download.php files in fact


we still need this ;)


Fixes and closes #3


Hi

After adding
#include <SoftwareSerial.h> in Arduino its started working

thanks


BWildblood


two line words


Restart is slow (minimum of 1024 jesd clock cycles), so doing a MultiReg + rising edge detection should be fine.
I'll consider the others solutions.


Indeed, I'll have a mechanism for that similar to what we are doing on others design.


But you keep the high order function constructor. I was saying that I don't know if the object is created when you use that function in the test even if you haven't called it yet. We should ask to the experts 🤔


Updation of readme file


There is no more log visible on Travis for the code_layout test since this commit.


烦烦烦


![](https://github.trello.services/images/mini-trello-icon.png) [design upgrades](https://trello.com/c/b7x5IVrW/115-design-upgrades)


I guess that we never call do_action with on_success in options?


ok


注意以后构建数据库时，列名不能与数据库关键字重复！！！！


(good catch :))


We should be able to remove that, I need to setup ARTIQ here to be able to test. I'll do it in the next days. I create an issue for that.


test


なにしてんの
くたばRE


wwww


changed the case in the name of the project in bower.json


ハローこんにちわ久しぶり


Shortcodes in a markdown file? Rad.


Congrats!


https://secure.php.net/manual/de/function.preg-quote.php - an even more simple solution


thanks.


I am not sure if this is a good idea to require not actually needed permissions. This is quite strange because of Feedly is a wrapper which is giving you wrapped content. Isn't there an option to get a wrapped icon from feedly domain instead of getting just a link to an icon and fetching it from other domains? It was working fine somehow for non-blog subscriptions right?
Anyway is there an option to require such permissions later in options instead of when installing for those who are ready to grant them?


ggg


ggrr


frf


When I run this line, I find an error. The error is following.
Using TensorFlow backend.
Extracting ../../MNIST_data\train-images-idx3-ubyte.gz
Extracting ../../MNIST_data\train-labels-idx1-ubyte.gz
Extracting ../../MNIST_data\t10k-images-idx3-ubyte.gz
Extracting ../../MNIST_data\t10k-labels-idx1-ubyte.gz
C:\Users\Administrator\Desktop\conditional_vae\cvae_keras.py:29: UserWarning: The `merge` function is deprecated and will be removed after 08/2017. Use instead layers from `keras.layers.merge`, e.g. `add`, `concatenate`, etc.
  inputs = merge([X, cond], mode='concat', concat_axis=1)
C:\Users\Administrator\Anaconda3\envs\tensorflow\lib\site-packages\keras\legacy\layers.py:460: UserWarning: The `Merge` layer is deprecated and will be removed after 08/2017. Use instead layers from `keras.layers.merge`, e.g. `add`, `concatenate`, etc.
  name=name)
Traceback (most recent call last):
  File "C:\Users\Administrator\Desktop\conditional_vae\cvae_keras.py", line 29, in <module>
    inputs = merge([X, cond], mode='concat', concat_axis=1)
  File "C:\Users\Administrator\Anaconda3\envs\tensorflow\lib\site-packages\keras\legacy\layers.py", line 460, in merge
    name=name)
  File "C:\Users\Administrator\Anaconda3\envs\tensorflow\lib\site-packages\keras\legacy\layers.py", line 121, in __init__
    self(input_tensors, mask=input_masks)
  File "C:\Users\Administrator\Anaconda3\envs\tensorflow\lib\site-packages\keras\engine\topology.py", line 578, in __call__
    output = self.call(inputs, **kwargs)
  File "C:\Users\Administrator\Anaconda3\envs\tensorflow\lib\site-packages\keras\legacy\layers.py", line 214, in call
    return K.concatenate(inputs, axis=self.concat_axis)
  File "C:\Users\Administrator\Anaconda3\envs\tensorflow\lib\site-packages\keras\backend\tensorflow_backend.py", line 1555, in concatenate
    return tf.concat([to_dense(x) for x in tensors], axis)
  File "C:\Users\Administrator\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\ops\array_ops.py", line 1075, in concat
    dtype=dtypes.int32).get_shape(
  File "C:\Users\Administrator\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\ops.py", line 669, in convert_to_tensor
    ret = conversion_func(value, dtype=dtype, name=name, as_ref=as_ref)
  File "C:\Users\Administrator\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\constant_op.py", line 176, in _constant_tensor_conversion_function
    return constant(v, dtype=dtype, name=name)
  File "C:\Users\Administrator\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\constant_op.py", line 165, in constant
    tensor_util.make_tensor_proto(value, dtype=dtype, shape=shape, verify_shape=verify_shape))
  File "C:\Users\Administrator\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\tensor_util.py", line 367, in make_tensor_proto
    _AssertCompatible(values, dtype)
  File "C:\Users\Administrator\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\tensor_util.py", line 302, in _AssertCompatible
    (dtype.name, repr(mismatch), type(mismatch).__name__))
TypeError: Expected int32, got list containing Tensors of type '_Message' instead.


Although this is nice, this ends up fooling users because localWorkers do not work pretty well. I have been commenting that as more workers much slower the compiler... 😢
```
› mvn clean package -Dgwt.localWorkers=1
[INFO]    Compilation succeeded -- 27.795s
› mvn clean package -Dgwt.localWorkers=3
[INFO]    Compilation succeeded -- 28.631s
› mvn clean package -Dgwt.localWorkers=5
[INFO]    Compilation succeeded -- 31.938s
› mvn clean package -Dgwt.localWorkers=1
[INFO]    Compilation succeeded -- 26.480s
```
(just executed sequentially right now, repeated =1 just to confirm, pretty bad performance test, but suppose it is enough to demonstrate my point)
And this is rxcanvas-gwt, in big projects this is worst. And, and important fact! if you do not have much RAM memory and you use 1C workers you'll probably don't get it work, so IMO is much better to use 1 be default so much less memory and same speed.


Also the formatting of the header.title also reverts to defaults when you $reload the view 😞


Thank you for adding restart_count csr. Will increments to the counter be
reported in ARTIQ Logging? Seems like user should know that a link reset
happened so current experiment rep can be flagged as bad.

On Thu, Apr 27, 2017 at 2:11 AM enjoy-digital <notifications@github.com>
wrote:

> We should be able to remove that, I need to setup ARTIQ here to be able to
> test. I'll do it in the next days. I create an issue for that.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/m-labs/artiq/commit/79c339d4ac1440b24b84a2f4210e773a7ee029c5#commitcomment-21927787>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ATl51m_QuWpV0qCQpKA5ZQ25exe43jLzks5r0DGpgaJpZM4NJsCF>
> .
>
--
Joe Britton
Sensors and Electron Devices
Army Research Lab
2800 Powder Mill Rd
Adelphi, MD 20783
301-394-3130
joseph.w.britton5.civ@mail.mil


@Vidrep be sure to open an issue when you notice such failure on an architecture-enabled recipe. Thanks!


Might be related to this

> Scheduled - We need to get our regular partition maintenance query back on track, which will require an interruption in log parts processing. During the maintenance, we expect jobs to continue running, including any deployment steps and GitHub status updates, but realtime log streaming and lookup of log output from *public* jobs that were running from the beginning of maintenance will be unavailable.

https://www.traviscistatus.com/

Let's wait and see


![Image text](https://github.com/Endless-Android/MyViewDrawDemo/blob/master/image/GIF.gif)


Mothership:
- Changed position, shape, and size
- Shield reset script is tied to a check on whether the shield object is "active"

Shields:
- Changed shape and size
- Shield deactivates upon ball's collision with it, instead of collision with the mothership

Drones:
Now positioned behind the player.  Parent object destroys when all child objects are destroyed.

Energy:
Changed movement to start at speed = 0, and accelerate.


以上是对仓库的操作，是通过命令行创建一个仓库，


I don't understand why you put the exit code '100' instead of '1'. Did you just want to distinguish between normal errors and this?


😄 hehe 1C has been removed! 👍


This is not actual part of the patch, thus will be removed. Just testing if there exists getting the assert .


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/bbd03871-45c1-4377-b52e-3f5e51a59df1 "TravelDevOps"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/1d323200-e247-49e1-81e1-59555c6773d1 "TravelDevOps") deployed [TravelDevOps](https://github.com/plainfield/TravelDevOps/releases/tag/deploy-ibm-yp-us-south-IBM-PoCs-DevOps-20170427-062209 "deploy-ibm-yp-us-south-IBM-PoCs-DevOps-20170427-062209") to [DevOps](https://console.ng.bluemix.net/apps/095fd8a4-3869-4422-ba85-69b961765d24 "ibm:yp:us-south:IBM PoCs:DevOps"), including this commit


sorry for the accusation!


Excellent! :+1:  @david-a-wheeler


Hello @pedrobaeza

Yes thanks. It is very nice to catch it so quickly since github displaying system made it seem really innocuous. I have reverted it with https://github.com/odoo/odoo/commit/75d9674d459


Ah... somehow broke the live website quite badly...
Fixing it. Sorry guys :(


scapy-pppoe


aaaaa


this is my 13th day, and i stil do not konw what to, how to do it


I'm agree, it could be very usefull.


Hey, @iivashchenko ! Yes you are right regarding `buffer.notify`, observables and erasing messages immediately. One point I still want to make though. As you say, `messages` in `customerData` is observable. `this.messages` points to the same observable via the expression `this.messages = customerData.get("messages") ...`. Now, when we set `messages` in `customerData` to `{}` this immediately propagates the change back to `this.messages` and `this.messages` is set to `{}` too. So, at the end of the initialization of `messages.js` `this.messages` is ALWAYS empty.
The question is why we still see the messages appearing on pages at all? This happens because something[1] in magento codebase updates the contents of `messages` in `customerData` AFTER `messages.js` completes initialization. Since `messages` in `customerData` and `this.messages` both point to the same observable the messages are propagated to [html](https://github.com/magento/magento2/blob/develop/app/code/Magento/Theme/view/frontend/templates/messages.phtml#L19) that renders them. So it seems to me that the fact that messages appear is just due to luck of `messages.js` being initialized early enough.
But if something updates the `messages` in `customerData` after we clear them in `messages.js` why don't the messages re-appear then on every page load? What removes the messages after all? The answer is `disposableCustomerData`. It is registered in your code in line 27 and is fired 3 sec after we set `messages` to `{}` in the init of `messages.js`. This luckily happens to be long enough for the anything that updates the messages to complete.

Because of the above I don't think that there is a difference between the current approach and the approach I proposed in terms of timeout effects.
If you would like to clear the messages immediately in the customer data but still show new messages that are added to customerData at run time, you might need to register an observable callback on messages where you could copy the new messages, show them on front, and ensure that `messages` in `customerData` remain empty (if that is what you want).

[1] Here I suspect that XHR request fired by `customerData` to the backend in order to get section data takes long enough time.

PS. Sorry for the comment length, I don't have time to write a shorten int. My motivation here is: I spent much time debugging this issue because of a particular use-case and would like to share the findings with the community.


Are you sure index buffers are never registered? If they are, then this registration case should still be present, albeit simpler, without actual conversion


Yes indeed. Thanks!


@thomasfowler Would you please check this?


since this is the generic addref, removing this affects more than just index buffers - are you sure about that?


jkkkkjjkj


Тест


EmuIndexBuffer field could be entirely removed now, can't it?


I've incorporated your changes back into the master branch.


initial commit


@freman
Dont know how I missed that, after scanning that code a million times.

The password hash that goes on the CheckPassword command line is  :

- The lowercase SHA-1 of the entered passwd
- xor with the magic number returned by InitSession, as uppercase HEX
- SHA-1 that, and shift to uppercase

I missed the bit about the 1st pass being a _lowercase_ SHA-1, which is different to the rest.

Still fails, but must be closer now :)


てｔ


Is g_bBadIndexData still used anywhere? If not, it can be removed too


test


No unit test for this?  Would be nice use it as a reference of how to use the query.  Even a bit of JavaDoc at the class-level with a small inline example would be useful.


Why did you mix changes for different issues in such a commit?


as long as the global pIndexData is only set here, this patch must stay enabled


I owe u a beer

or 2


![](https://github.trello.services/images/mini-trello-icon.png) [Dokan Add New product refill data on Error submission](https://trello.com/c/PJQvamBE/87-dokan-add-new-product-refill-data-on-error-submission)


это правильно


reduce from 5 to 3


`messageReceived` and `signalReceived`?


этот код суммирует не элементы списка, а числа от 0 до длины списка.
если ваш список будет [1,1,1,1,1], Вы увидите разницу.


missing import of WebViewClient in this Activity, won't let code compile.


@scottgonzalez Any update on when a release may be made?


Congrats too!


It seems sync losses only happen a few times during initialization and it's stable afterwards. We can handle them in a simpler way: delay DRTIO link establishment until the JESD stuff behaves.


это код предполагает, что у Вас между перым и вторым символом только один символ, но это в общем случае не так. Например, функция может быть вызвана так: `sum_of_unicodes('a', 'z')`
Все остальное (название, возврат результата) - отлично!


moan...


Yes, I agree. I had failed to use Response<Integer> that time and decided to use bean Id instead to put it into Response. But surely it can be explicitly wrapped from ordinary Integer in REST method body. Thanks.


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/fef3767f-e573-44d5-97a7-71f9efa96fab "simple-toolchain-20170427050200944"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/5429e87c-09fc-4d51-9526-441b7e2d6c37 "Demotoolchain-20170427050200944") deployed [Demotoolchain-20170427050200944](https://github.com/sarangatripathy/Demotoolchain-20170427050200944/releases/tag/deploy-ibm-yp-us-south-sarang.tripathy-in.ibm.com-Tripathy_sarangWorkspace-20170427-065409 "deploy-ibm-yp-us-south-sarang.tripathy-in.ibm.com-Tripathy_sarangWorkspace-20170427-065409") to [Tripathy_sarangWorkspace](https://console.ng.bluemix.net/apps/df55744e-3dfc-4756-a587-23f8340fa067 "ibm:yp:us-south:sarang.tripathy@in.ibm.com:Tripathy_sarangWorkspace"), including this commit


Hi @harish86, now we can use Vue.currentUser.token to get token


My bad. I missed noticing put in release even after searching multiple times. Sorry about that !


Looks good to me.


我已经把host改成本地，帐号也改为root,密码为root


This masks the `tags()` function and therefore breaks the tags functionality in 3.5.3.


add in README to let people pay attention for different OS distribution , the name is diff


суммируемые числа не в диапазоне от 1 до 1000000, т.к. уже начиная с i=13, 3**13 будет больше 1000000.


Yikes, a typo in the commit message.


Here's at least one Qubes dev/user complaining about "paranoid" being too loaded a term (note his post predates this debate): https://groups.google.com/d/msg/qubes-users/TB1mhB2cp18/lmuddbMpCAAJ

FWIW, I think `--safe-mode` sounds really neutral and also conveys the meaning pretty well... Perhaps we should adopt this one?

/cc @marmarek


@panpan0000 OK, I'll mention that this is only an example configuration when control interface is "eth1"


I should have double checked, glob-stream 6 was released since I first looked at this, now at 6.1.0.


I'm sorry = have I created a problem?
Because there was a number of minor issues...
How can I best help you?

describe the change you want to do?

Or rewind it - and check them in one by one?


то есть я не то суммирую ?


accepted


![](https://github.trello.services/images/mini-trello-icon.png) [Create mockup design for list employees [4 hours]](https://trello.com/c/0S1VEMrQ/11-create-mockup-design-for-list-employees-4-hours)


![](https://github.trello.services/images/mini-trello-icon.png) [It's hard to copy/paste Device Settings into an email AND edit them (i.e. add a new basal segment)](https://trello.com/c/ICFnscSF/115-it-s-hard-to-copy-paste-device-settings-into-an-email-and-edit-them-i-e-add-a-new-basal-segment)


haode


[DateRangeInput] Fix various bugs (#1041)

Preview: documentation
Coverage: core | datetime


It's not used at the minute, I've left it there for now but I'll be cleaning things up after I have everything working properly.


Settings saved in settings.xml in app directory.


Hi @blomman9 .
I just discovered that you forked my PhpMydomo, and added the Tellstick support.
If it works well, it would be nice to send me a PR....
Le'ts continue the discussion here, if you mind: https://github.com/phpMyDomo/phpMyDomo/issues/54

Thank you


OK. Sounds like a straightforward way to start.

On Thu, Apr 27, 2017 at 2:50 AM Sébastien Bourdeauducq <
notifications@github.com> wrote:

> It seems sync losses only happen a few times during initialization and
> it's stable afterwards. We can handle them in a simpler way: delay DRTIO
> link establishment until the JESD stuff behaves.
>
> —
> You are receiving this because you commented.
>
>
> Reply to this email directly, view it on GitHub
> <https://github.com/m-labs/artiq/commit/79c339d4ac1440b24b84a2f4210e773a7ee029c5#commitcomment-21928047>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ATl51gZ2w5aMrIAXpVo6FuIIC7zHbIYjks5r0DqsgaJpZM4NJsCF>
> .
>
--
Joe Britton
Sensors and Electron Devices
Army Research Lab
2800 Powder Mill Rd
Adelphi, MD 20783
301-394-3130
joseph.w.britton5.civ@mail.mil


это не расстояние между точками


это не абсолютное значение числа


16, 17 accepted


Splitting: To split back-end from front-end you can create one directory for front-end, and second directory. for back-end. Both projects can use package.json and Yarn/Npm for dependencies. Yarn supports full flattening, so you get similar bundle size to Bower's.

Complexity: It's easy/familiar to start with bower avoiding this "complexity", but it ends with either tenths of <script src=""> in production, or by implementing bundler by hand with something like gulp or grunt (these tools aren't bundlers but for automating tasks).

Yarn dropping support for bundling dependencies from bower.json doesn't mean it isn't reasonable to use it for new projects (you just need to put your dependencies in package.json). I don't see how it's misleading.


This change leads to an error for me:

[748] error @1.187632> [hit #1]request to POST / crashed: Not enough arguments for grep at /home/magnus/kohaclone//Koha/Illbackends/NNCIPP/Base.pm line 136, near "%out;"

Commenting out line 136 makes things run again.


@panzergame : Hello, Do you think exposure, range, envlightenergy have to be updated both in UpdateBackground AND UpdateWorldSettings?


Index buffers always live within the CPU Virtual address space, so there is no need to register them

Additionally, debug versions of the XDK libraries specifically check if D3DResource_Register is called on an index buffer (if so, it triggers an error)


//exception handling


@dairejpwalsh any update sir


Once we are sure this works properly, then yes!


Happy naming!


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/efced7ac-9b0f-4200-8ee1-23a416976b72 "CCCloudChatPBKS"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/df96631c-d5ed-44b3-a52e-1cbf4c8876f6 "CCCloudChatPBKS") deployed [CCCloudChatPBKS](https://github.com/KevinSchroetter/CCCloudChatPBKS/releases/tag/deploy-ibm-yp-us-south-CCBluemix-dev-20170427-071444 "deploy-ibm-yp-us-south-CCBluemix-dev-20170427-071444") to [dev](https://console.ng.bluemix.net/apps/0a3c4394-a44f-487d-ac94-f4d1989dcc7d "ibm:yp:us-south:CCBluemix:dev"), including this commit


Looks good


这是还没有完成的版本


it's not a comment it's just text


Sai!

Client gửi request tới server, server nhận request.
TH1: Nếu resource bị busy sẽ trả lại HTTP code 202 (Accepted) hoặc 204 (No Content). Sau đó ở phía server sẽ queue cái request này lại, định kỳ check xem resource đã được release lock chưa. Nếu resource đã được release lock và chưa hết số lần retry hoặc timeout thì thực hiện.
TH2: Nếu resource không bị busy thì sẽ trả lại HTTP code 200 (OK) và thực hiện luôn request.

Như vậy, client chỉ cần gửi request 1 lần duy nhất.


Ý tưởng hay nhưng không ai dùng cách tạo 2 WSGI server cả.
Idea này có thằng implement rồi, nhưng nó ở layer sâu bên dưới, đó chính là epoll của Linux kernel và kqueue của BSD. Để dễ tiếp cận hơn chính là goroutines của Golang.
Nếu làm như cách của em thì tầng application rất nặng nề, chưa hẳn đã nhanh hơn. người ta chỉ làm cách này ở tầng dưới để control dễ hơn.
Tham khảo: https://kipalog.com/posts/Goroutines-under-the-hood


`np.resize()` is a very useful thing. Perhaps better to using it instead of `second_as_first_cycle()`


@haminhcong check comments ở ^


Thank you for this release, however the release addresses SRAM configuration and dynapse_config_spikegen. These features require a new version of the logic which is not available at this stage. Please release also the FPGA logic (in a beta version) so that we can test these new functionalities.


OK.


Happened!!!! Thank you. Inserted a change in the file and it all worked!


### Fixes:
1. исправил цвет при выделениии 2 строк в меню.
2. Убрал автоподстановку в формах
3. Инвертировал сообщения об ошибках, добавил анимацию, изменил размеры.
4. Выровнял отступы
5. Немножко починил меню. Вроде теперь всегда адекватно?


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/5e04fc2b-048a-4fe3-9cab-6419f1ce9bda "mfe-dev-fe"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/d2e8d9ea-7a90-487a-a9cd-c822cc6d9891 "mfe-dev-fe") deployed [mfe-dev-be](https://github.com/ilantoren/mfe-dev-be/releases/tag/deploy-ibm-yp-us-south-MyFavoreats-myfavoreats-20170427-072443 "deploy-ibm-yp-us-south-MyFavoreats-myfavoreats-20170427-072443") to [myfavoreats](https://console.ng.bluemix.net/apps/4a80c652-9946-4627-8e17-db91b70a3998 "ibm:yp:us-south:MyFavoreats:myfavoreats"), including this commit


Good decision, great work guys.


what about ```unless query.name.trim()```, as a single space should not be accepted as a name.


Amazing!


sure... I'll fix it.
Thanks for the hint!


I'm not sure if something else in master might be broken, but I had problem today with decorated_collections. `decorated_collection` only had 1 item:

```
@departments.any?: true

Decorated collection
@decorated_collection=[#<DepartmentDecorator:0x007f828ff8fc00 @object=#<Department id: 3, name: "Accounting", parent_id: nil, head_employee_id: 44, employees_count: 9, created_at: "2017-04-14 18:53:32", updated_at: "2017-04-14 18:53:47">, @context={}>]>

Full
@departments.inspect: #<Draper::CollectionDecorator:0x007f828c2fa8a8 @object=#<ActiveRecord::Relation [#<Department id: 3, name: "Accounting", parent_id: nil, head_employee_id: 44, employees_count: 9, created_at: "2017-04-14 18:53:32", updated_at: "2017-04-14 18:53:47">, #<Department id: 1, name: "Banking", parent_id: nil, head_employee_id: 98, employees_count: 14, created_at: "2017-04-14 18:53:32", updated_at: "2017-04-14 18:53:47">, #<Department id: 2, name: "Farming", parent_id: nil, head_employee_id: 84, employees_count: 13, created_at: "2017-04-14 18:53:32", updated_at: "2017-04-14 18:53:47">, #<Department id: 7, name: "Legal", parent_id: nil, head_employee_id: 90, employees_count: 19, created_at: "2017-04-14 18:53:32", updated_at: "2017-04-14 18:53:47">, #<Department id: 8, name: "Mining", parent_id: nil, head_employee_id: 16, employees_count: 10, created_at: "2017-04-14 18:53:32", updated_at: "2017-04-14 18:53:47">, #<Department id: 4, name: "Real-Estate", parent_id: nil, head_employee_id: 78, employees_count: 8, created_at: "2017-04-14 18:53:32", updated_at: "2017-04-14 18:53:47">, #<Department id: 6, name: "Retail", parent_id: nil, head_employee_id: 40, employees_count: 15, created_at: "2017-04-14 18:53:32", updated_at: "2017-04-14 18:53:47">, #<Department id: 5, name: "Sales", parent_id: nil, head_employee_id: 57, employees_count: 12, created_at: "2017-04-14 18:53:32", updated_at: "2017-04-14 18:53:47">]>, @decorator_class=nil, @context={}, @decorated_collection=[#<DepartmentDecorator:0x007f828ff8fc00 @object=#<Department id: 3, name: "Accounting", parent_id: nil, head_employee_id: 44, employees_count: 9, created_at: "2017-04-14 18:53:32", updated_at: "2017-04-14 18:53:47">, @context={}>]>
```

view
```
  <% if @departments.any? %>
    <%= render partial: 'department', collection: @departments, cached: true %>
  <% end %>
```

controller
```
@departments = Department.all.decorate
```


>have I created a problem?

It depends on your views around recommended software development processes.
How much do you care for patch granularity?

>Or rewind it -

A revert could be an option for a questionable commit.

>and check them in one by one?

How do you think about to integrate the desired source code adjustments on topic branches and combine the accepted improvements by a corresponding merge commit then?


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/5a1658d0-cdd4-46dd-82af-939ab6e8978b "Demo_toolchainexam"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/d9f5c32e-eb2b-4a19-97f1-46e77a2487ca "Demo_toolchainexam") deployed [Demo_toolchainexam](https://github.com/sarangatripathy/Demo_toolchainexam/releases/tag/deploy-ibm-yp-us-south-sarang.tripathy-in.ibm.com-Tripathy_sarangWorkspace-20170427-072631 "deploy-ibm-yp-us-south-sarang.tripathy-in.ibm.com-Tripathy_sarangWorkspace-20170427-072631") to [Tripathy_sarangWorkspace](https://console.ng.bluemix.net/apps/7c966367-b3d4-4728-8b2c-d185f6b8b31b "ibm:yp:us-south:sarang.tripathy@in.ibm.com:Tripathy_sarangWorkspace"), including this commit


Agreed. Can be implemented properly as a feature later. OK


OK


82c019bで対応し､動作確認を行ないました｡


本来是[chatnoir](https://github.com/makaria/chatnoir)的commit.
切错窗口, 然后git revert HEAD又没确认, 就这样了.


bad idea


Congrats!


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/5a1658d0-cdd4-46dd-82af-939ab6e8978b "Demo_toolchainexam"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/d9f5c32e-eb2b-4a19-97f1-46e77a2487ca "Demo_toolchainexam") deployed [Demo_toolchainexam](https://github.com/sarangatripathy/Demo_toolchainexam/releases/tag/deploy-ibm-yp-us-south-sarang.tripathy-in.ibm.com-Tripathy_sarangWorkspace-20170427-072911 "deploy-ibm-yp-us-south-sarang.tripathy-in.ibm.com-Tripathy_sarangWorkspace-20170427-072911") to [Tripathy_sarangWorkspace](https://console.ng.bluemix.net/apps/550e8953-30d5-4d32-93e7-3e43a4e09c14 "ibm:yp:us-south:sarang.tripathy@in.ibm.com:Tripathy_sarangWorkspace"), including this commit


我还以为你要上线了


This is great! I think some of our `openssl` problems could also be socket problems, so good to get these passing.


Can't locate object method "disable_vnc_stalls" - https://openqa.suse.de/tests/902967#step/shutdown/18


thanks @ihadeed, actually I already pulled version 3.4.4 in my project to go forward... let me know when it will be definitively fixed.


WS's methods encapsulation is present - good.
But these methods should be public - in that case user can use your client


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/5a1658d0-cdd4-46dd-82af-939ab6e8978b "Demo_toolchainexam"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/d9f5c32e-eb2b-4a19-97f1-46e77a2487ca "Demo_toolchainexam") deployed [Demo_toolchainexam](https://github.com/sarangatripathy/Demo_toolchainexam/releases/tag/deploy-ibm-yp-us-south-sarang.tripathy-in.ibm.com-Tripathy_sarangWorkspace-20170427-073141 "deploy-ibm-yp-us-south-sarang.tripathy-in.ibm.com-Tripathy_sarangWorkspace-20170427-073141") to [Tripathy_sarangWorkspace](https://console.ng.bluemix.net/apps/a6cf4839-62a5-4a33-a5c9-9be4b3736c2b "ibm:yp:us-south:sarang.tripathy@in.ibm.com:Tripathy_sarangWorkspace"), including this commit


You should use `Locale.ROOT` or `Locale.ENGLISH` for the lowercase. Avoiding stull like Turkish dotless i.


Good solution!


birthday should be a simple date


Looks reasonable to me.


Why do you try to transform text in json?
I think it's not necessary


this patch works. no crash so far in a quick test


@sindresorhus I started to update doctrine-awesome repository again after talked with Tomas. What do you think about adding again doctrine-awesome to awesome list? This is new address : https://github.com/biberlabs/awesome-doctrine


It'd be clear if @Produces and @Consumes are on particular methods where they are needed


Sorry, it just doesn't make sense to have an empty class attribute and `js-timeline` on one object and `lb-timeline` on another. Please remove one.


As a return type you could use Response class


@parallel588 ok


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


Ups ;) Besides there's a TODO so I'm hoping to return to this code before this PR will be ready ;)


Should be fixed in 3.6.1, but I haven't updated the docs yet.


Do you need these imports?


Do you need this as well?


@dstogov can you please add a small note in UPGRADINGS.INTERNAL ?


Congrats too!


@fuzexuan yes, I agree.


You are right!

Believe it or not, the whole series was tested and reported as working. At least the not working diag led should have been noticed while testing 725238f698c94656dc216bdd6ae6e3275f266ea4.

Anyway, thanks a lot for spotting this. I pushed a commit to fix this stupid mistake.