Skip to content

Still blank on modern python librarys  #173

New issue
New issue
Open
Open
Still blank on modern python librarys #173

Description

@decryptedchaos
decryptedchaos
opened on Aug 27, 2023

This has already been brought up back in 2022 here #164 and #136

I found none of the discussed workarounds viaable.. I really wanted vaping to work as a simpler alternative to smokeping (rrdtool alignment sucks)

But after a day of messing with it and trying to pin library versions which debian gets mad at you for doing anyway.. i just could not get it to work with a resonable amount of effort.. i'd have to completely change all my python librarys to older/newer versions to work and thats just not resonable to me..

I would have hoped this would have been solved since 2022, but with that said this does seam to be a small team project so thats understandable..

Well there you go, i suggest this remain open or something opened in its place because this is still very much a big issue.

Activity

  1. grizz commented on Aug 28, 2023

    @grizz
    grizz
    on Aug 28, 2023
    Member

    @decryptedchaos Sorry to hear you've had issues, both issues listed were different causes, but yeah, a blank graph is frustrating.

    This is definitely overdue a dependencies update, which may fix your library issues. What libraries were causing problems?

    Could you post your config and any error messages you got?

    Thanks!

  2. grizz commented on Aug 29, 2023

    @grizz
    grizz
    on Aug 29, 2023
    Member

    Just did an initial pass on updates with #174

  3. grizz commented on Aug 29, 2023

    @grizz
    grizz
    on Aug 29, 2023
    Member

    Actually, it's looking like it might a js issue, could you check and see if you're getting a javascript error on the vaping page?

  4. decryptedchaos commented on Sep 2, 2023

    @decryptedchaos
    decryptedchaos
    on Sep 2, 2023
    Author

    Sorry for the late response, GitHub isn't doing a good job of notifying me of responses, I will look into the pr tomorrow and get back to you it's late here

  5. w4rum commented on Sep 22, 2023

    @w4rum
    w4rum
    on Sep 22, 2023

    I believe I have the same issue:

    Screenshots

    image

    image

    I get the following error in the JS console:

    Uncaught TypeError: this.d3.data.selectAll(...).data(...).enter is not a function
    render_data http://localhost:7021/static/graphsrv/js/graphsrv.js:1465
    render_dynamic http://localhost:7021/static/graphsrv/js/graphsrv.js:1356
    Base http://localhost:7021/static/graphsrv/js/graphsrv.js:869
    jQuery 2
        dispatch
        handle
