profile
viewpoint

nuxt/nuxt.js 26155

The Vue.js Framework

nuxt-community/typescript-template 457

Typescript starter with Nuxt.js

nuxt-community/micro-template 72

Starter template for Nuxt.js with Δ micro

nuxt-community/webpack-profile-module 7

Nuxt module to display webpack build progress steps with core ProgressPlugin

qm3ster/broccoli-pug-render 3

Broccoli.js plugin to render Pug templates

qm3ster/linnertmedia 3

Static version of linnertmedia.de

qm3ster/jest-buffer-snapshot-serializer 1

A jest snapshot serializer for buffers

qm3ster/ajv 0

The fastest JSON Schema Validator. Supports draft-04/06/07

qm3ster/ajv-pack 0

Produces a compact module exporting JSON-schema validation functions compiled by Ajv

qm3ster/awesome-vue 0

A curated list of awesome things related to Vue.js

issue commentrust-lang/futures-rs

zip_latest Stream adapter

  1. This would require the items to be Clone, right? Because they can't be borrows?
  2. I currently solved my need for such an operator with this, based on async_stream::stream! and tokio::select!. It does look kinda verbose, but it gives you a lot of other opportunities, and doesn't impose any limits on the Item. I'm not sure that I would prefer a separate adapter that gives me a tuple, even when I'm working of signals of primitive types. (In RxJS I have at first had quite the number of problems with one of the inputs not having a value for a long time, blocking the entire stream. I don't think startWith on inputs or outputs is an improvement over setting default values or yielding something in the post-select! section when certain values are still not ready.
stephaneyfx

comment created time in 4 days

startedbe5invis/Iosevka

started time in 4 days

startedmunrocket/overload-bracket

started time in 7 days

startedwessberg/rollup-plugin-ts

started time in 8 days

issue commentbabel/babel

[Feature Request] Add "preserveConstEnums" option to transform-typescript

Why is removeConst the default? What are the tradeoffs? (considering the transform-typescript doesn't typecheck anyway)

ForbesLindesay

comment created time in 8 days

issue commentinfluxdata/influxdb

Set Telegraf hostname from enviromental variable

I did

docker exec influxdb influx pkg export --telegraf-configs 05656e888c6f2000 > temp.yml
code -w temp.yaml
docker exec -i influxdb influx pkg -o daid  < temp.yml
rm temp.yml

Wherein I obtained 05656e888c6f2000 from Setup Instructions in the UI. This created an updated Telegraf besides the original one, with a different ID. Shouldn't I want to update the same ID, so that daemons can reload it on restart?

qm3ster

comment created time in 12 days

issue openedinfluxdata/influxdb

Set Telegraf hostname from enviromental variable

Seems like influxdb v2 load-data/telegrafs currently creates configs like the following:

  hostname = ""
  omit_hostname = false

When using such a config in a telegraf docker container, it takes on the hostname of the container and not the docker host. This can obviously be undesirable when it is used as the telegraf instance for the host. I imagine that by setting it to something like "$TELEGRAF_HOSTNAME" this could easily be solved, while retaining the existing behavior if the env var is unset?

created time in 13 days

issue openedEmpty2k12/influxdb-rust

Influxdb v2

Is it within the scope of this project to support InfluxDB v2.0.0?

created time in 13 days

issue openedinfluxdata/influxdb

Updates to 2.0.0-beta-alpine?

Henlo, I noticed that nightly-alpine builds just as often and just as well as nightly, but 2.0.0-beta-alpine has not been updated for months (unlike the debian-based image). Is this intentional?

created time in 13 days

issue commentgrafana/grafana

[hover tooltip]-values are rounded

Should that apply to Explore view too? image

HarmOtten

comment created time in 14 days

push eventqm3ster/zigbee-herdsman-converters

Koen Kanters

commit sha e606ece16ba3ff0171a4332641a52ca67323b786

Add LifeControl devices. https://github.com/Koenkk/zigbee2mqtt/issues/3108

view details

Koen Kanters

commit sha d0be67918410571cac6c1f02f82e463feb4f668c

Add HOMA0019 zigbeeModel for HLC610-Z. https://github.com/Koenkk/zigbee2mqtt/issues/3109

view details

Koen Kanters

commit sha 5438a9ee4c45a9ca6a51230601d0049ba7341407

12.0.45

view details

Mihail Malo

commit sha cea437cd4862492b57d47690b7da2170d47aceae

Let npm resolve eslint "binary" (#1061) YEET Makes compatible with pnpm

view details

Mihail Malo

commit sha 2f97a350231d80c742a3457d263de19aa800a793

Prevent Xiaomi reset on long press (#1060) Respond to long press like stock hub does. Currently added behavior only to devices I own, but most likely applies to "without neutral" variants as well, since those lie inbetween battery and "with neutral" devices. Tested, really prevents escape.

view details

r1cht3r

commit sha 706623903b31270d0c381ee69c4459e1a46d38bf

add Centralite 3323-G Micro-Door sensor (#1058) * add Centralite 3323-G Micro-Door sensor * removing fz.centralite_3323G_contact * remove genPowerCfg * Update devices.js Co-authored-by: Jason Ramey <ramey@helpscout.com> Co-authored-by: Koen Kanters <koenkanters94@gmail.com>

view details

Stuart Vickers

commit sha d41c24df95c1c443c227d3b9c53ea38803c6ee8f

Added Linkind E14 C35 LED Bulb (#1062) * Added Linkind E14 C35 LED Bulb * Update devices.js Co-authored-by: Koen Kanters <koenkanters94@gmail.com>

view details

Kryzek

commit sha e2218b29e2b60a2fea9dce2a3be80fb6ba28c4fb

Update devices.js (#1063) * Update devices.js Per https://github.com/Koenkk/zigbee-herdsman-converters/issues/1059 I did not touch model or vendor. This setup works with my device (Lonhonso branded device model X702). * Update devices.js * Update devices.js Co-authored-by: Koen Kanters <koenkanters94@gmail.com>

view details

Koen Kanters

commit sha b85c73640fec7982ac455a994c2d9a5439cea988

12.0.46

view details

qm3ster

commit sha b0008fa323e9811f95488c3274542f278ece804c

Update documentation

view details

push time in 15 days

push eventqm3ster/zigbee-herdsman-converters

qm3ster

commit sha f8c9ea088821009031890aa8ef0f26cde087b6fe

Update documentation

view details

push time in 15 days

PR opened Koenkk/zigbee-herdsman-converters

Let npm resolve eslint "binary"

YEET Makes compatible with pnpm

+2 -2

0 comment

2 changed files

pr created time in 16 days

create barnchqm3ster/zigbee-herdsman-converters

branch : scripts-eslint

created branch time in 16 days

issue closedvuejs/awesome-vue

Add REAM

As far as I could see, REAM (ream.js.org) is missing. It should probably be featured alongside Nuxt.js, which perhaps also deserves a more prominent spot.

closed time in 16 days

qm3ster

issue commentvuejs/awesome-vue

Add REAM

@Scrum deprecated in favor of https://vapperjs.org/ @egoist lol

qm3ster

comment created time in 16 days

pull request commentKoenkk/zigbee-herdsman-converters

Prevent Xiaomi reset on long press

(eslint)

qm3ster

comment created time in 16 days

push eventqm3ster/zigbee-herdsman-converters

qm3ster

commit sha 66a2141f225ecc2b5d94063110ddf53c33f4aa88

Prevent Xiaomi reset on long press Respond to long press like stock hub does. Currently added behavior only to devices I own, but most likely applies to "without neutral" variants as well, since those lie inbetween battery and "with neutral" devices. Tested, really prevents escape.

view details

push time in 16 days

PR opened Koenkk/zigbee-herdsman-converters

Prevent Xiaomi reset on long press

Respond to long press like stock hub does.

Currently added behavior only to devices I own, but most likely applies to "without neutral" variants as well, since those lie in-between battery and "with neutral" devices.

Remaining questions:

  1. This does not prevent kicking from the network, but some crazy people might still want it configurable. For this options (device specific configuration) needs to be passed to onEvent or I need a way to obtain it using the passed in device. Or, does this need to be dynamically configurable via mqtt?
  2. Maybe I should blindly add this to more devices, otherwise we need testers with device / sniffers with device and hub / someone to send me a device. Shouldn't be any harm.
  3. It's not clear what the contents of the message actually are, and when they might change.

[0xaa, 0x10, 0x05, 0x41, 0x87, 0x01, 0x01, 0x10, 0x00] On wired devices in the report, the last octet is always 0, and the "counter" octet (after 0x84) is always 1. On wireless buttons, the last octet was 1 (like in the write response from hub) and the counter was incremented on the device side, sometimes by 2. The write response always has 0x47 instead of 0x87, so that bit is moved, always 1 in the last octet, and is generally identical for all devices tested, just merrily incrementing the counter (IIRC globally, for any device it sends this to). Not incrementing the counter didn't interfere with the functionality of this PR, even if the response value was less than that in the report, so its purpose remains unknown.

It might be worthwhile to mess around more with what we send and see what works, but currently the goal is achieved. I tested this with CC2531 to not disturb my production networks.

+24 -0

0 comment

1 changed file

pr created time in 16 days

create barnchqm3ster/zigbee-herdsman-converters

branch : xiaomi-no-escape

created branch time in 16 days

push eventqm3ster/zigbee2mqtt

Koen Kanters

commit sha 58d987b52328a40b6ac92f343f3e8ceeae3f2a10

Implement update_available attribute and discover Home Assistant sensor. #2948

view details

Koen Kanters

commit sha f0903cd02cd18a58c37a72a2a3a0d1cbfca52e00

Discover action sensor for WXKG11LM. #2953

view details

Takisg

commit sha 6ef4fac30aa94741c4180e6c6cd294fa588c4244

GL-C-007S (#2955) Gledopto GL-C-007S Add support for Gledopto GL-C-007S Zigbee LED controller RGBW plus model

view details

Koen Kanters

commit sha 2b3cdebe41c1dd269b6bb0608fd9818c2a141df9

Fix AC08559 missing Home Assistant colorxy mapping. #2966

view details

Koen Kanters

commit sha 0289a6c30de7217f382ffac49896fa94900601c6

Update converters.

view details

Koen Kanters

commit sha 9b644ff82d51fde89e5e9aa86926d94419f9d70b

Update herdsman.

view details

Koen Kanters

commit sha c25c32f1be28487f17e74ae5e5ba4505eb8ce5b6

Update converters.

view details

Koen Kanters

commit sha 6b5b4ab4332343b5b42ba889c7dbfd6434bdd772

Log when update is availabe. https://github.com/Koenkk/zigbee2mqtt/commit/58d987b52328a40b6ac92f343f3e8ceeae3f2a10#r37363068

view details

Koen Kanters

commit sha df67c429bf90737e87b062b827997a190f5dc923

Undiscover ota_update sensor on device remove.

view details

Koen Kanters

commit sha ad59ff57bc14c1d791d48b9d0911dd220445a0a1

Also remove group from herdsman on remove. #2265

view details

Koen Kanters

commit sha 79116a1158b3aa1e10594098881195cc22aae0a5

Fix Hue bulbs in a group controlled by a Hue dimmer not reporting off state. #2882

view details

Koen Kanters

commit sha aca32e2f02a76c2f58427477c6f57bb227ed8338

Update converters.

view details

shades684

commit sha 409df4c193adcd37c2eef75ac234728ff2e2473b

Matches this pull request: https://github.com/Koenkk/zigbee-herdsman-converters/pull/1010 (#2988)

view details

Koen Kanters

commit sha 645da4e3c0115715de44cd47e1356a99af52f67c

Update herdsman.

view details

Koen Kanters

commit sha 66173ff6894e9d563488d9d1c9a297de4f240b0a

Update herdsman.

view details

Koen Kanters

commit sha 2a9d0d1875950db45771584884caadfb69308e68

Update converters. https://github.com/Koenkk/zigbee2mqtt/issues/2921

view details

Koen Kanters

commit sha dd82b29629b716bd6c1e33f6b5d5f2837e3c5a2c

Update converters. https://github.com/Koenkk/zigbee2mqtt/issues/2967

view details

Koen Kanters

commit sha 9cc84feb676dbc0a7bf0ee125756b537433d3c59

Allow to rename groups through zigbee2mqtt/bridge/config/rename. https://github.com/Koenkk/zigbee2mqtt/issues/2991

view details

Koen Kanters

commit sha a36f11a4fbd205f573d6b56ce727534ab181ee06

Update converters.

view details

Koen Kanters

commit sha 95788b8847e796608c63c5b0f2a56de2ef19f008

Discover illuminance_lux sensor.

view details

push time in 16 days

fork qm3ster/zigbee-herdsman-converters

Collection of device converters to be used with zigbee-herdsman

fork in 16 days

CommitCommentEvent

push eventqm3ster/svelte-router-example

snyk-bot

commit sha e1f429cebf78a0ca680ecc6812f822e385b28dcb

fix: package.json & yarn.lock to reduce vulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-MINIMIST-559764

view details

push time in 17 days

startedConfusingboat/ros-uefi

started time in 19 days

delete branch qm3ster/rumq

delete branch : patch-2

delete time in 20 days

starteds-panferov/observe

started time in 24 days

issue commenttekjar/rumq

Reconnection issue

It's just that the only branch that could reset await_pingresp as successfully getting a pingresp, and the branch that made a pingreq asking for one was conveniently the only thing blocked by checking for this error. But no one else checked for it, so it didn't actually interfere with handling any other packet (unless I myself got spooked by the error and dropped the eventloop)

mojzu

comment created time in a month

issue commenttekjar/rumq

Reconnection issue

@mojzu were you still getting some or all messages (together with the repeating error)? Or did this error completely block incoming in your case?

mojzu

comment created time in a month

issue commentpnpm/pnpm

Alpine Linux - pnpm package

Has the blessed docker image taken place yet?

f3l1x

comment created time in a month

startedSimonSapin/rust-typed-arena

started time in a month

delete branch qm3ster/rumq

delete branch : patch-1

delete time in a month

PR opened tekjar/rumq

Reset self.await_pingresp if we miss ping response

We missed the ping. It's over. It's never coming back. The only thing we can do is send a new request, and wait for the response to that one.

tentatively fixes #34

+1 -0

0 comment

1 changed file

pr created time in a month

push eventqm3ster/rumq

Mihail Malo

commit sha cfb59944737099e45fa8338dee649be2338b1127

Reset self.await_pingresp if we miss ping response We missed the ping. It's over. It's never coming back. The only thing we can do is send a new request, and wait for the response to that one.

view details

push time in a month

issue commenttekjar/rumq

Reconnection issue

"minimum" repro:

use rumq_client::MqttOptions;
use rumq_client::QoS::AtLeastOnce;
use std::time::Duration;
use tokio::stream::StreamExt;
use tokio::sync::mpsc;
use tokio::time::delay_for;
#[tokio::main]
async fn main() {
    let mut options = MqttOptions::new("Obama", "10.22.22.6", 1883);
    options
        .set_credentials("mqttuser", "mqttpass")
        .set_keep_alive(5);
    let (mut req_tx, req_rx) = mpsc::channel(10);
    let mut eventloop = rumq_client::eventloop(options, req_rx);
    loop {
        let mut stream = eventloop.stream();
        while let Some(notif) = stream.next().await {
            println!("{:?}", notif);
            use rumq_client::Notification as N;
            use rumq_client::Request as R;
            use rumq_client::{publish, subscribe};
            let req = match notif {
                N::Connected => Some(R::Subscribe(subscribe("in", AtLeastOnce))),
                N::Publish(pubar) => Some(R::Publish(publish("out", AtLeastOnce, pubar.payload))),
                _ => None,
            };
            if let Some(req) = req {
                req_tx
                    .send(req)
                    .await
                    .expect("`requests` dropped by eventstream")
            }
        }
        eprintln!("stream ended, retrying in 100ms");
        delay_for(Duration::from_millis(100)).await;
    }
}
[package]
name = "min-example"
version = "0.1.0"
edition = "2018"

[dependencies]
rumq-client = "0.1.0-alpha.5"
tokio = {version = "0.2.11", features = ["stream", "macros", "sync"]}

Output:

Connected
Suback(Suback { pkid: PacketIdentifier(1), return_codes: [Success(AtLeastOnce)] })
StreamEnd(MqttState(AwaitPingResp))
stream ended, retrying in 100ms
StreamEnd(Timeout(Elapsed(())))
stream ended, retrying in 100ms
Connected
Suback(Suback { pkid: PacketIdentifier(2), return_codes: [Success(AtLeastOnce)] })
StreamEnd(MqttState(AwaitPingResp))
stream ended, retrying in 100ms
Connected
Suback(Suback { pkid: PacketIdentifier(3), return_codes: [Success(AtLeastOnce)] })
StreamEnd(MqttState(AwaitPingResp))
stream ended, retrying in 100ms
Connected
Suback(Suback { pkid: PacketIdentifier(4), return_codes: [Success(AtLeastOnce)] })
StreamEnd(MqttState(AwaitPingResp))
stream ended, retrying in 100ms
Connected
Suback(Suback { pkid: PacketIdentifier(5), return_codes: [Success(AtLeastOnce)] })
Publish(Topic = in, Qos = AtMostOnce, Retain = false, Pkid = None, Payload Size = 8)
Puback(PacketIdentifier(6))
StreamEnd(MqttState(AwaitPingResp))
stream ended, retrying in 100ms
Connected
Suback(Suback { pkid: PacketIdentifier(7), return_codes: [Success(AtLeastOnce)] })
Publish(Topic = in, Qos = AtMostOnce, Retain = false, Pkid = None, Payload Size = 8)
Puback(PacketIdentifier(8))
StreamEnd(MqttState(AwaitPingResp))
stream ended, retrying in 100ms
Connected
Suback(Suback { pkid: PacketIdentifier(9), return_codes: [Success(AtLeastOnce)] })
StreamEnd(MqttState(AwaitPingResp))
stream ended, retrying in 100ms
Connected
Suback(Suback { pkid: PacketIdentifier(10), return_codes: [Success(AtLeastOnce)] })
mojzu

comment created time in a month

PR opened tekjar/rumq

Enable "stream" tokio feature

Required by tokio::time::throttle

+1 -1

0 comment

1 changed file

pr created time in a month

push eventqm3ster/rumq

Mihail Malo

commit sha d4bcf0a84a269f3be4b75cf0b11f88e5cfaf0376

Enable "stream" tokio feature Required by `tokio::time::throttle`

view details

push time in a month

fork qm3ster/rumq

Mqtt ecosystem in rust

fork in a month

issue commenttekjar/rumq

Reconnection issue

I feel like I'm in the same boat. If a packet is dropped (eg if I unplug the cable) and I get even a single AwaitPingResp, I keep getting AwaitPingResp forever (which causes the stream to break), despite actually having a valid connection (I get Subacks, and Publishes and everything)

mojzu

comment created time in a month

issue openedtekjar/rumq

Expose state somewhat

In https://github.com/tekjar/rumq/blob/8c20d58523bcd5ca74c823a9f20c0f3dc5a04393/rumq-client/src/eventloop.rs#L72-L76, it is alleged that options, state and requests can be accessed and even updated, at least in case of error. However, these fields of MqttState are private, and none of the component are returned in error variants or anything.

Maybe fn stream should consume the MqttState so that it can only by accessed when the stream isn't polled?

created time in a month

issue commentKoenkk/zigbee-herdsman

Allow permit join to router

Isn't this https://github.com/Koenkk/zigbee-herdsman/commit/0015e9cbb1056e90937e75701c7d5d1bdbc7fc93

kirovilya

comment created time in a month

CommitCommentEvent

fork qm3ster/zigbee2mqtt

Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨

https://www.zigbee2mqtt.io

fork in a month

issue commentKoenkk/zigbee2mqtt

Feature request 'genTime' and type 'read' and data '["time"]'

The lines have moved, it's this: https://github.com/Koenkk/zigbee-herdsman/blob/7650ad1bff19ca738fc7a02d5ad9153916935dc9/src/controller/controller.ts#L525-L550

edillmann

comment created time in a month

startedslackhq/nebula

started time in a month

startedskalavala/mysmarthome

started time in 2 months

startedtekjar/rumq

started time in 2 months

issue commentrust-lang/backtrace-rs

Cross compilation fails on Windows because of missing `ar` command prefix.

I just had the same problem with ring, building for aarch64-unknown-linux-musl using https://win.musl.cc/ and https://www.msys2.org/. I managed to build by making a symlink: mklink ar.exe aarch64-linux-musl-ar.exe. Is there a proper solution? Setting neither AR nor aarch64_unknown_linux_musl did anything.

nikonthethird

comment created time in 2 months

issue commentrust-lang/rust

Cannot cross-compile aarch64-musl on x86_64 linux

@ciofeca's solution worked for me on Windows I still had to mklink ar.exe aarch64-linux-musl-ar.exe for the moment, not sure how to get gcc to ask for the right one.

asonix

comment created time in 2 months

startedreverieline/CC2538-CC2592-ZNP

started time in 2 months

issue commentayufan-rock64/linux-build

Disable debug console on serial 1 and enable it for serial communications

sudo systemctl mask serial-getty@ttyS2 worked. disable didn't, it would just come back upon reboot.

gnitzan

comment created time in 2 months

startedyene/knxproj

started time in 2 months

starteduwearzt/knx_rs

started time in 2 months

push eventqm3ster/zigbeer-rs

qm3ster

commit sha b8675d5e27a845cd317b1a2aff44d17b64ada185

Update to tokio 0.2 release

view details

push time in 2 months

issue closeddilame/instagram-private-api

How to send a video as a direct?

Henlo, trying to make a DM out of an mp4.

Based on what I found here: https://github.com/dilame/instagram-private-api/blob/d5fc6a7a2c6b2aefa639bee53195886102ac5c7b/src/entities/direct-thread.entity.ts#L50-L62

I tried:

    const vidUp = await ig.upload.video({
      video: await fs.readFile(
        path.resolve(__dirname, "../data/SampleVideo_1280x720_1mb.mp4")
      ),
      duration: 5312,
      height: 720,
      width: 1280
    })
    console.log("vidUp", vidUp)

The video upload process returns: vidUp { xsharing_nonces: {}, status: 'ok' } (no upload_id in response body)

I based configure_video not just on similarity, but also these lines from mgp25/Instagram-API (see URL).

Not sure what video_result there stands for.

It's strange I am not getting an upload_id back despite the 'ok', it seems to be expected.

I also tried this:

    const uploadId = "1568498701788"
    const vidUp = await ig.upload.video({
      uploadId,
      video: await fs.readFile(
        path.resolve(__dirname, "../data/SampleVideo_1280x720_1mb.mp4")
      ),
      duration: 5312,
      height: 720,
      width: 1280
    })
    console.log("vidUp", vidUp)
    console.log("uploadId", uploadId)
    const res = await ig.directThread.broadcast({
      item: "configure_video",
      form: {
        upload_id: uploadId
      },
      threadIds: "340282366841710300949128112692906930936"
    })

which is probably stupid since the ID I should get back is probably different than the option ID. (I didn't check in the photo case, but the current code uses the returned one.) Anyway, this gives 403 Forbidden (probably because I am referencing someone else's or nonexistent video upload).

closed time in 3 months

qm3ster

startedsimple-icons/simple-icons

started time in 4 months

delete branch qm3ster/examples

delete branch : event-emitter-no-promisify

delete time in 4 months

issue commentnuxt-community/typescript-template

Saperate the script in vue files to .ts files.

@lsotoangeldonis what's in navbarCategoriesComponent.ts?

hannanmumtaz

comment created time in 4 months

issue closedberkowski/tokio-serial

Futures 0.3

Are there any plans to convert to core futures (implementing the AsyncRead and such from futures crate instead of tokio) or will this project wait for tokio to switch first?

closed time in 4 months

qm3ster

push eventqm3ster/rust-wasm-capnproto-example

snyk-bot

commit sha 1ce74767813c27e453328b8979c0ff58d73d956b

fix: package.json to reduce vulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/npm:qs:20170213

view details

push time in 4 months

issue openedmoonlight-stream/moonlight-qt

Expose Video Stream

Describe the solution you'd like I would like an option to connect to a Game Stream computer and just get the video stream, for example as a DirectShow device on Windows or v4l device on linux, without sending control back. This would be very useful for streamers with a 2-PC setup, as the performance of and efficiency GameStream is on par with NDI, while supporting non-cinema resolutions like 1440p. (NDI encoded though OBS has worse quality than either of these)

Describe alternatives you've considered Forking the RTMP stream or exposing an RTMP server could also work, whichever is easier. (possible duplicate of #142, which however is about recording).

created time in 4 months

startedrsaxvc/LowLatencyVideoPrototype

started time in 4 months

issue commentbalena-io/etcher

libgconf-2.so.4 missing on Ubuntu 18.02 Beta

Does libgconf2-4 package just pull in libgconf-2-4 or does it do anything else? Not sure how to check.

probonopd

comment created time in 5 months

issue commentqm3ster/zigbeer-rs

interoperability with rust's zigbee "common interface for the interoperability"

@garro95

  1. Where can I contact you in a more realtime fashion?
  2. Do you have any Zigbee dongles/end devices?
akrpic77

comment created time in 6 months

push eventqm3ster/zigbeer-rs

qm3ster

commit sha 4e56baf98597c4c51a4f326b8f38b95198cb5652

Add interrogation commands, concept of sender

view details

push time in 6 months

push eventqm3ster/zigbeer-rs

qm3ster

commit sha 7b8cf96cd7cbc117cc5ed8b034eb41c93febebf7

Fix FrameControl order

view details

qm3ster

commit sha 9091284500f6fae88a1b8573fd9118d061390e40

Rename UnimplementedCmd to UnknownCmd

view details

qm3ster

commit sha 8c888b169cfc1a1820187cfc682ef41cd1b66a8d

Replace `for_each` with `while next()`

view details

qm3ster

commit sha 5b2181a757b7bc035c89425a8252f000dffba06b

Add more clusters, commands, value types

view details

push time in 6 months

issue commentqm3ster/zigbeer-rs

interoperability with rust's zigbee "common interface for the interoperability"

@akrpic77 I am probably going to continue this project now, do you know anything about the status of standardization of a Zigbee interface in Rust, or what @garro95 is up to now?

akrpic77

comment created time in 6 months

push eventqm3ster/zigbeer-rs

qm3ster

commit sha 673a5299c047d21f44e3cd513173afc676ec53a6

Bulkhead before tokio 0.2

view details

qm3ster

commit sha deb64ae3ab7705b2968ddfd591ebde0434014802

Update to tokio 0.2 Also updated other dependencies

view details

push time in 6 months

issue commenttokio-rs/tokio

framed with framed

I only find examples for sync adaptors: AES, Cryptostream, gzip. But it seems the differences would be very small, you just have to poll the underlying Read instead of blocking on it.

nnovikov

comment created time in 6 months

issue commenttokio-rs/tokio

framed with framed

Do these shorter buffers each contain exactly one serialized struct? Exactly multiple? Or can these structs be fragmented across the buffers you are producing?

nnovikov

comment created time in 6 months

issue commenttokio-rs/tokio

framed with framed

It doesn't sound like you need another Framed. What is the type of Item your Decoder produces?

nnovikov

comment created time in 6 months

pull request commentdilame/instagram-private-api

Add ListReelMediaViewerFeed and DirectThreadEntity.broadcastVideo()

So, in #891, by not having direct_v2 = '1' I was uploading it in a way that would never be accessible to a DM? For future reference, where did you get this information from?

Also, what does the "sampled" option mean?

Nerixyz

comment created time in 6 months

issue openeddilame/instagram-private-api

How to send a video as a direct?

Henlo, trying to make a DM out of an mp4.

Based on what I found here: https://github.com/dilame/instagram-private-api/blob/d5fc6a7a2c6b2aefa639bee53195886102ac5c7b/src/entities/direct-thread.entity.ts#L50-L62

I tried:

    const vidUp = await ig.upload.video({
      video: await fs.readFile(
        path.resolve(__dirname, "../data/SampleVideo_1280x720_1mb.mp4")
      ),
      duration: 5312,
      height: 720,
      width: 1280
    })
    console.log("vidUp", vidUp)

The video upload process returns: vidUp { xsharing_nonces: {}, status: 'ok' } (no upload_id in response body)

I based configure_video not just on similarity, but also these lines from mgp25/Instagram-API (see URL).

Not sure what video_result there stands for.

It's strange I am not getting an upload_id back despite the 'ok', it seems to be expected.

I also tried this:

    const uploadId = "1568498701788"
    const vidUp = await ig.upload.video({
      uploadId,
      video: await fs.readFile(
        path.resolve(__dirname, "../data/SampleVideo_1280x720_1mb.mp4")
      ),
      duration: 5312,
      height: 720,
      width: 1280
    })
    console.log("vidUp", vidUp)
    console.log("uploadId", uploadId)
    const res = await ig.directThread.broadcast({
      item: "configure_video",
      form: {
        upload_id: uploadId
      },
      threadIds: "340282366841710300949128112692906930936"
    })

which is probably stupid since the ID I should get back is probably different than the option ID. (I didn't check in the photo case, but the current code uses the returned one.) Anyway, this gives 403 Forbidden (probably because I am referencing someone else's or nonexistent video upload).

created time in 6 months

more