Edgewall Software

Opened 10 years ago

Last modified 7 years ago

#11775 closed defect

trac-admin "changeset modified" with an invalid changeset is not logged — at Version 5

Reported by: Ryan J Ollos Owned by: Ryan J Ollos
Priority: normal Milestone: 1.0.3
Component: version control Version:
Severity: normal Keywords:
Cc: Branch:
Release Notes:
  • A warnings is logged when an invalid changeset is passed to RepositoryManager.notify().
  • An exception without traceback is printed to the console when TracAdmin's changeset added or changeset modified is called with invalid revision arguments.
API Changes:
Internal Changes:

Description

With the changes implemented in #11386, trac-admin $env changeset added $repos $rev with an invalid rev results in an error being logged. However an error is not logged when the changeset modified command is called.

The following is the output with logging directed to the console: 

$ trac-admin ../tracdev changeset modified tracdev2 100
NoSuchChangeset: No changeset 100 in the repository
$ trac-admin ../tracdev changeset added tracdev2 100
07:32:46 Trac[api] DEBUG: No changeset '100' found in repository 'tracdev2'. Skipping subscribers for event changeset_added

Change History (5)

comment:1 by Ryan J Ollos, 10 years ago

Owner: set to Ryan J Ollos
Status: new → assigned

Proposed changes in log:rjollos.git:t11775. It might be good to add a unit test or two before pushing the changes.

comment:2 by Jun Omae, 10 years ago

I reconsider about Skipping subscribers … messages, perhaps we should use log.warn() rather than log.debug() when no such changeset because the specified reponame and/or revs are probably wrong…?

  • trac/versioncontrol/api.py 

    diff --git a/trac/versioncontrol/api.py b/trac/versioncontrol/api.py
index 816dcc4..391fbf6 100644
    a b class RepositoryManager(Component):  
    693693                    try:
    694694                        old_changeset = repos.sync_changeset(rev)
    695695                    except NoSuchChangeset:
    696                         self.log.debug(
     696                        self.log.warn(
    697697                            "No changeset '%s' found in repository '%s'. "
    698698                            "Skipping subscribers for event %s",
    699699                            rev, reponame, event)
    … … class RepositoryManager(Component):  
    707707                        repos.sync_changeset(rev)
    708708                        changeset = repos.get_changeset(rev)
    709709                    except NoSuchChangeset:
    710                         self.log.debug(
     710                        self.log.warn(
    711711                            "No changeset '%s' found in repository '%s'. "
    712712                            "Skipping subscribers for event %s",
    713713                            rev, reponame, event)

comment:3 by Ryan J Ollos, 10 years ago

Logging a warning seems like I good idea. I'll include the comment:2 patch in the changes.

in reply to:  2 comment:4 by Ryan J Ollos, 10 years ago

Replying to jomae:

I reconsider about Skipping subscribers … messages, perhaps we should use log.warn() rather than log.debug() when no such changeset because the specified reponame and/or revs are probably wrong…?

Log level for existing message changed in [13339], merged in [13340].

comment:5 by Ryan J Ollos, 10 years ago

Release Notes: modified (diff)

Revised changes in log:rjollos.git:t11775.2. 

$ trac-admin ../tracdev changeset added "(default)" 100 101
NoSuchChangeset: No changeset 100 in the repository
NoSuchChangeset: No changeset 101 in the repository

$ trac-admin ../tracdev changeset modified "(default)" 100 101
NoSuchChangeset: No changeset 100 in the repository
NoSuchChangeset: No changeset 101 in the repository
Note: See TracTickets for help on using tickets.