question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Git fatal error when using a Kedro project inside directory without an initialised repo

See original GitHub issue

Description

Kedro Docs contains a pandas Iris example project which has Python 3.6 in the requirements file, which does not execute on newer Apple M1 chipsets. Attempting to execute it on an M1-compatible version of Python 3.8.13 via kedro run results in:

kedro.framework.session.store - INFO - `read()` not implemented for `BaseSessionStore`. Assuming empty store.
fatal: Needed a single revision

Context

Attempt the docs instructions on https://kedro.readthedocs.io/en/stable/get_started/example_project.html on an Apple M1.

Steps to Reproduce

Execute the following on an Apple M1:

kedro new --starter=pandas-iris
cd pandas-iris
git init
pip install -r src/requirements.txt
kedro run

Expected Result

Run without fatal errors.

Actual Result

kedro.framework.session.store - INFO - `read()` not implemented for `BaseSessionStore`. Assuming empty store.
fatal: Needed a single revision

Your Environment

Include as many relevant details about the environment in which you experienced the bug:

  • Kedro version used: 0.17.7
  • Python version used (python -V): 3.8.13
  • Operating system and version: macOS 12.3

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:16 (11 by maintainers)

github_iconTop GitHub Comments

1reaction
AntonyMilneQBcommented, Apr 11, 2022

Just to understand where we stand on this… This isn’t actually related to Apple M1 chips at all, right? It’s just what happens if you do kedro run in a directory which hasn’t had git commit yet?

1reaction
oj-mcommented, Apr 5, 2022

@datajoely That’s what initially gave me pause, as I didn’t catch that the fatal error was actually a benign INFO log. Without diving into the codebase, it just wasn’t immediately clear the error was bubbling messaging up from an expected git state.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Git error - Fatal: Not a git repository and how to fix it | Datree.io
This error means you attempted to run a Git command, but weren't inside a Git repository. Make sure you've: Navigated to the right...
Read more >
fatal: Not a git repository (or any of the parent directories): .git
The command has to be entered in the directory of the repository. The error is complaining that your current directory isn't a git...
Read more >
How to Fix the “fatal: not a git repository” Error - ContainIQ
Check that you correctly created the repo. If the directory doesn't contain a .git repo, use git init to properly initialize the repo...
Read more >
Solving “Fatal: Not A Git Repository” (Or Any Of The Parent ...
In this article, we will explore what causes, how to prevent, and how to solve the “fatal: not a git repository” error.
Read more >
Git Error: "Does Not Appear To Be a Git Repository"
At the most basic level, Git is basically indicating that the repository you are trying to work with is unrecognizable as a Git...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found