You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
im getting some inconsistant behaviour between kappa-view-pull-query v 1.0 and 1.1. Perhaps the behaviour is intentional.
when doing: core.api.query.read({ query, opts })
v1.0 queries give me the complete objects: { key: 'deadbeef', seq: 4, value: { content: 'of the message' } }
but v1.1 queries are giving me objects with only { value: {... } }, without the { key: ..., seq: n ... part. so i cant work out who authored them from the queries.
but its difficult to say for sure if this module is causing the problem, because if i try to downgrade to 1.0 in the kappa-bls-sign module, stuff breaks.
upgrading metadb from 1.0 to 1.1 does indeed mean that the queries only contain the value properties.
but these two modules are using different versions of kappa-core (4.0.1 and 3.0.2 respectively) so its hard to know what is causing what.
The text was updated successfully, but these errors were encountered:
sorry if the problem is not so clearly described:
im getting some inconsistant behaviour between kappa-view-pull-query v 1.0 and 1.1. Perhaps the behaviour is intentional.
when doing:
core.api.query.read({ query, opts })
v1.0 queries give me the complete objects:
{ key: 'deadbeef', seq: 4, value: { content: 'of the message' } }
but v1.1 queries are giving me objects with only
{ value: {... } }
, without the{ key: ..., seq: n ...
part. so i cant work out who authored them from the queries.im using v1.1here: https://gitlab.com/dark-crystal/kappa-bls-sign/blob/master/index.js
and 1.0 here: https://github.com/ameba23/metadb/blob/master/index.js
but its difficult to say for sure if this module is causing the problem, because if i try to downgrade to 1.0 in the
kappa-bls-sign
module, stuff breaks.upgrading
metadb
from 1.0 to 1.1 does indeed mean that the queries only contain the value properties.but these two modules are using different versions of
kappa-core
(4.0.1 and 3.0.2 respectively) so its hard to know what is causing what.The text was updated successfully, but these errors were encountered: