Various attempts to commit a new plasmid via <https://genepool.me/jeremycahill/prime-editing/new/master/?plasmid=1> fail. This is unaffected by all of the following: 1. completion or non-completion of commit message info 2. completion or non-completion of `Properties` info 3. file extension used in commit prompt's `File Name` field 4. test sequence content, including FASTA header or no-header 5. sequence upload method — direct paste versus file drag&drop 6. whether the repo is bare. Tested on current FF, FF dev, and chrome builds.
Link machine broke again. Links in `<>` will be stripped? \*Various attempts to commit a new plasmid via `https://genepool.me/jeremycahill/prime-editing/new/master/?plasmid=1` fail.
Further test that failed: committing from a subdirectory with test sequence [addgene 132774](https://www.addgene.org/132774/). (File extension doesn't match the content in the screenshot but multiple extensions failed the same way.) ![2019-10-23_011520_Genepool.png](https://files.catbox.moe/ciunz9.png)
Further test that passed: committing exactly the sequence mentioned in the guide doc, from addgene in genbank format. Link: https://genepool.me/jeremycahill/prime-editing/master/puc19_test-05-upload-in-topdir.gbk/ Munged if the above breaks: `https://genepool.me/jeremycahill/prime-editing/master/puc19_test-05-upload-in-topdir.gbk/`
Further test that passed: same as previous but directly pasted. No header. Link: https://genepool.me/jeremycahill/prime-editing/master/puc19_test-06-direct-paste-in-topdir.txt/ `https://genepool.me/jeremycahill/prime-editing/master/puc19_test-06-direct-paste-in-topdir.txt/`
Addendum to the initial list of conditions tested, in the OP: 7\. trailing whitespace at end of sequence paste and files Since I was testing with addgene, sequences terminate in a newline followed by a line containing 8 spaces. Modifying this had no effect.
Can't seem to replicate this bug. Just tested dropping a gbk into the plasmid editor with [addgene 132774](https://www.addgene.org/132774/sequences/) and committed to a subdirectory without problem via firefox without issue. When it fails does the form just not submit or does it return some 400/500 error?
When it fails, nothing visible happens on the page at all. The button is clicked and nothing changes. If there's an http error code getting logged to console or similar, I'll have to check later.
Further attempts have passed. Drag&drop and paste both working currently. I'll check back tomorrow. Maybe it affects new accounts? Intermittent connectivity issue on the backend? Dunno.
No problem today.
Ideally I'd keep this open a bit longer in case the problem resurfaces, but I'm pretty busy for the rest of the week. So I'll close now. Now that I'm no longer experiencing the bug, any further end-user guesswork from me will just be uninformed voodoo. If it's helpful to ping me or reopen later on, tim and co, feel free.