Well, I spun up a test server on GAE and it works fine with my app. So now
my best guess is that the problem is specific to OSX. Anyone else have a
mac to test on? I'm afraid I only have the one.
On Tuesday, May 2, 2017 at 6:26:45 AM UTC-7, Karoly Kantor wrote:
>
>
> Dear Massimo,
>
> As you
Dear Massimo,
As you are looking into this particular issue, may I please suggest that
you test it with a 2nd generation Google Cloud SQL instance? That would,
with the same effort, automatically address the issue I have raised
earlier. (Google declared 1st generation Cloud SQL instances
I guess if you can't replicate, the full error might be helpful:
ERROR2017-05-02 02:36:08,394 restricted.py:171] Traceback (most recent
call last):
File "/Users/sin/Dev/Trytha/web2py/gluon/restricted.py", line 216, in
restricted
exec(ccode, environment)
File
On Monday, May 1, 2017 at 6:09:42 PM UTC-7, webm...@trytha.com wrote:
>
> I could zip that up into an app if you like, but I can literally change
> any portion of that connection string and have it work in the old version
> of pydal and not work in the new version (in a completely fresh web2py
Ah, I think the reason he couldn't replicate it last time was because it
was a different error that he had already fixed. The SQL was broken during
15.x, I believe, then working for a very short period (1 day) during 16.03,
then broken again in a different way.
On Monday, May 1, 2017 at
I could zip that up into an app if you like, but I can literally change any
portion of that connection string and have it work in the old version of
pydal and not work in the new version (in a completely fresh web2py install
which I performed while I wrote the steps to replicate). This is also
The steps are kinda simple:
1. Install web2py:
git clone --recursive https://github.com/web2py/web2py.git
2. Move gaehandler.py and app.yaml into the web2py directory.
3. In the Welcome app, change the GAE connection string in db.py to:
db =
On Monday, May 1, 2017 at 4:30:59 PM UTC-7, webm...@trytha.com wrote:
>
> Here is the error from the current version of pydal when trying to connect
> to Cloud SQL (my memory is better than I thought):
>
> File "/Dev/Trytha/web2py/gluon/packages/dal/pydal/adapters/google.py",
> line 44, in
Here is the error from the current version of pydal when trying to connect
to Cloud SQL (my memory is better than I thought):
File "/Dev/Trytha/web2py/gluon/packages/dal/pydal/adapters/google.py",
line 44, in _find_work_folder
super(GoogleSQL)._find_work_folder()
AttributeError: 'super'
Ah, I think the problem might actually be slightly different, but the
solution is the same. If I recall correctly, the error I was getting said
something about super() not having a method called something like
_find_work_folder(). I can give you the exact error when I get home later
today.
Same problems as I detailed on this thread:
https://groups.google.com/forum/#!topic/web2py/XsSvnbGzzws
Basically, it seems like it was fixed and then immediately broken again.
The commit I mention above is the one where it was broken again.
On Monday, May 1, 2017 at 7:21:12 AM UTC-7, Massimo
Can you provide a quick summary of the problem you are having with Cloud
SQL?
I will make it a priority to fix it.
On Sunday, 30 April 2017 18:47:19 UTC-5, webmas...@trytha.com wrote:
>
> Figured this should have a new topic because it's been a year without two
> massive bugs being addressed.
12 matches
Mail list logo
