opm upload with github_account as an organization results in 500 error
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 485
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
Attempting to upload a new package where the github_account is set to an organization produces a 500 error. When changed to my personal user account, the upload is successful. This was attempted using the latest openresty/openresty:alpine-fat image.
bash-5.1# opm upload
found license: BSD 2-Clause "Simplified" or "FreeBSD" license.
Package lua-resty-iputils-0.3.0 already installed.
Package lua-resty-string-0.11 already installed.
lua-resty-digitalelement-0.1.0/
lua-resty-digitalelement-0.1.0/README.md
lua-resty-digitalelement-0.1.0/dist.ini
lua-resty-digitalelement-0.1.0/lib/
lua-resty-digitalelement-0.1.0/lib/resty/
lua-resty-digitalelement-0.1.0/lib/resty/digitalelement.lua
HTTP/2 500
date: Fri, 18 Mar 2022 01:44:19 GMT
content-type: text/html; charset=utf-8
content-length: 174
server: OpenResty Edge
req-id: 00000a0002b83f534f80eea6
<html>
<head><title>500 Internal Server Error</title></head>
<body>
<center><h1>500 Internal Server Error</h1></center>
<hr><center>openresty</center>
</body>
</html>
; .opmrc
github_account=revcontent
github_token=[redacted]
upload_server=https://opm.openresty.org
download_server=https://opm.openresty.org
; dist.ini
name = lua-resty-digitalelement
abstract = Query DigitalElement database files
version = 0.1.0
author = Richard Onyon (cebollia)
is_original = yes
license = 2bsd
lib_dir = lib
doc_dir = lib
repo_link = https://github.com/revcontent/lua-resty-digitalelement
main_module = lib/resty/digitalelement.lua
requires = luajit, openresty/lua-resty-string >= 0.11, hamishforbes/lua-resty-iputils >=0.3.0
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with the opm upload entry point and the .opmrc configuration using an organization account, then compare it with the successful personal-account upload. Use the dist.ini package metadata and upload-server response to trace the organization-account handling; done means organization-owned packages upload successfully without a 500 error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- api, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100