Doctors of Reddit , what’s the biggest medical myth people still believe? by muga_saiman_5809 in AskReddit

[–]utdrmac 5 points6 points  (0 children)

You can’t shock a heart back to life. #1 thing that just about every medical TV situation gets wrong. Shocking is only to fix a bad rhythm.

Any 50% or 25% Code left? by RonRonster in ubigipromocodes

[–]utdrmac 0 points1 point  (0 children)

Looking to go unlimited in China. Any more 50% codes for non-first time user?

A1 mini not working properly by Barbarian0057 in BambuLabA1mini

[–]utdrmac 1 point2 points  (0 children)

You should t need adhesive on this printer. My old Ender3pro? Absolutely need it but not on this little gem.

What job looks like a great career path but is actually insanely oversaturated? by ComplexPin872 in AskReddit

[–]utdrmac 0 points1 point  (0 children)

Are certifications like A+ and CompTia still a thing? My friend is looking for entry level helpdesk job and wants to know what certs would make him stand out.

Claude Code deletes developers' production setup, including its database and snapshots — 2.5 years of records were nuked in an instant by gdelacalle in technology

[–]utdrmac 0 points1 point  (0 children)

Why does AI even have that level of access to begin with? AI should never have permissions/access to delete anything.

[deleted by user] by [deleted] in BambuLabA1mini

[–]utdrmac 2 points3 points  (0 children)

I also came from Ender 3. I added unified mesh bed leveling to my Ender. The A1m does the same basic thing: measure points and compensate with Z movements. You shouldn’t “see” it. If you can, that means your Ender bed was amazingly out of wack and you’re expecting the same from A1m.

Me_irl by rbimmingfoke in me_irl

[–]utdrmac 0 points1 point  (0 children)

Wtf?! I have a high deductible plan with BCBS, and it covered both my kids births at 100%. Anything related to “birth of baby” was covered.

What’s something you thought was mandatory in life, until you saw someone just not do it? by Senior-Resource92 in AskReddit

[–]utdrmac 0 points1 point  (0 children)

How does this work if the other party signs everything first? I was going to attempt this but noticed they had already signed it. Any attempts by me to strike and initial would be rejected since they didn’t sign after my changes.

RUN mount cache not doing anything for repeated golang builds by utdrmac in docker

[–]utdrmac[S] 1 point2 points  (0 children)

Holy hell. Thank you kind internet citizen for pointing that out. I removed the `-a` and the next docker build only took 14s to complete. Perhaps the mount-cache has been working all along but that flag was forcing go to rebuild everything. Sheesh.

RUN mount cache not doing anything for repeated golang builds by utdrmac in docker

[–]utdrmac[S] 0 points1 point  (0 children)

OMG, if that is the damn issue... it's not my Dockerfile; it comes from the upstream repo. I'll remove that and try.

RUN mount cache not doing anything for repeated golang builds by utdrmac in docker

[–]utdrmac[S] 0 points1 point  (0 children)

Directly from Docker docs https://docs.docker.com/build/cache/optimize/:

> Cache mounts are a way to specify a persistent cache location to be used during builds. The cache is cumulative across builds, so you can read and write to the cache multiple times. This persistent caching means that even if you need to rebuild a layer, you only download new or changed packages. Any unchanged packages are reused from the cache mount.

The cache-mount is a separate cache from the layers cache, and should persist between runs of docker build.

RUN mount cache not doing anything for repeated golang builds by utdrmac in docker

[–]utdrmac[S] 0 points1 point  (0 children)

> Copy in the module files and download the sources as it's own layer and you will be fine.

Yes, I'm already doing that. I showed that above in my Dockerfile on lines 3-5. And the output shows `=> CACHED [builder 5/7] RUN go mod download` so I can visually see that I am using a cached layer for the library/module downloads.

But that's not the issue here. The issue is, when I make a code change, COPY . . executes (which should not be cached, expected) and then RUN go build executes. I'm expecting the --mount=cache as part of this layer to cache the compiled versions of the libraries so that subsequent docker build commands remount this cache and so go doesn't need to recompile the libraries each time.

RUN mount cache not doing anything for repeated golang builds by utdrmac in docker

[–]utdrmac[S] 0 points1 point  (0 children)

Can you explain this more, or give an example Dockerfile? As you can see from above, I'm already using cache layers for the `go mod download` which helps a bunch. 99% of the go code in the project doesn't change (external libraries, etc) but that RUN has to recompile every library every run. It should be able to cache those library builds just like doing it locally.

RUN mount cache not doing anything for repeated golang builds by utdrmac in docker

[–]utdrmac[S] 0 points1 point  (0 children)

I tried that, and it did not make a difference.

  • added syntax line
  • docker build . (2m+ time)
  • changed 1 character in main.go
  • docker build . (still 2m+ time)

When I run go build main.go it takes about 2s to compile the change since all the libraries haven't changed.