monit: 5.32.0 -> 5.33.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/monit/versions.
meta.description for monit is: Monitoring system
meta.homepage for monit is: https://mmonit.com/monit/
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.33.0 with grep in /nix/store/l05d942gmzh9fs80gvf096ah4dgpbj0f-monit-5.33.0
found 5.33.0 in filename of file in /nix/store/l05d942gmzh9fs80gvf096ah4dgpbj0f-monit-5.33.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
monit

Instructions to test this update (click to expand)

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

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

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

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

1 package built:

monit

Maintainer pings
cc @7c6f434c @wmertens @ryantm for testing.

Result of nixpkgs-review pr 218798 run on aarch64-linux 1

1 package built:

monit


Can use "Repeat" and "Speed" buttons ever

My suggestion is to user can use this buttons before loading any media.

These don't work properly anyway.

I understand that these buttons can not work properly, But for now, user can do pointer events before loading any sound, and in future when these buttons will work like a charm, this previous commit will be usefull. Here is in https://github.com/nt1m/HTML5AudioPlayer/pull/24 pull request.


[setup][eslint] No error, linting or console output

reloading plugin SublimeLinter.commands
reloading plugin SublimeLinter.sublimelinter
reloading plugin SublimeLinter-contrib-eslint.linter
SublimeLinter: eslint linter loaded
plugins loaded
SublimeLinter: debug mode: on
SublimeLinter: temp directory: c:\users\user~1\appdata\local\temp\SublimeLinter3-user

It was working just fine yesterday and today it suddenly isn't working.
Running ESLint manually from the command line works just fine, but running it manually or saving does not return any logs at all in the console.
Even when there is an obvious error/violation, nothing is printed to the console.
So it is a bit similar to #594 except nothing is printed when it is manually ran.
What I have tried so far is to uninstall and reinstall sublimelinter, the contrib for eslint and eslint itself. Nothing seems to work.
Windows 10, ST3 3126

I have this same problem.
Debug output is:
reloading plugin SublimeLinter.sublimelinter
reloading plugin SublimeLinter-contrib-eslint.linter
plugins loaded
SublimeLinter: debug mode: on
SublimeLinter: temp directory: /var/folders/x7/_s_mvrc11hsgxl5_p9cyw8dm0000gn/T/SublimeLinter3-jakelear ```

Running `eslint` in bash works as expected.
`which eslint` in bash returns `/Users/jakelear/.nvm/versions/node/v6.11.2/bin/eslint` which is correctly in my $PATH. Manually running the "Lint this View" option in Sublime does nothing. I too tried uninstalling/reinstalling everything,

MacOS Sierra: 10.12.6

Same problem here.
I have carefully followed the installation & configuration guide and still have no luck to get it working.
Packages/modules I have installed

tslint (globally installed)
SublimeText Linter 3 (installed via package control)
SublimeLinter-contrib-tslint (installed via package control)

SublimeLinter config
{
    "user": {
        "debug": true,
        "delay": 0.25,
        "error_color": "D02000",
        "gutter_theme": "Packages/SublimeLinter/gutter-themes/Default/Default.gutter-theme",
        "gutter_theme_excludes": [],
        "lint_mode": "background",
        "linters": {
            "tslint": {
                "@disable": false,
                "args": [],
                "excludes": []
            }
        },
        "mark_style": "outline",
        "no_column_highlights_line": false,
        "passive_warnings": false,
        "paths": {
            "linux": [],
            "osx": [],
            "windows": [
                "C:\\Users\\davhe1\\AppData\\Roaming\\npm\\tslint.cmd"
            ]
        },
        "python_paths": {
            "linux": [],
            "osx": [],
            "windows": []
        },
        "rc_search_limit": 3,
        "shell_timeout": 10,
        "show_errors_on_save": false,
        "show_marks_in_minimap": true,
        "syntax_map": {
            "html (django)": "html",
            "html (rails)": "html",
            "html 5": "html",
            "javascript (babel)": "javascript",
            "magicpython": "python",
            "php": "html",
            "python django": "python",
            "pythonimproved": "python"
        },
        "tooltip_fontsize": "1rem",
        "tooltip_theme": "Packages/SublimeLinter/tooltip-themes/Default/Default.tooltip-theme",
        "tooltip_theme_excludes": [],
        "tooltips": false,
        "warning_color": "DDB700",
        "wrap_find": true
    }
}

And console shows no errors
SublimeLinter: debug mode: on
SublimeLinter: temp directory: c:\users\davhe1\appdata\local\temp\SublimeLinter3-davhe1
Package Control: Skipping automatic upgrade, last run at 2017-10-13 09:45:04, next run at 2017-10-13 10:45:04 or after
reloading settings Packages/User/SublimeLinter.sublime-settings

System I am using
windows 10
cmder (terminal)
sublimeText Version 3.0, Build 3143

Any updates??

Note, semistandard is working fine but not tslint

Not sure, but could you try changing your path config to point at a director, not the executable itself?

have tried that with no luck either

Any update on this?

@eugene-soxhub this is mostly debugging someone’s particular setup, it doesn’t sound like anything wrong with SL.
@DavidHe1127 you didn’t mention if you’ve installed typescript together with tslint, or if linting works from the command line?

It's not working for me either, on macOS Sierra 10.12.6.
{
    "user": {
        "debug": true,
        "delay": 0.25,
        "error_color": "D02000",
        "gutter_theme": "Packages/SublimeLinter/gutter-themes/Default/Default.gutter-theme",
        "gutter_theme_excludes": [],
        "lint_mode": "manual",
        "linters": {
            "eslint": {
                "@disable": true,
                "args": [],
                "excludes": []
            },
            "tslint": {
                "@disable": false,
                "args": [],
                "config_filename": "tslint.json",
                "excludes": []
            }
        },
        "mark_style": "outline",
        "no_column_highlights_line": false,
        "passive_warnings": false,
        "paths": {
            "linux": [],
            "osx": [
                "/usr/local/bin"
            ],
            "windows": []
        },
        "python_paths": {
            "linux": [],
            "osx": [],
            "windows": []
        },
        "rc_search_limit": 3,
        "shell_timeout": 10,
        "show_errors_on_save": false,
        "show_marks_in_minimap": true,
        "syntax_map": {
            "html (django)": "html",
            "html (rails)": "html",
            "html 5": "html",
            "javascript (babel)": "javascript",
            "magicpython": "python",
            "php": "html",
            "python django": "python",
            "typescript": "javascript"
        },
        "tooltip_fontsize": "1rem",
        "tooltip_theme": "Packages/SublimeLinter/tooltip-themes/Default/Default.tooltip-theme",
        "tooltip_theme_excludes": [],
        "tooltips": true,
        "warning_color": "DDB700",
        "wrap_find": true
    }
}

TypeScript and tslint were installed separately (both withnpm install -g). Checking that they're in the path:
$ which tsc
/usr/local/bin/tsc

$ which tsserver
/usr/local/bin/tsserver

$ which tslint
/usr/local/bin/tslint

Linting does work from command line:
$ tslint -p /path/to/project/web

My tslint.json is in a different directory from my sublime project root (/path/to/project/web/) but it still doesn't seem to work when I open up that directory, either.

@braver Hmm, ok. I'm having a very similar issue, in that SublimeLinter stopped working for me. I can run eslint manually from the command line and it will find errors, but none of those same errors seem to show up in Sublime anymore. I am not seeing any errors in the console that indicate that SublimeLinter has any issues.

@kvcrawford please share any related debug output in the console.

There wasn't any debug output in the console. But I finally figured out the setting that was causing a problem for me:
"syntax_map": {
  "typescript": "javascript"
}

Removed that and it's working correctly now :+1:

@kvcrawford Great to hear that you get it working. I will give it go. Thanks


Use the Ruby directory basename to decide the GEM_HOME

Such that each installed Ruby has its own GEM_HOME, even if RUBY_VERSION
is the same for multiple installed Rubies.
This is particularly important for TruffleRuby, where different releases
with the same RUBY_VERSION might compile C extensions differently, and
each release should have a different GEM_HOME.

This is the better version of https://github.com/postmodern/chruby/pull/410, discussed in that PR starting from https://github.com/postmodern/chruby/pull/410#issuecomment-509155061
I believe this is the right fix for always setting GEM_HOME correctly to a separate directory per Ruby installation.
I added an entry in the changelog along with upgrade notes.
I also updated the README.
Fixes https://github.com/oracle/truffleruby/issues/1723.
@postmodern @havenwood What do you think? Could we merge this?

Tests passing now, I had to adapt one expectation.

Also, if we're going to change chruby's gem home directory schema, perhaps we should move it out of ~/.gem/ entirely so as not to contaminate RubyGems ~/.gem/ and to make cleanup of chruby easier? Maybe ~/.gems/ or even ~/.local/share?

It might be possible to write an ugly migration script to rename chruby's gem dirs based on the #!/path/to/$ruby_dir/bin/ruby of any bin stubs within $gem_dir/bin/.

Added a 1.0.0 milestone and separate branch.

@postmodern Thank you for the great review, I'll take a look at addressing it soon.

Also, if we're going to change chruby's gem home directory schema, perhaps we should move it out of ~/.gem/ entirely so as not to contaminate RubyGems ~/.gem/ and to make cleanup of chruby easier? Maybe ~/.gems/ or even ~/.local/share?

I would keep it under .gem, that directory already exists and it's very easy to find and I find it intuitive.

Added a 1.0.0 milestone and separate branch.

Thanks, should I target this PR to the 1.0.0 branch then?

3. Probably need a safer way of cleaning up chruby gem homes inside ~/.gem/ without deleting gems installed outside of chruby (aka system ruby).

That seems difficult, because gem install --user-install would install to e.g. ~/gem/ruby/2.6.0, i.e., potentially mixing the gems with chruby < 1.0's gems.
Maybe we should just mention to look at directories under ~/.gem and consider removing them to save disk space? For many cases, I'd think rm -rf ~/.gem would be correct though. If one is using chruby then one likely doesn't install gems on the system ruby.

@postmodern I updated the Upgrade Notes with some of the discussion here. Now waiting from your feedback.

Currently the 1.0.0 branch is identical to master. This will be merged into the 1.0.0 branch, so probably no need to rebase it.

The 0.4.0 branch does have the addition of a manpage. If we want to add the manpage in 1.0.0, it would just need updating to reflect these changes.

@postmodern I updated the documentation, I think it's both safe and accurate now.
Could we merge this?
I updated the PR to target the 1.0.0 branch.

@postmodern @havenwood is there anything left to do before merging this?

Finally merged something :stuck_out_tongue:

@postmodern Awesome, thanks! (I reacted with a :tada: before but might as well write it in words).
Any plan as to when to release 1.0.0, and if other changes should make it for 1.0.0?
I'd like a way to solve #422 for 1.0.0.

@postmodern What's your branching model?
Shouldn't this change be on master?
Or should https://github.com/postmodern/chruby/pull/431 target the 1.0.0 branch? But that needs test fixes from master.

@eregon once I get ready to release 1.0.0, I merge the 1.0.0 branch into master and hit release. I need to start doing the release engineering work to get 1.0.0 ready (ChangeLog, README, man pages, homebrew recipe, etc).

OK, should I retarget this PR against the 1.0.0 branch then?
Could you merge master to 1.0.0, or rebase 1.0.0 on top of master? This PR depends on test fixes in master.

@eregon fixes and tests can go into master, and we can always rebase other branches.

I realized, while this works well for releases, it works less nicely for -dev/-head builds which always have the same directory basename.
https://github.com/postmodern/chruby/pull/431 will fix that though.

I realized, while this works well for releases, it works less nicely for -dev/-head builds which always have the same directory basename.
#431 will fix that though.

@postmodern I forgot about this, but the point above seems to make #431 (that is not setting GEM_HOME) the only solution to reliably have a gem home per Ruby build, also when having local Rubies or head Rubies installed (assuming these Rubies are rm -rf before a reinstall, which seems very much recommended for head Rubies).

I just realized, this approach is not good enough for any head Ruby, e.g. ruby-head (while ruby-install doesn't support it, chruby doesn't say anything about head Rubies AFAIK), because the ABI then changes but the name does not if reinstalled.
A workaround is users manually clean the GEM_HOME, but this feels impractical and easy to forget.
There is work in CRuby to actually give a proper ABI version for CRuby dev builds.
So a combination of ruby-name + ABI version (RbConfig::CONFIG["ruby_version"]) would work, or of course simply not setting GEM_HOME: https://github.com/postmodern/chruby/pull/431

If a user is running and updating ruby-head, then it should be the user's responsibility to run gem pristin --extensions to rebuild any extensions that were compiled against a previous ABI. Or, rubygems could better handle edge cases where C extensions were previously built, but against the an older ABI or static vs. dynamic libruby, and print an informative error message.

With https://github.com/ruby/ruby/pull/5474, CRuby would raise LoadError if the ABI doesn't match for dev versions, so that should be helpful and be much clearer than a segfault or so later on.
I understand your point of view, I just don't think people are easily aware they need to both rm -r ruby-head-prefix && rm -r ~/.gem/ruby-head before reinstalling ruby-head (or recompile all extensions as you said instead of second rm -r).
With the current chruby release + CRuby head reporting RUBY_VERSION as the next release (e.g., RUBY_VERSION is 3.2.0 on ruby-master currently), dev builds and the 3.2.0 release when it comes out share the same gem home, so that is rather unfortunate, and CRuby releases will probably still not warn on ABI mismatch for releases.
IMHO it's hard for RubyGems to detect ABI mismatches (and it doesn't currently), that should be the job of the Ruby implementation and e.g. TruffleRuby always checks the ABI matches. RubyGems could try to better separate per ABI version, but the current design when GEM_HOME is set is RubyGems just uses that path and assumes it's correct whether it is or not. Hence the responsibility is moved to whatever sets GEM_HOME as things stand.


Form should not validate hidden form item

[ ] I'm sure this does not appear in the issue list of the repository

Basic Info

Package Name And Version<EMAIL_ADDRESS>Browser: chrome<IP_ADDRESS>

What is expected?
hidden form item skips validation.
Steps to reproduce

set a form item with rule={[{required: true]} to hidden={true}, and leave it empty.
form.validate().

目前是会校验所有处于挂载状态的且设置了 field 、 rules 的 formitem 的


chore(ci): Run Trivy scan fs instead of image for rocm+pytorch image due to resource constraints

Description

Run Trivy scan fs instead of image for rocm+pytorch image due to resource constraints. At least, the daily report and PR will pass and will show the results for the lock file while we don't reduce the image size.
How Has This Been Tested?

Run the updated workflow for the pytorch image and another one to check both behaviors (image and fs)
Merge criteria:

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

I don't like how complicated is the ci script becoming. So many variables. Let's see first if the grouping of run commands can make trivy image scan run?
Maybe there's still something else to shrink the images they can be tried?

TBH I don't like to see a red CI every day. So I'd rather have this in while we progress with the image optimizations.

/lgtm
i'm not happy, but if we want to have passing trivy, this is the way

/override ci/prow/rocm-notebooks-e2e-tests
/override ci/prow/images


 Why? parted tries to interact with the user.
You can run parted, without user intervention:
man parted
       -s, --script
                never prompts for user intervention
--- screenshot 1 -- pishrink with corrupt image
./pishrink2.sh /mnt/usb/corrupt.img /mnt/usb/corrupt-shrink.img
Copying /mnt/usb/corrupt.img to /mnt/usb/corrupt-shrink.img...
Error: Can't have a partition outside the disk!
^C                          <=== interaction, I aborted pishrink with Ctrl-C / Strg-C
--- screenshot 2 -- parted with corrupt image
parted -m /mnt/usb/pishrink/corrupt-shrink.img unit B print
Error: Can't have a partition outside the disk!
Ignore/Cancel? Cancel                               <=== interaction, I entered "Cancel"
BYT;
/mnt/usb/corrupt-shrink.img:4021420032B:file:512:512:unknown::;
--- screenshot 3 -- parted ... with option '-s'
parted -s -m /mnt/ntfs/corrupt-shrink.img unit B print
Error: Can't have a partition outside the disk!
BYT;
/mnt/ntfs/corrupt-shrink.img:4021420032B:file:512:512:unknown::;

This should have gotten fixed in #40. Thanks for reporting the issue!


parametrize the software by an Atom module

encoding is parametrized by this Atom.t type (for example either ph4 or PiEltHA)

not necessary if atom types are strings (even in the ph4 space); lazy but unbeatable productivity solution ...

note that in the ph4 space, we have to ignore atoms which don't have a ph4 feature


Introduce wallpapers.

Redesign app to allow wallpapers.

@volnes, introduced wallpapers.

how to disable this function?

So far you can select black wallpaper in your android settings. But I will add this option into the app.

not needed to add this feature.
I think so)

Not needed to add wallpapers or to add option to have black background
wallpaper?
On Oct 7, 2015 11:32 AM, "volnes"<EMAIL_ADDRESS>wrote:

not needed to add this feature.
I think so)
—
Reply to this email directly or view it on GitHub
https://github.com/vackosar/search-based-launcher/issues/14#issuecomment-146131515
.

add option to have black background
wow...
This feature is needed!
I think u just add function to disable wallpapers ( but if u add option to have black background its would be very good)

Will do that. By default old phones have ugly wallpapers i know. Btw you
can upload a black picture as a wallpaper now or some nicer on some phones.
On Oct 7, 2015 11:42 AM, "volnes"<EMAIL_ADDRESS>wrote:

add option to have black background
wow...
This feature is needed!
I think u just add function to disable wallpapers ( but if u add option to
have black background its would be very good)
—
Reply to this email directly or view it on GitHub
https://github.com/vackosar/search-based-launcher/issues/14#issuecomment-146133970
.

what resolution needed?
i have black wallpaper with resolution 3264x2448 but i use a QuickPic to make lower 480x854.
Maybe try to use #FF000000 or 16777216 (0xff000000) ?

Resolution depends on your phone.
On Oct 7, 2015 12:05 PM, "volnes"<EMAIL_ADDRESS>wrote:

what resolution needed?
i have black wallpaper with resolution 3264x2448 but i use a QuickPic to
make lower 480x854.
Maybe try to use #FF000000 or 16777216 (0xff000000) ?
—
Reply to this email directly or view it on GitHub
https://github.com/vackosar/search-based-launcher/issues/14#issuecomment-146138742
.

well upload? with high res? or what?


Attempt to fix the startup hang with nodes > 32

Fixes #5369

I can't judge this change at all, so if this fixes the hang let's go with it!


Cannot login

When trying to use the application, I get this error:
Error Image
I can login on the website (no problem) - Have tried on two computers, and  have the same issue on Windows and Linux.
All I have done so far, is making an account with the invite I got, and trying to follow to instructions on the website to get started.

we're have a problem with your PGP key, but what else is new :(  It's nearly impossible to keep up with the many ways in which PGP keys are broken, but we'll try to get to it soon.  Unfortunately it's not high priority since it's not affecting many others than you.

That should fair enough. When you say that "PGP keys are broken" - (Just to understand) Is there anything I can do to help out, and resolve the issue? :-)

I have a fix, hopefully can get it in today!!
On Tuesday, July 12, 2016, Steffen Mogensen<EMAIL_ADDRESS>wrote:

That should fair enough. When you say that "PGP keys are broken" - (Just
to understand) Is there anything I can do to help out, and resolve the
issue? :-)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/issues/3403#issuecomment-232019802,
or mute the thread
https://github.com/notifications/unsubscribe/AA05_7Y87UIB7x0mb05yjq9s351rwj2lks5qU31dgaJpZM4JJEqG
.


vtgate/buffer: Move context canceled error to the group of other errors.

BUG=26755052

LGTM

I'm ignoring the test error here because it's not related to my change.


feat: Add option to specify int64 as an Input dtype

Description

Rework Input paradigm to be based on at::ScalarType as opposed to the previous nvinfer1::DataType, allowing a larger representation space of data types

When paired with truncate_long_and_double, insert casts to ensure Torch engines using Int64 tensors receive the correct types, and TensorRT engines operating on those tensors receive downcasted Int32 versions thereof

Add Torch block at the beginning of model graph to prepare types of input tensors for forthcoming engines in sequence

Automatically follow internal tensor types to abstract away the different internal engines used (Torch/TensorRT) from the user

Provide a framework for streamlined addition of other data types, including torch.double as valid input types

Improve error checking to ensure model compilation and behavior is as documented. For example, disallow specification of Long type input if the engine is required to be converted entirely to TRT

Modify compiler to extract inferred data types for each input

Add Python API testing to ensure casts are inserted correctly and run in Torch

Known Limitations:

Specifying dtype=torch.long on an Input in an input_signature is not supported currently and will throw an error before model compilation when used with the Python API
While Torch may output Int64 tensors from the overall model, Torch-TRT currently can only output Int32 tensors for models using TRT, as there is not a mechanism in place for differentiating intermediate blocks from final/beginning blocks in the graph
Torch-TRT will almost definitely alter the data type of the input tensor, in-place, if dtype=torch.long is specified, and the returned result will be of type torch.int32

Note: The scope of this feature is currently limited to partitioning-enabled models (require_full_compilation=False) having truncate_long_and_double=True, since the feature prepends a Torch-executed block to the graph which performs the necessary casts, and so it requires both partitioning and truncation.
Fixes #1546
Addresses most of #1543
Type of change

New feature (non-breaking change which adds functionality)

Checklist:

[ x ] My code follows the style guidelines of this project (You can use the linters)
[ x ] I have performed a self-review of my own code
[ x ] I have commented my code, particularly in hard-to-understand areas and hacks
[ x ] I have made corresponding changes to the documentation
[ x ] I have added tests to verify my fix or my feature
[ x ] New and existing unit tests pass locally with my changes
[ x ] I have added the relevant labels to my PR in so that relevant reviewers are notified

@peri044 is the reviewer for this feature

@mfeliz-cruise Please check the description for more details on the extent of int64 dtype support. This PR should resolve the usecases that we discussed.

Fixes #1543


How to disable Sunday?

In my calendar i don't want to display sunday but the only way is to disable saturday too, or i want to keep saturday. How i can disable sunday only?

We do not currently support such features.
Not planned yet.

hello there,
I would like to take this issue.

I am student, so I have the subject where I have to solve some issue. And this project seems good and I know Javascript good.
So would it be possible to assign to me this issue?
I will work at this issue weekly.


Fixed bug with loading json files using windows filepaths

jsonReferenceLoader#LoadJson fails when loading files in a window's file system.
To reproduce, on a windows machine, use this example from my Github:
file.json
{
	"id":"1",
	"description": "A Description"
}

main.go
package main

import (
	"fmt"
	"log"
	"path/filepath"

	"github.com/xeipuuv/gojsonschema"
)

const schema = `
{
	"type":"object",
	"properties":{
		"id":{
			"type":"string"
		},
		"description":{
			"type":"string"
		}
	}
}
`

func main() {
	file := "file.json"
	canonical, err := filepath.Abs(file)
	if err != nil {
		log.Fatal(err)
	}

	schemaLoader := gojsonschema.NewStringLoader(schema)
	documentLoader := gojsonschema.NewReferenceLoader("file://" + canonical)

	result, err := gojsonschema.Validate(schemaLoader, documentLoader)
	if err != nil {
		log.Fatal(err)
	}

	if result.Valid() {
		fmt.Printf("The document is valid\n")
	} else {
		fmt.Printf("The document is not valid. see errors :\n")
		for _, desc := range result.Errors() {
			fmt.Printf("- %s\n", desc)
		}
	}
}

$ go run main.go
2018/05/16 11:09:34 parse file://C:\Users\danielhouston\go\src\github.com\Daniel-Houston\examples\file.json: invalid character "\\" in host name
exit status 1

The example works fine on Linux, but fails on Windows.
Please let me know if there is anything else you would like from me before you merge it, as I would like to get this fix in ASAP.
Thanks!

The error is not wrong. A ReferenceLoader expects a URI and Windows file paths with backslashes are invalid URIs, while Linux file paths are valid. File URIs on Windows use forward slashes too, so if you'd provided file://C:/Users/danielhouston/go/src/github.com/Daniel-Houston/examples/file.json  by adding a line canonical = filepath.ToSlash(canonical) instead, things work fine.
It is a pretty understandable error as this step isn't necessary on Linux. I understand this PR will fix this issue for some people by hiding it from them, but to me it feels a bit like a hack. We should probably add a few lines to the documentation about windows file URIs. A different approach would be to have a separate FileLoader that works with raw file paths instead of file URIs, so the end user doesn't have to do any conversion.

I'm closing this issue due to inactivity and the fact I'm not going to merge this specific PR.


Populate & Display Base SSM Params in the Management Console UI

POPULATE SSM:
subnets
account ID
venue name
project name
VPC
Also display these params in the MC UI.

unity-cloud-env terraform module for populating base ssm params works


Buttons states (map/table) are changed

The states of the buttons (map/table) over the map are changed.

When you are on map view, the states should be Icon map=Black, Icon table=blue

When you are on a table view the states should be Icon map=blue and Icon table=black

We'll try to give more emphasis to the buttons.
When you are on map view the buttons are:

and when you are on a table view the buttons are:


Microsoft Purview E5/A5/F5?

Hello,
Just to verify, as I cannot find detailed information about: Microsoft Purview E5/A5/F5
Is the license Microsoft Purview E5/A5/F5 correct? Or should it be Microsoft Compliance E5/A5/F5 ?
Thanks for verification.
Lukas

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

ID: d1fa045c-9edd-2d50-8c55-25b5be8ec9c8
Version Independent ID: d1fa045c-9edd-2d50-8c55-25b5be8ec9c8
Content: Turn on app governance in Microsoft Defender for Cloud Apps - Microsoft Defender for Cloud Apps
Content Source: CloudAppSecurityDocs/app-governance-get-started.md
Service: defender-for-cloud-apps
GitHub Login: @batamig
Microsoft Alias: bagol

Hi @getazcloud, thanks for your question! We'll investigate this and get back to you.

Hi @getazcloud, we're planning to update this text to remove specific license names. App governance is available to any organization with a valid Defender for Cloud Apps license.
You can find more details about specific licenses on the Microsoft 365 licensing datasheet.
If you have additional questions about App governance or Defender for Cloud Apps licensing, we suggest you contact your admin or sales representative.
I'm going to close this issue for now, but feel free to continue commenting if you have more feedback for docs.
#please-close


style: update eslint config and resulting source code changes

What is the current behavior? (You can also link to an open issue here)
Currently, the ESLint config contains some things which I think could be improved.
What is the new behavior (if this is a feature change)?
I updated the following things:

removed seemingly useless "ignorePatterns": ["projects/**/*"] config
Since it is consequently ignored throughout formly, disabled @angular-eslint/no-conflicting-lifecycle
added @typescript-eslint/no-unused-vars and updated many occurences of unused imports/vars/args. I enabled the option to bypass this rule by naming vars with a leading underscore
fixed some small additional stuff

Please check if the PR fulfills these requirements

[x] The commit messages follow our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[x] A unit test has been written for this change.
[x] Running npm run build produced a successful build. (Unit testing can be done by running npm test;)
[x] My code has been linted. (npm run lint to do this. npm run build will fail if there are files not linted.)

Please provide a screenshot of this feature before and after your code changes, if applicable.
Other information:

Thank you @MaxKless!


Coordinating edits

What are the @PyAbel/developers working on?
When building the docs, I get a large amount of warnings because many of the docstrings are not quite in the perfect numpy docstring format. I would love to go through an fix all of these, at least to the extent that they do not throw warnings.
But, I fear that this might cause a case of terrible overlapping edits if you are all working on various aspects of the code.
@DhrubajyotiDas, are you heading up the cleanup of basex.py? I think that @rth's effort to make the abel.i/fabel class is, to some extent, waiting for basex.py to be cleaned up.

@DanHickstein Yes, I am cleaning up basex.py. By that I mean

Setting defaults to values for parameters center and n
Changing the name of the main basex.py function from BASEX(...) to iabel_basex_transform(...)

Unless there is something specific within these steps that is important for @rth's work to make the abel/i/fabel class, feel free to go ahead with that.
If I have my git straight, there shouldn't be any edit clashes if we merge PRs in the proper sequence.

@DanHickstein (welcome back!), excellent work on the doc generation.
I have recently changed abel.tools.analytical.sample_image(). The class part of this file has old style comments. The file structure requires an executive decision @PyAbel/developers as to whether sample_image() is implemented as a class method.  In addition, I believe that some of the tests/ functions should be moved to analytical.py e.g. in  test_hansenlaw.py: Curve A:  f(r), g(R). I think, somewhere, @DhrubajyotiDas also has the same function defined.
As for current activity I am:

checking on transform self-consistency, whole image vs quadrant, initially hansenlaw, and then the other methods.
verifying that for even images scipy.ndimage.shift(IM, (-1/2, 1/2)) followed by trimming one row/col IM=IM[:-1, :-1] is sufficient to provide an identical odd image.
improvements to the example codes. I find example_O2_PES_PAD.py cloned from the original example templates to be too long winded and off-putting for a task that is simply: IM=np.loadtxt("file"), AIM = iabel_<method>(IM), speed, radial = calculate_speeds(AIM).
For the simple GUI interface, example_simple_GUI.py, I would like to make it look more like the original basex.exe. I initially opted for buttons since Mac OXS pushed the menuitems to the toolbar, but I have changed my mind on this.
whether the image 2D test is necessary for (f/i)abel_<method>().
longer term, code to circularize an image.

I think that documentation changes should easily merge, so there should be little to be concerned about.

I think, somewhere, @DhrubajyotiDas also has the same function defined.

@stggh, I've coded up that function and others here.

Excellent! These functions should be adapted to live in abel.tools.analytical.py to be available for the unit tests.

It sounds like most of these changes have been made. I will close this issue. Good work team!


Rails 5.1 ActionController::Parameters doesn't have method except

https://github.com/rocketjob/rails_semantic_logger/blob/master/lib/rails_semantic_logger/extensions/action_controller/log_subscriber.rb#L14 needs to change.

Awesome, thank you for finding, reporting and fixing this issue for us :tada:


Sass::Syntax error at @import "refills/flashes"

Unable to import 'refills/flashes' when running rspec
ActionView::Template::Error:
   File to import not found or unreadable: refills/flashes.
   Load paths:
     /Users/ryanwaits/.rvm/gems/ruby-2.3.0/gems/babel-source-5.8.35/lib
     /Users/ryanwaits/Code/projects/paste_bin/app/assets/images
     /Users/ryanwaits/Code/projects/paste_bin/app/assets/javascripts
     /Users/ryanwaits/Code/projects/paste_bin/app/assets/stylesheets
     /Users/ryanwaits/Code/projects/paste_bin/vendor/assets/javascripts
     /Users/ryanwaits/Code/projects/paste_bin/vendor/assets/stylesheets
     /Users/ryanwaits/.rvm/gems/ruby-2.3.0/gems/normalize-rails-3.0.3/vendor/assets/stylesheets
     /Users/ryanwaits/.rvm/gems/ruby-2.3.0/gems/neat-1.7.4/app/assets/stylesheets
     /Users/ryanwaits/.rvm/gems/ruby-2.3.0/gems/jquery-rails-4.1.1/vendor/assets/javascripts
     /Users/ryanwaits/.rvm/gems/ruby-2.3.0/gems/bourbon-5.0.0.beta.5/core
 # ./app/assets/stylesheets/application.scss:9

# --- Caused by: ---
 # Sass::SyntaxError:

Related to #476

Closing as duplicate of https://github.com/thoughtbot/suspenders/issues/779. Thanks for your report!


App crashes with this plugin added

My app crashes as soon as I call navigator.app.loadUrl(). I haven't enabled backgroun mode yet and use this plugin for unlock and wakeup. I'm using the master branch.
I've tried this in Android 5.x and 7.x.
Could there be a workaround?

Are you sure the app crash is caused by this plugin?

Based on my testing on at least 2 devices with different versions, navigator.app.loadUrl() triggers the crash only when this plugin is added to Cordova project (background mode was disabled).

background mode was disabled

Does it mean you didn't call any functions in this plugin? All you did was just cordova plugin add cordova-plugin-background-mode, but the app crashes despite not modifying the project files?

I'm seeing a similar problem, though it seems to be limited to very specific Android phones. Can reproduce it repeatedly on said phones while using Android 8.0 and 9.0
We don't use navigator.app.loadUrl() so at least in our case it's unrelated.
The app loads, shows some permission requests and crashes immediately - if I remove the plugin it works fine.
One thing I've noticed while trying to debug is that when I run the build from Android Studio (not via Cordova) I don't see any crashes. I'm still trying to investigate the root cause, I've not been able to get any debug data off the app so far.

Seems to be related to his https://github.com/katzer/cordova-plugin-background-mode/issues/393 (at least for me). There's a pending pull req, not sure where it stands but this is going to break for everyone in the next few weeks / months as updates to v9 starts to roll out
https://github.com/katzer/cordova-plugin-background-mode/pull/389


Avalonia AOT

Avalonia and AOT work well together for small self containing app with a better startup time
MR available https://github.com/xM4ddy/OFGB/pull/7

I'm going to go ahead and say there is a fair chance I don't use this but I will look into it so thanks!


Item collection is slow

Currently, item collection is very slow. It's possible we could speed this up by compiling the items into a separate file at start as well as the inventory.

Fixed in https://github.com/mscroggs/AVE/commit/7be1d03d5c4578e74bab5c1a6f63964888076037
Now startup is very slow. Probably want to have a loading screen between titles and start?


httpjson plugin should allow JSON to add tags

The httpjson plugin should have a way for the data emitter/end-point to specify tags to add to each key/value pair. This would make it possible to make "InfluxDB-aware" (telegraf-aware, I guess to be exact) applications and just use this plugin, rather than having to make a specific plugin for each application.

that sounds like a good idea :+1:

Closing this in favor of https://github.com/influxdb/telegraf/issues/277, @abh let me know what you think of what I proposed in that case


Allow overwrite the builtin Postgres DB password

The default behavior of the codecentric Helm Chart does set a
predefined password, which is insecure.
Checklist

[x] Keep pull requests small so they can be easily reviewed.
[x] Update the documentation.
[ ] Categorize the PR by setting a good title and adding one of the labels:
bug, enhancement, documentation, change, breaking, dependency
as they show up in the changelog
[ ] Link this PR to related issues.

Will be resolved via #13.


Fix spurious pytest warning

This patches fixes the infamous, long-standing warning from the test suite:
Modules are already imported so can not be re-written: testinfra

It turns out that the testinfra binary is redundant, and that you should just invoke pytest, which will do everything needed to run Testinfra tests anyway.

Thanks for nailing that one!


Suggestion: why not have theme related plugin settings inside of theme folder?

I believe it would make sense to have plugin setting files in the theme folder. For example a lot of plugins have their css files included by default and if my theme provides styles for, lets say, pagination I need to create plugin config file in, probably (differs by plugins, also annoying), user/config/plugins/ folder.
The issue is if I have few themes and I want to swap them on occasion, I need to modify those config files. Wouldn't it make sense to have theme related settings in theme folder. In addition it would be easier to install new themes without having to add extra settings.
Also, plugins, should have standardized rules on where, how to use config files and template file overrides: some plugins have config files directly in  user/config/ some in user/config/plugins/; template files sometimes are located directly in templates/ folder while sometimes in 'templates/partials/`.
This is just a suggestion.

i'll have a think about this.  Thanks!

Regarding the location of things I can definitely clarify that a little.
All plugins can have a configuration file called pluginname.yaml in the root of the plugin.  E.g. user/plugins/pluginname/pluginname.yaml
There is only one location supported for this.  You override the plugin configuration by putting a similar file in your user/config/plugins/ folder, e.g. user/config/plugins/pluginname.yaml.
That is consistent for all plugins and will "just work".  However, In Grav YAML is converted into a PHP array, so you could theoretically have a user/config/plugins.yaml file that contains configuration for all plugins as long as in that file you have format like this:
pluginname:
  enabled: true

anotherplugin:
  someoption: false

This is because both methods effectively create a php array of the same format. However, for simplicity I always advocate the first method of having a folder called plugins and putting individual plugin configuration files in there.
Regarding Twig templates, every theme has a templates/ folder that is the location of the Twig templates.  Plugins can also have a similar templates/ folder although the naming is not as critical there as actually register this location in your plugin.  The important thing is that there is really only one main folder level that you register with Twig.
Page files have a template associated with them, and those are are requested from the Twig setup simply as default.html.twig (for example).  These would then have to sit at the top level to be found.
As a naming convention, top level templates that render a page, should be at this top level.  Parts that are used to render one of these top level pages, should be put in templates/partials/.  But there is nothing hardcoded to say this is the folder to use, the theme's templates just load partials/somepartial.html.twig and so they are looked for in the partials sub directory.
Most plugins have partials because they are Twig bits of a greater page.  Although some plugins such as feed has top level Twig templates because they are actually used to render the entire page as an XML RSS feed.
Hope that sheds some light on those parts :)

This makes sense. Thanks for clarification, tho I would love to bundle theme with plugin settings.

I'm still thinking about that part :)

Ok, so i've thought about this and here are my thoughts:
While it could be possible to add support to look in the theme for a plugins.yaml file that was then merged with the plugin configuration, I think this could lead to more problems than it resolves.  There could be unpredictable results for the user where plugins all of a sudden change their behavior without any clear indication of how or why this is happening.  Also it could change a a configuration setting that the user explicitly set for the plugin.  It just opens up a can of worms that could potentially lead to more errors.
The better solution is to create a skeleton package that contains sample pages for the theme and configuration for the site, plugins, etc.  We do this already for a variety of our themes for this very reason.  It provides a ready-to-run package for the user.
Usually skeleton repos contain the basics of the user/ folder, without the actual plugins nor the theme.  It has a .dependencies file that contains references to the Git repos where these can be obtained.  This allows you to download the skeleton and insert it as the user/ folder, then run bin/grav install to obtain the dependencies.  The resulting site should 'just run'.
The release package should be the entire site include Grav etc.  You can see some of our skeleton packages for reference.


fix mxnet warning in timeseries

Issue #, if available:
Description of changes:
Right now after install time series errors with no module found: mxnet. This fixes it back to fail more gracefully.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-1888-1 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1888/1/index.html

Job PR-1888-2 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1888/2/index.html


add generalized SBP approximation type

Todo: figure out how to add a GSBP approximation type (primarily for use in Trixi.jl). The issue is that GSBP operators are nodal SBP approximations, but the nodes lie in the interior. Switching to this representation would be inconvenient for curving meshes, since curving only interior nodes may result in non-conforming face node distributions.
Another option is to just leave the definition of a GSBP approximation type to Trixi, where the GSBP operators can just be defined within create_cache.

Will leave the definition of GSBP type to Trixi.


adding kitops

Adding information on KitOps, the fastest growing open source AI project packaging and versioning tool.

Is this list being actively maintained?


Added a MERN Stack blogging app with robust implementations of user auth., user-specific blogs, creation, editing, and deletion of blogs, and user profile updates.

Artfully designed and meticulously engineered a captivating MERN Stack blog application that offers a seamless and engaging user experience. This feature-rich platform boasts elegant user authentication, enabling users to create, customize, and curate their profiles. The heart of the application lies in its effortless blog management, where users can compose, edit, and delete their thoughts with ease. With this immersive and intuitive canvas, every interaction becomes a moment of inspiration, fostering a vibrant community of idea-sharing. 🚀

Sure .


Implement more detailed memory statistics

Add more detailed statistics, such as cache transitions, map/unmap calls and number of used spans.

Additional statistics for cache transitions and map/unmap calls added


{% endblock %} is parsed when inside {# comment #} block

While I am developing a template, I sometimes need to comment out some code to try it another way.  With the dev version of Jinja2, if the commented out section contains an {% endblock %} command, then rendering the template generates an error:
... <<<--- snip -->>>
File "/home/rgibson/src/mymoney/mymoney/templates/root.html", line 20, in
{% extends "layout.html" %}
File "/home/rgibson/src/mymoney/env/lib/python3.3/site-packages/Jinja2-2.8_devdev_20131021-py3.3.egg/jinja2/environment.py", line 742, in handle_exception
reraise(exc_type, exc_value, tb)
File "/home/rgibson/src/mymoney/env/lib/python3.3/site-packages/Jinja2-2.8_devdev_20131021-py3.3.egg/jinja2/_compat.py", line 36, in reraise
raise value.with_traceback(tb)
File "/home/rgibson/src/mymoney/mymoney/templates/layout.html", line 30, in
{% endblock %}
File "/home/rgibson/src/mymoney/env/lib/python3.3/site-packages/Jinja2-2.8_devdev_20131021-py3.3.egg/jinja2/environment.py", line 459, in _parse
return Parser(self, source, name, encode_filename(filename)).parse()
File "/home/rgibson/src/mymoney/env/lib/python3.3/site-packages/Jinja2-2.8_devdev_20131021-py3.3.egg/jinja2/parser.py", line 893, in parse
result = nodes.Template(self.subparse(), lineno=1)
File "/home/rgibson/src/mymoney/env/lib/python3.3/site-packages/Jinja2-2.8_devdev_20131021-py3.3.egg/jinja2/parser.py", line 875, in subparse
rv = self.parse_statement()
File "/home/rgibson/src/mymoney/env/lib/python3.3/site-packages/Jinja2-2.8_devdev_20131021-py3.3.egg/jinja2/parser.py", line 136, in parse_statement
self.fail_unknown_tag(token.value, token.lineno)
File "/home/rgibson/src/mymoney/env/lib/python3.3/site-packages/Jinja2-2.8_devdev_20131021-py3.3.egg/jinja2/parser.py", line 89, in fail_unknown_tag
return self._fail_ut_eof(name, self._end_token_stack, lineno)
File "/home/rgibson/src/mymoney/env/lib/python3.3/site-packages/Jinja2-2.8_devdev_20131021-py3.3.egg/jinja2/parser.py", line 82, in _fail_ut_eof
self.fail(' '.join(message), lineno)
File "/home/rgibson/src/mymoney/env/lib/python3.3/site-packages/Jinja2-2.8_devdev_20131021-py3.3.egg/jinja2/parser.py", line 51, in fail
raise exc(msg, lineno, self.name, self.filename)
jinja2.exceptions.TemplateSyntaxError: Encountered unknown tag 'endblock'.
To recreate, extend a template, and in the extended template add a block comment that includes a {% endblock %}.  (I didn't try it with direct template)

I dunno if this is still relevant or not, so it should just be closed or marked unfixable/can't recreate.

Yes, it is still relevant!
The failing template for me is a child template as well.
I'm attaching a copy of the problematic one.
incident_report.txt
The error message I get ends this way:
"templates/incident_report.html", line 407, in template
{% endfor %}
TemplateSyntaxError: Encountered unknown tag 'endfor'. Jinja was looking for the following tags: 'elif' or 'else' or 'endif'. The innermost block that needs to be closed is 'if'."
Hope that helps.
Cheers.

Could you please provide an SSCCE that shows the error?

This is odd. When I prepared a very simplified version for you it works fine. :-/
Anyway, this is the idea:
`
{% extends "test_base.txt" %}
{% block main %}
{% set a_test = {'my_key': 'just testing'} %}
{% if  a_test %}
{% set sorted = a_test | dictsort %}
{{ sorted | safe }}
                    {#

                    {% for i in a_test %}
		    {{ i }}
                    {% endfor %}

#}
{% endif %}
{% endblock main %}
`
In the original template, it complains about that 'endfor' tag.
I guess it can be reproduced, indeed :-(
Thanks anyway for your time! :-)

I found the problem!
There was another block commented out within the problem block:
{#
{% for i in a_test %}
    {#
     #}
{% endfor %}
#}
My bad. Sorry about that!
Thanks for your time though!

Yeah, this might seem like a bug, but since we don't do any parsing within comment blocks we also can't balance opening/closing braces.


Fix #882 add noonpacific

#882

Just wanted to note that although it looks like artist and song are swapped in this commit, they are swapped in the noonpacific.com source, so this commit is correct.

Closed in favor of #1186.


Fix: merge conflicts in pRU

This PR fixes the merge conflicts in #869

isn't quite right approach... close.

Maybe I'll consider using cherry-pick to avoid lots of commits in history.

@yo1995 It looks like you'll need to update from v.next again. There are now seven files in conflict:

It looks like you'll need to update from v.next again. There are now seven files in conflict:

I've fixed these conflicts.
Also get a better idea about how git works! In the future I'll make improvements to my commit messages.


Network restarting with openssl error

Problem/Motivation

A few days ago all of my zwave devices became unresponsive, trying to access the webUI failed so I went into supervisor and can see it looks like it crashing and restarting.

Expected behavior
Have access to the Z-Wave JS to MQTT Web UI
Actual behavior
My logs are getting flooded with
2021-12-04 13:27:19.300 WARN STORE: scenes.json not found
2021-12-04 13:27:19.307 INFO APP: HTTPS is enabled. Loading cert and keys
2021-12-04 13:27:19.308 INFO APP: Cert and key not found in store, generating fresh new ones...
Error: Could not find openssl on your system on this path: openssl
at /opt/node_modules/pem/lib/openssl.js:237:23
[13:27:19] INFO: Starting the Z-Wave JS to MQTT...
[13:27:19] TRACE: bashio::net.wait_for 3000 localhost 1800
Steps to reproduce
I dont actually know. Prior to seeing this issue my last update of the zwavejs2mqtt was a couple of weeks ago. Sorry if this is a vague question but I am a little unsure where to look to try troubleshoot this myself

I also experience this issue after the recent 0.31.1 update that was published yesterday. I had initially setup zwavejs2mqtt the day prior without issue, once the autoupdate finished, I am receiving the same issue and it seems to be suck in a constant loop. Opening the Z-Wave JS side bar results in a 502 error both with the local and remote Home Assistant paths.
In my Supervisor system logs, I also see the following which is also stuck in a loop.
21-12-04 14:16:48 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host <IP_ADDRESS>:8099 ssl:default [Connect call failed ('<IP_ADDRESS>', 8099)]
21-12-04 14:17:53 WARNING (MainThread) [supervisor.misc.tasks] Watchdog missing application response from a0d7b954_zwavejs2mqtt
21-12-04 14:19:53 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with a0d7b954_zwavejs2mqtt application!
21-12-04 14:19:53 INFO (SyncWorker_1) [supervisor.docker.interface] Stopping addon_a0d7b954_zwavejs2mqtt application
21-12-04 14:19:58 INFO (SyncWorker_1) [supervisor.docker.interface] Cleaning addon_a0d7b954_zwavejs2mqtt application
21-12-04 14:19:59 INFO (SyncWorker_5) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/zwavejs2mqtt/amd64 with version 0.31.1

I've attempted restarting the host, core, and supervisor with no luck.

I've dug into it a little more and was able to find the following info
When running an interactive shell with the add-on docker container, the following errors are dumped to the console

After this, it goes into a loop of attempting to connect and then retrying connection again in 3 seconds. Also, the proxy_pass_header error.
While looking at the proxy_pass_header, the following is the contents of the /etc/nginx/servers/ingress.conf file

Not sure if that needs to be explicitly set here for this add-on or not.
After commenting out the proxy_pass_header in the ingress.conf file, the nginx emerg errors disappear and only the ZWAVE errors exist

In the first screenshot, it mentions Controller status: Driver: "path" is not defined: and looking online it seems that other users have mentioned that it may be related to the path of the zwave USB and the driver not finding it. Everything seems to be okay, and the USB is mounted and can be found inside HASSIO. From here, it looks like it kicks off the endless loop of attempting to connect and failing.

I also see the following when viewing the Z-Wave JS integration configuration

Hopefully that helps narrow down the issue a little more. If there's anything else I can grab, feel free to let me know!

I ended up just uninstalling the addon and reinstalling. A real shame as the addon is working again however I have lost all the names from the addon and home assistant

My apologies for the late response. When I was trying to replicate the issue in a dev instance of HA and accidentally ended up nuking my main HA instance. Thankfully, I was just starting out, so it was easy to get everything back.
After setting everything up again, zwavejs2mqtt is working without an issue and I'm no longer experiencing this issue.

I have this exact issue today.  Can't figure out what to do!

same issue i reproduce by starting a fresh install, in settings under general i enable https. restart container and it will go into an unending loop.
resolution for now is to uninstall and then reinstall. this does prevent me from using some features of smart start if i cannot use https

I had this same issue and was able to restore from a backup to before I set the HTTPS option in the settings.   I enabled HTTPS so I could scan QR for SmartStart and that update broke this.  I have had zero problems since with HTTPS being unchecked, but I can not use SmartStart Scan feature.

this happened to me as well, you can ssh into your hass instance, then find the container as it's looped with docker ps, then you can use "docker exec -it container_id bash" and get into the container, then "vi /data/store/settings.json" then search for http and change true to false, save, restart, and your back...  it should be moved to the add-on configuration page and then allowed to specify where to load the pem files

Im also running into this issue.  Looks like the haos does not ship with openssl, so this issue exists when attempting to enable https?

So, compared to the zwavejs2mqtt repo's dockerfile, I don't see that this one is adding openssl anywhere.
https://github.com/zwave-js/zwavejs2mqtt/blob/master/docker/Dockerfile#L52
versus
https://github.com/hassio-addons/addon-zwavejs2mqtt/blob/main/zwavejs2mqtt/Dockerfile#L20-L24
Is there a reason that change never made it to the add-on based image?

I just got this EXACT same issue after doing a update today. I did try to enable SSL like a month ago but was given a warning and disabled it. I've restarted many time since then and am curious why it would now enable SSL after updating? I am running a virtual box vm and cannot access the settings.json file as described by dkmcgowan can some please advise me on opening it?

this happened to me as well, you can ssh into your hass instance, then find the container as it's looped with docker ps, then you can use "docker exec -it container_id bash" and get into the container, then "vi /data/store/settings.json" then search for http and change true to false, save, restart, and your back... it should be moved to the add-on configuration page and then allowed to specify where to load the pem files

This just happened to me after a update today. What’s the easiest way to get the container ID on a virtual box VM running on a Windows 10 pc? I have physical access and also SSH. All the commands I’ve tried don’t work.

I am seeing this same issue after the most current core and OS update. I am trying to set it back to HTTP to at least get back to the screen and can't see to find the proper way to actually get into the docker its running in.
I am also running this as a VM on a windows 10 machine

After hours of messing with this I was able to get it back up using the following steps.
[dkmcgowan] gave most of the steps but there was a few more (https://github.com/dkmcgowan)https://github.com/hassio-addons/addon-zwavejs2mqtt/issues/309#issuecomment-1051342300
I was running a virtualbox vm and didn't have host ssh access until I install the SSH & Web Terminal addon and disabled protected mode. Then I had full access to the docker and could get the container ID and edit settings.json
I was able to get into the zwavejs2mqtt web ui now but it was completely blank because it couldn't connect to my zstick7. After verifying the settings what finally worked was actually restarting the host computer not just the VM. Then everything was back up and running.

this happened to me as well, you can ssh into your hass instance, then find the container as it's looped with docker ps, then you can use "docker exec -it container_id bash" and get into the container, then "vi /data/store/settings.json" then search for http and change true to false, save, restart, and your back... it should be moved to the add-on configuration page and then allowed to specify where to load the pem files

Hi dkmcgowan, could you please help me with this? I have Home Assistant installed as a docker container on a Synology NAS, with zwavejsmqtt in another container. I stupidly enabled SSL and now can't get into zwavejs2mqtt. How do I manually revert that config? I have a environment variable in my docker-compose ZWAVEJS_EXTERNAL_CONFIG=/usr/src/app/store/.config-db but that was just a copy-paste from an online guide so I have no idea where it actually exists.

This is still a problem, why is this closed?

This needs to be reopened. It is still a problem.


Update messages

是用ERROR: please open Brevent to make a new brevent.sh还是ERROR: please open Brevent to create a new brevent.sh呢

已完成所要求的更改。

@samforo please refer commit cf3bed2 to continue your translation.

Hi, this weekend I'm going to finish the pending translations. If I have time today, I'll get on with it.
A greeting

All changes have been made. You can merge this pull request.
Thanks


Add dynamic channel expansion.

Hello. I have been looking at the current implementation and I have found that it uses .repeat() on CPU.
However, I would like to propose using .expand() inside the ssim() function. This has several  advantages.
First, this will significantly reduce the amount of data passing from CPU to GPU, which is a major bottleneck in CUDA programming. .repeat() copies data. .expand() does not copy data. So there is not much overhead in using .expand() after transferring the kernel to GPU.
Second, this will allow one to remove the 'channel' parameter from SSIM(), which will remove an unnecessary parameter.

@veritas9872 Thanks for your advice. I think so too, I just tested the expand operation, but found that performance has decreased. It seems that pytorch jit is not working as we think. This is the modified branch. The time statistics below have been updated.
https://github.com/One-sixth/ms_ssim_pytorch/tree/flexible_multi_channel

@One-sixth Hello. Thank you for the information on performance. I am glad to know this.
As for the small increase in time, I think that expanding the kernel in ssim() and ms_ssim() functions might reduce the overhead somewhat. The current implementation has the .expand() inside gaussian_kernel(), which is used several times in each function.

I have modified the code and update branch, but the strange thing is that the time spent does not seem to change. The pytorch jit optimization may be weird. Pytorch jit may have considered this situation and optimized it.
ssim
old
Performance Testing SSIM

testing losser2
cuda time 88984.921875
perf_counter time 86.7958464

testing losser3
cuda time 36126.84375
perf_counter time 36.0654904

testing losser4
cuda time 34692.1953125
perf_counter time 33.896039900000005

new
Performance Testing SSIM

testing losser2
cuda time 88994.9140625
perf_counter time 86.8065547

testing losser3
cuda time 36120.90625
perf_counter time 36.0597451

testing losser4
cuda time 35769.17578125
perf_counter time 35.1033664

@One-sixth Does the new implementation use dynamic value scaling by any chance?
I implemented the value range to be the range of values for the target if the value range was not specified.

@veritas9872 No, not in my implementation. I think users should set these values manually instead of using automatic.

I sorted out the code. The new dynamic channel version is available at https://github.com/One-sixth/ms_ssim_pytorch/tree/dynamic_channel_num .

@One-sixth Thanks for the update!
I have one more question. Do both versions use the 'compensation' variable?
Transferring data from CPU to GPU is actually a very expensive operation and I think that this might be the cause of the difference in speed.

@veritas9872 Sorry. I don't really understand the meaning of "compensation". My English is not good.
Transferring data from the CPU to the GPU is of course a very expensive operation. But through
Mod = SSIM()
Mod = mod.cuda()

All parameters will be moved to the GPU. you can run this
print(mod.window.device)

to found the variable is in the gpu. Because of the use of ScriptModule, all python variables such as self.data_range will become jit constants and merge in jit script. I think my code should be without CPU to GPU performance loss.

@One-sixth I was referring to the variable compensation = 1.0 in ssim.py.
However, I checked and both versions have the variable.

@veritas9872 I don't know... You need to ask @VainF.

The variable comes from ssim of Tensorflow


condense all silent trajs that are next to one another

simple clean up function to do upon save / load.
prevent it from even happening in the first place: when deleting trajs I believe. (Perhaps they are being created somewhere else)

Maybe this bandaid solution could be improved by having an action occur on the particular phrase with every added trajectory?


Alphabetize kernel headers to be installed, include some missing required ones for plugins

fixes https://github.com/chipsalliance/synlig/pull/1972 https://github.com/dau-dev/tools/issues/6

It's worthwhile to point out the headers being added, these seem to be:
6a7
> $(eval $(call add_include_file,kernel/cost.h))
8a10,11
> $(eval $(call add_include_file,kernel/ffmerge.h))
> $(eval $(call add_include_file,kernel/fmt.h))
20a24
> $(eval $(call add_include_file,kernel/timinginfo.h))

Ideally the change to sort the headers and to add new ones would be split. FWIW with the change the order is not fully alphabetical either (e.g. kernel/modtools.h above kernel/mem.h).

I'm happy to alphabetize the remaining, let me know! Given that these headers were omitted by mistake, and should have been added here when the files themselves were added, I don't think there's a ton of value in separate commits (e.g. the git blame is already separated from the original commit)

Thanks! I think we will merge this as-is (dev call where PRs are discussed is in two hours). I see the value in separate commits in easier review and making it obvious what the user-facing changes are (which comes down to the diff I extracted above).


fix(plugin-package-json): add bugs url

This PR adds a bugs URL to the plugin's package.json
Checklist
Please add a x inside each checkbox:

[x] I have read the contribution guidelines.
[x] I have added tests (we are enforcing 100% test coverage).
[x] I have added documentation in the README.md, the docs directory (if
any) and the examples directory (if any).
[x] The status checks are successful (continuous integration). Those can be
seen below.

CI failure seems unrelated


Document how to initally set up server with Rancher API

This issue represents a small piece of the work in https://github.com/rancher/rancher-docs/issues/173

Duplicate of #170


Improve Documentation in DG

Codecov Report

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

@@            Coverage Diff            @@
##             master     #252   +/-   ##
=========================================
  Coverage     53.10%   53.10%
  Complexity      620      620
=========================================
  Files           133      133
  Lines          2757     2757
  Branches        334      334
=========================================
  Hits           1464     1464
  Misses         1150     1150
  Partials        143      143

Continue to review full report at Codecov.

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


Field 'mergeQueueEntry' doesn't exist on type 'PullRequest' GraphQL error: No such type MergeQueueEntry, so it can't be a fragment condition

I'm getting the error when I press "Create" in PR create "wizard" since v0.82.0:
Field 'mergeQueueEntry' doesn't exist on type 'PullRequest' GraphQL error: No such type MergeQueueEntry, so it can't be a fragment condition

v0.80.1 of plugin is working fine

Extension version: v0.82.0
VSCode Version: 1.87.0
OS: Ubuntu 22.04
Repository Clone Configuration (single repository/fork of an upstream repository): single
Github Product (Github.com/Github Enterprise version x.x.x): GHE 3.7.4

Steps to Reproduce:

push a new branch with some changes
try to create a new PR

same issue here
2024-03-06 08:07:08.537 [error] GitHubRepository> Fetching all pull requests failed: Error: GraphQL error: Field 'mergeQueueEntry' doesn't exist on type 'PullRequest'
GraphQL error: No such type MergeQueueEntry, so it can't be a fragment condition
2024-03-06 08:07:08.538 [error] GitHubRepository> Error querying GraphQL API: GraphQL error: Field 'mergeQueueEntry' doesn't exist on type 'PullRequest'
GraphQL error: No such type MergeQueueEntry, so it can't be a fragment condition
2024-03-06 08:07:08.539 [error] GitHubRepository> Error querying GraphQL API: GraphQL error: Field 'mergeQueueEntry' doesn't exist on type 'PullRequest'
GraphQL error: No such type MergeQueueEntry, so it can't be a fragment condition
2024-03-06 08:07:08.539 [error] GitHubRepository> Fetching all pull requests failed: Error: GraphQL error: Field 'mergeQueueEntry' doesn't exist on type 'PullRequest'
GraphQL error: No such type MergeQueueEntry, so it can't be a fragment condition
2024-03-06 08:07:09.830 [info] FolderRepositoryManager+0> Found GitHub pr repo for pr #1030: yes

Same issue with vscode 1.87.1

I had the same issue Extension version: v0.82.0
I workaround it by rolling back to previous version v0.80.1

Folks who see this: I think your enterprise instance is returning an error that the extension isn't handling properly. I've added logging in the latest pre-release version of the extension. If you could install the pre-release version of the extension then share the output of "GitHub Pull Request" once you see the issue again then I'll know what error I need to look for.

v0.83.2024030509 (pre-release)
2024-04-02 16:08:49.655 [error] GitHubRepository> Fetching pull request templates failed: TypeError: Cannot read properties of null (reading 'repository')
2024-04-02 16:08:49.683 [error] GitHubRepository> Fetching pull request templates failed: TypeError: Cannot read properties of null (reading 'repository')
2024-04-02 16:08:49.776 [error] GitHubRepository> Error querying GraphQL API: GraphQL error: Field 'mergeQueue' doesn't exist on type 'Repository'
GraphQL error: Variable $branch is declared by MergeQueueForBranch but not used
2024-04-02 16:08:49.776 [error] GitHubRepository> Fetching branch has merge queue failed: Error: GraphQL error: Field 'mergeQueue' doesn't exist on type 'Repository'
GraphQL error: Variable $branch is declared by MergeQueueForBranch but not used
2024-04-02 16:08:49.817 [info] CreatePullRequestViewProvider> Initializing "create" view: {"defaultBaseRemote":{"owner":"tag","repositoryName":"tag.terraform"},"defaultBaseBranch":"master","defaultCompareRemote":{"owner":"tag","repositoryName":"tag.terraform"},"defaultCompareBranch":"TAG-1586","defaultTitle":"Get code directly from GHE","defaultDescription":"","defaultMergeMethod":"merge","baseHasMergeQueue":false,"remoteCount":2,"allowAutoMerge":false,"mergeMethodsAvailability":{"merge":true,"squash":true,"rebase":true},"autoMergeDefault":false,"createError":"","labels":[],"isDraftDefault":false,"isDarkTheme":true,"generateTitleAndDescriptionTitle":"Generate with Copilot","creating":false,"initializeWithGeneratedTitleAndDescription":false}
2024-04-02 16:09:06.684 [error] GitHubRepository> Unable to create PR: Error: GraphQL error: Field 'mergeQueueEntry' doesn't exist on type 'PullRequest'
GraphQL error: No such type MergeQueueEntry, so it can't be a fragment condition
2024-04-02 16:09:06.684 [error] FolderRepositoryManager+0> Creating pull requests failed: Error: GraphQL error: Field 'mergeQueueEntry' doesn't exist on type 'PullRequest'
GraphQL error: No such type MergeQueueEntry, so it can't be a fragment condition

@DenisBY thanks for the logs, but it looks like you're on a version of the pre-release extension that's nearly a month old. Can you update to the latest? You'll need to use VS Code insiders to get the latest version.

@DenisBY thanks for the logs, but it looks like you're on a version of the pre-release extension that's nearly a month old. Can you update to the latest? You'll need to use VS Code insiders to get the latest version.

v0.85.2024032704 (pre-release)
2024-04-02 17:06:18.820 [error] GitHubRepository> Fetching pull request templates failed: TypeError: Cannot read properties of null (reading 'repository')
2024-04-02 17:06:18.835 [error] GitHubRepository> Fetching pull request templates failed: TypeError: Cannot read properties of null (reading 'repository')
2024-04-02 17:06:18.940 [error] GitHubRepository> Error querying GraphQL API: GraphQL error: Field 'mergeQueue' doesn't exist on type 'Repository'
GraphQL error: Variable $branch is declared by MergeQueueForBranch but not used. undefinedField,variableNotUsed
2024-04-02 17:06:18.941 [error] GitHubRepository> Fetching branch has merge queue failed: Error: GraphQL error: Field 'mergeQueue' doesn't exist on type 'Repository'
GraphQL error: Variable $branch is declared by MergeQueueForBranch but not used
2024-04-02 17:06:18.955 [info] CreatePullRequestViewProvider> Initializing "create" view: {"defaultBaseRemote":{"owner":"tag","repositoryName":"tag.terraform"},"defaultBaseBranch":"master","defaultCompareRemote":{"owner":"tag","repositoryName":"tag.terraform"},"defaultCompareBranch":"TAG-1586","defaultTitle":"Get code directly from GHE","defaultDescription":"","defaultMergeMethod":"merge","baseHasMergeQueue":false,"remoteCount":2,"allowAutoMerge":false,"mergeMethodsAvailability":{"merge":true,"squash":true,"rebase":true},"autoMergeDefault":false,"createError":"","labels":[],"isDraftDefault":false,"isDarkTheme":true,"creating":false,"initializeWithGeneratedTitleAndDescription":false}
2024-04-02 17:06:36.292 [error] GitHubRepository> Unable to create PR: Error: GraphQL error: Field 'mergeQueueEntry' doesn't exist on type 'PullRequest'
GraphQL error: No such type MergeQueueEntry, so it can't be a fragment condition
2024-04-02 17:06:36.293 [error] FolderRepositoryManager+0> Creating pull requests failed: Error: GraphQL error: Field 'mergeQueueEntry' doesn't exist on type 'PullRequest'
GraphQL error: No such type MergeQueueEntry, so it can't be a fragment condition

Thanks @DenisBY for trying it out so quickly! We're getting ready to release soon, so I can't publish a new pre-release version with the fix, but I think I see what the problem is. If you're willing, here's an unpublished pre-release version of the extension to try out. You can rename to .vsix instead of .zip and install in VS Code with the command "Extensions: Install from VSIX...".
GitHub.vscode-pull-request-github.0.85.2024040310.zip
Or, if you wait until tomorrow the fix will be in the pre-release version of the extension tomorrow. As soon as we can confirm that this solves the issue I'll make a patch release with the fix.

@alexr00 thanks, looking good with v0.85.2024040310. I don't see the error anymore.

Great, thanks for testing! I just published a pre-release build with the fix, which should be available shortly. I'll aim to have a stable build with the fix on Monday.


Add check for Kafka resources

Add checks for kafka, kafkaclaim, kafkacomposite, and kafkauser

Great addition! Especially when there are install related problems this will help quickly identify the area to focus on!

The example should include the name and namespace that are in our docs. I think this would be cp4waiops namespace and ibm-cp-watson-aiops

Good point.  Updated.


having difficulty building...

So I am trying to build this for the first time. I do have go 1.10 on my mac. I had to install dep using brew (not sure why the go get... command didn't appear to do anything.
Anyway, I am on the make deps step and I get an error:
SECMacbookPro:newrelic-cli scottchapman$ make deps
git config --global url."git@github.com:".insteadOf "https://github.com/"
dep ensure
/Users/scottchapman/Workspaces/newrelic-cli is not within a known GOPATH/src
make: *** [deps] Error 1

(sorry, not a seasoned Go developer...)

I had the same issue. Move "newrelic-cli" to the ~/go/src/ folder and try again.

Make sure that your $GOPATH is corrected configured, you can checkout a command go env
Also add the GOPATH and you bash profile:
echo export GOPATH="$HOME/go" >> ~/.bash_profile
echo export PATH="$PATH:$GOPATH/bin" >> ~/.bash_profile

Not sure if you all have made progress, but this is what worked for me...
go get github.com/IBM/newrelic-cli
this installed the binary to run to $GOPATH/bin/newrelic-cli
then i just aliased that in my ~/.bash_profile
alias nr=newrelic-cli
Next new terminal session you start should be able to run nr. Alternatively run source ~/.bash_profile and your current session should also work.


Improved triggers for Main Workflow

Description
Self-explained
Types of changes

[x] House cleaning (change at project level, like tooling revamp, refactors, etc)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] Enhancement (non-breaking change which improves existing functionality)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (something that would cause existing functionality to not work as expected)
[ ] Documentation (self-explained)

Implementation details
N/A

Codecov Report

Merging #59 (ed50df9) into master (342a4e6) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #59   +/-   ##
=======================================
  Coverage   96.64%   96.64%
=======================================
  Files           8        8
  Lines         149      149
=======================================
  Hits          144      144
  Misses          5        5

Continue to review full report at Codecov.

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


Motion detector sensor not available (continue from #61)

Yes, all those steps were checked.
Originally posted by @vdiogo in https://github.com/JurajNyiri/HomeAssistant-Tapo-Control/issues/61#issuecomment-767509290

Please do not open new tickets and keep the conversation in the old one.

Please do not open new tickets and keep the conversation in the old one.


Can't install on Windows

I am getting this error:

Thanks.

This is a duplicate of many others issues regarding the postinstall script of cross-spawn for Windows: https://github.com/Glavin001/atom-beautify/search?q=postinstall&type=Issues&utf8=✓

I just published a patch in release v0.29.4 that makes cross-spawn dependency optional.
The cross-spawn package depends on spawn-sync and has been causing problems when installing Atom-Beautify for many users. By making this dependency optional, users will be able to easily install Atom-Beautify and, in the case that cross-spawn fails to install, will fallback to the builtin spawn method.


[WIP] feat: convert artist insights filter button to new style

The type of this PR is: FEAT

This PR resolves FX-2905
Description
Following up on #4703, this PR does the same for the Insights tab
Still to resolve:

[ ] Stickiness

PR Checklist (tick all before merging)

[ ] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[ ] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[ ] I have documented any follow-up work that this PR will require, or it does not require any.
[ ] I have added an app state migration, or my changes do not require one. (What are migrations?)
[ ] I have added a CHANGELOG.yml entry or my changes do not require one.

Closing - deprioritized for saved search v1.0


Add tfcmt

https://github.com/suzuki-shunsuke/tfcmt
https://speakerdeck.com/szksh/terraform-platform-in-quipper?slide=26
tfcmt is CLI to notify the result of plan and apply as Pull Request comment.

Mighty helpful. Thanks for creating this @suzuki-shunsuke


ceylon-lang.org, not .com

The readme has a link pointing to http://try.ceylon-lang.com but it should be http://try.ceylon-lang.org

Done, thx.


How do I know which major stemcell versions to be fetching on?

How can the pipeline know which major stemcell version to go retrieve? Should each individual tile pipeline be in charge of downloading/uploading the latest stemcell? Should some other pipeline automatically listen for available stemcells & upload them automatically, then the tile-pipelines be responsible for applying them? Should I just load the opsman with a pivnet API token & poll the "check for available stemcells" API endpoint?
Inspiration: https://github.com/pivotal-cf/pcf-pipelines/blob/master/tasks/upload-product-and-stemcell/task.sh

I think I'm going with putting the stemcell version for the tile in the tile.yml for each product

Simply going to write the stemcell version in the products' tile.yml & load it in as a param when flying up the pipeline.


Develop

#1293 unify cookie for api and ui tests
Thanks for contributing this Pull Request. Make sure that you submit this Pull Request against the develop branch of this repository, add a brief description, and tag the relevant issue(s) and PR(s) below.

Relevant Issues : Allow UI cookies to flow through api calls and vice-versa.
Type of change :

[x] New feature
[x] Bug fix for existing feature

@ptrthomas - thank you for the review - I will make the changes and resubmit.

@ptrthomas - pushed changes per review comments. Thank you.


should Diff Two Arrays' tests consider the order?

Challenge Diff Two Arrays has an issue.
User Agent is: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36.
It seems that the tests are not considering the order of elements in the returned array au contraire to the given "should return ..." causing a false-positive pass for test:

3 (should return ["diorite", "pink wool"])
6 (should return ["piglet", 4])
7 (should return ["snuffleupagus", "cookie monster", "elmo"])
8 (should return [1, "calf", 3, "piglet", 7, "filly"])

The following code will return an array with random order, however the tests will always pass:
/* jshint esversion: 6 */
/* jshint asi: true */

function shuffle (a) {
  for (let i = a.length; i; i--) {
    let j = Math.floor(Math.random() * i)
    ;[a[i - 1], a[j]] = [a[j], a[i - 1]]
  }
  return a
}

function diffArray (arr1, arr2) {
  return shuffle(arr1.filter(e => !arr2.includes(e)).concat(arr2.filter(e => !arr1.includes(e))))
}

diffArray([1, "calf", 3, "piglet"], [7, "filly"])

Apart from test 3 (which then should return ["pink wool", "diorite"]), the required results make me feel like one should use a solution that first returns the overall unique elements of arr1 and then those of arr2 (in occurring order).
If that is inteded the tests are wrong, if not maybe it should be mentioned in the instructions?

@logol the tests look like they use Chai's sameMembers assertion, which only tests that two arrays share the same members, and does not account for order. You bring up a good point, the test case messages indicate the arrays should be in a particular order, and your example does get around that.
I think we could fix this by saying should return an array containing... and list the elements, OR, we could use the deepEqual assertion to account for order, however, if we do that, I agree that it should go in the instructions.
I think the first option is probably better.


Bump dependencies

Bump golang:1.22.3-alpine
Bump alpine 3.19
I've upgraded and tested on my environment and all is good.

LGTM, ty!


Android - Emoji- Emoji is selected only on second tap

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Launch the app
Log in with account and select user
On Input box - tap on emoji icon
Tap on any emojis

Expected Result:
Emoji is selected on first tap
Actual Result:
Emojie is selected only on second tap
Workaround:
Unknown
Platform:

Where is this issue occurring?

Android

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/157999784-c9d4bb51-bd7c-4f01-8285-b90eecd9cd10.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause
Slack conversation:
Job Post: https://www.upwork.com/jobs/~01d711814db7c31f61
View all open jobs on GitHub

Triggered auto assignment to @johnmlee101 (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

K reproduced. Opening this up to external. I'm guessing it has to do with focus of the picker

Triggered auto assignment to @kevinksullivan (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

Triggered auto assignment to Contributor-plus team member for initial proposal review - @Santhosh-Sellavel (Exported)

Triggered auto assignment to @tgolen (Exported), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

Proposal
The issue is happen because the keyboard is still visible after the modal show, show the first press is for dismissing the keyboard then the second press is for selecting emoji.
My solution is to dismiss the keyboard when emoji button is pressed to open emoji modal.
https://github.com/Expensify/App/blob/7919e24c808dea9dedfe4a2d513365cf092cc1e1/src/components/EmojiPicker/EmojiPickerButton.js#L27-L34
-            onPress={() => EmojiPickerAction.showEmojiPicker(props.onModalHide, props.onEmojiSelected, emojiPopoverAnchor)}

+            onPress={() => {
+                /* Dismiss the keyboard before opening the modal, this will prevent double press when selecting emoji */
+                Keyboard.dismiss();
+                EmojiPickerAction.showEmojiPicker(props.onModalHide, props.onEmojiSelected, emojiPopoverAnchor);
+            }}

Also we need to add the timeout time from 50 to 100 to make room for keyboard opening.
https://github.com/Expensify/App/blob/7919e24c808dea9dedfe4a2d513365cf092cc1e1/src/pages/home/report/ReportActionCompose.js#L280
-                setTimeout(() => this.textInput.focus(), 50);
+                setTimeout(() => this.textInput.focus(), 100);

Result
https://user-images.githubusercontent.com/25520267/158630032-88984723-1f47-4894-b54c-d5058a7d215f.mov

@mollfpr Thank you for the proposal! It looks mostly good to me, but I did have a question.

The issue is happen because the keyboard is still visible after the modal show

From watching your video, it doesn't look to me like the keyboard is open before the modal opens, so then why does the keyboard need to be dismissed?

Ah, OK. That sounds good. Thank you!
I'm not too excited about changing the setTimeout() but it seems like that hack is still going to be there for a while, so I don't have any other suggestions.
🟢  to hire @mollfpr with that proposal @kevinksullivan

Hired @mollfpr , go ahead and accept whenever you get a chance!

@tgolen
Thanks for taking this quicker!
Seems PR is ready, let's assign @mollfpr this issue!

@tgolen Solution does not work for me!

@Santhosh-Sellavel what Android version do you use?

@mollfpr I am using a Android 12
Samsung device.

@Santhosh-Sellavel @tgolen I found the culprit.
We need to make the text input unfocus. There are two approaches to do this.

Dismiss the keyboard without checking is shown or not, in this way the text input will be blurred.

                /* Dismiss the keyboard before opening the modal, this will prevent double press when selecting emoji */
-                if (props.isShown) {
                    Keyboard.dismiss();
-                }

Passing the text input ref to EmojiPickerButton and call blur() when the modal will show.

                /** Unfocusing the text input to prevent double press when select a emoji */
                if (props.textInput) {
                    props.textInput.blur();
                }

Before either above solution applied
https://user-images.githubusercontent.com/25520267/159104272-1d53741c-2b05-4f0c-b1d0-0e5d9b231fe9.mov
With Keyboard.dismiss()
https://user-images.githubusercontent.com/25520267/159104386-0b3782fd-a2e9-4bfc-a086-0d4ce553c1bf.mov
With text input blur
https://user-images.githubusercontent.com/25520267/159104423-5456270e-53f4-4984-a96e-b8110763b357.mov
Those above solutions are great, but I'm thinking probably the EmojiPicker will be used not only in ReportActionCompose but maybe other components will also use this and maybe without EmojiPickerButton which trigger the modal in composing component. So the best solution I came up with is calling Keyboard.dismiss() whenever is emoji picker visible or not.
https://github.com/Expensify/App/blob/0b0a51ed0035d4e211e96c7cebfed83ce0063105/src/components/EmojiPicker/index.js#L32-L35
    // eslint-disable-next-line rulesdir/prefer-early-return
    componentDidUpdate(prevProps, prevState) {
        if (prevState.isEmojiPickerVisible !== this.state.isEmojiPickerVisible) {
            Keyboard.dismiss();
        }
    }

Result
https://user-images.githubusercontent.com/25520267/159104923-dd7d9e02-66e6-4d4d-82db-08d902479bcb.mov

@tgolen @Santhosh-Sellavel updated PR.

PR is merged!

Issue not reproducible during KI retests. (First week)

The solution for this issue has been :rocket: deployed to production :rocket: in version 1.1.49-1 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:

https://github.com/Expensify/App/pull/8221

If no regressions arise, payment will be issued on 2022-04-12. :confetti_ball:

Applied for C+ @kevinksullivan

Hired @Santhosh-Sellavel .

Issue not reproducible during KI retests. (Second week)

Paid. Thanks again @Santhosh-Sellavel @mollfpr !