-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[bug] The process of "Building a Trace Receiver" is broken #3488
Comments
After digging into the code and playing with Golang's module design, I realized that there are two issues:
I can send a PR to fix above issues that I mentioned if that makes sense. Meanwhile, I'd suggest to create a new |
PR appreciated! |
Okay, let me walk it through again to see where and how to enhance the dev experience with potential practices embedded. Will prepare and send a PR soon. |
fixed via #3524 |
What happened? Describe the problem that occurred.
Was trying to follow the "Building a Trace Receiver" to walk through the process of building a trace receiver, but I was stuck at step of "Adding the receiver factory to the Collector’s initialization".
It's obvious that, before we run below command, after importing the
github.com/rquedas/otel4devs/collector/receiver/trace-receiver/tailtracer module
, a new compilation should be required:Otherwise below exception is expected:
However, there is a compilation issue if we simply issue the
go build
command:It won't help if we follow the instructions to
go get
the required module:What did you expect would happen? Describe the expected result/output.
No doubt, such a tutorial is great and very helpful.
But if it's version specific, please highlight which version(s) are tested, and version pinning might be a good practice to avoid confusion.
And it should be reviewed regularly to make it work for the latest release.
What is the name + path of the page where you encountered the issue? The
relative path and page title where you found a problem.
The Building a Trace Receiver
What browser, OS, and platform were you using when you encountered the
problem? Include the browser version if you know it as well.
MacBook Pro with M1 chip.
Additional context: anything else you can think about that would be helpful.
The text was updated successfully, but these errors were encountered: