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

Ambiguity in OSI trace file format documentation, document saying *.txt is Plain - text trace file(Readable format) but it storing multiple serialized OSI messages(non readable format) in one trace file. There is some contradiction. Is .txt readable? #70

Open
surevpraveen opened this issue Jul 12, 2023 · 0 comments
Labels
question General questions about the standard, work-flow and code.

Comments

@surevpraveen
Copy link

Describe the problem

I want to do ... in my application, but what I am actually getting is....
Here is a screenshot that illustrates the problem:

image.png

Describe what you have already tried

This is the most simplified version of my code that I have been able to get, which still produces the problem I described above.

// my code
...

Basically, what the code is doing is....
Changing ... does not work because it gives the following error:

Some error

Describe your research

[The documentation here] mentioned ... but did not provide a clear example of how that is done.
[This Stack Overflow question] describes a similar problem, but mine is different because....

Ask your question

So my basic question is, how do I...?

Additional context

Add any other context or screenshots about the question here.

@surevpraveen surevpraveen added the question General questions about the standard, work-flow and code. label Jul 12, 2023
@surevpraveen surevpraveen changed the title Ambiguity in OSI trace file format documentaition, *.txt means Plain - text trace file(Readable format) but document saying storing multiple serialized OSI messages(non readable format) in one trace file. There is some contradiction. Explain briefly? Ambiguity in OSI trace file format documentation, document saying *.txt is Plain - text trace file(Readable format) but it storing multiple serialized OSI messages(non readable format) in one trace file. There is some contradiction. Is .txt readable? Jul 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question General questions about the standard, work-flow and code.
Projects
None yet
Development

No branches or pull requests

1 participant