From: Rob Herring <robh+dt@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: devicetree@vger.kernel.org
Subject: Re: dtschema v2020.08.1 json.decoder.JSONDecodeError error
Date: Wed, 2 Sep 2020 12:29:00 -0600 [thread overview]
Message-ID: <CAL_JsqLLPmirYSLqOuvoXrmxA7ST_iG01xL6ypqSraZCbR-ADw@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqLKKagxyJPRK=_Xze7jWYAsqSBPbyZC3CLBeDZp5H49hQ@mail.gmail.com>
On Fri, Aug 28, 2020 at 4:58 PM Rob Herring <robh+dt@kernel.org> wrote:
>
> On Fri, Aug 28, 2020 at 3:51 AM Krzysztof Kozlowski <krzk@kernel.org> wrote:
> >
> > Hi Rob,
> >
> > I am trying dt_bindings_check with on top of next-20200826 with dtschema
> > v2020.08.01 and got errors on all schemas:
> >
> > =======
Did you miss some of the traceback?:
Traceback (most recent call last):
File "/home/rob/.local/lib/python3.6/site-packages/jsonschema-3.2.0-py3.6.egg/jsonschema/validators.py",
line 774,
in resolve_from_url
document = self.store[url]
File "/home/rob/.local/lib/python3.6/site-packages/jsonschema-3.2.0-py3.6.egg/jsonschema/_utils.py",
line 22, in _
_getitem__
return self.store[self.normalize(uri)]
KeyError: 'https://protect2.fireeye.com/url?k=59835ffc-05905d01-59822c67-0cc47a336902-306bd2691e458c36&q=1&u=http%3A
%2F%2Fdevicetree.org%2Fmeta-schemas%2Fcore.yaml%23'
I get this and then the same traceback as you. This is now fixed in -next.
Rob
next prev parent reply other threads:[~2020-09-02 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 9:51 dtschema v2020.08.1 json.decoder.JSONDecodeError error Krzysztof Kozlowski
2020-08-28 15:44 ` Krzysztof Kozlowski
2020-08-28 22:58 ` Rob Herring
2020-09-02 18:29 ` Rob Herring [this message]
2020-09-02 19:22 ` Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAL_JsqLLPmirYSLqOuvoXrmxA7ST_iG01xL6ypqSraZCbR-ADw@mail.gmail.com \
--to=robh+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).