Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to remove signs/channels (SQLite not updated) #217

Open
Ru1x opened this issue Apr 28, 2020 · 0 comments
Open

Failed to remove signs/channels (SQLite not updated) #217

Ru1x opened this issue Apr 28, 2020 · 0 comments
Labels

Comments

@Ru1x
Copy link

Ru1x commented Apr 28, 2020

Bug report

I'm using version:4.0.4
I'm on Minecraft:1.12.2
I'm running:Paper

Seen results:
Removing any signs or /wr remove <Channel ID> does not remove records from SQLite DB therefore signs are re-generated once the server restarts

Expected results:
Destroying Signs immediately removes records from the database.

How to reproduce:

  1. Create the first sign (let's do transmitter), and name it wrtest
  2. You just created a new channel is shown
  3. Verify that Debug message are shown as well
[INFO]: [WirelessRedstone][Debug] Channel created in database. wrtest
[INFO]: [WirelessRedstone][Debug] Placed new WirelessPoint in the database
  1. Create another sign (maybe receiver)
  2. You just extended a channel is shown
  3. Verify that Debug message are shown as well
[INFO]: [WirelessRedstone][Debug] Placed new WirelessPoint in the database
  1. Verify database has these records on the table channel, transmitter, and receiver
  2. Destroy 2 signs
  3. 2x Successfully deleted this sign are shown
  4. Any Debug Message is NOT shown
  5. Database records still exist on the table channel, transmitter and receiver

Additional info:
Manually remove records from SQLite using external tools can delete channels entirely.

@Ru1x Ru1x added the Bug label Apr 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant