Add smt-encoding "strategy"

Towards meeting the short-term needs of https://github.com/informalsystems/apalache/issues/1099
The new strategy lets us get some immediate feedback on the performance of the array encoding vs. the oopsla encoding. The current ordering (10 using the oopsla encoding then 10 using the array encoding) is selected to show the trend in performance in the difference encodings as the length increases.
As per our discussion today, @rodrigo7491 will push any additional changes to this branch that he sees fit to meet the his near-term needs.

@rodrigo7491 here’s an example of the report generated with the current set up: https://github.com/informalsystems/apalache-tests/blob/46272492162fbef3ff80a401e71233ac99348424/results/010encoding-report.md

re: 1 -- How big would you like to go?
re: 2 -- As a stop-gap hack, we can use the makefile to generate all the csv files based on a script that takes a feww  params. However, if you want to extend the functionality much beyond this, then let's just pivot to taking a fresh approach to the benchmarking. Sound OK?

1: I'll start with 30 for now. And we can see see how long that takes to run.
2: Let's stick with the hack for now, as a rework will be much more involved, and we'll want requirements and an issue to track it.

Since you think this looks ok in general, I'm gonna merge this in, then will add the additional extensions as followup. This should give us the ability to start running the strategy in isolation to improve the feedback loop.

What about the failing check? It didn't failed because of the run itself, but because of a failed push. Do you know what it is about?

Yeah, that's just because we already had a branch open with the name of the version (i.e., we had concurrent benchmarks running and there was a race condition over the branch name).
It might indicate we'll want to give branches of reports more specific names, but that's not particularly related to this change :)


WARNING: Forward backward likelihood mismatch 0.000050

In my training phase, I am frequently getting this Warning

I am also getting the same Warning,
did you find any solution


Event.body is an object

I had a working lambda that handles basic get requests.  I had to implement the webpack serverless plugin recently for another issue, and now when a request is made, I get the following error:
2019-11-05T16:15:11.032Z 0055b8bf-3549-4acd-83b1-357c731b3803 INFO ERROR: aws-serverless-express error
2019-11-05T16:15:11.033Z 0055b8bf-3549-4acd-83b1-357c731b3803 ERROR TypeError [ERR_INVALID_ARG_TYPE]: The first argument must be one of type string, Buffer, ArrayBuffer, Array, or Array-like Object. Received type object
at Function.from (buffer.js:232:9)
at getEventBody (/var/task/node_modules/aws-serverless-express/src/index.js:25:17)
at mapApiGatewayEventToHttpRequest (/var/task/node_modules/aws-serverless-express/src/index.js:46:18)
at forwardRequestToNodeServer (/var/task/node_modules/aws-serverless-express/src/index.js:135:28)
at proxy (/var/task/node_modules/aws-serverless-express/src/index.js:202:7)
at Server.startServer.on (/var/task/node_modules/aws-serverless-express/src/index.js:206:32)
at Server.emit (events.js:203:15)
at Server.EventEmitter.emit (domain.js:448:20)
at emitListeningNT (net.js:1314:10)
at process._tickCallback (internal/process/next_tick.js:63:19)

I found the line added to aws-serverless-express that check for event.body and then uses it to set content-length, which is causing this issue as for some reason my event.body === {} now.
This did work prior to adding the serverless-webpack plugin, so unsure exactly what is going on however I did read the comments on that content-length PR, and one assumption was that event.body would always be a string so not totally sure what to do here.  Any help would be appreciated.
EDIT: If I manually change the empty object in event.body to an empty string '' then I get a different error regarding requestPath:
2019-11-05T17:38:48.956Z 15280953-68b6-4797-9204-ed0bc36910f6 INFO ERROR: aws-serverless-express error
2019-11-05T17:38:48.957Z 15280953-68b6-4797-9204-ed0bc36910f6 ERROR TypeError [ERR_UNESCAPED_CHARACTERS]: Request path contains unescaped characters
at new ClientRequest (_http_client.js:115:13)
at Object.request (http.js:42:10)
at forwardRequestToNodeServer (/var/task/node_modules/aws-serverless-express/src/index.js:136:22)
at proxy (/var/task/node_modules/aws-serverless-express/src/index.js:202:7)
at Server.startServer.on (/var/task/node_modules/aws-serverless-express/src/index.js:206:32)
at Server.emit (events.js:203:15)
at Server.EventEmitter.emit (domain.js:448:20)
at emitListeningNT (net.js:1314:10)
at process._tickCallback (internal/process/next_tick.js:63:19)

After seeing this and being unable to fix, I went back and ripped out the webpack plugin to go back to the typescript plugin.  Unfortunately, still get the same errors as above with that plugin as well.  No idea what else has changed since it was working right before initially adding the webpack plugin.

I am facing a similar issue, do anyone has a solution for this, In my organization, we are using our own API Gateway setup which triggers ALB Lambda API, when I call ALB directly using postman, everything works fine, but when I call via using the API Gateway(which trigger ALB). I am getting the below error.
instance of Buffer, ArrayBuffer, or Array or an Array-like Object. Received an instance of Object
at Function.from (buffer.js:331:9)
at getEventBody (/var/task/node_modules/aws-serverless-express/src/index.js:25:17)
at mapApiGatewayEventToHttpRequest (/var/task/node_modules/aws-serverless-express/src/index.js:46:18)
at forwardRequestToNodeServer (/var/task/node_modules/aws-serverless-express/src/index.js:135:28)
at Object.proxy (/var/task/node_modules/aws-serverless-express/src/index.js:202:7)
at Runtime.exports.handler (/var/task/index.js:24:26)
at Runtime.handleOnce (/var/runtime/Runtime.js:66:25) {
code: 'ERR_INVALID_ARG_TYPE'
}

I'm experiencing this issue as well.
When using Nest.js api:s using either "mystream.pipe(res)" for binary content or if I'm just returning a "string" then the Body response always becomes an empty object ("{}").
When I return a normal object then I get the full Json back, just as expected.
Example of a binary stream response:
`HTTP/1.1 200 OK
Date: Mon, 09 Nov 2020 15:42:19 GMT
Content-Type: application/octet-stream; charset=utf-8
Content-Length: 2
Connection: keep-alive
X-Powered-By: Express
etag: W/"2-vyGp6PvFo4RvsFtPoIWeCReyIC8"
Apigw-Requestid: Vvx1ZiKQIAMEJRg=
{}`

@brettstack  can we please reopen this one?


fix: add missing parameter to delete requests from ExternalAPI

Description
This PR fixes the ExternalAPI class where a parameter was missing in the Fetch options.
Screenshot (if UI-related)
To-Dos

[x] Successful build pnpm build
[ ] Translation keys pnpm i18n:extract
[ ] Database migration (if required)

Issues Fixed or Closed

Fixes #903

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

v2.0.0
GitHub release

Your semantic-release bot :package::rocket:


build-optimizer: high memory usage (node crash)

From @MrBlaise on October 26, 2017 12:8

Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request

Area
- [x] devkit
- [ ] schematics

Versions

macOS 10.13 (High Sierra)
It affects Windows as well, but on mac it is higher (larger than 1.7 gigs, therefore causes crash with node by default)
Repro steps

The problem is happening with the build-optimizer version 0.0.31.
Using @angular/cli 1.5.0-rc.2 and building with
ng build --prod --aot --build-optimizer
The memory usage starts to grow radically at 95% emitting stage. On a semi-large project this reaches 1.7 gigs on mac, which in turn causes a crash. Increasing the memory limit on node solves the issue, but this seems rather high.
Running it without build-optimizer it builds fine without a crash.
The log given by the failure

$ ng build --prod --aot --build-optimizer
 95% emitting                                                                 s <--- Last few GCs --->

[10242:0x103000000]   191148 ms: Mark-sweep 1417.1 (2081.5) -> 1417.1 (2081.5) MB, 753.9 / 0.0 ms  allocation failure scavenge might not succeed
[10242:0x103000000]   191836 ms: Mark-sweep 1417.1 (2081.5) -> 1417.1 (2035.5) MB, 687.0 / 0.0 ms  last resort GC in old space requested
[10242:0x103000000]   192507 ms: Mark-sweep 1417.1 (2035.5) -> 1417.1 (2013.5) MB, 670.8 / 0.0 ms  last resort GC in old space requested

<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x31fd83fa5e91 <JSObject>
    1: DoJoin(aka DoJoin) [native array.js:~95] [pc=0x112d8f5ead39](this=0x31fd64e82311 <undefined>,p=0x31fdc377f859 <JSArray[432]>,q=432,E=0x31fd64e823b1 <true>,A=0x31fd83fef239 <String[1]:  >,z=0x31fd64e82421 <false>)
    2: Join(aka Join) [native array.js:~120] [pc=0x112d8ee542a9](this=0x31fd64e82311 <undefined>,p=0x31fdc377f859 <JSArray[432]>,q=432,A=0x31fd83fef239 <String[1]:  >,z=0x31fd64e...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: node::Abort() [/Users/balazsrostas/.nvm/versions/node/v8.8.1/bin/node]
 2: node::FatalException(v8::Isolate*, v8::Local<v8::Value>, v8::Local<v8::Message>) [/Users/balazsrostas/.nvm/versions/node/v8.8.1/bin/node]
 3: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/Users/balazsrostas/.nvm/versions/node/v8.8.1/bin/node]
 4: v8::internal::Factory::NewRawTwoByteString(int, v8::internal::PretenureFlag) [/Users/balazsrostas/.nvm/versions/node/v8.8.1/bin/node]
 5: v8::internal::Runtime_StringBuilderJoin(int, v8::internal::Object**, v8::internal::Isolate*) [/Users/balazsrostas/.nvm/versions/node/v8.8.1/bin/node]
 6: 0x112d8ed0463d
error Command failed with signal "SIGABRT".

Desired functionality
Using the build-optimizer shouldn't exceed the default 1.7GB threshold on a semi-large project.

Copied from original issue: angular/devkit#240

This one allowed me to get past the build - https://github.com/angular/angular-cli/issues/12645#issuecomment-431323670
but there are other problems... I'll report them separately.

@chadbr the out of memory issue when updating to 7.0 is reported and investigated in https://github.com/angular/angular-cli/issues/12646. It has to do with more code being brought in.
I don't think the original issue here is present anymore. It was originally from about a year ago and since then we have addressed a lot of the performance problems with build optimizer.


Search syntax [symbol] seems to be not working anymore.

In the past I remember using the syntax [symbol], like [credit], [trash] or [click] in the search bar to search a specific symbol in the text. Now it seems to be broken and even the following example from the syntax documentation on the site is not returning any result: x:"the Corp loses 1[credit]" returns Amina, Corporate "Grant", and Lamprey
A search like x:"[click]" or x:"[credit]" or other symbol always returns no results.

I think this is mainly an issue in the case of "trash" since you find it both as text and symbol and you cannot distinguish between the two cases
If I would like to search all the cards having a [trash] ability and I search the word "trash" I will actually get all the cards having either the trash ability or just the trash word on them

This was intentional because that support was rough but it's not ideal and we've considered adding it back.

The syntax guide has been updated in the most recent release, it's just not live yet. It's probably worth leaving this issue open to reconsider how the search algorithm works with keywords.

This was intentional because that support was rough but it's not ideal and we've considered adding it back.

To me the only ambiguous case right now is with the trash symbol vs trash text. I think having a specific keyword for symbols would make sense. If not the brackets maybe a case sensitive name like TRASH, CREDIT, CLICK or some other convention like _trash, _credit, _click (but in the end this is the same than the brackets).


Bank account - Inconsistency bug: Checking ToS box before filling fields throws error in mweb but not in android app

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Login to staging new dot
Go to workspaces and select Bank account
Click on connect manually and check the ToS box before filling the routing and bank account number fields
Observe that an error is thrown
Login to android app and repeat steps 2-3
Observe that no error is thrown when checking and unchecking ToS box before filling routing and bank account number fields

Expected Result:
Error throwing should be consistent across platforms
Actual Result:
Inconsistent error throwing
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[x] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.57-5
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/78819774/acd3ef2a-c62e-4a8a-9367-cf45176e657f
https://github.com/Expensify/App/assets/78819774/4de07e4c-db19-49d4-96a1-2aa58d261d78
Expensify/Expensify Issue URL:
Issue reported by: @sofoniasN
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1692271454788889
View all open jobs on GitHub

Proposal
Please re-state the problem that we are trying to solve in this issue.
Checking the ToS box before filling fields throws an error in MWeb but not in android app
What is the root cause of that problem?
On mobile web, checking the ToS box causes the blur event for the text input field to fire which triggers validation. On native platforms, this is not the case.
What changes do you think we should make in order to solve the problem?
Either of these solutions has to be selected for implementation.
Solution 1
On mobile web, add a preventDefault call for the checkbox event and then programmatically change the value of the checkbox using a state variable.
Solution 2
On native platforms, blur the text input when the checkbox is tapped or clicked.
What alternative solutions did you explore? (Optional)
None.

Proposal
Please re-state the problem that we are trying to solve in this issue.
Bank account - Inconsistency bug: Checking ToS box before filling fields throws error in mweb but not in android app
What is the root cause of that problem?
The root cause of this issue is TextInput.autoFocus prop
https://github.com/Expensify/App/blob/c029dc509d03fd13ece058ba89ab25c4318a9050/src/pages/ReimbursementAccount/BankAccountManualStep.js#L97-L98
The Form component you have logic the show the error message when the value change, but the error message only shows when the input already added into the touchedInputs list
https://github.com/Expensify/App/blob/c029dc509d03fd13ece058ba89ab25c4318a9050/src/components/Form.js#L150-L157
What alternative solutions did you explore?
Update childrenWrapperWithProps logic to call setTouchedInput when the child.props.autoFocus is true
https://github.com/Expensify/App/blob/c029dc509d03fd13ece058ba89ab25c4318a9050/src/components/Form.js#L219-L357
like this
if (child.props.autoFocus) {
    setTouchedInput(child.props.inputID);
}

https://github.com/Expensify/App/assets/3086267/49340cc4-ade5-499c-8349-fcb71da64123

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~0133d983376a3d0d3d

This was previously reported and the GH closed as a feature request, not a bug.

I'm going to move this to external so that we have consistency between devices.
Note that on m/web AND android/native, the error happens if you enter an account number before the routing number. I think the easiest solution is to populate the error when the TOS checkbox or accounting number is entered before the routing number. That way both devices would be just as picky about the order.

@strepanier03 Just to be clear: based on your comment, the correct behaviour is to show the validation error when we click/tap on the checkbox first (or trying to provide account number before routing number)? Ergo, we need to fix it on mobile, not on web. Am I right?

@tamdao Just wondering, what if there is more than one input with autoFocus property inside the Form? Probably it's rare case scenario, but I think we shouldn't add all of these inputs to the touchedInput list, but only this one that is really focused... WDYT?

@strepanier03 Just to be clear: based on your comment, the correct behaviour is to show the validation error when we click/tap on the checkbox first (or trying to provide account number before routing number)? Ergo, we need to fix it on mobile, not on web. Am I right?

If this is the expected behaviour, Solution 2 in my proposal takes care of this.

@tamdao I agree no one should do that but, as far as I know, it's not programmatically forbidden anywhere, so in case there is more than one autoFocus all of them will be added to the thouchedInput array in your solution - that's why I think your proposal should contain some kind of check for it.

@burczu if you want, I can add more logic to check that. But you know in development, we also need to compare the performance and the value of the logic to make sure that change valuable

