Removing ANSIBLE_ENABLE_TASK_DEBUGGER

ref: https://github.com/ansible/ansible-runner/issues/1327

+2


SingleThreadEventExecutor#scheduleRemoveScheduled no need to execute immediate

Hi there,
I think there is no need to wakeup ioHandler in this case.

Just like before lazyExecute will not wakeup ioHandler.

Netty version
4.2.0.Alpha3

I think the code is correct


Add systemic name for feature annotations

The tag systemic name should be located in the pkc and added as a column to the feature annotations.  Systematic name includes all targets hit by a probe. This should go for other headers in the pkc file. Check with Erin which ones may want to port over or if all should automatically for ease of use? Alternatively, allow the user to decide which data to append to feature data.
NOTE: generate_targ_notes in read pkc is not used at all and will need to be merged in with lookup table generation function to add to feature data.

Included in 2.99.2


refactor: make RegionOptions and MergeOutput serializable

I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
What's changed and what's your intention?
Make PickerOutput and MergeOutput serializable and deserializable. It's easy to transmit over the network in JSON format.
In order to use #[serde(skip)], the PR will make file_purger in FileHandleInner as Option type.

Make MergeOutput serializable and deserializable;
Make RegionOptions serializable, and we can marshal it into JSON string;

Checklist

[ ] I have written the necessary rustdoc comments.
[ ] I have added the necessary unit tests and integration tests.
[ ] This PR requires documentation updates.

@evenyag @WenyXu I have removed Serialize and Deserialize from PickerOutput and add the new modification of making RegionOptions serializable.

@coderabbitai review


smraposo-original.png missing

When you try to knit the paper, you get an error: "unable to open ../figures/smraposo-original.png"
It looks like it's missing from the figures directory

closed.
Mike
On Fri, Jul 22, 2016 at 1:29 PM, Robert X.D. Hawkins <
<EMAIL_ADDRESS>wrote:

When you try to knit the paper, you get an error: "unable to open
../figures/smraposo-original.png"
It looks like it's missing from the figures directory
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/StanfordPsych254/replication_project/issues/7, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABGul104Ib8UWKvRwsu1Lk0bBqUxKFOeks5qYSg9gaJpZM4JTGpc
.

Hmmm, I still don't see it when I pull -- maybe try pushing again in case it didn't go through?

Oh shoot, it actually looks like it's called sraposo-original.png in the folder, but smraposo-original.png in the project keys. I'll change the name of the figure to match the project key.


Barcode scanning

Overview
This PR implements the "quick scan" dialog functionality in the new user interface, as well as refactoring / further features for the "barcode actions" page.
The "scan barcode" dialog has now been refactored into a common component, with support for:

Camera scanning
USB scanning
Raw keyboard input

Related Issues

Closes https://github.com/inventree/InvenTree/issues/8323
Closes https://github.com/inventree/InvenTree/issues/8692
Closes https://github.com/inventree/InvenTree/issues/8703

TODO

[x] Playwright testing
[x] Improved documentation
[x] Prevent duplicate scans
[x] Fix issue deleting "last" item (or all items at once)

Future Work

Implement some actions

@sur5r @saschaludwig this should fix your scanning issues

Great improvement @SchrodingersGat! Looking very nice


the meaning of the sequence name of the output

Dear,
i want to know the meaning of the sequence name of output file. Such as the difference between  ">c0/f1p54/17291.1.1 SUBSTR:0,5481 SUBSTR:3919,1562" and ">c0/f1p54/17291.1.2 SUBSTR:0,5481 SUBSTR:1449,649".
Best regards.

Sorry for the very late answer... The IDs and description indicate how the read has been cut by proovread. There are two steps in the pipeline that can lead to cutting reads - chimera detection and trimming. The read at hand has been cut in both steps  - every time a cut happened the ID has been appended by a .X (1, 2, ... different pieces). The first SUBSTR:0,5481 indicates the coordinates of the first cutting operation in perl-style substr notation: start (0-offset), length, and with respect to how the read looked like at that stage of correction (NOTE that removing indels during correction slightly shifts coordinates between original and corrected reads). The second SUBSTR fields indicate the coordinates of the two high-quality pieces that were cut out from the read created during the first cutting operation, i.e. the trimming operation. One piece starts at 1449 and with length 649 bp, and a second high-quality piece starts at 3913, with length 1562.
Hope that helps!


Ensure the extension array in Helpers is indeed an array

Solves the fatal error when no options are set in the plugin, and ensures the $extension array exists.
Fixes #175

This PR checks if $extension is an array, which is always a string. So, I'm closing this. I've added the fix to #175 myself in https://github.com/plausible/wordpress/commit/8b349d3d1a4cab19d29051854a21f30b00703355


Add new ICL kwargs in eval.py and long_context yamls

Adds new kwargs included in the icl_refactor
Namely:

generation_kwargs
hf_parsing_map
hf_loading_vars

Required CoT criteria are there as well.

do_normalization
early_stopping_criteria

I also added fewshot_random_seed to be settable from the root level of the yaml, i.e. the same as max_seq_len.

👨🍳  great work Max! Do you think the long-context gauntlet would justify it's own readme, akin to EVAL_GAUNTLET.md?

👨🍳 great work Max! Do you think the long-context gauntlet would justify it's own readme, akin to EVAL_GAUNTLET.md?

I added it to the EVAL_GAUNTLET.md because I felt like it didn't deserve a full readme. Can redo if you'd like.


Loader

A loader when the API is busy fetching the data would look great.

Want to work on it.

That's cool! I had one additional request
Fix the font in your last pr, make it similar to theme of website.
And put the satellite svg in smooth motion on its place, like done by srijit's PR.

Sure!


[Feature] Repositories - Autolinks - Manage autolinks to external resources

https://docs.github.com/en/rest/repos/autolinks?apiVersion=2022-11-28

Testing autolinks: GH-123

GH-132A
GH-125B


↩ Displaying newlines and EOFs?

Per @mikeshulman's suggestion, perhaps it's useful to display newline characters and/or the end-of-file. I can think of a few choices:

Newline: ␤ ⏎ ↲ ↵
End of file: ␄ ⌁ ¶ ⏹

It still seems annoying to represent a span/range that marks the EOF, though. :thinking:

I don't quite understand what you mean by "represent"?

I don't quite understand what you mean by "represent"?

I believe the idea is to write down the range that marks the EOF as [len,len) where len is the size of the file/string. Suppose the whole file has exactly two characters. The EOF will be represented as [2,2).
The trouble is that this seems to break the range algebra, which assumes the following laws:

[i,j) and [j,k) are disjoint, but the disjoint union of them is exactly [i,k).
[i,l) contains [j,k) if and only if i <= j and k <= l.

Suppose the whole file is of length 2. The range [1,2) must contain the EOF as well, but then [1,2) and [2,2) are no longer disjoint. The end-of-file is different from newlines because newline sequences do occupy actual bytes.
One possibility is to use [len,len+1) for EOF. I haven't checked how other libraries/programs handle it...

Is there any situation in which one would want to talk about a range that includes EOF and also other characters?  If not, then I would be inclined to just treat EOF as a separate condition rather than any pair of offsets.

I think we solved the EOF. I now feel showing newlines might be useless. @mikeshulman Do you have other relevant requests? Or I'll close this issue. :-)

The EOF interface and display looks good to me.  Thanks!


Modify Makefile to copy package.json from root to all assignments

Interim fix for issue #84.

Small change but an important one, thanks!


[Question] Interpreter for multiple effects

I don't know if this belong here, but I ran into some issues implementing an interpreter that interprets two effects at a time.
I tried to understand if it was possible to do with reinterpret, and if any of the unlifting strategies were relevant, but I struggled to make sense of things. I generally find this lib easy to work with, but I think I lack some mental models for the interpreter implementations.
The solution I ended up with isn't very satisfying, is it possible to do the following in another way?
modelScenario :: forall a. [Event a] -> Model a
modelScenario events = runPureEff $ pureInterpreter scenario
  where
    scenario :: Eff (Event_Write a : Event_Read a : State [Event a] : '[]) (Model a)
    scenario = do
      forM_ events DomainThingy.writeEvent
      DomainThingy.getModel

pureInterpreter :: forall a b es. Eff (Event_Write a : Event_Read a : State [Event a] : es) b -> Eff es b
pureInterpreter = State.evalState [] . interpretRead . interpretWrite
  where
    interpretWrite :: Eff (Event_Write a : Event_Read a : State [Event a] : es) b -> Eff (Event_Read a : State [Event a] : es) b
    interpretWrite = interpret $ \_ -> \case
      DomainThingy.WriteEvent e -> State.modify (e :)
    interpretRead :: Eff (Event_Read a : State [Event a] : es) b -> Eff (State [Event a] : es) b
    interpretRead = interpret $ \_ -> \case
      DomainThingy.ReadEvents -> State.get

If you want to hide State [Event a] you can use inject, but you'll need additional constraint Subset

@Nexmean is right, inject works. Unfortunately at the moment you will need to add the appropriate Subset constraint because it only works for fully known lists.
I have a plan to generalize inject so that it automatically resolves for lists that share a common suffix, so then you will be able to write
hideState :: Eff (Event_Write a : Event_Read a : State [Event a] : es) r -> Eff (Event_Write a : Event_Read a : es) r
hideState = inject

and use this to hide the State without the need of Subset.

You can also write reinterpret2 that does what you want yourself.
reinterpret2
  :: (DispatchOf e1 ~ Dynamic, DispatchOf e2 ~ Dynamic)
  => (Eff handlerEs a -> Eff es b)
  -> EffectHandler e1 handlerEs
  -> EffectHandler e2 handlerEs
  -> Eff (e1 : e2 : es) a
  -> Eff            es  b
reinterpret2 runHandlerEs handler1 handler2 m = unsafeEff $ \es -> do
  (`unEff` es) . runHandlerEs . unsafeEff $ \handlerEs -> do
    (`unEff` es) $ runHandler (Handler handlerEs handler2)
                 $ runHandler (Handler handlerEs handler1)
                 $ m

You'll need to import Effectful.Internal.Monad for this though.
Perhaps it's worth to include this in the library for up to reinterpret5 :thinking:

@jonathanmoregard is reinterpret2 what you were looking for?

I haven't tried it out, but it looks like it!
This turned out to not be needed atm, but I can repro where I was if it helps you.
Adding reinterpretN for n upt o 5 seems like a good idea

I decided to go with the route of generalizing inject for now as it seems cleaner and is more general than reinterpretN variants.


bot_ai already_pending_upgrade(upgrade_id) fails when using certain upgrade_ids

I called bot_ai already_pending_upgrade(UpgradeId.ANIONPULSECRYSTALS) and the following error occurs:
File ".../sc2/bot_ai.py", line 366, in already_pending_upgrade
    creationAbilityID = self._game_data.upgrades[upgrade_type.value].research_ability.id
AttributeError: 'NoneType' object has no attribute 'id'

Below is the game_data for the specific resource:

upgrade_id: UpgradeId.ANIONPULSECRYSTALS   (this is a value upgrade_id)
value: 112  (this is the correct upgdrade id value)
object data: UpgradeData(AnionPulseCrystals - research ability: None, Cost(0, 0))

It would appear that the associated research ability" for this upgrade is missing ("None" as per above)

I believe this upgrade is not in the game.
If you are trying to research phoenix range upgrade, this should be the correct upgrade:
https://github.com/Blizzard/s2client-api/blob/d9ba0a33d6ce9d233c2a4ee988360c188fbe9dbf/include/sc2api/sc2_typeenums.h#L798
https://github.com/Dentosal/python-sc2/blob/8a8f5c5517f84fc2b5b88f27b1235c64dd75fd5a/sc2/ids/upgrade_id.py#L106


[ConsoleMethods.simulate_queue_worker] Honor :deliver_on

Previously, queue items that had :deliver_on in them were executed right away by simulate_queue_worker, since the only thing it filters by is queue_name.
This is problematic for things like importing zip files for automate domains as it will upload file, and then queue it for deletion a day later:

https://github.com/ManageIQ/manageiq-ui-classic/blob/7b0bda1/app/services/automate_import_service.rb#L44-L50
https://github.com/ManageIQ/manageiq-ui-classic/blob/7b0bda1/app/services/automate_import_service.rb#L94

Only when doing this with simulate_queue_worker, it deletes it right away, and in many cases doesn't give it a chance to get processed before it is deleted.
Honoring the :deliver_on attribute fixes that issue.
Steps for Testing/QA

Start a bin/rails console and run simulate_queue_worker
Go to Automation -> Embedded Automate -> Import / Export
Import "some kind of zip" (the .zip shouldn't matter, but if you want legit one, you probably can use this)

Before this change, it will flash an error stating the file can not be found.
After this change, it will upload the file and allow you to pick your automate domains to import.

@miq-bot assign @agrare
@miq-bot assign @Fryguy
Since the both of you worked on this recently, hoping you can give this a look.

I think I have a bug with this query, as it currently isn't picking up work.  For now, going to put this as WIP.

I think master is failing at the moment with some date issue.


we need to verify xboost performance after update the default configs

we need to verify xboost performance after update the default configs, verify #226

updated the perf for pyspark+xgboost in #252 , will draft a follow up pr to add scala version performance


Did some stuff

Did some stuff with the README.md file and i think it looks ok, i will continue to improve it and in my opinion it is nowhere near done but want to see what things you would like changed.
(There is no longer a massive penny head because it looked weird, you can change that if you want for example.)

,
I am working on presenting the bot invite link better while not obstructing the whole README too.


It is impossible to switch units from meters to kilometers

I tried switching the units of the earth to km using by writing
planet3D('Earth','km')
on Matlab but it doesn't work as it keeps the units in meters

The opts input is a struct. Something like
plot_opts.units = 'km'
planet3D('Earth',plot_opts)

should work.

Thank you
Il giorno mer 23 nov 2022 alle 15:54 Tamas Kis @.***>
ha scritto:

Closed #2 https://github.com/tamaskis/planet3D-MATLAB/issues/2 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/tamaskis/planet3D-MATLAB/issues/2#event-7878042809,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4LHQDSIELLZG6FXZK73L4DWJYV3LANCNFSM6AAAAAASJBJEWQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Use https://s3.amazonaws.com/bbop-sqlite/hp.db.gz as an example S3 download, not https://s3.amazonaws.com/bbop-sqlite/hp.db

And/or encoutrage people to look at the manifest at https://s3.amazonaws.com/bbop-sqlite
Although, for some ontologies, there are a lot of objects other than the semantic sql database file.

solved by https://github.com/INCATools/semantic-sql/pull/78


Lecture 7 - Slide 27 - grammar

"If you used BERT to make a medical diagnosis based on doctors notes" -> "If you used BERT to make a medical diagnosis based on doctors' notes"

Thanks. 1 point


feat(few-shot-examples): add new chromadb flow to get similar examples

This PR adds the following:
Major:
New ChromaDB collection that includes example questions and corresponding queries. It works as follows:

It creates a collection called examples/ where all the example questions are indexed and their corresponding query attached as metadata
A new function generate_examples queries the collection and outputs a structured prompt which can be embedded into a template prompt

A practical example. Given a file q1.sparql:
# Who am I?
SELECT ?me

The ChromaDB collection examples/  will store the question Who am I? and attach SELECT ?me as metadata. When calling the generate_example function on a question (Who am I working with?), ChromaDB will look for the closest question(s) and return the following output:
Question:
Who am I?
Answer:
SELECT ?me

Minor

Renamed default collection to schema instead of test
Added function to import examples (get_sparql_examples) to io.py as it seemed more fitting there
Updated dependencies to have prefect working (see #18 for longer-term solution)
Updated ChromaDB API functions

Thank you for all the comments and suggestions @cmdoret 🙌
Summary of relevant or open changes
Based on your suggestion on making the example parser more flexible:

I created a parse_sparql_example function that works with a text stream in aikg/utils/io.py
I added get_sparql_examples as a task in aikg/flows/chroma_examples.py as you suggested

Clarification 1
clarification/question: the newget_sparql_examples function works slightly differently compared to before.

Before: output a list with a single Document
After: output a list with multiple Document one per example

Because of this in chroma_build_examples_flow I had to loop through the output to be able to batch
# aikg/flows/chroma_examples.py
# L110-122

    # Create subject documents
    docs = get_sparql_examples(
        dir=chroma_input_dir,
    )

    # Vectorize and index documents by batches to reduce overhead
    logger.info(f"Indexing by batches of {chroma_cfg.batch_size} items")
    embed_counter = 0
    for doc in docs:
        for batch in chunked(doc, chroma_cfg.batch_size):
            embed_counter += len(batch)
            index_batch(batch)
    logger.info(f"Indexed {embed_counter} items.")

Clarification 2
clarification/question: for https://github.com/sdsc-ordes/kg-llm-interface/pull/21#pullrequestreview-1843605495 should I directly change the sparql_template to match the one we used or would you like to add another template so that we have one with and one without examples?

clarification 1: If docs is a list of Documents, we should be able to loop directly on chunk(docs):

In [2]: from more_itertools import chunked

In [3]: docs = [{'data': i, 'meta': v} for i, v in enumerate(['red', 'blue', 'green'])]

In [4]: docs
Out[4]:
[{'data': 0, 'meta': 'red'},
 {'data': 1, 'meta': 'blue'},
 {'data': 2, 'meta': 'green'}]

In [5]: for batch in chunked(docs, 2):
   ...:     print(f"---\nBATCH: {batch}")
   ...:
---
BATCH: [{'data': 0, 'meta': 'red'}, {'data': 1, 'meta': 'blue'}]
---
BATCH: [{'data': 2, 'meta': 'green'}]

clarification 2: Indeed, examples should be optional. We can change the template directly, however we should set a default value for the examples parameter of generate_sparql, such that the user can ignore it and it will just insert nothing. Does that make sense?.

Also rather than having the Examples: header in the template, it should probably be inserted dynamically if examples is not empty. Otherwise, not providing examples will result in an Example: header followed by another header.


Position right and widescreen plugin not working together

I am trying to use the menu positioned right while also using the widescreen plugin, so that it's open by default at a larger media query. This doesn't seem to be working. I get a blank area on the left where the menu would normally be, instead of being open on the right.
The margin-left on mm-slideout should be a margin-right when position right is used. Am I missing something?

The widescreen add-on will always assume the menu to be positioned on the left.
I'll see if I can force the menu to be positioned on the left in the next version.
Thanks for pointing out the issue.

Should be fixed in the current version.


Failed to skeletonize the mesh

Hi, MeshParty Team.
I am skeletonize the mesh provided by MeshParty. But many resulted skeleton vertices are on the surface of the mesh instead of inside the mesh. Are there any extra steps such as parameters I have missed here? Many Thanks here.
The test mesh is from "precomputed://gs://neuroglancer-public-data/kasthuri2011/ground_truth",
from meshparty import trimesh_io
from meshparty import trimesh_vtk
from meshparty import skeleton, skeleton_quality, skeletonize
import os
from pyvista import examples
import trimesh
import numpy as np
def testLoad():
    meshFilePath="../data/test.obj"

    meshA = trimesh.load_mesh(meshFilePath)

    if (os.path.exists(meshFilePath)):
        print(f"{meshFilePath} does exist")

    mesh = trimesh_io.Mesh(vertices=meshA.vertices, faces=meshA.faces)
    mesh_actor = trimesh_vtk.mesh_actor(mesh, color=(1,0,0),opacity=0.5)
    trimesh_vtk.render_actors([mesh_actor])
    sk = skeletonize.skeletonize_mesh(mesh)
    vs = np.asarray(sk.vertices)
    np.savetxt("../output/vs.xyz",vs)
    return

This is an intentional feature of the approach/algorithm.  I've written an extensive discussion on it in the documentation
https://meshparty.readthedocs.io/en/latest/guide/skeletons.html
If having a centered skeleton is important for your use case, there is an approach to move the skeletons half the SDF distance perpendicular to the mesh surface and then smooth the result, this works OK, but if your use case really demands precise centering than a different more computationally intensive skeletonization procedure might be a better way to go.  Voxel based skeletonization is possible but is expensive when not done in bulk, and mesh shrinking approaches work well but don't guarantee a tree like topology, so again.. depends on what you are trying to do with it.

@fcollman , thanks for your reply.
Yes, I am interesting in both the topology and  precise centering. Regarding to the toplogy, I have used the same code but with a more complex mesh. It turns out some branches and part of the main branches missed.

Any thoughts on possible causes here? Thanks.

This has to do with the parameters of the algorithm, namely the invalidation_d.  The defaults were designed for mammalian neurons assuming mesh vertices were in nm units.  If you have a different mesh you will likely need to adjust a lot of parameters to make it work right for you, and so you'll have to read the documentation about how the algorithm works to understand how they should be tuned.
In this case, you should turn down the invalidation distance.. which should be set to on order the distance 'around' the main branches you are interested in skeletonizing in the units of the mesh vertices.

@fcollman , Thanks for your advice. I will have a good read on the documentation.

@fcollman , after your tip. I realised that the input mesh has max distance to the surface roughly around 12 meters. By resetting the invalidation_d down to much smaller parameters. Topology can be captured without loss in this case. Many Thanks again.

excellent, there are some more computationally intensive but potentially more accurate ways to estimate the caliber and curvature  of the mesh at each point which can help you create a centered mesh, I gave a sketch of them conceptually in the documentation but let me know if you need help running those.


[test] Fix flaky test CloseableThreadLocalTest::testClose

Fix flaky test CloseableThreadLocalTest::testClose

This test fails on JDK8 often. The current logic assumes that tasks will
get allocated to all the threads but this may not be always the case. Hence,
use the number of threads that actually did some work in an assertion.
How was this PR tested?

Running internal CI
Does this PR introduce any user-facing changes?

[X] No. You can skip the rest of this section.
[ ] Yes. Make sure to explain your proposed changes and call out the behavior change.

Not a correct fix.

Not a correct fix.

Updated with correct fix.

Thanks for the review, @nisargthakkar. Could you please take another look and see if this looks good?


Programmatic use: validate anchors in other files (like CLI)

With the CLI it is possible to validate anchor references to other files: [some link](another-file.md#some-anchor).
This is because the code path for the CLI accepts multiple files. However, the code path for programmatic use can only accept one file; as such it does not validate external anchors like the CLI.
It would be nice to be able to pass a set of files in for programmatic use. For example, my current situation looks like this:
const processor = remark().use(validateLinks);

fastGlob('{,!(.git|node_modules)/}**/*.md')
  .then(paths => Promise.all(
    paths.map(p => vfile.read(p, 'utf8'))
  ))
  .then(vfiles => Promise.all(
    vfiles.map(file => processor.process(file))
  ));

As you can see, I already have a collection of files - and I would like to validate that cross references between files are valid. Is this possible today in a way that I'm not seeing?

@DesignByOnyx I'd recommend using unified engine for handling globs of files programmatically.
Using a combination of the processor, plugins, and files can get the files processing through remark validate links the same way as the CLI would.

Thank you! That ended up working perfectly. For anybody else who may come across this, I was able to change my existing code (above) to the following (with virtually no other changes to my code):
    engine({
      processor: remark(),
      files: ['!(scripts|node_modules|.git)/**/*.md'],
      plugins: ['remark-validate-links'],
    }, (err, code, context) => {
      if(err) return reject(err);
      resolve(context.files);
    });


Image card named Ganpatipule does not have an image to its background.

there is no image in background as you see.

can you assign this issue to me? I will solve it ASAP. Also add hacktoberfest labels to the issue, please.

I'm creating a PR regarding this issue check PR/no. #257. this is already solved my me.


Switch lang tabs clears any in progress solutions

Because there's only one instance of the editor. Should be simple enough to store the solutions in JS vars.

Related to #120


App freezes when using open file dialog

I was developing an app on linux. After some time I switched to windows and now when i use open file dialog, the whole app freezes.

Does it just freeze for like 5 seconds? Or does it freeze permanently?
Does it freeze every time? Or just sometimes?

I have noticed a several second freeze that only happens occasionally.

It freezes everytime and i waited for about 2-3 minutes before terminating it. It didnt unfreeze

Does it just freeze for like 5 seconds? Or does it freeze permanently?
Does it freeze every time? Or just sometimes?

I have noticed a several second freeze that only happens occasionally.

It freezes everytime and i waited for about 2-3 minutes before terminating it. It didnt unfreeze

If you are able to create a simple test case that always freezes that would be helpful.  It happens rarely enough for my test case (ControlGallery) that I can't really debug it.

If you are able to create a simple test case that always freezes that would be helpful. It happens rarely enough for my test case (ControlGallery) that I can't really debug it.

When I call this function it just freezes
Here is a video that shows what happens:
https://github.com/modern-forms/Modern.Forms/assets/96019707/dd7f8b20-5370-4bcc-8fa9-74deba49c5b7

Ah, the old "sync over async" deadlock:
https://devblogs.microsoft.com/pfxteam/await-and-ui-and-deadlocks-oh-my
I'm not sure how to work around this currently.  Likely we probably need to add a sync version for people to easily use.
In the meantime, you will need to use await to prevent the deadlock.
Example:
https://github.com/modern-forms/Modern.Forms/blob/main/samples/ControlGallery/Panels/FileDialogPanel.cs#L24-L41

This works, but how can i tell it to wait until I hit OK in file explorer. Currently it doesn't wait.
https://github.com/modern-forms/Modern.Forms/assets/96019707/3ede2578-2793-4e59-ad9b-5c579bdcdf23

I'm not sure what you mean by "it doesn't wait".
The error you are hitting looks like https://github.com/modern-forms/Modern.Forms/issues/40.
I am guessing you are using a NuGet package rather than building Modern.Forms from source?
You will likely want to build from source to ensure you have the latest fixes.

I'm not sure what you mean by "it doesn't wait".
The error you are hitting looks like #40.
I am guessing you are using a NuGet package rather than building Modern.Forms from source?
You will likely want to build from source to ensure you have the latest fixes.

The behavior of the open file dialog should be this:
Open Existing -> wait until i select file and click OK -> *open editor (the other window) -> load data -> etc...
Currently when i hit Open Existing it opens the file dialog but also opens the editor

Ok. so i was a problem on my end. I didn't put the open file dialog where it needed to be.
In my case i had to call OpenFileDialog before I opened my other form.
Hope this helps :D


Test Lukas' environment

[ ] Test in Lukas' environment
[ ] Test colab notebook sharing
[ ] Review for workflow

Docker doesn't work on my PC. It requires Win Pro.

Shouldn't matter too much, you don't need it for local execution. This will become apparent in the new README, hopefully. Did you try setting up the environment/using it, and running shared colab notebooks?

Fixed virtualenv check, colab works fine.


Strange green box artifact on Nexus 6P when activating the Animation demo

On a Nexus 6P, in portrait or landscape, open gallery, and scroll down to Animation. Tap into Animation. Tap the floating-action-button to trigger the animation.
Notice the flashing green box artifact that flashes while the animation is running.
See it in action: https://www.youtube.com/watch?v=k6JBlc2ekdU

There was another report of this.  @chinmaygarde believed it was likely gpu specific.  Just have to find the dupe.

Dupe of https://github.com/flutter/flutter/issues/5898


Error when using generated prisma client: const dmmf = JSON.parse(dmmfString)  SyntaxError: Unexpected token in JSON

I have this schema:
CREATE TABLE IF NOT EXISTS organizations (
  id TEXT,
  name TEXT,
  profile JSONB,
  registered DATE,
  logo_image TEXT,
 verification_code SERIAL,
 verified BOOLEAN,
 PRIMARY KEY (id)
);

and get this model after running prisma2 introspect
model organizations {
  id                String    @id
  logo_image        String?
  name              String?
  profile           String?
  registered        DateTime?
  verification_code Int
  verified          Boolean?
}

after running prisma2 generateand I execute the following code:
const { PrismaClient } = require("@prisma/client");
const prisma = new PrismaClient();

async function main() {
  const x = await prisma.organizations.create({
    data: {
      id: "some_id",
      verification_code: 123345
    }
  });
  console.log(x);
}

main();

I get the following error:
const dmmf = JSON.parse(dmmfString)
                  ^
SyntaxError: Unexpected token
 in JSON at position 6232
    at JSON.parse (<anonymous>)
    at Object.<anonymous> (~/prisma/node_modules/@prisma/client/index.js:3989:19)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Module.load (internal/modules/cjs/loader.js:599:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
    at Function.Module._load (internal/modules/cjs/loader.js:530:3)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:22:18)
    at Object.<anonymous> (~/prisma/index.js:1:26)

I can confirm this fails, with alpha.820 it is this error message::
C:\Users\Jan\Documents\throwaway\1083>node index.js
(node:17724) UnhandledPromiseRejectionWarning: Error:
Invalid `prisma.organizations.create()` invocation in
C:\Users\Jan\Documents\throwaway\1083\index.js:5:40

Error occurred during query execution:
ConnectorError(ConnectorError { user_facing_error: None, kind: QueryError(Error { kind: FromSql(3), cause: Some(WrongType { postgres: Type(Jsonb), rust: "core::option::Option<alloc::string::String>" }) }) })
    at PrismaClientFetcher.request (C:\Users\Jan\Documents\throwaway\1083\node_modules\@prisma\client\index.js:89:17)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:17724) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:17724) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

@xuxusheng Can you please share your datamodel with us? Are you also using Json or JSONB types in your database?

I encountered this problem during the upgrade of prisma2.0.0-preview019 to 2.0.0-preview022，The database is automatically generated by Prisma。
model User {
  id        String     @default(cuid()) @id
  email     String     @unique
  name      String     @unique
  password  String
  isAdmin   Boolean    @default(false)
  posts     Post[]
  types     PostType[]
  tags      PostTag[]
  createdAt DateTime   @default(now())
  updatedAt DateTime   @updatedAt
}

model Post {
  id          String    @default(cuid()) @id
  title       String?
  content     String?
  author      User
  type        PostType?
  tags        PostTag[]
  publishedAt DateTime?
  createdAt   DateTime  @default(now())
  updatedAt   DateTime  @updatedAt
}

model PostType {
  id        String   @default(cuid()) @id
  name      String
  posts     Post[]
  user      User
  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt
}

model PostTag {
  id        String   @default(cuid()) @id
  name      String
  posts     Post[]
  user      User
  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt
}

I am unable to reproduce this with the schema you have shared. Can you please share a minimal reproduction of your problem in a Git repository.
Also, maybe open a new issue, as your problem is unrelated to this issue.

Thanks a lot for reporting 🙏
This issue is fixed in the latest alpha version of @prisma/cli.
You can try it out with npm i -g @prisma/cli@alpha.
In case it’s not fixed for you - please let us know and we’ll reopen this issue!


About the optimization of pascal_voc.py

def load_pascal_annotation(self, index):
    imname = os.path.join(self.data_path, 'JPEGImages', index + '.jpg')
    im = cv2.imread(imname)
    h_ratio = 1.0 * self.image_size / im.shape[0]
    w_ratio = 1.0 * self.image_size / im.shape[1]

    label = np.zeros((self.cell_size, self.cell_size, self.num_class + 5))
    filename = os.path.join(self.data_path, 'Annotations', index + '.xml')
    tree = ET.parse(filename)
    objs = tree.findall('object')

The role of this paragraph is to read the length and width of each picture, but there is such information in the xml of the picture, test it, if rewritten into the following code
def load_pascal_annotation(self, index):
    label = np.zeros((self.cell_size, self.cell_size, self.num_class + 5))
    filename = os.path.join(self.data_path, 'Annotations', index + '.xml')
    tree = ET.parse(filename)
    size=tree.find('size')
    h_ratio = 1.0 * self.image_size / int(size.find('height').text)
    w_ratio = 1.0 * self.image_size / int(size.find('width').text)
    objs = tree.findall('object')

The label information of 5011 pieces of cyclically read training data will change from 17 seconds to 0.95 seconds.

Yes, I didn't consider this.
Thank you for your contribution. Actually, you can 'pull requests' the modified code directly.

I have completed 'pull requests'


NorESM2-LM e2e DTR run fails downscaled validation on polar values out of range

Workflow : https://argo.cildc6.org/archived-workflows/default/f6dc456f-daa0-4d11-81db-e84e0c1d6d41?nodeId=e2e-noresm2-lm-dtr-ql8ds-264390888
Log :
assert (
AssertionError: diurnal temperature range max is <xarray.DataArray 'dtr' ()>
dask.array<nanmax-aggregate, shape=(), dtype=float32, chunksize=(), chunktype=numpy.ndarray> for polar northern latitudes

The max over southern and non polar values is 118.89946.

@emileten I think we can close this now?

closed due to switch to additive approach for tasmin

@emileten I think we can close this now?

yes thanks @dgergel!


Replace deprecated ioutil funcs with io

ioutil has been deprecated and equivalent methods are in the io package now.

Codecov Report
Base: 70.80% // Head: 70.76% // Decreases project coverage by -0.03% :warning:

Coverage data is based on head (bc6564e) compared to base (cf2f07f).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #184      +/-   ##
==========================================
- Coverage   70.80%   70.76%   -0.04%
==========================================
  Files          26       26
  Lines        2699     2699
==========================================
- Hits         1911     1910       -1
- Misses        665      666       +1
  Partials      123      123

Impacted Files
Coverage Δ

middleware.go
85.24% <100.00%> (ø)

auth.go
88.53% <0.00%> (-0.64%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[BUG] - refinery start leads to gitpython error

Describe the bug
refinery start leads to this error, right after pip installing 🥺:
Traceback (most recent call last):
  File "/Users/adrien/miniconda3/bin/refinery", line 5, in <module>
    from refinery.cli import main
  File "/Users/adrien/miniconda3/lib/python3.8/site-packages/refinery/cli.py", line 6, in <module>
    from git import Repo
  File "/Users/adrien/miniconda3/lib/python3.8/site-packages/git/__init__.py", line 6, in <module>
    from repository import Repository, InvalidRepositoryError
ModuleNotFoundError: No module named 'repository'

Desktop (please complete the following information):

OS: macOS Monterey 12.4

Yup, I can start from a fresh env. Gimme a few hours :)

Looks like that did it 🎈
However I'm getting some Docker errors below, and the UI: http://localhost:4455/app/ link doesn't seem to be working. Is this expected? Very possible that it is! I haven't delved too deeply into the documentation 😊
(base) adrien@Adriens-MacBook-Pro ~ % conda create -n kern
Collecting package metadata (current_repodata.json): done
Solving environment: done

## Package Plan ##

  environment location: /Users/adrien/miniconda3/envs/kern

Proceed ([y]/n)?

Preparing transaction: done
Verifying transaction: done
Executing transaction: done
#
# To activate this environment, use
#
#     $ conda activate kern
#
# To deactivate an active environment, use
#
#     $ conda deactivate

(base) adrien@Adriens-MacBook-Pro ~ % conda activate kern
(kern) adrien@Adriens-MacBook-Pro ~ % pip install kern-refinery
DEPRECATION: Configuring installation scheme with distutils config files is deprecated and will no longer work in the near future. If you are using a Homebrew or Linuxbrew Python, please see discussion at https://github.com/Homebrew/homebrew-core/issues/76621
Collecting kern-refinery
  Using cached kern_refinery-1.0.2-py2.py3-none-any.whl (18 kB)
Collecting wasabi
  Using cached wasabi-0.9.1-py3-none-any.whl (26 kB)
Requirement already satisfied: GitPython in /opt/homebrew/lib/python3.9/site-packages (from kern-refinery) (3.1.27)
Requirement already satisfied: requests in /opt/homebrew/lib/python3.9/site-packages (from kern-refinery) (2.27.1)
Requirement already satisfied: gitdb<5,>=4.0.1 in /opt/homebrew/lib/python3.9/site-packages (from GitPython->kern-refinery) (4.0.9)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in /opt/homebrew/lib/python3.9/site-packages (from requests->kern-refinery) (1.26.8)
Requirement already satisfied: certifi>=2017.4.17 in /opt/homebrew/lib/python3.9/site-packages (from requests->kern-refinery) (2021.10.8)
Requirement already satisfied: charset-normalizer~=2.0.0 in /opt/homebrew/lib/python3.9/site-packages (from requests->kern-refinery) (2.0.10)
Requirement already satisfied: idna<4,>=2.5 in /opt/homebrew/lib/python3.9/site-packages (from requests->kern-refinery) (3.3)
Requirement already satisfied: smmap<6,>=3.0.1 in /opt/homebrew/lib/python3.9/site-packages (from gitdb<5,>=4.0.1->GitPython->kern-refinery) (5.0.0)
Installing collected packages: wasabi, kern-refinery
  DEPRECATION: Configuring installation scheme with distutils config files is deprecated and will no longer work in the near future. If you are using a Homebrew or Linuxbrew Python, please see discussion at https://github.com/Homebrew/homebrew-core/issues/76621
  DEPRECATION: Configuring installation scheme with distutils config files is deprecated and will no longer work in the near future. If you are using a Homebrew or Linuxbrew Python, please see discussion at https://github.com/Homebrew/homebrew-core/issues/76621
DEPRECATION: Configuring installation scheme with distutils config files is deprecated and will no longer work in the near future. If you are using a Homebrew or Linuxbrew Python, please see discussion at https://github.com/Homebrew/homebrew-core/issues/76621
Successfully installed kern-refinery-1.0.2 wasabi-0.9.1
(kern) adrien@Adriens-MacBook-Pro ~ % refinery start
ℹ Cloning from code-kern-ai/refinery into repository refinery
./start: line 21: docker: command not found
./start: line 22: docker: command not found
./start: line 23: docker: command not found
./start: line 29: docker-compose: command not found
UI:           http://localhost:4455/app/
Minio:        http://<IP_ADDRESS>:7053
MailHog:      http://localhost:4436/

great that this fixed this issue. Now for the error messages, it seems you don't have docker installed (or at least it's not recognized by bash). Its used to run the containerized application. Could you check and install docker desktop

sweeeet, that worked 💓
i had docker desktop downloaded, but hadn't gone through the installation process. thanks for the tip!


 Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box.

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you check the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package-lock.json
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/gatsby
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/gatsby-plugin-offline
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /var/folders/0k/b4kl43997r90vwdccslxdvnm0000gn/T/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR!


CreateSrsMedia.ps1 script link fails

The link for the CreateSrsMedia.ps1 link is currently broken.
Can be corrected/updated?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 6f8b204f-9650-d268-8566-7a75ba0a1b6a
Version Independent ID: 9a963e63-6716-7522-8abe-c8a407d3a46d
Content: Configure a Microsoft Teams Rooms console - Microsoft Teams
Content Source: Teams/rooms/console.md
Service: msteams
GitHub Login: @LanaChin
Microsoft Alias: v-lanac

@kevincallanan  Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Hi @kevincallanan, thank you for your feedback.
I tried 1 minute ago, and it worked for me. Could you kindly try again?

This is working now, the link now downloads the version 1.6.0 Thanks!

Trying to download the script is giving:
404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.

Still getting 404 error today.

@dstrome could you kindly help here? Thanks!

Came here to report on the link and the script itself getting http 404 errors, however just now I've tested both and they are working.
Thanks for you and your teams' work on this

@maxpeet thanks!

Same issues again, getting a 404 when trying to access the link to the script from the MS documentation...any help @dariomws

This is still an issue. How is it possible that you can't successfully and permanently host one powershell script?

@dstrome could you kindly help here? Thanks!

The script should be available again. I apologize for the inconvenience. Unfortunately, when the script is updated, there's an interval where it's unavailable as the backend system goes through various compliance, security, and other checks.


How to drag points on chart ?

Is this possible to drag points on chart and update data with yours plugin ?

No, only annotations can be dragged with the mouse using this plugin.


Idea: ScrollerFactory() that allows alternate template type and renderer

I like this vscroll-native example.  But I would like to use something different than innerHTML in createItemElement.
createItemElement is a fine default, but there would be some advantages if something like uhtml or lithtml were an option. (I prefer uhtml, but I am sure lithtml and others could be popular too.)
What if there was ScrollerFactory that is provided the desired renderer and returns a Scroller class with the applicable Template type for the renderer chosen?

The existing Scroller.prototype.createItemElement would be replaced with a createItemElement<TEMPLATE> that is provided to the ScrollerFactory and would have the same interface.  But it would dictate the TEMPLATE type for the renderer used.
As a default, the provided createItemElement could be the same implementation as the existing Scroller.prototype.createItemElement, where the TEMPLATE generic would be set to the existing Template type.

Is this something you'd consider?  If so, I am happy to see if this idea works and create a pull request. (I may have some flaws in my current thinking/idea, but my hope is that its mostly feasible and that I can work out problems if I pursue it.)  I just want to proceed if the idea is not valued.
Alternatively I could use vscroll-native as an example and create my own implementation that uses my preferred renderer.  But it feels like there is opportunity for reuse if there were a ScrollerFactory that provided the desired renderer.

@darcyparker DOM-related operations is one of the weak points through the vscroll infrastructure. I tried to make the implementation as simple/rough as possible, relying on browser year-to-year growing performance rather than lib performance. The idea of pluggable DOM-engine is very good. Moreover, I already extracted the most part of the DOM-related logic into a separate class inside the core: vscroll/src/classes/domRoutines.ts. And I planned to make it replaceable: a consumer (vscroll-native) should be able to override this class via config of the Workflow super-entity. Currently such approach is done for the Adapter reactive props, which are configurable at the Datasource factory level: core DS factory -> consumer specific DS. The Workflow should receive domRoutines configuration.
1) Routines is not finished yet, for example items rendering is not under its control, and this relates to what you want to change: hiding items in vscroll-native is served by render process in vscroll. Both operations can be moved to Routines and Routines could be replaced by consumer. The argument of createItemElement is an instance of Item class which has Routines instance on it. As you see, we can't separate these two operations and replace one of it (core relies on hiding!), but we can try to gather them in a single place and provide a consumer-core overriding mechanism to replace them both. This is one point of the createItemElement problem.
2) Another one is that you want to give an option to change a consumer DOM-related logic, which is not connected with the core. This is VERY good idea, but before discussing the details, let's think about scoping. The logic we are going to deal with is the most low-level across the project, and my guess the consumer layer is the best place that matches it, so it should not leak into the end app. Let me put here the vscroll introduction image:

So your suggestion could be treated as a factory of native consumers. Setting up such a factory would require good qualifications from the end app devs. My idea is not to give in the hands of the end app devs such fundamental pieces as rendering implementation, even if it's optional. Maybe it will be better to

implement the best approach and replace the existed one inside vscroll-native
develop all rendering options inside one (vscroll-native) consumer and provide simple switching setting
turn vscroll-native into a consumer factory, but publish each stand-alone implementation as a separate library with no DOM-config (1 extra dependency)
forget about vscroll-native and develop completely separate vscroll-consumer with its own unique rendering (no extra dependency)
...

I will be glad to participate whichever way you/we choose.

My idea is not to give in the hands of the end app devs such fundamental pieces as rendering implementation, even if it's optional. Maybe it will be better to
I agree.

With regards to the 4 options:

The 'best approach' is subjective... and could change
developing all rendering options inside one consumer seems overkill
I like the idea of turning vscroll-native into a consumer factor and publish each stand alone implemention.
I also like the idea of forgetting about vscroll-native... but I like the previous choice because I think the interface for a Template and render can satisfy all render/template cases I can think of... and it would keep things DRY to have a the vscroll-native consumer factory.

The popular choices for a renderer are likely uhtml, lit-html et al... and there could be more.

I am going to chew on your other comments... but also interested in helping.

