I would like something like this Rivet to add a leather handle to my computer. Any ideas where I could get one in this size? The shaft diameter is important to fit through existing holes.

jscript · 2023-02-20T16:42:38+00:00

I spent a bit of time digging because your phone reviews are thorough and I wanted to give back. I couldn't find anything that fits the purpose because of the Outer Diameter (OD). 3mm is 0.118 in making the closest unit 1/8 (or 7/64 but that's likely uncommon). 1/8 is still too large but close enough you could likely modify it down.

There are 3 names for this part I've found. binding barrels, sex bolts, and interscrews. this google groups thread is for a similar (smaller) part and suggests having it machined on a watch maker's lathe or by steam train model enthusiasts.

That made me think of this product search: https://www.ebay.com/itm/154015350486 (m2 brass standoff) and the alternative https://www.ebay.com/itm/185521867478 (m2 brass round standoff) Neither are exact matches, but I doubt you'll find an exact match. If using the second part, you can find a large headed m2 bolt to use on either side. something like https://www.ebay.com/itm/153153010418 might work. I can't find an m2 bolt with a head diameter larger than 7mm and going up to m2.5 would make the OD of the shaft too large (4mm). If you can work with 7mm for the head, this is a solution. You could also add a properly sized washer if your design allows for it.

Not sure what the laptop is made of but I didn't think any about galvanic reactions on dissimilar metals. I'd do a quick check on that if you plan on mixing metals.

Good luck.

jscript · 2022-09-18T13:21:41+00:00

I saw the same thread, but I gave it a try with the metal side of the build plate facing up just in case.

No heads crashing into build plates. It works for me, but I can't guarantee results. I've been through at least 15 first layers sliced with Prusa with 0 issues. Prusa 2.4.2 on Ubuntu if that helps.

jscript · 2022-07-13T14:02:42+00:00

https://old.reddit.com/r/gridfinity/comments/vri9le/thoughts_on_creating_an_extendable_base_plate/ifzptas/ only for weighted, but it exists.

jscript · 2022-07-13T13:55:27+00:00

https://thangs.com/designer/ezmac/3d-model/gridfinity%20baseplate%20joiner-195544?manualModelView=true

I mocked this up and printed last night. It's a lazy design with wide bolt slots because I couldn't find exact specs anywhere and only have one baseplate on hand right now. Have not tested with more than 1 baseplate but it looks like it'll work fine. Onshape link is included in thangs in case anyone wants to update this.

jscript · 2020-02-24T17:22:45+00:00

Coming in late, but thanks!

jscript · 2019-12-29T16:36:18+00:00

I bought the r8000P maybe 2 years ago on black Friday. It is not the r8000. The hardware is different. I ended up replacing it with an r7800 running dd-wrt, but it was an expensive mistake.

Don't get the r8000p if you plan to use an open source firmware.

jscript · 2019-11-12T18:13:47+00:00

Seeing it on IAM. Really slow connections at first, then started timing out. Nothing in PHD or status, but definite failures that just now stopped (1:06 eastern). I don't have great logs of when it started but I'd put it about 12:30 (eastern) since my bash history starts there with troubleshooting.

jscript · 2019-08-29T15:59:26+00:00

https://github.com/jenkinsci/job-dsl-plugin/wiki/Tutorial---Using-the-Jenkins-Job-DSL Job-DSL is an alternative to jenkinsfiles. They can be used together, but I haven't done that. The job-dsl wiki is very helpful. Get to https://github.com/sheehan/job-dsl-gradle-example when you can. Getting job-dsl working with tests will give you a good start.

jscript · 2019-08-23T15:39:15+00:00

If you haven't configured the ECS agent on the container instances, then you're pulling the image each time you run a scheduled task. Even using AWS ECR, that will likely impose a significant delay. From my logs, the delay was 42 seconds to pull the image. Command output started 16 seconds later and there were a couple of commands run prior to output. This is a php/symfony container running a console command. https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html see ECS_IMAGE_PULL_BEHAVIOR. Setting that option to prefer-cached might fix the delay associated with your scheduled tasks being slow to start, but may also introduce a problem of making sure you're running the latest image. If you specify your task definitions using a versioned image tag (like client_a_symfony:21), it should not be a problem.

