Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

style: include spaces around all variables #573

Open
wants to merge 2 commits into
base: development
Choose a base branch
from

Conversation

gclough
Copy link
Collaborator

@gclough gclough commented Mar 27, 2024

No description provided.

tasks/users_privileges.yml Outdated Show resolved Hide resolved
@gclough
Copy link
Collaborator Author

gclough commented Mar 27, 2024

@MrMegaNova , the pipeline seems to be breaking on debian12. I think it's unrelated to this PR, so any idea why?

TASK [Gathering Facts] *********************************************************
  fatal: [postgresql-13]: FAILED! => {"msg": "failed to transfer file /home/runner/.ansible/tmp/ansible-local-311737jo_bd0/tmpu3wbecvw to /tmp/.ansible-runner/tmp/ansible-tmp-171[154](https://github.com/ANXS/postgresql/actions/runs/8452288398/job/23152495560?pr=573#step:5:160)5116.2229574-3188-270162615485133/AnsiballZ_setup.py:\n\ndd: failed to open '/tmp/.ansible-runner/tmp/ansible-tmp-1711545116.2229574-3188-270162615485133/AnsiballZ_setup.py': No such file or directory\n"}
  fatal: [postgresql-16]: FAILED! => {"msg": "failed to transfer file /home/runner/.ansible/tmp/ansible-local-311737jo_bd0/tmp3hlnu5qv to /tmp/.ansible-runner/tmp/ansible-tmp-1711545116.2686648-3210-188811211754346/AnsiballZ_setup.py:\n\ndd: failed to open '/tmp/.ansible-runner/tmp/ansible-tmp-1711545116.2686648-3210-188811211754346/AnsiballZ_setup.py': No such file or directory\n"}
  fatal: [postgresql-14]: FAILED! => {"msg": "failed to transfer file /home/runner/.ansible/tmp/ansible-local-311737jo_bd0/tmpltqenivg to /tmp/.ansible-runner/tmp/ansible-tmp-1711545116.2045798-3189-118414509770377/AnsiballZ_setup.py:\n\ndd: failed to open '/tmp/.ansible-runner/tmp/ansible-tmp-1711545116.2045798-3189-118414509770377/AnsiballZ_setup.py': No such file or directory\n"}
  fatal: [postgresql-12]: FAILED! => {"msg": "failed to transfer file /home/runner/.ansible/tmp/ansible-local-311737jo_bd0/tmpxrsi7fah to /tmp/.ansible-runner/tmp/ansible-tmp-1711545116.2014093-3185-190524406011025/AnsiballZ_setup.py:\n\ndd: failed to open '/tmp/.ansible-runner/tmp/ansible-tmp-1711545116.2014093-3185-190524406011025/AnsiballZ_setup.py': No such file or directory\n"}
  fatal: [postgresql-15]: FAILED! => {"msg": "failed to transfer file /home/runner/.ansible/tmp/ansible-local-311737jo_bd0/tmpqu9425dq to /tmp/.ansible-runner/tmp/ansible-tmp-1711545116.2519045-3193-102489124427116/AnsiballZ_setup.py:\n\ndd: failed to open '/tmp/.ansible-runner/tmp/ansible-tmp-1711545116.2519045-3193-102489124427116/AnsiballZ_setup.py': No such file or directory\n"}

@MrMegaNova
Copy link
Collaborator

I have no idea, I've just retry the failed check, we'll see
I have no time to debug today, I will take a look tomorrow or next week

Please do not push or request direct push to master anymore, fist create a PR to development then when development branch are stable merge into master

@gclough
Copy link
Collaborator Author

gclough commented Mar 27, 2024

¯\_(ツ)_/¯, looks like it's running now.

OK, sounds good. Let me find the name of the dev branch and I'll re-jig this PR. It's only a cleanup, so nothing urgent.

@gclough gclough changed the base branch from master to development March 27, 2024 13:25
@MrMegaNova
Copy link
Collaborator

Thanks for your work

@gclough
Copy link
Collaborator Author

gclough commented Mar 27, 2024

Glad to help out @MrMegaNova, as I've been in your shoes... years ago when it was just me maintaining it. :-(

Also, can we change from master -> main at some point?

@MrMegaNova
Copy link
Collaborator

Glad to help out @MrMegaNova, as I've been in your shoes... years ago when it was just me maintaining it. :-(

Also, can we change from master -> main at some point?

Happy to see you back on this project, hoping our latest updates will bring back some maintainers on this project
Great idea, maybe next week because it require some changes to rename the master branch into main. You can open an issue about this to keep it in mind.

Copy link

This pr has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

@github-actions github-actions bot added the stale label Jun 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants