push eventqm3ster/zigbeer-rs

qm3ster

commit sha 1615e3a19be0122ffc14971185ac72d9fbfbb133

Update tokio for latest nightly

view details

qm3ster

commit sha 273a560a992d60795d9b0b09631d38875384370d

Start coordinator

view details

qm3ster

commit sha 7b74d2a4670d6fa903e88878f99290ad3b313e39

Parse zcl frame

view details

push time in 2 days

issue commenttokio-rs/tokio

Tokio-async-await fails to compile on latest nightly

@emk or for those that do want latest nightly,

[dependencies]
futures-preview = "0.3.0-alpha.14"
tokio = { version = "0.1.18", features = ["async-await-preview"] }
[patch.crates-io]
tokio = { git = "https://github.com/tokio-rs/tokio" }
tokio-async-await = { git = "https://github.com/tokio-rs/tokio" }

currently works splendidly.

tyrylu

comment created time in 2 days

issue commentFTBTeam/FTB-Presents-Stoneblock-2

Continuous crashes on Stoneblock 2 server

Do you have a weirdly shaped EnderIO capacitor bank, like donut shaped or something? It's trying to use an air (empty) block as part of the capacitor bank multiblock.

federico2407

comment created time in 4 days

push eventqm3ster/zigbeer-rs

qm3ster

commit sha a30b59f0385fbfc96b895c44f264287399771369

Start coordinator

view details

qm3ster

commit sha 77c382edc5187e58be1b5ebfb0a32ed945ac0f7b

Parse zcl frame

view details

push time in 6 days

push eventqm3ster/zigbeer-rs

qm3ster

commit sha 51fd58b7d729d8039d7a1e64ab7d7fcdcdae016b

Add AF `AF_REGISTER` command and `AF_INCOMING_MSG` event

view details

qm3ster

commit sha 69cf5e851915921bfba591632ddb8cbbcfb5e345

Move initialization out of main

view details

qm3ster

commit sha f9d90ce397945b9dcfcd3418c9cbf2d6b80a30fe

Use tokio master for latest nightly

view details

qm3ster

commit sha 8a0a3b2960021f68b2eef4cc8df944d374047775

Start coordinator

view details

push time in 6 days

push eventqm3ster/zigbeer-rs

qm3ster

commit sha 2e9ef19518a0d597c548117699805832f680c58a

Use tokio master for latest nightly

view details

push time in 7 days

push eventqm3ster/zigbeer-rs

qm3ster

commit sha 42b2198960d0aad2e9b916e934f31b276b553d4e

Use `taiki-e` fork for latest nightly

view details

push time in 8 days

pull request commenttokio-rs/tokio

async-await: update to new futures_api

Yay, it works with futures-preview = "0.3.0-alpha.14"

taiki-e

comment created time in 8 days

push eventqm3ster/zigbeer-rs

qm3ster

commit sha a24141cb9a0bc965531559d76cb192b8a3abad4a

Fix deserialization endianness

view details

qm3ster

commit sha 20af1795def5d02836b42aaa1e54c55148e4f8cd

Typo

view details

qm3ster

commit sha 170f6fae66eb812bc012b833593bb633e8c0ff5b

Add AF `AF_REGISTER` command and `AF_INCOMING_MSG` event

view details

qm3ster

commit sha 584daf0d5efc99671621b548bcbaa06b0e10f056

Move initialization out of main

view details

push time in 10 days

push eventZigBeans/zigbee2mqtt

Koen Kanters

commit sha 99a29293ddfa6f76aca366faee0bfcdf26f1be00

Mock homeassistant zigbee2mqtt version.

view details

Bruceforce

commit sha 8ffd7653ac8e2b5983bc36cbe163deab8414dc76

[devicePublish.js] Increase timeout (#974) This should avoid a non-function state of the app when too many requests arrive at a specific time frame (e. g. turning a lot of lights out in the same time). See discussion in #362

view details

Koen Kanters

commit sha 30823a5a0cedc5989bf2a689a46ff73e03512f5a

Update zigbee-shepherd.

view details

jbn

commit sha 588124b97152852aeab6fd87b14186a3c53ee681

Add announcement handler to deviceAvailability extension

view details

Koen Kanters

commit sha d5c6e39e7d5547e08d216017f57b948e330eb8ea

Refactor device reconfigure when device comes online and mark online. #966 #775

view details

Koen Kanters

commit sha dd8ee60535f35087b8e7300f89a1facd2c661853

Drop node 8 and 9 support.

view details

Koen Kanters

commit sha b8744ce890b6b80c826d6578280e3c61d672007e

Add reporting feature. #966

view details

Koen Kanters

commit sha 7d9c21ba246c9483ab9433e83a9423fe20f9666b

Fix reporting.

view details

Koen Kanters

commit sha 0d9741e5110d3ace0b4d2436bc13b1cda3eb5fe1

Update zigbee-shepherd-converters to 7.0.28.

view details

Koen Kanters

commit sha ae08deb2fd563922f5fda553b67d85bb91292c51

Refactor and remove unnecessary bind. #966

view details

Koen Kanters

commit sha 89c66094c65373ce6030d3192398f01943cff6a3

Setup reporting for X/Y color. #966

view details

Koen Kanters

commit sha 4558bffd413f6cadbd93c1443b5bcf7794d7c0e7

Don’t setup reporting for binding, use report functionallity. #782

view details

Koen Kanters

commit sha 720addd906cae53d2505d5097f12394392a0f4dd

Update zigbee-shepherd-converters to 7.0.30.

view details

Koen Kanters

commit sha 3963a8d26f8e79011629a34aac3549e26766bd52

Refactor ping queue to zigbee.js.

view details

Koen Kanters

commit sha fd4a88acd06ae02e7444a5201d3160d1633bf6b7

Refactor zigbee publish queue to zigbee.js

view details

Koen Kanters

commit sha 4405e716106bf533e40d315254d715a05ee8d4d1

Retrieve device state after device offline -> online. #775

view details

Koen Kanters

commit sha 0b3c8df81097f397c271bd7e6c33a3cddfa47bb9

Fix linting.

view details

Koen Kanters

commit sha dc70840c8a29024888eedc4ba96cd019a624ae8b

Use defaultCfg.

view details

Koen Kanters

commit sha 189c0f360e4d6c72406418154774367d888eea79

Guard callbacks.

view details

Koen Kanters

commit sha 054892641bca7b596817d33f72ae159694856290

Check availability for new devices. #775

view details

push time in 11 days

push eventZigBeans/zigbee2mqtt

Koen Kanters

commit sha ac28ca28416c0e550b06dae13e07bf5097b42ce2

Update to zigbee-shepherd-converters 8.0.0

view details

Koen Kanters

commit sha a65fbd6e2c19de86c1032437d3e3fe09560c8121

Update zigbee-shepherd-converters to 8.0.1.

view details

Koen Kanters

commit sha 03ca8ec24de421af834a0fb12c7f122a7be2b341

Update zigbee-shepherd-converters to 8.0.2.

view details

Koen Kanters

commit sha f54f3bd40f4f4a49da4eefbadbda607cca1bcde2

Add coordinator to zigbee2mqtt/bridge/config/devices. #1236

view details

Koen Kanters

commit sha d4d85633d2f770a6e00ecb2acad730928f52d88d

Log groupID. #1238

view details

Koen Kanters

commit sha 969585c84e7f4789bd5eec2f7cf0dc909bedb905

Allow to bind specific endpoint. #176

view details

Koen Kanters

commit sha f37d52b870084cb0e7d2119cd64d0de73a9b5798

Discover click sensor for QBKG03LM, QBKG04LM, QBKG11LM and QBKG12LM. https://github.com/Koenkk/zigbee2mqtt/issues/723

view details

Koen Kanters

commit sha f2cdbeab3823e5458e8942daf1500d48a3384159

Update zigbee-shepherd-converters to 8.0.3.

view details

Koen Kanters

commit sha b39e195763322ea532f39df9cf13223b9b6db0c8

Update zigbee-shepherd.

view details

Koen Kanters

commit sha fdcf2e8c3d57889652724ab6316af51a09fe0e84

Option to set Home Assistant discovery topic. #1019

view details

Koen Kanters

commit sha 8b4b9bea190b9240bc3d8820a4a76c25f6d16585

Refactor property cache responsibility to state.

view details

Koen Kanters

commit sha 7461fec28bbc0aa3b6c2cab4df1c47a8174e0d1a

Update zigbee-shepherd-converters to 8.0.4.

view details

Koen Kanters

commit sha 661f79ce936512b8bbbdca44e5a38563d285952e

Whoops! Fix tests

view details

Koen Kanters

commit sha 3a96473e2b21e8716c43c5b4e47400b6b7c1533e

Improve device bind robustness. https://github.com/Koenkk/zigbee2mqtt/issues/176

view details

Koen Kanters

commit sha ad835e090bea53b246b3a84f265ffa7c8a8bae9c

Add Discord channel. https://github.com/Koenkk/zigbee2mqtt.io/issues/31

view details

Koen Kanters

commit sha a8cf925fcb7cc40f549c95f82899855641f2aaef

Update zigbee-shepherd, zigbee-shepherd-converters and zcl-id.

view details

Koen Kanters

commit sha e6044da6045cfeeec47e31d3aa2f9301527e3cc1

Implemented device debounce option. #1264

view details

Koen Kanters

commit sha 1043053812fb3294a4af22bc8f174ad9e4b2d1f3

Update zigbee-shehperd.

view details

Oli

commit sha a2a90bcdbd963cd5deae7a4b0c2a1a374a905cc1

Log zigbee2mqtt version information to bridge/config (#1267) * add coordinator_firmware to bridge/config * Add zigbee2mqtt version and commit * Whoops

view details

Koenkk

commit sha 36bba0154dff9a5ddf4e1ffbb0e5d93190dbb3c2

Fix groupid logging.

view details

push time in 11 days

push eventqm3ster/zigbeer-rs

qm3ster

commit sha 116b63849038b6b7ccf9ec431dbe8451a3d0443a

Improve SRSP callback handling

view details

qm3ster

commit sha 275cf32838313182643d919b22208acb9d4367a7

Return Sender struct and incoming Stream Returning a struct instead of a Sink allows holding the device struct for arbitrary amounts of time, for example to block sending during reset

view details

push time in 11 days

push eventqm3ster/zigbeer-rs

qm3ster

commit sha 275cf32838313182643d919b22208acb9d4367a7

Return Sender struct and incoming Stream Returning a struct instead of a Sink allows holding the device struct for arbitrary amounts of time, for example to block sending during reset

view details

push time in 11 days

delete branch qm3ster/html2pug-website

delete branch : update2017

delete time in 11 days

push eventqm3ster/zigbeer-rs

qm3ster

commit sha 5587ccf3176df8ce58ebd3090393b732895ff3ff

Add AREQ Also added SYS_RESET_REQ Also began adding timeout

view details

push time in 14 days

create barnchqm3ster/zigbeer-rs

branch : areq

created branch time in 14 days

push eventqm3ster/html2pug-website

snyk-bot

commit sha a88db9d60f422089abdbbaefaa16bed78a6118c3

fix: package.json to reduce vulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-JSYAML-174129

view details

push time in 16 days

create barnchqm3ster/html2pug-website

branch : snyk-fix-26ks68

created branch time in 16 days

issue commenttokio-rs/tokio

Timeout consumes inner even it hadn't used

I actually found this out about Sink, but guessed the same is true for Stream, and it is :smile: ended up changing

    async fn sreq(&mut self, req: ZnpReq) -> ParsingResult<ZnpRes> {
        let mut tx_lock = await!(self.tx.lock());
        let send = tx_lock.take().unwrap().send(req);
        let tx = await!(send).unwrap();
        *tx_lock = Some(tx);
    }

to just

    async fn sreq(&mut self, req: ZnpReq) -> ParsingResult<ZnpRes> {
        let mut tx_lock = await!(self.tx.lock());
        let send = Stream::send(&mut *tx_lock, req);
        await!(send).unwrap();
    }
DenisKolodin

comment created time in 17 days

issue commentAPIDevTools/json-schema-ref-parser

How to see current path inside resolver?

This is where the file object is created - https://github.com/APIDevTools/json-schema-ref-parser/blob/master/lib/parse.js#L29

qm3ster

comment created time in 17 days

issue commentAPIDevTools/json-schema-ref-parser

How to see current path inside resolver?

@ziadsawalha no, sorry. I started, but I don't think I have that branch any more.

qm3ster

comment created time in 17 days

Pull request review commentneon-bindings/examples

Remove promisify from event-emitter

 class MyEventEmitter extends EventEmitter {       // until either the next event is sent on the channel or a receive       // timeout has occurred.       if (this.isShutdown) {-        return channel.shutdown();+        channel.shutdown();+        return;       }        // Poll for data-      return (-        poll()-          .then(e => {-            // Timeout on poll, no data to emit-            if (!e) {-              return undefined;-            }--            const { event, ...data } = e;--            // Emit the event-            this.emit(event, data);--            return undefined;-          })--          // Emit errors-          .catch(err => this.emit('error', err))--          // Schedule the next iteration of the loop. This is performed with-          // a `setImmediate` to extending the promise chain indefinitely-          // and causing a memory leak.-          .then(() => setImmediate(loop))-      );+      channel.poll((err, e) => {+        if (err) this.emit('error', err);+        else if (e) {+          const { event, ...data } = e;++          // Emit the event+          this.emit(event, data);+        }+        // Otherwise, timeout on poll, no data to emit++        // Schedule the next iteration of the loop. This is performed with+        // a `setImmediate` to yield to the event loop, to let JS code run+        // and avoid a stack overflow.+        setImmediate(loop);+      });     }; -    // Start the polling loop-    loop();+    // Start the polling loop on next iteration of the JS event loop to prevent zalgo.

Agreed + I think this change actually isn't necessary the way the example is currently written.

qm3ster

comment created time in 17 days

issue commenttokio-rs/tokio

Timeout consumes inner even it hadn't used

@DenisKolodin Great new development you'll be happy to hear about: impl<'a, S: Stream + ?Sized> Stream for &'a mut S Which means you don't have to give your Stream away!

let (tx, mut rx) = mpsc::channel(10);

let with_timeout = (&mut rx).into_future().timeout(Duration::from_millis(1));

match with_timeout.wait() {
    Ok((item, _)) => { }
    Err(err) => { /* Not sure what to do here, I use async/await, which simplifies lifetimes */ }
}
DenisKolodin

comment created time in 17 days

push eventqm3ster/zigbeer-rs

qm3ster

commit sha fe0af3bca0ab175575f4d419687f6d0dc5d0de2e

typo: Rename ZpiCmd to ZnpCmd

view details

qm3ster

commit sha 1d9a031aa21f5b392c822b450671b1addd7b1073

Add AREQ Also added SYS_RESET_REQ Also began adding timeout

view details

push time in 18 days

push eventqm3ster/zigbeer-rs

qm3ster

commit sha 4b7f681e79aea6d174ccef27062d0c3a44aaaf30

Add more ZDO AREQs

view details

qm3ster

commit sha 658e094b1c438fd6b214ef36e5d65c546193fe1d

Extract blinking

view details

qm3ster

commit sha 10e68faf1ba44d31c39ec9b1df3499568e7a8c40

Add ConfigIDs enum

view details

qm3ster

commit sha 702454e2d6f2678777c20a23767f6a7c14d213c2

Add SYS_RESET_IND

view details

push time in 20 days

push eventqm3ster/zigbeer-rs

qm3ster

commit sha 5a27396aa6dc687149c7b1ac2009d7a717bf1182

Improve AREQ printing

view details

push time in 20 days

push eventqm3ster/zigbeer-rs

qm3ster

commit sha 9a84fd561ea5a7b63d15104516844e6e6de5beeb

Add ZDO_STARTUP_FROM_APP, ZDO_STATE_CHANGE_IND

view details

push time in 21 days

push eventqm3ster/zigbeer-rs

qm3ster

commit sha 17ba39fee23bc92bf2fa0207d1431420d6be102b

Add SYS_OSAL_NV_READ

view details

qm3ster

commit sha 14a6cc1b8b3dcea1cf091fc2ef1b0966faf03d72

Add ZB_READ_CONFIGURATION

view details

push time in 21 days

push eventqm3ster/zigbeer-rs

qm3ster

commit sha 0f0458b5bd6850abc2b47891d0c2dc27ae6c856e

Use u8 as seq len in serse_znp::de

view details

qm3ster

commit sha 3d582f76b528574b8755b21573e0cb3e08ab1029

Add SYS_OSAL_NV_READ

view details

push time in 21 days

push eventqm3ster/zigbeer-rs

qm3ster

commit sha db02d7d812a9fe770cc6cba808e1b73406e03faf

Use u8 as seq len in serse_znp::de

view details

qm3ster

commit sha cde2d602bf5820a77ed9cd71eac22ecca17f0152

Add SYS_OSAL_NV_READ

view details

push time in 21 days

push eventqm3ster/zigbeer-rs

qm3ster

commit sha a18c79d00a31b98852e04b8f6debe12f7625dcbf

Propagate errors

view details

push time in 21 days

push eventqm3ster/zigbeer-rs

qm3ster

commit sha a40cfe2b4f3a22e153b34defc3e55e1564a9c4fe

Add incoming AREQ parsing

view details

push time in 21 days

push eventqm3ster/zigbeer-rs

qm3ster

commit sha 9d8a515b692bdf1ccf8760e06a69d80ca818d6b9

Fix endianness

view details

qm3ster

commit sha 773126d0c9b52e51b26be90b3cbdfb24541650b2

Start implementing incoming AREQ

view details

qm3ster

commit sha 9c6f2b4c35114f418c509ddec0170e38720512f3

Add SREQ SYS_OSAL_START_TIMER

view details

qm3ster

commit sha 7e535c44417202f2daa218c4447d9967f5f914b0

Move Sreq::frame into trait

view details

push time in 21 days

push eventqm3ster/zigbeer-rs

qm3ster

commit sha c41fa85c59d73cc63e576a8d273742136c1b8d22

Fix endianness

view details

qm3ster

commit sha f1b364d15330f5696dc9743c502373b20fe97262

Start implementing incoming AREQ

view details

qm3ster

commit sha 1559b2842f18d8b65a08e6660086f565b707bf49

Add SREQ SYS_OSAL_START_TIMER

view details

push time in 22 days

pull request commentserde-rs/example-format

Minimal update to 2018 edition

Alright, I know that one. :+1:

qm3ster

comment created time in 22 days

create barnchqm3ster/zigbeer-rs

branch : master

created branch time in 22 days

created repositoryqm3ster/zigbeer-rs

Everything will be okay, don't worry.

created time in 22 days

pull request commentserde-rs/bench

Convert to 2018 edition

Noted. I used rustfmt to get rid of try! macro, but I could split those changes.

qm3ster

comment created time in 22 days

pull request commentserde-rs/example-format

Minimal update to 2018 edition

@dtolnay noted. I do not yet know what idiomatic 2018 looks like, feel free to close.

qm3ster

comment created time in 22 days

pull request commentneon-bindings/examples

Replace lerna with pnpm

@theJian It does not. The users can, just as before, cd to a specific example's package directory and yarn or npm i it alone.

qm3ster

comment created time in 24 days

push eventqm3ster/html2pug-website

snyk-bot

commit sha fe9f7be7fe785236e12d2c36905278433c79095f

fix: package.json to reduce vulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-JSYAML-173999

view details

push time in 25 days

create barnchqm3ster/html2pug-website

branch : snyk-fix-ffkoit

created branch time in 25 days

pull request commentserde-rs/bench

Convert to 2018 edition

That's Rust: 1.15.0 failing, unsurprisingly.

qm3ster

comment created time in 25 days

PR opened serde-rs/bench

Convert to 2018 edition
+232 -171

0 comment

7 changed files

pr created time in a month

create barnchqm3ster/bench

branch : 2018

created branch time in a month

fork qm3ster/bench

Minimal serialization format for benchmarking Serde

fork in a month

startedrust-embedded/cross

started time in a month

PR opened serde-rs/example-format

Minimal update to 2018 edition

Fixed paths to compile. Also silenced stable clippy warning and applied stable rustfmt.

+5 -6

0 comment

3 changed files

pr created time in a month

create barnchqm3ster/example-format

branch : 2018

created branch time in a month

fork qm3ster/example-format

An example Serializer and Deserializer data format for Serde

fork in a month

CommitCommentEvent

issue commentnuxt/nuxt.js

Will you consider separating server-side code from client-side code in the future?

lmao

<!--cmty_prevent_hook-->

651778286

comment created time in a month

push eventzigbeer/zigbeer

qm3ster

commit sha b5513adc8a41017575d5a95d3205b434f37fa01d

fix(zigbee-shepherd): Take cc-znp default import

view details

push time in a month

push eventzigbeer/zigbeer

qm3ster

commit sha 4f0adbe958a4e9b6ae90e9a989c5e75ba146e258

refactor(cc-znp): use buffster, not dissolve Also created missing parsers and serializers BREAKING CHANGES: - attributes with counts now just return arrays - attributes with address type now return `{type: number, addr: Buffer|number}`

view details

qm3ster

commit sha cb609e2379cc2f8c10583d3d6e481c5f774827f6

feat(buffster): Add uint32be

view details

qm3ster

commit sha 9bacd8bcafbdf2f2e2c75ad775c9557b1b37d107

refactor(cc-znp): Make use of uint32be

view details

qm3ster

commit sha 9e666637c15e7479c0b13d626f1ebc309ee28d71

fix(zigbee-shehperd): Take cc-znp default import

view details

push time in a month

push eventzigbeer/zigbeer

qm3ster

commit sha 26f69434dc9cbbef4059da66041dce3f2979baf6

fix(zigbee-shehperd): Take cc-znp default import

view details

push time in a month

push eventzigbeer/zigbeer

qm3ster

commit sha e8eec866e222ecdb1747a56cf3d3c908e58b09e6

fix(zigbee-shehperd): Take cc-znp default import

view details

push time in a month

push eventzigbeer/zigbeer

qm3ster

commit sha 3ab5f2d435f659f5e92d1f644ae6875542a16ba0

refactor(cc-znp): Make use of uint32be

view details

push time in a month

push eventzigbeer/zigbeer

qm3ster

commit sha 5b677ead8e0ce48eb1f63ef1245b5ee867b82d91

feat(buffster): Add uint32be

view details

push time in a month

PR opened zigbeer/zigbeer

Switch cc-znp to buffster
+6555 -6830

0 comment

23 changed files

pr created time in a month

create barnchzigbeer/zigbeer

branch : cc-znp-buffster

created branch time in a month

pull request commentneon-bindings/examples

Replace lerna with pnpm

Well for me, pnpm is its own reward, because of its speed and "strictness" (no transient dependencies). And since this repo isn't a set of packages that are meant for release, the things missing from pure pnpm (bumping versions, publishing) don't matter here. For repos that do need releasing, I have recently deployed @microsoft/rush, and I am very pleased with it. The default there is also pnpm, but they do support npm and yarn as well.

qm3ster

comment created time in a month

PR opened neon-bindings/examples

Replace lerna with pnpm

This allows for much faster CI and local builds

Also added jest to travis

Tests are currently failing, but fixed in PR #31

Also fixed eslint config not to have implicit dependencies and irrelevant plugins, eg: browser compatibility and flowtype

+5266 -12407

0 comment

25 changed files

pr created time in a month

push eventqm3ster/examples

qm3ster

commit sha 42dc67dc977a934ee94808f0d9b619cc4af72be4

Replace lerna with pnpm Also added `jest` to travis Tests are currently failing, but fixed in PR #31 Also fixed eslint config not to have implicit dependencies and irrelevant plugins, eg: browser compatibility and flowtype

view details

push time in a month

push eventqm3ster/examples

qm3ster

commit sha b00f5e4dea147da619f8e209d01238fb8d474f41

Replace lerna with pnpm Also added `jest` to travis Tests are currently failing, but fixed in PR #31 Also fixed eslint config not to have implicit dependencies and irrelevant plugins, eg: browser compatability and flowtype

view details

push time in a month

create barnchqm3ster/examples

branch : goodbye-lerna

created branch time in a month

fork qm3ster/eslint-config-bliss

An opinionated ESLint config general node development 🎉

fork in a month

pull request commentneon-bindings/examples

Remove promisify from event-emitter

@kjvalencik I'm glad this will be fixed in core, this is an important usecase for me. But I think we should provide the best possible solution in the meantime.

Do you think it would be harmful if I added the synchronous fetching of multiple events when available, as I described in the Slack reply thread?

qm3ster

comment created time in a month

pull request commentMicrosoft/TypeScript

Const contexts for literal expressions

@maartenth I was thinking

import as const * as data from 'data.json'
//or
import data from 'data.json' as const //my preference, and generally the position in which I would like to cast imports, if that feature ever becomes available.
ahejlsberg

comment created time in a month

push eventqm3ster/examples

qm3ster

commit sha 4c2ea2bad2b678e2ff93346b29cc974f774e36ff

Fix event-emitter test Has been broken since previous refactor

view details

push time in a month

PR opened neon-bindings/examples

Remove promisify from event-emitter

Simplifies the example

Transferred the promisify usage to async example instead

Also removed unused dependencies from package.json

+34 -37

0 comment

3 changed files

pr created time in a month

push eventqm3ster/examples

qm3ster

commit sha 16212b480a8b48160e83d5d85cab0b8c5839460d

Remove promisify from event-emitter Simplifies the example Transferred the promisify usage to `async` example instead Also removed unused dependencies from previous refactor

view details

push time in a month

push eventqm3ster/examples

qm3ster

commit sha 7e8e24908599dc8817ba7f707bda5e65e6ca4b20

Remove promisify from event-emitter Simplifies the example Transferred the promisify usage to `async` example instead. Also removed unused dependencies

view details

push time in a month

create barnchqm3ster/examples

branch : event-emitter-no-promisify

created branch time in a month

fork qm3ster/examples

A collection of examples of Neon

fork in a month

pull request commentneon-bindings/neon

Allow mutable borrow of self for Tasks.

Totally. I can see ergonomic value for people coming from JS of having complete return a value.

abrodersen

comment created time in a month

pull request commentneon-bindings/neon

Allow mutable borrow of self for Tasks.

@kjvalencik, I just thought of another killer use for passing the handle to the callback into complete. If this is done, the Task can now reschedule itself or a different Task on this callback, in addition to calling it! This would significantly improve the (event-emitter)[https://github.com/neon-bindings/examples/tree/master/event-emitter] usecase, removing the setImmediate polling trickery. It will look like a real subscription on the JS side.

abrodersen

comment created time in a month

issue commentMicrosoft/TypeScript

In the typescript-3.3.3333 npm package, two dotfiles accidentally? included

  1. I highly recommend the package.json "files" key, for specifying a whitelist instead of a blacklist. Totally allowed me to leave .npmignore nightmares in the past, regardless of complicated builds.
  2. Not relevant to the thing that happened this time, but I also suggest looking at package-preview to make sure that you include enough into the tarball.
metanest

comment created time in a month

pull request commentneon-bindings/neon

Allow mutable borrow of self for Tasks.

Additionally, it would probably be more flexible to just pass the handle to the callback into complete. The current way makes it clearer what to do with errors, but it would be more flexible to be able to conditionally call the JsFunction 0, 1, or more times. :+1: for the separate extra data struct to be available in the complete, especially if it can have references to values from the Js world by not being sent.

abrodersen

comment created time in a month

pull request commentneon-bindings/neon

Allow mutable borrow of self for Tasks.

Oh :O I didn't know there's such a thing. Can I come in?

abrodersen

comment created time in a month

pull request commentneon-bindings/neon

Allow mutable borrow of self for Tasks.

@kjvalencik Was this comment to any extent motivated by our discussion in the Slack? :stuck_out_tongue: Also, I have since learned that calling them "static method"s is bad manners. In Rust, they are "associated functions" :stuck_out_tongue:

abrodersen

comment created time in a month

pull request commentneon-bindings/neon

Add ThreadSafeCallback helper to schedule callbacks on the main thread

Oh wow, this is exactly what I need. I've been trying to get "emitting" to work, even with help on the JS side, but I can neither call a callback asynchronously without terminating a Task, nor pass a tokio::sync::mpsc::Receiver on the "class" struct into a new Task because of lifetimes.

geovie

comment created time in a month

push eventqm3ster/rust-prebuild-test

qm3ster

commit sha 277fbe04fb2fcdc9daad7f8fd34111c66a214d8e

Add `poll_read`

view details

push time in a month

push eventqm3ster/rust-prebuild-test

qm3ster

commit sha e7e9736f43d2c37e52b19fda1b44e9caa45ee7c5

Use idiomatic constructor

view details

push time in a month

startedlupyuen/rustl8710

started time in a month

startedkappaio-gateway/kappaio

started time in a month

issue commentneon-bindings/neon

error: Neon only builds with --release. For tests, try `cargo test --release`.

Having same issue, only on Windows. Repro: https://github.com/qm3ster/rust-prebuild-test On Ubuntu 18.20, pnpm i compiles correctly. On Windows, pnpm i fails with this error, requiring pnpm run install -- --release.

mlengse

comment created time in a month

create barnchqm3ster/rust-prebuild-test

branch : master

created branch time in a month

created repositoryqm3ster/rust-prebuild-test

created time in a month

pull request commentrust-lang/rls-vscode

Allow to not look for config in outermost nested folder.

@ppiet can you reopen this? It doesn't look like it went stale, and I would like this feature.

ppiet

comment created time in a month

issue commentrust-lang/rls-vscode

Multi-root workspaces: handling of nested roots (getOuterMostWorkspaceFolder)

This issue also takes place when working with Neon projects (native nodejs modules written in Rust). The only way to make it work correctly is opening the inner folder as a separate workspace:

{
	"folders": [
		{
			"name": "Rust",
			"path": "native"
		},
		{
			"path": "."
		}
	],
	"settings": {}
}
ppiet

comment created time in a month

startedrust-console/gba-proc-macro

started time in a month

startedzkochan/package-preview

started time in a month

issue commentMicrosoft/web-build-tools

[rush] publishing prereleases breaks inter-repo dependencies

Great to know that this project is heading towards the latter design. It makes perfect sense, and is similar to what people do semi-manually with semantic release and such. I ended up setting up the current publishing, but it was rather frustrating since either half could fail. Another advantage of the split approach is that now only the bumping stage needs push access to the code, and only the publish stage needs npm token.

raygesualdo

comment created time in a month

issue commentMicrosoft/web-build-tools

[rush] Intent to collaborate for virtualized dependency management

Of note may be that pnpm switched from separate shrinkwrap to a unified shrinkwrap as the default with the 3.0 release.

KevinGrandon

comment created time in a month

issue commentMicrosoft/web-build-tools

[rush] rush add npm tags

Perhaps anything that fails semver parsing should just go in the next ("latest") branch? (With "latest" literal generalized to initialSpec)

qm3ster

comment created time in a month

startedbenbalter/change_agent

started time in a month

issue openedMicrosoft/web-build-tools

[rush] rush add multiple packages

Not sure why rush add takes packages through the -p flag and not just naked parameters like all the package managers do, but it should still be able to install/update version of multiple package identifiers at once, for example with multiple flags: -p PACKAGE -p PACKAGE@VERSION.

The current behavior when you supply rush add -p foo -p bar is particularly surprising - instead of erroring out since this isn't supported, it just ignores the package names before the last one supplied. (You end up only adding bar). That's probably a Bad Thing™

created time in a month

issue openedMicrosoft/web-build-tools

[rush] rush add npm tags

Currently, running rush add with a tag specifier as the version doesn't work, unlike in the package managers. Example:

rush add -m -p typescript@next

This fails with ERROR: The SemVer specifier "next" is not valid.

Suggested behavior:

This should resolve to the latest version with the tag, then save it in accordance with --caret|--exact flags.

created time in a month

push eventzigbeer/zigbeer

qm3ster

commit sha 764d15cfd62758a3c9766c1ad8baa6ec6d4a31de

chore(ci): hide npm token from logs

view details

push time in a month

more