I wanted to submit ticket but no success. I got following stack trace:
Traceback (most recent call last):
File "/usr/local/lib/python2.4/site-packages/trac/web/main.py",
line
314, in dispatch_request
dispatcher.dispatch(req)
File "/usr/local/lib/python2.4/site-packages/trac/web/main.py",
line
199, in dispatch
resp = chosen_handler.process_request(req)
File
"/usr/local/lib/python2.4/site-packages/trac/ticket/web_ui.py",
line 109, in process_request
self._do_create(req, db)
File
"/usr/local/lib/python2.4/site-packages/trac/ticket/web_ui.py",
line 170, in _do_create
ticket.insert(db=db)
File "/usr/local/lib/python2.4/site-packages/trac/ticket/model.py",
line 162, in insert
[self[name] for name in std_fields] +
File "/usr/local/lib/python2.4/site-packages/trac/db/util.py", line
47, in execute
return self.cursor.execute(sql_escape_percent(sql), args)
File "/usr/local/lib/python2.4/site-packages/trac/db/util.py", line
47, in execute
return self.cursor.execute(sql_escape_percent(sql), args)
File "/usr/local/lib/python2.4/site-packages/pyPgSQL/PgSQL.py",
line
3111, in execute
raise OperationalError, msg
OperationalError: ERROR: null value in column "id" violates not-null
constraint
The content of ticket I wanted to submit is:
------
Summary: Adding attachment causes charset encoding disappear from
Content-Type header in first part
Full description:
Sending an e-mail without attachment generates correct header
{{{Content-Type: text/html; charset=utf-8}}}
But as soon as attachment is added, there''s missing
"charset=utf-8" in
that header in very first part of message.
Hack that solved problem was the change of
[http://dev.rubyonrails.org/browser/trunk/actionmailer/lib/action_mailer/base.rb#L376
this line] to one having content_type specified such as:
{{{
@parts.unshift Part.new(:content_type => content_type,
:charset => charset, :body => @body)
}}}
-----
--
Kamil Kukura
Czech Republic
On 2006-08-01, at 03:59 , Kamil Kukura wrote:> I wanted to submit ticket but no success. I got following stack trace:Isn''t it maybe a good idea to take the new ticket page down for the moment? I''m sure a lot of people are posting reports only to be greeted with an error, and that''s a waste of their time. While trac is not fixed, that page should be replaced with a notice. Perhaps redirecting people here?
On 8/1/06, Caio Chassot <lists@v2studio.com> wrote:> > On 2006-08-01, at 03:59 , Kamil Kukura wrote: > > > I wanted to submit ticket but no success. I got following stack trace: > > Isn''t it maybe a good idea to take the new ticket page down for the > moment? > > I''m sure a lot of people are posting reports only to be greeted with > an error, and that''s a waste of their time. > > While trac is not fixed, that page should be replaced with a notice. > Perhaps redirecting people here?+1 Definitely take it down until its fixed...it annoys potential contributors and looks unprofessional. - rob
Are all new, noncritical patches on hold for right now pending the new ticket page? I''ve started editing documentation in the core Rails classes to make them more clear, fix typos, and in some cases, fill in undocumented public methods. Speaking of which, is this what David wanted at RailsConf when he asked for more documentation? I interpreted as such and then, after I''d done some work, I realized he may have meant the HOWTOs in the wiki. Can someone on the core team give me clarity on what they would have a warm body do if they had them once a week for eight hours? mg ref: http://en.wikipedia.org/wiki/Warm_body Rob Sanheim wrote:> On 8/1/06, Caio Chassot <lists@v2studio.com> wrote: >> >> On 2006-08-01, at 03:59 , Kamil Kukura wrote: >> >> > I wanted to submit ticket but no success. I got following stack trace: >> >> Isn''t it maybe a good idea to take the new ticket page down for the >> moment? >> >> I''m sure a lot of people are posting reports only to be greeted with >> an error, and that''s a waste of their time. >> >> While trac is not fixed, that page should be replaced with a notice. >> Perhaps redirecting people here? > > +1 > > Definitely take it down until its fixed...it annoys potential > contributors and looks unprofessional. > > - rob > _______________________________________________ > Rails-core mailing list > Rails-core@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails-core >-- Michael Genereux SimianCodex - Web Application Development 949-874-6268
On Aug 1, 2006, at 1:34 PM, Michael Genereux wrote:> Are all new, noncritical patches on hold for right now pending the > new ticket page? I''ve started editing documentation in the core > Rails classes to make them more clear, fix typos, and in some > cases, fill in undocumented public methods. Speaking of which, is > this what David wanted at RailsConf when he asked for more > documentation? I interpreted as such and then, after I''d done some > work, I realized he may have meant the HOWTOs in the wiki. Can > someone on the core team give me clarity on what they would have a > warm body do if they had them once a week for eight hours?I''d like to see the docs thoroughly reviewed against the source and expanded with concise examples from the wiki et al. Think of the process as rcov for docs - the behavior of a method should be transparently and completely reflected in its docs. See AR associations for some poor examples (Dave T ran into considerable ambiguity documenting them for agile2.) Interestingly, something that''d make documentation easier and clearer would be more managable unit tests. Since a method''s tests are our ultimate measure of its expected behavior, good documentation starts there. Tests are roughly organized but a jumble when it comes to "where is method X behavior tested?". Break em up those ice floes and reorganize similarly to Active Support''s lib layout. Thanks Michael - jeremy
Caio Chassot napsal(a):> > On 2006-08-01, at 03:59 , Kamil Kukura wrote: > >> I wanted to submit ticket but no success. I got following stack trace: > > Isn''t it maybe a good idea to take the new ticket page down for the moment? > > I''m sure a lot of people are posting reports only to be greeted with an > error, and that''s a waste of their time.Eh, posted there also a fix, so people looking after solution of same problem can google it at least...> While trac is not fixed, that page should be replaced with a notice. > Perhaps redirecting people here?-- K.