text:
Help about the memory utilization

I test the panorama to get my UAV images stitch, but the panorama seems memory guzzler.
Bellow are the jpg files I used in the test

Using a modern memory allocator (e.g. tcmalloc) can help a lot in reducing total memory used. Default allocator is known to have issues under parallel environment.
And please note that your images are very large. And simply storing them in the original size would require: M = 4608 * 3456 * 9 * 3 * 4 (bytes) = 1.6 G memory. The peak memory could be about: 2 * M * (number of threads)
Btw, your images doesn't look panorama even to me, and they are quite feature-less. I guess it won't work well with my program.

It used 6.1G memory to process the images, but it failed to get the panorama images.

[init_config@main.cc:184] Run with camera estimation mode.
[calc_feature@stitcher.cc:73] Image 3 has 443507 features
[calc_feature@stitcher.cc:73] Image 4 has 480034 features
[calc_feature@stitcher.cc:73] Image 5 has 560969 features
[calc_feature@stitcher.cc:73] Image 2 has 427705 features
[calc_feature@stitcher.cc:73] Image 1 has 448812 features
[calc_feature@stitcher.cc:73] Image 0 has 435534 features
[calc_feature@stitcher.cc:73] Image 6 has 613574 features
[calc_feature@stitcher.cc:73] Image 7 has 607284 features
calc_feature(): 299885 milliseconds.
BuildTrees: 65681.6 milliseconds.
[pairwise_match@stitcher.cc:103] Connection between image 0 and 6, ninliers=8889, conf=2.071786
[pairwise_match@stitcher.cc:103] Connection between image 1 and 2, ninliers=63572, conf=2.665135
[pairwise_match@stitcher.cc:103] Connection between image 1 and 3, ninliers=13284, conf=1.999488
[pairwise_match@stitcher.cc:103] Connection between image 0 and 7, ninliers=31757, conf=2.736398
[pairwise_match@stitcher.cc:103] Connection between image 2 and 4, ninliers=10987, conf=2.002406
[pairwise_match@stitcher.cc:103] Connection between image 2 and 3, ninliers=65417, conf=2.675257
[pairwise_match@stitcher.cc:103] Connection between image 3 and 4, ninliers=49299, conf=2.678842
[pairwise_match@stitcher.cc:103] Connection between image 5 and 6, ninliers=90342, conf=2.829102
[pairwise_match@stitcher.cc:103] Connection between image 5 and 7, ninliers=17354, conf=2.167787
[pairwise_match@stitcher.cc:103] Connection between image 6 and 7, ninliers=87977, conf=2.867344
pairwise_match() with transform: 2.4179e+06 milliseconds.
[estimate@camera_estimator.cc:29] Cannot estimate focal. Will use a naive one.[max_spanning_tree@camera_estimator.cc:100] MST: Best edge from 6 to 7
[max_spanning_tree@camera_estimator.cc:100] MST: Best edge from 5 to 6
[max_spanning_tree@camera_estimator.cc:100] MST: Best edge from 0 to 7
error: Found a tree of size 3!=7, images are not connected well!
Aborted (core dumped)
xl@ubuntu:~/modis/panorama-master/src$

Right, because your images doesn't look like panoramas. Panoramas should be taken by a rotation-only camera.
Also, your images are feature-less, so I don't think they'll work well with any matching-based vision algorithms.
This project can also deal with translation-only camera movement. Your first 4 images look translational, and, after I manually rotate them, I can stitch them with the TRANSLATION mode (see README).

Yes, those images were obtained by UAV with a roundtrip flight, the first 4 images, the fifth image and the end 4 images represent the images took at first fly, the turning point and the second fly.
I have tried the OpenCV stitching module, but it often failed with bundle adjustment operation, but by using the ICE whcih provided by Microsoft I can get the reasonable mosaic image, as show bellow

But, ICE is not an open source software.

ICE seems like a much more general purpose image stitcher. However this project right now only focuses on rotation-only panorama: the CAMERA_ESTIMATE mode assumes fixed-center camera, and the TRANSLATION mode only try to simply stitch input one by one. Neither of them are good for stitching translation-only unordered photos for now.

Yes, Could you give me some suggestions about how to study the images stitch, such as, the prime books et al.

Start with Wikipedia items and some classical papers, about SIFT, ransac, homography estimation, and so on. Also the book "Multiple View Geometry in Computer Vision" contains most of the basic theory behind image stitching.

repo: ppwwyyxx/panorama


text:
Getting url.split is not a function at getFilenameFromURL and Request for a fresher version

Getting the error above from this code

const MultipleImages = ({multipleFiles,setMultipleFiles,name,maxNumber})=>{
  const ref = React.useRef(null);
  return (
    <div style={{width: '95%'}}>
      <FilePond
        ref={ref}
        files={multipleFiles}
        maxFiles={maxNumber}
        allowMultiple={maxNumber > 1 ? true : false}
        fileValidateTypeLabelExpectedTypes="Invalid File Type"
        imagePreviewMaxFileSize='3MB'
        imagePreviewTransparencyIndicator="gray"
        labelIdle={`Drag & drop your ${name} or <span class="filepond--label-action"> Browse </span>`}
        acceptedFileTypes={[ 'image/png','image/jpeg']}
        onupdatefiles={fileItems => {
          setMultipleFiles(fileItems.map(fileItem => fileItem.file))
        }}
      />
    </div>
  );
};

Looks like this problem has never been solved

This is related to the react implementation, will close this one and reopen the other one.

source: gharchive/issue

authors: cngeru rikschennink

repo: pqina/filepond

license: MIT

license_type: permissive

license_source: github-api


text:
"All ports busy" error when trying to connect to console of OpenBSD 6.0 installer guest

I've created a new guest for installing OpenBSD and when I launch the installer and try to connect to the console I get an "All ports busy" error msg.
Environment:
FreeNAS-9.10.2-U1
iohyve v0.7.7 2016/11/10 I Think I'll Go for a Walk Edition
Guest properties:
bargs          -A_-H_-P
boot           1
con            nmdm1
cpu            1
description    Freeswitch on OpenBSD
install        yes
loader         grub-bhyve
name           fs
os             custom
persist        1
ram            256M
size           20G
tap            tap1
template       NO
vnc            NO
vnc_h          600
vnc_ip         127.0.0.1
vnc_tablet     NO
vnc_w          800
vnc_wait       NO

Custom grub and device map files:
device.map
(hd0) /dev/zvol/bits/iohyve/fs/disk0
(cd0) /iohyve/ISO/obsd6.iso/obsd6.iso

grub.cfg
kopenbsd -h com0 (cd0)/6.0/amd64/bsd.rd
boot

I have another pre-existing linux guest that does not have this problem. My hunch is that only the nmdm0 console device is available and working.

Thank you for the detailed report!
First off, is the nmdm kernel module loaded? It should appear in kldstat.
This is also usually a sign that you have a previous session open on /dev/nmdm1A and /dev/nmdm1B. I've ran into this in the past, so I implemented iohyve conreset which is documented here. I just runs killall cu.
There is also the possibility that you have more than one grub-bhyve process open for a guest.

kldstat | grep nmdm
33    1 0xffffffff8237c000 2edb     nmdm.ko
Running iohyve conreset then destroying and re-launching the guest install resolved the issue, thanks!

license_source: bigquery


text:
Allow use on Python 3.7

I'd love to switch from sphinx_tabs to sphinx-inline-tabs but the hard requirement on Python >= 3.8 make it impossible to do so: my project works with Python >= 3.7, which is still getting security fixes until 2023-06-27.
So in the same spirit as #24, is there any possibility to have Python requirement relaxed to 3.7 as a minimum? 🙂

Why do you need to generate the docs using Python 3.7?

Why do you need to generate the docs using Python 3.7?

True. I don't need to generate the docs in Python 3.7.
But my all my Sphinx dependencies for doc building are set in my pyproject.toml, which also specify the minimal Python version to 3.7: https://github.com/kdeldycke/meta-package-manager/blob/main/pyproject.toml#L92 . Hence the conflict.
This is really practical as I can propose to the developer a way to build docs locally and test them, as straightforward as:
$ poetry install
$ poetry run sphinx-build -b html ./docs ./docs/html

Also, having all doc-related dependencies in pyproject.toml allow me to:

Let dependabot manage and notify me of new releases
Simplify my doc building workflow as I need to locally install my project for sphinx-click extension to generate the CLI documentation.

Since I created this bug, I moved to sphinx-design to render tabs, so I don't need sphinx-inline-tabs anymore. Let's close this issue to keep the backlog lean.

authors: kdeldycke pradyunsg

repo: pradyunsg/sphinx-inline-tabs


text:
Updating Readme file for banking website

Describe the Feature you want to end
documenting for banking website

Expected behavior
It helps in better contributing

Screenshots (optional)

Additional context (optional )

@MohitGupta121 Kindly,assign this to me

repo: pranjay-poddar/Dev-Geeks


text:
Egg animation added

Title and Issue number

I have added the project .Can it be merged now?
Close #5073

Checklist:

[X] I have mentioned the issue number in my Pull Request.
[] I have commented my code, particularly in hard-to-understand areas
[] I have created a helpful and easy to understand README.md

@MohitGupta121 ,@TusharKesarwani Please review my PR.

source: gharchive/pull-request


text:
Question: Make changes to Java version of adapter

We, at 33Across, would like to recommend making the following changes to our bid adapter. What is the best practice to do so? To have us make a PR or for the Prebid dev team to make them?

Add caller info, like the Go version does. This didn't get ported over?
Rename our adapter from TTX to ThirtyThreeAcross as naming is extremely important to us in terms of bidder recognition from partners.

@rpanchyk so I have already made the changes in my fork. Can I make a PR against your repo?

ah cool, sure - go ;)

thanks! I will file the PR after the holidays as we don't want to make any new releases.

authors: curlyblueeagle rpanchyk

repo: prebid/prebid-server-java


text:
update s2s config params

This PR update the s2s config for syncUrlModifier documentation and usage

released with 2.8


text:
Add demo application parallel to lib

While developing a library it is always helpful to use an application that consumes that library within the same project.
The most obvious reasons are:

Speeds up developments in a large factor
Easy debugging
Provides examples to end user
A github.io site for presentation (script to upload can be easily integrated)

Suggested Structure:
src
---lib
---demo-app

Webpack is used for development and for bundling the output for the github.io site.
Rollup is used for NPM package creation.

demo app exists here: https://github.com/preboot/angular2-library-seed/tree/master/src
But I assume you are going for a completely separated demo app which would consume the npm lib and module.

Yep, see my repo https://github.com/shlomiassaf/angular2-modal/tree/master/src , disregard naming...

@shlomiassaf a PR sometime would be appreciated; the seed setup at the moment just mirrors https://github.com/preboot/angular2-webpack right now for ease of use and updating.

authors: NathanWalker shlomiassaf

license: mit


text:
fix fonts loading and cache bust

Adding the publicPath like we have in the ng1 starter fixes the issue.
Also, I put all the fonts in the right folder with the right way to cache them.
Fixes #59
Fixes #53

:+1:

authors: Foxandxss ocombe


text:
Added precompress script

This adds the ability to inject a script before compression.
Can be used for code signing the binaries.
Test needs to be added still.

Rebase had too many conflicts so I created a new branch, see #218

repo: prebuild/prebuild


text:
Water Sensors - IYB

I've been in contact with Ashley about this field as she's been uploading the data to Google Drive.
There are a few issues with this site.

Node #18000519 is not showing any data on the downloaded data. I instructed Lindsey to check and make sure that everything was turned and connected correctly, and to do a reset of the nodes and gateway.
Node #18000277 has not made contact with the gateway at all. I instructed Lindsey to do the same as the other node (check that it's turned on, check the wiring, etc.) and reset the system.

