Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Adrian Moreno Zapata
    @amorenoz_gitlab
    Screenshot from 2021-06-09 14-13-06.png
    oh, cool :)
    Ben Jackson
    @puremourning
    i bet this is that strange error with logger
    something installing a global log handler or something
    Boris Staletic
    @bstaletic

    @puremourning Yup. That's what I was suspecting.

    @amorenoz_gitlab Notice that the log format isn't the same as in the YcmToggleLogs.

    Adrian Moreno Zapata
    @amorenoz_gitlab
    can I force the ycm log level from the vimrc?
    Boris Staletic
    @bstaletic
    Yes. let g:ycm_log_level='whatever'.
    But for the record, the fault is on your virtual env management tool side.
    Adrian Moreno Zapata
    @amorenoz_gitlab
    yes, it seems so, I'll ask around pipenv project
    Boris Staletic
    @bstaletic
    @amorenoz_gitlab Are you managing your virtual environments with vext
    Vext is known to break exactly like this.
    You can try :py3 import logging; print( [logging.getLogger(name) for name in logging.root.manager.loggerDict] )
    Adrian Moreno Zapata
    @amorenoz_gitlab
    Interesting...I did install vext for a quick experiment.... let me remove it from my virtualenv
    awesome catch @bstaletic !
    [<Logger vext (ERROR)>, <Logger ycmd (WARNING)>, <Logger ycm.client.base_request (INFO)>, <Logger ycm.client (INFO)>, <Logger ycm (INFO)>, <Logger ycm.client.completion_request (INFO)>, <Logger ycm.client.resolve_
    completion_request (INFO)>, <Logger ycm.client.signature_help_request (INFO)>, <Logger ycm.client.messages_request (INFO)>, <Logger pydocstyle.utils (WARNING)>, <Logger pydocstyle (WARNING)>, <Logger concurrent.fu
    tures (WARNING)>, <Logger concurrent (WARNING)>]
    removed vext and logs are back to normal:
    [<Logger ycmd (WARNING)>, <Logger ycm.client.base_request (INFO)>, <Logger ycm.client (INFO)>, <Logger ycm (INFO)>, <Logger ycm.client.completion_request (INFO)>, <Logger ycm.client.resolve_completion_request (INF
    O)>, <Logger ycm.client.signature_help_request (INFO)>, <Logger ycm.client.messages_request (INFO)>, <Logger pydocstyle.utils (WARNING)>, <Logger pydocstyle (WARNING)>, <Logger concurrent.futures (WARNING)>, <Logg
    er concurrent (WARNING)>]
    Boris Staletic
    @bstaletic

    It's so annoying that it breaks vim like that... It took us forever to diagnose this the second time.

    Why, Boris? What happened to diagnosing the first time someone had this problem?

    Well... we failed to figure it out! Vext should burn!

    Adrian Moreno Zapata
    @amorenoz_gitlab
    :D
    Thanks anyway for the quick response! You folks rock!
    Boris Staletic
    @bstaletic
    Welcome! You're definitely lucky that you aren't the first with this problem, so we didn't have to use you for the better part of the day to figure this out.
    Boris Staletic
    @bstaletic
    It's even using a null handler.
    hansioux
    @hansioux

    I'm trying to get ycm up and running on Ubuntu 21.04. When I run install.py, I get stuck on compiling for boost parts object_operators.cpp, which when I google I couldn't find any information on.

    The command:
    ~/.vim/bundle/YouCompleteMe$ python3 ./install.py -all

    The error:

    Building CXX object BoostParts/CMakeFiles/BoostParts.dir/libs/python/src/object_operators.cpp.o
    In file included from /usr/include/boost/parameter/name.hpp:50,
                     from /home/user/.vim/bundle/YouCompleteMe/third_party/ycmd/cpp/BoostParts/boost/graph/named_function_params.hpp:19,
                     from /home/user/.vim/bundle/YouCompleteMe/third_party/ycmd/cpp/BoostParts/boost/graph/breadth_first_search.hpp:23,
                     from /home/user/.vim/bundle/YouCompleteMe/third_party/ycmd/cpp/BoostParts/libs/python/src/object/inheritance.cpp:7:
    /usr/include/boost/parameter/keyword.hpp:405:38: error: ‘default_r_’ is not a member of ‘boost::parameter::aux’; did you mean ‘default_’?
      405 |           , ::boost::parameter::aux::default_r_<Tag,Default const>
          |                                      ^~~~~~~~~~
          |                                      default_
    /usr/include/boost/parameter/keyword.hpp:405:38: error: ‘default_r_’ is not a member of ‘boost::parameter::aux’; did you mean ‘default_’?

    Is there anything that could fix this?

    hansioux
    @hansioux
    Uh... I don't what what I did to fix it. However, I've since installed cscope, exuberant-ctags, neovim, and python-is-python3. One of them did the trick and now install.py can complete all compilation...
    Boris Staletic
    @bstaletic
    @hansioux The problem was that you hadnt updated YCM in years
    Boris Staletic
    @bstaletic
    Offtopic, but I know there are at least two Arch users listening. Can anyone help me change my AUR email?
    mark2185
    @mark2185
    I finally get to play the "I'm gonna need more info than that" card against Boris
    Boris Staletic
    @bstaletic
    @mark2185 Steps to repro:
    1. Open aur.arhclinux.org and login.
    2. Click on "My Account"
    3. 2nd text box is email. Change it and click save.
    4. See error "Invalid password"
    5. Try again, but this time also change the password at the same time.
    6. See error "invalid password"
    7. Try again, but only with changing the passowrd.
    8. Error "invalid password"
    Ben Jackson
    @puremourning
    but to change your eamil you'll have to tell us your password
    Boris Staletic
    @bstaletic
    I don't want to change password, just email.
    Ben Jackson
    @puremourning
    who said anything about chaging password .0 << >> << >_>
    i didn't ninja edit
    no
    not me
    Boris Staletic
    @bstaletic
    You could have got away with your ninja edit. I just woke up.
    mark2185
    @mark2185
    @bstaletic have you tried rebooting?
    I'll try it now, gimme a sec
    Boris Staletic
    @bstaletic
    Rebooting AUR?
    mark2185
    @mark2185
    No no, your router obv
    Your bad-jokes processing unit hasn't woken up yet, it seems
    Boris Staletic
    @bstaletic
    Definitely isn't.
    mark2185
    @mark2185
    Hmmmm
    May be a dumb question, but
    Did you input your password in the last field?
    I.e. not changing your password, but the "To confirm the profile changes, please enter your current password:"
    And then you input hunter2
    Boris Staletic
    @bstaletic
    Obviously I didn't, because I didn't see that field. I did find it odd that there was no confirmation, but I thought "okay, so that's why I have to 'change' the password at the same time".
    The account, staletic, has been successfully modified.
    Thanks.
    mark2185
    @mark2185
    No problem, I'm glad it worked.