Update: The original dev does not remember exactly. However they have said that clientId was originally a VARCHAR, so this may have been checking for both '0' or ''

So an over-engineered workaround to a bad datatype perhaps?

I forgot to mention this is in SQL Server, so SIN operates on radians. So I THINK this can only ever cast to a 0 when clientId is also 0

It certainly doesn’t for any of the 100,000 existing rows

The client table has around 100,000 rows each with a unique clientId, none of which are returned from the CAST / ABS / SIN

I think you are right and this is a ‘fix’ for something lost to time. I am going to talk to the original dev tomorrow to see if they remember what it was for

1. Soft Skills Engineering - Software engineering advice podcast
2. If Books Could Kill - Criticising reviews of bestselling books
3. CoRecursive - Stories about software

Let me make sure I understand first

1. You are attempting to passwordlessly SSH from Window to a group of servers using Powershell
2. Something stopped working and you regenerated your Windows SSH keys

i added my private key, and tried to connect

This concerns me, as the server should have the user’s public key, not private. Private should be exactly that, private

Is the Powershell user / SSH key the same as the Putty user / SSH key that still works?

When you run the Powershell script, does it give any error messages?

I know with Linux -> Linux SSH you can log verbosely with -v, is that something you can do under Powershell?

Is password auth enabled? Does that still work from Putty, and can you do the same from Powershell?

@orbit@beehaw.org just suggested this 24-hour cyberpunk playlist to me too

Not specific to AI, some of the people I work with make me prone to drinking as well

These are really nice! Thank you

I followed Paged Out for a year before I realised that Issue #3 was never going to happen