To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.admin.generalOpen lugnet.admin.general in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Administrative / General / 8331
8330  |  8332
Subject: 
Re: error message!
Newsgroups: 
lugnet.admin.general
Date: 
Sun, 19 Nov 2000 11:50:15 GMT
Viewed: 
250 times
  
Thanks Todd,

everything now works fine again, please excuse that I have stolen your time
as we all know you have so much to do. I didn't entirely understand what
excactly went wrong, but I'm happy it's okay now. I don't think that I
entered an ASCII #0 character, I assume much more that I 'opened' the set
2198 twice on the same page. Let me explain that:
I usually enter a lot of info at once, whenever I picked up a couple of sets
that are not listed as part of my collection. In order to upload all info
quickly, I simply put ALL set numbers into the 'LEGO Set Reference' Search
field so that I will see a page that shows excactly the sets I picked up,
for example:
http://guide.lugnet.com/set/?q=2805,+2806,+2198,+4990,+2198&v=a
The problem with this specific page was that it is listing 2198 twice as I
picked up two copies and therefor entered it twice in the same Search field.
Instead of submitting 'Own Public: 2' I must have entered 1 in both fields
(though a different private note) and it seems like the server mixed some
info up because of that. I'll better not 'test' again what happens when
entereing two different notes for one set at the same time, but you might
find a way to forbid it completely, maybe I'll be uncareful again one day.

Again, thanks a lot for the support, maybe you'll think about my description
also. And don't worry about slow replies, I am usually horribly slow in
replying also.

Bye, Christian --- xTI@N.
------------------------------------------------------------------------
Lugnet #479 - The World is full of AFOLs - e-mail: gech1@t-online.de
my website: www.members.tripod.de/crazymaniac/my_own_news.html

"Todd Lehman" <lehman@javanet.com> wrote in message
news:G48s24.KC8@lugnet.com...
In lugnet.admin.general, Christian Gemuenden writes:
Can anyone tell me what happened or how I can fix this error? Or will I • have
to live with this error message regarding these four sets?

Christian,

The error message was an internal consistency check -- the system noticed
that an element of the cross-reference data in a two-dimensional matrix
(that's what the "m2" in the assertion failure stood for) was • inconsistent.
As near as I can figure, what happened is that, somehow, you entered an
ASCII #0 character (that is to say, an actual ASCII NUL (#0), not the • digit
"0", which is ASCII #48) into the form fields for private and public notes
for two sets (2198 and 6569).

Since ASCII #0 is used in this particular instance as a list-item • separator
in the data matrix (it assumed that ASCII 0 couldn't be present in the • input
data), the extra ASCII 0 caused confusion and made the code think the data
was corrupt.

To clear up the problem, I converted the 0's to spaces (ASCII #32) in the • raw
data.  (So you might want to double-check what shows up for those two • sets.)
I also added an encoding filter on the data to make sure that ASCII 0's • don't
sneak in again in the future.

I apologize for the inconvenience this has caused -- and for not getting • to
the bottom of this sooner.  We were out of town on business Tuesday and
Wednesday and I started a new day-job on Thursday, so it's been an unusual
week.  Things should be settling back to normal in a few days.

--Todd



Message has 1 Reply:
  Re: error message!
 
(...) Aha! OK, then I see now how the ASCII 0 got there! :-) :-) When the low- level CGI stuff on the server receives two copies of the same field, it pastes them together with and ASCII 0 separator into a single string. In an HTML, the only time (...) (24 years ago, 19-Nov-00, to lugnet.admin.general)

Message is in Reply To:
  Re: error message!
 
(...) Christian, The error message was an internal consistency check -- the system noticed that an element of the cross-reference data in a two-dimensional matrix (that's what the "m2" in the assertion failure stood for) was inconsistent. As near as (...) (24 years ago, 18-Nov-00, to lugnet.admin.general)

15 Messages in This Thread:




Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR