-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Reply By Tweet Bug Discussion #6085
Comments
cc @jywarren , @gauravano |
@jywarren I tried on local with the same tweet. I was able to find node on local machine but same was not happening on production. I think it is something to do with the website host pattern env variable. Can anyone of @jywarren or @icarito let me know that what is the ENV["WEBSITE_HOST_PATTERN"] set on production? Is it Thanks |
Hmm, yes it is! |
I checked the logs and yayy, I found this: Line 501 in e224639
Can you run this function from the rails console and find out if is there data for email : "[email protected]"? -- We are very close this time, just need to find user email. Thanks!! |
Also, can you delete the logs file or copy it somewhere else /public/cron_log1.log file on publiclab. Because this file is big and I need to download it very ofter after doing various reply by tweet. Line 509 in e224639
|
Hi, @namangupta01 what query exactly should I run or what data should I look for? |
If it's helpful, I've just logged in via twitter! https://publiclab.org/profile/warren/ |
Yes! And also can you also try to run with your username as well? |
Can you run it with two of my usernames?
|
|
Yes, this is the problem. This is what I was thinking. |
Ah, ok. Do we need to re-prompt them somehow? Or could we run a query to
generate a list of people for whom this is the case?
…On Mon, Aug 19, 2019 at 5:22 PM Naman Gupta ***@***.***> wrote:
Yes, this is the problem. This is what I was thinking.
The problem is the people who logged in before we started storing for
users data in UserTag if not present there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6085?email_source=notifications&email_token=AAAF6J4YL6DNE6LN5OKBB3LQFMFHXA5CNFSM4IIA2RQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4UKXCI#issuecomment-522759049>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAF6J2YXEUSEFJARU3DL3TQFMFHXANCNFSM4IIA2RQQ>
.
|
I will look to the flow of login via twitter and will add condition there
to save the data in UserTag whenever any user login again via twitter.
On Tue, Aug 20, 2019 at 2:59 AM Jeffrey Warren <[email protected]>
wrote:
… Ah, ok. Do we need to re-prompt them somehow? Or could we run a query to
generate a list of people for whom this is the case?
On Mon, Aug 19, 2019 at 5:22 PM Naman Gupta ***@***.***>
wrote:
> Yes, this is the problem. This is what I was thinking.
> The problem is the people who logged in before we started storing for
> users data in UserTag if not present there.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <
#6085?email_source=notifications&email_token=AAAF6J4YL6DNE6LN5OKBB3LQFMFHXA5CNFSM4IIA2RQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4UKXCI#issuecomment-522759049
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AAAF6J2YXEUSEFJARU3DL3TQFMFHXANCNFSM4IIA2RQQ
>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6085?email_source=notifications&email_token=AE6AEYNRZQGZQYI32PFJ4JLQFMGD3A5CNFSM4IIA2RQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4ULJOI#issuecomment-522761401>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AE6AEYNWLAWBTSGLGKT7ULDQFMGD3ANCNFSM4IIA2RQQ>
.
|
And also can you delete the file /cron_log1.log? Its is getting very big? |
Ah that's great. If we could generate the list we could also ask people to
log in once again.
On Mon, Aug 19, 2019 at 5:32 PM Naman Gupta <[email protected]>
wrote:
… I will look to the flow of login via twitter and will add condition there
to save the data in UserTag whenever any user login again via twitter.
On Tue, Aug 20, 2019 at 2:59 AM Jeffrey Warren ***@***.***>
wrote:
> Ah, ok. Do we need to re-prompt them somehow? Or could we run a query to
> generate a list of people for whom this is the case?
>
> On Mon, Aug 19, 2019 at 5:22 PM Naman Gupta ***@***.***>
> wrote:
>
> > Yes, this is the problem. This is what I was thinking.
> > The problem is the people who logged in before we started storing for
> > users data in UserTag if not present there.
> >
> > —
> > You are receiving this because you were mentioned.
> > Reply to this email directly, view it on GitHub
> > <
>
#6085?email_source=notifications&email_token=AAAF6J4YL6DNE6LN5OKBB3LQFMFHXA5CNFSM4IIA2RQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4UKXCI#issuecomment-522759049
> >,
> > or mute the thread
> > <
>
https://github.com/notifications/unsubscribe-auth/AAAF6J2YXEUSEFJARU3DL3TQFMFHXANCNFSM4IIA2RQQ
> >
> > .
> >
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <
#6085?email_source=notifications&email_token=AE6AEYNRZQGZQYI32PFJ4JLQFMGD3A5CNFSM4IIA2RQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4ULJOI#issuecomment-522761401
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AE6AEYNWLAWBTSGLGKT7ULDQFMGD3ANCNFSM4IIA2RQQ
>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6085?email_source=notifications&email_token=AAAF6JY7RZSIRRZT7OB7X2TQFMGLTA5CNFSM4IIA2RQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4ULPCI#issuecomment-522762121>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAF6J23H6IUZCHRIJKAQQLQFMGLTANCNFSM4IIA2RQQ>
.
|
Yup we can do! |
Ah yes, will delete it now.
…On Mon, Aug 19, 2019 at 5:37 PM Naman Gupta ***@***.***> wrote:
Yup we can do!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6085?email_source=notifications&email_token=AAAF6J2IILJT4HZHGIZ72MDQFMG7RA5CNFSM4IIA2RQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4UL4ZY#issuecomment-522763879>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAF6JZLUA2RYJ4S7MOQ7X3QFMG7RANCNFSM4IIA2RQQ>
.
|
Let me know when its deleted. I will check with the new tweet made by
naman18996 account.
On Tue, Aug 20, 2019 at 3:07 AM Jeffrey Warren <[email protected]>
wrote:
… Ah yes, will delete it now.
On Mon, Aug 19, 2019 at 5:37 PM Naman Gupta ***@***.***>
wrote:
> Yup we can do!
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <
#6085?email_source=notifications&email_token=AAAF6J2IILJT4HZHGIZ72MDQFMG7RA5CNFSM4IIA2RQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4UL4ZY#issuecomment-522763879
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AAAF6JZLUA2RYJ4S7MOQ7X3QFMG7RANCNFSM4IIA2RQQ
>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6085?email_source=notifications&email_token=AE6AEYP5ILH5T4AJHYDLTLLQFMHDNA5CNFSM4IIA2RQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4UL7JY#issuecomment-522764199>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AE6AEYIP74DJ6N3OHBUTZT3QFMHDNANCNFSM4IIA2RQQ>
.
|
Its deleted!
…On Mon, Aug 19, 2019, 5:49 PM Naman Gupta ***@***.***> wrote:
Let me know when its deleted. I will check with the new tweet made by
naman18996 account.
On Tue, Aug 20, 2019 at 3:07 AM Jeffrey Warren ***@***.***>
wrote:
> Ah yes, will delete it now.
>
> On Mon, Aug 19, 2019 at 5:37 PM Naman Gupta ***@***.***>
> wrote:
>
> > Yup we can do!
> >
> > —
> > You are receiving this because you were mentioned.
> > Reply to this email directly, view it on GitHub
> > <
>
#6085?email_source=notifications&email_token=AAAF6J2IILJT4HZHGIZ72MDQFMG7RA5CNFSM4IIA2RQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4UL4ZY#issuecomment-522763879
> >,
> > or mute the thread
> > <
>
https://github.com/notifications/unsubscribe-auth/AAAF6JZLUA2RYJ4S7MOQ7X3QFMG7RANCNFSM4IIA2RQQ
> >
> > .
> >
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <
#6085?email_source=notifications&email_token=AE6AEYP5ILH5T4AJHYDLTLLQFMHDNA5CNFSM4IIA2RQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4UL7JY#issuecomment-522764199
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AE6AEYIP74DJ6N3OHBUTZT3QFMHDNANCNFSM4IIA2RQQ
>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6085?email_source=notifications&email_token=AAAF6JYPOPTJVCIUW2BSAKTQFMINDA5CNFSM4IIA2RQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4UMYTI#issuecomment-522767437>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAF6J5YDG2LGA7TNJPCFALQFMINDANCNFSM4IIA2RQQ>
.
|
Yay, It's working!!! 🎉 🎉 LOL, this was working all this time the only thing is that we were not doing reply by a tweet from the proper accounts. By proper accounts, I mean those accounts whose first login via twitter was done after we implemented this feature --as I said above. |
Oh wow! That's great! So, we still have to be sure it uses a proper /n/____
shortcode, not a t.co one, right?
Can we add a "this comment was added by tweet" and corresponding icon to
this template?
https://github.com/publiclab/plots2/blob/3a0e9744d626ebfa7646ab2b406b8244172b6468/app/views/notes/_comment.html.erb#L52-L54
This is amazing - it's working in production?
…On Tue, Aug 20, 2019 at 1:58 AM Naman Gupta ***@***.***> wrote:
Yay, It's working!!! 🎉 🎉
[image: Screen Shot 2019-08-20 at 11 23 16 AM]
<https://user-images.githubusercontent.com/20709985/63321022-15f04500-c33d-11e9-970a-e8a7660394ee.png>
Link here:
https://publiclab.org/notes/mimiss/08-05-2019/trawling-with-babylegs-in-new-orleans-city-park
This was done by reply by tweet.
LOL, this was working all this time the only thing is that we were not
doing reply by a tweet from the proper accounts. By proper accounts, I mean
those accounts whose first login via twitter was done after we implemented
this feature --as I said above.
Finally, it's working just have to solve the case with old accounts :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6085?email_source=notifications&email_token=AAAF6JYLWWL242XI6VG7733QFOBWRA5CNFSM4IIA2RQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4VEXXI#issuecomment-522865629>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAF6J3UITVN25HC5VDJPMLQFOBWRANCNFSM4IIA2RQQ>
.
|
Yes! This is working in production. |
Here's the tweet where I replied https://twitter.com/PublicLab/status/1159583447926677505 |
In this tweet, it uses /n/___. But I am not sure about t.co but we can also test this out as well. And sure I will add the icon. |
Great! I tweeted here: https://twitter.com/jywarren/status/1163852083747012609 but maybe mine is an old account? |
If Comment.find_email is able to find email from your user name then you can. |
Ah, it did find an email but it wasn't the email I am signed up on PL for,
is that OK?
Also, how often does it check? Is it possible i need to wait longer?
…On Tue, Aug 20, 2019 at 1:28 PM Naman Gupta ***@***.***> wrote:
If Comment.find_email is able to find email from your user name then you
can.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6085?email_source=notifications&email_token=AAAF6JYTDQK4TEIBU6M2ALTQFQSTHA5CNFSM4IIA2RQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4XBWBA#issuecomment-523115268>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAF6J6ZV6MAHVFVO6BDBGLQFQSTHANCNFSM4IIA2RQQ>
.
|
This is weird. If you have logged in via twitter then your twitter email and email on PublicLab is supposed to be same? Isn't it? |
Can you tell me how different email id case? |
Oh, I got it. |
Here's the fix jeff #6166 |
Hi @namangupta01 do you think you could remove the comments used in reply by tweet now? |
Sure! |
Hi 😄, this issue has been automatically marked as stale because it has not had recent activity. Don't worry you can continue to work on this and ask @publiclab/reviewers to add "work in progress" label 🎉 . Otherwise, it will be closed if no further activity occurs in 5 days -- but you can always re-open it if you like! 💯 Thank you for your contributions 🙌 🎈. |
Sorry about the stalebot message here, it was a mistake! 😅 |
So I have figured out what the actual problem is after adding the console to print the mid way data in #6064.
The actual problem is short links.
parent tweet #<Twitter::Tweet:0x00005646ea71df68> parent tweet full text -> We’ve overhauled the entire https://t.co/PKr9eq2bkF website! Thanks to support from @GoogleOSS and contributors from five continents(!), we’re helping people around the world to better tell their stories through aerial mapping. Read all about it! https://t.co/nBXpX7hCHZ https://t.co/HClNdCS9y4 urls => ["https://t.co/PKr9eq2bkF", "https://t.co/nBXpX7hCHZ", "https://t.co/HClNdCS9y4"] node => node.nil? => true
So here, https://t.co/nBXpX7hCHZ opens to https://publiclab.org/notes/warren/07-26-2019/community-atlas-an-around-the-world-collaboration-on-mapknitter where we have implemented the algo for the https://publiclab.org/n/20331.
plots2/app/models/comment.rb
Line 452 in 449d047
I guess we can try this once with a tweet with this kind of link https://publiclab.org/n/20331
If you want to see the logs, you can see at stable.publiclab.org/cron_log1.log
What do you think?
The text was updated successfully, but these errors were encountered: