SDL2 compilation in macOS fails with a single error.

../network/net.c:68:10: fatal error: 'linux/if.h' file not found
In the network directory, there are the following files: lgy98.c    lgy98.h    lgy98.o    lgy98dev.h net.c      net.h      readme.txt but no if.h.
EDIT: if.h exists under <net/if.h>, if_ether.h under <netinet/if_ether.h> but if_tun.h does not seemingly exist.
EDIT2: added where if_ether.h is located at and a clarification.

NP2kai does not support SDL2 build on Mac.
I do not know how to build and necessary libraries.
According to your report, dependency of header file seems to be complicated.
I am sorry, but I will not correspond.
Thanks.

I added Makefile.mac.
$ make -f Makefile.mac
then maked np2kai executable file.
(You can use Makefile21.mac too.)
Please try it.

Thank you! :D
2018-07-07 2:38 GMT-04:00 AZO<EMAIL_ADDRESS>
I added Makefile.mac.
$ make -f Makefile.mac
then maked np2kai executable file.
(You can use Makefile21.mac too.)
Please try it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/AZO234/NP2kai/issues/54#issuecomment-403193174, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ARaBmTCchzfnbahpDPhuK463WK-P5otdks5uEFd7gaJpZM4VDCbr
.

@AZO234 , the compilation works, the executable runs, but the button to show GUI is used by the "Show Desktop" function of Mission Control (an hotkey that shows the desktop quickly).
I changed the binding, and the GUI works, but the mouse can barely move, as the instant it moves it is locked back to the center of the window.

There was a report on RetroArch of Mac that mouse operation is not good.
Is it a problem with SDL?
About the header file of the network, it seems that it is not just the difference of the directory.
Another implementation is required.
I was informing RA developers,
I currently refraining from developing NP2kai for health reasons.
I'm sorry, I don't have the power to solve problems now.
Regard.

I changed the binding, and the GUI works, but the mouse can barely move, as the instant it moves it is locked back to the center of the window.

I'm experiencing the same issue. building from source (no x11) The mouse resets back to center when attempting to select GUI menu. Unable to use

Since I do not own a Mac,
I operated macOS with a simulator and confirmed the build of NP2kai.
However, it has not been sufficiently inspected until operation.
The mouse cursor is not fixed in the center.
But there seems to be a problem with GUI operation as well.
It will take time to fix it.

Are there hotkeys or keyboard shortcuts to use as workaround?

The GUI key of NP2 is currently assigned to F12 key.
When using on a Mac, which key should I assign?

i think F12 is fine for GUI. Is there a modifier key to select one of the gui menu items without using mouse? like ALT or so?

I examined it in detail.
When clicking the mouse, the coordinates pointed to the center of the screen.
I finally understood the phenomenon.
We changed the coordinates when moving the mouse and use that coordinates when clicking.
I loaded FD and HDD and confirmed that the game can operate.

Excellent AZO!

Since this seems to be solved... I close it. Thank you for your help.


getFrameId behavior when out of range.

This is similar to #1025, however there are some specificities which encourage me to open a separate issue.
Currently, if a frame is not present, getFrameId returns nframes in Release mode but it triggers an assertion in Debug mode:
https://github.com/stack-of-tasks/pinocchio/blob/8f97fda4a93e2b004cacfc29d225156c7bcfd3eb/src/multibody/model.hxx#L236
The fact that the assertion is raised in Debug mode goes contradicts the documentation, which explicitly says
https://github.com/stack-of-tasks/pinocchio/blob/8f97fda4a93e2b004cacfc29d225156c7bcfd3eb/src/multibody/model.hpp#L482
Unfortunately, this property isn't tested in the CI and therefore it is not enforced in Debug mode.
Otherwise, I believe the solution for the future would be throwing an exception, as suggested in #1025. But I am not sure wether this might break some existing code which was relying on it. It would only be true if this code had never been tested in debug mode, but still... Plus, it's better to be consistent with getJointId, I think.
Therefore, I suggest that a proper solution might be the following:

Temporarily remove the assertion
In Pinocchio 3, throw an exception

What do you think?

You can proceed to 1. Next time, I think it would be better to have the discussion in #1025, to avoid issue inflation and repetitions I would say.

Yes, I had thought about putting it in #1025, but since there was the specific issue with the assertion I thought it was better to open a new issue. I'll do it as soon as I can

Solved by #1209


Store the result that caused the UnwrapError, like in Do::Halt

This PR is basically a copy of https://github.com/dry-rb/dry-monads/pull/138 but keeping the naming consistent with Do::Halt (https://github.com/dry-rb/dry-monads/blob/master/lib/dry/monads/do.rb#L24).
I find it handy, to have access to the result, in systems that only implement "happy path" and delegate all exception handling to an external component.

Thanks but it doesn't make it consistent. result in Halt is a result of a method, a returned value. UnwrapError deals with the value! receiver so it's different. I think even source isn't the best choice here. I'll do something about it.


Go to definition goes to stub files instead of actual definitions

Type: Bug
from operator import itemgetter

On operator 'Go to Definition' works fine,
but not on itemgetter, it goes to stub (go to and peek )
Extension version: 2022.8.30
VS Code version: Code 1.70.2 (e4503b30fc78200f846c62cf8091b76ff5547662, 2022-08-16T05:35:13.448Z)
OS version: Windows_NT x64 10.0.19044
Modes:

Repros for me too. Very weird that it goes to the stub for itemgetter, but not operator.

@IanMatthewHuff, might be related to the issue you were seeing?

Oh it seems in main, it shows both:

That's on VS code stable and building from source.
Should we just skip showing the PYI version if there's a .PY one?

Nevermind, that was my bad. When building from source, I end up with a Jedi LS and Pylance. Jedi must be finding the .py definition.

Go-to-definition in Pylance should only show a stub file if no non-stub file locations were found. Go-to-declaration does the opposite.

No, it's not complited!
from operator import add

'Go to definition' on 'operator' - gose to operator.py = fine.
But 'go to definition' on 'add' - goes to _operator.pyi - NOT fine!
from operator import __add__

This works fine! ??

_operator.pyi and operator.pyi - Pylance confused.

When the bug is closed it means the code has been submitted to main. It does not mean it's shipped. This should work when the next prerelease is shipped.
Here's what the prerelease version should show:

The commit was to pylance (private repository) so unfortunately it doesn't show in the issue.
It's being ported to pyright at the moment. Should release today or tomorrow.

@rchiodo, actually we leave Pylance issues open until the fix ships. The dev handling the release will close all "fixed in next version" issues once the release is published.

This issue has been fixed in prerelease version 2022.10.21, which we've just released. You can find the changelog here: CHANGELOG.md


X11 lib not found

Hello,
I'm trying to run a program that uses x11-dl to interact with X11 but it cannot find it.
I have enabled nix-ld with the appropriate libs:
programs.nix-ld.enable = true;
programs.nix-ld.libraries = with pkgs; [
    openssl
    xorg.libX11
    xorg.libXcursor
    xorg.libxcb
    xorg.libXi
    libxkbcommon
    libz
];

I also managed to isolate the problem using a dummy program written in Rust:
use x11_dl::xlib;

fn main() {
    let _xlib = xlib::Xlib::open().unwrap();
}

And I get the output:
[kamereon@nixos:~/test_xlib]$ cargo run
   Compiling test_xlib v0.1.0 (/home/kamereon/test_xlib)
    Finished dev [unoptimized + debuginfo] target(s) in 0.19s
     Running `target/debug/test_xlib`
thread 'main' panicked at src/main.rs:4:36:
called `Result::unwrap()` on an `Err` value: OpenError { kind: Library, detail: "opening library failed (libX11.so.6: cannot open shared object file: No such file or directory); opening library failed (libX11.so: cannot open shared object file: No such file or directory)" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I have read documentation about dlopen and I believe it should act the same way as having an ELF linked binary but I may be mistaken that's why I open this ticket.
I this behaviour expected ? If yes could you tell me how to run a binary with dynamically loaded libraries on Nixos ?
The only way I got it to work but it's quite dirty is by setting the LD_LIBRARY_PATH to the content of NIX_LD_LIBRARY_PATH manually before running cargo run.

If you use a nix environment to build your project, I don't think nix-ld will be used at all.
nix-ld only has an effect for binaries that have their link loader set to /lib64/ld-linux-x86-64.so.2 or similar. To me it looks like what you rather need is to either set LD_LIBRARY_PATH or extend the rpath of your executable to include xorg.libX11.
You can export export LD_DEBUG=libs to get more feedback from your libc why it cannot load libraries.


Consider updating EFS to use elastic throughput mode

💡 Summary
Consider updating the EFS to use elastic throughput mode.
Motivation and context
I heard from an RTA entity that the EFS is very slow in their assessment environment.  I also recently received an email from AWS that stated that one or more EFS shares had been throttled because the current mode (bursting throughput mode) is insufficient to handle the traffic.  The email suggested switching to elastic throughput mode.  (The EFS can also apparently switch between the two modes on demand.)
Contents of the email from AWS:
Hello,

You are receiving this message because, at least once in the past 30 days, one or more Amazon EFS file systems in your account has been constrained by the performance limits of EFS’s Bursting throughput mode. Specifically, these file systems have exhausted the Bursting mode’s available throughput and/or IOPS performance, which could result in a degraded experience for your application or end users.

Your file system is currently configured to use EFS's Bursting Throughput mode. Bursting file systems' throughput capacity is determined by a credit model (“burst credits”) and IOPS capacity is up to 35,000 read IOPS and up to 7,000 write IOPS [1]. When your file system exhausts its “burst credits” or reaches its IOPS limit, throttling of additional I/O can result in unexpected slowness, timeouts, or other application failures for your end users or workloads.

We have identified the following impacted Amazon EFS file system(s) that have been throttled in the past 30 days and require more throughput or IOPS than what Bursting Throughput provides.

A list of your affected resource(s) can be found in the 'Affected resources' tab in the AWS Health Dashboard.

#Action Recommended:
To help your end users and applications to achieve their required throughput and IOPS performance, we recommend that you update your file system configuration to Elastic Throughput mode [2]. When in Elastic Throughput mode, your file system can achieve up to 10 GiB/s of read throughput or 3 GiB/s of write throughput — depending on the AWS Region [3] — and up to 55,000 read IOPS and 25,000 write IOPS. Elastic Throughput charges a pay-as-you-go rate for data transfer to/from your file system, which means you only pay for what you use [4]. You can update your file system configuration to switch between Elastic and Bursting throughput modes on demand.

If you have already updated your file system configuration to one of EFS’s enhanced throughput modes - Elastic or Provisioned Throughput - you can disregard this message.

If you have questions or concerns, please contact AWS Support [5].

[1] https://urldefense.us/v3/__https://docs.aws.amazon.com/efs/latest/ug/performance.html*performance-overview__;Iw!!BClRuOV5cvtbuNI!EogXGg2V2HigA96RB39oMQc433wJ7T0KegTJXaXvs7PGLdiHUkFlAVIMAxzCJ-jhRN8h35x-sfds1IBoiSEYoa6H12FwpyVgFhNv5TjW07-ahyg$
[2] https://urldefense.us/v3/__https://docs.aws.amazon.com/efs/latest/ug/performance.html*throughput-modes__;Iw!!BClRuOV5cvtbuNI!EogXGg2V2HigA96RB39oMQc433wJ7T0KegTJXaXvs7PGLdiHUkFlAVIMAxzCJ-jhRN8h35x-sfds1IBoiSEYoa6H12FwpyVgFhNv5TjWygC6JEY$
[3] https://urldefense.us/v3/__https://docs.aws.amazon.com/efs/latest/ug/limits.html__;!!BClRuOV5cvtbuNI!EogXGg2V2HigA96RB39oMQc433wJ7T0KegTJXaXvs7PGLdiHUkFlAVIMAxzCJ-jhRN8h35x-sfds1IBoiSEYoa6H12FwpyVgFhNv5TjWNjU9s3U$
[4] https://urldefense.us/v3/__https://aws.amazon.com/efs/pricing/__;!!BClRuOV5cvtbuNI!EogXGg2V2HigA96RB39oMQc433wJ7T0KegTJXaXvs7PGLdiHUkFlAVIMAxzCJ-jhRN8h35x-sfds1IBoiSEYoa6H12FwpyVgFhNv5TjWXjBwRUY$
[5] https://urldefense.us/v3/__https://aws.amazon.com/support__;!!BClRuOV5cvtbuNI!EogXGg2V2HigA96RB39oMQc433wJ7T0KegTJXaXvs7PGLdiHUkFlAVIMAxzCJ-jhRN8h35x-sfds1IBoiSEYoa6H12FwpyVgFhNv5TjW_TGYkJ0$

Sincerely,
Amazon Web Services

Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amazon.com is a registered trademark of Amazon.com, Inc. This message was produced and distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA 98109-5210

Implementation notes
None.
Acceptance criteria
How do we know when this work is done?

[ ] The EFS is switched to use elastic throughput mode.
[ ] The assessors verify increased performance of the EFS.

Based on what I read in the AWS documentation, it makes sense to use the elastic throughput mode (versus provisioned mode).


"Sticky properties"

Enable message properties that are propagated through the trace. This can be used both as a "ThreadLocal"-like hack-solution for user-level information, passing some info to a downstream service that the DTOs on an intermediate service does not provide a method of propagating, or for system-level information, e.g. "non-persistent" (i.e. "I don't care whether my messages are dropped on the floor!", which is relevant for purely synchronous "GET"-style service calls), or "non-transactional" (also relevant for "GET"-style stuff, where no persistent state is changed).

This is implemented, by context.[set|get]TraceProperty(String key, [Object value|Class clazz])


extend introspection schema to include oneOf and specifiedByURL

A small proposed change to the introspection query, adding support for two currently proposed directives in the GraphQL spec. They are:

oneOf
specifiedByURL

They are both available to read about here

Hi! Thanks for the PR. Won't that cause a validation error on APIs that don't support these yet?

@tomhoule, thanks for calling this out; I tested several before submitting the PR; however, after more extensive testing, it seems to be very hit-and-miss. I'll update this PR with something that allows for this to be turned on/off via command flags.
I'm unsure about this, and I hope you know the answer. In theory, I should be able to put these behind an @include(if: $variable). My understanding from reading the spec is that the server should ignore the field based on whether the variable is true or false. I've tested this across many public GraphQL services, and it is very implementation-specific.
Is my understanding of how @include and @skip should be handled by servers misguided?

I have pushed the experimental code that puts the IsOneOf behind an @include boolean. This works on more GraphQL services than it did without the include. However, some services don't seem to work as expected with that logic. I have provided this as a reference for my last comment, maybe my understanding is wrong, maybe the syntax is wrong. I'll come back to this early next week.

@tomhoule I've updated the code to remove the included logic; it seems it is not well supported. I've since been able to test various graphql APIs successfully.

all APIs work with the default configuration. This is the same as how it was before this PR
APIs that support @oneOf or @specifiedbyURL work with the options enabled and disabled

@tomhoule, I appreciate that you are busy and doing open source. Above and beyond, your day job isn't full of rewards. I hope you can find some time to review this PR. I want to start contributing more to improve Rust's graphql tooling, hopefully this can alleviate some of the load placed on you.

Sorry for the delay, it's indeed stressful times right now. The contents of the PR look good to me, thank you for the contribution and the perseverance. Let's merge as soon as CI is green.

I've added a commit to fix the clippy errors and the formatting of the schema and excess newline at the end of one of the files. It should be green now

Thanks!


Notebook screen cheese

from my memory, this is what I did

author release notes, edit a MD cell
splitting editor via cmd+\
in the new editor stop editing the MD cell (go in preview mode)
go back to first editor

Good catch, I can easily reproduce this with the release note and markdown notebook.

Good catch, I can easily reproduce this with the release note and markdown notebook.


Update Global Payment Account

After entering a global payment account id after being prompted to, I am redirected to the admin page without the option to update anything.

@BryceStevenWilley I thought this was a minor bug but now I'm noticing when I add a global payment account, it's not actually marked as global anywhere in the case return.
I'm also thinking that we actually don't need the separate call to Update Global Payment account because it's merged into the same REST call--is that right?

Lots of changes happened since I last saw this issue, but I went through and fixed a few issues with updating global payments, should be all good now.


splunk connect for kubernetes is not compatible with recent versions of kubernetes

What happened: Helm chart fails to apply with the error Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "DaemonSet" in version "extensions/v1beta1"
What you expected to happen: Helm chart applies successfully
How to reproduce it (as minimally and precisely as possible): Try to install on kubernetes v1.17.2
Anything else we need to know?:
Environment:

Kubernetes version (use kubectl version): v1.17.2
Ruby version (use ruby --version): NA
OS (e.g: cat /etc/os-release):
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

Splunk version: 7.3.1
Others:

which version of splunk connect for kubernetes are you using? I think you are on an older version and need to upgrade


Wrong columns names after application of train_test_split

bug description
After using train_test_split, the column names of the new datasets do not match with the original ones.
To Reproduce
from sklearnex.model_selection import train_test_split
import pandas as pd

import numpy as np

a = np.random.normal(size = (1000, 2))
df = pd.DataFrame({"s1": a[:, 0], "s2": a[:, 1]})
train_test_split(df)

>> [           0        1
 591  0.511214 -0.045184
 361  0.925741 -0.529199
 588  1.254017  0.464942
 624 -1.212655  0.519108
 357 -1.511506  1.229999
 ..        ...       ...
 156  1.517716  0.487247
 282 -1.312615 -0.910005
 820 -0.913284  0.739692
 652 -0.702827  1.681329
 450  0.079615  0.134168

Expected behavior
from sklearn.model_selection import train_test_split
import pandas as pd

import numpy as np

a = np.random.normal(size = (1000, 2))
df = pd.DataFrame({"s1": a[:, 0], "s2": a[:, 1]})
train_test_split(df)

>> [           s1       s2
 591  0.511214 -0.045184
 361  0.925741 -0.529199
 588  1.254017  0.464942
 624 -1.212655  0.519108
 357 -1.511506  1.229999
 ..        ...       ...
 156  1.517716  0.487247
 282 -1.312615 -0.910005
 820 -0.913284  0.739692
 652 -0.702827  1.681329
 450  0.079615  0.134168

Fixed with train_test_split incorrect column names fix PR

Expected to be in next release as merged change.


support object setters

close #97

oops, the working version is this one: https://codesandbox.io/s/valtio-proxywithcomputed-update-array-bug-forked-xspuk


[PL]Translate new info - switch

I gave a new Polish translation for the new switch command.
ps. I made a link in HTML tags to add target="_ blank" to open in a new browser window... propose to do it in the original EN ... I also send PR #756 (either accept or reject) ;)

Woohoo! First translation of the new screen :)


account info should show details about TLS on the connection if possible.

https://github.com/nats-io/nats.go/pull/996

Ah, correction, any verified connection shows this:
            TLS Verified: issuer CN=R3,O=Let's Encrypt,C=US

never just true, was looking at a older binary


Das_Geek: Watch f%C3%BChrerschein-online-kaufen.com

Das_Geek requests the watch of the watch_keyword f%C3%BChrerschein-online-kaufen\.com. See the MS search here and the Stack Exchange search here.

f%C3%BChrerschein-online-kaufen\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by double-beep in Charcoal HQ


Install and configure Alpine Linux WSL image

manual intervention to configure the first account for the distro is acceptable

Image is installing via chocolatey


Environment failed to launch as it entered Terminated state

DESCRIPTION
Create stack (using required KeyName), and after 8 minutes, run into this:

11:34:57 UTC-0700
CREATE_FAILED
AWS::ElasticBeanstalk::Environment
ChatEnvironment
Environment failed to launch as it entered Terminated state

I don't know enough about the internals to test this locally and find out why it was terminating.  Nothing in the UI is showing why/how it failed, so I don't know how to further troubleshoot and provide something useful.
Any instructions how to run NodeJS + Nginx + Redis locally?  Maybe could reproduce locally.

Same here

That worked for me: https://github.com/amanjuman/elasticache-refarch-chatapp/commit/89b662869fcebb13041d3970eedadda954431b59

Thanks @cfcraspi for the help. Here is the cloudformation template which worked just fine for me after long time fixing the issue.
  Resources:
    RestApplication:
      Type: AWS::ElasticBeanstalk::Application
      Properties:
        ApplicationName: ${self:provider.environment.RESTAPP_NAME}
    RestAppDockerEnvironment:
      Type: AWS::ElasticBeanstalk::Environment
      Properties:
        EnvironmentName: ${self:provider.environment.RESTAPP_ENVIRONMENT_NAME}
        ApplicationName:
          Ref: RestApplication
        SolutionStackName: "64bit Amazon Linux 2 v3.1.2 running Docker"
        OptionSettings:
          - Namespace: aws:elasticbeanstalk:environment
            OptionName: EnvironmentType
            Value: SingleInstance
          - Namespace: aws:autoscaling:launchconfiguration
            OptionName: IamInstanceProfile
            Value: aws-elasticbeanstalk-ec2-role
          - Namespace: aws:elasticbeanstalk:environment
            OptionName: ServiceRole
            Value: aws-elasticbeanstalk-service-role

thank you this helped me a lot

I have added following lines in clodformatoin

Namespace: aws:autoscaling:launchconfiguration
OptionName: IamInstanceProfile
Value: aws-elasticbeanstalk-ec2-role
- Namespace: aws:elasticbeanstalk:environment
OptionName: ServiceRole
Value: aws-elasticbeanstalk-service-role

Thanks @cfcraspi for the help. Here is the cloudformation template which worked just fine for me after long time fixing the issue.
Below is the EB environment i required for my docker application. Replace ApplicationName and EnvironmentName with your choice.
  Resources:
    RestApplication:
      Type: AWS::ElasticBeanstalk::Application
      Properties:
        ApplicationName: ${self:provider.environment.RESTAPP_NAME}
    RestAppDockerEnvironment:
      Type: AWS::ElasticBeanstalk::Environment
      Properties:
        EnvironmentName: ${self:provider.environment.RESTAPP_ENVIRONMENT_NAME}
        ApplicationName:
          Ref: RestApplication
        SolutionStackName: "64bit Amazon Linux 2 v3.1.2 running Docker"
        OptionSettings:
          - Namespace: aws:elasticbeanstalk:environment
            OptionName: EnvironmentType
            Value: SingleInstance
          - Namespace: aws:autoscaling:launchconfiguration
            OptionName: IamInstanceProfile
            Value: aws-elasticbeanstalk-ec2-role
          - Namespace: aws:elasticbeanstalk:environment
            OptionName: ServiceRole
            Value: aws-elasticbeanstalk-service-role

thanks this one helps me a lot.

Welcome @Uditmartyn


Bump protobuf version from 3.19.5 to 3.20.3

This PR bumps the version of protobuf from 3.19.5 to 3.20.3
The main reason is packages like tensorflow require >=3.20.3

Please also add the dependencies label.


Add TypeScript definitons

Adds type definitions to assist TypeScript developers.

Coverage remained the same at 100.0% when pulling 46e7c5ca78ad355d037ca57bbd21ada9fc1f56f4 on janslow:feature/typescript-definitions into aee90f2d2234c62e8b43d3d939b1c853328f8f22 on glenjamin:master.

Coverage remained the same at 100.0% when pulling 3ff39e279f8078c99d50d198512a4ab77c8f3cbb on janslow:feature/typescript-definitions into aee90f2d2234c62e8b43d3d939b1c853328f8f22 on glenjamin:master.

Coverage remained the same at 100.0% when pulling 3ff39e279f8078c99d50d198512a4ab77c8f3cbb on janslow:feature/typescript-definitions into aee90f2d2234c62e8b43d3d939b1c853328f8f22 on glenjamin:master.

Coverage remained the same at 100.0% when pulling 3ff39e279f8078c99d50d198512a4ab77c8f3cbb on janslow:feature/typescript-definitions into aee90f2d2234c62e8b43d3d939b1c853328f8f22 on glenjamin:master.

Looks like the test failures are unrelated to this change, will take a look into that when I get a moment.

Coverage remained the same at 100.0% when pulling fe88392a123679080a092597a848d62177a26b13 on janslow:feature/typescript-definitions into aee90f2d2234c62e8b43d3d939b1c853328f8f22 on glenjamin:master.

Coverage remained the same at 100.0% when pulling fe88392a123679080a092597a848d62177a26b13 on janslow:feature/typescript-definitions into aee90f2d2234c62e8b43d3d939b1c853328f8f22 on glenjamin:master.

Coverage remained the same at 100.0% when pulling fe88392a123679080a092597a848d62177a26b13 on janslow:feature/typescript-definitions into aee90f2d2234c62e8b43d3d939b1c853328f8f22 on glenjamin:master.

Coverage remained the same at 100.0% when pulling fe88392a123679080a092597a848d62177a26b13 on janslow:feature/typescript-definitions into aee90f2d2234c62e8b43d3d939b1c853328f8f22 on glenjamin:master.

Coverage remained the same at 100.0% when pulling fe88392a123679080a092597a848d62177a26b13 on janslow:feature/typescript-definitions into aee90f2d2234c62e8b43d3d939b1c853328f8f22 on glenjamin:master.

Coverage remained the same at 100.0% when pulling fe88392a123679080a092597a848d62177a26b13 on janslow:feature/typescript-definitions into aee90f2d2234c62e8b43d3d939b1c853328f8f22 on glenjamin:master.

Coverage remained the same at 100.0% when pulling 39bbf9f04cd1f3cd8998b2569bfde1389f2c4bac on janslow:feature/typescript-definitions into aee90f2d2234c62e8b43d3d939b1c853328f8f22 on glenjamin:master.

Coverage remained the same at 100.0% when pulling 39bbf9f04cd1f3cd8998b2569bfde1389f2c4bac on janslow:feature/typescript-definitions into aee90f2d2234c62e8b43d3d939b1c853328f8f22 on glenjamin:master.

Sorry, I hadn't noticed the comment about peerDependencies, I've removed that (and the @types/react for consistency). The @types/react is the typescript definitions of React, so that the types of a React element and component can be used.
I've also restricted the context and props types, per your suggestions.
I believe I've also corrected the Selector/Matcher types. Selector can either be a string or a React component type and Matcher can either be an object (i.e., a subset of component props) or a predicate which takes a react node.

Coverage remained the same at 100.0% when pulling 61703035d00b4360cf410d5b0dc6364d1e1e5dd8 on janslow:feature/typescript-definitions into aee90f2d2234c62e8b43d3d939b1c853328f8f22 on glenjamin:master.

Coverage remained the same at 100.0% when pulling 61703035d00b4360cf410d5b0dc6364d1e1e5dd8 on janslow:feature/typescript-definitions into aee90f2d2234c62e8b43d3d939b1c853328f8f22 on glenjamin:master.

Coverage remained the same at 100.0% when pulling 61703035d00b4360cf410d5b0dc6364d1e1e5dd8 on janslow:feature/typescript-definitions into aee90f2d2234c62e8b43d3d939b1c853328f8f22 on glenjamin:master.

Also, out of interest, what's your reason against using peer dependencies for React? Surely "react": ">= 0.14.0" provides flexibility for users, as it adds allows all React versions above/including the supported 0.14.

@janslow ">= 0.14" makes a promise that isn't really true - it's claiming to work with any new version, but I have no idea if we'll work with the next version.
For that reason I just leave it out.

Released in v1.0.0-alpha2

That's great, thanks.


Add GitHub Pages link to documentation

This PR adds the newly functional link to the sphinx-generated documentation to:

the README.md file.
the pyproject.toml file, under the name "Documentation"

Fixes #221.
It might close (decided that it will not for the moment) #109, but #109 contains a list of points that should be done, and that are not fully done yet.

Let's not close the issue #109 yet, I feel like this PR is not fixing it entirely.


Game crashing when tolded to assemble ship Error code: "Error: java.lang.ClassCastException:"

All the info I know to give, please help!
"The game crashed whilst unexpected error
Error: java.lang.ClassCastException: net.minecraft.world.chunk.Chunk cannot be cast to org.valkyrienskies.mod.client.render.ITileEntitiesToRenderProvider
Exit Code: -1"
hastebin link - hastebin is not working atm but I'll update this if it starts working bc despite it all I still love hastebin
pastebin link - https://pastebin.com/iBWU0JUL
privatebin link- https://privatebin.net/?8f5af83e7a13219d#ANPHvE74nFqLb7dJKNYCMwNJHQw4QVEcfUBmUCgCB4ui
ghostbin link - https://ghostbin.com/paste/shSoO
justpastit link - https://justpaste.it/4gtcc
I was snooping the other topics to see if I could fix this myself and a lot of the pastebin links were gone so maybe I can avoid that happening with mine lol.

Try adding a bunch of brackets to the front of the name of the valkyrien skies JAR, such as [[[[valkyrienskies.jar

Try adding a bunch of brackets to the front of the name of the valkyrien skies JAR, such as [[[[valkyrienskies.jar

Okay, that worked but now half my ship is really dark for some reason?

Okay, that worked but now half my ship is really dark for some reason?

That did work though, thank you so much!

That did work though, thank you so much!

it seems to be the shadow from the sails

it seems to be the shadow from the sails


bucket with type FILESYSTEM is not supported

Thanos, Prometheus and Golang version used:
thanos, version 0.8.1 (branch: HEAD, revision: bd8278859b2321aaaa7514edde764816cc039d34)
build user:       root@2227d9a2fdb1
build date:       20191014-12:03:55
go version:       go1.13.1

Object Storage Provider:
FILESYSTEM
What happened:
I tried running store with below command
./thanos store --data-dir /home/ubuntu/thanos/data --http-address <IP_ADDRESS>:19191 --grpc-address <IP_ADDRESS>:19090 --objstore.config-file /home/ubuntu/thanos/thanos_storage.yaml

I get error caller=main.go:200 err="store command failed: create bucket client: bucket with type FILESYSTEM is not supported".
contents of thanos_storage.yaml is
type: FILESYSTEM
config:
  directory: "/home/ubuntu/thanos/data"

What you expected to happen:
Thanos store to run using filesystem
How to reproduce it (as minimally and precisely as possible):

download latest Thanos version from releases
start the store with command above with --objstore.config-file and file contents as above
Full logs to relevant components:

./thanos store --data-dir /home/ubuntu/thanos/data --http-address <IP_ADDRESS>:19191 --grpc-address <IP_ADDRESS>:19090 --objstore.config-file /home/ubuntu/thanos/thanos_storage.yaml
level=info ts=2019-11-20T11:07:37.651512947Z caller=main.go:170 msg="Tracing will be disabled"
level=info ts=2019-11-20T11:07:37.652173682Z caller=factory.go:39 msg="loading bucket configuration"
level=error ts=2019-11-20T11:07:37.652302315Z caller=main.go:200 err="store command failed: create bucket client: bucket with type FILESYSTEM is not supported"

Anything else we need to know:

@bwplotka

Hello! Please use the master version - https://github.com/thanos-io/thanos/commit/b7f3ac9e758d29765f8a0b676f898fef72d73e3a this has not been in any official release yet!


Prep for <IP_ADDRESS> release

This change is

Codecov Report

Merging #53 into master will not change coverage.
The diff coverage is n/a.


Prevented cron jobs from effecting each other by changing parameters

I believe this should be safe across the board, but it definitely warrants review since the global $_GET and $_POST vars are being modified (only for crons).

Kyle just approved via Slack.  Merging...


Added worker.ReplayWorkflowHistory and ReplayWorkflowExecution

Feature request from https://github.com/uber-go/cadence-client/issues/274

Coverage increased (+3.5%) to 64.467% when pulling 1c8c7887021229ec2bcedfd8b0f47651dd86e759 on mfateev:replay_workflow into 72dadb920be49baab8c6098638cb1822bfd6f2b8 on uber-go:master.

Added the requested fixes.


[New] Add tiled layer as basemap

Description
This PR implements Add tiled layer as basemap in Edit and Manage Data category.
URL to README: Add tiled layer as basemap
Linked Issue(s)

swift/issues/6215

How To Test

Open the sample to see the basemap tiled layer.

Screenshots

The iOS implementation has a button to view the other tile package files in the bundle and documents. This was not part of the design, so I did not implement this. Let me know if you think it is needed.

Thank you both!


Add support for ECIES scheme

Hello everyone,
has been ECIES scheme already implemented in openssl? I need it to implement an ETSI standard and, more specifically, to realize communications with a PKI.

Not yet, the problem with implementing ECIES is that there are quite a lot of defined standards with none to govern them all.
That been said, the required components to implement it by yourself are already available in OpenSSL which are ECDH, ECDSA, HMAC, and any reasonable symmetric encryption algorithm preferably (AES).
So in reality, you just have to pick a choice in the sea of various standards and implement it yourself.

Ok, thanks for the quick response! I'll try to implement it.


Gridsome build failing with TypeError

Description
Gridsome build gives me the following error:

Could not generate HTML for "/work/":
TypeError: Cannot read property 'console' of null
at Object. (C:\Users\Micah\Desktop\my-gridsome-site\node_modules\vue-meta\dist\vue-meta.common.js:103:23)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Module.require (internal/modules/cjs/loader.js:692:17)
at require (internal/modules/cjs/helpers.js:25:18)
at C:\Users\Micah\Desktop\my-gridsome-site\node_modules\vue-server-renderer\build.prod.js:1:77671
at Object. (webpack:/external "vue-meta":1:0)

Steps to reproduce
Run gridsome build from command line.
Environment
System:
OS: Windows 10
CPU: (4) x64 Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz
Binaries:
Node: 10.16.3 - C:\Program Files\nodejs\node.EXE
npm: 6.9.0 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: 44.18362.449.0
npmPackages:
gridsome: ^0.7.11 => 0.7.11
gridsome-plugin-tailwindcss: ^2.2.26 => 2.2.26

The site runs on localhost with no problem. I tried npm install gridsome@latest to no avail.

i'm getting the same error, did you find any solution @MFukazawa

@vishnucr Please how did you fix this? Don't seem to get what you said. I'm still getting the same error.

@EbenOladutemu If you are using @gridsome/vue-remark or a similar package to load markdown files from the filesystem, switch to using @gridsome/source-filesystem. This starter project pretty much has everything you need.

Actually, I seem to have found the issue. If you are globally loading a non-SSR compatible Vue component in main.js, the build will fail...

https://github.com/gridsome/gridsome/issues/882


Typing in with async fastapi and encode/databases

First check

[x] I used the GitHub search to find a similar issue and didn't find it.
[x] I searched the FastAPI documentation, with the integrated search.
[x] I already searched in Google "How to X in FastAPI" and didn't find any information.

Description
Will the documentation of https://fastapi.tiangolo.com/advanced/async-sql-databases/ include types in the future? I am currently writing a application with fastapi and encode/databases but after looking into databases i can see that it returns a low level RowProxy object from sqlalchemy. I know that pydantic handles the mapping to the result, but it would be nice to have some type hints in the code. Like that people could see what the database layer returns and don't have to go debug like i did :-)

In that case you are probably looking for an ORM and not encode/databases.
If you want async, you can probably check Tortoise ORM, Gino, or Encode/ORM.

@tiangolo thanks for the response. you are right. encode/databases is not really an orm. its just a layer above sqlalchemy core api. i will close the issue. also fastapi is really awesome :)


"/" is added for filenames even on Windows

Originally reported in forum at https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/tesseract-ocr/O81luGbEbHI/flBHt7OYDAAJ

The thing is that the training software adds a "/" instead of a "\".
I've looked on unicharset_training_utils.cpp, in the line 166, the "/" is added without taking care if the command is used on Windows or Linux.

https://github.com/tesseract-ocr/tesseract/blob/2633fef0b6ac9b616eae3d457bf796076eb8f43c/training/unicharset_training_utils.cpp#L145-147
https://github.com/tesseract-ocr/tesseract/blob/2633fef0b6ac9b616eae3d457bf796076eb8f43c/training/unicharset_training_utils.cpp#L168-170
There also seem to be instances in https://github.com/tesseract-ocr/tesseract/blob/master/training/lang_model_helpers.cpp

Thanks, I was going to do it :)
Jehan

Failed to load script unicharset from:C:\Program Files (x86)\Tesseract-OCR\training/Latin.unicharset
[I'm a Linux guy]
I think that Windows can handle forward slash as path separator.

Yes. Although it is widely unknown, all versions of MSDOS and Windows work with / as a directory separator.

So the problem is not that.
I'll see why I can't load the file.

Are you sure you have  Latin.unicharset in the right path? Are you able to open it in a text editor?
Sometimes if file is not downloaded correctly you may get an error.

OK, so I downloaded Latin.unicharset again and it worked !


Fixing yellow warning for UIManager in ReactNative

Base on fork @tt-driver-apps,  fixed comment for review #266 .
Happy to close it if @tt-driver-apps will update his PR.

updated latest master from WIX

@wixmobile
Just Like
#266
the Jenkins is not building due to licensing issue while downloading the SDK tools...
maybe this could be a solution?
This is the Jenkins error... copied from this build
09:30:20 Unzipping /home/jenkins/.gradle/wrapper/dists/gradle-4.10.2-all/9fahxiiecdb76a5g3aw9oi8rv/gradle-4.10.2-all.zip to /home/jenkins/.gradle/wrapper/dists/gradle-4.10.2-all/9fahxiiecdb76a5g3aw9oi8rv
09:30:23 Set executable permissions for: /home/jenkins/.gradle/wrapper/dists/gradle-4.10.2-all/9fahxiiecdb76a5g3aw9oi8rv/gradle-4.10.2/bin/gradle
09:30:23
09:30:23 Welcome to Gradle 4.10.2!
09:30:23
09:30:23 Here are the highlights of this release:
09:30:23  - Incremental Java compilation by default
09:30:23  - Periodic Gradle caches cleanup
09:30:23  - Gradle Kotlin DSL 1.0-RC6
09:30:23  - Nested included builds
09:30:23  - SNAPSHOT plugin versions in the `plugins {}` block
09:30:23
09:30:23 For more details see https://docs.gradle.org/4.10.2/release-notes.html
09:30:23
09:30:23 Starting a Gradle Daemon (subsequent builds will be faster)
09:30:48
09:30:48 > Configure project :app
09:30:48 File /home/jenkins/.android/repositories.cfg could not be loaded.
09:30:49 Checking the license for package Android SDK Build-Tools 28.0.3 in /usr/local/share/android-sdk/licenses
09:30:49 Warning: License for package Android SDK Build-Tools 28.0.3 not accepted.
09:30:49 Checking the license for package Android SDK Platform 28 in /usr/local/share/android-sdk/licenses
09:30:49 Warning: License for package Android SDK Platform 28 not accepted.
09:30:49
09:30:49 FAILURE: Build failed with an exception.
09:30:49
09:30:49 * What went wrong:
09:30:49 A problem occurred configuring project ':app'.
09:30:49 > Failed to install the following Android SDK packages as some licences have not been accepted.
09:30:49      build-tools;28.0.3 Android SDK Build-Tools 28.0.3
09:30:49      platforms;android-28 Android SDK Platform 28
09:30:49   To build this project, accept the SDK license agreements and install the missing components using the Android Studio SDK Manager.
09:30:49   Alternatively, to transfer the license agreements from one workstation to another, see http://d.android.com/r/studio-ui/export-licenses.html
09:30:49
09:30:49   Using Android SDK: /usr/local/share/android-sdk
09:30:49
09:30:49 * Try:
09:30:49 Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
09:30:49
09:30:49 * Get more help at https://help.gradle.org
09:30:49
09:30:49 BUILD FAILED in 32s
09:30:49 detox[20873] ERROR: [cli.js] Error: Command failed: cd playground/android && ./gradlew :app:assembleRelease :app:assembleAndroidTest -DtestBuildType=release
09:30:49
09:30:49 npm ERR! code ELIFECYCLE
09:30:49 npm ERR! errno 1
09:30:49 npm ERR<EMAIL_ADDRESS>build:android: `detox build --configuration android.emu.release`
09:30:49 npm ERR! Exit status 1
09:30:49 npm ERR!
09:30:49 npm ERR! Failed at the<EMAIL_ADDRESS>build:android script.
09:30:49 npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
09:30:49
09:30:49 npm ERR!  Exit status 1
09:30:49 npm ERR!
09:30:49 npm ERR! Failed at the<EMAIL_ADDRESS>e2e:android:ci script.
09:30:49 npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
09:30:49
09:30:49 npm ERR! A complete log of this run can be found in:
09:30:49 npm ERR!     /home/jenkins/.npm/_logs/2019-06-06T07_30_49_505Z-debug.log
09:30:49 Build step 'Execute shell' marked build as failure
09:30:51 Finished: FAILURE

What is the hold up?

maybe @donghungx can check it?

or maybe @Inbal-Tish ?


SOLR-15485: discourage Collections.singleton.forEach use

https://issues.apache.org/jira/browse/SOLR-15485

It's mind boggling to me what thought process led to that line of code in the first place ;-)  I like to think I'd catch that in a code review.

#213  to action post-commit review feedback.


typos found in INB*/IND* directories

More corrections for trivial touch-typing slips.

Well, so we could argue about the correct spelling of "premise"/"premiss"... but I won't. Thanks for finding all these typos.


(WIP) test windows askpass

ignore in favour of #414

ah idk if this handles the env var issue on windows; also, AIUI the password will still fail because Write-Output necessarily adds a "\n" but getting to that stage would be a win I think


New Setup Sucks

Describe the bug
It is not possible to launch OpenDevin using the new instructions/process. The old process worked flawlessly.
Steps to Reproduce

Follow the instructions

Expected behavior
Working Open/Devin
Actual behavior
Can't get past "uvicorn opendevin.server.listen:app --port 3000" command.
Additional context
I've lost interest. I know developers are hard at work on this critical, fast-moving project. I'll be back when things have stabilized.
Again, I appreciate your work.
1of13

Same here, could not find the requirements.txt suddenly

@1of13 Setup was changed to use pipenv with Pipfile instead of requirements.txt

You can use pipenv to generate a requirements.txt file
pip install pipenv
pipenv requirements > requirements.txt

@1of13 please try to be a little more polite 😄 we're all working for free here.
We are actively discussing what the best package manager is. Python package management is hard

I followed the pipenv, and now encountered a torch lib could not be found error, when I tried to start the server. We are quite excited with the possibilities of this platform and hence I will wait for this platform to be stable to try out actively. Many thanks and appreciate all the effort here.

This is probably fixed by the transition to poetry, please try out with the new directions!


ci: Cache cocoapods cache dir

~/.cocoapods/ folder is too big to cache. Especially ~/.cocoapods/repos/cocoapods/ is the problem.


Standardises and centralises compacted item handling

Moves compacted item determination out of FactoryMod and into CivModCore. This is meant to make it easier for other plugins to determine whether items are compacted without roundabout testing, effectively hard-coding predicates based on how FactoryMod is configured.

After the most recent commits, compacted items no longer contain the "Compacted Item" lore. That lore is instead added just prior to the item being sent over the network. This doesn't contaminate the original item, see screenshot of using /debugging rawitem:

I like the way you've approached this, it makes it look like compacted items should've always been done this way. I'll give it a proper review when I have the time.

Thanks :) I've just noticed a few little things to clean up like this and this(https://github.com/Protonull/CivPlugins/blob/9f3a17d1400e1e67ac5a297a2e587cb2d5c9dbde/plugins/civmodcore-paper/src/main/java/vg/civcraft/mc/civmodcore/inventory/items/compaction/Compaction.java#L19), but other than that it should be good to go, pending some verification testing.

Just tested this with FactoryMod. I used /fmtest give recipe INGREDIENTS adv_xp_1 to give me all the inputs that XP 1 of the Advanced Cauldron and ran it, and it successfully produced 2 compacted emerald blocks. I then ran those through a decompactor and got 2 stacks of emerald blocks.

Just realised that this'll need to include a new ItemExchange rule modifier since items wont have the lore anymore to match against.

Will this also affect wordbank recipes that use compacted items?

Will this also affect wordbank recipes that use compacted items?

Yeah, it probably would as it changes the hash of the item, though keep in mind that the 1.20.5 update will probably break most, if not all wordbank recipes, for the same reason.


[Device Support Request] TS0601 by _TZE204_nklqjk62

Problem description
I'm new with ZHA, and my first difficulties were this product, it seems to be unsupported at this moment, and i don"t know how to make hard code python for that zigbee device.
I don't really know how to do this.
Solution description
I need a python hard code probably
Screenshots/Video
Screenshots/Video
[Paste/upload your media here]

![image](https://github.com/zigpy/zha-device-handlers/assets/27150945/39d6196b-a288-43a9-bc78-611b8b834754)
Device signature
Device signature
[Paste the device signature here] "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>, omplex_descriptor_available=0,  user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>,  mac_capability_flags=<MACCapabilityFlags.FullFunctionDevice|MainsPowered|RxOnWhenIdle|AllocateAddress: 142>,  manufacturer_code=4417, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752,  maximum_outgoing_transfer_size=66, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True,  *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=False, *is_full_function_device=True,  *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True, *is_security_capable=False)",

Diagnostic information
Diagnostic information
[Paste the diagnostic information here]

Logs
Logs
[Paste the logs here]

Custom quirk
Custom quirk
[Paste your custom quirk here]

Additional information
No response

these quirks seem to work
"""Tuya based cover and blinds."""
from typing import Dict
from zigpy.profiles import zgp, zha
from zigpy.quirks import CustomDevice
import zigpy.types as t
from zigpy.zcl.clusters.general import Basic, GreenPowerProxy, Groups, Ota, Scenes, Time
from zigpy.zcl.clusters.security import IasZone
from zhaquirks.const import (
DEVICE_TYPE,
ENDPOINTS,
INPUT_CLUSTERS,
MODELS_INFO,
OUTPUT_CLUSTERS,
PROFILE_ID,
)
from zhaquirks.tuya import NoManufacturerCluster, TuyaLocalCluster
from zhaquirks.tuya.mcu import (
DPToAttributeMapping,
TuyaMCUCluster,
TuyaOnOff,
)
from zhaquirks.tuya.ts0601_dimmer import TuyaOnOffNM
ZONE_TYPE = 0x0001
class ContactSwitchCluster(TuyaLocalCluster, IasZone):
"""Tuya ContactSwitch Sensor."""
_CONSTANT_ATTRIBUTES = {ZONE_TYPE: IasZone.ZoneType.Contact_Switch}

def _update_attribute(self, attrid, value):
    self.debug("_update_attribute '%s': %s", attrid, value)
    super()._update_attribute(attrid, value)

class TuyaGarageManufCluster(NoManufacturerCluster, TuyaMCUCluster):
"""Tuya garage door opener."""
attributes = TuyaMCUCluster.attributes.copy()
attributes.update(
    {
        # ramdom attribute IDs
        0xEF02: ("dp_2", t.uint32_t, True),
        0xEF04: ("dp_4", t.uint32_t, True),
        0xEF05: ("dp_5", t.uint32_t, True),
        0xEF0B: ("dp_11", t.Bool, True),
        0xEF0C: ("dp_12", t.enum8, True),
    }
)

dp_to_attribute: Dict[int, DPToAttributeMapping] = {
    # garage door trigger ¿on movement, on open, on closed?
    1: DPToAttributeMapping(
        TuyaOnOffNM.ep_attribute,
        "on_off",
    ),
    2: DPToAttributeMapping(
        TuyaMCUCluster.ep_attribute,
        "dp_2",
    ),
    3: DPToAttributeMapping(
        ContactSwitchCluster.ep_attribute,
        "zone_status",
        lambda x: IasZone.ZoneStatus.Alarm_1 if x else 0,
        endpoint_id=2,
    ),
    4: DPToAttributeMapping(
        TuyaMCUCluster.ep_attribute,
        "dp_4",
    ),
    5: DPToAttributeMapping(
        TuyaMCUCluster.ep_attribute,
        "dp_5",
    ),
    11: DPToAttributeMapping(
        TuyaMCUCluster.ep_attribute,
        "dp_11",
    ),
    # garage door status (open, closed, ...)
    12: DPToAttributeMapping(
        TuyaMCUCluster.ep_attribute,
        "dp_12",
    ),
}

data_point_handlers = {
    1: "_dp_2_attr_update",
    2: "_dp_2_attr_update",
    3: "_dp_2_attr_update",
    4: "_dp_2_attr_update",
    5: "_dp_2_attr_update",
    11: "_dp_2_attr_update",
    12: "_dp_2_attr_update",
}

class TuyaGarageSwitchTO(CustomDevice):
"""Tuya Garage switch."""
signature = {
    MODELS_INFO: [
        ("_TZE200_nklqjk62", "TS0601"),
        ("_TZE200_wfxuhoea", "TS0601"),
        ("_TZE204_nklqjk62", "TS0601"),
    ],
    ENDPOINTS: {
        # <SimpleDescriptor endpoint=1 profile=260 device_type=0x0051
        # input_clusters=[0, 4, 5, 61184]
        # output_clusters=[10, 25]>
        1: {
            PROFILE_ID: zha.PROFILE_ID,
            DEVICE_TYPE: zha.DeviceType.SMART_PLUG,
            INPUT_CLUSTERS: [
                Basic.cluster_id,
                Groups.cluster_id,
                Scenes.cluster_id,
                TuyaGarageManufCluster.cluster_id,
            ],
            OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
        },
        # <SimpleDescriptor endpoint=242 profile=41440 device_type=97
        # input_clusters=[]
        # output_clusters=[33]
        242: {
            PROFILE_ID: zgp.PROFILE_ID,
            DEVICE_TYPE: zgp.DeviceType.PROXY_BASIC,
            INPUT_CLUSTERS: [],
            OUTPUT_CLUSTERS: [GreenPowerProxy.cluster_id],
        },
    },
}

replacement = {
    ENDPOINTS: {
        1: {
            DEVICE_TYPE: zha.DeviceType.ON_OFF_LIGHT,
            INPUT_CLUSTERS: [
                Basic.cluster_id,
                Groups.cluster_id,
                Scenes.cluster_id,
                TuyaGarageManufCluster,
                TuyaOnOffNM,
            ],
            OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
        },
        2: {
            PROFILE_ID: zha.PROFILE_ID,
            DEVICE_TYPE: zha.DeviceType.IAS_ZONE,
            INPUT_CLUSTERS: [
                ContactSwitchCluster
            ],
            OUTPUT_CLUSTERS: [],
        },
        242: {
            PROFILE_ID: zgp.PROFILE_ID,
            DEVICE_TYPE: zgp.DeviceType.PROXY_BASIC,
            INPUT_CLUSTERS: [],
            OUTPUT_CLUSTERS: [GreenPowerProxy.cluster_id],
        },
    },
}

"""Tuya based cover and blinds."""
from typing import Dict

from zigpy.profiles import zgp, zha
from zigpy.quirks import CustomDevice
import zigpy.types as t
from zigpy.zcl.clusters.general import Basic, GreenPowerProxy, Groups, Ota, Scenes, Time
from zigpy.zcl.clusters.security import IasZone

from zhaquirks.const import (
    DEVICE_TYPE,
    ENDPOINTS,
    INPUT_CLUSTERS,
    MODELS_INFO,
    OUTPUT_CLUSTERS,
    PROFILE_ID,
)

from zhaquirks.tuya import NoManufacturerCluster, TuyaLocalCluster
from zhaquirks.tuya.mcu import (
    DPToAttributeMapping,
    TuyaMCUCluster,
    TuyaOnOff,
)
from zhaquirks.tuya.ts0601_dimmer import TuyaOnOffNM

ZONE_TYPE = 0x0001

class ContactSwitchCluster(TuyaLocalCluster, IasZone):
    """Tuya ContactSwitch Sensor."""

    _CONSTANT_ATTRIBUTES = {ZONE_TYPE: IasZone.ZoneType.Contact_Switch}

    def _update_attribute(self, attrid, value):
        self.debug("_update_attribute '%s': %s", attrid, value)
        super()._update_attribute(attrid, value)

class TuyaGarageManufCluster(NoManufacturerCluster, TuyaMCUCluster):
    """Tuya garage door opener."""

    attributes = TuyaMCUCluster.attributes.copy()
    attributes.update(
        {
            # ramdom attribute IDs
            0xEF02: ("dp_2", t.uint32_t, True),
            0xEF04: ("dp_4", t.uint32_t, True),
            0xEF05: ("dp_5", t.uint32_t, True),
            0xEF0B: ("dp_11", t.Bool, True),
            0xEF0C: ("dp_12", t.enum8, True),
        }
    )

    dp_to_attribute: Dict[int, DPToAttributeMapping] = {
        # garage door trigger ¿on movement, on open, on closed?
        1: DPToAttributeMapping(
            TuyaOnOffNM.ep_attribute,
            "on_off",
        ),
        2: DPToAttributeMapping(
            TuyaMCUCluster.ep_attribute,
            "dp_2",
        ),
        3: DPToAttributeMapping(
            ContactSwitchCluster.ep_attribute,
            "zone_status",
            lambda x: IasZone.ZoneStatus.Alarm_1 if x else 0,
            endpoint_id=2,
        ),
        4: DPToAttributeMapping(
            TuyaMCUCluster.ep_attribute,
            "dp_4",
        ),
        5: DPToAttributeMapping(
            TuyaMCUCluster.ep_attribute,
            "dp_5",
        ),
        11: DPToAttributeMapping(
            TuyaMCUCluster.ep_attribute,
            "dp_11",
        ),
        # garage door status (open, closed, ...)
        12: DPToAttributeMapping(
            TuyaMCUCluster.ep_attribute,
            "dp_12",
        ),
    }

    data_point_handlers = {
        1: "_dp_2_attr_update",
        2: "_dp_2_attr_update",
        3: "_dp_2_attr_update",
        4: "_dp_2_attr_update",
        5: "_dp_2_attr_update",
        11: "_dp_2_attr_update",
        12: "_dp_2_attr_update",
    }

class TuyaGarageSwitchTO(CustomDevice):
    """Tuya Garage switch."""

    signature = {
        MODELS_INFO: [
            ("_TZE200_nklqjk62", "TS0601"),
            ("_TZE200_wfxuhoea", "TS0601"),
            ("_TZE204_nklqjk62", "TS0601"),
        ],
        ENDPOINTS: {
            # <SimpleDescriptor endpoint=1 profile=260 device_type=0x0051
            # input_clusters=[0, 4, 5, 61184]
            # output_clusters=[10, 25]>
            1: {
                PROFILE_ID: zha.PROFILE_ID,
                DEVICE_TYPE: zha.DeviceType.SMART_PLUG,
                INPUT_CLUSTERS: [
                    Basic.cluster_id,
                    Groups.cluster_id,
                    Scenes.cluster_id,
                    TuyaGarageManufCluster.cluster_id,
                ],
                OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
            },
            # <SimpleDescriptor endpoint=242 profile=41440 device_type=97
            # input_clusters=[]
            # output_clusters=[33]
            242: {
                PROFILE_ID: zgp.PROFILE_ID,
                DEVICE_TYPE: zgp.DeviceType.PROXY_BASIC,
                INPUT_CLUSTERS: [],
                OUTPUT_CLUSTERS: [GreenPowerProxy.cluster_id],
            },
        },
    }

    replacement = {
        ENDPOINTS: {
            1: {
                DEVICE_TYPE: zha.DeviceType.ON_OFF_LIGHT,
                INPUT_CLUSTERS: [
                    Basic.cluster_id,
                    Groups.cluster_id,
                    Scenes.cluster_id,
                    TuyaGarageManufCluster,
                    TuyaOnOffNM,
                ],
                OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
            },
            2: {
                PROFILE_ID: zha.PROFILE_ID,
                DEVICE_TYPE: zha.DeviceType.IAS_ZONE,
                INPUT_CLUSTERS: [
                    ContactSwitchCluster
                ],
                OUTPUT_CLUSTERS: [],
            },
            242: {
                PROFILE_ID: zgp.PROFILE_ID,
                DEVICE_TYPE: zgp.DeviceType.PROXY_BASIC,
                INPUT_CLUSTERS: [],
                OUTPUT_CLUSTERS: [GreenPowerProxy.cluster_id],
            },
        },
    }

hello @evlas did you know where can we have some documentation to test this ? (i'm new too with quirks)

This works, but it's detected as a light instead of a garage door

Paired, quirk seems to be loaded but no enitities shown:

Works fine when setting/reading attributes:

I'm not sure what I did wrong... Any idea I should try/check?

I have the exact same issue, I woke up one morning to find the entity unavailable. Removed the working device to do a re-pair in ZHA and now the light entity is missing and the quirk appears to be loaded
Manually writing to the cluster works.
Has anyone else this or have any suggestions?

Same issue here, although I've never been able to get the Entities showing. Please help! (also, I'm assuming I don't need local tuya or similiar installed, just using ZHA directly)
I've followed the steps, added the custom ZHA py file, adn config entries, but still no entities.

I have the following file entries (but with carriage returns, not sure why they don't display):
Configuration.yaml
zha:   database_path: /config/zigbee.db   enable_quirks: true   custom_quirks_path: /config/custom_zha_quirks
Folders created:

and ts0601_garage.py is as #above

So i didn't get the entity part working but i did figure out how to call the service directly from HA.
Just as a workaround until someone can input why the entity is missing.
Use the call service command - select "Zigbee Home Automation: Set zigbee cluster attribute"
set the conditions as follows (i'll include the yaml)
service: zha.set_zigbee_cluster_attribute
data:
ieee:
endpoint_id: 1
cluster_id: 61184
attribute: 61185
value: 0
That should allow you to atleast write an automation assuming you can call the attribute directly.

Thanks @intra-aud , this works perfectly.  Obviously not the ideal solution, but this achieves everything I needed it to on my dashboard.  I'm calling the set attribute command from a Script, so that I can just add a 'Run' command to my Dashboard under the existing 'Garage' entity card.  I guess we just wait and see if the original tuya entity starts getting fully detected in the future. :)

I had the same problem of no entities being detected.
As I was continously updating the file I missed deleting the cache, basically

(1) deleting the __pycache__ folder in your custom_quirks_path folder is important (see comment here)
(2) adding the database_path to my zha config. Before everything was ignored

zha:
  database_path: /config/zigbee.db
  enable_quirks: true
  custom_quirks_path: /config/zhaquirks/

I used the quirks that create a light and binary sensor, it works for me but even if light was a swtich, I was disapointed to not have a real garage door or gate entity.
Downsides:

I reproduce that with a switch or light, trigger of open/close command was only fired off when entity is turn on.
During opening / closing door, we dont have state return so it can be difficult to see if action has been fired

So, to compensates those inconvenience, I have set up multiple configurations.
In my case, it was for a gate.
Open/close only when turning on
I use a simple automation because I dit not spend much time on this, seems a dirty solution but was a quick fix.
I just turn off light/switch just after it has been turned during 1 second.
alias: "Reset state of Garage door / Gate"
description: ""
trigger:
  - platform: state
    entity_id:
      - light.gate # Or switch.garage_door depending of quirks used
    to: "on"
    for:
      hours: 0
      minutes: 0
      seconds: 1
condition: []
action:
  - service: light.turn_off
    target:
      entity_id: light.gate
    data: {}
mode: single

State of opening/closing
I created some helpers in HA interface:

input_boolean.gate_opening: Switch that when turning on, indicate that gate is in a opening state.
input_boolean.gate_closing: Switch that when turning on, indicate that gate is in a closing state.
input_number.duration_opening_gate: Number of seconds the gate make to open.
input_number.duration_closing_gate: Number of seconds the gate make to close. It can be different of the opening duration.

Then a simple automation to switch on/off the boolean input depending of the state and duration:
alias: "Update gate status"
description: ""
trigger:
  - platform: state
    entity_id:
      - light.gate
    to: "on"
condition: []
action:
  - if:
      - condition: state
        entity_id: binary_sensor.gate_sensor
        state: "off" # Mean that gate is open in my configuration
    then:
      - service: input_boolean.turn_on
        metadata: {}
        data: {}
        target:
          entity_id: input_boolean.gate_closing
      - delay:
          hours: 0
          minutes: 0
          seconds: "{{ states('input_number.duration_closing_gate') | int }}"
          milliseconds: 0
      - service: input_boolean.turn_off
        target:
          entity_id: input_boolean.gate_closing
        data: {}
    else:
      - service: input_boolean.turn_on
        metadata: {}
        data: {}
        target:
          entity_id: input_boolean.gate_opening
      - delay:
          hours: 0
          minutes: 0
          seconds: "{{ states('input_number.duration_opening_gate') | int }}"
          milliseconds: 0
      - service: input_boolean.turn_off
        metadata: {}
        data: {}
        target:
          entity_id: input_boolean.gate_opening
mode: single

With this automation, I have 2 switchs, one will be on when gate is opening the other one when gate is closing.
Obviously, it's not the more reliable you can have. Multiple calls could mess up those switch states, wind will speed up or slow down closing/opening action, gate security could occurs etc.
Gate/Garage door entity
Finally, I can create a custom entity that I could add to my dashboard.
I simply add to my configuration.yaml file a new custom cover entity following HA documentation:
cover:
  - platform: template
    covers:
    gate:
      device_class: gate # can be 'garage' as well
      friendly_name: "Gate (custom)"
      icon_template: >-
          {% if is_state('binary_sensor.gate_sensor', 'on') %}
            mdi:gate
          {% else %}
            mdi:gate-open
          {% endif %}
      value_template: >-
          {% if is_state('input_boolean.gate_opening', 'on') %}
            opening
          {% elif is_state('input_boolean.gate_closing', 'on') %}
            closing
          {% elif is_state('binary_sensor.gate_sensor', 'on') %}
            closed
          {% elif is_state('binary_sensor.gate_sensor', 'off') %}
            open
          {% endif %}
      availability_template: "{{ is_state('binary_sensor.gate_sensor', 'on') or is_state('binary_sensor.gate_sensor', 'off') }}"
      open_cover:
        service: light.turn_on
        data: {}
        target:
          entity_id: light.gate
      close_cover:
        service: light.turn_on
        data: {}
        target:
          entity_id: light.gate

Now I can have a well working card of my gate on my dashboard without any specific card configuration or script calls.
Go further ?
When using this entity in a dashboard, when gate is opening, we will only see a message saying "opening", not really how much time it remain to be fully opened. Like a classic cover, we miss the percentage progression of opening.
I haven't tested it really but it should be pretty easy with the use of attribut position_template instead of value_template in custom entity.
It should looks like something like this:
      position_template: >-
          {% if is_state('input_boolean.gate_opening', 'on') %}
            {{ ((as_timestamp(now()) - as_timestamp(states.input_boolean.gate_opening.last_changed))/states('input_number.duration_opening_gate')|int)|int }}
          {% elif is_state('input_boolean.gate_closing', 'on') %}
            {{ ((as_timestamp(now()) - as_timestamp(states.input_boolean.gate_closing.last_changed))/states('input_number.duration_closing_gate')|int)|int }}
          {% elif is_state('binary_sensor.gate_sensor', 'on') %}
            0
          {% elif is_state('binary_sensor.gate_sensor', 'off') %}
            100
          {% endif %}

Hope it can help some people while we wait a fully integrated module in ZHA 🙂

Thanks for the quirk, it's working fine.
Turning on the switch activate the physical connection for a second, then it is automaticaly deactivated. This is the expected behaviour for a garage door but not for the device I use. I need a normal on/off switch.
Is this behaviour built in the hardware or is it programmed in the quirk? Do you know if there is a software way to modify it??
Thanks a lot!

the built-in quirk is definitely not working and I can't override it:

the built-in quirk is definitely not working and I can't override it:

I'm having the exact same issue.

Hi,
unfortunately I don't have any experiance in quirks.
I've the same problem and with the here quirk posted here it works. But - as already mentioned - as a light switch.
I wonder if this can be changed as the quirk says:
ENDPOINTS: {             1: {                 DEVICE_TYPE: zha.DeviceType.ON_OFF_LIGHT,                 INPUT_CLUSTERS: [                     Basic.cluster_id,                     Groups.cluster_id,                     Scenes.cluster_id,                     TuyaGarageManufCluster,                     TuyaOnOffNM,                 ],                 OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],             },
So it's build in in the quirk. Is there any chance this can be changed to a garage door directly?
Thanks

any updates on this?

@freiadam -> check my post over here: https://community.home-assistant.io/t/how-to-add-a-garage-door-opener-to-zha/454783/6
I got it working with ZHA

@freiadam -> check my post over here: https://community.home-assistant.io/t/how-to-add-a-garage-door-opener-to-zha/454783/6
I got it working with ZHA

Too late for me... I bought a dual-relay-board with an ESP8266-01s as conrtroller for 7€, connected it (it has a 9V to 25V power supply on board) to the internal power connector of my Hörmann motor, used two door sensors as "door is open" and "door is closed" sensors (that way I can even tell which direction the door is going if someone is pressing the emergency button inside or using the original wireless remote) and don't have to invoke magic incantations for ZHA.
After adding a second coordinator for Z2M the TS0601 is working without any problem (but also without any garage), too.


Blank lines option

Is possible to have an option to add blank line rule(s) in the formatter?
Eg transform this
class Temp {
    @Dec1
    prop1! int;
    @Dec2
    prop2! string;
}

to this:
class Temp {
    @Dec1
    prop1! int;

    @Dec2
    prop2! string;
}

or this:
class Temp {

    @Dec1
    prop1! int;

    @Dec2
    prop2! string;

}

@dsherret Any update on this?

I love coming to an issue and being greeting with my own comment 😄
Experimenting with dprint again; would love to see this option. Here's a list of my mental rules for formatting -- it might help decide on which options to add.

Obligatory exactly two blank lines after all imports. Allow at most one blank line between groups of imports.

import a from 'a'
import b from 'b'

import x from './x'
import y from './y'

console.log()

Inside blocks, allow at most one blank line between things.

function () {
  foo()
  bar()
}

If the block has at least one empty line, then padding empty lines are necessary.

function () {

  // first this
  foo()
  bar()

  // then this
  foo()
  bar()

}

That way, a simple class could be written as
class Foo {
  bar: string
  baz: number
}

but a more complex one would, due to blank lines between properties, force the padded lines.
class Foo {

  /** docs */
  bar: string

  /** docs */
  baz: string

}

Bonus points: anything multi-lined in a class forces blank lines around it (which in turn forces the padding.
I love the topic of formatting code. I probably sound crazy to some with the rules I follow, and yet I had to ask myself really hard to define how I format code manually (and subconsciously) to derive all the rules up there 🤔

I am currently experimenting with dprint, and it appears to be superior to many options I have tried so far, such as eslint, prettier, oxc, and biome. The "AST configuration" feature is particularly impressive. dprint is almost perfect and lacks only a few options, and this is one of them.
I largely agree with the proposal made by @lazarljubenovic in https://github.com/dprint/dprint-plugin-typescript/issues/7#issuecomment-1778074041. However, I'm not entirely convinced by the two-blank lines part.
Additionally, I would like to suggest an option to preserve single empty lines and remove only redundant ones. With the AST configuration, this enhancement would make dprint even more powerful.

@lazarljubenovic for the two-blank lines part you are, probably, interested in https://github.com/dprint/dprint-plugin-typescript/issues/394

@dsherret after thinking about the two blank lines proposed earlier, I have come to the conclusion that the best option would be something like 'maintain' | number, where the number represents the count of line breaks. 0 would mean no line break, 1 would represent one line break, and so on. Together with the AST configuration, this would be quite powerful.

This project looks amazing, I'd use it over prettier/biome in a heartbeat once this feature is done.

Is there a vision on how we want this to look like? I would love to give implementing it a go.
@dsherret

While I prefer two lines separating imports from the following code, it doesn't matter all that much to me.
Two cases are a deal breaker though. Class padding, and empty lines in tests.
Here's what I'd like to see:
// foo.ts
class Foo {

    public constructor() {
        // ...
    }

}

// foo.spec.ts
import { describe, it } from "my-testing-framework"

describe('Foo Test', () => {

    it('should do the thing', () => {
        arrange()

        act()

        assert()
    })

    it('should do the thing without arranging', () => {

        act()

        assert()
    })

})

Rather than that:
// foo.ts
class Foo {
  public constructor() {
    // ...
  }
}

// foo.spec.ts
import { describe, it } from "my-testing-framework"

describe("Foo Test", () => {
  it("should do the thing", () => {
    arrange()

    act()

    assert()
  })

  it("should do the thing without arranging", () => {
    act()

    assert()
  })
})

The class padding doesn't seem very useful in this small example, but is so much better as soon as there are generics, constructor arguments or base classes involved.
The tests are too dense even in this small example. It suffers from visual closeness where it should be (describe, it, arrange), but has visual stops inside test cases instead. Also, I like to structure tests in arrange/act/assert, and split them by a newline. If there is no setup code, I leave a blank line to make it clear.
I did implement something (even though my Rust skills are zero, and I don't understand how dprint works at all. It's pretty gruesome, but maybe helps the discussion). I think it might be good enough for my taste, to always have padding. Sure, simple classes don't really need it, but rather this than the opposite.
I fell like a perfect solution would allow me to configure a whitelist of keywords/function names that allow for leading blank lines:
  "allowLeadingBlanks": "/class|describe|it/",

(This would not solve blank lines at the end of a class body, but I could live with that)


Bump Jetty to 9.3 for Accumulo 1.10

Fix flaky build issue with Hadoop 3 profile by using the same Jetty release series as Hadoop 3.0.3,
which is Eclipse Jetty 9.3. Select the latest patched version of 9.3.

All tests passed with both profiles, so I'll merge this, then prepare a 1.10.3-rc1.


Add column name when error occurred while decoding: Null

Motivation
A common error I make is forgetting to map a nullable column using Option, so I receive the error message error occurred while decoding: Null.
I would like the have the column name in the error message so I can easily identify what column was mapped wrongly.

Proposed Solutions
It seems the column name is available in all places the Null error is generated, so it would be nice if the column name is passed to it as parameter, so it can be included in error message.

Additional Information
Example of code where col parameter exists and could be used to identify the column that failed with the Null message:
https://github.com/SeaQL/sea-orm/blob/0c96e133250b7c8ab43a6a99931b82c95f59acc1/src/executor/query.rs#L346-L354

Thank you for your suggestion. I agree with that. PR is welcomed.

Hey @dinhani, welcome! Sorry for the delay! Yeah, it's definitely doable and making it much easier to debug.

For anyone who is reading this, I'll mark this issue as open for contributions :)

@billy1624
hello, Could you please assign me with this issue?

@kyoto7250 done)

@ikrivosheev
Thank you.
I will try it.

Thanks! @kyoto7250 let me know if you need any help along the way :)
Just open a draft PR


[FEA] Improve Scala 2.13 build process to not require building against unstaged git changes

This is a follow on to #1525. The changes in #8592 do not address a concern in the build process in that the CI will build against unstaged git changes. See this thread:
https://github.com/NVIDIA/spark-rapids/pull/8592#discussion_r1240630240
We should generate the pom files directly, and we can put the generated pom files in gitignore, so the CI will be able to build against what it sees as a clean working copy.
Note the CI will not be building Scala 2.13 artifacts until this issue is addressed.

archetype could be an interesting option for pom generation


mgmt, update hdinsights tests to include delete

also update codegen version (to latest) and ci template (to Wes).

/check-enforcer override


Size of camera on large resolutions

On my webpage I have the webcamjs size set to 320 x 240 resolution, on all the resolutions upto and including 1920x1080, the webcamjs control is taking up the entire space I have given it. however on any resolution greater then 1920x1080, the size of the control is staying correct BUT the actual 'camera view' is only taking a portion of 320 x 240, leaving an thick white border below and to the right of the webcamjs control, This occurs within IE 11 and unfortunately I am currently unable to test this using any other browser
Any assistance would be greatly appreciated,
Thanks

So it turns out, the problem is not caused by the screen resolution as such. This is in fact being caused by IE automatically scaling the web page to make it usable at high resolutions but the flash object is not  taking the page scaling into account.. I'm a flash noob, is it even possible to make it scale?

Sooo despite this fitting into the 'no-one really cares pile, after doing some researching i found the cause of this issue which is that within the .as file it explicitly states:
stage.scaleMode = StageScaleMode.NO_SCALE;
changing the above to:
stage.scaleMode = StageScaleMode.SHOW_ALL;
and (after working out how to recompile, FYI instructions are OLD) the web cam flash fallback now scales happily on a 4K display :)

I'm so sorry you had to deal with this.  I fought with the scaleMode in Flash for a long time before deciding that NO_SCALE was the best overall option.  I can't remember the details now, as this was about 7 or 8 years ago when this project was JPEGCam, but something caused the other scale modes (i.e. FIT, SHOW_ALL) to behave strangely on some browsers in some cases.  NO_SCALE was the only option that seemed to work universally.  I apologize you had to spend so much time on this.  Perhaps I should expose the scaleMode as a parameter on the JavaScript side, so people can customize it without having to recompile the Flash movie.

I can definitely say this as a configuration option would have been a great help ... about a month ago lol ... whether or not it would be beneficial to anyone else is unknown as i guess most people that run 4K screens are most likely going to do the update to windows 10 therefore wont need the flash fallback anyway... I could be wrong but i don't think anyone running ie5 will be driving a 4K screen lol.  saying that it would be nice not to have a custom swf file ;)


GetAddOnMetadata API Deprecated

the GetAddOnMetadata API is Deprecated and has been moved to the C_AddOns namespace current works on live but as of <IP_ADDRESS> (TWW Launch) the addon will fail to work
https://github.com/Gethe/wow-ui-source/blob/7547929cf58cc69525bfe193a5444e7acb2646df/Interface/AddOns/Blizzard_Deprecated/Deprecated_10_1_0.lua#L11
All occurrences of GetAddOnMetadata need to be replaced with  C_AddOns.GetAddOnMetadata

Thanks, I will get this fixed as soon as possible.

Fixed in https://github.com/MChambers1992/CopyPasta2/pull/15. Thank you for assisting.


USHIFT-1069: add script for automating ticket status based on branch

/test e2e-openshift-conformance-reduced-arm

/test e2e-openshift-conformance-reduced-arm


Akka license changes

With Akka's move to BSL license and its ASF fork getting traction (https://github.com/apache/incubator-pekko), I think we should consider doing one of the following upon Pekko's release:

Change all Akka-based code to use Pekko.
Create Pekko-based alternatives for all Akka-based code.

Pekko HTTP 1.0.0 should be released this week.
https://pekko.apache.org/docs/pekko-http/current/

I see in the stats that the Akka HTTP interpreter is still used by ~15% of the users of endpoints4s.
For the sake of simplicity, I would like to avoid having both Akka HTTP and Pekko HTTP in this repository (endpoints4s/endpoints4s). It would be better to move the existing Akka HTTP interpreter to its own repository (endpoints4s/akka-http) and have the Pekko HTTP interpreter here. Is there anyone interested in this task?

I was planning to pick this up eventually, and I think I should be able to get started even this week. Moving Akka HTTP to a separate repository and replacing it in this repository with Pekko certainly simplifies things. In regards to the new repository for Akka HTTP interpreter, I assume that because of permissions and secrets required for the initial repository setup, @julienrf you are the only person that can do that, am I correct?

@julienrf I pushed the initial split to https://github.com/endpoints4s/akka-http, but the branch was called split and it got set as default branch. Could you set main as default? I do not have the permissions to do that.

Thank you very much @ptrdom! I changed the default branch to main and also gave you admin access to the repo in case this is needed in the future…


First Tap ignored after scrolling

playground demo to reproduce:https://play.nativescript.org/?template=play-ng&id=HcogW2&v=8
steps to reproduce:
1. open the drawer
2. scroll down little
3. tap label. (it will not work)
4. again tap same label (this time it will work.

it was becasue of margin . my bad. closing issue.


Not working with Internet Explorer

I have this plugin working fine with Chrome and Firefox, any idea how to make it function with IE?
Thanks

Can you please supply a non-working minimal example, preferrably in codepen.io? And don't forget to add your version of Internet Explorer :)

I have the same problem.  It works fine in Microsoft Edge, Chrome but not IE 11 no matter it's in Windows 7 64-bit or Window 10 64-bit.
I've enabled Script sessions but still have the same problems


Not working with targetApi 31 and above

When using this library with targetApi 31 and above, I'm getting this error:
java.lang.IllegalArgumentException: xxx: Targeting S+ (version 31 and above) requires that one of FLAG_IMMUTABLE or FLAG_MUTABLE be specified when creating a PendingIntent.     Strongly consider using FLAG_IMMUTABLE, only use FLAG_MUTABLE if some functionality depends on the PendingIntent being mutable, e.g. if it needs to be used with inline replies or bubbles.
Looking the stack trace it seems that this comes from:
com.firebase.ui.auth.ui.email.CheckEmailHandler.fetchCredential(CheckEmailHandler.java:29)
This is a known issue with Firebase sdk, it's easily fixed by updating the sdk.
This is an important blocker because google play will all start accepting app updates only for apps targeting api 31 or above by November 22.

Sorry, the problem was not related with this library.
If someone else is having the same issue, I solved it upgrading the auth.ui library:
implementation("com.firebaseui:firebase-ui-auth:8.0.2")


Add support for Table of contents block type

Notion has added support for adding and retrieving Table of Contents and Divider block types.
Table of Contents blocks
You can now can add Table of Contents blocks to pages and other blocks.
Below is an example response from Append block children containing a Table of Contents block uploaded to Notion.
{
    "object": "list",
    "results": [
        {
            "object": "block",
            "id": "block-id",
            "created_time": "2021-10-14T18:10:00.000Z",
            "last_edited_time": "2021-10-14T18:10:00.000Z",
            "has_children": false,
            "archived": false,
            "type": "table_of_contents",
            "table_of_contents": {}
        }
    ],
    "next_cursor": null,
    "has_more": false
}

Notion API change log: https://developers.notion.com/changelog/table-of-contents-and-divider-block-types-are-now-supported

Hi there, I'm looking to make my first open source contribution - would I be able to work on this issue?

@mhall002 yeah sure.


Added Gold/Diamond/Ruby textures in response to issue #45

(https://github.com/WSU-CEG-6110-4410/ADAD-Craft/issues/45)

Awesome change, thank you for documenting how to do it future developers. That makes it much easier


Recursive directory creation function (mkdir -p like)

os.makedirs is what is intended here, rather than os.mkdir (I believe):
https://docs.python.org/3/library/os.html?highlight=exist_ok#os.makedirs

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


M3-449 Linode Watchdog Panel

Purpose
Provide means to enable/disable Lassie/Watchdog.
Note
Requires API release 53.3

Coverage decreased (-0.1%) to 29.057% when pulling f345f0295232c332cf6080c904980aefe6b1c043 on rjstires:M3-449 into bfb7cd543f3c4f42a46b7fd5b7572aefc54ed6da on linode:develop.

@alioso This panel needs a breakpoint for smaller screens. The toggle is overlapping

@alioso can you handle that breakpoint for me?

updated breakpoints, again @martinmckenna


Fix workflow syntax

What are the relevant tickets?
N/A
What's this PR do?
Fixes a syntax error in the release github action yaml
How should this be manually tested?
Will test after merge.

👍


Refactor Dockerfile, test scripts and CI (WIP)

Current progress of backports.
Review Checklist

Tests were added to cover all code changes
Documentation was added / updated
Code and tests follow standards in CONTRIBUTING.md

@ambrussimon
A temporary change to .travis.yml to push docker images for this branch would be appreciated, so we can end2end test impact of this PR with our prod CI.


Adding a node while hovering over an area fill causes a stack trace

While debugging the 'navigation' step of the walkthrough, I see we are now able to click the 'add point' button and click on a building interior fill. This is an improvement over before, where we simply weren't allowed to click on the fill (the click wasn't honored).
Now, though, the 'add node' mode thinks we're clicking ON THE WAY and so that we need to add a midpoint to the way- this is absolutely not the case.
Stack trace:
Uncaught TypeError TypeError: Cannot read properties of undefined (reading 'id')
    at <anonymous> (/Users/clarkben/working/RapiD/modules/actions/add_midpoint.js:10:54)
    at _act (/Users/clarkben/working/RapiD/modules/core/history.js:43:29)
    at _perform (/Users/clarkben/working/RapiD/modules/core/history.js:61:28)
    at perform (/Users/clarkben/working/RapiD/modules/core/history.js:220:24)
    at <anonymous> (/Users/clarkben/working/RapiD/modules/core/context.js:318:25)
    at _clickWay (/Users/clarkben/working/RapiD/modules/modes/ModeAddPoint.js:135:18)
    at _click (/Users/clarkben/working/RapiD/modules/modes/ModeAddPoint.js:107:14)
    at emit (/Users/clarkben/working/RapiD/node_modules/eventemitter3/index.js:181:35)
    at _doClick (/Users/clarkben/working/RapiD/modules/behaviors/BehaviorDraw.js:303:10)
    at _pointerup (/Users/clarkben/working/RapiD/modules/behaviors/BehaviorDraw.js:213:12)
    at emit (/Users/clarkben/working/RapiD/node_modules/eventemitter3/index.js:202:33)
    at _pointerup (/Users/clarkben/working/RapiD/modules/pixi/PixiEvents.js:242:10)
    at notifyListeners (/Users/clarkben/working/RapiD/node_modules/@pixi/events/src/EventBoundary.ts:1313:26)
    at notifyTarget (/Users/clarkben/working/RapiD/node_modules/@pixi/events/src/EventBoundary.ts:545:14)
    at propagate (/Users/clarkben/working/RapiD/node_modules/@pixi/events/src/EventBoundary.ts:336:18)
    at dispatchEvent (/Users/clarkben/working/RapiD/node_modules/@pixi/events/src/EventBoundary.ts:240:14)
    at mapPointerUp (/Users/clarkben/working/RapiD/node_modules/@pixi/events/src/EventBoundary.ts:830:14)
    at mapEvent (/Users/clarkben/working/RapiD/node_modules/@pixi/events/src/EventBoundary.ts:261:28)
    at onPointerUp (/Users/clarkben/working/RapiD/node_modules/@pixi/events/src/EventSystem.ts:290:31)

Fixed in 334140e524a1010b2bf49970eaeb844c211b8ca5.


Access Entries are deleted before Helm charts so helm charts stays orphan in the terraform state

Description
We deploy a couple of helm charts inside the same terraform state where the eks module is called. It works like a charm with access entries while creating the resources but it cannot delete the helm resources properly in terraform destroy. The reason is that terraform destroy deletes the access entries before the helm charts.
It was working great in version 19.21.0 with aws-auth configmap

[x ] ✋ I have searched the open/closed issues and my issue is not listed.

⚠ Note
Versions

Module version [Required]: 20.2.1

Terraform version:1.6.6

Provider version(s): 1.6.6

Reproduction Code [Required]

Steps to reproduce the behavior:

Create the eks cluster without giving any access entries.
Deploy a dummy helm chart
Run terrafrom destroy

Expected behavior
Terraform destroy should run successfully
Actual behavior
It deletes the access entries and cannot delete the helm charts so helm charts stays idle at the terraform sate

It was working great in version 19.21.0 with aws-auth configmap

Thats because the cluster creator was granted admin permissions automatically that were outside of Terraform's control. I'm open to ideas but I currently don't see a way to achieve the same.
Also, the guidance will always be - destroy the resources on the cluster first before destroying the cluster. There are a number of reasons for this

Should I add explicit depends_on = [ module.eks] on the resources? Is that only way to let terraform remove the helm charts and then the eks cluster?

you can try, but if its a module then it will face challenges
you are better off separating your infrastructure from your applications. this would be two different statefiles, and you would need to explicitly handle the removal of the applications running on the cluster first, before destroying the cluster

I have the same challenge.
I use terraform-aws-eks-blueprints-addons module to install addons like karpenter. All managed within the same state file.
When I perform a terraform destroy, it may fail depending if the access entry is deleted before or after the helm deployments performed by the terraform-aws-eks-blueprints-addons module.

@nascit you'll need to either separate the cluster infra from the app deployment (recommended route), or follow the steps we provide to carefully tear down resources in order https://aws-ia.github.io/terraform-aws-eks-blueprints/patterns/karpenter/#destroy - and with Karpenter thats even more relevant because its creating additional AWS resources outside of Terraform's purview

Since the permissions are now controlled in code, you will need to handle the destroy situation a little differently as stated above. You can use the following when destroying the cluster to ensure permissions aren't removed too early:
# Necessary to avoid removing Terraform's permissions too soon before its finished
# cleaning up the resources it deployed inside the cluster
terraform state rm 'module.eks.aws_eks_access_entry.this["cluster_creator"]' || true
terraform state rm 'module.eks.aws_eks_access_policy_association.this["cluster_creator_admin"]' || true

Can this module allow us to have the flexibility to use CONFIG_MAP? Time is needed to adopt API_AND_CONFIG_MAP...

Using the built-in example here:
# Comment this line to not using EKS access management control yet. default to false.
# enable_cluster_creator_admin_permissions = true

# Add this line for the cluster to use CONFIG_MAP authentication mode only.
authentication_mode = CONFIG_MAP

Now perform terraform apply and it will fail with bootstrapClusterCreatorAdminPermission must be true when authentication_mode is set to CONFIG_MAP.

@bryantbiggs One thing that occurs to me that might help with this, would be to use depends_on in the output for the cluster_endpoint, forcing it to wait until the access entries and associations are complete. Since the helm provider requires the cluster endpoint as an input, that should get the order of operations correct on both create and destroy.
output "cluster_endpoint" {
  description = "Endpoint for your Kubernetes API server"
  value       = try(aws_eks_cluster.this[0].endpoint, null)

  depends_on = [
    aws_eks_access_entry.this,
    aws_eks_access_policy_association.this,
}

I don't think those are valid - have you tested those?

@bryantbiggs Yes absolutely, using depends_on in an output is 100% valid, and used for exactly this kind of timing issue where an output for a single resource isn't fully available until some other resource completes. S3 bucket and bucket policy is another common one. Or IAM role and role attachments.

They have a doc on it now also: https://developer.hashicorp.com/terraform/language/values/outputs#depends_on-explicit-output-dependencies

Fyi, I am testing a PR to see if I can cleanly apply and destroy the "complete" test on the blueprints-addons project without manually using state rm and target... So far, so good! 🤞

just validated this on the karpenter example which I think is more representative, and it was able to apply then destroy without targets or intervention! Great find - please feel free to open a PR to add these, I don't want to steal your thunder on the great find 😉

@bryantbiggs Done, see https://github.com/terraform-aws-modules/terraform-aws-eks/pull/3000! (And I got the 3000th pr, woot!)

dang, thats a lot of PRs 😅

This issue has been resolved in version 20.8.5 :tada:


Addition of new functionality to NLM denoising

Addition of fastNlMeansDenoisingAbs and fastNlMeansDenoisingMultiAbs which accept both 8-bit and 16-bit input. They use squared sum of absolute value distances instead of sum of squared distances for weight calculation. OpenCL implementation has also been added.
http://code.opencv.org/issues/4143

Extension to 4-channel input.

Addition of overloaded versions which accept separate h-values, one for each channel.

@erikrk, thank you for the contribution! May I ask you about the rationale of the patch? I mean, the NLM method is okay denoising algorithm, not the best one, not the fastest one. With this patch the amount of code implementing just this single algorithm in OpenCV has been increased by an order of magnitude. So I believe there should be some strong reasons to do that.

The main rationale behind working on the NLM implementation is that I am using it myself. As you pointed out NLM is not particularly fast but is does a great job with my data. The current implementation only accepts 8-bit input and uses the same h-value for all channels. Since I needed to process multichannel 16-bit data and use separate h-values per channel I decided to extend the implementation. The OpenCL implementation is also limited to 1-2 channels and the C++ implementation is limited to 1-3 channels. I have extended both of them so they accept 1-4 channels.
This necessitated an extensive refactoring since the current implementation is hard-coded for 8-bit input. Additional code had too be written too, particularly in modules/photo/src/denoising.cpp and modules/photo/src/fast_nlmeans_denoising_invoker_commons.hpp to handle the new combinations of bit depth and number of channels. The files implementing the algorithm itself, modules/photo/src/fast_nlmeans_denoising_invoker.hpp and modules/photo/src/fast_nlmeans_multi_denoising_invoker.hpp have not been extensively modified though.
16-bit/channel data is becoming more and more common and I think that an implementation that only accepts 8-bit input is eventually going to become of limited value. This has also been requested in the above-mentioned issue.

Just to put things into perspective, there are currently 2394 lines implementing NLM in OpenCV and after application of the patch there are 3236 lines (in cuda/nlm.cu, opencl/nlmeans.cl, denoising.cpp, denoising.cuda.cpp,  fast_nlmeans_denoising_invoker.hpp, fast_nlmeans_denoising_invoker_commons.hpp, fast_nlmeans_denoising_opencl.hpp, fast_nlmeans_multi_denoising_invoker.hpp, and opencv2/photo.hpp). That's a 35 % increase. I don't really see how this becomes an order of magnitude.

@erikrk, that's right, increase of the source code size is not severe (but still ~35%). I was mainly talking about the binary size increase, which is something like 800%.

Since separate h value for each channel is extension of a single h value for all channels, can we completely replace the old version with the new one?
what's the reason to have 4-channel denoising? if it's mostly for convenience, probably it makes sense to extract the first 3 channels, do the denoising and then put the original alpha channel back. The extra operations are very cheap, comparing to the denoising time.

can we make the norm type (L2/L1) an additional function parameter? Otherwise there is too many similar external functions.

The external interface has definitely become too complicated. The main reason behind this is that I have tried to maintain full backwards compatibility, both source-wise and binary-wise. If maintaining source compatibility is sufficient, adding the norm type as a parameter with a default value should work just fine.
The main reason for extending to 4 channels is that vector sizes in OpenCL have to be powers of 2. There are 3-component vectors though, but they occupy the same space in memory as 4-component vectors. 3-channel images thus have to be padded up to 4 channels for the OpenCL implementation to work. Consequently, processing of 4-channel images comes with little additional cost. I then decided to the extend the C++ implementation to 4 channels also in order to make it possible to run test cases which compare the OpenCV implementation to the C++ implementation.
The reason for the increase in binary size is that templates are used to generate separate codes for various different cases. This is done for reasons of speed and has not been introduced with this patch. The number of different cases has simply increased substantially. One thing that could be be done if binary size is a concern is to remove the implementations that use a single h-value for all channels. That might affect speed negatively though. If the size of denoising.cpp.o itself is a concern, it could be split up in two, with one file for fastNlMeansDenoising/fastNlMeansDenoisingColored and one for fastNlMeansDenoisingMulti/fastNlMeansDenoisingColoredMulti. That would reduce the size of statically linked binaries that use only one of those two.

I have removed fastNlMeansDenoisingAbs and fastNlMeansDenoisingMultiAbs. Instead I have added a new parameter, normType, which can be either NORM_L2 or NORM_L1, to fastNlMeansDenoising and fastNlMeansDenoisingMulti. Binary compatibility is maintained since the new parameter has only been added to the new overloaded variants that take std::vectorconst& h.

@erikrk, the latest variant looks great! thank you! :+1: