text:
Protect against spurious dist refreshes and also remove some old stuff from the ci script

There was a bad CI nightly job that errored out with:
[STDERR]/bin/bash: /usr/bin/time: No such file or directory
but resulted in a refresh of the dist directory that removed everything because errors weren't caught. This PR tries to fix it while removing some old stuff that was lying around.
Adding Chris: let us know if someone still uses vale-only CI on the vale branch.

I'm not using them at this point.

authors: msprotz parno

repo: project-everest/hacl-star


text:
Readonly cache

First step in the cache support. Fixes #53.

What you need is an on-event hook..(called "pre-processor" in BE) This is the place where you can load necessary tuples from the store. Also this needs to be integrated with the rule session api with a "Store" interface.
Incidentally I have a WIP branch that addresses the store interface and some more (like an interface to externalise join tables themselves and an in-memory implementation of those) Perhaps you can use that as the starting point for implementing your Solr/Redis store?

Take a look at the 'store' branch to start with.

@balamg Sure, will take a look.

After reviewing the WIP store branch, it would be best to merge the two branches first. The merge should include direct tuple integration with redis, TupleType based secondary index, multi store support, pre-processor(or startup) time tuple loading and tuple update propagation to clustered engines. Thus closing the PR.

source: gharchive/pull-request

repo: project-flogo/rules

license_type: permissive

license_source: github-api


text:
Construct values lazily

Lazy construction will work better with concolic execution because it defers path splitting to the point where a value is accessed.
This cannot be done for types like Option
But it can possibly be done for abstract Types like BTreeMap - possibly depending mutability?

Two directions to take this:

Rust's lazy statics potentially have the opposite problem: deferring construction of an object until after a path split - which requires every path to repeat the effort of creating the object for itself. Perhaps the initialize method would help with this?

Chopped symbolic execution adds lazy evaluation into KLEE and might be worth investigating.

source: gharchive/issue

repo: project-oak/rust-verification-tools

license_source: bigquery


text:
Should Events emitted by Anchor contain tx signature?

I can see a potential use case like pubsub topics when you want to commit a subscriber to process certain events. Should this instead be inferred after decoding the event via a topic field?

A tx signature would be useful information. If I recall correctly, this is not given by the web3.js subscription methods (though the RPC node does return it).

authors: armaniferrante whymidnight

repo: project-serum/anchor


text:
Upgradeable accounts

Accounts can have a version field (which is part of seed when creating associated accounts). Then, we can change the data of an account and there can be a method that will migrate data from the old to the new account, destroying the old one.
Suggested by @NorbertBodziony

We could potentially put the version number in the account header, next to the discriminant. So the layout is 8-byte-discriminant || version || borsh(account)

We will also need to force that no one will be able to create an old version of the account. Maybe allow for only one use of init/associated ?

@NorbertBodziony I believe no one will be able to create an old version of the account by virtue of the program's code being updated, since only the program can modify account data.

authors: NorbertBodziony armaniferrante


text:
[ISSUE-2] Corrected "source"/"dest" mix-up

"_source" and "_dest" were passed to CopyBuffer() in the wrong order, making the cache flush/invalidate operations useless to incorrect.

Well that's not embarrassing. Well spotted.


text:
[Feat]: report scheduler outstanding tasks as a metric

Is your feature request related to a problem? Please describe.
We want to know if some tasks are getting starved.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

Duplicate of #1870

authors: andaaron rchincha

repo: project-zot/zot


text:
Unity JsonRpc request bug

According to this, this takes only 1 argument, but you have 2.

https://github.com/project3fusion/StarkSharp/commit/bd1359e6a27334bae5fc5ac828ffc4e8f70bdf1e

https://github.com/project3fusion/StarkSharp/commit/bd1359e6a27334bae5fc5ac828ffc4e8f70bdf1e

authors: LastCeri jelilat

license: MIT


text:
Implement --squash for build-using-dockerfile and commit

Handle a Squash option when committing images, and make it available as a flag for buildah commit and buildah build-using-dockerfile.

Couple of minor Nits, but LGTM

LGTM

Fixed, added tests to exercise build-using-dockerfile and verify that a file removed in an intermediate layer is not in the final image.

LGTM assuming happy tests.

F27 RPM build test failing in RH CI.  We'd issues with this yesterday too, all unrelated to any Buildah changes.  Should we kill/ignore that test?
not ok 115 rpm-build Fedora 27

@rh-atomic-bot r+

authors: TomSweeneyRedHat nalind rhatdan

repo: projectatomic/buildah


text:
Correct version check for Docker > 1.7

This line would have failed as soon as Docker 2.0 was released. Also de-quoted for numeric comparison (keeps consistent with rest of file)

So docker will move to 2.0 instead of continuing with 1.11 ?
If that's the case, then above LGTM.

@cgwalters ping

:+1: from me.

authors: cgwalters delitescere rhvgoyal

repo: projectatomic/docker-storage-setup


text:
Add Pod restart

Moved contents of RestartWithTimeout to restartWithTimeout in container_internal to be able to call restart without locking in function.
Refactored startNode to be able to either start or restart a node.
Built pod Restart() with new startNode with refresh true.
Added podman pod restart with tests, man page and completions.

@rhatdan @umohnani8 @mheon PTAL

LGTM

bot, retest this please

@haircommander good work ... couple of simple clarifications in the man page are recommended.  one other thing, can you please begin to stub out the varlink side of the pod commands?  You do not need to make it work but something to indicate that there will be an API for it but it isn't implemented yet.  I'll be back soon if you want me to walk you through how to do that ... but stubbing things out does force us to think about how the funcs are designed including return types and input values.

@baude I was going to wait till you were back, I tried setting up varlink functions but I'm missing parts that make nothing work.

LGTM

@rh-atomic-bot r+

authors: baude haircommander mheon rhatdan

repo: projectatomic/libpod


text:
Copy resolv.conf into container

For DNS to work properly, we need to copy the host's /etc/resolv.conf
into the container during Init().  We do this by copying it into the
containers rundir and then bind mounting it into the container.
Signed-off-by: baude bbaude@redhat.com

Two nits, otherwise LGTM

I agree we need this for compatibility but long term I think we should default to delegating DNS to the host more directly by having the container talk via a private socket or whatever.  Would require something like annotating images as supporting the protocol.
(There are a massive number of bugs around docker's resolv.conf handling such as not tracking host changes, etc.)

@cgwalters I would love to see something like that.  Is there a socket we could leak into the container that  the resolver would use now?

LGTM. Should be good to merge once CI is working again

@rh-atomic-bot r+

@rh-atomic-bot r+

@rh-atomic-bot retry

@rh-atomic-bot r+

authors: baude cgwalters mheon rhatdan


text:
Make 'kpod create' also create the container in runc

Split off from #78 where the first commit was causing problems.

@baude PTAL
This was already reviewed under #78 so I think we can just merged if it passes tests

@rh-atomic-bot r+

@rh-atomic-bot retry

@rh-atomic-bot r+

@rh-atomic-bot retry

authors: baude mheon rhatdan


text:
SSL error on calico-policy when not using default domain

If K8S_API URL is not changed and your API certificates do not have 'kubernetes.default' SAN, calico-policy will fail (although it wont restart).
Out of this there are a few things to note:

calico-policy-controller is not 'health checked'
SSL could be disabled (or not)
Update documentation to note that K8S_API should be set to a proper value

Describe pod calico-policy-controller:
Conditions:   Type		Status   Initialized 	True   Ready 	True   PodScheduled 	True
Related config:
           # The location of the Kubernetes API.  Use the default Kubernetes             # service for API access.             - name: K8S_API               value: "https://kubernetes.default:443"             # Since we're running in the host namespace and might not have KubeDNS             # access, configure the container's /etc/hosts to resolve             # kubernetes.default to the correct service clusterIP.
Related error:
Traceback (most recent call last):
  File "<string>", line 295, in _manage_resource
  File "<string>", line 381, in _sync_resources
  File "<string>", line 433, in _api_get
  File "site-packages/requests/sessions.py", line 480, in get
  File "site-packages/requests/sessions.py", line 468, in request
  File "site-packages/requests/sessions.py", line 576, in send
  File "site-packages/requests/adapters.py", line 447, in send
SSLError: hostname 'kubernetes.default' doesn't match either of 'domain.used.in.ssl.cert'
2016-09-26 17:21:39,326 5 WARNING Re-starting watch on resource: NetworkPolicy```

Yes, this could certainly be documented better.  Basically, the policy controller uses a cert that is mounted into the Pod by the kubelet which expects kubernetes.default.
One option would be to document mounting of other API access certs into the container.
We could also add an option to disable SSL verification (which is done by default when the cert is present)

I managed to get it working by explicitly specifying a CA file
"k8s_certificate_authority": "/etc/kubernetes/ssl/ca.crt"

But yes, usually clusters are not signed with a 'known' CA.
Feel free to close/rename at will
Bests

calico-policy-controller is not 'health checked'

This is probably a separate issue.  I've raised this guy: https://github.com/projectcalico/k8s-policy/issues/44

authors: TaiSHiNet caseydavenport

repo: projectcalico/calico-containers


text:
calicoctl endpoint remove is documented but not implemented

As documented on how to stop a calico node it is advised to call calicoctl endpoint remove. This in fact results into the following.
core@xh3b4sd-k8svm-master ~ $ calicoctl endpoint remove
Usage:
  calicoctl endpoint show [--host=<HOSTNAME>] [--orchestrator=<ORCHESTRATOR_ID>]
    [--workload=<WORKLOAD_ID>] [--endpoint=<ENDPOINT_ID>] [--detailed]
  calicoctl endpoint <ENDPOINT_ID> profile (append|remove|set) [--host=<HOSTNAME>]
    [--orchestrator=<ORCHESTRATOR_ID>] [--workload=<WORKLOAD_ID>]  [<PROFILES>...]
  calicoctl endpoint <ENDPOINT_ID> profile show [--host=<HOSTNAME>]
    [--orchestrator=<ORCHESTRATOR_ID>] [--workload=<WORKLOAD_ID>]

I feel like I am doing something fundamentally wrong. Can somebody provide feedback here?

That might be a typo for calicoctl container remove.  Could you try it and let me know if the doc works modulo that substitution?  If so I can update the doc (or you could make a PR for it if you like).

I think it is a typo in the docs and calicoctl container remove does the trick.

This issue was moved to projectcalico/calico#68

authors: djosborne matthewdupre xh3b4sd


text:
felix/wireguard.go 578: Wireguard is not enabled

Log spammed with felix/wireguard.go 578: Wireguard is not enabled
Expected Behavior
Less frequent alerting to Wireguard not being enabled
Current Behavior
Log flooded with felix/wireguard.go 578: Wireguard is not enabled
Possible Solution

Steps to Reproduce (for bugs)

run calico v3.15.0 with default configs

Your Environment

v3.15.0
k3s 1.17.7
RHEL 7.8

This is an identical setup to the ones described here with the exception of FELIX_LOGSEVERITYSCREEN being unmodified

Looks like this log has been downgraded to "debug" in master, so future releases won't be so chatty. Thanks for raising.

authors: caseydavenport tomdoherty

repo: projectcalico/calico


text:
Update reqs-sys.md

Description

Added info about the requirement for disabling Firewalld

documentation enhancement

Related issues/PRs

adds info about the issue with networking when Firewalld is used as described in issue https://github.com/projectcalico/calico/issues/4382
Todos
Release Note

None required

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for the PR! Just a couple minor comments

OK, I'll change it.

One more minor thing I missed the first time... then good to go. Thanks for the PR!

Fixed.

authors: CLAassistant elcomtik


text:
Switch back to the upstream client-go

Description

k8s.io/client-go@v0.21.9 contains a backport of https://github.com/kubernetes/kubernetes/pull/107311 -> https://github.com/kubernetes/kubernetes/pull/107336.
This should allow us to switch back from the forked github.com/projectcalico/k8s-client-go to the upstream client-go (k8s.io/client-go).
The forked client-go was introduced with https://github.com/projectcalico/calico/pull/5324 and https://github.com/projectcalico/calico/pull/5351.
Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[x] Release note

Release Note

Kubernetes dependencies are updated from v0.21.8 to v0.21.9.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

/cc @fasaxc

/sem-approve

Thanks!

authors: CLAassistant fasaxc ialidzhikov


text:
change installation path to GITHUB_WORKSPACE

Closes #67.

Code wasn't built with this PR, for this reason this changes are not currently active if you use the version in main

@felipesaezreyes, I have made a new release. You can check it out at  https://github.com/projectdiscovery/nuclei-action/releases/tag/v2.0.0

authors: dogancanbakir felipesaezreyes

repo: projectdiscovery/nuclei-action


text:
Support for more than 299 items

When navigating to C:\home\site\wwwroot we only see the first 299 directories and files.
Expected: Could you please help us change the max file limit to 400?

I refer to this commit https://github.com/projectkudu/kudu/commit/719319a11cf4a75608914696482e7d20aff0b56d

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

repo: projectkudu/kudu


text:
Properly nest elements that don't have an apparent parent

This can happen when a element can contain a sequence of xs:any. One way to do this is to search the document for occurrences of the known parent, but requires parsing the doc, which we've been able to avoid so far.

False positives are possible with the current impl. Improve.

One option is to pass a mapping to VDX instead of interrogating the document, since the document can be wrong.

repo: projectodd/vdx


text:
🛑 Prokerala is down

In 35ce42b, Prokerala (https://www.prokerala.com) was down:

HTTP code: 503
Response time: 273 ms

Resolved: Prokerala is back up in 94fc9fe after 11 minutes.

repo: prokerala/uptime


text:
Chore/documentation

Added more documentation throughout the entire code base in order to tackle Issue #38.

👍

👍

authors: DannyVancura ThibaultKlein sagarnatekar

repo: prolificinteractive/Caishen

license: mit


text:
fix: fixes binding evaluation issue

if there are no bindings for a project the evaluation in PreSubstitutePlaceholders causes a NRE.
this fix just makes use of pattern matching which corrects the order of evaluation and gets around this issue.

Hi - Thanks for this
I actually noticed it myself while working on volume support, but this is cleaner and you added a test so i'm going to pull it into #145 directly and merge in


text:
Resolution causes email when an alert is removed from a group

What did you do?

Create an alert , use send_resolved: no
Add a second alert in the group
the two alerts are sent in the same mail
solve one of the alerts

What did you expect to see?

I should have received one mail with the original alerts

What did you see instead? Under which circumstances?

I received 2 mails:
one mail with two alerts
another mail with only the remaining alert

Environment

Alertmanager version:

alertmanager, version 0.16.0 (branch: HEAD, revision: 73bdd966e0055f3b828340ade3ef1f3a38169cdc)
build user:       root@fbea1f55d584
build date:       20190121-12:58:06
go version:       go1.11.4

To be clear, this was at the group_interval not the repeat_interval?

Yes

Okay this is not a bug. Actually the event occured twice in a short interval, and the second time only one alert was firing.

Sorry :)

authors: brian-brazil roidelapluie

repo: prometheus/alertmanager


text:
api/v2: Delete silence respond with 404 when silence is not found

When a client attempts to delete a non-existent silence, respond with 404 instead of 500.
This PR is a rebase of an old an open PR by @hateeyan and fixes the test failures.

Hi @simonpasquier good day. Can you review this PR when you get a chance? Thank you.


text:
Adds LTS blog post

The PR for prometheus#1163
CC: @juliusv

Thanks (a DCO signoff is missing)!
Some thoughts: The article introduction implies that the article reviews all LTS options that are currently available ("...at the time of writing..."). However, it only mentions 3 out of the 15 remote write options currently known to us (https://prometheus.io/docs/operating/integrations/#remote-endpoints-and-storage), plus the special case of Thanos. The actual choice of LTS implementations in the article seems to be rather guided by the LTS panel participants that you link to in the end.
I don't know - the current amount of information given about each of the examples is roughly the depth I would expect if the article aimed to review all known solutions, otherwise I would have expected an article that takes a few solutions, but describes them in some more depth. Otherwise it seems like just a slight, but partial elaboration of https://prometheus.io/docs/operating/integrations/#remote-endpoints-and-storage. Another option would be to compare-and-contrast the two fundamentally different approaches (pros+cons) of remote-write-based LTSes vs. Thanos.

@mhausenblas My apologies. Yeah, I hadn't followed #1163 so far, so this is just my own, completely independent first reaction. I'm happy to bow to other people's opinions.
Reading #1163, I don't see full consensus on content, depth, and location yet, so CC-ing @brian-brazil, @RichiH, and @brancz as the original issue commenters here.

Anyone?

Sorry, I have been travelling, matter of fact, I am also writing this from an airport.
I agree with @juliusv ; he put it better than I did in https://github.com/prometheus/docs/issues/1163#issuecomment-416263705 back when you first submitted this issue.

@RichiH you might have noticed that I closed the PR and issue. I've published it someplace else now so there's really no point in wasting even more time on it, content-wise.
Process-wise, concerning your point "the same, and longer, wait periods" … I appreciate that ye folks apply strict standards and proper consensus in the context of software artefacts since every line of code means a longterm commitment. In case of a blog post, however, I find this process of forcing committer-wide consensus ridiculous. With my Cloud Native Ambassador hat on: my intention with this and other related actions was to help the Prometheus project since we often receive the criticism that we focus too much on Kubernetes and neglect the many other CNCF projects we have. Seems this help is not appreciate or wanted, so I won't push it further.

I feel that your recurring references of our interactions with you wasting your time are unfair given the facts and timeline. I find them especially demotivating as your implication is that any time taken by jrv and me to interact in this context are a net-negative for you and/or the project.
As to the process, it is up to the contributor to take feedback into account or not. Your assumption of a need for team-wide consensus for blog posts is incorrect; rough consensus in IETF definition does state that all concerns need to be addressed, though. Choosing to close the PR short-circuits said process. This is obviously a valid choice to make, but this was not our choice.
Either way, I am happy you found a place for your blog post.

authors: RichiH juliusv mhausenblas

repo: prometheus/docs


text:
Test don't pass on OSX 10.10.5

--- FAIL: TestSelf (0.00s)
	proc_test.go:13: could not read /proc: stat /proc: no such file or directory
--- FAIL: TestFileDescriptors (0.00s)
	proc_test.go:102: could not read /proc: stat /proc: no such file or directory
--- FAIL: TestFileDescriptorTargets (0.00s)
	proc_test.go:149: could not read /proc: stat /proc: no such file or directory
FAIL
FAIL	github.comcast.com/vbo/derp-4/vendor/github.com/prometheus/procfs	0.013s

OSX/darwin does not have a procfs, that's why these tests fail. I guess the point can be made that this dependency is not strictly necessary for tests, so I removed it in #14.

authors: grobie hydroflame

repo: prometheus/procfs


text:
Compare label values of a single metric

Proposal
Use case. Why is this important?
Some exporters give important information in form of labels in a single metric.
For example, mysqld exporter has a metric
mysql_global_status_wsrep_cluster_info{"cluster-uuid":"1122", "local-uuid":"1122"}
If the cluster uuid is not equal to local uuid, an alert needs to be raised as all the nodes in the cluster needs to have the same cluster uuid.
I have not found any functionality regarding comparing labels of a single metric.

I don't think this is currently possible in prometheus. If you are using grafana though, you can realize this using variables.

Try something like this:
mysql_global_status_wsrep_cluster_info unless ignoring(dst) (label_replace(mysql_global_status_wsrep_cluster_info, "dst", "$1", "cluster-uuid", "(.)") == label_replace(mysql_global_status_wsrep_cluster_info, "dst", "$1", "local-uuid", "(.)"))

Hi @IldarMinaev, your answer was very useful. Thanks.
Now I need to create a chart from this result, something like this:
mysql_global_status_wsrep_cluster_info[1h:1d] unless ignoring(__dst__) (label_replace(mysql_global_status_wsrep_cluster_info, "__dst__", "$1", "cluster-uuid", "(.*)") == label_replace(mysql_global_status_wsrep_cluster_info, "__dst__", "$1", "local-uuid", "(.*)"))
But I'm getting this error: Error executing query: 1:1: parse error: binary expression must contain only scalar and instant vector types

Hello from the bug scrub.
Apologies for the delay in responding to this.
This is more of a usage question and so converting to a discussion.

authors: HardikSo IldarMinaev alexgreenbank erickalmeidaptc kaffarell

repo: prometheus/prometheus


text:
Prometheus frequently switch normal mode into rush mode

My premehteus v1.7.1 occurs some error in log, prompts that the promtheus server enter into The Rush Mode frequencely:
time="2017-12-08T04:04:37+08:00" level=warning msg="Storage has entered rushed mode." chunksToPersist=92489 memoryChunks=493796 source="storage.go:1867" urgencyScore=0.932
time="2017-12-08T04:05:03+08:00" level=info msg="Storage has left rushed mode." chunksToPersist=92439 memoryChunks=493196 source="storage.go:1857" urgencyScore=0.637
time="2017-12-08T04:05:10+08:00" level=warning msg="Storage has entered rushed mode." chunksToPersist=92413 memoryChunks=493327 source="storage.go:1867" urgencyScore=0.856
time="2017-12-08T04:05:27+08:00" level=info msg="Storage has left rushed mode." chunksToPersist=92473 memoryChunks=493225 source="storage.go:1857" urgencyScore=0.692
time="2017-12-08T04:05:49+08:00" level=warning msg="Storage has entered rushed mode." chunksToPersist=92633 memoryChunks=493890 source="storage.go:1867" urgencyScore=0.887
time="2017-12-08T04:06:03+08:00" level=info msg="Storage has left rushed mode." chunksToPersist=92509 memoryChunks=493240 source="storage.go:1857" urgencyScore=0.695
time="2017-12-08T04:06:15+08:00" level=warning msg="Storage has entered rushed mode." chunksToPersist=92421 memoryChunks=493468 source="storage.go:1867" urgencyScore=0.802
time="2017-12-08T04:07:04+08:00" level=info msg="Storage does not need throttling anymore." chunksToPersist=94037 memoryChunks=495819 source="storage.go:1015" urgencyScore=0.952
time="2017-12-08T04:08:08+08:00" level=error msg="Storage needs throttling. Scrapes and rule evaluations will be skipped." chunksToPersist=94052 memoryChunks=494618 source="storage.go:1007" urgencyScore=1

And there are also massive of hints of urgencyScore=1:
level=error msg="Storage needs throttling. Scrapes and rule evaluations will be skipped."
crapes and rule evaluations will be skipped." urgencyScore=1

In my opinion the prometheus_local_storage_persistence_urgency_ score should be between 0 < urgencyScore < 1, when it bigger than 0.8 promeheus will enter rush mode.
Due to this, It seems some data lose that make some break points:

Typically you would need to allocate more RAM to the Prometheus server to avoid this rush mode. Also it is better to ask such questions on the mailing list.

authors: Keleir simonpasquier


text:
"keep-alive" connections to consul

I just bumped into a situation where Prometheus v1.6.1 stopped receiving updates from Consul server.
This is probably due to a temporary networking failure between Prometheus and Consul.
netstat on Prometheus node shows ESTABLISHED connections to Consul.
netstat on Consul node shows no incoming connections from Prometheus.
I assume this is the consequence of using "blocking" api when you open a long-living connection to Consul and wait for changes to be pushed to you.
So it seems that Consul failed to push changes to Prometheus while network was down or maybe wait timeout exceeded. So he closed connection on his side, but that did not reach Prometheus.
On the other way, Prometheus still thinks everything is fine, since from his point of view "no changes" and "server dropped his end of connection" looks the same.
It would be nice to have an option to, maybe, periodically reconnect to consul server
P.S. I know that I am doing it wrong and should launch consul agent locally :-)

Sounds similar to: https://github.com/prometheus/prometheus/issues/3314


text:
/metrics does not respect --web.external-url configuration

Bug Report
What did you do?
I have configured --web.external-url=http://gajus.com/prometheus/.
What did you expect to see?
All Prometheus service endpoints to be prefixed with a path that is part of the --web.external-url.
What did you see instead? Under which circumstances?
The host is respected, but the path is not respected, i.e. Prometheus attempts to look for http://gajus.com/metrics instead of http://gajus.com/prometheus/metrics.
Environment

Prometheus version: v2.3.2
Prometheus configuration file:

https://github.com/helm/charts/tree/master/stable/prometheus +
alertmanager:
  persistentVolume:
    size: '32Gi'
server:
  baseURL: https://gajus.com/prometheus/
  prefixURL: /prometheus
storage:
  local:
    retention: '720h'

I have raised an issue with Helm charts too, just in case this is a configuration error.
https://github.com/helm/charts/issues/7088

Can you share your configuration file?
This setting configures the Prometheus http server, it has no effect on the scrape logic.

Can you share your configuration file?

Using the default configuration (https://github.com/helm/charts/blob/master/stable/prometheus/values.yaml) extended with the earlier mentioned configuration.

This setting configures the Prometheus http server, it has no effect on the scrape logic.

Point is that the http://gajus.com/prometheus/metrics endpoint exists and http://gajus.com/metrics does not. Since I have configured baseURL / prefixURL, I expect the checker to use the correct endpoint.
By the way, Prometheus does actually work as expected. I think it is just the liveness checker that is not aware of the prefix.

That sounds like an issue with the Helm chart, Prometheus is working as documented.

That sounds like an issue with the Helm chart, Prometheus is working as documented.

Which part of Prometheus is working as expected... ?

If by baseURL is https://gajus.com/prometheus/, then the above should query http://localhost:9090/prometheus/metrics or this assumption flawed?

Prometheus has no notion of baseURL, that's a Helm thing.

Prometheus has no notion of baseURL, that's a Helm thing.

--web.external-url, sorry.
https://github.com/helm/charts/blob/333bdfb086f70f4e8c3fe6f1c239418d6ff1e653/stable/prometheus/templates/server-deployment.yaml#L90-L92
Doesn't change the question.

Yes, Prometheus is working as expected. You told it to scrape /metrics so that's what it tried to do.

Yes, Prometheus is working as expected. You told it to scrape /metrics so that's what it tried to do.

Which part of configuration is that?

Which part of configuration is that?

I am not familiar with helm/charts at all, but if I were to guess, this is the place where another metrics path would have to be configured:
https://github.com/helm/charts/blob/4728544e0556cac4e52c70691f60c4ba31e36231/stable/prometheus/values.yaml#L789
No metrics_path is configured there, which means Prometheus takes the default of /metrics. This works as long as --web.external-url is not set. But as soon as it is modified, metrics_path would have to be adjusted (or rather: set at all) as well.
Relevant docs:
https://prometheus.io/docs/prometheus/latest/configuration/configuration/#<scrape_config>
So you are probably right that this is an issue, but Prometheus-wise there is little which can be done as it is a configuration issue. It has therefore be fixed in the configuration files, which seem to be managed by helm/charts in your case. Therefore, It might make sense to open an issue in the helm/charts repository (maybe referencing this one).

I got it working after setting the correct metric_path . Here are my configurations:
apache virtualhost
 <VirtualHost *:443>
                ServerName servername.org
                ProxyPreserveHost on
                ProxyPass /prom/ http://localhost:9090/prom/
                ProxyPassReverse /prom/ http://localhost:9090/prom/
                <Location /prom>
                    AuthType Basic
                    AuthName "Restricted Content"
                    AuthUserFile /etc/apache2/.htpasswd
                    Require valid-user
                </Location>
                SSLEngine on
                SSLCertificateFile    /etc/letsencrypt/live/servername.org/cert.pem
                SSLCertificateKeyFile /etc/letsencrypt/live/servername.org/privkey.pem
                SSLCertificateChainFile /etc/letsencrypt/live/servername.org/chain.pem
</VirtualHost>

prometheus.yml
global:
  scrape_interval:     10s
  evaluation_interval: 15s # Evaluate rules every 15 seconds. The default is every 1 minute.

scrape_configs:
  - job_name: 'prometheus'
    static_configs:
      - targets:
        - 'localhost:9090'
    metrics_path: '/prom/metrics/'

prometheus.service (systemd)
[Unit]
Description=Prometheus Server

[Service]
User=prometheus
Group=prometheus
Type=simple
ExecStart=/usr/local/bin/prometheus \
    --config.file=/etc/prometheus/prometheus.yml \
    --storage.tsdb.path=/var/lib/prometheus/ \
    --web.console.templates=/etc/prometheus/consoles \
    --web.console.libraries=/etc/prometheus/console_libraries \
    --web.external-url=https://servername.org/prom/
ExecReload=/bin/kill -HUP $MAINPID
KillMode=mixed
Restart=always

[Install]
WantedBy=multi-user.target

Now I can get the prometheus explorer at https://servername.org/prom/ (the tailing slash is important here)

authors: brian-brazil gajus geekodour hoffie


text:
kubernetes  Failed to list *v1.Endpoints: Get https://xxxx:6443/api/v1/endpoints?limit=500&resourceVersion=0: x509: certificate signed by unknown authority"

Bug Report
What did you do?
configuration in outside kubernetes cluster
- job_name: 'kubernetes-service-endpoints'

  kubernetes_sd_configs:
  - role: endpoints
    api_server: https://xxxx(outside cluster):6443
    tls_config:
      insecure_skip_verify: true
    bearer_token: xxxx
  relabel_configs:
  - action: labelmap
    regex: __meta_kubernetes_service_label_(.+)
  - source_labels: [__meta_kubernetes_namespace]
    action: replace
    target_label: kubernetes_namespace
  - source_labels: [__meta_kubernetes_service_name]
    action: replace
    target_label: kubernetes_name

What did you expect to see?
it can get entpoints info.
What did you see instead? Under which circumstances?
level=error ts=2018-09-29T12:31:02.230105551Z caller=main.go:234 component=k8s_client_runtime err="github.com/prometheus/prometheus/discovery/kubernetes/kubernetes.go:286: Failed to list *v1.Endpoints: Get https://xxxxxx:6443/api/v1/endpoints?limit=500&resourceVersion=0: x509: certificate signed by unknown authority"

Environment

System information:
Darwin 17.3.0 x86_64

Prometheus version:
prometheus, version 2.4.2 (branch: HEAD, revision: c305ffaa092e94e9d2dbbddf8226c4813b1190a0)
build user:       root@dcde2b74c858
build date:       20180921-07:27:12
go version:       go1.10.3

it work by
curl -k -H "Authorization: Bearer $(cat ../kubernetes/token)" 'https://xxx:6443/api/v1/endpoints?limit=500&resourceVersion=0'

I've tested on my local environment and it works fine with insecure_skip_verify: true. Can you paste the full configuration as displayed in the Prometheus UI (Status > Configuration menu)?

I was getting the same error even after mentioning insecure_skip_verify: true.
Though it worked for me in this way
kubernetes_sd_configs:
- api_server: https://<ip>:6443
  role: node
  bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token
  tls_config:
    insecure_skip_verify: true

By specifying inseucre_skip_verfity as a part of api_server context

Closing due to inactivity.

I'm getting this error too, the certificate and the token work fine with curl and other tools, but prometheus is having this error
kubernetes Failed to list *v1.Endpoints: Get https://xxxx:443/api/v1/endpoints?limit=500&resourceVersion=0: x509: certificate signed by unknown authority"


text:
Document exemplars

The exemplars feature is under-documented.
I would appreciate documentation in the release-2.26 branch, notably how to enable them (add to the disable feature page).
cc @cstyan

It's documented in the enable-feature flag but I can add it to that docs page as well.

We made the feature flag a lot shorter unfortunately because it was unreadable, and it points to the disabled features page.Sorry about that, I did not realize it was not documented on the page.

authors: cstyan roidelapluie


text:
sd: change hetzner role type and constants to be exportable

This PR changes hetzner's service discovery Role to be exportable. The same for HetznerRoleRobot and HetznerRoleHcloud constants. This is needed when doing conversions from a config format to internal prometheus config, like what we are doing here.

Thanks

Thanks for the fast review @roidelapluie !

authors: marctc roidelapluie


text:
refactor: reuse the slice to optimize

ref: prometheus/tsdb#676
@bwplotka @krasi-georgiev
Signed-off-by: YaoZengzeng yaozengzeng@zju.edu.cn

@krasi-georgiev Also optimize seriesHashmap.del() with same way :)

@bwplotka @krasi-georgiev
After reading the code more comprehensively, I think the slice of MemPostings.Delete() should not be reused.
Because MemPostings.Get(name, value) will return the Postings for querying whose underlying slice share same memory with MemPostings.m[name][value].
If we reuse the slice in deleting, the Postings may return duplicate series ref.
seriesHashmap.del() and baseChunkSeries.Next()  could reuse the slice safely.

@krasi-georgiev @bwplotka @csmarchbanks
It's proved that reuse the slice for memPostings.Delete() is not correct and the code change has been rollbacked.
But seriesHashmap.del() and baseChunkSeries.Next() could reuse the slice safely.
PTAL.

@YaoZengzeng thanks,
I just run the BenchmarkQueries and it didn't show any difference in the allocs and total bytes.
Could you check if we have another func that shows the improvment or write one to see what are the real gains by this change.

@krasi-georgiev Maybe the referenced functions are not called frequently, so the optimization is not obvious. But reusing the slice that way is appropriate and more efficient in theory, right? :)

yep 100% correct, but sometime the theory is not what we see in practice.
It should be simple enough to write some benchmark that shows the difference and it should be useful for future tests.
Would you have the time to write it?
If yes please use only public API interfaces as these are less likely to change.

Yes, I'd like to research it in more depth :)

Thanks, Appreciated. waiting for the results.

@YaoZengzeng any progress on this?

ping @YaoZengzeng

@krasi-georgiev Sorry for the delay, but really busy these days. :joy:
I'll move on once I have time :)

@YaoZengzeng are you still busy? any chance to look into this anytime soon?

In the bug scrub, we decided to close this for lack of activity. If somebody wants to pick this up, we'll appreciate it. Next step, as discussed above, would be to verify the improvement with a benchmark.

authors: YaoZengzeng beorn7 krasi-georgiev


text:
cut 0.10.0

This release brings some good allocation improvements in queries and compaction.

Sticking these benchmark results here http://prombench.prometheus.io/grafana/d/7gmLoNDmz/prombench?orgId=1&var-RuleGroup=All&var-pr-number=5765&from=1563170890686&to=1563213975521

repo: prometheus/tsdb


text:
exception in phase 'canonicalization' in source unit ... errors

I am using groovy-language-server with emacs and lsp-mode with javac 11.0.9.1. I am seeing the following error
BUG! exception in phase 'canonicalization' in source unit '/home/vspinu/.../xyz.groovy' ClassNode#getTypeClass for groovy_scripts_utils.utils.test_util.ApplicantModifierTest is called before the type class is set
	at org.codehaus.groovy.ast.ClassNode.getTypeClass(ClassNode.java:1387)
	at org.codehaus.groovy.ast.ClassNode.getTypeClass(ClassNode.java:1381)
	at org.codehaus.groovy.transform.trait.Traits.findHelpers(Traits.java:149)
	at org.codehaus.groovy.transform.trait.TraitComposer.doExtendTraits(TraitComposer.java:110)
	at org.codehaus.groovy.control.CompilationUnit$5.call(CompilationUnit.java:235)
	at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1084)
	at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:640)
	at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:618)
	at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:595)
	at net.prominic.groovyls.GroovyServices.compile(GroovyServices.java:448)
	at net.prominic.groovyls.GroovyServices.compileAndVisitAST(GroovyServices.java:431)
	at net.prominic.groovyls.GroovyServices.didOpen(GroovyServices.java:138)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.eclipse.lsp4j.jsonrpc.services.GenericEndpoint.lambda$null$0(GenericEndpoint.java:65)
	at org.eclipse.lsp4j.jsonrpc.services.GenericEndpoint.notify(GenericEndpoint.java:152)
	at org.eclipse.lsp4j.jsonrpc.RemoteEndpoint.handleNotification(RemoteEndpoint.java:220)
	at org.eclipse.lsp4j.jsonrpc.RemoteEndpoint.consume(RemoteEndpoint.java:187)
	at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.handleMessage(StreamMessageProducer.java:194)
	at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.listen(StreamMessageProducer.java:94)
	at org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor.run(ConcurrentMessageProcessor.java:113)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:834)
Unexpected exception in language server when compiling Groovy.

The project is rather big and I am not a groovy programmer. I see rather long delays and frequent hangs. I presume it has to do with this error.

Do you think that you can try to strip it down to a small class or single file? It looks like the error is happening around this code: groovy_scripts_utils.utils.test_util.ApplicantModifierTest, but there's not much I can suggest beyond that.

I will try to isolate tomorrow, but my expertize is pretty limited. Unfortunately it's a private repo.

I have the same issue in https://github.com/dansomething/coc-groovy/issues/20 which uses this repository.
This has been fixed in newer groovy versions, but I'm stuck on grails 3 and can't really upgrade 😢

authors: aminroosta joshtynjala vspinu

repo: prominic/groovy-language-server


text:
password not placed in generated propel.php configuration

When using propel init to create an initial propel.php configuration file, the password that the user input via command line prompt is not included in the php configuration file.  However, it is included correctly in the propel.yml configuration file if that is chosen instead

Thanks for the report :) Could you check if https://github.com/propelorm/Propel2/pull/1140 fixes this?

@mpscholten That fixed it.  Thanks!

authors: benbankes mpscholten


text:
🛑 fips.filecoin.io is down

In 50247e9, fips.filecoin.io (https://fips.filecoin.io) was down:

HTTP code: 0
Response time: 0 ms

Resolved: fips.filecoin.io is back up in e12ec3b after 11 minutes.

repo: protocol/upptime-pln


text:
🛑 nftschool.dev is down

In 1d04dc8, nftschool.dev (https://nftschool.dev) was down:

HTTP code: 0
Response time: 0 ms

Resolved: nftschool.dev is back up in 97c0077 after 6 minutes.


text:
Add Environmental Data Science book

Environmental Data Science book

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

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

@acocac Thank you for your contribution. This is truly an epic project that your community has created here.
I was already familiar with this project, but a long time ago we decided to move the very good courses and tutorials to the Education section of this project, where Environmental Data Science book is already listed, which is unfortunately a different list. We did this to make it easier for newcomers to find entry-level projects among the hundreds of expert-level open source projects. For various reasons, we are considering moving the education projects to the main list, but this has not yet happened. One reason is that I have noticed that people simply overlook the education section.
It would be great to get your feedback on this. Does it make sense to create a "sustainable education" section, or "education for sustainable development" as the UN calls it, under sustainable development with all the projects from the education list? @andrew @RichardLitt @joshhopkins

This is truly a great resource. However, at the risk of becoming noisy, I think educational resources should remain seperate from tooling.

I don't see a reason not to have a longer Markdown list with an education section. I don't know how many eyes are on the education.md file.

@Ly0n apologies, it was my bad that I didn't double check the education section. I suggest increasing the awareness of the education resources by including them in the Climate Triage. There's a great opportunity to promote all educational resources that are complementary to the curated list of tools. Indeed, I added the EDS book because it wasn't listed in the Triage.
I think the Education for Sustainable Development makes sense. I am a topic editor for JOSE, and there are other great examples of educational resources for environmental sustainability (see for example 1.
@joshhopkins can you expand what do you mean by noisy? Please be aware some educational resources such as Project Pythia and EDS book have a strong investment in the community and maximise open source infrastructure to increase the visibility of open research (data, software, pipelines) in environmental sustainability. Project Pythia has solid developments for scheduling and testing the health of their foundational materials and cookbooks.

@acocac I definitely appreciate your view on this. I mean potentially noisey, in that educational resources are so vast, that without applying normative judgments there is a risk of diluting this directory. Of course, there is often overlap between documentation and tooling, but in general, I think there should be some separation between the two with a slightly different acceptance criteria.

@acocac I definitely appreciate your view on this. I mean potentially noisey, in that educational resources are so vast, that without applying normative judgments there is a risk of diluting this directory. Of course, there is often overlap between documentation and tooling, but in general, I think there should be some separation between the two with a slightly different acceptance criteria.

@joshhopkins thanks for elaborating your points on this. There's then a clear opportunity for a dedicated initiative tracking progress and foster collaboration on educational-focused open source resources in environmental sustainability.
👏 The climate triage is an amazing portal, I hope others can extend it to other domains!

We have to decide at the next community meeting how to deal with the educational area. Until then, I don't see a problem with including these projects on both lists. So it will also appear on ClimateTriage.

Just a small side note. This was repo #2000 we listed based on ecosyste.ms data.. :partying_face: :balloon: :rocket:

authors: Ly0n RichardLitt acocac joshhopkins

repo: protontypes/open-sustainable-technology


text:
Add grist funding table

This PR extends the existing grist tables Projects and Organizations with a Funding one. The new Funding table will then be accessible on openclimate.fund (repo: https://github.com/protontypes/open-climate-fund) for users to look which project they would like to sponsor.
The Funding table is basically a filtered Projects table based on if they contain a funding link. For now i added the columns project_names, description, git_url, category, stars, and obviously the funding_links. Open to any suggestions about changes. The chosen set seems appropriate to me as it provides some background to the project without overwhelming the user.
I tested the script on my grist. The result can be seen here: https://docs.getgrist.com/eBTy4nHT95K6/test
Related Issue: #527

Thanks @lappemic. Look great! Could you please make your test grist public so that we could see it?
At the moment I can only see one larger tweak:  The requirements.txt is not needed and contains dependencies not used by the ecosystems_to_grist.py
I will test the script tomorrow morning on my local machine.

Try the open grist here https://docs.getgrist.com/eBTy4nHT95K6/test?utm_id=share-doc


text:
what credentials are required for sso?

I get this error, I run it with these parameters
sudo docker run -p 8080:8080 -e AUTH_TYPE=OAUTH2 -e SPRING_SECURITY_OAUTH2_CLIENT_REGISTRATION_AUTH0_CLIENTID=kafka -e SPRING_SECURITY_OAUTH2_CLIENT_REGISTRATION_AUTH0_CLIENTSECRET=***** -e SPRING_SECURITY_OAUTH2_CLIENT_PROVIDER_AUTH0_ISSUER_URI=https://*/auth/realms/* -e SPRING_SECURITY_OAUTH2_CLIENT_REGISTRATION_AUTH0_SCOPE=openid -d  -e KAFKA_CLUSTERS_0_NAME=stage -e KAFKA_CLUSTERS_0_BOOTSTRAPSERVERS=kafka:9092 provectuslabs/kafka-ui:latest

my mistake in client secret

repo: provectus/kafka-ui


text:
Epic: Metadata and wasm

Summary
This is an epic to track issues related to updates to the x/metadata module in order to make it easier to use, and useable with wasm. The end goal is to make it easier to for smart contracts to use the x/metadata module.
Issues

[x] #1279
[x] #1280
[x] #1381
[x] #1437
[x] #1438
[ ] #1439
[x] #1443

For Admin Use

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

Since there's only one issue left in this, I'm going to go ahead and close it.

repo: provenance-io/provenance


text:
Wait-RSJob doesn't output RSJob when completed

Similar to Wait-Job, Wait-RSJob should output a RSJob object if the jobs have completed. If the timeout parameter is used, nothing should output if the timeout has been reached.

Updated Wait-RSJob to output RSJob object.

repo: proxb/PoshRSJob


text:
下载速度很慢（不管文件大小）

问题描述(必要)
最近2天下载速度很慢，平均只有20KB/s
版本号(必要)
2.54
操作系统(必要)
Windows10 1803
相关截图

相关日志
2018-08-25  16:52:57.086 [nioEventLoopGroup-7-1] ERROR lee.study.down.handle.HttpDownInitializer - down onChunkError:
java.io.IOException: 远程主机强迫关闭了一个现有的连接。
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
at sun.nio.ch.IOUtil.read(IOUtil.java:192)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
at io.netty.buffer.PooledUnsafeDirectByteBuf.setBytes(PooledUnsafeDirectByteBuf.java:288)
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1106)
at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:373)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:123)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:645)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:580)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:497)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:459)
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:138)
at java.lang.Thread.run(Thread.java:748)
2018-08-25  16:53:44.151 [nioEventLoopGroup-7-1] ERROR lee.study.down.handle.HttpDownInitializer - down onChunkError:
java.io.IOException: 远程主机强迫关闭了一个现有的连接。
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
at sun.nio.ch.IOUtil.read(IOUtil.java:192)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
at io.netty.buffer.PooledUnsafeDirectByteBuf.setBytes(PooledUnsafeDirectByteBuf.java:288)
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1106)
at io.netty.buffer.WrappedByteBuf.writeBytes(WrappedByteBuf.java:813)
at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:373)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:123)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:645)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:580)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:497)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:459)
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:138)
at java.lang.Thread.run(Thread.java:748)

不少朋友也是一样的问题，限速很严重，百度这又折腾呢-就是吃相太难看

我今天也是很慢,几十 一百k, 还以为自己网有问题呢

没速度了+1...
百度云又在搞事情

下载好慢了，5Kb，百度云又在搞事情

同没速度……大部分连接都是0B/s，其他的是10K/s左右

百度真是毒

nj02cm01

不是软件问题，黑号了

@Blackcf @dabi3ng @hy345 @Eisx11o @operammm @zhezh 可以尝试使用代理进行下载，速度会快很多

真的6 从台湾或者从美国绕一圈回来,速度倒是快...

@TrustTheBoy 哇真的 谢谢大佬

这百毒就是只限速大陆，现在就是基于aria2的还能有速度！

我这几天也是这样。。换了个百度盘账号就恢复了。。可能之前号被黑了。

我这下载挺快的，感觉没什么影响，我用的2.54版本

试试3.0版本

repo: proxyee-down-org/proxyee-down


text:
Bugfix/windows 10 firewall service

Fixed: Assert-FirewallConfigurable fails on Windows 10 due to firewall service name change.
Fixed: ReparsePointTestFixture test was broken due to using TEMP environment variable which contains a shortened tilde path.

@splatteredbits Requested changes made.

Build failed due to exceeding maximum execution time (60min). The last successful build came in just under at 57min.

Build is now green, ready for merge.

repo: pshdo/Carbon


text:
Attempt to automatically verify DOI for incoming publications

Publications entering the new open access workflow will already have metadata that was imported from Activity Insight. Sometimes this metadata will include a DOI that was entered into Activity Insight by the faculty member, and sometimes not. In any case, RMD won't be able to simply trust that a provided DOI is the correct one for the given publication since no validation or verification of the DOI would have been done prior to this point.
It's very important for the rest of the workflow that we obtain and verify a DOI for a publication if at all possible since having a correct DOI will allow the automation of subsequent steps and also facilitate any subsequent manual work that needs to be done by an RMD admin for the given publication.
The oats utilities already include a command for verifying the DOI of a publication by querying Crossref using the given DOI and then comparing the returned title to the given title for the publication (from the Activity Insight metadata). Ideally, we would reimplement this utility in Ruby and integrate it directly into RMD so that:

It can be easily invoked and run on incoming publications in the new OA workflow
It can be easily updated/maintained by the PSU Libraries development team

Additionally, RMD will need to be able to track the results of this DOI verification which will probably mean storing a new boolean flag somewhere.
Here's how I picture this possibly working:

When a new publication with an associated file is imported from Activity Insight or when an existing Activity Insight publication import is updated with a new file location, a background job will be queued up to do DOI verification only if a DOI was provided.
The background job will call a process that uses the same logic that is currently implemented in oats to verify the DOI with Crossref.
If the DOI is successfully verified via Crossref, then we'll set a flag indicating that the DOI has been verified. This flag will indicate that the publication needs no manual intervention for the DOI verification step in the workflow. In a subsequent issue, a successful result here could also queue up another kind of background job to attempt to automatically perform the next step in the workflow.
If the DOI is not verified via Crossref because the titles do not match sufficiently, then we'll set the verification flag to be false. This will be the indicator that the publication needs to be queued up in a list for manual review by an RMD admin.
If DOI verification fails for any reason, (i.e. Crossref API is temporarily down), then it should retry until verification is performed successfully.
For publications where no DOI was imported from Activity Insight, the DOI verification flag will remain null.

Questions:

What if RMD already has a DOI for the incoming publication from another source (like Pure)? This may be the case for publications that were imported previously, merged with duplicate Pure metadata, and then had a file uploaded in Activity Insight later. Do we simply trust the DOI from Pure in these cases and skip the verification process? Or should we go ahead and try to verify the DOI via Crossref anyway?

If we have no DOI, would it be helpful to try to find one with a title query to Unpaywall or Open Access Button?

authors: EricDurante ajkiessl

repo: psu-libraries/researcher-metadata


text:
MTV入站时间识别不准确

PT 助手版本: © 栽培者 2023, 版本 v1.6.1.2056 zip
PT 助手安装方式：zip包安装
浏览器名称及版本：Chrome 版本 110.0.5481.177（正式版本） (x86_64)
浏览器是否安装了其他插件：是
停用其他插件后是否正常工作：否
问题描述：

如图所示 这个入站时间不对
（搞得我都不敢PTPP截图了 一截图显示P龄23年。。。）

相关截图：

重现步骤：

我这里没有问题，你用界面是什么语言？

mtv的界面吗？就是英语

相关截图：
重现步骤：

我这里无法重现，显示是正确的。试试清理一下缓存。

authors: LoneFireBlossom fzlins

repo: pt-plugins/PT-Plugin-Plus


text:
🛑 广电VRBT is down

In db96ff3, 广电VRBT (https://vrbt.10099.com.cn/#/home) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 广电VRBT is back up in bd12d0f after 9 minutes.


text:
Studios need some way to know something went wrong

Right now all of this info is in Sidekiq. Ideas?

We could do something similar to what we do with Browse Everything ingests - keep track of things in the database and have the jobs update it.

authors: jpstroop tpendragon

repo: pulibrary/plum


text:
Hide long values behind "More..." link

Truncate long values with a link to reveal the rest of the value.  This will make metadata display better by not having long values hide other fields below.

https://dpul.princeton.edu/catalog/k930bx11x#?c=0&m=0&s=0&cv=0&xywh=-9703%2C-401%2C24996%2C8000

authors: christinach escowles

repo: pulibrary/pomegranate


text:
Building the hardware use command  "make bin/snitch_cluster.vlt" has error

To compile the hardware for simulation,run one of the following commands:
make bin/snitch_cluster.vlt
but has below error：
    import hjson
ModuleNotFoundError: No module named 'hjson'

Forgot this command：
docker run -it -v   $REPO_TOP:/repo     -w /repo ghcr.io/pulp-platform/snitch_cluster:main


text:
Add a tip-type callout to the notes shortcode

We have info-style notes and warnings, but it'd be nice to have tips, too, like for things like this, which are meant to be read more as "try this" than "bear in mind":

We should probably also rename the shortcode from notes to something more generic. Leanpub uses an expression called {blurb} for this that takes a class, like tip or info, and it works pretty well.

Implemented in #13335 with a slightly different style than described here.

authors: cnunciato thoward

repo: pulumi/docs


text:
Replace CDK random suffix with Pulumi random suffix

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

CDK automatically adds a random suffix to the resource logicalId to make the name that is eventually generated by CFN unique. We use the LogicalId as the Pulumi resource Id and then autonaming will add it's on random suffix so we end up with two random suffixes which does not look great. For example, we might end up with a role name like testapimyapiCloudWatchRoleA84BAE8E-120b18f
The cdk.Stack class has a protected property allocateLogicalId which is responsible for creating this LogicalId. We should override this method to having our own naming logic.
Affected area/feature

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

repo: pulumi/pulumi-cdk


text:
Career page - Fix EE indentation

Fix Electrical Engineering section indentation
I think the problem should be from the electrical_engineer.md file (thought i'd already fixed this in the previous PR)

https://github.com/nathakits/pupil-labs-website/commit/423a1f9ff24b55474973d51dc57d20ad029af522
The PR is already merged but don't know why it's not working.

Doesn't work in both desktop and mobile - only my localhost works...

https://github.com/pupil-labs/pupil-labs-website/pull/93 - made a new PR to fix this issue

It is a nested list. The indentation is intentional -- it was reverted from your previous PR. Please look through commit messages.

authors: nathakits willpatera

repo: pupil-labs/pupil-labs-website


text:
Set java_home directory

Default it will look to the environment settings JAVA_HOME.
We install java by just unpacking a packages in a directory.
So it would be nice if this can be set optionally.

lgtm

authors: BobVanB nibalizer

repo: puppet-community/puppet-rundeck


text:
Initial port of puppet dasboard radiator view

Ported the puppet dashboard radiator view to puppetboard. This is a simple but useful heads up display of the last run status of all nodes a master knows about.

I really like the addition of this feature.  I cobbled something together to use in for a "radiator" for sorts and was hoping someone would do a better job of it.
Playing devil's advocate on the color a bit (I know it can be argued either way)....  My current company is a Puppet Enterprise customer and we also use Puppetboard for an unauthenticated read-only view.
In Puppet Enterprise Console (like Puppet Dashboard) we grew accustomed to the "changed" being blue and the "unchanged" being green.  The thinking behind this is that "unchanged" means everything is as it should be.  "changed" means something has happened  and hopefully it was intentional.
In translating this to a monitoring/alerting system (nagios oriented) I would return an "ok/green" if nothing has changed, a "warning/yellow" if something has changed or a noop run wants to apply changes , and a "critical/red" if something fails.  Other states are "unknown/orange".
We also make use of noop in production in some cases.  It is useful for us to know how much of our infrastructure is actually in noop and is in noop and wants to apply changes.  Not really the "puppet way" of doing things, but it's how we've had to implement a few configurations.  If there is accounting for noop that would be awesome in our case.

What about extending this to the config so users can pick their colors? I would like this feature more than any one color scheme.

I have actually changed jobs and am no longer using puppetboard, so I'm not the best person to further develop this. As far as I can tell, this contribution has never been merged upstream. If someone would be so kind as to do that, someone else could take over making the requested changes (or not). Either way, I'm no longer the appropriate person to take care of this.

@ardichoke do you mean the radiator never made it into puppet-dashboard?

I believe he means this pull request never made it into the main branch.
I have changed jobs as well, but am still using Puppetboard.  I am standing up new puppet server and puppetdb now.  I implemented a radiator and am planning on switching to the implementation in this commit instead.  I'll see about adding the configuration variables for color and update the merge request.

@johnzimm is correct. I'm sorry if that was not clear from my comment.

@nibalizer, any plans about merging this feature ?

@mvisonneau there was talk of making the colors configurable, which I would greatly prefer. If no one is willing to do this work up-front though, I suppose this can land as is. I'll let this comment sit for a few days and if no one steps forward we can merge.

There's a few things that don't super-excite me about this change but not strongly enough to block any of it:

Configurable colours (as noted by @nibalizer)
Not a fan of the <meta content='150' http-equiv='refresh' />, I'm pretty sure this can be done more elegantly and less invasively by having /radiator return JSON instead and then rendering that with some JS that just updates the HTML
The amount of CSS, especially the super-specific CSS selectors which are needlessly specific and slow down rendering. For example the body.radiator_controller table.node_summary tr.unchanged .percent can be changed to tr.unchanged .percent and achieve the same thing (most of the body.'s are pointless too as are the table.node_summary since almost everything is contained within them).

I agree the code is less than ideal (side effect of forking code from the Puppet team and integrating it into another project, as well as my own lack of experience in web development, I suppose), but I don't have a puppetboard install to be able to further work on this any more. This either needs to be rejected, or moved upstream and out of my repo, as I am not currently able to do any further work on this and do not believe I will be in a position to do so for the foreseeable future. It would be pointless for people to submit changes to my fork, as I have no means of testing them anyway.

http://imgur.com/hZGImPY Is what it looks like right now.

I hate to keep bumping this, but this pull request has been open for over a year at this point. I rebased this commit on the latest version of master. Once again, I don't have an environment available to test, but it doesn't look like anything has changed that would cause this to break. Could someone review it and either pull it in or reject it?  Either way, I'd like to get this wrapped up, as I do not like things lingering about indefinitely.

In app.py I can see 2 routes for /radiator and the same function code broken up in 2 places. Can you please clean that up?

I think it might be worth redoing this PR. The history is going to be a mess now on account of us not merging this sooner.

I cleaned up app.py.
If you're going to redo it, then grab a copy of the files and reject the pull request please. I just want this closed out, one way or another.

To keep the commit history clean the code in this PR will have to be redone in a new PR.

authors: ardichoke corey-hammerton daenney johnzimm mvisonneau nibalizer

repo: puppet-community/puppetboard


text:
Blank screenshot with headless true, else fine.

Puppeteer version: 0.1.13
Platform / OS version: Ubuntu 17.04
URLs (if applicable): http://eu.patagonia.com/gb/en/home/
Node.js version: 9.2.0

When running the following:
const puppeteer = require('puppeteer');

(async () => {
  const browser = await puppeteer.launch({headless: true});
  const page = await browser.newPage();
  let source = await page.goto('http://eu.patagonia.com/gb/en/home/');
  await page.screenshot({path: 'example.png', fullPage: false});
  await browser.close();
})();

The resulting screenshot is blank, however by setting headless to false the screenshot works perfectly.
I don't know if it is a site specific thing but I haven't seen it on any other site, but AFAIK it shouldn't make a difference if headless if true or false.

Same here v1.1.0

Something is up with the site. I'm not able to curl -v http://eu.patagonia.com/gb/en/home/ and get a response.

@ebidel That is weird- somehow it loads find in a normal browser window.

Any solution for this?

i always get blank screenshot if isMobile is true. i have tried all possible values of waitUntil page.goto(url, {waitUntil: ''} but it did not help. only option worked for me is sloMo.
puppeteer.launch({"slowMo" : 500});  but the value of slowMo is not predictable. sometime/some site will give non black screenshot even it is 250.
is there any proper fix for it?
i use puppeteer@1.8.0

@aha7 can you please file a separate issue with reproducible script?

Up, did anyone find a solution ? (same pb with an other site using spip)

Up, did anyone find a solution ? (same pb with an other site using spip)
Edit: found a solution
      await page.setUserAgent('Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3738.0 Safari/537.36');

resolve pb
#665

Saved my day

authors: IneoO aha7 ashwinsingh2007 aslushnikov digitalhank ebidel eliseumds grantstephens

repo: puppeteer/puppeteer


text:
feat: add experimental browser.debugInfo

This is an experimental method that provides debugging information to help debug issues with Puppeteer.
Currently, it only provides the stacktraces for pending protocol calls.
Note: the test failure is unrelated and tracked in https://github.com/puppeteer/puppeteer/issues/11749 It's revealed by the change in sharding caused by introduction of a new spec.

We miss adding this to the website, can you file an issue or PR for that?


text:
(PUP-10527) Test puppet service runs puppet

This commit adds an acceptance test to ensure that starting the puppet
service on agents runs puppet.  This validation was missing from the
puppet_service_management.rb test.  Due to the comprehensive nature of
the existing test, this test is added independently to reduce execution
time.  The existing test takes about 4m to execute while this specific
case takes about 30s.

This test has been locally validated on el-7 and windows-2012 to:

Fail on puppet agent f7013c2 which contains puppet with this commit triggering the issue documented in PUP-10527.
Pass on puppet agent 6.16.0 with contains puppet with this commit to fix the issue.

I am not sure what is going on with the windows spec test failure in appveyor. :shrug:

CLA signed by all contributors.

For me this fails if the agent didn't run before on the target machine, since the last_run_report file was never there. We should also take this into account.
Maybe an easier way would be to remove the file when starting the test, and after the puppet run to check if it's present. Then we wouldn't need to compare times and whatnot.
Failing output:
Begin tests/resource/service/puppet_service_runs_puppet.rb

Starting the puppet service should successfully run puppet

  * Ensure stop puppet service

    playable-girth.delivery.puppetlabs.net (playable-girth.delivery.puppetlabs.net) 17:31:50$ cmd.exe /c puppet resource service puppet ensure=stopped
      Warning: Skipping ip method to ssh to host as its value is not set. Refer to https://github.com/puppetlabs/beaker/tree/master/docs/how_to/ssh_connection_preference.md to remove this warning
      Attempting ssh connection to playable-girth.delivery.puppetlabs.net, user: Administrator, opts: {:config=>false, :verify_host_key=>false, :auth_methods=>["publickey"], :port=>22, :forward_agent=>true, :keys=>["id_rsa_acceptance", "~/.ssh/id_rsa-acceptance"], :user_known_hosts_file=>"/home/gabi/.ssh/known_hosts", :keepalive=>true}
verify_host_key: false is deprecated, use :never
      service { 'puppet':
        ensure   => 'stopped',
        provider => 'windows',
      }

    playable-girth.delivery.puppetlabs.net (playable-girth.delivery.puppetlabs.net) executed in 5.72 seconds

    playable-girth.delivery.puppetlabs.net (playable-girth.delivery.puppetlabs.net) 17:31:55$ cmd.exe /c puppet resource service puppet
      service { 'puppet':
        ensure   => 'stopped',
        enable   => 'manual',
        provider => 'windows',
      }

    playable-girth.delivery.puppetlabs.net (playable-girth.delivery.puppetlabs.net) executed in 3.13 seconds

  playable-girth.delivery.puppetlabs.net (playable-girth.delivery.puppetlabs.net) 17:31:58$ cmd.exe /c puppet config print statedir
    C:/ProgramData/PuppetLabs/puppet/cache/state

  playable-girth.delivery.puppetlabs.net (playable-girth.delivery.puppetlabs.net) executed in 2.50 seconds

  playable-girth.delivery.puppetlabs.net (playable-girth.delivery.puppetlabs.net) 17:32:01$ env PATH=":${PATH}" ruby -e 'puts File.stat("C:/ProgramData/PuppetLabs/puppet/cache/state/last_run_report.yaml").mtime.to_i'
    -e:1:in `stat': No such file or directory @ rb_file_s_stat - C:/ProgramData/PuppetLabs/puppet/cache/state/last_run_report.yaml (Errno::ENOENT)
    	from -e:1:in `<main>'

  playable-girth.delivery.puppetlabs.net (playable-girth.delivery.puppetlabs.net) executed in 0.75 seconds
  Exited: 1

jenkins please test this on redhat7-64,ubuntu1804-64,windows2016-64

jenkins please test this on redhat7-64,ubuntu1804-64,windows2016-64

CLA signed by all contributors.

authors: GabrielNagy johnduarte puppetcla

repo: puppetlabs/puppet


text:
Allow substitution tokens in valid SQL.

This replaces any substitution token (%s) with a quoted version of
that token, to please the parser.
It will not affect a substitution token that is already quoted.

Thanks for submitting this. I confess I don't really understand the purpose: I haven't come across this syntax in SQL previously. Could you give me a pointer please?

Strictly speaking, it’s not valid SQL. But those tokens are replaced by the parameters passed to a call to cursor.execute() from python db api calls. It’s the mechanism that prevents sql injection.

Right. I'm not going to merge this, sorry. This is highly implementation-dependent and it would be impossible in the general case to make sqlint cater safely for the non-standard quirks of various languages' DB access libraries.
I also suspect this specific change would break the linting process when the SQL looks like this:
SELECT foo FROM bar WHERE baz LIKE 'r%s%st'

However, with that said, I think you can just use the standard ? syntax for placeholders in the Python DB API, and then I imagine sqlint will be happy with it.

authors: purcell schinckel

repo: purcell/sqlint


text:
能否为 后端传来的 前端尚未实现的 路由菜单 添加“建设中……”视图？

描述问题 (Describe the problem)
导航菜单 一般在项目设计阶段就确定下来，但是前后端的开发需要根据客户需求实现，且前后端分离开发，实现步调可能不一致。 能否为 后端传来的 前端尚未实现的 路由菜单 添加“建设中……”视图？
如何复现该问题 (How to reproduce the problem)
这是一个新的功能需求，不是BUG
操作系统和浏览器信息 (Operating system and browser information)
这是一个新的功能需求，不是BUG
验证 (Verify)

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

这种业务代码很简单 请自行实现

repo: pure-admin/vue-pure-admin


text:
RFC: Remove colors re-exports

To me, re-exports from the colors package just increase the css API surface area for no apparent benefit. Am I missing something?
If not, I propose that we remove these altogether... Does anyone think otherwise?

I agree, and support removing them.

Fine by me!

authors: JordanMartinez nsaunders thomashoneyman

repo: purescript-contrib/purescript-css


text:
Update Pandoc options; resolves #95.

As I mentioned in #95, Pandoc options have changed since the Makefile was written. The CLI was clear about updating --chapters to --top-level-division=chapter; but it was less clear what to do with the -S option. However, the Pandoc User's Guide doesn't list html5 (or html) in the list of formats that support the smart extension that was previously enabled with -S.

Yeah, I'm not sure what the -S did and can't find any info. If it looks good on your end I'm happy to merge this.

Indeed, I reviewed the output and didn't see any obvious problems. After reading the documentation linked above, I think the smart extension simply doesn't apply to HTML output.

Thanks @nsaunders !

authors: nsaunders owickstrom

repo: purescript-spec/purescript-spec


text:
User should be able to provide a list of assemblies to search for ViewModels

Currently the library only searches Assembly-CSharp which is default Unity assembly. Need a way to allow users to provide additional assemblies to search in. This is important for other packages/libraries to depend on this lib

84d83a5c68f555662a827723cb8fc3591dfe8d35

repo: push-pop/Unity-MVVM


text:
عدم دریافت پوش

با عرض سلام
پوشه روی برنامه من رجیستر میشه و دستگاههای مورد نظر رو در لیست نصب میاره ولی امکان دریافت نوت برای برنامم فراهم نیست؟
کسی میدونه چرا؟

سلام.
آیا پوش تستی رو هم دریافت نمی‌کنه؟ از بخش نصب‌ها دیوایس رو پیدا کنید و اعلان تستی ارسال کنید.
اینترنت رو هم وصل کنید

با سلام مجدد
تمام این کارها رو کردم
دستگاه رجیستر میشه ولی نوت تستی رو دریافت نمی کنه
بنده ۳ سال هست با پوشه کار می کنم و تا الان همچین چیزی ندیدم
این پوش آی دی یکی از دستگاه های رجیستر شده
pid_a61d-627a-40
Samsung A30
ممنون میشم زودتر نتیجه رو اعلام کنید

من برناممم روزی چند هزار نصب داره لطفا
زودتر نتیجه رو به بنده اعلام کنید

Closed for Inactivity. Feel free to reopen the issue if the problem still exists.

authors: ansaralghaem mahdi-malv

repo: pusheco/android-studio-sample


text:
Swift example should call completion handler

Swift example for receiving notifications in README:
func application(_ application: UIApplication, didReceiveRemoteNotification userInfo: [AnyHashable : Any], fetchCompletionHandler completionHandler: @escaping (UIBackgroundFetchResult) -> Void) {
    print(userInfo)
}

I think this violates the documentation for this callback which says

As soon as you finish processing the notification, you must call the block in the handler parameter or your app will be terminated.

I would suggest immediately calling the completion handler with .newData.

Fixed in 254e6b7

authors: hamchapman jameshfisher

repo: pusher/pusher-websocket-swift


text:
StorIOSQLite Query builders and tests

Compile-time safe builders for StorIOSQLite queries
@nikitin-da PTAL btw you used Query builder incorrectly in integration tests! Ha!

Part of #218

repo: pushtorefresh/storio


text:
React reboot

note: chaque tache ci dessous à peut-être des choses intéressantes liés dans ./todo.
Ce dossier devra être vide pour les bonnes raisons avant publish de cette nouvelle version. Je pense qu'on se comprends :)

[x] convertir les posts au format souhaité [@MoOx]
[x] parsing des .md  (@bloodyowl)
[ ] pre-render des pages  (@bloodyowl)

[x] post
[ ] home
[ ] liste
[ ] page spécifique

[ ] base du routing
[x] logique de fetching de la data côté front (@bloodyowl)
[x] récupération de la data initiale côté front  (@bloodyowl)
[ ] séparation correcte des CSS
[ ] pre-render pour style-loader/usable
[ ] update cssrecipes
[ ] intégration des contributeurs

[ ] authors json
[ ] task contribution + cache
[ ] contributeur de chaque pages sur chaque pages

[ ] server-side rendering ?
[ ] eslint
[ ] travis testing
[ ] feed.xml
[ ] sitemap.xml ?
[ ] commentaires (disqus, on traitera la migration après)
[ ] script deploy
[ ] listes des posts
[ ] home

[ ] liste des derniers posts
[ ] manifesto
[ ] top contributeur

[ ] 404
[ ] highligh du code
[ ] Vérifier tracker analytics
[ ] CNAME
[ ] favicon (automatiser le build du favicon pour toute plateforme)
[ ] redirection des posts à url pourri (post/entreprendre/*)
[ ] Revoir CONTRIBUTING.md et le post sur comment contribuer (merger tout ça c'est pénible à maintenir 2 ressources)
[ ] Revoir README.md + README branche buildé
[ ] vérifier que ./todo est vide (rien ne devrait rester)
[ ] trouver un hébergeur node gratos si nécessaire (eg: render static trop compliqué) (heroku?)
[ ] travis deploy

J'ai essayé de faire une PR avec une liste assez complète pour qu'on se lance petit à petit :)

Idéalement on fera des PRs sur cette branche.

Je m'occupe de la migration du format des posts demain (mon script est quasi bon)

Super je regarde ce que je peux faire en ren rentrant

Faudrait avant qu'on itère que @bloodyowl pousse ce qu'il a dans le pipe (que ça marche ou pas).
Et je crois qu'il voulait que je pousse les posts migrés. J'essaye de faire ça rapido.

c'est bien d'avoir fait.

Bon voilà les posts sont migrés sur cette branche. @bloodyowl j'attends de tes news maintenant :)

@bloodyowl après t'avoir harcelé par IRC, iMessages puis Twitter j'aimerais savoir si je dois t'envoyer un colis piégé ou plutôt un chèque bancaire pour récupérer ton taf (que même si en travaux sera mieux QUE NOTRE SITE ACTUEL COMPLÈTEMENT PÉTÉ).
Sans quoi je vais partir sur du fresh ou un wordpress par flemme.

Le jour où @bloodyowl va nous pusher ses commits:

Si on passe à Wordpress...

je sens que @bloodyowl va nous faire une paul walker et mourrir en nous laissant un travail inachevé qu'on va devoir remasteriser

tkt une fois que je m'y mets c'est parti @Nyalab https://twitter.com/moox/status/583867151628500992

Là ça fait tellement longtemps qu'on en parle (depuis novembre 2014). On y croit plus. @bloodyowl est un hoax. Un bot. TJ a juste été rename. Je crie au fake.

Sinon on peut utiliser bootstrap avec Joomla ?

je suis tombé la dessus https://github.com/acdlite/flummox
le site de la doc est une  app isomorphic  pré-rendue... react et flux

Perso je l'ai déjà vu.
Tout ce qui nous manque ici n'est pas la technique je pense, mais un peu de volonté de @bloodyowl de se sortir les doigts du cul :trollface:

De mon point de vue, je pense que c'est pas une bonne idée d'attendre la solution clé en main de @bloodyowl , je préférerai qu'il pousse une base  pour itérer dessus. ça permettrai à tout ceux qui le souhaite de prendre le train en marche et de s'approprier le site plutôt que se retrouver à comprendre une archi complète.
Après comme j'ai pas de temps en ce moment à y consacrer,  ça me paraissait une bonne idée pour démarrer une base pour ceux qui voudrait s'y mettre.
des bisous de bisounours

Je rejoins le point de vue de @lionelB . On veut coder, on veut coder

:+1: (comme ça en plus on arrêtera de me casser les couilles :smile:)

Personne à demandé à bloody de tout coder. Cela dit il a déjà fait un gros boulot, autant ne pas le refaire. Pousse nous ça enculay de bloudioule.

Pour info je vais cadeau d'un an d'un serveur node chez gandi (taille M) à celui qui réussi à faire pousser à bloodyowl (cadeau à 100€) + un .fr + cadeau à bloudiouile.
Si @bloodyowl => même cadeau pour lui soit 2 instances M node pour 1 an (non cumulable) + 2 .fr ou 1 .me. Kdo. Mais seulement si :)

230€ de cadeaux à partager. Ou pas @bloodyowl :)

@bloodyowl push le contenu et je te file les liens de GoT eps 6,7,8 ...

franchement c'est n'imp...

t'as mieux ? Je ne pense pas.

bah si @bloodyowl fait son fdp, on s'y met tous et on fait une autre branche. moi je commence à plus y croire, je veux bien attendre mais pas de vraie news, ça traine depuis décembre ... et il veut même pas push pour avoir un truc en pending state quoi ...
je suis juste pas capable de le faire tout seul je pense, mais si y'en a 2 ou 3 avec moi, on fait la maj du site nous même, peut être en plus light, mais whatever quoi, qu'on puisse sortir des posts sur un site correct avec du code propre

J'ai l'impression de revivre l'histoire de robobot (je ne parle pas du projet en lui-même mais comment cela a progressé).
Je me sens un peu impuissant face à tout ça : faute de temps et d'envie, j'étais plutôt clair sur le fait que je voulais surtout juste poster avant tout. Après c'est un peu trop simple de ma part de dire "démerdez vous avec le site, moi j'm'en occupe pas".
Par contre, je n'étais pas pro-react sur ça non plus. Belle idée mais ça semble prendre énormement de temps.
Et je ne peux que dans un premier temps (à voir côté perf) valider le choix de metalsmith qui me convient déjà parfaitement sur mon blog perso.
S'il y a besoin d'aide et qu'on se bouge pour avoir soit une nouvelle version soit régler le bug, dites-le.

Les propos tournent en rond. On sait tous ce qu'on peut faire. C pas question de temps mais de volonté.
J'vais pas sortir des pr or stfu mais ca va pas tarder.
Pour ma part plutot que de parler, je vais decoupler un max ce qui est possible. Et je partirais sur metalsmith car en l'état je ne me sens pas de refaire ce qu'a entamer bloodyowl.

bon, juste histoire que ce soit clair et que vous arrêtiez tous de me les briser: arrêtez avec le "faut pousser ce que t'as", j'ai 2 versions complètement inachevées (une qui partait du principe qu'on pre-render côté local, l'autre côté statique) pour l'instant, et j'ai eu le temps depuis décembre d'en poursuivre aucune, pour des raisons pro & du fait que les problématiques de data-fetching étaient particulièrement chiantes & chronophage sur la première version.
donc le plan idéal, c'est qu'on part tous ensemble sur la branche react-reboot, qu'on se fout une putain de milestone & on itère dessus.

et au pire on part sur metalsmith pour pas se prendre la tête et ça ira très bien.

donc le plan idéal, c'est qu'on part tous ensemble sur la branche react-reboot, qu'on se fout une putain de milestone & on itère dessus.

Go, on prépare tout ça demain sur irc.

bah même en suivant je savais même pas qu'il y avait eu 2 versions différentes qui sont inachevées, je pensais que c'était une seule qui était en cours depuis décembre. enfin un commentaire qui explique clairement où t'en es. ta situation pro osef, on sait tous que personne peut mener à bien un truc comme ça tout seul, on a jamais demandé ça. bon bah du coup ok, on laisse tomber tes branches, tu les feras si tu veux, je pars pour aider sur celle là donc, et je vais essayer de comprendre ce qui a été fait et qui reste à faire, thanks.

Pour ma part vu la complexité du truc, je pense pas partir sur une branche react pour le moment et je vais me concentrer sur les à côtés.
Pas besoin de savoir qui fait quoi. Dire "on explose tout en petites tâches" c'est facile, mais en attendant personne ne l'a fait, moi le dernier.
J'ai tenté un découpage "minimal" et d'ailleurs je viens de le mettre un peu à jour (cf desc de l'issue).
Je renomme cette branche "reboot", car vu comment on part, on sait même pas ou on va.
Moi je veux juste pouvoir pousser des posts. Si on bosses sur un version react dans 1 ans je m'en fou.
md -> html et zou avec découplage maximale des responsabilités.

https://github.com/kud/diary/tree/master/tasks sans gulp ?

Oui kud.
Bon je viens de discuter avec @bloodyowl sur irc. Résumé simple: ce qui a été fait serait à refaire from scratch, certaines taches demandent du temps que nous ne sommes pas prêt à faire. On a pas envie quoi.
Voilà ce qui va se passer: je ferme cette branche.
Cela ne veut pas dire qu'on fera jamais le site en react, ca veut juste dire que ca sera pas dessuite.
En attendant on va se taper un délire vu qu'on veut pas handlebar ni jade (les 2 soules à l'usage): un metalsmith car c'est rapide, avec des templates react car c rigolo et des scripts es6.

Ca me parait pas mal du tout comme roadmap. ;)

authors: MoOx Nyalab bloodyowl kud lionelB magsout


text:
Signup Interactor Test

if there was a ui i was going to add one, but the thing is....

LGTM!!


text:
Fix error message in ModelChain pertaining to temp_model inference

Describe the bug
Error message is incorrect.
The message is:
ValueError: could not infer temperature model from system.temperature_model_parameters. Check that all Arrays in system.arrays have parameters for the same temperature model. Common temperature model parameters: set().
However, in code below we are creating a PVSystem without using Arrays.  So the second sentence in the message above is not describing the proper way to fix this issue.
To Reproduce

from pvlib import pvsystem
from pvlib.location import Location
from pvlib.modelchain import ModelChain

location = Location(latitude=32.2, longitude=-110.9)

modules = pvsystem.retrieve_sam('cecmod')
module_parameters = modules['Canadian_Solar_Inc__CS5P_220M']
inverter_parameters = {'pdc0': 5000, 'eta_inv_nom': 0.96}
system = pvsystem.PVSystem(inverter_parameters=inverter_parameters,
                           module_parameters=module_parameters)

# create the model chain
modelchain = ModelChain(
    system, location, name='dummy_name', aoi_model="physical", temperature_model="pvsyst"
)

Expected behavior
Error message correctly explains what needs to be changed in pvsystem insantiation in order for ModelChain to run.
Versions:

pvlib.__version__: 0.10.2
python: 3.9.6

Additional context
This error message also appears in other contexts.  Namely for other model types:
AC
AOI
DC
spectral
So the error messages for those models should be fixed as well.  Search for 'could not infer' to see which messages.

I started to tackle this issue.  3 questions:

Following @cwhanse wording for the updated error message:
"Could not infer the temperature model. If Arrays are not used to construct the PVsystem, check the PVsystem attributes racking_model and module_type. If Arrays are used, check that all Arrays in ModelChain.system.arrays have parameters for the same temperature model. Common temperature model parameters: {params}."

I did some experimentation when specifying 2 arrays for the PVSystem:
location = Location(latitude=32.2, longitude=-110.9)

modules = pvsystem.retrieve_sam('cecmod')
module_parameters = modules['Canadian_Solar_Inc__CS5P_220M']
inverter_parameters = {'pdc0': 5000, 'eta_inv_nom': 0.96}

module_parameters = {'pdc0': 5000, 'gamma_pdc': -0.004}

mount = pvsystem.FixedMount(surface_tilt=20, surface_azimuth=180)

array_one = pvsystem.Array(mount=mount, module_parameters=module_parameters, temperature_model_parameters={'a': -3.47, 'b': -.0594, 'deltaT': 3})
array_two = pvsystem.Array(mount=mount, module_parameters=module_parameters, temperature_model_parameters={'a': -3.56, 'b': -.0750, 'deltaT': 3}
system_two_arrays = pvsystem.PVSystem(arrays=[array_one, array_two],
                                      inverter_parameters=inverter_parameters)

modelchain = ModelChain(
    system_two_arrays, location, name='dummy_name', aoi_model="physical", temperature_model="sapm", spectral_model="no_loss"
)

I'm not following the reasoning of the last sentence in the error message.  If we specify any dictionary from the same temp model family as above, then we don't get the error at all.
TEMPERATURE_MODEL_PARAMETERS = {
'sapm': {
'open_rack_glass_glass': {'a': -3.47, 'b': -.0594, 'deltaT': 3},
'close_mount_glass_glass': {'a': -2.98, 'b': -.0471, 'deltaT': 1},
'open_rack_glass_polymer': {'a': -3.56, 'b': -.0750, 'deltaT': 3},
'insulated_back_glass_polymer': {'a': -2.81, 'b': -.0455, 'deltaT': 0},
},
'pvsyst': {'freestanding': {'u_c': 29.0, 'u_v': 0},
'insulated': {'u_c': 15.0, 'u_v': 0}}
}
However, if we specify one array to be from 'sapm' and the other one from 'pvsyst' then the error reads:
"Common temperature model parameters: set()."
which is confusing to a user.

Is the wording of the other similar error messages in modelchain that pertain to AC, AOI, DC, spectral in scope to be updated for this issue?  For example, here.

#1942 is a related issue that might be worthwhile tackling first (though I don't have knowledge to take it on without help) before this one, so that we can directly point the user to where to read about racking_module and module_type in the updated error message.  Open to guidance but happy to just focus on this issue first as it is more straightforward.

@cwhanse or one of the other maintainers, can you please provide some pointers on the above.  I would like to start working to resolve this issue.  Thanks.

@matsuobasho pvlib's ModelChain currently only supports a single temperature model for all arrays. There's no way to set a temperature model for each array. We don't need to test or provide an error message if a user specifies temperature model parameters from different models, for different arrays.
We should allow for a user to specify different parameters for the same temperature model, as is done in your example with SAPM. When I run that code, I don't get the error, even after adding a modelchain.run_model call. I think that is correct behavior.
Re-reading that error message text, I would edit it as:
"Could not infer the temperature model. If Arrays are used to construct the PVSystem, check that all Arrays in ModelChain.system.arrays have parameters for the same temperature model. If Arrays are not used, check that the PVsystem attributes racking_model and module_type are valid."
I'm now on the fence if returning " Common temperature model parameters: {params}." is useful.

Regarding your first point, the following comment really pertains to #1942 - the assumption is that the user understands that different parameters in the format
{'a': -3.47, 'b': -.0594, 'deltaT': 3} are from the same temperature model (i.e. there are only 2 temp models).  I think a new user may incorrectly consider 'open_rack_glass_glass', 'close_mount_glass_glass', etc to be different temperature models.
I'll incorporate the wording you propose.
Can you please make a recommendation about whether the wording of the other messages in modelchain that pertain to AC, AOI, DC, spectral are in scope in this issue?

Can you please make a recommendation about whether the wording of the other messages in modelchain that pertain to AC, AOI, DC, spectral are in scope in this issue?

Let's address only the message for the temperature model this issue. When we get concurrence on that change, we can make similar changes to the other messages.

I submitted the PR 1 week ago, requesting feedback on it.  Thank you.

@matsuobasho can you fix the linter issues? I could push to your fork if you would like help.

authors: cwhanse matsuobasho

repo: pvlib/pvlib-python


text:
AWS host: Return the right status

Fixing a small issue, STATUS_MAP was defined but not used.
Issue described at https://github.com/pvoborni/aiohabit/pull/8#issuecomment-663308754.

@pvoborni  let us merge this! thanks for the fix!

authors: Tiboris netoarmando

repo: pvoborni/mrack


text:
How to use moment.js filter function on output ?

How to use moment.js filter function on output ?
Thanks for your work btw!

Merged issue

Hi @nestarz thank you for your update

authors: nestarz pvoznyuk

repo: pvoznyuk/react-live-clock


text:
Add Wilderness weapon tracking

Closes #26
I don't believe the added animations for the Sceptre will have any negative effect on L669-683 of SuppliesTrackerPlugin (hence the deliberate omission of a break; in the added code).

Are you willing to redo this PR so it can be automatically merged?

Added in 6bc3e42e1bc483df258b4c0aa6dc2518521d51ae


text:
Uncover 4.3.1 Still a Failure iPhone 11 Pro Max

Describe the bug
Unc0ver Still Having Issues Please fix
To Reproduce
Steps to reproduce the behavior:

Go to Unc0ver App 4.3.1
View The Log
Scroll down to log Unc0ver App
See error Cant End Background Task 0xb

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

Device (please complete the following information):

iOS Version: iOS 13.3
iOS Device: iPhone 11 Pro Max
unc0ver Version: 4.3.1

Place an "x" between the brackets if true:

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

Logs
If applicable, add logs or error messages here.

when is this issue going to be fixed is getting me frustrated

Itt

@miguelr4720 its an iOS UI error, just ignore it, it doesn't effect unc0ver at all.

authors: Cryptiiiic Yone-beep miguelr4720