لا أستطيع تسجيل دخول بسبب رمز وصل


Successfully aliased the URL <https://first-zeit-nknfntudg.now.sh> to the following aliases:

* https://first-zeit.danikristianto.now.sh
* https://first-zeit-git-master.danikristianto.now.sh


I just pushed a commit with some fixes and a friendly tank re-work (b3461ebaa2e690c9cd05c2a7c837d4a51117df2c).  As it was, the VM would abort if you shot a friendly tank (Why, I don't know - I don't *think* it crashed before).  Plus the final battle script was never being called...

Overall feedback: 👍
- I enjoyed the first parts of the map...  Really liked the train explosion and the sprinkler effect.  Also appreciated the blue key health room - we'll see how many people realize that you can use the shelves to get bandages.
- The zombie survival portion wasn't to my tastes, but it works.  It requires a very drastic change in gameplay style to survive - I'd almost prefer if there was an intended way to evade and escape to a safe zone (ladders/rooftops, maybe?), then strategically make your escape once the Russians arrive, so the player could have the option of playing different ways.  Yes, you might miss out on the ammo caches and soul pickups, but it would be more fun to play for those of us who prefer a more strategic and cautious play style...
- There should probably be some kind of reward for getting all of the big soul pickups - right now it's a challenge, but what does it get you?  Maybe stop the spawn waves?  Flash the screen and add some kind of effect to make the zombies afraid of you?  Both?


Successfully aliased the URL <https://scd-cdp-portal-es9kgwtl4.now.sh> to the following aliases:

* https://scd-cdp-portal.mkr-js-prod.now.sh
* https://scd-cdp-portal-git-develop.mkr-js-prod.now.sh


Deployment failed with the following error:

~~~
Your `package.json` file is missing a `build` property inside the `script` property.
~~~


Successfully aliased the URL <https://first-zeit-6je7i2mj4.now.sh> to the following aliases:

* https://first-zeit.danikristianto.now.sh
* https://first-zeit-git-master.danikristianto.now.sh


Thanks!!


@JuliaRegistrator `register()`


> Can we expect some way to use this app on android? Either in browser or on google play

I have used it on my Google Pixel XL 2 using the chrome browser.


