Skip to content

Search in folder stopped working #1127

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
elgandoz opened this issue Oct 30, 2019 · 20 comments
Closed

Search in folder stopped working #1127

elgandoz opened this issue Oct 30, 2019 · 20 comments
Assignees
Labels
bug Something isn't working

Comments

@elgandoz
Copy link

elgandoz commented Oct 30, 2019

  • code-server version: 2.1662-vsc1.39.2
  • OS Version: Centos/RHEL 7

Description

Searching a string in files, in a non-ignored folder, doesn't return any result, regardless of settings or type.
It looks somehow a regression from #438.

Reverting to 2.1650-vsc1.39.2, using the exact same configuration, works as expected.
I also tried to remove the configuration (thus starting with a fresh one) to make sure the issue doesn't sit there, but I get the same behavior.

I didn't try on version 2.1655-vsc1.39.2 (yet).

Steps to Reproduce

  1. In the file explorer, right click on a folder > Find in Folder...
  2. Type a string expected to be found and hit enter
  3. The result is empty, even if you extend the search to all files
@elgandoz elgandoz added the bug Something isn't working label Oct 30, 2019
@code-asher
Copy link
Member

code-asher commented Oct 30, 2019 via email

@elgandoz
Copy link
Author

Thanks for fixing it!

@roflcoopter
Copy link

@code-asher This issue seems to be again present in the latest release.
reverting back to tag 2.1697-vsc1.39.2 makes Find in Folder work again.

@muhammadnscorp
Copy link

@code-asher Find in Folder not working in
Version: 1.41.1
Code Server Version: 2.1698-vsc1.41.1

@nhooyr
Copy link
Contributor

nhooyr commented Feb 19, 2020

Is there an error?

@nhooyr nhooyr reopened this Feb 19, 2020
@kylecarbs
Copy link
Member

It's working for me on 2.1698-vsc1.41.1.

@muhammadnscorp
Copy link

image

@muhammadnscorp
Copy link

Its working on HTTPS but not on HTTP. Dont know if that is an intended behavior, if that is then its working fine.

@kylecarbs
Copy link
Member

kylecarbs commented Feb 20, 2020

Did you remove /tmp/code-server?

On launch, code-server unpacks rg into that dir.

@muhammadnscorp
Copy link

I tried that and it's working now. thanks @kylecarbs

@roflcoopter
Copy link

This does not work still. Find in folder only applies to files that are open in the editor.
I am on the latest build from docker. No error is being printed

@nhooyr nhooyr reopened this Feb 20, 2020
@kylecarbs
Copy link
Member

@roflcoopter does /tmp/code-server/rg exist on your machine?

@roflcoopter
Copy link

Yes it's there

root@67ec5bfc0290:/tmp/code-server# ls
rg
root@67ec5bfc0290:/tmp/code-server#

@kylecarbs
Copy link
Member

@roflcoopter is it executable? I'm not sure how you'd be unable to search in folders without an error appearing 🤔

@nhooyr
Copy link
Contributor

nhooyr commented Feb 21, 2020

He also said it only works on open files which is interesting.

@roflcoopter
Copy link

Yes it is executable. I have seen this issue mentioned in the vscode repo, I'm gonna try to setup a fresh install and see if that works.

@kylecarbs
Copy link
Member

That'd be great!

@roflcoopter
Copy link

Got some time to test this out.
I created a new container based off of the official codercom/code-server:latest, all default settings.
I created som files and tried to search, but the results only show up if i have the files opened in the editor still. This is what the trace log says, not sure if it helps.

[2020-02-23 19:48:25.217] [remoteagent] [trace] telemetry/searchResultsShown {"properties":{"options.wordSeparators":"`~!@#$%^&*()-=+[{]}\\|;:'\",.<>/?","scheme":"file","common.machineId":"redacted","sessionID":"redacted","commitHash":"f51e045cd5483561afc07694f39307fb673b6d1d","version":"2.1698-vsc1.41.1","common.platformVersion":"4.15.0","common.platform":"Linux","common.nodePlatform":"linux","common.nodeArch":"x64","common.product":"code-server","timestamp":"2020-02-23T19:48:25.217Z"},"measurements":{"count":0,"fileCount":0,"options.isRegExp":0,"options.isCaseSensitive":0,"options.isWordMatch":0,"duration":1,"searchOnTypeEnabled":1,"common.timesincesessionstart":145377,"common.sequence":68}}
[2020-02-23 19:48:25.239] [remoteagent] [trace] telemetry/searchResultsShown {"count":0,"fileCount":0,"options":{"isRegExp":false,"isCaseSensitive":false,"isWordMatch":false,"wordSeparators":"`~!@#$%^&*()-=+[{]}\\|;:'\",.<>/?"},"duration":1,"scheme":"file","searchOnTypeEnabled":true}
[2020-02-23 19:48:25.240] [remoteagent] [trace] telemetry/searchResultsFinished {"properties":{"common.machineId":"redacted","sessionID":"redacted","commitHash":"f51e045cd5483561afc07694f39307fb673b6d1d","version":"2.1698-vsc1.41.1","common.platformVersion":"4.15.0","common.platform":"Linux","common.nodePlatform":"linux","common.nodeArch":"x64","common.product":"code-server","timestamp":"2020-02-23T19:48:25.239Z"},"measurements":{"duration":1,"common.timesincesessionstart":145399,"common.sequence":69}}
[2020-02-23 19:48:25.243] [remoteagent] [trace] telemetry/searchResultsFinished {"duration":1}
[2020-02-23 19:48:25.244] [remoteagent] [trace] telemetry/searchResultsFirstRender {"properties":{"common.machineId":"redacted","sessionID":"redacted","commitHash":"f51e045cd5483561afc07694f39307fb673b6d1d","version":"2.1698-vsc1.41.1","common.platformVersion":"4.15.0","common.platform":"Linux","common.nodePlatform":"linux","common.nodeArch":"x64","common.product":"code-server","timestamp":"2020-02-23T19:48:25.243Z"},"measurements":{"duration":1,"common.timesincesessionstart":145403,"common.sequence":70}}
[2020-02-23 19:48:25.246] [remoteagent] [trace] telemetry/searchResultsFirstRender {"duration":1}

@code-asher
Copy link
Member

code-asher commented Mar 5, 2020

I'm curious if 3.0.0 fixes this. We have a 3.0.0 Docker tag if you have some time to check it out. I just ran it and was able to search without any issues (on both HTTP and HTTPS).

@roflcoopter
Copy link

I'm curious if 3.0.0 fixes this. We have a 3.0.0 Docker tag if you have some time to check it out. I just ran it and was able to search without any issues (on both HTTP and HTTPS).

Sorry for the late reply, but yes 3.0.0 seems to fix it! I Haven't move over to it just yet i just did a quick smoke test. You can close this for now and I'll report back if it doesnt work in the future

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants