Unable to parse aws-exports.js. Has this file been modified

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
16.13.2
Amplify CLI Version
12.8.2
What operating system are you using?
Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
I firstly hosted my website using Amplify manually before I install the Amplify-cli on my backend using the Visual Studio terminal
Describe the bug
Initially when I run "npm run serve" on my terminal I get this warnings:
in ./src/components/AppSignin.vue?vue&type=script&lang=js
export 'default' (imported as 'Auth') was not found in '@aws-amplify/auth' (possible exports: AuthError, autoSignIn, confirmResetPassword, confirmSignIn, confirmSignUp, confirmUserAttribute, decodeJWT, deleteUser, deleteUserAttributes, fetchAuthSession, fetchDevices, fetchMFAPreference, fetchUserAttributes, forgetDevice, getCurrentUser, rememberDevice, resendSignUpCode, resetPassword, sendUserAttributeVerificationCode, setUpTOTP, signIn, signInWithRedirect, signOut, signUp, updateMFAPreference, updatePassword, updateUserAttribute, updateUserAttributes, verifyTOTPSetup)
warning  in ./src/components/AppSignup.vue?vue&type=script&lang=js
export 'Auth' (imported as 'Auth') was not found in '@aws-amplify/auth' (possible exports: AuthError, autoSignIn, confirmResetPassword, confirmSignIn, confirmSignUp, confirmUserAttribute, decodeJWT, deleteUser, deleteUserAttributes, fetchAuthSession, fetchDevices, fetchMFAPreference, fetchUserAttributes, forgetDevice, getCurrentUser, rememberDevice, resendSignUpCode, resetPassword, sendUserAttributeVerificationCode, setUpTOTP, signIn, signInWithRedirect, signOut, signUp, updateMFAPreference, updatePassword, updateUserAttribute, updateUserAttributes, verifyTOTPSetup)
App running at:

Local:   http://localhost:8080/
Network: http://<IP_ADDRESS>:8080/

Note that the development build is not optimized.
To create a production build, run npm run build.
Then I proceeded to run "amplify pull --appId d1jj85s7k5o6br --envName dev"
then I got this:
Pre-pull status:
Current Environment: dev

┌──────────┬───────────────────┬───────────┬───────────────────┐
│ Category │ Resource name     │ Operation │ Provider plugin   │
├──────────┼───────────────────┼───────────┼───────────────────┤
│ Auth     │ flickgridce0c352e │ No Change │ awscloudformation │
└──────────┴───────────────────┴───────────┴───────────────────┘
✔ Successfully pulled backend environment dev from the cloud.
✖ There was an error initializing your environment.
🛑 Unable to parse aws-exports.js. Has this file been modified?
Expected behavior
I want to authenticate users on my web application using AWS Cognito. I have created a form for Signup and Signin and would love to use the AWS Cognito to authenticate users after signing up. Authenticated users would be directed to another page in the website.
Reproduction steps
npm run serve
amplify pull --appId d1jj85s7k5o6br --envName dev

Project Identifier
Project Identifier: 1ffc49228437ff9bed7582f86c66138c
Log output

# Put your logs below this line

USER@DESKTOP-2JMHJBF MINGW64 ~/Documents/flickgrid (master)
$ git init
Reinitialized existing Git repository in C:/Users/USER/Documents/flickgrid/.git/

USER@DESKTOP-2JMHJBF MINGW64 ~/Documents/flickgrid (master)
$ git add .
warning: in the working copy of '.gitignore', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'package-lock.json', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'package.json', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'src/App.vue', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'src/main.js', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'vue.config.js', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'amplify/.config/project-config.json', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'amplify/README.md', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'amplify/backend/auth/flickgridce0c352e/cli-inputs.json', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'amplify/backend/backend-config.json', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'amplify/backend/tags.json', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'amplify/backend/types/amplify-dependent-resources-ref.d.ts', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'amplify/cli.json', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'amplify/hooks/README.md', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'amplify/team-provider-info.json', LF will be replaced by CRLF the next time Git touches it

USER@DESKTOP-2JMHJBF MINGW64 ~/Documents/flickgrid (master)
$ git commit -m "Latest Commit"
[master 1792c39] Latest Commit
 25 files changed, 6532 insertions(+), 1090 deletions(-)
 create mode 100644 amplify/.config/project-config.json
 create mode 100644 amplify/README.md
 create mode 100644 amplify/backend/auth/flickgridce0c352e/cli-inputs.json
 create mode 100644 amplify/backend/backend-config.json
 create mode 100644 amplify/backend/tags.json
 create mode 100644 amplify/backend/types/amplify-dependent-resources-ref.d.ts
 create mode 100644 amplify/cli.json
 create mode 100644 amplify/hooks/README.md
 create mode 100644 amplify/team-provider-info.json
 create mode 100644 src/components/AppMoviesLayout.vue
 create mode 100644 src/components/AppSignin.vue
 create mode 100644 src/components/AppSignup.vue
 create mode 100644 src/router/index.js

USER@DESKTOP-2JMHJBF MINGW64 ~/Documents/flickgrid (master)
$ git remote add origin https://github.com/michaelflourish/flickgrid
error: remote origin already exists.

USER@DESKTOP-2JMHJBF MINGW64 ~/Documents/flickgrid (master)
$ git remote add origin https://github.com/michaelflourish/flickgrid/
error: remote origin already exists.

USER@DESKTOP-2JMHJBF MINGW64 ~/Documents/flickgrid (master)
$ git push -u origin master
Enumerating objects: 54, done.
Counting objects: 100% (54/54), done.
Delta compression using up to 8 threads
Compressing objects: 100% (33/33), done.
Writing objects: 100% (38/38), 68.26 KiB | 1.59 MiB/s, done.
Total 38 (delta 6), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (6/6), completed with 6 local objects.
To https://github.com/michaelflourish/flickgrid
   ad575f9..1792c39  master -> master
branch 'master' set up to track 'origin/master'.

USER@DESKTOP-2JMHJBF MINGW64 ~/Documents/flickgrid (master)
$ npm run serve

><EMAIL_ADDRESS>serve
> vue-cli-service serve

 INFO  Starting development server...

 WARNING  Compiled with 3 warnings                                                                             4:50:12 PM

 warning  in ./src/components/AppSignin.vue?vue&type=script&lang=js

export 'Auth' (imported as 'Auth') was not found in '@aws-amplify/auth' (possible exports: AuthError, autoSignIn, confirmResetPassword, confirmSignIn, confirmSignUp, confirmUserAttribute, decodeJWT, deleteUser, deleteUserAttributes, fetchAuthSession, fetchDevices, fetchMFAPreference, fetchUserAttributes, forgetDevice, getCurrentUser, rememberDevice, resendSignUpCode, resetPassword, sendUserAttributeVerificationCode, setUpTOTP, signIn, signInWithRedirect, signOut, signUp, updateMFAPreference, updatePassword, updateUserAttribute, updateUserAttributes, verifyTOTPSetup)

 warning  in ./src/components/AppSignup.vue?vue&type=script&lang=js

export 'default' (imported as 'Auth') was not found in '@aws-amplify/auth' (possible exports: AuthError, autoSignIn, confirmResetPassword, confirmSignIn, confirmSignUp, confirmUserAttribute, decodeJWT, deleteUser, deleteUserAttributes, fetchAuthSession, fetchDevices, fetchMFAPreference, fetchUserAttributes, forgetDevice, getCurrentUser, rememberDevice, resendSignUpCode, resetPassword, sendUserAttributeVerificationCode, setUpTOTP, signIn, signInWithRedirect, signOut, signUp, updateMFAPreference, updatePassword, updateUserAttribute, updateUserAttributes, verifyTOTPSetup)

 warning  in ./src/main.js

export 'default' (imported as 'Amplify') was not found in 'aws-amplify' (possible exports: Amplify)

  App running at:
  - Local:   http://localhost:8081/
  - Network: http://<IP_ADDRESS>:8081/

  Note that the development build is not optimized.
  To create a production build, run npm run build.

USER@DESKTOP-2JMHJBF MINGW64 ~/Documents/flickgrid (master)
$ npm run serve

><EMAIL_ADDRESS>serve
> vue-cli-service serve

 INFO  Starting development server...

 WARNING  Compiled with 3 warnings                                                                             4:51:16 PM

 warning  in ./src/components/AppSignin.vue?vue&type=script&lang=js

export 'Auth' (imported as 'Auth') was not found in '@aws-amplify/auth' (possible exports: AuthError, autoSignIn, confirmResetPassword, confirmSignIn, confirmSignUp, confirmUserAttribute, decodeJWT, deleteUser, deleteUserAttributes, fetchAuthSession, fetchDevices, fetchMFAPreference, fetchUserAttributes, forgetDevice, getCurrentUser, rememberDevice, resendSignUpCode, resetPassword, sendUserAttributeVerificationCode, setUpTOTP, signIn, signInWithRedirect, signOut, signUp, updateMFAPreference, updatePassword, updateUserAttribute, updateUserAttributes, verifyTOTPSetup)

 warning  in ./src/components/AppSignup.vue?vue&type=script&lang=js

export 'default' (imported as 'Auth') was not found in '@aws-amplify/auth' (possible exports: AuthError, autoSignIn, confirmResetPassword, confirmSignIn, confirmSignUp, confirmUserAttribute, decodeJWT, deleteUser, deleteUserAttributes, fetchAuthSession, fetchDevices, fetchMFAPreference, fetchUserAttributes, forgetDevice, getCurrentUser, rememberDevice, resendSignUpCode, resetPassword, sendUserAttributeVerificationCode, setUpTOTP, signIn, signInWithRedirect, signOut, signUp, updateMFAPreference, updatePassword, updateUserAttribute, updateUserAttributes, verifyTOTPSetup)

 warning  in ./src/main.js

export 'default' (imported as 'Amplify') was not found in 'aws-amplify' (possible exports: Amplify)

  App running at:
  - Local:   http://localhost:8081/
  - Network: http://<IP_ADDRESS>:8081/

  Note that the development build is not optimized.
  To create a production build, run npm run build.

USER@DESKTOP-2JMHJBF MINGW64 ~/Documents/flickgrid (master)
$ npm run serve

><EMAIL_ADDRESS>serve
> vue-cli-service serve

 INFO  Starting development server...

 WARNING  Compiled with 3 warnings                                                                            10:25:38 AM

 warning  in ./src/components/AppSignin.vue?vue&type=script&lang=js

export 'Auth' (imported as 'Auth') was not found in '@aws-amplify/auth' (possible exports: AuthError, autoSignIn, confirmResetPassword, confirmSignIn, confirmSignUp, confirmUserAttribute, decodeJWT, deleteUser, deleteUserAttributes, fetchAuthSession, fetchDevices, fetchMFAPreference, fetchUserAttributes, forgetDevice, getCurrentUser, rememberDevice, resendSignUpCode, resetPassword, sendUserAttributeVerificationCode, setUpTOTP, signIn, signInWithRedirect, signOut, signUp, updateMFAPreference, updatePassword, updateUserAttribute, updateUserAttributes, verifyTOTPSetup)

 warning  in ./src/components/AppSignup.vue?vue&type=script&lang=js

export 'default' (imported as 'Auth') was not found in '@aws-amplify/auth' (possible exports: AuthError, autoSignIn, confirmResetPassword, confirmSignIn, confirmSignUp, confirmUserAttribute, decodeJWT, deleteUser, deleteUserAttributes, fetchAuthSession, fetchDevices, fetchMFAPreference, fetchUserAttributes, forgetDevice, getCurrentUser, rememberDevice, resendSignUpCode, resetPassword, sendUserAttributeVerificationCode, setUpTOTP, signIn, signInWithRedirect, signOut, signUp, updateMFAPreference, updatePassword, updateUserAttribute, updateUserAttributes, verifyTOTPSetup)

 warning  in ./src/main.js

export 'default' (imported as 'Amplify') was not found in 'aws-amplify' (possible exports: Amplify)

  App running at:
  - Local:   http://localhost:8081/
  - Network: http://<IP_ADDRESS>:8081/

  Note that the development build is not optimized.
  To create a production build, run npm run build.
  To create a production build, run npm run build.

 WAIT  Compiling...                                                                                11:09:56 AM

Compiling...

 WARNING  Compiled with 3 warnings                                                                            11:10:06 AM

 warning  in ./src/components/AppSignin.vue?vue&type=script&lang=js

export 'Auth' (imported as 'Auth') was not found in '@aws-amplify/auth' (possible exports: AuthError, autoSignIn, confirmResetPassword, confirmSignIn, confirmSignUp, confirmUserAttribute, decodeJWT, deleteUser, deleteUserAttributes, fetchAuthSession, fetchDevices, fetchMFAPreference, fetchUserAttributes, forgetDevice, getCurrentUser, rememberDevice, resendSignUpCode, resetPassword, sendUserAttributeVerificationCode, setUpTOTP, signIn, signInWithRedirect, signOut, signUp, updateMFAPreference, updatePassword, updateUserAttribute, updateUserAttributes, verifyTOTPSetup)

 warning  in ./src/components/AppSignup.vue?vue&type=script&lang=js

export 'default' (imported as 'Auth') was not found in '@aws-amplify/auth' (possible exports: AuthError, autoSignIn, confirmResetPassword, confirmSignIn, confirmSignUp, confirmUserAttribute, decodeJWT, deleteUser, deleteUserAttributes, fetchAuthSession, fetchDevices, fetchMFAPreference, fetchUserAttributes, forgetDevice, getCurrentUser, rememberDevice, resendSignUpCode, resetPassword, sendUserAttributeVerificationCode, setUpTOTP, signIn, signInWithRedirect, signOut, signUp, updateMFAPreference, updatePassword, updateUserAttribute, updateUserAttributes, verifyTOTPSetup)

 warning  in ./src/main.js

export 'default' (imported as 'Amplify') was not found in 'aws-amplify' (possible exports: Amplify)

  App running at:
  - Local:   http://localhost:8081/
  - Network: http://<IP_ADDRESS>:8081/

USER@DESKTOP-2JMHJBF MINGW64 ~/Documents/flickgrid (master)
$ npm run serve

><EMAIL_ADDRESS>serve
> vue-cli-service serve

 INFO  Starting development server...

 WARNING  Compiled with 1 warning                                                                                12:17:55 PM

 warning  in ./src/components/AppSignin.vue?vue&type=script&lang=js

export 'default' (imported as 'Auth') was not found in '@aws-amplify/auth' (possible exports: AuthError, autoSignIn, confirmResetPassword, confirmSignIn, confirmSignUp, confirmUserAttribute, decodeJWT, deleteUser, deleteUserAttributes, fetchAuthSession, fetchDevices, fetchMFAPreference, fetchUserAttributes, forgetDevice, getCurrentUser, rememberDevice, resendSignUpCode, resetPassword, sendUserAttributeVerificationCode, setUpTOTP, signIn, signInWithRedirect, signOut, signUp, updateMFAPreference, updatePassword, updateUserAttribute, updateUserAttributes, verifyTOTPSetup)

  App running at:
  - Local:   http://localhost:8080/
  - Network: http://<IP_ADDRESS>:8080/

  Note that the development build is not optimized.
  To create a production build, run npm run build.

 WAIT  Compiling...                                                                                12:21:58 PM

Compiling...

 WARNING  Compiled with 2 warnings                                                                               12:22:00 PM

 warning  in ./src/components/AppSignin.vue?vue&type=script&lang=js

export 'default' (imported as 'Auth') was not found in '@aws-amplify/auth' (possible exports: AuthError, autoSignIn, confirmResetPassword, confirmSignIn, confirmSignUp, confirmUserAttribute, decodeJWT, deleteUser, deleteUserAttributes, fetchAuthSession, fetchDevices, fetchMFAPreference, fetchUserAttributes, forgetDevice, getCurrentUser, rememberDevice, resendSignUpCode, resetPassword, sendUserAttributeVerificationCode, setUpTOTP, signIn, signInWithRedirect, signOut, signUp, updateMFAPreference, updatePassword, updateUserAttribute, updateUserAttributes, verifyTOTPSetup)

 warning  in ./src/components/AppSignup.vue?vue&type=script&lang=js

export 'Auth' (imported as 'Auth') was not found in '@aws-amplify/auth' (possible exports: AuthError, autoSignIn, confirmResetPassword, confirmSignIn, confirmSignUp, confirmUserAttribute, decodeJWT, deleteUser, deleteUserAttributes, fetchAuthSession, fetchDevices, fetchMFAPreference, fetchUserAttributes, forgetDevice, getCurrentUser, rememberDevice, resendSignUpCode, resetPassword, sendUserAttributeVerificationCode, setUpTOTP, signIn, signInWithRedirect, signOut, signUp, updateMFAPreference, updatePassword, updateUserAttribute, updateUserAttributes, verifyTOTPSetup)

  App running at:
  - Local:   http://localhost:8080/
  - Network: http://<IP_ADDRESS>:8080/

USER@DESKTOP-2JMHJBF MINGW64 ~/Documents/flickgrid (master)
$ amplify pull --appId d1jj85s7k5o6br --envName dev

Pre-pull status:

    Current Environment: dev

┌──────────┬───────────────────┬───────────┬───────────────────┐
│ Category │ Resource name     │ Operation │ Provider plugin   │
├──────────┼───────────────────┼───────────┼───────────────────┤
│ Auth     │ flickgridce0c352e │ No Change │ awscloudformation │
└──────────┴───────────────────┴───────────┴───────────────────┘

✔ Successfully pulled backend environment dev from the cloud.
✖ There was an error initializing your environment.
🛑 Unable to parse aws-exports.js. Has this file been modified?

Resolution: Please report this issue at https://github.com/aws-amplify/amplify-cli/issues and include the project identifier from: 'amplify diagnose --send-report'
Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

Session Identifier: 748eb2b6-6431-4ce8-b110-2600c40a8149

USER@DESKTOP-2JMHJBF MINGW64 ~/Documents/flickgrid (master)
$ amplify pull

Pre-pull status:

    Current Environment: dev

┌──────────┬───────────────────┬───────────┬───────────────────┐
│ Category │ Resource name     │ Operation │ Provider plugin   │
├──────────┼───────────────────┼───────────┼───────────────────┤
│ Auth     │ flickgridce0c352e │ No Change │ awscloudformation │
└──────────┴───────────────────┴───────────┴───────────────────┘

✔ Successfully pulled backend environment dev from the cloud.
✖ There was an error initializing your environment.
🛑 Unable to parse aws-exports.js. Has this file been modified?

Resolution: Please report this issue at https://github.com/aws-amplify/amplify-cli/issues and include the project identifier from: 'amplify diagnose --send-report'
Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

Session Identifier: ea773c86-46ae-474f-bab1-b691d0c2793d

USER@DESKTOP-2JMHJBF MINGW64 ~/Documents/flickgrid (master)
$ amplify diagnose --send-report

Learn more at https://docs.amplify.aws/cli/reference/diagnose/

✅ Report saved: C:\Users\USER\AppData\Local\Temp\flickgrid\report-1701539405681.zip

✔ Done

Project Identifier: 1ffc49228437ff9bed7582f86c66138c

USER@DESKTOP-2JMHJBF MINGW64 ~/Documents/flickgrid (master)
$ npm --version
8.1.2

USER@DESKTOP-2JMHJBF MINGW64 ~/Documents/flickgrid (master)
$ amplify --version
12.8.2

USER@DESKTOP-2JMHJBF MINGW64 ~/Documents/flickgrid (master)
$ amplifycli --version
bash: amplifycli: command not found

USER@DESKTOP-2JMHJBF MINGW64 ~/Documents/flickgrid (master)
$ node -v
v16.13.2

USER@DESKTOP-2JMHJBF MINGW64 ~/Documents/flickgrid (master)
 WARNING  Compiled with 2 warnings                                                                                1:04:40 PM

 warning  in ./src/components/AppSignin.vue?vue&type=script&lang=js

export 'default' (imported as 'Auth') was not found in '@aws-amplify/auth' (possible exports: AuthError, autoSignIn, confirmResetPassword, confirmSignIn, confirmSignUp, confirmUserAttribute, decodeJWT, deleteUser, deleteUserAttributes, fetchAuthSession, fetchDevices, fetchMFAPreference, fetchUserAttributes, forgetDevice, getCurrentUser, rememberDevice, resendSignUpCode, resetPassword, sendUserAttributeVerificationCode, setUpTOTP, signIn, signInWithRedirect, signOut, signUp, updateMFAPreference, updatePassword, updateUserAttribute, updateUserAttributes, verifyTOTPSetup)

 warning  in ./src/components/AppSignup.vue?vue&type=script&lang=js

export 'Auth' (imported as 'Auth') was not found in '@aws-amplify/auth' (possible exports: AuthError, autoSignIn, confirmResetPassword, confirmSignIn, confirmSignUp, confirmUserAttribute, decodeJWT, deleteUser, deleteUserAttributes, fetchAuthSession, fetchDevices, fetchMFAPreference, fetchUserAttributes, forgetDevice, getCurrentUser, rememberDevice, resendSignUpCode, resetPassword, sendUserAttributeVerificationCode, setUpTOTP, signIn, signInWithRedirect, signOut, signUp, updateMFAPreference, updatePassword, updateUserAttribute, updateUserAttributes, verifyTOTPSetup)

  App running at:
  - Local:   http://localhost:8080/
  - Network: http://<IP_ADDRESS>:8080/

  Note that the development build is not optimized.
  To create a production build, run npm run build.

USER@DESKTOP-2JMHJBF MINGW64 ~/Documents/flickgrid (master)
$ npm run serve

><EMAIL_ADDRESS>serve
> vue-cli-service serve

 INFO  Starting development server...

 WARNING  Compiled with 2 warnings                                                                                1:17:50 PM

 warning  in ./src/components/AppSignin.vue?vue&type=script&lang=js

export 'default' (imported as 'Auth') was not found in '@aws-amplify/auth' (possible exports: AuthError, autoSignIn, confirmResetPassword, confirmSignIn, confirmSignUp, confirmUserAttribute, decodeJWT, deleteUser, deleteUserAttributes, fetchAuthSession, fetchDevices, fetchMFAPreference, fetchUserAttributes, forgetDevice, getCurrentUser, rememberDevice, resendSignUpCode, resetPassword, sendUserAttributeVerificationCode, setUpTOTP, signIn, signInWithRedirect, signOut, signUp, updateMFAPreference, updatePassword, updateUserAttribute, updateUserAttributes, verifyTOTPSetup)

 warning  in ./src/components/AppSignup.vue?vue&type=script&lang=js

export 'Auth' (imported as 'Auth') was not found in '@aws-amplify/auth' (possible exports: AuthError, autoSignIn, confirmResetPassword, confirmSignIn, confirmSignUp, confirmUserAttribute, decodeJWT, deleteUser, deleteUserAttributes, fetchAuthSession, fetchDevices, fetchMFAPreference, fetchUserAttributes, forgetDevice, getCurrentUser, rememberDevice, resendSignUpCode, resetPassword, sendUserAttributeVerificationCode, setUpTOTP, signIn, signInWithRedirect, signOut, signUp, updateMFAPreference, updatePassword, updateUserAttribute, updateUserAttributes, verifyTOTPSetup)

  App running at:
  - Local:   http://localhost:8080/
  - Network: http://<IP_ADDRESS>:8080/

  Note that the development build is not optimized.
  To create a production build, run npm run build.

USER@DESKTOP-2JMHJBF MINGW64 ~/Documents/flickgrid (master)
$ amplify diagnose --send-report

Learn more at https://docs.amplify.aws/cli/reference/diagnose/

✅ Report saved: C:\Users\USER\AppData\Local\Temp\flickgrid\report-1701541168478.zip

✔ Done

Project Identifier: 1ffc49228437ff9bed7582f86c66138c

USER@DESKTOP-2JMHJBF MINGW64 ~/Documents/flickgrid (master)

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hey @michaelflourish, thank you for reaching out. Could you remove the local aws-exports.js then re-run the pull commands with --debug and provide us the output.

Closing due to inactivity


Move period inside ending quotations in hanging-your-two-factor-authentication-method#adding-a-totp-app

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-your-two-factor-authentication-method#adding-a-totp-app
What part(s) of the article would you like to see updated?

On GitHub, type the code into the field under "Verify the code from the app".

Move period inside ending quotations to align with our style guide
Additional information
No response

I would like to take this issue and put up the PR.

@prashant3286 Hello! 👋 Thank you for interest in contributing to GitHub Docs! While we don't generally assign issues to contributors, if you find an issue to work on, you are welcome to open a PR with a fix.
With that said, it looks like @iamAyushChamoli has already reviewed submitted a PR for this issue! Feel free to search for other issues labeled good first issue or help wanted to see what's available to work on 💛


oh no, behavior inappropriate

Subject: oh no, behavior inappropriate
Description:
I let my review sit a day in an open tab and once i submitted it, the status had changed to "behavior inappropriate". please fix this ASAP! I'm so embarrassed
Results:
Travis was def NOT inappropriate. he was amazing! please correct this!
Backend version: develop-ea44d455
Frontend version: develop-ea44d455
User Agent: Mozilla/5.0 (X11; CrOS x86_64 14268.67.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.111 Safari/537.36
Page: https://app.couchers.org/
User: jlam (8216)

Forwarded to support


Netlify deployment problem when Nextjs 12.2.3 is used

there is a problem with the deployment using Netlify and Next 12.2.3. It works ok with 12.2.2
works well locally with nextjs 12.2.3

Elven Tools Dapp works with Next 12.2.4. Worth checking here...

Confirmed, works well with 12.2.4


Cleanup dependencies

I noticed there were more dependencies than needed being installed. This resolves this so that only the required dependencies will be installed.

Thanks, I must be forgotten -D when installing those packages :facepalm:.


Can not execute the operation on ended Span / tls.connect .. You can only call end() on a span once.

What happened?
Steps to Reproduce
Run a private repo using nodemon
Expected Result

Actual Result
logs
Additional Details
Seems related to:

the https://github.com/open-telemetry/opentelemetry-js/issues/2575 issue - but 0.41.0 is not fixing it 😕
the https://github.com/open-telemetry/opentelemetry-js/issues/908
the https://github.com/open-telemetry/opentelemetry-js-contrib/issues/107

OpenTelemetry Setup Code
/* eslint-disable no-console -- this file cannot use the proper logger
 */

import { createAzureSdkInstrumentation } from '@azure/opentelemetry-instrumentation-azure-sdk'
import { OTLPTraceExporter } from '@opentelemetry/exporter-trace-otlp-proto'
import { registerInstrumentations } from '@opentelemetry/instrumentation'
import { DnsInstrumentation } from '@opentelemetry/instrumentation-dns'
import { ExpressInstrumentation } from '@opentelemetry/instrumentation-express'
import { HttpInstrumentation } from '@opentelemetry/instrumentation-http'
import { NetInstrumentation } from '@opentelemetry/instrumentation-net'
import { WinstonInstrumentation } from '@opentelemetry/instrumentation-winston'
import { Resource } from '@opentelemetry/resources'
import {
  BatchSpanProcessor,
  NoopSpanProcessor,
} from '@opentelemetry/sdk-trace-base'
import { NodeTracerProvider } from '@opentelemetry/sdk-trace-node'
import { SemanticResourceAttributes } from '@opentelemetry/semantic-conventions'
import { getCurrentLoggerMetadata } from './common/logger-metadata-context'
import { getVersionString } from './common/version-string'
import type { SpanExporter, SpanProcessor } from '@opentelemetry/sdk-trace-base'

/*
 * This file is responsible for initializing OpenTelemetry. It is preloaded by
 * Node.js, so it can be used to initialize OpenTelemetry before any other code
 * is executed.
 *
 * It's important that this file does not import any other non-essential modules,
 * because those modules may be instrumented by OpenTelemetry and importing them
 * here would break the instrumentation.
 */

main()

function main() {
  const resource = createResource()

  const provider = new NodeTracerProvider({
    resource,
  })

  const exporter = createExporter()

  const spanProcessor = createSpanProcessor(exporter)

  provider.addSpanProcessor(spanProcessor)
  provider.register()

  registerInstrumentations({
    instrumentations: [
      new HttpInstrumentation({
        ignoreIncomingPaths: ['/health'],
      }),
      new WinstonInstrumentation({
        logHook: (_, record) => {
          const currentLoggerMetadata = getCurrentLoggerMetadata()
          if (currentLoggerMetadata !== undefined) {
            Object.assign(record, currentLoggerMetadata)
          }
        },
      }),
      new ExpressInstrumentation(),
      new DnsInstrumentation(),
      new NetInstrumentation(),
      createAzureSdkInstrumentation(),
    ],
    tracerProvider: provider,
  })

  const exitHandler = () => {
    console.log('Shutting down OpenTelemetry...')
    // Schedule the shutdown to happen after the current event loop iteration
    // completes. This is necessary because we want to give the exporter a
    // chance to send any remaining spans.
    provider
      .shutdown()
      .then(() => console.log('OpenTelemetry shutdown complete'))
      .catch((ex) => console.error('OpenTelemetry shutdown failed', ex))
  }

  process.on('SIGINT', exitHandler)
  process.on('SIGTERM', exitHandler)
}

function createResource(): Resource {
  const serviceName = process.env['NAME_SERVICE']
  const envName = process.env['ENVIRONMENT_NAME']

  return Resource.default().merge(
    new Resource({
      [SemanticResourceAttributes.SERVICE_NAME]: serviceName,
      service_name: serviceName,
      [SemanticResourceAttributes.SERVICE_NAMESPACE]: 'Namespace name',
      [SemanticResourceAttributes.SERVICE_VERSION]: getVersionString(),
      [SemanticResourceAttributes.DEPLOYMENT_ENVIRONMENT]: envName,
    }),
  )
}

function createExporter() {
  const exporterNameEnvVar = 'OTEL_TRACES_EXPORTER'
  const exporterName = process.env[exporterNameEnvVar]
  const isProduction = process.env['NODE_ENV'] === 'production'

  switch (exporterName) {
    case undefined:
    case '':
      if (isProduction) {
        console.error(
          'Opentelemetry span exporting has not been configured, and defaulted to off. This is probably a mistake in production.',
        )
      }
      return undefined
    case 'none':
      if (isProduction) {
        console.warn(
          'Opentelemetry span exporting has been explicitly disabled. This is probably a mistake in production.',
        )
      }
      return undefined
    case 'otlp':
      return new OTLPTraceExporter()
    default:
      throw new Error(
        `Unknown value received for the environment variable '${exporterNameEnvVar}'`,
      )
  }
}

function createSpanProcessor(
  exporter: SpanExporter | undefined,
): SpanProcessor {
  return exporter === undefined
    ? new NoopSpanProcessor()
    : new BatchSpanProcessor(exporter)
}

/* eslint-enable no-console */

package.json
"dependencies": {
    "@azure/opentelemetry-instrumentation-azure-sdk": "^1.0.0-beta.2",
    "@opentelemetry/api": "^1.3.0",
    "@opentelemetry/exporter-trace-otlp-proto": "^0.38.0",
    "@opentelemetry/instrumentation": "^0.38.0",
    "@opentelemetry/instrumentation-dns": "^0.31.0",
    "@opentelemetry/instrumentation-express": "^0.32.0",
    "@opentelemetry/instrumentation-http": "^0.41.0",
    "@opentelemetry/instrumentation-net": "^0.31.0",
    "@opentelemetry/instrumentation-winston": "^0.31.0",
    "@opentelemetry/resources": "^1.8.0",
    "@opentelemetry/sdk-trace-base": "^1.8.0",
    "@opentelemetry/sdk-trace-node": "^1.8.0",
    "@opentelemetry/semantic-conventions": "^1.8.0",
...
    "express": "^4.18.2",
    "express-basic-auth": "^1.2.1",
    "express-jwt": "^8.4.1",

Relevant log output
[WebServer] {
  "level": "warn",
  "message": "Can not execute the operation on ended Span {traceId: b77b886664c95c5e7e937f5a6200fcf0, spanId: 6a4d3ced1105c832}",
  "span_id": "78d5aca7fc8ac3c2",
  "timestamp": "2023-07-17T07:27:02.300Z",
  "trace_flags": "01",
  "trace_id": "b77b886664c95c5e7e937f5a6200fcf0"
}
{
  "level": "warn",
  "message": "Can not execute the operation on ended Span {traceId: b77b886664c95c5e7e937f5a6200fcf0, spanId: 6a4d3ced1105c832}",
  "span_id": "78d5aca7fc8ac3c2",
  "timestamp": "2023-07-17T07:27:02.301Z",
  "trace_flags": "01",
  "trace_id": "b77b886664c95c5e7e937f5a6200fcf0"
}
[WebServer] {
  "level": "error",
  "message": "tls.connect b77b886664c95c5e7e937f5a6200fcf0-6a4d3ced1105c832 - You can only call end() on a span once.",
  "span_id": "78d5aca7fc8ac3c2",
  "timestamp": "2023-07-17T07:27:02.301Z",
  "trace_flags": "01",
  "trace_id": "b77b886664c95c5e7e937f5a6200fcf0"
}

They are most definitely unexpected. And very predictable - "just start and wait 2 minutes" (or so)

We are seeing the same issue when using @opentelemetry/instrumentation-net

@stdedos What version of Node.js are you running?
We are seeing this on Node.js 20 similarly with express and some auto-instrumentation

Answering for my teammate @stdedos, we are seeing this on node 18

@googol Ok so I guess it's not neccessarily node version related.
Doing a little digging i found a change in @opentelemetry/instrumentation-net that could be related - this commit: https://github.com/open-telemetry/opentelemetry-js-contrib/commit/1ee197ed74e44054b092d0adcdac7f9db1a42737
This has landed in 0.31.1 of @opentelemetry/instrumentation-net
Maybe if you have time you can try and install exactly<EMAIL_ADDRESS>to see if this was a regression?

No luck:
u@h:prj$ npm i<EMAIL_ADDRESS>
added 1 package, changed 2 packages, and audited 1113 packages in 15s
u@h:prj$ (test/rpa/create-employee *+|u+8) npm run dev

><EMAIL_ADDRESS>dev
> nodemon

[nodemon] 2.0.22
[nodemon] to restart at any time, enter `rs`
[nodemon] watching path(s): src/**/*
[nodemon] watching extensions: ts
[nodemon] starting `ts-node -r ./src/initialize-telemetry.ts --transpile-only ./src/index.ts`
...
{
  "level": "info",
  "message": "Server listening for connections on <IP_ADDRESS>:4900",
  "timestamp": "2023-08-09T15:02:46.259Z"
}
{
  "level": "warn",
  "message": "Can not execute the operation on ended Span {traceId: b67fc07d0cf9496fe8dad2a49c0dc4f0, spanId: cac5b97cca3baf39}",
  "span_id": "8581abcc0d119d2f",
  "timestamp": "2023-08-09T15:05:50.430Z",
  "trace_flags": "01",
  "trace_id": "b67fc07d0cf9496fe8dad2a49c0dc4f0"
}
{
  "level": "warn",
  "message": "Can not execute the operation on ended Span {traceId: b67fc07d0cf9496fe8dad2a49c0dc4f0, spanId: cac5b97cca3baf39}",
  "span_id": "8581abcc0d119d2f",
  "timestamp": "2023-08-09T15:05:50.430Z",
  "trace_flags": "01",
  "trace_id": "b67fc07d0cf9496fe8dad2a49c0dc4f0"
}
{
  "level": "error",
  "message": "tls.connect b67fc07d0cf9496fe8dad2a49c0dc4f0-cac5b97cca3baf39 - You can only call end() on a span once.",
  "span_id": "8581abcc0d119d2f",
  "timestamp": "2023-08-09T15:05:50.431Z",
  "trace_flags": "01",
  "trace_id": "b67fc07d0cf9496fe8dad2a49c0dc4f0"
}

Hello everyone! Any progress? 🙃

@stdedos Do you have an example of such a span? Would be interesting to see whether it had any relevant attributes (e.g. errors).

@seemk, unfortunately, I cannot provide a direct example of such a span due to the private nature of the project.
I also don't have any data (that I am aware of), apart from what is already on my comment and in the warning logs.
Doesn't my example replicate locally?

We are also seeing them on every 400 request to our API

I haven't managed to reproduce it yet, but my hunch is that a TLS socket error is emitted after a successful tls.connect.

Server is express (as visible in package.json above)
Client is axios
    "axios": "^1.4.0",

It seems that
import { NetInstrumentation } from '@opentelemetry/instrumentation-net'

Is the culprit in our situation.

Registered via:
function main() {
  const resource = createResource()

  const provider = new NodeTracerProvider({
    resource,
  })

  const exporter = createExporter()

  const spanProcessor = createSpanProcessor(exporter)

  provider.addSpanProcessor(spanProcessor)
  provider.register()

  registerInstrumentations({
    instrumentations: [
      // new ...({
      //   ...
      // }),
      // new ...({
      //   ...
      // }),
      // new ...(),
      // new ...(),
      new NetInstrumentation(),
      // ...(),
    ],
    tracerProvider: provider,
  })

  const exitHandler = () => {
    console.log('Shutting down OpenTelemetry...')
    // Schedule the shutdown to happen after the current event loop iteration
    // completes. This is necessary because we want to give the exporter a
    // chance to send any remaining spans.
    provider
      .shutdown()
      .then(() => console.log('OpenTelemetry shutdown complete'))
      .catch((ex) => console.error('OpenTelemetry shutdown failed', ex))
  }

  process.on('SIGINT', exitHandler)
  process.on('SIGTERM', exitHandler)
}


Take a look at stuff on Awesome Serverless

https://github.com/anaibol/awesome-serverless

@aharris88 maybe label this "hacktoberfest", it might get some extra attention ;)

If someone can take a look at the awesome-serverless list and see if there is anything that should be added to this, that would be awesome.


Update documentation and Ansible script to reflect required env vars

Seeding the DB doesn't work (or provisioning with Ansible, for that matter, which depends on seeding the DB as part of its provisioning flow) without setting environment variables for GitHub first, so this should probably be pointed out in the docs. This relates to #1592.
I'd love to do this myself, but I don't know what it's looking for! A bit further down, we mention GITHUB_KEY and GITHUB_SECRET, but I can't figure out where to generate these.

[ ] Update documentation, including link to GitHub docs showing how to create the right keys
[ ] Update Ansible script to require these variables at provision time

@adamyeats I would like to work on this issue :)
Please assign it to me

