primordic/IssueDupesLite huggingface dataset:
Repository: microsoft/vscode-docs

Issue #3428: A11y_code.visualstudio.com_WCAG2.1_Homepage_Orientation: When the orientation is changed to portrait, 2 scroll bars appears One vertical and another horizontal bar.
Created: 2020-02-27T08:33:55Z
“Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.”
GitHubTags: #A11ySev1; #A11yTCS; #A11yWCAG2.1; #Benchmark;#ChromiumEdge; #Orientation; #DesktopWeb; #MAS1.3.4; #Win10; #Visual Studio Code; #A11y_code.visualstudio.com_WCAG2.1;#A11y_WCAG2.1_FEB2020; #A11yMAS
Environment Details:
Application Name: code.visualstudio.com
#URL:https://code.visualstudio.com/
Windows Version: Windows10
Browser version: Microsoft Edge 80.0.361.5
Chrome:Version 80.0.3987.106
Repro Steps:

Launch the application URL: https://code.visualstudio.com/
Home screen will open
Navigate to display in setting-->system-->display orientation-->portrait.

Actual:
When the orientation is changed to portrait, 2 scroll bars appears One vertical and another horizontal bar.
Expected:
When the orientation is changed to portrait, only 1 scroll bars should appear vertical or horizontal.
User Impact:
Users will find it difficult to view the data in a single layout .
Attachment:
#3428.zip

Duplicate issue #5531: A11y_Visual Studio Code Services_Home_Reflow: There are two scrollbars present on the screen one is horizontal scrollbar and other is vertical scrollbar.
Created: 2022-08-04T13:00:26Z
“Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.”
GitHubTags:#A11yMAS;#A11yTCS;#A11yWCAG2.1;#BM_Visual Studio Code Services_Aug2022;#Visual Studio Code Services;#Win10;#FTP;#DesktopWeb;#A11ySev3;#WCAG1.4.10;#Reflow;#Chrome;
Environment Details:
Application Name: Visual Studio Code Services
URL: https://code.visualstudio.com
Windows Version: Win10
Chrome Version: Version 103.0.5060.134(Official build)(64-bit)
Pre-requisite:

Press "Ctrl+Shift+I" to open developer tool.
Now in dock side click on "undock into separate window" so that developer tool will get open in separate window.
Adjust the screen to 320px*256px.

Repro Steps:

Please do not close this bug. This bug should only be closed by TCS, C+AI Accessibility tester after verification of the fix
Launch the application Url : https://code.visualstudio.com
Do reflow and observe
Check whether there are two scrollbars horizontal and vertical scrollbar present on the screen or not.

Actual:
There are two scrollbars present on the screen one is horizontal scrollbar and other is vertical scrollbar.
Expected:
When we apply reflow resolution only one vertical scroll bar or one horizontal bar must be present on the screen
User Impact:
Reflow users will not be able to view the screen in one dimension scrolling
Attachment

Closing comment (2022-09-22T14:23:10Z): Duplicate of #3428
Repository: microsoft/vscode-docs

Issue #5911: Incorrect steps mentioned on VS Code website to deploy Azure App Service
Created: 2023-01-05T12:01:00Z
The steps mentioned on this link:
https://code.visualstudio.com/docs/java/java-on-azure
for the following:






Tutorial
Description
Related Tools




Deploy Java web appsto Azure App Service
Deploy a web app to the cloud
Apache MavenAzure App Service


Deploy Spring Boot appsto Azure Spring Apps
Deploy a Spring Boot applicationto Azure Spring Apps
Apache MavenAzure Spring Apps






The above articles provide steps to deploy App Service from VS Code. The steps are wrong and they are not working for:
https://code.visualstudio.com/docs/java/java-webapp
https://code.visualstudio.com/docs/java/java-spring-apps
It should be as follows:

Clone the Sample Project
Optional: Create the App Service with Linux, Java 17, and Java SE from Azure Portal. Could not create the App Service from VS Code.
Follow the steps from here to config the project for Azure deployment:
https://learn.microsoft.com/en-us/azure/app-service/quickstart-java?pivots=platform-linux-development-environment-maven&tabs=tomcat

PS> mvn com.microsoft.azure:azure-webapp-maven-plugin:2.5.0:config
PS> mvn package azure-webapp:deploy

The above PS commands will also create the App Service and deploy it.
Please fix the relevant web pages.

Duplicate issue #5921: Incorrect steps mentioned on VS Code website
Created: 2023-01-05T11:51:06Z
The steps mentioned on this link:
https://code.visualstudio.com/docs/java/java-on-azure
for the following:






Tutorial
Description
Related Tools




Deploy Java web appsto Azure App Service
Deploy a web app to the cloud
Apache MavenAzure App Service


Deploy Spring Boot appsto Azure Spring Apps
Deploy a Spring Boot applicationto Azure Spring Apps
Apache MavenAzure Spring Apps






The above articles provide steps to deploy App Service from VS Code. The steps are wrong and they are not working for:
https://code.visualstudio.com/docs/java/java-webapp
https://code.visualstudio.com/docs/java/java-spring-apps
It should be as follows:

Clone the Sample Project
Optional: Create the App Service with Linux, Java 17, and Java SE from Azure Portal. Could not create the App Service from VS Code.
Follow the steps from here to config the project for Azure deployment:
https://learn.microsoft.com/en-us/azure/app-service/quickstart-java?pivots=platform-linux-development-environment-maven&tabs=tomcat

PS> mvn com.microsoft.azure:azure-webapp-maven-plugin:2.5.0:config
PS> mvn package azure-webapp:deploy

The above PS commands will also create the App Service and deploy it.
Please fix the relevant web pages.

Closing comment (2023-01-06T16:28:24Z): Duplicate of #5911
Repository: microsoft/vscode-docs

Issue #448: Consider moving 'Node Debugging' section out of 'Debugging' 
Created: 2016-07-04T16:14:51Z
IMO the 'Debugging' chapter has this purpose:

give an overview of the runtime-independent debugging functionality of VS Code (some of this is shown for node.js because there is no 'generic' debugger),
serve as a 'trampoline' for the builtin (or almost-builtin) debug extension for JS, TS and .NET Core,
serve as a 'trampoline' for other debug extensions on the marketplace.

With this it does not make a lot of sense to have very detailed feature explanation for node.js inlined in this chapter. I suggest to move everything under 'Node Debugging' into 'Runtimes/Node.js'
/cc @isidorn @egamma

Duplicate issue #712: Break "Node Debugging" out onto its own page
Created: 2016-12-12T19:18:34Z
I think there's a lot more that could be said about node debugging, especially troubleshooting. Since the "Node debugging" section is already almost half the debugging page, I think it might deserve its own page, beyond being a section of the general debugging page.

Closing comment (2016-12-12T19:29:28Z): Duplicate of #448. Andre agrees.
Repository: microsoft/vscode-docs

Issue #5546: A11y_Visual Studio Code Services_Download Insiders_Keyboard: The "See SHA-256 Hashes" control is a button but visually it appears as a link.
Created: 2022-08-05T10:13:26Z
“Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.”
GitHubTags:#A11yMAS;#A11yTCS;#BM_Visual Studio Code Services_Aug2022;#Visual Studio Code Services;#Win10;#FTP;#DesktopWeb;#A11ySev2;#WCAG3.2.4;#Keyboard;#Chrome;#Closed;
Environment Details:
Application Name: Visual Studio Code Services
URL: https://code.visualstudio.com/
Windows Version: Win10
Chrome Version: Version 103.0.5060.134(Official build)(64-bit)
Repro Steps:

Please do not close this bug. This bug should only be closed by TCS, C+AI Accessibility tester after verification of the fix
Launch the application Url : https://code.visualstudio.com/
Tab till "Download" button.
Scroll down the page and hit enter on "Insiders build" link.
Tab till button "See SHA-256 Hashes".
Observe that "See SHA-256 Hashes" is a button but visually appearing as link.

Actual:
The "See SHA-256 Hashes" is a button but visually it is appearing as a link.The visual appearance of this contol as a link is not consistent.
Expected:
The "See SHA-256 Hashes" control is a button and visually should also appears as a button. All buttons should be consistent in appearance visually.
User Impact:
Keyboard users will get confused with the control appearance as a link and function as a button.
Attachment

Duplicate issue #6222: A11y_Visual Studio Code Service_Download_Download VS Code_Usability: Visually "See SHA-256 Hashes" button looks like a link.
Created: 2023-04-12T10:55:19Z
GitHub Tags
#A11ySev4; #A11yTCS; #A11yWCAG2.1; #Chrome; #DesktopWeb; #Win11; #Visual Studio Code Services; #BM_VisualStudioCodeServices_Web_Apr2023; #A11yUsable; #Closed;
Environment Details
Application Name: Visual Studio Code Services
URL: https://code.visualstudio.com/
Microsoft Windows 11 Enterprise 10.0.22621 Build 22621
Chrome Version 112.0.5615.49 (Official Build) (64-bit)
Repro Steps

Hit the application URL: https://code.visualstudio.com/
Tab till "Download" button and press enter.
Tab till "See SHA-256 Hashes" button.
Verify whether the See SHA-256 Hashes button visually also looks like button or not.

Actual Result
Visually "See SHA-256 Hashes" button looks like a link.
Expected Result
Visually "See SHA-256 Hashes" button should be looks like a button only.
User Impact
User will not able to differentiate the "See SHA-256 Hashes" control as button or link.
Attachment

Closing comment (2023-04-13T18:59:03Z): Duplicate of #5546 for added context
Repository: microsoft/vscode-react-native

Issue #1026: Command failed: adb -s "emulator-5554" shell getprop ro.build.version.sdk
Created: 2019-06-10T07:32:16Z
Actual Behavior

Can't debug app.I'm getting 'Command failed: adb -s "emulator-5554" shell getprop ro.build.version.sdk' error. I tried to run this command from cmd and it worked.

Expected Behavior

Run debugger without errors.

Software versions

React-Native VS Code extension version: 0.9.3
VSCode version: 1.35.0
OS platform and version: Windows 10
NodeJS version: 10.16.0
React Native version: 0.57.8

Outputs (Include if relevant)

Output of the Debug Console (View -> Toggle Debug Console):

Could not debug. Error while executing command 'adb -s "emulator-5554" shell getprop ro.build.version.sdk': Command failed: adb -s "emulator-5554" shell getprop ro.build.version.sdk


Output of the React-Native output channel (View -> Toggle Output -> Select React-Native in ListBox):

Error: Error while executing command 'adb -s "emulator-5554" shell getprop ro.build.version.sdk': Command failed: adb -s "emulator-5554" shell getprop ro.build.version.sdk

Duplicate issue #1027: Extension Debugging not working after Update SDK tools
Created: 2019-06-13T10:40:39Z
Actual Behavior

Before UPDATE SDK Tools Android, Extension Debugging console working, just fine!

Expected Behavior

After UPDATE SDK Android Tools, Extension Debugging not working

Without Extension, manual command debug running normally and use Chrome Debugging http://localhost:8081/debugger-ui/
Software versions

Android SDK version: 26.1.1
Android SDK Platform-Tools: 29.0.1
React-Native VS Code extension version: 0.9.3
OS platform and version: [Devices] Android 9.0 (API-28)
NodeJS version: 10.2.0
React Native version: 0.59.9
React Native Cli: 2.0.1
VSCode version: 1.35.1

Outputs (Include if relevant)

Output of the Debug Console (View -> Toggle Debug Console):

Could not debug. Error while executing command 'D:\Android\tools\sdk\platform-tools\adb -s "10.9.27.25:5555" shell getprop ro.build.version.sdk': Command failed: D:\Android\tools\sdk\platform-tools\adb -s "10.9.27.25:5555" shell getprop ro.build.version.sdk


Output of the NPM start output :

[Error] Error: Error while executing command 'D:\Android\tools\sdk\platform-tools\adb -s "10.9.27.25:5555" shell getprop ro.build.version.sdk': Command failed: D:\Android\tools\sdk\platform-tools\adb -s "10.9.27.25:5555" shell getprop ro.build.version.sdk

Closing comment (2019-06-13T12:47:45Z): Hi @banihasan . This issue is a duplicate of #1026 . I'd recommend you to downgrade platform-tools to version 28. To do that please do the following:

