Assigned
Status Update
Comments
ll...@google.com <ll...@google.com>
ll...@google.com <ll...@google.com> #2
I have one question related to Google translate API. but it is not related to this issue.
When i am trying to access Google Translate API using javascript when the query string size is around 13000 characters i am getting server response error code 400. Can you please let me know what is the request size limit if any exist.
When i am trying to access Google Translate API using javascript when the query string size is around 13000 characters i am getting server response error code 400. Can you please let me know what is the request size limit if any exist.
da...@gmail.com <da...@gmail.com> #3
@vrames
according to Google API FAQ
The maximum size of each text to be translated is 5000 characters, not including any HTML tags.
according to Google API FAQ
The maximum size of each text to be translated is 5000 characters, not including any HTML tags.
ro...@google.com <ro...@google.com> #4
N/A
ty...@anz.com <ty...@anz.com> #5
I also have a same problem some html tags who are divided in few tags , and it's problematic .. there is some news about it ??
se...@subimage.com <se...@subimage.com> #6
I met with the problem just now, it seems the bug nof fixed yet.
da...@gmail.com <da...@gmail.com> #7
Update: I found the bug triggered not only by anchor tag, but also others. It seems that the problem is the context, and when I replace the tag with special symbol, 【】 for example, it worked.
In some context:
<a id="text">bla bla...</a> -> <a id="text">alb</a>alb<a id="text">...</a>
after change anchor tag to 【】,it worked:
【bla bla ...】 -> 【alb alb ...】
In some context:
<a id="text">bla bla...</a> -> <a id="text">alb</a>alb<a id="text">...</a>
after change anchor tag to 【】,it worked:
【bla bla ...】 -> 【alb alb ...】
Description
Problem you have encountered:
Cloud Functions lags (particulary) Go releases.
The platform recommends Go 1.16 (Feb'21) while Go 1.18 is imminent.
One of the major Golang APIs (Kubernetes) now prefers Go 1.17(.5)
Customers wishing to use Cloud Functions must remain on earlier versions of these APIs to avoid breaking changes.
Remaining on earlier versions of the API because of a platform dependency is:
What you expect(ed) to happen:
I expect Google to remain current on Cloud Functions runtimes (especially for its own runtimes, e.g. Go) and even if the runtimes were provided on a "developer beware" basis.
Truthfully, it's remarkable that there is such latency on the availability of these runtimes. It would be helpful if Google were willing to consider providing a roadmap for future runtime availability (and even better some insight into why currency is challenging).
Steps to reproduce:
I'm using the (otherwise excellent) Google Cloud Firestore Triggers . On a change event in a Firestore database, the code creates a Kubernetes client and mutates the equivalent Custom Resource in Kubernetes.
With
go.mod
:And:
Yields:
And this is because, in the standard library in 1.16(.12), the
reflect
package'sStructField
type does not have the method:Whereas it does since 1.17.1:
Downgrading k8s.io/apimachinery` to v0.22.5 succeeds:
go.mod
:And:
Other information (workarounds you have tried, documentation consulted, etc):