How to unblock Golang channel

Case #1:
I have a golang websockets server using buffered channels and coroutines. every X amount of notifications, the channel becomes blocked, and I'm trying to figure out how to unblock it.

If the channel is blocked, it means that the receiver is not currently reading from it, and therefore the buffer is full. One way to unblock the channel is to increase the buffer size. This can be done by specifying the buffer size when creating the channel:

1 codemyChannel := make(chan string, bufferSize)

where bufferSize is the number of elements that the channel can hold before it blocks. Increasing the buffer size may not solve the root cause of the blocking issue, but it can provide some temporary relief by allowing more messages to be queued before the channel blocks.
Another option is to make sure that the receiver is reading from the channel frequently enough to prevent it from becoming blocked. If the receiver is not keeping up with the message flow, then the channel will block until it is able to deliver the message to the receiver. You can try using a select statement to read from the channel in a non-blocking way:

1select {
2case msg := <-myChannel:
3    // process the message
4default:
5    // no message available
6}

This will allow the program to continue running even if no message is available to read from the channel. The default case will be executed if the channel is empty, and the program can perform other tasks while waiting for a message to arrive.
Another option is to use a buffered channel with a timeout. This can be done by combining a select statement with a time.After function call:

1select {
2case msg := <-myChannel:
3    // process the message
4case <-time.After(time.Second):
5    // timeout after 1 second
6}

This will wait for a message to arrive on the channel for up to one second. If a message arrives during that time, it will be processed. If no message arrives within one second, the timeout case will be executed.
It's important to note that increasing the buffer size or using a timeout can mask the underlying issue of slow message processing. It's a good idea to monitor the program and investigate why the channel is becoming blocked in the first place.