Can you provide specific version information of the environment or is the configuration file in the Config file correct?

Hi,
Can you provide specific version information of the environment or is the configuration file in the Config file correct?
Are the configurations of the datasets in the Model Zoo chapter the same？all get in https://github.com/ayanban011/SwinDocSegmenter/blob/main/configs/coco/instance-segmentation/maskdino_R50_bs16_50ep_4s_dowsample1_2048.yaml？
I encountered some issues in Step 3: For testing the model, I loaded the model and configuration files, but encountered warning messages. I think it may be due to version issues, or whether these warning messages are normal. It seems that the forward predict results I received are also abnormal.
warnings as follows:
Environment info:

sys.platform                     linux
Python                           3.8.16 (default, Jun 12 2023, 18:09:05) [GCC 11.2.0]
numpy                            1.24.3
detectron2                       0.6
Compiler                         GCC 5.5
CUDA compiler                    CUDA 11.2
detectron2 arch flags            7.5
DETECTRON2_ENV_MODULE
PyTorch                          1.10.2
PyTorch debug build              False
torch._C._GLIBCXX_USE_CXX11_ABI  False
GPU available                    Yes
GPU 0                            GeForce RTX 2080 Ti (arch=7.5)
Driver version                   460.27.04
CUDA_HOME                        /usr/local/cuda-11.2
Pillow                           9.4.0
torchvision                      0.11.3
torchvision arch flags           3.5, 5.0, 6.0, 7.0, 7.5, 8.0, 8.6
fvcore                           0.1.5.post20221221
iopath                           0.1.9
cv2                              4.7.0

PyTorch built with:

GCC 7.3
C++ Version: 201402
Intel(R) oneAPI Math Kernel Library Version 2023.1-Product Build 20230303 for Intel(R) 64 architecture applications
Intel(R) MKL-DNN v2.2.3 (Git Hash 7336ca9f055cf1bfa13efb658fe15dc9b41f0740)
OpenMP 201511 (a.k.a. OpenMP 4.5)
LAPACK is enabled (usually provided by MKL)
NNPACK is enabled
CPU capability usage: AVX512
CUDA Runtime 11.3
NVCC architecture flags: -gencode;arch=compute_37,code=sm_37;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_61,code=sm_61;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_80,code=sm_80;-gencode;arch=compute_86,code=sm_86;-gencode;arch=compute_37,code=compute_37
CuDNN 8.2
Magma 2.5.2
Build settings: BLAS_INFO=mkl, BUILD_TYPE=Release, CUDA_VERSION=11.3, CUDNN_VERSION=8.2.0, CXX_COMPILER=/opt/rh/devtoolset-7/root/usr/bin/c++, CXX_FLAGS= -Wno-deprecated -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -fopenmp -DNDEBUG -DUSE_KINETO -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DSYMBOLICATE_MOBILE_DEBUG_HANDLE -DEDGE_PROFILER_USE_KINETO -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-sign-compare -Wno-unused-parameter -Wno-unused-variable -Wno-unused-function -Wno-unused-result -Wno-unused-local-typedefs -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-psabi -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Wno-stringop-overflow, LAPACK_INFO=mkl, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, TORCH_VERSION=1.10.2, USE_CUDA=ON, USE_CUDNN=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=ON, USE_MPI=OFF, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON,

[07/17 17:27:45 detectron2]: Command line arguments: Namespace(EVAL_FLAG=1, config_file='configs/coco/instance-segmentation/maskdino_R50_bs16_50ep_4s_dowsample1_2048_doc_publaynet.yaml', dist_url='tcp://<IP_ADDRESS>:10791', eval_only=True, machine_rank=0, num_gpus=1, num_machines=1, opts=['MODEL.WEIGHTS', 'weights/model_final_publay_swindocseg.pth'], resume=False)
[07/17 17:27:45 detectron2]: Contents of args.config_file=configs/coco/instance-segmentation/maskdino_R50_bs16_50ep_4s_dowsample1_2048_doc_publaynet.yaml:
BASE: Base-COCO-InstanceSegmentation.yaml
MODEL:
META_ARCHITECTURE: "MaskDINO"
SEM_SEG_HEAD:
NAME: "MaskDINOHead"
IGNORE_VALUE: 255
NUM_CLASSES: 5 # 11
LOSS_WEIGHT: 1.0
CONVS_DIM: 256
MASK_DIM: 256
NORM: "GN"
# pixel decoder
PIXEL_DECODER_NAME: "MaskDINOEncoder"
DIM_FEEDFORWARD: 2048
NUM_FEATURE_LEVELS: 3
TOTAL_NUM_FEATURE_LEVELS: 4
IN_FEATURES: ["res2", "res3", "res4", "res5"]
DEFORMABLE_TRANSFORMER_ENCODER_IN_FEATURES: ["res2","res3", "res4", "res5"]
COMMON_STRIDE: 4
TRANSFORMER_ENC_LAYERS: 6
FEATURE_ORDER: "low2high"
MaskDINO:
TRANSFORMER_DECODER_NAME: "MaskDINODecoder"
DEEP_SUPERVISION: True
NO_OBJECT_WEIGHT: 0.1
CLASS_WEIGHT: 4.0
MASK_WEIGHT: 5.0
DICE_WEIGHT: 5.0
BOX_WEIGHT: 5.0
GIOU_WEIGHT: 2.0
HIDDEN_DIM: 256
NUM_OBJECT_QUERIES: 300
NHEADS: 8
DROPOUT: 0.0
DIM_FEEDFORWARD: 1024
ENC_LAYERS: 0
PRE_NORM: False
ENFORCE_INPUT_PROJ: False
SIZE_DIVISIBILITY: 32
DEC_LAYERS: 9  # 9+1, 9 decoder layers, add one for the loss on learnable query
TRAIN_NUM_POINTS: 12544
OVERSAMPLE_RATIO: 3.0
IMPORTANCE_SAMPLE_RATIO: 0.75
EVAL_FLAG: 1
INITIAL_PRED: True
TWO_STAGE: True
DN: "seg"
DN_NUM: 100
INITIALIZE_BOX_TYPE: 'no'
TEST:
SEMANTIC_ON: False
INSTANCE_ON: True
PANOPTIC_ON: False
OVERLAP_THRESHOLD: 0.8
OBJECT_MASK_THRESHOLD: 0.25
DATASETS:
TRAIN: ("doc_train",)
TEST: ("doc_val",)
TEST: ("publaynet_minival",)
SOLVER:
AMP:
ENABLED: True
INPUT:
IMAGE_SIZE: 512
TEST:
EVAL_PERIOD: 5000
EVAL_FLAG: 1
OUTPUT_DIR: output/doc_publaynet
[07/17 17:27:58 d2.checkpoint.detection_checkpoint]: [DetectionCheckpointer] Loading from weights/model_final_publay_swindocseg.pth ...
[07/17 17:27:58 fvcore.common.checkpoint]: [Checkpointer] Loading from weights/model_final_publay_swindocseg.pth ...
WARNING [07/17 17:28:00 fvcore.common.checkpoint]: Skip loading parameter 'sem_seg_head.pixel_decoder.input_proj.0.0.weight' to the model due to incompatible shapes: (256, 192, 1, 1) in the checkpoint but (256, 256, 1, 1) in the model! You might want to double check if this is expected.
WARNING [07/17 17:28:00 fvcore.common.checkpoint]: Skip loading parameter 'sem_seg_head.pixel_decoder.input_proj.1.0.weight' to the model due to incompatible shapes: (256, 384, 1, 1) in the checkpoint but (256, 512, 1, 1) in the model! You might want to double check if this is expected.
WARNING [07/17 17:28:00 fvcore.common.checkpoint]: Skip loading parameter 'sem_seg_head.pixel_decoder.input_proj.2.0.weight' to the model due to incompatible shapes: (256, 768, 1, 1) in the checkpoint but (256, 1024, 1, 1) in the model! You might want to double check if this is expected.
WARNING [07/17 17:28:00 fvcore.common.checkpoint]: Skip loading parameter 'sem_seg_head.pixel_decoder.input_proj.3.0.weight' to the model due to incompatible shapes: (256, 1536, 1, 1) in the checkpoint but (256, 2048, 1, 1) in the model! You might want to double check if this is expected.
WARNING [07/17 17:28:00 fvcore.common.checkpoint]: Skip loading parameter 'sem_seg_head.pixel_decoder.transformer.level_embed' to the model due to incompatible shapes: (5, 256) in the checkpoint but (4, 256) in the model! You might want to double check if this is expected.
WARNING [07/17 17:28:00 fvcore.common.checkpoint]: Skip loading parameter 'sem_seg_head.pixel_decoder.transformer.encoder.layers.0.self_attn.sampling_offsets.weight' to the model due to incompatible shapes: (320, 256) in the checkpoint but (256, 256) in the model! You might want to double check if this is expected.
WARNING [07/17 17:28:00 fvcore.common.checkpoint]: Skip loading parameter 'sem_seg_head.pixel_decoder.transformer.encoder.layers.0.self_attn.sampling_offsets.bias' to the model due to incompatible shapes: (320,) in the checkpoint but (256,) in the model! You might want to double check if this is expected.
WARNING [07/17 17:28:00 fvcore.common.checkpoint]: Skip loading parameter 'sem_seg_head.pixel_decoder.transformer.encoder.layers.0.self_attn.attention_weights.weight' to the model due to incompatible shapes: (160, 256) in the checkpoint but (128, 256) in the model! You might want to double check if this is expected.
WARNING [07/17 17:28:00 fvcore.common.checkpoint]: Skip loading parameter 'sem_seg_head.pixel_decoder.transformer.encoder.layers.0.self_attn.attention_weights.bias' to the model due to incompatible shapes: (160,) in the checkpoint but (128,) in the model! You might want to double check if this is expected.
WARNING [07/17 17:28:00 fvcore.common.checkpoint]: Skip loading parameter 'sem_seg_head.pixel_decoder.transformer.encoder.layers.0.linear1.weight' to the model due to incompatible shapes: (512, 256) in the checkpoint but (2048, 256) in the model! You might want to double check if this is expected.
WARNING [07/17 17:28:00 fvcore.common.checkpoint]: Skip loading parameter 'sem_seg_head.pixel_decoder.transformer.encoder.layers.0.linear1.bias' to the model due to incompatible shapes: (512,) in the checkpoint but (2048,) in the model! You might want to double check if this is expected.
WARNING [07/17 17:28:00 fvcore.common.checkpoint]: Skip loading parameter 'sem_seg_head.pixel_decoder.transformer.encoder.layers.0.linear2.weight' to the model due to incompatible shapes: (256, 512) in the checkpoint but (256, 2048) in the model! You might want to double check if this is expected.
WARNING [07/17 17:28:00 fvcore.common.checkpoint]: Skip loading parameter 'sem_seg_head.pixel_decoder.transformer.encoder.layers.1.self_attn.sampling_offsets.weight' to the model due to incompatible shapes: (320, 256) in the checkpoint but (256, 256) in the model! You might want to double check if this is expected.
WARNING [07/17 17:28:00 fvcore.common.checkpoint]: Skip loading parameter 'sem_seg_head.pixel_decoder.transformer.encoder.layers.1.self_attn.sampling_offsets.bias' to the model due to incompatible shapes: (320,) in the checkpoint but (256,) in the model! You might want to double check if this is expected.
WARNING [07/17 17:28:00 fvcore.common.checkpoint]: Skip loading parameter 'sem_seg_head.pixel_decoder.transformer.encoder.layers.1.self_attn.attention_weights.weight' to the model due to incompatible shapes: (160, 256) in the checkpoint but (128, 256) in the model! You might want to double check if this is expected.
WARNING [07/17 17:28:00 fvcore.common.checkpoint]: Skip loading parameter 'sem_seg_head.pixel_decoder.transformer.encoder.layers.1.self_attn.attention_weights.bias' to the model due to incompatible shapes: (160,) in the checkpoint but (128,) in the model! You might want to double check if this is expected.
WARNING [07/17 17:28:00 fvcore.common.checkpoint]: Skip loading parameter 'sem_seg_head.pixel_decoder.transformer.encoder.layers.1.linear1.weight' to the model due to incompatible shapes: (512, 256) in the checkpoint but (2048, 256) in the model! You might want to double check if this is expected.
WARNING [07/17 17:28:00 fvcore.common.checkpoint]: Skip loading parameter 'sem_seg_head.pixel_decoder.transformer.encoder.layers.1.linear1.bias' to the model due to incompatible shapes: (512,) in the checkpoint but (2048,) in the model! You might want to double check if this is expected.
WARNING [07/17 17:28:00 fvcore.common.checkpoint]: Skip loading parameter 'sem_seg_head.pixel_decoder.transformer.encoder.layers.1.linear2.weight' to the model due to incompatible shapes: (256, 512) in the checkpoint but (256, 2048) in the model! You might want to double check if this is expected.
WARNING [07/17 17:28:00 fvcore.common.checkpoint]:
Could you give me some advice or helpful information about the problem ? thank you!

Updated Config files. The warnings are due to the image size mismatch.

@ jianfengzhai I am running into the same issue and I see that @ayanban011 advised you to modify the config files to fix the image size mismatch.  I have been looking through the .yaml file and I am not sure what values I need to change.  Any suggestions?
_BASE_: Base-COCO-InstanceSegmentation.yaml
MODEL:
  META_ARCHITECTURE: "MaskDINO"
  SEM_SEG_HEAD:
    NAME: "MaskDINOHead"
    IGNORE_VALUE: 255
    NUM_CLASSES: 11
    LOSS_WEIGHT: 1.0
    CONVS_DIM: 256
    MASK_DIM: 256
    NORM: "GN"
    # pixel decoder
    PIXEL_DECODER_NAME: "MaskDINOEncoder"
    DIM_FEEDFORWARD: 2048
    NUM_FEATURE_LEVELS: 3
    TOTAL_NUM_FEATURE_LEVELS: 4
    IN_FEATURES: ["res2", "res3", "res4", "res5"]
    DEFORMABLE_TRANSFORMER_ENCODER_IN_FEATURES: ["res2","res3", "res4", "res5"]
    COMMON_STRIDE: 4
    TRANSFORMER_ENC_LAYERS: 6
    FEATURE_ORDER: "low2high"
  MaskDINO:
    TRANSFORMER_DECODER_NAME: "MaskDINODecoder"
    DEEP_SUPERVISION: True
    NO_OBJECT_WEIGHT: 0.1
    CLASS_WEIGHT: 4.0
    MASK_WEIGHT: 5.0
    DICE_WEIGHT: 5.0
    BOX_WEIGHT: 5.0
    GIOU_WEIGHT: 2.0
    HIDDEN_DIM: 256
    NUM_OBJECT_QUERIES: 300
    NHEADS: 8
    DROPOUT: 0.0
    DIM_FEEDFORWARD: 1024
    ENC_LAYERS: 0
    PRE_NORM: False
    ENFORCE_INPUT_PROJ: False
    SIZE_DIVISIBILITY: 32
    DEC_LAYERS: 9  # 9+1, 9 decoder layers, add one for the loss on learnable query
    TRAIN_NUM_POINTS: 12544
    OVERSAMPLE_RATIO: 3.0
    IMPORTANCE_SAMPLE_RATIO: 0.75
    EVAL_FLAG: 1
    INITIAL_PRED: True
    TWO_STAGE: True
    DN: "seg"
    DN_NUM: 100
    INITIALIZE_BOX_TYPE: 'no'
    TEST:
      SEMANTIC_ON: False
      INSTANCE_ON: True
      PANOPTIC_ON: False
      OVERLAP_THRESHOLD: 0.8
      OBJECT_MASK_THRESHOLD: 0.25
DATASETS:
  TRAIN: ("doc_train",)
  TEST: ("doc_val",)
SOLVER:
  AMP:
    ENABLED: True
TEST:
  EVAL_PERIOD: 5000
#  EVAL_FLAG: 1
OUTPUT_DIR: "/home/ubuntu/git/doc_segmenter/data2/output_doclay_comp_Res"

Please change the DIM_FEEDFORWARD value of the SEM_SEG_HEAD as well as MasKDINO  based on your current input image size

Well I answered my own question above.  It turns out that with all the .YAML files if I switch to the .YAML file that matches the model weights then the image sizes are correct and it works with all warning messages gone.


Appendix with implementation advice for avoiding common pitfalls

Large batches in the Write RPC can cause gRPC to error with RESOURCE_EXHAUSTED, because the default maximum size for metadata is very low.  This new section shows how to avoid that.

Thanks for proposing adding a section like this.  I do not have enough detailed knowledge of gRPC to review these changes, but the question I asked in this issue https://github.com/p4lang/p4runtime/issues/125 and Antonin's response, while not exactly the same topic as your changes discuss, seem closely related (max metadata size vs. maximum message size).  If there is anything worth adding to what you wrote here on the maximum message size, and why increasing it might be useful for enabling larger binary blobs to be sent, that sounds useful.

Thanks Andy for pointing that out.  I agree that the maximum message size is also something we should point out, maybe we can do that in a follow-up PR.  The metadata size is probably a bigger problem, because the limit is so small, so it seems quite common to run into this.

@jafingerhut That is a good point. I actually brought that up with Stefan earlier and was planning on having a follow-up PR to his.


Design feedback

This PR fixes the missing baseurl in the _config.yml file and defaults it to /. While browsing the site, I found it incredibly hard to see links in the content body. I've added an underline to all content body links.
The only place I've noticed "odd" behavior is when the link contains code block, in which I question whether a code tag should even be in a link.
Issue Reference: #281

This is great, thank you @jakefolio!  Improvements to the UI/UX are always welcomed.
@pragmaticivan / @pjhampton — any thoughts before I merge?

LGTM :+1:

Something tells me that we should go using baseurl instead the one we're using now.
Not clear but looks like we can avoid the problem change urls just updating the README and passing a flag to tell the server to use localhost:

We need a little bit more of research.

Thank @jakefolio.  @pragmaticivan if you want to look into that, I'd be grateful!


Impressive test coverage

Nice to meet you and thanks for sharing the tech details in the blog!
May I ask how you prioritize which part of SOQL syntax to implement first? Based on your usage in work, how convenient to implement or both?

@nobodxbodon
No problem, man!
It's really simple, I first prioritized building a mechanism to mock queries by hand, i.e. by setting explicit return values. This was to ensure there's always a backup approach to allow someone to use Moxygen even if at the time a query isn't supported.
I then prioritized common queries first and gradually built out support for more and more complex ones. What I determined as "common" was just whatever I used most at work.

Got it thanks. I'll use some queries in mock-soql-database/main/default/classes/database/mock-database-tests/MockDatabaseTest.cls when building the prototype.
BTW are you able to use Python and pip install at work? Because I was planning to publish the prototype on PyPI.

@nobodxbodon
Sorry for the delayed response, I've been a bit pre-occupied studying up for tech interviews. I can use Python, but there's already been conversations about using Moxygen at work - and unfortunately my job would likely try to claim it if I ever used it in their codebase. So it depends how dependent on Moxygen your project is.

Closing the issue due to inactivity.


Inheriting the implicit style not working fine in WinUI 3 for desktop

I have a custom control CustomControl1
public class CustomControl1 : Control
{
    public CustomControl1()
    {
        this.DefaultStyleKey = typeof(CustomControl1);
    }
}

Whose implicit style is
    <Style TargetType="local:CustomControl1">
        <Setter Property="Background" Value="Green"/>
        <Setter Property="Template">
            <Setter.Value>
                <ControlTemplate TargetType="local:CustomControl1">
                    <Border
                        Background="{TemplateBinding Background}"
                        BorderBrush="{TemplateBinding BorderBrush}"
                        BorderThickness="{TemplateBinding BorderThickness}">
                    </Border>
                </ControlTemplate>
            </Setter.Value>
        </Setter>
    </Style>

And a second custom control CustomControl2, inheriting CustomControl1
public class CustomControl2 : CustomControl1
{
    public CustomControl2()
    {
        DefaultStyleKey = typeof(CustomControl2);
    }
}

whose implicit style only sets the Background
    <Style TargetType="local:CustomControl2">
        <Setter Property="Background" Value="Red"/>
    </Style>

The problem is the "Template" of CustomControl1 is not inherited automatically. Therefore nothing is rendered.
This looks as a bug as the implicit style of CustomControl2 doesn't override Template, so it should take the parent one.
In case that were intentional, there should be at least a way to base the style on the parent control implicit style, I couldn't find anything, x:Type doesn't exist in WinUI. Is there any way round?
Here the repo project App12.zip

@arivoir have you tried naming your CustomControl1 Style and then using it as argument for BasedOn parameter?
Likes this:
`

<Style TargetType="local:CustomControl2" BasedOn="{StaticResource DefaultCustomControl1Style}"/>

@arivoir try like this:
  <Style TargetType="local:CustomControl1" BasedOn="{StaticResource DefaultCustomControl1Style}" />
        <Style TargetType="local:CustomControl2" BasedOn="{StaticResource DefaultCustomControl1Style}">
            <Setter Property="Background" Value="Red"/>
        </Style>

        <Style x:Key="DefaultCustomControl1Style" TargetType="local:CustomControl1">
            <Setter Property="Background" Value="Green"/>
            <Setter Property="Template">
                <Setter.Value>
                    <ControlTemplate TargetType="local:CustomControl1">
                        <Border
                        Background="{TemplateBinding Background}"
                        BorderBrush="{TemplateBinding BorderBrush}"
                        BorderThickness="{TemplateBinding BorderThickness}">
                        </Border>
                    </ControlTemplate>
                </Setter.Value>
            </Setter>
        </Style>

@beervoley  using a shared name is not an option as the controls are in different assemblies (I put both in the same project to make the repo sample easier)

I think this is by design, when an item is added to the visual tree the system will search for an unnamed style of the same type to apply, it will then merge that unnamed style with the metadata defined default style. In this case the your CustomControl2's meta data defined default style is the style with just the background property set, so there is nothing to merge with.  In this case, I would suggest that you created a named style for CustomControl1 and have both your CustomControl1 and CustomControl2 unnamed styles be based off the named one.

Using a named resource will only work if you are the owner of the control inheriting and if both are in the same resource dictionary. But what about the other cases?

@arivoir Given the current constraint, I think you best bet is to wrap the control instead of inheriting it. If you need those properties/methods, then you will need to use the adapter pattern to adapt one by one.

To put this in context, I'm developing a suite of controls, so I'm looking for a maintainable solution, adapting every control or making copies of the template is a real problem and the reason why the platform must solve this.

I see 2 posible solutions

Change the platform so the implicit styles are automatically composed by its style and its ancestors implicit styles
Provide a way to allow specifying BasedOn="local:CustomControl" this way the inherited control base its implicit type in the implicit type of its ancestor

This is still a big issue. Is there any light in the horizon?

It only grew stale because no one from Microsoft ever responded.

Any solution to this problem in recent releases?

If I understand your situation correctly, you have Control1 in assembly A, and Control2 in assembly B. Control2 inherits Control1.
In this case, in your control 2's style
<Style TargetType="local:CustomControl2">
        <Setter Property="Background" Value="Red"/>
    </Style>

you just need to declare this style is based on control 1:
        <Setter Property="Background" Value="Red"/>
    </Style>

For your user of control2, it should work, as in, the system should be able to find Control1Style for your control2, regardless of whether control1 is in another assembly, as long as:

Both assembly A and B is available for your user's app
The generic.xaml of assembly A is available for your user's app
If Control1Style is defined elsewhere, it is included in your user's Application.xaml's resource dictionary at appropriate location (i.e. XamlControlResources's merged dictionary)

@legistek Yes. If not it's a bug. The naming convention is DefaultXXxStyle. Eg. .button has DefaultButtonStyle. You can start searching your control's styles from check https://github.com/microsoft/microsoft-ui-xaml/tree/winui3/release/1.5.3/controls/dev/CommonStyles


Test Release 3

All issues in the Release 3 is now completed and it's almost time for a final release. After 3 long months I'm looking forward to try it out!
Test it!
Windows:
Test the Windows packaged development version and make sure it runs.
https://bintray.com/artifact/download/konstructs/windows/konstructs-client.zip
Linux:
Test the Linux packaged development version and make sure it runs.
https://bintray.com/artifact/download/konstructs/linux/konstructs-client.tar.bz2
Linux:
Test the Linux deb on a Debian based system and make sure it runs.
https://bintray.com/artifact/download/konstructs/linux/konstructs-client.tar.bz2
OS X (not required):
There are no packages yet, so there is nothing to test. A compile and a sanity check from master is nice to have but not required.
Report problems

Open a new issue report the problem.
Add [BUG R3] to the subject for easy identification.
Add Ref #141 to the bottom of the issue.

Questions and any other questions, use this issue or Gitter

I can do the windows test :)

Awesome!

Thank you all for all the help, both Linux and Windows version are tested and verified working!


Oss secure option default to true, Fix doc error

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "fix-oss-doc-error" git@github.com:farmerworking/distribution.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

https://github.com/docker/distribution/blob/master/registry/storage/driver/oss/oss.go#L140-L147


ReferenceError: before is not defined

I'm trying to make some tests with Mocha for my Sails application. As described here.
I have files:
test/mocha.opts:
--require test/bootstrap.test.js

test/bootstrap.test.js:
var Sails = require('sails'), sails;

before(function(done) {
  Sails.lift({
    // configuration for testing purposes
  }, function(err, server) {
    sails = server;
    if (err) return done(err);
    // here you can load fixtures, etc.
        console.log("Sails Loaded");
    done(err, sails);
  });
});

after(function(done) {
  // here you can clear fixtures, etc.
  sails.lower(done);
});

test/unit/model/User.test.js
/* global describe, User */

describe.only('UserModel', function() {

    describe('#find()', function() {
        it('should check find function', function(done) {
            User.find()
                            .then(function(results) {
                                console.log(results);
                                done();
                            })
                            .catch(done);
        });
    });

});

When I'm running tests, I see an error:
...
test\bootstrap.test.js:4
before(function(done) {
^
ReferenceError: before is not defined
...

You don't declare suites, tests or hooks on --required files.
Instead, you could require(...) helpers in your spec/test files, and execute methods that define those hooks.
require('./setup.js')()

describe(..., function () {
  it(...)
})

To clarify, --required files are require(...)d once by the CLI even before a Mocha instance is created, so they are useful for one time setup of globals and stuff.
e.g, you can execute require('chai').should() in your --required file to avoid doing so in each of your test files.

Thans for explanation  and for solution @dasilvacontin!
I solved it by simply running test/bootstrap.test.js through  test/mocha.opts:
test/bootstrap.test.js

@elennaro what do you mean by:

I solved it by simply running test/bootstrap.test.js through test/mocha.opts:

you just put that line as the first line in your test/mocha.opts ?

Yes @aventurella
Here's my mocha opts:
--silly
--full-trace
--timeout 20000
test/bootstrap.test.js

I was also getting below mentioned error.

global.window.beforeEach = beforeEach;
^
ReferenceError: beforeEach is not defined

I changed --require to --required and now its working fine.
My application mocha.opt
--compilers js:babel-register,jsx:babel-register
--recursive
--colors
--reporter list
--required ./test/setup.js

Hi guys, I just find using async call in the required file will solve this problem:
setTimeout(() => {
  beforeEach(async () => {
    // ***
  });

  afterEach(async () => {
    // ***
  });
});

@tianjianchn it only works for beforeEach and afterEach, before and after still suck

I got the same error, but the reason was that I was using tdd, which uses suiteSetup instead of before.

For me what worked was the following:
From docs:

Mocha loads modules specified by --require
If a file loaded this way contains known Mocha-specific exports (e.g., root hook plugins), Mocha “registers” these
If not, Mocha ignores any exports of a --require’d module

// common JS

exports.mochaHooks = {
  beforeEach(done) {
    // do something before every test
    done();
  }
};

// with ES Modules

export const mochaHooks = {
  beforeEach(done) {
    // do something before every test
    done();
  }
};


Unexpected behavior

Cases:
K is negative:
const quickselect = require('quickselect');

const numbers = [1, 2, 3, 4];
quickselect(numbers, -99999);

console.log(numbers); // [ 3, 4, 2, undefined, '-99999': 1 ]

K is greater than numbers.length:
const quickselect = require('quickselect');

const numbers = [1, 2, 3, 4];

quickselect(numbers, 99999);
console.log(numbers); // [ 3, 4, undefined, 1, <99995 empty items>, 2 ]

I'd consider this a documentation issue:

The array should have at least one element. The bounds are non-negative integers smaller than array's length. left should be smaller than or equal to right, and k must be in range. Proceeding otherwise leads to undefined behavior.

The calling code is in control, and can check for out of bounds errors if it doesn't directly control what's going in.


[Feature]: Rethinking package classes design pattern.

Description
Hey @nidhaloff, I have a question related to the design pattern followed in this class. For me it looks redundant. Take a look at its usage in the tests:
https://github.com/nidhaloff/b-rabbit/blob/f71ed6ed953db752dc72c1d34d9557a2406fd391/tests/test_b_rabbit.py#L10-L11
In order to create an EventPublisher, you have to call the inner class and pass the outer reference, BRabbit, as a parameter to the __init__ function:
https://github.com/nidhaloff/b-rabbit/blob/f71ed6ed953db752dc72c1d34d9557a2406fd391/tests/test_b_rabbit.py#L23
It kind of looks unnecessary to do so since you already have the outer reference, the BRabbit instance. It looks like a self-reference problem or something of that nature. Also, I think this way it will allocate unnecessary space in memory.
Solution
All Inner classes should be moved outside the BRabbit class for better design.

@wiseaidev Good idea. Unfortunately, I can't remember the reason for this design. It has been years since I worked on this. Would you be interested to contribute your ideas? I can add you as a direct contributor to this repo in order to give you more freedom.

Yup!

@wiseaidev Done!


MSID: 99611 Version: 1 DOI: 10.1101/2<IP_ADDRESS>4825

MSID: 99611
Version: 1
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>4825
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=99611
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>4825

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/99611v1
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>4825
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/99611/v1/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

warn: [journal-ref-text-content] This journal reference (id c5) has untagged textual content - , Z. (. Is it tagged correctly?
warn: [journal-ref-text-content] This journal reference (id c10) has untagged textual content - , A. (. Is it tagged correctly?


babel-polyfill

WalletConnect/walletconnect-monorepo#48

Looking to solve this for soon for both walletconnect, eth-registry and dapparatus

Replacing @babel/polyfill with idempotent-babel-polyfill
https://www.npmjs.com/package/idempotent-babel-polyfill
I will submit a PR in a second

Fixed on #16


[NEED HELP] Vee-validate not working as expected in localhost, but in Codepen works well

Versions:

VueJs: 2.5.2
Vee-Validate: 2.10 beta-7

Description:
System: Windows 8.1
Directory File: C:\xampp\htdocs\ {myproject}
Steps To Reproduce:
#vuetify #vee-validate
I have a problem with password confirmation. no error whatsoever on my local console. the rest of story is on the title and the code below
codepen: https://codepen.io/dhika345/pen/QBYzEB
pastebin.com: https://pastebin.com/EK3Q3mHV
codepen works well: image

localhost error: image

Codepen uses the stable 2.0.9 version. There was a bug in 2.1.0-beta.7 that prevented Vue components from validating in some cases.  It produces the same results in your screenshot if you used 2.1.0-beta.7 in codepen.
The next version should fix your code, but there is one issue remaining, in the beta releases confirmed requires a ref to be present on the target field, so you need to add this to your pw_confirm field:
data-vv-name="password"
name="pw_confirm"
ref="pw_confirm" <--- Must add this
 v-validate=" 'required|min:8' "


Add GoWebApp as a project that uses Bolt.

Added GoWebApp as a project that uses Bolt.

Awesome, thanks! :+1:

Great, thanks!


Adding Support for Laravel 9

This PR "adds" support for Laravel 9 by:

Declaring support for illuminate/encryption version ^9.0, which contains no breaking changes I am aware of.
Adding Support for PHP 8 and 8.1 in both composer.json, as 8 is the new minimum version.
Additing testing support for PHP ^8.0 in Travis CI.

Simple testing of php artisan credentials:edit and the crendentials(key) helper in Laravel 9 show the output working as expected. Great success?

Since it might take a little while for BeyondCode to merge this or do it themselves, feel free to use my forked repository by telling composer.json about it like this.
"repositories": [
{
  "type": "vcs",
  "url": "https://github.com/mknooihuisen/laravel-credentials.git"
}],
"require": {
    "php": "^8.0",
    "beyondcode/laravel-credentials": "dev-master",
    ...
}

I have no desire to replace Marcel, so, if and when I find out Official Laravel 9 support exists, I'll deprecate my version with a note to revert to the official package.

This project appears no longer maintained, thanks for this.


Safe creation - Inconsistent policies when removing an owner from the list

Env: https://pr2084--safereact.review.gnosisdev.com/rinkeby/app/#/open
Steps:
Create a safe
Set 2 owners in the owners list
Set the policies in "2 out of 2" owners
Remove one owner
Result:
The policies dropdown will show empty
You can go to the review step, were you will see the messages "2 out of 1" owners.
Snapshot:

I just reproduce this one.
The Safe ultimately won't be created since the creation tx fails.
I would close this one mark as "won't fix" since a user sees "2 out of 1" on the review screen and thus should realize that this won't work.
Happy to reopen if that's an actual issue for externals.


Can't restore model

Hi,
Still not able to restore the model. Tried all combinations of model path, including calling tf.train.latest_checkpoint() .
I keep getting messages that the variable names don't match the checkpoint.
I should mention that I am using tf 1.13, because if I use the default line pip3 install -r requirements.txt I get tf version 2.2.0, and when I try to run with it I get error messages about placeholders, so I figured a lower version is required.
Thanks
Tsubu

@tsubu01 1. git pull update the code repo 2. Download new pretrained model here https://www.dropbox.com/sh/0b6r0ljqi76kyg9/AADedYWO3bnx4PhK1BmbJkJKa?dl=0 3. Make sure you have use the right way to restore model from ckpt file:)

Thanks @MaybeShewill-CV ! Now it works! (with TF1.13.1, doesn't work with TF2.2.0).
Tsubu

@tsubu01 Welcome:)


ExtraData: unpack(b) received extra data.

model in init = True
 ExtraData: unpack(b) received extra data.
---------------------------------------------------------------------------
ExtraData                                 Traceback (most recent call last)
<ipython-input-6-3f11485ad4f8> in <module>
----> 1 neuralcoref.add_to_pipe(nlp)

/workspace/neuralcoref_02/neuralcoref_with_training_mods/neuralcoref/__init__.py in add_to_pipe(nlp, **kwargs)
     40
     41 def add_to_pipe(nlp, **kwargs):
---> 42     coref = NeuralCoref(nlp.vocab, **kwargs)
     43     nlp.add_pipe(coref, name="neuralcoref")
     44     return nlp

neuralcoref.pyx in neuralcoref.neuralcoref.NeuralCoref.__init__()

neuralcoref.pyx in neuralcoref.neuralcoref.NeuralCoref.from_disk()

/opt/conda/lib/python3.6/site-packages/thinc/neural/_classes/model.py in from_bytes(self, bytes_data)
    353
    354     def from_bytes(self, bytes_data):
--> 355         data = srsly.msgpack_loads(bytes_data)
    356         weights = data[b"weights"]
    357         queue = [self]

/opt/conda/lib/python3.6/site-packages/srsly/_msgpack_api.py in msgpack_loads(data, use_list)
     27     # msgpack-python docs suggest disabling gc before unpacking large messages
     28     gc.disable()
---> 29     msg = msgpack.loads(data, raw=False, use_list=use_list)
     30     gc.enable()
     31     return msg

/opt/conda/lib/python3.6/site-packages/srsly/msgpack/__init__.py in unpackb(packed, **kwargs)
     58         object_hook = kwargs.get('object_hook')
     59         kwargs['object_hook'] = functools.partial(_decode_numpy, chain=object_hook)
---> 60     return _unpackb(packed, **kwargs)
     61
     62

_unpacker.pyx in srsly.msgpack._unpacker.unpackb()

ExtraData: unpack(b) received extra data.

What iam doing wrong?

Could you post the code you run when this error is thrown, and details on how you installed neuralcoref and spacy?

@svlandeg I think he encountered this error while trying to load a new trained model. Currently, we all having this problem, can you please give us an instruction to load a new trained model (trained by neuralcoref) using the add_to_pipe function?
Thank you!

yes please!^^ We are already on the verge of developing a new model, because we have already wasted so much time with the German model.

I understand you are frustrated, but please consider that it is very difficult for us to follow up on user's issues when only presented with a raw stack trace, no example code or software/model versions, and phrasings like "we all having this problem".
We need some more context - but please stick to the specific issue in each thread. Let's try to keep the discussion focused on one issue at the time, or it simply gets too complicated to address.
@snape6666 : which versions of neuralcoref, spacy and de_core_news_md are you using? Have you recently upgraded to spacy v.2.3? Did you upgrade the model as well? Was this working on 2.2.3 or not?

For this test i was using spacy 2.1.0 with the 2.1.0 model. neuralcoref in the newest version.

This was the step that a friendly guy did and also the way I trained my Dutch model this way.
For you @snape6666, I think you are not alone as this guy already posted this question with exactly the same error.
Can you please share with me maybe the way you did to export the trained model to this?

Hi @EricLe-dev : please, it is becoming increasingly difficult to follow the thread of an issue as you're constantly mixing in your specific questions and problems in other's threads. Please also stop pinging maintainers as this makes our GH mentions really hard to use.

Hi svlandeg,
his questions are related to my problem. My students are just summarizing how we created our model. I agree with EricLe-dev that the error is in the model generation and therefore it does not load properly. The answer should come in the next few minutes.

For this test i was using spacy 2.1.0 with the 2.1.0 model. neuralcoref in the newest version.
@snape6666

the englisch Model loads fine. But when i try to load my self trained model, it throws this error.

So the error gets thrown with a model you've trained and stored to disk? Not with de_core_news_md ?

yes!! the de_core_news_md works fine! Its the self trained neuralcoref model

I asked you to produce a code snippet that throws the error, and you gave one with de_core_news_md. Then it turns out, that is not the problem. I'm sorry, but I really can't try and reproduce your error like this.

I think the error is a result of using the wrong data in the neuralcoref_cache. We did the following to extract the model and save it to disk:

Install the alpha version of thinc, as this version includes the PyTorchWrapper
Create an Instance of the model in a python shell. I basically used the same instantiation that is >used in train/dataset.py: from neuralcoref.train.model import Model
model = Model(len(voc), SIZE_EMBEDDING, Args.h1, Args.h2, Args.h3, SIZE_PAIR_IN, >SIZE_SINGLE_IN)
Adjust the parameters according to the ones you used during traininig.
Load the model checkpoint you want to use: >model.load_state_dict(torch.load(path_to_checkpoint_file)) You can find this in train/learn.py.
If everything worked so far you should see a message, that all keys could be matched and if you >call the model, you should see  different parts of the net labeled (word_embeds), (drop), (pair_top) >and (single_top).
As far as I could tell the (pair_top) and (single_top) parts are used in the model that is loaded >from neuralcoref cache. I think to avoid exporting the  dropout layers used in training you need to >change the model to evaluation mode using model.eval()
6.You can now use the PyTorchWrapper from the thinc alpha.
from thinc.api import PyTorchWrapper
pair_top_model = PyTorchWrapper(model.pair_top)
single_top_model = PyTorchWrapper(model.single_top)
These models can now be written to disk using:
f = open('trained_pair_top_model', 'wb')
f.write(pair_top_model.to_bytes())
f.close()

We then replaced the files in the neuralcoref_cache. As I stated in another issue I'm not sure if this is even the correct way of starting to replace the model used by neuralcoref.

yes please!^^ We are already on the verge of developing a new model, because we have already wasted so much time with trying to fix loading our own German model.
The Code, with custom Model:
import de_core_news_md
import logging;
logging.basicConfig(level=logging.INFO)
import neuralcoref
INFO:neuralcoref:Loading model from /root/.ger_neuralcoref_cache/neuralcoref

nlp = spacy.load("de_core_news_md")
neuralcoref.add_to_pipe(nlp)

as you see here my last line in the code is the neuralcoref.add_to_pipe(nlp)
Here i try to load the new model, and then i get the error shown in the first comment

Hi svlandeg,
his questions are related to my problem. My students are just summarizing how we created our model (...) The reply of my students should come in the next few minutes.

Can you please clarify which github handles you are referring to? Who are your students? Are they all working on the same assignment?
That helps me to follow the discussion.

Sorry for the confusion.
chieter is one oy my students.

Ok, good to know. And by the alpha version of thinc, you mean thinc 8?

Yes, I used pip install thinc==8.0.0a1 .

Ok. Unfortunately, Thinc 8 and spaCy 2 aren't compatible. We're currently working on a major release spaCy v.3 which will use thinc 8. A lot of the internals are different and not backwards compatible, so I couldn't imagine how this would ever work.
Due to the work on spaCy 3, we haven't had the bandwith to provide full support for neuralcoref. We do want to bring the code up-to-date with Thinc 8 and spaCy 3, but this will have to wait until we get a first release out for spaCy 3.
Also, just FYI, I haven't myself tried training a new model with neuralcoref, as I wasn't involved in the original development of this code base.

Thanks for your reply :)
My colleague just informed me, that it is indeed unneccessary to use the thinc 8 version, as PyTorchWrapper is available in earlier releases but was relocated. So i mistakenly assumed it was added later. I will try to use an earlier version of thinc, maybe this will resolve some issues.
Best wishes to you! I'm looking forward to spacy v3 :)

I think the error is a result of using the wrong data in the neuralcoref_cache. We did the following to extract the model and save it to disk:

Install the alpha version of thinc, as this version includes the PyTorchWrapper
Create an Instance of the model in a python shell. I basically used the same instantiation that is >used in train/dataset.py: from neuralcoref.train.model import Model
model = Model(len(voc), SIZE_EMBEDDING, Args.h1, Args.h2, Args.h3, SIZE_PAIR_IN, >SIZE_SINGLE_IN)
Adjust the parameters according to the ones you used during traininig.
Load the model checkpoint you want to use: >model.load_state_dict(torch.load(path_to_checkpoint_file)) You can find this in train/learn.py.
If everything worked so far you should see a message, that all keys could be matched and if you >call the model, you should see  different parts of the net labeled (word_embeds), (drop), (pair_top) >and (single_top).
As far as I could tell the (pair_top) and (single_top) parts are used in the model that is loaded >from neuralcoref cache. I think to avoid exporting the  dropout layers used in training you need to >change the model to evaluation mode using model.eval()
6.You can now use the PyTorchWrapper from the thinc alpha.
from thinc.api import PyTorchWrapper
pair_top_model = PyTorchWrapper(model.pair_top)
single_top_model = PyTorchWrapper(model.single_top)
These models can now be written to disk using:
f = open('trained_pair_top_model', 'wb')
f.write(pair_top_model.to_bytes())
f.close()

We then replaced the files in the neuralcoref_cache. As I stated in another issue I'm not sure if this is even the correct way of starting to replace the model used by neuralcoref.

Thank you for taking your time and trying to understand the problem with us svlandeg! =)
We are sure that the error occurs because of the pairs_model and single_model.
The error actually occured also with earlier versions of thinc (e.g. 7.0.8).
Additionally to the described procedure of @chieter, we came up with the idea to create the required key2row and vectors file in the static_vectors folder and tuned_vectors folder respectively with the (command line command)[https://spacy.io/api/cli#init-model] and only moved the key2row and vectors file in the respective folders.
In order to use that command we merged prior to that the ./neuralcoref/train/weights/tuned_word_embeddings.npy and ./neuralcoref/train/weights/static_word_vocabulary.txt in a text file with a similar structure to this

so we were able to apply that command. So far this isn't raising any errors though, but due to the previous mentioned ExtraData error, we weren't able to test our German NeuralCoref model yet. But maybe you can say, if this makes sense or not.
Again, thank you very much for your great work with this package and for answering our questions.

Thanks for your reply :)
My colleague just informed me, that it is indeed unneccessary to use the thinc 8 version, as PyTorchWrapper is available in earlier releases but was relocated. So i mistakenly assumed it was added later. I will try to use an earlier version of thinc, maybe this will resolve some issues.
Best wishes to you! I'm looking forward to spacy v3 :)

Hello,
which version of thinc have you used please, i couldn't find PytorchWrapper in earlier version

have anyone find a  solution to this error please ?
I'am facing the same error after training my model

@chieter hello,
have succeded to load the model please ?


Stathat

Adds stathat module
send donation stats to stathat

Code looks good, just need to check for minor edge case where form may be submitted before key is entered (or if erased)..

wouldn't really want to hardcode the key into code...

Yah, think its fine for now since it's just Donate Page, i'm just not sure if the module throws an error/watchdog if the key doesnt exist, if it gets wiped out by chance.


linux_*, except testing: apply patch for CVE-2023-32233

Description of changes
https://www.openwall.com/lists/oss-security/2023/05/08/4
If we don't get any stable kernel before fixing that.
Apply cleanly on:

[ ] Linux testing: has already the fix
[x] Linux 6.2
[x] Linux 6.3
[x] Linux 6.1
[ ] Linux 6.1 RT
[x] Linux 5.15
[x] Linux 5.10
[x] Linux 5.4
[x] Linux 4.19
[ ] Linux 4.14: not relevant

Tested on:

[ ] Linux testing: has already the fix
[x] Linux 6.2
[x] Linux 6.3
[x] Linux 6.1
[ ] Linux 6.1 RT
[x] Linux 5.15
[x] Linux 5.10
[x] Linux 5.4
[x] Linux 4.19
[ ] Linux 4.14: not relevant

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

@ofborg build linux_4_14 linux_4_19 linux_5_4 linux_5_10 linux_5_15 linux_6_1 linux_6_2 linux_6_3

It's only queued upstream back to 4.19.  Do we have a reason to think it needs backported further?

It's only queued upstream back to 4.19. Do we have a reason to think it needs backported further?

We discussed it and I removed 4.14 :). (reflected in the message of the PR)

Backport https://github.com/NixOS/nixpkgs/pull/231057


Push version 41 back to 43 in website text

After quite a bit of looking, I couldn't seem to find any other messages than the one changed here in the website.

r+

Could you put the bug number in the commit message please? Normally of the format "do something... (bug: xyz)".

@andymckay oops. Commit msg is updated with bug #


Changing Icon Set

I am trying to replace the default set of icons with my own (to match a custom Sublime icon). I tried creating a new application with Discord, enabled RPC, and uploaded my icons. I then swapped out the keys in the fork. However, the icon names seem to not be correct. Here is what I uploaded as assets:
c
Small

c
Large

cpp
Small

cpp
Large

crystal
Small

crystal
Large

cs
Small

cs
Large

css
Small

css
Large

d
Small

d
Large

elixir
Small

elixir
Large

extra
Small

extra
Large

go
Small

go
Large

html
Small

html
Large

java
Small

java
Large

javascript
Small

javascript
Large

json
Small

json
Large

lua
Small

lua
Large

markdown
Small

markdown
Large

php
Small

php
Large

python
Small

python
Large

ruby
Small

ruby
Large

rust
Small

rust
Large

sh
Small

sh
Large

sublime3
Large

sublime3
Small

typescript
Small

typescript
Large

What is the proper way to do so?

The language is prefixed with lang- in the code:
https://github.com/Snazzah/SublimeDiscordRP/blob/cd6579588f086f29d6437844407188a8e2cb06e7/drp.py#L76

This is not conventional for usage of Discord Rich Presence.

@FichteFoll Thank you. That's exactly what I was looking for.


After provisioning all tenant sharing controls were changed to no external sharing

Describe the bug
After provisioning the tenant sharing settings were set back to internal only for sharepoint and onedrive, this was not expected and was confirmed by the audit logs
To Reproduce
Sharing is set to Anyone for OneDrive and SharePoint
Deploy the solution
Sharing is set to internal only
Expected behavior
I did not expect this solution to change my sharing settings for the tenant
Learning Pathways version number
<IP_ADDRESS>
Additional context
Just followed the instructions on the site, nothing special happened

We have just had the exact same issue happen to us. Audit log shows my account changing the sharing permissions for the entire tenant at the exact time the learning pathways site was provisioned.
I've raised a premier support call with Microsoft for this.

Unfortunately, this is not an issue with learning pathways but an issue with the lookbook.microsoft.com provisioning service. I believe it's fixed but not sure exactly of the status.

I've been informed that the bug has been fixed in the provisioning service.


mamba_ssm code version

Hi,
As the ProtMamba_ssm/ is missing the mamba_ssm code in the distribution, can you please point me to the right version of mamba_ssm code you used for ProtMamba or add that to the ProtMamba_ssm/?
Thank you

Hi, it's not missing, it's part of the pip requirements on settings.ini
It's the original mamba repository and it should be installed when you run pip -e .

Thanks for the quick reply.
Below is the first error I get from running ProtMamba. As you can see there is no layernorm function in mamba_ssm code, infact it is layer_norm. Next it errors with arguments on other mamba_ssm modules/functions. It seems that there are changes in the code that is being installed and that has been used.
Traceback (most recent call last):
File "/home/ubuntu/scratch/ProtMamba-ssm/ProtMamba_ssm/sample_from_pretrained_model.py", line 4, in
from ProtMamba_ssm.modules import *
File "/home/ubuntu/scratch/ProtMamba-ssm/ProtMamba_ssm/modules.py", line 19, in
from mamba_ssm.ops.triton.layernorm import RMSNorm, layer_norm_fn, rms_norm_fn
ModuleNotFoundError: No module named 'mamba_ssm.ops.triton.layernorm'

Oh ok, we didn't specify the version on setting.ini, I'll fix it. A quick fix for you would be to downgrade Mamba to the version previous to Mamba2


nixos/geth: initial service

Motivation for this change
Add a service to run a Ethereum node with go-ethereum.
The service uses the same pattern as the bitcoind and allows multiple instances to be run.
Contributes to https://github.com/NixOS/nixpkgs/issues/103890
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

/cc @RaghavSood

Did a quick test synching goerli. Looks to be working.

Wouldn't it make sense to have "ipcdisable" as an option to be able to enable attaching to geth?

Did a quick test synching goerli. Looks to be working.

Wouldn't it make sense to have "ipcdisable" as an option to be able to enable attaching to geth?

@excogitation I ussually attacht to the node over http via geth attach http://localhost:8545. Adding an option would sure be possible. Do you see an advantage in having IPC too? The option could also be added later should the need arise.
As the module supports multiple instances, it might also be worth to create a wrapper script geht-<instance>, that has the correct parameters already set.

@excogitation I ussually attacht to the node over http via geth attach http://localhost:8545. Adding an option would sure be possible. Do you see an advantage in having IPC too? The option could also be added later should the need arise.
As the module supports multiple instances, it might also be worth to create a wrapper script geht-<instance>, that has the correct parameters already set.

@RaghavSood @Mic92 Could you take a look at this MR?

@RaghavSood @Mic92 Could you take a look at this MR?

I do not want to rename the package to to geth.
Geth is just one of the binaries in this package and the upstream repository name is go-ethereum.
I would be fine with an alias mapping geth to go-ethereum.

@bachp I decided to make go-ethereum multi output in https://github.com/NixOS/nixpkgs/pull/113960 so this service doesn't need to pull in the entirety of go-ethereum as a runtime dependency.

I did the following changes:

package now defaults to go-ethereum.geth
package is now added to the systemPackages to be able to interact with the daemon
added test that checks if the daemon starts up with the correct network

All good!


RUF007 - False positive when zip() contains more than 2 arguments

RUF007 should only hit when zip() is called with no more than 2 arguments, as pairwise() does not support it.
Introduced with #3501
See

https://docs.python.org/3/library/itertools.html#itertools.pairwise
https://docs.python.org/3/library/functions.html#zip

pyproject.toml
[tool.ruff]
target-version = "py311"

test.py
foo = [1, 2, 3, 4]

bar = zip(foo[:-1], foo[1:], foo, strict=True)

ruff test.py
test.py:5:7: RUF007 Prefer `itertools.pairwise()` over `zip()` when iterating over successive pairs
Found 1 error.

ruff --version
ruff 0.0.257

Thanks!

I would like to work on it.


add: job_type and tags for wandb

@soumik12345 thanks for the PR!
Could you walk me through the advantages of how to use the tag and job_type to our advantage in logging here?

Closing as per discussion over Whatsapp.


HHH-12741 Register new reserved words added in mysql 8.0

https://dev.mysql.com/doc/refman/8.0/en/keywords.html#keywords-new-8-0-A
https://hibernate.atlassian.net/browse/HHH-12741

@quaff thanks for the PR!

Thanks!

@vladmihalcea I'm surprised we don't have any reserved keywords for MySQL right now as they have a lot of them. Do you happen to know why?

@sebersole Do you happen to know the answer to @gsmet 's question above?

It should handled by DatabaseMetaData.getSQLKeywords(),  but mysql jdbc driver com.mysql.cj.jdbc.DatabaseMetaData.ProcedureType.MYSQL_KEYWORDS doesn't add new reserved words in order to keep back compatibility

@quaff interesting, thanks!
Is there a reason why you haven't added all of them? I see WINDOW (R) for instance that is missing in your PR.

The SQL keyword got from the DB metadata got to the IdentifierHelper, but we need to check if they are available to queries as well. Maybe that's a problem too.

@quaff I merged your PR, thanks. Will be included in the upcoming 5.3.2.


Request support for Proscenic A9 Air Purifier

I am wondering why is Proscenic A9 Air Purifier still not supported:
https://www.amazon.de/-/en/Proscenic-A9-Purifier-Performance-Sufferers/dp/B096M3Z8VV/ref=sr_1_1?crid=R5KVQACQ6S40&keywords=Proscenic+A9&qid=1692793759&sprefix=proscenic+a9%2Caps%2C120&sr=8-1
But I found among Tuya local devices Proscenic A8, which IS supported.
Possibly is much more users with A9, than with A8 ( I have 2x A9 in my house).
Is possible to implement also support for A9 ?
I have A9 in HA linked via the official Tuya integration, but I cannot set fan (vent) speed...always only one.
This is, why I found Tuya Local and open a new req.
All info i found about A9 issues in HA is here:
https://github.com/tuya/tuya-home-assistant/issues/727
and here:
https://community.home-assistant.io/t/proscenic-purifier-a8/315680
I will really appreciate if you manage to include A9 via Tuya Local (and many others too).
If you need any additional (json) data, please let me know what exactly is needed (link on the official tuya page).
Thank you very much.
Rob

There is no local protocol info in any of the links.
I already put a lot of effort into explaining the information needed in the issue template, as I do not want to spend time explaining it personally to every reporter.  If you cannot put the effort in yourself, then I can only close the issue if there is not sufficient info.


White flicker on switching to full-screen

Already reported ? *

[X] I have searched the existing open and closed issues.

Regression?
No
System Info and Version
 System/Version info
Hyprland, built from branch  at commit 0f594732b063a90d44df8c5d402d658f27471dfe  (props: bump version to 0.43.0).
Date: Sun Sep 8 16:48:21 2024
Tag: v0.43.0, commits: 5196

flags: (if any)

System Information:
System name: Linux
Node name: 10303B-arch
Release: 6.10.10-arch1-1
Version: #1 SMP PREEMPT_DYNAMIC Thu, 12 Sep 2024 17:21:02 +0000

GPU information:
0d:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] [1002:73bf] (rev c1) (prog-if 00 [VGA controller])

os-release: NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo

plugins:

======Config-Start======

Config File: /home/lucas/.config/hypr/hyprland.conf: Read Succeeded
autogenerated = 0

# Make systemd, dbus aware of environment
exec-once = systemctl --user import-environment DISPLAY WAYLAND_DISPLAY XDG_CURRENT_DESKTOP
exec-once = hash dbus-update-activation-environment 2>/dev/null && dbus-update-activation-environment --systemd DISPLAY WAYLAND_DISPLAY XDG_CURRENT_DESKTOP
exec-once = ~/.config/hypr/scripts/restart_portals.sh

exec-once = ~/.config/hypr/scripts/setup_workspaces.py
exec-once = ~/.config/hypr/scripts/on_event.py ~/.config/hypr/scripts/on_monitors_changed.py monitoradded monitorremoved

# Source a file (multi-file configs)
source = ~/.config/hypr/config.d/appearance.conf
source = ~/.config/hypr/config.d/env.conf
source = ~/.config/hypr/config.d/idle.conf
source = ~/.config/hypr/config.d/inputs.conf
source = ~/.config/hypr/config.d/keybindings.conf
source = ~/.config/hypr/config.d/outputs.conf
source = ~/.config/hypr/config.d/rules.conf

# exec-once = waybar
exec-once = ags

# Autostart apps
exec-once = ~/dotfiles/scripts/autostart.sh

exec-once = workstyle &> /tmp/workstyle.log

exec-once = gammastep

debug {
    # overlay = true
    # damage_blink = true
    # disable_logs = false
}

Config File: /home/lucas/.config/hypr/config.d/appearance.conf: Read Succeeded
$gnome-schema = org.gnome.desktop.interface

exec = gsettings set $gnome-schema gtk-theme 'Arc-Dark'
exec = gsettings set $gnome-schema icon-theme 'Papirus-Dark'
exec = gsettings set $gnome-schema cursor-theme 'breeze_cursors'
exec = gsettings set $gnome-schema font-name 'Noto Sans 10'

env = QT_QPA_PLATFORMTHEME,qt5ct
env = GTK_THEME,Arc-Dark
env = XCURSOR_SIZE,24
env = XCURSOR_THEME,breeze_cursors
env = HYPRCURSOR_SIZE,24
env = HYPRCURSOR_THEME,breeze_cursors

blurls=waybar

# Heavy effects only on these machines
exec = zsh -c "if [ $(hostname) = 10303B-arch ]; then hyprctl keyword decoration:blur:enabled yes; fi;"
exec = zsh -c "if [ $(hostname) = 10303B-arch ]; then hyprctl keyword decoration:drop_shadow yes; fi;"
exec = zsh -c "if [ $(hostname) = b650-la ]; then hyprctl keyword decoration:blur:enabled yes; fi;"
exec = zsh -c "if [ $(hostname) = b650-la ]; then hyprctl keyword decoration:drop_shadow yes; fi;"

general {
    # See https://wiki.hyprland.org/Configuring/Variables/ for more

    gaps_in = 5
    gaps_out = 5
    border_size = 2
    col.active_border = rgba(33ccffee) rgba(00ff99ee) 45deg
    col.inactive_border = rgba(595959aa)

    resize_on_border = false
    layout = dwindle
}

decoration {
    # See https://wiki.hyprland.org/Configuring/Variables/ for more

    rounding = 5

    drop_shadow = no
    shadow_range = 4
    shadow_render_power = 3
    col.shadow = rgba(1a1a1aee)

    blur {
        enabled = no
        size = 10
        passes = 1
        new_optimizations = on
    }
}

animations {
    enabled = yes

    # Some default animations, see https://wiki.hyprland.org/Configuring/Animations/ for more

    animation = windows, 1, 2, default
    animation = windowsIn, 1, 2, default, popin 80%
    animation = windowsOut, 1, 2, default, popin 80%

    animation = border, 1, 5, default

    animation = fade, 1, 2, default
    animation = workspaces, 1, 2, default, slide
}

# LAYOUT

dwindle {
    # See https://wiki.hyprland.org/Configuring/Dwindle-Layout/ for more
    pseudotile = false
    preserve_split = yes
}

exec-once = hyprctl monitors -j | jq ".[] | .name" -r | xargs -I "{}" zsh -c 'swaybg -o "{}" -i $(find ~/dotfiles/wallpaper/. -type f | shuf -n1) -m fill &'
#exec-once = swaybg -i $(find ~/dotfiles/wallpaper/. -type f | shuf -n1) -m fill &

misc {
    disable_hyprland_logo = true
    disable_splash_rendering = true
    new_window_takes_over_fullscreen = 2
}

Config File: /home/lucas/.config/hypr/config.d/env.conf: Read Succeeded
# Fix java apps
env = _JAVA_AWT_WM_NONREPARENTING,1

# Qt should use wayland if possible
env = QT_QPA_PLATFORM,wayland;xcb

env = XDG_CURRENT_DESKTOP,Hyprland
# Deprecated, needed for some scripts
env = DESKTOP_SESSION,Hyprland

env = HYPRLAND_LOG_WLR,1

env = MOZ_ENABLE_WAYLAND,1

Config File: /home/lucas/.config/hypr/config.d/idle.conf: Read Succeeded
exec-once = hypridle

Config File: /home/lucas/.config/hypr/config.d/inputs.conf: Read Succeeded
input {
    kb_layout = de
    kb_variant = nodeadkeys
    kb_model =
    kb_options =
    kb_rules =

    follow_mouse = 1

    touchpad {
        natural_scroll = yes
    }

    accel_profile = flat

    sensitivity = 0 # -1.0 - 1.0, 0 means no modification.
}

device {
    name = cherry-gmbh-cherry-wireless-device
    # EurKEY layout: American but uses AltGr+A for ä and so on
    kb_layout = de
    kb_variant = us
}

device {
    name = logitech-pro-x-gaming-keyboard
    kb_layout = de
    kb_variant = qwerty
}

device {
    name = at-translated-set-2-keyboard
    kb_layout = de
    kb_variant = qwerty
}

device {
    name = keychron-keychron-q1
    # EurKEY layout: American but uses AltGr+A for ä and so on
    kb_layout = de
    kb_variant = us
}

device {
    name = keychron-keychron-v1
    # EurKEY layout: American but uses AltGr+A for ä and so on
    kb_layout = de
    kb_variant = us
}

gestures {
    # See https://wiki.hyprland.org/Configuring/Variables/ for more
    workspace_swipe = on
}

exec-once = systemctl --user start opentabletdriver.service && ~/dotfiles/hypr/scripts/on_event.py '~/dotfiles/hypr/scripts/tablet_map_to_focus_otd.py "Wacom CTL-4100"' focusedmon

Config File: /home/lucas/.config/hypr/config.d/keybindings.conf: Read Succeeded
# See https://wiki.hyprland.org/Configuring/Keywords/ for more
$mainMod = SUPER

# Example binds, see https://wiki.hyprland.org/Configuring/Binds/ for more
bind = $mainMod, RETURN, exec, alacritty
bind = $mainMod + SHIFT, RETURN, exec, [float] alacritty
bind = $mainMod + CTRL, D, exec, nemo
bind = $mainMod + CTRL, B, exec, firefox
bind = $mainMod + CTRL, S, exec, subl

bind = $mainMod + SHIFT, S, exec, grimshot copy area

bind = $mainMod, Q, killactive,
bind = $mainMod, L, exec, loginctl lock-session
bind = $mainMod + ALT, Q, exit,
bind = $mainMod + ALT, R, forcerendererreload,
bind = $mainMod + SHIFT, SPACE, togglefloating,
bind = $mainMod, D, exec, anyrun
bind = $mainMod, P, pseudo, # dwindle
bind = $mainMod, E, togglesplit, # dwindle
bind = $mainMod, F, fullscreen, 1
bind = $mainMod + SHIFT, F, fullscreen

# Move focus with mainMod + arrow keys
bind = $mainMod, left, movefocus, l
bind = $mainMod, right, movefocus, r
bind = $mainMod, up, movefocus, u
bind = $mainMod, down, movefocus, d

# Move windows
bind = $mainMod + SHIFT, left, movewindow, l
bind = $mainMod + SHIFT, right, movewindow, r
bind = $mainMod + SHIFT, up, movewindow, u
bind = $mainMod + SHIFT, down, movewindow, d

# Switch workspaces with mainMod + [0-9]
bind = $mainMod, 1, workspace, 1
bind = $mainMod, 2, workspace, 2
bind = $mainMod, 3, workspace, 3
bind = $mainMod, 4, workspace, 4
bind = $mainMod, 5, workspace, 5
bind = $mainMod, 6, workspace, 6
bind = $mainMod, 7, workspace, 7
bind = $mainMod, 8, workspace, 8
bind = $mainMod, 9, workspace, 9
bind = $mainMod, 0, workspace, 10
bind = $mainMod, ssharp, togglespecialworkspace

# Move active window to a workspace with mainMod + SHIFT + [0-9]
bind = $mainMod SHIFT, 1, movetoworkspacesilent, 1
bind = $mainMod SHIFT, 2, movetoworkspacesilent, 2
bind = $mainMod SHIFT, 3, movetoworkspacesilent, 3
bind = $mainMod SHIFT, 4, movetoworkspacesilent, 4
bind = $mainMod SHIFT, 5, movetoworkspacesilent, 5
bind = $mainMod SHIFT, 6, movetoworkspacesilent, 6
bind = $mainMod SHIFT, 7, movetoworkspacesilent, 7
bind = $mainMod SHIFT, 8, movetoworkspacesilent, 8
bind = $mainMod SHIFT, 9, movetoworkspacesilent, 9
bind = $mainMod SHIFT, 0, movetoworkspacesilent, 10
bind = $mainMod SHIFT, ssharp, movetoworkspacesilent, special

# Scroll through existing workspaces with mainMod + scroll
bind = $mainMod, mouse_down, workspace, m+1
bind = $mainMod, mouse_up, workspace, m-1
bind = $mainMod SHIFT, mouse_down, movetoworkspace, m+1
bind = $mainMod SHIFT, mouse_up, movetoworkspace, m-1

# Move/resize windows with mainMod + LMB/RMB and dragging
bindm = $mainMod, mouse:272, movewindow
bindm = $mainMod, mouse:273, resizewindow

# XF86 Keys

bindl = ,XF86AudioMicMute, exec, wpctl set-mute @DEFAULT_SOURCE@ toggle
bindl = ,XF86AudioMute, exec, wpctl set-mute @DEFAULT_SINK@ toggle
bindl = ,XF86AudioRaiseVolume, exec, wpctl set-volume @DEFAULT_SINK@ 0.05+ -l 1.0
bindl = ,XF86AudioLowerVolume, exec, wpctl set-volume @DEFAULT_SINK@ 0.05- -l 1.0
bindl = ,XF86AudioPlay, exec, playerctl play-pause
bindl = ,XF86AudioStop, exec, playerctl stop
bindl = ,XF86AudioNext, exec, playerctl next
bindl = ,XF86AudioPrev, exec, playerctl previous
bindl = ,XF86MonBrightnessUp, exec, zsh -c 'if [[ $(light) -lt 15 ]]; then light -A 1; else light -A 5; fi; notify-send "Brightness $(light)%" -h int:value:$(light) -h string:synchronous:brightness -t 1500 -e'
bindl = ,XF86MonBrightnessDown, exec, zsh -c 'if [[ $(light) -lt 15 ]]; then light -U 1; else light -U 5; fi; notify-send "Brightness $(light)%" -h int:value:$(light) -h string:synchronous:brightness -t 1500 -e'

bind=$mainMod,v,submap,vnc
# will start a submap called "vnc"
# Use this to disable all bindings and allow the
# remote pc to receive them.
submap=vnc

# use reset to go back to the global submap
bind=,escape,submap,reset

# will reset the submap, meaning end the current one and return to the global one
submap=reset

Config File: /home/lucas/.config/hypr/config.d/outputs.conf: Read Succeeded
# See https://wiki.hyprland.org/Configuring/Monitors/
monitor=, preferred, auto, auto

# generated by nwg-displays
source= ~/.config/hypr/monitors.conf

# Turn off when lid closes
#bindl=, switch:on:Lid Switch, exec, hyprctl keyword monitor "eDP-1, 1920x1080, 0x0, 1.0"
#bindl=, switch:off:Lid Switch, exec, hyprctl keyword monitor "eDP-1, disable"

misc {
    vrr = 2 # fullscreen only
    vfr = true
#    mouse_move_enables_dpms = true
}

Config File: /home/lucas/.config/hypr/monitors.conf: Read Succeeded
# Generated by nwg-displays on 2024-04-13 at 11:42:38. Do not edit manually.

monitor=desc:ASUSTek COMPUTER INC VG259QM L4LMQS072375,1920x1080@239.76,0x0,1.0
monitor=desc:Ancor Communications Inc VS248 H2LMQS031073,1920x1080@60.0,1920x0,1.0

Config File: /home/lucas/.config/hypr/config.d/rules.conf: Read Succeeded
# Wayland Native
windowrule = float,^sublime_merge$
windowrule = float,^akonadi_followupreminder_agent$
windowrule = float,^Slack$
windowrule = float,^zenity$
windowrule = float,^wdisplays$

windowrulev2 = float,title:^Select Folder$

windowrulev2 = float,title:^Picture-in-Picture$
windowrulev2 = pin,title:^Picture-in-Picture$

# XWayland
windowrule = float,^Signal$
windowrule = float,^discord$

# windowrulev2 = noborder, fullscreen:1
#windowrulev2 = norounding, fullscreen:1

workspace=f[0],rounding:false,bordersize:0,gapsout:0
workspace=f[1],rounding:false,bordersize:0,gapsout:0
# workspace=f[2],rounding:false,bordersize:0

======Config-End========

Description
A white flicker can be observed when switching to full-screen (see video).
How to reproduce

Start hyprland
Toggle full-screen.

Crash reports, logs, images, videos
https://github.com/user-attachments/assets/980de157-635f-4eaf-b339-5c78b2e99a17

Can't reproduce.

that's just the window not resizing in time, the "white" is your wallpaper

What about drawing the window which is about to full-screen over the other windows? This would prevent a transition to the background and prevent this kind of flickering?

they fade out, you probably have quite a sharp out curve for fade.


Deploying scikit learn model using Flask

Closes #2
I have written code for this but I am unable to figure out the query part for this.

So try to look at the last line of the graph for how to manage input output. For now you just need to return the value of the number of cycles required for a particular day!
I don't understand what this means


Greenshock --> Greensock

Typo (no "h")
http://bestof.js.org/projects/greenshock

Hello @crazy4groovy , thank you.
I have just fixed the typo (disable the browser cache if the typo is still displayed on your screen).
If you have any feedback about bestof.js.org, or if there is any feature that could be useful for you, do not hesitate to contact me!

Thanks, it's a great site already!


double-beep: Watch bindasmaldoors.com

double-beep requests the watch of the watch_keyword bindasmaldoors\.com. See the MS search here and the Stack Exchange search here.

bindasmaldoors\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Shree in Charcoal HQ


re-release as version 0.2.11

Issue:
https://github.com/FusionAuth/fusionauth-issues/issues/2498
Problem:
Updating applications to use latest java-http version of 0.3.0 would require all their dependencies (such as prime-mvc) to use version 0.3 of java-http.  Recent TLS updates of java-http are backwards compatible with previous versions, so technically, the current version should be 0.2.11.  (Version 0.*.* rules of Semver.)
Solution:
Re-release java-http with a minor version change to 0.2.11

This will work. Another option is to checkout 0.3.0 and create a maintenance branch off of that - and then release from there.
If we do this (which is fine) it just means that we need to make another commit after we release this to go back to 0.3.0.

If we do this (which is fine) it just means that we need to make another commit after we release this to go back to 0.3.0

Ack.  Will do this.


fix(pagination): Fix double BEM classes on elements

Need #516 merged first
Fixes #500
BREAKING CHANGE: Removes all __disabled, __first, __last,
__next, __previous, __active and __page classes added on the links in the
pagination. It only adds them to the parent li. Links instead now
have a .ais-pagination--link class
Previously, the same CSS classes where added to both the item (li) and the
link inside it. I've split them in --item and --link.
I've also made the various active/first/disabled/etc modifiers as
actual __modifier classes.
I've updated the tests, the CSS skeleton, the examples and the docs
accordingly.
The mixins and internal variable where misnamed. We use the BEM naming
with the following pattern: .ais-block--element__modifier.
Mixins where usin component instead of block and where swapping
element and modifier. I've reverted to something more readable.

conflicts

rebased

This is ready for some review love :heart:

Lgtm


Feat cnab inspect

- What I did
Two things:

removed fetching docker application package from URL
moved the inspect action inside the invocation image and add it as a custom CNAB action in the bundle.json

- A picture of a cute animal (not mandatory but encouraged)

Suggested also to drop the old image support as this PR drops URL handling already.

@ulyssessouza is dropping the experimental commands for the old image support (image-add, image-load, pack and unpack), so maybe he can drop the support too in the same PR?

Depends on #457

Don't know why, but there is a test consistently failing on Windows (tried to relaunch the workflow, and that reproduced it) on pr-merge.

You might want to rebase on master and try to see what happens by running the suite locally

Just rebases on top of master


How to sent request to local server?

My server started on localhost and i want calc route.
I write on cromium
"http://localhost:5000/&start=30.449616345352,50.547395972105&dest=30.4713468,46.7296333&z=15&output=json&jsonp=showResultsRoute&geomformat=cmp&instructions=true"
and recive "400 bad request"
Where can i read about good request?

you're missing 'viaroute'. here's an example:
http://localhost:5000/viaroute&start=1.0,1.002&dest=1.0,1.0&output=json&geomformat=cmp
if you use open web interface index.html file, you can look at what request the browser is sending when search for routes.

I'll close this issue, but discussion can continue here if there are further related questions.

Thanks.


Passing zero to nfs.update(...) multiple times without error.

https://forum.safedev.org/t/implementing-nfs-api-rename/2109/13
I'm able to pass 0 as the version when updating a file multiple times without error.
nfs.update(fileName, file, 0, userMetadata)
Is this expected behavior?

@hunterlester as per further comments in that thread it seems it's expected and it's a feature provided by the underlying safe_app lib, although I'd say we are missing a constant for that specific value, similar to the constants we have for other functions, e.g. USER_ANYONE, NFS_FILE_END, etc.


Add L1 and Elastic Net regularization terms to the Logistic Regression

We need additional parameters to support L2 and Elastic Net (optional) regularization of Logistic Regression parameters

This issue depends on #70

This issue depends on #70


Design getting started video

We need to update the design getting started video:

[ ] Connect with systems squad on available materials. latest response:

[ ] Rewrite script based on new material for v11

[ ] outline what new visual elements will be needed and connect with jeannie/tracey on what needs to be made

[ ] make video (details to come)

Hey team! Please add your planning poker estimate with ZenHub @aubrey-oneal @kingtraceyj

How can system squad help (or drive) this effort?

In the interim, I've written up two proposals for temporary copy:
https://www.figma.com/file/KZ6SWR2abIniIJY4RewDeA/Getting-Started-Design---Redline?node-id=10%3A13436


"table" class mangles signpost styling

Describe the bug
When a signpost is used:

inside of a table header
and the table has the class "table"

The styling of the signpost is mangled
How to reproduce
stackblitz reproduction
Steps to reproduce the behavior:

create a table
set the table's class to "table"
create a table header
add a signpost to the head
click signpost to see mangled formatting

Expected behavior
signpost will retain formatting regardless of outer element
Versions
App

Angular: 9
Node: 12.18.0
Clarity: 3

Device:

Type: mbp
OS: Mac OS 10.15.4
Browser chrome
Version 81

Additional notes
none

Yes, some styles are set on the table header cells that bleed into the signpost content areas. This should be something you can workaround in the CSS but it is likely to be fixed by #1757.


Total failure to function

I recently became aware that a previously functioning dexter plugin no longer worked in VS2015. Re-installation did not fix the issue. The installer reports success and the Dexter menu appears, however all menu options are greyed and do not function.  In tools/options/dexter a message states "an error occurred loading this property page".
This has occurred without warning to a previously functioning installation. Unless this can be fixed quickly I will abandon this tool and search for a better one.

Hi, We apologize for the inconvenience.
Could you attach a screenshot or a log?
Please attach the screen with the disabled menu and the Dexter Settings to help us solve this problem.
We will review it as soon as possible.

I re-installed dexter with the following result;
The dexter menu is non-functional. I cannot go to the settings page. I can't capture the menu either so a description must suffice. All items in the dexter menu are enabled but items in sub menus are grayed. No menu items function, despite being enabled. Click on settings and nothing happens. Click on open dexter dashboard and nothing happens. click on any other menu item and a grayed sub menu appears.
In tools/dexter the following message is displayed "An error occurred loading this property page"
When first installed, dexter worked. There is nothing unusual about my vs installation. Dexter's failure was arbitrary and unpredictable. I will not be reinstalling vs - too much effort to re-configure it to my liking.
Any help would be appreciated.

I just got dexter working again. Uninstall, delete cli folders, edit registry to remove dexter entries, then re-install with the latest cli.
Not happy. I should not need a registry edit to uninstall software. Uninstall from vs leaves hundreds of dexter references in the registry. Some are ok but many are not and should have been removed.
I am uncertain which action resolved the problem but the two most probable are removing the registry entries and deleting the cli folder. The old cli was v9xxx and the new is v10xxx.
This has been a very messy business.

Hi @jfitter,
we are happy that your Dexter works again!
Moreover, we kindly thank you for the thorough feedback.
I believe that one of our developers already managed to reproduce your error. So it will be easier to work on it and prevent similar issues happening to long-term users of Dexter.
Thank you for your feedback and wish you a successful time hunting those pesky defects with Dexter!


median income

3/4/2024  Currently, when rolling (hovering) over the map, the tooltip pop-up shows median income in the form:
153.292k
I think it would be more readable and more consistent with how the amount is shown in the table if median income were shown in this form:
153,292

I agree. It looks like plotly called this "hover text". A good google search for this seems to be "px.choropleth_map hover text"

[like]  Charles R Jones (CENSUS/ACSO FED) reacted to your message:

From: Ari Lamstein @.>
Sent: Monday, March 4, 2024 4:39:32 PM
To: arilamstein/censusdis-streamlit @.>
Cc: Charles R Jones (CENSUS/ACSO FED) @.>; Author @.>
Subject: Re: [arilamstein/censusdis-streamlit] median income (Issue #3)
You don't often get email from @.*** Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
I agree. It looks like plotly called this "hover text". A good google search for this seems to be "px.choropleth_map hover text"
—
Reply to this email directly, view it on GitHubhttps://github.com/arilamstein/censusdis-streamlit/issues/3#issuecomment-1977010365, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A26PGHHSK2GKC2Q2DESR5ATYWSPUJAVCNFSM6AAAAABEFRAGDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZXGAYTAMZWGU.
You are receiving this because you authored the thread.Message ID: @.***>

Here is how to solve this problem.

Section "Disabling or customizing hover of columns in plotly express" from this page.

It says:

For an existing column, the values can be ... a formatting string starting with : for numbers d3-format's syntax, and | for dates in d3-time-format's syntax, for example :.3f, |%a.

So I need to spend some time with that d3 page.

Ah, it appears to be as simple as:
    fig = px.choropleth_mapbox(df,
                               ...
                               hover_data={var_label: ":$,"},

Also, this formatting should probably be included for median rent as well (but not for population).
hover_data={var_label: ":$,"},

The solution is now in production.


Wordpress livepreview

Release 1.9 versión 1.9.0-17312 (release 189f6d39a)
windows 10 64x
chrome 58.0.3029.96 (64-bit)
xampp v3.2.2
Hi I am trying to use a Life preview for wordpress,  I am running apache with xampp and have my URL base http://localhost/
The theme twentyseventeen is activated on the wordpress instalation and when openening the page.php file and trying to live preview i get the follogwng error
Fatal error: Call to undefined function get_header() in C:\xampp\htdocs\wp3\wp-content\themes\twentyseventeen\page.php on line 28
before the get_header() I inserted some php code and it is running correctly and if a make a change on this code and save the file, the livepreview updates as well but i don't know what is happening.
I tried as well a .htaccess on the twentyseventeen folder with the following line
RewriteRule page.php "http://localhost/wp3/?page_id=2" but does't solve the problem.
I have read the https://github.com/adobe/brackets/wiki/How-to-Use-Brackets the own backend section but it has not help solve it ether, If someone know a solution for this please share it.

on the .htaccess the following line was missing
RewriteEngine On
now it is working great

After saving the changes the live preview is not refreshing... anyone has solved this?


connection not working

I am doing everything according to tutorial, but my code doesn't show any output. I am running this example https://www.youtube.com/watch?v=BV6xK3EOznI code on the same machine as the server.
there is no output in the console or canvas.

Do you have output on the canvas or in the console of the server application?

Thanks for the reply Lisa. There was no output on either canvas or console.
Its resolved now.
I was running the code on firefox before. Just switched to chrome and it
worked perfectly. Not sure why it wasnt working on firefox.
But i have noticed that the feed on the canvas has a bit of lag even though
the server feed is smoooth.
On Mon, 4 Feb 2019 at 6:05 AM, Lisa Jamhoury<EMAIL_ADDRESS>wrote:

Do you have output on the canvas or in the console of the server
application?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kinectron/kinectron/issues/43#issuecomment-460106221,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AqPDlUe1a8ARb5eOKHc0b64KOE8X6JwKks5vJ4dAgaJpZM4aZoLx
.

--
Regards,
Muhammad Umair Khan
Research Officer
Bioinformatics Research Lab
Al-Khawarzimi Institute of Computer Sciences (KICS)
University of Engineering and Technology (UET), Lahore

Ok glad you got it to work. The lag may be a result of the peer server library that I am using in Kinectron. It is a few years out of date and needs to be replaced.


⚠ Bofrost.fr has degraded performance

In 22c956f, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1094 ms

Resolved: Bofrost.fr performance has improved in 404f262.


Home Assistant

The README mentions Home Assistant, is there any HA integration that uses this library or official advice on how to push contact energy data into HA using this library?
The custom component https://github.com/codyc1515/ha-contact-energy does not seem to work nor uses this library.

Ther was an integration that I planned to push into HA core: https://github.com/home-assistant/core/pull/91349 but I unfortunately could not get it across the line. At this stage I don't have bandwidth to attempt it again.
You probably could use the code from there as reference to get the sensor going.

@tkhadimullin Thanks for letting me know. I certainly understand why you would run out of steam.
Maybe in the future HACS would be a better fit: https://www.hacs.xyz/


Polygon points offset after drawing

Hello Team,
Polygon Points are not consistant
Sometimes its is showing
sometimes

Thanks for reporting. Can you let me know which browser (and OS) you are using? Can you identify any special conditions that seem to cause the problem? Or is it completely random?

Hi ,
I am using Latest Chrome version.
Points are generating randomly sometimes comma saperated like
sometimes it is giving

i am using latest version of Chrome

Sorry, I cannot reproduce this. Do you have a screenshot of the issue? Or do you mean that when you edit a polygon shape and move the whole shape, only the shape moves but not the corner points? That was an unfinished piece of code which is now completed in the master branch.

Just bumping: are there any news on this?

I think I could finally reproduce this issue. Polygon corner handles are offset from the polygon, right after the polygon was created. Interestingly, this seems to happen only in the compiled library, but never in development mode.

Turns out that this happend in both built and dev mode - but was actually related to scaled images. Polygon corner handles would be offset from their position when the image (and the SVG canvas) were resized from their natural width and height.

I'm seeing this in scaled images too. Any suggestions/fixes for the same?

I have recently revised the code that scales the shapes. Looks like this is now fixed in the latest release published just now.


add screenplaysubs extension example

Awesome boilerplate. Used it for ScreenplaySubs. Would be cool to showcase it here ;)

Thank you. Nice extension, I'll try to use it. 👍


control block matching seems to find wrong block head or tail.

Notice the IF and ENDIF lines outlined.  The IF that is highlighted is not the if for the ENDIF highlighted.

Ctrl+Shift+\ matches the wrong ENDIF.
Ctrl+Shift+[ folds the correct control block.
If I comment out the exe sql code the block marking works

This fix did work for the sample I gave you but I found another version of code that its not working correctly for.

Ctrl+Shift+\ matches the wrong ENDIF.
Ctrl+Shift+[ folds the correct control block.
If I comment out the exe sql code the block marking works
One thing I noticed with this is that i have a CASE statement which has an END keyword.


Use DeferredDisplay for GLX

Since OpenGL rendering happens mostly from the render thread, it should be using the secondary X11 connection (we already have it).
Should fix some rare deadlocks in XGetGeometry

You can test this PR using the following package version. 11.0.999-cibuild0032947-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0032961-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0032985-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]


Prevent Bubbling when setting DOY/hours/minutes/etc

We have a form that lets users input the value for minutes, seconds, DOY, etc to then build date objects used elsewhere, and having everything bubble-up by default is rather unexpected to most users.
Moment having an option to disable this or bypass the bubbling up, event saying it's invalid etc would be great.

@ichernev
+1 for a switch to disable bubbling or turn on "strict" bubbling e.g. 0h67m -> 1h07m, 15d ->2w1d etc.
For me the current semantics is counterintuitive. Without grepping through the code I'm not sure if a duration like moment.duration({weeks: 80}) is going to represent exactly 80 weeks or something around 1.5 year when added to some moment.
Then, correct me if I'm wrong, but to be able to read the exact value of a duration I have to access its private members, which is not covered by official docs/api:
moment.duration({weeks: 5}).weeks()  // 0
moment.duration({weeks: 5}).months() // 1
moment.duration({weeks: 5}).days()   // 4
moment.duration({weeks: 5})._days    // 35 <- that's what I wanted. At least sort of

I know this is an old ticket but I'd like to help out.
@mszczepanczyk to get the exact value of a duration, you can use:
moment.duration({weeks: 5}).asDays()

This is in the docs; let me know if they're unclear!
@Gillingham Probably, the "error" depends on the particular application, so @ichernev 's suggestion seems like it would work for you.

See https://momentjs.com/docs/#/-project-status/ . We will not make substantial changes to Moment.js going forward.


Update sift_1b.cpp

It seems it missed inputGT.close() in this file.

@jshang2 Thanks!
Can you redo the PR against the develop branch?

@yurymalkov Okay!
I have't realized there is a develop branch before. Thanks for sharing your code. I've learned a lot from this library. 👍


Update README.md code to correct data frame

Readme sample code is referring to a previously used data frame simply named pumpkins. pumpkins data frame was renamed to new_pumpkins prior to this sample code. Updated sample code to reflect the change.

Readme sample code is referring to a previously used data frame simply named pumpkins. pumpkins data frame was renamed to new_pumpkins prior to this sample code. Updated sample code to reflect the change.

Hi @asilich123, thanks for your PR! The code is referring to the original dataset, not the one resulting from column filtering, that's why it refers to pumpkins vs new_pumpkins. In fact, the description before that code chunk says 'Digging into the original data' and it suggests to 'Add a filter at the top of the file, under the initial .csv import'. Have a look at the solution notebook to see the final code.


man-db: add support for zstd + fix undeclared runtime deps

Motivation for this change
man-db supports zstd since 2.9.2 (1 June 2020).
There might be man pages out there which are compressed with this format.
Also this opens up the possibility to compress with zstd instead of gzip in nixpkgs to benefit from faster builds and lower closure sizes.
Things done

Add zstd to nativeBuildInputs
patch configure.ac to properly reference runtime dependencies via absolute paths

The package previously had undeclared runtime deps like gnugrep or gzip.

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

Switched to pname + version and utilizing autoreconfHook now.

@SuperSandro2000 Anything left to do here?

happy to help you get this merged if you can rebase this.

alright just tested on darwin, and zstd does end up in the dependents.
looks good to me.
Thanks!

When cross-compiling this now shows this error, causing the build to fail:
Found an erroneous dependency on groff ^^^.
This is an error from the derivation, written in the postFIxup.
Possibly due to this?
--replace AC_CHECK_PROGS AC_PATH_PROGS
Haven't looked further into this other than seeing it fail on my hydra instance, but could use some investigation.

The current PR removed groff from the nativeBuildInputs. Maybe it should be added again.

Hmm, I don't think that's what happened since I still see groff in the nariveBuildInputs in staging-next

https://github.com/NixOS/nixpkgs/pull/169380