authinfo incompatibility with saspy module
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 停滞
- 技术栈
- python
调研方向
从 utils/authinfo.py:191 开始，检查解析器如何拆分 .authinfo 记录。使用报告中所示的命名条目 IOM_Linux_SASGrid 和 default 重现该问题，然后验证命名配置不再破坏解析，并且能够正确选择 default 记录。
由索引模型根据 Issue 内容生成。
描述
I'm using both saspy [for sas_kernel/jupyter as well as some of our 9.4 systems and SAS Grid], as well as SWAT for working directly with CAS. I spent quite a while trying to debug a connection issue with SWAT that turned out to be due to how my .authinfo was written.
What I had originally looked like this:
IOM_Linux_SASGrid user not_my_real_user password not_my_real_password
default user not_my_real_user password not_my_real_password
SWAT kept having authentication problems, because the syntax with the named config line doesn't work with the parser process in utils/authinfo.py:191 , where it splits on "host|machine|default".
The SASPy documentation is here: https://sassoftware.github.io/saspy/configuration.html#iom , this is the line about "authkey" that's specced thus, that is the line causing the problem:
authkey user omr_user_id password omr_user_password
My workaround was to flip the lines:
default user not_my_real_user password not_my_real_password
IOM_Linux_SASGrid user not_my_real_user password not_my_real_password
And now the "default" one is correctly picked up, [and the rest of the "defs" variable is nonsensical from the perspective of the rest of the parsing code, but it doesn't matter because it doesn't play because default already got returned]
Because the named configs don't make sense with SWAT's configuration, I would suggest the shortest fix that is to split on line breaks first, then split the rest, the way you do now. That way, named configs will be functionally ignored but won't break subsequent records.
- 主要语言
- Python
- 星标
- 159
- 派生
- 66
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
sassoftware/python-swat 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 30/100
sassoftware/python-swat#191 · 1 条评论 ·
-
难度 3/5 1-2 天 新手友好度 35/100
sassoftware/python-swat#183 · 1 条评论 ·
-
难度 4/5 3-5 天 新手友好度 25/100
sassoftware/python-swat#180 ·
-
难度 4/5 3-5 天 新手友好度 25/100
sassoftware/python-swat#177 · 1 条评论 ·
-
难度 3/5 1-2 天 新手友好度 35/100
sassoftware/python-swat#175 · 1 条评论 ·
查看 sassoftware/python-swat 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 64/100
its-me-prash/vwgroup-connect-ha#2019 ·
维护者通常 1 天内回复
-
bug good first issue
难度 2/5 1-3 小时 新手友好度 86/100
KonstantinStarovoytov/kitden#21 ·
维护者通常 1 天内回复
-
Refactor未关闭
难度 2/5 1-3 小时 新手友好度 62/100
ehmatthes/gh-profiler#166 ·
-
难度 2/5 1-3 小时 新手友好度 68/100
smart-on-fhir/smart-fetch#73 ·
-
good first issue help wanted
难度 1/5 1-3 小时 新手友好度 85/100
RizgarOzan/playcal#13 ·