Lahuca-Software-Development / Lahuca-Software-Development/BotSentry

SQL error 1213 for Multi Proxies

Open
#109 4 comments 0 reactions 1 assignee View on GitHub

@Laurenshup is already working on this.

Since Dec 13, 2023.

good first issue medium priority question
Dominant language
CSS
Stars
6
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Proxies version:
Flamecord 1.5.9
BotSentry 9.5.3

Each Bungeecord has this bug at different times. None is the same.
No one even has to be on the server for it to do it.

Proxy Log 1:
[20:55:17 INFO]: (!) SQL error is 1213.
[20:56:17 INFO]: (!) SQL error is 1213.
[13:29:17 INFO]: (!) SQL error is 1213.
[13:30:17 INFO]: (!) SQL error is 1213.

Proxy Log 2:
[00:32:52 INFO]: (!) SQL error is 1213.
[00:33:53 INFO]: (!) SQL error is 1213.
[00:35:53 INFO]: (!) SQL error is 1213.
[03:03:28 INFO]: (!) SQL error is 1213.
[03:06:29 INFO]: (!) SQL error is 1213.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.