text:
"Definite Integrals" Javascript submission does not work

It is just spinning indefinitely. Code itself is ok, checked in browser console.

https://github.com/project-lovelace/lovelace-problems/issues/76#issuecomment-831350553

authors: paniash tiitlan

repo: project-lovelace/lovelace-problems


text:
META: Implementing POW Re-Designs for Tabs and Facets on Results page

Problem Description:
User testing findings from February 2024  shows users face confusion with understanding:

facets only apply to the specific scope rather than apply to all scopes (Objects, works, concepts, etc)
scope tabs have different results than one another. (are NOT non-mutually exclusive)

POW was given the task of reviewing our current layout and modifying it to solve these issues. From the new designs, the
May/June user testing findings has given feedback for it be implemented.
This ticket will serve as the implementation of the re-designs for tabs and facets in advanced and simple search.
Expected Behavior/Solution:

Re-design the front end layout to include all the approved changes from the POW redesigns pdf. (link below)

Requirements:
Simple Search:

Tabs will be connected to the search results box.

Advanced Search:

Tabs will connect to and appear above the search query box.
Search results will be a separate box displayed under the search query.

Simple Search/Advanced Search:

Icons will display within the tab on the right hand side of the scope name.
The facets will no longer display the label Refine.
Facets will live within the  search results page on the left-hand side and under the blue line.
Information text icon (?) will display at the end of the text "X  results"
Selected Filters, Grid View, Sort By and Desc/Asc will continue to work the same.

Needed for promotion:
If an item on the list is not needed, it should be crossed off but not removed.

[x] Wireframe/Mockup - Mike
[ ] Committee discussions - Sarah
[ ] Feasibility/Team discussion - Sarah
[ ] Backend requirements - TBD
[ ] Frontend requirements- TBD
[ ] Are new regression tests required for QA - Amy
[x] Questions
List of questions for discussions. Answers should be documented within the issue.

UAT/LUX Examples:

TBD
TST SS: https://lux-front-tst.collections.yale.edu/view/results/objects?q={"AND"%3A[{"text"%3A"andy"%2C"_lang"%3A"en"}%2C{"text"%3A"warhol"%2C"_lang"%3A"en"}]}&sq=andy+warhol&ip=1&facetRequest=true
TST AS: https://lux-front-tst.collections.yale.edu/view/results/objects?q={"AND"%3A[{"text"%3A"andy"%2C"_lang"%3A"en"}%2C{"text"%3A"warhol"%2C"_lang"%3A"en"}]}&ip=1&facetRequest=true

Dependencies/Blocks:

Blocked By: Issues that are blocking the completion of the current issue.
Blocking: Issues being blocked by the completion of the current issue.

Related Github Issues:
Child Tickets:

https://github.com/project-lux/lux-frontend/issues/416 **
https://github.com/project-lux/lux-frontend/issues/417
https://github.com/project-lux/lux-frontend/issues/418

Related links:
Presentation
Design walkthrough
Prototype
Wireframe/Mockup:
Desktop Mockups can be found here:
FINAL_Approved_Changes_LUX-Yale-Screens for User Testing-2024_05_10.pdf
** Page 7-9 have been labeled as DO NOT USE as we will not be implementing those changes.
Mobile designs - complete, coming (7/23/24)

Update 6/14:
This issue requires POW designs for the mobile view and a design that includes the correct label for the "People and Group" tag. The label should say "People & Groups".

POW has been contacted; next meeting on 6/17.

@roamye What is left to do in order to move this forward? Based on the number of changes, I would say this can be a meta ticket for "Frontend Design Changes" with all additional/individual changes in their own issues and linked to this one. I will map out the specifics but just wondering how this issue should be handled.

@kamerynB - I agree this should be a META ticket. Before moving this to prioritization review the other sub tickets should be listed.
The sub-tickets need to be focused on the  requirements listed above. Do you think two issues would suffice? One focused on Simple Search and another focused on Advanced Search? Or would it be better to split them on each feature? (Ex: one ticket for AS/SS tab redesign, another for the facet redesign... etc) or as you mentioned have a different issue for each individual change?
Let me know what works best for you.

@roamye @jffcamp @prowns I have 2 questions that I wanted to confirm with you all before breaking this out into smaller issues.

I've noticed some changes in the font weight/color/family in the POW designs, such as the advanced search dropdown button text being a black rather than gray. Another example is the help text header "Help" appears to be bolded. Are these also changes that should be made in addition to the layout?

Example of what POW has:

What we currently show:

What is the additional collapse button next to the "Add Row" button in the advanced search? Is this something that was requested?

Example from POW designs:

@kamerynB -
FYI: my answers may be incorrect and replies are based off my current knowledge of this topic
1/2) I do not think font weight/class is being considered to be changed. I think POW could not replicate our old font and used a font solely for mockup purposes which is why design A differs from design B.
3) I am not sure why that is there.
Overall I think the main changes to be considered are those of the tabs and facets and not other changes which differ from our current version (such as fonts, or that expanded/collapsed button).
@jffcamp @prowns - can you confirm or provide a more accurate answer for Kam?
It may be best to bring this to #agenda for a small discussion.

@kamerynB - this ticket should be on hold. Per @prowns we are still waiting on final designs. Once we have those a meeting with you @dcheather and Jimmy will take place to sort out the details.

Can this be a quick agenda topic? @prowns @roamye

@kamerynB - Yes, its added to today's agenda.

From IT Team Meeting 08/07:
We are awaiting for the figma files to be completed. However, @kamerynB can start mapping out tickets.
There will need to be a deskptop/mobile discussion with Jimmy, Heather and Kam after figma files have been finalized.

@kamerynB - as of 9/9 the following links contain the finalized version for the mobile/desktop updates:
Presentation
Design walkthrough
Prototype
I have also linked these in the related links section of this issue. Would a PDF copy of the finalized figmas be helpful?
If you would like, I can create some initial requirements based on what I have seen in the figma. We can then map out tickets based on what is needed.
Please let me know if you have any questions, or would like my help mapping out the issues.
Thank you!
(I have also left the same comment on #269)

Note from 10/4/24 team meeting:
The switch from advanced search to simple search should be clearer as to how the user will be impacted, ie lost search criteria.

From Meeting 11/4 with @kamerynB -

The sub/children tickets are fine with Kam and have been moved officially moved to backlog.
one PR/branch may need to be opened rather than two when working on #417 & #418.

Not approved by UAT as there are some issues that will need to be added. Removing this off the milestone and it's corresponding labels.

source: gharchive/issue

authors: kamerynB prowns roamye

repo: project-lux/lux-frontend

license_type: permissive

license_source: github-api


text:
Tutorials are using Result<()> as return type of the functions instead of ProgramResult

The tutorials functions are all returning Result<()> without using anyhow crate, all fn should be returning ProgramResult so we can use Ok(()) at the end of the functions

Result<()> is not specific to anyhow. ProgramResult should not be used with Anchor, which uses a custom error type to store diagnostic information.

authors: armaniferrante rsWrathionTBP

repo: project-serum/anchor


text:
cli: add warning when program is found with mismatched anchor version

resolves #1684

This doesnt achieve much yet as the check is in get_program which is only used by publish. The check should be in/before all commands

source: gharchive/pull-request

authors: callensm paul-schaaf


text:
Create token accounts if they don't already exist

Swapping to a token should create an associated token account, if it doesnt already exist. This includes intermediary accounts (udsc, usdt) for transitive swaps. This should happen in the transactions constructed from the @project-serum/swap package.

This shouldn't block the first release. Removing p1 tag.

This issue is resolved, just tested. Can close the issue

authors: armaniferrante secretshardul

repo: project-serum/swap-ui


text:
Fix BZ1329743 [rhel7-1.10.3]

Fix https://bugzilla.redhat.com/show_bug.cgi?id=1329743
Signed-off-by: Antonio Murdaca runcom@redhat.com

LGTM

authors: rhatdan runcom

repo: projectatomic/docker

license_source: bigquery


text:
latest skopeo and oci image-tools don't seem to match up

Testing out skopeo and image-tools but having a hard time getting them to work together.
[root@ed78599d315d deleteme]# skopeo copy docker://centos oci:centos-oci
Getting image source signatures
Copying blob sha256:45a2e645736c4c66ef34acce2407ded21f7a9b231199d3b92d6c9776df264729
 67.13 MB / 67.13 MB [=========================================================]
Copying config sha256:67591570dd29de0e124ee89d50458b098dbd83b12d73e5fdaf8b4dcbd4ea50f8
 0 B / 2.25 KB [---------------------------------------------------------------]
Writing manifest to image destination
Storing signatures
[root@ed78599d315d deleteme]# oci-image-validate centos-oci/
centos-oci/: validation failed: mediaType: mediaType is required
[root@ed78599d315d deleteme]# oci-image-validate --ref latest centos-oci/
centos-oci/: validation failed: mediaType: mediaType is required

Any idea what is going on?  Running this inside docker with the following Docker file
# Followed https://www.digitalocean.com/community/tutorials/how-to-install-go-1-7-on-centos-7
FROM centos:centos7

# Setup golang
RUN (cd /usr/local; curl -L 'https://storage.googleapis.com/golang/go1.7.linux-amd64.tar.gz' | tar -xzf -)

# Setup go source locations
RUN \
  mkdir -p /opt/golang/ $HOME/bin && \
  echo "export PATH=$PATH:/usr/local/go/bin" >> /etc/bashrc && \
  echo "export GOBIN=$HOME/projects/bin" >> /etc/bashrc && \
  echo "export GOPATH=$HOME/projects/src" >> /etc/bashrc

ENV PATH    $PATH:/usr/local/go/bin:$HOME/bin
ENV GOBIN   $HOME/projects/bin
ENV GOPATH  $HOME/projects/src

# install dependencies
RUN \
  yum groupinstall -y "development tools" && \
  yum install -y tree git make gpgme-devel libassuan-devel device-mapper-devel btrfs-progs-devel libseccomp-devel which

# install skopeo
# https://github.com/projectatomic/skopeo
RUN \
  git clone https://github.com/projectatomic/skopeo $GOPATH/src/github.com/projectatomic/skopeo && \
  cd $GOPATH/src/github.com/projectatomic/skopeo && \
  make binary-local && \
  mv skopeo $HOME/bin/ && \
  mkdir -p /etc/containers && \
  cp default-policy.json /etc/containers/policy.json

# install OCI image tools
# https://github.com/opencontainers/image-tools/
RUN \
  git clone https://github.com/opencontainers/image-tools.git $GOPATH/src/github.com/opencontainers/image-tools && \
  cd $GOPATH/src/github.com/opencontainers/image-tools && \
  make tools && \
  mv oci-* $HOME/bin

# install runC
# https://github.com/opencontainers/runc
run \
  git clone https://github.com/opencontainers/runc.git $GOPATH/src/github.com/opencontainers/runc && \
  cd $GOPATH/src/github.com/opencontainers/runc && \
  make && \
  mv runc $HOME/bin

This is an issue with upstream oci-image-tool. oci-image-tool uses image-spec v1.0.0-rc3 whether we're tracking image-spec master and master contains https://github.com/opencontainers/image-spec/pull/531 which drops mediaType at the manifest level.
As soon as image-spec reaches v1.0.0 we'll freeze the spec vendored and everything should work.

authors: dcapwell runcom

repo: projectatomic/skopeo


text:
Pods connected to Calico IPPool with NAT not connecting from Node IP

I have a Raspberry Pi K8S cluster, 1 master (192.168.86.150) and 2 nodes (192.168.86.152 and 153).  I also have another Pi acting as an NFS server (192.168.86.160). I have Calico configured, and I used calicoctl to see if it had NAT enabled, which it does.
However, any outgoing traffic from a pod to my local network appears to come from the Pod IP, not the node IP, which means nothing can route back in.
Bit more info: my local subnet (as in everything on my home network) is 192.168.86.0/24 provided by DHCP on my Google Wifi router.
This is my Calico IPPool config
{
  "kind": "IPPoolList",
  "apiVersion": "projectcalico.org/v3",
  "metadata": {
    "resourceVersion": "11027205"
  },
  "items": [
    {
      "kind": "IPPool",
      "apiVersion": "projectcalico.org/v3",
      "metadata": {
        "name": "default-ipv4-ippool",
        "uid": "7f876465-0c94-4087-b567-8b12171421aa",
        "resourceVersion": "2336",
        "creationTimestamp": "2020-09-15T17:13:01Z"
      },
      "spec": {
        "cidr": "192.168.0.0/16",
        "vxlanMode": "Never",
        "ipipMode": "Always",
        "natOutgoing": true,
        "blockSize": 26,
        "nodeSelector": "all()"
      }
    }
  ]
}

My nodes have chosen 192.168.185.0/24 and 192.168.244.0/24 for the pod networks.
When I do a connection test from a pod to a server on my local network, this is what I see in tcpdump
13:29:05.294836 IP 192.168.185.244.32866 > k8snfs.9000: Flags [S], seq 4185311275, win 64400, options [mss 1400,sackOK,TS val 3431307964 ecr 0,nop,wscale 7], length 0
Note how it's connected from the Pod IP, and not a NAT IP (which I assume would be the node's IP ?) Because the server it connected to doesn't know how to route back to 192.168.185.0/24, it just fails the connection, which makes total sense.
What have I missed ? What can I check ? I'm pretty new to K8S, so a bit of guidance would be greatly appreciated :)

Update to this: I thought it might be caused by my K8S calico ippool kinda being in the same subnet, so I switched my whole environment to using 172.16.0.0/16 and recreated my test pods, but it still connects as the pod IP and not the NAT IP
10:55:17.402626 IP 172.16.249.4.37082 > ubuntu-vm.lan.9000: Flags [S], seq 2636212639, win 64400, options [mss 1400,sackOK,TS val 136381942 ecr 0,nop,wscale 7], length 0
Please help :(

So to get NATed, the packet must be leaving the pod subnet.  I think what's wrong here is that the NFS server has an IP inside the pod-cidr, so Calico thinks that the traffic is pod-pod.
You need pod cidr, host cidr and service cidr to be non-overlapping to avoid issues.

Hey @lwr20 - thanks.  I experience the same issue even once I've changed the pod CIDR to 172.16.0.0/16 - all connections (as per my update) are being received from the pod IP, not the node IP :(

Can I see the output of ip r on the node with the pod please?
BTW - I can also help you with this on slack - http://slack.projectcalico.org/ for an invite, I'm lrobson in there

repo: projectcalico/calico


text:
[DO NOT MERGE] Updated document for host endpoint policy on forward traffic.

Description
Document for host endpoint policy on forward traffic.

Another overall comment: our renderer has no problem if we break the lines at 70-80 characters, the text flows fine, so we have been breaking the lines around there for readability of the source markdown. So it might be nice if you could insert those breaks, as well.

Just noticed a few more minor items @song-jiang ... Thanks!

Looking good @song-jiang I just had one more comment...not sure if I mentioned this in my previous review...my bad if I omitted this feedback earlier. Overall, it's looking great! Thanks... 👍

LGTM thanks @song-jiang ! We need to hold off on merging this though...until after 2.6 gets released. cc @ozdanborne

Thanks @song-jiang - I'm happy with the changes for my last comments.  If you just address @emanic's last comments, I'll be happy to approve and merge this!

Hi @song-jiang  @neiljerram I only got partway through my review yesterday. However, we do not want to merge this until AFTER 2.6 gets released. That's because this feature will not be included in 2.6. Thanks!

Really starting to look pretty good @song-jiang !! thanks for all of your work on this! 💯

Related PRs for this feature.
https://github.com/projectcalico/calico/pull/1100
https://github.com/projectcalico/libcalico-go/pull/512
https://github.com/projectcalico/felix/pull/1542
https://github.com/projectcalico/calicoctl/pull/1705
https://github.com/projectcalico/typha/pull/47

All related PRs has been merged.

authors: emanic neiljerram song-jiang


text:
Add terraform logic for building a release VM

Description

Adds simple terraform to manage a build-machine for releasing Calico.
Deploys a build-machine with:

Prerequisites installed
Calico repo checked out
Docker daemon authenticated using provided credentials
GH access via user provided token in environment

To use, simply provide the necessary variables and run terraform apply.
You can then SSH to the machine to run build commands.
Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Still need to get github auth so we can push the tag, and fix ghr so that it's in the path on the machine.


text:
chore: slice lopp replace

Description

Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

TBD

Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one docs-* label.

docs-pr-required: This change requires a change to the documentation that has not been completed yet.
docs-completed: This change has all necessary documentation completed.
docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

release-note-required: This PR has user-facing changes. Most PRs should have this label.
release-note-not-required: This PR has no user-facing changes.

Other optional labels:

cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

 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.

/sem-approve

@caseydavenport @testwill  Can we please update and fix the incorrect conversion between Uint64 to Int64? Alternatively, the commit can be reverted.
The error message:
Incorrect conversion of an unsigned 64-bit integer from strconv.ParseUint to a lower bit size type int64 without an upper bound check.
The path data takes:
apiserver/pkg/storage/calico/api_object_versioner.go:30
apiserver/pkg/storage/calico/resource.go:304
apiserver/pkg/storage/calico/resource.go:308
For more info see CodeQL alert.

authors: Behnam-Shobiri CLAassistant caseydavenport testwill


text:
554 edit admin set redirect

When an admin set title or description is updated, the redirect now sends an update message and remains on the same tab of the form.
Fixes https://github.com/projecthydra-labs/hyrax/issues/554
Also adds a translation for the permission template update message when a participant's rights are removed.
@projecthydra-labs/hyrax-code-reviewers

Can you squash these into one commit?  You are testing for the translated value in the first commit and changing the translated value in the controller on the second commit, so two commits is a little awkward.

@jcoyne done. :)

authors: jcoyne laritakr

repo: projecthydra-labs/hyrax


text:
Enable "Always On" by Default

"Always On" is disabled by default. If a customer has a function that triggers on a specific action that doesn't happen for an extended period, this can cause the app to be shutdown due to inactivity. This results in the function's trigger no longer firing. Enabling "Always On" by default will prevent this and it's the solution given when a user encounters this issue.
It would also be nice to have a notation for Function Apps explaining this. We might even want to expose the "Always On" setting directly in the Function App as one of the big, blue buttons along with a note explaining it.

How are you creating your function app? Always On is supposed to be enabled by default when creating a Classic mode function app via Portal. And for Dynamic, Always On is not needed.

Created it in the portal. It could just be the confusing UI. I see the setting set to "Off" and it's disabled so that I can't change it. (This is in my classic mode function app.) In my dynamic mode app, I can change it even though it's unnecessary. Is that the way it should be? Disabled and showing Off? Seems like it should be disabled and showing "On". That would resolve this concern.

You cannot change it in a dynamic app. You'll get an error if you try. Though I do agree it should be disabled. @Tuesdaysgreen?
Is your Classic app in Free/Shared, or in Basic/Standard? Always On is only available in Basic/Standard. And yes, that does mean if you use Free/Shared, you'll get a Function app which won't work properly (outside of http triggers). Same issue exists for continuous WebJobs.

Ah, got it. That makes sense. We'll write up a blog post on this in CSS to help customers who are encountering it. Thanks!

Sounds good, thanks!

repo: projectkudu/AzureFunctionsPortal


text:
Implement invoke command

also adds support for:

optional arguments
base double dash arguments
os/exec testing

@markfisher raised a question as to whether invoke should be a command. Even if we don't want the command, dealing with option arguments and testing code that shells out to another executable is interesting.

Marking this command as hidden until we figure out what to do with it. It can be called by clients that know it exists, but is otherwise invisible.

repo: projectriff/riff


text:
🛑 Prokerala is down

