Reputation
Badges 1
125 × Eureka!right, and why can't a particular version be found? how it does it try to find python versions?
Is this a possible future feature? I have used cometML before and they have this. I'm not sure how they do it though...
Hey AgitatedDove14 , thanks for the answer. What does that mean? In any case I think it would be a nice to have feature.
Ah, so you're saying I can write a callback for stuff like train_loss
, val_loss
, etc.
Absolutely, I could try but I'm not sure what it entails...
Hey AgitatedDove14 , did you get a chance to look at this?
And then you'll hook it
Ok gotchu. I'll do that as soon as I can.
I have this inside my pipeline defined with decorator
(base) emilio@unicorn:~$ docker version Client: Docker Engine - Community Version: 19.03.13 API version: 1.40 Go version: go1.13.15 Git commit: 4484c46d9d Built: Wed Sep 16 17:02:36 2020 OS/Arch: linux/amd64 Experimental: false (base) emilio@unicorn:~$ docker-compose --version docker-compose version 1.17.1, build unknown
Yeah, that would be nice!
i'm just interested in actually running a prediction with the serving engine and all
some documentation for understanding the parameters, flags, options etc.
I want my serving controller to go into a particular project instead of the default DevOps, for example
Other things might be programatically adding endpoints instead of using cli (this is because I potentially have hundreds of models to serve so I can't do this manually)
but it's been that way for over 1 hour.. I remember I can force the task to wait for the upload. how do i do this?
I have done this but I remember someone once told me this could be an issue... Or I could be misremembering. I just wanted to double check
hi SuccessfulKoala55 ! has the docker compose been updated with this?>
Hi SuccessfulKoala55 , do you have an update on this?
instead of, say, the binary the task was launched with
I can do curl
http://localhost:8080 but it's a remote server so unless I do X forwarding I can't browse it
I understand! this is my sysadmin message:
"if nothing else, they could publish a new elasticsearch image of 7.6.2 (ex. 7.6.2-1) which uses a newer patched version of JDK (1.13.x but newer than 1.13.0_2)"