Hacktoberfest 2026：維護者為十月標記出來的 issue，仍然開放、適合新手。 瀏覽 Hacktoberfest issue

sh script not running

未關閉
  • 哪裡不對？
#367 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 5 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
30/100
Issue 類型
缺陷
描述清晰度
需要釐清
活躍度
停滯
技術堆疊
shell
領域
build-system

研究方向

從 build_and_run.sh 開始，檢查 ./build_and_run.sh 執行的 OpenSSL 憑證產生命令；在日誌所示的環境中重現該失敗，包括 OpenSSL 錯誤中的 Git 路徑。完成的標準是指令碼在沒有 CSR 錯誤或檔案讀取錯誤的情況下執行完畢，並產生預期的憑證檔案。

由索引模型根據 Issue 內容生成。

描述

ℹ️ Please note that the best way to get support for Real Python courses & articles is to join one of our weekly Office Hours calls or in the RP Community Slack.

You can report issues and problems here, but we typically won't be able to provide 1:1 support outside the channels listed above.

Describe the bug
$ ./build_and_run.sh
Generating a RSA private key
................................................................................
..........................................++++
................................................................................
.................++++
writing new private key to 'ca.key'

name is expected to be in the format /type0=value0/type1=value1/type2=... where
characters may be escaped by . This name is not in that format: 'C:/Program Fil
es/Git/O=me'
problems making Certificate Request
Generating a RSA private key
....................................................................++++
................................................................................
..........++++
writing new private key to 'client.key'

name is expected to be in the format /type0=value0/type1=value1/type2=... where
characters may be escaped by . This name is not in that format: 'C:/Program Fil
es/Git/CN=marketplace'
problems making Certificate Request
Generating a RSA private key
..........................................................++++
................................................................................
..............................................++++
writing new private key to 'server.key'

name is expected to be in the format /type0=value0/type1=value1/type2=... where
characters may be escaped by . This name is not in that format: 'C:/Program Fil
es/Git/CN=recommendations'
problems making Certificate Request
Can't open client.csr for reading, No such file or directory
19404:error:02001002:system library:fopen:No such file or directory:../openssl-1.1.1s/crypto/bio/bss_file.c:69:fopen('client.csr','r')
19404:error:2006D080:BIO routines:BIO_new_file:no such file:../openssl-1.1.1s/crypto/bio/bss_file.c:76:
Can't open server.csr for reading, No such file or directory
19660:error:02001002:system library:fopen:No such file or directory:../openssl-1.1.1s/crypto/bio/bss_file.c:69:fopen('server.csr','r')
19660:error:2006D080:BIO routines:BIO_new_file:no such file:../openssl-1.1.1s/crypto/bio/bss_file.c:76:

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
image

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

主要語言
Jupyter Notebook
星號
5.2k
分支
5.3k
平均合併
5 天 4 小時
30 天內合併 PR
15

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 有 Pull Request 範本
  • 沒有貢獻指南

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

realpython/materials 的其他 Issue

查看 realpython/materials 的全部 Issue

相似的 Issue

更多 Build System Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。