text:
Coding guidlines

There should be a document about coding guidelines/best practices for tellurium (can be part of the release checklist wiki document).
Some short basic things like

if you write a function/class/module it has to be documented (one sentence + description of input and output arguments)
all variable names are camelCase
code should adhere to PEP8
how to handle logging, exceptions, warnings ? (no idea what I should do at this point to be consistent with how tellurium is handeling things)
...
Currently, things are very divers in the code base.

I would like to remove author names & create date from headers (This is unnecessary information and discourages changes, best described in
https://youtu.be/ZSFDm3UYkeE?t=864 (around 17.10)
Very interesting video and worth a watch for everybody contributing to open source projects.
Can you give me a okay if I can remove names and dates?
M

Some things I notices:

all classes should be new style classes i.e. be subclass of object

class SomeClass(object):
    pass

do imports on top of the module not within functions. The function imports can be packaged even if the import requirements are not full-filled. But will fail on run-time
run the tests after changes! And especially run the tests after packaging Tellurium. In addition do some minimal testing of the packaged version and before shipping. This will find things like #79. A simple

 import tellurium as te

would have revealed the problem.

write tests for things you implement. This will make your life so much easier in the long run.
A first test suite is implemented which can be run via

import tellurium.tests.test_runner as tetest
runner = tetest.TestRunner()
runner.te_passes_tests()

I added a document for coding guidelines to the Wiki
https://github.com/sys-bio/tellurium/wiki/Coding-Guidlines
Important points should be stated there.

repo: sys-bio/tellurium


text:
Fix bad object reference

inlinedLoad has depMap property. inlinedModule is just a string name.

Amazing, thank you for catching this.

sweet!

Yep. I could not make a build. With this fix it works. Thanks!

source: gharchive/pull-request

authors: MeoMix davis guybedford mikz

repo: systemjs/builder

license: mit

license_type: permissive

license_source: bigquery


text:
doc: CLI screencast of popper hands-on exercise

do a screencast (make it a gif for the website) of the hands-on exercise

@shamedian sorry to bother again with this, but I just fixed #183 and, after we release 0.5, the screencast will be outdated. Would it be possible for you to generate it again? BTW, when working on steps:
mkdir mypaper
cd mypaper
git init
echo '# mypaper' > README.md
git add .
git commit -m 'first commit'

can you just do?:
mkdir mypaper
cd mypaper
git init

source: gharchive/issue

repo: systemslab/popper


text:
EISW-48864 - OpenCV linux download error - missing package

There was a problem with downloading ocv package on linux build. Below PR fix mentioned issue.
set IE_PATH_TO_DEPS="http://releases.ti.intel.com/Releases/opencv" if needed to build linux package
Linux job: https://vpu-validation-ci-icv.ir.intel.com/job/Utils/job/Build_VPUX_Plugin/job/Linux/81/
Windows job: https://vpu-validation-ci-icv.ir.intel.com/job/Utils/job/Build_VPUX_Plugin/job/Windows/25/

This is covered already through: https://github.com/sysvpujenks/openvino/pull/3
Reviewed with @JakubPalIntel, @KrzysztofPatynaIntel, @razvanandras, @RazvanLacatusu
and agree https://github.com/sysvpujenks/openvino/pull/1 & https://github.com/sysvpujenks/openvino/pull/2 are covered by https://github.com/sysvpujenks/openvino/pull/3

repo: sysvpujenks/openvino

license_source: github-api


text:
ユーザーページで10個目以降の投稿を読み込めない

💡 Summary
いっぱい400
https://misskey.io/notes/7rlugxy3gw

ローカルだと再現しなくてウケる

ローカルだと再現しな

私も

ioの問題そう

何らかの原因で https://github.com/syuilo/misskey/commit/b357afa30a6f6420218ad80b9a731dc379e1fd36#diff-4c7833e09c839d22f0e87854bcdb7ad6 が適応されてなさそう

ですね

情報です
https://misskey.io/notes/7rna7p8546

完全に謎

ローカルだと再現しない謎

この問題直してほしいとよく言われるけどローカルで再現しないし、コード見ても発生するはずなさそうなのでどうしたらいいか困ってる

5511b6e0136ee3f585527d0371268556265811b7 が適用されたので確認してみたら、恐らく直ってそう
@ Firefox 68.0b2 (64 ビット) / Misskey 11.18.0

authors: Simiralin mei23 rinsuki syuilo tamaina

repo: syuilo/misskey

license: MIT


text:
Source tarball size increased from 4 KB to 4.6 MB

The source tarball for checkssl 0.2 is about 4 KB, while the source tarball for version 0.3 is about 4.6 MB. It seems this increase was mainly caused by the addition of binaries under lambda/testmain. Do these binaries need to be in the repository and release tarball, or have these been added unintentionally maybe? I'm not sure, just thought I'd ask.

Thank you for pointing that out, yes it was a mistake to add to git. I pushed out a 0.3.1 tag but to be honest there aren't many downloads of checkssl, I would be open to moving the release tag 0.3 if that helps you any since functionally they are the same.

Thank you for pointing that out, yes it was a mistake to add to git. I pushed out a 0.3.1 tag but to be honest there aren't many downloads of checkssl, I would be open to moving the release tag 0.3 if that helps you any since functionally they are the same.

I maintain the checkssl port for MacPorts and MacPorts servers cache the tarballs, which is how I noticed. But I’d say there is no hurry to do another release now if this is fixed for future releases.

I maintain the checkssl port for MacPorts and MacPorts servers cache the tarballs, which is how I noticed. But I’d say there is no hurry to do another release now if this is fixed for future releases.

authors: breun szazeski

repo: szazeski/checkssl


text:
[WIP] Added AuthorityFactory

refs #14

@gakuzzzz Are you planning on merging this?

@gakuzzzz This doesn't seem to have been merged.

Sorry, late replay.
I'm not confident if this is the good way......
I think maybe there is more better solution...

authors: gakuzzzz samco


text:
bug: type error with new module "next-auth" in auth.ts

Provide environment information
System:
OS: Windows 10 10.0.19044
CPU: (48) x64 AMD Ryzen Threadripper 3960X 24-Core Processor
Memory: 48.73 GB / 63.90 GB
Binaries:
Node: 18.14.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
npm: 9.3.1 - C:\Program Files\nodejs\npm.CMD
 "ct3aMetadata": {
    "initVersion": "6.11.4"
  }

Describe the bug
I am manually updating my scaffolding to the latest T3 version. The issue is in auth.ts, specifically with this code:
declare module 'next-auth' {
  interface Session extends DefaultSession {
    user: {
      id: string
      // ...other properties
      // role: UserRole;
    } & DefaultSession['user']
  }

  // interface User {
  //   // ...other properties
  //   // role: UserRole;
  // }
}

I receive the following error:
(property) Session.user?: {
    id: string;
} & {
    name?: string | null | undefined;
    email?: string | null | undefined;
    image?: string | null | undefined;
}
All declarations of 'user' must have identical modifiers.ts(2687)

Error goes away if I make user optional, but I'm not really sure how that will effect things down the line:
declare module 'next-auth' {
  interface Session extends DefaultSession {
    user?: {
      id: string
      // ...other properties
      // role: UserRole;
    } & DefaultSession['user']
  }

  // interface User {
  //   // ...other properties
  //   // role: UserRole;
  // }
}

Reproduction repo
n/a
To reproduce
see above
Additional information
No response

UPDATE: I forgot to take out the old next-auth.d.ts


text:
Fw memory optimization

Issues

Fixes #188

Description

Reduced item name size from 36 to 24.
Adjusted send, receive, encode and decode buffers to fit exactly the longest messages we have.

Before:
RAM:   [======    ]  63.5% (used 1300 bytes from 2048 bytes)
Flash: [========  ]  79.9% (used 24542 bytes from 30720 bytes)
After:
RAM:   [=====     ]  49.5% (used 1014 bytes from 2048 bytes)
Flash: [========  ]  79.9% (used 24542 bytes from 30720 bytes)
Types of changes
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[X] Requested changes are in a branch
[X] Compiled and tested requested changes on target hardware (PC, device)
[X] Updated the documentation, if necessary
[x] Updated the LICENSES file, if necessary
[x] Reviewed the guidelines for contributing to this repository

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

After approving your changes I realized that long items name scrolling was corrupted because we absolutely need a \0 to determine string end on the Arduino side or we will scroll some random characters on the display.

Fantastic, thank you!


text:
[BUG] Player tags show only HP, but not the name or ID.

txAdmin/FXServer versions:
tx: v4.13.3
fxs: 5411
Describe the bug
Player tags show only HP, but not the name or ID.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots

Additional context
Posted by @DerPeter77#9543 on discord.
Report states this happened on normal player id view instead of on spectate mode.
Server is infinity with 128 slots.

[  script:es_extended] [WARNING] Server callback "relisoft_tag:getAdminsPlayers" does not exist. Please Check The Server File for Errors!
This is in the console.

I have now the solution: you have to download relisoft nametags and put it in the es_extended folder and name it: relisoft_tag:getAdminsPlayers

This esx thing is likely not related.

I tested now everything and if I restart es_extended in game then it works but only then and I can`t restart every time es_extended in game

@PC1up Yeah i'm pretty sure you are correct, this is another resource hiding the player IDs.
Furthermore, this is stale so I'm closing it.

repo: tabarra/txAdmin


text:
Proposed Recommendation: empty status

Okay so CSSWG does not go to Proposed Rec very often, this stage is likely not tested super much but:

Status of this document

Table of Contents

Notice the totally empty status section. No copyright, no patent section nothing.
Meanwhile I'm going to paste in status from a recent CR and manually hack on it until the pubrules checker stops complaining, but this needs to be fixed at some point.

Oh, this is what is in the .bs
Shortname: css-ui
Level: 3
Group: csswg
Status: PR
Date: 2017-12-14
Deadline: 2018-01-23
Prepare for TR: yes
Work Status: stable

repo: tabatkins/bikeshed


text:
Actual results for some TDVT datename.sow and datepart.sow test cases are correct but do not match any expected results

About You:
Name: Michael Habiger
Company: Actian Corporation
Your question:
These test cases are returning correct actual results, but do not match any of the expected results.

Test Name
Test Case

date.datename.sow.week
DATENAME('week', [date2], 'monday')

date.datepart.sow.week
DATEPART('week', [date2], 'monday')

Checking the operations manually using the definition for ISO week date and using various ISO 8601 "week of year" calculators on the web indicates that the actual results are correct and that a few of the TDVT expected values are incorrect.
Environment:
MS Windows 10 Enterprise
Tableau Desktop 2023.2
Connector SDK repository cloned from master branch on Sep 20, 2023
Actian JDBC Tableau Connector (development/testing)
Actian Vector 6.3 on Ubuntu 20.04 LTS
Request:
We would like to request that a new expectation file be added (or an existing one be updated?) to match the Actian results.
Actian TDVT Actual Results:
actual.setup.date.datename.sow.week.txt
actual.setup.date.datename.sow.week_diff.txt
actual.setup.date.datepart.sow.week.txt
actual.setup.date.datepart.sow.week_diff.txt
Relevant Expected Results Files:
expected.setup.date.datename.sow.week.txt
expected.setup.date.datename.sow.week.1.txt
expected.setup.date.datename.sow.week.2.txt
expected.setup.date.datepart.sow.week.txt
expected.setup.date.datepart.sow.week.1.txt
expected.setup.date.datepart.sow.week.2.txt

Hi @hab6 could you bring this conversation to your internal repo? Let's continue the conversation there - it looks like the test cases is right and there may be an implementation issue in the dialect file.

@lukewrites Issue 2 in our internal repo has been updated with details.

repo: tableau/connector-plugin-sdk


text:
Overwrite workbook with the Update Workbook Endpoint

When moving a workbook from one project to another using the Update Workbook Endpoint, if there is a workbook in a project with the same name I get the following error:
summary: [ 'Resource Conflict' ]
What I would like to see is an attribute to overwrite the workbook in the destination project.
Example:
<tsRequest>
    <workbook showTabs="show-tabs-flag" overwrite="true" >
        <project id="new-project-id" />
        <owner id="new-owner-id" />
    </workbook>
</tsRequest>

Note: The reason why this would be really helpful is that workbooks in the destination project (Prod) are all embedded in a public website via the URL via Trusted Ticketing. The Workbook with the same name in the original folder (Dev) has a different URL than in Prod. Deleting the workbook from Prod and then moving the Dev version, results in updating ht HTML on the website due to how Tableau Server handles multiple workbooks with the same name in different projects.

Hey guys? Is there any word on this?

Workbook names have always been unique in a project.  Need to consider options here carefully as it could have unintended side effects.

I don't think we will ever implement this, because we aren't sure if it would break things.
One workaround might be to download and re-publish the new workbook with the same name - there is an overwrite flag for publishing.

authors: irwando jacalata landonconover

repo: tableau/server-client-python


text:
load: report concise error if JSON file syntax is illegal

Problem
JSON syntax error:

Load report error: proto: syntax error (line 35:17): unexpected token "5"
Solution
error message should include:

json file path
indicate json syntax error

ItemConf.json:
{
    "itemMap": {
        "1": {
            "id": 1,
            "num": 100
        },
        "2": {
            "id": 2,
            "num": 200
        } // here missing ","
        "3": {
            "id": 3,
            "num": 300
        }
    }
}

Wanted error message:
error[E0002]: cannot unmarshal file content to given proto.Message
Reason: failed to unmarshal file "..\testdata\unittest\conf\ItemConf.json" to message "ItemConf": proto: syntax error (line 11:9): unexpected token "3"
Help: check the file content format is correct

repo: tableauio/tableau


text:
Reduce logging level to :warn for auth errors

The "Request was closed prematurely" exception is triggered fairly
frequently during synchronization worker loops, and doesn’t seem to
represent anything actionable. Since we handle it at the sync level by
retrying the entire processing loop, it should be sufficient to log the
exception at the :warn level and proceed as usual.

:+1:

authors: ahorner rdunlop

repo: tablexi/restforce-db


text:
Adding feature - support of XChaCha20+Poly1305 algorithms for SecretBox processing

Original libsodium library supports XChaCha20+Poly1305 algorithm for SecretBox processing. It would be nice to add this feature to Sodium.Core also; and it's rather easy to do so because requres only trivial wrapping.
So, then a user would have an option to choose between the default algorithm (XSalsa20+Poly1305) and XChaCha20+Poly1305 algorithm:

Please review the suggeted changes, I expect no difficulties there. Though just please pay attention to two chunks marked with "todo" (you will definitely understand quickly the reason of my doubt; most likely, these chunks are just not needed for XChaCha20+Poly1305 therefore i've commented them out, and I will delete them completely after your confirmation).
So, I hope your review will not consume much of your time.
(We would like to migrate from original library to Sodium.Core, but we urgently need the abovementioned functionality to do this).

Hi, @tabrath. Could you please help us with AppVeyor? It fails for all recent pull requests. It looks like there is just something wrong with its settings.

Hi, @tabrath. Could you please help us with AppVeyor? It fails for all recent pull requests. It looks like there is just something wrong with its settings.

I can foresee someone having to fork this repo just like how libsodium-net was forked since tabrath doesn't seem to be very active.

@samuel-lucas6 @Lesnik4u you 2 can check my libsodium binding instead. It's called ASodium (could be found on nuget as well).

Since libsodium-core is now in maintenance mode, I'm not sure if this is still something that should be added. Please feel free to open a new issue if you think it is.

repo: tabrath/libsodium-core


text:
Recent time vs overall time

I guess its more of an steam problem but i just wanted to ask.
My overall time does not match up with the recent time after using your script.

Sorry it's german the picture displays 27 minutes recent time and 1 minute overall time. (Which makes no sense)
Did you also encounter this issue? It happens to every game i used your script for.
Thanks for the good script and your work!

Okay it's taking steam a while to sync to the overall playtime if you use the api.

Ah, I'm glad it's working for you now

I never checked the recent time - I've only used this tool to have a ridiculous amount of hours in certain games, and "Last 2 weeks" in my profile 🙂

Btw the limit is capped to 32 games which you can 'play' at the same time :)

authors: WastedFreeTime tacheometry

repo: tacheometry/steam-hour-farmer


text:
Problems of SMPL/SMPL+D Registration

@taconite
Hi, taconite
When I run the command python smpl_registration/fit_SMPLD_PTFs.py --num-joints 24 --use-parts --init-pose configs/cape/${config}.yaml, the output logs are as follows:
(PTF) ang@ang-All-Series-Invalid-entry-length-16-Fixed-up-to-11:/media/ang/PTF-main$ python smpl_registration/fit_SMPLD_PTFs.py --num-joints 24 --use-parts --init-pose configs/cape/ptf_decoder-width-256-128_ptfs-width-256-128_full-smpl_ce-ce_w-skin-1e-1_conv-encoder_hidden-256_plane64x3_softmax_npts-5000_CAPE-release-with-aug-trans_1gpus.yaml
Warning: unable to import datasets/nusc:
No module named 'nuscenes'
Traceback (most recent call last):
File "/media/ang/PTF-main/kaolin/kaolin/datasets/init.py", line 11, in
from .nusc import NuscDetection
File "/media/ang/PTF-main/kaolin/kaolin/datasets/nusc.py", line 21, in
from nuscenes.utils.geometry_utils import transform_matrix
ModuleNotFoundError: No module named 'nuscenes'
Warning: unable to import datasets/nusc:
None
Using BLB SMPL from the project: LearningRegistration
/media/ang/PTF-main/im2mesh/config.py:19: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
cfg_special = yaml.load(f)
/media/ang/PTF-main/im2mesh/config.py:30: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
cfg = yaml.load(f)
0%|                                                                                | 0/331 [00:00<?, ?it/s](6890, 3, 10)
/media/ang/PTF-main/smpl_registration/lib/smpl_layer.py:54: UserWarning: The given NumPy array is not writeable, and PyTorch does not support non-writeable tensors. This means you can write to the underlying (supposedly non-writeable) NumPy array using the tensor. You may want to copy the array to protect its data or make it writeable before converting it to a tensor. This type of warning will be suppressed for the rest of this program. (Triggered internally at  /opt/conda/conda-bld/pytorch_1595629403081/work/torch/csrc/utils/tensor_numpy.cpp:141.)
torch.Tensor(smpl_data['betas'].r).unsqueeze(0))
Optimizing SMPL global orientation                                                                             | 0/30 [00:00<?, ?it/s]
Iter: 29, s2m: 0.1590, m2s: 0.2704, betas: 0.0418, pose_pr: 0.0004, part: 0.5812: 100%|██████████████| 30/30 [05:54<00:00, 11.83s/it]
Iter: 29, s2m: 0.1590, m2s: 0.2704, betas: 0.0418, pose_pr: 0.0004, part: 0.5812: 100%|██████████████| 30/30 [05:54<00:00, 12.03s/itOptimizing SMPL pose only                                                                                | 0/30 [00:00<?, ?it/s]
Iter: 29, s2m: 0.0200, m2s: 0.0064, betas: 0.0014, pose_pr: 0.0003, part: 0.0155: 100%|██████████████| 30/30 [06:05<00:00, 12.19s/it]
Iter: 29, s2m: 0.0203, m2s: 0.0030, betas: 0.0002, pose_pr: 0.0003, part: 0.0078: 100%|██████████████| 30/30 [06:16<00:00, 12.54s/it]
** Optimised smpl pose **s: 0.0030, betas: 0.0002, pose_pr: 0.0003, part: 0.0078: 100%|██████████████| 30/30 [06:16<00:00, 12.48s/it]
Iter: 29, s2m: 0.0095, m2s: 0.0105, betas: 0.0007, pose_pr: 0.0008, part: 0.0287: 100%|██████████████| 30/30 [06:17<00:00, 12.59s/it]
Iter: 29, s2m: 0.0131, m2s: 0.0035, betas: 0.0004, pose_pr: 0.0004, part: 0.0107: 100%|██████████████| 30/30 [06:19<00:00, 12.64s/it]
Iter: 29, s2m: 0.0176, m2s: 0.0023, betas: 0.0006, pose_pr: 0.0003, part: 0.0071: 100%|██████████████| 30/30 [06:18<00:00, 12.63s/it]
** Optimised smpl pose and shape ** betas: 0.0006, pose_pr: 0.0003, part: 0.0071: 100%|██████████████| 30/30 [06:18<00:00, 12.87s/it]
Lx100. Iter: 9, s2m: 0.0023, m2s: 0.0032, lap: 0.0007, offsets: 0.0044: 100%|████████████████████████| 10/10 [02:11<00:00, 13.18s/it]
Lx100. Iter: 9, s2m: 0.0010, m2s: 0.0015, lap: 0.0004, offsets: 0.0038: 100%|████████████████████████| 10/10 [02:13<00:00, 13.35s/it]
Lx100. Iter: 9, s2m: 0.0004, m2s: 0.0008, lap: 0.0002, offsets: 0.0039: 100%|████████████████████████| 10/10 [02:08<00:00, 12.87s/it]
Lx100. Iter: 9, s2m: 0.0002, m2s: 0.0005, lap: 0.0001, offsets: 0.0041: 100%|████████████████████████| 10/10 [02:08<00:00, 12.90s/it]
Lx100. Iter: 9, s2m: 0.0001, m2s: 0.0004, lap: 0.0001, offsets: 0.0042: 100%|████████████████████████| 10/10 [02:09<00:00, 12.94s/it]
Inner distance for input shortlong_ATUsquat.000001: 0.01631784997880459 cm0%|████████████████████████| 10/10 [02:09<00:00, 12.87s/it]
Outer distance for input shortlong_ATUsquat.000001: 0.017044199630618095 cm
Inner distance for input shortlong_ATUsquat.000006: 0.013444711454212666 cm
Outer distance for input shortlong_ATUsquat.000006: 0.014601950533688068 cm
Inner distance for input shortlong_ATUsquat.000011: 0.015537642873823643 cm
Outer distance for input shortlong_ATUsquat.000011: 0.0160372331738472 cm
Inner distance for input shortlong_ATUsquat.000016: 0.014674867503345013 cm
Outer distance for input shortlong_ATUsquat.000016: 0.015363145619630814 cm
Inner distance for input shortlong_ATUsquat.000021: 0.013980861753225327 cm
Outer distance for input shortlong_ATUsquat.000021: 0.014812660403549671 cm
Inner distance for input shortlong_ATUsquat.000026: 0.014417361468076706 cm
Outer distance for input shortlong_ATUsquat.000026: 0.014523924328386784 cm
Inner distance for input shortlong_ATUsquat.000031: 0.014444430358707905 cm
Outer distance for input shortlong_ATUsquat.000031: 0.015400375239551067 cm
Inner distance for input shortlong_ATUsquat.000036: 0.014390168711543083 cm
Outer distance for input shortlong_ATUsquat.000036: 0.014232808724045753 cm
Inner distance for input shortlong_ATUsquat.000041: 0.01653471030294895 cm
Outer distance for input shortlong_ATUsquat.000041: 0.017072072252631187 cm
Inner distance for input shortlong_ATUsquat.000046: 0.01617429219186306 cm
Outer distance for input shortlong_ATUsquat.000046: 0.015451897867023945 cm
Inner distance for input shortlong_ATUsquat.000051: 0.01808827929198742 cm
Outer distance for input shortlong_ATUsquat.000051: 0.017144061625003815 cm
Inner distance for input shortlong_ATUsquat.000056: 0.016339648514986038 cm
Outer distance for input shortlong_ATUsquat.000056: 0.016375551000237465 cm
0%|▎                                                                                | 1/331 [48:37<267:23:39, 2917.03s/it](6890, 3, 10)
Optimizing SMPL global orientation                                                                             | 0/30 [00:00<?, ?it/s]
Iter: 15, s2m: 0.8738, m2s: 1.0011, betas: 0.0114, pose_pr: 0.0014, part: 3.3756:  53%|███████▍      | 16/30 [04:05<03:34, 15.29s/it]
.....
It seems that there're 2 problems:
1) No module named 'nuscenes':
Is it matters? We do not use the nuscenes dataset after all.
2) PTF-main/smpl_registration/lib/smpl_layer.py:54: UserWarning: The given NumPy array is not writeable, and PyTorch does not support non-writeable tensors.
Although it warns, it can output the registration .ply files. I wonder if I can ignore the warning?
Thanks in advance, and look forward to your reply!

Hi, Bingoang
Sorry for the late reply, I was busy preparing our NeurIPS presentation and code release

This should not affect the code; it is some optional dependency of kaolin, which we never actually used.
You can ignore the warning since these underlying numpy arrays were never directly modified after creation.

best,
Shaofei

@taconite
Thanks very much for your reply, and looking forward to your new interesting works!

authors: Bingoang taconite

repo: taconite/PTF


text:
Unify the format of when and others

when
others

dict
d['key']
d[key]

access
d.prop or d[prop]
d[prop]

did_challenge/tag
reqs2reqs/rename
final/slack
empty_guard

repo: tadashi-aikawa/jumeaux


text:
Landmarks in cavas are not showing up

When we do a landmark search, headers in canvas are not showing up.
Here is the configuration

Hi, @ShravanSunder :)
I think that feature has not been implemented because, in canvas mode, it is assumed that getting information about the files in the node would be impossible. Someday, when that becomes possible, I will consider implementing it.

@tadashi-aikawa that makes sense.  I just noticed there's no hash for canvas files in fileCache.  And i guess no metadata 😢

authors: ShravanSunder tadashi-aikawa


text:
Using : class on protocols is deprecated

https://github.com/tadija/AELog/blob/f559b3014d234c3997dc6272d9b29d705b6933c3/Sources/AELog/Log.swift#L57
This particular line is giving a warning while compiling on Xcode 13.2.1, as using protocol SomeProtocol: class {} is now deprecated.
Changing it to protocol SomeProtocol: AnyObject {} is the suggested way of updating it, according to Xcode. The warning message says:
Using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead

Hi @alejandroivan, thanks for reporting, this is now fixed in the latest release (0.6.3).

authors: alejandroivan tadija

repo: tadija/AELog


text:
Updating for Xcode 9.3 and Swift 4.1

Three changes in Element.Swift from flatMap to the equivalent compactMap for Swift 4.1 compliance (otherwise would produce three deprecation warnings)

Updating AEXML and demo project to recommended Xcode 9.3 build settings. This just adds two Objective-C clang warnings that have no effect on AEXML (which is all Swift) but will silence the build warnings

Xcode 9.3, according to release notes, now adds a IDEWorkspaceChecks.plist file,

... to store the state of necessary workspace checks. Committing this file to source control will prevent unnecessary rerunning of those checks for each user opening the workspace.

Podspec and .swift-version now show a Swift version of 4.1 instead of 4.0

Hi, thanks for the efforts! This is merged now in 4.3.0.

authors: lightbow tadija

repo: tadija/AEXML


text:
Handle thing like "key" : null and number in json that supposed to ma…

…p to Int but passed as string ("key" : "123"

Can you add some tests for that? I don't really see the usecase from the description

Oh right, that should be clearer now :)

I think this will be fixed by #23

#23 seems to do a similar thing, but it seems like the tests from this one don't pass on it.
First one in t/any.t: { json => '{ "any-attr" : null }', value => Any, type => Any }. We currently get Mu instead. I think I'd rather have Any in there, opinions? @jonathanstowe
As for the second failing test, in t/types.t: I don't think "42" should unpack into an Int 42. The test now fails, and, imho, rightfully so. @Skarsnik?

I think my issue was when playing around with Discord API, big int number (ID in Discord case see https://github.com/Skarsnik/perl6-discord/blob/master/lib/Discord/User.pm6#L4) were passed as string because JSON probably does not support then as int. But I wanted to have them typed as Int in my class.

I'm cool with Any, I think the Mu is probably a result of the way the multis pan out, JSON::Fast gives an Any there, I'll take a look later.

authors: Skarsnik jonathanstowe tadzik

repo: tadzik/JSON-Unmarshal


text:
'odict_keys' object does not support indexing

When I execute the following code:
In [1]: import tensorflow as tf
/usr/software/anaconda3/lib/python3.6/importlib/_bootstrap.py:219: RuntimeWarning: compiletime version 3.5 of module 'tensorflow.python.framework.fast_tensor_util' does not match runtime version 3.6
  return f(*args, **kwds)
imp
In [2]: import tensornets as nets

In [3]: inputs = tf.placeholder(tf.float32, shape=[1, 224, 224, 3])

In [4]: model = nets.DenseNet121(inputs)

In [5]: with tf.Session() as sess:
   ...:     nets.pretrained(model)

I encountered the following errors:
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-6-ba1220a3288a> in <module>()
      1 with tf.Session() as sess:
----> 2     nets.pretrained(model)
      3

/usr/software/anaconda3/lib/python3.6/site-packages/tensornets-0.1.0-py3.6.egg/tensornets/pretrained.py in pretrained(scopes)
     47         model_name = parse_scopes(scope)[0]
     48         try:
---> 49             __load_dict__[model_name](scope)
     50         except KeyError:
     51             found = False

/usr/software/anaconda3/lib/python3.6/site-packages/tensornets-0.1.0-py3.6.egg/tensornets/pretrained.py in load_densenet121(scopes)
    280         cache_subdir='models',
    281         file_hash='9817430b1d3634645f6b04b8c663c34f')
--> 282     return load_torch_weights(scopes, weights_path)
    283
    284

/usr/software/anaconda3/lib/python3.6/site-packages/tensornets-0.1.0-py3.6.egg/tensornets/utils.py in load_torch_weights(scopes, weights_path, move_rules)
    203     for (i, name) in enumerate(names):
    204         if 'running_mean' in name:
--> 205             names[i-1], names[i-2] = names[i-2], names[i-1]
    206
    207     values = []

TypeError: 'odict_keys' object does not support indexing

How could I solve this problem? Thanks!

The problem is solved by adding Python 3 compatibility (see codes). In Python 2, keys() of a class collections.OrderedDict returns a list but a odict_keys in Python 3. Thank you for reporting the issue, @auroua!

authors: auroua taehoonlee

repo: taehoonlee/tensornets


text:
feat(intersection-observer): migrate to SafeObserver

Closes #

There is a similar issue in MutationObserver.
We need to make the same changes over there and switch to SafeObserver.
https://github.com/taiga-family/ng-web-apis/issues/524

authors: MillerSvt pppdns

repo: taiga-family/ng-web-apis


text:
Add unstable --print-command-list flag

Closes #172
 --print-command-list
    Print commands without run (Unstable).

$ cargo hack check --each-feature --include-deps-features --print-command-list
cargo check --manifest-path Cargo.toml --no-default-features
cargo check --manifest-path Cargo.toml --no-default-features --features anyhow/backtrace
cargo check --manifest-path Cargo.toml --no-default-features --features anyhow/default
cargo check --manifest-path Cargo.toml --no-default-features --features anyhow/std
cargo check --manifest-path Cargo.toml --no-default-features --features ctrlc/termination
cargo check --manifest-path Cargo.toml --no-default-features --features indexmap/arbitrary
cargo check --manifest-path Cargo.toml --no-default-features --features indexmap/quickcheck
cargo check --manifest-path Cargo.toml --no-default-features --features indexmap/rayon
cargo check --manifest-path Cargo.toml --no-default-features --features indexmap/rustc-rayon
cargo check --manifest-path Cargo.toml --no-default-features --features indexmap/serde
cargo check --manifest-path Cargo.toml --no-default-features --features indexmap/serde-1
cargo check --manifest-path Cargo.toml --no-default-features --features indexmap/std
cargo check --manifest-path Cargo.toml --no-default-features --features indexmap/test_debug
cargo check --manifest-path Cargo.toml --no-default-features --features indexmap/test_low_transition_point
cargo check --manifest-path Cargo.toml --no-default-features --features libc/align
cargo check --manifest-path Cargo.toml --no-default-features --features libc/const-extern-fn
cargo check --manifest-path Cargo.toml --no-default-features --features libc/default
cargo check --manifest-path Cargo.toml --no-default-features --features libc/extra_traits
cargo check --manifest-path Cargo.toml --no-default-features --features libc/rustc-dep-of-std
cargo check --manifest-path Cargo.toml --no-default-features --features libc/rustc-std-workspace-core
cargo check --manifest-path Cargo.toml --no-default-features --features libc/std
cargo check --manifest-path Cargo.toml --no-default-features --features libc/use_std
cargo check --manifest-path Cargo.toml --no-default-features --features serde_json/alloc
cargo check --manifest-path Cargo.toml --no-default-features --features serde_json/arbitrary_precision
cargo check --manifest-path Cargo.toml --no-default-features --features serde_json/default
cargo check --manifest-path Cargo.toml --no-default-features --features serde_json/float_roundtrip
cargo check --manifest-path Cargo.toml --no-default-features --features serde_json/indexmap
cargo check --manifest-path Cargo.toml --no-default-features --features serde_json/preserve_order
cargo check --manifest-path Cargo.toml --no-default-features --features serde_json/raw_value
cargo check --manifest-path Cargo.toml --no-default-features --features serde_json/std
cargo check --manifest-path Cargo.toml --no-default-features --features serde_json/unbounded_depth
cargo check --manifest-path Cargo.toml --no-default-features --features slab/default
cargo check --manifest-path Cargo.toml --no-default-features --features slab/serde
cargo check --manifest-path Cargo.toml --no-default-features --features slab/std
cargo check --manifest-path Cargo.toml --no-default-features --features toml_edit/default
cargo check --manifest-path Cargo.toml --no-default-features --features toml_edit/easy
cargo check --manifest-path Cargo.toml --no-default-features --features toml_edit/perf
cargo check --manifest-path Cargo.toml --no-default-features --features toml_edit/serde

I think this looks great 👏🏻. I think the output looks good. I haven't entirely figured out the best way yet to chunkify the output into batches to then build into a matrix, but I'm going to give that a try next week.

@taiki-e Thoughts on including this in a release?

I think the +<toolchain> in the output should be removed as it limits the reusability of the output, but once that is done, I think we can merge this

bors r+

I think the +<toolchain> in the output should be removed as it limits the reusability of the output,

Maybe whether it is provided in the prior or not should be based on if it is explicitly set in the input command?

Maybe whether it is provided in the output or not should be based on if it is explicitly set in the input command?

No, it just displayed the toolchain currently in use. +<toolchain> specified by the user precedes the subcommand, and cargo passes the corresponding cargo for that toolchain as a CARGO environment variable to the subcommand. So, it is not always easy to determine if +<toolchain> was specified by the user.

Published in 0.5.28.

FYI, --partition added in https://github.com/taiki-e/cargo-hack/pull/253 is the way that can replace this in most use cases and is much easier to use.

authors: leighmcculloch taiki-e

repo: taiki-e/cargo-hack


text:
Use -Clink-dead-code

Fixes #21
The unstable book says that unused functions are also instrumented, but it seems that -Clink-dead-code is also needed.
https://doc.rust-lang.org/nightly/unstable-book/compiler-flags/instrument-coverage.html#-z-instrument-coverageoptions

-Z instrument-coverage=all: Instrument all functions, including unused functions and unused generics. (This is the same as -Z instrument-coverage, with no value.)

The unstable book says that unused functions are also instrumented, but it seems that -Clink-dead-code is also needed.
https://doc.rust-lang.org/nightly/unstable-book/compiler-flags/instrument-coverage.html#-z-instrument-coverageoptions

-Z instrument-coverage=all: Instrument all functions, including unused functions and unused generics. (This is the same as -Z instrument-coverage, with no value.)

FYI @richkadel If this is not the intended behavior.

I don't think -Clink-dead-code should have any impact.
In fact, that option is known to break the coverage workflow in some cases (particularly on MSVC/Windows builds).
Why, what makes you think it is operating differently without that option?

Ah, I just reviewed your updated test. Correct me if I'm wrong. It looks like you are adding -Clink-dead-code in order to get coverage for an entire mod. Apparently, without it, coverage ignores the file or ignores the mod (I'm not sure which).
That should be filed as an issue against rust-lang/rust and maybe I can figure out how to get coverage to include unused mods / files without requiring the troublesome -Clink-dead-code.
I would advise against adding -Clink-dead-code for coverage, or make it opt-in with a warning to "use at your own risk".
Thoughts?

Thanks for your advice! I opened https://github.com/rust-lang/rust/issues/86177 to report this problem.
And for -Clink-dead-code, I'll revert this PR and mention the known workarounds and how they are likely to cause another problem.

authors: richkadel taiki-e

repo: taiki-e/cargo-llvm-cov


text:
Story discovering failed:  [ConfigError: [BABEL] unknown file: Preset /* your preset */ requires a filename to be set when babel is called directly

I could work around this problem by moving my babel config out of the root dir and reference it by the other tooling that needs it (e.g. Webpack, Jest, …). I don't expect a fix per se, but reporting nevertheless in case someone else runs into this issue. :)

Describe the bug
Adding MDX file with project that have babel config fails upon startup like so:
   ╭───────────────────────────────────────────────────╮
   │                                                   │
   │   🥄 Ladle.dev served at http://localhost:4123/   │
   │                                                   │
   ╰───────────────────────────────────────────────────╯

Story discovering failed:

ConfigError: [BABEL] unknown file: Preset /* your preset */ requires a filename to be set when babel is called directly,

babel.transformSync(code, { filename: 'file.ts', presets: [/* your preset */] });

See https://babeljs.io/docs/en/options#filename for more information.
    at new ConfigError (/home/projects/ladle-o7lxfz/node_modules/.pnpm/@babel+core@7.24.6/node_modules/@babel/core/lib/errors/config-error.js:10:5)
    at validateIfOptionNeedsFilename (/home/projects/ladle-o7lxfz/node_modules/.pnpm/@babel+core@7.24.6/node_modules/@babel/core/lib/config/full.js:265:11)
    at eval (/home/projects/ladle-o7lxfz/node_modules/.pnpm/@babel+core@7.24.6/node_modules/@babel/core/lib/config/full.js:275:103)
    at validatePreset (/home/projects/ladle-o7lxfz/node_modules/.pnpm/@babel+core@7.24.6/node_modules/@babel/core/lib/config/full.js:275:76)
    at loadPresetDescriptor (/home/projects/ladle-o7lxfz/node_modules/.pnpm/@babel+core@7.24.6/node_modules/@babel/core/lib/config/full.js:293:3)
    at recursePresetDescriptors (/home/projects/ladle-o7lxfz/node_modules/.pnpm/@babel+core@7.24.6/node_modules/@babel/core/lib/config/full.js:77:31)
    at eval (/home/projects/ladle-o7lxfz/node_modules/.pnpm/@babel+core@7.24.6/node_modules/@babel/core/lib/config/full.js:156:21)

More info: https://ladle.dev/docs/stories#limitations

Reproduction

Create a new Stackblitz
Add babel.config.json in the root with contents:

{
  "presets": [
    "@babel/preset-env",
    "@babel/preset-react",
    "@babel/preset-typescript"
  ]
}

Add/install aforementioned deps

pnpm add @babel/preset-env @babel/preset-react @babel/preset-typescript

Add a src/whatever.stories.mdx file, contents doesn't matter
Restart dev server pnpm install && pnpm run dev

Environment

OS: Mac OS Sonoma 14.6.1 (23G93)
Browser: Brave Version 1.70.126 Chromium: 129.0.6668.100 (Official Build) (arm64)
Version: Ladle latest stable, 4.1.2 at time of writing

fyi: by default, Ladle doesn't use babel anymore (we use swc plugin instead)

authors: tajo viddo

repo: tajo/ladle


text:
✘ [DeepSeek] Request failed with status code 400

Bug description
I have been using the DeepSeek API, and it works fine most of the time. However, when I attempt to modify a large number of files at once, sometimes I encounter an error message:
✘ [DeepSeek] Request failed with status code 400. According to the documentation error code: https://platform.deepseek.com/api-docs/zh-cn/quick_start/error_codes
This error is due to a format error in the request body. The logging=true configuration has been enabled, but no logs have been generated, and it is unclear what exactly is wrong with the request format.
aicommit2 config get DEEPSEEK：
DEEPSEEK {
  key: 'sk-***',
  model: 'deepseek-coder',
  topP: 0.9,
  systemPrompt: '',
  systemPromptPath: 'C:\\Users\\myname\\.aicommit2.conf\\prompt.txt',
  codeReviewPromptPath: '',
  timeout: 10000,
  temperature: 1,
  maxTokens: 10000,
  logging: true,
  locale: 'zh',
  generate: 1,
  type: 'conventional',
  maxLength: 50,
  includeBody: true,
  codeReview: false
}

aicommit2 version
2.1.2
Environment
System:
    OS: Windows 11 10.0.22631
    CPU: (12) x64 11th Gen Intel(R) Core(TM) i5-11400 @ 2.60GHz
    Memory: 1.54 GB / 15.73 GB
Binaries:
    Node: 20.10.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.2.3 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.9.0 - C:\Program Files\nodejs\pnpm.CMD

Can you contribute a fix?

[ ] I’m interested in opening a pull request for this issue.

When the API response doesn't come through properly, no log is generated. I'll look into the issue you raised.

When the API response doesn't come through properly, no log is generated. I'll look into the issue you raised.

Thank you for your response. The latest situation is that even if I only modify one line of code and directly use the aicommit2 command, I will encounter the error message ✘ [DeepSeek] Request failed with status code 400. To better troubleshoot the issue, is there anything I can do? For example, can I manually modify some code to get the request body content of the API request?

@hsu1943 I've changed the method for requesting the Deepseek API. Could you try it out? Please use version 2.1.5.


text:
Generate Comparison Images with RoborazziRule Even When Verification Fails

Overview
This PR specifically changes the behavior of the verification task when using RoborazziRule. Previously, if the verification task failed while using RoborazziRule, the process would halt, and no further comparison images would be generated. With this change, comparison images will continue to be generated even when the initial verification fails.

copilot:all

So I've realized that when I was asking about this I was thinking narrowly about my current and basic use case where I am only capturing one image per test function.
So three scenarios. I've asked about a subset of these, but I want to ask about all of them at once, just to be clear.
1: I have three captureRoboImage() calls within a test function and the first call fails image validation.
2: I have three test functions inside a test class and the first function fails image validation
3: I have three test classes and the first one fails image validation
In each scenario, with the current behavior, will I:
A: Get validation results for the later tests/calls?
B: Get image comparisons for the later test/calls?

Thanks for bringing this up. We might need to consider these specific test scenarios. Below is a summary of the current behavior:

Scenario
Verification Behavior (verifyRoborazziDebug)
Comparison Behavior (compareRoborazziDebug)

Multiple captureRoboImage() calls within a test function
If the first captureRoboImage() call throws an exception, subsequent calls won't be executed. However, you will still receive validation results and images from that initial call.
captureRoboImage() calls are expected to execute without issues, and you'll receive complete validation results and images, including those from the first call.

Multiple test functions within a test class
Even if the first test function throws an exception, the remaining functions will still be executed. You'll get validation results and images from all functions.
You'll have access to validation results and images from all functions.

As for this PR, the behavior will be as follows:

Scenario
Verification Behavior (verifyRoborazziDebug)
Comparison Behavior (compareRoborazziDebug)

Multiple captureRoboImage() calls within a test function
The first captureRoboImage() call doesn't throw an exception, and the test function itself later throws an exception. You will receive all images. However, due to throwing the first VerificationError at the end of the test, you won't have access to additional validation results or stack traces from subsequent calls.
captureRoboImage() calls are expected to proceed as usual, and you'll receive complete validation results and images, including those from the first call.

@timothyfroehlich
Thanks for bringing this up. We might need to consider these specific test scenarios. Below is a summary of the current behavior:

Scenario
Verification Behavior (verifyRoborazziDebug)
Comparison Behavior (compareRoborazziDebug)

Multiple captureRoboImage() calls within a test function
If the first captureRoboImage() call throws an exception, subsequent calls won't be executed. However, you will still receive validation results and images from that initial call.
captureRoboImage() calls are expected to execute without issues, and you'll receive complete validation results and images, including those from the first call.

Multiple test functions within a test class
Even if the first test function throws an exception, the remaining functions will still be executed. You'll get validation results and images from all functions.
You'll have access to validation results and images from all functions.

As for this PR, the behavior will be as follows:

Scenario
Verification Behavior (verifyRoborazziDebug)
Comparison Behavior (compareRoborazziDebug)

Multiple captureRoboImage() calls within a test function
The first captureRoboImage() call doesn't throw an exception, and the test function itself later throws an exception. You will receive all images. However, due to throwing the first VerificationError at the end of the test, you won't have access to additional validation results or stack traces from subsequent calls.
captureRoboImage() calls are expected to proceed as usual, and you'll receive complete validation results and images, including those from the first call.

Incorporating this PR would bring some convenience, but it also presents a trade-off. Specifically, there is an existing best practice that suggests having one 'verify' operation per test. Adding this new functionality could complicate the structure of the test reports. Therefore, I'm unsure whether implementing this change is the right move.

Thank you. I won't be implementing these behavior changes, but I believe some refactoring can be done in this PR. Therefore, I'll modify this PR to focus solely on refactoring.

authors: takahirom timothyfroehlich

repo: takahirom/roborazzi


text:
FEATURE: Disable Boundary Checking

On every render, log messages showing up from number-precision for every aspect-ratio.
This fix deactivates the BoundaryChecking on number-precision.
Example:
[1] 968619246861924900 is beyond boundary when transfer to integer, the results may not be accurate
[1] 11517412935323384 is beyond boundary when transfer to integer, the results may not be accurate
[1] 11517412935323384 is beyond boundary when transfer to integer, the results may not be accurate
[1] 1151741293532338400 is beyond boundary when transfer to integer, the results may not be accurate

@takamoso any updates?

authors: freesh negezor

repo: takamoso/postcss-aspect-ratio-polyfill


text:
"python main.py --dataset spade_celebA --segmap_ch 3 --phase" random saved image is dark

I run python main.py --dataset spade_celebA --segmap_ch 3 --phase, but the sved image is dark. something is wrong.

I changed related codes as following:from PIL import Image
def inverse_transform(images):
var = (images+1.) / 2
var[var < 0] = 0
var[var > 1] = 1
var = var * 255
return var
def imsave(images, size, path):
img = merge(images, size)
return img.save(path)
def merge(images, size):
h, w = images.shape[1], images.shape[2]
c = images.shape[3]
img = np.zeros((h * size[0], w * size[1], c))
for idx, image in enumerate(images):
i = idx % size[1]
j = idx // size[1]
img[hj:h(j+1), wi:w(i+1), :] = image
return Image.fromarray(img.astype('uint8'))

generated images are as following:

the result is not very good. is this the best SPADE can achieve on human face?


text:
Bug: Unions broken in python 3.10 on dataclass_utils.into

Hello, I ran into a bug similar to https://github.com/tamuhey/dataclass_utils/issues/8
If i try using the python 3.10 union syntax sugar on dataclass type hints then try to call dataclass_utils.into on them, it breaks, but doing so with a normal typing union doesn't even though they should be equivalent
import dataclasses
import dataclass_utils
import typing

print(int | str)
print(typing.Union[int, str])

@dataclasses.dataclass
class FooUnion:
    foo: typing.Union[str, int] = "foo"

@dataclasses.dataclass
class FooSugar:
    foo: str | int = "foo"

f_union = FooUnion()
f_dict = dataclasses.asdict(f_union)
f_union_from_dict = dataclass_utils.into(f_dict, FooUnion)
print(f"Pass! {f_union_from_dict=}")

f_sugar = FooSugar()
f_dict = dataclasses.asdict(f_sugar)
f_sugar_from_dict = dataclass_utils.into(f_dict, FooSugar)
print(f"Pass! {f_sugar_from_dict=}")

Traceback (most recent call last):
File "[...]\dataclass_utils_bug.py", line 23, in
f_sugar_from_dict = dataclass_utils.into(f_dict, FooSugar)
File "[...]\lib\site-packages\dataclass_utils\into_dataclass.py", line 24, in into_root
raise ret
dataclass_utils.error.Error0: Error in field 'foo'. Expected type str | int, got <class 'str'> (value: foo)
int | str
typing.Union[int, str]
Pass! f_union_from_dict=FooUnion(foo='foo')
Process finished with exit code 1

Thanks for reporting the bug! I'll investigate it.

Just released version 0.7.23, which should fix this issue.


text:
Stop engine command GPS103 doesn't work

Anton,
I've been testing some GPS103 devices in http://dev.traccar.org and the stop/resume engine doesn't work. I have the manufacturer app installed in my computer and I sniffed the commands it sends. When I send STOP command, it sends in HEX:
2a:2a:2c:69:6d:65:69:3a:33:35:39:37:31:30:30:34:38:37:33:30:33:33:38:2c:4a
And when I send RESUME command, it sends this:
2a:2a:2c:69:6d:65:69:3a:33:35:39:37:31:30:30:34:38:37:33:30:33:33:38:2c:4b
I see there is no semicolon at the end like in your code, maybe that's why it doesn't work.
Thanks.

Can you please provide network packets log (pcap?).

I have updated http://dev.traccar.org/. Please try now and see if it works.

Anton, I just tested sending commands some minutes ago. I guess now it works. Can you check your logs? The IMEI is 359710047648192.
I can send you the manufacturer app pcap file if you need it.
Thanks

Well, I have already checked that it sends commands without semi-colon, but does it work with a real device? Does device accept the command this way?
As for pcap, it would be great if you could provide the file. You can send to my email (address is in profile). Thanks.

Anton, I just tried sending commands in DEV Traccar but engineStop command doesn't work. However, resume command does work and Fix positions command works too. It is weird.

Now. I know. The ENGINE STOP COMMAND has a semicolon at the end while the others don't.
https://github.com/tananaev/traccar/blob/master/src/org/traccar/protocol/Gps103ProtocolEncoder.java
Check it out!

Fixed now.

Now, everything works as expected. Thanks Anton. Great work.

Thanks for feedback.

authors: Jeferex tananaev

repo: tananaev/traccar


text:
Wrapper problems

This is what I get using the last 32 bits stable release on a CentOS 64 bits environment:
[root@b196 traccar]# service traccar console
Running traccar...
wrapper  | --> Wrapper Started as Console
wrapper  | Java Service Wrapper Community Edition 32-bit 3.5.16
wrapper  |   Copyright (C) 1999-2012 Tanuki Software, Ltd. All Rights Reserved.
wrapper  |     http://wrapper.tanukisoftware.com
wrapper  |
wrapper  | Wrapper Process has not received any CPU time for 12 seconds.  Extending timeouts.
wrapper  | Launching a JVM...
jvm 1    | WrapperManager: Initializing...
wrapper  | Wrapper Process has not received any CPU time for 49 seconds.  Extending timeouts.
When I try to stop the program I get this status:
[root@b196 traccar]# service traccar status
traccar is running: PID:5824, Wrapper:STOPPING, Java:Unknown
[root@b196 traccar]#

hi i too facing same issue
INFO   | wrapper  | 2017/03/27 11:40:55 | Wrapper Process has not received any CPU time for 50 seconds.  Extending timeouts.
INFO   | wrapper  | 2017/03/27 11:41:34 | Wrapper Process has not received any CPU time for 39 seconds.  Extending timeouts.
INFO   | wrapper  | 2017/03/27 11:42:07 | Wrapper Process has not received any CPU time for 32 seconds.  Extending timeouts.
INFO   | wrapper  | 2017/03/27 11:43:02 | Wrapper Process has not received any CPU time for 54 seconds.  Extending timeouts.
INFO   | wrapper  | 2017/03/27 11:43:35 | Wrapper Process has not received any CPU time for 33 seconds.  Extending timeouts.
INFO   | wrapper  | 2017/03/27 11:44:35 | Wrapper Process has not received any CPU time for 60 seconds.  Extending timeouts.
INFO   | wrapper  | 2017/03/27 11:45:35 | Wrapper Process has not received any CPU time for 60 seconds.  Extending timeouts.
INFO   | wrapper  | 2017/03/27 11:46:35 | Wrapper Process has not received any CPU time for 60 seconds.  Extending timeouts.
INFO   | wrapper  | 2017/03/27 11:47:08 | Wrapper Process has not received any CPU time for 32 seconds.  Extending timeouts.
INFO   | jvm 1    | 2017/03/27 11:52:06 | 2017-03-27 11:52:06,550 WARN [0-BAM::

@manoj425, have you looked at the date on the thread? Your issue is definitely different. Please don't comment on old closed thread. If you have some problem or question, create a new issue.

authors: hackerunet manoj425 tananaev


text:
[NEW ICON] Leetcode

Skill Name
Leetcode
Why?
Leetcode is a DSA problem solving platform used by many developers. A icon to showcase that skill would be great
Reference Image

I created a new project since this project is no longer updating & the author left it, leetcode is available skills-icons
https://skills-icons.vercel.app/api/icons?i=leetcode

repo: tandpfun/skill-icons


text:
Deprecate setCameraType for dynamic scene update

Set camera type should be deprecated and scene update should be used instead (https://github.com/tangrams/tangram-es/issues/650)

MapController API
Tangram API

Closed by #679

EraserMap code will also have to make this change.
cc. @ecgreb @sarahlensing

authors: karimnaaji tallytalwar

repo: tangrams/tangram-es


text:
Could not listen on port 8000

mac os
python 2.7.11

昨晚刚刚安装了，写了两篇（感觉很棒），但今早一跑 simiki p就提示Could not listen on port 8000
①用lsof -i:8000检查了端口没有被占用
②在配置文件里配置了debug模式为true 但在preview这一步上除了以上的那条外没有更多的提示信息
本人Python小白一枚，查看源码只看懂了是捕捉到了OSError 或IOError @-@
望作者能给予帮助
谢谢

你好。
因为当前8000端口无法使用，所以才会报这个。
可以先确认下是否还有simiki的进程(ps aux | grep simiki)

你好刚刚我使用了那个指令查询和simiki相关的进程但显示只有 grep这个进程
username      944   0.0  0.0  2432792    576 s000  R+   11:09AM   0:00.00 grep simiki

并且我尝试用simiki p --port 8001更换监听端口，它也给了同样的**[ERROR]: Could not listen on port 8001**的提示,更换多个未占用port也是同样的结果😢

@toastsgithub
尝试SimpleHTTPServer:
python -m SimpleHTTPServer

以及(mac下)：
nc -l 8000

确认是否都能监听？

能的（吧？）
第一个指令的响应是：
Serving HTTP on 0.0.0.0 port 8000 ...

第二个指令没有任何提示

@toastsgithub 你可以按这个diff 63888fa80f74c09cefe670ff58df0be7a92b5340 本地改下源码 simiki/server.py ，输出一些详细信息并贴出来。之前我也没遇到过这种情况。
通过下面这条命令找到simiki源码目录：
python -c 'import simiki; print(simiki.__path__)'

输出信息如下

额，执行下：
 ping localhost  # 或者 host localhost

确认下localhost是否可以解析（正常情况是在/etc/hosts中定义）。感觉像是localhost无法解析造成，因为我这边默认是bind到localhost。如果是这个问题，那我得考虑改为'127.0.0.1'了。

①localhost 是ping不通的但是这个问题是一直存在，至少在使用simiki之前也是ping不通的，这点可以确认，奇怪的是在这样的情况下（昨天一整晚）还是能成功运行simiki。
②用host localhost 有以下输出
localhost has address 127.0.0.1
localhost has IPv6 address ::1

有解析，但是ping不通。你执行ifconfig -a 或者 ip a 截图我看下。我感觉你的 loopback(lo) 口宕了。

回到宿舍无意发现localhost能ping通，接着simiki也能正常运行，接着我重新做了几个测试
①在宿舍使用自己的路由器无线接入，能ping通，能preview

②关闭网络，不能ping通，不能preview

③在公共环境下，通过无线路由器（由网络中心配置）接入无线网，不能Ping通，不能review

大致来说  ：就是ping不通的时候就运行不了了，具体是什么样的配置导致我在某些环境下能ping通有的又不能，还没搞清楚，不过如果没有别的方面的考虑，您还是可以考虑下默认用127.0.0.1代替localhost

@toastsgithub 断开网络的情况下，是不会影响loopback口的。而且我看你的三个截图，lo0都是UP且RUNNING的
你可以贴下你的/etc/hosts配置吗（主要是localhost对应的ip）？我感觉你本地是不是用了一些hosts工具，改了/etc/hosts文件。
另外，localhost这个我确实需要改下，直接写为127.0.0.1

恩 hosts中所有关于localhost的配置如下

ping 127.0.0.1在上述三种情况下都是通的

@toastsgithub 比较奇怪了，想不到哪个地方可以在网络断掉的时候，修改localhost的记录并影响到解析。
目前使用的话，你可以先将源码下simiki/cli.py的第30行，Bind host to preview [default: localhost] 改为Bind host to preview [default: 127.0.0.1]，以解决你目前的问题。过些天我会发布一个版本，顺便处理这个。
另外，这个问题的表象已经解决了，深层次的问题没法实际去排查，所以就先关闭这个Issue了，感谢你的支持，后续还有问题，欢迎随时提出来 👍

好的 也感谢你的耐心解答，很棒的东西，很喜欢 ， 会持续关注的

@toastsgithub Sorry，上面说错了，没必要去改代码了，preview时直接加上--host 127.0.0.1就可以了：
simiki p --host 127.0.0.1

恩 手动测试了都可以运行的  因为写了些脚本运行simiki 就直接改source不一一修改脚本了

authors: tankywoo toastsgithub

repo: tankywoo/simiki


text:
World Time app

I want to add my Worldtime app to your repo under hacktoberfest 2023.

@kaushal1717 here you go


text:
Streaming table HOC.

This functionality enables react table to continuously streaming data from the server. Here is the sample screenshot

Please ingest changes from master and resolve conflicts, then reopen. Thanks!

Hi, it's unfortunate that this was abandoned. I think it's a crucial feature for any table component.

authors: hasufell sivagollapalli tannerlinsley

repo: tannerlinsley/react-table


text:
negative timings on a served index being built

Describe the bug
While trying out tantivy using the CLI crate, I wanted to search for documents while the wikipedia articles were being indexed. I got a response where timings reported negative times.
Probably I shouldn't get negative values there.
http localhost:3000/api q==barack+obama nhits==20
HTTP/1.1 200 OK
Content-Length: 279
Content-Type: application/json
Date: Sat, 10 Oct 2020 23:11:15 GMT

{
    "hits": [],
    "num_hits": 0,
    "q": "barack+obama",
    "timings": {
        "timings": [
            {
                "depth": 0,
                "duration": -194,
                "name": "search"
            },
            {
                "depth": 0,
                "duration": -4,
                "name": "fetching docs"
            }
        ]
    }
}

Which version of tantivy are you using?
tantivy-cli: https://github.com/tantivy-search/tantivy/commit/d63cae71b19b99fb9c7dbca49daf88339fae6e7a
To Reproduce
Serve index as it is being indexed and search it.

This is bug... but please report it in the tantivy-cli repository in the future. Anywya it is fixed now.

authors: fulmicoton scampi

repo: tantivy-search/tantivy


text:
WIP: compiling to wasm

I started an experiment to compile tantivy to wasm. These are some of the features I had to adjust to get it to compile.
The index writing doesn't work because it seems to be using std lib features that aren't supported by wasm target yet, such as std::threads. I can see from https://github.com/fulmicoton/tantivy-wasm that tantivy seems to have worked with wasm at some point with StaticDirectory which confirms that at least the index writing never worked in wasm.
Although there is no StaticDirectory in the current master, I don't see the Directory trait having changed since when it existed, so I could add it back. But I am a little stumped at how the DATA: &'static [u8] was generated. Would appreciate any pointers

The index writing doesn't work because it seems to be using std lib features that aren't supported by wasm target yet, such as std::threads. I can see from https://github.com/fulmicoton/tantivy-wasm that tantivy seems to have worked with wasm at some point with StaticDirectory which confirms that at least the index writing never worked in wasm.

Yes this is correct.
So for my small experiment, I just:

indexed things using a non-wasm program
merged all of the segments together.
wrote a small program to put the resulting segment in the static directory format.
included the resulting index file in the WASM program using include_bytes

(Of course this is not a good solution )

Hey @jonfk - thanks for the PR.
I have been hacking away on a WIP branch in my own fork. I followed Paul's earlier work on it, but haven't tracked upstream for a while. Have a look and let me know, if any of it is useful.
https://github.com/petr-tik/tantivy/commits/compiling_for_wasm

Thanks @jonk, I made some change your PR and merged it.

Thanks @fulmicoton for the quick work.
@petr-tik I will take a look at your branch. It seems like you are using a similar method to what @fulmicoton was using to generate the data to be served to the wasm. If we could add a serialization and deserialization scheme for the index so that we could have a better way to serve the index to the wasm.

If we could add a serialization and deserialization scheme for the index so that we could have a better way to serve the index to the wasm.

Can you be as explicit as possible about what you mean by serialization and deserialization scheme for the index?
Also do you need to index in web assembly or are you trying to serve a static index?

@fulmicoton Sorry for being vague about a serialization/deserialization scheme, it's just because I am not very knowledgeable about the inner workings of tantivy.
What I meant is some kind of defined format to transport the index. It could be json, protobuf, etc... which would allow some kind of client (here wasm) that could serve as the read only querying side of the index.
I don't know if that would be possible without breaking changes over time, which would really be a disadvantage of defining such a format.
My idea would be to implement a read-only Directory for wasm that would use indexeddb as the backing store to serve search queries.

authors: fulmicoton jonfk petr-tik


text:
v0.4.1 react-web init error

$ react-web init RN4Web
This will walk you through creating a new React Web project in /Users/tyrealgray/RN4Web
Installing react-web package from npm...
Setting up new React Web app in /Users/tyrealgray/RN4Web
npm ERR! Darwin 15.6.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "" "--save-dev" "webpack@1.13.2" "webpack-dev-server@1.16.1" "babel-loader@6.2.5" "json-loader@0.5.4" "react-hot-loader@1.3.0" "haste-resolver-webpack-plugin@0.2.1" "webpack-html-plugin@0.1.1" "babel-preset-es2015@undefined" "babel-preset-react@undefined" "babel-preset-stage-1@6.16.0"
npm ERR! node v4.4.4
npm ERR! npm  v2.15.1
npm ERR! code ETARGET
npm ERR! notarget No compatible version found: babel-preset-es2015@'undefined'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["6.0.2","6.0.8","6.0.11","6.0.12","6.0.14","6.0.15","6.1.2","6.1.4","6.1.17","6.1.18","6.2.4","6.3.13","6.5.0","6.5.0-1","6.6.0","6.9.0","6.13.0","6.13.1","6.13.2","6.14.0","6.16.0"]
npm ERR! notarget
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'RN4Web'
npm ERR! notarget
npm ERR! Please include the following file with any support request:
npm ERR!     /Users/tyrealgray/RN4Web/npm-debug.log
npm install failed
$ react-web -v
react-web-cli: 0.0.3

the same to me

It was fine at version 0.3.2, but something goes wrong when they update and didn't test the cmd line.
If I edit devDependencies in package.json by myself and install, it still could work.

Fixed in react-web@0.4.2 @TyrealGray @ezioruan

authors: TyrealGray ezioruan yuanyan

repo: taobaofed/react-web


text:
Why does TRANCOS dataset needs to be preprocessed?

Dear author @taohan10200,
I downloaded TRANCOS, SHHA, SHHB, and URBAN_TREE,
but it seems that only TRANCOS is preprocessed (cutting the edges off, etc.), is there a particular reason for that?
Thanks in advance!!

Hi, @sullivantee
TRANCOS is not fully annotated, which was only annotated in some interested regions.  So we cut the edges with the methods proposed in the original paper. The pre-processing guaranteed all cars having labels.


text:
Systems:  Tenant admin can create systems owned by any arbitrary string

A tenant admin can create a system that has an owner with any string - for example "bogusUser".  There is no validation that it is a real user.  Child systems suffer from the same problem.

Check with developers of authenticator service to see if it is possible to validate a username.

repo: tapis-project/tapis-systems


text:
Fixed DbSet property naming

close #70
sometimes the DbSet name is the same as the property name, which ends up altering the DbSet name by adding the suffix HIDDEN
public virtual DbSet<Employee> Employees_HIDDEN { get; set; } = null!;
public virtual DbSet<EmployeeDevice> EmployeeDevices_HIDDEN { get; set; } = null!;
 public virtual DbSet<Equipment_HIDDEN> Equipment_HIDDEN { get; set; } = null!;

Good catch. Will review, thank you for contributing!

Thanks @jwallet, sorry was out of town for a few days. PR looks good.

authors: jwallet tareqimbasher

repo: tareqimbasher/NetPad


text:
feat: add epoch events

Description
Add epoch events

End this is added at the last base layer block that is still in the epoch. We have to bury the block to be locked, after that we officially end the epoch
Start this will be in the first block when the epoch switch, its parent will have End or it will be genesis block.

Motivation and Context
How Has This Been Tested?
I've tested multiple committees and I switched epoch many times. I've checked the blocks and the commands in them to confirm the epoch end/start.
There is also a cucumber test. That checks if the epoch ended with a EpochEnd command and new one started with EpochStart command.
What process can a PR reviewer use to test or verify this change?
Do as above, or go a step further and try to make a transaction during epoch switching when you also add a VNs that changes space division.
Breaking Changes

[ ] None
[ ] Requires data directory to be deleted
[x] Other - The 2nd layer should be restarted, otherwise the blocks validation will fail.

Further testing revealed a unique constraint issue when validator nodes re-register. Investigating.

authors: Cifko sdbondi

repo: tari-project/tari-dan


text:
Web player websocket port and handshake issues

The web player keeps defaulting back to port :9000 when accessed directly from its URL (or the page is reloaded):

Enable web player and set HTTP and websocket ports to different values
Open web player (I am using a domain name in my case, tunneling my computer with ssh -R to a Raspberry Pi server connected to a DNS entry).
Visit the web interface
Click the Player tab, then this works the first time (the dev tools Network tab shows the websocket connection is the newly chosen one)
Reload the player page, now the websocket connection is back to :9000 and fails.
It appears every time /player is loaded directly, it requests :9000 while every time it is accessed by clicking the Player tab, the port is correct.

The web player fails to establish a websocket connection when visiting the Player link a second time:

Visit the web interface home page and hard refresh (Ctrl Shift R)
Click the Player tab, the connection should be working and videos play
Hit the back button in the browser
The console shows this error and eventually the music for the currently queued karaoke video plays despite not even being on the player:

Uncaught TypeError: Cannot read property 'callback' of undefined
    at r (1.karaoke-rs.js:1)
    at Module.Ve (1.karaoke-rs.js:1)
    at __wbg_cargowebsnippetf5302c0143e9bd10d39262404fc2b4c9660c7f9d_645c5ca38dda53ac (karaoke-rs.js:1)
    at <yew::services::resize::ResizeTask as core::ops::drop::Drop>::drop::hf45e7f94856691f9 (:my-http-port/wasm-function[768]:0xbbe35)
    at core::ptr::real_drop_in_place::h76a109ebe0812206 (:my-http-port/wasm-function[673]:0xb2ce2)
    at <yew::html::scope::DestroyComponent<COMP> as yew::scheduler::Runnable>::run::h82153cfbd3015bc8 (:my-http-port/wasm-function[358]:0x823cd)
    at yew::scheduler::Scheduler::put_and_try_run::h654711681d8a2ef3 (:my-http-port/wasm-function[576]:0xa7e23)
    at yew::agent::AgentLink<AGN>::callback::{{closure}}::h164a1611c4638d27 (:my-http-port/wasm-function[860]:0xc32ba)
    at <stdweb::webcore::newtype::Newtype<(stdweb::webcore::serialization::FunctionTag, (A12,)),stdweb::webcore::mutfn::Mut<F>> as stdweb::webcore::serialization::FuncallAdapter<F>>::funcall_adapter::h3f17d9ef7d5dc8f9 (:my-http-port/wasm-function[243]:0x5aa58)
    at Object.n.STDWEB_PRIVATE.dyncall (1.karaoke-rs.js:1)

If you fool around with it enough, like remove the /player from the URL and hit enter, or reload the page on the home page, sometimes (often more consistently than other times) this error appears instead of the currently-queued video:

karaoke-rs.js:1 WebSocket connection to 'ws://my-domain:my-websocket-port/' failed: Connection closed before receiving a handshake response

Good news, after I merge https://github.com/tarkah/karaoke-rs/pull/19, this should fully fix all issues related to navigating away from the player page. If you click back, the audio will end properly and the page you were previously on will render properly.
No idea if any of this will fix the issue around the below error, but if not, it should be the ONLY error left related to this issue
Uncaught (in promise) DOMException: Failed to set the 'buffer' property on 'AudioBufferSourceNode': Cannot set buffer to non-null after it has been already been set to a non-null buffer

@Keavon please try the newest release, 0.9.1 and see if any of these issues still exist. Thanks!

@tarkah I downloaded 0.9.1 and I am getting this error when I open the Player page. I also see [2020-02-07T08:52:26Z INFO  karaoke_rs::websocket] Connection from 127.0.0.1:63241 show up in the karaoke-rs console and [2020-02-07T08:52:26Z INFO  karaoke_rs::websocket] Connection from 127.0.0.1:63241 when closing the browser page. The web player is entirely nonfunctional because of this error.

Huh, does it do this for all your songs, or just a specific song? I'll try to fix it so the program doesn't panic and the web page is still usable. If it can't decode your mp3 file, I'm not sure why that'd be.
Sorry for all these errors, I'm not experiencing any of them. Appreciate you uncovering them all!

@Keavon #20 should do the trick. The player will no longer panic, however it will obviously not play the song because it can't decode that audio file. A WARN will be logged to console notifying the user to remove that song from the queue. Since no panic occurs, you can easily backspace -> Queue page, hit next song, then go back to player (or have queue open on another tab / device)

authors: Keavon tarkah

repo: tarkah/karaoke-rs


text:
this.state cannot be parsed

In the issue #76 , the way suggested is not working, please help
this.state.search cannot be parsed, please help. Thanks
<ParsedText
style={styles.text}
parse={
[
{pattern: /{this.state.search}/,style: styles.found},
]
}
childrenProps={{allowFontScaling: false}}
pattern : RegExp(/{this.state.search}/) is not working also.

it is solved. Thanks. please close this issue.

repo: taskrabbit/react-native-parsed-text


text:
How create the symbol to get candles of certain periods

I can't wrap my head around how to get candles for certain periods.
Is it added to the symbol in the symbol list?
I've tried:
subs_list = ['BTCUSD&period=10m']
# this function fetches quotes once, then closes the subscription
await streamer.subscribe(EventType.CANDLE, subs_list)

Also had some other permutations without '&' and '=' etc, but just can't get it to work. Also the DXfeed docs don't make me any smarter.

Hey! If you look at the SDK docs (it could probably be a bit clearer, sorry about that...), you actually need to use a separate subscription function for candles:
from tastytrade.instruments import Cryptocurrency
from datetime import datetime, timedelta

btc = Cryptocurrency.get_cryptocurrency(session, "BTC/USD")
await streamer.subscribe_candle(btc.streamer_symbol, start_time=datetime.now() - timedelta(minutes=30), interval='5m')
n = 0
async for data in streamer.listen_candle():
    n += 1
    print(data)
    if n > 5:
        break

I got this output:
Candle(eventSymbol='BTC/USD:CXTALP{=5m}', eventTime=0, eventFlags=4, index=7252381703287603200, time=1688576700000, sequence=0, count=41, open=30470.4291875, high=30481.4343737, low=30464.4982534, close=30481.4343737, volume='NaN', vwap='NaN', bidVolume='NaN', askVolume='NaN', impVolatility='NaN', openInterest=0.0)
Candle(eventSymbol='BTC/USD:CXTALP{=5m}', eventTime=0, eventFlags=0, index=7252380414797414400, time=1688576400000, sequence=0, count=243, open=30463.1579548, high=30479.4223798, low=30448.2561021, close=30470.5827183, volume='NaN', vwap='NaN', bidVolume='NaN', askVolume='NaN', impVolatility='NaN', openInterest=0.0)
Candle(eventSymbol='BTC/USD:CXTALP{=5m}', eventTime=0, eventFlags=0, index=7252379126307225600, time=1688576100000, sequence=0, count=230, open=30450.3426869, high=30491.3908612, low=30450.3426869, close=30463.1566781, volume='NaN', vwap='NaN', bidVolume='NaN', askVolume='NaN', impVolatility='NaN', openInterest=0.0)
Candle(eventSymbol='BTC/USD:CXTALP{=5m}', eventTime=0, eventFlags=0, index=7252377837817036800, time=1688575800000, sequence=0, count=218, open=30436.0089948, high=30450.7425733, low=30425.7046032, close=30449.6946234, volume='NaN', vwap='NaN', bidVolume='NaN', askVolume='NaN', impVolatility='NaN', openInterest=0.0)
Candle(eventSymbol='BTC/USD:CXTALP{=5m}', eventTime=0, eventFlags=0, index=7252376549326848000, time=1688575500000, sequence=0, count=241, open=30445.2262747, high=30446.7292009, low=30426.3221241, close=30436.5038203, volume='NaN', vwap='NaN', bidVolume='NaN', askVolume='NaN', impVolatility='NaN', openInterest=0.0)
Candle(eventSymbol='BTC/USD:CXTALP{=5m}', eventTime=0, eventFlags=0, index=7252375260836659200, time=1688575200000, sequence=0, count=221, open=30448.7940944, high=30448.7940944, low=30432.2586602, close=30445.22495, volume='NaN', vwap='NaN', bidVolume='NaN', askVolume='NaN', impVolatility='NaN', openInterest=0.0)

Totally overlooked it in the SDK. Probably because I was not looking for a separate method :(
But it works.
Thanks a bundle.

repo: tastyware/tastytrade


text:
Build failing (possibly, incompatibility with beam-core)

Hi, I'm getting the following build errors (stack, lts-14.4):
    /Users/alexandergranin/workspace/juspay/euler-hs/.stack-work/downloaded/rmpqrO0jDOOa/Database/Beam/MySQL/Connection.hs:138:23: error:
        Not in scope: data constructor ‘PeekField’
        Perhaps you meant variable ‘peekField’ (imported from Database.Beam.Backend)
        |
    138 |                 step (PeekField next) curCol fields@((desc, field):_) =
        |                       ^^^^^^^^^

    /Users/alexandergranin/workspace/juspay/euler-hs/.stack-work/downloaded/rmpqrO0jDOOa/Database/Beam/MySQL/Connection.hs:143:23: error:
        Not in scope: data constructor ‘PeekField’
        Perhaps you meant variable ‘peekField’ (imported from Database.Beam.Backend)
        |
    143 |                 step (PeekField next) curCol [] =
        |                       ^^^^^^^^^

    /Users/alexandergranin/workspace/juspay/euler-hs/.stack-work/downloaded/rmpqrO0jDOOa/Database/Beam/MySQL/Connection.hs:145:23: error:
        Not in scope: data constructor ‘CheckNextNNull’
        |
    145 |                 step (CheckNextNNull n next) curCol fields

Is there any solution to this?

Seems duplication of https://github.com/tathougies/beam-mysql/issues/11.

It seems these options have been made conditionally compillable in the mysql library:
#if !defined(MARIADB_BASE_VERSION) && MYSQL_VERSION_ID >= 80000
#else
      UseRemoteConnection ->
        go (#const MYSQL_OPT_USE_REMOTE_CONNECTION) nullPtr
      UseEmbeddedConnection ->
        go (#const MYSQL_OPT_USE_EMBEDDED_CONNECTION) nullPtr
      GuessConnection ->
        go (#const MYSQL_OPT_GUESS_CONNECTION) nullPtr
      ClientIP ip ->
        useAsCString ip $ go (#const MYSQL_SET_CLIENT_IP)
      SecureAuth b ->
        withBool b $ go (#const MYSQL_SECURE_AUTH)
#endif

I've commented them out in the beam-mysql, and also I've merged the travis/better-parsing branch into master in my fork:
https://github.com/graninas/beam-mysql
Not sure if it works though, and what features are now broken. Hopefully we'll not be needing in them.

repo: tathougies/beam-mysql


text:
Does not detect connected device and tries to launch Android Studio which is not installed

I have connected my device and can see with adb devices -l :
List of devices attached
WCB665T87LAA7L6L       device usb:2-2 product:RMX3392 model:RMX3392 device:RE879EL1 transport_id:3

But on running pnpm tauri android dev :

> tauri@0.0.0 tauri /home/john/Desktop/tauri
> tauri "android" "dev"

✔ What external IP should we use for your development server? · 192.168.1.13
Running BeforeDevCommand (`PUBLIC_TAURI_DEV=true pnpm run dev`)

> tauri@0.0.0 dev /home/john/Desktop/tauri
> vite dev

Warn Waiting for your frontend dev server to start on http://192.168.1.13:5173/...

VITE v4.0.4  ready in 1677 ms

➜  Local:   http://localhost:5173/
➜  Network: http://192.168.1.13:5173/
Info detected host target triple "x86_64-unknown-linux-gnu"
Error No available Android Emulator detected
Info Opening Android Studio
Error Launch failed: Failed to wait for child process for command "Android Studio" to exit: No such file or directory (os error 2)
^C ELIFECYCLE  Command failed.
ELIFECYCLE  Command failed with exit code 130.

I use Arch linux with pnpm as package manager. I updated the tauri cli and api packages to the `next` version using pnpm.

I have the same problem. Did you find any solution?
tried to install android studio in multiple places changing the JAVA_HOME env variable but still not recognized.
Also tried the standallone installation but its the same... It still asks for android studio. Its driving me insane D:

I used the rust version of cli in every project now.

Ok... seems the npm or node wrapper for this is not quite ready yet. Alpha...still on the early phase right :)). Try use cargo to launch the app. It should launch on your usb connected device. cargo tauri android dev or cargo tauri ios dev

Could you guys give it another try and see if the issue is fixed?

@amrbashir no, it's not fixed in 2.0.0.alpha.20

For those that still have this issue, it was fixed with tauri cli alpha 21

repo: tauri-apps/tauri


text:
[feat] On Windows, allow to customize the name of window class used v1.x

Describe the problem
Currently, on Windows, all app windows created by tauri have the same class named "Window Class", it would be neet to allow for customization of the Windows' window class name.
One use case: some windows custom hotkey managers leverage window class names to select windows...
Describe the solution you'd like
I would like to add a WindowConfig option called window_classname. Default should still be "Window Class" : it would be a non-breaking change :)
Alternatives considered
No alternative, unless simply dumping those tools and find one using other characteristics of windows...
Additional context
I have patched it on my side and want to contribute it to the upstream project.
It does depend on a new feature on Tao / winit side. Here are the correponding PRs:

winit : https://github.com/rust-windowing/winit/pull/2978
Status : All 55 checks passed, waiting for merge
tao : https://github.com/tauri-apps/tao/pull/770
Status : waiting for merge

This issue is a mirror of #7498 but dedicate to the version 1 of Tauri.

No need to open multiple issues, if the feature lands in 1.x, it will be merged to 2.0 as well

authors: amrbashir geraudloup


text:
[bug]  2.0.0-alpha.4 error Error tauri.conf.json error on tauri: Additional properties are not allowed ('allowlist', 'updater' were unexpected)

Describe the bug
The version I am using is 2.0.0-alpha.4. When I created mobile applications for android and ios【 yarn tauri android init
yarn tauri ios init】I got an error.
tauri android init
Error tauri.conf.json error on tauri: Additional properties are not allowed ('allowlist', 'updater' were unexpected)
tauri ios init
Error tauri.conf.json error on tauri: Additional properties are not allowed ('allowlist', 'updater' were unexpected)
Reproduction
No response
Expected behavior
No response
Platform and versions
pm run tauri info

> mm@0.0.0 tauri
> tauri info

       Error `tauri.conf.json` error on `tauri`: Additional properties are not allowed ('allowlist', 'updater' were unexpected)

Stack trace
No response
Additional context
No response

Hi, we have a wip migrate guide here: https://beta.tauri.app/guides/upgrade-migrate/from-tauri-1/#tauri-configuration - also alpha.4 isn't really supported anymore so i'd suggest to upgrade all packages to their latest version.
Furthermore, if your app is still pretty new, i'd suggest to re-run yarn create tauri app --alpha to have a ready to use project.

authors: FabianLars aibihub


text:
Error [tauri_cli] command ["xcodebuild"] exited with code 70[bug]

Describe the bug
cannot run cargo tauri ios dev, the output: xcodebuild: error: Found no destinations for the scheme 'tauri-mobile_iOS' and action build.
All as follow:
% cargo tauri ios dev
Detected connected device: iPhoneXSMax (iPhone11,6) with target "aarch64-apple-ios"
        Info Using 10.254.75.208 to access the development server.
        Info detected host target triple "aarch64-apple-darwin"
Building app...
Command line invocation:
    /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -scheme tauri-mobile_iOS -workspace /Users/sope/workspaces/rust/tauri/tauri-mobile/src-tauri/gen/apple/tauri-mobile.xcodeproj/project.xcworkspace/ -sdk iphoneos -configuration debug -arch arm64 -allowProvisioningUpdates build

User defaults from command line:
    IDEPackageSupportUseBuiltinSCM = YES

Build settings from command line:
    ARCHS = arm64
    SDKROOT = iphoneos17.2

2024-01-05 18:23:37.604 xcodebuild[73289:7197573] Writing error result bundle to /var/folders/j4/lf3vdk9n1fz_cf5ymm0pw4sh0000gn/T/ResultBundle_2024-05-01_18-23-0037.xcresult
xcodebuild: error: Found no destinations for the scheme 'tauri-mobile_iOS' and action build.
       Error command ["xcodebuild"] exited with code 70

% cargo tauri ios dev -vvv
       Trace [notify::fsevent] FSEvent: path = `/Users/sope/workspaces/rust/tauri/tauri-mobile/src-tauri/Cargo.toml`, flag = StreamFlags(INODE_META_MOD | ITEM_MODIFIED | IS_FILE)
       Trace [notify_debouncer_mini] raw event: Event { kind: Modify(Metadata(Any)), paths: ["/Users/sope/workspaces/rust/tauri/tauri-mobile/src-tauri/Cargo.toml"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None }
       Trace [notify_debouncer_mini] raw event: Event { kind: Modify(Data(Content)), paths: ["/Users/sope/workspaces/rust/tauri/tauri-mobile/src-tauri/Cargo.toml"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None }
       Trace [notify_debouncer_mini] debounced event: Any
Detected connected device: iPhoneXSMax (iPhone11,6) with target "aarch64-apple-ios"
       Trace [notify::fsevent] FSEvent: path = `/Users/sope/workspaces/rust/tauri/tauri-mobile/src-tauri/Cargo.toml`, flag = StreamFlags(INODE_META_MOD | ITEM_MODIFIED | IS_FILE)
       Trace [notify_debouncer_mini] raw event: Event { kind: Modify(Metadata(Any)), paths: ["/Users/sope/workspaces/rust/tauri/tauri-mobile/src-tauri/Cargo.toml"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None }
       Trace [notify_debouncer_mini] raw event: Event { kind: Modify(Data(Content)), paths: ["/Users/sope/workspaces/rust/tauri/tauri-mobile/src-tauri/Cargo.toml"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None }
       Trace [notify_debouncer_mini] debounced event: Any
       Debug [globset] built glob set; 0 literals, 2 basenames, 0 extensions, 0 prefixes, 0 suffixes, 0 required extensions, 0 regexes
       Debug [globset] glob converted to regex: Glob { glob: "**/npm-debug.log*", re: "(?-u)^(?:/?|.*/)npm\\-debug\\.log[^/]*$", opts: GlobOptions { case_insensitive: false, literal_separator: true, backslash_escape: true, empty_alternates: false }, tokens: Tokens([RecursivePrefix, Literal('n'), Literal('p'), Literal('m'), Literal('-'), Literal('d'), Literal('e'), Literal('b'), Literal('u'), Literal('g'), Literal('.'), Literal('l'), Literal('o'), Literal('g'), ZeroOrMore]) }
       Debug [globset] glob converted to regex: Glob { glob: "**/yarn-debug.log*", re: "(?-u)^(?:/?|.*/)yarn\\-debug\\.log[^/]*$", opts: GlobOptions { case_insensitive: false, literal_separator: true, backslash_escape: true, empty_alternates: false }, tokens: Tokens([RecursivePrefix, Literal('y'), Literal('a'), Literal('r'), Literal('n'), Literal('-'), Literal('d'), Literal('e'), Literal('b'), Literal('u'), Literal('g'), Literal('.'), Literal('l'), Literal('o'), Literal('g'), ZeroOrMore]) }
       Debug [globset] glob converted to regex: Glob { glob: "**/yarn-error.log*", re: "(?-u)^(?:/?|.*/)yarn\\-error\\.log[^/]*$", opts: GlobOptions { case_insensitive: false, literal_separator: true, backslash_escape: true, empty_alternates: false }, tokens: Tokens([RecursivePrefix, Literal('y'), Literal('a'), Literal('r'), Literal('n'), Literal('-'), Literal('e'), Literal('r'), Literal('r'), Literal('o'), Literal('r'), Literal('.'), Literal('l'), Literal('o'), Literal('g'), ZeroOrMore]) }
       Debug [globset] glob converted to regex: Glob { glob: "**/pnpm-debug.log*", re: "(?-u)^(?:/?|.*/)pnpm\\-debug\\.log[^/]*$", opts: GlobOptions { case_insensitive: false, literal_separator: true, backslash_escape: true, empty_alternates: false }, tokens: Tokens([RecursivePrefix, Literal('p'), Literal('n'), Literal('p'), Literal('m'), Literal('-'), Literal('d'), Literal('e'), Literal('b'), Literal('u'), Literal('g'), Literal('.'), Literal('l'), Literal('o'), Literal('g'), ZeroOrMore]) }
       Debug [globset] glob converted to regex: Glob { glob: "**/lerna-debug.log*", re: "(?-u)^(?:/?|.*/)lerna\\-debug\\.log[^/]*$", opts: GlobOptions { case_insensitive: false, literal_separator: true, backslash_escape: true, empty_alternates: false }, tokens: Tokens([RecursivePrefix, Literal('l'), Literal('e'), Literal('r'), Literal('n'), Literal('a'), Literal('-'), Literal('d'), Literal('e'), Literal('b'), Literal('u'), Literal('g'), Literal('.'), Literal('l'), Literal('o'), Literal('g'), ZeroOrMore]) }
       Debug [globset] glob converted to regex: Glob { glob: ".vscode/*", re: "(?-u)^\\.vscode/[^/]*$", opts: GlobOptions { case_insensitive: false, literal_separator: true, backslash_escape: true, empty_alternates: false }, tokens: Tokens([Literal('.'), Literal('v'), Literal('s'), Literal('c'), Literal('o'), Literal('d'), Literal('e'), Literal('/'), ZeroOrMore]) }
       Debug [globset] glob converted to regex: Glob { glob: "**/*.ntvs*", re: "(?-u)^(?:/?|.*/)[^/]*\\.ntvs[^/]*$", opts: GlobOptions { case_insensitive: false, literal_separator: true, backslash_escape: true, empty_alternates: false }, tokens: Tokens([RecursivePrefix, ZeroOrMore, Literal('.'), Literal('n'), Literal('t'), Literal('v'), Literal('s'), ZeroOrMore]) }
       Debug [globset] glob converted to regex: Glob { glob: "**/*.sw?", re: "(?-u)^(?:/?|.*/)[^/]*\\.sw[^/]$", opts: GlobOptions { case_insensitive: false, literal_separator: true, backslash_escape: true, empty_alternates: false }, tokens: Tokens([RecursivePrefix, ZeroOrMore, Literal('.'), Literal('s'), Literal('w'), Any]) }
       Debug [globset] built glob set; 1 literals, 6 basenames, 5 extensions, 0 prefixes, 0 suffixes, 0 required extensions, 8 regexes
       Debug [globset] built glob set; 1 literals, 0 basenames, 0 extensions, 0 prefixes, 0 suffixes, 0 required extensions, 0 regexes
       Debug [ignore::walk] ignoring /Users/sope/workspaces/rust/tauri/tauri-mobile/src-tauri/target: Ignore(IgnoreMatch(Gitignore(Glob { from: Some("/Users/sope/workspaces/rust/tauri/tauri-mobile/src-tauri/.gitignore"), original: "/target/", actual: "target", is_whitelist: false, is_only_dir: true })))
       Debug [globset] built glob set; 0 literals, 3 basenames, 0 extensions, 0 prefixes, 0 suffixes, 0 required extensions, 0 regexes
       Debug [ignore::walk] ignoring /Users/sope/workspaces/rust/tauri/tauri-mobile/src-tauri/gen/apple/Externals: Ignore(IgnoreMatch(Gitignore(Glob { from: Some("/Users/sope/workspaces/rust/tauri/tauri-mobile/src-tauri/gen/apple/.gitignore"), original: "Externals/", actual: "**/Externals", is_whitelist: false, is_only_dir: true })))
       Debug [ignore::walk] ignoring /Users/sope/workspaces/rust/tauri/tauri-mobile/src-tauri/gen/apple/.gitignore: Ignore(IgnoreMatch(Hidden))
       Debug [ignore::walk] ignoring /Users/sope/workspaces/rust/tauri/tauri-mobile/src-tauri/.cargo: Ignore(IgnoreMatch(Hidden))
       Debug [ignore::walk] ignoring /Users/sope/workspaces/rust/tauri/tauri-mobile/src-tauri/.gitignore: Ignore(IgnoreMatch(Hidden))
        Info [tauri_cli::dev] Using 10.254.75.208 to access the development server.
       Trace [hyper::proto::h1::conn] Conn::read_head
       Trace [hyper::proto::h1::conn] flushed({role=server}): State { reading: Init, writing: Init, keep_alive: Busy }
       Trace [hyper::proto::h1::conn] Conn::read_head
       Trace [hyper::proto::h1::io] received 0 bytes
       Trace [hyper::proto::h1::io] parse eof
       Trace [hyper::proto::h1::conn] State::close_read()
       Debug [hyper::proto::h1::conn] read eof
       Trace [hyper::proto::h1::conn] State::close_write()
       Trace [hyper::proto::h1::conn] State::close_read()
       Trace [hyper::proto::h1::conn] State::close_write()
       Trace [hyper::proto::h1::conn] flushed({role=server}): State { reading: Closed, writing: Closed, keep_alive: Disabled }
       Trace [hyper::proto::h1::conn] shut down IO complete
        Info [cargo_mobile2::util] detected host target triple "aarch64-apple-darwin"
Building app...
Command line invocation:
    /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -scheme tauri-mobile_iOS -workspace /Users/sope/workspaces/rust/tauri/tauri-mobile/src-tauri/gen/apple/tauri-mobile.xcodeproj/project.xcworkspace/ -sdk iphoneos -configuration debug -arch arm64 -allowProvisioningUpdates build

User defaults from command line:
    IDEPackageSupportUseBuiltinSCM = YES

Build settings from command line:
    ARCHS = arm64
    SDKROOT = iphoneos17.2

2024-01-05 18:25:48.848 xcodebuild[73897:7201841] Writing error result bundle to /var/folders/j4/lf3vdk9n1fz_cf5ymm0pw4sh0000gn/T/ResultBundle_2024-05-01_18-25-0048.xcresult
xcodebuild: error: Found no destinations for the scheme 'tauri-mobile_iOS' and action build.
       Error [tauri_cli] command ["xcodebuild"] exited with code 70

Reproduction
No response
Expected behavior
No response
Full tauri info output
% cargo tauri info
WARNING: no lock files found, defaulting to npm

[✔] Environment
    - OS: Mac OS 14.2.1 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.75.0 (82e1608df 2023-12-21)
    ✔ cargo: 1.75.0 (1d8b05cdd 2023-11-20)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (environment override by RUSTUP_TOOLCHAIN)
    - node: 20.9.0
    - pnpm: 8.9.2
    - npm: 10.2.4
    - bun: 0.5.9

[-] Packages
    - tauri [RUST]: 2.0.0-alpha.20
    - tauri-build [RUST]: 2.0.0-alpha.13
    - wry [RUST]: 0.35.2
    - tao [RUST]: 0.24.0
    - tauri-cli [RUST]: 2.0.0-alpha.20
    - @tauri-apps/api : not installed!
    - @tauri-apps/cli [NPM]: 2.0.0-alpha.20

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../src
    - devPath: ../src

[-] iOS
    - Developer Teams: None

Stack trace
No response
Additional context
No response

iPhone Settings > Privacy & Security, scroll down to the Developer Mode list item and navigate into it. Then reboot your phone.
Connect your phone to your MacOS device with cable.
Open XCode project and open run device selection list Manage Run Destinations > + >
Run cargo tauri ios dev - the application should be copied to your phone.
iPhone `Settings > VPN & Device Management > trust developer
Run the application

Worked for me now


text:
Tauri Overwriting Fluent UI Dialog Component [bug]

Describe the bug
Hello,
I'm using the Fluent UI dialog component in my project. When I added the component, Tauri complained about not allowing listing the dialog, so I added it to the allow list. However, the rendered dialog appeared weird and only shows a text called.

Figure Rendered Dialog
My Code:

Triggering the Dialog

<DialogTrigger disableButtonEnhancement>
              <Button onClick={handleDelete}>
                <Icon path={mdiDelete} size={0.8} />
                Delete
              </Button>
</DialogTrigger>

Dialog

<Dialog>
        <DialogSurface>
          <DialogBody>
            <DialogTitle>Dialog title</DialogTitle>
            <DialogContent>
              Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam
              exercitationem cumque repellendus eaque est dolor eius expedita
              nulla ullam? Tenetur reprehenderit aut voluptatum impedit
              voluptates in natus iure cumque eaque?
            </DialogContent>
            <DialogActions>
              <DialogTrigger disableButtonEnhancement>
                <Button appearance="secondary">Close</Button>
              </DialogTrigger>
              <Button appearance="primary">Do Something</Button>
            </DialogActions>
          </DialogBody>
        </DialogSurface>
</Dialog>

Added dialog in allowlist otherwise the component won't render

"dialog": {
        "all": true
      },

Fluent UI React Components v9.46.1
Reproduction
This can be reproduced by adding Fluent UI Dialog In Tauri App.
Expected behavior
Should render the dialog box from Fluent UI Dialog
Full tauri info output
[✔] Environment
    - OS: Windows 10.0.19045 X64
    ✔ WebView2: 120.0.2210.144
    ✔ MSVC: Visual Studio Build Tools 2022
    ✔ rustc: 1.72.0-nightly (36fb58e43 2023-06-26)
    ✔ cargo: 1.72.0-nightly (03bc66b55 2023-06-23)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: nightly-x86_64-pc-windows-msvc (environment override by RUSTUP_TOOLCHAIN)
    - node: 18.18.0
    - pnpm: 8.12.1
    - yarn: 1.22.21
    - npm: 9.8.1

[-] Packages
    - tauri [RUST]: 1.5.4
    - tauri-build [RUST]: 1.5.1
    - wry [RUST]: 0.24.7
    - tao [RUST]: 0.16.6
    - tauri-cli [RUST]: 1.5.9
    - @tauri-apps/api [NPM]: 1.5.3
    - @tauri-apps/cli [NPM]: 1.5.9

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../out
    - devPath: http://localhost:3000/
    - framework: React (Next.js)
    - bundler: Webpack

Stack trace
No response
Additional context
No response

I don't see why/how it would call tauri's dialog api here. Seems like Fluent UI Dialog is a fully html/js solution that doesn't interact with the os dialog apis. Could you try to upload a (full) minmal reproduction project to github for us?

I don't see why/how it would call tauri's dialog api here. Seems like Fluent UI Dialog is a fully html/js solution that doesn't interact with the os dialog apis. Could you try to upload a (full) minmal reproduction project to github for us?

Sure, here is a Link to a test app I've made..

Sorry, it was my mistake!! I added an alert in the function which causes this. Thanks For Your Reply..

authors: FabianLars ananduremanan


text:
[feat] add capabilities at runtime

Describe the problem
The ACL system implemented by #8428 is a static implementation of access control for IPC commands. Dynamic usage like starting a localhost server that needs access to the IPC is not supported securely.
An example is the localhost plugin which starts a localhost server to serve your app assets.
To support this use case, we need to add a runtime API that lets you allow commands on a specific execution context.
Describe the solution you'd like
Add a new function in the runtime authority to enable new permissions.
Alternatives considered
No response
Additional context
No response

This is similar to #8798 but adding the capability at runtime is better for performance and validation.


text:
fix: use specta's derive feature

Specta recently moved the specta::Type macro to the derive feature, which broke the docs.rs build for beta 24. This PR fixes that, moving to specta rc 15 as the minimum and using the derive feature.

Published Specta 2.0.0-rc.16 which should hopefully apply the fix to the CI issues we are seeing here.
I don't have access to the branch so @Brendonovich give it a shot.

authors: Brendonovich oscartbeaumont