shimataro

Results 23 comments of shimataro

Hello! I think Granite version must be >=5.3.0. [Granite v5.2](https://github.com/elementary/granite/tree/5.2.0/lib/Widgets) does not have `AccelLabel`, and [v5.3](https://github.com/elementary/granite/tree/5.3.0/lib/Widgets) has it. Therefore, `granite>=5.2` in README should be `granite>=5.3`.

> It may be fixed by changing the SSH target to one created by Docker I think it cannot be tested on Windows/macOS if I use Docker service container... :thinking:

@tats-u Do you mean using Docker directly, not as [service container](https://docs.github.com/en/actions/guides/about-service-containers)? It might work on Windows, but won't on macOS. > macOS is similar to Linux, and most bugs in...

Hi @spaquet Hmm... :thinking: `KNOWN_HOST` seems to be no problem. Could you paste entire workflow file and error log?

:thinking: Let me ask you some questions. 1. Are you sure that secret name is `KNOWN_HOSTS`? (in , you wrote "and KNOWN_HOST value is". is this just a typo?) 1....

@retrorocket 報告ありがとうございます!マジで謎ですね。。。 --- @spaquet Thank you for the details. It seems your environment-specific problem, because: - SSH works successfully - @retrorocket tried `git clone` from Bitbucket but no errors occurred...

@spaquet I've created [test workflow](https://github.com/shimataro/test-clone-bitbucket-in-actions/blob/master/.github/workflows/ci.yml) and [test bitbucket repository](https://bitbucket.org/shimataro999/test-repo), and [it works fine](https://github.com/shimataro/test-clone-bitbucket-in-actions/runs/805348478?check_suite_focus=true). Could you test it in the following steps: 1. fork [this repo](https://github.com/shimataro/test-clone-bitbucket-in-actions) 1. add your private key...

Hi, @jacktuck Thank you for your detailed expression! It seems to be better to append LF to `known_hosts`. I will address it immediately!

@jacktuck If not prepend, I think it will cause same error when `known_hosts` already exists(created by previous step) and does not end with LF.

@ramonheras Very sorry for late response. Is your key format OpenSSH? If yes, it might be same cause as #147. Please retry after converting to PEM format as a temporary...