getting password mismatch error in while running fastlane in azure devops yaml file

Hello in my Azure CI/CD pipeline I am trying to integrate testflight for deployment on app store .
pipeline command are as below:

script: |
gem install fastlane
export APPLE_ID_PASSWORD=$(Apple_ID_Pswd)
export FASTLANE_PASSWORD=$(Fastlane_Pswd)
fastlane pilot upload --verbose -u *** -a com.beasensors.orascan -f '$(build.artifactStagingDirectory)/output/$(SDK)/$(Configuration)/***.ipa'
displayName: 'Upload to TestFlight'

where APPLE_ID_PASSWORD is the apple developer account password
and FASTLANE_PASSWORD is the app specific token created by same apple developer account .
since it is non intearctive shell 2FA will not work here , so i am trying to use app specific token ,but i am getting password mismatch error . could you please help me in this regard
log file are as below
2023-06-05T14:04:32.9181200Z ##[debug]Evaluating condition for step: 'Upload to TestFlight'

2023-06-05T14:04:32.9183000Z ##[debug]Evaluating: SucceededNode()
2023-06-05T14:04:32.9183370Z ##[debug]Evaluating SucceededNode:
2023-06-05T14:04:32.9183980Z ##[debug]=> True
2023-06-05T14:04:32.9184840Z ##[debug]Result: True
2023-06-05T14:04:32.9185620Z ##[section]Starting: Upload to TestFlight
2023-06-05T14:04:32.9194370Z ==============================================================================
2023-06-05T14:04:32.9194510Z Task         : Command line
2023-06-05T14:04:32.9194560Z Description  : Run a command line script using Bash on Linux and macOS and cmd.exe on Windows
2023-06-05T14:04:32.9194650Z Version      : 2.212.0
2023-06-05T14:04:32.9194700Z Author       : Microsoft Corporation
2023-06-05T14:04:32.9194780Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/command-line
2023-06-05T14:04:32.9194870Z ==============================================================================
2023-06-05T14:04:32.9753850Z ##[debug]Using node path: /Users/runner/runners/3.220.2/externals/node16/bin/node
2023-06-05T14:04:33.1116800Z ##[debug]agent.TempDirectory=/Users/runner/work/_temp
2023-06-05T14:04:33.1135070Z ##[debug]loading inputs and endpoints
2023-06-05T14:04:33.1141230Z ##[debug]loading INPUT_SCRIPT
2023-06-05T14:04:33.1157740Z ##[debug]loading INPUT_WORKINGDIRECTORY
2023-06-05T14:04:33.1160090Z ##[debug]loading INPUT_FAILONSTDERR
2023-06-05T14:04:33.1162500Z ##[debug]loading ENDPOINT_AUTH_SYSTEMVSSCONNECTION
2023-06-05T14:04:33.1165380Z ##[debug]loading ENDPOINT_AUTH_SCHEME_SYSTEMVSSCONNECTION
2023-06-05T14:04:33.1167410Z ##[debug]loading ENDPOINT_AUTH_PARAMETER_SYSTEMVSSCONNECTION_ACCESSTOKEN
2023-06-05T14:04:33.1173010Z ##[debug]loading SECRET_FASTLANE_USER
2023-06-05T14:04:33.1176800Z ##[debug]loading SECRET_KEYCHAINPASSWORD
2023-06-05T14:04:33.1180320Z ##[debug]loading SECRET_SYSTEM_ACCESSTOKEN
2023-06-05T14:04:33.1184240Z ##[debug]loading SECRET_FASTLANE_PASSWORD
2023-06-05T14:04:33.1188180Z ##[debug]loading SECRET_APPLE_ID_PSWD
2023-06-05T14:04:33.1192140Z ##[debug]loading SECRET_APPLE_ID_USERNAME
2023-06-05T14:04:33.1195670Z ##[debug]loaded 12
2023-06-05T14:04:33.1201540Z ##[debug]Agent.ProxyUrl=undefined
2023-06-05T14:04:33.1202300Z ##[debug]Agent.CAInfo=undefined
2023-06-05T14:04:33.1202790Z ##[debug]Agent.ClientCert=undefined
2023-06-05T14:04:33.1203360Z ##[debug]Agent.SkipCertValidation=undefined
2023-06-05T14:04:33.1314000Z ##[debug]check path : /Users/runner/work/_tasks/CmdLine_d9bafed4-0b18-4f58-968d-86655b4d2ce9/2.212.0/task.json
2023-06-05T14:04:33.1318350Z ##[debug]adding resource file: /Users/runner/work/_tasks/CmdLine_d9bafed4-0b18-4f58-968d-86655b4d2ce9/2.212.0/task.json
2023-06-05T14:04:33.1318880Z ##[debug]system.culture=en-US
2023-06-05T14:04:33.1338880Z ##[debug]failOnStderr=false
2023-06-05T14:04:33.1342610Z ##[debug]script=gem install fastlane
export APPLE_ID_PASSWORD=***
export FASTLANE_PASSWORD=***
fastlane pilot upload --verbose -u *** -a com.beasensors.orascan -f '/Users/runner/work/1/a/output/iphoneos/Release/.ipa'
2023-06-05T14:04:33.1345390Z ##[debug]workingDirectory=/Users/runner/work/1/s
2023-06-05T14:04:33.1346940Z ##[debug]check path : /Users/runner/work/1/s
2023-06-05T14:04:33.1367330Z Generating script.
2023-06-05T14:04:33.1370320Z ##[debug]Agent.Version=3.220.2
2023-06-05T14:04:33.1370820Z ##[debug]agent.tempDirectory=/Users/runner/work/_temp
2023-06-05T14:04:33.1371250Z ##[debug]check path : /Users/runner/work/_temp
2023-06-05T14:04:33.1380280Z ========================== Starting Command Output ===========================
2023-06-05T14:04:33.1383280Z ##[debug]which 'bash'
2023-06-05T14:04:33.1405740Z ##[debug]found: '/bin/bash'
2023-06-05T14:04:33.1407070Z ##[debug]which '/bin/bash'
2023-06-05T14:04:33.1408790Z ##[debug]found: '/bin/bash'
2023-06-05T14:04:33.1410400Z ##[debug]/bin/bash arg: --noprofile
2023-06-05T14:04:33.1411650Z ##[debug]/bin/bash arg: --norc
2023-06-05T14:04:33.1412150Z ##[debug]/bin/bash arg: /Users/runner/work/_temp/efee1b2b-1ff2-4191-9038-1be807bd1558.sh
2023-06-05T14:04:33.1415810Z ##[debug]exec tool: /bin/bash
2023-06-05T14:04:33.1416290Z ##[debug]arguments:
2023-06-05T14:04:33.1416800Z ##[debug]   --noprofile
2023-06-05T14:04:33.1417320Z ##[debug]   --norc
2023-06-05T14:04:33.1417790Z ##[debug]   /Users/runner/work/_temp/efee1b2b-1ff2-4191-9038-1be807bd1558.sh
2023-06-05T14:04:33.1420810Z [command]/bin/bash --noprofile --norc /Users/runner/work/_temp/efee1b2b-1ff2-4191-9038-1be807bd1558.sh
2023-06-05T14:05:00.9536980Z Successfully installed fastlane-2.213.0
2023-06-05T14:05:00.9538000Z Parsing documentation for fastlane-2.213.0
2023-06-05T14:05:00.9538620Z Installing ri documentation for fastlane-2.213.0
2023-06-05T14:05:00.9539220Z Done installing documentation for fastlane after 23 seconds
2023-06-05T14:05:00.9539730Z 1 gem installed
2023-06-05T14:05:02.9054510Z [14:05:02]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
2023-06-05T14:05:05.1634840Z INFO [2023-06-05 14:05:05.16]: Sending anonymous analytics information
2023-06-05T14:05:05.1636880Z INFO [2023-06-05 14:05:05.16]: Learn more at https://docs.fastlane.tools/#metrics
2023-06-05T14:05:05.1638450Z INFO [2023-06-05 14:05:05.16]: No personal or sensitive data is sent.
2023-06-05T14:05:05.1639500Z INFO [2023-06-05 14:05:05.16]: You can disable this by adding opt_out_usage at the top of your Fastfile
2023-06-05T14:05:05.2063820Z INFO [2023-06-05 14:05:05.20]: Login to App Store Connect ()
2023-06-05T14:05:05.2119140Z Reading keychain entry, because either user or password were empty
2023-06-05T14:05:05.7054170Z The login credentials for '' seem to be wrong
2023-06-05T14:05:05.7054860Z The password was taken from the environment variable
2023-06-05T14:05:05.7055280Z Please make sure it is correct
2023-06-05T14:05:05.7159750Z
2023-06-05T14:05:05.7160670Z Looking for related GitHub issues on fastlane/fastlane...
2023-06-05T14:05:05.7161340Z Search query: The request could not be completed because:
2023-06-05T14:05:05.7162380Z 	Invalid username and password combination. Used '' as the username.
2023-06-05T14:05:05.7163230Z
2023-06-05T14:05:05.7163940Z URL: https://api.github.com/search/issues?q=The request could not be completed because%3A
	Invalid username and password combination. Used '***' as the username.+repo:fastlane/fastlane
2023-06-05T14:05:05.8286580Z Found no similar issues. To create a new issue, please visit:
2023-06-05T14:05:05.8288760Z https://github.com/fastlane/fastlane/issues/new
2023-06-05T14:05:05.8289560Z Run fastlane env to append the fastlane environment to your issue
2023-06-05T14:05:05.8292160Z /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/spaceship/lib/spaceship/client.rb:511:in rescue in send_shared_login_request': \e[31m[!] The request could not be completed because: (Spaceship::InvalidUserCredentialsError) 2023-06-05T14:05:05.8293300Z 	Invalid username and password combination. Used '***' as the username.\e[0m 2023-06-05T14:05:05.8293820Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/spaceship/lib/spaceship/client.rb:474:in send_shared_login_request'
2023-06-05T14:05:05.8294440Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/spaceship/lib/spaceship/tunes/tunes_client.rb:130:in send_login_request' 2023-06-05T14:05:05.8295950Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/spaceship/lib/spaceship/client.rb:855:in do_login'
2023-06-05T14:05:05.8296370Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/spaceship/lib/spaceship/client.rb:394:in login' 2023-06-05T14:05:05.8296950Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/spaceship/lib/spaceship/client.rb:355:in login'
2023-06-05T14:05:05.8297490Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/spaceship/lib/spaceship/tunes/spaceship.rb:24:in login' 2023-06-05T14:05:05.8297950Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/spaceship/lib/spaceship/connect_api/client.rb:56:in login'
2023-06-05T14:05:05.8299100Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/spaceship/lib/spaceship/connect_api/spaceship.rb:85:in login' 2023-06-05T14:05:05.8299570Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/pilot/lib/pilot/manager.rb:36:in login'
2023-06-05T14:05:05.8300120Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/pilot/lib/pilot/manager.rb:19:in start' 2023-06-05T14:05:05.8300580Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/pilot/lib/pilot/build_manager.rb:17:in upload'
2023-06-05T14:05:05.8301040Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/pilot/lib/pilot/commands_generator.rb:67:in block (2 levels) in run' 2023-06-05T14:05:05.8301520Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/commander-4.6.0/lib/commander/command.rb:187:in call'
2023-06-05T14:05:05.8301900Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/commander-4.6.0/lib/commander/command.rb:157:in run' 2023-06-05T14:05:05.8302650Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/commander-4.6.0/lib/commander/runner.rb:444:in run_active_command'
2023-06-05T14:05:05.8303170Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:124:in run!' 2023-06-05T14:05:05.8303600Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/commander-4.6.0/lib/commander/delegates.rb:18:in run!'
2023-06-05T14:05:05.8304090Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/pilot/lib/pilot/commands_generator.rb:167:in run' 2023-06-05T14:05:05.8304500Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/pilot/lib/pilot/commands_generator.rb:19:in start'
2023-06-05T14:05:05.8305010Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/fastlane/lib/fastlane/cli_tools_distributor.rb:115:in take_off' 2023-06-05T14:05:05.8305560Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/bin/fastlane:23:in <top (required)>'
2023-06-05T14:05:05.8305800Z 	from /usr/local/lib/ruby/gems/3.0.0/bin/fastlane:25:in load' 2023-06-05T14:05:05.8306050Z 	from /usr/local/lib/ruby/gems/3.0.0/bin/fastlane:25:in '
2023-06-05T14:05:05.8306540Z /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/spaceship/lib/spaceship/client.rb:952:in handle_error': Unauthorized Access (Spaceship::UnauthorizedAccessError) 2023-06-05T14:05:05.8307100Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/spaceship/lib/spaceship/client.rb:933:in block in send_request'
2023-06-05T14:05:05.8307570Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/spaceship/lib/spaceship/client.rb:688:in with_retry' 2023-06-05T14:05:05.8308010Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/spaceship/lib/spaceship/client.rb:929:in send_request'
2023-06-05T14:05:05.8308730Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/spaceship/lib/spaceship/client.rb:773:in request' 2023-06-05T14:05:05.8309290Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/spaceship/lib/spaceship/client.rb:500:in send_shared_login_request'
2023-06-05T14:05:05.8309850Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/spaceship/lib/spaceship/tunes/tunes_client.rb:130:in send_login_request' 2023-06-05T14:05:05.8310340Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/spaceship/lib/spaceship/client.rb:855:in do_login'
2023-06-05T14:05:05.8311190Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/spaceship/lib/spaceship/client.rb:394:in login' 2023-06-05T14:05:05.8311700Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/spaceship/lib/spaceship/client.rb:355:in login'
2023-06-05T14:05:05.8312120Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/spaceship/lib/spaceship/tunes/spaceship.rb:24:in login' 2023-06-05T14:05:05.8312620Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/spaceship/lib/spaceship/connect_api/client.rb:56:in login'
2023-06-05T14:05:05.8313110Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/spaceship/lib/spaceship/connect_api/spaceship.rb:85:in login' 2023-06-05T14:05:05.8313530Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/pilot/lib/pilot/manager.rb:36:in login'
2023-06-05T14:05:05.8314470Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/pilot/lib/pilot/manager.rb:19:in start' 2023-06-05T14:05:05.8314870Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/pilot/lib/pilot/build_manager.rb:17:in upload'
2023-06-05T14:05:05.8315400Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/pilot/lib/pilot/commands_generator.rb:67:in block (2 levels) in run' 2023-06-05T14:05:05.8316020Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/commander-4.6.0/lib/commander/command.rb:187:in call'
2023-06-05T14:05:05.8316480Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/commander-4.6.0/lib/commander/command.rb:157:in run' 2023-06-05T14:05:05.8316970Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/commander-4.6.0/lib/commander/runner.rb:444:in run_active_command'
2023-06-05T14:05:05.8317400Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:124:in run!' 2023-06-05T14:05:05.8317900Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/commander-4.6.0/lib/commander/delegates.rb:18:in run!'
2023-06-05T14:05:05.8318360Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/pilot/lib/pilot/commands_generator.rb:167:in run' 2023-06-05T14:05:05.8318800Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/pilot/lib/pilot/commands_generator.rb:19:in start'
2023-06-05T14:05:05.8319310Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/fastlane/lib/fastlane/cli_tools_distributor.rb:115:in take_off' 2023-06-05T14:05:05.8319710Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/bin/fastlane:23:in <top (required)>'
2023-06-05T14:05:05.8320010Z 	from /usr/local/lib/ruby/gems/3.0.0/bin/fastlane:25:in load' 2023-06-05T14:05:05.8320200Z 	from /usr/local/lib/ruby/gems/3.0.0/bin/fastlane:25:in '
2023-06-05T14:05:05.8441170Z ##[debug]Exit code 1 received from tool '/bin/bash'
2023-06-05T14:05:05.8447890Z ##[debug]STDIO streams have closed for tool '/bin/bash'
2023-06-05T14:05:05.8515090Z ##[error]Bash exited with code '1'.
2023-06-05T14:05:05.8525640Z ##[debug]Processed: ##vso[task.issue type=error;]Bash exited with code '1'.
2023-06-05T14:05:05.8526480Z ##[debug]task result: Failed
2023-06-05T14:05:05.8530100Z ##[debug]Processed: ##vso[task.complete result=Failed;done=true;]
2023-06-05T14:05:05.8532910Z ##[section]Finishing: Upload to TestFlight

2023-06-05T14:43:59.4723650Z [14:43:59]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
2023-06-05T14:44:01.9550470Z [14:44:01]: Sending anonymous analytics information
2023-06-05T14:44:01.9551550Z [14:44:01]: Learn more at https://docs.fastlane.tools/#metrics
2023-06-05T14:44:01.9555390Z [14:44:01]: No personal or sensitive data is sent.
2023-06-05T14:44:01.9556380Z [14:44:01]: You can disable this by adding `opt_out_usage` at the top of your Fastfile
2023-06-05T14:44:02.0273950Z [14:44:02]: Generating fastlane environment output, this might take a few seconds...
2023-06-05T14:44:07.7129030Z swift-driver version: 1.62.15 ✅ fastlane environment ✅
2023-06-05T14:44:07.7224810Z
2023-06-05T14:44:07.7326500Z ### Stack
2023-06-05T14:44:07.7373940Z
2023-06-05T14:44:07.7383630Z | Key                         | Value                                            |
2023-06-05T14:44:07.7403180Z | --------------------------- | ------------------------------------------------ |
2023-06-05T14:44:07.7403980Z | OS                          | 12.6.5                                           |
2023-06-05T14:44:07.7404670Z | Ruby                        | 3.0.6                                            |
2023-06-05T14:44:07.7405280Z | Bundler?                    | false                                            |
2023-06-05T14:44:07.7405940Z | Git                         | git version 2.40.1                               |
2023-06-05T14:44:07.7406850Z | Installation Source         | /usr/local/lib/ruby/gems/3.0.0/bin/fastlane      |
2023-06-05T14:44:07.7407510Z | Host                        | macOS 12.6.5 (21G531)                            |
2023-06-05T14:44:07.7408090Z | Ruby Lib Dir                |<EMAIL_ADDRESS>           |
2023-06-05T14:44:07.7409590Z | OpenSSL Version             | OpenSSL 1.1.1t  7 Feb 2023                       |
2023-06-05T14:44:07.7410210Z | Is contained                | false                                            |
2023-06-05T14:44:07.7410750Z | Is homebrew                 | false                                            |
2023-06-05T14:44:07.7411390Z | Is installed via Fabric.app | false                                            |
2023-06-05T14:44:07.7412010Z | Xcode Path                  | /Applications/Xcode_14.2.app/Contents/Developer/ |
2023-06-05T14:44:07.7412580Z | Xcode Version               | 14.2                                             |
2023-06-05T14:44:07.7413190Z | Swift Version               | 5.7.2                                            |
2023-06-05T14:44:07.7416230Z
2023-06-05T14:44:07.7416390Z
2023-06-05T14:44:07.7416660Z ### System Locale
2023-06-05T14:44:07.7416770Z
2023-06-05T14:44:07.7417310Z | Variable | Value       |   |
2023-06-05T14:44:07.7418080Z | -------- | ----------- | - |
2023-06-05T14:44:07.7418450Z | LANG     | en_US.UTF-8 | ✅ |
2023-06-05T14:44:07.7418840Z | LC_ALL   | en_US.UTF-8 | ✅ |
2023-06-05T14:44:07.7419850Z | LANGUAGE |             |   |
2023-06-05T14:44:07.7420300Z
2023-06-05T14:44:07.7420460Z
2023-06-05T14:44:07.7420620Z ### fastlane files:
2023-06-05T14:44:07.7420680Z
2023-06-05T14:44:07.7421950Z No Fastfile found
2023-06-05T14:44:07.7422040Z
2023-06-05T14:44:07.7422080Z
2023-06-05T14:44:07.7422530Z No Appfile found
2023-06-05T14:44:07.7422610Z
2023-06-05T14:44:07.7422650Z
2023-06-05T14:44:07.7422960Z ### fastlane gems
2023-06-05T14:44:07.7423020Z
2023-06-05T14:44:07.7423580Z | Gem      | Version | Update-Status |
2023-06-05T14:44:07.7423970Z | -------- | ------- | ------------- |
2023-06-05T14:44:07.7424330Z | fastlane | 2.213.0 | ✅ Up-To-Date  |
2023-06-05T14:44:07.7424400Z
2023-06-05T14:44:07.7424440Z
2023-06-05T14:44:07.7424640Z ### Loaded fastlane plugins:
2023-06-05T14:44:07.7424700Z
2023-06-05T14:44:07.7425130Z No plugins Loaded
2023-06-05T14:44:07.7425210Z
2023-06-05T14:44:07.7425250Z
2023-06-05T14:44:07.7425460Z Loaded gems
2023-06-05T14:44:07.7425530Z
2023-06-05T14:44:07.7425700Z | Gem                             | Version      |
2023-06-05T14:44:07.7426160Z | ------------------------------- | ------------ |
2023-06-05T14:44:07.7426340Z | did_you_mean                    | 1.5.0        |
2023-06-05T14:44:07.7426560Z | atomos                          | 0.1.3        |
2023-06-05T14:44:07.7426740Z | rexml                           | 3.2.5        |
2023-06-05T14:44:07.7426880Z | CFPropertyList                  | 3.0.6        |
2023-06-05T14:44:07.7427070Z | claide                          | 1.1.0        |
2023-06-05T14:44:07.7427200Z | colored2                        | 3.1.2        |
2023-06-05T14:44:07.7427390Z | nanaimo                         | 0.3.0        |
2023-06-05T14:44:07.7427800Z | xcodeproj                       | 1.22.0       |
2023-06-05T14:44:07.7427960Z | rouge                           | 2.0.7        |
2023-06-05T14:44:07.7428160Z | xcpretty                        | 0.3.0        |
2023-06-05T14:44:07.7428430Z | terminal-notifier               | 2.0.0        |
2023-06-05T14:44:07.7428880Z | unicode-display_width           | 1.8.0        |
2023-06-05T14:44:07.7429260Z | terminal-table                  | 1.8.0        |
2023-06-05T14:44:07.7429410Z | plist                           | 3.7.0        |
2023-06-05T14:44:07.7429620Z | addressable                     | 2.8.4        |
2023-06-05T14:44:07.7429860Z | multipart-post                  | 2.0.0        |
2023-06-05T14:44:07.7430080Z | word_wrap                       | 1.0.0        |
2023-06-05T14:44:07.7430270Z | optparse                        | 0.1.1        |
2023-06-05T14:44:07.7430510Z | tty-screen                      | 0.8.1        |
2023-06-05T14:44:07.7430820Z | tty-cursor                      | 0.7.1        |
2023-06-05T14:44:07.7431040Z | tty-spinner                     | 0.9.3        |
2023-06-05T14:44:07.7431510Z | artifactory                     | 3.0.15       |
2023-06-05T14:44:07.7432170Z | babosa                          | 1.0.4        |
2023-06-05T14:44:07.7432550Z | colored                         | 1.2          |
2023-06-05T14:44:07.7432950Z | highline                        | 2.0.3        |
2023-06-05T14:44:07.7433250Z | commander                       | 4.6.0        |
2023-06-05T14:44:07.7433620Z | excon                           | 0.99.0       |
2023-06-05T14:44:07.7433960Z | faraday-em_http                 | 1.0.0        |
2023-06-05T14:44:07.7434210Z | faraday-em_synchrony            | 1.0.0        |
2023-06-05T14:44:07.7434530Z | faraday-excon                   | 1.1.0        |
2023-06-05T14:44:07.7434770Z | faraday-httpclient              | 1.0.1        |
2023-06-05T14:44:07.7435090Z | faraday-multipart               | 1.0.4        |
2023-06-05T14:44:07.7435400Z | faraday-net_http                | 1.0.1        |
2023-06-05T14:44:07.7435640Z | faraday-net_http_persistent     | 1.2.0        |
2023-06-05T14:44:07.7436220Z | faraday-patron                  | 1.0.0        |
2023-06-05T14:44:07.7436460Z | faraday-rack                    | 1.0.0        |
2023-06-05T14:44:07.7436780Z | faraday-retry                   | 1.0.3        |
2023-06-05T14:44:07.7437000Z | ruby2_keywords                  | 0.0.5        |
2023-06-05T14:44:07.7437140Z | faraday                         | 1.10.3       |
2023-06-05T14:44:07.7437800Z | unf_ext                         | <IP_ADDRESS>      |
2023-06-05T14:44:07.7437930Z | unf                             | 0.1.4        |
2023-06-05T14:44:07.7438140Z | domain_name                     | 0.5.20190701 |
2023-06-05T14:44:07.7438460Z | http-cookie                     | 1.0.5        |
2023-06-05T14:44:07.7438700Z | faraday-cookie_jar              | 0.0.7        |
2023-06-05T14:44:07.7438930Z | faraday_middleware              | 1.2.0        |
2023-06-05T14:44:07.7439070Z | fastimage                       | 2.2.6        |
2023-06-05T14:44:07.7439260Z | gh_inspector                    | 1.1.3        |
2023-06-05T14:44:07.7439680Z | json                            | 2.5.1        |
2023-06-05T14:44:07.7439830Z | mini_magick                     | 4.12.0       |
2023-06-05T14:44:07.7440620Z | naturally                       | 2.2.1        |
2023-06-05T14:44:07.7440760Z | rubyzip                         | 2.3.2        |
2023-06-05T14:44:07.7440960Z | security                        | 0.1.3        |
2023-06-05T14:44:07.7441300Z | xcpretty-travis-formatter       | 1.0.1        |
2023-06-05T14:44:07.7441460Z | dotenv                          | 2.8.1        |
2023-06-05T14:44:07.7441670Z | bundler                         | 2.4.13       |
2023-06-05T14:44:07.7441810Z | simctl                          | 1.6.10       |
2023-06-05T14:44:07.7441990Z | jwt                             | 2.7.0        |
2023-06-05T14:44:07.7442180Z | uber                            | 0.1.0        |
2023-06-05T14:44:07.7442460Z | declarative                     | 0.0.20       |
2023-06-05T14:44:07.7442800Z | trailblazer-option              | 0.1.2        |
2023-06-05T14:44:07.7442970Z | representable                   | 3.2.0        |
2023-06-05T14:44:07.7443390Z | retriable                       | 3.1.2        |
2023-06-05T14:44:07.7443580Z | mini_mime                       | 1.1.2        |
2023-06-05T14:44:07.7443720Z | memoist                         | 0.16.2       |
2023-06-05T14:44:07.7443920Z | multi_json                      | 1.15.0       |
2023-06-05T14:44:07.7444050Z | os                              | 1.1.4        |
2023-06-05T14:44:07.7444240Z | signet                          | 0.17.0       |
2023-06-05T14:44:07.7444420Z | googleauth                      | 1.5.2        |
2023-06-05T14:44:07.7444560Z | httpclient                      | 2.8.3        |
2023-06-05T14:44:07.7444920Z | webrick                         | 1.8.1        |
2023-06-05T14:44:07.7445480Z | google-apis-core                | 0.11.0       |
2023-06-05T14:44:07.7446040Z | google-apis-playcustomapp_v1    | 0.13.0       |
2023-06-05T14:44:07.7446420Z | google-apis-androidpublisher_v3 | 0.42.0       |
2023-06-05T14:44:07.7447060Z | google-cloud-env                | 1.6.0        |
2023-06-05T14:44:07.7447740Z | google-cloud-errors             | 1.3.1        |
2023-06-05T14:44:07.7448110Z | google-cloud-core               | 1.6.0        |
2023-06-05T14:44:07.7448390Z | google-apis-iamcredentials_v1   | 0.17.0       |
2023-06-05T14:44:07.7448740Z | google-apis-storage_v1          | 0.19.0       |
2023-06-05T14:44:07.7448890Z | rake                            | 13.0.3       |
2023-06-05T14:44:07.7449310Z | digest-crc                      | 0.6.4        |
2023-06-05T14:44:07.7449850Z | google-cloud-storage            | 1.44.0       |
2023-06-05T14:44:07.7450210Z | emoji_regex                     | 3.2.3        |
2023-06-05T14:44:07.7450450Z | jmespath                        | 1.6.2        |
2023-06-05T14:44:07.7450710Z | aws-partitions                  | 1.765.0      |
2023-06-05T14:44:07.7451030Z | aws-eventstream                 | 1.2.0        |
2023-06-05T14:44:07.7451320Z | aws-sigv4                       | 1.5.2        |
2023-06-05T14:44:07.7451590Z | aws-sdk-core                    | 3.172.0      |
2023-06-05T14:44:07.7452130Z | aws-sdk-kms                     | 1.64.0       |
2023-06-05T14:44:07.7452390Z | aws-sdk-s3                      | 1.122.0      |
2023-06-05T14:44:07.7452600Z | set                             | 1.0.1        |
2023-06-05T14:44:07.7453250Z | public_suffix                   | 5.0.1        |
2023-06-05T14:44:07.7453410Z | forwardable                     | 1.3.2        |
2023-06-05T14:44:07.7453590Z | logger                          | 1.4.3        |
2023-06-05T14:44:07.7453730Z | pathname                        | 0.1.0        |
2023-06-05T14:44:07.7453920Z | shellwords                      | 0.1.0        |
2023-06-05T14:44:07.7454090Z | cgi                             | 0.2.2        |
2023-06-05T14:44:07.7454230Z | date                            | 3.1.3        |
2023-06-05T14:44:07.7454420Z | timeout                         | 0.1.1        |
2023-06-05T14:44:07.7454560Z | stringio                        | 3.0.1        |
2023-06-05T14:44:07.7454750Z | securerandom                    | 0.1.0        |
2023-06-05T14:44:07.7455090Z | uri                             | 0.10.2       |
2023-06-05T14:44:07.7455280Z | ipaddr                          | 1.2.2        |
2023-06-05T14:44:07.7455480Z | openssl                         | 2.2.2        |
2023-06-05T14:44:07.7455620Z | digest                          | 3.0.0        |
2023-06-05T14:44:07.7455940Z | io-nonblock                     | 0.1.0        |
2023-06-05T14:44:07.7456230Z | io-wait                         | 0.2.0        |
2023-06-05T14:44:07.7456380Z | zlib                            | 2.0.0        |
2023-06-05T14:44:07.7456570Z | resolv                          | 0.2.1        |
2023-06-05T14:44:07.7456710Z | time                            | 0.1.1        |
2023-06-05T14:44:07.7456990Z | open-uri                        | 0.1.0        |
2023-06-05T14:44:07.7457190Z | mutex_m                         | 0.1.1        |
2023-06-05T14:44:07.7457450Z | net-protocol                    | 0.1.1        |
2023-06-05T14:44:07.7457660Z | ostruct                         | 0.3.1        |
2023-06-05T14:44:07.7457790Z | english                         | 0.7.1        |
2023-06-05T14:44:07.7458190Z | erb                             | 2.2.0        |
2023-06-05T14:44:07.7458380Z | strscan                         | 3.0.1        |
2023-06-05T14:44:07.7458530Z | abbrev                          | 0.1.0        |
2023-06-05T14:44:07.7458840Z | io-console                      | 0.5.7        |
2023-06-05T14:44:07.7458990Z | tempfile                        | 0.1.1        |
2023-06-05T14:44:07.7459200Z | delegate                        | 0.2.0        |
2023-06-05T14:44:07.7459380Z | fileutils                       | 1.5.0        |
2023-06-05T14:44:07.7459520Z | tmpdir                          | 0.1.2        |
2023-06-05T14:44:07.7459700Z | base64                          | 0.1.0        |
2023-06-05T14:44:07.7459840Z | singleton                       | 0.1.1        |
2023-06-05T14:44:07.7460500Z | net-http                        | 0.1.1        |
2023-06-05T14:44:07.7460710Z | open3                           | 0.1.1        |
2023-06-05T14:44:07.7460850Z | nkf                             | 0.1.0        |
2023-06-05T14:44:07.7461230Z | prettyprint                     | 0.1.1        |
2023-06-05T14:44:07.7461390Z | pp                              | 0.2.1        |
2023-06-05T14:44:07.7461580Z | find                            | 0.1.0        |
2023-06-05T14:44:07.7461760Z | yaml                            | 0.1.1        |
2023-06-05T14:44:07.7461900Z | psych                           | 3.3.2        |
2023-06-05T14:44:07.7462080Z
2023-06-05T14:44:07.7462130Z
2023-06-05T14:44:07.7462170Z
2023-06-05T14:44:07.7462510Z generated on: 2023-06-05
2023-06-05T14:44:07.7462670Z
2023-06-05T14:44:07.7463130Z [14:44:07]: Take notice that this output may contain sensitive information, or simply information that you don't want to make public.
2023-06-05T14:44:07.7463610Z [14:44:07]: Open https://github.com/fastlane/fastlane/issues/new to submit a new issue ✅
2023-06-05T14:44:09.3282990Z [14:44:09]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
2023-06-05T14:44:11.6754580Z INFO [2023-06-05 14:44:11.67]: Login to App Store Connect ()
2023-06-05T14:44:11.6837330Z Reading keychain entry, because either user or password were empty
2023-06-05T14:44:12.2471950Z The login credentials for '' seem to be wrong
2023-06-05T14:44:12.2516840Z The password was taken from the environment variable
2023-06-05T14:44:12.2594920Z Please make sure it is correct
2023-06-05T14:44:12.2607670Z
2023-06-05T14:44:12.2610540Z Looking for related GitHub issues on fastlane/fastlane...
2023-06-05T14:44:12.2610960Z Search query: The request could not be completed because:
2023-06-05T14:44:12.2611640Z 	Invalid username and password combination. Used '' as the username.
2023-06-05T14:44:12.2611810Z
2023-06-05T14:44:12.2612270Z URL: https://api.github.com/search/issues?q=The request could not be completed because%3A
	Invalid username and password combination. Used '%27%20as%20the%20username.+repo:fastlane/fastlane
2023-06-05T14:44:12.4100250Z Found no similar issues. To create a new issue, please visit:
2023-06-05T14:44:12.4100980Z https://github.com/fastlane/fastlane/issues/new
2023-06-05T14:44:12.4101550Z Run `fastlane env` to append the fastlane environment to your issue
2023-06-05T14:44:12.4102800Z /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.213.0/spaceship/lib/spaceship/client.rb:511:in `rescue in send_shared_login_request': \e[31m[!] The request could not be completed because: (Spaceship::InvalidUserCredentialsError)


BUG -  Generation of sap-fe-mockserver middleware configuration files, does not append annotations to the configuration

Description
When generating a Fiori Elements application, multiple yaml files are generated. In those yaml files, the sap-fe-mockserver is configured. Unfortunately, in the configuration the annotations are configured with an empty array.
This empty array creates an issue if you run the local karma or do run the azure pipeline. The mockserver does not find the annotations, which results e.g. in a empty table. This effect cannot be seen running OPA5 tests in Business Application Studio. This makes the life from an application developer hard.
Solution
Please add the configuration to the annotation.xml when generating according to the following documentation.
https://github.com/SAP/open-ux-odata/tree/main/packages/ui5-middleware-fe-mockserver#usage
Expected results
Example Correct Entry:
- name: sap-fe-mockserver
  mountPath: /
  beforeMiddleware: csp
  configuration:
    annotations:
      - localPath: './webapp/localService/UI_MANAGEREPAIROBJECTS_VAN.xml'
        urlPath: '/sap/opu/odata/IWFND/CATALOGSERVICE;v=2/Annotations*'
    services:
      - urlPath: '/sap/opu/odata/sap/UI_MANAGEREPAIROBJECTS'
        metadataPath: './webapp/localService/metadata.xml'
        mockdataPath: './webapp/localService/data'

Actual results
    - name: sap-fe-mockserver
      beforeMiddleware: csp
      configuration:
        mountPath: /
        services:
          - urlPath: /sap/opu/odata/sap/SEPMRA_PROD_MAN
            metadataPath: ./webapp/localService/metadata.xml
            mockdataPath: ./webapp/localService/data
            generateMockData: true
        annotations: []

Screenshots
If applicable, add screenshots to help explain the problem.
Version/Components/Environment
Add any other context about the problem here
OS:

[X] Mac OS
[X] Windows
[ ] Other

Root Cause Analysis
Problem
{describe the problem}
Fix
{describe the fix}
Why was it missed
{Some explanation why this issue might have been missed during normal development/testing cycle}
How can we avoid this
{if we don’t want to see this type of issues anymore what we should do to prevent}

Issue found when testing, if a ui5-mock.yaml already exists, the annotations are not being appended when the command the following command is executed;
npx --yes @sap-ux/create@latest add mockserver-config

Generated an App with sample OData V2:

When running Add Mockserver Config from Application Info page on a newly generated App containing ui5-local.yaml, ui5-mock.yaml and ui5.yaml. The ui5-mock.yaml is modified with new annotation changes (see screenshot).
If ui5-mock.yaml doesn't exist , a new ui5-mock.yaml  is created based off ui5.yaml
If ui5-mock.yaml and ui5.yaml doesn't exist, creates a fresh ui5-mock.yaml

I've validated the two issues identified;

annotations are now added when a new project is created
appending annotations if ui5-mock.yaml already exista and the mock server config is re-run again

Happy for this issue to be closed.


dynamic terminal output of exec process not showing up

If I do something like exec('npm install'), I don't see the spinner thing that npm shows in the console normally.  Or for instance download progress meters that some commands print to the console.  Is there a way to get them to show up with shelljs?

+1 same question

This is a duplicate of #251.

(Technically, #251 is a duplicate of this one :stuck_out_tongue_winking_eye:)
I think this would also be a good place to discuss the ability to read the stdout buffer line-by-line.
For example, with exec('...', { silent: false }); within a gulp stream, you'll get this:
nathanbrauer@macthan:~/Web/git/Component-Core$ gulp compile:styles
[18:33:08] Using gulpfile ~/Web/git/Component-Core/gulpfile.js
[18:33:08] Starting 'compile:styles'...
    write build/brand.css (0.713s)

    write build/brand.css.map

[18:33:10] Finished 'compile:styles' after 1.17 s

Ideally, each of the lines (starting with write build/brand.css...) would also conform to gulp's logging (gutils.log(...)).  But the only way to do that, currently, is to wait for the entire buffer to end, then parse every line on your own.  This means that the timestamps are completely wrong which makes it pointless... (but at least it's prettier :wink:):
var output = exec('...', { silent: false }).output,
	output_lines = output.replace(/^\s+|\s+$/,'').split(/[\n\r]+/),// Trims the output and returns it split into an array of lines
	log_line;
if (output) {
	for (log_line = 0; log_line < output_lines.length; ++log_line) {
		gutil.log(log_indent,output_lines[log_line]);
	}
}

Here's a real example: https://github.com/Marketera/gulp-composer/blob/master/index.js#L28

Ideally we'd be able to do something along the lines of....
var cmd = exec('composer install', {
    silent: true,
    onPrint: function(line){
        gutil.log(line);
    }
});

// ...which is basically the same as:
var cmd = exec('composer install', {
    silent: true,
    onPrint: gutil.log
});

// ...the default behavior, essentially being:
var cmd = exec('composer install', {
    //...
    onPrint: console.log
});

@nathanbrauer I think this could be do-able. This would be lower on the priority list. I think it would be done fairly differently from the colored text, however. But I can write up a PR along the lines of the onPrint implementation. Would you be able to copy-paste this as a separate issue?

@cancerberoSgx, let's continue discussion here.

OK, I'm pasting my initial comment with a solution here so we don't miss it:
Hello, good project!
I'm having trouble with .exec/.execAsync, particularly when invoking command line tools that uses terminal colors or terminal advanced features like cli-spinner, etc.
By default, shelljs will create a new buffer for child processes and executing command line tools that use for example cli-spinner will just break.
PLEASE provide a .exe API so I can control this, for example like the following one. :
var child_process = require('child_process');
var exec = function(cmd, args, callback)
{
    var child = child_process.spawn(cmd, args, {
        stdio: [
            0, // use parents stdin for child
            1, // use parent's stdout stream - IMPORTANT if we dont do this things like the spinner will break the automation.
            2  // fs.openSync('err.out', 'w') // direct child's stderr to a file
        ]
    });
    child.on('close', function()
    {
        callback.apply(null, arguments);
    });
    return child;
};

Just ran into this myself, and would mean poor ergonomics for the utility I'm building. What would be required in order to add this feature?

This is tricky to get right. Node does not offer APIs to emulate a TTY while also capturing output.
If you don't need to capture output, try:
child_process.execFileSync('cmd', [ 'arg1', 'arg2', 'arg3' ], { stdio: 'inherit' });

as a workaround, I managed to have my dynamic terminal using spawn with stdio
  const {spawn} = require('child_process');

  spawn(
    'my-command',
    ['any', 'options'],
    {stdio: [process.stdin, process.stdout, process.stderr]}
  );


Need simple hook when navigating away from a screen

I have a screen which gathers input from the user.  I need a hook so that I can persist the changes when they hit the back button.  What's the simplest way?  I'm using StackNavigator.

Nevermind.  componentWillUnmount() is what I want.  (I'm new to react)


Connection refused on registry.ollama.ai

What is the issue?
Hi,
Since this morning I get a Connection refused error when trying to pull models:
ollama pull nomic-embed-text:137m-v1.5-fp16
pulling manifest
Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/nomic-embed-text/manifests/137m-v1.5-fp16": dial tcp <IP_ADDRESS>:443: connect: connection refused
I'm behind a proxy which worked well last week (http_proxy and https_proxy env variables are correct)
With my browser (behind the same proxy) I get this:
https://registry.ollama.ai/v2/library/nomic-embed-text/manifests/137m-v1.5-fp16
{"schemaVersion":2,"mediaType":"application/vnd.docker.distribution.manifest.v2+json","config":{"digest":"sha256:31df23ea7daa448f9ccdbbcecce6c14689c8552222b80defd3830707c0139d4f","mediaType":"application/vnd.docker.container.image.v1+json","size":420},"layers":[{"digest":"sha256:970aa74c0a90ef7482477cf803618e776e173c007bf957f635f1015bfcfef0e6","mediaType":"application/vnd.ollama.image.model","size":274290656},{"digest":"sha256:c71d239df91726fc519c6eb72d318ec65820627232b2f796219e87dcf35d0ab4","mediaType":"application/vnd.ollama.image.license","size":11357},{"digest":"sha256:ce4a164fc04605703b485251fe9f1a181688ba0eb6badb80cc6335c0de17ca0d","mediaType":"application/vnd.ollama.image.params","size":17}]}
I updated Ollama this morning to 0.2.7, the script worked well.
Did I miss something?
Thanks
JC
OS
Linux
GPU
No response
CPU
Intel
Ollama version
0.2.7

Hi,
I upgrade to Ollama 0.2.8, it did not change.
What is weird is that with curl from the same machine, it seems to work:
`curl "https://registry.ollama.ai/v2/library/nomic-embed-text/manifests/137m-v1.5-fp16"
`{"schemaVersion":2,"mediaType":"application/vnd.docker.distribution.manifest.v2+json","config":{"digest":"sha256:31df23ea7daa448f9ccdbbcecce6c14689c8552222b80defd3830707c0139d4f","mediaType":"application/vnd.docker.container.image.v1+json","size":420},"layers":[{"digest":"sha256:970aa74c0a90ef7482477cf803618e776e173c007bf957f635f1015bfcfef0e6","mediaType":"application/vnd.ollama.image.model","size":274290656},{"digest":"sha256:c71d239df91726fc519c6eb72d318ec65820627232b2f796219e87dcf35d0ab4","mediaType":"application/vnd.ollama.image.license","size":11357},{"digest":"sha256:ce4a164fc04605703b485251fe9f1a181688ba0eb6badb80cc6335c0de17ca0d","mediaType":"application/vnd.ollama.image.params","size":17}]}

OK. I finally found out: for an unknown reason I had to add http/s_proxy env variables to the /etc/systemd/system/ollama.service file. It did work without this last week.


Added DLC items from TGA tables

Hey, I converted the TGA tables for the DLC items so they can be modified here
I know you mentioned here that you'll need to think about how to gate DLC content to avoid people getting banned, but I figured somebody might find this useful in the meantime.

Could you compile this into an executable?

Functional on my side. I'm now digging into bosses event id's.
er-save-editor.zip here is the executable @oospack

nice! If you still didn't figure it out, share it and I'll also take a look at it.
btw, I submitted a PR #52 which includes this one and adds the ability to modify dlc related stats.

Idk, works for me have no idea why

@0xRyN Am I just stupid or why does the executable crash when I try to open it?

@0xRyN Happened to me as well. I don't have any knowledge of rust whatsoever. But I feel it's erroring out while fetching the icon.png file.
PS C:\Users\rajath\Downloads\ER-Save-Editor-master> .\er-save-editor.exe
thread 'main' panicked at src/main.rs:31:40:
Failed to get image data
stack backtrace:
   0:     0x7ff7413a07c8 - <unknown>
   1:     0x7ff7413c04e9 - <unknown>
   2:     0x7ff74139ca81 - <unknown>
   3:     0x7ff7413a05a6 - <unknown>
   4:     0x7ff7413a26a8 - <unknown>
   5:     0x7ff7413a2317 - <unknown>
   6:     0x7ff7413a2bd8 - <unknown>
   7:     0x7ff7413a2a97 - <unknown>
   8:     0x7ff7413a113f - <unknown>
   9:     0x7ff7413a2748 - <unknown>
  10:     0x7ff74147ca04 - <unknown>
  11:     0x7ff7413be51d - <unknown>
  12:     0x7ff74147c9ce - <unknown>
  13:     0x7ff7408754ed - <unknown>
  14:     0x7ff7409e27b5 - <unknown>
  15:     0x7ff7409750d3 - <unknown>
  16:     0x7ff740961396 - <unknown>
  17:     0x7ff7407b70fc - <unknown>
  18:     0x7ff741398efe - <unknown>
  19:     0x7ff7407b70ca - <unknown>
  20:     0x7ff7409e3d39 - <unknown>
  21:     0x7ff74147a320 - <unknown>
  22:     0x7ffbb800257d - BaseThreadInitThunk
  23:     0x7ffbb968af28 - RtlUserThreadStart

@0xRyN Am I just stupid or why does the executable crash when I try to open it?

@0xRyN Happened to me as well. I don't have any knowledge of rust whatsoever. But I feel it's erroring out while fetching the icon.png file.

Yeah it's a problem with the icon, this line of code to be precise. I'm not a rust developer, so I don't know how to fix it. Running the .exe straight from the zip file works for me though
#[derive(RustEmbed)]
#[folder = "icon/"]
struct Asset;

let image = Asset::get("icon.png").expect("Failed to get image data").data;

I know you mentioned here that you'll need to think about how to gate DLC content to avoid people getting banned, but I figured somebody might find this useful in the meantime.

If there's no good way to figure out whether the user has the DLC active just from the save alone, you could always just ask the user whether to show DLC's related stats and items in the editor.

Yeah it's a problem with the icon, this line of code to be precise. I'm not a rust developer, so I don't know how to fix it. Running the .exe straight from the zip file works for me though
#[derive(RustEmbed)]
#[folder = "icon/"]
struct Asset;

let image = Asset::get("icon.png").expect("Failed to get image data").data; // Exception here

Did you upload a debug build? If so, the icon is not embedded within the binary, and it'll look for it relative to the binary path.

Yeah it's a problem with the icon, this line of code to be precise. I'm not a rust developer, so I don't know how to fix it. Running the .exe straight from the zip file works for me though
#[derive(RustEmbed)]
#[folder = "icon/"]
struct Asset;

let image = Asset::get("icon.png").expect("Failed to get image data").data; // Exception here

@0xRyN
Did you upload a debug build? If so, the icon is not embedded within the binary, and it'll look for it relative to the binary path.
It should work otherwise.

@nozwock I just ran cargo build iirc, im not familiar with Rust / Cargo. What would be the solution ?

@0xRyN
cargo build --release

This will build it in release mode, the binary then should have the icon embedded within itself.

Is the editor working for Playstation saves again, everytime I import ps
save the exe just closes/crashes, I know I'm not alone in this
On Tue, Jul 16, 2024, 12:31 AM nozwock @.***> wrote:

I know you mentioned here
https://github.com/ClayAmore/ER-Save-Editor/pull/33#issuecomment-2181822360
that you'll need to think about how to gate DLC content to avoid people
getting banned, but I figured somebody might find this useful in the
meantime.
If there's no good way to figure out whether the user has the DLC active
just from the save alone, you could always just ask the user whether to
show DLC's related stats and items in the editor.
—
Reply to this email directly, view it on GitHub
https://github.com/ClayAmore/ER-Save-Editor/pull/49#issuecomment-2229998986,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJ2VSEJYCKMLZV2VF6MCJWLZMSO33AVCNFSM6AAAAABJ6OZDV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRZHE4TQOJYGY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@twp2000 You may try this, https://github.com/klarkyson/ER-Save-Editor/releases/

Yeah I did, still crashes for some reason :/ that's why I tried doing th
coding thing and exporting the zip to .exe and couldn't figure out the
process nor was youtube any help :/
On Tue, Jul 16, 2024, 1:59 PM nozwock @.***> wrote:

@twp2000 https://github.com/twp2000 You may try this,
https://github.com/klarkyson/ER-Save-Editor/releases/
—
Reply to this email directly, view it on GitHub
https://github.com/ClayAmore/ER-Save-Editor/pull/49#issuecomment-2231500075,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJ2VSEPMCRNXJ37UHMQT3RDZMVNQJAVCNFSM6AAAAABJ6OZDV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZRGUYDAMBXGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

@twp2000 You're not on the latest version of ER, are you? Because they're not supported yet (1.12.3/1.12.4).

That would be why then cause yeah my games updated and I got the dlc
On Tue, Jul 16, 2024, 3:21 PM nozwock @.***> wrote:

@twp2000 https://github.com/twp2000 You're not on the latest version of
ER, are you? Because they're not supported yet (1.12.3/1.12.4).
—
Reply to this email directly, view it on GitHub
https://github.com/ClayAmore/ER-Save-Editor/pull/49#issuecomment-2231671396,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJ2VSELSKL4IHLPQ467PYRTZMVXC7AVCNFSM6AAAAABJ6OZDV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZRGY3TCMZZGY
.
You are receiving this because you were mentioned.Message ID:
@.***>


Component as stateless functions

https://facebook.github.io/react/docs/reusable-components.html#stateless-functions
Use them once we figure out how to use them with shouldComponentUpdate check.

From tail of doc you refs:

In an ideal world, most of your components would be stateless functions because in the future we’ll also be able to make performance optimizations specific to these components by avoiding unnecessary checks and memory allocations. This is the recommended pattern, when possible.

So using this pattern will be good choice where sensible.
However Babel 5.8.23 and newer include some new optimizations I'm not sure if you know about.
From React v0.14 Release Candidate blog post:

React now supports two compiler optimizations that can be enabled in Babel 5.8.23 and newer. Both of these transforms should be enabled only in production (e.g., just before minifying your code) because although they improve runtime performance, they make warning messages more cryptic and skip important checks that happen in development mode, including propTypes.
Inlining React elements: The optimisation.react.inlineElements transform converts JSX elements to object literals like {type: 'div', props: ...} instead of calls to React.createElement.
Constant hoisting for React elements: The optimisation.react.constantElements transform hoists element creation to the top level for subtrees that are fully static, which reduces calls to React.createElement and the resulting allocations. More importantly, it tells React that the subtree hasn’t changed so React can completely skip it when reconciling.

@steida

Use them once we figure out how to use them with shouldComponentUpdate check.

I bet recompose is not an option then?

@langpavel Both these optimizations are already enabled in Este.

@cbioley I am aware of recompose, but I am waiting for more general approach, ideally from Facebook.

@steida Are you sure? I cannot find the lines...

@langpavel
"babel-plugin-transform-react-constant-elements": "^6.3.13",
"babel-plugin-transform-react-inline-elements": "^6.3.13",

Oh, sorry, I see


Guess version number from URL

Source tarballs include the version number in the file name, e.g.
http://downloads.xiph.org/releases/ogg/libogg-1.3.4.tar.xz

Looks good, thanks for the PR! Some requests:

Could you also add a unit test in ./tests/unit, similar to the version_from_git_tag.cmake test? This will prevent another PR accidentally breaking the feature.
Support for GitHub style releases would also be nice. They have a  https://github.com/<user>/<name>/releases/download/<version_tag>/<filename> schema.

Looks good, thanks for the PR! Some requests:

Could you also add a unit test in ./tests/unit, similar to the version_from_git_tag.cmake test? This will prevent another PR accidentally breaking the feature.
Support for GitHub style releases would also be nice. They have a  https://github.com/<user>/<name>/releases/download/<version_tag>/<filename> schema.


Pandas Indexing Error

References #10
Currently, the DataManager DataFrame is throwing an indexNotFound exception.
It should parse the input, generate a relatedness matrix, and return it.

{t:60}


The debug result is different with go run result ( using unsafe. Pointer, got []byte cap = 0 and len >0 )

What version of Go are you using (go version)?

$ go version
go version go1.13.9 darwin/amd64

Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN="/xxx/go/bin"
GOCACHE="/xxx/Library/Caches/go-build"
GOENV="/xxx/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=" -mod="
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/xxx/go"
GOPRIVATE=""
GOPROXY="https://goproxy.cn/"
GOROOT="/xxx/.g/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/xxx/.g/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/secret/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/3p/qnjdkh4j6z1f3g1rnbrjzsmm0000gn/T/go-build668244624=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

Debug using delve
package main

import (
   "unicode/utf8"
   "unsafe"
)

func main() {
   b := stringToBytes("模板ID")
   println(len(b))
   println(cap(b))
   r, width := utf8.DecodeRune(b[6:])
   println(r)
   println(width)
   println(b[0:5])
}

func stringToBytes(s string) []byte {
   return *(*[]byte)(unsafe.Pointer(&s))
}

Run directly result
GOROOT=/xxx/.g/versions/1.13.9 #gosetup
GOPATH=/xxx/go #gosetup
/xxx/.g/versions/1.13.9/bin/go build -i -o /xxx/GolandProjects/x/bin/go_build_main_go /xxx/GolandProjects/x/cmd/main.go #gosetup
/xxx/GolandProjects/x/bin/go_build_main_go #gosetup
8
824633993168
73
1
[5/824633993168]0x107187a

debug result
GOROOT=/xxx/.g/versions/1.13.9 #gosetup
GOPATH=/xxx/go #gosetup
/xxx/.g/versions/1.13.9/bin/go build -o /xxx/GolandProjects/x/bin/go_build_main_go -gcflags "all=-N -l" /xxx/GolandProjects/x/cmd/main.go #gosetup
/Applications/GoLand.app/Contents/plugins/go/lib/dlv/mac/dlv --listen=localhost:65499 --headless=true --api-version=2 --check-go-version=false --only-same-user=false exec /xxx/GolandProjects/x/bin/go_build_main_go -- #gosetup
API server listening at: <IP_ADDRESS>:65499
debugserver-@(#)PROGRAM:LLDB  PROJECT:lldb-1103.0.22
 for x86_64.
Got a connection, launched process /xxx/GolandProjects/x/bin/go_build_main_go (pid = 28332).
8
0
65533
1
panic: runtime error: slice bounds out of range [:5] with capacity 0

goroutine 1 [running]:
main.main()
        /xxx/GolandProjects/x/cmd/main.go:15 +0x1c2
Exiting.

What did you expect to see?

The Result same with run directly
The unsafe.Pointer didnt return []byte with cap = 0 and len > 0

What did you see instead?

The debug result is different with run directly result
I got a []byte with cap = 0 and len > 0

I submited an issue on delve, somebody say its not the delve's problem，Im confused
https://github.com/go-delve/delve/issues/2115

Your code is not sound, you cannot convert a string to a []byte safely.
I'm going to close this issue as it does not seem like there is a bug in Go. Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
For asking questions, see:

Stack Overflow with questions tagged "go"

The Go Forum, a web-based forum

Gophers Slack, use the invite app for access. The #general channel is a good starting point.

Go Community on Hashnode with questions and posts tagged with "go"

The golang-nuts mailing list

IRC channel #go-nuts on Freenode


Expose formatter options and change default for spaces from tabs to spaces

The CQL Formatter defines several options internally, but they are not exposed as publicly accessible properties on the formatter. These options should be exposed as properties, and then the command-line access should provide a way to set them from the command-line.
In particular, the option to use tabs vs spaces needs to be available, and the default for the behavior should be changed to use spaces rather than tabs.

Changing the default behavior in this case addresses the requirement, so I'm not exposing the options right now.

This feature is included in release 1.2.19


Update for latest version of rubocop (0.36.0)

Change a few things, per Rubocop:

Set variable values from conditional
Indention updates to match
Convert "else ... if" to "elsif"
Use casecmp over downcase

:+1: lgtm


jadx: 1.4.5 -> 1.4.6

Description of changes
Changelog: https://github.com/skylot/jadx/releases/tag/v1.4.6
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 221401 run on aarch64-darwin 1

2 packages built:

apkleaks
jadx


Plushies can now have pAIs stuffed into them to make your companion even better!

About the PR
I added a slot to plushies which can contain pAIs and only pAIs.
Why / Balance
I thought it would be really neat.
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog
:cl:

add: Plushies now have some space inside where you can insert a pAI, for the ultimate companion.

best change ever

does this also apply to the PAI syndicate? If yes, then this is a funny disguise

this is a funny disguise for the PAI syndicate

it does apply the the syndicate pAI

Finally, a true companion :)

so I have no idea why the check failed. Need some help with that

add a container for it too

I think it should just have a 2x1 inventory, so you can hide other small items like c4 also. And maybe require a sharp item to access it.

i feel like this would be better if you had to cut it open or something, like was suggested. Every plushie having a slot in the verb menu that is only used for PAIs is kinda strange. It should definitely be expanded to fit any small item.

alright then, I'll have to see how I can make it where you have to cut it. And then I can change it to just have like a 2x1 storage or something.

I agree that it would be interested if you had to interact with the plushie with a sharp object first, and I also believe it should be a general small storage space as opposed to only allowing pAIs, but this is a fantastic use case plushie-storage.

additionally make it so when inserting a mind container it transfers mind to the plushie :trollface:

additionally make it so when inserting a mind container it transfers mind to the plushie :trollface:

Just stuck a plushie that can only Weh!

i feel like this would be better if you had to cut it open or something, like was suggested. Every plushie having a slot in the verb menu that is only used for PAIs is kinda strange. It should definitely be expanded to fit any small item.

hand a lizard plushie with a remote explosive grenade to a lizard

So I agree with emo on how it should work, but I honestly don't know how to do that. It's beyond the scope of what I know how to do right now. So if someone else wants to figure it out or if someone wants to try and help me out with it I'd love that but for now I'm just at a standstill.

So I agree with emo on how it should work, but I honestly don't know how to do that. It's beyond the scope of what I know how to do right now. So if someone else wants to figure it out or if someone wants to try and help me out with it I'd love that but for now I'm just at a standstill.

using any sharp object (similar to “butcher”) will start a doafter where the entity now shows storage. This storage will be 2x3 and cannot hold any objects (blacklist) that hold a tag determining if they are “sharp” or not. You can then close it up again (not sure how yet, probably add a new entity like a sowing needle or something. Maybe more simply just an action.) This then preserves the item inside the object as it is still a container but you cannot open it up.
This is my idea anyway.

it's not that I don't know how to do it in concept, but rather that I can't understand the code. I thought I knew C# and I did spend some time learning it but any time I look at the code in this project it's like reading hieroglyphs, and I'm not sure where or how to start getting it.

So I agree with emo on how it should work, but I honestly don't know how to do that. It's beyond the scope of what I know how to do right now. So if someone else wants to figure it out or if someone wants to try and help me out with it I'd love that but for now I'm just at a standstill.
Edit: when I posted this comment my github hadn't refreshed and I completely missed TheShuEd's review, it's not that I meant to ignore it or anything. I could make that change but thinking about it I really think it would make more sense if it worked more in the way emo proposed.

Emo probably assumes that it is enough to make a 1x2 storage space where you can store any kind of things. And since I've done the moth eating, I can do something to help.

Are you going to figure out how to code it or..?

Hey! If ya can't finish this I'd love to do it myself. Let me know if your still working on it!

You are welcome to finish it because I just don't have time for this before the feature freeze, been very busy with life stuff so. I can't figure out how to close the PR on my phone so until I get on my computer just pretend it's closed :P


Fix the not operator, to respect code expressions

Code like
!Z_TYPE_P(
    (_array ? ZEPHIR_GLOBAL(global_true) : ZEPHIR_GLOBAL(global_false))
) == IS_ARRAY

could be produced before.
The problem is, that the not operator (!) has a higher precedence than the assignment operator (=),
which leads to a boolean being compared with IS_ARRAY.
This fixes #680.

Seems like okey, thanks


Introduce a condition option and copy request body when condition is met

Targets #179

Another item is the predicate is a bit "open-ended". It has full access to the HttpRequest which is mutable. Willing to bet someone is going to do something silly in this hook.

It isn't a remedy at first glance yes, we need to point to this option in the documentation for the people saying the underlying reason why and when you can implement this predicate.
Agree with the Predicate part and naming as well.
One option also could've been is exposing only HttpMethod in Predicate to prevent someone changes something in a silly way.  Predicate<string, bool> CopyRequestBodyWhen


Add tests for scrolling logic

Scrolling logic is currently implemented in ledger stack with no tests.
Move it to the library and add unit tests.

is this still relevant?

This issue is no longer valid. We now use pixel scrolling which is provided by ledger's SDK.


Please provide an example of apikeys.json

I tried by defining it as a variable inside the example but fails later on.
Can you please provide an example of the file?

{
    "PLANET_API_KEY":"XXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
}

If you would like an API key you need to register here for non-profit access and here for API developer access.


Grid  internal Padding

What problem does this feature solve?
it will resolve internal top and bottom padding problem for grid charts
What does the proposed API look like?
i want a normal key padding like borderwidth in grid object for e chart

Grid is the chart area by definition. You could provide some illustrations to demo what you want.

in this image i want top and bottom padding between y axis values and grid border

(url)

It seems you should set grid.top and grid.bottom to be larger.


PWA needs to be configured

We are currently using the vite-pwa/nuxt package for PWA.
But it is not configured yet, so the app cannot be used offline. The habit and diary alongside the pictures can be cached or called from LocalStorage. At the moment no relevant data is being saved in the LocalStorage, so that probably needs to be done first.

depends on #7


Show virtual product name along with variant in app product list

What is the motivation for adding/enhancing this feature?

What are the acceptance criteria?

[ ] ...

Can you complete this feature request by yourself?

[ ] YES
[ ] NO

Additional information

Makes sense @dt2patel


zibs MedicalDevice HearingFunction and VisualFunction

Please review these profiles. I tried to improve the mapping of MedicalDevice ProductID in FHIR, which still has an open question (https://bits.nictiz.nl/browse/ZIB-1535). I haven't slilenced all issues for ProductId in the known-issues for this yet.
Moreover, I believe the QA tooling has some complaints that will need to be silenced in the tooling:

== NL-CM:4.16.4 (DeviceUseStatement)
  short:       WARN ('MedicalDevice / VisualAid' instead of 'MedicalDevice / VisualAid:MedicalDevice')
 datatype:    ERROR (undefined instead of undefined)

I'd like to propose other names for these profiles using the zib concept names rather than the FHIR resource names. I think this is more clear than some part zib concept, some part FHIR resource:

zib-MedicalDevice-Device => zib-MedicalDevice.Product
zib-HearingFunction-MedicalDevice => zib-HearingFunction.HearingAid
zib-HearingFunction-MedicalDevice => zib-HearingFunction.HearingAid.Product
zib-VisualFunction-MedicalDevice => zib-VisualFunction.VisualAid
zib-VisualFunction-MedicalDevice-Device => zib-VisualFunction.VisualAid.Product

I'd like to propose other names for these profiles using the zib concept names rather than the FHIR resource names. I think this is more clear than some part zib concept, some part FHIR resource:

zib-MedicalDevice-Device => zib-MedicalDevice.Product
zib-HearingFunction-MedicalDevice => zib-HearingFunction.HearingAid
zib-HearingFunction-MedicalDevice => zib-HearingFunction.HearingAid.Product
zib-VisualFunction-MedicalDevice => zib-VisualFunction.VisualAid
zib-VisualFunction-MedicalDevice-Device => zib-VisualFunction.VisualAid.Product

And than the same pattern for nl-core

I agree! Fixed.

The errors:
  short:       WARN ('MedicalDevice / VisualAid' instead of 'MedicalDevice / VisualAid:MedicalDevice')
 datatype:    ERROR (undefined instead of undefined)

are now changed to:
     == NL-CM:4.16.4 (DeviceUseStatement)
        short:       WARNING (MedicalDevice / VisualAid instead of MedicalDevice / VisualAid:MedicalDevice)
        datatype:    WARNING (undefined instead of Reference)

I think it's correct to conclude that the short should be combined; there's a mapping to both elements. Regarding the inclusion of "VisualAid:" ... that's a zib bug (single colon instead of double colon, so splitting doesn't work correctly).

Sorry I missed updating the names, titles etc too! I now also have updated the know-issues.yml to the new names and added more to it.
The only remaining errors are the below ones.
==== snapshots/zib-HearingFunction.HearingAid.json
== NL-CM:10.1.1 (DeviceUseStatement)
datatype:    ERROR (undefined instead of undefined)
== NL-CM:4.17.4 (DeviceUseStatement)
datatype:    ERROR (undefined instead of undefined)

Manually rebased and merged


refactor(FOROME-1166): unify modal and panel for custom inh mode

https://quantori.atlassian.net/browse/FOROME-1166

Margin-bottom under the header of the modal will be fixed after this component is refactored to `Dialog`


frictionless v3.37.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

noarch: python recipes are recommended to have a lower bound on the python version. This recommendation will become a requirement in the future.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

requirements: run: jsonschema> =2.5 must contain a space between the name and the pin, i.e. jsonschema >=2.5

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


error reading log lines: error reading file system events: failed to read inotify events: interrupted system call

Hello @fstab
I have a Spring based application that uses log4j2 to write log files using an appender like this one:
<RollingRandomAccessFile append="true"
                                            name="StatusLogService"
                                            fileName="./Status.log"
                                            filePattern="./Status.log.%d{yyyy-MM-dd-HH}">
  <PatternLayout>
    <Pattern>%-5p %m%n</Pattern>
  </PatternLayout>
  <Policies>
    <TimeBasedTriggeringPolicy interval="1" />
  </Policies>
</RollingRandomAccessFile>

After starting grok_exporter with readall: false I could briefly poll the metrics, however, after a few seconds the exporter stopped and the log showed
error reading log lines: error reading file system events: failed to read inotify events: interrupted system call
I understand that someone had a similar problem on Windows (issue #17), which was solved after you implemented the poll_interval property. However, I am using RedHat Linux 6
I was wondering if there is something I have do to on my end, or if should use the poll_interval property. Moreover, if I use this property, will the log rollover be detected?
Thanks

I can confirm that grok_exporter works fine on RHEL6 with poll_interval set. The problem must be due to the old kernel used (2.6.x)


Update only the repository columns that need updating

We should only update is_empty, default_branch and updated time columns
during commitRepoAction and not update other columns as we risk
overwriting incorrect information.
Fix #11823
Fix #10536
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

Codecov Report

Merging #12900 into master will decrease coverage by 0.02%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master   #12900      +/-   ##
==========================================
- Coverage   43.11%   43.09%   -0.03%
==========================================
  Files         657      657
  Lines       72340    72342       +2
==========================================
- Hits        31189    31175      -14
- Misses      36107    36111       +4
- Partials     5044     5056      +12

Impacted Files
Coverage Δ

services/repository/push.go
57.92% <0.00%> (-0.65%)
:arrow_down:

modules/charset/charset.go
68.53% <0.00%> (-4.50%)
:arrow_down:

modules/notification/ui/ui.go
80.55% <0.00%> (-2.78%)
:arrow_down:

services/pull/check.go
47.69% <0.00%> (-2.31%)
:arrow_down:

modules/queue/workerpool.go
58.77% <0.00%> (-1.23%)
:arrow_down:

models/notification.go
65.83% <0.00%> (-0.91%)
:arrow_down:

models/error.go
34.81% <0.00%> (-0.86%)
:arrow_down:

modules/notification/mail/mail.go
34.48% <0.00%> (ø)

models/repo.go
55.77% <0.00%> (+0.22%)
:arrow_up:

modules/log/event.go
59.43% <0.00%> (+0.94%)
:arrow_up:

... and 1 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 89c94e2...c3eced8. Read the comment docs.

🚀

@zeripath please send backport:)


Add tools to test container

While debugging problems interactively, I missed several tools in the test container:

vim (create sql files)
ip (check ip adresses)
ss (checking open ports)
tmux

In order to avoid increase of size of the test container image, it would be better to add a script which can be used to install the mentioned packages on demand.


[Feature Request] Change the default source used with the "@bot Play [song title]"

Is your feature request related to a problem? Please describe.
Youtube playback being largely borked.
What is your ideal solution to the problem?
Enable users to choose a new default source for "@bot Play [song title]" from the supported options.
YouTube
SoundCloud
Bandcamp
Vimeo
Twitch streams
Local files
HTTP URLs

How would this feature be used?
via the config.txt or with another bot command
Additional Info
No response
Checklist

[X] I have checked the documentation to make sure this feature doesn't already exist
[X] I have searched for similar feature requests
[X] I have confirmed that my requests is not on the list of things that will not be added
[X] I am running the latest version of the bot:

YES. Youtube doesnt work or I just dont know how to get it too but If I could just select soundcloud as my main that would be amazing. Also if the search could be updated to work with soundcloud if that was selected as the main option.

youtube works if you update the youtube lavaplayer maven dependencies to their latest versions. you might also need to use the oauth branch, unsure

you might also need to use the oauth branch

do not use the oauth2 branch. i abandoned & deleted that branch a few weeks ago, because youtube patched the oauth2 workaround.


getState: doesn't report :focus state.

Expected:
let isFocused = Radium.getState(this.state, null, ':focus');

returns true if the root element focused.
Resulted:
It seems that :focus is never true in the internal state. (So this is not related to the key that's passed in...)

The second parameter is supposed to be the element's key


nsz: 4.4.0 -> 4.5.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/nicoboss/nsz/releases.
meta.description for nsz is: Homebrew compatible NSP/XCI compressor/decompressor
meta.homepage for nsz is: https://github.com/nicoboss/nsz
meta.changelog for nsz is: https://github.com/nicoboss/nsz/releases/tag/4.5.0
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.5.0 with grep in /nix/store/mi3sz9sx3s464p4jxw6qq1m66x38szyl-python3.10-nsz-4.5.0
found 4.5.0 in filename of file in /nix/store/mi3sz9sx3s464p4jxw6qq1m66x38szyl-python3.10-nsz-4.5.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
nsz
python310Packages.nsz
python311Packages.nsz

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mi3sz9sx3s464p4jxw6qq1m66x38szyl-python3.10-nsz-4.5.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A nsz https://github.com/r-ryantm/nixpkgs/archive/092aa3e184fe79146008a4368eb77601e54e924a.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/092aa3e184fe79146008a4368eb77601e54e924a#nsz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mi3sz9sx3s464p4jxw6qq1m66x38szyl-python3.10-nsz-4.5.0
ls -la /nix/store/mi3sz9sx3s464p4jxw6qq1m66x38szyl-python3.10-nsz-4.5.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

nsz (python310Packages.nsz)
python311Packages.nsz

Maintainer pings
cc @eyJhb for testing.

Result of nixpkgs-review pr 259547 run on x86_64-linux 1

4 packages built:

nsz (python310Packages.nsz)
nsz.dist (python310Packages.nsz.dist)
python311Packages.nsz
python311Packages.nsz.dist


Review message displayed when minimum requirements are not met for LS support

Current message displayed is as follows:

Feedback

We can change message to:

Your operating system does not meet the minimum requirements of the Python Language Server. Reverting to the alternative autocompletion provider, Jedi.

More info could redirect to this instead: https://github.com/microsoft/python-language-server/blob/master/TROUBLESHOOTING.md#requirements

Do we display something in the output for this? If so we could potentially add a "show output" button as well.

cc @qubitron

Let's make it an aka.ms link so we can update the link if necessary if we have a better doc topic in the future.

https://aka.ms/pythonlsrequirements

I believe we can change that to needs PR, can't we? @DonJayamanne

@luabud if you believe the spec is done then please change the label.

validated


Did not track Unstable Portal

Hi, don't know if this is a consistent issue as I have just started using this awesome tool, but the tracker just missed an Unstable Portal. Opponent played Mana Wyrm T1 (tracked), Unstable Portal T2 (untracked), Then Teacher/Frostbolt T3 (both tracked).
If it occasionally misses cards, no problem, but I wanted to mention this in case it is specifically an Unstable Portal issue that could be fixed.

I'm trying to replicate the bug, did not have the chance to atm, but I'm still trying


Update GrantPermissions.ps1

Remove dependency on the soon to be deprecated AzureAD module
Add some error management
ℹ Use emojis in the output
Fixes #160

@briandelmsft if you are good with that, I'll make the changes on the different small permission scripts

@piaudonn I'm wondering if we should just get rid of the small ones.  In my mind the small ones exist for 2 reasons, as a sort of document of what permissions that specific module needs, and, if we need to change permissions for a module that we could say just run the update for that module.  But is it really worth it?  We could document in md the permissions specific to each module.
How does this new script handle if the permission is already assigned?  Does it throw an error?  If it does can we handle that error since if the permission is already present it's not really an issue for us.  If the full script can re-execute on an existing deployment to add additional perms without throwing tons of errors I think we can get rid of the small scripts

When there are duplication:
⚙ Connect to the Azure AD tenant: 550a9b78-cb2e-43e0-9c5b-db194784b875
⚙ Connecting to  to the Azure subscription: 12f5f23d-9ade-4a66-ad94-67cf1314f629
⚙ Setting permission Data.Read on LS-Get-UEBAInsights
❌ Permission being assigned already exists on the object
⚙ Adding Microsoft Sentinel Responder to LS-Get-UEBAInsights
❌ Operation returned an invalid status code 'Conflict'
⚙ Setting permission MailboxSettings.Read on LS-Get-OOFDetails
❌ Permission being assigned already exists on the object
⚙ Adding Microsoft Sentinel Responder to LS-Get-OOFDetails
❌ Operation returned an invalid status code 'Conflict'
⚙ Setting permission Data.Read on LS-Get-RelatedAlerts
❌ Permission being assigned already exists on the object
⚙ Adding Microsoft Sentinel Responder to LS-Get-RelatedAlerts
❌ Operation returned an invalid status code 'Conflict'
⚙ Setting permission User.Read.All on LS-Get-MDEInsights
✅ Permission granted
⚙ Setting permission AdvancedQuery.Read.All on LS-Get-MDEInsights
✅ Permission granted
⚙ Setting permission Machine.Read.All on LS-Get-MDEInsights
...
Need to handle the case when it does not exist though.

I added the handling of principals not existing.
Yeah, the small scripts could go away. I have not used them since we have the custom connector.

what if we assigned a ℹ to the cases where the permission was already assigned instead of an ❌
I think if that were the case we could just do away with the small scripts and just guide people to re-run the full script in cases where permissions get added to modules over time

⚙ Setting permission Data.Read on LS-Get-UEBAInsights
ℹ Permission being assigned already exists on the object
⚙ Adding Microsoft Sentinel Responder to LS-Get-UEBAInsights
ℹ Permissions already assigned

I am getting failures about insufficient privileges, it seems on any of the Microsoft Graph permissions.  When I did the consent, I only consented as the user, not the organization.  Does the consent need to be for the whole organization?  It was done as a GA:

Also, is the warning to be expected?

I don't have the warning.
It doesn't look like you have the consent on the enterprise app in your tenant for that user.
No user consented permissions found for the application under Microsoft Graph PowerShell

Maybe it's an old module on my box that I need to update.
I did have the consent on the user, but I removed it so it would re-prompt for admin consent but I haven't got around to trying it again yet

@piaudonn I tracked the warning down to the Az.Resources module.  I was running 6.0.0, when I upgraded to the current (6.4.1) the warning went away.  I'm not sure what version specifically fixed it.  I don't know if this warrants putting in some module version check into the script?  but it certainly runs much nicer when you don't get those warnings
As for the insufficient privileges I'm still getting that error.  This time I left the consent grants in place so you should see them if you check the lab

@briandelmsft scope updated in the script
Also created the Legacy version of the script and updated the troubleshooting documentation.


Add android auto support

Added zoomBy(), getZoom() and setZoom to MapLibreMap
Added androidautoapp module to MapLibreAndroidTestApp

Very interested in Android Auto 👍

I also scheduled Android Auto as a discussion item for the next TSC Meeting.
7 PM to 8 PM CEST, MapLibre Native, https://zoom.us/j/97047175665?pwd=8C1EUbqXoNdUBJdmkfuhrb45PuxjzJ.1
(That time likely won't work for @thanhdang198).
On Slack I discussed with @frankkienl why I believe a separate repo for an Android Auto example project is a better idea:

The maplibre/maplibre-native repo focuses on the core renderer in C++ plus some platform bindings that wrap that renderer and essential functionality for a map toolkit on those platforms.  We also have apps part of this repo, but they exist primarily for the purpose of testing the platform bindings and/or core renderer. Platforms that do not directly integrate with the C++ renderer should in my opinion not be added to maplibre/maplibre-native. Android Auto is arguably such a platform.
Since end users using Android Auto will use MapLibre Android directly, having it in a separate project is a better demonstration of how they would intergrate it.
Maybe the project will grow out into a utility library to make intergrating MapLibre Android with Android Auto easier to use. In this case a separate project is definitely the better option.

@frankkienl said he will discuss with his colleagues if @flitsmeister can kick-off such a repo until we onboard it in the MapLibre organization.

I see some of the code I wrote for Flitsmeister, including my exact comments 😂 Curious to know how you got it.
I feel that if there would be official Android Auto support from MapLibre, that there should be a more efficient way instead of drawing a bitmap of the MapView to the Android Auto surface. If something like that were possible, I'd be very interested.

@rubenmx Oof, if that is really true and not some crazy coincidence, that is something we take very seriously.
@thanhdang198 Did you write this code yourself?

We did share it privately with another developer, I don't think its that big a deal, just curious if it ended up somewhere online or something.

@rubenmx Including code that infringes on someone copyright is a huge liability both for MapLibre as a project and our users, so we take great care to avoid that and have a policy in place to handle situations where this happened.
We rely on contributions following GitHub TOS which state:

Whenever you add Content to a repository containing notice of a license, you license that Content under the same terms, and you agree that you have the right to license that Content under those terms.

https://docs.github.com/en/site-policy/github-terms/github-terms-of-service#6-contributions-under-repository-license

@rubenmx Oof, if that is really true and not some crazy coincidence, that is something we take very seriously.
@thanhdang198 Did you write this code yourself?

I saw it in Slack chat and I mentioned it before. You can see this in the Slack thread.
I added more additional code for the gesture handles, like double-click zoom, two-finger zoom, and move the map.
With the gesture handle, I confirmed that I do not copy anywhere OUTSIDE the maplibre-native project. And of course, it not against the Mapbox license too.

We did share it privately with another developer, I don't think its that big a deal, just curious if it ended up somewhere online or something. Edit: I see now that Sjoerd shared in on the MapLibre slack.

Sorry if this PR is against any license of your code. I found they were shared in Slack without any license included.
If you need any additional action before it can be shared with the public or don't allow it, please let me know.
Thank you.

@thanhdang198 Ah so Flitsmeister shared some of this code on Slack? Thanks for clarifying.
Let's see if we hear back from @frankkienl and @rubenmx if @flitsmeister can release this code with a proper license. 👍
Closing this PR for now, but feel free to re-open one with the needed changes to MapLibreMap (still needs some tests).


How can I modify RNN cell weight during each training epoch?

I want to binarize the weights of RNN-GRU cell during each training epoch, in order to reduce the model size and increase the performance. Instead of binarizing the weights after freezing the graph, I wonder how can I get access to and modify the weights during each training epoch, or more specifically, before computing gradients and updating weights? It seems no API is provided to let RNN cell weight exposed to users.
Thank you so much.

Your question can be better addressed on StackOverflow. The GitHub "Issues" section is mainly for bug reporting and feature requests.
On the topic: take a look at tf.get_variable, it may help you.

As @MicaelCarvalho this is best answered on StackOverflow where we monitor all questions with the tag tensorflow. All optimizers have the compute_gradients method. You will get the variables and gradients back, then you can modify them at your leisure, before calling apply_gradients.


Add support for session listeners

Currently ther is no possibility to add custom dsession listeners (for e.g. to track session expired events) with embedded spark configuration.
It would be great to have such API to add custom listeners either on the configuration level or right from session insatnce, like this:
req.session().listener(new HttpSessionListener() {
                    @Override
                    public void sessionCreated(HttpSessionEvent se) {
                        // do custom things here
                    }

                    @Override
                    public void sessionDestroyed(HttpSessionEvent se) {
                        // do custom things here
                    }
                });

When trying to use raw session with embedded server it gives NullPointerException since JettyHandler provides no SessionDataStoreFactory and  NullSessionDataStore is used in Jetty by default and no servlet context is available:
                                 v // servlet context is null
session.raw().getServletContext().addListener(new HttpSessionListener() {
                    @Override
                    public void sessionCreated(HttpSessionEvent se) {
                       // custom logic here
                    }

                    @Override
                    public void sessionDestroyed(HttpSessionEvent se) {
                        // custom logic here
                    }
                });

Possibly implemented with this PR


Using pundit to ensure all controller actions have authorisation policy coverage

Move after_action :verify_authorized from documents_controller to
application_controller. This allows pundit to throw a warning when we
expose a controller action without proper authorisation rules in place.
Pass tests by adding policy for all controller actions
The pundit policy related to manuals are completely open right now, this has no effect on the existing authorisations and scoping that is inside of controller actions for manuals. The pundit policy offers some boilerplate for when we want to implement all the rules there.

A couple of ideas:

could we try reducing the number of policies to the number of different rule sets that we have (probably down to 2: rules for manuals and rules for specialist documents)? Currently all the manual* policies are the same.
could we bring the manual access rules in line with SP v1? I know we are trying to focus on specialist documents at the moment, but I feel like doing the manual permissions work later will require loading up a lot of context all over again.

I will work on adding unit tests for DocumentPolicy class and implementing the ManualPolicy rules as suggested.
As for the use of alias_method, we can revisit that when this PR gets updated with the new changes of manual policy

➕ 💯 for the implementation, couple of reservations about the tests though (that I could be talked out of).

Rebased against master and added a couple of commits to address the comments I left.  A little bit uncertain of how useful the specs actually are now they're written, but I was a little time constrained, sorry!


Offline setup fails, cannot fetch Singularity images

I am downloading MetScale for the first time and am running into issues with the download of the Singularity images when I run python download_offline_files.py --workflow all
Error message
Downloading singularity image fastqc_0.11.7--pl5.22.0_2.sif
FATAL:   While making image from oci registry: error fetching image to cache: failed to get checksum for docker://quay.io/biocontainers/fastqc:0.11.7--pl5.22.0_2: not a valid image manifest or image index
OS Error  fastqc_0.11.7--pl5.22.0_2.sif
[Errno 2] No such file or directory: 'fastqc_0.11.7--pl5.22.0_2.sif' -> '../container_images/fastqc_0.11.7--pl5.22.0_2.sif'
Additional context
I get this error for all the biocontainers (Trimmomatic, MultiQC, Khmer, MegaHIT, etc), but the database files are downloading properly.
Could you offer some guidance on the correct versions of the containers that I will need? Thanks!

Great, thanks! Can you try this command next? That is an equivalent command for what the metscale scripts are doing to download the singularity images.
singularity pull docker://quay.io/biocontainers/fastqc:0.11.7--pl5.22.0_2

Thanks! Here's the output:
singularity pull docker://quay.io/biocontainers/fastqc:0.11.7--pl5.22.0_2
FATAL:   While making image from oci registry: error fetching image to cache: failed to get checksum for docker://quay.io/biocontainers/fastqc:0.11.7--pl5.22.0_2: not a valid image manifest or image index

Thanks for the quick response! Unfortunately, I don't have an older version on the system, so I will look forward to the updated post. Really appreciate your help and support!

Thanks for your help on this issue. On a side note, could you share how much disk space and computing power is required for MetScale? I'm not having much luck when searching through the Wiki but I could have missed something!


Fix dnslink.sh issue when creating new TXT record

I had to tweak dnslink.sh when testing it out on a new domain to use the property name record_type instead of type to get it to create a new TXT record where none previously exists. See https://developer.dnsimple.com/v1/domains/records/#create

Whoopsie :)


cargo test --no-run should print paths to stdout

Problem
#10346 allowed printing the executable path from cargo test --no-run. It works however it prints to stderr and doesn't print the paths to stdout.
Proposed Solution
Print just the paths to stdout.
Notes
You would use --no-run for example if you need to execute a cross-arch binary. For example, qemu-aarch64 <path-to-binary>.
With this change it would be possible to do something like this.
cargo test --target aarch64-unknown-linux-gnu --no-run | xargs -L1 qemu-aarch64

Today the command looks like this,
cargo test --target aarch64-unknown-linux-gnu --no-run --message-format=json | jq  -r 'select(.reason=="compiler-artifact") | .executable | select(. != null)' | xargs -L1 qemu-aarch64

Sounds like what you are wanting is for cargo test --no-run to provide machine-readable output of the test executables.
Looking over #9957, it seems that our intended way for you to do that is with cargo test --no-run --message-format=json, for example cargo test --no-run --message-format=json | jq 'select(.reason=="compiler-artifact") | .executable'.

@epage I updated my post as soon as you posted, but yes I'm aware of that solution. When I followed the original issue, they were also aware of this but chose to continue to output the paths. I think this was the right call but it feels like the current solution just added logging instead of addressing the original issue.

While I understand the convenience of just reading stuff from stdout, this kind of approach is usually a bit too implicit. See https://github.com/rust-lang/cargo/issues/7280 about cargo vendor which prints to stdout for needed configurations but people are confused.
To me, I would prefer a more formal machine-readable format, like what epage recommended.

When I followed the original issue, they were also aware of this but chose to continue to output the paths

The original issue was targeted at providing the paths for a user which the PR resolved.
If we blindly printed paths, that would resolve this for you but would likely be confusing to others without additional context.  It would likely need to be opt-in.  This is what we have --message-format for.  We prefer to have a more structured form for programmatic use (json) as the needs can vary more than "output one specific field per line".  In your case, the field feels obvious for which field but that doesn't help with others.  The "per line" can also be a problem which leads to people also wanting null-terminated delimiters, etc.

@weihanglo I feel that comparison is a bit of a different situation. In that case cargo vendor path is printing out an entire config.toml. (But I actually kind of like this and I personally don't think it's that confusing)
What I'm suggesting is for the command output to behave more like standard cli tools. For example, awk sed grep tar were designed around this type of behavior.
@epage Sorry, I wasn't implying that the Issue wasn't resolved, it was more after following the problem my expectations didn't match the solution. The opt-in is reasonable, even if it was just --message-format path-list I think that would be really helpful.

Sorry, I wasn't implying that the Issue wasn't resolved, it was more after following the problem my expectations didn't match the solution.

That was what I was trying to clarify.  We had an existing solution for programmatic usage.  The problem that needed solving was for human usage.  The solution fits that quite well.  The root of this is not with that issue or its solution but that you are questioning the existing programmatic usage.

. The opt-in is reasonable, even if it was just --message-format path-list I think that would be really helpful.

I mentioned that only in the context that it might not be as reasonable to provide.
In maintaining software, we have to balance user requests with the ability to continue to deliver on user requests.  The more we add to cargo,

The more that needs documenting, the less people can find what they want, and the less of the provided features they use and the bigger the support burden in leading people to those features
The more we have to maintains and make sure works through all cases, slowing down overall progress.

@epage Okay sounds reasonable, I'll close the issue then.

I thought I would mention, since I didn't see anyone reference it, is that the intended method for doing things like qemu for testing is to use a target runner.


Set no-unused-var to on in linting

This removes the lint rule that had been set to warn for no-unused-vars.  This PR also updates the codebase to pass the linter.

Unused variable that were required have been removed.
Unused variables inside of callbacks have been commented out
One unused var for uid in posts has been left in and it is currently throwing.  It seemed odd that it wasn't being used. It isn't breaking the test suite but I want someone to sign off that it isn't an issue to remove it.

@jasonrhodes @isaacs @ednapiranha do you know anything about this rogue uid in posts?


Update GO version

Description
Update GO version
GitHub Issues
List the GitHub issues impacted by this PR:

GitHub Issue #

https://github.com/dell/csm/issues/491

Checklist:

[x] I have performed a self-review of my own code to ensure there are no formatting, vetting, linting, or security issues
[ ] I have verified that new and existing unit tests pass locally with my changes
[x] I have not allowed coverage numbers to degenerate
[x] I have maintained at least 90% code coverage
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have maintained backward compatibility

How Has This Been Tested?
https://osj-sio-03-prd.cec.lab.emc.com/job/CSM-Operator/job/csm-operator-build/206/

Why there are changes in all the manifest files.. Please rebase your branch and revert the changes made in all manifest files

@rensyct  rebased and now all the changes taken care after rebase.

@karthikk92 , please sign your commit

@karthikk92 , please sign your commit

taken care


Add Permanent Private User profile

Add Permanent Private User profile on localStorage or IPFS

dup #381

done in v1.6.4