MapGuide trac instance not showing newer commits in timeline view

[jng]

The timeline view on the MapGuide trac instance seems to be "frozen in time" regarding commits. Code commits after rev 10092 do not appear (HEAD rev is currently 10095).

Also previously, if a commit message contains text of the form "Fixes #nnnn" it will auto-close the ticket of the corresponding number, but that has not been happening for commits after rev 10092.

Other changes like wiki and ticket changes do appear though.

Not sure if related to #3185

[robe]

Might be related. Did you just start noticing this. I forget how svn and trac talk.

[jng]

I started noticing this behavior when the "too many connections" errors started happening on the MG trac instance.

[robe]

Okay I've changed the connection limit for trac_mapguide to 30. Before it was 5.

SELECT datconnlimit FROM pg_database WHERE datname = 'trac_mapguide'; -- returned 5
ALTER DATABASE trac_mapguide WITH CONNECTION LIMIT = 30;

Feel free to close this if this change fixes the problem.

[jng]

Update: The "too many connections" error still occasionally happens, but not as frequently as before, so it's much more usable now. Thanks.

Timeline view still is not picking up new commits.

[strk]

I see 10097 as the most recent commit, from August 19 2024. Assuming closed. Feel free to reopen otherwise.

[jng]

The event on August 19th was me manually closing a ticket and referencing the commit 10097 done on the same day. The code commit 10097 itself is not present on the timeline and the rev link to 10097 on that closed ticket is broken (no changeset 10097 in the repository)

[jng]

Huh! The commits are showing up now. All good then!

[strk]

I've raised the limit on number of connection to 30 as I was getting a lot of errors about too many connections. See also #3185

[robe]

Replying to strk:

I've raised the limit on number of connection to 30 as I was getting a lot of errors about too many connections. See also #3185

strk this was already raised as I mentioned on #3185, perhaps we need to raise it more or did you not see it at 30 when you set it to 30. I might have been mistaken I guess.