Cannot load module with extension in rpc input with printed context address

[jeremie6wind]

Hi,
I have several yang files with extensions working fine.
However, in some specific cases, the module cannot be loaded:

• when the extension is in a rpc input.

Here is a yang example with an extension in the rpc input loaded with the command:
sysrepoctl -i example.yang -v3

module example {
	yang-version 1.1;
	namespace "urn:examples";
	prefix e;
	extension my-extension {
		description
			"Description.";
	}

	rpc myrpc {
		description
			"Manage troubleshooting reports.";

		input {
			e:my-extension;

			leaf list {
				type empty;
				description
					"List.";
			}
		}
	}
}

  __assert_fail (libc.so.6 + 0x3b517)
  sr_lycc_store_context (libsysrepo.so.8 + 0x5c9cd)
 _sr_install_modules (libsysrepo.so.8 + 0xfd68)

[jeremie6wind]

Same issue in this specific case:

module example {
	yang-version 1.1;
	namespace "urn:example";
	prefix e;

	extension my-description-extension {
		description
			"Description.";
	}
	container cont1 {
		leaf l1 {
			type string;
		}
		leaf myenum {
			type enumeration {
				enum any {
					description
						"Use any.";
				}

				enum myenumvalue1 {
					description
						"Description.";
					e:my-description-extension;
				}
				enum myenumvalue2 {
					description
						"Description.";
					e:my-description-extension;
				}
			}
		}
	}
}

  #4   __assert_fail (libc.so.6 + 0x3b517)
  #5   ly_ctx_compiled_addr_ht_get (libyang.so.4 + 0x12694c)
  #6   ly_ctx_compiled_print (libyang.so.4 + 0x30559)
  #7   sr_ly_ctx_compiled_print (libsysrepo.so.8 + 0x383ea)
  #8   sr_lycc_store_context (libsysrepo.so.8 + 0x5c931)

[michalvasko]

Thanks, these 2 cases should be fixed, different issues.

[jeremie6wind]

Thank you for the fix.
I have found another case, should I open another issue?
One identity with extension works fine, but a second with the same extension fails.

module example2 {
	yang-version 1.1;
	namespace "urn:example2";
	prefix e2;

	extension my-description-extension {
		description
			"Description.";
	}

	identity myidentity3 {
		description
			"Descr.";

		e2:my-description-extension;
	}

	identity myidentity4 {
		description
			"Descr.";

		e2:my-description-extension;
	}
}