@darcyparker My other comments were about the createItemElement method can't be replaced entirely due to render-hiding-showing logic that is scattered over the core and consumer; additional efforts are needed to put it in a single configurable DOM Routines class (which is not configurable for now, and more efforts are needed to make it configurable).
But if you don't want to change these particular operations (btw they are required by the core doc), we may start the Factory developing. From the one hand, I'd be glad to see something like core Datasource factory (a parametrized function returning extended class); from the other hand, we may move toward ts abstract class or native mixins. I think, since the project is quite small, it should be not a problem to update the infrastructure. The more important is to implement a new renderer...
Once we have two different renderers (default and 1 new), we'll be able to generalize the Scroller entity, taking into account their specificity. The entry (and the only important) point is the Workflow run callback implementation, which is wrapped with the wf-storage:
https://github.com/dhilt/vscroll-native/blob/d422f6806182e5a174f9a3160a137701b88526ed/src/vscroll-native.ts#L43
So the updateViewport must satisfy the requirements listed in the doc. The updateViewport method calls createItemElement in the end. That's how the default Scroller class is written. Another implementation of the Scroller class might not contain createItemElement at all, it just should provide correct updateViewport method.
Adding you to the repository collaborators for not to waste time. We may continue the discussion by the code.

@dhilt - Thanks for adding me as a repository collaborator.
I understand what you mean about the render hiding logic being scattered over core and consumer.  I have some thoughts but they aren't fully formed.
I can get started with the factory development... (likely Monday).
With regards to the Datasource factory, I am open to an abstract ts class or native mixins too.  But you're right, that if a factory is  created, and later like another approach its probably not too hard to update.  As a side question, would you be open to adding something like (index: number) => AsyncIterable<T> | (index: number) => Iterable<T> to DatasourceGet?  (Notice a count is not necessary because the consumer can iterate as much as needed.)

