text:
Prometheus quit via url

What did you do?
curl -X POST localhost:9090/-/quit
What did you expect to see?
Prometheus to stop
What did you see instead? Under which circumstances?
Prometheus keeps running and I get 404 page not found for /-/quit
Environment
ubuntu 14.04

System information:
insert output of uname -srm here

Linux 4.4.0-64-generic x86_64

Prometheus version:
insert output of prometheus -version here

prometheus -version
prometheus, version 1.5.2 (branch: master, revision: bd1182d29f462c39544f94cc822830e1c64cf55b)
build user:       root@a8af9200f95d
build date:       20170210-14:41:22
go version:       go1.7.5

Alertmanager version:
insert output of alertmanager -version here (if relevant to the issue)

Prometheus configuration file:

insert configuration here

Alertmanager configuration file:

insert configuration here (if relevant to the issue)

Logs:

curl -X POST localhost:9090/-/quit
404 page not found

Could you elaborate your use case? Why do you need this?

Since allowing remote shutdown is a bit risky, you need to start Prometheus with the -web.enable-remote-shutdown flag to enable this. It works for me with that flag, so closing.


text:
When bad configuration defined prometheus should exit with non zero exit-code.

Bug Report
What did you do?
Prometheus config have a error.
What did you expect to see?
Startup failed -> non zero exit-code.
This is important for automation tools and systemd.
What did you see instead? Under which circumstances?
Startup failed -> zero exit-code.
Environment

System information:

Linux 4.11.12-1-nfcustom x86_64

Prometheus version:

prometheus, version 2.3.1 (branch: non-git, revision: non-git)
  build user:       someman@linux01
  build date:       20180620-05:11:40
  go version:       go1.10.3

Prometheus configuration file:

- mybad:

Logs:

[root@linux01 prometheus]# prometheus
level=info ts=2018-06-20T05:43:40.583393016Z caller=main.go:222 msg="Starting Prometheus" version="(version=2.3.1, branch=non-git, revision=non-git)"
level=info ts=2018-06-20T05:43:40.583468472Z caller=main.go:223 build_context="(go=go1.10.3, user=someman@linux01, date=20180620-05:11:40)"
level=info ts=2018-06-20T05:43:40.58386063Z caller=main.go:224 host_details="(Linux 4.11.12-1-nfcustom #1 SMP PREEMPT Fri Nov 3 13:29:36 +07 2017 x86_64 linux01 (none))"
level=info ts=2018-06-20T05:43:40.584102954Z caller=main.go:225 fd_limits="(soft=1024, hard=4096)"
level=info ts=2018-06-20T05:43:40.585073298Z caller=main.go:514 msg="Starting TSDB ..."
level=info ts=2018-06-20T05:43:40.585125536Z caller=web.go:415 component=web msg="Start listening for connections" address=0.0.0.0:9090
level=info ts=2018-06-20T05:43:40.593193403Z caller=main.go:524 msg="TSDB started"
level=info ts=2018-06-20T05:43:40.593257652Z caller=main.go:603 msg="Loading configuration file" filename=prometheus.yml
level=info ts=2018-06-20T05:43:40.593524321Z caller=main.go:402 msg="Stopping scrape discovery manager..."
level=info ts=2018-06-20T05:43:40.59355105Z caller=main.go:416 msg="Stopping notify discovery manager..."
level=info ts=2018-06-20T05:43:40.593566994Z caller=main.go:438 msg="Stopping scrape manager..."
level=info ts=2018-06-20T05:43:40.593598464Z caller=main.go:412 msg="Notify discovery manager stopped"
level=info ts=2018-06-20T05:43:40.593743405Z caller=manager.go:464 component="rule manager" msg="Stopping rule manager..."
level=info ts=2018-06-20T05:43:40.593810228Z caller=manager.go:470 component="rule manager" msg="Rule manager stopped"
level=info ts=2018-06-20T05:43:40.594547611Z caller=main.go:398 msg="Scrape discovery manager stopped"
level=info ts=2018-06-20T05:43:40.594595131Z caller=main.go:432 msg="Scrape manager stopped"
level=info ts=2018-06-20T05:43:40.593827729Z caller=notifier.go:512 component=notifier msg="Stopping notification manager..."
level=info ts=2018-06-20T05:43:40.594785248Z caller=main.go:588 msg="Notifier manager stopped"
level=error ts=2018-06-20T05:43:40.594809317Z caller=main.go:597 err="Error loading config couldn't load configuration (--config.file=prometheus.yml): parsing YAML file prometheus.yml: yaml: unmarshal errors:\n  line 1: cannot unmarshal !!seq into config.plain"
level=info ts=2018-06-20T05:43:40.594922161Z caller=main.go:599 msg="See you next time!"

[root@linux01 prometheus]# echo $?
0

promtools works fine:
[root@linux01 prometheus]# promtool check config /etc/prometheus/prometheus.yml
Checking /etc/prometheus/prometheus.yml
  FAILED: parsing YAML file /etc/prometheus/prometheus.yml: yaml: unmarshal errors:
  line 1: cannot unmarshal !!seq into config.plain

[root@linux01 prometheus]# echo $?
1

I will take a look at this one tonight if nobody has put up a PR by then. I have never contributed to this project, so it may take me sometime to get my environment setup and get accustomed to the repo, but the fix seems like it would be pretty straight forward.

Great! If you've any questions we're in #prometheus-dev on freenode.

source: gharchive/issue

authors: brian-brazil k0ste mikeykhalil

repo: prometheus/prometheus

license_type: permissive

license_source: github-api


text:
2.8.0 OOM

2.8.0 version OOM always， update from 2.7.2

@HarveyJie are you using remote_write?

@codesome yes!, I use remote_write  by timesale

remote_write uses WAL in 2.8.0 which apparently takes more memory than before. Work is in progress here https://github.com/prometheus/prometheus/pull/5316 to reduce the memory usage.

authors: HarveyJie codesome


text:
Example graph seems wrong

Proposal
Use case. Why is this important?
Trying to run example tutorial.
Bug Report
What did you do?

Go through Prometheus example steps until you get to the last one where you set up the command job_service:rpc_durations_seconds_count:avg_rate5m.
Switch between "stacked" and "unstacked"
The legend remains the same, but the colors switch places in the graph and don't match their values.

What did you expect to see?
The stacked version of this correct graph:

What did you see instead? Under which circumstances?
This incorrect graph:

Environment
Ubuntu Linux 18.04 LTS

System information:

Linux 4.15.0-46-generic x86_64

Prometheus version:

prometheus, version 2.9.2 (branch: HEAD, revision: d3245f15022551c6fc8281766ea62db4d71e2747)
build user:       root@1d43b6951e8f
build date:       20190424-15:32:31
go version:       go1.12.4

Prometheus configuration file:

# my global config
global:
  scrape_interval:     15s # Set the scrape interval to every 15 seconds. Default is every 1 minute.
  evaluation_interval: 15s # Evaluate rules every 15 seconds. The default is every 1 minute.
  # scrape_timeout is set to the global default (10s).

# Alertmanager configuration
alerting:
  alertmanagers:
  - static_configs:
    - targets:
      # - alertmanager:9093

# Load rules once and periodically evaluate them according to the global 'evaluation_interval'.
rule_files:
  - 'prometheus.rules.yml'
  # - "first_rules.yml"
  # - "second_rules.yml"

# A scrape configuration containing exactly one endpoint to scrape:
# Here it's Prometheus itself.
scrape_configs:
  # The job name is added as a label `job=<job_name>` to any timeseries scraped from this config.
  - job_name: 'prometheus'

    # metrics_path defaults to '/metrics'
    # scheme defaults to 'http'.

    static_configs:
    - targets: ['localhost:9090']

  - job_name: 'example-random'

    # Override the global default and scrape targets from this job every 5 seconds.

    scrape_interval: 5s

    static_configs:
    - targets: ['localhost:8080', 'localhost:8081']
      labels:
        group: 'production'

    - targets: ['localhost:8082']
      labels:
        group: 'canary'

I don't see anything wrong with the stacked version. The value in the tooltip looks correct and the total value seems ok too.
I'm closing it for now. If you have further questions, please use our user mailing list, which you can also search.

What are you talking about? The color values are FLIPPED. The green value has a value of 7.24 and it's on TOP, sitting above 30! The graph is completely flipped... how do you not see this?

Well each time-series graph is stacked above the previous one. This is exactly the same as viewed here if you switch between the stack and value representations.

Maybe it is my misunderstanding of what stacked graphs are supposed to represent.. it seems like the Y-axis values are supposed to match their corresponding Y-values... but apparently it's actually just the proportion of the SUM of Y-axis values? This is a very confusing data visualization...

but apparently it's actually just the proportion of the SUM of Y-axis values?

Yes, this is similar to Grafana's stack mode.

That makes a lot more sense, sorry for the misunderstanding!

No problem! Happy that we finally agree :-)


text:
Testing alert rule brings about unexpected evaluation behaviour

Bug Report
What did you do?
I have the following test case (inspired by RobustPerception's blog post), which is bringing about unexpected behaviour.
groups:
- name: ssl-certificates
  rules:
  - alert: SSLCertificateExpiringIn2Weeks
    expr: ((probe_ssl_earliest_cert_expiry{domain=~"https.*"} - time()) < (86400 * 14))
    for: 1m
    labels:
      severity: warning
      environment: some_environment
    annotations:
      summary: The summary
      description: The description

And the relevant test file:
---
rule_files:
  - ../rules/ssl-certificates-alerts.yml
evaluation_interval: 1m
tests:
  - input_series:
      - series: probe_ssl_earliest_cert_expiry{domain="https://example.com"}
        # 1209660 triggers alert
        # 1209659 does not trigger alert
        values: '1209659'
    alert_rule_test:
      - eval_time: 2m
        alertname: SSLCertificateExpiringIn2Weeks
        exp_alerts:
        - exp_labels:
            severity: warning
            environment: some_environment
            domain: 'https://example.com'
          exp_annotations:
            summary: The summary
            description: The description

Unless I am missing something (which could easily be the case, I find the way one defines tests for alerting rules complex and a little bit cryptic; I am honestly never sure whether I'm doing it right or not), I don't understand why 1209660 triggers the alert and 1209659 does not.
Shouldn't I provide timestamp values?
I was initially providing 1573464347, which in relative unix timestamp means "in 10 days" (less than 2 weeks). But this does not bring about any alert and I fail to understand why.
What did you expect to see?
See above
What did you see instead? Under which circumstances?
See above
Environment

System information:
Darwin 19.0.0 x86_64

Prometheus version:

prometheus, version 2.13.1 (branch: non-git, revision: non-git)
  build user:       brew@Catalina.local
  build date:       20191018-01:35:32
  go version:       go1.13.1

And:
promtool, version 2.13.1 (branch: non-git, revision: non-git)
  build user:       brew@Catalina.local
  build date:       20191018-01:35:32
  go version:       go1.13.1

Alertmanager version:
N/A

Prometheus configuration file:
N/A

Alertmanager configuration file:
N/A

Logs:
N/A

This is because of the for clause. If you set it to 59s or evaluate the alert at 3m then the alert fires.
I'm closing it for now. If you have further questions, please use our user mailing list, which you can also search.

@simonpasquier what exactly is "because of the for clause"? Can you please expand a bit more on this for everyone's future benefit?
The metric/query in question returns a unix timestamp value. But the values I reported setting above are not. They don't make sense in terms of unix timestamp values.
I'm mostly interested in the following:

I don't understand why 1209660 triggers the alert and 1209659 does not. Shouldn't I provide timestamp values?

Thanks.

As per https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/#defining-alerting-rules

The optional for clause causes Prometheus to wait for a certain duration between first encountering a new expression output vector element and counting an alert as firing for this element. In this case, Prometheus will check that the alert continues to be active during each evaluation for 10 minutes before firing the alert. Elements that are active, but not firing yet, are in the pending state.

I misread your initial description and thought that 1209659 triggered the alert at t0+2m while 1209660 didn't (because the alert is pending, not firing). FWIW this is what I'm observing locally so not sure what happens with your setup.
I think that when no firing alert matches, promtool could check whether a pending alert matches and surface it to the user.

@simonpasquier that still does not answer the question why I have to provide the non-unix timestamp values such as i.e. 1209659  (7 digits, which converted to to human readable date equates to Thursday, 15 January 1970 00:00:59) instead of i.e. 1572031521 (10 digits, which converted to to human readable date equates to Friday, 25 October 2019 19:25:21).
I'm also not really sure the for clause is the thing one ought to be focusing here.
Is it because of a discrepancy between the expr defined and the input_series being used?
Does promtool expect the entire expr to be mocked, or just the metric?

that still does not answer the question why I have to provide the non-unix timestamp values

the initial time for unit alert tests is 0, eg Jan 1 1970 so samples representing timestamps should be relative to the epoch.
I'm not sure what you call "discrepancy". In general I would recommend for consistency to have samples that span to the last rule evaluation time.

@simonpasquier thank you for your prompt replies on this! Please see below.

I'm not sure what you call "discrepancy". In general I would recommend for consistency to have samples that span to the last rule evaluation time.

Let me explain a bit further.
Given the following expr:
# If result is "less than 14 days", then notify/alert
expr: ((probe_ssl_earliest_cert_expiry{domain=~"https.*"} - time()) < (86400 * 14))

And the following input_series:
- series: probe_ssl_earliest_cert_expiry{domain="https://example.com"}
   values: '1573464347'  # GMT: Monday, 11 November 2019 09:25:47, Relative: In 5 days

Will Prometheus/promtool take the value defined in values and evaluate/apply it against the whole expression, including the time() function, etc? Or will whatever is defined in series actually be the expression?
In other words, given the above, will Prometheus/promtool do this?
(1573464347 - time()) < (86400 * 14))

Or do I need to write this?
- series: (probe_ssl_earliest_cert_expiry{domain="https://example.com"}  - time()) < (86400 * 14))
   values: '1573464347'  # GMT: Monday, 11 November 2019 09:25:47, Relative: In 5 days

If it's the latter, then this is what I define as "discrepancy". As one would have to define the whole expression instead of just mocking the metric used in the expr and its result.
Please let me know if it's not clearer after this.

the initial time for unit alert tests is 0, eg Jan 1 1970 so samples representing timestamps should be relative to the epoch.

Hmmmm. That means one would have to specify i.e. 1573464347 and not 1209659  or 12096560, then. Is that correct?

Will Prometheus/promtool take the value defined in values and evaluate/apply it against the whole expression, including the time() function, etc? Or will whatever is defined in series actually be the expression?

The former. input_series represents streams of datapoints where series represents a timeseries (metric name + a set of labels (key/value)) and samples the values at every interval.
Regarding time() it will return 0 when eval_time: 0m, 60 when eval_time: 1m, and so on.

The former.

OK. Thanks for the clarification. It means only the metric query needs to be written (i.e. probe_ssl_earliest_cert_expiry{domain="https://example.com"}). That's good.

series represents a timeseries (metric name + a set of labels (key/value)) and samples the values at every interval.

By samples, did you mean values? As defined as follows?
- input_series:
     - series: ...
        values: ...

Regarding time() it will return 0 when eval_time: 0m, 60 when eval_time: 1m, and so on.

Oh. Does that mean that in order to test the following:
((probe_ssl_earliest_cert_expiry{domain=~"https.*"} - time()) < (86400 * 14))

Which, as I wanted to test, would translate to:
(1573464347 - 1573059143) < 1209600

I would need to write this?
  - input_series:
      - series: probe_ssl_earliest_cert_expiry{domain="https://example.com"}
        values: '1573464347' # GMT: Monday, 11 November 2019 09:25:47
    alert_rule_test:
      - eval_time: 1573059143s  # GMT: Wednesday, 6 November 2019 16:52:23
        alertname: SSLCertificateExpiringIn2Weeks
        exp_alerts:

Because if that's the case, it would take ages to run a test like this.

authors: simonpasquier walterdolce


text:
docs: Update chunk layot for NHCB

Another part of resolving https://github.com/prometheus/prometheus/issues/12005 .

@krajorama @zenador is that all we need to document NHCB for the on-disk format?

@krajorama @zenador is that all we need to document NHCB for the on-disk format?

For now yes, but later when we have #14730 implemented, we should update https://github.com/prometheus/prometheus/blob/main/tsdb/docs/format/wal.md as well. cc @carrieedwards

Thank you.
WRT location of the notes: I just put it with all the other notes. It also struck me as weird to explain all of that only at the bottom, but I didn't want to do two changes in one go.

source: gharchive/pull-request


text:
web: remove security headers

Sorry. Of course I forgot the right merge base again...

shame on you :stuck_out_tongue_winking_eye:
LGTM

For people who stumble on this without context, here is more context in the original PR against the master branch: https://github.com/prometheus/prometheus/pull/4258

authors: fabxc juliusv krasi-georgiev


text:
Devkid feature/aws routing policies

Merging changes from devkid/feature/aws-routing-policies

Hi @johngmyers
I probably didn't do something right as the commits are showing my name also.
These are the changes to support different routing policies on AWS using external-dns.
our changes for health checks will be based on top of this PR.
Thanks
Rajat Jindal

repo: proofpoint/external-dns


text:
Don't always include published: false for markdown

For example, editing a readme.md file in a jekyll site does not need a published: false if it is in the _config.yml to be excluded. This might be tricky to avoid though.

Hello and thank you for this issue report. There have been several point releases in Prose since this issue was opened and there has not been much discussion here. I wanted to ask if you could please assist in confirming this is still an issue in the latest version of the product. If it is fixed, please close this issue :-)
Also, if possible could you please

Create a test case -- a list of steps we can perform to reproduce the problem

Since this project is looking for new maintainers (#743), it will be helpful if users can double check the old issues and delete ones that are fixed. This will be super helpful for the new team that works on moving this project forward.
I'm sorry this message is impersonal. And thanks for your help!

So now it always sets published: true..is this intended? I don't use Jekyll and have no use for it at all. Can we either not set it by default or hide it behind a config?

This just happened to me too, on a project that doesn't require it. I agree it's annoying, and doesn't make sense if the file is not in a _posts folder.

In jekyll,
prose.io create published: false if you are in _posts.
prose.io will note create published: false if you are not in _posts.
so if you want to create a post inside _posts, you need to:
create the post -> back previous page -> reload page -> go into the post -> click unpublished icon
... WTF :(

ok, I got it.
add this in _config.yml:
prose:
  metadata:
    _posts:
      - name: "published"
        field:
          element: "checkbox"
          label: "published"
          value: "true"

Everything works perfect!
check here: https://github.com/prose/prose/wiki/Prose-Configuration

Hi, I'm slightly confused by all the discussion on this - I don't use Jekyll or a directory called _posts, yet an unneeded published: false is always added into any files I create using Prose. It would be nice to avoid this :)

Finally had a moment to get around to this. A bit of a tricky one since as mentioned above there were some red herrings in finding where published: true was even being set in the first place.
I would appreciate some feedback on the PR (#1151) if anyone has a second to read it over but the TL;DR is that I've settled on a pattern that hopefully resolves this issue for everyone not using Jekyll while still retaining the original functionality. From now on published: true will no longer appear in front-matter unless explicitly set.
If I don't hear anything in the PR or this issue I'll merge and close both sometime later this week.

authors: babbitt dereklieu dhcole fghhfg fulldecent jgillich sarajw

repo: prose/prose

license_source: bigquery


text:
🛑 webui.ipfs.io is down

In 4e66769, webui.ipfs.io (https://webui.ipfs.io) was down:

HTTP code: 0
Response time: 0 ms

Resolved: webui.ipfs.io is back up in feb1ac7 after 2 hours, 3 minutes.

repo: protocol/upptime-pln

license: MIT


text:
Should goog.DEBUG be false for builds distributed via npm?

goog.DEBUG is true in the google-protobuf.js runtime distributed in the npm package. This setting gates the various assertion code in the runtime (goog.asserts.ENABLE_ASSERTS = goog.DEBUG;).

Is this expected?
If so, should DEBUG be set to false for production builds? And should two builds be distributed, or a means be exposed to configure this?
If not, should the gulpfile that generates the runtime supply --define goog.DEBUG=false to the closure compiler invocation?

Good question. Internally, we are use to people deliberately disabling debug mode when moving to production. It's unclear what the best approach is for public distribution.

i think this is a case where we would need a new API
it would be reasonable to expect some customers to want to run with asserts and debug code disabled, but due to our releasing a bundled version of closure library this isn't possible.
consider angulars enableProdMode

authors: dibenede lukesandberg tatethurston

repo: protocolbuffers/protobuf-javascript


text:
(Dev task) Create epoch module to track incentive rewards

Summary

Problem Definition
Why do we need this feature?
For Incentive rewards.
Create an epoch module to track incentive rewards.
Define proto/keeper/genesis etc for this module.

message EpochInfo {
  string identifier                 = 1;
  int64  start_height               = 2; // start height of the beginning of all epoch
  int64  duration                   = 3; // in blocks for e.g a month will be (30*24*7*60*60)/5 blocks
  int64  current_epoch              = 4;
  int64  current_epoch_start_height = 5; // start height of the current epoch
  bool   epoch_counting_started     = 6;
}

// GenesisState defines the epochs module's genesis state.
message GenesisState {
  repeated EpochInfo epochs = 1 [ (gogoproto.nullable) = false ];
}

Default genesis
// DefaultGenesis returns the default Capability genesis state
func DefaultGenesis() *GenesisState {
	epochs := []EpochInfo{
		{
			Identifier:              "week",
			StartHeight:             0,
			Duration:                int64((24 * 60 * 60 * 7) / 5), //duration in blocks
			CurrentEpoch:            0,
			CurrentEpochStartHeight: 0,
			EpochCountingStarted:    false,
		},
		{
			Identifier:              "day",
			StartHeight:             0,
			Duration:                int64((24 * 60 * 60) / 5),
			CurrentEpoch:            0,
			CurrentEpochStartHeight: 0,
			EpochCountingStarted:    false,
		},
		{
			Identifier:              "monthly",
			StartHeight:             0,
			Duration:                int64((60 * 60 * 24 * 30 * 7) / 5),
			CurrentEpoch:            0,
			CurrentEpochStartHeight: 0,
			EpochCountingStarted:    false,
		},
	}
	return NewGenesisState(epochs)
}

Proposal

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

This is complete as a development effort for now, more integration testing is needed.

repo: provenance-io/provenance


text:
[WIP] refactor(Prowler): Main logic refactor

Context
Please include relevant motivation and context for this PR.
Description
Please include a summary of the change and which issue is fixed. List any dependencies that are required for this change.
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

NO MERGE THIS PR IS A WORK IN PROGRESS

Reaaaally nice work guys !!

repo: prowler-cloud/prowler


text:
Git-Projects no longer finds my Git Projects...

It worked fine on Friday, then I updated and blam... nothing found.
ATOM: https://www.dropbox.com/s/znnio88jzcd8smk/Screenshot 2015-03-16 11.36.08.png?dl=0
CONSOLE: https://www.dropbox.com/s/qfsjfte277wkqsv/Screenshot 2015-03-16 11.36.35.png?dl=0

Reverting to this fixes the issue: https://raw.githubusercontent.com/prrrnd/atom-git-projects/f3cd7a1307d17ac68901aaf2a561287a02f792aa/lib/git-projects.coffee

Thanks for reporting your issue.
Could you post the content of your config.cson file, which is located in your .atom directory?
Please make sure that your path is not being ignored with this feature
Have you tried uninstalling and re-installing the package as well?

I have tried uninstalling and re-installing the package.
I am ignoring some paths, but only in the fuzzy-finder array.
config.cson is below:

"":
"exception-reporting":
userId: "bc24b7a3-adcc-a82d-c126-9098e6739f31"
welcome:
showOnStartup: false
linter: {}
core:
themes: [
"seti-ui"
"seti-syntax"
]
projectHome: "/Users/nkronemeyer/sharecare"
editor:
invisibles: {}
fontSize: 14
autoIndent: false
scrollPastEnd: true
"git-projects":
rootPath: "/Users/nkronemeyer/git"
openInDevMode: true
"fuzzy-finder":
ignoredNames: [
".txt"
".git*"
"Gemfile*"
"README*"
"README"
".project"
".sh"
".xml"
".rb"
".json"
".properties"
"cfg"
".example"
".pdf"
".png"
".types"
]

i'm having the issue also.  here is my config.cson
$ cat config.cson
"*":
  editor:
    softTabs: false
    scrollPastEnd: true
    invisibles: {}
    fontSize: 14
  core:
    themes: [
      "atom-dark-ui"
      "atom-dark-syntax"
    ]
  linter: {}
  "exception-reporting":
    userId: "f0c4d091-8112-1ff9-5056-538039e6d16e"
  welcome:
    showOnStartup: false
  "tree-view": {}
  minimap: {}
  "atom-terminal":
    app: "iTerm.app"
  "spell-check": {}
  "autocomplete-plus": {}
  "project-ring": {}
  "git-projects":
    showSubRepos: true
    rootPath: "/Users/davidc397/git; /Users/davidc397/out/git"
    sortBy: "Latest modification date"

Alright, I believe I figured it out. Both of you have a rootPath containing the string "git", which is also contained in the default ignored path. I updated the default ignored path from node_modules;.git to node_modules;\\.git. The fix should be available today in the 1.10.1 release.

:+1:

That fixed it for me. Thanks.

authors: DonkeyAfterDark davidschou prrrnd

repo: prrrnd/atom-git-projects

license: mit


text:
Free Heroku hosting is being phased out

Got this today:

Dear Customer,
Thank you for being a Heroku user. Starting November 28, 2022, free Heroku Dynos, free Heroku Postgres, and free Heroku Data for Redis® will no longer be available. You can learn more about these and other important changes from our GM, Bob Wise, on the Heroku blog.
Existing free dynos and Heroku data add-ons will be impacted, so action by you is required. To prevent any disruption to your apps or data using free plans, you will need to upgrade from a free plan to a paid plan before November 28, 2022.
For instructions on how to upgrade and for other questions, please visit our FAQ.
Thank you,
The Heroku Team

Currently it serves ~30 requests per day.

So it's probably quite affordable to go serverless in this case.

Got it running on Google Cloud functions: https://github.com/psalm/psalm-github-bot/issues/6#issuecomment-1264235367

The Google Cloud function deployment and hosting work fine.

@orklah @muglug there's a new github application available: https://github.com/apps/psalm-github-bot-beta, currently installed in this repo only, in addition to the regular bot. We should test it and then replace update the primary bot settings with to use the function running on GCF.

This comment should be picked up by both bots.
https://psalm.dev/r/4121eceef8

seems to work fine! What should we do to install it?

There's no rush, the Heroku-hosted bot should work fine until Nov 28.
I think when the time comes I would just replace github app settings for the current bot with the settings for the new one, so no reinstallation would be necessary. However, if I'm not available at that time you could just uninstall the old one and install the new one:

Navigate to https://github.com/apps/psalm-github-bot-beta
Click Configure
In Repository access section, select the repositories you need
Navigate to https://github.com/apps/psalm-github-bot
Click Configure
Click Uninstall

Installation in vimeo/psalm repo may require admin access, so you may need to contact @muglug

@psalm-github-bot (production version) now runs on GCF.
@orklah you don't need to install beta bot, nor you can as I deleted it.

authors: orklah weirdan

repo: psalm/psalm-github-bot

license: ISC


text:
DOC: fix typo

Fix #448

I'm going to blindly merge this in. No need to burn CI minutes for a one character doc change.

repo: psyinfra/onyo


text:
Rework --message parameter

Closes #685
TODO:

[ ]  tests
[ ]  make default for --no-auto-message configurable

While this is a draft, I still had a look because I am excited for the functionality to be added.
Very cool, thanks for working on it :)

authors: TobiasKadelka bpoldrack


text:
percent should be "ratio"

Prometheus best practice is to use "ratio": rather than percent. https://prometheus.io/docs/practices/naming/#base-units
The field names should be updated to end in _ratio rather than _percent. And the values should be changed accordingly.

So would this mean ups_output_percent_load_in_percent should rather be ups_output_percent_load_ratio ?

Correct. And the value itself should be (for example) 0.82 instead of 82.

Ah okay, I've just exposed the data as it is given by the API.
Is it a common thing to change the format of the scraped data?

Done

For something as simple as this, it definitely makes sense. If we normalize the data flowing into Prometheus, it makes it much easier to reuse graphs and compare across systems.
However, in other situations, we ignore it. For example, Prometheus suggests using joules rather than watts. IMO, it's not worth it to adjust our watt metrics into joules, so we'll leave them as they are. :-)

Sorry to bug again on this issue, but it's better to prefix metrics with eaton_ups_* instead of ups_*, because this exporter only works for eaton UPS's.

Alright I will make the changes

Alex has addressed this in PR #15 already. If you can validate it and merge it to master, then we can run it and I'll set up the accompanying Eaton UPS Dashboard.

I just saw it.

Merged

authors: aqw mathisloevenich nhjjreuter

repo: psyinfra/prometheus-eaton-ups-exporter


text:
提高反馈效率的建议和bug反馈

PT 助手版本:1.6.0
PT 助手安装方式：zip包安装
浏览器名称及版本：Microsoft Edge
版本 108.0.1462.46 (正式版本) (64 位)
浏览器是否安装了其他插件：是
停用其他插件后是否正常工作：是
问题描述：
搜索影视z相关影视总会有hdtime站点的种子
https://hdtime.org/details.php?id=47767&hit=1
相关截图：
照片太大没法上传
重现步骤：
【能不能建一个qq群，方便反馈问题。这个站点太慢了，不方便联系，下载也不方便】

P主界面右下方有TG群组链接 图太大可以借助
图床上传

这个我知道，我的意思是用qq群交流方便，梯子很多人还不太实用

可以发个外链的图片

我说下我对开源软件的理解。
开源软件是没有售后的，自然也没有高效客服，虽然我们有Mit.
你可以在任何相关的地方提出问题

repo: pt-plugins/PT-Plugin-Plus


text:
坚果云参数备份失败，点击测试显示服务器可连接

请确认你已经做过并了解如下步骤，在 [] 中填入 x 选中

[ ] 仔细看并搜索过Wiki
[ ] 请确认你的版本比当前Pre-release要新，我们建议使用crx版本作为标准
[ ] 搜素过Issue，确认没有相关问题
[ ] 不理解、询问问题或者使用上的问题请使用Discuissions

PT 助手版本: v1.6.1.2552

PT 助手安装方式：chrome市场安装

浏览器名称及版本：chrome

浏览器是否安装了其他插件：

停用其他插件后是否正常工作：

问题描述：

相关截图：

重现步骤：

https://github.com/pt-plugins/PT-Plugin-Plus/issues/1740


text:
commit a38d531b breaks configs that declare variables in pre and uses it in post.

Plugin affected: all?
Nixpkgs channel: 22.05
Description
commit a38d531bf4d02974d9e3088146cbaf896f2fcb00 breaks my config. I am using the extraConfigLuaPre options, where I define some variables. In extraConfigLuaPost I am using those variables. But in the aforementioned commit it seems to break this funcitonality, since the lua part is now split in two.
I have tried to change my config, to use global variables (not sure if I am doing it correctly), but then I am having issues with my cmp mappings.
I can see why it was chosen to be separated into two different lua sections and I am not sure if we should do something about it.
Config
nixvim config

I just converted my config to use global variables in the pre config, and then renaming my cmp variable and that seems to fix it.

I'm not really sure how desirable it can be to fix this, I think the alternative fix to preserve backwards-compatibility would be to just run everything in a lua block and the vim commands would be ran through vim.cmd (should probably do that anyway so we can move to init.lua). But at what point would it not be better to just specify that Pre, normal and Post are in different scopes?


text:
Master

拉去最新

update

update

repo: ptliao/databinding-samples


text:
BUG: log lines with []'ed text are mistaken for rich tags

This log line fails to show in the TUI:
2023-07-14 08:00:02 ub-3 polkitd(authority=local): Registered Authentication Agent for unix-session:1 (system bus name :1.48 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)

With this error:
││ C:\Users\ptmcg\dev\venvs\log_merger\Lib\site-packages\rich\text.py:283 in from_markup
││
││ C:\Users\ptmcg\dev\venvs\log_merger\Lib\site-packages\rich\markup.py:164 in render
MarkupError: closing tag '[/usr/bin/gnome-shell]' at position 105 doesn't match any open tag

Fixed, will be in 0.7.0

Released in 0.7.0

repo: ptmcg/logmerger


text:
failed to build puckel/docker-airflow

Hi,
when trying to build puckel/docker-airflow i got this error: Cython.Compiler.Errors.InternalError: Internal compiler error: 'algos_common_helper.pxi' not found
More logs:
Downloading/unpacking pandas<1.0.0,>=0.15.2 (from airflow[celery,hdfs,hive,postgres]==1.7.1.3)
Running setup.py (path:/tmp/pip-build-fReTFb/pandas/setup.py) egg_info for package pandas
package init file 'pandas/io/tests/sas/__init__.py' not found (or not a regular file)
pandas/index.pyx: cannot find cimported module 'datetime'
pandas/index.pyx: cannot find cimported module 'util'
./pandas/hashtable.pxd: cannot find cimported module 'khash'
Traceback (most recent call last):
  File "<string>", line 17, in <module>
  File "/tmp/pip-build-fReTFb/pandas/setup.py", line 680, in <module>
    **setuptools_kwargs)
  File "/usr/lib/python2.7/distutils/core.py", line 151, in setup
    dist.run_commands()
  File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
    self.run_command(cmd)
  File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
    cmd_obj.run()
  File "<string>", line 15, in replacement_run
  File "/usr/local/lib/python2.7/dist-packages/setuptools/command/egg_info.py", line 306, in find_sources
    mm.run()
  File "/usr/local/lib/python2.7/dist-packages/setuptools/command/egg_info.py", line 533, in run
    self.add_defaults()
  File "/usr/local/lib/python2.7/dist-packages/setuptools/command/egg_info.py", line 562, in add_defaults
    sdist.add_defaults(self)
  File "/usr/local/lib/python2.7/dist-packages/setuptools/command/py36compat.py", line 36, in add_defaults
    self._add_defaults_ext()
  File "/usr/local/lib/python2.7/dist-packages/setuptools/command/py36compat.py", line 119, in _add_defaults_ext
    build_ext = self.get_finalized_command('build_ext')
  File "/usr/lib/python2.7/distutils/cmd.py", line 312, in get_finalized_command
    cmd_obj.ensure_finalized()
  File "/usr/lib/python2.7/distutils/cmd.py", line 109, in ensure_finalized
    self.finalize_options()
  File "/usr/local/lib/python2.7/dist-packages/Cython/Distutils/build_ext.py", line 19, in finalize_options
    self.distribution.ext_modules)
  File "/usr/local/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", line 809, in cythonize
    aliases=aliases)
  File "/usr/local/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", line 714, in create_extension_list
    kwds = deps.distutils_info(file, aliases, base).values
  File "/usr/local/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", line 590, in distutils_info
    return (self.transitive_merge(filename, self.distutils_info0, DistutilsInfo.merge)
  File "/usr/local/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", line 600, in transitive_merge
    node, extract, merge, seen, {}, self.cimported_files)[0]
  File "/usr/local/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", line 605, in transitive_merge_helper
    deps = extract(node)
  File "/usr/local/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", line 581, in distutils_info0
    externs = self.cimports_and_externs(filename)[1]
  File "/usr/local/lib/python2.7/dist-packages/Cython/Utils.py", line 44, in wrapper
    res = cache[args] = f(self, *args)
  File "/usr/local/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", line 491, in cimports_and_externs
    for include in self.included_files(filename):
  File "/usr/local/lib/python2.7/dist-packages/Cython/Utils.py", line 44, in wrapper
    res = cache[args] = f(self, *args)
  File "/usr/local/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", line 474, in included_files
    include_path = self.context.find_include_file(include, None)
  File "/usr/local/lib/python2.7/dist-packages/Cython/Compiler/Main.py", line 274, in find_include_file
    error(pos, "'%s' not found" % filename)
  File "/usr/local/lib/python2.7/dist-packages/Cython/Compiler/Errors.py", line 177, in error
    raise InternalError(message)
Cython.Compiler.Errors.InternalError: Internal compiler error: 'algos_common_helper.pxi' not found
Complete output from command python setup.py egg_info:
running egg_info

creating pip-egg-info/pandas.egg-info
writing requirements to pip-egg-info/pandas.egg-info/requires.txt
writing pip-egg-info/pandas.egg-info/PKG-INFO
writing top-level names to pip-egg-info/pandas.egg-info/top_level.txt
writing dependency_links to pip-egg-info/pandas.egg-info/dependency_links.txt
writing manifest file 'pip-egg-info/pandas.egg-info/SOURCES.txt'
warning: manifest_maker: standard file '-c' not found
package init file 'pandas/io/tests/sas/init.py' not found (or not a regular file)
pandas/index.pyx: cannot find cimported module 'datetime'
pandas/index.pyx: cannot find cimported module 'util'
./pandas/hashtable.pxd: cannot find cimported module 'khash'
Traceback (most recent call last):
File "", line 17, in
File "/tmp/pip-build-fReTFb/pandas/setup.py", line 680, in
**setuptools_kwargs)

File "/usr/lib/python2.7/distutils/core.py", line 151, in setup
dist.run_commands()

File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
self.run_command(cmd)

File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()

File "", line 15, in replacement_run
File "/usr/local/lib/python2.7/dist-packages/setuptools/command/egg_info.py", line 306, in find_sources
mm.run()

File "/usr/local/lib/python2.7/dist-packages/setuptools/command/egg_info.py", line 533, in run
self.add_defaults()

File "/usr/local/lib/python2.7/dist-packages/setuptools/command/egg_info.py", line 562, in add_defaults
sdist.add_defaults(self)

File "/usr/local/lib/python2.7/dist-packages/setuptools/command/py36compat.py", line 36, in add_defaults
self._add_defaults_ext()

File "/usr/local/lib/python2.7/dist-packages/setuptools/command/py36compat.py", line 119, in _add_defaults_ext
build_ext = self.get_finalized_command('build_ext')

File "/usr/lib/python2.7/distutils/cmd.py", line 312, in get_finalized_command
cmd_obj.ensure_finalized()

File "/usr/lib/python2.7/distutils/cmd.py", line 109, in ensure_finalized
self.finalize_options()

File "/usr/local/lib/python2.7/dist-packages/Cython/Distutils/build_ext.py", line 19, in finalize_options
self.distribution.ext_modules)

File "/usr/local/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", line 809, in cythonize
aliases=aliases)

File "/usr/local/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", line 714, in create_extension_list
kwds = deps.distutils_info(file, aliases, base).values

File "/usr/local/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", line 590, in distutils_info
return (self.transitive_merge(filename, self.distutils_info0, DistutilsInfo.merge)

File "/usr/local/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", line 600, in transitive_merge
node, extract, merge, seen, {}, self.cimported_files)[0]

File "/usr/local/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", line 605, in transitive_merge_helper
deps = extract(node)

File "/usr/local/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", line 581, in distutils_info0
externs = self.cimports_and_externs(filename)[1]

File "/usr/local/lib/python2.7/dist-packages/Cython/Utils.py", line 44, in wrapper
res = cache[args] = f(self, *args)

File "/usr/local/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", line 491, in cimports_and_externs
for include in self.included_files(filename):

File "/usr/local/lib/python2.7/dist-packages/Cython/Utils.py", line 44, in wrapper
res = cache[args] = f(self, *args)

File "/usr/local/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", line 474, in included_files
include_path = self.context.find_include_file(include, None)

File "/usr/local/lib/python2.7/dist-packages/Cython/Compiler/Main.py", line 274, in find_include_file
error(pos, "'%s' not found" % filename)

File "/usr/local/lib/python2.7/dist-packages/Cython/Compiler/Errors.py", line 177, in error
raise InternalError(message)

Cython.Compiler.Errors.InternalError: Internal compiler error: 'algos_common_helper.pxi' not found

Cleaning up...
Command python setup.py egg_info failed with error code 1 in /tmp/pip-build-fReTFb/pandas
Storing debug log for failure in /root/.pip/pip.log
The command '/bin/sh -c set -ex     && buildDeps='         python-dev         python-pip         libkrb5-dev         libsasl2-dev         libssl-dev         libffi-dev         build-essential         libblas-dev         liblapack-dev     '     && echo "deb http://http.debian.net/debian jessie-backports main" >/etc/apt/sources.list.d/backports.list     && apt-get update -yqq     && apt-get install -yqq --no-install-recommends         $buildDeps         apt-utils         curl         netcat         locales     && apt-get install -yqq -t jessie-backports python-requests libpq-dev     && apt-get install -y sshpass     && apt-get install -y openssh-server     && sed -i 's/^# en_US.UTF-8 UTF-8$/en_US.UTF-8 UTF-8/g' /etc/locale.gen     && locale-gen     && update-locale LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8     && useradd -ms /bin/bash -d ${AIRFLOW_HOME} airflow     && pip install --upgrade setuptools     && pip install Cython     && pip install pytz==2015.7     && pip install python-dateutil     && pip install numpy     && pip install cryptography     && pip install pyOpenSSL     && pip install ndg-httpsclient     && pip install pyasn1     && pip install psycopg2     && pip install airflow[celery,postgres,hive,hdfs]==$AIRFLOW_VERSION     && apt-get remove --purge -yqq $buildDeps libpq-dev     && apt-get clean     && rm -rf         /var/lib/apt/lists/*         /tmp/*         /var/tmp/*         /usr/share/man         /usr/share/doc         /usr/share/doc-base' returned a non-zero code: 1

any ideas ?

I am facing the same issue

I have temporarily fixed it by installing the older version of pandas. pandas dependency is coming from airflow. Add pip install pandas==0.18.1 to the docker file(before pip install airflow) to force older version of pandas used in airflow. Seems to be an issue with pandas 0.19

@anurajp yo it works ! thanks.
But i cann acces the webUI after building. with docker ps it shows that the scheduler keeps restarting every ~1 min. Any idea?
PS: i'm using a modifed version of the celereExecutor docker compose file:
version: '2'
services:
rabbitmq:
image: rabbitmq:3-management
restart: always
ports:
- "15672:15672"
- "5672:5672"
environment:
- RABBITMQ_DEFAULT_USER=airflow
- RABBITMQ_DEFAULT_PASS=airflow
- RABBITMQ_DEFAULT_VHOST=airflow
postgres:
    image: postgres
    environment:
        - POSTGRES_USER=airflow
        - POSTGRES_PASSWORD=airflow
        - POSTGRES_DB=airflow
    volumes:
        - /stor/OSF_Tracking/tmp/postgresql:/var/lib/postgresql/data

webserver:
    image: puckel/docker-airflow:1.7.1.3-3
    restart: always
    depends_on:
        - postgres
        - rabbitmq
    environment:
        # - LOAD_EX=n
        - EXECUTOR=Celery
    volumes:
        - /stor/OSF_Tracking/airflow_docker/dags_folder:/usr/local/airflow/dags
        - /stor/OSF_Tracking/airflow_docker/logs:/usr/local/airflow/logs
    ports:
        - "9595:9595"
    command: webserver

flower:
    image: puckel/docker-airflow:1.7.1.3-3
    restart: always
    depends_on:
        - rabbitmq
    environment:
        - EXECUTOR=Celery
    ports:
        - "5555:5555"
    command: flower

scheduler:
    image: puckel/docker-airflow:1.7.1.3-3
    restart: always
    depends_on:
        - webserver
    volumes:
        - /stor/OSF_Tracking/airflow_docker/dags_folder:/usr/local/airflow/dags
        - /stor/OSF_Tracking/airflow_docker/logs:/usr/local/airflow/logs
    environment:
        # - LOAD_EX=n
        - EXECUTOR=Celery
    command: scheduler -n 5

worker:
    image: puckel/docker-airflow:1.7.1.3-3
    restart: always
    depends_on:
        - scheduler
    volumes:
        - /stor/OSF_Tracking/airflow_docker/dags_folder:/usr/local/airflow/dags
        - /stor/OSF_Tracking/airflow_docker/logs:/usr/local/airflow/logs
    environment:
        - EXECUTOR=Celery
    command: worker

@sdikby could you follow the webserver and scheduler log and paste the error?

@anurajp i solved it. it was some network problem with an old container version of docker airflow.
I have one last question if i may. To connect to my host via airflow docker i use a tool named sshpass. Icall it each time within any airflow operator for example to execute some extern bash script or to do something in HDFS. I think it is some brute solution because my username/password for the host are hard coded in each DAG. Can you maybe point me to another alternative? Which method do you use to interact with extern component from airflow docker ?

@sdikby apologies for late reply. We use SSHOperator to connect airflow docker with our gateway machine. Our gateway machine has all hadoop clients installed. So far it has worked pretty nicely for us.

@anurajp would you please tell me exactly how you do it with SSHOperator ? maybe with a SSHOperator task layout example? and if i should do something else beside instanciating this operator?

authors: anurajp sdikby

repo: puckel/docker-airflow


text:
"Create a New Exhibit" and

We should probably just choose one of these.  Since "Create a new exhibit" is the text for the button itself, I propose using the same text on the actual creation page.  Thoughts?

As long as it is consistent, I think it's great either way. Go with Collection to make consistent with everything else

repo: pulibrary/dpul


text:
Document dependsOn a Component resource

Document dependsOn a Component resource.  (A new feature in 0.17.1). See https://pulumi-community.slack.com/archives/C84L4E3N1/p1551945676230900.

Closing out stale issue. This is documented in https://www.pulumi.com/docs/intro/concepts/programming-model/

authors: andrewlayman leezen

repo: pulumi/docs


text:
Add home-page video

Also makes a few slight adjustments to improve mobile layout on the home page.

Part of #1213.

cc @aydrian @joeduffy ☝

I updated the title and description and fixed up the auto generated captions. Probably a lot of improvements to the captions. Please let me know if anything to be updated on the YouTube side. It's still unlisted. I can change that when we go live.

authors: aydrian cnunciato


text:
Elastic Beanstalk Option settings not removing

Options settings that have been added using Pulumi not removing from the beanstalk after removing from Pulumi
Expected: When we remove the option settings from Pulumi this has to remove from the Beanstalk also

@locus-akhilkrishna Could you please provide more details on what you're referring to and a repro case if possible? Are you talking about the settings property for an environment or something else?

There isn't a repro here - so will close this out.  But there are a number of issues with Beanstalk in the upstream provider and noted in https://github.com/pulumi/pulumi-aws/issues/920#issuecomment-623580979 which may be relevant.

authors: leezen locus-akhilkrishna lukehoban

repo: pulumi/pulumi-aws


text:
pulumi_aws python package doesn't specify requirement on setuptools / pkg_resources

What happened?
When pulumi project is installed in an environment without setuptools, running program fails with:
Diagnostics:
  pulumi:pulumi:Stack (dev):
    error: Program failed with an unhandled exception:
    Traceback (most recent call last):
      File "__main__.py", line 8, in <module>
        from pulumi_aws import ec2
      File ".venv\Lib\site-packages\pulumi_aws\__init__.py", line 5, in <module>
        from . import _utilities
      File ".venv\Lib\site-packages\pulumi_aws\_utilities.py", line 10, in <module>
        import pkg_resources
    ModuleNotFoundError: No module named 'pkg_resources'

Expected Behavior
pulumi_aws should either explicitly specify its requirement on setuptools or (better) switch away from deprecated technology

Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions.

(https://setuptools.pypa.io/en/latest/pkg_resources.html)
Steps to reproduce
Steps are basically the same as in https://github.com/pulumi/pulumi/issues/12390, just pick aws template and add pip (the workaround)
Output of pulumi about
CLI
Version      3.56.0
Go Version   go1.20.1
Go Compiler  gc
Plugins
NAME    VERSION
aws     5.30.1
gcp     6.51.0
github  5.5.0
python  unknown
Host
OS       Microsoft Windows 11 Home
Version  10.0.22621 Build 22621
Arch     x86_64
This project is written in python: executable='C:\Users\Yuri\AppData\Local\Programs\Python\Python311\python.exe' version='3.11.2
'
Current Stack: dev
Found no resources associated with dev
Found no pending operations associated with dev
Backend
Name           NOID-00646
URL            s3://***
User           NOID-00646\Yuri Timenkov
Organizations
Dependencies:
NAME             VERSION
infra-ci-runner  1.0.0
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).

This actually a Python SDK codegen consideration. Transferring to the pulumi/pulumi.

authors: justinvp ytimenkov


text:
Query of StreamingJob does not seem to work with import

Query in the transformation setting is shown as added when importing a streaming job resource. The query does not seem to be validated at all during import since it is not flagged as deleted if not specifying it at all.

Could you add a code snippet to repro?

Could you add a code snippet to repro?

`
var jobArgs = new StreamingJobArgs
{
CompatibilityLevel = "1.0",
DataLocale = "en-US",
EventsLateArrivalMaxDelayInSeconds = 5,
EventsOutOfOrderMaxDelayInSeconds = 10,
EventsOutOfOrderPolicy = "Adjust",
Functions = { },
JobName = args.Name,
Location = args.Location,
OutputErrorPolicy = "Drop",
ResourceGroupName = args.ResourceGroupName,
Sku = new SkuArgs
{
Name = SkuName.Standard
},
Tags =
{
{ "displayName", "StreamAnalytics" }
},
OutputStartMode = OutputStartMode.LastOutputEventTime,
OutputStartTime = "2020-03-31T10:56:19.017Z",
Transformation = new TransformationArgs
{
//Name = "transformationtest",
Query =
@"WITH
Input AS
(
SELECT
*
FROM
[iothubinput]
)
SELECT
*
INTO
[eventhuboutput]
FROM
Input
",
//StreamingUnits = 1,
}
};
var streamingJob = new StreamingJob($"sasj-", jobArgs,
new CustomResourceOptions
{
ImportId = "/subscriptions//resourceGroups//providers/Microsoft.StreamAnalytics/streamingjobs/"
});`

`
var jobArgs = new StreamingJobArgs
{
CompatibilityLevel = "1.0",
DataLocale = "en-US",
EventsLateArrivalMaxDelayInSeconds = 5,
EventsOutOfOrderMaxDelayInSeconds = 10,
EventsOutOfOrderPolicy = "Adjust",
Functions = { },
JobName = args.Name,
Location = args.Location,
OutputErrorPolicy = "Drop",
ResourceGroupName = args.ResourceGroupName,
Sku = new SkuArgs
{
Name = SkuName.Standard
},
Tags =
{
{ "displayName", "StreamAnalytics" }
},
OutputStartMode = OutputStartMode.LastOutputEventTime,
OutputStartTime = "2020-03-31T10:56:19.017Z",
Transformation = new TransformationArgs
{
//Name = "transformationtest",
Query =
@"WITH
Input AS
(
SELECT
*
FROM
[iothubinput]
)
SELECT
*
INTO
[eventhuboutput]
FROM
Input
",
//StreamingUnits = 1,
}
};
var streamingJob = new StreamingJob($"sasj-", jobArgs,
new CustomResourceOptions
{
ImportId = "/subscriptions//resourceGroups//providers/Microsoft.StreamAnalytics/streamingjobs/"
});`

Another minor thing compared to the query, is that these two, especially OutputStartTime should not be validated during import, since that is only a runtime value when last starting the service.
OutputStartMode = OutputStartMode.LastOutputEventTime,
OutputStartTime = "2020-03-31T10:56:19.017Z",

Another minor thing compared to the query, is that these two, especially OutputStartTime should not be validated during import, since that is only a runtime value when last starting the service.
OutputStartMode = OutputStartMode.LastOutputEventTime,
OutputStartTime = "2020-03-31T10:56:19.017Z",

Thank you, I'll take a look. For now, try listing that property in the IgnoreChanges option to upblock the import

Thank you, I'll take a look. For now, try listing that property in the IgnoreChanges option to upblock the import

is that these two, especially OutputStartTime should not be validated during import, since that is only a runtime value when last starting the service.

There's nothing in the specification that says they aren't valid input values, so we just treat them normally. If you think they should be read-only, please file an issue in the specs repo.
query isn't special in any way either, see spec, so we can't predict that the API wouldn't return the value when we read it.
I hope IgnoreChanges can get you through.

is that these two, especially OutputStartTime should not be validated during import, since that is only a runtime value when last starting the service.

There's nothing in the specification that says they aren't valid input values, so we just treat them normally. If you think they should be read-only, please file an issue in the specs repo.
query isn't special in any way either, see spec, so we can't predict that the API wouldn't return the value when we read it.
I hope IgnoreChanges can get you through.

Ignore changes is fine for the two Output properties, but not for Query, since that is something you would want Pulumi to track and update if changed.

Ignore changes is fine for the two Output properties, but not for Query, since that is something you would want Pulumi to track and update if changed.

You can remove IgnoreChanges after the import and re-run pulumi up

You can remove IgnoreChanges after the import and re-run pulumi up

Is this an upstream issue that you should report as well, same as with SiteConfig on WebApp, where the transformation object is not returned when you query the streaming job api?

Is this an upstream issue that you should report as well, same as with SiteConfig on WebApp, where the transformation object is not returned when you query the streaming job api?

It could be. Feel free to open an issue upstream with this question.

It could be. Feel free to open an issue upstream with this question.

authors: WillooWisp mikhailshilkov

repo: pulumi/pulumi-azure-nextgen


text:
Bug in automatic location propagation for non-existing resource groups

I think #216 doesn't fully work just yet.
Here is a simple repro:
import * as pulumi from "@pulumi/pulumi";
import * as azure from "@pulumi/azure";

const resourceGroup = new azure.core.ResourceGroup("test", { location: "WestUS" });

const sa = new azure.storage.Account("storage", {
    resourceGroupName: resourceGroup.name,
    accountReplicationType: "LRS",
    accountTier: "Standard"
});

If I run this on a clean stack, I get an error on preview:
    panic: interface conversion: interface {} is resource.Computed, not string
    goroutine 70 [running]:
    github.com/pulumi/pulumi-azure/vendor/github.com/pulumi/pulumi/pkg/resource.PropertyValue.StringValue(...)
        /home/travis/gopath/src/github.com/pulumi/pulumi-azure/vendor/github.com/pulumi/pulumi/pkg/resource/properties.go:327
    github.com/pulumi/pulumi-azure.Provider.func1(0xc0007a8f60, 0xc000478ae0, 0x31ab6c8, 0x8, 0x60c1ba0)
        /home/travis/gopath/src/github.com/pulumi/pulumi-azure/resources.go:967 +0x565
    github.com/pulumi/pulumi-azure/vendor/github.com/pulumi/pulumi-terraform/pkg/tfbridge.MakeTerraformInputs(0xc0007a8f60, 0xc000478ae0, 0xc000478b10, 0xc0006f4c90, 0xc00066dce0, 0xc000543780, 0xc0004892c0, 0x1, 0xc000713648, 0x47c902, ...)
        /home/travis/gopath/src/github.com/pulumi/pulumi-azure/vendor/github.com/pulumi/pulumi-terraform/pkg/tfbridge/schema.go:184 +0xe9e
    github.com/pulumi/pulumi-azure/vendor/github.com/pulumi/pulumi-terraform/pkg/tfbridge.(*Provider).Check(0xc000362b40, 0x375b660, 0xc000478a50, 0xc000bd1400, 0xc000362b40, 0x2d8fc01, 0xc000bd1440)
        /home/travis/gopath/src/github.com/pulumi/pulumi-azure/vendor/github.com/pulumi/pulumi-terraform/pkg/tfbridge/provider.go:451 +0x680
    github.com/pulumi/pulumi-azure/vendor/github.com/pulumi/pulumi/sdk/proto/go._ResourceProvider_Check_Handler.func1(0x375b660, 0xc000478a50, 0x2fbb2a0, 0xc000bd1400, 0x300eae0, 0x60c05e0, 0x375b660, 0xc000478a50)
        /home/travis/gopath/src/github.com/pulumi/pulumi-azure/vendor/github.com/pulumi/pulumi/sdk/proto/go/provider.pb.go:1295 +0x8d
    github.com/pulumi/pulumi-azure/vendor/github.com/grpc-ecosystem/grpc-opentracing/go/otgrpc.OpenTracingServerInterceptor.func1(0x375b660, 0xc000478900, 0x2fbb2a0, 0xc000bd1400, 0xc0007a8e00, 0xc0007a8e20, 0x0, 0x0, 0x36f19c0, 0xc0002bee90)
        /home/travis/gopath/src/github.com/pulumi/pulumi-azure/vendor/github.com/grpc-ecosystem/grpc-opentracing/go/otgrpc/server.go:57 +0x2eb
    github.com/pulumi/pulumi-azure/vendor/github.com/pulumi/pulumi/sdk/proto/go._ResourceProvider_Check_Handler(0x3059300, 0xc000362b40, 0x375b660, 0xc000478900, 0xc000906dc0, 0xc00051cee0, 0x375b660, 0xc000478900, 0xc0000f2750, 0xc2)
        /home/travis/gopath/src/github.com/pulumi/pulumi-azure/vendor/github.com/pulumi/pulumi/sdk/proto/go/provider.pb.go:1297 +0x15f
    github.com/pulumi/pulumi-azure/vendor/google.golang.org/grpc.(*Server).processUnaryRPC(0xc0004c4600, 0x379de80, 0xc0002aaa80, 0xc0007abf00, 0xc000488870, 0x6094c80, 0x0, 0x0, 0x0)
        /home/travis/gopath/src/github.com/pulumi/pulumi-azure/vendor/google.golang.org/grpc/server.go:971 +0x477
    github.com/pulumi/pulumi-azure/vendor/google.golang.org/grpc.(*Server).handleStream(0xc0004c4600, 0x379de80, 0xc0002aaa80, 0xc0007abf00, 0x0)
        /home/travis/gopath/src/github.com/pulumi/pulumi-azure/vendor/google.golang.org/grpc/server.go:1250 +0xd2c
    github.com/pulumi/pulumi-azure/vendor/google.golang.org/grpc.(*Server).serveStreams.func1.1(0xc0002f0050, 0xc0004c4600, 0x379de80, 0xc0002aaa80, 0xc0007abf00)
        /home/travis/gopath/src/github.com/pulumi/pulumi-azure/vendor/google.golang.org/grpc/server.go:690 +0xa6
    created by github.com/pulumi/pulumi-azure/vendor/google.golang.org/grpc.(*Server).serveStreams.func1
        /home/travis/gopath/src/github.com/pulumi/pulumi-azure/vendor/google.golang.org/grpc/server.go:688 +0xa8

    error: transport is closing

Workaround:
I can make it work by first deploying the resource group without the storage account, and then deploying the storage account. If the resource group exists, location propagation works as advertised.

tagging @joeduffy @jen20

repo: pulumi/pulumi-azure


text:
v6 Checklist

Running list of changes to make in the next major version of pulumi-azure:

[ ] Remove resources like NamespaceAuthorizationRule which were renamed and are deprecated. Example: https://github.com/pulumi/pulumi-azure/issues/998
[ ] Remove type overrides for azurerm_availability_set.

@mikhailshilkov Is this repo still maintained? I'm using the Azure-Native provider for almost everything, but some things are not supported in the native provider, e.g., creating Azure Keyvault Access Rules as independent Resources. I tried to use this provider alongside the native provider, but this repo misses some tags for the go SDK. For the latest version, there is no Tag available:

I'm happy to contribute the missing resource to the native provider, but I wonder what the intention is within the community.

I tried to use this provider alongside the native provider, but this repo misses some tags for the go SDK.

That's unexpected! Could you please file a separate issue and we'll fix it asap? Thank you!

authors: mikhailshilkov stefanhenseler


text:
Unable to use OriginCaCertificate

What happened?
I'm trying to generate origin ca certificates. As per the documentation, This resource requires you use your Origin CA Key as the api_user_service_key, in conjunction with an api_token or email and api_key.. However, if I try to have both the api_user_service_key and one of api_token or (email and api_key), the provider refuses to validate the configuration.
Steps to reproduce

Set the api_user_service_key, email and api_key as needed (I've tried both using the config and the environment variables.)
Try to create a OriginCaCertificate resource.
An error occurs:

  cloudflare:index:OriginCaCertificate (cf-origin-cert):
    error: could not validate provider configuration: 3 errors occurred:
        * Invalid combination of arguments: "api_key": only one of `api_key,api_token,api_user_service_key` can be specified, but `api_token,api_user_service_key` were specified.
        * Invalid combination of arguments: "api_user_service_key": only one of `api_key,api_token,api_user_service_key` can be specified, but `api_token,api_user_service_key` were specified.
        * Invalid combination of arguments: "api_token": only one of `api_key,api_token,api_user_service_key` can be specified, but `api_token,api_user_service_key` were specified.

Expected Behavior
A certificate will be generated.
Actual Behavior
An error occurred, preventing the provider from validating its config.
Output of pulumi about
No response
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).

On further inspection this seems to be an upstream issue, which was fixed in v3.25.0

Hi @ehhthing - thank you for filing this issue, and for the followup! Let me see if I can cut an upgrade for you here :)

authors: ehhthing guineveresaenger

repo: pulumi/pulumi-cloudflare


text:
The priority have different value between inputs and outputs

What happened?
the command pulumi preview always show plan update for Pagerule with priority change
   ~ cloudflare:index/pageRule:PageRule: (update)
        [id=a0efd388972a6cf571ae64b33729a335]
        [urn=urn:pulumi:<redacted>:pulum::cloudflare:index/pageRule:PageRule::<redacted>]
        [provider=urn:pulumi:<redacted>:pulum::pulumi:providers:cloudflare::default_5_0_0::a0abfaba-348c-4230-b2bc-11ed8f071084]
      ~ priority: 15 => 16

Expected Behavior
the priority should be updated accordingly between inputs and outputs
Steps to reproduce

create multiple Pagerule
run pulumi up to create page rules
insert a page rule to make priority change
run pulumi up to apply change
run pulumi preview --diff
notice that priority didn't updated

Output of pulumi about
Found no pending operations associated with <redacted>

Backend
Name           <redacted>
URL            s3://system-pulumi/<redacted>?endpoint=<redacted>&s3ForcePathStyle=true
User           <redacted>
Organizations

Dependencies:
NAME                   VERSION
json-duplicate-keys    23.2.7
pip                    23.0.1
pulumi-cloudflare      5.0.0
pulumi-confluentcloud  1.12.0
pulumi-vault           5.8.0
pulumiverse-sentry     0.0.8
requests               2.28.2
setuptools             67.0.0
wheel                  0.38.4

Pulumi locates its logs in /var/folders/g1/sqrw886s103g1bl1jldvmjx00000gq/T/ by default

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

HI @bds-congnguyen, thank you for opening this issue. Would you be able to provide a minimal program for us to attempt to reproduce?

HI there,
first you need create a json file name PageRule.json
replace value <your_domain> and <your_zone_id>
{
    "<your_domain>/pulumi-test-pagerule-priority-change": {
        "actions": {
            "cache_level": "bypass"
        }
    },
    "<your_domain>/pulumi-test-pagerule-priority-change2": {
        "actions": {
            "cache_level": "bypass"
        }
    },
    "<your_domain>/pulumi-test-pagerule-priority-change3": {
        "actions": {
            "cache_level": "bypass"
        }
    }
}

then create minimal program with
import json
import pulumi_cloudflare as cloudflare
import pulumi

PRIORITY = 1
zoneID=<your_zone_id>
file="PageRule.json"
with open(file) as f:
            parsed = json.load(f)
for k, v in parsed.items():
                v['name'] = k
                PageRule(v)
def PageRule(v):
        v['actions'] = cloudflare.PageRuleActionsArgs(**v['actions'])
        v['resource_name'] = f"{v['name']}_DOMAIN_{zoneID}"
        v['zone_id'] = zoneID
        v['target'] = v['name']
        v.pop('name', None)
        if "status" not in v:
            v["status"] = "active"
        v["priority"] = PRIORITY
        cloudflare.PageRule(**v)
        PRIORITY += 1

I also noticed that when run pulumi up --debug with debug option, it show
    debug: resource registration successful: ty=cloudflare:index/pageRule:PageRule, urn=urn:pulumi:<redacted>::pulum::cloudflare:index/pageRule:PageRule::<redacted>
    error: update failed
    debug: resource registration successful: ty=cloudflare:index/pageRule:PageRule, urn=urn:pulumi:<redacted>::pulum::cloudflare:index/pageRule:PageRule::<redacted>
    debug: resource registration successful: ty=cloudflare:index/pageRule:PageRule, urn=urn:pulumi:<redacted>::pulum::cloudflare:index/pageRule:PageRule::<redacted>
    debug: resource registration successful: ty=cloudflare:index/pageRule:PageRule, urn=urn:pulumi:<redacted>::pulum::cloudflare:index/pageRule:PageRule::<redacted>

Resources:
    1409 unchanged

Duration: 36s

I don't know reason of error: update failed,

Everything I've tried here behaves as expected.  Adding and removing rules updates the priority as expected even when priorities are added or removed in the middle or end.
Here was my more slightly shorted version of the repro - though I can't see anything in the Python repro that was trying to do anything different here.
let priority = 1
const parsed = {
    "ts-test-cloudflare-kl7hhx86-zone.com/pulumi-test-pagerule-priority-change": {
        "actions": {
            "cacheLevel": "bypass"
        }
    },
    // "ts-test-cloudflare-kl7hhx86-zone.com/pulumi-test-pagerule-priority-change2": {
    //     "actions": {
    //         "cacheLevel": "bypass"
    //     }
    // },
    "ts-test-cloudflare-kl7hhx86-zone.com/pulumi-test-pagerule-priority-change3": {
        "actions": {
            "cacheLevel": "bypass"
        }
    }
}

for (const [k, v] of Object.entries(parsed)) {
    new cloudflare.PageRule(k, {
        actions: v.actions,
        zoneId: zone.id,
        target: k,
        priority: priority,
    });
    priority += 1;
}

Going to close as no repro, but if anyone has a reliabel repro with repro steps - would love to see it!

authors: aq17 bds-congnguyen lukehoban


text:
Pulumi.yaml backend variables

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
Pulumi.yaml, enable the option to use variables in the backend url variable like:
backend:
   url: s3://${PROJECT}-${STACK}-test.bucket.com"

Affected area/feature

Hey @saarw-opti, thanks for asking this.
If you're looking to generate stack references that include the project or stack name, in the variables, resources, and outputs blocks of Pulumi that is supported via the built-in pulumi variable name:
https://www.pulumi.com/docs/languages-sdks/yaml/yaml-language-reference/#built-in-variables
That won't work with the "backend" field of the project file, though. Can you elaborate on the use case for supporting interpolation in the backend field?

This sounds like it's not about Pulumi YAML (the language) but about the Pulumi.yaml project file for any Pulumi project.  So moving to pulumi/pulumi.
It also sounds like it's an ask to solve the same problem as https://github.com/pulumi/pulumi/issues/11182, but via a different approach.  In that issue, the backend url can be specified as part of the stack file.  In this issue, it is specified in the project file but with replacements applied.  The approach suggested here does have some benefits that this doesn't have to be copied into every stack file.  But solving this would also likely resolve 11182.

authors: AaronFriel lukehoban saarw-opti

repo: pulumi/pulumi-yaml


text:
Issues with GIFs

I've run into a very odd issue with gifs. It revolves around JIMP, but I haven't seen it mentioned there, so I'm not 100% sure yet whether the issue is with JIMP, or with this particular implementation of it.
When trying to upload a gif with apostrophe-images, it gives the generic image error in the browser, and on the server, it gives the following error output:
Unsupported MIME type: image/gif
Unsupported MIME type: image/gif
Unsupported MIME type: image/gif
Unsupported MIME type: image/gif
Unsupported MIME type: image/gif
Unsupported MIME type: image/gif
TypeError: Cannot read property 'bitmap' of undefined
    at Jimp.<anonymous> (/Users/nick/Development/annual-report/cms/node_modules/apostrophe/node_modules/uploadfs/lib/image/jimp.js:46:34)
    at Jimp.throwError (/Users/nick/Development/annual-report/cms/node_modules/jimp/index.js:85:44)
    at ReadFileContext.callback (/Users/nick/Development/annual-report/cms/node_modules/jimp/index.js:201:44)
    at FSReqWrap.readFileAfterOpen [as oncomplete] (fs.js:366:13)

Jimp knows what the MIME type is in previous functions, and has a conditional to handle image/gif specifically, yet when it gets here, the image variable is undefined. Let me know if there's more information I can provide, I'm not the best at debugging, haha.

Happens with every gif?
On Wed, May 9, 2018, 7:43 PM tortilaman notifications@github.com wrote:

I've run into a very odd issue with gifs. It revolves around JIMP, but I
haven't seen it mentioned there, so I'm not 100% sure yet whether the issue
is with JIMP, or with this particular implementation of it.
When trying to upload a gif with apostrophe-images, it gives the generic
image error in the browser, and on the server, it gives the following error
output:
Unsupported MIME type: image/gif
Unsupported MIME type: image/gif
Unsupported MIME type: image/gif
Unsupported MIME type: image/gif
Unsupported MIME type: image/gif
Unsupported MIME type: image/gif
TypeError: Cannot read property 'bitmap' of undefined
at Jimp. (/Users/nick/Development/annual-report/cms/node_modules/apostrophe/node_modules/uploadfs/lib/image/jimp.js:46:34)
at Jimp.throwError (/Users/nick/Development/annual-report/cms/node_modules/jimp/index.js:85:44)
at ReadFileContext.callback (/Users/nick/Development/annual-report/cms/node_modules/jimp/index.js:201:44)
at FSReqWrap.readFileAfterOpen [as oncomplete] (fs.js:366:13)
Jimp knows what the MIME type is in previous functions, and has a
conditional to handle image/gif specifically, yet when it gets here, the
image variable is undefined. Let me know if there's more information I
can provide, I'm not the best at debugging, haha.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/punkave/uploadfs/issues/37, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB9ffPXObg83RLGmmi6qA2ISCQvlS_uks5tw38ogaJpZM4T5J43
.

Jimp is the slowest option btw but of course we want it to work too because
it is the zero effort option.
On Wed, May 9, 2018, 7:43 PM tortilaman notifications@github.com wrote:

I've run into a very odd issue with gifs. It revolves around JIMP, but I
haven't seen it mentioned there, so I'm not 100% sure yet whether the issue
is with JIMP, or with this particular implementation of it.
When trying to upload a gif with apostrophe-images, it gives the generic
image error in the browser, and on the server, it gives the following error
output:
Unsupported MIME type: image/gif
Unsupported MIME type: image/gif
Unsupported MIME type: image/gif
Unsupported MIME type: image/gif
Unsupported MIME type: image/gif
Unsupported MIME type: image/gif
TypeError: Cannot read property 'bitmap' of undefined
at Jimp. (/Users/nick/Development/annual-report/cms/node_modules/apostrophe/node_modules/uploadfs/lib/image/jimp.js:46:34)
at Jimp.throwError (/Users/nick/Development/annual-report/cms/node_modules/jimp/index.js:85:44)
at ReadFileContext.callback (/Users/nick/Development/annual-report/cms/node_modules/jimp/index.js:201:44)
at FSReqWrap.readFileAfterOpen [as oncomplete] (fs.js:366:13)
Jimp knows what the MIME type is in previous functions, and has a
conditional to handle image/gif specifically, yet when it gets here, the
image variable is undefined. Let me know if there's more information I
can provide, I'm not the best at debugging, haha.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/punkave/uploadfs/issues/37, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB9ffPXObg83RLGmmi6qA2ISCQvlS_uks5tw38ogaJpZM4T5J43
.

I tried it with several different gifs. Different tools were used to export them and I had them exported at different sizes.
I was a bit confused why it was trying to use Jimp and not ImageMagick or something else.

You have to have the imagemagick convert and identify utilities in your
PATH.
On Thu, May 10, 2018, 1:32 PM tortilaman notifications@github.com wrote:

I tried it with several different gifs. Different tools were used to
export them and I had them exported at different sizes.
I was a bit confused why it was trying to use Jimp and not ImageMagick or
something else.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/punkave/uploadfs/issues/37#issuecomment-388125839,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB9fTNV55ojkVG_pNu7OVrTqIjWDnauks5txHmrgaJpZM4T5J43
.

Ah, that might be difficult with cloud hosting. I'll look into it. Thanks for the info.

Heroku has it. Amazon EC2, you can install it from package manager at
startup of the instance, for instance via etc/rc.local
On Thu, May 10, 2018, 4:32 PM tortilaman notifications@github.com wrote:

Ah, that might be difficult with cloud hosting. I'll look into it. Thanks
for the info.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/punkave/uploadfs/issues/37#issuecomment-388176662,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB9fZDaXUuMzT_aXDVRhBo_WAsYTfqgks5txKPtgaJpZM4T5J43
.

I would think adding documentation to make the limitation clear, along with that flag to fake it is probably sufficient for now.
That being said, in the thread you linked this Jimp compatible gif tool was mentioned. From an initial look it doesn't seem mature enough for production code, and I didn't see if it supports resizing.
I think a more important consideration though is that when using GIFs there's always a quality/filesize compromise (or challenge) that has to be overcome before even uploading. Would resizing gifs that a user (may have) spent a lot of time optimizing cause quality/filesize or optimization issues?

I'll work on a PR for faking it as I can.

authors: boutell tortilaman

repo: punkave/uploadfs


text:
Enable a way to access an Element properties with ElementHandle

I would like for example to do
   let input = await page.$('input')
   assert.equal(input.value, 'some text')

It could be input.getAttribute('value') or/and getProperty('value'). Or anything else that could make sense.

This will work out nicely with #382.

@aslushnikov I see. I didn't realise this PR was solving this problem. ElementHandle would inherit from ObjectHandle and you could do input .property('foo')
This would be very nice because ATM testing the value of an input is quite awkward.

Temporarily, you can use a DOM manipulator like JSDOM to get value (if you also want to navigate through DOM)
let content  = await page.content();
let dom = new JSDOM(content);
let value = dom.window.document.querySelector(selector).value;

The page.content() method is pushed to master branch a few hours ago.
To be able to use it, you would have to install the puppeteer via GitHub (only until update via npm is available)
npm i --save https://github.com/GoogleChrome/puppeteer

JSHandles have landed; now the following is possible:
let input = await page.$('input');
let valueHandle = await input.getProperty('value');
assert.equal(await valueHandle.jsonValue(), 'some text')

Hi it doesn't seem to get all of the properties, for example how do I get source of an Iframe, doing this code:

var puppeteer = require("puppeteer");

(async() => {
    var browser = await puppeteer.launch();
    console.log("Got browser", browser);
    var page = await browser.newPage();
    console.log(page,"got page");
    await page.goto("https://docs.google.com/file/d/1Cyuh41yNfYZU_zL-MHLf_EPJCYnlT7oJ/preview?enablejsapi=1&playerapiid=player4");
    console.log("went to page..");

    var clickEl = ".ndfHFb-c4YZDc-aTv5jf-bVEB4e-RJLb9c";
    await page.click(clickEl);
    console.log("clicked")
    var frame = await page.waitForSelector("iframe[id=drive-viewer-video-player-object-0]");
    var props = await frame.getProperties();
    console.log(frame, "got video frame, props: ", props);
)();

only prints: 'got video frame, props: ' Map {} even though I know there are tons of more DOM properties like src ??

@yaakovyitzchak it doesn't seem to get all of the properties, for example how do I get source of an Iframe, doing this code:

Related to: https://github.com/puppeteer/puppeteer/issues/4995 - elementHandle.getProperties() returns an empty map - which i think is a bug

Hey can anyone answer this plz ?
https://stackoverflow.com/questions/66541493/how-to-check-the-disabled-property-on-an-element-handle-in-puppeteer

authors: Rupeshiya aslushnikov batiste emadehsan evandrocoan yaakovyitzchak

repo: puppeteer/puppeteer


text:
(BOLT-1170) Fixing crashes caused by large file uploads during apply() blocks

Background
Details are in the JIRA ticket: https://tickets.puppetlabs.com/browse/BOLT-1170
Potential solution
Instead of base64 encoding the plugins tarball and catalog, i've written these out as temporary files and attached them to the Bolt::Task that apply() executes on the target hosts. Transports then take care of uploading all files  (extra files) associated with a task, putting them in the _installdir automatically for us. Finally libexec/apply_catalog.rb reads the plugins tarball and catalog from the filesystem at _installdir instead of from STDIN arguments.
Extent of my testing
I've tested this out practically using the same scenario where it was failing previously and no issues occurred on Linux (SSH transport) or Windows hosts (WinRM transport). Actually the Windows hosts executed faster because the WinRM file upload was much quicker than having the data base64 encoded (actually makes it larger) and added onto the command line.
TODO

[ ] Check if this works with PXP / Orchestrator
[ ] Check if we should be using this "out-of-band" transfer for the two other places where we transfer plugin tarballs:

[ ] bolt-modules/boltlib/lib/puppet/functions/apply_prep.rb
[ ] bolt-modules/boltlib/lib/puppet/functions/get_resources.rb

[ ] Potential further optimization. Instead of tar'ing up the whole files/ directory for every module, we could inspect the catalog for puppet:/// URIs and only include the files referenced by the resources in the catalog. Question? The only place i know if this being used is in a 'file' resource in the 'source' parameter, are there other places where this URI type is valid?

CLA signed by all contributors.

It will definitely not work with orchestrator since the "task" files used are ones deployed to the master. We'll have to continue base64 encoding these there.
I think is a good optimization otherwise. I feel like we're getting to the point that we need to extract the set up a puppet environment logic into some shared code.

authors: adreyer nmaludy puppetcla

repo: puppetlabs/bolt


text:
(BUG) Cannot run exec command with tool

Describe the bug
During the execution of the exec command I assume PRM builds the docker image in order to run the tool.  It appears as if that image build is failing and the image is never created therefore the tool cannot be run.
To Reproduce
Steps to reproduce the behavior:

Install prm on a clean system
Run prm exec puppetlabs/ra10ke
See error

Expected behavior
Would see output related to running ra10ke
Screenshots or logs
➜  ~ prm exec puppetlabs/ra10ke -d --log-level=debug
12:35AM DBG pkg/prm/prm.go:157 > Searching /home/user1/.puppetlabs/prm/tools for tool configs
12:35AM DBG pkg/prm/prm.go:163 > Found: /home/user1/.puppetlabs/prm/tools/nwops/debugger/0.1.1/prm-config.yml
12:35AM DBG pkg/prm/prm.go:163 > Found: /home/user1/.puppetlabs/prm/tools/nwops/debugger/0.1.2/prm-config.yml
12:35AM DBG pkg/prm/prm.go:163 > Found: /home/user1/.puppetlabs/prm/tools/puppetlabs/epp/0.1.0/prm-config.yml
12:35AM DBG pkg/prm/prm.go:163 > Found: /home/user1/.puppetlabs/prm/tools/puppetlabs/heira-eyaml/0.1.0/prm-config.yml
12:35AM DBG pkg/prm/prm.go:163 > Found: /home/user1/.puppetlabs/prm/tools/puppetlabs/metadata-json-lint/0.1.0/prm-config.yml
12:35AM DBG pkg/prm/prm.go:163 > Found: /home/user1/.puppetlabs/prm/tools/puppetlabs/onceover/0.1.0/prm-config.yml
12:35AM DBG pkg/prm/prm.go:163 > Found: /home/user1/.puppetlabs/prm/tools/puppetlabs/parser/0.1.0/prm-config.yml
12:35AM DBG pkg/prm/prm.go:163 > Found: /home/user1/.puppetlabs/prm/tools/puppetlabs/puppet-lint/0.1.0/prm-config.yml
12:35AM DBG pkg/prm/prm.go:163 > Found: /home/user1/.puppetlabs/prm/tools/puppetlabs/puppet-strings/0.1.0/prm-config.yml
12:35AM DBG pkg/prm/prm.go:163 > Found: /home/user1/.puppetlabs/prm/tools/puppetlabs/puppet-syntax/0.1.0/prm-config.yml
12:35AM DBG pkg/prm/prm.go:163 > Found: /home/user1/.puppetlabs/prm/tools/puppetlabs/r10k/0.1.0/prm-config.yml
12:35AM DBG pkg/prm/prm.go:163 > Found: /home/user1/.puppetlabs/prm/tools/puppetlabs/ra10ke/0.1.0/prm-config.yml
12:35AM DBG pkg/prm/prm.go:163 > Found: /home/user1/.puppetlabs/prm/tools/puppetlabs/rubocop/0.1.0/prm-config.yml
12:35AM DBG pkg/prm/prm.go:163 > Found: /home/user1/.puppetlabs/prm/tools/puppetlabs/spec_cache/0.1.0/prm-config.yml
12:35AM DBG pkg/prm/prm.go:163 > Found: /home/user1/.puppetlabs/prm/tools/puppetlabs/spec_puppet/0.1.0/prm-config.yml
12:35AM INF pkg/prm/docker.go:95 > Creating new image. Please wait...
12:35AM DBG pkg/prm/docker.go:101 > Creating Dockerfile
--------------------
FROM puppet/puppet-agent:7.0.0
RUN apt update
RUN apt install git -y
RUN /opt/puppetlabs/puppet/bin/gem install bundler --no-document
RUN /opt/puppetlabs/puppet/bin/gem install ra10ke -f --conservative --minimal-deps --no-document
RUN /opt/puppetlabs/puppet/bin/gem install rubygems-update -f --conservative --minimal-deps --no-document
COPY ./content/* /tmp/
VOLUME [ /code, /cache ]
WORKDIR /code
ENTRYPOINT ["/tmp/entrypoint.sh"]
CMD ["-T"]
--------------------

12:35AM DBG pkg/prm/docker.go:159 > Step 1/11 : FROM puppet/puppet-agent:7.0.0
12:35AM INF pkg/prm/docker.go:261 > Code path: /home/user1
12:35AM INF pkg/prm/docker.go:263 > Cache path: /home/user1/.pdk/prm/cache
12:35AM INF pkg/prm/docker.go:265 > Additional Args: []
12:35AM ERR pkg/prm/exec.go:29 > Error executing tool puppetlabs/ra10ke: Error response from daemon: No such image: pdk:puppet-7.0.0_puppetlabs-ra10ke_0.1.0
Error: Error response from daemon: No such image: pdk:puppet-7.0.0_puppetlabs-ra10ke_0.1.0

What versions are you running?:

PopOS 21.10
Docker 20.10.12
prm 0.1.0 36276c0 2022/01/31

Additional context
Add any other context about the problem here.

So the issue above is a result of trying to use a docker image that does not exist.  I don't know how prm gathers the puppet version but the reference to this image is causing a failure to build and run the tool.
docker run -ti puppet/puppet-agent:7.0.0 /bin/bash
Unable to find image 'puppet/puppet-agent:7.0.0' locally
docker: Error response from daemon: manifest for puppet/puppet-agent:7.0.0 not found: manifest unknown: manifest unknown.
See 'docker run --help'.

repo: puppetlabs/prm


text:
(PUP-4199) Add codedir to ARGV in config.ru example

While our config.ru was mostly modified to work with the AIO and Puppet
4, we missed adding the codedir option. This commit adds that with the
default of /etc/puppetlabs/code as the value.

:+1: will merge after master branch is open for merges, likely Monday

CLA signed by all contributors.

authors: joshcooper puppetcla stahnma

repo: puppetlabs/puppet


text:
(PUP-6270) Update Acceptance tests for PUP-3827

PUP-3827 updated the error messages from the indirector to return valid
JSON.
There are acceptance tests that parse error messages - assuming plain text -
to validate that improper behavior cannot be accomplished. This
relaxes the validation to allow for JSON formatted error messages.

Apparently, the local test run I did in https://github.com/puppetlabs/puppet/pull/4875 managed to not actually run some master tests... Still not sure how. But this is now failing in CI.
I got these reliably failing locally (don't know how they didn't before). I'm running these locally, fingers crossed.

LGTM. Please merge once Justin's laptop test completes.
/cc @shrug, @geoffnichols

The regular expression relaxing doesn't fix some of the tests, which are still failing deeper within test helper methods. It shouldn't be too hard to fix these on Monday. But doing further surgery on a Friday evening is not a practical path forward. Reverting in PR #4948 until we can work on this Monday.

CLA signed by all contributors.

authors: justinstoller kylog puppetcla


text:
(PUP-10528) Extend trusted_external_command to support a directory

If a directory is specified, then trusted['external'] will contain a
hash of <basename> => <data> for each executable file in the directory.
Signed-off-by: Enis Inan enis.inan@puppet.com

Looking into the appveyor failures

Appveyor's still running into that maxwaitforlock issue that I think https://github.com/puppetlabs/puppet/pull/8171 was supposed to fix?

CLA signed by all contributors.

Cool, rebased to pick up https://github.com/puppetlabs/puppet/pull/8178 and now CI's passing.

jenkins please test this with servertests

Looks good @ekinanp. I think these lines are left over from before and need to be deleted? https://github.com/puppetlabs/puppet/pull/8173/files#diff-265f9ffdaee6639c0831fd19bd1b25b3R23-R24. Could you also update the new setting description to mention how the basename of the file will be the key in the trusted hash?

@joshcooper Thanks, addressed the review feedback.

authors: ekinanp joshcooper puppetcla


text:
Master

Thnx

Can one of the admins verify this patch?

Hello, what's going on?


text:
(PUP-11691) Report configured environment dir even when containing resolved symlinks

Needs more work and tests, but wanted to put what I have so far up to discuss approach.

Looks good to me, thanks @justinstoller!

Thanks, Josh!
FWIW, I looked into threading this info through the parser and into the locator but there's several places where we call the parser and few of them have local references to the environment anyways. It does look like all resource creation goes through this code, and we're already pulling the environment out of the scope, so it seemed like a good approach.

Soooo, when looking for a way to test this I found another place where we legitimately create Resources outside of the Runtime3ResourceSupport module, which made me think the file munging might better be done within the Resource class itself.

Rebased onto 7.x.

This PR is picking up the wrong set of tests because it originally targeted main. Going to close and reopen to use the 7.x tests.

jenkins please test this with servertests

@joshcooper said prior to merging we should see that "servertests" pass. They've passed now so I will merge!

authors: joshcooper justinstoller mhashizume


text:
(maint) tweaks to anonymization

when randomizing strings, use a max length equal to the length of the target
when randomizing floats, cap the value with the target
remove some unused leaf types

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-stable/49/
Test FAILed.

@puppetlabs-jenkins test this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-stable/50/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-stable/51/
Test PASSed.

authors: puppetlabs-jenkins wkalt

repo: puppetlabs/puppetdb


text:
FreeBSD PostgreSQL wouldn't start first time

It would be enabled, but it wouldn't work properly. This fixes that
issue the same way Puppet does itself; use the onestart/onestop and most
importantly in this case, the onestatus command.
By using this approach it means the Database server will actually start
whereas it would not before. It would enable, but not actually start.
onestatus means the service type gets the right response and behaves
properly.

for reference (from rc.subr(8)):
one	Skip the checks	for rcvar being	set to ``YES'',	but
    performs all the other prerequisite tests.

:+1: from me.

authors: igalic leepa

repo: puppetlabs/puppetlabs-postgresql


text:
Create highlevel-main

branch to be used as main for all high level work. intent is the separate this branch and whatever PRs will happen with our main and testing branches. Branches off of this should be named as highlevel-YOUR_NAME_HERE or highlevel-TASK_HERE. If a feature branch, it should be deleted when merged. If an individual branch, it may be kept or deleted depending on if future work is expected.
This PR exists primarily so that new contributors can be familiar with the existing high level codebase.

I'll plan to merge this in a day or so. Feel free to review the code and point out anything that looks odd so that we can add it to our list of planned improvements.

Once merged, the snake-dqn branch should be deleted.


text:
Can't find the password for vault id start with "-"

Please agree to the following

[X] I have searched existing issues for duplicates

Summary
The cryptomator's vault id starts with hyphen won't be able to locate the saved password in Keepass
What software is involved?

Operating System: Ubuntu 22.04.2 LTS
Cryptomator: 1.6.17
keepassxc-cryptomator-1.2.1.jar
KeePassXC: 2.6.6 (ubuntu official package)

Steps to Reproduce
Have no idea how to reproduce the cryptomator's vault ID with hyphen in the beginning. (-Ucq0zYwVtth)
But when I remove the vault, and successfully import it again to Cryptomator with new ID (tIcNZ-5GLXQ_), everything is normal.
Expected Behavior
The saved vault would be opened successfully
Actual Behavior
The saved vault can't auto-open, it would display the form to enter password even the new record was already successfully created in Keepass
Reproducibility
Always
Relevant Log Output
11:00:33.703 [JavaFX Application Thread] INFO  o.p.i.keychain.KeePassXCAccess - No password found for vault -Ucq0zYwVtth
11:00:38.109 [App Scheduled Executor 02] INFO  o.c.common.settings.SettingsProvider - Settings saved to /home/abc/.config/Cryptomator/settings.json
11:01:19.874 [JavaFX Application Thread] INFO  org.purejava.KeepassProxyAccess - org.purejava.KeepassProxyAccessException: ErrorCode: 15, No logins found
11:01:19.875 [JavaFX Application Thread] INFO  o.p.i.keychain.KeePassXCAccess - No password found for vault -Ucq0zYwVtth
11:01:35.608 [App Background Thread 017] INFO  org.purejava.KeepassProxyAccess - org.purejava.KeepassProxyAccessException: ErrorCode: 15, No logins found
11:01:35.715 [App Background Thread 017] INFO  o.p.i.keychain.KeePassXCAccess - Password successfully stored for vault -Ucq0zYwVtth
11:01:35.717 [JavaFX Application Thread] INFO  o.c.ui.unlock.UnlockWorkflow - Unlock of 'somevault' succeeded.
11:02:56.325 [fuseMount-6-main] INFO  org.cryptomator.common.vaults.Vault - Unmounted vault 'somevault'
11:02:56.333 [JavaFX Application Thread] INFO  o.cryptomator.ui.lock.LockWorkflow - Lock of somevault succeeded.
11:02:57.418 [JavaFX Application Thread] INFO  org.purejava.KeepassProxyAccess - org.purejava.KeepassProxyAccessException: ErrorCode: 15, No logins found
11:02:57.418 [JavaFX Application Thread] INFO  o.p.i.keychain.KeePassXCAccess - No password found for vault -Ucq0zYwVtth
11:03:12.762 [JavaFX Application Thread] INFO  org.purejava.KeepassProxyAccess - org.purejava.KeepassProxyAccessException: ErrorCode: 15, No logins found
11:03:12.763 [JavaFX Application Thread] INFO  o.p.i.keychain.KeePassXCAccess - No password found for vault -Ucq0zYwVtth
11:03:22.963 [App Background Thread 020] INFO  org.purejava.KeepassProxyAccess - org.purejava.KeepassProxyAccessException: ErrorCode: 15, No logins found
11:03:23.067 [App Background Thread 020] INFO  o.p.i.keychain.KeePassXCAccess - Password successfully stored for vault -Ucq0zYwVtth
11:03:23.068 [JavaFX Application Thread] INFO  o.c.ui.unlock.UnlockWorkflow - Unlock of 'somevault' succeeded.
11:03:58.879 [fuseMount-7-main] INFO  org.cryptomator.common.vaults.Vault - Unmounted vault 'somevault'
11:03:58.889 [JavaFX Application Thread] INFO  o.cryptomator.ui.lock.LockWorkflow - Lock of somevault succeeded.

Anything else?
The new created record in KeepassXC is:

Having error in URL field
The tittle is empty.

Thanks for reporting this issue. I investigated it.
In your case Cryptomator obviously generated a vault ID stating with "-". The ID is generated randomly. This library saves the vault ID in the URL field of an entry in the KeePassXC database, as it can be seen in your screenshot, from where it can be retrieved.
When this library requests a vault password, KeePassXC searches the database for the URL it got within the request from the library and matches it with the URL field of the entries in the KeePassXC database.  I debugged the KeePassXC code and this is where it fails:
QUrl siteQUrl(siteUrl);

https://github.com/keepassxreboot/keepassxc/blob/56178f976a39ecba049fdadae2b051e533cba170/src/browser/BrowserService.cpp#L1080
This creates a QUrl object from the URL.
Doing this with an URL starting with "-" creates an empty object.

In the end, KeePassXC does not return a matched URL.
Unfortunately, there is nothing we can do about it, as the handling on the KeePassXC site for URLs is correct.
You already described the workaround for this case: altering the vault ID. This can be done directly in the Cryptomator settings file ~/.config/Cryptomator/settings.json.

Thanks for your quick investigation. It's true we can't do anything on KeepassXC or Cryptomator side.
Therefore, if possible, I would suggest to have some notifications in this case, so future users will know what to do. Maybe the quick one is having a message on the log file (Eg: "Please change your vault ID...").
It would be nice if there is a wiki for this issue also. 😀

Therefore, if possible, I would suggest to have some notifications in this case, so future users will know what to do. Maybe the quick one is having a message on the log file (Eg: "Please change your vault ID...").

I think this would be a bit overdone, as this should occur in rare cases.

It would be nice if there is a wiki for this issue also. 😀

That's a good idea. Done, see: Known-issues

authors: pttri purejava

repo: purejava/keepassxc-proxy-access


text:
shouldn't the index.js in examples use ./output/Main? or else live in dist dir

following the instructions in the README exactly leads you to a Parcel failure because examples/output is not one level above index.js...works fine if you edit the index.js so i guess either you meant to put examples/index.html and examples/index.js in the dist directory?

I was also caught by this error, which I now see is over a month old. Is this project being actively maintained?

@jamievicary Yes it is, I've just been a bit busy the past month.
@afcondon I may have broken the examples during a reorganisation. Do you mind submitting a PR that fixes the path? I'll put in a more permanent fix some time later if needed.

sure, i'll try to do it tomorrow morning, @ajnsit

@afcondon I've merged your fix. Thanks!

authors: afcondon ajnsit jamievicary


text:
Fixed typo

Hi, I'm new to satysfi. I'm looking for code highlighting package and finally installed this package.
Thus I found trivial typo in README.md. (because I'm new to satysfi, it may be valid in old satysfi)

thank you!


text:
Adding different type of alerts

I want add alert components which will be in different options and customisable too

Hey @purnima143  please assign this issue to me

please allow me the opportunity to work on this project