ietf-tools / datatracker

The day-to-day front-end to the IETF database for people who work on IETF standards.
https://datatracker.ietf.org
BSD 3-Clause "New" or "Revised" License
588 stars 350 forks source link

Author extraction fails for some author names #3276

Open ietf-svn-bot opened 3 years ago

ietf-svn-bot commented 3 years ago

type_defect | by jennifer@painless-security.com


The test_submit_existing_rg test fails occasionally. This seems to happen when the PersonFactory generates an author name with non-western characters. I'm not sure whether this reflects a failure that would occur in production, but I suspect it does.

This affects my tests roughly one out of every 5-10 runs through the test suite.

test_submit_existing_rg (ietf.submit.tests.SubmitTests.test_submit_existing_rg) ... 
Author extraction failure.
Author name used in test: उमा के.सी.
Author ascii name: Umaa Kesii.
Author initials: U.
FAIL
======================================================================
FAIL: test_submit_existing_rg (ietf.submit.tests.SubmitTests.test_submit_existing_rg)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/jlr/Documents/painless-security/src/ietf/datatracker/ietf/submit/tests.py", line 677, in test_submit_existing_rg
    self.submit_existing(["txt"],group_type='rg', stream_type='irtf')
  File "/home/jlr/Documents/painless-security/src/ietf/datatracker/ietf/submit/tests.py", line 541, in submit_existing
    status_url, author = self.do_submission(name, rev, group, formats, author=prev_author.person)
  File "/home/jlr/Documents/painless-security/src/ietf/datatracker/ietf/submit/tests.py", line 212, in do_submission
    self.assertEqual(len(submission.authors), 1)
AssertionError: 0 != 1

Issue migrated from trac:3276 at 2022-03-04 08:39:47 +0000

ietf-svn-bot commented 3 years ago

@rjsparks@nostrum.com changed priority from n/a to major

ietf-svn-bot commented 3 years ago

@rjsparks@nostrum.com changed status from new to accepted

ietf-svn-bot commented 3 years ago

@rjsparks@nostrum.com commented


I'm not sure we would allow the names creating the issue into the production database, but it does need investigation. This is a very annoying and frequently encountered fail for me as well.

ietf-svn-bot commented 3 years ago

@jennifer@painless-security.com commented


Likely related: #3231