primordic/IssueDupesLite huggingface dataset:
Repository: peaceiris/actions-gh-pages

Issue #318: Deploy from master branch to other master branch
Created: 2020-05-22T15:02:09Z
Describe the bug
Deployment from master branch of one repo to master branch of other repo failes with the following error:
##[error]Action failed with "You deploy from master to master"

To Reproduce
      - uses: peaceiris/actions-gh-pages@v3
        with:
          github_token: ${{ secrets.SUPER_GITHUB_TOKEN }}
          external_repository: [other repo]
          publish_dir: target/site
          publish_branch: master

Expected behavior
Allow deploying to other masterbranch when external_repository is set.
Your YAML file
See above.

Duplicate issue #245: Prohibited branch detection does not work
Created: 2020-04-23T04:09:38Z
Describe the bug
When users set a publish_branch that is the same as a branch triggered by the workflow, this action stops the deployment to protect the branch.

  
    
      actions-gh-pages/src/set-tokens.ts
    
    
        Lines 76 to 81
      in
      e3404eb
    
  
  
    

        
          
           if (eventName === 'push') { 
        

        
          
             isProhibitedBranch = ref.includes(`refs/heads/${publishBranch}`); 
        

        
          
             if (isProhibitedBranch) { 
        

        
          
               throw new Error(`You deploy from ${publishBranch} to ${publishBranch}`); 
        

        
          
             } 
        

        
          
           } 
        
    
  


Currently, this protection behavior does not work.
To Reproduce
With peaceiris/actions-gh-pages@v3
on:
  push:
    branches:
      - master
...
          publish_branch: master
Expected behavior
This Action should return the error You deploy from master to master
Screenshots

Your YAML file

A link to your repository: https://github.com/peaceiris/test-mdbook
A link to your YAML file: https://github.com/peaceiris/test-mdbook/actions/runs/85307348/workflow
A link to your workflow log: https://github.com/peaceiris/test-mdbook/runs/610595170?check_suite_focus=true#step:6:116

Additional context
I found this bug in this article: AsciidocのドキュメントをGitHub Actionsを用いてGitHub Pagesで公開する。 - Qiita
This protection should be also implemented for personal_token, deploy_key, and eventName === 'pull_request'.

Closing comment (2020-05-28T07:02:11Z): @abedurftig Did you understand your mistake which is related to #318?
I found your your workflow using github_token to deploy to an external repository. You should have used personal_token. Is the README unfriendly?

README.md
You can use deploy_key or personal_token. When you use deploy_key, set your private key to the repository which includes this action and set your public key to your external repository.
Be careful, GITHUB_TOKEN has no permission to access to external repositories.
Repository: peaceiris/actions-gh-pages

Issue #163: option to commit .github files
Created: 2020-03-17T09:55:20Z
Thank you for sharing this good project :)
Is your feature request related to a problem? Please describe.
In some use cases, we want to commit .github workflow files so that we can trigger actions on gh-pages branch.
Describe the solution you'd like
An option to determine if .github files to commit or not.
Describe alternatives you've considered
I made a commit to disable .github filtering, but I know this is a temporary workaround.
specup@9cb1a7c

Duplicate issue #415: Give an option to not omit .github dir
Created: 2020-07-25T10:54:17Z
Is your feature request related to a problem? Please describe
I am using this Action to update files in my master branch, including a workflow file (which is to schedule a trigger to another workflow).
But as Here filters, this Action ignores the .github dir, which prevents the workflow file to be created
Describe the solution you'd like
An option to force copy .github (and .git?) directory
Describe alternatives you've considered

Additional context

Closing comment (2020-07-25T10:59:24Z): Duplicate of #163. Please watch the issue.
Repository: peaceiris/actions-gh-pages

Issue #677: proposal: Bump node from 12 to 16
Created: 2021-12-08T02:35:04Z
Checklist

 I am using the latest version of this action.
 I have read the latest README and followed the instructions.
 I have read the latest GitHub Actions official documentation and learned the basic spec and concepts.

Describe your proposal
Bump runtime version from node12 to node16
Describe the solution you'd like

update action.yml
update test
update CI

Describe alternatives you've considered
N/A
Additional context

actions/runner#772
actions/runner#1439

Duplicate issue #788: proposal: Upgrade NodeJS
Created: 2022-10-17T02:07:56Z
Checklist

 I am using the latest version of this action.
 I have read the latest README and followed the instructions.
 I have read the latest GitHub Actions official documentation and learned the basic spec and concepts.

Describe your proposal
Actions says:
Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: peaceiris/actions-gh-pages

Describe the solution you'd like
Upgrade NodeJS
Describe alternatives you've considered
No response
Additional context
No response

Closing comment (2022-10-17T02:12:06Z): Thanks, duplicate of #677
Repository: peaceiris/actions-gh-pages

Issue #759: proposal: auto-retry
Created: 2022-06-08T11:36:40Z
Checklist

 I am using the latest version of this action.
 I have read the latest README and followed the instructions.
 I have read the latest GitHub Actions official documentation and learned the basic spec and concepts.

Describe your proposal
Action fails intermitently due to concurrent updates

Describe the solution you'd like
Action should implement/support an auto retry mechanism e.g. retry: 3
Describe alternatives you've considered
Two consecutive steps for publishing where the second one only runs if the first one fails
Additional context
No response

Duplicate issue #1078: support: action failed with "fetch first" hint
Created: 2024-05-18T08:38:18Z
Checklist

 I am using the latest version of this action.
 I have read the latest README and followed the instructions.
 I have read the latest GitHub Actions official documentation and learned the basic spec and concepts.

Describe your question
First of all, thanks for this awesome action !
I'm using it from a job with a matrix configuration, so the action may run concurrently.
Sometimes, it fails because the gh-pages branch is not up-to-date (see logs).
Any advice to prevent this?
Relevant links
My repository is private.
Relevant log output
Push the commit or tag
  /usr/bin/git push origin gh-pages
  To https://github.com/semarchy/mdm.git
   ! [rejected]        gh-pages -> gh-pages (fetch first)
  error: failed to push some refs to 'https://github.com/***/mdm.git'
  hint: Updates were rejected because the remote contains work that you do not
  hint: have locally. This is usually caused by another repository pushing to
  hint: the same ref. If you want to integrate the remote changes, use
  hint: 'git pull' before pushing again.
  hint: See the 'Note about fast-forwards' in 'git push --help' for details.
  Error: Action failed with "The process '/usr/bin/git' failed with exit code 1"

Additional context.
My matrix configuration:
      matrix:
        browser: [ chrome, firefox ]
        java_version: [ "17", "21" ]

How I have configured the step:
      - name: Upload report to GH Pages
        uses: peaceiris/actions-gh-pages@v4
        if: always()
        with:
          github_token: ${{ secrets.GITHUB_TOKEN }}
          publish_dir: playwright-report/
          destination_dir: "${{ env.TIMESTAMP }}/${{ matrix.browser }}/java${{ matrix.java_version }}/report"

Closing comment (2024-05-18T09:11:36Z): Thanks, this seems to be related to #759

#759
Repository: peaceiris/actions-gh-pages

Issue #163: option to commit .github files
Created: 2020-03-17T09:55:20Z
Thank you for sharing this good project :)
Is your feature request related to a problem? Please describe.
In some use cases, we want to commit .github workflow files so that we can trigger actions on gh-pages branch.
Describe the solution you'd like
An option to determine if .github files to commit or not.
Describe alternatives you've considered
I made a commit to disable .github filtering, but I know this is a temporary workaround.
specup@9cb1a7c

Duplicate issue #273: remove only certain directories
Created: 2020-05-03T21:07:38Z
Is your feature request related to a problem? Please describe
I update only certain directories of a repository, however their filenames change. Thus, I need a way to clean only certain directories before copying the new files.
Describe the solution you'd like
a glob pattern that specifies either the files to keep or another glob pattern that specifies the files to remove.
Describe alternatives you've considered
implementing it using a shell script but the deploy key isn't that easy.

Closing comment (2020-05-03T21:24:13Z): I don't fully understand the background of your issue, but this issue seems to be a duplicate of #163

implementing it using a shell script but the deploy key isn't that easy.

Shell Script? Are you still using version 2?
This Action has been migrated to a TypeScript Action (version 3). There are no plans to add any new features to version 2. Please use the v3.
Repository: peaceiris/actions-gh-pages

Issue #45: cp: can't create '/.git': File exists | Error on user type repository deployment
Created: 2019-10-22T07:38:33Z
Hello I found a recurring error when I try to deploy to my user type repository.
Stack trace:
/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/blog/blog":"/github/workspace" fbc64f:bd4f8c40a2ff4d509a3eda2d208b73d4
INFO: Deploy to asurbernardo/asurbernardo.github.io
INFO: setup with ACTIONS_DEPLOY_KEY
# github.com:22 SSH-2.0-babeld-85ff8279
Cloning into '/github/home/ghpages_12475'...
Warning: Permanently added the RSA host key for IP address '192.30.253.112' to the list of known hosts.
rm '404.html'
rm 'CNAME'
rm 'README.md'
rm 'commento.html'
rm 'images/design-inspiration.jpg'
rm 'index.html'
rm 'index.xml'
rm 'install-sw.html'
rm 'manifest.json'
rm 'offline.html'
rm 'posts/el-primer-post-en-mi-nuevo-blog/index.html'
rm 'posts/index.html'
rm 'posts/index.xml'
rm 'posts/la-primera-iteracion-amp-estilos-y-miscelanea/index.html'
rm 'posts/mi-primer-post/index.html'
rm 'sitemap.xml'
rm 'sw.js'
rm 'tags/deploy/index.html'
rm 'tags/deploy/index.xml'
rm 'tags/evolutivo/index.html'
rm 'tags/evolutivo/index.xml'
rm 'tags/git/index.html'
rm 'tags/git/index.xml'
rm 'tags/index.html'
rm 'tags/index.xml'
rm 'tags/iteracion/index.html'
rm 'tags/iteracion/index.xml'
rm 'tags/iteración/index.html'
rm 'tags/iteración/index.xml'
cp: can't create '/github/home/ghpages_12475/.git': File exists
##[error]Docker run failed with exit code 123

My action main.yml:
name: Deploy blog
on:
  push:
    branches:
    - master

jobs:
  build-deploy:
    runs-on: ubuntu-latest
    steps:

    - name: Pull source
      uses: actions/checkout@master
      with:
        submodules: true

    - name: Update submodules to latests master
      run: git submodule update --remote

    - name: Setup Hugo
      uses: peaceiris/actions-hugo@v2.2.2
      with:
        hugo-version: '0.58.3'
        extended: true

    - name: Build
      run: hugo -t amperage --gc --minify

    - name: Deploy script
      uses: peaceiris/actions-gh-pages@v2.5.0
      env:
        ACTIONS_DEPLOY_KEY: ${{ secrets.ACTIONS_DEPLOY_KEY }}
        EXTERNAL_REPOSITORY: asurbernardo/asurbernardo.github.io
        PUBLISH_BRANCH: master
        PUBLISH_DIR: ./public

I think I've followed the guide correctly, but maybe I'm missing something.

Duplicate issue #53: "can't create '/github/home/ghpages_30566/.git': File exists"
Created: 2019-11-21T20:00:52Z
Hello,
I am trying to build my Hugo website with peaceiris/actions-hugo and deploy with actions-gh-pages to the master branch of my GitHub pages repository.
It fails on the Deploy job where actions-gh-pages is used with the following error:
cp: can't create '/github/home/ghpages_30566/.git': File exists
##[error]Docker run failed with exit code 123


Logs
main.yml

Can it be because of the fact that ./public (my PUBLISH_DIR) is actually a submodule with GitHub pages repo? I used it to quickly build and deploy locally.
Thank you.

Closing comment (2019-11-21T23:54:10Z): Related to #45
Repository: peaceiris/actions-gh-pages

Issue #9: About limitation of GITHUB_TOKEN
Created: 2019-09-02T05:58:54Z
GitHub Actions v2 is still beta and deploying to GitHub Pages with GITHUB_TOKEN has some problems. Until it is fixed, I provide ACTIONS_DEPLOY_KEY to deploy with ssh from peaceiris/actions-gh-pages@v2.0.0

Duplicate issue #18: Deployment to git repository works but website is not deployed
Created: 2019-09-06T13:09:58Z
I have a strange behavior here, which is not strictly related to this action but kinds of defeat its purpose.
Here is a quite trivial repository showing this problem: https://github.com/nicolas-van/hugotest (the attached workflow: https://github.com/nicolas-van/hugotest/blob/master/.github/workflows/hugo.yml )
When I commit something the workflow performs correctly ( https://github.com/nicolas-van/hugotest/actions ) and I can validate it did deploy correctly to the gh-pages branch.
But when I take a look at the deployments ( https://github.com/nicolas-van/hugotest/deployments ) I can see that Github just didn't care re-deploying my website to its static content server. He doesn't seem to understand that there is a new version on the gh-pages branch and doesn't care re-deploying.
I suppose it has something to do with the fact that this action just erase all the commits on the gh-pages branch and make a force push. When I edit a file on that branch (thus creating a new commit) Github seems to detect it correctly and re-deploy my Github Pages site.
Does anyone else has encountered that problem ? If I'm not the only one maybe we could consider adding a mode similar to what Travis uses ( See keep_history https://docs.travis-ci.com/user/deployment/pages/).

Closing comment (2019-09-06T13:59:11Z): Nevermind, it seems like this is just a duplicate of #9
Repository: peaceiris/actions-gh-pages

Issue #677: proposal: Bump node from 12 to 16
Created: 2021-12-08T02:35:04Z
Checklist

 I am using the latest version of this action.
 I have read the latest README and followed the instructions.
 I have read the latest GitHub Actions official documentation and learned the basic spec and concepts.

Describe your proposal
Bump runtime version from node12 to node16
Describe the solution you'd like

update action.yml
update test
update CI

Describe alternatives you've considered
N/A
Additional context

actions/runner#772
actions/runner#1439

Duplicate issue #786: proposal: Upgrade dependency to node16
Created: 2022-10-13T14:02:13Z
Checklist

 I am using the latest version of this action.
 I have read the latest README and followed the instructions.
 I have read the latest GitHub Actions official documentation and learned the basic spec and concepts.

Describe your proposal
The action should be updated to run on Node16 as Github now shows a warning for actions running on Node12, see https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/
Describe the solution you'd like
Update the action to run on Node16
Describe alternatives you've considered
No response
Additional context
No response

Closing comment (2022-10-13T14:06:25Z): Thanks, duplicate of #677
Repository: penpot/penpot

Issue #688: Can not write character with special accent
Created: 2021-02-23T16:45:10Z
Describe the bug
I want to write text in French in my designs. I'm able to write characters like "é" and "è", but not "û" and "ê". To write these characters on other apps, I need to tap on the "^" button of the keyboard and then on the "e" letter as an example. In Penpot the characters simply doesn't show up.
For the moment the workaround I use is to copy the characters inside Penpot.
To Reproduce
Steps to reproduce the behavior:

Create a text box
Write the following text: "un coût"
See that only this has been written: "un cot"

Expected behavior
Have "un coût" written
Desktop (please complete the following information):

OS: Linux (Arch Linux)
Browser (e.g. chrome, safari): Firefox Developer edition
Version (e.g. 22) 86.0b4

Environment (please complete the following information):
https://design.penpot.app

Duplicate issue #701: Internal server error when typing é
Created: 2021-02-24T20:04:11Z
Describe the bug
When trying to type é (e-acute) I get an internal server error
To Reproduce
Steps to reproduce the behavior:

Go to this file
Double-click on the Text-5 element to start editing the text
Type é
See error

Expected behavior
Add the é
Screenshots


Desktop (please complete the following information):

OS: Ubuntu
Browser Firefox

using SAAS (https://design.penpot.app)

Closing comment (2021-02-24T20:05:17Z): Duplicate of #688
Repository: penpot/penpot

Issue #620: Provide libraries for (open source, publicly available) icons
Created: 2021-02-10T11:44:26Z
Is your feature request related to a problem? Please describe.
I would like Penpot to provide user with libraries of icons which I can import to my projects, or have them shared so I can use them. There are collections of icons like https://feathericons.com/.
Describe the solution you'd like
In the current penpot UI, I'd like the following:

click assets
on the right hand side of the panel, under shared libraries, I'd like to see the libraries (icons, UI elements) which have been shared by the penpot community, or by penpot itself
from there I can import the library for my use

Describe alternatives you've considered
The current alternative is to import icons en-masse which takes a lot of time, or make them myself which is too onerous (and I cannot make icons)
Additional context
I can't think of any additional context needed. Let me know if I need to add more.
Thanks for penpot! ❤️

Duplicate issue #630: Create a "material design" dashboard as default
Created: 2021-02-11T10:24:08Z
Hi,
While creating a first project, the current "Penpot onboarding" screens allow to copy-past custom elements of the whole interface. That's extra useful!
As a lot of projects are following the materal design guidelines, a nice feature would be to display a sample project with these elements too. That would definitely speed up the process of creating a first screen.
Thanks in advance and congrats for this great tool that I just discovered and will use for my open source projects.

Closing comment (2021-02-24T14:31:09Z): Close this, as it's related to #620
Repository: penpot/penpot

Issue #4440: bug: Shape selection is triggered on mouseup, so click+dragging shapes doesn't work
Created: 2024-04-15T11:13:32Z
Steps To Reproduce

Create any shape
Try to click and drag that shape, i.e. press mouse on object, and move mouse

Expected behavior
The shape should be selected on mouse press, and moved while dragging / keeping mouse pressed
Actual behavior
The shape is selected only when moving mouse or releasing mouse button -
so the shape is not moving while dragging -
it requires user to

first click to select
next click + drag to move the object

Screenshots or video

Desktop (please complete the following information)

MacOSX 12.7.4
Firefox 124.0.2

Smartphone (please complete the following information)
No response
Environment (please complete the following information)
http://design.penpot.app
Frontend Stack Trace
No response
Backend Stack Trace
No response
Additional context
The behaviour is like before when you click and drag a board from its title (as seen in the screenshot)

Duplicate issue #4514: feature: Instantly activate drag and drop after clicking element
Created: 2024-04-24T16:32:58Z
Is your feature request related to a problem? Please describe.
I want to be able to directly move things around the canvas while clicking it just one time. It's annoying on the long run (while effectively working) to have to click on an element a second time to be able to drag and drop it around the canvas (see video)

  
    
    

    penpot-instant_drag_drop.mp4
    
  

  

  


Describe the solution you'd like.
I'd like to instantly be able to drag and drop an element after clicking and holding the mouse while selecting the element.
Describe alternatives you've considered.
No response
Additional context
No response

Closing comment (2024-04-26T09:34:46Z): Duplicate of #4440
Repository: penpot/penpot

Issue #5430: bug: wrong port in docker-compose.yaml 
Created: 2024-12-06T10:19:48Z
Steps To Reproduce
Check https://raw.githubusercontent.com/penpot/penpot/main/docker/images/docker-compose.yaml
Expected behavior
port of frontend should be 80 (not 8080) » at least for me it didn't work with 8080
Actual behavior
port 8080 on frontend not working

Duplicate issue #5502: bug: docker 
Created: 2024-12-30T01:44:05Z
Steps To Reproduce
I used the 2 commands to install Penbot using docker compose
curl -o docker-compose.yaml https://raw.githubusercontent.com/penpot/penpot/main/docker/images/docker-compose.yaml docker compose -p penpot -f docker-compose.yaml up -d
On this specific VM, i can access portainer but Penpot return no response.
I ssh into the VM and ran a: wget localhost:9001 and also no response.
I check every Penpot container logs in Portainers and no error. Everything seems to run just fine (see screenshot)
I can access MailCatcher over the port 1080
Note: i used many containers on this specific VM successfully. So it really seems a problem from Penbot
Expected behavior
Being able to access penpot frontend at 9001
Actual behavior
Nothing happen. I can't access the frontend at 9001
Screenshots or video

Desktop (please complete the following information)
Ubuntu
Smartphone (please complete the following information)
No response
Environment (please complete the following information)
No response
Frontend Stack Trace
No response
Backend Stack Trace
No response
Additional context
No response

Closing comment (2024-12-30T15:28:18Z): This is a duplicate of #5430. The latest version of the docker-compose.yml in the repo was updated to facilitate the port change necessary for 2.4.0, but the latest docker image is still 2.3.3, which uses port 80 instead of port 8080.
Edit your docker-compose.yml file and change the place where it says 8080 to 80:
penpot-frontend:
    image: "penpotapp/frontend:latest"
    restart: always
    ports:
-        - 9001:8080
+        - 9001:80
Re-deploy and your penpot instance should be up and running. However when 2.4.0 is finally released you will have to change the compose file back to 8080
Repository: penpot/penpot

Issue #80: Grid is disabled when pages are changed.
Created: 2017-03-09T10:04:45Z

Duplicate issue #79: Magnet is checked, but not enabled when grid is off.
Created: 2017-03-09T09:54:37Z
Grid is off in the image below, but the magnet is checked. If I move objects when grid is off, it does not snap to grid.

There are three solutions:

snap to grid even when grid is off.
dim and disable magnet (and other grid settings) when grid is off.
dim and disable grid settings, on click of grid settings, undim, enable and edit settings and show grid.

Option 3 is the best UX and most work :D. This would require some thought as to how to show that the settings are disabled. The text is so dim already, another visual indicator is required.
As an aside, the "Magnet option" would be better named "Snap", with the checkbox labelled "Snap to grid".

Closing comment (2017-03-21T22:15:11Z): If the "Activate magnet" checkbox is checked, it should mean that objects will snap to the grid even if the grid is invisible. Therefore, if objects do not snap to grid when the grid is invisible, then the "Activate magnet" checkbox should have a different state, eg unchecked or dimmed.
If you can accept the above logic, then my three proposals above should make sense. This issue is partly related to #80, since I do not think using a grid as a flag to indicate workspace is sensible. Surely the page name is what indicates workspace?!? I do not understand why grid is related to workspace. Maybe (more) usability testing is required?
Here are all possible combinations:
Repository: pftf/RPi4

Issue #157: Unable to boot from USB - xhci_hcd deregistered - Kernel 5.12.0+
Created: 2021-06-16T19:51:10Z
Hello,
I am having a issue with my RPI 4B 8GB.
EFI on SD CARD and system on SSD connected via USB.
I have been using Fedora Server from version 33. Now I have latest version 34 and it was working as expected.
Configured devicetree in EFI, 8GB enabled. Kernel was 5.11.x. System booted and I could see /dev/i2c-1 which I used a lot.
Now after upgrading kernel to 5.12.x and having configured  device tree in EFI it gets stuck on deregistering all USBs.
I am unable to boot from my external SSD nor use keyboard. Does anyone have same problem as me with latest kernels?
Is there any workaround for this?
I tried to boot with ACPI configured in EFI and I was able to get to the system, but I am not able to detect any i2c bus which I need.
Could anyone please point me what can be done?
thanks.

Duplicate issue #174: Version 1.29 No longer boots raspberrypi kernel, only boots upstream kernel
Created: 2021-08-24T20:28:02Z
Hello, I upgraded today to 1.29 and when trying to boot a manually compiled kernel from https://github.com/raspberrypi/linux I am greeted by this message:

However the standard upstream kernel provided by fedora boots just fine. Also previous versions of the firmware including 1.28 boots the compiled kernels just fine.

Closing comment (2021-08-26T15:44:32Z): This is possibly duplicate of #157

It might be related but in my case v1.29 fails to boot kernel 5.10.60 which might not contain these XHCI changes or whatever is causing this.
While trimming down the fedora kernel, after changing some USB flags I did indeed run into this, so yes the problem is probably the same.
Repository: pftf/RPi4

Issue #6: Writeable UEFI variables using runtime services (during OS lifetime)
Created: 2020-03-01T20:26:46Z
Because the PI has no dedicated chip that could be used for NVRAM, the current variables support relies on modifying RPI_EFI.FD in place. This of course only works before UEFI transitions to the OS, because the the SD controller is exposed via ACPI and subsequently owned by the OS.
Several approaches here to evaluate at some point
Approach 1
The easiest would be to add a boot option that would keep the SD controller as entirely owned by firmware (i.e. removed from ACPI and DT). Then, the runtime support for variable services could be modified to work in runtime, but it would be messy (today the support involves the SD controller, MmcDxe, block driver, fs layer and FAT driver).
Approach 2
Support an optional hat/dongle with another device (SD card?) over SPI pins. Since we can't expect this to always exist, the variable services would have to be rewritten to support both the fall back (current approach) or the SPI-attached storage. Also, the backing SPI controller would still need to be hidden from OS at boot.
Oh and of course none of these methods can support secure var storage.

Duplicate issue #158: systemctl reboot --firmware-setup doesn't work
Created: 2021-06-23T03:27:40Z
The subject is somewhat self-explanatory, although come to think about it, I'm not sure I've ever tried this on a arm64 before. The grub setup option does work, so its likely something to do with the uefi variables misbehaving again.

Closing comment (2021-12-03T05:23:54Z): Definitely a variable store bug, as it works now. Closing as a dupe of #6
Repository: pftf/RPi4

Issue #151: Change default boot order when no SD card is used
Created: 2021-05-19T19:00:30Z
When you use a SD card, you can change the boot order and have it saved to RPI_EFI.fd. However when you are not using an SD card there is no way to "presist" this change.
Theoretically Actually, you can plug in a SD card, make the change, and then copy the RPI_EFI.fd back to your tfpt server. However, this means that the RPI_EFI.fd will only work for that host and is no longer universal as things like MAC Address are different which makes the PXE boot fail on a diff host if you happened to have put this as first in the order.
So my question then is, as the "build in" default is SD card, is there a way to make the build-in default something else, like PXE/HTTP boot?  Or instead of rebooting if there is nothing to boot on the SD card to move to the next item in the order? Which in this case is PXE.
This might be slightly related to #136 I'm not sure. As my goal is to essentially:

EEPROM PXE boot RPi4
Use PRi4 to PXE iPXE
Use iPXE to boot my OS

Step 2 is where I get stuck/need human intervention unless I go the tedious route of saving unique  RPI_EFI.fd for each host.

Duplicate issue #131: Persistent UEFI settings across reboots while netbooting on RPI4
Created: 2021-02-18T02:22:46Z
Not too sure if this has been covered here.
I have a netboot infrastructure with a mix of iPXE and DNSMASQ.
The RPI4 boots fine, but needs to be configured to boot off of the UEFI IPv4 after every reboot.
Further, none of the UEFI settings are kept between reboots.
This RPI4 does not have an SD card inserted while booting.

Closing comment (2021-05-20T15:11:02Z): Ah similar to #151
Repository: pftf/RPi4

Issue #144: Modified .fd file results in failed Windows ARM booting via boot order
Created: 2021-04-10T15:51:05Z
I use grub2 to dual boot linux and Windows ARM on a RPi4 with a USB SSD on a powered hub.
If I use the default RPI_EFI.fd, booting works as expected for both Linux and Windows ARM.
However, if I use Setup to change either the 3GB Limit to Disabled, or set ACPI + Devicetree and Save and Reset, and then allow the UEFI to find the boot device via the boot order, Windows 10 ARM will fail to boot:
error: not a valid root device.
Below is the snippit from my grub.cfg file:
menuentry "Windows 10 ARM" { 
         echo "Windows 10 ARM booting..."
          insmod part_gpt
          insmod fat
          insmod chain
          set root=(hd0,gpt1)
          chainloader (hd0,gpt1)/EFI/Microsoft/Boot/bootmgfw.efi
}
If I restore the RPI_EFI.fd file, booting works again.
Or if I enter Setup, and use the Boot Manager to select UEFI USB device 2,
it always works.
RPi4_UEFI_Firmware_v1.25

Duplicate issue #117: Path chosen to execute UEFI shell impact the map
Created: 2020-11-30T18:34:07Z
Upon booting the UEFI from USB, the path used to launch the UEFI Shell impact the map.
At the splash screen

F1 (shell) -> the map is not complete
ESC -> Boot Manager -> UEFI Shell -> the map is correct

based on Raspberry Pi 4 8GB, UEFI Firmware v1.21

Closing comment (2021-04-12T21:17:55Z): This may be related to #144
A patch has been sent to EDK2 (not merged yet). Please try and confirm if it fixes the issue
Repository: pftf/RPi4

Issue #235: coreos install fails using v1.35 with 'synchronous exception at 0x000000003384D000'
Created: 2023-06-18T20:46:02Z
Hi, when using v1.35 and following instructions at https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-raspberry-pi4/#_edk2_combined_disk_mode_alternate_machine_disk_preparation the firmware boots, but then stops at the point of booting the os, with an error - synchronous exception at 0x000000003384D000.
If I use v1.34 no problem at all.
This is on a coreos install on a Raspberry Pi 4B 8Gb.  I tried several different microsd cards, and several different ignition files, but always with the same issue.  I am guessing there is a problem with the firmware addressing the bootloader incorrectly.

Duplicate issue #246: Error Synchronous Exception at 0x000000033A42000
Created: 2023-10-15T05:06:49Z
I am trying to build release of this repository.
Here are my steps to build
# Download code
git clone https://github.com/pftf/RPi4.git --depth=1
cd RPi4/
git submodule update --init --depth=1

cd ../edk2
git submodule update --init --depth=1
git apply ../0001-MdeModulePkg-UefiBootManagerLib-Signal-ReadyToBoot-o.patch

cd ../edk2-platforms/
git submodule update --init --depth=1
git apply ../0002-Check-for-Boot-Discovery-Policy-change.patch

cd ../

# Change My logo
cp MyLogo.bmp ./edk2-non-osi/Platform/RaspberryPi/Drivers/LogoDxe/Logo.bmp
cp MyLogo.eps ./edk2-non-osi/Platform/RaspberryPi/Drivers/LogoDxe/Logo.eps

# Set Variables
export WORKSPACE=$PWD
export PACKAGES_PATH=$PWD/edk2:$PWD/edk2-platforms:$PWD/edk2-non-osi
export GCC5_AARCH64_PREFIX=aarch64-linux-gnu-
export NUM_CPUS=$((`getconf _NPROCESSORS_ONLN`))

# Run setup commands
. edk2/edksetup.sh
make -C edk2/BaseTools

# Set PLATFORM_VERSION
sed -i 's/PLATFORM_VERSION               = 1.0/PLATFORM_VERSION               = 1.34/g' ./edk2-platforms/Platform/RaspberryPi/RPi4/RPi4.dsc

# Build command
build -n $NUM_CPUS -a AARCH64 -t GCC5 -p ./edk2-platforms/Platform/RaspberryPi/RPi4/RPi4.dsc -b RELEASE

# Download release for missing files i.e bcm2711-rpi-4-b.dtb, bcm2711-rpi-400.dtb, bcm2711-rpi-cm4.dtb
wget https://github.com/pftf/RPi4/releases/download/v1.35/RPi4_UEFI_Firmware_v1.35.zip
mkdir RPi4_UEFI_Firmware_v1
unzip ./RPi4_UEFI_Firmware_v1.35.zip -d RPi4_UEFI_Firmware_v1

# Build Final Release
mkdir Release
cp -r ./RPi4_UEFI_Firmware_v1/* ./Release
cp ./Build/RPi4/RELEASE_GCC5/FV/RPI_EFI.fd ./Release

When I boot using this release I am getting this error
Synchronous Exception at 0x000000033A42000
What am I doing wrong ?

Closing comment (2023-11-14T07:16:55Z): Closed because of duplicate of #235
Repository: pftf/RPi4

Issue #37: Improve Arasan driver to fail gracefully when no card is present
Created: 2020-04-16T15:23:16Z
Booting UEFI from USB or network still requires an SD card, because the Arasan driver will loop forever on I/O errors. Unfortunately the Pi Foundation didn't wire up the card detect pin so we have to do something more creative.

Duplicate issue #77: RPi4, USB-MSB context, no microsd card: What is the intent? FYI: What v1.16 does.
Created: 2020-06-23T22:41:40Z
USB-MSB for the RPi4 is now in stable instead of beta. Just to see what the status was for attempting its use I tried setting up for booting without a microsd card. v1.16 hung-up. Using a debug RPI_EFI.fd showed:
UEFI firmware (version UEFI Firmware v1.16 (DEBUG) built at 12:15:58 on Jun 18 2020)
. . . (omitted) . . .
add-symbol-file /home/appveyor/projects/rpi4/Build/RPi4/DEBUG_GCC5/AARCH64/Platform/RaspberryPi/Drivers/ArasanMmcHostDxe/ArasanMmcHostDxe/DEBUG/ArasanMMCHost.dll 0x36D39000
Loading driver at 0x00036D38000 EntryPoint=0x00036D3B6AC ArasanMMCHost.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 35F3BB18
ProtectUefiImageCommon - 0x35F3B2C0
  - 0x0000000036D38000 - 0x0000000000007000
SetUefiImageMemoryAttributes - 0x0000000036D38000 - 0x0000000000001000 (0x0000000000004008)
SetUefiImageMemoryAttributes - 0x0000000036D39000 - 0x0000000000004000 (0x0000000000020008)
SetUefiImageMemoryAttributes - 0x0000000036D3D000 - 0x0000000000002000 (0x0000000000004008)
InstallProtocolInterface: 3E591C00-9E4A-11DF-9244-0002A5F5F51B 36D3D030
InstallProtocolInterface: 964E5B21-6459-11D2-8E39-00A0C969723B 35F2DBC8
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 35F2DD98
MMCSendCommand(371): MMC_CMD1 ERRI MmcStatus 0x18040
MMCSendCommand(371): MMC_CMD8 ERRI MmcStatus 0x18040
Not a SD2.0 Card
MMCSendCommand(371): MMC_CMD55 ERRI MmcStatus 0x18040
Card should be MMC
MMCSendCommand(371): MMC_CMD1 ERRI MmcStatus 0x18040
MMCSendCommand(371): MMC_CMD55 ERRI MmcStatus 0x18040
Card should be MMC
MMCSendCommand(371): MMC_CMD1 ERRI MmcStatus 0x18040
MMCSendCommand(371): MMC_CMD55 ERRI MmcStatus 0x18040
. . . (omitted) . . .

The last 3 shown lines repeated, without bound? Release was silent about the problem but I expect was stuck looping the same way, just without the messages.
This was a 4 GiByte RPi4 v1.1 for the test context.

Closing comment (2020-06-23T22:45:20Z): Duplicate of #37. This issue is tracked there. We can't provide an ETA. as to when we are going to address it.
Closing this as duplicate.
Repository: pftf/RPi4

Issue #211: How to modify boot screen？
Created: 2022-03-12T04:15:22Z
Hello, I want to ask a question, how to modify the boot screen? I want to change the boot screen, but I don't know how to change it. Can you tell me how to change it?

Duplicate issue #233: Customize Splash Image
Created: 2023-05-28T11:47:29Z
Is there any way to customize splash screen image which is coming in the beginning ?

Closing comment (2023-05-28T13:26:20Z): Duplicate of #211
Repository: pftf/RPi4

Issue #105: RPi 4B firmware misreports SoC model GPIO MMIO space
Created: 2020-10-29T17:02:34Z
While working on a native GPIO driver for ESXi, I noticed that the vmkernel misreports the size of the GPIO MMIO space for the BCM2711 SoC.
I've talked to the ESXi on Arm folks and they believe it's a firmware bug.
I've tested this on two different Raspberry Pi 4Bs, and the MMIO space is reported as being 180 bytes in size on both. This size corresponds to the BCM2835 (an older chip). The BCM2711 has an MMIO space of 244 bytes, to make room for the pull-up/pull-down config registers.
References:

BCM2835: p. 91 in https://www.raspberrypi.org/documentation/hardware/raspberrypi/bcm2835/BCM2835-ARM-Peripherals.pdf
BCM2711: p. 65 in https://datasheets.raspberrypi.org/bcm2711/bcm2711-peripherals.pdf

Duplicate issue #90: VIOMMU & ACPI DMAR Table (virtual address translation)
Created: 2020-08-01T04:29:08Z
There are many issues being caused by the lack of virtual addressing.
This issues specifically involve I/O memory mapping for GPIO/Ethernet etc. and also System memory mapping for Virtualisation.
This is usually the responsibility of a Direct Memory Access Controller (DMA), usually found on the motherboard as an FPGA.
The Pi4 has no such IOMMU (Input/Output Memory Management Unit).
I propose something called a VIOMMU to be implemented in Raspberry Pi Firmware.
As the name suggests, it is a Virtual Input/Output Memory Management System for the Pi4 Address Space.
When for example Windows 64-bit calls MmMapIoSpace, the firmware would be responsible for allocating a section of
system memory which is directly linked to the I/O memory of the ARM SoC. This could either be a hard link or a soft link.
The system should aim to be either Bit-Agnostic or 64-bit if necessary. Issues with dual 32-bit accesses should be resolved by the use of this VIOMMU unit which sits between the hardware and the operating system to link and translate addresses.
The Operating System can be presented with a DMAR table from the ACPI specification.
This table is already used to make technologies such as Intel-VT-d and AMD-V functional.
It would be good to see an ARM equivalent, especially since the Cortex A72 has hardware virtualisation support.
Any corrections or additional thoughts are welcome.
Alastair Cota - Embedded Firmware Developer

Closing comment (2020-11-25T16:44:29Z): Possibly related to #105 ?
Repository: pftf/RPi4

Issue #6: Writeable UEFI variables using runtime services (during OS lifetime)
Created: 2020-03-01T20:26:46Z
Because the PI has no dedicated chip that could be used for NVRAM, the current variables support relies on modifying RPI_EFI.FD in place. This of course only works before UEFI transitions to the OS, because the the SD controller is exposed via ACPI and subsequently owned by the OS.
Several approaches here to evaluate at some point
Approach 1
The easiest would be to add a boot option that would keep the SD controller as entirely owned by firmware (i.e. removed from ACPI and DT). Then, the runtime support for variable services could be modified to work in runtime, but it would be messy (today the support involves the SD controller, MmcDxe, block driver, fs layer and FAT driver).
Approach 2
Support an optional hat/dongle with another device (SD card?) over SPI pins. Since we can't expect this to always exist, the variable services would have to be rewritten to support both the fall back (current approach) or the SPI-attached storage. Also, the backing SPI controller would still need to be hidden from OS at boot.
Oh and of course none of these methods can support secure var storage.

Duplicate issue #102: Provide some way to set/preserve variables directly on SD card
Created: 2020-10-01T21:32:06Z
I normally run my pis without a console attached, and only attach a serial console for debugging and setup. Unfortunately, that's the only way to modify firmware variables now, which means I have to do it every time I replace with a newer firmware. Either a tool to set the variables in the firmware image from Linux or a way to copy variables from one version to another, would let me do in place upgrades much more easily.

Closing comment (2020-11-20T03:12:21Z): Appears to be related to: #6
Repository: phoenixframework/phoenix

Issue #1473: PubSub.subscribe should not dup subscription
Created: 2016-01-17T19:55:14Z

Duplicate issue #1474: clarify PubSub semantics around a pid joining a topic multiple times
Created: 2016-01-17T20:05:09Z
It looks like the behavior at present is that a pid can subscribe to a pubsub topic multiple times, and will receive multiple broadcasts if it does so, and unsubscribing will remove all subscriptions to the topic for that pid.
https://gist.github.com/adamkittelson/60919b8bb70651f1ca7d
I brought it up in irc and Jose asked me to open an issue so you can nail down the semantics you want and test them to avoid changes having them change unexpectedly in a future refactoring.

Closing comment (2016-01-19T13:11:18Z): dup of #1473
Repository: phoenixframework/phoenix

Issue #4720: SSL 
Created: 2022-03-14T23:17:49Z
https://www.phoenixframework.org/ is throwing an SSL connection error. Tested on Firefox, Chrome, and Safari. I'm not sure where else to flag this due to not having access to the site so I figured this might be a good place...
Specifically, I'm shown this on Firefox:
Secure Connection Failed

An error occurred during a connection to www.phoenixframework.org. Peer received a valid certificate, but access was denied.

Error code: SSL_ERROR_ACCESS_DENIED_ALERT

The dev tools reveal nothing, this is the most descriptive thing I could find. I'll also attach a screenshot.

Duplicate issue #4724: Website Down
Created: 2022-03-15T16:05:08Z
You probably know this, but it appears that your website is down. Just a heads up. http://www.phoenixframework.org

Closing comment (2022-03-15T16:08:09Z): Duplicate of #4720
Repository: phoenixframework/phoenix

Issue #1085: Better error message when rendering `Ecto.Association.NotLoaded`
Created: 2015-08-03T18:32:45Z
I was working with some views in Phoenix 0.14.0 and I called render_one(post.comments, "index.son")
I got an error along the lines of MyApp.NotLoadedView module does not exist. I was not sure why it was trying to call that view when I passed in comments and later realize it was because I did not preload the comments association.
I think it would be nice if it raised a helpful error message when you passed an Ecto.Association.NotLoaded as the model to render_one or render_many. I can tackle this on Friday if this is something that you think would be helpful.
post = Repo.one(Post)
render_one(post.comments, "index.json")
# I believe it should raise something like:
# "You tried to render Ecto.Association.NotLoaded. 
# This probably means you forgot to preload the record. Try using Repo.preload"
post = post |> Repo.preload(:comments)
render_one(post.comments, "index.json")
# Works as expected

Duplicate issue #1084: Better error message when rendering `Ecto.Association.NotLoaded`
Created: 2015-08-03T18:32:08Z
I was working with some views in Phoenix 0.14.0 and I called render_one(post.comments, "index.son")
I got an error along the lines of MyApp.NotLoadedView module does not exist. I was not sure why it was trying to call that view when I passed in comments and later realize it was because I did not preload the comments association.
I think it would be nice if it raised a helpful error message when you passed an Ecto.Association.NotLoaded as the model to render_one or render_many. I can tackle this on Friday if this is something that you think would be helpful.
post = Repo.one(Post)
render_one(post.comments, "index.json")
# "You tried to render Ecto.Association.NotLoaded. 
# This probably means you forgot to preload the record. Try using Repo.preload"
post = post |> Repo.preload(:comments)
render_one(post.comments, "index.json")
# "Works as expected"

Closing comment (2015-08-03T18:33:04Z): Duplicate of #1085
Repository: phoenixframework/phoenix

Issue #849: Update phoenix_live_reload to new channel client
Created: 2015-05-07T02:59:10Z

Duplicate issue #858: Live Reload is broken on master
Created: 2015-05-10T06:03:20Z
Uncaught TypeError: socket.join is not a function

Closing comment (2015-05-10T06:24:59Z): Dup of #849.
Repository: phoenixframework/phoenix

Issue #2015: Allow configuration to be passed on Endpoint.start_link and deprecate {:system, ...}
Created: 2016-11-30T13:48:38Z

Duplicate issue #1906: Remove force_ssl option
Created: 2016-09-09T17:03:50Z
Instead of a configuration option, we can tell users to plug the SSL plug directly AND pass the force_ssl option to sockets. This removes unnecessary lines of code from Phoenix while making it more apparent for users how to customize their app to their needs. We should generate 3 LOC commented out on the endpoint with relevant examples.
The only downside that comes to mind from this approach is that we lose the per environment configuration. So users will need to rely on checks such as if Mix.env == :prod in their endpoint module body.
Thoughts?

Closing comment (2016-12-01T09:10:23Z): This is also related to #2015 since force_ssl has dynamic configuration.
Repository: phoenixframework/phoenix

Issue #2687: Don't swallow exceptions when they are translated with Plug.Exception protocol
Created: 2017-12-20T20:08:27Z
Environment

Elixir version (elixir -v): 1.5.2
Phoenix version (mix deps): 1.3.0
Operating system: macOS

Actual behavior
In production, when running with debug_errors: false when one of the errors that implement the Plug. Exception protocol is raised, nothing is logged - only the status code is changed.
Unfortunately that means we're throwing away a lot of information that could be helpful for the programmer when trying to debug production issues.
For example, in couple places we use Repo.insert! when data inserted doesn't come from the user (so there's no point in rendering errors from the changeset). The result is that in the logs we can only see a sudden rollback query and that Send 422 in Xms. Basically nothing to go on (tracing is a god-send).
Expected behavior
There should be at least some trace of the exception in the logs. I agree, it's sensible not to log it with error level (since in many cases exceptions like that are used for normal application operation, however unfortunate I think that might be). But I think logging with warn or at least debug should always occur. If not by default, there should at least be a way to configure it.

Duplicate issue #2484: scrub_params on :new action, causes phoenix to throw 400 without error message
Created: 2017-09-08T21:31:12Z
Environment

Elixir  1.5.1:
Phoenix 1.2.4:
Operating system: macOS 10.12.6

So today I was silly and instead of doing plug :scrub_params, "report" when action in [:create] in the controller I did plug :scrub_params, "report". Which caused the server to throw a 400 error without any error messages, when going to the new report path. Just [info] Sent 400 in 2ms
I was wondering if this would be a good opportunity to improve error messages. I was able to figure it out eventually but I was very confused and getting frustrated. I could see this being a place a newbie might get tripped up.

Closing comment (2018-02-12T20:25:51Z): Duplicate of #2687.