text:
Something goes wrong!

I haven't isolated what I did to cause this.
Using this commit: https://github.com/shuppet/p6-api-discord/tree/093a7c84e0e38716463a5bddcc2496a015a9c78b
$ raku --ll-exception -Ilib -MAPI::Discord
No such method 'raku' for invocant of type '::?CLASS'
   at SETTING::src/core.c/Exception.pm6:62  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/CORE.c.setting.moarvm:throw)
 from SETTING::src/core.c/Exception.pm6:2808  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/CORE.c.setting.moarvm:)
 from gen/moar/BOOTSTRAP/v6c.nqp:3888  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/BOOTSTRAP/v6c.moarvm:)
 from SETTING::src/core.c/Signature.pm6:137  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/CORE.c.setting.moarvm:gistperl)
 from SETTING::src/core.c/Signature.pm6:148  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/CORE.c.setting.moarvm:raku)
 from SETTING::src/core.c/Mu.pm6:706  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/CORE.c.setting.moarvm:raku)
 from gen/moar/Metamodel.nqp:3622  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Metamodel.moarvm:apply)
 from gen/moar/Metamodel.nqp:3808  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Metamodel.moarvm:compose)
 from gen/moar/World.nqp:3354  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/World.moarvm:)
 from gen/moar/World.nqp:5514  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/World.moarvm:)
 from gen/moar/World.nqp:5522  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/World.moarvm:ex-handle)
 from gen/moar/World.nqp:3353  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/World.moarvm:pkg_compose)
 from gen/moar/Actions.nqp:3245  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Actions.moarvm:package_def)
 from gen/moar/stage2/QRegex.nqp:1545  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/QRegex.moarvm:!cursor_pass)
 from gen/moar/Grammar.nqp:2207  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Grammar.moarvm:package_def)
 from <unknown>:1  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Grammar.moarvm:package_declarator:sym<class>)
 from gen/moar/stage2/QRegex.nqp:1644  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/QRegex.moarvm:!protoregex)
 from <unknown>:1  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Grammar.moarvm:package_declarator)
 from <unknown>:1  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Grammar.moarvm:term:sym<package_declarator>)
 from gen/moar/stage2/QRegex.nqp:1644  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/QRegex.moarvm:!protoregex)
 from <unknown>:1  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Grammar.moarvm:term)
 from gen/moar/Grammar.nqp:3685  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Grammar.moarvm:termish)
 from gen/moar/stage2/NQPHLL.nqp:1208  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:EXPR)
 from gen/moar/Grammar.nqp:3728  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Grammar.moarvm:EXPR)
 from gen/moar/Grammar.nqp:957  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Grammar.moarvm:statement)
 from gen/moar/Grammar.nqp:885  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Grammar.moarvm:statementlist)
 from gen/moar/stage2/NQPHLL.nqp:1430  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:LANG)
 from gen/moar/Grammar.nqp:1323  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Grammar.moarvm:FOREIGN_LANG)
 from gen/moar/Grammar.nqp:833  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Grammar.moarvm:comp_unit)
 from gen/moar/Grammar.nqp:555  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Grammar.moarvm:TOP)
 from gen/moar/stage2/QRegex.nqp:2211  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/QRegex.moarvm:parse)
 from gen/moar/stage2/NQPHLL.nqp:2262  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:parse)
 from gen/moar/stage2/NQPHLL.nqp:2180  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:execute_stage)
 from gen/moar/stage2/NQPHLL.nqp:2213  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:run)
 from gen/moar/stage2/NQPHLL.nqp:2205  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:)
 from gen/moar/stage2/NQPHLL.nqp:2200  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:compile)
 from gen/moar/stage2/NQPHLL.nqp:1883  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:eval)
 from gen/moar/stage2/NQPHLL.nqp:2118  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:evalfiles)
 from gen/moar/stage2/NQPHLL.nqp:2078  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:command_eval)
 from gen/moar/Compiler.nqp:55  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Compiler.moarvm:command_eval)
 from gen/moar/stage2/NQPHLL.nqp:2003  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:command_line)
 from gen/moar/perl6.nqp:127  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/perl6.moarvm:MAIN)
 from gen/moar/perl6.nqp:92  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/perl6.moarvm:<mainline>)
 from <unknown>:1  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/perl6.moarvm:<main>)
 from <unknown>:1  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/perl6.moarvm:<entry>)

   at SETTING::src/core.c/Exception.pm6:62  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/CORE.c.setting.moarvm:throw)
 from SETTING::src/core.c/control.pm6:202  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/CORE.c.setting.moarvm:die)
 from SETTING::src/core.c/control.pm6:190  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/CORE.c.setting.moarvm:die)
 from SETTING::src/core.c/CompUnit/PrecompilationRepository.pm6:327  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/CORE.c.setting.moarvm:precompile)
 from SETTING::src/core.c/CompUnit/PrecompilationRepository.pm6:215  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/CORE.c.setting.moarvm:precompile)
 from SETTING::src/core.c/CompUnit/PrecompilationRepository.pm6:46  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/CORE.c.setting.moarvm:try-load)
 from SETTING::src/core.c/CompUnit/Repository/FileSystem.pm6:79  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/CORE.c.setting.moarvm:)
 from SETTING::src/core.c/CompUnit/Repository/FileSystem.pm6:73  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/CORE.c.setting.moarvm:need)
 from gen/moar/World.nqp:1481  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/World.moarvm:load_module)
 from gen/moar/World.nqp:1431  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/World.moarvm:do_pragma_or_load_module)
 from gen/moar/Grammar.nqp:1295  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Grammar.moarvm:statement_control:sym<use>)
 from gen/moar/stage2/QRegex.nqp:1644  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/QRegex.moarvm:!protoregex)
 from <unknown>:1  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Grammar.moarvm:statement_control)
 from gen/moar/Grammar.nqp:957  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Grammar.moarvm:statement)
 from gen/moar/Grammar.nqp:885  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Grammar.moarvm:statementlist)
 from gen/moar/stage2/NQPHLL.nqp:1430  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:LANG)
 from gen/moar/Grammar.nqp:1323  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Grammar.moarvm:FOREIGN_LANG)
 from gen/moar/Grammar.nqp:833  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Grammar.moarvm:comp_unit)
 from gen/moar/Grammar.nqp:555  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Grammar.moarvm:TOP)
 from gen/moar/stage2/QRegex.nqp:2211  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/QRegex.moarvm:parse)
 from gen/moar/stage2/NQPHLL.nqp:2262  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:parse)
 from gen/moar/stage2/NQPHLL.nqp:2180  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:execute_stage)
 from gen/moar/stage2/NQPHLL.nqp:2213  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:run)
 from gen/moar/stage2/NQPHLL.nqp:2205  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:)
 from gen/moar/stage2/NQPHLL.nqp:2200  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:compile)
 from gen/moar/stage2/NQPHLL.nqp:1883  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:eval)
 from gen/moar/stage2/NQPHLL.nqp:2118  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:evalfiles)
 from gen/moar/stage2/NQPHLL.nqp:2078  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:command_eval)
 from gen/moar/Compiler.nqp:55  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Compiler.moarvm:command_eval)
 from gen/moar/stage2/NQPHLL.nqp:2003  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:command_line)
 from gen/moar/perl6.nqp:127  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/perl6.moarvm:MAIN)
 from gen/moar/perl6.nqp:92  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/perl6.moarvm:<mainline>)
 from <unknown>:1  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/perl6.moarvm:<main>)
 from <unknown>:1  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/perl6.moarvm:<entry>)

   at SETTING::src/core.c/Exception.pm6:62  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/CORE.c.setting.moarvm:throw)
 from SETTING::src/core.c/control.pm6:202  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/CORE.c.setting.moarvm:die)
 from SETTING::src/core.c/control.pm6:190  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/CORE.c.setting.moarvm:die)
 from SETTING::src/core.c/CompUnit/PrecompilationRepository.pm6:327  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/CORE.c.setting.moarvm:precompile)
 from SETTING::src/core.c/CompUnit/PrecompilationRepository.pm6:215  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/CORE.c.setting.moarvm:precompile)
 from SETTING::src/core.c/CompUnit/PrecompilationRepository.pm6:46  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/CORE.c.setting.moarvm:try-load)
 from SETTING::src/core.c/CompUnit/Repository/FileSystem.pm6:79  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/CORE.c.setting.moarvm:)
 from SETTING::src/core.c/CompUnit/Repository/FileSystem.pm6:73  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/CORE.c.setting.moarvm:need)
 from gen/moar/World.nqp:1481  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/World.moarvm:load_module)
 from gen/moar/World.nqp:1431  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/World.moarvm:do_pragma_or_load_module)
 from gen/moar/World.nqp:816  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/World.moarvm:comp_unit_stage1)
 from gen/moar/Grammar.nqp:833  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Grammar.moarvm:comp_unit)
 from gen/moar/Grammar.nqp:555  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Grammar.moarvm:TOP)
 from gen/moar/stage2/QRegex.nqp:2211  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/QRegex.moarvm:parse)
 from gen/moar/stage2/NQPHLL.nqp:2262  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:parse)
 from gen/moar/stage2/NQPHLL.nqp:2180  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:execute_stage)
 from gen/moar/stage2/NQPHLL.nqp:2213  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:run)
 from gen/moar/stage2/NQPHLL.nqp:2205  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:)
 from gen/moar/stage2/NQPHLL.nqp:2200  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:compile)
 from gen/moar/stage2/NQPHLL.nqp:1883  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:eval)
 from gen/moar/Compiler.nqp:94  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Compiler.moarvm:interactive)
 from gen/moar/stage2/NQPHLL.nqp:2078  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:command_eval)
 from gen/moar/Compiler.nqp:55  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/lib/Perl6/Compiler.moarvm:command_eval)
 from gen/moar/stage2/NQPHLL.nqp:2003  (/home/adouglas/src/rakudo-2020.01/bin/../share/nqp/lib/NQPHLL.moarvm:command_line)
 from gen/moar/perl6.nqp:127  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/perl6.moarvm:MAIN)
 from gen/moar/perl6.nqp:92  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/perl6.moarvm:<mainline>)
 from <unknown>:1  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/perl6.moarvm:<main>)
 from <unknown>:1  (/home/adouglas/src/rakudo-2020.01/bin/../share/perl6/runtime/perl6.moarvm:<entry>)

I've removed all mentions of ::?CLASS from that compilation area and it has not changed the result.
https://github.com/shuppet/p6-api-discord/blob/8cc714c8ae9d905d35d2c76005312a17a7563874/lib/API/Discord/Channel.pm6

Removing the use of Object::Delayed shows me: Attribute $!api not declared in class API::Discord::Channel::API::Discord::Channel::ButReal
I assume this is the actual error and O:D is getting upset with it.

This seems like a raku bug, which is probably just a badly-worded error message (or rather, an error message from another error message).

repo: lizmat/Object-Delayed


text:
dont use delta-space when possible

this makes it so that normal prompts will have identical results whether the extension is enabled or not.

1girl (2 latents, 1 cond and 1 uncond) and 1girl AND_PERP 1boy:0 (3 latents, 2 conds and 1 uncond) give different results on my system. The reason is that, apparently, the first Conv2d layer encountered in the forward function of the model gives different results depending on whether it is given a batch of 3 tensors or 2.
This isn't something I can fix. It has implications for any processing that changes the batch size. This extension heavily relies on a dynamic unet batch size.

The reason is that, apparently, the first Conv2d layer encountered in the forward function of the model (the first processed h) gives different results depending on whether it is given a batch of 3 tensors or 2. The error propagates to the rest of the unet layers, and then the rest of the denoising steps. It gives a drastically different image as a result.

If I may ask for learning purposes, how did you determine this? (Tool that you used or method for testing, external source that you consulted, etc)?
Does it depend on the sampler, or matter if we disable the A1111 setting that batches cond and uncond?

If I may ask for learning purposes, how did you determine this?

I debugged in the code. Exact same input noise 2x gives slight precision differences from exact same input 3x.
I tested in an isolated environment to make sure (asked chatgpt because I was lazy):
import torch
import torch.nn as nn

# Creating a batch of random tensors (e.g., a batch of 5 images, each with 3 channels, 64x64 pixels)
batch_size = 5
channels = 3
height = width = 64
tensors = torch.randn(batch_size, channels, height, width)

# Defining a 2D convolutional layer
conv_layer = nn.Conv2d(in_channels=channels, out_channels=6, kernel_size=3, stride=1, padding=1)

# Applying the convolutional layer to the entire batch
batch_result = conv_layer(tensors)

# Applying the convolutional layer to each tensor individually
individual_results = torch.stack([conv_layer(t.unsqueeze(0)) for t in tensors])

# Checking if the results are exactly the same
result_comparison = torch.nonzero(batch_result.squeeze() == individual_results.squeeze())

print((result_comparison, result_comparison.shape))

Which prints
(tensor([[ 0,  0,  0,  1],
         [ 0,  0,  0,  2],
         [ 0,  0,  0,  3],
         ...,
         [ 4,  5, 63, 60],
         [ 4,  5, 63, 61],
         [ 4,  5, 63, 62]]),
 torch.Size([93901, 4]))

Does it depend on the sampler, or matter if we disable the A1111 setting that batches cond and uncond?

Sampler shouldn't matter, unless a sampler changes the batch size. Batch cond uncond should change the result, but when I tested it becomes automatically enabled even when I uncheck it and save settings, as soon as I generate an image. Maybe I have an extension that messes with this setting, I haven't investigated the auto-enable of batch_cond_uncond.

Sampler shouldn't matter, unless a sampler changes the batch size. Batch cond uncond should change the result, but when I tested it becomes automatically enabled even when I uncheck it and save settings, as soon as I generate an image. Maybe I have an extension that messes with this setting, I haven't investigated the auto-enable of batch_cond_uncond.

1girl (2 latents, 1 cond and 1 uncond) and 1girl AND_PERP 1boy:0 (3 latents, 2 conds and 1 uncond) give different results on my system even though they should be identical.
The reason is that, apparently, the first Conv2d layer encountered in the forward function of the model (the first processed h) gives different results depending on whether it is given a batch of 3 tensors or 2. The error propagates to the rest of the unet layers, and then the rest of the denoising steps. It gives a drastically different image as a result.

I think batch_cond_uncond is the issue but I can't reproduce a drastic difference like you described. Even when I crank CFG up to 20 I get only very slight difference between a vs. a AND_PERP b :0.
When I disable batch_cond_uncond, the images are identical.
I had all other extensions disabled while testing, and I tried both empty and non-empty negative prompts.

Even when I crank CFG up to 20 I get only very slight difference between a vs. a AND_PERP b :0

To be clear, by drastically different images, I don't mean to say that they have different content, but that practically all pixel values seem to change at least a lityle bit. I think you reproduced the issue.
For batch cond uncond, if you disable it under optimizations, then generate, then apply settings without explicitly checking or unchecking batch cond uncond, do you see the seeting being applied again? This is how I determined that it was automatically enabled when clicking on generate.

For batch cond uncond, if you disable it under settings>optimizations, then generate, then go back to settings and apply settings without explicitly checking or unchecking batch cond uncond, do you see the setting being applied again? This is how I determined that it was automatically enabled when clicking on generate.

Nope, it stays disabled for me, and only when I manually re-enable it do the differences return.
If it still happens even once other extensions are enabled, maybe you have the old CLI version of that setting in your launch script and that's re-enabling it? (Just a dumb guess, I haven't actually looked at how they implemented the change to it being a WebUI setting... my gut feeling is another extension is more likely responsible)

source: gharchive/pull-request

authors: ljleb wbclark

repo: ljleb/sd-webui-neutral-prompt

license: MIT

license_type: permissive

license_source: github-api


text:
Edit data in table after query --

Table should show what data set is being viewed/edit
Table should have a default sort order.
In multi-page tables, screen should show what page we are on ( 1 of 47 etc)
Sort should sort the ENTIRE table, not just the displayed page.

all complete

source: gharchive/issue

authors: BoatrightTBC ljramones

repo: ljramones/trips


text:
Failed to load Colonize.chv

number format exception while loading this files
terranrepublicviewer.log
ErrorLoadingCOLONIZE.CHV.txt

file was corrupted so unable to parse
put in more error handling to show why

I am going to try my version of the filed, see if it works in CHViewer. If it does, that means one of two things:

the file was simply a corrupted example and my version could be used (which is important for me in terms of invested development in terms of bakcground)
there might be something else going on.

Ok
Sent from ProtonMail Mobile
On Sat, Sep 12, 2020 at 20:33, cegannon1 notifications@github.com wrote:

I am going to try my version of the filed, see if it works in CHViewer. If it does, that means one of two things:

the file was simply a corrupted example and my version could be used (which is important for me in terms of invested development in terms of bakcground)
there might be something else going on.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.

Well, this is still weirder. I have gone through all my old .chv files on all my old machines and in all my old archives. Nada. Am sending a few that may or may not already be among those you have, if you could please check?


text:
CDATA support for RSS description was added

RSS allows to use CDATA blocks (proof), so I offer to add the optional parameter type to the description() function (as in content()).

Hi woxcab,
I am hesitant to merge this because of the related ATOM text fields which also have an attribute called type which has another meaning entirely. This attribute is not supported in feedgen yet but it it will ever be added, things might get really confusing.
My suggestion would be to just name the argument cdata which would be a not so nice quick fix which I nevertheless would accept since it should not harm.
Since all the ATOM text fields and probably also some other RSS fields (not sure about that; would have to check) also may contain CDATA, and could have the ATOM types linked above, a proper way would be to add a new text type class, supporting CDATA as well as the different types possible for these fields (and possibly even do the encoding?). But I fear that I do not have the time to implement that in the near future.
Please let me know if you disagree.
Regards,
Lars

Hi woxcab,
I am hesitant to merge this because of the related ATOM text fields which also have an attribute called type which has another meaning entirely. This attribute is not supported in feedgen yet but it it will ever be added, things might get really confusing.
My suggestion would be to just name the argument cdata which would be a not so nice quick fix which I nevertheless would accept since it should not harm.
Since all the ATOM text fields and probably also some other RSS fields (not sure about that; would have to check) also may contain CDATA, and could have the ATOM types linked above, a proper way would be to add a new text type class, supporting CDATA as well as the different types possible for these fields (and possibly even do the encoding?). But I fear that I do not have the time to implement that in the near future.
Please let me know if you disagree.
Regards,
Lars

Hi Lars.
What do you mean by text type class?

There are several fields in ATOm (e.g , , , and ) (and I suspect also in RSS feeds) which could have CDATA entries as well as having several different content types like text or xhtml.
One possible way to handle this is to add support for this to every field, using a dictionary. This is basically what this patch is doing, though for one RSS field only. A differnt idea would be to add a general Python class to handle all this. It would still be necessary to add the arguments to all the setter functions but we would have a similar handling of content for these fields. I would add a cdata field as well as the type field taken from the ATOM specs. Possibly, even an optional autoencoding property could be added which would then ensure that HTML/XML entities are encoded if necessary, …
But that is obviously a bit more work and I suspect that I will not find the time in the near future to do this. That is why I said that I would accept this patch with only the argument name changed so that it does not get confused with the ATOM type attribute if it is added at some point. You should not suffer from my lack of time ;-P And if at some point I have the time to work on this, the cdata argument could still be used.

Oh. I cannot imagine implementation details for class-based way, so I abstain from this.
P.S.  CDATA possibly can be used only for description in the RSS (e.g.  cannot be used for title, if believe to w3c validator).

Is there any update on this? If not I can respin the patch to adjust based on woxcab's comments.

authors: lkiesow mtreinish woxcab

repo: lkiesow/python-feedgen


text:
🛑 신세계L&B www.shinsegae-lnb.com is down

In cb7b26b, 신세계L&B www.shinsegae-lnb.com (http://www.shinsegae-lnb.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 신세계L&B www.shinsegae-lnb.com is back up in 9414efc.

repo: lksjames/monitoring


text:
🛑 까사미아 www.guud.com is down

In a952075, 까사미아 www.guud.com (http://www.guud.com) was down:

HTTP code: 503
Response time: 977 ms

Resolved: 까사미아 www.guud.com is back up in cd3a8fa.


text:
[Bug] - I cannot install this in Windows 11 Pro using Anaconda Prompt - I get an error "solving environment"

Describe the bug
When running the 3rd step/command from the steps for Windows install:   'conda install pytorch torchvision torchaudio pytorch-cuda=11.6 -c pytorch -c nvidia'
I get this error:

To Reproduce
Steps to reproduce the behavior:

Open Anacondo Prompt
conda create -n sd-inf python=3.10'
conda activate sd-inf
ERROR AS PER ABOVE (image)
Weep tears of frustration and repeat steps in vain.

Expected behavior
I expected the Windows setup guide to guide me through installing this and not encountering this error...
Screenshots
See attached error
Desktop (please complete the following information):

OS: Windows 11 Pro
Browser I use Chrome, Edge, and Firefox

Additional context
Any help is appreciated; I have a 4090 card and really want to maximize my experience with this once it is working; however I can... thank you.

Anyone?


text:
Change Background for PM hours in Clock activity

Fixes part of #921
Updated Background to Black and boundary to white for PM hours.

That's the idea but the background should be change only in 12/24 mode.

That's the idea but the background should be change only in 12/24 mode.

When 12/24 mode is clicked it shows 24 hours on Clock like this:

Can you please explain whether we need it when Clock is showing upto 24 hours as shown above or when it is showing only upto 12 hours.
I think when it's in 12 hours mode we have to apply these changes and in 24 hours mode background will always remain white. Please confirm.

When 12/24 mode is clicked it shows 24 hours on Clock like this:

Can you please explain whether we need it when Clock is showing upto 24 hours as shown above or when it is showing only upto 12 hours.
I think when it's in 12 hours mode we have to apply these changes and in 24 hours mode background will always remain white. Please confirm.

Changes made:

Background will remain white in 24 hours mode and white/black in 12 hours mode.
Time shown at the bottom will be updated in AM/PM in 12 hours mode and remain same in 24 hours mode.

Preview of changes:

If these changes look good to you, I will update the PR.

Changes made:

Background will remain white in 24 hours mode and white/black in 12 hours mode.
Time shown at the bottom will be updated in AM/PM in 12 hours mode and remain same in 24 hours mode.

Preview of changes:

If these changes look good to you, I will update the PR.

Sounds good.
BTW as mentioned at https://github.com/llaske/sugarizer/issues/921
24h mode should be use also to:

Allow to pass to AM and PM when rotating the clock arrows
Ask questions for AM and PM in play mode

Sounds good.
BTW as mentioned at https://github.com/llaske/sugarizer/issues/921
24h mode should be use also to:

Allow to pass to AM and PM when rotating the clock arrows
Ask questions for AM and PM in play mode

Regarding:

Allow to pass to AM and PM when rotating the clock arrows

I have toggled AM and PM whenever the clock passes angle 0. But in that case, it is only updating from AM to PM or PM to AM when the drag is smooth so that the clock is able to detect when the angle becomes 0.
Preview of what I explained above:

I am searching for a better alternative to it. If you can help me with what else we can do, it will help me a lot.
Regarding:

Ask questions for AM and PM in play mode

I didn't get you exactly what we need for this. Do we just need to add AM and PM in the bottom time when in play mode or do we need any changes in Clock also?
Like for both 5:00:00 AM and 5:00:00 PM, we have to drag the hands at 5'o clock if I am correct.

Regarding:

Allow to pass to AM and PM when rotating the clock arrows

I have toggled AM and PM whenever the clock passes angle 0. But in that case, it is only updating from AM to PM or PM to AM when the drag is smooth so that the clock is able to detect when the angle becomes 0.
Preview of what I explained above:

I am searching for a better alternative to it. If you can help me with what else we can do, it will help me a lot.
Regarding:

Ask questions for AM and PM in play mode

I didn't get you exactly what we need for this. Do we just need to add AM and PM in the bottom time when in play mode or do we need any changes in Clock also?
Like for both 5:00:00 AM and 5:00:00 PM, we have to drag the hands at 5'o clock if I am correct.

@saurabhhere for toggling AM/PM in set time mode, I would suggest suggest you to toggle it wrt the time ( timeToBeDisplayed ) that has been calculated already via the angles see here. so use timeToBeDisplayed rather than handAngles directly e.g. toggle whenver it passes hour 12 rather than angle 0.

@saurabhhere for toggling AM/PM in set time mode, I would suggest suggest you to toggle it wrt the time ( timeToBeDisplayed ) that has been calculated already via the angles see here. so use timeToBeDisplayed rather than handAngles directly e.g. toggle whenver it passes hour 12 rather than angle 0.

@prakashujjwal1010 If I use timeToBeDisplayed instead of  handAngles and rotate minute hand when timeToBeDisplayed['hours']==12 it will toggle again and again till the hour is between 12 and 1.
Preview:

I have placed toggle function inside moveHandsInSetTime and called when isDrag is true :

Can you please help me with that?
Thanks

@prakashujjwal1010 If I use timeToBeDisplayed instead of  handAngles and rotate minute hand when timeToBeDisplayed['hours']==12 it will toggle again and again till the hour is between 12 and 1.
Preview:

I have placed toggle function inside moveHandsInSetTime and called when isDrag is true :

Can you please help me with that?
Thanks

@saurabhhere obviously this simple logic won't work you have to consider the "change" not only the current hour value. By "toggle whenever it passes 12" I meant:

check if the hour hand moves from the top-left clock's half( 9 to 12) to another top-right clock's half(12 to 3).
check if the hour hand moves from the top-right clock's half( 12 to 3) to another top-left clock's half(9 to 12).

so plan above logic by comparing the previous value and current value of hour :)
(Note: Also test for the situation when the drag is very fast)

@saurabhhere obviously this simple logic won't work you have to consider the "change" not only the current hour value. By "toggle whenever it passes 12" I meant:

check if the hour hand moves from the top-left clock's half( 9 to 12) to another top-right clock's half(12 to 3).
check if the hour hand moves from the top-right clock's half( 12 to 3) to another top-left clock's half(9 to 12).

so plan above logic by comparing the previous value and current value of hour :)
(Note: Also test for the situation when the drag is very fast)

@prakashujjwal1010  Thanks! It worked :)

@prakashujjwal1010  Thanks! It worked :)

Changes Made:

Toggle AM/PM in Set-Time Mode
Ask questions till 23H in Set-Time-Game Mode

Preview of Changes:

All changes mentioned in #921 are made. Please review If any change is required.

Changes Made:

Toggle AM/PM in Set-Time Mode
Ask questions till 23H in Set-Time-Game Mode

Preview of Changes:

All changes mentioned in #921 are made. Please review If any change is required.

That's the idea.
But:

In 24h mode when rotating hands and hour pass 12h, the background should change
In 12h mode the Clock should be like before: background always white and no display of AM/PM after digit.

Updated PR with new changes.
Preview:

Nice job.
Still one issue: in play mode in 24h mode the background should change be adapted to the question asked.
In the following screen capture, the background should be white.

Plus finally I'm not a big fan of "AM" "PM" format for digits when in 24h mode. It will be more consistent to display it in 0-23 format like in play mode.

@saurabhhere oops you're right

Changes made :

In 12h mode Clock will show 1-12h with white background and in 24h mode Clock will show 0-23h (black background during PM hours).
During Set-Time-Game Mode, in 24h mode, the background will be white for 0-11h and black for 12-23h.
During Set-Time-Mode, in 24h mode, format will be digit only (without AM/PM) and background will toggle between white and black for AM & PM hours respectively.

Preview of all changes:

If all changes looks good to you, I will update the PR.

Sounds good.

PR Updated. Please Review

Good job @saurabhhere.
Thanks for your contribution.

authors: llaske prakashujjwal1010 saurabhhere

repo: llaske/sugarizer

license_source: bigquery


text:
Motor C wont spin below 15% throttle

Have to set higher throttle. Maby the esc needs calibration

esc calibration fixed the issue, throttle at 5% can spinn all motors

repo: lloois/Drone-Programming


text:
update function of UMAP does not work

I'm trying to build an incremental trainer for umap, updating on batches of data. I'm testing this out with mnist.
import numpy as np
import sklearn.datasets
import umap
import umap.utils as utils
import umap.aligned_umap
from sklearn.datasets import fetch_openml
from sklearn.decomposition import PCA

mnist = fetch_openml('mnist_784', version=1)
mnist.target = mnist.target.astype(int)

first, second = mnist.data[:50000], mnist.data[50000:]
print(first.shape, second.shape)

standard_embedding = umap.UMAP(random_state=42).fit(first)
standard_embedding.update(second)

on update I see
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
/var/folders/3d/d0dl2ykn6c18qg7kg_j7tplm0000gn/T/ipykernel_98177/3602609767.py in <module>
----> 1 standard_embedding.update(second)

~/.pyenv/versions/3.9.6/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/umap/umap_.py in update(self, X)
   3129
   3130         else:
-> 3131             self._knn_search_index.update(X)
   3132             self._raw_data = self._knn_search_index._raw_data
   3133             (

~/.pyenv/versions/3.9.6/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/pynndescent/pynndescent_.py in update(self, X)
   1611         X = check_array(X, dtype=np.float32, accept_sparse="csr", order="C")
   1612
-> 1613         original_order = np.argsort(self._vertex_order)
   1614
   1615         if self._is_sparse:

AttributeError: 'NNDescent' object has no attribute '_vertex_order'

Is this expected behavior? Am I using UMAP improperly here? I see an example of aligned_umap but I was hoping to use the standard umap as I do not have relations

Hi, I am also trying to build an incremental UMAP trainer where I load my embedding vectors in batches of 9k. But for the following code :
cnt = 0
start_index = 0
end_index = 100
search_space = {}
reducer = None

# Loading all search space pickles one by one
for i in tqdm(range(start_index, end_index), leave = True, position = 0):
  searchSpacePath = emb_vectors_path + "Split_" + str(i) + const_string
  embDict = {}
  with open(searchSpacePath, 'rb') as handle:
    embDict = pickle.load(handle)

  search_space.update(embDict)

  data_to_df = convert_to_df(list(embDict.values()))

  # updating the low dimensional graph with new points :

  # first set of vectors loaded & fit :
  if i == 0:
    reducer = umap.UMAP(n_neighbors = 10,
                        min_dist = 0.0,
                        n_components = 20,
                        metric = "euclidean",
                        random_state = random_state).fit(data_to_df)
  else:
    reducer.update(data_to_df)

print("\nLoaded %d items"%(len(search_space)))

I am facing this error :
ZeroDivisionError                         Traceback (most recent call last)
<ipython-input-30-f5089cfcbf5e> in <module>()
     26                         random_state = random_state).fit(data_to_df)
     27   else:
---> 28     reducer.update(data_to_df)
     29
     30 print("\nLoaded %d items"%(len(search_space)))

/usr/local/lib/python3.7/dist-packages/umap/umap_.py in update(self, X)
   3346             )
   3347             init[:original_size] = self.embedding_
-> 3348             init_update(init, original_size, self._knn_indices)
   3349
   3350             if self.n_epochs is None:

ZeroDivisionError: division by zero

My data is basically L2 normalised vectors of 1024 dimensions & I am making use of update to incrementally add 9 lakh data points to the UMAP mapper.
I tried the MNIST example & it worked properly with ".update()". The only difference I could find with my data & MNIST one was that mine is L2 normalised, is that causing the zero division error ?
Also I tried to load 3 lakh vectors & apply UMAP on them directly via the fit function. The results were amazing but for any data more than 3 lakh my Colab instance kept on crashing. Is there any other way to handle such a large dataset for dimensionality reduction ?

@ThomasNickerson  is that PR merged?

@ThomasNickerson Really cool to see this new PR! I was playing around a bit with this new functionality and seemed to have uncovered a bug, I think related to @vedrocks15's post. When trying out different dataset splits using the update function I noticed that I was getting the division by zero error in the init_update function. After a bit more digging, I believe that the issue happens when you call update on a dataset that is larger than the current dataset that UMAP has been fit over.
As a reference here is the code that I am using:
import numpy as np
import sklearn.datasets
import umap
import umap.plot
import umap.utils as utils
import umap.aligned_umap
from sklearn.datasets import fetch_openml
from sklearn.decomposition import PCA
import matplotlib.pyplot as plt

mnist = fetch_openml('mnist_784', version=1)
mnist.target = mnist.target.astype(int)
mnist_data = mnist.data.values
mnist_labels = mnist.target.values

split = 20000
first, second = mnist_data[:split], mnist_data[split:]
standard_embedding = umap.UMAP(random_state=42, verbose=True).fit(first)
standard_embedding.update(second)

Since the size of the MNIST dataset is 70_000, based on some spot testing, if you set split to be < 35_000 you get the divide by zero error described by @vedrocks15.
Additionally, here is the code for the init_update function, where I believe the error comes in the line current_init[i, d] /= n
@numba.njit()
def init_update(current_init, n_original_samples, indices):
    for i in range(n_original_samples, indices.shape[0]):
        n = 0
        for j in range(indices.shape[1]):
            for d in range(current_init.shape[1]):
                if indices[i, j] < n_original_samples:
                    n += 1
                    current_init[i, d] += current_init[indices[i, j], d]
        for d in range(current_init.shape[1]):
            current_init[i, d] /= n

    return

@jonathangomesselman even I saw this code & clearly the "n" variable in the loop is not being updated which is causing the division by zero error. I would just like to add that I also tried to .fit() the UMAP object with 3 lakh vectors (it worked) followed by using ".update()" with only 9k vectors & again the same problem of division by zero error.

Hey @lmcinnes & @vedrocks15 I am working on something similar and got the same error of divide by zero.
My dataset has more than 4M rows and 384 dimensions. While trying to reduce the dimension to 50, my 32 Gb RAM system doesn't take all of the 4M rows at once and I had to go with Batch processing. I am trying to fit the small chunks of data to UMAP and in the process of doing that, update doesn't seem to help much.
First of the small chunk:
xvs[:10000].shape => (10000, 384)
model1 = umap.UMAP(
            n_neighbors=30,
            min_dist=0.0,
            n_components=50,
            random_state=42,
            ).fit(xvs[:10000])

model1.embedding_.shape => (10000, 50)

model1.update(xvs[10000:20000]) gives the following error
ZeroDivisionError                         Traceback (most recent call last)
Input In [13], in <cell line: 1>()
----> 1 model1.update(xvs[10000:20000])

File ~\anaconda3\envs\py39\lib\site-packages\umap\umap_.py:3348, in UMAP.update(self, X)
   3344 init = np.zeros(
   3345     (self._raw_data.shape[0], self.n_components), dtype=np.float32
   3346 )
   3347 init[:original_size] = self.embedding_
-> 3348 init_update(init, original_size, self._knn_indices)
   3350 if self.n_epochs is None:
   3351     n_epochs = 0

ZeroDivisionError: division by zero

But when I re-run the same update code, I get different error this time.
ValueError                                Traceback (most recent call last)
Input In [14], in <cell line: 1>()
----> 1 model1.update(xvs[10000:20000])

File ~\anaconda3\envs\py39\lib\site-packages\umap\umap_.py:3347, in UMAP.update(self, X)
   3329 self.graph_, self._sigmas, self._rhos = fuzzy_simplicial_set(
   3330     self._raw_data,
   3331     self.n_neighbors,
   (...)
   3341     self.verbose,
   3342 )
   3344 init = np.zeros(
   3345     (self._raw_data.shape[0], self.n_components), dtype=np.float32
   3346 )
-> 3347 init[:original_size] = self.embedding_
   3348 init_update(init, original_size, self._knn_indices)
   3350 if self.n_epochs is None:

ValueError: could not broadcast input array from shape (10000,50) into shape (20000,50)

Not sure how to approach this problem and if there is any better solution for the batch processing in UMAP as I just need to fit the chunks of data and I need model.embeddings_  at the end to follow the next steps.
Thank you.!

repo: lmcinnes/umap


text:
Warn about writing to rc files

I always find it nice when install scripts that want to make changes to any config files ask/warn first. In the future I figure there'll be a default install and an advanced install process that would ask me if I'd like it to write to any rc files automatically, else print out what I need to do manually.
For now, it'd be cool if there was an additional note during or after the install process telling users that whichever rc file was written to so if they manage their own dotfiles they know to go check it out and update manually if need be.
A message in that dimmed font color (grey for me), in the post-install message, something that makes sense to those who manage their own dots but doesnt scare those who don't. "lms was added to your $PATH", for example, may be all that's needed so you're not even potentially adding friction by saying a file was written to.
Overall, a pretty low-priority request in my opinion, but I was gushing too much in my previous comment and you're the ones who set the bar so high with all you've been doing anyways so...
(and feel free to close/ignore/etc if you disagree or dont want this left open)

Hi, thanks for the suggestion. We will definitely consider it.

Hi, thanks for the suggestion. We will definitely consider it.

authors: panckreous ryan-the-crayon

repo: lmstudio-ai/lms


text:
fix var names and check auth type

Fix var confusing (conflicting?) naming.
Fix handling auth token when requesting from curl/swagger
Closes #12

Merge and release?

repo: lnbits/lndhub


text:
add Uri Online Judge

It's good site for beginners but there is more than that... I did the challenge last year and it turned out interesting tbh.

Hello,
I had a quick look. It looks good indeed.
However I believe I recognised some problems from UVa online judge.
Are you aware of where does URI online judge get its problems?

Hello,
I'm not aware of it.
Can you be more specific about the problems ?

Well It doesn't seem to be discussed as often compared to the ones on the list.
In addition, I cannot verify the "awsomeness" of it (a quick search on Codeforces showed up nothing but heavily downvoted posts - even though it's attributed to the terrible grammar and formatting).
I'm also slightly concerned about the problems not being very original (In that case, people can just goto the source platform to practice).

Most of them is easy and that's why probable.
Yes I can verify that some of their problems has got terrible grammar because some of them I reported last year.
Things that I like about UOJ - their problems are separated by topic author and it's divided in levels.
I agree that other sites are more popular and they got more problems too.

All that was discussed above says that you don't have to add that URI online judge.
So I'll close this pr.

I would just need someone else to back it.
It does seem like a good platform, but I have no knowledge of it personally.
When I mentioned terrible grammar earlier, I wasn't referring to the problem statements, but the posts on Codeforces that refer to the URI judge. I cannot really get any information on those posts.
I'll try to find out more about it later.
Thank you for the PR :)

I got it. Now I see what you mean.
That's really good platform but still they had lot's of things to improve.
Ok try it later... Don't forget to check out their toolkit, that's one of the greatest thing about their platform.
Welcome !

authors: dreamtocode lnishan

repo: lnishan/awesome-competitive-programming


text:
ChatCompletionMessage union types dissallow proper FunctionAwareAssistantCompletionMessage and AssistantCompletionMessage usage

When passing function and function_call to the createChatCompletion() we should expect to have function_call object inside content of a message, however it's impossible to determine whether the openAI response is AssistantCompletionMessage or FunctionAwareAssistantCompletionMessage as both share the same role:
interface AssistantCompletionMessage {
  content: string;
  name?: string;
  role: "assistant";
}

interface FunctionAwareAssistantCompletionMessage {
  content: string | null;
  role: "assistant";
  function_call?: {
    "name": string;
    "arguments": string;
  };
}

And it seems impossible to narrow the type from that point, so properties name from AssistantCompletionMessage and property function_call from FunctionAwareAssistantCompletionMessage can't be accessed.

Moreover, those types are not exported, so you can't really create a Type Guard yourself.

You should be able to narrow the type further by checking of the object has a key. I'm away from my computer at the moment but something like
if ("function_call" in completionMessage) {

}

We should probably export the types anyways though.

That's a great point, thanks @lino-levan ! I have created a Pull Request with the exports - if you're interested https://github.com/load1n9/openai/pull/25


text:
@2.15.0 - puppeteer@21.9.0

close #611

coverage: 99.245%. remained the same
when pulling a6b432710c84ba6675081b84c123e4092a1b4aa7 on rc-2.15.0
into 6ee7edc5070956486f362042b4a655f602bde7d2 on master.

authors: coveralls localnerve

repo: localnerve/html-snapshots

license: mit


text:
Update configuration document with new networking description

The new variables require explanation on how they work, and what the default behaviour will be if they are absent.
See the implementation PR in the community repo

hey @simonrw, what's happening with this PR?

authors: simonrw thrau

repo: localstack/docs


text:
How to view the load of the master when starting in a distributed manner

Prerequisites

[X] I am using the latest version of Locust
[X] I am suggesting a new feature, not asking a question

Description
I am currently using local for distributed startup, and I can obtain the workload of the worker from the master. However, I need more master workload information, such as CPU usage and memory usage. Where should I obtain it from? Can you provide me with specific code? The code for obtaining the worker is as follows:
workers_info = [w for w in runner.clients.values()]

Hi! Master logs a high cpu-warning like how workers do, and if it it doesn't you should be fine.
Are you encountering a problem? If not, master stats are kind of boring as they should have zero impact on the actual load (unless it is, for some reason, completely overloaded).

authors: cyberw ikun-bug

repo: locustio/locust


text:
Requirements packaging problem with ubuntu 16.04

Changes from #33 don't appear to work with ubuntu 16.04.  Reproducing case:
serverless.yml
service: my-service

provider:
  name: aws
  runtime: python3.6
  stage: dev
  region: eu-west-1

package:
  exclude:
    - "**"
  include:
    - handler.py

functions:
  hello:
    handler: handler.hello
    events:
      - http:
          path: /foo
          method: get

plugins:
  - serverless-wsgi

custom:
  wsgi:
    app: handler.hello
    pythonBin: python3

handler.py
import xmltodict

def hello(event, context):
    body = {
        "message": "Hello lambda world",
        "input": event
    }

    response = {
        "statusCode": 200,
        "body": xmltodict.unparse({"result": body}),
    }

    return response

requirements.txt
xmltodict

Results:

When the function is called, it returns {"message": "Internal server error"}.
CloudWatch logs show: Unable to import module 'handler': No module named 'xmltodict'
.serverless/my-service.zip is huge (20.52MB) and contains a load of unrelated junk in a .venv top-level directory.

$ unzip -v .serverless/my-service.zip
Archive:  .serverless/my-service.zip
 Length   Method    Size  Cmpr    Date    Time   CRC-32   Name
--------  ------  ------- ---- ---------- ----- --------  ----
     241  Defl:N      152  37% 1980-01-01 00:00 4c3917f2  handler.py
    6091  Defl:N     2497  59% 1980-01-01 00:00 04039966  wsgi.py
      13  Defl:N       15 -15% 1980-01-01 00:00 a6e25e52  .wsgi_app
    2108  Defl:N      833  61% 1980-01-01 00:00 84ee13bb  .venv/bin/activate
    1137  Defl:N      537  53% 1980-01-01 00:00 078145a3  .venv/bin/activate_this.py
    1050  Defl:N      532  49% 1980-01-01 00:00 6824902d  .venv/bin/activate.csh
    2248  Defl:N      900  60% 1980-01-01 00:00 82d1587f  .venv/bin/activate.fish
     278  Defl:N      206  26% 1980-01-01 00:00 514e61e4  .venv/bin/easy_install
     278  Defl:N      206  26% 1980-01-01 00:00 514e61e4  .venv/bin/easy_install-2.7
     250  Defl:N      188  25% 1980-01-01 00:00 e0fcf0e5  .venv/bin/pip
     250  Defl:N      188  25% 1980-01-01 00:00 e0fcf0e5  .venv/bin/pip2
     250  Defl:N      188  25% 1980-01-01 00:00 e0fcf0e5  .venv/bin/pip2.7
 5429482  Defl:N  1653333  70% 1980-01-01 00:00 46c4a7b2  .venv/bin/python
    2367  Defl:N      905  62% 1980-01-01 00:00 9b7d9935  .venv/bin/python-config
 5429482  Defl:N  1653333  70% 1980-01-01 00:00 46c4a7b2  .venv/bin/python2
 5429482  Defl:N  1653333  70% 1980-01-01 00:00 46c4a7b2  .venv/bin/python2.7
     257  Defl:N      193  25% 1980-01-01 00:00 8fcca9bf  .venv/bin/wheel
   18619  Defl:N     5186  72% 1980-01-01 00:00 b0f6c3cf  .venv/lib/python2.7/_abcoll.py
   30978  Defl:N     8802  72% 1980-01-01 00:00 5f62d05f  .venv/lib/python2.7/_abcoll.pyc
    5911  Defl:N     1619  73% 1980-01-01 00:00 0d0944be  .venv/lib/python2.7/_weakrefset.py
   12100  Defl:N     2989  75% 1980-01-01 00:00 bbd04380  .venv/lib/python2.7/_weakrefset.pyc
    7145  Defl:N     2393  67% 1980-01-01 00:00 c9f117b3  .venv/lib/python2.7/abc.py
    6780  Defl:N     2784  59% 1980-01-01 00:00 8d2304aa  .venv/lib/python2.7/abc.pyc
...
  151008  Defl:N    72686  52% 1980-01-01 00:00 9d6eb4c8  .venv/share/python-wheels/urllib3-1.13.1-py2.py3-none-any.whl
  118619  Defl:N    56392  53% 1980-01-01 00:00 169d61c0  .venv/share/python-wheels/wheel-0.29.0-py2.py3-none-any.whl
--------          -------  ---                            -------
67493747         21060069  69%                            2104 files

Note that the .venv subdirectory appears to include a bunch of python2 stuff, even though I have specified pythonBin: python3.
And it doesn't include the package from requirements.txt
$ unzip -v .serverless/my-service.zip | grep xmltodict
$

Looking at output from strace -s256 -f sls deploy 2>/tmp/strace.out
$ grep execve /tmp/strace.out  | grep -v ENOENT
execve("/usr/bin/sls", ["sls", "deploy"], [/* 22 vars */]) = 0
execve("/usr/bin/node", ["node", "/usr/bin/sls", "deploy"], [/* 22 vars */]) = 0
[pid  7886] execve("/usr/bin/python3", ["python3", "/usr/lib/node_modules/serverless-wsgi/requirements.py", "/usr/lib/node_modules/serverless-wsgi/requirements.txt", "/home/ubuntu/sless/my-service/requirements.txt", "/home/ubuntu/sless/my-service/.requirements"], [/* 22 vars */] <unfinished ...>
[pid  7886] <... execve resumed> )      = 0
[pid  7887] execve("/usr/bin/python2", ["/usr/bin/python2", "/usr/lib/python3/dist-packages/virtualenv.py", "/home/ubuntu/sless/my-service/.requirements/.venv", "--quiet"], [/* 23 vars */] <unfinished ...>
[pid  7887] <... execve resumed> )      = 0
[pid  7888] execve("/home/ubuntu/sless/my-service/.requirements/.venv/bin/python2", ["/home/ubuntu/sless/my-service/.requirements/.venv/bin/python2", "-c", "import sys;out=sys.stdout;getattr(out, \"buffer\", out).write(sys.prefix.encode(\"utf-8\"))"], [/* 23 vars */] <unfinished ...>
[pid  7888] <... execve resumed> )      = 0
[pid  7889] execve("/home/ubuntu/sless/my-service/.requirements/.venv/bin/python2", ["/home/ubuntu/sless/my-service/.requirements/.venv/bin/python2", "-", "setuptools", "pkg_resources", "pip", "wheel"], [/* 30 vars */] <unfinished ...>
[pid  7889] <... execve resumed> )      = 0
[pid  7890] execve("/bin/sh", ["sh", "-c", "LC_ALL=C LANG=C /sbin/ldconfig -p 2>/dev/null"], [/* 30 vars */]) = 0
[pid  7891] execve("/sbin/ldconfig", ["/sbin/ldconfig", "-p"], [/* 31 vars */]) = 0
[pid  7891] execve("/sbin/ldconfig.real", ["/sbin/ldconfig.real", "-p"], [/* 31 vars */]) = 0
[pid  7892] execve("/bin/sh", ["sh", "-c", "uname -p 2> /dev/null"], [/* 30 vars */]) = 0
[pid  7893] execve("/bin/uname", ["uname", "-p"], [/* 30 vars */]) = 0

Note that it's explicitly running /usr/bin/python2

The solution is to add -p <pythonversion> to virtualenv.
I don't know how to get hold of the custom.wsgi.pythonBin setting in requirements.py, but if I hard-code the value I want it works:
--- requirements.py.orig	2017-10-03 11:41:11.433869466 +0000
+++ requirements.py	2017-10-03 11:41:27.806597479 +0000
@@ -41,7 +41,7 @@
         shutil.rmtree(tmp_dir)

     original = sys.argv
-    sys.argv = ['', venv_dir, '--quiet']
+    sys.argv = ['', venv_dir, '--quiet', '-p', 'python3']
     try:
         virtualenv.main()
     finally:

Now the zipfile is 952 KB
$ unzip -v .serverless/my-service.zip
Archive:  .serverless/my-service.zip
 Length   Method    Size  Cmpr    Date    Time   CRC-32   Name
--------  ------  ------- ---- ---------- ----- --------  ----
    6091  Defl:N     2497  59% 1980-01-01 00:00 04039966  wsgi.py
      13  Defl:N       15 -15% 1980-01-01 00:00 a6e25e52  .wsgi_app
    1591  Defl:N      831  48% 1980-01-01 00:00 a3e71e5a  Werkzeug-0.12.2.dist-info/DESCRIPTION.rst
       4  Defl:N        6 -50% 1980-01-01 00:00 c2971fc7  Werkzeug-0.12.2.dist-info/INSTALLER
    1532  Defl:N      816  47% 1980-01-01 00:00 c0421a8f  Werkzeug-0.12.2.dist-info/LICENSE.txt
    2738  Defl:N     1233  55% 1980-01-01 00:00 bde3ac78  Werkzeug-0.12.2.dist-info/METADATA
    1276  Defl:N      593  54% 1980-01-01 00:00 a9fbc245  Werkzeug-0.12.2.dist-info/metadata.json
    6646  Defl:N     2964  55% 1980-01-01 00:00 b70eb044  Werkzeug-0.12.2.dist-info/RECORD
       9  Defl:N       11 -22% 1980-01-01 00:00 d4cd6b6c  Werkzeug-0.12.2.dist-info/top_level.txt
     110  Defl:N       95  14% 1980-01-01 00:00 6f7f3387  Werkzeug-0.12.2.dist-info/WHEEL
   14633  Defl:N     7005  52% 1980-01-01 00:00 c31e127d  __pycache__/xmltodict.cpython-35.pyc
  101373  Defl:N    33527  67% 1980-01-01 00:00 6291aaa7  pkg_resources/__init__.py
  106583  Defl:N    43516  59% 1980-01-01 00:00 988b7b82  pkg_resources/__pycache__/__init__.cpython-35.pyc
     761  Defl:N      468  39% 1980-01-01 00:00 dc457869  pkg_resources/__pycache__/py31compat.cpython-35.pyc
...
   82986  Defl:N    26108  69% 1980-01-01 00:00 acc1e2c0  werkzeug/wrappers.py
   42838  Defl:N    13458  69% 1980-01-01 00:00 7b28fd02  werkzeug/wsgi.py
      10  Defl:N       12 -20% 1980-01-01 00:00 d27f2d5e  xmltodict-0.11.0.dist-info/DESCRIPTION.rst
       4  Defl:N        6 -50% 1980-01-01 00:00 c2971fc7  xmltodict-0.11.0.dist-info/INSTALLER
    1144  Defl:N      372  68% 1980-01-01 00:00 e7c56768  xmltodict-0.11.0.dist-info/METADATA
    1270  Defl:N      518  59% 1980-01-01 00:00 c16b04df  xmltodict-0.11.0.dist-info/metadata.json
     713  Defl:N      429  40% 1980-01-01 00:00 8d51f2ed  xmltodict-0.11.0.dist-info/RECORD
      10  Defl:N       12 -20% 1980-01-01 00:00 06727e3b  xmltodict-0.11.0.dist-info/top_level.txt
     110  Defl:N       95  14% 1980-01-01 00:00 1382dbab  xmltodict-0.11.0.dist-info/WHEEL
   17356  Defl:N     5618  68% 1980-01-01 00:00 65119ad2  xmltodict.py
--------          -------  ---                            -------
 2578966           951253  63%                            145 files

repo: logandk/serverless-wsgi


text:
loading config file during installation

loading config file to related config path during pip installation
version unification - we need to edit one place to bump the version all over the code now
version bump

+1

repo: logentries/lecli


text:
Node type Calculator not found

Describe the bug
In hugging face space, I create a simple agent, and get error "Node type Calculator not found". I think It's a bug, or maybe I did something wrong?

In my own mac have same problem.
langchain                0.0.166
langflow                 0.0.74

repo: logspace-ai/langflow


text:
Travis CI build failing - zeromq context singleton

Currently, the travis ci build is failing: https://travis-ci.org/logstash-plugins/logstash-input-zeromq/builds/127623701
I reproduced the problem on my system. I think, the reason for this is the zeromq context singleton, introduced in https://github.com/logstash-plugins/logstash-mixin-zeromq/commit/53130a3e13a20ae1a67c82ff143b6142c0be9c5e
The problem is, in one spec test, the plugin is closed, which causes the zmq context to be terminated. Because @context in the ZeroMQContext-singleton (https://github.com/logstash-plugins/logstash-mixin-zeromq/blob/master/lib/logstash/plugin_mixins/zeromq.rb#L5) is not reset to nil, no new zmq context is created for the second spec test, which follows. This causes to failure to create a new zmq socket and finally leads to the error of calling close on a NilClass.
One way to make the spec-tests working again is to remove line https://github.com/logstash-plugins/logstash-input-zeromq/blob/master/lib/logstash/inputs/zeromq.rb#L136, where the ZMQ context is terminated.
In my opinion, there are two issues:

terminating the context is potentially called multiple times (multiple worker or even from different plugins like zmq input, filter and output).
terminating the context alone is not enough, the ZeroMQContext-singleton should also set @context = nil after the context is terminated.

I suggest the following solution:

The zmq plugins (input, filter, output) should call terminate_context in their close method.
The terminate_context method should check, if the context is not yet terminated. If so, the context should be terminated and @context should be set to nil.
The terminate_context should be thread safe.

@avishai-ish-shalom

Related to https://github.com/logstash-plugins/logstash-mixin-zeromq/issues/3

The underlying problem is that Logstash doesn't have global termination hooks. ZeroMQ termination needs to be orchestrated - as terminating the context releases blocked sockets. Having plugins call terminate_context is a poor man's workaround, but we may have to live with it.

@avishai-ish-shalom I agree. For the moment, the poor man's workaround seems to be to only/best available solution.

authors: avishai-ish-shalom breml

repo: logstash-plugins/logstash-input-zeromq


text:
Add ability to set `transport.publish_host'

Allow settings the transport.publish_host.
This is needed when using private networks for the transport or when running in docker across hosts (e.g. not using --link).

:+1:


text:
GraphQL Error: "message": "options.ctr is not a constructor" when using fieldEdge?

Setup is like this:
UserSchema:
...
 fields: {
    foodID: UUIDType({
      fieldEdge: { schema: "Food", inverseEdge: "users" },
    }),
...

FoodSchema:
...
edges: [
    {
      name: "users",
      schemaName: "User",
    },

Codegen is successful, but I think some files/naming is missing/incorrect? When running the query in GraphiQL, it produces the error "message": "options.ctr is not a constructor". I saw that in user_to_foods_connection_type.ts, UserToFoodsEdge is missing:
import { UserToFoodsEdge } from "src/ent/";

Am I missing something in my setup?

I'm not sure. this might be a weird pluralization thing
are you using v0.1.* or v0.2.*?
UserToFoodsEdge should be defined in src/ent/user/query/user_to_foods_query.ts based on your schema
are you using docker or running locally?
if you're using docker, can you run with --write-all
docker-compose -f docker-compose.dev.yml run --rm app tsent codegen --write-all

or locally:
tsent codegen --write-all

repo: lolopinto/ent


text:
scripts: add command line args

With these patches command line arguments can be used in Lona scripts.
python lona_script.py --port=8081 --shell -O Foo=True

Codecov Report

Merging #127 (9edf946) into master (3430711) will decrease coverage by 0.17%.
The diff coverage is 2.32%.

@@            Coverage Diff             @@
##           master     #127      +/-   ##
==========================================
- Coverage   32.60%   32.42%   -0.18%
==========================================
  Files          68       68
  Lines        4438     4444       +6
==========================================
- Hits         1447     1441       -6
- Misses       2991     3003      +12

Impacted Files
Coverage Δ

lona/command_line/handle_command_line.py
0.00% <0.00%> (ø)

lona/app.py
20.30% <3.12%> (-3.13%)
:arrow_down:

lona/html/abstract_node.py
32.97% <0.00%> (-0.71%)
:arrow_down:

lona/html/data_binding/inputs.py
43.06% <0.00%> (-0.69%)
:arrow_down:

lona/static_file_loader.py
72.38% <0.00%> (-0.27%)
:arrow_down:

lona/command_line/collect_static.py
0.00% <0.00%> (ø)

lona/server.py
47.09% <0.00%> (+0.16%)
:arrow_up:

lona/view_runtime_controller.py
47.36% <0.00%> (+0.75%)
:arrow_up:

lona/connection.py
34.61% <0.00%> (+1.28%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3430711...9edf946. Read the comment docs.

@maratori I think it's a very useful feature that you just call app.run() and can override the port for example. If we get a bug report with a reproducing script, the first thing i do is patching app.run() to app.run(log_level='debug', shell=True). It would be nice to just run it with -l debug --shell without changing something.
If we put this functionality in it's own place, i would recommend everyone to use it, because it adds the same interface to scripts like in projects, which is especially useful if you read https://lona-web.org/end-user-documentation/debugging.html while developing. I think it makes it consistent.
Also: I like debugging infrastructure that's always in place. Not only if you set it up. I can tell every user to add -l debug, but not every user to patch a line of code.
Is there a reason to split that, that i miss?

@maratori Thanks for reviewing!

authors: codecov-commenter fscherf

repo: lona-web-org/lona


text:
🛑 lbkrs.com -> longportapp.com is down

In dc5d9e2, lbkrs.com -> longportapp.com (https://lbkrs.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: lbkrs.com -> longportapp.com is back up in 313b6e1.

repo: longbridgeapp/uptime


text:
🛑 Northern Light is down

In 1ff1fe0, Northern Light (https://northernlight.jau.co.jp) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Northern Light is back up in 476582d.

repo: longforme/longforme-uptime-monitor


text:
Progress report for backup

Backup should report progress.
It's not straightforward in the current engine architecture when the backups are done out of band without the engine knowing it.
Design needed.

Hi, looking forward to seeing this implemented. At the moment I am backing up some volumes but I don't know if the backup has finished or not yet.

Usage for UI:
The backup list could be seen in the JSON format with the following request:
curl http://<longhorn-ui-ip>:<port>/v1/volumes
Sample Response:
{
    "createTypes": {
        "volume": "http://206.189.69.105:32338/v1/volumes"
    },
    "data": [
        {
            "actions": {
                ...
            },
            "backupStatus": [
                {
                    "actions": null,
                    "backupError": "",
                    "backupURL": "s3://backupbucket@us-east-1/backupstore?backup=backup-cc0d6fbc1a7f4760&volume=btest",
                    "id": "backup-cc0d6fbc1a7f4760",
                    "links": null,
                    "progress": 100,
                    "snapshot": "6598a238-3c7e-4373-a74f-1d3e0ac6deef"
                },
                {
                    "actions": null,
                    "backupError": "",
                    "backupURL": "s3://backupbucket@us-east-1/backupstore?backup=backup-932d69f9ee4f4187&volume=btest",
                    "id": "backup-932d69f9ee4f4187",
                    "links": null,
                    "progress": 100,
                    "snapshot": "68403f2d-65d8-4a70-bf5e-4feedef348f0"
                }
            ],
            "baseImage": "",
            "conditions": {
               ...
                }
            },
          ...

@shreesha21 Also need to document the interaction between fields in backup status.

In BackupStatus, there are 4 important fields whose purpose is defined below:
`Snapshot`: This indicates the name of the snapshot being backed up.
`Progress`: This indicates the progress percentage of the backup. Value: 0 - 100
`BackupURL`: When the progress reaches 100, a backupURL is generated and populated here. This backupURL is required while restoring this backup in the future.
`BackupError`:  If there are any error thats encountered while creating the backup, it will be populated in this field.

Steps to test:

Create longhorn volume
Attach the volume to a node
Mount the volume on the node
Write fairly large data into the mounted volume ~ 3 GB
On volume details page, click Create Backup
Expected result:

In volume details page, Snapshots section you should see a new snapshot being created, and you should see backup progress.
Hovering on the snapshot, a tool-tip will be appear, and it will contain backup information (backup URL, snapshot name, progress, .. )

authors: meldafrawi shreesha21 vitobotta yasker

repo: longhorn/longhorn


text:
[BUG] cannot mount NFSv4 after update from master-head to v1.4.1

Describe the bug (🐛 if you encounter this issue)

I have a HA cluster running 2 Master 5 Worker.
I upgraded from longhorn-engine:master-head to longhorn-engine:v1.4.1
After the upgrade I did the usual "Engine Upgrade" on the Volumes
than I saw some Volumes are stuck in either

or

So I wanted to try and restore a Backup and there I saw the error message above
Expected behavior
See and create Backups
Log or Support bundle
supportbundle_cf330071-3915-4950-a919-2a9294554885_2023-03-13T13-51-15Z.zip
Environment

Longhorn version:
1.4.1

Installation method (e.g. Rancher C
supportbundle_cf330071-3915-4950-a919-2a9294554885_2023-03-13T13-51-15Z.zip
atalog App/Helm/Kubectl):
Kubectl

Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version:
K8s with kubeadm - all 1.24.0

Number of management node in the cluster:
2
Number of worker node in the cluster:
5

Node config

OS type and version:
Ubuntu 22.04 and Ubuntu 20.04
CPU per node:
~20-40 depends on the nodes
Memory per node:
~ 300GB

Disk type(e.g. SSD/NVMe):
HDD over SAN

Network bandwidth between the nodes:
~4-10G

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
Baremetal

Number of Longhorn volumes in the cluster:
14

Additional context
Add any other context about the problem here.
I updated the control plane yesterday from 1.23.X to 1.24.0 and had some troubles, because I switched from Docker to containerd.

I upgraded from longhorn-engine:master-head to longhorn-engine:v1.4.1

Is your previous longhorn-engine version master-head?
master-head is for development. We cannot guarantee downgrade from master-head to v1.4.1 if safe.
For the backup error, you can mount the remote nfs folder in the longhorn-manager pod and check if it works.

Can you check both server and client sides support NFSv4.0, v4.1 or v4.2?
Ref: https://longhorn.io/kb/troubleshooting-unable-to-mount-an-nfs-backup-target/

You can try

Set backup target setting to empty
Enter each longhorn-manager pod and unmount the NFS backup target monntpoint by force unmount umount -f
Set backup target setting to your remote NFS server

Sorry, in the Second step, can you login into each longhorn-manager pod and check the mountpoint by mount | grep nfs?

Do you have any idea? @mantissahz @weizhe0422

@Razorbob Can you provide the support bundle? Thank you.

@Razorbob had you run curl -sSfL https://raw.githubusercontent.com/longhorn/longhorn/v1.4.1/scripts/environment_check.sh | bash this script before?

Sorry, updated the command.

I think it was a typo -> Longhon instead of Longhorn

Oh, yeah. You're right.
Except for mars4, all nodes looks work well. Can you check dmesg of the mars4 host and see if there is any clue?

[1402749.847295] nfs: server 10.0.10.51 not responding, timed out
[1402749.847316] NFS: state manager: lease expired failed on NFSv4 server 10.0.10.51 with error 110

I think the next step we can troubleshooting why the sever is not responding.

Its a Qnap NAS with 3.4.6 Kernel

Do you mean the backup target is a QNAP NAS?
Will update if I have any idea.

Hey Guys any ideas? I don't know why, but I feel like the NAS is not the problem here - cause I can mount the share manually just fine.

I still have no idea why the NFS client is somehow stuck on the mars4 node, but it looks not related to Longhorn itself. Would you mind trying to restart this node and see if the issue still remains?

@Razorbob Everything is back to normal, right?

authors: Razorbob derekbit mantissahz


text:
🛑 Minecraft Main Server is down

In 44ef101, Minecraft Main Server ($MC_MAIN_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Minecraft Main Server is back up in f9501af.

repo: loongwork/status


text:
RegexCorsConfiguration - always calls the super class method

I'm trying to use your RegexCorsConfiguration I have kind of the same implementation as you except I expose CorsFilter using a FilterRegistrationBean and via @Bean annotation.
        @Bean
        FilterRegistrationBean corsFilter() {
          UrlBasedCorsConfigurationSource source = new UrlBasedCorsConfigurationSource();
          CorsConfiguration config = new RegexCorsConfiguration();
          config.setAllowCredentials(true);

          this.corsSettings.getAllowedHeaders().forEach(config::addAllowedHeader);
          this.corsSettings.getAllowedMethods().forEach(config::addAllowedMethod);
          this.corsSettings.getAllowedOrigins().forEach(config::addAllowedOrigin);

          source.registerCorsConfiguration("/**", config);
          FilterRegistrationBean bean = new FilterRegistrationBean<>(new CorsFilter(source));
          bean.setOrder(Ordered.HIGHEST_PRECEDENCE);
          return bean;
        }

But for some reason, it always calls the superclass implementation of the checkOrigin method. Do you have any idea about this? Appreciate your feedback

Hi @RockyRx ,
RegexCorsConfiguration redefines checkOrigin like this:
https://github.com/looorent/spring-security-jwt/blob/bf0dac14736db062fd43862c58eebf0d4aadd0b2/src/main/java/be/looorent/security/jwt/RegexCorsConfiguration.java#L48-L52
This means before checking the origin based on a regular expression, it initially checks whether the origin already meets some basic CORS checks (for instance, if you allow "*" in your CORS configuration, your regex won't be used).
If you actually want to avoid this basic CORS check, you could extend RegexCorsConfiguration.checkOrigin to not call super.checkOrigin in checkOrigin.

@looorent
Thanks for the quick response.
I tried commenting off the super.checkOrigin in checkOrigin, but still, it calls the superclass method. I think I have done something fundamentally wrong here but still could not figure it out.
  @Nullable
  public String checkOrigin(String requestOrigin) {
//    String result = super.checkOrigin(requestOrigin);
    return checkOriginWithRegularExpression(requestOrigin);
  }

Would you have a repository with a working example? So I could debug it by myself and identifies why there is a unexpected check.

authors: RockyRx looorent

repo: looorent/spring-security-jwt


text:
Screen shader parser: Screen shader parse failed

When using the main branch of Hyprshade, shaders fail to parse correctly.
Steps to Reproduce

Check out the main branch of the Hyprland repository.
Attempt to run Hyprland with custom shaders (blue filters).

Please provide your configuration file (hyprshade.toml), the command(s) you ran (e.g. hyprshade on blue-light-filter), and the command output.

Actually, did you set decoration:screen_shader to the path to blue-light-filter.glsl.mustache manually?

I managed to fix it by copying https://github.com/loqusion/hyprshade/tree/3.2.1/shaders into my shaders directory instead of using shaders from master branch. I used the default example config that is provided in code.

The shaders on the main branch are actually Mustache templates, so they will only work when rendered into GLSL. Hyprshade on the main branch does this with hyprshade on, hyprshade toggle, etc. so that shaders are configurable (see the 4.0.0 README for more info).
Did you activate the shader with Hyprshade on the main branch, with Hyprshade pre-4.0.0, or some other way?

At first I copied config from the master branch and activated the shaders using hyprshade on blue-light-filter. It didn't produce any relevant output, only displaying 'parse failed.' Eventually, I managed to fix it using the method I described earlier here.

Was the hyprshade executable from the main branch or was it a stable version? If main, this could be a bug.

It was a stable version, it was my mistake because of copying shaders from main branch.

Shaders should not need manual installation, they are included in the wheel. Did your installation of Hyprshade not include them?

Since I'm using nixos, I didn't declare shaders path in my config. Instead, I manually placed it in my .config directory from github repo.

authors: loqusion vitezprchal

repo: loqusion/hyprshade


text:
Support un-persisted ActiveRecord objects

It would be useful if the ActiveRecord adapter support workflow transitions on newly-created (unpersisted) objects. I believe it would only require the persist_workflow_state method to check persisted? first, and to assign the attribute directly without attempting to update_column.

Hi @jasonkarns, It has been a while since I used this project (or ruby) so development hasn't been very active.
I'll check into this in next couple of days. But if you'd like to submit a PR for this I'll be happy to merge it.

authors: jasonkarns lorefnon

repo: lorefnon/workflow-orchestrator


text:
links to user guide and data sheet

Hi, this might be useful ...

Thanks!

authors: lorenzschmid vencax


text:
Improve stuffs for PHPUnit fixture

Changed log

Adding the prefer-stable to be true and it can install stable dependencies when setting the minimum-stability is dev.
Adding the autoload-dev setting for composer.json file and it can load testing classes automatically.
According to the official PHPUnit doc, it should be the protected function setUp method.

Merged hhanks Peter !
i would suggest you open pull request for develop branch, master branch contains only stable versions.

Merged hhanks Peter !
i would suggest you open pull request for develop branch, master branch contains only stable versions.

repo: lotfio/ouch


text:
Stroke effect is not working

Hi, i'm new in Lottie/After Effects so i don't know if is my mistake or bug/library limitation. I made a animation one logo with two animations, one to move a pen and other to show a letter simulating writing. When i export using bodymovin, in lottiefiles works absolutely fine but when i show in react native project only the pen movement works, the effect on letter that i made using stroke not work.
My Animation
https://lottiefiles.com/share/woltdzbn

Hey, yeah, some Afrer Effects features are not supported by lottie. Here's the full list: https://github.com/airbnb/lottie/blob/master/supported-features.md

Correct me if I'm wrong but this effect is using Strokes and according to your link, strokes are completely supported.

repo: lottie-react-native/lottie-react-native


text:
"react/bridging/AString.h" file not found

"lottie-ios": "^3.4.0",
"lottie-react-native": "^5.1.4",
"react-native": "^0.70.5",

Expected behavior: Build should succeed.
Actual behavior:
Even though the file is present in node_modules/react-native/ReactCommon/react/bridging/AString.h.
It throws an error Could not build Objective-C module 'React' "react/bridging/AString.h" file not found
Also tried solution as present here
https://github.com/lottie-react-native/lottie-react-native/issues/708#issuecomment-775175081
Versions
{
  npm: '8.19.2',
  node: '14.17.6',
  v8: '8.4.371.23-node.76',
  uv: '1.41.0',
  zlib: '1.2.11',
  brotli: '1.0.9',
  ares: '1.17.2',
  modules: '83',
  nghttp2: '1.42.0',
  napi: '8',
  llhttp: '2.1.3',
  openssl: '1.1.1l',
  cldr: '39.0',
  icu: '69.1',
  tz: '2021a',
  unicode: '13.0'
}

I'm facing the same issue!

I have the same issue! There are no solutions yet?

Would you please share your Podfile configuration?
This can be due to using modular headers being enabled.
@roots-ai
@SoohyungJung
@virginiab10

Same issue here in RN 0.70.5

`require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'
platform :ios, '12.4'
install! 'cocoapods', :deterministic_uuids => false
target 'MyApp' do
#rn_maps_path = '../node_modules/react-native-maps'
#pod 'react-native-google-maps', :path => rn_maps_path
permissions_path = '../node_modules/react-native-permissions/ios'
pod 'Permission-Camera', :path => "#{permissions_path}/Camera"
pod 'Permission-LocationAccuracy', :path => "#{permissions_path}/LocationAccuracy"
pod 'Permission-LocationAlways', :path => "#{permissions_path}/LocationAlways"
pod 'Permission-LocationWhenInUse', :path => "#{permissions_path}/LocationWhenInUse"
pod 'Permission-Motion', :path => "#{permissions_path}/Motion"
pod 'Permission-Notifications', :path => "#{permissions_path}/Notifications"
pod 'Permission-FaceID', :path => "#{permissions_path}/FaceID"
config = use_native_modules!
Flags change depending on the env values.
flags = get_default_flags()
use_react_native!(
:path => config[:reactNativePath],
# Hermes is now enabled by default. Disable by setting this flag to false.
# Upcoming versions of React Native may rely on get_default_flags(), but
# we make it explicit here to aid in the React Native upgrade process.
:hermes_enabled => true,
:fabric_enabled => flags[:fabric_enabled],
# Enables Flipper.
#
# Note that if you have use_frameworks! enabled, Flipper will not work and
# you should disable the next line.
:flipper_configuration => FlipperConfiguration.enabled(["Debug"], {'Flipper' => '0.163.0'}),
# An absolute path to your application root.
:app_path => "#{Pod::Config.instance.installation_root}/.."
)
target 'MyApp' do
inherit! :complete
# Pods for testing
end
post_install do |installer|
react_native_post_install(
installer,
# Set mac_catalyst_enabled to true in order to apply patches
# necessary for Mac Catalyst builds
:mac_catalyst_enabled => false
)
__apply_Xcode_12_5_M1_post_install_workaround(installer)
end
end
`
Here is what my Podfile looks like.

Here's what my pod file pretty much looks like.
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'

platform :ios, '12.4'
install! 'cocoapods', :deterministic_uuids => false

target 'MyExampleApp' do

  #rn_maps_path = '../node_modules/react-native-maps'
  #pod 'react-native-google-maps', :path => rn_maps_path

  permissions_path = '../node_modules/react-native-permissions/ios'

  pod 'Permission-Camera', :path => "#{permissions_path}/Camera"
  pod 'Permission-LocationAccuracy', :path => "#{permissions_path}/LocationAccuracy"
  pod 'Permission-LocationAlways', :path => "#{permissions_path}/LocationAlways"
  pod 'Permission-LocationWhenInUse', :path => "#{permissions_path}/LocationWhenInUse"
  pod 'Permission-Motion', :path => "#{permissions_path}/Motion"
  pod 'Permission-Notifications', :path => "#{permissions_path}/Notifications"
  pod 'Permission-FaceID', :path => "#{permissions_path}/FaceID"

  config = use_native_modules!

  # Flags change depending on the env values.
  flags = get_default_flags()

  use_react_native!(
    :path => config[:reactNativePath],
    # Hermes is now enabled by default. Disable by setting this flag to false.
    # Upcoming versions of React Native may rely on get_default_flags(), but
    # we make it explicit here to aid in the React Native upgrade process.
    :hermes_enabled => true,
    :fabric_enabled => flags[:fabric_enabled],
    # Enables Flipper.
    #
    # Note that if you have use_frameworks! enabled, Flipper will not work and
    # you should disable the next line.
    :flipper_configuration => FlipperConfiguration.enabled(["Debug"], {'Flipper' => '0.163.0'}),
    # An absolute path to your application root.
    :app_path => "#{Pod::Config.instance.installation_root}/.."
  )

  target 'MyExampleAppTests' do
    inherit! :complete
    # Pods for testing
  end

  post_install do |installer|
    react_native_post_install(
      installer,
      # Set `mac_catalyst_enabled` to `true` in order to apply patches
      # necessary for Mac Catalyst builds
      :mac_catalyst_enabled => false
    )
    __apply_Xcode_12_5_M1_post_install_workaround(installer)
  end
end

It seems this issue is not related to lottie-react-native. Will the build succeed if you uninstall lottie-react-native?

This is the error Xcode is throwing at me. Directly states lottie-react-native. I can try building without.
<module-includes>:1:9: note: in file included from <module-includes>:1:
#import "lottie-react-native-umbrella.h"
        ^
/Users/treeeest/Projects/WridzRefactorV2/ios/Pods/Headers/Public/lottie_react_native/lottie-react-native-umbrella.h:13:9: note: in file included from /Users/treeeest/Projects/WridzRefactorV2/ios/Pods/Headers/Public/lottie_react_native/lottie-react-native-umbrella.h:13:
#import "Bridging.h"
        ^
/Users/treeeest/Projects/WridzRefactorV2/node_modules/react-native/ReactCommon/react/bridging/Bridging.h:10:10: error: 'react/bridging/AString.h' file not found
#include <react/bridging/AString.h>
         ^
<unknown>:0: error: could not build Objective-C module 'lottie_react_native'

I also want to state this is only happening for Release builds. My debug builds have been working fine.

Also noting that my versions are slightly different. I was unsuccessfully able to get pods to install using the versions listed here
"lottie-ios": "3.2.3",
"lottie-react-native": "5.1.3",
"react-native": "^0.70.5",

My project "built" after removing lottie-react-native. It failed to resolve the module when bundling the index file. But other than that every other pod/package built successfully. I'm not going to go through my entire package and comment out Lottie. We utilize it in our splash screen, and it'll be a hassle. Please tag me if there's any updates

I was able to strangely get passed this issue. Maybe there was some caching issues in my pods? I'm not sure. But after trying to do the build without Lottie, I reinstalled the most recent version. Pods installed. App built.

Try it
yarn remove lottie-react-native
cd ios
pod install --repo-update
cd ..
yarn add lottie-react-native
cd ios
pod install --repo-update
cd ..
yarn ios

Same issue here in RN 0.71.1!!

We have updated all examples to RN 0.71.1 and we did not face this issue at all. Maybe there is something wrong in your dependencies or your environment. I would suggest you installing lottie-react-native on a bare project and see if still happens and let us know again.

I solved problem. I missed yarn add lottie-ios@3.4.0

Same issue, any solutions?

@mMarcos208  following @riku99 steps worked for me

lottie-ios

after deleting ios/build and also applying this patch to force last version of the lib it solved for me
diff --git a/node_modules/lottie-react-native/lottie-react-native.podspec b/node_modules/lottie-react-native/lottie-react-native.podspec
index 656fc69..d093697 100644
--- a/node_modules/lottie-react-native/lottie-react-native.podspec
+++ b/node_modules/lottie-react-native/lottie-react-native.podspec
@@ -23,7 +23,7 @@ Pod::Spec.new do |s|
   s.author                  = package["author"]
   s.homepage                = package["homepage"]

-  s.ios.deployment_target   = '12.4'
+  s.ios.deployment_target   = '13.0'
   s.osx.deployment_target   = '10.12'
   s.tvos.deployment_target  = '12.4'

@@ -33,7 +33,7 @@ Pod::Spec.new do |s|
     'Lottie_React_Native_Privacy' => ['ios/PrivacyInfo.xcprivacy'],
   }

-  s.dependency 'lottie-ios', '4.4.1'
+  s.dependency 'lottie-ios', '4.4.3'

   s.swift_version = '5.7'

authors: FadiAboMsalam JJalit SoohyungJung mMarcos208 matinzd riku99 rodgomesc roots-ai tristanheilman virginiab10


text:
tweak brew to work on intel mac too

atm brew stup opnly works on M series mac

done


text:
corrective import error

BETA 0.6.171:
# Error: NameError: file /mnt/rez/release/ext/vetala/0.6.15.sse.1.0.0/python/vtool/maya_lib/ui_core.py line 70: name 'selection_change_signal' is not defined
The error occurs when selecting anything in the scene after importing correctives.

This should be fixed with this pull
https://github.com/louisVottero/vtool/pull/258

repo: louisVottero/vtool


text:
Case insensitive sorting?

Is there any way to do case insensitive sorting? Any way at all?
I note Issue 150, but that was in 2014. Any progress?
Just a simple callback on two sort keys would solve the problem.

@david-pfx i just ran into this need as well--i think a sort callback would be a great way to solve this but since i don't think that's going to happen i'm going to solve for my project by denormalizing a document property just for sorting, e.g. saving the toLowerCase() version in a separate property

oh, this is actually the suggestion from #150 as well (creating sort keys)

there is also the compareStrings option to Datastore, but it's global to the Datastore (that may be fine for your use case, though!)

compareStrings (optional): function compareStrings(a, b) compares strings a and b and return -1, 0 or 1. If specified, it overrides default string comparison which is not well adapted to non-US characters in particular accented letters. Native localCompare will most of the time be the right choice

and for completeness' sake, an example:
    compareStrings: (a, b) => {
      return a.toLowerCase().localeCompare(b.toLowerCase());
    },

Yes, that does seem to be the state of play. One of these days I think I'm going to have to fork NeDB, but other things are taking priority right now.

MongoDB doesn't even support this functionality for sorting AFAIK, so I can't see NeDB adding it any time soon.
https://docs.mongodb.com/manual/reference/method/cursor.sort/

NeDB seems to not use compareStrings when comparison operators such as $lt and $gt are used.
Here's an example:
(async function () {
    const db = new Nedb({
      compareStrings: (a, b) => {
        return a.toLowerCase().localeCompare(b.toLowerCase());
      },
    });

    for (const title of ['A1', 'B', 'C', 'a2']) {
      await new Promise(resolve => db.insert({ title }, resolve));
    }

    function find(query) {
      return new Promise(resolve => db.find(query).sort({ title: 1 }).projection({ _id: 0 }).exec((err, res) => resolve(res)));
    }

    console.log(JSON.stringify({
      find: await find({}),
      find2: await find({ title: { $lt: 'a2' } }),
    }, null, 2));
  })();

The outcome is as follows:
{
  "find": [
    {
      "title": "A1"
    },
    {
      "title": "a2"
    },
    {
      "title": "B"
    },
    {
      "title": "C"
    }
  ],
  "find2": [
    {
      "title": "A1"
    },
    {
      "title": "B"
    },
    {
      "title": "C"
    }
  ]
}

If compareStrings worked with comparison operators then find2 would contain only A1. But judging from the outcome we can conclude that the lowercase title goes after the uppercase ones irrespective of the compareStrings option.

authors: JamesMGreene beaugunderson david-pfx polomoshnov

repo: louischatriot/nedb


text:
chore: update gamedig dep to 4.3.0

⚠⚠⚠ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma
Tick the checkbox if you understand [x]:

[x] I have read and understand the pull request rules.

Description
Updates the GameDig dependency from 4.2.0 to 4.3.0.
Node-GameDig 4.3.0 changelog:

Fix Post Scriptum not being on the valve protocol.
Added support for the Minecraft Better Compatibility Checker Mod.
Halo Online (ElDewrito) - Added support (by @Sphyrna-029)

Type of change
New feature (non-breaking change which adds functionality)
Checklist

[x] My code follows the style guidelines of this project
[ ] (not applicable) I ran ESLint and other linters for modified files
[x] I have performed a self-review of my own code and tested it
[x] I have commented my code, particularly in hard-to-understand areas (including JSDoc for methods)
[x] My changes generates no new warnings
[ ] My code needed automated testing. I have added them (this is optional task)

It is already in Uptime Kuma 1.23.9.

authors: CosminPerRam louislam

repo: louislam/uptime-kuma


text:
Differentiate the point paginations (p. 10) from the passages (pp. 10-15)

Actually hugo-cite, and in particular the shortcodes cite.html, is set up for the passages between one page to another indicated with a double "pp". But we need to cite with just a page indicated with a single "p".
For the implementation we can use the indication of the -.

Yes! Usage examples:

{{< cite Fauchie2020 20 >}} -> (Fauchié, 2020, p. 20)
{{< cite Fauchie2020 20-22 >}} -> (Fauchié, 2002, pp. 20-22)

Perfect :100:

authors: antoinentl loup-brun

repo: loup-brun/hugo-cite

license: WTFPL


text:
extend background property {r:0, g:0, b:0, alpha:0} can't be handled properly on Windows

tested sharp version: 0.17
On Windows platform the background option {r:0, g:0, b:0, a:0} is OK, alpha is properly handled.
But on macos, I must use {r:0, g:0, b:0, alpha:0}.
If I stick to {r:0, g:0, b:0, a:0} , I will get this error message:

I found the docs here http://sharp.dimens.io/en/stable/api-operation/#extend is also using the a for alpha.
I think this might be a bug

This is my bad

Hello, it looks like the example in the extend jsdoc is incorrect. As you correctly point out, alpha should be used here. I'm happy to accept a PR to correct this or can fix it myself when I get a moment.

@lovell  thanks, 😄  I could make one

@lovell  done.

authors: lovell zilongshanren

repo: lovell/sharp