-
Notifications
You must be signed in to change notification settings - Fork 37
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
Clean up browser logs #154
Comments
@d-ivashchuk maybe i could start with this? forking the repo right now do you've a discord i can add you in? |
This one seems to be perfect 👍🏼 @narutosstudent |
I am not yet sure how discord works, even using it for gaming for years now 😂😅 do I have a username there? |
@narutosstudent if you don't mind I will point your to the rights parts of codebase so you have easier time navigating! But tomorrow already, quite a day it was! |
@d-ivashchuk sounds good, discord shouldn't be necessary tbh 😂 Github got enough ways to communicate, even emojis here lol 💀 I'm happy to also hack on features eventually, will go through the codebase this evening and make sure to study it a bit, will try to take notes of questions I've that you could respond to. Thank you ❤️ . |
@d-ivashchuk It might be a bit small, but check the top left chrome group of mine, lost-pixel 😎 🔥 got the fork and this github issue open, ready anytime 💪 😄 |
If you will have time and gather some amount of questions already - we can even jump on quick call in the evening 😊 |
Hey can I join too? would love to know more about this project for future contribution :) |
@judicaelandria absolutely, I will work on the weekend to create some issues that would be good first issues and make it easier for people of various knowledge and backgrounds to contribute! Thanks for your interest 🥇 |
@narutosstudent soo the scope of the issue is quite limited. Trying to be more verbose in debugging at some point we've added this chunk of code which is responsible for piping the browser logs to the general logs of lost-pixel. Those are seen on the runs in the CI and if you have some problems with your screenshots it makes it easier to debug. Image for informational purposes - it does not have browser logs in this case! the main problem with it is that sometimes it just pollutes the console in cases where we are not interested in the logs. Meaning we have couple of options to remedy this:
I am very much happy to listen to your suggestions and explore good practices though @narutosstudent, I bet tools like @chriskalmar thoughts? |
cool! here's my email for the invitation judicaelandria7@gmail.com |
@d-ivashchuk Sorry for the late response, was busy 😄 ❤️ Let me read your reply. Yes, I'm happy to jump on a call. Feel free to invite me to a meeting that fits for you, Zoom or Google Meet ❤️ My email: tigerabrodi@gmail.com Though we may not need a meeting yet, I'm happy to pair code and learn more about the codebase ❤️ @d-ivashchuk At work, we're using this package to make sure when a console error happens, that the test fails: https://www.npmjs.com/package/cypress-fail-on-console-error
I see, so the goal here is for the logs in CI to be cleaned up, so it doesn't get too dirty, am I right? |
@judicaelandria You can continue on this if you want, I've decided to step away from open-source as I'm busy with other things. 👍 |
Mode
No response
Feature description
Potentially introduce the flag to mute the browser logs.
The text was updated successfully, but these errors were encountered: