text:
Protected Admin route added

Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
@pooranjoyb
[Feature] Add login before access admin panel #334
Fixes #334 (issue)
Type of change
Please give a X on it which is applicable

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Refactor Code
[ ] A documentation update
[ ] Others(mentioned in the issue number)

How Has This Been Tested?
try to navigate /admin route
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Test A Describe here
Test B Describe here (if Requred)
Screenshots and Videos:

it take username and password for admin login
username : admin
password: Admin@123
Give screenshots and video of the changes you made
Checklist:
Give a X on, which is applicable

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

@pooranjoyb
kindly check this and merge it

@pooranjoyb
kindly please review it
if you need any modification please inform me

@pooranjoyb
i created protected route for admin page
kindly please review it and merge it

@pooranjoyb
i created protected route for admin page kindly please review it and merge it

Hey I can see there are some issues.

Add a link similar to this like, Login as Admin here below the Don't you have an account?

Remove this in Admin Login
Add a Logout button similar to the one you created in Profile page in Admin Dashboard in the sidebar.
It should clear the state and redirect user back to /admin route

@dhruv8433

@pooranjoyb
i updated my code and make it same as you said
if you think my code is good enought to get level 3 please assign it
https://github.com/user-attachments/assets/4c92c549-2f03-473d-86f6-9377d5903c9d

@pooranjoyb
i updated my code and make it same as you said
if you think my code is good enought to get level 3 please assign it

@pooranjoyb
i updated my code and make it same as you said
if you think my code is good enought to get level 3 please assign it

@pooranjoyb
please response
i request you kindly check this and merge it

Hii @dhruv8433 i am travelling today will review and merge tomorrow.

ok thank you for response

@pooranjoyb
when you become free, please check this and merge it


text:
可惜了

这么好用的工具，作者不怎么维护了，可惜了

最近发现clone不下来仓库了

我一直在用，没遇到 clone 问题。有问题就带问题提 issue 或者找到问题提 PR 啊。

具体的问题是？

抱歉抱歉，是我网络的问题

source: gharchive/issue

authors: atian25 dzhmoper popomore

repo: popomore/projj

license: mit

license_type: permissive

license_source: bigquery


text:
Express  support?

will edge support Express?

@fanybook I needed this too and ended up creating an Express wrapper.
It even overrides the render function to that you can reference your views with dot notation.
➡ https://github.com/ecrmnn/express-edge

authors: ecrmnn fanybook

repo: poppinss/edge


text:
[canvas] object

much like what I proposed for vanilla...
it could have [canvas name] - [canvas wname] - [canvas mouse], maybe even inlcude 'properties'/'click'

dollar

iohannes canvas def

repo: porres/pd-else

license: WTFPL

license_source: github-api


text:
--admin-password-file does not set up admin user correctly

Bug description
Specifying the --admin-password-file option logs a message that it creates an admin user with a calculated password hash, but the plain-text password in the given file doesn't work on the login page.
Consider this docker-compose config file:
version: "3.7"
services:
  portainer:
    image: portainer/portainer
    container_name: portainer
    restart: always
    command: --admin-password-file /run/secrets/portainer_admin_password -H unix:///var/run/docker.sock
    ports:
      - "9000:9000"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /home/ubuntu/docker/portainer/data:/data
    secrets:
      - portainer_admin_password
  test:
    image: centos:7
    entrypoint: "cat /run/secrets/portainer_admin_password"
    secrets:
      - portainer_admin_password
secrets:
  portainer_admin_password:
    file: /home/ubuntu/docker/portainer_admin_password

Additionally, I created /home/ubuntu/docker/portainer_admin_password with my desired plain-text password.
If I remove the portainer data directory (to ensure a clean up) and run docker-compose up portainer, the output looks like this:
Creating portainer ... done
Attaching to portainer
portainer     | 2019/04/07 19:18:39 Creating admin user with password hash <redacted>
portainer     | 2019/04/07 19:18:39 Starting Portainer 1.20.2 on :9000

However, attempting to log in with the password contained in the secret file fails.
I considered that there may be a problem with the secrets file.  Since I can't exec bash into the portainer container, I defined the test service. docker-compose up test outputs the exact contents of the secrets file.  This tells me that /run/secrets/portainer_admin_password should exist with the correct contents on the portainer container.
Expected behavior
The --admin-password-file option should work given the docker-compose configuration above.
Steps to reproduce the issue:
Steps to reproduce the behavior:

Define a docker-compose.yaml file similar to the one given above.
docker-compose up -d portainer
In a web-browser, navigate to portainer on port 9000.
Attempt to login with username admin and password matching the contents of the portainer_admin_password file.

Technical details:

Portainer version: 1.20.2
Docker version (managed by Portainer): Docker version 18.09.4-ce, build d14af54266
Platform (windows/linux): linux
Command used to start Portainer (docker run -p 9000:9000 portainer/portainer): docker-compose up -d portainer
Browser: Firefox 66.0.2

Additional context
n/a

I can confirm that we're also seeing this issue in docker swarm.

Just to confirm have you been following our docs at https://portainer.readthedocs.io/en/stable/configuration.html#inside-a-file ?

Yes, I've definitely read through all of it.  As I explained though, I'm using docker-compose in this case.

In my case I'm using a secret injected via the compose file and then deployed via a stack. I did this a few times to get some generated hashes and it looks like the problem is simply the code that reads the file is not stripping the ending newline. I generated a few hashes in the logs and then tested the hashes in a small script and verified that simply adding a newline to the end causes the hash to match.
version: '3.2'

services:
  agent:
    image: portainer/agent
    environment:
      # REQUIRED: Should be equal to the service name prefixed by "tasks." when
      # deployed inside an overlay network
      AGENT_CLUSTER_ADDR: tasks.agent
      # AGENT_PORT: 9001
      # LOG_LEVEL: debug
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /var/lib/docker/volumes:/var/lib/docker/volumes
    networks:
      - agent_network
    deploy:
      mode: global
      placement:
        constraints: [node.platform.os == linux]

  portainer:
    image: portainer/portainer
    command: -H tcp://tasks.agent:9001 --tlsskipverify --admin-password-file /run/secrets/portainer-pass
    ports:
      - "9000:9000"
    volumes:
      - /path/to/portainer/config/data:/data
    networks:
      - agent_network
    deploy:
      mode: replicated
      replicas: 1
      placement:
        constraints: [node.role == manager]
    secrets:
      - portainer-pass

secrets:
  portainer-pass:
    external: true

networks:
  agent_network:
    driver: overlay
    attachable: true

I can also confirm this issue using Docker Compose.

Hi guys, just adding my 2 cents here -> we have the same issue when using the admin password file from a secret. I did manage to get it working however -> The issue is in the newline character... if you create a password secret without the newline character, it works just fine..
This secret doesn't work:
echo $password | docker secret create ADMIN_PASSWORD -
This secret works:
echo -n $password | docker secret create ADMIN_PASSWORD -
@devs:  the fix would be to just trim the newline character from the password string:
e.g
password=$($password | tr -d '\n' )

Can confirm bug still exists in version 1.22.0
I'm also using it via a file-based docker secret (in docker-compose).
Bug is the trailing newline.
Is that patch going to be merged?

Basically just remove the trailing line when creating your password: echo -n "my password"

had a similar issue.
only when i clean old volumes it strarted to work

authors: dan-boehm deviantony hagaluly hhofs iicky lonix1 new-guy wingrunr21

repo: portainer/portainer

license: Zlib


text:
can you make a version 1.1 so pip install is easier?

this repo has changed a lot since version one, some people interested in developing Kvasir have been complaining that installing this dependency is too complicated (pip installing from a git hub repo took me a bit of time to figure out myself). Could we make a version 1.1?

Sure.  I'm traveling so it will probably be a few days.

No problem, have fun!

Sorry for the delay.  Version 0.2 is now published: https://pypi.python.org/pypi/cmsis-svd/0.2

authors: porkybrain posborne

repo: posborne/cmsis-svd


text:
Bounce Rules

Hello,
Could anyone tell me where to locate bounce code rules?
I mean how Postal read bounce codes to determine either soft or hard fail.
For example: 553 5.3.0 (A code like this says it is hardfails whereas in PMTA it is soft. Sincerely, it supposed to be soft and that is what Postal has been lacking behind for some times now)
I need the file location where the codes/rules are.
Thanks

I think that is mostly triggered here https://github.com/postalhq/postal/blob/ed7889a40e1d777f1d80821043562ab18b04766e/lib/postal/smtp_sender.rb#L171-L176
The error code you mentioned 553 is greater than 500 implying the message won't be able to be delivered hence the hard fail. See also https://www.serversmtp.com/smtp-error/

Thanks @willpower232 ,
"553 5.3.0 alpd681 DNSBL:RBL 521< 51.xxx.x.xx >_is_blocked.For assistance forward this error to abuse_rbl@abuse-att.net"
The same type of error above should be soft and not hardfail because it is a temporary things.
That is why PMTA is still more powerful because same error code is regards as softfail on PMTA.
It should not be regard as hardfail or permanent error because even after Postal said hardfail, there was still button option to "Redeliver the message" I clicked on the redeliver button and the message was again sent successfully.
Some of the ISP may block an IP for some reasons. Sometimes because IP may be cold, reputation e.t.c and after some hours their system automatically release the IP from being blocked. But since Postal is marking them as hardfail, there's no way Postal could automatically redeliver the message except you manually click on the "Redeliver" button.
This issue also very relate to this #266 and also #787 and it hasn't yet be worked on.
Postal is lacking a lot of futures even as it is good with great UI.
How I wish the developer could put more effort to make Postal great.
If it requires donation, we would donate.
Thanks for your help tho.

I understand the annoyance, I'd say this is a complicated topic and worthy of input from someone who is more familiar with the SMTP standards and RFCs.
I'd imagine that the current line is drawn between problems that are solved by time, like servers being offline, and problems that require manual intervention, like being blocked or emailing an address that doesn't exist.
Postal is using the one exception Ruby provides for this purpose and whilst that seems fine at a casual glance, it may not be the completely correct interpretation or it may be other email providers using the status codes inappropriately.

repo: postalhq/postal

license: MIT


text:
Object.Paths is not generic

In the examples it says
import { Object } from "hkt-toolbelt";

type Result = Object.Paths<{ name: { first: "foo"; last: "bar" } }>; // [["name", "first"], ["name", "last"]]

But should be:
import { $, Object } from "hkt-toolbelt";

type Result = $<Object.Paths, { name: { first: "foo"; last: "bar" } }>; // [["name", "first"], ["name", "last"]]

Thanks @nicobrinkkemper, I would accept a PR if you want to fix this element of the docs!

Closed by https://github.com/poteat/hkt-toolbelt/commit/c077c0b335698f04b03401b04859c6eedba91dc2 ✅

authors: nicobrinkkemper poteat

repo: poteat/hkt-toolbelt


text:
build check for new logger level: SOAPY_SDR_SSI

maintain compatibility with soapy release on current master

Added an ifdef check https://github.com/pothosware/pothos/commit/6ea767f3f0a9be8f986c07a664321f4df354c09e

repo: pothosware/pothos-sdr


text:
[error] Protocol 'fd' not on whitelist 'pipe,crypto,udp,rtp'!

Hi,
Thought I would try my luck again with this plugin and install it on a VM to isolate any docker related issues, now I've got a separate instance of Homebridge for this plugin running on Ubuntu Server 22.04.
But I'm still encountering issues streaming from my Nest Doorbell (Gen 2 Battery), with the following errors on debugging mode:
[10/19/2023, 1:53:30 AM] [homebridge-google-nest-sdm] Video stream requested: 1280 x 720, 30 fps, 299 kbps Front door Doorbell
[10/19/2023, 1:53:30 AM] [homebridge-google-nest-sdm] Executing command sdm.devices.commands.CameraLiveStream.GenerateWebRtcStream with parameters {"offerSdp":"v=0\r\no=- 17370516 0 IN IP4 0.0.0.0\r\ns=-\r\nt=0 0\r\na=group:BUNDLE 0 1 2\r\na=extmap-allow-mixed\r\na=msid-semantic:WMS *\r\nm=audio 9 UDP/TLS/RTP/SAVPF 96\r\nc=IN IP4 0.0.0.0\r\na=ice-ufrag:90fb\r\na=ice-pwd:6aaa26726e0358a97bb772\r\na=ice-options:trickle\r\na=fingerprint:sha-256 50:D8:52:A0:A5:74:B1:34:31:F7:72:0F:0A:4D:B3:A4:F3:87:26:13:E0:CF:47:FF:81:74:7B:C2:4A:E3:78:88\r\na=setup:actpass\r\na=recvonly\r\na=mid:0\r\na=msid:feea6529-d892-4984-98f2-55cb49eab00a c3aa68c9-b672-4372-a569-fca54d188ddd\r\na=rtcp:9 IN IP4 0.0.0.0\r\na=rtcp-mux\r\na=ssrc:3939234099 cname:99e1d9b4-2afc-4071-bf0c-21d49b2f33ec\r\na=rtpmap:96 opus/48000/2\r\nm=video 9 UDP/TLS/RTP/SAVPF 97\r\nc=IN IP4 0.0.0.0\r\na=ice-ufrag:90fb\r\na=ice-pwd:6aaa26726e0358a97bb772\r\na=ice-options:trickle\r\na=fingerprint:sha-256 50:D8:52:A0:A5:74:B1:34:31:F7:72:0F:0A:4D:B3:A4:F3:87:26:13:E0:CF:47:FF:81:74:7B:C2:4A:E3:78:88\r\na=setup:actpass\r\na=recvonly\r\na=mid:1\r\na=msid:3739da3d-c9a0-460d-a242-81eabae1fda8 9f8126ce-0845-4e8e-b03c-c8a8def156d8\r\na=rtcp:9 IN IP4 0.0.0.0\r\na=rtcp-mux\r\na=ssrc:649911642 cname:99e1d9b4-2afc-4071-bf0c-21d49b2f33ec\r\na=rtpmap:97 H264/90000\r\na=rtcp-fb:97 transport-cc\r\na=rtcp-fb:97 ccm fir\r\na=rtcp-fb:97 nack\r\na=rtcp-fb:97 nack pli\r\na=rtcp-fb:97 goog-remb\r\na=fmtp:97 level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=42e01f\r\nm=application 9 UDP/DTLS/SCTP webrtc-datachannel\r\nc=IN IP4 0.0.0.0\r\na=ice-ufrag:90fb\r\na=ice-pwd:6aaa26726e0358a97bb772\r\na=ice-options:trickle\r\na=fingerprint:sha-256 50:D8:52:A0:A5:74:B1:34:31:F7:72:0F:0A:4D:B3:A4:F3:87:26:13:E0:CF:47:FF:81:74:7B:C2:4A:E3:78:88\r\na=setup:actpass\r\na=mid:2\r\na=sctp-port:5000\r\na=max-message-size:65536\r\n"} Front door Doorbell
[10/19/2023, 1:53:33 AM] [homebridge-google-nest-sdm] Execution of command sdm.devices.commands.CameraLiveStream.GenerateWebRtcStream returned {"answerSdp":"v=0\r\no=- 0 2 IN IP4 127.0.0.1\r\ns=-\r\nt=0 0\r\na=group:BUNDLE 0 2 1\r\na=msid-semantic: WMS 14855667341365504641/4189994649 virtual-6666\r\na=ice-lite\r\nm=audio 19305 UDP/TLS/RTP/SAVPF 96\r\nc=IN IP4 172.253.59.127\r\na=rtcp:9 IN IP4 0.0.0.0\r\na=candidate: 1 udp 2113939711 2404:6800:4006:1004::7f 19305 typ host generation 0\r\na=candidate: 1 tcp 2113939710 2404:6800:4006:1004::7f 19305 typ host tcptype passive generation 0\r\na=candidate: 1 ssltcp 2113939709 2404:6800:4006:1004::7f 443 typ host generation 0\r\na=candidate: 1 udp 2113932031 172.253.59.127 19305 typ host generation 0\r\na=candidate: 1 tcp 2113932030 172.253.59.127 19305 typ host tcptype passive generation 0\r\na=candidate: 1 ssltcp 2113932029 172.253.59.127 443 typ host generation 0\r\na=ice-ufrag:nDOIlP-RuVOFKAoKWigaIAQQABgHARIFCJI\r\na=ice-pwd:W/BD9QFEI37PMZJCWMWEH2GI\r\na=fingerprint:sha-256 C0:97:4C:68:C3:9E:B6:70:AA:46:0A:8E:00:49:D1:EA:1B:82:EC:BB:F0:08:91:FA:F4:5B:54:79:3D:46:84:5C\r\na=setup:passive\r\na=mid:0\r\na=sendrecv\r\na=msid:virtual-6666 virtual-6666\r\na=rtcp-mux\r\na=rtpmap:96 opus/48000/2\r\na=fmtp:96 minptime=10;useinbandfec=1\r\na=ssrc:6666 cname:6666\r\nm=video 9 UDP/TLS/RTP/SAVPF 97\r\nc=IN IP4 0.0.0.0\r\na=rtcp:9 IN IP4 0.0.0.0\r\na=ice-ufrag:nDOIlP-RuVOFKAoKWigaIAQQABgHARIFCJI\r\na=ice-pwd:W/BD9QFEI37PMZJCWMWEH2GI\r\na=fingerprint:sha-256 C0:97:4C:68:C3:9E:B6:70:AA:46:0A:8E:00:49:D1:EA:1B:82:EC:BB:F0:08:91:FA:F4:5B:54:79:3D:46:84:5C\r\na=setup:passive\r\na=mid:1\r\na=sendrecv\r\na=msid:14855667341365504641/4189994649 14855667341365504641/4189994649\r\na=rtcp-mux\r\na=rtpmap:97 H264/90000\r\na=rtcp-fb:97 ccm fir\r\na=rtcp-fb:97 nack\r\na=rtcp-fb:97 nack pli\r\na=rtcp-fb:97 goog-remb\r\na=fmtp:97 level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=42e01f\r\na=ssrc:4189994649 cname:4189994649\r\nm=application 9 DTLS/SCTP 5000\r\nc=IN IP4 0.0.0.0\r\na=ice-ufrag:nDOIlP-RuVOFKAoKWigaIAQQABgHARIFCJI\r\na=ice-pwd:W/BD9QFEI37PMZJCWMWEH2GI\r\na=fingerprint:sha-256 C0:97:4C:68:C3:9E:B6:70:AA:46:0A:8E:00:49:D1:EA:1B:82:EC:BB:F0:08:91:FA:F4:5B:54:79:3D:46:84:5C\r\na=setup:passive\r\na=mid:2\r\na=sctpmap:5000 webrtc-datachannel 1024\r\n","expiresAt":"2023-10-19T01:58:33.554341Z","mediaSessionId":"nDOIlP-RuVOFKAoKWigaIAQQABgHARIFCJI"} Front door Doorbell
[10/19/2023, 1:53:33 AM] [homebridge-google-nest-sdm] Stream command: ffmpeg -protocol_whitelist pipe,crypto,udp,rtp -analyzeduration 15000000 -probesize 100000000 -i - -an -sn -dn -codec:v libx264 -preset ultrafast -tune zerolatency -pix_fmt yuv420p -color_range mpeg -bf 0 -r 30 -b:v 1196k -bufsize 1196k -maxrate 2392k -filter:v scale='min(1280,iw)':'min(720,ih)':force_original_aspect_ratio=decrease,scale=trunc(iw/2)*2:trunc(ih/2)*2 -payload_type 99 -ssrc 13873515 -f rtp -srtp_out_suite AES_CM_128_HMAC_SHA1_80 -srtp_out_params 3VLx1GKYbjcdVurM4966sjJgfsmNSG77Dib+zrkT srtp://192.168.0.192:56588?rtcpport=56588&pkt_size=1378 -vn -sn -dn -codec:a libfdk_aac -profile:a aac_eld -flags +global_header -ar 16k -b:a 24k -ac 1 -payload_type 110 -ssrc 14598580 -f rtp -srtp_out_suite AES_CM_128_HMAC_SHA1_80 -srtp_out_params pBhSx34XZ9pV3w0qYwoxK5jb6FWu0XpNDsdbc3+p srtp://192.168.0.192:58063?rtcpport=58063&pkt_size=188 -loglevel level+verbose v=0
o=- 0 0 IN IP4 127.0.0.1
s=-
c=IN IP4 127.0.0.1
t=0 0
m=audio 19703 UDP 96
a=rtpmap:96 opus/48000/2
a=fmtp:96 minptime=10;useinbandfec=1
a=rtcp-fb:96 transport-cc
a=sendrecv
m=video 13106 UDP 97
a=rtpmap:97 H264/90000
a=rtcp-fb:97 ccm fir
a=rtcp-fb:97 nack
a=rtcp-fb:97 nack pli
a=rtcp-fb:97 goog-remb
a=fmtp:97 level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=42e01f
a=sendrecv Front door Doorbell
[10/19/2023, 1:53:33 AM] [homebridge-google-nest-sdm] [info] ffmpeg version 6.0-homebridge-alpine-x86_64-static Copyright (c) 2000-2023 the FFmpeg developers Front door Doorbell
[10/19/2023, 1:53:33 AM] [homebridge-google-nest-sdm] [info]   built with gcc 12.2.1 (Alpine 12.2.1_git20220924-r10) 20220924 Front door Doorbell
[10/19/2023, 1:53:33 AM] [homebridge-google-nest-sdm] [info]   configuration: --enable-hardcoded-tables --enable-nonfree --enable-gpl --enable-hardcoded-tables --enable-hardcoded-tables --enable-openssl --enable-libdav1d --enable-libsvtav1 --enable-libx264 --enable-libx265 --enable-libvpx --enable-libxvid --enable-libvidstab --enable-libaom --enable-libzimg --enable-lv2 --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libtheora --enable-libfdk-aac --enable-libwebp --enable-libsrt --enable-libvpl --disable-ffnvcodec --enable-amf --disable-debug --disable-shared --enable-pthreads --enable-static --enable-version3 --extra-cflags='-I/build/workspace/include -I/build/workspace/include/lilv-0' --extra-ldexeflags=-static --extra-ldflags=-L/build/workspace/lib --extra-libs='-ldl -lpthread -lm -lz' --pkgconfigdir=/build/workspace/lib/pkgconfig --pkg-config-flags=--static --prefix=/build/workspace --extra-version=homebridge-alpine-x86_64-static Front door Doorbell
[10/19/2023, 1:53:33 AM] [homebridge-google-nest-sdm] [info]   libavutil      58.  2.100 / 58.  2.100 Front door Doorbell
[10/19/2023, 1:53:33 AM] [homebridge-google-nest-sdm] [info]   libavcodec     60.  3.100 / 60.  3.100 Front door Doorbell
[10/19/2023, 1:53:33 AM] [homebridge-google-nest-sdm] [info]   libavformat    60.  3.100 / 60.  3.100 Front door Doorbell
[10/19/2023, 1:53:33 AM] [homebridge-google-nest-sdm] [info]   libavdevice    60.  1.100 / 60.  1.100 Front door Doorbell
[10/19/2023, 1:53:33 AM] [homebridge-google-nest-sdm] [info]   libavfilter     9.  3.100 /  9.  3.100 Front door Doorbell
[10/19/2023, 1:53:33 AM] [homebridge-google-nest-sdm] [info]   libswscale      7.  1.100 /  7.  1.100 Front door Doorbell
[10/19/2023, 1:53:33 AM] [homebridge-google-nest-sdm] [info]   libswresample   4. 10.100 /  4. 10.100 Front door Doorbell
[10/19/2023, 1:53:33 AM] [homebridge-google-nest-sdm] [info]   libpostproc    57.  1.100 / 57.  1.100 Front door Doorbell
[10/19/2023, 1:53:33 AM] [homebridge-google-nest-sdm]  Front door Doorbell
[10/19/2023, 1:53:33 AM] [homebridge-google-nest-sdm] [fd @ 0x7fc3f9e6d640] [error] Protocol 'fd' not on whitelist 'pipe,crypto,udp,rtp'! Front door Doorbell
[10/19/2023, 1:53:33 AM] [homebridge-google-nest-sdm] [error] fd:: Invalid argument Front door Doorbell
[10/19/2023, 1:53:33 AM] [homebridge-google-nest-sdm]  Front door Doorbell
[10/19/2023, 1:53:33 AM] [homebridge-google-nest-sdm] FFmpeg exited with code: 1 and signal: null (Error) Front door Doorbell
[10/19/2023, 1:53:33 AM] [homebridge-google-nest-sdm] Executing command sdm.devices.commands.CameraLiveStream.StopWebRtcStream with parameters {"mediaSessionId":"nDOIlP-RuVOFKAoKWigaIAQQABgHARIFCJI"} Front door Doorbell

This is a fresh install with nothing else, I've installed ffmpeg-for-homebridge separately after installing this plugin as suggested by @litex2x in #86 to no avail. Tried the latest version and rolled back to 1.1.12, same results.
Seems like the stream command isn't configured properly or there's an issue with my FFmpeg for some reason?
Any help would be appreciated!

Check if v1.1.20 resolves this issue.

Same issue here. Any ideas?

@jacobwtyler : What version are you using?

Closing due to lack of activity.

authors: jacobwtyler kaytek potmat

repo: potmat/homebridge-google-nest-sdm

license: ISC


text:
Make docker container to be buildable from local state

Previous version required the changes to be published in a named repo, making local testing impossible.
This will also fix the --version endpoint to show the correct information instead of ${APP_VERSION}-${githash} (built at ${today})

@ilari-makimattila My bad, I didn't see your PR so I created a similar one. The approach is similar but it doesn't interfere with the original Dockerfile https://github.com/pottava/aws-s3-proxy/pull/45.

source: gharchive/pull-request

authors: EvgeniGordeev ilari-makimattila


text:
feature: add node in Dockerfile

Signed-off-by: Allen Sun shlallen1990@gmail.com

LGTM

repo: pouchcontainer/pouchlinter


text:
Ability to run individual couchdb-harness tests

Annoying that you currently can't without directly invoking the couchdb-harness executable.

There is probably a way to do this by either modifying the scripts or modifying https://github.com/pouchdb/couchdb-harness itself.

repo: pouchdb/pouchdb-server


text:
Todo

[x] Unit Test example
[ ] timeline background image url is not refreshed
[ ] websocket with next-pwa didn't work fine

[ ] 从非等宽字体 swap to 等宽字体页面闪烁，不知道能不能解决呢。

[ ] https://github.com/peers/peerjs/issues/630#issuecomment-1046151278
[ ] https://github.com/vercel/next.js/issues/35835#issuecomment-1100057011
[ ] https://github.com/vercel/next.js/issues/36127#issuecomment-1112240572


text:
Update kubernetes/master/golang/master build

This is an automated PR via build-bot

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ltccci
To complete the pull request process, please assign  after the PR has been reviewed.
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


text:
Update golang/master build

This is an automated PR via build-bot

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ltccci
To complete the pull request process, please assign
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


text:
Reintroduce & fix gamewindow refactor

Reintroduces the changes and fixes the windows bug from #1420 .
This should probably still be tested on all other platforms.
Edit: Closes #1102 (again).

Tested on macOS and Windows, looks ok to me. 👍

authors: FreezyLemon smoogipoo

repo: ppy/osu-framework


text:
Add parts of the new testbrowser toolbar's record section design

Like mentioned in #2135, I wasn't sure what to do about the red circle and the time.
The backdrop of this section is also coded a bit ugly 😕

Please drop the button colouring altogether (and update the button font to Roboto).

authors: jorolf peppy


text:
WIP: Introduce Window base class

On hold pending a rethink.

As part of the next step in #2448, this PR:

Replaces the osuTK IGameWindow inheritance with a placeholder clone ILegacyWindow.  This will be removed when the refactor is complete.
Introduces a new base class Window that GameWindow inherits from.
Moves anything not specifically osuTK-related into Window.

Shouldn't be any breaking changes, as long as everything is still referencing via IWindow.

looks good otherwise!

Updated #2448 with a draw.io design.

Closing for now while I rethink it.

authors: peppy swoolcock


text:
Join Chinese to explain

Join Chinese to explain,I believe that more people will know about filepond.

Everything else is in English so I'd rather not add a tutorial link that far up on the page and make it look like a language switch.

authors: kalifun rikschennink

repo: pqina/filepond


text:
can not download binary files

Unable to download the binary files required in makeImage.sh file. It seems that those files
can not be downloaded from https://github.com/pr0v3rbs/FirmAE/releases/tag/v1.0 manually,
only the source code can be downloaded.

Maybe this issue already resolved in the #1
And with my mistake, I force pushed Initial commit 854a41c8688c3b68ff89a363fc51e726fb9ec950 after you forked.
So, if your forked repository can't sync with this upstream/master repository, then I suggest that re-fork this repository again. Sorry about that.

it is ok now.


text:
Add bbm partner GA code

https://praekeltorg.atlassian.net/browse/GEMMOLO-475

👍

repo: praekelt/molo-gem


text:
Activate updated_by and created_by

Also flesh out the tests to ensure client stability

@rudigiesler @smn @jpaidoussi Please review.

:+1:

authors: gsvr rudigiesler

repo: praekelt/seed-service-rating


text:
Fake Marathon

Halp! I don't know what I'm doing.

[Current coverage][cc-pull] is 92.04%

Merging [#8][cc-pull] into [develop][cc-base-branch] will decrease coverage by -6.18%

@@            develop         #8   diff @@
==========================================
  Files             9         11     +2
  Lines           561        691   +130
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            551        636    +85
- Misses           10         55    +45
  Partials          0          0

Powered by Codecov. Last updated by [b8059fa...2dd2f34][cc-compare]
[cc-base-branch]: https://codecov.io/gh/praekeltfoundation/certbot/branch/develop?src=pr
[cc-compare]: https://codecov.io/gh/praekeltfoundation/certbot/compare/b8059fa09cafd9099b935aa0f729460169da7d8d...2dd2f34beb4fc3cb987427efc66f689e27b1aaf2
[cc-pull]: https://codecov.io/gh/praekeltfoundation/certbot/pull/8?src=pr

Superseded by other work.

repo: praekeltfoundation/certbot


text:
BnnrFromResourceTest.java:33: Improve test coverage and...

The puzzle 8-71502d8f from #8 has to be resolved:
https://github.com/pragmatic-objects/oo-atom/blob/a7afe924ca017c9fcec5e88923819ed144ade50d/atom-basis/src/test/java/com/pragmaticobjects/oo/atom/banner/BnnrFromResourceTest.java#L33-L33
The puzzle was created by Kapralov Sergey on 04-Jun-18.
Estimate: 15 minutes,
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@skapral please pay attention to this new issue.

repo: pragmatic-objects/oo-atom


text:
Replace controllers to thunks

Привет. Опять PR получился большой по кол-ву затронутых файлов.
Убрал контроллеры. Сделал санки. чуть подшаманил с аутентификацией. В общем посмотрите плиз с пристрастием

 Избавиться от всех контроллеров в проекте и переписать на Thunk

Запушил обновления с попыткой исправить прошлые замечения от коллег.

 Добавить в проект HOC или Hook для работы с авторизацией через Redux Thunk, Reselect и API

 Разбить аргументы в useFormInput в отдельные и сделать рефакторинг небольшой

authors: ShvetsovYura Verisana

repo: praktikum-game/defence-game


text:
[GSSOC'23] Add: Number Guessing Game

Number Guessing Game in Java

A Java program where the player guesses a random number within a given range. Feedback is provided after each guess, and the game continues until the correct number is guessed.
Expected behaviour

Generate a random number within a specific range.
Prompt the player to enter their guess.
Read the player's input and compare it to the generated number.
If the guess is correct, display a congratulatory message and end the game.
If the guess is incorrect, provide feedback to the player (e.g., too high or too low).
Allow the player to make additional guesses until they guess the correct number.
Repeat steps 2-6 until the correct number is guessed.
End the game and display the total number of guesses made.

Screenshots (optional)

Additional context (optional )

generated the game please assign me this issue under gssoc 23

Please assign me this issue under GSSoC'23

Looking forward to work on this issue please assign me 🙌

Kindly assign me with this issue.

@pranjay-poddar Kindly assign me this issue asap.

@MisterMickey go ahead.

@Saurabh-kumar09 Kindly review and merge my PR.

repo: pranjay-poddar/Dev-Geeks


text:
changed navbar and the client page : food website #1827

Title and Issue number

Close #1827
Checklist:

[] I have mentioned the issue number in my Pull Request.
[] I have commented my code, particularly in hard-to-understand areas
[] I have created a helpful and easy to understand README.md

@pranjay-poddar please review , here is screen recording of my changes.
https://github.com/pranjay-poddar/Dev-Geeks/assets/104628038/7a6be9f3-9bc3-4c65-b703-5f94d0157e6f


text:
Image Reducer

It closes the issue #242

@pranjay-poddar Please check and review


text:
Add random_story_generator.py

Title and Issue number

Random Story Generator (Python program). Issue #629
Close #629

Checklist:

[X] I have mentioned the issue number in my Pull Request.
[X] I have commented my code, particularly in hard-to-understand areas

Please kindly label 'hacktoberfest-accepted' if PR is ok, many thanks!
Happy Hacktobefest 2022 🎉


text:
UI Error on resetting Guild Store filters

When resetting filters while in guild store, this error appears
user:/AddOns/BetterUI/Modules/GuildStore/Module.lua:108: function expected instead of nil
stack traceback:
user:/AddOns/BetterUI/Modules/GuildStore/Module.lua:108: in function 'callback'
EsoUI/Libraries/ZO_KeybindStrip/ZO_KeybindStrip.lua:614: in function 'ZO_KeybindStrip:TryHandlingKeybindDown'
(tail call): ?
(tail call): ?

I will look into this. Thanks for reporting it!

Fixed in V2.25 (uploading shortly)

authors: lawsongrey prasoc

repo: prasoc/BetterUI


text:
🛑 Natural Language <2> SQL Query is down

In e81f934, Natural Language <2> SQL Query (https://natural-language-2-sql-queries.onrender.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Natural Language <2> SQL Query is back up in a45377a after 4 minutes.

repo: prateekralhan/status


text:
🛑 ChatGPT Beyond 2021 is down

In 51e6acd, ChatGPT Beyond 2021 (https://chatgpt-beyond-2021.onrender.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGPT Beyond 2021 is back up in 9a76c37 after 25 minutes.


text:
Create a virtual metadata table that returns the list of Pravega streams

The implementation should go in https://github.com/pravega/spark-connectors/blob/master/src/main/scala/io/pravega/connectors/spark/PravegaSourceProvider.scala#L180.

The PR has been merged for [Issue-60] Add virtual metadata table for Pravega Streams #70

authors: claudiofahey youminhan

repo: pravega/spark-connectors


text:
Cannot change how quickly it zooms

None of the "AnimationSpeed" props seem to work. Can someone help me zoom faster or slower?
Also, I noticed the within the source code, the animation speed props are set to PropTypes,bool instead of PropTypes.number could that be the issue? I did not trace the code any further.

Yeah, it's about being implemented, I will need some time to fully close the animations logic.

No worries, thank you for the reply. This library has been very helpful.


text:
GetHistoricRate doesn't work

Returns "Expected string" error. Fails when trying to parse the time in the array

It's because of the last PR for https://github.com/preichenberger/go-gdax/pull/48. Golang doesn't like the conversion to string...expects float64....

Fixed in: https://github.com/preichenberger/go-gdax/commit/9f655a0fe4900955cb03da9c37f186b463cb9339
Re-enabled GetHistoricRates test as well

repo: preichenberger/go-gdax


text:
Billing and API Key Management

Project Overview
The goal is to develop a platform that integrates with an existing system to safeguard running services by enforcing users to provide a valid API key. The UI/UX should draw inspiration from the ChatGPT API Key Management platform, focusing on credit-based payments without a subscription option.
Target Users

Admin: Will use the current prem-app as an admin dashboard. In this role, they should be able to create API keys (e.g., without constraints), view usage, etc.
Users/Developers: Will use a new frontend app to create API keys, top up credit balance, and view usage of API keys.

Core Features
Identity Management

Users should be able to register/login to a web app separate from the current prem-app dashboard.

API Key Management

Users should be able to generate one or more API keys.
API keys should have several levels of access constraints based on requests per minute (rate limit), tokens per minute for each service (service path), and a credit limit, which is a cumulative number of tokens determined by the user balance (available credit amount).

Billing

Users should be able to top up their credit balance using various payment methods: credit card, BTC, etc.
Users should be able to view usage and remaining credit balance.

Usage/Analytics

Users should be able to view the usage of their API keys to understand consumption and remaining access.
Administrators should have access to analytics to monitor service usage, identify trends, and optimize offerings.

Integration

The platform should integrate with the existing system, which consists of services running behind a Traefik proxy.
The existing Admin frontend application (prem-app) should be enhanced to enable the admin to create API keys and view Billing/Usage analytics.
Integration should be achieved through Traefik forward auth middleware to ensure authentication and authorization.

Main Flow

Admin API Key constraints creation: Admin creates API key constraints per service and configures the price of 1K tokens. Users will access prem-service based on API Key constraints which include:

Service Constraints: For each service, there will be a rate limit (number of requests in a minute) and usage limit (number of tokens in a minute).
Balance Constraints: Each balance can be converted to an accumulative number of tokens (token credit), based on the price of 1K tokens. For each user, the usage (number of tokens used) will be tracked, and access will be denied if the user of the API key runs out of token balance.

User Registration and API Key Creation: User registers/logs in to the Identity Management platform, tops up credit balance with a payment method, and creates an API key. There is a consideration whether users should have the option to create a key for one or more services or if a key should be for all services.
Request Verification: User makes a request to prem-service using the API key. The platform checks if the API key exists, whether the related user has enough balance, and whether the rate and usage limits for the desired service path are adhered to.

@tiero @filopedraz

w.r.t tokens concept NACK
The best way to represent the atomic resource is to represent the underlying compute, rather the length of the prompt of the request.
It should be a combination of time (minutes of billing) and "weight" of the RAM on the total available, to run the cumulative transformer blocks that are serve to consumers.
Think of Ethereum Gas consumption as an example; you estimate the GPU compute in advance (with static analysis you can infer the cost of each Operator that maps to a collection of instructions for a model
Ie.

FLOPS per second?

authors: sekulicd tiero

repo: premAI-io/prem-gateway


text:
Improve "all bookmarks" button

By default, bookmarks in a digest are not displayed. User can use the "All bookmark button" to display them:

However, this button isn't very clear; we should use a switch button instead with the label "View all bookmarks".
There is another issue :

when an user clicks on the button, the page query should be removed to avoid weird state pagination

[ ] Use switch and change wording for all bookmarks button
[ ] Reset page number on switch

[ ] Fix DarkMode

authors: Lucieo shinework

repo: premieroctet/digestclub


text:
[add]kmatsumoto3

最終行に追記しましたのでお手数ですがご確認お願いいたします。

↓の手順で、developをmasterに読みかえ、b_branch をkmatsumoto3に読み替えてください。
https://qiita.com/crarrry/items/c5964512e21e383b73da#手順

repo: prettyhappycatty/nodejsapp


text:
Feature/input field add auto hide prop

Update inputField prop from 'alwaysShow' to 'autoHide'
before:
default: toggle show/hide
alwaysShowLabel: always show the label
now:
default: always show the label
autoHide: toggle show/hide

Fixes #226

Going to close this out since we haven't had any updates on it

authors: jxnblk mattcpchen

repo: pricelinelabs/design-system


text:
Add focusZone to TabNav

Motivation
The TabNav should match the focus rules define by WAI-ARIA for the tablist role - specifically:

Tab should move to the next focusable element (not the next tab)
Left and Right Arrow Keys should cycle the focus on the tabs
When the tablist receives focus, the selected tab should become focused

I've also added aria-selected="true" to the selected tab.
Related to https://github.com/github/accessibility-audits/issues/2459
Merge checklist

[x] Added/updated tests
[ ] Tested in Chrome
[ ] Tested in Firefox
[ ] Tested in Safari
[ ] Tested in Edge

(not a blocker for this pull request) Hi! quick question, what is the focus expectation when a tab is selected with Enter/Space? It is ideally accompanied by a route/hash change in the url as well.

authors: owenniblock siddharthkp

repo: primer/react


text:
Hooking up getAnchoredPosition to position menu

cc: @langermank, @lindseywild

@langermank, @lindseywild:
I'm so excited by how close we are 😄. Just so I don't forget next week, I'm noting here what I think the most immediate To-Dos CSS wise are:

Introducing a CSS class for styling the ul[role='none'] bits. I I don't think we have this yet. We're mocking this temporarily with a temporary style tag as noted in https://github.com/primer/view_components/pull/1131#discussion_r856748915 but we definitely don't want this in production.
Making sure that the above CSS class and the Overlay classes are available for production use.
Verifying the menu is responsive and looks as we expect in various scenarios.

Less urgent in terms of MVP but still ideal to get done:

Creating an Overlay component.
Swapping the Overlay related parts of ActionMenu with the said Overlay component.


text:
Create User on Local Net with Funds to Swap

Create some user on the local net where we can have a cloned pool running. Give a user funds to swap against this pool.

Defunct given REVM use.

repo: primitivefinance/arbiter


text:
Export Bookmark Error

export bookmark到第五页就出现error了，看起来好像是读不到response 的cache。
因为我自己看network tab 如果load太多，有些旧的twitter bookmark response会卡掉。

Hi,
可以详细提供一下报错的具体场景吗？

是在进行什么操作时发生的报错，是预览书签的时候，还是导出数据的时候？
浏览器 DevTools 的 Console 中应该有具体的报错信息，可以一起贴上来吗？
导出的数据量是多少？刷新一下页面再试的话，每次都会报错吗？

Thank you.

预览书签和导出数据都会遇到，觉得有可能是response那里的问题。
数据只要多过430+就会有error，试过少过430没问题。

重现步骤:

load好bookmark

预览的时候只要到第5页就会这样

如果直接导出，会卡在这个情况

Console 报错:

浏览第五页:

[twitter-web-exporter] Cannot read properties of undefined (reading 'user_results') TypeError: Cannot read properties of undefined (reading 'user_results')
    at extractTweetUserScreenName (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:1498:23)
    at Object.quoteSourceAccessor [as accessorFn] (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:1793:21)
    at Object.getValue (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:23:46141)
    at Object.getValue (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:23:45538)
    at k.cell [as constructor] (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:2018:32)
    at k.N [as render] (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:3:8708)
    at L (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:3:6218)
    at S (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:3:1853)
    at j (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:3:7956)
    at L (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:3:6765)

导出的报错:

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'user_results')
    at extractTweetUserScreenName (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:1498:23)
    at Object.quoteSourceAccessor [as accessorFn] (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:1793:21)
    at Object.getValue (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:23:46141)
    at Object.getValue (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:23:45538)
    at onExport (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:1038:30)
    at HTMLButtonElement.T (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:3:4502)

不清楚是不是因为load到太下了 影响到上面的response，因为以前我是manual export bookmark的 Exporting your Twitter bookmarks in markdown file

看起来是某条推文的数据结构有点不一样，导致处理出错了。我做了个兼容，用这个版本试试呢：
https://github.com/prinsss/twitter-web-exporter/releases/download/nightly/twitter-web-exporter.user.js
更新 v1.0.2-alpha.1 之后，翻到第 5 页时 Console 应该会有 "Failed to extract tweet user screen name" 的报错，以及报错的具体推文数据，麻烦也一起贴上来，谢谢。:)

用了兼容版，没问题了
concole的报错在这:
userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:232 [twitter-web-exporter] Failed to extract tweet user screen name TypeError: Cannot read properties of undefined (reading 'user_results')
    at extractTweetUserScreenName (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:1499:25)
    at Object.quoteSourceAccessor [as accessorFn] (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:1798:21)
    at Object.getValue (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:23:46141)
    at Object.getValue (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:23:45538)
    at k.cell [as constructor] (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:2023:32)
    at k.N [as render] (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:3:8708)
    at L (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:3:6218)
    at S (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:3:1853)
    at j (userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:3:7956)

另外，我遇到export media 的一个问题，有4700+ media, 尝试比较少数的100+ media 可以成功export zip。

[twitter-web-exporter] Failed to export media. Open DevTools for more details. DOMException: The requested file could not be read, typically due to permission problems that have occurred after a reference to a file was acquired.
error @ userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:232
onExport @ userscript.html?name=Twitter-Web-Exporter.user.js&id=94fbb317-adc6-4f7f-970b-811005a21f3f:1624

Failed to extract tweet user screen name 报错的再后面应该还有一个 JSON 对象的，看看具体内容是什么呢？如果没有的话，看下第五页上应该会有一条在 Quote Source 列上显示了 READ_ERROR，点击最后面的 Details 按钮看看。
4700+ 的 media 有点多，这数量浏览器 hold 不住啊……目前由于实现方面的限制，Chrome 最大可以保存 2GB 的文件，Firefox 最大可以保存 800MB。
脚本更新了 1.0.2，在 Export Media 界面新增了一个 "Copy URLs" 按钮，可以把链接复制到剪贴板，然后配合 aria2 等外部下载器使用，下载会更稳定一些。
https://github.com/prinsss/twitter-web-exporter/releases/download/v1.0.2/twitter-web-exporter.user.js

好的哦明白，目前也是用着外部下载器方案，这里是第五页的报错json，应该是retweet的账号private了，你看下是这个json吗。

{
    "__typename": "TweetTombstone",
    "tombstone": {
        "__typename": "TextTombstone",
        "text": {
            "rtl": false,
            "text": "You’re unable to view this Post because this account owner limits who can view their Posts. Learn more",
            "entities": [
                {
                    "fromIndex": 92,
                    "toIndex": 102,
                    "ref": {
                        "type": "TimelineUrl",
                        "url": "https://help.twitter.com/rules-and-policies/notices-on-twitter",
                        "urlType": "ExternalUrl"
                    }
                }
            ]
        }
    }
}

看起来是的，我后面兼容下这种情况吧。如果还有其他问题，欢迎继续反馈。:)

repo: prinsss/twitter-web-exporter


text:
Beta push fix many issues see details

It's time to merge or fork.
@EricDavies,
Here is a full beta branch that merge with no conflicts and and suppose to solve following issues:

Add getSourceList and getAudioSourceList #80
easyrtc screen capture chrome extension example. #87
JSHint on easyrtc_int.js #169
Firefox and previous WebRTC impl does not call emitOnStreamClosed #173
getUserMediaConstraints() bug #176
Possible bad userAgent RegExp in Adapter.js #177
A mistake in documentation #188
wrong condition expression in buildLocalMediaStream #189
missing argument for wasAcceptedCB #190
too many arguments passed into onRemoveStreamHelper #192
using undefined error code SIGNAL_ERROR #193
using undefined error code NOVIABLEICE #193
Possible undefined getUserMedia #194
Adapter.js Update break easyrtc require-js and AMD support #195

Some already merged or closed, but still for reference.

WebRTC Version Detecting Fails When Simulating iPad In Chrome Dev Tools #90
callFailureCB is undefined #133
FileTransfer support on IE10 #137
FileTransfer support on IE10 #155

cc @dryswabbie
reporters @omochi, @ShiYw, @rretter

I think this patch is nice and great work. (except a tiny one I noted)
@EricDavies please accept these commits and clear issues.

@omochi,  I fixed your review and also applied SIGNAL_ERROR -> SIGNAL_ERR to be the same suffix on every errors "const" - https://github.com/hthetiot/easyrtc/commit/07f550805385c5bb69cccb6450b3464da0ba5830

@hthetiot thank you 😀

Hi Harold,
I've gotten authorization from my boss to give someone from the easyrtc
community administrative access to the easyrtc github site so that they
apply the minor fixes and pull requests that are needed to bring easyrtc
back to a state of usability. Rod and I just snowed under with work on a
critical project  right now and can't do it. Would you be willing to take
on that chore, at least for a few weeks?
Eric.
On Thu, Feb 18, 2016 at 7:35 PM, Harold Thétiot notifications@github.com
wrote:

It's time to merge or fork.
@EricDavies https://github.com/EricDavies,
Here is a full beta branch that merge with no conflicts and and suppose to
solve following issues:

Add getSourceList and getAudioSourceList #80
https://github.com/priologic/easyrtc/issues/80
easyrtc screen capture chrome extension example. #87
https://github.com/priologic/easyrtc/issues/87
JSHint on easyrtc_int.js #169
https://github.com/priologic/easyrtc/issues/169
Firefox and previous WebRTC impl does not call emitOnStreamClosed
#173 https://github.com/priologic/easyrtc/issues/173
getUserMediaConstraints() bug #176
https://github.com/priologic/easyrtc/issues/176
Possible bad userAgent RegExp in Adapter.js #177
https://github.com/priologic/easyrtc/issues/177
A mistake in documentation #188
https://github.com/priologic/easyrtc/issues/188
wrong condition expression in buildLocalMediaStream #189
https://github.com/priologic/easyrtc/issues/189
missing argument for wasAcceptedCB #190
https://github.com/priologic/easyrtc/issues/190
too many arguments passed into onRemoveStreamHelper #192
https://github.com/priologic/easyrtc/issues/192
using undefined error code SIGNAL_ERROR #193
https://github.com/priologic/easyrtc/issues/193
using undefined error code NOVIABLEICE #193
https://github.com/priologic/easyrtc/issues/193
Possible undefined getUserMedia #194
https://github.com/priologic/easyrtc/issues/194
Adapter.js Update break easyrtc require-js and AMD support #195
https://github.com/priologic/easyrtc/issues/195

Some already merged or closed, but still for reference.

WebRTC Version Detecting Fails When Simulating iPad In Chrome Dev
Tools #90 https://github.com/priologic/easyrtc/issues/90
callFailureCB is undefined #133
https://github.com/priologic/easyrtc/issues/133
FileTransfer support on IE10 #137
https://github.com/priologic/easyrtc/issues/137
FileTransfer support on IE10 #155
https://github.com/priologic/easyrtc/issues/155

cc @dryswabbie https://github.com/dryswabbie
reporters @omochi https://github.com/omochi, @ShiYw
https://github.com/ShiYw, @rretter https://github.com/rretter
You can view, comment on, or merge this pull request online at:
https://github.com/priologic/easyrtc/pull/198
Commit Summary

implement getSourceList and getAudioSourceList #80
fix review #80
add getMediaDevices support #80
merge #60 to beta
easyrtc screen share example #87
fix typo and doc
fix typo and doc for easyrtc_sc #87
merge beta changes
fix ua chrome version parsing #90
Merge branch 'beta2' into beta
merge easyrtc/beta
merge easyrtc beta
fix possible openwebrtc error
merge beta branch
fix AcceptChecker noWebrtcSupport error (and trim space) #133
fix FileTransfer support for IE #137
fix FileTransfer support for IE #155
fix case where MediaStream.hasOwnProperty return fasle on chrome and
FF
merge priologic/beta
add .jshintrc config #169
JSHint pass on easyrtc_int.js, no logic change #169
rebuild easyrtc.js #169
merge sylaps/beta
merge beta from priologic
Fix Firefox Does not call emitOnStreamClosed #173
repack easyrtc.js #173
improve isStreamActive for better cross WebRTC impl support #173
repack easyrtc.js #173
fix possible bad chrome userAgent regexp
repack with fixed webrtcDetectedVersion regExp
fix possible bad userAgent RegExp in adapter.js #177
fix Possible undefined getUserMedia #194
fix missing errCodes.NOVIABLEICE #193
fix missing wasAcceptedCB callback argument #190
remove extra argument on onRemoveStreamHelper #192
fix condition expression in buildLocalMediaStream #189
update doc #188
fix getUserMediaConstraints() desiredVideoProperties.height bug #176
merge @hthetiot/beta
merge priologic beta
merge priologic beta
fix bad merge
fix easyrtc AMD support #195
merge
revert regression on #194 after Adapter update
Merge branch 'beta' into beta_sylaps
fix window.getUserMedia usage and use getUserMedia from
closure/script #195

File Changes

A .jshintrc
https://github.com/priologic/easyrtc/pull/198/files#diff-0 (122)
M api/adapter.js
https://github.com/priologic/easyrtc/pull/198/files#diff-1 (47)
M api/easyrtc.js
https://github.com/priologic/easyrtc/pull/198/files#diff-2 (277)
M api/easyrtc_ft.js
https://github.com/priologic/easyrtc/pull/198/files#diff-3 (4)
M api/easyrtc_int.js
https://github.com/priologic/easyrtc/pull/198/files#diff-4 (229)
A api/labs/easyrtc_sc.js
https://github.com/priologic/easyrtc/pull/198/files#diff-5 (255)
A api/labs/easyrtc_sc_extension/Icon-16.png
https://github.com/priologic/easyrtc/pull/198/files#diff-6 (0)
A api/labs/easyrtc_sc_extension/Icon-64.png
https://github.com/priologic/easyrtc/pull/198/files#diff-7 (0)
A api/labs/easyrtc_sc_extension/background-script.js
https://github.com/priologic/easyrtc/pull/198/files#diff-8 (35)
A api/labs/easyrtc_sc_extension/content-script.js
https://github.com/priologic/easyrtc/pull/198/files#diff-9 (43)
A api/labs/easyrtc_sc_extension/manifest.json
https://github.com/priologic/easyrtc/pull/198/files#diff-10 (29)
M docs/easyrtc_server_configuration.md
https://github.com/priologic/easyrtc/pull/198/files#diff-11 (7)
M docs/easyrtc_server_install.md
https://github.com/priologic/easyrtc/pull/198/files#diff-12 (4)
M lib/easyrtc_default_event_listeners.js
https://github.com/priologic/easyrtc/pull/198/files#diff-13 (2)

Patch Links:

https://github.com/priologic/easyrtc/pull/198.patch
https://github.com/priologic/easyrtc/pull/198.diff

—
Reply to this email directly or view it on GitHub
https://github.com/priologic/easyrtc/pull/198.

Yes @EricDavies I will work with @omochi to merge the issues in beta and prepare the next release for you to merge in master if that works for you.

Sincerely thanks @EricDavies

@omochi Ready on my side for one last review.

@hthetiot I will check later.

@omochi Roger that! I used it without issue for now.

@hthetiot
I checked commits following.

merge Delete non existing room fix #84

Code is ok.
But, I am not sure where this new behavior is good or bad.
When we something delete,
if it is already not exists,
we can think as we get expected result that this is not exists.
I think that consistency is most important thing such case.
So if other deletion apis for entity other than room
returns failure when it is not exists,
this patch is ok.

merge Updated /etc/init/easyrtc.conf #101

ok

merge Added a bower.json #109

ok

merge remove duplicate line #117

ok

merge Fixed css class for mirroring local video #153

ok

fix undefined socket.io method #209

ok. thank you.

fix Unnecessary if branch and flow in InitMediaSource #203

ok. thank you.

fix Invalid range condition in getIthCaller #202

ok. thank you.

fix bug for in #201

ok. thank you.

fix unused argument in #200

ok.
But there is regression about fix bug for in #201.
please fix it.

wrong property access of message object for type 'error' in onChannel…
…Cmd #199

ok. thank you.

fix more trivia: joinRoom()'s roomParameters not a string #168

ok.

merge New feature: IceConnectionStateChangeListener #122

ok.

remove SetVideoBandWidth from doc and source after deprecation for mu…
…ltiple release #120

ok.

error "attempt to connect when already connected to socket server" even if connection failed #98

I wrote my opinion at #98 thread.
Please read it.

fix Strange code about refreshPane #204

ok. thank you.

merge updated example server #112

ok.

Will check you review ASAP
On Saturday, March 5, 2016, omochimetaru notifications@github.com wrote:

@hthetiot https://github.com/hthetiot
I checked commits following.
merge Delete non existing room fix #84
https://github.com/priologic/easyrtc/pull/84
Code is ok.
But, I am not sure where this new behavior is good or bad.
When we something delete,
if it is already not exists,
we can think as we get expected result that this is not exists.
I think that consistency is most important thing such case.
So if other deletion apis for entity other than room
returns failure when it is not exists,
this patch is ok.
merge Updated /etc/init/easyrtc.conf #101
https://github.com/priologic/easyrtc/pull/101
ok
merge Added a bower.json #109
https://github.com/priologic/easyrtc/pull/109
ok
merge remove duplicate line #117
https://github.com/priologic/easyrtc/pull/117
ok
merge Fixed css class for mirroring local video #153
https://github.com/priologic/easyrtc/pull/153
ok
fix undefined socket.io method #209
https://github.com/priologic/easyrtc/issues/209
ok. thank you.
fix Unnecessary if branch and flow in InitMediaSource #203
https://github.com/priologic/easyrtc/issues/203
ok. thank you.
fix Invalid range condition in getIthCaller #202
https://github.com/priologic/easyrtc/issues/202
ok. thank you.
fix bug for in #201 https://github.com/priologic/easyrtc/issues/201
ok. thank you.
fix unused argument in #200
https://github.com/priologic/easyrtc/issues/200
ok.
But there is regression about fix bug for in #201.
please fix it.
wrong property access of message object for type 'error' in onChannel…
…Cmd #199 https://github.com/priologic/easyrtc/issues/199
ok. thank you.
fix more trivia: joinRoom()'s roomParameters not a string #168
https://github.com/priologic/easyrtc/issues/168
ok.
merge New feature: IceConnectionStateChangeListener #122
https://github.com/priologic/easyrtc/issues/122
ok.
remove SetVideoBandWidth from doc and source after deprecation for mu…
…ltiple release #120 https://github.com/priologic/easyrtc/issues/120
ok.
error "attempt to connect when already connected to socket server" even if
connection failed #98 https://github.com/priologic/easyrtc/issues/98
I wrote my opinion at #98 https://github.com/priologic/easyrtc/issues/98
thread.
Please read it.
fix Strange code about refreshPane #204
https://github.com/priologic/easyrtc/issues/204
ok. thank you.
merge updated example server #112
https://github.com/priologic/easyrtc/pull/112
ok.
—
Reply to this email directly or view it on GitHub
https://github.com/priologic/easyrtc/pull/198#issuecomment-192626630.

--
Harold Thétiot.

@omochi
About #84

But, I am not sure where this new behavior is good or bad.
Will double check

About #201 and #200 i fixed regression
I merged the Jslint 190f7d2 that is only large because i changed the order of "private" function and "expression" for not to be use before being declared.

Ready to merge, will do change log and wait last approval from @omochi and @EricDavies or any other before merging.

About #84
Thank you checking. so ok.

About #201 and #202
I checked commit fix regression on #201 from #200	a28ddbc. ok.

About Jslint big pass
Yes I know. ok.

commit 	fix review #198	e119fed
I checked it. ok.

--
I think that we can merge it now at last !

authors: EricDavies hthetiot omochi

repo: priologic/easyrtc


text:
Field-level authorization for nexus-prisma models

Hey 👋
I can't tell if it's possible to do field-level read-authorization for a Nexus-Prisma generated model/field. For example, if I have the prisma model
type User {
  id: ID!
  firstName: String!
  address: String!
}

and I expose that using Nexus-Prisma, how would I go about making custom read rules for the firstName and address string? If, for example, everyone authorized can read the first name, but  only allow reading the address if you are the user?
I know Nexus supports field authorization resolvers, but can't seem to figure out how that works with Nexus Prisma models and types?

I wanted to open an issue about that. How could it work together? Same thing about mutation authorization. I would expect something like:
mutationType({
    definition(t) {
        t.crud.createOnePost({
            authorize: (root, args, ctx) => ctx.auth.canViewPost(args.id),
        })
})

Anyway to do it?

authors: jhalborg poulainv

repo: prisma-labs/nexus-prisma


text:
Support for @> and <@ operators when working with full-text-search

Problem
Prisma docs/full-text-search state that Prisma Client supports operators that Postgres supports.

When I tried executing a query using the @> or <@, Prisma Client returned the following error:
{ query: 'tom <@ sawyer' } // not related to the Prisma client error
{
  error: PrismaClientUnknownRequestError:
  Invalid `prisma.book.findMany()` invocation:

    Error occurred during query execution:
  ConnectorError(ConnectorError { user_facing_error: None, kind: QueryError(Error { kind: Db, cause: Some(DbError { severity: "ERROR", parsed_severity: Some(Error), code: SqlState("42601"), message: "syntax error in tsquery: \"tom sawyer\"", detail: None, hint: None, position: None, where_: None, schema: None, table: None, column: None, datatype: None, constraint: None, file: Some("tsquery.c"), line: Some(689), routine: Some("makepol") }) }) })
      at cb (/Users/ruheni/Documents/repos/work/prisma/projects/prisma-fulltextsearch/node_modules/@prisma/client/runtime/index.js:38692:17)
      at async handler (webpack-internal:///./pages/api/search.ts:40:29)
      at async Object.apiResolver (/Users/ruheni/Documents/repos/work/prisma/projects/prisma-fulltextsearch/node_modules/next/dist/server/api-utils.js:102:9)
      at async DevServer.handleApiRequest (/Users/ruheni/Documents/repos/work/prisma/projects/prisma-fulltextsearch/node_modules/next/dist/server/next-server.js:1064:9)
      at async Object.fn (/Users/ruheni/Documents/repos/work/prisma/projects/prisma-fulltextsearch/node_modules/next/dist/server/next-server.js:951:37)
      at async Router.execute (/Users/ruheni/Documents/repos/work/prisma/projects/prisma-fulltextsearch/node_modules/next/dist/server/router.js:222:32)
      at async DevServer.run (/Users/ruheni/Documents/repos/work/prisma/projects/prisma-fulltextsearch/node_modules/next/dist/server/next-server.js:1135:29)
      at async DevServer.run (/Users/ruheni/Documents/repos/work/prisma/projects/prisma-fulltextsearch/node_modules/next/dist/server/dev/next-dev-server.js:445:20)
      at async DevServer.handleRequest (/Users/ruheni/Documents/repos/work/prisma/projects/prisma-fulltextsearch/node_modules/next/dist/server/next-server.js:325:20) {
    clientVersion: '3.7.0'
  }
}

Suggested solution
It would be worth noting explicitly the operators Prisma client supports in the docs or provide more concrete examples of how it works/ use it.

The operators you're mentioning are Postgres operators, not query operators. The link provided in the documentation is misleading.
Below are the query operators Postgres supports, with the addition of <-> that I couldn't find documented anywhere:

This is more of a documentation issue. I, unfortunately, couldn't find any proper documentation on all the supported query operators.
I'll leave it open and hand it over to the docs team.

I think the link on https://www.prisma.io/docs/concepts/components/prisma-client/full-text-search#querying-the-database has been fixed. Can you confirm @ruheni?

Yes

authors: Weakky janpio ruheni

repo: prisma/prisma


text:
@default is not respected when using @db.Uuid with Postgres

Bug description
When adding a default case to the @db.uuid native type in Postgres, the @default is not respected. The generated SQL file does not have the expected DEFAULT keywords.
How to reproduce

Create a model with the @default(uuid()) @db.Uuid set after a parameter
prisma migrate dev --create-only
Notice that DEFAULT keyword is missing from generated SQL

Expected behavior
No response
Prisma information
generator client {
  provider        = "prisma-client-js"
  binaryTargets   = ["native", "linux-musl"]
  previewFeatures = ["fullTextSearch"]
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

Environment & setup

OS: Linux
Database: Postgresql
Node.js version: 16.14.2

Prisma Version
prisma                  : 4.0.0
@prisma/client          : 4.0.0
Current platform        : debian-openssl-1.1.x
Query Engine (Node-API) : libquery-engine da41d2bb3406da22087b849f0e911199ba4fbf11 (at node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node)
Migration Engine        : migration-engine-cli da41d2bb3406da22087b849f0e911199ba4fbf11 (at node_modules/@prisma/engines/migration-engine-debian-openssl-1.1.x)
Introspection Engine    : introspection-core da41d2bb3406da22087b849f0e911199ba4fbf11 (at node_modules/@prisma/engines/introspection-engine-debian-openssl-1.1.x)
Format Binary           : prisma-fmt da41d2bb3406da22087b849f0e911199ba4fbf11 (at node_modules/@prisma/engines/prisma-fmt-debian-openssl-1.1.x)
Default Engines Hash    : da41d2bb3406da22087b849f0e911199ba4fbf11
Studio                  : 0.465.0

So... Until now the @default(uuid()) does the uuid generation in the client. We do not yet support extensions and using it in the database level requires us to enable the uuid extension.
This will change in the future, follow and comment on this issue: https://github.com/prisma/prisma/issues/12308
Right now, if you want this in the database level, you should have the model like so:
model A {
  id   Int    @id
  data String @default(dbgenerated("uuid_generate_v4()")) @db.Uuid
}

And in the migration file, add to the beginning the following extension:
create extension if not exists "uuid-ossp";

There are two extensions for generating uuids (uuid-ossp and pgcrypto), and afaik pgcrypto is the recommended one these days, uuid-ossp is older and not as good. That should be checked of course.

authors: JoeyEamigh pimeys tomhoule


text:
Using MLab Sandbox with MongoDB connector

Currently using a mlab sandbox with the mongo connector results in an authentication error.
This is because prisma needs access to the admin DB as it will create a database named prisma to track all of the deployment and migration histories.
That being said I am able to use a sandbox MongoDB atlas deployment for development. Just use the connection string they give you to login in MongoDB compass, not the one they give you for the application. Give atlas a try here
If you want to use mlab anyways, you will need access to admin DB that means a dedicated box.
You may be aware of the fact that mlab has been acquired by MongoDB Inc and mlab deployment will be moved into atlas soon, so I will recommend using MongoDB atlas. Just make sure you use the right connection string there.

@pantharshit00 Used MongoDB atlas. But still getting the same issue.


text:
Can't delete nodes in Prisma Admin 1.31

Describe the bug
After upgrading to 1.31 and migrating to the new database syntax I can't delete any nodes. I tried to create new type, create node and delete it — same error. Also I've tried to clean cache and reload.
TypeError: Cannot read property 'id' of undefined
    at t.getDerivedStateFromProps (app.js:1)
    at ni (app.js:1)
    at xo (app.js:1)
    at Ao (app.js:1)
    at Va (app.js:1)
    at Ua (app.js:1)
    at ju (app.js:1)
    at wu (app.js:1)
    at Cu (app.js:1)
    at Sn (app.js:1)
    at HTMLDocument.r (app.js:1)
Uncaught TypeError: Cannot read property 'id' of undefined
    at t.getDerivedStateFromProps (app.js:1)
    at ni (app.js:1)
    at xo (app.js:1)
    at Ao (app.js:1)
    at Va (app.js:1)
    at Ua (app.js:1)
    at ju (app.js:1)
    at wu (app.js:1)
    at Cu (app.js:1)
    at Sn (app.js:1)
    at HTMLDocument.r (app.js:1)

To Reproduce
Steps to reproduce the behavior:

Go to http://localhost:4488/_admin
Choose any query (or even create one)
Click on any node
In Detail Area click on Delete icon
Whole page will become empty
In console you'll see error that I've mentioned above

Expected behavior
Deleted node
Screenshots

Versions (please complete the following information):

Connector: Postgres
Prisma Server: 1.31
prisma CLI: prisma/1.31.1 (darwin-x64) node-v11.14.0
OS: OS X High Sierra
other dependencies:  "prisma-client-lib": "1.31.1"

Created small reproduction repository for the issue: https://github.com/appdrop/prisma-deleting-node-issue

Not sure why, but it’s working now. I restarted Docker and updated few packages (with brew, not sure if that's related).


text:
"Update" on Json field that preserves the old KV pairs

Hey, when I run an update statement on a table that has a JSON field, I would like to update the JSON field that has some existing data, instead of "replacing" it. What I mean by this is to append another key-value pair to the JSON field, while preserving the old data in the JSON.
My schema:
model User {
  userMetadata   Json?

When I created the user, I did
const createUser = await prisma.user.create({
  data: {
    userMetadata: {
       name: "John"
    }
  }
});

Then when I want to update his metadata, I do:
  await prisma.user.update({
    where: {
      id: userId //suppose there is one
    },
    data:{
      userMetadata: {
        university: "Oxford"
      }
    }
  })

Expected results
Ideally after running the update I would like to see the user having such userMetadata:
userMetadata: {
  name: "John",
  university: "Oxford"
}

Actual results
However, it only shows
userMetadata: {
  university: "Oxford"
}

Question
I am wondering if there is a way to append new key-value pairs like university: "Oxford" to the userMetadata while preserving the old data?

Any progress on this? This seems like a must have when dealing with JSON. It is possible with Postgres queries.

This would be great to have natively. With Postgres 14, you could even use the native subscript syntax UPDATE "Relation" SET config['a']['foo'] = 'new value'.
Currently I'm achieving this with $executeRaw and
    UPDATE "Relation"
    SET config = coalesce(config, '{}'::jsonb) || ${JSON.stringify(configJson)}
    WHERE id = ${id}

Would also be interested in seeing this

hey
how that is going on?

Do we have an update on this?

Hi there, would also be interested in being able to set json fields without having to read before the write.

any updates here?

This feature would be very welcome

Any updates on plans to support this feature?

Any updates?

Also interested in this feature.

Calling for this update please...

4 1/2 years later.. do I dare ask for an update for fear of being marked as "abuse"? 😬
(asking for a friend)

authors: ChristophP GabrielSoga Kumagor0 RavenHursT Redzli Utkarshbhimte alexandrulesi camrank charanjit-singh ericpeng1999 kladnik leeratyou sarcastic-verma wyozi


text:
Support Google Cloud Spanner

Hey! :)
It would be awesome if Prisma Client could be compatible with https://cloud.google.com/spanner/

I'd love to see Spanner supported. Now that Spanner has granular instance sizing and cloud sql has mandatory downtime where Spanner doesn't, it makes it the preferred database over cloudsql.
Spanner is starting to rollout a postgres dialect to spanner. They mention it's not 100% compatible but it would be great have prisma add some documentation outlining limitations if any
https://cloud.google.com/spanner/docs/postgresql-interface

Nice.
(Note that the following does not indicate that we are committed to build a Google Spanner compatible connector any time soon. This is just me exploring and figuring out what might already work, and what does not. If Prisma will ever have this, and wants to spend more time on this, will be decided on a different level. I am just curious.)
Our next steps here would be to understand GCP enough to be able to have a Spanner instance with some schema and data in it, and enable the PostgreSQL interface. We would then try to run npx prisma db pull on it and see what fails (If it does not, we would probably still continue with a manually written schema of the database - starting with one table probably.) If it magically works out of the box, we would use the generated schema to send some manualy queries. If that also magically works, we could even try migrate dev after a small schema change to see what happens. And if that also succeeds we would then start to think how to integrate a Cloud only service into our test suite - but that is quite a bit off.
So if you understand GCP well, have a Spanner instance with data and the PostgreSQL interface enabled - please try these steps! (And/or send me an email at jan@prisma.io and send over the connection string, so we can do so at the side).

Tried to use PGAdapter and Spanner Emulator locally with Prisma using the following docker-compose file:
version: "3.3"
services:
  spanner:
    env_file: .env
    image: gcr.io/cloud-spanner-emulator/emulator
    ports:
      - '9010:9010'
      - '9020:9020'

  pg-adapter:
    image: gcr.io/cloud-spanner-pg-adapter/pgadapter:v0.6.1
    volumes:
      - ./test/fake-spanner-credentials.json:/acct_credentials.json
    ports:
      - 127.0.0.1:5432:5432
    command:
      - -p my_project
      - -i my_instance
      - -d my_database
      - -c /acct_credentials.json
      - -x

Getting this error:
Prisma CLI Version : 4.1.1
Error: Command failed: DATABASE_URL=cloudspanner:/projects/my_project/instances/my_instance/databases/my_database prisma migrate dev
Error: Get Config: Schema parsing - Error while interacting with query-engine-node-api library
Error code: P1012
error: Error validating datasource `db`: the URL must start with the protocol `postgresql://` or `postgres://`.
  -->  schema.prisma:6
   |
 5 |   provider = "postgresql"
 6 |   url      = env("DATABASE_URL")

So the problem is that PGAdapter requires connection url to start with cloudspanner:// while Prisma wants it to be postgresql://.
Using cloudspanner:// will error out on Prisma side.
Using postgresql:// will error out on PGAdapter side.

Adding an env var that allows cloudspanner:// as an alternative to postgresql:// (in a dev version maybe) would unblock this problem I guess @glebbash?

If there is no further validation for the rest of connection url: /projects/my_project/instances/my_instance/databases/my_database then yeah, it should work.

Thanks for clarifying that, we would indeed probably check for port and so on. So they way here would be to accept a completely different connection string. Interesting that psql seems to work for that out of the box (per PGAdapter docs). Can you share a full connection string that we would need to use?

Now that I think about which url would be okay for PGAdapter to work I am kinda lost, as it requires cloudspanner prefix and after that you would need to point to a local IP and port.
So theoretically it should be comething like cloudspanner://localhost:5432.
But there is a big chance that it wont work like that as PGAdapter docs say that only psql client is supported.

Has there been any updates / further thoughts on this @janpio?
Prisma should seriously consider supporting a Spanner connector.
The PostgreSQL interface for Cloud Spanner is now in GA and their basic pricing tier has dropped down to as low as $40/month.
Having a cheap, strongly consistent cross-region, ACID compliant, relational database is basically the holy grail, but unfortunately, many fast-moving teams will either overlook or avoid using Spanner because there is no Type-safe Node ORM that connects to it (despite the efforts by Google to provide the PostgreSQL Interface).
By supporting Spanner, Prisma has the opportunity to capture the market of large enterprise companies who use and/or want to use it with Node. This could then be leveraged as a funnel to drive these large customers towards your paid and enterprise offerings, which pays off the effort spent integrating Spanner.

This is currently not a priority for us.
If someone (@glebbash?) confirms that for example allowing cloudspanner:// as a protocol is all it needs to test this further, we might be happy to add that so we get to a better understanding where blockers will be. But w can currently not invest in figuring all this out or even implementing support unfortunately.

Hello,
I have setup a Spanner instance, with the PostgreSQL dialect.
When starting my app, I get the following error:
Error querying the database: db error: ERROR: Invalid SET statement: SET NAMES 'UTF8'. Expected TO or =.
I use DATABASE_URL="postgresql://127.0.0.1:5432/my-database" in my Prisma config.
Plus the following Docker container,
docker run \   -d -p 5432:5432 \   -v ${GOOGLE_APPLICATION_CREDENTIALS}:${GOOGLE_APPLICATION_CREDENTIALS}:ro \   -e GOOGLE_APPLICATION_CREDENTIALS \   gcr.io/cloud-spanner-pg-adapter/pgadapter \   -p my-gcp-project-id -i my-spanner-instance-id \   -x

Naive question, what is the quickest way to setup up the required GOOGLE_APPLICATION_CREDENTIALS?

I just tried the same thing as @etifontaine and got the same result.

Create a Google Cloud Account
Set up a Regional Spanner instance with 100 processing units ($0.09/h)
When it's done, create a database with PG Dialect. Remember the name.
Go to IAM > Services Accounts and create a new one with Owner Access.
Once created, click the 3 dots next to the new service account and 'Manage Keys'
Create a new JSON key, this will be your GOOGLE_APPLICATION_CREDENTIALS.
Follow the guide here and launch a local PGAdapter docker service. Below is the what I used. PROJECT_ID is found here. Spanner Instance ID is found under Spanner Tab and the database name is what you named it in step 3. CREDENTIALS_FILE_PATH is the downloaded JSON path from step 5.

docker run -d -p 5432:5432 \
    -v CREDENTIALS_FILE_PATH:/acct_credentials.json \
    gcr.io/cloud-spanner-pg-adapter/pgadapter:latest \
    -p PROJECT_ID -i SPANNER_INSTANCE_ID -d PG_DATABASE_NAME  \
    -c /acct_credentials.json -q -x

Create a basic node project with with the following

// prisma/schema.prisma
generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

// .env
DATABASE_URL="postgresql://localhost:5432/{DATABASE_NAME from step 3}"

// index.js
const { PrismaClient } = require('@prisma/client')
const prisma = new PrismaClient();

(async () => {
    const result = await prisma.$queryRaw`SELECT 1`
    console.log(result)
})()

Error querying the database: db error: ERROR: Invalid SET statement: SET NAMES 'UTF8'. Expected TO or =.
I also got the same error when trying.
npx prisma migrate dev --name init
--
When finished testing, make sure to delete your spanner instance. There is also a free trial for Spanner, but I have already used it. So testing for you may be free.

Some experimental work started over there: https://github.com/GoogleCloudPlatform/pgadapter/issues/589 + https://github.com/GoogleCloudPlatform/pgadapter/pull/590 <3

I'll add my two cents here - it would actually be nice to have a spanner native (non-postgres dialect) version. There are a few really interesting caveats to the way the postgres dialect works as have been noted in this thread. First, you have to run a separate process (the pgadapter) to do the translation, but secondly, there are actually some really important features missing when you use the postgres dialect - specifically, the change log that spanner produces and is consumable for CDC doesn't work with postgres (as I understand it). I also remember the journey we went through here for cockroach where, even though it said wire compatible, there are enough special things that prisma does that it didn't really work perfectly until there was a full, flavored release.

We fundamentally agree, but to explain why I am pushing on this: Native Spanner support is not happening for sure this year. If it turns out that the PgAdapter is close enough or can be adapted though, we could possibly find a way to make this usable sooner.

I think version() again is something the adapter could handle. It is one of the default system functions of PostgreSQL, which is why Prisma expects it to exist: https://www.postgresql.org/docs/current/functions-info.html#:~:text=to current_user.-,version () → text,-Returns a string
(We could rewrite our code to handle this not being present, but for normal PostgreSQL (and compatible databases) that is never expected to fail, so would be a bit weird - but we most probably could: https://github.com/prisma/prisma-engines/blob/af46365b40aa4864b99acec97dc2dd5bdc27411c/migration-engine/connectors/sql-migration-connector/src/flavour/postgres.rs#L562-L594)
I expect a few more of these to pop up on db pull as well, where Prisma queries a lot of the PostgreSQL system tables for information about the available tables and columns and so on.

I've mentioned this on the prisma support issue: https://github.com/GoogleCloudPlatform/pgadapter/issues/589

im running into similar errors when using pgadapter with prisma migrate
Error: Schema engine error:
db error: ERROR: Postgres function current_setting(text) is not supported - Statement: 'with pg_namespace as (
  select case schema_name when 'pg_catalog' then 11 when 'public' then 2200 else 0 end as oid,
        schema_name as nspname, null as nspowner, null as nspacl
  from information_schema.schemata
)
SELECT EXISTS(SELECT 1 FROM pg_namespace WHERE nspname = $1), '14.1', current_setting('server_version_num')::integer as numeric_version;'

fyi, i changed my url to be DATABASE_URL="postgres://postgres@127.0.0.1:5432/test_db?schema=transactions" which includes both the database name as well as the schema name, and npx prisma migrate dev --name init is able to run successfully.

Hello everyone, do you have any update on the Spanner support? Has anybody been able to make it work reliably with Prisma? 🙇♂

We recently tried to use Spanner as a Prisma backend but gave it up in the end. If I remember correctly, we couldn't make migrations work properly without more work than it was worth.
I'd love to hear if and how anyone got this to work properly

authors: NOT-HAL9000 etifontaine fuvidani glebbash janpio jhalborg jillxuu m3adow patwhite wgottschalk


text:
chore: revert "fix(sdk): avoid crash in prisma version, rename 'getVersion' -> 'getBinaryVersion' (#13737)"

This reverts commit 3718bfa2dbdc7c069de77fe07ce6cf0f624a9f15.
@jkomyno we will need to redo your PR after release and see what was causing that.

ecosystem-tests running at https://github.com/prisma/ecosystem-tests/actions/runs/2570503301 and 🟢


text:
refactor: remove __PRODUCTION__ and invariant; add tests for development environment

Types of changes

[x] Chore (a non-breaking change which is related to package maintenance)
[ ] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
This PR refactors the codebase by:

Replcing __PRODUCTION__ with direct access to process.env.NODE_ENV
Adds tests for the development environment

Checklist:

[ ] My change requires an update to the official documentation.
[x] All TSDoc comments are up-to-date and new ones have been added where necessary.
[x] All new and existing tests are passing.

Codecov Report

Merging #180 (2da0d38) into master (aac1cc7) will increase coverage by 0.19%.
The diff coverage is 88.23%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##           master     #180      +/-   ##
==========================================
+ Coverage   99.24%   99.44%   +0.19%
==========================================
  Files          21       20       -1
  Lines        2388     2332      -56
  Branches      129      126       -3
==========================================
- Hits         2370     2319      -51
+ Misses         18       13       -5

Impacted Files
Coverage Δ

src/lib/processPolyfill.ts
25.00% <25.00%> (ø)

src/SliceZone.tsx
98.57% <95.00%> (+0.96%)
:arrow_up:

src/PrismicImage.tsx
100.00% <100.00%> (ø)

src/index.ts
100.00% <100.00%> (ø)

src/react-server/PrismicLink.tsx
100.00% <100.00%> (ø)

src/usePrismicClient.ts
100.00% <100.00%> (ø)

authors: angeloashmore codecov-commenter

repo: prismicio/prismic-react


text:
fix: prevent jruby bundler from installing a test library with native extenstion.

there's a dependancy of bundler, racc this seems to be creating issues with jruby.
Using bundler -v 2.1.4 worked locally now to test it in travis.

note, adding the deployment flag will break a few things.
https://travis-ci.org/github/prismicio/ruby-kit/jobs/774521398

So there are a couple of issues here.
in our test suite we use a library nokogiri the requires native extensions: (c and java  for ruby and jruby respectively)
The good news it's only in the tests, the bad news is that it's buggy when installing in ci as the bundler version has to be correct for jruby or things break.
I would sujest looking for a non-native replacement for nokogiri

repo: prismicio/ruby-kit


text:
confDirName is never assigned

The instructions at https://github.com/privacybydesign/irma_api_server#configuring-the-server-without-docker don't work because the value confDirName is never assigned a value, resulting in it looking for places like /etc/null instead of /etc/irma_api_server.

Thanks for catching this! I guess I never noticed as I tend to explicitly define my configuration directories.
Although I appreciate that you submitted a fix, I think this problem should be fixed in a different way. Your fix (hardcoding the irma_api_server value in a private variable) would mean that other users of this library (such as our keyshare server or email attribute issuer) would also look at /etc/irma_api_server for its configuration without it having the ability to change of switch off this behaviour. Instead I think this variable should be public, so that the irma_api_server can provide a value like it already does for the other public variables. I'll push this shortly.

authors: PaulWagener sietseringers


text:
🛑 Webseite is down

In 952480f, Webseite (https://www.edvgarbe.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Webseite is back up in 1268cef.

repo: privatereese/upptime


text:
Added a test for local storage library (Level 2)

Added a test for the local storage to check whether the it  returns undefined  when deleting a data that doesn't exist
Also fixed a typo in the description of the first test

This PR includes the changes from your other PR. In the future, please develop them on separate feature branches and allow the maintainer to handle merging them.

Fixed that
https://privlyalpha.org/apps/Message/show?privlyApp=Message&privlyInject1=true&random_token=5270ed1d2d&privlyDataURL=https%3A%2F%2Fprivlyalpha.org%2Fposts%2F2173.json%3Frandom_token%3D5270ed1d2d#privlyLinkKey=fLduvgyxE7gKbiHrYSmygfnMTo9YKUuG9kcrY25mrGU=

You fixed one of the problems. What are you going to do about having two PRs included in this one? I recommend removing the commit from this branch's history since I haven't fetched your changes yet..
Feel free to dogfood comments, but I don't generally expect/want privacy on GitHub comments since the ability to search GitHub issues is important.

So I remove the commit from the branch and PR another branch with just the stipulated changes :grey_question:

If you don't comment about the changes you made to the PR, it won't make its way back into the review queue.

@smcgregor Sorry about that
[c72dfa7] (https://github.com/jatindhankhar/privly-applications/commit/c72dfa76a4631f9f260682924d4709e3463af9f1) - Fixed the indentation issue
7aedb2a - Removed the quotation marks

For my reference, this is ready to merge with the exception of the whitespace in the testing file. I should squash the commits, then update the testing file's whitespace and merge.

Do you want to squash the commits? It removes you from the commit history. If you don't care then I can take care of it.

What should be the best way ?
I'll do it :)

You should squash the commits using git. I think these answers give some guidance, but leave another comment if something isn't making sense: http://stackoverflow.com/questions/5189560/squash-my-last-x-commits-together-using-git

So I went through several SO answers and most of them suggested to use interactive mode to make things simpler. However I found this blog very helpful.
Still listing down the steps, so to have a log for future references. Here are the steps I followed

Pull all the branches of my forked repo locally , followed this SO thread to get these commands

for remote in `git branch -r`; do git branch --track $remote; done
git fetch --all
git pull --all

Generated the digested log of the changes between master and testing-level-2-patch using the following command

 git log --oneline remotes/origin/master..remotes/origin/testing-level-2-patch

7aedb2a Updated new.html.subtemplate
c72dfa7 Update local_storage.js
141866f Updated local_storage.js
73d404e Added Test for local storage
f6a95e4 Updated new.html.subtemplate
d27c450 Update Sub Template for New Help

Next and final step was to rebase files and using the command
git rebase -i remotes/origin/master
gave me

pick d27c450 Update Sub Template for New Help
pick f6a95e4 Updated new.html.subtemplate
pick 73d404e Added Test for local storage
pick 141866f Updated local_storage.js
pick c72dfa7 Update local_storage.js
pick 7aedb2a Updated new.html.subtemplate

# Rebase 854ccad..90d3629 onto 854ccad

and changed pick with s (squash)
pick d27c450 Update Sub Template for New Help
s f6a95e4 Updated new.html.subtemplate
s 73d404e Added Test for local storage
s 141866f Updated local_storage.js
s c72dfa7 Update local_storage.js
s 7aedb2a Updated new.html.subtemplate

# Rebase 854ccad..90d3629 onto 854ccad

Then I was dropped to message window for commits, and I replace all the messages with a short message  (or do I have to let commit messages be as it is ? )
Are these steps okay ?
For now changes I made are local, and are not  pushed to Github. Let me know if these are okay to be pushed

I think so, but it is difficult to say for certain without more time investment. I think you should push the changes to remote and we'll see what happens. If things go wrong, we'll close this PR and open a new one based on master.

Pushed the changes. Learned more about git in this one week than I did in one year.
Little note for me
If you want all branches of a repo and don't want the local names like remotes/origin/testing`` which could pose problems during push (may create a new repo with name origin/testing```
Recommended while fresh cloning
for branch in `git branch -a | grep remotes | grep -v HEAD | grep -v master `; do
   git branch --track ${branch#remotes/origin/} $branch
done

Source

The pull request still has 11 commits on it. Is this the case when you look at the history of your branch locally?

Yes it shows two commits, may because of merging it with the same branch from github before pushing, as all changes were not synced.

Logs

Should I squash the commits again into one ?

Hi @smcgregor sir, @jatindhankhar ,
Sorry if I am intruding here. I have been following all PRs and issues. Jatin, I feel you should squash commits using the following command:
git reset --soft HEAD~4 &&
git commit

Replace 4 with the number of last X commits you want to squash and then force push it to this branch using git push -f. Sir, please correct me if I am wrong.
Reference: SO link
Also I see this branch has merge conflicts with my last PR for level 2 which need to resolved.

Did that @ManrajGrover.Thanks for the help :+1:
I squashed the latest 8 commits of testing-level-2-patch branch int one (See commit )
Not sure whether it did more good or bad (no offence), as now pull request contains merge conflicts.
Also it force push rewrites the public history, so don't know how much it is welcomed in collaborative environments.
@smcgregor Please look into this :sweat_smile:

I believe you squashed the commits after you rebased on master. This means you pulled in changes that were made on master, then you squashed these changes into your commit. Now you are effectively trying to make the changes that have already been made. I think the way to proceed is to create a new local branch based on master, then to copy/paste your changes from Help/new.html.subtemplate, commit the changes, then force push this new branch to the remote testing-level-2-patch branch. This will remove all the unneeded changes and rewrite history in this pull request.
It is generally bad form to rewrite history on a remote, but the change is sufficiently localized that I am not worried about maintaining history.

So I did it
Tried this from the fix-sqaushes branch (I mispelled squashes :sweat_smile: )
git push origin testing-level-2-branch -f but it said Everything up to date
Finally found this SO answer which said to do this
git push origin fix-sqaushes:testing-level-2-patch -f  and it  worked

I still see 5 commits. Are you not going to squash?

Sorry, I followed your instructions too literally. I am having problems squashing the commits (or I am confused about this whole squashing thing). Commits to cherry pick are distributed far away between logs. Maybe you can help me fix this. As you said earlier
Do you want to squash the commits? It removes you from the commit history. If you don't care then I can take care of it.. I don't care much about appearing in commit history. Moreover, this discussion has become too big and might be hindering your productivity

I'm happy to help (assuming I am actually being helpful), but yes it has become more an academic exercise.
If you want to make this easy create a new pull request from a fresh checkout of master.
git checkout master
git checkout -b reword-help-messages
# copy your changes to the subtemplate file
git add Help/new.html.subtemplate
git commit -m "Made help messages more informative"
git push origin reword-help-messages

Then open a new pull request that references this one in the comments.
...or I could do this myself, it is up to you.

It's good to hear that you are happy to help me despite having other important tasks but I would like you to do this and close this PR for final as even if the task is dead simple, I may eventually goof up things :sweat_smile: :
Will find other PR's, ways to bother/help Privly Org :smile:

Done.
https://github.com/privly/privly-applications/commit/7c0c875e8ec3a12db5ea4531de4b10a30990b4e1

authors: ManrajGrover jatindhankhar smcgregor

repo: privly/privly-applications


text:
♻ Refactor routes

As of react-router-dom v6 we no longer need to add exact to our routes, as it is the default behavior now.
Reference - Point Number 3

Hi @priyankarpal, please assign this to me.

repo: priyankarpal/ProjectsHut


text:
added-c-project

Related Issue
closes #428
Description
added my C programs
Screenshots
nil

please add your projects here you can check the docs for more information

Why does every time quality check keeps failing, even after the pnpm format command?

Why does every time quality check keeps failing, even after the pnpm format command?

yes

authors: akkshayTandon priyankarpal


text:
adddata feature

For plotting intervals, the default behavior is to plot the data if it is included

Pull Request Test Coverage Report for Build 461

2 of 4 (50.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.07%) to 97.555%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pymcmcstat/propagation.py
2
4
50.0%

Totals

Change from base Build 459:
-0.07%

Covered Lines:
2593

Relevant Lines:
2658

💛  - Coveralls

authors: coveralls prmiles

repo: prmiles/pymcmcstat


text:
Add weekly selection option

Hi @probablykasper ,
I had a need to add weekly selection to the date picker and added it. I'm not sure at all if this is even anything that you'd be interested in but I'll just create a PR if this is interesting for the library!

Let me know what you think.
✌🏻 Adam

Not something I want added, but looks cool! Feel free to publish your own package

authors: adamnyberg probablykasper

repo: probablykasper/date-picker-svelte