[yaco-community-tool] Fwd: RE: Beta testing of upcoming draft tracking service

[Henrik Levkowetz <[e-mail]>]

Hi Emilio,

It would be good if it was possible to test notifications for
new drafts, by doing draft submissions, but this fails at the
moment with the error below.  Could you have a look at this,
please?


Best regards,

	Henrik

-------- Original Message --------
Subject: RE: Beta testing of upcoming draft tracking service
Date: Tue, 6 Dec 2011 16:25:22 -0800
From: Jim Schaad <[e-mail]>
To: 'Henrik Levkowetz' <[e-mail]>

When trying to import a new document I get the following 

Jim


ImportError at /submit/
No module named magic

Request Method:

POST

Request URL:

http://beta.community.yaco.es/submit/

Exception Type:

ImportError

Exception Value:

No module named magic 

Exception Location:

/home/community/community/ietf/submit/parsers/plain_parser.py in
parse_file_charset, line 33

Python Executable:

/usr/bin/python

Python Version:

2.6.6

Python Path:

['/home/community/community',
'/usr/local/lib/python2.6/dist-packages/pytz-2011n-py2.6.egg',
'/usr/lib/python2.6', '/usr/lib/python2.6/plat-linux2',
'/usr/lib/python2.6/lib-tk', '/usr/lib/python2.6/lib-old',
'/usr/lib/python2.6/lib-dynload', '/usr/local/lib/python2.6/dist-packages',
'/usr/lib/python2.6/dist-packages', '/usr/lib/pymodules/python2.6',
'/usr/lib/python2.6/dist-packages/wx-2.8-gtk2-unicode',
'/home/community/community', '/home/community/community/redesign']

Server time:

Tue, 6 Dec 2011 16:23:32 -0800


***************************************

Environment:

Request Method: POST
Request URL: http://beta.community.yaco.es/submit/
Django Version: 1.1.1 SVN-3714
Python Version: 2.6.6
Installed Applications:
['django.contrib.auth',
 'django.contrib.contenttypes',
 'django.contrib.sessions',
 'django.contrib.sites',
 'django.contrib.sitemaps',
 'django.contrib.admin',
 'django.contrib.admindocs',
 'django.contrib.humanize',
 'south',
 'workflows',
 'permissions',
 'redesign.person',
 'redesign.name',
 'redesign.group',
 'redesign.doc',
 'ietf.announcements',
 'ietf.idindex',
 'ietf.idtracker',
 'ietf.ietfauth',
 'ietf.iesg',
 'ietf.ipr',
 'ietf.liaisons',
 'ietf.mailinglists',
 'ietf.meeting',
 'ietf.proceedings',
 'ietf.redirects',
 'ietf.idrfc',
 'ietf.wginfo',
 'ietf.submit',
 'ietf.ietfworkflows',
 'ietf.wgchairs',
 'ietf.community']
Installed Middleware:
('django.middleware.common.CommonMiddleware',
 'django.contrib.sessions.middleware.SessionMiddleware',
 'django.contrib.auth.middleware.AuthenticationMiddleware',
 'django.contrib.auth.middleware.RemoteUserMiddleware',
 'django.middleware.doc.XViewMiddleware',
 'ietf.middleware.SQLLogMiddleware',
 'ietf.middleware.SMTPExceptionMiddleware',
 'ietf.middleware.RedirectTrailingPeriod',
 'django.middleware.transaction.TransactionMiddleware',
 'ietf.middleware.UnicodeNfkcNormalization')


Traceback:
File "/home/community/community/django/core/handlers/base.py" in
get_response
  92.                 response = callback(request, *callback_args,
**callback_kwargs)
File "/home/community/community/ietf/submit/views.py" in submit_index
  26.             if form.is_valid():
File "/home/community/community/django/forms/forms.py" in is_valid
  120.         return self.is_bound and not bool(self.errors)
File "/home/community/community/django/forms/forms.py" in _get_errors
  111.             self.full_clean()
File "/home/community/community/django/forms/forms.py" in full_clean
  243.                     value = getattr(self, 'clean_%s' % name)()
File "/home/community/community/ietf/submit/forms.py" in clean_txt
  96.         parsed_info = PlainParser(txt_file).critical_parse()
File "/home/community/community/ietf/submit/parsers/plain_parser.py" in
critical_parse
  22.         self.parse_file_charset()
File "/home/community/community/ietf/submit/parsers/plain_parser.py" in
parse_file_charset
  33.         import magic

Exception Type: ImportError at /submit/
Exception Value: No module named magic

> -----Original Message-----
> From: Henrik Levkowetz [mailto:[e-mail]]
> Sent: Monday, December 05, 2011 4:15 AM
> To: Jim Schaad
> Cc: 'WG Chairs'; [e-mail]
> Subject: Re: Beta testing of upcoming draft tracking service
> 
> Hi Jim,
> 
> On 2011-12-04 23:07 Jim Schaad said:
> > Can we do draft submissions followed by working group acceptance of a
> > document?
> 
> You should be able to, although I've not tested doing draft submissions
> against the beta server.  If anything, there might be a problem with
missing
> draft repository directories, but we can fix that if there is a problem.
> 
> 
> Best regards,
> 
> 	Henrik
> 
> 
> >> -----Original Message-----
> >> From: [e-mail] [mailto:[e-mail]] On
> >> Behalf Of Henrik Levkowetz
> >> Sent: Friday, December 02, 2011 10:25 AM
> >> To: WG Chairs
> >> Subject: Re: Beta testing of upcoming draft tracking service
> >>
> >> Hi again,
> >>
> >> One more point related to this:  When you create a test login, please
> >> use
> > a
> >> throwaway password, not something you'd not care for people seeing.
> >>
> >> The reason is that although no passwords are stored in database or
> >> apache login digest file, passwords will be visible if something goes
> >> wrong when
> > you
> >> set up your account and a crash log including stack dump is created.
> >>
> >>
> >> Best regards,
> >>
> >> 	Henrik
> >>
> >> On 2011-12-02 14:28 Henrik Levkowetz said the following:
> >>> Hi,
> >>>
> >>> Introduction
> >>> ------------
> >>>
> >>> We now have an implementation of RFC 6293
> >>> (http://tools.ietf.org/html/rfc6293)
> >>> "Requirements for Internet-Draft Tracking by the IETF Community in
> >>> the Datatracker" ready for some testing.
> >>>
> >>> It would be much appreciated if you would assist in testing this.
> >>>
> >>> If you go to http://beta.community.yaco.es/ you'll see a pretty
> >>> ordinary datatracker first page; in order to test the new
> >>> functionality you'll need to get and use a test login.
> >>>
> >>> Account Setup
> >>> -------------
> >>>
> >>> You acquire a test login by clicking on the 'New Account' link at
> >>> the top of the lefthand menubar, and then follow the 'Request an
> account'
> > link.
> >>> Fill in the email address you want to use, and you'll be sent an
> >>> email with further instructions.  Once you've completed those,
> >>> you'll have an account on the beta server which you can use to test
> >>> the draft
> > tracking
> >> service.
> >>>
> >>> Setting up documents to track
> >>> -----------------------------
> >>>
> >>> Use your account to log in.  You will now see a new link in the
> >>> lefthand menubar, under "Community ID lists": "Personal list".
> >>> Click this, and you'll be taken to a page with 5 tabs, where you can
> >>> set up the rules for drafts you want to follow, and see the
> >>> generated status page which lists all the drafts you've chosen.
> >>>
> >>> So far, so good -- it would be appreciated if you would test this
> >>> out, and send feedback to the [e-mail] mailing
> >>> list about what you find.
> >>>
> >>> Triggering notifications
> >>> ------------------------
> >>>
> >>> There is one part of the functionality which is complete, but will
> >>> require manual work by the testers in order to manifest:  Normally,
> >>> email notifications about changes to the documents you have set up
> >>> for tracking will be sent out as soon as an AD, Chair, or someone
> >>> from the secretariat goes in and changes status for a document.  As
> >>> this isn't happening on the beta server, it is required that you as
> >>> a tester go in and make changes in order to see change notifications
> coming.
> >>>
> >>> The developer has set up a particular user which has been given
> >>> authority to change the state of any draft in any stream:
> >>> 'stream_user' with password 'stream_user'.  Please use this to go in
> >>> and change the state of documents you have set up tracking for, in
> >>> order
> > to
> >> exercise the notification feature.
> >>>
> >>> We are aware that this is less than ideal, but we don't currently
> >>> have any way to trigger changes in the beta server based on actions
> >>> taken in the production server.
> >>>
> >>> Questions, feedback
> >>> -------------------
> >>>
> >>> As mentioned earlier, please send questions and feedback to the
> >>> mailing list set up for the project: [e-mail].
> >>>
> >>>
> >>> Best regards,
> >>>
> >>> 	Henrik
> >>>
> >
> >
> >