[BUG] /api/get-ldap-users return badRequest when ldap "dn" without "ou"

Problem
when using follow ldap admin dn, (by the word, this dn is the default configuration for https://github.com/osixia/docker-openldap)
cn=admin,dc=example,dc=org

return error message

LDAP Result Code 34 "Invalid DN Syntax": bind failed ErrMsg: please use correct Admin Name format like cn=xxx,ou=xxx,dc=example,dc=com

then I found the source code, it seems ou is mandatory

https://github.com/casdoor/casdoor/blob/master/object/ldapserver.go#L25

But ou might be optional in dn?
FIY:

https://www.google.com.hk/search?q=ldap+is+"ou"+mandatory+for+dn&ei=7z8mZLTWII3ThwOF1LsI&ved=0ahUKEwj0idOoioX-AhWN6WEKHQXqDgEQ4dUDCA8&uact=5&oq=ldap+is+"ou"+mandatory+for+dn&gs_lcp=Cgxnd3Mtd2l6LXNlcnAQAzIFCAAQogQyBQgAEKIEMgUIABCiBDIFCAAQogQ6CggAEEcQ1gQQsANKBAhBGABQ4gVYrQxgsg9oAXABeACAAYEBiAHnAZIBAzAuMpgBAKABAcgBCMABAQ&sclient=gws-wiz-serp

Reproduce step
Organization ldap config

@lzw5399 You use Casdoor ldapserver to test. Actually, casdoor ldapserver is used for resove some clients that only support ldapto login by casdoor. So it is not a complete ldap server that support most of the ldap server function.


Implemented SA1507 (incl. codefix + tests)

Fixes #108

Working on a fix where SA1507 triggers within verbatim string literals

Fixed the issue with verbatim string literals.

Otherwise this looks good.

:question: @vweijsters I want you to consider the following alternative implementation, decide which approach we should favor, and then explain your position. :smile: Please note that the tests do not pass out-of-the-box with this due to dotnet/roslyn#1655.
public override void Initialize(AnalysisContext context)
{
    context.RegisterSyntaxTreeAction(this.HandleSyntaxTreeAnalysis);
}

private void HandleSyntaxTreeAnalysis(SyntaxTreeAnalysisContext context)
{
    SyntaxNode root = context.Tree.GetRoot(context.CancellationToken);
    foreach (var token in root.DescendantTokens(descendIntoTrivia: false))
    {
        if (token.IsKind(SyntaxKind.EndOfFileToken))
        {
            // If the file ends with blanks lines, ignore them, they will be handled by SA1518.
            continue;
        }

        int blankLineIndex = 0;
        int blankLineEndIndex = -1;
        int blankLineCount = 0;
        SyntaxTriviaList leadingTrivia = token.LeadingTrivia;
        for (int i = 0; i < leadingTrivia.Count; i++)
        {
            switch (leadingTrivia[i].Kind())
            {
            case SyntaxKind.WhitespaceTrivia:
                continue;

            case SyntaxKind.EndOfLineTrivia:
                blankLineEndIndex = i;
                blankLineCount++;
                if (blankLineIndex < 0)
                {
                    blankLineIndex = i + 1;
                    blankLineCount = 0;
                }

                continue;

            default:
                ReportDiagnosticIfNecessary(context, leadingTrivia, blankLineIndex, blankLineEndIndex, blankLineCount);
                blankLineIndex = -1;
                continue;
            }
        }

        ReportDiagnosticIfNecessary(context, leadingTrivia, blankLineIndex, blankLineEndIndex, blankLineCount);
    }
}

private static void ReportDiagnosticIfNecessary(SyntaxTreeAnalysisContext context, SyntaxTriviaList leadingTrivia, int blankLineIndex, int blankLineEndIndex, int blankLineCount)
{
    if (blankLineIndex < 0 || blankLineEndIndex <= blankLineIndex)
    {
        // nothing to report
        return;
    }

    if (blankLineCount < 2)
    {
        // only care about multiple blank lines in a row
        return;
    }

    if (leadingTrivia[blankLineIndex].SpanStart == 0)
    {
        // blank lines at the beginning are reported by SA1517
        return;
    }

    TextSpan span = TextSpan.FromBounds(leadingTrivia[blankLineIndex].SpanStart, leadingTrivia[blankLineEndIndex].Span.End);
    Location location = Location.Create(context.Tree, span);
    context.ReportDiagnostic(Diagnostic.Create(Descriptor, location));
}

The issue reported in the Roslyn database is not a bug. Have another close look at the test code (I needed several) and notice that the test code is trying to use using statements inside a class declaration, which is of course invalid C#. I'll fix the test code straight away.
Still trying decide which implementation I like more...

I'm still undecided.
I very much like the way the alternative implementation elegantly handles the verbatim string literals, the multi-line comments and the disabled text trivia.
I don't like the fact that it can't handle empty lines in the trailing trivia (or worse a mix of leading and trailing trivia that cause empty lines). Not sure if the Roslyn parser will ever generate them, if not then this is a moot point.
@sharwell What made you propose an alternative implementation?

This is a fixed alternative implementation that passes the revised tests
The original alternative implementation had issues with directive trivia, which imply a new line at the end of that trivia.
        public override void Initialize(AnalysisContext context)
        {
            context.RegisterSyntaxTreeAction(this.HandleSyntaxTreeAnalysis);
        }

        private void HandleSyntaxTreeAnalysis(SyntaxTreeAnalysisContext context)
        {
            SyntaxNode root = context.Tree.GetRoot(context.CancellationToken);
            foreach (var token in root.DescendantTokens(descendIntoTrivia: false))
            {
                if (token.IsKind(SyntaxKind.EndOfFileToken))
                {
                    // If the file ends with blanks lines, ignore them, they will be handled by SA1518.
                    continue;
                }

                int blankLineIndex = 0;
                int blankLineEndIndex = -1;
                int blankLineCount = 0;
                SyntaxTriviaList leadingTrivia = token.LeadingTrivia;
                for (int i = 0; i < leadingTrivia.Count; i++)
                {
                    switch (leadingTrivia[i].Kind())
                    {
                        case SyntaxKind.WhitespaceTrivia:
                            break;

                        case SyntaxKind.EndOfLineTrivia:
                            blankLineEndIndex = i;
                            blankLineCount++;
                            break;

                        default:
                            ReportDiagnosticIfNecessary(context, leadingTrivia, blankLineIndex, blankLineEndIndex, blankLineCount);
                            blankLineIndex = i + 1;
                            blankLineCount = 0;
                            break;
                    }
                }

                ReportDiagnosticIfNecessary(context, leadingTrivia, blankLineIndex, blankLineEndIndex, blankLineCount);
            }
        }

        private static void ReportDiagnosticIfNecessary(SyntaxTreeAnalysisContext context, SyntaxTriviaList leadingTrivia, int blankLineIndex, int blankLineEndIndex, int blankLineCount)
        {
            if (blankLineIndex < 0 || blankLineEndIndex <= blankLineIndex)
            {
                // nothing to report
                return;
            }

            if (blankLineCount < 2)
            {
                // only care about multiple blank lines in a row
                return;
            }

            if (leadingTrivia[blankLineIndex].SpanStart == 0)
            {
                // blank lines at the beginning are reported by SA1517
                return;
            }

            TextSpan span = TextSpan.FromBounds(leadingTrivia[blankLineIndex].SpanStart, leadingTrivia[blankLineEndIndex].Span.End);
            Location location = Location.Create(context.Tree, span);
            context.ReportDiagnostic(Diagnostic.Create(Descriptor, location));
        }

What made you propose an alternative implementation?

Among other things, the call to GetText in the original implementation concerns me. Whenever I have concerns about performance or simplicity, sometimes it helps to see two implementations side-by-side and discuss them. If I put in that work and it gets thrown out in the end, I'll know it's because the one we picked is at least as good. :smile:

I don't like the fact that it can't handle empty lines in the trailing trivia (or worse a mix of leading and trailing trivia that cause empty lines).

From everything I've seen so far, trailing trivia for a token includes but never extends beyond the EndOfLineTrivia containing the token. This means a SyntaxTrivia cannot both exist on a blank line and be containing in the trailing trivia for a token.

Your effort to make an alternative implementation is very much appreciated and in this case it won't be thrown out :smile: I was just curious what triggered you to make it.
I've made up my mind and given the current behavior of Roslyn with respect to trailing trivia (and the low probability that that behavior will change before release) I think we should go with the alternative implementation, as it is much more elegant at handling the special cases.
@sharwell If you are ok with it, I'll change the pull request to use the fixed alternative implementation.

@vweijsters that's fine with me.

Switch to alternative implementation has been committed.


DATASTD 1574

Grand Bend sample XML updated to 2021-2022 school year.

All my review comments are addressed, and the data looks pretty solid.  @ejansson A lot of the updates that looked strange, when I dug in more were just fixing inconsistencies in the original data.  For example there's a mix of 2010-2011 and 2011-2012 data in some of the domains, so the general intent seems to have been to make sure the data is aligned to a 2021-2022 school year, making the dates make sense in general for representing a single school year.
At this point probably makes sense to spin off data standard tickets for updating the section and assessment identifiers to get away from dates, but this is good to go once Eric/Gabrielle are good with it.

Ready to pull this in, but the merge is blocked pending some changes. Will also raise a ticket to remove school years from identifiers and course titles.


[NEURIPS] Hosted Editor hides files with errors (cannot be deleted)

Using the editor hosted on HuggingFace (https://huggingface.co/spaces/MLCommons/croissant-editor), I first accidentally added a FileObject instead of a FileSet. When I selected FileSet as that FileObjects parent, the editor hid the file (I'm assuming because an error was raised?). I corrected my mistake by adding two FileSets instead. Now, the editor shows that I have 3 resources on  the overview tab even though I only two resources show up on the resources tab (see images). Furthermore, the overview tab highlights a number of errors related to that initial FileObject having unfilled fields (see image), and so I cannot export my croissant metadata (export button is not clickable).
Overview tab shows 3 resources:

Resource tab shows only 2 resources (which is what I want):

Overview tab shows errors relating to missing resource file:

Hi Francois,
If your data is in an archive, you should first add a FileObject for the archive file, and then a "child" FileSet with containedIn set to the FileObject.
I would recommend creating a new dataset from scratch in the editor... I'm not sure the one you currently have can be easily fixed.
Hope this helps,
Omar

If your data is in an archive, you should first add a FileObject for the archive file, and then a "child" FileSet with containedIn set to the FileObject.

The problem is that the editor doesn't support uploading an archive file:

I would recommend creating a new dataset from scratch in the editor... I'm not sure the one you currently have can be easily fixed.

Fair enough. However, the fact that I have to restart from scratch every time I make even a small mistake makes the editor not user-friendly in the slightest. I should be able to free delete mistake files, rather than the editor hiding them from the UI but still complaining about the errors.

Same issue with tar.xz files, when provide a link and all requied fields, the error message persists.

I encounter similar issues, where the difference is that even when I upload unarchived .csv files, the editor still shows errors like "At least one of these properties should be defined: ['md5', 'sha256'].", "Property "https://schema.org/contentUrl" is mandatory, but does not exist.", "Property "https://schema.org/encodingFormat" is mandatory, but does not exist.", Node "xxx" is a field and has no source. Please, use http://mlcommons.org/croissant/source to specify the source.
Especially for the "no source" issue, the croissant documentation https://mlcommons.org/croissant/source does not exist.


win+e don't bring the opened File window forward

Description
win+e will open a new tab if there is an existing File window. However, the windows aren't brought forward. It remains under other windows.
Steps To Reproduce

Open File and focus on another full-screen app (like chrome)
Win+e
A new tab will open in File, but the window remains in the background

Steps to fix

bring the window forward when opening a new tab

Files Version
版本: <IP_ADDRESS> OS Version: 10.0.22621.900
Windows Version
Windows 11 22H2 22621.900
Relevant Assets/Logs
debug.log

This issue will be resolved with #13588.


Send event and wait response

Hello!
I need your help.
We are developing a mobile application.
We send an event to the mobile application and we need to receive a response to this event within a certain timeout; if the response is not received, we need to send another event to another channel.
Maybe there is another better solution
I kindly ask you to help me solve this problem.

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord or InertiaJS Discord for Inertia questions
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.


Small text change

Changed text within Limited section of page

This will have to be fixed in #108


How to set the currency

Hello, I'm new integrating the Mercado Pago SDK and have a few questions about the usage and was hopping you can help me understand better the flow.
My first question is how to set the currency of the payment to COP? I saw there is a CurrencyId class on the Payment class but there is no setter method for the payment, and I was wondering how to set that info.
Also I read that the card token is for only one usage, but I got a question about this, my current flow is: My user adds the credit card info in front end and generate a card token, I send that card token to my backend and try to do an small payment to check that the card ids real, if the payment turns out as a success I want to add that card to my Customer, but Since the card token was already used I don't know if thats possible.
Thanks!

Hello, mamup11.
There is no way to enter currency for the Mercado Pago Api. It is associated to your user.
It is possible save a card with a token that was used for a payment.
Any other questions please contact us.


Removed extraneous sample azure.json entries

Proposed changes
Currently we specify quite a few extra lines in the azure.json file that are unneeded due to the default values.
I removed cloudProviderBackoff and its extraneous related values, and useManagedIdentityExtension since the default value is the same.
Removing these entries tidies up and simplifies the sample azure.json for end users.
I also standardized on 3 *** placeholder characters, as currently there is an inconsistent mixture of sometimes 3, and sometimes 4.

There was also an extra / characters in "subnetName": "/****", that I removed.
All of this should be in accordance with the docs

Deploy preview for docsdocker ready!
Built with commit c5c32f63a512d4a3e3447a33539cae20d7b37e4f
https://deploy-preview-9271--docsdocker.netlify.com


build_helper: Optionally allow building without jemalloc

As a workaround for https://github.com/facebook/folly/issues/976, modify build_helper.sh to allow disabling jemalloc use by passing the appropriate argument to the cmake invocation on folly.

Looks like the travis build is running into a time limit: https://travis-ci.com/facebookincubator/mvfst/builds/111963309#L9510

@akshayknarayan you'll need to sign the CLA before I can import your commit.

@udippant is there something further I need to do? I have emailed<EMAIL_ADDRESS>but haven't gotten a response.

@akshayknarayan - your CLA status should be resolved now.


More explanatory warning with language-not-exist

Many people seem puzzled by the message displayed when a certain language doesn't exist, and they even think it's an error. While the message in necessary, because it's relevant for some languages, it could be more informative, with something like:
Package fontspec Warning: Language 'Thai' not available for font 'FreeSerif'
(fontspec)                with script 'Thai'. There is nothing intrinsically wrong with
(fontspec)                this warning, and if the output is as expected, you can
(fontspec)                ignore it.

@wspr I've noticed some people is rejecting babel because of this message, which leads them to think the babel language is not available and therefore not useable. Please, can you provide some advice about what can I do to improve the situation? I'm trying to conceal it, but I haven't managed to do it yet. I'm even considering forcing the quiet mode, which is clearly a bad idea, but anyway better than showing this misleading message.

Sorry I overlooked this previously. Probably a better option (?) is to check if the language/script is present and only load it if so. There should be enough commands in the API section of the manual to do this without delving into fontspec internals. If you think that's clunky, I could also add something like TryLanguage={...} or Language*={...} which has the same behaviour but doesn't call the warning. Or I could drop the warning all together but default and add a new LanguageStrict={...} key instead. What do you think would be best?

This is just a reminder, because many people clearly think there is something wrong when this warning is shown.


2 generators run initially... then 4 subsequently

I'm not sure I understand why this happens:
[kent@mbp ~]$ helm fetch deis/deis-dev
---> Fetched chart into workspace /Users/kent/.helm/workspace/charts/deis-dev
---> Done
[kent@mbp ~]$ helm generate deis-dev
---> Ran 2 generators.
[kent@mbp ~]$ helm generate deis-dev
---> Ran 4 generators.

I'm gonna guess that whatever gets generated also has helm:generate in the headers

Shouldn't helm generate only be looking in the tpl dir for templates?  If the generated manifests still mentioned helm:generate (albeit in a comment), shouldn't those be ignored?  I'm probably misunderstanding something.  fwiw, this is with the official deis-dev chart, so the issue should be easily reproducable.

Maybe the generated files shouldn't contain the helm:generate line?

We don't strip anything out of a file because we don't want to presume intent.
Is this still a problem somewhere? I'd like to take a look.

Alright, so I reproduced the problem with the deis-dev chart.
The reason it is happening is because the helm:generate header is inside of a manifest file, and that file operates on itself as input.
There are two design decisions that we made that are resulting in this problem. Both decisions were made intentionally, but I'd be open to reconsidering.

helm generate operates on an entire chart, including the directory manifests. While we don't recommend people store templates in manifests, we don't prevent the generator from checking that directory. We could do this.
helm generate itself NEVER modifies a file. So it will not strip a generate header from output, or do any other modification. And the template engine doesn't remove helm:generate headers. While we could change this behavior, I'm not all that keen on this.

Thoughts?

I think requiring templates to live only in tpl/ (or ignoring them in manifests/) is too much magical behavior. At least I wouldn't expect it.
Stripping the helm:generate header seemed reasonable to me. Or you could rewrite it as helm:generated and otherwise keep it intact. The problem is obviously when there's a template actually in the destination manifests/ directory, then helm:generate would only work once under this proposal, and you'd have to "reset" the templates by editing them to say helm:generate again...ugly.
I guess on balance solution 1. seems saner. Or there's:

leave this all as-is since the bug is mostly benign :disappointed:

If we leave it as is, it remains a head scratching moment for anyone who just wants to regenerate secrets and such on the chart they already have (meaning no update) to bootstrap a second cluster or replacement cluster.

Or... we could use the --exclude flag that's been in there the whole time, but which I forgot about.
$ helm generate --exclude=manifests


Adding required permissions to enable uploading of CodeQL results

Related Issues

Closes #
Helps #

Why is this change being made?
Although pr build succeeded, the builds triggered after merge of the change to enable CodeQL failed due to some missing permission needed to upload the CodeQL scan results.
What is being changed?
-Adding the required permissions.
-There was also a warning about codeql-action version v2 getting deprecated in December, hence the version is bumped to v3
How was the change tested?
Will verify from the build after merge

@ogbolade-msft please create a new bug in the repo to track the issue and connect it here.

Can you add a link to the doc explaining that this is the solution for the issue?


Stream does not close when pulling an image

Crate version: 0.9.1
OS: MacOS 12.3.1
Output of running docker version on the command line:

Client: Docker Engine - Community
 Cloud integration: 1.0.12
 Version:           20.10.5
 API version:       1.41
 Go version:        go1.13.15
 Git commit:        55c4c88
 Built:             Tue Mar  2 20:13:00 2021
 OS/Arch:           darwin/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.5
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       363e9a8
  Built:            Tue Mar  2 20:15:47 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.4
  GitCommit:        05f951a3781f4f2c1911b05e61c160e9c30eaa8e
 runc:
  Version:          1.0.0-rc93
  GitCommit:        12644e614e25b05da6fd08a38ffa0cfe1903fdec
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

When pulling an image, per the example in the repository, the image is able to be pulled successfully per the logs, but then the program just hangs, without moving out of the loop, at the end. Is there a way to close the stream or send None when the pull has finished?
    let pull_opts = PullOpts::builder().image(config.image.clone()).build();
    let images = docker.images();
    let mut stream = images.pull(&pull_opts);

    while let Some(pull_result) = stream.next().await {
        match pull_result {
            Ok(output) => {
                println!("{:?}", output);
            },
            Err(e) => eprintln!("{}", e),
        }
    }

The issue should be resolved as of https://github.com/vv9k/containers-api-conn/commit/b172a97ca7163c6236ec54d097e84ac59009aef6 That I just commited. The fix was in a separate crate so you might need to cargo update before running your project again to see the results.
I've tested using the example of this crate:
$ cargo r --example image pull centos:latest

Before this commit it would hang at the end and after it correctly ends the process.

Thanks for the quick reply! Really appreciate it. I will go ahead and update the project, that seems like it will resolve the issue.


Please support ADTS encapsulated track (.aac files)

Summary
Many of our files are .aac files, which is encoded in ADTS.
Note : https://github.com/taglib/taglib/pull/856/files
API design
No response

Sure, I'll look into this for 0.9.0 :slightly_smiling_face:.

@vapormusic Could you checkout #71 to see if everything is working as expected?

Its been two weeks, so I'll just merge #71 as is.


Bug: Coil the Blue manifest missing & Zombie game errors

Describe the bug
Coil the blue:
--> manifest.json is missing
--> extension window styles need to be fixed
Zombie game:
--> manifest.json wrongly configured.
--> size need to increase for extension window.
To Reproduce
Steps to reproduce the behavior:

Go to chrome extensions
Click on load unpacked
Scroll down to Coil the Blue or Zombie Game
See error

Expected behavior
Extensions should work properly
Screenshots

Desktop (please complete the following information):

windows (chrome browser)

Additional context
please assign me under GSSoC'24

How many points you earned @anisharma07 ? If 150 crossed than close all the issues


Sensors not updating

This project is awesome to remove the wrapapi dependency. Also love that the individual sensors show up in Home.app. Am seeing the sensors but the sensor states don’t seem to update in Home.app, eg when I open a door or window. Happy to help debug.

@djstarr I'll definitely look into this as I have the same issue. Can you list the number and types of sensors you have (motion-sensor, contact-sensor, and leak-sensor)? I only have motion and contact sensors, but it'd be nice to test with the leak one as well.

Cross-posted from
https://github.com/mkormendy/node-alarm-dot-com/issues/2

Thanks for your work on this. I have a smoke detector, glass break, 3 door sensors and 2 keyfobs all showing up in HomeKit now. Status does not report, but it’s promising to have them appear at all.

@mkormendy I have 1 motion sensor and it appears to be working, properly showing as motion detected in Home.app. I also have 4 groups of window/door contact sensors, 1 keypad, 1 group of glass break sensors, and 1 carbon monoxide detector.

@djstarr well that's good news! I have motion sensors and they are not reporting motion detected, so I am wondering if there's a delay. How long did it take for the system to report the motion on your Home app?

@mkormendy Now that I’m looking at it more closely, I think it’s just perpetually detecting motion. Doesn’t seem to reset. Turned on notifications to see if I can better monitor activity.

@mkormendy awesome work on this!  Ive got it running, and the panel arming states appear to be working now (Yay!).  It is also detecting my sensors (Motion Detectors, Door Sensors, Glass Break Sensors) which is pretty cool.  However, those sensors don't appear as accessories in the Home App.    I also get a number of 'Warning: Sensor with unknown state 0' being logged every minute for each sensor.

@djstarr let me know!

@amitgandhinz you say that it is "detecting" your sensors, but "they don't appear as accessories" in the Home App. What do you mean by "detecting"?

@mkormendy by detecting, I mean that when home bridge starts up, I see in the logs things like Added sensor Back Door, etc.  This is however immediately followed by the Warning: Sensor with unknown state 0.  Once homebridge is fully started up, I continue to get the Warning messages.

@amitgandhinz please open a separate issue for the problems you are experiencing. This issue thread deals with sensors showing up in the Home app but their states not updating.

created https://github.com/mkormendy/homebridge-node-alarm-dot-com/issues/4 for my issue

I confirm the same behavior as @djstarr mentions. The motion sensor perpetually reports motion detected.

Ok, have a little more detail. The motion sensor isn’t perpetually detecting motion. It just seems that the delay to reset the sensor is so long that I still haven’t “seen” it. But it was reset over night and walking out to our main living area triggered within a couple of seconds. It may also be staying on given the motion sensor is in the main open living area of our first floor. One last note is that I’m living on the latest iOS 12 betas. Am still not entirely sure what additional data would be useful to you but I’ll share what I can.

Not on my main phone, but im ready to make the jump. Is HomeKit rock solid on the latest beta? I have a very large HomeKit setup and wanted to certain before I make the jump.

For the first time I chose not to do the beta program, so I am not sure, but I think the public release is coming out in a week's time to coincide with the reveal of the new iPhone, so I'm going to wait for that before I update to 12.

Have been on iOS 12 since beta 1 and same for macOS 10.14 Mojave (which includes Home.app). No major issues with the homebridge setup. YMMV.

Update, it's odd, I've now been getting notifications about my door contact sensors that doors were open and closed exactly when they happened.
However I'm still not getting the notifications of movement from my motion sensors.
Not sure why or how they started working, since I haven't actually made any updates or changes to the code on my live homebridge setup.

After some testing, I have come to what I feel is an unfortunate conclusion.
My testing can confirm that the sensor states are being detected correctly, and homebridge does poll for them, and they DO show up.  However, the fact of the matter is that alarm.com website, nor the mobile app, don't report the events fast enough before they get deactivated.
The test case I used was at my entrance where I have a door contact sensor, and a motion sensor as well.
Opening the front door took anywhere from 45secs-1.5mins to report to the website api that the state has changed to 'Open'. Add the addition polling time  that is either built into the Home.app or into homebridge to query states of accessories (could be anywhere  up to 30secs). I know this because I left the app open while waiting and had my stopwatch on my watch counting until the icon changed with a little animation of the contact sensor being triggered.
This worked as well when I closed the door and about a minute and a half later the door contact sensor showed as closed.
The motion sensors are another story, and the data object received from alarm.com always showed the state of the sensor as 'Idle', and never anything else. I also noticed that my motion sensors (wired only) have a red light that shows that it detected motion. This light would never stay on for longer than roughly 3 seconds before going off for a second and then back on again - regardless of my still constantly making considerable motion and never stopping.
My keypad screen, which just so happens to be at the front entrance too, did register my motion on the screen and that the system was actively 'Open', however the second I saw that state on the keypad, I then immediately queried the interface and received no change.
It seems that the motion sensors themselves are only allowed to report motion for a short time, and that signal gets sent to the keypad to register that the system is open then quickly closed again, and then open again.
At the same time, I'm sure the motion sensor trigger sends a signal to the cellular modem in the alarm.com panel, connecting to the alarm.com servers, and reporting what the system detected.
This is never real-time for me. My mobile app doesn't actively report motion in the history panel. However the history panel does register it eventually (2 minutes or more), but so late in time that it's useless, and reset or made idle again before the json object gets updated on the website API that I poll with the node interface I built.
It's of note that I have top tier fiber internet, so my internet speed is ludicrous and never laggy.
I thought about adding a poll timer to poll more frequently like every 5 seconds or 10 seconds, but no matter how short between polls I made to the alarm.com server, I could never get the motion sensor to be anything but 'Idle'. I think this is an inherent result of the entire Alarm.com network/connectivity setup.
That being said, I am going to close this ticket as unresolved unless something improves or someone sheds light about my misinterpretation of the setup and the resulting code.

@mkormendy oddly enough I too received my first status change this morning around 9:30 am PST. I had installed your updated plugin this past week and was getting excited by the inclusion of all my sensors in HomeKit etc., albeit them not updating yet. Then yesterday I enabled a Status notification in the Home app for our Front Door. Well I received a notification that the door was opened and then another when it was closed. I wasn’t home at the time so I can’t say what sort of latency there was but still strange that all of a sudden I received a notification. But I didn’t receive any yesterday and the Front Door was opened / closed multiple times. I’m going to enable a few other notifications and see what happens.
In any case this definitely puts the effectiveness of these sensors / HomeKit into question.
The one thing I’ll add is that my notifications from the Alarm.com app are typically pretty immediate, at least they are for my outdoor motion sensors triggering a iOS notification. I’ll do some more tests when I can.
Thanks for all your work on this!

I've noticed that the Alarm.com app Push Notifications are delayed anywhere from 5 seconds to 1 minute on my system. This means that the communication from the panel to Alarm.com servers to the Apple Notification Servers (which handle push notifications) are even delayed before they reach the phone Alarm.com app.
Unfortunately we can't listen in on those specific push notifications to the app because they are encrypted from the Apple Servers to the Alarm.com app on the phone with SSL certs. So we are relegated to waiting for the Alarm.com website to update it's sensor states which is slow.

Is there a way to stop the plugin from creating the HomeKit sensors (based on the sensors I have)? That is, since mine are never updating (rarely the Front Door updates)  they're just taking up lots of space in my Home App. Or do you still plan on figuring out how to get them to update more consistently?
Thanks!

I ended up cutting a huge cedar tree down this past weekend, but initially planned to spend time implementing a couple user-configuration options to hide messages in the log as well as hide different sensor accessories since some of them don't update.
I have actually had more reliability with the contact sensors lately. They let me know that a door is open or closed consistently now, albeit a little less-immediate, they do actually fire-off nonetheless.

I see. Good to know.
Any ideas why the Contact sensor notifications would be sporadic?

No, the Alarm.com app is pretty consistent. I’ve testing the front door sensor specifically and I will always receive a notification from the Alarm.com app and only sometimes from the Home App.
Also, what is the purpose of the Homebridge plugin logging in to Alarm.com every 10 minutes? Is this the temporary polling that you have in place? If it’s only polling every 10 minutes then how are certain things like an System Armed command sent immediately (if we’re in the middle of the 10 minute pause)? It seems like ‘any’ status change would update and not just system arming actions etc.

I've got some testing to do myself and I've made a list of different scenarios.
Did you manage to see if the notifications show up for your door if you open it long enough?

I tested it a bit. Like you found it’s not good news.
Some general notes:
Alarm.com App Notifications:

Not precise. Held the front door open for 3 minutes and it didn’t register in the App for at least a few minutes. And it’s worse because it timestamps it at the time of the notification and not the actual time. But I swear sometimes it’s more accurate. I’ll test some more this evening.
These seem to at least be consistent in that if an event ‘happens’ it is recorded, or I am notified.

HomeKit

Held the door open for 3 minutes and closed, never received a HomeKit notification.

Again, I’ll test more this evening but if it ends up that these aren’t fairly reliable I’ll end up just using the panel arm / disarm functions with Homebridge and hide the rest.
I’m interested to see what else you find.


positional encoding fix

This is the fix for the positional encoding. I have run the experiments and the final
loss is the same with either positional encoding. I don't really know how to evaluate
if the model is better with this change

Thank you for the contribution @alalbiol !
It probably doesn't make too much of a difference because the model is powerful enough to adapt for the mistake and still properly classify MNIST digits. It probably would be different on another dataset.


Show quantitative color legend

Refer to https://github.com/higlass/higlass/blob/caf230b5ee41168ea491572618612ac0cc804e5a/app/scripts/HeatmapTiledPixiTrack.js#L580


Latest versions in snap or other repositories

Hi!
Version 5 is not available in snap, even though it's been quite some time since it was released. What's the holdback?
Other question is if it's planned/considered to distribute the app in conventional linux repositories like apt? If not why?

Snap is currently hosted on k8slens.dev. We are not planning to release it onto snapcraft. We have not considered yet hosting a third party apt registry yet.

related https://github.com/lensapp/lens/issues/3273

@Nokel81 - is there any movement on publishing the packages to yum/apt/snap repositories?  Just want to automate the upgrade process, which is currently pretty painful to do compared to everything else.


CASMINST-5935 / CASMINST-5904

Address IUF doc issues CASMINST-5935 and CASMINST-5904.
Checklist

[x] If I added any command snippets, the steps they belong to follow the prompt conventions (see example).
[x] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in Cray-HPE.
[x] My commits or Pull-Request Title contain my JIRA information, or I do not have a JIRA.

/backport release/1.4


[NETBEANS-1074] Module Review j2ee.sun.ddui

changed license headers in five files
added  license headers to two file
added 55 graphic files to licenseinfo.xml

@junichi11 @matthiasblaesing Please review the changes. Thanks. :)


ntr: abolished mitotic chromosome condensation at the kinetochore

def
A cellular process phenotype observed in the vegetative growth phase of the life cycle in which mitotic chromosome condensation at the kinetochore is abolished.
descendent of
abnormal mitotic chromosome condensation
PMID:21633354
Taken together, these results indicate that the pools of condensin at kinetochores and along the chromosome arms, which are recruited respectively by the Pcs1–Mde4 complex and TFIIIC, are functionally separable (Fig. 1e).

also see https://github.com/geneontology/go-ontology/issues/12135

It's the chromosome (DNA, histones, etc) rather than the kinetochore that condenses, so I think it would be better to use "centromere" in the term name, and "kinetochore" is a synonym.

abolished mitotic chromosome condensation at centromere FYPO:0005025
(with "kinetochore" synonym)

adjusted name to match GO:1990893

edit file: fd602879fa65355870ae8d5088ae34201572015f
release: 181b3899dabcbb4162464ba5e7afb857bd6e6776


Add 'middle' value for legend

Hi, I am using your script to visualize the difference of the stock price. I want to use 'red' to represent decreasing and 'green' to represent increasing. But the HCL interpolation is ugly since the middle color is brown.
Is it possible to define a 'middle' color, so that I can use 'white' to guide the color interpolation and make the plot better? Thank you very much.

Added in v4


fixes for RTS-257

This commit writes the DDL version to the object meta data and also remove the time series local index which has been passed along with the object.

@borshop merge


[Feature] Scheduled pauses for speedtests

General

[X] My feature does not exist in the latest version of MySpeed.
[X] I have checked that my feature has not been suggested by anyone else.

Your Idea
I would love the ability to automatically pause tests at a certain time every day, for a specified length. I game at the same hours every night and can usually notice a short ping spike when the speedtest runs, and I would be alright with just skipping a couple hours to prevent it.
This option could be added to the current "Pause tests" dropdown option. (Pause speedtests every day at: __ for __ hours)

Hm... you could also just do it twice or once a day...
There isn't really a need to do speed tests on an hourly bases, remember: Bandwidth (and Energy) is not free.

But a schedule for when MySpeed is paused at an interval doesn't actually sound bad. If you know that you already have bad internet and don't want MySpeed to take up your bandwidth when you need it most, that's a good thing.