Status Update
Comments
sp...@google.com <sp...@google.com>
di...@google.com <di...@google.com> #2
Our business model requires a higher traffic during this time of month, which is why we have seen the err - maybe the error appeared even before.
If the user re-tries ( using the same credentials ) the same action couple of minutes after , it is working.
Please advice.
as...@pakdata.com <as...@pakdata.com> #3
Hello,
As the example shown in the video is testing the connection multiple times in a row, has it happened by testing the connection once (or until it succeeds), then running the code and queries needed and after a while trying to connect again? Is it still failing?
Regards.
as...@pakdata.com <as...@pakdata.com> #4
We have also noticed that sometimes if we refresh the Google Sheet file, from where the INSERT is fired , using the JDBC connection , we are able to connect and insert the records.
Last year we have had a similar issue due to a rollout of some changes on JDBC class ( related to Issue # 28402227 )
Following the discussions with your developers , they did a rollback which fixed the error and we were able again to use the mechanism.
I guess now there is another rollout related to JDBC ?
Or what is the reason of this issue happening suddenly and randomly?
di...@google.com <di...@google.com> #5
It connects intermittently and when it doesn't, it stays 30 seconds connecting until the error is thrown.
I tell my users to try to run the code over and over again, until they finally connect.
as...@pakdata.com <as...@pakdata.com> #6
Hello,
Thank you for your comments, this has been forwarded internally.
Regards.
di...@google.com <di...@google.com> #7
I have the same issue, getting this error "Failed to establish a database connection. Check connection string, username and password." around 30% of the time.
We are getting frequently below error.
Error : Failed to establish a database connection. Check connection string, username and password. at __GS_INTERNAL_top_function_call__.gs:1:8
Please fix this issue ASAP
it...@pakdata.com <it...@pakdata.com> #8
Our deployment is experiencing the same issues, spiking on August 1 -- by August 4 we realized that our allowlist in Cloud SQL lacked a few critical subnets. That was completely a problem on our end.
After fixing it, the connection error rate dropped to the ambient level of less than 45k/day. On August 12 we tracked only ~3k errors, but after that connection errors have been on the rise again, reaching 125k failed connections just yesterday (Aug 16).
I understand that the issue has already been reported internally. But I hope these additional time references will be helpful.
Thanks
it...@pakdata.com <it...@pakdata.com> #9
Hello,
In order to move this investigation forward our product engineering team may need sensitive data, therefore Issue Tracker is not the best environment (public) to do so.
This is why I strongly encourage you to reach out to your admin to open a ticket to
If you have any additional questions, please feel free to reach out.
Kind regards.
jc...@gmail.com <jc...@gmail.com> #10
We are getting frequently below error and unable to use the application -
Error : Failed to establish a database connection. Check connection string, username and password.
lu...@gmail.com <lu...@gmail.com> #11
lu...@gmail.com <lu...@gmail.com> #12
as...@pakdata.com <as...@pakdata.com> #13
ku...@google.com <ku...@google.com>
ku...@google.com <ku...@google.com> #14
Can any one help on this, incase found any solutions
as...@pakdata.com <as...@pakdata.com> #15
A few days ago I've updated the whitelist based on this document:
ku...@google.com <ku...@google.com> #16
The DB we are connecting to is an AWS RDS database. So far, no signs of trouble with the database itself.
I don't see what I can do to improve the experience (apart from migrating the app). Any insights?
ku...@google.com <ku...@google.com>
ku...@google.com <ku...@google.com> #17
One behavior I noticed was when I caught the error in error handling and tried to reconnect in the same code execution it would fail 100% of the time. So my work around ended up writing code that if the execution was from a trigger to create a new trigger to run the code and that seems to work. If the execution was from a menu I would simply alert the user to re-try.
ku...@google.com <ku...@google.com> #18
Please use enabledTLSProtocols=TLSv1.2 instead of useSSL=false, Hope it will work.
Description
After last update large webp images takes up half of coding area. Please fix.
ATTACH SCREENSHOTS/RECORDINGS OF THE ISSUE
ATTACH LOG FILES (Select Help > Show Log in Files, or Show Log in Finder on a Mac)
------------------
IMPORTANT: Please read
all required information.
------------------
Android Studio Electric Eel | 2022.1.1
Build #AI-221.6008.13.2211.9477386, built on January 11, 2023
Runtime version: 11.0.15+0-b2043.56-8887301 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 11 10.0
GC: G1 Young Generation, G1 Old Generation
Memory: 4096M
Cores: 16
Registry:
external.system.auto.import.disabled=true
ide.text.editor.with.preview.show.floating.toolbar=false
Non-Bundled Plugins:
dev.polek.adbwifi (1.2.5)
org.intellij.plugins.markdown (221.5787.39)
Studio Build:
Version of Gradle Plugin:
Version of Gradle:
Version of Java:
OS: