Add Hashable instances for UPLC Term and related types

This will be needed by CSE.
@kwxm let me know what you think of the instances for the BLS types.

Merging since I want to open the next PR. If there are any comments I'll address them later.


Not published in npm?

npx greencost does not work...
npm ERR! 404  'greencost@latest' is not in the npm registry.

I noticed the same thing.
:( Anne

Hey there folks, so sorry about this!
The package is installed here, and that readme made the assumption that the code had already been installed using: npm install @tgwf/green-cost-explorer and then running npx greencost.
https://www.npmjs.com/package/@tgwf/green-cost-explorer
Can you try running this instead?
npx @tgwf/green-cost-explorer

There's no checking for the env vars right now, so if you don't have deets , you'll get a stack trace a bit like this one:
npx @tgwf/green-cost-explorer

(node:54109) UnhandledPromiseRejectionWarning: UnrecognizedClientException: The security token included in the request is invalid.
    at Request.extractError (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/protocol/json.js:51:27)
    at Request.callListeners (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
    at Request.emit (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
    at Request.emit (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:683:14)
    at Request.transition (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at /Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:685:12)
    at Request.callListeners (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
(node:54109) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:54109) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I'll can update the README, but I'd really appreciate some helping getting a simple try/catch check for this, for others coming to it for the first time.

I am so happy about getting this answer!!!
I will try this and keep you posted.
THANK YOU!!!!
🌼Anne
Anne Thorne
Arbonne Principal Software Engineer
Email: athorne<EMAIL_ADDRESS>Cell:<PHONE_NUMBER>
Whatever be the character of life or its unexpected events – to the heart that loves, all is well.
St. Thérèse de Lisieux ("The Little Flower")
From: Chris Adams<EMAIL_ADDRESS>Sent: Tuesday, May 5, 2020 2:52 AM
To: thegreenwebfoundation/green-cost-explorer<EMAIL_ADDRESS>Cc: Anne Thorne<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [thegreenwebfoundation/green-cost-explorer] Not published in npm? (#24)
Hey there folks, so sorry about this!
The package is installed here, and that readme made the assumption that the code had already been installed using: npm install @tgwf/green-cost-explorer and then running npx greencost.
https://www.npmjs.com/package/@tgwf/green-cost-explorer
Can you try running this instead?
npx @tgwf/green-cost-explorer
There's no checking for the env vars right now, so if you don't have deets , you'll get a stack trace a bit like this one:
npx @tgwf/green-cost-explorer
(node:54109) UnhandledPromiseRejectionWarning: UnrecognizedClientException: The security token included in the request is invalid.
at Request.extractError (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/protocol/json.js:51:27<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/protocol/json.js:51:27>)

at Request.callListeners (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/sequential_executor.js:106:20<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/sequential_executor.js:106:20>)

at Request.emit (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/sequential_executor.js:78:10<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/sequential_executor.js:78:10>)

at Request.emit (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:683:14<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:683:14>)

at Request.transition (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:22:10<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:22:10>)

at AcceptorStateMachine.runTo (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/state_machine.js:14:12<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/state_machine.js:14:12>)

at /Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/state_machine.js:26:10<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/state_machine.js:26:10>

at Request.<anonymous> (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:38:9<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:38:9>)

at Request.<anonymous> (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:685:12<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:685:12>)

at Request.callListeners (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/sequential_executor.js:116:18<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/sequential_executor.js:116:18>)

(node:54109) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:54109) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
I'll can update the README, but I'd really appreciate some helping getting a simple try/catch check for this, for others coming to it for the first time.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/thegreenwebfoundation/green-cost-explorer/issues/24#issuecomment-623961166, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABZFN5IXXQGYCMS5JTLZDYDRP7OVRANCNFSM4MFU5OZQ.

This is helped Chris!
I am getting another error… a permissions error that Arbonne’s AWS admin said he would fix tomorrow for me.
Arbonne is now a B Corp company. The information that the green cost explorer will give us, will, I think, be beneficial.
I’ll keep you posted.
Thank you again!!
🌼Anne
Anne Thorne
Arbonne Principal Software Engineer
Email: athorne<EMAIL_ADDRESS>Cell:<PHONE_NUMBER>
Whatever be the character of life or its unexpected events – to the heart that loves, all is well.
St. Thérèse de Lisieux ("The Little Flower")
From: Anne Thorne
Sent: Tuesday, May 5, 2020 6:42 AM
To: thegreenwebfoundation/green-cost-explorer<EMAIL_ADDRESS>thegreenwebfoundation/green-cost-explorer<EMAIL_ADDRESS>Cc: Comment<EMAIL_ADDRESS>Anne Thorne<EMAIL_ADDRESS>Subject: RE: [thegreenwebfoundation/green-cost-explorer] Not published in npm? (#24)
I am so happy about getting this answer!!!
I will try this and keep you posted.
THANK YOU!!!!
🌼Anne
Anne Thorne
Arbonne Principal Software Engineer
Email: athorne<EMAIL_ADDRESS>Cell:<PHONE_NUMBER>
Whatever be the character of life or its unexpected events – to the heart that loves, all is well.
St. Thérèse de Lisieux ("The Little Flower")
From: Chris Adams <notifications<EMAIL_ADDRESS>Sent: Tuesday, May 5, 2020 2:52 AM
To: thegreenwebfoundation/green-cost-explorer <green-cost-explorer<EMAIL_ADDRESS>Cc: Anne Thorne <athorne<EMAIL_ADDRESS>Comment <comment<EMAIL_ADDRESS>Subject: Re: [thegreenwebfoundation/green-cost-explorer] Not published in npm? (#24)
Hey there folks, so sorry about this!
The package is installed here, and that readme made the assumption that the code had already been installed using: npm install @tgwf/green-cost-explorer and then running npx greencost.
https://www.npmjs.com/package/@tgwf/green-cost-explorer
Can you try running this instead?
npx @tgwf/green-cost-explorer
There's no checking for the env vars right now, so if you don't have deets , you'll get a stack trace a bit like this one:
npx @tgwf/green-cost-explorer
(node:54109) UnhandledPromiseRejectionWarning: UnrecognizedClientException: The security token included in the request is invalid.
at Request.extractError (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/protocol/json.js:51:27<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/protocol/json.js:51:27>)

at Request.callListeners (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/sequential_executor.js:106:20<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/sequential_executor.js:106:20>)

at Request.emit (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/sequential_executor.js:78:10<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/sequential_executor.js:78:10>)

at Request.emit (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:683:14<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:683:14>)

at Request.transition (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:22:10<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:22:10>)

at AcceptorStateMachine.runTo (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/state_machine.js:14:12<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/state_machine.js:14:12>)

at /Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/state_machine.js:26:10<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/state_machine.js:26:10>

at Request.<anonymous> (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:38:9<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:38:9>)

at Request.<anonymous> (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:685:12<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:685:12>)

at Request.callListeners (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/sequential_executor.js:116:18<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/sequential_executor.js:116:18>)

(node:54109) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:54109) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
I'll can update the README, but I'd really appreciate some helping getting a simple try/catch check for this, for others coming to it for the first time.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/thegreenwebfoundation/green-cost-explorer/issues/24#issuecomment-623961166, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABZFN5IXXQGYCMS5JTLZDYDRP7OVRANCNFSM4MFU5OZQ.

Hi Chris,
Arbonne now has the green versus grey cost of our AWS Services.
Thank you!!!
Anne Thorne
From: Anne Thorne
Sent: Tuesday, May 5, 2020 6:17 PM
To: thegreenwebfoundation/green-cost-explorer<EMAIL_ADDRESS>thegreenwebfoundation/green-cost-explorer<EMAIL_ADDRESS>Cc: Comment<EMAIL_ADDRESS>Subject: RE: [thegreenwebfoundation/green-cost-explorer] Not published in npm? (#24)
This is helped Chris!
I am getting another error… a permissions error that Arbonne’s AWS admin said he would fix tomorrow for me.
Arbonne is now a B Corp company. The information that the green cost explorer will give us, will, I think, be beneficial.
I’ll keep you posted.
Thank you again!!
🌼Anne
Anne Thorne
Arbonne Principal Software Engineer
Email: athorne<EMAIL_ADDRESS>Cell:<PHONE_NUMBER>
Whatever be the character of life or its unexpected events – to the heart that loves, all is well.
St. Thérèse de Lisieux ("The Little Flower")
From: Anne Thorne
Sent: Tuesday, May 5, 2020 6:42 AM
To: thegreenwebfoundation/green-cost-explorer <reply<EMAIL_ADDRESS>thegreenwebfoundation/green-cost-explorer <green-cost-explorer<EMAIL_ADDRESS>Cc: Comment <comment<EMAIL_ADDRESS>Anne Thorne <athorne<EMAIL_ADDRESS>Subject: RE: [thegreenwebfoundation/green-cost-explorer] Not published in npm? (#24)
I am so happy about getting this answer!!!
I will try this and keep you posted.
THANK YOU!!!!
🌼Anne
Anne Thorne
Arbonne Principal Software Engineer
Email: athorne<EMAIL_ADDRESS>Cell:<PHONE_NUMBER>
Whatever be the character of life or its unexpected events – to the heart that loves, all is well.
St. Thérèse de Lisieux ("The Little Flower")
From: Chris Adams <notifications<EMAIL_ADDRESS>Sent: Tuesday, May 5, 2020 2:52 AM
To: thegreenwebfoundation/green-cost-explorer <green-cost-explorer<EMAIL_ADDRESS>Cc: Anne Thorne <athorne<EMAIL_ADDRESS>Comment <comment<EMAIL_ADDRESS>Subject: Re: [thegreenwebfoundation/green-cost-explorer] Not published in npm? (#24)
Hey there folks, so sorry about this!
The package is installed here, and that readme made the assumption that the code had already been installed using: npm install @tgwf/green-cost-explorer and then running npx greencost.
https://www.npmjs.com/package/@tgwf/green-cost-explorer
Can you try running this instead?
npx @tgwf/green-cost-explorer
There's no checking for the env vars right now, so if you don't have deets , you'll get a stack trace a bit like this one:
npx @tgwf/green-cost-explorer
(node:54109) UnhandledPromiseRejectionWarning: UnrecognizedClientException: The security token included in the request is invalid.
at Request.extractError (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/protocol/json.js:51:27<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/protocol/json.js:51:27>)

at Request.callListeners (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/sequential_executor.js:106:20<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/sequential_executor.js:106:20>)

at Request.emit (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/sequential_executor.js:78:10<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/sequential_executor.js:78:10>)

at Request.emit (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:683:14<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:683:14>)

at Request.transition (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:22:10<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:22:10>)

at AcceptorStateMachine.runTo (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/state_machine.js:14:12<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/state_machine.js:14:12>)

at /Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/state_machine.js:26:10<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/state_machine.js:26:10>

at Request.<anonymous> (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:38:9<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:38:9>)

at Request.<anonymous> (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:685:12<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/request.js:685:12>)

at Request.callListeners (/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/sequential_executor.js:116:18<mailto:/Users/chrisadams/.npm/_npx/54109/lib/node_modules/@tgwf/green-cost-explorer/node_modules/aws-sdk/lib/sequential_executor.js:116:18>)

(node:54109) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:54109) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
I'll can update the README, but I'd really appreciate some helping getting a simple try/catch check for this, for others coming to it for the first time.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/thegreenwebfoundation/green-cost-explorer/issues/24#issuecomment-623961166, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABZFN5IXXQGYCMS5JTLZDYDRP7OVRANCNFSM4MFU5OZQ.


The error in ‘Application - Part Segmentation’

My environment is ubuntu16.04，cuda9.2，cudnn7.6.4,pytorch1.1.0,faiss and visdom installed.

I used the shapenet dataset in your Google Drive.Its location is '/media/rmv/data1/CPR/shapenetcore_partanno_segmentation_benchmark_v0_normal/',and I changed the 'dataroot' in the opinion of part-seg folder.

Then I compiled customized cuda code.The process is showed below.

Then I began the training,but I found the error''No module named 'util'''.To slove this,I add the 'SO-Net-master' folder path to the python path.

At last it showd the error in the error.txt below,and I cannot figure out how to solve it.

error.txt

To avoid the Error,I Commented out these code in ‘train.py' ：
            visualizer.print_current_errors(epoch, epoch_iter, errors, t)
            visualizer.plot_current_errors(epoch, float(epoch_iter) / dataset_size, opt, errors)

and then I ran the 'train.py', it can run, but visdom server couldn't show any information. Instead, I can only see the output in the terminal:

I wonder how to get the training and test log to particular object like 'table', 'car' and so on. And how to get the '.txt' or '.npz'
files which are the test results?

Is this problem solved please?


Generated release apk fails to run in 0.16

I'm having trouble running the generated apk files. This problem happens on both the emulator and physical device.
Steps to reproduce

Created a blank application using init.

Verify that the app runs using run-android

Genrate apk following instructions at http://facebook.github.io/react-native/docs/signed-apk-android.html#content

Install the app-release.apk on phone.

Running the app produces this output in logcat

--------- beginning of crash
--------- beginning of system
--------- beginning of main
E/ReactNative( 8863): Got JS Exception: ReferenceError: Can't find variable: require

@arunabha did you try opening the developer menu (shake the device or click the hardware menu button in emulator) selecting "Debug in Chrome"?

@jforaker No, I couldn't. The app shuts down immediately upon launching producing the logcat output mentioned in the original report. There is no chance to try the dev menu.

This most probably means that the JS bundle didn't get included. Did you upgrade from a previous version?

@arunabha Any updates on this?

I have the same problem.
I tried once with my existing project that was upgraded from 0.16.0 to 0.17.0 and as this was not working and showing the same message as mentioned by @arunabha , I tried with a completely new project with react-native init and again, the same output was shown in the log.

Yes, I upgraded from a previous version. I was able to get it working by regenerating the signing key.

@schinknbrot Try clearing the build directory to see if this is fixed for you.

@arunabha Good to know. Closing.


How can I prevent duplicates?

For some reason, the autocomplete plugin always shows the contents of the directory twice.  In the notes section of the documentation, it says "if you have issues with duplicate suggestions please use the path-autocomplete.ignoredFilesPatter option to disable the path autocomplete in certain file types"  However, I do not want to disable certain file types, I just want to eliminate duplicate files or folders from the list of suggestions.
How can I use path-autocomplete.ignoredFilesPattern to ignore duplicates?  It's also interesting that the duplicates are not always right next to each other. It is not clear what sorting method is used when listing possible matches.

Try with the excludedItems option, it allows you control based on the current line context.
// disable all suggestions in HTML files, when the current line contains the href or src attributes
"path-autocomplete.excludedItems": {
        "**": {
            "when": "**/*.html",
            "context": "(src|href)=.*"
        }
},

Please try it out and close the issue if it works for you.

Related to #85

That did the trick! Thank you.


Specify that the cluster.yml playbook should run as root

This is a possible fix for #3388.
The following examples show the option -b too:
https://kubernetes.io/docs/setup/custom-cloud/kubespray/
https://github.com/kubernetes-incubator/kubespray/blob/master/docs/getting-started.md#starting-custom-deployment

/approve
/lgtm

ci check this

My comment was not addressed:
could you use the long-form: --become and add also --become-user=root.
Also in this part of the documentation, I would not enter in too many details. Please free to extend why it's needed outside the 'code' part.
     # Deploy Kubespray with Ansible Playbook  - I
     # note: it's required to sudo as `root` on the target hosts with the option `--become`
      ansible-playbook -i inventory/mycluster/hosts.ini --become --become-user=root cluster.yml

@ant31 are you happy with this?

@oz123 Thanks I missed it.

/lgtm
/approve


[1.16, Bug] Crash with Futurepack mod

-- Describe how you caused the bug --
When you have Futurepack mod (https://www.curseforge.com/minecraft/mc-mods/futurepack) and Smaller-Units mod installed, putting an block into a Smaller-Units tile causes the game to crash.
The Unit tiles are also broken with Futurepack installed. In the screenshot i have 1/3 unit on the left, and 1/16 unit on the right, but theyr both the same size. This does not happen when only Smaller-Units is installed.

If this is something that should be reported to Futurepack instead, please let me know and i will re-direct this!
-- Describe the expectation --
The game doesent crash when placing blocks on unit tiles and the unit tiles are the intended size
-- Describe what happened instead --
The game crashes when placing blocks on unit tiles and the unit tiles are not the intended size
-- Additional info --
SU Version: 1.3
Futurepack Version: 31.3.7008
Exact MC Version: 1.16.5
Loader: Forge
Any optimization mods: No
-- Logs if the game crashed --
Crash report: https://pastebin.com/PetJAX89
Log: https://pastebin.com/1Lcejaq6
Thank you for your time!

I… am pretty sure I fixed that crash at some point, but I guess I never uploaded it?
It’s more so a forge version thing than a modpack thing.
As for them both being 1/4, that is odd, I have not seen that

Yeah, its a super weird issue. Two things i forgot to mention in my initial post:

I dont have other mods installed than these two
Im running the latest 1.16.5 forge, which is 36.2.39

If you need any more info on the subject please ask!

SU was truthfully designed for forge 36.2.20
I believe forge update since then and made a change which happened to make, probably truthfully a large standing issue, crash the game the moment anyone interacts with the unit spaces

That could explain it. The crash only happens with Futurepack installed, Small-Units works fine standalone

Ok nvm then
That makes this… a lot more interesting
I’ll have to look at it at some point, but at this point I’m mostly fixing simple issues with the 1.16 version, so I don’t have any guarantee

Np! Take your time with the fixes, better safe than sorry. Thank you for looking into it!


Suggestion: resolve .d.ts at higher priority than .ts

I would like to see resolution of foo try to locate and use foo.d.ts before it looks for foo.ts. OK ok, I suspect such a breaking change will never happen, but I think it's sufficient to call attention to a real problem!
The problem is: When building in-place (i.e. not as --outDir dist), typescript prefers the sources to the built results, which may cause errors. The errors arise from the fact that some relevant configuration goes into how to generate .d.ts files from .ts sources. In my case a my package blows up when used because the .ts files contain null errors, something which the tsconfig.json explicitly permits. Unfortunately when used as a package these files are evaluated as built artifacts (e.g. according to the including tsconfig.json not the package's own tsconfig.json. Meanwhile the real built code is ignored.
This is especially pernicious because in package.json I've specified "types": "index.d.ts", but since that file imports other files e.g. as export * from "./bar", the resolution algorithm decides that that means to import bar.ts not bar.d.ts, which is just plain old wrong in this circumstance.

More than anything I want to understand if this is something Typescript has any interest in resoving (and how), because it is my intention to make this problem much, much more common.

Duplicate of #15272. You forgot to fill out the issue template.

Ok, but that was locked and limited and while the technical issue may be the same I have a heck of a lot more to say about why this matters. Sorry about your template.

It's not my template. It's the issue template provided by the TypeScript team: for feature requests and for bug reports.
Quoting RyanCavanaugh:

To expedite the triage process, we need everyone to follow the issue template and instructions.
When you clicked "Create New Issue", the issue form was pre-populated with a template and some instructions. We need you to read those instructions completely, follow them, and then fill in all the fields in that template.
We are not able to assist with issues that don't follow the template instructions as they represent a significantly larger amount of work compared to issues which are correctly specified. Thank you for understanding.

Another times where this issue came up: #11196, #42329, #10704.
This is working as intended. If you don't want this behaviour, place the files in a different directory.

I reject the idea that I must never talk to the people who have the ability to make decisions unless what I say fits neatly in a form. This is a very complicated topic.

The issue you linked says this:

the rational, is that sources are more up-to-date than an output

Ok, I get that but that implies that the sources should be equivalent to their built output, which is not true due to reading the wrong tsconfig.json. If this is the real problem I'm happy to file an issue with the template filled out fully and to help fix it.
I also think I may be able to offer a means to tell whether built outputs are stale. I'm hundreds of hours into a next-gen project called macrome which is focused around this capability. For example I could include a header annotation like @generatedfrom ./foo.js#71d3be, while providing the tooling that makes sense of that.

I also asked a version of this question in a discord help channel and @blutorange there noted that when doing npm installs with git package sources that npm itself respects the contents of the files attribute of the package. This solves the problem by excluding the sources except during development.
I'm going to close this for now and wait and see what this looks like when esm resolution lands.

Nope I'm reopening it because that fix doesn't work. Unfortunately yarn 1.x does not respect the content of the files in package.json, and it has tremendous usage including all my projects. Its development is also frozen. Aaaaaaaaaaarrrrrrrgh.

Duplicate of #10704, #14787, and more recently, #46880 - this is by design and, from what I've seen, very unlikely to be changed.
Note this comment:
https://github.com/microsoft/TypeScript/issues/10704#issuecomment-245336321

We did in the past give .d.ts higher precedence in importing, and that broke scenarios for npm-link for example, where you really want to import the .ts and not the .d.ts as you are developing multiple npm modules that depend on each other.

See also, this one:
https://github.com/microsoft/TypeScript/issues/46880#issuecomment-975806524

All the rationale from #10704 still applies here and I'm not sure how this option even helps -- the issue is in downstream consumers of the package, who might not be able to enable this option for whatever reason, so they'd just be completely stuck?

OK, here's my pitch.
When you see a sources alongside compiled files, you have basically two correct options. Either you can compile the sources or you use the compiled versions.
If you use the compiled versions you risk their being out of date, something which is insanity-inducing because it is a silent failure.
If you compile the sources yourself nothing can ever be stale, but you must know how to compile them correctly.
Compile is a bit a of a vague term, as extracting types from a source in node_modules is not emitting any new code, but you still have to extract the types correctly and currently this is not the case. The install blows up because the included project has loose nulls and the including project does not. The compiler understands how to extract correct typedefs from sources with loose nulls and does so in the compiled typedefs, but the including project does not extract correct types.
This describes an issue in using Typescript in what I a way that I find to be generally consistent with best practices. It is a surprising failure. But it does not necessarily make clear which part of the behavior is the cause of the problem. You are saying that typescript very intentionally made the choice to recompile instead of using compiled files on disk.
I'm saying I think it was the wrong choice, because the implementation of type extraction is just so hard. For one you need to do it using the project's own tsconfig.json, and typescript doesn't seem to have support for nested projects at all. For a second, you can't assume it's safe to use your own version of typescript in place of the version that the package was compiled with. Their version of typescript won't even be installed because it's just a dev dependency, so now we're back where we started and I think the resolution order is just plain old wrong, even if it was a well-intentioned change.

As a note I've been thinking about these kinds of problems a lot because I'm working on a build system, and I've wondered if typescript might be interested in integrating it.
The system is called macrome, and I've designed it to use the filesystem as the source of truth for built artifacts by prepending header comments which might look something like this:
/* @macrome
 *  generatedby @typescript/macrome-generator
 *  generatedfrom ./foo.ts#f873be2
 * This file is autogenerated. Please do not edit it directly.
 * When editing run `macrome watch` then change the file this is generated from.
 */

My build system is make-inspired and can parse leading comments in source files (with a configurable set of extensions and parsers) using a streaming regex engine that can read a leading comment of any file (by parsing it with a streaming regex engine) and then either close the handle or provide a handle the the remaining content of the file. It also provides watching and caching when coupled with the watchman file watching service, but is also capable of running without it. It views files as a dependency graph, and writes can always trigger other writes. Macrome provides protection against cycles in this graph.
It has some pretty cool characteristics then:

It can check built artifacts for staleness without having to do an actual build at all.
It can always detect and remove orphaned build artifacts.

Some of these advantages seem like they could be very relevant to this problem.

Ah and one last thought. If the built types are stale, won't the the built code stale too? If someone changes code without building I'd rather the type system alert me to the problem rather than than end up running code that doesn't match its own types.

Reading those other duplicate issues I see one counterargument is: it's just wrong to create output side by side with input if you have a choice.
Well, I disagree. I think there are fabulous advantages to maintaining locality. I often think of this as the "component" style of organization, thanks to Ember.
The idea is that when your development process starts to become richer than the feature set of the language, you should colocate related assets to the degree possible. For a web component that might mean having components/foo/index.js and components/foo/index.css. For typescript it can be having foo/index.ts alongside foo/index.d.ts and foo/index.js.
The point is, everything related to foo is in one place. This is tremendously important in the real world because developers need to be able to learn about code, and they often will not get a complete and correct overview of the environment and architecture before they dive in. They need some place to look to understand what it is that they don't understand about the thing they are working with, so hiding your build artifacts is not much of a help.
I don't think I'm too far out on a limb here, after all this is how make traditionally works, and its outputs aren't human readable. It's good sense to keep data that represents the same thing together.
The biggest drawback to mixing files has been that if you specify --outDir dist/ you can always clean up with rm -rf dist. Make is usually able to clean because all generated files have a different extension. This will not be true of javascript source trees. Some .js files will be transpiled from .ts and some will not be, so obviously rm **/*.js is out. But I have a third solution which parses header comments (efficiently) so I think the practical obstacle(s) may soon be removed.

Such a "componentized" solution would be extremely powerful in allowing projects to mix js and ts sources seamlessly during incremental adoption.

I reject the idea that I must never talk to the people who have the ability to make decisions unless what I say fits neatly in a form. This is a very complicated topic.

This is about being respectful of our time. You might notice the issue number here implies forty-seven thousand prior issues that also needed human attention.
It seems like you're asking for something akin to what project references already does - can you compare/contrast that with what you need to happen?

Everyone who has already reported that this behavior is wrong has been dismissed without serious discussion. I'm sorry if you feel that I am wasting your time.

There was a serious discussion the first time this was raised (and indeed another prior one when we designed module resolution in the first place). There is not sufficient time available to rehash this debate with every person who shows up and wants to have their own iteration of that discussion.
You're very encouraged to log a suggestion that outlines exactly how you think this should work. The suggestion template describes the kinds of things we would need to consider that proposal.

Excuse me, I have outlined exactly how I think this should work and why. It is actionable.

Could you link those original design discussions? I do not know where to find them.

You basically outlined the entirety of it at https://github.com/microsoft/TypeScript/issues/47206#issuecomment-999069431
Simply preferring .d.ts is not a thought-out change. How would any build apart from the first one work in this world?

Stale built files would indeed be picked up and used. Alerting users that this had happened would seem to be critical, but their recourse would either be cleaning built assets or running tsc watch.
Are you able to comment on why the sources in a package in node_modules are being interpreted in accordance with the including package's tsconfig.json? You mention project references, but those are for when you own all the interoperating projects. I'm working to unbreak the workflow of using git repos (including forks) as npm packages, which I believe would have great value to the community.

Also you're referring to the problem that building once could cause breakages due to usage of stale code, to which I say this: it will break only when the project is actually in a broken state. I prize this property in tools I use.


PowerToys - "Something went wrong" Whole screen went black. Killed Teams and Edge

Microsoft PowerToys version
<IP_ADDRESS>
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
General
Steps to reproduce
I have no idea. This is the only time this has ever happened.
✔ Expected Behavior
I wasn't actively interacting with PowerToys at the time
❌ Actual Behavior
Version: <IP_ADDRESS>
OS Version: Microsoft Windows NT 10.0.22631.0
IntPtr Length: 8
x64: True
Date: 30/09/2024 10:42:03
Exception:
System.Runtime.InteropServices.COMException (0x80263001): {Desktop composition is disabled} The operation could not be completed because desktop composition is disabled. (0x80263001)
at Standard.NativeMethods.DwmExtendFrameIntoClientArea(IntPtr hwnd, MARGINS& pMarInset)
at System.Windows.Shell.WindowChromeWorker._ExtendGlassFrame()
at System.Windows.Shell.WindowChromeWorker._UpdateFrameState(Boolean force)
at System.Windows.Shell.WindowChromeWorker._HandleDwmCompositionChanged(WM uMsg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Shell.WindowChromeWorker._WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Interop.HwndSource.PublicHooksFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
2024-09-30.txt
Other Software
No response

/dup #30507


Add info btn

What I done

add information tool tip for add recipe page
Improve picture and description  formatting

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.


[PROBLEM] 55. Jump Game

Difficulty
Medium
Problem Description

You are given an integer array nums. You are initially positioned at the array's first index, and each element in the array represents your maximum jump length at that position.
Return true if you can reach the last index, or false otherwise.
Example 1:
Input: nums = [2,3,1,1,4]
Output: true
Explanation: Jump 1 step from index 0 to 1, then 3 steps to the last index.

Example 2:
Input: nums = [3,2,1,0,4]
Output: false
Explanation: You will always arrive at index 3 no matter what. Its maximum jump length is 0, which makes it impossible to reach the last index.

Constraints:

1 <= nums.length <= 104
0 <= nums[i] <= 105

Link
https://leetcode.com/problems/jump-game/

Hey @godkingjay can you please assign me this issue?


Cross join use probe info

What problem does this PR solve?
Issue Number: ref #7443
Problem Summary:
What is changed and how it works?
This is the first part of #7443: enable ProbeProcessInfo for cross join
Check List
Tests

[x] Unit test
already add ut in https://github.com/pingcap/tiflash/pull/7321
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/merge


[SPARK-6629] cancelJobGroup() may not work for jobs whose job groups are inherited from parent threads

When a job is submitted with a job group and that job group is inherited from a parent thread, there are multiple bugs that may prevent this job from being cancelable via SparkContext.cancelJobGroup():

When filtering jobs based on their job group properties, DAGScheduler calls get() instead of getProperty(), which does not respect inheritance, so it will skip over jobs whose job group properties were inherited.
Properties objects are mutable, but we do not make defensive copies / snapshots, so modifications of the parent thread's job group will cause running jobs' groups to change; this also breaks cancelation.

Both of these issues are easy to fix: use getProperty() and perform defensive copying.

Test build #29471 has started for   PR 5288 at commit 3f7b9e8.

On further reflection, this might not be a use-case that we want to support.  I don't think we make any user-facing promises about how / whether these properties are inherited across threads and there are reasons why we may want to discourage this implicit inheritance in favor of explicitly setting the job group in each thread that submits jobs; see https://issues.apache.org/jira/browse/SPARK-4514 for a related discussion.

@jerryshao, since you added unit tests for localProperty inheritance in ffa5f8e, do you know of any actual use-cases that motivate this inheritance?  As far as I can tell, we don't seem to rely on it internally inside of Spark and it's not documented in a user-facing way.  Users can't be relying on it for job group cancellation, since this patch demonstrates that this has always been broken, and it seems unlikely that anyone would choose to use this for cross-thread communication: in order to read and write these properties, you need to have a reference to the SparkContext instance, at which point you might as well just pass the information directly instead of implicitly inheriting it across threads.
If there's no actual use for this inheritance, it might be nice to remove it.

Test build #29471 has finished for   PR 5288 at commit 3f7b9e8.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/29471/
Test PASSed.

Hi @JoshRosen , sorry for late response, looks like I missed this notification. The reason why here changes to InheritableThreadLocal is that: we have such a scenario, we enabled FairScheduler in Spark with two groups, one group is running streaming program, and another group is running query, they separated in two threads and shared with same SparkContext, since streaming job is running in a threadpool when submitted to Spark DAGScheduler, so if we do not use InheritableThreadLocal, we cannot get the right value in child thread, so I changed to this way.

Hi @JoshRosen , I think this is the original PR (https://github.com/mesos/spark/pull/937). I'm not sure is this issue still existed, it is a quite old code.

use getProperty() and perform defensive copying.

+1. It's possible that SparkListener will see some wrong key-values in SparkListenerJobStart.properties without the defensive copying.

@JoshRosen, will this PR be merged? I'm using localProperties in #5473. If we don't copy localProperties, SparkListenerJobStart.properties will just point to localProperties. It will be used in SparkListener, which runs in another thread. If localProperties is changed before a listener uses SparkListenerJobStart.properties, the listener will see the modification rather than the properties when Job starts.

@zsxwing I haven't merged this yet because I had some doubts about how inheritance of local properties should work, especially when threads are re-used.  Let me revisit this now, though, since I think the changes here seem to make the behavior more consistent.  I'll also take a closer look at your use-case in #5473 to try to understand how it would be affected by this change and whether it's prone to any of the weird thread re-use corner cases that can crop up with localProperties.

Test build #30540 has started for   PR 5288 at commit 5d90750.

Test build #30540 has finished for   PR 5288 at commit 5d90750.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/30540/
Test FAILed.

Test build #30542 has started for   PR 5288 at commit 9e29654.

Test build #30542 has finished for   PR 5288 at commit 9e29654.

This patch passes all tests.

This patch merges cleanly.

This patch adds the following public classes (experimental):

  case class Params(

sealed abstract class Node extends Serializable

sealed trait Split extends Serializable

final class CategoricalSplit(

final class ContinuousSplit(override val featureIndex: Int, val threshold: Double) extends Split

trait DecisionTreeModel

This patch does not change any dependencies.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/30542/
Test PASSed.

/cc @andrewor14, what do you think about this fix?  The inheritance + cancellation tests here address an incredibly obscure corner-case that most users might not hit or expect to work (since I don't think that we ever explicitly state that job groups will be inherited across threads).  The defensive copy of Properties seems like a good change by itself, though.
I'd like to try to get some closure on this issue by either deciding that we're going to support the inheritance feature as it was originally described or by removing this feature and instructing users to manually set job groups in child threads; at this point, I think that either option could work since the current behavior is broken.  We could also decide to just leave the inheritance alone and only do the copying change.

Test build #706 has started for   PR 5288 at commit 9e29654.

Test build #707 has started for   PR 5288 at commit 9e29654.

Test build #31033 has started for   PR 5288 at commit 9e29654.

@JoshRosen is it ready to go? At least, #5473 needs the defensive copy of Properties to avoid breaking tests. Thank you.

Merging this. The defensive copying is blocker for #5473 .


Store data on local computer

Hey there,
I've been looking through all your documentation. And if I'm understanding correctly this only builds the Meteor client, not the server, correct?
Is there a way using this package to connect to a remote a server for a few things, but store most of the data locally?
thanks!

Hello,
yes, this is a client only integration.

Is there a way using this package to connect to a remote a server for a few things, but store most of the data locally?

Well you can do that in many ways. Some people are using https://github.com/GroundMeteor/db for that afaik. You can use localStorage or indexedDB (indexedDB will be supported in 1.0) or you can just write you own storage mechanism on the desktop side. The problem is that you have to dump your collections and then restore them at next app startup but it's definitely doable.
Bundling mongo and meteor server is in the plan after first 1.0 release.

@wojtkowiak do you have a planned release date for 1.0 (or just the new client storage facilities)?
We're running into some issues with localstorage being unavailable sometimes.
Is there any branch/defined issue we could work on to speed up the release of these functionalities?

@wojtkowiak we tried using LocalForage and also created a module for the ElectronSettings package.
Can share the code if required, or discuss which implementations could/should be considered :)


Start hub from inside the frontend tests

This is a left over from #93. Right now we start the hub once and then run all the frontend tests against that one instance. This is good because we can have concurrent access. The downside is that we get one big log file which makes it a bit tricky to find the relevant parts when a test fails and subsequent tests might also fail because of a previous failure.
In the unittests in everware/tests a new (simplified) hub is started for each test. We don't get to see any log files for tests that pass and always get a clean slate for each test. This issue should investigate if it is possible to get a similar setup for the frontend tests while still being able to have concurrent access to a hub for multi user testing.

Any thoughts on this @anaderi?


feat(overlay): add maxWidth and maxHeight

@jelbourn looks like there's a linting error.

Fixed lint
(I don't know why WebStorm doesn't trim trailing whitespace sometimes...)


[HTK] Problems with MicStream on Hololens

Describe the bug
Hello, I am experiencing several problem with the Microphone on the Holotoolkit.
Here what I try to achieve: Record the voice input and send it to Azure Speech-To-Text, the only way I found to do this is to use the MicStream class, save the data in a file then upload the file to Azure.
Here are my problems:

When I try to to stop de record, if I call MicStream.MicStopRecording, the app crashs despite the fact the file is well saved on the Music folder. However calling MicStream.MicStopStream seems to work. Is this normal and a viable solution? I was not able to catch any error since the application totally crashes.

I cannot read the file once created, the path is ?/Music/MicStreamRecordings/... , I enabled the application capabilities to access audio library. I don't have the full path since I did not use MicStream.MicStopRecording, I tried

#if ENABLE_WINMD_SUPPORT
        Debug.Log("test");
        Debug.Log(KnownFolders.MusicLibrary);

    #endif

however the Hololens build does not seem to enable this compiler condition, I tried Environment.GetFolderPath(Environment.SpecialFolder.UserProfile) but I get an error UnauthorizedAccessException. I am not even sure that I have access to this folder.

Finally, I am doing all this to send byte[], is there any better method than using files to achieve this?

Thank you
Here my MicStreamInitialization:
MicStream.StreamCategory streamType = MicStream.StreamCategory.HIGH_QUALITY_VOICE;
MicStream.MicInitializeCustomRate((int) streamType, AudioSettings.outputSampleRate);
MicStream.MicSetGain(1);

And how I start record:
MicStream.CheckForErrorOnCall(MicStream.MicStartRecording(fileName, false));

And here how I read the file:
byte[] data = File.ReadAllBytes(microphoneRecorder.GetFileLocation());
Expected behavior
MicStream.MicStopRecording does not make the application crash and return the file path that should be accessible.
Your Setup (please complete the following information)

Unity Version 2019.1
MRTK Version 2017.4.2

Target Platform (please complete the following information)

HoloLens

Assigning to @Yoyozilla. I do not know that we will continue to provide fixes for moving the holotoolkit to newer unity versions.

I understand, but this is more a problem about the UWP API. I guess also that the MRTK 2 will have a similar feature implemented not much differently. This could be enough for me to do the fix.
Thank you.

Is this something we can repro on MRTK v2?

I could make it works by using an UWP exemple for Windows Phone instead of the MicStream plugin+script from the HTK. I let you choose to close or not this issue.

Thanks for the update! we are not actively updating HTK anymore so I will close this issue. We will make sure MicStream works in MRTK v2.


Investigate memory issue

While running a 3 day experiment with Webindex on EC2, I noticed that workers were constantly being killed for using two much memory.  I started off with 128 threads and 4G per workers.   I increased to 5G and then 6G and workers were still being killed or dying.
When the workers had 4G and were being killed I looked in the YARN logs to determine why and found it was memory usage.   After increasing the memory, I noticed they were still dying (based on attempt count in task ID).  However I did not inspect YARN logs again to verify it was memory related, I should have.

Resolved by fluo-io/fluo#648


[CARBONDATA-1955] Delta DataType calculation is incorrect for long type

Problem:
In case of Long type, the delta data type is always choosing the Long type.
But it should choose the datatype based on diff (max-min)  of max and min values.
Solution:
Corrected to choose the delta data type based on max and min values.

[X] Any interfaces changed?
NA

[X] Any backward compatibility impacted?
This issue must be synced to 1.2.0 branch

[X] Document update required?

[X] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.
Added unit test cases to test codec selection

[X] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.
NA

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/2637/

Build Success with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1235/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2459/


Unable to run Stryker on react type script project--Getting error

I have configured Stryker for my project in React Type script. But unable to generate the results. Its throwing me error on running (Emit Error.)
This is my project where i am trying to run. Can anyone suggest me a solution for this.
joyal.zip

Hi @JoyalJoyMadeckal 👋 I've managed to get it working ❤
First of all, there is an issue in more recent versions of react-scripts. It doesn't support directories starting with a .. For example .stryker-tmp, the temp directory Stryker creates to run its sandboxes 🤦♂. See https://github.com/facebook/create-react-app/issues/7660
Luckily, we've just merged configurable temp directory: #1644. It is released with stryker 2.1.0.
Update your stryker dependencies:
"@stryker-mutator/core": "^2.1.0",
"@stryker-mutator/jest-runner": "^2.1.0",
"@stryker-mutator/typescript": "^2.1.0",

And add this to your stryker.conf.js
 tempDirName: 'stryker-tmp',

There was one more issue. It has to do with your css files. They are generated and ignored with .gitignore. Therefore, Stryker doesn't know to include them. So either remove *.css from .gitignore (not ideal) or override the files property in stryker.conf.js:
    files: [
      'src/**',
      'public/**'
    ],

Result here:
joyal.zip
Have a lot of Joy mutation testing!

Ah yes, forgot one more thing. You'll have to remove transpilers from your stryker.conf.js. Jest is a magical tool which takes care of transpiling ts to js for us. No need to "compile twice".


pre-commit instructions not in sync with ruff-pre-commit repo

https://github.com/charliermarsh/ruff/blob/605416922d193d2261bc8b5ed0de8741691a018d/README.md#usage has
- repo: https://github.com/charliermarsh/ruff-pre-commit
  # Ruff version.
  rev: 'v0.0.233'
  hooks:
    - id: ruff

but the latest tag is https://github.com/charliermarsh/ruff-pre-commit/tree/v0.0.231 (there is no v0.0.233)

Thank you. We update the README when we make the release commit, but the release itself takes a bit. (This release also failed due to us finally hitting a PyPI limit.) I'll back this out for now until 0.0.233 is out.

Fixed!


feat(conf) way to blacklist listener flags

It should be possible to disallow certain flags from parse_listeners on a per-call basis.
e.g. ssl should be disallowed from stream_listen

I did this on mock branch (which is not merged), feel free to steal some of the idea from there, and make a PR:
https://github.com/Kong/kong/pull/3237/files#diff-a2237d21dd96315727f1b771bf0111f5R424

This is not needed anymore as we removed service mesh.


Random STARTTLS anecdote

mendel
27 days ago
made a change today to only permit FIPS ciphers in STARTTLS on our mail servers. the senders that are having trouble are all US government :facehoof:

reaperhulk
[10 months ago]
If you need FIPS compliance there are quite a few things to watch out for...
OpenSSL has a bunch of forms of FIPS. There's the legacy FIPS canister from 1.0.x, there's the RHEL style FIPS patches, and there's the new OpenSSL 3.0 FIPS provider. Each one behaves differently with regard to how to enable it, whether it allows non-FIPS algorithms in FIPS mode, etc.
For example, enabling FIPS in RHEL8 requires following section 9.1 in the security policy for this CMVP certificate (https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4271), which notes that the kernel must be booted with fips=1 as an arg or else it is not compliant (despite potentially appearing to be so).
Once you've verified that you have correctly enabled it (shockingly hard especially at scale) and you're using FIPS only algorithms (which some of these enforce and others do not), then you've got even more nonsense. For example, what if you need BGP with MD5? Well, that's not FIPS, but it turns out you may have to do it anyway. So now you've got to figure out a way to run FIPS and non-FIPS alongside each other. Or perhaps you're using AES GCM. FIPS compliant right? Well, FIPS has very weird requirements for nonce generation that include generation inside the FIPS boundary so simply generating 12 random bytes with your FIPS CSPRNG is arguably insufficient.
I could go on for a long time here, but honestly any organization that starts needing FIPS will learn these lessons via painful interactions with auditors and their own engineering teams screaming at them. But remember, scrypt is FIPS compliant because its final step is PBKDF2 :cool-cat:


Any support available with Camera2 API

We are working on real time video streaming using Lib streaming library. Lib streaming library supports old Camera api, all is working fine but we required to integrate Camera2 api to Lib streaming library. Some of functionality like video preview display using Camera2 api, we integrated but we need to get video frame data for stream continuously, how to get it? please suggest the way forward.
In Lib streaming library, they used below callback method for frame data for old camera api:
mCamera.setPreviewCallback(new Camera.PreviewCallback() {
@Override
public void onPreviewFrame(byte[] data, Camera camera) {
// here we get frame by frame data
}
});

Hi anandk32,
Maybe you can try to use gles.

Thanks for the reply, but can you please elaborate more on this. I didn't catch that how to implement with GLES with Camera2, Can you suggest any example or steps?

@anandk032 any progress with this issue?

yes, we integrate by own with Camera2 api
On Wed, Jun 14, 2017 at 2:17 PM, Ulrich-Matthias Schäfer <
<EMAIL_ADDRESS>wrote:

@anandk032 https://github.com/anandk032 any progress with this issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fyhertz/libstreaming/issues/159#issuecomment-308365978,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANOKJfgSJqyJ0at05U-Cy9EO6LpaU3L5ks5sD54egaJpZM4G3V3M
.

any chance, that you can share the code? I have a similar problem at the moment

Okay, give me your email address. I will talk with you.
On Wed, Jun 14, 2017 at 4:36 PM, Ulrich-Matthias Schäfer <
<EMAIL_ADDRESS>wrote:

any chance, that you can share the code? I have a similar problem at the
moment
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fyhertz/libstreaming/issues/159#issuecomment-308399066,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANOKJbO7xNpsmgO1MzNkPtoz65AFl6PUks5sD77RgaJpZM4G3V3M
.

<EMAIL_ADDRESS>Thanks!

I will guide you how to integrate it.

@anandk032 @Fuzzyma @RyandHo Hi guys, I too am looking into integrating the library with Camera2. Would anyone be able to share on how you approached the problem? Thank you!

@anandk032 , how did you resolve this issue, please

You need to use MediaCodec to encode the images from Camera2 yourself and then use one of the packetizers to pack the encoded images and send them out. I made a demo for people who are interested in use libstreaming with Camera2 API. Check out https://github.com/hq286/Camera2RTPStream


Update the Server name

I've tested, the Server name "(localdb)\Projects13" lead to an error, the right value is "(localdb)\ProjectsV13".

@phuctv95 thanks for this fix. Can you make the change in the new repo https://github.com/aspnet/AspNetDocs ?


Warn when background tasks exceed their configured period

Fixes #3648.

Nice, just got the first example:
2023-02-21T10:06:49.002602Z  WARN compaction_loop{tenant_id=b432425593b3a450e6942a858034aa68}: task iteration took longer than the configured period elapsed=2s 176ms 407us 999ns period=1s task="compaction"

This does make me think it's a bad idea to use humantime here for elapsed.

Hybrid version after 5a3552c looks like:
WARN compaction_loop{tenant_id=8b94afd70534bda706ae5d4f49775b13}: task iteration took longer than the configured period elapsed=1.162653177s period=1s task="compaction"


TAJO-1934: Test failures in TestPgSQLQueryTests due to sort order

Add sort option test by test.

+1 LGTM


Add initial OCI container support

Description of changes
These changes add OCI container support for Tegra devices on NixOS. This is accomplished using NVIDIA's newer nvidia-ctk tooling, which uses the CDI spec. Docker does not yet support this spec in any released version, but will have experimental support for it in their next release. Podman has supported this spec for a few years. See changes to README.md for more notes.

Testing
Tested running a simple cuda program on an orin-agx-devkit0 with the nvcr.io/nvidia/l4t-base:35.3.1 image.

Could you also add an automated test for this functionality to our internal nightly tests?

Could you also add an automated test for this functionality to our internal nightly tests?

Already added!

Notice （outdated nvidia-container-toolkit):  It has been quite some time since I last upgraded the version of the nvidia-container-toolkit. If you have the time, please look at how to update the nvidia-container-toolkit to the latest version? The current version of nvidia-container-toolkit is outdated.  thanks

refs:
https://github.com/NixOS/nixpkgs/issues/272235
https://discourse.nixos.org/t/using-nvidia-container-runtime-with-containerd-on-nixos/27865/25

@GTrunSec I'll draft up a PR for nixpkgs targeting Nvidia container toolkit v1.15.0. This PR is highly focused on tegra support, but it would be great to use the same stuff on x86_64 too.

@jmbaur, sweet, thanks for your efforts. Feel free to ping me to review that code once you are ready.

How do https://github.com/NixOS/nixpkgs/pull/284507 and https://github.com/NixOS/nixpkgs/pull/291828 relate to this?

How do https://github.com/NixOS/nixpkgs/pull/284507 and https://github.com/NixOS/nixpkgs/pull/291828 relate to this?

The goal is to have all CDI support come from nixpkgs and eventually remove the tegra specific CDI support from this project. We need to verify that the newly added CDI support in nixpkgs works on tegra devices.


fix typo in README.md

Hey, just noticed this "huge" type

Hi @code4aman, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

Thanks!


Migrate to hack arrays internally

This only touches the implementation details.
The public and protected API (and private in traits) remains backwards compatible.
Mostly done to make the migration process easier later.

n.v.m. about the exposing of the mutable Vector thing.
I removed a new Vector() remove before that explicitly prevented this.
Will remove immediately.

Retargetting Fred's 4.x branch


NPE check not triggered for getters

I have a getter in a class that returns an Object. When a function of this object is called (eg. a.getObject().doSomething();), infer does not trigger a warning for a possible NullPointerException. Is this the designed behaviour or is this an issue at my end? If this is the designed behaviour, is there a good way of ensuring such things don't pass on to production?

Can you provide a full minimal example that reproduces your issue? Shooting from the hip, you could add a @Nullable annotation to the return of your getter method so that Infer assumes it can return null.
More (speculative) details: When Infer doesn't know about a function for whatever reason (no implementation available, or Infer failed to analyse it), Infer will treat that function "angelically" and assume that eg it never returns null. This is done to prevent being too noisy. This may or may not be what's happening in your case, we'd need to see some code to know for sure.

Closing for now, please reopen with more info if this is still an issue with the latest version.


New sample: Edit features with feature-linked annotation

Hello,
Some areas I would like some feedback are:

the identifyFeature() method identifies a feature in the topmost layer. This implementation handles the case where the user moves a point very close to a line, then wants to move either feature later. Otherwise, an exception is thrown when both features are selected, then moved.

I created updateAtttributes() to update the feature when it is moved, but the logic to update the user entered attributes is located within EditAttributesDialog

in the samples review, I received feedback that the sample does not need to prompt the user if they want to move the point, as that is outlined in the README.

is README Java specific enough?

Thanks!

Hi @sclaridge ,
To address your questions:

* the `identifyFeature()` method identifies a feature in the topmost layer. This implementation handles the case where the user moves a point very close to a line, then wants to move either feature later. Otherwise, an exception is thrown when both features are selected, then moved.

We don't have to overcomplicate the sample to account for every single case, so this sounds like a good compromise to me.

* I created `updateAtttributes()` to update the feature when it is moved, but the logic to update the user entered attributes is located within `EditAttributesDialog`

That's indeed a bit tricky. We could have the dialog return a Pair<String, String> with the information for each edited property, and then do the actual editing within the method updateAttributes(). You could have a go at that and see whether it looks clean and readible?

* in the samples review, I received feedback that the sample does not need to prompt the user if they want to move the point, as that is outlined in the README.

That seems fair, and the readme looks OK in that regard to me 👍

* is README Java specific enough?

The Java-fied terminology looks good to me!
For the how it works section, I'm personally not a fan of the phrasing 'a dialog opens', since we'd generally write these sections in phrasing along the lines of create/open/add/ a dialog (not sure of the grammatical term here).
However since this has been agreed upon in review, let's just leave as is for consistency with other platforms 👍


Improve the User Interface for Admin Log In Page

Replace the existing basic user interface with a better and clean one.
The Form should be responsive, clean, and minimally animated.

I would like to contribute to this issue.

I would like to contribute to this issue.

@luckykumarirai , follow the project setup docs and try to run it locally. It's great to see that you are interested to attempt the issue. But issues can't be assigned before 21st Jan.

@luckykumarirai , follow the project setup docs and try to run it locally. It's great to see that you are interested to attempt the issue. But issues can't be assigned before 21st Jan.

can i work on this

can i work on this

I want to work on this issue

I want to work on this issue

@435akashjha , I am assigning this issue to you.

@435akashjha , I am assigning this issue to you.

Hi, I would love to work on this issue. Please assign it to me.

Can I work on this issue as a GSSOC 2021 participant.

I am a GSSOC'21 participant and I wish to work on this . Hope to hear back from you .
There will be 3 parts of this page

Header with navbar
Main body
Footer
Thank you .

I would like to contribute to this issue. Kindly assign this to me as a part of GSSoc'21.

I would like to work on this issue . Please assign this to me .
I'm a GSSOC'21 participant.

@nikitajuneja1 assigned this issue to you.

Hey, I'm gssoc'21 participant, I would like to give my hand in this project. Please assign this issue to me. @amanjha8100


Do we need docs/content/en/docs?

docs/ is supposed to be the same with docs of the latest version(e.g. docs-v0.44.x/).
Also, When we jump "Documentation" from the top page with a specific version being selected, we are navigated to docs/. This should be docs of the selected version.

This is a legacy problem. Previously, we only have one single docs which is /docs/ and after that when we start versioning the docs, I thought link to /docs/ be referred out where (on other site blog, for instead) should be keep alive. That's why we decided that we have to keep /docs and make it points to the latest version docs. But, I get your point on this 🤔

I meant this;
https://github.com/pipe-cd/pipecd/assets/16733673/2eaf9fdd-f3af-4b4d-bd9c-d8e237a7b295

How about this?

remove /docs/.
configure to redirect all /docs/ to the latest URL (e.g. /docs-v0.44.0x on 2023-06-29)

because /docs/ and the latest versioned docs contain the same content.

Do you mean after that (on version v0.45.x release and so on), we don't do redirection any more, any require versioning docs url from now on 👀

I meant we would do redirect /docs/ to the latest version.
/docs will be removed because all accesses to /docs/ will be redirected to the latest docs.

@khanhtc1202
How about this simple way to do?
https://github.com/pipe-cd/pipecd/pull/4458

Remove /docs-dev
Treat /docs/ as master(I guess we already do that in our mind)

I looked at KubeFlow and they seem to do in this way.

Sorry but I don't think that way. First, the master means to dev version of the docs. Since it is docs for the not yet released version, I prefer to use the word dev over latest or master to mention that it's dev (not released) directly.
And besides, I don't think treating the /docs as master/dev/latest is a good idea. It should be treated as stable/latest-released docs, since it clearly means it's the documentation (users may don't aware of docs has other versions so /docs can be used as the only one)
This is the versioning of argocd (latest: dev / stable: latest released / versioning: ...)

I just started to think the current directory structure and writing flow is good enough.

We already have make gen/stable-docs.
Removing /docs/ and setting up the redirect to the latest version is not that easy.

So I'm thinking to close this issue until someone has the same thought.
@khanhtc1202 wdyt?

For sure, let's make a discussion for this later if we have a better idea around the docs :+1:


fix: 🐛 ci/cd revamp

Current dependencies on/for this PR:

master

PR #5   👈

PR #2

PR #3

PR #4

This comment was auto-generated by Graphite.


Add check for '(' before trying to make substring

Modifed the "cutMethod" function to add a check if the character '(' exists at all, before attempting to make a substring with it or not. I encountered this issue while it was processing "M:SolidShineUi.FlatWindow.DisableMinimizeAction" in my code's XML file.
It seems to me that C#'s XmlDoc doesn't mind if you include the parantheses or not for a function that has no arguments.
If you want to test this yourself, you can try downloading the compiled DLL and files from the latest release of my library. I was trying the net6.0-windows version. The line in question is line 494 in the documentation XML file included with my library.
I encountered another bug while trying to generate the documentation, which I'll cover in another issue.

All seems good


Implementation of basic LINQ methods

The project should provide its own implementation of LINQ methods which should be lightweight and fast as possible, ideally a chain of their invocations should create a single boxed state machine instead of multiple chained observers.
State and async support is out of scope for that issue. Only basic implementation is required at the moment to make the project usable.

[ ] Aggregate
[x] All
[x] Any
[ ] Average
[ ] Cast
[ ] Contains
[x] Count
[ ] DefaultIfEmpty
[ ] Distinct
[ ] First
[ ] FirstOrDefault
[ ] Last
[ ] LastOrDefault
[x] Max
[x] Min
[ ] OfType
[x] Select
[ ] Single
[ ] SingleOrDefault
[x] Skip
[x] SkipWhile
[x] Take
[x] TakeWhile
[x] Where

Since the C# compiler isn't able to deduce types well and it's not possible to have extension methods having the same return type as the source, this feature might be never shipped or be limited to Select, While, All, Any, Count.


Update GitHub Actions CI

The following updates are performed:

update actions/cache to v3
replace unmaintained actions-rs/toolchain by dtolnay/rust-toolchain
replace unmaintained actions-rs/cargo by direct invocation of cargo

Thanks!


bug get_rotation on Vehiclebody

get_rotation on VehicleBody return value only for 0 to Pi/4 (0 to 90 in deg) or for 0 to -Pi/4 (0 to -90 in deg)

bump

Please fix this issue

Please fix this issue

Alright, we got it, but just bumping issues like that won't fix them magically.

Also giving more information on the actual issue, steps to reproduce and maybe a test project that exhibits it would be better than just bumping. The initial report is not precise enough as it only says that the function works in a range, and "doesn't work" in another range; what does "doesn't work" mean? Does it return 0, and error, or a wrong value?
I know developers can test that by themselves, but to get a bug fixed, it's much better when the bug reporters take some time to simplify the work for developers. There are after more than 1000 issues opened for a handful of voluntary contributors.

Take the Truck Town demo, add print("Rotation: %.1f" % rad2deg(get_rotation().y)) to vehicle.gd.
You will see that the returned rotation of the car will vary from -90 to 90 degrees, but 180 degrees are not enough for a full rotation, as illustrated by the image above (except that 90° are PI/2 and not PI/4 @alexolin).
e.g. if get_rotation returns 0°, is the car pointing east or west?

Thanks for the details, I tested and the fact that it concerns the Y component is pretty relevant. I believe this bug has the same cause as #1479.

this is kind of unavoidable with euler rotations, and I recommend not using them (there is always better ways to do the same with vector math).
That said, we should improve how euler rotations are presented to the user, and this has been noted down in the 3.0 compatibility breakage list.

closed, as duplicate for #1479


deepstream with webRTC

Is there anyway to use deepstream pipeline with webRTC as source?

DeepStream plug-ins can be used as any other GStreamer plug-ins. So if you have working pipeline with WebRTC as source, then you certainly can plug DeepStream into it.

@bpawlik Thanks for your suggestion, i was tying to run it on AWS EC2 instance, and I don't find any GStreamer examples with webRTC as source (with/without aws) please let me know if you have seen it anywhere. Thanks.


You must specify the input hosts file(only one)

I can't run the update_hosts.py
Sorry to bother with such lame questions, but I cannot figure out how to manually specify the input or fix this problem..

Please first check the usage before you open an issue.
Sample: update_hosts.py host
usage: update_hosts [OPTIONS] FILE
A simple multi-threading tool used for updating hosts file.

Options:
  -h, --help             show this help message and exit
  -s DNS                 set another dns server, default: 2001:4860:4860::8844
  -o OUT_FILE            output file, default: inputfilename.out
  -t QUERY_TYPE          dig command query type, default: aaaa
  -c, --cname            write canonical name into hosts file
  -n THREAD_NUM          set the number of worker threads, default: 10


Provide initializer for binding in guard for earlier Swift compatibility

No functional change with this change. This allows the plugin to continue to build in Xcode 13.3.

@swift-ci Please test


Invalid autoload for Bundler::Specification?

It looks like lib/bundler.rb specified the following autoload
module Bundler
  # ...

  autoload :Specification,         "bundler/shared_helpers"

  # ...
end

even though Bundler::Specification was removed in 0f97e4fcea15b2e5f2d6d045c686b5750c5d54de.  Should this be removed?

Probably? Try removing it and see if the specs still pass?

Merged!
For context on this issue: I'm writing a tool which enumerates methods defined at a point in time in the ruby VM.  As a result, for every top level constant the following is performed:
SomeConstant.constants.map { |const_name| SomeConstant.const_get(const_name) }

therefore, since my gem uses bundler, it always ends up doing the following
Bundler.constants.map { |const_name| Bundler.const_get(const_name) }

which triggered the invalid autoload of Bundler::Specification


[PE-D][Tester C] Same name cannot be added twice

A user should be able to input 2 contacts of same name but different address, email and phone number, which should be a plausible scenario. The app however assumes the person's name solely to be a unique identifier. Perhaps you can include a combination of the fields for a unique person contact.

Labels: severity.Low type.FeatureFlaw
original: eunrcn/ped#3

its intended to be like that


sf::Clock restart() returns negative values in continuous work

Hello. I'm using SFML with a program for LED displays for railroad comunication in Russia. It displays nessesary information about trains on a screen and the hardware is converting video signal to LEDs. This program must run continuously and preferrably without restarts. I found an issue with SFML and how it calculates time (see below).

OS: Windows 10 x64
SFML Version: 2.5.1
Compiler: Microsoft Visual Studio Enterprise 2017

I'll go straight to the point. While testing my program, I encountered an issue, where after continuous work for about 10-11 days, the program started returning negative time and it disrupts normal work. I found the issue is in Win32 ClockImpl implementation and similar to issue #1167 . Also I found out that it depends on hardware and return value of QueryPerformanceFrequency function.
This is current version of ClockImpl.cpp:
...
QueryPerformanceCounter(&time);
...
// Return the current time as microseconds
return sf::microseconds(1000000 * time.QuadPart / frequency.QuadPart);

The issue is in return statement. time.QuadPart type is signed __int64, which means if it goes over 9 223 372 036 854 775 807 it will go to negative numbers. In this calculation time.QuadPart needs to only be over 9 223 372 036 855, because this number is multiplied with 1000000 first. On my test computer, QueryPerformanceFrequency function returns 10000000, which means there is 10000000 tick per second. In this sircumstances time.QuadPart reaches it's overflow value in<PHONE_NUMBER>855 / 10000000 seconds or 922337,2 seconds or 256,2 hours or just only 10,6 days.
On my home computer, QueryPerformanceFrequency returns 3609372. If we calculate time it takes to overflow with this frequency , it is 29,57 days, which is still not good. This program should run uninterrupted for several months or years.
This issue is easily fixable. we just need to exclude a calculation with big intermediate result, for example like this:
// Return the current time as microseconds
double inverse = 1000000 / frequency.QuadPart;
return sf::microseconds(time.QuadPart * inverse);

In my program I used sf::Time elapsed = clock.restart();. Then I add this to my different timers to see if timer is fired, like sf::Int64 elapsedMicro = elapsed.asMicroseconds(); foregroundElapsedTimer += elapsedMicro; Which calculates elapsed time like:
Time Clock::restart()
{
    Time now = priv::ClockImpl::getCurrentTime();
    Time elapsed = now - m_startTime;
    m_startTime = now;
    return elapsed;
}

If now is suddenly goes to negative like I showed above, then elapsed time will be negative too and I doubt this is intended behaviour.
Unfortunatley I already changed time calculation in my project, because I needed it to work. You can reproduce this behaviour by adding a static number of tick to time variable in ClockImpl.cpp and wait until the overflow happens, like time.QuadPart = time.QuadPart +<PHONE_NUMBER>370;. This will simulate that your computer is running a long time. Of cource the constant you're adding must be calculated for your own computer (frequency and current ticks is different). Or just imitate same calculation in your own program, so that you don't have to rebuild SFML.

Nice catch, you're probably the first SFML user to run the clock for so long 🙂
And thanks for the elaborate description!
Even if we migrate to Chrono in SFML 3, we should still fix this in SFML 2.

I am not familiar with the implementation of the SFML internals since I use my custom Timer class which I'd like to share for some inspiration:
/// Helper class exposing methods for simple time measurement.
class Timer final {
public:
  /// Gets the number of milliseconds elapsed since the start of the server.
  /// @return An integer representing the milliseconds elapsed since the start
  /// of the server.
  /// @remark Be aware that the resulting value can overflow which is handled by
  /// the internal helper methods of this class.
  static inline auto now() -> const uint32 {
    using namespace std::chrono;
    static const system_clock::time_point ApplicationStartTime =
        system_clock::now();
    return uint32(
        duration_cast<milliseconds>(system_clock::now() - ApplicationStartTime)
            .count());
  }

  /// Gets the number of milliseconds between the given times.
  /// @param PreviousTime The earlier time.
  /// @param NewTime The later time.
  /// @return Number of milliseconds between the given times.
  static inline auto differenceInMilliseconds(const uint32 PreviousTime,
                                              const uint32 NewTime)
      -> const uint32 {
    // Handle overflowing numbers.
    if (PreviousTime > NewTime) {
      return (0xffffffff - PreviousTime) + NewTime;
    }
    return NewTime - PreviousTime;
  }
};

@Mozzg thanks for the detailed analysis. Would you be willing to provide a PR for the suggested fix?

@Mozzg thanks for the detailed analysis. Would you be willing to provide a PR for the suggested fix?

I tried to create a pull request (https://github.com/SFML/SFML/pull/1771). I'm not quite familiar with GitHub and I hope I've done it correctly. Also I can't test or compile my changes, because I used already compiled SFML libraries and I don't know how to compile SFML myself. Can anybody confirm that my changes are correct?
Also a program to test my changes and test the overflow is very dependant on a computer and current tick count, so creating a code for testing is difficult. I can help with that via Discord for example (Mozzg#6976).

Fixed with #1771


PayPal Payment suddenly not working any more

I have a problem with the payment suddenly, but it worked before and I just don't get it... I just posted the problem on stackoverflow as well: http://stackoverflow.com/questions/40684154/paypal-payment-not-working-any-more-laravel-paypal
Can you maybe help me with that? (Doesn't mind if you answer it here or on stackoverflow)

@schuesslerf  sorry man for the late response . I was bit busy and did not have much time to check the reported issue. can you please clarify to me what's the error/ exception you get

Hello, I now somehow got it fixed and I have no idea why, it seems like some formatting changed the behaviour (and the try-catch-blocks). I don't know why, but however it seems to work now.... I have one other question: Do you know if its possible to enter more then one amount for shipping costs? Like 2.5 for one product, 2.7 for the other, and 9.2 for the third, you know what I mean? Or is this not psosible?

@schuesslerf  no , but you can count the total  and set it at once when you set the shipping with details object


Dynamic Groups defined in <2.0 break in >2.0

Environment

Nautobot version (Docker tag too if applicable): 1.6.x ->2.0.1
Python version: 3.11
Database platform, version: psql
Middleware(s): n/a

Steps to Reproduce

In Nautobot 1.6.x create Dynamic Group using Tag tenant & status as a filter.
Upgrade Nautobot to 2.0.1
Attempt to open the dynamic group in the GUI

Expected the dynamic groups defined in 1.6.x to migrate safely to 2.0.1 and be able to open, view & edit the pre-upgrade dynamic group.

#4515 has restored tags to be used for filtering, and can successfully be applied to new dynamic groups, but so far all of the groups already setup cause log & display errors.
eg:
(
  tags__slug='campus' AND status__slug='active' AND tenant__slug='<tenant>'
)

Logs show warnings when NB2 launches:
07:33:41.815 WARNING nautobot.extras.models.groups :
  Filter for DynamicGroup "<tenant> Campus" is not valid

When attempting to open the dynamic group in GUI receive a Server Error:
<class 'KeyError'>

'tag'

Python version: 3.11.6
Nautobot version: 2.0.1

Hi,
They are associated with dcim.device; and yes they're using tag filters. I can make new groups ok now, but I can't view or edit the existing ones.

Thank you so much for the prompt response.
Can you go to nbshell and run this for loop to see if it fixes the issue? I can reproduce the KeyError when there is an outdated tag filter in my DynamicGroup filter data. This for loop goes through all the DPs and replace tag with tags.
for dp in DynamicGroup.objects.all():
    if "tag" in dp.filter:
        dp.filter["tags"] = dp.filter.pop("tag")
        dp.save()

Yep, that's perfect - they now load as expected.


GCov fail when testing c file without a header

I want to test a file that doesn't have a corresponding header file. e.g.
src/foo.c
int sum(int a, int b)
{
    return a + b;
}

test/test_foo.c
#include "unity.h"
#include "foo.c"

void test_sum(void)
{
    TEST_ASSERT_EQUAL(3, sum(1, 2));
}

ceedling test:test_foo runs without issue
Test 'test_foo.c'
-----------------
Running test_foo.out...

--------------------
OVERALL TEST SUMMARY
--------------------
TESTED:  1
PASSED:  1
FAILED:  0
IGNORED: 0

But ceedling gcov:test_foo fails with the following error
Test 'test_foo.c'
-----------------
Running test_foo.out...

--------------------------
GCOV: OVERALL TEST SUMMARY
--------------------------
TESTED:  1
PASSED:  1
FAILED:  0
IGNORED: 0

---------------------------
GCOV: CODE COVERAGE SUMMARY
---------------------------
build/gcov/out/foo.gcno:cannot open notes file
build/gcov/out/foo.gcda:cannot open data file, assuming not executed
ERROR: Shell command failed.
> Shell executed command:
'gcov -n -p -b -o "build/gcov/out" "foo.c"'
> Produced output:
No executable lines
> And exited with status: [1].

Exception raised in plugin: gcov, in method post_build
/home/ubuntu/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/ceedling-0.31.1/lib/ceedling/tool_executor.rb:88:in `exec': ShellExecutionException (ShellExecutionException)
        from /home/ubuntu/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/ceedling-0.31.1/plugins/gcov/lib/gcov.rb:89:in `block in report_per_file_coverage_results'
        from /home/ubuntu/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/ceedling-0.31.1/plugins/gcov/lib/gcov.rb:86:in `each'
        from /home/ubuntu/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/ceedling-0.31.1/plugins/gcov/lib/gcov.rb:86:in `report_per_file_coverage_results'
        from /home/ubuntu/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/ceedling-0.31.1/plugins/gcov/lib/gcov.rb:63:in `post_build'
        from /home/ubuntu/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/ceedling-0.31.1/lib/ceedling/plugin_manager.rb:99:in `block in execute_plugins'
        from /home/ubuntu/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/ceedling-0.31.1/lib/ceedling/plugin_manager.rb:97:in `each'
        from /home/ubuntu/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/ceedling-0.31.1/lib/ceedling/plugin_manager.rb:97:in `execute_plugins'
        from /home/ubuntu/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/ceedling-0.31.1/lib/ceedling/plugin_manager.rb:85:in `post_build'
        from /home/ubuntu/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/ceedling-0.31.1/lib/ceedling/rakefile.rb:78:in `block in <top (required)>'

Hi, @rickymohk. So sorry about this. Thank you for submitting the issue. I can confirm that the various improvements in the 1.0.0 prerelease have already fixed this problem some time ago. We don't have the resources to support multiple active versions of Ceedling. Since 1.0.0 is (finally) on the verge of being released, this bug in 0.31.1 will, unfortunately, need to go unfixed.

Is there any workaround for 0.31.1? I want  to at least create an empty coverage for that file so the denominator of the overall coverage is correct. But I can't because if I include this file it will crash and abort the process and any files come after will not be covered.

You seem to be having whole other problem than you underlined.
Why are you including foo.c in your test file and not foo.h and let compiler create foo.c and then reference its functions in test? Then your gcov will find the foo.c (which now it doesn't, because it is inlined - basically part of test file). If that foo.c is actually static inline implementation file, then name it at least foo.h and include that into the foo.c (just with that include) you will be able to see the coverage of that file.

As I mentioned because there is no foo.h. I am tasked to write tests for an existing project which source code can no longer be modified. Anyway I end up writing a bash script to run ceedling gcov on each test file one by one so that it doesn't stop when one fails. Thank you for helping me out.

@rickymohk The simplest option I can think of for a workaround is:

Expand your :paths ↳ :test list in your project configuration to add some appropriately named support directory. This directory would not be part of the source structure you aren't able to modify.
Drop in an empty foo.h (with some comment inside explaining the issue) into that new support directory.
Modify your test to #include "foo.h" instead of foo.c.

That should work. You'd be basically conforming to the normal Ceedling convention (that the Gcov plugin in 0.31.1 is too rigidly expecting) and simply inserting a search path and header file that only exist in your test build.

@rickymohk The simplest option I can think of for a workaround is:

Expand your :paths ↳ :test list in your project configuration to add some appropriately named support directory. This directory would not be part of the source structure you aren't able to modify.
Drop in an empty foo.h (with some comment inside explaining the issue) into that new support directory.
Modify your test to #include "foo.h" instead of foo.c.

That should work. You'd be basically conforming to the normal Ceedling convention (that the Gcov plugin in 0.31.1 is too rigidly expecting) and simply inserting a search path and header file that only exist in your test build.

Thank you. This way I can test those files properly.


Upload Changes

Find a way to upload my changes to GitHub...

Hi @KatieJyemfa , anything I can help with? Are these code changes you want to upload? If so, have a look at GitHub's desktop client for pushing/pulling changes https://desktop.github.com

Hi! Thanks, I tried to push but it didn't show my changes on GitHub.

can you take a screenshot of what you did? Did you get an error? You might need to pull first if you don't have the latest


Revert "Bump just-the-docs from 0.8.2 to 0.9.0"

Reverts endoflife-date/endoflife.date#5651.
Upgrade to sass-embedded 4.26 triggers a lot of deprecation warning during site build. Ignoring this upgrade until this is completely fixed.

@endoflife-date/everyone FYI.

good to know 👍


Problem with user authorities in oauth2 client

I'm having trouble picking up the user logged authorities in ResourceServer.
User authorities in Oauth2Server
"authorities": [
{
"authority": "ROLE_TEST1"
},
{
"authority": "ROLE_TESTE2"
}
]

User authorities in ResourceServers
"authorities": [
{
"authority": "{authority=ROLE_TEST1}"
},
{
"authority": "{authority=ROLE_TESTE2}"
}
]

I am using a Spring Boot 1.3.5 version and Spring cloud Brixton.RELEASE
Dependencies in maven:
       <dependency>
            <groupId>org.springframework.cloud</groupId>
            <artifactId>spring-cloud-starter-oauth2</artifactId>
        </dependency>
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-security</artifactId>
        </dependency>
        <dependency>
            <groupId>org.springframework.security.oauth</groupId>
            <artifactId>spring-security-oauth2</artifactId>
        </dependency>

For some reason is not being done correctly serialization of SimpleGrantedAuthority.

Did u solve this?


[UTIL] Interface listing is not working on Android

The dependency nix on its version 0.8 does not compile on Android due to a bug in it. Updating it to 0.22 and making a few adjustments on the code makes the compilation ok again, but the final application does not linking due to missing getifaddrs on Android.
May I suggest we delegate listing interfaces to a third party crate? https://crates.io/crates/get_if_addrs/0.5.3
Otherwise, we have to compile the C code that implements getifaddrs:
https://github.com/maidsafe-archive/get_if_addrs/blob/master/get_if_addrs-sys/build.rs
Once the appropriate approach is decided. I will gladly open a Pull Request

Let’s use the latter approach : compile the C code that implements getifaddrs, in order to minimize the changes for other platforms.

this is still happening for me, meanwhile if-addrs works just fine:
#[cfg(target_os = "android")]
pub fn ifaces() -> Result<Vec<crate::ifaces::Interface>, std::io::Error> {
    use crate::ifaces::Kind;
    use std::net;
    fn ip_to_sa(ip: net::IpAddr) -> net::SocketAddr {
        net::SocketAddr::new(ip, 0)
    }
    Ok(if_addrs::get_if_addrs()?.into_iter().map(|iface| {
        let if_addrs::Interface { name, addr } = iface;
        let ip = addr.ip();
        crate::ifaces::Interface {
            name,
            kind: if ip.is_ipv6() {
                Kind::Ipv6
            } else {
                Kind::Ipv4
            },
            hop: None,
            addr: Some(ip_to_sa(ip)),
            mask: Some(ip_to_sa(match addr {
                if_addrs::IfAddr::V4(addr) => addr.ip.into(),
                if_addrs::IfAddr::V6(addr) => addr.ip.into(),
            })),
        }
    }).collect())
}