I have run into this issue multiple times with Nomad. For some reason, when jobs are redeployed/restarted, the service registration isn’t removed. This causes my Traefik reverse proxy to send requests to a non-existing allocation in Nomad.
Last time this happened, I think I completely nuked the Nomad setup and setup everything from scratch. This time around, I finally figured out the right way to do things.
Use nomad service list to get a list of the services
The use nomad service info -verbose <service_name> to get the service registrations for the app having the issue.
Open the UI and click on the Job > Services and click on the allocations to identify the dead allocation
Note the allocation ID and get the corresponding ID from the service info
Finally, remove the ghost entry with nomad service delete <service-name> <ID>
Change the Policy of the role applied to the user. Since I have a single person instance, I just needed to update the default Policy Template from the Control Panel
Go to Control Panel
Click Roles
Either change the “Role Template” if you have no roles defined, or edit the role governing the users for whom the limit needs to be changed.
4. Their “Roles” page should show the new limit under driveCapacityMb and also their “Drive” page in Basic Settings
Getting Pyenv and Pyright to play nice in python-mode on Doom Emacs requires sticking to a few rules. I discovered these after multiple attempts of trial and error. All the following things might not be needed. But I got things to work only when I set all of these up.
So, best advice is – start here and try to reduce it down.
Emacs Config
Edit your .doom.d/init.el
Enable both lsp and tree-sitter in the tools. tree-sitter is not probably needed for this. But, I wanted to use it, so.
Enable python mode with (python +lsp + tree-sitter +pyenv +pyright)
Then run ~/.emacs.d/bin/doom sync and then ~/.emacs.d/bin/doctor to ensure the required tools are available.
Setting up your Python Env
Add your project as a Projectile project using SPC p a
Now if you have read the Projectile script you would have noticed that the “pyenv mode” sets the name of the project as the Python environment name. So, if you like me use pyenv-virtualenv to create multiple virtual environments, then create your virtualenv with the same name as your project and install the dependencies within that virtualenv. For example,
# project name is awesome-sauce
cd awesome-sauce
pyenv virtualenv 3.11 awesome-sauce
pyenv local awesome-sauce
pip install -r requirements.txt # or any way you want to setup the dependencies
This will create a local .python-version file with the virtualenv name. This file seems to be crucial in getting the pyright to work. I tried multiple times without this file and just using pyenv shell <env> to activate the env and install the dependencies. And when I loaded up a file in Emacs, pyright would complain that none of the dependencies were available for import.
Results
With all of this setup clearly, now I get autocompletion for dependencies installed via pip as expected, and syntax checking is happening as I type.
Notice that in the modeline, pyenv has loaded the correct environment and the LSP is also using the same one (the blue Python awesome-sauce).
I can now also run my tests quickly using SPC m t t using pytest.
Finally – a request
There’s a big chance that I might have missed something while documenting this. In case you are trying to achieve the same setup, but these rules aren’t sufficient to get things working for you, kindly drop a line.
Let’s say you set up Doom Emacs from scratch for the first time, and you followed the instructions correctly and install the all-the-icons fonts when prompted, saw the icons properly displayed in the dashboard (launch window), but once you open a file, the status line starts showing random characters, instead of icons.
You need to install nerd-icons using M-x nerd-icons-install-fonts because the doom-modline has switched from all-the-icons to nerd-icons
I listen to podcasts while doing chores like cooking, travelling in public transport, doing dishes…etc., In most cases, I just absorb what I can with the partial attention I provide to the podcast. Recently I thought, I would listen to some of them with a bit more attention, like a lecture and take some notes. I learnt a lot in this one from how EV range anxiety is a non-problem to wineries hedge their quality of wine my mixing grapes from different fields.
Introduction
This one is a conversation between Bloomberg Opinion columnist Barry Ritholtz speaks and Darren Palmer, Ford Motor Co.’s vice president for electric vehicle programs. They take about Darren Palmer’s professional journey in Ford and Ford’s electric vehicle lineup and the future of Ford and Electric vehicles.
Ford Electric Vehicles
11 Billion starting investment
50 billion in current investment
use lessons from startups for velocity of execution
travelled to EV rich countries like Norway to China to learn
Interesting case where an EV user declined 100% refund of the EV vehicle and a BMW car to get rid of the EV and switch to petrol car, because he was holding the future and he doesn’t want to go back
focus on millennial market + Mustang brand
lack of Operating System is what was the limiting factor once the design was completed
using web technologies for creating the interface provided the team with great velocity
UI was hosted by a developer sitting at home, which was live updated during a test run based on customer complaint
from the first day, social media is being watched and feedback followed up
Team Edison – has a very flat structure
Ask what they want and move out of their way
fast track approvals and let them do their jobs
Converting Petrol Heads
Mustang club wasn’t comfortable and said they won’t be endorsing the EV Mustang
end of the launch presidents of both the Mustang clubs had purchased multiple vehicles
realisation – EV provides complementary experience with Petrol vehicles
petrol heads are not petrol heads, but performance heads and electric vehicles can deliver better performance
EV Mustang has such a performance that the only thing needed to be done to convert a person into EV is just getting them into the EV vehicle
tests for the vehicles are no longer done with humans because the acceleration limits are too high
torture tests for Ford vehicles on YouTube
E Transit – Vans
Focus on commercial customers
Payback starts from day 1
running costs are about half
extra mileage is limited because of predictability of routes – so EV mileage anxiety is not an issue
trips are planned and executed with right charging window
only 10% of our market
everyday seeing new use-cases in the commercial sector
Use-case #1: French Winery
wineries collect grapes from different parcels of land and mix them to get an average better wine (if 1 of 3 is bad), they still get a decent wine because of the 2 good parcels
but they don’t know if they have had 2 of 3 bad until a year later when they pull samples from the vats
a winery wanted to get the best quality and decided to use 1 vat per parcel, so at t
vat sizes are big and restriction on building above ground, so winery built the vats under ground by a mountain side
used the diesel vehicles for transportation
converted entire fleet to the electrical after seeing electrical performance
talks to American group of wine makers
now there is a huge demand from the wineries for electrical vehicles
USE-CASE #2: Mobile kitchens
popup kitchens with electric equipment
uses the battery to drive to people’s homes, plug-in and start cooking
battery operated electrical vehicles can use the battery to power the kitchen
BlueOval Charging Network
have the resources to setup independent network
but poor value for customers with each manufacturer setting up their own networks – so created a coalition
there are regional networks
remote monitoring of all stations
payment systems, terminals, ..etc all have to play along
they have instrumented vehicles, roaming the network, just to test the charging stations
problems identified are communicates to the CEOs of the stations of the network
problematic stations can be removed from the network if the quality problems aren’t addressed
Long charge times
perception is very different
charge in iPhone is bad compared to a flip phone, still no-one wants to switch back to a flip phone after using an iphone
the process of going to get petrol is obsolete
it actually takes 30 seconds to charge the car – because all you do is just plugin
daily charge is almost never conscious – go home, plugin and walk away, its charged and ready to go when you come back to it again
tech to charge faster is still developing
but it makes less difference than we think because the human element plays a very big role in when/how we charge
with 300 mile cars (current range of Ford EVs), it’s not actually a requirement
users will take a break after driving for a couple of hours (~200 miles), pit stops are more than necessary to replenish the charge
large miles like 800-1000 miles
Recycling and reusablity
materials are really in demand
if they don’t have access to minerals for batteries now, they are going to be in trouble
Blue City (Blue Ocean City? Blue Oval City??) – vertical integrated city for battery integration
collection of leftover and recycling to be more efficient in production
Buttons in the Cars
hardware switches/buttons are difficult to modify once installed
software provides the ability to change and modify
context level buttons – adaptable interface based on the context
parking camera buttons are not needed at 60 miles/hr – UI can hide them
smart vehicles can remember the way you park, so it will auto launch camera when on parking mode and can remember which camera is more frequently used and launch it automatically
smart UI with sensible human overrides
we think we need a button until we are presented with a better experience
no cycling around the cameras pressing the same button again and again
Customer education
basic problems because customers completely ignore the instructions
they just buy the car and use it without any research
so gamification kind of notifications to teach customers about nuances of an EV
I had to copy all the files from the home directory into a Azure Blob container today. All the regular folders without any of the dot files and dot folders.