Registration pull request created: [JuliaRegistries/General/2568](https://github.com/JuliaRegistries/General/pull/2568)

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if [Julia TagBot](https://github.com/apps/julia-tagbot) is installed, or can be done manually through the github interface, or via:
```
git tag -a v0.1.1 -m "<description of version>" 812f21224d683f4119b02c456dda47d4d0a4a471
git push origin v0.1.1
```


@JuliaRegistrator register

Release notes:

- Upgraded to GLFW v3.3.
- Dropped support for Julia v0.7.
- Switched package metadata from `REQUIRE` to `Project.toml`.
- Switched package build process from `BinaryDeps` to `BinaryProvider`.
  - Windows and MacOS builds are downloaded from https://github.com/JuliaGL/GLFWBuilder.
  - Linux builds continue to be from source.
  - FreeBSD builds from source are fixed (thanks @iblis17).


Registration pull request created: [JuliaRegistries/General/2569](https://github.com/JuliaRegistries/General/pull/2569)

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if [Julia TagBot](https://github.com/apps/julia-tagbot) is installed, or can be done manually through the github interface, or via:
```
git tag -a v3.0.0 -m "<description of version>" e3330c49a0f1f0700cfb1a3bb641b03651b61782
git push origin v3.0.0
```


Successfully aliased the URL <https://scd-cdp-portal-16cjdyx4b.now.sh> to the following aliases:

* https://scd-cdp-portal.mkr-js-prod.now.sh
* https://scd-cdp-portal-git-develop.mkr-js-prod.now.sh


**public function withSubPage( $title = null )**

change to this code to make it work with PHP5


[Guo Xiang Tan posted](https://review.discourse.org/t/dev-add-comment-about-fork-of-image-optim/5110/2):

This needs to be followed up since the original author of the gem wasn't active in reviewing my PR.


Successfully aliased the URL <https://reactforxiangyun-pj9jlfm5s.now.sh> to the following aliases:

* https://reactforxiangyun.1098693467.now.sh
* https://reactforxiangyun-git-master.1098693467.now.sh


@tavsica-shitaljit
link to the problem is http://codejam.tavisca.com/Arena.aspx


Thanks for this :) fixed my code too :)


Course of Angular (Master Detail) with objective to reduce repeat code in project. Master-detail architecture is the most incredible resource to developers reduce strongly the time of coding.


cache-psy (energy-plus) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-UnitTestsCoverage-Debug: OK (1126 of 1126 tests passed, 0 test warnings)

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


Successfully aliased the URL <https://staticman-r7bouls19.now.sh> to the following aliases:

* https://staticman.kimdhoebot.now.sh
* https://staticman-git-master.kimdhoebot.now.sh


thanks for the update @aaronqiuchiu


wwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwww


PR_opened/Fix_7378_StorageTankTempLimit (jmarrec) - Win64-Windows-10-VisualStudio-16: OK (2442 of 2449 tests passed, 4 test warnings)

Messages:\n
 * 8 tests had: EIO diffs.
 * 1 test had: ESO small diffs.
 * 2 tests had: BND diffs.
 * 3 tests had: AUD diffs.
 * 7 tests had: ESO big diffs.
 * 5 tests had: MTR big diffs.
 * 3 tests had: RDD diffs.
 * 7 tests had: Table big diffs.
 * 3 tests had: ERR diffs.
 * 1 test had: MTD diffs.
 * 2 tests had: MTR small diffs.

Failures:\n

regression Test Summary
 * Passed: 655
 * Failed: 7

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


Successfully aliased the URL <https://currency-api-coxc1nosx.now.sh> to the following aliases:

* https://currency-api.geshanm.now.sh
* https://currency-api-git-master.geshanm.now.sh


Successfully aliased the URL <https://scd-cdp-portal-moi2ac12u.now.sh> to the following aliases:

* https://scd-cdp-portal.mkr-js-prod.now.sh
* https://scd-cdp-portal-git-develop.mkr-js-prod.now.sh


You still need to add a marker on top of the month name

![image](https://user-images.githubusercontent.com/48784121/62676810-5e5a4b00-b9ac-11e9-882b-ab3d17c2a7a3.png)


Deployment failed with the following error:

~~~
Your `package.json` file is missing a `build` property inside the `script` property.
~~~


You should set a const for 120 i.e. `monthNameSpacer = 120`


wip


PR_opened/Fix_7151_GeneratorPVAvailSched (jmarrec) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-IntegrationCoverage-Debug: OK (667 of 667 tests passed, 0 test warnings)

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


Can you test out the issues mentioned in #186 and comment the results there?


Copy of this build can be found at
https://builds.myetherwallet.com/build/dfd133caf8e7e67b68553c0b03080aa0f44a0135/index.html
                       https://www.cloudflare-ipfs.com/ipfs/QmSYmNkiBQSbUfqytzZhxjxCSCFcmt4UpBQ3vv4Abq8njn
                       Virus Total analysis
                       https://www.virustotal.com/file/1bdda6d4d11af9f23efd4bb5066aaf461b49d619f39465b2a59a94cc9c696fe7/analysis/1565241573/


The following doc(s) have been deployed to the [allenfearp](https://allenfearp-static-docs.pantheonsite.io/docs) Multidev environment:
- [source/content/solr-drupal-8.md](https://github.com/pantheon-systems/documentation/commit/1b3b348e40889995b3565a3cac043b870051c28b/source/content/solr-drupal-8.md)


Both methods do not return any object but you can verify if nested service is executed. Please use the `verify` method as shown in module 7.


900 is max.


Thanks for the extra work.

Has this Transaction class been tested against both APIs?

This was the main thing I wanted fixed before merge. (Namely to make sure that we choose __slots__ that are common to both API responses...

Once that's fixed, I'm happy.

But reading on my phone - looks good. And re: the Base Class API idea etc. My take is that it would be a fine idea if we had e.g. 4 or 5 APIs... but right now I think it'd be premature. I think this is a case where I would trade more code for something easier on the brain because when you start doing inheritance, the relevant code backing it up is in a different file/place... I don't like it personally in general.


PR_opened/Fix_7315_BuildDocs (jmarrec) - x86_64-Linux-Ubuntu-18.04-cppcheck: OK (0 of 0 tests passed, 0 test warnings)

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


Now could not deploy this pull request since the `now.json` file does not contain valid JSON.

	Click here to see the contents of `now.json`

{
	"version": 2,
	"builds": [
		{
			"src": "package.json",
			"use": "@now/next"
		}
	],
	"routes": [
		{
			"src": "studentapp.html",
			"dest": "https://forms.gle/GX3DK4Dg3zFaCxVo9" // new google form
		},
		{
			"src": "/about-us.html",
			"dest": "/about"
		},
		{
			"src": "/hostapp.html",
			"dest": "https://forms.gle/KMv9PU3kBdbazfFX9" // new google form
		},
		{
			"src": "/host-a-student.html",
			"dest": "/hosts"
		},
		{
			"src": "/chairperson-letter.html",
			"dest": "/letter"
		}
	],
	"alias": ["ifriendstucson.org", "www.ifriendstucson.org"]
}

For more information on now.json visit https://zeit.co/docs/features/configuration#now.json.


+Devaraj : singleton ,CRUD operation and using collections


PR_opened/Fix_7315_BuildDocs (jmarrec) - x86_64-Linux-Ubuntu-18.04-custom_check: OK (9 of 9 tests passed, 0 test warnings)

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


Shouldn't this part better be in "default" of the previous select statement. If somewhen stringTypeId extends objectTypeId then it would else get handled from both code portions ... Is that desired?


I think it's time to remove this from ALARM repositories. The AUR package already supports armv7 and aarch64 and uses the .deb instead of packages for home NAS server. https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=plex-media-server
armv5 package should probably be removed as well as it is really outdated and not supported by current plex clients with the exception of PlexWeb which allows direct access to it, but not via plex.tv
@tokenize47 @kmihelich


I added the line of code of second branch.


Successfully aliased the URL <https://hydrus-web-98b32p5lw.now.sh> to the following aliases:

* https://hydrus.app
* https://hydrus-web.floogulinc.now.sh
* https://hydrus-web-git-master.floogulinc.now.sh


There is missing comma that separates SignedHeaders from Signature. This causes MissingFields API error.


welcomefile不能这么写 narbar只是一个导航条 不是欢迎界面


##二级标题
###三级标题


Successfully aliased the URL <https://ifriends-next-pgvma49iu.now.sh> to the following aliases:

* https://ifriendstucson.org
* https://www.ifriendstucson.org
* https://ifriends-next.youhaowei.now.sh
* https://ifriends-next-git-master.youhaowei.now.sh


@nainar friendly ping


Have you looked into this? It's been like 8 months

On Thu, Aug 8, 2019, 9:41 AM Piyusha Pawar <notifications@github.com> wrote:

> How can I contact you??
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/boksheos/Ravindrababu-GATE-Lectures-Downloader/commit/de57d6ccf777fce86f9d96af104f8acb61e3a0b8?email_source=notifications&email_token=AGBXQHMWCCESSGBV3S3F6QLQDOMGDA5CNFSM4GHU6OP2YY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBBALIE#commitcomment-34614532>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AGBXQHO2FC652EH4EKT3C53QDOMGDANCNFSM4GHU6OPQ>
> .
>


:hourglass_flowing_sand: Waiting for custom rule data to be resolved
:point_right: click here to view a full list of the events :point_left:


looks good


sorry about that I thought I already undid that...


Successfully aliased the URL <https://gatsby-theme-documentation-c8etci5v1.now.sh> to the following aliases:

* https://docs-theme.johno.com
* https://gatsby-theme-documentation.johno1.now.sh
* https://gatsby-theme-documentation-git-master.johno1.now.sh


IBM Cloud [toolchain](https://cloud.ibm.com/devops/toolchains/ec39efc7-cd25-45db-97eb-94fa2b7ecf6e?env_id=ibm%3Ayp%3Aus-south "lightbluecompute-devops-20190807040640277"): [Delivery Pipeline](https://cloud.ibm.com/devops/pipelines/7b92560c-38d9-4dfb-8f70-f7dafbad8f9d "lightblue-web") deployed [lightblue-web-20190807040640277](https://github.com/alexcarroll1/lightblue-web-20190807040640277/releases/tag/deploy-ibm-yp-us-south-alex.carroll1-ibm.com-dev-20190808-053638 "deploy-ibm-yp-us-south-alex.carroll1-ibm.com-dev-20190808-053638") to [dev](https://console.bluemix.net/apps/f7271f42-d62c-47de-b430-cf6ced1e10ad?env_id=ibm:yp:us-south "ibm:yp:us-south:alex.carroll1@ibm.com:dev"), including this commit


Deployment failed with the following error:

~~~
Missing `start` (or `now-start`) script in `package.json`. See: https://docs.npmjs.com/cli/start
~~~


:white_check_mark: All Rules (3 / 3) Passed

      :crown: Good job! this pull request is aligned with your organization's best practices!

      :point_right: You can review your rules settings at smart policy management :point_left:

:point_right: click here to view a full list of the events :point_left:


add


Check this: https://github.com/GoogleChrome/rendertron/pull/258#pullrequestreview-191228544


Successfully aliased the URL <https://staticman-bot-6pgbisctu.now.sh> to the following aliases:

* https://staticman-bot.kimdhoebot.now.sh
* https://staticman-bot-git-master.kimdhoebot.now.sh


input now replaces the original variables first_num and second_num. Those variables are only assigned after number validation using the last verified value.


@nla-odoo @dbo-odoo I suggest you make the cross icon in the top right corner of the popup more visible/darker. It is very light grey on white background and almost invisible (moreover neither the ESC key nor clicking outside allow to escape the popup).


We don't have to worry about chains if we follow only once anyway.


where did you get the data set


PR_opened/Fix_7315_BuildDocs (jmarrec) - x86_64-Linux-Ubuntu-18.04-gcc-7.4: OK (2480 of 2487 tests passed, 2 test warnings)

Messages:\n
 * 8 tests had: EIO diffs.
 * 1 test had: ESO small diffs.
 * 2 tests had: BND diffs.
 * 3 tests had: AUD diffs.
 * 7 tests had: ESO big diffs.
 * 5 tests had: MTR big diffs.
 * 3 tests had: RDD diffs.
 * 7 tests had: Table big diffs.
 * 1 test had: ERR diffs.
 * 1 test had: MTD diffs.
 * 2 tests had: MTR small diffs.

Failures:\n

regression Test Summary
 * Passed: 675
 * Failed: 7

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


**Copy from:**
_https://blog.scottlogic.com/2018/10/08/infrastructure-as-code-getting-started-with-terraform.html_

### **Infrastructure as Code - Getting Started with Terraform**

This blog post serves as a brief introduction to what Infrastructure as Code is, as well as how to get started using it with Terraform. Although Terraform can be used with many cloud providers, the post focuses particularly on deploying resources to AWS.

**The problem**
So, you need some kind of cloud deployed software and you’ve already decided on some Infrastructure as a Service provider (IaaS - one of the many something as something acronyms that’s all the rage) such as AWS or Azure. If you require a large set of infrastructure, for a complex distributed application for instance, all of a sudden you find yourself spending a lot of your free time and weekends in the AWS console.

Live configuration of services and the bringing up and down of resources becomes a frequent endeavour, especially during the developmental/experimental stages. On top of the gradual attrition of your will to live, this manual and repetitive procedure also opens you up to human error. Provisioning resources in a slightly different sequence can cause parts of the application to behave unexpectedly. Moreover, with all those services, it’s much more likely you’ll forget to destroy one of them; hiding out of sight while the AWS bill creeps up insidiously.

We recently found ourselves in a very similar situation, building a cloud hosted tool for comparing various data engineering technologies. Everything was deployed to AWS, primarily using the EC2 Container Service for managing all the dockerised services that made up our distributed application. As the tool rapidly grew in functionality, so too did the required infrastructure; we suddenly had to account for various network resources (subnets, internet/api gateways, route53 hosted zones etc.), load balancers, EC2 clusters, container repositories and more.

We spent many hours staring at the AWS console, wondering why everything was broken, despite being certain we followed the same deployment steps as the time it worked. Instead of trying to rigidly document the exact provisioning process, we decided there must be a better way…

**The Solution**
…well, specifically, infrastructure as code

**What is infrastructure as code?**
Infrastructure as Code, in simple terms, is a means by which we can write declarative definitions for the infrastructure we want to exist and using them with a provisioning tool that deals with the actual deployment. This means that we can code what we want built, provide necessary credentials for the given IaaS provider, kick off the provisioning process, pop the kettle on and come back to find all your services purring along nicely in the cloud… or a terminal screen full of ominous warnings about failed deployment and “unrecoverable state” and a deep sense of growing unease (but not often, don’t worry 👍).

**Advantages**
Using Infrastructure as Code as part of your deployment process has a number of immediate benefits to your workflow:

**Speed** - This one speaks for itself really, automation beats manually navigating through an interface to deploy and connect up resources, hands down.

**Reliability** - With a large set of infrastructure, it becomes so easy to misconfigure a resource or provision the services in the wrong order. With IaC the resources will be configured exactly as declared, and implicit/explicit dependencies can be used to ensure the creation order.

**Experimentation** - With the ease at which the infrastructure can be deployed, experimental changes can be readily investigated with scaled down resources to minimise the cost. Once approved, everything can be scaled up for production deployments.

**Best Practices** - As developers, we’re always looking to employ the known best practices of software engineering wherever we can. Writing code to design and deploy infrastructure facilitates this in the arena of cloud provisioning, using established techniques like writing modular, configurable code committed to version control. This leads us to view our infrastructure as somewhat of a software application in itself, and shifts us in the direction of a DevOps culture.

The enabling idea of infrastructure as code is that the systems and devices which are used to run software can be treated as if they, themselves, are software - Kief Morris

**Sounds like dark magic, how does it actually work?**
There are two overarching methods to implement Infrastructure as Code - ‘Push’ and ‘Pull’: The Push approach is based around a controlling server, ie the user’s machine, pushing the all the provisioning information to the actual destination server/s to be configured. (CFEngine, Chef, Puppet) Conversely, the Pull method involves the IaaS requesting it’s configuration from another server, either at a set interval or after receiving a cue. (Terraform, Otter, Ansible Tower).

Although there are number of cloud provisioning IaC tools, each with its own implementation, for the purpose of this blog post I will focus exclusively on using Terraform for deploying to AWS. Also, for the sake of simplicity, I won’t get into all the details and best practices of working with Terraform in an agile team environment, but will attempt to cover that in a subsequent post.

Terraform uses a Push approach, and therefore initiates the provisioning process by interacting directly with AWS to communicate the desired infrastructure. It does this by using the supplied AWS credentials with the Terraform AWS Provider Plugin, which under the hood utilises the AWS Go SDK.

From its knowledge of the live infrastructure, Terraform generates a ‘terraform.tfstate’ file, with which it can effectively employ a ‘diffing’ technique on the declared desired infrastructure and that which is actually deployed. Once any required live changes have been calculated, a plan (.tfplan) file is generated. If approved, Terraform can get to work in effecting these changes in AWS. It’s important to note that in the majority of cases, Terraform treats these resources as immutable, that is, rather than trying make configuration changes to already deployed infrastructure, it opts to destroy the resource and create a new one. This directly relates to the ‘speed’ and ‘experimentation’ advantages - rather than wasting time fiddling with deployed resources, developers can just destroy them and create them anew. After all, in today’s world, server time is cheap and developer time is expensive

**Let’s see Terraform in action / Getting started using Terraform**
Terraform itself is a CLI tool, and can be downloaded from ‘the official release page’. It is developed by Hashicorp so, naturally, relies on the HashiCorp Configuration Language (HCL) for creating declarations. HCL strives to be both human and machine friendly, being fully JSON compatible while also supporting comments and variable interpolation etc. Terraform files themselves are referred to as ‘configuration files’ and have the file extensions .tf and .tf.json.

In order to start using Terraform, initialise a terraform directory by calling terraform init in any directory containing at least one configuration file. A typical Terraform module will have the following structure:

**my-terraform-files
│
└───my-terraform-module
│   │   main.tf
│   │   variables.tf
|   |   outputs.tf
│
└───my-other-terraform-module
│   │   main.tf
│   │   variables.tf
|   |   outputs.tf**

Note that the file names themselves are not important, and terraform commands will load all configuration files in the directory. For simplicity’s sake, I won’t cover the creation of reusable modules in this post, and will keep all the declarations in one simple directory with the minimal amount of files.

**Provider**
Before Terraform will be able to do anything useful, you must specify which IaaS provider you’re using. This will be the cue to download the plugins necessary to read from and write to the hosting service. Of course, before it can access anything on AWS, it needs the relevant permissions, so here comes the scary part… supplying your AWS credentials 😧. Before doing so, create a user in your AWS IAM account for Terraform itself (just giving it the permissions you’re happy with). There’s a few ways of supplying the provider with your AWS credentials, but a pretty standard way is as follows:

**main.tf**

provider "aws" {
 region = "eu-west-1"
 version = "~> 1.19"
 access_key = "${var.aws_access_key}"
 secret_key = "${var.aws_secret_key}"
}

Here, we declare that our provider (AWS), the AWS region (Ireland 💚) , the plugin version and the credentials. Notice here how the credentials are declared using variable interpolation syntax. This leads us on nicely to an essential aspect of HCL: variables. Remember that all configuration files (.tf) in the directory are loaded when run running commands, allowing us to declare variables wherever we want. So, along with a ‘variables.tf’ file, we could also have:

**variables.secret.tf**

variable "aws_access_key" {
 description = "The AWS access key."
 default     = "XYXYXACCESSKEYXYXYX"
}

variable "aws_secret_key" {
 description = "The AWS secret key."
 default     = "XYXYSUPERSECRETKEYXYXYX"
}

Then, we can simply ignore ‘.secret.tf’ files in our version control 👊. (Alternative means of supplying credentials are from environment variables or storing them in ~/.aws/config, as explained in more detail here. In an another ‘main’ variables file ( variables.tf), we declare values essential to our resource provisioning such as instance sizings, autoscale desired capacities and the various human-friendly names of all the resources. A typical file may look like:

**variables.tf**

**variable "instance_type" {
 description = "Type of EC2 instance to use"
 default = "t2.small"
}

variable "instance_types" {
 type    = "map"
 default = {
   "dev" = "t2.small"
   "prod" = "t3.large"
 }
}

variable "autoscale_min" {
 description= "The minimum number of EC2 instances"
 default = 2
}

variable "autoscale_max" {
 description= "The maximum number of EC2 instances"
 default = 5
}

variable "autoscale_desired" {
 description = "Desired autoscale (number of EC2)"
 default = 3
}

variable "alb_name" {
 description = "Human-friendly application load balancer name"
 default = "my-alb"
}

Here, we’re simply declaring some values to be reused when declaring the infrastructure we need. The descriptions are purely optional, and for the developer’s benefit only. The possible variable types are string (default type), list and map. Variables can also be declared but left blank, setting their values through environment variables or .tfvars files, explained here. The former can be accomplished by prepending the variable name with TF_VAR_, for example:

variable "environment" {
 description = "Generic environment"
}
$ TF_VAR_environment=foo terraform apply
Ok cool, but we haven’t really done anything yet. Time to actually do, infrastructure, stuff.

Resources
The most essential components of configuration files are ‘resources’. This is where you declare the type of resource and all of the resource specific settings. Let’s take a look at a simple set of resources:

resource "aws_instance" "myapp_ec2_instance" {
 ami               = "ami-21f78e11"
 availability_zone = "${var.availability_zone}"
 instance_type     = "${var.instance_type}"

 tags {
   Name = "myapp-EC2-instance"
 }
}

resource "aws_ebs_volume" "myapp_ebs_volume" {
 availability_zone = "${var.availability_zone}"
 size              = 1

  tags {
   Name = "myapp-EBS-volume"
 }
}

resource "aws_volume_attachment" "myapp_vol_attachment" {
 device_name = "/dev/sdh"
 volume_id   = "${aws_ebs_volume.myapp_ebs_volume.id}"
 instance_id = "${aws_instance.myapp_ec2_instance.id}"
}
Here, we’ve declared a few pieces of infrastructure that we want Terraform to provision in AWS. After the ‘resource’ keyword, we specify the type and a local identifier as strings before providing necessary information in the code block.

First, we declare a simple EC2 instance (‘aws_instance’) and give it the local identifier of "myapp_ec2_instance" so that we can reference it elsewhere and Terraform can keep track of it in the .tfstate file. Then we pass in some settings to configure how it is provisioned (the instance size etc.), simple :). Next up, we want an Elastic Block Storage volume, so we go ahead and declare that too in the same manner.

Finally, we want to actually attach this block volume to the EC2 instance. This attachment is itself considered a ‘resource’, so we can declare it as the others, passing in the relevant IDs for the instance and the volume. This is where implicit dependencies come into the scene: we can reference the other two Terraform resources, which means Terraform to wait until these resources exist and then use their ‘id’ attributes. This gives us reliable provisioning order :)

We can also give provide explicit dependencies to resources where necessary, instructing Terraform to wait until the dependent resources exist by specifying a ‘depends_on’ field.

Also,we gave everything we could a tag. This is for us to quickly find the resource should we need to in the AWS console, maybe to track costs or manually delete it if something does go wrong.

**Data Sources**
The other key construct in Terraform is the ‘data source’. This enables us to reference resources that should already exist in AWS, allowing us to extract information from them to feed into new resources etc. For example:

data "aws_route53_zone" "myapp_private_hosted_zone" {
 vpc_id       = "${var.myapp_vpc.id}"
 name         = "${var.private_hosted_zone_name}"
 private_zone = true
}

resource "aws_eip" "myapp_eip" {
 instance = "${aws_instance.myapp_ec2_instance.id}"
 vpc      = true
}

resource "aws_route53_record" "myapp_hosted_zone_entry" {
 zone_id = "${data.aws_route53_zone.myapp_private_hosted_zone.id}"
 name    = "subdomain.myapp"
 type    = "A"
 ttl     = "300"
 records = ["${aws_eip.myapp_eip.public_ip}"]
}

Here, we want to create a new route53 DNS record in our hosted zone (e.g. subdomain.myapp.com) so that it points to an elastic ip address we created. In this case, we create the elastic ip and the route53 record, but our hosted zone already exists. Therefore, in order to reference our hosted zone, we use a data source.

We declare them much the same as with resources, only the information we supply in the block is used by Terraform to discover such resources, not create them. Then, we can reference the data sources in the same way, extracting information to pass into new resources.

Once you’ve declared all your resources and data sources, defined your necessary variables and provided your credentials, you’re all set to let Terraform do its magic! To check if everything will work and there’s no errors, run terraform plan from within the directory. If all is well and you’re happy with what it plans to build, kick off the process with terraform apply, one final approval, then wait for your infrastructure to be deployed :)

If you make changes to your code, running the plan and apply commands again will let Terraform use its knowledge of the deployed resources (.tfstate) to calculate what changes need to be made, whether building or destroying. Finally, when you want to bring down your infrastructure, simply issue a terraform destroy command and down it comes.

That’s all for an introduction, thanks for reading! Later posts may cover best practices for running Terraform in a team, as well as how to remotely run Terraform in automation.

_https://blog.scottlogic.com/2018/10/08/infrastructure-as-code-getting-started-with-terraform.html_


@fhe-odoo we don't have control over the look of the popup, it's an iframe from authorize.net that we cannot modify unfortunately. we can't change the close icon nor the behaviour of the popup w. regards to keyboard input...


Unhandled Failure


Hello @fhe-odoo
Thanks for the suggestion, but we can not manage this, as this popup is generated by Authorize.net.
We are just using their library and showing this popup
Thanks


Oh, now that I think about it, may be you don't have enough permissions to see the registrations? :thinking:
It could be possible that my access keys are more powerful than yours...


move code script to dom.js


> The username can't be changed by the users themselves now

Hm? I still see the username setting.


Successfully aliased the URL <https://dailyrandomphotogithubio-lrbwefnze.now.sh> to the following aliases:

* https://dailyrandomphoto.now.sh
* https://photooftheday.now.sh
* https://randomphoto.now.sh
* https://dailyphoto.now.sh
* https://picoftheday.now.sh
* https://todayphoto.now.sh
* https://dailyrandomphotogithubio.dailyrandomphoto.now.sh
* https://dailyrandomphotogithubio-git-master.dailyrandomphoto.now.sh


:white_check_mark: All Rules (5 / 5) Passed

      :crown: Good job! this pull request is aligned with your organization's best practices!

      :point_right: You can review your rules settings at smart policy management :point_left:

:point_right: click here to view a full list of the events :point_left:


> Thanks for this! Just wanted to create a PR until I noticed you already fixed this. Can you create a respective release on crates.io?

I'm sorry, I think the push to crates should have the original author to do, Because I will not necessarily maintain this project for a long time.
And other i created the same project

- https://github.com/fewensa/telegrambot
- https://github.com/fewensa/telegram-client

My focus will be on my project.

If I find a problem, I might submit it to other authors.

If the original author didn't post to crates.io, I think it's a good idea to use git source in cargo.toml.


Successfully aliased the URL <https://currency-api-jvkz49mle.now.sh> to the following aliases:

* https://currency-api.geshanm.now.sh
* https://currency-api-git-master.geshanm.now.sh


We will have to revert this, I'm afraid.  Because every time we pull the `mdsplib` library, this will revert...  :-(

Unless you modify the `scripts/import_mdsplib` to automatically modify all these instances.


**Copied from**
_https://learn.hashicorp.com/terraform/getting-started/build_

### **Build Infrastructure**

With Terraform installed, let's dive right into it and start creating some infrastructure.

We'll build infrastructure on AWS for the getting started guide since it is popular and generally understood, but Terraform can manage many providers, including multiple providers in a single configuration. Some examples of this are in the use cases section.

If you don't have an AWS account, create one now. For the getting started guide, we'll only be using resources which qualify under the AWS free-tier, meaning it will be free. If you already have an AWS account, you may be charged some amount of money, but it shouldn't be more than a few dollars at most.

Warning! If you're not using an account that qualifies under the AWS free-tier, you may be charged to run these examples. The most you should be charged should only be a few dollars, but we're not responsible for any charges that may incur.

**»Configuration**
The set of files used to describe infrastructure in Terraform is simply known as a Terraform configuration. We're going to write our first configuration now to launch a single AWS EC2 instance.

The format of the configuration files is documented here. Configuration files can also be JSON, but we recommend only using JSON when the configuration is generated by a machine.

The entire configuration is shown below. We'll go over each part after. Save the contents to a file named example.tf. Verify that there are no other *.tf files in your directory, since Terraform loads all of them.

provider "aws" {
  profile    = "default"
  region     = "us-east-1"
}

resource "aws_instance" "example" {
  ami           = "ami-2757f631"
  instance_type = "t2.micro"
}

Note: The above configuration is designed to work on most EC2 accounts, with access to a default VPC. For EC2 Classic users, please use t1.micro for instance_type, and ami-408c7f28 for the ami. If you use a region other than us-east-1 then you will need to choose an AMI in that region as AMI IDs are region specific.

The profile attribute here refers to the AWS Config File in ~/.aws/credentials on MacOS and Linux or %UserProfile%\.aws\credentials on a Windows system. It is HashiCorp recommended practice that credentials never be hardcoded into *.tf configuration files. We are explicitly defining the default AWS config profile here to illustrate how Terraform accesses sensitive credentials.

To verify an AWS profile and ensure Terraform has correct provider credentials, install the AWS CLI and run aws configure. The AWS CLI will then verify and save your AWS Access Key ID and Secret Access Key. Those credentials are found on this page.

Note: If you simply leave out AWS credentials, Terraform will automatically search for saved API credentials (for example, in ~/.aws/credentials) or IAM instance profile credentials. This option is much cleaner for situations where tf files are checked into source control or where there is more than one admin user. See details here. Leaving IAM credentials out of the Terraform configs allows you to leave those credentials out of source control, and also use different IAM credentials for each user without having to modify the configuration files.

This is a complete configuration that Terraform is ready to apply. The general structure should be intuitive and straightforward.

The provider block is used to configure the named provider, in our case "aws". A provider is responsible for creating and managing resources. Multiple provider blocks can exist if a Terraform configuration is composed of multiple providers, which is a common situation.

The resource block defines a resource that exists within the infrastructure. A resource might be a physical component such as an EC2 instance, or it can be a logical resource such as a Heroku application.

The resource block has two strings before opening the block: the resource type and the resource name. In our example, the resource type is "aws_instance" and the name is "example." The prefix of the type maps to the provider. In our case "aws_instance" automatically tells Terraform that it is managed by the "aws" provider.

Within the resource block itself is configuration for that resource. This is dependent on each resource provider and is fully documented within our providers reference. For our EC2 instance, we specify an AMI for Ubuntu, and request a "t2.micro" instance so we qualify under the free tier.

**»Initialization**
The first command to run for a new configuration -- or after checking out an existing configuration from version control -- is terraform init, which initializes various local settings and data that will be used by subsequent commands.

Terraform uses a plugin based architecture to support the numerous infrastructure and service providers available. As of Terraform version 0.10.0, each "Provider" is its own encapsulated binary distributed separately from Terraform itself. The terraform init command will automatically download and install any Provider binary for the providers in use within the configuration, which in this case is just the aws provider:

$ terraform init
Initializing the backend...

Initializing provider plugins...
- Checking for available provider plugins...
- Downloading plugin for provider "aws" (terraform-providers/aws) 2.10.0...

The following providers do not have any version constraints in configuration,
so the latest version was installed.

To prevent automatic upgrades to new major versions that may contain breaking
changes, it is recommended to add version = "..." constraints to the
corresponding provider blocks in configuration, with the constraint strings
suggested below.

* provider.aws: version = "~> 2.10"

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
The aws provider plugin is downloaded and installed in a subdirectory of the current working directory, along with various other book-keeping files.

The output specifies which version of the plugin was installed, and suggests specifying that version in configuration to ensure that running terraform init in future will install a compatible version. This step is not necessary for following the getting started guide, since this configuration will be discarded at the end.

**»Apply Changes**
Note: The commands shown in this guide apply to Terraform 0.11 and above. Earlier versions require using the terraform plan command to see the execution plan before applying it. Use terraform version to confirm your running version.

In the same directory as the example.tf file you created, run terraform apply. You should see output similar to below, though we've truncated some of the output to save space:

$ terraform apply
# ...

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # aws_instance.example will be created
  + resource "aws_instance" "example" {
      + ami                          = "ami-2757f631"
      + arn                          = (known after apply)
      + associate_public_ip_address  = (known after apply)
      + availability_zone            = (known after apply)
      + cpu_core_count               = (known after apply)
      + cpu_threads_per_core         = (known after apply)
      + get_password_data            = false
      + host_id                      = (known after apply)
      + id                           = (known after apply)
      + instance_state               = (known after apply)
      + instance_type                = "t2.micro"
      + ipv6_address_count           = (known after apply)
      + ipv6_addresses               = (known after apply)
      + key_name                     = (known after apply)
      + network_interface_id         = (known after apply)
      + password_data                = (known after apply)
      + placement_group              = (known after apply)
      + primary_network_interface_id = (known after apply)
      + private_dns                  = (known after apply)
      + private_ip                   = (known after apply)
      + public_dns                   = (known after apply)
      + public_ip                    = (known after apply)
      + security_groups              = (known after apply)
      + source_dest_check            = true
      + subnet_id                    = (known after apply)
      + tenancy                      = (known after apply)
      + volume_tags                  = (known after apply)
      + vpc_security_group_ids       = (known after apply)

      + ebs_block_device {
          + delete_on_termination = (known after apply)
          + device_name           = (known after apply)
          + encrypted             = (known after apply)
          + iops                  = (known after apply)
          + snapshot_id           = (known after apply)
          + volume_id             = (known after apply)
          + volume_size           = (known after apply)
          + volume_type           = (known after apply)
        }

      + ephemeral_block_device {
          + device_name  = (known after apply)
          + no_device    = (known after apply)
          + virtual_name = (known after apply)
        }

      + network_interface {
          + delete_on_termination = (known after apply)
          + device_index          = (known after apply)
          + network_interface_id  = (known after apply)
        }

      + root_block_device {
          + delete_on_termination = (known after apply)
          + iops                  = (known after apply)
          + volume_id             = (known after apply)
          + volume_size           = (known after apply)
          + volume_type           = (known after apply)
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.

This output shows the execution plan, describing which actions Terraform will take in order to change real infrastructure to match the configuration. The output format is similar to the diff format generated by tools such as Git. The output has a + next to aws_instance.example, meaning that Terraform will create this resource. Beneath that, it shows the attributes that will be set. When the value displayed is (known after apply), it means that the value won't be known until the resource is created.

If terraform apply failed with an error, read the error message and fix the error that occurred. At this stage, it is likely to be a syntax error in the configuration.

If the plan was created successfully, Terraform will now pause and wait for approval before proceeding. If anything in the plan seems incorrect or dangerous, it is safe to abort here with no changes made to your infrastructure. In this case the plan looks acceptable, so type yes at the confirmation prompt to proceed.

Executing the plan will take a few minutes since Terraform waits for the EC2 instance to become available:

# ...
aws_instance.example: Creating...
aws_instance.example: Still creating... [10s elapsed]
aws_instance.example: Creation complete after 1m50s [id=i-0bbf06244e44211d1]

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

After this, Terraform is all done! You can go to the EC2 console to see the created EC2 instance. (Make sure you're looking at the same region that was configured in the provider configuration!)

Terraform also wrote some data into the terraform.tfstate file. This state file is extremely important; it keeps track of the IDs of created resources so that Terraform knows what it is managing. This file must be saved and distributed to anyone who might run Terraform. It is generally recommended to setup remote state when working with Terraform, to share the state automatically, but this is not necessary for simple situations like this Getting Started guide.

You can inspect the current state using terraform show:

$ terraform show
# aws_instance.example:
resource "aws_instance" "example" {
    ami                          = "ami-2757f631"
    arn                          = "arn:aws:ec2:us-east-1:130490850807:instance/i-0bbf06244e44211d1"
    associate_public_ip_address  = true
    availability_zone            = "us-east-1c"
    cpu_core_count               = 1
    cpu_threads_per_core         = 1
    disable_api_termination      = false
    ebs_optimized                = false
    get_password_data            = false
    id                           = "i-0bbf06244e44211d1"
    instance_state               = "running"
    instance_type                = "t2.micro"
    ipv6_address_count           = 0
    ipv6_addresses               = []
    monitoring                   = false
    primary_network_interface_id = "eni-0f1ce5bdae258b015"
    private_dns                  = "ip-172-31-61-141.ec2.internal"
    private_ip                   = "172.31.61.141"
    public_dns                   = "ec2-54-166-19-244.compute-1.amazonaws.com"
    public_ip                    = "54.166.19.244"
    security_groups              = [
        "default",
    ]
    source_dest_check            = true
    subnet_id                    = "subnet-1facdf35"
    tenancy                      = "default"
    volume_tags                  = {}
    vpc_security_group_ids       = [
        "sg-5255f429",
    ]

    credit_specification {
        cpu_credits = "standard"
    }

    root_block_device {
        delete_on_termination = true
        iops                  = 100
        volume_id             = "vol-0079e485d9e28a8e5"
        volume_size           = 8
        volume_type           = "gp2"
    }
}
You can see that by creating our resource, we've also gathered a lot of information about it. These values can actually be referenced to configure other resources or outputs, which will be covered later in the getting started guide.

»**Provisioning**
The EC2 instance we launched at this point is based on the AMI given, but has no additional software installed. If you're running an image-based infrastructure (perhaps creating images with Packer), then this is all you need.

However, many infrastructures still require some sort of initialization or software provisioning step. Terraform supports provisioners, which we'll cover a little bit later in the getting started guide, in order to do this.


Don’t think you’re importing the 900 weight then.

> On Aug 7, 2019, at 10:21 PM, Jacob Patel Iglesias <notifications@github.com> wrote:
>
> 900 is max.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub, or mute the thread.


good


What's the difference between restore_tablet_path and restore_schema_hash_path ?


if `_reload_tablet` fail, why don't we remove destination director.


Successfully aliased the URL <https://sapper-tailwind-kstyxxgt4.now.sh> to the following aliases:

* https://sapper-tailwind.mindfuljs.now.sh
* https://sapper-tailwind-git-master.mindfuljs.now.sh


fix #2


should check the return value


:white_check_mark: All Rules (3 / 3) Passed

      :crown: Good job! this pull request is aligned with your organization's best practices!

      :point_right: You can review your rules settings at smart policy management :point_left:

:point_right: click here to view a full list of the events :point_left:


Successfully aliased the URL <https://rc-tree-e1280b9pf.now.sh> to the following aliases:

* https://rc-tree.react-component.now.sh
* https://rc-tree-git-master.react-component.now.sh


IBM Cloud [toolchain](https://cloud.ibm.com/devops/toolchains/ec39efc7-cd25-45db-97eb-94fa2b7ecf6e?env_id=ibm%3Ayp%3Aus-south "lightbluecompute-devops-20190807040640277"): [Delivery Pipeline](https://cloud.ibm.com/devops/pipelines/7b92560c-38d9-4dfb-8f70-f7dafbad8f9d "lightblue-web") deployed [lightblue-web-20190807040640277](https://github.com/alexcarroll1/lightblue-web-20190807040640277/releases/tag/deploy-ibm-yp-us-south-alex.carroll1-ibm.com-dev-20190808-060326 "deploy-ibm-yp-us-south-alex.carroll1-ibm.com-dev-20190808-060326") to [dev](https://console.bluemix.net/apps/f7271f42-d62c-47de-b430-cf6ced1e10ad?env_id=ibm:yp:us-south "ibm:yp:us-south:alex.carroll1@ibm.com:dev"), including this commit


Hi, just a comment. The separator could use  Unicode Character “⎯” (U+23AF)  if available. It looks better visually as a continuous line.


Tested and approved : compiles fine on my setup. Thanks !


Copy of this build can be found at
https://builds.myetherwallet.com/build/f3435f6a16447166f14fcacc06acd69e8d8f9a49/index.html
                       https://www.cloudflare-ipfs.com/ipfs/Qme4DdS3T1vGhtq3jKz56dX7NQ7SSJf5atjZoe88tFbf6V
                       Virus Total analysis
                       https://www.virustotal.com/file/c494362a384ce903fd0e3a6c99bf937b807f2fee7b069413dfb5998b9683ab5c/analysis/1565244230/


@dbo-odoo @nla-odoo That's what I was afraid of. Thanks for checking (and for this improvement)!


Thanks Werner for the detailed info.
Why we do not just replace /EHsc and /EHs in the CMAKE_CXX_FLAGS_RELEASE and leave the debug one?


The directory is already using the dash, why should it be renamed?


Deployment failed with the following error:

~~~
Your `package.json` file is missing a `build` property inside the `script` property.
~~~


:hourglass_flowing_sand: Waiting for custom rule data to be resolved
:point_right: click here to view a full list of the events :point_left:


Successfully aliased the URL <https://staticman-bot-14s8eyezy.now.sh> to the following aliases:

* https://staticman-bot.kimdhoebot.now.sh
* https://staticman-bot-git-master.kimdhoebot.now.sh


Successfully aliased the URL <https://dailyrandomphotogithubio-pg5xmyik3.now.sh> to the following aliases:

* https://dailyrandomphoto.now.sh
* https://photooftheday.now.sh
* https://randomphoto.now.sh
* https://dailyphoto.now.sh
* https://picoftheday.now.sh
* https://todayphoto.now.sh
* https://dailyrandomphotogithubio.dailyrandomphoto.now.sh
* https://dailyrandomphotogithubio-git-master.dailyrandomphoto.now.sh


# Specs execution successful
:scroll: [View logs](http://bamboo.comnull)
### Plans updated

Bamboo specs have been successfully imported and the following plans have been updated.

Project | Plan | Build
---|---|---
[Test](http://bamboo.com/browse/TEST) | [Comment test](http://bamboo.com/browse/TEST-CTEST)  | :white_check_mark: [\#1](http://bamboo.com/browse/TEST-CTEST-1)
[New project](http://bamboo.com/browse/NEW) | [Disabled plan](http://bamboo.com/browse/NEW-DISABLED) **disabled** | :white_check_mark: [\#1](http://bamboo.com/browse/NEW-DISABLED-1)

### Deployments updated

Bamboo specs have been successfully imported and the following deployment projects have been updated.

|Deployment project |
----|
[Deployment test](http://bamboo.com/deploy/viewDeploymentProjectVersions.action?id=2162689)|


a


❌ [Build was (probably) aborted](https://jenkins.internalx.com/job/macios/job/xcode11/194/display/redirect)

🔥 [Jenkins job](https://jenkins.internalx.com/job/macios/job/xcode11/194/display/redirect) (on internal Jenkins) failed in stage(s) 'Running XM tests on '10.15', Running XM tests on '10.15'' 🔥

✅ [Build succeeded](https://jenkins.internalx.com/job/macios/job/xcode11/194//console)
✅ Packages: [xamarin.ios-12.99.2.45.pkg](https://bosstoragemirror.blob.core.windows.net/wrench/jenkins/xcode11/193ae8bfdfe7c10ec17f7441d954397ebf15eae7/194/package/xamarin.ios-12.99.2.45.pkg) [xamarin.mac-5.99.2.45.pkg](https://bosstoragemirror.blob.core.windows.net/wrench/jenkins/xcode11/193ae8bfdfe7c10ec17f7441d954397ebf15eae7/194/package/xamarin.mac-5.99.2.45.pkg)
✅ [API Diff (from stable)](http://xamarin-storage/jenkins/xamarin-macios/xcode11/193ae8bfdfe7c10ec17f7441d954397ebf15eae7/194/jenkins-results/api-diff/index.html)
ℹ [API Diff (from PR only)](http://xamarin-storage/jenkins/xamarin-macios/xcode11/193ae8bfdfe7c10ec17f7441d954397ebf15eae7/194/jenkins-results/apicomparison/api-diff.html) (please review changes)
✅ [Generator Diff](http://xamarin-storage/jenkins/xamarin-macios/xcode11/193ae8bfdfe7c10ec17f7441d954397ebf15eae7/194/jenkins-results/generator-diff/index.html) (no change)
🔥 [Xamarin.Mac tests on 10.15 failed: Xamarin.Mac tests on macOS 10.15 failed (introspection)](https://jenkins.internalx.com/job/macios/job/xcode11/194/display/redirect) 🔥
🔥 [Test run failed](http://xamarin-storage/jenkins/xamarin-macios/xcode11/193ae8bfdfe7c10ec17f7441d954397ebf15eae7/194/jenkins-results/tests/index.html) 🔥

# Test results

<details>
<summary>1 tests failed, 233 tests passed.</summary>

## Failed tests

 * monotouch-test/watchOS 32-bits - simulator/Debug: Crashed
</details>


thanks arjun

On Thu, Aug 8, 2019 at 8:08 AM arjunmdas <notifications@github.com> wrote:

> This can be written as
>
> rollno.nil?
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/sethugudi/saas-201-sethuraman/commit/bbf945389d27f6be97a865b48035cc57a4f7542c?email_source=notifications&email_token=AMY52PWAP7UHR2NEF5J54YTQDOBIZA5CNFSM4IKFY3OKYY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBBAKS4#commitcomment-34613852>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AMY52PWRP34DVYWG6TLKJGTQDOBIZANCNFSM4IKFY3OA>
> .
>


> thanks for the update @aaronqiuchiu

you are welcome


PR_opened/Fix_7315_BuildDocs (jmarrec) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-UnitTestsCoverage-Debug: OK (1121 of 1121 tests passed, 0 test warnings)

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


Looks like you beat me to it. Thanks.


Successfully aliased the URL <https://hydrus-web-cftrr9qdq.now.sh> to the following aliases:

* https://hydrus.app
* https://hydrus-web.floogulinc.now.sh
* https://hydrus-web-git-master.floogulinc.now.sh


there is no schema hash in the restore_tablet_path


|  03  | 毕超然    |  NKU  |    旅行 电影     |


destination will be removed


Unhandled Failure


This file is empty. Is it still needed?


ok


Remove pip module, unified use of apt-get for installation


Successfully aliased the URL <https://phew-m1d0t9uiq.now.sh> to the following aliases:

* https://phew.kimdhoebot.now.sh
* https://phew-git-master.kimdhoebot.now.sh


@alanbato @web-flow @lintool  it seems there are few issues. I would like to contribute to this project. WIll it be ok ?


Hi, which ones do you need removing? What problems do you have?


> FYI: 32bit is passed now, 64 won't - I've just made some sw changes.
> I'll restore it during couple of days.
>
> https://ci.appveyor.com/project/zdenop/tesseract/builds/26525170

Funny that build is not broken as I thought.


Thanks @zerouid  feel free to send a PR


cache-psy (energy-plus) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-IntegrationCoverage-Debug: OK (667 of 667 tests passed, 0 test warnings)

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


> Oh, this is what I was waiting for!
> can you build this without power patches?

Which ones do you need removing?
Are you having problems with power management?


uyggyuyg


@waitingsong windows端不支持`` rm -rf ``


[![Visit Site](https://raw.githubusercontent.com/pantheon-systems/ci-drops-8/0.1.0/data/img/visit-site-36.png)](https://ci-32-d8cij.pantheonsite.io/)

Created multidev environment [ci-32](https://dashboard.pantheon.io/sites/5e0d4d42-4aed-448e-9b26-16d7b8a3cab2#ci-32) for d8cij.


Successfully aliased the URL <https://noahzinsmeistercom-h620ddm92.now.sh> to the following aliases:

* https://noahzinsmeister.com
* https://noahzinsmeistercom.noahwz.now.sh
* https://noahzinsmeistercom-git-master.noahwz.now.sh


| 35       |    孟磊 |  数字媒体学院 |    散步    |


Ok, maybe we should move include folder to inst/include


:white_check_mark: All Rules (3 / 3) Passed

      :crown: Good job! this pull request is aligned with your organization's best practices!

      :point_right: You can review your rules settings at smart policy management :point_left:

:point_right: click here to view a full list of the events :point_left:


no


@sushantpaste Can we contribute this back? We need to check for other amounts(if any) that had their decimal digits numbers increased in DB as well.


PlantMassFlowRatesChangeForTankSourceSide (yzhou601) - x86_64-Linux-Ubuntu-18.04-cppcheck: OK (0 of 0 tests passed, 0 test warnings)

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


I don't think so. Only methods which were actually just a passthrough to `Arr` (and `Str`) where deprecated.

But `last()` is it's own "thing" and it's not `Arr::last`:
```php
if (! function_exists('last')) {
    /**
     * Get the last element from an array.
     *
     * @param  array  $array
     * @return mixed
     */
    function last($array)
    {
        return end($array);
    }
}
```
That workaround is what makes it work inline but not `end()`; that is the unfortunate thing here.


Probably better calling getTime() to avoid this mess `Thu Aug 08 2019 08:25:23 GMT+0200 (Central European Summer Time)`


PlantMassFlowRatesChangeForTankSourceSide (yzhou601) - x86_64-Linux-Ubuntu-18.04-custom_check: OK (9 of 9 tests passed, 0 test warnings)

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


Deployment failed with the following error:

~~~
Your `package.json` file is missing a `build` property inside the `script` property.
~~~


Nice!  I knew there must be a better way!


Successfully aliased the URL <https://noahzinsmeistercom-591nbhd7u.now.sh> to the following aliases:

* https://noahzinsmeister.com
* https://noahzinsmeistercom.noahwz.now.sh
* https://noahzinsmeistercom-git-master.noahwz.now.sh


|  29  |   林存玲    |   清大创新  |    看书、看电影     |


Oh `Date.now()` is the same as `getTime()`, ignore me 😁


It should be `ccc.github.github_api` right?


Is there a way to disable this? (so files in the trash will never be permanently deleted until I do it)


check initial


It needs to renamed to global executor


啥玩意


你真的很无聊诶


|    |姜欣辰｜大连工业大学｜ 绘画  摄影｜


я вообще не понимаю что тут делать!


I have problems with IOMMU. and they started after power management changes.
DMAR tables not working, NVME device loads on the nth try


This can be part of config


Might be best to update https://github.com/JunoLab/language-weave/blob/master/menus/language-weave.cson as well :)


This change breaks V1.1:
After joining, the MAC command RekeyInd is sent as DataUp (CID 11). The server responds with RekeyConf. This is now removed from the mac commands list because there is no check with CIDsStickyAnsCmds[]. It is however also removed a second time in ProcessMacCommands, case SRV_MAC_REKEY_CONF.

            case SRV_MAC_REKEY_CONF:
            {
                uint8_t serverMinorVersion = payload[macIndex++];

                // Compare own LoRaWAN Version with server's
                if( MacCtx.NvmCtx->Version.Fields.Minor == serverMinorVersion )
                {
                    // If they equal remove the sticky RekeyInd MAC-Command.
                    LoRaMacCommandsGetCmd( MOTE_MAC_REKEY_IND, &macCmd);
                    LoRaMacCommandsRemoveCmd( macCmd );
                }
                break;
            }

Because there is no check on the return value of LoRaMacCommandsGetCmd, the remove proceeds and results in an invalid deletion on the underlying linked list, It causes a hardfault on my LPC 54628.

See trace below which gives an idea of th flow:

[lorawan] initialisation
[lorawan] join;attempt=0
[lorawan] join=executing
[lorawan] lwn_network_task RECV
DEBUG - ProcessRadioTxDone
$ [lorawan] lwn_network_task RECV
DEBUG - ProcessRadioRxDone
LoRaMacCommandsAddCmd - cid: 11 <---- mac command added
DEBUG - ProcessRadioRxDone - exit
[lorawan] JOIN OK
[lorawan] MIB_DEV_ADDR:  FC0023C4
[lorawan] join=success
[lorawan] session=get
[lorawan] SEND START
[lorawan] lwn_network_task RECV
DEBUG - ProcessRadioTxDone
[lorawan] lwn_network_task RECV
DEBUG - ProcessRadioRxDone
LoRaMacCommandsRemoveCmd - cid: 11 <---- mac command removed first time, OK
ProcessMacCommands - payload[macIndex]: 11
LoRaMacCommandsRemoveCmd - cid: 181 <----- mac command remove attempted 2nd time but on empty list, FAIL


Successfully aliased the URL <https://reactforxiangyun-g4o2pdcp5.now.sh> to the following aliases:

* https://reactforxiangyun.1098693467.now.sh
* https://reactforxiangyun-git-master.1098693467.now.sh


Just track caf.


祝贺开场词


ki humans


HELLOW WORD


mkdir awesome
cd awesome
git init


GUI app using the AlphaNumGenerator


|  31   |姜欣辰｜大连工业大学｜ 绘画 摄影｜


paxton put on his programmer socks


Successfully aliased the URL <https://noahzinsmeistercom-6e362fjx2.now.sh> to the following aliases:

* https://noahzinsmeister.com
* https://noahzinsmeistercom.noahwz.now.sh
* https://noahzinsmeistercom-git-master.noahwz.now.sh


Why switch to a potentially unstable android studio release?


Unhandled Failure


* 增加文件


We can use the `map` method to make this simpler, and cleaner. `map` creates an array containing whatever the block returns:

```ruby
@departments = ['EEE', 'MECH', 'CSE', 'CIVIL'].map do |department_name|
  Department.new(department_name)
end
```


Successfully aliased the URL <https://first-zeit-g6s33s71a.now.sh> to the following aliases:

* https://first-zeit.danikristianto.now.sh
* https://first-zeit-git-master.danikristianto.now.sh


I am using develop image always. When EPGRefresh is running in standby and in EPGRefresh is set option "Flush EPG before refresh" to "Yes", then enigma crashes on all my boxes with same error. And it seems, it began after added one of this two your last patches. And when there was not problem before it, where could be problem ?

`/usr/bin/enigma2(handleFatalSignal(int, siginfo_t*, void*)) [0x72914]
/lib/libc.so.6(__default_rt_sa_restorer) [0xB626B3D0]
/usr/bin/enigma2(eEPGCache::channel_data::cleanupOPENTV()) [0xD39D4]
/usr/bin/enigma2(eEPGCache::channel_data::startEPG()) [0xD4738]
/usr/bin/enigma2(eEPGCache::flushEPG(uniqueEPGKey const&)) [0xD7B38]
/usr/bin/enigma2(n/a) [0x1A9D04]
-------FATAL SIGNAL`

When I disable "Flush EPG before refresh" (config.plugins.epgrefresh.erase.value) in plugin - no problem then.
`		if config.plugins.epgrefresh.erase.value:
			print("[EPGRefresh] flushing EPG cache...")
			from enigma import eEPGCache
			epgcache = eEPGCache.getInstance()
			epgcache.flushEPG()`


Try to avoid _indirection_ in your code. What you're doing here is using the _getter_ method `departments()` supplied by the attr_accessor statement at the top of the class.

However, the attr_accessor's purpose is to allow access to these values from outside the class. Methods inside the class can safely (and directly) access the instance variables that hold these values - `@departments` in this case.


@niko-rodrigue


[![Visit Site](https://raw.githubusercontent.com/pantheon-systems/ci-drops-8/0.1.0/data/img/visit-site-36.png)](https://ci-37-d8cij.pantheonsite.io/)

Created multidev environment [ci-37](https://dashboard.pantheon.io/sites/5e0d4d42-4aed-448e-9b26-16d7b8a3cab2#ci-37) for d8cij.


小版本号改API。。。好坑呀🤔


Maybe you need to upgrade your cmake?


Try not to leave old or useless comments in your code - use comments to leave helpful hints about complex sections of code - it's quite helpful when you've working in a team.


Adding a border for the dart launch config tab will differentiate with the other eclipse launch tabs.


PlantMassFlowRatesChangeForTankSourceSide (yzhou601) - x86_64-Linux-Ubuntu-18.04-gcc-7.4: OK (2487 of 2493 tests passed, 2 test warnings)

Messages:\n
 * 7 tests had: EIO diffs.
 * 1 test had: ESO small diffs.
 * 1 test had: BND diffs.
 * 3 tests had: AUD diffs.
 * 6 tests had: ESO big diffs.
 * 4 tests had: MTR big diffs.
 * 3 tests had: RDD diffs.
 * 6 tests had: Table big diffs.
 * 2 tests had: MTR small diffs.

Failures:\n

regression Test Summary
 * Passed: 676
 * Failed: 6

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


a


Compilation error will occur!


sfsf


Ah yes thanks, it was a typo on the dictionary name on misp2stix_mapping.py


Successfully aliased the URL <https://noahzinsmeistercom-dagwf6jr1.now.sh> to the following aliases:

* https://noahzinsmeister.com
* https://noahzinsmeistercom.noahwz.now.sh
* https://noahzinsmeistercom-git-master.noahwz.now.sh


Thanks! Added with https://github.com/danmar/cppcheck/commit/27cc58db4374dbcadf8582b1d89d2778fe6bc7d4


Great work arnav!!


Successfully aliased the URL <https://rc-tree-k1069hhgm.now.sh> to the following aliases:

* https://rc-tree.react-component.now.sh
* https://rc-tree-git-master.react-component.now.sh


This should start with 'Error: ' - This is one of the failing tests


The problem is that `mdsplib` contains these relative folder locations, and have hard-coded references.

I already have a script that modifies some of the content of `mdsplib`. Let me take a look to automate this (and move `metar.h` into `src`).


3.15.1 is the newest version available on MacPorts, which version are you using?

$ENV{} is not a new feature (it's documented [as far back as 3.0.2](https://cmake.org/cmake/help/v3.0/variable/ENV.html)) so I wonder if it's being misused/is inapplicable here. I know nothing about cmake, however.


运行python app.py db init 没有办法生成表结构


That's the problem of #7614. It `type_field` follows once without detecting recursive abstracts.
Since `get_underlying_type` do recursive check I thought it's ok to change it like this.
If not, then we need to merge #8609


[![Visit Site](https://raw.githubusercontent.com/pantheon-systems/ci-drops-8/0.1.0/data/img/visit-site-36.png)](https://ci-40-d8cij.pantheonsite.io/)

Created multidev environment [ci-40](https://dashboard.pantheon.io/sites/5e0d4d42-4aed-448e-9b26-16d7b8a3cab2#ci-40) for d8cij.


Successfully aliased the URL <https://rc-tree-5h6b7eae4.now.sh> to the following aliases:

* https://rc-tree.react-component.now.sh
* https://rc-tree-git-master.react-component.now.sh


What is this feature?
@alexbers
@seriyps


还有那个#150 也莫名其妙。自己图片太大怪框架(;¬_¬)。
使用id直接设置图片，Android内部会有bitmap重用的，相比来说手动缩放出来的bitmap不会重用，反而会消耗更多内存。
所以我认为，向前兼容的重载方法直接设置id就行了
像这样：
```kotlin
fun BGABanner.setData(vararg drawableIds: Int) {
    setData(drawableIds.map { drawableId ->
        ImageView(context).apply {
            setImageResource(drawableId)
            isClickable = true
            scaleType = ImageView.ScaleType.CENTER_CROP
        }
    })
}
```


:white_check_mark: All Rules (3 / 3) Passed

      :crown: Good job! this pull request is aligned with your organization's best practices!

      :point_right: You can review your rules settings at smart policy management :point_left:

:point_right: click here to view a full list of the events :point_left:


🔥 Device tests completed (Failed) on iOS on [Azure DevOps](https://dev.azure.com/devdiv/DevDiv/_build/index?buildId=2924137)(iOS): [Html Report](http://xamarin-storage/jenkins/xamarin-macios/alex-mono-bump-d163/17b415b3d1c294eda07f5f6a7c1a2a067ae35c82/2924137/device-tests/jenkins-results/tests/index.html) 🔥

# Test results

<details>
<summary>113 tests failed, 0 tests passed.</summary>

## Failed tests

 * monotouch-test/iOS Unified 64-bits - device/Debug: Crashed
 * framework-test/iOS Unified 64-bits - device/Debug: Crashed
 * interdependent-binding-projects/iOS Unified 64-bits - device/Debug: Crashed
 * fsharp/iOS Unified 64-bits - device/Debug: Crashed
 * dont link/iOS Unified 64-bits - device/Debug: Crashed
 * link all/iOS Unified 64-bits - device/Debug: Crashed
 * link sdk/iOS Unified 64-bits - device/Debug: Crashed
 * mono-native-compat/iOS Unified 64-bits - device/Debug: Crashed
 * mono-native-unified/iOS Unified 64-bits - device/Debug: Crashed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/Debug: Crashed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/Debug: Crashed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/Debug: Crashed
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/Debug: Crashed
 * mscorlib/iOS Unified 64-bits - device/Debug: Crashed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/Debug: Crashed
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Release: Crashed
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Debug (dynamic registrar): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Release (all optimizations): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Debug (all optimizations): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Debug: SGenConc: Crashed
 * monotouch-test/iOS Unified 64-bits - device/Debug (interpreter): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Debug (interpreter -mscorlib): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Release (interpreter -mscorlib): Crashed
 * framework-test/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * framework-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * framework-test/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * framework-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * framework-test/iOS Unified 64-bits - device/Release: Crashed
 * framework-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * interdependent-binding-projects/iOS Unified 64-bits - device/Release: Crashed
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * fsharp/iOS Unified 64-bits - device/Release: Crashed
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * dont link/iOS Unified 64-bits - device/Release: Crashed
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * link all/iOS Unified 64-bits - device/Release: Crashed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * link sdk/iOS Unified 64-bits - device/Release: Crashed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * mono-native-compat/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * mono-native-compat/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * mono-native-compat/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * mono-native-compat/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * mono-native-compat/iOS Unified 64-bits - device/Release: Crashed
 * mono-native-compat/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * mono-native-unified/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * mono-native-unified/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * mono-native-unified/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * mono-native-unified/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * mono-native-unified/iOS Unified 64-bits - device/Release: Crashed
 * mono-native-unified/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/Release: Crashed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/Release: Crashed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/Release: Crashed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/Release: Crashed
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * mscorlib/iOS Unified 64-bits - device/Release: Crashed
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * mscorlib/iOS Unified 64-bits - device/Debug: SGenConc: Crashed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/Release: Crashed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
</details>


the zh-cn version (FountainHub#3)


Commit was authored by: Isaac Hernandez <isaacfi@gmail.com> @isaacfi

Author information was lost when squashing commit. Please see #312 for the original commit history. Sorry for any inconvenience.


pakka

On Thu, Aug 8, 2019 at 12:27 PM arjunmdas <notifications@github.com> wrote:

> This should start with 'Error: ' - This is one of the failing tests
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/sethugudi/saas-201-sethuraman/commit/bbf945389d27f6be97a865b48035cc57a4f7542c?email_source=notifications&email_token=AMY52PU7UXVPOTMQLAH2JVTQDO7VFA5CNFSM4IKFY3OKYY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBBAMSY#commitcomment-34615896>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AMY52PXOG5TN4O76VGJ4TXTQDO7VFANCNFSM4IKFY3OA>
> .
>


ok


Closes #1


Making assumptions about the file ending (or "extension") can be dangerous. What if the file ends with `.sbml`?


Is this line  necessary?
Add this line will cause error.
This line will cause ignore templates.go,templates_others.go,templates_windows.go in dir mongo-tools\vendor\github.com\spacemonkeygo\spacelog.
so we will get this error after git download the code:
vendor/src/github.com/spacemonkeygo/spacelog/handler.go:51:34: undefined: StdlibTemplate
vendor/src/github.com/spacemonkeygo/spacelog/setup.go:48:46: undefined: ColorizeLevel
vendor/src/github.com/spacemonkeygo/spacelog/setup.go:135:8: undefined: SyslogTemplate
vendor/src/github.com/spacemonkeygo/spacelog/setup.go:140:8: undefined: DefaultTemplate
vendor/src/github.com/spacemonkeygo/spacelog/setup.go:145:8: undefined: DefaultTemplate
vendor/src/github.com/spacemonkeygo/spacelog/setup.go:150:8: undefined: StandardTemplate


:x: 1 / 6 Rules Failed

      :cold_sweat: It's not you, it's your code. It may not be aligned with your organization's best practices

      :point_right: You can review your rules settings at smart policy management :point_left:

:point_right: click here to view a full list of the events :point_left:


https://stackoverflow.com/questions/57375015/i-was-trying-to-insert-websocket-apis-in-a-project-that-uses-rest-apis-using-s  Can anyone tell me what's the problem with those codes in that link?


There's a principle called _Have a single-source-of-truth_, that is being broken here, when you store the count of students separately from the list of students.

We _know_ that the number of students in a department is the count of student names that are stored in each section - so we can always calculate that number. If we store the count separately, then we need to update the count each time a student is added or removed from any section. This is what you've done in the methods below.

However, we can avoid that entirely by changing the data-structure a bit to allow us to _calculate_ the number of students.

```ruby
class Department
  def initialize
    # Let's try to make each section hold an array of student names.
    @sections = { 'A' => [], 'B' => [], 'C' => [] }
  end

  def students_count
    # The count of students in the department is simply the sum of the lengths of each section.
    # Note that Enumerable#sum is a convenience method like map. I think you can guess what it does.
    @section.values.sum { |section| section.length }
  end

  def section_with_free_slots
    # Just return the first section that has length less than 10.
    @sections.first { |section| section.length < 10 }
  end

  # etc...
end
```

Similarly, we don't need to store the roll number either. We _know_ that the roll numbers are generated depending on the alphabetical order of students. There is a **logic** (rules) that define how they're created. So as long as students are ordered within the array, we can _calculate_ the roll number from the index.

I think you should be able to see where I'm going with this.

The advantage of this approach is that it frees us (the developers) from having to keep track of the number of students, or remembering to change it when we do something to alter the list of students - we push the responsibility onto a method by simply writing down the logic to achieve it.


@aknuds1 the main idea behind preprocessing instructions was to let multiple instructions execute on the same node. That would have allowed to have smaller instruction sets for each node.

e.g. a preprocessor to update all anchor tags, another to add specific ids to tags containing specific `preprocess='true'`. If an anchor tag contained `preprocess='true'` then the updates would depend on the order of instruction set while the expected output was to have an anchor tag get its href updated and also have an id added.

The only way to get it do the above is to have multiple preprocessing instructions, 1 for anchor update, another for adding id and also another that checks both anchor and the attribute to do both things together too.


ZEIT Now cannot deploy this project to production due to following domain related issues:

 * `snuggsi.com`(for alias `snuggsi.com`) is not found inside your account. [Add it](https://zeit.co/dashboard/domains?action=add&domain=snuggsi.com).


It's the PCI stuff then. If you are building it yourself you can disable these things editing devicetree.cb. Just switch PcieRpClkReqSupport (2,3 and 8) to 0. The nvme stuff is odd though. What distro/kernel/nvme are you on?


FYI https://mvnrepository.com/artifact/com.github.docker-java/docker-java/3.1.5


@mishacucicea what is the `cross-env`?


New-Feature-CBVAV-Mods (rraustad) - x86_64-Linux-Ubuntu-18.04-cppcheck: OK (0 of 0 tests passed, 0 test warnings)

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


New-Feature-CBVAV-Mods (rraustad) - x86_64-Linux-Ubuntu-18.04-custom_check: OK (9 of 9 tests passed, 0 test warnings)

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


This commit are breaking gfp-doctor's own tests.


It didn't cause me any problems, but the server started throwing a Tick Next Tick exception, does this commit fix this error?


@mishacucicea this does not work with the way `node-config` [works](https://github.com/lorenwest/node-config/issues/272). It might be working on local because of explicitly setting the variable as boolean but it is not working when I deploy it to the AWS.


Well done Manogna!


Where?


:white_check_mark: All Rules (2 / 2) Passed

      :crown: Good job! this pull request is aligned with your organization's best practices!

      :point_right: You can review your rules settings at smart policy management :point_left:

:point_right: click here to view a full list of the events :point_left:


New-Feature-CBVAV-Mods (rraustad) - x86_64-Linux-Ubuntu-18.04-gcc-7.4: Build Failed

Messages:\n
 * 11 tests had: EIO diffs.
 * 1 test had: ESO small diffs.
 * 5 tests had: BND diffs.
 * 7 tests had: AUD diffs.
 * 10 tests had: ESO big diffs.
 * 6 tests had: MTR big diffs.
 * 7 tests had: RDD diffs.
 * 10 tests had: Table big diffs.
 * 4 tests had: MTR small diffs.

Failures:\n

regression Test Summary
 * Passed: 672
 * Failed: 10

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


which parts require sudo really?


ok


Oh, it's under account settings. I hadn't seen that. Anyways, it's not meant to be shown to other users anymore, so I still think this change is good.


except writing to the /usr/bin


@mishacucicea we might need to validate that the project member role of the requesting user is manager category as configured [here](https://github.com/topcoder-platform/tc-project-service/blob/dev/src/constants.js#L32) instead of directly validating the user role. May be we can add both types of role validation to be more secure, but I think we do need to validate the project member role as well. We already have the project members list available in request's context as used [here](https://github.com/topcoder-platform/tc-project-service/blob/dev/src/routes/scopeChangeRequests/update.js#L81).


하하하하하하


Successfully aliased the URL <https://ohjelmointi-20-74li8okq8.now.sh> to the following aliases:

* https://ohjelmointi-20.now.sh
* https://ohjelmointi-20.mooc.now.sh
* https://ohjelmointi-20-git-master.mooc.now.sh


Maybe I'll do that with the ipv6 fix. Is there a special window of opportunity here now, or what do you mean?


Would it not be better to use the default value for options? https://symfony.com/doc/current/console/input.html#options-with-optional-arguments


Maybe use the null coalescing operator (`??`) and/or throw an error, if the stack is set to `0` since there seems to be a problem which might not be sensible to use a magic default value (maybe a bug in a shell script, where you should be notified, that something does not work as expected).


Same as above. Maybe it would be also reasonable to change this behavior in a different Pull Request.


It makes probably more sense to change the order of `\Throwable`and `\Exception`. `\Throwable` is PHP 7 only, and for PHP 5 nothing happens in this catch branch (but you still want to catch the `\Exception`). But since the code is now PHP 7 only, the `\Exception` branch could be removed all together.


Why is the space removed, should be there, see https://github.com/FriendsOfPHP/PHP-CS-Fixer#usage (`cast_spaces`), same is true for all other type casts.


Cha


网页地址


You need sudo for all package installations, both writing to `/usr/bin` (and so on) and for updating the package database. The package manager is also authorized to run any scripts included in the package...

`dpkg: error: requested operation requires superuser privilege`


Thanks a lot for writing this. A lot of good proposals in here ! Can you address the comments I made first ?
Thanks.


The keys can be of any type, not only `int`. I think text refers to this code which just uses encoding/json to encode and decode keys (`string` type is an exception to remove the quote characters that would be present using json).

```go

func serializeMapKey(v reflect.Value) (string, error) {
	if v.Type().Kind() == reflect.String {
		return v.Interface().(string), nil
	}

	arr, err := json.Marshal(v.Interface())
	if err != nil {
		return "<ERROR>", err
	}
	return string(arr), nil
}
```


I think the correct name would be callbacks here, since those are implemented as callbacks I believe.


`with at key` should be `at key`


I would keep 'to request recursive storage' in the parenthesis.


I find the first sentence a bit strange, is it just me ?


This is explained in next section.


I think there is a wild ')' here.


Not all types are supported.
functions and channels cannot be encoded.
Slices are not supported and it might be challenging to implement them efficiently.
Static arrays are not supported but it should not be too hard to add them.

Note: For now, arrays are encoded as json blobs when they are needed.


Should it be a 'and' rather than a comma  in:

> to *set*, *get* and *synchronize* objects, Go types (e.g. `int`, `string`, `struct`, `map`, etc..),


Hi Paolo,# @paoloemilioserra
Is possible this changes to be implement also for Link? To not rebuild the corridor when export link, or at least to have a Boolean in Dynamo if to rebuild or not.


I added some words.


Okay I have just added fatJar() tasks to the cineast-api and cineast-runtime projects.


Nice! 👍


PR_opened/Fix_7315_BuildDocs (jmarrec) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-IntegrationCoverage-Debug: OK (667 of 667 tests passed, 0 test warnings)

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


:white_check_mark: All Rules (2 / 2) Passed

      :crown: Good job! this pull request is aligned with your organization's best practices!

      :point_right: You can review your rules settings at smart policy management :point_left:

:point_right: click here to view a full list of the events :point_left:


Actually, although PINGAN TECH submitted their result on EN->ZH track, they didn't present any formal technical paper or poster.

ref. http://www.statmt.org/wmt19/pdf/WMT0001.pdf


What does it do

`var _r_r_ = (+(+!+[]+(...)` ?

I noticed that its connected with in game font:

```
c.font = "30px GameFont";
        c.fillText(_r_r_, 20, 250);
```

It's very interesting!


Successfully aliased the URL <https://backyourstack-jddhgwvxzm.now.sh> to the following aliases:

* https://backyourstack.now.sh
* https://backyourstack.com
* https://www.backyourstack.com


❌ [Build was (probably) aborted](https://jenkins.internalx.com/job/macios/job/alex-mono-bump/1/display/redirect)

🔥 [Jenkins job](https://jenkins.internalx.com/job/macios/job/alex-mono-bump/1/display/redirect) (on internal Jenkins) failed in stage(s) 'Test run, Test run' 🔥

✅ [Build succeeded](https://jenkins.internalx.com/job/macios/job/alex-mono-bump/1//console)
✅ Packages: [xamarin.ios-12.15.0.287.pkg](https://bosstoragemirror.blob.core.windows.net/wrench/jenkins/alex-mono-bump/829da61569e40bc88fb04e3959f3c492de8c6cbc/1/package/xamarin.ios-12.15.0.287.pkg) [xamarin.mac-5.15.0.287.pkg](https://bosstoragemirror.blob.core.windows.net/wrench/jenkins/alex-mono-bump/829da61569e40bc88fb04e3959f3c492de8c6cbc/1/package/xamarin.mac-5.15.0.287.pkg)
✅ [API Diff (from stable)](http://xamarin-storage/jenkins/xamarin-macios/alex-mono-bump/829da61569e40bc88fb04e3959f3c492de8c6cbc/1/jenkins-results/api-diff/index.html)
✅ [API Diff (from PR only)](http://xamarin-storage/jenkins/xamarin-macios/alex-mono-bump/829da61569e40bc88fb04e3959f3c492de8c6cbc/1/jenkins-results/apicomparison/api-diff.html) (no change)
✅ [Generator Diff](http://xamarin-storage/jenkins/xamarin-macios/alex-mono-bump/829da61569e40bc88fb04e3959f3c492de8c6cbc/1/jenkins-results/generator-diff/index.html) (no change)
🔥 [Test run failed](http://xamarin-storage/jenkins/xamarin-macios/alex-mono-bump/829da61569e40bc88fb04e3959f3c492de8c6cbc/1/jenkins-results/tests/index.html) 🔥

# Test results

<details>
<summary>4 tests failed, 167 tests passed.</summary>

## Failed tests

 * [NUnit] Mono Mac OS X BCL tests group 2/Mac/Full: Failed (Test run crashed (exit code: 134).)
 * [NUnit] Mono SystemWebServicesTests/watchOS 32-bits - simulator/Debug: Crashed
 * [xUnit] Mono MicrosoftCSharpXunit/watchOS 32-bits - simulator/Debug: Crashed
 * introspection/watchOS 32-bits - simulator/Debug (watchOS 2.0): Crashed
</details>


[Your benchmark job](https://github.com/JuliaLang/julia/commit/ad8cf8d8f7b2ca9f2612581a21283b14c7b22e7d#commitcomment-34614262) has completed - possible performance regressions were detected. A full report can be found [here](https://github.com/JuliaCI/BaseBenchmarkReports/blob/ed14321dae742707ae66fee50ae7e24a52e1edd1/daily_2019_08_08/report.md). cc @ararslan


:hourglass_flowing_sand: Waiting for custom rule data to be resolved
:point_right: click here to view a full list of the events :point_left:


@MinhasRizwan You should look into ktx extensions to reference views initialized in xml


We don't need this.


Should be in the `.gradle` subpackage.


[Daniel Waterworth posted](https://review.discourse.org/t/fix-remove-dependency-on-present-in-distributed-mutex-lib/5105/3):

Do you have any thoughts on how to prevent this happening in the future?


Successfully aliased the URL <https://blogbukhalocom-d1vgsmuv1.now.sh> to the following aliases:

* https://blog.bukhalo.com
* https://blogbukhalocom.bukhalo.now.sh
* https://blogbukhalocom-git-master.bukhalo.now.sh


I think an easier code path would be that the consumer is for a `StandardGradlePlugin`. That way it is clear that you're trying to customize a standard plugin (as applied plugin don't need that). If this changes in the future, we can change the signature and figure things out.


@MinhasRizwan You should break this down into smaller functions that only do one thing i.e. Validate Special character, Validate Number


this method must be grouped with the `register` so that it's clearer they share a common goal.


Successfully aliased the URL <https://nuxt-typescript-vuetify-otx8359x3.now.sh> to the following aliases:

* https://nuxt-typescript-vuetify.justhannes.now.sh
* https://nuxt-typescript-vuetify-git-master.justhannes.now.sh


@MinhasRizwan You were supposed to add the fragment programmatically not through xml


We should extract the logic in a private method that both this one and apply share. Something like

```
private GradlePlugin register(String id, Function<String,GradlePlugin> pluginId) {
  return this.plugins.computeIfAbsent(id, pluginId);
}
```


I don't understand why this while is no longer needed


Small details but I'd like the order of methods to match the ones in `BuildItemContainer` (or we can revisit them to order them differently).


Should move to the `.maven` sub-package.


:white_check_mark: All Rules (3 / 3) Passed

      :crown: Good job! this pull request is aligned with your organization's best practices!

      :point_right: You can review your rules settings at smart policy management :point_left:

:point_right: click here to view a full list of the events :point_left:


This should return a `Stream` with consistency with the other containers.


Successfully aliased the URL <https://reactforxiangyun-jmnoa74k2.now.sh> to the following aliases:

* https://reactforxiangyun.1098693467.now.sh
* https://reactforxiangyun-git-master.1098693467.now.sh


Hi, thank you for this great Work. Now I am finally able to connect all my Cameras.
I know ist been a while singe posted…

Im currently using the Smartthings Classic as well as the nee app.
With the classic app everythings seems to work well gut with the nee app, the cameras ar only shown as switch devices. Is there maybe a solution for this?

Many thanks in advacnce.


We should get rid of that to avoid having to deal with this and just use the other register method that takes a callback to set the version.


Gentoo with IOMMU, SR-IOV, dmar, enabled, latest 5.2.7 kernel
nvme: samsung 970 pro.


Successfully aliased the URL <https://blogbukhalocom-o65ffhq6n.now.sh> to the following aliases:

* https://blog.bukhalo.com
* https://blogbukhalocom.bukhalo.now.sh
* https://blogbukhalocom-git-master.bukhalo.now.sh


Eclipse commit


I'd called that `plugins` for consistency with other containers (see `Build`).


@eolivelli
I would open a PR. That's better view for everyone.


[SamSaffron posted](https://review.discourse.org/t/fix-remove-dependency-on-present-in-distributed-mutex-lib/5105/4):

We could make a gem for this, it may be a bit overkill


This should be renamed to `plugins()`


When writing Ruby, it's always preferable to use descriptive names, even if it's longer. There is very little (if any) advantage in writing short, terse variable or method names. When working with many team members, it's really helpful to take some time to think about how to name your variables and methods. This _sentence_ can be rewritten to something like this:

```ruby
seats_available = old_department.seats_available_in_section(section)
```


Due to the nature of `StandardGradlePlugin` (they don't offer a way to set the apply flag), it should be a filter based on instances. The cast is a bit annoying but hopefully it should be the only place where we have to do that.


feature


This could use a method reference.