yank to clipboard using xsel doesn't work

Hi!
I run tmux with tmux-yank via x-forwarding on Windows, don't know if this is related. At least using xsel works fine: echo "foo" | xsel -b results in having "foo" in the system clipboard, accessible both from Linux and Windows.
However when copying from tmux by either using the mouse (with mouse-mode on) or by using the copy mode, the selection is always put in the PRIMARY clipboard, where I can paste it by using  + ].
I tried using @override_copy_command or custom_copy_command, setting both to xsel -b, but with no effect.  Also I set yank_selection_mouse to clipboard, which also has no effect. Am I doing something wrong?
Thanks,
Torsten

@hensz Have you found a workaround for this? I can work around it by pressing y while holding the mouse button down, but it's annoying to hold the mouse button down. But disabling auto-yank on mouseup doesn't work either...it ignores the setting.

Hi!
The workaround I currently use is holding SHIFT while selection - this disables tmux copy mode and uses the regular Linux copy mode. I can live with this, however I still want to know why the way I want to use doesn't work. Is this a bug, or am I doing somethign wrong here?

Another user chiming in. It doesn't seem to work with xclip either. I can confirm that the workaround by @hensz works on my machine too, but at that point, there is no reason to use tmux-yank. For context, I'm running a very recent Arch Linux with tmux version 2.9a.

Same here.  Running PhotonOS v3 which doesn't support xclip, xsel, or pbcopy so was hoping the ESC sequences (which I thought was the original magic behind this) would be my one option.  Alas, this plugin still does not transfer anything to the clipboard.

Hi there!
Does no one have any clue what causes the issue? Since tmux-yank explicitly supports pasting to the system clipboard it should be possible to get it to work - but how, with which settings?
Any help is appreciated. If you need further information e.g. logs or whatever, I'm happy to provide this.
Thanks,
Torsten

So while I can live with the workaround, using Shift+select, I still like to use the built-in copy&paste functionality of tmux to copy into the clipboard. Since this is not working with tmux-yank, is someone aware of an alternative way to do this, e.g. with a different plugin?

Is someone reading this? As three user already mentioned, tmux-yank seems to be useless of this is a general issue. Or does anyone see this different?

maybe we should use the origin tmux way to do the samething.
https://unix.stackexchange.com/a/131187

There are several suggestions in this thread. I tried a few, but none worked for me. Since I'm not really familiar with Linux clipboard, I don't understand much from these threads and can only copy&paste without understanding what actually is going on here.
Nevertheless, there's this extension, tmux-yank, which should solve exactly this problem, yanking to clipboard, but in fact it doesn't.

There are several suggestions in this thread. I tried a few, but none worked for me. Since I'm not really familiar with Linux clipboard, I don't understand much from these threads and can only copy&paste without understanding what actually is going on here.
Nevertheless, there's this extension, tmux-yank, which should solve exactly this problem, yanking to clipboard, but in fact it doesn't.

My tmux work fine with xsel with this configure in tmux.conf:
bind -T copy-mode-vi y send-keys -X copy-pipe-and-cancel 'xsel -i -b'
My tmux version is 3.1 and this configure should work in tmux version > 2.5
It works the way exactly as tmux-yank, so also check you disable the old run tmux-yank configure.
I put my tmux.conf here, you may compare it with yours.

Nope, doesn't work. Since I suspected xsel to behave strange I tested this:
echo foo | xsel -ib
This does nothing, the clipboard content (which I then paste with Ctrl+Insert) is still unchanged.
However, when I run xsel with -ip (primary instead of clipboard) pasting with both Ctrl+Insert and middle mouse click pasted "foo\n" -- sadly with a trailing newline, but better than nothing.
So I modified you config entry from xsel -i -b to xsel -ip, just as on the command line. But no luck, pasting doesn't work.
Is there a way to diagnose why this doesn't work? Since currently I don't see where things go wrong. Is it the hook for copy-mode-vi, is it send-keys, is it the copy-pipe-and-cancel event or the xsel command?

I also now tried tmux 3, but the result is nearly identical. The only difference is: With tmux 3 the command xsel -ib works as expected - but only when run from command line, but not together with tmux-yank.
Has anyone ever managed to get copying to the clipboard to work? If yes, how?

Still no update... :-(

Do you run tmux with set -g mouse on ?
If so, make sure to change the default of tmux_yank to copy to clipboard via
# With mouse support turned on (see below) the default clipboard for mouse selections is primary.
set -g @yank_selection_mouse 'clipboard' # or 'primary' or 'secondary'

Refer also the Readme

I take it that this project is abandoned? It would've been really useful...

Since we don't use x-forwarding anymore (for reasons), xsel and xclip doesn't work at all. Thus, this issue is not relevant for me anymore, so from my perspective the issue can be closed.

If wl-copy is installed then it will be picked up automatically. Even if running X11. See the following comment for how to fix this: https://github.com/tmux-plugins/tmux-yank/issues/180#issuecomment-2309004378


fi ligatures not disabled in VScode 1.53

The fi family of ligatures are not disabled in the latest VScode at the time of writing (1.53.0)
I'm not sure if this is the same issue as https://github.com/microsoft/vscode/issues/106596

Is this only with a particular ligature font? I've updated to VSCode 1.53.0, and I'm not seeing a problem when using Fira Code.

That old bug #106596 was caused by an update of VSCode back in September that caused the old technique I had used for breaking apart ligatures, borrowed from Disable Ligatures, to fail. I came up with a new trick using hair spaces which has since then remained working. That fix has been in since 2020-09-14.

I tried the Iosevka font, and saw no problems with that either. By the way, there are single-codepoint Unicode ligatures for ﬀ, ﬁ, ﬂ, ﬃ, and ﬄ -- if you use those, Ligatures Limited will have no effect on them. It only breaks apart multi-codepoint ligatures which are blended into single glyphs via font rendering.

Sorry for the delay in response here - I didn't get the notifications.
I'm using a vanilla fresh install of VScode 1.53.2, on a MacBook running Catalina 10.15.7 (in case that makes a difference). I'm using Fira Code. The document I'm looking at includes words like "final" in standard UTF8 encoding - not using the codepoint for "fi" - but the "fi" of "final" is still being squashed into the corresponding ligature.

That seems very odd, since afaik Fira Code doesn't even have the fi ligature. Are you sure your font wasn't accidentally changed to Menlo, which does have those ligatures?
At an rate, this addition to your settings.json should help:
"ligaturesLimited.ligatures": "- ff fi fl ffi ffl"

Are you sure your font wasn't accidentally changed to Menlo

Oh. Looks like that is exactly what happened, and I hadn't noticed. Not sure what caused that to happen. Thanks for the assistance, and apologies for suggesting it was your awesome extension that was at fault.


The Heroku-20-Build Ruby version does not match the Heroku Platform Ruby.

We are using Heroku-20-build Docker image to simulate the Heroku platform locally in our development environments. We are using the build image as some gems are C extensions and require building. However, the Heroku-20-build has Ruby 2.7.0 and when we do a git push to deploy to the Heroku platform, the platform is expecting Ruby 2.7.2 and rejects the push.
I would have expected the Heroku-20-build Docker image to match the Heroku-20 platform.

@davidhooey Hi! The Heroku stack images act as a base image that contains commonly used OS libraries and tooling, such as OpenSSL, compilers, C library development headers etc. The full list of packages they contain can be seen here:
https://devcenter.heroku.com/articles/stack-packages
Whilst some language toolchains(eg Python and Ruby) are included in the base image for convenience, these are not intended for use by your application, and more to make it easier for various compile-time scripts (that might have a dependency on another language) to just work. For example when using Node.js and npm installing a packaging, it might need to use node-gyp, which requires that Python be available on the system in some form.
Instead, an applications primary language is provided by a buildpack:
https://devcenter.heroku.com/articles/buildpacks
In the case of a Ruby app, that means this buildpack:
https://github.com/heroku/heroku-buildpack-ruby
So in production, your app won't be using the Ruby 2.7.0 from the stack image, but the copy of Ruby installed by the buildpack into your app's slug. The buildpack will also be performing other tasks beyond just providing Ruby -- for example helping to configure Rails.
If you wanted to more closely emulate Heroku builds locally, you would need to use one of the examples from this thread:
https://github.com/heroku/stack-images/issues/56#issuecomment-788402124
However, unless you have very specific requirements I would recommend just using the official Docker Hub Ruby images (eg ruby:2.7.2) when developing locally, and instead catching the rare dev-prod parity issues via Heroku CI, Review Apps or a staging app.

Awesome, thanks!


Repeated Diagnostic Messages in coc.nvim with Verible Language Server

My IDE is as following:

gvim (v9.0.1897) with coc.nvim (v0.0.82-84ce0312)
Verible Verilog Language Server built at v0.0-3638-ge3ef2a37

Repeated Warning Messages
The verible-verilog-ls configurations are as following:
"languageserver": {
        "verible":{
            "enable": true,
            "command": "verible-verilog-ls",
            "filetypes": ["verilog", "systemverilog"],
            "trace.server":"messages"
        }
    }

When I created a new .v file and typed several spaces, repeated identical warning messages popped up:

I expect a single warning message per actual issue per file change or analysis trigger.
After I configured the language server as following in coc.nvim, the second warning message dissapeared.
"languageserver": {
        "verible":{
            "enable": true,
            "command": "verible-verilog-ls",
            "filetypes": ["verilog", "systemverilog"],
            "disabledFeatures": ["diagnostics"], //  fix repeated identical messages bug
            "trace.server":"messages"
        }
    }

But I don't think this is an expected behavior or a long-term solution.
Log Messages
Logs of the preceeding different configurations are smilar except the message timestamps and durations.
[Trace - 22:45:20.639] Sending request 'initialize - (0)'.
Verible Verilog Language Server built at v0.0-3638-ge3ef2a37
commandline: C:/Program Files/Vim/vimfiles/languageserver/verible/verible-verilog-ls.exe
[Trace - 22:45:20.647] Received response 'initialize - (0)' in 8ms.
[Trace - 22:45:20.647] Sending notification 'initialized'.
[Trace - 22:45:20.650] Sending notification 'workspace/didChangeConfiguration'.
[Trace - 22:45:20.650] Sending notification 'textDocument/didOpen'.
[Trace - 22:45:20.650] Sending request 'textDocument/diagnostic - (1)'.
[Trace - 22:45:20.651] Received notification 'textDocument/publishDiagnostics'.
[Trace - 22:45:20.651] Received response 'textDocument/diagnostic - (1)' in 1ms.
[Trace - 22:45:40.429] Sending notification 'textDocument/didChange'.
[Trace - 22:45:40.429] Sending request 'textDocument/diagnostic - (2)'.
[Trace - 22:45:40.429] Received notification 'textDocument/publishDiagnostics'.
[Trace - 22:45:40.430] Received response 'textDocument/diagnostic - (2)' in 1ms.
[Trace - 22:45:41.191] Sending notification 'textDocument/didChange'.
[Trace - 22:45:41.193] Sending request 'textDocument/diagnostic - (3)'.
[Trace - 22:45:41.194] Received notification 'textDocument/publishDiagnostics'.
[Trace - 22:45:41.195] Received response 'textDocument/diagnostic - (3)' in 2ms.

Verbose logs of the two configurations are also similar except the message timestamps and durations.

On every change of the file, the diagnostics are updated. It seems like your editor does not coalesce these ?
There are also two mechanisms diagnostics can be received:

the default by Verible is to publish new diagnostics whenever some change happens in the file (textDocument/publishDiagnostics)
It also seems that your editor is requesting diagnostics independently (textDocument/diagnostic), so maybe this is where things get merged and show up multiple times ? Is the "disabledFeatures" configuration switching the explicit request off ?

So things do look like they work as intended, just that the editor does not remove the duplicates.
I'll have a look if it is possible by the editor to request not auto-publishing diagnostics when it actually does the request by itself (maybe there is a setting the editor can send to the language server).
But  you should probably also file an issue with your editors' language server implementation to make sure they coalesce the identical diagnostic messages properly or ignore diagnostic notifications when they already request

The "disabledFeatures" configuration doesn't switch the explicit request off. I think it just diabled one of the messages from diaplaing.
I will file an issue with the language server implementation plugin as well.

Is the "disabledFeatures" configuration switching the explicit request off ?

The disabledFeatures made coc.nvim ignore publishDiagnostics one.
verible server files the capabilities with diagnosticProvider, coc.nvim will use pull mode to request to server for diagnostics.
I think the server should use both publishDiagnostics and diagnosticProvider at the same time.

Just chiming in that this is also an issue with nvim-lspconfig:

Here's my setup:
-- ~/.config/nvim/after/plugin/lsp.lua
require'lspconfig'.verible.setup{}

I'm not sure what the differences are between the implementation of Verible and other language servers, but this is the only language server that outputs diagnostic messages twice for me.

So maybe we need to change the language server to not auto-publish findings whenever the editor is in a mode where it actively pulls the diagnostics regardless if there was an auto-diagnostic already sent.
I am having some vacation coming up, so I might have some time to look at it.


FastAdapter.expand notifyItemChanged always return false?

public void expand(boolean notifyItemChanged) {
        int length = getItemCount();
        for (int i = length - 1; i >= 0; i--) {
            expand(i);
        }
    }

 public void expand(int position) {
        expand(position, false);
}

i have to override expand(int position) to this to get the correct behavior
public void expand(int position) {         expand(position, true);

@adrianpdm seems like I do not pass forward the value. true.

This is fixed in v3


Correction for raw affiliation Building Blocks for FUture Electronics Laboratory (2BFUEL) IRL2002 CNRS – Yonsei University  03722 Seoul Republic of Korea; Univ. Angers CNRS MOLTECH-Anjou UMR 6200 SFR MATRIX  F-49000 Angers France

Correction needed for raw affiliation Building Blocks for FUture Electronics Laboratory (2BFUEL) IRL2002 CNRS – Yonsei University  03722 Seoul Republic of Korea; Univ. Angers CNRS MOLTECH-Anjou UMR 6200 SFR MATRIX  F-49000 Angers France
raw_affiliation_name: Building Blocks for FUture Electronics Laboratory (2BFUEL) IRL2002 CNRS – Yonsei University  03722 Seoul Republic of Korea; Univ. Angers CNRS MOLTECH-Anjou UMR 6200 SFR MATRIX  F-49000 Angers France
new_rors: 039yyx623;02feahw73;01wjejq96;01w108f05
previous_rors: 039yyx623;02feahw73;01wjejq96
works_examples: W4311776856
contact:<PHONE_NUMBER>219485ada19f296bf9c023:b08b01dc5ee73f0af2f3b4e7e6 @ sorbonne-universite.fr

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


Update just file

Add new recipe to merge current branch with dev branch

I don't know what I was hoping to do with this issue. Marking as closed


Feat - Manage role accessibility

We have to manage roles with following hierarchy
ROLE_ADMIN - Can do anything
ROLE_PENTESTER - Can do the same as MANAGER and manage vulns, view only his missions, manage only his own account
ROLE_MANAGER - Can assign users to a mission, manage a client account, manage missions
ROLE_CLIENT - Can view only his mission
To populate rights on resources for each role we will provide native roles such as ROLE_{resource}{action} (eg. ROLE_MISSION_READ) and ROLE{resource}_MANAGE to allow all actions on a resource.

done in #59


Correct prepupal/pharate synonyms [sf#34]

Reported by mmc46 on 2014-05-06 16:21 UTC
Correct synonyms for prepupa and pharate stages from FBrf0036849.
Change from:
synonym: "brown puparium" EXACT [FlyBase:FBrf0036849]
to
synonym: "brown puparium stage" EXACT [FlyBase:FBrf0036849]

Updated by mmc46 on 2014-05-06 16:21 UTC

Priority: 1 --> 5

Updated by mmc46 on 2014-06-02 14:09 UTC

status: open --> closed


Allow NSURLCredential persistence to be specified

There's currently no clear way to reset the current session preventing logout for web services that use basic auth and session storage.
    public func authenticate(#user: String, password: String) -> Self {
        let credential = NSURLCredential(user: user, password: password, persistence: .ForSession)

        return authenticate(usingCredential: credential)
    }

I'd propose adding a persistence parameter to the authenticate method or adding a method to the Manager to clear the current session.

Hi @jessecurry, thank you for your feedback.
There is a way to reset the credential, but it is pretty hidden. You could get the credential storage and remove the credential like so:
let manager = Alamofire.Manager.sharedInstance
if let storage = manager.session.configuration.URLCredentialStorage {
    storage.removeCredential(credential: credential, forProtectionSpace: protectionSpace)
}

However, since this would be brutal to have to do each time and still utilize the convenience of the authenticate method, I think your proposal for exposing the persistence parameter is valid.
I have incorporated your suggestion into cb9e11b9 and set the default value to .ForSession. Thus, the change is backwards compatible and still has the same default behavior as before.
Cheers 🍻

Thanks!
And thanks for the info.

I think this should be considered for re-opening - I'm using None as the persistence, however the credential still persists. Is this actual Alamofire or NSURLCredential's fault?
let credential = NSURLCredential(user: studentUsername, password: studentPassword, persistence: .None)
Alamofire.request(.GET, "https://api.co.uk/Default.aspx").authenticate(usingCredential: credential)


ModuleNotFoundError: No module named 'sklearn.ensemble.forest'

Hi,
After downloading the repository and setting up the conda environment, I get the error "ModuleNotFoundError: No module named 'sklearn.ensemble.forest'" after trying to run "python CRISPRidentify.py --input_folder TestInput". Running "python CRISPRidentify.py -h", works and shows me the flags, so I believe the environment was properly set up, but I cannot troubleshoot the error. Do you have any insight on solving this? Attached is a screenshot of the error.

Best,
Megan

Hi,
could you activate the environment you set up and post the output of conda list ?


about 'strategy = "ddp_find_unused_parameters_false"' and 'strategy = "ddp_find_unused_parameters_true"' error

Bug description
I want to train a gan model, and use MANUAL OPTIMIZATIONhttps://lightning.ai/docs/pytorch/stable/model/manual_optimization.html to setup my training process. I got the following errors when setting 'strategy = "ddp_find_unused_parameters_false"'.
Traceback (most recent call last):
  File "/home/lee/Desktop/workspace2/project/tts/RVC/c/training/trainv1.py", line 296, in <module>
    main(conf, exp_dir, training_dir, bool(args.use_pretrain))
  File "/home/lee/Desktop/workspace2/project/tts/RVC/c/training/trainv1.py", line 205, in main
    trainer.fit(system)
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/pytorch_lightning/trainer/trainer.py", line 545, in fit
    call._call_and_handle_interrupt(
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/pytorch_lightning/trainer/call.py", line 43, in _call_and_handle_interrupt
    return trainer.strategy.launcher.launch(trainer_fn, *args, trainer=trainer, **kwargs)
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/pytorch_lightning/strategies/launchers/subprocess_script.py", line 102, in launch
    return function(*args, **kwargs)
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/pytorch_lightning/trainer/trainer.py", line 581, in _fit_impl
    self._run(model, ckpt_path=ckpt_path)
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/pytorch_lightning/trainer/trainer.py", line 990, in _run
    results = self._run_stage()
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/pytorch_lightning/trainer/trainer.py", line 1036, in _run_stage
    self.fit_loop.run()
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/pytorch_lightning/loops/fit_loop.py", line 202, in run
    self.advance()
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/pytorch_lightning/loops/fit_loop.py", line 359, in advance
    self.epoch_loop.run(self._data_fetcher)
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/pytorch_lightning/loops/training_epoch_loop.py", line 136, in run
    self.advance(data_fetcher)
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/pytorch_lightning/loops/training_epoch_loop.py", line 242, in advance
    batch_output = self.manual_optimization.run(kwargs)
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/pytorch_lightning/loops/optimization/manual.py", line 92, in run
    self.advance(kwargs)
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/pytorch_lightning/loops/optimization/manual.py", line 112, in advance
    training_step_output = call._call_strategy_hook(trainer, "training_step", *kwargs.values())
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/pytorch_lightning/trainer/call.py", line 309, in _call_strategy_hook
    output = fn(*args, **kwargs)
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/pytorch_lightning/strategies/strategy.py", line 381, in training_step
    return self._forward_redirection(self.model, self.lightning_module, "training_step", *args, **kwargs)
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/pytorch_lightning/strategies/strategy.py", line 628, in __call__
    wrapper_output = wrapper_module(*args, **kwargs)
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/torch/nn/parallel/distributed.py", line 1519, in forward
    else self._run_ddp_forward(*inputs, **kwargs)
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/torch/nn/parallel/distributed.py", line 1355, in _run_ddp_forward
    return self.module(*inputs, **kwargs)  # type: ignore[index]
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/pytorch_lightning/strategies/strategy.py", line 621, in wrapped_forward
    out = method(*_args, **_kwargs)
  File "/home/lee/Desktop/workspace2/project/tts/RVC/c/training/core/model/systemv2.py", line 249, in training_step
    loss_d, loss_g, total_loss = self.common_step(batch, batch_nb, train=True)
  File "/home/lee/Desktop/workspace2/project/tts/RVC/c/training/core/model/systemv2.py", line 222, in common_step
    self.manual_backward(loss_gen_all)
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/pytorch_lightning/core/module.py", line 1050, in manual_backward
    self.trainer.strategy.backward(loss, None, *args, **kwargs)
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/pytorch_lightning/strategies/strategy.py", line 200, in backward
    self.pre_backward(closure_loss)
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/pytorch_lightning/strategies/ddp.py", line 307, in pre_backward
    prepare_for_backward(self.model, closure_loss)
  File "/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/pytorch_lightning/overrides/distributed.py", line 55, in prepare_for_backward
    reducer._rebuild_buckets()  # avoids "INTERNAL ASSERT FAILED" with `find_unused_parameters=False`
RuntimeError: It looks like your LightningModule has parameters that were not used in producing the loss returned by training_step. If this is intentional, you must enable the detection of unused parameters in DDP, either by setting the string value `strategy='ddp_find_unused_parameters_true'` or by setting the flag in the strategy with `strategy=DDPStrategy(find_unused_parameters=True)`.
Epoch 0:   0%|          | 0/264 [00:02<?, ?it/s]

Process finished with exit code 1

So I changed the setting to 'strategy = "ddp_find_unused_parameters_true"' and also got the following warnings:
[W reducer.cpp:1346] Warning: find_unused_parameters=True was specified in DDP constructor, but did not find any unused parameters in the forward pass. This flag results in an extra traversal of the autograd graph every iteration,  which can adversely affect performance. If your model indeed never has any unused parameters in the forward pass, consider turning this flag off. Note that this warning may be a false positive if your model has flow control causing later iterations to have unused parameters. (function operator())

I haven't found an effective way after searching github issues.
What version are you seeing the problem on?
v2.1
How to reproduce the bug
No response
Error messages and logs
When find_unused_parameters=True, and add the following code to model:
    def on_after_backward(self) -> None:         print("on_after_backward enter")         for name, p in self.named_parameters():             if p.grad is None:                 print(name)         print("on_after_backward exit")
I don't know why this happen， the net_g model(gan generator) will be trained in the training process.
on_after_backward enter

net_g.flow.flows.6.enc.res_skip_layers.2.weight_v
net_g.flow.flows.6.enc.cond_layer.bias
net_g.flow.flows.6.enc.cond_layer.weight_g
net_g.flow.flows.6.enc.cond_layer.weight_v
net_g.flow.flows.6.post.weight
net_g.flow.flows.6.post.bias
net_g.emb_g.weight
on_after_backward exit
[W reducer.cpp:1346] Warning: find_unused_parameters=True was specified in DDP constructor, but did not find any unused parameters in the forward pass. This flag results in an extra traversal of the autograd graph every iteration,  which can adversely affect performance. If your model indeed never has any unused parameters in the forward pass, consider turning this flag off. Note that this warning may be a false positive if your model has flow control causing later iterations to have unused parameters. (function operator())
on_after_backward enter
on_after_backward exit
Epoch 0:   0%|          | 1/264 [00:02<10:06,  0.43it/s, v_num=15]/home/lee/Documents/software/anaconda3/envs/rvc-webuibkp/lib/python3.9/site-packages/torch/autograd/__init__.py:251: UserWarning: Grad strides do not match bucket view strides. This may indicate grad was not created according to the gradient layout contract, or that the param's strides changed since DDP was constructed.  This is not an error, but may impair performance.
grad.sizes() = [64, 1, 4], strides() = [4, 1, 1]
bucket_view.sizes() = [64, 1, 4], strides() = [4, 4, 1] (Triggered internally at ../torch/csrc/distributed/c10d/reducer.cpp:320.)
  Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass
on_after_backward enter
on_after_backward exit
on_after_backward enter
on_after_backward exit
Epoch 0:   1%|          | 2/264 [00:03<06:58,  0.63it/s, v_num=15]on_after_backward enter
on_after_backward exit
on_after_backward enter
on_after_backward exit
Epoch 0:   1%|          | 3/264 [00:04<05:53,  0.74it/s, v_num=15]on_after_backward enter
on_after_backward exit
on_after_backward enter
on_after_backward exit
Epoch 0:   2%|▏         | 4/264 [00:04<05:17,  0.82it/s, v_num=15]on_after_backward enter
on_after_backward exit
on_after_backward enter
on_after_backward exit
Epoch 0:   2%|▏         | 5/264 [00:05<04:57,  0.87it/s, v_num=15]on_after_backward enter
on_after_backward exit
on_after_backward enter
on_after_backward exit
Epoch 0:   2%|▏         | 6/264 [00:06<04:44,  0.91it/s, v_num=15]on_after_backward enter
on_after_backward exit
on_after_backward enter
on_after_backward exit
Epoch 0:   3%|▎         | 7/264 [00:07<04:35,  0.93it/s, v_num=15]on_after_backward enter
on_after_backward exit
on_after_backward enter
on_after_backward exit
Epoch 0:   3%|▎         | 8/264 [00:08<04:27,  0.96it/s, v_num=15]on_after_backward enter
on_after_backward exit
on_after_backward enter
on_after_backward exit
Epoch 0:   3%|▎         | 9/264 [00:09<04:22,  0.97it/s, v_num=15]on_after_backward enter
on_after_backward exit

Environment

Current environment
#- Lightning Component (e.g. Trainer, LightningModule, LightningApp, LightningWork, LightningFlow):
#- PyTorch Lightning Version (e.g., 1.5.0): 2.1.0
#- Lightning App Version (e.g., 0.5.2):
#- PyTorch Version (e.g., 2.0): 2.1.0+cu118
#- Python version (e.g., 3.9): 3.10
#- OS (e.g., Linux): ubuntu20.04
#- CUDA/cuDNN version:2.1.0+cu118
#- GPU models and configuration: rtx1080ti
#- How you installed Lightning(`conda`, `pip`, source): pip
#- Running environment of LightningApp (e.g. local, cloud): local

More info
No response

the same problem.

the same problem
self.manual_backward(l1_loss, retain_graph=True)
self.manual_backward(other_loss)


Make directories recursive.

Refs #249. (It's only part 1).

Actually, I'm just going to make them one PR.


List of tools broken

The file that the list of Tools included in the container link shown below does not exist;

See here for a list of Tools included in the container

I think it should be going to https://github.com/efabless/foss-asic-tools/blob/main/recipe.csv rather than https://github.com/efabless/foss-asic-tools/blob/main/recipes/recipe.csv?


-bash: bash_execute_unix_command: cannot find keymap for command

I am on OSX El Capitan. I upgraded bash with brew install bash. Then installed marker. But, when I try to activate with Ctrl+Space, I get the following error: -bash: bash_execute_unix_command: cannot find keymap for command

@pindexis I cannot speak for @saptak , but I am having exactly the same problem with bash 4.3.46:
$ bash --version
GNU bash, version 4.3.46(1)-release (x86_64-apple-darwin15.5.0)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

I also installed bash 4.3+ via brew install bash.

Any news about this ?
Same here with 4.4.0
GNU bash, version 4.4.0(1)-release (x86_64-apple-darwin15.6.0)
Copyright (C) 2016 Free Software Foundation, Inc.```

Same thing here. Bump. Any chance to get this working and package this as a homebrew install?
$ bash --version
GNU bash, version 4.4.5(1)-release (x86_64-apple-darwin16.3.0)
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

BUMP

And another one..... This is broke on osx..
Anyone figured this one out?

and another one.. looking for a solution to this one.

come oooon

guys, I'm on OSX and couldn't reproduce this. Here's the bash version I installed with brew:
NU bash, version 4.4.12(1)-release (x86_64-apple-darwin16.3.0)
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Ok so I finally succeeded to reproduce. It seems be related to Ctrl+space binding in Bash 4+.
Switching the key-binding to something other that Ctrl+space will fix the issue.
You can do that by setting the MARKER_KEY_GET env in .bashrc (before sourcing marker):
export MARKER_KEY_GET='\C-l'
[[ -s "$HOME/.local/share/marker/marker.sh" ]] && source "$HOME/.local/share/marker/marker.sh"

It would be good to try this on the latest tip of the master branch

The issue seems resolved now, tried on macOS Sierra. It will great to add this is a note in README.

issue still exists with Ubuntu 18.04

issue still exists with Ubuntu 18.04

Can confirm, same here.

I ubuntu, I set it to export MARKER_KEY_GET='\C-P', this way I have the same shortcut for Sublime Text, VSCode and marker.


Entity extraction using ruta scripts are not working post upgrading uima and ruta to 3x version.

Entity extraction using ruta scripts are not working post upgrading uima and ruta to 3x version.
It was working fine with 2x versions and only JCas classes are upgraded to 3x version.
I did not find any exceptions but its not detecting any entities.
Any extra steps need to do for ruta scripts during migration.
versions used:
[uimaj-3.4.1]
[uimafit-3.4.0]
[ruta-3.3.0]
[cleartk-3.0.0]
i am expecting any heads up which can help in debugging this and any steps that missed during migration.

Have you tried running your scripts using the Ruta Eclipse plugins in Ruta debug mode?

yes , its working with ruta eclipse plugin and tested with below eclipse update
https://downloads.apache.org/uima/eclipse-update-site-v3/

Getting Null pointer exception from the framework side
at org.apache.uima.ruta.condition.PartOfCondition.check(PartOfCondition.java:80) ~[ruta-core-3.3.0.jar:?]
at org.apache.uima.ruta.condition.PartOfCondition.eval(PartOfCondition.java:52) ~[ruta-core-3.3.0.jar:?]
at org.apache.uima.ruta.condition.NotCondition.eval(NotCondition.java:37) ~[ruta-core-3.3.0.jar:?]
at org.apache.uima.ruta.condition.AndCondition.eval(AndCondition.java:42) ~[ruta-core-3.3.0.jar:?]
at org.apache.uima.ruta.rule.RutaRuleElement.doMatch(RutaRuleElement.java:381) ~[ruta-core-3.3.0.jar:?]
at org.apache.uima.ruta.rule.RutaRuleElement.startMatch(RutaRuleElement.java:81) ~[ruta-core-3.3.0.jar:?]
at org.apache.uima.ruta.rule.ComposedRuleElement.startMatch(ComposedRuleElement.java:79) ~[ruta-core-3.3.0.jar:?]
at org.apache.uima.ruta.rule.RutaRule.apply(RutaRule.java:72) ~[ruta-core-3.3.0.jar:?]
at org.apache.uima.ruta.rule.RutaRule.apply(RutaRule.java:63) ~[ruta-core-3.3.0.jar:?]
at org.apache.uima.ruta.rule.RutaRule.apply(RutaRule.java:42) ~[ruta-core-3.3.0.jar:?]
at org.apache.uima.ruta.block.RutaScriptBlock.apply(RutaScriptBlock.java:74) ~[ruta-core-3.3.0.jar:?]
at org.apache.uima.ruta.RutaModule.apply(RutaModule.java:56) ~[ruta-core-3.3.0.jar:?]

I dimly remember something about potentially having to re-generate ruta basic annotations in particular after certain actions such as deleting annotations or adding annotations outside of ruta scripts. Check the RutaEngine.PARAM_REINDEX_UPDATE_MODE, e.g. try setting it to COMPLETE.

Its not helping and mostly anchors values are coming as null in ruta internal classes

@pkluegl Any idea?

@reckart:
The RutaBasic annotations store additional information about the annotations.
They need to be updated for each addition or removal of any annotations,
i.e internal maps need to be up to date all the time or else the rules will be executed incorrectly.
The RutaBasic annotations can be shared across different analysis engines processing the same CAS and the RutaEngine provides parameters configuring the internal update strategy.
These parameters are named PARAM_INDEX_** or PARAM_REINDEX_**.
If runtime is not an issue, then you can set PARAM_REINDEX_UPDATE_MODE to COMPLETE and the RutaEngine will update everything.
These configuration helped and it regenerated ruta basic annotations.

Thanks for the feedback!


Support for casting from strings

Hi there,
I was trying out timex_ecto and now I have encountered the problem that I can’t seem to cast ISO 8601 strings into Timex.Ecto.Datetime through a changeset.
Say I have the following Ecto Schema:
defmodule DateTimeTest do
  use Ecto.Schema
  import Ecto.Changeset

  schema "date_time_test" do
    field :timex, Timex.Ecto.DateTime
    field :ecto, Ecto.DateTime
  end

  def changeset(struct, params) do
    cast(struct, params, [:timex, :ecto])
  end
end

When I try to cast ISO 8601 strings, it works fine with Ecto.DateTime while Timex.Ecto.DateTime fails:
iex> DateTimeTest.changeset(%DateTimeTest{}, %{timex: "2016-12-19T02:23:05Z", ecto: "2016-12-19T02:23:05Z"})
# #Ecto.Changeset<action: nil,
#  changes: %{ecto: #Ecto.DateTime<2016-12-19 02:23:05>},
#  errors: [timex: {"is invalid",
#    [type: Timex.Ecto.DateTime, validation: :cast]}], data: #DateTimeTest<>,
#  valid?: false>

Am I missing something here? Unfortunately, the Timex docs don’t mention changesets at all.

Some more context: I’m trying this with Elixir 1.3.3, timex_ecto 3.0.5 and timex 3.1.5.
Researching the problem, I also tried the example given in #16 and it doesn’t work either:
iex> Timex.Ecto.DateTime.cast!("2016-02-02T12:30:00Z")
# :error

Could you upgrade to timex_ecto 3.1.0? Your example code works as expected there.

Where would I find that version? timex_ecto’s latest version on Hex is 3.0.5 just like here on GitHub.

I just published it, sorry about that!


day 1 of requesting for input otp & breadcrumb 🔥🔥

Describe the feature
day 1 of requesting for input otp & breadcrumb 🔥🔥
edit:
for reference
https://ui.shadcn.com/docs/components/breadcrumb
https://ui.shadcn.com/docs/components/input-otp

Hello,
Tbh, these reminders are very distracting and not necessary.

It is assumed that any feature in shadcn/ui is already on the roadmap/being worked on for this project, therefore it doesn't need a feature request issue

Related:

https://github.com/huntabyte/shadcn-svelte/issues/645#issuecomment-1908562871
https://github.com/huntabyte/shadcn-svelte/issues/683
And others...

Also, for some additional context on the otp input, the origina/headless author is working on a Svelte wrapper/version here, https://github.com/guilhermerodz/input-otp/tree/feat/multi-frameworks, and until that is merged/released, the best we can do is wait for Svelte support to arrive.
Cheers.

Yep, exactly what @shyakadavis said! You can sleep easy knowing that everything in the original is making its way here!


WIP: deCONZ use forward entry setup

Description:
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

@balloob just a quick check I'm not doing something different from how you want it. Also, are tests expected for the platforms and deconz setup?

Yes this seems right.
And yes, everything that has to do with config entries or entity registry requires full test coverage.

Make sure to remove the WIP from the title when it's ready for review.

@balloob it's the tests that are left. Trying to figure stuff out. Would help if you could hint me in the right direction.
I'm trying to figure out how to mock the pydeconz class and methods since they only need to return true or false

@balloob I feel like this is ready for a review now

Awesome!

Great @balloob !


airhv report error 647 on win11

reboot the system
run on.bat  with administry, report error 647
and cannot turn off except reboot

actually facing same issue but on windows 10 21H2

Run DbgView as administrator enable "Capture Kernel" try to start airhv then paste its output here

interesting that before some windows update it was working and i have intel cpu

can it be cuz of Hyper-V possibly enabled?

Yes, nested virtualization is disabled by default in hyper-v

i have disabled Hyper-V and some other related thing in windows components but it doesnt take any effect and also tried commenting vmx support check in airhv and got reasonable bsod

uploaded minidump of bsod here https://easyupload.io/jkfk0b

as i discovered it bsods here

also issue may be in Virtualization-Based Security (VBS) windows feature and i dont know why its enabled on my windows in first place (probably some windows update enabled it) and i dont know how to disable it
tried following this guide but its still active on my system

create service 647
winver win10 22h2 19045, vmware vm enable vt-x and virtual iommu
[12:57:39.473]  [INFORMATION]   [perform_allocation:117] Allocation successful
[12:57:39.510]  [INFORMATION]   [perform_allocation:117] Allocation successful
[12:57:39.528]  [INFORMATION]   [perform_allocation:117] Allocation successful
[12:57:39.544]  [INFORMATION]   [perform_allocation:117] Allocation successful
[12:57:39.600]  [INFORMATION]   [perform_allocation:117] Allocation successful
[12:57:39.661]  [INFORMATION]   [init_vcpu:271] vcpu entry allocated successfully at FFFFDB032ED05190
[12:57:39.770]  [INFORMATION]   [init_vcpu:271] vcpu entry allocated successfully at FFFFDB032ED05270
[12:57:39.915]  [ERROR]   [create_ept_page_table:254] Failed to allocate memory for PageTable
[12:57:39.942]  [ERROR]   [DriverEntry:113] Vmm initialization failed
[12:57:40.739]  [INFORMATION]   [DriverEntry:89] HyperVisor On
[12:57:40.739]  [INFORMATION]   [DriverEntry:94] Got offsets
[12:57:41.618]  [INFORMATION]   [DriverEntry:99] Got Ssdt

create service 647 winver win10 22h2 19045, vmware vm enable vt-x and virtual iommu
[12:57:39.473] [INFORMATION] [perform_allocation:117] Allocation successful [12:57:39.510] [INFORMATION] [perform_allocation:117] Allocation successful [12:57:39.528] [INFORMATION] [perform_allocation:117] Allocation successful [12:57:39.544] [INFORMATION] [perform_allocation:117] Allocation successful [12:57:39.600] [INFORMATION] [perform_allocation:117] Allocation successful [12:57:39.661] [INFORMATION] [init_vcpu:271] vcpu entry allocated successfully at FFFFDB032ED05190 [12:57:39.770] [INFORMATION] [init_vcpu:271] vcpu entry allocated successfully at FFFFDB032ED05270 [12:57:39.915] [ERROR] [create_ept_page_table:254] Failed to allocate memory for PageTable [12:57:39.942] [ERROR] [DriverEntry:113] Vmm initialization failed [12:57:40.739] [INFORMATION] [DriverEntry:89] HyperVisor On [12:57:40.739] [INFORMATION] [DriverEntry:94] Got offsets [12:57:41.618] [INFORMATION] [DriverEntry:99] Got Ssdt

Virtualization-based Security already disable

create service 647 winver win10 22h2 19045, vmware vm enable vt-x and virtual iommu
[12:57:39.473] [INFORMATION] [perform_allocation:117] Allocation successful [12:57:39.510] [INFORMATION] [perform_allocation:117] Allocation successful [12:57:39.528] [INFORMATION] [perform_allocation:117] Allocation successful [12:57:39.544] [INFORMATION] [perform_allocation:117] Allocation successful [12:57:39.600] [INFORMATION] [perform_allocation:117] Allocation successful [12:57:39.661] [INFORMATION] [init_vcpu:271] vcpu entry allocated successfully at FFFFDB032ED05190 [12:57:39.770] [INFORMATION] [init_vcpu:271] vcpu entry allocated successfully at FFFFDB032ED05270 [12:57:39.915] [ERROR] [create_ept_page_table:254] Failed to allocate memory for PageTable [12:57:39.942] [ERROR] [DriverEntry:113] Vmm initialization failed [12:57:40.739] [INFORMATION] [DriverEntry:89] HyperVisor On [12:57:40.739] [INFORMATION] [DriverEntry:94] Got offsets [12:57:41.618] [INFORMATION] [DriverEntry:99] Got Ssdt

Increasing the virtual machine memory to 4G can solve this problem


Sierra support

On macOS Sierra I get Seil cannot connect with kernel extension. Please restart your system in order to solve the problem., and remapping does not work.

See #68

whoops missed that.

dkarter, that thread has since closed.


Review script for paper "2023SpWea..2103358H" made with predictor "DataLinkerCondenseDetailsWithTemplate"

Created by Paper Data Linking Bot
Please review the download script and instrument details for the paper.
bibcode: 2023SpWea..2103358H
predictor: DataLinkerCondenseDetailsWithTemplate

There is definitely some pagination or something going on in the background with these results:
LASCO
Query for LASCO C2 Detector Data:
Results from 1 Provider:

10000 Results from the VSOClient:
Source: http://vso.stanford.edu/cgi-bin/search
Total estimated size: 1[9](https://github.com/abuonomo/paper-data-links/pull/8/checks#step:8:10).806 Gbyte

results from 2011-01-01 to 2011-03-28, so its been truncated because this is the (correct) query range from script:
start_date = '2011-01-01'
end_date = '2011-12-31'

SECCHI COR-2 on STERO_A
no records returned.
SECCHI COR-2 on STEREO_B
https://github.com/abuonomo/paper-data-links/pull/8/checks#:~:text=4000 Results from,size%3A 30.905 Gbyte
Goes from 2011-01-01 to 2011-01-25.
SECCHI HI1 on STEREO_A
https://github.com/abuonomo/paper-data-links/pull/8/checks#:~:text=Query for SECCHI,size%3A 17.087 Gbyte
2011-01-01 to 2011-09-21
SECCHI HI1 on STEREO_A
2011-01-01 to 2011-04-21
and similar results for the rest, showing evidence of truncation.


Support for Keyed Messages in Producer

The current Producer doesn't support Keyed Messages. We use log compaction in a number of topics, and this would prevent us from fully moving to the new driver. Is this feature in the roadmap?
Great improvements in the last weeks @oleksiyk!

Sorry, what do you mean it doesn't support keyed messages?
producer.send({
            topic: 'kafka-test-topic',
            partition: 1,
            key: 'test-key',
            message: {
                value: new Date().toISOString()
            }
        }),

That's wonderful news then. Neither the documentation nor the unit tests had any mention of it. I should have looked at the source code: https://github.com/oleksiyk/kafka/blob/master/lib/producer.js#L131. Sorry about that!

I just didn't consider this as standalone feature. Will add a separate docs and tests items.


add ecs support

Elastic Common Schema Support
target uses client as the default in ECS; legacy keeps geoip as default
Co-authored-by: Ry Biesemeyer<EMAIL_ADDRESS>Fix: https://github.com/logstash-plugins/logstash-filter-geoip/issues/163

published at v7.1.0


[PHPStanRules] Fixes to ensure check next node instanceof Identifier on CheckUsedNamespacedNameOnClassNodeRule

Ref https://github.com/rectorphp/rector/pull/4727#issuecomment-735271972

All checks have passed :tada: @TomasVotruba it is ready for review.

Thanks.
Failing test case should be added too, so we know if still works

not sure about that, I will try if that possible.

fixture next is not identifier has been added.

All checks have passed 🎉 @TomasVotruba it is ready.

Thank you


Implement smux transition

This does not include switching the handshake to JSON.
I'm rerunning the test that failed (nondeterministically) in #1758 to see if it still fails with smux. If so, we'll tackle it here.

update: I've confirmed that the bug is caused by two gateways attempting to connect to each other at the same time. Adding a global mutex to serialize calls to Connect fixes the bug. Of course, in real life there isn't any way to prevent this scenario. Instead, we could add a mutex so that the gateway is never both connecting and accepting a connection at the same time. A related problem is that the connection protocol does not allow the gateway to reject a connection after it reads the remote's port number; the remote will assume that the connection was successful, while the other end has already hung up. We should modify the handshake so that after all relevant information has been sent, the gateways confirm that they want to continue the connection. I recommend that we do this in tandem with the transition to JSON.

I suggest that we merge this, after which I'll open a PR that:

switches handshake to JSON
changes handshake sequence
uses UniqueID to prevent double-connecting

The new handshake sequence is:

Connecting peer sends JSON-encoded sessionHeader, which includes GenesisID, UniqueID, and port number
Receiving peer sends a string indicating acceptance, or an error indicating why the connection was rejected
If receiving peer accepts, it also sends its own sessionHeader
Connecting peer responds with accept/reject string

Instead of the WantConn boolean, the connecting peer will send an error in step 4 if it just wants to ping instead of a full connection.
Additionally, the gateway will maintain a map of UniqueIDs (possibly as the key for its peer map, instead of the net address). This will be used to prevent double-connect scenarios, especially the recently discovered race where two gateways connect to each other at the same time. Of course, we still need to check the IP/hostname to prevent a single IP (or later, /16 block) from monopolizing the peer list.

Double connecting is more trivially fixed with a lock that prevents you from accepting and forming connections at the same time. That lock will also prevent two peers from connecting to eachother at the same time

Sorry, that is what I meant by "double connecting". I guess there are two situations that could refer to.
I don't think a simple mutex will prevent it. You need to check your peer list for duplicates too, because you can't simply assume that current peers will never try to dial you again (they could be running non-standard code). And if you have the duplicate-checking code, there's little reason to add a new mutex, because the dup check could already use an exclusive lock on the existing mutex.

Pretty much looks good. I'm expecting to be doing a ton of testing on the interactions between the versions before we merge the gateway branch, so I'm not nearly as worried about testing here.


install: enhance start probe checker conditions

When creating e2e test case for CAA DeamonSet rolling update, I found the test sometimes fails. For a peerpod deployment with 2 replicas, the AvailableReplicas may change to zero when CAA DeamonSet rolling update. That means the service based on the deployment will be unavailable when rolling update. It's not as expected.
After investigation, it looks like it's not a good idea to check pod.Status.Phase is "Running" to determine if the PeerPod is available or not:
https://github.com/confidential-containers/cloud-api-adaptor/blob/c30eaac2f971229c9059f4a7a935294c8d9f8524/pkg/probe/checker.go#L50C4-L50C4
According to go docs, pod phase Running means:
https://pkg.go.dev/k8s.io/api/core/v1#PodPhase
// PodRunning means the pod has been bound to a node and all of the containers have been started.
// At least one container is still running or is in the process of being restarted.
PodRunning PodPhase = "Running"

In following CAA logs, we can see the PodPhase is "Running", however, the Ready Condition is "False":
v1.PodCondition{Type:"Ready", Status:"False", LastProbeTime:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC), LastTransitionTime:time.Date(2023, time.September, 14, 6, 21, 58, 0, time.Local), Reason:"ContainersNotReady", Message:"containers with unready status: [nginx]"}
2023/09/14 06:22:19 [probe/probe] Dealing with PeerPod: nginx-deployment-6c59c6f6d-jwzv6, in phase: Running
2023/09/14 06:22:19 [probe/probe] Last time the Pod ready: 2023-09-14 06:21:58 +0000 UTC
2023/09/14 06:22:19 [probe/probe] pod has not restarted: v1.PodStatus{Phase:"Running", Conditions:[]v1.PodCondition{v1.PodCondition{Type:"Initialized", Status:"True", LastProbeTime:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC), LastTransitionTime:time.Date(2023, time.September, 14, 6, 18, 7, 0, time.Local), Reason:"", Message:""}, v1.PodCondition{Type:"Ready", Status:"False", LastProbeTime:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC), LastTransitionTime:time.Date(2023, time.September, 14, 6, 21, 58, 0, time.Local), Reason:"ContainersNotReady", Message:"containers with unready status: [nginx]"}, v1.PodCondition{Type:"ContainersReady", Status:"False", LastProbeTime:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC), LastTransitionTime:time.Date(2023, time.September, 14, 6, 21, 58, 0, time.Local), Reason:"ContainersNotReady", Message:"containers with unready status: [nginx]"}, v1.PodCondition{Type:"PodScheduled", Status:"True", LastProbeTime:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC), LastTransitionTime:time.Date(2023, time.September, 14, 6, 18, 7, 0, time.Local), Reason:"", Message:""}}, Message:"", Reason:"", NominatedNodeName:"", HostIP:"<IP_ADDRESS>", PodIP:"<IP_ADDRESS>", PodIPs:[]v1.PodIP{v1.PodIP{IP:"<IP_ADDRESS>"}}, StartTime:time.Date(2023, time.September, 14, 6, 18, 7, 0, time.Local), InitContainerStatuses:[]v1.ContainerStatus(nil), ContainerStatuses:[]v1.ContainerStatus{v1.ContainerStatus{Name:"nginx", State:v1.ContainerState{Waiting:(*v1.ContainerStateWaiting)(nil), Running:(*v1.ContainerStateRunning)(nil), Terminated:(*v1.ContainerStateTerminated)(0xc0003f8380)}, LastTerminationState:v1.ContainerState{Waiting:(*v1.ContainerStateWaiting)(nil), Running:(*v1.ContainerStateRunning)(nil), Terminated:(*v1.ContainerStateTerminated)(nil)}, Ready:false, RestartCount:0, Image:"[Encrypted]", ImageID:"[Encrypted]", ContainerID:"containerd://28dcc4efe3b5c0dda7c7a399fa4fcbb1111def15c6be832f72e15137f8736778", Started:(*bool)(0xc0009ebd28)}}, QOSClass:"BestEffort", EphemeralContainerStatuses:[]v1.ContainerStatus(nil)}

So it's better to check pod.Status.Conditions with type "Ready", if the Status is "True":
https://pkg.go.dev/k8s.io/api/core/v1#PodConditionType
// PodReady means the pod is able to service requests and should be added to the
// load balancing pools of all matching services.
PodReady PodConditionType = "Ready"

Moreover, we can compare the Probe start time and the Ready condition LastTransitionTime, make sure the Peer Pod is ready after CAA pod restarted.

I think the license compliance can be ignored, it pops looks because of a PR against a branch, can you please fix the others failures in CI. @genjuro214

@huoqifeng now passed


emmet.excludeLanguages needs a window reload to take effect

VSCode Version: Code - Insiders 1.14.0-insider (15b579d13dbf6817bb493feff6f36cec87577929, 2017-06-27T05:11:33.154Z)
OS Version: Linux x64 4.10.0-24-generic
Extensions:

Extension
Author (truncated)
Version

EditorConfig
Edi
0.9.3

lorem-ipsum
Tyr
1.0.0

sort-lines
Tyr
1.3.0

vscode-svgviewer
css
1.4.2

tslint
eg2
0.15.0

git-project-manager
fel
1.3.2

md-navigate
jri
0.0.1

vscode-scss
mrm
0.6.2

seti-icons
qin
0.1.3

vim
vsc
0.9.0

(1 theme extensions excluded)

#29500

You mean the auto completions.
The command Emmet: Expand Abbreviation doesnt need the reload


Quick fix for issue #233. Lock the current react-native version to 0.28

Please verify the following:

[X] Everything works on iOS/Android
[X] ignite-base ava tests pass
[X] fireDrill.sh passed

Describe your PR

Locks the react-native version used to init the base template to 0.28.0. Since the base directory assumes 0.28, I felt hard-coding the current version was appropriate.

@GantMan @skellock Is this what you were thinking for 0.28?

Yes!
It might need to become 2 parameters because of the space between --version and 0.28.0 though.  I'd have to test that.
But yes.  That's exactly it.
Just to need to run a few tests to make sure all is well.
Thank you @tminard

This looks great!   Couple things.
I'd like that moved into two params, and the second param I'd like it to pull from a well placed variable.
A const at the top of the file is fine.
We're going to eventually need to move this as a possible parameter, so we can test locally with different RN versions before we release to the public.  But I feel that might be out the scope of your PR.  Perhaps it's a secondary ticket.
Thanks @tminard

This is perfect.   Yeah, the next thing I'd like to do is add that parameter at some point.  It would be exclusively for us to test versions of RN before changing the lock version here in the repo.
We can do it via code for now :)


Use procedure IsSaaSInfrastructure instead of IsSaaS

Summary
Use procedure IsSaaSInfrastructure since for azure key vault secrets it's only important if the environment is BC SaaS or anything else.
If the key vault feature should be checked during testing then this has to be done in a BC SaaS Sandbox.
Work Item(s)
Fixes #27260
Fixes AB#549124

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 24627.


Update doc build instructions

Closes #5638

Thanks @jrbourbeau. Worked for me.

Looks good!  Thanks @jrbourbeau


minor typo worth fixing

In the "Important" box shaded blue - small typo worth fixing: "metadat" should be "metadata"
Enabling the enhanced dataset metadata feature results in an irreversible upgrade to reports. Any Power BI reports loaded or created with Power BI Desktop, once the enhanced dataset metadata enabled, are irreversibly converted to the enhanced dataset metadat [METADATA] format.

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

ID: 7e42fcb7-fa8f-638c-bdfd-8d5110baa3ed
Version Independent ID: c5e57e1b-b10a-7070-d26e-829feda2f2ed
Content: Using enhanced dataset metadata in Power BI Desktop (preview) - Power BI
Content Source: powerbi-docs/connect-data/desktop-enhanced-dataset-metadata.md
Service: powerbi
Sub-service: powerbi-desktop
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Thanks, @JD-BOS! Nice catch! I've corrected the typo.

Thanks so much for the impressive PBI documentation – very helpful!! ~ Jay
From: Kate Follis<EMAIL_ADDRESS>Sent: Thursday, August 13, 2020 6:56 PM
To: MicrosoftDocs/powerbi-docs<EMAIL_ADDRESS>Cc: Jay DeLaune<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/powerbi-docs] minor typo worth fixing (#2425)
Thanks, @JD-BOShttps://github.com/JD-BOS! Nice catch! I've corrected the typo.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/powerbi-docs/issues/2425#issuecomment-673749341, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQTIYMA44AGP4OTVMN5TGGTSARVOXANCNFSM4P6NZ2PA.
JF&CS NOTICE: 'EXTERNAL EMAIL’: This email originated from outside of the organization. Do Not Click any links or open any attachments unless you trust the sender and know the content is safe.
External Message Warning
JF&CS CONFIDENTIALITY NOTICE: The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited.


Add playground demo to make website script.

This change is

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

Comments from Reviewable


Set up edge click events and have edges populate the sidebar form, Thomasg/edge-sidebar

Also switched out the familiarity and stress level text fields with sliders. Merge this one after my other branch that resolves tickets #80 and #88, as this branch has those changes within it as well.

Newer PR deals with this issue.


METRON-1474 Add normalizecss

Contributor Comments
This PR adds normalizecss to the frontend projects. It is useful to bridge the differences between browsers.
Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:

[X] Is there a JIRA ticket associated with this PR? If not one needs to be created at https://issues.apache.org/jira/browse/METRON-1474.
[X] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

[ ] Have you included steps to reproduce the behavior or problem that is being changed or addressed?

[ ] Have you included steps or a guide to how the change may be verified and tested manually?

[ ] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh

[ ] Have you written or updated unit tests and or integration tests to verify your changes?

[X] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

[X] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:
cd site-book
mvn site

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

Normalize is included with Bootstrap, so it isn’t necessary to add it again as an NPM dependency. You can see it being imported in the metron-alerts application on this line. We should be doing something similar in metron-config in a new PR.

@sardell Thanks.
@xyztdanid4 Please let us know if you feel this PR is still relevant.  If not, please close the PR.  Otherwise, the PR may be closed as inactive according to the Metron Development Guidelines.

-1 as this has become an abandoned PR.  I will open a request to close this PR.


Support Microsoft Edge browser

If this already works, then we simply need to update the documentation to indicate support. Support for Edge must be complete before or very close to the release of Windows 10 (scheduled for July 29). If this does not coincide with a planned release of Fine Uploader, a hotfix release should be pushed out instead.

I just tested Spartan/Edge/whatever via a Windows 10 Insider Preview against Fine Uploader 5.2.2. Brief tests suggest that everything obvious is working well except for file dropping. This is not a big surprise as each new version of Explorer in the past has required adjustments to Fine Uploader's DnD module.
The next task will involve fixing DnD for Spartan. Then, I'll spend some time with more in-depth testing.

It looks like Spartan may not yet support dropping of files from the desktop. I assume that will be ironed out before release.

Official word is that drooping of files will not be supported by Edge in the initial release. https://twitter.com/morris_charles/status/611997674460479488

pushing this to 6.0.0 since Edge still does not support file dropping, AFAIK.

I'm dropping this from the schedule as Microsoft doesn't seem to have any specific plans to support this feature.

According to the Edge changelog, support for this feature was added in build 10565. Assuming this passes verification, Edge will be supported as part of Fine Uploader 5.5.0.

When attempting to test out the DnD feature in Edge, I noticed that the available Windows 10 VMs only support Edge 10240. I reached out to the Edge team, and they informed me that indeed there is no support for 10565 in Windows 10 VMs at the moment. No known date for release of a VM with this build of Edge. So, I'll need to remove this from the schedule yet again.

Still not working in Edge. The drop-zone appears and immediately disappears when dragging a file onto the browser window, flickering when moving the file around. Dropping does not work.
BUT, when I manually remove the "display: none;" from the drop-zone in developer tools, I'm able to drag a file onto it and have it uploaded, without any problems and no flickering of the drop zone. The drop zone then disappears after the upload as normal.
Any chance you could fix this?

Edge is not yet supported by Fine Uploader. This has not been possible for various reasons (all on the Microsoft side). Edge didn't even support file dropping until a few months ago, and then there was no VM available with the build of edge that included support for file dropping. I'll check again to see if there is an updated VM. If there is, I'll try to add edge support again.

good news :) I checked the code myself and found a solution for DnD
The problem is not in the DnD module itself, that one is fully working. The problem is in the browser being incorrectly detected as Firefox, while not all Firefox features seem to work.
This same problem seems to have happened with IE11 in the beginning. See master/client/js/util.js Line 554:
qq.firefox = function() {         return (!qq.ie11() && navigator.userAgent.indexOf("Mozilla") !== -1 && navigator.vendor !== undefined && navigator.vendor === "");     };
Here you explicitly say it is not Firefox if it is also IE11. You just need to do the same thing with Edge
So I added another function to identify Edge and then changed the Firefox function as following:
qq.edge = function() { 	return navigator.vendor === "" && navigator.userAgent.indexOf("Edge") !== -1; }; qq.firefox = function() { 	return (!qq.edge() && !qq.ie11() && navigator.userAgent.indexOf("Mozilla") !== -1 && navigator.vendor !== undefined && navigator.vendor === ""); };
With these lines changed, the DnD (and all other features I have used) work as expected.
Maybe you can use this information to fix the DnD problem in Edge :)

Thanks for looking into this! I'll take a closer look and add support for edge in a near future release.

Sorry, still blocked on this. Microsoft has still not released a VM with a current build of Edge. The latest one available is 10240, which does not support file dropping. Without that VM, there isn't much I can do here. I'd suggest pinging someone at Microsoft about this. I'm going to mention this to them again, as I did a couple months ago.

Microsoft tells me an updated VM will be available in a couple weeks.

I now have a VM to work with, so I'll begin updating investigating support for Edge. Once this is complete (assuming I don't run into any more blockers) this will be released as 5.7.0.

PR to release Edge support is #1557. Anyone here interested in giving it a whirl to verify before I release?

This is completed and Microsoft Edge is now supported as of Fine Uploader 5.7.0.


Weather app search field should become empty after every search

Is your feature request related to a problem? Please describe.

We have to manually remove the previous city entered
Cities input field has spellcheck = true, which results in an unnecessary line under the name making it look incorrect.

Describe the solution you'd like.
I would like to make the search field become empty after every search.
Will make spellcheck = false for the input field.
Describe alternatives you've considered.
n/a
Add any other context or screenshots about the feature request here.

@AtharvKasar04 Thank you for providing your insight but it is not required as of now.


[BUG]: why duplicate PID appears on rank 0

Is there an existing issue for this bug?

[X] I have searched the existing issues

🐛 Describe the bug
When using the GeminiPlugin to train a model, it runs normally at the start. However, once a checkpoint（shard） is saved, a duplicate PID appears on rank 0.
Start:

After Saved Checkpoint

Why and how to avoid it ? Thanks a lot
Environment
Torch: 2.1.2
Colossalai: 0.4.2
Python: 3.8
Cuda: 12.1.0

While dig into, I found that when saving the optimizer, the PIDs from other ranks appear on rank 0.
torch.cuda.empty_cache()
booster.save_optimizer(optimizer, path_optimizer, shard=True, size_per_shard=2048)

I observed that, following this line: https://github.com/hpcaitech/ColossalAI/blob/2f583c154944b1f00d7a4fb1ce529db9d8595056/colossalai/zero/gemini/gemini_optimizer.py#L525,  the PID for other ranks starts appearing on rank-0
Furthermore, after reaching this line: https://github.com/hpcaitech/ColossalAI/blob/2f583c154944b1f00d7a4fb1ce529db9d8595056/colossalai/zero/gemini/gemini_optimizer.py#L593

any Colossalai-ers could help me? Thanks a lot.


bug: ENS image is not showing up

I have many example of account with ENS domains like fireeyesdao.eth or griff.eth where avatar exist in ENS records but it's not showing up on Stamp, check here:
https://snapshotx.xyz/#/sn:0x0041ada9121061198b52ae28edeec8ace7c23f2ba8d66938c129af1a2245701c/delegates
https://app.ens.domains/fireeyesdao.eth
https://app.ens.domains/griff.eth

Seems like 0x839395e20bbB182fa440d08F850E6c7A8f6F0780 is associated to griff.eth, but

https://stamp.fyi/avatar/griff.eth
https://stamp.fyi/avatar/0x839395e20bbB182fa440d08F850E6c7A8f6F0780

Do not yield the same result.
Investigating ...


Allow the footer to be split in several columns

Feature Request
Is your feature request related to a problem or unsupported use case? Please describe.
We want to be able to split the footer in several columns.

Describe the solution you'd like
The number of columns could be determined by the number of pages below the root footer page. Their children would then be the links.

@sampaccoud you mean to determine columns count depending computed multiple from page count ? Or you mean choosing number of columns from page count total (if > 5: two column, if > 10: four column, etc..) ?
By the way, i don't think this is a good idea to let automatically split columns, this should be something statically defined in template and css. Responsive behavior will be hard to implement correctly with dynamical number of columns.

@sampaccoud i just looked on ongoing homepage mockup, annexes pages is clearly splitted in three columns and don't allow for more (no more space left).

@sveetch what I meant was that today we have the following pages:
Annex
    About
    Sitemap

That renders on one line in the footer: "About   Sitemap"
What we want is the following pages to render in 2 columns:
Annex
    Column 1
        Item 1-1
        Item 1-2
    Column2
        Item 2-1
        Item 2-2

The number of columns in the footer should adapt to the number of pages below "Annex" and it is up to the site administrator to adjust the number of columns to the place left by the css and the length of each pages' title.

This feature was introduced by https://github.com/openfun/richie/pull/836


Homekit cover stays in openning state

Home Assistant release with the issue:

0.96.5
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):

Raspbian / Hass.io
Component/platform:

Homekit
Description of problem:
The cover on the iOS Home App shows "Openning..." instead of "Open"
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

homekit:
  filter:
    include_domains:
      - alarm_control_panel
      - light
      - climate
      - media_player
      - cover
    include_entities:
      - binary_sensor.living_room_motion
  entity_config:
    alarm_control_panel.home_alarm:
      code: !secret alarm_pin

Traceback (if applicable):

Additional information:
Logs: search for cover, they report openning and the number increases then it shows 100.0 open but the iOS UI shows opening
https://pastebin.com/4y6Gjxw5
The cover is the ESPHome platform, the integration is created by ESPHome itself.

I'm experiencing the exact same thing using the Lutron component....the covers stay in a constant "opening..." status in Homekit (incidentally, covers also default to a "Closed" status in Homekit after a reboot of Home Assistant even if they're open, so attempting to change them to open results in them sticking in an "opening..." status).

I have the same problem in a time_base cover with esphome. In HA the open percentage shows ok, but in HK only appear closed/opened. If I manage the cover with HK, the states changes to "Openning" or "Closing".


Added md046 sentences-per-line

Complains if a line contains a second period followed by a space and an [A-Z|a-z] character. Ignores ``` and ` code blocks.
My build locally fails with 76 commits on master, so I couldn't easily figure out how to add tests. Filed #127.

Coverage remained the same at 100.0% when pulling 56643d90db3fb655d54006ca88b9c20844e57d6d on JoshuaKGoldberg:sentences-per-line into 2710c375b3c9b9b6531d546b667f50f7d0c956f2 on DavidAnson:master.

This looks like it might be a contentious rule, reporting failures in most scenarios (think of it like a significant breaking change). I agree with the sentiment and often use the "one sentence per line" practice myself, but experience has taught me to be careful about making the linter too opinionated.
What I'd prefer is to offer this as a custom rule. That allows anyone who wants to opt in without imposing it on everyone. Here's the documentation for custom rules, they're the same as internal rules (though they don't have access to all the helper methods): https://github.com/DavidAnson/markdownlint/blob/master/doc/CustomRules.md

That sounds good to me, thanks for the documentation! Once I finish that work I'll likely ask about making a list somewhere in this repo of community rules.

Following up: https://github.com/JoshuaKGoldberg/sentences-per-line exists. 😄


Hidden "Down" properties not working correctly

It seems that the down property is not working correctly for the  element. Seems like the xs sm md lg xl are shifted by one. (for  element only! casual breakpoints in style, etc.. works as expected)
Current Behavior 😯
lgDown works when the screen size is less than <= 1920
mdDown works when the screen size is less than <= 1280
and so on..
Expected Behavior 🤔
lgDown works when the screen size is less than <= 1280
mdDown works when the screen size is less than <= 960
and so on..
Your Environment 🌎

Tech
Version

Material-UI
v4.8.3

React
16.12.0

Browser
Chrome

TypeScript
yes

etc.

See #13448, we plan to change the behavior in v5.


Helm template for multiple nginx domain template

Hello Team,
Hope you are fine..
I  am working on one Kubernetes application and we are using helm chart for multiple environment .
I have nginx running on a pod and nginx having five domain for each environment . These nginx domain are different for every environment. we decide to mount these nginx configuration through configmap.
We need helm template for this scenerio.
Could you pls  share template to fix .
Pls revert if any further info required.

If you need assistance with specific charts you should reach out those chart authors.


Improperly Handled SSL Labs Error

User error report:

I just received another yawast error, this time on a different domain.  Both issues were encountered on version v0.8.0b6.

       Completed (Elapsed: 0:00:42.072029 - Peak Memory: 62.58MB)
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/yawast/commands/scan.py", line 46, in start
    ssl_labs.scan(session)
  File "/usr/local/lib/python3.7/site-packages/yawast/scanner/cli/ssl_labs.py", line 28, in scan
    api.start_scan(session.domain)
  File "/usr/local/lib/python3.7/site-packages/yawast/scanner/plugins/ssl_labs/api.py", line 26, in start_scan
    resp = _analyze(domain, True)
  File "/usr/local/lib/python3.7/site-packages/yawast/scanner/plugins/ssl_labs/api.py", line 67, in _analyze
    errors=str(body["errors"])
ValueError: SSL Labs returned the following error(s): [{'message': 'Running at full capacity. Please try again later.'}]

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/bin/yawast", line 38, in <module>
    main.main()
  File "/usr/local/lib/python3.7/site-packages/yawast/main.py", line 64, in main
    args.func(args, urls)
  File "/usr/local/lib/python3.7/site-packages/yawast/command_line.py", line 152, in command_scan
    scan.start(session)
  File "/usr/local/lib/python3.7/site-packages/yawast/commands/scan.py", line 53, in start
    ssl_internal.scan(session)
  File "/usr/local/lib/python3.7/site-packages/yawast/scanner/cli/ssl_internal.py", line 132, in scan
    server_info, compression_plugin.CompressionScanCommand()
  File "/usr/local/lib/python3.7/site-packages/sslyze/synchronous_scanner.py", line 46, in run_scan_command
    return plugin.process_task(server_info, scan_command)
  File "/usr/local/lib/python3.7/site-packages/sslyze/plugins/compression_plugin.py", line 56, in process_task
    ssl_connection.connect()
  File "/usr/local/lib/python3.7/site-packages/sslyze/utils/ssl_connection.py", line 96, in connect
    self.do_pre_handshake(network_timeout)
  File "/usr/local/lib/python3.7/site-packages/sslyze/utils/ssl_connection.py", line 80, in do_pre_handshake
    sock = self._socket_helper.create_connection(final_timeout)
  File "/usr/local/lib/python3.7/site-packages/sslyze/utils/connection_helpers.py", line 36, in create_connection
    sock = socket.create_connection((self._server_ip_addr, self._server_port), timeout=timeout)
  File "/usr/local/Cellar/python/3.7.4/Frameworks/Python.framework/Versions/3.7/lib/python3.7/socket.py", line 727, in create_connection
    raise err
  File "/usr/local/Cellar/python/3.7.4/Frameworks/Python.framework/Versions/3.7/lib/python3.7/socket.py", line 716, in create_connection
    sock.connect(sa)
ConnectionRefusedError: [Errno 61] Connection refused

This was caused by the following events:

SSL Labs returned an error.
We switched to using SSLyze, so that we can still provide something useful.
SSLyze threw an error.

That last exception wasn't properly handled, and was passed all the way out.


fix generation of phone numbers (domestic/international/mobile)

I realized that PhoneNumberTest almost didn't test anything: it did 10 iterations, but checked that error count is < 25. :)
Now phone numbers are

fully correct for et, bg, mk, md, al, ru
partially correct for most countries (66% errors tolerance)
other countries are marked as FIXME.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.09%. Comparing base (b37c566) to head (e6375c8).
Report is 123 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##               main    #1225      +/-   ##
============================================
- Coverage     92.35%   92.09%   -0.27%
- Complexity     2821     2998     +177
============================================
  Files           292      306      +14
  Lines          5609     5905     +296
  Branches        599      628      +29
============================================
+ Hits           5180     5438     +258
- Misses          275      305      +30
- Partials        154      162       +8

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


pip: do not know how to unpack source archive xxxx.whl

I tried packaging a pip module: https://codeberg.org/raboof/nix-vulnerablecode
... but it fails to unpack the .whl:
      > Using setuptoolsShellHook
       > Sourcing pypa-install-hook
       > Using pypaInstallPhase
       > Sourcing python-imports-check-hook.sh
       > Using pythonImportsCheckPhase
       > Sourcing python-namespaces-hook
       > Sourcing python-catch-conflicts-hook.sh
       > unpacking sources
       > unpacking source archive /nix/store/01nnkk77w2vi7jv9g3yjlmrphyc40wdk-vulnerablecode-33.6.3-py3-none-any.whl
       > do not know how to unpack source archive /nix/store/01nnkk77w2vi7jv9g3yjlmrphyc40wdk-vulnerablecode-33.6.3-py3-none-any.whl

Is it incorrect that this is pointing to a whl, or that it fails to unzip the whl, or is the way this software is packaged not supported by dream2nix?

Is it incorrect that this is pointing to a whl, or that it fails to unzip the whl, or is the way this software is packaged not supported by dream2nix?

This should be supported. For some reasons, your flake end's up with buildPythonPackage.format = "setuptools";, while it works with
  buildPythonPackagesformat = "wheel";

This should be set as a default in https://github.com/nix-community/dream2nix/blob/1c2b47f042d95619d5a4514417220d675bcb0886/modules/dream2nix/pip/default.nix#L58 if mkDerivation.src ends with '.whl', which packages.x86_64-linux.default.config.mkDerivation.src does according to my nix repl.


The text of the Group Buttons overlaps each other..

Describe the bug 📝
I have 2 ContextMenu of group buttons: Hide/Show and Measurement (as shown below).
When I click the Measurement button, the buttons of the Hide/Show group do not hide. Make the text overlap as shown.
I hope the “openbim-components” library will update and resolve this bug!
Thanks so much!

Reproduction ▶
No response
Steps to reproduce 🔢
No response
System Info 💻
openbim-components

Used Package Manager 📦
npm
Error Trace/Logs 📃
No response
Validations ✅

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a IFC.js components issue and not a framework-specific issue. For example, if it's a THREE.js related bug, it should likely be reported to mrdoob/threejs instead.
[X] Check that this is a concrete bug. For Q&A join our Community.
[X] The provided reproduction is a minimal reproducible example of the bug.

This will be worked on during the development of UI Components 2.0

We will release UIComponents 2.0 as a complete separate library and get rid of everything regarding UI from this repo. The new UIComponents are being done from scratch using a different technology.
Will close this issue as it won't be valid since release 1.6.0!


Cannot skip unknown words

In training one cannot skip a word without entering text.
Either add a "Skip" button or allow to leave editText for translation empty.

Added a skip button if empty translation is submitted.


Update Sub Template for New Help

As a response to the Issue #165
Replaced the "Experts only" heading with "Indie Hosts only"
Also replaced the http protocol with https, so as to avoid redirection done by server side and pushing the world towards HTTPS era :smile:

Looks good.
One more change would be for the text description: "These applications provide privacy if you host your own content server. If you don't know what that means, you should not use these apps."

Changed the text as per the suggestion [f6a95e4d....] (https://github.com/jatindhankhar/privly-applications/commit/f6a95e4d6b94b70f6d29fa7252f1e6e061110e7a)

Fixed in https://github.com/privly/privly-applications/commit/7c0c875e8ec3a12db5ea4531de4b10a30990b4e1


Got Waypoint below home warning with v3.1.3

@ashwanisihag can you provide logs or screenshots? Was this in simulation or flying outdoors? Did you check the altitude of your waypoints?

This is not a PX4 release number.

This is qGroundControl number and PX4 with latest firmware.
Regards
On Wed, 12/4/17, Lorenz Meier<EMAIL_ADDRESS>wrote:
Subject: Re: [PX4/Firmware] Got Waypoint below home warning with v3.1.3 (#7023)
To: "PX4/Firmware"<EMAIL_ADDRESS>Cc: "ashwanisihag"<EMAIL_ADDRESS>"Mention"<EMAIL_ADDRESS>Date: Wednesday, 12 April, 2017, 5:14 AM
This is not a PX4 release
number.
—
You are receiving this because you were mentioned.
Reply to this email directly, view
it on GitHub, or mute
the thread.

Hi,
I was flying outdoor, set all altitudes as 8 meters, suddenly when it was approaching way point first, it landed and warning came that "waypoint below home".
Will test once more to duplicate it.
Regards

On Tue, 11/4/17, Daniel Agar<EMAIL_ADDRESS>wrote:
Subject: Re: [PX4/Firmware] Got Waypoint below home warning with v3.1.3 (#7023)
To: "PX4/Firmware"<EMAIL_ADDRESS>Cc: "ashwanisihag"<EMAIL_ADDRESS>"Mention"<EMAIL_ADDRESS>Date: Tuesday, 11 April, 2017, 9:53 PM
@ashwanisihag can you
provide logs or screenshots? Was this in simulation or
flying outdoors? Did you check the altitude of your
waypoints?
—
You are receiving this because you were mentioned.
Reply to this email directly, view
it on GitHub, or mute
the thread.


Do I need to download the blockchain if I have already running full bitcoin node?

Hey guys,
I have fully synced bitcoin blockchain on my server. As I found out the omnicored uses bitcoin blockchain. So the question is do I have to download blockchain again If I already have downloaded full bitcoin blockchain?
Thank you!

@dexX7 getnetworkinfo rpc returns 'subversion': '/Satoshi:0.14.99/'

@skinderis: that should work. You can point Omni Core to use your old datadir, however, you must have the "txindex" option enabled.


Add a missing comma

I second this ! Had the same issue today, adding the comma fixed it. Seems to have been added during the last commit

Thanks for the PR !


Throw the base exception in the serializer which also takes care of the inner exception

[clabot:check]

@confluentinc It looks like @danielmarbach just signed our Contributor License Agreement. :+1:
Always at your service,
clabot

No interest in this contribution?

Can you elaborate on why you why throwing the base exception is better?
IIRC, it's the way it is so you don't get nested Aggregate exceptions (for convenience). If you throw the base exception, you'll need to traverse to get the exception you want (i believe). But maybe you sometimes want the base exception. I don't understand the scenario for that, but as you're requesting the change, I'm guessing there is a reason.
Also, this is a breaking change, so we have to be very careful how we resolve this if there is an issue.

This is already a long time I go, so my memories might no longer be entirely correct. I believe I introduced this change because the actual root exception was masked by throwing the inner exception. With the GetBaseException method the aggregate exception is properly traversed until the actual root exception is found (even if the inner exception is another aggregate exception) and then that exception is thrown.
The example in the documentation shows that behavior
https://docs.microsoft.com/en-us/dotnet/api/system.exception.getbaseexception?view=net-6.0

A chain of exceptions consists of a set of exceptions such that each exception in the chain was thrown as a direct result of the exception referenced in its InnerException property. For a given chain, there can be exactly one exception that is the root cause of all other exceptions in the chain. This exception is called the base exception and its InnerException property always contains a null reference.
For all exceptions in a chain of exceptions, the GetBaseException method must return the same object (the base exception).
Use the GetBaseException method when you want to find the root cause of an exception but do not need information about exceptions that may have occurred between the current exception and the first exception.

I'd argue that is the thing a consumer of the exception is actually interested in to be able to quickly troubleshoot what is going on. On top of that I would say it might even make sense to combine it with ExceptionDispatchInfo to properly freeze the stack trace.

Closing because of the lack of interest or interaction.


Add yamllint verification test

This PR adds yaml verification via yamllint. This will be used to validate plugin yamls, when users opens a PR making changes under plugins directory.
This change will be used by https://github.com/openshift/release/pull/42139

/cc @ingvagabund


Angular material local linking with yarn

Bug, feature request, or proposal:
Make yarn local linking work with Angular Material
What is the expected behavior?
Using yarn link inside a folder of Angular Material monorepo should register correctly for local linking.
Then using yarn link @angular/<cdk/material/...> should correctly link the dependency and ng serve should work without any errors.
What is the current behavior?
Entering single folders and using yarn link links the folder itself.
This is a problem because the packages released ARE NOT the plain folder, but are generated with gulp build-aot:release-packages (or single commands gulp <material/cdk/...>:build-release).
Running that command and manually copying the generated folders from dist/releases folder will do the job but it's a pretty awful solution.
There are a lot of gulp tasks not mentioned inside DEV_ENVIRONMENT and which should probably be.
For example gulp cdk:build-release, which is the CDK counterpart of the material task, and gulp build-aot:release-packages which builds all packages (material, cdk, cdk-experimental, material-experimental, material-moment-adapter and material-examples).
It's not possible to link dist folders with yarn, because there are no package.json files into the distribution from which to take the package name (or, at least, I think that's the reason)
What is the use-case or motivation for changing an existing behavior?
Enabling a simpler way to test in local environment will help to try out the changes directly on complex projects where components are used, instead of trying a PR and waiting until following release or relying only on the ad-hoc and simpler examples inside the repo.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 7.x
Material 7.x

For what it's worth, we publish each commit that is merged to https://github.com/angular/material2-builds which you can use to try out particular changes.

That's a useful info, thanks.
But that can be used only after the merge and this can literally take ages.
Example: last month I contributed with stepper label implementation of positioning. In examples it worked ok, then when it was released I found out that in real case scenario it had a bug (really simple to spot, except that on examples page).
Now I'm working on fixing nested table sticky rows on Edge, I made it work on example page, then I copied release packages onto my real world project and some basic things don't work.
And nobody is actually answering to the PR I made (this is not a critic, just a fact) so I can't even hope to get it merged at some point.
Only way for me is working and trying it locally, by copy/paste atm.
I don't know if it's possible to define a different folder target for yarn link in package.json, I'm actually searching for that kind of option to make linking easier

It's not possible to link dist folders with yarn, because there are no package.json files into the distribution from which to take the package name (or, at least, I think that's the reason)

If you run the release gulp tasks, there should be package.json files in the release output. So, you should be able to do yarn link inside of those?

Seems like I was wrong on this, I tried to link them from dist folder some days ago and didn't work, maybe I did something wrong, I'll retry tomorrow, ty!
Maybe just adding this kind of information to DEV_ENVIRONMENT file can be enough for now, so other people don't have to manually look into the code to understand how to generate and link a package locally.
The whole point of this issue was actually to document how to do that for other people/future me, so I'm already happy to have an answer now :P

I tryed linking from inside release folders and linking succeeded.
But then, when compiling, this error fired off for every single module imported from cdk or material packages:
Module not found: Error: Can't resolve '@angular/material/<module>' in 'C:\...\material2\dist\releases\material\esm5' ERROR in C:/.../material2/dist/releases/material/esm5/material.es5.js
Ideas on what it could be?

Hmm, I can't think of any reason why this doesn't work. I can try tomorrow and see if it works for me.
Are you just using a CLI project?

@IlCallo Sorry for the late response. I've looked into it and even tried linking the Github snapshot build repositories, but those didn't work either.
Since they work if you just add them like a normal package, but fail with yarn link, I feel like Yarn's link feature does not properly handle multiple package.json files in a linked package (or secondary entry-points).
As I think there is nothing we could do about and it would never become a high priority, I will be closing that issue. Happy to chat more about it here though.

I've opened a new issue on yarn repository for this, let's see if they can help us out...


Is there an inherent dependency on redux-thunk in redux-modules?

The docs specifically mention that the redux-thunk middleware is expected to be running.
Does this mean that using redux-modules with redux-saga is not possible/advisable?

There is a dependency on thunk, but that does not exclude it from being used with redux-saga. We use redux saga alongside


is it possible to access data from other columns from autocomplete?

Hi, I have two columns in my aggrid.
One with the autocomplete and other column (hidden) with ID.
I need get data from the column "ID" to call the API in my autocomplete and show the data right there.

Thanks

Yes, but it have nothing to do with the cellEditor itself. You need to create a scope where this data retrieved, you will be able to pass this data into the fetch function scope.
You probably want to check an Grid Api and Editing Api documentation.
I close this issue since it's not related to the plugin itself.


clouddrive2: 0.8.3 -> 0.8.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for clouddrive2 is: Multi-cloud drives management tool supporting mounting cloud drives locally
meta.homepage for clouddrive2 is: https://www.clouddrive2.com
meta.changelog for clouddrive2 is: https://github.com/cloud-fs/cloud-fs.github.io/releases/tag/v0.8.5
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.8.5 with grep in /nix/store/nvjcp4igyr17awb2iz7k4jw0hyhkx9l8-clouddrive2-0.8.5
found 0.8.5 in filename of file in /nix/store/nvjcp4igyr17awb2iz7k4jw0hyhkx9l8-clouddrive2-0.8.5

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

clouddrive2

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/nvjcp4igyr17awb2iz7k4jw0hyhkx9l8-clouddrive2-0.8.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A clouddrive2 https://github.com/r-ryantm/nixpkgs/archive/168441ba614d16039edc0f9a400e8181685aed43.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/168441ba614d16039edc0f9a400e8181685aed43#clouddrive2

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/nvjcp4igyr17awb2iz7k4jw0hyhkx9l8-clouddrive2-0.8.5
ls -la /nix/store/nvjcp4igyr17awb2iz7k4jw0hyhkx9l8-clouddrive2-0.8.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

clouddrive2

Maintainer pings
cc @L-Trump for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge