auto-imports (import suggestions) randomly stopped working

Type: Bug
A little while ago (like over a week now), I was working as I always do, and all of the auto-import suggestions for typescript just stopped working completely. I hadn't updated anything manually (my os, vscode, extensions, node modules, etc). It is possible something auto-updated somewhere behind the scenes, but I haven't been able to track it down.
Essentially no auto-imports work at all in my project anymore. I can't import from relative pathed files, workspace files, or node modules. All typescript imports, once imported work fine and are recognized, but any of the "quick fix" suggestions just don't work at all, both as I type or hovering over a missing reference. The quick fix popup does show, but the only option is my tabnine extension.
What is strange is the imports have worked once since they stopped. I did nothing out of the ordinary and they just randomly started working again. But then as quickly as they appeared, they disappeared.
I've tried all of the following:

changing ts versions
changing between vscode and project ts references
changing my pnpm version
turning on and off every one of my extensions
changing memory and storage size limits on wsl
trying to initialize the project in various ways (docker first, complete rebuilds, etc)
nearly every possible setting related to ts and tsserver in the vscode settings
nearly every possible intellisense setting I could find that might be related
restarting vscode and ts server in various ways
changing any settings related to docker, workspaces, or anything else that might affect my ts path lookups

The only other piece of information I have is this error in the ts logs, but I've tried tracking it down, even manually modifying the ts server code and logging things out for a couple hours, with no obvious things that stand out on why it is failing. This error appears when I try to hover over a known missing reference to have it show the imports, but then it just doesn't show them, presumably due to this error (some path parts redacted for privacy reasons).
Info 4708 [11:56:52.468] request:
    {
      "seq": 19,
      "type": "request",
      "command": "quickinfo",
      "arguments": {
        "file": "/<projectPath>/apps/main-app/src/client/components/MyComponent.tsx",,
        "line": 42,
        "offset": 22
      }
    }
Info 4712 [11:56:52.468] request:
    {
      "seq": 20,
      "type": "request",
      "command": "getCodeFixes",
      "arguments": {
        "file": "/<projectPath>/apps/main-app/src/client/components/MyComponent.tsx",
        "startLine": 42,
        "startOffset": 18,
        "endLine": 42,
        "endOffset": 25,
        "errorCodes": [
          2304
        ]
      }
    }
Err 4713  [11:56:52.550] Exception on executing command {
  "seq": 20,
  "type": "request",
  "command": "getCodeFixes",
  "arguments": {
    "file": "/<projectPath>/apps/main-app/src/client/components/MyComponent.tsx",
    "startLine": 42,
    "startOffset": 18,
    "endLine": 42,
    "endOffset": 25,
    "errorCodes": [
      2304
    ],
    "startPosition": 1103,
    "endPosition": 1110
  }
}:

    Debug Failure.

    Error: Debug Failure.
        at Object.getImmediateAliasedSymbol (/<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:74339:22)
        at getDefaultExportInfoWorker (/<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:135913:29)
        at getDefaultExportInfoWorker (/<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:135915:14)
        at getDefaultLikeExportInfo (/<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:135891:16)
        at /<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:152437:25
        at /<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:135751:119
        at forEachExternalModule (/<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:135812:7)
        at forEachExternalModuleToImportFrom (/<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:135751:3)
        at getExportInfos (/<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:152433:3)
        at /<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:152366:24
        at flatMap (/<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:2609:17)
        at getFixesInfoForNonUMDImport (/<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:152360:10)
        at getFixInfos (/<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:152206:12)
        at Object.getCodeActions (/<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:151577:18)
        at /<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:148588:46
        at flatMap (/<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:2609:17)
        at Object.getFixes (/<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:148588:10)
        at /<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:146859:33
        at flatMap (/<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:2609:17)
        at Object.getCodeFixesAtPosition (/<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:146857:12)
        at IpcIOSession.getCodeFixes (/<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:187265:50)
        at getCodeFixes (/<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:185371:43)
        at /<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:187569:69
        at IpcIOSession.executeWithRequestId (/<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:187561:14)
        at IpcIOSession.executeCommand (/<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:187569:29)
        at IpcIOSession.onMessage (/<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:187611:51)
        at process.<anonymous> (/<projectPath>/node_modules/.pnpm/typescript@5.4.5/node_modules/typescript/lib/tsserver.js:189220:14)
        at process.emit (node:events:518:28)
        at emit (node:internal/child_process:951:14)
        at process.processTicksAndRejections (node:internal/process/task_queues:83:21)

From what I can conclude, this seems like either a timing issue withing vscode starting things up, or some internal vscode or extension thing somewhere broke behind the scenes. I'm on a wsl docker setup, so there is a lot of linking going on behind the scenes, but given I hadn't changed anything when this started happening, I'm at a complete loss on what to even look for further at this point.
Oh, and unfortunately, I haven't been able to reproduce this on any other machine, so I'm a bit stuck on that front. I'm happy to try modifying any settings suggested, I just have no idea what else to look for at this point.
VS Code version: Code 1.90.0 (89de5a8d4d6205e5b11647eb6a74844ca23d2573, 2024-06-04T19:33:54.889Z)
OS version: Windows_NT x64 10.0.22635
Modes:
Remote OS version: Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 2808)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
31.89GB (6.29GB free)

Process Argv
--crash-reporter-id 10d747f9-1beb-40be-859f-a1379ddf2d04

Screen Reader
no

VM
0%

Item
Value

Remote
WSL: Ubuntu

OS
Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

CPUs
Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 0)

Memory (System)
17.57GB (11.70GB free)

VM
0%

Extensions (32)

Extension
Author (truncated)
Version

remote-containers
ms-
0.369.0

remote-ssh
ms-
0.110.1

remote-ssh-edit
ms-
0.86.0

remote-wsl
ms-
0.88.2

vscode-remote-extensionpack
ms-
0.25.0

atom-keybindings
ms-
3.3.0

remote-explorer
ms-
0.4.3

remote-server
ms-
1.5.1

reopenclosedtab
uyi
1.1.0

material-theme
zhu
3.17.2

vscode-zipfs
arc
3.0.0

vscode-tailwindcss
bra
0.10.5

vscode-better-align
cho
1.4.2

npm-intellisense
chr
1.4.5

path-intellisense
chr
2.9.0

vscode-css-modules
cli
0.5.1

vscode-eslint
dba
2.4.4

githistory
don
0.6.20

gitlens
eam
15.1.0

vscode-search-open-all-results
fab
2.0.2

vscode-pull-request-github
Git
0.88.1

vscode-duplicate
mrm
1.2.1

vscode-docker
ms-
1.29.1

atom-keybindings
ms-
3.3.0

vsliveshare
ms-
1.0.5918

color-highlight
nau
2.8.0

gremlins
nho
0.26.0

vscode-stylelint
sty
1.4.0

tabnine-vscode
Tab
3.108.0

reopenclosedtab
uyi
1.1.0

vscode-fold-level
vik
0.0.14

vscode-svg-previewer
vit
0.7.0

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
vscaac:30438847
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
9b8hh234:30694863
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
jchc7451:31067544
chatpanelc:31048052
dsvsc021:30996838
9c06g630:31013171
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
pythonprt:31056678
dwnewjupyter:31046869
26j00206:31048877

It'll be very quick for us to fix this once we have a project that can repro it, but we really do need a reproing project. Nothing else is particularly useful (unless you're able to attach a debugger and figure out why that assert is triggering)

It'll be very quick for us to fix this once we have a project that can repro it, but we really do need a reproing project. Nothing else is particularly useful (unless you're able to attach a debugger and figure out why that assert is triggering)

@RyanCavanaugh I haven't been able to reproduce in another sample project and unfortunately I cannot give access to this project. However, after spending probably way too much time on it, I am able to debug the tsserver and am able to breakpoint at the Debug.fail() that is being thrown. In the attached log above, the stack trace shows pretty well where the fail is being thrown:
function getImmediateAliasedSymbol(symbol) {
    Debug.assert((symbol.flags & 2097152 /* Alias */) !== 0, "Should only get Alias here.");
    const links = getSymbolLinks(symbol);
    if (!links.immediateTarget) {
      const node = getDeclarationOfAliasSymbol(symbol);
      if (!node) return Debug.fail(); ////////////// dying right here
      links.immediateTarget = getTargetOfAliasDeclaration(
        node,
        /*dontRecursivelyResolve*/
        true
      );
    }
    return links.immediateTarget;
  }

Here's a json output gist from when that fail happens for the "symbol" variable: https://gist.github.com/runfaj/08d7cdd31d97cdbdbd8425f643ae02bf
It appears that getDeclarationOfAliasSymbol is looking for symbol.declarations, but the symbol provided is undefined for declarations. I can see a parent symbol is in a completely unrelated file, so I'm not exactly sure what the actual AST going on here. If I had to guess, it might appear (just looking at that gist link above), that a "default" export is failing for a json file being included in one of the dist outputs in a dependent package. I'm not quite certain though. If that is the case, why tsserver is scanning a json file and trying to parse it like this also seems like a potential bug. I could be completely off though.

Okay, after much debugging, It appears that we have some translation json files. However, they get imported like so:
import * as dateRangePresets from<EMAIL_ADDRESS>assert { type: 'json' };

export default dateRangePresets.default;

It appears that the tsserver can't properly reconcile these and it breaks the quick fix imports. I was able to confirm by removing all these and the quick fix imports started appearing properly again. I may be able to find some alternative way to deal with this, but it would be something to address in the tsserver somehow.


Add handle_ties arg to in_top_k Op to deal with ties.(#10767)

#10767
Add handle_ties argument to in_top_k Op to make the Op more clear.

Can one of the admins verify this patch?

@tensorflow-jenkins test this please

@nolanliou FYI: Removing the stable sort from top_k was a mistake. We are in the process of restoring it. Perhaps this change becomes unnecessary then?

The change is about in_top_k, Is there a connection between top_k and in_top_k?

@nolanliou Ah, nevermind :-)  Can you please rebase?

Sorry, I screw it up, I'll close this and reopen a PR.


fix: no-overlap layout algorithm

Closes #2240
We have 3 cases to handle:

Current effect

Effect after fix

I am testing this, and doesn't work. Could you provide thecode that your used for this test ?

@blugnomeXD just reproduce the issue from #2240. Please remember that this code is related to no-overlap algorithm.

@lukbak  Thanks for your answer. Yes i am using no-overlap because i have the same issue that you reported.  Is enought to pass the prop dayLayoutAlgorithm='no-overlap' or i need something else?
Thanks

Hello @cutterbl. I would like to ask when we can expect this change? Do you have any comments?

@cutterbl @dhruvgoel92 Please take a look.


Question about hla_referenence_dna.fasta

Hello,
I was looking through the given fasta files under data directory and noticed that some of the sequences provided in there are combinations of coding sequence and non-coding sequence.
What puzzles me is that some of them have different first 2 digits. (ex. HLA07296_HLA00097 HLA-A_33:53 (introns from HLA-A_31:01:02)). And it seems like the list of combinations of exon and intron that share first two digits are not exhaustive.
Is there a logic to how these alleles are combined? (And if I were to update this fasta to more recent alleles from the HLA db, what logic should I use to combine the alleles?)
Thanks.

@Atalasia,
as you might have noticed HLA00097 translates to HLA-A31:01:02 (just search for it in the file).
This just means that the first allele (HLA07296) had no intron sequence available and had to be imputed somehow.
Citing the paper:

We impute the missing sequence data by replacing it with its closest neighbor with respect to sequence similarity from among the complete allele sequences

So rather than you updating the database, it is probably easier if there would be an update to OptiType (they should also have tested code for that). @andras86, what do you think?
I would also be very interested if that improves performance.

Thank you @messersc, this is exactly what happens, we lift over intron sequences from the most similar alleles. Updating them yourself would be difficult as there's a lot of sanity checking and some manual work in this process, but we're making a more-or-less automated pipeline to do it. We won't update the database for the current OptiType version, but the coming-soon OT2 (with Class II typing) will have the most recent one and we'll keep updating it.

@andras86 Do let us know when the OT2 will be out and I'm definitely looking forward to it.

@andras86 Hello. I was just wondering how the automated-pipeline for updating the OptiType database is coming along? I'm interested in using the updated HLA alleles with OptiType, but would rather not impute the introns on my own, if a validated procedure already exists. Is any of your code related to this released? Thank you.

@andras86 Hi. I also have the same request for using the updated HLA reference database since I realized that there are two things for me impossible to do by myself: 1. build genomic sequences for truncated alleles from intron 1 to intron 3 by imputing most similar intron from other allele. 2. how to format "alleles.h5" file. Looking forward to the updating.
Thank you.

@andras86 Looking forward to OT2. Thanks.

@AlfredShawn alleles.h5is a HDF5 file, therefore you can explore it using whatever packages such that, e.g., python ones: h5py or Pandas.
All the best

@zimoun  could you please  provide   the automated-pipeline for updating the OptiType database ?  I also wanna use the latest HLA database from IGMT.

I would appreciate any instruction for both hla_referenence_dna.fasta and hla_referenence_rna.fasta update! Can anyone provide it, please?

@lidd77  @serge2016 My comment was more than 2 years ago. :-)
Now I do not use OptiType anymore. Therefore, I cannot provide nothing.
Last, note that my comment did not suggest any "automated-pipeline for updating the OptiType database" but only a way to explore alleles.h5 to format it.
All the best and Godspeed!

@zimoun and what do you use now instead of OptiType?


gist:contributesTo is too similar to gist:produces

I think gist:contributesTo and gist:produces are too similar to be siblings (at the root of the obj prop tree).
I propose that we:

delete gist:contributesTo
create gist:partiallyProduces
make  gist:partiallyProduces a sub prop of gist:produces
give gist:produces the alt label "contributes to"

I read that label as "contributes to the existence of" which is why I think gist:partiallyProduces can replace gist:contributesTo

Some of the parts of a system partially produce the goal/function of the whole system.
The system partially produces the goal/function of the whole system.
The system + its environment (fully) produces the goal/function of the whole system.

Maybe we also need gist:fullyProduces as a sub prop of gist:partiallyProduces.

In my mind, "The parts of a system contribute to the goal/ function of the whole system" is not the same as "produces." An engine contributes to the goal/function of a car, but it does not produce the car.

An engine contributes to the goal/function of a car,

Agreed.

but [an engine] does not produce the car.

Of course, but the goal/function of a car is not the car.

... so we still have a use for contributesTo. I don't think we want to have to materialize the goal/function of a car just to state that an engine contributes to the functioning of a car.

Isn't the engine gist:isPartOf the car?

That too, but it's more than that.

Some of the ideas posed here make sense, ontologically. To add something to gist requirements a higher bar. There needs to be use cases that are likely to arise often in a variety of enterprises.
For example, a property like fullyProduces or partiallyProduces could be useful in a special situation. Less likely to have widespread application.

I think the current thing that needs attention is the fact it isn't clear enough when to use gist:contributesTo and not gist:produces (and vice versa).

I propose that we:
* create gist:partiallyProduces
* make  gist:partiallyProduces a sub prop of gist:produces
Some of the parts of a system partially produce the goal/function of the whole system. The system partially produces the goal/function of the whole system. The system + its environment (fully) produces the goal/function of the whole system.

This suggestion seems to create less useful information for a knowledge graph. With gist:partiallyProduces there is no indication of what contribution the subject provides to the outcome. Maybe it would be better to subdivide what is being produced so that you can say with more clarity and more information, what it actually being produced by the subject.

On many occasions I have used a property that i called 'facilitates' which is close in meaning to 'contributes to'.  Subgoals facilitate goals, subfunctions facilitate functions. People facilitate events (not in the sense of overseeing/running).   Technologies and techniques facilitate the achievement of goals. E.g. consistent naming conventions facilitate ontology clarity.

@Jamie-SA

Maybe it would be better to subdivide what is being produced so that you can say with more clarity and more information, what it actually being produced by the subject.

When that is possible with the information/data that is available, I agree. But often data don't have that much clarity.
e.g. data like this is common
{"event name" : "Sally's Wedding" ,
  "event staff: ["Bob","Fred","Alice","Wanda"],
  "sub events": ["Rehearsal Dinner", "Ceremony","Reception"]
}

We know the staff members each partially produce the services of the event but we don't know exactly who did what.

We know the staff members (at least) partially produce the services of the event but we don't know exactly who did what.

Sounds like gist:contributesTo, not gist:produces. But I'm not sure I'd model it that way if I wanted to know who the gist:hasParticipant were to the event of producing the event of the wedding.

If commit a change to gist, I am contributing to gist, but it's a stretch to say I produced gist; gist existed long before my contributions. Unless you want to split hairs and say I (along with others) produced the exact state of gist as it exists after my commit. I think that's too fine a point.

If I commit a change to gist, I am contributing to gist, but it's a stretch to say I produced gist

I think it is fair to say that your commit partially produces gist.

Basically I think "contributes to" is really "partially produces."
Making a contribution is partially/fully producing something. It is confusing to keep them both around.

Basically I think "contributes to" is really "partially produces." Making a contribution is partially/fully producing something. It is confusing to keep them both around.

Sounds like you are saying that "partially produces" is "contributes to". So why bother changing it? Just because you have a particular vocabulary preference isn't that compelling of a reason to me if you aren't going to change any definitions.
I don't find having both "contributes to" and "produces" is confusing.
I still think there are use cases where "contributes to" is more appropriate that "partially produces". If I let a high school group use my garage to build a float, did I partially produce the float? I don't think so. But I did contribute to the project. If I donate money to an local independent film project, did I partially produce the film? I don't think so. But I did contribute to the project. Etc.

Just because you have a particular vocabulary preference isn't that compelling of a reason to me if you aren't going to change any definitions.

I don't have a personal vocabulary preference but I do have a goal that gist should nudge users to the appropriate obj props. It is hard for gist to do that if it has very similar obj props as siblings the root level.
It's not that I especially like "partial production" but I think gist should build upon its primitives when possible, right? Since gist:produces already exists an option is to build upon it by making a sub prop of it which we could call gist:partiallyProduces (in the spirit of building upon the primitives).

If I let a high school group use my garage to build a float, did I partially produce the float?

The gist:Task the group performed in your garage gist:produces the float.

If I donate money to an local independent film project, did I partially produce the film?

The gist:Event of you putting money somewhere gist:partiallyProduces the film.
Maybe the thing to do here is to delete gist:contributesTo and just elaborate on the definition of gist:produces so that it includes full production and partial production.
before:
gist:produces
	a owl:ObjectProperty ;
	skos:definition "The subject creates the object."^^xsd:string ;
	skos:example "A task produces a deliverable."^^xsd:string ;
	skos:prefLabel "produces"^^xsd:string ;
	.

after:
gist:produces
	a owl:ObjectProperty ;
	skos:definition "The subject creates the object but the subject need not be fully responsible for the creation."^^xsd:string ;
	skos:example "A task produces a deliverable; An event partially produces an artifact."^^xsd:string ;
	skos:prefLabel "produces"^^xsd:string ;
	skos:altLabel "partially produces"^^xsd:string ;
        skos:altLabel "contributes to"^^xsd:string ;
	.

Thinking about this more... I see two independent dimensions for produces/contributesTo...
Did the thing in the object position exist already?

If a gist:Function is in the object position then the answer can be yes.
If a gist:Building is in the object position then the answer can be no.

Is the subject fully responsibility for the production of the object?

If a gist:Task is in the subject position then the answer can be yes.
If a gist:Artifacts is in the subject position then the answer can be no (sometimes it takes multiple artifacts to produce something).

Maybe the thing to do here is to delete gist:contributesTo and just elaborate on the definition of gist:produces so that it includes full responsibility production and partial responsibility production.

I disagree. I think Jamies examples make a compelling case for different uses.

I'm with Jamie and Michael on this one.

I think Jamies examples make a compelling case for different uses.

Jamie's example tried to directly connect (with 1 edge) himself to the production of a float and the production of a film. It turned out that the excessively causal gist:contributesTo allowed him to do that. gist isn't doing its job if you can connect an arbitrary pair of things with a single edge.
gist:contributesTo offers so little constraint that you could use it to connect pairs of things for significantly different reasons. Why don't we attempt to formalize its skos:definition: "The parts of a system contribute to the goal/ function of the whole system"?
If we do then a gist:Person likely can't appear in the subject position.

gist:contributesTo offers so little constraint that you could use it to connect pairs of things for significantly different reasons. Why don't we attempt to formalize its skos:definition: "The parts of a system contribute to the goal/ function of the whole system"?
If we do then a gist:Person likely can't appear in the subject position.

Then it becomes awkward to say that Rebecca contributes to the development of gist. People contribute to all kinds of things.

People contribute to all kinds of things.

Sure, but gist can't let each person be directly connected to the thing they contribute to and at the same time expect ontology users to arrive at consistent representations.
I think this is close to how I would say that Rebecca contributes to gist:
:task0 gist:hasParticipant :Rebecca .
:task0 a gist:Task .
:task0 gist:produces :commit0 .
:commit0 gist:goesToPlace :repository0 .
:repository0 skos:prefLabel "Github repository for gist" .
:repository0 gist:hasAddress :addy0 .
:addy0 gist:containedText "git@github.com:semanticarts/gist.git" .

If someone wants to directly connect Rebecca to repository then they could define an obj prop:
ex:contributesTo  owl:propertyChainAxiom  ( [ owl:inverseOf gist:hasParticipant ]  gist:produces gist:goesToPlace ) .

This way the direct connection is just a name for a more principled connection.

This way the "direct" connection is just a name for a more principled connection.

There is much truth in what you say. The challenge is to decide when all the details of the more principled connection are ever going to matter in practice.  Our usual approach is Einsteinien: as simple as possble, but no simpler.  Start simple. If all the stuff that makes a more principled connection turns out to be necessary to achieve specific practical goals, then it can be extended. The original simple approach can then be formally defined as you say.

Our usual approach is Einsteinien: as simple as possble, but no simpler. Start simple.

I agree with that. I just think the gist primitives are what decides how much granularity is needed. Although you can always name things built from gist primitives for more terse looking representations.
Once it is decided that gist is going to be used and a domain of interest is selected then the resultant RDF should just be a consequence of gist and the domain of interest. If too much priority is given to "what are the known uses of the data" then we don't get the atomicity of representation that yields serendipity, the ability to speculate based on analogy, the harmonization of different domains, etc.
If too much priority is given to "what are the known uses of the data" then we get application-centric data dressed in RDF.

Designing a usable ontology involves a balance between top-down and bottom-up approaches. BFO takes a top-down approach, and is an ontology that no one actually uses (even if they claim to) because it is too abstract and doesn't help model anything in the real world.
Translating existing data directly to an OWL data model is a fully bottom-up approach. You get an ontology but not one that can provide new insights into existing data or connect it to other data. Library of Congress's BIBFRAME is such an ontology: it is almost a literal translation of MARC into RDF.
gist aims to strike a balance. It is not attempting to find the ontological underpinnings of the universe, or even of all of human behavior. It provides enough abstraction to unify unruly data under a common data model that is, as Michael says, as simple as required but no simpler (roughly Occam's razor, which was postulated about 700  years before Einstein). We do not look at common use cases because we are enslaved by existing data, but because we want to provide an ontology that is both practically useful and conceptually sound.

Hi Rebecca - I love your positioning of gist in that comment :) !
I've bookmarked your comment for my own personal future reference, but I'd recommend weaving your comment back into the current gist web page (i.e., what's on the gist web page already is good, but your expansion here really gives it weight - in particular your references to past attempts at the extremes of the Top-Down and Bottom-Up approaches, thereby beautifully positioning gist as a 'practical middle-ground').

Thanks, Pat, I'm glad you found this helpful. BTW, we are about to post a rewritten version of the web page, though in terms of the core concepts above it's mostly unchanged.

Gist has a small number of top level concepts from which everything else derives

Agreed.
And I am proposing that a contributesTo predicate can be derived. Something like:

ex:contributesTo  owl:propertyChainAxiom  ( [ owl:inverseOf gist:hasParticipant ]  gist:produces gist:goesToPlace ) .

That makes it more likely that different users of gist will arrive at consistent representations of the same situation.

@rjyounes @jamie @justin2004
SUMMARY: This was a long conversation bringing up a variety of interesting points.

there are a number of interesting relationships between contributing to something and producing things.
we could tease them all out, but that is out of scope for gist
excellent examples making clear that contributesTo is significantlhy different from produces are provided by Jamie below:

If I let a high school group use my garage to build a float, did I partially produce the float? I don't think so. But I did contribute to the project. If I donate money to an local independent film project, did I partially produce the film? I don't think so. But I did contribute to the project.

PROPOSAL: close this issue and leave things as they are.
See also #765

Agreed - closing.


Border radius not working on android. Working on iOs

I am trying to show local video stream to the user. I have applied the border radius to the local video stream. On iOs, I can see it working fine. But on android, it doesn't get applied.

My JSX object is:
<AgoraView style={{                         width: width / 3, //width is obtained from device width                         height: width / 2,                         backgroundColor: '#ddd',                         position: 'absolute',                         top: 50,                         right: 20,                         borderRadius: 15,                         overflow: 'hidden',                         zIndex: 3                     }}                         zOrderMediaOverlay={true}                         showLocalVideo />
if I set zOrderMediaOverlay false, then on android, the local video stream does not appear at all.
Kindly fix this issue

We use SurfaceView on the Android platform, so it does not support radius.
We will upgrade it before Q3, it will support TextureView.

add texture view at  react-native-agora@beta


Drop unused type traits

Rational: The traits have been unused for a long time and I don't anticipate we will change our mind anytime soon.

Besides not being used, is_expandable and has_centroid functionality can easily be implemented using the detection idiom.
is_complete had other issues that led to our using another mechanism to detect whether the access traits were specialized. https://github.com/arborx/ArborX/blob/b020ca71f3994d9bc8c0c3b151dceb41114061e3/src/details/ArborX_AccessTraits.hpp#L35

The CUDA-10.2-NVCC failure was fetnat03 running out of space

The CUDA-10.2-NVCC failure was fetnat03 running out of space


timer needs to be reset when 'closeOnConfirm' is set to false

If the alert has a timer set (say n seconds), and 'closeOnConfirm' is set to false, then the second window that appears (after confirm) will get closed if 'n' seconds elapse. This time includes the time spent in deciding confirm or no.
The timer needs to be reset in between for correct/desirable operation.

I could not replicate this issue.
Below is a fiddle, exactly as you described (I believe), and the second window won't get closed.
https://jsfiddle.net/crabbly/wmydys9L/
Make sure you are using the latest version of the library.

thank you @crabbly for jsfiddle!


ziti-router: introduced health checks fail

Hi,
I tried to upgrade to the latest helm charts. For my router the deployment never became active and was restarting. After some investigation I noticed the health checks introduced in this commit https://github.com/openziti/helm-charts/commit/3c2afc53c49f8a3c7d24ceb6d199c88d2d9474aa fialed to succeed. After manually removing them from the deplyment it became active and everything worked as expected.
I tried to execute them manually in the pod and it seems ziti agent stats fails to find the ziti router process:
[ziggy@core-router-858f76f8fb-fvtqm ~]$ ziti agent stats
Error: no processes found matching filter, use 'ziti agent list' to list candidates
Usage:
  ziti agent stats [flags]

Flags:
  -a, --app-alias string      Alias of host application to talk to (specified in host application)
  -i, --app-id string         Id of host application to talk to (like controller or router id)
  -t, --app-type string       Type of host application to talk to (like controller or router)
  -h, --help                  help for stats
  -p, --pid uint32            Process ID of host application to talk to
  -n, --process-name string   Process name of host application to talk to
      --tcp-addr string       Type of host application to talk to (like controller or router)
      --timeout duration      Operation timeout (default 5s)

no processes found matching filter, use 'ziti agent list' to list candidates
[ziggy@core-router-858f76f8fb-fvtqm ~]$ ziti agent list
╭─────┬────────────┬────────┬─────────────┬──────────┬─────────────┬───────────╮
│ PID │ EXECUTABLE │ APP ID │ UNIX SOCKET │ APP TYPE │ APP VERSION │ APP ALIAS │
├─────┼────────────┼────────┼─────────────┼──────────┼─────────────┼───────────┤
╰─────┴────────────┴────────┴─────────────┴──────────┴─────────────┴───────────╯

Hint: I'm using security contexts as additional security layer on my containers:
  podSecurityContext:
    allowPrivilegeEscalation: false
    capabilities:
      drop:
      - ALL
    privileged: false
    readOnlyRootFilesystem: true
    runAsGroup: 2171
    runAsNonRoot: true
    runAsUser: 2171
    seccompProfile:
      type: RuntimeDefault
  securityContext:
    fsGroup: 2171
    runAsNonRoot: true

might this prevent ziti agent stats to find its process?
bye,
Chris

Yes, I think the read only root might have prevented placing the IPC socket used by the probe. It will be more elegant to use the controller and router HTTP health checks, but there's a little work needed to template those on a separate web listener's binding. That way they'll be published to the kubelet but not to all IP addresses, especially avoiding publishing them with the client API, because they could represent a vector for DoS.

What is the path to the IPC socket? We could mount a tmpfs for the IPC to have an initial solution before migrating to the HTTP checks.

That might work. I've only observed the IPC socket in paths like this: /tmp/gops-agent.{pid}.sock.

That was it. I just added
additionalVolumes:
- name: tmp
  volumeType: emptyDir
  mountPath: /tmp

and the health checks started working. What do you think? Should we add an emptyDir to /tmp by default or should we keep it this way? At least I would extend it to limit the size of the emptyDir sizeLimit: 1Mi. Call me paranoid, but just in case something 'unexpected' happens and someone finds a way to upload data to /tmp - the OOMKiller would kill the pod and we would be informed that something is going on here...

It seems reasonable for us chart maintainers to define a non root emptyDir volume for temp, or to find a way to influence the socket path and ensure a writable volume is available there. I'll support using /tmp until we have a reason not to.


Set rotation center

c.f. https://github.com/geoman-io/leaflet-geoman/pull/1311
This PR allowing shapes to be rotated around any point in addition to the shape's center.

@strfx no, thank you. After a review of @codeofsumit we will merge it


Add Dynamic Lazy Load Module

Hello,
I managed to implement lazy load a feature module dynamically and load the the component in the DOM using this library for dynamic rendering of the component.
Works in both JIT and AOT runtime.
I think this feature will be great addition to the list of features this library supports.
Steps:

Add a lazy route which will never be accessed like after the path to not found route in the app routing. The lazy loaded module route config should be defined in the root route config.

const appRoutes: Routes = [
  ...
  {
    path: '**',
    component: NotFoundComponent,
    // redirectTo: 'login'
  },
  {
    path: 'lazyModule',
    loadChildren: () => import('./lazyModule/lazyModule.module').then(m => m.LazyModule)
  }
]

Define the lazy loaded module and set the entry component as static property on the module class.

import {CommonModule} from '@angular/common';
import {NgModule} from '@angular/core';
import {LazyFeatureComponent} from './lazy-feature.component';

@NgModule({
  declarations: [LazyFeatureComponent],
  exports: [LazyFeatureComponent],
  entryComponents: [LazyFeatureComponent],
  imports: [ CommonModule]
})
export class LazyModule {
  static entry = LazyFeatureComponent; // This is needed to determine the component we want to render
}

Here I created a wrapper component around the this library to load the lazy module.

import {Compiler, Component, Input, NgModuleFactory, OnInit} from '@angular/core';
import {Router} from '@angular/router';

@Component({
  selector: 'app-lazy-load',
  templateUrl: './lazy-load.component.html',
  styleUrls: ['./lazy-load.component.scss']
})
export class LazyLoadComponent implements OnInit {
  @Input() module: string;
  @Input() context: object;

  component: any;
  moduleFactory: NgModuleFactory<any>;

  constructor(private compiler: Compiler, private router: Router) {
  }

  ngOnInit() {
    const routeConfigs = this.router.config.filter(routeConfig => routeConfig.path === this.module);
    if (routeConfigs[0] && routeConfigs[0].loadChildren && routeConfigs[0].loadChildren instanceof Function) {
      (routeConfigs[0].loadChildren() as any)
        .then(module => {
          if (module instanceof NgModuleFactory) { // for AOT runtime
            return module;
          } else { // for JIT runtime
            return this.compiler.compileModuleAsync(module);
          }
        })
        .then(moduleFactory => {
          this.component = (moduleFactory.moduleType as any).entry; // our entry component to our feature
          this.moduleFactory = moduleFactory;
        });
    } else {
      console.error('Lazy module not found.');
    }
  }
}

<ng-container *ngIf="moduleFactory">
  <ng-container
    *ngxComponentOutlet="component; context: context; ngModuleFactory: moduleFactory;">
  </ng-container>
</ng-container>

 <app-lazy-load [context]="{...}"
                 [module]="'lazyModule'"></app-lazy-load>

That is all the setup needed to make a feature module lazy load at runtime when needed depending on data you have.
The loading of the module is the same thing as what angular does on lazy routes here but the code is private and not accessible from Router.
If the angular team makes the code public API in the future we can reuse they're loadModuleFactory method.
Let me know if you have any further questions or need any help integrating this part in the library.
Thanks

Hello, thanks for interesting suggestion!
Did you tried using Lazy Modules with Ivy Renderer API before? I think it can be more declaratively instead of using old View Engine.
Do you want to discuss that feature and implement that via PR?

Hello,
Tried using the my implementation of Lazy Modules and they work with Ivy.
Didn't try using the Ivy Renderer API, didn't had the time to look into it.
We can discuss what ideas you have for improvement.

I'll close that issue because with Angular Ivy we can load components lazily. You can find out example in readme or check out that tweet.
Thanks!

Hello @thekiba ,
With the release of Ivy I think that in the ngxd needs some changes regarding ngModuleFactory.

// https://github.com/IndigoSoft/ngxd/blob/master/projects/core/src/lib/directive/component.outlet.ts
// from
@Input() ngxComponentOutletNgModuleFactory: NgModuleFactory<any> | null;
// to
@Input() ngxComponentOutletNgModule: Type<any> | null;
...
// https://angular.io/api/core/createNgModuleRef
  private createNgModuleRef() {
    if (this.ngxComponentOutletNgModule) {
      this._ngModuleRef = createNgModuleRef(this.ngxComponentOutletNgModule, this.injector);
    }
  }

So my code from original post will be a bit simpler:
      (routeConfigs[0].loadChildren() as any).then(module => {
        this.component = module.entry;
        this.module = module;
      });

I also tested your suggestion with component | async and to have it load the component directly, but I have an issue if I have some services provided on the module and the entire module is defined as a lazy load route, in this case I will get an a NullInjectorError: No provider for ... error. Yeah probably I should move them from module to providedin root.
Interestingly in angular they still use compiler and NgModuleFactory, even tho they are deprecated. https://github.com/angular/angular/blob/master/packages/router/src/router_config_loader.ts#L71
If you think this changes would be useful I can work on a PR to make the changes.

Hello,
Updated code for lazy load of standalone components in Angular v14:
// define your route on the root routes
// this is needed for angular to build your component in the final package, they detect dynamic imports only defined in routes.
const appRoutes: Routes = [
  ...
  {
    path: '**',
    component: NotFoundComponent,
    // redirectTo: 'login'
  }, // lazy standalone components routes below, so user never reaches them
  {
    path: LazyComponents.MY_LAZY_COMPONENT,
    loadComponent: () => import('./lazyComponent/lazy.component').then(c=> c.LazyComponent)
  }
];
// enum to make things easy
export enum LazyComponents {
  MY_LAZY_COMPONENT = 'my-random-path'
}

// app-lazy-load component to fetch the component
import {CommonModule} from '@angular/common';
import {Component, Input, OnInit, Type} from '@angular/core';
import {Router} from '@angular/router';
import {NgxdModule} from '@ngxd/core';
import {from, Observable, of} from 'rxjs';
import {LazyComponents} from '....';

const wrapInObservable = <T>(value: T | Observable<T> | Promise<T>): Observable<T> => {
  if (value instanceof Observable) {
    return value;
  }
  if (value instanceof Promise) {
    return from(value);
  }

  return of(value);
};

@Component({
  selector: 'app-lazy-load',
  templateUrl: './lazy-load.component.html',
  standalone: true,
  imports: [CommonModule, NgxdModule]
})
export class LazyLoadComponent implements OnInit {
  @Input() component: LazyComponents;
  @Input() context: object;

  component: Type<unknown>;

  constructor(private router: Router) {}

  ngOnInit() {
    const routeConfig = this.router.config.filter(routeConfig => routeConfig.path === this.module)[0];
    if (routeConfig && routeConfig.loadComponent && routeConfig.loadComponent instanceof Function) {
      wrapInObservable(routeConfig.loadComponent()).subscribe(component => (this.component = component));
    } else {
      console.error('Lazy component not found.');
    }
  }
}

<ng-container *ngIf="component">
  <ng-container *ngxComponentOutlet="component; context: context;"> </ng-container>
</ng-container>

// app component in which to load my lazy standalone component
import {Component} from '@angular/core';
import {LazyComponents} from '....';
@Component({
  selector: 'app-component',
  template: './app-component.component.html',
})
export class AppComponent {
 LazyComponents = LazyComponents;
}

  <app-lazy-load [context]="mycontext" [component]="LazyComponents.MY_LAZY_COMPONENT"></app-lazy-load>

Hey, we can now lazy load standalone components with ngxd. If the modules are converted to standalone components, there's no need for this workaround.


Didn't find classes in another souceSet  ( android)

I'm not sure this bug is occured by auto-service-ksp or auto-service or kotlin.
I have multiple @AutoService annotated classes in multiple sourceset in same module. But services file contains lists of only one sourceset classes.
for example, I have files like this and all files have @AutoService(mypkg.MyTarget) annotions.
my_module/ src/ sandbox / mypkg / TargetA.kt
my_module/ src/ main / mypkg / MyTarget.kt
my_module/ src/ main / mypkg / TargetB.kt
my_module/ src/ main / mypkg / TargetC.kt

then, generated mypkg.MyTarget contains only TargetB , TargetC.
Is there any solution for this problem?

Sorry I don't understand

@ZacSweers ok, I'll try to write again :)
A module in an Android project can have multiple source sets. However, when I used auto-service-ksp to annotate classes, the resulting file in META-INF/service only contained classes from one source set.
for example, if my module name is my_module and my auto-service target class is MyTarget , I can wirte classes like below.
//my_module/src/debug/pkg_name/ TargetA.kt
package pkg_name
@AutoService( MyTarget)
class TargetA { ... }

//my_module/src/main/pkg_name/ TargetB.kt
package pkg_name
@AutoService( MyTarget)
class TargetB { ... }

//my_module/src/main/pkg_name/TargetC.kt
package pkg_name
@AutoService( MyTarget)
class TargetC { ... }

In this case, I expect the following content to be generated in the META-INF/services/MyTarget file.
pkg_name.TargetA
pkg_name.TargetB
pkg_name.TargetC

but generated file only contains class names from one source set like below. Class defined in another source set is omitted.
pkg_name.TargetB
pkg_name.TargetC

I used kotlin 1.8.21 , ksp 1.8.21-1.0.11.

can you make a minimally reproducing sample project and link/attach it here?

@ZacSweers i've made a sample project. https://github.com/kingori/ksp_test
Anyway, I think this is bug of android gradle plugin 7.3.1 because if I update plugin, this problem is gone. So it's not issue of auto service ksp. Sorry for wrong issue report.


[image_picker] Pin version of platform_interface.

Description
Publishing v1.1.0 of the platform_interface before the core plugin was ready to accept it (ignoring deprecation warnings) has caused breakage.
This PR locks the version of the platform interface to 1.0.0 so end users of the plugin (still) don't see the deprecation warnings themselves.
Related Issues
https://github.com/flutter/plugins/pull/2791
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[x] No, this is not a breaking change.

This will have to be merged on red, because submit-queue is broken because of the publish of the platform_interface.
This PR should pass analysis checks.

LGTM.

analyze is passing, merging on red.

analyze and publishable are passing. I'm merging this on red to fix the CI.


Spatially Resolved Thermochemical analysis of Molten Salt Fast Reactor

This model is the multiphysics RZ steady-state model of the Molten Salt Fast Reactor paid for by the NEAMS and ART-MSR program - for Issue #315 .

This will need a rebase.
Which code is going to be used to test this? We need to make civet install thermochimica for that code

Job VTB Documentation on 7a0a5d3 wanted to post the following:
View the site here
This comment will be updated on new commits.

Job Precheck on 7bef49f : invalidated by @GiudGiud
mstdb checkout merged

For future reference, the MSTDB thermo-file is outdated in this PR.
This isn't a large concern as users should be getting access to MSTDB from ORNL. We do not ship the whole database with the VTB, we only have an internal version available but the test suite only and not to users.
The thermo-file and the reference results will be updated in later PRs, as we update the version of MSTDB used by continuous integration.


Training yaml

Hello! Thank you for publishing the code!
I'm wondering if you could clarify which YAML file was used to train the CLIP model (efficient net 5b + Bio_ClinicalBERT)?

This one: pre_train_b5_clip.yaml
All the corresponding yaml files are referred from here based on hydra

Thanks for the quick response!
I have a few more questions:

Which CSV file contains the REPORT column? After reading the code this seems to be the text encoder input column, please correct me if I am wrong.
How does the code access the model config since they are not in this yaml file?

Here is my answer:
For data preparation you should go to this part
We have given a demo csv upmc_dicom_consolidated_final_folds_BIRADS_num_1_report.csv. You should have either of findings and impressions or both. Once you have this csv, call this function: augment_text.py with the csv and it will give you the final csv:  clip_pretrain_100.csv). This final csv file will be used for pretraining.
During pre-training, text encoder of Mammo-CLIP needs text and text_augment columns as specified in this file: clip_pretrain_100.csv).

Got it, thank you!


[Feature]: support yaml  config alias.

Description
Background
Apinto is a great project. But i found apinto already support read yml config file. But as we all know .yaml is equal with .yml. But from the eosc/config.go. I notice it's only read .yml suffix file. I think we can set up an constant array containing .yaml and .yml.Then read .yml first.

#52 Quote this issue.

Thank you for your support.
Apinto stipulates that the default configuration file is config.yml.
If you want to have other suffixes, you can configure the config field of apinto.yml file, like this
 config: config.yaml

 data_dir: ./tmp

 pid_dir: ./tmp/

 log_dir: ./tmp

 socket_dir: ./tmp

 extends_dir: ./tmp/extenders/

# error_log_name:  error.log

# error_log_level: error

# error_log_expire: 7d

# error_log_period: day

@Dot-Liu Thanks. I will close this issue.


Create camera-traps Jenkins job

Be able to build the camera-traps Rust code in Jenkins and, optionally, build all its images and push them to DockerHub.

Won't do, our current manual build using make meets our needs.


Lineage API: Duplicate nodes

Lineage API currently is sending duplicate nodes to the UI.
e.g. https://prospectlog.dev.odc.provectus.io/dataentities/29301/lineage

Fixed


Handle lifecycle accordingly

Maybe we can use a library for this too. We've had the problem a lot of times that Inexor won't properly shut down. Investigate, fix, make it awesome.

This includes mainly a strategy for thread pooling and signalling @a-teammate

I believe @a-teammate and I solved this in a hacking session in Stuttgart. Closing.


replasing named client

When trying to request a new tunnel with id/subdomain that was already requested a random one is being returned:
2018-04-10T01:05:42.163Z localtunnel:server making new client with id mycustomid
2018-04-10T01:05:42.164Z localtunnel:server:eprytkxfix tcp server listening on port: 45728
2018-04-10T01:05:42.246Z localtunnel:server:eprytkxfix new connection from: ::ffff:<IP_ADDRESS>:45728

I'm requesting the tunnel not via API (haven't tried tunnel.close() method so I don't know whether it would help) but via command line. Basically every time I restart my local tunnelable app I can't reach it anymore via the tunnel. So naturally I try to generate a new tunnel with the same id.
lt -h mylocaltunnelserver.tld -s mycustomid
But instead of expected mycustomid.mylocaltunnelserver.tld i get something like eprytkxfix.mylocaltunnelserver.tld. I don't know, maybe mycustomid has a ttl and I can regenerate it after some time but that would not be a solution anyway. Right now I have to restart the server every time.
I don't know if this is a by design. If it is please introduse an option to force replacement/overwriting which would terminate the old one before recreating it under the same id. Maybe it would be wise to allow this only from the remote ip that has created the first tunnel in the first place or do it with the help of secret words or something.
Thank you.

It will let you reuse the id once the existing client connection is closed.

I have pushed a large refactor to the server code (and deployed the refactor to the localtunnel.me production version).
The behavior around releasing old client ids should be much improved (I did a lot of local testing around various restart conditions). The timeout for releasing an ID once your localtunnel client dies is now 1 second.


Create ccp-spain.toml

Parser for CVKMNLC COVID-19 patient data, Hospital del Mar, Barcelona, Spain.
Needs review. Thanks!

@ekamau thanks for picking up on this!
I've double checked and it appears that all of the 'observations' are indeed recorded at the time of admission.
During the hospitalisation only what we consider as 'treatments' are recorded (e.g. specific drugs).


Fix for issue #711: The specified item already exists in the keychain, iOS Code -25299, -25300

My suggestion for fixing bugs 25299 and 25300, which have existed on iOS since version greater than 9.0.0.
Original issue: The specified item already exists in the keychain, IOS #711
The problem occurred when the parameter kSecAttrAccessible was used to check whether a certain key already exists. The parameters kSecAttrAccount and kSecAttrAccessible together are not unique. The key kSecAttrAccount can therefore only occur once, even if kSecAttrAccessible is different.
In addition, kSecAttrAccessible cannot be changed by SecItemUpdate. This requires the key to be deleted and recreated.
Another problem arises with the kSecAttrSynchronizable parameter. To check whether a key already exists, it must be checked with and without synchronize. Not setting kSecAttrSynchronizable in order to ignore it in the query does not seem to help here. The current workaround is to read the value with and without sync.

This is the correct PR to merge. Please do NOT merge #734 as it will exacerbate the issue.
The parameters that were optional (kSecAttrAccessible) should be made optional again. This PR does that, and should be merged to fix the issues in #711

I think this PR may also be missing the ability to set the accessibility key to null via dart. Otherwise, the value is still always set.

I think this PR may also be missing the ability to set the accessibility key to null via dart. Otherwise, the value is still always set.

Hi, why do you think that? In this PR, accessibility should be optional.
if (accessibility != nil) {
    keychainQuery[kSecAttrAccessible] = parseAccessibleAttr(accessibility: accessibility)
}

If it is not specified in flutter, the attribute is ignored.
But at the latest apple will set kSecAttrAccessibleWhenUnlocked as the default attribute.
Or have I missed something?

Hi all, if i read everything correctly, this PR is done for merge, however the only thing on the dart side AppleOptions that should change is this:
    KeychainAccessibility? accessibility,
    // KeychainAccessibility accessibility = KeychainAccessibility.unlocked,

I will make this change in a new major version since it would change the current default behavior.

@dballance Has kindly done some work on this already @juliansteenbakker. This is the commit you want I believe!
https://github.com/Tango-Tango/flutter_secure_storage/commit/400f6b4eb6ebaea6936fdbaa0d2f16ef36576678

Thank you for pointing me in the good direction @paulking86 ! Since that change is not breaking, i will merge it right away.


General UI enhancements

Add local notifications for successful and failed transactions

only show/ring when not on the page

Fix the "retrigger step" Button glitch in swapping modal
general styling and animations
refresh balances on successful swap
show final balance in modal after a swap
"no routes found" information display
error handling

fixed error-parsing in nxtp process

Pretty cool, looks nice.
Feedback:

[ ] The mobile layout of the swap timeline should maybe not switch between the left and right side
[ ] The desktop modal is very big. I think it does not have to be that tall. Also the footer section looks quite empty most often. Perhaps it would help to vertically center the loading animation to use the space
[ ] I like that we show the new balance at the end. Perhaps also add on which chain we have this balance, add a coin icon and make the balance/coin clickable with a hint, to add the coin to metamask
[ ] We may allow to extend the process with an optional footer message, that would allow to keep the message in the timeline short and add a longer more explaining message for the footer section
[ ] We need a warning/info box on top of the swap to add explaination, a beta waring and that users should use metamask. Maybe you can think about a design for this, and make the image smaler...
[ ] The "No Route Found" section could have a background so it better readable

I have to test the notifications more, so far I didn't see any.


[feature] statically typed vdom

Use type wrapping, just like Iterator do. One of the "react in rust" projects used to do that, can't remember which one.

make children and attributes generic:

struct Node<C: Diff, A: Diff> {
  children: C,
  attributes: A,
}

stored attributes as a list of key-value-pairs
store children and attributes as tuples and implement diffing as a Trait:

impl <T0: Diff, T1: Diff, T2: Diff> Diff for (T0, T1, T2) {
  fn diff(&self, ancestor: &Self, ...) {
    self.0.diff(&ancestor.0);
    // ...
  }
}

nice-to-have rust features:

impl-trait-existential-types: so we can return an impl Trait from Renderable::view
const-generics: to store the html element tags and attribute keys and values in the type. Until this lands, we could store them as values and assume (add debug_assert_eq to diffing) they never change

pros:

less runtime overhead
less allocations

cons:

bigger binaries (?)
higher compiletime overhead (incremental compilation?)
limited number of children elements/attributes without manually fallbacking to dynamic  (can this be done automatically? eg by the html macro?)

Another feature that could be based on this one is to store all the static parts as an html "template", then copy that to the proper locations in the DOM and fill in the dynamic parts.
This is inspired by lit-html
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/template

@chpio why did you close this?

yew's vdom has a strong "attachment" to the real dom, i just don't think it's compatible with my feature request.


DefaultDockerClient.execCreate() always tries to connect over UNIX socket

This is very slightly related to #283 but I get a different error in a slightly different context.
Using latest stable API 3.5.12 inside a docker-compose group, I try to execute a command on one container inside another running container (for restarting a supervisord service inside the target container):
String execId = client.execCreate(container.id(), new String[]{"supervisorctl", "-c", "/etc/supervisord.conf", "restart", "worker"},
                DockerClient.ExecCreateParam.attachStderr(),
DockerClient.ExecCreateParam.attachStdout());

My Docker client is connected to : http://dockerhost:2375
(which is resolvable, the same command - I took the POST Url generated by DefaultDockerClient#execCreate() - works just fine over Postman from the host).
However, using the API, the call fails with no concrete error, only in the docker logs, I see it tries to connect over socket instead of TCP/IP as configured:

level=error msg="attach: stdout: write unix /var/run/docker.sock->@: write: broken pipe"

Is there a way to force TCP/IP connection? When I try to connect from one container to another, sockets won't work...
I'm on Linux 4.4.1-2-MANJARO x64 using Docker 1.9.1 and docker-compose 1.5.2

level=error msg="attach: stdout: write unix /var/run/docker.sock->@: write: broken pipe"

The error message looks to me less like the client is attempting to connect to the socket, and more like the host is receiving the request correctly over http but having an error trying to write the logs from the socket. Try making the same call but not attaching the stdout log and see if it works.

You can use TCP sockets if you set your env vars correctly. See this part in the README:
// Create a client based on DOCKER_HOST and DOCKER_CERT_PATH env vars
final DockerClient docker = DefaultDockerClient.fromEnv().build();

thanks for the info, tried but did not help.
I can use the API without problems from a standalone app and the same Docker client builder opts (using a valid http:// docker host url).
I seem to run into a similar issue as this one:
http://stackoverflow.com/questions/29938208/docker-client-java-api-the-server-failed-to-respond-with-a-valid-http-response
Because I don't use any other libraries in my standalone test, it works there, but inside my JEE wildfly environment, where we also use RESTeasy, there seems to be a clash with the spotify client lib's Jersey lib. I also tried the shaded JAR, but then my request broke even earlier.

Closing since this issue is pretty old and OP seems to have found a workaround. I can reopen if it's still a problem.


Code refactor.

Refactore flush logic which is commonly used to sync operation with Elastic search in batch.

Thanks @atapatel


[security] make it easier to redefine Alpha/Gamma

While talking about some security aspect and as to how you'd alter Alpha
or Gamma role in a specific environment, I realized that these
module-scoped constants would be much more useful as class attributes.
This way, someone can override these sets in their security manager
to alter base roles.

Codecov Report

Merging #7036 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master    #7036   +/-   ##
=======================================
  Coverage   64.63%   64.63%
=======================================
  Files         422      422
  Lines       20607    20607
  Branches     2253     2253
=======================================
  Hits        13320    13320
  Misses       7165     7165
  Partials      122      122

Impacted Files
Coverage Δ

superset/security.py
75.65% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6e79e84...6e1488a. Read the comment docs.


fix column names in versionable with Postgres

When using Postgres, the versionable behavior produces invalid column names for the *_ids and *_versions columns, because the foreign table name it uses as a prefix includes the Postgres schema name and a dot. This pull request uses getCommonName() instead of getName() for the table name when generating the column names, thus leaving off the schema prefix.
This replaces the pull request submitted a while back as #498.

Has this issue been fixed?


React Native UI-Kitten Overflow Menu inside Top Navigation renders on left first before rendering to Right.

💬 Question
I have created a react native project with a Top Navigation Bar, top Navigation consists of Title and right menu (accessoryRight).  I have used Overflow Menu and Menu Item to get the menu working.
Issue:
The menu renders to the left momentarily before adjusting the rendering to the right.
I have upgraded my project from UI Kitten version 4 to 5 when the issue started to happen.
UI Kitten and Eva version

Package
Version

@eva-design/eva
2.2.0

@ui-kitten/components
5.3.1

@ui-kitten/components
5.3.1

@ui-kitten/eva-icons
5.3.1

@ui-kitten/metro-config
5.3.1

`
import React from 'react';
import { View } from 'react-native';
import {Icon, IconElement, MenuItem, OverflowMenu, Text, TopNavigation, TopNavigationAction} from '@ui-kitten/components';
const MenuIcon = (props): IconElement => (
<Icon
{...props}
name='more-vertical'
/>
);
const InfoIcon = (props): IconElement => (
<Icon
{...props}
name='info'
/>
);
const LogoutIcon = (props): IconElement => (
<Icon
{...props}
name='log-out'
/>
);
export const HomeScreen = (): React.ReactElement => {
const [menuVisible, setMenuVisible] = React.useState(false);
const toggleMenu = (): void => {
setMenuVisible(!menuVisible);
};
const renderMenuAction = (): React.ReactElement => (

);
const renderOverflowMenuAction = (): React.ReactElement => (

);
const renderTitle = (props): React.ReactElement => (

<Text {...props}>
Test Application

);
return (

);
};

`
I have attached the video as well for reference
RightMenu.webm
Any advise on how to stop the temporary rending to left would really be helpful.
Environment
--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>Testing in Android 11 and 8

I have another an issue. If on mobile changed orientation to landscape mode, then all select, overflow menu broken. When I click open select my phone changed orientation to portrait

I'm also experiencing the same behaviour.

I created the issue long time ago but didn't answer me

Same issue for me

Same issue for me

I'm also running into the same issue. 🤔

I think I was able to workaround the issue. I noticed that the contentPosition within the popover's initial state was set to Point.zero() which corresponds to the top left corner of the screen where the render flicker occurs. After setting the contentPosition's initial state to Point.outscreen(), the issue was resolved for me.

I think I was able to workaround the issue. I noticed that the contentPosition within the popover's initial state was set to Point.zero() which corresponds to the top left corner of the screen where the render flicker occurs. After setting the contentPosition's initial state to Point.outscreen(), the render flicker was resolved.

On checking this out myself, the Point.outscreen() cleans the rendering up a ton for me as well. I have a fork set up where I've tried this out on my own WIP. The fork https://github.com/KasemOmary/react-native-ui-kitten/blob/419898b3130a18570acebd195f920ae4d2d834a4/src/components/ui/popover/popover.component.tsx#L118 - is strongly preferred.


Mouse events from Feature components not firing

Hello,
I'm having trouble getting mouse events to fire from Feature components. I installed the debugging boilerplate and was able to reproduce the issue.
The click events seem to go straight through the Feature component, the onClickMap event gets fired instead as if Feature components weren't there. The Marker component fires all events (onClick, onMouseEnter, onMouseLeave) correctly.
I think this is related to comments by @jpdevries https://github.com/alex3165/react-mapbox-gl/issues/197#issuecomment-309316227 and @stereobooster https://github.com/alex3165/react-mapbox-gl/issues/217#issuecomment-309294793
Sandbox with debugging version: https://codesandbox.io/s/E113Kmnl (logging mouse events to console).
Perhaps I'm missing something obvious? Thanks!

Hey @rlueder, thank you for reporting the issue, could you send me a link to the bug you reproduced with react-mapbox-gl-debug?

Sure, added a sandbox link to the issue description. 👍

As a side note, I thought that adding transparent Markers on top of the Features could work, it does work as a quick hack but performance when moving/panning/zooming the map drops so much that's not a good idea.

Hey @rlueder, That's not how you should use Layer and GeoJsonLayer here is your example modified: https://codesandbox.io/s/k5QVw577x
Layer add both a Layer and a Source that's probably a confusing bit I should add to the documentation. You should use GeoJsonLayer only for static data that doesn't need interactions (mouse events...)

@alex3165 Thanks for finding the time to reply and posting an example. I understand now, and have managed to make it fit my needs (I have an API generating GeoJSON for a few thousand points I need added to the map).
In case someone else has the same wrong assumptions as me, here's a summary of what I did wrong:

GeoJSONLayers do not support mouse events, I wrongly assumed they were a "shorthand" for rendering layers from GeoJSON. I think having Layers in the name made me think I could add Features to it as to a Layer component.

Source components are not needed to render Layers based on GeoJSON, all I had to do was map the properties of my GeoJSON directly to the Layers, maybe the docs could use some clarification here as the docs say "Add a source to the map (for layers to use, for example)." followed by:

 so I just assumed they'd always go together.

Events fired on a Feature component do not block events being fired on the map, I thought that being "on top" of the map would block events on the map itself.

And here's an example forked from my original sandbox that satisfies my needs (clickable Features rendered from GeoJSON data): https://codesandbox.io/s/kZXqNV8n5
Thanks!

Thanks for the detailed answer 👍


refactor(symbol): replace symbol polyfill to separate package

Description:
This PR replaces existing symbol declaration into symbol-observable package.
Related issue (if exists):
closes #1636
Notes
Blocked by https://github.com/blesh/symbol-observable/pull/4 .

@kwonoj FYI: the issue is resolved and a new version of symbol-observable has been published.

So just one nitpick, other than that, it LGTM.

I'll wait travis to be happy before check this in.

Well, right now it looks like CJS will compile, but ES6 will not, for whatever reason. When compiling the ES6 it can't find the module.

Specifically: npm run build_cjs works, but npm run build_es6 does not

Ugh, I'd bet anything that TypeScript is expected all imported modules from node_modules to be ES2015.

Yes, noticed that, thanks for pointing out. Looking into it now..

Ugh, I'd bet anything that TypeScript is expected all imported modules from node_modules to be ES2015.

: Uh-oh, :fire: I'm burning..

Just fyi, moduleResolution solves es15 build but not systemjs-builder complains about external dependencies. :/ looking into it also..

@blesh - I've updated 2 parts more,

symbol-observable is now dependency instead of devDependency
systemjs bundler will mark symbol-observable externally resolved, let each consumer to provide it

and I believe both need to be approved. Will leave this to get suggestions & corrections if there's wrong I did.

the use case for the system bundles is to provide tool-free usage, so it seems to be it would be simpler just to include it, as its unlikely to be provided elsewhere, no?

so it seems to be it would be simpler just to include it, as its unlikely to be provided elsewhere, no?

: Yes, I wasn't sure if current change's legit so would like to ask to confirm it. I'll try to include it as well, my initial attempt wasn't successful while resolving external modules.

Updated PR as suggested.

Merged with b626d97 .


error while installation via lazy.nvim

Hello! Congrats on the plugin—it's looking really good!
I did run into one issue during installation: a duplicate tag error for "FOCUS" while using lazy.nvim:
...hare/nvim/lazy/lazy.nvim/lua/lazy/manage/task/plugin.lua:95: Vim:E154: Duplicate tag "FOCUS" in file .../.local/share/nvim/lazy/focus.nvim/doc/focus.txt

If possible, would love support for mini.pick as well, as it's a great alternative to telescope. Thanks again!

Thanks, I just fixed that. I will look into mini.pick support!


Allow for a configurable connector on search component

This PR adjusts the search component, allowing you to provide a custom SiteSearchAPIConnector. This allows the same component to be used to search other Swiftype "engines".
Todo

[x] write a test for the condition
[x] look into whether prop types can assert that the .connector is an instanceOf SiteSearchAPIConnector

Thanks @katydecorah for the feedback. This all feels a lot better to me now. Final review?


Support annotations for the Service resource

Edit: Created a PR: https://github.com/trinodb/charts/pull/149
When using aws-load-balancer-controller, it is useful to pass annotations in the Service ( https://github.com/trinodb/charts/blob/trino-0.19.0/charts/trino/templates/service.yaml ) to denote what properties the load balancer could have.
Proposed solution:
From https://github.com/trinodb/charts/blob/trino-0.19.0/charts/trino/values.yaml#L226
service:
  type: ClusterIP
  port: 8080
  annotations: {} # <--------- this field is new

From  https://github.com/trinodb/charts/blob/trino-0.19.0/charts/trino/templates/service.yaml
metadata:
name: {{ template "trino.fullname" . }}
labels:
  app: {{ template "trino.name" . }}
  chart: {{ template "trino.chart" . }}
  release: {{ .Release.Name }}
  heritage: {{ .Release.Service }}
#######
# This section is new
########
{{- with .Values.service.annotations }}
annotations:
  {{- toYaml . | nindent 4 }}
{{- end }}
#######
# /This section is new
########
spec:

I could make a pull request if you'd like.

Created a PR: https://github.com/trinodb/charts/pull/149

Fixed by #134


OmxEncoder: do not call handle_out_buf if flag is EOS

I don't think we can do this because https://github.com/commaai/openpilot/blob/master/selfdrive/loggerd/omx_encoder.cc#L398.

I don't think we can do this because https://github.com/commaai/openpilot/blob/master/selfdrive/loggerd/omx_encoder.cc#L398.


My slide

--- layout: slide title: "Welcome to our second slide!" --- Your text Use the left arrow to go back!

git fetch origin git checkout -b My-slide origin/My-slide git merge main

git fetch origin git checkout -b My-slide origin/My-slide git merge main


[Feature Request] support for meson or cmake

Feature description:

Can it support the use of meson? or how to use it in meson after I use the following command to build
Problem it solves or use case:

Proposed implementation or solution:

build protovalidate-cc

make build

use protovalidate in proto

gen proto to c++，why not generated  protovalidate.pb.cc and protovalidate.pb.h?

my config for test.proto

what should i do?

Contribution:

Examples or references:

Additional context:

solve by command:
buf generate --include-imports


chore(build): remove html-loader options

Follow-up from #2537, these options still remained.

LGTM.


Enable SSL connections with User/Pass authentication

Fix #54

Thank for pull ;) Today I will try to publish a new version


Tvp server cursor fix

for issue #224

Codecov Report

Merging #234 into dev will increase coverage by 0.49%.
The diff coverage is 90%.

@@             Coverage Diff              @@
##                dev     #234      +/-   ##
============================================
+ Coverage     33.45%   33.94%   +0.49%
- Complexity     1487     1507      +20
============================================
  Files            97       97
  Lines         23390    23406      +16
  Branches       3840     3843       +3
============================================
+ Hits           7824     7945     +121
+ Misses        14002    13873     -129
- Partials       1564     1588      +24

Flag
Coverage Δ
Complexity Δ

#JDBC41
33.83% <90%> (+0.53%)
1500 <1> (+25)
:arrow_up:

#JDBC42
33.89% <90%> (+0.5%)
1504 <1> (+19)
:arrow_up:

Impacted Files
Coverage Δ
Complexity Δ

...n/java/com/microsoft/sqlserver/jdbc/Parameter.java
30.95% <ø> (+1.33%)
37 <0> (+1)
:arrow_up:

...om/microsoft/sqlserver/jdbc/SQLServerResource.java
100% <ø> (ø)
4 <0> (ø)
:arrow_down:

...m/microsoft/sqlserver/jdbc/SQLServerResultSet.java
24.91% <100%> (+0.9%)
173 <1> (+3)
:arrow_up:

...in/java/com/microsoft/sqlserver/jdbc/IOBuffer.java
37.46% <89.47%> (+0.51%)
0 <0> (ø)
:arrow_down:

src/main/java/microsoft/sql/DateTimeOffset.java
37.14% <0%> (-2.86%)
8% <0%> (-2%)

.../microsoft/sqlserver/jdbc/SQLServerConnection.java
41.14% <0%> (-0.05%)
230% <0%> (+1%)

...om/microsoft/sqlserver/jdbc/SQLServerBulkCopy.java
44.98% <0%> (+0.07%)
183% <0%> (+1%)
:arrow_up:

...m/microsoft/sqlserver/jdbc/SQLServerStatement.java
58.36% <0%> (+0.4%)
129% <0%> (+1%)
:arrow_up:

... and 5 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0a0f330...207cf4b. Read the comment docs.

In ResultSet+storedProcedure+Cursor combination, no exception is thrown if there is no storedProcedure or if invalid/incompatible storedProcedure name is passed.

@v-suhame fixed exception issue with invalid SP/TVP name


Proper Structured Data Implementation

Few more validation errors that can be fixed. Logo structured data is missing on all pages
https://search.google.com/structured-data/testing-tool/u/0/?url=http%3A%2F%2Ftechpp.com%2F%3Famp#url=http%3A%2F%2Ftechpp.com%2F2013%2F06%2F27%2Fandroid-lock-screen-apps%2F%3Famp
not only does it throw validation errors, it also ensures that the logo doesn't show up on Google search page
REPORTED AT: https://www.facebook.com/its.Ahmed.K/posts/1142008352536646?__mref=message_bubble

We don't handle the Structured data output. It is managed by the AMP plugin. We need a way to edit it / make changes.

I just found a quick solution to that problem,
Go to Customizer > Then navigate to 'Site Icon'
just add the image in the Site Icon and that will fix that validation issue as well


Re-work csvcubed Resource URIs

[x] Shorten concept scheme URIs. They should be #{notation} and #codelist instead of #concept/{scheme-name}/{notation} and #scheme/{scheme-name} respectively. The catalogue metadata URIs should probably continue to contain their type in their name since the concepts are the primary identifiers of interest in the CSV-W.

[x] Add a validation check which ensures that none of the concepts in the scheme happen to have the uri-identifier of codelist so that a concept called codelist cannot clash with the scheme definition.

[x] Alter all relative URLs so that they never use a slash / after the fragment identifier (unless there is a parent/child relationship between the two parts of the URL). We need to replace all these instances of / with another character. Use a semicolon (;) for now -- but make sure this parameter comes from a configurable value in the WriterBase class so we can easily alter the functionality in future.
[x] Add the capability to alter how we deal with defining URIs for each file. We currently use ./{data-file-name}.csv# to differentiate resources declared in different files. Add some functionality to easily customise this.

N.B. this task will require reworking a lot or behave tests in both csvcubed and gss-utils.

Not using semi-colon ; since it's a reserved character

Once this has been published, @canwaf agrees to act as spokesperson to present this to the real world to see what they think about our URIs.
Speak to the Greek Lord of the Qb + Swirrl.


PressListener.pressedTrail can be incorrect

In https://github.com/phetsims/scenery/issues/1356 we identified a case where the pressedTrail of PressListener can be incorrect. The pressedTrail is set in onPress. But it doesn't update if the targetNode moves in the scene graph. For example, consider this case in function-builder:
On press, PressListener.pressedTrail looks like
[Node, Node, PatternsScreenView, Node, PatternsSceneNode, Carousel, Node, Rectangle, CardContainer, Node, ImageCardNode]

But during the drag, Trails (plural, this example uses DAG) of the last Node for that Trail look like
[Node, Node, PatternsScreenView, Node, PatternsSceneNode, Node, ImageCardNode]
[Node, Node, PatternsScreenView, Node, PatternsSceneNode, SeeInsideLayer, Node, ImageCardNode]

And the pressedTrail that was set in onPress no longer exists in the scene graph.
This is potentially problematic because DragListener uses the pressedTrail for coordinate transforms. Also, if pressedTrail is up to date, it can be used in https://github.com/phetsims/scenery/issues/1356 for the coordinate transforms necessary to keep the target of the PressListener in view. Assigning to @jonathanolson to investigate.

Since the pressedTrail is set every press on the PressListener instead of the pointer it might become inaccurate in cases of multitouch.


Car Shop Mod ver1.5 crashes the game

When using Car Shop Mod ver1.5 https://www.gtainside.com/en/gta4/mods/32149-car-shop-mod-ver1-5/ then the game will crash. Also if I remove my save, it loads the cutscene and everything works fine but if you try to skip the initial cutscene (when you make a new save game) then the game freezes and you can hear audio and a few seconds later closes.

Also it seems like Robbery Mod V2 also crashes the game the same way https://www.gtainside.com/en/gta4/mods/65034-robbery-mod-v2/, also while the Farnsworth's Business Mod https://www.gtagaming.com/farnsworths-business-mod-complete-v2-f21460.html does seems to load into the game, It doesn't seem to function as it does show the prompts like to buy a property or to start work put pressing any key nothing happens, also a few prompts look a bit odd. Ultimate Indicator Script https://github.com/pedro2555/gta-iv-mods/releases/tag/ultimate-indicator-script-v1.0.0 also has the same problem as the business mod, pressing any of the keys the indicators don't work and you get an error.

Please open up a new issue for each script that gives you problems so it's better organized, and prevents others from posting duplicates.

Please open up a new issue for each script that gives you problems so it's better organized, and prevents others from posting duplicates.

Ok sure thing


change of sign in surface loss

Before posting, do check out the FAQ: https://github.com/LIVIAETS/boundary-loss#frequently-asked-question , the answer of your question might be there
i have use the surface loss that has been mentioned here " https://github.com/LIVIAETS/boundary-loss/issues/14#issuecomment-547007286"
so i am using a dataset where the images have two different labels, so i have trained two models for two different label for the first label the surface loss is positive in all the cases. whereas while using the second set of label,  the surface loss is negative. how can i solve this problem

thanks in advance

It is hard to help you, with so little information.
I am not fully sure this is really a problem; with different labels, the optimal loss will have different values, and the problem will be easier (or harder) to optimise.
So, if one of the set of labels ends up with a positive loss, it means that the network is having troubles to learn for that specific case. You could try to tune parameters of the optimizer (learning rate & co), the loss weight, and try another base loss (there are many alternatives to GDL).
Best,
Hoel


get_query_parameter_u64_with_offset is broken

Looks like it accepts an offset and passes it to GL as a pointer?
I think it needs to be 2 variations of this function: one where you pass a buffer with offset, and another where you pass a pointer. Similar to glReadPixels and friends.

Looks like it was added in #260
@Zoxc do you remember why it was set up this way, or maybe an example of how you were testing it with query objects? Just wondering if it's missing something here

I made it take usize because this library seem to prefer typical Rust types when possible. An additional variant which uses a pointer would also make sense. The offset variant makes it clear that you're not actually passing a pointer.

I used this function here and tested it with wgpu_profiler.

It seems to require that a buffer be bound, and then read from. Would be nice if it worked like the u32 functions where the value is just returned.


Improve author search

From beta feedback, many test cases.

Fixed by https://culibrary.atlassian.net/browse/ARXIVNG-372


Prevent computing full document content highlight per block and only compute current block content for performance

Related with https://github.com/napari/napari/issues/6845
Current code computes the full document highlight for each document block/paragraph causing freezes as soon the document content starts to get a little bit long. To reproduce, you can run the examples/code_highlight.py, copy and paste the widget text content multiple times (selecting the full content to do a new paste increases the chance to stumble with a freeze in a shorter amount of time). So something like:

This PR tries to prevent/improve the situation by only computing the current block content/text highlight data (not sure if there is a better approach so happy to give a check to any other ideas!). Doing a similar check with the example content copy and paste operations with the changes in this PR:

@Czaki, since this is your object, would appreciate your review

This change provides a significant performance boost and I do not see downsides of these changes.
Test failures look unrelated.


Regarding Alternatives to Hashicorp Vault for On-Premise Deployments

Dear All,
Is there an alternative to Hashicorp Vault for on-premise deployment of Hyperledger Bevel?
Thanks and Regards,
Gokul Alex

@gokulsan Thanks for the question. Please check https://hyperledger-bevel.readthedocs.io/en/latest/contributing/how-to-contribute/ and https://hyperledger-bevel.readthedocs.io/en/latest/contributing/asking-a-question/ before creating "questions" as "Issues". If you have a question, you can post it on the Discord channel


RF: Reimplement SignalExtraction

nipype.interfaces.nilearn.SignalExtraction has been a consistent pain point for users with large BOLD series, resulting in the creation of the --low-mem flag (#663) to reduce its memory usage by saving an uncompressed copy of its inputs, thus enabling loading data on an as-needed basis via mmap.
This is a proof-of-concept for a pure nibabel replacement. I haven't included all of the options that the nilearn interface presents, but it does handle our use case.
The heart of it is this:
series = np.zeros((img.shape[3], n_masks))

data = img.get_data()
for j in range(n_masks):
    series[:, j] = data[masks[j], :].mean(axis=0)

The reason I treat time series as the basic unit rather than volumes is that Nifti images are row-major, so each time series is contiguous in memory, rather than each volume. So there's no getting around loading the whole data set, but we can at least avoid making unnecessary copies (or, rather, letting them garbage-collect, rather than computing them in one large data array, as a GLM-based algorithm would).
The test is provided as a verification that we get the same results, as well as a speed-up, even in mmaped cases. I test 3 and 10 masks, for the sake of making sure that the improvements generalize beyond our specific case.
I haven't yet done memory profiling, but I believe for the reasons stated above that the memory usage should be substantially lower. @oesteban, your input would be appreciated here, as I think you could probably fix up this test to add memory profiling in much less time than I could.

will look into this next week 👍

Hooray!


Pin ubi image v

Issue link

What changes have been made

Verification steps

Checks

[ ] I've made sure the tests are passing.
Testing Strategy

[ ] Unit tests
[ ] Manual tests
[ ] Testing is not required for this change

/lgtm

/approve


docs: add note to check constructor for retry opts params

Pull Request Checklist

[ ] Did you add new tests and confirm existing tests pass? (yarn test)
[ ] Did you update relevant docs? (docs are found in the site folder, see guidleines below)
[ ] Do your commits follow the Conventional Commits standard?
[ ] Does your PR title also follow the Conventional Commits standard?
[ ] If you have a breaking change, is it [correctly reflected in your commit message](https://www.conventionalcommits.org/en/v1.0.0/#examples? (e.g. feat!: breaking change)
[ ] Did you run lint (yarn lint:check) and fix any issues? (yarn lint:fix)
[ ] Is the base branch you're merging into development and not main?

PR-Codex overview
Detailed summary

Added a note about modifying retry configurations in the waitForUserOperationTransaction method.
Changed the argument passed to waitForUserOperationTransaction from result.hash to userOperationResult.hash.
Removed the example code block for waitForUserOperationTransaction from the documentation.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Current dependencies on/for this PR:

development

PR #203

PR #202

PR #201

PR #204

PR #205   👈

This stack of pull requests is managed by Graphite.


Support unix sockets

Requires https://github.com/keathley/finch/issues/139 and #30
Curl allows to do:
$ curl --unix-socket /var/run/docker.sock http:///v1.41/_ping
OK

Let's support that in Req too:
iex> Req.get!("http:///v1.41/_ping", unix_socket: "/var/run/docker.sock").body
"OK"

maybe the url could even simply be: "/v1.41/_ping" and we'd default it to http + localhost.

On main!


Add multinomial_logit

Summary:
Add a function that matches the existing bernoulli_logit and  categorical_logit.
Description:
This would add a convenience function usable in multi-outcome logistic regression problems. For models with larger data sets it would add a significant speedup, given that the current multinomial function has to be called every single iteration, since it currently only accepts a single vector.
Current behavior
Assume there are N data points and K different outcomes, y is a NxK matrix of integers, beta is a K vector with some combination of covariates and predictors for each outcome,
for (n in 1:N) {
    ...
    y[n] ~ multinomial(softmax(beta))
}

Wanted behavior
y ~ multinomial_logit(beta)
In this case beta would be a NxK matrix with some combination of covariates and predictors for each outcome.
Additional Information:
I could not find any open issues for this missing feature. Also, I am not sure if this should be added as an issue to the stan-dev/math repository.
Current Version:
v2.9.0

Helping @mcol clean up stan issues. Feel free to close if any of this is irrelevant now.

This should be included in Stan.  So please don't close.


on_stats transfer time wrong using async functionality

It might be intended behavior, but it feels odds to me.
I'm basically building a pile of promises to keep my script processing fast. At the end of the script, I'm firing all the promises using the Pool functionality using concurrent connections. In the 'on_stats' callback I'm registering my API call process times, to figure out whether requests are too slow so they need optimisation.
Using sync requests, this performs quite well, as the request is performed directly and the transfer time is reported correctly. When using asynchronous requests, it seems the transfer time is registered from the moment the promise is created until it is totally finished. This adds my scripts process time to it basically, giving wrong statistics.
So - tried to simplify in an example:
$params = array_merge($params, [
    'on_stats' => function (TransferStats $stats) {
        echo $stats->getTransferTime(); // This results in a high number instead of just the transfer time it seems
    }]);

$promises = [
    $client->postAsync($url, $params),
    $client->postAsync($url, $params),
    $client->postAsync($url, $params),
    $client->postAsync($url, $params),
];

// PERFORM A LOT OF CODE IN HERE (takes 10 seconds e.g.)

// Build callable list of promises
$requests = function ($promises) {
    yield function() use ($promises) {
        return array_shift($promises);
    };
};

// Handle concurrent requests
$pool = new Pool($command->getAboss()->getClient(), $requests($promises), [
    'concurrency' => 5,
    'fulfilled' => function ($response, $index) {
        // this is delivered each successful response
    },
    'rejected' => function ($reason, $index) {
        // this is delivered each failed request
    },
]);

// Initiate the transfers and create a promise
$promise = $pool->promise();

// Force the pool of requests to complete.
$promise->wait();

See #1506 for explanation of how this got 'solved'. Basically it was my mistake.


[FEATURE]  Ensure section 1 is always set to public

PR here

Dom's feedback:
Site details and location’ – this section must be public with no option to make private regardless of whether the user choses to make all sections private by default/what they change other sections to


create anchors to each subsection

This adds some javascript code to address #73
Each section (e.g. h1, h2, h3, etc.) now gets an anchor, using https://www.bryanbraun.com/anchorjs.

Here is an example. Note however that the latest change (enabling the anchor also for h1) somehow also enables it for the website title...  That is something to address.

Since I opened this PR, I propose that someone else approves of it and merges it for release on the  website.


Breaks trying to compile on debian

Used latest git of nghttp2
Making all in mod_h2
make[1]: Entering directory '/usr/src/mod_h2/mod_h2'
  CC       mod_h2_la-h2_alt_svc.lo
  CC       mod_h2_la-h2_config.lo
  CC       mod_h2_la-h2_conn.lo
  CC       mod_h2_la-h2_conn_io.lo
  CC       mod_h2_la-h2_ctx.lo
  CC       mod_h2_la-h2_from_h1.lo
  CC       mod_h2_la-h2_h2.lo
  CC       mod_h2_la-h2_h2c.lo
  CC       mod_h2_la-h2_io.lo
  CC       mod_h2_la-h2_io_set.lo
  CC       mod_h2_la-h2_mplx.lo
  CC       mod_h2_la-h2_request.lo
  CC       mod_h2_la-h2_response.lo
  CC       mod_h2_la-h2_session.lo
h2_session.c: In function 'init_callbacks':
h2_session.c:524:52: error: passing argument 2 of 'nghttp2_session_callbacks_set_on_invalid_frame_recv_callback' from incompatible pointer type [-Werror]
     NGH2_SET_CALLBACK(*pcb, on_invalid_frame_recv, on_invalid_frame_recv_cb);
                                                    ^
h2_session.c:510:60: note: in definition of macro 'NGH2_SET_CALLBACK'
 nghttp2_session_callbacks_set_##name##_callback(callbacks, fn)
                                                            ^
In file included from h2_private.h:19:0,
                 from h2_session.c:26:
/usr/include/nghttp2/nghttp2.h:1713:1: note: expected 'nghttp2_on_invalid_frame_recv_callback' but argument is of type 'int (*)(struct nghttp2_session *, const union nghttp2_frame *, uint32_t,  void *)'
 nghttp2_session_callbacks_set_on_invalid_frame_recv_callback(
 ^
h2_session.c: In function 'h2_session_create_int':
h2_session.c:598:9: error: implicit declaration of function 'nghttp2_option_set_recv_client_preface' [-Werror=implicit-function-declaration]
         nghttp2_option_set_recv_client_preface(options, 1);
         ^
cc1: all warnings being treated as errors
Makefile:682: recipe for target 'mod_h2_la-h2_session.lo' failed
make[1]: *** [mod_h2_la-h2_session.lo] Error 1
make[1]: Leaving directory '/usr/src/mod_h2/mod_h2'
Makefile:449: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

Compiled with nghttp 0.7.15...

https://nghttp2.org/blog/2015/05/16/nghttp2-v1-0-0/ ...... https://nghttp2.org/documentation/package_README.html#migration-from-v0-7-15-or-earlier

If I understand you correctly, mod_h2 compiles with nghttp2 0.7.5, but not with v1.0.0. This is known, and beside the error you listed, there are other incompatible API changes in nghttp2 1.0.0.
mod_h2 will migrate to nghttp2 1.0.0 once curl has done so (mid June), as there are both dependent on the same nghttp2 version. If you see a need for an earlier change, please explain.
Dependencies and incompatible API changes always will suck...

yes, that is correct

Closing, issue seems to be solved now.