[graphsrv.js:1465:10](http://localhost:7021/static/graphsrv/js/graphsrv.js)

    image

    Same issue on Firefox and Chrome.

  6. decryptedchaos commented on Sep 28, 2023

    @decryptedchaos
    decryptedchaos
    on Sep 28, 2023
    Author

    Yea there were definitely JS errors like that, I just haven't had time to test it anymore I kinda got mad at it and removed it and I've been distro hopping lately so might test on this one soon

  7. jamespo commented on Oct 18, 2023

    @jamespo
    jamespo
    on Oct 18, 2023

    I also get blank pages, in the console all I get are warnings like:

    The script from “http://yourdomain.coml:7121/graph/?targets=all&id=auto-2&fit=yes&type=multitarget&config=multitarget&source=latency.distant” was loaded even though its MIME type (“text/html”) is not a valid JavaScript MIME type.

    These don't seem to be fatal though. This is in a virtualenv on debian 12 (python 3.11).

  8. pppwaw commented on May 24, 2024

    @pppwaw
    pppwaw
    on May 24, 2024

    When blank, I got this response from api:

    {"meta": {"error": "module 'inspect' has no attribute 'getargspec'"}, "data": []}

    After search, I think that it comes from the 42 line of vodka/data/renderers.py:

    class RPC(DataRenderer):

    """
    RPC renderer, renders an rpc response containing meta and data objects

    Should be used as a decorator. The decorated function will be called
    with the data container as first argument and the meta container referenced
    in the "meta" keyword argument.
    """

    def __init__(self, type="json", data_type=list, errors=False):
        super().__init__(type=type)
        self.errors = errors
        self.data_type = data_type

    def __call__(self, fn):
        def wrapped(*args, **kwargs):
            resp = {"meta": {}, "data": self.data_type()}
            try:
                i_args = inspect.getargspec(fn)
                if i_args.args and i_args.args[0] == "self":
                    fn(args[0], resp["data"], meta=resp["meta"], *args, **kwargs)
                else:
                    fn(resp["data"], meta=resp["meta"], *args, **kwargs)
            except Exception as inst:
                if self.errors:
                    resp["meta"]["error"] = str(inst)
                else:
                    raise
            return self.render(resp)

        wrapped.__name__ = fn.__name__
        return wrapped

  9. pppwaw commented on May 24, 2024

    @pppwaw
    pppwaw
    on May 24, 2024

    I sent a PR to fix this: 20c/vodka#23

  10. teadur
    added a commit that references this issue on Jul 11, 2024

    fix standalone_dns config and use unreleased vodka from github to mit…

    1a0fcfc

  11. kashieda commented on Nov 22, 2024

    @kashieda
    kashieda
    on Nov 22, 2024

    bild

    Is this the same issue, or should I start another thread/issue?

  12. kashieda commented on Nov 22, 2024

    @kashieda
    kashieda
    on Nov 22, 2024

    Output from vaping start standalone_dns --debug:

    pluginmgr hook.compile(vaping.plugins) init.py:24
    vaping.daemon plugins.std_fping: unknown attribute 'period' daemon.py:132
    PidFile <pid.posix.PidFile object at 0x7fff368af710> entering setup base.py:89
    PidFile <pid.posix.PidFile object at 0x7fff368af710> create pidfile: /home/ekengren/vaping/vaping.pid base.py:194
    PidFile <pid.posix.PidFile object at 0x7fff368af710> check pidfile: /home/ekengren/vaping/vaping.pid base.py:181
    2024-11-22 22:31:06,424 - vaping.plugins.fping - DEBUG: popen fping -u -C10 -p20 -e 8.8.8.8 4.2.2.1 208.67.222.222
    vaping.plugins.fping popen fping -u -C10 -p20 -e 8.8.8.8 4.2.2.1 208.67.222.222 init.py:127
    root 8.8.8.8 : 5.83 5.68 5.75 5.51 5.51 5.62 5.52 5.70 5.66 5.65
    fping.py:104
    root 4.2.2.1 : - - - - - - - - - -
    fping.py:104
    root 208.67.222.222 : 15.7 15.8 15.5 15.4 15.6 15.4 15.7 15.7 15.7 15.6
    fping.py:104
    2024-11-22 22:31:06,732 - vaping.plugins.fping - DEBUG: queue emission to vodka (0)
    vaping.plugins.fping queue emission to vodka (0) init.py:230
    2024-11-22 22:31:09,427 - vaping.plugins.fping - DEBUG: emit to vodka
    vaping.plugins.fping emit to vodka init.py:227
    2024-11-22 22:31:09,585 - vodka - DEBUG: making sure configuration is sane ...
    vodka making sure configuration is sane ... log.py:34
    2024-11-22 22:31:09,591 - vodka - DEBUG: instantiating data types
    vodka instantiating data types log.py:34
    2024-11-22 22:31:09,591 - vodka - DEBUG: instantiating plugins
    vodka instantiating plugins log.py:34
    2024-11-22 22:31:09,593 - vodka - DEBUG: instantiating applications
    vodka instantiating applications log.py:34
    2024-11-22 22:31:09,593 - vodka - DEBUG: starting plugins
    vodka starting plugins log.py:34
    2024-11-22 22:31:09,596 - vodka - DEBUG: starting http ..
    vodka starting http .. log.py:34
    2024-11-22 22:31:09,598 - vaping.plugins.fping - DEBUG: popen fping -u -C10 -p20 -e 8.8.8.8 4.2.2.1 208.67.222.222
    vaping.plugins.fping popen fping -u -C10 -p20 -e 8.8.8.8 4.2.2.1 208.67.222.222 init.py:127

    • Serving Flask app 'vaping' (lazy loading)
    • Environment: production
      WARNING: This is a development server. Do not use it in a production deployment.
      Use a production WSGI server instead.
    • Debug mode: on
      werkzeug * Running on all addresses.
      WARNING: This is a development server. Do not use it in a production deployment. _internal.py:225
      werkzeug * Running on http://192.168.1.229:7021/ (Press CTRL+C to quit) _internal.py:225
      werkzeug 192.168.1.108 - - [22/Nov/2024 22:31:09] "POST /graph_data/ HTTP/1.1" 200 - _internal.py:225
      werkzeug 192.168.1.108 - - [22/Nov/2024 22:31:09] "POST /graph_data/ HTTP/1.1" 200 - _internal.py:225
      root 8.8.8.8 : 5.53 5.55 5.47 5.49 5.59 5.63 5.56 5.45 5.56 5.65
      fping.py:104
      root 4.2.2.1 : - - - - - - - - - -
      fping.py:104
      root 208.67.222.222 : 15.6 15.5 15.5 15.6 15.6 15.6 15.4 15.6 15.7 15.6
      fping.py:104
      2024-11-22 22:31:09,906 - vaping.plugins.fping - DEBUG: queue emission to vodka (0)
      vaping.plugins.fping queue emission to vodka (0) init.py:230
      werkzeug 192.168.1.108 - - [22/Nov/2024 22:31:10] "POST /graph_data/ HTTP/1.1" 200 - _internal.py:225
      werkzeug 192.168.1.108 - - [22/Nov/2024 22:31:11] "POST /graph_data/ HTTP/1.1" 200 - _internal.py:225
      ^CPidFile <pid.posix.PidFile object at 0x7fff368af710> closing pidfile: /home/ekengren/vaping/vaping.pid base.py:220
      2024-11-22 22:31:12,236 - vaping.daemon - DEBUG: stopping vodka
      vaping.daemon stopping vodka daemon.py:256
      2024-11-22 22:31:12,236 - vaping.daemon - DEBUG: stopping latency
      vaping.daemon stopping latency daemon.py:256

  13. xylix commented on Apr 12, 2025

    @xylix
    xylix
    on Apr 12, 2025

    I had the this.d3.data.selectAll(...).data(...).enter is not a function error in console and the Vodka fix seems to work, after installing latest vodka with pip install https://github.com/20c/vodka/archive/master.zip the graphs are displaying.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions