On Tue, Sep 7, 2010 at 7:47 AM, Dan Urist <[email protected]> wrote: > On Mon, 6 Sep 2010 16:52:05 -0700 > Nigel Kersten <[email protected]> wrote: > > >> I've actually always considered this to be relatively comprehensible. >> >> Client and server start with a clean slate. >> Client requests module X >> Server parses module X via autoloading, complains about parse error. >> Client requests module X >> Server tells you it can't find it as it's not going to reattempt >> parsing unless the file changes. >> >> Does it really impact upon debugging that much? > > I've also found the inconsistency in the errors very confusing, but > this explanation makes perfect sense. > >> What do you think makes more sense? To not present the parsing error >> to the client at all? Or to continuously try and parse manifests even >> though the server thinks that they have a parse error? > > Maybe cache the error for consistency if that's not too much work, or at > least document the behavior, maybe as a FAQ?
Doug, did you put a bug report in? If there's a clear way to cache the initial error, that does seem like the most user friendly solution. > > > -- > Dan Urist > [email protected] > 303-497-2459 > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
