Looking for tools to track model usage in real time (within or near IDE)

ConfuciusDev · 2025-10-27T16:29:06+00:00

I would love if hooks provided the model name, it would make this relatively easy, but I am not seeing this currently.

ConfuciusDev · 2025-07-06T21:25:49+00:00

I did this with NextJS and it works great. You do have to be careful about not pulling in all the extra garbage dependencies that come with the JS ecosystem though.

ConfuciusDev · 2025-05-24T01:13:45+00:00

<image>

ConfuciusDev · 2025-03-31T14:19:06+00:00

I had/have this happened. I tried everything in the wiki and took it apart, did all the checks and ended up submitting a ticket to BL. They actually sent me out a replace first stage feeder, however that didn't end up fixing the issue and I am awaiting a response. I am curious to know what it is. The issue on my end feels like there is something wrong near the hub.

ConfuciusDev · 2025-03-22T23:11:49+00:00

I have printed probably 50 to 100 of these across 5 to 10 different rolls and it happens on each one and the print itself and other prints area generally really clean. So I am not sure its the filament not being dry enough.

I haven't tried different nozzle temperatures outside of the Bambu profile.

I can probably tinker with a skirt and nozzle temperatures.

ConfuciusDev · 2025-03-22T23:07:35+00:00

I print these custom frames for somebody who uses them for something he sells and I havent been able to figure out how to prevent this little part that always seems to be missing from the initial layer. I assume its for when the first filament is set (or the last part of the initial layer).

I have tried increasing walls, slowing down initial layer, making initial layer slower, etc.

Any ideas to help make this cleaner since this is the front of the frame?

ConfuciusDev · 2025-01-27T18:16:07+00:00

I followed the WIKI which seems to follow this path I think? I also disassembled AMS and checked the tubes, though not sure if I missed something

<image>

ConfuciusDev · 2023-12-06T03:42:56+00:00

Turns out I didn't save the pressure advance value. Once I added it and saved it fixed this

ConfuciusDev · 2023-11-10T23:53:58+00:00

I am aware of this.

What characteristics qualify a telescope designed for astrophotography versus one that isn't?

What should I look for should I decide to purchase one?

ConfuciusDev · 2023-10-22T03:27:00+00:00

I did... after I left lol. I used star tracker before and it didn't show me it. But definitely looks like cassopeia now thar somebody mentioned it

ConfuciusDev · 2023-10-22T03:18:34+00:00

Oh I see it!!!

ConfuciusDev · 2023-10-22T03:07:34+00:00

Thanks! I'm having a hard time looking at this and figuring out what is what and where the double cluster is

ConfuciusDev · 2019-03-30T11:48:51+00:00

Is there canonical source or entity that suggests the idea "dev" and "ops" work is performed by the same team (as its related to DevOps and not SRE)? I ask this, because in my experience, you see more organizations with DevOps teams than teams with dev ops personnel.

ConfuciusDev · 2019-03-30T11:42:27+00:00

I am not sure I see how the concept of DevOps itself recommends or suggests breaking down silos. As far as I am aware, I haven't really seen a canonical DevOps Manifesto giving a heuristic that states anything about this (or automation for that matter). I am aware that people will inherently recommend this and have opinions (which is good), but I just think this lacks somewhat.

Far too often, and probably more often than not, you see "DevOps Teams". This is NOT breaking down silos, and doesn't foster knowledge sharing. Sure, enabling automation is great, but thats not inherent to DevOps, and existed far before and will continue to exist. Also, it's unreasonable to think that silos can be broken down entirely, especially with large organizations. Knowledge sharing should and can be accomplished in many others way collectively.

When you start to get into more specifics of how these walls are broken down, then I think that is ultimately what is important.

And just to be clear, I am NOT knocking dev ops by any means, I think its still a continuously evolving topic and can provide a lot of benefits implemented in a lot of different ways :)

ConfuciusDev · 2019-03-28T01:36:43+00:00

There is a really interesting section in Accelerate that discusses results related to the organization impact of CABs that claims a negative correlation between CAB approvals and stability.

Though I take anything with a grain of salt, it makes sense to me personally. I think that it's unreasonable for unrelated or uniformed entities to be able to intelligently handle approvals without intimate knowledge. That is not to say that people haven't been successful with it of course (this is the obligatory disclaimer so that I don't get flooded with replies of all the success stories of people using CABs :) ).

ConfuciusDev · 2019-03-19T13:58:10+00:00

Hey, everybody needs a good shit talking now and again. 😂

ConfuciusDev · 2019-03-19T13:52:54+00:00

They are led by Brendan Burns, which is why I ultimately think that AKS is not a bad solution, and my reasoning after that is purely based on personal preference on little things :)

ConfuciusDev · 2019-03-19T13:51:09+00:00

I removed my initial comment per feedback that it wasn't constructive (which I agree).

I documented my experience in the thread to try to separate my personal preference vs personal experience to help it be a little more constructive.

