revChatGPT.typings.Error (code 403) using V1 for non GPT-3.5 models

I'm not sure if this is something I am not doing correct with revChatGPT or if it is related to the proxy. When I dont specify a model, the API's ask function works flawless. When I specify any gpt-4 model on my account with chatgpt plus, I get this error message:
revChatGPT.typings.Error: OpenAI: {"detail":"Our systems have detected unusual activity from your system. Please try again later."} (code: 403)
I wonder if setting up my own proxy would solve it?

It might be detecting a conflict in PUID. I'll add some mitigation tomorrow.

I wonder if setting up my own proxy would solve it?

Yes if you use the same plus account

I assume that PUID update worked and everyone is jamming your server now?
revChatGPT is giving a giant html response from cloudflare in terminal.
The connection to the origin web server was made, but the origin web server timed out before responding. The likely cause is an overloaded background task, database or application, stressing the resources on your web server. To resolve, please work with your hosting provider or web development team to free up resources for your database or overloaded application. Additional troubleshooting information here.
I'm going to try a local server to see if that solves and will update. Anyways, thanks for all you are doing for open source!  @archeong08


Something with page.status

reload got weird when a page.status got changed in update(), no idea what is the bug yet, this is not the best bug report in the world, it's just a tribute 🎵

this was  me being an human bug, it worked i was just being dumb


The internal schema printer should ommit built-in scalars.

When representing a GraphQL schema using the type system definition language, all built‐in scalars must be omitted for brevity.

https://spec.graphql.org/draft/#sel-FAHXLFCAACCmCgpC

This one is now fixed.


Doesn't appear to work with Photo Mode Camera

This plugin is pretty awesome but I noticed it does not appear to work with the photo mode camera in TaleSpire.
It would be really amazing to have a separate setting for photomode and the normal camera.  That way one could keep the normal camera closer in, but really open up the photomode to get some amazing screenshots.
Thanks!

Glad you are enjoying the plugin, I'll add that to my backlog and try and get that done when I get some time.
I'll also be adding some run-time configuration support with the configuration manager being WIP so you can eventually adjust the config on the fly with that installed.

Not sure if you updated the plugin or if it was the integration of the 2 different camera systems in TaleSpire, but it now appears that this works in both modes.  I don't feel the extra setting of having a further viewing distance in Photo mode is that important so I'm just going to mark this closed.


Fix position on home page

no issue for this one only kick fixing of home page

Not sure if it works, please rebase this pr on main before i can review


Show Top X of subregion map in cases per 100k

Problem
If the user wants to compare which counties have the most cases of COVID in their state, the current workflow is to hover over each county and take a note/screenshot of the hover text.There is no way to display multiple at once or intuitively see which states are best/worst (especially if color shade is the same).
For example,  in the following image, it is difficult to pinpoint the worst counties without hovering over all the green ones.

Request
Add a toggle on the map to “Show Top X of [Counties/States] with the highest incidences of Cases per 100k. Clicking the toggle will only highlight the top X.
Additional comments / risks
Consider Wording - Top vs Best vs Bottom  …. Top is actually the worst geography? Can we include toggle for best and worst?
Top X - originally discussed as Top 5. Good? Or Top 10? Or both with a toggle? (too many toggles)?
Risking information overload

The main work is done here, leaving it open in backlog to discuss how we want the highlighting to work post-launch

Actually this seems like a dupe of #826, going to close this one and move the other one to the backlog (as the other issue has more details)


lib/modules: Change mkAliasOptionModule to use the priority for the alias

This commit changes the mkAliasOptionModule function to make sure that the priority for the aliased option is propagated to the non-aliased option.
This also affects the mkRenamedOptionModule function in a similar fashion.
This also removes the mkAliasOptionModuleWithPriority function, since its functionality is now subsumed by mkAliasOptionModule.
This change was recommended by @nbp to see what would be the effect of doing this:
https://github.com/NixOS/nixpkgs/pull/53397#discussion_r245487432
Motivation for this change
The motivation for this change (as well as a use-case) is listed in https://github.com/NixOS/nixpkgs/pull/53397#issue-242220506.
Pinging @nbp, since he suggested this change.  Also pinging @Infinisil since he helped with the original PR that inspired this change.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[X] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Assured whether relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

@nbp Would you be able to take a look at this?  It might be nice to get this in for 19.03.

I just discovered this stuff in the lib, noticed it was introduced in #53397, but I don't understand the use case for withPriority = false.
Having read the aforementioned thread I still don't understand what is going on here, wasn't it just a bug that mkAliasOptionModule didn't copy the priority? Shouldn't mkRenamed* do the same too?
I.e. why that second function was introduced in the first place?
Shouldn't this PR just remove all withPriority stuff and always propagate the priority?

@oxij Thanks for doing a review of this.  You bring up some good questions.  Let me try to answer them.

Having read the aforementioned thread I still don't understand what is going on here, wasn't it just a bug that mkAliasOptionModule didn't copy the priority?

Originally, the documentation for the functions in question mentioned that they don't copy the priority.  I assumed it wasn't a bug, but intentional.  In the few previous PRs I sent surrounding this issue, no one seemed to think it was a bug.
This PR changes mkAliasOptionModule (and mkRenamedOptionModule) to copy over the priority.
My assumption is that this isn't really "fixing a bug", but adding an additional feature to these functions.
I think that most people who use mkAliasOptionModule (and mkRenamedOptionModule) will want this new functionality.

Shouldn't mkRenamed* do the same too?

Yes, this PR changes mkRenamedOptionModule to also copy over the priority.

Why was that second function (mkAliasOptionModuleWithPriority) introduced in the first place?

mkAliasOptionModuleWithPriority was introduced to do the same thing as mkAliasOptionModule, but also additionally copy over the priority.
It makes sense to have mkAliasOptionModuleWithPriority if you think that mkAliasOptionModule shouldn't copy over the priority.  Since this PR changes mkAliasOptionModule to copy over the priority, then mkAliasOptionModuleWithPriority is no longer needed.

Shouldn't this PR just remove all withPriority stuff and always propagate the priority?

Yeah, that is one option.  I'd be fine with that (since it would make the code slightly simpler), but I'm not sure why mkAliasOptionModule originally did not copy over the priority.  If this was just an oversight, then I imagine it wouldn't have been added to the documentation.  If it was intentional, then I didn't want to completely change it if someone was relying on that functionality.
This PR does change that functionality, but at least it provides a backdoor for someone to use who is depending on that functionality (by leaving the option available in doRename).

I see. I guess it would be nice to hear what @nbp thinks about this then. I see no explanation for not propagating the priority in the first place.

I think this is fine, this change makes sense, and I also even doubt anybody relied on the previous behavior


Permission denied (publickey) on mysocketctl connect

When i try to connect a socket, i get a publickey error. I think its related to ssh login process.
mboscovich@tesla03:~ $ mysocketctl login --email<EMAIL_ADDRESS>--password "XXXXXXXXXXXXX"
Logged in! Token stored in /home/mboscovich/.mysocketio_token

mboscovich@tesla03:~ $ mysocketctl connect --port 8080 --name "prueba"
+--------------------------------------+--------------------------------------+---------+------+--------+
|              socket_id               |               dns_name               | port(s) | type |  name  |
+--------------------------------------+--------------------------------------+---------+------+--------+
| a79e3ce9-27f0-4abc-97bd-9991bbb3e5a7 | delicate-brook-3736.edge.mysocket.io |  80 443 | http | prueba |
+--------------------------------------+--------------------------------------+---------+------+--------+

Connecting to Server: ssh.mysocket.io

<EMAIL_ADDRESS>Permission denied (publickey).
Disconnected... Automatically reconnecting now..
Press ctrl-c to exit
<EMAIL_ADDRESS>Permission denied (publickey).
Disconnected... Automatically reconnecting now..
Press ctrl-c to exit
<EMAIL_ADDRESS>Permission denied (publickey).
Disconnected... Automatically reconnecting now..
Press ctrl-c to exit
<EMAIL_ADDRESS>Permission denied (publickey).
Disconnected... Automatically reconnecting now..
Press ctrl-c to exit

I think the problem could be, that pub key isn't on the remote host. This is the ssh output
mboscovich@tesla03:~ $ ssh<EMAIL_ADDRESS>-i ~/.ssh/id_rsa  -v
OpenSSH_8.2p1 Ubuntu-4ubuntu0.1, OpenSSL 1.1.1f  31 Mar 2020
debug1: Reading configuration data /home/mboscovich/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug1: Connecting to ssh.mysocket.io [<IP_ADDRESS>] port 22.
debug1: Connection established.
debug1: identity file /home/mboscovich/.ssh/id_rsa type 0
debug1: identity file /home/mboscovich/.ssh/id_rsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.1
debug1: Remote protocol version 2.0, remote software version OpenSSH_8.2p1 Ubuntu-4ubuntu0.1
debug1: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.1 pat OpenSSH* compat 0x04000000
debug1: Authenticating to ssh.mysocket.io:22 as 'c43803bf25064017a3948ebc06fd3f65'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher<EMAIL_ADDRESS>MAC: <implicit> compression: none
debug1: kex: client->server cipher<EMAIL_ADDRESS>MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:35ZtwZ4HRme2W3Mktt/ZQEM8NlgvPOG3Q6w26NrxHA4
debug1: Host 'ssh.mysocket.io' is known and matches the ECDSA host key.
debug1: Found key in /home/mboscovich/.ssh/known_hosts:264
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 134217728 blocks
debug1: Will attempt key: /home/mboscovich/.ssh/id_rsa RSA SHA256:2biByZSAZxvtsZDbxPwTIMqlXJmTPdM1h+BtQloHX2g explicit agent
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,sk-ssh-ed25519<EMAIL_ADDRESS>debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /home/mboscovich/.ssh/id_rsa RSA SHA256:2biByZSAZxvtsZDbxPwTIMqlXJmTPdM1h+BtQloHX2g explicit agent
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
<EMAIL_ADDRESS>Permission denied (publickey).

hi Maximiliano,
sorry about that. there was a temporary hick-up with distributing the config in the last 3 hours.
this has now been resolved. Can you try it again?
thanks
Andree

Hi Andree,
Yes!, thats right, the problem is fixed!.
Thank you for the instant reply and fix.
Great service!

Hey, @atoonk, seems like this issue is back. I was running into it, without changes on my so far working config?

Hey, @atoonk, seems like this issue is back. I was running into it, without changes on my so far working config?

Hi @gklasen
i will need some more info, like what socket_id. Do you see the problem right now?
i just tested myself to the EU and US-west server and it seems to work ok now.
did you use the regular client? if so what version?

Hi @gklasen
i will need some more info, like what socket_id. Do you see the problem right now?
i just tested myself to the EU and US-west server and it seems to work ok now.
did you use the regular client? if so what version?

Version: mysocketctl 0.14
Socket_ID: Cannot be measured, system is cleaning up after i abort the command.
Error is:
Logged in! Token stored in /root/.mysocketio_token

Traceback (most recent call last):
  File "/usr/local/bin/mysocketctl", line 8, in <module>
    sys.exit(cli())
  File "/usr/local/lib/python3.7/dist-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.7/dist-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.7/dist-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.7/dist-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.7/dist-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.7/dist-packages/click/decorators.py", line 21, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/usr/local/lib/python3.7/dist-packages/mysocketctl/connect.py", line 100, in connect
    print_sockets([new_conn])
  File "/usr/local/lib/python3.7/dist-packages/mysocketctl/utils.py", line 153, in print_sockets
    socket["cloud_authentication"],
KeyError: 'cloud_authentication'

Version: mysocketctl 0.14
Socket_ID: Cannot be measured, system is cleaning up after i abort the command.
Error is:
Logged in! Token stored in /root/.mysocketio_token

Traceback (most recent call last):
  File "/usr/local/bin/mysocketctl", line 8, in <module>
    sys.exit(cli())
  File "/usr/local/lib/python3.7/dist-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.7/dist-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.7/dist-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.7/dist-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.7/dist-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.7/dist-packages/click/decorators.py", line 21, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/usr/local/lib/python3.7/dist-packages/mysocketctl/connect.py", line 100, in connect
    print_sockets([new_conn])
  File "/usr/local/lib/python3.7/dist-packages/mysocketctl/utils.py", line 153, in print_sockets
    socket["cloud_authentication"],
KeyError: 'cloud_authentication'

hi @gklasen
this was a bug in v0.13 I believe. v0.14 should have solved this. Are you sure you're running v0.14?
line 153 of utils.py in v0.14 is  socket["cloud_authentication_enabled"],
https://github.com/mysocketio/mysocketctl/blob/main/mysocketctl/utils.py#L153
can you make sure you run v.014
check version:
pip3 freeze | grep mysocketctl
mysocketctl==0.14

check line 153 of utils.py
sed -n 153p /usr/local/lib/python3.7/dist-packages/mysocketctl/utils.py
            socket["cloud_authentication_enabled"],

hi @gklasen
this was a bug in v0.13 I believe. v0.14 should have solved this. Are you sure you're running v0.14?
line 153 of utils.py in v0.14 is  socket["cloud_authentication_enabled"],
https://github.com/mysocketio/mysocketctl/blob/main/mysocketctl/utils.py#L153
can you make sure you run v.014
check version:
pip3 freeze | grep mysocketctl
mysocketctl==0.14

check line 153 of utils.py
sed -n 153p /usr/local/lib/python3.7/dist-packages/mysocketctl/utils.py
            socket["cloud_authentication_enabled"],

I get the output as expected.  Sorry, i was testing different versions and left with 10.13. Back to 10.14, i got the output expected, but still the error from @mboscovich.
But: Since ~10 minutes, it is working again like it should. So issue for now is solved, but not with the hick-ups in general, it seems.

I get the output as expected.  Sorry, i was testing different versions and left with 10.13. Back to 10.14, i got the output expected, but still the error from @mboscovich.
But: Since ~10 minutes, it is working again like it should. So issue for now is solved, but not with the hick-ups in general, it seems.

That's good to @gklasen
I'm committed to getting to the bottom of what you're seeing. in order to do so, I need to reproduce it. can you tell me exactly what you're doing? Something I can easily reproduce / try myself?

That's good to @gklasen
I'm committed to getting to the bottom of what you're seeing. in order to do so, I need to reproduce it. can you tell me exactly what you're doing? Something I can easily reproduce / try myself?

Actually, all i am doing was creating an account
mysocketctl connect --port 8443 --name "COMPRISE Personal Server" --type https,
logging in
mysocketctl login --email<EMAIL_ADDRESS>--password *********
and running:
mysocketctl connect --port 8443 --name "COMPRISE Personal Server" --type https
So kind of reproducable for every kind of account. I was not changing anything, just deleted old sockets here and there, and connected again.

Actually, all i am doing was creating an account
mysocketctl connect --port 8443 --name "COMPRISE Personal Server" --type https,
logging in
mysocketctl login --email<EMAIL_ADDRESS>--password *********
and running:
mysocketctl connect --port 8443 --name "COMPRISE Personal Server" --type https
So kind of reproducable for every kind of account. I was not changing anything, just deleted old sockets here and there, and connected again.

what is the exact error you get when you do this?
this, or something else?
<EMAIL_ADDRESS>Permission denied (publickey).
Disconnected... Automatically reconnecting now..

what is the exact error you get when you do this?
this, or something else?
<EMAIL_ADDRESS>Permission denied (publickey).
Disconnected... Automatically reconnecting now..

Got the error you pasted, except that ...

Disconnected... Automatically reconnecting now..

... was missing. Only got

<EMAIL_ADDRESS>Permission denied (publickey).

Got the error you pasted, except that ...

Disconnected... Automatically reconnecting now..

... was missing. Only got

<EMAIL_ADDRESS>Permission denied (publickey).

hhm. I will need some more details..

can you paste the complete output of a failed attempt.

are you using docker? if so what base docker container? (I may be able to use that to reproduce)

does the system have ssh installed? (what is the output of which ssh (if not it will fall back to paramiko. )

if not, can you install the ssh client and see if it makes a difference

in addition to step1, can you do the same with debug enabled, like
MYSOCKET_DEBUG=TRUE mysocketctl connect --port 8443 --name "COMPRISE Personal Server" --type https

are you sure the machine has access to the private key? what is the location of the private key? can you show the output of ls -la <your private key> (I'm interested in the key type / name)

hhm. I will need some more details..

can you paste the complete output of a failed attempt.

are you using docker? if so what base docker container? (I may be able to use that to reproduce)

does the system have ssh installed? (what is the output of which ssh (if not it will fall back to paramiko. )

if not, can you install the ssh client and see if it makes a difference

in addition to step1, can you do the same with debug enabled, like
MYSOCKET_DEBUG=TRUE mysocketctl connect --port 8443 --name "COMPRISE Personal Server" --type https

are you sure the machine has access to the private key? what is the location of the private key? can you show the output of ls -la <your private key> (I'm interested in the key type / name)

@gklasen I'm happy to jump on a call if that works better for you. we can try and troubleshoot it together. just let me know. you can email me at andree at mysocket

@gklasen I'm happy to jump on a call if that works better for you. we can try and troubleshoot it together. just let me know. you can email me at andree at mysocket

any changes @gklasen ? let me know if we need to keep digging or can close this

any changes @gklasen ? let me know if we need to keep digging or can close this

Hey, sorry.
It is working again, so it seems like it was a temporary issue. Feel free to close.

Hey, sorry.
It is working again, so it seems like it was a temporary issue. Feel free to close.


deepspeed was missing, then torch.distributed.elastic.multiprocessing.errors.ChildFailedError

Followed the manual installation process on Ubuntu Linux 4090 24G.
On the first run I got the error message that the deepspeed package was missing -> installed it.
Next tries I got the following error messages...
[2024-09-15 20:18:01] [INFO] enable fp8 training for Text Encoder.
[2024-09-15 20:18:04] [INFO] 2024-09-15 20:18:04 INFO     prepare CLIP-L for fp8: set to torch.float8_e4m3fn, set embeddings to torch.bfloat16       flux_train_network.py:464
[2024-09-15 20:18:04] [INFO] [rank0]: Traceback (most recent call last):
[2024-09-15 20:18:04] [INFO] [rank0]:   File "/srv/www/vhosts/fluxgym/sd-scripts/flux_train_network.py", line 519, in <module>
[2024-09-15 20:18:04] [INFO] [rank0]:     trainer.train(args)
[2024-09-15 20:18:04] [INFO] [rank0]:   File "/srv/www/vhosts/fluxgym/sd-scripts/train_network.py", line 596, in train
[2024-09-15 20:18:04] [INFO] [rank0]:     unet = accelerator.prepare(unet)
[2024-09-15 20:18:04] [INFO] [rank0]:   File "/srv/www/vhosts/fluxgym/venv/lib/python3.10/site-packages/accelerate/accelerator.py", line 1303, in prepare
[2024-09-15 20:18:04] [INFO] [rank0]:     result = self._prepare_deepspeed(*args)
[2024-09-15 20:18:04] [INFO] [rank0]:   File "/srv/www/vhosts/fluxgym/venv/lib/python3.10/site-packages/accelerate/accelerator.py", line 1621, in _prepare_deepspeed
[2024-09-15 20:18:04] [INFO] [rank0]:     raise ValueError(
[2024-09-15 20:18:04] [INFO] [rank0]: ValueError: When using DeepSpeed, `accelerate.prepare()` requires you to pass at least one of training or evaluation dataloaders with `batch_size` attribute returning an integer value or alternatively set an integer value in `train_micro_batch_size_per_gpu` in the deepspeed config file or assign integer value to `AcceleratorState().deepspeed_plugin.deepspeed_config['train_micro_batch_size_per_gpu']`.
[2024-09-15 20:18:04] [INFO] [rank0]:[W915 20:18:04.860252397 ProcessGroupNCCL.cpp:1250] Warning: WARNING: process group has NOT been destroyed before we destruct ProcessGroupNCCL. On normal program exit, the application should call destroy_process_group to ensure that any pending NCCL operations have finished in this process. In rare cases this process can exit before this point and block the progress of another member of the process group. This constraint has always been present,  but this warning has only been added since PyTorch 2.4 (function operator())
[2024-09-15 20:18:05] [INFO] E0915 20:18:05.670000 5825 torch/distributed/elastic/multiprocessing/api.py:869] failed (exitcode: 1) local_rank: 0 (pid: 5881) of binary: /srv/www/vhosts/fluxgym/venv/bin/python
[2024-09-15 20:18:05] [INFO] Traceback (most recent call last):
[2024-09-15 20:18:05] [INFO] File "/srv/www/vhosts/fluxgym/venv/bin/accelerate", line 8, in <module>
[2024-09-15 20:18:05] [INFO] sys.exit(main())
[2024-09-15 20:18:05] [INFO] File "/srv/www/vhosts/fluxgym/venv/lib/python3.10/site-packages/accelerate/commands/accelerate_cli.py", line 48, in main
[2024-09-15 20:18:05] [INFO] args.func(args)
[2024-09-15 20:18:05] [INFO] File "/srv/www/vhosts/fluxgym/venv/lib/python3.10/site-packages/accelerate/commands/launch.py", line 1091, in launch_command
[2024-09-15 20:18:05] [INFO] deepspeed_launcher(args)
[2024-09-15 20:18:05] [INFO] File "/srv/www/vhosts/fluxgym/venv/lib/python3.10/site-packages/accelerate/commands/launch.py", line 787, in deepspeed_launcher
[2024-09-15 20:18:05] [INFO] distrib_run.run(args)
[2024-09-15 20:18:05] [INFO] File "/srv/www/vhosts/fluxgym/venv/lib/python3.10/site-packages/torch/distributed/run.py", line 910, in run
[2024-09-15 20:18:05] [INFO] elastic_launch(
[2024-09-15 20:18:05] [INFO] File "/srv/www/vhosts/fluxgym/venv/lib/python3.10/site-packages/torch/distributed/launcher/api.py", line 138, in __call__
[2024-09-15 20:18:05] [INFO] return launch_agent(self._config, self._entrypoint, list(args))
[2024-09-15 20:18:05] [INFO] File "/srv/www/vhosts/fluxgym/venv/lib/python3.10/site-packages/torch/distributed/launcher/api.py", line 269, in launch_agent
[2024-09-15 20:18:05] [INFO] raise ChildFailedError(
[2024-09-15 20:18:05] [INFO] torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
[2024-09-15 20:18:05] [INFO] ============================================================
[2024-09-15 20:18:05] [INFO] sd-scripts/flux_train_network.py FAILED
[2024-09-15 20:18:05] [INFO] ------------------------------------------------------------
[2024-09-15 20:18:05] [INFO] Failures:
[2024-09-15 20:18:05] [INFO] <NO_OTHER_FAILURES>
[2024-09-15 20:18:05] [INFO] ------------------------------------------------------------
[2024-09-15 20:18:05] [INFO] Root Cause (first observed failure):
[2024-09-15 20:18:05] [INFO] [0]:
[2024-09-15 20:18:05] [INFO] time      : 2024-09-15_20:18:05
[2024-09-15 20:18:05] [INFO] host      : mule.byteconcepts.com
[2024-09-15 20:18:05] [INFO] rank      : 0 (local_rank: 0)
[2024-09-15 20:18:05] [INFO] exitcode  : 1 (pid: 5881)
[2024-09-15 20:18:05] [INFO] error_file: <N/A>
[2024-09-15 20:18:05] [INFO] traceback : To enable traceback see: https://pytorch.org/docs/stable/elastic/errors.html
[2024-09-15 20:18:05] [INFO] ============================================================
[2024-09-15 20:18:06] [ERROR] Command exited with code 1
[2024-09-15 20:18:06] [INFO] Runner: <LogsViewRunner nb_logs=149 exit_code=1>

Any ideas?

same here


Check Android Studio, gradle and android sdk version compatibility

Android studio 2.2 beta and above
Gradle version 2.2 beta and above
android sdk version support from 15 (4.0.3)


Presidio integration

Description
Integrating presidio for PII detection and anonymization.
Fixes # (issue)
Type of Change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Added new unit/integration tests
[ ] Added new notebook (that tests end-to-end)
[ ] I stared at the code and made sure it makes sense

Suggested Checklist:

[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added Google Colab support for the newly added notebooks.
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I ran make format; make lint to appease the lint gods

@RoeyBC with the v0.10.0 release today, the package structure has changed for integrations
You can create a new integration package under llama-index-integrations/postprocessors
More details here
https://github.com/run-llama/llama_index/blob/main/CONTRIBUTING.md#creating-a-new-integration-package

@nerdai 100%!
I wasn't sure if it's supported before merging/publishing. Stay tuned :D


RoBERTa : add_special_tokens=True

I set add_special_tokens=True
but I still get:
A sequence with no special tokens has been passed to the RoBERTa model. This model requires special tokens in order to work. Please specify add_special_tokens=True in your encoding.

I'm getting the same warning, also here: https://github.com/huggingface/pytorch-transformers/issues/1318

I think you should add  before and after sentences.


Solution for tests that require path to test data but don't read in a configuration file

In an effort to strip all the METplus code from hard-coded paths, the full file paths to some tests for StringTemplateSubstitution were removed.   As a result, these tests will not pass unless all instances of "/path/to" are replaced with valid file paths.  As a temporary work-around, these tests will be skipped until a solution can be found.  These tests (unlike a majority of the pytests for METplus) do NOT require a METplus config file.

Skip running the following tests because they need a hard-coded path to the data and none of these tests
require reading in a METplus config file:
-test_create_grid2obs_regex_gfs()
-test_create_grid2obs_regex_nam()
-test_create_grid2obs_regex_gdas()
-test_create_grid2obs_regex_hrrr()
-test_create_grid2obs_regex_all()

Refactor the tests that are being ignored to use the test data in the data tarball that is provided in the release.

Numerous tests that were previously skipped were removed because the functions which they were testing no longer exist in string_template_substitution.py:
test_calc_valid_for_prepbufr()
test_nam_substitution_HH()
test_nam_substitution_HHH()
test_nam_substitution_dHMS()
test_create_grid2obs_regex_gfs()
test_create_grid2obs_regex_nam()
test_create_grid2obs_regex_gdas()
test_create_grid2obs_regex_hrrr()
test_create_grid2obs_regex_all()
Replaced the '/path/to' with '/d1/METplus_Data', the 'de facto' location for the use case sample data on 'eyewall' for test_create_cyclone_regex().  Now there are 14 tests and no more tests are skipped.


doc: Add Orhun's profile to README.md

What type of PR is this? (check all applicable)

[x] 🚀 Added Name
[ ] ✨ Feature
[ ] ✅ Joined Community
[x] 🌟 ed the repo
[ ] 🐛 Grammatical Error
[ ] 📝 Documentation Update
[ ] 🚩 Other

Description
I've added my minimalistic and simple GitHub profile link to README.md
Add Link of GitHub Profile
https://github.com/orhun

Merge conflicts resolved +

Merge conflicts resolved ++


PanZoom does not work with pandas datetime data - x-axis overzooms

Trying to panzoom a linechart generated with the attached csv file.
When using the zoom function, the x-axis (DateScale) goes completely off, making this feature unusable. For one click in the wheel, the scale changes by more than 5 hours. I was expecting changes in the order of minutes.
Attached is a reference notebook implementation showing the problem.
bqplot_panzoom_issue.zip
You will need to change your file path to import the data, currently set to:
file_path = '~/work/FCMC_10Hz_simple.csv'
This is the data file:
FCMC_10Hz_simple.zip
The last cell is my current, inelegant, workaround, where I need to plot my data against numeric index instead of its true time stamp.
Could you look into this? I could not find what the problem is. I tried to set the min= during my DateScale declaration, but that did not help either.
Help is much appreciated.
Tks.

@DougRzz , I tried your code (verbatim) on Chrome, Firefox and Edge. They all give me the same result:

Notice how my time axis changes from 10:00 to 03:00 on the first click.
Do you think this maybe a timezone problem? Or a computer setting related to timezone?
I run my notebook on a jupyterhub server (Ubuntu based) which spawns a docker container (also Ubuntu based). But in the past, I ran also the notebook server locally and had the exact same problem.
Let me know how I can help troubleshooting.
bqplot is AWESOME and I really think it is a great idea. I want to help improve it.
  I'm not sure what to suggest.  Are you able to try it on Mac or Windows?  Maybe show that animation on the BQplot Gitter channel and one of the developers might be able to help.

Thanks for looking into this @DougRzz

Hello folks, I just installed jupyter locally on a windows machine and I get the exactly same bad result I had before. Chrome or Edge or Firefox.
Like I said, what seems really weird to me is that the scaling seems to change the minutes as expected, however it adds 5 hours to it... which smells like timezone issue. But I don't know what to do/try.
I printed the data min value and the scale min values. See below.
Running copy paste code from @DougRzz
Tks.

Follow-up.
OK, so I went into Windows>Settings>Date&Time
Under the "Time Zone" dropdown, I had "(UTC -05:00) Eastern Time (US & Canada)"
Bingo, when I change it to " (UTC) Coordinated Universal Time", zooming works as posted above.
@DougRzz , please try to reproduce this.
Let me know...

Yep.  When i change the timezone, it messes up the zoom.   So zooming will only work for those living in Iceland, UK, and Portugal.  A bit unfair I say.

ok. should I raise a bug somewhere else?
tks for helping me out!

@acelere just leave it here. I might soon be demonstrating my bqplot dashboard with zoomable date scale to my colleagues in the US. So thanks for spotting that one.

My Javascript knowledge is zero.  But i had a look at the Panzoom class and it led me to BaseModel.js.  I would guess that the problem lies in this bit of code.......
convert_to_json: function(elem) {
	// converts the date to a json compliant format
	if(elem === undefined || elem === null) {
		return null;
	} else {
		if (elem.toJSON === undefined) {
			return elem;
		} else {
			// the format of the string to be sent across is
			// '%Y-%m-%dT%H:%M:%S.%f'
			// by default, toJSON returns '%Y-%m-%dT%H:%M:%S.%uZ'
			// %u is milliseconds. Hence adding 000 to convert it into
			// microseconds.

			return elem.toJSON().slice(0, -1) + '000';
		}
	}
}

So Json by default returns '%Y-%m-%dT%H:%M:%S.%uZ' where the Z indicates it has been converted to UTC.  The Z is removed and then the  milli seconds is converted to micro seconds, but there is nothing to now indicate it is a time relative to UTC.   Its just a guess.    I maybe on completely the wrong track.  Does anyone have any suggestions?

Yes, I agree.
I wonder why they need to set it to a JSON compliant date.
Still in BaseModel.js:
set_date_elem: function(param, value) {

    this.set(param, this.convert_to_json(value));

},

Perhaps try something like:
set_date_elem: function(param, value) {

    this.set(param, value);

},

and see what happens...
But I have also crude understanding of JavaScript...
Tks.

It appears similar issues have been around since 2015: this old thead where jasongrout said:

By the way, IIRC, there is a difference between how python and how browsers handle local vs. UTC. If I remember correctly, we were having issues where python converted things to UTC, and the browser assumed it was local time, or vice versa, if the timezone offset wasn't explicitly specified. There's a whole can of worms there.

I did some further investigation and it is not just the IndexSelector and Panzoom that have this issue. If I modify the "Selectors.ipynb" example in the repo by setting the index of the dataframe to something that is a Timestamp, the line graph shows me the wrong time (x-axis):
#original code
#price_data = pd.DataFrame(np.cumsum(np.random.randn(150, 2).dot([[0.5, 0.4], [0.4, 1.0]]), axis=0) + #100,
#                          columns=[symbol, symbol2],
#                          index=pd.date_range(start='11-01-2019', periods=150))

#modified code
start = pd.Timestamp('2019-11-01T16:00:00')
end = pd.Timestamp('2019-11-01T17:00:00')
t = np.linspace(start.value, end.value, 150)
t = pd.to_datetime(t)
price_data = pd.DataFrame(np.cumsum(np.random.randn(150, 2).dot([[0.5, 0.4], [0.4, 1.0]]), axis=0) + 100,
                          columns=[symbol, symbol2],
                          index=t)

Notice that my data starts at 2019-11-11 16:00:00
My timezone (on windows OS) is set to UTC-5
and I get this graph:

I tried changing the timezone on the OS and it does affect the date that I get on the graph.
I am running bqplot version 0.12.0

Another minimal replicating example:
import importlib
import bqplot
importlib.reload(bqplot)
from bqplot import *
xsc=DateScale()
ysc=LinearScale()
pz=PanZoom(scales={'x':[xsc],'y':[ysc]})
mark=Scatter(scales={'x':xsc,'y':ysc})
xax=Axis(scale=xsc)
yax=Axis(scale=ysc,orientation='vertical')
fig = Figure(marks=[mark],axes=(xax,yax),interaction=pz)
mark.x=np.array([
    "2019-01-01T00:00:00",
    "2019-01-02T00:00:00",
    "2019-01-03T00:00:00",
]).astype("datetime64[s]")
mark.y=[0,1,0]
fig

I also tested the fix with the initial example given above

This issue has been fixed by PR#968 merged by commit afbe2db into masters. (bqplot version 0.12.8). Thanks for the fix @joders !


Make RuntimePlugin & RuntimePlugins Send/Sync

Motivation and Context
We will eventually want to store additional runtime plugins on fluent builders, clients, etc. To make this work, the RuntimePlugin trait needs to assert Send/Sync
Description
Small tweaks + test on the RuntimePlugin trait
Testing
CI

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Breaking change? I don't think it is since nothing in these runtime crates are actually used by anything yet.


hiredis memory leak test by valgrind

hello, I am using hiredis library in my C++ service , but have occur memory leak. the valgring output like this:
==11465== 867 (816 direct, 51 indirect) bytes in 17 blocks are definitely lost in loss record 127 of 158
==11465==    at 0x4C27F6F: calloc (vg_replace_malloc.c:623)
==11465==    by 0x5C8DF67: createReplyObject (hiredis.c:64)
==11465==    by 0x5C8DF67: createStringObject (hiredis.c:106)
==11465==    by 0x5C9550C: processLineItem (read.c:230)
==11465==    by 0x5C9550C: processItem (read.c:405)
==11465==    by 0x5C9550C: redisReaderGetReply (read.c:503)
==11465==    by 0x5C8E173: redisGetReplyFromReader (hiredis.c:863)
==11465==    by 0x5C8ECEA: redisGetReply (hiredis.c:890)
==11465==    by 0x5C8FEA4: __redisBlockForReply (hiredis.c:995)
==11465==    by 0x5C8FEA4: redisvCommand (hiredis.c:1005)
==11465==    by 0x5C8FF37: redisCommand (hiredis.c:1011)

Can you provide a small script that causes the problem?  There is no way to know if that call stack shows a leak in phpredis or in how you're calling it.
Are you sure you're calling freeReplyObject each time you retrieve a reply?

like this:
==11465== 1,020 (960 direct, 60 indirect) bytes in 20 blocks are definitely lost in loss record 128 of 158
==11465==    at 0x4C27F6F: calloc (vg_replace_malloc.c:623)
==11465==    by 0x5C8DF67: createReplyObject (hiredis.c:64)
==11465==    by 0x5C8DF67: createStringObject (hiredis.c:106)
==11465==    by 0x5C9550C: processLineItem (read.c:230)
==11465==    by 0x5C9550C: processItem (read.c:405)
==11465==    by 0x5C9550C: redisReaderGetReply (read.c:503)
==11465==    by 0x5C8E173: redisGetReplyFromReader (hiredis.c:863)
==11465==    by 0x5C8ECEA: redisGetReply (hiredis.c:890)
==11465==    by 0x5C8FEA4: __redisBlockForReply (hiredis.c:995)
==11465==    by 0x5C8FEA4: redisvCommand (hiredis.c:1005)
==11465==    by 0x5C8FF37: redisCommand (hiredis.c:1011)
==11465==    by 0x477A64: Redis::selectdb(int) (redis.cpp:100)
==11465==    by 0x4781C3: Redis::hset_get(int, std::string const&, std::string const&) (redis.cpp:224)
and in my redis.cpp:
void Redis::selectdb(int db)
{
redisCommand(_connect, "SELECT %d", db);
}
string Redis::hset_get(int db, const string& key, const string& field)
{
std::string str="";
selectdb(db);
_reply = (redisReply*)redisCommand(_connect, "HGET %s %s", key.c_str(), field.c_str());
if (_reply->len > 0)
{
str = _reply->str;
}
freeReplyObject(_reply);
return str;
}

does select db also need to freeReplyObject ?

I get it, thanks

In this code :
void Redis::selectdb(int db)
{
redisCommand(_connect, "SELECT %d", db);
}
the redisCommand return value not free;
Right approach:
redisReply *reply;
reply = redisCommand(_connect, "SELECT %d", db);
if (reply)
{
freeReplyObject(reply);
}
2017-09-19 10:58 GMT+08:00 gameyin<EMAIL_ADDRESS>
hello, I am using hiredis library in my C++ service , but have occur
memory leak. the valgring output like this:
==11465== 867 (816 direct, 51 indirect) bytes in 17 blocks are definitely
lost in loss record 127 of 158
==11465== at 0x4C27F6F: calloc (vg_replace_malloc.c:623)
==11465== by 0x5C8DF67: createReplyObject (hiredis.c:64)
==11465== by 0x5C8DF67: createStringObject (hiredis.c:106)
==11465== by 0x5C9550C: processLineItem (read.c:230)
==11465== by 0x5C9550C: processItem (read.c:405)
==11465== by 0x5C9550C: redisReaderGetReply (read.c:503)
==11465== by 0x5C8E173: redisGetReplyFromReader (hiredis.c:863)
==11465== by 0x5C8ECEA: redisGetReply (hiredis.c:890)
==11465== by 0x5C8FEA4: __redisBlockForReply (hiredis.c:995)
==11465== by 0x5C8FEA4: redisvCommand (hiredis.c:1005)
==11465== by 0x5C8FF37: redisCommand (hiredis.c:1011)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/redis/hiredis/issues/546, or mute the thread
https://github.com/notifications/unsubscribe-auth/AFz9paGGNFCWQQYtW7bRlQlL-EHINXh6ks5sjy3ggaJpZM4PbyeT
.

good


Improvements to the way we run tests on CI (and locally)

Only perform one build on CI, avoid using Browserstack as a test server, and run it on a separate port.
See individual commits for details.

OH THE IRONY.
Will fix the failing linting errors.

You can preview this change here:
Built with commit e16f8951edb7aa90ee968cf3f757507aaa1670d6
https://deploy-preview-577--govuk-design-system-preview.netlify.com

From the CI ouput, running against ac7e867 (which enabled server.debug, so we get the server output included in the Jest output):
Jest Puppeteer server output:
[Jest Puppeteer server] Running in CI, using existing build...
[Jest Puppeteer server] Listening on port 3333...

Force pushed back to remove that debug output.


Add abuse reporting endpoint for extensions aka add-ons.

Bonus: remove high abuse reporting trigger code that doesn't work.

r+


Add Max Connection Age

What kind of issue is this?

[ X ] Feature Request. Start by telling us what problem you’re trying to solve. Often a solution
already exists! Don’t send pull requests to implement new features without first getting our
support. Sometimes we leave features out on purpose to keep the project small.

In our server environment, we use DNS for Blue-Green deployment routing.  Since extremely active connections never go idle, they are never torn down and they never re-resolve DNS.  Thus the server never changes the environment it is calling.  Can a Max Connection Age be added to the Connection/Connection Pool?
We have a potential work around using a Network Interceptor.  It feels hacky since we're messing with connections, casting objects and closing sockets.
new Interceptor() {
    final ConcurrentHashMap<Integer, Long> CONNECTION_LIFETIME_MAP = new ConcurrentHashMap<>();
    final Long maxAge = TimeUnit.SECONDS.toMillis(2);

    @Override
    public Response intercept(Chain chain) throws IOException {

        Response response = chain.proceed(chain.request());

        Connection connection = chain.connection();
        if (connection != null && connection instanceof RealConnection) {
            RealConnection realConnection = (RealConnection) connection;
            int hashCode = realConnection.hashCode();
            Long current = System.currentTimeMillis();

            Long connectionStartTime = CONNECTION_LIFETIME_MAP.putIfAbsent(hashCode, current);
            if (connectionStartTime != null && current - connectionStartTime > maxAge) {
                realConnection.noNewStreams = true;
                if (realConnection.allocations.size() <= 1) {
                    CONNECTION_LIFETIME_MAP.remove(hashCode);
                    Socket socket = connection.socket();
                    Util.closeQuietly(socket);
                }
            }
        }
        return response;
    }
}

Thanks
Peter

I don’t think this is a thing. What do you do for browser user-agents?
Instead, servers should send Connection: close when they’re going out of rotation.

When we do a blue/green deploy we change the CName from pointing to ELB A (Elastic Load Balancer) to point to ELB B.  Since the connection using okhttp is coming from a very active service, the load balancer idle timeout is not hit to close the connection, nor is the okhttp idle timeout hit to close the connection.  Thus, traffic is sent to ELB A until we restart the very active service.  We typically do not tear down the inactive load balancer and leave it in an idle state.  We always run the risk of an external consumer hitting the old ELB A, but most traffic switches over within minutes.

This is topology is based on the amazon whitepaper https://d0.awsstatic.com/whitepapers/AWS_Blue_Green_Deployments.pdf

What do browsers do?

Browsers and other clients with keep alive eventually go idle and hit an idle timeout either in the client or on the ELB.  Our servers making multiple req's/sec never go idle, thus never hit the idle timeout.

I think this is best implemented as a custom interceptor.


Duplication membersAdded event

Version
JavaScript "botbuilder": "4.14.0",
Describe the bug
Give a clear and concise description of what the bug is.
We receive 2 or 4 events when user installs our application.
Expected behavior
Receive event once
Additional context
    "membersAdded": [
        {
            "id": "29:1Iat8W8y5w9RxIgqFnDUqJlJalpDXC5jlXWG3hYzfczu25fn_gNbbc6WV7V36GbpgvQjpt8_w5nHuW_os7d",
            "aadObjectId": "9272a828-5c43-4a1c-8a15-e315f8a8"
        },
        {
            "id": "28:331df719-bfd2-4fcc-aa91-f08bc21a"
        }
    ],
    "type": "conversationUpdate",
    "timestamp": "2022-11-12T12:57:45.190Z",
    "id": "f:884a2807-d9d0-d4cb-ffd6-eec40244",
    "channelId": "msteams",
    "serviceUrl": "https://smba.trafficmanager.net/amer/",
    "from": {
        "id": "29:1Iat8W8y5w9RxIgqFnDUqJlJalpDXC5jlXWG3hYzfczu25fn_gNbbc6WV7V36GbpgvQjpt8_w5nHuW_os7d",
        "aadObjectId": "9272a828-5c43-4a1c-8a15-e315f8a8"
    },
    "conversation": {
        "conversationType": "personal",
        "tenantId": "f8ed7ee1-1d5c-48b5-b6c3-6a31e6fc",
        "id": "a:18hXVgntuPkzeTp8DS4JaeE7ua5b9sk24t8WVVfeGEb-Lt0Idw_ZOEAbWq9sGopVv6FzGM7BqZjyLv985oC4SwVjrjpMKumbK2UOj128CpWCnFvJdKQ-Xxdgz9NsK"
    },
    "recipient": {
        "id": "28:331df719-bfd2-4fcc-aa91-f08bc21a",
        "name": "ProHabits Bot"
    },
    "channelData": {
        "tenant": {
            "id": "f8ed7ee1-1d5c-48b5-b6c3-6a31e6fc"
        }
    },
    "rawTimestamp": "2022-11-12T12:57:45.1909085Z",
    "callerId": "urn:botframework:azure",
    "hashId": "5da0a5f4-0e83-4e9d-a1d5-2026b69"
}

Do you have any ideas how we can receive event only once?

Might be related to https://github.com/microsoft/botbuilder-js/issues/4202
Fix #4203 was included in JavaScript SDK release 4.17.0.
@Serginyo90, could you please try to update the javascript botbuilder sdk to latest version?

@ramfattah I updated botbuilder and botbuilder-dialogs to 4.18.0 but issue still exists.
The same behavior. Duplicated onMembersAdded event

here is example of code
`export default class TeamsActivityService extends TeamsActivityHandler {
constructor() {
super()
this.onConversationUpdate(async (context: TurnContext, next) => {
  await this.addConversationReference(context)
  await next()
})

this.onMembersAdded(async (context: TurnContext, next) => {
  await this.addConversationReference(context)
  await next()
})

this.onMessage(async (context: TurnContext, next) => {
  await this.addConversationReference(context)
  await next()
})

// this.initConversations()

}`

Thanks for providing the code @Serginyo90, looking into this further.

Thanks for your patience @Serginyo90,
I was able to repro this issue after installing bot sample bot-conversation in Teams.
sharing the steps to repro:

Clone bot-conversation/nodejs
Follow the readme to set up the bot with Teams
In bots/teamsConversationBot.js, change the onMembersAddedActivity method to the following:    this.onMembersAdded(async (context, next) => {
        await Promise.all((context.activity.membersAdded || []).map(async (member) => {
            if (member.id !== context.activity.recipient.id) {
                await context.sendActivity(`Welcome to the team`);
            }
        }));

        await next();
    });

Run and add the bot app to Teams client.

Notice the POST request in Ngrok after the bot has been installed and onMembersAdded event is triggered:

Hey @JuanAr,
I was able to repro this issue. Assigned this to you for now.
Please let me know if you have any questions.
Thanks.

Hi @ramfattah .
We tried to reproduce the issue but we couldn't see the onMembersAdded event triggered more than once.
Have you been able to see the event triggered two times? In the image you shared, we see it once with the ids of the user and the bot.

Thanks for checking on this @erquirogasw,
The above screenshot was taken right after the bot app was installed in Teams.
If a member was added to a group (not install), then the result looked like:
    "membersAdded": [
        {
            "id": "xx:xxxxx...........................",
            "aadObjectId": "xxxxxxxx..........."
        }
    ],

While investigating this issue; so far, I've found that the onMembersAdded event gets triggered with the following scenarios:

If user joins a group chat
If user install the bot app in Teams

Scenario #1 was not reproducible, whereas scenario #2 is reproducible.
    "membersAdded": [
        {
            "id": "29:1Iat8W8y5w9RxIgqFnDUqJlJalpDXC5jlXWG3hYzfczu25fn_gNbbc6WV7V36GbpgvQjpt8_w5nHuW_os7d",
            "aadObjectId": "9272a828-5c43-4a1c-8a15-e315f8a8"
        },
        {
            "id": "28:331df719-bfd2-4fcc-aa91-f08bc21a"
        }
    ],

Please let me know if I've done something incorrectly or if you have any questions.
Thanks.

@ramfattah @erquirogasw main issue for me is I receive current event twice and sometime once. But usually twice. Did you able to reproduce it?

Hi everyone, we couldn't reproduce the issue. If we install the app normally, we only receive the event once (with the two ids, user and bot, but that's expected).
We can see two MembersAdded events when we install the app in two different scopes (team and personal) as shown in the images.
@Serginyo90, can you give us more information? In which scope are you installing your bot (personal, team, meeting)? Do you have a sample bot to test this behavior?
Thanks!

@erquirogasw it is personal scope in both cases.

I see that you received 2 api calls each time when add app on your screenshot. But must be only one. Correct?
Does in 2nd one the same information like in first one?

@erquirogasw Ok. I will prepare the code and share with you on Tuesday

@erquirogasw You can find the sample bot here https://github.com/Serginyo90/issue-with-ms-bot .
P.S. I tried to reproduce it with Bot Framework Emulator but can't. Can you try reproduce with Azure Bot?

Hi @Serginyo90, we weren't able to reproduce the issue when installing the provided sample in Teams. We got the same outputs as before and the behavior seems to be the expected. The only difference we can think off is the app manifest. Could you share yours so we can compare and test it?

Closing due to inactivity. @Serginyo90, please re-open if needed.

Sorry, I was in vacation guys.
Sure... here is manifest
{   "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.13/MicrosoftTeams.schema.json",   "manifestVersion": "1.13",   "version": "2.3.13",   "id": "e1dc8cc5-....",   "packageName": "com.microsoft.teams.extension",   "developer": {     "name": "Teams App, Inc.",     "websiteUrl": "https://prohabits.com",     "privacyUrl": "https://assets.stg.prohabits.com/mst/helpers/privacy.html",     "termsOfUseUrl": "https://prohabits.com/how-it-works-2"   },   "icons": {     "color": "resources/color.png",     "outline": "resources/outline.png"   },   "name": {     "short": "ProHabits Stg",     "full": "ProHabits Stg Corporation"   },   "description": {     "short": "ProHabits Stg is created for motivation",     "full": "ProHabits Stg makes people better and better each day. We are here 24/7 to help you achieve your goals."   },   "accentColor": "#FFFFFF",   "bots": [     {       "botId": "e1dc8cc5-8...",       "scopes": ["personal", "team", "groupchat"],       "supportsFiles": false,       "isNotificationOnly": true     }   ],   "composeExtensions": [],   "configurableTabs": [     {       "configurationUrl": "https://assets.stg....",       "canUpdateConfiguration": true,       "scopes": ["team", "groupchat"]     }   ],   "staticTabs": [     {       "entityId": "conversations",       "scopes": ["personal"]     },     {       "entityId": "dashboard",       "name": "Community",       "contentUrl": "https://assets.stg.prohabits.com/...#/dashboard",       "websiteUrl": "https://assets.stg.prohabits.com/...#/dashboard",       "scopes": ["personal"]     },     {       "entityId": "myActivities",       "name": "Progress",       "contentUrl": "https://assets.stg.prohabits.com/...#/myActivities",       "websiteUrl": "https://assets.stg.prohabits.com/...#/myActivities",       "scopes": ["personal"]     },     {       "entityId": "settings",       "name": "Settings",       "contentUrl": "https://assets.stg.prohabits.com/...#/settings",       "websiteUrl": "https://assets.stg.prohabits.com/...#/settings",       "scopes": ["personal"]     },     {       "entityId": "leaderboard",       "name": "Leaderboard",       "contentUrl": "https://assets.stg.prohabits.com/...#/leaderboard",       "websiteUrl": "https://assets.stg.prohabits.com/...#/leaderboard",       "scopes": ["personal"]     }   ],   "permissions": ["identity", "messageTeamMembers"],   "validDomains": [     "mabbly.wistia.com",     "youtube.com",     "youtu.be",     "prohabits.com",     "typeform.com",     "assets.prohabits.com",     "assets.dev.prohabits.com",     "assets.stg.prohabits.com"   ],   "webApplicationInfo": {     "id": "e1dc8cc5-....",     "resource": "https://localhost:3000"   },   "activities": {     "activityTypes": [       {         "type": "Daily MicroActivity",         "description": "Morning Notification",         "templateText": "{activityName}"       }     ]   } }

Hi @Serginyo90. We tested your manifest with the sample you provided both locally and in Azure, and the membersAdded event was received only once.
Also, we connected the sample to Azure Application Insights to discard a problem with it, and we got only one event.
Do you have any other feature implemented that might be causing that behavior?

@erquirogasw Ok. Looks like I found issue. Just want to confirm that it triggers onMembersAdded and onConversationUpdate events when user installs the App.

@erquirogasw so could you confirm that it triggers onMembersAdded and onConversationUpdate events when user installs the App, please?

Hi @Serginyo90. When installed, it triggers the installationUpdate and conversationUpdate (containing membersAdded info) events.

@erquirogasw thank you. I will rewrite logic using installationUpdate type.

@erquirogasw I can confirm that installationUpdate also triggered twice. The same like conversationUpdate. So issue still exists

Hi @ramfattah @Serginyo90 .
We weren't able to reproduce this issue in any of the following scenarios:

Using the bot-conversation sample. Locally and deployed to Azure.
Using the provided sample. Locally, deployed in Azure and with Application Insights.

In both scenarios, we could see 2 requests. One with activityType installationUpdate and another with activityType conversationUpdate.
The conversationUpdate contains the membersAdded array with the data of the bot and the user.
Also, we tried installing the application as personal chat, meeting, and group.
@ramfattah should we re-open this issue to investigate further?


New update broke ecowitt

I dont know what's up but the new update totally broke it. Sorry.

Oh and you can't uninstall it. Async something error.

I redownloadeded the 0.6 version of the integration and that still works. After a reboot everything works as it should.
I am afraid the integration is not maintained anymore, so at least it still works this way probably someone should take it up, but I am not capable enough to update it. I will look at the differences between the versions and see if I can figure out but do not have much hope of being successful...

Errors I get:
ERROR (MainThread) [homeassistant.setup] Setup failed for custom integration ecowitt: Unable to import component: cannot import name 'async_get_registry' from 'homeassistant.helpers.entity_registry' (/usr/src/homeassistant/homeassistant/helpers/entity_registry.py)

ERROR (MainThread) [homeassistant.config_entries] Error occurred loading flow for integration ecowitt: cannot import name 'async_get_registry' from 'homeassistant.helpers.entity_registry' (/usr/src/homeassistant/homeassistant/helpers/entity_registry.py)

I get this error since Update to HAS 5.0
How to solve?
Setup failed for custom integration ecowitt: Unable to import component: cannot import name 'async_get_registry' from 'homeassistant.helpers.entity_registry' (/usr/src/homeassistant/homeassistant/helpers/entity_registry.py)

Solution is: https://github.com/garbled1/homeassistant_ecowitt/issues/149

Solution is: #149

Doesnt work for me. I removed everything, redownloaded the 0.7 version of the integration, but cannot set it up under integrations. It gives me the  message "Config flow could not be loaded: {"message: "Invalid Handler specified"}
Redownloading the 0.6 version of the integration works then.

@pvizeli
Thank you! It works now :-)

Here is the official integration
https://www.home-assistant.io/integrations/ecowitt/
I far as I understand. this HACS version is no longer maintained.

Aah... Got it now. All working again...

Hi when i reinstall the official integration then i got the same error as Remko76.
Can anybody help me because when i add the integration Ecowitt the error come  {"message: "Invalid Handler specified"}
So what can i do?
Thx

is here any solution?

The HACS version is not maintained anymore. Uninstall and setup the official integration.

is here any solution?

had same issue because updated to HA 2023.5 while using HACS Ecowitt integration.
solved by:
-removing HACS Ecowitt integration (bypass warning that integration is configured)
-reboot HA
-remove old zombie Ecowitt configuration
-reboot HA
-add new configuration for Ecowitt using already-included Ecowitt integration
note: obviously IP will remain the same but endpoint path and port for server will change, depending on your configuration.
note2: you'll have to rename old entities on frontend because names will be different.

So how can I keep the naming of sensors? And can someone just update the hacs one to the regular one?  Also the version 0.6 won't change to Fahrenheit. And I don't know if the new update will break more stuff.

Go there --> https://github.com/garbled1/homeassistant_ecowitt/issues/155#issuecomment-1609959845


Remove unnecessary custom events

Removed unnecessary custom events and moved creation logic to a new controller
Also moved validation to controllers
fixes #86

Nothing to comment, looks good. Second member can merge.

Except for two minor things, good work!


chore(Dashboard): Remove unnecessary loading

SUMMARY
The goal of this PR is unblock the Dashboard skeleton (showing of the filters, tabs, charts containers, etc.) progressively so that the user experience is improved by showing available content sooner rather than later. This approach only works for dashboards that do not require pre-filled filters values such as "select first value by default".
This PR also cleans up places where a loading spinner was being implemented multiple times.
BEFORE
https://github.com/user-attachments/assets/ecdb36c3-d63a-4ef6-b547-1d5c95cb9505
AFTER
https://github.com/user-attachments/assets/29fa10ea-7902-4b8c-8038-19ab189f52bf
TESTING INSTRUCTIONS

The Dashboard should load normally.

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up

Dashboard doesn't load when I try to open it from tab permalink
https://github.com/user-attachments/assets/fca176fd-c5f3-4f5b-8db6-275b2b1562ac

Great catch @kgabryje. After a bit of investigation I found that permalinks use uuid for some reasons, but the frontend was completely unaware of their existence and just relied on ID or slugs. After adding some checks this issue popped up. Now the backend is exposing the uuid to the frontend to do the necessary checks when permalinks are involved.

@geido It looks like the data requests are done multiple times - twice without native filters, and even more times with native filters
BEFORE without and with native filters - all data requests fired only once

AFTER without and with native filters

Thanks again @kgabryje. By unblocking the skeleton a few competing places were trying to run the requests. I did my best to spot all of them and control the flow a little bit better. I am continuing with functional tests. All the help is appreciated!

/testenv up

@geido Tested again but it looks like the requests are still dispatched twice

Thanks for catching that again @kgabryje. It looks like that was happening on Dashboards with filters but none applied and it wasn't doing it for the other cases. I made more changes but these feel riskier as I am now controlling the triggering of the query which was set to true by default before. This approach needs more testing. Moving this back to draft for now.

/testenv up

Tentatively opening this up for review

This PR will be superseded by smaller PRs. I will update this thread accordingly:
https://github.com/apache/superset/pull/30611


Automated cherry pick of #7948: fix update image status after save failed

Cherry pick of #7948 on release/3.2.
#7948: fix update image status after save failed

/lgtm
/approve


Album title is not sanitized.

This code.
https://github.com/cjcodeproj/musicscan/blob/082b6b626c220aacda554828425f2c770c1d8e30/src/musicscan/xml/builder.py#L251-L263
The album title is not run through the XML sanitization function, sanitize_for_xml.

Commit:
https://github.com/cjcodeproj/musicscan/commit/dd90826868cff048057b1e73d3549c8a0b9331bb


Added the changes of web application firewall for application gateway

Description

Added new web application firewall features for application gateway
Updated to the 2017-03-01 Api version of Network component.

https://github.com/Azure/azure-rest-api-specs/pull/1052
This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as a link to the swagger spec, used to generate the code.
[ ] The project.json and AssemblyInfo.cs files have been updated with the new version of the SDK.

@jobatzil,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Segmentation fault with Python package for the approximate method only

Hi everyone,
I'm trying to use xgboost for a classification task with fairly big data (25M rows in the training set, the libsvm file is 2.2Go on disk), using the python package.
It works fine when I set the tree_method to 'exact' but I have a segmentation fault with the 'approx' tree_method.
Initially I thought that it was related to the high usage of RAM (I'm using a computer with 32Go RAM), so I'm using the version with external memory (https://github.com/dmlc/xgboost/blob/master/doc/external_memory.md) which create cache files correctly. But I still have a segfault.
I've tried to launch my model with xgboost directly (without using the python package) and it works for both the exact and the approx methods (although it's quite slow).
Here is the code that I'm using in python :
dtrain = xgb.DMatrix('/path/to/data/data_train_libsvm#dtrain.cache')
dval = xgb.DMatrix('/path/to/data/data_val_libsvm#dval.cache')
param = {'booster':'gbtree','silent':0, 'nthread':8,
'eta':0.1, 'max_depth':6, 'subsample':0.8, 'colsample_bytree':0.8, 'scale_pos_weight':12000,
'objective':'binary:logistic', 'eval_metric':'auc' }
watchlist  = [(dtrain,'train'), (dval,'eval')]
num_round = 300
bst = xgb.train(param, dtrain, num_round, watchlist, early_stopping_rounds=30)
I've tried to track down the error and it appears during the first booster update : line 750 in file core.py when calling _LIB.XGBoosterUpdateOneIter
If anyone has an idea of what could be going on, I would be super greatful !
Thanks,
Cheers,
Imen

interesting, if you can do gdb and get the backtrace of where the segfault happens, we can take a more careful look.

Hi,
Thanks for your quick answer.
Here is the answer I get from gdb  :
Thread 1 received signal SIGSEGV, Segmentation fault.
0x0000000108f30cb7 in rabit::engine::AllreduceBase::TryReduceScatterRing(void*, unsigned long, unsigned long, void ()(void const, void*, int, MPI::Datatype const&)) () from /usr/local/lib/python2.7/site-packages/xgboost-0.4-py2.7.egg/xgboost/libxgboost.so
(gdb) bt full
#0  0x0000000108f30cb7 in rabit::engine::AllreduceBase::TryReduceScatterRing(void*, unsigned long, unsigned long, void ()(void const, void*, int, MPI::Datatype const&)) () from /usr/local/lib/python2.7/site-packages/xgboost-0.4-py2.7.egg/xgboost/libxgboost.so
No symbol table info available.
#1  0x0000000108f314db in rabit::engine::AllreduceBase::TryAllreduceRing(void*, unsigned long, unsigned long, void ()(void const, void*, int, MPI::Datatype const&)) () from /usr/local/lib/python2.7/site-packages/xgboost-0.4-py2.7.egg/xgboost/libxgboost.so
No symbol table info available.
#2  0x0000000108f34ba5 in rabit::engine::AllreduceBase::Allreduce(void*, unsigned long, unsigned long, void ()(void const, void*, int, MPI::Datatype const&), void ()(void), void*) ()
from /usr/local/lib/python2.7/site-packages/xgboost-0.4-py2.7.egg/xgboost/libxgboost.so
No symbol table info available.
#3  0x0000000108f3dc6f in rabit::engine::Allreduce_(void*, unsigned long, unsigned long, void ()(void const, void*, int, MPI::Datatype const&), rabit::engine::mpi::DataType, rabit::engine::mpi::OpType, void ()(void), void*) ()
from /usr/local/lib/python2.7/site-packages/xgboost-0.4-py2.7.egg/xgboost/libxgboost.so
No symbol table info available.
#4  0x0000000108ecf483 in xgboost::tree::CQHistMakerxgboost::tree::GradStats::InitWorkSet(xgboost::DMatrix*, xgboost::RegTree const&, std::vector<unsigned int, std::allocator >) ()
from /usr/local/lib/python2.7/site-packages/xgboost-0.4-py2.7.egg/xgboost/libxgboost.so
No symbol table info available.
#5  0x0000000108eccc08 in xgboost::tree::HistMakerxgboost::tree::GradStats::Update(std::vector<xgboost::bst_gpair, std::allocatorxgboost::bst_gpair > const&, xgboost::DMatrix, xgboost::RegTree*) ()
from /usr/local/lib/python2.7/site-packages/xgboost-0.4-py2.7.egg/xgboost/libxgboost.so
No symbol table info available.
#6  0x0000000108ec7059 in xgboost::tree::HistMakerxgboost::tree::GradStats::Update(std::vector<xgboost::bst_gpair, std::allocatorxgboost::bst_gpair > const&, xgboost::DMatrix*, std::vector<xgboost::RegTree*, std::allocatorxgboost::RegTree* > const&) ()
from /usr/local/lib/python2.7/site-packages/xgboost-0.4-py2.7.egg/xgboost/libxgboost.so
No symbol table info available.
#7  0x0000000108e71045 in xgboost::gbm::GBTree::BoostNewTrees(std::vector<xgboost::bst_gpair, std::allocatorxgboost::bst_gpair > const&, xgboost::DMatrix*, long long, int, std::vector<std::unique_ptr<xgboost::RegTree, std::default_deletexgboost::RegTree >, std::allocator<std::unique_ptr<xgboost::RegTree, std::default_deletexgboost::RegTree > > >) ()
from /usr/local/lib/python2.7/site-packages/xgboost-0.4-py2.7.egg/xgboost/libxgboost.so
No symbol table info available.
#8  0x0000000108e73b92 in xgboost::gbm::GBTree::DoBoost(xgboost::DMatrix, long long, std::vector<xgboost::bst_gpair, std::allocatorxgboost::bst_gpair >*) () from /usr/local/lib/python2.7/site-packages/xgboost-0.4-py2.7.egg/xgboost/libxgboost.so
No symbol table info available.
#9  0x0000000108e13f86 in XGBoosterUpdateOneIter ()
from /usr/local/lib/python2.7/site-packages/xgboost-0.4-py2.7.egg/xgboost/libxgboost.so
No symbol table info available.
#10 0x000000010077c7ef in ffi_call_unix64 ()
from /usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_ctypes.so
No symbol table info available.
#11 0x000000010077d024 in ffi_call ()
from /usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_ctypes.so
No symbol table info available.
#12 0x000000010077863f in _ctypes_callproc ()
from /usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_ctypes.so
No symbol table info available.
#13 0x0000000100772c60 in PyCFuncPtr_call ()
from /usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_ctypes.so
No symbol table info available.
#14 0x000000010000eeb0 in PyObject_Call () from /usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/Python
No symbol table info available.
#15 0x000000010008ea27 in PyEval_EvalFrameEx () from /usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/Python
No symbol table info available.
#16 0x00000001000880f1 in PyEval_EvalCodeEx () from /usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/Python
No symbol table info available.
#17 0x000000010009269a in fast_function () from /usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/Python
No symbol table info available.
#18 0x000000010008eaf3 in PyEval_EvalFrameEx () from /usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/Python
No symbol table info available.
#19 0x00000001000880f1 in PyEval_EvalCodeEx () from /usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/Python
No symbol table info available.
#20 0x000000010009269a in fast_function () from /usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/Python
No symbol table info available.
#21 0x000000010008eaf3 in PyEval_EvalFrameEx () from /usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/Python
---Type  to continue, or q  to quit---
No symbol table info available.
#22 0x00000001000880f1 in PyEval_EvalCodeEx () from /usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/Python
No symbol table info available.
#23 0x0000000100087abc in PyEval_EvalCode () from /usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/Python
No symbol table info available.
#24 0x00000001000abea1 in run_mod () from /usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/Python
No symbol table info available.
#25 0x00000001000abf44 in PyRun_FileExFlags () from /usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/Python
No symbol table info available.
#26 0x00000001000aba93 in PyRun_SimpleFileExFlags ()
from /usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/Python
No symbol table info available.
#27 0x00000001000bd445 in Py_Main () from /usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/Python
No symbol table info available.
#28 0x00007fff99dc95ad in start () from /usr/lib/system/libdyld.dylib
No symbol table info available.
#29 0x0000000000000000 in ?? ()
No symbol table info available.
I don't know much about c++ so I'm not sure I understand this message. It seems related to some lib, but I don't really get how I could fix it.
I'm running xgboost on a Mac Pro with el Capitan (32Go RAM).
Thanks a lot !
Imen

Make sure you update the most recent version, specifically pull the most recent version of rabit.
Doing a clean clone might be easier.
This should have been solved in most recent version

I've installed the lib last Monday with a clean clone and used the setup.py file from the package. Did you change anything since then ?
Thanks !

In the latest version of rabit https://github.com/dmlc/rabit/blob/849b20b7c822d194a515cc5587c37764cdf39385/src/allreduce_robust.cc#L82
If you are not in distributed mode, the TryAllreduceScatterRing won't be executed from allreduce function. I fixed in in sometime. But somehow in your case the code still get into this function

Hi,
Thanks for the answer. I've checked that I have the correct version of rabit and this is ok.
But I did some printing and it seems that the python package is not calling allreduce_robust.cc methods but directly allreduce_base.cc
This could explain why I don't have the segfault issue when launching xgboost directly (not through python).
But I don't know how to fix the python call to the c++ lib.
Thanks again for your help!

I would add that I am also experiencing this behavior with the approximate algorithm, although it seems to be pretty inconsistent with how many observations it can handle; I was feeding 40 million points in a couple days ago, and now it's choking on 7 million from the same dataset.  It seems to work fine when set to exact, although that would certainly seem to defeat the purpose of approximation for larger datasets!
A clean clone/install didn't seem to help me, either.

I can confirm this error.

clean install from latest sources
py wrapper
data fits in memory
approx tree method crashes for me if tree depth is set greater than 6

I tried to enforce robust allreduce without any luck.

everything works fine if linked against librabit_empty.a
(after changing LIB_RABIT = librabit.a to LIB_RABIT = librabit_empty.a in make/config.mk)

please check if latest change fixed this problem https://github.com/dmlc/xgboost/pull/1186

seems to work just fine now

it seems to work fine now, so I close the issue.
Thanks !


Make some improvements to documentation

This PR improves the readme.rst file to give a better overview of the moscot software.
Closes #772

I'm not sure how to fix
docs/index.rst:23: (INFO/1) No role entry for "doc" in module "docutils.parsers.rst.languages.en".
docs/index.rst:23: (ERROR/3) Unknown interpreted text role "doc".
docs/index.rst:23: (INFO/1) No role entry for "doc" in module "docutils.parsers.rst.languages.en".
docs/index.rst:23: (ERROR/3) Unknown interpreted text role "doc".
docs/index.rst:23: (INFO/1) No role entry for "doc" in module "docutils.parsers.rst.languages.en".
docs/index.rst:23: (ERROR/3) Unknown interpreted text role "doc".
docs/index.rst:26: (INFO/1) No role entry for "doc" in module "docutils.parsers.rst.languages.en".
docs/index.rst:26: (ERROR/3) Unknown interpreted text role "doc".
docs/index.rst:27: (INFO/1) No role entry for "doc" in module "docutils.parsers.rst.languages.en".
docs/index.rst:27: (ERROR/3) Unknown interpreted text role "doc".
docs/index.rst:28: (INFO/1) No role entry for "doc" in module "docutils.parsers.rst.languages.en".
docs/index.rst:28: (ERROR/3) Unknown interpreted text role "doc".
docs/index.rst:29: (INFO/1) No role entry for "doc" in module "docutils.parsers.rst.languages.en".
docs/index.rst:29: (ERROR/3) Unknown interpreted text role "doc".
docs/index.rst:33: (INFO/1) No role entry for "doc" in module "docutils.parsers.rst.languages.en".
docs/index.rst:33: (ERROR/3) Unknown interpreted text role "doc".
docs/index.rst:34: (INFO/1) No role entry for "doc" in module "docutils.parsers.rst.languages.en".
docs/index.rst:34: (ERROR/3) Unknown interpreted text role "doc".

The links work fine after building the docs locally, would appreciate some help here.

@MUCDK, feel free to modify this PR to your liking, it's meant as a starting point.

Looks good thanks!
The error is due to wrong links to notebooks, e.g. do
- :doc:`Trajectory inference <notebooks/moscot_notebooks/tutorials/200_temporal_problem>`

instead of
- :doc:`Trajectory inference <notebooks/tutorials/200_temporal_problem>`

notebooks/moscot_notebooks/tutorials/

Unfortunately that change does not fix the issue, and additionally, it gives
/Users/mlange/Projects/moscot/docs/index.rst:23: WARNING: unknown document: 'notebooks/moscot_notebooks/tutorials/200_temporal_problem' [ref.doc]
/Users/mlange/Projects/moscot/docs/index.rst:23: WARNING: unknown document: 'notebooks/moscot_notebooks/tutorials/500_spatiotemporal' [ref.doc]
/Users/mlange/Projects/moscot/docs/index.rst:23: WARNING: unknown document: 'notebooks/moscot_notebooks/tutorials/100_lineage' [ref.doc]
/Users/mlange/Projects/moscot/docs/index.rst:26: WARNING: unknown document: 'notebooks/moscot_notebooks/tutorials/400_spatial_mapping' [ref.doc]
/Users/mlange/Projects/moscot/docs/index.rst:27: WARNING: unknown document: 'notebooks/moscot_notebooks/tutorials/300_spatial_alignment' [ref.doc]
/Users/mlange/Projects/moscot/docs/index.rst:28: WARNING: unknown document: 'notebooks/moscot_notebooks/tutorials/600_tutorial_translation' [ref.doc]
/Users/mlange/Projects/moscot/docs/index.rst:34: WARNING: unknown document: 'notebooks/moscot_notebooks/tutorials/index' [ref.doc]
/Users/mlange/Projects/moscot/docs/index.rst:72: WARNING: unknown document: 'notebooks/moscot_notebooks/tutorials/index' [ref.doc]
/Users/mlange/Projects/moscot/docs/notebooks/examples/problems/200_custom_cost_matrices.ipynb:80004: WARNING: py:attr reference target not found: moscot.problems.generic.FGWProblem.prepare.cost [ref.attr]


Dockerize code generation

Added a docker-compose spec that uses an openapitools image for codegen
Reran client gen, which added a missing file for the alternate AddAllowListEntry binding
Renamed 'ccloud' dir to 'openapi-generator'

TFTR!


Allow disabling signatures

As I run imgproxy behind the main application server to apply authorization, there's not much point in signing it. It's both coding and runtime overhead, so can we make it optional?

Hi! This is the part of v2.0 that will be released soon.

:tada: imgproxy v2.0 has been released :tada: Take a look at the new features, including disabling signature checking: https://github.com/DarthSim/imgproxy/blob/master/CHANGELOG.md#v200