Tom Pollard
Tom Pollard
I'm not sure if it's just me, but a recent update to vscode (I'm on 1.33 now) has reverted itself back to it's stock icon I'm on Gnome 3.28, with...
Currently azure & appveyor are the supported `win` providers. Adding/Assessing Travis support could be beneficial for users allowing for linux/osx/win to be covered by one travis endpoint https://docs.travis-ci.com/user/reference/windows/
The windows azure pipeline template uses the conda-environment task: https://github.com/conda-forge/conda-smithy/blob/master/conda_smithy/templates/azure-pipelines-win.yml.tmpl#L43 However, the documentation & task source claims it's deprecated and recommends against using it: - https://docs.microsoft.com/en-gb/azure/devops/pipelines/tasks/package/conda-environment?view=azure-devops - https://github.com/microsoft/azure-pipelines-tasks/blob/master/Tasks/CondaEnvironmentV1/task.json#L5
The blob library gocloud.dev/blob has various ['drivers'](https://pkg.go.dev/gocloud.dev/blob?utm_source=gopls#section-directories) (for instance the gcsblob package) which makes it relatively easy to interact with different 'blobstore' type backends via a common api. Utilising this...
This could also be versioned and validated(as is the case for [`package-feeds`](https://github.com/ossf/package-feeds/blob/main/package.schema.json) 'package' output) providing a reference for potential downstream consumers of the analysis results.
The pubsub library gocloud.dev/pubsub has various ['drivers'](https://pkg.go.dev/gocloud.dev/pubsub?utm_source=godoc#section-directories) (for instance the gcppubsub package) which makes it relatively easy to interact with different 'pubsub' type systems via a common api. [package-feeds](https://github.com/ossf/package-feeds/blob/main/publisher/kafkapubsub/kafkapubsub.go) has...
The `package-feeds` project now validates & versions its package data output against a json schema https://github.com/ossf/package-feeds/blob/main/package.schema.json The `SchemaVer` should follow semantic versioning, as such any minor 1.* release should guarantee...
Modules can be in installed (`go install package@version`) which will also build the given module, in a `golang` container
Targeting a rust:minimal container for cargo builds of the given package tarballs for example
Currently errors which occur during polling or publishing at a package level are logged, resulting in a generic `pollErr/pubErr`, with the given packages data being lost whilst the remaining packages...