autoconf
automake
build-essential
gcc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
unsafe static byte[] DoublesToBytes(double[] value) | |
{ | |
var bytes = new byte[8*value.Length]; | |
fixed (byte* b = bytes) | |
{ | |
for (int i = 0; i < value.Length; i++) | |
{ | |
var v = value[i]; | |
*((int*)(b + 8*i)) = *(int*)&v; | |
*((int*)(b + 8*i+4)) = *(((int*)&v) + 1); |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
namespace Downloader | |
{ | |
using System; | |
using System.IO; | |
using System.IO.Compression; | |
using System.Net.Http.Json; | |
using System.Text; | |
using System.Text.Json.Nodes; | |
using Azure.Core; | |
using Azure.Identity; // <PackageReference Include="Azure.Identity" Version="1.9.0" /> |
- Federated credentials / workload identity federation allows your CI/CD pipelines in GitHub and GitLab to access your Azure subscription without any secrets stored in the pipeline config.
- GitHub's
azure/login@1
task handles this transparently, but I also explain how it works under the hood. GitLab supplies the necessary token directly to your pipeline run. - Both GitHub and GitLab are easy to setup and federate securely with your Azure subscription.
- BitBucket can't be setup that way, because tokens issued by BitBucket don't have a predicable subject identifier.
NewerOlder