[Bug]-[210]:Mongo plugin URI parsing issue
Is there an existing issue for this?
- [X] I have searched the existing issues
Description
Ref: https://theappsmith.slack.com/archives/C0341RERY4R/p1649405309648129 Cannot share the URI string publicly here for security reasons.
Steps To Reproduce
https://theappsmith.slack.com/archives/C0341RERY4R/p1649405309648129 Cannot share the URI string publicly here for security reasons.
Workaround: Use the form based datasource config page.
Public Sample App
No response
Version
cloud
@sumitsum do we have a clue about the root cause, so that we can more intelligently get at the reach of this problem? Are there any known peculiarities in the URI which cause our algorithm to fail?
@rohan-arthur Sorry, I just realised - not saving the URI string in some way was a mistake. Now I am not able to access the app that had the URI - we may not be able to figure out what the exact issue was - but I think we can figure out certain things from trial and error. From what I remember, our regex was parsing the URI string in a wierd way because the URI string had certain characters that the regex was using to identify the pattern. I think a little bit of trial and error should reveal some of such bad URI string types.
mongo 6m usage: 1050 Assume 5% users face this issue: 52.5
Stats
| Stat | Values |
|---|---|
| Reach | 52.5 |
| Effort (months) | 0.5 |
Closing this issue since the URI that was failing is lost. We'll revisit this the next time we have a user report a similar issue.
@nidhi-nair this issue has resurfaced. Internal discussion
Another user flagged this issue - link
@jnikhila added draft for the documentation change related to this issue here.