Continuous transform can't  used pg_notify.

version: pipelineDB-0.9.5
I  have question.
why this function pg_notify is not seed msg?
postgres=# insert into str1(x) select 12; INSERT 0 1
I can't find any notify msg.but I executor
`
postgres=# select pg_notify('foobar','test');
pg_notify
(1 row)
`
I can find msg abcdefg and test.
abcdefg in function func_3()
about transaction?
create stream str1(x bigint);
create stream str2(x bigint y bigint);
create continuous view cv_2 as select x,y from str2;

create continuous transform trans as select
x ,func_2(x) as y from str1
THEN EXECUTE PROCEDURE pipeline_stream_insert('str2');

create or replace function func_2(x bigint)
returns bigint as $$

declare

begin

perform func_3();
return x+1;

end
$$
language plpgsql;

create or replace function func_3()
returns void as $$
declare
begin

perform pg_notify('foobar','abcdefg');

raise log '%','------------';

end
$$
language plpgsql;

@usmanm  can you give me some suggest?

I can see the log statement in the server logs:
LOG:  ------------
CONTEXT:  SQL statement "SELECT func_3()"
	PL/pgSQL function func_2(bigint) line 8 at PERFORM
STATEMENT:  trans

How are you checking pg_notify(...)?

yes,server logs is OK.
but ,pg_notify is can't run,because pg_notify  need transaction is commit.
I used
retval = select(sock + 1, &rfds, &wfds, NULL, NULL);
notify = PQnotifies(conn)
checking pg_notify.
if i executor select pg_notify('footer','abde');
select is OK
but,transform executor pg_notify,I can't  get any msg.

If you can read source ,I can seed to you mail.

So pg_notify() won't work with continuous transforms. It must be called from the process forked for the client connection, but in the case of continuous transforms its called from a worker process. #1582 this could be used as an alternative to get notified when a transform outputs something. It'll be implemented in the next few days.

OK Thanks @usmanm


Support for getClass and getClassHashAt

Hello, currently Starknetjs only supports getClassAt, would be great to also have getClass and getClassHashAt. I can submit a PR to add these. Thanks

Hello, which starknet.js version are you using?
We support all the methods you mentioned in the RPC provider

Try to use starknet@next or 4.7.0.
You could create PR updating project documentation.
Thanks for feedback.

Ahh got it, completely missed that. Thanks! Happy to update the doc


Feature: use transfer name as AIP name

Is your feature request related to a problem? Please describe.
All the AIPs created by enduro have the name "enduro-<UUID>.zip", and when uncompressed, they have a folder named enduro-<UUID>
Describe the solution you'd like
Add a configuration setting that allows for AIPs  to be created using the transfer name, without the ".zip" suffix, so the folder is named <transfer_name>-UUID, and the AIP <transfer_name>-UUID.zip
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Related: https://github.com/artefactual-labs/a3m/issues/352


Sergen : syntax erros despite rebuilt

For one of my internship mission, I need to use a C# app-builder, serenity.is with Visual Studio 2015. I'm following this official tutorial. More precisely, i followed the begin of the tutoriel p 43. (I'm just adapting it to what I do, I join the code at the end of the post). Nothing is going wrong till p 49. The code generator of the app-builder, sergen.exe, is creating some code (I don't have the detail of what he creates but it doesn't seems to be important).
They ask me to "rebuild all", what I did, and everything should work smoothly.
Nevertheless, when i compile and execute my code, I've got a bunch of syntax error which shouldn't happen.
Please find code and screen capture here
Is there any Serenity user which could help ?
Feel free to ask any other details

for straters. You did a big mistake with the naming of the columns.

Could you provide more details please x) ?

Well, DB's have restrictions on the use of certain characters on the name of the columns
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/154c19c4-95ba-4b6f-b6ca-479288feabfb/characters-that-are-not-allowed-in-table-name-column-name-in-sql-server-?forum=databasedesign
If what you want is to have the field sdisplay the "<---" and "--->" on the client side, you  should just create the fields and use the DisplayName() attribute to deal lwith the display of the field name.

Ooh !! Ok ! Thank you a lot 👍 :D

have you worked much with DB's before?

Not so much.. Some SQL Request on already-created DBs but no real DB construction


Node JS <IP_ADDRESS>?

Followed the guide on the wiki:
https://github.com/nfarina/homebridge/wiki/Running-HomeBridge-on-a-Raspberry-Pi
I know it says will install NodeJS 4.0.0 and this will not work with homekit.
How can I install a version of NodeJS that will work?
Assume I can just choose a different dist from:
https://nodejs.org/dist/
Instead of:
https://nodejs.org/dist/v4.0.0/node-v4.0.0-linux-armv7l.tar.gz
However which should I choose for Raspberry Pi 2 Model B that will work?
Many Thanks,

I installed node v4.1.1 on a RPi 2, it works with homebridge and HAP-NodeJS if you remove these dependencies in package.json:
"harmonyhubjs-client": "^1.1.4",
"harmonyhubjs-discover": "git+https://github.com/swissmanu/harmonyhubjs-discover.git",

You might take a look here

@cflurin did you update gcc to 4.8 and if not, what distro are you on (the May 2015 version of Raspbian)? I'm actually struggling to get mdns to install: getting errors related to nan ...

No, I didn't update gcc, currently my RPi 2 has this version:
uname -a
pi@raspberrypi ~ $ uname -a
Linux raspberrypi 4.1.7-v7+ #815 SMP PREEMPT Thu Sep 17 18:34:33 BST 2015 armv7l GNU/Linux

What RPi Model are you using?

Thanks for the reply, followed your guide and removed those dependencies however now have this error when trying to run the server:
pi@raspberrypi ~/homebridge $ npm run start

<EMAIL_ADDRESS>start /home/pi/homebridge
DEBUG=* node app.js || true

module.js:338
throw err;
^
Error: Cannot find module 'mdns'
at Function.Module._resolveFilename (module.js:336:15)
at Function.Module._load (module.js:286:25)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at Object.
(/home/pi/homebridge/node_modules/HAP-NodeJS/lib/Advertiser.js:1:74)
at Module._compile (module.js:434:26)
at Object.Module._extensions..js (module.js:452:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Module.require (module.js:365:17)
pi@raspberrypi ~/homebridge $

@cflurin actually, a RPi2 just like you are:

pi@raspberrypi ~/homebridge $ uname -a
Linux raspberrypi 4.1.6-v7+ #810 SMP PREEMPT Tue Aug 18 15:32:12 BST 2015 armv7l GNU/Linux

gcc -v
...
gcc version 4.6.3 (Debian 4.6.3-14+rpi1)

pi@raspberrypi ~/homebridge $ node -v
v4.1.1
pi@raspberrypi ~/homebridge $ npm -v
2.14.4

I guess I do a clean install from the image again ... see what that brings me ...

@dreameruk:
did you install Avahi?

yes

@desvdp:
you could try:
sudo rpi-update

Thanks for replying @cflurin yes I did, however during install had quite a few warnings:
pi@raspberrypi ~/homebridge $ sudo npm install
npm WARN engine<EMAIL_ADDRESS>wanted: {"node":"~0.10.0"} (current:
{"node":"4.1.1","npm":"2.14.4"})
/

<EMAIL_ADDRESS>install /home/pi/homebridge/node_modules/HAP-NodeJS/node_modules/curve25519
node-gyp rebuild

gyp WARN EACCES user "root" does not have permission to access the dev
dir "/root/.node-gyp/4.1.1"
gyp WARN EACCES attempting to reinstall using temporary dev dir
"/home/pi/homebridge/node_modules/HAP-NodeJS/node_modules/curve25519/.node-gyp"
gyp WARN install got an error, rolling back install
gyp WARN install got an error, rolling back install
gyp ERR! configure error
gyp ERR! stack Error: This is most likely not a problem with node-gyp
or the package itself and
gyp ERR! stack is related to network connectivity.  System Linux 3.18.7-v7+
gyp ERR! command "/usr/local/bin/node"
"/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js"
"rebuild"
gyp ERR! cwd /home/pi/homebridge/node_modules/HAP-NodeJS/node_modules/curve25519
gyp ERR! node -v v4.1.1
gyp ERR! node-gyp -v v3.0.3
gyp ERR! not ok

<EMAIL_ADDRESS>install /home/pi/homebridge/node_modules/HAP-NodeJS/node_modules/ed25519
node-gyp rebuild

gyp WARN EACCES user "root" does not have permission to access the dev
dir "/root/.node-gyp/4.1.1"
gyp WARN EACCES attempting to reinstall using temporary dev dir
"/home/pi/homebridge/node_modules/HAP-NodeJS/node_modules/ed25519/.node-gyp"
make: Entering directory
'/home/pi/homebridge/node_modules/HAP-NodeJS/node_modules/ed25519/build'
CC(target) Release/obj.target/ed25519/src/ed25519/keypair.o
CC(target) Release/obj.target/ed25519/src/ed25519/sign.o
CC(target) Release/obj.target/ed25519/src/ed25519/open.o
CC(target) Release/obj.target/ed25519/src/ed25519/crypto_verify_32.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_double_scalarmult.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_frombytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_scalarmult_base.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_precomp_0.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p2_0.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p2_dbl.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_0.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_dbl.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_to_p2.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_to_cached.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_tobytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_madd.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_add.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_msub.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_sub.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p1p1_to_p3.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p1p1_to_p2.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_tobytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_0.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_1.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_cmov.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_copy.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_neg.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_add.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_sub.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_mul.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_sq.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_sq2.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_invert.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_tobytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_isnegative.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_isnonzero.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_frombytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_pow22523.o
CC(target) Release/obj.target/ed25519/src/ed25519/sc_reduce.o
CC(target) Release/obj.target/ed25519/src/ed25519/sc_muladd.o
CXX(target) Release/obj.target/ed25519/src/ed25519.o
SOLINK_MODULE(target) Release/obj.target/ed25519.node
COPY Release/ed25519.node
make: Leaving directory
'/home/pi/homebridge/node_modules/HAP-NodeJS/node_modules/ed25519/build'

<EMAIL_ADDRESS>install /home/pi/homebridge/node_modules/HAP-NodeJS/node_modules/srp/node_modules/bignum
node-gyp configure build

gyp WARN EACCES user "root" does not have permission to access the dev
dir "/root/.node-gyp/4.1.1"
gyp WARN EACCES attempting to reinstall using temporary dev dir
"/home/pi/homebridge/node_modules/HAP-NodeJS/node_modules/srp/node_modules/bignum/.node-gyp"
make: Entering directory
'/home/pi/homebridge/node_modules/HAP-NodeJS/node_modules/srp/node_modules/bignum/build'
CXX(target) Release/obj.target/bignum/bignum.o
SOLINK_MODULE(target) Release/obj.target/bignum.node
COPY Release/bignum.node
make: Leaving directory
'/home/pi/homebridge/node_modules/HAP-NodeJS/node_modules/srp/node_modules/bignum/build'
npm ERR! Linux 3.18.7-v7+
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v4.1.1
npm ERR! npm  v2.14.4
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the curve25519 package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls curve25519
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/pi/homebridge/npm-debug.log
pi@raspberrypi ~/homebridge $
Thanks again!

@dreameruk
try:
npm install

without sudo, I've to check this point and correct the wiki.

Thanks however now:
pi@raspberrypi ~/homebridge $ npm install
npm WARN engine<EMAIL_ADDRESS>wanted: {"node":"~0.10.0"} (current:
{"node":"4.1.1","npm":"2.14.4"})

<EMAIL_ADDRESS>install /home/pi/homebridge/node_modules/HAP-NodeJS/node_modules/ed25519
node-gyp rebuild

make: Entering directory
'/home/pi/homebridge/node_modules/HAP-NodeJS/node_modules/ed25519/build'
CC(target) Release/obj.target/ed25519/src/ed25519/keypair.o
CC(target) Release/obj.target/ed25519/src/ed25519/sign.o
CC(target) Release/obj.target/ed25519/src/ed25519/open.o
CC(target) Release/obj.target/ed25519/src/ed25519/crypto_verify_32.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_double_scalarmult.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_frombytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_scalarmult_base.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_precomp_0.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p2_0.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p2_dbl.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_0.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_dbl.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_to_p2.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_to_cached.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_tobytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_madd.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_add.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_msub.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_sub.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p1p1_to_p3.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p1p1_to_p2.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_tobytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_0.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_1.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_cmov.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_copy.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_neg.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_add.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_sub.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_mul.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_sq.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_sq2.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_invert.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_tobytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_isnegative.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_isnonzero.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_frombytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_pow22523.o
CC(target) Release/obj.target/ed25519/src/ed25519/sc_reduce.o
CC(target) Release/obj.target/ed25519/src/ed25519/sc_muladd.o
CXX(target) Release/obj.target/ed25519/src/ed25519.o
SOLINK_MODULE(target) Release/obj.target/ed25519.node
COPY Release/ed25519.node
make: Leaving directory
'/home/pi/homebridge/node_modules/HAP-NodeJS/node_modules/ed25519/build'

<EMAIL_ADDRESS>install /home/pi/homebridge/node_modules/HAP-NodeJS/node_modules/curve25519
node-gyp rebuild

make: Entering directory
'/home/pi/homebridge/node_modules/HAP-NodeJS/node_modules/curve25519/build'
CXX(target) Release/obj.target/curve/node_curve.o
SOLINK_MODULE(target) Release/obj.target/curve.node
COPY Release/curve.node
make: Leaving directory
'/home/pi/homebridge/node_modules/HAP-NodeJS/node_modules/curve25519/build'

<EMAIL_ADDRESS>install /home/pi/homebridge/node_modules/HAP-NodeJS/node_modules/srp/node_modules/bignum
node-gyp configure build

make: Entering directory
'/home/pi/homebridge/node_modules/HAP-NodeJS/node_modules/srp/node_modules/bignum/build'
CXX(target) Release/obj.target/bignum/bignum.o
SOLINK_MODULE(target) Release/obj.target/bignum.node
COPY Release/bignum.node
make: Leaving directory
'/home/pi/homebridge/node_modules/HAP-NodeJS/node_modules/srp/node_modules/bignum/build'
npm WARN unmet dependency
/home/pi/homebridge/node_modules/node-hue-api requires<EMAIL_ADDRESS>but will load
npm WARN unmet dependency /home/pi/homebridge/node_modules/xml2js,
npm WARN unmet dependency which is version 0.4.12
npm WARN unmet dependency
/home/pi/homebridge/node_modules/node-hue-api requires<EMAIL_ADDRESS>but
will load
npm WARN unmet dependency /home/pi/homebridge/node_modules/q,
npm WARN unmet dependency which is version 1.4.1
npm WARN unmet dependency
/home/pi/homebridge/node_modules/harmonyhubjs-client/node_modules/node-stringprep
requires<EMAIL_ADDRESS>but will load
npm WARN unmet dependency /home/pi/homebridge/node_modules/debug,
npm WARN unmet dependency which is version 2.2.0
npm WARN unmet dependency
/home/pi/homebridge/node_modules/harmonyhubjs-client/node_modules/node-xmpp-client
requires<EMAIL_ADDRESS>but will load
npm WARN unmet dependency /home/pi/homebridge/node_modules/request,
npm WARN unmet dependency which is version 2.49.0
npm WARN unmet dependency
/home/pi/homebridge/node_modules/harmonyhubjs-client/node_modules/node-xmpp-client
requires<EMAIL_ADDRESS>but will load
npm WARN unmet dependency
/home/pi/homebridge/node_modules/harmonyhubjs-client/node_modules/node-xmpp-core,
npm WARN unmet dependency which is version 1.0.0
npm WARN unmet dependency
/home/pi/homebridge/node_modules/harmonyhubjs-client/node_modules/node-xmpp-client
requires<EMAIL_ADDRESS>but will load
npm WARN unmet dependency /home/pi/homebridge/node_modules/debug,
npm WARN unmet dependency which is version 2.2.0
npm WARN unmet dependency
/home/pi/homebridge/node_modules/harmonyhubjs-client/node_modules/node-xmpp-core
requires<EMAIL_ADDRESS>but will load
npm WARN unmet dependency
/home/pi/homebridge/node_modules/harmonyhubjs-client/node_modules/node-stringprep,
npm WARN unmet dependency which is version 0.6.2
<EMAIL_ADDRESS>node_modules/ad2usb
└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>node_modules/lifx
├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS>node_modules/elkington
└──<EMAIL_ADDRESS><EMAIL_ADDRESS>node_modules/HAP-NodeJS
├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS>Tried running server and get same error about mdms
Thanks

Hi @cflurin thanks, I missed that one : it seems I was still on 4.1.6-v7+  ... unfortunately it didn't fix it... I guess I'll start from a mint image. Just checking: where did you get yours? just the default one from the RPi site or a "Special" one ?

@dreameruk  the homebridge installation seems to be OK.
There must be an issue with Avahi ... I'm investigating.

@dreameruk
try again:
sudo apt-get install libavahi-compat-libdnssd-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libavahi-compat-libdnssd-dev is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

You should get the same result as above

@desvdp: I've downloaded the origin NOOBS here

pi@raspberrypi ~ $ sudo apt-get install libavahi-compat-libdnssd-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libavahi-compat-libdnssd-dev is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
pi@raspberrypi ~ $ npm run start
npm ERR! Linux 3.18.7-v7+
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "start"
npm ERR! node v4.1.1
npm ERR! npm  v2.14.4
npm ERR! path /home/pi/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! Please include the following file with any support request:
npm ERR!     /home/pi/npm-debug.log
pi@raspberrypi ~ $ cd homebridge
pi@raspberrypi ~/homebridge $ npm run start

<EMAIL_ADDRESS>start /home/pi/homebridge
DEBUG=* node app.js || true

module.js:338
throw err;
^
Error: Cannot find module 'mdns'
at Function.Module._resolveFilename (module.js:336:15)
at Function.Module._load (module.js:286:25)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at Object.
(/home/pi/homebridge/node_modules/HAP-NodeJS/lib/Advertiser.js:1:74)
at Module._compile (module.js:434:26)
at Object.Module._extensions..js (module.js:452:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Module.require (module.js:365:17)
pi@raspberrypi ~/homebridge $
On 25/09/2015, cflurin<EMAIL_ADDRESS>wrote:

@dreameruk
try again:
sudo apt-get install libavahi-compat-libdnssd-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libavahi-compat-libdnssd-dev is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

You should get the same result as above

Reply to this email directly or view it on GitHub:
https://github.com/nfarina/homebridge/issues/205#issuecomment-143242259

@cflurin Ok.. that's a difference then: I started from the Raspbian image (using dd etc ...  )

@dreameruk can you try:

npm install mdns

@cflurin Yes that did as yours did:
pi@raspberrypi ~ $ sudo apt-get install libavahi-compat-libdnssd-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libavahi-compat-libdnssd-dev is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
However still same error when try running server

@desvdp trying now thanks

@dreameruk
reboot your RPi
post your uname -a

@desvdp thanks, that fixed it I now only get the following error, so just need to setup the config file:
@cflurin thanks also for your help!
pi@raspberrypi ~/homebridge $ npm run start

<EMAIL_ADDRESS>start /home/pi/homebridge
DEBUG=* node app.js || true

*** WARNING *** The program 'node' uses the Apple Bonjour
compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see
http://0pointer.de/avahi-compat?s=libdns_sd&e=node
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which
is not supported (or only supported partially) in the Apple Bonjour
compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see
http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister
Starting HomeBridge server...

IMPORTANT: Homebridge is in the middle of some big changes.
Read more about it here:
https://github.com/nfarina/homebridge/wiki/Migration-Guide

There was a problem reading your config.json file.
Please try pasting your config.json file here to validate it:
http://jsonlint.com
/home/pi/homebridge/app.js:43
throw err;
^
SyntaxError: Unexpected token /
at Object.parse (native)
at Object. (/home/pi/homebridge/app.js:37:17)
at Module._compile (module.js:434:26)
at Object.Module._extensions..js (module.js:452:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Function.Module.runMain (module.js:475:10)
at startup (node.js:117:18)
at node.js:951:3
pi@raspberrypi ~/homebridge $

@dreameruk
could you please post your package.json

@dreameruk  Yeah, that's just an error in the config.json: just use the linter as suggested. You're now ahead of me: I can't ge the mdns to work :-)

@desvdp - hope you get there too :)
@cflurin - sure here it is:
{
"name": "homebridge",
"description": "HomeKit support for the impatient",
"version": "0.1.1",
"scripts": {
"start": "DEBUG=* node app.js || true"
},
"repository": {
"type": "git",
"url": "git://github.com/nfarina/homebridge.git"
},
"license": "ISC",
"dependencies": {
"ad2usb": "git+https://github.com/alistairg/node-ad2usb.git#local",
"carwingsjs": "0.0.x",
"chokidar": "^1.0.5",
"color": "0.10.x",
"eibd": "^0.3.1",
"elkington": "kevinohara80/elkington",
"hap-nodejs": "git+https://github.com/KhaosT/HAP-NodeJS#4650e771f356a220868d873d16564a6be6603ff7",
"lifx-api": "^1.0.1",
"lifx": "git+https://github.com/magicmonkey/lifxjs.git",
"mdns": "^2.2.4",
"node-hue-api": "^1.0.5",
"node-icontrol": "^0.1.4",
"node-milight-promise": "0.0.x",
"node-persist": "0.0.x",
"q": "1.4.x",
"tough-cookie": "^2.0.0",
"request": "2.49.x",
"sonos": "0.8.x",
"telldus-live": "0.2.x",
"teslams": "1.0.1",
"unofficial-nest-api": "git+https://github.com/hachidorii/unofficial_nodejs_nest.git#d8d48edc952b049ff6320ef99afa7b2f04cdee98",
"wemo": "0.2.x",
"wink-js": "0.0.5",
"xml2js": "0.4.x",
"xmldoc": "0.1.x",
"komponist" : "0.1.0",
"yamaha-nodejs": "0.4.x",
"debug": "^2.2.0"
}
}

@dreameruk:
strange mdns is a dependency and should be installed using your package.json.

Seems few other things did not install either, stripped back my config for only Sonos to test it. Run server and get following. Any ideas how to resolve?
Many thanks again!

pi@raspberrypi ~ $ cd homebridge
pi@raspberrypi ~/homebridge $ npm run start

<EMAIL_ADDRESS>start /home/pi/homebridge
DEBUG=* node app.js || true

*** WARNING *** The program 'node' uses the Apple Bonjour
compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see
http://0pointer.de/avahi-compat?s=libdns_sd&e=node
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which
is not supported (or only supported partially) in the Apple Bonjour
compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see
http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister
Starting HomeBridge server...

IMPORTANT: Homebridge is in the middle of some big changes.
Read more about it here:
https://github.com/nfarina/homebridge/wiki/Migration-Guide

Loading 1 platforms...
module.js:338
throw err;
^
Error: Cannot find module 'cookie-jar'
at Function.Module._resolveFilename (module.js:336:15)
at Function.Module._load (module.js:286:25)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at Object.
(/home/pi/homebridge/node_modules/sonos/node_modules/request/index.js:15:14)
at Module._compile (module.js:434:26)
at Object.Module._extensions..js (module.js:452:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Module.require (module.js:365:17)
at require (module.js:384:17)

@dreameruk
did you make a npm install as non root user inside the homebridge directory?

Am 25.09.2015 um 17:09 schrieb cflurin -<EMAIL_ADDRESS>@dreameruk:
strange mdns is a dependency and should be installed using your package.json.
—
Reply to this email directly or view it on GitHub.

I was a root user

@dreameruk
sorry it was my mistake with sudo ( I've modified the wiki)
If you like, you can rename homebridge to homebridge-01
cd home
and start again installing homebridge

I'm puzzled ... the mdns package keeps on bugging me and I can't find what's wrong with it... I'd guess it has to do with the nan package

><EMAIL_ADDRESS>install /home/pi/test2/node_modules/mdns
> node-gyp rebuild
make: Entering directory '/home/pi/test2/node_modules/mdns/build'
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_sd.o
In file included from /home/pi/.node-gyp/4.1.0/include/node/node.h:42:0,
from ../src/mdns.hpp:11,
from ../src/dns_sd.cpp:1:
/home/pi/.node-gyp/4.1.0/include/node/v8.h:336:1: error: expected unqualified-id before 'using'
/home/pi/.node-gyp/4.1.0/include/node/v8.h:469:1: error: expected unqualified-id before 'using'
/home/pi/.node-gyp/4.1.0/include/node/v8.h:852:1: error: expected unqualified-id before 'using'
In file included from ../node_modules/nan/nan.h:182:0,
from ../src/mdns.hpp:12,
from ../src/dns_sd.cpp:1:
../node_modules/nan/nan_maybe_43_inl.h:13:1: error: expected unqualified-id before 'using'
../node_modules/nan/nan_maybe_43_inl.h:16:1: error: expected unqualified-id before 'using'
../node_modules/nan/nan_maybe_43_inl.h:19:12: error: 'Maybe' does not name a type
../node_modules/nan/nan_maybe_43_inl.h:24:12: error: 'Maybe' does not name a type
../node_modules/nan/nan_maybe_43_inl.h:31:1: error: 'MaybeLocal' does not name a type
.....

Installed versions:

>uname -a
Linux raspberrypi 4.1.7-v7+ #817 SMP PREEMPT Sat Sep 19 15:32:00 BST 2015 armv7l GNU/Linux
>node -v
v4.1.0
> npm -v
2.14.3
gcc version 4.6.3 (Debian 4.6.3-14+rpi1)

@desvdp
It really strange, it should be possible. I tried in test folder:
pi@raspberrypi ~/test/mdns $ npm install mdns
/
><EMAIL_ADDRESS>install /home/pi/test/mdns/node_modules/mdns
> node-gyp rebuild

make: Entering directory '/home/pi/test/mdns/node_modules/mdns/build'
  CXX(target) Release/obj.target/dns_sd_bindings/src/dns_sd.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_browse.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_enumerate_domains.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_get_addr_info.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_process_result.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_ref.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_ref_deallocate.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_ref_sock_fd.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_register.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_resolve.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/mdns_utils.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/network_interface.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/socket_watcher.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/txt_record_ref.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/txt_record_create.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/txt_record_deallocate.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/txt_record_set_value.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/txt_record_get_length.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/txt_record_buffer_to_object.o
  SOLINK_MODULE(target) Release/obj.target/dns_sd_bindings.node
  COPY Release/dns_sd_bindings.node
make: Leaving directory '/home/pi/test/mdns/node_modules/mdns/build'
<EMAIL_ADDRESS>node_modules/mdns
├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>

@cflurin Thanks for testing, I'm currently loading a mint image in order to start over from scratch (busy doing apt-get upgrade)... in retrospective I wonder if the ~/.node-gyp had anything to do with it ... unfortunately I've already re-imaged the SD card so I can't verify the hypothesis...

@cflurin Ok ... I'm officially lost: brand new image, downloaded from the RPi site (Raspbian). The issued these commands, no more no less:
pi@raspberrypi ~/node-v4.1.1-linux-armv7l/test $ history
1  rpi-update
2  sudo rpi-update
3  reboot
4  sudo reboot
5  sudo apt-get update
6  sudo apt-get upgrade
7  sudo reboot
8  wget https://nodejs.org/dist/v4.1.1/node-v4.1.1-linux-armv7l.tar.gz
9  tar -xvf node-v4.1.1-linux-armv7l.tar.gz
10  cd node-v4.1.1-linux-armv7l/
11  sudo cp -R * /usr/local/
12  node -v
13  sudo apt-get install libavahi-compat-libdnssd-dev
14  mkdir test
15  cd test
16  npm install mdns
17  history
got the exact same error as before ... don't get it ... what am I missing here ?

One thing that concerns me: looking at the cpp error:

In file included from /home/pi/.node-gyp/4.1.1/include/node/node.h:42:0,
from ../src/mdns.hpp:11,
from ../src/dns_sd.cpp:1:
/home/pi/.node-gyp/4.1.1/include/node/v8.h:336:1: error: expected unqualified-id before 'using'
/home/pi/.node-gyp/4.1.1/include/node/v8.h:469:1: error: expected unqualified-id before 'using'
/home/pi/.node-gyp/4.1.1/include/node/v8.h:852:1: error: expected unqualified-id before 'using'
In file included from ../node_modules/nan/nan.h:182:0,

As far I know ... "using" is a C++11 feature when applied to a type. GCC 4.6 imho has no C++11 support.
In specific:  "Template aliases" were only introduced in GCC 4.7

http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2258.pdf
https://gcc.gnu.org/gcc-4.6/cxx0x_status.html

@desvdp
I didn't explicitly install gcc but yes the version is the same:
gcc (Raspbian 4.8.2-21~rpi3rpi1) 4.8.2

I hope, you can now use homebridge :smile:

Hi @cflurin thanks for confirming: maybe you can add a note to your wiki page... ;-) (btw, about that page: really nice work !)
Actually I've been using homebridge for quite some time already (and loving it !!), but on node 0.12.6. I'm currently going through the pain of upgrading to 4.x.x hoping to be more future proof...  next up ... node-serialport :-)

@desvdp Wiki updated, thanks. BTW this will probably be obsolete as soon the homebridge-shims will be installed as plug-ins.

@cflurin thanks for help, home bridge now connecting to phone - now to get Siri working.
@desvdp sorry only just saw this, glad you resolved it!
Will close the issue as all resolved. Thanks again.

@cflurin I'm not sure: I assume the mdns module will be part of the "core", although being pulled in via HAP-nodejs. In order to get the basic setup right, one would still need the right compiler...

@desvdp I think so, I'ver just installed node 4.0.0 and homebridge on RPi B (armv6l).
It perfectly works! The crucial point is the gcc 4.8 (thanks again for the tip). I'm updating the wiki now.

@cflurin : might be worth to update the wiki again ... https://www.raspberrypi.org/blog/raspbian-jessie-is-here/ no more isseus getting gcc 4.8 I suppose ...

@desvdp Thanks, I'll first install jessie ...

@cflurin Btw ... I haven't tried it yet myself (I will tonight ;-) ) , but this looks like a cool post : http://ryanteck.org.uk/rpi-sd-card-image-smallification/

It works with Jessie too. No need to change the Wiki.

I managed to validate my config.json but I get an error in output for npm run start.
Avahi is installed however
pi@raspberrypi ~/node-v4.2.1-linux-armv7l/homebridge $ npm run start

<EMAIL_ADDRESS>start /home/pi/node-v4.2.1-linux-armv7l/homebridge
DEBUG=* node app.js || true

*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister
Starting HomeBridge server...

IMPORTANT: Homebridge is in the middle of some big changes.
Read more about it here:
https://github.com/nfarina/homebridge/wiki/Migration-Guide

There was a problem reading your config.json file.
Please try pasting your config.json file here to validate it: http://jsonlint.com
/home/pi/node-v4.2.1-linux-armv7l/homebridge/app.js:43
throw err;
^
SyntaxError: Unexpected token
at Object.parse (native)
at Object. (/home/pi/node-v4.2.1-linux-armv7l/homebridge/app.js:37:17)
at Module._compile (module.js:435:26)
at Object.Module._extensions..js (module.js:442:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:311:12)
at Function.Module.runMain (module.js:467:10)
at startup (node.js:134:18)
at node.js:961:3


Update to solid 1.0.3

Hello,
Thanks for your work in the Solid.js ecosystem, I thought I might help by migrating this package to Solid.js 1.0.3 as I need it for one of my project.
Changes were pretty straightforward, just had to migrate assignProps to mergeProps and createResource.
I tested it in my project, and it seems to work properly, but maybe I'm missing something else. Let me know 👍

Seems like createResource was failing silently, I moved the auth0ClientPromise before instead of after and Auth0 seems to initialize correctly now

Thanks for doing this. Looks good.


Add TypeScript definitions

This pull request adds type metadata so that TypeScript users can use the library.

Thanks for the contribution! Published as v3.2.0.

Happy to help 👍

@delta62 I'm trying to use this like:
import ExtendableError from 'es6-error';

which tsc/babel compiles but gives runtime error
Uncaught TypeError: Super expression must either be null or a function, not undefined

This works for me (TS obviously complains):
import * as ExtendableError from 'es6-error';

Thoughts?

Yeah, you're right. It looks like the CJS exports are getting set up wrong:
exports.default = ExtendableError;
module.exports = exports['default']; // Oops, module.exports.default === undefined

Since
import ExtendableError from 'es6-error';

is sugar for
import { default as ExtendableError } from 'es6-error';

TypeScript (I am assuming you're targeting ES5) compiles into something similar to
var ExtendableError = require('es6-error').default;

I'd say that the Babel configuration / plugins for CommonJS exports need to be adjusted. I can create a PR in the next few days, but feel free to take it yourself if you need it quicker :)

@delta62 I think I would be more comfortable with you doing that :)

Okay, no problem. I'm out on vacation now, but I'll try to get a PR up when I come back at the end of this week.


Installation description outdated

From the README:

Installation
TSBS is a collection of Go programs (with some auxiliary bash and Python
scripts). The easiest way to get and install the Go programs is to use
go get and then make all to install all binaries:
# Fetch TSBS and its dependencies
$ go get github.com/timescale/tsbs
$ cd $GOPATH/src/github.com/timescale/tsbs
$ make

Using go 1.21.3, go get github.com/timescale/tsbs returns
go: go.mod file not found in current directory or any parent directory.
        'go get' is no longer supported outside a module.
        To build and install a command, use 'go install' with a version,
        like 'go install example.com/cmd@latest'
        For more information, see https://golang.org/doc/go-get-install-deprecation
        or run 'go help get' or 'go help install'.

Try:
go install github.com/timescale/tsbs@latest
cd go/pkg/mod/github.com/timescale/tsbs@*

Try:
go install github.com/timescale/tsbs@latest
cd go/pkg/mod/github.com/timescale/tsbs@*

This doesn't work anymore in go1.23.2 windows/amd64.
Output is:
C:\tsbs> go install github.com/timescale/tsbs@latest
go: github.com/timescale/tsbs@latest: module github.com/timescale/tsbs@latest found (v0.0.0-20230921131859-37fced794d56), but does not contain package github.com/timescale/tsbs


Why there is a support for two default .env files?

Question Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Question Subject

From my understanding the purpose of loading .env automatically is to have a default environment which is always loaded - this is cool but why .env.default is loaded automatically as well?
I do not understand the need for using .env.default file. If one wants to have some default environment variables it is reasonable to put them just in one file.
There is no difference whether you will only put them in .env or .env.default file - or am I missing something?
There is no option to use .env or .env.default separately so it is the same like keeping all the values from both of these files just in .env which is meant to be a default one by the dotenv authors.
Question Description

https://github.com/fastlane/fastlane/blob/f32b007ff45e648b37b6c9c2037ac481f36b7780/fastlane/lib/fastlane/helper/dotenv_helper.rb#L29-L32
Looking at these lines it also means that if one is using two files, then it can lead to a greater confusion. In example if keys in both files are not disjoint then only values from .env for these keys will be loaded which might not be intuitive.
However, like I said above if these are the default values why keeping them in two files which are always loaded?

but why .env.default is loaded automatically as well?

Possibly a misunderstanding ~4 years ago when this code was first added:
https://github.com/fastlane/fastlane/commit/a571512ce69dbfe141e48c92fb13597220589fb8#diff-685e939a0c766697a0a7eb8539782195R13 Today changing the behavior ould break backwards compatibility.
Is this causing any actual problems?

Yes, the only way to break compatibility would be to do it with the next major release of fastlane.
To close this off, did you encounter any documentation of fastlane switching between the two methods? That we could fix by defaulting to one of the two files and removing the mention of the other already.

Only here.


No GlobalCrashHandler equivalent for WinJS

The GlobalCrashHandler class assumes you're using a XAML-based application, so I wanted to roll my own to handle the same situation for WinJS.  Unfortunately, the LazyFlushManager is internal and so is the GetTargets method on the LoggingConfiguration.
So, I can't figure out how to make sure that all the messages are flushed before the app exits.

Closing for now. Will re-open if needed. Seems like WinJS usage is pretty low?


spamx.sh

Changes :- just adding clear command in 4th line
Just because it won't run properly
Now it will run properly  MR. NH you did a great
work all thanks to You buddy.

Changes :- just adding clear command in 4th line
It because some time it is not running properly
Now it will run properly MR. NH you did a great
work all thanks to You buddy.

Thanks


Fixed Buy Merchandise Section and Added Missing Favicons

Issue fixed #377
Description:
This pull request addresses two key issues:
Fixed Buy Merchandise Section:

Resolved the styling inconsistencies and responsiveness issues in the Buy Merchandise section.
Improved the layout and alignment of product cards, ensuring a consistent look across different screen sizes.
Optimized the product images to load faster and provide a better user experience.
Enhanced the overall visual appeal of the section with hover effects.

Hover Animation

hover animation is applied to cards
and on the buttons with unique transformations.

Added Missing Favicons:

Added favicons on the Appearances and Remarkable Achievements pages

Steps:
Identified and Fixed Styling Issues:

Reviewed the CSS code for the Buy Merchandise section and corrected any errors or inconsistencies.
Adjusted the media queries to ensure optimal layout and responsiveness on different screen sizes.
Added animation on cards and buttons.
optimizing the layout of the cards.

Added Missing Favicons:

Updated the favicon links on the Appearances and Remarkable Achievements pages.

Videos / screenshot
https://github.com/user-attachments/assets/147e784c-3f6e-410e-bc0a-af21c8fa87f8

Great work!

Thank you for your valuable feedback.

@aslams2020 please add gssoc-ext label

Ohk, i forgot to add. Thanks for notifying me

Ohk, i forgot to add. Thanks for notifying me

It's ok sir


Quick Installation Help

##Dear dev's,
When I restarted git bash as advised in the installation readme, the following is returned as the first line:
/c/Users/GunnyLiu/.pyenv/bin/pyenv: line 1: ../libexec/pyenv: No such file or directory
What is going on?
-gunny

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/35996397-quick-installation-help?utm_campaign=plugin&utm_content=tracker%2F282009&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F282009&utm_medium=issues&utm_source=github).

https://github.com/yyuu/pyenv/issues/332#issuecomment-81199008


Allow to repplace dialog action(OK and Cancel button) on DatePicker by another component

Hello everyone,
I have search for many hours and can't find the way to custom the bottom of datepicker like the image above.
Is there any way to do this.
I hope to get the answer and sorry for my English.
Thank you very much

@voquochuyhuy What version are you using?

@voquochuyhuy You could use the static version of the date range picker and compose a couple of textboxes to reach the same output.

@oliviertassinari Thank for fast reply.
I'm using @material-ui/pickers": "^3.2.10" and "@material-ui/core": "^4.3.1".
But I don't understand "use the static version of the date range picker",that mean i have to use another npm package?. I want to know is there anyway to replace ok and cancel button on datepicker dialog because I have to custom it from @material-ui/pickers to the date range picker like the image above

Oh,I find I can solve my problem by use calendar in my custom model, so it's easy to handle dialog action. Anyway , thanks alot


CSI Data Specificaition (AEGHB-141)

I have a question about CSI data that received. What is the unit of imaginary and real part? why there are double-digit without decimal fraction. what is the meaning of imaginary and real part? What is the basis to calculate this two data part? Thanks in advance.

There is no unit for both imaginary and real part of CSI data.
For the data is sampled and quantified at the PHY.
CSI represents the change of the signal from a transmitter (denote it as x) to a receiver (denote it as y) and it is represented in the frequency domain as y = Hx + n, where H is a complex matrix consisting of CSI values and n is the
channel noise.
The CSI for each subcarrier is: h = |h|e jθ , where |h| represents the amplitude and θ the phase. #24 and #95 may help.

By the way, for detailed information, this paper Human Activity Recognition based on Wi-Fi CSI Data -A Deep Neural Network Approach is recommended

Hello, @zikunliu
Closing this issue, feel free to reopen with more updates. Thanks.


Warnings at compile

libtorrent/src/rss.cpp:427:3: warning: invalid access to non-static data member ‘libtorrent::feed::m_title’  of NULL object [-Winvalid-offsetof]
libtorrent/src/rss.cpp:427:3: warning: (perhaps the ‘offsetof’ macro was used incorrectly) [-Winvalid-offsetof]
libtorrent/src/rss.cpp:428:3: warning: invalid access to non-static data member ‘libtorrent::feed::m_description’  of NULL object [-Winvalid-offsetof]
libtorrent/src/rss.cpp:428:3: warning: (perhaps the ‘offsetof’ macro was used incorrectly) [-Winvalid-offsetof]
libtorrent/src/rss.cpp:429:3: warning: invalid access to non-static data member ‘libtorrent::feed::m_last_attempt’  of NULL object [-Winvalid-offsetof]
libtorrent/src/rss.cpp:429:3: warning: (perhaps the ‘offsetof’ macro was used incorrectly) [-Winvalid-offsetof]
libtorrent/src/rss.cpp:430:3: warning: invalid access to non-static data member ‘libtorrent::feed::m_last_update’  of NULL object [-Winvalid-offsetof]
libtorrent/src/rss.cpp:430:3: warning: (perhaps the ‘offsetof’ macro was used incorrectly) [-Winvalid-offsetof]
libtorrent/src/session_impl.cpp:537:3: warning: invalid access to non-static data member ‘libtorrent::aux::session_impl::m_settings’  of NULL object [-Winvalid-offsetof]
libtorrent/src/session_impl.cpp:537:3: warning: (perhaps the ‘offsetof’ macro was used incorrectly) [-Winvalid-offsetof]
libtorrent/src/session_impl.cpp:539:3: warning: invalid access to non-static data member ‘libtorrent::aux::session_impl::m_dht_settings’  of NULL object [-Winvalid-offsetof]
libtorrent/src/session_impl.cpp:539:3: warning: (perhaps the ‘offsetof’ macro was used incorrectly) [-Winvalid-offsetof]
libtorrent/src/session_impl.cpp:541:3: warning: invalid access to non-static data member ‘libtorrent::aux::session_impl::m_proxy’  of NULL object [-Winvalid-offsetof]
libtorrent/src/session_impl.cpp:541:3: warning: (perhaps the ‘offsetof’ macro was used incorrectly [-Winvalid-offsetof]
libtorrent/src/session_impl.cpp:546:3: warning: invalid access to non-static data member ‘libtorrent::aux::session_impl::m_pe_settings’  of NULL object [-Winvalid-offsetof]
libtorrent/src/session_impl.cpp:546:3: warning: (perhaps the ‘offsetof’ macro was used incorrectly) [-Winvalid-offsetof]
src/twister.cpp:38:0: warning: "TORRENT_DISABLE_GEO_IP" redefined [enabled by default]
:0:0: note: this is the location of the previous definition

In the code:
./src/twister.cpp:38:#define TORRENT_DISABLE_GEO_IP
Also inserted in the command line for the compiler:
./Makefile:COMPILETIME_OPTIONS =  -DTORRENT_USE_OPENSSL  -DTORRENT_DISABLE_GEO_IP  -DBOOST_ASIO_HASH_MAP_BUCKETS=1021  -DBOOST_EXCEPTION_DISABLE  -DBOOST_ASIO_ENABLE_CANCELIO  -DBOOST_ASIO_DYN_LINK -DTORRENT_LINKING_SHARED


Out-of-date browser support

Browser support includes every sane browser and IE7+.

I believe this statement in the README is incorrect. Even in  the horsey.es5.js file, the ES6 Symbol is being used without a polyfill. Because of this, among other issues, horsey does not work on any version of IE.

Also, I believe IE is barfing on this throw with error Object expected:
https://github.com/bevacqua/horsey/blob/master/dist/horsey.js#L434

try -> catch -> finally -> try -> finally -> throw ( ⧉ ⦣ ⧉ )

The culprit might be the for (... of ...) loop here https://github.com/bevacqua/horsey/blob/b975868e64b094b9369ed8722e508ed2b8cf3b37/horsey.js#L364 which looks like it's being transformed with babel or something to provide the feature with ES5.

This also seems to be related https://github.com/babel/babel/issues/4451.
Specifically https://github.com/babel/babel/issues/4451#issuecomment-245415431 which looks similar to the bundled output.


Introduce ReturnFormat option to allow detailed or value-only outputs

This Pull Request addresses https://github.com/bramus/style-observer/issues/8 by introducing a new ReturnFormat option to the CSSStyleObserver. This enhancement allows users to choose between receiving only the current values of observed CSS properties or detailed information that includes previous values and change statuses
Changes

Introduced the ReturnFormat enum with options VALUE_ONLY (default) and OBJECT
Updated the CSSStyleObserver class to process observed properties based on the selected ReturnFormat
Updated the README.md to reflect the new ReturnFormat option and provide usage examples

Absolutely, that makes sense and would simplify switching between return formats - I have made the changes accordingly!
I did notice that the propertyName is duplicated both as the key and within each CSSPropertyInfo object. To avoid redundancy, perhaps we could omit the propertyName field inside the object since the key already provides that information. This would make the structure cleaner:
{
    "--my-variable": {
        "value": "1.0",
        "previousValue": "0.0",
        "changed": true
    },
    "display": {
        "value": "block",
        "previousValue": "block",
        "changed": false
    }
}

your thoughts on this?

Yeah, makes sense. Devs should use Object.entries() when looping the results.


Change home page link href to include #features

This will allow back navigation from element page to demo

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks broke.

Comments from Reviewable


Add tests for BC7 and UASTC4x4 transcoding.

Each test transcodes a 16x16 version of the Avocado.glb baseColor texture, shown below. I generated the 'golden' output with msc_basis_transcoder.js, which matched without changes.
Output:

 Archive.zip

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Looks great! Couple suggestions.

Replace single avocado image with the generator (#9)
Add CI via GitHub Actions:

✔ npm run asbuild succeeds
✔ build/ directory doesn't change after running npm run asbuild
✔ BC7, ASTC, and RGBA32_UNORM transcoding tests

Note that the output of our BC7 transcoder for UASTC Mode Index 8 blocks doesn't match the reference (MSC). This doesn't affect texture sampling results. We may need to maintain a custom MSC build to include those blocks in CI.

How should the first change be structured? I'm assuming:

Generate 'source' texture with the generator offline.
Generate 'golden' transcoder output offline (with this tool or the MSC transcoder).
Check the 'source' and 'golden' files into version control.
When running the unit tests, the 'source' is transcoded and compared against the 'golden' output.

Is that what you had in mind? I don't think that the golden files need to come from the MSC tool necessarily. We can generate goldens with these transcoders, keep them checked into the repository, and manually inspect output images if the output is changed intentionally — I assume that is rare.

UASTC is a very complex format. I wouldn't expect any "git-friendly" amount of test data to cover all possible transcoder code paths. For example, the latest ASTC transcoder bug (fixed earlier today) was affecting only 0.12% of 2.5GB dataset.

I see... in that case we will need the reference transcoder to be published on NPM to use it in our tests. I'm not sure when that will happen, since we're still waiting for various changes to be merged to the basis_universal repository. I don't know whether the current MSC transcoder works in node.js at all, and wouldn't want to maintain another variant of it.
Would you be okay with a few simple (not exhaustive) tests checked into Git in the meantime, to unblock https://github.com/KhronosGroup/Universal-Texture-Transcoders/issues/7#issuecomment-688376393?

Here's my current local setup:

2.5 GB of random data created with the generator + 320 MB converted from the sample models repo.
A reference (MSC) transcoder build with tweaked UASTC Mode Index 8 to BC7 transcoding.
Everything runs in Node.js CLI.

I don't know much about npm best practices, but the following setup seems pretty straightforward:

Compile a minimal (only needed formats) reference transcoder with the required BC7 tweak and check it in here (I can provide and maintain that easily).
During the CI run, generate and transcode data in memory, compare the results.

Checking in the modified reference transcoder might be good for now, then. How long does the generator take to generate 2.5 GB of sample data? I'd probably want to leave the glTF-Sample-Models repository out of the CI tests, downloading and encoding those would make CI much slower and potentially fragile.

The generator completes 19 modes * 8388608 blocks * 16 bytes in 12 seconds, including disk IO. We could speed up this by requesting fewer blocks for more simple modes (out of scope for now).

Ok, that seems more than sufficiently quickly. 🙂
I'll leave this PR alone for now, and update it after a reference transcoder is available, then?

With the generator and the MSC transcoder merged, I think we can proceed here.

@lexaknyazev I've integrated the generator and MSC transcoder. A few notes:
Transcoding 1024x1024 textures, it took about 3 minutes to complete tests for the two transcode targets above. That seemed slower than I'd like for quickly testing a change. So I included two macros here: npm run test does a faster build on 128x128 textures and completes in 12 seconds. npm run test:ci does a full test on 1024x1024 textures, and is intended to run on the GitHub Action (or manually, when needed).
Does this look OK so far? I'll add RGBA32_UNORM if so.
I'd like to check in the tests first, and then set up the CI in a separate PR.

Looks great overall, added a few comments.
As a future CI performance enhancement, we should be able to determine the minimum number of generated blocks for each of 19 modes that covers all possible transcode code paths.

Added the RGBA32 test — it's failing, with:
Incorrect array length. Expected 33554432 but got 262144.

With 256 x 256 x 4 = 262144, the reference transcoder is returning a larger response than I expect here. 😕

Tests are passing. ✅

Would it be possible to add an extra RGBA32 test for images with non-multiples-of-4 dimensions (like (WIDTH - 1) * (HEIGHT - 1)?

OK — the RGBA32 - npot test passes, but I'm not sure I understand part of it.

You caught the main issue here, but with variable scopes fixed there's still a failure on:
Incorrect array length. Expected 4186116 but got 4190208.

Looks good now: https://github.com/donmccurdy/Universal-Texture-Transcoders/actions/runs/260538042

Since this PR adds new deps, please commit the updated package-lock.json.

Done 👍


Cursor Focus Lost

Hi,
Problem: Editor Cursor can not regain focus after switching applications.
Environment: I have Atom 1.22.0 x64 on Mac running platform-ide-terminal 2.7.0
Steps to Reproduce:

In Atom, Start an Editor Window Editing Some File
Enable Terminal (Control-BackTick)
Test that Switching Cursor Back and Forth between Editor and Terminal Works (Command-Alt-F a few times). Leave cursor in Terminal
Switch To Another Application (Command-Tab)
Switch Back to Atom (Command-Tab)
Now It is not possible to regain focus in Editor (ie. Command-Alt-F no longer works)

I have this issue too. When the outside application closes the only way to get focus back on the editor is to either click on it with the mouse, or press Ctrl-0 twice go to the tree view and then back to the editor. I'm not an expert, but somehow Ctrl-0 still works. Whatever Ctrl-0 does, maybe the fix can do that?

Please retest again with platformio-atom-ide-terminal 2.9.0.
These type issues all so far seem fixed with this release due to using node-pty-prebuilt instead unmaintained and outdated pty.js


[Feature] Align RocketMQ C# SDK Features with Java Version

Programming Language of the Client
C#
Is Your Feature Request Related to a Problem?
The current RocketMQ v5 C# SDK lacks several crucial features available in the Java version, including:

Push Consumer for Normal Messages
Push Consumer for FIFO Messages
Reentrant Push Consumer Message Receiving
Namespace Support

Describe the Solution You'd Like
N/A
Describe Alternatives You've Considered
N/A
Additional Context
N/A

I've been working on it and will create individual pull request for each stage/feature later.


request parameter

https://github.com/yiisoft/input-http/blob/8179c1be1588f04aa9c4ed4420c0fc098dcaab12/src/RequestInputParametersResolver.php#L41
is $request parameter that implement of ServerRequestInterface used for resolve processing?
should we override resolve parameter to resolve and match the request parameters?
please help to implement this function.
thank you

is $request parameter that implement of ServerRequestInterface used for resolve processing?

Yes.

should we override resolve parameter to resolve and match the request parameters?

No.

What do you want to achieve?

What do you want to achieve?

why $request not used in this function?

Because:

It is ParametersResolverInterface implementation, so parameters are needed there.
In this particular implementation, it is not used.


AzCopy inside powershell

Would it be useful to have AzCopy inside powershell. The combination seems to go in that direction?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1141c265-4aea-c6be-4d61-3566fe8474b8
Version Independent ID: 3cb0f2ba-cf8b-7fdd-414b-b8d95dca004c
Content: Copy or move data to Azure Storage with AzCopy on Windows | Microsoft Docs
Content Source: articles/storage/common/storage-use-azcopy.md
Service: storage
GitHub Login: @seguler
Microsoft Alias: seguler

Thanks for the feedback! Can you post this as a feedback @ https://feedback.azure.com/forums/217298-storage.  This will allow the community to upvote and for the product team to include into their plans.
We also have the "Give Product Feedback" button in our documents now, to take you directly to the appropriate feedback page.


[WFLY-14001] Unable query logging of H2 database

https://issues.redhat.com/browse/WFLY-14001

Thanks, @hokuda !


Fix missing

When copying from the web page, unnecessary half-width spaces are mixed behind the code. Indentation is misaligned.

@changeworld @linda33wj - The commits in this PR were moved to the private repo (PR 64912) for validation and staging. We'll close this PR now.


Integrate Pivotal broker-registrar

Purpose
Simplify registration of the broker at the CF CC.
Motivation
The current release requires manual (or otherwise automated) registration of the broker at the CF CC. There is however a Pivotal broker-registrar that would be handy to use instead.
Proposal
Integrate https://github.com/pivotal-cf/broker-registrar.
Changes

Add new submodule with the Pivotal broker-registrar
Add jobs for registration and deregistration to all deployment samples
Add missing properties and rename former cfcontainersbroker properties into broker

Remark about the changed property names
The Pivotal broker-registrar properties overlap significantly with the docker-boshrelease properties. Unfortunately they are called differently. To avoid property duplicates defining the same data, this change renames all cfcontainersbroker properties into broker (as they are called in broker-registrar).
Note of caution
Changes were done, tested, and put to production only with our own cloud infrastructure which is neither of the supported ones.
CC
@frodenas @holgerkoser

@vlerenc Although I agree that using the broker-registrar is a better approach, I've some comments around this PR:

The broker actually it registers itself on app initialization. If we want to use the broker-registrar then we need to remove that broker code.
Also, it the broker does not register itself automatically, and now we need to run an errand, it can also affect other projects (like the docker-services-boshworkspace project), as the behavior has changed.
Related, the problem of renaming properties is that we will affect other repos when they switch to a newer release version, so I want to be sure that dependent project are aware of this change,

I'll take care of the 1st item, pinging @drnic, @longnguyen11288 & @geofffranks around 2 & 3. This change won't affect the actual docker-services-boshworkspace project, but if you want to upgrade to a new release, you'll need to modify your project, thoughts?

Hi @frodenas,

I am not sure I understand. I thought the broker doesn't register itself as a broker, but only the route in register_route?

Absolutely, this is incompatible. This PR is more a proposal if you like to reconcile it with the Pivotal broker-registrar. We used it and noticed the difference in behavior and property namespace. It is in no way mandatory for the Swarm changes we built on top. It is just that we had to add properties for Swarm and did that in the property namespace 'broker' (based on Pivotal broker-registrar which we adopted before we started to work on Swarm) rather than 'cfcontainersbroker'.

Let me know whether or not you will consider the Pivotal broker-registrar. If you decide (for compatibility reasons) against it, we can prepare a change in the 'cfcontainerbroker' property namespace for the Swarm content.
Cheers, Vedran

Thanks @vlerenc!
w/r/t 1) you're absolutely right, brain fart; 2) I haven't heard anything regarding incompatibilities.


[editor] goto references

Describe the solution you'd like
When c+click a definition, there shall show a list of references to jump.
With https://github.com/racket-tw/sauron/milestone/2
With the milestone, we have a local state for each file now. Now, each maintainer should broadcast for (list 'using me)-like messages to other maintainers, then the reply will build up to be a complete query result.
Based on this, each maintainer must first tell those maintainers are used by them, then they will ask back these maintainers the positions. There have two results

no using now, please remove me from your user list
still using, these are the positions(to report to the editor for jumping list)

In this method, maintaining the user list would be a problem, should it be a list of files or a list of thread-handle? Using thread-handle would be more efficient and easier to access a thread, but removing might be a problem(check if we have thread-equal?); files will not have this problem, but have to access the shared hashmap for thread-handle. Another problem is should we use list or hashmap to store? A list updating might be a trouble for big module like keyword module from Racket, let's see what would happen.

Blocked by #166

Another way is to let every file hold their reference to file:id as key, and ask every file when querying.

(define (make-record-maintainer file-path semaphore)
  (thread
   (thunk
    (define cached-record (collect-from file-path))
    (define depender (mutable-set))
    (for/async ([path (hash-keys (record-requires cached-record))])
      (thread-send (get-record-maintainer path #:wait? #t)
        (list 'depended (current-thread))))
    (let loop ()
      (match (thread-receive)
        [(list 'depended from)
         ; pseudo-code here
         (set-add! depender from)]
        ...)
      (loop)))))

The next to try

[ ] replace mutable-set with let loop state then an immutable set?
[ ] limit only those maintainers in the project get 'depended message and record them?
[ ] handle 'references message of course


Exported variable in chunk is not defined

Describe the bug
Some interaction between the packages<EMAIL_ADDRESS><EMAIL_ADDRESS>and<EMAIL_ADDRESS>leads to a chunk being generated which exports a variable that is not defined. In the browser's console:
Uncaught ReferenceError: makeStyles_default is not defined
    at Object.makeStyles (index.js:1)
    at Object.get [as makeStyles] (chunk.5ZFU4BUR.js?v=c903acc3:25)
    at main.js:3

This problem only seems to occur in specific circumstances. Depending on what the application imports Vite appears to generate different chunks. In some cases the chunk generated contains the error described above, in other cases it does not. I describe those cases in the reproduction.
Reproduction
https://gist.github.com/183adfb90326072f2f99522d01635497
git clone git@gist.github.com:183adfb90326072f2f99522d01635497.git vite-bug-1853
cd vite-bug-1853/
npm i && npm run dev

Open the Vite dev server and observe the following error in the browser console:
Uncaught ReferenceError: makeStyles_default is not defined
    at Object.makeStyles (index.js:1)
    at Object.get [as makeStyles] (chunk.5ZFU4BUR.js?v=c903acc3:25)
    at main.js:3

Now, stop the dev server. Edit main.js like so:
- import Delete from "@material-ui/icons/Delete"
+ import { Delete } from "@material-ui/icons"

then run rm -r node_modules/.vite && npm run dev and open the server again. You should not observe any error and instead see "Hello, world" on the page.
I investigated the behaviour and it would appear that Vite builds chunks with a radically different content for @material-ui/core in the two scenarios I just outlined. I am not sure what triggers this change in behaviour (evidently something to do with the deep import of the icon). In any case, the chunk generated in one of the scenarios is broken. I don't know if this is due to a problem in Material UI itself or a problem with Vite; I haven't gotten deep enough in my investigation to judge.
You can get this from the reproduction but you can clearly see in this Gist what's going on: https://gist.github.com/hmaurer/c0e17b79532dc0cc584831b2f5d641e3. The @material-ui_core.good.js file contains both an import for makeStyles_default and an export makeStyles_default  as makeStyles, whereas the @material-ui_core.buggy.js file contains an export makeStyles: () => makeStyles_default but no import or definition for makeStyles_default!
System Info

vite version: 2.0.0-beta.62
Operating System: MacOS Catalina
Node version: v14.9.0
Package manager (npm/yarn/pnpm) and version: NPM v6.14.8

PS: I am not exactly sure why but I couldn't get a reproduction without also importing the package @material-ui/pickers.

import Delete from "@material-ui/icons/Delete"

This import is importing a CJS file which transitively require()s an ESM file in @material-ui/core, which causes the entire @material-ui entry to bail out to CJS...
If you have control over this, use @material-ui/icons/esm/Delete instead.

This looks like a legit bug in esbuild.

Thanks for looking into this @yyx990803 ! Should I report it upstream, or do you think your mention of this issue in evanw/esbuild#706 is enough?

I have just ran into the same issue trying to migrate the main UI of our product from CRA to Vite, as a proof of concept to see if we can migrate without too much hassle 🚀.
It seems Material-UI is the main culprit (and I wouldn't be surprised), although I am not 100% sure.
@yyx990803 Comment did the trick for the icons.

import Delete from "@material-ui/icons/Delete"

This import is importing a CJS file which transitively require()s an ESM file in @material-ui/core, which causes the entire @material-ui entry to bail out to CJS...
If you have control over this, use @material-ui/icons/esm/Delete instead.

However I'm encountering another (similar) issue :

This happens with other Material components as well. I'm not sure if this is directly related to the issue described in the previous messages. I'm guessing that one of the dependencies is doing something "wrong" with the module types and it causes issues ?
@hmaurer did you encounter the same issue with the components not being defined ?
Is there any workaround I could try ?
Here's the deps scan below :
  vite:deps Scan completed in 423ms: {
  react: '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/react/index.js',
  'react-dom': '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/react-dom/index.js',
  '@apollo/react-common': <EMAIL_ADDRESS>  notistack: '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/notistack/dist/notistack.esm.js',
  '@material-ui/core': <EMAIL_ADDRESS>  'react-router': '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/react-router/esm/react-router.js',
  '@material-ui/pickers': <EMAIL_ADDRESS>  '@date-io/date-fns': <EMAIL_ADDRESS>  'apollo-boost': '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/apollo-boost/lib/bundle.esm.js',
  'query-string': '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/query-string/index.js',
  'react-router-dom': '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/react-router-dom/esm/react-router-dom.js',
  '@material-ui/core/styles': <EMAIL_ADDRESS>  jss: '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/jss/dist/jss.esm.js',
  formik: '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/formik/dist/formik.esm.js',
  history: '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/history/esm/history.js',
  clsx: '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/clsx/dist/clsx.m.js',
  'graphql-tag': '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/graphql-tag/src/index.js',
  '@material-ui/lab/Skeleton': <EMAIL_ADDRESS>  '@material-ui/icons/esm/DoneAll': <EMAIL_ADDRESS>  '@apollo/react-hooks': <EMAIL_ADDRESS>  '@material-ui/icons/esm/Menu': <EMAIL_ADDRESS>  '@material-ui/icons/esm/Delete': <EMAIL_ADDRESS>  '@material-ui/icons/esm/NavigateNext': <EMAIL_ADDRESS>  '@material-ui/icons/esm/Settings': <EMAIL_ADDRESS>  lodash: '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/lodash/lodash.js',
  '@material-ui/icons/esm/FileCopyRounded': <EMAIL_ADDRESS>  '@material-ui/icons/esm/InfoOutlined': <EMAIL_ADDRESS>  'formik-material-ui': '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/formik-material-ui/dist/formik-material-ui.es6.js',
  '@material-ui/icons/esm/WarningRounded': <EMAIL_ADDRESS>  '@material-ui/icons/esm/EditRounded': <EMAIL_ADDRESS>  '@material-ui/core/Tooltip': <EMAIL_ADDRESS>  '@material-ui/icons/esm/Search': <EMAIL_ADDRESS>  '@material-ui/icons/esm/ToggleOff': <EMAIL_ADDRESS>  '@material-ui/icons/esm/ToggleOn': <EMAIL_ADDRESS>  yup: '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/yup/es/index.js',
  uuid: '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/uuid/dist/esm-browser/index.js',
  '@nivo/line': <EMAIL_ADDRESS>  'date-fns': '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/date-fns/esm/index.js',
  '@material-ui/icons/esm/CheckCircleRounded': <EMAIL_ADDRESS>  '@material-ui/icons/esm/DesktopMac': <EMAIL_ADDRESS>  '@material-ui/icons/esm/CancelOutlined': <EMAIL_ADDRESS>  '@material-ui/core/styles/makeStyles': <EMAIL_ADDRESS>  '@material-ui/icons/esm/ArrowDropDownRounded': <EMAIL_ADDRESS>  '@material-ui/icons/esm/Close': <EMAIL_ADDRESS>  '@material-ui/icons/esm/ArrowRightRounded': <EMAIL_ADDRESS>  '@nivo/pie': <EMAIL_ADDRESS>  '@material-ui/icons/esm/FilterList': <EMAIL_ADDRESS>  '@material-ui/icons/esm/BarChart': <EMAIL_ADDRESS>  '@deepcrawl/lucene-regex-validator': <EMAIL_ADDRESS>  '@material-ui/icons/esm/Help': <EMAIL_ADDRESS>  pluralize: '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/pluralize/pluralize.js',
  '@material-ui/lab/Alert': <EMAIL_ADDRESS>  '@nivo/bar': <EMAIL_ADDRESS>  '@material-ui/icons/esm/FolderRounded': <EMAIL_ADDRESS>  '@material-ui/icons/esm/Person': <EMAIL_ADDRESS>  '@material-ui/icons/esm/FolderOpenRounded': <EMAIL_ADDRESS>  '@material-ui/icons/esm/FormatIndentIncrease': <EMAIL_ADDRESS>  '@material-ui/icons/esm/Build': <EMAIL_ADDRESS>  'material-ui-popup-state/hooks': '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/material-ui-popup-state/hooks.js',
  '@material-ui/icons/esm/Link': <EMAIL_ADDRESS>  'json-to-graphql-query': '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/json-to-graphql-query/lib/index.js',
  '@material-ui/icons/esm/Traffic': <EMAIL_ADDRESS>  '@material-ui/icons/esm/StayCurrentPortrait': <EMAIL_ADDRESS>  '@material-ui/icons/esm/Description': <EMAIL_ADDRESS>  '@material-ui/icons/esm/Speed': <EMAIL_ADDRESS>  '@material-ui/icons/esm/CompareArrows': <EMAIL_ADDRESS>  '@material-ui/icons/esm/Code': <EMAIL_ADDRESS>  '@material-ui/icons/esm/LibraryBooks': <EMAIL_ADDRESS>  'formik-material-ui-lab': '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/formik-material-ui-lab/dist/formik-material-ui.es6.js',
  'material-ui-popup-state/HoverPopover': '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/material-ui-popup-state/HoverPopover.js',
  'react-fast-compare': '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/react-fast-compare/index.js',
  'lodash/debounce': '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/lodash/debounce.js',
  '@material-ui/icons/esm/Clear': <EMAIL_ADDRESS>  '@material-ui/icons/esm/GetApp': <EMAIL_ADDRESS>  '@material-ui/icons/esm/OpenInNew': <EMAIL_ADDRESS>  'formik-material-ui-pickers': '/home/hebilicious/deepcrawl/core-ui/test-react-ts/node_modules/formik-material-ui-pickers/dist/formik-material-ui-pickers.es6.js',
  '@material-ui/icons/esm/TrendingUp': <EMAIL_ADDRESS>  '@material-ui/icons/esm/ViewList': <EMAIL_ADDRESS>  '@material-ui/icons/esm/AccountTree': <EMAIL_ADDRESS>  '@material-ui/icons/esm/Public': <EMAIL_ADDRESS>}

@Hebilicious I have similar issue, and in my code import CircularProgress from "@material-ui/core/CircularProgress"; works fine.
If anyone is investigating this, here's the situation I have observed:
import { createMuiTheme, ThemeProvider } from "@material-ui/core/styles";
import {
  createStyles,
  makeStyles,
  Theme,
  Grid,
  Button,
  TextField,
  InputAdornment,
  IconButton,
  Tooltip,
  Switch,
  FormControlLabel,
} from "@material-ui/core";

would cause Error:
client:188 ReferenceError: createStyles is not defined
    at Object.createStyles (index.js:1)
    at Object.get [as createStyles] (chunk.UQCKUTMR.js?v=a895762e:12)
    at App.tsx:19

while after I moved createStyles and makeStyles 's import from "@material-ui/core" to "@material-ui/core/styles", it works fine.

any others solutions ?

The following vite.config.js excerpt could work as a workaround:
export default defineConfig({
  // …
  resolve: {
    alias: {
      lodash: 'lodash-es',
      '@material-ui/core': './node_modules/@material-ui/core/esm',
      '@material-ui/icons': './node_modules/@material-ui/icons/esm',
      '@material-ui/styles': './node_modules/@material-ui/styles/esm',
      'hoist-non-react-statics':  './node_modules/hoist-non-react-statics/src/index.js',
    },
  },
  // …
})

Following config works for me:
import { defineConfig } from "vite";
import reactRefresh from "@vitejs/plugin-react-refresh";

export default defineConfig({
  plugins: [reactRefresh()],
  resolve: {
    alias: [
      {
        find: /^@material-ui\/icons\/(.*)/,
        replacement: "@material-ui/icons/esm/$1",
      },
      {
        find: /^@material-ui\/core\/(.+)/,
        replacement: "@material-ui/core/es/$1",
      },
      {
        find: /^@material-ui\/core$/,
        replacement: "@material-ui/core/es",
      },
    ],
  },
  define: {
    global: "window",
    "process.env.NODE_ENV": `"development"`,
    "process.env.APP_ENV": `"development"`,
  },
});

I'm facing a similar issue, import { Delete } from "@material-ui/icons"; works fine for me but my app breaks upon adding import { makeStyles } from "@material-ui/core/styles";
This is the error i get in console: Uncaught SyntaxError: The requested module<EMAIL_ADDRESS>does not provide an export named 'default'

Following config works for me:
import { defineConfig } from "vite";
import reactRefresh from "@vitejs/plugin-react-refresh";

export default defineConfig({
  plugins: [reactRefresh()],
  resolve: {
    alias: [
      {
        find: /^@material-ui\/icons\/(.*)/,
        replacement: "@material-ui/icons/esm/$1",
      },
      {
        find: /^@material-ui\/core\/(.+)/,
        replacement: "@material-ui/core/es/$1",
      },
      {
        find: /^@material-ui\/core$/,
        replacement: "@material-ui/core/es",
      },
    ],
  },
  define: {
    global: "window", // fix for packages that support both node and browser
  },
});

This worker for me. 🎉

For me at least, I didn't need any alias changes or messing with optimizeDeps

This looks like a legit bug in esbuild - probably related to evanw/esbuild#706, but this one actually generates a reference to an undefined variable.

It seems like it's fixed in esbuild v0.11+

I'm having same problem. None of the solutions above worked for me. The code works perfectly fine when I run yarn build, but I'm having various problems related to material UI.
I get the following error: Uncaught ReferenceError: Grid_default is not defined When I import it like that:
import { Grid } from "@material-ui/core";
import { makeStyles } from "@material-ui/core/styles";

The problem is solved by importing it as import Grid from @material-ui/core/Grid, but then, the makeStyles starts to give the same error.
Man material UI is seriously awful with anything esbuild 😄 I was having a lot of trouble when I tried to migrate our application to skypack as well, all related to material UI.

I was able to make it work by doing a pristine install like this:
rm -rf node_modules && rm package-lock.json && npm cache clear --force && npm i
Then is simply started working
My vite.config.js file:
import { defineConfig } from 'vite'
import reactRefresh from '@vitejs/plugin-react-refresh'

export default defineConfig({
  plugins: [reactRefresh()],
  build: {
    minify: process.env.ENV === 'development' ? false : 'terser',
    outDir: 'dist', // this is the defautl value
    sourcemap: false // this is the defautl vallue
  }
})

My tsconfig.json file:
{
  "compilerOptions": {
    "target": "esnext",
    "lib": ["dom", "dom.iterable", "esnext"],
    "allowJs": true,
    "skipLibCheck": true,
    "strict": false,
    "forceConsistentCasingInFileNames": true,
    "esModuleInterop": true,
    "module": "commonjs",
    "allowUnreachableCode": false,
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "jsx": "react",
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "outDir": "build",
    "sourceMap": true
  },
  "include": ["./src/**/*.ts"]
}

My packages:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
Hi, I had this problem too from importing an icon:
//This statement makes npm run dev implode
import Sort from "@material-ui/icons/Sort"
//This statement makes npm run build implode (EMFILE error)
import {Sort} from "@material-ui/icons"

For now I solved both problems by importing the icon with the first import statement ("@material-ui/icons/Sort") and by adding only this alias to vite.config:
import { defineConfig } from 'vite'
import reactRefresh from '@vitejs/plugin-react-refresh'

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [reactRefresh()],
  base:"/aniCheck/",
  resolve: {
    alias: [
        {
            find: /^@material-ui\/icons\/(.*)/,
            replacement: '@material-ui/icons/esm/$1',
        },
    ],
},
})

Would someone be interested in added an official Material-UI + Vite example in the MUI repo? https://github.com/mui-org/material-ui/issues/21377

Confirmed that updating esbuild fixes this. In addition to vite 2.2.3 I added esbuild 0.11.17 and then (using yarn) added
"resolutions": {
    "esbuild": "0.11.17"
  }

which forces vite to use the newer package.


[Bug] NavigationService -Footer navigation doesn't work

It is not possible to navigate to a FooterNavigationViewItem.
The problem is that JsonNavigationViewService only returns the MenuItems,
the FooterMenuItems are not returned.
IList<object>? MenuItems => _navigationView?.MenuItems;
This means that only the MenuItems are configured in ConfigPages.
    private void ConfigPages()
    {
        _pageService.GetPages(MenuItems);

It would be conceivable to also integrate the FooterItems into ConfigPages.
Either the IList<object>? MenuItems also contains the FooterItems,
or an additional IList<object>? FooterMenuItems which is then processed by the ConfigPages.

Thanks @RolandBuchholz
Fixed


factory and options decorators are missing from declarations file

I'm submitting a bug report

Library Version:
1.0.0

Please tell us about your environment:

Operating System:
Windows 10

Node Version:
4.2.2

NPM Version:
3.5.1

JSPM OR Webpack AND Version
N/A

Browser:
N/A

Language:
TypeScript 2.0 (though applies to 1.8?)

Current behavior:
Expected/desired behavior:

What is the expected behavior?
factory and options decorators are missing from aurelia-dependency-injection.d.ts

What is the motivation / use case for changing the behavior?
factory and options decorators should not be missing as they exist in the source.

factory
optional

We're currently having a bugfix release held up on this, would really appreciate it being fixed ASAP.

This seems to be fixed.

@EisenbergEffect They still appear to be missing from the d.ts file.
https://github.com/aurelia/dependency-injection/blob/ae2fdcc578ff6fc35dc2a22b02f6f4a1f5c937d8/dist/aurelia-dependency-injection.d.ts#L254-L268

I am confused. Aren't you highlighting them in the d.ts file right there?

factory and optional are missing, the others are there.

Sorry, I was in the wrong part of the file.
optional now correctly exists, factory is still missing.
It's declared @ https://github.com/aurelia/dependency-injection/blob/ae2fdcc578ff6fc35dc2a22b02f6f4a1f5c937d8/src/invokers.js#L13-L22

optional is present in the latest release. For some reason factory is not. I'm not sure how that would happen. That's very odd.

In see the problem. This is an issue where a duplicate name crept in somehow. I'll need to think about how we are going to solve this and if we can do it without making a breaking change.

@SPARTAN563 Can you describe the details of your situation? I need to know in order to guide me on how to fix the issue. The problem is that we've got two different decorators called factory. I need to pick the right one for backwards compat.

At the moment we don't have this deployed to production, so go ahead and do whatever you need to do.
The use case is that we have a couple of classes which need to be instantiated multiple times with context specific values as well as DI services.
The following is an example of how this is done (rather than the actual code being held up by this). If you are interested in discussing better ways of accomplishing this (as opposed to the @skipParams decorator, I'd be very interested in doing so, as it is a relatively common issue from what I've heard when discussing Aurelia's DI framework in more complex scenarios.
interface PersonFactory {
  new (id: number): Person;
}

@autoinject
@skipParams(1) //Custom decorator which skips the last N constructor params for DI
class Person {
  constructor(protected personAPI: PersonAPI, public id: number) {

  }
}

class PeopleProvider {
  constructor(
    private @factory(Person) personFactory: PersonFactory,
    private personAPI: PersonAPI
  ) {

  }

  getPeople(): Promise<Person[]> {
    return this.personAPI.list()
      .then(people => people.map(p => new this.personFactory(p.id))
  }
}

Ok. We will get this fixed and released this week.


Refactor engine

Refactoring for PTZ Camera Integration
I propose a refactor of the code to prepare for the use of PTZ cameras, which is divided into two features:
Feature 1: New ReolinkCamera
This new ReolinkCamera class allows control of both PTZ cameras and the current static cameras.
Feature 2: Parallel Processing
In the previous version of the engine, a 30-second loop would allocate 30 seconds / (number of cameras) per camera to perform three tasks:

Image capture
Prediction calculation
Processing the prediction and sending images in case of alerts

The problem was that in some cases, the image sending failed due to a lack of time. Additionally, this method does not scale well with a larger number of cameras, which will be the case with PTZ cameras that have a smaller field of view.
I propose to launch three parallel processes to manage these steps independently, optimizing the calculations as much as possible.
The code has been tested and works without any issues.

I will create a new PR


Is there a shortcut to playing a video once the player has been instantiated?

Is there a way to just replace the video identifier without having to reinitialize the YouTube player? Each time I play a video I'm using this code (below) but I feel like there is some way to make it faster. Thanks
Code:
XCDYOUTUBEPLAYERCONTROLLER = [[XCDYouTubeVideoPlayerViewController alloc] initWithVideoIdentifier:VIDEOID];
[XCDYOUTUBEPLAYERCONTROLLER presentInView:self.playerController.youtubeplayerView];
[XCDYOUTUBEPLAYERCONTROLLER.moviePlayer play];

try this code may be help you
XCDYOUTUBEPLAYERCONTROLLER.videoIdentifier = your videoIdentifier

As @anilappvolution said, you can simply set a new videoIdentifier. Instead of relying on KVO, you can add on observer on XCDYouTubeVideoPlayerViewControllerDidReceiveVideoNotification and call play in the notification callback.


Update AiffFileWriter.cs

dataChunkSize needs to be defined bigger than int, else the multiplication in function UpdateCommChunk will return negative value if the product of the multiplication exceeds Int.MaxValue

sorry for the delay, and thanks for your contribution


Crc start using ubuntu 18.04

Hello,
I am using this documentaion,
first,I installed crc
crc setup

command  run successfully
Then
crc start

I got this error  here
crc status
yehia@yehia-Laptop:~$ crc status
CRC VM:          Running
OpenShift:       Running (v4.5.7)
Disk Usage:      10.89GB of 32.72GB (Inside the CRC VM)
Cache Usage:     12.64GB
Cache Directory: /home/yehia/.crc/cache

crc console
crc console
Opening the OpenShift Web Console in the default browser...
[0907/155954.647256:ERROR:nacl_helper_linux.cc(308)] NaCl helper process running without a sandbox!
Most likely you need to configure your SUID sandbox correctly

I just started using Openshift. I am trying openshift locally.
Thanks in Advance.

@yehia67 Please check #549 and try to follow some manual steps listed on the issue, will close this issue as duplicate.

Okay, Thank you.


[improve] Refactor client version format

Motivation
Currently,  the client_version  only shows the version information. And clients in different languages use their own separate version numbers. This can lead to conflict. For example, the java client 2.10.2 uses the same value 2.10.2 as the C++ client 2.10.2. And C++ client 3.0.0 may conflict with the future java client 3.0.0. The information of client_version is incomplete. We could not determine what language(or specific library) the client uses. This raises inconvenience for debugging.
This PR adopts a new client version format for the C++ client.
Please see the discussion: https://lists.apache.org/thread/n59k537fhthjnzkfxtc2p4zk4l0cv3mp
Modifications

Change the client version value to Pulsar-C++-vXXX

Verifying this change
This change added tests.
Documentation

[ ] doc-required
(Your PR needs to update docs and you will update later)

[x] doc-not-needed
(Please explain why)

[ ] doc
(Your PR contains doc changes)

[ ] doc-complete
(Docs have been already added)

For Node.js and Python clients, How do we set this parameter?

For Node.js and Python clients, How do we set this parameter?

I made a discussion here: https://lists.apache.org/thread/ldmtjrqvz6bz2flpdl89k9ogybcm9mj1
I think we need to expose the configuration of the clientVersion.


Thoughts around WrapperImpls and providing out own Impls

Intro
Currently you are using a fixed WrapperImpl in Mediator.cs, i.e. one of Notification, Request, StreamRequest.
For example, for IRequest sending:

public class Mediator : IMediator
{
    //....
    public Task<TResponse> Send<TResponse>(IRequest<TResponse> request, CancellationToken cancellationToken = default)
    {
        if (request == null)
        {
            throw new ArgumentNullException(nameof(request));
        }

        var requestType = request.GetType();

        var handler = (RequestHandlerWrapper<TResponse>)_requestHandlers.GetOrAdd(requestType,
            static t => (RequestHandlerBase)(Activator.CreateInstance(typeof(RequestHandlerWrapperImpl<,>).MakeGenericType(t, typeof(TResponse)))
                                             ?? throw new InvalidOperationException($"Could not create wrapper type for {t}")));

        return handler.Handle(request, cancellationToken, _serviceFactory);
    }
    // ....
}

I thought I would open an issue to get thoughts around a possible implementation, or even the idea in general - does it even warrant considering when there are other options.
Motivation
I would like to provide my own WrapperImpl in order to e.g. have a pipeline that uses a single DB transaction throughout.
Implementation
I am not sure of the best way to do this, but was thinking of using a type 'provider', e.g.

public interface IRequestHandlerWrapperTypeProvider
{
    Type ImplementationType { get; }
}

public class DefaultRequestHandlerWrapperTypeProvider : IRequestHandlerWrapperTypeProvider
{
    public Type ImplementationType => typeof(RequestHandlerWrapperImpl<,>);
}

public class TransactionAwareRequestHandlerWrapperTypeProvider : IRequestHandlerWrapperTypeProvider
{
    public Type ImplementationType => typeof(TransactionAwareRequestHandlerWrapperImpl<,>);
}

The issue with this is that there is no guarantee that the implementation type is of type RequestHandlerBase, which is not ideal. But it does mean that we can change up the Mediator to look a little like the below, and then provide our own implementation type. (It does remove your static functions used in GetOrAdd, though, as _serviceFactory is needed, and I assume that's not static in order to handle threading).
public class Mediator : IMediator
{
    //....
    public Task<object?> Send(object request, CancellationToken cancellationToken = default)
    {
        // ....
                var responseType = requestInterfaceType.GetGenericArguments()[0];

                // Here we create out own implementation type by pulling the type provider from the service factory..
                var wrapperType = _serviceFactory.GetInstance<IRequestHandlerWrapperTypeProvider>().ImplementationType;

                return (RequestHandlerBase)(Activator.CreateInstance(wrapperType.MakeGenericType(requestTypeKey, responseType))
                                            ?? throw new InvalidOperationException($"Could not create wrapper for type {wrapperType}"));
            });

        // call via dynamic dispatch to avoid calling through reflection for performance reasons
        return handler.Handle(request, cancellationToken, _serviceFactory);
    }
    // ....
}

The WrapperImpl would look something like this:
namespace MyNameSpace;

public class TransactionAwareRequestHandlerWrapperImpl<TRequest, TResponse> : RequestHandlerWrapper<TResponse>
    where TRequest : IRequest<TResponse>
{
    public override async Task<object?> Handle(object request, CancellationToken cancellationToken,
        ServiceFactory serviceFactory) =>
        await Handle((IRequest<TResponse>) request, cancellationToken, serviceFactory).ConfigureAwait(false);

    public async override Task<TResponse> Handle(IRequest<TResponse> request, CancellationToken cancellationToken,
        ServiceFactory serviceFactory)
    {
        using var context = serviceFactory.GetInstance<IDbContextFactory<Context>>().CreateDbContext();
        using var transaction = await context.Database.BeginTransactionAsync();

        Task<TResponse> Handler() => GetHandler<ITransactionAwareRequestHandler<TRequest, TResponse>>(serviceFactory).Handle((TRequest) request, transaction, cancellationToken);

        var response = await serviceFactory
            .GetInstances<ITransactionAwarePipelineBehavior<TRequest, TResponse>>()
            .Reverse()
            .Aggregate((RequestHandlerDelegate<TResponse>) Handler, (next, pipeline) => () => pipeline.Handle((TRequest) request, transaction, cancellationToken, next))();

        transaction.Commit();

        return response;
    }
}

With my own defined interfaces, ITransactionAwareRequestHandler and ITransactionAwarePipelineBehavior.
There are other options that do not require code changes to Mediatr. For example using some sort of Transaction Provider that could be injected into my own PipelineBehaviours which can provide a specific transaction based on e.g. the current Thread.
Thoughts and discussions welcome!

If I was using asp.net then a scoped context would be ok. I was thinking about ways to manage the scope per pipeline and came across this in the source.
I'm building an offline-first MAUI/Xamarin app, so I have to manage the scope myself.
And in all honesty it's not really a big issue duplicating transaction management code in each handler, or wrapping handlers to do what I need - I just like the pipeline model (and agreed with one of your older posts that it was generally better for DI than composing handlers).

I would still go the scope route and create it yourself. That's what I do in background services.

Yeah I'll have a think about the best way to do that. The limitation is discoverability deeper into the pipeline - I'm not a fan of pulling magic contexts out of the air - we did that in an older asp.net project years ago with owin middleware, and coming back to it later took me a little time to realise what in earth we had done!


Does mail2most support STARTTLS?

I'm getting timeout errors connecting to my mail server, and I'm wondering if the issue is that the server is setup to use STARTTLS as the encryption method rather than the other ssl/tls method.
Please let me know if that might be the case!

I have confirmed that out-of-the-box, mail2most does not support StartTLS.
However, the underlying imap module does support it. I edited the code and got it to connect, by first doing a client.dial() as it would for the non-tls connection, but then calling client.StartTLS() which worked fine. The code works, although I did break the entire test suite in the process.

hi @dgarlans thanks for your issue your are right i added a StartTLS option in the profile configuration just set ImapTLS=false and instead add StartTLS=true if your mailserver has a port you can remove it since 143 is used. Can you test the following binary with the new configuration and confirm if everything works as expected?
windows-amd64.tar.gz
windows-386.tar.gz
linux-arm64.tar.gz
linux-arm.tar.gz
linux-amd64.tar.gz
linux-386.tar.gz

hi @dgarlans thanks for your issue your are right i added a StartTLS option in the profile configuration just set ImapTLS=false and instead add StartTLS=true if your mailserver has a port you can remove it since 143 is used. Can you test the following binary with the new configuration and confirm if everything works as expected?
windows-amd64.tar.gz
windows-386.tar.gz
linux-arm64.tar.gz
linux-arm.tar.gz
linux-amd64.tar.gz
linux-386.tar.gz

Unfortunately I can't seem to run the build, I get "./mail2most: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by ./mail2most)" on my Debian 10 server. I'll try to download and build the new code myself to see if it works.

@dgarlans  any updates on this?

I added support for StartTLS in the v1.11.5 release

@dgarlans feel free to reopen the issue if something does not work as expected and thank you very much for your issue


Add Update Factor Admin endpoint

What kind of change does this PR introduce?
Endpoints

[ ] UPDATE factor so status can be changed

What is the current behavior?
No admin Endpoints
What is the new behavior?
To be filled in
Additional context
Relevant issue #14
Still need an explicit /list factor

Closing since we overhauled the API routes  -- see #586 for update factor admin endpoint