cleanup | Remove gone Git branches with ease | Command Line Interface library

1. It is the main method, so there is no need to cleanup. When main returns, the program exits. If this wasn't the main, then you would be correct.

2. There is no best practice that fits all use cases. The code you show here is a very common pattern. The function creates a goroutine, and returns a channel so that others can communicate with that goroutine. There is no rule that governs how channels must be created. There is no way to terminate that goroutine though. One use case this pattern fits well is reading a large resultset from a database. The channel allows streaming data as it is read from the database. In that case usually there are other means of terminating the goroutine though, like passing a context.

3. Again, there are no hard rules on how channels should be created/closed. A channel can be left open, and it will be garbage collected when it is no longer used. If the use case demands so, the channel can be left open indefinitely, and the scenario you worry about will never happen.

According to Named Pipe Security and Access Rights,

In addition to the requested access rights, the DACL must allow the calling thread FILE_CREATE_PIPE_INSTANCE access to the named pipe.

I answered the part about why the paragraph mark is showing up in your question posted on Super User. This response is to address using vba to insert a building block. Your vba, though, is not causing the extra paragraph mark. As stated in the response in Super User, that is due to the content of the building block.

If your vba (not shown) opens the header or footer area and pastes content, then a bug in Word would retain the original paragraph mark as an extra. If you are using it, though, through one of the processes shown below, it should not.

A recorded macro will seldom do what you want, especially if you are sharing the template.

To do this, you need to know:

• The name of the building block

• The name (and location) of the template that holds the building block unless the macro is in the same template

• How to insert a macro. See Installing Macros and Install/Employ VBA Procedures (Macros).

• Building Block Name = "MyBB" (example in this macro, change to fit)

Situation 1 and 1a have the Building Block and the macro in the same template. This simplifies coding because a macro can always tell the name and location of the template that holds it. That information is required to use a macro to insert a building block.

Situation 1 - template holds both the building block and the macro

Here is the macro to insert that uniquely-named building block at the insertion point in the document:

You can't do this from command level. But I guess you could write container_commands script to rename your docker-compose file from docker-compose.dev.yml to docker-compose.yml:

You can use the container_commands key to execute commands that affect your application source code. Container commands run after the application and web server have been set up and the application version archive has been extracted, but before the application version is deployed.

UPDATE 12 Jun 2021

I tried to replicate the issue using simplified setup with just docker-compose.prod.yml and Docker running on 64bit Amazon Linux 2 3.4.1 EB platform.

docker-compose.prod.yml

It doesn't work because it seems you close over the initial newGameId state which has a value of '' and isn't the docRef.id it's updated to.

Use an additional useRef hook to cache a copy of the newGameId state value and reference this in the useEffect hook's cleanup function.

It looks like you're using the LabIcon component, yeah? https://github.com/jupyterlab/jupyterlab/blob/master/packages/ui-components/src/icon/labicon.tsx#L454

That's a class component, but useEffect and useState hooks can only be used in function components and in other hooks: https://reactjs.org/warnings/invalid-hook-call-warning.html

You can only call Hooks while React is rendering a function component:

Call them at the top level in the body of a function component.

Call them at the top level in the body of a custom Hook.

The main issue is that useEffect hook callbacks can't be async functions as these implicitly return a Promise which would, by design, be interpreted as an useEffect hook cleanup function. This won't work.

After looking at your code for a bit it looks like getting and setting the data state is independent of the firebase subscription. You can minify just the asynchronous logic into an async function to get and set the user data and invoke that, and access the firebase collection as per normal.

Use a React ref to hold on to the unsubscribe callback.

I think the following implementation should get you very close to what you are looking for. (Disclaimer: I've not tested this code but I think it should work)

You can do something like this, instead of exporting the results on each iteration and appending to a file, it's a better idea to first perform your test and save the results in memory. Once all is complete, export the results:

I figured it out: I don't need to brute force the path in; in the .pydevproject file of your python project, make sure you add in the full path to PySide6 because for some reason the system cannot find it without the path. Something like this: