primordic/IssueDupesLite huggingface dataset:
Repository: powerline/powerline

Issue #1652: Gnome 3.22 support
Created: 2016-10-01T10:02:49Z
Here is what I see after Gnome 3.22 upgrade:

Duplicate issue #1671: tmux duplicates statusline on every refresh of the powerline status
Created: 2016-10-29T11:42:11Z
Hello,
I have tried to use powerline with tmux but, for some reasons, tmux is duplicating the statusline on every time the data of one of the right segments is modified (for example, the CPU load, the time or the uptime)
I am currently using MATE Terminal, but I have also been able to replacate this bug on other term emulators: urxvt, xterm, termite and Tilda.

The bug on MATE Terminal
I am pretty sure powerline is at cause here, I have try to modify the POWERLINE_COMMAND variable, and the problem stopped. I have also managed to stop the duplication by setting the value of my right segment to something else (for instance : set status-right 1).
Another thing I managed to spot is that sometimes, when I start pwerline for tmux, an odd string appears in my left segment. It happens rather fast, so I've not been able to take a screencap, but it was something like "<env $POWERLI"
EDIT : just after finishing writing this report, I actually managed to take a screenshot of the string :

Closing comment (2016-10-29T12:20:13Z): Duplicate of #1652. Also see #1502.
Repository: powerline/powerline

Issue #250: powerline makes vim's inital start-up screen vanish
Created: 2013-02-21T23:04:51Z
The page that vim shows when starting, shows briefly (along with a 0 in the statusline, #243) and then, powerline shows up and this screen vanishes.
Probably has to do powerline redrawing the screen.
It's not really that important, but I actually kind of liked seeing that screen...

Duplicate issue #582: Vim start up screen no longer shows with powerline sourced
Created: 2013-07-03T18:47:59Z
I've finally identified by bisection of all bundles installed using vundle, powerline makes vim start to a blank screen instead of the default start screen showing "Vi Improved..."
It is a slight annoyance because it was peculiar and I've only noticed it recently but nothing intolerable. Not sure if we could get a fix for this.

Closing comment (2014-01-17T22:30:01Z): Duplicate of #250.
Repository: powerline/powerline

Issue #783: Revised themes
Created: 2014-02-04T18:14:42Z
Just like with themes I suggest to have themes hierarchy. Main reasons:

Make it easy to get rid of powerline fancy characters.
Some bit of deduplication.

Changes to config.json:

Move common dictionary keys to themes.
Add default_top_theme key with string value.
Add ext/{ext}/top_theme key with string value.

Hierarchy:

themes/{top_theme}.json. Contains segment_data key with strings, dividers and spaces keys moved from config.json/common. Themes available by default:

powerline.json or fancy.json: uses symbols defined in powerline fonts.
unicode.json: uses unicode symbols commonly found in fonts.
ascii.json: uses only symbols from ASCII table.
(optional) powerline_compact.json and/or unicode_compact.json: contains reduced number of spaces.


themes/{ext}/__main__.json. Contains keys for renderers like term_truecolor.
themes/{ext}/{theme}.json. Contains what is left: list of segments, some segment_data which does not fit in top-level theme (or maybe a zero level for this: I am talking about things like user/password for IMAP segment, only_if_ssh for hostname and dir_limit_depth for cwd segments?).

Duplicate issue #894: Disable special glyphs
Created: 2014-06-23T22:41:26Z
Would like to see a documented option to disable the special font glyphs in powerline entirely, and just display like the old vim-powerline default.
Some combinations of systems, finicky and complex X font servers, terminal emulators, etc appear to make the task of setting up the special fonts labor intensive, if not impossible. Have personally never been able to get patched fonts to work with rxvt-unicode, for example, despite many hours invested and numerous attempts.
An option to disable this feature altogether would allow users to simply skip this potentially-problematic task if desired, and might reduce the number of people forced to continue using the deprecated vim-powerline.

Closing comment (2014-06-24T03:32:52Z): Duplicate of #783.
Repository: powerline/powerline

Issue #850: powerline
Created: 2014-03-27T15:04:40Z
I'm getting the following message when trying to configure Powerline with Bash on Ubuntu 13.10:
bash: /home/ME/.local/lib/python2.7/site-packages/powerline/bindings/bash/../../../scripts/powerline: No such file or directory

Duplicate issue #1960: powerline bash binding looking for powerline-config in the wrong directory on macos
Created: 2018-11-05T20:10:35Z
attempted to launch powerline after installing using these instructions.
. ./Library/Python/3.7/lib/python/site-packages/powerline/bindings/bash/powerline.sh

Got this error:
. ./Library/Python/3.7/lib/python/site-packages/powerline/bindings/bash/powerline.sh
-bash: ./Library/Python/3.7/lib/python/site-packages/powerline/bindings/bash/../../../scripts/powerline-config: No such file or directory
-bash: ./Library/Python/3.7/lib/python/site-packages/powerline/bindings/bash/../../../scripts/powerline-config: No such file or directory

seems the file is actually here: ~/Library/Python/3.7/bin/powerline-config and not in the scripts directory.
I got it working with: ln -s  ~/Library/Python/3.7/bin ~/Library/Python/3.7/lib/python/site-packages/powerline/bindings/bash/../../../scripts but that seems suboptimal.
install info
Name: powerline-status
Version: 2.7
Summary: The ultimate statusline/prompt utility.
Home-page: https://github.com/powerline/powerline
Author: Kim Silkebaekken
Author-email: kim.silkebaekken+vim@gmail.com
License: MIT
Location: /Users/me/Library/Python/3.7/lib/python/site-packages
Requires: 
Required-by:

Closing comment (2018-11-07T15:06:13Z): This looks related to #850
Repository: powerline/powerline

Issue #835: powerline fails to render with newest psutil (v2)
Created: 2014-03-11T21:24:42Z
at least that’s what i guess broke it, as it’s the only thing used by powerline that was changed on my system.
2014-03-11 22:22:21,677:ERROR:shell:powerline:Failed to render: coercing to Unicode: need string or buffer, instancemethod found                                                               
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/powerline/__init__.py", line 435, in render
    return self.renderer.render(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/powerline/renderers/zsh_prompt.py", line 38, in render
    *args, **kwargs
  File "/usr/lib/python2.7/site-packages/powerline/renderer.py", line 208, in render
    segments = [self._get_highlighting(segment, mode) for segment in segments
  File "/usr/lib/python2.7/site-packages/powerline/theme.py", line 120, in get_segments
    segment['contents'] = segment['before'] + u(segment['contents'] if segment['contents'] is not None else '') + segment['after']
  File "/usr/lib/python2.7/site-packages/powerline/lib/unicode.py", line 13, in u
    return unicode(s, 'utf-8')
TypeError: coercing to Unicode: need string or buffer, instancemethod found
coercing to Unicode: need string or buffer, instancemethod found

Duplicate issue #832: Updated powerline, now my command line is a mess
Created: 2014-03-10T21:14:34Z
I update powerline daily and today I get this after the update
2014-03-10 23:11:29,766:ERROR:shell:powerline:Failed to render: coercing to Unicode: need string or buffer, instancemethod found
Traceback (most recent call last):
  File "/usr/local/Cellar/python/2.7.6/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/powerline/__init__.py", line 435, in render
    return self.renderer.render(*args, **kwargs)
  File "/usr/local/Cellar/python/2.7.6/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/powerline/renderers/zsh_prompt.py", line 38, in render
    *args, **kwargs
  File "/usr/local/Cellar/python/2.7.6/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/powerline/renderer.py", line 208, in render
    segments = [self._get_highlighting(segment, mode) for segment in segments
  File "/usr/local/Cellar/python/2.7.6/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/powerline/theme.py", line 120, in get_segments
    segment['contents'] = segment['before'] + u(segment['contents'] if segment['contents'] is not None else '') + segment['after']
  File "/usr/local/Cellar/python/2.7.6/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/powerline/lib/unicode.py", line 13, in u
    return unicode(s, 'utf-8')
TypeError: coercing to Unicode: need string or buffer, instancemethod found
coercing to Unicode: need string or buffer, instancemethod found

Closing comment (2014-03-13T15:37:21Z): Yes. Thus I am marking it as duplicate of #835.
Repository: powerline/powerline

Issue #815: Add min_cursor_columns option
Created: 2014-02-21T04:20:54Z
I remember this enhancement already discussed: make powerline be able to automatically leave some space for the user cursor in various shell implementations. I do not think this is doable without powerline-daemon so it depends on it being merged.
Proposed location: themes.

Duplicate issue #814: Add min_cursor_columns option
Created: 2014-02-20T17:52:52Z
I remember this enhancement already discussed: make powerline be able to automatically leave some space for the user cursor in various shell implementations. I do not think this is doable without powerline-daemon so it depends on it being merged.

Closing comment (2014-08-10T13:23:11Z): Duplicate of #815..
Repository: powerline/powerline

Issue #1727: tmux master branch version issue
Created: 2017-02-22T17:18:22Z
Hello,
when compiling the tmux from source (master branch). tmux -V shows "master" as the version number. This causes "source .powerline/powerline/bindings/tmux/powerline.conf" to fail. If I checkout the latest tag of tmux so that tmux -V shows a version number e.g. 2.3 - "source .powerline/powerline/bindings/tmux/powerline.conf" works fine.

Duplicate issue #1734: `powerline-config tmux setup` fails when using tmux compiled from github master since tmux commit c034670
Created: 2017-03-06T23:04:54Z
In commit c034670 to the tmux repo, powerline-config tmux setup has returned the following error:
Traceback (most recent call last):
  File "/usr/local/bin/powerline-config", line 22, in <module>
    args.function(pl, args)
  File "/usr/local/lib/python2.7/dist-packages/powerline/commands/config.py", line 15, in __call__
    self.function(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/powerline/bindings/config.py", line 181, in tmux_setup
    tmux_version = get_tmux_version(pl)
  File "/usr/local/lib/python2.7/dist-packages/powerline/bindings/tmux/__init__.py", line 79, in get_tmux_version
    major, minor = version_string.split('.')
ValueError: need more than 1 value to unpack

This is due to tmux author @nicm removing the version number from configure.ac so that tmux -V now returns tmux master instead of tmux 2.4.

programs should not rely on the format of tmux -V

For reference:
tmux/tmux@c034670
tmux/tmux#810

Closing comment (2017-03-18T15:23:32Z): duplicate of #1727
@ZyX-I I think this should be closed too?
Repository: powerline/powerline

Issue #1502: tmux status-right w/ powerline shows code briefly before rendering
Created: 2015-11-24T17:20:46Z
I recently made a big version jump up to tmux 2.1 and powerline 2.3 from some ancient version (sorry, don't remember what versions).  Took me a while to get the configs sorted out, but everything seems to be working now except for a strange rendering issue in tmux.  When I first switch windows in a tmux session, the status-right will flash showing code, then usually in less than a second it resolves to render the segments.
Here is what it looks like when it flashes the code:

And then when it resolves <1sec later:

I honestly don't know if this is a bug in tmux, powerline, or my config, but it is quite distracting when I'm working on something and I'd really appreciate any help figuring out the cause.

Duplicate issue #1544: tmux-powerline: environment variable pops up in tmux 2.1 statusbar
Created: 2016-03-16T07:58:26Z
More information: https://bugzilla.redhat.com/show_bug.cgi?id=1318155

Closing comment (2016-03-16T10:29:39Z): Duplicate of #1502.
Repository: powerline/powerline

Issue #1584: Broken after upgrade to Ubuntu Xenial
Created: 2016-04-25T22:44:29Z
After upgrading the Ubuntu release, vim does not start with the Powerline anymore. No idea why.
And I see this every time
~/D/abc ❯❯❯ vi                                                                                 develop ✭
You need vim compiled with Python 2.6, 2.7 or 3.2 and later support
for Powerline to work. Please consult the documentation for more
details.
Press ENTER or type command to continue

In your documentation I couldn't find any hints on how to fix the above.

Duplicate issue #1587: Python warning at startup
Created: 2016-05-04T22:07:37Z
I see this every time
~ ❯❯❯ vi
You need vim compiled with Python 2.6, 2.7 or 3.2 and later support
for Powerline to work. Please consult the documentation for more
details.
Press ENTER or type command to continue

Any ideas why? It didn't happen before I upgraded Ubuntu to 15.04 ...

Closing comment (2016-05-04T22:09:46Z): You have this warning because your Vim is compiled without Python support. This is exactly what warning tells you. I cannot say why you got such Vim, but in any case this is duplicate of #1584 and this is not a powerline issue.
Repository: ppy/osu-web

Issue #1709: New beatmap listing page - Thumbnail improvement suggestion
Created: 2017-11-11T13:01:33Z
Since the new thumbnails will be bigger size but only a portion of the background image used by a map, I think it should be made so that the mapper could select the portion of his background which gets used in the thumbnail. This map for example has the thumbnail pic taken of probably the worst possible position unless you have a feet fetish (https://puu.sh/yjDdD/bde73fc2ca.png). I don't think it would be necessary to integrate that into a new window but just rather use "move cursor" integrated so that you can move it on the listing page. I guess this is quite nitpicky but in case it isn't too hard to implement then it would just be a nice quality of life update.

Duplicate issue #7449: Allow repositioning of thumbnail in the new beatmap cards
Created: 2021-04-09T13:38:52Z
saw this tweet earlier which is kind of gaining traction as i wrote this issue post : http://twitter.com/iljaaz/status/1380512392099024901
in short some of the thumbnails that are being auto-generated by the new beatmap cards aren't highlighting the background properly. in some cases they would end up in a super awkward crop of the bg image as follows :




edit : i've just been told that apparently some of the cuts can end up being very visually explicit indeed http://twitter.com/Ryuusei_Aika/status/1380517124230184963 D:

Closing comment (2021-04-09T13:42:29Z): similar to #1709
Repository: ppy/osu-web

Issue #9594: Soft beatmap deletion being available for moderators to see
Created: 2022-12-06T02:31:49Z
New issue as solicited here #9572
This should tackle the point 2 made initially, which was availability for the background, but as Peppy said, it is just better to have it accessible to moderators to prevent beatmap duplication or other uploads being necessary.
The end goal is to have the contents accessible by moderators (GMT/NAT) after the deletion, with some kind of visibility or disclaimer being available for us to know it has in fact been deleted, so we don't confuse ourselves.
I was also thinking that, with the page being available, we could also possibly be able to restore beatmaps that have been deleted by mistake (like what happened with a beatmap recently that got deleted by inappropriate background but it could just be changed, as it wasn't anything egregious) but that surely needs discussion beforehand.
Edit: as talked with ppy now, not worth the effort of putting a restoration button, so only the visibility should be good.

Duplicate issue #9572: Beatmap removal tweaks
Created: 2022-12-01T07:16:45Z
The beatmap deletion command on ASS could use a few tweaks:
1 - BanchoBot is always the operator, it should probably be the person who uses the command, just like .s and .rm
2 - We don't have a copy of the background of the map, it would be VERY useful to have it, just like removing covers and avatars leave a logged copy. Inappropriate background removals are one of the most common ones, so it is very important.
3 - We could also make use of specifying reasons on the command, so it gets tracked better if the removal reason isn't really that obvious.
In case such reason can be appended on the support mail template, it would be very useful for the person to immediately know what was the cause behind it.

Closing comment (2022-12-06T02:35:43Z): Points 1 and 3 have been solved, point 2 now being tracked in #9594, will close it now.
Repository: ppy/osu-web

Issue #6915: Hype is null on beatmaps in the graveyard
Created: 2020-11-30T13:36:54Z
Originally made a tweet about it, but I was told to bring it here as an issue.
It’s pretty straightforward. Beatmaps that are WIP/Pending show 0/0 hypes and will do the same hovering over the hype icon. While graveyarded maps do not show 0/0 next to the hype icon and when hovering over it, it’ll show null/null.
A screenshot should be included in this issue.

Duplicate issue #6926: Hype counter showing null/null instead of 0/0
Created: 2020-12-02T19:22:06Z
As of recently it has come to my attention that the hype counter frequently will show null/null instead of the usual 0/0
Heres a screencap of it:

Closing comment (2020-12-02T20:12:29Z): duplicate of #6915, it was meant to be fixed by #6919 though 🤔
Repository: ppy/osu-web

Issue #3191: Modding V2 Copy-paste notes doesn't show correctly on Editor
Created: 2018-05-14T07:13:09Z
Problem Details:
I don't know if it is a known problem or some sort. I just found this problem and deal with it for some time.
And so, when i copy these certain notes highlighted and paste it on the v2 site modding thread. When i click it to see in the editor it won't show highlighted (apparently it should show highlighted to tell which it is, modding v1 has it.) It is however confusing for the Mapper which the Modder is pertaining to. (I tried it on other maps well same problem still)
Video or screenshot showing the problem:
When i copy paste this on site V2 modding thread

When i click the timeline code to see it on the editor it shows this exactly. Not the same to which i copy-pasted. (Not highlighted, it should be highlighted at it is)

osu! version: 20180510.4 (latest)

Duplicate issue #3837: Open timestamp result in "invalid format"
Created: 2018-10-26T14:49:58Z
When clicking on a timestamp in a modding osu://edit/00:42:553 (42553|1) i get the message "invalid format"
What would be the right format? Or is this a issue in the client?
osu://edit/00:20:184 (20184|2,20805|1)

Closing comment (2018-10-31T03:10:45Z): Probably same as #3191.
Repository: ppy/osu-web

Issue #5998: Add more filters to beatmap search
Created: 2020-05-08T19:49:42Z
Add to beatmap search form more filters such as:

OD, CS, AR, HP
BPM
Length
Streams, jumps? (very useful btw)
And also maybe give an option to choose star rating, because recommended diff isn't right in most cases.

Duplicate issue #7153: suggestion for the site (star rating)
Created: 2021-02-02T21:01:16Z
hello hello, I have a suggestion that more than one player would like to see on the site in order to improve the user experience but also the convenience of the site.
indeed it would be comfortable to add the option "star rating" on the osu! website in order to classify the level of the proposed beatmap, for example in my case I would have liked it to be there in order to select this option in the 6.80-7.90 stars configuration.

Closing comment (2021-02-02T21:07:12Z): Duplicate of #5998
Repository: ppy/osu-web

Issue #1173: Voting on feature requests
Created: 2017-05-18T11:40:54Z
We need to display current star priority at a minimum

Duplicate issue #3768: Display star rating in Feature Request forum listing
Created: 2018-10-08T20:07:51Z

Closing comment (2018-10-09T04:05:58Z): Closing as duplicate of #1173.
Repository: ppy/osu-web

Issue #2428: Hyperlink beatmap source as a search term
Created: 2018-02-16T03:28:31Z
It should be the same as tags.

Duplicate issue #2767: Source on beatmap information page isn't clickable
Created: 2018-03-22T03:31:51Z
It should be a clickable link to take you automatically to a beatmap search using it as your search term, just like the title and artist are. It is clickable for this purpose on the old website as well.

Closing comment (2018-03-22T04:38:09Z): Duplicate of #2428.
Repository: ppy/osu-web

Issue #1692: Favourites missing on new beatmap listing
Created: 2017-11-07T08:39:34Z
Now that the new beatmap listing is being forced on maps even though it feels unfinished I wanted to ask for hotfix on something that not only I found annoying but other mappers aswell.
All favourites on a map are now treated as a tiny number and the mapper can't tell at all who have favourited the map and that is really frustrating. I think looking at who I have impressed enough to make them favourite my maps is the thing I look at the most when I check out how the listings of my maps are doing and making that just a tiny number besides playcount is just mind boggling to me. Please bring the old way of showing favourites back incorporated to the new website design or even better, make it so that there is a dropdown list for ALL of the favourites the map has gotten. I also think that seeing names you can recognize having favourited a map gives you immediate feedback on how good the map is and if it is worth downloading to some degree.
Thank you for your time!

Duplicate issue #1781: Display people who favourited the map on beatmap page v2?
Created: 2017-11-20T11:33:35Z
hello using github for the first time here,
I've asked mappers/the community a bit around and there seems to be a decent demand for displaying which people favourited map just like beatmap page v1
Is this ever going to comeback? It was one of those things i really liked, if not? then this is just an idea.

Closing comment (2017-11-20T11:40:56Z): Hi, this is duplicate of #1692.
Repository: ppy/osu-web

Issue #4798: Add scope to users endpoints
Created: 2019-08-17T07:50:01Z
Please add a scope to the api/v2/users/{user}/ endpoints to make them accessible.

Duplicate issue #5630: Enable getting profile "me!" data via API
Created: 2020-02-14T07:04:48Z
It would be kinda neat to get the data from different "me!" sections from other profiles so that we can probably use the data to make more neat stuff i.e. Tracking of Beatmap Nominator userpages for easy viewing rather than going to each individual one. It's also cool to see who's available for a bubble whenever they say "Active" or something in their userpages.

Closing comment (2020-02-21T09:21:28Z): duplicate of #4798
Repository: pre-commit/pre-commit-hooks

Issue #794: `file-contents-sorter` Not working same way everytime
Created: 2022-07-29T11:32:45Z
I get strange issue that file-contents-sorter hook does not work same way everytime. I made little test case which trickers the issue. If i run this 10 times it will sometimes pass and sometimes not. I did not have time to look what problem might be.
Add this to file_contents_sorter_test.py
(
    b'pre\nPre\n',
    ['--unique', '--ignore-case'],
    PASS,
    b'pre\nPre\n',
),

And run it with
for run in {1..10}; do pytest tests/file_contents_sorter_test.py; done
This gives me that about 30% pass and 70% fails

Duplicate issue #1105: `file-contents-sorter` doesn't use consistent order with `--ignore-case` option
Created: 2024-10-31T11:00:37Z
I'm trying to use file-contents-sorter to keep a dictionary file sorted, ignoring case. The hook runs fine and updates the file, but when I attempt to commit the changes, it resorts the file again, moving around some entries which differ only in case. If I try to commit those changes, the process repeats.

Closing comment (2025-01-08T23:18:26Z): then that's a dupe of #794
Repository: pre-commit/pre-commit-hooks

Issue #395: Increase json to bypass the option of comment error
Created: 2019-07-22T03:07:46Z
pre-commit-hooks/pre_commit_hooks/check_json.py
    
    
        Lines 17 to 23
      in
      9ce6b9f
    
  
  
    

        
          
           for filename in args.filenames: 
        

        
          
               try: 
        

        
          
                   json.load(io.open(filename, encoding='UTF-8')) 
        

        
          
               except (ValueError, UnicodeDecodeError) as exc: 
        

        
          
                   print('{}: Failed to json decode ({})'.format(filename, exc)) 
        

        
          
                   retval = 1 
        

        
          
           return retval 
        
    
  


When json file check, json can ignore comments with comments when it is used as a configuration file. Increase options to bypass errors

Duplicate issue #695: [check-json]: Support JSON with Comments (JSONC)
Created: 2021-11-25T22:48:17Z
Please :)

Closing comment (2021-11-25T22:56:40Z): dupe #395
Repository: pre-commit/pre-commit-hooks

Issue #656: check-added-large-files does not run correctly in parallel, needs require_serial to work correctly
Created: 2021-10-01T19:31:50Z
check-added-large-files hook does not work properly when multiple large files are present to be staged. It will randomly fail on some of the files each time you run it depending on how it groups the files for parallel execution:
❯ git commit
Check for added large files..............................................Failed
- hook id: check-added-large-files
- exit code: 1

x/a/bigfile (10726 KB) exceeds 10000 KB.
x/c/bigfile (10726 KB) exceeds 10000 KB.
x/b/bigfile (10726 KB) exceeds 10000 KB.
❯ git commit
Check for added large files..............................................Failed
- hook id: check-added-large-files
- exit code: 1

x/c/bigfile (10726 KB) exceeds 10000 KB.
x/a/bigfile (10726 KB) exceeds 10000 KB.
❯ git commit
Check for added large files..............................................Failed
- hook id: check-added-large-files
- exit code: 1

x/b/bigfile (10726 KB) exceeds 10000 KB.
x/a/bigfile (10726 KB) exceeds 10000 KB.

We had to enable require_serial: true in our hook config to get it to work properly. We suspect that the call in the hook to git lfs status --json is not working properly when run multiple times in parallel in the same repo. After adding require_serial: true to our hook config, the commit/check works correctly:
❯ git commit
Check for added large files..............................................Passed

Maybe require_serial: true should be set by default in the pre-commit-hooks repo definition in .pre-commit-hooks.yaml?

Duplicate issue #657: check-added-large-files does not run correctly in parallel, needs require_serial to work correctly (con'd)
Created: 2021-10-01T19:56:37Z
I added a print statement to CalledProcessError that you have in the code:
❯ pre-commit run
Check for added large files..............................................Failed
* hook id: check-added-large-files
* exit code: 1

CalledProcessError happened
CalledProcessError happened
x/a/bigfile (10726 KB) exceeds 10000 KB.
x/c/bigfile (10726 KB) exceeds 10000 KB.
CalledProcessError happened
x/b/bigfile (10726 KB) exceeds 10000 KB.
CalledProcessError happened


You aren't handling errors properly, so I don't know how you can blame git lfs on this. You just return an empty file list, and then the code continues without any indication of an error occurring. It took us an hour just to figure out the hook wasn't running properly even though our file was properly added to LFS. You should at least report that git lfs is erroring out for some reason, not just assume no files were returned.

Closing comment (2021-10-01T19:58:06Z): dupe #656
Repository: pre-commit/pre-commit-hooks

Issue #265: no-commit-to-branch on CI
Created: 2018-02-19T19:51:25Z
As a safety net, we've started running pre-commit on CI, e.g.
git diff --name-only "$GIT_COMMIT"^..."$GIT_COMMIT" | xargs pre-commit run --files

one of our projects uses no-commit-to-branch and we just noticed this behavior on CI:
Don't commit to branch...................................................Failed
hookid: no-commit-to-branch

Traceback (most recent call last):
  File "/var/lib/jenkins/.cache/pre-commit/repoVUdrA6/py_env-python2.7/bin/no-commit-to-branch", line 11, in <module>
    load_entry_point('pre-commit-hooks==1.1.0', 'console_scripts', 'no-commit-to-branch')()
  File "/var/lib/jenkins/.cache/pre-commit/repoVUdrA6/py_env-python2.7/local/lib/python2.7/site-packages/pre_commit_hooks/no_commit_to_branch.py", line 22, in main
    return int(is_on_branch(args.branch))
  File "/var/lib/jenkins/.cache/pre-commit/repoVUdrA6/py_env-python2.7/local/lib/python2.7/site-packages/pre_commit_hooks/no_commit_to_branch.py", line 10, in is_on_branch
    branch = cmd_output('git', 'symbolic-ref', 'HEAD')
  File "/var/lib/jenkins/.cache/pre-commit/repoVUdrA6/py_env-python2.7/local/lib/python2.7/site-packages/pre_commit_hooks/util.py", line 28, in cmd_output
    raise CalledProcessError(cmd, retcode, proc.returncode, stdout, stderr)
pre_commit_hooks.util.CalledProcessError: (('git', 'symbolic-ref', 'HEAD'), 0, 128, u'', u'fatal: ref HEAD is not a symbolic ref\n')

most likely this is not really an issue with pre-commit but with the way our Jenkins jobs are set up (?). I worked around this by using SKIP=no-commit-to-branch pre-commit run but just thought I would let you know.

Duplicate issue #653: Skip `no-commit-to-branch` When `CI` Is Defined
Created: 2021-09-27T20:34:30Z
Many continuous integration platforms set the CI environment variable since it's fairly common for tools to need slightly different settings when running in CI. Presently, one can set the SKIP environment variable to no-commit-to-branch, but it would be ideal for no-commit-to-branch to effectively skip itself in CI. It would probably be necessary to offer an option to disable this behavior (e.g., --enforce-in-ci).

Closing comment (2021-09-27T21:10:16Z): This is not a duplicate. #265 makes no mention of the CI environment variable.
Repository: pre-commit/pre-commit-hooks

Issue #835: forbid-submodules hook fails
Created: 2022-11-10T19:54:39Z
forbid-submodules hook fails with this error:
[ERROR] `forbid-submodules` is not present in repository https://github.com/pre-commit/pre-commit-hooks.  Typo? Perhaps it is introduced in a newer version?  Often `pre-commit autoupdate` fixes this.

Config:
repos:
  - repo: https://github.com/pre-commit/pre-commit-hooks
    rev: v4.3.0
    hooks:
      - id: forbid-submodules

Duplicate issue #837: Published documentation inaccurate
Created: 2022-11-11T22:45:13Z
The published documentation at https://pre-commit.com/hooks.html and https://github.com/pre-commit/pre-commit-hooks/blob/main/README.md appear to reflect the state of the production version of these hooks (v4.3.0), but contains references to forbid-submodules and perhaps other hooks that have been added but are only available in development builds.
This issue was reported in #835 and #816 and workarounds suggested, but discussion of the documentation issue is off topic on those issues.
If the documentation published on pre-commit.com and the main branch cannot reflect the current release state, it may be worth annotating the documentation pages or specific hooks with information about the supported version of the hook.

Closing comment (2022-11-11T22:48:20Z): dupe #835 #816
Repository: pre-commit/pre-commit-hooks

Issue #589: Add check for illegal Windows filenames
Created: 2021-04-22T12:21:02Z
There are file and directory names which are legal in Git and most operating systems but illegal in Windows.  They should be avoided in case a developer happens to use Windows.
The following names are illegal as bare names as well as with extensions regardless of case for files or directories.  For instance CoM6, cOm6.txt, com6.foo.jpg, etc are all illegal.  Windows will refuse to create those files if you try to check them out.
From: https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file

Do not use the following reserved names for the name of a file:
CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9. Also avoid these names followed immediately by an extension; for example, NUL.txt is not recommended. For more information, see Namespaces.

Duplicate issue #899: Windows file verification
Created: 2023-04-24T18:33:29Z
Windows has a bunch of restrictions on file names which can really easily affect repositories that use mainly Posix for development, but have to build some artifacts on Windows. As an example take a Python project where a wheel needs to be able to be compiled on Windows, but someone checked in a file with the name 2023_04_19-13:56:08.json.
My proposal is to add a hook that simply verifies file paths are valid on Windows according to the Windows docs.
Maybe the opposite is also true, devs on Windows could create a file that is invalid on OSX. So this hook should maybe verify for all file path pitfalls of Linux, BSD, OSX, and Windows.
For now I'm just looking for some comments and consideration. Our team could look into contributing this, if people think that this would be useful.

Closing comment (2023-04-24T18:35:11Z): dupe #589
Repository: pre-commit/pre-commit-hooks

Issue #507: Support for conda environment.yml files in requirements-txt-fixer
Created: 2020-07-27T21:22:24Z
It would be very helpful if the requirements-txt-fixer supported conda's environment.yml file format for both pip and conda requirements.  These are being used more widely in the scientific computing community.

Duplicate issue #537: ENH environment-yml-fixer sorter
Created: 2020-12-10T18:09:38Z
I have a local hook which sorts dependencies in conda environment.yml files (analogous to this repo's requirements-txt-fixer) - would that be a welcome addition to pre-commit-hooks?

Closing comment (2020-12-10T18:13:29Z): dupe #507
Repository: prefix-dev/pixi

Issue #771: Tracking issue: PyPI dependencies pixi can't manage yet.
Created: 2024-02-02T19:46:33Z
There are a few PyPI packages pixi can't install yet, where pip can.
Please paste your examples in this issue so we have a list of known packages we can track, test and benchmark with along the way.
Information we would like:


What did you run and what was the outcome?
e.g. pixi add --pypi packagex
If it doesn't recreate in an empty environment please share your pixi.toml that recreates the issue.


What error did pixi return?
e.g.
× RECORD file doesn't match wheel contents: missing hash for mediapipe/version.txt (expected sha256=-fE2KU)



Can pip install the package?
Does pip install packagex work?


What platform are you on?
e.g. linux-64


Did you find a workaround, if so please explain.
e.g. build it into a conda package, using a custom fork, etc.


Your input would greatly help us improve the pixi's experience!
Thanks in advance! ❤️

Duplicate issue #1933: Pixi 0.28.1 breaks pypi dependency installation
Created: 2024-08-28T05:45:00Z
Checks


 I have checked that this issue has not already been reported.


 I have confirmed this bug exists on the latest version of pixi, using pixi --version.


Reproducible example
$ pixi --version
pixi 0.28.1
$ pixi init
✔ Created /home/user/test/pixi.toml
$ pixi add python
✔ Added python >=3.12.5,<4
$ pixi add --pypi ctranslate2==4.3.1
  × failed to solve the pypi requirements of 'default' 'linux-64'
  ├─▶ failed to resolve pypi dependencies
  ╰─▶ Because ctranslate2==4.3.1 has no wheels with a matching Python ABI tag and you require ctranslate2==4.3.1, we can conclude that your requirements are unsatisfiable.

$ pixi list -x
Package  Version  Build               Size      Kind   Source
python   3.12.5   h2ad013b_0_cpython  30.2 MiB  conda  python-3.12.5-h2ad013b_0_cpython.conda
Issue description
It works in Pixi 0.28.0 but not in 0.28.1. Pixi 0.28.1 fails with the error "no wheels with a matching Python ABI tag".
Expected behavior
With pixi 0.28.0
$ pixi self-update --version 0.28.0
✔ Pixi will be updated from 0.28.1 to 0.28.0
✔ Pixi archive downloaded.
✔ Pixi archive uncompressed.
✔ Pixi has been updated to version 0.28.0.
$ pixi init
✔ Created /home/user/test/pixi.toml
$ pixi add python
✔ Added python >=3.12.5,<4
$ pixi add --pypi ctranslate2==4.3.1
✔ Added ctranslate2==4.3.1
Added these as pypi-dependencies.
$ pixi list -x
Package      Version  Build               Size       Kind   Source
ctranslate2  4.3.1                        339.4 MiB  pypi   ctranslate2-4.3.1-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.http.whl
python       3.12.5   h2ad013b_0_cpython  30.2 MiB   conda  python-3.12.5-h2ad013b_0_cpython.conda

Closing comment (2024-08-28T05:45:58Z): It's also reported in #771 (comment)
Repository: prefix-dev/pixi

Issue #379: Weird behavior when using packages that overwrite each other
Created: 2023-10-04T17:17:11Z
Checks


 I have checked that this issue has not already been reported.


 I have confirmed this bug exists on the latest version of pixi, using pixi --version.


Reproducible example
[project]
name = "test-opt"
version = "0.1.0"
description = ""
authors = [""]
channels = ["conda-forge"]
platforms = ["osx-arm64"]

[tasks]

[dependencies]
opt-einsum = "3.0.0.*"
opt_einsum = "3.3.0.*"
open .pixi/env/lib/python3.12/site-packages

Issue description
The opt_einsum directory gets written to by both opt_einsum and opt-einsum (which are two different versions).
Expected behavior
pixi should crash here or print a warning at least.

Duplicate issue #2150: panic: if a file is clobbered it must also be in the registry
Created: 2024-09-28T06:47:07Z
ondrej@laptop:~/repos/gui(master)$ pixi add qt
⠐ updating environment 'default'
  ✔ validate cache       11 packages in 11s 629ms
  ✔ download & extract   11 packages (212.96 MiB) in 11s 627ms
  ⠒ installing packages  [00:00:13] [━━━━━━━━━━━━━━━━━━━━]    11/11       thread 'main' panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rattler-0.27.9/src/install/clobber_registry.rs:205:18:
if a file is clobbered it must also be in the registry
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I think a Rust panic is always a bug, one should catch it and return a user-friendly error instead.

Closing comment (2024-09-30T06:33:09Z): I would agree, @wolfv is figuring this out. The implementation of this was related to : #379
Repository: prefix-dev/pixi

Issue #381: Add a way to show commands executed by pixi run <task>
Created: 2023-10-05T20:58:17Z
Problem description
I have a lot of tasks for executing various commands, would be handy to have -v show the command before running it, would also be handy to have --dry-run to show all commands that would be run by a particular task. This is especially useful to see what runs when a task has dependent tasks

Duplicate issue #438: Print executed tasks
Created: 2023-11-07T11:01:18Z
Problem description
When running tasks, you only see output produced by the tasks themselves.
Especially for tasks with a long chain of dependencies, this can make it hard to see which task is currently being executed.
Let's take the following task
[tasks]
test-rust = "cargo test"
There are two ways to improve its output:

Print the task name "test-rust"
Print the executed command: "cargo test" (similar to just)

Closing comment (2023-11-07T12:35:56Z): Closing because duplicate #381
Repository: prefix-dev/pixi

Issue #815: Improve `system-requirements` UX
Created: 2024-02-16T07:48:32Z
Problem description
Currently a user is getting an error if the "default" system requirements are not sufficient for the dependency that they try to install. This is done regardless of the local system availability.
Now the user needs to understand the error and edit the [system-requirements] table.
It would be a better experience for the user if pixi automatically solves for the local machine and if that results in a more specific set of system-requirements than the default requirements it should automatically add that to the configuration (pixi.toml).

Duplicate issue #263: Issue with examples on linux
Created: 2023-08-17T21:10:30Z
Hi,
Just wanted to say I love what you guys have been doing here. I've been following this project for a little bit and have even used pixi for a small personal project. The workflow was marvelous :).
This week I decided to see if how it would work on linux. Trying the examples I run into the following error...
 ~/pixi/examples/turtlesim
21:06 $ pixi run start
  × The current system has a mismatching virtual package. The project requires '__linux' to be at least version '5.10' but the system has version '3.10.0'

I confirmed the linux version.
21:06 $ uname -r
3.10.0-1062.4.2.el7.x86_64

This still leaves me a little bit of a loss. I don't see any explicit mention of a minimum linux version in the lock/toml file. What is the recommended workflow to resolve this?

Closing comment (2024-03-20T16:00:19Z): @jelber2 we've noted this as an issue we still have to improve the workflow for. It is tracked in #815
Repository: prefix-dev/pixi

Issue #323: Add pixi package to winget
Created: 2023-09-06T07:00:25Z
Problem description
I recently set up a new Windows machine, and I installed almost everything I needed in the PC (including Visual Studio compilers via VS BuildTools) via winget, the Windows Package Manager (https://learn.microsoft.com/en-us/windows/package-manager/), and I found it quite convenient (I never used it before).
I do not feel enough about this at the moment to work directly on this (and mantain the resulting package), but anyhow I thought for dissemination it could be useful to have a pixi package on winget, to streamline installation on Windows. See conda-forge/miniforge#163, microsoft/winget-pkgs#16674 and https://github.com/search?q=repo%3Amicrosoft%2Fwinget-pkgs+CondaForge&type=pullrequests for similar issues/PRs for miniforge.

Duplicate issue #506: winget installer
Created: 2023-11-27T20:12:33Z
Problem description
winget is practically on every windows machine now. it's definitely easier to deal with than the powershell installation instruction or downloading the msi.
related #425

Closing comment (2023-11-29T12:22:38Z): This is a duplicate of #323
Repository: prefix-dev/pixi

Issue #136: Autocompletion of globally installed executables
Created: 2023-06-23T11:27:33Z
When you run
pixi global install pre-commit

You will not have any TAB completion for the pre-commit command.
This is a user experience issue we should solve.
The same holds for the environments in pixi projects where autocompletion in the pixi run would be an awesome addition.

Duplicate issue #372: `pixi run` should invoke the shell's autocompletion
Created: 2023-10-03T10:05:17Z
Problem description
It would be nice to be able to invoke the shell's autocompletion when using pixi run.
pixi run b<tab>
# becomes
pixi run build

# if no matching pixi task is found, the shell's autocompletion could be called
pixi run git ch<tab>
# becomes
pixi run git checkout

Closing comment (2023-10-03T10:16:01Z): Slightly related to #136
Repository: prefix-dev/pixi

Issue #172: Add support for global configuration
Created: 2023-07-03T13:21:45Z
It would be nice to support a global configuration file (for example $XDG_CONFIG_HOME/pixi/pixirc) in which you can specify channel aliases.
Like this, one would be able to support channel mirrors and it's possible not to ship credentials for custom channels in pixi.toml.
Some thoughts:
# all channels are by default "https://path-to-custom-quetz-server/get/<channel-name>"
channel-alias: https://path-to-custom-quetz-server/get

custom-channels:
  - conda-forge:
      http://custom-conda-forge-mirror
  - cf-staging:
      https://conda.anaconda.org/cf-staging
This would allow pixi to be used in locked down systems that don't allow conda-forge without modifying the pixi.toml.

Duplicate issue #523: Global config for Pixi (suppress ps1 change in shell)
Created: 2023-11-29T21:32:26Z
Problem description
Pixi needs a way to set global configuration settings.
Similar to conda config, or maybe inspired from other package managers, if there are better solutions.
I specifically need a way to suppress the change to ps1 when running pixi shell

Closing comment (2023-11-29T21:34:14Z): Duplicate of #172
Repository: presidentbeef/brakeman

Issue #972: False positive (dynamic SQL from a case statement)
Created: 2016-12-06T19:14:26Z
I have code like this:
group_by_col =
      case params[:group_by]
      when 'brand'            then 'brand'
      when 'year'             then 'YEAR(date_utc)'
      when 'month'            then "CONCAT(YEAR(date_utc), '-', LPAD(MONTH(date_utc), 2, '0'))"
      when 'week'             then "CONCAT(YEAR(date_utc), '-', LPAD(WEEK(date_utc, 1), 2, '0'))"
      when 'day'              then "DATE(date_utc)"
      else raise ArgumentError, 'Invalid group by value'
      end

query = "SELECT id, #{group_by_col} AS group_by_col, COUNT(*) FROM records"

rows = Record.connection.select_rows(query)

This gives me a possible SQL injection warning using -w3, and I have no idea how to change it to make brakeman stop complaining.

Duplicate issue #1002: False positive - SQL injection
Created: 2017-02-18T00:36:50Z
subset_clause = case script_subset
	when :greasyfork
		"AND `sensitive` = false"
	when :sleazyfork
		"AND `sensitive` = true"
	else
		""
end
sql =<<-EOF
	SELECT
		text, SUM(daily_installs) install_count, COUNT(s.id) script_count
	FROM script_applies_tos
	JOIN scripts s ON script_id = s.id
	WHERE
		domain
		AND script_type_id = 1
		AND script_delete_type_id IS NULL
		AND !tld_extra
		#{subset_clause}
	GROUP BY text
	ORDER BY text
EOF
by_sites = Script.connection.select_rows(sql)
"Possible SQL injection".

Closing comment (2017-02-18T01:06:02Z): Yeah, same as #972 and #944