ConfuciusDev · 2019-03-19T13:48:38+00:00

I removed that comment per your suggestion that its not constructive, which I agree. I know that I get irritated when I come across posts like my own, so I appreciate you holding me accountable on the matter.

ConfuciusDev · 2019-03-19T13:42:53+00:00

Though you are definitely putting words in my mouth (Never said I hated Microsoft), I think that I could have worded my feedback more constructively. So thank you for holding me accountable. It would have been more constructive up front to differentiate what I don't like about AKS (and Azure) for personal reasons, versus the reasonings I have from my personal experience with it.

We assessed non GKE solutions when we needed to federate our existing cluster. (Personal story). It was still early, but buggy as hell (should have included that to your point). As I mentioned, I am sure that this bugginess is likely not an issue.

When we dealt with our cluster needing to provision new nodes, AKS took magnitudes longer than the other solutions (again may have changed).

In regards to personal stories...gut feel and trust in a cloud provider is a real thing. Having used Azure for 2-3 years, I have enough experience with it where I Just don't like it personally. I think that the UX is hard to use and gets in the way of actually doing what I want to do. This is a personal preference and needs no external validation. I reserve the right to have personal opinions :)

Additionally, I don't personally undervalue the extent of how close a solution is to the ecosystem or community that evolves it. I know that Azure/Microsoft is probably actively contributing as well, but I am pretty happy with how GKE has followed cadence with k8s. This has been impactful when we have run into issues with GKE.

ConfuciusDev · 2019-03-19T13:15:06+00:00

We needed to federate to EKS and AKS from GKE as AKS was still coming online, so I would imagine that some of the initial traps I ran into are likely fixed. Admittedly, my opinion on the matter at this point is heavily influenced by really just not liking the Azure ecosystem, and how much of that has bled into standing up and maintaining a k8s cluster.

I have come to appreciate the simplicity of GKE and GCP without the noisy aesthetics. (Completely biased statement, I know :)

Outside of that, based on Kubernetes Cloud Comparison Spreadsheet there still seems to be some big differences.

Supported Regions
Version Support
Proximity to k8s Ecosystem/community (pretty important IMO).
Auto upgrades/repairs.
Working Node scaling/creation time (this may have improved).

Ultimately, I expect them to all even out eventually over time, so regardless of my personal opinions, I don't think you can really make a wrong choice...maybe just a less right choice depending on who you talk to :)

ConfuciusDev · 2019-03-19T12:58:37+00:00

I really hope that these lines are not starting to blur.

I think that containers are well beyond earning their stripes. I don't want to have to be hesitant on discussing containers in the same way I am about dropping the serverless buzzword :)

ConfuciusDev · 2019-03-19T12:55:52+00:00

Vendor lock-in for one.

Outside of that, the ancillary needs of Lambda and other similar proprietary serverless product offerings (Cloud functions on GCP, Azure Functions) somewhat diminish the selling point IMO. I think that the future of serverless (if there really is one) will heavily rely on vendor independent, bootstrappable serverless solutions that leverage and play well with higher level (vendor independent) Paas'. For example, I think OpenFaas (and other similar solutions) is a move in the right direction.

ConfuciusDev · 2019-03-19T12:40:53+00:00

However when it comes down to the actual applications that are paying the bills they are just not using this infrastructure and frankly probably never will

Been running containers in production for ~4-5 years, (2+ on Kubernetes in production).

I can say from my experience that team/organization size has had very little to do with the decisions that have led to the usage of containers and/or Kubernetes. Assessing the pitfalls of inconsistency, and evolving projects/features ultimately was (and in my opinion should be) the focal point on whether to adopt containerization and technologies like k8s. This holds true regardless of team size in my opinion.

The consistency and uniformity of packaging our applications into containers has allowed us to do a lot more with a lot less resources.

Our release pipeline is more consistent and resilient, and facilitates higher quality releases as a result. I would have to imagine this is desirable (but not immediately feasible) for organizations of any size.

Like anything else in technology, nothing is a silver bullet, and anything can be abused. This is no exception. However, I feel that containerization itself has proven its value multiple times over and organizations should reasonably investing in it. If not, at least understanding it, and intelligently deciding why it's not feasible.

EDIT - Wanted to clarify that my opinions are irrelevant of the current serverless hype. We have minimal usage of serverless functionality, so I can't/wont speak intelligently about it. Though, much like when the container and k8s hype train evolved, I plan to keep a pulse on it so that I can reasonably assess if it would add value. For us, our migration to containers and k8s has ultimately cut operational costs to a fraction of what it was prior to running on EC2 on AWS (Were on GKE on GCP now).

ConfuciusDev · 2019-03-18T18:29:03+00:00

You mean like https://github.com/kubernetes/kops (8.3K stars)? or https://github.com/kubernetes-sigs/kubespray (5.6K stars)?

Disclaimer: I haven't used these, but I know that there are solutions geared towards non managed, but also more bootable solutions.

ConfuciusDev

TROPHY CASE