Viewing a single comment thread. View all comments

ckperry t1_j8xfzm2 wrote

[edit] This is fixed now. The prices shown in DK were incorrect, but afaict all users were charged correct amounts. If I'm wrong and someone was charged incorrectly, they can reach out at colab-billing@google.com

Hi, I lead product for Colab. Thanks for flagging. This is clearly a mistake and we're looking into how it slipped through our testing.

We'll get this fixed asap and proactively issue refunds to anyone impacted. We haven't changed prices for Colab Pro.

Sorry about this. If you hit weird things in the future, I'm @thechrisperry on twitter (I check that a little more religiously than reddit where I mostly lurk).

284

FreePenalties OP t1_j8xrm5m wrote

Thank you very much for the response, will edit the post to be less alarmist. Would also like to just say thank you for making a great platform for data science collaboration, and also for finally bringing pro to scandinavia :D it is a great value product and im very happy to pay 9 euro for it, but 94 would definitely have been too much.

45

ckperry t1_j8xtufq wrote

lol please do complain very loudly if we 10x your prices! and thank you!!

in this case it appears only the messaging was affected, and nobody was charged the 94 euros thankfully. I'll update when we get our page fixed. thanks again!

48

Appropriate_Ant_4629 t1_j8y3koe wrote

> Hi, I lead product for Colab.

Thanks for your responses here!

And thank google's management chain above you for allowing you to represent the product here.

Your comments here just saved a number of subscriptions that would have otherwise canceled.

33

ckperry t1_j8yhh4f wrote

Thanks! Though a lot of thanks to my buddy in Google Brain who saw this thread and pinged me this morning :)

18

DigThatData t1_j8xxnpp wrote

unrelated to OP: what is the "best practice" method for a notebook to self-test if it's running in a colab environment? i think the method I'm currently using is something like

probably_colab = False
try:
    import google.colab
    probably_colab = True
except ImportError:
    pass

which I'm not a fan of for a variety of reasons. what would you recommend?

5

ckperry t1_j8ygjep wrote

[edit] I give up on formatting

We've never really worked on a foilproof way to detect if you're using Colab, but this might work a little better for you:

import sys probably_colab = False

if 'google.colab' in sys.modules: probably_colab = True

11

Captain_Cowboy t1_j8z1lv4 wrote

Maybe a little easier:

import sys
probably_colab = 'google.colab' in sys.modules
12

daking999 t1_j8yao4j wrote

Oh nice. Please can you get invoice based billing set up so I can have my university pay for my students' Colab subscription!

3

ckperry t1_j8ygy9m wrote

I was so close to getting this and then our partner team got hit by layoffs which set us back. Hoping before next school year to have something (not perfect), but we'll see.

8

daking999 t1_j91mtko wrote

Good to hear, thanks. That's when I'm teaching next so would be great. It's a fantastic resource for teaching ML but frustrating when students hit the GPU cap. My university also won't let the students pay for Colab Pro on their .edu google account themselves, some legal nonsense. Some of them end up paying on their personal google accounts but then it's awkward needing to share the notebooks again (and I feel bad about the students paying when it should really be the school).

1

ach224 t1_j8ywbup wrote

I have been using colab for ML training big models. It is a good product. Would love a more straightforward integration with my proper python modules. I end up having to update my libraries on my local, pushing to gh, then refresh/restart the colab kernel. Would love a better way to run my python module in -e mode. Thanks.

2

phobrain t1_j904xfl wrote

Bonus for the bug report? Think of all the effort and adrenaline that went into this.

1