They will be checking on this field this coming week, and I'm working with them to try and work out a time that I can remote in through Esper to see if any of these will work.

Tom Bodden, field manager with Ashley, is visiting this site on Tuesday, 08/02/22


text:
Why are not all environments created on pixi install?

Checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example
[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"

[project]
name = "dummyproj"
version = "0.1"
requires-python = "==3.11.*"

[tool.pixi.project]
channels = ["conda-forge"]
platforms = ["linux-64", "win-64"]

[tool.pixi.system-requirements]
linux = "3.10.0"

[tool.pixi.dependencies]
pip = ">=24.0,<25"
requests = ">=2.31.0,<2.32"
numpy = ">=1.26.4,<1.27"
pandas = ">=2.2.2,<2.3"
matplotlib = ">=3.8.4,<3.9"
pydantic = ">=2.7.0,<2.8"

[tool.pixi.feature.lint.dependencies]
ruff = ">=0.3.4,<0.4"

[tool.pixi.feature.lint.tasks]
lint = "ruff check ."

[tool.pixi.tasks]
plot = "python -m dummyproj.plot"
task1 = "echo hi from pyproject"

[tool.pixi.environments]
lint = {features = ["lint"], no-default-feature = true}

Issue description
In the above example, i used the new feature in the v0.21 no-default-feature and after running the following command rm -f pixi.lock && pixi install,  the lint env is not present in the .pixi/envs folder.
What am i doing wrong?
Expected behavior
both default and lint envs are present and usable.

Thanks for the info. This was not clear to me, now running pixi run lint does what you mentioned and the lint env is now there. I have a further point regarding this. When running pixi run lint for the first time i got the following error
pixi run lint
✨ Pixi task (lint-code in lint): ruff check --fix . && ruff format .
  × The current system has a mismatching virtual package. The project requires '__linux' to be at least version '5.10' but the system has version
  │ '3.10.0'

I guess the no-default-feature ignores everything from the default ? would be good if there is a fine grained filter avaialble, platforms,  system-requirements ,  etc.  so that i don't have to redefine the fields.
maybe
[no-default-feature]
include = [ "platforms", "system-requirements" ]

The current logic only takes over what is defined in the project table. Specifically channels and platforms. But your point of makes sense. Checkout https://github.com/prefix-dev/pixi/pull/1092 to see the full discussion, because there was a pretty big one including your proposal.
The system requirements could be revisited. But for now the fix would be is to redefine them. I posted a different idea for system requirements in general in this Issue.

Your proposal makes sense. I am closing this issue and will followup on the linked ones. Thanks again for the prompt and detailed response.

authors: ruben-arts vigneshmanick

repo: prefix-dev/pixi


text:
Fix wrong target/build platform during rendering

The issue only appeared during cross compilation when target was different from the build platform.
I encountered the issue when converting a feedstock to rattler at https://github.com/conda-forge/xformers-feedstock/pull/33
Sister PR: https://github.com/conda-forge/conda-forge-ci-setup-feedstock/pull/360

It fixes the error reported in https://github.com/prefix-dev/rattler-build-conda-compat/issues/58

Thank you @hadim !

authors: hadim wolfv

repo: prefix-dev/rattler-build-conda-compat


text:
Use & produce run_exports.json

rattler-build could make use of the new run_exports.json which is a new file available "next" to the repodata.json file (e.g. https://conda.anaconda.org/conda-forge/osx-arm64/run_exports.json)
Then we don't need to download the packages to extract that information.
Our own indexing process should also produce this file.
And lastly, prefix.dev does not produce this file (yet) – but that's another issue.

Do quetz and artifactory produce these files?

Quetz and prefix do not produce them yet. Would be nice to add the features, but we can always fall back.
No idea about artifactory.
It's a relatively new thing :)

authors: pavelzw wolfv

repo: prefix-dev/rattler-build


text:
Render plan structure

Make the tree structure of the plan clearer. Sample output:
                                               Query Plan
---------------------------------------------------------------------------------------------------------
 Output[_col0]
 │   Layout: [count:bigint]
 │   Estimates: {rows: ? (?), cpu: ?, memory: ?, network: ?}
 │   _col0 := count
 └─ Aggregate(FINAL)
    │   Layout: [count:bigint]
    │   Estimates: {rows: ? (?), cpu: ?, memory: ?, network: ?}
    │   count := "count"("count_9")
    └─ LocalExchange[SINGLE] ()
       │   Layout: [count_9:bigint]
       │   Estimates: {rows: ? (?), cpu: ?, memory: ?, network: ?}
       └─ RemoteExchange[GATHER]
          │   Layout: [count_9:bigint]
          │   Estimates: {rows: ? (?), cpu: ?, memory: ?, network: ?}
          └─ Aggregate(PARTIAL)
             │   Layout: [count_9:bigint]
             │   count_9 := "count"(*)
             └─ InnerJoin[("orderkey" = "orderkey_0")]
                │   Layout: []
                │   Estimates: {rows: 60175 (0B), cpu: 2.32M, memory: 528.88kB, network: 528.88kB}
                │   Distribution: PARTITIONED
                ├─ TableScan[tpch:orders:sf0.01]
                │      Layout: [orderkey:bigint]
                │      Estimates: {rows: 15000 (131.84kB), cpu: 131.84k, memory: 0B, network: 0B}
                │      orderkey := tpch:orderkey
                │      tpch:orderstatus
                │          :: [[F], [O], [P]]
                └─ LocalExchange[HASH] ("orderkey_0")
                   │   Layout: [orderkey_0:bigint]
                   │   Estimates: {rows: 60175 (528.88kB), cpu: 1.55M, memory: 0B, network: 528.88kB}
                   └─ RemoteExchange[REPARTITION]
                      │   Layout: [orderkey_0:bigint]
                      │   Estimates: {rows: 60175 (528.88kB), cpu: 1.03M, memory: 0B, network: 528.88kB}
                      └─ TableScan[tpch:lineitem:sf0.01]
                             Layout: [orderkey_0:bigint]
                             Estimates: {rows: 60175 (528.88kB), cpu: 528.88k, memory: 0B, network: 0B}
                             orderkey_0 := tpch:orderkey

@martint, does it relate to @wagnermarkd's https://github.com/prestodb/presto/pull/12101?

Inspired by that, but I had to reimplement it since his version was from before PlanPrinter was refactored.

authors: findepi martint

repo: prestosql/presto


text:
Driver not started for unibet

Quand je lance l'interface graphique j'ai une erreur qui tourne en boucle.
Driver not started for unibet
Restarting driver

Bonjour
C'est corrigé !
Merci pour votre message.

Bonjour, merci pour votre rapidité cependant j'ai la même erreur avec parionssport, betclic, unibet
J'ai augmenter le timeout à 30 et j'ai toujours l'erreur. les bookmakers concernés sont pas toujours les mêmes.

idem pour betstars (timeout 45)

idem joa (timeout 60)

timeout 120 j'ai cet erreur.

Personnellement j'aimerais utiliser uniquement winamax avec l'interface graphique.

Il est possible que le problème vienne du fait que vous utilisez une version trop ancienne de Chrome.
Mais si vous n'utilisez que Winamax alors vous pouvez simplement retirer la ligne 59 de interface_pysimplegui.py
sb.selenium_init.start_drivers()

Je suis pourtant à jour sur la version de google chrome c'est bizarre.
d'accord je vais tester en enlevant cette ligne. Merci beaucoup je reviens vers vous si ça fonctionne.

En supprimant la ligne ça fonctionne.

Je ferme l'issue. N'hésitez pas à la rouvrir si jamais vous voulez utilisez les autres bookmakers et que le problème est encore là.

repo: pretrehr/Sports-betting


text:
Implementation: configurable

base url?
api version？

for now, no need

repo: prezzemolo/pomodori


text:
Example for NextJS 14 and Tailwind with App Router

Hi, do you mind updating (or adding) the examples with nextjs+tailwind, styled and unstyled, using the new App Router in v14? I'm struggling about configuring the new layout.tsx, I managed to use Primereact OR Tailwind, but not both together.
Thank you
Regards

Issue has been asked under the Free Sakai React template as well: https://github.com/primefaces/sakai-react/issues/47
And open issue: https://github.com/primefaces/primereact/issues/5127

Has Next14 been able to integrate with Prime React and Tailiwind?

+1

i got news. nextjs 13+ with app router and tailwind could work together without the layer thing. just need to import the css theme.css below the globals.css in layout file. i figure this out after i got no styling at all even after following the tailwind instruction, turns out i got it working after switching these line.
// this is the wrong order
import "primereact/resources/themes/md-dark-indigo/theme.css";
import "./globals.css";

// this is the right order
import "./globals.css";
import "primereact/resources/themes/md-dark-indigo/theme.css";

import "primereact/resources/themes/md-dark-indigo/theme.css";

Can you share a complete configuration for this? Do we still need the PrimeReactProvider?

import "primereact/resources/themes/md-dark-indigo/theme.css";

Hey man, nice! Can you share a complete configuration for this? Do we still need the PrimeReactProvider?

basically, no. The provider only hold state for components and themes, but the css only apply the style, and if the style applied in incorrect order, the tailwind will reset the primereact style cause it is tailwind behavior to reset any styling that applies before them.

@BanDroid i would love if you wanted to submit a PR for this example here in the examples folders because this gets asked a lot?

@BanDroid i would love if you wanted to submit a PR for this example here in the examples folders because this gets asked a lot?

others need to confirm if my solution works or not, it works with mine, but if i'm not sure if this is working with someone else.

The only way I managed to work is by adding preflight as false in my tailwind.config.ts but this is a huge nuclear bomb so is not a solution but a workaround.
const config: Config = {
  corePlugins: {
    preflight: false,
  }

I have no idea but this layers in global.css are doing jack.
@layer twbase, primereact, twutilities;

@import 'primereact/resources/themes/lara-light-indigo/theme.css' layer(primereact);

@layer twbase {
 @tailwind base;
}

@layer twutilities {
 @tailwind components;
 @tailwind utilities;
}

The issue itself is with the tailwind, not primereact because if you remove the tailwind either by disabling the preflight or by removing the layers and leaving just your theme in your global.css, it suddenly works.
@BanDroid, can you share a stackblitz so we can take a look? ❤

SO... I was able to find a weird solution but I have NO IDEA why it works, I really don't understand.
The usual global.css
@layer tailwind-base, primereact, tailwind-utilities;

@import 'primereact/resources/themes/saga-blue/theme.css' layer(primereact);

@layer tailwind-base {
  @tailwind base;
}

@layer tailwind-utilities {
  @tailwind components;
  @tailwind utilities;
}

AND...
Bro, I don't understand why.
Just add a second import with the actual theme you want to use in your layout.tsx
import "./globals.css";
import 'primereact/resources/themes/saga-blue/theme.css';

You can go either way with provider or not.
<PrimeReactProvider>
    {children}
</PrimeReactProvider>

Is this what you meant @BanDroid? We basically have to add the theme twice, one "dummy" and another one you actually want to use.

Bro, I don't understand why.
Just add a second import with the actual theme you want to use in your layout.tsx
import "./globals.css";
import 'primereact/resources/themes/saga-blue/theme.css';

You can go either way with provider or not.
<PrimeReactProvider>
    {children}
</PrimeReactProvider>

Is this what you meant @BanDroid? We basically have to add the theme twice, one "dummy" and another one you actually want to use.

yes, this is what i mean, you dont exactly need to import primereact in globals.css, cause primereact classes and tailwind classes have different prefixes, it will be different case if you also use primefaces (seriously, why? 2 utility library?)

Thanks to @BanDroid and @meowzhin a new sample has been added: https://github.com/primefaces/primereact-examples/tree/main/nextjs-app-router-styled-tailwind

Trying to use the unstyled version like this:
<PrimeReactProvider
    value={{
        unstyled: true,
        pt: Tailwind,
        ptOptions: { mergeSections: true, mergeProps: true, classNameMergeFunction: twMerge },
}}>
    {children}
</PrimeReactProvider>

Causes an error when trying to pass twMerge into classNameMergeFunction:
[ Server ] Error: Functions cannot be passed directly to Client Components unless you explicitly expose it by marking it with "use server". Or maybe you meant to call this function rather than return it.
  {mergeSections: true, mergeProps: true, classNameMergeFunction: function callTailwindMerge}
                                                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^

Trying to use the unstyled version like this:
<PrimeReactProvider
    value={{
        unstyled: true,
        pt: Tailwind,
        ptOptions: { mergeSections: true, mergeProps: true, classNameMergeFunction: twMerge },
    }}>
    {children}
</PrimeReactProvider>

Causes an error when trying to pass twMerge into classNameMergeFunction:
[ Server ] Error: Functions cannot be passed directly to Client Components unless you explicitly expose it by marking it with "use server". Or maybe you meant to call this function rather than return it.
  {mergeSections: true, mergeProps: true, classNameMergeFunction: function callTailwindMerge}
                                                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^

the file where you create the twMerge function, add the "use client" directives, because your provider is client-component, but this twMerge function is in server, i'm not sure how you import the twMerge

authors: BanDroid VytautasLozickas gygabyte017 melloware meowzhin nicolasGallegos robsoncombr

repo: primefaces/primereact-examples


text:
feat: Logging interface for SDK

What this PR does

Introduce a logging interface that can be implemented by merchants
Implements it within the debug app

QA

[x] I manually tested this with a demo application (simulator)
[x] I manually tested this with a demo application (real device)
[ ] I wrote unit tests for each new util-like function
[ ] I wrote at least basic e2e tests for the new functionalities or new paths

Documentation

[ ] If this PR modifies the API, I updated the API Reference.
[ ] If this PR adds new options to the API, I wrote some documentation or guide in the online documentation

After merging

Make sure a new release has been pushed to Cocoapods trunk

General question, if developer only use headless integration, is it enough to set Logger only on Primer object?

Yes, the logger works independently of checkout type. This is why the logger property is on the SDK singleton (Primer.shared.logger)

repo: primer-io/primer-sdk-ios


text:
Component status page

Summary
Counterpart to https://github.com/primer/react/pull/1656, part of https://github.com/github/primer/issues/114

Component descriptions are generated from first line of docs pages via gatsby's excerpt for the mdx node

Preview

Currently any mdx node with a status value in the frontmatter is pulled into the table, but this doesn't line up with the sidebar navigation which is pulled in from a yml file. This confused me initially because this file wasn't mentioned in the contrib doc, and it seems quite easy to get out of sync; I wonder whether we could have that auto-generated as part of the docs build?
It seems like there a quite a few internal components (e.g. BorderBoxHeader used in BorderBox, BaseButton used in button components) that aren't in the sidebar and aren't linked to from other docs page - do they need a status or is it logical that whatever the 'parent' component is would reflect the status of the child? Is there a better way to call out these internal components? (preferably in a way that could exclude them from this table 🙃)

N.B. failing lint is from main, I've fixed it in another PR https://github.com/primer/view_components/pull/917/commits/2fa2529ce402cbcee7418ca3b6d3761700bb72d5

I think that using a query like that is more complicated than it needs to be 🤔
We currently export static files with all the info we need https://github.com/primer/view_components/blob/main/static/statuses.json
Is it possible to read the data from that file in your React component? If not maybe we could add a new step to docs.rake, which can generate the necessary MDX based on the content of the file

Is it possible to read the data from that file in your React component? If not maybe we could add a new step to docs.rake, which can generate the necessary MDX based on the content of the file

I would vote for that approach ☝🏻

I think that using a query like that is more complicated than it needs to be 🤔
We currently export static files with all the info we need https://github.com/primer/view_components/blob/main/static/statuses.json
Is it possible to read the data from that file in your React component? If not maybe we could add a new step to docs.rake, which can generate the necessary MDX based on the content of the file

I think trying to use statuses.json here would be more complicated to implement (open to being proven wrong though). Using Gatsby's GraphQL API makes it easier to get page links and component descriptions in addition to component statuses.
The statuses.json file and the status frontmatter variable get generated from the same data, right? So there shouldn't be any risk of the two being out of sync.

I think the graphql method is the best:

Getting simplified names and slugs from the data in statuses.json would be messy and we already have that info in graphql.
Adding a step to docs.rake to generate the table would also be scrappy because we'd have to use HTML syntax rather than markdown (bc we'd need to use Gatsby's Link component so that it respects publicPath), and it also adds another auto-generated committed file that could be accidentally edited.

authors: colebemis joelhawksley manuelpuyol pouretrebelle


text:
Measurement 4: old download link for the cifar_resnet110.th?

Hello,
I think the download bash script should be updated.
Using the current script caused the error: _pickle.UnpicklingError: invalid load key, '<'.
By manually downloading from this link rather than the one from download.sh I resolved the error.
Just as a tip for future users. :)
Thank you very much for providing this tool.
Best regards,
Nastassia

Hmm I didn't run into this when I downloaded, but it may just be a difference in python versions, thanks for noting!

Hmm I didn't run into this when I downloaded, but it may just be a difference in python versions, thanks for noting!

authors: Angelina-Wang aitrain

repo: princetonvisualai/revise-tool


text:
Update 100-soft-delete-middleware.mdx

Describe this PR
Soft deletes aren't handled by prisma natively. This article talks about a workaround using middlewares.
There are two clear drawbacks of this approach that should be better documented in the "cons" list:

Can't handle complex queries with AND, every, etc (@chrissisura's [comment]
Can't handle include

Examples where soft deleted rooms would be returned in queries:
const rooms = await prisma.room.findMany({
    where: {
        AND: [
            {
                something: true
            },
        ],
    },
})

const building = await prisma.building.findUnique({
    where: {
        id: 1
    },
    include: {
        rooms: true
    }
})

Changes
Added two drawbacks in the const list
What issue does this fix?
Doesn't fix an issue, but it is discussed in #3398

Thanks so much @larskarbo for adding these important factors. Your help is much appreciated!

How can we get this merged? I see the "Comment with Netlify Deploy URLs of changed pages / Create or Update (pull_request)" check is failing, but not sure how it works.. @tanberry

authors: larskarbo tanberry

repo: prisma/docs


text:
graphqlbin share function does not function

Attempting to use https://www.graphqlbin.com/v2/new share function produces an error:
{
  "data": {
    "addSession": null
  },
  "errors": [
    {
      "code": 5008,
      "locations": [
        {
          "column": 11,
          "line": 3
        }
      ],
      "message": "software.amazon.awssdk.services.lambda.model.ResourceNotFoundException: Function not found: arn:aws:lambda:eu-west-1:484631947980:function:cj81hi46q03c30196uxaswrz2-add-session (Service: null; Status Code: 404; Error Code: ResourceNotFoundException; Request ID: 66711723-89ea-11e8-a743-ab4f35b737a4)",
      "path": [
        "addSession"
      ],
      "requestId": "eu-west-1:simple:cjjpzysua1kz9013124ybf6lu"
    }
  ]
}

ping @timsuchanek

Same issue 🤔

Same issue for us, the legacy URL with any endpoint (https://legacy.graphqlbin.com/... 6chars) is redirecting us to https://legacy.graphqlbin.com/new requiring an end point.

Also seeing this issue.  It also appears that the Share button fails with an error in the console:
Cannot read property 'id' of null

I am also seeing the issue for Apollo Server 2 projects on Glitch like https://apollo-launchpad.glitch.me/

Just tested this on a local project using the HAPI middleware, and it is failing there as well.

Another version of the console error (for people Googling):
TypeError: "n.data.addSession is null"

Looks like it's coming from here: https://github.com/prisma/graphql-playground/blob/524155be1d944c6c564fff9cbdfcfd7980cf9ece/packages/graphql-playground-react/src/state/sharing/sharingSaga.ts#L34

Looks like a missing lambda:{   "data": {     "addSession": null   },   "errors": [     {       "locations": [         {           "line": 3,           "column": 11         }       ],       "path": [         "addSession"       ],       "code": 5008,       "message": "software.amazon.awssdk.services.lambda.model.ResourceNotFoundException: Function not found: arn:aws:lambda:eu-west-1:484631947980:function:cj81hi46q03c30196uxaswrz2-add-session (Service: null; Status Code: 404; Error Code: ResourceNotFoundException; Request ID: 7e97f93b-c68c-11e8-b263-13c33c672168)",       "requestId": "eu-west-1:simple:cjms952td19st0108a7jc99qg"     }   ] }

Looks like this would resolve it: #847

But maybe not. When I go to the playground for the share-server and copy in the query, I get a Bad Gateway error.

Graphqlbin now works properly, sorry for troubles. Enjoy using it now

@Huvik Can you elaborate on what the fix was?  Because I am still seeing this being broken on other systems using GraphQL Playground.  Like https://apollo-launchpad.glitch.me/

https://api.graphqlbin.com/ is also still broken

Looks like the fix is in https://github.com/prisma/graphql-playground/pull/847/files

Other systems (like https://apollo-launchpad.glitch.me/ and https://api.graphqlbin.com/) embedding the Playground are probably using jsDelivr like inlcuding:
<script src="//cdn.jsdelivr.net/npm/graphql-playground-react/build/static/js/middleware.js"></script>

But jsDelivr does not contain v1.8.0, only up to v1.7.8, see https://www.jsdelivr.com/package/npm/graphql-playground-react
This is similar issue as https://github.com/prisma/graphql-playground/issues/865

1.7.8 its correct version of react playground. Electron version is 1.8.0 and has react playground version 1.7.8 inside :)

OK than I'm really interested to see why #865 is happening, as I can't understand.

I will look into it next week :)

authors: GeorgioWan Huvik gajus jjdiezm konsumer marceloverdijk mkochendorfer wKovacs64

repo: prisma/graphql-playground


text:
Missing documentation property in DMMF.Field and DMMF.Model

My datamodel:
/// User model comment
model User {
  /// User model field comment
  id       String  @default(cuid()) @id @unique
}

When I log the dmmf datamodel, I have a documentation property:

But it is missing in typedefs:

This is fixed in the latest alpha.

authors: MichalLytek timsuchanek

repo: prisma/photonjs


text:
Connection to Postgres database with pgbouncer is significant slower on Digital Ocean

Bug description
Hello,
we would like to use a connection pool to our Postgres database at Digital Ocean. For this we have entered pgbouncer=true in the connection string.
This causes significantly slower queries, so we can't use the feature. Without pgbouncer our queries take about 20-25ms, with pgbouncer sometimes from 229-400ms.
We're hosting our app at heroku and the database at digital ocean.
This is a log from a query with pgbouncer activated (please have a look at duration)
Query:  {   timestamp: 2022-10-31T22:28:38.431Z,   query: 'SELECT "public"."User"."id", "public"."User"."email", "public"."User"."title", "public"."User"."firstName", "public"."User"."lastName", "public"."User"."gender", "public"."User"."role", "public"."User"."phoneNumber", "public"."User"."password", "public"."User"."isEmailAddressConfirmed", "public"."User"."fullyRegistered" FROM "public"."User" WHERE "public"."User"."id" IN ($1) OFFSET $2',   params: '["619d3b22b24ae50018cf3719",0]',   duration: 229,   target: 'quaint::connector::metrics' }
this is a similar query without pgbouncer
Query:  {   timestamp: 2022-10-31T22:43:24.222Z,   query: 'SELECT "public"."User"."id", "public"."User"."email", "public"."User"."title", "public"."User"."firstName", "public"."User"."lastName", "public"."User"."gender", "public"."User"."role", "public"."User"."phoneNumber", "public"."User"."password", "public"."User"."isEmailAddressConfirmed", "public"."User"."fullyRegistered" FROM "public"."User" WHERE "public"."User"."id" IN ($1) OFFSET $2',   params: '["619d3b22b24ae50018cf3719",0]',   duration: 22,   target: 'quaint::connector::metrics' }
The reason why we just don’t use the pgbouncer is that this would lead to this error, which is mentioned here: https://github.com/prisma/prisma/discussions/14958
How to reproduce

Expected behavior
The queries should be as fast as without pgbouner
Environment & setup

OS: macOS
Database: PostgreSQL
Node.js version: v17.2.0

Prisma Version
prisma                  : 3.15.2
@prisma/client          : 3.15.2
Current platform        : darwin-arm64
Query Engine (Node-API) : libquery-engine 461d6a05159055555eb7dfb337c9fb271cbd4d7e (at node_modules/@prisma/engines/libquery_engine-darwin-arm64.dylib.node)
Migration Engine        : migration-engine-cli 461d6a05159055555eb7dfb337c9fb271cbd4d7e (at node_modules/@prisma/engines/migration-engine-darwin-arm64)
Introspection Engine    : introspection-core 461d6a05159055555eb7dfb337c9fb271cbd4d7e (at node_modules/@prisma/engines/introspection-engine-darwin-arm64)
Format Binary           : prisma-fmt 461d6a05159055555eb7dfb337c9fb271cbd4d7e (at node_modules/@prisma/engines/prisma-fmt-darwin-arm64)
Default Engines Hash    : 461d6a05159055555eb7dfb337c9fb271cbd4d7e
Studio                  : 0.462.0

@DanielJanke could you please try more recent Prisma version?

@SevInf I can confirm that the issue still occurs at Prisma and Prisma client version 4.5.0.

Interested to know more about this issue as well as we are running with the same setup at the moment and are facing some latency issues with pgbouncer in DO.

What does "without pgbounce" really mean? Are you disabling PgBouncer on the DigitalOcean side, or are you just dropping the &pgbouncer=true configuration from the connection string?

I had a similar issue and asked questions about it here: https://github.com/prisma/prisma/discussions/17919#discussioncomment-4982734
I also run some tests to compare performances with various providers and regions: https://docs.google.com/spreadsheets/d/1mAy9BEEKkqEKGgcT87ZHhbb6Sroxy2z-srlUmXy_q6o/edit?usp=sharing

Has there been any development on this? I am running into the same issue with pgbouncer and supabase. When using the Data Proxy service offered by Prisma the query speed is comparable to a direct connection.

Same issue here, but it becomes much more evident when using createMany.
For the given (simplified) schema, it takes about 17 minutes (!) to save 8000 records, whereas it takes 2 seconds without using pgBouncer.
In both cases, I'm running this locally and connecting to a Postgres database in DigitalOcean.
Any updates on this?
Simplified schema
model BulkEmailMessage {
  id                      String      @db.Uuid @id
  to                      Subscriber  @relation(fields: [toId], references: [id])
  toId                    String      @db.VarChar(24)

  // One-to-many
  bulkEmail              BulkEmail   @relation(fields: [bulkEmailId], references: [id])
  bulkEmailId            String      @db.VarChar(24)
  events                  Json        @db.JsonB

  created                 DateTime    @default(now())
  updated                 DateTime    @updatedAt
}

model BulkEmail {
  id                      String      @db.VarChar(24) @id
  name                    String      @unique

  emails                  BulkEmailMessage[]
  subject                 String
  from                    String
  html                    String

  // One-to-many
  emailList               EmailList   @relation(fields: [emailListId], references: [id])
  emailListId             String      @db.VarChar(24)

  created                 DateTime    @default(now())
  updated                 DateTime    @updatedAt

  @@unique([id, name])
}

Write 8000 records
    const bulkEmailMessageData = Array(8000)
      .fill(0)
      .map(() => ({
        id: randomUUID(),
        toId: 'c31prgr345tsq7po126z7rgx',
        bulkEmailId: 'uzg1rc7itt91yv7gw5saahx6',
        events: []
      }))

    console.log('d', bulkEmailMessageData)

    const savedBulkEmailMessage = await prisma.bulkEmailMessage.createMany({
      data: bulkEmailMessageData
    })

We too are experiencing massive overhead when using Prisma in PGBouncer mode. In my scenario we have our node application running in GKE, the path our application takes to communicate with its database is the following:
Application -> PG Bouncer -> Cloud SQL Proxy -> Managed Postgres Instance.
I have ran different testing scenarios to rule the different moving parts out that might be the cause and will try to explain them. Hopefully this will give enough information to solve the slowness.
Versions of the moving pieces:
prisma                  : 4.12.0
@prisma/client          : 4.12.0
Current platform        : darwin
Query Engine (Node-API) : libquery-engine 659ef412370fa3b41cd7bf6e94587c1dfb7f67e7 (at node_modules/prisma/node_modules/@prisma/engines/libquery_engine-darwin.dylib.node)
Migration Engine        : migration-engine-cli 659ef412370fa3b41cd7bf6e94587c1dfb7f67e7 (at node_modules/prisma/node_modules/@prisma/engines/migration-engine-darwin)
Format Wasm             : @prisma/prisma-fmt-wasm 4.12.0-67.659ef412370fa3b41cd7bf6e94587c1dfb7f67e7
Default Engines Hash    : 659ef412370fa3b41cd7bf6e94587c1dfb7f67e7
Studio                  : 0.483.0
Preview Features        : tracing

Postges: 14.5
PG Bouncer: 1.18.0
Prisma Schema
generator client {
  provider        = "prisma-client-js"
  output          = "../src/persistence/generated/client"
  binaryTargets   = ["native", "debian-openssl-1.1.x"]
  previewFeatures = ["tracing"]
}

generator dbml {
  provider = "prisma-dbml-generator"
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model Inventory {
  id           String           @id
  slug         String
  gtin         String
  location     String
  qoh          Int
  type         InventoryType
  createdDate  DateTime      @default(now()) @map("created_date")
  modifiedDate DateTime      @updatedAt @map("modified_date")

  @@unique([slug, gtin, location, type])
  @@index([slug])
  @@index([gtin])
  @@index([type])
  @@index([location])
  @@map("inventory")
}

enum InventoryType {
  brand
  retailer
}

DAO
Below is the bit of code that handles the saving of data to Postgres
    async saveNewInventory(newInventory: Prisma.InventoryCreateManyInput[], jobId?: string) {
        try {
            await prisma.$transaction(
                async (prisma) => {
                    logger.info({ jobId }, 'about to delete inventory ...');
                    await prisma.inventory.deleteMany({ where: { slug: newInventory[0].slug } });

                    logger.info({ jobId }, 'recreating it ...');
                    await prisma.inventory.createMany({ data: newInventory });
                },
                {
                    maxWait: 120000,
                    timeout: 120000,
                },
            );
        } catch (error) {
            logger.error({ jobId, error }, 'Error: inventory rolled back');
            throw new InternalServerError('Error saving new inventory');
        }
    }

Inserting 400K items with pgbouncer=true in the connection string and talking directly to postgres takes 58 minutes.
Inserting 400K items with pgbouncer=true going through pgbouncer to write to postgres takes 54 minutes.
Inserting 400K items with pgbouncer=true removed and talking directly to postgres takes 90 seconds.
From my understanding enabling pgbouncer=true wraps all calls into a transaction along with issuing DEALLOCATE ALL, but it comes with severe overhead issues.
Our infrastructure has OpenTelemetry enabled, looking at the first test above the slowness seems to be in the insert statement.

As you can see most of the time is spent in prisma:engine:itx_query_builder, by turning off pgbouncer in the connection string the same 400K items take less than 120 seconds. I would love to get some insights into what might be causing this, I don't know if by turning on pgbouncer and starting prisma.$transaction, everything is being double wrapped in a transaction call, or if that is even possible in postgres.

@dkamenov-fitted is your pgbouncer configured in transaction mode?
I'm not mistaken when this lands https://github.com/pgbouncer/pgbouncer/pull/845 we might be able to drop the pgbouncer=true and work normally

@dkamenov-fitted is your pgbouncer configured in transaction mode?
if I'm not mistaken when this lands pgbouncer/pgbouncer#845 we might be able to drop the pgbouncer=true and work normally

Yes, pgbouncer is configured to be in transaction mode as per this link
However I don't think this is a PGBouncer issue, one of the above tests was enabling pgbouncer in the connection string and making a request directly to the database without going through pg bouncer, this saw significant increase in how long the underlying query with 400K records took.

The cause here definitely is pgbouncer=true on Prisma's side, which adds complexity to the queries we need to run to overcome the limitation that PgBouncer can not handle prepared statements naively, which Prisma always uses to execute queries. So @masterkain's PR link indeed would make it much easier for Prisma to work with PgBouncer. But we will also try to overcome this limitation in other ways as we acknowledge that the performance impact is a desaster.

I can confirm this issue with pgbouncer. In a small project I developed a Next.js application, which runs serverless on Vercel and should run against a Supabase postgres database. The prisma overhead is clearly noticeable.

I can confirm this issue with pgbouncer. In a small project I developed a Next.js application, which runs serverless on Vercel and should run against a Supabase postgres database. The prisma overhead is clearly noticeable. My serverless function runs easily into timeouts. This is a reason for me to look for other solutions.

The cause here definitely is pgbouncer=true on Prisma's side, which adds complexity to the queries we need to run to overcome the limitation that PgBouncer can not handle prepared statements naively, which Prisma always uses to execute queries. So @masterkain's PR link indeed would make it much easier for Prisma to work with PgBouncer. But we will also try to overcome this limitation in other ways as we acknowledge that the performance impact is really bad.

Can you comment on what priority this issues is for the team?
FYI the linked PR was merged in yesterday.

We expect the problem to go away when support for prepared statements in PgBouncer is actually released and rolled out.
Until then, we are doing what we can - release 5.4.0 for example removed certain queries triggered by enums that were contributing to this. They are not done anymore, which - if you are using many enums - might lead to clear improvements here. The fundamental problem still exists though unfortunately.

It says it has been merged: https://github.com/pgbouncer/pgbouncer/pull/845

@amit1911 once pgbouncer makes a release with support for prepared statements (hopefully soon) prisma should work perfectly fine with pgbouncer

@amit1911 once pgbouncer makes a release with support for prepared statements (hopefully soon) prisma should work perfectly fine with pgbouncer

It was released yesterday I assume.

We don't know yet. Someone should open an issue for figuring that out and share information if they tried it out.

For all who have the same problem I would like to give the tip that Supabase, to solve some problems, has developed and published "Supavisor".
See https://supabase.com/blog/supavisor-1-million
See https://github.com/supabase/supavisor
Possibly this will help in conjunction with prisma. I have not been able to test this yet.

+1, running on version 5.19.0 i guess we'll just remove pgbouncer for now

Whats the state on this? When removing pgbouncer=true like @Moe03  suggested I am getting this error:
Error querying the database: FATAL: unsupported startup parameter: search_path

authors: DanielJanke LarsOlt Moe03 MorenoMdz SevInf cvolzer3 dkamenov-fitted jamiearonson janpio klanthier magoz masterkain pschaub sammyolo tekoh testerez wanschi

repo: prisma/prisma


text:
Update using Partial<Model> not working on 4.16.1

Bug description
So doing something like updating a object, we were doing update with Partial
On 4.15.0 this was working. On 4.16.1 this isn't working anymore. The error appear on data which doesn't correspond to what is expected in the update function.
How to reproduce
Post model has 4 n-1 relation like those below. We are using MongoDB, we have nested object and enum. Both have a optional and an required member
Expected behavior
Partial be enough for updating a Post object in the DB.
Prisma information

model User {
  id           String                  @id @default(auto()) @map("_id") @db.ObjectId
  post   Post @relation(fields: [postId], references: [id])
  postId String   @db.ObjectId
}

model Post {
  id           String                  @id @default(auto()) @map("_id") @db.ObjectId
  type1 Type1    // Nested Type
  type2 Type2? // Nested Type optional
  enum1 Enum1?
  enum2 Enum2 @default(Default)

  users User[]
  ...
}

import { Post } from "@prisma/client";
async updatePost(id:string, data: Partial<Post>)
const post = await prisma.post.update({
  where: {id},
  data
})

Environment & setup

OS: macOS
Database: MongoDB
Node.js version: 18.16.0

Prisma Version
4.16.1
Now reverted to 4.15.0 because the issues doesn't happen.

@maxime4000 this might be fixed already in 4.16.2, could you try it out and let us know?

Having the same problem with a field that's nullable JSON in the schema ... metadata Json?
Errors when using Partial<User> with Type 'JsonValue | undefined' is not assignable to type 'NullableJsonNullValueInput | InputJsonValue | undefined'.
Can sort of get around this by doing something like Partial<Omit<User, 'metadata'> & {metadata: object | undefined}> but its not ideal

@ben-mccrary-calendly On which Prisma Client version does this happen for you?
Could you share the output of npx prisma -v, and also provide a minimalistic reproduction (schema and code)?

@ben-mccrary-calendly On which Prisma Client version does this happen for you? Could you share the output of npx prisma -v, and also provide a minimalistic reproduction (schema and code)?

Made a repo with everything - https://github.com/ben-mccrary-calendly/prisma-issue-20058. On 5.2.0
But basically..
generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model User {
  id Int @id @default(autoincrement())
  metadata Json?
}

import {User, PrismaClient} from '@prisma/client'

const typescriptIsMad = async (id: number, user: Partial<User>) => {
    const client = new PrismaClient()
    await client.user.update({
        where: { id: id },
        // typescript has a problem with the line below because of Partial<User> and a nullable JSON field
        data: user
    })
}

It's cause of the whole Prisma.NullTypes.JsonNull versus Prisma.NullTypes.DbNull difference.


text:
Schema Drift with no changes

Bug description
I've been working with multiSchema and thought I'd managed to get everything happy, but now I've ended up in a situation where I get the dreaded Schema Drift message and asks me to reset the db, but doesn't list any changes.
> yarn prisma migrate dev --create-only
Prisma schema loaded from schema.prisma
Datasource "db": PostgreSQL database "postgres", schemas "auth, public, public_ro" at "aws-0-ap-southeast-2.pooler.supabase.com:5432"

Drift detected: Your database schema is not in sync with your migration history.

The following is a summary of the differences between the expected database schema given your migrations files, and the actual schema of the database.

It should be understood as the set of changes to get from the expected schema to the actual schema.

✔ We need to reset the following schemas: "auth, public, public_ro" at "aws-0-ap-southeast-2.pooler.supabase.com:5432"
Do you want to continue? All data will be lost. … no

Reset cancelled.

As far as Prisma migrate diff is concerned, we're actually all good.
> yarn prisma migrate diff --from-schema-datamodel ./schema.prisma --to-schema-datasource ./schema.prisma --script
-- This is an empty migration.

Because there is no changeset listed, I'm unsure what drift has occurred.
How to reproduce
yarn prisma migrate dev --create-only
Expected behavior
Migration should be created
Prisma information

// Add your schema.prisma
generator client {
  provider        = "prisma-client-js"
  output          = "./__generated__/prisma"
  previewFeatures = ["multiSchema", "tracing"]
}

datasource db {
  provider  = "postgresql"
  url       = env("APP_DATABASE_URL_RLS")
  directUrl = env("APP_DATABASE_URL_ADMIN")
  schemas   = ["public", "public_ro", "auth"]
}

// Supabase Auth Models

// Our Public Models

Environment & setup

OS: ubuntu / wsl2
Database: PostgreSQL
Node.js version: 20.9.0

Prisma Version
5.11.0

Ah, interestingly this was fixed by adding a new migration with create schema public_ro and marking it as applied. I assume it failed because there was no public_ro schema in the shadow database. Not sure this makes sense given I also didn't create the public or auth schemas via Prisma either.


text:
typedSql and Prisma Optimize extension errors

Bug description
It seems like the typedSql preview feature is not compatible with Prisma Optimize client extensions. Here is the error stack trace:
│ TypeError: Cannot read properties of undefined (reading 'map')
│     at El (/projects/prisma_optimize_tutorial/node_modules/.pnpm/@prisma+client@5.22.0_prisma@5.22.0/node_modules/@prisma/client/runtime/library.js:114:431)
│     at jt (projects/prisma_optimize_tutorial/node_modules/.pnpm/@prisma+client@5.22.0_prisma@5.22.0/node_modules/@prisma/client/runtime/library.js:114:376)
│     at /projects/prisma_optimize_tutorial/node_modules/.pnpm/@prisma+client@5.22.0_prisma@5.22.0/node_modules/@prisma/client/runtime/library.js:121:399
│     at Proxy._executeRequest (/projects/prisma_optimize_tutorial/node_modules/.pnpm/@prisma+client@5.22.0_prisma@5.22.0/node_modules/@prisma/client/runtime/library.js:130:10
│ 111)
│     at /projects/prisma_optimize_tutorial/node_modules/.pnpm/@prisma+client@5.22.0_prisma@5.22.0/node_modules/@prisma/client/runtime/library.js:31:9618
│     at i (/projects/prisma_optimize_tutorial/node_modules/.pnpm/@prisma+client@5.22.0_prisma@5.22.0/node_modules/@prisma/client/runtime/library.js:121:1016)
│     at PrismaPromise.then (/projects/prisma_optimize_tutorial/node_modules/.pnpm/@prisma+client@5.22.0_prisma@5.22.0/node_modules/@prisma/client/runtime/library.js:121:1091)
│     at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
│   clientVersion: '5.22.0'
│ }

Probably related to: https://github.com/prisma/prisma/issues/25481
How to reproduce

Enabled the tracing preview feature.
Enabled the typedSql preview feature.
Attempt to run $queryRawTyped

-- prisma/sql/getTodoCount.sql
SELECT COUNT(*) as count FROM "Todo";

import { getTodoCount } from "@prisma/client/sql";
const todoCount = await prisma.$queryRawTyped(getTodoCount())

It crashes only with the $extends, without it the client works fine.
Expected behavior
Be able to see queryRawTyped in Prisma Optimize  dashbaord
Prisma information

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["typedSql", "tracing"]
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model Todo {
  id          String   @id @default(cuid())
  title       String
  isCompleted Boolean  @default(false)
  isDeleted   Boolean  @default(false)
  createdAt   DateTime @default(now())
  updatedAt   DateTime @updatedAt
}

Environment & setup

OS: macOS
Database: PostgreSQL
Node.js version: v22.11.0 (lts)

Prisma Version
5.22.0

Hi @Aegirs
This is related to #25481. I'm going to close this in favour of that other issue.

authors: Aegirs ludralph


text:
PANIC: timer has gone away

Hi Prisma Team! My Prisma Client just crashed. This is the report:
Versions

Name
Version

Node
v20.17.0

OS
debian-openssl-1.0.x

Prisma Client
5.16.1

Query Engine
34ace0eb2704183d2c05b60b52fba5c43c13f303

Database
mysql

Logs
prisma:tryLoadEnv Environment variables not found at null
prisma:tryLoadEnv Environment variables not found at /home/n1602585/nodevenv/wtp-dev-api/20/lib/.env
prisma:tryLoadEnv No Environment variables loaded
prisma:client checkPlatformCaching:postinstall false
prisma:client checkPlatformCaching:ciName
prisma:tryLoadEnv Environment variables not found at null
prisma:tryLoadEnv Environment variables not found at /home/n1602585/nodevenv/wtp-dev-api/20/lib/.env
prisma:tryLoadEnv No Environment variables loaded
prisma:client dirname /home/n1602585/nodevenv/wtp-dev-api/20/lib/node_modules/.prisma/client
prisma:client relativePath ../../../prisma
prisma:client cwd /home/n1602585/nodevenv/wtp-dev-api/20/lib/node_modules/.prisma/client
prisma:client clientVersion 5.16.1
prisma:client:libraryEngine internalSetup
prisma:client checkPlatformCaching:postinstall false
prisma:client checkPlatformCaching:ciName
prisma:tryLoadEnv Environment variables not found at null
prisma:tryLoadEnv Environment variables not found at /home/n1602585/nodevenv/wtp-dev-api/20/lib/.env
prisma:tryLoadEnv No Environment variables loaded
prisma:client dirname /home/n1602585/nodevenv/wtp-dev-api/20/lib/node_modules/.prisma/client
prisma:client relativePath ../../../prisma
prisma:client cwd /home/n1602585/nodevenv/wtp-dev-api/20/lib/node_modules/.prisma/client
prisma:client clientVersion 5.16.1
prisma:client:libraryEngine internalSetup
prisma:client checkPlatformCaching:postinstall false
prisma:client checkPlatformCaching:ciName
prisma:tryLoadEnv Environment variables not found at null
prisma:tryLoadEnv Environment variables not found at /home/n1602585/nodevenv/wtp-dev-api/20/lib/.env
prisma:tryLoadEnv No Environment variables loaded
prisma:client dirname /home/n1602585/nodevenv/wtp-dev-api/20/lib/node_modules/.prisma/client
prisma:client relativePath ../../../prisma
prisma:client cwd /home/n1602585/nodevenv/wtp-dev-api/20/lib/node_modules/.prisma/client
prisma:client clientVersion 5.16.1
prisma:client:libraryEngine internalSetup
prisma:get-platform Don't know any platform-specific paths for "undefined" on x64 (x86_64)
prisma:get-platform Falling back to "ldconfig" and other generic paths
prisma:get-platform Don't know any platform-specific paths for "undefined" on x64 (x86_64)
prisma:get-platform Falling back to "ldconfig" and other generic paths
prisma:get-platform Don't know any platform-specific paths for "undefined" on x64 (x86_64)
prisma:get-platform Falling back to "ldconfig" and other generic paths
prisma:client:libraryEngine sending request, this.libraryStarted: false
prisma:get-platform Found libssl.so file using "ldconfig" or other generic paths: libssl.so.1.0.2o
prisma:get-platform The parsed libssl version is: 1.0.x
prisma:get-platform Distro is "undefined". Falling back to Prisma engines built for "debian".
prisma:client:engines:resolveEnginePath enginePath /home/n1602585/nodevenv/wtp-dev-api/20/lib/node_modules/.prisma/client/libquery_engine-debian-openssl-1.0.x.so.node
prisma:client:libraryEngine library starting
prisma:get-platform Found libssl.so file using "ldconfig" or other generic paths: libssl.so.1.0.2o
prisma:get-platform The parsed libssl version is: 1.0.x
prisma:get-platform Distro is "undefined". Falling back to Prisma engines built for "debian".
prisma:client:engines:resolveEnginePath enginePath /home/n1602585/nodevenv/wtp-dev-api/20/lib/node_modules/.prisma/client/libquery_engine-debian-openssl-1.0.x.so.node
prisma:get-platform Found libssl.so file using "ldconfig" or other generic paths: libssl.so.1.0.2o
prisma:get-platform The parsed libssl version is: 1.0.x
prisma:get-platform Distro is "undefined". Falling back to Prisma engines built for "debian".
prisma:client:engines:resolveEnginePath enginePath /home/n1602585/nodevenv/wtp-dev-api/20/lib/node_modules/.prisma/client/libquery_engine-debian-openssl-1.0.x.so.node
prisma:client:request_handler {"name":"PrismaClientRustPanicError","clientVersion":"5.16.1"}
prisma:client:libraryEngine sending request, this.libraryStarted: false
prisma:client:libraryEngine library starting
prisma:client:request_handler {"name":"PrismaClientRustPanicError","clientVersion":"5.16.1"}
prisma:client:libraryEngine sending request, this.libraryStarted: false
prisma:client:libraryEngine library starting

Hye @bayuhendrianto, can you please post the Prisma snippet that resulted in this panic? Without it, there's nothing we can do here. Thanks!

authors: bayuhendrianto jkomyno


text:
Update 01-Apollo.md

Proposal to include a bonus/optional deploy step at the end.
Since https://www.prismagraphql.com/docs/tutorials/graphql-server-development/deployment-with-now-ahs1jahkee only includes deploying the GraphQL server, and there were a couple steps that seemed confusing at first, so hopefully to save other people time.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hey @justinmpier, we're currently cleaning up our PRs. Apologies for not having looked at it in detail earlier, unfortunately it is outdated by now so I'll close it. Please keep opening PRs in the future if you see any issues with our docs 🙏

authors: CLAassistant justinmpier nikolasburk


text:
Expose GraphQl server options out of the box

I don't know if this feature is already planned/in the works, but it could provide a simpler way to work with other frameworks like Nuxt or Next
Is your feature request related to a problem? Please describe.
Currently, it's impossible to change server options (port, endpoint, playground, etc) without ejecting from conventions. I think it would be better if there was a simpler way to pass these options.
Describe the solution you'd like
There could be a new object in  yoga.config.ts that would allow changing those options. Options could be the same/similar to those in the start function of yoga1

@escargotprodige There currently is an express.ts config file that could be used to expose these options in the future.
Also, ejecting is not a permanent solution; one can still “reverse” the ejection. So this could be a temporary solution until the ability to configure some parts of the Express server are added.

@DevanB The settings could be exposed in both express.ts and yoga.config.ts so people don't need to create another file if they don't need it. If they don't need to use express features, they can still change the settings, vice-versa. Also it would let people choose where they put settings so if they want to keep all their settings in yoga.config.ts it is still possible.
Although, considering the plan to support multiple configurations files for different environments (roadmap), I think it would be better to prioritize exposing the settings in yoga.config.ts

Hey there,
This is a duplicate of #15. The issue is left open exactly for this purpose, you might find information about our original idea for not exposing the graphql server options, although I personally think there could be value in having such options in the config file.

authors: DevanB Weakky escargotprodige


text:
Gracefully handle query initialization errors

Currently IPA can recover if query execution fails at the protocol stage (i.e. when we actually start running IPA). However, if there was any error before that (that is - create_query or prepare_query failed), any subsequent attempt to run another query fails with "Query is already running error".
We have a drop guard already that removes the query from the list, we probably just need to change that to support another mode to clean up only if thread is panicking.

This is a bit annoying while running tests. Lets fix this before the test run @akoshelev. If you point me to an example of how to fix it, I can take it up

Do you happen to have a stack trace? I am not sure where we are panicking right now

One scenario I am aware of - when helper configuration is bad (wrong certificate, etc), an  attempt to run a query results in an SSL error. After that, helpers are unable to run queries. This is likely an unrecoverable error because it requires a bounce to read the new configuration, but deserves a quick fix anyway

It also happened when helpers were started without matchkey encryption keys and I tried to run a query with encryption enabled.

authors: akoshelev richajaindce

repo: private-attribution/ipa


text:
Plumb prng through as an arg where needed instead of making it a clas…

…s member.
I considered keeping prng as a member of (H)IRM, but plumbing it through added minimal code complexity and it seems better to pass it in where it's used instead of have it hidden in the class.
Closes #49

No prob! I needed something mechanical to do during the ChiExpert session on Friday...

repo: probcomp/hierarchical-irm


text:
RP2040 - Core gets stuck after reflashing

Describe the bug
Occasionally (~10% of the time) when I use probe-rs to reflash my chip with new software, the new software is reprogrammed but the chip appears to be stuck. The only way to get out of this state is to physically reset the chip.
probe-rs 0.23.0
git commit: 426750d

To Reproduce
Use probe-rs to reflash an RP2040 chip. This issue doesn't always manifest. I've noticed that it mostly happens with larger payloads
Expected behavior
Chip is reflashed and begins running the new software
Desktop (please complete the following information):
Ubuntu 22.04
Additional context
I'm using a CMSIS-DAP probe.
This is what I see after reflashing (again it's almost like the chip is running no software after reflashing since neither my old software nor the new one appears to be executing)
      Erasing ✔ [00:00:00] [###########################################################################################################################################################################################################################################################################################################] 56.00 KiB/56.00 KiB @ 71.87 KiB/s (eta 0s )
  Programming ✔ [00:00:01] [###########################################################################################################################################################################################################################################################################################################] 56.00 KiB/56.00 KiB @ 36.67 KiB/s (eta 0s )
    Finished in 2.337s
        Done processing config default
 WARN probe_rs::architecture::arm::core::armv6m: Core is running, but we expected it to be halted

Same on STM32F030CC. It seems that the chip is not reset automatically by probe-rs after flash done, unless manually run probe-rs reset. I don't know if it's a expected behavior.

probe-rs reset doesn't seem to be working for me
$ probe-rs reset --chip RP2040
 WARN probe_rs::architecture::arm::core::armv6m: The core is in locked up status as a result of an unrecoverable exception

Was running into a similar issue when reflashing an stm32h7 via an rp2040 probe running https://github.com/probe-rs/rusty-probe-firmware. Adding this delay between programming and the reset_and_halt seems to have fixed it: https://github.com/akhilles/probe-rs/commit/349ec7f1e93a1d238943db2258549edbcc631b93. Using the --verify flag, which effectively also adds a delay, also works.

authors: akhilles brt-adam-snaider xingrz

repo: probe-rs/probe-rs


text:
Added attention_jax.ipynb for attention_torch.ipynb

Based on: convert pytorch demos to JAX.

Converted torch code to jax and flax.
Verified that it runs on colab (after manually installing flax).

Edit:

Colab link
Rendered images

Please add a link to a version of the file which I can run
Please include commands to install flax etc
Please include any rendered images in the output

Please add a link to a version of the file which I can run

I have added the colab link.

Please include commands to install flax etc

Added.

Please include any rendered images in the output

Added.

authors: murphyk patel-zeel

repo: probml/probml-notebooks


text:
Error decoding HVAC IR code

I hope this library is still maintained! :-)
I'm attempting to convert the following code which throws an exception:
0000 006D 0000 0082 007D 003D 0010 000E 0010 000E 0010 002D 0010 000E 0010 002D 0010 000E 0010 000E 0010 000E 0010 002D 0010 002D 0010 000E 0010 000E 0010 000E 0010 002D 0010 002D 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 002D 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 002D 0010 000E 0010 000E 0010 000E 0010 000E 0010 002D 0010 002D 0010 002D 0010 002D 0010 002D 0010 002D 0010 002D 0010 002D 0010 000E 0010 000E 0010 002D 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 002D 0010 002D 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 002D 0010 000E 0010 002D 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 000E 0010 002D 0010 000E 0010 000E 0010 002D 0010 002D 0010 002D 0010 002D 0010 000E 0010 002D 0010 002D 0010 000E 0010 0ED1
This is the stack trace:
Exception (28):
epc1=0x4000bf80 epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000

ctx: cont
sp: 3ffef040 end: 3ffef380 offset: 01a0

>>>stack>>>
3ffef1e0:  4020184d 00000030 00000018 ffffffff
3ffef1f0:  006d0000 00820000 003d007d 000e0010
3ffef200:  000e0010 002d0010 000e0010 002d0010
3ffef210:  000e0010 000e0010 000e0010 002d0010
3ffef220:  002d0010 000e0010 000e0010 000e0010
3ffef230:  002d0010 002d0010 000e0010 000e0010
3ffef240:  000e0010 000e0010 000e0010 000e0010
3ffef250:  000e0010 000e0010 000e0010 000e0010
3ffef260:  000e0010 000e0010 000e0010 002d0010
3ffef270:  000e0010 000e0010 000e0010 000e0010
3ffef280:  000e0010 000e0010 000e0010 002d0010
3ffef290:  000e0010 000e0010 000e0010 000e0010
3ffef2a0:  002d0010 002d0010 002d0010 002d0010
3ffef2b0:  002d0010 002d0010 002d0010 002d0010
3ffef2c0:  000e0010 000e0010 002d0010 000e0010
3ffef2d0:  000e0010 000e0010 000e0010 000e0010
3ffef2e0:  000e0010 000e0010 000e0010 002d0010
3ffef2f0:  30313030 000e0000 000e0010 000e0010
3ffef300:  0000008b 3ffe0010 00000000 000002b7
3ffef310:  feefeffe 00000000 3ffee334 3ffee358
3ffef320:  3ffe8698 00000000 3ffee334 40201ced
3ffef330:  3fff07c4 0000052f 00000527 3fff028c
3ffef340:  0000052f 00000527 00000000 00000000
3ffef350:  00000000 feefeffe feefeffe feefeffe
3ffef360:  3fffdad0 00000000 3ffee350 402028d8
3ffef370:  feefeffe feefeffe 3ffee360 40100114
<<<stack<<<

I used the example sketch and just replaced the pronto code. I have a ESP-12E dev board. TV Codes seem to work fine.

Just guessing here, probably the code is too long to fit into some buffer. So the buffer needs to be increased. This is a typical issue in C.

Thanks :-) I ended up doing a rewrite of the lib. https://github.com/tuzzmaniandevil/ProntoHex

Interesting, thanks!

authors: probonopd tuzzmaniandevil

repo: probonopd/ProntoHex


text:
refactor(props): refactor about components

Based on our team's decision, we no longer require approval of the refactoring pull request. Instead, we will review and approve the refactoring once all changes related to a specific component have been completed.

https://github.com/process-analytics/process-analytics.dev/assets/4921914/ec3fc255-5a1c-473f-b3af-e9284310aa41
https://github.com/process-analytics/process-analytics.dev/assets/4921914/27882e94-149a-48e9-8328-784a2f3853dc


text:
document error capture

Document how procrastinate connects to error capture tools
Closes #606

Successful PR Checklist:

[ ] Tests

[x] (not applicable?)

[x] Documentation

[ ] (not applicable?)

Thank you, and congratulations.

authors: abe-winter ewjoachim

repo: procrastinate-org/procrastinate


text:
Update typed-error to 3.2.2

Change-type: patch

lgtm

repo: product-os/autumndb


text:
Conversion of label_name

With these commits, label_name function has been converted to a class named Label, extended from the original str. As it's just a subclass of str, it can be (and is) used as a drop-in replacement of label_name throughout the code. Modified files have been formatted with psf/black as well.
This branch has been branched from error-reporting, so includes it's changes as well.

cc/ @peterthiemann

If I understand correctly, this implementation of the Label class is good for tracking the type in the IDE, but it does not lead to a run-time error if someone ignores it and just puts in  a str.
I prefer a solution where Label is a distinct class with a getter name that returns the correctly formatted string. As Label is used as a key for dictionaries, it must be hashable and eq and all that. Something like
@dataclass(frozen=true) class Label:   name : str   def get(self):     return self.name
would do plus the mangling using sys.platform which you probably want to do in the __init__ method.
(Or maybe not.)
It would also be good to do the sys.platform == "darwin" test only once rather than every time you create a new label.

Changed the Label class into a distinct one with a name property, which is used throughout wherever it's needed. How does this look?

authors: berkaycagir peterthiemann

repo: proglang/assignment-final-stub


text:
Redirect subdomains to root domain and have custom ports

I have installed Dokku on DigitalOcean instance and it works really nice. Moreover; I would like have the following scenario regarding the subdomains of my domain and ports.

I want all subdomains to be Redirected to root domain and my production instance to be in the root domain listening port 80.
I also want a custom port for my staging instance. Of course, for the staging case also, all subdomains will be redirected to root domain by keeping the port.

For example
http://randomsubdomain.example.com will be redirected to http://www.example.com and be responded by my prod-app instance.
http://yarandomsubdomain.example.com:2323 will be redirected to http://www.example.com:2323 and be responded by my stag-app instance.
I looked DigitalOcean DNS, nginx and dokku plugins but I couldn't figure out how to do that. I appreciate any kind of help to give me a direction. Thanks.

I think this can now be accomplished with an nginx template and the domains plugin, no? Use the nginx template to do the redirection and the domains plugin to tie the root domain to a given app. Let me know if that works for your case.

The first part can potentially can be accomplished if we do #924. The ports bit might be tricky.

We now have custom ports via $DOKKU_NGINX_PORT and $DOKKU_NGINX_SSL_PORT

We also have an official redirect plugin. Closing. Let us know if these do not satisfy your use case.

authors: michaelshobbs osaatcioglu

repo: progrium/dokku


text:
[BUG] The bridge-app can connect to the homepod but not the google nest hub

Reproduction steps
The bridge can easily pair with my HomePod, but there's no way it can connect to my Google Nest Hub 2.
The error is too general "There is an error when connecting to the device".
Bug prevalence
all the time
GitHub hash of the SDK that was being used
latest
Platform
darwin
Platform Version(s)
No response
Anything else?
No response

Have you set up a matter integration project in the console?

I used the QR code that was generated from matter.

You need to set up a matter integration project in the google cloud console before, in order that the google home app gets the required information.

I stumbled over a tutorial from silabs https://docs.silabs.com/matter/2.1.0/matter-bridge/readme-user#using-google-nest-hub

repo: project-chip/connectedhomeip


text:
[Workflow] Submodule clone faild on ubuntu

Workflow issues
on ubuntu 18.04 + python 11  + x86_64
on branch test_event_7.lts

git submodule update --init
Submodule 'qrcode' (https://github.com/nayuki/QR-Code-generator.git) registered for path 'examples/common/QRCode/repo'
Submodule 'm5stack-tft' (https://github.com/jeremyjh/ESP32_TFT_library.git) registered for path 'examples/common/m5stack-tft/repo'
Submodule 'bluez' (https://github.com/bluez/bluez.git) registered for path 'third_party/bluez/repo'
Submodule 'cirque' (https://github.com/openweave/cirque.git) registered for path 'third_party/cirque/repo'
Submodule 'efr32_sdk' (https://github.com/SiliconLabs/sdk_support.git) registered for path 'third_party/efr32_sdk/repo'
Submodule 'freertos' (https://github.com/FreeRTOS/FreeRTOS-Kernel.git) registered for path 'third_party/freertos/repo'
Submodule 'happy' (https://github.com/openweave/happy.git) registered for path 'third_party/happy/repo'
Submodule 'mbed-os-cypress-capsense-button' (https://github.com/ARMmbed/mbed-os-cypress-capsense-button.git) registered for path 'third_party/mbed-os-cypress-capsense-button/repo'
Submodule 'third_party/mbed-os-posix-socket/repo' (https://github.com/ARMmbed/mbed-os-posix-socket.git) registered for path 'third_party/mbed-os-posix-socket/repo'
Submodule 'third_party/mbed-os/repo' (https://github.com/ARMmbed/mbed-os.git) registered for path 'third_party/mbed-os/repo'
Submodule 'mbedtls' (https://github.com/ARMmbed/mbedtls.git) registered for path 'third_party/mbedtls/repo'
Submodule 'nanopb' (https://github.com/nanopb/nanopb.git) registered for path 'third_party/nanopb/repo'
Submodule 'nlassert' (https://github.com/nestlabs/nlassert.git) registered for path 'third_party/nlassert/repo'
Submodule 'nlfaultinjection' (https://github.com/nestlabs/nlfaultinjection.git) registered for path 'third_party/nlfaultinjection/repo'
Submodule 'nlio' (https://github.com/nestlabs/nlio.git) registered for path 'third_party/nlio/repo'
Submodule 'nlunit-test' (https://github.com/nestlabs/nlunit-test.git) registered for path 'third_party/nlunit-test/repo'
Submodule 'third_party/openthread/ot-efr32' (https://github.com/openthread/ot-efr32.git) registered for path 'third_party/openthread/ot-efr32'
Submodule 'third_party/openthread/ot-nxp' (https://github.com/openthread/ot-nxp.git) registered for path 'third_party/openthread/ot-nxp'
Submodule 'third_party/openthread/ot-qorvo' (https://github.com/openthread/ot-qorvo.git) registered for path 'third_party/openthread/ot-qorvo'
Submodule 'openthread' (https://github.com/openthread/openthread.git) registered for path 'third_party/openthread/repo'
Submodule 'ot-br-posix' (https://github.com/openthread/ot-br-posix.git) registered for path 'third_party/ot-br-posix/repo'
Submodule 'p6/TARGET_CY8CKIT-062S2-43012' (https://github.com/Infineon/TARGET_CY8CKIT-062S2-43012) registered for path 'third_party/p6/p6_sdk/libs/TARGET_CY8CKIT-062S2-43012'
Submodule 'p6/abstraction-rtos' (https://github.com/Infineon/abstraction-rtos) registered for path 'third_party/p6/p6_sdk/libs/abstraction-rtos'
Submodule 'p6/bluetooth-freertos' (https://github.com/Infineon/bluetooth-freertos) registered for path 'third_party/p6/p6_sdk/libs/bluetooth-freertos'
Submodule 'p6/btstack' (https://github.com/Infineon/btstack) registered for path 'third_party/p6/p6_sdk/libs/btstack'
Submodule 'p6/clib-support' (https://github.com/Infineon/clib-support) registered for path 'third_party/p6/p6_sdk/libs/clib-support'
Submodule 'p6/connectivity-utilities' (https://github.com/Infineon/connectivity-utilities) registered for path 'third_party/p6/p6_sdk/libs/connectivity-utilities'
Submodule 'p6/core-lib' (https://github.com/Infineon/core-lib) registered for path 'third_party/p6/p6_sdk/libs/core-lib'
Submodule 'p6/core-make' (https://github.com/Infineon/core-make) registered for path 'third_party/p6/p6_sdk/libs/core-make'
Submodule 'p6/freertos' (https://github.com/Infineon/freertos) registered for path 'third_party/p6/p6_sdk/libs/freertos'
Submodule 'p6/kv-store' (https://github.com/Infineon/kv-store) registered for path 'third_party/p6/p6_sdk/libs/kv-store'
Submodule 'p6/mbedtls' (https://github.com/ARMmbed/mbedtls) registered for path 'third_party/p6/p6_sdk/libs/mbedtls'
Submodule 'p6/mtb-hal-cat1' (https://github.com/Infineon/mtb-hal-cat1) registered for path 'third_party/p6/p6_sdk/libs/mtb-hal-cat1'
Submodule 'p6/mtb-pdl-cat1' (https://github.com/Infineon/mtb-pdl-cat1) registered for path 'third_party/p6/p6_sdk/libs/mtb-pdl-cat1'
Submodule 'p6/psoc6cm0p' (https://github.com/Infineon/psoc6cm0p) registered for path 'third_party/p6/p6_sdk/libs/psoc6cm0p'
Submodule 'p6/recipe-make-cat1a' (https://github.com/Infineon/recipe-make-cat1a) registered for path 'third_party/p6/p6_sdk/libs/recipe-make-cat1a'
Submodule 'p6/retarget-io' (https://github.com/Infineon/retarget-io) registered for path 'third_party/p6/p6_sdk/libs/retarget-io'
Submodule 'p6/secure-sockets' (https://github.com/Infineon/secure-sockets) registered for path 'third_party/p6/p6_sdk/libs/secure-sockets'
Submodule 'p6/whd-bsp-integration' (https://github.com/Infineon/whd-bsp-integration) registered for path 'third_party/p6/p6_sdk/libs/whd-bsp-integration'
Submodule 'p6/wifi-connection-manager' (https://github.com/Infineon/wifi-connection-manager) registered for path 'third_party/p6/p6_sdk/libs/wifi-connection-manager'
Submodule 'p6/wifi-host-driver' (https://github.com/Infineon/wifi-host-driver) registered for path 'third_party/p6/p6_sdk/libs/wifi-host-driver'
Submodule 'p6/wifi-mw-core' (https://github.com/Infineon/wifi-mw-core) registered for path 'third_party/p6/p6_sdk/libs/wifi-mw-core'
Submodule 'pigweed' (https://github.com/google/pigweed.git) registered for path 'third_party/pigweed/repo'
Submodule 'third_party/pybind11/repo' (https://github.com/pybind/pybind11) registered for path 'third_party/pybind11/repo'
Submodule 'qpg_sdk' (https://github.com/Qorvo/qpg-connectedhomeip) registered for path 'third_party/qpg_sdk/repo'
Submodule 'simw-top-mini' (https://github.com/NXP/plug-and-trust.git) registered for path 'third_party/simw-top-mini/repo'
Submodule 'zap' (https://github.com/project-chip/zap.git) registered for path 'third_party/zap/repo'
Cloning into '/root/workspace/github/matter/examples/common/QRCode/repo'...
Cloning into '/root/workspace/github/matter/examples/common/m5stack-tft/repo'...
Cloning into '/root/workspace/github/matter/third_party/bluez/repo'...
Cloning into '/root/workspace/github/matter/third_party/cirque/repo'...
Cloning into '/root/workspace/github/matter/third_party/efr32_sdk/repo'...
fatal: the remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
fatal: clone of 'https://github.com/SiliconLabs/sdk_support.git' into submodule path '/root/workspace/github/matter/third_party/efr32_sdk/repo' failed
Failed to clone 'third_party/efr32_sdk/repo'. Retry scheduled
Cloning into '/root/workspace/github/matter/third_party/freertos/repo'...
Cloning into '/root/workspace/github/matter/third_party/happy/repo'...
Cloning into '/root/workspace/github/matter/third_party/mbed-os-cypress-capsense-button/repo'...
Cloning into '/root/workspace/github/matter/third_party/mbed-os-posix-socket/repo'...
Cloning into '/root/workspace/github/matter/third_party/mbed-os/repo'...
fatal: the remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
fatal: clone of 'https://github.com/ARMmbed/mbed-os.git' into submodule path '/root/workspace/github/matter/third_party/mbed-os/repo' failed
Failed to clone 'third_party/mbed-os/repo'. Retry scheduled
Cloning into '/root/workspace/github/matter/third_party/mbedtls/repo'...
fatal: the remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
fatal: clone of 'https://github.com/ARMmbed/mbedtls.git' into submodule path '/root/workspace/github/matter/third_party/mbedtls/repo' failed
Failed to clone 'third_party/mbedtls/repo'. Retry scheduled
Cloning into '/root/workspace/github/matter/third_party/nanopb/repo'...
Cloning into '/root/workspace/github/matter/third_party/nlassert/repo'...
Cloning into '/root/workspace/github/matter/third_party/nlfaultinjection/repo'...
Cloning into '/root/workspace/github/matter/third_party/nlio/repo'...
Cloning into '/root/workspace/github/matter/third_party/nlunit-test/repo'...
Cloning into '/root/workspace/github/matter/third_party/openthread/ot-efr32'...
Cloning into '/root/workspace/github/matter/third_party/openthread/ot-nxp'...
Cloning into '/root/workspace/github/matter/third_party/openthread/ot-qorvo'...
Cloning into '/root/workspace/github/matter/third_party/openthread/repo'...
Cloning into '/root/workspace/github/matter/third_party/ot-br-posix/repo'...
Cloning into '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/TARGET_CY8CKIT-062S2-43012'...
Cloning into '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/abstraction-rtos'...
Cloning into '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/bluetooth-freertos'...
Cloning into '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/btstack'...
fatal: the remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
fatal: clone of 'https://github.com/Infineon/btstack' into submodule path '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/btstack' failed
Failed to clone 'third_party/p6/p6_sdk/libs/btstack'. Retry scheduled
Cloning into '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/clib-support'...
fatal: unable to access 'https://github.com/Infineon/clib-support/': GnuTLS recv error (-110): The TLS connection was non-properly terminated.
fatal: clone of 'https://github.com/Infineon/clib-support' into submodule path '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/clib-support' failed
Failed to clone 'third_party/p6/p6_sdk/libs/clib-support'. Retry scheduled
Cloning into '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/connectivity-utilities'...
fatal: unable to access 'https://github.com/Infineon/connectivity-utilities/': Failed to connect to github.com port 443: Connection timed out
fatal: clone of 'https://github.com/Infineon/connectivity-utilities' into submodule path '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/connectivity-utilities' failed
Failed to clone 'third_party/p6/p6_sdk/libs/connectivity-utilities'. Retry scheduled
Cloning into '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/core-lib'...
fatal: unable to access 'https://github.com/Infineon/core-lib/': Failed to connect to github.com port 443: Connection timed out
fatal: clone of 'https://github.com/Infineon/core-lib' into submodule path '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/core-lib' failed
Failed to clone 'third_party/p6/p6_sdk/libs/core-lib'. Retry scheduled
Cloning into '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/core-make'...
fatal: unable to access 'https://github.com/Infineon/core-make/': Failed to connect to github.com port 443: Connection timed out
fatal: clone of 'https://github.com/Infineon/core-make' into submodule path '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/core-make' failed
Failed to clone 'third_party/p6/p6_sdk/libs/core-make'. Retry scheduled
Cloning into '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/freertos'...
fatal: unable to access 'https://github.com/Infineon/freertos/': GnuTLS recv error (-110): The TLS connection was non-properly terminated.
fatal: clone of 'https://github.com/Infineon/freertos' into submodule path '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/freertos' failed
Failed to clone 'third_party/p6/p6_sdk/libs/freertos'. Retry scheduled
Cloning into '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/kv-store'...
fatal: unable to access 'https://github.com/Infineon/kv-store/': Failed to connect to github.com port 443: Connection timed out
fatal: clone of 'https://github.com/Infineon/kv-store' into submodule path '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/kv-store' failed
Failed to clone 'third_party/p6/p6_sdk/libs/kv-store'. Retry scheduled
Cloning into '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/mbedtls'...
fatal: unable to access 'https://github.com/ARMmbed/mbedtls/': Failed to connect to github.com port 443: Connection timed out
fatal: clone of 'https://github.com/ARMmbed/mbedtls' into submodule path '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/mbedtls' failed
Failed to clone 'third_party/p6/p6_sdk/libs/mbedtls'. Retry scheduled
Cloning into '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/mtb-hal-cat1'...
fatal: unable to access 'https://github.com/Infineon/mtb-hal-cat1/': Failed to connect to github.com port 443: Connection timed out
fatal: clone of 'https://github.com/Infineon/mtb-hal-cat1' into submodule path '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/mtb-hal-cat1' failed
Failed to clone 'third_party/p6/p6_sdk/libs/mtb-hal-cat1'. Retry scheduled
Cloning into '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/mtb-pdl-cat1'...
fatal: unable to access 'https://github.com/Infineon/mtb-pdl-cat1/': Failed to connect to github.com port 443: Connection timed out
fatal: clone of 'https://github.com/Infineon/mtb-pdl-cat1' into submodule path '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/mtb-pdl-cat1' failed
Failed to clone 'third_party/p6/p6_sdk/libs/mtb-pdl-cat1'. Retry scheduled
Cloning into '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/psoc6cm0p'...
fatal: unable to access 'https://github.com/Infineon/psoc6cm0p/': Failed to connect to github.com port 443: Connection timed out
fatal: clone of 'https://github.com/Infineon/psoc6cm0p' into submodule path '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/psoc6cm0p' failed
Failed to clone 'third_party/p6/p6_sdk/libs/psoc6cm0p'. Retry scheduled
Cloning into '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/recipe-make-cat1a'...
Cloning into '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/retarget-io'...
Cloning into '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/secure-sockets'...
Cloning into '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/whd-bsp-integration'...
Cloning into '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/wifi-connection-manager'...
Cloning into '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/wifi-host-driver'...
Cloning into '/root/workspace/github/matter/third_party/p6/p6_sdk/libs/wifi-mw-core'...
Cloning into '/root/workspace/github/matter/third_party/pigweed/repo'...
fatal: the remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
fatal: clone of 'https://github.com/google/pigweed.git' into submodule path '/root/workspace/github/matter/third_party/pigweed/repo' failed
Failed to clone 'third_party/pigweed/repo'. Retry scheduled
Cloning into '/root/workspace/github/matter/third_party/pybind11/repo'...
Cloning into '/root/workspace/github/matter/third_party/qpg_sdk/repo'...
Username for 'https://github.com': Password for 'https://github.com':
remote: Repository not found.
fatal: Authentication failed for 'https://github.com/Qorvo/qpg-connectedhomeip/'
fatal: clone of 'https://github.com/Qorvo/qpg-connectedhomeip' into submodule path '/root/workspace/github/matter/third_party/qpg_sdk/repo' failed
Failed to clone 'third_party/qpg_sdk/repo'. Retry scheduled
Cloning into '/root/workspace/github/matter/third_party/simw-top-mini/repo'...
Cloning into '/root/workspace/github/matter/third_party/zap/repo'...
Cloning into '/root/workspace/github/matter/third_party/efr32_sdk/repo'...
error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: CANCEL (err 8)
fatal: the remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
fatal: clone of 'https://github.com/SiliconLabs/sdk_support.git' into submodule path '/root/workspace/github/matter/third_party/efr32_sdk/repo' failed
Failed to clone 'third_party/efr32_sdk/repo' a second time, aborting
Platform
No response
Anything else?
No response

I'm also facing the same issues with cloning the submodules


text:
[Cirque] use virtualenv

After upgrading to 24.04 it becomes very obvious that cirque should use a virtualenv instead of dirtying the system python packages.
We should instead create a virtualenv for every pip package install and python usage. We also seem to have significant copy&paste throughout the tests for pip install, those should be consolidated.

@andy31415 could you review the PR #36163 ? I don't know why there is no reviewers in this PR.

@andy31415 could you review the PR #36163 ? I don't know why there is no reviewers in this PR.

Reviewers are not added automatically anymore as that did not seem to actually encourage reviews (we kept adding the same 20-30 people on every PR). I expect reviews to happen and that PR does have one review and probably is a candidate for fast track.
I did have a comment on it though: it requires a"how is this tested" section (or if this just changes cirque tests, a statement that cirque tests uses this and as such it is tested). I would also prefer creating things into out instead of separating out yet another folder in the top level source tree.


text:
[Build] Compiling Android v1.3.0.0 version: 'CHIP_DEVICE_CONFIG_DYNAMIC_SERVER' is not defined

In the v1.3.0.0 branch, an error occurs when compiling Android products. The problem seems to be the definition of the macro writing problem

../../src/controller/java/AndroidDeviceControllerWrapper.h:49:5: error: 'CHIP_DEVICE_CONFIG_DYNAMIC_SERVER' is not defined, evaluates to 0 [-Werror,-Wundef]
#if CHIP_DEVICE_CONFIG_DYNAMIC_SERVER
^
../../src/controller/java/AndroidDeviceControllerWrapper.h:264:5: error: 'CHIP_DEVICE_CONFIG_DYNAMIC_SERVER' is not defined, evaluates to 0 [-Werror,-Wundef]
#if CHIP_DEVICE_CONFIG_DYNAMIC_SERVER
^
../../src/controller/java/AndroidDeviceControllerWrapper.cpp:647:5: error: 'CHIP_DEVICE_CONFIG_DYNAMIC_SERVER' is not defined, evaluates to 0 [-Werror,-Wundef]
#if CHIP_DEVICE_CONFIG_DYNAMIC_SERVER
^
../../src/controller/java/AndroidDeviceControllerWrapper.cpp:677:5: error: 'CHIP_DEVICE_CONFIG_DYNAMIC_SERVER' is not defined, evaluates to 0 [-Werror,-Wundef]
#if CHIP_DEVICE_CONFIG_DYNAMIC_SERVER
^
4 errors generated.

Sounds like someone is forgetting to include the right config headers...

this should have already be fixed in master branch via https://github.com/project-chip/connectedhomeip/pull/32704/commits/bbe758b3a2e4af14b13223cc554f5bdf415f9289
I am closing this one, feel free to reopen if the issue is still outstanding, thanks

authors: bzbarsky-apple kuyu132 yunhanw-google


text:
Mbed OS Docker image verification

Problem
Our team work on adding Mbed OS support into the CHIP project. Having Mbed OS docker image from this repository usable in our fork would help us with development where we have to sync often and work using the both the fork and the upstream repo.
Proposed Solution
Add GitHub workflow to verify Mbed OS image build process.

Please note: https://github.com/project-chip/connectedhomeip/issues/4654

@woody-apple Thanks, I will take a look.

authors: lukgni woody-apple


text:
RPC: Remove chip console build step from linux lighting

Problem
CI is seeing errors building the python whl for chip console as part of the linux example.
Change overview
Remove automatic install of the console for now until we can debug the issue.

fast track and it seems  reasonable to not make lighting app pull in a pigweed  wheel build for a separate example.


text:
Fix name prefix for host builds

Problem
build-examples.py fails to copy host output binaries because the name of the app is chip-all-clusters-app (code is missing the chip- prefix)
Change overview
Add the prefix
Testing
Manual test with --copy-artifacts-to argument passed in

Mark as hotfix to fix cloudbuild CI.


text:
[Add] Design doc for CodeFlare SDK

This PR adds design documentation for CodeFlare SDK to the repository for reference in future.
Issue link

What changes have been made

Verification steps

Checks

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

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

Just need to resolve conflict and it lgtm

@Bobbins228 could you approve the PR if everything looks good? Thanks! :)

repo: project-codeflare/codeflare-sdk


text:
JavaScript stubs inconsistent with var vs let

Some of the JavaScript code stubs use var to declare variables, while other use let to declare variables. These should probably be consistent between stubs (I'd advocate for let over var, but either way it should be consistent).

Ah good catch! We should switch to let as part of cleaning up the Javascript code stubs (+ #137). I'll be sure to use let in any future Javascript code stubs.

Fixed with #144

authors: BinaryFissionGames ali-ramadhan

repo: project-lovelace/lovelace-website