text:
= is considered as EQL in lexer when used within braces

What did you do?
I was working on developing Prettier for PromQL. While writing extensive unit tests, I came across this issue which was responsible for breaking the formatting at some places.
Issue
= should be considered as ASSIGN item by the lexer. This happens as expected until it is used inside label_matchers. When in label_matchers, it is treated as EQL. This leads to issues while formatting a PromQL expression.
Note: EQL should be ==.
Related code:

https://github.com/prometheus/prometheus/blob/f8c8adfd67b48709a4e57341c7cb6d7ebbdff061/promql/parser/lex_test.go#L231
https://github.com/prometheus/prometheus/blob/f8c8adfd67b48709a4e57341c7cb6d7ebbdff061/promql/parser/lex_test.go#L591

What did you expect to see?
Consider = as ASSIGN even when used inside label_matchers.
What did you see instead? Under which circumstances?
= is considered as EQL when used within label_matchers.

This sounds vestigial, from before recording rules were in YAML.

Will take up this.

Mmh this is not really correct, I think it is equal and not assign ?

You mean, in vector selectors, you use metric_name{label==value}? As far as I know, I don't think there's any such vector selector comparison. But yes, in terminology, we call that as equality.

I think this is a bug not a cleanup.

It is cleanup as there is no user impact.

Yeah, nothing is actually broken here. It's just something vestigial from Prometheus 1.x days that's still lying around.


text:
Prometheus crash with "unexpected fault address 0x7f16221ef000"

Environment

System information:
Linux 5.0.0-29-generic x86_64

Prometheus version:
version 2.15.2

* Logs:

unexpected fault address 0x7f16221ef000
fatal error: fault
[signal SIGBUS: bus error code=0x2 addr=0x7f16221ef000 pc=0x460388]
goroutine 1 [running]:
runtime.throw(0x24e01c1, 0x5)
/usr/local/go/src/runtime/panic.go:774 +0x72 fp=0xc0006cb3d8 sp=0xc0006cb3a8 pc=0x42f5d2
runtime.sigpanic()
/usr/local/go/src/runtime/signal_unix.go:391 +0x455 fp=0xc0006cb408 sp=0xc0006cb3d8 pc=0x444c85
runtime.memmove(0x7f16221ef000, 0x24dd696, 0x1)
/usr/local/go/src/runtime/memmove_amd64.s:146 +0x108 fp=0xc0006cb410 sp=0xc0006cb408 pc=0x460388
github.com/prometheus/prometheus/promql.NewActiveQueryTracker(0x7ffd72b9b18b, 0xb, 0x14, 0x2c66840, 0xc000771530, 0x2c66840)
/home/golang/src/github.com/prometheus/prometheus/promql/query_logger.go:118 +0x362 fp=0xc0006cb558 sp=0xc0006cb410 pc=0x1c84722
main.main()
/home/golang/src/github.com/prometheus/prometheus/cmd/prometheus/main.go:383 +0x538f fp=0xc0006cbf60 sp=0xc0006cb558 pc=0x1dd3eaf
runtime.main()
/usr/local/go/src/runtime/proc.go:203 +0x21e fp=0xc0006cbfe0 sp=0xc0006cbf60 pc=0x430f6e
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1357 +0x1 fp=0xc0006cbfe8 sp=0xc0006cbfe0 pc=0x45f0d1
goroutine 17 [syscall]:
os/signal.signal_recv(0x0)
/usr/local/go/src/runtime/sigqueue.go:147 +0x9c
os/signal.loop()
/usr/local/go/src/os/signal/signal_unix.go:23 +0x22
created by os/signal.init.0
/usr/local/go/src/os/signal/signal_unix.go:29 +0x41
goroutine 21 [select]:
go.opencensus.io/stats/view.(*worker).start(0xc00013edc0)
/home/golang/src/github.com/prometheus/prometheus/vendor/go.opencensus.io/stats/view/worker.go:154 +0x100
created by go.opencensus.io/stats/view.init.0
/home/golang/src/github.com/prometheus/prometheus/vendor/go.opencensus.io/stats/view/worker.go:32 +0x57
goroutine 102 [select]:
github.com/prometheus/prometheus/pkg/logging.(*Deduper).run(0xc00012d280)
/home/golang/src/github.com/prometheus/prometheus/pkg/logging/dedupe.go:74 +0x1f3
created by github.com/prometheus/prometheus/pkg/logging.Dedupe
/home/golang/src/github.com/prometheus/prometheus/pkg/logging/dedupe.go:60 +0xcf
goroutine 103 [chan receive]:
github.com/prometheus/prometheus/storage/remote.(*WriteStorage).run(0xc000122d20)
/home/golang/src/github.com/prometheus/prometheus/storage/remote/write.go:79 +0xc7
created by github.com/prometheus/prometheus/storage/remote.NewWriteStorage
/home/golang/src/github.com/prometheus/prometheus/storage/remote/write.go:72 +0x122

! also encountered the same problem, and finally found out that the disk was full
df -h
root@mgt08:~# df -h
Filesystem               Size  Used Avail Use% Mounted on
/dev/mapper/lma-monitor   20G   19G     0 100% /monitor

! also encountered the same problem, and finally found out that the disk was full
df -h
root@mgt08:~# df -h
Filesystem               Size  Used Avail Use% Mounted on
/dev/mapper/lma-monitor   20G   19G     0 100% /monitor

source: gharchive/issue

repo: prometheus/prometheus

license_type: permissive

license_source: github-api


text:
Changing TotalQueryableSamples from int to int64

Follow up of https://github.com/prometheus/prometheus/pull/10369
int can only count up to ~2B and for some very big query_ranges is possible have an overflow.
The stepStat  struct was already an int64 but some internal data structures and the totalQueryableSamples is using int.
https://github.com/prometheus/prometheus/blob/a236166c71b6eaae622d585f35f3f27459971c1c/util/stats/query_stats.go#L105-L109
https://github.com/prometheus/prometheus/blob/a236166c71b6eaae622d585f35f3f27459971c1c/util/stats/query_stats.go#L81-L84

I'm not sure why the checks are not passing.. seems not related at all with this change! :(

Thanks!

Thanks!!!  @roidelapluie

source: gharchive/pull-request

authors: alanprot roidelapluie


text:
bugfix: data race in head.Appender.AppendHistogram and Commit

Fixes: #15139
Two Appenders race when creating a series with a native histogram as the memSeries will be common and the lastHistogram field is written without lock.
Fix by:
Move writing memSeries lastHistogramValue and lastFloatHistogramValue
after series creation under lock.
The resulting code isn't totally correct in the sense that we're setting
these values before Commit() , so they might be overwritten/rolled back
later.
Also Append() of stale sample checks the values without lock, so there's
still a potential race.
The correct solution would be to set these only in Commit() which we
actually do, but then Commit() would also need to process samples in
order and not floats first, then histograms, then float histograms - which
leads to not knowing what stale marker to write for histograms.
Might be easier to do after : #15112

Ok

Leaving it open for you to merge 👍

Created issue #15177 to track the refactor.

authors: Benz1993com jesusvazquez krajorama


text:
fix word 'parmeters' to 'parameters'

make the comment more readable

Can you add the DCO please?

OK @brian-brazil

Thanks!

authors: AllenZMC brian-brazil


text:
declare variable from "var" to "make"

Which problem is this PR solving?

declare variable from "var" to "make"

Short description of the changes

Because we have knowed the slice's length. So we can avoid using 'append' to enlarge the extra memory.

@roidelapluie
Hello, my pr's reviewers are none. Could you please handle it or who?

I would say this kind of optimization is only required in (very) hot code paths. However, this is in a test, where the gain in efficiency is irrelevant, if noticeable at all.
The original code is idiomatic and readable. With your change, it's harder to read. (The make construct could mean many things, so the reader has it carefully: what is created? is it length or capacity I'm setting? The previously used append construct, while a bit verbose, is an extremely common and well known idiom.) It is also harder to maintain. (If the length ever changes, now two code locations have to be changed. If you change only one, you have created a bug.)
In short: I think this code should stay as is.

I would say this kind of optimization is only required in (very) hot code paths. However, this is in a test, where the gain in efficiency is irrelevant, if noticeable at all.
The original code is idiomatic and readable. With your change, it's harder to read. (The make construct could mean many things, so the reader has it carefully: what is created? is it length or capacity I'm setting? The previously used append construct, while a bit verbose, is an extremely common and well known idiom.) It is also harder to maintain. (If the length ever changes, now two code locations have to be changed. If you change only one, you have created a bug.)
In short: I think this code should stay as is.

I got it. Thanks for your answer.


text:
Summation ODE Trigger does not check if limit is reached

This issue should have been caught by a test case!

Merged into v0.15.alpha

license: MIT


text:
fix: trigger eval on config changes

Fixes #110

Thanks for being swift with the fixes!

authors: nwaughachukwuma typpo

repo: promptfoo/promptfoo-action


text:
Add option to turn off Nunjucks engine

Could we add an option to turn off Nunjucks templating? It's been messing me up 🙃
Usecase
I have a prompt that accepts fragments of file content - these files may be markdown files, code files, etc. I'm not using any Nunjucks templating - I'm constructing my prompts using JS files.
My problem is that the Nunjucks templating is causing issues - it's detecting all sorts of things in the files, which it thinks are opening tags (for example a line that contains {# .somevalue }), but because those aren't tags, it ends up throwing an exception and crashing the run.  It would be great to just have a flag to turn the templating off completely, for when it's not needed.
The only workaround I've found so far has been to just manually {% raw %} and {% endraw %} tags to the beginning and end of my example inputs, but this if very inconvenient and feels pretty silly to have to do.
You can imagine that even if it wasn't throwing errors, I'd want to be able to process files that do contain Jinja2 templates without Nunjucks trying to process the tables and messing everything up.
SIDE NOTE: what made this whole thing way worse is that when this templating exception is thrown, there is no simple way to know which test case is the one that's causing the issue - I had to manually run them one by one to find the offender. Might be nice if exceptions could have some info about the test case they happened in.

#405 adds an environment variable PROMPTFOO_DISABLE_TEMPLATING that should solve your immediate need :)

This is included in release 0.37.0

authors: nimrodolev typpo

repo: promptfoo/promptfoo


text:
Symfony2 has removed Propel bridge from Symfony Core.

Symfony2 has removed Propel bridge from Symfony Core. So your install instructions no longer work.
"require": {
"propel/propel": "2.0.*@dev",
"propel/propel-bundle": "~2.0@dev"
}
You must add:
"symfony/propel1-bridge": "master-dev"
as well.
https://github.com/symfony/symfony/commit/3f4b87d8c0103297fe6528845cdee0946de860ae

Its Propel1 bridge. What has v2 to do with it?

The version number doesn't matter.
I was just saying that Symfony no longer installs propel1-bridge by default. So if you follow the directions to install PropelBundle as they are written it will fail because the propel1-bridge classes are not there.

I guess it matters as Propel v2 doesnt need propel1-bridge.

Composer is showing propel/propel1 as required for
propel-bundle ~2.0@dev.
So it install propel1 as well.
./composer.phar show propel/propel-bundle ~2.0@dev
name     : propel/propel-bundle
descrip. : Integration of Propel in Symfony2
keywords : orm, persistence, propel
versions : * 2.0.0-alpha4
type     : symfony-bundle
license  : MIT License (MIT) (OSI approved) https://spdx.org/licenses/MIT.html#licenseText
source   : [git] https://github.com/propelorm/PropelBundle.git d54ee14d2a8cb636f413661930247834df61386b
dist     : [zip] https://api.github.com/repos/propelorm/PropelBundle/zipball/d54ee14d2a8cb636f413661930247834df61386b d54ee14d2a8cb636f413661930247834df61386b
names    : propel/propel-bundle

autoload
psr-0
Propel\PropelBundle => .

requires
propel/propel1 ~1.6
symfony/symfony ~2.4

requires (dev)
fzaninotto/faker dev-master
sensio/framework-extra-bundle ~3.0

This was a bug in 2.0.0-alpha4, which is fixed since months in master.

authors: ben-giles marcj

license: mit

license_source: bigquery


text:
Unsupported ARIA attribute

Hey, thanks for raising this. I'll get this sorted for the next release.

The PR for this is now in staging, this will be addressed in the next release

authors: HughParry hckhanh

repo: prosopo/captcha


text:
Visual for your bundle

Hi,
Your bundle look like great feature, thanks for your work,
Do you have any example to so visual new functionnality ?
Thanks in advance !

Hi
Visually it looks the same as EasyAdmin
This library is just to enhance the core functionality with more advanced features that are not supported build it.
It's still in early stages for now. With time I will extract code from personal projects to add them here.

Thanks for you response, do you have a personal project to see and share your advanced news features ?
I'm interested if it's possible

Unfortunately no project is public that I can share.

authors: dragosprotung john-dufrene-dev

repo: protung/easyadmin-plus-bundle


text:
Add an ability to deploy feature envs from forked repos

Currently it's not possible to exec feature testing workflows on PRs which have been opened on forked repos (due to pull_request_target)
A possible solution: checkout the forked branch, push it to our repo (on request, on added label) and run the workflow as usual

HI @Haarolean  I want to try this issue.
Can you give me headstart for this issue ?

HI @Haarolean I want to try this issue. Can you give me headstart for this issue ?

Hey, not so sure about the implementation. So basically we'd need a workflow which will take two inputs: first one is the forked repo (username/reponame) and the second one is the branch name we want, it will clone the repo and push the branch to our repo. And I'm not sure about the rest -- we usually add labels to the PRs, but I don't want to create a dummy PR just for that, so maybe we could run workflows with inputs instead, but it'd be complicated to track already deployed envs. What do you think?

repo: provectus/kafka-ui


text:
Issue 2304: applying fix for saved filters cancel navigation issue

[ ] Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)
Fixing navigation for saved filters navigation
Demo: https://recordit.co/zebQ52z15L
Is there anything you'd like reviewers to focus on?
How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

[ ] No need to
[x] Manually (please, describe, if necessary)
[ ] Unit checks
[ ] Integration checks
[ ] Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
[x] My changes generate no new warnings (e.g. Sonar is happy)
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged

Check out Contributing and Code of Conduct
A picture of a cute animal (not mandatory but encouraged)

Pls check all the warnings

authors: workshur yvaeltercero


text:
chore: bump dependencies

I ran poetry update on your lockfile. Do you want this monitored by dependabot as well?

@afuetterer it seems that the ruff update has caused some formatting changes which break the tests that check the ruffed output.

Oh no, damn it. Should I try to fix the tests or you want to stick to the older ruff version for now?

Updating the tests would be fine

Okay, let's see. :)

@afuetterer Turns out I was wrong: This is actually a bug. I'll create a fix for that in a different PR

I see, excellent.

authors: afuetterer provinzkraut

repo: provinzkraut/unasyncd


text:
Error streams duplicated in every job

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Start-RsJob { $ErrorActionPreference = "Stop"; Write-Error "Break me!" }
Start-RsJob { Write-Host "Hi" }
Receive-RSJob -Id 2

Results in
Exception calling "EndInvoke" with "1" argument(s): "The running command stopped because the preference variable
"ErrorActionPreference" or common parameter is set to Stop: Break me!"

Basically one failed job pollutes the streams of all the others.
Which versions of Powershell and which OS are affected by this issue? Did this work in previous versions of our scripts?
PoshRSJob 1.7.3.11
Name                           Value
----                           -----
PSVersion                      5.1.14409.1005
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14409.1005
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

In PoshRSJob.psm1 there's a "Routine to handle completed runspaces" and that's what seems to extract the error and add it to each job.
But I don't understand why it's dragging them out of other jobs and then appending them to later jobs.

It's because you check $CaughtErrors and never reset it. Modifying it to this fixes the problem:
$PoshRS_jobCleanup.PowerShell = [PowerShell]::Create().AddScript( {
        #Routine to handle completed runspaces
        #$PoshRS_jobCleanup.Host.UI.WriteVerboseLine("Begin Do Loop")
        Do {
            [System.Threading.Monitor]::Enter($PoshRS_Jobs.syncroot)
            try {
                Foreach ($job in $PoshRS_Jobs) {
                    $CaughtErrors = $false

I fixed a similar error for $Data in #122, but did not look at the $errors :)

I'm not able to reproduce this anymore on the current build.

authors: MVKozlov codykonior

repo: proxb/PoshRSJob


text:
错误码400

问题描述 当已有下载任务时再去创建，则会显示：创建失败，错误码400
版本号 3.03
操作系统 win10 1803 home edge浏览器
相关截图
相关日志

咦，我也遇到这个问题了。今天还下载了一个，第二个时就出现了错误代码400.
20180927

一样的

扩展相关的问题请移步到这里：https://github.com/proxyee-down-org/proxyee-down-extension/issues

authors: Literous certainlin gzkvb monkeyWie

repo: proxyee-down-org/proxyee-down


text:
V3.0

Update zh-TW.js

感谢！

authors: kulaLin monkeyWie


text:
Libp2p updates

TODO:

[x] implemented libp2p updates based on sigp/lighthouse/pull/979
[ ] enr_fork_id fix
[ ] rpc needs to be revisited
[ ] pubsub logic for propagation and filtering needs to be revisited
[ ] investigate dependency issues with lighthouse

sample apps work, but there is still work to be done to keep mothra generic

repo: prrkl/mothra


text:
How can I set default label background color to gray?

Btw, strip a label named @receiver doesn't work.
My configuration below.

Thanks in advance.

Btw, strip a label named @receiver doesn't work.

Receiver is not really a label, it's an extra field. I guess that handling of special @foo labels got a bit too messy.

How can I set default label background color to gray?

The config you provided should work, I tested the following config with latest release and it works as expected:
    custom:
      priority:
        - value: '3'
          color: '#f8b739'
        - value: '4'
          color: '#f3dcad'
        - value: '5'
          color: '#e7eaf6'
        - value_re: .*
          color: '#666'

Result:

@prymitive Sorry, I didn't describe it clearly. I want to defines a background color for all labels, not a specific one.

Right, sorry, thanks for clarification.
It's currently not possible.
But it feels like I should simply provide a single configuration scheme for customising labels with regex rules by matching both names and labels and drop all other options (like static colours).
Configuration grew a bit too organic so it's a little messy (as in the @receiver case).
I'm happy to refactor it, but might take a few weeks before I find the time for it.

I've found a work around to do that. Override the badge style in custom.css.
.badge-warning {
    color: #fff;
    background-color: #bababa !important;
}

Obiously didn't think of that, good idea. I'll keep this ticket open for the refactoring and cleanup of label configuration

hi,
+1 for strip label named @receiver and other @labels btw

authors: duthifree liujiawinds prymitive

repo: prymitive/karma


text:
tmt does not like if entrypoint is not standard

While working on our CLI tool, I found this annoyance, if I have ENTRYPOINT set, tmt starts the container with the command and just  exits, subsequent commands file. The error is cryptic:
❯ tmt run -dddvvv
Using tree '/home/mvadkert/git/gitlab.com/testing-farm/cli'.
/var/tmp/tmt/run-007
tmt version: 1.9.0 (599b9a1)
Read file '/var/tmp/tmt/run-007/run.yaml'.
Run data not found.
Enabled steps: discover, report, finish, provision, execute and prepare
    Sync the worktree to '/var/tmp/tmt/run-007/plans/sanity/tree'.
    Run command 'rsync -ar --exclude .git /home/mvadkert/git/gitlab.com/testing-farm/cli/ /var/tmp/tmt/run-007/plans/sanity/tree'.
Found 1 plan.
Write file '/var/tmp/tmt/run-007/run.yaml'.

/plans/sanity
summary: Sanity test plan
info
    environment: {}
    context: {}
wake
    discover
        Read file '/var/tmp/tmt/run-007/plans/sanity/discover/step.yaml'.
        Step data not found.
        Read file '/var/tmp/tmt/run-007/plans/sanity/discover/tests.yaml'.
        Discovered tests not found.
        Using the 'DiscoverFmf' plugin for the 'fmf' method.
        status: todo
        Write file '/var/tmp/tmt/run-007/plans/sanity/discover/step.yaml'.
        Write file '/var/tmp/tmt/run-007/plans/sanity/discover/tests.yaml'.
    provision
        Read file '/var/tmp/tmt/run-007/plans/sanity/provision/step.yaml'.
        Step data not found.
        Read file '/var/tmp/tmt/run-007/plans/sanity/provision/guests.yaml'.
        Provisioned guests not found.
        Using the 'ProvisionPodman' plugin for the 'container' method.
        status: todo
        Write file '/var/tmp/tmt/run-007/plans/sanity/provision/step.yaml'.
        Write file '/var/tmp/tmt/run-007/plans/sanity/provision/guests.yaml'.
    prepare
        Read file '/var/tmp/tmt/run-007/plans/sanity/prepare/step.yaml'.
        Step data not found.
        Using the 'PrepareShell' plugin for the 'shell' method.
        status: todo
        Write file '/var/tmp/tmt/run-007/plans/sanity/prepare/step.yaml'.
    execute
        Read file '/var/tmp/tmt/run-007/plans/sanity/execute/step.yaml'.
        Step data not found.
        Read file '/var/tmp/tmt/run-007/plans/sanity/execute/results.yaml'.
        Test results not found.
        Using the 'ExecuteInternal' plugin for the 'tmt' method.
        status: todo
        Write file '/var/tmp/tmt/run-007/plans/sanity/execute/step.yaml'.
        Write file '/var/tmp/tmt/run-007/plans/sanity/execute/results.yaml'.
    report
        Read file '/var/tmp/tmt/run-007/plans/sanity/report/step.yaml'.
        Step data not found.
        Report step always force mode enabled.
        Clean up workdir '/var/tmp/tmt/run-007/plans/sanity/report'.
        status: todo
        Using the 'ReportDisplay' plugin for the 'display' method.
        Write file '/var/tmp/tmt/run-007/plans/sanity/report/step.yaml'.
    finish
        Read file '/var/tmp/tmt/run-007/plans/sanity/finish/step.yaml'.
        Step data not found.
        Using the 'FinishShell' plugin for the 'shell' method.
        status: todo
        Write file '/var/tmp/tmt/run-007/plans/sanity/finish/step.yaml'.
    action
go
    discover
        workdir: /var/tmp/tmt/run-007/plans/sanity/discover
        how: fmf
        order: 50
            Run command 'git rev-parse --show-toplevel'.
            out: /home/mvadkert/git/gitlab.com/testing-farm/cli
        directory: /home/mvadkert/git/gitlab.com/testing-farm/cli
            Copy '/home/mvadkert/git/gitlab.com/testing-farm/cli' to '/var/tmp/tmt/run-007/plans/sanity/discover/default/tests'.
            Run command 'git rev-parse --short HEAD'.
            out: 3111ba8
        hash: 3111ba8
            Check metadata tree in '/var/tmp/tmt/run-007/plans/sanity/discover/default/tests/'.
        summary: 2 tests selected
            /tests/commands/request
            /tests/commands/version
        status: done
        Write file '/var/tmp/tmt/run-007/plans/sanity/discover/step.yaml'.
        Write file '/var/tmp/tmt/run-007/plans/sanity/discover/tests.yaml'.
        Write file '/var/tmp/tmt/run-007/plans/sanity/discover/run.yaml'.
    provision
        workdir: /var/tmp/tmt/run-007/plans/sanity/provision
        how: container
        order: 50
        image: quay.io/testing-farm/cli:latest
            Check for container image 'quay.io/testing-farm/cli:latest'.
            out: 082f27d79382
        name: tmt-var-tmp-tmt-run-007-plans-sanity
            Start container 'quay.io/testing-farm/cli:latest'.
            Run command 'podman run --security-opt seccomp=unconfined --name tmt-var-tmp-tmt-run-007-plans-sanity -v /var/tmp/tmt/run-007/plans/sanity:/var/tmp/tmt/run-007/plans/sanity:Z -itd quay.io/testing-farm/cli:latest'.
            err: time="2022-02-09T20:46:01+01:00" level=warning msg="The input device is not a TTY. The --tty and --interactive flags might not work properly"
            out: 0de66e9ef36b875974b0b3e7a92e8f702af38b1c827438351643f9f352f651d9
            Run command 'podman exec tmt-var-tmp-tmt-run-007-plans-sanity sh -c cat /etc/os-release'.
            out: PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
            out: NAME="Debian GNU/Linux"
            out: VERSION_ID="11"
            out: VERSION="11 (bullseye)"
            out: VERSION_CODENAME=bullseye
            out: ID=debian
            out: HOME_URL="https://www.debian.org/"
            out: SUPPORT_URL="https://www.debian.org/support"
            out: BUG_REPORT_URL="https://bugs.debian.org/"
        distro: Debian GNU/Linux 11 (bullseye)
            Run command 'podman exec tmt-var-tmp-tmt-run-007-plans-sanity sh -c uname -r'.
            out: 5.15.16-100.fc34.x86_64
        kernel: 5.15.16-100.fc34.x86_64
        summary: 1 guest provisioned
        status: done
        Write file '/var/tmp/tmt/run-007/plans/sanity/provision/step.yaml'.
        Write file '/var/tmp/tmt/run-007/plans/sanity/provision/guests.yaml'.
    prepare
        workdir: /var/tmp/tmt/run-007/plans/sanity/prepare
        summary: 0 preparations applied
        status: done
        Write file '/var/tmp/tmt/run-007/plans/sanity/prepare/step.yaml'.
    execute
        workdir: /var/tmp/tmt/run-007/plans/sanity/execute
        how: tmt
        order: 50
        exit-first: False
            Write file '/var/tmp/tmt/run-007/plans/sanity/execute/data/tests/commands/request/metadata.yaml'.
            Write file '/var/tmp/tmt/run-007/plans/sanity/execute/data/tests/commands/version/metadata.yaml'.
        Write file '/var/tmp/tmt/run-007/plans/sanity/execute/tmt-file-submit'.
            Back up '/usr/bin/rstrnt-reboot' if present.
            Run command 'podman exec tmt-var-tmp-tmt-run-007-plans-sanity sh -c [ ! -e "/usr/bin/rstrnt-reboot" ]'.
            Run command 'podman exec tmt-var-tmp-tmt-run-007-plans-sanity sh -c cp "/var/tmp/tmt/run-007/plans/sanity/execute/default/reboot_template" "/usr/bin/rstrnt-reboot" && chmod +x "/usr/bin/rstrnt-reboot"'.
            err: Error: can only create exec sessions on running containers: container state improper
            Command returned '255'.
            Remove our reboot script implementations.
            Run command 'podman exec tmt-var-tmp-tmt-run-007-plans-sanity sh -c rm "/usr/bin/rstrnt-reboot"'.
            err: Error: can only create exec sessions on running containers: container state improper
            Command returned '255'.
    finish
        workdir: /var/tmp/tmt/run-007/plans/sanity/finish
            Run command 'podman container stop tmt-var-tmp-tmt-run-007-plans-sanity'.
            out: tmt-var-tmp-tmt-run-007-plans-sanity
        container: stopped
            Run command 'podman container rm -f tmt-var-tmp-tmt-run-007-plans-sanity'.
            out: 0de66e9ef36b875974b0b3e7a92e8f702af38b1c827438351643f9f352f651d9
        container: removed
        summary: 0 tasks completed
        status: done
        Write file '/var/tmp/tmt/run-007/plans/sanity/finish/step.yaml'.

stderr (1/1 lines)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Error: can only create exec sessions on running containers: container state improper

Failed to run command 'podman exec tmt-var-tmp-tmt-run-007-plans-sanity sh -c rm "/usr/bin/rstrnt-reboot"'. Reason: Command returned '255'.

I believe we should support setting entrypoint in these cases or maybe even force entrypoint to sh? WDYT @lukaszachy @psss ?

I'd say tmt should set entrypoint to bash (as you pointed in #1047) but there should be way for user to keep entrypoint as is (if they know what they are doing) or to set it to their preferred value. TMT will just assume it behaves as if it was unset/set to bash

@lukaszachy agreed, seems like a good step forward. And document tmt right now requires bash in the container to work

authors: lukaszachy thrix

repo: psss/tmt


text:
tmt tests import -> traceback for missing RunFor

I was missing RunFor in the Makefile and I got traceback.
Please make it nicer message instead and make sure all expectated values from Makefile are in try/except because they will be missing for someone :)
Traceback (most recent call last):
  File "/home/lzachar/.virtualenvs/tmt/bin/tmt", line 7, in <module>
    exec(compile(f.read(), __file__, 'exec'))
  File "/home/lzachar/_important_/Gits/tmt/bin/tmt", line 11, in <module>
    tmt.cli.main()
  File "/home/lzachar/.virtualenvs/tmt/lib/python3.7/site-packages/click/core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "/home/lzachar/.virtualenvs/tmt/lib/python3.7/site-packages/click/core.py", line 717, in main
    rv = self.invoke(ctx)
  File "/home/lzachar/.virtualenvs/tmt/lib/python3.7/site-packages/click/core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/lzachar/.virtualenvs/tmt/lib/python3.7/site-packages/click/core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/lzachar/.virtualenvs/tmt/lib/python3.7/site-packages/click/core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/lzachar/.virtualenvs/tmt/lib/python3.7/site-packages/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/home/lzachar/.virtualenvs/tmt/lib/python3.7/site-packages/click/decorators.py", line 17, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/home/lzachar/_important_/Gits/tmt/tmt/cli.py", line 497, in import_
    path, makefile, nitrate, purpose, disabled)
  File "/home/lzachar/_important_/Gits/tmt/tmt/convert.py", line 135, in read
    r'^RunFor:\s*(.*)', testinfo, re.M).group(1).split()
AttributeError: 'NoneType' object has no attribute 'group'

@hegerj, would like to take this one?

@psss sure

authors: hegerj lukaszachy psss


text:
Rename master branch to main

It's a small thing, but meaningful it big ways.

some of the bits of CI are dependent on this change. I'll update them to look for both, and then after the switch remove master.

authors: awead whereismyjetpack


text:
Make it (somehow) possible to avoid needless allocations when serialising requests (needs GAT?)

I just was looking at some code and wondered why we really need vec! here:
impl GetInputFocusRequest {
    /// Serialize this request into bytes for the provided connection
    pub fn serialize(self) -> BufWithFds<PiecewiseBuf<'static>> {
        let length_so_far = 0;
        let mut request0 = vec![
            GET_INPUT_FOCUS_REQUEST,
            0,
            0,
            0,
        ];
        let length_so_far = length_so_far + request0.len();
        assert_eq!(length_so_far % 4, 0);
        let length = u16::try_from(length_so_far / 4).unwrap_or(0);
        request0[2..4].copy_from_slice(&length.to_ne_bytes());
        (vec![request0.into()], vec![])
    }
}

All of this is static. It would e.g. possible to do something like this (however, no idea how to set the length field in a way that works for both big endian and little endian):
fn serialize(self) -> &'static [u8] {
    &[GET_INPUT_FOCUS_REQUEST, 0, 1, 0]
}

Of course, this return type is not compatible with everything else. Perhaps a Cow<'static, [u8]> could work?
Also: Of course, "just because" is not good enough, so: Would there be any actual benefit to doing this?
(The original code has two allocations. The one I am talking about above is for the "actual on-the-wire bytes". There is also the two vec!s in the last line. The first one could also be replaced with something static, but Cow<'static, [Cow<'static, [u8]]> seems a bit ugly. The second is actually free since there are no FDs and AFAIK an empty Vec does not allocate anything.)

