profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/itowlson/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

deislabs/yo-wasm 28

Yeoman generator for Rust projects intended to build to WASM in OCI registries

deislabs/duffle-vscode 16

VS Code extension for Duffle, the CNAB installer

deislabs/kind-vscode 14

Integrating the Kind local Kubernetes cluster into Visual Studio Code

deislabs/duffle-bag 10

GUI tooling for CNAB bundles

deislabs/gatekeeper-vscode 9

Rapidly develop and test Gatekeeper policies in Visual Studio Code

deislabs/kubernetes-opa-vscode 9

A VS Code extension for working with Open Policy Agent in Kubernetes

deislabs/microk8s-vscode 7

Integrating the Microk8s local Kubernetes cluster into Visual Studio Code

deislabs/hippo-cli 6

The Hippo CLI

deislabs/krustlet-wagi-provider 6

A Krustlet Provider for WAGI modules.

issue openedbytecodealliance/wasmtime

Crash when Wasmtime invokes nondefault AssemblyScript function

I originally raised this at AssemblyScript (https://github.com/AssemblyScript/assemblyscript/issues/2099) but they appear to view it as an issue with Wasm runtimes; they have raised a Wasmer bug but my use case is Wasmtime.


Consider the following AssemblyScript program:

import "wasi";

export function foo(): void {
  console.log("foo");
  console.log(Math.random().toString());
}

console.log("start");

Compile this using

asc test.ts --explicitStart --debug

Now run wasmtime run --invoke foo ./build/untouched.wasm

It crashes with:

Caused by:
    0: failed to invoke `foo`
    1: exit with invalid exit status outside of [0..126)
       wasm backtrace:
           0:  0x5a9 - <unknown>!~lib/wasi/index/abort
           1: 0x2c4a - <unknown>!~lib/rt/itcms/visitRoots
           2: 0x2e73 - <unknown>!~lib/rt/itcms/step
           3: 0x2fb2 - <unknown>!~lib/rt/itcms/interrupt
           4: 0x31ea - <unknown>!~lib/rt/itcms/__new
           5: 0x3441 - <unknown>!~lib/util/number/dtoa
           6: 0x322c - <unknown>!~lib/number/F64#toString
           7: 0x337b - <unknown>!assembly/index/foo```

The crash occurs within the AssemblyScript garbage collector while trying to allocate a string.

I believe the reason AssemblyScript considers this a runtime bug is that they set up the GC in the implicit _start function. Calling wasmtime run --invoke foo bypasses _start and therefore the GC is not set up when it needs to do the allocation.

This also occurs when invoking the function via the Wasmtime Rust crate hosted in my own program (https://github.com/deislabs/wagi/issues/128).

There are additional details and discussion in the original AssemblyScript issue https://github.com/AssemblyScript/assemblyscript/issues/2099.

created time in 6 hours

push eventAzure/vscode-kubernetes-tools

Ronan Flynn-Curran

commit sha 1b51769accfa646562817aa8227171f0c0db4197

Document the Hugo microsite (#987) Signed-off-by: flynnduism <dev@ronan.design>

view details

push time in 7 hours

PR merged Azure/vscode-kubernetes-tools

uodate README to document the hugo microsite

This PR makes a small edit to the readme, to point to a new sub-readme that explains the little website for this repo: https://azure.github.io/vscode-kubernetes-tools/

That site is generated from the files inside the site folder. I've added a README there explaining how Hugo, Gulp and Github Pages generate the site.

Signed-off-by: flynnduism dev@ronan.design

+19 -0

0 comment

2 changed files

flynnduism

pr closed time in 7 hours

PullRequestReviewEvent
PullRequestReviewEvent

push eventitowlson/vscode-kubernetes-tools

itowlson

commit sha 922642d8e85b388aaea787bdeff3bdea466185d5

Publish 1.3.4 (#986)

view details

push time in 8 hours

push eventAzure/vscode-kubernetes-tools

itowlson

commit sha 922642d8e85b388aaea787bdeff3bdea466185d5

Publish 1.3.4 (#986)

view details

push time in 10 hours

PR merged Azure/vscode-kubernetes-tools

Reviewers
Publish 1.3.4
+16 -1

0 comment

2 changed files

itowlson

pr closed time in 10 hours

PR opened Azure/vscode-kubernetes-tools

Reviewers
Publish 1.3.4
+16 -1

0 comment

2 changed files

pr created time in 10 hours

create barnchitowlson/vscode-kubernetes-tools

branch : publish-1.3.4

created branch time in 10 hours

Pull request review commentgetporter/vscode-extension

GitHub actions to build and publish

+## How to Release++To make a new release and publish it to the marketplace you have to follow the following steps.++1. Create a branch `publish-x.y.z`+2. Update `package.json` with the new version +3. Add a section to `CHANGELOG.md` with the header `## [x.y.z]` (N.B: make sure to write the new version in square brackets as the `changelog-reader` action only works if the `CHANGELOG.md` file follows the [Keep a Changelog standard](https://github.com/olivierlacan/keep-a-changelog))+4. Create a new PR, get approval and merge+5. Run the `Build & Publish` workflow manually from the GH Actions tab++### Build & Publish ++The `Build & Publish` workflow allows to create a new release, package it in a VSIX file and publish to the VSCode marketplace with a single click.++The only requirement needed to run the workflow is to have a secret named `VS_MARKETPLACE_TOKEN` containing the Personal Access Token of the publisher. You can find more infos about how to create a publisher/token in the [official documentation](https://code.visualstudio.com/api/working-with-extensions/publishing-extension#create-a-publisher)

Yes, you should generate a token. You should now have publish permissions on the ms-kubernetes-tools publisher which this extension is part of, so your user account should work. I'm happy to go through this with you if that would be helpful, though the docs are pretty good.

If you want to put it under a different publisher (because that publisher has a Microsoft connection and that has Implications), you'll need to create that publisher in Marketplace and update the publisher field in package.json. From the point of view of VS Code this will result in an entirely different extension. Existing users will not be auto upgraded and will need to re-acquire; and the old and new versions will fight if installed side by side. There are tricks we can do to make this reasonably smooth but they are fiddly. If you want to do this, better to do it sooner rather than later; happy to get on a call about it and work through it (I'm thinking we may need to do this for the k8s extension too so it would be good for me to think about it!).

itowlson

comment created time in 12 hours

PullRequestReviewEvent

push eventitowlson/ivanos

Ivan Towlson

commit sha d41414c2d5aa9762019cdf3899814a756ef80b43

Trying to understand why format blows up

view details

push time in 4 days

create barnchitowlson/ivanos

branch : understand-format-woes

created branch time in 4 days

MemberEvent
MemberEvent

push eventitowlson/porter-vscode

Ivan Towlson

commit sha 8309dfd9767d9d4e6f67384bc5d374dbf864147f

GitHub actions to build and publish Signed-off-by: Ivan Towlson <itowlson@microsoft.com>

view details

push time in 4 days

PR opened getporter/vscode-extension

Reviewers
GitHub actions to build and publish

Provides GitHub actions to build and publish the extension.

  • The build.yml action builds the extension on every PR and merge to main. It compiles the TypeScript, packages a VSIX, and archives the VSIX as a build artifact. This means that 1. we check that packaging works (will be doubly important if/when we webpack it) and 2. there are binaries available if we want a user to test a change.

  • The publish.yml does NOT run automatically; it must be manually triggered from the Actions tab. It does the build and package, creates a release and uploads it to the marketplace. This will require a marketplace token; there are also some new changelog conventions which it requires us to observe. These are described in docs/maintenance/README.md (for an example of them in action, see the Kubernetes extension, from which these were shamelessly copied).

+125 -0

0 comment

4 changed files

pr created time in 4 days

create barnchitowlson/porter-vscode

branch : action-we-demand-action

created branch time in 4 days

push eventitowlson/porter-vscode

itowlson

commit sha a5ed70f038589808646e946fb7e91b2a8bbd53ab

Installation browser (#45)

view details

push time in 4 days

push eventitowlson/vscode-aks-tools

Tatsinnit

commit sha 22b1606344537197b50fcd2672f5110ab237069e

Remove unused package and update handlebars (#85)

view details

itowlson

commit sha 8df0c93003a024e90101a91619a60d7afdd49775

GitHub action to release and publish (#86)

view details

push time in 4 days

push eventAzure/vscode-aks-tools

itowlson

commit sha 8df0c93003a024e90101a91619a60d7afdd49775

GitHub action to release and publish (#86)

view details

push time in 4 days

push eventAzure/vscode-aks-tools

Tatsinnit

commit sha 22b1606344537197b50fcd2672f5110ab237069e

Remove unused package and update handlebars (#85)

view details

push time in 4 days

PR merged Azure/vscode-aks-tools

Remove unused package and update handlebars. dependencies

This PR is to cater most of direct dependency alerts. Rest of the alerts are dependent and not directly impacting.

  • Removed jszip and axios which were no longer in use, also updated the handlebars to ">=4.7.7" (https://github.com/advisories/GHSA-f2jv-r9rf-7988) .

Thanks, 🙏cc: @itowlson

+9 -156

2 comments

2 changed files

Tatsinnit

pr closed time in 4 days

pull request commentAzure/vscode-aks-tools

Remove unused package and update handlebars.

Confirmed vsce package succeeds

Tatsinnit

comment created time in 4 days

PR opened Azure/vscode-aks-tools

Reviewers
GitHub action to release and publish
+85 -0

0 comment

3 changed files

pr created time in 4 days

create barnchitowlson/vscode-aks-tools

branch : publish-action

created branch time in 4 days

push eventitowlson/vscode-aks-tools

Tatsinnit

commit sha c3611e220d2847089f29b52ba5f318a20bfdd66a

Fix packaging failure (#84)

view details

push time in 4 days

push eventitowlson/vscode-kubernetes-tools

pantosha

commit sha 78c4249f625698d0019071bcda4bb1c80f396351

Configure path to vsdbg (#967)

view details

Luca Stocchi

commit sha 32179d7095fb467698c0819bdb973f0f61b2af32

Fix issue when displaying many large secrets on tree (#971) Signed-off-by: Luca Stocchi <lstocchi@redhat.com>

view details

Florian Schumann

commit sha f6759b7acb43225586080ddfbb92bbf1414e3ad3

Start Helm values completion whenever .Values. occurs (#984)

view details

Yevhen Vydolob

commit sha 506537289499d728cfa525e8b4d1adde21aca0da

Suggest extensions based on installed CRDs (#780)

view details

push time in 4 days