Void potentials sometimes unusable for clients when host is playing as void fiend

AFAIK this was the only problem caused by the mod. We were playing simulacrum and I (the host) was playing as void fiend while 2 other clients weren't, and every so often a void potential couldn't be interacted with by the clients. Sometimes those potentials were still there on my end and I could choose the item for them while other times they weren't there.
This error was being spammed in one of the clients log:
[Error  : Unity Log] NullReferenceException
Stack trace:
UnityEngine.GameObject.GetComponent[T] () (at <85d1d3e7744a4a47b5f51883bf40bba2>:IL_0021)
VoidFiendHudTweaks.VoidFiendHudTweaks.UpdateCorruptionDeltaNotices () (at <a47a88b3ee9546f3953dacefb5366673>:IL_001B)
VoidFiendHudTweaks.VoidFiendHudTweaks.VoidSurvivorController_OnCorruptionModified (On.RoR2.VoidSurvivorController+orig_OnCorruptionModified orig, RoR2.VoidSurvivorController self, System.Single newCorruption) (at <a47a88b3ee9546f3953dacefb5366673>:IL_0191)
DMD<>?-536932096.Hook<RoR2.VoidSurvivorController::OnCorruptionModified>?-1842606336 (RoR2.VoidSurvivorController , System.Single ) (at <fe03b8ceebe34842b6bc144c914979c5>:IL_0014)
RoR2.VoidSurvivorController.OnDeserialize (UnityEngine.Networking.NetworkReader reader, System.Boolean initialState) (at <78ca0507428e4dbea7a28fe14402f720>:IL_002E)
UnityEngine.Networking.NetworkIdentity.OnUpdateVars (UnityEngine.Networking.NetworkReader reader, System.Boolean initialState, UnityEngine.Networking.NetworkMessage netMsg) (at <0979500d450f40e18351f1e5893a2968>:IL_0012)
UnityEngine.Networking.ClientScene.OnUpdateVarsMessage (UnityEngine.Networking.NetworkMessage netMsg) (at <0979500d450f40e18351f1e5893a2968>:IL_0059)
UnityEngine.Networking.NetworkConnection.HandleReader (UnityEngine.Networking.NetworkReader reader, System.Int32 receivedSize, System.Int32 channelId) (at <0979500d450f40e18351f1e5893a2968>:IL_012D)
UnityEngine.Networking.NetworkConnection.HandleBytes (System.Byte[] buffer, System.Int32 receivedSize, System.Int32 channelId) (at <0979500d450f40e18351f1e5893a2968>:IL_0007)
UnityEngine.Networking.NetworkConnection.TransportReceive (System.Byte[] bytes, System.Int32 numBytes, System.Int32 channelId) (at <0979500d450f40e18351f1e5893a2968>:IL_0000)
RoR2.Networking.SteamNetworkConnection.TransportReceive (System.Byte[] bytes, System.Int32 numBytes, System.Int32 channelId) (at <78ca0507428e4dbea7a28fe14402f720>:IL_0019)
RoR2.Networking.NetworkManagerSystemSteam.OnP2PData (Facepunch.Steamworks.BaseSteamworks receiver, CSteamID senderSteamId, System.Byte[] data, System.Int32 dataLength, System.Int32 channel) (at <78ca0507428e4dbea7a28fe14402f720>:IL_0044)
RoR2.Networking.NetworkManagerSystemSteam.OnSteamClientP2PData (System.UInt64 senderSteamId, System.Byte[] data, System.Int32 dataLength, System.Int32 channel) (at <78ca0507428e4dbea7a28fe14402f720>:IL_000C)
Facepunch.Steamworks.Networking.ReadP2PPacket (System.Int32 channel) (at <0ca17294c1634ce4acda47c711e5ecf1>:IL_0082)
Facepunch.Steamworks.Networking.Update () (at <0ca17294c1634ce4acda47c711e5ecf1>:IL_0054)
Facepunch.Steamworks.BaseSteamworks.Update () (at <0ca17294c1634ce4acda47c711e5ecf1>:IL_0006)
Facepunch.Steamworks.Client.Update () (at <0ca17294c1634ce4acda47c711e5ecf1>:IL_0025)
RoR2.SteamworksClientManager.Update () (at <78ca0507428e4dbea7a28fe14402f720>:IL_0006)
RoR2.RoR2Application.Update () (at <78ca0507428e4dbea7a28fe14402f720>:IL_005F)

Huh, I'll take a look when I get the chance, to be honest i'm really inexperienced with with RoR2 modding so I'm surprised the mod is doing anything network related.

oops, didn't mean to close this yet since I'm not actually sure if I did fix this in the latest version.
I was able to reproduce and fix the error spam but not the void potential issue. I'm not sure if its related to my mod at all to be honest, since I don't think I touch anything close to that.

the void potential thing was probably a byproduct of the errors since they were networking related.
whenever i play multiplayer simulacrum as viend again i'll post here if it was fixed or not

Got it, I'll keep the issue open for now


Update CKV_AZURE_167 for azurerm 4 changes

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #
Test URLs:

Before: https://main--prisma-cloud-docs--hlxsites.hlx.page/
After: https://--prisma-cloud-docs--hlxsites.hlx.page/
Worker: https://prisma-cloud-docs-production.adobeaem.workers.dev/?branch=

@JBakstPaloAlto Terraform changed its syntax for this attribute so we adjusted the check and need to adjust the fix. Can you review and merge when ready? Fixes PCSUP-25842


otelgorm feature: pick which query variables are emitted

otelgorm has the WithoutQueryVariables() option to keep the emitted statement unparameterized. I would like to emit statements that are partially parameterized. My use-case is: my service occasionally handles information which I do not want logged. On the other hand, it's really useful being able to see which IDs a database statement actually hit.
One way to satisfy this is providing something like:
func WithQueryVariableFilter(predicate func(var interface{}) bool) Option

.. and I could provide a filter that only allows uuid strings (etc)
Thoughts? I'd be happy to open a PR.

Sounds like a good idea :+1: Let's see how the code looks like.


Add CI for Python Versions

I launched support for SQLite Vec in a recent version of Feast but, due to some CI issues, only released it to a subset of Python versions.
I was considering contributing to this project to add a CI to verify the Python package behavior. It would also help the Feast support.
The solution would add a github/worfklow like so:
name: unit-tests of Ubuntu and Mac

on: []
jobs:
  unit-test-python:
    runs-on: ${{ matrix.os }}
    strategy:
      fail-fast: false
      matrix:
        python-version: [ "3.9", "3.10", "3.11"]
        os: [ ubuntu-latest, macos-13 ]
        exclude:
            python-version: "3.9"
    env:
      OS: ${{ matrix.os }}
      PYTHON: ${{ matrix.python-version }}
    steps:
      - uses: actions/checkout@v4
      - name: Setup Python
        id: setup-python
        uses: actions/setup-python@v5
        with:
          python-version: ${{ matrix.python-version }}
          architecture: x64
      - name: Install uv
        run: |
          curl -LsSf https://astral.sh/uv/install.sh | sh
      - name: Get uv cache dir
        id: uv-cache
        run: |
          echo "::set-output name=dir::$(uv cache dir)"
      - name: Install dependencies
        run: pip install sqlite_vec
      - name: run script
        run: python unit_tests.py

@asg017 happy to take this on if you're good with it

It now should work in all Python versions, if you update your KNN SQL queries to look like this:
select rowid, distance
from vec_items
where embedding match ?
  and k = 10

Instead of:
select rowid, distance
from vec_items
where embedding match ?
limit 10

The limit 10 syntax only works in SQLite versions 3.41+, which older Python versions typically dont have. But the k = 10 syntax should work on all versions of SQLite
I'm a bit hesitant to add a CI rule to test across multiple Python versions, and that can slow down the CI quite a lot. But if the k = 10 syntax doesn't work for you, happy to dig into it further!

Yeah I swapped that syntax but still encountered issues.
Here's the PR I have https://github.com/feast-dev/feast/pull/4333
I tried some changes and now it fails on 3.10 mac instead of 3.11 as well as Ubuntu.
It feels a bit like wack-a-mole which is why I thought adding the CI would help me. I can just make a fork I suppose and have the CI in mine.

The error that's being raised is
E       sqlite3.OperationalError: no such module: vec0

So I tried the latest version (v0.1.0) and created a simple example with the workflow below and there are some interesting issues. It looks like now these issues are associated with build time errors instead of code failures like I reported in the first run.
For what it's worth, here's the current list of OSs where things are failing (mostly installing)

Failed
a. 3.9 mac-latest
b. 3.10 mac-latest
c. 3.11.0-rc.2* mac-13
d. 3.11-rc.2 mac-latest
e. 3.12 mac-13
f. 3.12 mac-latest
Passed
a. 3.9 ubuntu-latest
b. 3.10-ubuntu-latest
c. 3.10-mac-latest
d. 3.10 mac-13
e. 3.11.0-rc.2 ubuntu-latest
f. 3.12 ubuntu-latest

I briefly looked at your test.yaml workflow and noticed you're building python a bit differently so I'll try to see if it has something to do with using actions/setup-python.
name: unit-tests

on:
  pull_request:
  push:
    branches:
      - main
jobs:
  unit-test-python:
    runs-on: ${{ matrix.os }}
    strategy:
      fail-fast: false
      matrix:
        python-version: [ "3.9", "3.10", "3.11", "3.12"]
        os: [ ubuntu-latest, macos-13, macos-latest ]
        exclude:
          - os: macos-13
            python-version: "3.9"
    env:
      OS: ${{ matrix.os }}
      PYTHON: ${{ matrix.python-version }}
    steps:
      - uses: actions/checkout@v4
      - name: Setup Python
        id: setup-python
        uses: actions/setup-python@v5
        with:
          python-version: ${{ matrix.python-version }}
          architecture: x64
      - name: Install uv
        run: |
          curl -LsSf https://astral.sh/uv/install.sh | sh
      - name: Get uv cache dir
        id: uv-cache
        run: |
          echo "::set-output name=dir::$(uv cache dir)"
      - name: Install dependencies
        run: pip install sqlite_vec==v0.1.0
      - name: run script
        run: python sqlite_vec_demo.py

And the sqlite_vec_demo.py file is just:
import sqlite3
import sqlite_vec

from typing import List
import struct

def serialize_f32(vector: List[float]) -> bytes:
    """serializes a list of floats into a compact "raw bytes" format"""
    return struct.pack("%sf" % len(vector), *vector)

def main() -> None:
    db = sqlite3.connect(":memory:")
    db.enable_load_extension(True)
    sqlite_vec.load(db)
    db.enable_load_extension(False)

    sqlite_version, vec_version = db.execute(
        "select sqlite_version(), vec_version()"
    ).fetchone()

    print(f"sqlite_version={sqlite_version}, vec_version={vec_version}")

    items = [
        (1, [0.1, 0.1, 0.1, 0.1]),
        (2, [0.2, 0.2, 0.2, 0.2]),
        (3, [0.3, 0.3, 0.3, 0.3]),
        (4, [0.4, 0.4, 0.4, 0.4]),
        (5, [0.5, 0.5, 0.5, 0.5]),
    ]
    query = [0.3, 0.3, 0.3, 0.3]

    db.execute("CREATE VIRTUAL TABLE vec_items USING vec0(embedding float[4])")

    with db:
        for item in items:
            db.execute(
                "INSERT INTO vec_items(rowid, embedding) VALUES (?, ?)",
                [item[0], serialize_f32(item[1])],
            )

    rows = db.execute(
        """
          SELECT
            rowid,
            distance
          FROM vec_items
          WHERE embedding MATCH ?
          and k = 3
        """,
        [serialize_f32(query)],
    ).fetchall()

    print(rows)

if __name__ == "__main__":
    main()

*Note I had to use 3.11.0-rc.2 because of this thread.

Yeah, that's right. I'll raise an issue with SQLite and tag it here. I'll rename this issue so it's more explicit in case someone else encounters it.


single az native

See detailed description in the commit message.

this logic does not cover the subnet distribution yet

it seems cluster provision without multiAz flag already makes it possible to put every node into one AZ, so it seems subnet distribution logic looks good as is


Move off travis completely

Afaik the only blocker for us to go full CircleCI is that our travis setup includes macOS.
This also helps decongest travis' facebook/ queue.

I'm looking into this 👍

Is it even supported on CIrcleCI? https://discuss.circleci.com/t/os-x-macos-ios-support-on-circleci-2-0/16430

Oh wait, I think it is now?

cc @dwwoelfel do you know if this is possible now?

I think this is possible by just adding another job that uses the macos container instead of a docker images: https://circleci.com/docs/2.0/testing-ios/#supported-xcode-versions
Should be fairly easy to test, but I'm not sure if I'll have time to get to it in the near future.


Stream test changes

Slightly extends the functionality of the existing USB streaming code to support performance monitoring/unidirectional streams better, allowing the host application to adapt automatically to the test being performed.

Migrates the streaming code into the lib/testing directory alongside the other usb_testutils code, importantly allowing this streaming test to be used in multiple top-level tests in various ways, such as:

intermixing Isochronous streams with Bulk Transfer streams
suspending/resuming/sleep /whilst/ actively transferring data
system integration testing; top-level tests may perform USB traffic whilst exercising other blocks

Please Note Most of this commit is just separating some of the code from tests/usbdev_stream_test.c out into lib/testing/usb_testutils_streams.c/h but sufficient editing is required in this refactoring that the diff doesn't make that very clear.

Renames the functions, data types and macros to suit its new location and reduce the chances of name conflicts.

I have been trying hard to sequence things, but it becomes tricky with a lot of branches/PRs and their dependencies. I had thought it would be okay to leave the function implementation for a subsequent PR since its invocation is inaccessible in this PR.
Having tried to migrate the faster routines into a DIF I've bumped into other environment/software requirements anyway, so I'll just remove the '...Faster' method code for now and leave this as a TODO. Hope that's okay.

Yes, I believe removing this USBUTILS_MEM_FASTER block would be best and then we can merge this PR.

Thanks @alees24 Let's wait for CI to finish and then I'll merge this.


use an actual example

Also, the second example was broken

@steveklabnik redone https://github.com/rust-lang/rfcs/pull/1171


Feature Request: Use WMI object to collect netstat information

Noticing that the get-netstat command uses the netstat.exe binary. Calling that binary not being a bad way and parsing what is on the screen, however if you use the Get-WmiObject win32_process it has most of the information we are trying to get to sans the username. That in conjunction with the Get-NetTcpConnection cmdlet provides the same information. I have made a sample out on my repo.
Some things I may have overlooked,
I am not sure when get-net* was implemented so it may not be available in PS v2
It's not currently the prettiest code it was written to be a one line tool for rapid deployment
https://github.com/mwilco03/GPSBL/blob/master/Get-NetStatObject
If this is interesting I'd be happy to help contribute.

Agree the netstat screen scrapping is awful and doesn't work for non-English versions of Windows. A while back I wrote a version that would do this using PSReflect, but given that triggers lots of AV, I decided not to release it. I'd welcome your contribution, if you want to submit a PR or if you're granting permission, I can copy and paste your code and add a new collector.

100% have permission to use, just in case I messed up the PR.
Very happy to contribute to a great framework.


Automated cherry pick of #2097: secgroups get distinct tenant

Cherry pick of #2097 on release/2.11.
#2097: secgroups get distinct tenant

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.11@c90a3bd). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.11   #2098   +/-   ##
==============================================
  Coverage                ?   7.17%
==============================================
  Files                   ?     445
  Lines                   ?   69523
  Branches                ?       0
==============================================
  Hits                    ?    4985
  Misses                  ?   64126
  Partials                ?     412

Flag
Coverage Δ

#aFlag
7.17% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/secgroups.go
2.47% <0%> (ø)

Continue to review full report at Codecov.

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

/approve
/lgtm


Fix bug in callback

here

I already "fixed" this (deleted it) in #74, since Debug.Trace exists now and can save the same purpose. We have jshint setup so that code like this in the JS would be an error now too.


Inconsistent indentation with dataview embedded lists

Is the bug present when using the default Obsidian theme?
No
Is the bug present when snippets and plugins are disabled?
Yes
Minimal theme version
6.0.4
Describe the bug
The styles for dataview embedded lists are applied inconsistently in two ways:

The rendered view (right pane) has an indent applied to the taskList that isn't present in the live preview (see Grouped section). I'd prefer the non-indented, "strict embed" style, but consistency between the two would be nice, and/or an easy way to override.
The first-level list items (see Ungrouped section) are outdented when the taskList is rendered without grouping. The ungrouped version lacks a div with dataview result-group class wrapping the ul.

Raw markdown:
## Tasks

- [ ] one
    - [ ] subtask
- [ ] two

## Dataview

### Grouped

```js
dv.taskList(dv.current().file.tasks, true)
```

```dataviewjs
dv.taskList(dv.current().file.tasks, true)
```

### Ungrouped

```js
dv.taskList(dv.current().file.tasks, false)
```

```dataviewjs
dv.taskList(dv.current().file.tasks, false)
```

Debug info
SYSTEM INFO:
	Obsidian version: v0.16.2
	Installer version: v0.15.9
	Operating system: Darwin Kernel Version 21.6.0: Wed Aug 10 14:28:23 PDT 2022; root:xnu-8020.141.5~2/RELEASE_ARM64_T6000 21.6.0
	Login status: logged in
	Catalyst license: insider
	Insider build toggle: on
	Live preview: on
	Legacy editor: off
	Base theme: dark
	Community theme: Minimal
	Snippets enabled: 1
	Restricted mode: off
	Plugins installed: 57
	Plugins enabled: 2
		1: Dataview v0.5.45
		2: Minimal Theme Settings v6.0.5

RECOMMENDATIONS:
	Custom theme and snippets: for cosmetic issues, please first try updating your theme and disabling your snippets. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.
	Community plugins: for bugs, please first try updating all your plugins to latest. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community plugins.

I notice this says I have 1 snippet enabled still, but the two custom css files I use are disabled in settings.

I was able to get alignment to be more consistent by resetting the max-width:var(--max-width); from line-width.scss. My override (using the generated selectors)
body:not(.table-100):not(.table-max):not(.table-wide) .markdown-preview-view.is-readable-line-width:not(.table-100):not(.table-max):not(.table-wide) .block-language-dataview h4,
body:not(.table-100):not(.table-max):not(.table-wide) .markdown-preview-view.is-readable-line-width:not(.table-100):not(.table-max):not(.table-wide) .block-language-dataview>h4,
body:not(.table-100):not(.table-max):not(.table-wide) .markdown-preview-view.is-readable-line-width:not(.table-100):not(.table-max):not(.table-wide) .block-language-dataviewjs h4,
body:not(.table-100):not(.table-max):not(.table-wide) .markdown-preview-view.is-readable-line-width:not(.table-100):not(.table-max):not(.table-wide) .block-language-dataviewjs>h1,
body:not(.table-100):not(.table-max):not(.table-wide) .markdown-preview-view.is-readable-line-width:not(.table-100):not(.table-max):not(.table-wide) .block-language-dataviewjs>h2,
body:not(.table-100):not(.table-max):not(.table-wide) .markdown-preview-view.is-readable-line-width:not(.table-100):not(.table-max):not(.table-wide) .block-language-dataviewjs>h3,
body:not(.table-100):not(.table-max):not(.table-wide) .markdown-preview-view.is-readable-line-width:not(.table-100):not(.table-max):not(.table-wide) .block-language-dataviewjs>h4,
body:not(.table-100):not(.table-max):not(.table-wide) .markdown-preview-view.is-readable-line-width:not(.table-100):not(.table-max):not(.table-wide) .block-language-dataviewjs>p,
body:not(.table-100):not(.table-max):not(.table-wide) .markdown-preview-view.is-readable-line-width:not(.table-100):not(.table-max):not(.table-wide) .dataview.dataview-container>.contains-task-list,
body:not(.table-100):not(.table-max):not(.table-wide) .markdown-preview-view.is-readable-line-width:not(.table-100):not(.table-max):not(.table-wide) .dataview.dataview-error,
body:not(.table-100):not(.table-max):not(.table-wide) .markdown-preview-view.is-readable-line-width:not(.table-100):not(.table-max):not(.table-wide) .dataview.list-view-ul,
body:not(.table-100):not(.table-max):not(.table-wide) .markdown-preview-view.is-readable-line-width:not(.table-100):not(.table-max):not(.table-wide) .dataview.result-group {
  max-width: 100%;
}

Same problem. Waiting to be fixed officially.

I'm also stuck trying to debug this issue. Please update if anyone was able to find a workaround. I'm using Minimal theme.

Please try again with Minimal 7.0+

I still have this issue:

But it's also present while using the default theme:

Yeah, still looks like it's not quite consistent. Edit mode on the left, view mode on the right:

This
.is-live-preview ul[class="contains-task-list"]{
	padding-left: 1.9em !important;
	text-indent: -1.5em !important
}

Seems to solve the issue, on my device, for Dataview, but not for Tasks.

OK, this seems to solve the issue for me:
/* fix for Dataview checklists */
.is-live-preview ul[class="contains-task-list"]{
	padding-left: 1.9em !important;
	text-indent: -1.5em !important
}

/* fix for Tasks checklists */
.is-live-preview ul > li.plugin-tasks-list-item {
	padding-left: 0em !important;
	text-indent: -1.5em !important
}

I found this issue whilst investigating the non-indentation of task lines in Tasks query blocks in Live Preview.
The discussion here has been helpful.
Summary
After much more experimentation, I am now as confident as I can be that it happens in many themes and multiple plugins, and so should be fixed in Obsidian, and not in individual themes in plugins (especially as the fix requires !important so is intrusive).
Reasoning
Please see the self-contained comment: https://github.com/obsidian-tasks-group/obsidian-tasks/issues/2361#issuecomment-1774049936


refactor: FacetedSearchSettingsModule

Checklist

[x] the contributor license agreement is signed
[x] commit message follows commit guidelines
[x] tests are included
[ ] screenshots are included showing significant UI changes
[ ] documentation is changed or added

Description of change
Create rest module FacetedSearchSettings.
Replace all Axios usage in FacetedSearchSettingsModule.
Will remove deps query-string after mergeing.

Gah, the old GHA out of memory issue surfaces again.
But I see key tests have passed and also the New UI tests are run on CodeBuild, so let's merge this.


Inconsistent openapi-typescript import

Environment

Operating System: Linux
Node Version:     v18.16.0
Nuxt Version:     3.6.5
Nitro Version:    2.5.2
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      modules, apiParty, typescript
Runtime Modules<EMAIL_ADDRESS>Build Modules:    -

Reproduction
Reproduction can be done with the playground being run separate from the rest of the repo.
cp -r playground ../api-playground
cd ../api-playground
echo 'shamefully-hoist=true' > .npmrc
pnpm add -D nuxt nuxt-api-party openapi-typescript
pnpm nuxi prepare

Describe the bug
Whether openapi-typescript is imported as a module or function seems to depend on whether the package is installed in node_modules. When in node_modules, it behaves as expected, being imported as a module. Otherwise, it imports the function. I'm not sure whether this is an issue with node or typescript.
I suggest the following change to openapi.ts.
diff --git a/src/openapi.ts b/src/openapi.ts
index 2527990..cc84fd5 100644
--- a/src/openapi.ts
+++ b/src/openapi.ts
@@ -3,6 +3,15 @@ import { useNuxt } from '@nuxt/kit'
 import type { OpenAPI3, OpenAPITSOptions } from 'openapi-typescript'
 import type { Endpoint } from './module'

+function importOpenapiTypescript() {
+  return import('openapi-typescript').then((openapiTS) => {
+    // The import is somehow different during dev and prod
+    if (typeof openapiTS === 'function')
+      return openapiTS
+    return openapiTS.default
+  })
+}
+
 export async function generateTypes(
   endpoints: Record<string, Endpoint>,
   globalOpenAPIOptions: OpenAPITSOptions,
@@ -15,7 +24,7 @@ export async function generateTypes(
       throw new Error('Caught process.exit()')
   })

-  const openapiTS = await import('openapi-typescript')
+  const openapiTS = await importOpenapiTypescript()
   const schemas = await Promise.all(
     Object.keys(endpoints).map(async (id) => {
       let types = ''
@@ -25,7 +34,6 @@ export async function generateTypes(
       runningCount++

       try {
-        // @ts-expect-error: ESM import type mismatch
         types = await openapiTS(schema, {
           commentHeader: '',
           ...globalOpenAPIOptions,

Additional context
No logs were created to indicate an error, just the types not being generated. When I edited the javascript to add a console.error() inside the catch block surrounding openapiTS(), I got the error openapiTS is not a function.
Logs
ERROR  openapiTS is not a function                                                                                5:02:09 PM

  at /home/username/api-playground/node_modules/.pnpm/nuxt-api-party@0.15.1/node_modules/nuxt-api-party/dist/module.mjs:20:23
  at async Promise.all (index 0)

@killjoy1221 Can you verify that it now works as intended? 🙂

Yes, it works fine now.
On Wed, Aug 23, 2023 at 7:43 AM Johann Schopplich @.***>
wrote:

@killjoy1221 https://github.com/killjoy1221 Can you verify that it now
works as intended? 🙂
—
Reply to this email directly, view it on GitHub
https://github.com/johannschopplich/nuxt-api-party/issues/35#issuecomment-1689811802,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2AQKVWL4QCLCBJM44INW3XWXUGTANCNFSM6AAAAAA3Z6X6J4
.
You are receiving this because you were mentioned.Message ID:
@.***>


Docforge blocks when multiple errors occur

What happened:
Docforge blocks forever when there are multiple errors. The patterns is relatively hard to pin.
What you expected to happen:
Non-blocking executution
How to reproduce it (as minimally and precisely as possible):
run TestDispatchFaultTolerantOnError with
tasksCount := 200  maxWorkers := 25
and change faultySender's Work to return error unconditionally.
Anything else we need to know:
The core problem was pinned to be in a race condition due to unsynchronized shared resource errcList (the slice gathering all worker error channels),
How to categorize this issue?
/kind bug
/priority critical

fixed with #145

fixed with #145


SegmentationTree class is missing

There are couple references in ACCESS2021_release of SegmentationTree but it's nowhere to be found

Hello,
Can you provide more details on which script where you trying to execute,
and the specific line of code throwing the error?
Thanks,
Kdavila
On Tuesday, January 2, 2024, MansurBib @.***> wrote:

There are couple references in ACCESS2021_release of SegmentationTree but
it's nowhere to be found
—
Reply to this email directly, view it on GitHub
https://github.com/kdavila/lecturemath/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABU72UJYTAYWCPTAEVKVRNDYMSZF3AVCNFSM6AAAAABBKYXCX6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGA3DGMJTHAYTMMI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

in
ACCESS2021_release/AccessMath/annotation/keyframe_words.py
ACCESS2021_release/AccessMath/annotation/gt_projection_annotator.py
ACCESS2021_release/AccessMath/annotation/gt_word_annotator.py
ACCESS2021_release/AccessMath/annotation/gt_unique_word_annotator.py
there are imports for SegmentationTree like this
from AccessMath.preprocessing.content.segmentation_tree import SegmentationTree

but when looking into the path there is not segmentation_tree.py or the class SegmentationTree to be found in the repository

I see. Please note the AccessMath library has been used internally for
multiple projects including some earlier publications and even a few
non-published projects. This repository only contains the minimum set of
classes needed to reproduce the work specifically related to our IEEE
ACCESS paper from 2021 (
https://ieeexplore.ieee.org/abstract/document/9494351). In that paper, we
did not use the word-level annotator, hence we omitted the class. We have a
separate release for the annotation tools:
https://github.com/adaniefei/vid_annotation_tool/tree/main
That said, I just pushed the missing file.
Best,
kdavila
On Tuesday, January 2, 2024, MansurBib @.***> wrote:

in
ACCESS2021_release/AccessMath/annotation/keyframe_words.py
https://github.com/kdavila/lecturemath/blob/7836868241de4c83f3884c4511a82d7af9e22477/ACCESS2021_release/AccessMath/annotation/keyframe_words.py#L6
ACCESS2021_release/AccessMath/annotation/gt_projection_annotator.py
https://github.com/kdavila/lecturemath/blob/7836868241de4c83f3884c4511a82d7af9e22477/ACCESS2021_release/AccessMath/annotation/gt_projection_annotator.py#L760
ACCESS2021_release/AccessMath/annotation/gt_word_annotator.py
https://github.com/kdavila/lecturemath/blob/7836868241de4c83f3884c4511a82d7af9e22477/ACCESS2021_release/AccessMath/annotation/gt_word_annotator.py#L20
ACCESS2021_release/AccessMath/annotation/gt_unique_word_annotator.py
https://github.com/kdavila/lecturemath/blob/7836868241de4c83f3884c4511a82d7af9e22477/ACCESS2021_release/AccessMath/annotation/gt_unique_word_annotator.py#L26

there are imports for SegmentationTree like this

from AccessMath.preprocessing.content.segmentation_tree import SegmentationTree
but when looking into the path there is not segmentation_tree.py or the
class SegmentationTree to be found in the repository
—
Reply to this email directly, view it on GitHub
https://github.com/kdavila/lecturemath/issues/1#issuecomment-1874779297,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABU72UIYMOOVLSQUS4ZJ75TYMS7LBAVCNFSM6AAAAABBKYXCX6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZUG43TSMRZG4
.
You are receiving this because you commented.Message ID:
@.***>

Ohhh I understand. Thank you very much and best wishes


Fix for Remote Rendering build failure

This fixes an issue with Netty version resolution.

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

/azp run java - remoterendering - tests

/azp run java - remoterendering

API change check
API changes are not detected in this pull request.


test: fix flaky tests by introducing komega

This change will hopefully fix the flaky integration tests that have been annoying me in several PRs. I like Ginkgo/Gomega, but I know the maintainers are not big fans. 😁 But as long as we are using Ginkgo/Gomega, I think komega (part of controller-runtime) makes the code more compact and avoids attempts on outdated test resource updates.
/cc @inteon @SgtCoDFish

/test pull-trust-manager-smoke

Created manual cherry-pick PR: https://github.com/cert-manager/trust-manager/pull/264


chore: update pr template

To Reviewers

[x] Skipping review is not a problem (style, chore ONLY)
[ ] Not that difficult

Type of Change

[ ] New feature
[ ] Bug fixes
[ ] Feature improvement

[ ] These changes require a usage change

[x] Others (performance improvement, refactoring, CI/CD, etc.)

Checklist

[ ] Updated Storybook documents
[ ] Tested with console

Description
Things to Talk About

:tada: This PR is included in version 1.1.0-beta.451 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[FEATURE] Deprecate combine in Swarp

Is your feature request related to a problem? Please describe.
I'm always frustrated when I read the swarp processor, which is full of warnings that combine should always be true since it makes no difference.
Describe the solution you'd like
I want to deprecate combine as an argument (have it always be True). It seems like that unexpectedly makes a difference to the end data though.

We need combine=True for specific use-cases. Right now, we need it only for image subtraction, which is consistent with the imsub test failing for #449 .
The warning in swarp has been updated accordingly and processors using combine=True catch the warnings and supress it. Closing.


Does not reflect correctly when camera FOV changes from default value

If main camera be physical and sensorSize or focalLength changes, same as change in FOV value in non physical camera, the reflection position is not true anymore

I'm not maintaining this project any more. The planer reflection component in HDRP does the same thing in a more sophisticated way. I'll keep this issue ticket opened for record purpose, please don't expect that this will be fixed.

Bumping this issue... I know you are not maintaining this project anymore, but it's too complicate for me to move now to HDRP (need to change all my shaders/materials... and I've tons of custom ones), so I'm looking a solution like your great Plane Reflection, that, however, has the FOV problem...

p.s. I've solved deleting the ProjectMatrix line.

Yeah It works if u delete the Project matrix line.... Anyway how should I give credits to it on my game? during the credits?
thanks


Can I download the course after I pay?

Can I download the course after I pay?
Thank you

I believe download is only available for mobile apps on Udemy, it can't be downloaded on the desktop version, but is streamed on-demand.


Fix getElementText util function

close #21
I believe that we got only this cases:

await expect(page).toHaveText('test') 2 arguments, look through body to contain 'test'
await expect(page).toHaveText('.selector', 'test') 3 arguments, wait for .selector, look through .selector to contain 'test'
await expect(page).toHaveText('.selector', 'test', options) 4 arguments, wait for .selector with passed options, look through .selector to contain 'test'
await expect(element).toHaveText('test') 2 arguments, look through element to contain 'test'

@mxschmitt what do you think about possible cases? I'll fix tests and add some more for this cases tomorrow.
I just think that there is no much sense in this case:
await expect(element).toHaveText('test', options)

cause I just don't have any ideas where should we pass them

@mxschmitt what do you think about possible cases? I'll fix tests and add some more for this cases tomorrow.
I just think that there is no much sense in this case:
await expect(element).toHaveText('test', options)

cause I just don't have any ideas where should we pass them


[Pages] Clarify individual header length limit

Similar to the redirects documentation, we should include the amount of headers you can declare and the maximum length of a given header value.
Ref:
https://developers.cloudflare.com/pages/platform/limits/#headers
https://community.cloudflare.com/t/cloudflare-pages-header-file-line-limit/387052/5?u=kiannh

@KianNH Do you not think it would go better in the limits section?

Probably - I was just following along with how we do it in _redirects where the overall limit of the given rules (i.e 100 for _headers and 2,100 for _redirects) is in limits and the per-rule character length is in the individual file, i.e redirects
Could put it in both? It'd make sense that if you know how to use them but want to know about limits, you might only check the specific limits page.

Personally, I think it would be best to put it in both. When I get an issue, I check the limit's section to see if it's a known limitation. It probably also doesn't hurt to put it in two places even if it might be changed

Yep we should definitely put it in both. Appreciate the issue!

Updated the limit from 1,000 to 2,000

The limit bump to 2k hasn't been released yet pending testing so put it back to 1k - also clarified that the limit is for the entire line, not just the header value.


App icon as tab icon without tint

Sadly I have to ask this, the customer is resistant to any common sense or guideline. Which means I have to place a colored app icon as tab Icon, is that even possible or do I have to alter the lib for that purpose?

just give an active and in-active icon then it won't apply tints for them


Update README.md

Updated the link to how to upgrade Ghost

Please include a description of your change & check your PR against this list, thanks!

[x] There's a clear use-case for this code change
[x] Commit message has a short title & references relevant issues
[x] The build will pass (run yarn test and yarn lint)

More info can be found by clicking the "guidelines for contributing" link above.

Thanks for spotting @TheodoreChu :+1:


Add completed bonfire comparisons

(Initially #1212, which I opened and @BerkeleyTrue closed without discussion and which I can't reopen.)

This really isn't Ideal to compare your solutions

Actually, from a learner's perspective, being able to compare their own solution against the ideal solution is absolutely ideal.  In fact, "If feedback is not appropriate (either from an instructor or from self-reference to an information source), then the practice tends to be ineffective or even detrimental to learning." [1].  It isn't about competition with others, but self-reflection.
One of the biggest challenges becomes identifying "the ideal solution".  But interestingly, reviewing peers' work can be, in and of itself, an effective pedagogical method if certain conditions are met  [2, 3, 4], and FCC is a poster-child for these conditions!
The current approach means:

Having to go search for feedback (e.g. go look it up on the wiki), which means many learners simply won't get that feedback.
Lack of comparison between alternative answers (e.g. comparing and rating multiple working solutions) means learners aren't exposed to other solution paradigms, and therefore aren't developing relevant critical thinking skills.

And to be very clear, providing alternative solutions does not necessitate competition.  Reviewing multiple alternative solutions (including non-optimal solutions), and comparing peers' ratings of solutions, is the goal.  There is no need for names, affiliations, or anything else that breeds competition with anyone else.  However, it should encourage self-reflection.
[1] https://en.wikipedia.org/wiki/Practice_(learning_method)#Deliberate_practice
[2] https://onlinelearninginsights.wordpress.com/2013/03/09/why-and-when-peer-grading-is-effective-for-open-and-online-learning/ , particularly:

Listed below are a list of conditions needed to ensure that peer grading  is effective:

When learners are at a similar skill level.
When assignments are low stakes [i.e. when a course is taken for professional development of personal interest as was the Digital Cultures course].
Where credit is not granted.
When learners are mature, self-directed and motivated.
When learners have experience in learning and navigating within a networked setting [if the review is completed in an open and online setting].
Learners have a developed set of communication skills.

[3] http://www.lrdc.pitt.edu/schunn/research/peers.html
[4] http://eric.ed.gov/?id=EJ938586

Please do NOT open new duplicate issue's. You can keep discussing on the issue I closed last night and I will happily re-open it.
Happy Coding.


Add support for UptimeRobot probes

Currently only Pingdom Probes are supported. Make necessary changes to also support UptimeRobot and change the behaviour to automatically update a domain with all available probes/services but make it optional to only add a specific service with a command line flag -s|--service where the service is then directly named like pingdom or uptimerobot.

https://uptimerobot.com/locations

Fixed with v2.1.0 Release


[Question] How to handle prod/dev request flow

Hey peeps love your work!
After developing my app locally using a smee channel, I went to deploy a production version and got stuck in a predicament about how to handle future development of my app. I am using probot as a one-off app to automate a single repo and not a publicly shared/installable app.
I would like the deployed/prod version to continue handling webhook events while I am developing changes locally that way no events get dropped or error due to my local development. That said I end up with two questions:
Toggling webhooks (dev/prod)
First, what is the best way to toggle the webhook in the GitHub App config between the local smee url and the production url? Seeing as GitHub Apps are only allowed one webhook this is non-trivial to me.

I thought of a few possibilities such as:

Set GitHub App webhook to the prod url and a route that somehow knows dev vs. prod (see next question) and redirects to either smee or the webhook handling route. Not sure if smee would like this or not.
Set GitHub App webhook to the prod url and add the dev smee url in the test repo settings but then the event context.octokit does not have access to the installationId and all requests return 401. Thus would require somehow injecting the installationId or using a custom GitHub client which would not make sense for sharable GitHub Apps. Also the webhook events could be different.

Dev event flagging
Second, what is the best way to indicate an event as development? My thoughts on a solution...

I thought about adding a condition for each event, for example a label could be added for pull_request events say dev-ci that is ignored on the prod app and only run on the local development app. This is not ideal as not all events have a good way to indicate this such as a push event that would likely require a branch name matching.
Another approach could be to have a top-level filter for local development that passes the event to a filter and then conditions could be set on the fly and only events that meet these conditions are forwarded to probot. This would not prevent the prop instance from handling this and would likely result in duplicated actions.
Or could be a mix between the two where you can set top-level prod or dev filters for each event type and then all the events are filtered on both dev and prod running instances.

Anyways, just wondering if anyone else has come across this and found a good solution. Open to all ideas. Thanks 🙏🏼

I create a separate app for local development. For bigger apps I end up with three apps

production app
Staging/Beta app
Local development app (sometimes one per developer)

Howe that helps?

@gr2m Ahh right forgot to list that as an option. That makes sense.
So what is your approach, if any, for filtering only events that you are actively developing?

I'm not sure what you mean by filtering events? The production app would point at a server somewhere, while your local dev app would point to a smee URL. You would install the dev app on a separate test repository

Ahh I missed the test repo part, I was thinking of testing it on an active repo. That makes sense. Thanks for the suggestions, much appreciated!


ci: include testing for build.gradle and *.sbt

Fixes #issue

It's a good idea to open an issue first for discussion.

[ ] I have followed Sample Format Guide
[ ] pom.xml parent set to latest shared-configuration
[ ] Appropriate changes to README are included in PR
[ ] API's need to be enabled to test (tell us)
[ ] Environment Variables need to be set (ask us to set them)
[ ] Tests pass:   mvn clean verify required
[ ] Lint  passes: mvn -P lint checkstyle:check required
[ ] Static Analysis:  mvn -P lint clean compile pmd:cpd-check spotbugs:check advisory only
[ ] Please merge this PR for me once it is approved.

This is bigger in scope than I realized. The test runners for gradle and sbt need to be created; Java versions checked; etc. Closing and will revisit when time allows.


Bug: Odd error message on kustomization

Where are we getting this from?
Output from flux/message on the object is Health check failed after 30.01174149s, timeout waiting for: [Deployment/test/backend status: 'Failed']

@sympatheticmoose Can you look at your browser console and let me know what the /kustomization endpoint is returning?

This might actually be a CSS issue where the beginning of the message is getting truncated. Here is what I get:

Nope, this is a valid message from the kustomize controller:
https://github.com/fluxcd/kustomize-controller/blob/f2f9395c4d7754144f48ac80a03bbba228a1dc32/controllers/kustomization_controller.go#L861

I'm not yet convinced. How frequent is our polling? The bug is that there is a different error message displayed here than is displayed through inspection of the object through kubectl/flux

A refresh of the page will demonstrate the behavior. I would bet that it will be in this state for 30s after the object is created or while it is running its timeout.

Re-opening until we are both convinced its working @sympatheticmoose

@sympatheticmoose How do we reproduce the steps to investigate this issue? It looks like the most recent changes on main does not even have a status:

@rokshana-b the status is shown in the top right of your screenshot. It was moved to allow for a larger error message.
In terms of recreating, all objects including this specific kustomization are in https://github.com/sympatheticmoose/gitops-error-scenarios/, kustomization: https://github.com/sympatheticmoose/gitops-error-scenarios/blob/main/clusters/my-cluster/kc-health-check/podinfo-deploy-2-bad-kustomization.yaml
My concern is that there seemed to be inconsistency/potentially timing related, in the error message depending on whether you queried using the Flux CLI or viewing in the UI.

Accidentally closed this

@sympatheticmoose I cloned your error-scenario repo and bootstrapped flux using that repo. This is what I got:


feature(instrumentor): Define specific mutants to instrument and don't mutate other mutants

Is your feature request related to a problem? Please describe.
What I want to be able to do is to rerun specific mutants that survived on the last run, and only those mutants. By doing this I can get a faster feedback loop when looking for mutants in my project.
Describe the solution you'd like
I'd like to be able to define mutants to be instrumented with the following specificity:

What file(s) to mutate (Yes, the --mutate command already serves this purpose, but I think specifying the file path will be necessary for creating an identity of the mutant that I desire
What character range(s) I want mutated. This would be in the format of defining a startLine and startCharacterOffset as well as endLine and endCharacterOffset. This should be a strict match, where any mutants who are inside those offsets without matching those offsets should be ignored

As an extra, if it were possible to specify:

What kind of mutation you want
What the mutation result is

That would allow greater control over specifying which mutants survived such as

const a = "default string"
const a = ""; (killed)
 const a = "Stryker Was Here"; (survived)

I'm not sure how this data would be passed into the CLI command. With the level of specificity I'm looking for perhaps passing in a JSON string would be good, if user unfriendly. Perhaps there should be a user-friendly option where they just pass in locations such as --specificMutants src/filename.ts::1:3::1:5,src/filename.ts::2:1::2:2 where the format would be [filename]::[line:column]::[line:column] and then a more tool-oriented input for JSON like --specificMutantsJson?
Describe alternatives you've considered
I considered creating a separate plugin that would act as a mutant filtering plugin, but it was suggested that this would be much better as a core functionality that might then be re-used for future incremental build functionality. I think that's a better idea and integrating it at the instrumentor level as opposed to post-instrumentation would also save some work since there would be less code to mutate over all.
Additional context
The overall context is that I have a IDE plugin that can run mutations, keep track of surviving mutants and when it comes to a "Rerun surving mutants" functionality can also keep track of the positions of the surviving mutants after the source file has been edited. This tool should hopefully be able to provide as much specificity as is needed in order to pinpoint the exact mutants that should be re-run.

Hmm this is interesting. How about trying to keep it simple
--mutate file:fromLine:Column:toLine:toColumn
For example:

--mutate foo.js:1:0:5:0 would mutate foo.js from line 1 to line 5 (exclusive).
--mutate bar.js:1:4:1:20 would mutate bar.js only on line 1 between characters 4 and 20 (exclusive).

We would need to do some parsing magic to make sure globbing still works as expected

I think specifying mutants and using globs should be mutually exclusive. If you're specifying what mutants you want, does it make sense to be specifying text ranges for a non-specific file pattern? If we can detect if a filestring is a glob, we could throw an error if there's also lines/columns. On the other hand it's not like it'd hurt to let the user specify lines/columns for globs, I just don't see it as being a desirable effect
What do you think of having another interface for the more specific information such as mutation type and output?

On the other hand it's not like it'd hurt to let the user specify lines/columns for globs

Actually, it kind of does, since you could specify a position in the source file that doesn't exist. For example
/* 1 */ import foo from 'foo';
/* 2 */
/* 3 */ foo()

in this example line, 3 doesn't exist. Neither does line 3 column 9. It would be useful if we can give a clear error message, so users know that they did something wrong.
I think not allowing glob expressions and locations to be mixed makes a lot of sense.

What do you think of having another interface for the more specific information such as mutation type and output?

You mean mutator name and replacement 😉. If we would really want to provide those, then we would need something linke --specificMutantsJson. I personally don't see the need really.
Maybe you can explain your exact use case. I have a hunch that it has to do with your IntelliJ plugin 😏, but maybe you want to elaborate a bit more?

Maybe you can explain your exact use case. I have a hunch that it has to do with your IntelliJ plugin 😏, but maybe you want to elaborate a bit more?

 I put this in the context of the ticket, but I'll elaborate a bit
The idea of this feature in the intellij plugin is to imitate a feature for regular test frameworks where you can Re-run only failed tests. Implemented well, it could allow a user to run stryker over a set of files to see what mutations exist in the first place and then re-run only those mutants that have survived while they explore ways to write good tests to bust those mutants.
My personal workflow, and I suspect one that others use, is to go on "mutant busting" sessions once in a while over the whole codebase to see what I've missed over a couple weeks worth of development. Doing this means I tend to re-run my mutation tests very often, so being able to pinpoint only the mutants I'm focusing on can save a lot of time.
As for the specific use-case of --specificMutantsJson to allow for more information, I want to be able to make my "Re run surviving mutants" a rather smart command that only the mutants that survived, not other mutations of the same code that's already been busted. In the example that I posted for more specific options:
const a = "default string"

Becomes:
Mutant 1: const a = ""; (killed)
Mutant 2: const a = "Stryker Was Here"; (survived)

If the user hits a "Re run surviving mutants button" the expected result would be that only Mutant 2 would run, because Mutant 1 is already dead. Having more control over exactly which mutants are generated for a given node, rather than just disabling nodes altogether, I can provide a smarter and more intuitive feature to the user.
If I were a user and a feature called "Re-run surviving mutants" ran both Mutant 1 and Mutant 2, I'd assume it was bug in the tool rather than an implementation detail to keep interfaces simple.

If you only want to rerun the survived mutants, why don't we make that specific use case possible in that case?
This could use the json reporter. We can read the json file in and determine exactly which mutants survived the last time. We can then load the input files to verify if nothing changed, if it did, we can just decide to rerun all mutants for that file.
This is beginning to sound like --diff mode, except that one only reruns changed files (ignoring any tests that might have changed).

If you only want to rerun the survived mutants, why don't we make that specific use case possible in that case?

I'm happy to build that as a feature too, but with my plugin I also want to support the case of re-running only the failed mutants if the file has changed

I see. Yes, rerunning on all --survived mutants is different than using --diff mode.
Maybe we could add a flag called --survived? It would rerun both survived and no-coverage mutants. It would have to rely on the json file format. You could then combine it with --mutate to be sure to only run survived mutants on a given file.
@simondel @hugo-vrijswijk do you have thoughts on this?

I would love this feature for several reasons:

Shorter feedback loop, since I need to mutate less files and less segments.
More focused feedback. When I'm running mutation tests, I am essentially running around trying to splat them all. The less stuff I need to look at, the easier it becomes to splat them. Currently, I have to recheck the full report to see what mutants I need to splat next. That's really time consuming.

Whole topic sounds to me like mutants cache or stryker cache. I can imagine, that just 'stryker run' would be enough to repeat with cache when I change only tests. When code, then run all.

@nicojs I think a --survived flag sounds very good. I would however only run survived mutants in source files that haven't changed since the last run. If the source files did change, they should all be tested again in my opinion.
By only changing your tests you could cause other mutants to survive which were previously killed, but this is not the case when you're adding tests.

Whole topic sounds to me like mutants cache or stryker cache. I can imagine, that just 'stryker run' would be enough to repeat with cache when I change only tests.

That's an interesting idea. I think we currently don't want to add that. We could add the json reporter to the default list of reporters, that way running stryker run would work.
Note: the JSON report currently doesn't have enough information to do a proper diff run, nor is this feature request about a true "diff" run. It only contains info about the files under test, not the test files. We're slowly adding that support, but it will take some time. I will create an issue for --diff mode when I have some time.


Add change failure rate chart component

What this PR does / why we need it:

Create a common chart component and use it to implement the CHR chart component.(Implemented based on the original DeploymentFrequencyChart )

Use that common chart component at the Deployment Frequency Component too.

Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

Nice.
/lgtm

🚀 🚀 🚀
/approve


Rewrite using tree-sitter

I have started on a tree-sitter-based rewrite of go-mode. The plan going forward is to tag a final release of the existing go-mode, then replace it with the tree-sitter-based one and require Emacs 29 + tree-sitter for all future versions.
The tree-sitter version, aside from being much simpler, will also fix various bugs involving indentation and navigation, especially involving generics. Syntax highlighting will likely get a fair bit more powerful, too.
I have decided against maintaining both the old and new version as separate modes. Using a proper (and fast) parser is the way forward. The current implementation of syntax highlighting, indentation and navigation is based on a hacky collection of regular expressions. The code is barely maintainable, doesn't handle several corner-cases correctly, and we haven't managed to update it to support generics reliably for years. We clearly don't have the manpower or interest to keep working on the existing code base. Instead of keeping an unmaintained copy of the old version around, make it very clear that we will only work on the tree-sitter version going forward.
This also means that the tree-sitter-based mode will not be getting its own name; it will continue to be called go-mode. There will be two tree-sitter-based modes: our go-mode, and the buggy, low-effort go-ts-mode that comes bundled with Emacs.

Hey @dominikh 👋 thank you for the amazing work.
Any news on the rewrite? I don't see any public branch on tag, are you working on that? If not, are you open to contributions?

@fedeizzo I am working on it, yes. In part I am waiting on the next release of Emacs, as the current one has some unfortunate bugs.

is there a way we can help? if you have some plan to rewrite parts and it could be done independently maybe we can help

Thank you for the offer, but no.


Segmentation Fault in jax-metal with variable indexing and partial slice in scan

Description
I'm observing a consistent segmentation fault when attempting to perform a scan on the code attached below on a jax metal device (M1 Ultra Mac Studio, Sequoia 15.0). I've attempted show the minimum criteria needed to trigger the bug.
import jax
import jax.numpy as jnp

jax.config.update('jax_platform_name', 'METAL') # fine when setting to 'cpu'

n_layer = 5
state_width = 2  # fine when setting equal to to_add
to_add = 1
x_size = 5

out_state = jax.random.uniform(jax.random.key(0), (n_layer, state_width))
print(out_state)
def do_loop(x, i):
    s1 = out_state[i, :to_add]  # fine when replacing i with constant
    to_update = jnp.concat((s1, x[:-to_add]))
    # to_update = jnp.concat((s1, jnp.zeros(x_size - to_add))) # still has same bug
    # to_update = s1 @ jnp.zeros((to_add, x_size)) # still has same bug
    return to_update, i

x = jnp.zeros(x_size)
for i in range(n_layer): # fine with python for-loop
    x, _ = do_loop(x, i)
print("correct output", x)

x = jnp.zeros(x_size)
print("   scan output", jax.lax.scan(do_loop, x, jnp.arange(n_layer))[0]) # segmentation fault

Some notes:

this bug only happens on metal; CPU is perfectly fine
this bug is only triggered when indexing using a scan input AND taking a partial slice (the bug does not occur when only one of these conditions are met)
this bug is not triggered on python for-loops (even when using jit)

System info (python version, jaxlib version, accelerator, etc.)
jax:    0.4.31
jaxlib: 0.4.31
numpy:  2.1.1
python: 3.12.6 | packaged by conda-forge | (main, Sep 22 2024, 14:07:06) [Clang 17.0.6 ]
jax.devices (1 total, 1 local): [METAL(id=0)]
process_count: 1
platform: uname_result(system='Darwin', node='Mac.attlocal.net', release='24.0.0', version='Darwin Kernel Version 24.0.0: Mon Aug 12 20:51:54 PDT 2024; root:xnu-11215.1.10~2/RELEASE_ARM64_T6000', machine='arm64')

Additionally, jax-metal is 0.1.0

i suspect this is a dupe of #21552

I closed #21552, since it works in jax-metal 0.1.1, however I can reproduce that this one still results in a segfault.


Deny nested cancellation blocks.

We don't allow to () cancellation steps.
class Action(Story):
    I.one(
        ~I.cancel_one_a,
        ~I.cancel_one_b(
            ~I.cancel_cancel_one_b
        ),
    )

This code should raise exception.

Superseded by #627


Kubean v0.2.1 is not supported installing ARM arch kubernetes?

usage issue

doubts about how to use the software
Hello ErikJiang,
I want to konw the Kubean v0.2.1 is not supported installing  kubernetes in ARM arch? The kubean version v0.2.1 Release can not supply the os-pkgs and image_pkgs of the arm. If supported ARM  only replace amd64 install package files of os-pkgs same version?

I'm curious why you chose an early version of kubean. Was there a specific reason? You should know that early versions of kubean have very limited, or even no, support for offline scenarios. If you want to deploy an ARM-based cluster, you should use a more recent higher version.

Thank you for your response. Due to project requirements, I must use K8s v1.22, and only Kubean v0.2.1 supports this. It worked when I tried it on a Debian system. However, since version 0.2.1 does not provide ARM architecture images, I had to download a separate one. Now, the issue is that I cannot combine them into a single manifests file, hence this confusion.

I roughly understand your requirements. In fact, kubean has already considered the deployment management needs of customers with low-version Kubernetes clusters, but it currently only supports the minimum version of v1.23.0, and users need to manually build the offline package through the airgap-patch image. The support for backward compatible versions can be referred to at: https://kubean-io.github.io/kubean/en/releases/artifacts/.


Tapping failed on EKS Fargate

HI,all.
I tried to use mizu on EKS Fargate.
But  streaming did not appeared all.
So , I tried to use same mizu on EKS EC2 . And it worked fine.
Is there some right way to use mizu at EKS Fargate?
If mizu does not suuport EKS Fargate , please tell me ,are there any plans to support EKS Fargate?

Hi @ryotaro-kobayashi,
As you can see in our wiki page we are adding tapper pod for each node (you can see the image at the top of the page)
In EKS Fargate - we can't start those pods (daemon set) because there are not real nodes in the cluster and it is managed in different way - so it is currently not supported.
I'm not aware of plans to support it in the near future but it might be changed if more users asked for it.

Hi @gadotroee ,
Thank you for your reply.

so it is currently not supported.

Thank you ,I see .
I felt mizu is very simple, beautiful and powerful tool .
I hope mizu support EKS Fargate in the future.


Using join on same table CANNOT get right result

Hi, all, thanks for maintaining this wonderful library!
I were trying to use join on one table to get results at one requests, here is my code:
export interface CategoryTable {
  id: number;
  name: string;
  slug: string;
  parent: number;
  description: string;
  image: string;
  isHomepage: boolean;
}

await db.selectFrom('category')
    .leftJoin('category as parent', 'parent.id', 'category.parent')
    .selectAll()
    .where('category.id', '=', id)
    .executeTakeFirst();

but I can only get the parent record, without the record pointe by id.
I have read documents, I think I did write the right code.
And I tried the example on: https://kysely.dev/docs/examples/JOIN/simple-inner-join ,
copied the generated SQL into my DB client, it works well.
So I have to ask you here to help me on this. Thanks all. Wish you a good day!

Are you expecting the parent to be provided as a nested object under a parent property? Kysely doesn't do that since that's not what the db returns. Kysely is just a query builder and it returns what the DB returns.
If you want nested objects, see this recipe

@koskimas thanks for replying.
Actually I didn't expect the parent to be returned as a nested object, here is what I got:
{
    "id": 1,
    "name": "Special",
    "slug": "special",
    "parent": "0",
    "image": null,
    "createdAt": "2023-07-16T14:19:54.098Z",
    "updatedAt": "2023-07-16T14:19:54.098Z",
    "deletedAt": null,
    "description": "",
    "isHomepage": false
}

And what I expect to get is like DB returns:

so I think in JSON object, it would be like:
{
  "category.id": 3,
  "category.parent": 1
  ....
  "parent.id": 1
  ....
}

The column names you see in that tool are the combination of table and column name. That's not what the db returns. Kysely doesn't touch the result at all. It simply returns what the db returns.


Update alpha with master

Description
Update alpha with the latest changes in master
Breaking Changes
None
JIRA Link

Checklist

[ ] Updated the Readme.md (if required) ?

gonna reopen with latest alpha commits


font: update macOS core-text dependency to 6.1.0, fixes #685

Ping, any interest in this PR?
It is necessary to compile alacritty on macOS

Yep, definitely interested. Thanks for the PR; big time saver :)


Create and Edit Category Bug Fix

A blog administrator can now view, create, and edit a category.   The bug was preventing a user to successfully access admin categories and to edit and create them.  An ID was not being assigned to the category, preventing the new, create, and edit methods in the admin categories controller to run.  RSPEC and Cucumber tests passing, some pending.
Challenges:  Initially I overlooked that there were separate admin and user sections of the site.  I kept getting errors for a missing template when I was editing methods in the admin categories controller, so I started  to create new views outside of admin.  After closely examining the tests, I realized my mistake and the bugs became easier to fix.

You should not have the db/db_development and db/db_test files in your commits, please delete and add to your gitignore


mxnet mobilefacenet to IR error

Platform (mac):
Python version:
python3
Running scripts:
python -m mmdnn.conversion._script.convertToIR -f mxnet -n model-symbol.json -w model-0104.params -d anti_spoof --inputShape 3 112 112
error log：
[21:03:01] src/nnvm/legacy_json_util.cc:209: Loading symbol saved by previous version v1.2.0. Attempting to upgrade...
[21:03:01] src/nnvm/legacy_json_util.cc:217: Symbol successfully upgraded!
Warning: MXNet Parser has not supported operator null with name data.
Warning: convert the null operator with name [data] into input layer.
Warning: MXNet Parser has not supported operator L2Normalization with name l2normalization0.
Traceback (most recent call last):
File "/usr/local/Cellar/python/3.7.0/Frameworks/Python.framework/Versions/3.7/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/usr/local/Cellar/python/3.7.0/Frameworks/Python.framework/Versions/3.7/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/usr/local/lib/python3.7/site-packages/mmdnn/conversion/_script/convertToIR.py", line 197, in
_main()
File "/usr/local/lib/python3.7/site-packages/mmdnn/conversion/_script/convertToIR.py", line 192, in _main
ret = _convert(args)
File "/usr/local/lib/python3.7/site-packages/mmdnn/conversion/_script/convertToIR.py", line 115, in _convert
parser.run(args.dstPath)
File "/usr/local/lib/python3.7/site-packages/mmdnn/conversion/common/DataStructure/parser.py", line 22, in run
self.gen_IR()
File "/usr/local/lib/python3.7/site-packages/mmdnn/conversion/mxnet/mxnet_parser.py", line 265, in gen_IR
self.rename_UNKNOWN(current_node)
File "/usr/local/lib/python3.7/site-packages/mmdnn/conversion/mxnet/mxnet_parser.py", line 376, in rename_UNKNOWN
raise NotImplementedError()
NotImplementedError

@namizzz

Hi, @ronyuzhang , MMdnn focus on the network architecture part , so it doesn't support the operators like L2Normalization. Thanks!

Hi @ronyuzhang , MMdnn focus on the network architecture part, so we don't implement the L2Normalization operator. Thanks!


When the dataset is to big it eats a lot of memory and crashes

I imagine there is no simple workaround for this issue, since the calculation matrix gets huge, but can some some sort of calculation steps be made?
Like, take the first 10 calculate for them, loop for the rest and then, do the final calculation with the resulting dataset?

This algorithm is not meant for large datasets, since small to medium datasets can provide you with good enough predictions, I would say to solve you issue you need to segment your users into groups and perform predictions with only a subset of users ratings or calculate the model and save it somewhere.

I did a partial solution partitioning the dataset and making smaller datasets, and get all the predictions (using an empty item to check), but over time it gets eventually way big too.
Thank you for your time and contribution, very useful.


Add JMESPropertyWrapper protocol

To aid Mirror parsing of property wrappers

Codecov Report

Merging #3 (9afac9e) into main (9095158) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main       #3      +/-   ##
==========================================
+ Coverage   94.43%   94.44%   +0.01%
==========================================
  Files          10       10
  Lines        1186     1189       +3
==========================================
+ Hits         1120     1123       +3
  Misses         66       66

Impacted Files
Coverage Δ

Sources/JMESPath/Expression.swift
68.18% <ø> (ø)

Sources/JMESPath/Lexer.swift
98.77% <ø> (ø)

Sources/JMESPath/Parser.swift
99.24% <ø> (ø)

Sources/JMESPath/Token.swift
100.00% <ø> (ø)

Sources/JMESPath/Variable.swift
93.51% <100.00%> (+0.09%)
:arrow_up:

Continue to review full report at Codecov.

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


type hint error from mypy

mypy doesn't seem to like the type hint Optional[Union[int, float, Literal[inf, - inf, 'fro', 'nuc']]] for matrix_norm, giving
error: Parameter 1 of Literal[...] is invalid

Yes, mypy doesn't like floating point literals in Literal. So this is a question of whether we should aim for correctness in the type hints or aim to please mypy.

Okay. Also is float necessary? The accepted values seem to be ints, except for inf but this is in the Literal.

Okay. Also is float necessary? The accepted values seem to be ints, except for inf but this is in the Literal.

Assumedly the spec here means to say you can use float-integers (e.g. 1., 2., -1., ...), which indeed is what implementations seem to support.


Fix parsing failures for diagnostics

For whatever reason, the outputs neotest gives us are in DOS format (\r\n line endings). This is why failures don't show up in diagnostics even though we set errors in the results and tests are passing.
Luckily, it seems we don't need the newlines in failure_pattern.
Added a test with a file in DOS format to cover this going forward.
Before

After

Nice one 🚀


What is meant by build tags in Release Pipeline triggers?

The article isn't clear as to what build tags refers to in the screenshots when discussing PR triggers or artifact filters on a stage trigger.
Is this a Git tag or something else?

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

ID: 70217fc0-8411-04b1-d448-d013398c5ac8
Version Independent ID: ed92b98e-2d6f-8dfb-9319-85c825b2cb30
Content: Classic release triggers for stages, branches, and pipelines - Azure Pipelines
Content Source: docs/pipelines/release/triggers.md
Product: devops
Technology: devops-cicd-release
GitHub Login: @RoopeshNair
Microsoft Alias: ronai

Think I've worked this out by trial and error. It's tags that are applied to the build pipeline run.
Would it be worth updating the doc to let other folks understand what is meant by build tags specifically? It isn't clear even when going through the UI for a run that you can even apply tags.

With regards to the build branch, is it possible to set this value to a Git tag?

@jamesmcroft -- James, thank you for your question and research.  Please consider these resources:

Azure DevOps Services
Azure DevOps on Stack Overflow

@RoopeshNair -- Roopesh, please look into this issue.

@jamesmcroft Thank you for your feedback! I'm updating the article shortly


⚠ Bofrost.es has degraded performance

In adcd795, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1602 ms

Resolved: Bofrost.es performance has improved in 511211f after 8 minutes.


Fix: lack of Legacy register amino codec for UpdateMigrationRecordsProposal and ReplaceMigrationRecordsProposal

Closes: #XXX
What is the purpose of the change
Add Legacy register amino codec for UpdateMigrationRecordsProposal and ReplaceMigrationRecordsProposal so we can continue to solve #4496
Brief Changelog
Testing and Verifying
This change is a trivial rework / code cleanup without any test coverage.
Documentation and Release Note

Does this pull request introduce a new feature or user-facing behavior changes? (no)
Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md? (no)
How is the feature or change documented? (not documented)

@ThanhNhann nice work. For the future, this is state-breaking as codec changes essentially register new messages


Avido/shipping options

Description
Added delivery options:

age_check
insurance

Added delivery Types

morning
evening
express

Motivation and context

Age_check & insurance weren't available.
Delivery Types were missing mandatory delivery_date
Added easier access to deliveryTypes such as morning/evening

How has this been tested?
See unit tests
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (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 change)

*This change shouldn't be breaking however by adding the Nesbot\Carbon package unexpected results could occure.
Checklist:
Go over all the following points, and put an x in all the boxes that apply.
Please, please, please, don't send your pull request until all of the boxes are ticked.

[x] I have read the CONTRIBUTING document.
[ ] My pull request addresses exactly one patch/feature.
[x] I have created a branch for this patch/feature.
[x] Each individual commit in the pull request is meaningful.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] If my change requires a change to the documentation, I have updated it accordingly.
[x] My code follows the code style of this project.

If you're unsure about any of these, don't hesitate to ask. We're here to help!

Thanks for your PR!
This PR addresses multiple new features at once.
Please address only one new feature per pull request.
Second, the tests added were not passing.
Closing this for now.

Hi,
The tests are not passing because of missing environment var.

Error: Class 'Carbon\Carbon' not found

Error: Class 'Carbon\Carbon' not found

Missed that one.. Is the automation running a composer update ? As the package is included in the composer file

Ah yeah, that's probably the reason.
Still I don't want to add the nesbot/carbon package as a required dependency.
I think using DateTimeInterface is a better solution here.


Update UG with recurring tasks

Codecov Report
Base: 69.03% // Head: 69.03% // No change to project coverage :thumbsup:

Coverage data is based on head (a223641) compared to base (541aeec).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #259   +/-   ##
=========================================
  Coverage     69.03%   69.03%
  Complexity      765      765
=========================================
  Files           148      148
  Lines          2655     2655
  Branches        280      280
=========================================
  Hits           1833     1833
  Misses          725      725
  Partials         97       97

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

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


🐛 [all] main branch build fails because of removed registerWith function

Bug report
#7127 removed the registerWith function from the core plugin. Other plugins are however still depending on this. These references have to be removed in order to fix the build of the main branch.
Steps to reproduce
See https://github.com/FirebaseExtended/flutterfire/runs/3816828774

Closed in #7158


Missing steps for Blazor-WASM

The section for using grpc web client as part of a Blazor-WASM app is missing steps.  There's no instruction for how/where to add the .proto file for instance.

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

ID: 1c13a1c7-4683-a9a5-9ab3-e28d4506af26
Version Independent ID: ea3b00c8-8f09-c045-4641-dc3a0030d6e5
Content: Use gRPC in browser apps
Content Source: aspnetcore/grpc/browser.md
Product: aspnet-core
Technology: aspnetcore-grpc
GitHub Login: @JamesNK
Microsoft Alias: jamesnk

@JamesNK, perhaps due to my lack of familarity with this gRPC+Blazor scenario, should I let you handle this one?

The instructions on this page are written with the assumation that you have already added the nessessary packages and proto files for basic gRPC, and they just talk about how to add gRPC-Web on top. Not every page can re-explain everything from scratch.
Add a link to https://docs.microsoft.com/en-us/aspnet/core/grpc/basics

Will do :+1:.

Hmm, there are already links in the introduction to other pages with instructions on getting started.

I won't be able to look until Friday morning, but feel free to close now if you think it's all good.

I had a minute to look this evening. I see what you mean ... and there's a Blazor sample, too.
@alexclarkmusa ... Start earlier in the gRPC coverage than this topic.
@JamesNK ... You might want to consider as a long-range idea that I work from your guidance + your sample to create a gRPC-Blazor tutorial akin to the one we did for SignalR-Blazor. Just work it up to your current sample step-by-step but also include a Blazor Server experience. It takes a little while to create one tho. I still have a lot of UE pass work to do 🏃 + 6.0 content for Blazor is just starting to land now 🏃. I have a feel'in that it would take several months to get to it unless you/DR/Artak feel that it should be higher priority than UE passes. Anyway ... just tossing that out there as an idea.

I think this is fine for now. If there is more feedback that people are stuck on this then we can reconsider.


[Bug] The chip is deleted in backspace

When the user type a bad word and wants to fix it the previous chip is deleted.
Steps to reproduce:

Add a chip
Type some word
Delete a letter with backspace

All right I merged your pull request.
Thanks !


Add Tox config and prepare for project releases.

Refs https://github.com/jazzband-roadies/help/issues/174.

Hmm, not sure what's causing Travis to stall the jobs now, will look into it.

Ah this seems to have worked now.


Choose color palette

the color palette for groups should be choosable somehow (feature for later)

This is almost a feature already. I wanted the interaction for choosing color to be as simple as possible, so I made group-colors continuously change when the node color is changed. It looks quite cool actually and making it work was a little complicated so maybe I'm too happy with it compared to the confusion it creates, but as it stands you are able to change group colors, just not exactly as you like. THAT SAID, if the group name is a string that matches a known color (like "red" or "#e74c3c") then the nodes will have that color.

ah wow, I did not know this. Can you write a short paragraph highlighting this feature in the docs?

On Apr 9, 2019, at 03:24, Ulf Aslak<EMAIL_ADDRESS>wrote:
This is almost a feature already. I wanted the interaction for choosing color to be as simple as possible, so I made group-colors continuously change when the node color is changed. It looks quite cool actually and making it work was a little complicated so maybe I'm too happy with it compared to the confusion it creates, but as it stands you are able to change group colors, just not exactly as you like. THAT SAID, if the group name is a string that matches a known color (like "red" or "#e74c3c") then the nodes will have that color.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/ulfaslak/network_styling_with_d3/issues/17#issuecomment-481174126, or mute the thread https://github.com/notifications/unsubscribe-auth/AKOzvD90N-GqIYELsbamhAlR-T46oGmTks5vfFxPgaJpZM4cStDk.

Will do


chore: improve markdownlint

Markdownlint is a crucial tool for us, but the usability was not as good as it could be.

It was confusing, as it was not accessible within the docs
The configuration deviated from the defaults, IDE-plugins did not pick up those settings
documentation of the setting was missing

With this pull-request we address the points above, and make it easier to be used for our contributors.

Please do not merge before #866 to reduce merge conflicts :)

@mowies This file has more details than what is in the CONTRIBUTING.md file and covers software facilities as well as the docs build engine.  I am thinking that eventually (not real long term) we should make this doc part of the Contributing Guide and then have the CONTRIBUTING.md files point to that guide for info


Typings not found

Could not find a declaration file for module '@kinescope/react-kinescope-player'. '/project-path/node_modules/.pnpm/@kinescope+react-kinescope-player@0.4.1_react-dom@18.2.0_react<EMAIL_ADDRESS>implicitly has an 'any' type.
  There are types at<EMAIL_ADDRESS>but this result could not be resolved when respecting package.json "exports". The '@kinescope/react-kinescope-player' library may need to update its package.json or typings.ts(7016)

typescript 5.2.2
nextjs 13.5.1
macos sonoma

Accordingly to npmfs, there are src dir in the package:
<EMAIL_ADDRESS>


clean up twisted code in RewarderSession

Biggest change is nested callbacks -> linear code using @inlineCallbacks.

This look infinitely better than before :).


Change the text of the buttons

Hi, can I change the text 'Choose image' and 'Take photo' of the InputCameraView buttons?
Thanks for listening :)

Solved!