@burczu We can add a flag like this
let isTouchedAutoFucusInput = false;
const childrenElements = React.Children.map(childNodes, (child) => {
....
    if (child.props.autoFocus && !isTouchedAutoFucusInput) {
       setTouchedInput(child.props.inputID);
       isTouchedAutoFucusInput = true;
     }
....

But I have tested the form with multiple autoFocus, it will cause validation issue when user open the screen like this

This issue happens because I add 2 autoFucus into 2 input and the second will show the error message

Thanks @tamdao for this investigation! So it seems this check is not necessary because having more than one autoFocus in the Form will cause unexpected behaviour anyway.
Let's wait for the confirmation from @strepanier03 about my concern here. But once confirmed I think we will proceed with your proposal.

Sorry for the confusion and thanks for the ping to clarify.
To bring consistency, the update needed here is only on Android/native so that when the TOS checkbox is checked before the routing number is entered, the error populates.

Thanks @strepanier03!
So, I think the proposal from @tamdao is the one we should proceed with - it fixes the issue in the Form component, so we may avoid similar issues in the future.
The solution 2 from @akinwale proposal is might also fix the issue but it's more like workaround that fixes the issue only in the bank account flow.
🎀 👀 🎀 C+ reviewed

@burczu Sorry to distract you, but when I tested my solution, I found another issue. About the issue I found is focus the second input and check the checkbox the validation not show, because you know this input is not in the touched list. So here new proposal:
Proposal
Please re-state the problem that we are trying to solve in this issue.
Bank account - Inconsistency bug: Checking ToS box before filling fields throws error in mweb but not in android app
What is the root cause of that problem?
The root cause of this issue is value change for the input not trigger blur event. In this case the input is checkbox.
What alternative solutions did you explore?
Update the childrenWrapperWithProps function in Form component
https://github.com/Expensify/App/blob/c029dc509d03fd13ece058ba89ab25c4318a9050/src/components/Form.js#L219-L357
Add new ref
const focusedInput = useRef(null);

Update childrenWrapperWithProps logic to add onFocus function:
... line 307
onFocus: (event) => {
    focusedInput.current = inputID;
    if (_.isFunction(child.props.onFocus)) {
        child.props.onFocus(event);
    }
},
onBlur: ....

and update the onInputChange function (line 336) to check the changed value is focused input or not
const inputKey = key || inputID;

if (focusedInput.current && focusedInput.current !== inputKey) {
    setTouchedInput(focusedInput.current);
}

I have tested this change and it works well.

@tamdao I've just checked the new solution and it does the trick indeed - I like it. Please update your original proposal with the new one, and your last comment with something like:
## Proposal
[Updated](link to proposal)

Read more about it here.

@burczu Thanks for your comment.
Proposal
Updated

Hmm, interesting. @burczu @tamdao to make sure I understand, will this solution affect the behavior of any other types of form inputs? Or only check boxes?

@puneetlath my solution fixes any inputs form not trigger blur event when user change value, not only checkbox

@puneetlath short answer: No
Long answer: My change only adds logic the check changed input and the current focus input is different or not. If it's different, I will add the current focus input into touched list to let the validation check that input. And this change didn't change any old behavior

Ok, thanks for the explanation. Let's do it then.

@burczu @puneetlath PR is ready https://github.com/Expensify/App/pull/26699. Please help me review it. Thanks ❤

Just to inform: I'll be OOO on Thursday and Friday (7-8 September).

That not true :(

@puneetlath I noticed that the offer sent in upwork for the bug report is 50 dollars, but this issue was created before the new price scheme was announcement and is eligble for the original 250 payment . Could you please look into it. Thanks

Payment summary:

[x] External issue reporter - @SofoniasN - $250 paid via Upwork
[x] Contributor that fixed the issue - @tamdao - $1000 paid via Upwork
[ ] Contributor+ that helped on the issue and/or PR - @burczu - $1000 paid via Manual Requests

Speed bonus assessment: @tamdao assigned on 2023-09-04 / PR merged on 2023-09-08 - 4 days lapsed = not eligible

@burczu - Please submit your manual request for payment and let me know once you've done so. I will then assign Jason to issue payment.
@SofoniasN - I have paid you via Upwork and since this was reported prior to our pay change I made sure it was $250.
@tamdao - I took another look at the timeline based on your comment here but I confirmed the date you were assigned and the PR was merged was 4 days so I paid you out via Upwork at $1000.

@burczu - I totally spaced the checklist here so please take care of that and then submit for manual payment, sorry about that!

@strepanier03 I'm from Callstack, so I'm not eligible for payment for this.

Oh doh, I knew that. Thanks for reminding me @burczu 🤦♀.
I'll follow along and finish up once you have time to do the checklist. Thanks again!

I'm out of the office Monday-Tuesday next week. If urgent action is needed from a BZ either day, please reach out in #expensify-open-source for help. Otherwise I'll check in Wednesday.

Going to set this to weekly priority since only thing left is the checklist.

@burczu also, if you have too many issues to handle, please feel encouraged to ask in #contributor-plus if others want to take some over!

@puneetlath No worries, I've just managed to address all my other assignments and will start handling BZ checklists that are waiting for me.

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[x]  [@burczu] The PR that introduced the bug has been identified. Link to the PR: This is not a regression - it just wasn't implemented this way.
[x]  [@burczu] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: n/a
[x]  [@burczu] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: n/a
[x]  [@burczu] Determine if we should create a regression test for this bug.
[x]  [@burczu] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[ ]  [@puneetlath / @strepanier03] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

Thanks! I think we're good to go here.


Unexpected Identifier in login-template.js

This is the error i get after trying to start the server using "node app.js"
:\Users\Rares\Desktop\UNI\ONE FELL SWOOP new\node_modules\admin-bro\src\frontend\login-template.js:1
(function (exports, require, module, __filename, __dirname) { import React from 'react'
^^^^^

SyntaxError: Unexpected identifier
at new Script (vm.js:84:7)
at createScript (vm.js:264:10)
at Object.runInThisContext (vm.js:312:10)
at Module._compile (internal/modules/cjs/loader.js:684:28)
at Module._compile (C:\Users\Rares\Desktop\UNI\ONE FELL SWOOP new\node_modules\pirates\lib\index.js:99:24)
at Module._extensions..js (internal/modules/cjs/loader.js:732:10)
at Object.newLoader [as .js] (C:\Users\Rares\Desktop\UNI\ONE FELL SWOOP new\node_modules\pirates\lib\index.js:104:7)
at Module.load (internal/modules/cjs/loader.js:620:32)
at tryModuleLoad (internal/modules/cjs/loader.js:560:12)
at Function.Module._load (internal/modules/cjs/loader.js:552:3)
at Module.require (internal/modules/cjs/loader.js:657:17)
at require (internal/modules/cjs/helpers.js:22:18)
at Object. (C:\Users\Rares\Desktop\UNI\ONE FELL SWOOP new\node_modules\admin-bro\src\admin-bro.js:5:23)
at Module._compile (internal/modules/cjs/loader.js:721:30)
at Module._compile (C:\Users\Rares\Desktop\UNI\ONE FELL SWOOP new\node_modules\pirates\lib\index.js:99:24)
at Module._extensions..js (internal/modules/cjs/loader.js:732:10)
This is the code from my app.js file
`var express = require("express"),
app = express(),
bodyParser = require("body-parser"),
mongoose = require("mongoose"),
passport = require("passport"),
LocalStrategy = require("passport-local"),
methodOverride = require("method-override"),
seedDB = require("./seedDB"),
Testimonial = require("./models/Testimonial");
//Route import
var indexRoutes = require("./routes/index");
var testimonialRoutes = require("./routes/testimonials/testimonials");
var adminRoutes = require("./routes/admin");
// var testimonials = require("./routes/testimonials");
//Database connect
mongoose.connect("mongodb://localhost/One-fell-swoop", {
useNewUrlParser: true
});
seedDB();
app.set("view engine", "ejs");
app.use(bodyParser.urlencoded({
extended: true
}));
app.use(express.static(__dirname + "/css"));
app.use(methodOverride("_method"));
app.use(indexRoutes);
app.use("/testimonials", testimonialRoutes);
app.use("/admin", adminRoutes);
//Port setup
var port = process.env.PORT || 3000;
app.listen(port, function () {
console.log("Server is up");
});`
And this is the code from my admin.js file where i connected mongoose to admin-bro
`const AdminBro = require('admin-bro');
const AdminBroExpress = require('admin-bro-expressjs');
const express = require('express');
const app = express();
const mongoose = require('mongoose');
AdminBro.registerAdapter(AdminBroMongoose);
const adminBro = new AdminBro({
databases: [mongoose],
rootPath: '/admin',
})
const router = AdminBroExpress.buildRouter(adminBro)
module.exports = router;`
Could you help me understand what is going on?

which node version do you have? - try to update to the at least 10.x and let me know if that helped.

Thank you for your response! i am currently running node v11.6, so i don't think that is the problem

I installed the latest version of node, hoping that maybe it will fix the problem, but i still get the same error

It seems to be a problem related with babel. The error you have: (function (exports, require, module, __filename, __dirname) points to the already transcompiled file (the original file looks like this: https://github.com/SoftwareBrothers/admin-bro/blob/master/src/frontend/login-template.js#L1).
But first, can you try to launch admin with the simplest, one file, server (https://softwarebrothers.github.io/admin-bro-dev/tutorial-01-example.html) and let me know if it works. If it doesn't - maybe there is something wrong with admin-bro + windows in general.

I created a new "server.js" file where i put the code from the example app. This time the error changed a bit:

import React from 'react'
^^^^^

SyntaxError: Unexpected identifier
at Module._compile (internal/modules/cjs/loader.js:703:23)
at Module._compile (C:\Users\Rares\Desktop\UNI\ONE FELL SWOOP new\node_modules\pirates\lib\index.js:99:24)
at Module._extensions..js (internal/modules/cjs/loader.js:770:10)
at Object.newLoader [as .js] (C:\Users\Rares\Desktop\UNI\ONE FELL SWOOP new\node_modules\pirates\lib\index.js:104:7)
at Module.load (internal/modules/cjs/loader.js:628:32)
at Function.Module._load (internal/modules/cjs/loader.js:555:12)
at Module.require (internal/modules/cjs/loader.js:666:19)
at require (internal/modules/cjs/helpers.js:16:16)
at Object. (C:\Users\Rares\Desktop\UNI\ONE FELL SWOOP new\node_modules\admin-bro\src\admin-bro.js:5:23)
at Module._compile (internal/modules/cjs/loader.js:759:30)
at Module._compile (C:\Users\Rares\Desktop\UNI\ONE FELL SWOOP new\node_modules\pirates\lib\index.js:99:24)
at Module._extensions..js (internal/modules/cjs/loader.js:770:10)
at Object.newLoader [as .js] (C:\Users\Rares\Desktop\UNI\ONE FELL SWOOP new\node_modules\pirates\lib\index.js:104:7)
at Module.load (internal/modules/cjs/loader.js:628:32)
at Function.Module._load (internal/modules/cjs/loader.js:555:12)
at Module.require (internal/modules/cjs/loader.js:666:19)

I got exactly the same problem. Like I mentioned on https://github.com/SoftwareBrothers/admin-bro/issues/84 simple file with:
const AdminBro = require('admin-bro')

only results in the same exception being thrown.
Don't you plan to release dist build with everything already transpiled in it?

@404-html do you use windows as well?

Yes. Win10 x64.

@404-html - regarding the build - I added this to the project but before that, there are lots of other things planned. Unfortunately, I don't have windows machine now to debug that.
But you can use docker environment until this issue is closed.

@404-html, @Odisseuss - I've just added a build stage in the deployment. This should fix the issue. Please install the 0.9.0-beta.2 version and let me know


Memory leak in pytlsd.

I am trying to train your network on some other dataset. However, when generating groundtruth with LSD, I found that there's a heavy memory leak in pytlsd. My PC has 32G ram, and my PC will OOM in several minutes when generating groundtruth. Shown in image:

I found that your pytlsd code is forked from https://github.com/iago-suarez/pytlsd, and I substitute your version with iago-suarez's version, and there is no memory leak anymore. I think it might be useful by merging iago-suarez's repository into yours.

Hi, yes I was aware of this issue and it is on my todo list to fix it. As a quick workaround, one can substitute the original pytlsd when generating the ground truth. However, when using DeepLSD at test time, the fork is necessary to be able to use the new 'grad_nfa' option, which keeps the NFA check proposed in LSD, based on the image gradient. This can filter out many noisy lines.
I will try to look into this once I find the time for it.

Sorry for the late reply, and thanks a lot for the fix!!


Feature request: Add location/rewrite rules

This would make it even easier for beginners to do it the right way, could also add a preview for the regex so it's easy to see what the results will become.

how would you see this option being presented?
some default rewrites that are used quite a bit or some presets such as
location /{LOCATION} {
    try_files $uri $uri/ /index.php?$args;
}

Just trying to think how it should be presented for what people need

This would be awesome to have.
Maybe have an input box where you put an URL and it would show you haw it would look after it goes through the rewrite.

YES this most important missing
• add path
• exclude path string
etc


This terminal has encountered an issue with the graphics driver and it could not recover in time.

Windows Terminal version
1.18.2822.0
Windows build number
10.0.22631.0
Other Software
No response
Steps to reproduce
Open terminal, wait an undefined period of time (could be within 10 minutes) and the message 'This terminal has encountered an issue with the graphics driver and it could not recover in time.' appears. Graphics driver is Nvidia Geforce 546.17 but this happened in previous versions as well.
Expected Behavior
For me not having to open a new terminal every few minutes.
Actual Behavior
The message that I antecedently delineated appears and Terminal becomes unusable.

Unfortunately the log file didn't seem to contain any debug information from Windows Terminal. I've removed it because it contained your name and mail address and I wasn't sure if you intended to share that information.
Do you have "AtlasEngine" enabled in your "Rendering" settings? If not, could you enable it?

I've enabled "AtlasEngine" and so far, the issue has not manifested. Thanks!

I've enabled "AtlasEngine" and so far, the issue has not manifested. Thanks!

i have the same problem, but i don't know how to enable AtlasEngine, i wonder if you can help me

In your settings there's a "Rendering" section which should have an "AtlasEngine" option.

I fixed this issue by enabling "Use software rendering"

Hello everyone, I have the same problem when I use window's built-in emojis (windows key + dot key).
I changed some settings related (Graphic API, Software Rendering,Full colored emojis, Builtin Glyphs) but the problem is same.
after the error message the terminal is hanging and nothing working.

I had this problem, I solved it by resetting the video card settings to default.

Pasting this string triggers it for me on Direct3D 11:
s = """ءاﺍﺎأإٲٳآٱٮبپࢾٻڀتټٽثٹٺٿݐݑݒݓݔݕݖࢠࣀࢡࣅࣆجچࣁڇڿڃڄحﺡﺢﺤﺣځڂݗڅݘخݮݯݼࢢدﺩﺪذڈڌڍډڊڋڎڏڐۮݙݚࢮرﺭﺮزࢲࢳࢴڑڒړڔڕږڗژڙۯݛݫݬݱࢪسﺱﺲﺴﺳښڛشڜ
   ...: صﺹﺺﺼﺻڝڞࢯضطﻁﻂﻄﻃڟظࢣعﻉﻊﻌﻋڠغࣃفڤڡڣڥࢤڦࢻٯقڧڨࢥࢼࣄكﻙﻚﻜﻛکػؼݢݣݤࣂگڰڴګڬڮڲࢰڭڱڳلﻝﻞﻠﻟڵڶڷڸࢦࣇمﻡﻢﻤﻣࢧنڹںﮞﮟڻڼڽࢽهﻬﻫۀہﮦﮧﮨۂھﮪﮫﮭﮬۿةۃࢿوﻭﻮۄۊ
   ...: ۏؤݸݹࢫࢱۅۆۇۈۉۋىﻰࢭݳݴيئێࢨࢩؽیؾؿݵݶݷۍؠېۑےﮮﮯۓݺݻࢬەݜݝݞݟݠݡݥݦݧݨݩݪݭݰݲݽـࢶࢷࢸࢹࢺﷲﷴﷺﷻ٫٬٠١٢٣٤٥٦٧٨٩۰۱۲۳۴۵۶۷۸۹0123456789

Works with Direct2D. Terminal version 1.21.3231.0.


Feature proposal: Condition hold for at least X without expected evaluation changes afterward

I want to ensure that some condition would be held for given time, but i do not expect it to change in future.
I thought I could use #during(Duration) for such cases, but it looks like it expects condition to fail after duration and I could not find the way to disable that behavior.
To be exact I expect following to not throw any timeout/assertion exception.
await().during(1, SECONDS).until(() -> true);

However it throws:
org.awaitility.core.ConditionTimeoutException: Condition {} was not fulfilled within 10 seconds.

I've just been struggling with the semantics of during myself. It appears that you might need to also use atMost in conjunction with during. So in your case:
await().during(1, SECONDS).atMost(2, SECONDS).until(() -> true);

Should help. Experimenting, it seems that atMost always needs to be slightly longer than during. I think that your original examples will always run for the default time. (Lots of uncertainty here, as I'm just going by what I've observed and not through studying the code).
It would seem to be logical that if during == atMost it should pass, however it does not. Thus:
await().during(1, SECONDS).atMost(1, SECONDS).until(() -> true);

also fails.


Don't apply redundent operations to the cache

Filters out:

Link operations against records that haven't been added yet
Add link operations that make no change
Remove link operations that make no change

@dgeb done

Thanks @opsb!

:heart:


Builds not reliable

A git submodule pull failed, the build succeeded anyway it seems for windows.
https://ci.appveyor.com/project/modulesio/exokit

Hasn't been a problem lately.


Search bar enabled border not set

Search bar enabled border not set, as shown in below image.
@avinashkranjan  I would like to fix it please assign this to me.
GSSOC'21 participant.

Go Ahead @abstrxtInfinity


Source Sync 🔄

Source Sync 🔄
This pull request syncs changes from the parent template repo astrowind, to this one

resolves: https://github.com/caragolfoundation/caragolfoundation.org/issues/91

.deploy


Luma updater 2.5 fail?

What model of system are you using?

[x ] Old 3DS
[ ] Old 3DS XL
[ ] 2DS (non-XL)
[ ] New 3DS
[ ] New 3DS XL
[ ] New 2DS XL

What is your current Luma3DS version?
If you are running an hourly version of Luma3DS, please manually update to a stable version as I will no longer deal with people who are using hourlies.

[ ] Luma3DS v7.1 + boot9strap v1.0/v1.1
[ ] Luma3DS v8.0 + boot9strap v1.2+
[ ] Luma3DS v8.1 + boot9strap v1.2+
[ ] Luma3DS v8.1.1 + boot9strap v1.2+
[ ] Luma3DS v9.0 + boot9strap v1.2+
[ ] Luma3DS v9.1 + boot9strap v1.2+
[ x] Luma3DS v10.0+ + boot9strap v1.2+

What version of Luma Updater are you using?

[ ] v2.0
[ ] v2.1
[ ] v2.1.1
[ ] v2.1.2
[ ] v2.2
[ ] v2.3
[ x] v2.4
[ ] v2.5

How are you running Luma Updater?

[x ] .cia
[ ] .3dsx + HBL/Rosalina
I think?

What problems are you experiencing?
Please tell us what problems you are facing.
It says new update is available to go from luma updater 2.4 to 2.5
What is the exact error code you are receiving?
SHOWS
FATAL: could not get location header for 3xx reply
Ret code:ded92
Please give the exact error code the app gives you
Ret code:ded92
Steps to reproduce

#53


Inside a ngFor loop, MdCheckbox 'change' event is not emitted when 'checked' binding change.

Bug, feature request, or proposal:
Bug
What is the expected behavior?
MdCheckbox 'change' event is always emitted when 'checked' binding change.
What is the current behavior?
It works for a standalone MdCheckbox but not when MdCheckbox is inside a ngFor loop.
What are the steps to reproduce?
I created a small plunkr with standalone checkboxes and checkboxes inside ngFor loop:
http://plnkr.co/edit/v2Nv4QcMVPVwdX32z3hQ
Steps:
Open the devtools console to see console.log messages.
Check (e.g. click) the "Select all" checkbox.
All the checkboxes become selected.
In the devtools console you see:

onSelectAllCheckboxChange
onCheckboxChange
onCheckboxChange

Instead of what you'd expect:

onSelectAllCheckboxChange
onCheckboxChange
onCheckboxChange
onNgForCheckboxChange
onNgForCheckboxChange

Which versions of Angular, Material, OS, browsers are affected?
Latest version (see the plunkr), tested on Goobuntu with Chrome.
Is there anything else we should know?
This bug could be an Angular 2 bug and not a MdCheckbox bug. Feel free to move it to Angular 2 issues if relevant.

This is not an issue. I investigated at your issue and noticed, that you're recreating the row object on each select all call.
This causes the components to be re-rendered, with new instances, which are by default set to unchecked (You can also see, that the animation is not working on un-checking)
If you only modify the given property of the row, it will work properly.
See my modified plunker.

http://plnkr.co/edit/EdHoPxVOOz1AFS4mQ0KD?p=preview

This issue can be closed.

Thanks Paul, it makes sense, I wasn't aware the components were re-created every-time in this case.


[WARN] PersistentConnection: pc_0 - Provided authentication credentials are invalid

When I run the function startWeeklyTopPostEmailer() it has the following problem.
[WARN] PersistentConnection: pc_0 - Provided authentication credentials are invalid. This usually indicates your FirebaseApp instance was not initialized correctly. Make sure your google-services.json file has the correct firebase_url and api_key. You can re-download google-services.json from https://console.firebase.google.com/.
I created the firebase app and created service account key (JSON).
Please let me know if I need to provide more info. Thanks

The important lines in the quickstart are:
            FirebaseOptions options = new FirebaseOptions.Builder()
                    .setServiceAccount(new FileInputStream("service-account.json"))
                    .setDatabaseUrl(DATABASE_URL)
                    .build();
            FirebaseApp.initializeApp(options);

This requires that you have properly placed the service-account.json file and have updated the DATABASE_URL variable.  Have you done both of those? Are there other errors in your logs?

I modified DATABASE_URL in Database.java and placed the service-account.json in database folder (where the gradlew is placed).
Thanks

Just found it that there is some problem in key creation.
When a key is being created, I need to add Editor role

@winstonma did adding 'Editor' solve your issue?

Yes I followed this Stackoverflow Issue and created a new service account.
Originally I created a service account without any role attached to it I got the problem above.

Fixed by #8


generated /etc/resolv.conf in containers not compatible with alpine:3.4

Rancher Version:
1.0.2
Docker Version:
1.11.2
OS and where are the hosts located? (cloud, bare metal, etc):
Ubuntu 16.04 on digital ocean
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
single node, internal DB
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:

Add a service with image = alpine:3.4, CMD = ping rancher-metadata.rancher.internal, using default for all other options.
Execute Shell from the container.
run ping rancher-metadata

Results:
ping: bad address 'rancher-metadata'
Expected:
pingable to rancher-metadata, similar to rancher-metadata.rancher.internal:
PING rancher-metadata.rancher.internal (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: seq=0 ttl=64 time=0.220 ms
64 bytes from <IP_ADDRESS>: seq=1 ttl=64 time=0.236 ms

Other useful info:

related issue on alpine: gliderlabs/docker-alpine/issues/8
musl version of alpine:3.4

ldd --version
musl libc (x86_64)
Version 1.1.14
Dynamic Program Loader

search domain resolving is supported from musl 1.1.13+
inside alpine:3.4 container:

# cat /etc/resolv.conf
search mosquitto.rancher.internal alpine.mosquitto.rancher.internal rancher.internal
nameserver <IP_ADDRESS>

mosquitto is stack name, alpine is service name.
If I change /etc/resolv.conf to (move rancher.internal to first search domain):
search rancher.internal mosquitto.rancher.internal alpine.mosquitto.rancher.internal
nameserver <IP_ADDRESS>

Then I can ping rancher-metadata as expected:
# ping rancher-metadata
PING rancher-metadata (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: seq=0 ttl=64 time=0.338 ms

maybe resolv.conf is setup in start_handler.
I wonder whether we can move rancher.internal to be the first search domain (so rancher dns can work with alpine:3.4+)?

@giabao This problem is fixed in alpine:edge

@giabao yes, you are right. the rancher.internal needs to be the first

Alpine Linux uses musl lib to handle resolv.conf, which behaves differently than glibc's implementation in several ways. If rancher.internal is the third item in resolv.conf's search definition, 'rancher-metadata' will not get searched against rancher.internal, and dns resolution will fail.

I see the same in ubuntu:14.04.3 with my internal domains (which I think come from ros config get rancher.network.dns.search?)
Moving the rancher.internal to the front makes it work:
search rancher.internal myinternal.domain.com
nameserver <IP_ADDRESS>

My workaround:
I manually set "internal.rancher" as a search domain for my services, and it is now the first search domain.
It works by changing the configuration in Networking Tab of the UI,
or including in your docker-compose file this:
`
alpine:
image: alpine:3.4
dns_search:

rancher.internal
`

Has there been any movement on this?

I am also concerned by the problem. I run CI build in Kubernetes and I am using the docker image which is based on Alpine 3:4...

Could this be related to the issue #7160 I have?

Has there been any progress on that?

The problem seems to be that rancher's dns is returning "name exists but has no RRs of the requested type" (RCODE=0, Success) instead of "name does not exist" (RCODE=3, NxDomain), for nonexistent names. Fixing this should solve all compatibility problems with musl libc/Alpine.

@richfelker The solution you just described conflicts with https://www.ietf.org/rfc/rfc4074.txt where the current return is proper.

@JakeWarner You need to be more specific about what part of the RFC you claim supports the current behavior. My reading of it is the opposite; it explains why the nameserver needs to behave the way I suggested fixing it to behave, and why musl's resolver behaves the way it does, in order to ensure consistency when you have existent names that have just one or the other (but not both) of A and AAAA records. It does not in any way imply that you should return RCODE=0 for names that do not exist at all.

Oh, my bad -- for nonexistent names you're correct.
I was doing a ton of research on services return IPv6 vs IPv4 and how musl is different than the others in resolution. My initial message was based on the assumption this thread was talking about ipv4 (type A) results existing but not ipv6 (type AAAA) which would have referenced section 3 on RFC 4074:

Expected Behavior

Suppose that an authoritative server has an A RR but has no AAAA RR
for a host name.  Then, the server should return a response to a
query for an AAAA RR of the name with the response code (RCODE) being
0 (indicating no error) and with an empty answer section (see
Sections 4.3.2 and 6.2.4 of [1]).  Such a response indicates that
there is at least one RR of a different type than AAAA for the
queried name, and the stub resolver can then look for A RRs.
This way, the caching server can cache the fact that the queried name
has no AAAA RR (but may have other types of RRs), and thus improve
the response time to further queries for an AAAA RR of the name.

Agree with @richfelker's assessment on what's the root cause here. The specialty of the musl resolver seems to be that when it does the search it "takes none for an answer" (NODATA) and stops trying the other search domains. glibc's resolver on the contrary will continue searching the other domains and thus find the record with the data. That probably also means that with musl you should under no circumstances have a wildcard domain in your domain tree as this might mask the actual record.

Fixed by network-services: v0.2.0 and rancher/dns:v0.15.0.

Tested with network-services: v0.2.0 and  rancher/dns:v0.15.0
Able to ping rancher-metadata from within containers deployed with image = alpine:3.4 and command ping rancher-metadata.rancher.internal.

Was able to reproduce this issue with 1.2.4 rancher server which has network-services: v0.0.8 and rancher/dns:v0.13.0

It seems that it is still an issue with Alpine when services are in different stacks.


Fix Credits

We are moving to the crediting scheme in https://github.com/jstac/QuantEcon.lectures/issues/1195.
Highlights:

Standardized format for coauthors at the top of each page. (when applicable)
Removing all "inline" citations/attributions (e.g., in comments, cells, Markdown, etc.) and moving these to a global credits page. There should be no names in the code.
Credits page will be in a different repo. Details on where to submit them TBD.

No need to duplicate the whole checklist here. Can just be mindful of this as we proceed with the rewrite, and then do a final pass to make sure we got them all.
cc: @jstac, @jlperla, @Nosferican

Sounds good. For now, if there is someone not listed in https://lectures.quantecon.org/about_lectures.html#id7 I think you should add a note to this issue so we don't lose them

Probably best to do all in one repo after the first pass.

OK, per @jlperla, I did a first pass; below are the names of people whose names come up in the lectures but who aren't credited on the global attribution paragraph. Some of these cites are for QuantEcon.jl contributions which are tightly bound to the lectures.

Max Huber
Balint Szoke
Victoria Gregory
Willem Hekman
Guanlong Ren (with Will, for solving Ex. 1 in linear_algebra)
Alberto Polo (for editing the Wald_Friedman_jl.ipynb
Ranjan Ananthamaran (for working on lss.jl in QuantEcon, which powers the linear_models lecture).
Zac Cranko (for the lqcontrol file in the QuantEcon package).
Colin Beckingham (for work on the QuantEcon.jl/src/markov/markov_approx.jl file, which solves Exercise 3).

Also, below is the table I was using to keep track of references to people by name. Doesn't directly apply to a task, but I figure it's useless to just destroy it. Some lines may omit frequent contributors.

Lecture Filename
Author(s)
Contributors

additive_functionals
Chase Coleman and Balint Szoke (joint)
Shunsuke Hori

aiyagari
N/A
N/A

amss
N/A
N/A

arellano
N/A
Chase Coleman

arma
N/A
N/A

career
N/A
N/A

classical_filtering
N/A
Shunsuke Hori

coleman_policy_iter
N/A
Shunsuke Hori, Spencer Lyon, John Stachurski

discrete_dp
N/A
Daisuke Oyama, Max Huber

dyn_stack
N/A
Spencer Lyon, Victoria Gregory (for dyn_stack/oligopoly.jl), Zac Cranko (for QuantEcon.jl/lqcontrol.jl)

egm_policy_iter
N/A
Shunsuke Hori

estspec
N/A
Spencer Lyon, Shunsuke Hori

finite_markov
N/A
Spencer Lyon, Chase Coleman, José, Natasha, Colin Beckingham

harrison_kreps
N/A
Shunsuke Hori

hist_dep_policies
N/A
Spencer Lyon, Victoria Gregory

ifp
N/A
N/A

julia_arrays
N/A
N/A

julia_by_example
N/A
N/A

julia_essentials
N/A
N/A

julia_libraries
N/A
Victoria Gregory, Chase Coleman, Spencer Lyon

julia_plots
N/A
N/A

jv
N/A
Spencer Lyon

kalman
N/A
Spencer Lyon, Victoria Gregory

lake_model
N/A
Victoria Gregory, John Stachurski

linear_algebra
N/A
Spencer Lyon, Victoria Gregory, William Hekman, Guanlong Ren

linear_models
N/A
Chase, Natasha, José, Spencer, Victoria, Ranjan Ananthamaran, Shunsuke

lln_clt
N/A
Spencer and Victoria

lqcontrol
N/A
N/A

lqramsey
N/A
Spencer

lu_tricks
N/A
Shunsuke

lucas_model
N/A
Spencer Lyon, John Stachurski

markov_asset
N/A
Spencer Lyon, Tom Sargent, John Stachurski

markov_perf
N/A
Shunsuke

matsuyama
Chase Coleman (co-author)
Shunsuke Hori

`mccall_model_with_separation
N/A
N/A

mccall_model
N/A
N/A

multiplicative_functionals
Chase Coleman and Balint Szoke (joint)
Shunsuke Hori

need_for_speed
N/A
N/A

odu
N/A
Spencer Lyon

opt_tax_recur
N/A
N/A

optgrowth
N/A
Spencer Lyon, John Stachurski

orth_proj
N/A
N/A

perm_income_cons
Chase Coleman (co-author)
N/A

perm_income
N/A
Spencer, Victoria

rational_expectations
N/A
Chase Coleman, Spencer Lyon, Thomas Sargent and John Stachurski

robustness
N/A
Spencer

schelling
N/A
N/A

short_path
N/A
N/A

smoothing
N/A
N/A

stationary_densities
N/A
Spencer, Victoria

types_methods
N/A
N/A

uncertainty_traps
N/A
N/A

wald_friedman
Chase Coleman (co-author)
Shunsuke Hori, Alberto Polo

@arnavs  Thanks so much for this.  Based on https://github.com/jstac/QuantEcon.lectures/issues/1195#issuecomment-417498436 I think that can now take the next steps:

Standardize the Coauthored with XXX and YYY at the top of the page where there are co-authors
Remove all other names from the sourcecode/etc.
Get these names merged into the global contributors, as in https://github.com/jstac/QuantEcon.lectures/issues/1195#issuecomment-417498436

@jstac : I don't think we have access to the make PRs on the main attributions page, so perhaps you could have someone on the python page merge these in based on however you want to organize the "Developers" vs. "Other Contributors"?

OK, I did a few passes on the Julia side and the code should be free of names. What's the plan for merging in the names above? Should I add them to the individual index pages for the Julia, or are we doing something globally?

@jstac We will take your lead on this, as I am not sure which repo/file this would go in.  I think it may be on the global website?
Alternatively, if there is some repo we could add an issue in with this list of names, then we could close things out here.

I'm actually not sure to put global credits, now I think about it.  Soon the lectures.quantecon.org portal will be used to link to multiple lecture sites (python, julia, data bootcamp).  Perhaps each of those needs their individual "Preface / About these lectures" page, and credits belong there.
Or, we could put some additional credits down the bottom of https://quantecon.org/team.
That page is easy to edit.

Sounds good @jstac. For now, I've created a credits text file in the repo with this list of names, so we don't lose them.

Put back names from exercises

Done at a6b4f71.


Update pv name and path creation

Hello,
This PR resolved issue #1339.
In the scope of this PR was added the ability to use metadate (name, namespace, labels, annotations) PVC field for dynamical creation the pvPath and pvName.
Example:
StorageClass:
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  namespace: kube-system
  name: managed-nfs-storage-test-2
provisioner: fuseim.pri/ifs
parameters:
  archiveOnDelete: "false"
  pathPattern: "{pvc.namespace}/{pvc.name}"
  namePattern: "{pvc.name}-{pvc.annotations.volume.beta.kubernetes.io/storage-class}"

PersistentVolumeClaim:
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  namespace: kube-system
  name: managed-nfs-storage-test-2
provisioner: fuseim.pri/ifs
parameters:
  archiveOnDelete: "false"
  pathPattern: "{pvc.namespace}/{pvc.name}"
  namePattern: "{pvc.name}-{pvc.annotations.volume.beta.kubernetes.io/storage-class}"

PersistentVolume
kubectl get pv test-claim-2-managed-nfs-storage-test-2 -o yaml
apiVersion: v1
kind: PersistentVolume
metadata:
  annotations:
    pv.kubernetes.io/provisioned-by: fuseim.pri/ifs
  creationTimestamp: "2020-07-09T14:17:25Z"
  finalizers:
  - kubernetes.io/pv-protection
  name: test-claim-2-managed-nfs-storage-test-2
  resourceVersion: "34210609"
  selfLink: /api/v1/persistentvolumes/test-claim-2-managed-nfs-storage-test-2
  uid: 61a86d68-f6b5-4f1a-ac26-20bcdd7f4952
spec:
  accessModes:
  - ReadWriteMany
  capacity:
    storage: 1Mi
  claimRef:
    apiVersion: v1
    kind: PersistentVolumeClaim
    name: test-claim-2
    namespace: kube-system
    resourceVersion: "34210604"
    uid: d7d65376-4495-488c-91bd-57317c09311e
  mountOptions:
  - lookupcache=pos
  nfs:
    path: /kube-system/test-claim-2
    server: ***
  persistentVolumeReclaimPolicy: Delete
  storageClassName: managed-nfs-storage-test-2
  volumeMode: Filesystem
status:
  phase: Bound

/check-cla

@k8s-ci-robot /check-cla

@k8s-ci-robot /retest

/assign @wongma7

/assign @jsafrane

@Bledai - thank you for this PR.
We are in the middle of migrating the NFS client code into a new home under  https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner. The migration PR is up for review at the moment. https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner/pull/2
Can I request you to raise the PR on the new repo, once the above migration PR is closed?
Thank you for working on this fix.

@Bledai - thank you for this PR.
We are in the middle of migrating the NFS client code into a new home under https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner. The migration PR is up for review at the moment. kubernetes-sigs/nfs-subdir-external-provisioner#2
Can I request you to raise the PR on the new repo, once the above migration PR is closed?
Thank you for working on this fix.

@kmova Thanks for your response.
Got it, I'm going to open PR for a new home after PR migrations will be merged.

As @kmova mentioned, we are in the process of archiving this repo and continuing work in https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner. Please reopen a PR in the new repo once https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner/pull/2 has merged. Thanks for your patience! :)
Going to close this PR in order to be able to archive this repo.


Hi, request to add a feature

I wanted to make a request to add a feature, For now, when you click "add menu" an application listed in the pop-up window that shows the apps installed in a distrobox container is added to the desktop in the path:
/home/$user$/.local/share/applications
The problem is that the .desktop comes without the icon, what you could do is a symbolic link to a folder located in the boxbuddyrs files folder or copy the icons to a folder with any name to the boxbuddyrs folder, I hope you can solve that, good luck.

Hello, this is functionality in Distrobox itself.
The icon should be exported by distrobox-export, and if you close and re-open the View Applications modal, you should then see the icon.


Using distilled indic-indic model for translation

I am using the distilled pre-trained model checkpoint for indic-indic translation. I am getting error because of the --arch arguments which defaults to transformer_18_18.
Can you please tell which architecture to use? I am finetuning using our dataset.

For fine-tuning distilled models, you should use transformer_base18L arch,  as described in the README.


No information on "How to view available dev drives?"

Type of issue
Missing information
Feedback
I have used "new vhd" way to setup my dev drive. after several days I logged in and I couldn't recall where my vhdx file was located.  As a result, I couldn't start my dev drive. Is there a way to (1) auto-mount this VHD so that I can always see my dev drive or (2) in the dev drive settings UI, show the list of such VHDX that were used to setup dev drives.
Page URL
https://learn.microsoft.com/en-us/windows/dev-drive/
Content source URL
https://github.com/MicrosoftDocs/windows-dev-docs/blob/docs/hub/dev-drive/index.md
Author
@mattwojo
Document Id
bfda7965-bc34-ab88-fdc9-efef4a5d8a9e

The dev drive should be automounted. We are aware of a bug in this area and are working to get it serviced. More information about Dev Drive VHDs can be found in Dev Home under Windows Customizations->Dev Drive Insights.
When a dev drive is mounted but you forgot where its located, you can use the following:

DISKPART and the "list vdisk" command to show the full path to the vhdx.
Powershell and "Get-Disk | Select-Object FriendlyName,Location"

For reference - currently if a dev drive vhd becomes dismounted, and the user re-mounts it via File Explorer, DiskMgmt, or powershell, that will not set the automount capability. Currently automount is only supported through the Settings app UI under Disks & Volumes. We are working to plug this feature gap on those other tools.

Thanks for contributing this issue @sriharshamadala.
And for the recommended methods for finding a drive, Adam!
I added a section to the FAQs: "How can I find a Dev Drive that I created and lost track of?" with these methods listed.
Updated in https://github.com/MicrosoftDocs/windows-dev-docs/commit/ddfe90ad006d62c3a900ca85ccc7df3767b6219f


Profile reconcile not working anymore

Describe the bug
sfdx sfpowerkit:source:profile:reconcile is not working , after reconcile while deploying the profiles getting an error like "Unknown user permission: SendExternalEmailAvailable" or "Unknown user permission: ManageHpi". Looks like profiles are not getting cleaned up
To Reproduce
Steps to reproduce the behavior:

sfdx sfpowerkit::

Expected behavior
Post profile reconcile it should be in deployable state.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [ Windows]
Node Version
Version of sfpowerkit[e.g 1.45.0]
Salesforce Org Version [ Sprin22/Summer 22 ]

On Spring22 getting errors while deploying profile post reconcile:
Unknown user permission: SendExternalEmailAvailable
On Summer 22 getting errors while deploying profile post reconcile:
Unknown user permission: ManageHpi
Errors_Profile_Deploy.txt
Version:
sfdx plugins --core
»   Warning: sfdx-cli update available from 7.145.0 to 7.146.1.
@dxatscale/sfpowerscripts 13.0.12
@oclif/plugin-autocomplete 0.3.0 (core)
@oclif/plugin-commands 1.3.0 (core)
@oclif/plugin-help 3.3.1 (core)
@oclif/plugin-not-found 1.2.6 (core)
@oclif/plugin-plugins 1.10.11 (core)
@oclif/plugin-update 1.5.0 (core)
@oclif/plugin-warn-if-update-available 1.7.3 (core)
@oclif/plugin-which 1.0.4 (core)
@salesforce/sfdx-plugin-lwc-test 0.1.7 (core)
alias 2.0.0 (core)
apex 0.11.0 (core)
auth 1.8.2 (core)
community 1.1.4 (core)
config 1.3.24 (core)
custom-metadata 1.0.12 (core)
data 0.6.12 (core)
generator 1.2.2 (core)
info 1.3.1 (core)
limits 1.3.0 (core)
org 1.11.2 (core)
salesforce-alm 54.1.0 (core)
schema 1.1.0 (core)
sfdmu 4.13.4
sfdx-cli 7.145.0 (core)
sfpowerkit 4.2.5
source 1.9.2 (core)
telemetry 1.4.0 (core)
templates 54.3.0 (core)
trust 1.1.0 (core)
user 1.7.1 (core)
Additional context
Add any other context about the problem here.

Issue is consistently happening on Summer22 especially.
On my VSCODE with same version of sfpowerkit/sfdmu/sfdx happening for spring22 as well but not with other team members.
Hence, i believe primary focus should be on summer 22 issue with "Unknown user permission: ManageHpi".
Any pointer for Spring22 issue will help for my machine, but that is secondary and am checking too how this can be resolved. Thanks


deleteSession! error on sessionConnection_ALL

julia> deleteSession!(DFGClient(userLabel, robotLabel, sessionLabel; apiUrl))
ERROR: GraphQLError: Request to server failed

Message:

Field "sessionConnection_ALL" is not defined by type "BlobEntryWhere".

Message:

Field "sessionConnection_ALL" is not defined by type "BlobEntryWhere".
Stacktrace:
 [1] checkbodyforerrors
   @ ~/.julia/packages/GraphQLClient/Wm5fb/src/http_execution.jl:129 [inlined]
 [2] _execute(endpoint::String, execution_string::String, headers::Dict{…}, output_type::Type{…}; retries::Int64, readtimeout::Int64, operation_name::Nothing, throw_on_execution_error::Bool)
   @ GraphQLClient ~/.julia/packages/GraphQLClient/Wm5fb/src/http_execution.jl:116
 [3] execute(endpoint::String, payload::Dict{…}, headers::Dict{…}, output_type::Type{…}; kwargs::@Kwargs{…})
   @ GraphQLClient ~/.julia/packages/GraphQLClient/Wm5fb/src/http_execution.jl:80
 [4] execute(client::GraphQLClient.Client, payload::Dict{…}, output_type::Type{…}; kwargs::@Kwargs{…})
   @ GraphQLClient ~/.julia/packages/GraphQLClient/Wm5fb/src/http_execution.jl:74
 [5] execute(client::GraphQLClient.Client, query::String, output_type::Type{…}; variables::Dict{…}, operation_name::Nothing, kwargs::@Kwargs{…})
   @ GraphQLClient ~/.julia/packages/GraphQLClient/Wm5fb/src/http_execution.jl:70
 [6] execute
   @ ~/.julia/packages/GraphQLClient/Wm5fb/src/http_execution.jl:69 [inlined]
 [7] deleteSession!(fgclient::DFGClient)
   @ NavAbilitySDK ~/.julia/dev/NavAbilitySDK/src/services/UserRobotSession.jl:179
 [8] top-level scope
   @ REPL[15]:1
Some type information was truncated. Use `show(err)` to see complete types.

julia> listSessionBlobEntries(DFGClient(userLabel, robotLabel, sessionLabel; apiUrl))
Symbol[]

this was already fixed in v0.7.0, I just had an older version of code.


USB Won't Initialise - "This device cannot start. (Code 10)"

I'm sure I'm doing something wrong here, but now I've got everything building successfully (thanks for the pointer chegewara), I now cant get the ESP to initialise as a USB device properly.
For example, using the keyboard2.ino example (or any other example from this library I've tried), Windows shows this error in device manager:

And with Core Debug=Verbose on the ESP, I get the following lines logged from via UART0:
13:55:02.704 -> [  1248][D][hidkeyboard.cpp:23] begin(): begin len: 25
13:55:02.737 -> [  1248][D][usb_descriptors.cpp:45] getConfigurationDescriptor(): descriptor length: 34
13:55:02.737 ->
13:55:02.737 -> [  1250][W][esptinyusb.cpp:185] begin(): failed to init, (return fixed in tinyusb 0.8.0)
13:55:02.737 -> [  1258][D][esptinyusb.cpp:47] esptinyusbtask(): USB tud_task created
13:55:04.746 -> FAIL
13:55:05.720 -> FAIL
13:55:07.726 -> FAIL

So it looks like the usb begin() is failing, but I cannot see why.
I've tried the same setup using PlatformIO and Arduino IDE and have the same results.
I'm able to successfully compile and run the USBSerial example from ESP32 Arduino, which gives the expected results on the USB interface. I believe this rules out possibilities that I have some kind of hardware problems...maybe? I can also upload sketches to the board using CDC so that also gives me confidence in the hardware.
A few other points about my environment, in case it is of relevance:

Windows 10
Board is Lilygo TTGo T8 ESP32S2. Also tried and same issue with Lilygo TTGO ESP32S2 V1.1

Please can anyone help? Any pointers would be very greatly appreciated.

I've kept investigating this, and concluded that my best next step would be to enable the built in TinyUSB debug logging.
I added the relevant build flag (-DCFG_TUSB_DEBUG=3) but was getting no new debug logs on UART0... so started trying to chase that down.
I what I found is that the ESP32-S2 port of TinyUSB doesn't currently have the board_uart_write() hooked up to anything, so perhaps log lines are just being ignored? On second thoughts this might not be related because I now cannot confirm that this method is actually called by the logging macros - I thought I'd traced it through earlier but am now completely confused.
I would have just modified that method in the TinyUSB library to see what happens, but I also find that the ESP32 Arduino framework included libraries are in the form of headers only, so cant actually find the c file referenced above that would be consumed during my build in order to make that edit. Rabbit holes within rabbit holes! What am I missing?
I'm a bit out of my depth here, but can anyone tell me if I'm heading in the right direction? Has anyone had success getting TinyUSB debug logging out of an ESP32-S2?

Hi,
i dont know why HID is not working, i will have to test it.
About logging, it will not work, because tinyusb library is precompiled without logging enabled.

Thanks as always Chegewara.
To be honest I think I was having the same symptoms when building some of the other examples too, but I can't remember exactly which I tested now.
I'm travelling for work for a couple of days now but will retest as soon as I'm home and let you know if my issue is isolated to HID only or not.
Thanks re. TinyUSB logging, that explains the trouble.

OK, just got home and ran some more tests... I can confirm that the MIDI example is working as expected - MIDI device is recognised and outputting MIDI notes. So perhaps it is just the HID class that isn't working.
Interestingly, despite the successful USB connection, the ESP debug log still shows the following lines, indicating some failure. What could this mean?
...
[   562][D][usb_descriptors.cpp:45] getConfigurationDescriptor(): descriptor length: 101

[   563][W][esptinyusb.cpp:185] begin(): failed to init, (return fixed in tinyusb 0.8.0)
[   567][D][esptinyusb.cpp:47] esptinyusbtask(): USB tud_task created
[  1573][V][midiusb.cpp:88] setSong(): MThd format => 0

MTrk
[  1573][V][midiusb.cpp:103] setSong(): song => 40, i = 40

we can play now
[  1575][V][midiusb.cpp:145] playSong(): play
...

Could it be that the "failed to init" message is always shown regardless of successful connection or not, therefore indicating that might not be related to my issues with the HID example?

Confirmed, I also just tested the Ramdisk example and that works 100% but yields the same "failed to init" log line.
[   573][E][ramdisk.cpp:103] begin(): NO disk
[   574][E][ramdisk.cpp:109] begin(): init ram disk from internal memory: 4
[   574][E][ramdisk.cpp:115] begin(): init ram disk size: 4
[   578][D][usb_descriptors.cpp:45] getConfigurationDescriptor(): descriptor length: 32

[   587][W][esptinyusb.cpp:185] begin(): failed to init, (return fixed in tinyusb 0.8.0)
[   594][D][esptinyusb.cpp:47] esptinyusbtask(): USB tud_task created
MSC lun 1 begin
[   938][V][ramdisk.cpp:23] onInquiry(): default onInquiry
[   939][V][ramdisk.cpp:23] onInquiry(): default onInquiry
[   939][V][ramdisk.cpp:41] onCapacity(): ram disk block count: 200, block size: 512
...

So it looks like "failed to init" is a red herring and I need to look elsewhere for clues.
I'm very interested now if you are able to successfully use the HID class, Chegewara because it looks like that might be the only problem now.

@chegewara i tried the HID Composit and it's also giving me the same error in windows.
using arduino-esp-2.00_rc1 and lib1.31

@chegewara I have the same issue with the HID Keyboard example. The problem is not related to hardware because I can run my ESP32S2 HID with CircuitPython and it works like a charm.
I am using arduino-esp-2.00_rc1 and the master lib version with the attribute ((weak)) in lines in local arduino files.
Thank you.

Ok, thanks for reporting. It should be fixed in 1.3.2.

Awesome! Tested the fix and can confirm HID Class is now working! Thanks so much Chegewara!

Tested and it is working like a charm! Good job @chegewara, Awesome.

@chegewara - I have a similar problem on esp-idf. I'm implementing a custom vendor device and it was working fine. Now I have to modify just VID / PID to emulate different devices and now getting Code 10 error also - can you point me to a solution to this problem - maybe I can solve my problem also.


Reintroduce make srpm

And document the rules.

Looks nice to me :). Can we have this used in the Github workflows to make sure it works?

Looks nice to me :). Can we have this used in the Github workflows to make sure it works?

Yeah, that's my plan. Just wanted to get this up quickly to have the target on master again. I can also add to this PR right here if you can wait a bit longer.


Remove dead links from free-programming-books-langs.md

What does this PR do?
Remove resource(s)
For resources
Description
The links for

jQuery Fundamentals - Bocoup (HTML)
Angular for the jQuery developer

Aren't active anymore. So, it's better to remove them.
Why is this valuable (or not)?
Keeps the repo updated
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Thanks, and welcome to free-programming-books!


ImportError: cannot import name 'cvxpy' from 'qiskit.ignis.verification.tomography.fitters.cvx_fit'

Informations

Qiskit version:
Python version:
Operating system:

What is the current behavior?
Steps to reproduce the problem
What is the expected behavior?
Suggested solutions

Thanks for reporting this, this was an issue introduced in qiskit 0.19.5 and was reported to ignis: https://github.com/Qiskit/qiskit-ignis/issues/429 and will be included in a pending 0.19.6 release shortly. While you wait for that release to go live you can workaround this by either downgrading to 0.19.3 by running pip install qiskit==0.19.3 or by installing cvxpy with pip install cvxpy.

Closing as solved.


use of min/max and endAdornment in InputProps

for the Textbox component it appears you have to use "inputProps" to use the max and min properties on a numeric type, but to have the InputAdornment you have to use "InputProps". This is both confusing to reading the code, and also eslint does not like duplicate props for a component

[x ] The issue is present in the latest release.
[ x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
To use the min and max properties you have to declare it in "inputProps" and to use adornments you have to use "InputProps" or else they will not work. Currently eslint throws a warning about no duplicated props.

Expected Behavior 🤔
should not be two props with the same name (ignoring capitalization)

Steps to Reproduce 🕹
https://codesandbox.io/embed/material-demo-3kqy3

Steps:

Context 🔦

Your Environment 🌎

Tech
Version

Material-UI
v4.?.?

React

Browser

TypeScript

etc.

@coch110149 This concern has been explored in the past. Maybe # is the most up-to-date effort #14580. It's a non-trivial problem. You can find more related issues in https://github.com/mui-org/material-ui/issues/11377#issuecomment-489188714.

I'm closing for #11377.


ISSUE on production build / Master branch: remove last cart item

For bigcommerce headless, the last cart item cannot be deleted unless the page is manually refreshed.

I am having this problem, also.

Looks like this has been solved already!


SLING-4093 Added performance tests to compare JSP and Sighlty

Changes:

Added test content
Made improvements to performance module to allow results comparison and test failures if a threshold ratio is surpassed
ITs for Sightly performance
@trivial formatting changes (separate commit)

Created #69 and #70 to track these changes, closing this PR.


Bug Report - Documentation - Wiki home page links seems broken

Describe the bug
Accessing the links under https://github.com/Azure/Enterprise-Scale/blob/main/docs/wiki/Home.md page return 404.
Steps to reproduce

Go to https://github.com/Azure/Enterprise-Scale/blob/main/docs/wiki/Home.md
Click any links on the home page

Screenshots

Hey @cbezenco,
Thanks for raising this issue.
This is occurring as you are accessing the docs via the repo instead of via the Wiki.
If you use this link and access the wiki via the wiki tab, these all work 👍https://github.com/Azure/Enterprise-Scale/wiki

However, I will raise a PR to fix this so they work from both places, just in case.

Thanks for the workaround :-)

Thanks for the workaround :-)


set attribute "analytics" of membershipcard

same specification as for the voucher

can you explain in detail @ThierryThevenet ?


Change text for Action from fixes to fix

@valorkin It's too annoying to use the similar texts for Tag and Action (Fix and fixes). I've checked 5 or even more  times just to be sure i remember which word should be used. And refs i've forgot 2 times: should it be ref or refs.

@valorkin It's too annoying to use the similar texts for Tag and Action (Fix and fixes). I've checked 5 or even more  times just to be sure i remember which word should be used. And refs i've forgot 2 times: should it be ref or refs.

@korel-san need to check Jira and Github issues integration,
which words are works really


Proposals to improve update/installation process

I have 2 proposals to improve update/installation process:

Make it possible for update.sh & install.sh to receive arguments for dialog forms, to replace human interaction with automation...
Maybe there is some way to store the server username and password encrypted somehow in config.txt (or anywhere else), and not plain text? for security reasons...

This should already be possible for install. The parameters are read from config.txt. If "q" is included as a command line parameter then a quiet install is performed just using the values in config.txt Currently update doesn't pass that through but I'll change that.

I'll look at that one. It probably won't be very secure though as it would be more like obfuscation. The script needs to decode it to do its work, so it would be possible for somebody else to do the same. The other option would be not to store it and so a user would need to enter it each time, but that would conflict with quiet installs.

I see that installation still asking the user either to reboot or not, it would be great if it could be possible to determine it with another argument for install/update, to make a fully automatic update process.

Actually I believe most of the time the reboot is unnecessary even after a first install. It should be sufficient to just run ./start.sh The reboot request was left in as a safety measure.
I'll change wording to reflect this.


When I run this code, I get an error

from psbody.mesh import Mesh
ImportError: No module named mesh

Hi, thanks for reporting the error. Just updated the README file. To use the Mesh functionality, you need to install another library from this link: https://github.com/MPI-IS/meshlite/blob/master/mesh/mesh.py. It should do the work.

Hi,it's not work.I have installed MeshLite，but it doesn't work. Still reported this error.
Can you check it? Are you sure that the MeshLite  you are using has not been modified?

Thanks for your help,I have solved this error.

Hi @LoneRangerY I am getting the same error would you be able to explain what you did to solve the error?


Bundler usage and $ref pointers

Hi!
I got pointed at your repo from a twitter conversation today and have been tinkering.
We are looking to use json schema in React components to generate input forms using react-json-schema-forms, I got this working and then started to look at code re-use.
We are hoping to make use of $refs to other schema files in the code-base to maximize re-use as we have a number of common complex types.
So, I took your bundler and made a simple webpack loader
In one of my components the pageProperties.schema.json is imported, this in turn references scope.schema.json
##pageProperties.schema.json
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "title": {
      "type": "string"
    },
    "requiresScope": {
      "type": "array",
      "items": {
        "$ref": "scope.schema.json#/definitions/Scope"
      }
    }
  }
}

##scope.schema.json
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "definitions": {
    "Scope": {
      "type": "string",
      "enum": ["user", "exec-user", "reporting-user", "admin"]
    }
  }
}

With my loader setup calling the bundler I get a bundled schema
##bundle output
{
  "$schema": "http://json-schema.org/draft-07/schema",
  "type": "object",
  "properties": {
    "title": { "type": "string" },
    "requiresScope": {
      "type": "array",
      "items": { "$ref": "scope.schema.json#/definitions/Scope" }
    }
  },
  "$defs": {
    "scope.schema.json": {
      "$id": "scope.schema.json",
      "$schema": "http://json-schema.org/draft-07/schema",
      "definitions": {
        "Scope": {
          "type": "string",
          "enum": ["user", "exec-user", "reporting-user", "admin"]
        }
      }
    }
  }
}

The pulls in the linked schema into the $defs property, however the $ref is not updated to use the bundled
Based on my very limited knowledge and some runtime editing of the generated bundle it looks like the $ref needs to be updated to provide a valid pointer to the Scope which is now in the bundled schema file, i.e. "#/$defs/scope.schema.json/$defs/Scope"

The references should not be updated. They still resolve to the same place.
I suggest reading through https://json-schema.org/understanding-json-schema/structuring.html to learn more about how schema identification and referencing works. You can also read https://json-schema.org/blog/posts/bundling-json-schema-compound-documents for an explanation of how the bundling process used in this library works.
If that doesn't help explain why the references don't have to change. Let me know and I'll try to explain better.

Thanks for those links, incredibly helpful.
I think I get it.
Essentially when resolving a $ref the contents of $def should be checked for a pointer that matches the $ref before attempting to read it from the external location?
That closes this issue from my perspective. Do you know when was this $ref resolution behavior added to the spec?
I need to work out if this is an issue that should be raised with react-json-schema-forms or if I should build a post processor to (incorrectly) patch the $refs for consumption by the forms library.

Essentially when resolving a $ref the contents of $def should be checked for a pointer that matches the $ref before attempting to read it from the external location?

Not exactly. Your bundled schema contains two schema resources: file:///path/to/pageProperties.schema.json and file://path/to/scope.schema.json. Whenever you have an $id in a sub-schema, it indicates a separate schema resource. An $id can be in any sub-schema, but there's no good reason to use it anywhere other than $defs. The scope.schema.json#/definitions/scope/ reference is in the file:///path/to/pageProperties.schema.json schema resource. So, that reference resolves to file:///path/to/scope.schema.json#/definitions/scope. Which means, the location /definitions/scope within the file:///path/to/scope.schema.json schema resource.

Do you know when was this $ref resolution behavior added to the spec?

It has always worked this way. It's standard behavior based on RFC 3986.


better ui

Describe the feature
we can some better ui like background design and color , font style
allow me to do.
assign this issue to me under GSSoC'24.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Hey there! I'm eager to bring my HTML/CSS skills to your open source project in GSSoC, ready to add some impactful design enhancements!
please assign this issue to me,

Hi, I am good at frontend as well as in ui designing with good experience, I will try to make it more better, please assign this task to me.

@Suchitra-Sahoo please assign this issues me


fix: emr.create_cluster was not passing security to configuration to internal method

Bugfix
Detail

emr.create_cluster was not passing security to configuration to internal method
Validate tests are passing security configuration for IMDSv2
Add wait condition as EMR cluster must terminate before pytest teardown

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: e3ef98e1e25598f700aa8f3555e0eb19f0fd162d
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 555cef2900f725759655fceba5950cdecbaf57dc
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: e3ef98e1e25598f700aa8f3555e0eb19f0fd162d
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 555cef2900f725759655fceba5950cdecbaf57dc
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: db525b5b7d3f7d7955e6e2aeeba8938157998a9a
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: db525b5b7d3f7d7955e6e2aeeba8938157998a9a
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: f1a892583623670c033ef2a8ca9217ae76390b0c
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: f1a892583623670c033ef2a8ca9217ae76390b0c
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 73d81df5b0aae191d3caaae29384d16455264369
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: fa9856c1d42f9362674bf7f3a1b3ed3381138595
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Default variant for an internally tagged enum

Question from IRC:

<azdle> Is there anyway to set set a default variant for an internally tagged structure, that is to say on an enum with #[derive(tag = "foo")] can I set a variant to use when that field is undefined in some JSON I'm deserializing?

#[macro_use]
extern crate serde_derive;

extern crate serde;
extern crate serde_json;

use serde::de::{self, Deserialize, Deserializer};
use serde_json::Value;

#[derive(Debug)]
enum ConnectRequest {
    Unspecified(UnspecifiedSecurity),
    Wpa2(Wpa2Security),
}

#[derive(Deserialize, Debug)]
struct UnspecifiedSecurity {
    ssid: String,
    psk: Option<String>,
}

#[derive(Deserialize, Debug)]
struct Wpa2Security {
    ssid: String,
    psk: String,
}

impl<'de> Deserialize<'de> for ConnectRequest {
    fn deserialize<D>(deserializer: D) -> Result<Self, D::Error>
    where
        D: Deserializer<'de>,
    {
        #[derive(Deserialize)]
        #[serde(field_identifier, rename_all = "lowercase")]
        enum Tag {
            Wpa2,
            Other(String),
        }

        let v = Value::deserialize(deserializer)?;
        match Option::deserialize(&v["security"]).map_err(de::Error::custom)? {
            Some(Tag::Wpa2) => {
                let inner = Wpa2Security::deserialize(v).map_err(de::Error::custom)?;
                Ok(ConnectRequest::Wpa2(inner))
            }
            None => {
                let inner = UnspecifiedSecurity::deserialize(v).map_err(de::Error::custom)?;
                Ok(ConnectRequest::Unspecified(inner))
            }
            Some(Tag::Other(other)) => {
                const VARIANTS: &[&str] = &["wpa2"];
                Err(de::Error::unknown_variant(&other, VARIANTS))
            }
        }
    }
}

fn main() {
    let present = r#"{"ssid": "foo", "psk": "bar", "security": "wpa2"}"#;
    println!("{:?}", serde_json::from_str::<ConnectRequest>(&present).unwrap());

    let missing = r#"{"ssid": "foo", "psk": "bar"}"#;
    println!("{:?}", serde_json::from_str::<ConnectRequest>(&missing).unwrap());

    let unknown = r#"{"ssid": "foo", "psk": "bar", "security": "unrecognized"}"#;
    println!("{}", serde_json::from_str::<ConnectRequest>(&unknown).unwrap_err());
}

I'm currently staring down a situation just like what's described above but my enum may have as many as 73 variants. Deserializing it is also showing up in my profile, so I'm a bit bothered by the bookkeeping of the approach you've suggested above as well as what looks like a possible performance penalty from deserializing twice (I'd like to measure but I don't have an alternate approach).
Is there anything more to your simple explanation above? Do you plan on supporting a #serde[ attribute to support this pattern?

The trouble with internally tagged enums is that in general you may receive many fields of data before the tag, and those fields can only be meaningfully interpreted after knowing the tag. So it seems inherent that you would need to do two passes to deserialize fully. If your data always contains the tag field first, you may be able to do better. Or if the variants have many fields in common then you may be able to handle those fields better.


Fluix Crystal to Fluix Dust - does not work

Crusher does not work with Fluix Crystals.

forge/1.12.2-<IP_ADDRESS>69
Mekanism-1.12.2-<IP_ADDRESS>0
appliedenergistics2-rv5-stable-11

Peanut to bio fuel does not work

For pams integration, take a look at the this crafttweaker script:
https://github.com/DarethZ33/pams-harvestcraft-mekanism-crusher/blob/master/03_pams_harvestcraft_mekanism_crusher.zs

thommy101, thanks, but to work it (CraftTweaker2-1.12-4.1.6.jar) also needs MTLib-3.0.4.jar, modtweaker-4.0.10.jar.
Fixed with CraftTweaker, MTLib, modtweaker, DarethZ33 03_pams_harvestcraft_mekanism_crusher.zs, and few scripts from Enigmatica 2 Modpack.

thommy101, thanks, but to work it (CraftTweaker2-1.12-4.1.6.jar) also needs MTLib-3.0.4.jar, modtweaker-4.0.10.jar.
Fixed with CraftTweaker, MTLib, modtweaker, DarethZ33 03_pams_harvestcraft_mekanism_crusher.zs, and few scripts from Enigmatica 2 Modpack.


grpc_message":"No module named 'concurrent.futures.thread'"

What version of gRPC and what language are you using?
grpcio                          1.45.0
grpcio-tools                    1.45.0

What operating system (Linux, Windows,...) and version?
Linux dev-2 5.15.0-1019-azure #24~20.04.1-Ubuntu SMP Tue Aug 23 15:52:52 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

What runtime / compiler are you using (e.g. python version or version of gcc)
python --version
Python 3.8.10

What did you do?
Using a gRPC python client to call stub endpoint.
And got this gRPC error
2022-10-21 23:23:09 - ERROR - Unknown Error: <_InactiveRpcError of RPC that terminated with:
	status = StatusCode.UNKNOWN
	details = "No module named 'concurrent.futures.thread'"
	debug_error_string = "{"created":"@1666394589.340558094","description":"Error received from peer ipv4:<IP_ADDRESS>:50055","file":"src/core/lib/surface/call.cc","file_line":905,"grpc_message":"No module named 'concurrent.futures.thread'","grpc_status":2}"

I can find the module installed
Python 3.8.10 (default, Sep 22 2022, 23:15:12)
[GCC 11.1.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import concurrent.futures.thread
>>> concurrent.futures.thread
<module 'concurrent.futures.thread' from '/home/user/.pyenv/versions/3.8.10/lib/python3.8/concurrent/futures/thread.py'>

What did you expect to see?
No error.
What did you see instead?
This error.

Would you care to share your server-side code?

Actually figured out the issue.
Previously I upgraded python from 3.7 to 3.8, concurrent.futures.thread becomes a standard library.
The grpc server I'm working with does file lock stuff preventing itself from being updated and still running with 3.7.
After restarting the server, the issue went away.


Derive Gradle module metadata for Ivy publications

Fixes https://github.com/gradle/gradle/issues/23302

@bot-gradle test acc

I've triggered the following builds for you:

AllConfigCacheTestsPullRequestFeedback build

@bot-gradle test acc

@bot-gradle test acc

I've triggered the following builds for you:

AllConfigCacheTestsPullRequestFeedback build

@bot-gradle test acc

I've triggered the following builds for you:

AllConfigCacheTestsPullRequestFeedback build

@bot-gradle test and merge

I've triggered a build for you.