Lewdiculous (AetherArchitectural)

Lewdiculous

AI & ML interests

🔹https://arch.datasets.fyi | [Personal Profile] General tech and LLM stuff! https://beacons.ai/Lewdiculous | https://rentry.co/Lewdiculous | Mancer LLM Inference (ref): https://link.datasets.fyi/lwdmncr

Recent Activity

View all activity

Organizations

Blog-explorers's profile picture CyberHarem's profile picture LWDCLS Research's profile picture Social Post Explorers's profile picture AetherArchitectural's profile picture

Lewdiculous's activity

reacted to Nitral-AI's post with 🤯❤️ about 18 hours ago
view post
Post
2728
That moment when you spend 5 days up babysitting trains, only for colab pro + to randomly disconnect the environment at every chance with 0 error indication of any kind (it just disconnects without an error). Nuke the session from the interface, but continue to eat my colab credits while it reports to wandb. 0 way of saving the models when this happens since it nukes the code preset up to auto-execute. And since the sessions 'exist' but also at the same time doesn't exist i cant close it. And have to wait till they auto timeout after 24hrs. Guess, i won't be using colab for 'quick' test trains anymore. Thanks google for scheming the very little model training budget i had for the month.
·
replied to Nitral-AI's post about 18 hours ago
view reply

They managed to misidentify my subscription tier twice within the same email thread (quite the achievement).

Repeatedly suggested I purchase more credits, even though my issue had/has absolutely nothing to do with credits (a fantastic way to build trust and totally not come off as scammy).

Holy, this is unacceptable support quality for a paid service, not to mention the issue itself directly harming you by burning credits. Shameful.

reacted to Nitral-AI's post with 😔 about 18 hours ago
view post
Post
2728
That moment when you spend 5 days up babysitting trains, only for colab pro + to randomly disconnect the environment at every chance with 0 error indication of any kind (it just disconnects without an error). Nuke the session from the interface, but continue to eat my colab credits while it reports to wandb. 0 way of saving the models when this happens since it nukes the code preset up to auto-execute. And since the sessions 'exist' but also at the same time doesn't exist i cant close it. And have to wait till they auto timeout after 24hrs. Guess, i won't be using colab for 'quick' test trains anymore. Thanks google for scheming the very little model training budget i had for the month.
·

Update README.md

1
#1 opened 7 days ago by
woofwolfy