Search
1000 results for “heaths”
-
Prototyping test recording for #AzureSDK for #RustLang: https://github.com/heaths/recorded-tests
Attribute sync or async tests using `#[recorded]` and can accept optional `TestContext` parameter. Full implementation should automatically set up HTTP transport to record or play back.
Thoughts? Still early.
-
After seeing that The #CodeProject is shutting after the many early years I put on that site, I wanted to archive at least a few articles that were a step in my journey. I added a custom archive collection to my #Jekyll-based site and will add some more articles as I have time: https://heaths.dev/archive/
-
Updated my #GitHubCLI extension to view information about CODEOWNERS: https://github.com/heaths/gh-codeowners
Added a new `pr` command to view all a PR's files' owners e.g., `gh code owners pr #123`
Nice to jump back into a little #golang
-
@ekis @[email protected] I often work with monorepos like the #AzureSDK for #Go. That's when git worktrees and sparse checkouts can help reduce checkout time and drive space exhaustion. Check out https://heaths.dev/tips/2022/06/18/reduce-fetch-and-checkout-times-in-git.html for some tips. I should probably update that to mention worktrees too, though that really just helps reduce cloning time and minimizes disk space.
One advantage is having different copies of dependencies in different states, though I wonder how often that's a problem.
-
Nothing like being asked to provide cross-platform support for my MSI #PowerShell cmdlets (https://github.com/heaths/psmsi) to extract the ProductCode - which is dubious since they depend on Windows-only APIs and most features would only work on Windows where MSIs can be installed - and saying you could write a simple #rustlang CLI using a crate that implements OLE docs and #WindowsInstaller's proprietary compression algorithm, only to realize you already did it a long time ago: https://github.com/heaths/msigetprop-rs
-
Nothing like being asked to provide cross-platform support for my MSI #PowerShell cmdlets (https://github.com/heaths/psmsi) to extract the ProductCode - which is dubious since they depend on Windows-only APIs and most features would only work on Windows where MSIs can be installed - and saying you could write a simple #rustlang CLI using a crate that implements OLE docs and #WindowsInstaller's proprietary compression algorithm, only to realize you already did it a long time ago: https://github.com/heaths/msigetprop-rs
-
Nothing like being asked to provide cross-platform support for my MSI #PowerShell cmdlets (https://github.com/heaths/psmsi) to extract the ProductCode - which is dubious since they depend on Windows-only APIs and most features would only work on Windows where MSIs can be installed - and saying you could write a simple #rustlang CLI using a crate that implements OLE docs and #WindowsInstaller's proprietary compression algorithm, only to realize you already did it a long time ago: https://github.com/heaths/msigetprop-rs
-
Nothing like being asked to provide cross-platform support for my MSI #PowerShell cmdlets (https://github.com/heaths/psmsi) to extract the ProductCode - which is dubious since they depend on Windows-only APIs and most features would only work on Windows where MSIs can be installed - and saying you could write a simple #rustlang CLI using a crate that implements OLE docs and #WindowsInstaller's proprietary compression algorithm, only to realize you already did it a long time ago: https://github.com/heaths/msigetprop-rs
-
Nothing like being asked to provide cross-platform support for my MSI #PowerShell cmdlets (https://github.com/heaths/psmsi) to extract the ProductCode - which is dubious since they depend on Windows-only APIs and most features would only work on Windows where MSIs can be installed - and saying you could write a simple #rustlang CLI using a crate that implements OLE docs and #WindowsInstaller's proprietary compression algorithm, only to realize you already did it a long time ago: https://github.com/heaths/msigetprop-rs
-
The #AzureDeveloperCLI `azd` has been available for a short while as a #devcontainer feature, which I recently used in https://github.com/heaths/azcrypto: https://github.com/heaths/azcrypto/pull/63/files#diff-24ad71c8613ddcf6fd23818cb3bb477a1fb6d83af4550b0bad43099813088686R8
It will not only install `azd`, but the #Azure dev extension for #VSCode. It makes deploying resources and applications a breeze.
I use it in azcrypto in lieu of the resource provisioning scripts I originally wrote for all of #AzureSDK to deploy resources uniformly. This is a publicly available (near) equivalent.
-
Now that the #golang #AzureSDK for #KeyVault has released v1.0.0, I have updated to it and released v1 of https://pkg.go.dev/github.com/heaths/a[email protected] : a cryptography client for Key Vault and #ManagedHSM that not only makes it easier to call crypto operations but tries to first cache the public key and do public key operations locally to improve performance and help mitigate throttling.
We have this in our other languages' SDKs but doesn't fit our design goals for #golang, so I wrote it as a separate module.
-
My https://github.com/heaths/azcrypto module for easy #Azure #KeyVault and #ManagedHSM crypto operations is now feature-complete and at parity with our other #AzureSDK languages' crypto libraries. It now supports crypto operations locally using a JWK.
Not likely to make it into our official azkeys SDK, but written to our same SDK guidelines.
azkeys will GA soon, and once I upgrade my dependency I plan to GA this module.
-
I've been working on a "business adjacent" project - as many of mine are - but for something that may one day be part of our #AzureSDK for #golang. Regardless of whether it gets included, I want it to feel like a first-party experience when used with our other client libraries. Given I'm part of the team, I'm coining(?) the phrase, "first-ex parte".
See https://github.com/heaths/azcrypto for a cryptography client for #Azure #KeyVault or #ManagedHSM. It's basically the same as we have in other languages.
-
Full #RSA and #ECDsa support is now available in https://github.com/heaths/azcrypto for #Azure #KeyVault. I'm consider AES support, but still researching AES in #golang. The APIs I'm familiar with in #csharp are significantly different so it may be a while, and AES is limited to #ManagedHSM anyway.
-
Since the #AzureSDK for #golang's philosophy is thin, mostly generated clients - which I don't disagree with - I built a #cryptography client atop it much like I helped drive in our other SDK languages and wrote for the #Azure #KeyVault SDK for .NET: https://github.com/heaths/azcrypto
It's very early in development right now - supporting only #ECDsa sign and verify - but is an MVP enough to get some feedback from my team or anyone else who may be interested.
-
Maintaining a #monorepo already has enough challenges. Keeping its #CODEOWNERS up to date can be difficult. I started on a new #GitHubCLI extension: `gh ext install heaths/gh-codeowners`
It does only simple linting for now but will have a fix mode for supported error types.
See https://github.com/heaths/gh-codeowners/releases/tag/v0.1.0 for more information. #GitHub
-
Maintaining a #monorepo already has enough challenges. Keeping its #CODEOWNERS up to date can be difficult. I started on a new #GitHubCLI extension: `gh ext install heaths/gh-codeowners`
It does only simple linting for now but will have a fix mode for supported error types.
See https://github.com/heaths/gh-codeowners/releases/tag/v0.1.0 for more information. #GitHub
-
Maintaining a #monorepo already has enough challenges. Keeping its #CODEOWNERS up to date can be difficult. I started on a new #GitHubCLI extension: `gh ext install heaths/gh-codeowners`
It does only simple linting for now but will have a fix mode for supported error types.
See https://github.com/heaths/gh-codeowners/releases/tag/v0.1.0 for more information. #GitHub
-
Maintaining a #monorepo already has enough challenges. Keeping its #CODEOWNERS up to date can be difficult. I started on a new #GitHubCLI extension: `gh ext install heaths/gh-codeowners`
It does only simple linting for now but will have a fix mode for supported error types.
See https://github.com/heaths/gh-codeowners/releases/tag/v0.1.0 for more information. #GitHub
-
Maintaining a #monorepo already has enough challenges. Keeping its #CODEOWNERS up to date can be difficult. I started on a new #GitHubCLI extension: `gh ext install heaths/gh-codeowners`
It does only simple linting for now but will have a fix mode for supported error types.
See https://github.com/heaths/gh-codeowners/releases/tag/v0.1.0 for more information. #GitHub
-
Just uploaded a CC BY-NC 4.0 textured 3D model and pointcloud of the Heath Street cycleway that the Canada Bay Council is planning to remove.
https://files.jakecoppinger.com/heath-st-scan/heath-st-textured-model.zip
https://files.jakecoppinger.com/heath-st-scan/Heath-Street-georeferenced_model.laz
From my blog post: https://jakecoppinger.com/2023/03/canada-bay-council-plans-to-remove-heath-st-cycleway-due-to-a-misleading-traffic-report/
#heathstreet #betterstreets #opendata #obj #laz #pointcloud #creativecommons #canadabay #canadabaycouncil #sydney #blender #cloudcompare
-
Just uploaded a CC BY-NC 4.0 textured 3D model and pointcloud of the Heath Street cycleway that the Canada Bay Council is planning to remove.
https://files.jakecoppinger.com/heath-st-scan/heath-st-textured-model.zip
https://files.jakecoppinger.com/heath-st-scan/Heath-Street-georeferenced_model.laz
From my blog post: https://jakecoppinger.com/2023/03/canada-bay-council-plans-to-remove-heath-st-cycleway-due-to-a-misleading-traffic-report/
#heathstreet #betterstreets #opendata #obj #laz #pointcloud #creativecommons #canadabay #canadabaycouncil #sydney #blender #cloudcompare
-
Just uploaded a CC BY-NC 4.0 textured 3D model and pointcloud of the Heath Street cycleway that the Canada Bay Council is planning to remove.
https://files.jakecoppinger.com/heath-st-scan/heath-st-textured-model.zip
https://files.jakecoppinger.com/heath-st-scan/Heath-Street-georeferenced_model.laz
From my blog post: https://jakecoppinger.com/2023/03/canada-bay-council-plans-to-remove-heath-st-cycleway-due-to-a-misleading-traffic-report/
#heathstreet #betterstreets #opendata #obj #laz #pointcloud #creativecommons #canadabay #canadabaycouncil #sydney #blender #cloudcompare
-
Just uploaded a CC BY-NC 4.0 textured 3D model and pointcloud of the Heath Street cycleway that the Canada Bay Council is planning to remove.
https://files.jakecoppinger.com/heath-st-scan/heath-st-textured-model.zip
https://files.jakecoppinger.com/heath-st-scan/Heath-Street-georeferenced_model.laz
From my blog post: https://jakecoppinger.com/2023/03/canada-bay-council-plans-to-remove-heath-st-cycleway-due-to-a-misleading-traffic-report/
#heathstreet #betterstreets #opendata #obj #laz #pointcloud #creativecommons #canadabay #canadabaycouncil #sydney #blender #cloudcompare
-
Nothing like writing a #GitHubCLI extension to work around a bug in the CLI for which I've had a PR out for over 9 months waiting for one person to review it (other staffers have already), but here we are: https://github.com/heaths/gh-merge-json
`gh api --paginate` may return invalid JSON, so this extension does what my PR does but within the gh ecosystem.
Just `gh ext install heaths/gh-merge-json` and pipe paginated JSON to it to merge the JSON (mainly nested arrays) and get back valid JSON.
-
@roguequery if you're interested in making this template...we'll, more template-like so people can just define a few replacement variables...check out https://github.com/heaths/gh-template. It's a #GitHubCLI extension to "fork" the template and uses #golang templates for replacement.
Like you, I also got tired of copypasta but also all manual replacements.
-
@m8urnett it gets even worse for #WindowsInstaller packages that will forever be stuck at #Windows 8.1: https://fosstodon.org/@heaths/109654404801981864 #MSI
There are also AppCompat shims that will lie about certain file versions, which are just as clunky as Windows versions, so "feature detection" based on implemention files often won't work. It's hostile behavior toward installers, pushing people back to custom, perhaps ill-behaved installers.
-
@m8urnett it gets even worse for #WindowsInstaller packages that will forever be stuck at #Windows 8.1: https://fosstodon.org/@heaths/109654404801981864 #MSI
There are also AppCompat shims that will lie about certain file versions, which are just as clunky as Windows versions, so "feature detection" based on implemention files often won't work. It's hostile behavior toward installers, pushing people back to custom, perhaps ill-behaved installers.
-
@m8urnett it gets even worse for #WindowsInstaller packages that will forever be stuck at #Windows 8.1: https://fosstodon.org/@heaths/109654404801981864 #MSI
There are also AppCompat shims that will lie about certain file versions, which are just as clunky as Windows versions, so "feature detection" based on implemention files often won't work. It's hostile behavior toward installers, pushing people back to custom, perhaps ill-behaved installers.
-
@m8urnett it gets even worse for #WindowsInstaller packages that will forever be stuck at #Windows 8.1: https://fosstodon.org/@heaths/109654404801981864 #MSI
There are also AppCompat shims that will lie about certain file versions, which are just as clunky as Windows versions, so "feature detection" based on implemention files often won't work. It's hostile behavior toward installers, pushing people back to custom, perhaps ill-behaved installers.