Availability and use terms for minimized HTTP traces linked to recorded agent configurations
還沒有人認領這個 Issue。
評估
研究方向
The issue names no files, tests, or entry points. First establish whether the published dataset retains HTTP request records separately from browser actions, DOM observations, and screenshots, then check the documented reuse terms or identify a public custodian contact. Done means providing a documentation or availability/use-terms answer, including whether records were not retained; do not attach run data.
由索引模型根據 Issue 內容生成。
描述
Hello, I am investigating whether actual website-visible HTTP request sequences
can support an offline comparison between recorded browser-agent configurations.
This is an availability question, not a request to run experiments or disclose
private data.
For the published agentlabtraces/agentlabtraces dataset, were actual network
request records retained separately from browser actions, DOM observations and
screenshots? If so, is there an existing, documented-use export or a public
custodian contact for a minimized, non-executable JSON/CSV projection?
A useful projection would separate: (1) same-property HTTP method and sanitized
route category, observation order and capture location; (2) independently saved
invocation/configuration records; and (3) explicit linkage between those records
for evaluation grouping. We would also need the attempted/captured-run accounting,
cache and capture-loss semantics, source/runtime versions, clock semantics if
timing is present, and applicable reuse/retention terms. Labels and run identifiers
would be evaluation-only, not predictor inputs.
We are not requesting cookies, authentication material, raw headers, request or
response bodies, raw URLs/query strings, personal data, screenshots, DOM text,
model reasoning or private traces. Please do not attach run data to this issue;
documentation or an availability/use-terms answer is sufficient. If HTTP records
were not retained, that answer is useful too. Thank you.
- 主要語言
- Python
- 星號
- 644
- 分支
- 134
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
ServiceNow/AgentLab 的其他 Issue
-
難度 4/5 3-5 天 新手友好度 48/100
ServiceNow/AgentLab#340 ·
-
難度 4/5 3-5 天 新手友好度 22/100
ServiceNow/AgentLab#331 ·
-
難度 4/5 3-5 天 新手友好度 15/100
ServiceNow/AgentLab#329 ·
-
難度 3/5 1-2 天 新手友好度 25/100
ServiceNow/AgentLab#324 · 2 個 reaction ·
-
難度 4/5 3-5 天 新手友好度 18/100
ServiceNow/AgentLab#323 ·
查看 ServiceNow/AgentLab 的全部 Issue
相似的 Issue
-
Context/namespace resources fail in-cluster: "Invalid kube-config file. No configuration found."未關閉
難度 2/5 1-3 小時 新手友好度 76/100
-
bug documentation
難度 1/5 1 小時以內 新手友好度 88/100
awslabs/visual-asset-management-system#880 ·
維護者通常 1 天內回覆
-
netbox status: needs owner type: documentation
難度 2/5 1-3 小時 新手友好度 74/100
netbox-community/netbox#23533 ·
維護者通常 1 天內回覆
-
app: scripts status: backlog type: documentation
難度 2/5 1-3 小時 新手友好度 86/100
netbox-community/netbox-scripts#68 ·
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 91/100
marin-community/marin#10765 ·
維護者通常 1 天內回覆