text:
docs: Add auto-generated page for current metrics Prometheus exposes about itself.

Proposal
It would be amazing to have list of exact metric names and their help that Prometheus gives about itself. This is common for many products that expose Prometheus metrics, so would be nice to have Prometheus ones too (e.g head compactions). Perhaps we could expand on each HELP to tell more.
Extra: Have it autogenerate from source code would be amazing, so it's not requiring manual changes (or validation) on every PR.

A quick hack is to give link to demo instance: https://prometheus.demo.do.prometheus.io/metrics

Hi @bwplotka  I'd like to work on this issue (#12397). Can you assign the issue to me? Thanks!

Hi @bwplotka, I can work on this issue.

@bwplotka I would like to work on this can you give some more information

Sure, help wanted. We don't assign issues, so anybody is free to make PR, no need to ask for permission. The fact PR was made with the link to this issue will show others that the issue is worked on. 🤗
Let us know what "more information" mean. What questions do you have?
Note that no Prometheus maintainer (other than me), commented or shared opinion on this one, so it's unsure yet if we want that.

Sure, help wanted. We don't assign issues, so anybody is free to make PR, no need to ask for permission. The fact PR was made with the link to this issue will show others that the issue is worked on. 🤗
Let us know what "more information" mean. What questions do you have?
Note that no Prometheus maintainer (other than me), commented or shared opinion on this one, so it's unsure yet if we want that.

Hi @bwplotka, I am working on this issue, I have the list of Prometheus metric names and the TYPE/HELP Prometheus gives about the metrics, please find a screenshot attached. However, I don't understand how I can add an auto-generated page for the metrics from the source code(if more light can be shed on that); what I intend to do is document the metrics per category(service discovery, TSDB, targets, etc) in a metrics.md file in the prometheus/docs directory.

https://github.com/yeya24/promlinter
This is the tool that can be used to grab metric name, help, labels, etc from source code and generate markdown. However, it doesn't work well for those dynamically generated metrics I think.

Thanks for your response @yeya24; I have looked into promlinter and like you highlighted its use case doesn't work for this scenario, as it doesn't capture metrics at runtime likewise at /metrics as seen here and here.
I am generating the dynamic metrics via a specific URL of the Prometheus Demo Instance which populates a list of which i am able to filter prometheus specific metrics(160 in number, i have verified these metrics accordingly by deepdiving into the source code) from it and I intend to document the prometheus metrics manually in a metrics.md file categorically; Going forward, this won't be auto-populated/generated in docs meaning if metrics are updated later the metrics.md has to be updated as well.
PS: I did the same manual documentation for [Thanos components metrics](https://github.com/thanos-io/thanos/pull/7522, https://github.com/thanos-io/thanos/pull/7533, https://github.com/thanos-io/thanos/pull/7535) recently, given promlinter couldn't capture its use case as well.
Please see this when available @bwplotka.

Sounds good enough for a start. From source I meant perhaps some static analysis but let's see if needed.

On static analysis, the promlinter tool is a use case but as discussed it does not capture all metrics; I have opened a PR of the documented metrics.

I am generating the dynamic metrics via a specific URL of the Prometheus Demo Instance which populates a list

I am sure this way doesn't capture all metrics as well. If a specific metric (like a counter) doesn't initialize its value until it is triggered, for example some corruption metrics disappear from /metrics until some real TSDB corruption happens.
That being said, I think either way has its own drawback. We can start with whatever that works for you.

I am generating the dynamic metrics via a specific URL of the Prometheus Demo Instance which populates a list

I am sure this way doesn't capture all metrics as well. If a specific metric (like a counter) doesn't initialize its value until it is triggered, for example some corruption metrics don't show up from /metrics until some real TSDB corruption happens. Similar reason applies to some service discovery provider metrics if a SD type is not in use so its metrics won't show up.
That being said, I think either way has its own drawback. We can start with whatever that is easier for you.

This is the URL:https://prometheus.demo.do.prometheus.io/api/v1/metadata, I might be wrong but I believe it captures all metrics reason being I checked each metric listed on the URL against the source code one by one and it aligns.
I have an opened a PR for the prometheus specific metrics on  #14487.

@TomiwaAribisala-git
I don't think /api/v1/metadata captures all metrics. It basically contains metrics exposed from Prometheus' own /metrics. So if a metric is not exposed during runtime for some reason, then it is not included in the list.
For example, I checked some service discovery metrics and I don't think they are included. https://github.com/prometheus/prometheus/blob/main/discovery/metrics_k8s_client.go#L64

@TomiwaAribisala-git I don't think /api/v1/metadata captures all metrics. It basically contains metrics exposed from Prometheus' own /metrics. So if a metric is not exposed during runtime for some reason, then it is not included in the list.
For example, I checked some service discovery metrics and I don't think they are included. https://github.com/prometheus/prometheus/blob/main/discovery/metrics_k8s_client.go#L64

@yeya24 I see, thanks for clarifying; the PR I opened has only PROMETHEUS SPECIFIC METRICS which I think the issue was about, but to compile ALL METRICS which is not PROMETHEUS SPECIFIC(given static analysis and api/v1/metadata does not capture all metrics) I can deepdive into the source code to compile the list including the one you highlighted, I await your opinion.
@bwplotka.

I like this idea, yea.
However, I think there is a room to go even further long term, by... perhaps leveraging Otel semconv tooling for defining metrics. We plan to design something with @vesari around this.

authors: TomiwaAribisala-git akshayamadhuri bwplotka cloudnativeau codewdhruv yeya24

repo: prometheus/prometheus


text:
Feature Flag "Created Timestamps Zero Injection" requires enabled "Native Histograms"

What did you do?
If you activate the feature flag --enable-feature=created-timestamp-zero-ingestion in Prometheus, you must also activate the feature flag --enable-feature=native-histograms, otherwise the following error message will appear when you scrape your own Prometheus metrics (:9090/metrics):

I don't know if this is intentional, but otherwise it should be documented as a dependency in the documentation?
What did you expect to see?
No response
What did you see instead? Under which circumstances?
Error: native histograms are disabled
System information
No response
Prometheus version
prometheus, version 2.51.2 (branch: HEAD, revision: b4c0ab52c3e9b940ab803581ddae9b3d9a452337)
  build user:       root@b63f02a423d9
  build date:       20240410-14:05:54
  go version:       go1.22.2
  platform:         linux/amd64
  tags:             netgo,builtinassets,stringlabels

Prometheus configuration file
No response
Alertmanager version
No response
Alertmanager configuration file
No response
Logs
No response

Thanks for the report.
Yes, IIUC, that shouldn't be required.
This looks like a regression for https://github.com/prometheus/prometheus/pull/12733 (I tested with the PR's code and the error wasn't there)

Running a binary search:
git bisect start 4a6f8704efcabfe9ee0f74eab58d4c11579547be 5082655392fe2eb036f24da51b54ca050496368a
git bisect run bash -c '
make common-build
./prometheus --enable-feature=created-timestamp-zero-ingestion > /dev/null 2>&1 &
PPPID="$!"
sleep 15
last_error=$(curl -s "http://localhost:9090/api/v1/targets" | jq -er ".data.activeTargets[0].lastError")
if [ -z "$last_error" ]; then
    echo "lastError is empty."
else
    echo "lastError contains: $last_error"
    kill -9 $PPPID
    exit 13
fi
kill -9 $PPPID
'

returns https://github.com/prometheus/prometheus/pull/13681/commits/4d4d822c36b7fdda555aec124eb7b031ed0daa6b as the first bad commit.
But that commit only adds come native histograms metrics into prometheus'. I think https://github.com/prometheus/prometheus/pull/12733 was already broken for native histograms metrics.

Thanks for reporting!
Yea, it seems proto parsing with native histograms assumes native histograms being enabled in the Prometheus storage, otherwise error is returned.
Skipping native histograms (dropping them), might not be a desired option either.
I think I would be supporting on keeping this and documenting better cc @ArthurSens @beorn7 @krajorama as we want to have native histogram by default going forward, so that won't be a problem.

In that case I think created-timestamp-zero-ingestion should itself make all the needed changes so native histograms are accepted, because when --enable-feature=created-timestamp-zero-ingestion is omitted, prometheus is able to scrape native histograms without having to set --enable-feature=native-histograms.

I think it's also OK to modify protobuf parsing to ignore native histograms if the feature flag is disabled.

I think it's also OK to modify protobuf parsing to ignore native histograms if the feature flag is disabled.

Yes, just have to make sure to not ignore classic histograms as well :)

I think it's also OK to modify protobuf parsing to ignore native histograms if the feature flag is disabled.

Yes, just have to make sure to not ignore classic histograms as well :)

I'm looking at the scrape.go code now... do I understand correctly that float histograms represent the classic histograms? and histogram represent native histograms? I.e, the change is simply checking if the native histogram feature flag is enabled here?
https://github.com/prometheus/prometheus/blob/f36915b6b14e3b54132a9cd701835d0255741f96/scrape/scrape.go#L1630-L1635

Both classic and native histograms have a float histogram version.
Or in other words: "classic" vs. "native" on the one hand and "integer" vs "float" on the other hand are orthogonal properties.
So no, the if statement you have quoted is not about switching between classic and native histograms, but about switching between integer native histograms and float native histograms.
But it should be a quite easy switch.

source: gharchive/issue

authors: ArthurSens beorn7 bwplotka dbluxo krajorama machine424

license_type: permissive

license_source: github-api


text:
AquaSec metrics in Prometheus

What did you do?
Our AquaSec is installed in ECS, and we previously scraped the host in Prometheus, which indicates that the target is up and we are able to get the basic metrics (logins, scan -inprogress, pending, done). Therefore, there are no issues there. However, we are encountering a problem only with the metrics and need your suggestions on this issue.
When we click on the target in Prometheus or use the command 'curl -H "Authorization: Bearer " http:///metrics, we receive the following error: {"message":"You are not allowed to perform this action","code":403}`.
The reason this happens is because no bearer token is supplied. We can test this by opening Developer Tools (ctrl + shift + I) and going to the Networking tab, doing the same thing.
please suggest
What did you expect to see?
No response
What did you see instead? Under which circumstances?
{"message":"You are not allowed to perform this action","code":403}
System information
No response
Prometheus version
No response
Prometheus configuration file
No response
Alertmanager version
No response
Alertmanager configuration file
No response
Logs
No response

Are you using the shown URL or the one in the href? As sometimes they're not the same: https://github.com/prometheus/prometheus/issues/13376
As Prometheus can successfully scrape the target, it's clear this is not an issue in Prometheus itself.
You just need to better simulate the request that Prometheus runs.
I'll convert this into a discussion.


text:
UYUNI SD: Validate HTTP config

Related-to #12810

Thanks!

source: gharchive/pull-request

authors: roidelapluie slashpai


text:
1.7 easyjson

This is a fix for #3601, this wouldn't be the actual PR (as we'll need to commit the changes in https://github.com/prometheus/common/pull/112 first) but this gives an idea of the level of change required (very small).
I've run this locally with some test data, and here are the comparisons:

pre-patch
with-patch

Matrix
214ms
37ms

Vector
108ms
20ms

Scalar
20ms
11ms

String
18ms
13ms

With this we can see the large performance gains even with small returns. Not only do we get these gains (~5-6 for "real" data) we also significantly reduce the memory required to marshal out the response (which means this scales significantly better into large response sizes.
Also, as a bonus, since this iteratively serializes it will also stop mid-serialization if the client disconnects!

CI CI failure seems unrelated (due to unmounting FS?)

To include a complete end-to-end benchmark I've done a simple promql query (metricname[range]) over various time durations pre and post easyjson change, here are the results:

Time (minutes)
Old
New
Improvement

0
0.121
0.086
-28.92561983

1
0.171
0.076
-55.55555556

10
1.226
0.119
-90.29363785

30
2.126
0.58
-72.7187206

60
5.173
0.441
-91.47496617

120
9.086
1.107
-87.81642087

180
13.719
1.795
-86.91595597

240
17.668
1.956
-88.92913742

This PR is against Prometheus 1.7, which is not the current development version. Any changes of this nature should be proposed against master.

@brian-brazil I can do that, I opened the PR here as the issue (#3601 ) was reported on 1.7. The changes here can (and should) be applied to any releases that are still supported (I'm not sure which ones those are, so I'll need some guidance on what are the currently supported releases).

A change like this would be aimed for 2.1 currently, which is to say master. New features are not being added to 1.x.

I can re-open the PR against master, but https://github.com/prometheus/common/pull/112 needs to be merged first. Before moving the PR I'd like to see that merged and some feedback on this change (since it will be basicaly the same change against master).
Is there also no mechanism to backport to previous releases? From looking at the releases page it seems that N-1 is supported (minor releases etc.)?

All the relevant code changed with 2.0, you'd need to redo it all.
Only bugfixes would be considered for backport.

What classifies bug fix? From the end to end data this is ~10x perf
improvement.
Also, your latest response still has no feedback for a change like this.
On Dec 27, 2017 4:48 PM, "Brian Brazil" notifications@github.com wrote:

All the relevant code changed with 2.0, you'd need to redo it all.
Only bugfixes would be considered for backport.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/prometheus/pull/3608#issuecomment-354205590,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABi3nXHiLCCYI_2QTp4GzjKfuVV9Tt1Zks5tEuVhgaJpZM4RKaNd
.

A performance improvement is not considered a bugfix.

Ok, how about feedback on the change?
On Dec 27, 2017 4:57 PM, "Brian Brazil" notifications@github.com wrote:

A performance improvement is not considered a bugfix.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/prometheus/pull/3608#issuecomment-354206788,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABi3nR1QakyNWtnQ3j9B1mWlfCAoIqyuks5tEudsgaJpZM4RKaNd
.

It's a highly invasive change that'd require significant ongoing error-prone maintenance, and it also violates layering. Such downsides require major major benefits to justify, and the benchmark numbers produced thus far are at odds with previous profiling in this area.

It's a highly invasive change

I'm not sure if we're looking at the same diff? The reason this particular PR is so large is due to changes in the vendor directory. The actual change to the code is ~30-40 lines of change, which I'd hardly call "highly invasive".

that'd require significant ongoing error-prone maintenance

I'm also not sure what maintenance you are expecting to perform? There is one codegen'd file -- which requires no human to write the code and the only other one is a small marshal method on the queryData struct -- which isn't exactly a large struct.

and it also violates layering.

What are you implying with this? What layering is being broken? In golang marshal methods have to be in the package with the struct definition-- so if you don't want the marshal/unmarshal methods in this package then we need to move it to another package. Past that I have no idea what other layering you could be referring to, so please elaborate.

Such downsides require major major benefits to justify

I agree, which is why I've spent a significant amount of time collecting a LOT of data (and creating a variety of benchmarks to demonstrate this)

and the benchmark numbers produced thus far are at odds with previous profiling in this area.

Thats usually how performance improvements work? For all the benchmarks we're talking about the code is all open -- so it is comparable. The benchmarks you are referring to are all done by the jsoniter guys on a generic dataset. The benchmarks I've put in place are (1) with the prometheus structs and (2) a full end-to-end test (which is exactly what you asked for). At this point I'm at a loss for what additional information to provide. I have overwhelming data supporting my position, and all you've been able to counter with is "suspicion" -- with no recourse.
What data or proof do you require to get such a change in? I'm growing weary of gathering data only to be met with 'suspicion' and uncertainty. This is a simple performance optimization (a HUGE one, but a simple one nonetheless). If not performance data, what data do you need?

Obsoleted by #3536

authors: brian-brazil jacksontj


text:
[remote-storage] use warn log level when send samples to remote failed

What type of PR is this?
Add a detail error for sendSamplesWithBackoff
What this PR does / why we need it:
This useful for user to find remote write error directly, rather than a context deadline exceeded.
e.g. no route to host occured, we can easily find it.

Thank you for the PR!
A couple things here, I don't like that we could potentially be printing out nil errors here, and would prefer the error to be reported more quickly as it would currently be necessary to shutdown or change a queue to get this error.
What would you and @cstyan think of increasing the level of the "Failed to send batch, retrying" log message? We use a dedupe logger so it shouldn't be too noisy.
This could fix #5735 depending on the implementation

If dedupe logger is ok, increasing the send batch error log level maybe reasonable.

I think bumping the log level while we're still using the deduper is fine. Especially given that we also have the metric for retried samples.

Was this merged to prom/prometheus:v2.24.1 ? I can see the proper error when using debug level but not info level (which is "higher" than warn)
Am I missing something?

Was this merged to prom/prometheus:v2.24.1 ? I can see the proper error when using debug level but not info level (which is "higher" than warn)
Am I missing something?

Can you paste the log line ?

Can you paste the log line ?

Also note that the error will not be repeated if it is the same (IIRC)

Also note that the error will not be repeated if it is the same (IIRC)

@roidelapluie

Changed log.level to debug, info and warn
Disallowed outbound connection (AWS Security Group > removed outbound to 0.0.0.0/0 rule)
Restarted Prometheus - kill -HUP 1

--log.level=debug (works as expected)
ts=2021-01-27T11:21:21.540Z caller=dedupe.go:112 component=remote
level=debug remote_name=lalala url="https://metric-api.newrelic.com/prometheus/v1/write?X-License-Key=TOKEN&prometheus_server=prom" msg="failed to send batch, retrying" err="Post \"https://metric-api.newrelic.com/prometheus/v1/write?X-License-Key=TOKEN&prometheus_server=prom\": context deadline exceeded"

--log.level=info - no error appears, even though there's outbound connection is not allowed
ts=2021-01-27T11:51:24.781Z caller=dedupe.go:112 component=remote
level=info remote_name=lalala url="https://metric-api.newrelic.com/prometheus/v1/write?X-License-Key=TOKEN&prometheus_server=prom" msg="Done replaying WAL" duration=14.391332476s

--log.level=warn - nothing to show, no logs at all

@roidelapluie

Changed log.level to debug, info and warn
Disallowed outbound connection (AWS Security Group > removed outbound to 0.0.0.0/0 rule)
Restarted Prometheus - kill -HUP 1

--log.level=debug (works as expected)
ts=2021-01-27T11:21:21.540Z caller=dedupe.go:112 component=remote
level=debug remote_name=lalala url="https://metric-api.newrelic.com/prometheus/v1/write?X-License-Key=TOKEN&prometheus_server=prom" msg="failed to send batch, retrying" err="Post \"https://metric-api.newrelic.com/prometheus/v1/write?X-License-Key=TOKEN&prometheus_server=prom\": context deadline exceeded"

--log.level=info - no error appears, even though there's outbound connection is not allowed
ts=2021-01-27T11:51:24.781Z caller=dedupe.go:112 component=remote
level=info remote_name=lalala url="https://metric-api.newrelic.com/prometheus/v1/write?X-License-Key=TOKEN&prometheus_server=prom" msg="Done replaying WAL" duration=14.391332476s

--log.level=warn - nothing to show, no logs at all

This was a part of v2.19, but it looks like in v2.23 a change was merged that accidentally changed it back to debug. Here is a PR to change this line back to warn: https://github.com/prometheus/prometheus/pull/8412.
So v2.19.x -> v2.22.x should have the debug log if you need it. Sorry about that!

This was a part of v2.19, but it looks like in v2.23 a change was merged that accidentally changed it back to debug. Here is a PR to change this line back to warn: https://github.com/prometheus/prometheus/pull/8412.
So v2.19.x -> v2.22.x should have the debug log if you need it. Sorry about that!

@csmarchbanks - Thank you very much for the clarification, I'll use v2.22.x, no biggy. Originally I used 2.18.1 so 2.22.x is still an upgrade ... 😄
Thanks!

@csmarchbanks - Thank you very much for the clarification, I'll use v2.22.x, no biggy. Originally I used 2.18.1 so 2.22.x is still an upgrade ... 😄
Thanks!

authors: csmarchbanks cstyan qingwave roidelapluie unfor19


text:
add root endpoint with redirect

Adds a root endpoint similar to haproxy exporter and node exporter

:+1: Thanks! Sorry for the slow response on this one, been traveling for VelocityConf and all...

authors: juliusv macb

license_source: bigquery


text:
Fix ${line} in text format to mean line number

How to reproduce:
Create a reasonable-sounding .pronto.yml that looks like this, based on documentation from https://github.com/prontolabs/pronto#message-format:
 text:
   format: "%{path} %{line} %{runner} %{msg}"

Run against a project
Expected results:
Receive text output that looks like this:
Rakefile 124 rubocop Use `%i` or `%I` for an array of symbols.

Observed results:
Rakefile #<struct Pronto::Git::Line line=#<Rugged::Diff::Line:70253771778400 {line_origin: :addition, content: "task quality: [:pronto, :update_bundle_audit]\n">, patch=#<struct Pronto::Git::Patch patch=#<Rugged::Patch:70253763427640>, repo=#<Pronto::Git::Repository:0x007fca7539fe08 @repo=#<Rugged::Repository:70253763428080 {path: "/Users/broz/src/vincelifedaily/.git/"}>>>, hunk=#<Rugged::Diff::Hunk:70253771778940 {header: "@@ -115,7 +115,13 @@ end\n", count: 14}>> rubocop Use `%i` or `%I` for an array of symbols.

Notes:
Looks like the json_formatter.rb already looks for line number via the same method I'm proposing here.  I'm guessing changing the meaning of message.line is a nonstarter given you'd have to change all of the runners at the same time, so using the decorator to adjust the meaning seemed like the right thing.

@apiology this is wonderful, thank you!  Would it be possible for you to update or add test coverage for this change?

@doomspork: Added - let me know what you think!

Thank you @apiology!  I'm going to give @mmozuras an opportunity to review this change before we merge.
I'm not sure whether or not you're participating in Digital Ocean's Hacktoberfest but I went ahead and tagged the PR for you anyways 😀

Thanks--wasn't aware of it, but just signed up!

@apiology thanks! 🙇
Exemplary pull request, love the fact that you've written a perfect "how to reproduce" 😄

authors: apiology doomspork mmozuras vinceatbluelabs

repo: prontolabs/pronto

license: mit


text:
Create COD in dev-tools or Filecoin

Problem Description
We need to add additional, high value dev tools
Purpose
Create a Dev tools section with tutorial
Proposed Solution
What features, user stories, or product/ content you would like as an output
Where Can we find out more about this topic?
Additional context

Blog/ Videos from CoD at IPFS Camp

Milestones (Optional)
1) Milstone Name Text
2) Milstone Name Text
Acceptance Criteria
Describe the out put and criteria for this output for considering this task completed

I reached out to Iryna who is a new devrel/ content writer for COD and would love to have someone work with her to add some of this content!

duplicate https://github.com/orgs/protocol/projects/21?pane=issue&itemId=18463926

repo: protocol/launchpad


text:
Musl compatible protoc-gen-js

Please provide a musl compatible protoc-gen-js.
I know it's possible because I've been able to build the project in Alpine Linux, but a release tar like the ones we already have for Glibc would be much more convenient. Or maybe a static build that works on both.

In principle, we are not opposed to this, but this work would be blocked on protoc providing build support (likewise for static compilation). It looks like they have a similar issue open here: https://github.com/protocolbuffers/protobuf/issues/7040.
I'll poke the thread to see if they have any updates.

authors: dibenede sp-marcel-hernandez

repo: protocolbuffers/protobuf-javascript


text:
In read-only mode, it remains possible to edit the broker's configuration

Issue submitter TODO list

[X] I've looked up my issue in FAQ
[X] I've searched for an already existing issues here
[X] I've tried running master-labeled docker image and the issue still persists there
[X] I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)
In read-only mode, it remains possible to edit the broker's configuration
Expected behavior
No response
Your installation details
56fa824
27.06.2023, 16:36:09
helm: version.BuildInfo{Version:"v3.5.1", GitCommit:"32c22239423b3b4ba6706d450bd044baffdcf9e6", GitTreeState:"clean", GoVersion:"go1.15.7"}
Steps to reproduce
Through the dashboard, select kafka, go to the brokers section, select any broker from the list and go to the configs tab, the edit and save buttons are active
Screenshots

Logs
No response
Additional context
No response

@BeardedShamrock - When you are saving post editing , is it getting saved ? In my case its not.

@BeardedShamrock - When you are saving post editing , is it getting saved ? In my case its not.

Hi! I'll try, ty for answer.

repo: provectus/kafka-ui


text:
leftFlatMap purpose

can we have follow method for BIO?
leftFlatMap => it performs redeem logic, but prevents to map right side into identity
flip (or another literal) => swaps Left and Right
flips could help us to prevent map asBad and other related stuff for tests

@pshirshov @kaishh

Your PR has been merged 👍

authors: kaishh ratoshniuk


text:
Users can CRUD deputy assignments

A few things to note:

I modified the database schema of the deputy_assignments table, added another column which allows me to write a database level uniqueness constraint that all active DeputyAssignments must have a unique pairing of (primary, deputy) but inactive DeputyAssignments can have multiples. There's now a big comment on DeputyAssignment class explaining how this works.
There's a big form object that accepts a user's webaccess id, then does all the legwork of creating and validating a DeputyAssignment for them. The logic for this is broken down in #269. It also puts a lot of effort into making the validation errors look reasonable to the user on the screen.
There's also a much smaller service object used to delete/deactivate DeputyAssignments
Based on the fact that we renamed Delegates/Deputies/Proxies three times in a week, I put everything in a translation file. While I was at it, I just put the entire user profile management navigation bar into the translations as well.
I added ViewComponent for making the Proxies UI

There is one thing I noticed when coding this up, it seems like the Rails-UJS javascript is being loaded/initialized twice. We should look into that, because any button with data: { confirm: ... } will prompt you twice.
Closes #269

Relying on raising and catching exceptions is thornier than using errors directly

Adam, I refactored that class to not use (as many) catches, give the new version a perusal

repo: psu-stewardship/researcher-metadata

license: MIT


text:
Errors using supabase

Can you provide a proper documentation to use Supabase. I have the URL and the key but getting below error while trying to upload the file:
{'statusCode': 400, 'error': 'Invalid JWT', 'message': 'new row violates row-level security policy for table "buckets"'}
Are there any pre-requisites?

@jammy23495 I just updated the readme with new instructions. It sounds like you are probably using the supabase public key server side instead of the secret key.

Thanks @Ayan-Bandyopadhyay. I will try it out. Is there any Slack / Discord channels where we can discuss these kind of issues?

I have few questions:

Which key should I use from the below screenshot?

While trying to reset the password, I am getting below message.

