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

Discord Data Parse Error #2 #64

Closed
Solixity opened this issue Feb 23, 2021 · 4 comments
Closed

Discord Data Parse Error #2 #64

Solixity opened this issue Feb 23, 2021 · 4 comments

Comments

@Solixity
Copy link

Solixity commented Feb 23, 2021

Extension of Issue #63

I'm currently going through what #63 was going through, the directory length is always 0.
image

When I attempt to test a small cut out of my Discord Message data (as you can see here, that was originally made from this), it continues to return no matches at all. I have not modified any part of the script or the exported data, what's going on and how can I manage to fix it?

@Solixity
Copy link
Author

I'd like to add on that if I need to show exported data, I will, but the other person in the data will be anonymous due to their preference.

@TotallyNotChase
Copy link
Collaborator

TotallyNotChase commented Feb 23, 2021

Interesting, Your format seems to have 3 newlines as separators between messages instead of 2. I try to refrain from greedy matching newlines but if there's inconsistency in the number of newlines in formats - that should be the only solution.

Also, note that in the regex link you posted - you're missing the # in your name. This won't fix the problem at hand. But if you also go ahead and cut down the 3 newlines down to 2, you'll see them match.

Here's also the matches from the other perspective

Could you confirm that the separators for each message in your exported format is indeed 3 newlines? If this is the case. I'll just switch the newline matchers to greedy and roll out a fix.

Note that this is in no way related to #63 as the format provided there matches successfully in the regex tester.

@Solixity
Copy link
Author

Note that this is in no way related to #63 as the format provided there matches successfully in the regex tester.

My fault, I thought that it was related due to how it was dealing with the same data and how the regex wasn't able to parse data. I'll go ahead and double check if there's 3 newlines instead of 2. I haven't modified the data as said (other than anonymizing the other person in this case) so there may be 3 newlines. Thanks for the help so far though.

@Solixity
Copy link
Author

Closed it due to it being a stale issue.

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

No branches or pull requests

2 participants