mok | mok: master of keys | Data Mining library

What i did?

• Change alert_coords(evt) with alert_coords(event) because evt doesn't exist.
• Add the function AddHtml directly into alert_coords function
• Instead of return data from alert_coords active directly AddHtml with array coords

Now when you click will ouput coords.

Looking at the file list of the gnu-efi package, I see:

There is no way of creating a collection without any document in firestore. If you check the official documentation, the last paragraph says:

You do not need to "create" or "delete" collections. After you create the first document in a collection, the collection exists. If you delete all of the documents in a collection, it no longer exists.

So, a collection needs at least one document in it.

Based on the error message, you are using an async version of reqwest. The latest version contains both async and blocking versions, if I recall correctly.

In order to actually consume the future and get to the value inside, you need to execute it using an executor e.g. Tokio. This can be done in multiple ways.

The simplest way is to add tokio = { version = "0.2.22", features = ["macros"] } to your Cargo.toml and then have this in main.rs:

You need to style

You need to use new variable and break loop if found match. Also, condition $newNAME|strpos:$spec !== false is better (if you allow to search string in "0" position of text).

Opening a file with mode "w" will erase the existing file and start with an empty new one. That is why you are getting only one number. Every time you write to the file, you overwrite whatever was there before. There is no mode "w+". I believe that ought to cause a ValueError: invalid mode: 'w+', but in fact it seems to do the same as "w". The fact that "r+" exists doesn't mean you can infer that there is also an undocumented "w+".

From the documentation for open():

The second argument is another string containing a few characters describing the way in which the file will be used. mode can be 'r' when the file will only be read, 'w' for only writing (an existing file with the same name will be erased), and 'a' opens the file for appending; any data written to the file is automatically added to the end. 'r+' opens the file for both reading and writing. The mode argument is optional; 'r' will be assumed if it’s omitted.

So, no "w+".

I think you want mode "a" for append. But if you do that, the first time your code tries to write to the file, it won't be there to append to, so you get the file not found error that you had a problem with.

Before writing to the file, check to see if it is there. If not, open it for writing, otherwise open it for appending.

We discovered several things in the comments. Firstly, that you had a proxy problem that prevented one container using the API in another container.

Secondly, and critically, you discovered that the service names in your Docker Compose configuration file are made available in the virtual networking system set up by Docker. So, you can ping front from back and vice-versa. Importantly, it's worth noting that you can do this because they are on the same virtual network, mynet. If they were on different Docker networks, then by design the DNS names would not be available, and the virtual container IP addresses would not be reachable.

Incidentally, since you have all of your containers on the same network, and you have not changed any network settings, you could drop this network for now. In other words, you can remove the networks definition and the three container references to it, since they can just join the default network instead.

Thirdly, you learned that Docker's virtual DNS entries are not made available on the host, and so front and back are not available here. Even if the were (e.g. if manual entries were made in the hosts file) those IPs would not work, since there is no direct networking route from the host to the containers.

Instead, those containers are exposed by a Docker device that proxies connections from a custom localhost port down to those containers (4200, 5000 and 5001 in your case).

A good interim solution is to load your frontend at http://localhost:4200 and hardwire its API address as http://localhost:5000. You may have some CORS issues with that though, since browsers will see these as different servers.

Moreover, if you go live, you may have some problems with mobile networks and corporate firewalls - you will probably want your frontend app to sit on port 443, but since it is a separate server, you will either need a different IP address for your API, so it can also go on 443, or you will need to use another port. A clean solution for this is to put a frontend proxy in front of both containers, and then just expose the proxy in Docker. This will send HTTP requests from the outside to the correct container, depending on a filtering criteria set by you. I recommend Traefik for this, but there are undoubtedly several other approaches.