Your message dated Tue, 13 Feb 2024 16:20:15 +0100
with message-id <[email protected]>
and subject line graphite-web: aliasByNode() gets upset by 'odd' characters in 
data paths
has caused the Debian Bug report #770331,
regarding graphite-web: aliasByNode() gets upset by 'odd' characters in data 
paths
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
770331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770331
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: graphite-web
Version: 0.9.12+debian-6
Severity: normal

If I store my data in a path looking like:

   host:server.disk:sda.dir:w.sectors

then this confuses the aliasByNode() function. Asking it to set the
legend as node 0 produces simply "host", and nodes 1 onwards yield an
invalid graph entirely. It gets similarly upset if I use "=" to separate
these name=value pairs.

For now, I have reshaped my data into paths like

   by_host.server.by_disk.sda.by_dir.w.sectors

which now works as expected.

It seems only the aliasByNode() function itself that gets upset by this
though; other functionallity seems unaffected.


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages graphite-web depends on:
ii  adduser                3.113+nmu3
ii  libjs-jquery           1.7.2+dfsg-3.2
ii  libjs-jquery-flot      0.8.2+dfsg-1
ii  libjs-prototype        1.7.1-3
ii  libjs-scriptaculous    1.9.0-2
ii  python                 2.7.8-2
ii  python-cairo           1.8.8-1+b2
ii  python-django          1.7.1-1
ii  python-django-tagging  1:0.3.1-4
ii  python-pyparsing       2.0.3+dfsg1-1
ii  python-simplejson      3.6.5-1
ii  python-tz              2012c-1
ii  python-whisper         0.9.12-1

graphite-web recommends no packages.

Versions of packages graphite-web suggests:
ii  graphite-carbon      0.9.12-3
pn  libapache2-mod-wsgi  <none>
pn  python-ldap          <none>
pn  python-memcache      <none>
pn  python-mysqldb       <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 1.0.2+debian-1

Hi,

This seems to have been fixed in upstream commit:

    
https://github.com/graphite-project/graphite-web/commit/b71f0e01b7b8b90f8124fabcc591c1f77e04ffc3

And released in 1.0.0 (from what I can see in the changelog).

Feel free to reopen if I'm mistaken.

Thanks,

Alex

--- End Message ---

Reply via email to