Not any file named q
See original GitHub issueHi
using q in an ansible module as follows:
def exec_module(self):
changed = False
result = dict()
state = self.want.state
import q
q.q(state)
There is no file q created anywhere in the file system…
[root@ansible-tower-32 library]# find / -type f -name q -print | wc -l
0
I reckon this is a problem between the chair and the keyboard… any tip would be more than welcome
Thanks!
Ulises
Issue Analytics
- State:
- Created 5 years ago
- Comments:5
Top Results From Across the Web
dir | Microsoft Learn
Reference article for the dir command, which displays a list of a directory's files and subdirectories.
Read more >Can not delete file named :q · Issue #984 - GitHub
Version info OS: macOS 10.15.7 Build: 2032 or 2038 Description If I have an untracked file named :q in my repo and I...
Read more >How to delete files/subfolders in a specific directory at the ...
rmdir is my all time favorite command for the job. It works for deleting huge files and folders with subfolders. A backup is...
Read more >How to Delete Undeletable Files & Folders in Windows 10 or 8 ...
In this video, I will show you how to delete undeletable files on Windows 10, 8 or 7 using command prompt. This tutorial...
Read more >How can I delete all files/subfolders in a given folder via the ...
You can do this using del and the /S flag (to tell it to remove all files from all subdirectories): del /S C:\Path\to\directory\*....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I have run into the same problem while trying to debug build backends and I suspect we have the same problem: q respects
tempfile.gettmpdir()
which for instance in the project I’m working on looks like this:It would be nice if I could overwrite that with something like
Q_FORCE_FILE=/tmp/q
.@alonsocamaro did you get this to work in the end? I’m trying to use q to trace an ansible module, and so far it’s just adding to the confusion.
Adding @q decorator to all the module’s internal methods seems to result in /tmp/q just listing them all. Using
@q.t
gives the expected parameters etc in the file, but only for some calls (I can see from behaviour that some of the trace functions are being called but not logged).I really want this to work - debugging ansible is horrible!
(so, for the
@q
case, I get something like this, which is just a list of all the functions in the module - there is no code path that will actually run them in this order)