Cron Schedule Format parsing error

63 views
Skip to first unread message

an0

unread,
Apr 8, 2009, 5:04:38 AM4/8/09
to Google App Engine
sdk's parser fails to parse the example from the doc:
- description: monday morning mailout
url: /mail/weekly
schedule: every monday 9:00

Error parsing yaml file:
Unable to assign value 'every monday 9:00' to attribute 'schedule':
schedule 'every monday 9:00' failed to parse: line 1:13 mismatched
input u'9:00' expecting OF
in "./cron.yaml", line 4, column 13

djidjadji

unread,
Apr 8, 2009, 12:19:53 PM4/8/09
to google-a...@googlegroups.com
The SDK is now at number google_appengine_1.2.0.zip

http://code.google.com/appengine/downloads.html


2009/4/8 an0 <an0...@gmail.com>:

an0

unread,
Apr 8, 2009, 10:19:25 PM4/8/09
to Google App Engine
Of course I am using 1.2.0. Isn't it the first version officially
supporting cron service?

daly

unread,
Apr 14, 2009, 8:18:48 AM4/14/09
to Google App Engine

I tried and met this error too.
You can solve it by
every mon of month 09:00

month looks like replacing all months,
but there seems no abbr. for weekdays,
so I have to using
"every mon,tue,wed,thu,fri,sat,sun of month 00:00"
for my target

hope they can add 'days' or 'day' for replacing the long days string

an0

unread,
Apr 14, 2009, 11:27:21 PM4/14/09
to google-a...@googlegroups.com
Yes, it is quite verbose, and I am using the long trivial 'day of week' list, too.

However, whatsoever, it is not reasonable that the very first example they gave does not work. What a shame to doc writer and what a frustration to the readers, including me:(
--
Hell boy is cool, but let me be healthy boy first.

Dan Sanderson

unread,
Apr 15, 2009, 12:44:46 AM4/15/09
to google-a...@googlegroups.com
My apologies for the frustration.  I'll get the docs fixed.  (There is a pending fix that makes the example work, but it didn't get out in time for launch.)

*hangs head in shame*

-- Dan

an0

unread,
Apr 15, 2009, 7:10:45 AM4/15/09
to google-a...@googlegroups.com
Dan, 
It is nice to see quick response and even better, quick reactions. 
And I'm really glad to hear that the "every month" shortcut given in the "premature" doc is indeed going to work; but what about the "everyday" shortcut?

Anthony Baxter

unread,
Apr 15, 2009, 11:11:26 PM4/15/09
to Google App Engine
Would something as simple as "every day 09:00" be enough? (No it's not
there yet, just enquiring).

On Apr 15, 9:10 pm, an0 <an0...@gmail.com> wrote:
> Dan, It is nice to see quick response and even better, quick reactions.
> And I'm really glad to hear that the "every month" shortcut given in the
> "premature" doc is indeed going to work; but what about the "everyday"
> shortcut?
>
> On Wed, Apr 15, 2009 at 12:44 PM, Dan Sanderson <dansander...@google.com>wrote:
>
>
>
> > My apologies for the frustration.  I'll get the docs fixed.  (There is a
> > pending fix that makes the example work, but it didn't get out in time for
> > launch.)
> > *hangs head in shame*
>
> > -- Dan
>
> > On Tue, Apr 14, 2009 at 8:27 PM, an0 <an0...@gmail.com> wrote:
>
> >>  Yes, it is quite verbose, and I am using the long trivial 'day of week'
> >> list, too.
>
> >> However, whatsoever, it is not reasonable that the very first example they
> >> gave does not work. What a shame to doc writer and what a frustration to the
> >> readers, including me:(
>

风笑雪

unread,
Apr 15, 2009, 11:27:27 PM4/15/09
to google-a...@googlegroups.com
try this:
every day of month 09:00

The document is wrong, i met the same error.

2009/4/16 Anthony Baxter <anthon...@gmail.com>

Anthony Baxter

unread,
Apr 17, 2009, 1:07:03 AM4/17/09
to Google App Engine
No, I'm asking as a future feature for the grammar. The doc will be
fixed soon to match the 1.2.0 release, and a future release will make
the "of month" words unnecessary.

Anthony

On Apr 16, 1:27 pm, 风笑雪 <kea...@gmail.com> wrote:
> try this:every day of month 09:00
>
> The document is wrong, i met the same error.
>
> 2009/4/16 Anthony Baxter <anthonybax...@gmail.com>

Dan Sanderson

unread,
Apr 17, 2009, 1:52:15 PM4/17/09
to google-a...@googlegroups.com
The docs have been fixed to match 1.2.0.

-- Dan

2009/4/16 Anthony Baxter <anthon...@gmail.com>
Reply all
Reply to author
Forward
0 new messages