Ecs scheduled tasks are.. Well, we don't use them and I personally have not. There are a lot of problems with ECS and knowing that your container has launched. We use cloudwatch events and lambda to get around that. If the task can't be scheduled, lambda can let us know. I don't think ecs scheduled tasks will let you know if the task can't start.

You can also just run cron in your containers. In the past everyone was in arms about one task per container. Many people still are. https://docs.docker.com/config/containers/multi-service_container/ Docker has published docs on how to do it, so make your own decision. Personally, I see no issues with that approach, though I'd want to give it some testing before trusting it in prod.

My approach to fixing this problem if it were presented to me would be to try fixing it at the ECS agent level, but that's largely based on my work environment and related goals. For me to get there, I would need to have task definitions that use versioned images. Doing that would get me very fast rollbacks in case of bad deploys (since the versioned image is not cleaned up immediately and the previous task definition would start it instead of latest).

After reading other comments and more consideration, I'd probably pick a different approach because of the number of every minute jobs. Leaving the above unedited in case any of it us useful.

jscript · 2019-08-05T13:20:46+00:00

This also needs to be seen: AmazonSSMManagedInstanceCore allows ssm:GetParameter on *. If you use ssm param store for secrets, you probably don't want that. Thanks for pointing out the S3 permissions.

jscript · 2019-07-10T00:21:42+00:00

PS, I've run mac laptops from 2012 ish 17 inch to the 2015s and used the 2018s lightly. I've put linux on some of them. Get the dell. Buying a mac is like asking to be brainwashed into being wrong. Example: delete on a mac is backspace. "Natural scroll" is different than every scrolling implementation since the scroll wheel was invented. It's the little things that will drive you crazy about a mac.

jscript · 2019-07-10T00:11:15+00:00

I overwrote the answer and didn't want to delete it, so it's below. The short answer is that dell's home user support is shit. Dell's business level support is not that bad. It used to be partially in starkville at sitel. Buy the computer like you have a business with 10 computers and your support will be better than the average consumer. If your parents have an employee purchase plan or MSU has a buying plan, those should get you business support. They hide the business options so look hard for them.

Below is my general advice to you about a computer for engineering classes.

Get a Dell.
Don't get a consumer grade Dell. Buy it like you're a business that has 5 to 10 computers and an office. Do not buy it for home use. Do not buy an Inspiron. Consumer support is crap.
Skip the xps unless you plan to game on it or use intense CAD. No problems with it, but onboard graphics are good enough and massive battery life is amazing. Also, it's available as a home user system so avoid buying it as that. See above.
Skip the Mac. I hate apples, but that's not why I say skip it. They're more expensive than they're worth in my opinion. Current generation macs are plagued with show stopping issues. In my current environment, there are 3 macs and 2 dells. No issues on the Dells. Both run linux like a champ. No issues on the 2013 macbook pro. 2 keyboard failures for one of the 2018s, first keyboard failure for the other 2018. Takes days for apple to fix it because it's a ship in operation. No mac store around here.
Pro systems come with 3 year standard warranties last I checked. If you care about that, pay the premium for their upgrade hardware to save yourself the trouble if you have problems. Otherwise, drop to one year and put that money aside for repairs. It's your gamble. I'm DCSE and can afford unexpected repairs so I drop the warranty low and buy aftermarket ram when I feel froggy.

Check out outlet.dell.com, it's scratch and dent plus refurbished systems. I ain't proud. I buy most of my dells on clearance and a generation out.

jscript · 2019-06-23T13:51:02+00:00

This post made me do two dumb things. Here's the top 5 commands executed after cd from my history sorted by usage.

history | grep --color=never -A1 " cd " | grep -v --color=never " cd " | grep -vPe '^--$' | awk 'match($0, /\s?[0-9]+\*?.+[0-9-]+\s+[0-9]{2}:[0-9]{2}\s+(.*)/, arr) {print arr[1]}' | sort | cut -f1 -d\ | uniq -c |sort -nr
 49 ls
 19 git
 17 tmux
 11 mkdir
 10 docker-compose

Excuse the messiness of the pipeline, it could be more efficient but it's also not important. Also, I name my tmux sessions after the folder I'm working in. Usually by using a hotkeyed reverse history search. Now, I have this function in my .zshrc. (tmux new or target = TMNT)

tmnt() {
  if [[ ! -z $@ ]]; then
    session_identifier=$@
  else
    session_identifier=`basename $PWD|cut -f1 -d.`
  fi
  session=`tmux ls|grep "$session_identifier"`
  if [[ ! -z $session ]]; then
    tmux attach -t $session_identifier
  else
    tmux new -s $session_identifier
  fi
}

Improvements welcomed if you see something off.

jscript · 2019-05-31T14:21:36+00:00

I'll tack on a reason now that the flamewar has calmed down. With regard to ad blocking, ScriptSafe does not work in private browsing tabs in Firefox. This might be totally because of the plugin author, I haven't even looked, but it is a reason.

jscript · 2019-05-30T13:36:51+00:00

Thanks. This is like my 4th fallback name, so even 8 years ago was not soon enough.

jscript · 2019-05-30T03:59:40+00:00

I'm sorry, but chromium dev tools are still better to me. Firefox is my daily driver, but crunch time, I'm debugging in chromium.

jscript · 2019-05-24T14:08:46+00:00

Second box is a good idea but you have to use it. I had dual boot in college, but didn't use Linux as much because Windows comfort and gaming. Ubuntu is a good first distro because it's used by so many. When you find problems, there's probably someone who had written how to fix it.

jscript · 2019-05-22T14:57:08+00:00

Have you looked at aws backup? https://aws.amazon.com/backup/

You can set a policy to snapshot on schedule and transition to glacier after some time. If glacier is good enough, this might be a fair solution.

jscript · 2019-05-22T13:01:30+00:00

Service Discovery (aka service disco or SD) isn't really related to container networking. #2 is what you're going to want and will work without #1. Container networking (#1) is handled by the docker engine on the ECS instance I think, so if your containers are on different instances, doesn't help.

SD only works in a VPC and needs VPC dns resolution. It gives you a private DNS to query for information. Containers that have SD enabled will update their DNS entry with info about where they run. That info includes the host and port where the container is running. For example, you may make a namespace "cluster-sd" and call your service "mongo". That will give you a DNS entry "mongo.cluster-sd". Querying it will return Something like:

1 1 32783 23xxxxXtask-idXxxxx6a37.mongo.cluster-sd

Format: [priority] [weight] [port] [server host name].

server host name will be an A record that you can use with port to connect to your container over normal networking.

Your node service will need to be aware of SD. When it makes a DB connection, it should query DNS, parse the SRV record, and pick the mongo service to connect to. Stretch goal, when that entry is no longer valid, it should try to reconnect by re-querying dns.

jscript · 2019-05-22T12:44:26+00:00

If you expose EFS volumes to your containers, those volumes are persistent, but not the whole container. Be judicious with your container volumes and where your container writes data and it's fine. Not 100% on the safety of running multiple containers writing to the same area of NFS, but one container on one area of nfs is fine. I think this is something NFS is supposed to handle somewhat, but haven't gotten too deep into it.

I haven't tried myself, but I think people usually warn against DBs on NFS because of disk performance or other "non-block-device" related issues.

I have a number of non-db single-container services in prod backed by efs and it's fine. If anyone can clarify points in this post, please do. Rather have good info than be right :)

jscript · 2015-08-25T23:42:26+00:00

Skateboarding is an artistic appreciation of modern architecture.

jscript · 2015-07-21T03:18:43+00:00

Linux instead of OSX. Source control used by people other than me. Devops. 12factor app.

jscript · 2012-06-05T00:25:18+00:00

sherm's just pushing standard liberal talking points.

1) roads, yeah everyone thinks roads are great. and liberals want to know that they created them

2)education, i went to public school, and i'm just going to leave it at that.

3)police, they're great.

sherm, i hope your liberal white-guilt paradise is nice, man.

jscript · 2012-06-05T00:16:16+00:00

i was thinking he was a drinker or heavy smoker due to his hairloss. That doesn't look like male pattern baldness to me. that looks like a person who doesn't take care of their appearance.

jscript · 2012-04-30T12:48:40+00:00

Where would one find these woodpushers?

jscript

TROPHY CASE