Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Could not evaluate: Working directory <virualenv> does not exist!

未关闭
#615 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
python, ruby
领域
devops

调研方向

Start in manifests/pip.pp, focusing on the exec resource and its $cwd evaluation during Puppet noop runs. Reproduce the virtualenv and pip resource scenario in noop mode, then verify that a new virtual environment produces no missing-working-directory error while normal mode still installs dependencies.

由索引模型根据 Issue 内容生成。

描述

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 2019.8
  • Ruby: 2.5.7-1
  • Distribution: ---
  • Module version: v6.1.0

How to reproduce (e.g Puppet code you use)

python::pyvenv { $_virtualenv:
  ensure   => 'present',
  version  => $pythonconfig::package_ensure,
  venv_dir => $_virtualenv,
}

python::pip { $pkgname:
  ensure       => $ensure,
  pkgname      => $pkgname,
  virtualenv   => $_virtualenv,
  pip_provider => 'pip3',
  require      => Python::Pyvenv[$_virtualenv]
}

python::pip { "certifi for venv ${_virtualenv}":
  ensure       => 'present',
  pkgname      => 'certifi',
  virtualenv   => $_virtualenv,
  pip_provider => 'pip3',
  require      => Python::Pip[$pkgname]
}

What are you seeing

Issue only occurs when running Puppet in noop mode.
The following error occurs:

Could not evaluate: Working directory <virtualenv> does not exist!

When running Puppet in normal mode the virtual environment is created and all dependencies are installed.

Looks like the evaluation on the $cwd parameter in the exec in https://github.com/voxpupuli/puppet-python/blob/master/manifests/pip.pp is not working as expected.

What behaviour did you expect instead

No error message and a successful noop run when deploying a new virtual environment.

Output log

Any additional information you'd like to impart

主要语言
Ruby
星标
196
派生
371
平均合并
5 小时 54 分钟
30 天内合并 PR
5

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

voxpupuli/puppet-python 的其他 Issue

查看 voxpupuli/puppet-python 的全部 Issue

相似的 Issue

更多 Ruby Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。