Jeffrey Vandenborne

Facing the same issue with v1.0.0-rc.3 My binary is installed using scoop

This sums it up well: https://github.com/binref/refinery/issues/5 I also wrote a snippet that writes the uint64 binary representation of the numbers 0 to 9 to a file and to stdout to...

I'm having this issue as well. Use case is creating a publicly reachable machine with only an IPv6 IP. There are 2 solutions: - adding an IPv4 public IP -...

==> Vaprobash: Cloning VMware VM: 'ubuntu/trusty64'. This can take some time... ==> Vaprobash: Verifying vmnet devices are healthy... Can confirm this!

Apologies, my bad. I seem to have already cloned a trusty64 box. I'm testing to see if everything works and i'll get back to you

This machine should work

Yep, same problem on my cluster: ``` WARN source{component_kind="source" component_id=aws_cloudtrail component_type=aws_s3}:lazy_load_identity: aws_config::meta::credentials::chain: provider failed to provide credentials provider=EcsContainer error=the credentials provider was not properly configured: invalid full URI for ECS...

@jszwedko Yep, this is the container I'm running: ``` Image: timberio/vector:0.41.1-alpine Image ID: docker.io/timberio/vector@sha256:501e5403e19238c9073c116fb3cbb750a9201d0271b09dae88f044534803c670 ``` also, not unimportant to mention, this error is basically occurring in a loop it seems...

 I'd really love to have this merged in. This happens when I copy "ls -l"

Restarting the pod works for me as well.