trac down since hosting provider move?
Trying to create a new issue gave: ==== How to Reproduce ==== While doing a POST operation on `/newticket`, Trac issued an internal error. ''(please provide additional details here)'' Request parameters: {{{ {u'__FORM_TOKEN': u'06615ae4525d84b22e503ba8', u'action': u'create', u'field_branch': u'', u'field_branch_author': u'', u'field_cc': u'', u'field_component': u'trial', u'field_description': u"Reproducer:\r\n\r\n\r\n{{{\r\nfrom twisted.trial.unittest import TestCase\r\n\r\n\r\nclass StatefulCleanup:\r\n\r\n called = False\r\n\r\n def __call__(self):\r\n if self.called:\r\n raise AssertionError('Called more than once')\r\n self.called = True\r\n\r\n\r\nclass TestAddCleanup(TestCase):\r\n\r\n def setUp(self):\r\n self.addCleanup(StatefulCleanup())\r\n\r\n def testIt(self):\r\n pass\r\n}}}\r\n\r\n\r\nIf run with trial -u, the AssertionError will be issued.", u'field_keywords': u'', u'field_milestone': u'', u'field_priority': u'normal', u'field_summary': u'Cleanups added with addCleanup incorrectly called on subsequent runs when using `trial -u`', u'field_type': u'defect', u'sfp_email': u'', u'sfph_mail': u'', u'submit': u'Create ticket'} }}} User agent: `Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.71 Safari/537.36` ==== System Information ==== ''System information not available'' ==== Enabled Plugins ==== ''Plugin information not available'' ==== Interface Customization ==== ''Interface customization information not available'' ==== Python Traceback ==== {{{ Traceback (most recent call last): File "/srv/trac/virtualenv/lib/python2.7/site-packages/trac/web/main.py", line 623, in _dispatch_request dispatcher.dispatch(req) File "/srv/trac/virtualenv/lib/python2.7/site-packages/trac/web/main.py", line 239, in dispatch resp = chosen_handler.process_request(req) File "/srv/trac/virtualenv/lib/python2.7/site-packages/trac/ticket/web_ui.py", line 175, in process_request return self._process_newticket_request(req) File "/srv/trac/virtualenv/lib/python2.7/site-packages/trac/ticket/web_ui.py", line 523, in _process_newticket_request self._do_create(req, ticket, action) File "/srv/trac/virtualenv/lib/python2.7/site-packages/trac/ticket/web_ui.py", line 1382, in _do_create ticket.insert() File "/srv/trac/virtualenv/lib/python2.7/site-packages/trac/ticket/model.py", line 293, in insert listener.ticket_created(self) File "/srv/trac/virtualenv/lib/python2.7/site-packages/twisted_trac_plugins/ticket_reporter.py", line 20, in ticket_created ticket.values['summary']]) File "/usr/lib/python2.7/subprocess.py", line 172, in call return Popen(*popenargs, **kwargs).wait() File "/usr/lib/python2.7/subprocess.py", line 394, in __init__ errread, errwrite) File "/usr/lib/python2.7/subprocess.py", line 1047, in _execute_child raise child_exception OSError: [Errno 2] No such file or directory }}} Guessing this is related to the hosting provider move? Chris
hello this has now been fixed! https://gitter.im/twisted/twisted?at=615ac7dad78911028abc240f
Hi, Thanks for the report. On Mon, 4 Oct 2021 at 09:30, Chris Withers <chris@withers.org> wrote:
Trying to create a new issue gave:
==== How to Reproduce ====
While doing a POST operation on `/newticket`, Trac issued an internal error.
''(please provide additional details here)''
Request parameters: {{{ {u'__FORM_TOKEN': u'06615ae4525d84b22e503ba8', u'action': u'create', u'field_branch': u'', u'field_branch_author': u'', u'field_cc': u'', u'field_component': u'trial', u'field_description': u"Reproducer:\r\n\r\n\r\n{{{\r\nfrom twisted.trial.unittest import TestCase\r\n\r\n\r\nclass StatefulCleanup:\r\n\r\n called = False\r\n\r\n def __call__(self):\r\n if self.called:\r\n raise AssertionError('Called more than once')\r\n self.called = True\r\n\r\n\r\nclass TestAddCleanup(TestCase):\r\n\r\n def setUp(self):\r\n self.addCleanup(StatefulCleanup())\r\n\r\n def testIt(self):\r\n pass\r\n}}}\r\n\r\n\r\nIf run with trial -u, the AssertionError will be issued.", u'field_keywords': u'', u'field_milestone': u'', u'field_priority': u'normal', u'field_summary': u'Cleanups added with addCleanup incorrectly called on subsequent runs when using `trial -u`', u'field_type': u'defect', u'sfp_email': u'', u'sfph_mail': u'', u'submit': u'Create ticket'} }}}
User agent: `Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.71 Safari/537.36`
==== System Information ==== ''System information not available''
==== Enabled Plugins ==== ''Plugin information not available''
==== Interface Customization ==== ''Interface customization information not available''
==== Python Traceback ==== {{{ Traceback (most recent call last): File "/srv/trac/virtualenv/lib/python2.7/site-packages/trac/web/main.py", line 623, in _dispatch_request dispatcher.dispatch(req) File "/srv/trac/virtualenv/lib/python2.7/site-packages/trac/web/main.py", line 239, in dispatch resp = chosen_handler.process_request(req) File "/srv/trac/virtualenv/lib/python2.7/site-packages/trac/ticket/web_ui.py", line 175, in process_request return self._process_newticket_request(req) File "/srv/trac/virtualenv/lib/python2.7/site-packages/trac/ticket/web_ui.py", line 523, in _process_newticket_request self._do_create(req, ticket, action) File "/srv/trac/virtualenv/lib/python2.7/site-packages/trac/ticket/web_ui.py", line 1382, in _do_create ticket.insert() File "/srv/trac/virtualenv/lib/python2.7/site-packages/trac/ticket/model.py", line 293, in insert listener.ticket_created(self) File "/srv/trac/virtualenv/lib/python2.7/site-packages/twisted_trac_plugins/ticket_reporter.py", line 20, in ticket_created ticket.values['summary']]) File "/usr/lib/python2.7/subprocess.py", line 172, in call return Popen(*popenargs, **kwargs).wait() File "/usr/lib/python2.7/subprocess.py", line 394, in __init__ errread, errwrite) File "/usr/lib/python2.7/subprocess.py", line 1047, in _execute_child raise child_exception OSError: [Errno 2] No such file or directory }}}
Guessing this is related to the hosting provider move?
Chris
This was failing due to Twisted Trac customization . I have disabled the plugin. I think Trac was trying to talk with the IRC integration, but the IRC integration was not migrated to the new server. If you want to help with the migration, let me know. For me, the Trac migration was Plan B, and I would like to spend the available time looking at migrating Trac Tickets to GitHub Issues Regards -- Adi Roiban
On 04/10/2021 10:32, Adi Roiban wrote:
For me, the Trac migration was Plan B, and I would like to spend the available time looking at migrating Trac Tickets to GitHub Issues
That would certainly get my vote. I wish I had spare cycles, but I'm already in three levels deep yack shaving that had me hit this... If I *did* have cycles, it would be to fix that bug in trial/UnitTest, although I really wish someone had the cycles to make a real pytest plugin that replaced trial; there's so much overlap with pytest, where pytest already does an infinitely better job... Chris
On Mon, Oct 4, 2021 at 5:39 AM Chris Withers <chris@withers.org> wrote:
On 04/10/2021 10:32, Adi Roiban wrote:
For me, the Trac migration was Plan B, and I would like to spend the available time looking at migrating Trac Tickets to GitHub Issues
That would certainly get my vote.
I wish I had spare cycles, but I'm already in three levels deep yack shaving that had me hit this...
I am working on migrating Tahoe-LAFS Trac to GitLab. If Twisted wants to use GitLab instead, I'll probably eventually have a tool that makes this an easy transition. If not, I'll at least have a tool that loads everything from a trac project environment into an in-memory model where it's easier to transform into something else. Jean-Paul
On Mon, 4 Oct 2021 at 12:07, Jean-Paul Calderone <exarkun@twistedmatrix.com> wrote:
On Mon, Oct 4, 2021 at 5:39 AM Chris Withers <chris@withers.org> wrote:
On 04/10/2021 10:32, Adi Roiban wrote:
For me, the Trac migration was Plan B, and I would like to spend the available time looking at migrating Trac Tickets to GitHub Issues
That would certainly get my vote.
I wish I had spare cycles, but I'm already in three levels deep yack shaving that had me hit this...
I am working on migrating Tahoe-LAFS Trac to GitLab. If Twisted wants to use GitLab instead, I'll probably eventually have a tool that makes this an easy transition. If not, I'll at least have a tool that loads everything from a trac project environment into an in-memory model where it's easier to transform into something else.
Jean-Paul
I saw this project which does Trac to GitLab migration: https://github.com/tracboat/tracboat I didn't have time to check it out, but even when migrating to GitHub, I was thinking that some code can be reused from there. For example converting from TracWiki markup to Markdown. Regards -- Adi Roiban
On Mon, Oct 11, 2021 at 8:33 PM Adi Roiban <adiroiban@gmail.com> wrote:
On Mon, 4 Oct 2021 at 12:07, Jean-Paul Calderone <exarkun@twistedmatrix.com> wrote:
On Mon, Oct 4, 2021 at 5:39 AM Chris Withers <chris@withers.org> wrote:
On 04/10/2021 10:32, Adi Roiban wrote:
For me, the Trac migration was Plan B, and I would like to spend the available time looking at migrating Trac Tickets to GitHub Issues
That would certainly get my vote.
I wish I had spare cycles, but I'm already in three levels deep yack shaving that had me hit this...
I am working on migrating Tahoe-LAFS Trac to GitLab. If Twisted wants
to use GitLab instead, I'll probably eventually have a tool that makes this an easy transition. If not, I'll at least have a tool that loads everything from a trac project environment into an in-memory model where it's easier to transform into something else.
Jean-Paul
I saw this project which does Trac to GitLab migration: https://github.com/tracboat/tracboat
I didn't have time to check it out, but even when migrating to GitHub, I was thinking that some code can be reused from there. For example converting from TracWiki markup to Markdown.
Yes, that project exists. It's not a good fit for the Tahoe-LAFS migration. Maybe it will work for Twisted though. And as you point out, maybe it has components that are helpful even if the tool as a whole isn't.
Regards
-- Adi Roiban _______________________________________________ Twisted mailing list -- twisted@python.org To unsubscribe send an email to twisted-leave@python.org https://mail.python.org/mailman3/lists/twisted.python.org/ Message archived at https://mail.python.org/archives/list/twisted@python.org/message/SVPIPR4GXP5... Code of Conduct: https://twisted.org/conduct
Hi On Tue, 12 Oct 2021 at 01:42, Jean-Paul Calderone <exarkun@twistedmatrix.com> wrote:
On Mon, Oct 11, 2021 at 8:33 PM Adi Roiban <adiroiban@gmail.com> wrote:
On Mon, 4 Oct 2021 at 12:07, Jean-Paul Calderone <exarkun@twistedmatrix.com> wrote:
On Mon, Oct 4, 2021 at 5:39 AM Chris Withers <chris@withers.org> wrote:
On 04/10/2021 10:32, Adi Roiban wrote:
For me, the Trac migration was Plan B, and I would like to spend the available time looking at migrating Trac Tickets to GitHub Issues
That would certainly get my vote.
I wish I had spare cycles, but I'm already in three levels deep yack shaving that had me hit this...
I am working on migrating Tahoe-LAFS Trac to GitLab. If Twisted wants to use GitLab instead, I'll probably eventually have a tool that makes this an easy transition. If not, I'll at least have a tool that loads everything from a trac project environment into an in-memory model where it's easier to transform into something else.
Jean-Paul
I saw this project which does Trac to GitLab migration: https://github.com/tracboat/tracboat
I didn't have time to check it out, but even when migrating to GitHub, I was thinking that some code can be reused from there. For example converting from TracWiki markup to Markdown.
Yes, that project exists. It's not a good fit for the Tahoe-LAFS migration. Maybe it will work for Twisted though. And as you point out, maybe it has components that are helpful even if the tool as a whole isn't.
Jean Paul, have you managed to do the migration from Trac to GitLab for the Tahoe tickets? Was it a smooth migration ? For my company we have migrated from Trac Tickets to GitHub (multi-repo). It was not a perfect migration ... but it was not that bad. With the bulk import API we managed to keep the creation date for each comment. The Trac tickets that had the same ID as GitHub PR were migrated last. In this way we preserve the ID of most of the tickets Also, we plan to keep the legacy Trac instance in read only mode for the near future. The trac ticket have a reference like trac#1234 in the comments and with GitHub autolinks we automatically get a link Btw. This is already enabled on twisted/twisted trac#123 → https://twistedmatrix.com/trac/ticket/123 We also moved the wiki to GitHub Wiki .. we lost some nice features from Trac Wiki macros ...but that was not a big deal. The code is here https://github.com/chevah/trac-to-github/pull/13 Regards -- Adi Roiban
On Thu, Nov 11, 2021 at 4:19 AM Adi Roiban <adiroiban@gmail.com> wrote:
Hi
On Tue, 12 Oct 2021 at 01:42, Jean-Paul Calderone <exarkun@twistedmatrix.com> wrote:
On Mon, Oct 11, 2021 at 8:33 PM Adi Roiban <adiroiban@gmail.com> wrote:
On Mon, 4 Oct 2021 at 12:07, Jean-Paul Calderone <exarkun@twistedmatrix.com> wrote:
[snip]
I am working on migrating Tahoe-LAFS Trac to GitLab. If Twisted wants to use GitLab instead, I'll probably eventually have a tool that makes this an easy transition. If not, I'll at least have a tool that loads everything from a trac project environment into an in-memory model where it's easier to transform into something else.
Jean-Paul
I saw this project which does Trac to GitLab migration: https://github.com/tracboat/tracboat
I didn't have time to check it out, but even when migrating to GitHub, I was thinking that some code can be reused from there. For example converting from TracWiki markup to Markdown.
Yes, that project exists. It's not a good fit for the Tahoe-LAFS migration. Maybe it will work for Twisted though. And as you point out, maybe it has components that are helpful even if the tool as a whole isn't.
Jean Paul, have you managed to do the migration from Trac to GitLab for the Tahoe tickets? Was it a smooth migration ?
I haven't done this migration yet. It's sort of a mid-level priority for the Tahoe project so it isn't moving along very quickly.
For my company we have migrated from Trac Tickets to GitHub (multi-repo). It was not a perfect migration ... but it was not that bad. With the bulk import API we managed to keep the creation date for each comment.
I'm curious if you wrote any software to produce a neutral-format representation of Trac state as part of this migration effort or if you just went straight from Trac to GitHub? (ie, I wonder if you made any tools I can leverage for a different Trac migration) Jean-Paul
The Trac tickets that had the same ID as GitHub PR were migrated last. In this way we preserve the ID of most of the tickets
Also, we plan to keep the legacy Trac instance in read only mode for the near future.
The trac ticket have a reference like trac#1234 in the comments and with GitHub autolinks we automatically get a link
Btw. This is already enabled on twisted/twisted trac#123 → https://twistedmatrix.com/trac/ticket/123
We also moved the wiki to GitHub Wiki .. we lost some nice features from Trac Wiki macros ...but that was not a big deal.
The code is here https://github.com/chevah/trac-to-github/pull/13
Ah - a quick skim of this code suggests the answer to my question above is no. Okay. :) Jean-Paul
Hi, On Thu, 11 Nov 2021 at 13:31, Jean-Paul Calderone <exarkun@twistedmatrix.com> wrote:
On Thu, Nov 11, 2021 at 4:19 AM Adi Roiban <adiroiban@gmail.com> wrote:
Hi
On Tue, 12 Oct 2021 at 01:42, Jean-Paul Calderone <exarkun@twistedmatrix.com> wrote:
On Mon, Oct 11, 2021 at 8:33 PM Adi Roiban <adiroiban@gmail.com> wrote:
On Mon, 4 Oct 2021 at 12:07, Jean-Paul Calderone <exarkun@twistedmatrix.com> wrote:
[snip]
I am working on migrating Tahoe-LAFS Trac to GitLab. If Twisted wants to use GitLab instead, I'll probably eventually have a tool that makes this an easy transition. If not, I'll at least have a tool that loads everything from a trac project environment into an in-memory model where it's easier to transform into something else.
Jean-Paul
I saw this project which does Trac to GitLab migration: https://github.com/tracboat/tracboat
I didn't have time to check it out, but even when migrating to GitHub, I was thinking that some code can be reused from there. For example converting from TracWiki markup to Markdown.
Yes, that project exists. It's not a good fit for the Tahoe-LAFS migration. Maybe it will work for Twisted though. And as you point out, maybe it has components that are helpful even if the tool as a whole isn't.
Jean Paul, have you managed to do the migration from Trac to GitLab for the Tahoe tickets? Was it a smooth migration ?
I haven't done this migration yet. It's sort of a mid-level priority for the Tahoe project so it isn't moving along very quickly.
For my company we have migrated from Trac Tickets to GitHub (multi-repo). It was not a perfect migration ... but it was not that bad. With the bulk import API we managed to keep the creation date for each comment.
I'm curious if you wrote any software to produce a neutral-format representation of Trac state as part of this migration effort or if you just went straight from Trac to GitHub? (ie, I wonder if you made any tools I can leverage for a different Trac migration)
Nothing generic yet. Very specific to GitHub API ... which is not the best. I hope GitLab has a better import API. And it's kind of specific to sqlite and converting from one Trac to multiple GitHub repos, with organization-wide projects. This might change when updating to handle Twisted.
The Trac tickets that had the same ID as GitHub PR were migrated last. In this way we preserve the ID of most of the tickets
Also, we plan to keep the legacy Trac instance in read only mode for the near future.
The trac ticket have a reference like trac#1234 in the comments and with GitHub autolinks we automatically get a link
Btw. This is already enabled on twisted/twisted trac#123 → https://twistedmatrix.com/trac/ticket/123
We also moved the wiki to GitHub Wiki .. we lost some nice features from Trac Wiki macros ...but that was not a big deal.
The code is here https://github.com/chevah/trac-to-github/pull/13
Ah - a quick skim of this code suggests the answer to my question above is no. Okay. :)
The code just gets the things done :) For ticket, the code only handles sqlite and Twisted has PostgreSQL Converting to PostgreSQL to do wiki migration was not that complicated https://github.com/chevah/trac-to-github/pull/12/files And I expect that converting the ticket migration from sqlite to psql will not be complicated. -- Adi Roiban
participants (4)
-
Adi Roiban -
Chris Withers -
Jean-Paul Calderone -
Thomas Grainger