text:
Fast server failed

I got this all working well, untill some recents reboots, made last upgrades now it fails with:
|| fast
|| Quantity            1
|| Command             bundle exec rake postal:fast_server
|| Respawning          5 every 3600 seconds
|| Restart mode        term-start
|| Log path            none specified
|| Address/Port        none
|| => fast.1           Failed       02/12/2020   pid:2880     respawns:0      port:-        tag:-

Executing manually bundle exec rake postal:fast_server is like stuck.
postal@post:~/app$ bundle exec rake postal:fast_server --trace
** Invoke postal:fast_server (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute postal:fast_server
The log shows:
ESC[35m[fast.2:17030]ESC[0m [2020-12-03T22:45:06.915] INFO -- : Fast server started listening on HTTP (92.222.242.242:80)
ESC[35m[fast.2:17030]ESC[0m [2020-12-03T22:45:06.915] INFO -- : Fast server started listening on HTTPS port (92.222.242.242:443)
ESC[31m[fast.3:17159]ESC[0m [2020-12-03T22:45:26.903] INFO -- : Fast server started listening on HTTP (92.222.242.242:80)
ESC[31m[fast.3:17159]ESC[0m [2020-12-03T22:45:26.903] INFO -- : Fast server started listening on HTTPS port (92.222.242.242:443)
ESC[32m[fast.4:17279]ESC[0m [2020-12-03T22:45:37.476] INFO -- : Fast server started listening on HTTP (92.222.242.242:80)
ESC[32m[fast.4:17279]ESC[0m [2020-12-03T22:45:37.476] INFO -- : Fast server started listening on HTTPS port (92.222.242.242:443)

From sentry log:
Interrupt: null
  from lib/postal/fast_server/server.rb:29:in `select'
  from lib/postal/fast_server/server.rb:29:in `block in run'
  from lib/postal/fast_server/server.rb:27:in `loop'
  from lib/postal/fast_server/server.rb:27:in `run'
  from lib/tasks/postal.rake:33:in `block (2 levels) in <top (required)>'
  from rake/task.rb:273:in `block in execute'
  from rake/task.rb:273:in `each'
  from rake/task.rb:273:in `execute'
  from rake/task.rb:214:in `block in invoke_with_call_chain'
  from monitor.rb:214:in `mon_synchronize'
  from rake/task.rb:194:in `invoke_with_call_chain'
  from rake/task.rb:183:in `invoke'
  from rake/application.rb:160:in `invoke_task'
  from rake/application.rb:116:in `block (2 levels) in top_level'
  from rake/application.rb:116:in `each'
  from rake/application.rb:116:in `block in top_level'
  from rake/application.rb:125:in `run_with_threads'
  from rake/application.rb:110:in `top_level'
  from rake/application.rb:83:in `block in run'
  from rake/application.rb:186:in `standard_exception_handling'
  from rake/application.rb:80:in `run'
  from /opt/postal/vendor/bundle/ruby/2.3.0/gems/rake-12.3.3/exe/rake:27:in `<top (required)>'
  from /opt/postal/vendor/bundle/ruby/2.3.0/bin/rake:22:in `load'
  from /opt/postal/vendor/bundle/ruby/2.3.0/bin/rake:22:in `<main>'

SignalException: SIGTERM
  from lib/postal/fast_server/server.rb:29:in `select'
  from lib/postal/fast_server/server.rb:29:in `block in run'
  from lib/postal/fast_server/server.rb:27:in `loop'
  from lib/postal/fast_server/server.rb:27:in `run'
  from lib/tasks/postal.rake:33:in `block (2 levels) in <top (required)>'
  from rake/task.rb:273:in `block in execute'
  from rake/task.rb:273:in `each'
  from rake/task.rb:273:in `execute'
  from rake/task.rb:214:in `block in invoke_with_call_chain'
  from monitor.rb:214:in `mon_synchronize'
  from rake/task.rb:194:in `invoke_with_call_chain'
  from rake/task.rb:183:in `invoke'
  from rake/application.rb:160:in `invoke_task'
  from rake/application.rb:116:in `block (2 levels) in top_level'
  from rake/application.rb:116:in `each'
  from rake/application.rb:116:in `block in top_level'
  from rake/application.rb:125:in `run_with_threads'
  from rake/application.rb:110:in `top_level'
  from rake/application.rb:83:in `block in run'
  from rake/application.rb:186:in `standard_exception_handling'
  from rake/application.rb:80:in `run'
  from /opt/postal/vendor/bundle/ruby/2.3.0/gems/rake-12.3.3/exe/rake:27:in `<top (required)>'
  from /opt/postal/vendor/bundle/ruby/2.3.0/bin/rake:22:in `load'
  from /opt/postal/vendor/bundle/ruby/2.3.0/bin/rake:22:in `<main>'

what is weird is that after few restarts it seems to be working, and when i login its failes again.

Odd indeed, you could try comparing your Postal code against a fresh git checkout and see if there are any bad differences or alternatively you aren't running any antivirus or anything like that that would kill the processes randomly?

repo: postalhq/postal


text:
[WIP] feat(index): pass result.root, result.messages as metadata to loaders

This PR exposes result.root && result.messages to other loaders via the meta parameter in the loader callback. result.root is needed for css-loader v1.0.0 to avoid reparsing the file and result.messages is/will be needed especially for CSS Modules support in postcss-loader to expose the messages/dependencies of various postcss-icss-* plugins to css-loader e.g
// passed by postcss-loader to css-loader
const messages = [
  {
    // postcss-icss-selectors
    selectors: [
       className: '436kfzuk',
       ...,
    ]
  }
]

will be process and exported by css-loader as a named ESM Export
// CSS URLs (.selector { decl: url(); })
import CSS__URL__0 from './file.png'; // => resolved by 'file-loader'

// CSS Imports (@import)
import CSS__IMPORT__0 from './file.css'; // => recursively resolved by css-loader!postcss-loader

// CSS Exports (CSS Modules) // <= This PR
export const className = ' 436kfzuk';
...

// CSS
export default \`${css)\`;

Type

ℹ  What types of changes does your code introduce?

[x] Feature

SemVer

ℹ  What changes to the current semver range does your PR introduce?

[x] Feature (:label: Minor)

Issues

ℹ  What issue (if any) are closed by your PR ?

Fixes #227

Checklist

ℹ  You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. This is a reminder of what we are going to look for before merging your code.

[x] Lint and unit tests pass with my changes
[x] I have added tests that prove my fix is effective/works
[x] I have added necessary documentation (if appropriate)
[x] Any dependent changes are merged and published in downstream modules

Coverage decreased (-0.2%) to 86.624% when pulling 60220832b4095013a59bd196717cc77dd5b5221e on feature/meta into b9c1add9a1c5abfebd58006965d278787ce28d4a on master.

source: gharchive/pull-request

authors: coveralls michael-ciniawsky

repo: postcss/postcss-loader

license: MIT

license_type: permissive

license_source: github-api


text:
Add missing on_4f_nil_precommit in the Pseudo code

Note that this is not included in Tendermint (They don't care about the early termination of the round)

hmm I think this is a mistake. It's already implemented

source: gharchive/issue

repo: postech-dao/simperby


text:
Add css file

Add styles to index.html

Let me try

authors: lokeshvasnik potapchuk-anna

repo: potapchuk-anna/homepage


text:
version bump to 1.4.0

Closes: #219

[x] Fix Failing Tests
[x] Update Acceptance Test Example
[x] Add ability to return flash object
[x] Defer remove on mouse over
[x] Add changelog for release notes

@poteto Let me know if you are good with bumping to version 1.4.0 and I can merge add the git tag. Would need you to publish to npm if you 👍 the changes

@sbatson5 LGTM, I'll add you as a collaborator on the npm package tomorrow

repo: poteto/ember-cli-flash

license: mit

license_source: bigquery


text:
Update README.md for Ember-CLI 0.2.3

Ember CLI updated it's install command.  This commit puts documentation inline with the new command while keeping the old syntax around for those who need it.

Thanks!

@poteto -- Looks good to go on tests and squashed the commit to just the original and linebreaks.

Awesome, thank you! :)

Thanks Lauren =]


text:
PotreeConverter gets killed in a Docker container after processing 60000000 points

@m-schuetz
I am trying to process a LAZ file (774 MB) using Potree Converter. It is running in a docker container. After processing 60000000 points, the converter gets killed. Please see the output for details. Any recommendations to get this working?
root@fcc6f9096a0d:/data# ./PotreeConverter/build/PotreeConverter/PotreeConverter /input -o /output --output-format LAZ
== params ==
source[0]:         	/input
outdir:            	/output
spacing:           	0
diagonal-fraction: 	200
levels:            	-1
format:
scale:             	0
pageName:
projection:

AABB:
min: [762042, 3.38515e+06, 48.864]
max: [762782, 3.38587e+06, 77.331]
size: [740.186, 727.092, 28.467]

cubic AABB:
min: [762042, 3.38515e+06, 48.864]
max: [762782, 3.38589e+06, 789.05]
size: [740.186, 740.186, 740.186]

spacing calculated from diagonal: 6.4102
READING:  /input/TexasPowerline_UTM14N_RGB_Classified.laz
INDEXING: 1000000 points processed; 1000000 points written; 0.97 seconds passed
INDEXING: 2000000 points processed; 2000000 points written; 1.932 seconds passed
INDEXING: 3000000 points processed; 3000000 points written; 3.008 seconds passed
INDEXING: 4000000 points processed; 4000000 points written; 4.229 seconds passed
INDEXING: 5000000 points processed; 5000000 points written; 5.543 seconds passed
INDEXING: 6000000 points processed; 6000000 points written; 6.823 seconds passed
INDEXING: 7000000 points processed; 7000000 points written; 8.156 seconds passed
INDEXING: 8000000 points processed; 8000000 points written; 9.533 seconds passed
INDEXING: 9000000 points processed; 9000000 points written; 10.984 seconds passed
INDEXING: 10000000 points processed; 10000000 points written; 12.427 seconds passed
FLUSHING: 36.263s
INDEXING: 11000000 points processed; 11000000 points written; 50.271 seconds passed
INDEXING: 12000000 points processed; 12000000 points written; 51.897 seconds passed
INDEXING: 13000000 points processed; 13000000 points written; 53.582 seconds passed
INDEXING: 14000000 points processed; 14000000 points written; 55.251 seconds passed
INDEXING: 15000000 points processed; 15000000 points written; 56.997 seconds passed
INDEXING: 16000000 points processed; 16000000 points written; 58.743 seconds passed
INDEXING: 17000000 points processed; 17000000 points written; 60.534 seconds passed
INDEXING: 18000000 points processed; 18000000 points written; 62.33 seconds passed
INDEXING: 19000000 points processed; 19000000 points written; 64.246 seconds passed
INDEXING: 20000000 points processed; 20000000 points written; 66.079 seconds passed
FLUSHING: 70.699s
INDEXING: 21000000 points processed; 21000000 points written; 138.711 seconds passed
INDEXING: 22000000 points processed; 22000000 points written; 140.653 seconds passed
INDEXING: 23000000 points processed; 23000000 points written; 142.582 seconds passed
INDEXING: 24000000 points processed; 24000000 points written; 144.442 seconds passed
INDEXING: 25000000 points processed; 25000000 points written; 146.497 seconds passed
INDEXING: 26000000 points processed; 26000000 points written; 148.632 seconds passed
INDEXING: 27000000 points processed; 27000000 points written; 150.674 seconds passed
INDEXING: 28000000 points processed; 28000000 points written; 152.787 seconds passed
INDEXING: 29000000 points processed; 29000000 points written; 155.12 seconds passed
INDEXING: 30000000 points processed; 30000000 points written; 157.266 seconds passed
FLUSHING: 115.347s
INDEXING: 31000000 points processed; 31000000 points written; 274.103 seconds passed
INDEXING: 32000000 points processed; 32000000 points written; 275.731 seconds passed
INDEXING: 33000000 points processed; 33000000 points written; 277.202 seconds passed
INDEXING: 34000000 points processed; 34000000 points written; 278.953 seconds passed
INDEXING: 35000000 points processed; 35000000 points written; 280.636 seconds passed
INDEXING: 36000000 points processed; 36000000 points written; 282.467 seconds passed
INDEXING: 37000000 points processed; 37000000 points written; 284.459 seconds passed
INDEXING: 38000000 points processed; 38000000 points written; 286.862 seconds passed
INDEXING: 39000000 points processed; 39000000 points written; 288.884 seconds passed
INDEXING: 40000000 points processed; 40000000 points written; 291.248 seconds passed
FLUSHING: 53.473s
INDEXING: 41000000 points processed; 41000000 points written; 347.298 seconds passed
INDEXING: 42000000 points processed; 42000000 points written; 349.763 seconds passed
INDEXING: 43000000 points processed; 43000000 points written; 352.306 seconds passed
INDEXING: 44000000 points processed; 44000000 points written; 355.177 seconds passed
INDEXING: 45000000 points processed; 45000000 points written; 358.165 seconds passed
INDEXING: 46000000 points processed; 46000000 points written; 361.306 seconds passed
INDEXING: 47000000 points processed; 47000000 points written; 364.683 seconds passed
INDEXING: 48000000 points processed; 48000000 points written; 367.968 seconds passed
INDEXING: 49000000 points processed; 49000000 points written; 371.243 seconds passed
INDEXING: 50000000 points processed; 50000000 points written; 375.377 seconds passed
FLUSHING: 66.463s
INDEXING: 51000000 points processed; 51000000 points written; 445.214 seconds passed
INDEXING: 52000000 points processed; 52000000 points written; 448.759 seconds passed
INDEXING: 53000000 points processed; 53000000 points written; 452.744 seconds passed
INDEXING: 54000000 points processed; 54000000 points written; 456.714 seconds passed
INDEXING: 55000000 points processed; 55000000 points written; 461.18 seconds passed
INDEXING: 56000000 points processed; 56000000 points written; 466.335 seconds passed
INDEXING: 57000000 points processed; 57000000 points written; 471.616 seconds passed
INDEXING: 58000000 points processed; 58000000 points written; 476.769 seconds passed
INDEXING: 59000000 points processed; 59000000 points written; 482.641 seconds passed
INDEXING: 60000000 points processed; 60000000 points written; 492.572 seconds passed
Killed

I didn't setup the docker container as per instructions and hence the problem. Closing this issue as it is a user error.

@cherukumilli can you specify which instructions you followed?
I have the same problem and can't solve it
thank you

authors: Nevernat cherukumilli

repo: potree/PotreeConverter


text:
Try adding a manually triggered workflow

Add the workflow to main for testing if run button appears when the configuration is in main branch.

Developing #35

repo: pottumuusi/rogue-forever


text:
New Filter

I'd like to see a 'Min vCPUs Count' please.
(Feature Request)

@ronpzenoss I guess it'd be useful for someone taking this up if you could point to the source AWS URIs to find the required 'Min vCPUs Count'.

@powdahound think this can be closed
https://github.com/powdahound/ec2instances.info/blob/5281faf2a9dfec2bff233ae375b6872f90e8f756/in/index.html.mako#L108

I'm not sure @ronpzenoss was asking for a filter, though I'm not sure what the request was actually for. Please reopen with more details if this is still wanted.

authors: PatMyron checkaayush powdahound ronpzenoss


text:
Improve performance of PC lookup

The typical PC lookup is a gigantic lookup of more than 200 columns into a fixed table.
There are three things that could be optimized:

The index uses a BTreeMap, because it is generic. For the PC lookup, it might be useful to try out if a Vec could provide better performance. We could start building a BTreeMap and once the index is finished, we check how "dense" the entries are. If they are dense enough, we could switch to Vec. Note that the value of the index is a row index, so it is rather small.

Instead of storing the row number, store the actual values. That could save an indirection, but maybe the cache is so small that it is in the cache anyway. I think I tried that once and it did not provide a big gain.

Once we know which row to copy the values from the fixed column table, we need to actually assign them to the witness columns.
This is done in the following code:

        let mut result = EvalValue::complete(vec![]);
        for (l, r) in output_expressions.into_iter().zip(output) {
            let evaluated = l.clone() - r.into();
            // TODO we could use bit constraints here
            match evaluated.solve() {
                Ok(constraints) => {
                    result.combine(constraints);
                }

Note that it generates an equation and solves it. This is useful if the LHS is x + 2 or something like that, but I think in that case we might not even use the lookup. An easy win might be to add a funciton solve_equal(&self, rhs: T) to AlgebraicExpression, which checks if coefficients.len() == 1, and then just directly returns the result. Otherwise, it calls (self.clone() - rhs.into()).solve().

Looks like dup https://github.com/powdr-labs/powdr/issues/343

authors: chriseth leonardoalt

repo: powdr-labs/powdr


text:
🛑 Raspberry Pi Tunnel is down

In 9a0d055, Raspberry Pi Tunnel (https://rpiblog.l3zc.com) was down:

HTTP code: 530
Response time: 107 ms

Resolved: Raspberry Pi Tunnel is back up in 64b11da after 18 minutes.

repo: powerfullz/upptime


text:
Update golang/master build

This is an automated PR via build-bot

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ltccci
To complete the pull request process, please assign
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


text:
Update kubernetes/master/golang/master build

This is an automated PR via build-bot

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ltccci
To complete the pull request process, please assign
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


text:
Edição de vídeo - Vídeo 3 Espanhol

Essa issue é uma continuação da issue #325
O roteiro está aqui
Pasta Drive

vídeo finalizado está nesta pasta

repo: practice-uffs/programa


text:
⚡ Feature | Custom domain

Description
Allow users to host the blog on a custom domain.

Beta version shipped, if you want to try the feature https://docs.sigle.io/ressources/custom-domains

repo: pradel/sigle


text:
Sphinx 5.0 support

https://www.sphinx-doc.org/en/master/changes.html

Looks like I already implemented this a while back?

authors: PerchunPak pradyunsg

repo: pradyunsg/sphinx-basic-ng


text:
feat:added docker support

based on #98

@milton ready for review

:+1:

repo: praekelt/molo-ndoh-yep


text:
update transaction cost calculations

Update the transaction cost calculations to include calculating the cost of the time length of a session.

One more minor comment, otherwise looks good.

:+1: when travis is happy.

Belated :+1:. :)

authors: hodgestar justinvdm rudigiesler

repo: praekelt/vumi-go


text:
Experiment: Add an event reflector

This PR adds a simple event reflector that wraps a nested mom and offers two functions, one to send an event and one to receive one. This can be the basis for a better cross-mom communication (🤔 probably should be named "book club"?).
A reflector is bound to a specific type of event. When sent using the sender function, the event is being reflected back to the nested moms at the point in the hierarchy where the mom got wrapped and can be received by the receiver function. The event flow is isolated from all other events: from events of the same type and even events other reflectors of the same types are communicating with.
The usage is similar to a "scoped" n:n communication channel.

Worked as expected and solved a "real" problem in the IVR project. Merging as soon CI passes.

repo: pragmatrix/Mom


text:
[GSSoC'23]: Add a new tic-tac-toe game to JS Games.

Describe the project you want to add with tech stack
I want to add a tic tac toe game to the JS-games folder. Tech stack: HTML, CSS, JavaScript.
Expected behavior
On starting the game, two players will be able to mark on a 3x3 board alternatively, each having been assigned either X or O. from there on, the winner is decided just as it is expected in a normal Tic-Tac-Toe game. Throughout the game, there wil be a button for restarting and a button for new game after the winner has been decided.
Screenshots (optional)

@pranjay-poddar @Saurabh-kumar09 @0307Vish please assign me this issue

Tic tac toe game is already present

authors: SoarinSkySagar pranjay-poddar

repo: pranjay-poddar/Dev-Geeks


text:
4 Band Resistance Calculator Project added

Title and Issue number
4 Band Resistor Colour code Calculator[GSSoC'23] #4781
Close #4781

Checklist:

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

Screenshots of the Project

Please Assign the respective GSSoC Labels on this PR and issue.

Please assign the respective gssoc labels on the PR and issue so that my score will be counted.
Thank you :)


text:
Implementation for download and upload limits

Hi,
Will be nice if gdrive has the bandwidth limits. The google app already have this feature, see https://support.google.com/drive/answer/2375083?hl=en&ref_topic=6069785 and https://productforums.google.com/forum/#!topic/drive/SUJe8y0oryA
Best regards,
Cleverton

For those that want a workaround to this. On the Linux I'm using throttle and the stdin upload and it works like a charm.
Throttle man : https://linux.die.net/man/1/throttle
and the source : ftp://ftp.fi.freebsd.org/pub/FreeBSD/ports/distfiles/throttle-1.2.tar.gz

This would be great. Unfortunately, @chentz78 suggestion doesn't work for me because I need to download stuff...

repo: prasmussen/gdrive


text:
Sort map keys before converting from Value to Json.

NewValue(map).ToJson(jsn).Bytes() should return JSON string with keys sorted.

JSON is also exposed to users via API. This means JSON Properties may not have its keys sorted.
Would be a good feature to implement:

JSON->JSON with property keys sorted.

JSON->CBOR with property keys sorted.

For Values, JSON property is stored as map[string]interface{}, so no point is sorting it before converting to Value.

For Collate, JSON properties are already sorted :)

repo: prataprc/gson


text:
🛑 QRCode Generator is down

In 1bfd19b, QRCode Generator (https://qrcode-generator.onrender.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: QRCode Generator is back up in 7d253f3 after 5 minutes.

repo: prateekralhan/status


text:
Add a stream for comments on a submission

Describe the solution you'd like

A stream for all comments made to a post.
Toggle-able options such as top level comments only, etc.
However, if we used the current implementation of retrieving comments, trying to stream a large submission would require a lot of calls to replace_more.

I don't think this feature is within PRAW's scope. This can be achieved using a normal comment stream while filtering based on which post the comment is from. Perhaps this would fit in better to prawdditions.

I agree with @jarhill0. PRAW closely mimics functionality available from Reddit's API. Streaming comments by submission is only partially accomplishable by filtering a subreddit stream, which can be easily done by the end user. We could certainly provide an example in our documentation how someone might achieve such a stream.
I'm going to close this issue.

This is basically an issue for #1355 so I will link this issue and re-open it, since a suitable API point was found.

Closing per slack discussion: This will be a prawdditions feature.

authors: PythonCoderAS bboe jarhill0

repo: praw-dev/praw


text:
signals/react: React components rendered as child routes with React Router don't update when using signal.value

Hi there,
I've recently been experimenting with using Signals in React and have discovered a strange behavior when using it in concert with React Router. It seems that when you render a component in a React Router <Outlet> (as a child route), there's something about the interaction between the Outlet and signals that causes the component itself to not actually update.
However, this can be fixed by only referring the signal itself (e.g.
{signal}
 as opposed to
{signal.value}
. If you do that, the component suddenly behaves as expected.
I've created a repo with a small reproduction here: https://github.com/cafreeman/signals-react-weirdness
Please let me know if there's any other information I can provide.
Thanks!

Update: this appears to only happen when using the automatic JSX runtime. If I instead use the classic runtime, the component behaves as expected.

I'm happy to see someone else posted about this. I'm using signals within React Router and either the HMR will crash my page or within a sandbox demo I did, just importing signals into a file will give an error. I've tested importing signals in React non-React-Router projects and they work just fine. I have no clue what Signals does to the React component that alters how React Router handles the routing.

Live Testing

Switching to the JSX "classic" mode didn't help for me,

react-router throws an error if @preact/signals-react is imported to the same project. This is because the preact lib wraps components in a Proxy. When react-router calls this code https://github.com/remix-run/react-router/blob/main/packages/react-router/lib/components.tsx#L572 it errors because the Router type doesn't match the Proxy type.

hello, even i am facing same issue as above, -- Uncaught Error: [Route] is not a  component --
So is there any workaround to resolve this issue?

Hi 👋
I had this same issue with version 1.2.X of @preact/signals-react:
Uncaught Error: [Route] is not a <Route> component. All component children of <Routes> must be a <Route> or <React.Fragment>
    at invariant (history.ts:480:11)
    at components.tsx:593:5
    at react.development.js:1195:17
    at react.development.js:1158:17
    at mapIntoArray (react.development.js:1049:23)
    at mapIntoArray (react.development.js:1099:23)
    at mapChildren (react.development.js:1157:3)
    at Object.forEachChildren [as forEach] (react.development.js:1194:3)
    at createRoutesFromChildren (components.tsx:575:18)
    at Routes (components.tsx:413:20)

But, it seems fixed in version 1.3.X. No more problem using signals, computed or even effect despite the use of a routing (react-router-dom@6.11.0). My code:
import { computed, effect, signal } from "@preact/signals-react";
import ReactDOM from "react-dom/client";
import { BrowserRouter, Link, Navigate, Route, Routes } from "react-router-dom";

const counter = signal(0);
const isEven = computed(() => counter.value % 2 === 0);

effect(() => {
  console.log(isEven.value ? "Even" : "Odd");
});

const increment = () => (counter.value += 1);
const decrement = () => (counter.value -= 1);

function Result() {
  return (

      Value: {counter.value}
      <Link to="/btn-grp">Go To ButtonGroup</Link>

  );
}

function ButtonGroup() {
  return (

        <button onClick={decrement}>-1</button>
        <button onClick={() => (counter.value = 0)}>Reset</button>
        <button onClick={increment}>+1</button>

      <Link to="/result">Go To Result</Link>

  );
}

function App() {
  return (
    <Routes>
      <Route path="/" element={<Navigate to="/result" />} />
      <Route path="/result" element={<Result />} />
      <Route path="/btn-grp" element={<ButtonGroup />} />
    </Routes>
  );
}

const root = ReactDOM.createRoot(document.getElementById("root"));

root.render(
  <BrowserRouter>
    <App />
  </BrowserRouter>
);

Can anyone else confirm?

This might be related to the issue I am having, I too am using React router. If i use a mySignal.value created using the signal() function, exported from a module directly inside my component then my component will re-render on signal updates. But, if i call a function which eventually uses mySignal.value, it won't update on changes. It only works if the signal value was directly used.

@JoviDeCroock Probably it's not actual too, probably it's related with fact only some of high order component have been patched in previous implementation

authors: DmnChzl XantreDev aspizu cafreeman cedeber harshithr jesseagleboy theverything

repo: preactjs/signals


text:
Create uid2.0.md

Adding UID2.0 Docs

@bretg the UID2.0_testpage.md is still a WIP. Prebids UID2 token is not functioning I'm waiting to get a replacement from TTD. The rest of the code could use a second set of eyes, specifically if we want to render a creative.


text:
NGINX 504 Gateway timeout

Hi guys
I'm new to prerender
I just installed prerender on my server EC2 AWS t2.nano (1 CPU 512MB RAM)
I'm getting timeout Gateway
this is the logs
0|server   | 2016-10-31T17:38:24.804Z getting
0|server   | 2016-10-31T17:38:25.409Z getting
0|server   | 2016-10-31T17:38:35.369Z getting http://google.com/
0|server   | 2016-10-31T17:39:46.524Z Terminating worker #1 <-- crashes and restart again
0|server   | 2016-10-31T17:39:46.842Z starting worker thread #0
0|server   | 2016-10-31T17:39:47.032Z starting phantom...
0|server   | 2016-10-31T17:39:47.038Z Server running on port 3000

my configuration in server.js
#!/usr/bin/env node
var prerender = require('./lib');
var server = prerender({
    workers: 1,
    iterations: 40 // i also try to set this to 10 then 0
});

server.use(prerender.sendPrerenderHeader());
// server.use(prerender.basicAuth());
// server.use(prerender.whitelist());
server.use(prerender.blacklist());
// server.use(prerender.logger());
server.use(prerender.removeScriptTags());
server.use(prerender.httpHeaders());
// server.use(prerender.inMemoryHtmlCache());
// server.use(prerender.s3HtmlCache());

server.start();

In NGINX I set the send_timeout, proxy_timeout ... to 6000
I also can see this error in the logs
You have triggered an unhandledRejection, you may have forgotten to catch a Promise rejection:
TypeError: Bad argument
    at TypeError (native)
    at ChildProcess.spawn (internal/child_process.js:289:26)
    at Object.exports.spawn (child_process.js:380:9)
    at /home/centos/apps/prerender/node_modules/phridge/lib/spawn.js:102:38
    at startPhantom (/home/centos/apps/prerender/node_modules/phridge/lib/spawn.js:72:20)

How can I fix this issue
I'm using Node 6.9.1
I also tested with Node 4.6.1
I'm using Node 0.12.x

unhandledRejection is gone now after using Node 0.12.x
However it stills timing out

I also tested without using NGINX just using http://myserver.com:3000/http://google.com and it also timeout

Hi @benishak. A t2.nano might be too underpowered for running Prerender.
I'd also suggest putting your proxy_timeout higher to something like 20 seconds. I don't know how long your pages take to load, but you'll want to make sure the Prerender server has enough time to render your pages.
As for that error, are you seeing that when loading a page or is that error happening on startup? I haven't seen that error yet in Node v4 or v6.
You aren't passing any custom PhantomJS parameters?

when I check the load using top or pm2 monit I see 0% CPU usage for prerender process.
I even tried without NGINX just connecting directly to prerender NodeJS and still timing out. PhantomJS worker crashes and process restart.
I only saw that error on startup, only with Node 4.6.1 or 6.9.1
No i'm not passing any parameters

Im using last version of PhantomJS 2 , couldn't be the reason?
I install phantomjs binaries manually before runinng npm install,

Running npm install will install the correct PhantomJS version for you. That might be the reason. What happens when you just run npm install without already installing PhantomJS?

I got this error https://github.com/Medium/phantomjs/issues/344
I tried to fix it and only installing phantomjs manually solved the problem ....

Which error exactly? There are multiple errors there. Are you running your t2.nano with Windows?

this
https://cloud.githubusercontent.com/assets/12117128/7779940/223dd7f8-008e-11e5-9b28-b9e91d315a0b.PNG

no im using Centos7

Why is it trying to install PhantomJS 1.9.17? Which version of Prerender are you using?
Also why does it think you are on Windows NT?
It looks like it has you using Node v0.10.35. Can you upgrade to at least Node v4?

no that error is not from my screen but it is the same error, ignore windows and the other details.
the error is
Failed at the phantomjs-rebuild@2.... install script 'npm install.js'

Can you post the full error you are receiving? I'll need to see the full error to help diagnose the issue.

I removed the PhantomJS I manually install then I removed the node_module directory then I run npm install and didn't get that error
Then I realized why I got that error before is I didn't have bzip2 installed and I install it when I install PhantomJS manually ...
Now prerender works without timeout
0|server   | 2016-11-02T15:06:41.160Z getting http://google.com
0|server   | 2016-11-02T15:06:41.190Z + 1 http://google.com
0|server   | 2016-11-02T15:06:41.979Z - 0 http://google.com
0|server   | 2016-11-02T15:06:41.982Z + 1 http://google.com
0|server   | 2016-11-02T15:06:42.101Z got 301 in 941ms for http://google.com

So for everybody before running npm install make sure you have bzip2 installed!

But I don't know why it do 301 redirection, i also tested on google.com

because http://google.com will redirect to https://www.google.com
Glad you figured it out.

authors: benishak thoop

repo: prerender/prerender


text:
Is there a way to start chrome that preserves the chrome cache?

Thanks all for the great software
I notice from other threads that each request opens a new tab like if it were in incognito. The problem is that this wont preserve the cache and will hit my CDN for each javascript & css files (higher expense). Is there a way to start pre-render that it preserves the website cache so that each file doesn't have to be re-downloaded?

This is by design since we open separate incognito contexts for each request to prevent cookies, local storage, etc from bleeding over. It would be nice to somehow share the cache between tabs but would require some work to put together, especially sharing a cache between different servers in a cluster.
Are you just worried about the higher costs from your CDN or is your rendering too slow with those extra requests to the CDN?

@Yoshi9143 how about this: https://forums.meteor.com/t/server-side-rendering-for-seo-improvement/42327/3

I think this could be built as a plugin or something to add to Prerender/chrome but isn't currently a priority here. If anyone comes up with something in the future please let us know.

authors: Yoshi9143 paulincai thoop


text:
Create new tab to show rectangles in a 2D space with arrows in between

Fixes #164

There are still some issues to be fixed with this:

Allow resizing of the canvas
Arrows change of anchor position too soon when dragging an element from a bottom position to the left.

Shall we extract issues for these?

Resizing of arrow calculation has been fixed, positioning the blocks is not. This is more complicated sadly. The arrows could be improved, but let's move that to a new issue.

Very good, I'll extract some issues

authors: TimvdLippe txsmith

repo: preview-code/rite-evaluation


text:
OperationFailure: WiredTigerIndex::insert: key too large to index

Traceback (most recent call last):
  File "/home/usom/.local/lib/python2.7/site-packages/gevent/greenlet.py", line 536, in run
    result = self._run(*self.args, **self.kwargs)
  File "/home/usom/.local/lib/python2.7/site-packages/mrq/worker.py", line 166, in greenlet_scheduler
    scheduler.sync_tasks(self.config.get("scheduler_tasks") or [])
  File "/home/usom/.local/lib/python2.7/site-packages/mrq/scheduler.py", line 56, in sync_tasks
    self.collection.find_one_and_update({"hash": task["hash"]}, {"$set": task}, upsert=True)
  File "/home/usom/.local/lib/python2.7/site-packages/mrq/monkey.py", line 99, in mrq_monkey_patched
    ret = base_method(self, *args, **kwargs)
  File "/home/usom/.local/lib/python2.7/site-packages/pymongo/collection.py", line 2422, in find_one_and_update
    sort, upsert, return_document, **kwargs)
  File "/home/usom/.local/lib/python2.7/site-packages/pymongo/collection.py", line 2198, in __find_and_modify
    collation=collation)
  File "/home/usom/.local/lib/python2.7/site-packages/pymongo/collection.py", line 232, in _command
    collation=collation)
  File "/home/usom/.local/lib/python2.7/site-packages/pymongo/pool.py", line 419, in command
    collation=collation)
  File "/home/usom/.local/lib/python2.7/site-packages/pymongo/network.py", line 116, in command
    parse_write_concern_error=parse_write_concern_error)
  File "/home/usom/.local/lib/python2.7/site-packages/pymongo/helpers.py", line 210, in _check_command_response
    raise OperationFailure(msg % errmsg, code, response)
OperationFailure: WiredTigerIndex::insert: key too large to index, failing  50510

I am trying to create a scheduler task which obtains a large dict of params and getting this error when I start a worker. As far as I can see this is because of indexing limitations of mongodb. Is there a workaround for that? If there is not, can you provide a fix or I can patch the code if you lead me the way.

Hi!
This is indeed a design limitation.
If you are configuring your task to be scheduled I guess your big dict of parameters is relatively static? Can't you just pass a smaller identifier for it to the task?
In general, task parameters should be as small as possible.

Task parameters are configurable from a user interface. User can add thousands of entries for just one task if s/he wishes to. I have tried to pickle and encode the parameters to shrink the size and decode-unpickle at job body but that doesn't give much benefit.
I have come up with a temporary solution. I am setting failIndexKeyTooLong parameter of mongodb to false . I think job is not indexed but I can still find it writing a query. I hope it does not create a problem in future.
Thank you for your help.

I think the real solution would be to store those parameters in a separate database, get an ID for each set of them, and then just pass that single ID to the task. But it's up to you!
Best,

authors: functure sylvinus

repo: pricingassistant/mrq


text:
OmniFaces/PrimeFaces Namespaces

Allow this plugin to support both namespace URL and URN.
http://omnifaces.org/ui --> omnifaces.ui
http://omnifaces.org/functions --> omnifaces.functions
xmlns:p="http://primefaces.org/ui" --> xmlns:p="primefaces"
xmlns:pe="http://primefaces.org/ui/extensions" --> xmlns:pe="primefaces.extensions"

We should add a separate issue to add Omnifaces functions if it's not already there

Well i think i tried to add functions but since they are EL expressions there is nothing to AutoComplete

authors: FlipWarthog melloware


text:
About AVSPEECH dataset

full AVSPEECH dataset is roughly about 1500 GB, too large to download；and would you like to share your own with me? Thanks a lot.

My organization downloaded it, so I don't have permission to share it. Thanks


text:
Don’t indicate neutral status with 'exit 78'

This was removed in Actions v2: https://twitter.com/ethomson/status/1163899559279497217?s=20

This is great, thanks! I would also vote to bump the version to 2.0.0, since this is kind of a breaking change... and lines up with Actions v2?

Makes sense to me! 👍 Bumped the version in https://github.com/primer/publish/pull/22/commits/b24b926a7611f855a3b9db21946dcda8c21e7d25.

repo: primer/publish


text:
Breadcrumbs should support as prop and custom label

Breadcrumbs always renders as .... This is not ideal because nav creates a navigation landmark, and landmark roles should be used sparingly to avoid cluttering the screen reader navigation tools. And each instance of a landmark role should have a unique label, so there is currently no way to use multiple instances of the component on the same page.
As an example, you might have navigation menu that includes breadcrumbs along with a 'Home' link. In this case, you would want to include 'Home' inside the navigation landmark, so you might do something like:

  Home
  <Breadcrumbs>...</Breadcrumbs>

This would result in semantically invalid HTML - a nav inside of a nav. In this case, it would be useful to render the breadcrumbs without the navigation role, like:

  Home
  <Breadcrumbs as="div" role="group">...</Breadcrumbs>

But the as and role props are not allowed on this component.
Another example might be to use Breadcrumbs as a top-level site-wide navigation but also want another instance of the component to use for navigating within a source code view. In this case the second instance should not be a nav and/or should have a different label than "Breadcrumbs".

Hi @iansan5653 👋 Thanks for the report! Can you please share some more detail with us about the specific use case you have where you're running into a need for a Home anchor beside a Breadcrumbs component as opposed to inside of it?
A potential action item we might take here is to allow customizability for the aria-label value (e.g., don't hardcode aria-label="Breadcrumbs"), but would love to learn more about the use case first.

repo: primer/react


text:
About supervised SimCSE

Hi,
I would like to check if I want to get my own three sentences pair could I generator from two contrast sentences? (x,x,x-)
In this case, my understanding is that simCSE still works.
Best

Hi,
Yes, this should still work with SimCSE.

@gaotianyu1350 If I just have two sentences  pari and its label which mean the pair same or not~ In the other way, I do not have hard_ne, how can I format the data for training supervised-SimCSE? Thanks a lot~

authors: MrRace cordeliazhu gaotianyu1350

repo: princeton-nlp/SimCSE


text:
Ability to use Heroku's pgbouncer

Heroku has a pgbouncer that is one line to install (https://devcenter.heroku.com/articles/postgres-connection-pooling).
Currently its options do not seem to line up 100% with the requirements of prisma and it isn't possible to change them.
server_reset_query = DISCARD ALL
 server_reset_query_always = 0

When running we see errors like the following:
2020-04-02T17:29:11+00:00 app[postgres.13791]: [AMBER] [11-1]  sql_error_code = 42P05 ERROR:  prepared statement "s3" already exists
2020-04-02T17:29:11+00:00 app[postgres.13791]: [AMBER] [11-2]  sql_error_code = 42P05 STATEMENT:  UPDATE "public"."Log" SET "ownerId" = $1, "type" = $2, "id" = $3, "updatedAt" = $4, "createdAt" = $5, "date" = $6 WHERE "public"."Log"."id" IN ($7)

Not sure if this would be possible to support, but it would be nice to use this vs. setting up and running our own instance of pgbouncer if at all possible!

You cannot run Prisma without setting the options correctly with pgBouncer.

I made a fix for Heroku
https://github.com/heroku/heroku-buildpack-pgbouncer/pull/129
But they haven't even looked at my pull request...
Maybe try to use the patched buildpack?

ok, I'll look into it. Our app itself isn't hosted on Heroku, just our DB is so I would need to find some way to send the modified database url to our app. Not sure if that is possible. I might also need to host our own copy of pgbouncer, but I'm also not sure how to do that :D

We implemented a new PgBouncer mode in https://github.com/prisma/prisma/issues/2520 that is activated by adding ?pgbouncer=true (or &pgbouncer=true of course) to your connection string. Available in the current alpha, and the next normal beta release 🚀
We will now try to test this with Heroku in our e2e tests to make sure this indeed works and will keep working long term: https://github.com/prisma/e2e-tests/issues/385
If you try it out yourself @chrisdrackett, let us know if it works or not - until then we assume it does ;)

@janpio We already moved our server to Heroku from next so this no longer applies to us ;)

We'll have to find someone else to test this then :D

authors: chrisdrackett janpio pimeys

repo: prisma/prisma-client-js


text:
Use Object.freeze to generate enum

To add more runtime safety Object.freeze could be used to wrap around the generate const for the enum types from the schemas. For example,
export const AddressType = {
  BILLING: 'BILLING'
};

function makeEnum(x) {
    return Object.freeze(x);
}

export const AddressType = makeEnum({
  BILLING: 'BILLING'
});

This just adds another layer of security and immutability, which are known to prevent some many fallbacks of state changes

isnt this like using as const in TS? would make implementing this easier

What is the motivation behind this? In which situation would you say there is a risk that not doing that poses a potential problem?

authors: deviprsd janpio sakgoyal

repo: prisma/prisma


text:
Getting error on deeper includes

I am getting this error on Preview 23 that worked on Preview 21
Error:
Expected at most 1 item for 'timetable', got 2

Query:
  const data = await prisma.passenger.findMany({
    include: {
      booking: {
        include: {
          timetable: true
        }
      }
    }
  });

Might help while reproducing, this error and another one complaining about a missing FROM caause seem to happen once the includes get nested. So
...,
include: { posts: true },

works fine,, whereas
...,
include: { posts: { include: { tags: true } } } },

will crash reliably

+1 I am also seeing the missing FROM-clause error when trying to include a field that is part of a M-N relation. It was working fine in preview022

@malekjaroslav I was unable to reproduce this. I used Preview 24 Maybe it is reproducible with the data that you have in your database. Can share a SQL dump of your database? If you like we can sign an NDA if you are not comfortable sharing it here.
If someone else can provide a more minimal reproduction, it would be quite helpful.

@pantharshit00 Here is the dump. It still happens even on Preview 24. After you import the tables, call this query: dump-issue-1785.gz
 const passenger = await prisma.passenger.findMany({
            where: {
                booking: {
                    bookingStatusLogs: {
                        some: {
                            status: "CONFIRMED"
                        }
                    },
                    timetable: {
                        id: "ck7r8b65w0023llb31i581ncg"
                    }
                }
            },
            include: {
                booking: {
                    include: {
                        timetable: true
                    }
                },
                passengerStatusLogs: {
                    orderBy: {
                        createdAt: "desc"
                    },
                    first: 1
                }
            }
        })

I'm having the issue too that came up after an upgrade, and was able to narrow down at least what is causing this issue. The stripped down version of my relational model:
model TimeEntry {
  id            String     @default(cuid()) @id
  trip          Trip
  startTime     DateTime
  updatedAt     DateTime   @updatedAt
  createdAt     DateTime   @default(now())
  ...Other Fields
}

model Trip {
  id              String     @default(cuid()) @id
  route           Route
  name            String
  ...Other Fields
}

model Route {
  id           String       @default(cuid()) @id
  trips        Trip[]
  name         String
  ...Other Fields
}

A Route can have a bunch of Trips, where in this case a truck driver creates a time Entry that links to a Trip which would have info such as where they started, ended, times, etc. The query I make is:
const data = await db.timeEntry.findMany({
  where: {
    // some where clause
  },
  include: {
    trip: {
      include: {
        route: true,
      },
    },
  },
})

The problem lies in if I get multiple TimeEntries that have the same trip. It will error when it then tries to get the routes because it is the same Route. So if i just {include: { trip: true} } all is well. Or if I happen to call a data set where the TimeEntires are all different Trips, it works. (which would be why an empty data set would be successful) Now i'm not sure if the createdAt or updatedAt or startTime fields come into play. I was able to narrow down the query by filtering and shrinking the startTime interval until i got a small enough dataset to visually parse through and see what was going on.
I hope thats helpful and not super confusing. Its hard to explain just over text.
happy to clarify anything if needed.

@pantharshit00 Do you have some update on this? It is quite a big issue. Thanks!

Can confirm this breaks.

Smaller client call to reproduce this:
  const data = await prisma.passenger.findMany({
    include: {
      booking: {
        include: {
          timetable: true
        }
      }
    }
  });

Data used from the dump above

+1 I am also seeing the missing FROM-clause error when trying to include a field that is part of a M-N relation. It was working fine in preview022

Same here, anything after 21 breaks.

Guys, have you found any workarounds? The new release from today has so many new cool things I could use but I’m already stuck at v21 with 5 versions behind. Thanks!

@tomitrescak There is no good workaround other than making multiple queries or using raw method.

Latest alpha should contain a fix for the issue. Please verify that it works for you.

I just tried 2.0.0-alpha.1013 and I'm still getting this same error when running Prisma studio.
Here is what I get
Error in request:  {
  telemetry: true,
  message: '\n' +
    'Invalid `prisma.activity.findMany()` invocation:\n' +
    '\n' +
    "Expected at most 1 item for 'branch', got 58",
  stack: 'Error: \n' +
    'Invalid `prisma.activity.findMany()` invocation:\n' +
    '\n' +
    "Expected at most 1 item for 'branch', got 58\n" +
    '    at PrismaClientFetcher.request (/Users/josh/.cache/prisma/studio/Users-josh-Dev-prisma-examples-javascript-rest-nextjs/runtime/index.js:1:51485)\n' +
    '    at processTicksAndRejections (internal/process/task_queues.js:93:5)',
  isPanic: undefined,
  code: undefined
} {
  query: 'prisma.activity.findMany({\n' +
    '  first: 100,\n' +
    '  select: {\n' +
    '    branch: true,\n' +
    '  }\n' +
    '})'
}

Here is the relevant schema section
model Activity {
  branch Branch? @relation("ActivityBranch", references: [id])
  id String @default(cuid()) @id
}
model Branch {
  activity Activity[] @relation("ActivityBranch")
  id String @default(cuid()) @id
}

You miss the scalar field of the relation and the field definition. The validator merged today will not pass your datamodel anymore.

Ok, I made that change, but now prisma migrate wants to drop tables that have data. I'm just starting to try to migrate from Prisma 1.

Maybe introspect the database with the beta1 or the latest alpha. Migrate is still experimental.

@pimeys Thank you.  That got me a bit further, I will now have to wait for this issue before proceeding.
https://github.com/prisma/prisma/issues/1996

FWIW I was able to get up and running with 2.0.0-beta.1 and still have the same issue. Expected at most 1 item for 'route', got 11

FWIW I was able to get up and running with 2.0.0-beta.1 and still have the same issue. Expected at most 1 item for 'route', got 11

@RussMax783 the fix was merged in alpha after beta1 release, not in the beta release

Ah, Should have checked that. I just installed @latest. Anyways, installed the alpha and ran a couple queries that I knew would break and they now work!  Nice work!!

I think I still have this issue using beta.2. Was the fix included?
    let user = await ctx.prisma.auth0User
      .findOne({
        where: { auth0Id: auth0Id },
      })
      .user();

model User {
  id         String      @default(cuid()) @id
  auth0Users Auth0User[] @relation(references: [id])
  email      String      @unique
  username   String      @unique
  name       String
}

model Auth0User {
  id      String @default(cuid()) @id
  auth0Id String @unique
  user    User   @relation(fields: [userId], references: [id])
  userId  String @map("user")
}

Problem seems to be with the secondary/sub query:
SELECT "public"."User"."id", "public"."User"."email", "public"."User"."username", "public"."User"."name" FROM "public"."User" WHERE () IN (($1)) OFFSET $2

Specifically WHERE () should have a field I think?

You datamodel is invalid, auth0Users field should not provide any relation sirective as it is virtual. Here is the correct model:
model User {
  id         String      @default(cuid()) @id
  auth0Users Auth0User[]
  email      String      @unique
  username   String      @unique
  name       String
}

model Auth0User {
  id      String @default(cuid()) @id
  auth0Id String @unique
  user    User   @relation(fields: [userId], references: [id])
  userId  String @map("user")
}

Current alpha will give you a validation error for this.

authors: RussMax783 c316 dpetrick homerjam luhagel malekjaroslav narciero pantharshit00 pimeys tomitrescak


text:
run introspection-engine.exe directly exit #17985

Bug description
1: download introspect-engine
https://binaries.prisma.sh/all_commits/11e97a060a6eaa5ca0b29f3b612466b33fab1a21/windows/introspection-engine.exe.gz
2: os
win10 amd64
3: exe directly exit, no blocking

How to reproduce
exe directly exit, no blocking

Expected behavior
blocking
Prisma information
directly run engine.exe
Environment & setup

OS:windows

Prisma Version

Your screenshot tries you to run a query engine, while your instructions show you downloading an introspection engine.
Even with that fixed, the engines are not meant to be run directly, but via Prisma Client and CLI.
What are you trying to do?
If you really see no other way, look at how the CLI and Client use the engines to figure out their API (which is not public and can change without notice).

because prisma do not have golang sdk. So, we use os.exec  package in golang to wrap introspection engine and query engin. then, wen can use introsecpion or query directive in our project. Do you have some ideas about this, because we want to use golang to implment introspect and query directive.

maybe you mean i can use goland to wrap prisma cli?

i use 'npm install -g prisma' install prisma, and still meet err

Are you aware of https://github.com/prisma/prisma-client-go?
The screenshot you shared and the error report unfortuantely do not include any helpful information.
What output do you get when you run prisma -v?

@janpio i run prisma -v

Oookay. Here is the solution to your problem: https://github.com/prisma/prisma/issues/9975#issuecomment-952944479

Oookay. Here is the solution to your problem: #9975 (comment)

cool

Did it work? Is the problem resolved?

yes, thx.


text:
Support for TLS v1.3

Note that I haven't confirmed that TLS v1.3 is unsupported in the most recent version but it was confirmed to not be supported in April.
Additional context

Some Prisma Client Python users are asking for this.

I can confirm that Prisma 5.20 still does not support TLS v1.3.  I get the same error:
P1011: Error opening a TLS connection:.
I'm using the Prisma client for Node/Typescript.
Also, since Neon database, now ONLY support TLS v1.3, Prisma Client is broken for Neon DB.
([ prisma migrate dev --name dbinit ] command is broken when connecting to Neon DB.


text:
findFirst and findUnique do not return null according to types

Bug description

I have a user entity where the findFirst and findUnique always returns the entity and never null.
How to reproduce
Steps to reproduce the behavior:

Clone https://github.com/hgezim/prisma-error-find
Open src/user/user.service.ts
findOrCreate has return type of Promise<User>
TypeScript throw no errors

Expected behavior
TypeScript should throw an error since the function returns the results of userOne() or userUnique() which both
can have no results. However, that's not what the prisma client types say:

Prisma information

async findOrCreate(data: Prisma.UserCreateInput): Promise<User> {
    const userUnique = await this.prisma.user.findUnique({
      where: { facebookId: data.facebookId },
    });

    const userOne = await this.prisma.user.findFirst({
      where: { facebookId: data.facebookId },
    });

    return userUnique || userOne;
  }

Environment & setup

OS: Mac OS
Database: SQLite
Node.js version: v12.20.0
Prisma version:

@prisma/cli@2.13.1
@prisma/client@2.13.1

You should set strict: true in your tsconfig.json

Indeed, nice catch by @oceandrama
Either enable strictNullChecks or strict (which implicitly enables strictNullChecks and other good TS options). Then you will get a TS error like so:

authors: hgezim oceandrama pantharshit00


text:
Getting lots of errors in node_modules/.prisma/client/index.d.ts after upgrading to 2.17

Bug description
After upgrading to 2.17 I am suddenly seeing a lot of errors in node_modules/.prisma/client/index.d.ts and my nest js build step is failing. Here are a few screenshots.
I tried rebuilding prisma, also deleted node_modules, cleared npm cache and tried rebuilding the whole thing but still getting errors both in local as well as Docker build.

How to reproduce
Not sure. Can share my schema file and generated ts file on Slack.

Prisma information

Environment & setup

OS: MacOS Catalina 10.15.1, Running inside docker node:14.15.4-alpine
Database: PostgreSQL
Node.js version: v14.15.4
Prisma version:

prisma               : 2.17.0
@prisma/client       : 2.17.0
Current platform     : linux-musl
Query Engine         : query-engine 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at node_modules/@prisma/engines/query-engine-linux-musl)
Migration Engine     : migration-engine-cli 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at node_modules/@prisma/engines/migration-engine-linux-musl)
Introspection Engine : introspection-core 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at node_modules/@prisma/engines/introspection-engine-linux-musl)
Format Binary        : prisma-fmt 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at node_modules/@prisma/engines/prisma-fmt-linux-musl)
Studio               : 0.353.0
Preview Features     : createMany

Originally posted in public Slack

From Slack
Looks like I have found the issue. Reverting to old version helped fixed the issue.
Here is the difference between generated types in 2.16 vs 2.17.
2.16
export type payroll_kw_wallet_transactionsTypeSourceInvoice_idStatusCompoundUniqueInput = {
    type: payroll_kw_wallet_transactions_types
    source: payroll_kw_wallet_transaction_source
    invoice_id: string
    status: payroll_transaction_status
}
2.17
export type payroll_kw_wallet_transactionsPayroll_kw_wallet_transactions.type_source_invoice_id_status_unCompoundUniqueInput = {
    type: payroll_kw_wallet_transactions_types
    source: payroll_kw_wallet_transaction_source
    invoice_id: string
    status: payroll_transaction_status
}
Look at the difference in the names. Typescript isn't allowing . in the type name and hence the issue. (edited)

Just one more update so that it helps you debug the issue. This doesn't look to be an issue with Prisma version. The problem was that I introspected my schema just to make it in sync with existing DB. So in my schema the unique constraints got changed from @@unique([type, source, invoice_id, status]) to @@unique([type, source, invoice_id, status], name: "payroll_kw_wallet_transactions.type_source_invoice_id_status_un")  which on being generated by Prisma is leading to this incorrect type naming issue in both the versions. This was the reason reverting only the version earlier didn't help.
Please let me know when a fix is available. For now I will remove the naming from my schema.

Also this is only happening with compound unique constraints. Single unique constraints seem to be working fine even with . in the name

Thanks for the details. Through lots of discussion, we realized this wasn't actually a regression between 2.15 and 2.16, but actually an outstanding bug. We have a couple possible solutions being tracked here: https://github.com/prisma/prisma/issues/3193


text:
Support for CockroachDB serverless

Problem
As it stands Prisma ignores the options parameter that is in CockroachDB's connection string for their serverless/cloud plans this value indicates which cluster to connect to. Without this value you'll recieve a connection error.
Valid values for the options paramter for cockroach is:
options=--cluster=%3Dmy-cluster-name
or:
options=-c%3Dmy-cluster-name

This is documented here: https://www.cockroachlabs.com/docs/stable/connection-parameters.html#supported-options-parameters
A connection string will look similar to this:
postgresql://{{USER}}:{{PASS}}@{{HOST}}:{{PORT}}/defaultdb?options=--cluster%3D{{CLUSTER_NAME}}

Suggested solution
Support the options parameter in the postgres connection string.
Additional context
I receive the following error:
Database connection error:

undefined: Database error
Error querying the database: db error: FATAL: codeParamsRoutingFailed: missing cluster name in connection string

All that being said, the cluster name in the connection string can be worked around:

To construct a suitable connection string, open the cluster in the CockroachCloud, click the Connect button on the rop right to open the Connection info modal. There go to the Connection parameters tab and construct a connection string with these values.

https://github.com/prisma/e2e-tests/pull/1597/files#diff-3ff81f6c96e193d32a22f6cea59f0e08e0f4609c685d3e0c8f2bd0346e8abd49R7
That way should be able to connect to the database. Let me know if that works @ashsmith

@ashsmith @otan Can you please confirm that using the individual Connection parameters allows you to proceed further? Thanks.

@janpio No. I can confirm that the issue @otan reported remains. I still got the following error message
Error: db error: ERROR: unknown function: pg_get_functiondef()
   0: migration_core::api::SchemaPush
             at migration-engine/core/src/api.rs:184

@alvis You just confirmed that you could actually connect to the server using the Connection Parameters from the Cockroach UI (vs. the Error querying the database: db error: FATAL: codeParamsRoutingFailed: missing cluster name in connection string error message that @ashsmith initially got), and that you are now getting the expected error message when using db push (or another Migrate command) which is an overall problem with CockroachDB and Prisma. We will work on that via https://github.com/prisma/prisma/issues/4702
(Maybe post your current error message and the command you are trying to run in that issue so the current state is reflected there. Thanks!)

@janpio Thanks for your quick feedback. Yes. You're right that I got the error from prisma db push. The error does indicate that prisma can connect to the database, but it hits a problem that cockroachdb lacks pg_get_functiondef for getting info about user-defined functions.

"Yes", but it is quite an effort: You can use db push (or any other Prisma Migrate command) with a Postgres database, then download the SQL to create the database manually (or take it from the generated migration files) and use it on your CockroachDB server - the end result should be the same. The problem is just in Introspection and internal assumption of Migrations that do not work on CockroachDB.

For posterity, I've put an issue up on our side detailing what needs to change in either prisma and/or Cockroach to get migrate working: https://github.com/cockroachdb/cockroach/issues/73137
We'll make it work together one day :)!

Follow up issue: https://github.com/prisma/prisma/issues/10494

Update: In recent dev versions of Prisma CLI the connection string com CockroachDB Cloud Serverless can just be copy pasted into Prisma and works. No additional work is need any more. This will be released with 3.8.0.

authors: alvis ashsmith janpio otan


text:
Specify types and arguments on databases that support it

Feature Request
What feature are you missing?
There isn't a way to specify the string length (or type) on a string field for databases that support it.
https://www.prisma.io/forum/t/is-there-a-way-to-add-a-length-to-string-varchar/3546/2
Also, it might be beneficial to allow the type (CHAR or VARCHAR) to be specified or the arguments used for any of the other data types like INT
https://dev.mysql.com/doc/refman/5.7/en/create-table.html
How could this feature look like in detail? Tradeoffs?
Either we should add these arguments to the GraphQL type (i.e. String should allow the length argument) if that is even possible, if not, perhaps there should be some "easy" way to specify new primitive types? Like perhaps I could define a new String type that is of database type CHAR(20)?
The tradeoff would be that it cannot be assumed that a String is of the same length for the same field, but I think being able to extend the primitives would aliviate that (and would allow a place to document the restrictions).

Any update on this? Is it possible to specify string field length

I'm interested in this too.
Also wondering...aren't there performance implications to storing all strings as a "mediumtext" column in mysql? (as opposed to designing tables as varchars to match the expected data lengths)

I'd also need this feature. Currently, we always have to check for a specific maximum length inside of our resolvers, this would make all of this logic obsolete, which would be very nice!

+1

+1

+1

+1

+1

+1

+1

+1

+1

authors: Lohann MohamedElmdary VulgarnyKarlson affanshahid carstenbaumhoegger cmdshepard davidbarratt hoffnung8493 jhaemin kokokenada lucasferreiralsf mikepuglisi mukhlim


text:
Add watchman to installation instructions

Without it, the GraphQL language server complains that it is missing.

Thank you @borekb for this PR 🙌

authors: borekb divyenduz

repo: prisma/vscode-graphql


text:
Looped Cascade Directive when parent and child are of same object.

Bug Report
Current behavior
Consider the folowing data type:
type Folder @model {
  id: ID! @unique
  parent: Folder @relation(name: "FolderOnFolder", onDelete: SET_NULL)
  children: [Folder!]! @relation(name: "FolderOnFolder", onDelete: CASCADE)
}

This seems reasonable. A folder will cascade its deletes down the tree, but only set null up the tree.
This causes an error:
{
  "data": {
    "deleteFolder":null
  },
  "errors": [
    {
      "message":
        "There was a loop in the path generated by the onDelete: Cascade directives on your schema when trying to do the delete.",
      "locations":[],
      "path":["deleteFolder"],
      "code":3043,
      "requestId":"api:api:cjeh2wc500055016429dfdckw"
    }
  ]
}

Reproduction
This seems to be the case in any situation in which an object has a parent/child of its own data type.
Expected behavior?
Behavior like one would expect from a folder.

I can confirm this bug.
It seems like the recursive CASCADE is correct detected as a loop, but I don't see why that shouldn't be allowed.

+1

@marktani Any update on this?

still stucked on this

Same

Same

+1

Hi,
I was facing the same issue and solved it by declaring children relation before parent relation:
# This will generate error
type Folder @model {
  id: ID! @unique
  parent: Folder @relation(name: "FolderOnFolder", onDelete: SET_NULL)
  children: [Folder!]! @relation(name: "FolderOnFolder", onDelete: CASCADE)
}
# This wont generate error
type Folder @model {
  id: ID! @unique
  children: [Folder!]! @relation(name: "FolderOnFolder", onDelete: CASCADE)
  parent: Folder @relation(name: "FolderOnFolder", onDelete: SET_NULL)
}

Hope it helps! :)

prisma 1.17.1
Changing the order fixed the issue for me too.

We just released an update that fixes this bug. We were also able to remove most of the restrictions around cascading deletes. So looping is not checked for anymore.

authors: Aubron Kisepro LuHugo do4gr harrisrobin marktani seagram sejr valentinbe wuzhuzhu

repo: prismagraphql/prisma


text:
fix: introspection input - don't ask for schemaName when no data

Fixes https://github.com/prismagraphql/prisma/issues/2413

It turned out that this case is already handled by https://github.com/divyenduz/prisma/blob/01bda96f627fc0a48a5167256f881c8dd521ae0e/cli/packages/prisma-cli-core/src/utils/EndpointDialog.ts#L382-L386

authors: divyenduz timsuchanek


text:
fix cfOrVm prompt

Description
Expected behavior:
When setting up a ceremony for a circuit with >1M constraints, the CLI automatically chooses VM verification and promps the user to select and instance type.
Actual behavior:
When setting up a ceremony for a circuit with >1M constraints, the CLI automatically chooses CF verification
The reason this occurs was because we assume cfOrVM is a boolean when it's actually a string in the case that enforceVm is true. Since the string is truthy, the CLI sets it to CF verification instead of VM verification.
Checklist:

[X] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[X] Any dependent changes have been merged and published in downstream modules
[X] I reviewed the code of conduct and contributors' guide

@ctrlc03 I believe this fixes #191


text:
✨ Feature Suggestion | Analytics

Description
Include a list of privacy respecting alternatives to Google Analytics for web developers to replace with. Could be put under "Provider" section.
I have gathered a possible list of products to put there:
Plausible Analytics
Goat Counter
Simple Analytics
Keep It Simple Stupid Stats

Potentially duplicate of https://github.com/privacytools/privacytools.io/issues/1186

Potentially duplicate of https://github.com/privacytools/privacytools.io/issues/1186

I don't think that this is within the scope of the site. I'm closing this, but if anyone from @privacytools/editorial wants to reopen it thats fine.

I don't think that this is within the scope of the site. I'm closing this, but if anyone from @privacytools/editorial wants to reopen it thats fine.

authors: Domant3lis Mikaela freddy-m


text:
fix issue 506 - test-latest-20

fix https://github.com/privatenumber/tsx/issues/506

Closed via https://github.com/privatenumber/tsx/pull/518

authors: cenfun privatenumber

repo: privatenumber/tsx


text:
Blender crash if trying to open a while while IPR

If you are rendering in IPR and try to open another file Blender will crash

OK, I can reproduce this 2.83.16 and 2.92, but with our dev build running 2.93, I'm not getting a crash, so seems like this was a problem on the Blender side.
I'll keep this issue open, but please let us know if you still get this when RenderMan 24.1 ships using Blender 2.93.

authors: prman-pixar riouxr

repo: prman-pixar/RenderManForBlender


text:
Allow custom log function to be provided

Currently this library logs using console methods.
We're using structured logging in JSON using a library (Pino but that's not relevant here) in all of our applications, including AWS Lambda functions. Using this library currently results in unstructured log statements in our log aggregation which makes queries difficult.
I'd suggest adding a logger parameter to an options object and then calling that instead of console, defaulting to console if none is provided.
e.g.
serverless(handler, {logger});

where logger has the same interface as console.

This will be possible via https://github.com/probot/adapter-aws-lambda-serverless/pull/59
const { createLambdaFunction, createProbot } = require("@probot/adapter-aws-lambda-serverless");
const appFn = require("./");

module.exports.webhooks = createLambdaFunction(appFn, {
  probot: createProbot({
    defaults: {
      log: logger
    }
  })
});

Also with Probot v11, Probot itself is using pino, too :) We created a custom transport: https://github.com/probot/pino/

repo: probot/adapter-aws-lambda-serverless

license: ISC


text:
Missing types for other packages used by Probot

Bug Report
Current Behavior
All TypeScript types located in src/@types/ are missing from final build, and any used as they are marked as devDependencies and cause errors when using Probot in a TS application
// Your code here
import { Application } from 'probot';
export = (app: Application) => {
  app.log('There is a bug')
}

Expected behavior/code
For the npm module to have the required types, and the package.json list the @types/* packages in dependencies
Environment

Probot version(s): [e.g. v6.0.0] any version written in TS
Node/npm version: [e.g. Node 8/npm 5] Node 10
OS: [e.g. OSX 10.13.4, Windows 10] Windows 10

Possible Solution
Add a script to copy those files to the final output folder and mark the required @types/* packages as dependencies
Additional context/Screenshots
Encompases #675

Not stale

Would this be fixed if we add the src/@types folder to
https://github.com/probot/probot/blob/bcc3203930e47385fb997f247b5a5bf1bc84b6b0/package.json#L20-L25
An alternative would be to list the @types in dependencies with a relative path instead of a version as the value. But I think we’ll have to add package.json files in order to make that work?

Yes, that could work

From: Gregor Martynus notifications@github.com
Sent: Thursday, February 14, 2019 4:01:37 PM
To: probot/probot
Cc: wolfy1339; Author
Subject: Re: [probot/probot] Missing types for other packages used by Probot (#759)
Would this be fixed if we add the src/@types folder to
https://github.com/probot/probot/blob/bcc3203930e47385fb997f247b5a5bf1bc84b6b0/package.json#L20-L25
An alternative would be to list the @types in dependencies with a relative path instead of a version as the value. But I think we’ll have to add package.json files in order to make that work?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/probot/probot/issues/759#issuecomment-463794645, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEYfFZB4wlUeWu71Onf3qlCAT4QF5iXzks5vNc6xgaJpZM4YNuAQ.

Not stale

From: stale[bot] notifications@github.com
Sent: Monday, April 15, 2019 7:53:59 PM
To: probot/probot
Cc: wolfy1339; Author
Subject: Re: [probot/probot] Missing types for other packages used by Probot (#759)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/probot/probot/issues/759#issuecomment-483460117, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEYfFatK4PYHQ6_ukURSJGCVIBd1tbQlks5vhREXgaJpZM4YNuAQ.

I think this should all be resolved now. Please let me know if there is anything left

repo: probot/probot


text:
Fix link to deployment docs

Tests on the website are failing because of this: https://travis-ci.org/probot/probot.github.io/builds/421240578

Would it be better to hard link to https://probot.github.io/docs/deployment/ ?

I like linking directly to the markdown files because that keeps the docs browsable on GitHub. Jekyll will automatically translate them to the appropriate paths on the website.


text:
Sort collection by field when defining association

Hey,
I have the following problem:
Let's say I have 2 models: questions and slides. In the respective controller I pass the collection of questions to the QuestionBlueprint in a sorted fashion:
render json: QuestionBlueprint.render(questions.order(position: :asc), view: :normal, root: :questions)

This ensures that the questions in the resulting json are sorted by the position field.
Now let's say I also have a SlideBlueprint that has associated questions:
class SlideBlueprint < Blueprinter::Base
  identifier :id

  association :questions, blueprint: QuestionBlueprint, view: :normal
end

Here I don't have any control over how the collection of questions is sorted. This results in potentially unsorted questions when using the SlideBlueprint. My current idea is using a custom transformer to sort the questions hash before passing it to serialization. Is there a better way to tell blueprinter to sort a associated collection by a certain field?

Hey @leonhess, could you try doing something like the following?
class SlideBlueprint < Blueprinter::Base
  identifier :id

  association :questions, blueprint: QuestionBlueprint, view: :normal do |slide, options|
    slide.questions.order(position: :asc)
  end
end

Thanks for the quick reply. Your suggested solution worked like a charm. Thanks, closing this issue.

authors: leonhess mcclayton

repo: procore/blueprinter


text:
please provide more info

Dear @dlcarter,
This gem, looks like new version of your ApplicationSerializer mentioned by you in "RailsConf 2017: Rails APIs: The Next Generation" talk. I'm right about it? (semantic looks almost identical). Can you provide some examples about how to integrate it with Rails application? Do you have any new remarks from using it in your application? Maybe some blog post about it?

@andrzejsliwa the gem is released, currently 0.2.0. So a typical gem install blueprinter would work now. I'll close this for now, but if you have any other questions, feel free to re-open or start a new issue.

authors: andrzejsliwa philipqnguyen


text:
api-extractor package rename namespace with suffix

api-extractor rename namespace with suffix when d.ts file had namespace conflict with global namespace.
this is api-extractor bug

solutions:

waitting the @microsoft/api-extractor pr to fix.
use RegExp to replace namespace with suffix.

currently we take solution 1.

repo: produck/charon


text:
Update queue and core dependencies

Change-type: major
Signed-off-by: Carol Schulze carol@balena.io

@balena-ci I self-certify!

@balena-ci retest

repo: product-os/jellyfish-worker


text:
Remove Flowdock references

Change-type: patch
Signed-off-by: Josh Bowling josh@monarci.com

@balena-ci I self certify!

@balena-ci retest

@balena-ci retest


text:
🛑 Multi Hardware is down

In 6176375, Multi Hardware (https://www.multi-hardware.com/retrogami) was down:

HTTP code: 500
Response time: 558 ms

Resolved: Multi Hardware is back up in 2b8eda4 after 7 minutes.

repo: proger-su/upptime


text:
What is the best way to use different configs based on the connection ?

My use case is I need to use different server configs based on the SNI value (multiple domains each with different certificates and client certificate authentication requirements). Rustls offers an acceptor for this use case. I can see that there is an Accept trait for similiar use case. However looking at the code the default RustlsAcceptor uses a RustlsAcceptorFuture which actually setups the rustls. Should I make my own Acceptor if so do I need to replicate the behaviour of RustlsAcceptorFuture ?

Take a look at RustlsConfig::from_config it might just work for you.
If you want to implement Accept trait I suggest using BoxFuture as Future return type. Then you can return a normal async block like Box::pin(async move {}).


text:
[Bug] TC-VALCC-2.1 The "TestPlanVerificationSteps" no validation step of TC-VALCC-2.1 ,TC-VALCC-2.1 tests scop in this SVE-1.3.

Describe the bug
The "TestPlanVerificationSteps" no validation step of TC-VALCC-2.1 ,TC-VALCC-2.1 tests scop in this SVE-1.3.And except for TC-VALCC-1.1, there is no verification step for other cases
Steps to reproduce the behavior
No response
Expected behavior
There are verification steps for these cases
Log files
No response
PICS file
No response
Screenshots

Environment
TH Version: 2.10-beta3+spring2024
Additional Information
No response

These tests are scripted, so I'm of the impression that there should not be any verifications steps for these? @raju-apple is that not correct?

The script steps are available here: https://github.com/CHIP-Specifications/chip-test-plans/blob/master/src/cluster/valve_configuration_and_control.adoc

@zhishan67 yes there will only be VS steps if the test case isn't already an automated one. There is no plan to add VS steps for already automated test cases

Ok, I see. Thanks for the answer！

authors: CoekaertsJasper ReneJosefsen raju-apple zhishan67

repo: project-chip/certification-tool


text:
[BUG] Error flashing Matter light example into esp32c3

Reproduction steps
I'm following the following espressif documentation for Matter implementation:
documentation
Installed the prerequisites for ESP IDF:
mkdir -p ~/esp cd ~/esp git clone -b v4.4.3 --recursive https://github.com/espressif/esp-idf.git
cd ~/esp/esp-idf ./install.sh esp32
Getting the Repositories:
`cd esp-idf
source ./export.sh
cd ..
git clone --depth 1 https://github.com/espressif/esp-matter.git
cd esp-matter
git submodule update --init --depth 1
cd ./connectedhomeip/connectedhomeip
./scripts/checkout_submodules.py --platform esp32 linux --shallow
cd ../..
./install.sh
cd ..`
After getting the Repositories:

cd esp-idf; source ./export.sh; cd ..
cd esp-matter; source ./export.sh; cd..
cd esp-matter/examples/light
idf.py set-target esp32c3
idf.py -p /dev/ttyUSB0 flash

Bug prevalence
Everytime I try to flash an example
GitHub hash of the SDK that was being used
Espressif
Platform
esp32
Platform Version(s)
No response
Anything else?
Screenshot of error message

This sounds like an issue that should be reported at https://github.com/espressif/esp-matter/issues

authors: LinJiaDeng bzbarsky-apple

repo: project-chip/connectedhomeip


text:
clang-tidy: Apply fixes "misc-unused-using-decls"

Problem
There are unused "using" declarations.
Summary of Changes
Remove them.

these are great.  do you intend to put a CI guard on these at some point?

@hawk248 @saurabhst @jelderton @BroderickCarlin ?

these are great. do you intend to put a CI guard on these at some point?

Yeah, I'd like to, for some subset of the supported checks at least. Filed https://github.com/project-chip/connectedhomeip/issues/2814

authors: mspang rwalker-apple


text:
Remove '-Wno-non-virtual-dtor' from compiler flags

Problem
It seems like there is no reasons (at least in term of code in the tree) to use this flag.
Summary of Changes

Remove -Wno-non-virtual-dtor from build/config/compiler/BUILD.gn

Sorry I'm re-requesting a review because I realised -Wnon-virtual-dtor is not currently enabled. And in fact there is a few missing dtor...


text:
[clusters] Network Commissioning Server

Problem
We don't have network commissioning cluster on the server side.

Summary of Changes
Add clusters for network commissioning to the lighting app server side. After this is merged and tested, will scale to all example apps.
Also, the AddThreadNetwork temporary does not work, it will be fixed by full support of bytes string.
Test
chip-device-ctrl > connect -ip fd12::2 12345678
...
Device temporary node id (**this does not match spec**): 269170
chip-device-ctrl > zcl NetworkCommissioning AddWiFiNetwork 269170 1 0 ssid=test credentials=12345678 breadcrumb=0 timeoutMs=1000
...
chip-device-ctrl > zcl NetworkCommissioning EnableNetwork 269170 1 0 networkID=test breadcrumb=0 timeoutMs=1
...

The device can connect to the network now.

Fixes #3945

Hi, pull latest code and compiling  chip-device-ctrl:
zcl  NetworkCommissioning AddWiFiNetwork 269170 1 0 ssid=test credentials=12345678 breadcrumb=0 timeoutMs=1000
An exception occurred during process ZCL command:
Parsing Error: value should be encoded in encoding:encodedvalue format

No clue to solve it.

Hi, pull latest code and compiling chip-device-ctrl:
zcl  NetworkCommissioning AddWiFiNetwork 269170 1 0 ssid=test credentials=12345678 breadcrumb=0 timeoutMs=1000
An exception occurred during process ZCL command:
Parsing Error: value should be encoded in encoding:encodedvalue format

Test it in many ways. No clue to solve it.

zcl  NetworkCommissioning AddWiFiNetwork 269170 1 0 ssid=str:test credentials=str:12345678 breadcrumb=0 timeoutMs=1000
I will add some more documents about this.

authors: erjiaqing yuzibo


text:
Add a doc to describe build and run lighting app for i.mx 8mmevk

This is a document describes how to:

generate the Yocto SDK and the SD card image with NXP released
Yocto source code.
cross-compile the Linux lighting example on a host machine with
the Yocto SDK.
run the output executable file on i.MX 8M Mini EVK.
run the ChipDeviceController on Raspberry Pi to communicate
with i.MX 8M Mini EVK.

Below directory is created to hold the document:
examples/lighting-app/nxp/
NXP SoC related content like the lighting example implementation
on k32w is planned to be moved to this directory.
Signed-off-by: faqiang.zhu faqiang.zhu@nxp.com

@saurabhst @Damian-Nordic @msandstedt ?

authors: FaqiangZhu-nxp woody-apple


text:
[TC-OPSTATE-2.2] Step 16 and 17 -   The PICS should be updated in the script based on VS

From chip-test-scripts created by Rajashreekalmane: CHIP-Specifications/chip-test-scripts#693
Description :
[TC-OPSTATE-2.2] Step 16 and 17 -  PICS should be updated in script has per VS
PFA Script screenshot :

PFA VS screenshot :

Test-Plan PR that updated PICS in these steps : https://github.com/CHIP-Specifications/chip-test-plans/commit/a0d33b87c34cc7851cb7254ffef12f280fe27bc5

@Rajashreekalmane fixed in PR 29727 please verify it and close the ticket.

Issue resolved in latest Image.

authors: Rajashreekalmane raju-apple

repo: project-chip/matter-test-scripts


text:
Update README.md with info that Avahi daemon and Chrome on Linux should be stopped

Follow-up on #66

Probably, you need to change MulticastDNS=yes to MulticastDNS=no in /etc/systemd/resolved.conf if you're using systemd-resolved.

I came to this after running into issues with avahi-daemon.service and avahi-daemon.socket. I think printing a log::info statement in the std environment would be helpful as right now there's no level of logging that actually reveals the root issue (since StdIoError is kind of opaque).
Additionally, stopping avahi is not as trivial as sudo systemctl stop|disable <service> as it will retrigger itself. I had to do sudo systemctl mask <service> for each of them to completely stop them.

I came to this after running into issues with avahi-daemon.service and avahi-daemon.socket. I think printing a log::info statement in the std environment would be helpful as right now there's no level of logging that actually reveals the root issue (since StdIoError is kind of opaque).

Which is why we also have #67

Additionally, stopping avahi is not as trivial as sudo systemctl stop|disable <service> as it will retrigger itself. I had to do sudo systemctl mask <service> for each of them to completely stop them.

Yes, this can go into the readme.

@ivmarkov what are your thoughts on adding a zeroconf feature for hosted systems in order to support using mDNS with Avahi rather than adding directions on how to disable?

@ivmarkov what are your thoughts on adding a zeroconf feature for hosted systems in order to support using mDNS with Avahi rather than adding directions on how to disable?

If somebody (you?) want to spend time on making it work - by all means do. I was unable to find a Rust crate that can talk to Avahi. astro-dnssd (the one we use for MacOSX) claims to do so, but fails at runtime.
IMO, for real (embedded) use cases, this does not bring much value, as you want a tightly controlled, minimal Linux stack, possibly created with buildroot underneath your embedded software. I don't think Avahi has a place there.

Of course, in my case I'm looking at implementing a Matter bridge on my home server for a non-Matter set of devices so I'm not really resource constrained but I also don't want to prevent other processes from making use of mDNS at the same time.
The zeroconf library claims to support avahi and depends on avahi-sys (it also supports Bonjour, but I don't have a Mac system to test on).

Maybe I misunderstood this PR but as far as I can tell this didn't fix the issue for me.
Still panics without disabling the demon on Ubuntu 22.04:
[2023-10-06T20:04:44Z INFO  rs_matter::transport::core] Transport: waiting for incoming packets
Error: Error::StdIoError: Address already in use (os error 98) {
0: rs_matter::error::Error::new_with_details
at ./rs-matter/src/error.rs:111:24
1: <rs_matter::error::Error as core::convert::Fromstd::io::error::Error>::from
at ./rs-matter/src/error.rs:165:9
2: <core::result::Result<T,F> as core::ops::try_trait::FromResidual<core::result::Resultcore::convert::Infallible,E>>::from_residual
at /rustc/9f5fc1bd443f59583e7af0d94d289f95fe1e20c4/library/core/src/result.rs:1962:27
3: rs_matter::transport::udp::async_io::UdpListener::new::{{closure}}
at ./rs-matter/src/transport/udp.rs:58:40
4: rs_matter::mdns::builtin::MdnsService::run::{{closure}}
at ./rs-matter/src/mdns/builtin.rs:141:10
5: <core::pin::Pin as core::future::future::Future>::poll
at /rustc/9f5fc1bd443f59583e7af0d94d289f95fe1e20c4/library/core/src/future/future.rs:125:9
6: <&mut F as core::future::future::Future>::poll
at /rustc/9f5fc1bd443f59583e7af0d94d289f95fe1e20c4/library/core/src/future/future.rs:113:9
7: <embassy_futures::select::Select3<A,B,C> as core::future::future::Future>::poll
at /home/nikolas/.cargo/registry/src/index.crates.io-6f17d22bba15001f/embassy-futures-0.1.0/src/select.rs:111:33
8: async_io::driver::block_on
at /home/nikolas/.cargo/registry/src/index.crates.io-6f17d22bba15001f/async-io-1.12.0/src/driver.rs:146:33
9: dimmable_light::run
at ./rs-matter/../examples/dimmable_light/src/main.rs:165:5
10: core::ops::function::FnOnce::call_once
at /rustc/9f5fc1bd443f59583e7af0d94d289f95fe1e20c4/library/core/src/ops/function.rs:250:5
11: std::sys_common::backtrace::rust_begin_short_backtrace
at /rustc/9f5fc1bd443f59583e7af0d94d289f95fe1e20c4/library/std/src/sys_common/backtrace.rs:154:18
12: std::thread::Builder::spawn_unchecked::{{closure}}::{{closure}}
at /rustc/9f5fc1bd443f59583e7af0d94d289f95fe1e20c4/library/std/src/thread/mod.rs:529:17
13: <core::panic::unwind_safe::AssertUnwindSafe as core::ops::function::FnOnce<()>>::call_once
at /rustc/9f5fc1bd443f59583e7af0d94d289f95fe1e20c4/library/core/src/panic/unwind_safe.rs:271:9
14: std::panicking::try::do_call
at /rustc/9f5fc1bd443f59583e7af0d94d289f95fe1e20c4/library/std/src/panicking.rs:526:40
15: std::panicking::try
at /rustc/9f5fc1bd443f59583e7af0d94d289f95fe1e20c4/library/std/src/panicking.rs:490:19
16: std::panic::catch_unwind
at /rustc/9f5fc1bd443f59583e7af0d94d289f95fe1e20c4/library/std/src/panic.rs:142:14
17: std::thread::Builder::spawn_unchecked::{{closure}}
at /rustc/9f5fc1bd443f59583e7af0d94d289f95fe1e20c4/library/std/src/thread/mod.rs:528:30
18: core::ops::function::FnOnce::call_once{{vtable.shim}}
at /rustc/9f5fc1bd443f59583e7af0d94d289f95fe1e20c4/library/core/src/ops/function.rs:250:5
19: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce>::call_once
at /rustc/9f5fc1bd443f59583e7af0d94d289f95fe1e20c4/library/alloc/src/boxed.rs:2007:9
20: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce>::call_once
at /rustc/9f5fc1bd443f59583e7af0d94d289f95fe1e20c4/library/alloc/src/boxed.rs:2007:9
21: std::sys::unix::thread::Thread::new::thread_start
at /rustc/9f5fc1bd443f59583e7af0d94d289f95fe1e20c4/library/std/src/sys/unix/thread.rs:108:17
22: start_thread
at ./nptl/pthread_create.c:442:8
23: clone3
at ./misc/../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
}
Steps to reproduce:
Boot Ubuntu 22.04
Open Browser to clone rs-matter repository
Build and run OnOff_Light example

I would recommend copying the example code into an application and then initializing with the zeroconf feature.
Sidenote: @kedars what do you think about splitting the examples on a per platform basis? There's a lot of extra noise in the example in making the same source file support esp32 and Linux.

I just on the master commit 3d8fc59596c0413a7ded32bb401a3858b34a14e1, also met this issue.   On arch linux.

I just on the master commit 3d8fc59, also met this issue. On arch linux.

This issue is no longer relevant because the current main branch now does support Avahi. You just need to compile with cargo build --features async-io,zeroconf --examples

This issue is no longer relevant because the current main branch now does support Avahi. You just need to compile with cargo build --features async-io,zeroconf --example

On mine node,
sudo lsof -i -P -n | grep 5353
systemd-r     457 systemd-resolve  15u  IPv4     18562      0t0  UDP *:5353
systemd-r     457 systemd-resolve  16u  IPv6     18563      0t0  UDP *:5353

cargo build --features async-io,zeroconf --examples
And the error log is that:
2024-03-21T08:28:35Z INFO  rs_matter::mdns::builtin] mDNS TXT key D val 250
[2024-03-21T08:28:35Z INFO  rs_matter::mdns::builtin] mDNS TXT key CM val 1
[2024-03-21T08:28:35Z INFO  rs_matter::mdns::builtin] mDNS TXT key DN val OnOff Light
[2024-03-21T08:28:35Z INFO  rs_matter::mdns::builtin] mDNS TXT key VP val 65521+32768
[2024-03-21T08:28:35Z INFO  rs_matter::mdns::builtin] mDNS TXT key SII val 5000
[2024-03-21T08:28:35Z INFO  rs_matter::mdns::builtin] mDNS TXT key SAI val 300
[2024-03-21T08:28:35Z INFO  rs_matter::mdns::builtin] mDNS TXT key PH val 33
[2024-03-21T08:28:35Z INFO  rs_matter::mdns::builtin] mDNS TXT key PI val
[2024-03-21T08:28:35Z DEBUG zeroconf::linux::service] Registering service: AvahiMdnsService { client: None, poll: None, context: AvahiServiceContext { name: Some("135098307ADC8921"), kind: "_matterc._udp", port: 5540, group: None } }
[2024-03-21T08:28:35Z ERROR rs_matter::mdns::builtin] Encountered error registering mDNS service: could not initialize AvahiClient

Should i also need disable it with MulticastDNS=no?

On mine node,
sudo lsof -i -P -n | grep 5353
systemd-r     457 systemd-resolve  15u  IPv4     18562      0t0  UDP *:5353
systemd-r     457 systemd-resolve  16u  IPv6     18563      0t0  UDP *:5353

What you have running on your node is not Avahi, but systemd-resolve - which - to my understanding - is a "very minimal" mDNS-like client which we cannot / do not yet integrate with.
So it is normal that the app outputs:

[2024-03-21T08:28:35Z DEBUG zeroconf::linux::service] Registering service: AvahiMdnsService { client: None, poll: None, context: AvahiServiceContext { name: Some("135098307ADC8921"), kind: "_matterc._udp", port: 5540, group: None } }
[2024-03-21T08:28:35Z ERROR rs_matter::mdns::builtin] Encountered error registering mDNS service: could not initialize AvahiClient

... because what you have is not Avahi in the first place.
I think what you should do is
(a) stop this systemd-resolve
(b) Build and run the rs-matter stack without Avahi/zeroconf support, as you started originally. I.e. cargo build --features async-io --examples

Should i also need disable it with MulticastDNS=no? look like We should also zeroconf for mdns in systemd-resolved. Because systemd-resoloved and avahi conflict on the mdns.
Now I just disable mdns in systemd-resolved, and build without zeroconf, now example run ok.

Exactly. Until (if ever) we also have an integration with systemd-resolved, you need to disable it, and then run rs-matter with its own built-in mDNS responder.

authors: cheat-sc inevity ivmarkov newcomertv ssnover

repo: project-chip/rs-matter


text:
Toggling storage option is broken

Go to any attribute.
Toggle the "Storage option" dropdown.
Observe:

⇝ (node:59858) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'map' of undefined
    at /Users/fesseha/Sources/connectedhomeipfork/third_party/zap/repo/src-electron/rest/user-data.js:189:26
    at Layer.handle [as handle_request] (/Users/fesseha/Sources/connectedhomeipfork/third_party/zap/repo/node_modules/express/lib/router/layer.js:95:5)
    at next (/Users/fesseha/Sources/connectedhomeipfork/third_party/zap/repo/node_modules/express/lib/router/route.js:137:13)
    at Route.dispatch (/Users/fesseha/Sources/connectedhomeipfork/third_party/zap/repo/node_modules/express/lib/router/route.js:112:3)
    at Layer.handle [as handle_request] (/Users/fesseha/Sources/connectedhomeipfork/third_party/zap/repo/node_modules/express/lib/router/layer.js:95:5)
    at /Users/fesseha/Sources/connectedhomeipfork/third_party/zap/repo/node_modules/express/lib/router/index.js:281:22
    at Function.process_params (/Users/fesseha/Sources/connectedhomeipfork/third_party/zap/repo/node_modules/express/lib/router/index.js:335:12)
    at next (/Users/fesseha/Sources/connectedhomeipfork/third_party/zap/repo/node_modules/express/lib/router/index.js:275:10)
    at /Users/fesseha/Sources/connectedhomeipfork/third_party/zap/repo/src-electron/server/http-server.js:212:11
⇝ (node:59858) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 52)

Same happens for assigning a default value to an attribute.
You can write the desired value in the text box. But once you click elsewhere,it reverts back to 0
⇝ (node:87101) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'map' of undefined
    at /Users/GitHub/connectedhomeip/third_party/zap/repo/src-electron/rest/user-data.js:189:26
    at Layer.handle [as handle_request] (/Users/GitHub/connectedhomeip/third_party/zap/repo/node_modules/express/lib/router/layer.js:95:5)
    at next (/Users/GitHub/connectedhomeip/third_party/zap/repo/node_modules/express/lib/router/route.js:137:13)
    at Route.dispatch (/Users/GitHub/connectedhomeip/third_party/zap/repo/node_modules/express/lib/router/route.js:112:3)
    at Layer.handle [as handle_request] (/Users/GitHub/connectedhomeip/third_party/zap/repo/node_modules/express/lib/router/layer.js:95:5)
    at /Users/GitHub/connectedhomeip/third_party/zap/repo/node_modules/express/lib/router/index.js:281:22
    at Function.process_params (/Users/GitHub/connectedhomeip/third_party/zap/repo/node_modules/express/lib/router/index.js:335:12)
    at next (/Users/GitHub/connectedhomeip/third_party/zap/repo/node_modules/express/lib/router/index.js:275:10)
    at /Users/GitHub/connectedhomeip/third_party/zap/repo/src-electron/server/http-server.js:212:11
(node:87101) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 88)

The XML needs a 'strorage' option so that the storage class can be properly defaulted.

authors: jmartinez-silabs jonsmirl tecimovic

repo: project-chip/zap


text:
Continuous work from TDJ

https://github.com/project-chip/zap/issues/286
https://github.com/project-chip/zap/issues/343
https://github.com/project-chip/zap/issues/354
cypress test reenablement

@bzbarsky-apple : this is just UI and cypress unit testing work, so I don't think we need a review from you, but if you're curious, feel free to review.

Going to pass on this one.  It'd have to be either a complete rubberstamp or a large time investment...

authors: bzbarsky-apple tecimovic