False positive argmatch results

The argmatch function currentlty does what it is supposed to; it returns whether a panel variant matches with a variant in the pandora VCF. But there can be false positives which lead to FP resistance calls. For example
gid     715     cd8b83c0        ACGACG  ACGACA,GCGACG   .       PASS    SVTYPE=PH_SNPs;GRAPHTYPE=SIMPLE;VARID=gid_A205E,gid_A205*;PREDICT=R,R        GT:MEAN_FWD_COVG:MEAN_REV_COVG:MED_FWD_COVG:MED_REV_COVG:SUM_FWD_COVG:SUM_REV_COVG:GAPS:LIKELIHOOD:GT_CONF    2:13,10,25:14,9,27:12,0,24:14,0,28:55,30,102:57,28,110:0.5,0.666667,0:-360.9,-412.153,-214.773:146.127

(I've removed some VARIDs for brevity)
This variant simplifies to
gid     715     cd8b83c0        A  G   .       PASS    SVTYPE=PH_SNPs;GRAPHTYPE=SIMPLE;VARID=gid_A205E,gid_A205*;PREDICT=R,R        GT:MEAN_FWD_COVG:MEAN_REV_COVG:MED_FWD_COVG:MED_REV_COVG:SUM_FWD_COVG:SUM_REV_COVG:GAPS:LIKELIHOOD:GT_CONF    2:13,10,25:14,9,27:12,0,24:14,0,28:55,30,102:57,28,110:0.5,0.666667,0:-360.9,-412.153,-214.773:146.127

The two variants gid_A205E and gid_A205* do overlap this VCF record, but they're not technically a match.
This position, 715, maps to codon 205, which in the reference is GCA. So this VCF position is the last base in the codon.
Changing the last base to G, as this record calls, would make the codon GCA->GCG which in amino space is A->A - i.e., synonymous. However, what argmatch does (by design) is look in the panel VCF and see that a G at this position matches with those other two variants, which it does, but it's complicated....
Here are the panel VCF records for those two variants
gid     713     gid_A205E       GCA     GAA,GAG 0       .       PAD=100;GENE=gid;VAR=A205E;RES=PROT;DRUGS=Streptomycin;ST=-
gid     713     gid_A205*       GCA     TGA,TAA,TAG     0       .       PAD=100;GENE=gid;VAR=A205*;RES=PROT;DRUGS=Streptomycin;ST=-

Extracting just position 715 from these variants does indeed provide A->G as an option. But it ignores the fact that you would also need to change positions 713 and/or 714, which our running example at the top does not.
I need to think about the cleanest way to handle this... Any thoughts are most welcome though.

Suggest you turn a catalogue into three catalogues
Part A: nucleotide matches
Use VCF definition of catalogue,  and match Drprg  vcf with catalogue vcf. Some trickiness with indel normalisation.
Part B: amino variants
First translate the pandora-inferred sequence into amino sequence
Then,

catalogue has two dictionaries. Both have key which is  amino position /index in the reference amino sequence.  First dictionary has value which is array of amino acids which cause resistance.  Second dictionary has value which is array of amino acids which definitely don't cause resistance. WHO and others starting to provide these "definitely not a resistance variant" lists, could be useful to report.

Finally notice if there is

stop codon
Part of the Pandora sequence has zero coverage,  signifying truncated gene

Part C

rule about whether frameshifts or stop codon or truncations in a gene are meant to cause resistance.  Frameshift detection by aligning amino sequence seems most reliable as you incorporate all variants at the same time.


Label Fix

Just have seen, that the label of the Popup for Note Editing has a wrong name. Changed it to "Edit notes"

Thanks for this PR!


Fix missing local cluster logs when running integration test

Description
Fix missing local cluster logs when running integration test.
Currently the local cluster is wiped out before the logs recorded. Rearrange the logics and record the logs after remove everything including the local cluster logs.
This is an alternative way of #3404 to resolve the issue.
Issues Resolved
#3382
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #3453 (12fbdf8) into main (cdf86d5) will decrease coverage by 0.31%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main    #3453      +/-   ##
==========================================
- Coverage   91.74%   91.44%   -0.31%
==========================================
  Files         172      172
  Lines        4991     4991
==========================================
- Hits         4579     4564      -15
- Misses        412      427      +15

Impacted Files
Coverage Δ

src/test_workflow/integ_test/service.py
92.85% <ø> (-0.09%)
:arrow_down:

src/test_workflow/test_cluster.py
85.52% <100.00%> (+0.19%)
:arrow_up:

... and 3 files with indirect coverage changes

You should be writing tests for these, because it fixes a real problem.


GraphQL response content-type header assertion failing

Love your library design BTW.
Small issue I thought I would call out. I'm using Github enterprise server 2.19.7 and the content-type header on the response to the /api/graphql request is different than the rest api. By one space to be exact.
There's an assertion on line 242 that expects the content type to equal application/json; charset=utf-8, and it does in response a v3 rest api call, but the v4 graphql api returns application/json;charset=utf-8.
https://github.com/brettcannon/gidgethub/blob/48db737541537d0df78dac2cfac717e86d158e7a/gidgethub/abc.py#L242
It's easy enough to work around (because your library is awesome), I'm just doing this for now:
class MyGitHubAPI(GitHubAPI):
    async def _request(
        self, method: str, url: str, headers: Mapping[str, str], body: bytes = b""
    ) -> Tuple[int, Mapping[str, str], bytes]:
        # Add proxy auth token
        headers = dict(**headers, **generate_proxy_header())
        # return await super(MyGitHubAPI, self)._request(method, url, headers, body)
        resp_status, resp_headers, resp_data = await super(MyGitHubAPI, self)._request(
            method, url, headers, body
        )
        resp_headers = dict(resp_headers)
        resp_headers["content-type"] = "application/json; charset=utf-8"
        return resp_status, resp_headers, resp_data

Of course Enterprise has to be different by a character. 🙄  My laziness of not wanting to care about the encoding has come back to 👻 me. 😉
Probably the best solution is to:

Drop the assert
Use https://github.com/brettcannon/gidgethub/blob/master/gidgethub/sansio.py#L33 to detect the decoding and do proper decoding based on it
Raise an exception when the result is not JSON (probably a new exception)

Would you like to submit a PR, @caseyduquettesc ?
(And thanks for the kind words!)

I'd be happy to.


runtime: scavenger not freeing all possible memory on darwin

This is effectively a follow-up to #29844. I am attempting to reduce our memory usage on iOS, where we are severely memory-constrained.
On darwin, sysUnused calls madvise(v, n, _MADV_FREE_REUSABLE). This marks the pages as reclaimable by the OS. However, unexpectedly, it does not mark all the pages as reclaimable. I do not understand why, but here's a way to reproduce it.
The following program makes and then frees a single large byte slice. It pauses three times: before the allocation, after the allocation, and after the allocation has been freed.
package main

import (
	"runtime/debug"
	"time"
)

var b []byte

func main() {
	// Call time.Sleep and debug.FreeOSMemory once up front,
	// so that all basic runtime structures get set up
	// and all relevant pages get dirtied.
	time.Sleep(time.Millisecond)
	debug.FreeOSMemory()
	println("start")
	time.Sleep(5 * time.Second)

	b = make([]byte, 4_000_000)
	for i := range b {
		b[i] = 1
	}
	println("allocated")
	time.Sleep(5 * time.Second)

	b = nil
	debug.FreeOSMemory()
	time.Sleep(3 * time.Second) // wait for the scavenger's effects to be visible
	println("freed")
	time.Sleep(3 * time.Hour)
}

Running this on macOS, I use footprint to measure the app's footprint and vmmap to get the memory usage details, at each pause point. Concretely, I run go build -o jjj x.go && GODEBUG=allocfreetrace=1 ./jjj to run it and footprint jjj && vmmap -pages -interleaved -submap jjj to measure it.
Before the alloc, for the Go heap, footprint reports:
  Dirty      Clean  Reclaimable    Regions    Category
    ---        ---          ---        ---    ---
1168 KB        0 B          0 B         38    untagged ("VM_ALLOCATE")

After the alloc:
  Dirty      Clean  Reclaimable    Regions    Category
    ---        ---          ---        ---    ---
5344 KB        0 B          0 B         39    untagged ("VM_ALLOCATE")

After the free:
  Dirty      Clean  Reclaimable    Regions    Category
    ---        ---          ---        ---    ---
4192 KB        0 B      1344 KB         40    untagged ("VM_ALLOCATE")

Note that 4192KB-1344KB=2848KB, which is considerably higher than the 1168KB we began with.
(The exact numbers vary slightly from run to run.)
We can get a glimpse into the details of the accounting using vmmap (with flags listed above). For the Go heap, before the alloc:
REGION TYPE                    START - END         [   VSIZE    RSDNT    DIRTY     SWAP] PRT/MAX SHRMOD PURGE    REGION DETAIL
VM_ALLOCATE<PHONE_NUMBER>0-14000400000  [  256       40       40        0   ] rw-/rwx SM=ZER
VM_ALLOCATE<PHONE_NUMBER>0-14004000000  [ 3840        0        0        0   ] ---/rwx SM=NUL

After the alloc:
REGION TYPE                    START - END         [   VSIZE    RSDNT    DIRTY     SWAP] PRT/MAX SHRMOD PURGE    REGION DETAIL
VM_ALLOCATE<PHONE_NUMBER>0-14000400000  [  256      200      200        0   ] rw-/rwx SM=ZER
VM_ALLOCATE<PHONE_NUMBER>0-14000800000  [  256       85       85        0   ] rw-/rwx SM=PRV
VM_ALLOCATE<PHONE_NUMBER>0-14004000000  [ 3584        0        0        0   ] ---/rwx SM=NUL

After the free:
REGION TYPE                    START - END         [   VSIZE    RSDNT    DIRTY     SWAP] PRT/MAX SHRMOD PURGE    REGION DETAIL
VM_ALLOCATE<PHONE_NUMBER>0-14000400000  [  256      202      202        0   ] rw-/rwx SM=ZER
VM_ALLOCATE<PHONE_NUMBER>0-14000800000  [  256       85        1        0   ] rw-/rwx SM=PRV
VM_ALLOCATE<PHONE_NUMBER>0-14004000000  [ 3584        0        0        0   ] ---/rwx SM=NUL

This lines up with what tracealloc said:
tracealloc(0x14000180000, 0x3d2000, uint8)

and then
tracefree(0x14000180000, 0x3d2000)

The large byte slice spans the<PHONE_NUMBER>0-14000400000 and the<PHONE_NUMBER>0-14000800000 regions. However, the free appears only to have marked the pages in the<PHONE_NUMBER>0-14000800000 region as reclaimable. (84 pages = 1344KB, which is exactly what footprint reported as reclaimable.) The pages in the<PHONE_NUMBER>0-14000400000 region are still marked as dirty.
As an experiment, I changed sysUnused to also call mprotect(v, n, _PROT_NONE) then mprotect(v, n, _PROT_READ|_PROT_WRITE). See https://github.com/tailscale/go/commit/38ab03e1b4bd0699759860fb9235ae382470b623.
Running again with this change, the unreclaimable space reported by footprint disappears. At the three pause points:
  Dirty      Clean  Reclaimable    Regions    Category
    ---        ---          ---        ---    ---
1168 KB        0 B          0 B         37    untagged ("VM_ALLOCATE")

  Dirty      Clean  Reclaimable    Regions    Category
    ---        ---          ---        ---    ---
5328 KB        0 B          0 B         38    untagged ("VM_ALLOCATE")

  Dirty      Clean  Reclaimable    Regions    Category
    ---        ---          ---        ---    ---
1584 KB        0 B          0 B         39    untagged ("VM_ALLOCATE")

We're not back down to 1168KB (I wish I knew why), but it's considerably better than 2848KB. vmmap shows more or less the same pattern as before:
REGION TYPE                    START - END         [   VSIZE    RSDNT    DIRTY     SWAP] PRT/MAX SHRMOD PURGE    REGION DETAIL
VM_ALLOCATE<PHONE_NUMBER>0-14000400000  [  256       40       40        0   ] rw-/rwx SM=ZER
VM_ALLOCATE<PHONE_NUMBER>0-14004000000  [ 3840        0        0        0   ] ---/rwx SM=NUL

REGION TYPE                    START - END         [   VSIZE    RSDNT    DIRTY     SWAP] PRT/MAX SHRMOD PURGE    REGION DETAIL
VM_ALLOCATE<PHONE_NUMBER>0-14000400000  [  256      188      188       12   ] rw-/rwx SM=ZER
VM_ALLOCATE<PHONE_NUMBER>0-14000800000  [  256       85       85        0   ] rw-/rwx SM=PRV
VM_ALLOCATE<PHONE_NUMBER>0-14004000000  [ 3584        0        0        0   ] ---/rwx SM=NUL

REGION TYPE                    START - END         [   VSIZE    RSDNT    DIRTY     SWAP] PRT/MAX SHRMOD PURGE    REGION DETAIL
VM_ALLOCATE<PHONE_NUMBER>0-14000400000  [  256      197      197        5   ] rw-/rwx SM=ZER
VM_ALLOCATE<PHONE_NUMBER>0-14000800000  [  256       85        1        0   ] rw-/rwx SM=PRV
VM_ALLOCATE<PHONE_NUMBER>0-14004000000  [ 3584        0        0        0   ] ---/rwx SM=NUL

(Note that if you add the dirty and swapped pages together in the mprotect run, they match the madvise run dirty pages count exactly.)
I don't know how to interpret all of this. But it looks a bit like madvise(v, n, _MADV_FREE_REUSABLE) isn't sufficient to fully return memory to the OS, perhaps because of something having to do with allocation regions.
I'm out of ideas for what/how to investigate from here, but I'm happy to follow up on suggestions.
cc @mknyszek @bradfitz @randall77

I was walking over iOS issues and somehow I never noticed this. I'm very sorry for the years-late reply here.
I think what may be going on is that MADV_FREE_REUSABLE still behaves like MADV_FREE where the OS won't actually take the memory back unless there's memory pressure. I wish I knew how to investigate this further. MADV_FREE_REUSABLE isn't actually documented, and IIUC everyone just guesses as to what it does, or asks someone who works at Apple. AFAICT this is the only madvise on the system that actually updates system metrics.
It's also kind of slow, in my experience (it's especially slow on the MADV_FREE_REUSE side, IIRC). I wonder if we should just do the "remap as read/write" for all future darwin versions. I'll benchmark the difference. If there isn't one, I'll switch to the remap one.


[New game]: Slide Puzzle

🎮 Game Request
Simple puzzle game in which we have to complete an image using different small pieces of it.
Point down the features
Small pieces of a large image.
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @sumitkr2000  ! Thank you for raising an issue 💗 You have been assigned this issue you can start working on the issue 🎮

Hello @sumitkr2000, Time's Uppp!⏰
Sorry for closing your issue!
But it's more than a week since we haven't received anything from your side 😢 .
Come up with new ideas, create a new issue and make sure you finish it within a week! 🔥
All the best! 🚀
Happy Hacking! 💗

Hey @sumitkr2000 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Slideshow inside div

I've been messing around for some time now without figuring out how to have the Backstretch slideshow inside a div rather than on body background. Can someone explain?

Hi, if u want to have the Backstretch slideshow inside a div u must have to put the class or id of the corresponding div before the Backstretch, something like this:
$(".yourClass").backstretch('instruction')
$(".yourId").backstretch('instruction')
I know this is old, but i hope to help someone :v


possible regression in ZDEMO_EXCEL3 or outdated reference file

While reviewing #16 , I noticed that ZDEMO_EXCEL_CHECKER reported differences on ZDEMO_EXCEL3 and ZDEMO_EXCEL15_03, which should be investigated, either fixing the cause or updating the reference file. This happened with both versions of the checker, so it's not a new issue with the checker itself.
in worksheets/sheet1.xml
Old: <pane ySplit="3" topLeftCell="A4" activePane="bottomRight" state="frozen"/>
New: <pane ySplit="3" xSplit="1" topLeftCell="B4" activePane="bottomRight" state="frozen"/>

Got it! In this case, the difference is due to c24193b9 which introduced ip_num_columns = 1 in call to freeze_panes method.
@sandraros updating the reference file in this case, too.


Avoid Passing Null

Not sure if there is a rule for this yet, but it could probably done in a plugin.
Bad:
if (err) return cb(err, null)

Good:
if (err) return cb(err)

Why is that better?
getName(err, name = 'Default') {
   console.log(name); // might end up as `null`
});

In other words: functions that get called with a parameter named err should only have one parameter.

cb(null, "name") in this case is great, but cb(err, null) is bad news.
I think people are used to typing cb(null, data) when things go well, so sometimes they do cb(err, null when things go wrong.
There may be a case where you'd want to do cb(err, data), so I'm not sure you'd want to ban anything except null explicitly.

functions that get called with a parameter named err should only have one parameter.

Unless you're callback is just a pass-through:
f(..., function (err, result) {
  console.log('Wrapper called with ', x)

  callback(err, result)
})

@dcousens Good point. So there's no way to reliably enforce this.
@xjamundx I think it would be a mistake to write code that assumes that the value will be undefined just because there's an err. You should check if there's an err explicitly every time.

Hmm probably a good point (this came up at work today and we found it was
happening in a few places). Probably we should avoid null in general at
this point, but community isn't there yet :)
On Tue, Mar 15, 2016 at 5:34 PM Feross Aboukhadijeh <
<EMAIL_ADDRESS>wrote:

@dcousens https://github.com/dcousens Good point. So there's no way to
reliably enforce this.
@xjamundx https://github.com/xjamundx I think it would be a mistake to
write code that assumes that the value will be undefined just because
there's an err. You should check if there's an err explicitly every time.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/feross/standard/issues/460#issuecomment-197084971


Unable to start local instance of FCC

Greetings,
I believe I've installed all the dependencies correctly. However, when I gulp this error is thrown.
No idea what am I missing out on.
C:\My Place\FCC\FreeCodeCamp>gulp
module.js:442
    throw err;
    ^

Error: Cannot find module 'babel-helpers'
    at Function.Module._resolveFilename (module.js:440:15)
    at Function.Module._load (module.js:388:25)
    at Module.require (module.js:468:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (C:\My Place\FCC\FreeCodeCamp\node_modules\babel-core\lib\transformation\file\index.js:34:45)
    at Module._compile (module.js:541:32)
    at Object.Module._extensions..js (module.js:550:10)
    at Module.load (module.js:458:32)
    at tryModuleLoad (module.js:417:12)
    at Function.Module._load (module.js:409:3)

C:\My Place\FCC\FreeCodeCamp>

Node - v6.2.0
npm - 3.8.9

Also tried npm install --save babel-helpers. No luck.

I'm not able to reproduce this error. Have you tried removing your node_modules folder from the FreeCodeCamp folder and doing a fresh npm install?

Go to bed Einstein   I am
Sent from my iPhone6c

On May 23, 2016, at 7:56 AM, Logan Tegman<EMAIL_ADDRESS>wrote:
I'm not able to reproduce this error. Have you tried removing your node_modules folder from the FreeCodeCamp folder and doing a fresh npm install?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub

@adityaparab alternatively you can follow the recommended versions of the node and npm as mentioned on the Contributing guidelines and seek any assistance in the Contributors Chat room, its way faster to resolve your issue this way.

Closing as stale. As @raisedadead mentioned, using the same version of node/npm we use in production should solve this problem (node 4.X and npm 2). Thanks and happy coding!


Crashed on start

macOS 13.0.1 on M2 (arm64)
Installed from Homebrew.
Running zsh with Oh My Zsh framework (tried both Terminal app and iTerm2).
after running kalk :
[1]    33491 killed     kalk

It seems that the AOT version on ARM64 is failing. Only workaround for now is to have installed a .NET Runtime 7.0+ and install kalk as a global tool as explained here

@santisbon, 54MB (!!!) calculator that refuses to accept arguments to calculate directly from the command line, and when it goes into its own shell, it throws errors trying to calculate the percentages. Why do you need such a calculator?
If you like gigantomania, try Qalculate, otherwise Kalker is a fast and small alternative.
$ qalc 100+10%
100 * (110 * percent) = 110

$ kalker 100+10%
110

and when it goes into its own shell, it throws errors trying to calculate the percentages

% is a modulo operator, it's not percentage, hence the error.

It seems that the AOT version on ARM64 is failing. Only workaround for now is to have installed a .NET Runtime 7.0+ and install kalk as a global tool as explained here

Thanks. I had to install the .NET SDK, not just the runtime to dotnet tool install --global kalk successfully.
Also, although the latest version of the runtime is 8, I indeed had to use version 7 to run kalk.


Fix config.show format

I fixed format of show method to pass its test.

LGTM!

Aggg, sorry, I fixed the format just before the release since the tab is shown ugly on the screen. I forgot to update the test. Is it better to re-send a PR?


Do not handle providers special on a PropertyValue level

Calling Provider.isPresent() at task graph building time caused the resolution of some dependencies. We don't actually need to call isPresent() to determine the dependencies.
The PR slightly changes behaviour when a Provider is in a FileCollection: If the Provider is not present, then it is silently ignored, similarly to Callables returning null.

I took at look at the current behaviour of adding different absent lazy values to the different kind of file collections. For lazy values, we have

A Callable returning null
A DirectoryProperty/RegularFileProperty which is not present
A Provider<FileSystemLocation> which is not present

From those things, it is possible to create file collections by:

Project.files()
Project.fileTree()
Project.files().getAsFileTree()

For DirectoryProperty, one can also use DirectoryProperty.getAsFileTree().
When trying to resolve those file collections by calling FileCollection.files(), the file collections either ignore the non-present values or fail.
What I think should happen is that files() should be lenient in all cases, ignoring the not present properties/providers.

I took at look at the current behaviour of adding different absent lazy values to the different kind of file collections. For lazy values, we have

A Callable returning null
A DirectoryProperty/RegularFileProperty which is not present
A Provider<FileSystemLocation> which is not present

From those things, it is possible to create file collections by:

Project.files()
Project.fileTree()
Project.files().getAsFileTree()

For DirectoryProperty, one can also use DirectoryProperty.getAsFileTree().
When trying to resolve those file collections by calling FileCollection.files(), the file collections either ignore the non-present values or fail.
What I think should happen is that files() should be lenient in all cases, ignoring the not present properties/providers.

@lptr PTAL! I still need to add some more tests. The resolving seems to be fine now, though.

@lptr PTAL! I still need to add some more tests. The resolving seems to be fine now, though.

So we are not changing any behavior now?

The exception message changes slightly and we now allow having Provider<?> values in file collections which are not present. I'll add some tests to show that. Though it seems like we didn't have any tests for the behaviour.

So we are not changing any behavior now?

The exception message changes slightly and we now allow having Provider<?> values in file collections which are not present. I'll add some tests to show that. Though it seems like we didn't have any tests for the behaviour.

Superseded by https://github.com/gradle/gradle/pull/15996


gluon marshalling complex foreign types

I’m trying to get marshalling a complex foreign type to work on stable (0.8.1).
I’d like to wrap a passed in immutable json::JsonValue and a mutable clone, pass those to gluon, run scripts on it to manipulate the data, then receive the mutated one back.
Is there any reason this might not work on 0.8.1? I’m struggling a bit and my life would be easier if rust’s orphan rules were less strict. Q
Details:
Taking a cue from the GluonUser example, I’m using a new struct JsonData {inner: JsonValue}, and struggling to get it to work.
Right now, I can’t seem to get the VmType trait on the JsonValue – does this technique only work for something that has a built-in generic?
impl  VmType for JsonData
where
JsonValue: 'static + VmType,
{
trait bound json::JsonValue: gluon_vm::api::VmType is not satisfied
impl VmType for JsonData
|      ^^^^^^ the trait gluon_vm::api::VmType is not implemented for json::JsonValue
Thanks.

This seems to be about https://docs.rs/json/0.11.13/json/enum.JsonValue.html ? If that is the case then it is correct that you can't use that directly since it is a foreign type and so you won't be able to implement a trait on it.
You can add a wrapper type like you seem to have but you can't add the where JsonValue: 'static + VmType, bound since it is impossible to implement VmType for the remote JsonValue type.
However, if I were to guess a little at what you want in the end I would actually recommend you depend on the git master for now as there are json support add if you enable the serialization feature which provides serialization and deserialization as well as Value type similar to JsonValue. Documentation is not quite up to date but the source is at https://github.com/gluon-lang/gluon/tree/master/std/json

Unless things go horribly wrong I hope to get 0.9 out during this weekend.

I'm removing the wheres and having other problems with make_type, but maybe this is going to be more of a documentation problem.
@Laegluin I have to say I don't yet know enough to understand your response - but I thank you for it. :)
@Marwes Yes. Okay, will try that. I feel like you're doing more work than I would have thought one would need to do, but maybe json is fundamentally special.
I started looking at how std::io and the like are done, and I don't understand them either, so what do I know. :).
Thank you for your efforts.

Small update wrt master:
the #[repr(transparent)] attribute is experimental (see issue #43036)
My colleagues are against relying on stuff that needs nightly.
Thanks.

Yes. Okay, will try that. I feel like you're doing more work than I would have thought one would need to do, but maybe json is fundamentally special.

It isn't special in any way, if you had https://docs.rs/json/0.11.13/json/enum.JsonValue.html defined in your own crate then you could easily implement VmType, Pushable and Getable for it (even derive it automatically, as long as all the internal values also get an implementation of the traits).
The issue is only that it is awkward to work with remote types (even serde has issues with this, the remote attribute it uses to workaround this is something I might add at some point https://serde.rs/container-attrs.html#serderemote--).
It is things I 100% want to make easier, but it is still a lot of work to get all the way there.
Another that that would work if you dont want to use master is to define an equivalent to https://docs.rs/json/0.11.13/json/enum.JsonValue.html in your own crate and then add a pair of conversion functions to convert between your JsonValue and the one in the json crate. Then you would only need to convert between these types in the Rust gluon layer but could otherwise derive the necessary traits.


[RA-23651] Bound autosizing on vertical and horizontal

Column widths should autosize.
Row heights are not autosized. The height is determined by the new lines in the cell.

I guess I should do my inline comments after the pull request. I thought I did, but maybe I did them on my branch so they don't show on the file diff here.


Editorial not coming

Editorial not coming on the opening of the premium question, only prompt/question statement is coming.
How to overcome this issue.

Hey, here is how to fix @UddeshyaSeth : https://github.com/31b4/Leetcode-Premium-Bypass/issues/14

@UddeshyaSeth sorry that's not possible 😂
you have to buy premium for that, the most we can do is show you the question.
and believe me you dont need that perticular question, the only thing you need is the pattern so just search for the pattern that question uses and you will get questions like that


Svelte type definition fix

https://github.com/concretesolutions/redux-zero/issues/47

@Kiho
Thanks for this!
Could you please:

Update the npm version (4.3.1)
Add this to the CHANGELOG

Closing because #57 is more generic


🐞  Error occurs while creating a poll.

Context
Cannot convert stake1u8rfysygca8m9x0qypxrutl5j2n9c252mev4qmwdtzw****![Image](https://github.com/user-attachments/assets/02437e02-672c-4db2-b7c8-e10905bdda27)  to a BigInt
Error is occurring in userDto function within checkIfCO where stake key is passed but user_id is expected
Actual Behaviors

Context
Also due to same issue cannot access /representatice/manage page
local

Deployed

As of Nov-25, this issue has been resolved by the dev team


Figure out why nodes are running out of memory on Tutum

Tutum nodes keep running out of memory, not sure if it's Tutum/Docker that's causing it or what's running inside the containers (Node?). It happens on both nodes with 500 MB and 1 GB of memory.

I've set up swap memory on the VMs, since I realized this was missing.

Closing it for now.


[Question] Performance consideration

I am using the JwtSecurityTokenHandler for encoding and decoding/validating JWT.
I use the JWT as SET.
I have a high load of JWT, and I have some issues with the current implementation of the handler.
First of all, I have to pass by ClaimPrincipal and Claim which are perfect for the usage of JWT as identity, by useless for other usages. As Claims are basically a key/value string pair, I have to convert back to JSON if the value were a JSON content type. (JSON => string => JSON).
The second performance issue seems to be on the Base64UrlEncoder. Encoding produce a lot of string allocations, mainly due to the Split().
Do you plan to enhance the JWT performance, or even to split the packages (IdentityModel feature on one side, JWT management on the other side) ?
Am I using the correct library for my usage (a JWT not for the identity) ?

@ycrumeyrolle you would like ValidateToken that just returns JSON ?
Can you provide some details on the performance issue with Base64UrlEncoder (split)? How did you detect this?

A ValidateToken that just return the JSON may be a good idea. As a string? As a JObject?
Here is my current code for illustration:
            if (!_jwtHandler.CanReadToken(token))
            {
                return JwtParsingResult.ParseError();
            }

            var set = _jwtHandler.ReadJwtToken(token);

            var eventStream = await _eventReceiverMetadataProvider.GetAsync(set.Issuer);
            if (eventStream == null)
            {
                return JwtParsingResult.IssuerError();
            }

            var validationParameters = new TokenValidationParameters
            {
                IssuerSigningKey = ConvertToSecurityKey(eventStream.FeedJwk),
                ValidAudiences = eventStream.Audiences,
                ValidIssuer = set.Issuer
            };
            SecurityToken securityToken;
            _jwtHandler.ValidateToken(token, validationParameters, out securityToken);
            var jwtSecurityToken = (JwtSecurityToken)securityToken;
            var claims = new Dictionary<string, JToken>();
            foreach (var claim in jwtSecurityToken.Claims)
            {
                switch (claim.ValueType)
                {
                    case JsonClaimValueTypes.Json:
                        claims.Add(claim.Type, JObject.Parse(claim.Value));
                        break;
                    case JsonClaimValueTypes.JsonArray:
                        claims.Add(claim.Type, JArray.Parse(claim.Value));
                        break;
                    case ClaimValueTypes.String:
                    case ClaimValueTypes.Integer:
                        claims.Add(claim.Type, new JValue(claim.Value));
                        break;
                    default:
                        break;
                }
            }
            // ...

About the Base64UrlEncoder, I just run a memory profiling and the Split() within the Encode() caused about 7.5% of the total allocation, which seems a lot just for removing trailing padding.

@ycrumeyrolle thinking about this some more, I am wondering if we should move away from returning a ClaimsPrincipal, just validate JWT and then return the Json in the payload as JSON.net objects.
Another possibility is to have a JsonClaimsIdentity that has JSON, integrating into the asp.net stack will require to return Claims. The runtime doesn't support custom ClaimsIdentities, so it would be lost there. However, for your scenario, it may work.

Maybe something like
public virtual JObject/string ValidateToken(string token, TokenValidationParameters validationParameters) { }

?

@ycrumeyrolle I opened the following to add such a feature: https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/issues/660


Json log missing - due to fields format changing

Describe the feature
Customer Json log partially lost, stored in backup bucket. After deep dive, it's come up to the jason fields format has been changed.
Use Case
When the Json fields format changes, it's leading that log partially lost.
Proposed Solution
Workaround: adjust the index template, setting the changed fields can not be index in the opensearch.
Other Information
No response
Solution version used
V1.2.0

For JSON logs, we will ingest all unconfigured fields.


Error says duplicates on data/required but none found

What version of Ajv are you using? Does the issue happen if you use the latest version?
<script src="https://cdnjs.cloudflare.com/ajax/libs/ajv/6.12.4/ajv.min.js" integrity="sha512-jT80r/QIunAH3Bng0028a3kMjhpr+ApSrAjshiM+0+6s/O01//jwogIby3WnFle7UxDas+/gf3BgI4Rjju17ww==" crossorigin="anonymous"></script>

Ajv options object

{allErrors: true, jsonPointers: true}

JSON Schema

{
"@context": {
"owl": "http://www.w3.org/2002/07/owl/",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"xsd": "http://www.w3.org/2001/XMLSchema#",
"schema": "http://schema.org/",
"n3c": "http://discovery.biothings.io/"
},
"@id": "https://discovery.biothings.io/view/n3c/",
"@graph": [
{
"@id": "n3c:Dataset",
"@type": "rdfs:Class",
"rdfs:label": "Dataset",
"rdfs:comment": "This is the schema for describing the Dataset schema used for N3C.",
"rdfs:subClassOf": {
"@id": "schema:Dataset"
},
"schema:isPartOf": {
"@id": "https://discovery.biothings.io/view/n3c/"
},
"$validation": {
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"properties": {
"name": {
"description": "Descriptive name of the dataset",
"type": "string"
},
"description": {
"description": "Longer description of what is contained in the dataset",
"type": "string"
},
"author": {
"description": "Name of the author or organization that created the dataset.  Note: schema.org/author and schema.org/organization have additional fields that can provide more information about the author/organization, if desired.",
"anyOf": [
{
"$ref": "#/definitions/person"
},
{
"type": "array",
"items": {
"$ref": "#/definitions/person"
}
},
{
"$ref": "#/definitions/organization"
},
{
"type": "array",
"items": {
"$ref": "#/definitions/organization"
}
}
]
},
"license": {
"description": "A license document that applies to this content, typically indicated by a URL.",
"type": "string"
},
"cost": {
"description": "Specify the cost to obtain the dataset, \"Free\", \"Subscription\" or others",
"type": "string"
},
"url": {
"description": "The main URL about the dataset",
"type": "string",
"format": "uri"
},
"identifier": {
"description": "identifier for the dataset in a shared repository (GEO, Zenodo, figshare, etc)",
"type": "string"
},
"contain_geo_codes": {
"description": "Does the dataset contains GEO codes (e.g. zip codes)?",
"type": "boolean"
},
"contain_phi": {
"description": "Does the dataset contains Protected health information (PHI)?",
"type": "boolean"
},
"justification": {
"description": "How is the dataset relevant to the N3C project, why does the community want and how can it be used?",
"type": "string"
},
"doi": {
"description": "The DOI for the dataset if available",
"type": "string"
},
"contact": {
"description": "Provide an email contact",
"type": "string"
},
"documentation": {
"description": "Provide the URL to the detailed documentation about the dataset",
"type": "string",
"format": "uri"
},
"funding": {
"description": "Funding that supports (sponsors) the collection of this dataset through some kind of financial contribution",
"oneOf": [
{
"$ref": "#/definitions/funding"
},
{
"type": "array",
"items": {
"$ref": "#/definitions/funding"
}
}
]
},
"keywords": {
"description": "A list of keywords associated with this dataset",
"oneOf": [
{
"type": "string"
},
{
"type": "array",
"items": {
"type": "string"
}
}
]
},
"measurementTechnique": {
"description": "A technique or technology used in a Dataset, corresponding to the method used for measuring the corresponding variable(s).",
"oneOf": [
{
"$ref": "#/definitions/controlledVocabulary"
},
{
"type": "array",
"items": {
"$ref": "#/definitions/controlledVocabulary"
}
}
]
},
"standards_used": {
"description": "A list of standards used in the dataset, e.g. OMOP.",
"oneOf": [
{
"type": "string"
},
{
"type": "array",
"items": {
"type": "string"
}
}
]
},
"citation": {
"description": "A citation to the dataset",
"oneOf": [
{
"$ref": "#/definitions/citation"
},
{
"type": "array",
"items": {
"$ref": "#/definitions/citation"
}
}
]
},
"release_frequency": {
"description": "How frequent is the new version of the dataset released (monthly, quarterly, etc)",
"type": "string"
},
"comment": {
"description": "Any other comments about this dataset?",
"type": "string"
},
"includedInDataCatalog": {
"description": "Data catalog(s) which contain this dataset.",
"oneOf": [
{
"$ref": "#/definitions/inclusionObject"
},
{
"type": "array",
"items": {
"$ref": "#/definitions/inclusionObject"
}
}
]
}
},
"required": [
"name",
"description",
"author",
"license",
"cost",
"url",
"identifier",
"contain_geo_codes",
"contain_phi",
"justification"
],
"definitions": {
"controlledVocabulary": {
"description": "collection of vocabulary terms defined in ontologies",
"@type": "CreativeWork",
"type": "string",
"vocabulary": {
"ontology": [
"efo",
"ncit",
"obi"
],
"children_of": [
"https://www.ebi.ac.uk/efo/EFO_0002694",
"http://purl.obolibrary.org/obo/NCIT_C20368",
"http://purl.obolibrary.org/obo/OBI_0000011"
]
},
"strict": false
},
"moreControlledVocabulary": {
"definition": "collection of vocabulary terms defined in ontologies",
"@type": "CreativeWork",
"type": "string",
"strict": false,
"vocabulary": {
"ontology": [
"efo",
"cido",
"epo",
"covid19"
],
"children_of": [
"https://www.ebi.ac.uk/efo/EFO_0001444",
"http://purl.obolibrary.org/obo/cido.owl",
"http://purl.obolibrary.org/obo/epo",
"https://bioportal.bioontology.org/ontologies/COVID19"
]
}
},
"baseOrgObject": {
"description": "A barebones Organization object to work around recursion issues in DDE",
"@type": "Organization",
"type": "object",
"properties": {
"name": {
"description": "name of the organization",
"type": "string"
},
"alternateName": {
"description": "Alternate name or Acronym for the organization.",
"type": "string"
}
},
"required": [
"name"
]
},
"person": {
"description": "Reusable person definition",
"@type": "Person",
"type": "object",
"properties": {
"name": {
"type": "string"
},
"givenName": {
"type": "string"
},
"familyName": {
"type": "string"
},
"orcid": {
"type": "string"
},
"affiliation": {
"oneOf": [
{
"$ref": "#/definitions/baseOrgObject"
},
{
"type": "array",
"items": {
"$ref": "#/definitions/baseOrgObject"
}
}
]
}
},
"required": [
"name"
]
},
"memberObject": {
"description": "Reusable person definition accounting for recursion issues in DDE",
"@type": "Person",
"type": "object",
"properties": {
"name": {
"type": "string"
},
"givenName": {
"type": "string"
},
"familyName": {
"type": "string"
},
"orcid": {
"type": "string"
},
"affiliation": {
"oneOf": [
{
"$ref": "#/definitions/baseOrgObject"
},
{
"type": "array",
"items": {
"$ref": "#/definitions/baseOrgObject"
}
}
]
}
},
"required": [
"name"
]
},
"organization": {
"description": "Reusable organization definition",
"@type": "Organization",
"type": "object",
"properties": {
"name": {
"type": "string"
},
"alternateName": {
"type": "string"
},
"affiliation": {
"$ref": "#/definitions/baseOrgObject"
},
"members": {
"oneOf": [
{
"$ref": "#/definitions/memberObject"
},
{
"type": "array",
"items": {
"$ref": "#/definitions/memberObject"
}
}
]
}
},
"required": [
"name"
]
},
"funding": {
"type": "object",
"@type": "MonetaryGrant",
"description": "Information about funding support",
"properties": {
"name": {
"type": "string",
"description": "The name of the monetary grant that funded/funds the Dataset"
},
"identifier": {
"type": "string",
"description": "Unique identifier(s) for the grant(s) used to fund the Dataset"
},
"funder": {
"description": "name of the funding organization",
"oneOf": [
{
"$ref": "#/definitions/baseOrgObject"
},
{
"type": "array",
"items": {
"$ref": "#/definitions/baseOrgObject"
}
}
]
},
"url": {
"type": "string",
"format": "uri",
"description": "award URL"
}
},
"required": [
"funder"
]
},
"citation": {
"description": "A citation object for a resource which is cited by the dataset (ie- is a derivative of the dataset) , related to the dataset, or from which the dataset was based on (ie- is derived from).",
"@type": "Thing",
"type": "object",
"properties": {
"name": {
"description": "Name of or title of the citation",
"type": "string"
},
"identifier": {
"description": "An identifier associated with the citation",
"type": "string"
},
"pmid": {
"description": "A pubmed identifier if available",
"type": "string"
},
"doi": {
"description": "A doi if available",
"type": "string"
},
"url": {
"description": "The url of the resource cited.",
"type": "string",
"format": "uri"
},
"citeText": {
"description": "The bibliographic citation for the referenced resource as is provided",
"type": "string"
}
},
"required": [
"name"
]
},
"inclusionObject": {
"description": "A data catalog which contains this dataset.",
"type": "object",
"properties": {
"name": {
"const": "N3C Datasets"
},
"url": {
"const": "https://ncats.nih.gov/n3c/"
}
}
}
}
}
},
{
"@id": "n3c:contain_geo_codes",
"@type": "rdf:Property",
"rdfs:comment": "Does the dataset contains GEO codes (e.g. zip codes)?",
"rdfs:label": "contain_geo_codes",
"schema:domainIncludes": {
"@id": "n3c:Dataset"
},
"schema:rangeIncludes": {
"@id": "schema:Boolean"
}
},
{
"@id": "n3c:contain_phi",
"@type": "rdf:Property",
"rdfs:comment": "Does the dataset contains Protected health information (PHI)?",
"rdfs:label": "contain_phi",
"schema:domainIncludes": {
"@id": "n3c:Dataset"
},
"schema:rangeIncludes": {
"@id": "schema:Boolean"
}
},
{
"@id": "n3c:doi",
"@type": "rdf:Property",
"rdfs:comment": "DOI for the dataset if available",
"rdfs:label": "doi",
"schema:domainIncludes": {
"@id": "n3c:Dataset"
},
"schema:rangeIncludes": {
"@id": "schema:Text"
}
},
{
"@id": "n3c:cost",
"@type": "rdf:Property",
"rdfs:comment": "Specify the cost to obtain the dataset, \"Free\", \"Subscription\" or others",
"rdfs:label": "cost",
"schema:domainIncludes": {
"@id": "n3c:Dataset"
},
"schema:rangeIncludes": {
"@id": "schema:Text"
}
},
{
"@id": "n3c:justification",
"@type": "rdf:Property",
"rdfs:comment": "How is the dataset relevant to the N3C project, why does the community want and how can it be used?",
"rdfs:label": "justification",
"schema:domainIncludes": {
"@id": "n3c:Dataset"
},
"schema:rangeIncludes": {
"@id": "schema:Text"
}
},
{
"@id": "n3c:contact",
"@type": "rdf:Property",
"rdfs:comment": "Provide an email contact",
"rdfs:label": "contact",
"schema:domainIncludes": {
"@id": "n3c:Dataset"
},
"schema:rangeIncludes": {
"@id": "schema:Text"
}
},
{
"@id": "n3c:standards_used",
"@type": "rdf:Property",
"rdfs:comment": "A list of standards used in the dataset, e.g. OMOP.",
"rdfs:label": "standards_used",
"schema:domainIncludes": {
"@id": "n3c:Dataset"
},
"schema:rangeIncludes": {
"@id": "schema:Text"
}
},
{
"@id": "n3c:release_frequency",
"@type": "rdf:Property",
"rdfs:comment": "How frequent is the new version of the dataset released (monthly, quarterly, etc)",
"rdfs:label": "release_frequency",
"schema:domainIncludes": {
"@id": "n3c:Dataset"
},
"schema:rangeIncludes": {
"@id": "schema:Text"
}
},
{
"@id": "n3c:documentation",
"@type": "rdf:Property",
"rdfs:comment": "Provide the URL to the detailed documentation about the dataset",
"rdfs:label": "documentation",
"schema:domainIncludes": {
"@id": "n3c:Dataset"
},
"schema:rangeIncludes": {
"@id": "schema:URL"
}
},
{
"@id": "n3c:funding",
"@type": "rdf:Property",
"rdfs:comment": "Funding for the generation of the dataset",
"rdfs:label": "funding",
"schema:domainIncludes": {
"@id": "n3c:Dataset"
},
"schema:rangeIncludes": {
"@id": "schema:MonetaryGrant"
}
}
]
}

Sample data

{
  "@type": "n3c:Dataset",
  "@context": {
    "schema": "http://schema.org/",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "bts": "http://schema.biothings.io/",
    "xsd": "http://www.w3.org/2001/XMLSchema#",
    "owl": "http://www.w3.org/2002/07/owl/",
    "niaid": "https://discovery.biothings.io/view/niaid/",
    "outbreak": "https://discovery.biothings.io/view/outbreak/",
    "n3c": "http://discovery.biothings.io/"
  },
  "name": "name",
  "description": "some description",
  "author": {
    "@type": "Person",
    "name": "First Last",
    "givenName": "First",
    "familyName": "Last",
    "orcid": "abc123",
    "affiliation": {
      "name": "company",
      "alternateName": "otherName"
    }
  },
  "license": "CC0",
  "cost": "some text",
  "url": "myurl.com",
  "identifier": "fdsaffdsaf",
  "contain_geo_codes": "true",
  "contain_phi": "true",
  "justification": "fdsafasdfasdk fhsl flk sdalkfjkl"
}

Your code

var ajv = new Ajv({allErrors: true, jsonPointers: true});
        // ajv.addMetaSchema()
        var schema = state.schema.validation
        var data = state.output

        const isValid = ajv.validate(schema, data); //schema, data
        if(! isValid){
          // console.log('%c ***** VALIDATION DETAILS *****','color:pink')
          // console.log("NOT VALID ",ajv.errors);
          state.valid = false;
          state.errors = ajv.errors;
        }else {
          // console.log('%c ***** VALIDATION RESULT *****','color:limegreen')
          // console.log(isValid)
          state.valid = true;
          state.errors = []
        }

Validation result, data AFTER validation, error messages
Uncaught Error: schema is invalid: data/required should NOT have duplicate items (items ## 10 and 6 are identical)

What results did you expect?
I don't see any duplicates on required or on the data being validated so I would expect it to validate
Are you going to resolve the issue?
I've tried adding older meta schemas with addMetaSchema but with no luck. I need help

Please reduce the example to the minimal size when it is still failing and post the failing code sample to runkit.com - it’s not clear what is what in the provided code.

It does look like the schema above and what is passed to Ajv are different

Hi, thank you I created this but this works. https://runkit.com/marcodarko/avj-schema-validator-test. However I'm not using node so I can't get the same error I see on my inspector console.

I'm sorry I updated the schema on this issue and the runkit version should be accurate too, I included the whole thing by accident but updated it to the part that avj receives. is the CDN version not up to date maybe? idk

Try reproducing it in a single script in the browser without dependencies - same script that works in runkit should work in the browser. There is nothing browser specific, unless you have some old browser.
Looking at the error, the schema above and what is passed to Ajv is not the same - so the problem might be in your code.
I’m going to close this issue - re-submit as browser / compatibility if these suggestions won’t help.

Also please use schema under say 20 lines - most issue usually can be reproduced with this size.

Just FYI I was able to reproduce the same error here : https://runkit.com/marcodarko/avj-schema-validator-test

“Required” on line 551 has a duplicate item “identifier”.

On 28 Sep 2020, at 22:59, Marco Cano<EMAIL_ADDRESS>wrote:

Just FYI I was able to reproduce the same error here : https://runkit.com/marcodarko/avj-schema-validator-test
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.


[bug/ios] background controls not show on IOS

Configuration
react-native-cli: 2.0.1
react-native: 0.61.5
react-native-track-player: ^2.0.0-rc13
xcode: version 11.3.1 (11C504)
Issue
Problems only at ios, when in background not show the action buttons and the quality of audio is decreased with hls type.
Code
###service.js

import TrackPlayer, {Event} from 'react-native-track-player';
module.exports = async function() {
TrackPlayer.addEventListener(Event.RemotePlay, () => TrackPlayer.play());
TrackPlayer.addEventListener(Event.RemotePause, () => TrackPlayer.pause());
};

init
import {put, call, select, all, takeLatest, take} from 'redux-saga/effects';
import {eventChannel} from 'redux-saga';
import * as PlayerActions from './actions';
import TrackPlayer, {Capability, Event, State} from 'react-native-track-player';
export function* setupTrackPlayer() {
console.log('setup TrackPlayer');
yield call(TrackPlayer.setupPlayer);
// yield call(TrackPlayer.reset);
TrackPlayer.updateOptions({
waitForBuffer: true,
stopWithApp: false,
capabilities: [Capability.Play, Capability.Pause, Capability.Stop],
// compactCapabilities: [Capability.Play, Capability.Pause, Capability.Stop],
// notificationCapabilities: [
//   Capability.Play,
//   Capability.Pause,
//   Capability.Stop,
// ],
});
yield call(statusChanged);
yield call(trackChanged);
}
function* statusChanged() {
const channel = eventChannel(emitter => {
const onStatusChanged = TrackPlayer.addEventListener(
Event.PlaybackState,
emitter,
);
return () => onStatusChanged.remove();
});
try {
while (true) {
const {state} = yield take(channel);
yield put(PlayerActions.setState({state}));
if (state === State.Ready) {
yield put(PlayerActions.play());
}
}
} finally {
channel.close();
}
}
function* trackChanged() {
const channel = eventChannel(emitter => {
const onTrackChange = TrackPlayer.addEventListener(
Event.PlaybackTrackChanged,
emitter,
);
return () => onTrackChange.remove();
});
try {
while (true) {
const res = yield take(channel);
console.tron.log(res);
}
} finally {
channel.close();
}
}
export function* setPodcast({podcast, episodeId}) {}
export function* setPlaylist(action) {
try {
const {playlist, header} = action.payload;
yield call(TrackPlayer.stop);
yield call(TrackPlayer.reset);
const array = [...playlist];
yield call(TrackPlayer.add, array);
// yield call(TrackPlayer.play);
} catch (error) {
console.log(error);
}
}
function* play() {
TrackPlayer.play();
}
function* pause() {
TrackPlayer.pause();
}
export function* prev() {}
export function* next() {}
export default all([
takeLatest('@player/setup', setupTrackPlayer),
takeLatest('@player/play', play),
takeLatest('@player/pause', pause),
takeLatest('@player/setPlaylist', setPlaylist),
]);

someone can help me?

Did you figure it out?


Rename to sentry_plugin?

Having dart in the name doesn't make that much sense on pub.dev - consider renaming to sentry_plugin (or is there a better name) before releasing the first version. Unfortunately, we can't rename a published package, the old one would need to be archived/deleted. Maybe the trouble is worth it 🤷
Or maybe even move it to the main sentry_dart as an additional binary, so people don't have to add yet another dependency?

Sentry has many plugins and the dart in it helps to distinguish them, that was the idea, every other plugin has the platform name such as Sentry Android Gradle Plugin.

Or maybe even move it to the main sentry_dart as an additional binary, so people don't have to add yet another dependency?

That would make it into the final binary increasing the App's bundle, or how else would you suggest?

While I agree with your statement, @vaind, I think renaming it to sentry_plugin on pub.dev is not worth the hassle.

Sentry has many plugins and the dart in it helps to distinguish them, that was the idea, every other plugin has the platform name such as Sentry Android Gradle Plugin.

yeah, I get that, though in my eyes that applies to the repo name, not the package name on pub.dev - the same way this isn't called sentry_dart

That would make it into the final binary increasing the App's bundle, or how else would you suggest?

not really, unless they actually use the code directly in their app - which isn't really a normal use case.

While I agree with your statement, @vaind, I think renaming it to sentry_plugin on pub.dev is not worth the hassle.

Totally got that

@vaind

not really, unless they actually use the code directly in their app - which isn't really a normal use case.

Do you mean adding as a dev_dependency or relying on Tree shaking?

@vaind we've agreed that renaming isn't worth the pain, so I'd close this issue, thanks for the feedback anyway.

Or maybe even move it to the main sentry_dart as an additional binary, so people don't have to add yet another dependency?

This one actually makes sense and we'd like to discuss it further, would you like to raise a new issue for that?


refactor: remove redundant mergeWith in ng-new

Looks like it's needed after all
ENOENT: no such file or directory, rename '/tmp/angular-cli-e2e-xa5Rjf/subdirectory/.git/HEAD' -> '/tmp/angular-cli-e2e-xa5Rjf/subdirectory/subdirectory-test-project/.git/HEAD'


Knowledge - Assistant - Show the list of knowledge files associated with an assistant in chat view

Electron build from - 37b7672110
Steps to reproduce the problem:

Create an assistant.
Use "+ Files" option and add few files
Chat with this assistant.

Notice that  clicking on Knowledge icon shows no knowledge files associated with the assistant.
Expected Behavior:
We should be able to provide information about all the files associated with the assistant in the chat view.

This is not necessarily the correct or desired behavior. We may not want to go down to that level of granularity. We may just want to show "This assistant has a custom knowledge set." The source documents may or may not be relevant to the end user.

This issue is addressed when testing with electron build - fbd02fab


initial version of checksum based freshness

Implementation for https://github.com/rust-lang/cargo/issues/14136 and resolves https://github.com/rust-lang/cargo/issues/6529
This PR implements the use of checksums in cargo fingerprints as an alternative to using mtimes. This is most useful on systems with poor mtime implementations.
This has a dependency on https://github.com/rust-lang/rust/pull/126930. It's expected this will increase the time it takes to declare a build to be fresh. Still this loss in performance may be preferable to the issues the ecosystem has had with the use of mtimes for determining freshness.

:umbrella: The latest upstream changes (presumably #13947) made this pull request unmergeable. Please resolve the merge conflicts.

Merge conflicts resolved.

:umbrella: The latest upstream changes (presumably #14590) made this pull request unmergeable. Please resolve the merge conflicts.

@bors try
Let's see how it really goes.

@bors try

:hourglass: Trying commit 4ddd017694a0415a7c91598153e642e3c2b26321 with merge 5b99bb7bc4645e2f33e933da4a809e516c5a3d45...

:broken_heart: Test failed - checks-actions

All tests are passed. I will do another round of review today.

@weihanglo All comments addressed in 9ede54d000c09e1824080d02bfbee647009def96
Also the PR has been rebased to remove some of the rejected designs for this feature.

@bors r? @weihanglo

@bors r+

:pushpin: Commit cf893c1695d96d4bddf5107b832df612d22b4612 has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit cf893c1695d96d4bddf5107b832df612d22b4612 with merge 15fbd2f607d4defc87053b8b76bf5038f2483cf4...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing 15fbd2f607d4defc87053b8b76bf5038f2483cf4 to master...

Is there a way we can tag this for mention in the release notes? May be worth giving a bit of celebration to :)

It has been listed in changelog of 1.83 already, under the nightly section! https://github.com/rust-lang/cargo/blob/master/CHANGELOG.md#cargo-183-2024-11-28
Though we haven't figured out the build script part (see https://github.com/rust-lang/cargo/issues/14136), maybe we could celebrate a bit later when we resolve that? :)

If anyone is interested in helping this go stabilized, please share your benchmark results for -Zchecksum-freshness on this Zulip topic, or in #14722.


Update README to include latest version on Conan

1.6.2 has been pushed to CCI, so I figured I'd give the README an update. Small change, but worth doing :)

err... I have a feeling this didn't cause failing CI :sweat_smile:

Nice, thanks!


CBL statement not recognized

CBL statement specifying compiler options at start of program is not recognized, as in
line 1:7 mismatched input 'CBL' expecting {ID, IDENTIFICATION, PROCESS}
   CBL ARITH(EXTEND)
   IDENTIFICATION DIVISION.
   ...

You are right, that's a bug. Fixed in b39ca6c92411fe7a8b09ef7e2fe9b22aaf349cc7 and added unit tests. PROCESS and CBL statements are now removed by the preprocessor.
I'm not 100% sure, if the syntax in Cobol85Preprocessor.g4 ist complete. If there are any PROCESS ... and CBL ... statements, which are not removed and thus lead to parsing errors in the parsing step, please let me know.
Thanks!

By the way, since today there is a new version 2.2.0-SNAPSHOT, so 2.1.0 does not contain the fix. Just in case you are fetching the parser by MAVEN dependencies instead of GIT.

I found a CBL ADV in one of the files I'm parsing;
java.lang.RuntimeException: syntax error in line 1:7 mismatched input 'CBL' expecting {ID, IDENTIFICATION}...

Thanks, hopefully fixed in f80ccbd1860eacc0e990c3f061b09a0c63f907cf.
Added a unit test.

Added a lot of other compiler options in that commit. Test suite is green. If this large commit produces problems with your files, please let me know.

fixed some errors in f510b3bc30e7001695179708a6e6660c73d367b2


README.md example in the section labeled Worker does not compile

Trying to follow the directions here to experiment with cadence and am unable to get the code in the readme to compile. This was with the current master revision of fbf8546955c8e16c42a11be402309ed6e253b0ce but I've also tried some of the more recent tags and they fail to compile as well. In particular, the function go.uber.org/cadence/.gen/go/cadence.NewTChanWorkflowServiceClient does not exist.
Could you update the README.md to reflect the current state of the code?

Thanks for letting us know. Will send out a PR for this shortly.


Colour contrast makes countdown text hard to read

What steps will reproduce the problem?

Installed the extension on Mac OS Sierra 10.12 running Chrome Version 56.0.2924.87 (64-bit)
Viewing on both the MacBook Pro screen or my Dell U2414 1920*1080 monitor
Colour contrast is insufficient between the pale green/teal and the white text (see screenshot)

What is the expected result?
I should be easily able to read the countdown timer on the widget icon that says how many minutes are remaining until my next meeting
What happens instead?
Due to the lack of colour contrast it is hard to read the text, particularly for numbers like 5,6,9,8 etc.
Screenshot URL: https://www.dropbox.com/s/8xlel8jbiyfogi5/Screenshot 2017-02-13 10.34.20.png?dl=0
Logs: Not required
System Information:
(This can be captured automatically if you click on Report Issue from the Chrome extension)

Installed the extension on Mac OS Sierra 10.12 running Chrome Version 56.0.2924.87 (64-bit)
Viewing on both the MacBook Pro Retina screen or my Dell U2414 1920*1080 monitor the same problem exists

[YES] I have read and performed all the steps listed under the Troubleshooting section:
https://github.com/manastungare/google-calendar-crx/wiki/Troubleshooting

That color is controlled by Chrome. Extensions can only specify a background color, which is the same as the calendar color.

Thanks that worked!

Readme


product type is not defined

Hi @Alex-Lewandowski
When I am trying to run this cell in Jupyter Notebook, I get this error. Previously, I did not receive such a error during the InASR time series processing time, but suddenly I got this error. Please look into it and thank you for your time and consideration.

In Alaska Vertex, I have this project. But it is not showing in Jupyter Notebook.

Hi @shubhayanroychowdhury,
It looks like your question relates to a notebook in a different repository: https://github.com/ASFOpenSARlab/opensarlab_MintPy_Recipe_Book/blob/main/3_Access_HyP3_Data.ipynb
However, I can provide an answer here. It appears that you have skipped running the code cell immediately prior to the one in the screenshot producing the error. It contains a single line of code, which defines product_type:

If you inadvertently deleted that or any other code cell, you can pull a fresh copy of the notebook onto your OpenSARLab  volume by deleting the notebook and restarting your server. This will automatically sync your repository and replace the missing notebook.
Best,
Alex


Minor Queue Visual Bugs

Queue arrows not placed correctly when queue is emptied. Additionally if queue exceeds a certain length, it will create an unappealing second row.

Resolved. See e5527f99c00c756e7ef3b39274a94a9a37652491


AP-3460 enhanced bank upload regular outgoings

What
Link to story

Add route, controller, form, view and content for regular outgoings page, so providers can select outgoing categories and add the amount and frequency of payment for each category
Add rspec tests for form and controller
Update existing rspec tests and feature tests

Checklist
Before you ask people to review this PR:

Tests and rubocop should be passing: bundle exec rake
Github should not be reporting conflicts; you should have recently run git rebase main.
There should be no unnecessary whitespace changes. These make diffs harder to read and conflicts more likely.
The PR description should say what you changed and why, with a link to the JIRA story.
You should have looked at the diff against main and ensured that nothing unexpected is included in your changes.
You should have checked that the commit messages say why the change was made.

I'll give this a full review on Monday, but it looks pretty good so far —nice work!
At a first glance, I reckon the transaction forms are ripe for some refactoring.
If you'd like to pair on it, feel free to chuck some time in my calendar anytime next week.


Automatically open the correct section using qa_expand_type

This is a new feature I plan to add soon. It will open up the correct section based on the query parameters.

It seems it is working for now, but it is not able to detect the difference between question answer and project help answer. I will leave this open for now.

Since this is your repo, why not start this under discussions or projects?

I don't know how to


=receptionist rdar://97586760 lookup() trying to cast stub actor

Depends on https://github.com/apple/swift-distributed-actors/pull/1027
Receptionist would bug out when trying to lookup() due to a wrongly implemented cast.

Resolves rdar://97586760

Sigh always one flaky test somewhere.
I'll spend this week tracking them all down 💯


record.kill() results in unreadable mp4

Firstly, I love this repo!
I am currently using this repo in a node webkit project and tried to apply a start record and stop record function. To be clearer, this is reading input from an rtmp stream where it doesn't have a "start" or "end" point.
var record=ffmpeg('http://<IP_ADDRESS>/hdmi')
.duration('1:00')
.audioBitrate(128)
.fps(25)
.videoBitrate('4096k')
.videoCodec('libx264')
.size('1920x1080')
.aspect('16:9')
.format('mp4')
.on('start',function(){
  console.log('started recording!')
})
.on('end', function() {console.log('saved');})
.on('error', function(err) { console.log(err);})
.save('C:/Users/Tony/output.mp4');

After using
record.kill();

If I let the time passed one minute, it did the record and can be opened properly. But if I want to manually stop it in between, it did save a file on the hard disk, but the mp4 file is not readable (I tried vlc and other players).
I have also tried omit the duration setting, but everything is still the same.
Can someone help? Thanks in advance.
Update:
if I remove all the video settings and use .noVideo() together with format('mp3')(which records mp3 only), it works pretty cool, the mp3 file is readable after manual kill.

Hi,
Good news is that I found a way to handle this.
I first directly record the stream into flv file (which works well with the manual kill),
then I start the transcode to mp4 after the "end" event of record. Anyway I love this repo~

Yeah, you cannot expect a valid mp4 when killing the process (notably, the default mp4 format has "headers" at the end of the file). You have to use specific options.

I face the same problem.
I'll try the flv to mp4 trick, but I'd love to know what options would allow me to just .kill() the command and have a valid file. I've tried .kill('SIGSTOP'), which doesn't throw an error (when the default SIGKILL does), but still results in an unreadable file.
@njoyard maybe ?

That's really a ffmpeg issue actually. Find a way to do that using command-line ffmpeg and the kill command, and I'll help you do it with fluent-ffmpeg.
You should ask the ffmpeg community about how to ensure having a valid output file even when interrupted, or maybe you'll have to resort to finding a way to fix the file afterwards.

Ok ! Thanks for your answer, I'll check this out and come back to you when I have further informations.

Hi 👋
I'm facing the same problem here.
Using ffmpeg CLI, and  using q when screen recording works well, and don't corrupt the fil. But I didn't find a trick w/ this package yet.
Would you have any idea ?
I didn't try the .flv trick tho.

Oops, nvm, regarding this issue (https://github.com/fluent-ffmpeg/node-fluent-ffmpeg/issues/673), you can do that command.ffmpegProc.stdin.write('q');
Thankks


The Token management function is not supported when pulsar Manager is deployed using helm Charts.

Fixes #
Motivation
In pulsar multi-tenant scenario, Pulsar Manager, as a management tool, provides a Web page for token management, but the helm deployment mode does not support token management.
Modifications

Add token management to Pulsar Manager when deploying pulsar using helm.
Mount asymmetric encryption Secret into the Pulsar Manager container and add asymmetric encryption related configurations in pulsar-manager-configmap.yaml.

Verifying this change

[ ] Make sure that the change passes the CI checks.

Closing this PR since it is outdated. Please create a new one if you'd like to make a contribution.


Form-floating form-control doesn't display placeholder

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
When I add the form-control class to an input element inside of a form-floating class, the placeholder value is not displayed.  This is a breaking change for me from Bootstrap v4.  When I change the form-control class to form-select, the placeholder is displayed.  I've used this as a workaround, but from a UI standpoint, it's not the best to have a dropdown arrow displayed on a non-dropdown element.
Reduced test cases
https://jsbin.com/jijopihebe/edit?html,output
What operating system(s) are you seeing the problem on?
Linux
What browser(s) are you seeing the problem on?
Chrome, Firefox
What version of Bootstrap are you using?
v 5.1.3

Select menus don't have placeholders, they show their first option. You're using a .form-select class on an input, which is incorrect. This also isn't a breaking change since the v4 version was just an example and not an officially supported component.
The docs mention how we use the placeholder to move the label. As of right now, we don't currently have an always showing placeholder option. I believe there's been a request for that in the past though I'm unsure of how feasible it is.

I realize that I was using the select class incorrectly, I was trying to illustrate the functionality that I was looking for.  Is there a ticket that I can follow for this functionality request?  It would really help my project.

For some reason bootstrap makes the color transparent. You can change it on focus to show the placeholder.
.form-control:focus::placeholder{color:black !important;}

Here is an idea to display the placeholder value when the control is focused and avoiding to use !important:
.form-floating > .form-control:focus::placeholder,
.form-floating > .form-control-plaintext:focus::placeholder {
    color: var(--bs-secondary-color);
    opacity: 0.5;
  }
}```


Updated SAI-Challenger to latest main as of May 30

This new version of SAI-Challenger auto-generates sai_thrift_metadata.py in run-time.
Fixes Issue https://github.com/sonic-net/DASH/issues/374

Hi @andriy-kokhan thanks for this. If this gets merged, would this allow @vijasrin to re-enable some of the tests which are skipped in https://github.com/sonic-net/DASH/pull/365 (except ones requiring changes to dpugen)?

Hi @andriy-kokhan thanks for this. If this gets merged, would this allow @vijasrin to re-enable some of the tests which are skipped in PR #365 (except ones requiring changes to dpugen)?

This PR enables metadata autogen. But one more improvement is needed - SaiObjType autogen which is addressed in https://github.com/sonic-net/DASH/pull/381.  With these two, some of the tests can be re-enabled. To do that, we will probably make another PR into #365.

Thanks for the clarification.


Tool Falsely Failed SA 0 for Erased Test Results

ETS-03-29-2022
SA 0 was failed for test results in Part 9.  This complaint may have cascaded from #1091.
The tool falsely flags that our controller erased DM5 data.
17:56:46.2271 Destination Specific DM5 Request to Engine #2 (1)
17:56:46.2316 18EA01F9 [3] CE FE 00 (TX)
17:56:46.2446 18FECE01 [8] 00 00 14 37 E0 02 E0 02
DM5 from Engine #2 (1): OBD Compliance: HD OBD (20), Active Codes: 0, Previously Active Codes: 0
FAIL: <IP_ADDRESS>.a - Engine #2 (1) erased DM5 data
DM5 from earlier in part 4:
17:56:31.7991 18FECE01 [8] 00 00 14 37 E0 02 E0 02
DM5 from Engine #2 (1): OBD Compliance: HD OBD (20), Active Codes: 0, Previously Active Codes: 0

This reminds me of #1034, where there was a 1-bit difference

What is needed to confirm this?

**_14 37 E0 02 E0 02 Is a composite value in
in 17:56:31.7991 18FECE01 [8] 00 00 14 37 E0 02 E0 02_**
Part 2 responses are.
Start Test 2.2 - DM5: Diagnostic readiness 1
14:38:02.2833 Global DM5 Request
14:38:02.2837 18EAFFF9 [3] CE FE 00 (TX)
14:38:02.2877 18FECE3D [8] 00 00 14 04 60 1C 60 1C
DM5 from Exhaust Emission Controller (61): OBD Compliance: HD OBD (20), Active Codes: 0, Previously Active Codes: 0
14:38:02.2884 18FECE01 [8] 00 00 14 37 A0 02 A0 02
DM5 from Engine #2 (1): OBD Compliance: HD OBD (20), Active Codes: 0, Previously Active Codes: 0
14:38:02.2926 18FECE00 [8] 00 00 14 04 00 00 00 00
DM5 from Engine #1 (0): OBD Compliance: HD OBD (20), Active Codes: 0, Previously Active Codes: 0
Vehicle Composite of DM5:
A/C system refrigerant     not supported,     complete
Boost pressure control sys     supported, not complete
Catalyst                   not supported,     complete
Cold start aid system      not supported,     complete
Comprehensive component        supported,     complete
Diesel Particulate Filter      supported, not complete
EGR/VVT system                 supported, not complete
Evaporative system         not supported,     complete
Exhaust Gas Sensor             supported, not complete
Exhaust Gas Sensor heater      supported, not complete
Fuel System                    supported, not complete
Heated catalyst            not supported,     complete
Misfire                        supported, not complete
NMHC converting catalyst       supported, not complete
NOx catalyst/adsorber          supported, not complete
Secondary air system       not supported,     complete
WARN: <IP_ADDRESS>.a (A6.2.d) - Exhaust Gas Sensor is supported by more than one OBD ECU
WARN: <IP_ADDRESS>.c - Required monitor Exhaust Gas Sensor is supported by more than one OBD ECU
14:38:02.8962 Destination Specific DM5 Request to Engine #1 (0)
14:38:02.8967 18EA00F9 [3] CE FE 00 (TX)
14:38:02.9019 18FECE00 [8] 00 00 14 04 00 00 00 00
DM5 from Engine #1 (0): OBD Compliance: HD OBD (20), Active Codes: 0, Previously Active Codes: 0
14:38:02.9038 Destination Specific DM5 Request to Engine #2 (1)
14:38:02.9056 18EA01F9 [3] CE FE 00 (TX)
14:38:02.9191 18FECE01 [8] 00 00 14 37 A0 02 A0 02
DM5 from Engine #2 (1): OBD Compliance: HD OBD (20), Active Codes: 0, Previously Active Codes: 0
14:38:02.9200 Destination Specific DM5 Request to Exhaust Emission Controller (61)
14:38:02.9213 18EA3DF9 [3] CE FE 00 (TX)
14:38:02.9277 18FECE3D [8] 00 00 14 04 60 1C 60 1C
DM5 from Exhaust Emission Controller (61): OBD Compliance: HD OBD (20), Active Codes: 0, Previously Active Codes: 0
End Test 2.2 - DM5: Diagnostic readiness 1

In Part 9, SA 0 fails, attributed to test data, and not DM5.
I think it is clear that SA 0 should have passed.
SA 0 Having no test data, or #1091, the manufacturer assigned SPs problem, each may explain the observed performance.  SA 0 had one positive response, for DM5, which did not change from Part 2.
15:26:23.8949 Global DM22 Request
15:26:23.8962 18C3FFF9 [8] 01 FF FF FF FF FF FF FF (TX)
15:26:24.4948 Timeout - No Response
15:26:24.4993 Global DM22 Request
15:26:24.5017 18C3FFF9 [8] 11 FF FF FF FF FF FF FF (TX)
15:26:25.0993 Timeout - No Response
<IP_ADDRESS>.d - Checking for erased diagnostic information
15:26:25.1048 Destination Specific DM6 Request to Engine #1 (0)
15:26:25.1054 18EA00F9 [3] CF FE 00 (TX)
15:26:25.1111 18E8FF00 [8] 01 FF FF FF F9 CF FE 00
Acknowledgment from Engine #1 (0): Response: NACK, Group Function: 255, Address Acknowledged: 249, PGN Requested: 65231
15:26:25.1123 Destination Specific DM12 Request to Engine #1 (0)
15:26:25.1143 18EA00F9 [3] D4 FE 00 (TX)
15:26:25.1208 18E8FF00 [8] 01 FF FF FF F9 D4 FE 00
Acknowledgment from Engine #1 (0): Response: NACK, Group Function: 255, Address Acknowledged: 249, PGN Requested: 65236
15:26:25.1212 Destination Specific DM23 Request to Engine #1 (0)
15:26:25.1234 18EA00F9 [3] B5 FD 00 (TX)
15:26:25.1307 18E8FF00 [8] 01 FF FF FF F9 B5 FD 00
Acknowledgment from Engine #1 (0): Response: NACK, Group Function: 255, Address Acknowledged: 249, PGN Requested: 64949
15:26:25.1311 Destination Specific DM29 Request to Engine #1 (0)
15:26:25.1326 18EA00F9 [3] 00 9E 00 (TX)
15:26:25.1407 18E8FF00 [8] 01 FF FF FF F9 00 9E 00
Acknowledgment from Engine #1 (0): Response: NACK, Group Function: 255, Address Acknowledged: 249, PGN Requested: 40448
15:26:25.1411 Destination Specific DM5 Request to Engine #1 (0)
15:26:25.1424 18EA00F9 [3] CE FE 00 (TX)
15:26:25.1507 18FECE00 [8] 00 00 14 04 00 00 00 00
DM5 from Engine #1 (0): OBD Compliance: HD OBD (20), Active Codes: 0, Previously Active Codes: 0
15:26:25.1523 Destination Specific DM25 Request to Engine #1 (0)
15:26:25.1529 18EA00F9 [3] B7 FD 00 (TX)
15:26:25.1607 18E8FF00 [8] 01 FF FF FF F9 B7 FD 00
Acknowledgment from Engine #1 (0): Response: NACK, Group Function: 255, Address Acknowledged: 249, PGN Requested: 64951
15:26:25.1616 Destination Specific DM31 Request to Engine #1 (0)
15:26:25.1633 18EA00F9 [3] 00 A3 00 (TX)
15:26:25.1707 18E8FF00 [8] 01 FF FF FF F9 00 A3 00
Acknowledgment from Engine #1 (0): Response: NACK, Group Function: 255, Address Acknowledged: 249, PGN Requested: 41728
15:26:25.1709 Destination Specific DM21 Request to Engine #1 (0)
15:26:25.1728 18EA00F9 [3] 00 C1 00 (TX)
15:26:25.1807 18E8FF00 [8] 01 FF FF FF F9 00 C1 00
Acknowledgment from Engine #1 (0): Response: NACK, Group Function: 255, Address Acknowledged: 249, PGN Requested: 49408
15:26:25.1817 Destination Specific DM26 Request to Engine #1 (0)
15:26:25.1829 18EA00F9 [3] B8 FD 00 (TX)
15:26:25.1904 18E8FF00 [8] 01 FF FF FF F9 B8 FD 00
Acknowledgment from Engine #1 (0): Response: NACK, Group Function: 255, Address Acknowledged: 249, PGN Requested: 64952
FAIL: <IP_ADDRESS>.d - Engine #1 (0) erased Test Results data

It appears Engine #1 SA 1 passes.
15:26:25.1919 Destination Specific DM6 Request to Engine #2 (1)
15:26:25.1933 18EA01F9 [3] CF FE 00 (TX)
15:26:25.2123 18FECF01 [8] 43 FF 00 00 00 00 FF FF
DM6 from Engine #2 (1): MIL: on, RSL: off, AWL: off, PL: not supported, No DTCs
15:26:25.2129 Destination Specific DM12 Request to Engine #2 (1)
15:26:25.2148 18EA01F9 [3] D4 FE 00 (TX)
15:26:25.2189 18FED401 [8] 43 FF 9B 01 04 01 FF FF
DM12 from Engine #2 (1): MIL: on, RSL: off, AWL: off, PL: not supported
DTC 411:4 - Engine EGR 1 Differential Pressure, Voltage Below Normal, Or Shorted To Low Source - 1 times
15:26:25.2201 Destination Specific DM23 Request to Engine #2 (1)
15:26:25.2214 18EA01F9 [3] B5 FD 00 (TX)
15:26:25.2324 18FDB501 [8] 43 FF 44 15 01 01 FF FF
DM23 from Engine #2 (1): MIL: on, RSL: off, AWL: off, PL: not supported
DTC 5444:1 - Engine Crankcase Breather Oil Separator Speed, Data Valid But Below Normal Operational Range - Most Severe Level - 1 times
15:26:25.2333 Destination Specific DM29 Request to Engine #2 (1)
15:26:25.2349 18EA01F9 [3] 00 9E 00 (TX)
15:26:25.2389 189EF901 [8] 00 FF 01 01 01 FF FF FF
DM29 from Engine #2 (1):
Emission-Related Pending DTC Count                               0
All Pending DTC Count                                not available
Emission-Related MIL-On DTC Count                                1
Emission-Related Previously MIL-On DTC Count                     1
Emission-Related Permanent DTC Count                             1
15:26:25.2398 Destination Specific DM5 Request to Engine #2 (1)
15:26:25.2414 18EA01F9 [3] CE FE 00 (TX)
15:26:25.2507 18FECE01 [8] 01 01 14 37 A0 02 A0 02
DM5 from Engine #2 (1): OBD Compliance: HD OBD (20), Active Codes: 1, Previously Active Codes: 1
15:26:25.2509 Destination Specific DM25 Request to Engine #2 (1)
15:26:25.2529 18EA01F9 [3] B7 FD 00 (TX)
15:26:25.6603 18FDB701 [136] 87 44 15 01 01 F8 9B 00 00 42 0F 9F 00 0A C8 26 52 3C C6 72 89 3D 1A 01 80 23 9E 2B B0 00 00 16 BA 30 8A 8A 80 3B 60 1F C0 28 20 32 C5 AF E1 E2 D0 FB 09 1F 6C 24 44 60 44 60 44 60 44 60 44 60 44 60 44 60 6B 27 F9 47 42 08 24 FF 34 9C 34 A5 38 3B 3A A3 39 65 00 65 00 C1 07 3C 1E 00 0E 00 00 00 00 01 0D E0 04 00 7C D9 37 34 07 A5 38 A3 39 17 04 C0 3D C0 3D 01 FF FE 00 0E 02 EC 79 04 FF FF 1A 00 BE 05 42 05
DM25 from Engine #2 (1):
Freeze Frames: [
Freeze Frame: {
DTC 5444:1 - Engine Crankcase Breather Oil Separator Speed, Data Valid But Below Normal Operational Range - Most Severe Level - 1 times
SPN Data: F8 9B 00 00 42 0F 9F 00 0A C8 26 52 3C C6 72 89 3D 1A 01 80 23 9E 2B B0 00 00 16 BA 30 8A 8A 80 3B 60 1F C0 28 20 32 C5 AF E1 E2 D0 FB 09 1F 6C 24 44 60 44 60 44 60 44 60 44 60 44 60 44 60 6B 27 F9 47 42 08 24 FF 34 9C 34 A5 38 3B 3A A3 39 65 00 65 00 C1 07 3C 1E 00 0E 00 00 00 00 01 0D E0 04 00 7C D9 37 34 07 A5 38 A3 39 17 04 C0 3D C0 3D 01 FF FE 00 0E 02 EC 79 04 FF FF 1A 00 BE 05 42 05
}
]
15:26:25.6639 Destination Specific DM31 Request to Engine #2 (1)
15:26:25.6654 18EA01F9 [3] 00 A3 00 (TX)
15:26:25.6824 18E8FF01 [8] 01 FF FF FF F9 00 A3 00
Acknowledgment from Engine #2 (1): Response: NACK, Group Function: 255, Address Acknowledged: 249, PGN Requested: 41728
15:26:25.6834 Destination Specific DM21 Request to Engine #2 (1)
15:26:25.6843 18EA01F9 [3] 00 C1 00 (TX)
15:26:25.6903 18C1F901 [8] 00 00 00 00 04 00 15 00
DM21 from Engine #2 (1): [
Distance Traveled While MIL is Activated:     0 km (0 mi)
Time Run by Engine While MIL is Activated:    4 minutes
Distance Since DTCs Cleared:                  0 km (0 mi)
Time Since DTCs Cleared:                      21 minutes
]
15:26:25.6922 Destination Specific DM26 Request to Engine #2 (1)
15:26:25.6938 18EA01F9 [3] B8 FD 00 (TX)
15:26:25.6987 18FDB801 [8] 00 00 00 37 A0 02 A0 02
DM26 from Engine #2 (1): Warm-ups: 0, Time Since Engine Start: 0 seconds
15:26:25.6996 Sending DM7 for DM30 to Engine #2 (1) for SPN 157
15:26:25.7017 18E301F9 [8] F7 9D 00 1F FF FF FF FF (TX)
15:26:25.7622 18A4F901 [12] F7 9D 00 0A 5E 01 B8 7D A4 88 5C 71
DM30 from 1: SPN 157 FMI 10 (SLOT 350) Result: Test Passed. Min: -149, Value: 9.2, Max: 149 l/h
15:26:25.7651 Destination Specific DM20 Request to Engine #2 (1)
15:26:25.7664 18EA01F9 [3] 00 C2 00 (TX)
15:26:25.8819 18C2F901 [32] 0A 00 01 00 C6 14 F8 00 00 01 00 F2 0B F8 00 00 01 00 C9 14 F8 00 00 01 00 EF 0B F8 00 00 01 00
DM20 from Engine #2 (1):  [
Num'r /  Den'r
Ignition Cycles                                                       10
OBD Monitoring Conditions Encountered                                  1
SPN 5318 AFT Exhaust Gas Sensor System Monitor                0 /      1
SPN 3058 Engine EGR System Monitor                            0 /      1
SPN 5321 Engine Intake Manifold Pressure System Monitor       0 /      1
SPN 3055 Engine Fuel System Monitor                           0 /      1
]
15:26:25.8849 Destination Specific DM28 Request to Engine #2 (1)
15:26:25.8866 18EA01F9 [3] 80 FD 00 (TX)
15:26:25.8987 18FD8001 [8] 43 FF 9B 01 04 01 FF FF
DM28 from Engine #2 (1): MIL: on, RSL: off, AWL: off, PL: not supported
DTC 411:4 - Engine EGR 1 Differential Pressure, Voltage Below Normal, Or Shorted To Low Source - 1 times
15:26:25.8996 Destination Specific DM33 Request to Engine #2 (1)
15:26:25.9017 18EA01F9 [3] 00 A1 00 (TX)
15:26:25.9727 18A1F901 [18] 01 00 00 00 00 00 00 00 00 05 03 00 00 00 00 00 00 00
DM33 Emission Increasing AECD Active Time from Engine #2 (1): [
EI-AECD Number = 1: Timer 1 = 0 minutes; Timer 2 = 0 minutes
EI-AECD Number = 5: Timer 1 = 3 minutes; Timer 2 = 0 minutes
]

It appears that SA 61 also passes.
15:26:25.9751 Destination Specific DM6 Request to Exhaust Emission Controller (61)
15:26:25.9766 18EA3DF9 [3] CF FE 00 (TX)
15:26:25.9812 18FECF3D [8] 03 FF 00 00 00 00 FF FF
DM6 from Exhaust Emission Controller (61): MIL: off, RSL: off, AWL: off, PL: not supported, No DTCs
15:26:25.9822 Destination Specific DM12 Request to Exhaust Emission Controller (61)
15:26:25.9833 18EA3DF9 [3] D4 FE 00 (TX)
15:26:25.9911 18E8FF3D [8] 03 FF FF FF F9 D4 FE 00
Acknowledgment from Exhaust Emission Controller (61): Response: Busy, Group Function: 255, Address Acknowledged: 249, PGN Requested: 65236
15:26:26.1919 18EA3DF9 [3] D4 FE 00 (TX)
15:26:26.2016 18FED43D [8] 03 FF 00 00 00 00 FF FF
DM12 from Exhaust Emission Controller (61): MIL: off, RSL: off, AWL: off, PL: not supported, No DTCs
15:26:26.2022 Destination Specific DM23 Request to Exhaust Emission Controller (61)
15:26:26.2036 18EA3DF9 [3] B5 FD 00 (TX)
15:26:26.2157 18E8FF3D [8] 03 FF FF FF F9 B5 FD 00
Acknowledgment from Exhaust Emission Controller (61): Response: Busy, Group Function: 255, Address Acknowledged: 249, PGN Requested: 64949
15:26:26.4179 18EA3DF9 [3] B5 FD 00 (TX)
15:26:26.4216 18FDB53D [8] 03 FF 00 00 00 00 FF FF
DM23 from Exhaust Emission Controller (61): MIL: off, RSL: off, AWL: off, PL: not supported, No DTCs
15:26:26.4222 Destination Specific DM29 Request to Exhaust Emission Controller (61)
15:26:26.4236 18EA3DF9 [3] 00 9E 00 (TX)
15:26:26.4322 18E8FF3D [8] 03 FF FF FF F9 00 9E 00
Acknowledgment from Exhaust Emission Controller (61): Response: Busy, Group Function: 255, Address Acknowledged: 249, PGN Requested: 40448
15:26:26.6354 18EA3DF9 [3] 00 9E 00 (TX)
15:26:26.6411 189EF93D [8] 00 FF 00 00 00 FF FF FF
DM29 from Exhaust Emission Controller (61):
Emission-Related Pending DTC Count                               0
All Pending DTC Count                                not available
Emission-Related MIL-On DTC Count                                0
Emission-Related Previously MIL-On DTC Count                     0
Emission-Related Permanent DTC Count                             0
15:26:26.6422 Destination Specific DM5 Request to Exhaust Emission Controller (61)
15:26:26.6438 18EA3DF9 [3] CE FE 00 (TX)
15:26:26.6511 18FECE3D [8] 00 00 14 04 60 1C 60 1C
DM5 from Exhaust Emission Controller (61): OBD Compliance: HD OBD (20), Active Codes: 0, Previously Active Codes: 0
15:26:26.6522 Destination Specific DM25 Request to Exhaust Emission Controller (61)
15:26:26.6534 18EA3DF9 [3] B7 FD 00 (TX)
15:26:26.6616 18FDB73D [8] 00 00 00 00 00 FF FF FF
DM25 from Exhaust Emission Controller (61):
Freeze Frames: [
No Freeze Frames
]
15:26:26.6622 Destination Specific DM31 Request to Exhaust Emission Controller (61)
15:26:26.6636 18EA3DF9 [3] 00 A3 00 (TX)
15:26:26.6724 18E8FF3D [8] 01 FF FF FF F9 00 A3 00
Acknowledgment from Exhaust Emission Controller (61): Response: NACK, Group Function: 255, Address Acknowledged: 249, PGN Requested: 41728
15:26:26.6734 Destination Specific DM21 Request to Exhaust Emission Controller (61)
15:26:26.6744 18EA3DF9 [3] 00 C1 00 (TX)
15:26:26.6811 18C1F93D [8] 00 00 00 00 00 00 12 00
DM21 from Exhaust Emission Controller (61): [
Distance Traveled While MIL is Activated:     0 km (0 mi)
Time Run by Engine While MIL is Activated:    0 minutes
Distance Since DTCs Cleared:                  0 km (0 mi)
Time Since DTCs Cleared:                      18 minutes
]
15:26:26.6822 Destination Specific DM26 Request to Exhaust Emission Controller (61)
15:26:26.6838 18EA3DF9 [3] B8 FD 00 (TX)
15:26:26.6911 18FDB83D [8] 00 00 00 04 60 1C 60 1C
DM26 from Exhaust Emission Controller (61): Warm-ups: 0, Time Since Engine Start: 0 seconds
15:26:26.6921 Sending DM7 for DM30 to Exhaust Emission Controller (61) for SPN 1761
15:26:26.6939 18E33DF9 [8] F7 E1 06 1F FF FF FF FF (TX)
15:26:26.7311 18A4F93D [12] F7 E1 06 12 1E 00 18 9C FF FF B8 0B
DM30 from 61: SPN 1761 FMI 18 (SLOT 30) Result: Test Passed. Min: 7.5, Value: 99.9, Max: N/A %
15:26:26.7331 Destination Specific DM20 Request to Exhaust Emission Controller (61)
15:26:26.7344 18EA3DF9 [3] 00 C2 00 (TX)
15:26:26.7908 18C2F93D [32] 0A 00 01 00 CA 14 F8 00 00 00 00 B8 12 F8 00 00 01 00 C6 14 F8 00 00 01 00 F8 0B F8 00 00 01 00
DM20 from Exhaust Emission Controller (61):  [
Num'r /  Den'r
Ignition Cycles                                                    10
OBD Monitoring Conditions Encountered                               1
SPN 5322 AFT NMHC Converting Catalyst System Monitor       0 /      0
SPN 4792 AFT 1 SCR System                                  0 /      1
SPN 5318 AFT Exhaust Gas Sensor System Monitor             0 /      1
SPN 3064 AFT DPF System Monitor                            0 /      1
]
End Test 9.3 - DM22: Individual clear/reset of active and previously active DTC

I Suggest fixing #1091 first, and see if the unexpected test results problem was a side-effect of unexpected data discrepancies from the TID F6 support showing the manufacturer-defined SPs and the incorrect placement of the the MSBits, shown in #1091, leading to an interpretation of missing test results.
This reminded me of #1034, where there was a 1-bit difference, but appears to be unrelated.

I don't think #1091 applies in this case, we don't support any test results with SA 0x00. What is the logic behind how the tool checks for deleted data?

This failure was for SA 1, not SA 0. #1087 is related to SA 0

NA to confirm pass fail after #1091 is fixed.

With the correction of #1091, these outcomes were isolated from the the assumption that unexpected test results may explain them.
The strategy to check the ECUs of a distributed system individually is logically correct.
The configuration of SA 0 is somewhat unusual and may be contributing to the outcome.  It’s NACKs are consistent with Part 1 performance.

From Nathan Roner
This is still an issue even after https://github.com/Equipment-and-Tool-Institute/j1939-84/issues/1091 is fixed:
<IP_ADDRESS>.a - Checking for erased diagnostic information
11:56:17.2865 Destination Specific DM6 Request to Engine https://github.com/Equipment-and-Tool-Institute/j1939-84/pull/1 (0)
11:56:17.2885 18EA00F9 [3] CF FE 00 (TX)
11:56:17.2930 18E8FF00 [8] 01 FF FF FF F9 CF FE 00
Acknowledgment from Engine https://github.com/Equipment-and-Tool-Institute/j1939-84/pull/1 (0): Response: NACK, Group Function: 255, Address Acknowledged: 249, PGN Requested: 65231
11:56:17.2955 Destination Specific DM12 Request to Engine https://github.com/Equipment-and-Tool-Institute/j1939-84/pull/1 (0)
11:56:17.2980 18EA00F9 [3] D4 FE 00 (TX)
11:56:17.3030 18E8FF00 [8] 01 FF FF FF F9 D4 FE 00
Acknowledgment from Engine https://github.com/Equipment-and-Tool-Institute/j1939-84/pull/1 (0): Response: NACK, Group Function: 255, Address Acknowledged: 249, PGN Requested: 65236
11:56:17.3045 Destination Specific DM23 Request to Engine https://github.com/Equipment-and-Tool-Institute/j1939-84/pull/1 (0)
11:56:17.3080 18EA00F9 [3] B5 FD 00 (TX)
11:56:17.3135 18E8FF00 [8] 01 FF FF FF F9 B5 FD 00
Acknowledgment from Engine https://github.com/Equipment-and-Tool-Institute/j1939-84/pull/1 (0): Response: NACK, Group Function: 255, Address Acknowledged: 249, PGN Requested: 64949
11:56:17.3145 Destination Specific DM29 Request to Engine https://github.com/Equipment-and-Tool-Institute/j1939-84/pull/1 (0)
11:56:17.3170 18EA00F9 [3] 00 9E 00 (TX)
11:56:17.3225 18E8FF00 [8] 01 FF FF FF F9 00 9E 00
Acknowledgment from Engine https://github.com/Equipment-and-Tool-Institute/j1939-84/pull/1 (0): Response: NACK, Group Function: 255, Address Acknowledged: 249, PGN Requested: 40448
11:56:17.3245 Destination Specific DM5 Request to Engine https://github.com/Equipment-and-Tool-Institute/j1939-84/pull/1 (0)
11:56:17.3270 18EA00F9 [3] CE FE 00 (TX)
11:56:17.3330 18FECE00 [8] [00 00 14 04 00 00 00](tel:00 00 14 04 00 00 00) 00
DM5 from Engine https://github.com/Equipment-and-Tool-Institute/j1939-84/pull/1 (0): OBD Compliance: HD OBD (20), Active Codes: 0, Previously Active Codes: 0
Continuously Monitored System Support/Status:
Comprehensive component supported, complete
Fuel System not supported, complete
Misfire not supported, complete
Non-continuously Monitored System Support/Status:
A/C system refrigerant not supported, complete
Boost pressure control sys not supported, complete
Catalyst not supported, complete
Cold start aid system not supported, complete
Diesel Particulate Filter not supported, complete
EGR/VVT system not supported, complete
Evaporative system not supported, complete
Exhaust Gas Sensor not supported, complete
Exhaust Gas Sensor heater not supported, complete
Heated catalyst not supported, complete
NMHC converting catalyst not supported, complete
NOx catalyst/adsorber not supported, complete
Secondary air system not supported, complete
11:56:17.3385 Destination Specific DM25 Request to Engine https://github.com/Equipment-and-Tool-Institute/j1939-84/pull/1 (0)
11:56:17.3410 18EA00F9 [3] B7 FD 00 (TX)
11:56:17.3435 18E8FF00 [8] 01 FF FF FF F9 B7 FD 00
Acknowledgment from Engine https://github.com/Equipment-and-Tool-Institute/j1939-84/pull/1 (0): Response: NACK, Group Function: 255, Address Acknowledged: 249, PGN Requested: 64951
11:56:17.3445 Destination Specific DM31 Request to Engine https://github.com/Equipment-and-Tool-Institute/j1939-84/pull/1 (0)
11:56:17.3480 18EA00F9 [3] 00 A3 00 (TX)
11:56:17.3530 18E8FF00 [8] 01 FF FF FF F9 00 A3 00
Acknowledgment from Engine https://github.com/Equipment-and-Tool-Institute/j1939-84/pull/1 (0): Response: NACK, Group Function: 255, Address Acknowledged: 249, PGN Requested: 41728
11:56:17.3555 Destination Specific DM21 Request to Engine https://github.com/Equipment-and-Tool-Institute/j1939-84/pull/1 (0)
11:56:17.3590 18EA00F9 [3] 00 C1 00 (TX)
11:56:17.3635 18E8FF00 [8] 01 FF FF FF F9 00 C1 00
Acknowledgment from Engine https://github.com/Equipment-and-Tool-Institute/j1939-84/pull/1 (0): Response: NACK, Group Function: 255, Address Acknowledged: 249, PGN Requested: 49408
11:56:17.3655 Destination Specific DM26 Request to Engine https://github.com/Equipment-and-Tool-Institute/j1939-84/pull/1 (0)
11:56:17.3690 18EA00F9 [3] B8 FD 00 (TX)
11:56:17.3735 18E8FF00 [8] 01 FF FF FF F9 B8 FD 00
Acknowledgment from Engine https://github.com/Equipment-and-Tool-Institute/j1939-84/pull/1 (0): Response: NACK, Group Function: 255, Address Acknowledged: 249, PGN Requested: 64952
FAIL: <IP_ADDRESS>.a - Engine https://github.com/Equipment-and-Tool-Institute/j1939-84/pull/1 (0) erased Test Results data

Eric to review with Nathan using a 3.1.3 report 7/8

Review versus #1130.

Nathan, is this still an issue?
How about we refresh using data from 3.1.14 if it is?
Above I observed.
11:56:17.3245 Destination Specific DM5 Request to Engine
11:56:17.3270 18EA00F9 [3] CE FE 00 (TX)
11:56:17.3330 18FECE00 [8] 00 00 14 04 00 00 00 00
DM5 from Engine OBD Compliance: HD OBD (20), Active Codes: 0, Previously Active Codes: 0
vs.
The tool falsely flags that our controller erased DM5 data.
17:56:46.2271 Destination Specific DM5 Request to Engine https://github.com/Equipment-and-Tool-Institute/j1939-84/pull/2 (1)
17:56:46.2316 18EA01F9 [3] CE FE 00 (TX)
17:56:46.2446 18FECE01 [8] [00 00 14 37](tel:00 00 14 37) E0 02 E0 02
DM5 from Engine https://github.com/Equipment-and-Tool-Institute/j1939-84/pull/2 (1): OBD Compliance: HD OBD (20), Active Codes: 0, Previously Active Codes: 0
FAIL: <IP_ADDRESS>.a - Engine https://github.com/Equipment-and-Tool-Institute/j1939-84/pull/2 (1) erased DM5 data
DM5 from earlier in part 4:
17:56:31.7991 18FECE01 [8] [00 00 14 37](tel:00 00 14 37) E0 02 E0 02
DM5 from Engine https://github.com/Equipment-and-Tool-Institute/j1939-84/pull/2 (1): OBD Compliance: HD OBD (20), Active Codes: 0, Previously Active Codes: 0

@naroner will check with 3.1.15 week of 3/20

@ericthomasswenson This is fixed in 3.1.19


role checking Proof of Work

syntax of json file is as the following
{"Moderator":[922947967260971089]}

feel free to deny the PR, this is just an example

Not necessarily a bad pr, but I'm most likely going to do this differently
Still, thank you for the ideas on the Discord and for making me look into better defining permission checks


FullItemAllOfFields TypeEnum.Totp points to incorrect field type

Your environment

SDK Version: 1.0.4

Connect Server Version: 1.5.0

OS: macOS 15.7

Node Version: 12.22.7
What happened?

Trying to create an item with an OTP field causes an error. The Connect server rejects the request with a validation error.
What did you expect to happen?

The item with an OTP field is created successfully.
Steps to reproduce

Create an item with the following config:

const item = new ItemBuilder()
    .setCategory(CategoryEnum.Login)
    .addField({
        type: TypeEnum.Totp,
        label: "My OTP Field",
        value: "otpauth://totp/Example:steve@example.com?secret=JBSWY3DPEHPK3PXP&issuer=Example",
    })
    .build();

/** setup client, send item to server **/
const op = OnePasswordConnect({
	serverURL: "http://localhost:8080",
	token: "my-token",
	keepAlive: true,
});
const createdItem = await op.createItem(my_vault_id_here, item);

You should receive a server error because the TypeEnum.Totp points to TOTP which is not a valid field type.
Notes & Logs

This is related to https://github.com/1Password/connect/pull/26

Closed by #41


DEP_WEBPACK_COMPILATION_ASSETS

$ cross-env NODE_ENV=development webpack --config ./webpack/chrome.js
[...]
rebuilding manifest.json
(node:17128) [DEP_WEBPACK_COMPILATION_ASSETS] DeprecationWarning: Compilation.assets will be frozen in future, all modifications are deprecated.
BREAKING CHANGE: No more changes should happen to Compilation.assets after sealing the Compilation.
        Do changes to assets earlier, e. g. in Compilation.hooks.processAssets.
        Make sure to select an appropriate stage from Compilation.PROCESS_ASSETS_STAGE_*.
(Use `node --trace-deprecation ...` to show where the warning was created)

Documenting the full error with --trade-deprecation
[04:16 PM] ~/code/videospeed-refactoring (master) $ node --trace-deprecation node_modules/webpack/bin/webpack --config ./webpack/chrome.js
Debugger listening on ws://<IP_ADDRESS>:19731/72888386-ac1b-47dd-9350-1a5d4486485d
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
WARNING: Development build only, not for use in prod

Rebuilding manifest.json
(node:9116) [DEP_WEBPACK_COMPILATION_ASSETS] DeprecationWarning: Compilation.assets will be frozen in future, all modifications are deprecated.
BREAKING CHANGE: No more changes should happen to Compilation.assets after sealing the Compilation.
        Do changes to assets earlier, e. g. in Compilation.hooks.processAssets.
        Make sure to select an appropriate stage from Compilation.PROCESS_ASSETS_STAGE_*.
    at emit (C:\Users\chadb\code\videospeed-refactoring\node_modules\generate-json-from-js-webpack-plugin\index.js:52:41)
    at Hook.eval [as callAsync] (eval at create (C:\Users\chadb\code\videospeed-refactoring\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:7:1)
    at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (C:\Users\chadb\code\videospeed-refactoring\node_modules\tapable\lib\Hook.js:18:14)
    at Compiler.emitAssets (C:\Users\chadb\code\videospeed-refactoring\node_modules\webpack\lib\Compiler.js:891:19)
    at C:\Users\chadb\code\videospeed-refactoring\node_modules\webpack\lib\Compiler.js:466:10
    at processTicksAndRejections (node:internal/process/task_queues:77:11)
    at runNextTicks (node:internal/process/task_queues:64:3)
    at process.processImmediate (node:internal/timers:442:9)