samsja
samsja
@zac-li I will investigate, it could be either a bug in the implementation or a wrong usage of the query
Putting this as priority since @florian-hoenicke might need such a metrics for defining alerting in jina-now
Link to track the Debian issue * https://security-tracker.debian.org/tracker/CVE-2022-1586 * https://security-tracker.debian.org/tracker/CVE-2022-1587
closing this PR has the bump in protobuf version has been handled in this PR: https://github.com/jina-ai/jina/pull/5082
Any news ?
>Client: I do not think this is feasible, also for other clients we may not have access to this information >Module: I am sure we can have the module, not...
> > surely we can only the format handler in Jcloud. However, this issue is about the jina executor logs output is not structed and we or users is very...
Hey @hsalehgh there is definitely something going wrong 14 seconds is not at all expected. We usually have great performance depending on which Executor your are using. Nevertheless I can't...
Are you using a GPU to compute the embedding ?