Getting started: https://github.com/oppia/oppia/wiki/Contributing-code-to-Oppia#setting-things-up || Active mentors on chat: @gp201, @Nik-09, @chris7716 (Expect a relpy within 24 hrs.)
2 replies
I am facing errors in running the server with respect to google cloud sdk (as shown above).. Has anyone figured the solution for this ?
I checked that the CLOUDSDK_PYTHON is pointing to an executable python file (as suggested in the error message) and I also tried deleting the ../oppia_tools/ directory and running the server again.
Neither of the options worked as solution.
1 reply
python -m scripts.linters.pre_commit_linter
Traceback (most recent call last):
File "/.pyenv/versions/3.7.10/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/.pyenv/versions/3.7.10/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/opensource/oppia/scripts/linters/pre_commit_linter.py", line 728, in <module>
main()
File "/opensource/oppia/scripts/linters/pre_commit_linter.py", line 620, in main
namespace=namespace
File "/opensource/oppia/scripts/linters/pre_commit_linter.py", line 483, in _get_all_filepaths
filename for filename in all_filepaths if not
File "/opensource/oppia/scripts/linters/pre_commit_linter.py", line 486, in <listcomp>
in general_purpose_linter.EXCLUDED_PATHS
File "/opensource/oppia/scripts/linters/pre_commit_linter.py", line 485, in <genexpr>
fnmatch.fnmatch(filename, pattern) for pattern # pylint: disable=comprehension-escape
File "/.pyenv/versions/3.7.10/lib/python3.7/fnmatch.py", line 36, in fnmatch
return fnmatchcase(name, pat)
File "/.pyenv/versions/3.7.10/lib/python3.7/fnmatch.py", line 71, in fnmatchcase
return match(name) is not None
TypeError: cannot use a string pattern on a bytes-like object
2 replies
2 replies
Hello Devs,
Hope you are well. We are excited that a Tech Talk on Frontend Testing is being organized today i.e. 28st August (Saturday) - 22:30 IST (17:00 UTC).
The talk would cover the following points:
- Writing robust frontend unit tests
- Covering various scenarios in the code (testing the code thoroughly instead
of just covering lines) - Different scenarios that are difficult to test
- Avoiding flakes
- Identifying and resolving flakes if you get any
After the talk, you will get a brief idea about Frontend Unit testing, which would be helpful to you, as you'll have to write Frontend Tests for your future contributions to Oppia.
Link for the event: https://meet.google.com/nuj-jate-rfz
Hoping to see you all there! If you have any questions/suggestions you can add them to this Slido Link: https://app.sli.do/event/bxrnwack
Hello Devs,
Hope you are well. We are excited that a Tech Talk on Frontend Testing is being organized today i.e. 28st August (Saturday) - 22:30 IST (17:00 UTC).
The talk would cover the following points:
- Writing robust frontend unit tests
- Covering various scenarios in the code (testing the code thoroughly instead
of just covering lines)- Different scenarios that are difficult to test
- Avoiding flakes
- Identifying and resolving flakes if you get any
After the talk, you will get a brief idea about Frontend Unit testing, which would be helpful to you, as you'll have to write Frontend Tests for your future contributions to Oppia.
Link for the event: https://meet.google.com/nuj-jate-rfz
Hoping to see you all there! If you have any questions/suggestions you can add them to this Slido Link: https://app.sli.do/event/bxrnwack
@/all Reminder
3 replies
10 replies
Hey team!
I was working the backend linter fix(oppia/oppia#11496) and I was able to successfully run the test prompt python -m scripts.run_custom_eslint_tests
---------------------------
All tests passed
---------------------------so I think it means that the linter test is working as intended. However when I was later running the three python command
python -m scripts.linters.pre_commit_linter --path core/tests/protractor
python -m scripts.linters.pre_commit_linter --path core/tests/protractor_desktop
python -m scripts.linters.pre_commit_linter --path core/tests/protractor_utils./.python-version is not listed in the .github/CODEOWNERS file.
./package-lock.json is not listed in the .github/CODEOWNERS file.