iTMSTransporter “Error accessing file” after upgrade to Catalina

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description

After upgrading macOS to Catalina I cannot use pilot to upload builds to the app store anymore. Looks like it is because the HOME directory path changed (from /Local/Users/jenkins to /Users/jenkins) and transporter still has a reference to the old directory.
Resolver: Install error - org.apache.httpcomponents.httpcore Exception's name: java.io.IOException, Exception's message: Error accessing file:/Local/Users/jenkins/Library/Caches/com.apple.amp.itmstransporter/obr/2.0.0/org.apache.httpcomponents.httpcore-4.4.11.jar
ERROR [2020-04-23 13:32:09.94]: [Transporter Error Output]: could not find the service with interface (com.apple.transporter.osgi.TransporterService)

Command executed

fastlane pilot upload -i MyApp.ipa -s true -z true --verbose

Complete output when running fastlane, including the stack trace and command used

fastlane pilot upload -i MyApp.ipa -s true -z true --verbose
[✔] 🚀
[13:32:03]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
Successfully loaded Appfile at path '/Users/jenkins/workspace/iOS/_____/fastlane/Appfile'
- app_identifier: '_____'
- apple_id: '_____'
- team_id: '_____'
- itc_team_id: '_____'
-------
INFO [2020-04-23 13:32:04.15]: Login to App Store Connect (_____)
Reading keychain entry, because either user or password were empty
Loading session from '/Users/jenkins/.fastlane/spaceship/_____/cookie'
Looking for App Store Connect Team with ID _____
INFO [2020-04-23 13:32:05.05]: Login successful
DEBUG [2020-04-23 13:32:05.05]: App identifier (_____)
INFO [2020-04-23 13:32:06.18]: Ready to upload new build to TestFlight (App: _____)...
DEBUG [2020-04-23 13:32:06.18]: App Platform (ios)
INFO [2020-04-23 13:32:07.17]: Wrote XML data to '/var/folders/9x/v3j3pwzs14z_lfxj40n_tmsw000034/T/d20200423-35508-1onk1n2/938467045.itmsp'
INFO [2020-04-23 13:32:07.22]: Going to upload updated app to App Store Connect
INFO [2020-04-23 13:32:07.22]: This might take a few minutes. Please don't interrupt the script.
DEBUG [2020-04-23 13:32:07.29]: /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/itms/java/bin/java -Djava.ext.dirs=/Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/itms/java/lib/ext -XX:NewSize=2m -Xms32m -Xmx1024m -Xms1024m -Djava.awt.headless=true -Dsun.net.http.retryPost=false -jar /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/itms/lib/itmstransporter-launcher.jar -m upload -u _____ -p YourPassword -f /var/folders/9x/v3j3pwzs14z_lfxj40n_tmsw000034/T/d20200423-35508-1onk1n2/938467045.itmsp -t DAV,Signiant -k 100000 2>&1
DEBUG [2020-04-23 13:32:09.63]: [Transporter]: INFO: Configuring logging...
DEBUG [2020-04-23 13:32:09.64]: [Transporter]: INFO: Logging level set to eXtreme
DEBUG [2020-04-23 13:32:09.64]: [Transporter]: INFO: Transporter is searching for new software components.
DEBUG [2020-04-23 13:32:09.64]: [Transporter]: INFO: INFO: using cached repository.xml file.
DEBUG [2020-04-23 13:32:09.78]: [Transporter]: INFO: Update check complete.
ERROR [2020-04-23 13:32:09.94]: [Transporter Error Output]: Resolver: Install error - org.apache.httpcomponents.httpcore Exception's name: java.io.IOException, Exception's message: Error accessing file:/Local/Users/jenkins/Library/Caches/com.apple.amp.itmstransporter/obr/2.0.0/org.apache.httpcomponents.httpcore-4.4.11.jar
ERROR [2020-04-23 13:32:09.94]: [Transporter Error Output]: could not find the service with interface (com.apple.transporter.osgi.TransporterService)
WARN [2020-04-23 13:32:10.00]: [iTMSTransporter] [2020-04-23 13:32:09 EDT]   INFO: Configuring logging...
WARN [2020-04-23 13:32:10.00]: [iTMSTransporter] [2020-04-23 13:32:09 EDT]   INFO: Logging level set to eXtreme
WARN [2020-04-23 13:32:10.00]: [iTMSTransporter] [2020-04-23 13:32:09 EDT]   INFO: Transporter is searching for new software components.
WARN [2020-04-23 13:32:10.00]: [iTMSTransporter] [2020-04-23 13:32:09 EDT]   INFO: INFO: using cached repository.xml file.
WARN [2020-04-23 13:32:10.00]: [iTMSTransporter] [2020-04-23 13:32:09 EDT]   INFO: Update check complete.
WARN [2020-04-23 13:32:10.00]: [iTMSTransporter] [2020-04-23 13:32:09 EDT] <Equinox Log Thread - Equinox Container: 8bb65b6e-fec1-4f6a-a767-104b8a5dfc93> ERROR: Resolver: Install error - org.apache.httpcomponents.httpcore Exception's name: java.io.IOException, Exception's message: Error accessing file:/Local/Users/jenkins/Library/Caches/com.apple.amp.itmstransporter/obr/2.0.0/org.apache.httpcomponents.httpcore-4.4.11.jar
WARN [2020-04-23 13:32:10.00]: [iTMSTransporter] [2020-04-23 13:32:09 EDT]  ERROR: could not find the service with interface (com.apple.transporter.osgi.TransporterService)
INFO [2020-04-23 13:32:10.00]: iTunes Transporter output above ^
ERROR [2020-04-23 13:32:10.00]: Resolver: Install error - org.apache.httpcomponents.httpcore Exception's name: java.io.IOException, Exception's message: Error accessing file:/Local/Users/jenkins/Library/Caches/com.apple.amp.itmstransporter/obr/2.0.0/org.apache.httpcomponents.httpcore-4.4.11.jar
could not find the service with interface (com.apple.transporter.osgi.TransporterService)
The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure.
#######################################################################
fastlane 2.146.1 is available.
You should use the latest version.
Please update using sudo gem install fastlane.
#######################################################################
2.146.1Improvements

[action] fix update_code_signing_settings for unknown keys (#16357) via Josh Holtz

Please update using sudo gem install fastlane
Traceback (most recent call last):
14: from /usr/local/Cellar/fastlane/2.146.0/libexec/bin/fastlane:23:in <main>' 	13: from /usr/local/Cellar/fastlane/2.146.0/libexec/bin/fastlane:23:in load'
12: from /usr/local/Cellar/fastlane/2.146.0/libexec/gems/fastlane-2.146.0/bin/fastlane:23:in <top (required)>' 	11: from /usr/local/Cellar/fastlane/2.146.0/libexec/gems/fastlane-2.146.0/fastlane/lib/fastlane/cli_tools_distributor.rb:111:in take_off'
10: from /usr/local/Cellar/fastlane/2.146.0/libexec/gems/fastlane-2.146.0/pilot/lib/pilot/commands_generator.rb:18:in start' 	 9: from /usr/local/Cellar/fastlane/2.146.0/libexec/gems/fastlane-2.146.0/pilot/lib/pilot/commands_generator.rb:166:in run'
8: from /usr/local/Cellar/fastlane/2.146.0/libexec/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in run!' 	 7: from /usr/local/Cellar/fastlane/2.146.0/libexec/gems/fastlane-2.146.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in run!'
6: from /usr/local/Cellar/fastlane/2.146.0/libexec/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in run_active_command' 	 5: from /usr/local/Cellar/fastlane/2.146.0/libexec/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in run'
4: from /usr/local/Cellar/fastlane/2.146.0/libexec/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in call' 	 3: from /usr/local/Cellar/fastlane/2.146.0/libexec/gems/fastlane-2.146.0/pilot/lib/pilot/commands_generator.rb:66:in block (2 levels) in run'
2: from /usr/local/Cellar/fastlane/2.146.0/libexec/gems/fastlane-2.146.0/pilot/lib/pilot/build_manager.rb:37:in upload' 	 1: from /usr/local/Cellar/fastlane/2.146.0/libexec/gems/fastlane-2.146.0/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in method_missing'
/usr/local/Cellar/fastlane/2.146.0/libexec/gems/fastlane-2.146.0/fastlane_core/lib/fastlane_core/ui/interface.rb:141:in `user_error!': [!] Error uploading ipa file, for more information see above (FastlaneCore::Interface::FastlaneError)

Environment

🚫 fastlane environment 🚫
Stack

Key
Value

OS
10.15.4

Ruby
2.5.8

Bundler?
false

Git
git version 2.24.2 (Apple Git-127)

Installation Source
/usr/local/Cellar/fastlane/2.146.0/libexec/bin/fastlane

Host
Mac OS X 10.15.4 (19E287)

Ruby Lib Dir
<EMAIL_ADDRESS>

OpenSSL Version
OpenSSL 1.1.1f  31 Mar 2020

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
11.4.1

System Locale

Variable
Value

LANG
en_CA.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
fastlane_version "2.61.0"

default_platform :ios

platform :ios do
  before_all do
  end

  desc "Runs all the tests"
  lane :test do
    scan
  end

  desc "SANDBOX/QA BUILD"
  lane :sandbox do
    sigh
    gym(
      workspace: "________________",
      scheme: "________________",
      export_method: "ad-hoc",
      silent: true)
  end

  desc "Submit a new Beta Build to Apple TestFlight"
  desc "This will also make sure the profile is up to date"
  lane :beta do
    # match(type: "appstore") # more information: https://codesigning.guide
    gym(scheme: "________________") # Build your app - more options available
    pilot
  end

  desc "Deploy a new version to the App Store"
  lane :release do
    gym(scheme: "________________) # Build your app - more options available
    deliver(force: true)
  end

  lane :refresh_dsyms do |options|
    download_dsyms(version:options[:version])  # Download dSYM files from iTC
    upload_symbols_to_crashlytics(dsym_worker_threads: 5, gsp_path: "________________")  # Upload them to Crashlytics
    clean_build_artifacts           # Delete the local dSYM files
  end

  after_all do |lane|
  end

  error do |lane, exception|
  end
end

`./fastlane/Appfile`
app_identifier "_______________" # The bundle identifier of your app
apple_id "________________" # Your Apple email address

team_id "________________" # Developer Portal Team ID
itc_team_id "________________" # Consumer App iTunes team

fastlane gems

Gem
Version
Update-Status

fastlane
2.146.0
🚫 Update available

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

slack-notifier
2.3.2

atomos
0.1.3

CFPropertyList
3.0.2

claide
1.0.3

colored2
3.1.2

nanaimo
0.2.6

xcodeproj
1.16.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.7.0

terminal-table
1.8.0

plist
3.5.0

public_suffix
2.0.5

addressable
2.7.0

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.7.1

tty-cursor
0.7.1

tty-spinner
0.9.3

babosa
1.0.3

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

excon
0.73.0

faraday
0.17.3

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday_middleware
0.13.1

fastimage
2.1.7

gh_inspector
1.1.3

json
2.3.0

mini_magick
4.10.1

multi_xml
0.6.0

rubyzip
1.3.0

security
0.1.3

xcpretty-travis-formatter
1.0.0

dotenv
2.7.5

bundler
2.1.4

naturally
2.2.0

simctl
1.6.8

jwt
2.1.0

uber
0.1.0

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.2

mini_mime
1.0.2

multi_json
1.14.1

signet
0.14.0

memoist
0.16.2

os
1.1.0

googleauth
0.12.0

httpclient
2.8.3

google-api-client
0.36.4

google-cloud-env
1.3.1

google-cloud-errors
1.0.0

google-cloud-core
1.5.0

digest-crc
0.5.1

google-cloud-storage
1.26.0

emoji_regex
1.0.1

jmespath
1.4.0

aws-partitions
1.300.0

aws-eventstream
1.1.0

aws-sigv4
1.1.2

aws-sdk-core
3.94.0

aws-sdk-kms
1.30.0

aws-sdk-s3
1.62.0

generated on: 2020-04-23

I was able to solve this by deleting the following pesky file which had the invalid directory reference:
./System/Volumes/Data/Users/jenkins/Library/Caches/com.apple.amp.itmstransporter/obr/2.0.0/repository.xml
I noticed INFO: using cached repository.xml file so I searched for that file.


GitHub Packages cleanup

download_strategy: only request image index JSON for downloading the manifest for the tab
use a shared OS constant for the version of glibc we use in CI
fix skoepeo typo
ensure that blank hash values are deleted (again) rather than just nil ones
use a shared Hardware::CPU constant for oldest CPU we're supporting/using on Intel 64-bit
re-add comment to software_spec

Review period skipped due to critical label.


SQL Agent Log Files written with Job/Step in the filename

Logging SQL Agent Job log files would be great if they would have the Job Name/Step instead of a GUID.
This will make them much more readable.

This was changed some years ago, after new SQL Server Agent tokens for JOBNAME and STEPNAME were added in SQL Server 2016.
For previous versions it is still using the JOBID and STEPID tokens.


Create pipelines to unlist deprecated packages on 4 feeds

Fixes #5818
Description
Feeds are MyGet, NuGet, Azure, npm.
Pipelines are:
Unlist-DotNet-Packages-On-Azure
Unlist-DotNet-Packages-On-MyGet
Unlist-DotNet-Packages-On-NuGet
Unlist-Packages-On-Npm
View-Npm-Package-Versions-On-MyGet ("Unlist" is not supported. "View" is.)
The pipelines are currently configured to  not actually unlist, for safety. They can be activated at any time.
Unlisting DotNet on Azure is not tested because lacking authorization.
Unlisting DotNet on NuGet is not tested because lacking authorization.
Unlisting JS on npm is not tested because lacking authorization.
Specific Changes
5 yaml files created

Pull Request Test Coverage Report for Build 263632

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage remained the same at 76.103%

Files with Coverage Reduction
New Missed Lines
%

/libraries/AdaptiveExpressions/BuiltinFunctions/GetNextViableTime.cs
1
90.91%

/libraries/AdaptiveExpressions/BuiltinFunctions/GetPreviousViableTime.cs
1
90.91%

Totals

Change from base Build 262558:
0.0%

Covered Lines:
23158

Relevant Lines:
30430

💛  - Coveralls

Sufficient privileges are needed to do final testing against the ConversationalAI, npm and Nuget feeds.


No Controls

Hello guys,
I only see the sensors and diagnostics on my two pellet stoves (EGO Air 10 Up and EGO Air 8. Unfortunately there are no controls.

Hi @Voidfloop,
Can you attach the diagnostics files for both stoves ?
I'll have a look what is going wrong here.
Thanks !

Hi, thanks for the fast reply. sorry for the stupid question but where can I find the diagnostic files?

Now I've found what I'm looking for
MCZ EGO 8 config_entry-maestro_mcz-3f3bf13e5a79eac7ad71a45e245748ea.json.txt
MCZ EGO Comfort Air UP 10 config_entry-maestro_mcz-3f3bf13e5a79eac7ad71a45e245748ea.json.txt

I'll have to investigate and I'll come back to you as soon as I have more information !
Thanks for the files !

@Voidfloop,
I believe you are the first one to use this integration in combination with a M1+ stove (others are M2+)
This seems to have entire other configuration names.
I'm building support for it.
Since I can't test this myself (don't have a M1+ stove).
I would like it if you can test out the different functionalities and verify these are actually working. (Keep in mind the 30sec polling time)
I'll push this code within a couple of days probably.
Kind regards,
Robbe

yes, MCZ ended support for the old app and dropped a new app via their cloud. I was really happy that my oven could finally work with Home Assistant. If you succeed, hundreds of users will be happy once the news has spread. I will of course test everything, thank you

I can already give you a sneak peak of what it will look like for you :) (still work in progress)

@Voidfloop,
You can try this out by installing v0.4.0-beta
Let me know what is working and what not 😄
Cheers !

@Voidfloop,
Can you also provide me with a new screenshot + diagnostics file when the stove is actually switched on ?
Thanks in advance,
Robbe

I tested everything with my little model. The large stove has just been serviced and is still missing a seal. The manual control for the fan is missing. The fan also cannot be switched off with the button. The control between automatic and manual doesn't work either. (This doesn’t always work via the MCZ app either). I took a screenshot of the app for the fan control for you. I also noticed that the controls no longer work in the dashboard after a while. So turning it on works, but at some point I can no longer turn it off. Maybe just a temporary bug.
Thank you in advance for your work. You've come a long way, great

MCZ EGO 8 05.10.23 config_entry-maestro_mcz-adce20763d0d6ee095bf28563a0834a8.json.txt

I'll look into these problems, you are aware of the 30 sec polling time right ?
At most it can take 30sec to find your actions taking place.
That can maybe explain some behavior ?

I'm also very interested in the stove state, reported in the logbook.
Example of the states of my stove doing a 'full-cycle'

I put my big stove back into operation today.
Here the same. After the stabilization phase it gets the “off” signal and I no longer have control. But it continues to run normally.

MCZ EGO Comfort AIR 10   06.10.2023 config_entry-maestro_mcz-adce20763d0d6ee095bf28563a0834a8.json.txt


Create new space in backend through SpaceService.

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Feature - implements functionality to create spaces at the backend.

What is the current behavior? (You can also link to an open issue here)

No functionality to POST a space to create one.

What is the new behavior (if this is a feature change)?

SpaceService now has a method that can be invoked to create spaces in the backend.

Can one of the admins verify this patch?

[test]


Can't deploy due to "Stack with id {stack_id} does not exist"

I've got the same error again, after bootstraping CDK in the account, creating the logging bucket and checking the config. Can you please help me to debug it?
I'm using CDK v2, as v1 will be deprecated soon. Could this be the cause of the error? Here's a message from AWS:
This is the AWS CDK v2 Developer Guide. The older CDK v1 entered maintenance on June 1, 2022 and will now receive only critical bug fixes and security patches. New features will be developed for CDK v2 exclusively. Support for CDK v1 will end entirely on June 1, 2023.

Checking the config:
# vboufleur @ wiipo161 in ~/Development/vboufleur/aws-firewall-factory on git:master x [12:19:46] C:130
$ REGION=us-east-1 task validateconfig config=owasptopten
Your config values/owasptopten.json is valid.

The config JSON:
{
    "General": {
      "Prefix": "wiipo",
      "Stage": "dev",
      "S3LoggingBucketName": "sre-firewall-factory-logs-dev",
      "CreateDashboard": true,
      "DeployHash": "c02e5ead7fcc5f66b9b7b06e6a1b856d",
      "FireHoseKeyArn": "arn:aws:kms:us-east-1:115131055398:key/6e343b5b-8f8a-454d-925d-ef166007b9a8",
      "SecuredDomain": [
        "dev.wiipo.com",
        "albsp.wiipo.com"
      ]
    },
    "WebAcl": {
      "Name": "owasptopten",
      "Scope": "REGIONAL",
      "Type": "AWS::ApiGatewayV2::Api",
      "IncludeMap": {
        "account": [
          "115131055398"
        ]
      },
      "PreProcess": {
        "ManagedRuleGroups": [
          {
            "Vendor": "AWS",
            "Name": "AWSManagedRulesAmazonIpReputationList",
            "Version": "",
            "Capacity": 25
          },
          {
            "Vendor": "AWS",
            "Name": "AWSManagedRulesAnonymousIpList",
            "Version": "",
            "Capacity": 50
          },
          {
            "Vendor": "AWS",
            "Name": "AWSManagedRulesBotControlRuleSet",
            "Version": "",
            "Capacity": 50
          },
          {
            "Vendor": "AWS",
            "Name": "AWSManagedRulesCommonRuleSet",
            "Version": "",
            "Capacity": 700
          },
          {
            "Vendor": "AWS",
            "Name": "AWSManagedRulesKnownBadInputsRuleSet",
            "Version": "",
            "Capacity": 200
          },
          {
            "Vendor": "AWS",
            "Name": "AWSManagedRulesSQLiRuleSet",
            "Version": "",
            "Capacity": 200
          }
        ]
      },
      "PostProcess": {}
    }
  }

The error:
# vboufleur @ wiipo161 in ~/Development/vboufleur/aws-firewall-factory on git:master x [12:17:34]
$ REGION=us-east-1 task deploy config=owasptopten

🏷  Version:   3.1.1
👤 AWS Account used:
<PHONE_NUMBER>98
🌎 CDK deployment region:
                    us-east-1

/home/vboufleur/Development/vboufleur/aws-firewall-factory/node_modules/@aws-sdk/smithy-client/dist-cjs/default-error-handler.js:8
  const response = new exceptionCtor({
                   ^
ValidationError: Stack with id WIIPO-WAF-OWASPTOPTEN-DEV-C02E5EAD7FCC5F66B9B7B06E6A1B856D does not exist
  at throwDefaultError (/home/vboufleur/Development/vboufleur/aws-firewall-factory/node_modules/@aws-sdk/smithy-client/dist-cjs/default-error-handler.js:8:22)
  at /home/vboufleur/Development/vboufleur/aws-firewall-factory/node_modules/@aws-sdk/smithy-client/dist-cjs/default-error-handler.js:18:39
  at de_DescribeStacksCommandError (/home/vboufleur/Development/vboufleur/aws-firewall-factory/node_modules/@aws-sdk/client-cloudformation/dist-cjs/protocols/Aws_query.js:1575:12)
  at processTicksAndRejections (node:internal/process/task_queues:96:5)
  at /home/vboufleur/Development/vboufleur/aws-firewall-factory/node_modules/@aws-sdk/middleware-serde/dist-cjs/deserializerMiddleware.js:7:24
  at /home/vboufleur/Development/vboufleur/aws-firewall-factory/node_modules/@aws-sdk/middleware-signing/dist-cjs/middleware.js:14:20
  at /home/vboufleur/Development/vboufleur/aws-firewall-factory/node_modules/@aws-sdk/middleware-retry/dist-cjs/retryMiddleware.js:27:46
  at /home/vboufleur/Development/vboufleur/aws-firewall-factory/node_modules/@aws-sdk/middleware-logger/dist-cjs/loggerMiddleware.js:7:26
  at Object.setOutputsFromStack (/home/vboufleur/Development/vboufleur/aws-firewall-factory/lib/tools/helpers.ts:183:25)
  at /home/vboufleur/Development/vboufleur/aws-firewall-factory/bin/aws-firewall-factory.ts:114:11

Subprocess exited with error 1
task: Failed to run task "deploy": task: Failed to run task "cdkdeploy": exit status 1

Here's the parameters of the CloudFormation stack I used for for bootstraping CDK in the account:

This is the template for bootstraping the CDK that I used: https://github.com/aws/aws-cdk/blob/main/packages/aws-cdk/lib/api/bootstrap/bootstrap-template.yaml

Did you added the DeployHash on your own? The AWS Firewall Factory is generating the deploy hash after first sucessfull deployment so the factory knows which json is related to which aws clooudformation stack

@daknhh yes I did! I'll retry the deployment with a empty DeployHash and let you know.

@daknhh It worked! Thanks a lot!
What do you think about adding to the docs a section informing that the DeployHash shouldn't be informed in the first time the repo is run and that the repo will auto-fill it up?
If you don't have the time to do it please let me know and I'll send you a PR soon. I'm filled with work, but I can arrange a spare time to help this awesome project.

Great. I will add it no worries. I thought I did it actually, just checked again and yes you are right. Sorry about that.

@daknhh As we're talking about adding to the docs to help new users, what do you think about adding that the WebAcl: {Description} prop must be defined in the JSON? I got this error in CloudFormation when I tried pushing a JSON without that prop: Resource handler returned message: "Model validation failed (#/PolicyDescription: failed validation constraint for keyword [pattern])".
I think its best if we either add this to the docs, or, even better, change the code to add a default description when the prop is not defined. The line that defines the prop in CloudFormation is this one: https://github.com/globaldatanet/aws-firewall-factory/blob/master/lib/firewall-stack.ts#L169
This is the pattern that AWS uses to verify this prop: ^([\p{L}\p{Z}\p{N}_.:/=+\-@]*)$.
Source: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-fms-policy.html

Adjusted: https://github.com/globaldatanet/aws-firewall-factory/tree/feature/52 - i will also adjust readme later / tomorrow and release a new version soon

@vboufleur readme is also adjusted in the new feature branch -   https://github.com/globaldatanet/aws-firewall-factory/tree/feature/52

fix here: https://github.com/globaldatanet/aws-firewall-factory/releases/tag/3.1.2


stalls on vim start

The player stalls with the vim status-bar and a blank screen every time vim is run
The player then ceases to function due to a JS error

This issue was produced on chrome
The scenario generates the following JS error (in term.js):

short analysis : term is receiving 23 lines of input in vi mode when screen height is 24 lines

This looks like a term.js bug, but I’ll need a little more to diagnose is precisely.
Could you please post the following:

a sample ttyrec file that demonstrates this;
the specific version of term.js being used?

attaching a sample

using the term.js from the ttyplayer repo.

On Thu, Aug 13, 2015 at 9:14 AM, Chris Morgan<EMAIL_ADDRESS>wrote:

This looks like a term.js bug, but I’ll need a little more to diagnose is
precisely.
Could you please post the following:

a sample ttyrec file that demonstrates this;
the specific version of term.js being used?

—
Reply to this email directly or view it on GitHub
https://github.com/chris-morgan/tty-player/issues/1#issuecomment-130549963
.

(Attaching a .ttyrec file having failed, I was emailed the sample file.)
If you resize the tty-player to 180 columns wide, it works. It’s failing when it sends ESC[23;1H~«178 spaces», so it’s a simple overflow that term.js isn’t coping with—79 spaces on line 23, 80 on line 24, then it’s off the screen for the final 19 spaces.
If you use termrec for recording, it includes the width and height in the ttyrec script (you need to use a version of term.js including chjj/term.js#75 for it to work), so you wouldn’t run into this issue. You can also go specifying the cols and rows attributes on the tty-player element.
As for the exception itself, I was able to reduce it very effectively and have filed chjj/term.js#84 for the matter. As it is a term.js issue and not a tty-player issue (with the way of achieving the desired behaviour explained in the previous paragraph also), I am closing this issue.


Fix cub not bundled in wheels

During the verification process, I found that CUB source tree is not bundled in CuPy wheels.

Diff of file list for reference.
This PR removes these from sdist:
< ./cupy-8.0.0b5/cupy/core/include/cupy/cub/.cproject
< ./cupy-8.0.0b5/cupy/core/include/cupy/cub/examples/block/.gitignore
< ./cupy-8.0.0b5/cupy/core/include/cupy/cub/examples/device/.gitignore
< ./cupy-8.0.0b5/cupy/core/include/cupy/cub/experimental/.gitignore
< ./cupy-8.0.0b5/cupy/core/include/cupy/cub/.git
< ./cupy-8.0.0b5/cupy/core/include/cupy/cub/.project
< ./cupy-8.0.0b5/cupy/core/include/cupy/cub/.settings
< ./cupy-8.0.0b5/cupy/core/include/cupy/cub/.settings/.gitignore
< ./cupy-8.0.0b5/cupy/core/include/cupy/cub/.settings/org.eclipse.cdt.codan.core.prefs
< ./cupy-8.0.0b5/cupy/core/include/cupy/cub/.settings/org.eclipse.cdt.core.prefs
< ./cupy-8.0.0b5/cupy/core/include/cupy/cub/.settings/org.eclipse.cdt.ui.prefs
< ./cupy-8.0.0b5/cupy/core/include/cupy/cub/.settings/org.eclipse.core.runtime.prefs
< ./cupy-8.0.0b5/cupy/core/include/cupy/cub/test/.gitignore
< ./cupy-8.0.0b5/cupy/core/include/cupy/cub/tune/.gitignore

and adds these to wheel:
> ./cupy/core/include/cupy/complex/README.md
> ./cupy/core/include/cupy/cub
> ./cupy/core/include/cupy/cub/CHANGE_LOG.TXT
> ./cupy/core/include/cupy/cub/common.mk
> ./cupy/core/include/cupy/cub/cub
> ./cupy/core/include/cupy/cub/cub/agent
> ./cupy/core/include/cupy/cub/cub/agent/agent_histogram.cuh
> ./cupy/core/include/cupy/cub/cub/agent/agent_radix_sort_downsweep.cuh
> ./cupy/core/include/cupy/cub/cub/agent/agent_radix_sort_upsweep.cuh
> ./cupy/core/include/cupy/cub/cub/agent/agent_reduce_by_key.cuh
> ./cupy/core/include/cupy/cub/cub/agent/agent_reduce.cuh
> ./cupy/core/include/cupy/cub/cub/agent/agent_rle.cuh
> ./cupy/core/include/cupy/cub/cub/agent/agent_scan.cuh
> ./cupy/core/include/cupy/cub/cub/agent/agent_segment_fixup.cuh
> ./cupy/core/include/cupy/cub/cub/agent/agent_select_if.cuh
> ./cupy/core/include/cupy/cub/cub/agent/agent_spmv_orig.cuh
> ./cupy/core/include/cupy/cub/cub/agent/single_pass_scan_operators.cuh
> ./cupy/core/include/cupy/cub/cub/block
> ./cupy/core/include/cupy/cub/cub/block/block_adjacent_difference.cuh
> ./cupy/core/include/cupy/cub/cub/block/block_discontinuity.cuh
> ./cupy/core/include/cupy/cub/cub/block/block_exchange.cuh
> ./cupy/core/include/cupy/cub/cub/block/block_histogram.cuh
> ./cupy/core/include/cupy/cub/cub/block/block_load.cuh
> ./cupy/core/include/cupy/cub/cub/block/block_radix_rank.cuh
> ./cupy/core/include/cupy/cub/cub/block/block_radix_sort.cuh
> ./cupy/core/include/cupy/cub/cub/block/block_raking_layout.cuh
> ./cupy/core/include/cupy/cub/cub/block/block_reduce.cuh
> ./cupy/core/include/cupy/cub/cub/block/block_scan.cuh
> ./cupy/core/include/cupy/cub/cub/block/block_shuffle.cuh
> ./cupy/core/include/cupy/cub/cub/block/block_store.cuh
> ./cupy/core/include/cupy/cub/cub/block/specializations
> ./cupy/core/include/cupy/cub/cub/block/specializations/block_histogram_atomic.cuh
> ./cupy/core/include/cupy/cub/cub/block/specializations/block_histogram_sort.cuh
> ./cupy/core/include/cupy/cub/cub/block/specializations/block_reduce_raking_commutative_only.cuh
> ./cupy/core/include/cupy/cub/cub/block/specializations/block_reduce_raking.cuh
> ./cupy/core/include/cupy/cub/cub/block/specializations/block_reduce_warp_reductions.cuh
> ./cupy/core/include/cupy/cub/cub/block/specializations/block_scan_raking.cuh
> ./cupy/core/include/cupy/cub/cub/block/specializations/block_scan_warp_scans2.cuh
> ./cupy/core/include/cupy/cub/cub/block/specializations/block_scan_warp_scans3.cuh
> ./cupy/core/include/cupy/cub/cub/block/specializations/block_scan_warp_scans.cuh
> ./cupy/core/include/cupy/cub/cub/cub.cuh
> ./cupy/core/include/cupy/cub/cub/device
> ./cupy/core/include/cupy/cub/cub/device/device_histogram.cuh
> ./cupy/core/include/cupy/cub/cub/device/device_partition.cuh
> ./cupy/core/include/cupy/cub/cub/device/device_radix_sort.cuh
> ./cupy/core/include/cupy/cub/cub/device/device_reduce.cuh
> ./cupy/core/include/cupy/cub/cub/device/device_run_length_encode.cuh
> ./cupy/core/include/cupy/cub/cub/device/device_scan.cuh
> ./cupy/core/include/cupy/cub/cub/device/device_segmented_radix_sort.cuh
> ./cupy/core/include/cupy/cub/cub/device/device_segmented_reduce.cuh
> ./cupy/core/include/cupy/cub/cub/device/device_select.cuh
> ./cupy/core/include/cupy/cub/cub/device/device_spmv.cuh
> ./cupy/core/include/cupy/cub/cub/device/dispatch
> ./cupy/core/include/cupy/cub/cub/device/dispatch/dispatch_histogram.cuh
> ./cupy/core/include/cupy/cub/cub/device/dispatch/dispatch_radix_sort.cuh
> ./cupy/core/include/cupy/cub/cub/device/dispatch/dispatch_reduce_by_key.cuh
> ./cupy/core/include/cupy/cub/cub/device/dispatch/dispatch_reduce.cuh
> ./cupy/core/include/cupy/cub/cub/device/dispatch/dispatch_rle.cuh
> ./cupy/core/include/cupy/cub/cub/device/dispatch/dispatch_scan.cuh
> ./cupy/core/include/cupy/cub/cub/device/dispatch/dispatch_select_if.cuh
> ./cupy/core/include/cupy/cub/cub/device/dispatch/dispatch_spmv_orig.cuh
> ./cupy/core/include/cupy/cub/cub/grid
> ./cupy/core/include/cupy/cub/cub/grid/grid_barrier.cuh
> ./cupy/core/include/cupy/cub/cub/grid/grid_even_share.cuh
> ./cupy/core/include/cupy/cub/cub/grid/grid_mapping.cuh
> ./cupy/core/include/cupy/cub/cub/grid/grid_queue.cuh
> ./cupy/core/include/cupy/cub/cub/host
> ./cupy/core/include/cupy/cub/cub/host/mutex.cuh
> ./cupy/core/include/cupy/cub/cub/iterator
> ./cupy/core/include/cupy/cub/cub/iterator/arg_index_input_iterator.cuh
> ./cupy/core/include/cupy/cub/cub/iterator/cache_modified_input_iterator.cuh
> ./cupy/core/include/cupy/cub/cub/iterator/cache_modified_output_iterator.cuh
> ./cupy/core/include/cupy/cub/cub/iterator/constant_input_iterator.cuh
> ./cupy/core/include/cupy/cub/cub/iterator/counting_input_iterator.cuh
> ./cupy/core/include/cupy/cub/cub/iterator/discard_output_iterator.cuh
> ./cupy/core/include/cupy/cub/cub/iterator/tex_obj_input_iterator.cuh
> ./cupy/core/include/cupy/cub/cub/iterator/tex_ref_input_iterator.cuh
> ./cupy/core/include/cupy/cub/cub/iterator/transform_input_iterator.cuh
> ./cupy/core/include/cupy/cub/cub/thread
> ./cupy/core/include/cupy/cub/cub/thread/thread_load.cuh
> ./cupy/core/include/cupy/cub/cub/thread/thread_operators.cuh
> ./cupy/core/include/cupy/cub/cub/thread/thread_reduce.cuh
> ./cupy/core/include/cupy/cub/cub/thread/thread_scan.cuh
> ./cupy/core/include/cupy/cub/cub/thread/thread_search.cuh
> ./cupy/core/include/cupy/cub/cub/thread/thread_store.cuh
> ./cupy/core/include/cupy/cub/cub/util_allocator.cuh
> ./cupy/core/include/cupy/cub/cub/util_arch.cuh
> ./cupy/core/include/cupy/cub/cub/util_debug.cuh
> ./cupy/core/include/cupy/cub/cub/util_device.cuh
> ./cupy/core/include/cupy/cub/cub/util_macro.cuh
> ./cupy/core/include/cupy/cub/cub/util_namespace.cuh
> ./cupy/core/include/cupy/cub/cub/util_ptx.cuh
> ./cupy/core/include/cupy/cub/cub/util_type.cuh
> ./cupy/core/include/cupy/cub/cub/warp
> ./cupy/core/include/cupy/cub/cub/warp/specializations
> ./cupy/core/include/cupy/cub/cub/warp/specializations/warp_reduce_shfl.cuh
> ./cupy/core/include/cupy/cub/cub/warp/specializations/warp_reduce_smem.cuh
> ./cupy/core/include/cupy/cub/cub/warp/specializations/warp_scan_shfl.cuh
> ./cupy/core/include/cupy/cub/cub/warp/specializations/warp_scan_smem.cuh
> ./cupy/core/include/cupy/cub/cub/warp/warp_reduce.cuh
> ./cupy/core/include/cupy/cub/cub/warp/warp_scan.cuh
> ./cupy/core/include/cupy/cub/eclipse code style profile.xml
> ./cupy/core/include/cupy/cub/examples
> ./cupy/core/include/cupy/cub/examples/block
> ./cupy/core/include/cupy/cub/examples/block/example_block_radix_sort.cu
> ./cupy/core/include/cupy/cub/examples/block/example_block_reduce.cu
> ./cupy/core/include/cupy/cub/examples/block/example_block_scan.cu
> ./cupy/core/include/cupy/cub/examples/block/Makefile
> ./cupy/core/include/cupy/cub/examples/block/reduce_by_key.cu
> ./cupy/core/include/cupy/cub/examples/device
> ./cupy/core/include/cupy/cub/examples/device/example_device_partition_flagged.cu
> ./cupy/core/include/cupy/cub/examples/device/example_device_partition_if.cu
> ./cupy/core/include/cupy/cub/examples/device/example_device_radix_sort.cu
> ./cupy/core/include/cupy/cub/examples/device/example_device_reduce.cu
> ./cupy/core/include/cupy/cub/examples/device/example_device_scan.cu
> ./cupy/core/include/cupy/cub/examples/device/example_device_select_flagged.cu
> ./cupy/core/include/cupy/cub/examples/device/example_device_select_if.cu
> ./cupy/core/include/cupy/cub/examples/device/example_device_select_unique.cu
> ./cupy/core/include/cupy/cub/examples/device/example_device_sort_find_non_trivial_runs.cu
> ./cupy/core/include/cupy/cub/examples/device/Makefile
> ./cupy/core/include/cupy/cub/experimental
> ./cupy/core/include/cupy/cub/experimental/defunct
> ./cupy/core/include/cupy/cub/experimental/defunct/example_coo_spmv.cu
> ./cupy/core/include/cupy/cub/experimental/defunct/test_device_seg_reduce.cu
> ./cupy/core/include/cupy/cub/experimental/histogram
> ./cupy/core/include/cupy/cub/experimental/histogram_compare.cu
> ./cupy/core/include/cupy/cub/experimental/histogram/histogram_cub.h
> ./cupy/core/include/cupy/cub/experimental/histogram/histogram_gmem_atomics.h
> ./cupy/core/include/cupy/cub/experimental/histogram/histogram_smem_atomics.h
> ./cupy/core/include/cupy/cub/experimental/Makefile
> ./cupy/core/include/cupy/cub/experimental/sparse_matrix.h
> ./cupy/core/include/cupy/cub/experimental/spmv_compare.cu
> ./cupy/core/include/cupy/cub/experimental/spmv_script.sh
> ./cupy/core/include/cupy/cub/LICENSE.TXT
> ./cupy/core/include/cupy/cub/README.md
> ./cupy/core/include/cupy/cub/test
> ./cupy/core/include/cupy/cub/test/half.h
> ./cupy/core/include/cupy/cub/test/link_a.cu
> ./cupy/core/include/cupy/cub/test/link_b.cu
> ./cupy/core/include/cupy/cub/test/link_main.cpp
> ./cupy/core/include/cupy/cub/test/Makefile
> ./cupy/core/include/cupy/cub/test/mersenne.h
> ./cupy/core/include/cupy/cub/test/test_allocator.cu
> ./cupy/core/include/cupy/cub/test/test_block_histogram.cu
> ./cupy/core/include/cupy/cub/test/test_block_load_store.cu
> ./cupy/core/include/cupy/cub/test/test_block_radix_sort.cu
> ./cupy/core/include/cupy/cub/test/test_block_reduce.cu
> ./cupy/core/include/cupy/cub/test/test_block_scan.cu
> ./cupy/core/include/cupy/cub/test/test_device_histogram.cu
> ./cupy/core/include/cupy/cub/test/test_device_radix_sort.cu
> ./cupy/core/include/cupy/cub/test/test_device_reduce_by_key.cu
> ./cupy/core/include/cupy/cub/test/test_device_reduce.cu
> ./cupy/core/include/cupy/cub/test/test_device_run_length_encode.cu
> ./cupy/core/include/cupy/cub/test/test_device_scan.cu
> ./cupy/core/include/cupy/cub/test/test_device_select_if.cu
> ./cupy/core/include/cupy/cub/test/test_device_select_unique.cu
> ./cupy/core/include/cupy/cub/test/test_grid_barrier.cu
> ./cupy/core/include/cupy/cub/test/test_iterator.cu
> ./cupy/core/include/cupy/cub/test/test_util.h
> ./cupy/core/include/cupy/cub/test/test_warp_reduce.cu
> ./cupy/core/include/cupy/cub/test/test_warp_scan.cu
> ./cupy/core/include/cupy/cub/tune
> ./cupy/core/include/cupy/cub/tune/Makefile
> ./cupy/core/include/cupy/cub/tune/tune_device_reduce.cu
> ./cupy/core/include/cupy/_cuda/README.md
> ./cupy/core/include/cupy/README.md

pfnCI, test this please.

Jenkins CI test (for commit 050318e443e0d5313d882d91bc27866c4989b390, target branch master) succeeded!


Publish development documents through github actions.

What type of PR is this?

release/none
kind/doc

What this PR does / why we need it:
Supports the latest branch and can generate development documents. The design is as follows:
In the github interface, you can pass in the parameter main to determine whether your document is published as the latest.If the value is main, development documentation will be generated based on the main branch. Its format is dev (main)，If the value is not main, it will be triggered based on tag.
Which issue(s) this PR fixes:

Fixes #2482
Special notes for your reviewer:
Signed-off-by: ty-dc<EMAIL_ADDRESS>

/hold

The effect looks like this:

不需要 0.8（latest），只需要latest。否则 没有tag或者 version没更新，就变成 0.7 latest

不需要 0.8（latest），只需要latest。否则 没有tag或者 version没更新，就变成 0.7 latest

是这样做的。只要是main 分支，都默认打到 dev 目录下，界面只会显示 dev。不会变为 0.7、0.8 这类的。
下列的命令 -t ，只是给 dev 从新取了个标题。大概告诉了一下，该 dev 是基于main 分支。
mike deploy --rebase -b ${{ env.MERGE_BRANCH }} dev -t "dev (${{ env.REF }})"

实际效果：


Add option to disable when using a git repository

When I'm already in a git repository, I'm less likely to need the local-history plugin.
I suggest adding a 4 option to the "local-history.enabled".

-1
Use local history is an addiction to git, not a competition, it is great to have versioning even without commit the file.
Intellij, webStorm and all brainStorm IDEs have this enabled by default and I'm pretty sure that there is no way to disable it.

I agree with @carlos-algms, it can be usefull to have versioning and git working together.
I'll not implement such a feature..


how to set a mirror repository with nvm command

Operating system and version:
nvm debug output:

nvm ls output:

How did you install nvm?

What steps did you perform?
What happened?
What did you expect to happen?
Is there anything in any of your profile files that modifies the PATH?

If you are having installation issues, or getting "N/A", what does curl -I --compressed -v https://nodejs.org/dist/ print out?

A mirror for what, exactly? For nodejs.org/dist and iojs.org/dist, you can set the appropriate env vars: https://github.com/nvm-sh/nvm/blob/master/nvm.sh#L1852-L1853

thanks a lot，you're right.
just set env: NVM_NODEJS_ORG_MIRROR


added docfx 2.40.4

resolves #1517
Wasn't sure if this should go in scoop-extras or directly in scoop as it is an official dotnet project tool

Since it's a CLI tool it should be added to the main bucket. :smile:


MAINT: pin python 3.7.4 in circle's build_docs

Addresses #1835 trying to get lucky (as python version is the most significant change w.r.t. to the latest successful build).

Okay, this works. Merging.


[Logical Optimizer] register logical properties

The logical properties of the logical optimizer includes:

[x] schema
[ ] outer cols (columns are not defined in the underlying expr trees, eg: agg output column...)
[ ] equivalent cols (equivalent column sets)
[ ] not null cols
[ ]  keys and weak keys cols (keys are unique not null columns, weak keys are unique columns(might contain nulls))
[ ] foreign keys cols (cols have foreign key constraints)

schema support is not complete 🤤


not able to downlaod the neo4j-cluster image via kitematic

Expected behavior
Actual behavior
(HTTP code 500) server error - {"message":"Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on <IP_ADDRESS>:53: lame referral"}
Information about the Issue
Steps to reproduce the behavior

...
...

Please make sure that you're on a stable connection and use a solid DNS such as Google DNS.


fixes +spin to preserve the type of the head of the product

This resolves an issue that I introduced when I refactor +spin and +spun in #649. The typecast of the sample gate c in +spin was throwing away the type of the head of the product, which is somewhat unfortunate:
> ? (spun "foo" |=([a=@tD b=@ud] [[b a] +(b)]))
  it(*)
~[[0 102] [1 111] [2 111]]

With this fix in place:
> ? (spun "foo" |=([a=@tD b=@ud] [[b a] +(b)]))
  it({@ud @tD})
~[[0 'f'] [1 'o'] [2 'o']]

My apologies for insufficiently testing the previous PR.

Seems legit.


Issue 7168 - Regression(1.072, 2.057) __traits(allMembers) returns wrong tuple

http://d.puremagic.com/issues/show_bug.cgi?id=7168

This bug was introduced by merging pull #437.

Does this also fix http://d.puremagic.com/issues/show_bug.cgi?id=7160 ?

Added fix for 7160.


Fix: Hide webview context menu commands as needed.

Fixes #474.

Abandoned due to a GPG signing mistake. Will redo.


Problems when sending messages with arrays

[v] I am at the right place and my issue is directly related to ROS#. General technical questions I would post e.g. at ROS Answers or Stack Overflow. For library-specific questions I would look for help in the corresponding library forums.
[v] I have thoroughly read the Contributing Guideline and writing this issue is the right thing to do in my case.

I found a bug!

[x] I am using the latest ROS# version available here on the master branch.

I was using ROS# release 1.4.

[v] I am adding all required information, code and data files, screenshots and log files so that you can reproduce the problem.

My OS is: Windows 10

My Unity Version is: 2018.2, 2018.3

My ROS Distribution is: Kinetic

My Build Target Platform is: Windows Desktop.

Here is my bug description:
When there is an array in my message, the receiver does not get the right results. To illustrate this, I am sending a Sensor::CompressedImage message at every fixed update, using the header.seq to mark the order of the messages, and writing on the data array integers modulo 8. See the code below.
Perform the following steps reproduce the bug:
Get RosSharp v 1.4, open the unity package in Unity. Add a RosConnector, it does not matter whether WebSocket Net or Sharp. Add the following publisher:
using UnityEngine;
namespace RosSharp.RosBridgeClient
{
    public class MyByteArrayPublisher : Publisher<Messages.Sensor.CompressedImage>
    {
        int cnt;
        protected override void Start()
        {
            base.Start();
            cnt = 0;
        }

        private void FixedUpdate()
        {
            Messages.Sensor.CompressedImage m = new Messages.Sensor.CompressedImage();
            m.header.seq = cnt;
            m.data = new byte[400 * 400];
            m.data[0] = (byte)(cnt % 8);
            m.data[2] = (byte)(cnt % 8);
            cnt += 1;
            Debug.Log("M: " + m.header.seq + ", " + m.data[2]);
            Publish(m);
        }
    }
}

On the ROS side, I have the following C++ receiver:
#include "ros/ros.h"
#include "sensor_msgs/CompressedImage.h"

void imageCallback(const sensor_msgs::CompressedImage::ConstPtr& msg)
{
  ROS_INFO("I heard: [%7d %8u %8u %8u %8u %8u]", msg->header.seq, msg->data[0],
           msg->data[1], msg->data[2], msg->data[3], msg->data[4]);
}

int main(int argc, char **argv)
{
  ros::init(argc, argv, "listener");
  ros::NodeHandle n;
  ros::Subscriber sub = n.subscribe("unity_bytes", 1000, imageCallback);
  ros::spin();

  return 0;
}

Observed results:
One can see in the picture, that the Unity Editor prints the messages correctly, but my C++ listener in Ubuntu does not. While the messages are received in order (header.seq looks fine), one can see that the data array starts well, but is quickly messed up.

Expected results:
Obviously, data should be the same on both Unity Editor and C++ listener. Running the following C++ publisher on the Linux side works as expected.
#include "ros/ros.h"
#include "sensor_msgs/CompressedImage.h"

int main(int argc, char **argv)
{
  ros::init(argc, argv, "speakingBytes");
  ros::NodeHandle n;
  ros::Publisher chatter_pub = n.advertise<sensor_msgs::CompressedImage>("unity_bytes", 1000);
  ros::Rate loop_rate(10);
  int count = 0;
  while (ros::ok())
  {
    sensor_msgs::CompressedImage imgMsg;

    imgMsg.header.seq = count;
    imgMsg.data = std::vector<uint8_t>(400*400, 0);
    imgMsg.data[2] = (uint8_t) (count % 8);

    ROS_INFO("I said: %7d %8u", imgMsg.header.seq, imgMsg.data[2]);

    chatter_pub.publish(imgMsg);
    ros::spinOnce();
    loop_rate.sleep();
   ++count;
  }

  return 0;
}

Anybody?

Hi @solernou !

When the message size exceeds a certain limit it is split up into multiple pieces. If additionally to many of those messages must be sent in too short time, more recent messages are re-composed before older ones on the other side and the order is lost. I also remeber that some messages were lost in these cases, most likely due to buffer/memory limits.

I presume that this change in order happens on the server / ROS side. At least the WebSocketNet Client that I implemented can in no case change the order of messages. Another indication for that is, that both WebSocketSharp and WebSocketNet yield the same problem.

I remember that I simply reduced the traffic load by reducing the time step between messages.

Another option would be to ask here for support.

Other than that, why do you publish an image every FixedUpdate() anyway? Unity renders an image every Update() only. By publishing every FixedUpdate() you will often send the same image multiple times.  If you publish in LateUpdate() , you will have the most freshly rendered data available
and at the same time drastically reduce your network load...
To further reduce load, you could implement a counter which only publishes every 2nd or 3rd LateUpdate() or so....

I hope this helps.

Hi @solernou did my answer help? Any update on your issue?

Hi Martin,
yes, your answer was really clarifying indeed. We're investigating
whether we can live with less data traffic, but haven't been able to
work on it as have been busy with some other projects.
I'll write you back when I have something useful :)
Cheers,
Albert
On 27/02/2019 11:50, Martin Bischoff wrote:

Hi @solernou https://github.com/solernou did my answer help? Any
update on your issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/siemens/ros-sharp/issues/161#issuecomment-467832932,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALeM-2Bs4BCO89qSjapcewqhBVIIZHyuks5vRnD_gaJpZM4aage5.

--
Dr Albert Solernou
Software Development Scientist,
Institute for Transport Studies,
University of Leeds
Tel: +44 (0)1133 438890

After some investigation I managed to make it work at 12Hz under the Unity Editor. In order to do this benchmark I set the frequency on both sides to it, while keeping the FixedUpdate on the Unity side. I also switched to LG's implementation of RosBridge this time. We're having internal discussions on whether to accept this frequency or not.
Something else I checked was to set the header ID to a fixed value:
imgMsg.header.seq = 1;
and to my surprise, this did not have an effect on the receptor side. Instead, the received messages showed the expected behaviour (1, 2, 3, 4, ...). Thus, it is either that:

ROS# fixes the header if it is invalid.
RosBridge does not care of this value and prints whatever it likes. In that case, we could be seeing out-of-order messages when the workload is too heavy for RosBridge to cope with.

I am happy for you to close this issue if you don't have anything further to add.

Thank you for reporting these results @solernou !
imgMsg.header will be corrected by ROS#, only if you call 'imgMsg.header.Update()'.
The corresponding method is here..
I also see no open point here for the ROS# side and close this issue.


#3326 - Add text field for query SMARTS advanced features

How the feature works? / How did you fix the issue?
https://github.com/epam/ketcher/assets/16281184/87e75cad-e150-421d-a74c-f093f7d01c4f
Check list

[ ] unit-tests written
[ ] e2e-tests written
[ ] documentation updated
[x] PR name follows the pattern #1234 – issue name
[x] branch name doesn't contain '#'
[x] PR is linked with the issue
[x] base branch (master or release/xx) is correct
[x] task status changed to "Code review"
[x] reviewers are notified about the pull request

Local report
reportLocal2.html.zip

Preview. No comments


feat/customer-information

What

Update admin view of customer details to enhance the experience as well as giving them the option to update first_name, last_name, phone and email (email only being if the customer has not signed up with the account).

Why

This is useful for administrators especially when a user may not have created their account themselves or signed up.

How

Modify customer/details and create an edit component.

The prices are still displaying wrong. Please see attached image and correct it :)
Also, only the order number should be blue.

The content of the rows is still blue :) Should only be the display order number as mentioned previously. @sebastiannicolajsen


broken models with same hash

Loading weights [e3b0c442] from /content/stable-diffusion-webui/models/Stable-diffusion/photorealistic-fuen-v1.ckpt
Loading weights [e3b0c442] from /content/stable-diffusion-webui/models/Stable-diffusion/vintedois_0_1.ckpt

fixed note: e3b0c442 this hash means empty


Can we know the slide number onchange?

Is their a way to track what slide number the user is on? like onchange get the slide number

That's a good question. Since google renders the actual slides I'm not sure that there is a callback handler for hooking into those internals. I'll poke around and see what I can find

hey guys @ajhenry
have you find a way to add a handler? thank you!!

Unfortunately I did not find a way to do it when I looked last year. I'm open to suggestions about how we might do this though!


Bounty: Upgrade the Cadastre’s Web3 wallet integration @ 250 xDAI

User Story
As a user, I want it to be super easy to connect my Web3 wallet of choice to the Geo Web Cadastre.
Why Is this Needed
A Web3 wallet is needed to transact on the Geo Web Cadastre. Right now, we are limited to a Metamask-only integration that isn’t intuitive for first time users.
Bounty Details
Type: Enhancement
Skill Level: Intermediate
Estimated Time: 5 hours
Bounty Amount: 250 xDAI
Acceptance Criteria
General

Enable loading of the appropriate Cadastre map and data without requiring a connection to a wallet (Kovan network is the only network currently)
Change the header tag from “Testnet” to “Kovan Testnet”
Prompt/warn the user to connect their Web3 wallet if they click on any transaction button, but have not yet connected their wallet

Wallet Connect

Integrate Web3Modal or Web-3 React library to add multi-option wallet support
Support injected wallet providers (eg Metamask, Frame, etc), WalletConnect, Torus, Portis, & Fortmatic
Show a warning that says “Wrong network - Please select the Kovan network in your wallet and try again” if the user attempts to connect their wallet but doesn’t select the right network.
Add a “Ok, try again” button to the “Wrong network” pop-up that returns the user to the wallet selection step

Additional Information
If you’re interested in claiming this bounty, please comment below and we’ll assign it to you, so we don’t end up with duplicate/competing submissions.
Questions can be directed toward Cody and Graven during development. Bounty is paid out upon successful completion of all acceptance criteria and PR merge.

@bschnelle Here's that first bounty that I mentioned. Take a look and let us know if you might be interested!


Try to add detailed steps for Vollausbau

As I struggled quite a bit with the switch from the nice step-by-step guide for the PID only setup to the "oh yeah just read the wiring diagram and figure it out" approach of Vollausbau, I decided to try and provide a more detailed list of steps.
However, I am by no means an expert, and tried to condense down the steps that I took, and the input that I received in the chat.
I hope that this can serve as a basis for additional edits/refinements, so that the project can soon provide a more beginner-friendly guide for the Vollausbau.

Thanks for this adition, merged!


Skills: Unknown intent is not an option for a task when creating a manifest.

Describe the bug
The unknown intent is the only logical task for my echo skill, as designed; however, I can't choose the unknown intent as the task the skill can perform.
Version
Version:  2.0.0-nightly.240624.c8283fa
Electron: 8.2.4
Chrome: 80.0.3987.165
NodeJS: 12.13.0
V8: 8.0.426.27-electron.0
Browser

[x] Electron distribution
[ ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[ ] macOS
[x] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Create a basic echo skill, once that does something based on any message that comes in.
Try to share the bot as a skill
Error: when you get to the Select which tasks this skill can perform dialog, the unknown intent trigger is not listed as an opion.

Expected behavior
A generic message activity should also be an option for a task a skill can start with, and presumably a generic event or invoke, too.
Screenshots

Additional context
Trying to figure out how to explain this wizard in the how to publish a skill article.

The unknown intent sounds like a by-default choice. I think user don't need to select it specifically, it is naturally supported. Either select or non-select it, the manifest will be generated for the same content. @darrenj @gabog, thoughts?

I will run with that assumption for now. The messaging in the UI is confusing on that front, but can be fixed later.

The default appears to be event, instead of unknown intent!
  "activities": {
    "EchoSkill": {
      "type": "event",
      "name": "EchoSkill",
      "description": "Skill for the local skills how to."
    }
  }

@luhan2017 Is this behaviour by design?
I.e we're assuming there insn't a scenario where a skill would handle unknown intent but the root bot would and therefore we dont expose it as a choice. We should verify this.
if its not by design or if we default to it - it should be exposed in the UI
@darrenj @mareekuh Can you help with some context here?
cc @mewa1024

My 2 cents:

Intents are sub types of message activities.
Unknown intents are a sub type of all activities, effectively.
If we don't allow the unknown intent to be included in the manifest, we don't allow a skill to handle a generic message without a recognizer in the consumer bot.

@gabog may be able to clarify.

@JonathanFingold When a skill receives a message activity it runs the dialogs recognizer to determine the intent. At that point, if the result is an unknown intent, the OnUnknownIntent handler is trigger exactly like how a known intent would trigger the OnIntent handler.
For the same reason OnIntent triggers aren't included in the generate skill manifest wizard, OnUnknownIntent triggers are not included. This is by design.

I'm a bit confused about the real-world scenario underpinning this, happy to be educated :-)
If I write a Bot which is intended to be used a skill I would have intents configured using one of the available recognizers. i.e. I'll have dialogs trigged by intents.  The triggers for these intents will have LU based training data so the bot knows where to direct each utterance.
When we switch to a skill, the goal of the manifest is to give the parent bot the information it needs to know when to pass an utterance across to the Skill. Utterances the Skill cannot handle should therefore not be passed across and handled by the parent bot and it's unknown handler as needed.
Therefore, having two levels of unknown intent handling doesn't feel right as the skill can say hey I've got all these utterances I can't handle but I'm going to advertise that I can meaning I may "steal" them away from the parent bot. I would therefore say that we should not support adding the unknown intent handler as per the current design. Open to discussion though!

@darrenj You are correct, the manifest is intended to communicate types of activities the skill can handle. When the developer adds an OnIntent trigger, we add a message activity to the manifest to indicate the skill can accept and process message activities. Adding an intent would result in the following manifest:
{
  ...
  "activities":  {
    "message": {
      "type": "message"
  }
}

If we allow a developer to add an OnUnknownIntent, they would be indicating that the skill can accept and process message activities, so the manifest would be exactly the same. Adding the ability to add OnUnknownIntent does not add much value, unless the skills only intent trigger is the OnUnknownIntent which is an edge case.
I'm on the fence about whether or not we should add OnUnknownIntent to the Select task step. It's probably more of a design question than anything else.

I've talked this through with a few to validate - I was right this is not a valid scenario. A skill should not advertise things it cannot call. A bot (or skill) should not wire up everything in say an unknown handler and should instead make use of triggers as that's the pattern for Composer first bots.
I don't believe this is a constraint and needs to be documented differently. However the copy on the UX does need changing and I believe is in flight @vivekkshankar ?

@vivekkshankar Did I already include this content or is it additional. LMK asap so I can add it - guys are implementing copy as we speak.


Feat: Hosted Spanish Docs

Docs PR Template
Why this should be merged

How this works

How these changes were tested

https://github.com/ava-labs/avalanche-docs/issues/1383


Github Releases and Tags did not match changelog

As I now want to update our internal version of Psake. I stuck at the release page witch only lists version v4.7.4 witch is from 2018. So I looked at at the tags. But the last tag is also v4.7.4. I can see that there are to more versions in changelog. But where can I find its tags/commits?
Can you please push the tags and add releases in github so the github releases matches the changelog.md.

@lanwin thanks for bringing this up!
I have just updated the Releases section to match the information that is in the changelog.
Please let me know if there is anything else that needs to be done.

Looks pretty good. Thank you!

Thanks @gep13!


⚠ Bofrost.lu has degraded performance

In 5b286d1, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1525 ms

Resolved: Bofrost.lu performance has improved in 128ff11.


fix: return $this from builder methods

[x] Added or updated tests
[x] Documented user facing changes

Related to #1871 and #1870 (but does not fully solve). Closes #1676. Should close #1538 (but will want to confirm).
Changes
Hello!
This PR updates the Builder methods to properly return $this (previously there was a mix of $this, static, and self) instead of creating new object classes.
I also included some slight refactors to simplify and improve the readability of the code---this includes things like removing duplicated code, returning early, reducing the number of indentation levels, etc. However, I've carefully segregated the changes into their own commits to make reviewing the changes easier---if the whole diff is a little hard to follow the individual commits should help to walk through the changes made.
Breaking changes
If users have specified the return type to be static or self they might need to update to $this (depending on their phpstan level).
Thanks!

As mentioned in https://github.com/larastan/larastan/issues/1538#issuecomment-1987873622, can confirm this solves the issues reported on #1538.

Hi,
Like I explained in other PR, this is not the way to go. Errors like this is always expected when you are analyzing the scopes, relations etc. itself. Because PHPStan does not have the right information. Most important thing is to look if there are errors or not when analyzing the code that calls these scopes/relations. If not then everything is fine 👍🏽
Thanks for understanding.

@canvural, this is the correct fix---all builder methods do return $this as opposed to self (a new instance of the declaring class) or static (a new instance of a child class). The same instance is returned and this PR correctly captures that.

Errors like these are always expected when you are analyzing the scopes, relations etc. itself. Because PHPStan does not have the right information. Most important thing is to look if there are errors or not when analyzing the code that calls these scopes/relations. If not then everything is fine

I would disagree here because

I completely agree with @calebdw, this is the correct solution. Even Laravel itself uses @return $this in the builder method docblocks, the builder methods always return the object itself, never a new instance.
As I see it, this PR does exactly what Larastan is supposed to do: it provides a Laravel specific solution to a Laravel specific PHPStan issue.

(preface: I'm not exactly sure about the specifications given I haven't checked this in a while, but let me try to join in based on the things I see and do remember)

Because PHPStan does not have the right information.

Isn't that exactly the originating problem and thus the whole point of this fix? Providing PHPStan with more accurate information, so it can check in a more accurate manner?
I do agree it would be much neater if there was some way where PHPStan could inherit that itself in some way, but it needs some form of input to do so, right? If this PR does exactly that (and I haven't heard yet of anything contradicting that), what exactly is the issue with proceeding in this?
Furthermore, if this would require some change on the PHPStan side, then probably it would be better to at least create some viable MWE to show where PHPStan could do better, report that at their end and then list that issue here as a blocker that should provide an alternate solution.

Again, this is not the correct solution.

the builder methods always return the object itself, never a new instance.

I don't understand this. There is no difference between those two in the eyes of static analysis.

Isn't that exactly the originating problem and thus the whole point of this fix? Providing PHPStan with more accurate information, so it can check in a more accurate manner?

PHPStan and Larastan already understands the code good enough when analyzing the builder calling code. So there is no problem there. The issue arrives when you analyze the builder class itself. But the issues there are low priority. And happens with even just PHPStan.

Again, this is not the correct solution.

@canvural, you're so adamant that this is not the correct solution, however, you've yet to provide the "correct" solution. I understand you haven't had time to fully work through the solution, but in your mind, what form would the "correct" solution take? Simply ignoring the errors is not a solution...

I don't understand this. There is no difference between those two in the eyes of static analysis.

This is simply not true---PHP itself only has self and static return types. If there was no difference between these static and $this "in the eyes of static analysis", then PHPStan would not have added the $this return type. I've found most often that the difference manifests itself in the retention of generic information (or lack thereof) when chaining method calls---particularly when these methods exist on a parent class/trait.
Here is what the ChatGPT has to say:

Prompt:

What is the difference between the static and the $this return type in PHPStan? Is there any difference in the eyes of static analysis? How does one over the other affect generic types where a certain where a certain class has the form Foo<Bar>?

In PHPStan, and more broadly in the field of static analysis for PHP, the return types static and $this are used to provide more specific type information, especially in a context where method chaining and inheritance are involved. Understanding the difference between these two is crucial for correct type hinting and can significantly affect how static analysis tools interpret the code, especially when dealing with generic types.
1. Understanding static and $this Return Types

$this Return Type: When a method's return type is hinted as $this, it indicates that the method returns the same instance of the class on which it was called. This is most useful in fluent interfaces where method chaining is expected. PHPStan understands that the returned type is exactly the same object as $this, with the same class and type parameters.
static Return Type: The static return type is similar but subtly different. It indicates that the method returns an instance of the same class where the method is defined, or possibly a subclass. This is particularly important in inheritance scenarios. static is a way to denote late static binding which means the return type will be the class of the object upon which the method is called, not necessarily the class where the method is defined.

2. Differences in Static Analysis
In the realm of static analysis, these differences are important:

Using $this: When $this is used as a return type, PHPStan (or any static analyzer) expects that the method will return exactly the same type of object, including all generic parameters. For instance, if a class is generic like Foo<Bar> and a method returns
'$this, PHPStan understands that the returned object is also of type Foo`.
Using static: The use of static allows for a more flexible return type, which can vary depending on the subclass from which it is called. If Foo<Bar> is a base class and Baz is a subclass, a method in Foo with a return type of static can return an instance of Baz. This is particularly useful in factory methods or when implementing the prototype pattern. However, this can introduce complexities in type inference, especially with generics, as static could refer to any subclass with potentially different type parameters.

3. Impact on Generic Types
When dealing with generic types like Foo<Bar>, the choice between $this and static can significantly affect type safety and correctness:

Methods Returning $this: These are straightforward in their implications. PHPStan will enforce that the returned object is not only of the same class but also maintains the same generic parameters. This is safer in terms of type correctness.
Methods Returning static: This allows for more flexibility, as subclasses can maintain or change the generic parameter. However, this can potentially lead to type safety issues if not properly handled. For instance, if a subclass does not correctly override generic parameters, it might lead to situations where the static analysis tool cannot accurately predict the type or enforces an incorrect one.

4. Conclusion
In summary, choosing between $this and static depends largely on the specific requirements of your codebase, especially regarding inheritance and method chaining. For maintaining strict type safety with generics, $this is more appropriate, whereas static offers more flexibility at the potential cost of type safety. Static analysis tools like PHPStan will treat these two differently, and understanding these nuances is key to leveraging these tools effectively for cleaner, more reliable code.

The issue arrives when you analyze the builder class itself. But the issues there are low priority.

I understand and respect that it's a low priority for Larastan, however, I would like Larastan to be able to analyze my builders without errors ( I'm not a fan of ignoring errors)---this is why I implemented the fix, because it wouldn't have been fixed otherwise (in the near term at least).
I've spent a lot of time on this, and I believe returning $this from the builders to be the most correct solution (although granted my implementation could probably be improved :sweat_smile:). Again, returning $this is exactly what the actual builder classes return, and this fixes the issues when analyzing the builder classes so I fail to see what about this implementation is so "incorrect" that it could not be merged (all the tests pass as well indicating nothing broke).
Path Forward
So then, what is the path forward and how do we fix the issue at hand? Going back and forth like this is not likely to change anyone's mind (although I hope I've presented the case well enough to change your mind :upside_down_face:). I want to work with you to fix the issue, not argue against you and nothing gets done. I would appreciate some direction instead just being shut down with "this is not the correct solution" and no indication of what the correct solution might be.
Thank you for your time and all the hard work you've put into this awesome package that we all love and want to make even better.


About obtaining the data set

Hello, I read your code and am very interested in this project. I have also recently been studying the operation of cables by a dual-Manipulator robot. Could you please share the method of obtaining the data set?

Hi, you can refer to the journal version of this work for a further improved shape control method and more details, including the description of the data collection method.


Solved Save function

Hey @pradeeban  ,
Now Save function works even when we try to save new files which is not working before
I removed that warning code which I added "directory="true" "
Now if there is Anything you would like to change please tell me

Please see last commit changes

The "Save" function was working fine, but only in Edge or Chrome. Hence the warning message indicating to switch to Edge/Chrome.
Do you mean this PR fixes the "Save" function for other broswers?
Please mention which browsers this was tested on.

Wait i will revert you about this

Actually the issue is that safari doesnot support any option to showSaveFile , so the only option we are left with firefox is that it provides the feature that it install file in the last saved directory
Actually this is requested that firefox would provide this feature

Ok, I will keep the PR on hold as currently, concore-editor only support Edge and Chrome.

The "Save" function was working fine, but only in Edge or Chrome. Hence the warning message indicating to switch to Edge/Chrome.
Do you mean this PR fixes the "Save" function for other broswers?
Please mention which browsers this was tested on.

It gives the above error in chrome and firefox
Above pic is of chrome browser


Snippet plugins seem not to work

The integration of the extension with all of my other Neovim plugins is seamless, however I cannot trigger the insertion of any code snippet.
I have currently tried both Ultisnips and Snipmate with no results.
Is the behavior expected?
I read the documentation and searched through the other issues here on Github but I've got no clues.

I think default vscode snippet engine was supposed to be used.

The key tradeoff made by this plugin, and mentioned in the readme, is that insert-mode is controlled by vscode. Using a vscode snippet plugin.


Aliases are not honored on SAP

What Happened?
I uses page aliases in Logseq, which are working great locally. After this GH action has rendered and published those pages the aliases are no longer honored. Instead links points to unrefrerenced pages with the name of the alias.
Reproduce the Bug
There's no need to reproduce the bug since all my work is public on this repo as well as GH action's log can be audited from here.
You can verify for instance that on this block I mention:
Retrieve [[ASREPRoast]] hashes

which is an alias for the AS-REP Roasing.

Nevertheless, if you click on the link on the mentioned block it points to
https://staypirate.github.io/HTB-Notes/#/page/asreproast
instead of
https://staypirate.github.io/HTB-Notes/#/page/as-rep%20roasting
I want to highlight again that locally the alias works, the problem is only present on the published pages. Which makes me think that the bug should rely on this GH actions.
You can test that the alias locally works by cloning my repo and open it on you Logseq client.
Expected Behavior
The aliases should be honored on the SAP the same way the Logseq client does.
Desktop or Mobile Platform Information
I locally run Logseq v0.9.20 via Flatpak:
❯ flatpak info com.logseq.Logseq

Logseq - A local-first, non-linear, outliner notebook for organizing and
sharing your personal knowledge base

          ID: com.logseq.Logseq
         Ref: app/com.logseq.Logseq/x86_64/stable
        Arch: x86_64
      Branch: stable
     Version: 0.9.20
     License: AGPL-3.0-or-later
      Origin: flathub
  Collection: org.flathub.Stable
Installation: user
   Installed: 425.3 MB
     Runtime: org.freedesktop.Platform/x86_64/23.08
         Sdk: org.freedesktop.Sdk/x86_64/23.08

      Commit: bf636be62e77efc1b529f79eabaa6f5eac551da6141a2d8e98dbd2449782552d
      Parent: 34810510e13c9cf47043d5c10488a3eb3a028442ef2221f7bb6528fb0283f1f7
     Subject: Update runtime to 23.08 (0769284e)
        Date: 2023-11-11 18:36:41 +0000

0.3.0 has been released. Can you see if clicking on page ref aliases is working?

Problem solved, thank you!


iOS - Chat - No preview when attaching large pdf file

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

Action Performed:

Open app and login
Tap on any chat
Tap on + sign > Add Attachment > Choose document
Choose the attached file in the issue (a large pdf file)

Expected Result:
Verify a preview of the PDF is displayed before uploading to the conversation
Actual Result:
The preview of the pdf file is not showing
Workaround:
Unknown
Platform:

Where is this issue occurring?

iOS

Version Number: 1.1.32-0
Reproducible in staging?: yes
**Reproducible in production?:**cyes
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
[OMCre

https://user-images.githubusercontent.com/43996225/150619179-3716b0a4-9c04-4550-93c4-a28d787c309c.mp4
ate Battery User  Manual (1).pdf](https://github.com/Expensify/App/files/7917369/OMCreate.Battery.User.Manual.1.pdf)
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
View all open jobs on GitHub

Triggered auto assignment to @johnmlee101 (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

This has to deal with our PDF view most likely here: https://github.com/Expensify/App/blob/d6a607324f84e654da2da6e073b150a00def7490/src/components/AttachmentView.js#L48
so that would be a great starting place to fix this. Should be fine marking as External

Triggered auto assignment to @SofiedeVreese (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

I'm going to have to reassign this one, I'm sorry. I'm back from OOO and autoassigner is playing catch-up so I'm absolutely smashed with assigned GHs atm.

Triggered auto assignment to @trjExpensify (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

👋 Job on upwork is here: https://www.upwork.com/jobs/~011ea8673c607beed8
@kavimuru, just to confirm.. this issue was reported by Applause, right? That detail is missing from the OP.

Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat (Exported)

@trjExpensify updated reporter to Applause

Issue not reproducible during KI retests. (First week)


Add double tap to go forward/backward in DefaultPlayerUIController

@PierfrancescoSoffritti
If you notice the youtube app, its buggy most of the time since half the time, I wasn't sure where to tap and until the tap is made, the player also doesn't come up.

Are we going with similar approach of double tap on screen ?
Or should we introduce the -10 & +10s icons to the left and right of the play/pause button ? (Similar to what Amazon prime does ?

Solution number 2 is basically already implemented, using setCustomAction1 and setCustomAction2. It's just a matter of doing seekTo(time +- 10). Users of the library can take care of that.
I think solution 1 is more interesting. It shouldn't be too hard to achieve, all is needed are 2 transparent views that cover one half of the screen each. These views can then be used to detect double taps.
I think the trickiest thing to implement (but i may be wrong) may be the detection of multiple double taps. eg: if the user taps 4 times on the right view, the player should seek to currentTime + 20 instead of currentTime + 10.

Ha. That's interesting. I just checked out the latest youtube app and the double tap issue seems to be fixed and it's working beautifully.
Also, about the multiple double tap, I think once the first double tap activates the fast forward (backward) mode, then the player doesn't differentiate between single/double tap. I was able to increment in single 10s counts also.
Let's try and emulate the exact behavior of the native app.  Would be happy to take this up.

You're right. After the first two taps it's only one to skip 10 seconds.
Sounds great to me, thanks for helping :)

Hey @PierfrancescoSoffritti, I have an issue related to the custom actions. I set the actions in initlistener method using the YouTubePlayerTracker class. The buttons appear at first when the video player is initializing but when the video starts to play the buttons disappear. This is the code I used, where ytVideo is the YouTubePlayerView: `
ytVideo.initialize(new YouTubePlayerInitListener() {
                @Override
                public void onInitSuccess(@NonNull final YouTubePlayer youTubePlayer) {
                    final YouTubePlayerTracker tracker = new YouTubePlayerTracker();
                    youTubePlayer.addListener(tracker);
                    PlayerUIController playerUIController = ytVideo.getPlayerUIController();
                    playerUIController.setCustomAction2(ContextCompat.getDrawable(ContentPageActivity.this, R.drawable.ic_forward_white_24dp), new View.OnClickListener() {
                        @Override
                        public void onClick(View view) {
                            float seekTo = tracker.getCurrentSecond() + 10;
                            youTubePlayer.seekTo(seekTo);
                        }
                    });
                    playerUIController.setCustomAction1(ContextCompat.getDrawable(ContentPageActivity.this, R.drawable.ic_back_white_24dp), new View.OnClickListener() {
                        @Override
                        public void onClick(View view) {
                            float seekTo = tracker.getCurrentSecond() - 10;
                            youTubePlayer.seekTo(seekTo);
                        }
                    });
                    playerUIController.showCustomAction1(true);
                    playerUIController.showCustomAction2(true);
                    youTubePlayer.addListener(new AbstractYouTubePlayerListener() {
                        @Override
                        public void onReady() {
                            String videoId = getYouTubeId(mContentPageResponse.getContent());
                            youTubePlayer.loadVideo(videoId, 0);
                        }
                    });
                }
            }, true);`

@abahl817  this problem is not related to this issue, I suggest you open a new issue.

@abahl817 this problem is not related to this issue, I suggest you open a new issue.

Okay, fine


re-sign ins with useChains

@adairrr Is there any more info about the issue? i.e. what the re-sign in issue exactly is? what’s the steps to reproduce the error?


dotenv: make it possible to define the file you would like to use

It would be good to have the ability to set the file's name  you would like to use for the env (I for example have a problem with .env file because it is not recognized by my pycharm EnvFle plugin)

Are you referring to the dotenv file? If so, this would be a simple change, just define a ZSH_DOTENV_FILE variable that defaults to .env and use that in the source_env function wherever it says .env:
https://github.com/robbyrussell/oh-my-zsh/blob/bb64446ebf51ef9ab8c6cf9f2569a0900529861e/plugins/dotenv/dotenv.plugin.zsh#L1-L14
Then add it to the README and it's done. Care to submit a PR?

I would like to take this up, if its still available

Absolutely, go ahead thanks!

Are you referring to the dotenv file? If so, this would be a simple change, just define a ZSH_DOTENV_FILE variable that defaults to .env and use that in the source_env function wherever it says .env:
https://github.com/robbyrussell/oh-my-zsh/blob/bb64446ebf51ef9ab8c6cf9f2569a0900529861e/plugins/dotenv/dotenv.plugin.zsh#L1-L14
Then add it to the README and it's done. Care to submit a PR?

I would need some more help. So as per my understanding, I have to create a temporary variable ZSH_DOTENV_FILE = .env
and then replace .env with ZSH_DOTENV_FILE in the function.
This should be defined inside the function above, or somewhere else.
What and where exactly this needs to be added in README.
This is my first contribution to oh-my-zsh, so might need help understanding the codebase

Ok let me run down the list of steps:
The plugin should:

Check if ZSH_DOTENV_FILE is defined, and set it to .env if it's not defined. This should go outside the source_env function, preferrably before it. You can do this two ways:

Check if $ZSH_DOTENV_FILE is empty, then set it. This is done with [[ -z $variable ]].

Use parameter expansion to set it to the default value .env. This would look like:
: ${ZSH_DOTENV_FILE:=.env}

Replace where it says .env with $ZSH_DOTENV_FILE in the source_env file.

In the echo dotenv error line you'll have to use double quotes (as well as using $ZSH_DOTENV_FILE instead of .env), and substitute the backticks (`) with single quotes (this last part is because backticks are interpreted as wanting to run a command):
echo "dotenv: error when sourcing '$ZSH_DOTENV_FILE' file" >&2

In the README, add a section called Settings or Configuration and document that there is this setting available, describe it and what its default value is. There is a GitHub Markdown guide available if you need it.

@mcornella I gave it a first try. Diff looks something like below
diff --git a/plugins/dotenv/dotenv.plugin.zsh b/plugins/dotenv/dotenv.plugin.zsh
index b701b559..abd26e5c 100644
--- a/plugins/dotenv/dotenv.plugin.zsh
+++ b/plugins/dotenv/dotenv.plugin.zsh
@@ -1,13 +1,13 @@
 source_env() {
-  if [[ -f .env ]]; then
+  if [[ -f $ZSH_DOTENV_FILE ]]; then
     # test .env syntax
-    zsh -fn .env || echo 'dotenv: error when sourcing `.env` file' >&2
+    zsh -fn $ZSH_DOTENV_FILE || echo `dotenv: error when sourcing '$ZSH_DOTENV_FILE' file` >&2

     if [[ -o a ]]; then
-      source .env
+      source $ZSH_DOTENV_FILE
     else
       set -a
-      source .env
+      source $ZSH_DOTENV_FILE
       set +a
     fi
   fi
@@ -16,4 +16,9 @@ source_env() {
 autoload -U add-zsh-hook
 add-zsh-hook chpwd source_env

+if $ZSH_DOTENV_FILE is empty; then
+  [[ -z $variable ]]
+else
+  : ${ZSH_DOTENV_FILE:=.env}
+
 source_env

I can't find Settings or Configuration in the main readme.
Is it in some other readme.

+    zsh -fn $ZSH_DOTENV_FILE || echo `dotenv: error when sourcing '$ZSH_DOTENV_FILE' file` >&2

Here the backticks (`) should be substituted with double quotes ("). Backticks are interpreted by the shell as "run whatever is inside it as a command". For example,
$ ls `echo /`

will run echo /, and pass that as an argument to ls, meaning it will eventually run ls /. See this stackoverflow question for more information.

As per

+if $ZSH_DOTENV_FILE is empty; then
+  [[ -z $variable ]]
+else
+  : ${ZSH_DOTENV_FILE:=.env}

I think I didn't make myself clear. You should use either one method or the other, not both in an if-else expression. Also, [[ -z $variable ]] is the construct to check if $variable is empty, so
if $ZSH_DOTENV_FILE is empty; then
    [[ -z $variable ]]

isn't correct. It should be [[ -z $ZSH_DOTENV_FILE ]]:
if [[ -z $ZSH_DOTENV_FILE ]]; then
    ZSH_DOTENV_FILE=.env
fi

Lastly,

I can't find Settings or Configuration in the main readme.
Is it in some other readme.

The section doesn't exist yet, you should create it yourself.

@mcornella I have sent a PR for this.
Can you also check my changes and README content, whether it makes sense.


Segfaults are not showing

Added hotfix but must be investigated more

This is mainly problem with original js++ compiler since it outputs SegFault directly into TTY which makes it impossible to catch.
Hotfix contains a check if error exit code matches ones I've got and if so then it outs error


Code change is hard to see if that really works.

In section Update the app, we ask developers to change max length of choice field to 100. And then redo migrate and deployment.
It works fine but from end user perspective, it's really hard to verify if this change works. That is just a small box in admin page, hard to count if I typed more than 100 characters.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1a96d5fc-0dd1-a344-5416-44039cee39b8
Version Independent ID: 72844ca4-b087-de15-be00-e0d87020a48b
Content: Tutorial: Deploy a Python Django app with Postgres - Azure App Service
Content Source: articles/app-service/tutorial-python-postgresql-app.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

@shizn, Thanks for the feedback! We are taking a look into this and will get back to you soon.

Xin, Apologies for the delay. If I have understood your question correctly - The tutorial aims to provide key concepts and instructions for containerization of Linux apps in App Service, the doc meant to show something more involved, but still allow users to learn things beyond a specific framework. It provides step-step process on how to connect WebApp to an Azure Database for Postgres database, view diagnostic logs, manage the web app in the Azure Portal. it doesn’t mean to teach Django web server/administering local admin console. For validation on the admin console page/localhost config, you can check out these discussion thread -The Django DB Docs, ref validators, SO thread .
Hope this helps! Thanks again for your feedback. We will close this for now.


Self_alignment error

Hi
I'd like to align raw signal to basecalled result generated from dorado with move table. But pysam module in your code can't read the
bam file. Here's my code and error message.

uncalled4 align --self --reads batch0.pod5 --bam-in batch0_seq_sort.bam --eventalign-out --eventalign-flags print-read-names,signal-index > test_uncall.txt

ValueError: file has no sequences defined (mode='rb') - is it SAM/BAM format? Consider opening with check_sq=False

I added "check_sq=False" to the code, but got another error. Bam file was transformed from basecaller's sam output by samtools.
 File "/path/uncalled4/__main__.py", line 358, in main
    ret = fn(conf=conf)
          ^^^^^^^^^^^^^
  File "/path/uncalled4/align.py", line 40, in align
    dtw_single(conf)
  File "/path/uncalled4/align.py", line 159, in dtw_single
    dtw = Aligner(tracks, aln)
          ^^^^^^^^^^^^^^^^^^^^
  File "/path/uncalled4/align.py", line 260, in __init__
    if self.renormalize(signal, self.aln):
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/path/uncalled4/align.py", line 311, in renormalize
    mask = na_mask & dist_mask
           ~~~~~~~~^~~~~~~~~~~
ValueError: operands could not be broadcast together with shapes (923,) (922,)


working_capacity2

…he difference between loadings

Yep, so per our conversation this is a hack but should work. We want to redo this by:

converting simulation files in a class
adding the data in a new data table via a join
allowing for arbitrary simulations to be added in any number, via the config file

but ok for now.


version update

Hi,
Default go mod points to v1.0 which has IPv4s bug. You should update module version to include the fix.
Thanks.

It seems updated.


lang: add anchor-zero-copy-repr-packed feature flag

Addresses https://github.com/project-serum/anchor/issues/1198.
Not sure the best way to write a test for this! If you have a suggestion I can add that as well
I tested locally by running the following in tests/chat/programs:

cargo expand
cargo expand --features anchor-zero-copy-repr-packed

What do you think about an argument instead of a feature flag. E.g. #[account(zero_copy, packed)]

Yeah I think that's probably nicer! Haven't worked in this part of the anchor code before, if you could link me to an example commit that does something similar, it might help me out

@crispheaney you can check if the repr attribute is on the syn::ItemStruct here https://github.com/project-serum/anchor/blob/master/lang/attribute/account/src/lib.rs#L292
See https://docs.rs/syn/1.0.85/syn/

This is supporting #[account(zero_copy, packed)] now.
I see @paul-schaaf suggested we support #[account(zero_copy, repr = packed)]. Do yall have an example on the cleanest way to parse the repr = packed? (Sorry I'm a marco noob)

@crispheaney
armani and I (we shouldve had the discussion here in the open mb) thought it would be better to have
[account(zero_copy)]
[repr(X)]

X being your desired alignment config
if the user marks it with a [repr(X)], use that. if there is none. add [repr(C)] to the struct.
you can still do that in the function of the account macro attribute

Implemented the repr override here https://github.com/project-serum/anchor/pull/1273

we have the override now so Im closing this


AADSTS65001 Error in multi-tenant app registration

Environment

Spring boot starter:

active directory spring boot starter

OS Type: MacOS

Java version:

1.8

Summary
Accessing an application from another tenant results in an 'AADSTS65001: The user or administrator has not consented to use the application with ID' error, even though the service principle has been granted access from the Azure portal.
Reproduce steps

Create bare-bones Spring Boot AAD app.
Register this in AAD, following the steps outlined at https://docs.microsoft.com/en-us/java/azure/spring-framework/configure-spring-boot-starter-java-app-with-azure-active-directory?view=azure-java-stable
Verify a successful login in the original tenant
Add the application to another tenant, and grant admin access to the service principle via the azure console.
Observe the error 'AADSTS65001: The user or administrator has not consented to use the application with ID' when trying to log in with a user from the tenant other than that which the application is registered in

Expected Results
I expect to be able to log in with a user from a different tenant.

@Incarnation-p-lee
Spring is version 2.0.6, Azure AD starter is 2.0.7. The user name definitely exists in the tenant that I am trying to log in from.

@TimSin
Can you reproduce that from chrome incognito mode ?

Looks like this was down to the tenant ID value being incorrect. Evidently this needs to be set to 'common' for multi tenant apps. Altering this has corrected the issue.
 azure:
  activedirectory:
    tenant-id: common

Could this be added to the documentation on the intro page?

@TimSin
Thanks for your information. These tips lays in our sample README, you can find the information from FAQ section here.
https://github.com/Microsoft/azure-spring-boot/tree/master/azure-spring-boot-samples/azure-active-directory-spring-boot-backend-sample


Is not work on ssl

Is not work on ssl
How run ssl on server

You must modify the code. This can be a feature request.

ok

I tested the beta and it worked with ssl but sometimes there are some bugs like second user screen crashing when entering a room. And sometimes when trying to join a two player room, the second user stays out but the room fills up and nothing happens.
I tried to install the release version on the ubuntu server (npm i) as root user but I get the error: permission denied, stat '.../root/.cache/electron/ SHASUMS256.txt'.

Not sure what the npm i error is about. The first problems you mentioned is known and isn’t just in ssl. See https://github.com/ethanaobrien/emulatorjs/issues/69  The solution is unknown and the problem is unknown


OpenEXR_Viewers  / libCg aliasing error

I'm building openexr with externalproject_add as a third party library for my application.  I was using 2.3.0, and everything was working - including the viewers.  I install Nvidia_Cg in an earlier step, and now it appears that the viewer's CMake isn't working like it used to.  It appears that this effects both 2.4.0 and 2.4.1.
I'm getting the following error about aliasing imported libraries
NOTICE-- Found Cg library
CMake Error at OpenEXR_Viewers/config/LocateCg.cmake:18 (add_library):
  add_library cannot create ALIAS target "Cg::Cg" because target "Cg" is not
  a library.
Call Stack (most recent call first):
  OpenEXR_Viewers/CMakeLists.txt:51 (include)

CMake Error at OpenEXR_Viewers/config/LocateCg.cmake:30 (add_library):
  add_library cannot create ALIAS target "Cg::CgGL" because target "CgGL" is
  not a library.
Call Stack (most recent call first):
  OpenEXR_Viewers/CMakeLists.txt:51 (include)

I can see that libCg.so exists, and it finds it, but gets hung up here.
Thoughts?

The OpenEXR_Viewer code is ancient and almost completely useless, it's not a functional viewer, it exists only as example code, but the dependencies are complicated and frequently problematic.
We discussed in the TSC and decided to remove the OpenEXR_Viewer code from the cmake build rules in the 2.5 release and then remove the code entirely in the 3.0 release, when the structure of the repo is rearranged.

@cary-ilm I had read that in some of the other commentary after submitting the report.  I'm not actually using my myself, but I was trying to build with all the available options turned on as a sanity check.  I hate to leave anything left to chance, but I'll turn it off for now and let it be if it's going to be removed down the road.
Thanks for the reply,
Kyle

#676 removes OpenEXR_Viewers from the cmake build process, and removes references to it in the INSTALL instructions. The code will be retired in the 3.0 release later in the year.  This hopefully resolves the issue, closing for now.


planning: Cortex Engines Management integrates with Jan data folders

Problem

the new cortex engines management broke Jan 0.5.8 (works successfully on cortex v1.0.2-rc4)
We will need to handle Jan's data folders to integrate with the upcoming changes for Cortex Engine Management
@louis-jan and @namchuai could you add your thoughts here?

Related to
#1416
#1638
Success Criteria
Tasklist

[ ]

Hi @gabrielle-ong I think we can close this issue. I'm filing a new issue from Jan here since it's easier to do from Jan for now. (E.g. packaging)
https://github.com/janhq/jan/issues/4025

Jan will download engine artifacts and structure them accordingly on CI when building the app.
Jan sets a default engine variant on load and settings changes.

This fixes from cortex.cpp, unblocked Jan integration already.
https://github.com/janhq/cortex.cpp/pull/1687

Thank you @Louis! closing this issue


chore(test): validate the commit messages on travis

Ref #158

Maybe we should validate the commit message format only in after_success from travis. Thus allowing pushes to check for passing tests before checking for the commit message format. Should be better?

Maybe we should validate the commit message format only in after_success from travis. Thus allowing pushes to check for passing tests before checking for the commit message format. Should be better?

The issue with after_success is that it doesn't affect the build result. I think it's OK to fail because of a commit message and without running the tests, no?

I think it's OK to fail because of a commit message and without running the tests, no?

It will be a pain for developers in the end, maybe we can just run the check AFTER the tests, that was initially what I wanted to do.
Knowing that the tests are passing here is way more important than having the commit message check failing right away (a bit like asking for lint before tests, it's a pain).
I wish travis exposed ways to have multiple status checks (https://github.com/blog/1227-commit-status-api) but no. The only way to have something better is to make a contribution bot run and do checks inside various status checks. This way you can see that the tests are passing but not the commit check.
For now, checking the commit status after the tests should be enough to keep a good flow.

For now, checking the commit status after the tests should be enough to keep a good flow.

Works for me, updated!

also that's awesome you did it :)

Just a note: you can also use local git hooks to test for commit messages and tests before pushing.

Just a note: you can also use local git hooks to test for commit messages and tests before pushing.

Yes, that's what Angular is doing with a "initialization" script to run setting it up after cloning the repo.

Yes, that's what Angular is doing with a "initialization" script to run setting it up after cloning the repo.

Yes but I think I saw somewhere they wanted to do it in travis also


zed: yoga merge

Update package update testing instructions (#830)
fix!: manage the physical interface in ci-aio
Bump kayobe-automation

This will need forcing merging as we don't perform a elasticsearch to opensearch migration hence the failure during upgrade.