authinfo incompatibility with saspy module

未關閉
#178 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 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 範本
  • 閱讀貢獻指南

從這裡開始

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

sassoftware/python-swat 的其他 Issue

查看 sassoftware/python-swat 的全部 Issue

相似的 Issue

更多 Python Issue

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

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