Buggish: AWS (3.1.3.1894 for Windows) latest patch broke tab hold

 I noticed in the patch notes that the latest version (3.1.3.1894) fixed a double-shift, but it seems this version broke hold tab key. Before this patch, I was able to hold the tab key down. I use this in excel where I want to move to the right (directional) column or when I ALT-TAB to another window. I also use SHIFT-TAB to go to the left column.

I have not tried to refresh my connection as I just connected to this session and need to start working on my next task. 

Scammish: Robinhood liquidity issue or not?

 I am not a regular trader and cannot follow all the news... but this sounds kind of fishy.

https://www.youtube.com/watch?v=cuCcchMOsKE&ab_channel=CNBCTelevision

In this video, CEO says directly that there is no liquidity problem.

But then I got this email from Robinhood that leads to their blog: https://blog.robinhood.com/news/2021/2/1/a-letter-to-our-robinhood-community

In this blog, they said it was due to regulations that seem to be tied with not having enough cash which to me sounds like a liquidity problem.

I kind of followed the short squeeze news, and know the bare minimum of sock investments. This is all beyond my knowledge but this still sounds suspicious.

Buggish: Microsoft SMO Index Fillfactor Defaults Unwanted Value Instead of 0, null, or nonexistent.

I am trying to copy objects from one environment to another. I do not care whether the developer created the objects correctly or not. I only care that I create an almost exact copy of the object to another database.

One of the features of my tool is to automatically pull the index from a lower environment and creating it in the new environment. For some reason, this automatically fills in the fillfactor to the default value of the target database which I do not want. One, this is not how the developer designed his index. Two, when promote that change to the next environment it will copy that defaulted fillfactor which may be different on the target database. 

So now I have no way of telling whether the developer intentionally added a fillfactor (which from what I read online is intentional) or didn't set a value but was added because Microsoft SMO doesn't set the fillfactor to the value that I want.

I have set fillfactor to 0 and to 100. 0 will always set fillfactor to the target database default fillfactor. 100 will be 100, obviously. I cannot set the value null because it is byte type. I tried to leave it unset, but will still set to default.

This is pretty dumb because you can execute a script to not have fillfactor. And once you have fillfactor, you cannot even go into the database to set it to 0 (even if the default db server value is the same as the fillfactor).

Simply, I just want the index to be the same as the source database. If the source database does not specify a fillfactor, I want the target database to also not specify a fillfactor.