Ticket #684 (assigned defect)

Opened 6 years ago

Last modified 5 years ago

[NEEDINFO] element Count: Schemas validity error : Element 'Count': This element is not expected. Expected is ( Frequency ).

Reported by: jas Owned by: cstender
Priority: normal Milestone:
Component: Format Plugin: vformat: event Version: 0.38
Severity: normal Keywords:
Cc: petr.novak@…

Description

Hi! I get this error when syncing with my nokia e51:

element Count: Schemas validity error : Element 'Count': This element is not expected. Expected is ( Frequency ).

The vevent is (sensitive information modified, but nothing else), from the file-sync local storage:

BEGIN:VCALENDAR
PRODID:-//OpenSync//NONSGML OpenSync vformat 0.3//EN
VERSION:2.0
BEGIN:VEVENT
CLASS:PRIVATE
DTEND:20060613T220000Z
DTSTART:20060613T220000Z
LAST-MODIFIED:20080207T145019Z
PRIORITY:0
RRULE:COUNT=0;INTERVAL=1
SEQUENCE:0
SUMMARY:Foo
UID:07022008145019137375-0
END:VEVENT
END:VCALENDAR

See also discussion at: http://thread.gmane.org/gmane.comp.misc.opensync.user/2453/focus=2455

Note that I don't get the same vevent card from the phone if I sync with 'vevent10' instead of 'vevent20'. Is this a problem in the phone? If I sync using vevent20 type in the syncml-obex-client configuration, I get the following vevent card (for same instance):

BEGIN:VCALENDAR

PRODID:-//OpenSync//NONSGML OpenSync vformat 0.3//EN

VERSION:2.0

BEGIN:VEVENT

CLASS:PRIVATE

DTEND:20060613T220000Z

DTSTART:20060613T220000Z

LAST-MODIFIED:20080207T145019Z

PRIORITY:0

RRULE:FREQ=YEARLY;UNTIL=21000613T0000-1Z;INTERVAL=1;BYMONTH=6

SEQUENCE:0

SUMMARY:Foo
UID:07022008145019137375-0

END:VEVENT

END:VCALENDAR

Thanks, Simon

Attachments

traces.tar.bz2 (37.9 KB) - added by mkoller 6 years ago.

Change History

comment:1 Changed 6 years ago by jas

Sorry, I mixed up 'vevent20' vs 'vevent10' there: the first vevent card (the incorrect one) was synced using vevent20 and the "correct" card was synced using vevent10.

I was also able to retrieve the "real" vevent card as returned by syncml-obex-client --slow-sync instead, and it is (regardless of whether it was synced with text/calendar or text/x-vcalendar):

BEGIN:VCALENDAR
VERSION:1.0
TZ:+01
DAYLIGHT:TRUE;+02;20060326T010000Z;20061029T010000Z;;
DAYLIGHT:TRUE;+02;20080330T010000Z;20081026T010000Z;;
DAYLIGHT:TRUE;+02;20090329T010000Z;20091025T010000Z;;
DAYLIGHT:TRUE;+02;20100328T010000Z;20101031T010000Z;;
DAYLIGHT:TRUE;+02;20110327T010000Z;20111030T010000Z;;
DAYLIGHT:TRUE;+02;20120325T010000Z;20121028T010000Z;;
BEGIN:VEVENT
UID:07022008145019137375-0
SUMMARY;ENCODING=QUOTED-PRINTABLE;CHARSET=UTF-8:Foo
DTSTART:20060613T220000Z
DTEND:20060613T220000Z
X-EPOCAGENDAENTRYTYPE:APPOINTMENT
CLASS:PRIVATE
SEQUENCE:0
X-METHOD:NONE
RRULE:YM1 6 21000613T000000
LAST-MODIFIED:20080207T145019Z
PRIORITY:0
X-SYMBIAN-LUID:30
END:VEVENT
END:VCALENDAR

Thanks, Simon

comment:2 Changed 6 years ago by felixmoeller

This seems the same as bug #678 ...

comment:3 Changed 6 years ago by jas

Yeah, they look the same. At least we now know that this arise in rather different environments.

comment:4 Changed 6 years ago by cstender

  • Status changed from new to assigned
  • Milestone set to OpenSync 0.40

comment:5 Changed 6 years ago by cstender

  • Priority changed from normal to high

Can you please provide OpenSyncs? trace files? I can't find the error with vformat.