@Ayan-Bandyopadhyay I have few questions:
1. Which key should I use from the below screenshot?
   ![image](https://user-images.githubusercontent.com/30603350/259057840-e5aa2e59-3b96-47f9-bd8d-0f18d3cd40f3.png)

2. While trying to reset the password, I am getting below message.
   ![image](https://user-images.githubusercontent.com/30603350/259058187-9fb62654-76c5-4e61-a481-19b40e08de2e.png)

The one tagged as service_role secret

repo: psychic-api/rag-stack


text:
x11rb-async async functions should have #[must_use] attributes

It is easy to forget to .await an async fn, and without a #[must_use] attribute, you won't get a warning for forgetting to do so.

This should probably go for cookies too actually.

My first thought is "this is not x11rb-async specific, but should rather be a rust ecosystem thing", but I cannot find much compiler or clippy lints that would warn about this. The closest I found are https://rust-lang.github.io/rust-clippy/master/index.html#/let_underscore_future and https://rust-lang.github.io/rust-clippy/master/index.html#/unused_async but neither would exactly hit this case.
Actually... the Future trait is marked must_use, so shouldn't that already be enough for a warning? I'm not sure.
But I just tried this and I couldn't get a warning. conn.query_tree(window); doesn't do anything. At least conn.query_tree(window).await; generates a warning due to the Result. conn.query_tree(window).await?; then again doesn't warn. With conn.query_tree(window).await?.reply(); I finally get warning: unused implementer of Future that must be used. conn.query_tree(window).await?.reply().await; again warns due to the unused Result.
Ahh, query_tree does not return a Future, but a Pin<Box<dyn Future<....>>>. That's why there is no warning here. x11rb_async::protocol::xproto::query_tree(conn, window); also causes a warning due to the naked future.

This should probably go for cookies too actually.

I'm not quite sure. The cookie by itself doesn't do much. The request was already sent and there are valid cases for ignoring a cookie. I guess must VoidCookies are immediately dropped and I bet I could even come up with a case where dropping a Cookie would be the right thing to do.

Actually... the Future trait is marked must_use, so shouldn't that already be enough for a warning? I'm not sure.

At least for async it should be. Like you mentioned it's a footgun that should be fixed on the Rust level.

authors: Antikyth notgull psychon


text:
Added EVA under Data Validation category

Thank you for taking the time to work on a Pull Request for this project!
To ensure your PR is dealt with swiftly please check the following:

[ ] Your submissions are formatted according to the guidelines in the contributing guide
[ ] Your additions are ordered alphabetically
[ ] Your submission has a useful description
[ ] The description does not end with punctuation
[ ] Each table column should be padded with one space on either side
[ ] You have searched the repository for any relevant issues or pull requests
[ ] Any category you are creating has the minimum requirement of 3 items
[ ] All changes have been squashed into a single commit

Thanks for the contribution @aman-agrwl-zz!!!
Can you please resolve the conflict?

Can you please resolve the conflict?

Done!
Thanks @aman-agrwl-zz :)

authors: aman-agrwl-zz marekdano matheusfelipeog

repo: public-apis/public-apis


text:
Add Meteorologisk Institutt API

Thank you for taking the time to work on a Pull Request for this project!
To ensure your PR is dealt with swiftly please check the following:

[x] Your submissions are formatted according to the guidelines in the contributing guide
[x] Your additions are ordered alphabetically
[x] Your submission has a useful description
[x] The description does not end with punctuation
[x] Each table column should be padded with one space on either side
[x] You have searched the repository for any relevant issues or pull requests
[x] Any category you are creating has the minimum requirement of 3 items
[x] All changes have been squashed into a single commit

Thank you

authors: mortenkleveland yannbertrand


text:
commonName deprecated for certificate issuance, use altNames instead

https://github.com/publishlab/node-acme-client/blob/master/examples/dns-01/dns-01.js#L45-L48
commonName limited with 63 symbols
altName - 255 characters (237 symbols for dns-01 - due to the challenge prefix)
https://letsencrypt.org/docs/glossary/

Common Name (CN) : Part of a certificate’s Subject describing what the certificate is about. For roots and intermediates it’s the human-readable name of the certificate authority. For leaf certificates it’s one of the domain names on the certificate. Note: The common name is limited to 63 characters. It is an obsolete method of indicating a domain name to which the certificate applies, since current Internet standards expect software to check only the Subject Alternative Names in order to determine the applicability of a certificate.

https://www.redhat.com/en/blog/details-on-https-common-name-deprecation-in-openshift-4.10

x509: certificate relies on legacy Common Name field, use SANs instead

https://cabforum.org/uploads/BRv1.2.3.pdf
9.2.2 Subject Common Name Field
Certificate Field: subject:commonName (OID 2.5.4.3)
Required/Optional: Deprecated (Discouraged, but not prohibited)
Contents: If present, this field MUST contain a single IP address or Fully-Qualified Domain Name that is one of
the values contained in the Certificate’s subjectAltName extension (see Section 9.2.1).

right way
        const [key, csr] = await acme.crypto.createCsr({
            altNames: [
                 WILDCARD_DOMAIN,
                 `*.${WILDCARD_DOMAIN}`
            ]
        });

Thanks for raising this, bug in auto() with no common name fixed in 9e277b5aedc380644f8de8982b60c6407f3406af, docs and examples in 12f8096f2cf7ca377d63dbfffad0a90ed605379c.

authors: nmorsman thebitrock

repo: publishlab/node-acme-client


text:
UAT| E-Filing | Representative details of Entity is optional

Module: Efiling
Screen: Respondent Details -> Entity
Make the Representative Details optional (First Name, Middle Name, Last Name)

Development Tasks

[ ] We have made middle name & last name was optional
[ ] In the registration and E-filling modules

Hi @devarajd94  We have made the middle name and last name as optional

repo: pucardotorg/dristi


text:
Allow to disable config helpers

NO_CONFIG_HELPER=true disables every configuration of AIRFLOW__* variables (and also implicitly the wait_for_port function)
The optional requirements installation has been moved to the top to be out of the configuration helper block.

Closing this to un-bloat the PR section of this repo. The entrypoint can be overridden with the --entrypoint Docker argument or the command container attribute in K8s as a workaround.

repo: puckel/docker-airflow


text:
Allow us to add labels and networks to the container when running in Docker

Would be very useful for things like Traefik

I think network is already supported, but labels is very useful. From the looks of it, it is a small change on the back-end:

I cannot push to a branch, otherwise I would've pushed it.

I would've liked to inject some labels for traefik, but it doesn't seem to work.

Is this the correct location in the server properties? Is there a workaround?
Thanks for any advise and help.

This only would apply for v3, which has not been officially released yet.

Ah, ok. That explains things. Thanks

authors: Jan-Ka LordRalex joost00719

repo: pufferpanel/pufferpanel


text:
(Suggestion) Change the mortar color of monochromatic bricks

Hi, first of all thank you for making this mod, it's amazing!
I have a suggestion which might make the bricks more appealing - can you darken the mortar in light grey, grey and black, and brighten the mortar in white bricks? If this is not ideal, why not add a new variation of the same bricks, except all have darker mortar?
Thanks

My graphical skills are very limited, so if someone modifies the textures, I'll gladly merge them in to my mod.
https://github.com/puggan/mc-colorbricks/tree/1.16/master/src/main/resources/assets/colorbricks/textures/block
I'm not used to the word "mortar", but in this context I guess its the "glue" between the bricks.

authors: puggan tanyan-tanyan

repo: puggan/mc-colorbricks


text:
[#2398] Remove marquand-phref

closes #2398

The location has been removed from https://bibdata-staging.princeton.edu/locations/holding_locations

repo: pulibrary/bibdata


text:
Display placeholder for FileSets before thumbnail is available?

Since we want to prioritize ingesting into Fedora over characterization/derivatives, FileSets will be present for a while before a thumbnail is available.  Do we want to show a placeholder if the thumbnail isn't ready?

Do we have a way to know if the placeholder is ready yet?

Isn't there a standard way to have a fallback to display for an image tag if the main src doesn't work?

authors: escowles tpendragon

repo: pulibrary/plum


text:
Displaying FileSet technical metadata

Closes #828

I looked at a TIFF in Fedora, and there are several other properties that could be added here:

hydrafits:valid "true"
hydrafits:wellFormed "true"
exif:colorSpace "RGB"
exif:exifVersion "9.13"
exif:orientation "normal*"
sweetjpl:byteOrder "big endian"
mix:colorProfileName "Adobe RGB (1998)"
mix:colorProfileVersion "2.1.0"
mix:compressionScheme "Uncompressed"
premis:hasCreatingApplicationVersion "0.8.6" (FITS version)

We talked about adding the valid/wellformed properties — do we want any of the others?

@escowles I made checkboxes.

No pronom ID though, right?

No, it looks like pronom id isn't mapped.

OK. Right now MIME/media type probably doesn't make sense, but it might eventually.

Here's what the new properties look like:

Coverage remained the same at 100.0% when pulling 9a4dc5709ffe00df47f2cf4bcecfd26decd10c7e on display-tech-md into 9688451be22ee54e08bda8bd418b474049321208 on master.

This looks good to me. I just tested this with geo objects, and it works just fine. Any reason to wait on merging this @escowles?

@eliotjordan No, I think this is ready to go.

authors: coveralls eliotjordan escowles jpstroop


text:
Increase header size of search result titles.

Closes #196.

Coverage remained the same at 100.0% when pulling 76e3192e77cc0769049fee1c42b04bdeb43e7601 on index_header_size into c290dc8e54df1467b08b5ec0062b1bfda84173bb on master.

authors: coveralls tpendragon

repo: pulibrary/pomegranate


text:
Release a new version of the gem

After releasing a new version. Update marc_liberation.

this was done


text:
Package atom-elixir-formatter should receive Broken Badge

This package uses JavaScript Sloppy mode and breaks on newer nodejs versions.
See pulsar-edit/pulsar#133

An update to the original discussion. @benonymushad intended to update the package source to provide a working fork of the package.
And while they haven't announced as such, seems they have successfully created and published a fork of the package here.
So this package should receive the 'deprecated' badge, suggesting installation of this package as an alternative.

repo: pulsar-edit/package-backend


text:
[BUG]Shop error

When you click on the menu to go to the Shop, you get an error
Steps to reproduce the behavior:

Go to Main Page
Click on Shop on the menu
See error

================================================================================
02-28-2024 14:16:25.505500 #### SELECT id, item_id, item_cat, name, original_item_cat, stick_level, price FROM DmN_Shopp WHERE price >= 1 AND item_cat IN ('0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15') ORDER BY  item_cat ASC, item_id ASC
================================================================================
02-28-2024 14:16:25.506400 #### PDOException: SQLSTATE[22018]: [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Conversion failed when converting the varchar value '0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15' to data type int. in C:\xampp\htdocs\application\libraries\lib.db.php:105
Stack trace:
#0 C:\xampp\htdocs\application\libraries\lib.db.php(105): PDO->query('SELECT id, item...')
#1 C:\xampp\htdocs\application\models\model.shop.php(35): db->query('SELECT id, item...')
#2 C:\xampp\htdocs\application\controllers\controller.shop.php(76): Mshop->load_items('DEFAULT', 1, '16', '4')
#3 C:\xampp\htdocs\system\router.class.php(91): shop->index()
#4 C:\xampp\htdocs\system\dmn.php(26): router->route(Object(request))
#5 C:\xampp\htdocs\system\dmn.php(29): initDmN()
#6 C:\xampp\htdocs\index.php(33): require_once('C:\\xampp\\htdocs...')
#7 {main}

https://github.com/pulseP1986/free-mu-cms/commit/018dd453fa6bce7585454a139bafdaaa75accb34

now it is giving another type of error


text:
aws:s3:BucketObjectv2 should only trigger an update when my code changes

Hello!

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details
Even when I don't change my code, the aws:s3:BucketObjectv2 goes through an Update cycle when I run pulumi up. I expect it to only do that when code changes. Does pulumi perform any hashing and caching to avoid redundant work like this?

Can you share the inputs you are passing in before and after the initial update?

Added to epic https://github.com/pulumi/home/issues/2191

authors: cleverguy25 lukehoban sam-goodwin

repo: pulumi/pulumi-cdk


text:
Kubernetes context config out of order

Problem description

I saw a product documentation issue on the following URL: https://www.pulumi.com/docs/get-started/kubernetes/begin/
I saw a product documentation issue on the following URL: https://www.pulumi.com/docs/intro/cloud-providers/kubernetes/setup/

When starting with the above begin guide for Kubernetes, near the bottom it tells you to configure Kubernetes first, which is the second link above. When setting up the cluster, and using context as I am you are asked to perform.
pulumi stack init new-kube-stack && pulumi config set kubernetes:context my-context
However, you haven't initialized a project yet and that command fails. The next page of getting started has you initialize a project at which point you can configure the context for the project.
Suggestions for a fix
Assuming my understanding above is correct, simply have the user initialize a project first and then explain how to configure Kubernetes for the stack. This would also make it more clear that a stack maps to a cluster initially I was under the impression I was configuring it globally but it certainly makes more sense for it to be a per-stack config.

@chris-sanders Thanks for the feedback. I just want to make sure you are unblocked? You're correct that you should first do a pulumi new to create the project.

@leezen not blocked, I just filed the bug to help improve it for future travelers once I realized what the issue was.

authors: chris-sanders leezen

repo: pulumi/pulumi-hugo


text:
Pull Cloudformation and CDK menu items into the main vs. list

This change should make these items a little easier to find in the menu.

should we add aliases here? i did share the new links with a few folks, though i can go correct it if you prefer.

why was there no preview on this?

authors: cnunciato susanev


text:
MultiLocationAlertCondition panic index out of range

What happened?
The following program yields this panic, could be upstream:
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s) panic: runtime error: index out of range [3] with length 1
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s) goroutine 59 [running]:
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s) github.com/newrelic/terraform-provider-newrelic/v2/newrelic.getMonitorID({0x1400013bb60?, 0x102e59d4a?})
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s)    /home/runner/work/pulumi-newrelic/pulumi-newrelic/upstream/newrelic/resource_helpers_synthetics.go:460 +0x84
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s) github.com/newrelic/terraform-provider-newrelic/v2/newrelic.expandMultiLocationSyntheticsCondition(0x10?)
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s)    /home/runner/work/pulumi-newrelic/pulumi-newrelic/upstream/newrelic/structures_newrelic_synthetics_multilocation_alert_condition.go:31 +0x288
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s) github.com/newrelic/terraform-provider-newrelic/v2/newrelic.resourceNewRelicSyntheticsMultiLocationAlertConditionCreate({0x1034c2248, 0x1400025ebd0}, 0x0?, {0x103249340?, 0x1400056c440?})
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s)    /home/runner/work/pulumi-newrelic/pulumi-newrelic/upstream/newrelic/resource_newrelic_synthetics_multilocation_alert_condition.go:110 +0x90
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s) github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).create(0x140000f2c40, {0x1034c21a0, 0x1400019e630}, 0xd?, {0x103249340, 0x1400056c440})
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s)    /home/runner/go/pkg/mod/github.com/pulumi/terraform-plugin-sdk/v2@v2.0.0-20240229143312-4f60ee4e2975/helper/schema/resource.go:783 +0xe8
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s) github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).Apply(0x140000f2c40, {0x1034c21a0, 0x1400019e630}, 0x0, 0x14000434a80, {0x103249340, 0x1400056c440})
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s)    /home/runner/go/pkg/mod/github.com/pulumi/terraform-plugin-sdk/v2@v2.0.0-20240229143312-4f60ee4e2975/helper/schema/resource.go:914 +0x86c
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s) github.com/pulumi/pulumi-terraform-bridge/v3/pkg/tfshim/sdk-v2.v2Provider.Apply({0x1400080c660?, {0x0?, 0x102e9756b?, 0x31?}}, {0x1034c21a0, 0x1400019e630}, {0x102e9756b, 0x31}, {0x0?, 0x0}, ...)
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s)    /home/runner/go/pkg/mod/github.com/pulumi/pulumi-terraform-bridge/v3@v3.78.0/pkg/tfshim/sdk-v2/provider.go:122 +0x148
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s) github.com/pulumi/pulumi-terraform-bridge/v3/pkg/tfbridge.(*Provider).Create(0x14000a01980, {0x1034c21a0?, 0x14000444ea0?}, 0x140002f8eb0)
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s)    /home/runner/go/pkg/mod/github.com/pulumi/pulumi-terraform-bridge/v3@v3.78.0/pkg/tfbridge/provider.go:1055 +0x67c
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s) github.com/pulumi/pulumi/sdk/v3/proto/go._ResourceProvider_Create_Handler.func1({0x1034c21a0, 0x14000444ea0}, {0x1033aeae0?, 0x140002f8eb0})
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s)    /home/runner/go/pkg/mod/github.com/pulumi/pulumi/sdk/v3@v3.111.1/proto/go/provider_grpc.pb.go:593 +0x74
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s) github.com/grpc-ecosystem/grpc-opentracing/go/otgrpc.OpenTracingServerInterceptor.func1({0x1034c21a0, 0x14000444b10}, {0x1033aeae0, 0x140002f8eb0}, 0x140001514e0, 0x14000554ac8)
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s)    /home/runner/go/pkg/mod/github.com/grpc-ecosystem/grpc-opentracing@v0.0.0-20180507213350-8e809c8a8645/go/otgrpc/server.go:57 +0x2e8
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s) github.com/pulumi/pulumi/sdk/v3/proto/go._ResourceProvider_Create_Handler({0x1034623c0?, 0x14000a01980}, {0x1034c21a0, 0x14000444b10}, 0x14000712480, 0x140007161e0)
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s)    /home/runner/go/pkg/mod/github.com/pulumi/pulumi/sdk/v3@v3.111.1/proto/go/provider_grpc.pb.go:595 +0x12c
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s) google.golang.org/grpc.(*Server).processUnaryRPC(0x14000282a00, {0x1034c21a0, 0x14000444a80}, {0x1034cc320, 0x140001024e0}, 0x14000110fc0, 0x140002682a0, 0x10406c560, 0x0)
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s)    /home/runner/go/pkg/mod/google.golang.org/grpc@v1.62.0/server.go:1383 +0xb8c
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s) google.golang.org/grpc.(*Server).handleStream(0x14000282a00, {0x1034cc320, 0x140001024e0}, 0x14000110fc0)
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s)    /home/runner/go/pkg/mod/google.golang.org/grpc@v1.62.0/server.go:1794 +0xc70
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s) google.golang.org/grpc.(*Server).serveStreams.func2.1()
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s)    /home/runner/go/pkg/mod/google.golang.org/grpc@v1.62.0/server.go:1027 +0x8c
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s) created by google.golang.org/grpc.(*Server).serveStreams.func2 in goroutine 100
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s)    /home/runner/go/pkg/mod/google.golang.org/grpc@v1.62.0/server.go:1038 +0x150
 +  newrelic:synthetics:MultiLocationAlertCondition newrelic_multilocationalertcondition creating (0s) error: error reading from server: EOF
 +  newrelic:synthetics:MultiLocationAlertCondition newrelic_multilocationalertcondition **creating failed** error: error reading from server: EOF
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev creating (1s) error: update failed
 +  pulumi:pulumi:Stack synthetics_multilocationalertconditionsHdfILQm1FTB-dev **creating failed (0.52s)** 1 error; 30 messages
Policies:
    ✅ pulumi-internal-policies@v0.0.6

Diagnostics:
  pulumi:pulumi:Stack (synthetics_multilocationalertconditionsHdfILQm1FTB-dev):
    panic: runtime error: index out of range [3] with length 1
    goroutine 59 [running]:
    github.com/newrelic/terraform-provider-newrelic/v2/newrelic.getMonitorID({0x1400013bb60?, 0x102e59d4a?})
        /home/runner/work/pulumi-newrelic/pulumi-newrelic/upstream/newrelic/resource_helpers_synthetics.go:460 +0x84
    github.com/newrelic/terraform-provider-newrelic/v2/newrelic.expandMultiLocationSyntheticsCondition(0x10?)
        /home/runner/work/pulumi-newrelic/pulumi-newrelic/upstream/newrelic/structures_newrelic_synthetics_multilocation_alert_condition.go:31 +0x288
    github.com/newrelic/terraform-provider-newrelic/v2/newrelic.resourceNewRelicSyntheticsMultiLocationAlertConditionCreate({0x1034c2248, 0x1400025ebd0}, 0x0?, {0x103249340?, 0x1400056c440?})
        /home/runner/work/pulumi-newrelic/pulumi-newrelic/upstream/newrelic/resource_newrelic_synthetics_multilocation_alert_condition.go:110 +0x90
    github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).create(0x140000f2c40, {0x1034c21a0, 0x1400019e630}, 0xd?, {0x103249340, 0x1400056c440})
        /home/runner/go/pkg/mod/github.com/pulumi/terraform-plugin-sdk/v2@v2.0.0-20240229143312-4f60ee4e2975/helper/schema/resource.go:783 +0xe8
    github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).Apply(0x140000f2c40, {0x1034c21a0, 0x1400019e630}, 0x0, 0x14000434a80, {0x103249340, 0x1400056c440})
        /home/runner/go/pkg/mod/github.com/pulumi/terraform-plugin-sdk/v2@v2.0.0-20240229143312-4f60ee4e2975/helper/schema/resource.go:914 +0x86c
    github.com/pulumi/pulumi-terraform-bridge/v3/pkg/tfshim/sdk-v2.v2Provider.Apply({0x1400080c660?, {0x0?, 0x102e9756b?, 0x31?}}, {0x1034c21a0, 0x1400019e630}, {0x102e9756b, 0x31}, {0x0?, 0x0}, ...)
        /home/runner/go/pkg/mod/github.com/pulumi/pulumi-terraform-bridge/v3@v3.78.0/pkg/tfshim/sdk-v2/provider.go:122 +0x148
    github.com/pulumi/pulumi-terraform-bridge/v3/pkg/tfbridge.(*Provider).Create(0x14000a01980, {0x1034c21a0?, 0x14000444ea0?}, 0x140002f8eb0)
        /home/runner/go/pkg/mod/github.com/pulumi/pulumi-terraform-bridge/v3@v3.78.0/pkg/tfbridge/provider.go:1055 +0x67c
    github.com/pulumi/pulumi/sdk/v3/proto/go._ResourceProvider_Create_Handler.func1({0x1034c21a0, 0x14000444ea0}, {0x1033aeae0?, 0x140002f8eb0})
        /home/runner/go/pkg/mod/github.com/pulumi/pulumi/sdk/v3@v3.111.1/proto/go/provider_grpc.pb.go:593 +0x74
    github.com/grpc-ecosystem/grpc-opentracing/go/otgrpc.OpenTracingServerInterceptor.func1({0x1034c21a0, 0x14000444b10}, {0x1033aeae0, 0x140002f8eb0}, 0x140001514e0, 0x14000554ac8)
        /home/runner/go/pkg/mod/github.com/grpc-ecosystem/grpc-opentracing@v0.0.0-20180507213350-8e809c8a8645/go/otgrpc/server.go:57 +0x2e8
    github.com/pulumi/pulumi/sdk/v3/proto/go._ResourceProvider_Create_Handler({0x1034623c0?, 0x14000a01980}, {0x1034c21a0, 0x14000444b10}, 0x14000712480, 0x140007161e0)
        /home/runner/go/pkg/mod/github.com/pulumi/pulumi/sdk/v3@v3.111.1/proto/go/provider_grpc.pb.go:595 +0x12c
    google.golang.org/grpc.(*Server).processUnaryRPC(0x14000282a00, {0x1034c21a0, 0x14000444a80}, {0x1034cc320, 0x140001024e0}, 0x14000110fc0, 0x140002682a0, 0x10406c560, 0x0)
        /home/runner/go/pkg/mod/google.golang.org/grpc@v1.62.0/server.go:1383 +0xb8c
    google.golang.org/grpc.(*Server).handleStream(0x14000282a00, {0x1034cc320, 0x140001024e0}, 0x14000110fc0)
        /home/runner/go/pkg/mod/google.golang.org/grpc@v1.62.0/server.go:1794 +0xc70
    google.golang.org/grpc.(*Server).serveStreams.func2.1()
        /home/runner/go/pkg/mod/google.golang.org/grpc@v1.62.0/server.go:1027 +0x8c
    created by google.golang.org/grpc.(*Server).serveStreams.func2 in goroutine 100
        /home/runner/go/pkg/mod/google.golang.org/grpc@v1.62.0/server.go:1038 +0x150

    error: update failed

  newrelic:synthetics:MultiLocationAlertCondition (newrelic_multilocationalertcondition):
    error: error reading from server: EOF

Example
name: synthetics_multilocationalertconditionsHdfILQm1FTB
runtime: yaml
resources:
  newrelic_multilocationalertcondition:
    properties:
      critical:
        threshold: 5
      enabled: true
      entities:
        - synthetics-monitor-id
      policyId: 12345678
      violationTimeLimitSeconds: 3600
    type: newrelic:synthetics:MultiLocationAlertCondition

Output of pulumi about
CLI
Version      3.111.1
Go Version   go1.22.1
Go Compiler  gc

Plugins
NAME      VERSION
newrelic  unknown
yaml      unknown

Host
OS       darwin
Version  14.1.1
Arch     arm64

This project is written in yaml

Current Stack: pulumi/synthetics_multilocationalertconditionsHdfILQm1FTB/dev

TYPE                       URN
pulumi:pulumi:Stack        urn:pulumi:dev::synthetics_multilocationalertconditionsHdfILQm1FTB::pulumi:pulumi:Stack::synthetics_multilocationalertconditionsHdfILQm1FTB-dev
pulumi:providers:newrelic  urn:pulumi:dev::synthetics_multilocationalertconditionsHdfILQm1FTB::pulumi:providers:newrelic::default

Found no pending operations associated with dev

Backend
Name           pulumi.com
URL            https://app.pulumi.com/venelin-pulumi-corp
User           venelin-pulumi-corp
Organizations  venelin-pulumi-corp, demo, pulumi
Token type     personal

No dependencies found

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).

So....while this should not panic, and error instead, this is definitely an upstream panic.
However - this code is incomplete. You'll need to add a policy and a monitor to query. When there is no valid monitor.id to query, the panic gets triggered.
I'll file an upstream bug. However, this being a legacy resource, they may not work on a fix or accept a patch.
For completeness sake:
To avoid hitting this panic, ensure you have a valid AlertPolicy and Monitor resource in addition to the MultiLocationAlertCondition. Link to Basic Example

update: several upstream issues report this behavior but the panic is never addressed; users are directed to use the correct monitor ID:
https://github.com/newrelic/terraform-provider-newrelic/issues/2003
https://github.com/newrelic/terraform-provider-newrelic/issues/2234

Filed https://github.com/newrelic/terraform-provider-newrelic/issues/2631.

Opened https://github.com/newrelic/terraform-provider-newrelic/pull/2632 to address.

Removing the p1 here because there's a clear path forward to avoid the panic.

Fixed via https://github.com/newrelic/terraform-provider-newrelic/issues/2631 and most recent version of this provider.

authors: VenelinMartinov guineveresaenger

repo: pulumi/pulumi-newrelic


text:
Update pulumi/pkg and pulumi/sdk dependencies to v3.109.0

To take full advantage of https://github.com/pulumi/pulumi/pull/15526 this codebase need to depend on a later version of pulumi/pkg. Should be hopefully a routine dependency update.

Something a tad fishy in https://github.com/pulumi/pulumi-aws/issues/3595

It appears that the codebase attempts to pin AWS to 5.35.0 but during some of the tests aws-6.25.0 gets installed anyway, which may be a change coming from the upgrade?
warning: using pulumi-language-yaml from $PATH at /home/runner/work/pulumi-yaml/pulumi-yaml/bin/pulumi-language-yaml
[resource plugin aws-native-0.98.0] installing
[resource plugin aws-6.25.0] installing

Ah looks like because of pulumi/pulumi#15568 there is a problem now with the auto-pin behavior this repository depended on. Since the new ProgramTest creates a separate sandbox for the test, TestExampleWebserver now starts auto-upgrading aws to 6.x with this change which hits the regression listed above.

** TODO FAIL: TestExampleAwsStaticWebsite (12.16s)

[[file:~/code/pulumi-yaml/pkg/tests/example_test.go::func TestExampleAwsStaticWebsite(t *testing.T) {][Test]]

Error: websiteURL does not exist on site-bucket

  on Pulumi.yaml line 6:

   6:     websiteUrl: ${site-bucket.websiteURL}

Existing properties are: websiteUrl, bucketName, domainName, id, tags and 22 others

Similarly caused by inadvertent AWS upgrade to 6.x

The TestExampleAwsx failure similarly caused by a schema change, which might have been called out in the major version rel notes...
Previewing update (p-it-antons-mac-awsx-farga-bfb0d9b9):
[resource plugin awsx-2.5.0] installing
@ previewing update....[resource plugin aws-6.25.0] installing

+ pulumi:pulumi:Stack: (create)
    [urn=urn:pulumi:p-it-antons-mac-awsx-farga-bfb0d9b9::awsx::pulumi:pulumi:Stack::awsx-p-it-antons-mac-awsx-farga-bfb0d9b9]
@ previewing update....
Downloading provider: aws

@ previewing update.....
Error: awsx:ecs:FargateService is not assignable from {cluster: string, taskDefinitionArgs: {container: {cpu: number, image: string, memory: number, portMappings: List<{containerPort: number, targetGroup: aws:lb/targetGroup:TargetGroup}>}}}

  on Pulumi.yaml line 14:

  14:                 container:

  15:                     cpu: 512

  16:                     image: nginx:latest

  17:                     memory: 128

  18:                     portMappings:

  19:                         - containerPort: 80

  20:                           targetGroup: ${lb.defaultTargetGroup}

Cannot assign '{cluster: string, taskDefinitionArgs: {container: {cpu: number, image: string, memory: number, portMappings: List<{containerPort: number, targetGroup: aws:lb/targetGroup:TargetGroup}>}}}' to 'awsx:ecs:FargateService':

  taskDefinitionArgs: Cannot assign '{container: {cpu: number, image: string, memory: number, portMappings: List<{containerPort: number, targetGroup: aws:lb/targetGroup:TargetGroup}>}}' to 'awsx:ecs:FargateServiceTaskDefinition':

    container: Cannot assign '{cpu: number, image: string, memory: number, portMappings: List<{containerPort: number, targetGroup: aws:lb/targetGroup:TargetGroup}>}' to 'awsx:ecs:TaskDefinitionContainerDefinition':

      name: Missing required property 'name'

Resources:
    + 1 to create

Per conversation with @Frassle looking into pinning provider versions in each individual test using this method from https://www.pulumi.com/docs/languages-sdks/yaml/yaml-language-reference/
resources:
  something:
    type: aws:s3:Bucket
    properties:
      ...
    options:
      version: 5.6.0

One more problem here, reusing PulumiPulumiProgramTests from pkg/codegen/testing/test is no longer working since
https://github.com/pulumi/pulumi/pull/15549 because it generates relative links that no longer resolve.

repo: pulumi/pulumi-yaml


text:
Is it possible to add jamming beams as a secondary weapon?

I recognize that jamming beams are really complicated to automate and dealing with them is very unmapped territory.

Possibly but as you note it gets strange quickly in terms of if you land a jam, what is the optimal token to remove, etc. I might add it at some point with some predictable heuristic, but over multiple attacks it's not necessarily easy to decide what the best jam target is.

authors: boredompwndu punkUser


text:
[Bug]: o código funciona perfeitamente fora do modo headless, porém com o modo ativo, ele nao consegue avançar em etapa, nem lançar erros, sem nenhum tipo de erro aparente, a seguir, meu código:

Minimal, reproducible example
const puppeteer = require('puppeteer');
const config = require('./config.json');
const IptuRepository = require('./Repository/IptuRepository.js');
const fs = require('fs');
const pdf = require('pdf-parse');
const axios = require('axios');

async function GuiasDeIptu() {

  const browser = await puppeteer.launch({
    headless: true,
    defaultViewport: null,
    args: ['--enable-javascript'],
  });
  const page = await browser.newPage();

  // console.log("Iniciei");
  await page.goto('https://e-gov.betha.com.br/cdweb/03114-365/contribuinte/directlogin.faces?iEntidades=t4EiJk503gM%3D&iDatabases=25QN-yzeEPY%3D');
  console.log("Entrei na url");

  const emitir = await page.$('div[class=\'icone emitir\'] span');
  await emitir.click();
  console.log("cliquei em emitir");

  const cndImovel = await page.$x('//*[@id="3"]/div[2]/ul/li[2]/a');
  await cndImovel[0].click();

  console.log("cliquei em cnd");
  const connectionDb = new IptuRepository(config);

  let input = await connectionDb.gatherSequence();

  // console.log("Input do banco de dados:", input);

  //////////////////seleciona caixa input
  await page.waitForSelector('#mainForm\\:iImoveis', { visible: true });
  const imvBt = await page.$('#modoAcesso > div.grid > div:nth-child(4) > div > div > div > a');
  await imvBt.click();
  console.log("esta visivel");

// transforma o result input atual em string
  let inputString = input.toString();

  ///////////escreve a input
  await page.$eval('#mainForm\\:iImoveis', (inputField, value) => {
    inputField.value = value;
  }, inputString);
  await page.click('#mainForm\\:btIImoveis');

  console.log('escrevi input');

  //////////////botao input
  await page.waitForSelector('#mainForm\\:btIImoveis');
  await page.click('#mainForm\\:btIImoveis');

await page.waitForTimeout(1000);
  await page.waitForSelector('#mainForm\\:t-imoveis > tbody > tr > td:nth-child(5) > img');

      await page.click('#mainForm\\:t-imoveis > tbody > tr > td:nth-child(5) > img');
  ////esperar a pagina carregar o novo browser
   const newTarget = await browser.waitForTarget(target => target.opener() === page.target());

   const newPage = await newTarget.page();

   console.log('espernado cnd ');
    //////////// Aqui estaria o erro, é uma pagina que esta abrindo um pdf o qual quero pegar
    console.log('esperenado cnd');
   console.log( await newPage.content());

   const pdfUrl = await newPage.url();
   //// obter o link do pdf
   console.log(pdfUrl);

   ///utilizando axios do js para obter o response de pdf
   const response = await axios.get(pdfUrl, { responseType: 'arraybuffer' });
   const pdfBuffer = response.data;

  // Ussando pdf-parse para extrair texto do PDF
  const responseCND = (await pdf(pdfBuffer)).text;

  console.log(responseCND);
   return responseCND.text;

  await browser.close();
}

GuiasDeIptu().then((response) => {
  // Faça algo com a resposta, se necessário
  // Encerre o processo Node.js
  process.exit();
}).
  catch((error) => {
    console.error('Ocorreu um erro:', error);

    // Encerre o processo Node.js com um código de erro
    process.exit(1);
  });

Error string
no error
Bug behavior

[ ] Flaky
[ ] PDF

Background
Estou usando o puppeter para web scraping, a página a qual quero usar abre uma nova página com uma função Js que carrega um pdf feito na hora, o tempo de espera normalmente é de 5/6 segundos. Fora do modo headless ele funciona perfeitamente, porém no modo headlees que é q qual eu quero usar ela não funciona em nenhum momento.
Expectation
Eu espero que o código consiga esperar o tempo para carregamento do pdf, para que eu possa pegar o link para baixar e fazer o parse. Também gostaria que a ferramenta lançasse um erro, e a resposta de vocês sobre o porque não funcionar no headless.
Reality
Ele trava, nao lança erro, mesmo com o triplo do tempo de espera ele nao avança e nao lança erro.
Puppeteer configuration file (if used)
No response
Puppeteer version
PS C:\Users\alani\OneDrive\Área de Trabalho\pupetter_test> npm list puppeteer alani@ C:\Users\alani ├─┬ pdf-puppeteer@1.1.11 │ └── puppeteer@21.3.8 deduped └── puppeteer@21.3.8
Node version
v18.15.0
Package manager
npm
Package manager version
9.5.0
Operating system
Windows

Please update your Bug report to English so I can review it properly.
Also please make a smaller reproducible example only using puppeteer without external packages. as the site you provide can't be access on our end.

English mate. https://www.deepl.com/en/translator

Está atualizado.

Provavelmente algo relacionado ao Chrome headless não ter um visualizador de PDF #1872 . Você pode tentar usar o modo New Headless no Chrome e ver se isso resolve seu problema. Para usá-lo no Puppeteer
const browser = await puppeteer.launch({
    headless: 'new',
    defaultViewport: null,
    args: ['--enable-javascript'],
  });

Obrigada amigo, deu certo!

Provavelmente algo relacionado ao Chrome headless não tem um visualizador de PDF #1872 . Você pode tentar usar o modo New Headless no Chrome e ver isso resolver seu problema. Para usá-lo no Puppeteer
const browser = await puppeteer.launch({
    headless: 'new',
    defaultViewport: null,
    args: ['--enable-javascript'],
  });

Provavelmente algo relacionado ao Chrome headless não tem um visualizador de PDF #1872 . Você pode tentar usar o modo New Headless no Chrome e ver isso resolver seu problema. Para usá-lo no Puppeteer
const browser = await puppeteer.launch({
    headless: 'new',
    defaultViewport: null,
    args: ['--enable-javascript'],
  });

Obrigada amigo, deu certo!

Provavelmente algo relacionado ao Chrome headless não tem um visualizador de PDF #1872 . Você pode tentar usar o modo New Headless no Chrome e ver isso resolver seu problema. Para usá-lo no Puppeteer
const browser = await puppeteer.launch({
    headless: 'new',
    defaultViewport: null,
    args: ['--enable-javascript'],
  });

Obrigada amigo, deu certo!

Caso queira visualizar o navegador execultando os comandos, podera ultilizar o seguinte:
{
headless: false,
executablePath: "C:/Program Files/Google/Chrome/Application/chrome.exe"
}

repo: puppeteer/puppeteer


text:
[Bug]: chrome.runtime or window.chrome.runtime not accessible in DOM

Bug description
Steps to reproduce the problem:

Create a new Puppeteer window with headless: false

const puppeteer = require('puppeteer');

(async () => {
const options = {
  headless: false,
  devtools: true,
  ignoreHTTPSErrors: true,
}

const browser = await puppeteer.launch(options);
const page = await browser.newPage();
await page.goto('https://example.com');

const window_chrome = await page.evaluate(() => {
      return typeof window.chrome.runtime;
   });

const chrome_runtime = await page.evaluate(() => {
      return typeof chrome.runtime;
   });

console.log(window_chrome, chrome_runtime);

})();

Try to access window.chrome.runtime  or chrome.runtime object. The same can be done via both browser and via console.log in the method above

Further Info

puppeteer.executablePath() shows <curr_dir>/node_modules/puppeteer/.local-chromium/mac-901912/chrome-mac/Chromium.app/Contents/MacOS/Chromium
I tried setting the executablePath to my local chrome, but that didn't help either (exact same issue)
Why do we need this? To have communication between an extension background.js and the main page DOM, the suggested method is to use chrome.runtime.sendMessage and chrome.runtime.onMessage.addListener but because this does not exist, the communication isn't working.

Puppeteer version
11.0.0
Node.js version
16.3.0
npm version
8.1.0
What operating system are you seeing the problem on?
macOS
Relevant log output
Promise {
  <pending>,
  [Symbol(async_id_symbol)]: 68,
  [Symbol(trigger_async_id_symbol)]: 5,
  [Symbol(destroyed)]: { destroyed: false }
}
> undefined undefined

Closing this since I understood that this communication can be done between contentScript.js and background.js and need not happen through the DOM directly


text:
[Bug]: Installation fails when using yarn --modules-folder=not_node_modules

Bug description
Steps to reproduce the problem:
$ mkdir puppeteer-failure-case
$ cd puppeteer-failure-case
$ yarn init --yes
$ yarn add puppeteer
$ rm -rf node_modules
$ yarn install --modules-folder=test

yarn install v1.22.4
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 🔨  Building fresh packages...
error /Users/evan/Coding/puppeteer-failure-case/test/puppeteer: Command failed.
Exit code: 1
Command: node install.js
Arguments:
Directory: /Users/evan/Coding/puppeteer-failure-case/test/puppeteer
Output:
node:internal/modules/cjs/loader:927
  const err = new Error(message);
              ^

Error: Cannot find module 'progress'
Require stack:
- /Users/evan/Coding/puppeteer-failure-case/test/puppeteer/lib/cjs/puppeteer/node/install.js
- /Users/evan/Coding/puppeteer-failure-case/test/puppeteer/install.js
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:927:15)
    at Function.Module._load (node:internal/modules/cjs/loader:772:27)
    at Module.require (node:internal/modules/cjs/loader:999:19)
    at require (node:internal/modules/cjs/helpers:93:18)
    at Object.<anonymous> (/Users/evan/Coding/puppeteer-failure-case/test/puppeteer/lib/cjs/puppeteer/node/install.js:24:36)
    at Module._compile (node:internal/modules/cjs/loader:1095:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1124:10)
    at Module.load (node:internal/modules/cjs/loader:975:32)
    at Function.Module._load (node:internal/modules/cjs/loader:816:12)
    at Module.require (node:internal/modules/cjs/loader:999:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/Users/evan/Coding/puppeteer-failure-case/test/puppeteer/lib/cjs/puppeteer/node/install.js',
    '/Users/evan/Coding/puppeteer-failure-case/test/puppeteer/install.js'
  ]
}
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Puppeteer version
12.0.1
Node.js version
16.5.0
npm version
yarn  1.22.4
What operating system are you seeing the problem on?
Linux, macOS
Relevant log output
No response

I'm having nearly the exact same error message when trying to install puppeteer.  There are just a few slight differences in the numbers on the end of the lines and mine is Module._load instead of Function.Module._load (and a few other like that).  I've tried adding via yarn add and also manually adding to package.json (puppeteer v14.1.0) and I get the same error for both.
yarn install v1.22.18
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
error /path-to-project/public/assets/vendor/puppeteer: Command failed.
Exit code: 1
Command: node install.js
Arguments:
Directory: /path-to-project/public/assets/vendor/puppeteer
Output:
node:internal/modules/cjs/loader:939
  const err = new Error(message);
              ^

Error: Cannot find module 'progress'
Require stack:
- /path-to-project/public/assets/vendor/puppeteer/lib/cjs/puppeteer/node/install.js
- /path-to-project/public/assets/vendor/puppeteer/install.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:939:15)
    at Module._load (node:internal/modules/cjs/loader:780:27)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/path-to-project/public/assets/vendor/puppeteer/lib/cjs/puppeteer/node/install.js:23:36)
    at Module._compile (node:internal/modules/cjs/loader:1105:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Module._load (node:internal/modules/cjs/loader:827:12)
    at Module.require (node:internal/modules/cjs/loader:1005:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/path-to-project/public/assets/vendor/puppeteer/lib/cjs/puppeteer/node/install.js',
    '/path-to-project/public/assets/vendor/puppeteer/install.js'
  ]
}

Commands
yarn add puppeteer or yarn install (after adding puppeteer to package.json)
Node version: 18.1.0
Yarn version: 1.22.18
OS
I'm having this happen on mac using a laravel homestead environment and also on our stage user that is running ubuntu 20.


text:
Updated "Running the image" example

test.js doesn't even exist anymore in this folder

What kind of change does this PR introduce?

Did you add tests for your changes?
If relevant, did you update the documentation?
Summary

Does this PR introduce a breaking change?

Other information

Closed due to lack of activity.

authors: NinoSkopac OrKoN


text:
(BKR-584) Change to use mkdir_p helper command

Makes command cross-compatible for PSWindows

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1678/
Test FAILed.

@puppetlabs-jenkins retest this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1765/
Test PASSed.

authors: kevpl petems puppetlabs-jenkins

repo: puppetlabs/beaker


text:
(maint) Fix broken Windows acceptance tests

Starting with Bolt 3.0, we no longer include the bolt function in the
PuppetBolt PowerShell module and instead shipped with a batch file for
Windows packages that would run the Bolt executable. When this change
was made acceptance tests were broken as the PATH did not include the
path to Bolt's bin/ directory and the test would error with a "bolt is
not a recognized command" message.
During the beaker setup process (specifically step 032), beaker
updates the PATH to include Bolt's bin/ directory. Previously, the
script responsible for this used the Join-Path cmdlet with multiple
positional arguments, which is not supported in PowerShell < 6.0,
resulting in the PATH not getting updated. Updating this line to not
error correctly sets the PATH for the step that sets it, but the
PATH is not preserved between PowerShell sessions. This resulted in
the tests continuing to fail since bolt was not recognized as a
command.
This change updates the bolt_command_on helper method to set the
PATH prior to invoking bolt, ensuring that the PATH is correctly
configured every time Bolt is run.
!no-release-note

Ran locally and confirmed that this results in acceptance tests passing with a Windows controller:
$ bundle exec beaker-hostgenerator windows2019-64bolt%2Cwinrm. --hypervisor abs --disable-default-role --osinfo-version 1 > hosts.yaml
$ bundle exec beaker --log-level debug --hosts hosts.yaml --tests tests --preserve-hosts never --keyfile ~/.ssh/id_rsa-acceptance --options config/package/options.rb

...

      Test Suite: tests @ 2021-07-06 14:27:15 -0700

      - Host Configuration Summary -

              - Test Case Summary for suite 'tests' -
       Total Suite Time: 347.57 seconds
      Average Test Time: 19.31 seconds
              Attempted: 18
                 Passed: 10
                 Failed: 0
                Errored: 0
                Skipped: 8
                Pending: 0
                  Total: 18

      - Specific Test Case Status -

repo: puppetlabs/bolt


text:
(BOLT-345) Provide summary of successful and failed nodes

Provides a summary at the end of a run of which nodes succeeded and
failed that can be copied and re-run via --nodes.

This makes me want a --quiet option more.

CLA signed by all contributors.

authors: MikaelSmith puppetcla


text:
(BUG) Negotiation fails for servers where 'NTLMv2 session security' i…

Negotiation fails for servers where 'NTLMv2 session security' is required
If a server has specified that  NTLMv2 session security is required,
then negotiation will fail as the client does not advertise this during
the handshake.    The negoiate message needs to include the relevant
flag 'negotiateFlagNTLMSSPNEGOTIATEEXTENDEDSESSIONSECURITY'
To test enable this on the remote server by using regedt32 to modify the
key
HKLM\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\NtlmMinServerSec and
set the value to 0x20080000

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Dave Johnston seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant davejohnston

repo: puppetlabs/go-ntlmssp


text:
(PUP-1601) Refactor split and regsubst to 4x API

Refactors the 3x functions to 4x API. Also adds more stringent
type checks and permits patterns to be sent as strings, regexps,
or regexp types.
A parameter restriciton is imposed when using precompiled regexps
or regexps types so that the flags are restricted to 'G' (global
substitution). Flags affectingn the actual regexp are not permitted
since that would mean recompiling the regexp. This approach was
chosen based on the assumption that regexp flags will be properly
implemented in the Puppet Parser in the future.

CLA signed by all contributors.

Reminder: since this guts the 3x versions, and people may be calling these functions from other 3x functions via scope, we should add a note to documentation about how to call them e.g.
closure_scope().function_foo()

authors: hlindberg puppetcla thallgren

repo: puppetlabs/puppet


text:
(PUP-4501) Fix TypeCalculator.instance_of? for PStringType

The current instance_of? method does not consider the values
of the string type. This commit adds that check.

CLA signed by all contributors.

authors: puppetcla thallgren


text:
(PUP-5761) Log warning instead of raising error when bad keys are detected in module data

This PR changes the behavior when validating the data of a module data provider so that:

It is no longer considered an error if a key is unqualified. Instead a warning is logged.
The validation works the same way for all types of module data providers (a design flaw prevented the Hiera module data provider from validating correctly).

Details can be found in the commit comments.

made some very picky comments - I am fine merging anyway, let me know if you want to do those small fixed @thallgren  ?

authors: hlindberg thallgren


text:
(PUP-10959) Lock loader hierarchy instead of individual loaders

This makes loaders aware of the environment they are loading for and then attempts to lock with the environment instead of synchronizing each loader instance on itself.

Did you do any multithreaded benchmarking with this? I don't think we need to block merging it on that, but I know we were wondering if it would be slower to share a central lock.

I didn't, though I don't think it's high risk. Worst case it still isn't slower than the current way of running.

authors: Magisus pcarlisle


text:
(DO NOT MERGE)(DOCS) Add PuppetDB 5.2.5 and 6.0.1 release notes

This commit adds the release notes for PuppetDB 5.2.5 and 6.0.1. Please distribute to the relevant branches.

Test PASSed

Test PASSed

Waiting for CLA signature by @clairecadman
@clairecadman - We require a Contributor License Agreement (CLA) for people who contribute to Puppet, but we have an easy click-through license with instructions, which is available at https://cla.puppet.com/
Note: if your contribution is trivial and you think it may be exempt from the CLA, please post a short reply to this comment with details. http://docs.puppet.com/community/trivial_patch_exemption.html

closing in favor of #2670 and #2672 which break up docs per branch. Thanks @clairecadman!

authors: Zak-Kent clairecadman puppetcla puppetlabs-jenkins

repo: puppetlabs/puppetdb


text:
Allow changing legacy_origin

Sometimes you don't want to use the default from params.pp

Fixes #423

Can we acceptance test this scenario?

@cyberious I don't see why this needs acceptance test, the only thing it's changing is a file, which is unit-tested

authors: cyberious mhaskel

repo: puppetlabs/puppetlabs-apt


text:
xDnsClientGlobalSetting - Unable to set DNS Search Suffix using dsc_xdnsclientglobalsetting: Access to a CIM resource was not available to the client

I have the following Puppet code running on a Windows 2012 R2 node (version 1.2.0 of the DSC module, and 2.1.0 of Powershell):
dsc_xdnsclientglobalsetting{ 'dns_add_search_suffixes':
  dsc_issingleinstance => 'Yes',
  dsc_suffixsearchlist => $search_domains,
  dsc_usedevolution    => false,
}

When I run this on the agent, I get the following error:
Invoke-DscResource : PowerShell DSC resource MSFT_xDnsClientGlobalSetting  failed to execute Set-TargetResource functionality with error message: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Access to a CIM resource was not available to the client.
At C:\Users\csodadmin\Documents\test3.ps1:17 char:5
+     Invoke-DscResource @invokeParams
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (root/Microsoft/...gurationManager:String) [Invoke-DscResource], CimException
    + FullyQualifiedErrorId : ProviderOperationExecutionFailure,Microsoft.PowerShell.DesiredStateConfiguration.Commands.InvokeDscResourceMethodCommand

The Puppet code gets translated to this:
function new-pscredential
{
  [CmdletBinding()]
  param (
    [parameter(Mandatory=$true,
      ValueFromPipelineByPropertyName=$true)]
    [string]
    $user,

    [parameter(Mandatory=$true,
      ValueFromPipelineByPropertyName=$true)]
    [string]
    $password
  )

  $secpasswd   = ConvertTo-SecureString $password -AsPlainText -Force
  $credentials = New-Object System.Management.Automation.PSCredential ($user, $secpasswd)
  return $credentials
}

$response = @{
  indesiredstate = $false
  rebootrequired = $false
  errormessage   = ''
}

$invokeParams = @{
  Name          = 'xDnsClientGlobalSetting'
  Method        = 'set'
  Property      = @{
    issingleinstance = 'Yes'
    suffixsearchlist = @('domain1.corp', 'domain2.corp', 'domain3.corp', 'domain4.corp', 'domain5.com', 'domain6.corp', 'domain7.corp')
    usedevolution = $false
  }
  ModuleName = @{
    ModuleName      = "C:/ProgramData/PuppetLabs/puppet/cache/lib/puppet_x/dsc_resources/xNetworking/xNetworking.psd1"
    RequiredVersion = "3.0.0.0"
  }
}

try{
    $result = Invoke-DscResource @invokeParams
}catch{
  $response.errormessage   = $_.Exception.Message
  return ($response | ConvertTo-Json -Compress)
}

# keep the switch for when Test passes back changed properties
switch ($invokeParams.Method) {
  'Test' {
    $response.indesiredstate = $result.InDesiredState
    return ($response | ConvertTo-Json -Compress)
  }
  'Set' {
    $response.indesiredstate = $true
    $response.rebootrequired = $result.RebootRequired
    return ($response | ConvertTo-Json -Compress)
  }
}

When I manually run this (get/test run successfully, set throws this error) in a Powershell ISE session on the node with a -Verbose switch, I get the following additional information:
Invoke-DscResource : PowerShell DSC resource MSFT_xDnsClientGlobalSetting  failed to execute Set-TargetResource functionality with error message: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Access to a CIM resource was not available to the client.
At C:\Users\csodadmin\Documents\test3.ps1:17 char:5
+     Invoke-DscResource @invokeParams
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (root/Microsoft/...gurationManager:String) [Invoke-DscResource], CimException
    + FullyQualifiedErrorId : ProviderOperationExecutionFailure,Microsoft.PowerShell.DesiredStateConfiguration.Commands.InvokeDscResourceMethodCommand

VERBOSE: Performing the operation "Invoke-CimMethod: Resourceset" on target "MSFT_DSCLocalConfigurationManager".
VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = Resourceset,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' = root/Microsoft/Windows/DesiredStateConfiguration'.
VERBOSE: An LCM method call arrived from computer TST-SB001 with user sid S-1-5-21-2572414471-1943467713-2787779731-500.
VERBOSE: [TST-SB001]: LCM:  [ Start  Set      ]  [[xDnsClientGlobalSetting]DirectResourceAccess]
VERBOSE: [TST-SB001]:                            [[xDnsClientGlobalSetting]DirectResourceAccess] Set-TargetResource: Setting DNS Client Global Settings.
VERBOSE: [TST-SB001]:                            [[xDnsClientGlobalSetting]DirectResourceAccess] Set-TargetResource: Setting DNS Client Global Settings parameter SuffixSearchList to "System.Object[]".
VERBOSE: [TST-SB001]:                            [[xDnsClientGlobalSetting]DirectResourceAccess] Set-TargetResource: Setting DNS Client Global Settings parameter UseDevolution to "False".
VERBOSE: [TST-SB001]: LCM:  [ End    Set      ]  [[xDnsClientGlobalSetting]DirectResourceAccess]  in 0.7500 seconds.
VERBOSE: Operation 'Invoke CimMethod' complete.

I can't see where the Invoke-CimMethod is being invoked or how I can try to dig into this further, but my use case seems pretty simple.  I'm using version 1.2.0 of the DSC module, and 2.1.0 of Powershell.  There are no switches to this task to pass credentials if this happens to be a permissions issue.  While this was ran as a local administrator on the machine, I tried to run Powershell ISE as a domain administrator and I get the following error instead:
Invoke-DscResource : Access denied
At C:\Users\csodadmin\Documents\test3.ps1:17 char:5
+     Invoke-DscResource @invokeParams
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : PermissionDenied: (root/Microsoft/...gurationManager:String) [Invoke-DscResource], CimException
    + FullyQualifiedErrorId : HRESULT 0x80041003,Microsoft.PowerShell.DesiredStateConfiguration.Commands.InvokeDscResourceMethodCommand

VERBOSE: Performing the operation "Invoke-CimMethod: Resourceset" on target "MSFT_DSCLocalConfigurationManager".
VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = Resourceset,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' = root/Microsoft/Windows/DesiredStateConfiguration'.
VERBOSE: Operation 'Invoke CimMethod' complete.

Any help or suggestions are appreciated :)

Am I right in understanding you were able to reproduce this behavior after taking Puppet out of the picture?

I took the code that puppet emitted for that particular DSC module and dropped it into the Powershell IDE.  The same error that I get in a puppet run was also obtained by running it in the Powershell IDE.
On Wednesday, January 4, 2017 9:57 AM, Rob Reynolds <notifications@github.com> wrote:

Am I right in understanding you were able to reproduce this behavior after taking Puppet out of the picture?—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Just to close the loop on this...I believe the underlying issue is that our DNS Search Suffix is managed by Active Directory, and is not editable via the DSC module or direct powershell calls.  The generic error of 'access denied' makes sense from this perspective, but isn't immediately obvious when it first appears.

repo: puppetlabs/puppetlabs-dsc


text:
(maint) Prevent the generate command from overwriting the CA

Previously, the generate command would overwrite any existing CA files
in the target locations. This meant that if a user called
generate more than once, they could accidentally nuke thier CA,
thereby making all certs issued by it invalid. This commit makes the
command exit if any of the CA files already exist, and prompts the user to
remove them manually if they really want to regenerate their CA.

That's a good point, we probably should.

Updated import now as well.

Gonna do the nasty rebase for this once https://github.com/puppetlabs/puppetserver-ca-cli/pull/21 has been merged.

Superseded by https://github.com/puppetlabs/puppetserver-ca-cli/pull/22

repo: puppetlabs/puppetserver-ca-cli


text:
go.mod: update kevinburke/ssh_config dependency

The previous version contained an error which could cause a program to
panic if a read error occurred while parsing the ssh config file. The
latest version fixes this problem.
This change also removes a dependency.
See kevinburke/ssh_config@14846fb743b68bface9321da06f8d83a6bfa7924 for
more information.
Contributions to this project require sign-off consistent with the Developers Certificate of Origin. This can be as simple as using git commit -s on each commit.

Also, we ask everyone contributing to sign their agreement to a Developer Certificate of Origin (already linked in your PR message). You can add this as easily as git commit --amend -s. Would you mind adding it?

Okay, I've made the requested changes.

authors: MikaelSmith kevinburke

repo: puppetlabs/wash


text:
设置跨域代理

描述问题 (Describe the problem)
为什么在vite.config.ts中设置跨域代理无效
如何复现该问题 (How to reproduce the problem)
proxy: {
'^/admin':'http://192.168.1.70/'
},
操作系统和浏览器信息 (Operating system and browser information)
No response
验证 (Verify)

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

新手多看文档 github的issues 只用来解决bug
https://www.bilibili.com/video/BV1kg411v7QT/

repo: pure-admin/vue-pure-admin


text:
Support for KeyboardEvent, MouseEvent, ...

Currently, we have
addEventListener :: forall eff. EventType
                 -> EventListener (dom :: DOM | eff)
                 -> Boolean
                 -> EventTarget
                 -> Eff (dom :: DOM | eff) Unit

where EventListener (dom :: DOM | eff) is basically a function Event -> Eff eff a (why not Eff eff Unit?).
In order to add support for KeyboardEvent, MouseEvent, .., we would need a way to add event listeners of the form KeyboardEvent -> _ instead of Event -> _. Otherwise, there would only be unsafe ways to convert Event to KeyboardEvent within the listener (?). That's certainly not a good design choice.
So how can this be fixed on the type level? Is it useful to annotate EventType with the type of the event? (sounds weird, but currently, EventType is just a string indicating the sort/kind/type of event). I would be happy to implement support for keyboard and mouse events, but I don't have the experience to choose the best way to proceed here...

I did consider doing this, using phantom types with EventType to specify the expected event type, but thought maybe it was too opinionated for this library. We'd also need duplicate EventType values for some events, as the same name can raise different types for some events.
Currently you can do it in a safe but clunky way: using readKeyboardEvent (toForeign ev).

authors: garyb sharkdp

repo: purescript-contrib/purescript-dom


text:
How to aggregate the lines

From the documentation it is unclear to me how you could do anything else than do a line-by-line transformation of the input, because the only way of handling input is by means of the line handler, which can only handle a single independent line.
E.g. how would you write a program that sums all the input lines with a number and prints the result?

This question is likely best answered by seeing what the general solution would be in JavaScript and then seeing what the idiomatic translation to PureScript would be.
When this question was not asked, we did not have complete bindings for readline. As of v10.0.0, we do. If the problem can be resolved using this module, then it should be easy to translate the JS solution to a PS one. If it cannot, then the problem isn't with this library's bindings.
I'd search and then ask on StackOverflow.
Closing.

authors: JordanMartinez chtenb


text:
Event handlers

Are the functions allowing attaching callbacks to various operations of the WebSocket missing?
I could write my own foreign function to do it given I have the WebSocket at hand but I was curious if this is something that was forgotten or whether there is a way to do it within the current library.

You mean the ability to addEventListener, and so on?
You can do that with what's here and the dependencies it pulls in - you need to cast the socket with toEventTarget, and then you can use Web.Event.EventTarget.addEventListener. That's the pattern in general for the web libraries, every type that supports it should have cast functions to each of the interfaces it supports.

Thank you very much!

authors: garyb pavlosgi

repo: purescript-web/purescript-web-socket


text:
🛑 Puro.earth Registry Services API is down

In 3db75a6, Puro.earth Registry Services API (https://rs.api.puro.earth/$API_SERVICES_HEALT_ENDPOINT) was down:

HTTP code: 503
Response time: 5472 ms

Resolved: Puro.earth Registry Services API is back up in 63533d2.

repo: puro-earth/status


text:
ReactNativeScannerView" was not found in the UIManager

Invariant Violation: requireNativeComponent: "ReactNativeScannerView" was not found in the UIManager.

@deeps0903

React native version
@pushpendersingh/react-native-scanner version
Are you using newArch?
Please share the "npx react-native info" command output.

@pushpender-singh-ap
React native version -> "0.64.4"
@pushpendersingh/react-native-scanner version -> "^1.1.0-beta.2"
Are you using newArch? -> enable new architecture for android (by addig newArchEnabled=true in gradle.properties )
Please share the "npx react-native info" command output. -> Not Found :-

In React Native, the introduction of 'newArch' came with version 0.68. However, your current version is 0.64. To leverage the new architecture, it's crucial to upgrade React Native to a minimum of version 0.70. Following the upgrade, ensure to enable the 'newArch' for both platforms. Once this is accomplished, you can seamlessly incorporate the functionality of the '@pushpendersingh/react-native-scanner' library by installing the stable 1.0.2 version of the library

okay! Thanks

i'm using 0.72.0 and newArchEnabled=true，still report “Possible Unhandled Promise Rejection (id: 0):
Invariant Violation: requireNativeComponent: "ReactNativeScannerView" was not found in the UIManager.
Invariant Violation: requireNativeComponent: "ReactNativeScannerView" was not found in the UIManager.”

@xiongxiongjiang Would you mind sharing a sample project with us? It would be immensely helpful for us to accurately diagnose and address the issue at hand.


text:
Unit tests for PreparedGet #69

Closes #69
Unit tests for PreparedGet
@artem-zinnatullin PTAL

Great job :+1:

Updated =)

authors: artem-zinnatullin nikitin-da

repo: pushtorefresh/bamboo-storage