Open Android Studio
Click Configure
Choose SDK Manager
Open SDK Tools
Uncheck Android SDK Platform Tools and click Apply
Download Android SDK Platform Tools 28 using this link : https://dl.google.com/android/repository/platform-tools_r28.0.0-windows.zip
Unzip this folder into Android SDK Location folder that is indicated at SDK Manager

This issue will be resolved as soon as Google will release updated SDK with the fix.
Repository: microsoft/vscode-react-native

Issue #281: React Native does not show up in debug environments
Created: 2016-08-12T13:04:40Z
Actual Behavior

Open a react native project folder
Try to create a new debug environment
React Native does not show up in the list

Expected Behavior

There should be a React Native option

Software versions

React-Native VS Code extension version: 0.1.5
VSCode version: 1.4.0
OS platform and version: Windows 7 64bit
React Native version: 1.0.0

Duplicate issue #681: React Native Debugg configuration dissapears if using flow
Created: 2018-04-12T07:56:43Z
Actual Behavior

if flow-bin is added as a dependency, React Native debug config disappears. It doesn't matter if is installed, just by adding it on package.json (no even need to save)





Expected Behavior

Show debug config when using flow

Software versions

React-Native VS Code extension version: 0.6.6
VSCode version: 1.22.1
OS platform and version: MacOS 10.13.4
NodeJS version:
React Native version: 0.54.4

Closing comment (2018-04-16T08:03:23Z): @tafelito @BarlowTucker @Yousefjb thank you for your requests!
As for me, I didn't manage to reproduce the issue neither with flow-bin or react-redux and I don't think that having these plugins in package.json is the root cause of the issue.
It seems that the issue you've faced with is a duplicate of #281 and #661 . You can try the solutions listed there or follow it on the updates.
Repository: microsoft/vscode-react-native

Issue #625: Breakpoint set but not yet bound
Created: 2018-02-05T08:57:59Z
Actual Behavior

Breakpoint does not stop code execution

Expected Behavior

Breakpoint stops code execution


Latest version of everything.
"Breakpoint set but not yet bound" is displayed when hovering over the breakpoint.
Debugger is working just fine, when pressing the pause button the execution stops.
Console log shows that the code is running in the file where the breakpoint is set.

Workaround
Just remove any of your breakpoints and add it again - breakpoints become red and stop code execution

Duplicate issue #630: breakpoints set but not yet bound
Created: 2018-02-16T09:09:15Z
Actual Behavior

program doesn't stop at any breakpoints

Expected Behavior

program should stop at breakpoints

It used to work, now it doesn't work on any project now.
It does stop on debugger expression in code though.
Is something wrong with the extension, or is it a potential problem with sourcemaps? If so, if there any easy way to find out, or to solve it?
Software versions

React-Native VS Code extension version: 0.5.7
VSCode version: 1.20.1
OS platform and version: macOS
NodeJS version: according to console "Adapter node: v7.9.0 x64", but when run in shell it's 8.9.0
React Native version: 0.53.0

Outputs (Include if relevant)

Output of the Debug Console (View -> Toggle Debug Console):

OS: darwin x64
Adapter node: v7.9.0 x64
vscode-chrome-debug-core: 3.18.5
Starting debugger app worker.
Established a connection with the Proxy (Packager) to the React Native application
Debugger worker loaded runtime on port 9684
Module RCTImageLoader requires main queue setup since it overrides `init` but doesn't implement `requiresMainQueueSetup`. In a future release React Native will default to initializing all native modules on a background thread unless explicitly opted-out of.
RCTLog.js:48


Output of the React-Native output channel (View -> Toggle Output -> Select React-Native in ListBox):

PASTE OUTPUT HERE


Output of the Developer Tools console (Help -> Toggle Developer Tools -> Select Console tab):

PASTE OUTPUT HERE

Closing comment (2018-02-16T09:25:50Z): Hi @novellizator, thanks for reaching us and for filling the issue details. I'm closing this as duplicate of #625 , so please let's have a discussion in the one common issue.
Please let us know if you have any questions or see any other issues.
Repository: microsoft/vscode-react-native

Issue #918: [loc][Query][vscode_extensions ] Localizability of <Shake or press menu button>,” “<Dev Settings>” and “<Debug Server host & port for Device>”? 
Created: 2019-02-25T07:41:54Z
Hi,
please help localization team to answer question from translator.
In case translator is not sure about context/meaning/localizability of string we raise a question to Core team.
Please re-assign back to use in case you are not the right contact person or you can´t assign to a proper person.
Can you help please?
Thanks!
Source:
Device {0} supports only API Level {1}. \r\n Level {2} is needed to support port forwarding via adb reverse. \r\n For debugging to work you'll need  for the dev menu, \r\n go into  and configure <Debug Server host & port for Device> to be \r\n an IP address of your computer that the Device can reach. More info at: \r\n https://facebook.github.io/react-native/docs/debugging.html#debugging-react-native-apps
File Name:
Src\vscode-extensions\vscode-react-native.xlf
Resource ID:
0; "./src/extension/android/androidPlatform.DeviceSupportsOnlyAPILevel"
Query:
Would you please check the localizability of “,” “” and “<Debug Server host & port for Device>”? For now, I translated “” and “” because they seem to be Android UIs; however, I left “<Debug Server host & port for Device>” in English because it is marked in grey on the following live page: facebook/react-native#17644.

Duplicate issue #960: [loc][Query][vscode_extensions ] Localizability of 0; "./src/extension/android/androidPlatform.DeviceSupportsOnlyAPILevel" 
Created: 2019-03-28T13:47:00Z
Hi,
please help localization team to answer question from translator.
In case translator is not sure about context/meaning/localizability of string we raise a question to Core team.
Please re-assign back to use in case you are not the right contact person or you can´t assign to a proper person.
Can you help please?
Thanks!
Source:
Device {0} supports only API Level {1}. \r\n Level {2} is needed to support port forwarding via adb reverse. \r\n For debugging to work you'll need  for the dev menu, \r\n go into  and configure <Debug Server host & port for Device> to be \r\n an IP address of your computer that the Device can reach. More info at: \r\n https://facebook.github.io/react-native/docs/debugging.html#debugging-react-native-apps
File Name:
Src\vscode-extensions\vscode-cordova.xlf
Resource ID:
0; "./src/extension/android/androidPlatform.DeviceSupportsOnlyAPILevel"
Query:
<Debug Server host & port for Device> are segments in brackets localizable ?

Closing comment (2019-03-28T13:48:58Z): Hi @PDostalek . Your query is similar to #918
And also I see that .xlf file name is incorrect - it should be Src\vscode-extensions\vscode-react-native.xlf.
With respect to your query: this string is not localizable.
Repository: microsoft/vscode-react-native

Issue #273: Breakpoint getting hit in JS, but not being recognized in VS Code when using node 6.X
Created: 2016-07-29T18:56:35Z
Actual Behavior

Added a breakpoint to a function that handles user input
Adding the breakpoint would lock the device's UI, but doesn't "turn on" debugging

Expected Behavior

The debugging session to start up, stack traces, variables etc

So I have a simple trivial example, you would need to run npm install then start a debug run for iOS inside VS Code.
https://cl.ly/3C0V2Z2i200l/react-native-debugger-issues.zip
You should tap the view to see it say both "yo" then "hello". If you add a breakpoint at "hello" (line 11) and tap the view, the console will print "yo" but not "hello" - and VS Code will not start showing the trace etc
Software versions

React-Native VS Code extension version: 0.1.5
VSCode version: 1.3.1
OS platform and version:  OS X, 10.11.6
React Native version: 0.30

/cc @mennenia

Duplicate issue #297: Debugger doesn't work with Fat arrow function using ES2015+ class properties
Created: 2016-08-31T13:34:48Z
Actual Behavior

Set a breakpoint on an onPress handler function (handleOnPress1)
Set a breakpoint inside a fat arrow function using ES2015+ class properties (handleOnPress2)
Debug the code on iOS
It stops fine on the onPress handler function
It doesn't stops on the class property with arrow function to handle an onPress event
The application hangs

Expected Behavior

Stop in an arrow functions defined in a ES2015+ class properties

Software versions

React-Native VS Code extension version: 0.1.6
VSCode version: 1.4.0
OS platform and version: OSX 10.11.6
React Native version: 0.31.0

Sample code
import React, { Component } from 'react'
import { View, Text, TouchableOpacity, StyleSheet } from 'react-native'

export default class Sample extends Component {
  handleOnPress1() {
    console.log('stops here!!!')
  }

  handleOnPress2 = () => {
    console.log('doesn\'t stops here')
  }

  render() {
    return (
      <View style={styles.container}>
        <TouchableOpacity onPress={() => this.handleOnPress1()} style={styles.button}>
          <Text style={styles.text}>Press Me 1!</Text>
        </TouchableOpacity>
        <TouchableOpacity onPress={this.handleOnPress2} style={styles.button}>
          <Text style={styles.text}>Press Me 2!</Text>
        </TouchableOpacity>
      </View>
    )
  }
}

var styles = StyleSheet.create({
  container: {
    flex: 1,
    alignItems: 'center',
    justifyContent: 'center',
  },
  button: {
    padding: 30,
    margin: 10,
    backgroundColor: 'cyan',
    borderColor: 'blue',
    borderWidth: 1,
  },
  text: {
    color: 'black'
  },
})

Closing comment (2016-10-27T17:47:57Z): I think this is a dupe of #273, so I am closing this. @jpgarcia, please let me know if that is not the case and I will re-open.
Repository: microsoft/vscode-react-native

Issue #85: IntelliSense Doesn't Understand Flow Type Annotations in .js files
Created: 2016-02-26T19:31:42Z
Salsa intellisense doesn't correctly handle JSX type annotations.
'property declarations' can only be used in a .ts file.

Duplicate issue #136: 'property declarations' can only be used in a .ts file.
Created: 2016-03-11T02:57:26Z
Define arrow function inside class report error:
'property declarations' can only be used in a .ts file.
This file work well when I run in react native.

Closing comment (2016-03-11T03:45:38Z): This is related to #85. Unfortunately the intellisense / red-squigglies are only aware of standard javascript constructs, while react uses babel to support the newer es6 classes and other constructs.
Repository: microsoft/winget-pkgs

Issue #39190: [Package Request]: All KDE Packages - Nightly, Stable, Release
Created: 2021-12-29T02:27:07Z
This issue is to combine all the requests for KDE packages into a single place and reduce clutter
Nightly

 #38999
 #38997
 #38996
 #38995
 #38994
 #38990
 #38989
 #38988
 #38987
 #38986
 #38985
 #38984
 #38983
 #38982
 #38981
 #38979
 #38978
 #38974
 #38973
 #38972
 #38971
 #38970
 #38968
 #38966
 #38935
 #38934
 #38930
 #38929
 #38928
 #38927
 #38926
 #34832
 #34831
 #34830
 #33737
 #33736
 #33735
 #33730
 #33729
 #33727
 #33725
 #33721
 #33716
 #33715
 #33713
 #33712
 #33711
 #33710
 #33709
 #33706
 #33705
 #33704
 #39245
 #39241
 #39240
 #39243
 #39245
 #39247
 #39251
 #39252

Stable

 #38967
 #38933

Release

 #38993
 #38991
 #38980
 #38969
 #38936
 #38932
 #33726
 #33722
 #33719
 #39242

Duplicate issue #33726: [Package Request]: KDE.Filelight.Release
Created: 2021-11-03T13:29:33Z
Package Requested

 I would like someone else to build the manifest.
 I would like help so I can submit the manifest.
 I have performed a search and couldn't find this package.
 I have checked that the installer for this package is not a standalone or portable executable or a .zip file
 I think there is a new version available and I have provided the URL.

Please provide the following information
Publisher: KDE e.V.
Publisher Url: http://kde.org
Package Name: KDE.Filelight.Nightly
Description: http://apps.kde.org/filelight
Package Version: master-785
Installer URL: http://binary-factory.kde.org/view/Windows%2064-bit/job/Filelight_Release_win64/lastSuccessfulBuild/artifact/filelight-21.08.2-785-windows-msvc2019_64-cl-sideload.appx
Current Package Identifier (for new versions): master-785

Closing comment (2021-12-29T16:23:47Z): Duplicate of #39190
Please post your KDE requests here
Repository: microsoft/winget-pkgs

Issue #166969: [Update Request]: Update scrcpy package to the latest version
Created: 2024-08-09T06:29:04Z
What type of update are you requesting?
A new version of an existing package
Current Package Identifier
Genymobile.scrcpy
Package Version
2.7
Please describe the changes you would like to see
There's a newer version of scrcpy(2.7) available to download at releases

Duplicate issue #171430: [Update Request]: scrcpy
Created: 2024-09-03T14:47:52Z
What type of update are you requesting?
A new version of an existing package
Current Package Identifier
scrcpy
Package Version
2.6.1
Please describe the changes you would like to see
There is a new version available. Download releases: https://github.com/Genymobile/scrcpy/releases/

Closing comment (2024-09-03T15:57:37Z): Close with reason: Duplicate of #166969;
Repository: microsoft/winget-pkgs

Issue #246: Config files to support silent installation
Created: 2020-05-18T15:17:53Z
Some installers require a configuration file to specify parameters necessary for silent installation.
The manifest could be extended to support the data needed in a config file and could be created at install time on the local machine, or a file could be provided in addition to the manifest with some kind of pointer.
microsoft/winget-cli#158

Duplicate issue #112817: InstallShield silent install with response file
Created: 2023-07-22T09:38:28Z
Discussed in #112816

Originally posted by jeremytmsi July 22, 2023
Hello everyone,
I want to create a package in WinGet who uses InstallShield installer [#112792]. I created a response file who is needed for silent install but when I want to validate the manifest with Windows Sandbox, I get this error :

Can you help me ?
Thanks

Closing comment (2023-07-22T14:22:32Z): Currently additional files are not supported. This request is being tracked in

#246
Repository: microsoft/winget-pkgs

Issue #39190: [Package Request]: All KDE Packages - Nightly, Stable, Release
Created: 2021-12-29T02:27:07Z
This issue is to combine all the requests for KDE packages into a single place and reduce clutter
Nightly

 #38999
 #38997
 #38996
 #38995
 #38994
 #38990
 #38989
 #38988
 #38987
 #38986
 #38985
 #38984
 #38983
 #38982
 #38981
 #38979
 #38978
 #38974
 #38973
 #38972
 #38971
 #38970
 #38968
 #38966
 #38935
 #38934
 #38930
 #38929
 #38928
 #38927
 #38926
 #34832
 #34831
 #34830
 #33737
 #33736
 #33735
 #33730
 #33729
 #33727
 #33725
 #33721
 #33716
 #33715
 #33713
 #33712
 #33711
 #33710
 #33709
 #33706
 #33705
 #33704
 #39245
 #39241
 #39240
 #39243
 #39245
 #39247
 #39251
 #39252

Stable

 #38967
 #38933

Release

 #38993
 #38991
 #38980
 #38969
 #38936
 #38932
 #33726
 #33722
 #33719
 #39242

Duplicate issue #33725: [Package Request]: KDE.Filelight.Nightly
Created: 2021-11-03T13:29:31Z
Package Requested

 I would like someone else to build the manifest.
 I would like help so I can submit the manifest.
 I have performed a search and couldn't find this package.
 I have checked that the installer for this package is not a standalone or portable executable or a .zip file
 I think there is a new version available and I have provided the URL.

Please provide the following information
Publisher: KDE e.V.
Publisher Url: http://kde.org
Package Name: KDE.Filelight.Nightly
Description: http://apps.kde.org/filelight
Package Version: master-931
Installer URL: http://binary-factory.kde.org/view/Windows%2064-bit/job/Filelight_Nightly_win64/lastSuccessfulBuild/artifact/filelight-master-931-windows-msvc2019_64-cl.exe
Current Package Identifier (for new versions): master-931

Closing comment (2021-12-29T16:23:17Z): Duplicate of #39190
Please post your KDE requests here
Repository: microsoft/winget-pkgs

Issue #39190: [Package Request]: All KDE Packages - Nightly, Stable, Release
Created: 2021-12-29T02:27:07Z
This issue is to combine all the requests for KDE packages into a single place and reduce clutter
Nightly

 #38999
 #38997
 #38996
 #38995
 #38994
 #38990
 #38989
 #38988
 #38987
 #38986
 #38985
 #38984
 #38983
 #38982
 #38981
 #38979
 #38978
 #38974
 #38973
 #38972
 #38971
 #38970
 #38968
 #38966
 #38935
 #38934
 #38930
 #38929
 #38928
 #38927
 #38926
 #34832
 #34831
 #34830
 #33737
 #33736
 #33735
 #33730
 #33729
 #33727
 #33725
 #33721
 #33716
 #33715
 #33713
 #33712
 #33711
 #33710
 #33709
 #33706
 #33705
 #33704
 #39245
 #39241
 #39240
 #39243
 #39245
 #39247
 #39251
 #39252

Stable

 #38967
 #38933

Release

 #38993
 #38991
 #38980
 #38969
 #38936
 #38932
 #33726
 #33722
 #33719
 #39242

Duplicate issue #33737: [Package Request]: KDE.KAtomic.Nightly
Created: 2021-11-03T14:54:08Z
Package Requested

 I would like someone else to build the manifest.
 I would like help so I can submit the manifest.
 I have performed a search and couldn't find this package.
 I have checked that the installer for this package is not a standalone or portable executable or a .zip file
 I think there is a new version available and I have provided the URL.

Please provide the following information
Publisher: KDE e.V.
Publisher Url: http://kde.org
Package Name: KDE.Katomic.Nightly
Description: http://apps.kde.org/katomic
Package Version: master-744
Installer URL: http://binary-factory.kde.org/view/Windows%2064-bit/job/KAtomic_Nightly_win64/lastSuccessfulBuild/artifact/katomic-master-744-windows-msvc2019_64-cl.exe
Current Package Identifier (for new versions): master-744

Closing comment (2021-12-29T16:23:10Z): Duplicate of #39190
Please post your KDE requests here
Repository: microsoft/winget-pkgs

Issue #97773: [New Feature]: Offer a kind of batch mode for YamlCreate.ps1
Created: 2023-02-25T11:12:07Z
Description of the new feature/enhancement
Some software projects offer a large amount of different languages and installer types. I am thinking of Mozilla here especially.
When using YamlCreate.ps1 in Quick-Update-Mode to update a manifest it is quiet time consuming to manually copy and paste all new URLs for each single item. A kind of batch mode might be helpful.
Proposed technical implementation details (optional)
IMO a quick and easy solution:
Offer an option to either specify a text file containing all new URLs. Either simply the URLs as CSV as sorted in the manifest or a bit mor complex like the following:
`
x64 msi en-US https://download-installer.cdn.mozilla.net/pub/firefox/releases/102.8.0/Win64/en-US/Firefox%20Setup%20102.8.0.msi,
x86 msi en-US https://download-installer.cdn.mozilla.net/pub/firefox/releases/102.8.0/Win32/en-US/Firefox%20Setup%20102.8.0.msi
x64 exe en-US https://download-installer.cdn.mozilla.net/pub/firefox/releases/102.8.0/Win64/en-US/Firefox%20Setup%20102.8.0.exe
...
x64 msi de-DE https://download-installer.cdn.mozilla.net/pub/firefox/releases/102.8.0/Win64/de/Firefox%20Setup%20102.8.0.msi
...
`
More flexible but even complex:
Offer additional variables for such a text file. The following is just a rough thought which will not work for various reasons:
`
[Version]
102.8.0esr
[Languages]
en-US,en-GB,de-DE,ja-JP, ...
[Architectures]
x86,x64,arm64, ...
[InstallerTypes]
exe,msi, ...
[URL]
https://download-installer.cdn.mozilla.net/pub/firefox/releases/%Version%/%Architectures%/%Languages%/Firefox%20Setup%20%Version%.%InstallerTypes%
`

Duplicate issue #120074: [New Feature]: Yamlcreate - Pass urls as a parameter
Created: 2023-09-18T03:23:08Z
Description of the new feature/enhancement
It would be cool if we could just pass the urls as a parameter, maybe separated by a comma for multiple urls. This would help with some automation around pushing updated packages.
Proposed technical implementation details (optional)
For instance if you used option 2 and passed the urls, it would automatically cycle through them. I think you would need to apply them in the same order they are listed in the YAML.

Closing comment (2023-09-18T04:13:23Z): Looks to be duplicate of

#97773
Repository: microsoft/winget-pkgs

Issue #80572: [New Feature]: Manifest-Version-Error Label
Created: 2022-09-23T13:11:06Z
Description of the new feature/enhancement
Pipelines tell us when a manifest version is not supported.
https://dev.azure.com/ms/winget-pkgs/_build/results?buildId=374829&view=logs&j=1c216ba8-f9ef-5707-496b-69e30b6cb45a&t=d5938111-0e28-5713-0070-4b1bb7df6b82&l=33
It would be a cleaner experience for contributors if a dedicated label and MSFTbot message were applied for this error.
Proposed technical implementation details (optional)

 Add a Manifest-Version-Error Label
 Configure a msftbot message when the label is added
 Configure wingetbot to add the label
 Integrate and test


Proposed Message
Hello @${issueAuthor},\n\nThe package manager bot determined that the ManifestVersion key does not match any version  currently approved for release.Please verify the manifest file is compliant with the package manager [1.0 manifest specification](https://github.com/microsoft/winget-pkgs/tree/master/doc/manifest/schema/1.0.0), [1.1 manifest specification](https://github.com/microsoft/winget-pkgs/tree/master/doc/manifest/schema/1.1.0), or [1.2 manifest specification](https://github.com/microsoft/winget-pkgs/tree/master/doc/manifest/schema/1.2.0).\n\nFor details on the specific error, see the details link below in the build pipeline.\n\nTemplate: msftbot/validationError/manifest/version


Hello @${issueAuthor},
The package manager bot determined that the ManifestVersion key does not match any version  currently approved for release. Please verify the manifest file is compliant with the package manager 1.0 manifest specification, 1.1 manifest specification, or 1.2 manifest specification.
For details on the specific error, see the details link below in the build pipeline.
Template: msftbot/validationError/manifest/version

Duplicate issue #124471: [New Feature]: Inform PR authors when they are using an invalid schema
Created: 2023-11-01T16:44:01Z
Description of the new feature/enhancement
When a PR is made for a package, the schema version should be a valid version.
A label "Manifest-Version-Error" should be added to the PR informing authors when they are using an invalid version.
PR authors should be informed which version of the schema is the latest supported by validation, and when a PR is created with an invalid version, a label should be added to inform them.
Proposed technical implementation details (optional)
No response

Closing comment (2023-11-01T18:57:33Z): Related to #80572
Related to #83014
Repository: microsoft/winget-pkgs

Issue #39190: [Package Request]: All KDE Packages - Nightly, Stable, Release
Created: 2021-12-29T02:27:07Z
This issue is to combine all the requests for KDE packages into a single place and reduce clutter
Nightly

 #38999
 #38997
 #38996
 #38995
 #38994
 #38990
 #38989
 #38988
 #38987
 #38986
 #38985
 #38984
 #38983
 #38982
 #38981
 #38979
 #38978
 #38974
 #38973
 #38972
 #38971
 #38970
 #38968
 #38966
 #38935
 #38934
 #38930
 #38929
 #38928
 #38927
 #38926
 #34832
 #34831
 #34830
 #33737
 #33736
 #33735
 #33730
 #33729
 #33727
 #33725
 #33721
 #33716
 #33715
 #33713
 #33712
 #33711
 #33710
 #33709
 #33706
 #33705
 #33704
 #39245
 #39241
 #39240
 #39243
 #39245
 #39247
 #39251
 #39252

Stable

 #38967
 #38933

Release

 #38993
 #38991
 #38980
 #38969
 #38936
 #38932
 #33726
 #33722
 #33719
 #39242

Duplicate issue #38974: [Package Request]: KDE.Kig.Nightly
Created: 2021-12-26T22:14:04Z
Package Requested

 I would like someone else to build the manifest.
 I would like help so I can submit the manifest.
 I have performed a search and couldn't find this package.
 I have checked that the installer for this package is not a standalone or portable executable or a .zip file
 I think there is a new version available and I have provided the URL.

Please provide the following information
Publisher: KDE e.V.
Publisher Url: http://kde.org
Package Name: KDE.Kig.Nightly
Description: http://apps.kde.org/kig
Package Version: master-970
Installer URL: http://binary-factory.kde.org/view/Windows%2064-bit/job/Kig_Nightly_win64/lastSuccessfulBuild/artifact/kig-21.12.0-970-windows-msvc2019_64-cl.exe
Current Package Identifier (for new versions): master-970

Closing comment (2021-12-29T16:22:52Z): Duplicate of #39190
Please post your KDE requests here
Repository: microsoft/winget-pkgs

Issue #39190: [Package Request]: All KDE Packages - Nightly, Stable, Release
Created: 2021-12-29T02:27:07Z
This issue is to combine all the requests for KDE packages into a single place and reduce clutter
Nightly

 #38999
 #38997
 #38996
 #38995
 #38994
 #38990
 #38989
 #38988
 #38987
 #38986
 #38985
 #38984
 #38983
 #38982
 #38981
 #38979
 #38978
 #38974
 #38973
 #38972
 #38971
 #38970
 #38968
 #38966
 #38935
 #38934
 #38930
 #38929
 #38928
 #38927
 #38926
 #34832
 #34831
 #34830
 #33737
 #33736
 #33735
 #33730
 #33729
 #33727
 #33725
 #33721
 #33716
 #33715
 #33713
 #33712
 #33711
 #33710
 #33709
 #33706
 #33705
 #33704
 #39245
 #39241
 #39240
 #39243
 #39245
 #39247
 #39251
 #39252

Stable

 #38967
 #38933

Release

 #38993
 #38991
 #38980
 #38969
 #38936
 #38932
 #33726
 #33722
 #33719
 #39242

Duplicate issue #38994: [Package Request]: KDE.KNetwalk.Nightly
Created: 2021-12-26T22:58:35Z
Package Requested

 I would like someone else to build the manifest.
 I would like help so I can submit the manifest.
 I have performed a search and couldn't find this package.
 I have checked that the installer for this package is not a standalone or portable executable or a .zip file
 I think there is a new version available and I have provided the URL.

Please provide the following information
Publisher: KDE e.V.
Publisher Url: http://kde.org
Package Name: KDE.KNetwalk.Nightly
Description: http://apps.kde.org/knetwalk
Package Version: master-782
Installer URL: http://binary-factory.kde.org/view/Windows%2064-bit/job/KNetwalk_Nightly_win64/lastSuccessfulBuild/artifact/knetwalk-master-782-windows-msvc2019_64-cl.exe
Current Package Identifier (for new versions): master-782

Closing comment (2021-12-29T16:22:39Z): Duplicate of #39190
Please post your KDE requests here
Repository: mileszs/wicked_pdf

Issue #794: PDF rendering fails on Heroku 16 Stack
Created: 2019-02-01T18:00:34Z
Heroku released an update to its Heroku 16 stack on December 18. Since that update to our Heroku instances, pdf rendering will only temporarily work on a new branch deploy. After ~5 mins pdf rendering silently fails (ie. no information presented in log file).
Final log entry is:
2019-02-01T17:37:56.044912+00:00 app[web.1]: WICKED
That is followed by a series of rack-timeout notifications until we reach the Heroku limit and the call fails.
2019-02-01T17:37:58.588912+00:00 app[web.1]: source=rack-timeout id=511db688-876f-4b5d-bb58-2a52f749509f wait=3ms timeout=28000ms service=3000ms state=active
2019-02-01T17:37:59.588844+00:00 app[web.1]: source=rack-timeout id=511db688-876f-4b5d-bb58-2a52f749509f wait=3ms timeout=28000ms service=4000ms state=active
...
rails 4.2.11
ruby 2.2.7
wicked_pdf 1.1.0
wkhtmltopdf-heroku 2.12.2.4
(we have also tried using dscout/wkhtmltopdf-buildpack but have the same result)

Duplicate issue #793: Stylesheets and images fail to render on Ubuntu 18.04
Created: 2019-01-25T22:24:01Z
We use the Rails assets pipeline for stylesheets and images, along with a CDN configured as an asset_host.
We upgraded from Ubuntu 14.04 (Trusty Tahr) to Ubuntu 18.04 LTS.
After the upgrade, we noticed that our PDFs generated with wicked_pdf gem were missing their styling and the logo png.
We reverted to Ubuntu 14.04 (Trusty Tahr), and it worked again.
We are running these on cloud foundry buildpack stacks (cflinuxfs3 which is built off of Ubuntu 18.04, cflinuxfs2 is built off of Ubuntu 14.04).
Versions:
wkhtmltopdf-binary (0.12.4)
wicked_pdf (1.1.0)
Rails 4.2.11

Closing comment (2019-02-01T22:47:54Z): Possibly related to #794 (since Heroku 16 is based on Ubuntu 16)
Repository: mileszs/wicked_pdf

Issue #344: Issues rending images from HTTPS
Created: 2014-10-16T21:38:09Z
Hi All,
A couple days ago I realized that images were missing from the PDF's I'm generating ... it wasn't an issue prior to that and I'm still trying to track down what "changed" (no code changes on my end). Anyways ... I noticed that images sourced from HTTPS are not rendering in the generated PDF's but they do render when show_as_html is enabled.
Anybody have any insight into this issue?
I've setup a working example of the issue @ http://dev.e-snapapps.com/welcome/test.pdf (for show_as_html use http://dev.e-snapapps.com/welcome/test.pdf?debug=true).
Thanks =~ J

Duplicate issue #741: PDF rendering fails on Heroku 18 Stack
Created: 2018-05-28T16:19:33Z
I have one problem PDF rendering works in development but not in production environment. The following error gets logged in "log/production.log"
I worked with heroku
2018-05-28T16:12:04.127157+00:00 app[web.1]: RuntimeError (Failed to execute:
2018-05-28T16:12:04.127159+00:00 app[web.1]: ["/app/vendor/bundle/ruby/2.4.0/bin/wkhtmltopdf", "-q", "file:////tmp/wicked_pdf20180528-4-1n6idpw.html", "/tmp/wicked_pdf_generated_file20180528-4-e58bir.pdf"]
2018-05-28T16:12:04.127161+00:00 app[web.1]: Error: PDF could not be generated!
2018-05-28T16:12:04.127163+00:00 app[web.1]: Command Error: ):
2018-05-28T16:12:04.127165+00:00 app[web.1]: app/controllers/facturas_controller.rb:25:in `reportes'
2018-05-28T16:12:04.127167+00:00 app[web.1]:
2018-05-28T16:12:04.127168+00:00 app[web.1]:
2018-05-28T16:12:04.284318+00:00 heroku[router]: at=info method=GET path="/favicon.ico" host=appvaluemi.herokuapp.com request_id=76e488db-f65e-46a0-ba95-02173902be1c fwd="" dyno=web.1 connect=0ms service=3ms status=304 bytes=62 protocol=http
in heroku i worked with
Rails 4.2.8
ruby 2.4.4p296 (2018-03-28 revision 63013) [x86_64-linux]
This problem started with change ruby 2.3 to ruby 2.4.4 in heroku
Please anyone help me
Thanks in advance.
Percy

Closing comment (2018-11-13T16:41:24Z): @unixmonkey the stack we use is the following one:
• Ruby 2.5.1
• Rails 5.2.0
• WickedPDF 1.1.0
• wkhtmltopdf 0.12.3 (through dscout/wkhtmltopdf-buildpack)
You're right though, it only concerns HTTPS pics so I guess my issue is more related to #344 even though the behavior changes between heroku-16 and heroku-18.
Repository: mileszs/wicked_pdf

Issue #810: Problem upgrading to 1.2.0
Created: 2019-03-18T08:29:16Z
After upgrading from 1.1.0 to 1.2.0 all requests to the rails app fail. The system seems to go into an infinite loop when trying to render the page. The log shows
FATAL Rails :
SystemStackError (stack level too deep):
wicked_pdf (1.2.0) lib/wicked_pdf/pdf_helper.rb:30:in render' wicked_pdf (1.2.0) lib/wicked_pdf/pdf_helper.rb:43:in render_with_wicked_pdf'
... (this goes on and on)...
wicked_pdf (1.2.0) lib/wicked_pdf/pdf_helper.rb:30:in render' wicked_pdf (1.2.0) lib/wicked_pdf/pdf_helper.rb:43:in render_with_wicked_pdf'
wicked_pdf (1.2.0) lib/wicked_pdf/pdf_helper.rb:30:in render' wicked_pdf (1.2.0) lib/wicked_pdf/pdf_helper.rb:43:in render_with_wicked_pdf'
wicked_pdf (1.2.0) lib/wicked_pdf/pdf_helper.rb:30:in render' wicked_pdf (1.2.0) lib/wicked_pdf/pdf_helper.rb:43:in render_with_wicked_pdf'
actionpack (4.2.11.1) lib/action_controller/metal/implicit_render.rb:10:in default_render' actionpack (4.2.11.1) lib/action_controller/metal/implicit_render.rb:5:in send_action'
System configuration:
Ubuntu 18.04
Rails 4.2.11.1
Ruby 2.4.5

Duplicate issue #650: SystemStackError issue with Rails 5.1 and Ruby 2.4.1
Created: 2017-05-02T01:31:14Z
system stack too deep when rendering any default html action.

Closing comment (2019-03-26T21:46:53Z): @mattnwa You are probably experiencing a similar error with the newly released version which is currently being tracked in #810. I'm actively working on a fix, but it's not really an issue with this gem, but it's interaction with other gems that mess with render in a similar way. If you are on the current version and have new information, please add it to that issue.
Repository: mileszs/wicked_pdf

Issue #1117: v2.8.0 causing ActionView::Template::Error: no implicit conversion of nil into String for first time in years
Created: 2024-05-13T14:52:32Z
Method generate_report_pdf is causing ActionView::Template::Error: no implicit conversion of nil into String error in wicked_pdf find_asset method in Staging & Production environments on Heroku only
Expect no error in asset retrieval
System specifications
wicked_pdf (2.8.0)
wkhtmltopdf 0.12.6 (with patched qt)
wkhtmltopdf-binary (0.12.6.6) used in test / development only
Heroku-22 Stack with heroku/nodejs & heroku/ruby buildpacks
Line 6 (in bold - stylesheet_link_tag) is causing the issue
<html>
  <head>
    <meta charset='utf-8' />
    <meta name="viewport" content="width=device-width, initial-scale=1">
    **<%= stylesheet_link_tag wicked_pdf_asset_base64("pdf") -%>**
  </head>
  <body>
    <%= render partial: "report/sections/cover", locals: { values: values, branding: branding, company: company, logo_url: logo_url } %>
  </body>
</html>

We recently updated our gemfile, including incrementing Rails 7.0.8 > 7.0.8.1 and wicked_pdf 2.7.0 > 2.8.0 which introduced the issue. PDF report generation failing as a result.
Everything works as expected if we revert to wicked_pdf (2.7.0)
Happy to supply as much more information as needed to identify the cause!

Duplicate issue #1102: ActionView::Template::Error uninitialized constant WickedPdf::WickedPdfHelper::Assets::SprocketsEnvironment::Sprockets
Created: 2024-02-06T14:16:51Z
The v2.7.0 of wicked_pdf seems not to be fully incompatible with Rails 7.
Rails 7.0 makes Sprockets an optional dependency. We don't use Sprockets in our Rails 7.1 app and updating wicked_pdf to v2.7.0 make us a bit of trouble.
There is a addition to WickedPdf::WickedPdfHelper::Assets#read_asset that makes the difference:
asset = find_asset(source)
Downgrading wicked_pdf back to v2.6.3 restored the functionality.

Closing comment (2024-08-06T12:16:21Z): Same error in one of our projects while upgrading to the version 2.8.0
Perhaps it could be related to: #1117
Repository: mileszs/wicked_pdf

Issue #482: Need to embed audio file in pdf
Created: 2016-01-13T08:32:33Z
I want to embed audio file into pdf but audio_tag is not working in pdf. How I can embed audio to pdf file?

Duplicate issue #484: Embed audio into pdf
Created: 2016-01-19T09:15:15Z
I need to play audio inside generated pdf file. audio tag does not working for it. Is there any way I can embed directly audio not link to audio file.

Closing comment (2016-01-19T14:57:36Z): Duplicate of #482.
WickedPDF is a wrapper around wkhtmltopdf, which essentially loads a website up in a headless web browser, and does a print-to-pdf.
Although it is possible to embed audio in a PDF with some of the Acrobat tools, it is not possible with wkhtmltopdf or WickedPDF. Sorry.