Hasho

These guys (they are a company) have a pen testing approach for blockchain. Apparently is it difficult to make transactions anonymous-in-source within a blockchain as any one transaction reveals a marker that allows a hacker to go fishing within the blockchain for comparable markers. In a Byzantine Agreement (in this space) there is a second round of acceptance, based on proof of work (POW), proof of stake, proof of trust, or proof of space. The blockchain security stuff comes with new challenges in short.

Add an environment to deploy to at Azure DevOps.

Go to the releases as described here. Then edit a release. You should see something like what you see in the image below. The items in the connected line below are part of an automatic deployment upon a successful merge to the master code branch while the disconnected item must be manually deployed to from within either Octopus, assuming you are using Octopus, or the shown UI. The "Clone" option here allows you to copy an environment. Across the top where is reads Pipeline, Tasks, Variables, Retention, Options, and History you may pick Tasks and then pick a particular task to set the "Deploy To Environments" setting to, yes, an environment to deploy to and you may also get to the Tasks by clicking the blue links shown here:

The icon of a person with a lightning bolt raining down on him opens a pane where you may pick between options for After release, After stage, and Manual only to determine if a push to this environment is automatically kicked off by something else somewhere in a chain as shown or must be done manually in isolation. (Maybe we should only push dev to test infrequently when requested to keep test from being polluted by dev's ongoing wackiness and midstream steps in between demonstratable stories in complete.) Clicking in the greater rectangle opens a pane where you may name your step.

How may I tell what user is running a website in Azure DevOps and Octopus?

It is probably kept in Octopus as an environment variable in Variables or as a part of a process step in Process.

If you hand a C# value type into a method signature where it gets altered and then later use the value type back in the blob of code that called the method signature, the value type will be unpolluted by the isolated changes.

This trick for reference types does NOT apply for value types. You are going to have to use ref or out at a method signature if you want the warping within to make its way back out.

Redux is a simplified version of Flux.

This touches on Flux some. Redux wouldn't really have Views in the React.js sense, not in an Angular application. I'm sure there are other differences beyond that. The modern JS frameworks are all reactionary to the memory leaks in the two-way data-binding in version 1 of Angular, and the thing to understand is that data flows in one direction through a set of common contortions in a consistent order. For example:

• https://www.tiktok.com/share/video/6674808864736546053?u_code=d1e3j0d078fbl5&preview_pb=0&language=en×tamp=1555378373&utm_campaign=client_share&app=musically&utm_medium=ios&tt_from=copy&utm_source=copy
• https://www.tiktok.com/share/video/6674808243153407237?u_code=d1e3j0d078fbl5&preview_pb=0&language=en×tamp=1555459643&utm_campaign=client_share&app=musically&utm_medium=ios&tt_from=copy&utm_source=copy
• https://www.tiktok.com/share/video/6674764978358111493?u_code=d1e3j0d078fbl5&preview_pb=0&language=en×tamp=1555870290&utm_campaign=client_share&app=musically&utm_medium=ios&tt_from=copy&utm_source=copy

Set a random attribute on an ElementRef in Angular 7 as you might elsewhere in JavaScript.

This is friendly to the TypeScript compiler:

this.iFrame.nativeElement.setAttribute("src", "http://www.example.com");

Use the draggable API in an Angular 6 application.

This touches on modern draggability some. I made use of it like so:

<div draggable="true" (dragstart)="startDrag($event)" (dragend)="endDrag($event)">

 
 

The events will have hanging off of them screenX, screenY, clientX, and clientY and properties.