Skip to content

Do not try to get xattrs for the root inode#2

Closed
djmaze wants to merge 1 commit into
ppenguin:masterfrom
djmaze:fix-xattrs-for-root-inode
Closed

Do not try to get xattrs for the root inode#2
djmaze wants to merge 1 commit into
ppenguin:masterfrom
djmaze:fix-xattrs-for-root-inode

Conversation

@djmaze

@djmaze djmaze commented Mar 23, 2021

Copy link
Copy Markdown

Otherwise the path in the S3 request is empty, which is invalid.

fixes kahing#522

Doing the PR here since the kahing version seems not maintained anymore and I am using your fork either way.

Otherwise the path in the S3 request is empty, which is invalid.
@djmaze

djmaze commented Mar 26, 2021

Copy link
Copy Markdown
Author

Uh, I guess this changes the plan: kahing@e3748e3

@kjetilho

kjetilho commented Sep 6, 2021

Copy link
Copy Markdown

I applied your patch to kahing/goofys and it worked very well. It would be nice if you submitted it as a PR there, too, or do you still recommend switching to ppenguin's fork?

@djmaze

djmaze commented Jan 15, 2022

Copy link
Copy Markdown
Author

@kjetilho Better late than never.. kahing#672

(Although I guess the kahing version is again out of maintenance.)

djmaze added a commit to djmaze/goofys-docker that referenced this pull request Jan 18, 2022
That fixes a bug with xattrs (see ppenguin/goofys#2)
@btakita

btakita commented Jul 6, 2023

Copy link
Copy Markdown

Hello @djmaze, I'd like to apply this patch via kahing#672. I would also like to get up to date on the latest from https://github.com/kahing/goofys.

I noticed that this repo forks https://github.com/kahing/goofys & there are some unique commits in this repo. Is there a benefit to using the commits from this repo or should I focus solely on kashing/goofys?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

I/O error with third party application

3 participants