Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Issues with the sentry-native submodule #4612

Copy link
Copy link
@jamescrosswell

Description

@jamescrosswell
Issue body actions

Description

Sometimes when creating a fresh clone of the repository, trying to fetch/pull from the remote fails with:

Fetching submodule modules/Ben.Demystifier
Fetching submodule modules/perfview
Fetching submodule modules/sentry-native
Fetching submodule modules/sentry-native/external/benchmark
fatal: cannot chdir to '../../../../../../../modules/sentry-native/external/benchmark': No such file or directory
Fetching submodule modules/sentry-native/external/breakpad
fatal: cannot chdir to '../../../../../../../modules/sentry-native/external/breakpad': No such file or directory
Fetching submodule modules/sentry-native/external/crashpad
fatal: cannot chdir to '../../../../../../../modules/sentry-native/external/crashpad': No such file or directory
Fetching submodule modules/sentry-native/external/libunwindstack-ndk
fatal: cannot chdir to '../../../../../../../modules/sentry-native/external/libunwindstack-ndk': No such file or directory
Fetching submodule modules/sentry-native/external/third_party/lss
fatal: cannot chdir to '../../../../../../../../modules/sentry-native/external/third_party/lss': No such file or directory
Errors during submodule fetch:
	external/benchmark
	external/breakpad
	external/crashpad
	external/libunwindstack-ndk
	external/third_party/lss
Errors during submodule fetch:
	modules/sentry-native

This may be related to an issue I bumped into some time ago... ultimately it's missing a commit in mini_chromium. It can be resolved manually be removing the remote that's configured for that submodule presently and adding git@github.com:getsentry/mini_chromium.git instead (since the commit that's checked out for that submodule only exists on our fork - not on the upstream origin).

We should try to address this permanently. I still haven't figured out a way to reliably reproduce the issue - although I'm bumping into it much more frequently since switching to using git worktrees for my workflow.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    Status

    No status
    Show more project fields

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.