#metabrainz

Got this so far :) Now a systematic view to present all the information?

nope, it is still a way to sort out exceptional issues

like the ff "web developer" console thing?

typical case is the following:

the user has an issue, and he's out of clue

he comes here or forums or whatever, and ask for help

if the issue is trivial, he gets a quick answer

but sometimes the issue is harder to locate

a dev or an advanced user can ask him to enable debug mode

and post the content

https://picard.musicbrainz.org/docs/troubleshoo... "Getting Logs"

okay...

there are 2 ways to do it: redirect console output to file, or copy the content of this window

first one is out of question for non-tech users

yep, agreed :p

the main problem is that the log can be huge, and basically it is hard to find anything in it if you arent used to

which is the case of most users

so i want to give more tools for the user to locate the issue in this log

first thing, colorization by level (info, warning, error, debug)

not ideal for color-blind people, so there's a prefix (I:, W:, E:, D:) on each line too

i get red error text and dark purple "d" text

zas

The "verbosity" control, okay.

yes, wait, i'll come to new things

current state: only checkbox to toggle debug mode, and colorization by level

oh okay..sorry. go on :)

what you see is the dev version i'm working on

so, first, filtering by level: give the possibility to show only errors, or warnings, etc...

usually verbosity is : show only info, show info+warning, show info+warning+error, show info+warning+error+debug

which means you can't have only errors

so i went for a menu with 4 checkboxes, with 2 drawbacks: you can uncheck all, and see nothing

and it is a bit unusual

show an error message "you cnat see logs because no options are checked" maybe?

It also closes after you check/uncheck once... so you have to open it again to check/uncheck another item

yup

:(

If I understand correctly, we need a small control panel-ish thing to filter all the info and help the user pin point the issue?

yes

the idea is to start from a big log to the issue

Which can be used to access all filters easily, highlight, clear logs and export.

Also is scalable for features in future?

typical case: a user contacts us, explain the issue, we ask him to filter a certain way, and he posts the related log view, instead the whole file

yes, scalable somehow, but it isn't the core of the app... so not much

let me explain what are "domains"

basically there are tags on certain log messages devs add in the code

yeah...and what are ws also?

this does sound like the webconsol thing in the ff browser. so i think that's a very good idea actually 👍 zas and chhavi, I won't interfere abymore sorry :)

ws=web service ;)

but that's not meant to be uber explicit

because domains are mainly a dev thing

the idea is to be able the user to post all lines related to one or more domains

for example, if the user have an issue with audio fingerprinting, that's acoustid domain

important thing before i continue: we intentionnally reduce the number of debug messages mainly because it would be too verbose for users and therefore even harder for them to sort out any issue

but ideally we should be able to "dig" into a domain

this is where verbosity is insufficient

debug messages are debug messages from every part, but i may want as much as debug messages for a specific thing

and just this one

so, the UI sucks atm

but the idea is there

Aah got your hassle..

So we need a ui which lets user do domaim specific "digging" as well

also, we could use source file and/or modules, but that's even worse, because what i call "domain" could be exploded over different files or modules, and filtering on modules or files is even less meaningful for end user (or beginner devs)

my idea is to be able to reduce the text in the log view to whatever is needed, press save as, and post the result for help

also, plugin devs could add their plugin name as domain, so one would be able to see only the messages from this plugin

read: the list can the long

and it is dynamically created

if code related to a new domain generates a new message, its domain is added to the list (if any)

its domains (that's a set)

domains will not be translated, and will be usually short names

With you so far.

well, that's all, expecting help on the UI part, because devs suck at UI things (and me, even more)

Give me a little time to think /research. Will get back to tonight or tomm morning :)

ok, np :) thanks

[16:15] <zas> my idea is to be able to reduce the text in the log view to whatever is needed, press save as, and post the result for help any open source type paste bins that we could make the thing automatically plug int to? giving the end user a handy link to post in irc etc. places maybe?

Hello there, anyone working at murdos/musicbrainz-scripts?

bitmap, yvanzo ?

no idea

HSOWA: yes, i thought about it, but for now i prefer the user to manage this (after all, he does since years)

hi jesus!

jesus2099: me

cool, zas  ! :)

zas: maybe she does too ;)

This bug causes this https://musicbrainz.org/edit/50779852

but you guys are le french! tell me what "violinfamily" should be in french!

submitting recording comment removal edits ??

i asked in #musicbrainz yesterday to os but it was eaten by noone readinged it

jesus2099: merged ;)

all i need now is danish, finnish and dutch

and we have users like that

zas: you’re so fast! thanks very much! :)

🙇 so if you could tell me that would help loads! :D

hey jesus2099

chhavi_: not exactly classes, but I would define them as less variables http://lesscss.org/features/#variables-feature

HSOWA: do you have other xxxxx family examples ?

this is what we do in https://github.com/metabrainz/musicbrainz-serve...

jesus2099: not really :(

right now the alias is "plurally violin" which is what we're going way from

I am not really knowledgeable… I thoght it was les instruments à cordes

but les instruments à cordes is much more general

you can set a variable to any string I believe, so e.g. "#000" or "12px" works

tht's probably "string isntruments" no?

la famille des violons ? sounds really weird

HSOWA: i would say "(classical) strings" = "cordes" in french

« les violons »

 ?

zas: yes. but for "violinfamily" what sort of words would you use? i can add as many aliases as possible so don't be afraid to come with several suggestions

chhavi_: and our current font size variables are defined here https://github.com/metabrainz/musicbrainz-serve...

zas: isn't "cordes" all types of strings?

explisitly violin, violin, viola(alto) cello(violoncello) and the bass(contra/double)

HSOWA: all the instruments in your violin family are part of the « instruments à cordes frottées » for us French

if we can stick to rem units, that would be ideal

we don’t have sub category in there, unlike in English https://en.wikipedia.org/wiki/Bowed_string_inst...

so you have to make up a name

(px can be used for the root element, i.e. <html>, then the rem units are relative to that)

actually violinfamily is even a subber category under bowed :D

« Violons et apparentés »

 ?

meaning « Violins and the likes »

heh

yes « Violons et apparentés » isn't bad

i'll use that as primary then, thanks a lot you guys

should it be capitalised also or not?

hi kartik!

i have infact added the rackett you researched https://tickets.metabrainz.org/browse/INST-193

INST-193: Rackett

:)

[listenbrainz-server] paramsingh opened pull request #352: LB-305: Improve parameter checking for timestamps (production...timestamp-checking) https://git.io/vAJTO

HSOWA: I don’t know about capitalisation…

bot to worry. it can be change later if it needs so :)