Matthew Hilton
Matthew Hilton
It doesn't need to be done via SMO, yes ideally it would be. Here is what I use to get the current classifications ```powershell $SQLInstance='Server1' $Database='Database1' $Query=@" SELECT Schema_name(objects.schema_id) AS...
Ok, Here is my workaround while the dbatools is not at the requred SMO version. In case someone else needs to do it. ```powershell $SQLInstance = 'Server1' $Database = 'Database1'...
This can be fixed by ## Clean old Python virtual env From inside core directory. ```bash rm -Rv venv ``` ## Build new virtual env ```bash python3.7 -m venv venv...
The above fix feel more like a workaround rather than a proper fix. I can submit a PR to update the documentation but I'd prefer to know if the above...
This was when running in WSL (Ubuntu) on windows 10. I did a fresh build and setup as per the Developing on windows guide.
I wasn't able to get it to work with bluetooth either. That was one reason why it upgraded to buster. I too managed to manually pair and was able to...
i think it is here /var/www/html/vids
I'm currently working at adding cantools to [Crankshaft](https://github.com/opencardev/crankshaft) so I'd also be looking at working on this aswell.
Could we build a CI pipeline to test configurations against esphome versions? With a step to update the markdown and then commit to the repo?
I'll see if I can get one of the cloud ci's working.