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

[DepthPacketStreamParser::onDataReceived] not all subsequences received 0 #94

Closed
3 tasks
kafilah opened this issue Apr 15, 2016 · 3 comments
Closed
3 tasks
Labels
needs response Needs a response from the issue/PR author

Comments

@kafilah
Copy link

kafilah commented Apr 15, 2016

Please follow the general troubleshooting steps first:

  • Ran brew update and retried your prior step?
  • Ran brew doctor, fixed as many issues as possible and retried your prior step?
  • If you're seeing permission errors tried running sudo chown -R $(whoami) $(brew --prefix)?

You can erase any parts of this template not applicable to your Issue.

Bug reports:

Please replace this line with a brief summary of your issue.

Feature Requests:

Please note by far the quickest way to get a new feature into Homebrew is to file a Pull Request.

We will consider your request but it may be closed if it's something we're not actively planning to work on.

@kafilah
Copy link
Author

kafilah commented Apr 15, 2016

[DepthPacketStreamParser::onDataReceived] not all subsequences received 0

I keep getting this every time I run a test!

@UniqMartin
Copy link
Contributor

Sorry, but from what you posted it's not obvious whether this is a Homebrew issue or what part of Homebrew the issue is related to. To help us debug this issue, can you explain:

  • What you were trying to do (and why)
  • What happened
  • What you expected to happen
  • Step-by-step reproduction instructions (with as minimal input data as possible)

@UniqMartin UniqMartin added the needs response Needs a response from the issue/PR author label Apr 15, 2016
@apjanke
Copy link
Contributor

apjanke commented Apr 18, 2016

This looks like an issue with the OpenKinect/libfreenect development library. While that can be installed via Homebrew, problems coding with it are probably not due to the Homebrew installation process, and it's not something we support beyond the installation.

I'm closing this out as not a Homebrew problem. If you think this is in fact an issue with Homebrew's installation of libfreenect, and not a problem with OpenKinect itself or your use of it, please re-open an issue on the homebrew/core repo, where we track issues with individual formulae.

@apjanke apjanke closed this as completed Apr 18, 2016
@Homebrew Homebrew locked and limited conversation to collaborators May 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
needs response Needs a response from the issue/PR author
Projects
None yet
Development

No branches or pull requests

3 participants