TypeError: Cannot read property 'on' of undefined

I played electron long time ago and it worked very well. But I had the issue today - 2016 Nov 19!
I simply cloned this repository and npm install && npm run start, but I got errors:
app.on('ready', createWindow)
   ^

TypeError: Cannot read property 'on' of undefined
    at Object.<anonymous> (/Users/johnking/workshop/electron/electron-quick-start/main.js:40:4)
    at Module._compile (module.js:556:32)
    at Object.Module._extensions..js (module.js:565:10)
    at Module.load (module.js:473:32)

    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)
    at Module.runMain (module.js:590:10)
    at run (bootstrap_node.js:402:7)
    at startup (bootstrap_node.js:157:9)
    at bootstrap_node.js:521:3

npm ERR! Darwin 16.1.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "start"
npm ERR! node v7.0.0
npm ERR! npm  v3.10.8
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: `electron .`
npm ERR! Exit status 1
...

I am using the latest electron version<EMAIL_ADDRESS>I googled the solutions and tried all kinds of workarounds but could not figure it out.
thanks for any suggestions and help
-John

Sounds like your node_modules got a bit funky.  Try just deleting your node_modules folder and reinstalling with npm install

thanks @MarshallOfSound
I googled the solutions and tried all kinds of workarounds but could not figure it out.

I tried to delete and reinstall the electron folder under node_modules
I tried to remove the globally installed electron module
I tried to delete the whole node_modules and reinstall
I also tried logs:

console.log(require.resolve('electron'))
console.log(require('electron'))

but it did not give me much useful information.
/Users/johnking/workshop/electron/electron-quick-start/node_modules/electron/index.js

/Users/johnking/workshop/electron/electron-quick-start/node_modules/electron/dist/Electron.app/Contents/MacOS/Electron

it blocks me now ...

Just to be sure you're getting a fresh start, please try running these exact commands from scratch, and paste the output here:
git clone https://github.com/electron/electron-quick-start
cd electron-quick-start
npm install
npm start

Hi Zeke @zeke
I got the same error after re-doing the steps as you specified.
$ npm start

><EMAIL_ADDRESS>start /Users/johnking/workshop/electron-quick-start
> electron .

/Users/johnking/workshop/electron-quick-start/main.js:40
app.on('ready', createWindow)
   ^

TypeError: Cannot read property 'on' of undefined
    at Object.<anonymous> (/Users/johnking/workshop/electron-quick-start/main.js:40:4)
    at Module._compile (module.js:556:32)
    at Object.Module._extensions..js (module.js:565:10)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)
    at Module.runMain (module.js:590:10)
    at run (bootstrap_node.js:402:7)
    at startup (bootstrap_node.js:157:9)
    at bootstrap_node.js:521:3

npm ERR! Darwin 16.1.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
npm ERR! node v6.9.1
npm ERR! npm  v3.10.8
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: `electron .`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'electron .'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the electron-quick-start package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     electron .
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs electron-quick-start
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls electron-quick-start
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/johnking/workshop/electron-quick-start/npm-debug.log

I found the information below from electron official site
When using Electron’s built-in module you might encounter an error like this:
> require('electron').webFrame.setZoomFactor(1.0)
Uncaught TypeError: Cannot read property 'setZoomLevel' of undefined

This is because you have the npm electron module installed either locally or globally, which overrides Electron’s built-in module.
To verify whether you are using the correct built-in module, you can print the path of the electron module:
console.log(require.resolve('electron'))

and then check if it is in the following form:
"/path/to/Electron.app/Contents/Resources/atom.asar/renderer/api/lib/exports/electron.js"

If it is something like node_modules/electron/index.js, then you have to either remove the npm electron module, or rename it.
npm uninstall electron
npm uninstall -g electron

I am confused here, if I uninstall the electron module, the compiler will complain sh: electron: command not found.
thanks a lot for your help.
-John

I spent the whole day to find the culprit  .....
It happens when I start the application from ATOM-terminal !!!

@johnking Is there any fix to this?

it is happen to me the same with atom and normal terminal.
It is one week I try to understand why and what I have to do for resolve it, but still nothing.
I 'm use ubuntu, I installed with super admin privileges and --unsafe-perm=true, this is the unique way for not have any errors.
I removed, I reinstalled, I used global and not global, I try different code, but still not work and I am start to be crazy.
Someone have solution?

Using NodeJS command prompt instead of Atom cmd worked for me.

replace your scripts with:
"scripts": {
"test": "electron .",
"start": "electron ."
}

@emmanuel39hanks Thanks man.. I was facing the issue. With your solution it is working fine.

Wow @emmanuel39hanks that worked somehow! Thank you so much. I've been debugging for hours trying to find the cause, but couldn't find it until I saw your post.

@ emmanuel39hanks useful


Adding target script that enables Criteo to receive the correct DFP tag values

Title says it all. Script comes directly from Criteo integration guide.
Verification

Visit http://assets.lonelyplanet.com/YXBwbGVfdGVzdA==.html
Verify that page loads correctly
Verify that there is a call to rta.js

Verification steps worked. :+1:


Stems in linguistic breakdown tooltips | No Migrations

Stems are now imported and shown in the linguistic breakdown popup.
before:

after:

I'll update the prod database when this merges.
The other minor change is migrations for API app is no longer source controled as we are not using the migration functionality from django. See newly added CreeDictionary/API/migration/readme.md for details. I've removed python manage.py migrate from redeploy on Sapir.
There were two migrations 0002_insert_sources.py and 0003_merge_preverbs.py, which shouldn't be implemented with migrations in the first place.
insert_sources is moved to the importer. merge_perverbs is no longer needed as the source XML files have evolved to be better.

@Madoshakalaka  I'm presuming you have to re-export the database before merging this?

I'm presuming you have to re-export the database before merging this?
Yes I'm doing it now!


Is there any plan to make the dataset public for research?

Hi Author,
This is a really good dataset for the object removal research field.
Is there any plan to make it public use?
I think public use of the dataset really speeds up the progress of the research field.
Thx!

I would like to express my gratitude for your interest in our data. However, as the data is part of a project supported by the NIA (National Information Society Agency) in Korea, it seems appropriate to suggest that you reach out to the NIA directly for further assistance.

I would like to express my gratitude for your interest in our data. However, as the data is part of a project supported by the NIA (National Information Society Agency) in Korea, it seems appropriate to suggest that you reach out to the NIA directly for further assistance.

Hello! Thank you for your work, collecting such great dataset.
I am in process of reaching NIA. However, I am confused and disoriented due to lack of knowledge of Korean language.
Could you please give some road map or mile stones on how to reach NIA?
Or maybe you can ask them to make dataset public, since it was published several years ago?

I would like to express my gratitude for your interest in our data. However, as the data is part of a project supported by the NIA (National Information Society Agency) in Korea, it seems appropriate to suggest that you reach out to the NIA directly for further assistance.

Hello! Thank you for your work, collecting such great dataset. I am in process of reaching NIA. However, I am confused and disoriented due to lack of knowledge of Korean language. Could you please give some road map or mile stones on how to reach NIA? Or maybe you can ask them to make dataset public, since it was published several years ago?

Thank you for your attention about our work
We just opened google drive link for dataset


Hot upgrade between hotfix versions when running in HA

Today is not always safe to upgrade between hotfix versions when you're running in HA. This is because distributed protocol is not versioned. We never did it, because Hazelcast didn't support this feature, so investing in a versioned distributed protocol was worthless.
Now that Hazelcast has it, we should version our distributed protocol, so our users can upgrade a cluster of servers, one by one.

Implemented through the new ORemoteTaskFactoryManager interface.


Specify what should happen if Row.get(…) is called with a negative/out of bounds index/non-existing column name

Right now, we're lacking a specification for Row.get(…) what should happen if the column index is out of bounds (negative, greater than the number of available columns) or a column name is used that isn't present in the result.
Analyzing the drivers yields the following behavior:

MySQL: NoSuchElementException/ArrayIndexOutOfBoundsException
Postgres: IllegalArgumentException
SQL Server: IllegalArgumentException
MariaDB: IllegalArgumentException
Spanner: IllegalArgumentException
H2: IllegalArgumentException

This ticket is to discuss the options and to agree on how implementations of Row.get(…) should behave.

After discussing the ticket in the monthly call, we want to do something about this. The design choices range from a R2dbcException subtype to the use of built-in Java exceptions.

I just wanted to make sure I did not mislead in the meeting -- I think IllegalArgumentException is semantically perfectly appropriate; I was not trying to tip the scales towards a custom exception.

All good, these are all valid options.

I agree that IllegalArgumentException seems like the best choice, as it is one of the exception types listed in section 11 of the 0.8.x specification. Drivers should follow the spec.
When invoking Row.get(...) with an invalid index or name, IllegalArgumentException seems more descriptive than IllegalStateException or UnsupportedOperationException. R2dbcException would signify a failed database interaction, so is not applicable here.

R2dbcException would signify a failed database interaction, so is not applicable here.

Well, the JDBC precedent is ResultSet.getXYZ() throws SQLException...

The problem with JDBC is that everything is an SQLException and drivers do not consistently implement the entire exception hierarchy.

and drivers do not consistently implement the entire exception hierarchy.

Same as here, given your initial issue text? 😀

Right now, the error behavior isn't specified so everyone is doing something different and now we have the chance to clean up things and actually put them into the TCK to help implementors convince towards the spec.


b1

Node ID:
4ab86817b5259bf2

Node ID: 4ab86817b5259bf2
Baker ID: 481
Account address: 33G2TsnyKjDqWZCGTZCJaKQfVVsJJJtm1E8toXvy1ocxoBLgMH

confirmed:B1
node:4ab86817b5259bf2

pending:T1
account1:3zQikkKtFPGPBghRBT76afht8SyHKAvdtYy8JbMUSWvNHyMKAW
account2:33G2TsnyKjDqWZCGTZCJaKQfVVsJJJtm1E8toXvy1ocxoBLgMH
DeviceDetails:verified
Screenshot:missing
We cannot fully verify this submission. Please provide us with screenshots with all transactions.
@yusuftrl

pending:T1
account1:3zQikkKtFPGPBghRBT76afht8SyHKAvdtYy8JbMUSWvNHyMKAW
account2:33G2TsnyKjDqWZCGTZCJaKQfVVsJJJtm1E8toXvy1ocxoBLgMH
DeviceDetails:verified
Screenshot:missing
We cannot fully verify this submission. Please provide us with screenshots with all transactions.
@yusuftrl

12 Oca 2021 Sal 15:35 tarihinde Suhas Hegde<EMAIL_ADDRESS>şunu
yazdı:

pending:T1
account1:3zQikkKtFPGPBghRBT76afht8SyHKAvdtYy8JbMUSWvNHyMKAW
account2:33G2TsnyKjDqWZCGTZCJaKQfVVsJJJtm1E8toXvy1ocxoBLgMH
DeviceDetails:verified
Screenshot:missing
We cannot fully verify this submission. Please provide us with screenshots
with all transactions.
@yusuftrl https://github.com/yusuftrl
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Concordium/Testnet3-Challenges/pull/1775#issuecomment-758627707,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARALRBDYQNBGBSFR23QSBXDSZQ62XANCNFSM4UE7VHBQ
.

12 Oca 2021 Sal 15:35 tarihinde Suhas Hegde<EMAIL_ADDRESS>şunu
yazdı:

pending:T1
account1:3zQikkKtFPGPBghRBT76afht8SyHKAvdtYy8JbMUSWvNHyMKAW
account2:33G2TsnyKjDqWZCGTZCJaKQfVVsJJJtm1E8toXvy1ocxoBLgMH
DeviceDetails:verified
Screenshot:missing
We cannot fully verify this submission. Please provide us with screenshots
with all transactions.
@yusuftrl https://github.com/yusuftrl
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Concordium/Testnet3-Challenges/pull/1775#issuecomment-758627707,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARALRBDYQNBGBSFR23QSBXDSZQ62XANCNFSM4UE7VHBQ
.

@cryptovoyagr  T1  screenshots

@cryptovoyagr  T1  screenshots

confirmed:T1
account1:3zQikkKtFPGPBghRBT76afht8SyHKAvdtYy8JbMUSWvNHyMKAW
account2:33G2TsnyKjDqWZCGTZCJaKQfVVsJJJtm1E8toXvy1ocxoBLgMH
DeviceDetails:verified

confirmed:T1
account1:3zQikkKtFPGPBghRBT76afht8SyHKAvdtYy8JbMUSWvNHyMKAW
account2:33G2TsnyKjDqWZCGTZCJaKQfVVsJJJtm1E8toXvy1ocxoBLgMH
DeviceDetails:verified

confirmed:B4
address:3bofjYxKSLD6weyi44569E7GCLrBkkgXbgTkUq5NQosX2WRa2i
baker:373

confirmed:B4
address:3bofjYxKSLD6weyi44569E7GCLrBkkgXbgTkUq5NQosX2WRa2i
baker:373


[Crash] FTB Beyond crash

Crash on Server join
*Ftb Beyond ver 1.1.0 (Beta)
2 different crashes? one has a block tied to it, the other one doesnt.
*Crash 1
*Crash 2

should be fixed in SonarSonic/Sonar-Core#30

Fixed in dev


send_direct_message api does not support sending options.

The following API http://docs.tweepy.org/en/latest/api.html#API.send_direct_message does not support sending the options in case the quick_reply_type is options. I checked the source code and unfortunately it is being added like this. So only type is added and the options are not added.

This is the twitter API reference - https://developer.twitter.com/en/docs/direct-messages/quick-replies/api-reference/options
Doesn't look there is a workaround for now. Please suggest any workaround you can think of.

Duplicate of #1280


How to install Unbuntu in WSL with no access to Store?

I don't have access to the MS Store at work.  I have the .deb file for Ubuntu and I enabled the Linux subsystem,  How do I get to it to install Ubuntu?

This is a question that's better suited for the Microsoft/WSL repo. I believe there are instructions in that repo for manually installing a distro locally.


 To solve this the cookie-notice needs to load outside the viewport and should be displayed and animated when cookie-notice isn't set.

Issue is ready for release.


Add node trace source map handling in dev mode

Fixes #2285

This will literally save hours of dev time, as it is currently so non-obvious what line is causing an error. 👍 👍

This looks really good, let me give it a few spins before merging 👌

This is brilliant @kpdecker !

This looks like something really great.
I'll give this a run and merge this.

Tried it last night, works 👌

This is fantastic.
Thanks for the hard work @kpdecker

I just published 3.2.0 which has this PR.

This broke browser source maps.
To reproduce, run an example (e.g. with-absolute-imports) with<EMAIL_ADDRESS>Source maps look like this:
null

// WEBPACK FOOTER //
// ./components/header.js

I can't really make sense of that output. What command is it from? What does your nextconfig look like?

And what browser?

Chrome Version 60.0.3112.101 (Official Build) (64-bit) / MacOS 10.12.6 / Node 8.1.2
As I said above, just running the with-absolute-imports example in the repo with<EMAIL_ADDRESS>and looking at the source maps in chrome devtools.

I'm thinking this is most likely related to the absolute imports example 🤔 cc @sergiodxa

I just tried a random example -- with-redux, same result.
Downgraded to<EMAIL_ADDRESS>and the source maps came back.

I'm also experiencing the same issue as @dnakov , I reverted back to<EMAIL_ADDRESS>and no longer see an issue with sourcemaps while debugging.

Fixed in #2900.


Update Composer dependencies (2020-06-05-00-08)

Visual regression test passed!
View the visual regression test report


Add comments to javascript wrapper parts.

The code in pre.js and engine.js is a bit confusing to see in isolation,
since the files aren't valid JS files by themselves. This just adds some
explanatory text to both files.
Fixes #22937.
Bugsquad edit: Closes #23146, Closes #23147

Cherry-picked for 3.0.7.


Custom svg for another Extensions type like excel or csv?

Hi, are you guys willing to add a custom SVG so it's not just an image format?

All files should be accepted, you can pass the list of the types as prop.
Let me know if further help needed


Add schema and segment crc to SegmentDirectoryContext

Adding a few more things to the SegmentDirectoryContext, to complete the context for a SegmentDirectory.

Codecov Report

Merging #8127 (3f3ae46) into master (7d74c8c) will decrease coverage by 57.16%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             master    #8127       +/-   ##
=============================================
- Coverage     71.33%   14.17%   -57.17%
+ Complexity     4302       81     -4221
=============================================
  Files          1624     1579       -45
  Lines         84140    82269     -1871
  Branches      12596    12392      -204
=============================================
- Hits          60021    11660    -48361
- Misses        20013    69735    +49722
+ Partials       4106      874     -3232

Flag
Coverage Δ

integration1
?

integration2
?

unittests1
?

unittests2
14.17% <0.00%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


⚠ ClamAV has degraded performance

In 80702ee, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 582 ms

Resolved: ClamAV performance has improved in 961661b after 5 minutes.


#47 ShuffleMapTask ignore spark.driver.maxResultSize

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)
Please review http://spark.apache.org/contributing.html before opening a pull request.

kap: https://github.com/Kyligence/KAP/issues/14465

retest this please


Error

The module has started, but there is a problem. I immediately wrote the following information to HA: Login attempt or request with invalid authentication from 2e565496-energomera-iek61107.local.hass.io (<IP_ADDRESS>). See the log for details.
In the module log: Other error occurred: 401
401: Unauthorized
Tell me what to do?

Try new version


KAFKA-12945: Remove port, host.name and related configs in 3.0

They have been deprecated since 0.10.0. Full list of removes configs:

port
host.name
advertised.port
advertised.host.name

Also adjust tests to take the removals into account. Some tests were
no longer relevant and have been removed.
Finally, took the chance to:

Clean up unnecessary usage of KafkaConfig$.MODULE$ in
related files.
Add missing Test annotations to AdvertiseBrokerTest and
make necessary changes for the tests to pass.

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Thanks @ijuma. I have started to work on this a while ago but I haven't had the time to finish it yet: https://github.com/apache/kafka/pull/10437. I will close it and review yours.

Sorry, this is my bad. I vaguely recalled a PR about this and searched for it, but somehow didn't find it.

@dajac I updated this PR to hopefully be a combination of our changes. I'll assign the JIRA to you since your PR was first and, if you're happy with it, we can merge this with both of us as co-authors. Once again, my bad for duplicating work here.

I noticed a few test failures, will fix them.

@dajac I updated this PR to hopefully be a combination of our changes. I'll assign the JIRA to you since your PR was first and, if you're happy with it, we can merge this with both of us as co-authors. Once again, my bad for duplicating work here.

Yeah, that works for me. No worries ;)

@ijuma Overall, the PR LGTM. There are few connect related failed tests in the last Jenkins run. This is suspicious... I haven't had the time to really investigate them though.

@dajac Most of them pass locally, I am re-running and will investigate more the ones that are not flaky.

Unrelated failures:

Build / JDK 11 and Scala 2.13 / org.apache.kafka.common.network.SslTransportLayerTest.[1] tlsProtocol=TLSv1.2, useInlinePem=false
Build / JDK 11 and Scala 2.13 / org.apache.kafka.common.network.SslTransportLayerTest.[2] tlsProtocol=TLSv1.2, useInlinePem=true
Build / JDK 11 and Scala 2.13 / org.apache.kafka.common.network.SslTransportLayerTest.[3] tlsProtocol=TLSv1.3, useInlinePem=false
Build / JDK 11 and Scala 2.13 / org.apache.kafka.common.network.SslTransportLayerTest.[1] tlsProtocol=TLSv1.2, useInlinePem=false
Build / JDK 11 and Scala 2.13 / org.apache.kafka.common.network.SslTransportLayerTest.[2] tlsProtocol=TLSv1.2, useInlinePem=true
Build / JDK 11 and Scala 2.13 / org.apache.kafka.common.network.SslTransportLayerTest.[3] tlsProtocol=TLSv1.3, useInlinePem=false
Build / JDK 16 and Scala 2.13 / kafka.server.RaftClusterTest.testCreateClusterAndCreateAndManyTopicsWithManyPartitions()
Build / JDK 16 and Scala 2.13 / kafka.server.RaftClusterTest.testCreateClusterAndCreateAndManyTopics()
Build / JDK 8 and Scala 2.12 / kafka.server.RaftClusterTest.testCreateClusterAndCreateAndManyTopics()
Build / JDK 8 and Scala 2.12 / kafka.server.RaftClusterTest.testCreateClusterAndCreateAndManyTopics()

LGTM! Thanks.

Ugh, I accidentally pressed the merge button before adding the Co-authored-by line.


Security scan recommendations from observatory.mozilla.org

Hello,
maybe this question should be in next-auth project, but it is connected with this site, so I put it here.
Do you know about this site?
https://observatory.mozilla.org/analyze/nextjs-starter.now.sh
Maybe it can help you with improving security settings of next-auth example page and nextjs-starter site too. Something could be solved with https://github.com/zeit/next.js/pull/4943
FYI I'm currently solving the problem of how to store JWT in SPA written in next.js & redux, so I'm checking all resources which could help me (including yours projects). For me it is most important https://github.com/zeit/next.js/issues/153
My current solution is to store JWT in redux store (for client API requests) & in httpOnly secure cookie (for server API requests).
But I not sure with one thing. If it is OK that JWT token (which is put from cookie into the redux store by server during the first server render) is actually stored in window.__NEXT_DATA__ which could be easy accessed from potential malicious XSS. Maybe I should ask in https://github.com/zeit/next.js/issues/153 too.

Hi there, thanks that's an interesting tool from Mozilla and I hadn't seen it before.
I probably won't add more to the next-auth example – as next-auth is already more complicated than it needs to be and I want to try and make things easier for folks by keeping the noise down – but it's interesting for nextjs-starter project and might be worth including some hardening tools for if there as some easy options to include by including an additional library for CORS, etc.
(I probably won't try to address all of those issues specifically – some of them are not relevant and Mozilla Firefox doesn't support all those headers – but it's interesting and helpful to have a good practice example of useful headers to have set, especially for folks building more complex sites.)
Regarding tokens readable in JavaScript:
So, there is a solution to this. It's a bit of a pain, but I take this approach on other services that need to do privileged operations in JavaScript (in my case, websockets). I use it with next-auth and not JWT in my case but the same approach applies to both.
The approach is to create an Access Token, that is not a Session ID but is attached to a session, and to store that value on the the client side accessible from JavaScript (e.g. JWT cookie, localStorage).
Often the Access Token is rotated in the session and includes an expiry time after which it is no longer valid. This can be anywhere from 5 minutes to a few hours. This makes it less valuable if someone somehow does manage to steal it using XSS, because it will eventually expire (unlike a session, which stays valid as long as it's actively being used).
You can the Access Token to allow some operations (e.g. identify the user, access to some read-only data) but not others. For example: You can still require a session token stored in an HTTP only cookie for POST requests (to modify data) or to read sensitive data (like billing or address info).
If you think it's worth the hassle I guess depends on what you are doing on your site and if you think it's worth the benefit and hassle over just storing the session in a JavaScript cookie. :-)
I've avoided JavaScript accessible cookies in next-auth to try and provide a best practice example, but a large number of major production sites just have sessions accessible in JavaScript because it's such a hassle and their risk/exposure is low.

Note: I'm leaving this ticket open till I've had a chance to look at the headers and see if there are some additional sensible defaults we could set. Am especially interested in node libraries for Express that provide some hardening by setting these automagically.

Here’s something I wrote explaining the best way to handing auth tokens with SSR and an external API: https://spectrum.chat/thread/91bdb515-11b8-4d39-bd9a-925e16395cb7


Increase code coverage 100%.

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
❌

@samdark  I'm still going to 52% :(


SWR: Attempted import error: 'swr' does not contain a default export (imported as 'useSwr').

What are the steps to reproduce this issue?

Run codegen with swr generator
Import one of the helper functions into an RSC component
Terminal shows this error

Nothing breaks, it's just a warning, but annoying
More info: https://github.com/vercel/swr/issues/2694
What happens?

What were you expecting to happen?
The codegen could add "use client" to parts that actually call useSWR and separate keys from this code as the keys are used in server components.
Any other comments?
Obviously we don't want to call useSWR in server components, however there are parts of the generated code that are useful in server components. One of these, which I make use of in Storyden's codebase is the generated keys. This means I can use fetch on the server but still use the generated types and paths.
export const getThreadListKey = (params?: ThreadListParams) =>
  [`/v1/threads`, ...(params ? [params] : [])] as const;

These generated key functions are useful to keep everything type safe - even while Orval doesn't generate server code, I can use these to ensure my code is at least somewhat type safe for server components:
import { server } from "src/api/client";
import { ThreadListOKResponse } from "src/api/openapi/schemas"; // schema imports are fine - no useEffect dependents here
import { getThreadListKey } from "src/api/openapi/threads"; // this causes the error, even though I'm not actually using useEffect dependents (useSWR) - the runtime still warns me because getThreadListKey is in the same file as a useSWR import+call

import { Client } from "./Client";

type Props = {
  category: string;
};

export async function FeedScreen(props: Props) {
  const key = getThreadListKey({ categories: [props.category] })[0]; // imported from Orval

  const data = await server<ThreadListOKResponse>(key);

  return <Client category={props.category} threads={data.threads} />;
}

What versions are you using?
Package Version: "orval": "^6.17.0",

PR is welcome.  SSR has been a nightmare for library implementors!

I'd be up for doing a PR to split these files, where's a good place to start?
I think we just need to put the SWR keys in a separate file to the actual fetch calls, should be quite simple!

Hmm this was handled differently for React Query and the files need not be split for SSR: https://github.com/anymaniax/orval/issues/985

@Southclaws
Hi, this similar issue seems to have been resolved in v14 of Next.js. This may also have been resolved, so could you please check again with v14?

@Southclaws
Hi, this similar issue seems to have been resolved in v14 of Next.js. This may also have been resolved, so could you please check again with v14?
@melloware
This problem is probably a problem with Next.js, not orval. The "bug" label attached to issue may not be necessary.

I removed bug and will close for now unless the OP can confirm.

Why was this issue closed? I just ran into the same problem with SWR. I imported the function that does Axios request into a server component and wanted to do a request on the server side but it failed with an error that matches the name of this issue. This makes the SWR generator kind of useless for those who want to do both server-side and client-side fetching unless I generate completely separate API files for use in server components but it feels very wrong considering that the files generated for the SWR client already have everything I need to use on server as well. I think splitting the files is the way to go. I don't know how come that this works in ReactQuery, but even there the hooks could be just tree-shaken away from the server bundle.

I got some extra information:
To be more correct this error doesn't crash the build and everything seems to be working on the server, including loading data. Nonetheless, it doesn't seem to be safe to use in production like this.
I tried to split it manually into separate files, but as long as they are re-exported by the same index.ts file, the error will persist. I imagine creating an entirely different barrel file would be quite a big change for orval, but thankfully the file with hooks can be marked with 'use client' directive and the server will ignore it, I can confirm that the error is then gone. So I'd propose to do something like this (in case of split-tags):
openapi/
├─ api/
│  ├─ tag-1/
│  │  ├─ tag-1.ts
│  │  ├─ tag-1-hooks.ts
│  ├─ tag-2/
│  │  ├─ tag-2.ts
│  │  ├─ tag-2-hooks.ts
│  ├─ index.ts
├─ models/
│  ├─ index.ts

With hooks files having 'use client' on top. Something similar can be probably done about split and tags mode, but as for single I am afraid nothing can be done.

Nice debugging. Still a big change but at least you know what works now.

@isoroka-plana
Hi, I would like to ask you a few questions to help me understand better.

Is it correct that what you are looking for is to use only the following two functions that do not depend on swr?

key generation function
Axios client

Also, is it correct to understand that it is used in the server-side component of Next.js?

Yes, I am looking to use axios client, and the function that does the axios request (if that's what you mean by key generation function, there's one that generates swr key, but it's only relevant for SWR itself). Here's an example that I am looking to import:

export const booksGet = (options?: SecondParameter<typeof customInstance>) => {
  return customInstance<Book[]>({url: `api/v1/books`, method: 'GET'}, options);
}

Yes, that's exactly right. Example component:

export const BooksPage = async () => {
  const books = await booksGet();

  return (

     {books .map(book => <Book key={book.id} book={book} />)}

  )
}

So the axios stuff is client/server agnostic while swr stuff is client only, that's why in order to make convenient to use it's best to split them into separate files. Cause I can create the above function myself using the same axios client and models used by Orval but still that means I have to hardcode the API path.

@isoroka-plana
Thank you for letting me know.
I thought this could be achieved by specifying the axios client, what do you think?
orval.config:
module.exports = {
  'petstore-file': {
    input: {
      target: './petstore.yaml',
    },
    output: {
      client: 'axios',
      target: 'src/gen/endpoints',
    },
  },
};

### generated

```typescript
const listPets = (
    params: ListPetsParams,
    version: number = 1,
 ) => {
      return listPetsMutator<Pets>(
      {url: `/v${version}/pets`, method: 'GET',
        params
    },
      );
    }

usage:
 const pets = await listPets(params);

  return (

     {pets .map(pet => <Pet key={pet.id} pet={pet} />)}

  )
}

@soartec-lab thank you for suggesting this idea. I considered this option but I still need swr for requests from the client side. This would require me to generate 2 different outputs 1 for plain axios and 1 for swr. Each of these will create their own models if I get everything correctly. It's a messier approach than just creating copies of the functions that I need by myself. But from the perspective of Nextjs + orval user there should be a way to use 1 generator and use its output on both sides.

@isoroka-plana
Hmmm. This can be achieved by creating automatic generation of axios for the server component and automatic generation of swr for the client component. For example, the directory structure is as follows.
# generated by `axios`
gen/server-endponin

# generated by `swr`
gen/client-endponin

But you say you don't want that. In other words, rather than managing two generators, you want to satisfy both with one generator.
Could you please explain in more detail why the above method is insufficient?

@soartec-lab Because the models will be generated by each of the generators, it will create a mess with imports since 1 and the same API. And swr client already uses axios and exports the necessary functions.

I understand. It's true that if you're using both, it's confusing and difficult to use. I change the label to enhancement.

I figured out an undocumented feature, that the models can be generated without generating endpoints and the endpoint generators can be pointed to models generated by the model generator 🤷 I found it surprising but it actually works, although there was a bit of a hiccup that the API exports also reexported the models, so I had to disable index files there. I managed to achieve the desired result by using multiple entries in the config file like so:
export default defineConfig({
  myapi: {
    input,
    output: {
      mode: 'tags-split',
      workspace: './build/openapi/myapi',
      schemas: './models',
    },
  },
  myapiClient: {
    input,
    output: {
      mode: 'tags',
      workspace: './build/openapi/myapi',
      target: './api/client',
      schemas: './models',
      indexFiles: false,
      client: 'swr',
      override: {
        mutator: {
          path: '../../../src/orval-mutator/custom-client-instance.ts',
          name: 'customInstance',
        },
      },
    },
  },
  myapiServer: {
    input,
    output: {
      mode: 'tags',
      workspace: './build/openapi/myapi',
      target: './api/server',
      schemas: './models',
      indexFiles: false,
      override: {
        mutator: {
          path: '../../../src/orval-mutator/custom-server-instance.ts',
          name: 'customInstance',
        },
      },
    },
  },
});

and then in tsconfig.json:
"@myapi/api": ["./build/openapi/myapi/index.ts"],
"@myapi/api/client/*": ["./build/openapi/myapi/api/client/*"],
"@myapi/api/server/*": ["./build/openapi/myapi/api/server/*"],

Maybe simply the documentation can be improved to have some sort of article with advanced stuff and maybe no need to complicate the implementation.

I've found a workaround for this edge case so closing


Can't reproduce DQN performance

I noticed you changed the optimizer and some hyper-parameters in DQN compared to those in the "Nature" paper, well, from my side I can't reproduce results by taking any of the two settings, could you share a learning curve of "Breakout"? I have been struggling with the hyper-parameters optimization for two months. Thanks.

Hi there.
This agent is intended to be a simple instantiation of the DQN algorithm (Q-learning + non-linear function approximation + experience replay), and isn't intended to reproduce the Nature Atari results. There are numerous subtleties related to interfacing with Atari (frame stacking, reward clipping, etc) that can be tricky to get right. For agents that are set up to run on Atari, see Dopamine (github.com/google/dopamine) or OpenAI baselines (github.com/openai/baselines)

Hi there.
This agent is intended to be a simple instantiation of the DQN algorithm (Q-learning + non-linear function approximation + experience replay), and isn't intended to reproduce the Nature Atari results. There are numerous subtleties related to interfacing with Atari (frame stacking, reward clipping, etc) that can be tricky to get right. For agents that are set up to run on Atari, see Dopamine (github.com/google/dopamine) or OpenAI baselines (github.com/openai/baselines)

Got it, thanks a lot.


fix(autoware_image_projection_based_fusion): fix clang-diagnostic-unused-private-field

Description
This is a fix based on clang-tidy clang-diagnostic-unused-private-field error.
The following PR was mistakenly assumed to be in use but was deleted as it was not actually being utilized.
/home/emb4/autoware/autoware/src/universe/autoware.universe/perception/autoware_image_projection_based_fusion/include/autoware/image_projection_based_fusion/debugger.hpp:59:18: error: private field 'node_ptr_' is not used [clang-diagnostic-unused-private-field]
  rclcpp::Node * node_ptr_;
                 ^

Related links
Parent Issue:

#9473

How was this PR tested?
Notes for reviewers
None.
Interface changes
None.

Effects on system behavior
None.

@badai-nguyen @kminoda @ktro2828 @miursh @tzhong518 @YoshiRi @yukkysaito
Please confirm the PR. Thank you very much.


can we make connection  between recast bot and wordpress website ???

yes, in the html you add your webchat script that you can find in "connect" on the builder


change redis.conf directory for RedHat systems

Hi,
I would like to see the redis.conf in a sub directory of /etc, not in /etc itself.
I think there is no reason to keep the file up there.
Kind regards,
tobias

// , Are you thinking of something like /etc/redis.d/ ?
Also, shouldn't you update the test suite?
This apparently breaks the build.

@tobiasschaber the redis.conf file in RedHat is /etc/redis.conf in the provided RPM:
%config(noreplace) %attr(0644, root, root) "/etc/logrotate.d/redis"
%config(noreplace) %attr(0644, redis, root) "/etc/redis-sentinel.conf"
%config(noreplace) %attr(0644, redis, root) "/etc/redis.conf"

If you wish to change it,
Changing the default param would be an breaking change to the module.
If you wish to provide a different path, you would just call the class with a different path:
class { 'redis':
  config_file => '/etc/redis/redis.conf',
}

As far as I can see from the module and reading the redis docs, there's no need for a config dir at all unless you're moving it from it's default location at /etc/redis.conf

Closing as default does not need to be changed, can be given as parameter


Node runtime version is inconsistent with console version

When using Node 8.9.0 with native support for async await, async function entry points do not work as function invocation.
Testing using the console works.
Investigative information

Timestamp: 2017-11-27T18:29:48.290
Function App version (1.0 or 2.0-beta): ~1.0 1.0.11388.0
Invocation ID: 7e94b5c4-b789-4cee-9b4b-f87ee87963fc
Region: West-Europe

Repro steps
async function reproFunction(context, myTimer) {
   return Promise.resolve('done');
}

module.exports = reproFunction;

Expected behavior
Should succeed with Node 8
Actual behavior
2017-11-27T18:33:47.266 Exception while executing function: Functions.xxx. mscorlib: One or more errors occurred. D:\home\site\wwwroot\xxx\build\index.js:7
async function reproFunction(context, myTimer) {
      ^^^^^^^^

SyntaxError: Unexpected token function
    at createScript (vm.js:56:10)
    at Object.runInThisContext (vm.js:97:10)
    at Module._compile (module.js:542:28)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at eval (eval at compileFunc (D:\Program Files (x86)\SiteExtensions\Functions\1.0.11388\bin\edge\double_edge.js:34:28), <anonymous>:1:80).
2017-11-27T18:33:47.344 Function completed (Failure, Id=d3aac6fc-8395-428a-930e-93e232800e54, Duration=239ms)

Related information
Provide any related information

Programming language used: Typescript -> JS

I have the environment variable WEBSITE_NODE_DEFAULT_VERSION set to 8.9.0
running node --version in any console logs 8.9.0
But I just tried,
function reproFunction(context, timer) {
context.log(process.version)
}

and I get v6.11.2
That's the source of the problem. Is there a way to change the runtime version of nodejs to match the one used in the console?

Are you running V1 or V2 (beta) when on Azure?

@fabiocav I'm running v1

@fabiocav I'm running v1

Unfortunately, in V1, you cannot change the Node version used by Azure Functions, as we're locked to what we build against. This is one of the benefits of the new V2 model.


I think fetchgit is broken

Commit https://github.com/NixOS/nixpkgs/commit/2cf7069b7da368326b51520536ac0f1020157f7a seems to have broken my calls to fetchgit:
Bash complains that it cannot execute the binary file. I noticed this when building gitAndTools.hub against nixpkgs 84b3af19b826cbab1cff4b26c0c53ee1d6e83ea3. Removing @peti's change makes it work again.

How do you call fetchgit and what error message do you get?

gitAndTools.hub compiles fine for me in the current unstable channel at b1dca6ca881e3e5864c60a2ef206579ce4d718b1.

It is broken for me as well. I am building NixOS on top of the current master. For me it fails for gnulib with:
/nix/store/33k6qnz10brkf66lr6yav6bcl4bhy5z0-bash-4.3-p42/bin/bash: /nix/store/33k6qnz10brkf66lr6yav6bcl4bhy5z0-bash-4.3-p42/bin/bash: cannot execute binary file
I guess that it uses /nix/*/bash /nix/*/bash as shell for calling nix-prefetch-git. I think this happens because as soon as you make the value of fetcher a string it will be executed with bash. The command does call bash itself so bash tries to call bash.

Please try version b89514eced6d32203982c54e0ad8c2f83dbca900 and let me know if that patch didn't do the trick.

:+1: thanks that fixed it.


where does Where cloudRIG save your machine in case you are being booted off?

Or when you manually stop the from the cloudrig GUI?
I looked under both of my EBS and snapshot windows and I don't see anything left over.
Also I check my s3 bucket and I don't see any cloudrig s3 bucket
How did you persist the content between instance ids?

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Never mind I see the AMI and the snapshots in my account


babel_preset_1.getTemplateProcessor is not a function (While processing: "base$2")

screenshot:

I searched in the corresponding repository (no results in twstyled's fork, yet in parent repo). I suspect that the 3.0.0-beta version exported this to delete? because the function exists
twstyled forked (note code is 0)

parent repo

Hi, I get sam err with u. and i delete node_modules rm -rf node_modules then yarn again.
It is ok.
It is cause yarn install has some err.:smile: hope it is useful.

@lod61 i removed and still error


Handy updates!

Updates ISO package for #264
Closes #331

Adds a new input for folders that allows disabling archive-in-archive recursion.

Closes #325

This refactors some code to more cleanly and correctly use the OutputPath parameter from the Starr Queue API.

Closes #272

Found a bug that leaves behind an empty temporary folder.

Re-does #304 by moving stderr to a config option.

Hiding errors in std err is problematic for Windows and Portainer (at minimum).

Download here: https://unstable.golift.io

When is this plan to be released? Just to know when to change back to a pinned version. Thanks :)

I'll try to get a release out in September.


reel_board: Do not include Bluetooth to every project

Including Bluetooth to every project unnecessary increase size of the
project, for example hello world sizes:
Memory region         Used Size  Region Size  %age Used
FLASH:       48492 B         1 MB      4.62%
SRAM:       11236 B       256 KB      4.29%
IDT_LIST:         136 B         2 KB      6.64%
after the patch:
Memory region         Used Size  Region Size  %age Used
FLASH:       13344 B         1 MB      1.27%
SRAM:        4004 B       256 KB      1.53%
IDT_LIST:          72 B         2 KB      3.52%
3+ times difference.
PS: It also crashes when 802.15.4 enabled.
Signed-off-by: Andrei Emeltchenko<EMAIL_ADDRESS>

Codecov Report

Merging #11614 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #11614   +/-   ##
=======================================
  Coverage   48.22%   48.22%
=======================================
  Files         279      279
  Lines       43285    43285
  Branches    10357    10357
=======================================
  Hits        20875    20875
  Misses      18270    18270
  Partials     4140     4140

Continue to review full report at Codecov.

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


DLRS will not count.

I just installed the DLRS managed package to my sandbox to count all the Campaign_Design_Profile__c (custom object) to the opportunity object. This is tied from the CDP to opportunities as a look up relationship. I put in all of the information (Image below) but it doesn't seem to be couting anything and just has a blank. I am wondering if there is anything that I am currently doing incorrectly?
Opportunity.Active_CDP_s__c is a number field. Is there an issue with that?

Change the field to aggregate to be ID
On Mar 31, 2017 3:53 PM, "jsacpt24"<EMAIL_ADDRESS>wrote:

I just installed the DLRS managed package to my sandbox to count all the
Campaign_Design_Profile__c (custom object) to the opportunity object. This
is tied from the CDP to opportunities as a look up relationship. I put in
all of the information (Image below) but it doesn't seem to be couting
anything and just has a blank. I am wondering if there is anything that I
am currently doing incorrectly?
Opportunity.Active_CDP_s__c is a number field. Is there an issue with that?
[image: dlrs]
https://cloud.githubusercontent.com/assets/16501949/24572004/04eda1d4-162a-11e7-863c-42762dd6919f.PNG
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/afawcett/declarative-lookup-rollup-summaries/issues/484,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APXKqqdYsiI84I5L6z86Pz3dy-1eyz9Sks5rrYPWgaJpZM4MwPQB
.


Update dependencies

I ran through all npm scripts, checked all tests and built code, nothing fails with all new deps.

should add react-engine and reactjs to this as well

Adding new stuff is off this one I believe. It's only about updating existing deps.

@nkbt should we be doing pr on the universal branch to update package.json file than? and also merging to that branch for all updates and tasks?

If you need to add dependency for particular issue - update package.json in your issue accordingly. No need to separate the change obviously.
If you are about update other deps not related to your issue - separate PR then.
Being captain obvious: in your PR include only updates related to the issue you are working on and strip out everything else that might be useful, but not related directly.

Ah, btw, this PR does nothing with #23. I made before making comment on #23.

So your saying just update my package.json which makes sense but if I try to get it merged it won't pass do to not having the dependencies.

Not sure I'm following you :). Just do not update package.json unless it is
required by the issue you are working on.
PS I'm off for now, sorry, will be back later.


Add selector support to json indexes

Adds selector support to json indexes. The selector can be used to filter what documents are
added to the index. When executing a query the index will
only be choosen if the query selector contains the selector defined in
the index or if the index is defined via use_index.
Checklist

[x] Code is written and works correctly;
[x] Changes are covered by tests;
[ ] Documentation reflects the changes;

Replaced by https://github.com/apache/couchdb/pull/808


Sync/cf218

Publishing CF218

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.3 out of 5 committers have signed the CLA.:white_check_mark: biancaluna:white_check_mark: sunilkn020:white_check_mark: VinayakPatilHcl:x: David Sayer:x: sunilkn002-hclDavid Sayer seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


delete unused import

Feel free to just let me know if you don't want me to touch deno.json

@itohatweb if you dont like me adding noUnusedLocals to deno.json just let me know and I will immediately commit and push that file without my changes

Do not touch deno.json

Do not touch deno.json

@itohatweb Done. You can review now


How to classify PNG?

Hello, I tried to classify a png image in nodejs, but it throws an exception: Size (357604) must match the product of 1,299,299,3 shapes.
How can this be resolved?

I assume you were trying to classify on node?

I assume you were trying to classify on node?
Have you looked at how to convert a PNG to a tensor? https://stackoverflow.com/questions/53231699/converting-png-to-tensor-tensorflow-js

@GantMan Thank you very much for your reply, this issue has been resolved.
I am now experiencing another problem. I trained a batch of images with nsfw_model / train_all_model.sh (using https://tfhub.dev/google/imagenet/mobilenet_v2_140_224/classification/4) and then I used tensorflowjs- The converter converted from keras or keras_saved_model to tfjs_layer_model and succeeded. But when I reference the model in nsfwjs-node, I get an error message:
2020-04-02 15:45:40,085 ERROR 70582 nodejs.unhandledRejectionError: Unknown layer: KerasLayer. This may be due to one of the following reasons:
1. The layer is defined in Python, in which case it needs to be ported to TensorFlow.js or your JavaScript code.
2. The custom layer is defined in JavaScript, but is not registered properly with tf.serialization.registerClass().
1. The layer is defined in Python, in which case it needs to be ported to TensorFlow.js or your JavaScript code.
2. The custom layer is defined in JavaScript, but is not registered properly with tf.serialization.registerClass().
    at new ValueError (/Users/wuguofeng/www/nodejs/classify/node_modules/nsfwjs-node/node_modules/@tensorflow/tfjs-layers/dist/errors.js:68:28)
    at Object.deserializeKerasObject (/Users/wuguofeng/www/nodejs/classify/node_modules/nsfwjs-node/node_modules/@tensorflow/tfjs-layers/dist/utils/generic_utils.js:260:19)
    at Object.deserialize (/Users/wuguofeng/www/nodejs/classify/node_modules/nsfwjs-node/node_modules/@tensorflow/tfjs-layers/dist/layers/serialization.js:29:28)
    at Sequential.fromConfig (/Users/wuguofeng/www/nodejs/classify/node_modules/nsfwjs-node/node_modules/@tensorflow/tfjs-layers/dist/models.js:958:41)
    at Object.deserializeKerasObject (/Users/wuguofeng/www/nodejs/classify/node_modules/nsfwjs-node/node_modules/@tensorflow/tfjs-layers/dist/utils/generic_utils.js:294:29)
    at Object.deserialize (/Users/wuguofeng/www/nodejs/classify/node_modules/nsfwjs-node/node_modules/@tensorflow/tfjs-layers/dist/layers/serialization.js:29:28)
    at /Users/wuguofeng/www/nodejs/classify/node_modules/nsfwjs-node/node_modules/@tensorflow/tfjs-layers/dist/models.js:290:45
    at step (/Users/wuguofeng/www/nodejs/classify/node_modules/nsfwjs-node/node_modules/@tensorflow/tfjs-layers/dist/models.js:54:23)
    at Object.next (/Users/wuguofeng/www/nodejs/classify/node_modules/nsfwjs-node/node_modules/@tensorflow/tfjs-layers/dist/models.js:35:53)
    at fulfilled (/Users/wuguofeng/www/nodejs/classify/node_modules/nsfwjs-node/node_modules/@tensorflow/tfjs-layers/dist/models.js:26:58)
name: "unhandledRejectionError"
pid: 70582
hostname: bogon

How should I train the models that nsfwjs-node can use?
Looking forward to your reply, thank you again!


Update makeOptions and SwiftOptions.

A new ModuleInterfaceOptionIgnorable as added to Options.inc, so makeOptions.cpp needed to be updated.

@swift-ci test


adding functionality such as update ,delete on each post

1.Add update option on post
2.Add delete option in the post so that a user can delete his/her post
I would like to work on it as a part of GSSOC'21
Can you please assign this work to me.

I would like to work on this issue.Please /assign this to me as a part of GSSOC'21

I would like to work on this issue.Please assign this to me as a part of GSSOC'21

Delete function on each post is already added. The feature is, the author of the post can only delete the post.

And update also after editing

Hi @Pranav016,  i would like to work on this issue.

Hello @Pranav016, Can you please tell me whether I can start working on this issue?

Hello @Pranav016, Can you please tell me whether I can start working on this issue?

Yes. You can start working. I've already assigned you the issue.


USB: Fix Coverity issues

Cherry-picked 2 patches from another PR to avoid conflicts
Fixes #14957
Fixes #14954

Codecov Report

Merging #14977 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master   #14977      +/-   ##
==========================================
- Coverage   52.93%   52.92%   -0.01%
==========================================
  Files         309      309
  Lines       45251    45257       +6
  Branches    10447    10453       +6
==========================================
  Hits        23953    23953
- Misses      16533    16539       +6
  Partials     4765     4765

Impacted Files
Coverage Δ

subsys/usb/usb_device.c
11.24% <0%> (-0.14%)
:arrow_down:

Continue to review full report at Codecov.

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

@finikorg any updates? This is blocking the release.

@jfischer-phytec-iot I have added PR #15140 to handle maximum-spedd issue, after it is merged we may add speed check.

@finikorg any updates? This is blocking the release.

Rebased and fixed conflicts.

@jfischer-phytec-iot I added offloading MPS check to usb device controller, depending on the mode it would check parameters. They need to add checking for MPS, I propose for now support only Full Speed.

I would add also unit test but we are stuck with problem merging before release (following patch #14874)

closing due to alternative fix


Errorformat tsc

Hello!
I'm trying out this cool but more advanced plugin. But I can't seem to produce any results with the custom "on_output_quickfix" -> errorformat command. Passing %f works, but then it gives me the whole error log. I'm apparently not able to really refine it deeper.
I want to implement the already working errorformat from withing the official tsc compiler in the vim repo.
I'm not able to produce any results using the same approach as showcased in the cargo template here.
This is an example of what I tried. I'm running the tsc --watch command here.
{
	"on_output_quickfix",
	open = not params.bang,
	close = true,
	items_only = true, -- only show items, not errors
	open_height = 8,
	open_on_match = true,
	set_diagnostics = true,
	tail = true,
	errorformat = [[%f\ %#(%l\\,%c):\ %trror\ TS%n:\ %m,]]
		.. [[\%trror\ TS%n:\ %m,]]
		.. [[\%-G%.%#]]
},

I don't want to post all examples but I've tried a lot of things :P.
"%f(%l,%c): %trror TS%%d: %%m,%f(%l,%c): %tarning TS%%d: %%m,%-G%.%#",
"%f:%l:%c: - %t TS%n: %m",
"%f" -- this works.. kinda. But outputs the whole error log.
Any ideas to what I might be doing wrong?

There is also a second part to the question. When running the command above with tail set to true, it indeed tails the output as expected. But I was wondering if it would be possible to somehow clear the quickfix menu every time the watch command does a rebuild and produces an updated list of errors. Its quite cumbersome to have have the qf list being populated with all the past errors as well. I'd like it to only show the active errors at all time. Do you think this is possible? Did I miss this option? Or does it not yet exist inside the current scope of the plugin?
To give a bit more context, I wish to have my tsc --watch command output all the active error every time a change has been spotted. Right now it also outputs the compilation messages and the history of all previous messages. With the first part of my question I'm trying to filter out these compilation messages. And with the second part I'm trying to filter out the old errors from the qflist whenever the watch command reloads.

If there is a better way to achieve this, I'm definitely all eyes and ears :).
Thank you very much for your time...

I also got errors using the built-in problem matchers. I use $gcc and the error says something about “autoDetect not found"

So there's the question you're asking: "how can I use on_output_quickfix and errorformat to parse the output of tsc --watch, and clear the quickfix whenever it restarts"
And there's the implicit question of "I want to parse the output of tsc --watch and clear the quickfix when it restarts. How can I best do this?"
It is easier to answer the second one, because there are better tools for this available that don't use on_output_quickfix and errorformat, but if you do really want to use that implementation let me know, because it is possible it's just more work right now.
Option 1: VS Code tasks.json format
Turns out this is a common task for people that use VS Code, and so there are pretty good builtins for handling it. Create a .vscode/tasks.json file and add the following contents:
{
  "version": "2.0.0",
  "tasks": [
    {
      "type": "shell",
      "command": "tsc --watch",
      "problemMatcher": "$tsc-watch"
    }
  ]
}

This will launch tsc --watch and parse the output. Each time it detects changes a re-runs, we'll clear the diagnostics & quickfix and repopulate the results. The default_vscode component alias should contain both on_result_diagnostics, which will put the parsed results into vim.diagnostic, and on_result_diagnostics_quickfix, which will put them into the quickfix list.
Option 2: Define in lua
Here's an example of the same task defined in lua:
overseer.register_template({
  name = "tsc --watch",
  builder = function()
    return {
      cmd = { "tsc", "--watch" },
      components = {
        "default",
        { "on_output_parse", problem_matcher = "$tsc-watch" },
        "on_result_diagnostics",
        "on_result_diagnostics_quickfix",
      },
    }
  end,
})

This is still using VS Code's problem matchers for parsing the output. If you want to define your own using a parser instead of a problem_matcher, that will be a more involved process. The translation from problem_matcher-to-parser makes use of parser.lib.watcher_output, which you can re-use to get the same structure.

Hey Steve!
Option 2 is exactly what I wanted. I feel like there is so much possible with this plugin, but for now that's all I needed.
Thanks a lot for your detailed reply.


Multiple schemas from same model give KeyError on model_name_map

MWE: (main.py)
from fastapi import FastAPI
from pydantic_sqlalchemy import sqlalchemy_to_pydantic
from sqlalchemy import Column, Integer, String, create_engine
from sqlalchemy.ext.declarative import declarative_base
from sqlalchemy.orm import Session, sessionmaker

Base = declarative_base()

engine = create_engine("sqlite://", echo=True)

class User(Base):
    __tablename__ = "users"

    id = Column(Integer, primary_key=True)
    name = Column(String)

PydanticUser1 = sqlalchemy_to_pydantic(User)
PydanticUser2 = sqlalchemy_to_pydantic(User, exclude=["id"])

Base.metadata.create_all(engine)

LocalSession = sessionmaker(bind=engine)

db: Session = LocalSession()

app = FastAPI()

@app.get("/user1", response_model=PydanticUser1)
def get_user1():
    return {"Hello": "World"}

@app.get("/user2", response_model=PydanticUser2)
def get_user2():
    return {"Hello": "World"}

Output: (uvicorn main:app --reload)
IINFO:     Started server process [149476]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     <IP_ADDRESS>:43332 - "GET /docs HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:43332 - "GET /openapi.json HTTP/1.1" 500 Internal Server Error
ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File "./venv/lib/python3.9/site-packages/uvicorn/protocols/http/h11_impl.py", line 394, in run_asgi
    result = await app(self.scope, self.receive, self.send)
  File "./venv/lib/python3.9/site-packages/uvicorn/middleware/proxy_headers.py", line 45, in __call__
    return await self.app(scope, receive, send)
  File "./venv/lib/python3.9/site-packages/fastapi/applications.py", line 199, in __call__
    await super().__call__(scope, receive, send)
  File "./venv/lib/python3.9/site-packages/starlette/applications.py", line 111, in __call__
    await self.middleware_stack(scope, receive, send)
  File "./venv/lib/python3.9/site-packages/starlette/middleware/errors.py", line 181, in __call__
    raise exc from None
  File "./venv/lib/python3.9/site-packages/starlette/middleware/errors.py", line 159, in __call__
    await self.app(scope, receive, _send)
  File "./venv/lib/python3.9/site-packages/starlette/exceptions.py", line 82, in __call__
    raise exc from None
  File "./venv/lib/python3.9/site-packages/starlette/exceptions.py", line 71, in __call__
    await self.app(scope, receive, sender)
  File "./venv/lib/python3.9/site-packages/starlette/routing.py", line 566, in __call__
    await route.handle(scope, receive, send)
  File "./venv/lib/python3.9/site-packages/starlette/routing.py", line 227, in handle
    await self.app(scope, receive, send)
  File "./venv/lib/python3.9/site-packages/starlette/routing.py", line 41, in app
    response = await func(request)
  File "./venv/lib/python3.9/site-packages/fastapi/applications.py", line 152, in openapi
    return JSONResponse(self.openapi())
  File "./venv/lib/python3.9/site-packages/fastapi/applications.py", line 130, in openapi
    self.openapi_schema = get_openapi(
  File "./venv/lib/python3.9/site-packages/fastapi/openapi/utils.py", line 354, in get_openapi
    definitions = get_model_definitions(
  File "./venv/lib/python3.9/site-packages/fastapi/utils.py", line 28, in get_model_definitions
    model_name = model_name_map[model]
KeyError: <class 'pydantic.main.User'>

Having the same issue. We want to use it as such:
PydanticTesting = sqlalchemy_to_pydantic(Testing) PydanticCreateTesting = sqlalchemy_to_pydantic(Testing, exclude=['id']) PydanticUpdateTesting = sqlalchemy_to_pydantic(Testing, exclude=['id', 'company_id'])
We want to use PydanticCreateTesting or PydanticUpdateTesting as body parameters for POST and PUT requests, and PydanticTesting as the response_model.

a hacky solution, not sure if it is 100% correct but it works
PydanticUser1 = sqlalchemy_to_pydantic(User)
PydanticUser1.__name__ = "PydanticUser1"
PydanticUser2 = sqlalchemy_to_pydantic(User, exclude=["id"])
PydanticUser2.__name__ = "PydanticUser2"

The Problem is, that FastAPI is using a Dictionary with the ModelClassName aka name as a Index. This isn't a Problem of the package itself.


nvidia-gpu-operator namespace issue

I am using OpenShift with Client Version: v4.2.0-alpha.0-1420-gf1f09a3, Server Version: 4.9.18, Kubernetes Version: v1.22.3+e790d7f to deploy a simple hello world job using MCAD AppWrapper.
I'm using the following hello world example file to create an appwrapper job:
apiVersion: mcad.ibm.com/v1beta1
kind: AppWrapper
metadata:
  name: aw-helloworld
  namespace: default
spec:
  resources:
    GenericItems:
      - replicas: 1
        generictemplate:
          apiVersion: v1
          kind: Pod
          metadata:
            name: helloworld
            labels:
              app: helloworld
          spec:
            containers:
              - name: helloworld
                image: vishakharamani/torchximgrepov1:myfirstimagepush

When you set the namespace to default, I can see the appwrapper and the pod associated getting created. However, if one sets the namespace to be nvidia-gpu-operator, only app wrapper is created and I see no pods associated with it.
to debug this I ran oc get appwrapper  aw-helloworld -oyaml, we get the following output:
apiVersion: mcad.ibm.com/v1beta1
kind: AppWrapper
metadata:
  creationTimestamp: "2022-07-14T13:41:47Z"
  generation: 7
  name: aw-helloworld
  namespace: nvidia-gpu-operator
  resourceVersion: "29656480"
  uid: bad4de28-cd2e-425b-89b4-81dfb8594319
spec:
  resources:
    GenericItems:
    - allocated: 0
      generictemplate:
        apiVersion: v1
        kind: Pod
        metadata:
          labels:
            app: helloworld
          name: helloworld
        spec:
          containers:
          - image: vishakharamani/torchximgrepov1:myfirstimagepush
            name: helloworld
      metadata: {}
      priority: 0
      priorityslope: 0
      replicas: 1
    metadata: {}
  schedulingSpec: {}
  service:
    spec: {}
status:
  canrun: true
  conditions:
  - lastTransitionMicroTime: "2022-07-14T13:41:47.611624Z"
    lastUpdateMicroTime: "2022-07-14T13:41:47.611622Z"
    status: "True"
    type: Init
  - lastTransitionMicroTime: "2022-07-14T13:41:47.611819Z"
    lastUpdateMicroTime: "2022-07-14T13:41:47.611819Z"
    reason: AwaitingHeadOfLine
    status: "True"
    type: Queueing
  - lastTransitionMicroTime: "2022-07-14T13:41:47.629030Z"
    lastUpdateMicroTime: "2022-07-14T13:41:47.629029Z"
    reason: FrontOfQueue.
    status: "True"
    type: HeadOfLine
  - lastTransitionMicroTime: "2022-07-14T13:41:48.737855Z"
    lastUpdateMicroTime: "2022-07-14T13:41:48.737854Z"
    reason: AppWrapperRunnable
    status: "True"
    type: Dispatched
  controllerfirsttimestamp: "2022-07-14T13:41:47.611496Z"
  filterignore: true
  queuejobstate: Dispatched
  sender: before manageQueueJob - podPhaseChanges
  state: Running

@vishakha-ramani @dmatch01 I can see that pods are being created by MCAD on the default namespace from podbug namespace in Minikube:
(base) asmalvan@mcad-dev:~/multi-cluster-app-dispatcher/deployment$ kubectl config view --minify -o jsonpath='{..namespace}'
podbug
(base) asmalvan@mcad-dev:~/multi-cluster-app-dispatcher/deployment$ kubectl apply -f /home/asmalvan/multi-cluster-app-dispatcher/deployment/pod_bug.yaml
appwrapper.mcad.ibm.com/aw-helloworld created
(base) asmalvan@mcad-dev:~/multi-cluster-app-dispatcher/deployment$ kubectl get pods -n default
NAME         READY   STATUS             RESTARTS     AGE
helloworld   0/1     CrashLoopBackOff   1 (9s ago)   11s

Could be the case that openshift does not allow pod creation from one namespace to another for all user accounts.

I ran this exp on another openshift cluster, looks to me like a cluster config issue, do we agree?:

    Status:                      True
    Type:                        HeadOfLine
    Last Transition Micro Time:  2022-07-25T14:11:17.177540Z
    Last Update Micro Time:      2022-07-25T14:11:17.177539Z
    Reason:                      AppWrapperNotRunnable.

    Status:                      True
    Type:                        HeadOfLine
    Last Transition Micro Time:  2022-08-01T23:31:11.837030Z
    Last Update Micro Time:      2022-08-01T23:31:11.837028Z
    Reason:                      AppWrapperRunnable
    Status:                      True
    Type:                        Dispatched
  Controllerfirsttimestamp:      2022-08-01T23:31:10.124393Z
  Filterignore:                  true
  Pending:                       1
  Queuejobstate:                 Dispatched
  Sender:                        before manageQueueJob - podPhaseChanges
  State:                         Running
Events:                          <none>
Abhisheks-MBP:deployment abhishekmalvankar$ oc get pods -n default | grep hellp
Abhisheks-MBP:deployment abhishekmalvankar$ oc get pods -n default | grep hello
helloworld                                     0/1     ContainerCreating      0          90s

Abhisheks-MBP:deployment abhishekmalvankar$ oc project
Using project "nvidia-gpu-operator" on server

I think the issue is running the example in any namespace other than default.  Can you validate?

ok minikube does not seem to have this issue, as shown here https://github.com/IBM/multi-cluster-app-dispatcher/issues/190#issuecomment-1201824771

Below sample yaml works for now, runs on nvidia-gpu-operator namespace or can run in any other user specified namespace:
apiVersion: mcad.ibm.com/v1beta1
kind: AppWrapper
metadata:
  name: aw-helloworld
  namespace: nvidia-gpu-operator
spec:
  resources:
    GenericItems:
      - replicas: 1
        generictemplate:
          apiVersion: v1
          kind: Pod
          metadata:
            name: helloworld
            namespace: nvidia-gpu-operator
            labels:
              app: helloworld
          spec:
            containers:
              - name: helloworld
                image: vishakharamani/torchximgrepov1:myfirstimagepush

    Status:                      True
    Type:                        Backoff
    Last Transition Micro Time:  2022-08-02T15:30:08.050033Z
    Last Update Micro Time:      2022-08-02T15:30:08.050032Z
    Reason:                      AppWrapperRunnable
    Status:                      True
    Type:                        Dispatched
    Last Transition Micro Time:  2022-08-02T15:30:13.066646Z
    Last Update Micro Time:      2022-08-02T15:30:13.066645Z
    Reason:                      PodsRunning
    Status:                      True
    Type:                        Running
  Controllerfirsttimestamp:      2022-08-02T15:29:46.347409Z
  Filterignore:                  true
  Queuejobstate:                 Running
  Running:                       1
  Sender:                        before [syncQueueJob] setRunning
  State:                         Running
Events:                          <none>
Abhisheks-MBP:mcad-pod-status-2 abhishekmalvankar$ oc get pods | grep hello
helloworld                                           0/1     Completed   2 (23s ago)   27s
Abhisheks-MBP:mcad-pod-status-2 abhishekmalvankar$ oc project
Using project "nvidia-gpu-operator" on server "https://xxxx:6443".

@vishakha-ramani can you verify please?


Update Ruff version to latest

Regular update for Ruff to latest version when run through pre-commit hooks. The rationale for not allowing autoupdates can be found here.
Please complete the following checklist:

[ ] I have read the contribution guidelines.

[ ] I have documented all public-facing changes in the changelog.

[ ] This pull request includes code, documentation, or other content derived from external source(s). If this is the case, ensure the external source's license is compatible with scikit-bio's license. Include the license in the licenses directory and add a comment in the code giving proper attribution. Ensure any other requirements set forth by the license and/or author are satisfied.

It is your responsibility to disclose code, documentation, or other content derived from external source(s). If you have questions about whether something can be included in the project or how to give proper attribution, include those questions in your pull request and a reviewer will assist you.

[ ] This pull request does not include code, documentation, or other content derived from external source(s).

Note: This document may also be helpful to see some of the things code reviewers will be verifying when reviewing your pull request.

@mataton Thanks! Should I merge?

@qiyunzhu Yes whenever you can, thanks.


Allow users to switch their login theme (dark / light / auto)

Preflight Checklist

[X] I could not find a solution in the existing issues, docs, nor discussions
[X] I have joined the ZITADEL chat

Describe your problem
Currently, the ZITADEL login always renders according to the users browser settings. They can't be overwritten and set explicitly.
Describe your ideal solution
As a user, I want to configure my preferred theme, so the login pages are rendered in that theme.
Version
latest
Environment
ZITADEL Cloud
Additional Context
Console currently sets the theme in localstorage whereas theme.js reads the cookie value.
There is no possibility to save a users preferred theme in the cookies via console.

@eliobischof I think this would better be handled with the issue: #5505
Should we close this one therefore?


ROLE rsp format error

nutcracker.log
[2018-05-12 13:23:45.576] [05] nc_request.c:816 sent 'sentinel get-master-addr-by-name groups_helf_0' req to '<IP_ADDRESS>:26400'
[2018-05-12 13:23:45.576] [05] nc_request.c:816 sent 'sentinel get-master-addr-by-name groups_helf_1' req to '<IP_ADDRESS>:26400'
[2018-05-12 13:23:45.576] [05] nc_sentinel.c:195 recv 'get-master-addr-by-name' rsp from '<IP_ADDRESS>:26400'
[2018-05-12 13:23:45.576] [05] nc_sentinel.c:250 master of group 'groups_helf_0' is the same: '<IP_ADDRESS>:6400'
[2018-05-12 13:23:45.576] [05] nc_sentinel.c:195 recv 'get-master-addr-by-name' rsp from '<IP_ADDRESS>:26400'
[2018-05-12 13:23:45.576] [05] nc_sentinel.c:250 master of group 'groups_helf_1' is the same: '<IP_ADDRESS>:6401'
[2018-05-12 13:23:45.576] [05] nc_redis.c:2984 sent 'ROLE' req to alpha | <IP_ADDRESS>:6400
[2018-05-12 13:23:45.576] [05] nc_redis.c:2984 sent 'ROLE' req to alpha | <IP_ADDRESS>:6401
[2018-05-12 13:23:45.577] [05] nc_server.c:630 recv 'ROLE' rsp from redis
[2018-05-12 13:23:45.577] [01] nc_server.c:658 ROLE rsp format error on alpha | <IP_ADDRESS>:6400
[2018-05-12 13:23:45.577] [05] nc_server.c:630 recv 'ROLE' rsp from redis
[2018-05-12 13:23:45.577] [01] nc_server.c:658 ROLE rsp format error on alpha | <IP_ADDRESS>:6401
twemproxy-163.yaml
###################
alpha:
listen: <IP_ADDRESS>:6379
hash: murmur
hash_tag: "{}"
distribution: ketama
timeout: 400
groups:
- groups_helf_0
- groups_helf_1
sentinel_heartbeat: 2000
sentinels:
- <IP_ADDRESS>:26400 sentinel0
- <IP_ADDRESS>:26400 sentinel1
- <IP_ADDRESS>:26400 sentinel2
Redis version 2.8.3
sentinel.conf
#################
daemonize yes
port 26400
dir "/data/redis/redis_sentinels"
pidfile "/var/run/sentinel6400.pid"
logfile "/data/redis/redis_sentinels/sentinel6400.log"
sentinel monitor groups_helf_0 <IP_ADDRESS> 6400 2
sentinel down-after-milliseconds groups_helf_0 5000
sentinel parallel-syncs groups_helf_0 1
sentinel config-epoch groups_helf_0 0
sentinel monitor groups_helf_1 <IP_ADDRESS> 6401 2
sentinel down-after-milliseconds groups_helf_1 5000
sentinel parallel-syncs groups_helf_1 1
sentinel config-epoch groups_helf_1 0

@liuflylove666 so, your problem is ...?

nc_server.c:658 ROLE rsp format error on alpha | <IP_ADDRESS>:6401
Redis version 2.8.3  not support ROLE command

redis 2.8 release notes
--[ Redis 2.8.12 ] Release date: 23 Jun 2014

[NEW] ROLE command added. (Salvatore Sanfilippo)

You have to upgrade to version 2.8.12 at least before using twemproxy-163. This is not an issue.


Debug not working

As soon as I turn on the debug mode on the app, the server crash right away.
Result
node_modules/metro/node_modules/jsonfile/node_modules/graceful-fs/graceful-fs.js:177
    if (this instanceof ReadStream)
             ^

RangeError: Maximum call stack size exceeded
    at Function.[Symbol.hasInstance] (<anonymous>)
    at ReadStream (node_modules/metro/node_modules/jsonfile/node_modules/graceful-fs/graceful-fs.js:177:14)
    at ReadStream (node_modules/metro/node_modules/jsonfile/node_modules/graceful-fs/graceful-fs.js:178:28)
    at ReadStream (node_modules/metro/node_modules/jsonfile/node_modules/graceful-fs/graceful-fs.js:178:28)
    at ReadStream (node_modules/metro/node_modules/jsonfile/node_modules/graceful-fs/graceful-fs.js:178:28)
    at ReadStream (node_modules/metro/node_modules/jsonfile/node_modules/graceful-fs/graceful-fs.js:178:28)
    at ReadStream (node_modules/metro/node_modules/jsonfile/node_modules/graceful-fs/graceful-fs.js:178:28)
    at ReadStream (node_modules/metro/node_modules/jsonfile/node_modules/graceful-fs/graceful-fs.js:178:28)
    at ReadStream (node_modules/metro/node_modules/jsonfile/node_modules/graceful-fs/graceful-fs.js:178:28)
    at ReadStream (node_modules/metro/node_modules/jsonfile/node_modules/graceful-fs/graceful-fs.js:178:28)
error Command failed with exit code 1.

React Native version:
System:
    OS: macOS Mojave 10.14.6
    CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
    Memory: 176.78 MB / 16.00 GB
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 10.16.3 - /usr/local/bin/node
    Yarn: 1.17.3 - /usr/local/bin/yarn
    npm: 6.9.0 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 13.0, DriverKit 19.0, macOS 10.15, tvOS 13.0, watchOS 6.0
    Android SDK:
      API Levels: 29
      Build Tools: 29.0.2
      System Images: android-29 | Google APIs Intel x86 Atom_64
  IDEs:
    Android Studio: 3.5 AI-191.8<IP_ADDRESS>91312
    Xcode: 11.0/11A420a - /usr/bin/xcodebuild
  npmPackages:
    react: 16.9.0 => 16.9.0
    react-native: 0.61.1 => 0.61.1
  npmGlobalPackages:
    react-native-cli: 2.0.1
    react-native-rename: 2.4.1

Steps To Reproduce

Open developer menu
Turn on Debug mode
Server crashes right away

I also have this issue when I refresh the app, when debugger is enabled.

+1

@elkinjosetm Did you solve this problem yet?

After spending a couple of hours, I resolved my issue by:

Delete node_modules , yarn.lock, package.lock.json

Run yarn to re-install node_modules

Run watchman watch-del-all && rm -rf /tmp/metro-bundler-cache-* && rm -rf /tmp/haste-map-react-native-packager-* to clear cache

Re-build project and Turn on debug mode again. Then it worked!

It really looks like something related to caches: I can't repro locally, sorry. If you manage to create a more reliable repro we can reopen it, if not I would recommend what @nysamnang mentioned above.

After spending a couple of hours, I resolved my issue by:

Delete node_modules , yarn.lock, package.lock.json
Run yarn to re-install node_modules
Run watchman watch-del-all && rm -rf /tmp/metro-bundler-cache-* && rm -rf /tmp/haste-map-react-native-packager-* to clear cache
Re-build project and Turn on debug mode again. Then it worked!

Thanks, this worked!

It really looks like something related to caches: I can't repro locally, sorry. If you manage to create a more reliable repro we can reopen it, if not I would recommend what @nysamnang mentioned above.

It's ok, that's all I needed to do, thanks!


Cannot build/dev main

Hi,
I'm following the quick start instructions but here are the errors:
▶ npm run dev

> dev
> vite

  VITE v5.4.2  ready in 151 ms

  ➜  Local:   http://localhost:20001/
  ➜  Network: use --host to expose
  ➜  press h + enter to show help
Error:   Failed to scan for dependencies from entries:
  /git/monaco-languageclient/index.html
/git/monaco-languageclient/packages/examples/bare.html
/git/monaco-languageclient/packages/examples/wrapper_ws.html
/git/monaco-languageclient/packages/examples/browser.html
/git/monaco-languageclient/packages/examples/wrapper_statemachine.html
/git/monaco-languageclient/packages/examples/wrapper_langium.html
/git/monaco-languageclient/packages/examples/python.html
/git/monaco-languageclient/packages/examples/groovy.html
/git/monaco-languageclient/packages/examples/react_statemachine.html
/git/monaco-languageclient/packages/examples/react_python.html
/git/monaco-languageclient/packages/examples/wrapper_ts.html
/git/monaco-languageclient/packages/examples/wrapper_adv.html

  ✘ [ERROR] Failed to resolve entry for package "@typefox/monaco-editor-react". The package may have incorrect main/module/exports specified in its package.json. [plugin vite:dep-scan]

    node_modules/vite/node_modules/esbuild/lib/main.js:1225:21:
      1225 │         let result = await callback({
           ╵                      ^

    at packageEntryFailure (file:///git/monaco-languageclient/node_modules/vite/dist/node/chunks/dep-BzOvws4Y.js:46541:15)
    at resolvePackageEntry (file:///git/monaco-languageclient/node_modules/vite/dist/node/chunks/dep-BzOvws4Y.js:46538:3)
    at tryNodeResolve (file:///git/monaco-languageclient/node_modules/vite/dist/node/chunks/dep-BzOvws4Y.js:46354:16)
    at ResolveIdContext.resolveId (file:///git/monaco-languageclient/node_modules/vite/dist/node/chunks/dep-BzOvws4Y.js:46104:19)
    at PluginContainer.resolveId (file:///git/monaco-languageclient/node_modules/vite/dist/node/chunks/dep-BzOvws4Y.js:48919:17)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async resolve (file:///git/monaco-languageclient/node_modules/vite/dist/node/chunks/dep-BzOvws4Y.js:49530:22)
    at async file:///git/monaco-languageclient/node_modules/vite/dist/node/chunks/dep-BzOvws4Y.js:49692:28
    at async requestCallbacks.on-resolve (/git/monaco-languageclient/node_modules/vite/node_modules/esbuild/lib/main.js:1225:22)
    at async handleRequest (/git/monaco-languageclient/node_modules/vite/node_modules/esbuild/lib/main.js:647:11)

  This error came from the "onResolve" callback registered here:

    node_modules/vite/node_modules/esbuild/lib/main.js:1150:20:
      1150 │       let promise = setup({
           ╵                     ^

    at setup (file:///git/monaco-languageclient/node_modules/vite/dist/node/chunks/dep-BzOvws4Y.js:49680:13)
    at handlePlugins (/git/monaco-languageclient/node_modules/vite/node_modules/esbuild/lib/main.js:1150:21)
    at buildOrContextImpl (/git/monaco-languageclient/node_modules/vite/node_modules/esbuild/lib/main.js:873:5)
    at Object.buildOrContext (/git/monaco-languageclient/node_modules/vite/node_modules/esbuild/lib/main.js:699:5)
    at /git/monaco-languageclient/node_modules/vite/node_modules/esbuild/lib/main.js:2032:68
    at new Promise (<anonymous>)
    at Object.context (/git/monaco-languageclient/node_modules/vite/node_modules/esbuild/lib/main.js:2032:27)
    at Object.context (/git/monaco-languageclient/node_modules/vite/node_modules/esbuild/lib/main.js:1874:58)
    at prepareEsbuildScanner (file:///git/monaco-languageclient/node_modules/vite/dist/node/chunks/dep-BzOvws4Y.js:49477:24)

  The plugin "vite:dep-scan" was triggered by this import

    packages/examples/src/langium/statemachine/main-react.tsx:8:38:
      8 │ import { MonacoEditorReactComp } from '@typefox/monaco-editor-react';
        ╵                                       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This after a clean clone and npm install

Hi  @rubenfiszel did you perform npm run build to build all local packages/libs first?

 Don't be to hard on yourself. 🙂


Specify target JDK version for Java

This prevents needing to use JDK 6/7 to build. You can use JDK 8 to
compile and it will still work with older JREs.
This is untested, because after installing node, npm, and dependencies I got this error when trying to run. After some more fiddling, I gave up.
/home/ejona/clients/packman/lib/api_repo.js:345
          var src = path.join(this.repoDir, protoPath),
                                  ^
TypeError: Cannot read property 'repoDir' of undefined

@tbetbetbe

Thanks for the fix!
I moved it to 701f9aa45bd795f3b23e20c82991508dabdb842b, part of #16 which fixes some bugs java package creation, so I'll close this now.  The type error you saw seems a bit odd, I'll follow-up offline to understand what went wrong.  It might be something that get's fixed in #16


The "set-output" command is deprecated and will be disabled soon.

Describe the bug
The set-output command is deprecated and will be disabled soon.
Which version of the action are you using?
v1
Environment
GitHub-hosted
Spark Versions
All
Screenshots

Additional context
Warning: The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

core.setOutput seems fixed in version 1.10.0 #1178
This affected file is setup-spark.ts

This warning has been fixed in core v1.10.0, which we are using here in the package-lock.json.  However, it does require the GITHUB_OUTPUT environment variable be set.

After Fix in PR #22 :

Note: Purple lines are Actions debug output.  Warnings are no longer shown in any capacity.


Dns checker

Pull Request Template
script name -
What have you Changed
what you changed in the codebase.write here
Issue no.(must) -
Self Check(Tick After Making pull Request)

[ ] This issue was assigned to me.
[x] One Change in one Pull Request
[x] My file is in proper folder (Name of folder should be in lowercase with no space in between)
[x] I am following clean code and Documentation and my code is well linted with flake8.
[x] I have added README.md and requirements.txt with my script

If issue was not assigned to you Please don't make a PR. It will marked as invalid.

Will you please remove .DS_Store file

Will you please remove .DS_Store file

done

That's awesome @aolaria. Leave a star in repo  ⭐ if you enjoy this

@all-contributors add @aolaria for code


An error when I run the train.py of LSTM-CNNs-CRF

Hi,I'm new to pytorch,when I run the train.py, I got error below, I try such ways to slove, bur all not work. How this error means,?Thanks.
`D:\workspace\Python\NLP\torch_light-master\LSTM-CNNs-CRF\model.py:158: UserWarning: nn.init.xavier_uniform is now deprecated in favor of nn.init.xavier_uniform_.
init.xavier_uniform(self.char_ebd.weight)
D:\workspace\Python\NLP\torch_light-master\LSTM-CNNs-CRF\model.py:31: UserWarning: nn.init.xavier_uniform is now deprecated in favor of nn.init.xavier_uniform_.
init.xavier_uniform(self.transitions)
D:\Program\Anaconda3\lib\site-packages\torch\cuda_init_.py:116: UserWarning:
Found GPU0 Quadro K600 which is of cuda capability 3.0.
PyTorch no longer supports this GPU because it is too old.
warnings.warn(old_gpu_warn % (d, name, major, capability[1]))
Train Processing: 0it [00:00, ?it/s]------------------------------------------------------------------------------------------
Traceback (most recent call last):
File "D:/workspace/Python/NLP/torch_light-master/LSTM-CNNs-CRF/train.py", line 148, in
loss = train()
File "D:/workspace/Python/NLP/torch_light-master/LSTM-CNNs-CRF/train.py", line 130, in train
loss, _ = model(word, char, label)
File "D:\Program\Anaconda3\lib\site-packages\torch\nn\modules\module.py", line 491, in call
result = self.forward(*input, **kwargs)
File "D:\workspace\Python\NLP\torch_light-master\LSTM-CNNs-CRF\model.py", line 187, in forward
char_feats = self.cnn(chars)
File "D:\Program\Anaconda3\lib\site-packages\torch\nn\modules\module.py", line 491, in call
result = self.forward(*input, **kwargs)
File "D:\workspace\Python\NLP\torch_light-master\LSTM-CNNs-CRF\model.py", line 163, in forward
encode = self.char_ebd(encode).unsqueeze(1)
File "D:\Program\Anaconda3\lib\site-packages\torch\nn\modules\module.py", line 491, in call
result = self.forward(*input, **kwargs)
File "D:\Program\Anaconda3\lib\site-packages\torch\nn\modules\sparse.py", line 108, in forward
self.norm_type, self.scale_grad_by_freq, self.sparse)
File "D:\Program\Anaconda3\lib\site-packages\torch\nn\functional.py", line 1076, in embedding
return torch.embedding(weight, input, padding_idx, scale_grad_by_freq, sparse)
RuntimeError: Expected tensor for argument #1 'indices' to have scalar type Long; but got CUDAIntTensor instead (while checking arguments for embedding)`

Found GPU0 Quadro K600 which is of cuda capability 3.0.
PyTorch no longer supports this GPU because it is too old.

Thanks for  replying,but that isn't the problem. I shut down the cuda ,and the error still be there. Then I change the line38 of  model.py to below:
`    def score_sentence(self, input, tags):
bsz, sent_len, l_size = input.size()
sco        re = Variable(self.torch.FloatTensor(bsz).fill(0.))
s_score = Variable(self.torch.LongTensor([[START]] * bsz)).long()
    tags = torch.cat([s_score, tags], dim=-1)
    input_t = input.transpose(0, 1)

The error is gone.You use pytorch0.2, and mine is pytorch 0.4,maybe there are some changes. And I have another question, hoping not bother you: in viterbi_decode() fuction,what's the meaning of the last element of variable best_path,the dimension shape of it is different from previous element,and that causetorch.cat(best_path, dim=-1)` raise an error.
Traceback (most recent call last):
File "D:/workspace/Python/NLP/torch_light-master/LSTM-CNNs-CRF/train.py", line 151, in
loss, corrects, acc, size = evaluate()
File "D:/workspace/Python/NLP/torch_light-master/LSTM-CNNs-CRF/train.py", line 111, in evaluate
pred = model.predict(word, char)
File "D:\workspace\Python\NLP\torch_light-master\LSTM-CNNs-CRF\model.py", line 198, in predict
return self.crf.viterbi_decode(out)
File "D:\workspace\Python\NLP\torch_light-master\LSTM-CNNs-CRF\model.py", line 108, in viterbi_decode
return torch.cat(best_path, dim=-1)
RuntimeError: invalid argument 0: Tensors must have same number of dimensions: got 2 and 1 at c:\users\administrator\downloads\new-builder\win-wheel\pytorch\aten\src\th\generic/THTensorMath.c:3577
I reshape it ,but the final result accuracy is always 0.00.
Thanks again.

i have fixed the issue
please update the code and train again
my pt version is updated to 0.4.0

OK，it works well,thanks, : ))