My solution to this (that I discussed earlier in #687) is to rewrite the Serialize trait to, rather than return a buffer of data, fill a buffer with the data required. The design I was experimenting with (that also takes advantage of vectorization) would look something like this:
pub trait Serialize {
    fn serialize<'this>(&'this self, target: &mut [IoSlice<'this>]);

    /// Get the number of slices that need to be available for `serialize`.
    fn num_slices(&self) -> usize;

    /// This function can be overrided by downstream implementors to use a fixed size array instead of a vector.
    fn to_slices(&self, callback: impl FnOnce(&mut [IoSlice<'_>])) {
        let mut target = vec![empty_io_slice(); self.num_slices()];
        self.serialize(&mut target);
        callback(&mut target);
    }
}

impl Serialize for GetInputFocusRequest {
    fn serialize(...) {
        target[0] = &[OPCODE, 0, 0, 0].into_io_slice();
    }

    fn num_slices(...) {
        1
    }

    fn to_slices(...) {
        let mut target = [empty_io_slice()];
        self.serialize(&mut target);
        callback(&mut target);
    }
}

With smaller requests, it ensures that serialization is kept out of the heap entirely. With larger requests that need the heap, it ensures that only one level is needed.
Is it worth it? Maybe. The bottleneck here is definitely going to be server communication. That being said, it should be worth it in certain cases, such as with larger requests (e.g. Trapezoids, which requires a copy under the current implementation).

Some things I noticed from profiling the simple_window example:

Just as we expected, overhead from polling the server takes up most of the time. In contrast, however, it doesn't take up as much time as expected. When you factor out the time that's spent waiting for events to arrive, I'd say about twice as much time is spent on I/O in comparison to allocations.
A surprising amount of time is spent in try_read_packets, more than pretty much everything else that isn't I/O. Most of it's in allocations and memmove. You could probably squeeze some important performance wins there.
PolyLineRequest::serialize() spends all of its time up to a rounding error growing/allocating the vectors it returns. So yes, reducing the allocations here would help a lot.
Other notable time sinks include Event::parse() and mutex locking/unlocking.
That being said, the above all go pretty fast in the grand scheme of things. About as much time is spent in the fmt module and writing to standard output as all of the above.

authors: notgull psychon


text:
Add a way to construct ClientMessageData

Currently, the only way to construct a ClientMessageData is TryParse. That is really not meant to be user-facing API. I guess this needs something like from_data32 etc.
It would be even better to have something like fn construct_client_message32(window: WINDOW, type_: ATOM, data: [u32; 5]) -> ClientMessageEvent. This should be able to set all the fields correctly and make using this a lot simpler...

In general for union X { Y, Z, ... }, one ought to impl From<Y> for X

Thanks for the suggestion, that seems like a good idea.

authors: dalcde psychon


text:
Port some existing project from xcb to x11rb

It would be nice to port some existing project from xcb to x11rb. This would show that this crate actually works and could point out holes in the API.
Crates.io allows to see dependent crates and sorts them by download count: https://crates.io/crates/xcb/reverse_dependencies
It would be a bad idea to send PRs to those projects for the port, because why? That would only annoy people.

I think porting st first would be easier since it have lesser lines of code.

I do not want to stop anyone from doing anything, but:
st includes X11/Xft/Xft.h. That pulls in Xft, freetype, and fontconfig. freetype and fontconfig (by itself) have nothing to do with X11. Xft is "just" a bridge between freetype and X11. Thus, one would need some Rust bindings to these libraries for such a port.
Anyway: Thanks for the suggestion. Sorry for the bad news.

authors: pickfire psychon


text:
minor hint: mv command with --help hint improvement

using onyo mv --help tells me in order to rename a file I have to use onyo set, but IRL using onyo edit also works AFAIK
this is a very minor thing

True and should be pointed out.
This leads to another small-ish issue, though: set does have a -r flag while edit doesn't. They should both do the same IMO.

This leads to another small-ish issue, though: set does have a -r flag while edit doesn't. They should both do the same IMO.

Verdict: Nope. edit is intentionally different and does not need that safeguard.
Hence, documentation is all that's to do here.

authors: bpoldrack j-leo

repo: psyinfra/onyo

license: ISC


text:
revamp ui

Changelog

increase pharagraph font size
add menu carrer, blog on sidebar

Screenshot

LGTM 👍

authors: masardee nemixe

repo: pt-dot/depot


text:
don't pip install opencv-python if opencv-contrib-python is installed

I just pip-installed the current dev branch into the venv for my app. My app uses functionality from the opencv-contrib-python. After installing imgui_bundle, i now have both opencv-contrib-python and opencv-python installed, and trying to use functionality from the contrib version does not work.
In short, opencv-python should not be installed if opencv-contrib-python is already installed. I am not sure if there is a way to specify that with the dependency infrastructure (e.g. somehow to say that either of these is fine), but right now this messes with a perfectly fine set of pip packages ;)

Humm.... DLL Hell approaching...
Strange however, I just retested this example under windows (not from this repo), which use an Oil painting effect from opencv-contrib .

So I would say it seems to kinda work on my computer.
Anyway, this is probably due to a DLL clash. I solved this under macOS and linux by compiling a minimalist version of OpenCV and statically linking it inside imgui_bundle. Please try it also and tell me if it helps:
demos/litgen/imgui_bundle/external/immvision/find_opencv.cmake:276
macro(immvision_find_opencv)
    if (IMGUI_BUNDLE_IMMVISION_FETCH_OPENCV)
        if (WIN32)
            set(IMGUIBUNDLE_OPENCV_WIN_USE_OFFICIAL_PREBUILT_460 ON)
        else()
            set(IMGUIBUNDLE_OPENCV_FETCH_SOURCE ON)
        endif()
    endif()

becomes:
macro(immvision_find_opencv)
    if (IMGUI_BUNDLE_IMMVISION_FETCH_OPENCV)
        set(IMGUIBUNDLE_OPENCV_FETCH_SOURCE ON)
    endif()

This will result in pip fetching OpenCV from source and compiling it, then statically link it into imgui_bundle.

... Fetching + compiling a minimalist OpenCV will add 3'30" to the pip build time

Ok, two things:

my previous suggestion about changing imgui bundle build mode will not help since the issue lies between two opencv packages, not within imgui bundle.

So I guess the only solution is to remove opencv from the requirements (as far as i understood  from reading the opencv contrib pipy page)

Building opencv via pip currently fails on windows because of a known bug in cmake 3.25.20 : pyproject.toml shall exclude cmake 3.25.20. I will push this later
3

This is a bit akin dll hell indeed. SUPER nice example by the way, would be nice to include somewhere, maybe as a third demo?
But yeah, fun new issue eh? So what happened exactly:

opencv-contrib-python was already installed in my venv and working fine upon cv2 import
installing imgui_bundle caused opencv-python to be installed
import cv2 now loads opencv from opencv-python not opencv-contrib-python
i uninstalled opencv-python
now import cv2 cannot find the module, despite opencv-contrib-python still being present
so i reinstalled opencv-contrib-python
all is working fine now

Solutions:

Yeah, one possible solution for now would be to not list opencv-python as a dependency, but then you have the problem that immvision demo won't run if there is no opencv package installed at all.
The open-cv python readme explicitly says not to install only one of the packages, if you have more than one uninstall them all and reinstall the one you want. Perhaps we can add some code somewhere in the module loading to check for this situation and telling the user to rectify it? I don't like this.
It would be great if opencv-python is installed by default, but advanced users can specify to not install it with something like imgui_bundle[no-opencv]. In a pyproject.toml file dependencies for extras are marked with, e.g., extra=="opencv", so it is maybe possible to add a specifier extra!='no-opencv' to an opencv-python (untested, not found on google...). But i think your dependencies instead come from setup.py, right? Then that would definitely not work. Seems rather hacky too
The best solution would be if opencv-python would not install when opencv-contrib-python is already present. From a google this does not appear to be possible with pip. Will post this upstream.

Ah, we're not the first to run into this:
https://github.com/opencv/opencv-python/issues/677
I think the solution they provide ("after install remove unused package variants") is not a good one because there will be plenty of packages listing imgui_bundle as a dependcy (mine's one) and at least some of those will also list opencv-contrib-python (again, mine). After just pip-installing such a package, the user will then have multiple opencv packages and need to do an uninstall. It also rather messes with my automated executable building as a github action.
Your solution is better. Its apparently what is commonly done as well for packages depending on tensorflow
Also relevant: https://discuss.python.org/t/conditional-package-install-depending-on-other-packages-in-environment/4140

I'll provide a PR

authors: dcnieho pthom


text:
AP1155 Archive Strategy Implementation

This will be the first opinioanted strategy for 1155, and will jsut provide a really simple validation check that data getting stored per token are strings (ex: ipfs links)

Closing due to protocol changes.

repo: public-assembly/assembly-press


text:
Estimate and display gas fee for minter, airdrop functions

Resolves #189

Checklist before requesting a review

[x] I have added documentation to README
[x] I have performed a self-review of my code
[] I have tested this new feature or change on devnet and verified that it works
I could not check if estimation is correct because right now no gas fee is collected on both mainnet and testnet

repo: public-awesome/stargaze-tools


text:
Extra docs on exactly where to start installing things?

I see this line is where some PRs start to make changes:
https://github.com/publiclab/pi-builder/blob/f9481e45f189ba1e7b15c6a6c2dd364b31540547/builder/chroot-script.sh#L207
Should we put some comment there and delineate an area where it's ideal to start installing scripts and running git or npm? I assume git is installed, is npm too?
Thank you!

Looking at #37 to install some NPM stuff...

Aha, sorry, so i think we need to separately document where to put things on initial install, vs. on each startup.
Maybe we ought to actually make 2 files, called startup and setup, which would be run as root? Then just link to them from the appropriate places? But i'm open to whatever makes sense!

We have two scripts, one runs outside the chroot as the build system (build.sh) and the other inside chroot (chroot-script.sh). Both run as root. The appropriate place to install git and npm etc is chroot-script.sh.

OK, and the place to put things to run on boot would be in a crontab,
potentially? Thanks!
On Mon, Oct 22, 2018 at 11:16 PM Sebastian Silva notifications@github.com
wrote:

We have two scripts, one runs outside the chroot as the build system
(build.sh) and the other inside chroot (chroot-script.sh). Both run as
root. The appropriate place to install git and npm etc is chroot-script.sh
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/publiclab/pi-builder/issues/36#issuecomment-432074047,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABfJ0x-avlt_zp9js4CXVHrGl_WDzILks5unooDgaJpZM4X0UNV
.

Oh, yes, I should add these questions to the docs. The canonical way to run stuff on boot is to add them to /etc/rc.local.

In the Camera PR I had to add an empty rc.local because the install script will modify it https://github.com/publiclab/pi-builder/pull/13/files#diff-25aa350b8efc5496496765f60725aa9c
Also this is documented at https://publiclab.gitlab.io/pi-builder/scripting.html#running-scripts-on-startup

The general architecture is that files under /builder/files get copied over to the final image (before chroot script is run).

awesome, thanks!!!
On Wed, Oct 24, 2018 at 1:45 PM Sebastian Silva notifications@github.com
wrote:

The general architecture is that files under /builder/files get copied
over to the final image (before chroot script is run).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/publiclab/pi-builder/issues/36#issuecomment-432759721,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABfJ26inE8fasQnbue-NZVUbOI6M9M0ks5uoKcegaJpZM4X0UNV
.

authors: icarito jywarren

repo: publiclab/pi-builder


text:
PROD SUPPORT: In complainant text box during E-filing , when written in Malayalam while generating pdf  box appears with symbols not with words

Describe the bug

Hi @Taherabharmal, for this previously we were using default Roboto font, that's why these boxes were coming for Malayalam. So we are now using kartika font which is working for both English and Malayalam. If it needs to be changed please provide the font.
Plz find the current font pic:

Hi @Susmitabe, tested in uat env, working as expected.
Attaching screenshot for reference:

cc: @rajeshcherukumalli @Ramu-kandimalla

@iknoorkaur @TusharKatiyar2002
Did we test this for unicode as well, that's the one - people usually use?
Do we need to pass specific instructions on what font should be used by the users?

Hi @mehulseg24, tested with various fonts in Malyalam text:

Noto Sans Malayalam

Manjari

Anek Malayalam

Baloo Chettan 2

Arima

cc: @rajeshcherukumalli @Ramu-kandimalla

repo: pucardotorg/dristi


text:
build.sbt: error: not found: value wartremoverErrors

run sbt compile failed, not found: value wartremoverErrors
[info] Loading project definition from /Users/hangbozhao/work/frontend_zhb/project
build.sbt:21: error: not found: value wartremoverErrors
wartremoverErrors := Warts.unsafe

My sbt files are as following:
build.properties
sbt.version = 0.13.2
project/plugin.sbt
addSbtPlugin("org.wartremover" % "sbt-wartremover" % "1.1.1")
build.sbt
import AssemblyKeys._

assemblySettings

jarName in assembly := "frontend.jar"

name := "frontend"

version := "1.0"

scalaVersion := "2.11.1"

scalacOptions += "-target:jvm-1.7"

instrumentSettings

ScoverageKeys.minimumCoverage := 1

ScoverageKeys.failOnMinimumCoverage := false

wartremoverErrors ++= Warts.unsafe  //!!!!!!!!!!!!!!  not found: value wartremoverErrors

publishArtifact in Test := false

javacOptions ++= Seq("-source", "1.7")

libraryDependencies ++= Seq(many stuffs)

sbt-wartremover requires at least sbt version 0.13.5, because it's an AutoPlugin.
Ideally sbt would enforce this, but for now I'll document this in the README.

authors: dwijnand zhaohangbo

repo: puffnfresh/wartremover


text:
Add a wart that disables implicits without a type ascription.

@puffnfresh This PR adds a wart that disables implicit definitions without an explicit type ascription.

Nice! Very useful :+1:

authors: ChrisNeveu puffnfresh


text:
Add "Priority feature requests" to Enterprise plan description

Fixes #11643 (see for context)

@meagancojocar this is an older issue, is this still something we want to include on the pricing page?

repo: pulumi/docs


text:
awsx.scheduler.Schedule option ScheduleTargetEcsParameters is missing serviceConnectConfiguration

Describe what happened
awsx.ecs.FargateServiceArgs has the option serviceConnectConfiguration which is not present in ScheduleTargetEcsParameters.
See https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateService.html for reference
Sample program
new aws.scheduler.Schedule(detailedResourceName(name), {
  name: detailedResourceName(name),
  groupName: cronScheduleGroup.name,
  scheduleExpression: schedule,
  target: {
    arn: cluster.arn,
    roleArn: cronJobSchedulerRole.arn,
    input: JSON.stringify({
    // @see https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_TaskOverride.html
    cpu: `${cpu}`,
    memory: `${memory}`,
    ecsParameters: {
      serviceConnectConfiguration: {
          enabled: true,
          namespace: clusterHttpNamespace.arn,
      },
      launchType: 'FARGATE',
      networkConfiguration: {
          securityGroups: [securityGroup.id],
          subnets: vpc.privateSubnetIds,
      },
      taskDefinitionArn: cronTaskDefinition.taskDefinition.apply(
          (task) => task!.arn,
      ),
    },
  },
});

Log output
No response
Affected Resource(s)
No response
Output of pulumi about
Does not compile
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Hey @Defman, thanks for reporting this issue!
From what I can tell this is not present in the AWS APIs either. See: https://docs.aws.amazon.com/scheduler/latest/APIReference/API_EcsParameters.html.
It seems like Service Connect is not supported for the event bridge scheduler integration. I'd recommend getting a feature request for this started in the AWS container roadmap in order to get it on their radar.
I'm gonna close this issue in the meantime, but don't hesitate to re-open it if there's any un-answered questions.

authors: Defman flostadler

repo: pulumi/pulumi-aws


text:
An error occurred trying to start process 'pulumi' with working directory '/tmp/pulumi'. No such file or directory

What happened?
We are using pulumi dotnet Automation API and we set up the working directory from the .Net Core 6 project and called to CreateOrSelectStackAsync.
We hosted our application in K8 and we are keep getting error "errorMessage": "An error occurred trying to start process 'pulumi' with working directory '/tmp/pulumi'. No such file or directory", but we verify the folder path exists in the pod and tmp folder have the necessary permissions as well.
This how we set up the working directory:
var stackArgs = new InlineProgramArgs(PulumiConfigurationConstants.ProjectName, environment, program)
        {
            StackSettings = new Dictionary<string, StackSettings>
            {
                [environment] = new() {SecretsProvider = PulumiConfigurationConstants.SecretsProvider,}
            },
            SecretsProvider = PulumiConfigurationConstants.SecretsProvider,
            ProjectSettings = new ProjectSettings(PulumiConfigurationConstants.ProjectName, ProjectRuntimeName.Dotnet)
            {
                Backend = new ProjectBackend {Url = PulumiConfigurationConstants.PulumiProjectBackendUrl},
            },
            WorkDir = Path.Cobmine("..", "tmp", "pulumi")
        };
        var stack = await LocalWorkspace.CreateOrSelectStackAsync(stackArgs);

  I can see the file also generated in   /tmp/pulumi folders.

Expected Behavior
Pulumi able to access the folder location and start the process
Steps to reproduce
Mention in the what happened section
Output of pulumi about
Mention in the what happened section
Additional context
Mention in the what happened section
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Hi @lahiruchamira . I wish I had a better answer for you, but I'm just as stumped as you are.
I searched the codebase for your error message in case Pulumi was doing something tricky when loading the stack, but the error doesn't appear in our codebase, which means its wrapped from another source. I'd be surprised if Pulumi was doing something odd with your tmp directory.
The only thing of notice is that the filepath provided in this snippet...
            WorkDir = Path.Cobmine("..", "tmp", "pulumi")

is not necessarily /tmp/pulumi, because .. is relative to the current working directory. Thus, the correctness of this line demands on the WORKDIR setting in your Dockerfile. It's also worth noting there's a typo in this line. Perhaps the path you provided is also typo'd?

Ran into this one today and it's because the pulumi CLI wasn't installed on the container. Makes total sense in retrospect but the error back from the Automation API lead me down the wrong path for a bit.

The issue is fairly old and we haven't heard back on the latest question. I'll go ahead and close it as no-repro.

authors: RobbieMcKinstry lahiruchamira mikhailshilkov whatsfordinner

repo: pulumi/pulumi-dotnet


text:
Upgrade terraform-libvirt-provider to 0.6.12

Closes #15
I hope it's cool I took a stab at this. I was running into a bug with bridge mode and qemu-agent not working properly but noticed https://github.com/dmacvicar/terraform-provider-libvirt/pull/873 fixes the problem. After updating to 0.6.12, I've confirmed it fixed the problem for me using pulumi-libvirt.
I haven't done any Pulumi/Terraform dev before, so please let me know if I can help with anything else or if I'm way off base.
The CONTRIBUTING.md and Makefile were super helpful! I wasn't sure how to get Pulumi to use a forked plugin binary, so I just manually copied the locally built provider binary over the existing resource-libvirt-v0.2.0 binary in ~/.pulumi and that seemed to work to prove the bridge/qemu-agent bug was fixed.

/run-acceptance-tests

@dustinspecker Thanks for the contribution!  Looks good, other than the CHANGELOG issue noted above.  If you push changes, we should be good to go, pending the checks passing.

Thank you for reviewing this!

/run-acceptance-tests

authors: dustinspecker jkodroff

repo: pulumi/pulumi-libvirt


text:
Upgrade Bridge and Pulumi versions. Integrate dependencies from master branch

This PR converges the new main branch with the old master branch.
In preparation for this PR, the v5 branch(with PF changes) was re-named to main.
Then all commits from master (with dependency bumps, modern pulumi and bridge versions) were reconciled with main on this upgrade branch via merge:

update pulumi version
update bridge version
modernize PF code in resources.go
keep all dependency bumps and new pulumi features such as ESC
re-generate schema
re-generate SDKs

After this pull request merges, we will:

make main the default branch for this repository
rename the old master branch to v4
migrate this repository to a patched repository and upgrade the upstream version as per #341., which represents a major upgrade v4 --> v5. (Note that the code in this PR already makes the v5 changes.)

/run-acceptance-tests

/run-acceptance-tests

repo: pulumi/pulumi-tls


text:
Remove mutexes introduced due to concurrency bug

Blocked on resolution of & PR:

https://github.com/pulumi/pulumi/issues/9667
https://github.com/pulumi/pulumi/pull/9675

Updating go.mod to target the branch for now so that this is reviewable.

Updating go.mod to target upstream after this fix was merged.

Totally random, but in cases like this, I always love when it’s possible to “assert” the safety of the concurrent access. Many times when removing a mutex lock, that means you can assert a certain lock is held as a precondition to the method call. Is that sort of thing relevant or possible here?

authors: AaronFriel joeduffy

repo: pulumi/pulumi-yaml


text:
Slideshow functionality - swiping for touch screens

Since 100% of web projects moving forward range from mobile-accessible to fully responsive, slideshows should act accordingly and respond naturally to swipe gestures.
Thoughts?

We primarily use other slideshow players in our own projects. Projector remains a handy proof of concept for those starting up new sites.

authors: boutell tquirino

repo: punkave/apostrophe


text:
test more puppet versions

test for strict-variables and future parser compatibility

3.5 was only released for like 2 weeks ( and was terrible) also while you're here why not remove the 2.7

okay

@nibalizer looks gooder now, but travis isn't picking this repository up, actually :(

squash/force push to make travis pick it up

i'm counting a 1.8.7 failure to due puppet-rspec fuckup as a success.

hits merge button

authors: igalic nibalizer

repo: puppet-community/puppetcommunity-extlib


text:
[Feature]: How to login using netscape cookies(not json) in puppeteer?

Feature description
I'm working on automating a login process using Puppeteer for a website that utilizes Netscape cookies for authentication. I've obtained the necessary Netscape cookies from a previous session and now I want to use them to log in programmatically. However, I'm encountering some difficulties in implementing this process.
Could someone provide guidance or a code example on how to set Netscape cookies in Puppeteer and use them to authenticate a user session? Specifically, I need assistance with the steps to properly set the cookies and navigate through the login flow using Puppeteer.
This code is for json cookies working fine but i want to login using txt netscape cookies
const puppeteer = require('puppeteer');
const fs = require('fs');

(async () => {
const browser = await puppeteer.launch({ headless: false });
const page = await browser.newPage();

try {
// Read cookies from file (assuming cookies.json contains an array of cookie objects)
const cookiesString = fs.readFileSync('C:\\Users\\myuser\\Desktop\\webscraper\\cookies.json');
const cookies = JSON.parse(cookiesString);

// Set each cookie individually
for (const cookie of cookies) {
await page.setCookie(cookie);
}

await page.goto('https://example.com');
} catch (error) {
console.error('Error setting cookies:', error);
} finally {
// Close the browser when done
// await browser.close();
  }
})();

I've tried setting the cookies using the page.setCookie() method and then navigating to the login page but its not working. I want to log in with Netscape cookies
Error: ProtocolError: Protocol error (Network.setCookies): Invalid cookie fields

You need to make sure to provide valid cookie fields to https://pptr.dev/api/puppeteer.page.setcookie/ which might involve parsing attributes from the JSON value and mapping the fields. In general, this is kind of question is better suitable for StackOverflow, please post the question there.

okay thanks i will post question on stackoverflow

repo: puppeteer/puppeteer


text:
[Bug]: Cannot save third-party cookies

Minimal, reproducible example
import puppeteer from 'puppeteer'

(async () => {
const browser = await puppeteer.launch({
    headless: false,
    args: [
      '--disable-features=SameSiteByDefaultCookies,CookiesWithoutSameSiteMustBeSecure',
      '--lang=en-USk',
    ],
  })

const page = await browser.newPage()
await page.goto('https://shopee.com.br')
})()

Background
No response
Expectation
Save third-party cookies
Reality
I opened and logged into website “https://shopee.com.br” but couldn't access it properly because I couldn't save third-party cookies.

After logging in, I cannot access it normally. If I manually set to allow third-party cookies to access, but I don't know how to implement it with code
Puppeteer configuration file (if used)
const {join} = require('path')

/**
 * @type {import("puppeteer").Configuration}
 */
module.exports = {
  // Download Chrome (default `skipDownload: false`).
  chrome: {
    skipDownload: false,
    version: '130.0.6723.116',
  },
  // Download Firefox (default `skipDownload: true`).
  firefox: {
    skipDownload: true,
  },
  cacheDirectory: join(__dirname, '.cache', 'puppeteer'),
};

Puppeteer version
23.9.0
Node version
18.20.2
Package manager
pnpm
Package manager version
9.3.0
Operating system
Windows

Third-party cookies are disabled in Chrome for Testing by default. You can use --disable-features=TrackingProtection3pcd arguments when launching the browser to opt-in into allowed third-party cookies.

I tried the method you provided and it solves the problem, thanks!


text:
Fixed 5 Warnings in src/common/EventContext.ts

when we run the command "npm run generate-docs", we were getting a number of warnings.
5 of which I have solved by introducing minor fixes!!!

@googlebot I signed it!
On Mon, Apr 5, 2021 at 7:00 PM google-cla[bot] @.***>
wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project (if not, look below for help).
Before we can look at your pull request, you'll need to sign a Contributor
License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot
I signed it! and we'll verify it.
What to do if you already signed the CLA Individual signers

It's possible we don't have your GitHub username or you're using a
different email address on your commit. Check your existing CLA data
https://cla.developers.google.com/clas and verify that your email is
set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.

Corporate signers

Your company has a Point of Contact who decides which employees are
authorized to participate. Ask your POC to be added to the group of
authorized contributors. If you don't know who your Point of Contact is,
direct the Google project maintainer to go/cla#troubleshoot (Public
version https://opensource.google/docs/cla/#troubleshoot).
The email used to register you as an authorized contributor must be
the email used for the Git commit. Check your existing CLA data
https://cla.developers.google.com/clas and verify that your email is
set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
The email used to register you as an authorized contributor must
also be attached to your GitHub account
https://github.com/settings/emails.

ℹ Googlers: Go here
https://goto.google.com/prinfo/https%3A%2F%2Fgithub.com%2Fpuppeteer%2Fpuppeteer%2Fpull%2F7057
for more info.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/puppeteer/puppeteer/pull/7057#issuecomment-813393468,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANVCKNA5OKF5GDLAPN6ZXFTTHG3OTANCNFSM42MZ6CWA
.

@anwersayeed hey, I'm sorry but it looks like another PR has fixed these issues already. Thank you though - I appreciate your contribution here. If you have any time to do any other warnings I'll be happy to review those, thanks!

authors: anwersayeed jackfranklin


text:
(BOLT-267) Add ExecutionResult and Target data types to Bolt

This commit adds the ExecutionResult and Target data types to Bolt
and makes them available to Puppet using the new
Puppet::DataTypes#create_type introduced by PUP-8195.
Note! The data types were previously present in Puppet core and this
commit must be synchronized with an upgrade to use a puppet version
where PUP-8265 (covering the removal) has been merged.

May I ask why this is being moved here? Execution result is generally useful outside of bolt for other integrations into the plan DSL. A bolt dependency to get plans working seems undesirable (if I understand the implication right)

The run_plan function has alredy moved into Bolt and with it, the plan DSL. See https://tickets.puppetlabs.com/browse/PUP-8073.

Ah bummer. And bolt is still censoring the entire puppet or is this towards being installable in AIO ?

Vendoring. Sorry can’t edit on mobile github

@ripienaar all of the puppet feature branch changes have been merged back into puppet#master, and that will be released as puppet 5.4.0 in January-ish. So bolt will be able to stop vendoring puppet "real soon now".

@joshcooper yes was really looking forward to 5.4 so I can realesse my plan integrations as well as my task runner.
Looks like I can finish task runner but with the plan function and results type gone that’s a dead stop to anything that want to build on the plan DSL - arguably the most interesting aspect of the new features in Puppet.
Anyway there also seem some disagreement between this and what Alex said on slack either that or it’s a case of can but won’t for a few months more :(

CLA signed by all contributors.

@joshcooper moving off of the feature branch is a necessary but not sufficient condition for undvendoring puppet. Bolt is still moving fast and will continue to require changes in puppet. We may not want to be blocked on puppet's release cycle. Users have expressed concern about installing the latest puppet vendoring removes this concern. I don't think we're quite done with vendoring.

This needs a rebase.

Rebased.

Looks like some rubocop work needed, as well as changes to how we reference ExecutionResult from the modules/boltlib spec tests.

Apparently we've deleted feature_puppet-tasks, so .gitmodules will need an update.
Also, whatever code vendored/puppet points to isn't on puppetlabs/puppet, so I can't update to it.

I'm actually confused how specs work but I'm not able to get submodules setup.

authors: MikaelSmith adreyer joshcooper puppetcla ripienaar thallgren

repo: puppetlabs/bolt


text:
(hack) fail fast

Adding --fail-fast to spec tests allows Bolt to fail faster and provide
opportunity for quicker feedback.
!no-release-note

Ah, you'll want to do:
git fetch upstream
git rebase upstream/main
git rebase -i HEAD~2 # then delete the first commit
git push -f origin hack/fail_fast

authors: artlawson lucywyman


text:
(maint) Properly configure bundler in bolt-server build

Previously we were setting bundler config options at the user level in
the build container, which meant they didn't get copied over to the
runtime container. That caused gems not to be found at runtime. We now
set them in the local .bundle/config file so they get copied over to the
final build.

I believe the reason this was missed during local development is that a local .bundle/config will be copied into the container, so if you already have BUNDLE_PATH set in that config, it just works.


text:
private key location - README does not match the PE docs

The docs for this repo say to place the private key at:

/etc/puppetlabs/puppetserver/code_manager.key

And the PE docs at https://docs.puppetlabs.com/pe/latest/cmgmt_control_repo.html say this:

After PE installation is complete, place this private key in a location that the pe-puppet user can access; we recommend /etc/puppetlabs/puppetserver/ssh/id-control_repo.rsa. The file itself should have the correct permissions for the pe-puppet user, which is created during PE installation, to use that key.

@robbyt The location of the key and it's name doesn't matter for functionality but I assume you are simply pointing out that this is inconsistent.
I would say it doesn't matter but I do appreciate the clarity of having an ssh directory under the puppetserver directory instead of just placing the key in the puppetserver directory like I did.
If I change the name/location of the key I'll need to remove the old private and public key as well as check the behavior of the git_deploy_key to make sure it correctly replaces the existing deploy key instead of creating a new deploy key and leaving the old one around.

@npwalker I understand that the location is configurable. Just pointing out the inconsistency between the two documentation sources. We just want to know the one "true way" to configure code-manager :)

@robbyt this should be resolved by the merge of https://github.com/puppetlabs/control-repo/pull/22

authors: npwalker robbyt

repo: puppetlabs/control-repo


text:
MCO-555 Add AIO variants of init and sysconfig files

The All-In-One Agent configures MCollective with a specific set of
paths for configurations and pidfiles.
Here we take the work of Geoff Nichols from PR#274 and moves it
into ext/aio, where the All-In-One build process can consume the
files.

CLA signed by all contributors.

:+1:

authors: geoffnichols puppetcla richardc

repo: puppetlabs/marionette-collective


text:
Legacy fact check should detect/remediate unscoped legacy facts.

This spec test validates that an unscoped fact like $osfamily is not detected or remediated. I think that it should be detected, especially in context of Puppet 8 deprecating those facts.
This means that people writing code that shadows those legacy facts by using the same variable name will now trigger a warning. If they genuinely want to do that, then they can configure the linter to skip that code 😁
@joshcooper @bastelfreak

Already picked up by http://puppet-lint.com/checks/variable_scope/ surely?

@alexjfisher I think that it should still correct this. If the user dislikes that style and disables that check, the legacy fact check should still identify known obsoleted facts.

I agree that legacy_facts should detect this, also in order for --fix to correct these. It will save a lot of people a lot of time.

authors: alexjfisher binford2k fbhdk

repo: puppetlabs/puppet-lint


text:
(PUP-3806) Add missing support for interpolation in collection

The support for double quoted (interpolated) strings were
missing in the new implementation of collectors introduced in
PUP-2906.This was not detected since there is a parser optimization
that treats double quoted strings that does not require
interpolation as literal strings and there were no tests
that included double quited strings with interpolation of an expression.
This commit adds support for concatenated string (i.e. interpolation).

CLA signed by all contributors.

authors: hlindberg puppetcla

repo: puppetlabs/puppet


text:
(QENG-1800) Install MSI during package acceptance

Previously it was not possible to run windows acceptance against FOSS
MSI packages. This commit adds a step to install the puppet-agent MSI. It
depends on https://github.com/puppetlabs/beaker/pull/674
With this commit you can do:
$ bundle exec rake ci:test:packages \
    CONFIG=config/nodes/win2008r2-rubyx64.yaml \
    SHA=<SHA> VERSION=3.7.4-1303

Note the VERSION string must match the filename of the MSI which
includes the output from git describe. The host definition file needs
to specify which ruby_arch it wants to install, either x86 or x64.

Out of curiosity, is there not a way to correlate a VERSION to a SHA without having to supply both?
I had to look at the code to figure out what SHA is used for.... and as it turns out, it looks like there's only ever a single x86 and single x64 MSI in the artifacts directory for a given SHA

It is possible to do git describe <SHA> and then strip out the short git:
$ git describe HEAD^1
3.7.4-1307-ge91e31f

But that requires that you have the commit in your current branch... We must do this somewhere else? /cc @haus @melissa

CLA signed by all contributors.

You may want to target this work also at the acceptance/setup/aio folder.

@justinstoller good point. I was hoping to get testing against packages working in puppet/master before the uber puppet PR is merged. Then look at AIO as a second step.

@Iristyle I talked with @haus about parsing the YAML to get the version and he said the AIO pipeline is not creating this file currently. And it would probably be easier for the pipeline to do a git describe at the beginning, strip the commit, and pass the version through. I'm thinking we come back to this issue, so the caller doesn't need to specify VERSION

Plan is to:

Modify the MSI packaging job to use git describe of puppet-agent in the package name, see https://github.com/puppetlabs/packaging/pull/374
Modify the AIO pipeline to include the PROJECT_VERSION as a build parameter, which will match the above.
Modify this PR to use the PROJECT_VERSION by default, but allow an alternate version to be specified on the command line.

I think we want to retarget this at the aio branch?

authors: Iristyle joshcooper justinstoller puppetcla


text:
(PUP-4527) Add MigrationChecker method to provide available migrations

Befoe this, reflection had to be used to see what a version of a
MigrationChecker implements.
This is now changed so all versions of puppet after 3.8.0 has a method
that returns the migration checks that are implemented. This makes it
possible to have newer versions of the migration checker support older
versions of puppet (>= 3.8.0).

CLA signed by all contributors.


text:
(PUP-8922) update permision for state files

This commit updates de default permisions for
state.yaml and transactionstore.yaml in order
to remove group write access.

jenkins please test this with servertests

CLA signed by all contributors.

jenkins please test this with servertests

authors: gimmyxd joshcooper puppetcla


text:
(NPUP-24) Fix environment manifest search to be recursive.

This fixes the manifest setting, when a directory (which is the default), to
recursively search for manifests in a deterministic order.
This commit removes the logic in the environment for searching for manifests
and consolidates the logic into the finder class.

Hm, this made me realize we have a problem with how to represent the recursive site.pp - the ruby impl searches and parses each file, it then creates an instance that when evaluated will evaluate all of the in the given order. Having an .xpp for each file does not seem ideal (it will work though).

@peterhuene do you want to address the "use C locale" in this PR, or as a new ticket? This is fine to merge if you want a separate ticket.

I'll push up a fix to this PR.

Updated.

i added a PUP ticket for the spec work.

authors: hlindberg peterhuene

repo: puppetlabs/puppetcpp


text:
Error creating ec2 instance

Hi
im getting the error below when im trying to create an ec2 instance ? any ideas on whats the problem ?
[root@tocwcds5ic aws]# puppet apply create.pp
Notice: Compiled catalog for tocwcds5ic.bns in environment production in 0.16 seconds
Notice: /Stage[main]/Main/Ec2_securitygroup[lb-sg]/ensure: created
Notice: /Stage[main]/Main/Ec2_securitygroup[web-sg]/ingress: ingress changed [] to '{"security_group"=>"lb-sg"} {"protocol"=>"tcp", "port"=>22, "cidr"=>"0.0.0.0/0"}'
Error: Security groups 'web-sg' not found in VPCs 'vpc-88cadded'
Error: /Stage[main]/Main/Ec2_instance[web-1]/ensure: change from absent to present failed: Security groups 'web-sg' not found in VPCs 'vpc-88cadded'
Notice: Applied catalog in 36.30 seconds
`# This will create a set of instances, load balancers and security groups in the
specified AWS region.
Ec2_securitygroup {
region => 'sa-east-1',
}
Ec2_instance {
region            => 'sa-east-1',
availability_zone => 'sa-east-1a',
}
Elb_loadbalancer {
region => 'sa-east-1',
}
ec2_securitygroup { 'lb-sg':
ensure      => present,
description => 'Security group for load balancer',
ingress     => [{
protocol => 'tcp',
port     => 80,
cidr     => '0.0.0.0/0'
}],
}
ec2_securitygroup { 'web-sg':
ensure      => present,
description => 'Security group for web servers',
ingress     => [{
security_group => 'lb-sg',
},{
protocol => 'tcp',
port     => 22,
cidr     => '0.0.0.0/0'
}],
}
ec2_instance { ['web-1']:
ensure          => present,
image_id        => 'ami-67a60d7a', # EU 'ami-b8c41ccf',
security_groups => ['web-sg'],
instance_type   => 't1.micro',
tags            => {
department => 'engineering',
project    => 'cloud',
created_by => $::id,
}
`

Hi hesamaseh, which version of puppet are you using ?

Hi hesamaseh, I'm getting the same error as you. Have you been able to find a solution?
Sagrahari1, I did a fresh new standalone install in order to try the puppetlabs-aws modules. I'm running a clean version of CentOs 7.2 with puppet 3.8.7 and all the updates installed. I followed the installation instructions and installed aws-sdk-core, retries and the puppetlabs-aws module.
So when I tried a simple ec2 instance creation with my AWS credentials export, I got the following error message:
Notice: Compiled catalog for ip-172-31-49-17.ec2.internal in environment production in 0.03 seconds
WARNING: jmespath gem requires json gem >= 1.8.1; json 1.7.7 already loaded
Error: Security groups 'default' not found in VPCs 'vpc-0e038a6b'
Error: /Stage[main]/Main/Ec2_instance[my-instance-name]/ensure: change from absent to present failed: Security groups 'default' not found in VPCs 'vpc-0e038a6b'
Notice: Finished catalog run in 1.02 seconds

The content of the manifest file is:
ec2_instance { 'my-instance-name':
  ensure        => present,
  region        => 'us-east-1',
  image_id      => 'ami-d97897b4',
  instance_type => 't2.micro',
}

When I try the stack test example, I'm able to create all the security groups but not instances. Here is the output error:
Notice: Compiled catalog for ip-172-31-49-17.ec2.internal in environment production in 0.08 seconds
WARNING: jmespath gem requires json gem >= 1.8.1; json 1.7.7 already loaded
Notice: /Stage[main]/Main/Ec2_securitygroup[lb-sg]/ensure: created
Notice: /Stage[main]/Main/Ec2_securitygroup[web-sg]/ensure: created
Error: Security groups 'web-sg' not found in VPCs 'vpc-0e038a6b'
Error: /Stage[main]/Main/Ec2_instance[web-2]/ensure: change from absent to present failed: Security groups 'web-sg' not found in VPCs 'vpc-0e038a6b'
Error: Security groups 'web-sg' not found in VPCs 'vpc-0e038a6b'
Error: /Stage[main]/Main/Ec2_instance[web-1]/ensure: change from absent to present failed: Security groups 'web-sg' not found in VPCs 'vpc-0e038a6b'
Notice: /Stage[main]/Main/Elb_loadbalancer[lb-1]: Dependency Ec2_instance[web-1] has failures: true
Notice: /Stage[main]/Main/Elb_loadbalancer[lb-1]: Dependency Ec2_instance[web-2] has failures: true
Warning: /Stage[main]/Main/Elb_loadbalancer[lb-1]: Skipping because of failed dependencies
Notice: /Stage[main]/Main/Ec2_securitygroup[db-sg]/ensure: created
Error: Security groups 'db-sg' not found in VPCs 'vpc-0e038a6b'
Error: /Stage[main]/Main/Ec2_instance[db-1]/ensure: change from absent to present failed: Security groups 'db-sg' not found in VPCs 'vpc-0e038a6b'
Notice: Finished catalog run in 5.60 seconds

Any help would be appreciate

I think its a bug, just make sure all your components ( eg security group, vpc, ... ) have the name Tag filled in.

@daveside, there is a bug with ec2_instance. though it says optional but it expects "subnet" to be passed. Try with passing "subnet" parameter.

Thank you very much. It is finally working with the subnet parameter with a name specified. Note: before using the script, I set the name of all the subnet manually using the AWS dashboard.
ec2_instance { 'my-instance-name':
  ensure        => present,
  region        => 'us-east-1',
  image_id      => 'ami-d97897b4',
  instance_type => 't2.micro',
  subnet        => 'subnet-us-east-1',
}

@daveside Hey, glad you find an answer, I've tried the same solution by providing the Name of the subnet I have made manually through AWS dashboard, but I am still getting the same error
Error: Security groups 'bnpl-web-tier-to-elb' not found in VPCs 'vpc-xxxxxxxx'
Any help is appreciated.

Please let me know how can solve this issue?.

authors: Skyish-me daveside hesamaseh sagrahari1 smdanzar

repo: puppetlabs/puppetlabs-aws


text:
Integrate with existing Bolt Inventory

Focus on interactive approach to interacting with Bolt targets rather than script-driven.

Easier to read logs across a variety of systems.
Pre-configured direct filesystem access.
Copy files between systems.

Add a new plugin that reads an existing Bolt inventory and presents items in that inventory as a hierarchy you can navigate.

Explore that inventory with Wash. Entries should include any information in the inventory as metadata.
Hierarchy could have: organize by groups and subgroups. Nodes not in a group are in an implicit all group, but that encompasses everything, so we should probably have a special group name for these.
Implement SSHFS over that inventory.

Initial plan is to implement as an external Ruby plugin.
Related improvements: parallel wash exec.

Could use signal for other Bolt actions not captured by Wash primitives like run_script, run_plan, etc, though we'd need to extend signal to support all of that.

I think that's a different facet of this, more aligned with #249.

Be careful not to pull in puppet as a dependency when loading Bolt as a library. Also, we can likely pre-compute the entire hierarchy the first time we run list.

authors: MikaelSmith ekinanp

repo: puppetlabs/wash


text:
系统管理/部门列表数据格式

描述问题 (Describe the problem)
你好作者，非常抱歉，又以这种方式打扰，看了源码，说的是

// 这里是返回一维数组结构，前端自行处理成树结构，返回格式要求：唯一id加父节点parentId，parentId取父节点id

按照说明返回数据了，显示了内容，但是并没有自动生成结构树。
服务器返回数据格式如下：
[
  {
    "department_id": 1,
    "department_status": 0,
    "department_title": "重庆总公司",
    "department_rank": 0,
    "employee_id": 1,
    "department_phone": "18875035736",
    "department_email": "kanshitech@gmail.com",
    "department_p_department": 0,
    "department_remark": "XX信息科技有限公司重庆总公司",
    "created_at": "2023-07-10 16:24:10",
    "updated_at": "2023-07-10 16:24:10",
    "deleted_at": null,
    "type": 1,
    "id": 1,
    "parentId": 0,
    "sort": 0,
    "employee": [
      {
        "employee_id": 1,
        "employee_status": 0,
        "employee_name": "系统管理员",
        "employee_phone": "18875035736",
        "employee_roles": "[\"admin\"]",
        "gender_id": null,
        "nationality_id": null,
        "education_background_id": null,
        "national_identification_number": null,
        "department_id": null,
        "subsidiary_id": null,
        "employee_last_login_time": null,
        "created_at": "2023-07-07T05:23:18.000000Z",
        "updated_at": "2023-07-07T05:23:18.000000Z",
        "deleted_at": null
      }
    ]
  },
  {
    "department_id": 2,
    "department_status": 0,
    "department_title": "开发部",
    "department_rank": 200,
    "employee_id": 1,
    "department_phone": "18523555736",
    "department_email": "1037067594@qq.com",
    "department_p_department": 1,
    "department_remark": "软件开发部",
    "created_at": "2023-07-10 16:27:19",
    "updated_at": "2023-07-10 16:27:19",
    "deleted_at": null,
    "type": 2,
    "id": 2,
    "parentId": 1,
    "sort": 200,
    "employee": [
      {
        "employee_id": 1,
        "employee_status": 0,
        "employee_name": "系统管理员",
        "employee_phone": "18875035736",
        "employee_roles": "[\"admin\"]",
        "gender_id": null,
        "nationality_id": null,
        "education_background_id": null,
        "national_identification_number": null,
        "department_id": null,
        "subsidiary_id": null,
        "employee_last_login_time": null,
        "created_at": "2023-07-07T05:23:18.000000Z",
        "updated_at": "2023-07-07T05:23:18.000000Z",
        "deleted_at": null
      }
    ]
  },
  {
    "department_id": 3,
    "department_status": 0,
    "department_title": "财务部",
    "department_rank": 300,
    "employee_id": 1,
    "department_phone": "18666222428",
    "department_email": "23031433@qq.com",
    "department_p_department": 1,
    "department_remark": "管理账务的财务部",
    "created_at": "2023-07-10 16:27:19",
    "updated_at": "2023-07-10 16:27:19",
    "deleted_at": null,
    "type": 2,
    "id": 3,
    "parentId": 1,
    "sort": 300,
    "employee": [
      {
        "employee_id": 1,
        "employee_status": 0,
        "employee_name": "系统管理员",
        "employee_phone": "18875035736",
        "employee_roles": "[\"admin\"]",
        "gender_id": null,
        "nationality_id": null,
        "education_background_id": null,
        "national_identification_number": null,
        "department_id": null,
        "subsidiary_id": null,
        "employee_last_login_time": null,
        "created_at": "2023-07-07T05:23:18.000000Z",
        "updated_at": "2023-07-07T05:23:18.000000Z",
        "deleted_at": null
      }
    ]
  }
]

且也按照demo设置了相关属性，pure-table相关属性设置如下
<pure-table
          ref="tableRef"
          border
          adaptive
          :adaptiveConfig="{ offsetBottom: 32 }"
          align-whole="center"
          row-key="id"
          showOverflowTooltip
          table-layout="auto"
          default-expand-all
          :loading="loading"
          :size="size"
          :data="listData"
          :columns="dynamicColumns"
          :header-cell-style="{
            background: 'var(--el-table-row-hover-bg-color)',
            color: 'var(--el-text-color-primary)'
          }"
          @selection-change="handleSelectionChangeMethod"
        />

如何复现该问题 (How to reproduce the problem)
无需复现
操作系统和浏览器信息 (Operating system and browser information)
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Edg/114.0.1823.82
验证 (Verify)

[X] 是否仔细阅读过 文档 (Have you read documentation carefully)
[X] 检查是否存在相同或类似的问题 issues (Check for the same or similar issues)

返回按照这种格式 https://github.com/pure-admin/vue-pure-admin/blob/main/src/views/system/dept/utils/hook.tsx#L77
然后用前端 handleTree 方法处理成树

https://github.com/pure-admin/vue-pure-admin/blob/main/src/views/system/dept/utils/hook.tsx#L77

谢谢大佬，大佬威武~~~

repo: pure-admin/vue-pure-admin


text:
Pcm 2024

This one is a doozy... Sorry.

Some notes about the changes I made:

When streamingClient wants to connect an instance of stanza, it will do so by calling connectionManager.getNewStanzaConnection(). This call will only resolve if stanza connects successfully. If the connection fails or times out, it will reject.

streamingClient will keep calling connectionManager.getNewStanzaConnection() until it gets a connected instance at which time it will associate that instance as the activeStanzaInstance and pass it to all of its extensions so they can setup/react to a new stanza instance.

once streamingClient has an activeStanzaInstance, it will set up a disconnected listener against that instance. If the instance becomes disconnected and streamingClient.disconnect() was never called, we assume the disconnect was unintentional and we will connect a new instance as if one never existed. (basically start at the first bullet point). This allows us to treat reconnected stanza instances the same as if it was an initial connection.

Because of the above mentioned bullets, we were able to remove the reconnector extension.


text:
Ace.ace undefined

Describe the bug
Using purescript-ace v8.0.0, running the following code, crashes immediately, the error message being self is undefined (same on firefox an google chrome), where self is the second argument of editNodeImpl.
  editor <- Ace.editNode element Ace.ace

Hi @rubenmoor, thanks for reporting this! Just a couple questions to help narrow things down:

What version of Ace (the JS library) do you have installed?
How are you including Ace (the JS library) in your code? Is it via a bundler, like Webpack or Parcel? Are you using a <script> tag pointing to a CDN?
Does this also happen on Ace v7.0.0?

Hopefully we can narrow this down and get it working for you!

authors: rubenmoor thomashoneyman

repo: purescript-contrib/purescript-ace


text:
update NSData Extension

        let signature = NSData.withBytes(hmac!).hexString

should be
let signature = NSData.withBytes(hmac!).toHexString
PusherSwift.swift : Line 373
Cannot compile unless this is fixed

/cc @hamchapman

I'll update this today. Thanks for the spot

You havent updated your Podspec, currently it still looks for hexString

authors: andyyhope hamchapman zimbatm

repo: pusher-community/pusher-websocket-swift


text:
Performance and reliability improvements

## Added

Performance and reliability improvements.

Changed

registerDeviceToken(_ deviceToken:, completion:) to func registerDeviceToken(_ deviceToken:)
addDeviceInterest(interest:, completion:) to func addDeviceInterest(interest:)
setDeviceInterests(interests:, completion:) to func setDeviceInterests(interests:)
removeDeviceInterest(interest:, completion:) to func removeDeviceInterest(interest:)
stop(completion: @escaping (Error?) -> Void) to func stop(completion: @escaping () -> Void)
clearDeviceInterests(completion:) to func clearDeviceInterests()
clearAllState(completion: @escaping (Error?) -> Void) to clearAllState(completion: @escaping () -> Void)

Removed

subscribe(interest:, completion:)
setSubscriptions(interests:, completion:)
unsubscribe(interest: String, completion:)
unsubscribeAll(completion:)
getInterests()
interestsSetDidChange()
interestsSetDidChange(interests:)

CC @pusher/mobile

Codecov Report

Merging #113 into master will increase coverage by 12.95%.
The diff coverage is 92.43%.

@@             Coverage Diff             @@
##           master     #113       +/-   ##
===========================================
+ Coverage   78.88%   91.84%   +12.95%
===========================================
  Files          38       49       +11
  Lines        1511     2439      +928
===========================================
+ Hits         1192     2240     +1048
+ Misses        319      199      -120

Impacted Files
Coverage Δ

Tests/Persistence/DeviceTests.swift
100% <ø> (ø)

Tests/Persistence/UserPersistableTests.swift
100% <ø> (ø)

Tests/Persistence/InterestPersistableTests.swift
100% <ø> (ø)

Tests/IntegrationTests/ReportEventTypeTests.swift
100% <100%> (ø)

Sources/Persistence/Instance.swift
100% <100%> (ø)

Sources/Persistence/DeviceStateStore.swift
100% <100%> (ø)

Tests/SDKTests.swift
100% <100%> (ø)
:arrow_up:

Sources/API/RetryStrategy.swift
100% <100%> (ø)

Sources/Persistence/Metadata.swift
100% <100%> (ø)

Sources/Persistence/Device.swift
100% <100%> (ø)

... and 37 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ea9c3b3...ab0383f. Read the comment docs.

authors: codecov-io lukabratos

repo: pusher/push-notifications-swift


text:
🛑 SISTER is down

In d31e169, SISTER (https://sister.unmer.ac.id/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SISTER is back up in 1cf18c6 after 9 minutes.

repo: pusimgit/upptime


text:
resolve react-moment?

Is there any trick to this?
./node_modules/react-live-clock/lib/Component.js
Module not found: Can't resolve 'react-moment' in '/Users/nolan/clock/node_modules/react-live-clock/lib'

I'm following documentation/ youtube and seem to keep runing into this...

I'm so sorry. I c&p the wrong console error this this the error I am referring to...
./node_modules/react-live-clock/lib/Component.js Module not found: Can't resolve 'moment-timezone' in '/Users/nolan/scratch-react/node_modules/react-live-clock/lib'

I'm so sorry. I c&p the wrong console error this this the error I am referring to...
./node_modules/react-live-clock/lib/Component.js Module not found: Can't resolve 'moment-timezone' in '/Users/nolan/scratch-react/node_modules/react-live-clock/lib'

You need to have this module installed yarn add moment-timezone or npm install moment-timezone

You need to have this module installed yarn add moment-timezone or npm install moment-timezone

Ye this is a bug it ought to be in dependencies , not peer dependencies

it was to fix a problem with the build size ( #40 ).
the dependencies go in the peer dependencies so that you can have the version you want and the build will be lighter.

it means we now have moment and moment-timezone though...

I think the problem is that some of the peer deps are locked down too tight.
This is the only package I have ever maintained, and I am doing my best.
@Nolanws1, @damiangreen could you please take a look at
https://nodejs.org/en/blog/npm/peer-dependencies
I moved them to peer deps so the package was smaller on build, I don't know why they are not automatically installing or at least giving an error telling you to install

It also appears it depends on @types/moment-timezone
This package is marked as unneeded by PnPm

@damiangreen  what do you suggest I do?

I made some changes I hope it helps

repo: pvoznyuk/react-live-clock


text:
Freeze and reboot

Hi bro must comment with you that a few minutes ago i did rootfs, did semirestore rollectra to turn iphone factory default rejailbreak without install any tweak, installed substrate and with Phone charging when i open cydia while refresh repos iphone freeze and reboot it happens to me 2 times with the same symptons exactly the same, m37 user told me yesterday the same while charging.thanks in advance

Im on 6s plus 11.3.1 unc0ver last version from this GitHub

@nosbourg try using v 2.0.2, i have used for 7 days v 2.0.2 on 6s 11.2.6 no random reboot or freezing
In v 2.1.0 it's not ready for production the label is pre-release

@nosbourg, I was having the same issue with cydia with the new substrate and v 2.1.0. I installed NoSub /w paypal and set cydia in the options. My freezing stopped once I did that. Don't know if it will help you or not, but it helped me.

@nosbourg, I was having the same issue with cydia with the new substrate and v 2.1.0. I installed NoSub /w paypal and set cydia in the options. My freezing stopped once I did that. Don't know if it will help you or not, but it helped me. I am on a 6s 11.2.6, btw...

I renamed the vsd daemon and it solved my cydia freezes. I was having the exact same problem with cydia freezing and rebooting when refreshing sources. Once I remaned the vsd daemon, it stopped.

Thx will do that now ...
Got freezes already 5-6 times in 2 days ...

you have to reboot and re-jailbreak afterwards. I just renamed it to videosupscriptionsd.bak in /usr/libexec

Yes I did thx

It’s fixed for me... since I renamed vsd the freezing while refreshing sources has stopped.

@nosbourg try using v 2.0.2, i have used for 7 days v 2.0.2 on 6s 11.2.6 no random reboot or freezing
In v 2.1.0 it's not ready for production the label is pre-release

Hey lucky man, that's great for somebody who is trying things become fix again, sometimes feel sad in choosing known/unknown options, however, I am such a fan of breaking tools but unfortunately there was no luck, I wonder if your options, where the right fit setup in the Settings button which one to check on/off for having the usability like yours.
Let me write what I can see now happening:

@pwn20wndstuff @iM4CH3T3

Thx for your help guys havent got any freeze reboot since update to las unc0ver and substrate👌👍


text:
ERROR (FATAL) Errno 2: Failed to copy over our resources to RootFS

Describe the bug
Simply tried running LdRestart on device...device rebooted back into stock mode (not JB state)...went into unCover to Jailbreak again...and go this error.
Tried to Recover RootFS, which was successful, then phone restarted like it usually does, opened unc0ver to continue to process...and now I keep getting this error.
To Reproduce
Steps to reproduce the behavior:

LdRestart
Try to jailbreak

Screenshots
If applicable, add screenshots to help explain your problem.

Device (please complete the following information):

iOS Version: 12.1.1
iOS Device: iPhone X
unc0ver Version: v3.0.0 beta 41

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce
[x] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[x] this issue is present after a rootfs restore
[x] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.
diagnostics.plist.zip

SOLVED!
Simply, Remove unC0ver application from Homescreen (like you would remove any application) and simply redownload it.
And Jailbreak
(I did Recover RootFS earlier trying to fix this error, soo I dont know if that was needed to fix the issue or not, soo attempt too delete & reinstall before attempting Recover RootFS)
Goodluck

Please close if solved @Oxycodon-IV

authors: Oxycodon-IV WalshyDev


text:
error 30 Failed to remount RootFS

I have been getting this error
Errno: 30
Test: spawnAndShaihuludAndWait("/sbin/mount_apfs","/dev/disk0s1s1","/var/tmp/rootfsmnt", NULL, NULL, NULL) == 0
Filename: ViewController.m
Line: 1575
Function: exploit
Description: Failed to remount RootFS
downloaded unc0ver(proper) from ignition
IOS 11.1 Model Iphone 6s
Stuck in 21/53

@WinstonDT please spell iPhone correctly next time. It's iPhone not Iphone. Also can you post your diagnostics.plist, there's a button in the settings page of unc0ver.

authors: Cryptiiiic WinstonDT


text:
Publish 4.1.0

Changes proposed in this Pull Request:

UserMenu component
MobileStepper component
Miscellaneous fixes

Whenever this button is pressed the npm auto-publish logic will run for the first time.

repo: pxblue/react-native-component-library