-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
yc.o sync #1591
yc.o sync #1591
Conversation
@xorrkaz, there are a bunch of errors in the IETF content. Will you be looking at those? |
I am watching. The problem is missing IANA modules. The IANA sync job is running, and I saw one leak out recently. I don't know why the rest are not. If they don't get pushed before 121, I'll spend some time there sorting it. |
Ah, actually, I lied @einarnn. The modules do exist in the repo. Your search path is wrong. The IANA modules are spread between extracted and standard, but the search path in the failing job is |
I think the ieee_dir_flag="--path $cwd/$ieee_dir/published/" Such as: iana_dir="standard/iana"
iana_dir_flag="--path $cwd/$iana_dir/"
pyang_flags="--verbose $ieee_dir_flag $iana_dir_flag" That won't fix all of the issues right now. But it seems like IANA is lagging a bit in tracking drafts turning into RFCs. I think they will eventually all work. |
@xorrkaz, it would be better if whoever is committing changes that broke the check scripts als fixed the check scripts as part of their commit. Was this broken by this commit or by a different one? |
It's not a question of a commit. The IANA modules are now automatically updated in their own directory. My other PR fixed looking for those. However, in the case of these IANA SSH modules, their repo still refers to the drafts and not the RFCs. Therefore, they aren't being added to the |
I spoke with Sabrina from IANA, and she said the SSH modules are pending a review from Kent Watsen. Once that clears, they should be fully published, and the |
No description provided.