Re: [google-appengine] Re: "One senses GAE is just not a major priority for Google"

[Jeff Schnitzer]

Funny. I also find myself consistently going back to the old console. The
log viewer is the one part of the new system that I think might be an
actual improvement since the old one seems to be very quirky about actually
finding logs, although I hate the new color scheme.

The task queue management is a huge step backwards though. I frequently
have to reload to see the state, and the new UI takes something like 5s to
reassemble itself from the various iframes/whatever it loads. It's a
serious drag. Maybe just a refresh button would help.

I just hope that someone is busy reinventing the datastore viewer. That
would be compelling.

Jeff

On Sat, Nov 8, 2014 at 6:26 PM, Brandon Thomson 
wrote:

> On Saturday, November 8, 2014 2:29:02 PM UTC-5, Josh Whelchel (Loudr)
> wrote:
>>
>> Also, to those criticisms of the new log viewer, what's the basis for
>> your complaints? I love the new viewer and after adjusting to it
>> (admittedly the transition took a few days) - it's MUCH faster and easier
>> to use.
>>
>
> To be clear, I am very happy with app engine in general. I like the
> existing offering very much and want it to either stay the same or to be
> genuinely improved. I am not a fan of change for its own sake, something
> which this new logs viewer seems to be an example of. I am calling it out
> publicly here to alert people to the risks of these kinds of changes, and
> also perhaps to decrease the odds that the old logs viewer will be scrapped.
>
> Based on my brief tests over the last few weeks, here are my complaints so
> far:
>
>   - infinite scroll seems to reliably duplicate log entries when
> long-running requests are involved. Very confusing.
>   - infinite scroll sometimes claims no new logs exist even when we are
> looking at them in the old logs viewer
>   - expand all button doesn't actually expand all: I still see "show more"
> links at the bottom of every log entry
>   - "Save As" does not work correctly after expanding a logs entry using
> said "show more" link (probably because the page's URL is not modified, but
> that's just a guess)
>   - limit param in url for fetching more than 100 results at once is not
> supported
>
> These are just a few things that I have noticed the new logs viewer breaks
> relative to the old one (And I use the latest Chrome stable on Win 7, so I
> doubt my browser is the issue). And, I'm sure there are more regressions
> that I haven't discovered yet.
>
> The one thing I like about the new viewer is the default "fully collapsed"
> view. Seeing more requests at a glance is handy and that would be a nice
> backport to the existing appspot logs viewer. But is it worth dealing with
> all of the above problems for this one new useful feature? Not hardly!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-appengine.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: "One senses GAE is just not a major priority for Google"

[Vinny P]

On Fri, Nov 7, 2014 at 10:17 PM, Brandon Thomson 
 wrote:

> Fixing bugs in legacy code is not exciting work and a new generation of
> engineers at Google may be tempted to "improve" things that aren't broken
> instead of doing the hard work of maintaining the existing code.
>


+1. New is not necessarily better. To go on a minor tangent, I liked the
older Google Groups UI better than the current version.


On Sat, Nov 8, 2014 at 2:56 PM, Kaan Soral  wrote:

> pdknsk has a nice point, you must be on a high support level :)
>


And +1 as well.  A paid support contract gives the App Engine unicorns some
extra pep in their step :-)



-
-Vinny P
Technology & Media Consultant
Chicago, IL

App Engine Code Samples: http://www.learntogoogleit.com

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Bug in ndb with StructuredProperty?

[Vinny P]

On Sat, Nov 8, 2014 at 7:44 AM, Lapteuh  wrote:
>
> I tested this code
> . First again,
> *required* parameter ignored, but it must be composable (It is written in
> the documentation). Second, *validation* in *StructuredProperty* work
> only on *not None* value and it's second bug, because writing custom
> property for model useless at this point.
>



I think you might be missing Tim's point. FirstModel will be validated, but
the inner SecondModel isn't being validated - it's serialized directly as a
property. You can see this because the pre-put and post-put hooks you
defined for SecondModel aren't being run (at least, I don't see the correct
log lines after line 64 in your Github gist).

If you want SecondModel validated, try to put it directly as Tim attempted
to do in his post (and received the correct error messages).

Now as for the larger question you asked in the OP, this might be something
that should be clarified in documentation, but I don't think it's
necessarily a bug. If you need this style of validation to work in your
app, you can try explaining your use case and there may be workarounds we
can try.


-
-Vinny P
Technology & Media Consultant
Chicago, IL

App Engine Code Samples: http://www.learntogoogleit.com

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.