tatami | alpine linux configs | Continuous Deployment library

Your problem is that n*(n+1) can be too large to store in an unsigned long long, even though the end result (half of that) which you calculate via iteration may still fit.

Assuming your unsigned long long has 64 bits, it can hold integers up to 18446744073709551615. Anything above that will restart from 0.

Edit: As Nathan points out, you can of course have both calculations overflow. The sum would still give the correct result modulo 2^64, but the direct calculation can be off because the division does not generally yield the same result modulo 2^64 after you have wrapped around.

Got it! Very strange but I had to go into the Azure portal -> App Services-> {My App}->Application Settings

There is a setting there for Connection Strings. The connection string had a value null for User ID. I changed it to my regular connection string and now it works fine.