What is the difference between this and laravel-phpredis from vetruvet?

There is a more popular repository https://github.com/vetruvet/laravel-phpredis
Is there a reason why you created a new one other than the returning null instead of false if key doesn't exist?
Also the other repository supports sharding? https://github.com/vetruvet/laravel-phpredis/blob/master/src/Vetruvet/PhpRedis/Database.php#L10-L70
Which one would be better to use yours or the other one?

I'd give both a try.
If you encounter weird results with other packages, especially with Cache::has() returning true even if the cache key doesn't exists, then try this package.
I can add RedisArray support to this package, but it seems like Clustering with PhpRedis is not production ready, yet: https://github.com/phpredis/phpredis/issues/214


Grammar check does not work

The site is in Russian and for some reason it stopped emphasizing words with errors in Russian and English.

Hi @Vladorld - Wagtail does not provide a grammar checker. Are you using the Wagtail AI add-on package, perhaps?

@gasman I see what the problem is. It's Google Chrome emphasizing the errors)


karate.call() fails when large volumes of tests (involving call()) are run in parallel

Tests that involve calling a separate file to build a request are failing when run in parallel.  This happens most frequently when at least some of the tests are of the Scenario Outline variety and the called file itself has numerous references to yet another file (or files) - e.g. a Java file that uses Faker to generate data.
To reproduce, simply run the ExamplesTest.java file in the attached project (currently configured with a thread count of 10).  You should see at least 1 (if not 4 or 5) of these errors:
org.opentest4j.AssertionFailedError: failed features:
examples.users.call: [2.6:42] call.feature:30 - null
KarateReadNullIssue.zip

closing as duplicate of #1394
the most helpful thing you can do right now is follow the dev guide and verify, thanks: https://github.com/intuit/karate/wiki/Developer-Guide

closing as duplicate of #1394
the most helpful thing you can do right now is follow the dev guide and verify, thanks: https://github.com/intuit/karate/wiki/Developer-Guide

Thanks, Peter - will do!

Thanks, Peter - will do!

We're in the process of upgrading from 0.9.6 to 0.9.9.RC4 today, actually, so I should have feedback soon!


Update cloudwatch, dynamodb, kinesis, s3, sns, ... to 2.17.66

Updates

software.amazon.awssdk:cloudwatch
software.amazon.awssdk:dynamodb
software.amazon.awssdk:kinesis
software.amazon.awssdk:s3
software.amazon.awssdk:sns
software.amazon.awssdk:sqs
software.amazon.awssdk:sts

from 2.16.104 to 2.17.66.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

labels: library-update, semver-minor

Superseded by #763.


group boxes into lines with tolerance

This PR groups boxes into lines without assuming a perfect match of box.t. We use the 3rd decimal point which seems small enough but also big enough to catch most cases.
This PR also merges adjacent boxes belonging to a mention which might have 2 spans that are far apart. Instead of not doing anything in that case, it only merges boxes with associated spans that are close.

Looks like this will improve things but wondering if we could take advantage of PDFPlumber's line segmentation (rows) downstream to decide how to draw boxes

Just realized a version bump is needed here, I'm setting it to 0.9.11 in my PR but idk when mine will merge so feel free to take 0.9.11 if I don't get to it first


Update Dockerfile

Coverage remained the same at 98.025% when pulling 4aecf23a567e7a98642269346f3e90073fdb12b4 on irio-docker into 285a38ba818717faf50ca04a6656f8d39aa9f19b on master.

Closed in favor of #92


cache the ScramSHA1 salted passwords, capping the cache at 200 entries

restores the_hiCache functionality, but without the unbounded cache growth

@andrasq thanks for the contribution!