pest-parser / intellij-pest

pest grammar file support for all JetBrains IDEs
Apache License 2.0
35 stars 5 forks source link

Disabling emmy-issue? #387

Open tomtau opened 6 months ago

tomtau commented 6 months ago

Raised on Discord:

pew; — Today at 00:59 ⁠github Should we just disable emmy-issue? This is simply spam at this rate

@ice1000 can it be disabled or shall we just block @emmy-issue from posting here?

ice1000 commented 6 months ago

Raised on Discord:

pew; — Today at 00:59 ⁠github Should we just disable emmy-issue? This is simply spam at this rate

@ice1000 can it be disabled or shall we just block @emmy-issue from posting here?

The intention is to make a convenient way to report bugs, but there are so many bugs that I have no idea how to reproduce or fix. I don't know what to do.

tomtau commented 6 months ago

I assume this extension may later be replaced by pest-ide-tools: https://github.com/pest-parser/pest-ide-tools/issues/10#issuecomment-1623189801 so those issues may not be relevant? Maybe we can disable it then? @Jamalam360 do you know how it looks like with pest-ide-tools in IntelliJ?

ice1000 commented 6 months ago

Maybe we can disable it then?

Unfortunately you can't simply disable it, but we can make an update where bug report feature is unavailable.

tomtau commented 6 months ago

@ice1000 I'm not familiar with how updates of the IntelliJ plugin are done, could you help with that? Alternatively, we can perhaps put @emmy-issue on the blocklist (so it won't be able to post new issues)?

ice1000 commented 6 months ago

@ice1000 I'm not familiar with how updates of the IntelliJ plugin are done, could you help with that? Alternatively, we can perhaps put @emmy-issue on the blocklist (so it won't be able to post new issues)?

I can do the update, but I'm just not sure if that's the right thing to do.

tomtau commented 6 months ago

thanks @ice1000 🙏 I think it should be ok to do:

  1. many (or most) of the issues seem duplicate, so at least the major ones look like they are already recorded
  2. the issues aren't being triaged (e.g. flagged / closed if they can't be reproduced)
  3. they may become irrelevant once pest-ide-tools is made available for IntelliJ

Or do you see any value in recording them or do you know if you or someone planned to address some of the repeated ones ?

ice1000 commented 6 months ago

Or do you see any value in recording them or do you know if you or someone planned to address some of the repeated ones ?

No and no

ice1000 commented 6 months ago

image

I hate myself

tomtau commented 6 months ago

@ice1000 different versions on CI?

ice1000 commented 6 months ago

@ice1000 different versions on CI?

Every version here is from 4 years ago and I need to update all of them to be able to run a test at all

tomtau commented 6 months ago

ouch 🙈

Jamalam360 commented 6 months ago

Regarding pest-ide-tools, I think it should be possible to port it to IntelliJ IDEs. It would need a Java/Kotlin component written which spawns the Rust language server binary and communicates with it, which I can do at some point (maybe this summer, currently busy with exams). Definitely worth the effort given that RustRover has now been released

process0 commented 6 months ago

Is there a way to disable this as a user? This is a huge no for me.

ice1000 commented 6 months ago

Is there a way to disable this as a user? This is a huge no for me.

Disable what

process0 commented 6 months ago

Automatically posting a bug report with filenames when the extension crashes

ice1000 commented 6 months ago

Automatically posting a bug report with filenames when the extension crashes

It's only going to disable it for the pest plugin, don't worry

ice1000 commented 6 months ago

I hate

tomtau commented 6 months ago

Plugin development in Kotlin troubles?

ice1000 commented 6 months ago

I just don't have the energy to update everything 😢

tomtau commented 6 months ago

Oh, no worries! Shall we try to block @emmy-issue from posting here instead?

ice1000 commented 6 months ago

Oh, no worries! Shall we try to block @emmy-issue from posting here instead?

Maybe yeah