Useless Thread MDCCCLXXXV: Pat McAfee Appreciation Thread

Status
Not open for further replies.
I'm two pages late, but @John Price having a "coding room" is wild as f***
yes I'm in it now.

PXL_20240124_154957160.jpg
PXL_20240124_155024426.jpg
PXL_20240124_155035196.jpg
PXL_20240124_155045050.jpg
PXL_20240124_155101658.jpg
 
Last edited:
yes I'm in it now.
what are you working on

i'm trying to improve our infra deployment scripts - i'm going to be writing some terraform goodies here over the next couple weeks.

no idea what i'm doing. never used terraform, so that'll be fun.

pretty boring working on bash scripts, NGL
 
what are you working on

i'm trying to improve our infra deployment scripts - i'm going to be writing some terraform goodies here over the next couple weeks.

no idea what i'm doing. never used terraform, so that'll be fun.

pretty boring working on bash scripts, NGL
had some technical issues logging in but that's fixed now
 
  • Haha
Reactions: Sega Dreamcast
Yes..........I have a computer here right now too. And I can 100% assure you I'm NOT "coding". So how about you just answer Mr. Fisherman's valid question and tell us what "coding" you are working on today. 🖥️

lol hard to answer i guess

coding without a project is impossible, so i don't really blame him. purposeless work is a total mood killer
 
  • Like
Reactions: PanthersPens62
Code:
{"@t":"2024-01-24T16:30:26.1373976Z","@m":"Unexpected Execution Error","@i":"f7f96a18","@l":"Error","@x":"ClickHouse.Client.ClickHouseServerException (0x000000F1): Code: 241. DB::Exception: Memory limit (total) exceeded: would use 3.61 GiB ││  (attempt to allocate chunk of 4662550 bytes), maximum: 3.60 GiB. OvercommitTracker decision: Query was selected to stop by OvercommitTracker.: While executing AggregatingTransform. (MEMORY_LIMIT_EXCEEDED) (version 23.11.2.11 (official bui ││ ld))\n\n   at ClickHouse.Client.ADO.ClickHouseConnection.HandleError(HttpResponseMessage response, String query, Activity activity)\n   at ClickHouse.Client.ADO.ClickHouseCommand.PostSqlQueryAsync(String sqlQuery, CancellationToken token)\ ││ n   at ClickHouse.Client.ADO.ClickHouseCommand.ExecuteDbDataReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)\n

this should be exciting
 
I wish these f***ing plastic chair mats didn't break so much

@LarryFisherman you work from home show your chairmats

How do they not fracture

dents and divots all over, f***
 
Code:
{"@t":"2024-01-24T16:30:26.1373976Z","@m":"Unexpected Execution Error","@i":"f7f96a18","@l":"Error","@x":"ClickHouse.Client.ClickHouseServerException (0x000000F1): Code: 241. DB::Exception: Memory limit (total) exceeded: would use 3.61 GiB ││  (attempt to allocate chunk of 4662550 bytes), maximum: 3.60 GiB. OvercommitTracker decision: Query was selected to stop by OvercommitTracker.: While executing AggregatingTransform. (MEMORY_LIMIT_EXCEEDED) (version 23.11.2.11 (official bui ││ ld))\n\n   at ClickHouse.Client.ADO.ClickHouseConnection.HandleError(HttpResponseMessage response, String query, Activity activity)\n   at ClickHouse.Client.ADO.ClickHouseCommand.PostSqlQueryAsync(String sqlQuery, CancellationToken token)\ ││ n   at ClickHouse.Client.ADO.ClickHouseCommand.ExecuteDbDataReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)\n

this should be exciting
I only know the very bare minimum things about coding, so how would one go about getting rid of a memory error? Is that a code based thing, as in parts of the code need fixing somewhere to where it won't run as many things as before? Or is that more towards what it is trying to push to that needs fixing?
 
Status
Not open for further replies.

Ad

Upcoming events

Ad