1
0
mirror of https://github.com/node-red/node-red-nodes.git synced 2023-10-10 13:36:58 +02:00
Commit Graph

349 Commits

Author SHA1 Message Date
Dave Conway-Jones
ed45d5622b
bump email package for de translations 2021-03-25 09:48:03 +00:00
heikokue
14b1e3aefb
email node: improved EN help and added DE help (#781) 2021-03-25 09:45:45 +00:00
JsBergbau
e05a3f3d4d
Added retry and expire setting for Prio 2 messages (#780) 2021-03-25 09:42:50 +00:00
JsBergbau
ef5b577f7f
Updated documentation for msg.html (#774) 2021-03-18 08:47:36 +00:00
Dave Conway-Jones
61025cc962
bump pushover for PR 2021-03-17 21:08:37 +00:00
JsBergbau
b87488df6d
Added support for msg.html (#773) 2021-03-17 21:07:35 +00:00
Dave Conway-Jones
3330053a1c
bump sensehat , irc, and twitter nodes for German translation 2021-03-14 14:10:26 +00:00
Dave Conway-Jones
e674f9ad97
cleanup some old x-red label - no new node versions 2021-03-13 14:25:45 +00:00
Dave Conway-Jones
169be33591
bump tail, sqlite, email, feedparser, pigpiod for German translations 2021-03-13 14:15:58 +00:00
heikokue
80b9316d92
added/improved DE translation of forms (#765) 2021-03-12 13:23:26 +00:00
heikokue
0772b545ea
added i18n help files (#766) 2021-03-12 13:17:23 +00:00
Dave Conway-Jones
f7be874e2c
fix linting for grunt 2021-03-12 09:36:20 +00:00
Dave Conway-Jones
4d7ba48797
Add room password, better error / status reporting 2021-03-01 13:40:14 +00:00
Dave Conway-Jones
59361625cc
Add subject to chat if known 2021-02-28 17:32:49 +00:00
Dave Conway-Jones
a9d1ca0491
xmpp disconnect more cleanly/correctly 2021-02-26 16:05:03 +00:00
Dave Conway-Jones
9db89f3ea1
RBE node - let topic handling be optional (#751)
* let rbe handle topics optional

and add tests

* fix text formatting

* Update package.json
2021-02-26 14:51:55 +00:00
Dave Conway-Jones
c368e3bcd4
xmpp auto create rooms correctly and auto join every 60 secs if required 2021-02-25 09:05:11 +00:00
Dave Conway-Jones
cafdb26832
add info command to xmpp nodes 2021-02-23 22:15:57 +00:00
Dave Conway-Jones
40362ee985
Let xmpp in handle a list of rooms 2021-02-23 12:45:55 +00:00
Dave Conway-Jones
7485760db9
xmpp node - use empty field to signify all rooms 2021-02-23 11:37:53 +00:00
Dave Conway-Jones
3ad829d75a
Let xmpp input node join "ALL_ROOMS" automatically (if asked) 2021-02-23 09:04:12 +00:00
Dave Conway-Jones
b1a2741fa0
fix pushover to handle false msg.payload
to close #756
2021-02-11 21:17:59 +00:00
Dave Conway-Jones
bbf9a3b7e4
bump xmpp package 2021-02-02 19:21:28 +00:00
Andreas Martens
1c34e39d8a
XMPP: improve debugging and error handling (#753) 2021-02-02 16:55:55 +00:00
Dave Conway-Jones
f99e52d1fa
Merge branch 'master' of https://github.com/node-red/node-red-nodes
merge upstream
2021-02-02 10:12:32 +00:00
Dave Conway-Jones
778fd68354
add contributor 2021-01-29 16:53:50 +00:00
Dave Conway-Jones
77fac03319
bump xmpp 2021-01-29 16:48:54 +00:00
Andreas Martens
fc2f6ed3c7
join a MUC if we're already connected to server and refactor error handling (#749) 2021-01-29 16:46:15 +00:00
Dave Conway-Jones
14983c9722
mail - check attachment valid contents if possible
to close #728
2021-01-12 12:41:41 +00:00
Dave Conway-Jones
4884550215
Tidy up pushbullet (no fixes)
remove old migration code)
2020-11-16 21:26:32 +00:00
Dave Conway-Jones
9e7a8d5764
bummp twitter and pi-gpio packages for recent PRs 2020-11-16 14:58:54 +00:00
Matt Borja
640a6d0cb2
Improve error handling for read-only applications (#709)
Applications pending approval will return a different response body than what is presently supported.

Below is a copy of the actual response that comes back in this scenario:
```
{"status":401,"rateLimitTimeout":null,"body":{"request":"/1.1/statuses/update.json","error":"Read-only application cannot POST."}}
```

Whereas the current implementation assumes the presence of an `errors` array, reading off the first element (i.e. `result.body.errors[0]`), the above scenario throws an exception as `result.body.errors` is now `undefined` and cannot be indexed).

The proposed update seeks to account for this while retaining existing functionality and has been tested (error message in debug now properly says "Read-only application cannot POST."
2020-11-11 11:26:56 +00:00
Dave Conway-Jones
07e5d9fd65
email node - add msg.priority and msg.headers options 2020-10-26 09:08:10 +00:00
Dave Conway-Jones
3b7fb0aa95
tidy up xmpp node 2020-10-24 15:02:45 +01:00
Dave Conway-Jones
6f351943cb
email node - remove promises for node8
and fixup tests
2020-10-19 21:33:32 +01:00
Dave Conway-Jones
ef1ebe7b44
Fix email tests and add one for MTA node 2020-10-19 14:32:09 +01:00
Dave Conway-Jones
14087a9f77
Add MTA node to email 2020-10-19 12:24:18 +01:00
Nick O'Leary
8f2c631410
Bump pushbullet node version 2020-10-13 22:38:18 +01:00
guzba
ff9d21827d
Attempt to mitigate stream server connect feedback loop
Pushbullet dev here. Around 36 hours ago we started receiving around 750 additional requests per second to connect to our stream server. I blocked around 50 - 100 IP addresses to mitigate the spam. This spam traffic has continued unchanged since then.

I don't know for sure what caused this, but one user came forward reporting issues with their Node-Red setup after I banned the IPs (status code is my banned IP status code which is pretty compelling evidence). I can't be sure what is causing the issue since no User-Agent is included in the requests, but it for sure is at least partly Node-Red API users. I'd like to work on mitigating this since mitigating the spam traffic costs money.

My first theory here is in this PR. I am not aware of any guarantees that you'll never get multiple 'error' events, so it makes sense to clear the timeout before setting a new one to reconnect. Even if it is just defensive, it may not have much cost? If you do get multiple error events without this change, it is possible to trigger many connect() requests which can error out and then trigger many more connect() requests with lots of timeouts, which is not good.

Another thing to consider is that this library's dependency for PB (https://github.com/alexwhitman/node-pushbullet-api) already has code to reconnect if a websocket connection is lost without having been properly closed. I think an even better solution is verifying this works and then deleting the reconnect logic from here.

I'm not an expert on Node-Red though so I am only trying to offer suggestions to ensure everyone is a good citizen when using our API :) Thanks!
2020-10-13 16:27:30 -05:00
Dave Conway-Jones
aa45796a98
bump pushbullet package for PR 2020-09-27 12:59:02 +01:00
Frakke0
e980c8c04d
Fix not shown error (#692)
Fixed response to shown as string and not object
2020-09-27 12:57:09 +01:00
Dave Conway-Jones
d3a3bc158c
email - show valid folders in error if fetch fails 2020-09-23 23:54:09 +01:00
Dave Conway-Jones
973fd8c6ec
bump email package version 2020-09-23 10:20:58 +01:00
Vincent Hou
606f9c71e7
Update 61-email.js (#689)
Fixed disposition issue caused by `this`.
2020-09-23 08:35:08 +01:00
Dave Conway-Jones
46f3dfc382
email don't retry connection while still busy. 2020-08-28 09:36:06 +01:00
Dave Conway-Jones
ea729546d4
add sms_changed to pushbullet handler 2020-08-24 12:12:32 +01:00
Dave Conway-Jones
4cabe5ea30
bump xmpp node package version 2020-07-16 10:15:49 +01:00
Andreas Martens
e334040dd7
replace xmpp-simple with @xmpp/client (#664)
* replace xmpp-simple with @xmpp/client

* indent at 4

* remove trailing commas
2020-07-16 10:00:27 +01:00
Andreas Martens
bf94d320a9
correctly join a chat room (#663) 2020-07-10 12:30:44 +01:00
Dave Conway-Jones
01d675b372
Merge branch 'master' of https://github.com/node-red/node-red-nodes 2020-05-24 16:42:42 +01:00