Closed intonet closed 5 years ago
Hi @intonet i test it with atom 1.32, mac osx 10.14 and last ansible build on single file and it works.
Can you tell me your project directory structure and the settings of ansible-vault package?
Thanks
Hi I made a video. https://youtu.be/IRFH8f73pDQ https://youtu.be/IRFH8f73pDQ Package was reinstalled but nothing change. Thanks
On 19 Nov 2018, at 16:31, sydro notifications@github.com wrote:
Hi, i test it with atom 1.32, mac osx 10.14 and last ansible build on single file and it works.
Can you tell me your project directory structure and the settings of ansible-vault package?
Thanks
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/sydro/atom-ansible-vault/issues/37#issuecomment-439932937, or mute the thread https://github.com/notifications/unsubscribe-auth/AiS9UrD5U8AXhTCj5zjuUfDCIvOtNzQ0ks5uws60gaJpZM4Yma-d.
Hi, with atom 1.32.2 without other packages, mac osx 10.14 (on x64) and ansible 2.6.4, i can't reproduce the bug. Can you tell me the list of other (Non-Core) packages installed in atom ? and how did you install ansible (pip/brew)?
Thanks for your help
Hi I have git-time-machine 2.1.0 Platformo-ide-terminal 2.8.4 Split-diff 1.5.3
I used pip to install ansible. Regards.
On 21 Nov 2018, at 11:10, sydro notifications@github.com wrote:
Hi, with atom 1.32.2 without other packages, mac osx 10.14 (on x86) and ansible 2.6.4, i can't reproduce the bug. Can you tell me the list of other packages installed in atom ? and how did you install ansible (pip/brew)?
Thanks for your help
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/sydro/atom-ansible-vault/issues/37#issuecomment-440607951, or mute the thread https://github.com/notifications/unsubscribe-auth/AiS9UlcmqimzqugrWChUDEMtlLQgFbVfks5uxSaEgaJpZM4Yma-d.
Hi, i added a few changes on the package. Can you try now and tell me if it's ok?
Thanks
Hi Unfortunately still the same.
On 21 Nov 2018, at 12:41, sydro notifications@github.com wrote:
Hi, i added a few changes on the package. Can you try now and tell me if it's ok?
Thanks
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/sydro/atom-ansible-vault/issues/37#issuecomment-440634409, or mute the thread https://github.com/notifications/unsubscribe-auth/AiS9UmzoBR4boyZPrPUyNNfQ_WR07s7Pks5uxTwEgaJpZM4Yma-d.
Please, can you try again ? sorry for the trouble :(
No problem And this time it is work again. Thanks a lot man!
On 21 Nov 2018, at 14:20, sydro notifications@github.com wrote:
Please, can you try again ? sorry for the trouble :(
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/sydro/atom-ansible-vault/issues/37#issuecomment-440659690, or mute the thread https://github.com/notifications/unsubscribe-auth/AiS9UgT8fC_En9VBwrjsbEhfl8ey-7iFks5uxVM0gaJpZM4Yma-d.
Wonderful! :+1: Thanks you!!!
Describe the bug After decryption files are empty
To Reproduce Steps to reproduce the behavior: 1.select file
Expected behavior See content of file.
Desktop (please complete the following information):
Stop working e few days ago. Uninstall and install add-on again not fix problem. Decryption using ansible-vault work ok.