ledfx: init at 0.10.7

Motivation for this change
Wanted to try this out. Works in combination with e.g. WLED, but eats a whole core on my i7-8550U while trying to drive ~2.1k LEDs with 30fps over WLAN to an ESP32. Not a pleasant experience, but totally not their fault.
The packaging patches out pyupdater, since that won't work on NixOS anyhow.
The packaging relies on the fact that the upstream ships their generated frontend files with their PyPi package, so it can leave out annoying NodeJS packaging efforts.
Dropping this as is for now, so others can find it and try it out. No intention to maintain at this point.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

added by #226211


feat: add neon driver

🔗 Linked issue

❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[x] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This PR adds support for Neon Postgres using the Neon Serverless driver.
📝 Checklist

[ ] I have linked an issue or discussion.
[x] I have updated the documentation accordingly.

Would be nice if we do have DB0 storage first because this way when unstorage is used in Nitro/Nuxt, we can leverage auto configuration. (There is even a placeholder page already!)
Next we can integrate neon with unstorage using generic SQL driver (https://github.com/unjs/unstorage/issues/400) but I see value of db0 provider would be much much more than focusing on unstorage first.


Brush box on px-vis-navigator disappears

Brush box on px-vis-navigator disappears when the two ends have the same value.
To reproduce, reload the chart and try dragging the left handle all the way to it overlaps on the right. Then let go. This overlap can happen anywhere, but is very easy to do this way.

brush box still can disappear, but now at least you can just draw a new one.

fixed in v0.6.32


[Docs][SLM] Update runtime tutorials

This PR updates the runtime portion of the documentation to reflect changes in SLM, as per https://github.com/mlc-ai/mlc-llm/issues/1420.

We specify the full model path and model lib path in Python/CLI runtime (S5).
Update project overview to remove local_id and model_lib fields from mlc-chat-config.json (redrew figure to highlight model weights and model lib) (S6)

cc @tqchen Please let me know if we should simplify the mlc-chat-config and config override portion of project overview, and make it almost only about model and model-lib.


limit bandwidth option

It would be nice if restic offered an option like rsync has to limit bandwidth usage. In particular when uploading. I have pretty bad internet where I live and when I upload it really kills my download connection. It would be great if I could limit the upload bandwidth being used by restic.

Great idea, I'll keep this issue as a reminder.

i'm using traffic shaping with trafficcontrol/iptables.
have a look at this link: https://help.atmail.com/hc/en-us/articles/201566464-Throttling-Bandwidth-using-Traffic-Controller-for-Linux
works perfect :-)

An integrated bandwith limiting feature would be great.
In the meantime, what I use to limit traffic for the sftp backend is to pipe the connection through pv:
Host myserver-restic
        ProxyCommand pv -q -L 100k | nc myserver.com 22

I would also really like to have this. My upload speed is about 120KB/s and for an initial backup of 300GB to BackBlaze I would need a month at full upload speed, so I'd rather make two months at half speed out of it and use my internet normally.
Off-topic - is restic even designed for what I want to do? Can the upload be interrupted and continued? I can not assume to have my laptop powered and online for such a long time.

Off-topic - is restic even designed for what I want to do? Can the upload be interrupted and continued? I can not assume to have my laptop powered and online for such a long time.

While it's not an ideal situation, I'm confident that restic will handle this just fine. It just might take longer to upload the data, and it will upload duplicate data.
During upload, even if the backup is not finished, restic will write intermediate index files that contain a list of blobs uploaded so far. At a minimum, such an index file is written every five minutes.
When you abort the backup, and re-run it later, restic will first download all the index files so it knows which blobs are already in the repo. This includes the intermediate index files.
So, eventually you'll finish uploading all data.

This would be a really nice feature to have.

While it's not an ideal situation, I'm confident that restic will handle this just fine. It just might take longer to upload the data, and it will upload duplicate data.

This is in fact how I uploaded my 185GB to B2. Since it took several days of saturating my Internet, I would ^C the process during the day, and re-run the backup at night. Not ideal, but it worked OK after a few days and then some prune/check sessions.
For pruning, I've found that merely suspending the process (^Z) and then "fg" works fine, even after several hours of suspension.

For pruning, I've found that merely suspending the process (^Z) and then "fg" works fine, even after several hours of suspension.

Please run restic check --read-data on that repo, I'm not sure what prune does when you suspend it for so long...

Please run restic check --read-data on that repo (re-downloads and checks everything), I'm not sure what prune does when you suspend it for so long...

Thanks for the heads-up. It checked out fine.

I've just merged #1336, which adds the options --limit-upload and --limit-download :)


Add rho devnet inventory files

Works for me- we can just wait until the testnet repo changes get merged to update the genesis file URLs.


Wait sequential loading

3 list items are expected to be loaded. The items are loaded sequentially. First, second, third ...
assert_page_like(@page, item_list: ['item1', 'item2', 'item3'])
When the first element appears, an error occurs with the message: “Wrong elements count. Actual: 1.Expected: 3”.
Expected result:
The test waits until all 3 items are loaded.

Looks like a bug

Fixed
Please update the gem


New version: LibUV_jll v2.0.0+12

Autogenerated JLL package registration

Registering JLL package LibUV_jll.jl
Repository: https://github.com/JuliaBinaryWrappers/LibUV_jll.jl
Version: v2.0.0+12

[noblock]
@staticfloat See the test failures.

[noblock]
@staticfloat See the test failures.

@staticfloat I think deleting lines 1-3 of the Compat.toml file should fix the CI.

@staticfloat I think deleting lines 1-3 of the Compat.toml file should fix the CI.


Opening 'biometric' settings on Android is crashing application

Hello,I installed the plugin to open biometrics (touchID/faceID) device settings from an Angular+ionic App. On IOS, everything works smooth by using the 'touch' option. For Android, however, I experienced a couple of issues:

'security' option does not always redirect to the correct settings section (ex. privacy)
'biometric' options is even making App crashing on some devices.
Have you ever experienced something like this and/or know what the issue could be?

Tech stack:
"@ionic/angular": "^6.0.9"
"cordova-open-native-settings": "^1.5.5"
"@awesome-cordova-plugins/open-native-settings": "^5.37.3"

See #57, 'biometric' fails on Android 13.


Checkbox with no container focus style is too subtle

Hi first of all thank you for your help with the previous issues. It is appreciated.
I noticed that focus style on the Checkbox with containers is very subtle. Could we have a border?

This does seem like a sensible request - I have also picked up on this previously.
I will check the original spec and discuss discuss with the wider team.


Add --record-video --no-record-video

#365

Codecov Report

Merging #414 into master will decrease coverage by <.01%.
The diff coverage is 66.66%.

@@             Coverage Diff              @@
##             master     #414      +/-   ##
============================================
- Coverage     78.98%   78.98%   -0.01%
- Complexity      560      571      +11
============================================
  Files            69       69
  Lines          1742     1746       +4
  Branches        267      267
============================================
+ Hits           1376     1379       +3
  Misses          196      196
- Partials        170      171       +1


Allow splitting packages into a group

Splitting packages work nicely however there is no way to organize or grouping some packages with other.
Let's assume that we have the following packages name:

pkg1
pkg2
pkg3

What I would like to achieve is to reorganize pkg1 & pkg3 in a bundle, and pkg2 in another bundle.
With FuseBox, we can enforce strong guidelines with a Team who develop a large application by recommending to use massively the syntax:
let r = await import("xxx");

By using the code splitting config, I would expect below grouping syntax:
{
   "bundle1": [ "pkg1", "pkg3" ],
   "bundle2": [ "pkg2" ]
}

bundle1 a bundle2 are named bundles but can be like bundle-[hash] during the finalization of the process.
What is the real benefits behind this ?
No matter how big or small you application, you can develop without thinking anymore about code splitting, the rule of thumb is just do import. Of course, FuseBox by default do the splitting as it is today, auto split per package.
If you are not happy with the default behavior, you can start to reorganize by optimizing the code splitting configuration.

Right, so you are suggesting grouping modules into a one bundle using config. What would come once you import it?
It doesn't sound very good, because typescript won't allow it, and it's off the standard, unless you specify typings for it.
const {moment, foobar } = await import("foo")

It's not what i meant. The developper doesnt do the syntax you are writing, otherwise it's a mess.
You don't change the way you are coding. The grouping or reorganization is a step for optimizing bundles by knowing well you application behavior.
Having a sort of mapping configuration would be nice.

@leon-andria what prevents you from create a module that exports these 2 bundles?
woo.ts
export foo from "foo";
export boo from "boo"

const {foo, boo} = await import("./woo")

Not a bad idea in a development phase but it's not what i want.
In a simple term, think it in a step of workflow.
1 guy who develops and 1 guy who manage the optimization. So, your developper should code as normal without knowing in advance how this will be bundled in the final process.

Does it help to have an idea if i'm telling you bundler visualizer?


A benchmark for the different levels of assembly inspired by the CEED benchmark.

The purpose of this PR is to implement a benchmark for MFEM testing the performance of the different levels of assembly on the different CEED benchmark problems.

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#2947
@YohannDudouit
@tzanio
@artv3 + @camierjs
3/30/22
⌛due 4/13/22
⌛due 4/20/22

PR Checklist

[ ] Code builds.
[ ] Code passes make style.
[ ] Update CHANGELOG:
[ ] Update INSTALL:

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

@YohannDudouit , How did you build?
/lib/../lib64/crt1.o:(.rodata+0x8): undefined reference to `main'
collect2: error: ld returned 1 exit status
I built mfem with cuda then typed make in the benchmarks folder

@YohannDudouit , How did you build?
/lib/../lib64/crt1.o:(.rodata+0x8): undefined reference to `main' collect2: error: ld returned 1 exit status
I built mfem with cuda then typed make in the benchmarks folder

Did you use MFEM_USE_BENCHMARK=YES?

@artv3 I don't think there is anything new to add in INSTALL.md, I added "New benchmark for the different assembly levels inspired by the CEED Back-Off Problems" to the CHANGELOG.md.

@artv3 I don't think there is anything new to add in INSTALL.md, I added "New benchmark for the different assembly levels inspired by the CEED Back-Off Problems" to the CHANGELOG.md.

Sounds good, I was just looking at your check list for the description for the PR.

@camierjs, can you please review when you get a chance?

The assemblies are also measured with the initial costs of allocations, sparsity pre-computation and restriction computation. Depending on the weight of the benchmark, it will be incorporated (1/1 or 1/n) which biases the results and won't be representative and usable as they are now.

@camierjs I verified this and I don't think this is correct, allocations are done in the constructors, whereas setup just reassembles, so we are benchmarking the same thing each time we are calling setup in the benchmark, I added a warmup setup nonetheless.
This is ready to be reviewed again from my point of view.

Merged in next for testing...


Ci wasm rest check

Codecov Report

Merging #181 (e1ead7a) into develop (ec6e85e) will decrease coverage by 0.01%.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@             Coverage Diff             @@
##           develop     #181      +/-   ##
===========================================
- Coverage    14.05%   14.04%   -0.01%
===========================================
  Files           22       22
  Lines         5813     5816       +3
===========================================
  Hits           817      817
- Misses        4996     4999       +3

see 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[terra-worklist-data-grid] Remove roving tabindex and resolve focus management issues

Summary

What was changed:
The WorklistDataGrid component was updated to remove the roving tabindex logic as it does not work when cells have focusable elements.  In addition, issues where the cell took focus from focusable child elements was also resolved.
Why it was changed:
The changes were made so that users could interact with focusable elements within the cells via the mouse.  In addition, we needed to clean up logic that was no longer necessary to reduce the complexity of the code for the component.
Testing

This change was tested using:

[x] WDIO
[ ] Jest
[ ] Visual testing (please attach a screenshot or recording)
[x] Other (please describe below)
[ ] No tests are needed

Verified that focus could be placed into focusable elements inside cells and select control could be used properly via the mouse.
Reviews
In addition to engineering reviews, this PR needs:

[x] UX review
[ ] Accessibility review
[ ] Functional review

Additional Details
N/A
This PR resolves:
UXPLATFORM-9436
UXPLATFORM-9440

Thank you for contributing to Terra.
@cerner/terra

LGTM!

@cm9361  The functionality of selecting the focusable element seems to work via mouse however if use a keyboard command after clicking the element the keyboard short cuts don't seem to function as expected. For example I click the Text Input in Column 1, Wayne, Bruce and press tab it takes me out of the component to the '' button rather to the Alert button. Also pressing Escape doesn't seem to work.

Tests failing due to issue with Terra Tabs component that must be resolved.


update e2e testing doc to direct user to enable adminserver tls

Why:
On a kas-installer OSD cluster the e2e tests were failing with the config generated by this script because there was no https route to the admin service.

Hi @MikeEdgar, I'm not confident on this one :grin: is this script used to run against environments where there is an https admin route?

Have changed to a README update after Mike showed us how to enable tls on the adminserver


feat(assets): add ?blob option

Description
This PR adds a new special query ?blob to import files as-is. This is needed when we don't have control on how and where the "import" might be used. closes #15650

What is the purpose of this pull request?

[ ] Bug fix
[x] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines, especially the Pull Request Guidelines.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Update the corresponding documentation if needed.
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

I would personally expect a module with ?blob query to be an instance of Blob 🤔

I would personally expect a module with ?blob query to be an instance of Blob 🤔

True, maybe ?plain could be more appropriate for importing files as-is.

If you don't want a file to be processed by Vite, you should put it in the public directory. Otherwise it's assume to be source code you write and you need to adjust accordingly.

I was planning on using this feature on a library

i just found this one on my search how to import an xlsx file in my vitest as (Blob) File for usage in a file select input.
for my test files i don't think it is a good idea to put it in the public folder.
and maybe is the best way to  just use the node fs module directly?
i have asked about this with detailed  use-case at stackoverflow

i ended up using vite-plugin-arraybuffer
that worked for me :-)

The reason I opened this PR is no longer an issue. Also, since there are better ways to import a file as is I'm going to close this PR.


Support for checking if a newer version of a file was downloaded.

Is it possible to check if a newer version of the file was downloaded while using the "onlyIfNewer" flag?

What do you mean exactly. Do you just want to check if there is a newer file without actually downloading it?

Closing due to inactivity. If the problem persists please reopen.


run migrations and collect static files on docker compose up

when docker-compose runs, automatically apply migrations and collect static files (note to self: look up what "collect static files" means)

To me, running these commands every time you start a container is a just little too much going on if you just want to quickly get the container up and running. If I needed to run a migration locally, I would want to be more deliberate about it. Typically to run these commands locally I would to create another container that with docker-compose exec django /bin/sh  and run these commands from that command line. If we have a huge ball of static files it may be annoying, but seems ok otherwise. Any reason for adding this beyond convenience?

good feedback, thanks!


Gnocchi: full archive policies support

Currently this repo only supports List and Get methods for the Gnocchi archive policies.
We need to also add support for the Create, Update and Delete requests.

[x] Gnocchi archive policy create (#43)
[x] Gnocchi archive policy update (#44)
[x] Gnocchi archive policy delete (#52)

Archive policies documentation reference:
https://gnocchi.xyz/rest.html#archive-policy

@ozerovandrei I have two things to apologize for:

I swear I left a comment last week about apologizing for the delay -- I was either imagining that or the comment never posted.
I just got a gnocchi environment up and running again, so I will be able to review these shortly. Sorry again for the delay.

@jtopjian there is no need to apologise.
Take your time, after all Gnocchi is not an OpenStack project (at least for now) 😄
I hope to create additional issues and PRs regarding another Gnocchi objects - resource types and archive policy rules. So, please do not destroy your Gnocchi environment after this issue!
Also I have another two questions outside of scope of this issue:

can you get the OpenLab acceptance tests runner working for this repository? (I forgot about acceptance tests by the way, will add them in PRs);
can I contribute Gnocchi archive policies, resource types and archive policy rules to the terraform-provider-openstack in the future? We discussed Gnocchi status regarding OpenStack in the form of Gophercloud issue#698. But what about the provider? Sorry for off topic. (But if you allow it, acceptance runner in the OpenLab is necessary, I guess).

@ozerovandrei Thanks for implementing this :)

can you get the OpenLab acceptance tests runner working for this repository?

I can see if OpenLab can integrate gophercloud/utils. It might take some work to get Gnocchi fully integrated, though, as I don't believe there's a devstack plugin for it.

can I contribute Gnocchi archive policies, resource types and archive policy rules to the terraform-provider-openstack in the future?

I gave this some thought. After working with Gnocchi and revisiting the discussion at https://github.com/gophercloud/gophercloud/issues/698, I think it was a good call not to bundle Gnocchi into Gophercloud. I think Gnocchi is best thought of as a time series database with optional OpenStack support rather than an OpenStack time series database.
My main concern with integrating Gnocchi with the Terraform provider is that it would require OpenStack to use Gnocchi rather than have Gnocchi be a standalone provider with optional OpenStack support.
I realize that 9/10 people would use Gnocchi+OpenStack, but given enough demand for Gnocchi-standalone, a separate provider would need created.
I'm going to close this issue but please feel free to continue this discussion if you have any questions or comments :)

@jtopjian thank you for a review.
Well, I'm of the same opinion about this, just wanted to hear your thoughts.


Belarusian language

Notify me if you find a mistake, I can fix it

please fix the conflicts @Smoothplayerr  thanks

Fixed


Change update stac source

when update_stac is True it will create a report with all scene paths from the source, instead the destination. In this way it will fill any gap while it is also updating the stac.

I don't like that the two behaviours are different. It adds complexity.
Does Landsat work the same or different?

I don't like that the two behaviours are different. It adds complexity.
Does Landsat work the same or different?

Landsat works exactly like that, because of that I changed so we won't have the orphans issue as we had previously with Landsat


Nimo and BigoTV cant use

When i using the link from nimo.tv and bigo.tv, the code response:
An error occurred: cannot be translated to a manifest URL
How can i fix that?

Please provide links so that I can check if this is a query-streamlink or global streamlink issue.


Bump to 39.0.0

To release #391
For: https://trello.com/c/opAHOMr4/443-4-of-4-delete-old-ldg-import-into-publisher-and-related-code-3

👍


Fix getEarliestMessageTime() in DLedger mode

BUG REPORT

Please describe the issue you observed:

What did you do (The steps to reproduce)?

Call DefaultMessageStore#getEarliestMessageTime() in DLedger mode

What is expected to see?

get correct timestamp

What did you see instead?

got a wrong timestamp

Please tell us about your environment:

Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):

DLedgerCommitLog's body start from offset 48, but in DefaultMessageStore#getEarliestMessageTime() still get from 0

#4168


Android: Can't adjust Animated.View's opacity from 1 to 0

this has been issued since last year and tagged resolved, but it seems still occurs the same trouble.
const opacity = useMemo(()=> new Animated.Vaue(1),[something]);

useEffect(() => {
   Animated.timing( opacity, {
      toValue(0),
      duration: 500,
      useNativeDriver: true,
   }
},[something]);

...

return (
...
   <Animated.View style={{opacity: opacity}}>
      <div> ... </div>
   </Animated.View>
...
)

this is the first issue that I found
https://github.com/facebook/react-native/issues/25318
and my react-native info
info Fetching system and libraries information...
System:
    OS: macOS 10.15.5
    CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
    Memory: 1.56 GB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 8.12.0 - ~/.nvm/versions/node/v8.12.0/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.4.1 - ~/.nvm/versions/node/v8.12.0/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.9.3 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.6, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK:
      API Levels: 23, 26, 28, 29, 30
      Build Tools: 29.0.2, 30.0.1
      System Images: android-28 | Google Play Intel x86 Atom, android-29 | Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 4.0 AI-193.69<IP_ADDRESS>14223
    Xcode: 11.6/11E708 - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_262 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.11.0 => 16.11.0
    react-native: 0.62.2 => 0.62.2
  npmGlobalPackages:
    *react-native*: Not Found

I'm experiencing this as well on both react-native 0.63.2 & 0.62.2. @jiyoon127 did you find a workaround?

If you stop using nativeDriver or set value from 0.9 to 0 works. but still, this fundamental problem wasn't solved.

I can confirm that it only works when you set the opacity to something like to 0.99.
Thanks @jiyoon127 for the suggestion. I would never arrive to this myself workaround myself.


Implement text clob writing

The TextWriter has text clob writing stubbed out with a todo!() implementation.
Here's the relevant portion of the spec.

@desaikd addressed this in #128.


Can we please upgrade to latest react-pdf version

9.0.0 has the security fix
https://github.com/wojtekmaj/react-pdf/releases

Also, there is a breaking change as the code includes pdf-worker.min.js instead of the breaking change pdf-worker-min.mjs
As the dependency is react-pdf@latest it automatically installs version 9.0.0 as a dependency and doesn't work.

v1.16.0 is experimental version with a lot of changes - especially about 9.0.0 of react-pdf upgrade. If you can, you can check if it is fine.

@cyntler I tried, I am using it in nextjs. but hitting below error:
Error: Cannot find module '/Users/xiaolongjiang/Documents/workspace/tax/node_modules/@cyntler/react-doc-viewer/dist/esm/DocViewer' imported from<EMAIL_ADDRESS>

It's also failing when doing yarn build
Collecting page data  ...Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/Users/xiaolongjiang/Documents/workspace/tax/node_modules/@cyntler/react-doc-viewer/dist/esm/DocViewer' imported from<EMAIL_ADDRESS>at finalizeResolution (node:internal/modules/esm/resolve:265:11)
at moduleResolve (node:internal/modules/esm/resolve:933:10)
at defaultResolve (node:internal/modules/esm/resolve:1157:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:390:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:359:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:234:38)
at ModuleWrap. (node:internal/modules/esm/module_job:87:39)
at link (node:internal/modules/esm/module_job:86:36) {
code: 'ERR_MODULE_NOT_FOUND',
url: 'file:///Users/xiaolongjiang/Documents/workspace/tax/node_modules/@cyntler/react-doc-viewer/dist/esm/DocViewer'
}

@xiaolongkipsi Hmm, I tried to run it locally with Next.js and it is working.

@xiaolongkipsi Check the example: https://github.com/cyntler/react-doc-viewer/tree/main/use-cases/nextjs

Can you try import with npm way? It seems you imported through your local
esm.
--
Xiaolong Jiang
Co-Founder & CTO, Kipsi
@.*** | LinkedIn
https://www.linkedin.com/in/xiaolong-jiang-25b34441/
On Sat, Jun 1, 2024 at 12:52 PM Damian Cyntler @.***>
wrote:

@xiaolongkipsi https://github.com/xiaolongkipsi Check the example
please:
https://github.com/cyntler/react-doc-viewer/tree/main/use-cases/nextjs
—
Reply to this email directly, view it on GitHub
https://github.com/cyntler/react-doc-viewer/issues/262#issuecomment-2143565163,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A23N7NOTPL3CV64OIQ5O3ETZFIRAVAVCNFSM6AAAAABIPC7NP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBTGU3DKMJWGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

@xiaolongkipsi Yes. I can. Check it: https://github.com/cyntler/react-doc-viewer/blob/main/use-cases/nextjs/src/app/page.tsx. I installed officially deployed version of this library and it is still working fine as expected.

Everything seems it should work. I am using latest nextjs but with older
pages style. But it should not matter. I am still hitting the same error
--
Xiaolong Jiang
Co-Founder & CTO, Kipsi
@.*** | LinkedIn
https://www.linkedin.com/in/xiaolong-jiang-25b34441/
On Sun, Jun 2, 2024 at 1:55 AM Damian Cyntler @.***>
wrote:

@xiaolongkipsi https://github.com/xiaolongkipsi Yes. I can. Check it:
https://github.com/cyntler/react-doc-viewer/blob/main/use-cases/nextjs/src/app/page.tsx.
I installed officially deployed version of this library and it is still
working fine as expected.
—
Reply to this email directly, view it on GitHub
https://github.com/cyntler/react-doc-viewer/issues/262#issuecomment-2143760777,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A23N7NO7UO2WY5TNAN5FYVTZFLMZBAVCNFSM6AAAAABIPC7NP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBTG43DANZXG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

@xiaolongkipsi Can you provide me more informations about your environment?
I mean:

Node.js & npm versions
Your package manager (npm/yarn/pnpm)?
Next.js version

node: v20.12.2
npm: 10.5.0
I am using yarn
Nextjs version: 14.2.3
I tried your nextjs use case example, that is working for me though.
--
Xiaolong Jiang
Co-Founder & CTO, Kipsi
@.*** | LinkedIn
https://www.linkedin.com/in/xiaolong-jiang-25b34441/
On Sun, Jun 2, 2024 at 11:58 AM Damian Cyntler @.***>
wrote:

@xiaolongkipsi https://github.com/xiaolongkipsi Can you provide me more
informations about your environment?
I mean:

Node.js & npm versions
Your package manager (npm/yarn/pnpm)?
Next.js version

—
Reply to this email directly, view it on GitHub
https://github.com/cyntler/react-doc-viewer/issues/262#issuecomment-2143986536,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A23N7NONL35KMVZ2RWH2O6LZFNTN3AVCNFSM6AAAAABIPC7NP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBTHE4DMNJTGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

I am getting same error:
node: v20.11.1
npm: 10.8.1

@jcvegan @emikira @xiaolongkipsi Please check the latest version: 1.16.2. I migrated to Vite build/compilation system instead of pure TS..

I got the same [ERR_MODULE_NOT_FOUND] error in v1.16.1
1.16.2 fixes the error for my project , thank you very much @cyntler


mockery: don't use boilerplate

Issue #, if available:
#234
Description of changes:
We decided against forcing one boilerplate to keep the copyright lines correct and because it's questionable whether generated files are subject to copyright.
However, we forgot to actually remove the boilerplate file from mockery config.
Testing performed:
make mockgen no longer fails.

approval in #236


possible memory leaks?

Hey, this is my first issue on Github, so bear with me...
I've been playing around with Raylib using pure interop with Swift language. As a comparison, I wanted to check for memory leaks against Go (which is a language I'm familiar with), and I found something interesting.
No matter what code it would be, you could use an example provided, and you would get similar or the same memory loss/leak.
I will go straight to the point.
Memory Check with Valgrind
If you check out the gist linked above, you can see that around 40,015 bytes in 573 blocks are possibly lost in go-raylib binding vs 0 bytes in 0 blocks against Swift's pure interop to C without any safe pointer management etc.
I did post this on raylib discord server under Go's channel, but I take it you aren't on the server? So I didn't know if it was worth posting it here either or not and find out what exactly is going on. Is it the binding that is leaking memory or something else?
Thanks!

@conifer-dev
tools like valgrind don’t understand Go’s calling conventions or stack layout.

package main

// #include <stdio.h>
// #include <stdlib.h>
//
// static void myprint(char* s) {
//   printf("%s\n", s);
// }
import "C"
import "unsafe"

func main() {
  cs := C.CString("Hello from stdio")
  C.myprint(cs)
  C.free(unsafe.Pointer(cs))
}

valgrind test
==16236== LEAK SUMMARY:
==16236==    definitely lost: 0 bytes in 0 blocks
==16236==    indirectly lost: 0 bytes in 0 blocks
==16236==      possibly lost: 1,152 bytes in 4 blocks
==16236==    still reachable: 0 bytes in 0 blocks
==16236==         suppressed: 0 bytes in 0 blocks
==16236== Rerun with --leak-check=full to see details of leaked memory

package main

// #include <stdio.h>
// #include <stdlib.h>
//
// static void myprint(char* s) {
//   printf("%s\n", s);
// }
import "C"
// import "unsafe"

func main() {
  cs := C.CString("Hello from stdio")
  C.myprint(cs)
  // C.free(unsafe.Pointer(cs))
}

==16452== LEAK SUMMARY:
==16452==    definitely lost: 17 bytes in 1 blocks
==16452==    indirectly lost: 0 bytes in 0 blocks
==16452==      possibly lost: 1,152 bytes in 4 blocks
==16452==    still reachable: 0 bytes in 0 blocks
==16452==         suppressed: 0 bytes in 0 blocks
==16452== Rerun with --leak-check=full to see details of leaked memory

tools like valgrind don’t understand Go’s calling conventions or stack layout.
golang use cgo, valgrind's possibly lost is useless.

Thanks for clearing that up! That makes more sense.


Outputs:SelectBox: Output channel selectbox, tweak main ARIA label

Tweak label option for outputs action bar select box as "Output Channels." for better readability.

Fixed with PR #61415


Change Farming growing progress colour

I think that green Complete and green In-progress colours can be hard to distinguish at a glance what has finished growing.
So cheap dirty win, swap Diseased to red and set Growing to yellow.
Could add additional In-progress colour into runelite-client/src/main/java/net/runelite/client/ui/ColorScheme.java to achieve same end result.
Thanks.

Diseased and dead aren't the same thing, thus they shouldn't be the same color.

agreed; but then why should Doing and Done be the same colour?

It's not, it's orange? GROWING(ColorScheme.PROGRESS_INPROGRESS_COLOR)
public static final Color PROGRESS_INPROGRESS_COLOR = new Color(230, 150, 30);

Where did you find that? my branch/PR?
Or in master runelite-client/src/main/java/net/runelite/client/plugins/timetracking/farming/CropState.java?

Meh, I read the diff wrong. The diseased should maybe be yellow instead. But I don't think it matters because you are looking at the progress???

I just think traffic light colouring system would be more fitting.
green = done/success
yellow = in progress/pending
red = stopped/error
What colour do you think would fit diseased best, to distinguish it from the existing? bright orange or yellow / super bright green? I did have a bit of play around before posting but nothing grabbed me.


Use preprocessed logcounts as input.

Hi,
Can I use preprocessed logcounts as input data? I tried setting normalize_library and log as False in ltv.utils.standard_clean_recipe(), it still preprocess the spliced and unspliced layers. Any suggestions?
Thanks.

Another problem is, after setting normalize_library and log as False in ltv.utils.standard_clean_recipe() and running train_vae(), it raises
KeyError: 'spliced_size_factor'


Revise helm chart's Github link to active repo

Mikescandy's repository at https://github.com/mikescandy/krakend-helm is not updated often (last update December 14, 2021) and uses the latest tag for the krakend image. There are 12 commits total here by 3 contributors.
The repo at https://github.com/equinixmetal-helm/krakend uses explicit version numbers and has regular releases and a full CI/CD pipeline set up vis GitHub Actions here: https://github.com/equinixmetal-helm/krakend/actions and the latest commit from 5 days ago.
Compare this https://github.com/mikescandy/krakend-helm/pulse/monthly with https://github.com/equinixmetal-helm/krakend/pulse/monthly

@ JAORMX , is this a :+1: or a :-1: ?

@ksylvan I'm one of the maintainers in the equinixmetal-helm/krakend, I'd be comfortable and happy if more folks take it into use. If you feel something is missing and want to contribute, we also would love to get external contributions.

Documentation published

@ksylvan I'm one of the maintainers in the equinixmetal-helm/krakend, I'd be comfortable and happy if more folks take it into use. If you feel something is missing and want to contribute, we also would love to get external contributions.

Awesome. I am happy to report that I was able to quickly bring up the latest KrakenD in a local Kubernetes cluster on my laptop using Rancher Desktop without any issues using that Helm chart.


Publish telemetry from ESC to ROS

The speed controllers (ESC) provide telemetry that can be useful for system monitoring and estimation of force provided by the thrusters. It woule be nice to make this available over our ros network

Here is an overview of the protocol provided by Jonas
KISS_telemetry_protocol.pdf

This has been tried two times, but for some reason, we cannot receive output from our ESCs. Since we have improved our thrust estimation instead, this issue is closed for now.


Ionic 4 with capacitor on iPhone landscape keyboard focus not right: iphone 8

Bug Report
Ionic version:

[x] 4.x
Current behavior:

On clicking on any input field on the iPhone landscape page shift is wrong. input field goes out of view and even on some screens keyboard is hidden behind a keyboard.
https://youtu.be/kveJ663r-oA

Expected behavior:
On clicking on input field focus should be right
Steps to reproduce:

Related code:

<div class="ion-page">
  <ion-header>
    <ion-toolbar color="dark">
      <ion-buttons slot="start">
        <menu-button></menu-button>
      </ion-buttons>
      <ion-title>
        Developer
      </ion-title>
    </ion-toolbar>
  </ion-header>
  <ion-content class="hasfooter">
    <ion-list>
      <ion-item>
        <ion-label position="stacked">Service Host</ion-label>
        <ion-input :value="serviceHost" @ionInput="serviceHost = $event.target.value" placeholder="Enter Service Host"></ion-input>
      </ion-item>
      <ion-item>
        <ion-label position="stacked">Test1</ion-label>
        <ion-input :value="serviceHost" @ionInput="serviceHost = $event.target.value" placeholder="Enter Service Host"></ion-input>
      </ion-item>
      <ion-item>
        <ion-label position="stacked">Test2</ion-label>
        <ion-input :value="serviceHost" @ionInput="serviceHost = $event.target.value" placeholder="Enter Service Host"></ion-input>
      </ion-item>
      <ion-item>
        <ion-label position="stacked">test3</ion-label>
        <ion-input :value="serviceHost" @ionInput="serviceHost = $event.target.value" placeholder="Enter Service Host"></ion-input>
      </ion-item>

    </ion-list>
  </ion-content>
  <ion-footer>
    <ion-toolbar color="dark">
    </ion-toolbar>
  </ion-footer>
</div>

Other information:

Ionic info:

"@capacitor/android": "1.0.0-beta.11",
		"@capacitor/cli": "1.0.0-beta.11",
		"@capacitor/core": "1.0.0-beta.11",
		"@capacitor/ios": "1.0.0-beta.11",
"@ionic/core": "4.0.0-beta.17",
		"@ionic/vue": "0.0.1",

Thanks for your issue! This is related to Capacitor. Please see here -> https://github.com/ionic-team/capacitor/issues/814

Thanks, @paulstelzer  for a response. Is this is issue discussing the same thing? I think they are discussing the solution of when keyboard is hidden then UI comes back to right position. But I am pointing out that when keyboard is opened then the input box goes out of view box.
Should I open separate issue with Cordova?
Solutions suggested in this thread (https://github.com/ionic-team/capacitor/issues/814) did not fix my issue

If this is an issue for Cordova keyboard, too, then you can open an issue ticket here -> https://github.com/ionic-team/cordova-plugin-ionic-keyboard
If you think you found a new issue, that nobody has mentioned yet, so feel free to open a new issue here at Capacitor -> https://github.com/ionic-team/capacitor/issues


Maybe use @ to mark these functions?

This has been possible since v2.3.0.


List snapshots and list disk API call failed if any other api hits at same time

Package Name: azure-mgmt-compute
Package Version: 29.1.0 and <IP_ADDRESS>
Operating System: RHEL
Python Version: 10.9.18

Describe the bug
We are listing the disk and snapshots using computre client and it faild to list with error
", (InvalidResourceType) The resource type 'disks' could not be found in the namespace 'Microsoft.Compute' for api version '2020-06-01'. The supported api-versions are '2017-03-30,2018-04-01,2018-06-01,2018-09-30,2019-03-01,2019-07-01,2019-11-01'..Code: InvalidResourceType.Message: The resource type 'disks' could not be found in the namespace 'Microsoft.Compute' for api version '2020-06-01'. The supported api-versions are '2017-03-30,2018-04-01,2018-06-01,2018-09-30,2019-03-01,2019-07-01,2019-11-01'"
To Reproduce
Steps to reproduce the behavior:

call list snapshot API or List disk API
during the pagination call  the other api call of the compute client hits

Expected behavior
we 100+ snapshots in subscription and when we enable the debug logs we can see pagination logic is working . idealy nextLink:"" have proper api versio i.e. 2019-07-01 but at same time some other compute clinet api hits with version 2020-06-01 and that cause the isssue
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.
we suspect issue is introduce from this PR https://github.com/Azure/azure-sdk-for-python/pull/26327
compute version = 28.0.0
on compute client =27.2.0 issue not reproduced
here are some code changes to pick api version from context not from nextLink

Hi @pavanpawar4591, thanks for the feedback we will investigate and get back to you asap

Hi @pavanpawar4591 Please try the following code which set specific api version to fix the issue:
from azure.mgmt.compute import ComputeManagementClient

ComputeManagementClient(..., api_version="2019-11-01")
...

HI @msyyc ,
your suggestion is not working for us .
we create compute management client ones and calling it for multiple  time for different resources like disks, vms, snaps, etc
and api version is different for all resources
raise ValueError(""API version {} does not have operation group 'virtual_machines'"".format(api_version))"
flexsnap-agent.22cf98e14c404000a483e20ad116b2fe: "ValueError: API version 2019-11-01 does not have operation group 'virtual_machines'"
we are using the profile, and use the same client for multiple resources like disk and snapshots etc
self.computeclient = ComputeManagementClient(
credentials, subscriptionid, base_url=cloud_base_url,
credential_scopes=credential_scopes, api_version="2019-11-01")

Hi @pavanpawar4591, The api of SDK is generated with swagger https://github.com/Azure/azure-rest-api-specs/blob/73d1e6522dfdedb795f46cf997921c623011caa6/specification/compute/resource-manager/Microsoft.Compute/DiskRP/stable/2020-06-30/disk.json#L590-L622. However, it seems service doesn't deploy the api-version "2020-06-60" even if they have published the api, which doesn't follow azure guideline. I will transfer the issue to rest repo so that service team could track it.


Error when run interactive demo

Hello, thanks for your work.
I installed the checkpoints and set up the environment but cannot run the demo.
python -m demo.demo   frames_path='/home/bbnclxy/ext16t/lyx-star/sam-pt-main/data/demo_data/bees/'   query_points_path=null   longest_side_length=1024 frame_stride=1 max_frames=-1
it reports error:

I would appreciate it if you could help me.

Hej, it looks like you're encountering an error when Hydra instantiates the model. To help us get a clearer understanding of the problem, could you set the HYDRA_FULL_ERROR environment variable to 1 to display the complete stack trace, which Hydra typically hides during the model instantiation process? You can do this by running export HYDRA_FULL_ERROR=1 in your terminal anytime before executing the python command. After setting this variable, you can run your command again and share the output with us. Thanks!

Had the same error, I missed tensorflow to be installed!

Hej @STAR-811, have you perhaps resolved your issue? Let us know if you need further guidance or if there are any updates.

@m43 hey,I also encountered the same problem, but after i set HYDRA_FULL_ERROR=1 in my terminal,This mistake still exists，like that

I have resolved the above issue because some third-party libraries from Github have not been fully installed.

@m43 hey,I also encountered the same problem, but after i set HYDRA_FULL_ERROR=1 in my terminal,This mistake still exists，like that

Hi, may I ask what's your solution to the problem? I've encountered the same problem but haven't found the reason/solution yet. Thank you so much!

Hej @ttanad, you can set the HYDRA_FULL_ERROR environment variable to 1 to see the full error. Has detectron2 been successfully installed on your system, i.e., can you run python -c 'import detectron2' without error?

Hej @ttanad, you can set the HYDRA_FULL_ERROR environment variable to 1 to see the full error. Has detectron2 been successfully installed on your system, i.e., can you run python -c 'import detectron2' without error?

Thank you so much for your response! Actually, I hadn't successfully installed the detectron2  since I saw another Issue post that said it's also okay for the demo even if skipping the detectron2. And I struggled for a long time but couldn't properly install detectron2 by your instruction lines and environment. Can you kindly suggest some solution for this case?

Here some things to try:

Run export HYDRA_FULL_ERROR=1 in your console and then run the demo. Paste the complete output log here or provide a pastebin link if the output is too long.
Remove<EMAIL_ADDRESS>from requirements.txt and re-run pip install -r requirements.txt. Try to run the demo again - will the demo work now?
Double check you have the minimal set of checkpoints downloaded as described here.

Thank you so much for your suggestions, after properly downloading all the minimal sets, it started working and the GUI page popped out for me to choose the points. But it seems that I have some problems exiting the page with esc and seeing the result. May I ask what should I expect to see after choosing the points? Is it only the point coordinates or it's expected to see the video as a result?
(sam-pt) C:\Users\ttana\OneDrive - HKUST Connect\Data\Point_tracking\sam-pt>python -m demo.demo  frames_path='${hydra:runtime.cwd}/data/demo_data/bees/' query_points_path=null  longest_side_length=1024 frame_stride=1 max_frames=-1
C:\Users\ttana.conda\envs\sam-pt\lib\site-packages\hydra_internal\hydra.py:119: UserWarning: Future Hydra versions will no longer change working directory at job runtime by default.
See https://hydra.cc/docs/1.2/upgrades/1.1_to_1.2/changes_to_job_working_dir/ for more information.
ret = run_job(
Setting seed to 72
model:
point_tracker:
target: sam_pt.point_tracker.pips.PipsPointTracker
checkpoint_path: ${hydra:runtime.cwd}/models/pips_ckpts/reference_model
stride: 4
s: 8
initial_next_frame_visibility_threshold: 0.9
sam_predictor:
sam_model:
image_encoder:
target: segment_anything.modeling.image_encoder.ImageEncoderViT
depth: 32
embed_dim: 1280
img_size: ${ ..image_size }
mlp_ratio: 4
norm_layer:
partial: true
target: torch.nn.LayerNorm
eps: 1.0e-06
num_heads: 16
patch_size: ${ ..vit_patch_size }
qkv_bias: true
use_rel_pos: true
global_attn_indexes:
- 7
- 15
- 23
- 31
window_size: 14
out_chans: ${ ..prompt_embed_dim }
prompt_encoder:
target: segment_anything.modeling.prompt_encoder.PromptEncoder
embed_dim: ${ ..prompt_embed_dim }
image_embedding_size:
- ${ ...image_embedding_size }
- ${ ...image_embedding_size }
input_image_size:
- ${ ...image_size }
- ${ ...image_size }
mask_in_chans: 16
mask_decoder:
target: segment_anything.modeling.mask_decoder.MaskDecoder
num_multimask_outputs: 3
transformer:
target: segment_anything.modeling.transformer.TwoWayTransformer
depth: 2
embedding_dim: ${ ...prompt_embed_dim }
mlp_dim: 2048
num_heads: 8
transformer_dim: ${ ..prompt_embed_dim }
iou_head_depth: 3
iou_head_hidden_dim: 256
target: sam_pt.modeling.sam.SamHydra
checkpoint: ${hydra:runtime.cwd}/models/sam_ckpts/sam_vit_h_4b8939.pth
prompt_embed_dim: 256
image_size: 1024
vit_patch_size: 16
image_embedding_size: 64
pixel_mean:
- 123.675
- 116.28
- 103.53
pixel_std:
- 58.395
- 57.12
- 57.375
target: segment_anything.predictor.SamPredictor
target: sam_pt.modeling.sam_pt.SamPt
sam_iou_threshold: 0.7
iterative_refinement_iterations: 12
positive_point_selection_method: kmedoids
negative_point_selection_method: mixed
positive_points_per_mask: -1
negative_points_per_mask: -1
add_other_objects_positive_points_as_negative_points: true
point_tracker_mask_batch_size: 5
use_patch_matching_filtering: false
patch_size: 3
patch_similarity_threshold: 0.01
use_point_reinit: false
reinit_point_tracker_horizon: 8
reinit_horizon: 8
reinit_variant: reinit-on-horizon-and-sync-masks
logging:
wandb:
entity: null
project: demo
tensorboard: true
log_code_path: ${hydra:runtime.cwd}/sam_pt
debug: false
exp_id: debug_72_2023.09.27_00.06.50
frames_path: ${hydra:runtime.cwd}/data/demo_data/bees/
query_points_path: null
longest_side_length: 1024
frame_stride: 1
max_frames: -1
seed: 72
annot_size: 16
annot_line_width: 6
wandb: Currently logged in as: ttanad664. Use wandb login --relogin to force relogin
wandb: wandb version 0.15.11 is available!  To upgrade, please run:
wandb:  $ pip install wandb --upgrade
wandb: Tracking run with wandb version 0.15.3
wandb: Run data is saved locally in C:\Users\ttana\OneDrive - HKUST Connect\Data\Point_tracking\sam-pt\outputs\2023-09-27\00-06-50\wandb\run-20230927_000652-rxqaxdhh
wandb: Run wandb offline to turn off syncing.
wandb: Syncing run debug_72_2023.09.27_00.06.50
wandb:  View project at https://wandb.ai/ttanad664/demo
wandb:  View run at https://wandb.ai/ttanad664/demo/runs/rxqaxdhh
C:\Users\ttana.conda\envs\sam-pt\lib\site-packages\torch\nn\functional.py:3499: UserWarning: The default behavior for interpolate/upsample with float scale_factor changed in 1.6.0 to align with other frameworks/libraries, and now uses scale_factor directly, instead of relying on the computed output size. If you wish to restore the old behavior, please set recompute_scale_factor=True. See the documentation of nn.Upsample for details.
warnings.warn(
How many positive points? 2
How many negative points? 1
Added positive point 1 at (272, 215)
Added positive point 2 at (224, 201)
Added negative point 3 at (401, 236)
Added query points for mask 1, you can now select points for the next mask or press esc to exit.
Added positive point 1 at (274, 174)
Added positive point 2 at (251, 163)
Added negative point 3 at (361, 271)
Added query points for mask 2, you can now select points for the next mask or press esc to exit.
Added positive point 1 at (907, 348)
Added positive point 2 at (911, 326)
Added negative point 3 at (802, 340)
Added query points for mask 3, you can now select points for the next mask or press esc to exit.
Added positive point 1 at (938, 332)
Added positive point 2 at (891, 339)
Added negative point 3 at (767, 334)
Added query points for mask 4, you can now select points for the next mask or press esc to exit.
Added positive point 1 at (904, 277)
Added positive point 2 at (984, 286)
Added negative point 3 at (917, 115)
Added query points for mask 5, you can now select points for the next mask or press esc to exit.
Traceback (most recent call last):
File "C:\Users\ttana.conda\envs\sam-pt\lib\runpy.py", line 194, in _run_module_as_main
return _run_code(code, main_globals, None,
File "C:\Users\ttana.conda\envs\sam-pt\lib\runpy.py", line 87, in _run_code
exec(code, run_globals)
File "C:\Users\ttana\OneDrive - HKUST Connect\Data\Point_tracking\sam-pt\demo\demo.py", line 372, in
main()
File "C:\Users\ttana.conda\envs\sam-pt\lib\site-packages\hydra\main.py", line 94, in decorated_main
_run_hydra(
File "C:\Users\ttana.conda\envs\sam-pt\lib\site-packages\hydra_internal\utils.py", line 394, in _run_hydra
_run_app(
File "C:\Users\ttana.conda\envs\sam-pt\lib\site-packages\hydra_internal\utils.py", line 457, in _run_app
run_and_report(
File "C:\Users\ttana.conda\envs\sam-pt\lib\site-packages\hydra_internal\utils.py", line 220, in run_and_report
return func()
File "C:\Users\ttana.conda\envs\sam-pt\lib\site-packages\hydra_internal\utils.py", line 458, in
lambda: hydra.run(
File "C:\Users\ttana.conda\envs\sam-pt\lib\site-packages\hydra_internal\hydra.py", line 119, in run
ret = run_job(
File "C:\Users\ttana.conda\envs\sam-pt\lib\site-packages\hydra\core\utils.py", line 186, in run_job
ret.return_value = task_function(task_cfg)
File "C:\Users\ttana\OneDrive - HKUST Connect\Data\Point_tracking\sam-pt\demo\demo.py", line 45, in main
rgbs, positive_points_per_mask, query_points = load_data(cfg)
File "C:\Users\ttana\OneDrive - HKUST Connect\Data\Point_tracking\sam-pt\demo\demo.py", line 96, in load_data
return data_loader(
File "C:\Users\ttana\OneDrive - HKUST Connect\Data\Point_tracking\sam-pt\demo\demo.py", line 341, in load_demo_data_interactive
k = cv2.waitKey(1)
KeyboardInterrupt
wandb: Waiting for W&B process to finish... (failed 255). Press Ctrl-C to abort syncing.
wandb:
wandb: Run summary:
wandb: work_dir C:\Users\ttana\OneDr...
wandb:
wandb:  View run debug_72_2023.09.27_00.06.50 at: https://wandb.ai/ttanad664/demo/runs/rxqaxdhh
wandb: Synced 6 W&B file(s), 0 media file(s), 0 artifact file(s) and 0 other file(s)
wandb: Find logs at: .\wandb\run-20230927_000652-rxqaxdhh\logs

After you press escape, you should get a message saying Below is the query point data... and then the inference would run, followed by displaying the segmentation result in the same cv2 window. Since cv2 does not recognize you clicking escape, make sure you have the cv2 window in focus when clicking escape (e.g., clicking on the titlebar puts a window into focus). If this does not work, I'd recommend you consider using a different termination criteria, here is the entry point.

@m43  Hello, after i set HYDRA FULL ERROR=1 in my terminal, the following error appears, could you please answer it for me? Thank you very much!
Traceback (most recent call last):
File "/home/miniconda3/envs/MCG/lib/python3.8/site-packages/hydra/_internal/instantiate/_instantiate2.py", line 92, in _call_target
return target(*args, **kwargs)
File "/root/mediachatgpt/sam_pt/sam_pt/point_tracker/cotracker/tracker.py", line 60, in init
self.model = build_cotracker(self.checkpoint_path)
File "/home/miniconda3/envs/MCG/lib/python3.8/site-packages/cotracker/models/build_cotracker.py", line 25, in build_cotracker
cotracker = CoTracker2(stride=4, window_len=8, add_space_attn=True)
File "/home/miniconda3/envs/MCG/lib/python3.8/site-packages/cotracker/models/core/cotracker/cotracker.py", line 48, in init
self.updateformer = EfficientUpdateFormer(
File "/home/miniconda3/envs/MCG/lib/python3.8/site-packages/cotracker/models/core/cotracker/cotracker.py", line 385, in init
[
File "/home/miniconda3/envs/MCG/lib/python3.8/site-packages/cotracker/models/core/cotracker/cotracker.py", line 386, in
AttnBlock(
File "/home/miniconda3/envs/MCG/lib/python3.8/site-packages/cotracker/models/core/cotracker/blocks.py", line 349, in init
self.mlp = Mlp(
File "/home/miniconda3/envs/MCG/lib/python3.8/site-packages/cotracker/models/core/cotracker/blocks.py", line 62, in init
self.act = act_layer()
File "/home/miniconda3/envs/MCG/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1054, in _call_impl
return forward_call(*input, **kwargs)
TypeError: forward() missing 1 required positional argument: 'input'


refactor(typescript/namespace): reuse TSModuleBlock's scope id

#3460
#3459  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Dunqing and the rest of your teammates on  Graphite

merge conflict

@Dunqing I've made some comments, but I don't fully understand TS namespaces. So feel free to ignore them and merge if you want.
Unless I'm understanding incorrectly, there should always be a TSModuleBlock we can get scope_id from unless the namespace is empty. And if the namespace is empty, we can exit from handle_nested early as the statement just gets deleted. Do I have that right?
If you like, merge this and then I'll have a go at fixing the "binding registered in wrong scope" problem I left unsolved previously, and you could check my work? Maybe that's easier than going back and forth with comments?

Unless I'm understanding incorrectly, there should always be a TSModuleBlock we can get scope_id from unless the namespace is empty. And if the namespace is empty, we can exit from handle_nested early as the statement just gets deleted. Do I have that right?

Yes. That's right.

If you like, merge this and then I'll have a go at fixing the "binding registered in wrong scope" problem I left unsolved previously, and you could check my work? Maybe that's easier than going back and forth with comments?

Sure!


feat(startup): sentry small cleanup

The type of this PR is: Feature

This PR resolves []
Description
I tested on ios.
I would appreciate someone trying out if android builds and shows the app normally for this. I cant seem to log in on my android emu.
The main change here is that I split the hook and the setup parts in two files, so when they get imported they are cleaner with cycles.

also moved the bootstrap env to the index files for a more explicit setup
added the useIdentifyUser, this comes from some work in the unleash PR that will come soon. Having one place to do all the user identification seems helpful.
seems like android didnt have the sentry setup for the app bootstrapping, added that.
made the flag into a devtoggle, seems more fitting there.

PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[ ] I have tested my changes on iOS and Android.
[x] I have added tests/stories for my changes, or my changes don't require testing/stories, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a changelog entry below or my changes do not require one.

To the reviewers 👀

[x] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

small sentry cleanup - pavlos

i think we are good to go 👍


Can't override injectGlobal fonts

I don't want to use the raleway default font and I'm keep geting:
http://localhost:3000/fonts/raleway-v12-latin-regular.woff net::ERR_ABORTED 404 (Not Found)
Any ideas?

Sounds like you have not copied the fonts into your project, so your app cannot find them. Try copying the fonts/ folder from react-skeleton-ui into your React project's public/ folder.
That should get the Raleway fonts to work.
To use another font, you need to: get the webfonts from places like google fonts, copy them similarly to your public/ folder and change the font-face directives in /src/index.js.
You should find them under the injectGlobal function; a long list of @font-face directives. I tend to use google-webfonts-helper, which makes things a lot easier; you can select the font you want, the app gives you code to copy and fonts to download. It even lets you specific what font sizes you want.
Hope that helps.


TXQ offloads are not working

integration_tests/reinvent_dpdk_udp/reinvent_dpdk_udp_integration_test.cpp currently computes and sets the IPV4 checksum because TXQ offloads, which should be able to do this, are not working. This is probably a bug in the setup config. While src/reinvent/dpdk/reinvent_dpdk_initaws.cpp reads the TXQ offload values, and installs it into the DPDK device and per TXQ initialization calls, packets are never delivered. That's why the TXQ offload mask is currently set 0 in scripts/reinvent_dpdk_udp_integration_test

fixed in https://github.com/rodgarrison/reinvent/pull/12


handshakeloss interop test fails for quic-go server because the server closes the connection after 5 seconds

When running the interop test "handshakeloss" against quic-go as the server, the test failed with:
Expected 50 handshakes. Got: 51

Looking at the logs, what seems to be happening here is that, the client is initiating a connection with an INITIAL packet which the quic-go server receives and creates a connection id for that incoming connect request:
2023/12/18 16:13:22 server Changing connection ID to 1a6717dc.
2023/12/18 16:13:22 Created qlog file: /logs/qlog/8d400180b4270a51bc38d805f45311bfc8.qlog
2023/12/18 16:13:22 Adding connection IDs 8d400180b4270a51bc38d805f45311bfc8 and 1a6717dc for a new connection.
2023/12/18 16:13:22 server <- Reading packet 2 (1200 bytes) for connection 8d400180b4270a51bc38d805f45311bfc8, Initial
2023/12/18 16:13:22 server 	Long Header{Type: Initial, DestConnectionID: 8d400180b4270a51bc38d805f45311bfc8, SrcConnectionID: a54057f7bea7cb8e0130976b51be1cbc1a986b61, Token: (empty), PacketNumber: 2, PacketNumberLen: 1, Length: 1153, Version: v1}
...

and responds to that INITIAL packet, with scid = 1a6717dc. Since this is "handshakeloss" test, the simulator drops this response packet from the server and the client never receives it. The client then retransmits that original INITIAL packet, but since this is handshakeloss test, the packet gets dropped and the server never receives that retransmission. This retransmission from the client happens a few more times and those packets get dropped. After 5 seconds (the default HandshakeIdleTimeout) the server closes this client initiated connection:
2023/12/18 16:13:27 Removing connection ID 8d400180b4270a51bc38d805f45311bfc8.
2023/12/18 16:13:27 Removing connection ID 16b1da65.
2023/12/18 16:13:27 Removing connection ID 1a6717dc.
2023/12/18 16:13:27 server accepting stream failed: timeout: no recent network activity
2023/12/18 16:13:27 server Connection 8d400180b4270a51bc38d805f45311bfc8 closed.

A second or two later, the client retransmits the original INITIAL packet, which this time makes it to the server, but since the quic-go server has already closed/aborted the previous connection request, it now creates a new connection id afresh for this incoming retransmitted INITIAL packet:
2023/12/18 16:13:28 server <- Received Initial packet.
2023/12/18 16:13:28 server Changing connection ID to 58750b92.
2023/12/18 16:13:28 Created qlog file: /logs/qlog/8d400180b4270a51bc38d805f45311bfc8.qlog
2023/12/18 16:13:28 Adding connection IDs 8d400180b4270a51bc38d805f45311bfc8 and 58750b92 for a new connection.
2023/12/18 16:13:28 server <- Reading packet 6 (1200 bytes) for connection 8d400180b4270a51bc38d805f45311bfc8, Initial
2023/12/18 16:13:28 server 	Long Header{Type: Initial, DestConnectionID: 8d400180b4270a51bc38d805f45311bfc8, SrcConnectionID: a54057f7bea7cb8e0130976b51be1cbc1a986b61, Token: (empty), PacketNumber: 6, PacketNumberLen: 1, Length: 1153, Version: v1}
...

and responds back with an INITIAL packet with the new connection id it just generated afresh scid = 58750b92
...
2023/12/18 16:13:28 server 	Long Header{Type: Initial, DestConnectionID: a54057f7bea7cb8e0130976b51be1cbc1a986b61, SrcConnectionID: 58750b92, Token: (empty), PacketNumber: 0, PacketNumberLen: 2, Length: 117, Version: v1}
2023/12/18 16:13:28 server 	-> &wire.AckFrame{LargestAcked: 6, LowestAcked: 6, DelayTime: 0s}

As a result, the captured packet trace will have 2 different "scid" values for the same connection that's being handshaked and thus the test fails with:
Expected 50 handshakes. Got: 51

Given that the "handshakeloss" test (intentionally) drops several packets during handshake, would it be better to not use the default HandshakeIdleTimeout (which is 5 seconds) and instead configure a higher value for it when specifically running this test? Something like this in the interop server's main.go:
diff --git a/interop/server/main.go b/interop/server/main.go
index df704462..bd212530 100644
--- a/interop/server/main.go
+++ b/interop/server/main.go
@@ -7,6 +7,7 @@ import (
	"net"
	"net/http"
	"os"
+	"time"

	"github.com/quic-go/quic-go"
	"github.com/quic-go/quic-go/http3"
@@ -51,7 +52,14 @@ func main() {
		Certificates: []tls.Certificate{cert},
		KeyLogWriter: keyLog,
	}
-
+	// for handshakeloss test case, we need to increase the handshakidletimeout
+	// (which by default is 5 seconds), so that the server doesn't forget
+	// the connection after the default 5 seconds, during which time
+	// the handshake may not yet have been established (due to handshake loss)
+	if testcase == "multiconnect" {
+		quicConf.HandshakeIdleTimeout = 30 * time.Second // 30 seconds
+		fmt.Printf("Using HandshakeIdleTimeout: %s\n", quicConf.HandshakeIdleTimeout)
+	}
	switch testcase {
	case "versionnegotiation", "handshake", "retry", "transfer", "resumption", "multiconnect", "zerortt":
		err = runHTTP09Server(quicConf)

With this above change to increase the HandshakeIdleTimeout for this test, the handshakeloss test now passes.
Does this patch look reasonable and if it does, can this be applied to this upstream repo?

Hello Marten @marten-seemann, any thoughts on this one?

I feel uncomfortable matching on "multiconnect", this seems to be the wrong thing to do. We can increase the handshake timeout to 10s though, that should help, right?

Hello Marten,

We can increase the handshake timeout to 10s though, that should help, right?

I just reran the handshakeloss interop test with 10s as the handshake idle timeout on quic-go server. Unfortunately, the connection is still timed out by the server due to being "idle":
2024/01/15 05:39:43 server Destroying connection: timeout: no recent network activity
2024/01/15 05:39:43 Removing connection ID 836feff479fc1f8b3c41e9775608d64c61.
2024/01/15 05:39:43 Removing connection ID 5fc2aa33.
2024/01/15 05:39:43 Removing connection ID d2d600ba.

This handshakeloss test has an extremely high drop-rate of 30%, that too both on server and client endpoint, so it's understandable why the handshake times out:
SCENARIO="drop-rate --delay=15ms --bandwidth=10Mbps --queue=25 --rate_to_server=30 --rate_to_client=30"

I feel uncomfortable matching on "multiconnect", this seems to be the wrong thing to do.

I think I understand why. Would it perhaps be OK if instead of checking for "multiconnect", this change would instead check exactly for the "handshakeloss" test case? I had a similar use case for the client side a while back and in the quic-interop-runner project, I had introduced a tiny enhancement which along with the TESTCASE ("multiconnect" in this case) passes a new TESTCASE_CONTEXT enviroment variable (whose value in this case will be "handshakeloss"). That allows endpoints (server or client or both) to do very specific decisions based on the test case being run. I hadn't proposed that change to the quic-interop-runner repo because I wasn't sure if there would be interest. But for this usecase, perhaps that would help. The patch in the quic-interop-runner would look something like:
diff --git a/docker-compose.yml b/docker-compose.yml
index 496d7aa..0909788 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -41,6 +41,7 @@ services:
       - SSLKEYLOGFILE=/logs/keys.log
       - QLOGDIR=/logs/qlog/
       - TESTCASE=$TESTCASE_SERVER
+      - TESTCASE_CONTEXT=$TESTCASE_CONTEXT
       - VERSION=$VERSION
     depends_on:
       - sim
@@ -69,6 +70,7 @@ services:
       - SSLKEYLOGFILE=/logs/keys.log
       - QLOGDIR=/logs/qlog/
       - TESTCASE=$TESTCASE_CLIENT
+      - TESTCASE_CONTEXT=$TESTCASE_CONTEXT
       - REQUESTS=$REQUESTS
       - VERSION=$VERSION
     depends_on:
diff --git a/interop.py b/interop.py
index a2f06aa..44c3638 100644
--- a/interop.py
+++ b/interop.py
@@ -353,6 +353,7 @@ class InteropRunner:
             "CERTS=" + testcase.certs_dir() + " "
             "TESTCASE_SERVER=" + testcase.testname(Perspective.SERVER) + " "
             "TESTCASE_CLIENT=" + testcase.testname(Perspective.CLIENT) + " "
+            "TESTCASE_CONTEXT=" + testcase.name() + " "
             "WWW=" + testcase.www_dir() + " "
             "DOWNLOADS=" + testcase.download_dir() + " "
             "SERVER_LOGS=" + server_log_dir.name + " "

Then here in quic-go we could have something like:
diff --git a/interop/server/main.go b/interop/server/main.go
index f950f223..afb2adf2 100644
--- a/interop/server/main.go
+++ b/interop/server/main.go
@@ -8,6 +8,7 @@ import (
 	"net/http"
 	"os"
 	"strings"
+	"time"

 	"github.com/quic-go/quic-go"
 	"github.com/quic-go/quic-go/http3"
@@ -57,6 +58,15 @@ func main() {
 	// use http3 server for all tests, if the client
 	// being tested against is the jdk-httpclient
 	useH3Server := strings.Contains(testClient, "jdk-httpclient")
+	// for handshakeloss test case, we need to increase the handshakidletimeout
+	// (which by default is 5 seconds), so that the server doesn't forget
+	// the connection after the default 5 seconds, during which time
+	// the handshake may not yet have been established (due to handshake loss)
+   testcaseContext := os.Getenv("TESTCASE_CONTEXT")
+	if testcaseContext == "handshakeloss" {
+		quicConf.HandshakeIdleTimeout = 30 * time.Second // 30 seconds
+		fmt.Printf("Using HandshakeIdleTimeout: %s\n", quicConf.HandshakeIdleTimeout)
+	}
+
 	switch testcase {
 	case "versionnegotiation", "handshake", "retry", "transfer", "resumption", "multiconnect", "zerortt":
 		if useH3Server {

If you think that the TESTCASE_CONTEXT enhancement to quic-interop-runner is of interest, then I can raise a PR there and once that is merged, I can then repropose this current patch in quic-go to only change the handshake idle timeout for handshakeloss test instead of multiconnect.

I feel like this is fundamentally the wrong way to solve this problem. This would be cheating the test case. A QUIC stack should be able to recover from packet loss without cheating.
You might argue that 30% loss rate is too high. Maybe we should reduce it to 25% or so?

A QUIC stack should be able to recover from packet loss without cheating.

Agreed. And the endpoints do recover from it. Just that our test expectations and the timeouts configured require changes to account for it.

You might argue that 30% loss rate is too high. Maybe we should reduce it to 25% or so?

I'll run some tests locally with a drop rate of 25 instead of 30, on both client and server and see whether it fits the 5 minute test timeout as well as the number of handshake expectations.

There will always be a loss pattern that breaks loss recovery. We actually have the same problem in the integration tests here. We could limit the number of packets are dropped in a row (or in total?), but I haven't spent time on coming with a good heuristic yet.


[Android] When I close the lightbox I get a temporary blank white page

When I close an open lightbox image, it zooms out into its original position, but then displays a white screen for 2-3 seconds before rending the rest of the page, any ideas?

@oblador Could be that Android Modal component requires the property onRequestClose : func to apply the state change to make it not visible anymore. I have run into similar issues with ^0.25


Async with delay unscaled

Should have used timescale parameter
On Sep 27, 2016 13:36, "astro75"<EMAIL_ADDRESS>wrote:

Merged #22 https://github.com/tinylabproductions/tlplib/pull/22.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tinylabproductions/tlplib/pull/22#event-803601872,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAyg1aQh0Kwek6Ify_Y-ZVxAC1tYJAEks5quPGDgaJpZM4KHgf6
.


Quadrotor keeps jumping when flying in altitude mode

Description
The problem occurs in altitude mode whether I switch in-flight or before takeoff. When the robot is taking off, it keep gaining altitude and doesn't come down. If you lower the stick to zero, it keeps climbing but starts jumping in the air. It falls for a few milliseconds and then gains thrust. It keeps repeating this while continuously gaining altitude. Same thing happens if you are flying in manual and you switch to altitude mode.
Reproduction

Switch to altitude mode.
Arm.
Bring throttle to take-off position.
Robot keeps climbing, so you lower the stick to control but nothing happens.
Lower the stick further down to zero, the robot start to jump.
Retake manual control.

Expected behavior
It should just takeoff and hold altitude.
Log Files and Screenshots
https://logs.px4.io/plot_app?log=5ef531fd-d7db-443b-8d76-c330044f0b29
You will clearly see how even when the throttle is at it's lowest position, there are huge spikes in the thrust of the robot as seen in actuator controls.
Drone
The drone is a 165mm quadrotor with 3750kV motors and 3040 Triblade props. It is using a Pixfalcon(also called Pixhawk Mini). The power is supplied by the PDB-ESC Combo.
Additional context
I have used this same setup with Ardupilot stack and it works fine somehow.

Hi @parakhm95 ,
It looks that you forgot to adjust the hover throttle. Since your vehicle has a higher thrust/weight ratio than usual, you should reduce the hover throttle to about 0.3 (from what I see in your log). The parameter is MPC_THR_HOVER.
As shown in the picture below, the land detector "thinks" the drone is touching the ground since the throttle is low compared to the defined hover throttle. It switches in and out of that "ground contact" state and this is why the throttle is jumping around.

I tried the fix you suggested and yes it works! Thank you so much. This has been stuck for a very long time now.
Also, how did you plot these flags? Are they available on the log review online and need to be enabled or do I have to manually find them in the log?
But it works for sure.

@parakhm95 I'm glad it worked out! Those flags are not shown on FlightReview (online tool) since you don't need to check them on a regular basis. To see them, you need to open the file using a program such as PlotJuggler.


explore a way to store the burner on the same origin as starkpilled

Objectives
We would like to know if there is a way to add the wallet on the same origin as the application. The motivations are beyond the scope of that issue and will be discussed. Anyway the goal of that PR is to see if we can move a NextJS app as a pure static app (i.e. no api) on a subdirectory of another app and load it in the iframe.
Success Criterias
The objective here is just to know if that is feasible. We would need:

[x] to see if we can package any react app in '/burner' and not '/' for a website
[x] what is required in the iframe to open `/burner'
[ ] see if we can access the sessionStore in incognito mode if the iframe content is on the same origin as the main app.

Additional Information
That would be interesting to check if anyone has done something like that already and if not, why?

There are 2 ways we can do that. Both seems to work:

we can serve the burner behind a proxy that has a prefix that would be /burner/vx.y.z
we can create an artefact with the keyring that is now a static and add it to /burner/vx.y.z in the public directory of the app in case of react.

I am not use which one is more convenient. There is only one drawback identified, beside the management part of the setup and that is we need to setup the proper CORS with drone so that people can sign the session key and get the project back.


Add att.dataSelecting and add it to symbolDef

This PR implements the result of the discussion in https://github.com/music-encoding/music-encoding/issues/1374
I am marking it a draft PR because I am not sure if the datatype for @select is right. I am actually pretty sure it is not. Any ideas what it should be?

I don't know of any regex or base data type for XPath expressions.  The XSLT 2.0 schema uses the following declaration:
<xs:simpleType name="expression">
  <xs:annotation>
    >xs:documentation>An XPath 2.0 expression</xs:documentation>
  </xsl:annotation>
  <xs:restriction base="xs:token">
    <xs:pattern value=".+"/>
  </xs:restriction>

which I think means "a sequence of characters".  For simplicity's sake, I think we can use:
<attDef ident="select" usage="opt">
  <desc xml:lang="en">XPath used to select data to which an
    element or a property applies.</desc>
  <datatype>
    <rng:data type="token"/>
  </datatype>
</attDef>

The RNG token datatype is preferred over the string datatype because whitespace within the value of @select won't be significant.


How to run cpack

Is it possible to run cpack?

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

ID: c6fa6eec-60ed-0a5c-7f79-a53088cf089e
Version Independent ID: 8a0a6b23-293e-c8c1-79bd-9409b11a8733
Content: CMake build and release task
Content Source: docs/pipelines/tasks/build/cmake.md
Product: devops
GitHub Login: @andyjlewis
Microsoft Alias: alewis

Running a command line tool from a script in CI is a pretty standard thing to do.  I am not sure I would say it is not elegant.


Switch cache directory with a trait to allow other storage backends

First off, thank you so much for this crate and for the quick merges on the pull requests I sent in last night.
I'm building a database which has its own encrypted-at-rest storage available, and I would like to be able to act as the account cache myself. I can manually manage the account and certificates if I drive the process by hand, but I can't use the rustls_helper::order function because that function returns a CertifiedKey which cannot be used to export the private key.
I propose changing the order function to take a trait implementation rather than a Path for the cache, with function calls to load and save accounts and certificates with their keys. The crate can continue to provide a filesystem implementation.
Would you be open to a pull request for this change?

Hi, thanks for contributing!
Yes, that sounds like a good way to deal with it.
A default implementation of the Trait on AsRef<Path> or Path could preserve the current behavior.
I created the rustls_helper::drive_order function just to be able to handle the cert storage myself but I am not to happy with that approach.
So this is actually very welcome.