Firefox will trigger write error: websocket: close sent (chromium seems to be unable to trigger this event, even with thousands of refreshes sent) by pressing refresh several times on a page with a load time of (network latency included) >250ms This causes the unregister <- connection to fire, however this breaks the socket entirely for ALL current connections and all future connections will connect to the websocket but the websocket is down and will not transfer / receive messages. (Messages can be sent to the server ACCORDING TO THE BROWSER but without error but they're thrown out by the server without notice of any kind).

No idea why it happens like that, but it does. Posted fix works fine.

Hello everyone, I'm starting with websockets and I would like to know if it is possible to send a WS notification after some action is done inside a HTTPS endpoint. For example, I want to notify some users (I still need to figure out how to broadcast just to some users) when a new User is created on the admin panel. A POST request is made to the endpoint /agent and I would like to use websockets to send this new data and populate a data grid when a certain user is on the Agents creation screen.

I don't know if its clear, but is it possible to be made?

Thanks in advance.

Question description In this example: https://github.com/gofiber/recipes/blob/master/websocket-chat/main.go , can you please show how we would close the connection to the client say after 5 minutes. This helps the client to reconnect with a new JWT token.

I tried adding in this into runHub but it doesn't seem to work.

		case <-time.After(5 * time.Second):

			log.Println("Reconnect")

			for connection := range clients {
				cm := websocket.FormatCloseMessage(websocket.CloseTryAgainLater, "add your message here")
				if err := connection.WriteMessage(websocket.CloseMessage, cm); err != nil {
					// handle error
					log.Println(err)
				}
			}

type Book struct {
	ID     primitive.ObjectID `json:"id"  bson:"_id,omitempty"`
	Title  string             `json:"title" binding:"required,min=2" bson:"title"`
	Author string             `json:"author" bson:"author,omitempty"`
}

link

Is it used by fiber or has it to be replaced with "validate" or just removed?

Context

OpenTelemetry is starting to be standard way to collect any metadata about running application. This example shows how to integrate it with fiber and how to use OpenTelemetry context later in nested layers of application (base on context).

Keep in mind that OpenTelemetry is complex piece of software and depends on many parts (e.g. collectors). This is not a scope of this example. Here we gonna use Lightstep as backend but it works with any other.

Changes

• [x] New example with opentelemetry integration
• [x] Comments in main.go for easier understanding
• [x] Screenshots what you will get at the end.

I have recently try to test Fiber using several examples, and it was until an hour later I noticed my error was because all the examples on this repo are using a go.mod file with old versions of Fiber.

I would be really helpful if all the examples were updated to the most recent version of Fiber.

previous one, i tested gracefully shutdown and i found it is not work. so i fix some code and it is ok.

app.listen should be running in goroutine. channel waiting for interrupt signal to gracefully shutdown

Question description I'm about to implement something similar to the websocket-chat example in one of my projects and the following question popped into my mind: Shouldn't the websocket send the messages to each client in parallel? As far as I understand connection.WriteMessage() is a blocking operation. Doesn't that mean, that the hub blocks until each client receives the broadcasting message? If I'm not mistaken, this can be an issue on clients with a slow connection and a limitation to the hubs processing speed in general.

The following snipped sends each message in a separate gorountine. If writing to the socket connection returns an error, the connection gets closed and send the connection back to the hub to unregister the client.

Code snippet (optional)

type client struct {
	isClosing bool
	mu        sync.Mutex
}

var clients = make(map[*websocket.Conn]*client)
var register = make(chan *websocket.Conn)
var broadcast = make(chan string)
var unregister = make(chan *websocket.Conn)

func runHub() {
	for {
		select {
		case connection := <-register:
			clients[connection] = &client{}
			log.Println("connection registered")

		case message := <-broadcast:
			log.Println("message received:", message)
			// Send the message to all clients
			for connection, c := range clients {
				go func(connection *websocket.Conn, c *client) { // send to each client in parallel so we don't block on a slow client
					c.mu.Lock()
					defer c.mu.Unlock()
					if c.isClosing {
						return
					}
					if err := connection.WriteMessage(websocket.TextMessage, []byte(message)); err != nil {
						c.isClosing = true
						log.Println("write error:", err)

						connection.WriteMessage(websocket.CloseMessage, []byte{})
						connection.Close()
						unregister <- connection
					}
				}(connection, c)
			}

		case connection := <-unregister:
			// Remove the client from the hub
			delete(clients, connection)

			log.Println("connection unregistered")
		}
	}
}

I'm happy to open a PR for this, but I thought I'd ask first if it even makes sense.

Edit: I realized that my initial code snipped caused a race condition and possibly a panic due to concurrent write to websocket connection. Therefore I added a mutex to the client to (hopefully) prevent that.

Fiber version/commit

master

Issue description

gcloud example: https://github.com/gofiber/recipes/blob/master/gcloud/README.md

Error from google is:

app.Start: listen tcp4: address 8080: missing port in address 

Expected behavior

Steps to reproduce

Click the "Run on Google Cloud" in the README.md

JWT+Mongo+Docker+Nginx 🚀

Freatures

• JWT : Custom middleware for JWT auth
• Mongo : Connection with mongodb and configuration file with the possibility of changing the environment
• Docker and Nginx : Deploy in docker using 5 replicas and load balancer with Nginx
• Logger : Request logger

Endpoints

| Name | Rute | Parameters | State | Protected | Method | | ------------ | --------- | ---------- | --------- | --------- | ------ | | Register | /register | No | Completed | No | POST | | Login | /login | No | Completed | No | POST | | Get Profile | /profile | id | Completed | Yes | GET | | Edit Profile | /profile | No | Completed | Yes | PUT |

What this PR fixes:

Currently dependabot can't update dependencies recursively as stated here: https://github.com/dependabot/dependabot-core/issues/2178 https://github.com/dependabot/dependabot-core/issues/2824

This PR adds each directory to dependabot.yml so the go dependencies get updated.

Related issue:

Fixes #171

How to replicate:

• Git clone this repo: git clone [email protected]:gofiber/recipes.git
• Run the following script python3 create_dependabot.py

import os

pwd = os.getcwd()
print(f"Current working directory: {pwd}")

dirs = [entry.name for entry in os.scandir(os.path.join(pwd, "recipes")) if entry.is_dir()]

for entry in dirs:
    print('  - package-ecosystem: "gomod"')
    print(f'    directory: "/{entry}"')
    print('    schedule:')
    print('      interval: "daily"')

Is your feature request related to a problem? For certain people a bootstrap is a starting point and should include clear instructions for setup.

Describe the solution you'd like Provide setup instructions in the README

Describe alternatives you've considered None

Additional context None

Is there any advantaje using ctx.UserContext() and pass it into GORM dbInstance.withContext() method?

By example in handler method

func Register(ctx *fiber.Ctx) error {
    err := r.db.WithContext(ctx.UserContext()).Updates(&model).Error
}

I would to know if we could have any kind of advantaje passing the userConext() into the WithContect() GORM query method, something like cancellationm boundary, etc.

Lastly I saw in the fiber source code that UserContext() is set with context.Background() if it was not previouly set by the user (me) so looks like If I'm not setting it previously we have not any kind or advantage?

Thanks in advance!