I always used the rabbitmq management plugin to inspect messages, but I don't know if that's provided by the docker container
Gentlecat
we are using rabbitmq:3.6.5-management
Mineo
oh, great - if you access the web interface it provides, you should be able to click your way to all the messages in a specific queue
Gentlecat
bitmap: ^ do we have a way to do that
bitmap
if the port is exposed you should be able to use an ssh tunnel
Mineo
alternatively, the caa-indexer also has a retry and failed queue, you should be able to use the same commands you use for inspecting those to look at the messages
zas Mineo bitmap, a proposal for picard plugins, can we include a compatibility list for all plugins?
so that only plugins that are tested by plugin authors to run in a particular os are included
I am willing to make a PR for all the existing plugins and include the code in plugins.py to process this
Freso
+1 from me, but I'd say it's too late for 1.4.
samj1912
Freso: I think we can make it
not much changes
I have a windows, linux and osx machine
I can test the plugins on all 3 and make a compatibilty list
the code wont be large enough to cause errors, just an if while loading
Mineo
please don't put any more things into 1.4. a lot of the pull requests this last month have been fixes for obviously easy things from the last 2 months already
Freso
^
There are plenty of things that individually "wont be large enough to cause errors".
1.4 is in feature freeze. This would be a feature.
samj1912
hmmm, what should we do about the inclusion of non compatible windows plugins then?
leave it for 1.4.1?
Freso
samj1912: I'd say so, yes.
samj1912
they cause import errors in the log which makes people wary that something is wrong with picard
Freso
Sure.
Mineo
I can't find the reason right now, why were plugins put back into the windows installer?
Freso
Mineo: Backwards compatibility I think.
samj1912
so that the required imports can be included by py2exe
Freso
Ah. Right.
Could that be written so py2exe includes the required imports, but doesn't actually bundle all the plugins?
samj1912
we can, well either have to write a script of some sort to figure out all the includes and add them to py2exe includes
Freso
(Also, it still won't help if a plugin changes dependencies between releases.)
samj1912
or if there is a built in functionality like that for py2exe that I am not aware of, then I am not sure
Freso
(Or if a new plugin is added with new dependencies.)
(So maybe another approach entirely should be sought.)
samj1912
Freso: yeah, that is why we need a more permanent solution so that picard doesn't load any plugins not marked tested for that OS
the plugin author can include a COMPATIBLE_OS list in which the plugins run and are tested and picard loads only those
Freso
I was thinking more like making bundled and unbundled packages.
So the script that currently creates the plugin .zip's would include script dependencies.
samj1912
hmmmm
Freso
Because your COMPATIBLE_OS list still won't solve plugin dependency changes between versions.
samj1912
how so?
when a plugin author updates his plugins he can simply update the COMPATIBLE_OS list
Freso
I may have tested a given plugin in a virtualenv on both Mac and Windows and concluded that it worked fine.
ferbncode has quit
But that doesn't mean that the additional PyPi packages in the virtualenv now exist on all Picard installations.
samj1912
hmm, we have to figure out some way to deal with pip packages and plugins
Freso
Anyway. This whole thing is too involved to make it into 1.4 in any shape or form.
samj1912
yeah I suppose
but we need to provide some sort of fix for the errors?
Freso
Don't even bother. Direct your energy towards maybe getting it into 1.4.1 or 1.4.2 or just keep it for 2.0.
Naw. Just get it out there. Make a fix to some degree for 1.4.1.
samj1912
hmmm
ZarkBit has quit
Mineo
do we know if there are any plugins that are compatible with windows and which have a dependency only added via py2exe?
samj1912
videotools I suppose, however even that is broken
We can remove sockets from the excludes and it should work though
Mineo
wait, why would videotools need the socket module?
We can only give hints about compatible envs and requirements, but we have no way to ensure a certain plugin will work or not, because we only have control over Picard, not plugin code nor the env Picard runs in. So the best we can do is to use safeguards (exception handling) and alert the user (error messages).
Do any plugin break Picard ? Or they just don't load/work ?
samj1912
they just dont load
and throw an error in the debug log
which makes people think something is wrong with picard
also the way picard handles erroneous plugins is not at all correct
zas
Well, something is wrong with Picard ;)
samj1912
it just gives a dialog box saying the plugin will be updated
mayhem does a slow clap for zas
in case there are plugin errors on load
Mineo
ok, musixmatch is another plugin that depends on urllib and therefore on socket
github joined the channel
github
[picard] samj1912 opened pull request #610: Remove sockets from py2exe exclude list (master...patch-9) https://git.io/vDYai
github has left the channel
zas
If a dialog appears, and it is unrelated, then it is a bug. But in which exact conditions does it happen ? Is there an easy way to reproduce on linux ?
samj1912
zas, trying now
Mineo
but here's the thing: if there's not a single plugin that works by being included in the installer, I don't see any reason to include plugins in the installer at all
zas
The plugin UI lacks of testing imho ;)
Mineo
the only thing we seem to be gaining are errors in the logs right after installing picard
samj1912
Mineo: true
if this continues, we can just remove the bundling code from setup.py and win packaging script making it like how it was before
zas
We can improve messages in log if they are confusing
Freso +1's not bundling plugins
samj1912
zas, can you merge that PR? I want to test if any of the currently unsupported plugins work after including sockets
if not we will remove the bundling code
github joined the channel
github
[picard] zas closed pull request #610: Remove sockets from py2exe exclude list (master...patch-9) https://git.io/vDYai
github has left the channel
zas
Anyone knows why we don't have tests anymore on Picard PRs ??
samj1912
also I think picard testing has been disabled in travis CI?
yeah ^^
zas
Who changed what .... that is the question...
samj1912
changing metabrainz's travis config seems to be the likely cause