Welcome!

Hello, وهراني, and welcome to Wikipedia! Thank you for your contributions. I hope you like the place and decide to stay. Here are some pages that you might find helpful:

I hope you enjoy editing here and being a Wikipedian! Please sign your messages on discussion pages using four tildes (~~~~); this will automatically insert your username and the date. If you need help, check out Wikipedia:Questions, ask me on my talk page, or ask your question on this page and then place {{helpme}} before the question. Again, welcome! --Meno25 (talk) 02:43, 12 December 2010 (UTC)Reply

wahrani tool temporary files

edit

Hi وهراني,

While debugging something else on Toolforge, I happened to notice that the wahrani Toolforge tool seems to be generating a very large number of temporary files in /tmp (30k+ since September 18). Are these necessary? Could the task be implemented a different way, or the files purged more quickly?

It's no big deal or anything, but having a huge number of files here can sometimes be slightly annoying when trying to find something else in /tmp, so I thought I'd just give you a headsup about it. Please do not feel obligated to do anything in particular about this, nor within any particular timeframe: I just wanted to mention it so you are aware.

PS. Apologies for writing on enWP (I believe arWP is your home wiki?) and in English instead of پښتو. My skills in non-Western languages are sadly deficient so this was the best I could do. --Xover (talk) 14:56, 7 November 2020 (UTC)Reply

Hi @Xover:, I run my own scripts on toolforge but I don't create any tmp file. And it's the same with the framework that I use (Wikipedia:Peachy). Can you help me to do some investigations ? --وهراني (talk) 15:09, 7 November 2020 (UTC)Reply
I'd certainly be happy to help any way I can. What do you need? --Xover (talk) 16:06, 7 November 2020 (UTC)Reply
Ah. I took a quick look at Peachy, and it looks like the files might be HTTP cookie stores. At HTTP.php line 101–102 it creates a cookie file in the system temporary files directory with a filename derived from the library name, the time of day, and a random value. That is, it looks like Peachy is, by design, creating a new cookie file for every time its HTTP object is instantiated. Since the unlink() call in the destructor is commented out, these files will never be deleted.
If you use a local copy of Peachy you could try uncommenting that line, but since I don't know why it's been commented out I can't guarantee that that won't have undesirable side effects (it looks safe, but…).
Maybe Cyberpower678 has an idea? --Xover (talk) 16:49, 7 November 2020 (UTC)Reply