In 5a9e06f, Prokerala (https://www.prokerala.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Prokerala is back up in f55eb6d.

repo: prokerala/uptime

license: MIT


text:
Remove alert_groups from alertmanager

I remember it being mentioned that we don't want to use this anymore, and as far as I can tell it is exposed via api but the neither the UI or the amtool use it. I also didn't see it mentioned in the proposal of the v2 api.
Is this something we can remove?
removal would be the opposite of http://petstore.swagger.io/?url=https://raw.githubusercontent.com/mxinden/alertmanager/apiv2/api/v2/openapi.yaml
@simonpasquier @mxinden

I thought about it but should probably check with @TheTincho

Are you talking about the alerts/groups function?
As far as I remember this was used in the old Angular UI, but was not needed anymore with the ELM rewrite. I have not included it in the API v2 Proposal for that reason.
Whats the reasoning for removing it now? I would suggest removing it along with the entire API v2, once v2 is merged and a two of minor releases passed.

I thought about it but should probably check with @TheTincho

As far as I know Debian simply removes the UI, thereby it is also not dependant on this endpoint, right?

I thought about it but should probably check with @TheTincho

As far as I know Debian simply removes the UI, thereby it is also not dependant on this endpoint, right?

I seem to recall that there was a tentative effort to retrofit the old UI in Debian (and thus depend on /api/v1/alerts/groups) but I might be wrong.
Assuming there's no opposition, I would be in favor of removing alerts/groups now.

Hey all, sorry for the late reply.
Like Stuart says, currently Debian ships no UI.
I wanted to retrofit the old UI, but I had understood that the API had changed so much it was not possible anymore, so I did not try in the end. I think it does not make sense to keep this, if we manage to finally prepare an UI, this will be just another thing to fix.
Thanks for checking!

authors: TheTincho mxinden simonpasquier stuartnelson3

repo: prometheus/alertmanager


text:
Adding ctime, rtime, and ttime metrics

This adds support for the ctime, rtime and ttime metrics in 1.5. I debated on converting them to seconds since they are reported in ms so I am looking for guidance there.

Duplicate of #38. See also #37.

Oh wow, sorry about that. I should have looked. Is there plans to merge either of those?

You'd need to add convincing arguments to the discussion. Brian argued the values can be far from the truth due to the decay. We should probably open the discussion with Willi/the HAProxy people to add proper counters.

@wtarreau WDYT?

To be clear, what would be perfect are millisecond cumulative int64 counters that go with ctime&friends, and are exposed with the csv metrics.

authors: brian-brazil davidkarlsen grobie ipstatic


text:
Add Generic HTTP-based SD

Proposal
Use case. Why is this important?
This SD should look exactly the same as the file-based SD, except that it is fetched from an HTTP endpoint rather than the local fs.
I work on a large project for storage monitoring and I think many face the same issue that we do. We don't want to open a SD request for our own Project, but a generic HTTP-based would satisfy everyone.
I am also coding in Go, so if the community thinks this is a good idea, I could prepare a pull request.

I am also coding in Go, so if the community thinks this is a good idea, I could prepare a pull request!

This is discussed here: https://docs.google.com/document/d/1tVeuzjpU4-TiYPNWJXKmcyIuZF6A2tUq270RbBT5zho/edit

awesome, thanks for sharing the link

is someone already working on this? should I go ahead and try to implement it myself?

There are still disagreements over the design doc.

This is being implemented in #8839

Can this issue be closed now?

Yes 🥳

authors: juliusv roidelapluie vgratian

repo: prometheus/prometheus


text:
Fix a very special case of handling the checkpoint timer

@fabxc This should finally nail it. Explanation for this is labyrinthine...

:+1:

:+1:

This has run over night on a heavily loaded server that was exposing the weird edge case.
I'm pretty confident it's fixed now. We should cut 0.17 soon.

authors: beorn7 fabxc juliusv


text:
promql: fix typo.

Swap the result and bool order.

Thanks, though this is not a typo.

authors: brian-brazil johncming


text:
Segmentation fault when set pipeline with RTSP source created from rtsp-simple-server

Currently, I'm using rtsp-simple-server to create a rtsp stream from video

run simple rtsp server docker:
docker run --rm -it -e RTSP_PROTOCOLS=tcp -p 8554:8554 aler9/rtsp-simple-server
stream video to rtsp server:
ffmpeg -re -stream_loop -1 -i <video_path> -f rtsp rtsp://localhost:8554/mystream
play:
ffplay rtsp://localhost:8554/mystream

I can use this RTSP stream with deepstream-app and deepstream-python-app as well.
But when I use dsl to create rtsp sink, the system return: Segmentation fault (core dumped). I used dsl_source_rtsp_new to created rtsp sink.
Here is my code:

import sys
import time
from dsl import *

# update host URL to IP address if clients are off device.
# host_uri = '0.0.0.0'

file_path = "/opt/nvidia/deepstream/deepstream/samples/streams/sample_1080p_h265.mp4"
rtsp_url = "rtsp://192.168.100.13:8554/mystream"

# Filespecs (Jetson and dGPU) for the Primary GIE
primary_infer_config_file = \
    '/opt/nvidia/deepstream/deepstream/samples/configs/deepstream-app/config_infer_primary.txt'
primary_model_engine_file = \
    '/opt/nvidia/deepstream/deepstream/samples/models/Primary_Detector/resnet10.caffemodel_b8_gpu0_int8.engine'

# Filespec for the IOU Tracker config file
iou_tracker_config_file = \
    '/opt/nvidia/deepstream/deepstream/samples/configs/deepstream-app/config_tracker_IOU.yml'

##
# Function to be called on XWindow KeyRelease event
##
def xwindow_key_event_handler(key_string, client_data):
    print('key released = ', key_string)
    if key_string.upper() == 'P':
        dsl_pipeline_pause('pipeline')
    elif key_string.upper() == 'R':
        dsl_pipeline_play('pipeline')
    elif key_string.upper() == 'Q' or key_string == '' or key_string == '':
        dsl_pipeline_stop('pipeline')
        dsl_main_loop_quit()

##
# Function to be called on XWindow Delete event
##
def xwindow_delete_event_handler(client_data):
    print('delete window event')
    dsl_pipeline_stop('pipeline')
    dsl_main_loop_quit()

##
# Function to be called on End-of-Stream (EOS) event
##
def eos_event_listener(client_data):
    print('Pipeline EOS event')
    dsl_pipeline_stop('pipeline')
    dsl_main_loop_quit()

##
# Function to be called on every change of Pipeline state
##
def state_change_listener(old_state, new_state, client_data):
    print('previous state = ', old_state, ', new state = ', new_state)
    if new_state == DSL_STATE_PLAYING:
        dsl_pipeline_dump_to_dot('pipeline', "state-playing")

def main(args):

    # Since we're not using args, we can Let DSL initialize GST on first call
    while True:

        # New File Source using the file path specified above, repeat enabled.
        # retval = dsl_source_file_new('file-source', file_path, True)
        # retval = dsl_source_uri_new('file-source', file_path, is_live=True, skip_frames=0, drop_frame_interval=0)
        retval = dsl_source_rtsp_new(name='file-source', uri=rtsp_url, protocol=DSL_RTP_ALL, skip_frames=0, latency=1000, timeout=0, drop_frame_interval=0)

        if retval != DSL_RETURN_SUCCESS:
            break

        # New Primary GIE using the filespecs above with interval = 0
        retval = dsl_infer_gie_primary_new('primary-gie',
            primary_infer_config_file, primary_model_engine_file, 0)
        if retval != DSL_RETURN_SUCCESS:
            break

        # New IOU Tracker, setting operational width and height.
        retval = dsl_tracker_new('iou-tracker', iou_tracker_config_file, 480, 272)
        if retval != DSL_RETURN_SUCCESS:
            break

        # New OSD with text, clock and bbox display all enabled.
        retval = dsl_osd_new('on-screen-display',
            text_enabled=True, clock_enabled=True,
            bbox_enabled=True, mask_enabled=False)
        if retval != DSL_RETURN_SUCCESS:
            break

        # New EGL Window Sink with offests and dimensions
        retval = dsl_sink_window_egl_new('window-sink', 100, 100, 1280, 720)
        if retval != DSL_RETURN_SUCCESS:
            break
        # Add the XWindow event handler functions defined above
        retval = dsl_sink_window_key_event_handler_add('window-sink',
            xwindow_key_event_handler, None)
        if retval != DSL_RETURN_SUCCESS:
            break
        retval = dsl_sink_window_delete_event_handler_add('window-sink',
            xwindow_delete_event_handler, None)
        if retval != DSL_RETURN_SUCCESS:
            break

        # Add all the components to our pipeline
        retval = dsl_pipeline_new_component_add_many('pipeline',
            ['file-source', 'primary-gie', 'iou-tracker', 'on-screen-display',
            'window-sink', None])
        if retval != DSL_RETURN_SUCCESS:
            break

        ## Add the listener callback functions defined above
        retval = dsl_pipeline_state_change_listener_add('pipeline',
            state_change_listener, None)
        if retval != DSL_RETURN_SUCCESS:
            break
        retval = dsl_pipeline_eos_listener_add('pipeline',
            eos_event_listener, None)
        if retval != DSL_RETURN_SUCCESS:
            break

        # Play the pipeline
        retval = dsl_pipeline_play('pipeline')
        if retval != DSL_RETURN_SUCCESS:
            break

        dsl_main_loop_run()
        retval = DSL_RETURN_SUCCESS
        break

    # Print out the final result
    print(dsl_return_value_to_string(retval))

    dsl_delete_all()

if __name__ == '__main__':
    sys.exit(main(sys.argv))

I'm using docker image nvcr.io/nvidia/deepstream:6.2-devel and run with dgpu

@subzeromot thanks for reporting this.
Could you look in your DSL Makefile and please tell me what version you are using?
and could you provide me with a log file?
export GST_DEBUG_FILE=./log.txt
export GST_DEBUG=1,DSL:4

So far, I'm unable to reproduce any issue with the cameras that I have.  Would you be willing to debug this issue for me a little? Do you use vscode?

@subzeromot I'm unable to reproduce any issue... If I try with you commands above, I see
INFO                     DSL src/DslSourceBintr.cpp:3579:HandleSelectStream:  : Media = 'video' for RtspSourceBitnr 'file-source'
INFO                     DSL src/DslSourceBintr.cpp:3581:HandleSelectStream:  : Encoding = 'MP4V-ES' for RtspSourceBitnr 'file-source'
ERROR                    DSL src/DslSourceBintr.cpp:3633:HandleSelectStream:  : Unsupported encoding = 'MP4V-ES' for RtspSourceBitnr 'file-source'
ERROR                rtspsrc gstrtspsrc.c:7966:gst_rtspsrc_open_from_sdp:<file-source-rtspsrc> setup failed
ERROR                    DSL src/DslPipelineStateMgr.cpp:472:HandleErrorMessage:  : Error message 'No supported stream was found. You might need to allow more transport protocols or may otherwise be missing the right GStreamer RTSP extension plugin.' received from 'file-source-rtspsrc'

...but no crash.
If I update the ffmpeg command to include -vcodec h264 your script above works correct for me.

@subzeromot I'm unable to reproduce any issue... If I try with you commands above, I see
INFO                     DSL src/DslSourceBintr.cpp:3579:HandleSelectStream:  : Media = 'video' for RtspSourceBitnr 'file-source'
INFO                     DSL src/DslSourceBintr.cpp:3581:HandleSelectStream:  : Encoding = 'MP4V-ES' for RtspSourceBitnr 'file-source'
ERROR                    DSL src/DslSourceBintr.cpp:3633:HandleSelectStream:  : Unsupported encoding = 'MP4V-ES' for RtspSourceBitnr 'file-source'
ERROR                rtspsrc gstrtspsrc.c:7966:gst_rtspsrc_open_from_sdp:<file-source-rtspsrc> setup failed
ERROR                    DSL src/DslPipelineStateMgr.cpp:472:HandleErrorMessage:  : Error message 'No supported stream was found. You might need to allow more transport protocols or may otherwise be missing the right GStreamer RTSP extension plugin.' received from 'file-source-rtspsrc'

...but no crash.
If I update the ffmpeg command to include -vcodec h264 your script above works correct for me.

thanks, it worked now


text:
Provider can stake tokens

As a Deactivated Provider
I can stake tokens
So that I can activate my service
As an Active Provider
I can stake tokens
So that I can maintain my service

Done but needs to be tested.

https://github.com/prosopo-io/provider/issues/18

repo: prosopo-io/provider


text:
🛑 nftschool.dev is down

In 6c4fa28, nftschool.dev (https://nftschool.dev) was down:

HTTP code: 0
Response time: 0 ms

Resolved: nftschool.dev is back up in 332a9ff after 16 minutes.

repo: protocol/upptime-pln


text:
🛑 fil.page is down

In 1b6fb2f, fil.page (https://fil.page) was down:

HTTP code: 0
Response time: 0 ms

Resolved: fil.page is back up in f997ddc after 7 minutes.


text:
button "+ Add Custom Parameter" return 404

Describe the bug
button "+ Add Custom Parameter" return 404
Expected behavior
a parameter list?
Set up
kafka-ui: v0.6.0 and v0.6.1
kafka: 2.2
Steps to Reproduce
choose an exist topic
enter "edit settings" page
click "+ Add Custom Parameter" button
i got a 404 page
Additional context

Hi, could you please share a screenshot of 404 you've got?

Hi, could you please share a screenshot of 404 you've got?

Duplicate of #3554. To be resolved within #3661.

authors: Haarolean fisherwei

repo: provectus/kafka-ui


text:
CVE fixes attempt 1

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

What changes did you make? (Give an overview)
Is there anything you'd like reviewers to focus on?
How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

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

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

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

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

closing due to https://github.com/provectus/kafka-ui/pull/3624

authors: Haarolean iliax


text:
Bump os to 0.7.0 in dev tools.

Ran the simple contract example successfully to verify.

Current dependencies on/for this PR:

main

PR #45  (this PR)

This comment was auto-generated by Graphite.

Codecov Report

Merging #45 (ebfbbc1) into main (7294f25) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main      #45   +/-   ##
=========================================
  Coverage     80.00%   80.00%
  Complexity      137      137
=========================================
  Files            19       19
  Lines          1110     1110
  Branches        123      123
=========================================
  Hits            888      888
  Misses          157      157
  Partials         65       65

Continue to review full report at Codecov.

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


text:
try excluding anything bouncycastle from MemoryClassLoader

kind of a band-aid for validation

Codecov Report

Merging #50 (3033201) into main (107a365) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main      #50   +/-   ##
=========================================
  Coverage     80.78%   80.78%
  Complexity      142      142
=========================================
  Files            19       19
  Lines          1145     1145
  Branches        132      132
=========================================
  Hits            925      925
  Misses          148      148
  Partials         72       72

Continue to review full report at Codecov.

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

authors: codecov-commenter piercetrey-figure


text:
Validator: Account not found: key not found rpc error

Summary of Bug
I hit an rpc error as key not found as below while creating a validator node on my ubuntu machine.
$ provenanced tx staking create-validator --moniker secured_provenance --pubkey tpvalconspub1zcjduepq5x4s983f2ueq3tr6mnkzcc3jvp637nnmu4swu4727c6u959qw9vqua29kg  --commission-rate=1.0 --commission-max-rate=1.0 --commission-max-change-rate=1.0 --min-self-delegation=1 --from=secure_key --amount 65000nhash --keyring-dir /home/ubuntu/.config/Provenance/ -t --broadcast-mode block
Error: rpc error: code = NotFound desc = account tp14qrnd9jplk4ag2e8620396mrag34esvenlaj6s not found: key not found

I have used the pub key derived from the show-validator command as below:
$ provenanced --testnet tendermint show-validator
tpvalconspub1zcjduepq5x4s983f2ueq3tr6mnkzcc3jvp637nnmu4swu4727c6u959qw9vqua29kg

The account and key-dir seems to be valid and active:
$ provenanced --testnet q bank balances tp14qrnd9jplk4ag2e8620396mrag34esvenlaj6s --node=tcp://rpc-0.test.provenance.io:26657
balances:
- amount: "2000000000"
  denom: nhash
pagination:
  next_key: null
  total: "0"

$ provenanced keys list --keyring-backend test -t
- name: secure_key
  type: local
  address: tp14qrnd9jplk4ag2e8620396mrag34esvenlaj6s
  pubkey: tppub1addwnpepqwgpkqemkvxjwv2nuvz5jehu9z89qcx5vme8356q5klh3lrj3ds2xw4lqg5
  mnemonic: ""
  threshold: 0
  pubkeys: []

Version
$ provenanced version
v1.0.0
Steps to Reproduce
git clone -b v1.0.0 https://github.com/provenance-io/provenance
cd provenance && make install
export PATH=$PATH:/home/ubuntu/go/bin
provenanced init secured_provenance --testnet
curl https://raw.githubusercontent.com/provenance-io/testnet/main/pio-testnet-1/genesis.json > genesis.json
export PIO_HOME=/home/ubuntu/.config/Provenance
mkdir -p $PIO_HOME/config
mv genesis.json $PIO_HOME/config
Edit $PIO_HOME/config/config.toml with
    db_backend = "cleveldb"
	seeds = "2de841ce706e9b8cdff9af4f137e52a4de0a85b2@104.196.26.176:26656,add1d50d00c8ff79a6f7b9873cc0d9d20622614e@34.71.242.51"
	namespace = "provenance"
go get github.com/provenance-io/cosmovisor/cmd/cosmovisor
mkdir -p $PIO_HOME/cosmovisor/install
cd $PIO_HOME/cosmovisor/install
git clone https://github.com/provenance-io/cosmovisor.git
cd cosmovisor
make
cp build/cosmovisor /home/ubuntu/go/bin/cosmovisor

export DAEMON_NAME="provenanced"
export DAEMON_HOME="${PIO_HOME}"
export DAEMON_ALLOW_DOWNLOAD_BINARIES="true"
export DAEMON_RESTART_AFTER_UPGRADE="true"

# Set up keys
# Whilelist the account

mkdir -p $PIO_HOME/cosmovisor/genesis/bin
mkdir -p $PIO_HOME/cosmovisor/upgrades
ln -sf $PIO_HOME/cosmovisor/genesis/bin $PIO_HOME/cosmovisor/genesis/current

cp $(which provenanced) $PIO_HOME/cosmovisor/genesis/bin
ln -sf $PIO_HOME/cosmovisor/genesis/bin/provenanced $(which provenanced)

# get the pub key
provenanced --testnet tendermint show-validator

# Run full node
cosmovisor start --testnet --home $PIO_HOME --p2p.seeds 2de841ce706e9b8cdff9af4f137e52a4de0a85b2@104.196.26.176:26656,add1d50d00c8ff79a6f7b9873cc0d9d20622614e@34.71.242.51:26656 --x-crisis-skip-assert-invariants

# Run validator
provenanced  tx staking create-validator --moniker secured_provenance --pubkey tpvalconspub1zcjduepq5x4s983f2ueq3tr6mnkzcc3jvp637nnmu4swu4727c6u959qw9vqua29kg  --commission-rate=1.0 --commission-max-rate=1.0 --commission-max-change-rate=1.0 --min-self-delegation=1 --from=secure_key --amount 65000nhash --keyring-dir /home/ubuntu/.config/Provenance/ -t --broadcast-mode block

For Admin Use

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

You have a potentially different paths on the keys list command and the others. For consistency use the same --home folder flag on all commands to ensure you are working with the same folder in each case.
The error you are getting simply means your keyring does not contain the key listed.

It all looks good there Ira Miller. I tried again and hitting the same issue. What else can I verify?
Tried with an earlier version this time -
$ provenanced version
0.2.0

I'm out for a few days... maybe @arnabmitra can assist or pull someone in to help you.

It all looks good there Ira Miller. I tried again and hitting the same issue. What else can I verify?
Tried with an earlier version this time -
$ provenanced version
0.2.0

Hi,
the current provenance version is 1.6.0 on testnet, however i think your problem is that the key is not being found in you create validator command

remove --keyring-dir
add --keyring-backend test to your existing cmd

not specifying a key ring backend default it to os which you are not setting up from what i can see
https://docs.cosmos.network/v0.43/run-node/keyring.html for more info.

Also, have you tried any other transactions with that account?  It would be a good test to try and send some nhash with a bank tx.
Example:
provenanced tx bank send tp14qrnd9jplk4ag2e8620396mrag34esvenlaj6s <to_address> 100000000nhash --fees 1000000000nhash --chain-id pio-testnet-1 --keyring-backend test --testnet --home $PIO_HOME

Thanks for your response Arnab and Carlton.
I can see the key when I specify  --keyring-backend test and also used the same in my command to start a validator or send some nhash. Both failed again with the same key not found issue. Where querying balance with my address still works as I had shown earlier.
$ provenanced keys show secure_key -t --keyring-backend test
- name: secure_key
  type: local
  address: tp1y7yhjnegfy86pctmva8helpf96dhua73fxq8pn
  pubkey: tppub1addwnpepq2k7rx5huv73r8ap4h3umk7a206uwv0x6lhv705tddev5dwk89t6w2wds54
  mnemonic: ""
  threshold: 0
  pubkeys: []

Noting my validator pub key:
$ provenanced --testnet tendermint show-validator --home $PIO_HOME
tpvalconspub1zcjduepqkrgu9k0p8dkvcma2uslhmpu6mdhf87etykwlfk456duy0hxtwqjq288jt3

Now both creating a validator or sending nhash fails even after specifying keyring-backend as test:
$ provenanced --testnet tx bank send  tp1y7yhjnegfy86pctmva8helpf96dhua73fxq8pn tp1qhutk7wuj96ufq96v2musp4gpqgphpzk37nq94 100000000nhash --fees 1000000000nhash --chain-id pio-testnet-1 --keyring-backend test --testnet --home $PIO_HOME
Error: rpc error: code = NotFound desc = account tp1y7yhjnegfy86pctmva8helpf96dhua73fxq8pn not found: key not found

$ provenanced  tx staking create-validator --moniker provenanced-node --pubkey tpvalconspub1zcjduepqkrgu9k0p8dkvcma2uslhmpu6mdhf87etykwlfk456duy0hxtwqjq288jt3  --commission-rate=1.0 --commission-max-rate=1.0 --commission-max-change-rate=1.0 --min-self-delegation=1 --from=secure_key --amount 65000nhash  -t --broadcast-mode block --keyring-backend test
Error: rpc error: code = NotFound desc = account tp1y7yhjnegfy86pctmva8helpf96dhua73fxq8pn not found: key not found

While I continue to try and debug this with your help, do you suggest me any alternate ways to create a validator? May be a container image which I can try and run as a validator in testnet network?
Thanks.

Hi @prabhanjangururaj , what is the result of the cmd provenanced keys show secure_key -t --keyring-backend test  --home $PIO_HOME, imo it will give you an  error
note this(from my mac may differ on your box)
     --home string              The application home directory (default "/Users/xxx/.provenanced")
     --keyring-backend string   Select keyring's backend (os|file|test) (default "test")
     --keyring-dir string       The client Keyring directory; if omitted, the default 'home' directory will be used```

tl;dr if you are defining home define the same when you do the key import `provenanced keys import name --home $PIO_HOME`

i.e when you import the keys you cannot say goto default `home` and then ask it to look at specific --home you specify

you can find the docker images here https://hub.docker.com/r/provenanceio/provenance

These guys can provide more help than I can, but testnet would take quite a long time to sync and catch up to the head state. It would be worthwhile to try your tx bank send attempt again with --node=tcp://rpc-0.test.provenance.io:26657 added just so you know the request is going to a node that's caught up and not behind at all.
I'm assuming here that if you submit to a local node that hasn't replicated to the block where that address existed and received hash, it would return the error you're seeing. This assumption could be totally wrong.

provenanced keys import name --home $PIO_HOME

Hi Arnab - this is the result of the command:
$ provenanced keys show secure_key -t --keyring-backend test --home $PIO_HOME
- name: secure_key
  type: local
  address: tp1y7yhjnegfy86pctmva8helpf96dhua73fxq8pn
  pubkey: tppub1addwnpepq2k7rx5huv73r8ap4h3umk7a206uwv0x6lhv705tddev5dwk89t6w2wds54
  mnemonic: ""
  threshold: 0
  pubkeys: []

Do you see any problem here?

--node=tcp://rpc-0.test.provenance.io:26657

Hi Stephen -
That made sense and here is what I observe now with tx send.  Thanks
$ provenanced --testnet tx bank send  tp1y7yhjnegfy86pctmva8helpf96dhua73fxq8pn tp1qhutk7wuj96ufq96v2musp4gpqgphpzk37nq94 100000000nhash --fees 1000000000nhash --chain-id pio-testnet-1 --keyring-backend test --testnet --home $PIO_HOME --node=tcp://rpc-0.test.provenance.io:26657
{"body":{"messages":[{"@type":"/cosmos.bank.v1beta1.MsgSend","from_address":"tp1y7yhjnegfy86pctmva8helpf96dhua73fxq8pn","to_address":"tp1qhutk7wuj96ufq96v2musp4gpqgphpzk37nq94","amount":[{"denom":"nhash","amount":"100000000"}]}],"memo":"","timeout_height":"0","extension_options":[],"non_critical_extension_options":[]},"auth_info":{"signer_infos":[],"fee":{"amount":[{"denom":"nhash","amount":"1000000000"}],"gas_limit":"200000","payer":"","granter":""}},"signatures":[]}

confirm transaction before signing and broadcasting [y/N]: y
{"height":"3367587","txhash":"3AC979A42DE93BDD407F848F5484646BDAFFD4FCD7AB7618D826429E94821790","codespace":"","code":0,"data":"0A060A0473656E64","raw_log":"[{\"events\":[{\"type\":\"message\",\"attributes\":[{\"key\":\"action\",\"value\":\"send\"},{\"key\":\"sender\",\"value\":\"tp1y7yhjnegfy86pctmva8helpf96dhua73fxq8pn\"},{\"key\":\"module\",\"value\":\"bank\"}]},{\"type\":\"transfer\",\"attributes\":[{\"key\":\"recipient\",\"value\":\"tp1qhutk7wuj96ufq96v2musp4gpqgphpzk37nq94\"},{\"key\":\"sender\",\"value\":\"tp1y7yhjnegfy86pctmva8helpf96dhua73fxq8pn\"},{\"key\":\"amount\",\"value\":\"100000000nhash\"}]}]}]","logs":[{"msg_index":0,"log":"","events":[{"type":"message","attributes":[{"key":"action","value":"send"},{"key":"sender","value":"tp1y7yhjnegfy86pctmva8helpf96dhua73fxq8pn"},{"key":"module","value":"bank"}]},{"type":"transfer","attributes":[{"key":"recipient","value":"tp1qhutk7wuj96ufq96v2musp4gpqgphpzk37nq94"},{"key":"sender","value":"tp1y7yhjnegfy86pctmva8helpf96dhua73fxq8pn"},{"key":"amount","value":"100000000nhash"}]}]}],"info":"","gas_wanted":"200000","gas_used":"154691","tx":null,"timestamp":""}

I wanted to have the sync complete and evaluate further, but the process crashed as below:
5:28AM INF ABCI Handshake App Info hash="0�;�1D\x18�\x03�O^�2\x02\u007f/\x19�t��S�\x15��\f���i" height=609072 module=consensus protocol-version=0 software-version=v1.7.0
5:28AM INF ABCI Replay Blocks appHeight=609072 module=consensus stateHeight=609072 storeHeight=609073
5:28AM INF Replay last block using real app module=consensus
Error: error during handshake: error on replay: wrong Block.Header.LastResultsHash.  Expected 567F1092207C8A52AA2E6CC4D697C4167B8815FABF07B9C88B6F2B7F9B1BD9F5, got 50F1D9F2DD2CD7971A4AFA9DF5D3B554C3050988247C9175994ADF131C69B182

I am right now on the latest version:
$ provenanced version
v1.7.0

Version of provenanced must match the version at a given blockheight. Neither testnet nor mainnet are running 1.7.0 at this time. If you are syncing from zero start with the genesis version and upgrade as instructed by the software at the required blockheights

Hi Ira - I moved to 1.7.0 hoping to resolve this, but hit this issue even at 1.0.0. Can you suggest ways to recover from here and continue syncing? As you had pointed, I started with 0.2.0, the genesis version initially.

You must match the version used when the block was cut... meaning you will need to transition through each version as your sync reaches the upgrade heights. 1.7.0 is not currently used in any public network (although testnet has an upgrade schedule to start minting blocks with it tomorrow).
Carefully review your output log for the upgrade needed statement which is output at the upgrade height. Alternatively use the cosmovisor setup (on our fork as the upstream version is broken) and it will help you manage these upgrades.

Hi Ira - I will initiate again as suggested.
I find a container to create a node on testnet here https://github.com/provenance-io/testnet/tree/main/docker. Have been running this without issues syncing close to a million blocks in the last 30hrs or so.
$ provenanced  --testnet q block | jq ".block.last_commit.height"
"939263"

The promotion to a validator node did happen now. Thanks all of you for your assistance so far:
https://explorer.test.provenance.io/validator/tp13f24k3zauhackjs6dqsj2zyvnf7zshmx32c0gq

authors: arnabmitra channa-figure iramiller prabhanjangururaj scirner22

repo: provenance-io/provenance


text:
下载速度一直为0

问题描述(必要)
下载速度一直为0
版本号(必要)
1.0
操作系统(必要)
mac os 10.13.6
相关截图

相关日志
无

Duplicate of #1075

repo: proxyee-down-org/proxyee-down


text:
preparation for application to the YJ band

Some instance variables have been added to treat YJ band or mmf1 (comb fiber) data. (See IRD_stream.py for usage.)
memo:
** The reduction process is NOT YET optimized for YJ band data.
**  The problem of setting the appropriate path for the data (e.g. the reference path of the master ThAr file) is NOT YET resolved.
The above things will be resolved in the future.

Thank you for your review! I made slight modifications.
Could you check it again? @HajimeKawahara  @kemasuda

Thanks for checking, looks good to me!

Thanks!

authors: HajimeKawahara YuiKasagi kemasuda

repo: prvjapan/pyird


text:
Plugin "PHP composer.json support" is incompatible (until build 202.0 < PS-202.6948.87).

Plugin is disabled with this message in event log (popup shown too)
09/09/2020
10:21	Plugin Error: Plugin "PHP composer.json support" is incompatible (until build 202.0 < PS-202.6948.87).

in PS version 202.6948.87 (2020-02.1 - current stable at this date)

It won't be updated. See https://github.com/psliwa/idea-composer-plugin/issues/93#issuecomment-642683958
So you can uninstall it.

authors: hluchas jgreth

repo: psliwa/idea-composer-plugin

license: mit


text:
add a schema for querying academic scores

schema "academic" can not run separately now, I used a warning and arbitaryly set the separate as FALSE when you set
schema = "academic" and separate = TRUE.

@Blockhead-yj Try using the latest unit test framework. Before your work, make sure this branch is rebased to develop branch. I think you'd better use git flow.

New logic is applied now. This PR is outdated.

Close because it is outdated.

authors: Blockhead-yj psychelzh


text:
[Problem Generator] Do not merge languages option with saved config

If user enters languages: e.g. javascript and the config already has ['javascript', 'python'], the config should replace the languages config. Instead, the config still preserves the non specified languages e.g. python . We should save last user's input for subsequent reruns.

31f09d81aeed30f6a4ad49de9c36e7f308811dd3

repo: psychobolt/generator-leetcode-storybook


text:
Add a function for getting the name of a request

Signed-off-by: Uli Schlachter psychon@znc.in

This is how far I got before noticing that #314 does not really work. Dunno if this should be merged or not.

[ ] TODO: It just occurred to me that this should use the generated constants instead of having just the plain number

whoops, I mistakenly checked the TODO checkbox (and then unchecked it again), just in case you get some notification about me modifying this PR

Nope, no notifications. :-)

Can this be closed?

Dunno. I still feel like this could be useful, but so far have not come across a case where I would be able to use this information. If #314 is not possible... well, I guess then this should be closed. Do you agree that #314 is not possible and that the addition in this PR is not useful?

If #314 is not possible, I cannot think of any other use of this right now. Anyways, this is right now written for the old python generator, so if someday we want this, it would need to be done from scratch.

authors: eduardosm psychon


text:
Lazy set operations

The standard library collections defines set operations in a lazy manner. Is it possible to define lazy iterators for interval and interval_set?
Also this library should be coherent with the decisions taken on std. The collections library is not mature yet, so we'll wait further developpement.

This issue has been transferred to https://github.com/ptal/gcollections/issues/2

repo: ptal/intervallum


text:
Vitual binary switches/sensors?

Could it be a possible feature in the future, that UART commands could define Zigbee switches/buttons?
This way outside of Z2M, the device is presenting zigbee switches for commands defined in the firmware.
I'm trying to recreate this but in zigbee with cc2530.
The device has an Rs232 port and I communicate fine with it, but it'd be nice if the device could present each command as a switch.

Hello,
This feature requires a dedicated firmware. You may add an Arduino in the middle that will convert the UART protocol to output states. You may connect these outputs with inputs on CC2530.

authors: Ruxton ptvoinfo

repo: ptvoinfo/zigbee-configurable-firmware


text:
only one ds18b20 sensor?

Hello everyone,
I use espeasy on an esp32 to read 10 ds18b20 sensors.

Since the WiFi is very bad, I wanted to use Zigbee.
(Zigbee network already exists)
I use this Zigbee device: (CC2531)

I get the 5V power and ground for the sensors from the USB pin.
and the following configuration:
[Common]
Left=-1230
Top=317
Width=1129
Board=5
Device type=1
LED active=True
LED inverted=False
Pin LED=P00
LED mode=2
Pin active 1=True
Pin No 1=P02
Pin Type 1=7
Pull Type 1=0
Pin inversed 1=False
StatechkState_1=True
Pin active 2=True
Pin No 2=P02
Pin Type 2=7
Pull Type 2=0
Pin inversed 2=False
StatechkState_2=True
Pin active 3=True
Pin No 3=P02
Pin Type 3=7
Pull Type 3=0
Pin inversed 3=False
StatechkState_3=True
Pin active 4=True
Pin No 4=P02
Pin Type 4=7
Pull Type 4=0
Pin inversed 4=False
StatechkState_4=True
Pin active 5=True
Pin No 5=P02
Pin Type 5=7
Pull Type 5=0
Pin inversed 5=False
StatechkState_5=True
Pin active 6=True
Pin No 6=P02
Pin Type 6=7
Pull Type 6=0
Pin inversed 6=False
StatechkState_6=True
Pin active 7=True
Pin No 7=P02
Pin Type 7=7
Pull Type 7=0
Pin inversed 7=False
StatechkState_7=True
Pin active 8=True
Pin No 8=P02
Pin Type 8=7
Pull Type 8=0
Pin inversed 8=False
StatechkState_8=True
Pin active 9=False
Pin No 9=
Pin Type 9=0
Pull Type 9=0
Pin inversed 9=False
StatechkState_9=True
Pin active 10=False
Pin No 10=
Pin Type 10=0
Pull Type 10=0
Pin inversed 10=False
StatechkState_10=True
Pin active 11=False
Pin No 11=
Pin Type 11=0
Pull Type 11=0
Pin inversed 11=False
StatechkState_11=True
Pin active 12=False
Pin No 12=
Pin Type 12=0
Pull Type 12=0
Pin inversed 12=False
StatechkState_12=True
Pin active 13=False
Pin No 13=
Pin Type 13=0
Pull Type 13=0
Pin inversed 13=False
StatechkState_13=True
Pin active 14=False
Pin No 14=
Pin Type 14=0
Pull Type 14=0
Pin inversed 14=False
StatechkState_14=True
Pin active 15=False
Pin No 15=
Pin Type 15=0
Pull Type 15=0
Pin inversed 15=False
StatechkState_15=True
Pin active 16=False
Pin No 16=
Pin Type 16=0
Pull Type 16=0
Pin inversed 16=False
StatechkState_16=True
Pin active 17=False
Pin No 17=
Pin Type 17=0
Pull Type 17=0
Pin inversed 17=False
LinkchkLink_17=True
SwitchchkSwitch_17=False
HoldchkHold_17=False
DoublechkDouble_17=False
TripplechkTripple_17=False
Bind type 17=0
Pin active 18=False
Pin No 18=
Pin Type 18=0
Pull Type 18=0
Pin inversed 18=False
LinkchkLink_18=True
SwitchchkSwitch_18=False
HoldchkHold_18=False
DoublechkDouble_18=False
TripplechkTripple_18=False
Bind type 18=0
Pin active 19=False
Pin No 19=
Pin Type 19=0
Pull Type 19=0
Pin inversed 19=False
LinkchkLink_19=True
SwitchchkSwitch_19=False
HoldchkHold_19=False
DoublechkDouble_19=False
TripplechkTripple_19=False
Bind type 19=0
Pin active 20=False
Pin No 20=
Pin Type 20=0
Pull Type 20=0
Pin inversed 20=False
LinkchkLink_20=True
SwitchchkSwitch_20=False
HoldchkHold_20=False
DoublechkDouble_20=False
TripplechkTripple_20=False
Bind type 20=0
Pin active 21=False
Pin No 21=
Pin Type 21=0
Pull Type 21=0
Pin inversed 21=False
LinkchkLink_21=True
SwitchchkSwitch_21=False
HoldchkHold_21=False
DoublechkDouble_21=False
TripplechkTripple_21=False
Bind type 21=0
Pin active 22=False
Pin No 22=
Pin Type 22=0
Pull Type 22=0
Pin inversed 22=False
LinkchkLink_22=True
SwitchchkSwitch_22=False
HoldchkHold_22=False
DoublechkDouble_22=False
TripplechkTripple_22=False
Bind type 22=0
Pin active 23=False
Pin No 23=
Pin Type 23=0
Pull Type 23=0
Pin inversed 23=False
LinkchkLink_23=True
SwitchchkSwitch_23=False
HoldchkHold_23=False
DoublechkDouble_23=False
TripplechkTripple_23=False
Bind type 23=0
Pin active 24=False
Pin No 24=
Pin Type 24=0
Pull Type 24=0
Pin inversed 24=False
LinkchkLink_24=True
SwitchchkSwitch_24=False
HoldchkHold_24=False
DoublechkDouble_24=False
TripplechkTripple_24=False
Bind type 24=0
Pin active 25=False
Pin No 25=
Pin Type 25=0
Pull Type 25=0
Pin inversed 25=False
LinkchkLink_25=True
SwitchchkSwitch_25=False
HoldchkHold_25=False
DoublechkDouble_25=False
TripplechkTripple_25=False
Bind type 25=0
Pin active 26=False
Pin No 26=
Pin Type 26=0
Pull Type 26=0
Pin inversed 26=False
LinkchkLink_26=True
SwitchchkSwitch_26=False
HoldchkHold_26=False
DoublechkDouble_26=False
TripplechkTripple_26=False
Bind type 26=0
Pin active 27=False
Pin No 27=
Pin Type 27=0
Pull Type 27=0
Pin inversed 27=False
LinkchkLink_27=True
SwitchchkSwitch_27=False
HoldchkHold_27=False
DoublechkDouble_27=False
TripplechkTripple_27=False
Bind type 27=0
Pin active 28=False
Pin No 28=
Pin Type 28=0
Pull Type 28=0
Pin inversed 28=False
LinkchkLink_28=True
SwitchchkSwitch_28=False
HoldchkHold_28=False
DoublechkDouble_28=False
TripplechkTripple_28=False
Bind type 28=0
Pin active 29=False
Pin No 29=
Pin Type 29=0
Pull Type 29=0
Pin inversed 29=False
LinkchkLink_29=True
SwitchchkSwitch_29=False
HoldchkHold_29=False
DoublechkDouble_29=False
TripplechkTripple_29=False
Bind type 29=0
Pin active 30=False
Pin No 30=
Pin Type 30=0
Pull Type 30=0
Pin inversed 30=False
LinkchkLink_30=True
SwitchchkSwitch_30=False
HoldchkHold_30=False
DoublechkDouble_30=False
TripplechkTripple_30=False
Bind type 30=0
Pin active 31=False
Pin No 31=
Pin Type 31=0
Pull Type 31=0
Pin inversed 31=False
LinkchkLink_31=True
SwitchchkSwitch_31=False
HoldchkHold_31=False
DoublechkDouble_31=False
TripplechkTripple_31=False
Bind type 31=0
Pin active 32=False
Pin No 32=
Pin Type 32=0
Pull Type 32=0
Pin inversed 32=False
LinkchkLink_32=True
SwitchchkSwitch_32=False
HoldchkHold_32=False
DoublechkDouble_32=False
TripplechkTripple_32=False
Bind type 32=0
Param1_1=28-af-4a-75-d0-01-3c-db
Param2_1=
Param3_1=
Param4_1=
Param5_1=
Param6_1=
Param7_1=
Param1_2=28-de-f4-75-d0-01-3c-99
Param2_2=
Param3_2=
Param4_2=
Param5_2=
Param6_2=
Param7_2=
Param1_3=28-4a-00-75-d0-01-3c-4d
Param2_3=
Param3_3=
Param4_3=
Param5_3=
Param6_3=
Param7_3=
Param1_4=28-e4-b2-75-d0-01-3c-ce
Param2_4=
Param3_4=
Param4_4=
Param5_4=
Param6_4=
Param7_4=
Param1_5=28-53-e7-75-d0-01-3c-0b
Param2_5=
Param3_5=
Param4_5=
Param5_5=
Param6_5=
Param7_5=
Param1_6=28-27-19-75-d0-01-3c-4b
Param2_6=
Param3_6=
Param4_6=
Param5_6=
Param6_6=
Param7_6=
Param1_7=28-ae-fe-75-d0-01-3c-bc
Param2_7=
Param3_7=
Param4_7=
Param5_7=
Param6_7=
Param7_7=
Param1_8=28-fe-20-75-d0-01-3c-6e
Param2_8=
Param3_8=
Param4_8=
Param5_8=
Param6_8=
Param7_8=
Param1_9=
Param2_9=
Param3_9=
Param4_9=
Param5_9=
Param6_9=
Param7_9=
Param1_10=
Param2_10=
Param3_10=
Param4_10=
Param5_10=
Param6_10=
Param7_10=
Param1_11=
Param2_11=
Param3_11=
Param4_11=
Param5_11=
Param6_11=
Param7_11=
Param1_12=
Param2_12=
Param3_12=
Param4_12=
Param5_12=
Param6_12=
Param7_12=
Param1_13=
Param2_13=
Param3_13=
Param4_13=
Param5_13=
Param6_13=
Param7_13=
Param1_14=
Param2_14=
Param3_14=
Param4_14=
Param5_14=
Param6_14=
Param7_14=
Param1_15=
Param2_15=
Param3_15=
Param4_15=
Param5_15=
Param6_15=
Param7_15=
Param1_16=
Param2_16=
Param3_16=
Param4_16=
Param5_16=
Param6_16=
Param7_16=

[Expert]
ManufacturerIdEn=False
ManufacturerId=64447
ManufacturerNameEn=False
ManufacturerName=ptvo.info
ModelIdEn=False
ModelId=ptvo.switch
Icon enabled=False
Icon=
LocationDescriptionEn=False
LocationDescription=
LinkKeyEn=False
LinkKey=01030507090B0D0F00020406080A0C0D
ReportIntEn=True
ReportInt=10
Disable report interval config=False
DateCode=False
WatchDog=True
PSM mode wait commands=False
PSM mode net poll enabled=False
PSM mode net poll interval=0
Disable reset=False

[PA]
TX EN=
RX EN=

[Expert.SBL]
Enabled=False
Pin=

[Expert.OTA]
MOSI=
MISO=
CLK=
CS=

However, I don't get any values:
{"type":"readResponse","data":{},"linkquality":51,"groupID":0,"cluster":"genOnOff","meta":{"zclTransactionSequenceNumber":216,"manufacturerCode":null,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

If I don't specify a ds18b20 id, then I only get a temperature value:
{"type":"attributeReport","data":{"presentValue":22.75,"description":"C,28-2B-16-75-D0-01-3C-59"},"linkquality":47,"groupID":0,"cluster":"genAnalogInput","meta":{"zclTransactionSequenceNumber":139,"manufacturerCode":null,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

It should all be listed here, right?
Did I miss something?
Thanks for the great project and greetings
mark
Originally posted by @MarkStephan89 in https://github.com/ptvoinfo/zigbee-configurable-firmware/discussions/246

@MarkStephan89 You should get a separate similar "attributeReport" for each of the sensors. I've checked your configuratio with two DS18B20 and it works as expected. Could you try with two sensors too?

Hi @ptvoinfo
if I only connect one sensor then it works. :)
I will test it again with several sensors.
Question: can I use the internal resistor or do I absolutely need the external resistor?
Thanks!

it is working :)
I reflash the firmware and now it is working :)
Question:
I have 10 DS18B20.
The limit is 8 sensors per pin.
Can I use 2 pins and 5 x ds18b20 on each pin in the free version?
Many thanks!

No, it is the total limit of sensors (in the Premium version too). You'll need to make two devices and split sensors between them.

thank you


text:
Added Romanian Jokes API

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

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

@tutyamxx thanks for your contribution!
Closing this PR - the link doesn't work.

It does work, but it is listed on free heroku hours. Every last 2 days of the month is stops do to hours.

authors: marekdano tutyamxx

repo: public-apis/public-apis


text:
Added Sentim-API, a free API for sentiment analysis

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

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

Fixed Now

Can It be merged now ?

Thank you

@sharadcodes down already?

It's up, dyno hours were exhausted, apologizes for inconvenience

authors: sharadcodes wobsoriano yannbertrand


text:
Pls accept my changes

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

Why do you make this change ? It doesn't seem to make any sense


text:
Mieux documenter le mécanisme "référence circulaire"

Je suis tombé sur ce cas d'usage
https://publi.codes/studio/travaux-plafonnés#travaux%3A %0A%20 formule%3A invest %2B aide %0A%20 résoudre la référence circulaire%3A oui%0A%0Aaide%3A p * travaux plafonnés%0A%0Ainvest%3A 20000%0A%23 tester avec la valeur 10000 sans le paramètre `...circulaire` sur%0A%23 ou avec 13000 sans circulaire sur travaux plafonnés %0A%0Ap%3A 45%25%0A%0Atravaux plafonnés%3A %0A%20 plafond%3A 40000%0A%20 valeur%3A travaux%0A%20 résoudre la référence circulaire%3A oui

Alors d'une, le mécanisme est super utile. Mais de deux, j'étais surpris qu'il me faille ici deux inscriptions du mécanisme pour que ça marche.
Si ce comportement est correct, je pense qu'il faut l'expliquer et donner cet exemple simple (mais réel, on parle des aides rénov 2024) dans la doc, je peux m'en charger après confirmation.
De trois, je pense qu'il faut documenter la différence entre référence circulaire et inversion numérique. Ayant codé la première version de l'inversion, je n'arrive pas personnellement à comprendre la différence, alors je pense que le nouvel utilisateur sera lui aussi perdu.
https://publi.codes/docs/api/mécanismes#inversion-numérique

Erreur de ma part, l'exemple publicode donné plus haut ne fonctionne pas même avec deux références circulaire : l'aide n'est plus calculée au-dessus de 20 k€.

Pour mon deuxième point, l'inversion numérique, à vrai dire je ne sais même pas la déclencher dans le studio.
Peut-être car la valeur de "brut" doit être saisie dans la situation, ce qui n'est pas possible dans le studio ?
https://publi.codes/studio/brut#net%3A %0A%20 formule%3A brut * 0.8%0A%20 par défaut%3A 1200%0A%0Abrut%3A%0A%20 inversion numérique%3A %0A%20%20%20 - net%0A

Je crois que le problème est dû au plafond de l'aide. Cela aboutit a plusieurs valeurs de travaux possible ce qui casse la résolution.
Voir la version qui marche sans plafond

Au temps pour moi je crois que j'ai réussi à le faire fonctionner y compris avec plafond :
Voir la version qui marche avec plafond

Le tout est de trouver la bonne valeur pivot à partir de laquelle résoudre l'équation. Je suis d'accord sur le manque de documentation. On pourrait même envisager la rédaction d'un guide dédié aux mécanismes inversion numérique et résoudre la référence circulaire.

@johangirod je crois que dans ton exemple, ça ne marche à 11000 d'invest, mais pas de 12000 à 22000, puis ça remarche à 23000. J'ai du mal à comprendre pourquoi. En effet c'est une histoire de plafond.

C'est comme si le plafond faisait diverger le calcul circulaire... alors qu'il ne me semble pas y avoir de raison pour ça...
https://publi.codes/studio/t#travaux%3A %0A%20 valeur%3A invest %2B aide%0A%20 résoudre la référence circulaire%3A oui%0A%0A%0Aaide%3A %0A%20 produit%3A %0A%20%20%20 - valeur%3A travaux%0A%20%20%20%20%20 plafond%3A 40000%0A%20%20%20 - 0.45%0A%0A%0Ainvest%3A 12000%0A%23 tester avec la valeur 11922 sans le paramètre `...circulaire` sur%0A%23 ou avec 11923 sans circulaire sur travaux plafonnés %0A%0At%3A 12000 %2F (1 - 0.45)

À confirmer, mais cette version là, inversée par mes soins (j'ai trois doctorats en sciences) semble fonctionner pour toutes les valeurs (sans référence circulaire donc) :
https://publi.codes/studio/travaux#travaux%3A invest %2F (1 - p)%0A%0A%0Aaide%3A p * travaux plafonnés%0A%0Ap%3A 0.45%0A%0Atravaux plafonnés%3A%0A%20 plafond%3A 40000%0A%20 valeur%3A travaux%0A%20%20%20 %0A%0Ainvest%3A 15000%0A%23 tester avec la valeur 11922 sans le paramètre `...circulaire` sur%0A%23 ou avec 11923 sans circulaire sur travaux plafonnés %0A

Ah oui c'est très chelou. Il y a clairement un bug, ou un comportement non spécifié. Si je devais faire une hypothèse, ce pourrait être dû aux valeurs initiales de l'algo. Dans un cas, elles font converger le calcul car les valeurs testées par l'algo sont en dessous du plafond, et diverge dans l'autre cas avec des valeurs au-dessus du plafond.
Mais c'est une hypothèse à tester et à raffiner.
https://github.com/publicodes/publicodes/blob/master/packages/core/src/mecanisms/résoudre-référence-circulaire.ts#L59-L82

Mmmh, sauf que tu perd le plafonnement de l'aide dans le calcul de travaux justement ?

Ah bah oui bien vu.

authors: johangirod laem

repo: publicodes/publicodes


text:
LOAD_EX in multiple services

Hi @puckel,
I just noticed that it is suggested to uncomment LOAD_EX=n in two services both inside docker-compose-CeleryExecutor.yml and docker-compose-LocalExecutor.yml. Is it how it is supposed to be? I'd intuitively expect this ENV variable to be needed only once because I don't think that more than one service can be responsible for adding extra DAGs. How about removing an extra occurrence of  LOAD_EX=n if not needed?
Thanks a lot for crafting the docker recipe for airflow - sooo cool to be able to launch airflow in under a minute without any preps!

Hi,
I've tried both options, the dags examples are loaded when the option is activated in webserver or scheduler

authors: kachkaev puckel

repo: puckel/docker-airflow


text:
Dependency updates for ingest

Fixes #732

The tests pass for me locally, but CircleCI errors (because it runs out of RAM?)

Coverage decreased (-0.03%) to 99.965% when pulling d8ff456a675e486aa4a9861867f1f5f2cee35155 on update-cc into fc12b879fbfedad2ddaf91c850c4f428271538f1 on master.

The build passes with the Jasmine tests disabled.  And I found an old bug about PhantomJS memory usage in CircleCI: https://discuss.circleci.com/t/phantomjs-2-memory-consumption-problem/4710.
So I'll start looking at what we can do to reduce the memory footprint of those tests.

Coverage decreased (-0.03%) to 99.965% when pulling a30637f285b8412671bb89fb0c5eef0d3f491f9f on update-cc into fc12b879fbfedad2ddaf91c850c4f428271538f1 on master.

Coverage decreased (-0.03%) to 99.965% when pulling 1b72f4ee6f861ac384ee885e5847f1772ee461ea on update-cc into fc12b879fbfedad2ddaf91c850c4f428271538f1 on master.

Coverage remained the same at 100.0% when pulling 9648bfa7d6176a54dd2b41453df7cc5b39ce71e0 on update-cc into fc12b879fbfedad2ddaf91c850c4f428271538f1 on master.

:tada:

authors: coveralls escowles jpstroop

repo: pulibrary/plum


text:
Mac DNS resolution failing CGO_ENABLED=0 for macos

What happened?
Hi I have a DNS resolution problem on my Mac (M1) with pulumi AWS provider
I keep getting error
 1 error occurred:
    	* error reading EC2 VPC (vpc-0f364d0fbd5be0015) ClassicLinkDnsSupported: RequestError: send request failed
    caused by: Post "https://ec2.eu-central-1.amazonaws.com/": dial tcp: lookup ec2.eu-central-1.amazonaws.com on 192.168.168.254:53: no such host

My DNS servers are coming from DHCP server (my router):
nameserver 192.168.168.254
nameserver 213.75.63.75
nameserver 213.75.63.76

When I set my DNS server to 213.75.63.75 pulumi then starts working
I suspect it is the same case as these issues
https://github.com/hashicorp/terraform/issues/3536
https://github.com/hashicorp/terraform-provider-kubernetes/issues/969
Steps to reproduce
n/a
Expected Behavior
no dns problems
Actual Behavior
dns is not resolving
Output of pulumi about
5.16.2
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Perhaps someone can help me modify my fork to build the binary I can test https://github.com/jans-forks/pulumi-aws/actions/runs/3288534376/jobs/5418989775

Hi @1oglop1 - you should be able to build your own provider locally, running make provider.
As for the resolution failure, we're not certain it's an M1 issue specifically, but rather a result of an upstream Golang resolver issue and as such we have very limited options to address this here.

The linked upstream issue was fixed.

repo: pulumi/pulumi-aws


text:
"unable to validate AWS credentials" when setting AWS profile via Pulumi config

What happened?
Up until now we have used env vars to set and use the default AWS provider:
export AWS_REGION=xx-xxx-x
export AWS_PROFILE=yyyyy

Now i am trying to use the Pulumi config instead of env vars, so i've added the following settings to the stack's pulumi config:
config:
  aws:profile: yyyyy
  aws:region: xx-xxx-x

Now i am getting the following errors:
error: unable to validate AWS credentials.
    Details: no valid credential sources for  found.

    Please see
    for more information about providing credentials.

    Error: failed to refresh cached credentials, no EC2 IMDS role found, operation error ec2imds: GetMetadata, http response error StatusCode: 404, request to EC2 IMDS failed

    Make sure you have:

     	 • Set your AWS region, e.g. `pulumi config set aws:region us-west-2`
     	 • Configured your AWS credentials as per https://pulumi.io/install/aws.html
     	 You can also set these via cli using `aws configure`.

I tried to add skipCredentialsValidation: true and skipMetadataApiCheck: false but getting the same result.
Expected Behavior
Should work with pulumi config the same as it worked with the env vars
Steps to reproduce
Use a simple AWS project without setting an explicit AWS provider (using the default one) and setting region and profile with env vars. Then remove env var and set region and profile using pulumi config.
Output of pulumi about
➜  ~ pulumi about
CLI
Version      3.49.0
Go Version   go1.19.3
Go Compiler  gc
Plugins
NAME        VERSION
aws         5.24.0
aws         5.24.0
cloudflare  3.6.0
cloudflare  3.3.0
datadog     3.3.0
datadog     3.3.0
docker      3.6.1
docker      3.0.0
kafka       3.4.0
kafka       3.0.1
kubernetes  3.6.0
kubernetes  3.6.0
mysql       3.1.0
mysql       3.0.0
nodejs      unknown
okta        3.17.0
okta        3.0.0
pagerduty   2.2.0
pagerduty   2.1.1
postgresql  3.6.0
postgresql  3.6.0
rabbitmq    3.2.0
rabbitmq    3.0.0
random      4.10.0
random      4.2.0
spotinst    3.8.0
spotinst    3.8.0
tls         4.8.0
tls         4.0.0
Host
OS       amazon
Version  2
Arch     x86_64
This project is written in nodejs: executable='~/.nvm/versions/node/v14.21.0/bin/node' version='v14.21.0'
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Hi @jasminen, following up on our conversation in Slack here. I tried to reproduce this with a new program and a new stack (via pulumi new aws-go), but wasn't able to. My terminal session is below.
I did go down a rabbit hole for a bit because I tried to repro it with a program using an explicit provider, and there seems to be something wrong there. However, you say you're using the default provider.
As a next step, are you able to add some debug output to this issue? Via pulumi preview --logtostderr --logflow -v=9 2> out.txt.
$ pulumi preview
Diagnostics:
  aws:s3:Bucket (my-bucket):
    error: unable to validate AWS credentials.
    Details: no valid credential sources for  found.
...

$ export AWS_PROFILE=AdministratorAccess-616138583583
$ export AWS_REGION=us-west-2

$ pulumi preview

     Type                 Name                   Plan
 +   pulumi:pulumi:Stack  repro-aws-creds-2-dev  create
 +   └─ aws:s3:Bucket     my-bucket              create

Outputs:
    bucketName: output<string>

Resources:
    + 2 to create

$ pulumi config set aws:profile AdministratorAccess-616138583583

$ pulumi config set aws:region us-west-2

$ unset AWS_PROFILE

$ unset AWS_REGION

$ export -p | rg AWS

$ pulumi preview

     Type                 Name                   Plan
 +   pulumi:pulumi:Stack  repro-aws-creds-2-dev  create
 +   └─ aws:s3:Bucket     my-bucket              create

Outputs:
    bucketName: output<string>

Resources:
    + 2 to create

Hey @jasminen! Did you get a chance to take another look at this issue?

Side issue (but possibly relevant): what's up with the missing value in
Details: no valid credential sources for  found.

@thomas11 same issue here, we are using this set of ENVs in CI to assume roles through profiles:
AWS_PROFILE: <PROFILE_NAME>
AWS_SDK_LOAD_CONFIG: "true"
AWS_CONFIG_FILE=<PATH_TO_CUSTOM_AWS_CONFIG>

Configs:
skipCredentialsValidation: "true"
skipMetadataApiCheck: "false"

Error:
Error: failed to refresh cached credentials, operation error STS: AssumeRole, failed to sign request: failed to retrieve credentials: failed to refresh cached credentials, no EC2 IMDS role found, operation error ec2imds: GetMetadata, expect HTTP transport, got <nil>

Side issue (but possibly relevant): what's up with the missing value in
Details: no valid credential sources for  found.

Fixed in #2367, but not related to this issue, unfortunately.

Hi @SharpEdgeMarshall , I tried to reproduce a few basic scenarios, like setting AWS_PROFILE and in the code creating a provider with a different profile:
		provider, err := aws.NewProvider(ctx, "provider", &aws.ProviderArgs{
			Profile: pulumi.StringPtr("accesskey"),
			Region:  pulumi.StringPtr("us-west-2"),
		})

Everything worked for me. Could you give me more information about your scenario, ideally some sample code to reproduce it?

Hi @jasminen, since I cannot reproduce the issue, I'll close it soon. Did you get a chance to look at this again?

@thomas11 Are you testing it on an AWS instance with an instance profile?

@SharpEdgeMarshall no, should I?
Can you share a code snippet of how exactly you're creating the explicit provider?

@thomas11 I have a theory that this is something to do with how default providers are resolved. Digging around the code for aws.Provider, it seems that if nothing is supplied for say region, it falls back to env variables. It probably first needs to fallback to the configured aws:region, and similarly for profile.
While I'm here I could also ask something else goofy about providers: why cant I feed string to Region attribute unless it's set explicitly in the options. For example it doesn't like this:
    import { getConfig } from "@pulumi/pulumi/runtime/config";

    const defaultProvider = new aws.Provider(`${stack}-${connection.id}-peer-provider`, {
        region: getConfig("aws:region"),
        profile: "sparkhire_prod"
    });

I'm basically blocked no matter what I do because even if I feed a default provider manually, I cant simply config it via the raw aws:region. I'm not really a typescript expert so if there's a workaround for this that would be great.

Hi @throttlehead-dev, this is actually as intended, although I do agree that it could be documented more clearly. See here:

Configuration file settings are only used by the default provider. If you instantiate a provider object, it will not read values from the stack configuration.

Since I wasn't able to reproduce the issue and some of the commenters didn't follow up so far, I'll close this issue. Feel free to reopen it if you still think Pulumi has a problem here.

Hey there, I'd like to reopen this.
I'm experiencing this with pulumi-3.111.0 and pulumi-aws-5.43.0
We're generating ~/.aws/credentials in our CI pipeline, then running a pulumi refresh.
When setting aws:profile: some-account it fails with
error: Preview failed: unable to validate AWS credentials.
    Details: no valid credential sources for  found.

    Please see
    for more information about providing credentials.

    Error: failed to refresh cached credentials, no EC2 IMDS role found, operation error ec2imds: GetMetadata, request send failed, Get "http://169.254.169.254/latest/meta-data/iam/security-credentials/": dial tcp 169.254.169.254:80: i/o timeout

but when setting the env var AWS_PROFILE it works fine.

authors: SharpEdgeMarshall jasminen squaremo thomas11 throttlehead-dev timbrammer910


text:
pulumi up is failing with insufficient logging

When deploying a stack, I'm getting a failure, but the logs aren't giving enough information to track down the issue. Also, if I rerun pulumi up one or two more times, it will succeed.
Expected Behavior
I get some indication of what went wrong, like the status code and any returned message
Current Behavior
I get the error status code and any message returned.
Steps to Reproduce

Create a resource group
Run pulumi up --skip-preview -v=3 --logtostderr
Get a failure with insufficient information

I1210 16:50:54.282491    2892 eventsink.go:59] Invoking function: token=azure-nextgen:resources/latest:getResourceGroup async +   pulumi:pulumi:Stack  AppServiceWebApp-aswadev  creating.    'dotnet build -nologo .' completed successfully
I1210 16:50:54.290488    2892 eventsink.go:59] Invoke RPC prepared: token=azure-nextgen:resources/latest:getResourceGroup
I1210 16:50:54.312492    2892 eventsink.go:59] Prepared resource: t=pulumi:pulumi:Stack, name=AppServiceWebApp-aswadev, custom=False, remote=False
Type                                           Name                      Status                  Info

pulumi:pulumi:Stack                            AppServiceWebApp-aswadev  creating...             'dotnet build -nologo
├─ azure-nextgen:web/v20180201:WebApp          siteResource              creating failed     error: autorest/az
├─ azure-nextgen:insights/v20150501:Component  componentResource         created
└─ azure-nextgen:web/v20180201:AppServicePlan  serverfarmResource        creating..
I1210 16:51:04.550530    2892 eventsink.go:59] Fields to assign: ["type","ingestionMode","provisioningState","hockeyAppId","retentionInDays","tags","appId","samplingPercentage","flowType","kind","id","immediatePurgeDataOn30Days","requestSource","urn","disableIpMasking","tenantId","instrumentationKey","name","creationDate","applicationType","connectionString","privateLinkScopedResources","hockeyAppToken","applicationId","location"]
pulumi:pulumi:Stack                            AppServiceWebApp-aswadev  creating...             error: update failed
=componentResource, custom=True, remote=False
I1210 16:51:04.564534    2892 eventsink.go:59] Preparing resource: t=azure-nextgen:insights/v20150501:Component, name=compone +   └─ azure-nextgen:web/v20180201:AppServicePlan  serverfarmResource        created
I1210 16:51:08.469863    2892 eventsink.go:59] Fields to assign: ["type","provisioningState","tags","isSpot","reserved","sku","kind","freeOfferExpirationTime","id","numberOfSites","hostingEnvironmentProfile","geoRegion","perSiteScaling","workerTierName","maximumElasticWorkerCount","status","maximumNumberOfWorkers","spotExpirationTime","targetWorkerCount","urn","targetWorkerSizeId","isXenon","name","subscription","resourceGroup","hyperV","location"]
I1210 16:51:08.474858    2892 eventsink.go:59] Registering resource start: t=azure-nextgen:web/v20180201:AppServicePlan, name=serverfarmResource, custom=True, remote=False
I1210 16:51:08.481877    2892 eventsink.go:59] Preparing resource: t=azure-nextgen:web/v20180201:AppServicePlan, name=serverfarmResource, custom=True, remote=False
I1210 16:51:08.502875    2892 ignore.go:44] Explicitly ignoring and discarding error: rpc error: code = Canceled desc = grpc: +   pulumi:pulumi:Stack                            AppServiceWebApp-aswadev  creating failed     1 error
├─ azure-nextgen:web/v20180201:WebApp          siteResource              creating failed     1 error

TerminateProcess: Access is denied.
Diagnostics:
azure-nextgen:web/v20180201:WebApp (siteResource):
error: autorest/azure: Service returned an error. Status=
pulumi:pulumi:Stack (AppServiceWebApp-aswadev):
error: update failed

Context (Environment)

Windows 10
Pulumi CLI v2.15.4
Nuget packages: Pulumi.AzureNextGen 0.* (resolving to 2.8)

Service returned an error. Status=

This is literally the response from Azure. App Service is famous for those. A way to troubleshoot is to look into the activity log of that resource.

This is literally the response from Azure. App Service is famous for those. A way to troubleshoot is to look into the activity log of that resource.

Yeah that rings a bell now that you mention it. Do you recall if we cut an azure ticket associated with this?

Do you recall if we cut an azure ticket associated with this?

I don't think we did. We may create a repro and file a ticket - but this behavior is there for years - so I wouldn't hold my breath.

authors: MisinformedDNA mikhailshilkov viveklak

repo: pulumi/pulumi-azure-nextgen