primordic/IssueDupesLite huggingface dataset:
Repository: ScoopInstaller/Main

Issue #4786: 7zip@22.01: decompress error
Created: 2023-05-10T06:07:13Z
Failed to extract files from C:\Scoop\apps\7zip\22.01\7z2201-x64.msi.
Log file:
C:\Scoop\apps\7zip\22.01\msi.log
Please try again or create a new issue by using the following link and paste your console output:
https://github.com/ScoopInstaller/Main/issues/new?title=7zip%4022.01%3a+decompress+error
The contents of the msi.log file are nill

Duplicate issue #4785: 7zip@22.01: decompress error
Created: 2023-05-09T23:06:27Z

Closing comment (2023-05-10T10:23:35Z): Duplicate of #4786
Repository: Semantic-Org/Semantic-UI

Issue #6123: [Dropdown] Selected multiple options are hidden (2.2.14)
Created: 2018-01-29T14:55:44Z
I've used to generate dropdowns from HTML in my forms, but Semantic 2.2.14 has a critical bug: selected options are hidden (but they are still considered as selected if you submit a form):
https://jsfiddle.net/3LaahL7e/1/

Duplicate issue #6145: [Dropdown] [v2.2.14] Multiple Dropdown pre-"selected" Options not visible
Created: 2018-02-07T17:10:40Z
When displaying a <selection multiple> with pre-selected Options, these options will not be displayed to the HTML.
This bug is existing after upgrading to 2.2.14
Example - before JS initialized (T1 will not be shown)
<select multiple class="ui dropdown">
  <option selected>T1</option>
  <option>T2</option>
  <option>T3</option>
</select>
3/3 options selected
No Option gets displayed (selection active)


2/3 Options selected
Only the not-selected Option gets displayed and is selectable (selection active)


When selecting T2, the expected behavior is shown until page refresh

Closing comment (2018-03-12T13:37:28Z): Duplicate #6123, @hammy2899 can you close this ?
Repository: Semantic-Org/Semantic-UI

Issue #6123: [Dropdown] Selected multiple options are hidden (2.2.14)
Created: 2018-01-29T14:55:44Z
I've used to generate dropdowns from HTML in my forms, but Semantic 2.2.14 has a critical bug: selected options are hidden (but they are still considered as selected if you submit a form):
https://jsfiddle.net/3LaahL7e/1/

Duplicate issue #6254: FORM SELECT "multiple" broken after 2.2.13 
Created: 2018-03-07T22:55:39Z
✖ USAGE QUESTIONS → Use these dedicated resources:
Docs - http://www.semantic-ui.com
Chat - https://gitter.im/Semantic-Org/Semantic-UI
SO - https://stackoverflow.com/questions/tagged/semantic-ui?sort=votes
✔ Enhancements → Be specific. Assume backwards compatibility is a necessity. Suggest implementation when possible.
✔ BUGS → ❤❤❤. Keep in mind some bugs may not be immediately fixable due to backwards compatibility or CSS limitations.
Title (Put in field above)
 existing values not longer selected by default.
Steps

	
		
			CoachClub=ListFind(ClubLocationList, Club_Number, ",");
		
		selected>#Location#
	

### Expected Result
Existing values to be "selected".
### Actual Result
Nothing at all is selected.
### Version
2.2.14 and later.
Testcase

Closing comment (2018-03-08T07:07:15Z): Duplicate #6123
Repository: Semantic-Org/Semantic-UI

Issue #614: Modal: Bad position on second show
Created: 2014-02-10T21:10:19Z
When modal showed for second time it "falls" half bellow screen.
var self = $('.ui.modal');
self.modal({
  onShow: function () {
    self.modal('refresh'); // does NOT help
    setTimeout(function () {
      self.modal('refresh');
    }, 1000); // does help 1s is probably overkill
  }
});
My uneducated guess is position is computed and set only first time when modal is shown and second time default CSS makes it fall.
Modal includes some generated items by KnockoutJS but items are not added between shows.

Duplicate issue #776: Modal: Bad position on second show #2
Created: 2014-04-11T08:08:25Z
Bug #614 is still reproduced.
Windows 8
FF 28.0
jQuery 2.0.2
demo: https://docs.google.com/file/d/0B19STWBC891DWEJXd2ZWeGxFY0E
but when the document or window size is changed, margin of the modal is fixed

Closing comment (2014-04-11T14:21:22Z): Duplicate #614
Repository: Semantic-Org/Semantic-UI

Issue #6123: [Dropdown] Selected multiple options are hidden (2.2.14)
Created: 2018-01-29T14:55:44Z
I've used to generate dropdowns from HTML in my forms, but Semantic 2.2.14 has a critical bug: selected options are hidden (but they are still considered as selected if you submit a form):
https://jsfiddle.net/3LaahL7e/1/

Duplicate issue #6213: BUG: Values not being pre-selected in multi selection downdown
Created: 2018-02-24T05:38:13Z
Values in hidden field not be pre-selected. However, they are disappeared from the dropdown menu. See fiddle: https://jsfiddle.net/vgbLs8nb/5/

Closing comment (2018-02-24T16:14:26Z): Duplicate #6123
Repository: Semantic-Org/Semantic-UI

Issue #6449: [Modal] Scrolling broken for mobile devices from recent 2.3.2 changes
Created: 2018-06-22T13:30:02Z
Steps
This can easily be replicated pressing "Run Code" in the "Scrolling Modal" example on a mobile device (Chrome or Android) or even in a device simulator on Chrome Desktop.
Expected Result
It should be able to scroll.
Actual Result
It cannot scroll.
Version
2.3.2
Testcase
https://semantic-ui.com/modules/modal.html#scrolling-modal
This is the culprit: 75dcaa2

Duplicate issue #6477: [Modal] Scrolling should work after showing modals
Created: 2018-07-12T00:19:00Z
Steps
The following html does nothing but shows a modal. However, after that, scrolling doesn't work on mobile devices(although it works on desktop browsers).
Note that scrolling works on mobile devices after the following line is removed.
  $("#test-modal").modal("show");
So I think maybe modal did something that prevented scrolling on mobile devices.
<html>
<head>
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <link rel="stylesheet" type="text/css"
        href="https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.3.2/semantic.min.css">
  <script
      src="https://code.jquery.com/jquery-3.1.1.min.js"
      integrity="sha256-hVVnYaiADRTO2PzUGmuLJr8BLUSjGIZsDYGmIJLv2b8="
      crossorigin="anonymous"></script>
  <script src="https://cdnjs.cloudflare.com/ajax/libs/semantic-ui/2.3.2/semantic.min.js"></script>
</head>
<body>
<pre>
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
    contents
</pre>
<div class="ui basic modal" id="test-modal">
  <div class="ui header">
    header
  </div>
  <div class="content">
    <p>content</p>
  </div>
  <div class="actions">
    <div class="ui green ok inverted button">
      <i class="checkmark icon"></i>
      OK
    </div>
  </div>
</div>
<script>
  $("#test-modal").modal("show");
</script>
</body>
</html>
Expected Result
Scrolling on mobile devices should work after showing the modal.
Actual Result
Scrolling doesn't work on mobile devices after showing the modal.
Version
2.3.2
Testcase
https://jsfiddle.net/t30wbo6n/1/

Closing comment (2018-07-12T05:08:08Z): Duplicate of #6449
Repository: Semantic-Org/Semantic-UI

Issue #2355: [Menu] Support inverted colored pointing menu
Created: 2015-06-03T09:43:51Z
As you can see:

It must be:

Duplicate issue #4846: [Menu] Colored variations of “.inverted.pointing.menu” should all have a colored pointer
Created: 2016-12-22T08:53:06Z
Pointing indicator color in inverted colored pointing menu is wrong.
See on JSFiddle.

Closing comment (2017-05-23T00:40:19Z): It’s in the process of being fixed, somebody already opened a PR the other day. Closing the issue as a duplicate of #2355.
Repository: Semantic-Org/Semantic-UI

Issue #6439: [Label] Basic label has same colored background since 2.3.2
Created: 2018-06-18T10:28:30Z
Steps
https://semantic-ui.com/elements/label.html -> Basic
Expected Result
up to version 2.3.1
Actual Result
colored background, if color was defined
Version
2.3.2
Testcase
https://semantic-ui.com/elements/label.html -> Basic

Duplicate issue #6496: Label - Basic Labels not styled properly
Created: 2018-07-23T19:58:40Z
Steps
If you set a label as basic it is not using the inverted (white) background.  It is using the label color.
You can see this on the label's documentation page at:
https://semantic-ui.com/elements/label.html
Check out the red pointing form label that says "Please enter a value" it just appears as solid red.

Closing comment (2018-07-23T21:49:43Z): Duplicate of #6439
Repository: Semantic-Org/Semantic-UI

Issue #5012: [Website] Scrolling the theming example causes the page to stutter across multiple devices and browsers
Created: 2017-02-12T12:30:34Z
It is almost impossible to scroll at this page on ipad and the latest ios:
http://semantic-ui.com/examples/theming.html
It is shaking as hell while scrolling...

Duplicate issue #5195: [Website] Scroll doesn't work properly on Google Chrome mobile
Created: 2017-03-24T07:48:58Z
There is some scroll hell on theming page.
Browser: Google Chrome 56.0.2924.87
OS: Android 5.1 / Flyme
Video

Closing comment (2017-03-24T08:51:00Z): Hi @radiocity and thanks, closing as a duplicate of #5012. I reposted your data there.
Repository: Semantic-Org/Semantic-UI

Issue #1330: [Progress] Indicating Progress Label Doesnt Adjust Immediately on Chrome
Created: 2014-11-30T00:09:52Z
On this page:
http://semantic-ui.com/modules/progress.html
Play around with the Indicating Types for a little while using Chrome version 39. (The second bar at the top of the page.) You'll notice that the color of the label isn't entirely predictable. Sometimes the label tracks with the color of the bar and sometimes it doesn't.
If you don't see the strangeness happen, try it after refreshing the page.

Duplicate issue #1483: Evenly Divided Button Rollover Display Bug
Created: 2014-12-19T16:04:22Z
I'm using latest stable released Chrome. When I roll over the Evenly Divided Buttons on this page: http://semantic-ui.com/elements/button.html from left to right, the background color doesn't properly reset until moving the cursor completely off the button group.
Looks like removing the position: relative from this style would fix the issue:
.ui.buttons>.button.active, .ui.buttons>.button:hover {
    position: relative;
}

Closing comment (2014-12-19T21:49:05Z): This is similar to #1330
Chrome sometimes is a bit miserly with its repaints.
Quickest fix is creating a new layer with transform or will-change but this might cause other issues.
Can confirm this fixes issues:
.ui.button {
  will-change: transform;
}
Will investigate if this is the best approach
Repository: Serene-Arc/bulk-downloader-for-reddit

Issue #844: Completions command in README is incorrect
Created: 2023-04-26T19:59:27Z
Description
The completions command in the main README is either incorrect or has a typo.
Command
bdfr completions

Environment (please complete the following information)

OS: All
Python version: 3.9.x

Logs
$ bdfr completions
Usage: bdfr [OPTIONS] COMMAND [ARGS]...

Error: No such command 'completions'.

Easy fix: either change the command name or readme snippet

Duplicate issue #893: Documentation Correction for bdfr completion Command
Created: 2023-06-19T09:15:02Z
bdfr v2.6.2
The docs show to use bdfr completions to install shell completion, but the correct command seems to be bdfr completion.

bdfr -h
Usage: bdfr [OPTIONS] COMMAND [ARGS]...

  BDFR is used to download and archive content
  from Reddit.

Options:
  -h, --help  Show this message and exit.
  --version   Check version and exit.

Commands:
  archive     Used to archive post data from...
  clone       Combines archive and download...
  completion  Installs shell completions for...
  download    Used to download content posted...

Closing comment (2023-06-21T03:03:43Z): Duplicate of #844
Repository: Serene-Arc/bulk-downloader-for-reddit

Issue #115: Issues with Redgifs and Gfycat
Created: 2020-06-03T11:21:17Z
i used python script /1.7.0 then 1.8.0 on windows
faceofpain subreddit when I download top >all time
even first post is not getting downloaded tried everything
even when I try hot>only few posts are downloading others giving error
[WinError 10054] An existing connection was forcibly closed by the remote host
Trying again

Duplicate issue #117: [WinError 10054] An existing connection was forcibly closed by the remote host
Created: 2020-06-04T14:50:04Z
Hi.
When the script tries to download large files (>35 Mb, I think)  from gfycat or redgifs, I get this error message and after three failed attempts, the file is skipped. Do you have an idea, how I can adress this error?
Thanks a lot =)

Closing comment (2020-06-04T15:32:55Z): Duplicate of #115
Repository: Serene-Arc/bulk-downloader-for-reddit

Issue #770: [IMPROVEMENT] Option 'search-existing' scans too many files
Created: 2023-02-05T14:19:11Z
I am requesting an improvement.
 I am running the latest version of BDfR
 I have read the Opening an issue

Description
It's unnecessary to scan the meta files (json/xml/yaml) and compute their hashes as these hashes aren't used anyway.
Skipping these file types by default would save some resources while scanning the files.
Not sure, if it should be labeled bug (or feature), at least an improvement of something that's already there.

Duplicate issue #801: [FEATURE] Cache hashes
Created: 2023-02-27T19:54:35Z
I am requesting a feature.
 I am running the latest version of BDfR
 I have read the Opening an issue

Description
After downloading a subreddit I downloaded another and it started calculating hashes, it took it quite a while, and after it finished I downloaded another subreddit and it started recalculating the hashes again and it took even longer. Saving the hashes for the files would save a lot of processing time. They could be saved in the configuration folder or in the submission files themselves.

Closing comment (2023-02-28T00:34:55Z): The use of hashes to determine existing files is highly discouraged. This feature is the same as #770 and #772 and won't be implemented
Repository: Serene-Arc/bulk-downloader-for-reddit

Issue #295: [BUG] File Scheme {DATE} returns a UNIX Timestamp instead of formatted date
Created: 2021-04-21T01:08:37Z
I am reporting a bug.
 I am running the latest version of BDfR
 I have read the Opening an issue

Description
Using the command below, the {DATE} parameter returns a different format than the previous version.
Actual example: 1618940992.0 in the file name instead of 2021-04-20_17-49
Command
python3 -m bdfr download '~\bdfr\redditor' --user USERNAME --submitted --sort new --no-dupes --folder-scheme '{REDDITOR}' --file-scheme '{DATE}_{REDDITOR}_{TITLE}_{POSTID}'

Environment (please complete the following information):

OS: Windows 10 20H2
Python version: 3.9.4

Logs
I, weirdly, don't have a bdfr folder appearing in my %AppData% directory as stated in the readme. Can't find it anywhere either. But it might not be needed for this specific issue?

Duplicate issue #359: [BUG] {DATE} Issue
Created: 2021-05-10T21:05:43Z
I am reporting a bug.
 I am running the latest version of BDfR
 I have read the Opening an issue

Description
When inputting file scheme, {DATE} produces something other than the date.
Command
python3 -m bdfr download sites --subreddit clashofclans --file-scheme {DATE}_{TITLE}_{POSTID} -L 2 -S new

Environment (please complete the following information):

OS: [MacOS 11.2.3]
Python version: [3.9.5]

Logs
MBP bulk-downloader-for-reddit-2.0.0 % python3 -m bdfr download sites --subreddit clashofclans --no-dupes --file-scheme {DATE}_{TITLE}_{POSTID} -L 2 -S new

[2021-05-10 14:03:07,997 - bdfr.downloader - INFO] - Downloaded submission n9fynh from ClashOfClans
[2021-05-10 14:03:08,154 - bdfr.downloader - INFO] - Downloaded submission n9fvzw from ClashOfClans
[2021-05-10 14:03:08,154 - root - INFO] - Program complete

//

FIle name output
1620680256.0_How do i rush my builderbase as quick as possible so i can get a 6th builder?_n9fvzw.txt

1620680433.0_Anyone please help why my x-bows are not attacking on anyone who is attacking on my base. I am a active user login in 2 or 3 days please help_n9fynh.txt

Closing comment (2021-05-10T23:23:28Z): Duplicate of #295
Repository: SharePoint/sp-dev-docs

Issue #642: Using UI Fabric Icons for ListView Commands
Created: 2017-06-13T13:49:25Z
Category

 Question
 Typo
 Bug
 Additional article idea

In addition to the iconImageUrl property for commands, an implementation of the officeFabricIconFontName property that would match the functionality of the same property for client-side web parts and allow the specification of a UI Fabric icon class name.
Currently, the iconImageUrl property generates this markup when located in the Toolbar:
<span class="CommandBarItem-icon">
  <i class="ms-Icon ms-Icon--custom" data-bind="style: { backgroundImage: 'url(\'' + $parent.iconUrl() + '\')' }" style="background-image: url(&quot;icons/request.png&quot;);"></i>
</span>

The proposed officeFabricIconFontName property with a value of "Emoji2" could generate something similar to this:
<span class="CommandBarItem-icon ms-Icon ms-Icon--Emoji2"></span>

Here's how that might look (I've replaced the generated markup with the proposed markup on the page directly):

For reference, here is the definition of the officeFabricIconFontName property from the client-side-web-part manifest.schema.json:
"officeFabricIconFontName": {
  "title": "Office Fabric Icon Name",
  "description": " The icon for the Web Part, to be displayed in the toolbox, represented as a character name in the Office 365 icon font file. The icon font is specified here: http://o365icons.cloudapp.net/. If this field has a value, the 'iconImageUrl' field will be ignored.",
  "type": "string",
  "minLength": 1
},

Duplicate issue #7565: Using Fluent UI icons in Command Set
Created: 2021-12-07T10:44:57Z
Is there any chance, that ListView Command Set will support official Fluent UI Icons, through CSS classes, like mentioned here (from 2017) #642
It was one of the most up-voted problems on SharePoint Online User Voice (that has been shut down...)
Thanks on any comment

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

ID: 38ba7b1f-b77a-0076-ed6c-dd84bbc104ea
Version Independent ID: d7cc472b-1c5b-fd7b-f7dc-6add54dd0886
Content: Configure extension icon in SharePoint Framework (SPFx) Extensions
Content Source: docs/spfx/extensions/basics/configure-extension-icon.md
Product: sharepoint
Technology: sharepoint-framework
GitHub Login: @VesaJuvonen
Microsoft Alias: vesaj

Closing comment (2021-12-07T13:38:07Z): Hello @mayo589  - thank yoi for the suggestion.
It is a dupe of #642.
Additionally, we're currently collecting the proposals for command sets here: #7375.
Please, feel free to add any additional thoughts in there.
Repository: SharePoint/sp-dev-docs

Issue #6496: Getting “Sorry, something went wrong with adding the app. Click to retry.” when adding a SPFx library to a site
Created: 2020-11-23T18:18:34Z
Category

 Bug

Describe the bug
I am getting “Sorry, something went wrong with adding the app. Click to retry.” when adding a SPFx library component to a site.
Steps to reproduce

Create an out of the box SPFx Library component.
Upload to tenant app catalogue (don't deploy tenant wide)
Add the app to some site
Switch back to classic view on site contents to see the error

Expected behavior
Apps successfully gets added to the site
Environment details (development & target environment)

DELETE THIS LINE BEFORE SUBMITTING - Complete the following (if ignored you'll be prompted for it before we can address your issue... save the time and provide it in your initial submission).

Windows 10
SharePoint Online
Node v10
Chrome 87
VS Code | SPFx v1.10.0
Comments
I went into the app details for the instance to check the errors, but when I click the link I get this image. Then it just goes into a white page with no content.

Duplicate issue #6902: SPFX library solution cannot be added to site collection
Created: 2021-04-12T07:43:38Z
Category

 Bug

Describe the bug
I am getting “Sorry, something went wrong with adding the app. Click to retry.” when adding a SPFx library component to a site.
Steps to reproduce

Created a SPFX library component.
Deployed the library package solution tenant wide.
Install the library component while adding app to site.
Library component is always installing and error can be seen in the site contents of classic view.

Expected behavior
SPFX Library component solution app should be successfully added to the site.
Environment details (development & target environment)
SharePoint online
SPFX v1.10.0
Additional context
Found some posts with the same reason. We are trying to find official statement that library component is not supported to install in site collection by adding as App.

Closing comment (2022-01-10T17:16:49Z): Sorry @arunakshi for the long delay.
This issue seems like a dupe of #6496. And, as mentioned there, the issue is fixed by now.
Please, feel free to open a new issue if you're still experiencing any problems with Library Components install.
Repository: SharePoint/sp-dev-docs

Issue #4054: ApplicationCustomizer: context.application.navigatedEvent logic
Created: 2019-05-28T16:31:19Z
Category

 Question
 Typo
 Bug
 Additional article idea

Could you please explain the logic, how context.application.navigatedEvent is called in ApplicationCustomizer?
From what I can see:

it is called when navigating between pages. For example, from one list to another. That seems correct.
If you navigate between two same pages (in my cases - two lists) it stops firing. List A -> List B - fired. List B -> List A - no fired
it is called when navigating between views in the same list FOR THE FIRST TIME ONLY. It seems weird.

Duplicate issue #5029: ApplicationCustomizer navigated event not firing when creating a new page
Created: 2019-12-18T03:51:42Z
Category

 Question
 Typo
 Bug
 Additional article idea

Expected or Desired Behavior
When a user is on a Site Page and clicks to add a new page via the command bar drop down or via "Add a page" in the settings panel the navigatedEvent should fire as the URL changes to:

"SitePages/newpage.aspx?Mode=Edit"
Then to a generated page URL e.g "SitePages/nmorjnzr.aspx?Mode=Edit"
Then to whatever title you have set in the page e.g "SitePages/addedpage.aspx"

This should then update the context object with the correct list item id of the newly created page in the application customizer (context.pageContext.listItem.id).
Observed Behavior
Navigated event is not fired on new page creation. The user is on the new page that was created but the current context is incorrect.
Steps to Reproduce
SharePoint Environment: SharePoint Online
SPFx Version: 1.9.1
Browser: Chrome
Create an application customizer that logs to the console each time the navigatedEvent fires.
It will not log when creating a new page from the command bar drop down or via "Add a page" in the settings panel. I'll provide a repo if necessary.

Closing comment (2019-12-18T10:53:53Z): Known issues with this event, this is a dupe of #4054 & #3210... as such can you consolidate any additional feedback to those issues for tracking? Thanks!
Repository: SharePoint/sp-dev-docs

Issue #2624: Cannot deploy packages anymore
Created: 2018-09-24T14:30:17Z
Category

 Question
 Typo
 Bug
 Additional article idea

Cannot deploy a previously good package anymore, this now results in a strange app catalog behavior.
Observed Behavior
Grabbed a previously good package from an earlier build, deployed this package to the app catalog.
Also tried deploying this package to a fresh (first release enabled) tenant (same problem).


The Title and ProductId are missing, and the version is incorrectly shown.
There is no deployment error logged.



App details screen is showing: 'Invalid SharePoint App Product ID:'

Duplicate issue #2642: App Package isn't detected correctly when uploaded to App Catalog
Created: 2018-09-26T11:27:09Z
Category

 Question
 Typo
 Bug
 Additional article idea

Expected or Desired Behavior
I upload an .spkkg to the App Catalog. I expect the Title, App Version, etc. to be displayed and the status of the app to be "Deployed".
Observed Behavior

The second line is good, everything is detected, etc. This is with a simple app that requests no permissions, etc.
However the first row is not good. Seems like that specific package cannot be parsed. And the status is not "Deployed". However I do not get any error message or additional information.
Additional Information

I can't say, since when it happens - as today is the first time I deployed the app since a couple of days.
However I can say that

this behavior occurs on different, new (demo) tenants...
...with the exact same app package that used to work a couple of days.


Updating the app on a tenant where it is already deployed doesn't work either.
So something must have changed, but I can't figure out, what it is.
I created a new app using the newest yo generator, and that one works too.

AppManifest.xml
<?xml version="1.0" encoding="utf-8"?>
<App xmlns="http://schemas.microsoft.com/sharepoint/2012/app/manifest" Name="XXX" ProductID="416b9b7c-5b8d-417b-ac86-0ae6a9cf43d5" Version="3.0.2.0" SharePointMinVersion="16.0.0.0" IsClientSideSolution="true">
  <Properties>
    <Title>XXX</Title>
  </Properties>
  <WebApiPermissionRequests>
    <WebApiPermissionRequest ResourceId="Microsoft Graph" Scope="People.Read"/>
    <WebApiPermissionRequest ResourceId="Microsoft Graph" Scope="Mail.Read"/>
    <WebApiPermissionRequest ResourceId="Microsoft Graph" Scope="Calendars.Read"/>
    <WebApiPermissionRequest ResourceId="Microsoft Graph" Scope="Sites.Read.All"/>
    <WebApiPermissionRequest ResourceId="Microsoft Graph" Scope="Group.Read.All"/>
    <WebApiPermissionRequest ResourceId="XXX" Scope="user_impersonation"/>
    <WebApiPermissionRequest ResourceId="Office 365 Exchange Online" Scope="Tasks.Read"/>
  </WebApiPermissionRequests>
</App>

Closing comment (2018-09-26T21:10:59Z): Might not be a duplicate of #2624 but is going in the same direction. However, there the length of WebApiPermissionRequest seems to be the problem. And in my case here it stopped working without any changes in the manifest. The result is the same though: The app can not be added/updated correctly in the app catalog.
Repository: Shopify/shopify-cli

Issue #740: new shopify cli 1.0.0 installed but got error 
Created: 2020-07-15T09:51:53Z
Issue summary
I've just migrated new version from old version according to https://shopify.github.io/shopify-app-cli/getting-started/migrate/
After installing, the directory "~/.shopify-app-cli/" doesn't generated and displayed error when I try any shopify command.
error:
Traceback (most recent call last):
        6: from /usr/local/Cellar/shopify-cli/1.0.0/src/bin/shopify:30:in `<main>'
        5: from /usr/local/Cellar/shopify-cli/1.0.0/src/vendor/deps/cli-kit/lib/cli/kit/error_handler.rb:21:in `call'
        4: from /usr/local/Cellar/shopify-cli/1.0.0/src/vendor/deps/cli-kit/lib/cli/kit/error_handler.rb:75:in `handle_abort'
        3: from /usr/local/Cellar/shopify-cli/1.0.0/src/bin/shopify:31:in `block in <main>'
        2: from /usr/local/Cellar/shopify-cli/1.0.0/src/lib/shopify-cli/core/entry_point.rb:11:in `call'
        1: from /usr/local/Cellar/shopify-cli/1.0.0/src/lib/shopify-cli/core/entry_point.rb:11:in `open'
/usr/local/Cellar/shopify-cli/1.0.0/src/lib/shopify-cli/core/entry_point.rb:11:in `initialize': The given fd is not accessible because RubyVM reserves it (ArgumentError)

Expected behavior
generate /.shopify-app-cli/ and then I can use shopify command
Actual behavior
not generate /.shopify-app-cli/ and error displayed
Steps to reproduce the problem

uninstall the old one. $ rm -rf ~/.shopify-app-cli/ and then commented out the line I found in ~/.zshrc
install new version. $ brew tap shopify/shopify then $ brew install shopify-cli
run shopify version to display error message

Specifications

App type: 1.0.0
Operating System: macOS Catalina 10.15.5
Shell: zsh
Ruby version (ruby -v): ruby 2.6.3p62 (2019-04-16 revision 67580) [universal.x86_64-darwin19]

Duplicate issue #742: v1 has killed the 'shopify' command: "shopify command is no longer bundled with shopify_api."
Created: 2020-07-15T15:37:52Z
Migrating to v1 by following the migration guide has me in a state with this error:
shopify command is no longer bundled with shopify_api.
if you need these tools, install the shopify_cli gem

I have closely followed the migration guide multiple times, double- and triple-checked my bash profile files for Shopify-related lines and removed them, I've un-and re-installed the shopify-cli gem multiple times, etc.
I no longer have ~/.shopify-app-cli/shopify.sh as deleting it was part of the migration steps, I'm not sure if it's supposed to have been replaced.
This is on MacOS 10.15.5, Ruby 2.7.0 installed via RVM.
Has the command changed? Something else I'm missing? I know at least one other with the same issue.

Closing comment (2020-07-15T20:36:11Z): Since this is now a duplicate of #740 we will track further update on that issue. It will remain open until we can confirm that it is working again for you.
Repository: Shopify/shopify-cli

Issue #1360: Cannot pull theme. Dozens of errors with image assets.
Created: 2021-07-08T21:53:30Z
Write a short description of the issue here ↓
I'm making multiple attempts to pull an existing theme from shopify and shopify-cli shopify theme pull -i 12463859322 keeps throwing errors
Shopify Cli Version 2.0.2 installed via Ruby Gems 3.2.21
➜  general git:(master) ✗ shopify theme pull -i 1234567891011
┏━━ Pulling theme files from Swatch Debug Jul 8 (#1234567891011) on store.myshopify.com ━━━━━━━━━━━
┃                                                                                                         100%
┃ ERROR get assets/adobe-w-undyed.png: wrong number of arguments (given 4, expected 2..3)
┃ // About 50 more lines of this error for various image assets for the theme.
┃ ERROR get assets/white.png: wrong number of arguments (given 4, expected 2..3)
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ (72.51s) ━━
✓ Theme pulled successfully (Nope!)

Duplicate issue #1396: Fonts are not pulling
Created: 2021-07-17T12:07:28Z
Issue summary
Using shopify CLI the pull when having custom font's in assets is trigerring error and not downloading theme font's
Expected behavior
Theme font's need to be downloaded.
Actual behavior
┃ ERROR get assets/Arial-Bold.eot: wrong number of arguments (given 4, expected 2..3)
┃ ERROR get assets/Arial-Bold.ttf: wrong number of arguments (given 4, expected 2..3)
┃ ERROR get assets/Arial-Bold.woff2: wrong number of arguments (given 4, expected 2..3)
┃ ERROR get assets/Arial-Bold.woff: wrong number of arguments (given 4, expected 2..3)
┃ ERROR get assets/Arial.eot: wrong number of arguments (given 4, expected 2..3)
┃ ERROR get assets/Arial.ttf: wrong number of arguments (given 4, expected 2..3)
┃ ERROR get assets/Arial.woff2: wrong number of arguments (given 4, expected 2..3)
┃ ERROR get assets/Arial.woff: wrong number of arguments (given 4, expected 2..3)

Steps to reproduce the problem

Add font's in assets folder and push theme
Pull curently pushed theme and the error will trigger

Reduced test case
The best way to get your bug fixed is to provide a reduced test case.
Specifications

App type:
Operating System: Windows 10
Shell: PowerShell
Ruby version (ruby -v): ruby 3.0.1p64 (2021-04-05 revision 0fb782ee38) [x64-mingw32]

Closing comment (2021-11-02T19:31:23Z): Closing as duplicate of #1360, which should now be fixed.
Repository: Shopify/shopify-cli

Issue #1409: Hot reload not working correctly
Created: 2021-07-26T17:16:47Z
Issue summary
The hot reload seems to be refreshing the page but the change don't appear until the page is refreshed manually.
Expected behavior
The page should refresh when a file is changed and the change should appear immediately.
Actual behavior
The page refresh but the change is not there.
Steps to reproduce the problem

Do shopify theme serve
Modify file
Save

Specifications

Operating System: Windows 10
Shell: powershell
Ruby version (ruby -v): 2.7.3p180

Duplicate issue #1483: Shopfy theme serve serves old *.liquid files and does not autoreload *.liquid properly
Created: 2021-08-28T19:54:39Z
shopify theme serve does not show lates template changes
I'm developing Shopify theme with CLI v 2.2.2 . Running shopify theme serve shows outdated templates on local http://127.0.0.1:9292/cart url. I will change something in the main-card.liquid file, but it will not reflect when the page is autoreloaded ( or reloaded by hand ). Disabled browser cache, etc.
Expected behavior
When modifying a .liquid template after the auto-reload the page should display the new  content.
Actual behavior
What actually happens?
The local http://127.0.0.1:9292/cart reloads and shows old ( probably cached ) version of the page. Changing CSS for example is shown properly after reload.
Steps to reproduce the problem

Create new custom theme
Create cart.json with section "main": { "type": "main-cart" } and change something in main-cart.liquid


Specifications

App type: Theme
Operating System: OSX Big Sur 11.3
Shell: Zsh
Ruby version (ruby -v): 2.6.3p62

Closing comment (2021-11-03T15:41:27Z): Closing as duplicate of #1409
Repository: Shopify/shopify-cli

Issue #1333: `theme serve` not working with password protected shop signing-in as staff
Created: 2021-07-02T15:01:17Z
Issue summary
Write a short description of the issue here ↓
I'm following the Getting Started tutorial on https://shopify.dev/themes/getting-started/create.
When I run shopify theme serve in the CLI, the URL address provided (http://127.0.0.1:9292) prompts me to enter the store password or login as store owner. Then, when I attempt to login as store owner and submit my credentials, I receive an error page (We'll be back soon).

I was able to successfully workaround this and access the page when I entered the password, but since I was following the getting started tutorial I had to log in via the admin and change the password first.
Specifications
App type: Theme, CLI
Operating System: macOS 11.4
Shell: /bin/zsh
Ruby version (ruby -v): ruby 2.6.3p62 (2019-04-16 revision 67580)

Duplicate issue #1415: shopify theme serve - infinite redirect
Created: 2021-07-29T13:00:52Z
Issue summary
Write a short description of the issue here ↓
When trying to access the local URL that shopify theme serve gives you (http://127.0.0.1:9292) it puts you in an infinite redirect loop.
Expected behavior
What do you think should happen?
It should allow me to access the site
Actual behavior
What actually happens?
Infinite redirect loop






Steps to reproduce the problem

run shopify theme serve on any project
visit http://127.0.0.1:9292

Closing comment (2021-11-02T20:06:33Z): This might have something to do with the shop being password protected. Did you log in as staff prior to this happening by any change? Might be related to #1333.
Repository: Shopify/shopify-cli

Issue #1309: Theme serve command returns scope error
Created: 2021-06-30T09:14:33Z
Whenever I run shopify theme serve, it returns this error:
✗ You are not authorized to edit themes on XXX.myshopify.com.
Make sure you are a user of that store, and allowed to edit themes.

shopify whoami returns the following:
Logged into store XXX.myshopify.com in partner organization XXX Org

I can login to this store and edit themes the "normal" way.
Specifications

Shopify CLI version: 2.0.1

Duplicate issue #1313: Shopify CLI not working as expected for store owner user
Created: 2021-06-30T13:52:09Z
Issue summary
If I logged in via "shopify login" as store owner but not as a store staff
all off commands like "shopify theme pull" or "shopify theme serve" return an error
Expected behavior
should work like described in documentation
Actual behavior
What actually happens?
I've got en error:
megazoid@MacBook-Pro % shopify theme pull
This command ran with ID: 34125
Please include this information in any issues/report along with relevant logs
/usr/local/Cellar/shopify-cli/2.0.1/gems/shopify-cli-2.0.1/lib/shopify-cli/api.rb:72:in `block in request': 403 (ShopifyCli::API::APIRequestForbiddenError)
{"errors":"Unauthorized Access"}
Steps to reproduce the problem

Create a new store (2.0)
shopify login --store=[STORE] using your account where you are a store owner only
shopify theme pull

Closing comment (2021-06-30T17:16:12Z): Duplicate of #1309
Repository: Shopify/shopify-cli

Issue #1409: Hot reload not working correctly
Created: 2021-07-26T17:16:47Z
Issue summary
The hot reload seems to be refreshing the page but the change don't appear until the page is refreshed manually.
Expected behavior
The page should refresh when a file is changed and the change should appear immediately.
Actual behavior
The page refresh but the change is not there.
Steps to reproduce the problem

Do shopify theme serve
Modify file
Save

Specifications

Operating System: Windows 10
Shell: powershell
Ruby version (ruby -v): 2.7.3p180

Duplicate issue #1450: CLI is not detecting any local changes when running shopify theme serve
Created: 2021-08-13T08:36:34Z
Issue summary
When I run shopify-theme-serve, any changes made to the code aren't updated in the browser.
Expected behavior
I'm not sure what to expect as it's my first time using it.
Actual behavior
Changes aren't updated and I don't see any change or activity in the CLI.  The CLI doesn't seem to be picking up changes.
Steps to reproduce the problem
I just followed the tutorial in the Shopify docs.
Specifications

App type: Theme
Operating System: Mac OS v11.5.2
Shell: zsh
Ruby version (ruby -v): 3.0.2p107

Closing comment (2021-11-03T14:58:26Z): Closing as duplicate of #1409
Repository: Shopify/shopify_app

Issue #874: capybara tests failing because of secure attribute on shopify session cookie
Created: 2020-01-25T18:06:52Z
Unable to run rspecs with js: true. Because while setting the shopify session cookie secure attribute is set by default.
As Rspecs are run mostly on http not on https protocol authentication is failing, becuase cookie is not set correctly on browser and its not sent back to server on following requests.
work around can be disabling the same site option in test mode.
ShopifyApp.configuration.enable_same_site_none = false

Duplicate issue #891: SameSiteCookieMiddleware breaks cookies in test environment
Created: 2020-02-06T23:46:17Z
We updated from version 11.4.0 of the gem to 12.0.0. After that upgrade the majority of our system specs were breaking. I isolated the upgrade to ensure that it was only the shopify_app gem (not some other dependency) version change that caused the issue. Diff of 11.4.0 to 12.0.0
The issue manifested as an inability to set the flash within Rails. Many of our specs were validating that certain flash messages were present in the page and those specs were failing. After digging in a little deeper I found that no session cookie was being set at all in the browser.
I was able to work around this issue by disabling the enable_same_site_none configuration option for the test environment. This is not an ideal fix because it creates parity between the test environment and production, but it will get us by for now.
The other environments do not seem to exhibit any issues with this middleware.
Workaround:
# Add this within the ShopifyApp.configure block
config.enable_same_site_none = !Rails.env.test?

Closing comment (2020-02-07T15:50:20Z): Will be fixed when I release today with #876
This is also a duplicate of #874 If you need this fixed today, install from master
Repository: Shopify/shopify_app

Issue #64: Add tests to the generators' templates.
Created: 2013-09-27T18:08:26Z
There's no tests for any of them

Duplicate issue #65: Add tests to the generators' templates.
Created: 2013-09-27T18:08:26Z
There's no tests for any of them

Closing comment (2014-06-05T02:20:32Z): Duplicate of #64
Repository: Shopify/shopify_app

Issue #1181: Per user auth from app list redirect with session query parameter
Created: 2021-02-08T03:21:39Z
Hi folks, Thanks for your work on this gem!
I've had non-embedded Shop session authentication working for years, and have been trying to follow the instructions for adding per-user session. I have it working when I use my own login page, however, when I click the link from a list of a shop's installed apps, I end up in an infinite loop.
From my research, the installed app list link redirects to app's URL with a session value in the query params.  From some debugging, it appears that session query param is tripping up part of LoginProtection.  After a successful Oauth login, shopify_app returns to the original URL that has the params[:session].  However, in LoginProtection the session[:user_session] from Oauth does not match the params[:session] from the redirect query string, triggering the session to be cleared, and login is forced again.  1. Successful login.  2. redirect to return URL. 3. sessions don't match in LoginProtection.  4. clear session.  Repeat.
I would guess that session param from the app list redirect should match the Oauth session?
Or should I be authenticating differently from the app list URL that has the session param?
What am I missing?
Thanks!
# shopify_app/lib/shopify_app/controller_concerns/login_protection.rb

def login_again_if_different_user_or_shop
   if session[:user_session].present? && params[:session].present? # session data was sent/stored correctly
     clear_session = session[:user_session] != params[:session] # current user is different from stored user
   end
...

Duplicate issue #1263: Can't open non-embedded app from within store's app dashboard
Created: 2021-05-04T11:54:52Z
Description
Login works through the app, on myapp.com/login.
It doesn't work through the Apps Dashboard on my test store (mystore.com/admin/apps -> click on app name)
This is a brand new app, the code and all steps to reproduce are on https://github.com/wnm/redirect-loop-test-app/
Steps to Reproduce

rails new
bundle add shopify_app
rails generate shopify_app --embedded false
rails db:migrate
rails generate shopify_app:user_model
rails db:migrate
add config.user_session_repository = 'User' to initializer
install app through app.com/login on test store
go to /admin/apps on test store, click on app

Expected behavior:
You should be able to open app through app dashboard
Actual behavior:
A redirect loop occurs
Reproduces how often:
100%
Browsers
Firefox, Chrome, Safari
Gem versions
18.0.0
Additional Information

config.embedded_app = false
config.shop_session_repository = 'Shop'
config.user_session_repository = 'User'
config.reauth_on_access_scope_changes = true
config.allow_jwt_authentication = false
config.allow_cookie_authentication = true
Security
[x] I have redacted any private information from my logs or code snippets.

Closing comment (2021-05-06T10:00:49Z): Just discovered that this is a duplicate of #1181
Repository: Shopify/shopify_app

Issue #814: Valid digest error in request_storage_access javascript file on Heroku
Created: 2019-11-04T22:53:00Z
After doing gem updates I started getting the following error for the request_storage_access file in production (a Heroku staging server) only:
Failed to find valid digest in the 'integrity' attribute for for resource 'https://[myapp]/assets/shopify_app/request_storage_access-[hash].js' with computed SHA-265 integrity '[different-hash]'. The resource has been blocked.

It looks like this error happened because I updated Sprockets to 4.0.0 and may be related to this very old but still open issue in sprockets-rails: rails/sprockets-rails#393. It looks like I have fixed the issue temporarily by downgrading Sprockets to 3.7.2 by adding gem 'sprockets', '~> 3.0' to my Gemfile.
I also noticed this issue which may be related. But I can confirm that my assets were compiling properly when deploying to Heroku. I wasn't getting 404 errors.
As mentioned, it looks like I have resolved this temporarily but thought I'd flag the issue in case others were running into it and because it may come up more often in the future.
Environment info:
Browser: Chrome Version 78.0.3904.70 (Official Build) (64-bit)
OS: MacOS Mojave 10.14.6
Ruby: 2.5.7
Rails: 5.2.3
Shopify App: 11.2.0

Duplicate issue #865: Just another borked install. 
Created: 2020-01-20T16:28:05Z
shopify app: 11.5
shopify_api: 8.1
rails 6.0.2
Completely messed up. Went for an install and got this crap:
None of the “sha256” hashes in the integrity attribute match the content of the subresource. login
​This gem is quickly sinking into unusable.
It does work with LOCALHOST fine. OK. It is a Custom App. I used the generated install link to get to this dismal dark place with a cloud based version of the App.

Closing comment (2020-01-20T17:45:52Z): Duplicate of #814 This is actually an issue with current sprockets. Please pin your sprockets to < 4
Repository: Shopify/shopify_app

Issue #1181: Per user auth from app list redirect with session query parameter
Created: 2021-02-08T03:21:39Z
Hi folks, Thanks for your work on this gem!
I've had non-embedded Shop session authentication working for years, and have been trying to follow the instructions for adding per-user session. I have it working when I use my own login page, however, when I click the link from a list of a shop's installed apps, I end up in an infinite loop.
From my research, the installed app list link redirects to app's URL with a session value in the query params.  From some debugging, it appears that session query param is tripping up part of LoginProtection.  After a successful Oauth login, shopify_app returns to the original URL that has the params[:session].  However, in LoginProtection the session[:user_session] from Oauth does not match the params[:session] from the redirect query string, triggering the session to be cleared, and login is forced again.  1. Successful login.  2. redirect to return URL. 3. sessions don't match in LoginProtection.  4. clear session.  Repeat.
I would guess that session param from the app list redirect should match the Oauth session?
Or should I be authenticating differently from the app list URL that has the session param?
What am I missing?
Thanks!
# shopify_app/lib/shopify_app/controller_concerns/login_protection.rb

def login_again_if_different_user_or_shop
   if session[:user_session].present? && params[:session].present? # session data was sent/stored correctly
     clear_session = session[:user_session] != params[:session] # current user is different from stored user
   end
...

Duplicate issue #1217: Turbo link issues
Created: 2021-03-14T18:54:50Z
Hi!
My issue is that I'm creating shopify multiple page app using rails and turbo link. I followed complete steps from the documentation but after installing my app than it redirect me to login page again and again. I don't know what's the issue behind it.
If anyone help me I'll  very thankful to them.

Closing comment (2021-04-08T15:32:20Z): Could this be related to #1181 ?