I don’t discount that you may have found a bug. I saw too many cases in my junior dev days where I assumed there could not possibly be one turn out to be egg on my face.

In this case, the burden is on you to submit an actionable report. There is not a single other monk standing up to say, Yes this happened to me when I’m sure it wasn’t my fault. This is a volunteer code base supporting an open source language. If a single user has an inscrutable problem, the burden is yours to move it forward. There is nothing worse than sinking half a day into a bug report that was actually just PEBCAK.

This is the … fourth? Or just third time I recommend capturing a record of the problem so that it can be sorted to see on which side of the pipe the problem lies. And I am volunteering some pmdev’s time that might not be forthcoming but without the first step to file a reasonable bug report on your part, no time should be; so I say. Maybe I was too vague or incorrectly assuming you knew how to go about this. So here it is in detail–

• Use Chrome.
• When you visit the site, either F12 or right click the page and select Inspect element.
• You now have the Developer Tools window/panel.
• Click the Network tab.
• Check ☐ Preserve log
• Sign-in, go about your business as usual.
• Do your browsing in the same tab! The Dev panel is per tab. It won’t capture things you do in others.
• It will save some small trouble later if you start anew by clicking the ⃠ near the ☑ Preserve log whenever you’re about to sign-in again.
• When the problem occurs, Stop! Be it in two pages or 2 months, you have the log of the page states, the form content, the cookies, the works.
• Go to the Dev panel and right click to Save as HAR with Content.
• If you’re comfortable doing it: Open the file, presumably permonks.org.har and carefully scan it for password/personal info. Redact as appropriate. Try to scan backwards to a request or two before the problem happened and remove any log info before it unless you think it might be relevant.
• Don’t break the JSON or else programatic checking/replaying with something like Archive::Har will be harder for the dev than necessary.
• /msg tye, Corion, or jdporter to ask for an opinion about what to do with the file.
• Profit.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.