Bot hangs after channel update

[kanielc]

Describe the bug After calling channel update, bot is no longer responsive to any commands. Executed method looks like:

func (sm slowmode) Exec(s disgord.Session, data *disgord.MessageCreate) {
    msg := data.Message

    mentionedChannel, _ := 123456789
    amount := 15
    reason := "just a reason"

    _, err := s.Channel(disgord.Snowflake(mentionedChannel)).UpdateBuilder().SetRateLimitPerUser(uint(amount)).Execute()

    if err != nil {
        log.Println(err)
    }

    msg.Reply(noCtx, s, fmt.Sprintf("Set the slowmode to **%d** in the channel **<#%d>** with reason **%s**", amount, mentionedChannel, reason))
}

Handler looks like

// handleMsg is a basic command handler
func handleMsg(s disgord.Session, data *disgord.MessageCreate) {
    msg := data.Message

    var cmdStr string
    spaceLoc := strings.Index(msg.Content, " ")
    if spaceLoc == -1 {
        cmdStr = msg.Content
    } else {
        cmdStr = msg.Content[:spaceLoc]
    }

    cmd, ok := commands.Commands[cmdStr]

    // if command not found, just return
    if !ok {
        return
    }

    cmd.Exec(s, data)
}

Expected behavior Follow up commands should invoke the handleMsg function

Error messages No errors are thrown

Desktop (please complete the following information):

• Golang version: 1.16.3
• Using Go modules? yes
• Disgord version? 0.26.10
• Connected to the gateway before using REST methods? yes

Additional context

Took images of the call stack with debugger and noticed a network connection thread seemed to still be active. Everything is fine after the first image, but the second one is where it hangs.

[kanielc]

This seems to be the place where things go wrong.

[andersfylling]

So that fixes one potential deadlock, but i dont think that is the actual issue

[andersfylling]

Yeah apparently I lock the same mutex twice. Once in updateChannel and once before calling it in a special branch: https://github.com/andersfylling/disgord/blob/develop/cache.go#L174

Currently writing a bunch of tests to fix this and detect other issues.

[andersfylling]

fix is not yet released. but u can checkout the latest commit and give it a try

[kanielc]

It works, thanks!