@darcyparker Great!
If you are speaking about a new signature for the Datasource.get method, then why not. There are only two places where this emerges:

Datasource interface, just definition
Fetch process, usage

Also, there is a spec in ngx-ui-scroll project handling the Datasource and Fetch process running: datasource.spec.ts. I'd recommend to run it in parallel with vscroll developing, this part of the doc tells how to do it. I'd be happy to remove the Datasource spec from ngx-ui-scroll and create a new one in vscroll; it should a) explicitly check all signatures with all possible (especially wrong) arguments, b) emulate Fetch process run and check all possible immediate and delayed results.

@dhilt - FYI. I started this today and made some progress, but it is still a WIP.

https://github.com/dhilt/vscroll/pull/28 (minor pull request)
I ran into some issues that will likely require some experimentation/tweaking of vscroll.  I tried npm install --save vscroll@github:darcyparker/vscroll#scrollFactory-wip (a temporary measure during development in my scrollFactory-wip branch.), but for some reason the node_modules/vscroll dir does not include the build of vscroll.  I suspect this has something to do with prepack... I am not sure why it is not running the build...
In my fork, I have a scrollFactory-wip that I expect I will rebase as my work progresses... It's not ready for discussion/review, but you're welcome to have a look.  I did backtrack on some of my previous work/experiments and expect I will do so again.
I am going to chip away at this as time permits... I think its going to take a bit more time to dive into vscroll and generalize its dom methods to better fit html and render interfaces from libaries like uhtml, lit-html, https://github.com/developit/htm and the numerous others like it.

@darcyparker Here's the tip on core-consumer development:

clone both vscroll and vscroll-native repositories into the same folder
replace "vscroll" import with local sources here

You may push your wip-branch to the original repo, open draft PR, then it may be easier to discuss


Dates show up in the rent timeline as 1 day before, probably because of a timezone issue

https://github.com/techequitycollaborative/tenantprotections2/pull/43


FR: make it more obvious that package names in the package catalog are case sensitive

Background & motivation
The Kurtosis package catalog search bar is case sensitive - I didn't know this and so when I was trying to deploy a the hyperlane package, I couldn't find the package when I used Hyperlane and could only find it when I typed hyperlane in the search bar.

Desired behaviour
To me, this is annoying because I did not expect the package catalog to be case sensitive. The ask here is to either:

Remove the case sensitivity restriction OR
Add a tool tip/disclaimer/banner to tell a user that its case sensitive

I prefer (1)
How important is this to you?
Nice to have; this feature would make using Kurtosis more enjoyable.

No longer the case


Contact Page Form Submission Error and Input Validation

🛠 Fixes Issue: #146

Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

👨💻 Changes proposed:
Summary:
The form action attribute is removed for now for resolving the issue where the form submission was causing a broken site experience and resulting in a "No Webpage Found" error. Also, added client side user input validation for the form data before submission
Motivation:
The proposed changes aim to fix a critical bug on the contact page, which currently make no validation on the user data and post the data to the broken page. By fixing this, we ensure that user-submitted data is processed correctly, providing a seamless and error-free experience for website visitors.

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.
[x] I have included comments in areas that may be difficult to understand.
[x] My changes have not introduced any new warnings.
[x] I have conducted a self-review of my code.
[x] I am a participant of Hacktoberfest 2023.

📷 Screenshots

Alert for submitting without Name Field:

Alert for submitting without Email Field:

Alert for submitting without Message Field:

Submission occurs and no error after it:

📄 Note to reviewers

@KiranAminPanjwani can you please review these fixes


Styling breaks since 7e00233

Environment
System: macOS
Terminal: Kitty 0.32.0 ($TERM: xterm-kitty)
Tmux: 3.3a
Awk: GNU Awk 5.3.0
sh --version: GNU bash, version 5.2.26(1)-release (x86_64-apple-darwin23.2.0)
.tmux.conf.local
Only overrode the separators. I made sure this was the only change after the default .tmux.conf.local changed too.
tmux_conf_theme_left_separator_main='\uE0B0'  # /!\ you don't need to install Powerline
tmux_conf_theme_left_separator_sub='\uE0B1'   #   you only need fonts patched with
tmux_conf_theme_right_separator_main='\uE0B2' #   Powerline symbols or the standalone
tmux_conf_theme_right_separator_sub='\uE0B3'  #   PowerlineSymbols.otf font, see README.md

Symptom
When using 1469d46:

When using 7e00233:

I can verify the same here. Anything after 7e00233 results in the plain status bar shown in the screenshot above.  Reverting back to 7e00233 allows the proper theme configuration to be applied.
NixOS 23.11
tmux 3.3a

Hello @Frederick888 and @mayersj1,
Can you please try reloading the configuration with <prefix> + r?

I tried on both macOS Ventura 13.4 and Sonoma 14.2.1 along with tmux 3.3a and I don't reproduce the issue, which may be caused by not reloading the configuration

@gpakosz I'm afraid the issue persists after reloading. Just tested under Arch too and it had the same issue.

I realised that this only happens with GNU sed. macOS (and BSD?) sed works fine. (GNU sed is my default sed under macOS too.)

@Frederick888 Ah thanks for mentioning GNU sed, that gives me a way to investigate.
I won't be able to fix that in the next couple of hours though. Stay tuned...

Can you please the gh-712 branch?

@gpakosz Yup it works :) Thank you

Verified fixed with latest pull.  Thanks for the quick turnaround!


Update instances of SuperstaQ to Superstaq in docs

Related: https://github.com/SupertechLabs/server-superstaq/issues/2375
Also note to update in docstrings

find . -type f -exec sed -i "s/SuperstaQ/Superstaq/g" {} \;
Also need to update:

[ ] SupermarQ --> Supermarq
[ ] SupercheQ --> Supercheq


cmd/kvpctl: hardcode Ignition config key prefix; fix get argument validation

Ignition config keys will always start with ignition.config., so don't require users to explicitly specify that prefix.
Also, the get subcommand allowed four arguments but not three, which should have been the other way around.
cc @baude.  Could we get a new release build that we could point users to?

LGTM
@n1hility PTAL

/lgtm

Thanks!  Could we get a new release with an updated kvpctl.exe artifact?  (xref #41)

@bgilbert here you go: https://github.com/containers/libhvee/releases/tag/v0.4.0


Use Google Compute Engine Autoscaler and Instance Group Manager API

Goal:
Reduce the utilization on low period and increase dynamically in high usage
periods using Autoscaler.
https://cloud.google.com/compute/docs/autoscaler/

I propose the following instance-specific tuning parameters:
- A minimum number of persistent instances.
- B maximum number of dynamic instances.
- C minimum number of idle bots at any time.
- D maximum number of idle bots at any time.
- E predefined time from requesting a new VM to time it's available.

Action Item:
- MVP is to create a cronjob which calls the Autoscaler API[1] to either add or
remove instances. Hardcode values [A-E] for now to get it out faster.
- Create a feedback loop based on BotEvents to determine the E value.
- Create support for autoscaling per OS. Initial value would be hard coded to
Ubuntu-12.04, eventually would support Ubuntu-12.04, Ubuntu-14.04 and
Windows-2008ServerR2-SP1.
- Add ability to edit GlobalConfig to stop using hardcoded values.
- Eventually switch from cronjob to taskqueue to get sub-minute adjustment.

[1] https://cloud.google.com/compute/docs/autoscaler/v1beta2/

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 10 Dec 2014 at 7:16

Blocking: #198

Not using the GCE autoscaler.


Maximum recursion level reached on input_process

I am getting this error when I run input_process.py on physionet data, the error is happening on this line:
rec = json.dumps(rec)
do you have any solution for this?
Thanks

Hi @ideznaby ,
I've been experimenting with BRITS model recently. In my opinion data format output is incorrect in input_process.py. I've changed parse_rec to
`def parse_rec(values, masks, evals, eval_masks, dir_):
deltas = parse_delta(masks, dir_)
ts_list = []
for r in range(values.shape[0]):
rec = {}
rec['values'] = np.nan_to_num(values[r]).tolist()
rec['masks'] = masks[r].astype('int32').tolist()
# imputation ground-truth
rec['evals'] = np.nan_to_num(evals[r]).tolist()
rec['eval_masks'] = eval_masks[r].astype('int32').tolist()
rec['deltas'] = deltas[r].tolist()
ts_list.append(rec)
return ts_list

`

Hi @Ubikas thank you for your answer, I tried this but I am still getting the same error, were you able to run the code on Physionet data?
Thanks

Hi @ideznaby ,
as far as I remember I was getting the same error with physionet data, but I adopted algorithm to my dataset and it has 19 attributes instead of 35. In my opinion to use json is not the best idea, I'd rather use numpy array with strict ts type order like [sample, ts_type, lag, attribute]. So in this case would be [2000,5,49,35]. Unfortunately I didn't have time to code it and as json format worked fine for me I left it as it was.

Instead of using usjon, just use python's original json API as follows in data_loader.py and input_process.py files:
#import ujson as json
import json

dumps() and loads() functions are the same. In input_process.py, define your own JSON encode as follows and dump rec as follows:
class NpEncoder(json.JSONEncoder):
    def default(self, obj):
        if isinstance(obj, np.integer):
            return int(obj)
        elif isinstance(obj, np.floating):
            return float(obj)
        elif isinstance(obj, np.ndarray):
            return obj.tolist()
        else:
            return super(NpEncoder, self).default(obj)

rec = json.dumps(rec,  cls=NpEncoder)
This effectively mitigated Maximum recursion level reached error in my code.

Hello @Ubikas @caow13 @#,
Can anybody help me with letting me know how I can have the file with the imputed values?
I do not get how and where I can find the output imputed results.
Thanks a lot in advance.

cls=NpEncoder

Thank you for your suggestions. It solved the problem of maximum recursion level issues. Btw have you got exact paper claimed results?

No, because PyTorch itself is non-deterministic. Please check: https://pytorch.org/docs/stable/notes/randomness.html

No, because PyTorch itself is non-deterministic. Please check: https://pytorch.org/docs/stable/notes/randomness.html


incorrect constant value for net.runelite.api.widgets.WidgetID.Shop.ITEMS_CONTAINER

The value net.runelite.api.widgets.WidgetID.Shop.ITEMS_CONTAINER = 2 is inconsistent with the actual in-game shop items container widget. As shown by this screenshot, the path to the container is 300.16, instead of the suggested 300.2.
https://github.com/runelite/runelite/blob/78e0cf53926a9060a559769bd3e40eab16582d22/runelite-api/src/main/java/net/runelite/api/widgets/WidgetID.java#L306

We are no longer using that definition, so it was removed in #13011.

We are no longer using that definition, so it was removed in #13011.


Sequence Labeling Issue

How to label words that bert vocab does not contain?
This situation happens in English corpus. For example, the word 'jony' is tokenizered to 'jon', '##y'. If in the origin corpus 'jony' is labeled with B-PER, how to modify the corresponding sequence labels in tokens produced by BERT in your code?

In my understanding, there is no need to modify the corresponding sequence labels.
For example,  given a sequence ['Jony', 'is', 'a', 'boy'] with label being ['B-PER', 'O', 'O', 'O'].
After tokenization, you will get ['Jon', '##y', 'is', 'a', 'boy'].
According to the BERT paper:

we use the representation of the first sub-token as the input to the token-level classifier over the NER label set.

In this setting, you are using  ['Jon', 'is', 'a', 'boy'] as the representative of the original sequence ['Jony', 'is', 'a', 'boy']. Since the sequence length is unchanged, you don't need to change the original sequence labels either. Hope this discussion would be helpful to you.


Array of type Enum not created in generated Schema

I have a prisma1 schema that looks like this.
type User {
  id: UUID! @id @unique
  email: String! @unique
  name: String!
  displayName: String!
  password: String!
  profile: UserProfile @relation(name: "UserProfile", link: INLINE, onDelete: CASCADE)
}

type UserProfile {
  id: UUID! @id @unique
  user: User! @relation(name: "UserProfile", onDelete: CASCADE)
  interests: [InterestOptions!] @scalarList(strategy: RELATION)

  createdAt: DateTime! @createdAt
  updatedAt: DateTime! @updatedAt
}

enum InterestOptions {
  FASHION
  TRAVEL_AND_HOSPITALITY
  COFFEE
}

When I run the commands to update the schema, the generated schema looks like this.
model User {
  id                     String   @default(uuid()) @id
  email               String   @unique
  name               String
  displayName  String
  password        String
  profile             String?
  Profile             UserProfile?   @relation(fields: [profile], references: [id])
}

model UserProfile {
  id                                                        String                             @default(uuid()) @id
  User                                                   User
  UserProfile_interests                        UserProfile_interests[]
}

*Enum type of InterestOptions was not created*

The error I got in running an SQL query
=> ALTER TABLE "default$default"."UserProfile" ADD UNIQUE ("user");

*ERROR:  column "user" named in key does not exist*

Version
"prisma-upgrade": "^0.0.26",
"@prisma/cli": "^2.2.0"
While that happened, can i just manually go ahead and update the model like this?:
model UserProfile {
  id                             String                             @default(uuid()) @id
  User                        User
  interests                 interestsOptions[]
}

enum InterestOptions {
  FASHION
  TRAVEL_AND_HOSPITALITY
  COFFEE
}

Thanks for reporting! I'll investigate this issue and get back to you soon.

Are you using MySQL or Postgres?

Postgres

Okay this should be fixed by #57. Please give it a try in 0.0.33.

@matthewmueller I'm having the same issue.
  Fix 1-1 relations by adding `UNIQUE` constraints
  https://pris.ly/d/schema-incompatibilities#inline-1-1-relations-are-recognized-as-1-n-missing-unique-constraint

    ALTER TABLE "default$default"."Location" ADD UNIQUE ("activity");
    ALTER TABLE "default$default"."ContactSettings" ADD UNIQUE ("contact");

My Prisma 1 datamodel file has this relevant section

type Activity {
  id: ID! @id
  location: Location @relation(name: "ActivityLocation", onDelete: CASCADE, link: INLINE)
}
type Location {
  activity: Activity @relation(name: "ActivityLocation", onDelete: SET_NULL)
  countryCode: String
  latitude: Float
  longitude: Float
  name: String
  id: ID! @unique @id
}

type Contact {
  address: String
  id: ID! @id
  settings: ContactSettings @relation(name: "ContactSettings", onDelete: CASCADE, link: INLINE)
}
type ContactSettings {
  doNotContact: Boolean
  contact: Contact! @relation(name: "ContactSettings", onDelete: SET_NULL)
  id: ID! @id
}


Broken link on Storage Classes page

Problem:
The text Storage Policy Based Management for dynamic provisioning of volumes on link is not working, it should point to these https://github.com/vmware-archive/vsphere-storage-for-kubernetes/blob/master/documentation/policy-based-mgmt.md
Check the page Storage Classes for the problem.
Page to Update:
https://kubernetes.io/docs/concepts/storage/storage-classes/
Proposed Solution:
It should resolve this issue by adding a simple link and enhancing the document line.
Update the link on the text Storage Policy Based Management for dynamic provisioning of volumes to https://github.com/vmware-archive/vsphere-storage-for-kubernetes/blob/master/documentation/policy-based-mgmt.md and not to this link.
/kind document
/assign
/language en

/triage accepted


TSCUtility: deprecate Bitstream interfaces

The bitstream interfaces were only used by swift-driver.  The implementation has been migrated into swift-driver, allowing us to now mark the interfaces as deprecated.

@swift-ci please test

SerializedDiagnostics also use the Bitstream interfaces, and now have warnings.  SwiftPM hasn't yet switched over to use that instead of just passing the .dia file up to Xcode to parse using libclang, but the plan was to move in that direction.  Is the plan to remove SerializedDiagnostics also?

we can roll this back if premature. @compnerd ?

@tomerd sure, we can revert this for now.  I can try to create an internal alias to avoid the warnings.  Not sure if I can do anything about removing the use of SerializedDiagnostics in SwiftPM, which would certainly be nice (otherwise we will have a copy of the bitcode logic in swift-driver and SPM).

Hmm... having two copies is certainly not good.  But what was the reason for wanting to move BitstreamReader directly into SwiftDriver package in the first place?  Is it just part of chipping away at TSC?
From SwiftPM's perspective, it certainly seems desirable for to be able to understand .dia files without taking on external dependencies on libclang etc.  SwiftPM's use of SerializedDiagnostics is still only minimal, but I was hoping to make more use of it because right now the manifest and plugin compilation APIs in libSwiftPM are kind of awkward: the SwiftPM logic doesn't actually see the errors but just passes the path of the .dia to an IDE like Xcode which then has to use libclang.dylib to read them.  Every IDE using libSwiftPM has to do this separately.
Besides being ugly, this makes it hard for SwiftPM to reason about the errors, or to produce formatted output or anything like that for diagnostics from compiled manifests and plugins.  So I was hoping to clean things up by having SwiftPM just load the diagnostics and then send them through the normal observability scope APIs that it uses for diagnostics.  There were a couple of fixes needed for that in SerializedDiagnostics, which I have been making on a side branch that isn't quite ready for a PR yet (properly handling annotations rather than emitting multiple top-level diagnostics, for example) and that I was going to put up a TSC PR for.
So making SerializedDiagnostics inaccessible to SwiftPM seems harmful, not nice.  If it can't be in TSC, could it be in some other package that can be shared?  We all agree (I think) that path and process and other general stuff shouldn't be in TSC now that we have support in SwiftSystem and Foundation etc, but there is a category of developer-focused functionality such as this that seems like it could have a hope in a shared package that is geared toward developer tools.

Removing SerializedDiagnostics is not the intent, the motivation here is to chip away at tools-support-core.  The removal of SerializedDiagnostics would be by pushing that into swift-package-manager as that is the only client of the API.  The piece I didn't realize was the internal dependency.
Currently, I'm looking at TSCUtility.  We are pretty close to stripping that out in practice.  swift-driver depends on Version, Diagnostics and SourceKit-LSP depends on Platform, BuildFlags.  The remainder of the interfaces that are in TSCUtility are in use in SwiftPM.  It would be possible to sink the rest of the interfaces into SwiftPM.
I suppose I don't fully understand the SwiftPM perspective here.  It is also possible to get the diagnostics without serializing them if the desire is to just get the data.  That would allow us to filter and stream it through the observability APIs.  A dependency on libclang also doesn't seem too onerous to me.  At least for Swift toolchain distributions, clang is a requisite component.  Additionally, for SourceKit-LSP (which is really an expectation I believe), clangd and libclang are part of the distribution.  So, while it might be increasing the interdependence between SPM and the rest of the toolchain, that connection is already present due to the other dependencies.

It is also possible to get the diagnostics without serializing them if the desire is to just get the data. That would allow us to filter and stream it through the observability APIs.

That sounds very promising!  It's annoying that structured diagnostics from Clang and Swift use the bitstream format when it seems that something like a JSON format would have been easier for callers to work with.  What's the other way to get these diagnostics in a structured form?  I've looked at -parseable-output in the past but although it passes on the textual output of each individual compiler invocation I haven't found a way to get the structured diagnostics that way.
I'm certainly not tied to parsing the .dia — I do think that SwiftPM should understand the diagnostics coming from the compiler and scraping the textual output is lossing.  But if there's another way at getting the diagnostics, then that would be great.

I don't think that there is another structured form.  The diagnostics can be formatted in specific manners (e.g. msvc, vi, or clang).  GCC does support json, which we could add to clang I suppose, as we do try to be compatible with gcc.  However, the diagnostics that it seems like are of interest here are the Swift ones rather than the C/C++ ones.

I see — I thought you were saying that there was a better structured format (for Swift in particular, which is what the manifest and plugins are — the other diagnostics we let llbuild handle) that was easier to parse than the .dia files.

I wonder if we should look at -diagnostics-editor-mode as it may be the mode that we need for dealing with the diagnostics.


Created draft example

Looks pretty good so far! Minor comments. Also @DanRod1999 will need to review for not breaking the test pipeline and performance report.

looks good to me. @KyryloVolotovskyi if you could send me the report.csv of a completed run so I can double check the format that would be great.

Looks pretty good so far! Minor comments. Also @DanRod1999 will need to review for not breaking the test pipeline and performance report.

looks good to me. @KyryloVolotovskyi if you could send me the report.csv of a completed run so I can double check the format that would be great.

Sent in personal messages


"invalid memory access" segfault using at_exit and $global variables

I couldn't reduce, but this now fails (not sure since when, but 0.14.2 is affected): https://github.com/ysbaddaden/selenium-webdriver-crystal/blob/d4179a8eb78420c699227c357cf67209ec55a82d/test/test_helper.cr
This is what happens:

the $driver and $session variables are initialized (they are accessible);
minitest executes in an at_exit block (Test instances are then created);
accessing @driver results in segfault.

I suspect that the global variables are collected at some point.
Note: I fixed it by using class variables instead of global variables, which was a bad design anyway.

@ysbaddaden I can try to reduce it.
I checkout out that branch but with 0.14.2 I can't compile it, lots of syntax errors regarding method arguments, and then when I fix that I get some semantic errors. If you point me to a version that compiles but fails I will take a look at it. Thanks!

It should compile with 0.14.2 at this commit: https://github.com/ysbaddaden/selenium-webdriver-crystal/commits/fe09386bc1c02176339ab63a5cce92c60bbbdb4f

Now that global variables are removed from Crystal. Can we close this issue?


add .listen_unix() to TypeScript definition file

https://github.com/uNetworking/uWebSockets.js/issues/815

It has to be like this
    listen_unix(options: ListenOptions, cb: (listenSocket: us_listen_socket | false) => void | Promise<void>, path: RecognizedString) : TemplatedApp;

Hi @uNetworkingAB, maybe we need 2 overloads for listen_unix, then?
Correct me if I'm wrong but by reading the source I don't see ListenOptions, I could only notice:

At least 2 arguments required https://github.com/uNetworking/uWebSockets.js/blob/00ccaa9edd2448fd54ef0a46f143c133dcf89079/src/AppWrapper.h#L342-L345
First argument is always a callback https://github.com/uNetworking/uWebSockets.js/blob/00ccaa9edd2448fd54ef0a46f143c133dcf89079/src/AppWrapper.h#L349-L350
Path is last https://github.com/uNetworking/uWebSockets.js/blob/00ccaa9edd2448fd54ef0a46f143c133dcf89079/src/AppWrapper.h#L357-L358

Perhaps we can have the signature I proposed + another with options as the second argument?
// 2 args
listen_unix(cb: (listenSocket: us_listen_socket) => void | Promise<void>, path: RecognizedString) : TemplatedApp;
// 3 args
listen_unix(cb: (listenSocket: us_listen_socket) => void | Promise<void>, options: ListenOptions, path: RecognizedString) : TemplatedApp;

Cheers

Ah


why llm_cache only supports in BaseLLM, not in BaseChatModel? I can't use llm_cache when using ChatOpenAI. instead, i can only use it by using OpenAI.

System Info
Langchain v0.0.200
I want to use GPTCache in my project based on langchain. But I find langchain.llm_cache only supports in BaseLLM, and it has no support in BaseChatModel. So I can't use llm_cache when using ChatOpenAI. instead, i can only use it by using OpenAI.
Related langchain source code:

Who can help?
No response
Information

[X] The official example notebooks/scripts
[ ] My own modified scripts

Related Components

[X] LLMs/Chat Models
[ ] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[ ] Vector Stores / Retrievers
[ ] Memory
[ ] Agents / Agent Executors
[ ] Tools / Toolkits
[ ] Chains
[ ] Callbacks/Tracing
[ ] Async

Reproduction
no step.
Expected behavior
I want to use llm_cache in ChatOpenAI.

Generated by a 🤖
Answer
The llm_cache is not supported in BaseChatModel because it is designed specifically for the BaseLLM class, which focuses on generating text completions with a single text input. In contrast, BaseChatModel, like ChatOpenAI, is designed for multi-turn conversations with a series of messages as input. The caching mechanism in BaseLLM is tailored for single-turn completion use cases and may not be suitable for multi-turn conversations. If you want to use llm_cache with ChatOpenAI, you would need to implement a custom caching mechanism compatible with the multi-turn conversation structure of the BaseChatModel class.
Sources

langchain/llms/openai.py

This response is meant to be helpful and save users time. It is not meant to be a precise solution.
Please leave a 👍 if this is helpful and 👎 if it is irrelevant


Add fake data methods

Generate fake data for:

College
Essay
Major
Recommendation Letter
Student Profile
Test Score

Leave comments inline if you have any, otherwise just comment "LGTM" (looks good to me) and we can merge this.


Zot website landing page: responsive page for mobile version

The website will be reimplemented with a separate framework.


Trying to make it work with RingFitAdventure on Yuzu

It detected joycons, but I cannot get the pull/squeeze functional...
Thanks for any help.

@ringrunnermg +1 on this. It appears unrelated to yuzu.
My ringcon works fine but my friend's doesn't show any xbox360 input for push/pull. We are using the same version of the program with the same settings on Windows 10.
The console window shows numbers when either of us push/pull the ring, the only difference is his doesn't press the triggers.

help with the JoiCon problem: https://github.com/ringrunnermg/Ringcon-Driver/issues/22?ysclid=llhxsz6lkk27258939