Skip to content
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

Adjust Windows Installation Instructions to account for Nuclio issue#1821 #5558

Merged
merged 6 commits into from Jan 10, 2023

Conversation

Bytestorm5
Copy link
Contributor

@Bytestorm5 Bytestorm5 commented Jan 8, 2023

Motivation and context

In my understanding of nuclio/nuclio#1821, the Nuctl (1.8.14) CLI is looking for a path that is only valid on a Linux environment, which it does not find when running via Git Bash (even when using the Windows version of Nuctl). However, installing CVAT onto a Linux VM allows Nuctl to locate this path and operate normally. I initially found this when setting up CVAT myself on Git Bash as per the given instructions for Windows 10.

(I am still learning how to use GitHub as far as pull requests / forks / etc work, sorry if this is not the right way to approach this change. Please let me know if I've missed something important.)

How has this been tested?

This is only a change to instructions, but I did test this on multiple machines . As long as the machine is capable of running a Linux kernel it shouldn't run into any issues.

Checklist

  • I submit my changes into the develop branch
  • I have added a description of my changes into CHANGELOG file
  • I have updated the documentation accordingly (Purely documentation changed)
  • I have added tests to cover my changes (Does not change code)
  • I have linked related issues (read github docs) (This doesn't resolve the root issue, rather just works around it; doesn't make sense to cause an automatic close)
  • I have increased versions of npm packages if it is necessary (cvat-canvas,
    cvat-core, cvat-data and cvat-ui)
    (Was not necessary)

License

  • I submit my code changes under the same MIT License that covers the project.
    Feel free to contact the maintainers if that's a concern.

CHANGELOG.md Outdated Show resolved Hide resolved
@nmanovic nmanovic merged commit c29b283 into cvat-ai:develop Jan 10, 2023
Copy link
Contributor

@nmanovic nmanovic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@AstronomyGuy , thanks for the contribution!

@Bytestorm5
Copy link
Contributor Author

@AstronomyGuy , thanks for the contribution!

Glad to help!

mikhail-treskin pushed a commit to retailnext/cvat that referenced this pull request Jul 1, 2023
…1821 (cvat-ai#5558)

In my understanding of nuclio/nuclio#1821, the
Nuctl (1.8.14) CLI is looking for a path that is only valid on a Linux
environment, which it does not find when running via Git Bash (even when
using the Windows version of Nuctl). However, installing CVAT onto a
Linux VM allows Nuctl to locate this path and operate normally. I
initially found this when setting up CVAT myself on Git Bash as per the
given instructions for Windows 10.

(I am still learning how to use GitHub as far as pull requests / forks /
etc work, sorry if this is not the right way to approach this change.
Please let me know if I've missed something important.)

### How has this been tested?
This is only a change to instructions, but I did test this on multiple
machines . As long as the machine is capable of running a Linux kernel
it shouldn't run into any issues.
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.

None yet

2 participants