comment:6 Changed 6 years ago by tuju

  • Milestone changed from 0.40 to 0.38

comment:7 Changed 6 years ago by tuju

  • Milestone changed from 0.38 to 0.39

vformat will get more attention in 0.39.

comment:8 Changed 6 years ago by tuju

  • Priority changed from high to normal
  • Version changed from 0.36 to 0.38

comment:9 Changed 6 years ago by cstender

  • Summary changed from element Count: Schemas validity error : Element 'Count': This element is not expected. Expected is ( Frequency ). to [NEEDINFO] element Count: Schemas validity error : Element 'Count': This element is not expected. Expected is ( Frequency ).

Please try latest svn and provide trace files, otherwise there is nothing I can do.

Changed 6 years ago by mkoller

comment:10 Changed 6 years ago by mkoller

  • Summary changed from [NEEDINFO] element Count: Schemas validity error : Element 'Count': This element is not expected. Expected is ( Frequency ). to element Count: Schemas validity error : Element 'Count': This element is not expected. Expected is ( Frequency ).

I have the same problem with todays SVN.

The vevent downloaded from the phone via syncml-ds-tool is:

BEGIN:VCALENDAR
VERSION:1.0
BEGIN:VEVENT
DTSTART:20081231T235900
DTEND:20081231T235900
DALARM:20081231T090000
AALARM:20081231T090000
PRIORITY:0
STATUS:NEEDS ACTION
RRULE:YD1 #0
CATEGORIES:SPECIAL OCCASION
SUMMARY:2008 Adgjm
END:VEVENT
END:VCALENDAR

When running vconvert --to-xmlformat it gives

<?xml version="1.0"?>
<event>
  <AlarmAudio>
    <AlarmAction>AUDIO</AlarmAction>
    <AlarmTrigger>20081231T090000</AlarmTrigger>
  </AlarmAudio>
  <AlarmDisplay>
    <AlarmAction>DISPLAY</AlarmAction>
    <AlarmTrigger>20081231T090000</AlarmTrigger>
  </AlarmDisplay>
  <Categories>
    <Category>SPECIAL OCCASION</Category>
  </Categories>
  <DateEnd>
    <Content>20081231T235900</Content>
  </DateEnd>
  <DateStarted>
    <Content>20081231T235900</Content>
  </DateStarted>
  <Priority>
    <Content>0</Content>
  </Priority>
  <RecurrenceRule>
    <Frequency>YEARLY</Frequency>
    <Count>0</Count>
    <Interval>1</Interval>
  </RecurrenceRule>
  <Status>
    <Content>NEEDS ACTION</Content>
  </Status>
  <Summary>
    <Content>2008 Adgjm</Content>
  </Summary>
</event>

Running this through

xmllint --schema ../share/libopensync1/schemas/xmlformat-event.xsd /tmp/vcal.xml

says, it's valid.

I also attach the logs during this sync:

Group: nokia-file
Member 1: syncml-obex-client
Member 2: file-sync

comment:11 Changed 6 years ago by che

  • Cc petr.novak@… added

comment:12 Changed 6 years ago by dgollub

  • Milestone OpenSync 0.39 deleted

comment:13 Changed 6 years ago by cstender

  • Component changed from Format Plugin: vformat to Format Plugin: vformat: event

comment:14 Changed 5 years ago by cstender

Sorry, but I can still not reproduce this on my local maschine with vconvert.

Can somebody please sent me a vevent which triggers the validation error + the corresponding trace files?

Maybe this is only reproducible when doing a full synchronization but I don't believe that.

comment:15 Changed 5 years ago by felixmoeller

cstender, have you looked at the traces provided by mkoller in comment:10?

They contain at least the error AFAIK.

comment:16 Changed 5 years ago by cstender

  • Summary changed from element Count: Schemas validity error : Element 'Count': This element is not expected. Expected is ( Frequency ). to [NEEDINFO] element Count: Schemas validity error : Element 'Count': This element is not expected. Expected is ( Frequency ).

Yes, I found some conversion errors and warnings in mkoellers traces and also the "ERROR: XMLFormat validation failed." message. Sadly, I can't see what went wrong, because sensitive content was hidden.

@mkoller: Can you please provide traces without the privacy feature activated and send them to me directly? Feel free to modify all names, numbers and so one.

Note: See TracTickets for help on using tickets.