container

Just sharing 😄

Install tools:

brew install geekbench
brew install w3m

Run benchmark, must have internet for Geekbench 5 tryout mode:

/Applications/Geekbench\ 5.app/Contents/Resources/geekbench5

Use w3m get result in terminal:

w3m -dump https://browser.geekbench.com/v5/cpu/5992961

One line can be:

w3m -dump $(/Applications/Geekbench\ 5.app/Conten

What would you like to be added/modified:

To improve project stability, we need more tests to cover corner cases.
And the code coverage is around 50% currently, we need to add more tests to improve it.

To improve case coverage, we may need a list of cases to track the work.
For code coverage, simply check bef

Describe the feature

Cur

Describe the bug
Multipass sometimes logs unrelated messages to stdout. When parsing stdout information, this can lead to undesirable behavior.

To Reproduce
Install multipass 1.5 for Windows.

Run multipass version

How, and what happened?

>multipass version 2>stderr.txt
multipass  1.5.0+win
multipassd 1.5.0+win

#####################################################

In google/ko#303 I added a big warning about GOROOT mismatches between ko and go. I think this is necessary given how ko works, but we should be able to remove that warning if we refactor the go builder a bit.

Historically, ko would attempt to Import every single string in a document to determine whether or not it sh

Is your feature request related to a problem?
"DevSpace should use the current docker behavior for dockerignore:
Dockerfile + .dockerignore
Dockerfile + Dockerfile.dockerignore
Dockerfile.frontend + Dockerfile.frontend.dockerignore
"

Which solution do you suggest?
Delegating the dockerignore file search to Docker if possible, otherwise copying the behavior as best as possible

Version of Singularity:

3.0.3

Expected behavior

Some progress or update information during the creation of the SIF file.

Actual behavior

During "Creating SIF file..." step, the console does not produce any visible output for the user - but does create the resulting file eventually.

Steps to reproduce behavior

I was executing a few “larger” builds through the bui

https://material.io/resources/color/#!/?view.left=1&view.right=0 readability needs to be possible almost universally ideally. This means avoiding all caps strings in titles as screen readers read every letter and other nonsense like this however the first and foremost concern is just simply that we ship with a default that is visible for our sighted users who may have issues with color blindness

Docker enables folks to use custom certs for their registries via this directory (and possibly environment variables). We should figure out how tools can support this, perhaps through support directly in the library, or perhaps through documentation on how to properly set up the http.RoundTripper passed into remote.Foo calls.

crane and ko would be good examples for how we add support f