StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14272967
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-01-11T06:35:38.893
FavoriteCount
0
LastActivityDate
2013-01-11T06:59:50.773
LastEditDate
2013-01-11T06:59:50.773
LastEditorUserId
1410342
OwnerUserId
1841991
ParentId
13494135
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Sorry for returning back late! The issue was finally solved. The root cause was the mis-config of Apache authentication! The phenomena is that only the merging log msg were missing, so I tried to take a look at the Apache access log, and found this: <pre><code>10.14.21.75 - - [22/Nov/2012:13:22:05 +0800] "OPTIONS /svn/opencore/branches/ali00304473_Other_20120426_opencore HTTP/1.1" 200 192 10.14.21.75 - - [22/Nov/2012:13:22:05 +0800] "PROPFIND /svn/opencore/branches/ali00304473_Other_20120426_opencore HTTP/1.1" 207 772 10.14.21.75 - - [22/Nov/2012:13:22:05 +0800] "PROPFIND /svn/opencore/!svn/vcc/default HTTP/1.1" 207 1040 </code></pre> No username was identified in the requests! Then I found the SVN access rights for the branch was set to allow EVERYONE to read: <pre><code>[opencore:/branches/ali00304473_Other_20120426_opencore] * = r </code></pre> Furthermore, in <code>httpd.conf</code>, it was configured like this: <pre><code><Location /svn/> DAV svn SVNParentPath /home/admin/svnroot AuthBasicProvider file ldap AuthType Basic ..... AuthUserFile /home/admin/svnfiles/svn-auth-file Satisfy Any Require valid-user AuthzSVNAccessFile /home/admin/svnfiles/svn-access-file </Location> </code></pre> So either changing "<code>* = r" to "* =</code>" in the SVN access file, or updating "Satisfy Any" to "Satisfy All" will fix the problem. Conclusion: In our previous config (bad config), when a SVN HTTP request (without auth info) comes to the server, it first handled by Apache httpd. Because httpd was configured as "Satisfy Any", so "Require valid-user" is not a necessary option, so the request was forwarded to MOD_SVN. As the branch was opened to every one (* = r), so MOD_SVN didn't rise the authentication request back to SVN client, it then tried to fetch the logs from repository. But fetching SVN log requires authentication/authorization token, so MOD_SVN just silently failed inside the module, and httpd just returned empty log message to the client.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSVN log message of some revisions are missing
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USNoNaMe
UserOwnerUserId
1. USvliux
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTApproveEditSuggestion
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.