text:
More informative status message for Vendor Patient and Bundle upload

Pull requests into Cypress require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Submitter:

[ ] This pull request describes why these changes were made.
[ ] Internal ticket for this PR:
[ ] Internal ticket links to this PR
[ ] Code diff has been done and been reviewed
[ ] Tests are included and test edge cases
[ ] Tests have been run locally and pass

Reviewer 1:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

repo: projectcypress/cypress


text:
Predictions outside of schedule list

During the last days I get often weired prediction data: Sometimes I get predictions for the past, which is not too problematic.
But I get also results which do not reflect the scheduled starts for the starting point in question:
Sometimes there are schedules missing, sometimes there are predictions outside of start schedules.
See the appended HC where are predictions #1,# 2,# 3 for the weekday of sunday, (Dec. 18) at which there is no start schedule on the list, as there are only services from Monday to Friday.

We've done a bunch of work on how predictions are generated since this issue was created - can you confirm its still an issue?

Hello again,
As far as I can see, this error has been fixed.

source: gharchive/issue

authors: TheSkorm Torrehoradada

repo: projecthorus/sondehub-tracker

license: MIT

license_type: permissive

license_source: github-api


text:
Add default_admin_set_generator

Adds the default_admin_set generator.
Fixes #237
Present tense short summary (50 characters or less)
Adds a generate called by:
rails generate hyrax:default_admin_set
This is NOT included in the insall generator stack as teh admin set requires a running fedora instance on create.
@projecthydra-labs/hyrax-code-reviewers

@mjgiarlo That was my original goal, yes. So any guidance in how we may tackle that based on the need for the fedora server would be great.

I don't know the impact of this being part of the boot sequence of the application. However I had suggested allowing the default admin set to be part of the Hyrax.config.
I believe we could add an after_prepare hook to the Rail tie that would ensure the AdminSet is created. See Hydra::Groupy for examples of to_prepare (https://github.com/projecthydra-labs/hydra-groupy/blob/master/lib/hydra/groupy/railtie.rb)

That would work for me, and I don't know if we have any better hooks for firing when e.g. Fedora spins up. IMO it's reasonable to assume that backend services are already up when Rails initializes.

@jeremyf Cool. So the to_prepare in railtie you have here runs at the end of the rails boot process? Then checking if there is a Default admin set as part of the config makes a lot more sense. I'll take a stab at that this afternoon sometime. Thanks!

FYI - This isn't working yet. Don't merge just because it passed ;-)

@scholarworks please update the title of this PR to reflect what is actually happening.

Closing in lieu of clean branch PR #477.

source: gharchive/pull-request

authors: jcoyne jeremyf mjgiarlo scholarworks

repo: projecthydra-labs/hyrax


text:
Move ProductTypes to JSON files

For more portability and some upcoming changes, we need to move the data from the ProductTypes to JSON files.
These should be stored in:
config/mods/:mod_name/product_types/:product_type.json
There could be one or more product types in that DIR.

Adding to backlog for now until Monday when we discuss with Thoughtbot.

This will be handled elsewhere as a side-effect.

authors: OBCENEIKON calebthompson chriskacerguis

repo: projectjellyfish/api

license_source: bigquery


text:
Adds UX for archiving projects

Converts the "Edit" button to a group now including "Archive", said button is disabled when a project has services that are active.
Hijacks the delete project action to act as archive (rather than delete).
Updates relevant directives on the project.details state to suppress actions when a project is archived.
Items of additional note:

archived table doesn't show till there's cause
confirmation modal gets wacky due to the source button being placed in the upper right, on the agenda, another pr to revert confirmation modal to be centered

Feedback based on screenshots

"ARCHIVED" is mispelled as "ACHEIVED"
The confirmation modal is half off the screen, directive accepts placement parameters.
Archive and Edit have been "smushed" together.

Instead of passing in a new parameter called projectArchived which if left alone and later we needed to add an additional check to each directive we'd end up with logic checking multiple values. In fact we see this already happening with the services directive.
Another approach would be to pass in a function to test against if the directive should allow modifications or should allow xyz action to happen.

:+1:

authors: AllenBW stackus


text:
When using precompiled assemblies, raw binary output is shown

This only repros in functions-next, not in prod.

The correct thing is to show function.json, so the title is correct.
Here are the contents of my function.json.
{
  "scriptFile": "..\\bin\\CoderCardsWebsite.dll",
  "entryPoint": "CoderCardsLibrary.CardGenerator.Run",
  "bindings": [
    {
      "name": "image",
      "type": "blobTrigger",
      "direction": "in",
      "path": "%input-container%/{filename}.jpg",
      "connection": "AzureWebJobsStorage"
    },
    {
      "type": "blob",
      "name": "outputBlob",
      "path": "%output-container%/{filename}.jpg",
      "connection": "AzureWebJobsStorage",
      "direction": "out"
    }
  ],
  "disabled": false
}

I'll give you RBAC access to repro.

@ahmelsayed I've given you access to resource group donnam-vs-demo2 in the donnam-msft directory. Let me know if you have problems accessing.

repo: projectkudu/AzureFunctionsPortal


text:
For non 200 http codes, portal shows response in a hard to read way

e.g. if my function returns a 400 with body:
{
  "error": "Please pass first/last properties in the input object"
}

The portal output displays this:
{"_body":"{\r\n  \"error\": \"Please pass first/last properties in the input object\"\r\n}","status":400,"statusText":"Ok","headers":{"Pragma":["no-cache"],"Date":["Fri"," 11 Mar 2016 02:53:49 GMT"],"Server":["Microsoft-IIS/8.0"],"X-AspNet-Version":["4.0.30319"],"X-Powered-By":["ASP.NET"],"Content-Type":["text/plain; charset=utf-8"],"Cache-Control":["no-cache"],"Content-Length":["72"],"Expires":["-1"]},"type":2,"url":"https://functions.azure.com/api/passthrough"}

I think it would be best to display the response content the same way as for success (the same way that postman does). Potentially, it could show the HTTP code above the box. Then if people want more than that, they can use postman, which we can never equal.

Thanks. Later we can think of ways of displaying the http code. It could be some little status bar above the output. e.g. postman has:

repo: projectkudu/WebJobsPortal


text:
Kudu routinely misses Web Job invocations

We have a critical Web Job that uses a Timer Trigger to run every 5 minutes that is a single-point of failure for a broader system. Because of this, we've instrumented up monitoring via the Kudu azurejobs/api/jobs/continuous/{webJobName}/functions?limit={maxExecutedFunctionsCount} API. We evaluate the results send notifications if the most recent successful invocation has aged more than 20 minutes.
However, we get a TON of false notifications indicating that the Web Job hasn't run successfully for over 20 minutes, when it has. The issue appears to be that Kudu does not correctly log some executions in its back-end for return via the API listed above.
Here are some screen snippets that illustrate the issue:

According to the log stream from Kudu, the job triggered at 13:50 and 13:55.
However, in Kudu's invocation list, the execution at 13:55 is missing:

It isn't simply a delay issue because you can see the invocation at 14:00 showing. The 13:55 was just completely skipped!
If this happens more than 3 times consecutively, we get the false notification, scramble to respond to the support incident, only to discover that the job did in fact invoke successfully. This happens a handful of times per day, so it is a huge issue for the support of this system.
Request:

Obviously, this needs to be fixed.
In the meantime, if anyone has an alternative suggestion for how to best monitor that this Web Job is invoking as expected, please share!

NOTE: The Web Job is running within an Azure App Service deployment.

Hi
If the problem persists and is related to running it on Azure App Service, please open a support incident in Azure:
https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request
This way we can better track and assist you on this case
Thanks,
Joaquin Vano
Azure App Service

authors: bojingo jvano

repo: projectkudu/kudu


text:
Accesible user guide

Added editor's accessible user guide.

something odd with this PR... redoing.

repo: projecttacoma/bonnie


text:
use value and naming system when finding unique QRDA entries

Pull requests into cqm-parsers require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Submitter:

[ ] This pull request describes why these changes were made.
[ ] Internal ticket for this PR:
[ ] Internal ticket links to this PR
[ ] Code diff has been done and been reviewed
[ ] Tests are included and test edge cases
[ ] Tests have been run locally and pass

Reviewer 1:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Codecov Report

Merging #48 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #48      +/-   ##
==========================================
+ Coverage    89.2%   89.21%   +<.01%
==========================================
  Files          68       68
  Lines        1686     1687       +1
==========================================
+ Hits         1504     1505       +1
  Misses        182      182

Impacted Files
Coverage Δ

lib/qrda-import/base-importers/section_importer.rb
91.72% <100%> (+0.05%)
:arrow_up:

Continue to review full report at Codecov.

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

authors: codecov-io dczulada

repo: projecttacoma/cqm-reports


text:
Carthage Install failure

Yoshi fails to build during carthage install, as it fails to find swiftlint.
*** xcodebuild output can be found in /var/folders/4v/ht9_lyvj4615x2rc_pdq3mnc0000gn/T/carthage-xcodebuild.h7n8es.log
*** Building scheme "Yoshi" in YoshiExample.xcworkspace
2016-04-27 19:21:42.321 xcodebuild[32993:1185701] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/Lin.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2016-04-27 19:21:42.322 xcodebuild[32993:1185701] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/KSImageNamed.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2016-04-27 19:21:42.324 xcodebuild[32993:1185701] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/FuzzyAutocomplete.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2016-04-27 19:21:42.324 xcodebuild[32993:1185701] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/BBUFullIssueNavigator.xcplugin' not present in DVTPlugInCompatibilityUUIDs
** BUILD FAILED **

The following build commands failed:
	PhaseScriptExecution SwiftLint /Users/mike/Library/Developer/Xcode/DerivedData/YoshiExample-ezojbuubfnsxbbfnuqeunkpdrrxq/Build/Intermediates/Yoshi.build/Release-iphonesimulator/Yoshi.build/Script-27AFFEF51C6574B400C656BA.sh
(1 failure)
/Users/mike/Desktop/test proj bro/Carthage/Checkouts/Yoshi/Yoshi/Yoshi/YoshiActionResult.swift:23: warning: Trailing Newline Violation: File should have a single trailing newline (trailing_newline)
/Users/mike/Desktop/test proj bro/Carthage/Checkouts/Yoshi/Yoshi/Yoshi/YoshiActionResult.swift:13: warning: Line Length Violation: Line should be 120 characters or less: currently 124 characters (line_length)
A shell task failed with exit code 65:
2016-04-27 19:21:42.321 xcodebuild[32993:1185701] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/Lin.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2016-04-27 19:21:42.322 xcodebuild[32993:1185701] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/KSImageNamed.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2016-04-27 19:21:42.324 xcodebuild[32993:1185701] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/FuzzyAutocomplete.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2016-04-27 19:21:42.324 xcodebuild[32993:1185701] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/BBUFullIssueNavigator.xcplugin' not present in DVTPlugInCompatibilityUUIDs
** BUILD FAILED **

The following build commands failed:
	PhaseScriptExecution SwiftLint /Users/mike/Library/Developer/Xcode/DerivedData/YoshiExample-ezojbuubfnsxbbfnuqeunkpdrrxq/Build/Intermediates/Yoshi.build/Release-iphonesimulator/Yoshi.build/Script-27AFFEF51C6574B400C656BA.sh
(1 failure)

Carthage now installs with the changes from #39

repo: prolificinteractive/Yoshi

license: mit


text:
Issue with PD integration (or how to debug)

What did you do?
I try to send alert from prometheus to PD. Some of them are failing and don't are ingested by PD.
Summary : there are surely a bad json generated but how to debug it ?
What did you expect to see?
An alert in PD.
What did you see instead? Under which circumstances?
so the alerts is not sent and here the log file :
level=error ts=2019-10-24T13:29:13.862Z caller=notify.go:372 component=dispatcher msg="Error on notify" err="cancelling notify retry for \"pagerduty\" due to unrecoverable error: unexpected status code 400: Event object format is unrecognized: JSON parse error" context_err=null
level=error ts=2019-10-24T13:29:13.862Z caller=dispatch.go:266 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="cancelling notify retry for \"pagerduty\" due to unrecoverable error: unexpected status code 400: Event object format is unrecognized: JSON parse error"

Environment
docker / linux basics

Alertmanager version:

0.19

Prometheus version:

2.9.2

Alertmanager configuration file:

global:
    resolve_timeout: 5m
inhibit_rules:
-   equal:
    - cloud
    - region
    - env
    - role
    - alertgroups
    source_match:
        severity: critical
    target_match:
        severity: warning
receivers:
-   name: default
    slack_configs:
    -   api_url: https://hooks.slack.com/services/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
        channel: '#alerts'
        send_resolved: true
-   name: slack
    slack_configs:
    -   actions:
        -   style: danger
            text: '{{ template "csq.slack.silence.text" . }}'
            type: button
            url: '{{ template "csq.slack.silence.link" . }}'
        -   style: primary
            text: '{{ template "csq.slack.dashboard.text" . }}'
            type: button
            url: '{{ template "csq.slack.dashboard.link" . }}'
        -   style: primary
            text: '{{ template "csq.slack.confluence.text" . }}'
            type: button
            url: '{{ template "csq.slack.confluence.link" . }}'
        -   style: primary
            text: '{{ template "csq.slack.grafana.text" . }}'
            type: button
            url: '{{ template "csq.slack.grafana.link" . }}'
        api_url: https://hooks.slack.com/services/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
        channel: '{{ template "csq.slack.channel" . }}'
        color: '{{ template "csq.slack.color" . }}'
        fields:
        -   short: true
            title: cloud
            value: '{{ .CommonLabels.cloud }}'
        -   short: true
            title: region
            value: '{{ .CommonLabels.region }}'
        -   short: true
            title: env
            value: '{{ .CommonLabels.env }}'
        -   short: true
            title: role
            value: '{{ .CommonLabels.role }}'
        icon_emoji: '{{ template "csq.slack.emoji" . }}'
        image_url: '{{ template "csq.slack.image" . }}'
        send_resolved: true
        short_fields: true
        text: '{{ template "csq.slack.text" . }}'
        title: '{{ template "csq.slack.title" . }}'
-   name: pagerduty
    pagerduty_configs:
    -   description: '{{ template "csq.pagerduty.description" . }}'
        details:
            alertname: '{{ .CommonLabels.alertname }}'
            cloud: '{{ .CommonLabels.cloud }}'
            env: '{{ .CommonLabels.env }}'
            region: '{{ .CommonLabels.region }}'
            role: '{{ .CommonLabels.role }}'
        send_resolved: true
        service_key: '{{ template "csq.pagerduty.service_key" . }}'
        severity: '{{ .CommonLabels.severity }}'
route:
    group_by:
    - cloud
    - region
    - env
    - role
    - alertname
    group_interval: 5m
    group_wait: 1m
    receiver: default
    repeat_interval: 1h
    routes:
    -   continue: false
        match:
            test: 'yes'
        receiver: slack
    -   continue: false
        group_by:
        - '...'
        match:
            env: production
        receiver: pagerduty
    -   continue: false
        receiver: slack
templates:
- /etc/alertmanager/templates.tmpl

Prometheus configuration file:

NA

Logs:

level=error ts=2019-10-24T13:29:13.862Z caller=notify.go:372 component=dispatcher msg="Error on notify" err="cancelling notify retry for \"pagerduty\" due to unrecoverable error: unexpected status code 400: Event object format is unrecognized: JSON parse error" context_err=null
level=error ts=2019-10-24T13:29:13.862Z caller=dispatch.go:266 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="cancelling notify retry for \"pagerduty\" due to unrecoverable error: unexpected status code 400: Event object format is unrecognized: JSON parse error"

Hmm, it could be that there's network hiccup resulting in the posted payload being truncated? AFAICT the notify/pagerduty code itself can't generate invalid JSON.

No network issue, this is reproductible with the alert. My question is still the same : how to debug ?
I think I will finish by hack the code by myself to add some debug log.
Another interesting one :
level=error ts=2019-10-24T14:21:08.917Z caller=dispatch.go:266 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="cancelling notify retry for \"pagerduty\" due to unrecoverable error: unexpected status code 400: Event object is invalid: 'routing_key' must be provided in the body, or provided in the headers using 'x-routing-key'"

with this configuration
-   name: pagerduty
    pagerduty_configs:
    -   description: '{{ template "csq.pagerduty.description" . }}'
        send_resolved: true
        severity: '{{ .CommonLabels.severity }}'
        details:
            alertname: '{{ .CommonLabels.alertname }}'
            cloud: '{{ .CommonLabels.cloud }}'
            env: '{{ .CommonLabels.env }}'
            region: '{{ .CommonLabels.region }}'
            role: '{{ .CommonLabels.role }}'
    routing_key: '{{ template "csq.pagerduty.service_key" . }}'

and this work with this modified conf :
-   name: pagerduty
    pagerduty_configs:
    -   description: '{{ template "csq.pagerduty.description" . }}'
        routing_key: '{{ template "csq.pagerduty.service_key" . }}'
        send_resolved: true
        severity: '{{ .CommonLabels.severity }}'
        details:
            alertname: '{{ .CommonLabels.alertname }}'
            cloud: '{{ .CommonLabels.cloud }}'
            env: '{{ .CommonLabels.env }}'
            region: '{{ .CommonLabels.region }}'
            role: '{{ .CommonLabels.role }}'

just change the order of the routing key.
I know yaml and templating are ugly but still.
I really think we miss some error checking in the integration code.

Re your last comment, I suspect that {{ template "csq.pagerduty.service_key" . }} expands to the empty string. There needs to be a check in the notifier about this.
As for debugging, yes you'll have to add some logs yourself and rebuild Alertmanager.

two comment : so yes it expands to nothing but due to previous error in the templating.
So maybe some code refacto is needed to the templating in multiple pass ?!
also why don't add some debug info ? and more generaly an option to debug templating isssue ?

Sorry but I'm not following, you didn't mention any templating errors before. Can you provide more details?

Ok I will to be more clear.
So we state that the order of the field in the yaml change something.
For example if we had a problem in the templating certainly in details (for example we miss some fields) and the routing key is after in the conf file the message with be not send cause the routing key field is empty.
This is why I suggest to do a two pass: First with mandatory field, and second with optionnal; cause we are never sure that are fields will be filled.
Anyway : I persist that having an option to see the result of the templating in a debug file would be really helpful.

So we state that the order of the field in the yaml change something.

It shouldn't.

For example if we had a problem in the templating certainly in details (for example we miss some fields) and the routing key is after in the conf file the message with be not send cause the routing key field is empty.

In case of templating errors, Alertmanager should return immediately and not send anything to PagerDuty.

Closing it. With https://github.com/prometheus/alertmanager/pull/2085, Alertmanager should now detect when routing/service keys are empty after templating and it should report the error in the logs.

repo: prometheus/alertmanager


text:
Added circleci config to run tests

Cont #196
Closes #177
Closes #152
This PR adds circleCI workflow to run basic tests on the prombench repository, the lint check was not added because it's failing.
It'll be good to fix the issues make lint is currently showing and then add lint to .circleci/config.yml in another PR.

Hm wondering why a job is not started here with this new circle ci config. I checked the circle ci settings and it seems to be enabled for this repo.

please open a new issue for make lint and maybe @nikita-mk 	can help with that one.

okay and I think it will work after the file is on merged to master, test master on a different repo: (https://github.com/testpromorg/prombench/pull/6)

Thanks!

authors: geekodour krasi-georgiev

repo: prometheus/prombench


text:
Improve Prometheus Startup Times

Proposal
Prometheus keeps 2 hours of WALs which need to be read on each Prometheus startup. Prometheus instances that ingest a lot of data need to read tens of gigabytes (or more), which means startup times can be very slow (it can last a few minutes). During this time Prometheus doesn't scrape metrics and alerting doesn't work as well.
The main goal of this issue would be to make the startup times short and the same no matter the activity of the Prometheus instances.
There are many ways to improve this, so I'm keeping this issue open for all possibilities.

We have a bunch of tracking and design docs for this, from general to specific:
https://docs.google.com/document/d/11NUjmCOoMjhbs4UlJmAOPa2Bir9akytkRkvTqGSDxe0/edit#heading=h.3o4u97rijjfb
https://docs.google.com/document/d/184urkLQnM7rqLmGvS66I15jU2pyPk_qwd8v_qDlXczo/edit?usp=sharing
https://docs.google.com/document/d/1pnEsxB0CDLOxQipGw_vhkJpoDZfZPs_KjqCriumDAXQ/edit#
In general, I don't think tracking things in an issue in addition to the above is helpful.

We have been looking at this during our bug scrub and we have decided to close it as this is discussed into other issues as mentioned by @beorn7 .

authors: beorn7 kustodian roidelapluie

repo: prometheus/prometheus


text:
Prevent number of remote write shards from going negative.

This can happen in the situation where the system scales up the number of shards massively (to deal with some backlog), then scales it down again as the number of samples sent during the time period is less than the number received.
(Cherry pick of 1d94eb8d into 1.7, see #2969)

Thanks. :+1:


text:
Tsdb StartTime : Use a simplier way to compute StartTime

Should fix #3340
cc @fabxc

Thank you @Thib17 for jumping in so quickly. I've to apologize though. Yesterday morning I read the previous code as traversing all series for a particular job. In fact, it just probed the first one. So my statement on the total cost were false.
Nonetheless, this greatly simplifies some of the logic which is always good. Thanks a lot!


text:
Persist alert 'for' state across restarts

Addresses #422
Design:

Store the time (ActiveAt) in nanoseconds in the series when the alert goes to Pending or Firing state. We add this sample in the series during every Eval.
If it goes to Inactive state, then store -1 in the series.
While restoring for state, we query for the time range (currentTime-holdDuration, currentTime), and if we find any samples in the series, we restore ActiveAt accordingly.

@brian-brazil PTAL, I have fixed some comments since last time. These 2 comments were not very clear though.
https://github.com/prometheus/prometheus/pull/4061#discussion_r183417333
https://github.com/prometheus/prometheus/pull/4061#discussion_r183417614

@brian-brazil I have updated the PR. Now the timestamp of the sample is being used to check for 'firing' state. Control flow has been modified to restore the state after the first Eval.

I've given it a quick test. When an alert stops firing it seems that the two ALERTS series aren't getting marked stale.
The flag names also need changing, as these settings are not AM related.

I think they should have been marked stale at least after few Eval if not active, as that part of code was not tinkered. I will give it a test and see what is the issue.
And about the flags:
alertmanager.outage-tolerance => for-outage-tolerance
alertmanager.for-grace-period => for-grace-period?

The flags still need a prefix, rule.alert... would be one option.

This?
rules.alert.for-outage-tolerance
rules.alert.for-grace-period

It's as good as anything.

@brian-brazil I don't see why the series won't be marked stale when the alert becomes inactive, the original logic is still in place. Did you observe that even 1-2 Evals after it became inactive?

Yes, it seemed to be that way even after waiting a bit.

@brian-brazil while testing for that I found a bug in another place where samples were not being added if alertHoldDuration was less than hold duration (as it was not set as restored).
The series was being marked stale after that (I did not test it before that fix).

That seems to be working okay now. Can you ensure all your commits have a DCO?

@brian-brazil There was an error while rebasing to change commit messages. Can this PR be merged without DCO for some commits ([very]old commits)?

We require DCO on all commits. You could try squashing.

@brian-brazil Many issues while trying to change commit messages. With some methods there is a conflict, and with another method I get
The previous cherry-pick is now empty, possibly due to conflict resolution.

Try squashing everything into one commit. That should bypass all that.

@brian-brazil It's done.

I haven't used Borgmon in 4 years or used Prometheus in 9 months ( 😭 ) but this is so great ❤

authors: brian-brazil codesome seanjfellows


text:
update inconsistent comment

update inconsistent comment in file storage/remote/storage.go.
Signed-off-by: aixeshunter aixeshunter@gmail.com

@codesome Thanks!

:+1:

Thanks!

authors: aixeshunter brian-brazil codesome


text:
Merge fanout module into fanout directory

Merge fanout module into fanout directory.
When I was writing the test class, I found that fanout.go was easy to cause the problem of "import cycle", so I created a "fanout" folder.
This PR is to move fanout from "storage" to "fanout" folder. Otherwise, there will be two files with the same name of "fanout_test.go"

This doesn't seem right. How were the tests passing if there was a cycle preventing a build?

This doesn't seem right. How were the tests passing if there was a cycle preventing a build?

storage/fanout_test.go->util/teststorage.go.New->storage/storage.Storage

This doesn't seem right. How were the tests passing if there was a cycle preventing a build?

The four methods of fanout.go (add addfast commit rollback) currently have no test classes, which should also be caused by the failure to import "teststorage. Go.New"

Hi @liguozhong, thanks for the PR, but unfortunately a lot of the code around this has been refactored. Could you see if the change you want is still relevant with the new code? If yes, could you open another PR for it?

authors: brian-brazil gouthamve liguozhong


text:
add vendor to this project

some package need to download ,please add vendor

In general this repository is a library and not a full application. A command line tool exists but in a very early state. In general, libraries should not have vendor/ directories in Go.

Closing this as won't fix. As said above, this is a lib and its highly unlikely we will add a vendor folder. But if you have good reasons for a vendor folder, please feel free to re-open.

authors: Gouthamve fabxc timchenxiaoyu

repo: prometheus/tsdb


text:
feat: prompt syntax for llama3

Related issue: https://github.com/promptfoo/promptfoo/issues/912

Thank you so much for this contribution @fvdnabee. I am going to clean it up a little, add tests, and get it deployed today!

@typpo and @fvdnabee - can you please take a look at this? You can run it with npm run local --  eval -c examples/amazon-bedrock/promptfooconfig.llama.yaml --no-cache

authors: fvdnabee mldangelo

repo: promptfoo/promptfoo


text:
iOS WKWebview Localtunnel Plugin

This pr creates a new plugin file: CDVWKLocalTunnel. This is a swift implementation of the Localtunnel plugin using WKWebivew.
Right now it handles the following:

scraper_xerox sync
scraper_xerox register
scraper_fis_with_register webdriver account creation
incapsula issues / captcha (I think this is working, but I have not been able to see an actual recaptcha from google??)

TODO In this PR

Fix a display issue. Some of the time (still not sure exact cause), when the localtunnel closes, the Freshebt app is left slightly zoomed in

TODO as follow up

Add in special redirect handling (I think this is needed for OK)

@rammie @lippytak what are the other edge cases I will need to deal with?

Server pr to turn off setting user agents server side

Add in special redirect handling (I think this is needed for OK)
Indeed, this is specifically for OK password expiration in case that helps.

@rammie @lippytak what are the other edge cases I will need to deal with?
Not much...I don't think any of these are directly related to this implementation but the few things on my mind in the ballpark are:

The recent CA DNS exceptions when we moved to localtunnel (https://sentry.easyfoodstamps.com/sentry/ebenefits-prod/issues/670609/?query=is%3Aunresolved)
Make sure to support the force CAPTCHA option in the debugger

I'll let you know if other things come to mind.

authors: lippytak paetling

repo: propelinc/cordova-plugin-inappbrowser


text:
Enable to load phing with composer

Enable to load phing with composer and add phing in autoload.php.dist

We should use a PEAR package instead.

See the last section on this page: http://packagist.org/about-composer

I have seen i do it tonight ;)
2012/1/31 William DURAND <
reply@reply.github.com

See the last section on this page: http://packagist.org/about-composer

Reply to this email directly or view it on GitHub:
https://github.com/propelorm/Propel2/pull/127#issuecomment-3735218

Any news Cédric?

done

@willdurand have you encounter bugs with the last phing version into your env ?

Nope, but I need to check if my fix has been added ;)
Le 14 févr. 2012 à 20:09, cedric lombardotreply@reply.github.com a écrit :

@willdurand have you encounter bugs with the last phing version into your env ?

Reply to this email directly or view it on GitHub:
https://github.com/propelorm/Propel2/pull/127#issuecomment-3967542

Can you rebase your commit?

Yes and i think that it not work anymore, now we need to tell that repository of phing is a "type": "pear"

Nevermind Cedric, it's no more used (almost).

authors: cedriclombardot willdurand


text:
what should be done if the randomly chosen provider is unresponsive?

Currently pops up with error but allows retry

impl block rollover

authors: HughParry goastler

repo: prosopo/procaptcha


text:
Launch cutover checklist

This issue is a holding pen for pre-launch items to be worked shortly before or day of launch. Please amend this comment to add more. We can move to separate issues as needed when launch is closer.

[x] Make repo public (and protect any branches necessary to make PRs cleaner)
[ ] Reconfigure repo perms to remove any unnecessary access
[ ] Set up DNS for domain name
[x] Update public repo readme, URL, etc
[ ] Confirm Speedcurve is pulling in data
[ ] Confirm Countly metrics are pulling in production data
[ ] Confirm social cards include image (see https://github.com/protocol/nft-website/issues/18#issuecomment-846311221 )

Have a DNS request open with @andyschwab for pointing nftschool.dev 😊

🎉  https://nftschool.dev/

Tested social cards in Slack, iMessage, Twitter, Facebook.

Tested Countly, Speedcurve are relaying production data. Good to close this issue!

authors: andyschwab jessicaschilling

repo: protocol/nft-website


text:
Add Climatematch Academy

Insert URLs to the project here:
https://academy.climatematch.io/
https://github.com/ClimateMatchAcademy/course-content
In one sentence, explain what the project is about:
A wide-reaching, inclusive and approachable program aimed to introduce computational methods for climate science.

[x] The projects is active, documented, open source licensed, shows usage from external parties and is directly targeting environmental sustainability. Find more details in the Contribution Guide.

Lots of broken links in their readme

Yes, I know. Had had to google for the deployed website, but the content is really great!

I created a PR to fix this: https://github.com/ClimateMatchAcademy/course-content/pull/276

It look like this project is maintained in a fork: https://github.com/neuromatch/climate-course-content

Links and content is now be updated here: https://github.com/neuromatch/climate-course-content

@nsea-log @iamzoltan @WesleyTheGeolien @jlpearso

@Ly0n thanks :)

authors: Ly0n andrew iamzoltan

repo: protontypes/open-sustainable-technology


text:
Add Plant Trait Ontology

Insert URLs to the project here:
https://github.com/Planteome/plant-trait-ontology

[x] The projects is active, documented, open source licensed, shows usage from external parties and is directly targeting environmental sustainability. Find more details in the Contribution Guide.

All issues labeled as 'Good First Issue' of the project listed on OpenSustain.tech will be visible on ClimateTriage.com. This is a great way to welcome new community members to your project.

@cooperl09 @elserj


text:
[Bug]: prowler/prowler: line 525: ((: 600 > : syntax error: operand expected (error token is "> ")

I'm getting the following error on Alpine Linux v3.16 - prowler/prowler: line 525: ((: 600 > : syntax error: operand expected (error token is "> ")
I'm not sure when this started, I just happened to be looking at the logs from my prowler run for an unrelated reason.

Hi @zfLQ2qx2, could you please input the bug issue template?
We need the debug output executing bash -x ./prowler 1>debug.txt 2>&1 to trace this error.
Doing an initial investigation the problem seems to be in the $SESSION_TIME_REMAINING variable, so if this value is empty the following error appears:
bash-5.1$ (( 500 > )) && echo si
bash: ((: 500 > : syntax error: operand expected (error token is "> ")

Please, test it again with Prowler at master branch because we've recently fix some issues in the assume_role logic.
Thanks!

I suspect this commit is the issue -- 1b63256b9cb0c6f6e47022fc219024b27943e33c
The date command appears to be the most non-portable thing ever, I've done several Prowler patches in the past for this, every platform seems to have its own date variant that takes wildly different options and input formats.
Since there is already some python in prowler, would be great if someone wrote a "universal" replacement for date. I tried once but my python skills aren't good enough.
I did a patch that used jq at one point instead since it seems to have the same output on every platform and jq is already used widely in the prowler checks.
I'll have time to debug in the next couple days if nobody beats me to it.

Hi @zfLQ2qx2 you're right, date command is a nightmare. The problem with that commit is that we've identified some abnormal behaviour using jq to parse some timestamps. The problem was describe here https://github.com/prowler-cloud/prowler/pull/1181
Also you can take a look at the jq issue here https://github.com/stedolan/jq/issues/2001#issuecomment-1145864809
The problem here is that the available date in AlpineLinux comes from busybox. Let me take a look into it. I'll keep you posted.

@jfagoagas Ah man! Good catch on stedolan's part. Yeah, Alpine does busybox which is great for containers (why I use it) but problem I've run into in the past is that even among different platforms that use busybox the compile time options and version of busybox result in binaries with very different capabilities. I think python would be the way to go since it seems to be a reoccurring and persistent problem.
I tested the previous commit 7930b449b3a341a0a45256ca99d21cced320074f and the error messages went away.

@zfLQ2qx2 Yes, that's the problem with the same command across multiple linux distributions.
One temporary solution is to use our official container image which is built on top of Amazon Linux to avoid this problem.
We're thinking how to support date from busybox at this moment but it's tough due to the different compilations and options in each distribution.

@jfagoagas one of my coworkers says it should be possible to write in python with only the base libraries, and it’s already used for the secret scanning so not a new requirement. I could whip one out in Perl or C in a minute but those come with a lot of overhead. One of the things I like best about Prowler is the most junior admin can look at the bash script and see how the checks work.

@jfagoagas idea! The jq solution did work except for the timezone, so maybe export TZ=UTC when calling it? You might want to do early on if you want all sub commands to run in UTC. Or you could just do it for the one place jq is called.

@jfagoagas one of my coworkers says it should be possible to write in python with only the base libraries, and it’s already used for the secret scanning so not a new requirement. I could whip one out in Perl or C in a minute but those come with a lot of overhead. One of the things I like best about Prowler is the most junior admin can look at the bash script and see how the checks work.

Yes! It is in our roadmap!

@jfagoagas idea! The jq solution did work except for the timezone, so maybe export TZ=UTC when calling it? You might want to do early on if you want all sub commands to run in UTC. Or you could just do it for the one place jq is called. I’m thinking the reason I didn’t see the timezone issue myself is I’m running my containers in UTC time.

Good point! We'll test it. And yes if you are running Prowler in UTC you are not experiencing the issue, it only appears in summertime timezones.

Please @zfLQ2qx2, check this PR https://github.com/prowler-cloud/prowler/pull/1195 and test it using this branch PRWLR-556-bug-prowler-prowler-line-525-600-syntax-error-operand-expected-error-token-is
I think this approach could work in every system.

Approach looks good, setting up a test run..

@jfagoagas Really awesome, switching back to master branch soon as I see the merge :)

Thank you! Merged!!!

repo: prowler-cloud/prowler


text:
Move functional tests into a more general location

Currently much of sql/translator.rs is functional tests testing the whole pipeline; e.g. here's 100 lines of them picked at random: https://github.com/prql/prql/blob/af3b5fb94fb7539307e50ef28cc40b47cfbb03bc/prql-compiler/src/sql/translator.rs#L1462-L1550.
We can:

move these to a separate file; either in a tests path, or into a test_lib.rs (or some similar name) file with unit tests designed for these
change all these parse(resolve_and_translate({query})) into just compile

I did some of this in https://github.com/prql/prql/pull/875, so I'll close this, but there's more to do here.

Maybe we can put them into test-databases/ so they are executed on at least SQLite and DuckDB?

I think this could be good, but one factor here is that having them in the examples path means they don't compile with --lib, and we want a fast write-compile-test cycle for that crate, so probably we don't want to mix it with starting a DB in-process... (Unless my estimate for how long that takes is too high)
We could definitely have them in a common location and then use them in both — I've been thinking of a more cohesive & complete set of tests, e.g. which test each stage of the compiler.

repo: prql/prql


text:
Unable to build v0.103

It fails with
$ make
....
go build -trimpath -modcacherw -ldflags "-X main.version=34 -s -w" ./cmd/karma
verifying github.com/go-openapi/spec@v0.20.5/go.mod: checksum mismatch
	downloaded: h1:2OpW+JddWPrpXSCIX8eOx7lZ5iyuWj3RYR6VaaBKcWA=
	go.sum:     h1:QbfOSIVt3/sac+a1wzmKbbcLXm5NdZnyBZYtCijp43o=

SECURITY ERROR
This download does NOT match an earlier download recorded in go.sum.
The bits may have been replaced on the origin server, or an attacker may
have intercepted the download attempt.

For more information, see 'go help module-auth'.

Am I doing something wrong here ?

Cannot reproduce, I suggest to clean you mod & build cache with go clean -modcache -cache

Thanks, that helped.

authors: alxric prymitive

repo: prymitive/karma


text:
Trying to connect 24-bit PCM5102 PCM5102A Stereo

I am stuck on this. I don't understand how to connect the board below. On the side of the esp32 is clear, but on the external dac SD, L/R, WS can not be found on the board. Also the BCK is in the colume ESP32. Could you please check this again.
External Dac 24-bit PCM5102 PCM5102A Stereo

I updated the documentation can you try it out and let me know the results ?

Thanks, that should do it. Only one thing you named XMT as XST.

corrected as well. Thanks for your feed back....

Can it be that L/R to GND is gone?

I found this connection diagram for a raspberry pi.
As you can see the FTL,DMP,SCL and FMT are connected to ground.

If I remember right, out of these only FMT is critical. I guess the others are connected to ground to have a defined state.
For DMP and FLT you could play around if setting it to high improves the quality.
I was really struggeling with this module and only when I started to set XMT to high it started to work for me.

I diden't test it yet. I let you know. I am trying to compile without disable the warnings. But without succes for now.

I hope the warnings are not coming from my library.
If so are you using the latest version ?

I downloaded them a while a go. The 4th of may to be precese. Are they addapted?

oh yes, I see now. Thanks

You might even consider to upgrade the ESP32 release to 2.0.0

What do you mean by upgrading the ESP32 release? Updating the boards of Arduino IDE?
The board works with you suggested wiring!
I just get noise when there is no music playing, even when the ESP32 is not powered on... Soo I think it is coming from my bad power supply I am currently using. The wiring is not solderd yet and the two GND of the power supply are currently not connected to each other. I will try it with my lineare regulated power supply. Would it help by setting the XSMT to low... This is what the datasheet tells me: Soft mute control : Soft mute (Low) / soft un-mute (High).

I did the following...
a2dp_sink.set_volume(0);
digitalWrite(PinMute,LOW);
Bound the grounds together
The noise remains. The only thing I can do as far as I know is place a filter around the power supply cable. Or use an other powersupply and solder the wires.

Is the sound muted when it's not connected?

In my code, the disconnect event is switching off I2S.
The only other setting related to noise that I am aware of is in
        i2s_config.tx_desc_auto_clear = true // avoiding noise in case of data unavailability

You might even consider to upgrade the ESP32 release to 2.0.0

You where right, there was a new release.
I followed the instruction
instruction

authors: podaen pschatzmann


text:
Status on Redux Package

Dug through the release notes and such, no mention, is the redux package discontinued moving forward?

When I originally implemented @curi/redux, the idea was to use Redux (and MobX because I made a package for that, too) to pass router/response data to components. The benefit of this was that it gave deep updates for "free", so I didn't have to setup some subscription system for people who use pure components/shouldComponentUpdate.
I removed the Redux package when React's new context was released because that is better suited for deep updates. Redux was no longer needed for passing the routing data and because of how the new context API's provider/consumer pairs work, there wasn't even a great way for "Curi aware" components to get their data from Redux instead.
While I generally think that linking Curi and Redux is not necessary, I'm not completely against bringing a Redux package back, but I would have to have a better understanding of the use cases. If you just want the responses to be in the store, that is easy enough, but if you wanted to use Redux as the sole source for passing response data throughout an application, then things might get a bit tricky.

Understood. I generally use Redux, for now anyway, as the single source of truth for both my component layer and my saga layer to know what to render/run. An example of my usage: https://github.com/bfillmer/greenfield/
Ultimately I have no reason not to just roll my own equivalent of syncResponses, I was about halfway through doing that myself originally when I found the Redux package for Curi.

If you run into any issues with that, please let me know.

authors: bfillmer pshrmn

repo: pshrmn/curi


text:
Add cmake to the pspdev container

I wasn't able to build my application with the pspdev container, because cmake is missing.

It seems make was also not installed, so I added that too

What you have done is not going to add anything to the container, there is a second stage that just copy the PSPDEV directory.
The strategy that I followed was to provide the tinies toolchain for being able to compile projects, but user would need to install some basic dependencies.
If you want to have a docker with a lot of tools installed I recommend to create another flavor, like pspdev:pspdev_full:latest

I guess. It's a bit problematic that cmake, make, gcc and g++ do not work in this container, though.

authors: fjtrujy sharkwouter

repo: pspdev/pspdev


text:
receve buffer size too small

https://github.com/psygames/UnityWebSocket/blob/89aedd6c3b2c6cde99a7ef0e30801393498a8357/Assets/UnityWebSocket/Scripts/Runtime/Implementation/NoWebGL/Default/WebSocket.cs#L221
receive buffer size too small, also send buffer size ?

fixed in 2.6.0

repo: psygames/UnityWebSocket


text:
Actual water temperature of Boiler

Hi  pszafer,
As you ask me I attached my rawscan. Also the screenshot of my sensors.
They are not made on the same time. As you see there are two Invalid sensors in my config.
Thx for your support so far.
bosch_scan.zip

I see it.  Actually you don't have these sensors.
Right now you can just delete those. In next version I will just stop adding sensors if they are not exist.

Hi Pszafer,
Can you explain how is it possible that these sensor are exest in my ProControl app? I guess that the data is available in the gateway, because it appairs in the app. Is it possible to add these in next version? Below all the info I can read from my heatpump. Its in Dutch, but under Warm water you see the actual hot water temperature. When it is not possible, then it stops and I will continue with other Home Assistant challenges :)

There is new version of component, which should cover your sensors.
Please test it. Closing issue for now. I'll reopen if you still have issue.

authors: Railittle pszafer


text:
Schema is missing

Prerequisites

[*] Is it a bug?
[ ] Is it a new feature?
[ ] Is it a a question?
[ ] Can you reproduce the problem?
[ ] Are you running the latest version?
[ ] Did you check for similar issues?
[ ] Did you perform a cursory search?

For more information, see the CONTRIBUTING guide.
Description
Description of the bug -
Couldn't import these queries
from graphql_auth.schema import UserQuery, MeQuery
Steps to Reproduce
If we need to reproduce and you don't provide steps for it, it will be closed. Alternatively, you can link a repo with the code to run your issue.

Try to import - from graphql_auth.schema import UserQuery, MeQuery
These are not found

Expected behavior
What you expected to happen
Should import UserQuery, MeQuery schemas.
Actual behavior
What actually happened
Requirements
Paste the packages you are using, you can get this information from executing pip freeze.

UserQuery and MeQuery are to be imported from graphql_auth.queries. That being said, the docs need to get updated.

repo: ptbang/django-graphene-auth


text:
Excuser API dosen't work

Hey, @Aniyo44 Thank You for opening an issue it seems that they have moved their website to a new domain.
I am working on it and will make the PR.
Thank You.

That API is just pulling some random ads now. Please avoid using it for a while

Hi @Aniyo44
Thanks for opening this issue ;)
We have some problems with Public APIs, so we won't be able to review/add this improvement right now.
Read this issue for more information, please: https://github.com/public-apis/public-apis/issues/3104

repo: public-apis/public-apis


text:
News API added

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

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

imma go find a corner to cry


text:
ruby 2.7: ensure keyword args are properly splatted

This fixes deprecations emitted on Ruby 2.7.0

It would appear seven_zip_ruby isn't yet ready for 2.7.0: masamitsu-murase/seven_zip_ruby/issues/31

masamitsu-murase/seven_zip_ruby/issues/31 has been closed and CI is now happy

masamitsu-murase/seven_zip_ruby/issues/31 has been closed and CI is now happy

authors: joshpencheon ollietulloch


text:
Use intermediate representation like Haskell "Core"

It would be useful to define a minimal simple functional intermediate language to which Roy can be compiled, analogous to Haskell Core.  This would:

clearly separate work on syntax and sugar from work on semantics.
simplify the task of defining Roy's semantics.
provide a language on which optimizations can be done.

I would then recommend defining a JS/JSON AST, and no-nonsense, plaintext, explicit syntax for this (e.g. something Lisp-like), for people working directly on Core.

repo: pufuwozu/roy


text:
Add types across modules

Though I'm not fully understand what this is.

Separate compilation.

authors: paulmillr pufuwozu


text:
Patron Group Review

Review Voyager Patron groups in the context of patrons who have an active barcode in more than one group. Also think about mapping the rather messy string labels to something more digestible for an API call.
See https://docs.google.com/a/princeton.edu/spreadsheets/d/1L0o8XDh2wJ27El8Da0Fh5nv6uxieV15uE9g1_K9etng/edit?usp=sharing for group names and current usage levels.
The response should provide the highest privilege group the patron is attached to.

A stat code of "EL" indicates someone is a Library Staff member. Patrons can have multiple stat codes attached to them.

On Alma this is moot.


text:
sw: Make compatible with non-12 LLVM versions

This targets the work-in-progress occamy branch, not main.
Make software build system work with LLVM versions other than 12.0.1 by:

Making LLVM lib paths adaptive to the version used
Fixing GNU C language violations in gemm.h: register may not be used with arrays (this was never legal to begin with, but the frontend lets it slide and the backend only fatals if it actually attempts to map registers)

Hi, this is quite exciting.
Which versions of LLVM will be tested?
Will it be the vanilla LLVM version or a custom/pulp one?
Thanks. Keep up the good work!


text:
RDS Cluster Parameter Group violates plan even without changes

Describe what happened
We recently enabled Pulumi "plan" in our CI/CD and we're facing an issue where an RDS cluster parameter group is violating the plan even when the changes are not related to this resource.
We are setting this parameters to our parameter group:
    parameters:
      param-1:
        name: "pg_stat_statements.track"
        value: "ALL"
      param-2:
        name: "pg_stat_statements.max"
        value: "10000"
        applyMethod: "pending-reboot"
      param-3:
        name: "shared_preload_libraries"
        value: "pgaudit,pg_stat_statements"
        applyMethod: "pending-reboot"
      param-4:
        name: "rds.logical_replication"
        value: "1"
        applyMethod: "pending-reboot"
      param-5:
        name: "wal_sender_timeout"
        value: "0"
      param-6:
        name: "max_replication_slots"
        value: "30"
        applyMethod: "pending-reboot"
      param-7:
        name: "idle_in_transaction_session_timeout"
        value: "1800000"
        applyMethod: "immediate"
      param-8:
        name: "max_wal_senders"
        value: "30"
        applyMethod: "pending-reboot"
      param-9:
        name: "pgaudit.role"
        value: "rds_pgaudit"
      param-10:
        name: "pgaudit.log"
        value: "all"
      param-11:
        name: "rds.force_ssl"
        value: "1"

The output error after running pulumi up --plan='plan.json'
error: resource urn:pulumi:infra-happyreturns-legacy-dev::aws-platform::hr:aws:ClusterParameterGroup$aws:rds/clusterParameterGroup:ClusterParameterGroup::dev-happyreturns-13/ClusterParameterGroup violates plan: properties changed: ~~parameters[{[{map[__defaults:{[{applyMethod}]} applyMethod:{immediate} name:{pgaudit.log} value:{all}]} {map[__defaults:{[]} applyMethod:{pending-reboot} name:{max_wal_senders} value:{30}]} {map[__defaults:{[]} applyMethod:{pending-reboot} name:{max_replication_slots} value:{30}]} {map[__defaults:{[]} applyMethod:{immediate} name:{idle_in_transaction_session_timeout} value:{1800000}]} {map[__defaults:{[{applyMethod}]} applyMethod:{immediate} name:{pgaudit.role} value:{rds_pgaudit}]} {map[__defaults:{[{applyMethod}]} applyMethod:{immediate} name:{wal_sender_timeout} value:{0}]} {map[__defaults:{[{applyMethod}]} applyMethod:{immediate} name:{rds.force_ssl} value:{1}]} {map[__defaults:{[]} applyMethod:{pending-reboot} name:{rds.logical_replication} value:{1}]} {map[__defaults:{[]} applyMethod:{pending-reboot} name:{pg_stat_statements.max} value:{10000}]} {map[__defaults:{[]} applyMethod:{pending-reboot} name:{shared_preload_libraries} value:{pgaudit,pg_stat_statements}]} {map[__defaults:{[{applyMethod}]} applyMethod:{immediate} name:{pg_stat_statements.track} value:{ALL}]}]}!={[{map[__defaults:{[]} applyMethod:{pending-reboot} name:{max_replication_slots} value:{30}]} {map[__defaults:{[]} applyMethod:{immediate} name:{idle_in_transaction_session_timeout} value:{1800000}]} {map[__defaults:{[]} applyMethod:{pending-reboot} name:{rds.logical_replication} value:{1}]} {map[__defaults:{[{applyMethod}]} applyMethod:{immediate} name:{wal_sender_timeout} value:{0}]} {map[__defaults:{[{applyMethod}]} applyMethod:{immediate} name:{pgaudit.log} value:{all}]} {map[__defaults:{[]} applyMethod:{pending-reboot} name:{pg_stat_statements.max} value:{10000}]} {map[__defaults:{[]} applyMethod:{pending-reboot} name:{max_wal_senders} value:{30}]} {map[__defaults:{[{applyMethod}]} applyMethod:{immediate} name:{rds.force_ssl} value:{1}]} {map[__defaults:{[{applyMethod}]} applyMethod:{immediate} name:{pgaudit.role} value:{rds_pgaudit}]} {map[__defaults:{[{applyMethod}]} applyMethod:{immediate} name:{pg_stat_statements.track} value:{ALL}]} {map[__defaults:{[]} applyMethod:{pending-reboot} name:{shared_preload_libraries} value:{pgaudit,pg_stat_statements}]}]}]
The pulumi plan file:
        "urn:pulumi:infra-happyreturns-legacy-dev::aws-platform::hr:aws:ClusterParameterGroup$aws:rds/clusterParameterGroup:ClusterParameterGroup::dev-happyreturns-13/ClusterParameterGroup": {
            "goal": {
                "type": "aws:rds/clusterParameterGroup:ClusterParameterGroup",
                "name": "dev-happyreturns-13/ClusterParameterGroup",
                "custom": true,
                "inputDiff": {
                    "updates": {
                        "parameters": [
                            {
                                "__defaults": [
                                    "applyMethod"
                                ],
                                "applyMethod": "immediate",
                                "name": "pgaudit.log",
                                "value": "all"
                            },
                            {
                                "__defaults": [],
                                "applyMethod": "pending-reboot",
                                "name": "max_wal_senders",
                                "value": "30"
                            },
                            {
                                "__defaults": [],
                                "applyMethod": "pending-reboot",
                                "name": "max_replication_slots",
                                "value": "30"
                            },
                            {
                                "__defaults": [],
                                "applyMethod": "immediate",
                                "name": "idle_in_transaction_session_timeout",
                                "value": "1800000"
                            },
                            {
                                "__defaults": [
                                    "applyMethod"
                                ],
                                "applyMethod": "immediate",
                                "name": "pgaudit.role",
                                "value": "rds_pgaudit"
                            },
                            {
                                "__defaults": [
                                    "applyMethod"
                                ],
                                "applyMethod": "immediate",
                                "name": "wal_sender_timeout",
                                "value": "0"
                            },
                            {
                                "__defaults": [
                                    "applyMethod"
                                ],
                                "applyMethod": "immediate",
                                "name": "rds.force_ssl",
                                "value": "1"
                            },
                            {
                                "__defaults": [],
                                "applyMethod": "pending-reboot",
                                "name": "rds.logical_replication",
                                "value": "1"
                            },
                            {
                                "__defaults": [],
                                "applyMethod": "pending-reboot",
                                "name": "pg_stat_statements.max",
                                "value": "10000"
                            },
                            {
                                "__defaults": [],
                                "applyMethod": "pending-reboot",
                                "name": "shared_preload_libraries",
                                "value": "pgaudit,pg_stat_statements"
                            },
                            {
                                "__defaults": [
                                    "applyMethod"
                                ],
                                "applyMethod": "immediate",
                                "name": "pg_stat_statements.track",
                                "value": "ALL"
                            }
                        ]
                    }
                },
                "outputDiff": {},
                "parent": "urn:pulumi:infra-happyreturns-legacy-dev::aws-platform::hr:aws:ClusterParameterGroup::dev-happyreturns-13",
                "protect": false,
                "provider": "urn:pulumi:infra-happyreturns-legacy-dev::aws-platform::pulumi:providers:aws::default_6_65_0::e8f0ea2d-b2a4-4641-8caf-67a5e4ffd5f6",
                "propertyDependencies": {
                    "description": [],
                    "family": [],
                    "name": [],
                    "parameters": [],
                    "tags": []
                },
                "deleteBeforeReplace": true,
                "customTimeouts": {}
            },
            "steps": [
                "same"
            ],
            "state": {
                "arn": "arn:aws:rds:us-west-2:374812476261:cluster-pg:dev-happyreturns-13",
                "description": "Managed by Pulumi",
                "family": "aurora-postgresql13",
                "id": "dev-happyreturns-13",
                "name": "dev-happyreturns-13",
                "namePrefix": "",
                "parameters": [
                    {
                        "applyMethod": "immediate",
                        "name": "idle_in_transaction_session_timeout",
                        "value": "1800000"
                    },
                    {
                        "applyMethod": "immediate",
                        "name": "pg_stat_statements.track",
                        "value": "ALL"
                    },
                    {
                        "applyMethod": "immediate",
                        "name": "pgaudit.log",
                        "value": "all"
                    },
                    {
                        "applyMethod": "immediate",
                        "name": "pgaudit.role",
                        "value": "rds_pgaudit"
                    },
                    {
                        "applyMethod": "immediate",
                        "name": "rds.force_ssl",
                        "value": "1"
                    },
                    {
                        "applyMethod": "immediate",
                        "name": "wal_sender_timeout",
                        "value": "0"
                    },
                    {
                        "applyMethod": "pending-reboot",
                        "name": "max_replication_slots",
                        "value": "30"
                    },
                    {
                        "applyMethod": "pending-reboot",
                        "name": "max_wal_senders",
                        "value": "30"
                    },
                    {
                        "applyMethod": "pending-reboot",
                        "name": "pg_stat_statements.max",
                        "value": "10000"
                    },
                    {
                        "applyMethod": "pending-reboot",
                        "name": "rds.logical_replication",
                        "value": "1"
                    },
                    {
                        "applyMethod": "pending-reboot",
                        "name": "shared_preload_libraries",
                        "value": "pgaudit,pg_stat_statements"
                    }
                ],
                "tags": {
                    "contact": "eng-cloud-infrastructure@happyreturns.com",
                    "env": "dev",
                    "hr:compliance:Framework": "SOC2",
                    "hr:cost:BusinessUnitID": "Engineering",
                    "hr:cost:CostCenter": "happyreturns",
                    "hr:cost:Owner": "CloudInfrastructure",
                    "hr:ops:Contact": "eng-cloud-infrastructure@happyreturns.com",
                    "hr:ops:Environment": "dev",
                    "hr:ops:IAC": "Pulumi",
                    "hr:ops:Owner": "CloudInfrastructure",
                    "hr:ops:hr:ops:ManagedBy": "aws-platform/infra-happyreturns-legacy-dev",
                    "pulumi-stack": "aws-platform/infra-happyreturns-legacy-dev",
                    "team": "devops"
                },
                "tagsAll": {
                    "contact": "eng-cloud-infrastructure@happyreturns.com",
                    "env": "dev",
                    "hr:compliance:Framework": "SOC2",
                    "hr:cost:BusinessUnitID": "Engineering",
                    "hr:cost:CostCenter": "happyreturns",
                    "hr:cost:Owner": "CloudInfrastructure",
                    "hr:ops:Contact": "eng-cloud-infrastructure@happyreturns.com",
                    "hr:ops:Environment": "dev",
                    "hr:ops:IAC": "Pulumi",
                    "hr:ops:Owner": "CloudInfrastructure",
                    "hr:ops:hr:ops:ManagedBy": "aws-platform/infra-happyreturns-legacy-dev",
                    "pulumi-stack": "aws-platform/infra-happyreturns-legacy-dev",
                    "team": "devops"
                }
            },
            "seed": "a++32PxL/DJpdZBkM4CHFPgCG6z6VA0tg3t+gbWC5A0="
        },
```

### Sample program

```
package main

import (
	"github.com/pulumi/pulumi-aws/sdk/v6/go/aws/rds"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := rds.NewClusterParameterGroup(ctx, "default", &rds.ClusterParameterGroupArgs{
			Name:        pulumi.String("rds-cluster-pg"),
			Family:      pulumi.String("aurora-postgresql13"),
			Description: pulumi.String("RDS default cluster parameter group"),
			Parameters: rds.ClusterParameterGroupParameterArray{
				&rds.ClusterParameterGroupParameterArgs{
					Name:  pulumi.String("pg_stat_statements.track"),
					Value: pulumi.String("ALL"),
				},
				&rds.ClusterParameterGroupParameterArgs{
					Name:  pulumi.String("pg_stat_statements.max"),
					Value: pulumi.String("10000"),
					ApplyMethod: pulumi.String("pending-reboot"),
				},
				&rds.ClusterParameterGroupParameterArgs{
					Name:  pulumi.String("shared_preload_libraries"),
					Value: pulumi.String("pgaudit,pg_stat_statements"),
					ApplyMethod: pulumi.String("pending-reboot"),
				},
				&rds.ClusterParameterGroupParameterArgs{
					Name:  pulumi.String("rds.logical_replication"),
					Value: pulumi.String("1"),
					ApplyMethod: pulumi.String("pending-reboot"),
				},
				&rds.ClusterParameterGroupParameterArgs{
					Name:  pulumi.String("wal_sender_timeout"),
					Value: pulumi.String("0"),
				},
				&rds.ClusterParameterGroupParameterArgs{
					Name:  pulumi.String("max_replication_slots"),
					Value: pulumi.String("30"),
					ApplyMethod: pulumi.String("pending-reboot"),
				},
				&rds.ClusterParameterGroupParameterArgs{
					Name:  pulumi.String("idle_in_transaction_session_timeout"),
					Value: pulumi.String("1800000"),
					ApplyMethod: pulumi.String("immediate"),
				},
				&rds.ClusterParameterGroupParameterArgs{
					Name:  pulumi.String("max_wal_senders"),
					Value: pulumi.String("30"),
					ApplyMethod: pulumi.String("pending-reboot"),
				},
				&rds.ClusterParameterGroupParameterArgs{
					Name:  pulumi.String("pgaudit.role"),
					Value: pulumi.String("rds_pgaudit"),
				},
				&rds.ClusterParameterGroupParameterArgs{
					Name:  pulumi.String("pgaudit.log"),
					Value: pulumi.String("all"),
				},
				&rds.ClusterParameterGroupParameterArgs{
					Name:  pulumi.String("rds.force_ss"),
					Value: pulumi.String("1"),
				},
			},
		})
		if err != nil {
			return err
		}
		return nil
	})
}
```

### Log output

_No response_

### Affected Resource(s)

_No response_

### Output of `pulumi about`

```
CLI
Version      3.143.0
Go Version   go1.23.4
Go Compiler  gc

Plugins
KIND      NAME        VERSION
resource  aws         6.65.0
resource  aws-native  1.4.0
language  go          3.143.0
resource  kubernetes  4.14.0
resource  random      4.16.3
resource  tls         4.11.1

Host
OS       darwin
Version  14.7
Arch     arm64

This project is written in go: executable='/opt/homebrew/bin/go' version='go version go1.23.2 darwin/arm64'

warning: Could not access the backend: read ".pulumi/meta.yaml": blob (key ".pulumi/meta.yaml") (code=Unknown): operation error S3: GetObject, https response error StatusCode: 400, RequestID: 4S0ZJW1YHHT7GEH4, HostID: OvhDtfNj/i3M7lYXadC0mDzirK7G2GG5SRopkwS6yWHxPOrNTrHi9QNgzEA2hKi3ZagVltpGnoPagkkXHZfa6g==, api error ExpiredToken: The provided token has expired.
Dependencies:
NAME                                        VERSION
github.com/go-viper/mapstructure/v2         v2.0.0
github.com/knadh/koanf                      v1.5.0
github.com/knadh/koanf/v2                   v2.1.1
github.com/pulumi/pulumi-aws-native/sdk     v1.4.0
github.com/pulumi/pulumi-aws/sdk/v6         v6.65.0
github.com/pulumi/pulumi-kubernetes/sdk/v4  v4.14.0
github.com/pulumi/pulumi/sdk/v3             v3.142.0
github.com/stretchr/testify                 v1.9.0
golang.org/x/exp                            v0.0.0-20240707233637-46b078467d37
github.com/pulumi/pulumi-random/sdk/v4      v4.16.3
github.com/pulumi/pulumi-tls/sdk/v4         v4.11.1
github.com/sethvargo/go-githubactions       v1.3.0
github.com/valyala/fastjson                 v1.6.4
```

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

oh sorry about the typo 🤦
Probably one thing to try is to create the resource beforehand and then try to run any other update using plan. This is exactly what we did.
The resources already existed when we implemented the plan usage.

Could you please provide a detailed repro?
Using this code:
package main

import (
	"github.com/pulumi/pulumi-aws/sdk/v6/go/aws/rds"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := rds.NewClusterParameterGroup(ctx, "default", &rds.ClusterParameterGroupArgs{
			Name:        pulumi.String("rds-cluster-pg"),
			Family:      pulumi.String("aurora-postgresql13"),
			Description: pulumi.String("RDS default cluster parameter group"),
			Parameters: rds.ClusterParameterGroupParameterArray{
				&rds.ClusterParameterGroupParameterArgs{
					Name:  pulumi.String("pg_stat_statements.track"),
					Value: pulumi.String("ALL"),
				},
				&rds.ClusterParameterGroupParameterArgs{
					Name:        pulumi.String("pg_stat_statements.max"),
					Value:       pulumi.String("10000"),
					ApplyMethod: pulumi.String("pending-reboot"),
				},
				&rds.ClusterParameterGroupParameterArgs{
					Name:        pulumi.String("shared_preload_libraries"),
					Value:       pulumi.String("pgaudit,pg_stat_statements"),
					ApplyMethod: pulumi.String("pending-reboot"),
				},
				&rds.ClusterParameterGroupParameterArgs{
					Name:        pulumi.String("rds.logical_replication"),
					Value:       pulumi.String("1"),
					ApplyMethod: pulumi.String("pending-reboot"),
				},
				&rds.ClusterParameterGroupParameterArgs{
					Name:  pulumi.String("wal_sender_timeout"),
					Value: pulumi.String("0"),
				},
				&rds.ClusterParameterGroupParameterArgs{
					Name:        pulumi.String("max_replication_slots"),
					Value:       pulumi.String("30"),
					ApplyMethod: pulumi.String("pending-reboot"),
				},
				&rds.ClusterParameterGroupParameterArgs{
					Name:        pulumi.String("idle_in_transaction_session_timeout"),
					Value:       pulumi.String("1800000"),
					ApplyMethod: pulumi.String("immediate"),
				},
				&rds.ClusterParameterGroupParameterArgs{
					Name:        pulumi.String("max_wal_senders"),
					Value:       pulumi.String("30"),
					ApplyMethod: pulumi.String("pending-reboot"),
				},
				&rds.ClusterParameterGroupParameterArgs{
					Name:  pulumi.String("pgaudit.role"),
					Value: pulumi.String("rds_pgaudit"),
				},
				&rds.ClusterParameterGroupParameterArgs{
					Name:  pulumi.String("pgaudit.log"),
					Value: pulumi.String("all"),
				},
				&rds.ClusterParameterGroupParameterArgs{
					Name:  pulumi.String("rds.force_ssl"),
					Value: pulumi.String("1"),
				},
			},
		})
		if err != nil {
			return err
		}
		return nil
	})
}

And the following steps:
pulumi up --yes

Apply an edit:
				&rds.ClusterParameterGroupParameterArgs{
					Name:        pulumi.String("max_wal_senders"),
					Value:       pulumi.String("20"),
					ApplyMethod: pulumi.String("pending-reboot"),
				},

Then:
pulumi preview --save-plan=plan.json
pulumi up --plan='plan.json'

Applies without issue for me.

repo: pulumi/pulumi-aws


text:
upstream v5.52.0

Moving ./upstream to v5.52.0
Update patches

Looks like you are missing a make tfgen build_sdks

Looks like you are missing a make tfgen build_sdks

Yeah missed pushing that commit :(

https://github.com/pulumi/schema-tools/issues/73

authors: flostadler iwahbe t0yv0


text:
Several properties are missing doc strings

Several properties in this provider are missing docs. It's not clear what the pattern is for the missing docs. For example, a "top-level" property readOnly is missing a doc string but has one on the Terraform site.
It appears that all nested properties are missing docs. For example, recurrence in Downtime.
Another, possibly related issue, is all nested properties are generated on a single line. The previously linked recurrence and widgets are examples.

@kennyjwilli is this still the case? We have invested a LOT on our docs recently

I spot-checked the links above and the docs are either fixed, or the property does not exist yet. Since the issue is so old, I'll go ahead and close it as fixed.

authors: kennyjwilli mikhailshilkov stack72

repo: pulumi/pulumi-datadog


text:
PulumiFn.Create() only accepts empty constructor stacks

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
PulumiFn.Create() only works with empty Constructors.  However, I wish to implement a web service that creates a stack per user.  Thus the web app needs to pass parameters to the Stack via the constructor.
public class MyCustomStack: Stack
{
    public MyCustomStack(string parameter1, string parameter2)
    {
      ....
    }
}

var program = PulumiFn<MyCustomStack>("param1", "param2");

I cannot do the following as PulumiFn is marked as an internal class.
new PulumiFn<MyCustomStack>(() =>
            new MyCustomStack("param1", "param2"));

Affected area/feature
Automation API, but could also be implemented for the CLI.

Thanks for the suggestion!
Seems reasonable to provide an overload of Create that could enable that, something like:
public static PulumiFn Create<TStack>(Func<TStack> stackFactory)
    where TStack : Stack

Usage:
var program = PulumiFn.Create(() => MyCustomStack("param1", "param2"));

In the meantime, as a workaround, you could use other overloads of PulumiFn.Create that aren't based on Pulumi.Stack.

@dsarosi - This works for me:
PulumiFn.Create(() => new MyCustomStack("param1", "param2");

Full example for completeness

  using System.Collections;
  using Pulumi.Automation;
  using Pulumi.Random;

  var program = PulumiFn.Create(() => new MyCustomStack("test", "example"));

  var programArgs = new InlineProgramArgs("test", "test-random", program)
  {
      EnvironmentVariables = new Dictionary<string, string?>
      {
          { "PULUMI_CONFIG_PASSPHRASE", "supersecret" }
      }
  };

  var stack = await LocalWorkspace.CreateOrSelectStackAsync(programArgs);

  await stack.UpAsync(new UpOptions
  {
      OnStandardOutput = Console.WriteLine,
      OnStandardError = Console.WriteLine
  });

  public class MyCustomStack : Stack
  {
      public MyCustomStack(string param1, string param2)
      {
          _ = new RandomPet($"{param1}-{param2}");
      }
  }

authors: JasonWhall dsarosi justinvp

repo: pulumi/pulumi-dotnet


text:
add functionality to link to and expand an individual faq

it would be helpful to be able to link to an individual faq and have it expanded. this would allow us to link to faqs on our marketing pages, but also when sharing links with community folks and customers.

just talked with a user who did not know about the faq where we share specific credit examples
even though the faq link was shared with them
it would be so much easier to support folks and share information if we had the ability to link directly to faq questions, with the answer auto-expanded

repo: pulumi/pulumi-hugo


text:
Fix resource identifier for upstream mist_site resource

Describe what happened
It appears the mist_site resource, when generated downstream is junipermist.device.Base which I would expect to be junipermist.site.Base instead
Sample program
N/A
Log output
No response
Affected Resource(s)
No response
Output of pulumi about
n/a
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).

Thanks for reporting @zbuchheit, we've got a fix incoming in https://github.com/pulumi/pulumi-junipermist/pull/31

authors: VenelinMartinov zbuchheit

repo: pulumi/pulumi-junipermist


text:
Move examples further down on the docs page

Move examples to further down on the docs page. Currently they are the first to display after the resource's description. They should follow after the input/output properties section.

I'm not apriori sure this is a good thing.  I would argue the examples are the highgest used part of these pages, and if anything, the fact that we have them collapsed by default actually is limiting usability of the pages overall.

I believe the addition of a complete/syntactically correct resource definition would provide greater value being higher on the page given that the examples are often not comprehensive of all available input properties/configurations. There are also more pedagogical benefits in this approach as well.

I'm not apriori sure this is a good thing. I would argue the examples are the highgest used part of these pages, and if anything, the fact that we have them collapsed by default actually is limiting usability of the pages overall.

I believe the addition of a complete/syntactically correct resource definition would provide greater value being higher on the page given that the examples are often not comprehensive of all available input properties/configurations. There are also more pedagogical benefits in this approach as well.

The registry does not control where examples are displayed in the body of resources. If we want to take this (and I'd argue we don't), then we would need to take it in the bridge.

authors: iwahbe lukehoban sean1588 toriancrane

repo: pulumi/registry


text:
Transpiling

Nice library.
FYI, its usage in browsers is hampered by the fact that there are some things needed transpile in older browser (let was the main thing I noticed).
I got around it by manually specifying transpiling in my webpack config, but you might consider adding some transpiling at the module level.

A reasonable idea, but since we don't use this in the browser, not something that I'll have the time for in-house. I've given the issue the "contribution welcome" label.

alternatively, changing the following two lines
    let rightSize = false;
    let wordUsed;

to:
    var rightSize = false;
    var wordUsed;

appears to obviate the need for transpilation.

Well... ES5 is pretty old at this point. I've been the first to insist on
keeping compatibility with it on many things but it's really getting to the
point where those who wish to support it should be running their imports
through babel or something.
On Mon, Aug 27, 2018 at 9:56 AM, Marty Jones notifications@github.com
wrote:

alternatively, changing the following two lines
let rightSize = false;
let wordUsed;

to:
var rightSize = false;
var wordUsed;

appears to obviate the need for transpilation.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/punkave/random-words/issues/9#issuecomment-416235039,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB9fZBMqzTHz6sk-8ftRfk7g6B83B14ks5uU_p7gaJpZM4WMaJt
.

--
THOMAS BOUTELL, CHIEF SOFTWARE ARCHITECT
P'UNK AVENUE | (215) 755-1330  |  punkave.com

@murtyjones Took the liberty to do a full ES6 rewrite, added Babel while at it. Can you check this branch does the trick?

I've forked this library so I'm going to go ahead and unsubscribe from this issue, after noting the following:

This library is about 90 lines of code.
87 of these lines appear to be ES5
three of thee lines appear to be ES6:

    let rightSize = false;
    let wordUsed;
...
    options.formatter = (word) => word;

These three lines could be converted to ES5 like so:

    var rightSize = false;
    var wordUsed;
...
    options.formatter = function (word) { return word; };

@murtyjones Indeed, but since it can be used in non-browser environment, I rewrote to ES6 anyway, transpiling it. Overkill maybe, I just liked the idea. :-)
Regarding the code:

The rewrite is the src folder, dist is built by Babel
I’ve moved some functions because there’s no need to expose/export them
AirBNB ESLint config is indeed maintained by AirBNB, but well respected as a coding styling guideline.

Use of the airbnb config is fine as long as it's something that the dependencies are enough to install/discover/whatever; that's what I'm asking about.
I was looking in the wrong place, yes. Still not sure why using "const" for functions and thus requiring them to come before the higher-level functions that call them is an improvement, though.
Fork it if you want I guess (not that I can stop you (: )

authors: CrlH boutell murtyjones

repo: punkave/random-words


text:
Log4j config with module

This is a WIP to solve #85.
Tag @wcooley

This seems to be ok.

As a bit of a side note, I'm slightly concerned with the growing number of parameters. Might need to raise another issue about that.

@liamjbennett I'll get on that.
Re: params number, I think that's the sign of a healthy and extensible module. Have you looked at https://github.com/jfryman/puppet-nginx? The curse of being easily-modifiable is a lot of code it seems.

Tests fail because the module expects the file to be XML. I wonder if this will be harder than I thought. Rundeck may be using a nonstandard config.

Tests fail because the module expects the file to be XML.

Yuck. I didn't notice that danielgil/log4j was only for the XML-formatted log4j.

I wonder if this will be harder than I thought.

Not necessarily; the Java properties format is much simpler than XML and, I suspect, the puppetlabs/inifile should suffice.

Rundeck may be using a nonstandard config.

No, Java properties like this are very common (possibly more common than XML, for logging, at least).
As far as the interface goes, I was thinking of something more like a few defined types, simliar to the log4j::logger type (but with path coming from something like $rundeck::config::log4j_properties_file).
rundeck::log4j::logger { 'org.codehaus.groovy.grails':
  level => 'info',
  appender => ['stdout', 'server-logger'],
  additivity => false,
}

I would probably also have a generic appender config that used the 3rd-level component (e.g., "cmd-logger" in "log4j.appender.cmd-logger.file") as the title and the 4th-level as parameters (with a special "classname" or "appenderclass" or "appender" for the appender Java class name, since that's otherwise at the 3rd level; I'm uncertain about using "class" as a parameter name).
$logdir = $rundeck::config::service_logs_dir # lazy abbrev
rundeck::log4j::appender { 'server-logger':
  classname => 'org.apache.log4j.DailyRollingFileAppender',
  file => "${logdir}/rundeck.log",
  datePattern => "'.'.yyyy-MM-dd",
  ...
}

Given that almost all of the default appenders have basically the same configuration, aside from file and ConversionPattern, it probably makes sense to make all that the default.
You might even start with a generic rundeck::log4j::setting defined type that's just a wrapper around ini_setting, to set the path to $rundeck::config::log4j_properties_file, section to "" ("global"-no section) and to declare the dependency/notification relationships, so that the other defines just have to provide the key/setting and value:
rundeck::log4j::setting { 'log4j.rootLogger':
  value => 'warn, stdout, server-logger',
}

(I started calling this rundeck::log4j::config, but thought that might make it confusing with rundeck::config; setting also maps it more closely to the ini_setting parameter.)
I probably wouldn't have anything in rundeck::config or rundeck, aside maybe from managing $rundeck::config::log4j_properties_file as a File resource (even that I am hesitant about). My opinion is that, since the distributed file works without changes, it should be let alone unless the user specifically requests it be changed. Making as few changes to mainline as possible makes support easier for everyone, unless the vendor can't be trusted to no break things.

@wcooley I'm quite against making rundeck manage log4j itself; using an external module, even if it's complex, would be preferable. I would rather be ready for the Rundeck devs to pivot to shipping an XML format, or the log4j devs changing their formatting, than to update some custom logic.

+1

Closing as I don't have time to work on this at the moment.

authors: igalic jyaworski liamjbennett wcooley

repo: puppet-community/puppet-rundeck


text:
[Bug]: Website not loading specifically for Linux: Headless mode

Minimal, reproducible example
const stealth = StealthPlugin();
puppeteer.use(stealth);

const browser = await puppeteer.launch({
  headless: true,
  args: [
    "--no-sandbox",
    "--disable-setuid-sandbox",
    "--font-render-hinting=none",
    "--disable-gpu",
    "--no-first-run",
  ],
});

const page = await browser.newPage();

page.setDefaultNavigationTimeout(30 * 1000);
let res = await page.goto(config.pageUrl, { waitUntil: "networkidle0" });

let pageContent = await page.content();
fs.writeFileSync("output.html", pageContent);

Background
Getting the page content some websites, does not include the dynamic content loaded by js/fonts/images only the inital doc is shown. This problem does not occur in windows headless or headfull mode, neither does this happen in linux headfull mode. After some debugging I have noticed that, the number of requests are less in headless mode. I have also used stealth mode plugin to bypass stealth detection.
Expectation
Whole page content with dynamic js should be shown from page.content, in linux headless mode.
Reality
page.content only gets the initial doc, in linux headless mode.
Puppeteer configuration file (if used)
No response
Puppeteer version
"puppeteer": "^23.11.1",
Node version
v22.12.0
Package manager
npm
Package manager version
10.9.0
Operating system
Linux

Please provide a complete executable example including a test site and without the use of third party packages. If the site errors or fails to load or blocks a particular visit, it can happen that dynamic content is not loaded and rendered, so might want to check the console messages on the page for errors and network requests for failed requests. It is also possible for sites to specifically detect and block headless browsers (avoiding any sort of detection is out of scope for Puppeteer).

authors: OrKoN snehilshah

repo: puppeteer/puppeteer


text:
Bolt 2.0 is using old version of reboot module

Describe the Bug
When trying to run the reboot plan with Bolt 2.0 it fails with:
{
  "kind": "bolt/pal-error",
  "msg": "reboot:\n  has no parameter named 'targets'\n  expects a value for parameter 'nodes'",
  "details": {
  }
}

Expected Behavior
This plan should accept targets as a parameter.
Steps to Reproduce
plan mymodule::myplan (
  TargetSpec $targets,
) {
  run_plan('reboot', targets => $targets)
}

Environment

Version: Bolt 2.0

Additional Context
Looks like the change was merged into the reboot module's master branch, but a release wasn't done: https://github.com/puppetlabs/puppetlabs-reboot/blob/master/plans/init.pp
The lastest release of this module is 2.4.0 and does NOT contain the updated plan. Looks like we're including version 2.2.0 in Bolt: https://github.com/puppetlabs/bolt/blob/master/Puppetfile#L28
I've created a ticket in JIRA for the Modules team: https://tickets.puppetlabs.com/browse/MODULES-10569

Closed by #1638

repo: puppetlabs/bolt


text:
Show PowerShell cmdlets in output when running in PowerShell

When running certain commands or raising certain errors, Bolt will
output a command to run. This change checks whether Bolt is running in
PowerShell or not, and sets the command in the output to a PowerShell
cmdlet if it is or a *nix shell command if it is not.
!no-release-note

CLA signed by all contributors.

Updated.
I left out https://github.com/puppetlabs/bolt/blob/main/lib/bolt/bolt_option_parser.rb#L199 because that help text isn't used in the Powershell module and is already specific to the *nix shell commands. It seems incorrect to show a Powershell cmdlet in the help text for *nix shell commands.
Similarly, https://github.com/puppetlabs/bolt/blob/main/lib/bolt/outputter/human.rb#L299 was left out since there is no Powershell cmdlet for the topic guides and this list won't be shown when using the Powershell cmdlet Get-Help about_bolt_*.

authors: beechtom puppetcla


text:
(WIP) (FACT-718) Blocklisting facts

This is a proof of concept for blocklisting facts based on a list in the config file. The facts grouping allows for parallel structure with the existing groups, and can probably also reasonably contain the TTL information later. The items in the lists correspond to top-level structured facts to be blocked.
facts : {     blocklist : [ os, ec2 ] }
Is this a reasonable approach? It seems to behave correctly on initial testing.
This is currently built on top of my other PR, will rebase once that is merged.

CLA signed by all contributors.

Needs a rebase now.

Closing this in favor of a different approach.

authors: Magisus MikaelSmith puppetcla

repo: puppetlabs/facter