@alienishi please open a pull request, I can't assign it to you as you are not a member of the org

Is this still active?
Please where exactly do you store your documentation on your dbs in particular.
Browsing through the code, I'm a little confused where they are @andrew


Building mbedtls 2.2.0 on RHEL 5 leads to "No rule to make target library/libmbedtls.so', needed by tests/test_suite_aes.cbc.c'"

Trying to build mbedtls 2.2.0 on RHEL 5 leads to the failure:
make[2]: *** No rule to make target `library/libmbedtls.so', needed by `tests/test_suite_aes.cbc.c'. Stop.

Running
sed -e 's/libmbedtls.so$/libmbedtls.so.2.2.0/' -i tests/CMakeFiles/test_suite_*.dir/build.make

after "cmake" and before "make" works around the issue. Interestingly, this only affects RHEL 5, not RHEL 6 or 7, thus this must be related to cmake somehow.

ARM Internal Ref: IOTSSL-596

To be honest, I looks more like a CMake issue than an mbed TLS issue, if it works with RHEL 6 and 7 but not 5. Did you try asking CMake folks what they think about it?
Also, though I realize this might not be very satisfactory, if CMake is not working for you, we have good old Makefiles too.

It could be that RHEL 5 has a very old version of CMake. You could try installing a recent CMake version, just to see if the problem then goes away.
Here, we use CMake on a variety of very old Unix and Linux platforms, and we actually installed the latest CMake from the source distribution when we moved from autoconf, since we couldn't find packages for all our build machines.

RHEL 5 has cmake in Version 2.6.4 – which we can't upgrade in EPEL, because it is a RHEL package. Do you see chances to get the CMakefiles adapted accordingly so that they support this cmake version (like mbedtls 1.3.x did)?

I'm certainly not opposed in principle to supporting older CMake versions if we can, but right now it isn't obvious to me what we changed between 1.3 and now that broke the CMake build with old versions. If you can help us pinpoint what the culprit is, I'll be able to give you a better answer as to whether we can adapt our CMakelists.txt to solve your issue. If you're able to git-bisect the issue and point us to the commit that introduces it, that would probably be a good starting point.

The problem is caused by your "make apidoc" target. Running "make -j4 all" seems to create the symlink, however "make apidoc" removes the symlink.

I read your patch and commit message, and while I agree that using cp -p in this case is desirable, I still think that:

it should work without -p if you do make -j4 all && make apidoc instead of make -j4 all apidoc
and you shouldn't do make -j4 all apidoc anyway because it's racy and you risk building the library with the wrong config.h modified by apidoc depending on the order things are built.

Anyway, I'm considering reverting the change to the apidoc target, because it's quite counter-intuitive and error-prone that make -j4 all apidoc is now racy.

When I apply my -p patch from #392 on RHEL 5, make -j4 all apidoc fails like #390 is doing on RHEL 7 and 6. However, #392 together with make -j4 all && make apidoc works fine on RHEL 7, 6 and 5 for me.
Given I understand that make -j4 all apidoc is racy, I had a discussion with @mortenstevens already about maybe using make -j4 all && make apidoc for Fedora and RHEL (which makes our *.spec file hopefully more readable again).

Does make -j4 all && make apidoc also work without #392? I think it should work (expect that if you run make all again after that it will re-build instead of outputing "nothing to do" as expected, which I agree is bad). I'm asking because if it fails, that means there is another issue I didn't understand yet, and I'd rather understand everything that's going on, in order to avoid making similar mistakes in the future.
Again, sorry for breaking your build script, especially on a patch release, that was definitely not the intention.

No. make -j4 all works as it should, however make apidoc kills the symlinks for library/libmbed*.so and this causes at latest a failure at make install then (already make apidoc fails if you drop the sed command from my initial posting).
This is because the header file timestamp changed, thus it needs to rebuild the library. As part of that, the symlinks library/libmbed*.so are partially removed and not created again. So the -p is essential for RHEL 5.

I'll see if I can reproduce the issue with cmake 2.8.9 (the oldest version I can easily access). I'm reverting the change anyway, but I'd really like to understand everything that's going on here.


feat: added footer

@Anuragwagh Let me know if you are facing any issue while making requested changes.

I'm not sure what exactly has to do with package json file it will great if you provide guidance


Issues with installation

The installation of atomistics package in a clean env caused the following issues:

phonopy is not automatically installed
structuretoolkit is not installed; and try except block prevents error from being captured

Yes, both are optional dependencies of the atomistics package:
https://github.com/pyiron/atomistics/blob/main/pyproject.toml#L41
I guess we should update the error message to advise users to install the optional dependencies. @srmnitc Can you open a pull request?


QMAPS-1715 hide top-bar shadows when the current panel is maximized and not held

Description

hide top-bar shadows when the current panel is maximized and not held
show the shadow again as soon as the panel is being dragged down or clicked to return to default size

Why
to make the top-bar and panel's header merge seamlessly
Screenshots

@bbecquet I resolved this by adding a class to top-bar. I hope it's clean enough, as I didn't find any cleaner way to achieve this effect.

@xem see mainly my big comment about where this should be moved to.
We also need to address the problem of the white to grey separation. I propose we move forward and change the style of mobile list panels here, as it's straightforward enough. Here is an example with the category panel. We need to confirm it though and check that the two other grey panels (Route result and Favorites) are ok.

Currently
Proposed


DSL can't select from second dropdown

I have this ERB snippet
2: <%= f.select :school_level, "<option>p1</option><option>p2</option>".html_safe %>
3: <%= f.label :school_year %>
4: <%= f.select :school_year, "<option>2010</option><option>2011</option>".html_safe %>

And Cucumber snipper
6: select '2011', :from => :school_year

Cucumber always shows error
```cannot select option, no option with text '2011' in select box 'school_year' (Capybara::ElementNotFound) (eval):2:in `select'
But if I comment out line 1,2,5, the test is pass.

Any suggestions on this?

I'm gonna bet two cows on the fact that this is a problem with your app code. Please investigate further ;)

Thanks for you response. I'm also try to investigate. I have more information I forgot to tell you.
If I modify line 2 to be like this
<%= f.select :school_level, "<option>p1</option><option>p2</option><option>2011</option>".html_safe %>

The test also pass.

Try using Strings instead of Symbols in select, Capybara doesn't officially support using Symbols there, so that could cause problems.

You probably right. I change to Strings and it works.
Previously I use Symbols instead of Strings because form_for will modify Strings and Symbols also work for other type of inputs.
However, I solve problem by using label's text instead.
Thank you very much.


fixed typos and missing information

Module: 00
Lab/Demo: Lab 1
Fixes # .
Changes proposed in this pull request:

There is some missing information in the lab. It doesn't mention what service (HTTP) to configure, when adding an inbound security rule to WS-VM1
Various typo's are fixed

pull request fixes #1

reviewed, thanks for the corrections.

Thanks for the corrections.


Convert fix

related to #22

@triniwiz i just added the  because value is supposed to already be a integer


spring cloud config monitor don't refresh when using profile

I'm using spring cloud version 2021.0.1 and I set a gitlab webhook to trigger the refresh of application configs with spring cloud config monitor.
(The application has enabled the profile dev)
And I found that when I edited the config file in git like foo.yml , the monitor triggered a refresh of application foo, but when I edited the file foo-dev.yml, the refresh didn't happen.
I traced to find the config server do sent a RefreshRemoteApplicationEvent to spring cloud bus but with destination foo:dev. And I checked the doc of spring cloud bus, it says:

The default value of the ID is constructed in the form of app:index:id, where:
app is the vcap.application.name, if it exists, or spring.application.name
index is the vcap.application.instance_index, if it exists, spring.application.index, local.server.port, server.port, or 0 (in that order).
id is the vcap.application.instance_id, if it exists, or a random value.

so the correct destination should be foo:8080 or just foo, the profile name should not appear in the destination address.

Why would an instance without that profile enabled be interested in a chance in that configuration file?

The instance have enabled the profile "dev", and it refreshes when "foo.yml" changes but not on "foo-dev.yml".

So if you have two instances of foo running, one has the dev profile enabled and you edit foo.yaml does both instances get notifications?
And if you edit foo-dev.yaml will neither app instance receive a notification or will only the app without the dev profile enabled receive a notification?

If I edit foo.yaml both instances get notifications.
And if I edit foo-dev.yaml then neither app instance receive a notification.

I think this is the same issue as https://github.com/spring-cloud/spring-cloud-config/issues/1884, would you agree?

Yes, I think they are the same. And I have made a PR #2139 try to fix this.


How I can run this plugin in Grails 2.3.11?

How I can run this plugin in Grails 2.3.11?

Please use version 2.2.3 for Grails 2.3.x and earlier, it should be functionally equivalent for the time being. Unfortunately, Grails 2.4 had some breaking changes to the test architecture and it made sense to modify build test data to fit the new architecture.
I believe we need to update the documentation to indicate the compatibility changes. Thanks for the reminder.

Updated the documentation to be more clear about required versions


Switch ReSpeaker driver to use Pulseaudio instead.

Information
ReSpeaker now does allow to use pulseaudio;
https://github.com/respeaker/seeed-voicecard/tree/master/pulseaudio
Thiss would be the preferred method in combination with udev.
So this relates to #14  and #15

Initial steps are done, last piece of configuring default.pa and daemon.conf to figure out.

Testing with 46d6ec7e9cc89b52b7d64472887fdbb4a5b5d3ba

Works as expected. Mycroft config, switched back to default settings for sound using pulseaudio.


Migrate the various installers to dialog

(For interactive and easier installation)
I should also maintain a way to install without the interaction for easier automation.

Added in https://github.com/gstavrinos/ros-ez/pull/40/commits/13a030b9b52fdf756fe28a4a0efe767ec18397c4


Test on 'iojs' and '0.12'

+1

The current one is wrong. 0.10 means your testing on 0.1. You need to quote it to test on '0.10'.

sorry I didn't see this one, can you please rebase?

@shinnn feel free to merge this yourself as well :smile:

rebased

I prefer node rather than 0.12.
http://docs.travis-ci.com/user/languages/javascript-with-nodejs/#Choosing-Node-versions-to-test-against

Specifying node or stable will run using the latest stable Node.js release

better?

Single quotes, please.

done. i was trying to do minimum changes :)

Ah, sorry I didn't check the existing style. Merging this anyway.

@stevemao Thanks!

Thanks. Can you make a release?

I'm considering whether 0.2.0 or 1.0.0.
I'd like to hear your opinion, @grncdr.

I think 1.0.0 should be fine :)

If there's no API change, I'd say let's do 0.1.9 and 1.0.0. 0.1.9 so that users of semver ranges get it, and 1.0.0 because this module is actually pretty stable and in wide use.

@grncdr because it switches from stream2 to 3 so you should at least do a minor release :)

Also we added isEmpty (will probably be replaced #21) so there is an enhancement.

@grncdr because it switches from stream2 to 3 so you should at least do a minor release :)

I definitely don't see the point in doing a 0.2.0. There's no need to bump minor for an enhancement pre 1.0.0. If the switch to streams3 changes the behaviour in a way that can be observed by users then 1.0.0 makes the most sense to me.


[FLINK-10800][network][test] Abstract StreamPartitionerTest for common codes

What is the purpose of the change
There are many duplicated codes in current ForwardPartitionerTest, RescalePartitionerTest, RebalancePartitionerTest, RebalancePartitionerTest, etc. StreamPartitionerTest is defined for abstracting the common codes.
Brief change log

Define StreamPartitionerTest for abstracting common codes.
Modify current specific implementation tests based on StreamPartitionerTest

Verifying this change
This change is already covered by existing tests.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

@pnowojski , this is the preparation for FLINK-10790. :)

@pnowojski , thanks for the quick reviews!
I already updated the codes addressing the above comments.

Thanks, LGTM and merged :)


Speed up parallel reading/writing. Synchronize read/write operations per key.

Originally discovered in #65

Duplicate, closed.


imp(hmsl): #EXPL-150 more cheerfull message when no leak has been found

This PR proposes improvements in messages displayed to users when no leak has been found by HMSL:

more cheerful text message if no leak is found
warning color in other cases
count of leaks found to avoid empty json array as sole output if no leak has been found

Thanks!


Update to Angular 5

Angular 5 has been officially released, so we should migrate to the new version

Sure ! We have to update with latest angular-cli also, and enable aot in serve mode as recommended.

The code needed for Angular@5 has been pushed, but won't be merged immediately because there is pending issues on @angular/cli which prevents proper usage:

https://github.com/angular/angular-cli/issues/8359#issuecomment-342092153
https://github.com/angular/angular-cli/issues/6650

Also for reference, @angular/service-worker cannot be updated to @5.0.0 because of https://github.com/angular/angular-cli/issues/8247 and we cannot migrate to the new HttpClient API because of https://github.com/angular/angular/issues/18155, so we are stuck with the deprecated Http service for now 😞


SRM-16363 moved CV and SLO examples link to harness-core public repo

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6597b924de1321936f321e22--harness-developer.netlify.app

@n00bitax This PR is getting stale and falling too far behind main. Please provide the URL for a public repo (ideally Harness Community, as suggested by Sid last week) so we can merge it. If not, it will be closed due to age/staleness.

Closing due to age/inactivity.


More lint

I suggest leaving a comment in addition to explicitly disabling an individual check when the reason is not immediately obvious, reminding the reader why it was okay for that check to be disabled.

Fun fact: it was exactly that sentiment that led to pylint suppressions using symbolic names (rather than completely obscure numeric codes) a few years ago.
Today I think it's the case that some suppressions probably should be explained at every site but others are kind of assumed to have their false positive circumstances just kind of known (like with broad-except which is used whenever one software component calls "foreign" code from another, untrusted software component - of course an exception raised from the latter should be unconditionally caught by the former and not to do so would be to allow failure to cascade).
One of the problems pylint has as a tool is that the inspections that have high false positive rates (or reasonable carve-outs like broad-except) cast a high-false-positive light on the tool itself, leading authors tend to cavalierly suppress other inspections (like unnecessary-lambda) that are much more robust and should rarely-if-ever be suppressed.

Pre-merge test assessment:

Basic Tests Mac: 9804.
Bazel Full Built & Tests: Not yet in effect.
Sanity Tests (Internal CI, ignore for now): Ignoring for now.
gRPC_interop_pull_requests): 9937.
kokoro: Not yet in effect.


Synthesis failed for datalabeling

Hello! Autosynth couldn't regenerate datalabeling. :broken_heart:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to branch 'autosynth-datalabeling'
Running synthtool
['/tmpfs/src/git/autosynth/env/bin/python3', '-m', 'synthtool', 'synth.py', '--']
synthtool > Executing /tmpfs/src/git/autosynth/working_repo/google-cloud-clients/google-cloud-datalabeling/synth.py.
synthtool > Ensuring dependencies.
synthtool > Pulling artman image.
latest: Pulling from googleapis/artman
Digest: sha256:e7f9554322a8aa1416c122c918fdc4cdec8cfe816f027fc948dec0be7edef320
Status: Image is up to date for googleapis/artman:latest
synthtool > Cloning googleapis.
synthtool > Running generator for google/cloud/datalabeling/artman_datalabeling_v1beta1.yaml.
synthtool > Generated code into /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/java.
synthtool > Running java formatter on 10 files
synthtool > Running java formatter on 1 files
synthtool > Running java formatter on 227 files
synthtool > Cleaned up 0 temporary directories.
synthtool > Wrote metadata to synth.metadata.

Changed files:
?? google-cloud-clients/google-cloud-datalabeling/synth.metadata
[autosynth-datalabeling 67c307b] Regenerate datalabeling client
 1 file changed, 32 insertions(+)
 create mode 100644 google-cloud-clients/google-cloud-datalabeling/synth.metadata
remote:
remote: GitHub found 1 vulnerability on googleapis/google-cloud-java's default branch (1 moderate). To find out more, visit:
remote:      https://github.com/googleapis/google-cloud-java/network/alerts
remote:
To https://github.com/googleapis/google-cloud-java.git
 + 4bdde1f...67c307b autosynth-datalabeling -> autosynth-datalabeling (forced update)
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 223, in <module>
    main()
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 211, in main
    args.repository, branch=branch, title=pr_title, body=pr_body
  File "/tmpfs/src/git/autosynth/autosynth/github.py", line 65, in create_pull_request
    response.raise_for_status()
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/requests/models.py", line 940, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 422 Client Error: Unprocessable Entity for url: https://api.github.com/repos/googleapis/google-cloud-java/pulls

Google internal developers can see the full log here.

This was generated successfully after: https://github.com/googleapis/google-cloud-java/pull/4883


ContinueException in 【for...continue...】

  @Async(logResultTree = true)
  public JPromise<Void> get() {
      ArrayList<Long> list = new ArrayList<>() {
          {
              add(1l);
              add(2l);
          }
      };

      for (Long l : list) {
          if (true) continue;   // throw io.github.vipcxj.jasync.spec.ContinueException
          JAsync.just().await();
      }

      return JAsync.just();
  }

but the following example is successful
  @Async(logResultTree = true)
  public JPromise<Void> get() {
      ArrayList<Long> list = new ArrayList<>() {
          {
              add(1l);
              add(2l);
          }
      };

      for (Long l : list) {
          JAsync.just().await();
          if (true) continue;
      }

      return JAsync.just();
  }

I have just released v0.1.7 that references this issue.
Closing this issue. Please re-open if you think there's still more to do.


The ultralight sync team SBAT work around a well-defined spec

The spec should specify the ultralight sync protocol. This is a bit task, so this issue is to track the initial draft sections and structure of the spec.
Some of the topics to include:

Curve choices, together with relevant parameters, such as G1/G2 generators.
Diff structure - a list of public keys to remove/add, a signature, etc.
BLS signature specification.
The algorithms which the validators use to sign and light-clients use to verify.
Specific "bits-and-bytes" encodings of relevant elements.
What else?

It doesn't have to include at the moment a security analysis.

Maybe it's time to transform it into a meta-issue


Attempts to import kubernetes fails - cause its looking at localhost?

Hey folks,
I am trying to import a bunch from deployments from a namespace to understand how terraformer works. Mine just fails outright and the errors suggest its looking for the resources on localhost instead of hitting the cluster's API Server. Here's a snippet of the output.
2021/10/18 13:37:43 Refreshing state... kubernetes_deployment.tfer--default-002F-golang-002D-ex-002D-git
2021/10/18 13:37:44 Get "http://localhost/apis/apps/v1/namespaces/xxx/deployments/ayyy": dial tcp <IP_ADDRESS>:80: connect: connection refused
2021/10/18 13:37:44 WARN: Fail read resource from provider, wait 300ms before retry
2021/10/18 13:37:44 Refreshing state... kubernetes_deployment.tfer--xx-002D-xx-002D-xx-002D-dev-002F-xx-002D-xx-002D-graphql-002D-dev
2021/10/18 13:37:44 Fail read resource from provider, trying import command
2021/10/18 13:37:44 Get "http://localhost/apis/apps/v1/namespaces/openshift-cluster-storage-operator/deployments/csi-snapshot-controller-operator": dial tcp <IP_ADDRESS>:80: connect: connection refused
I have -

Added a versions.tf which indicated kubernetes as a provider and ran terraform init.2
Ran the command to import deployment objects using terraformer.

Any idea how do I make it interact with the actual API server instead of localhost?

I'm facing the same issue with GKE

I'm also having this issue, compiling from master branch.
@juliankessel Which plugin are you referring to as the workaround?

So a versions.tf with the below contents works,just make sure to clear out the .terraform* files and call terraform init again.
terraform {
  required_providers {
    kubernetes = {
      source = "hashicorp/kubernetes"
      version = "= 1.13.4"
    }
  }
  required_version = ">= 0.13"
}

The version after that is 2.0.0, which is where it tries to connect to localhost. Probably worth opening a ticket in the kubernetes terraform repository, but I'm not sure where the actual problem exists.

So further investigation revealed the 2.0.0 migration doc mentions that it does not default to using ~/.kube/config by default and the new environment variable KUBE_CONFIG_PATH should be used.
Running terraformer like this will work properly:
KUBE_CONFIG_PATH=~/.kube/config terraformer import kubernetes --resources=deployments,services,namespaces


Install mercurial and subversion for composer.

Fixes #26

@bshaffer @JustinBeckwith Give me a quick LGTM

LGTM.  One little thing - for Ruby, we keep a table that lets us remember why we install the things we're installing:
https://github.com/GoogleCloudPlatform/ruby-docker/blob/master/appengine/Dockerfile#L5
May be nice to do that here too.  That way in a year we don't come back and say "why would we have subversion, lets rip that out" :)

Thanks. You can refer to the commit message then you'll see why :)


'501 Not Implemented' is an improper response for available API versions

HTTP spec designates the 501 response code to be used for a lack of HTTP functionality. That more or less means that the HTTP method used in the request isn't implemented by the server (not that the method is not available for an existing resource - that would entail a 405 response). The proper response code for a path that does not exist on the server is 404 Not Found.
Maybe we could use the alerts JSON object instead?
Alternatively, this would also be resolved if #2872 were resolved.

@ocket8888 The RFC you linked, RFC 2616, has been obsoleted by RFC 7231. Per RFC 7231:

The 501 (Not Implemented) status code indicates that the server does
not support the functionality required to fulfill the request.  This
is the appropriate response when the server does not recognize the
request method and is not capable of supporting it for any resource.

https://tools.ietf.org/html/rfc7231#section-6.6.2
Yes, 501 is appropriate for methods not supported. But it also more generically "indicates that the server does not support the functionality required to fulfill the request". Nowhere in there does the RFC indicate the functionality not supported SHOULD or MUST be "HTTP functionality".

The proper response code for a path that does not exist on the server is 404 Not Found.

A 404 is technically appropriate, but I do not believe a 501 to be inappropriate. A 404 does not indicate that the functionality may or may not be supported by future versions, where 501 allows us to indicate the real problem, namely that newer API version was requested. Yes, we could encode the real problem in a proprietary message in the body. but a 501 is the most likely to more readily help the user understand the real problem.
https://tools.ietf.org/html/rfc7231#section-6.6

The 5xx (Server Error) class of status code indicates that the server
is aware that it has erred or is incapable of performing the
requested method.

https://tools.ietf.org/html/rfc7231#section-6.5

The 4xx (Client Error) class of status code indicates that the client
seems to have erred.

A 4xx indicates a client problem, where a 5xx indicates a server problem. In this case, the client is correct, it's just newer than the server. The server is outdated. The real problem is that to use the new client functionality, the user needs to upgrade their Traffic Ops server. So, a 5xx, and specifically a 501, most accurately conveys the real problem to the user.
Yes, you could argue the client has "erred" by being too new. But that seems like an odd argument to me.
TLDR Yes, we're using a broad interpretation of the RFC, but I don't believe it to be strictly incorrect, and it's the best way to quickly convey the problem to the user.

I disagree that the problem is server-side, the client requested access to a resource that does not exist - presumably the request failed because of that, not because the server itself failed to accomplish anything.

The 404 (Not Found) status code indicates that the origin server did not find a current representation for the target resource or is not willing to disclose that one exists.

Since we already use 404 Not Found to indicate that the requested resource does not exist (e.g. no server with id 4 exists), it probably makes sense to use 501 just to differentiate those kinds of errors from "my client is too new and is requesting an API version that the server doesn't support yet" errors.


Issue installing / Running

When running i get an error:
Any help or ideas woudl be appriciated.
Thanks
J
bitnami@debian:~/delivery-slot-bot$ yarn start
yarn run v1.22.4
$ node ./src/index.js
internal/modules/cjs/loader.js:628
    throw err;
    ^

Error: Cannot find module 'node-schedule'
Require stack:
- /home/bitnami/delivery-slot-bot/src/index.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:625:15)
    at Function.Module._load (internal/modules/cjs/loader.js:527:27)
    at Module.require (internal/modules/cjs/loader.js:683:19)
    at require (internal/modules/cjs/helpers.js:16:16)
    at Object.<anonymous> (/home/bitnami/delivery-slot-bot/src/index.js:1:18)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (internal/modules/cjs/loader.js:643:32)
    at Function.Module._load (internal/modules/cjs/loader.js:556:12)
    at Function.Module.runMain (internal/modules/cjs/loader.js:839:10) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/home/bitnami/delivery-slot-bot/src/index.js' ]
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

had a look at issue https://github.com/paulmaunders/delivery-slot-bot/issues/53 as you have gone through a lot of installation issues on that one.
yarn install --check-files
Has fixed the error for finding the modules, but now getting a chrome error.
Error: Failed to launch chrome! /home/bitnami/delivery-slot-bot/node_modules/puppeteer/.local-chromium/linux-686378/chrome-linux/chrome: error while loading shared libraries: libX11-xcb.so.1: cannot open shared object file: No such file or directory

installing puppeteer might help ;)
npm i puppeteer

.... and yargs
npm i yargs

... and moment-timezone
npm i moment-timezone

then a missing chrome dependency....:
sudo apt-get install libatk3.0-cil

think i have hit a deadend now... so some help would be appricated. Have ensured all the chrome depencies are there, and it is still comeing up with a libatk3.0 error even though it is there???
any advice would be appricated.
Thanks!
j
bitnami@debian:~/delivery-slot-bot$ yarn start
yarn run v1.22.4
$ node ./src/index.js
index.js

Runs one-off

Options:
  --version  Show version number                                       [boolean]
  --help     Show help                                                 [boolean]

Error: Failed to launch chrome!
/home/bitnami/delivery-slot-bot/node_modules/puppeteer/.local-chromium/linux-686378/chrome-linux/chrome: error while loading shared libraries: libgtk-3.so.0: cannot open shared object file: No such file or directory

TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (/home/bitnami/delivery-slot-bot/node_modules/puppeteer/lib/Launcher.js:348:14)
    at Interface.<anonymous> (/home/bitnami/delivery-slot-bot/node_modules/puppeteer/lib/Launcher.js:337:50)
    at Interface.emit (events.js:208:15)
    at Interface.close (readline.js:401:8)
    at Socket.onend (readline.js:178:10)
    at Socket.emit (events.js:208:15)
    at endReadableNT (_stream_readable.js:1154:12)
    at processTicksAndRejections (internal/process/task_queues.js:77:11)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

and then do the chrome-sandbox fix you had in 53
AND WORKING!!!!
On Tesco..


@alloy => Remove unneeded server-side fetches, and remove assign

Removes the now redundant server-side fetches (and a bit of cleanup).

Sweet 👌
Those CI failures are legit, though. Feel free to merge on green.

Sigh, I just spent half an hour trying to get the tests passing.
It uses 3+ year old libraries (stubbing Backbone sync, mocha, there's a double _.defer going on..... 😢 ), and honestly I don't think the test really does much.
I'll try for a little bit longer and then I'll just pend them for now.
cc @craigspaeth if he's up for some pairing! He is the master of these tests.

I'm down @mzikherman feel free to put w/e is on the calendar. In the future when someone touches this kind of old backbone/coffeescript code should consider taking the extra effort to decaffinate the file and attempt to use async/await + metaphysics—too optimisitic maybe, but thatd simplify the stubbing madness quite a bit.

Ah good call @craigspaeth yea, that might be nice. I'll hunt around for some examples.
I'll make that a follow-up issue and pend for now, as working on the filters for Relay Modern basically got creeped to do a full rebuild of the gene + tag pages! 😅

I’m going to assume that you verified that the things the test tried to verify actually still work and merge 👍


Mention Nativefier options at app build time, in order to improve discoverability

First, a lot of issues are feature requests already present in nativefier as options, but user don't know about them.
Second, a lot of issues are about using old Electron versions. A fix is of course to release frequently with recent electron versions, but it only goes so far (doesn't cover users on old versions of Nativefier), so I think we should put give some emphasis to --electron-version.
I propose we add a little text popping up at app build time encouraging users to have a look at them. It would look like this:
~ nativefier -e 1.6.6 --name "gmail" "https://mail.google.com/mail"
Nativefier has many optional features you might like, run nativefier --help for the full list.
In particular, use --electron-version to pick your electron/chrome version!
Check you're asking for a recent one at https://github.com/electron/electron/releases
[ ... existing output]

EDIT 2017-04-19: In addition to mentioning use --electron-version to pick your electron/chrome version, since we're making network requests anyway to get the electron version list for useragent setting, we could explicitly say Building with Electron a.b.c, but a.b.f is available. Use --electron-version to pick your electron/chrome version!.
Note: I guess we don't want to dynamically/automatically use the last version, that would introduce non-deterministic behavior and may make troubleshooting more painful by putting us too much at Electron's bleeding edge.
Thoughts?

@ronjouch I think it's a little obvious to tell the user to check nativefier --help, but it's definitely a good idea to print the latest electron version there! Also, it would be great if we could print something telling them that they are using a outdated version of nativefier, or other useful things that they might want to know!

"I think it's a little obvious to tell the user to check nativefier --help, but it's definitely a good idea to print the latest electron version there! Also, it would be great if we could print something telling them that they are using a outdated version of nativefier, or other useful things that they might want to know!"

@jiahaog good point for the outdated nativefier, I'll consider it.
And regarding telling/encouraging to check nativefier --help, it's an idea I got after my big issue triage, which led me to think it's not so obvious for many users. Will keep it short when I work on it, and will submit output examples that we can discuss.

@ronjouch: I would prefer defaulting to the use of the latest stable electron version (which should be the version with the least bugs and security leaks). In the case the newest version introduces bugs nativefier has the option to set a custom (older) electron version making sure the user has something to fall back to.
This is why:
I don't follow electron releases so expecting me to specify electron releases forces me to make decisions I am not fit to make (I also happen to be lazy ^^) and where nativefier (in my case) made the lesser choice by default. An app was failing me and my default behaviour (rebuilding the app with nativefier after updating nativefier) did not fix it as I did not specify an electron version.
Annother idea:
If a commandline setting is optional, I expect software to use sane defaults, so if you want users to look into the options and choose please make the setting required (in this case the -e|--electron-version option).


Adding new attribute 'KnowType' to solve problems with the inability to create an interface or abstract class

Hi! When using the parameters of the interface method and the abstract class, Newtonsoft.Json throws an exception: 'Could not create an instance of type X. Type is an interface or abstract class and cannot be instantiated.'
Solve this problem can be settings JsonSerializer but why in this situation it did not solve the problem.
So I made a new attribute.
Here is an example of use:
[KnowType(typeof(Test))]
public interface ITest
{
    int Sum { get; }
}

@maksim789456 Thanks for your contribution. But instead of introducing a custom KnowType attribute, I fixed the problem by #107.
I'm closing this PR and feel free to reopen if you disagree.
Thanks again


Bumped snakeyaml version to address CVE-2022-25857

Description
Bumped snakeyaml version to address CVE-2022-25857
Issues Resolved
N/A
Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

LGTM. can you modify the commit to add DCO ?

Yes. Doing that.


Fix socket_addr_len

socket_addr_len "Specifies the length in bytes of the buffer pointed to by the buffer argument.", see https://pubs.opengroup.org/onlinepubs/9699919799/functions/recvfrom.html.
Now correctly returns the senders IP address.

Huh, good catch!


Min/max/exact number of checkboxes items required

Describe the solution you'd like
Allow study designers to define a min/max/exact number of checkbox items required for a response. This would be handled with the normal validation logic

Closed via #428


Add  element. closes #56

There are probably some more elements that don't highlight, but main seems to be low hanging fruit.

Closes #56

Is this still a wanted/desired change?


connection via pgbouncer takes 10x longer to load

Bug report
Describe the bug
Related to issue #203 (which is closed now): I'm currently encountering an issue where, holding everything else constant, if I switch from a connection to port 5432 to a connection to post 6543 using pg_bouncer, the same query takes 10x longer. This occurs in a local environment, but haven't been able to test in production yet.
Tech information

Nextjs v13.2.1
prisma v4.11.0

Could you share more details about your local development setup?
We officially support the CLI for local development but it doesn't run pgbouncer locally at all.

I was not using the CLI, but using prisma within a serverless frontend (NextJS) frameworks

Closing as pg_bouncer has been replaced with supavisor. Please follow up if this issue is still relevant and I misunderstood


Initial implementation of the calendar panel for the MVP.

Display the free hours in the calendar panel, both work and personal time.

The event duration is subtracted from either the personal or work time depending on the beginning of the event.
Will later work on having the possibility to differentiate between the work hours and personal time for a single event that overlaps both.
The work hours are defined as being between 10:00 am to 6:00 pm. The time is given as a long representing the Unix time. The timezone used is UTC.
The code to calculate the free time left is not very accurate and fails to account for many edge cases, will have to refactor the method as stated in Issue #104

Enhancement: Whenever you can, can you also implement default values while the panel is loading (Reference changes in PR #140). Basically, at the start of the populate-calendar function, just set the values for each of the containers to - or something to signify no data is (yet) available.
This isn't worth putting us off track for (so please feel free to let me know if you don't have time for this), but I think it would be cool


Auto close last logsegment during compaction

This pr support close last log segment before compact all policy, journal need to be clean up right after it.

Codecov Report

Merging #1844 (78fa93d) into master (729b93a) will decrease coverage by 12.33%.
The diff coverage is 13.00%.

@@              Coverage Diff              @@
##             master    #1844       +/-   ##
=============================================
- Coverage     74.05%   61.72%   -12.34%
+ Complexity     9577     7837     -1740
=============================================
  Files           690      690
  Lines         52456    52647      +191
  Branches       6512     6550       +38
=============================================
- Hits          38848    32496     -6352
- Misses        11577    18088     +6511
- Partials       2031     2063       +32

Impacted Files
Coverage Δ
Complexity Δ

...rc/main/java/com/github/ambry/store/BlobStore.java
47.43% <0.00%> (-40.28%)
52.00 <0.00> (-94.00)

...ava/com/github/ambry/store/BlobStoreCompactor.java
5.53% <0.00%> (-83.62%)
7.00 <0.00> (-132.00)

...java/com/github/ambry/store/CompactionManager.java
11.42% <0.00%> (-82.80%)
8.00 <0.00> (-19.00)

.../src/main/java/com/github/ambry/store/Journal.java
55.44% <0.00%> (-30.10%)
18.00 <0.00> (-12.00)

...n/java/com/github/ambry/store/PersistentIndex.java
37.89% <4.34%> (-53.81%)
91.00 <0.00> (-183.00)

...tore/src/main/java/com/github/ambry/store/Log.java
37.87% <8.57%> (-60.69%)
28.00 <0.00> (-33.00)

...main/java/com/github/ambry/store/IndexSegment.java
29.30% <53.84%> (-57.38%)
37.00 <0.00> (-113.00)

...main/java/com/github/ambry/config/StoreConfig.java
100.00% <100.00%> (ø)
1.00 <0.00> (ø)

...rc/main/java/com/github/ambry/store/TimeRange.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-8.00%)

...java/com/github/ambry/notification/UpdateType.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-1.00%)

... and 159 more

Continue to review full report at Codecov.

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


Expose openssl/vendored in encryption

What is changed and how it works?

Issue Number: Close #16222

What's Changed:
Expose openssl/vendored in encryption

Related changes

[ ] PR to update pingcap/docs/pingcap/docs-cn:
[ ] Need to cherry-pick to the release branch

Check List
Tests

[ ] Unit test
[ ] 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

Release note

None

/test


Stuck in full screen mode

I don't know why but once I click on the full screen button, I can't go back with ESC. Can I keep the button directly on the canva as a tool?

Hi. Excalidraw doesn't have a fullscreen button per-se. Are we talking about the Obsidian plugin? https://github.com/excalidraw/excalidraw/issues/5991

yes


list storage account and access key?

I want to list storage accounts and access keys to implement something similar to Azure CLI storage account list and storage account key list, but it seems storage account list is not implemented in  storage service entities
@ahmetalpbalkan @colemickens

found, it.


Position of section break elements is incorrect

The positions of section break elements don't seem to fit in Word nor in InDesign. (#2)

These lastRenderedPageBreak elements were misinterpreted as section breaks during the transformation.

This element specifies that this position delimited the end of a page when this document was last saved by an application which paginates its content.[^1]

[^1]: Position of Last Calculated Page Break
The last rendered page breaks do not make any sense when importing Word documents into InDesign. The position is application specific. Therefore, they are no longer transferred.
Fixed with #10


So I think that because they're worklets (at least on the web) then the innerPEC will persist, as an idle eventLoop in a process waiting for messages.
Which means we probably need a way to cleanly shut them down.

@shans thanks. i added disposal for the speculative arcs. PTAL

@shans could you, please, take a look?


Ptc login works, but Google gives error

Expected Behavior
Pokemon Go Bot is working with PTC accounts but not Google.
Actual Behavior
Gives an error and wont initiate login
Your FULL config.json (remove your username, password, gmapkey and any other private info)

{
"websocket_server": false,
"heartbeat_threshold": 10,
"enable_social": true,
"live_config_update": {
"enabled": false,
"tasks_only": false
},
"tasks": [
{
"type": "TelegramTask",
"config": {
"enabled": false,
"master": null,
"// old syntax, still supported: alert_catch": ["all"],
"// new syntax:": {},
"alert_catch": {
"all": {"operator": "and", "cp": 1300, "iv": 0.95},
"Snorlax": {"operator": "or", "cp": 900, "iv": 0.9}
}
}
},
{
"//NOTE: This task MUST be placed on the top of task list": {},
"type": "RandomAlivePause",
"config": {
"enabled": false,
"min_duration": "00:00:10",
"max_duration": "00:10:00",
"min_interval": "00:05:00",
"max_interval": "01:30:00"
}
},
{
"type": "HandleSoftBan"
},
{
"type": "RandomPause",
"config": {
"enabled": false,
"min_duration": "00:00:10",
"max_duration": "00:10:00",
"min_interval": "00:10:00",
"max_interval": "02:00:00"
}
},
{
"type": "CompleteTutorial",
"config": {
"enabled": false,
"// set a name": "",
"nickname": "",
"// 0 = No Team, 1 = Blue, 2 = Red, 3 = Yellow": "",
"team": 0
}
},
{
"type": "CollectLevelUpReward",
"config": {
"collect_reward": true,
"level_limit": -1
}
},
{
"type": "IncubateEggs",
"config": {
"enabled": false,
"infinite_longer_eggs_first": false,
"breakable_longer_eggs_first": true,
"min_interval": 120,
"infinite": [2,5,10],
"breakable": [2,5,10]
}
},
{
"type": "UpdateLiveStats",
"config": {
"enabled": true,
"min_interval": 10,
"stats": ["username", "uptime", "stardust_earned", "xp_earned", "xp_per_hour", "stops_visited"],
"terminal_log": true,
"terminal_title": true
}
},
{
"type": "UpdateLiveInventory",
"config": {
"enabled": false,
"min_interval": 120,
"show_all_multiple_lines": false,
"items": ["pokemon_bag", "space_info", "pokeballs", "greatballs", "ultraballs", "razzberries", "luckyegg"]
}
},
{
"type": "ShowBestPokemon",
"config": {
"enabled": true,
"min_interval": 60,
"amount": 5,
"order_by": "cp",
"info_to_show": ["cp", "ivcp", "dps", "hp"]
}
},
{
"type": "TransferPokemon",
"config": {
"enabled": true,
"min_free_slot": 5,
"transfer_wait_min": 3,
"transfer_wait_max": 5
}
},
{
"type": "NicknamePokemon",
"config": {
"enabled": true,
"nickname_above_iv": 0.9,
"nickname_template": "{iv_pct}_{iv_ads}",
"nickname_wait_min": 3,
"nickname_wait_max": 5
}
},
{
"type": "EvolvePokemon",
"config": {
"enabled": false,
        "// evolve only pidgey and drowzee": "",
        "// evolve_list": "pidgey, drowzee",
        "// donot_evolve_list": "none",

        "// evolve all but pidgey and drowzee": "",
        "// evolve_list": "all",
        "// donot_evolve_list": "pidgey, drowzee",

        "evolve_list": "all",
        "donot_evolve_list": "none",

      "first_evolve_by": "cp",
      "evolve_above_cp": 500,
      "evolve_above_iv": 0.8,
      "logic": "or",
      "min_evolve_speed": 25,
      "max_evolve_speed": 30,
      "use_lucky_egg": false
    }
  },
  {
    "type": "UseIncense",
    "config": {
      "use_incense": false,
      "use_order": [
        "ordinary",
        "spicy",
        "cool",
        "floral"
      ]
    }
  },
  {
    "type": "RecycleItems",
    "config": {
      "enabled": true,
      "min_empty_space": 15,
      "max_balls_keep": 150,
      "max_potions_keep": 2,
      "max_berries_keep": 2,
      "max_revives_keep": 2,
      "item_filter": {
        "Pokeball":       { "keep" : 100 },
        "Potion":         { "keep" : 1 },
        "Super Potion":   { "keep" : 1 },
        "Hyper Potion":   { "keep" : 1 },
        "Revive":         { "keep" : 1 },
        "Razz Berry":     { "keep" : 100 }
      },
      "recycle_wait_min": 3,
      "recycle_wait_max": 5,
      "recycle_force": true,
      "recycle_force_min": "00:01:00",
      "recycle_force_max": "00:05:00"
    }
  },
  {
    "type": "CatchPokemon",
    "config": {
      "enabled": true,
      "catch_visible_pokemon": true,
      "catch_lured_pokemon": true,
      "min_ultraball_to_keep": 5,
      "berry_threshold": 0.35,
      "vip_berry_threshold": 0.9,
      "treat_unseen_as_vip": true,
      "daily_catch_limit": 800,
      "vanish_settings": {
        "consecutive_vanish_limit": 10,
        "rest_duration_min": "02:00:00",
        "rest_duration_max": "04:00:00"
      },
      "catch_throw_parameters": {
        "excellent_rate": 0.1,
        "great_rate": 0.5,
        "nice_rate": 0.3,
        "normal_rate": 0.1,
        "spin_success_rate" : 0.6,
        "hit_rate": 0.75
      },
      "catch_simulation": {
        "flee_count": 3,
        "flee_duration": 2,
        "catch_wait_min": 3,
        "catch_wait_max": 6,
        "berry_wait_min": 3,
        "berry_wait_max": 5,
        "changeball_wait_min": 3,
        "changeball_wait_max": 5,
        "newtodex_wait_min": 20,
        "newtodex_wait_max": 30
      }
    }
  },
  {
    "type": "SpinFort",
    "config": {
      "enabled": true,
      "spin_wait_min": 3,
      "spin_wait_max": 5,
      "daily_spin_limit": 1900
    }
  },
  { "type": "UpdateWebInventory",
    "config": {
      "enabled": true
    }
  },
  {
    "type": "MoveToFort",
    "config": {
      "enabled": true,
      "lure_attraction": true,
      "lure_max_distance": 2000,
      "walker": "StepWalker",
      "log_interval": 5
    }
  },
  {
    "type": "FollowSpiral",
    "config": {
      "enabled": true,
      "diameter": 4,
      "step_size": 70
    }
  }
],
"map_object_cache_time": 5,
"forts": {
  "avoid_circles": true,
  "max_circle_size": 50,
  "cache_recent_forts": true
},
"pokemon_bag": {
  "// if 'show_at_start' is true, it will log all the pokemons in the bag (not eggs) at bot start": {},
  "show_at_start": true,
  "// if 'show_count' is true, it will show the amount of each pokemon (minimum 1)": {},
  "show_count": false,
  "// if 'show_candies' is true, it will show the amount of candies for each pokemon": {},
  "show_candies": false,
  "// 'pokemon_info' parameter define which info to show for each pokemon": {},
  "// the available options are": {},
  "// ['cp', 'iv_ads', 'iv_pct', 'ivcp', 'ncp', 'level', 'hp', 'moveset', 'dps']": {},
  "pokemon_info": ["cp", "iv_pct"]
},
"walk_max": 4.16,
"walk_min": 2.16,
"alt_min": 500,
"alt_max": 1000,
"sleep_schedule": [
  {
    "time": "15:00",
    "duration": "2:00",
    "time_random_offset": "00:30",
    "duration_random_offset": "00:30",
    "wake_up_at_location": ""
  },
  {
    "time": "19:00",
    "duration": "3:00",
    "time_random_offset": "01:00",
    "duration_random_offset": "00:30",
    "wake_up_at_location": ""
  }
],
"gps_default_altitude": 8.0,
"replicate_gps_xy_noise": false,
"replicate_gps_z_noise": false,
"gps_xy_noise_range": 0.000125,
"gps_z_noise_range": 12.5,
"debug": false,
"test": false,
"walker_limit_output": false,
"health_record": true,
"location_cache": true,
"distance_unit": "km",
"reconnecting_timeout": 15,
"logging": {
  "color": true,
  "show_datetime": true,
  "show_process_name": true,
  "show_log_level": true,
  "show_thread_name": false
},
"catch": {
  "any": {"candy_threshold" : 400 ,"catch_above_cp": 0, "catch_above_iv": 0, "logic": "or"},
  "// Example of always catching Rattata:": {},
  "// Rattata": { "always_catch" : true }
},
"release": {
  "any": {"release_below_cp": 0, "release_below_iv": 0, "logic": "or"},
  "// Example of always releasing Rattata:": {},
  "// Rattata": {"always_release": true},
  "// Example of keeping 3 stronger (based on CP) Pidgey:": {},
  "// any": {"keep_best_cp": 2},
  "// Example of keeping 2 best (based on IV) Zubat:": {},
  "// Zubat": {"keep_best_iv": 2},
  "// Keep no more than 3 best IV pokemon for every pokemon type": {},
  "// any": {"keep_best_iv": 2},
  "// Discard all pokemon in bag except 100 pokemon with best CP": {},
  "all": {"keep_best_cp": 200},
  "// Example of keeping the 2 strongest (based on CP) and 3 best (based on IV) Zubat:": {},
  "any": {"keep_best_cp": 2, "keep_best_iv": 2},
  "// Example of custom order of static criterion": {},
  "// Zubat": {"keep_best_custom": "iv, cp, hp_max", "amount":2}
},
"vips" : {
    "Any pokemon put here directly force to use Berry & Best Ball to capture, to secure the capture rate": {},
    "any": {"catch_above_cp": 1200, "catch_above_iv": 0.9, "logic": "or" },
    "Lapras": {},
    "Moltres": {},
    "Zapdos": {},
    "Articuno": {},

    "// S-Tier pokemons (if pokemon can be evolved into tier, list the representative)": {},
    "Mewtwo": {},
    "Dragonite": {},
    "Snorlax": {},
    "// Mew evolves to Mewtwo": {},
    "Mew": {},
    "Arcanine": {},
    "Vaporeon": {},
    "Gyarados": {},
    "Exeggutor": {},
    "Muk": {},
    "Weezing": {},
    "Flareon": {}
},
"websocket": {
	"start_embedded_server": true,
	"server_url": "<IP_ADDRESS>:4000"
}

}
Output when issue occurred

2016-09-10 11:51:43,700 [       cli] [INFO] PokemonGO Bot v1.0
2016-09-10 11:51:43,714 [       cli] [INFO] commit: 11123a82
2016-09-10 11:51:43,718 [       cli] [INFO] Configuration initialized
2016-09-10 11:51:43,718 [pokemongo_bot.health_record.bot_event] [INFO] Health check is enabled. For more information:
2016-09-10 11:51:43,718 [pokemongo_bot.health_record.bot_event] [INFO] https://github.com/PokemonGoF/PokemonGo-Bot/tree/dev#analytics
2016-09-10 11:51:43,729 [requests.packages.urllib3.connectionpool] [INFO] Starting new HTTP connection (1): www.google-analytics.com
(13588) wsgi starting up on http://<IP_ADDRESS>:4000
2016-09-10 11:51:43,910 [requests.packages.urllib3.connectionpool] [INFO] Starting new HTTP connection (1): <IP_ADDRESS>
[2016-09-10 11:51:43] [SleepSchedule] [INFO] Next sleep at 15:12:27, for a duration of 2:11:09
[2016-09-10 11:51:44] [PokemonGoBot] [INFO] Setting start location.
[2016-09-10 11:51:44] [PokemonGoBot] [INFO] [x] Coordinates found in passed in location, not geocoding.
[2016-09-10 11:51:44] [PokemonGoBot] [INFO] Location found: 37.787694, -122.407440 (37.787694, -122.40744, 8.0)
[2016-09-10 11:51:44] [PokemonGoBot] [INFO] Now at (37.787694, -122.40744, 8.0)
[2016-09-10 11:51:44] [PokemonGoBot] [INFO] Login procedure started.
Traceback (most recent call last):
File "pokecli.py", line 802, in
main()
File "pokecli.py", line 238, in main
report_summary(bot)
File "pokecli.py", line 286, in report_summary
metrics.capture_stats()
File "/media/stephenm/STORAGE/Software/PokemonGo-Bot/pokemongo_bot/metrics.py", line 105, in capture_stats
self.dust['latest'] = self.bot.stardust
File "/media/stephenm/STORAGE/Software/PokemonGo-Bot/pokemongo_bot/init.py", line 72, in stardust
return filter(lambda y: y['name'] == 'STARDUST', self._player['currencies'])[0]['amount']
AttributeError: 'PokemonGoBot' object has no attribute '_player'
[2016-09-10 11:51:44] [sentry.errors] [ERROR] Sentry responded with an error: 'utf8' codec can't decode byte 0x9c in position 1: invalid start byte (url: https://app.getsentry.com/api/90254/store/)
Traceback (most recent call last):
File "/media/stephenm/STORAGE/Software/PokemonGo-Bot/local/lib/python2.7/site-packages/raven/transport/threaded.py", line 174, in send_sync
super(ThreadedHTTPTransport, self).send(data, headers)
File "/media/stephenm/STORAGE/Software/PokemonGo-Bot/local/lib/python2.7/site-packages/raven/transport/http.py", line 47, in send
ca_certs=self.ca_certs,
File "/media/stephenm/STORAGE/Software/PokemonGo-Bot/local/lib/python2.7/site-packages/raven/utils/http.py", line 66, in urlopen
return opener.open(url, data, timeout)
File "/media/stephenm/STORAGE/Software/PokemonGo-Bot/local/lib/python2.7/site-packages/future/backports/urllib/request.py", line 494, in open
response = self._open(req, data)
File "/media/stephenm/STORAGE/Software/PokemonGo-Bot/local/lib/python2.7/site-packages/future/backports/urllib/request.py", line 512, in _open
'_open', req)
File "/media/stephenm/STORAGE/Software/PokemonGo-Bot/local/lib/python2.7/site-packages/future/backports/urllib/request.py", line 466, in _call_chain
result = func(*args)
File "/media/stephenm/STORAGE/Software/PokemonGo-Bot/local/lib/python2.7/site-packages/raven/utils/http.py", line 46, in https_open
return self.do_open(ValidHTTPSConnection, req)
File "/media/stephenm/STORAGE/Software/PokemonGo-Bot/local/lib/python2.7/site-packages/future/backports/urllib/request.py", line 1284, in do_open
h.request(req.get_method(), req.selector, req.data, headers)
File "/usr/lib/python2.7/httplib.py", line 1048, in request
self._send_request(method, url, body, headers)
File "/usr/lib/python2.7/httplib.py", line 1088, in _send_request
self.endheaders(body)
File "/usr/lib/python2.7/httplib.py", line 1044, in endheaders
self._send_output(message_body)
File "/usr/lib/python2.7/httplib.py", line 886, in _send_output
msg += message_body
File "/media/stephenm/STORAGE/Software/PokemonGo-Bot/lib/python2.7/encodings/utf_8.py", line 16, in decode
return codecs.utf_8_decode(input, errors, True)
UnicodeDecodeError: 'utf8' codec can't decode byte 0x9c in position 1: invalid start byte
[2016-09-10 11:51:44] [sentry.errors.uncaught] [ERROR] [u"AttributeError: 'PokemonGoBot' object has no attribute '_player'", u'  File "pokecli.py", line 802, in ', u'  File "pokecli.py", line 238, in main', u'  File "pokecli.py", line 286, in report_summary', u'  File "pokemongo_bot/metrics.py", line 105, in capture_stats', u'  File "pokemongo_bot/init.py", line 72, in stardust']
Sat Sep 10 11:51:44 EDT 2016 Pokebot  Stopped.
Press any button or wait 20 seconds to continue.
Steps to Reproduce

Anytime I use a Google account.
Other Information
OS:

Branch:

Git Commit:

Python Version:

Any other relevant files/configs (eg: path files)

Short Description

Possible solution

How it would help others

I've got same problem, PTC works well but goole account is not working

Do you have 2FA enabled on your Google account? I created a separate App Password and haven't had any problems with logging in.

PgoApi issue. See #5561 for further updates/workaround.


How to return CBCentralManager property to Use in react-native-nordic-dfu

  [RNNordicDfu setCentralManagerGetter:^() {
    return [BleManager getCentralManager];
  }];

  // Reset manager delegate since the Nordic DFU lib "steals" control over it
  [RNNordicDfu setOnDFUComplete:^() {
    NSLog(@"onDFUComplete");
    CBCentralManager * manager = [BleManager getCentralManager];
    manager.delegate = [BleManager getInstance];
  }];
  [RNNordicDfu setOnDFUError:^() {
    NSLog(@"onDFUError");
    CBCentralManager * manager = [BleManager getCentralManager];
    manager.delegate = [BleManager getInstance];
  }];

It can be work  in case of react-native- Ble-manager, but in case of react-native-ble-plx (We are using )it is not working
Dependencies :
"react-native-ble-plx": "^0.9.1",
"react-native-nordic-dfu": "^1.2.1"

You can create a separate CBCentralManager — from my experience it works just fine

Closing as this is suggested solution in case of mixing multiple BLE libraries.

Hii dariuszseweryn - Thanks for suggestion can you you please provide a little example code so i can fix this

https://github.com/Polidea/react-native-ble-plx/issues/260