RefResolver deprecated

[ejratl]

The build system is currently failing. jsonschema 4.18 introduced the referencing library and deprecated RefResolver. This is breaking some tests, namely marking_definition, network_traffic and observed_data. This is currently blocking all PRs and releases.
Note: calling setup.py is deprecated and license_file in setup.config is also deprecated in favor of license_files. These are not currently breaking the build system.

[ejratl]

RefResolver has been deprecated
https://github.com/python-jsonschema/jsonschema/releases/tag/v4.18.0

[ejratl]

As a tactical workaround, I am freezing jsonschema < 4.18.0 until the project can migrate to the referencing library. PRs welcomed.

[ostefano]

Changes do not seem be trivial. @ejratl could you put together an example detailing how to modify def load_validator(schema_path, schema)?

Then I could try to take it from there.

[ejratl]

We will need the assistance of @clenk for this, I believe.

[ostefano]

Folks, this is bound to become a bigger issue as we go forward. I would be happy to help, but I do need some guidance.

[aryabharat]

Hi @ejratl
I tried to resolve this: #226
Please let me know if something is wrong.

[aryabharat]

@ejratl @clenk I have raised a PR #226 while testing it locally was getting error on $ref path.
jsonschema.exceptions._RefResolutionError: <urlopen error [Errno 2] No such file or directory: '../common/core.json'>

Can you please help, is it a code level issue or i'm missing something else

[aryabharat]

Hi @ejratl @clenk Can you please have a look at the PR: https://github.com/oasis-open/cti-stix-validator

[ejratl]

Thanks for doing this work. Will you be able to sign the CLA? It looks a bit like Github and/or the CLA bot is having trouble with you account.

[ejratl]

I will ask the oasis-open admins to look into the problem.

[ostefano]

Hi @aryabharat , did you manage to sign the CLA on #226?

[aryabharat]

@ostefano Yes! i have signed the CLA.

[ostefano]

@ejratl anything that we can do to unblock this?

[ejratl]

@ostefano The issue here is that the user id that made the commits is different from the user id that signed the CLA (although they represent the same person most likely). The easiest solution would be for @aryabharat to set the local config for the repo and then force push using the id that signed the CLA to update the PR to all be from one user id that signed the CLA.

[ostefano]

@ejratl I see. Looks like the problem is now solved, so hopefully it can be merged soon :)

[ostefano]

@ejratl there is a new PR solving the issue available here: #228

[ostefano]

#228 is merged. We can close this.