Bugfix: upgrade hwi to 2.1.1 to fix #1840 (#1909)

* upgrade hwi to 2.1.1 to fix #1840

* comment on pip-compile in developments.md

Co-authored-by: Manolis Mandrapilias <[email protected]>
Co-authored-by: moneymanolis <[email protected]>

Author: k9ert

docs/development.md

@@ -443,12 +443,12 @@ If you see this to need some improvements, please make it in small steps and exp
 ### Some words about dependencies
 As a quite young project, we don't have many dependencies yet and as a quite secure-aware use-case, we don't even want to have too many dependencies. That's sometimes the reason that we decide to roll our own rather then taking in new dependencies. This is especially true for javascript. We prefer plain javascript over any kind of frameworks.
 
-If you update `requirements.in` you will need to run the following to update `requirements.txt`:
+If you update `requirements.in` you will need to run the code snippet below to generate a new `requirements.txt`. 
+In order to produce consistent values in `requirements.txt`, delete any pre-existing `requirements.txt` file before doing `pip-compile`.
 ```sh
 $ pip-compile --generate-hashes requirements.in
 ```
-
-This is good for both security and reproducibility.
+This approach is good for both security and reproducibility.
 
 ### Some words specific to the frontend
 We're aware that currently the app is not very compatible on different browsers and there is no clear strategy yet on how (and whether at all) to fix that.

requirements.in

@@ -8,14 +8,14 @@ Flask-Cors==3.0.10
 Flask-Login==0.5.0
 Flask-RESTful==0.3.9
 Flask-HTTPAuth==4.4.0
-hwi==2.1.0
+hwi==2.1.1
 importlib_metadata==4.8.1
 python-dotenv==0.13.0
 requests==2.26.0
 pysocks==1.7.1
 six==1.16.0
 stem==1.8.0
-embit==0.4.13
+embit==0.5.0
 psutil==5.9.0
 pyopenssl==20.0.1
 flask_wtf==0.15.1