Kotlin 1.6.X support

After upgraded project kotlin version to 1.6.21, build fails.
Can you help ?

Sorry to say, but this project is not maintained anymore. You can easily create an abstract class to encapsulate all serialization & deserialization logic.


Update kubernetes-portal.md for clusters with --api-server-authorized…

…-ip-ranges
// Customer feedback.
https://portal.microsofticm.com/imp/v3/incidents/details/205654912/home. We have two clusters - one with AuthorizedIPRanges enabled to restrict traffic and the other without. The one without nicely shows the Kubernetes resources blade and gives a great 'dashboard' view. However, the one with the rules is unable to pull up the dashboard. Which makes sense because of IP whitelisting. Is there anway to grant exception so the portal can still pull up the dashboard?
// Similar to below.
https://docs.microsoft.com/en-us/azure/container-registry/container-registry-access-selected-networks. 'To allow this access, you need the computer's public IPv4 address. You can find this address by searching "what is my IP address" in an internet browser'.
@palma21

@VijayRod : Thanks for your contribution! The author(s) have been notified to review your proposed change.


replies to comments don't show

Comments can be added as expected but replies don't show. the reply shows the user and the buttons but the reply text does  not appear.  I'm using Meteor <IP_ADDRESS>
See screenshots below
Screenshots

It doesn't work at all for me. Does it do the same thing when you set it up in a new/empty meteor app?

I answered in the issue you posted.

I am experiencing the same trouble.  Replies do not show.  They will show if you edit the reply and then save again.  However as soon as you refresh the page they disappear again.  I am using the semantic-ui template.

@delay Out of curiosity, what font are you using?

https://www.google.com/fonts/specimen/Source+Sans+Pro source sans pro. I really like it.

I did a tiny bit of testing.  replies work fine in version 0.2.15 but fail to show in the following version 1.0.0.  Which I am sure has some big changes given the versioning.  I will try to see if I can track it down further to see if I can discover the cause.

https://github.com/delay/comments-test  I made a simple project to demonstrate the bug.  The only thing that is installed is comments-ui accounts-password accounts-ui and semantic css.  if you try to make a reply it does not show.  Thanks so much for looking into this.

Some things. It's not updating even if i change data directly from the database.

Problem is here {{{enhancedContent}}}. Fast solutions is:
1: use markdown
2: replace {{{enhancedContent}}} with {{content}}
Long solution: observing changes when using a transformed publications.

I was able to reproduce it, will have a look when I get to it, feel free to submit PRs if you have an idea where the problem is.

This is fixed in the latest version 1.1.2

Thanks so much for the fix!  Great work!  I love this comment package.  It has saved me a ton of time in not having to code that functionality.


message_edit: Fix bug moving muted topic to already muted topic.

We were not handling this case, which resulted in failure.
discussion - https://chat.zulip.org/#narrow/stream/101-design/topic/Moving.20muted.20topics

Repushed a version that uses ignore_conflicts to silently do nothing in duplicate cases, rather than use a transaction.

This approach looks great to me, but there's some test failures I don't understand.

Looks great, configured to merge once CI passes.

@alexmv If I'm not wrong, after this PR we have two checks for duplicate attempts to mute topic/user, right?
# Topic muting
    if topic_is_muted(user_profile, stream.id, topic_name):
        raise JsonableError(_("Topic already muted"))

    try:
        do_mute_topic(user_profile, stream, topic_name, date_muted)
    except IntegrityError:
        raise JsonableError(_("Topic already muted")

# User muting
    if get_mute_object(user_profile, muted_user) is not None:
        raise JsonableError(_("User already muted"))

    try:
        do_mute_user(user_profile, muted_user, date_muted)
    except IntegrityError:
        raise JsonableError(_("User already muted")

... where the first duplicate detection is done by Django and the second by the DB. I did not understand why we could not have removed the first check then? Only having the second "check" (the try-catch block) should have been sufficient to handle both the non-race and race scenarios, correct?

Generally it's better to start this sort of conversation in #backend for visibility, but I believe it would be correct to remove the first check, yes. There can be some situations where it could be useful to have both checks, like if we had some expensive calculation that needs to happen in between, but I don't think that applies here.

Yeah, no objection to removing the first check -- that should be safe to do.

OK, @abhijeetbodas2001 want to do a quick PR for that removal? We can continue discussion of the rest here: https://github.com/zulip/zulip/pull/24236/files#r1096335153.

Discussion at https://chat.zulip.org/#narrow/stream/3-backend/topic/Follow.20Topics/near/1505448 and https://chat.zulip.org/#narrow/stream/3-backend/topic/UserTopic.3A.20Case.20insensitive.20topic.20name


FkConsumer.java:83: Fake consumer close is not implemented

The puzzle 54-846ada40 from #54 has to be resolved:
https://github.com/eo-cqrs/eo-kafka/blob/d78f949e67ac72229c396ec402568cb6573b91c9/src/main/java/io/github/eocqrs/kafka/fake/FkConsumer.java#L83-L83
The puzzle was created by h1alexbel on 04-May-23.
Estimate: 60 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@0pdd thank you for reporting this. I'll assign someone to take care of it soon.

@0pdd thank you for reporting this. I'll assign someone to take care of it soon.

I see you're talking to me, but I can't reply since I'm not a chat bot.

@l3r8yJ this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2023-05-14T12:12:45.756574.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@l3r8yJ Don't forget to close this ticket before the deadline (2023-05-14T12:12:46). You are past the first half of the allowed period.

@zoeself deregister

@h1alexbel ok, I've removed this task from scope. I'm not managing it anymore.

@l3r8yJ depends on #120


ARROW-12808: [JS] Document browser support

Merge after https://github.com/apache/arrow/pull/10340


Sending back result

Guessing from the title it probably relates to rex-client part. Closing as not related.


Dev Test: Projectile Motion 1.0.0-dev.13

Test Link: http://www.colorado.edu/physics/phet/dev/html/projectile-motion/1.0.0-dev.12/projectile-motion_en.html
Changes since last dev version:

Keypad ranges (https://github.com/phetsims/projectile-motion/issues/135)
Fix objects with wrong rotation (https://github.com/phetsims/projectile-motion/issues/137)
Add apex marker and prioritize it on the tracer tool
Fix iPad2 bugginess (https://github.com/phetsims/projectile-motion/issues/129)
New flatirons image (https://github.com/phetsims/projectile-motion/issues/142)
Make probe on tracer tool draggable

Updated test link: http://www.colorado.edu/physics/phet/dev/html/projectile-motion/1.0.0-dev.12/projectile-motion_en.html
With these updates:

Fix algorithm for new trajectories (https://github.com/phetsims/projectile-motion/commit/2bc0291c9adf22aa8897598443cf27fd87474b0d)
Make drag force label invisible if air resistance off (https://github.com/phetsims/projectile-motion/commit/8b37ab5a670f900dddd47b82da5607480987fe17)

Updated test link: http://www.colorado.edu/physics/phet/dev/html/projectile-motion/1.0.0-dev.13/projectile-motion_en.html
Should bring loading splash back.

Done.


Error when switch to built-in package without deleting repo from straight/repos directory.

What's wrong
Error when running straight-pull-package:
straight-vc: VC backend ‘built-in’ does not implement method ‘fetch-from-remote’

Directions to reproduce
At the beginning, I use org by (straight-use-package 'org).
Then I learn that I can use the built-in org package. So I change it to (straight-use-package '(org :type built-in)). And I kept the org repo in straight/repos directory.
I sometimes run straight-pull-all to update all the packages. This error message will occur. This may not actually be a bug, but I think it should be handled.
Version information

Emacs version: This is GNU Emacs 29.0.50 (build 3, x86_64-pc-linux-gnu, GTK+ Version 3.24.20, cairo version 1.16.0) of 2021-11-01
Operating system: Ubuntu 20.04.3

Does M-x straight-normalize-package org help?

Nope. Running straight-normalize-package on org causes the following error:
straight-vc: VC backend ‘built-in’ does not implement method ‘normalize’

I think straight-remove-unused-repos will solve the problem by removing the unused org repo. But I also think the user should be able to choose to keep the repo, if the repo is not automatically removed when commenting out (straight-use-package 'org) in startup file.

I've implemented a pseudo VC back-end for packages with :type built-in which
ignores all operations.
@raxod502: Does this seem like too blunt an approach? If not, we can likely remove some ad-hoc checks that were introduced to deal with the built-in type. Off the top of my head I recall #617, but I'm sure there are more.
@fengqi-w: The first test below installs Org via the provided straight recipe.
The second test declares Org as :type built-in and then attempts some VC operations on all repositories.
Everything looks fine from these, but I would appreciate it if you could test the fix out as well and confirm that it fixes the issue. You can do so pointing straight-repository-user and straight-repository-branch to the values in the tests prior to the straight bootstrapping snippet in your init file.
Yodel Report (2021-11-02 14:21:40):
(yodel
  :user-dir "vc-built-in-test"
  :save t
  :formatter yodel-format-as-github-markdown
  :post*
  (setq straight-repository-user "progfolio" straight-repostiory-branch "fix/built-in-vc-backend" no-native-compile t)
  (defvar bootstrap-version)
  (let
      ((bootstrap-file
        (expand-file-name "straight/repos/straight.el/bootstrap.el" user-emacs-directory))
       (bootstrap-version 5))
    (unless
        (file-exists-p bootstrap-file)
      (with-current-buffer
          (url-retrieve-synchronously "https://raw.githubusercontent.com/raxod502/straight.el/develop/install.el" 'silent 'inhibit-cookies)
        (goto-char
         (point-max))
        (eval-print-last-sexp)))
    (load bootstrap-file nil 'nomessage))
  (straight-use-package 'org)
  (straight-fetch-all)
  (straight-pull-all)
  (straight-push-all)
  (straight-merge-all)
  (straight-normalize-all)
  (straight-check-all)
  (straight-rebuild-all)
  (org-version nil 'full 'message))

STDOUT:
Bootstrapping straight.el...
Bootstrapping straight.el...done
Rebuilding all packages due to build cache schema change
Looking for gnu-elpa-mirror recipe → Cloning melpa...
Looking for gnu-elpa-mirror recipe → Cloning melpa...done
Looking for emacsmirror-mirror recipe → Cloning gnu-elpa-mirror...
Looking for emacsmirror-mirror recipe → Cloning gnu-elpa-mirror...done
Looking for straight recipe → Cloning emacsmirror-mirror...
Looking for straight recipe → Cloning emacsmirror-mirror...done
Building straight...
Building straight...done
Cloning org...
Cloning org...done
Building org...
Building org...done
Processing repository "org"...
Processing repository "org"...done
Processing repository "straight.el"...
Processing repository "straight.el"...done
Processing repository "emacsmirror-mirror"...
Processing repository "emacsmirror-mirror"...done
Processing repository "gnu-elpa-mirror"...
Processing repository "gnu-elpa-mirror"...done
Processing repository "melpa"...
Processing repository "melpa"...done
Processing repository "org"...
Processing repository "org"...done
Processing repository "straight.el"...
Processing repository "straight.el"...done
Processing repository "emacsmirror-mirror"...
Processing repository "emacsmirror-mirror"...done
Processing repository "gnu-elpa-mirror"...
Processing repository "gnu-elpa-mirror"...done
Processing repository "melpa"...
Processing repository "melpa"...done
Processing repository "org"...
Processing repository "org"...done
Processing repository "straight.el"...
Processing repository "straight.el"...done
Processing repository "emacsmirror-mirror"...
Processing repository "emacsmirror-mirror"...done
Processing repository "gnu-elpa-mirror"...
Processing repository "gnu-elpa-mirror"...done
Processing repository "melpa"...
Processing repository "melpa"...done
Processing repository "org"...
Processing repository "org"...done
Processing repository "straight.el"...
Processing repository "straight.el"...done
Processing repository "emacsmirror-mirror"...
Processing repository "emacsmirror-mirror"...done
Processing repository "gnu-elpa-mirror"...
Processing repository "gnu-elpa-mirror"...done
Processing repository "melpa"...
Processing repository "melpa"...done
Processing repository "org"...
Processing repository "org"...done
Processing repository "straight.el"...
Processing repository "straight.el"...done
Processing repository "emacsmirror-mirror"...
Processing repository "emacsmirror-mirror"...done
Processing repository "gnu-elpa-mirror"...
Processing repository "gnu-elpa-mirror"...done
Processing repository "melpa"...
Processing repository "melpa"...done
Processing repository "org"...
Processing repository "org"...done
Processing repository "straight.el"...
Processing repository "straight.el"...done
Processing repository "emacsmirror-mirror"...
Processing repository "emacsmirror-mirror"...done
Processing repository "gnu-elpa-mirror"...
Processing repository "gnu-elpa-mirror"...done
Processing repository "melpa"...
Processing repository "melpa"...done

Org mode version 9.5 (release_9.5-202-g2e9999 @ /tmp/vc-built-in-test/straight/build/org/)

Environment

emacs version: GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, X toolkit, cairo version 1.17.4, Xaw3d scroll bars)
of 2021-10-09
system type: gnu/linux

Yodel Report (2021-11-02 14:22:13):
(yodel
  :user-dir "vc-built-in-test"
  :save t
  :formatter yodel-format-as-github-markdown
  :post*
  (setq straight-repository-user "progfolio" straight-repostiory-branch "fix/built-in-vc-backend" no-native-compile t)
  (defvar bootstrap-version)
  (let
      ((bootstrap-file
        (expand-file-name "straight/repos/straight.el/bootstrap.el" user-emacs-directory))
       (bootstrap-version 5))
    (unless
        (file-exists-p bootstrap-file)
      (with-current-buffer
          (url-retrieve-synchronously "https://raw.githubusercontent.com/raxod502/straight.el/develop/install.el" 'silent 'inhibit-cookies)
        (goto-char
         (point-max))
        (eval-print-last-sexp)))
    (load bootstrap-file nil 'nomessage))
  (straight-use-package
   '(org
     :type built-in))
  (straight-fetch-all)
  (straight-pull-all)
  (straight-push-all)
  (straight-merge-all)
  (straight-normalize-all)
  (straight-check-all)
  (straight-rebuild-all)
  (org-version nil 'full 'message))

STDOUT:
Processing repository "straight.el"...
Processing repository "straight.el"...done
Processing repository "emacsmirror-mirror"...
Processing repository "emacsmirror-mirror"...done
Processing repository "gnu-elpa-mirror"...
Processing repository "gnu-elpa-mirror"...done
Processing repository "melpa"...
Processing repository "melpa"...done
Processing repository "straight.el"...
Processing repository "straight.el"...done
Processing repository "emacsmirror-mirror"...
Processing repository "emacsmirror-mirror"...done
Processing repository "gnu-elpa-mirror"...
Processing repository "gnu-elpa-mirror"...done
Processing repository "melpa"...
Processing repository "melpa"...done
Processing repository "straight.el"...
Processing repository "straight.el"...done
Processing repository "emacsmirror-mirror"...
Processing repository "emacsmirror-mirror"...done
Processing repository "gnu-elpa-mirror"...
Processing repository "gnu-elpa-mirror"...done
Processing repository "melpa"...
Processing repository "melpa"...done
Processing repository "straight.el"...
Processing repository "straight.el"...done
Processing repository "emacsmirror-mirror"...
Processing repository "emacsmirror-mirror"...done
Processing repository "gnu-elpa-mirror"...
Processing repository "gnu-elpa-mirror"...done
Processing repository "melpa"...
Processing repository "melpa"...done
Processing repository "straight.el"...
Processing repository "straight.el"...done
Processing repository "emacsmirror-mirror"...
Processing repository "emacsmirror-mirror"...done
Processing repository "gnu-elpa-mirror"...
Processing repository "gnu-elpa-mirror"...done
Processing repository "melpa"...
Processing repository "melpa"...done
Processing repository "straight.el"...
Processing repository "straight.el"...done
Processing repository "emacsmirror-mirror"...
Processing repository "emacsmirror-mirror"...done
Processing repository "gnu-elpa-mirror"...
Processing repository "gnu-elpa-mirror"...done
Processing repository "melpa"...
Processing repository "melpa"...done

Org mode version 9.5 (release_9.5-30-g10dc9d @ /usr/share/emacs/29.0.50/lisp/org/)

Environment

emacs version: GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, X toolkit, cairo version 1.17.4, Xaw3d scroll bars)
of 2021-10-09
system type: gnu/linux

I've tried branch fix/built-in-vc-backend and the error no longer exists.

Appreciate you testing it out. I've merged the fix into the "develop" branch.

Similar error appears again. The error only occurs when I run straight-pull-all. Running straight-pull-package on package org doesn't trigger this error.
I noticed there are functions straight-vc-git-merge-from-remote and straight-vc-git-merge-from-upstream. Maybe the built-in version is also needed.

Apologies. I somehow missed those two methods in #876. Fix is merged into the "develop" branch.

Thanks. It works now.

Does this seem like too blunt an approach? If not, we can likely remove some ad-hoc checks that were introduced to deal with the built-in type

Sorry the delay, no, your way seems more reasonable than my original design.


Unable to rollout converter

What happened?
From: https://github.com/pulumi/ci-mgmt/issues/889
This usually succeeds but trying it out here hits a panic at make tfgen.
First we get some warnings:
warning: %!(EXTRA string=Expected to pair --- begin/end for resource %v's Markdown header, string=digitalocean_monitor_alert)
warning: Expected an H1 in markdown for resource digitalocean_monitor_alert
warning: Found <elided> in description for [digitalocean_spaces_bucket_cors_configuration], but was able to preserve the examples. The description proper will be dropped in the Pulumi provider.
warning: Found <elided> in description for [digitalocean_spaces_bucket_policy], but was able to preserve the examples. The description proper will be dropped in the Pulumi provider.
warning: %!(EXTRA string=Expected to pair --- begin/end for resource %v's Markdown header, string=digitalocean_uptime_alert)
warning: Expected an H1 in markdown for resource digitalocean_uptime_alert
warning: %!(EXTRA string=Expected to pair --- begin/end for resource %v's Markdown header, string=digitalocean_uptime_check)
warning: Expected an H1 in markdown for resource digitalocean_uptime_check
warning: Found <elided> in description for [digitalocean_reserved_ip], but was able to preserve the examples. The description proper will be dropped in the Pulumi provider.
panic: fatal: error An assertion has failed: bulk converting examples failed. source error: convertViaPulumiCLI: pulumi command failed: exit sta

Then we get to this:
Converting from terraform...
panic: fatal: An assertion has failed: empty path part passed into getInfo

goroutine 71 [running]:

github.com/pulumi/pulumi/sdk/v3/go/common/util/contract.failfast(...)

        /Users/runner/go/pkg/mod/github.com/pulumi/pulumi/sdk/v3@v3.105.0/go/common/util/contract/failfast.go:23

github.com/pulumi/pulumi/sdk/v3/go/common/util/contract.Assertf(0x1?, {0xf67ceff?, 0x57a05748?}, {0x0?, 0x2?, 0xc001261750?})

        /Users/runner/go/pkg/mod/github.com/pulumi/pulumi/sdk/v3@v3.105.0/go/common/util/contract/assert.go:35 +0xe8

github.com/pulumi/pulumi-converter-terraform/pkg/convert.(*scopes).getInfo.func1({0x0, 0x0}, 0x0, {0xc000afb570?, 0x2, 0x2})

        /Users/runner/work/pulumi-converter-terraform/pulumi-converter-terraform/pkg/convert/tf_scopes.go:191 +0xc5

github.com/pulumi/pulumi-converter-terraform/pkg/convert.(*scopes).getInfo.func1({0x0, 0x0}, 0x0, {0xc000afb560?, 0x3, 0x3})

        /Users/runner/work/pulumi-converter-terraform/pulumi-converter-terraform/pkg/convert/tf_scopes.go:225 +0x376

github.com/pulumi/pulumi-converter-terraform/pkg/convert.(*scopes).getInfo(0xc000ab8500, {0xc000d223c0, 0x30})

        /Users/runner/work/pulumi-converter-terraform/pulumi-converter-terraform/pkg/convert/tf_scopes.go:311 +0x743

github.com/pulumi/pulumi-converter-terraform/pkg/convert.(*scopes).pulumiName(0x10081ce0?, {0xc000d223c0?, 0xfeef100?})

        /Users/runner/work/pulumi-converter-terraform/pulumi-converter-terraform/pkg/convert/tf_scopes.go:316 +0x2a

github.com/pulumi/pulumi-converter-terraform/pkg/convert.convertObjectConsExpr(0xc0012638c8, 0x7?, 0xc000ab8500, {0xc001888160, 0x1e}, 0x1c?)

        /Users/runner/work/pulumi-converter-terraform/pulumi-converter-terraform/pkg/convert/tf.go:992 +0x1e5

github.com/pulumi/pulumi-converter-terraform/pkg/convert.convertExpression(0xfe35c01?, 0xd8?, 0xc0019b91d8?, {0xc001888160?, 0x16?}, {0x1007dee0?, 0xc0006817c0?})

        /Users/runner/work/pulumi-converter-terraform/pulumi-converter-terraform/pkg/convert/tf.go:1582 +0x2b6

github.com/pulumi/pulumi-converter-terraform/pkg/convert.convertBody(0xc0012638c8, 0xc000ab8500, {0xc001888140, 0x19}, {0x1007de00, 0xc0009daa50})

        /Users/runner/work/pulumi-converter-terraform/pulumi-converter-terraform/pkg/convert/tf.go:1854 +0x1768

github.com/pulumi/pulumi-converter-terraform/pkg/convert.convertManagedResources(0xc0012638c8, {0x10067fc8, 0xc000c022a0}, 0xc000ab8500, 0xc001d88600, 0xc000aca5b8)

        /Users/runner/work/pulumi-converter-terraform/pulumi-converter-terraform/pkg/convert/tf.go:2290 +0x13d4

github.com/pulumi/pulumi-converter-terraform/pkg/convert.translateModuleSourceCode(0xc001263e58, {0x1008d130, 0xc000758990}, {0xfc674c0, 0x1}, {0x1008d130, 0xc000758a50}, {0xfc674c0, 0x1}, {0x10067fc8, ...})

        /Users/runner/work/pulumi-converter-terraform/pulumi-converter-terraform/pkg/convert/tf.go:3026 +0x3985

github.com/pulumi/pulumi-converter-terraform/pkg/convert.TranslateModule(...)

        /Users/runner/work/pulumi-converter-terraform/pulumi-converter-terraform/pkg/convert/tf.go:3128

main.(*tfConverter).ConvertProgram.func1({0xc000b9a12c, 0x3}, {0xc000495200, 0x2dc})

        /Users/runner/work/pulumi-converter-terraform/pulumi-converter-terraform/cmd/pulumi-converter-terraform/main.go:103 +0x2fe

main.parTransformMapWith[...].func1()

        /Users/runner/work/pulumi-converter-terraform/pulumi-converter-terraform/cmd/pulumi-converter-terraform/par.go:56 +0x1ac

created by main.parTransformMapWith[...] in goroutine 25

        /Users/runner/work/pulumi-converter-terraform/pulumi-converter-terraform/cmd/pulumi-converter-terraform/par.go:53 +0xd5

error: rpc error: code = Unavailable desc = error reading from server: EOF

Example
N/A
Output of pulumi about
v3.112.0
Additional context
N/A
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

I'll look into extracting the mappings and the specific example this fails on, this is not easy to debug.

@t0yv0 I'll assign this to you for now, hope that's fine, let me know if you need help.

https://gist.github.com/t0yv0/980a311738ac109de02e28f0dbe3ac4f is the repro

I can't take this unfortunately but I'll open an issue to block on.

https://github.com/pulumi/pulumi-converter-terraform/issues/145

Much appreciated!

Unmarking from blocked since the converter issue is fixed now

It's not released though @mikhailshilkov
@pulumi/platform  can we get a quick release of https://github.com/pulumi/pulumi-converter-terraform much appreciated

https://github.com/pulumi/pulumi-converter-terraform/pull/150

Fixed in https://github.com/pulumi/pulumi-digitalocean/commit/59545973392c701f5c08aab97778e432d89f6da2


Add Evidence: New Project command and folder context menu options

Per our discussions and scope set for the phase 1 of interactive Evidence extension features, we'll add Evidence: New Project functionality.
UX and Flow Details

[x] Add new evidence.newProject command config to package.json
[x] Add New Evidence Project context menu to folders in the File Explorer by adding evidence.newProject command to menus: explorer:context [] commands and contribution point in extension package.json config
[x] Add NewEvidence enum value to Commands to register enum in commands.ts
[x] Create new src/commands/project.ts for the project command(s) implementation with Select Folder dialog when no new project folder Uri is provided
[x] Display Open Dialog for the folder selection when this command is called from the Command Palette...
[x] Display an Info message if the selected folder contains files, and prompt to create and use new empty workspace folder for the new Evidence project
[ ] Extend current project from template functionality from #2 to create New Evidence Project inside the selected folder in VS Code File Explorer
[ ] Clone Evidence template project to the selected empty workspace folder
[ ] Open new Evidence project folder in a new VS Code window.

New Evidence Project command display in the Command Palette...

New Evidence Project command displayed for the selected folder in the built-in vscode File explorer context menu:

Select new project folder dialog display listing all the folders in an open workspace:

Evidence extension Output view with the start of Create new project logging to trace this process:

Empty folder check, info message, and project folder dialog selection re-redisplay when the previously selected folder has files, or subfolders with files:

Create New Project in selected Folder with the default Evidence template project cloning below. I don't think this can be any simpler. We'll see if we should embed template project instead of cloning it from github in a separate ticket.

Some final notes on this New Project feature implementation for testing:

We don't prompt for the template project github url to clone it for a new Evidence project
Users can use the initial Create Project from Template feature to create new projects from their own Evidence app templates on github
We don't prompt to install dependencies for the Evidence project created in an open Workspace with other files because we don't have support for the "nested" Evidence projects and files in an open workspace. See our new Limitations section in docs for more info on this. We will update that section prior to v1.1.0 final features release.

The last part is now scripted too in #59, but users need to click ok to open newly ceated Evidence project in a new VS Code window:

Updated New Project Output view logging and display from #58:

Changed Project is not empty notification to an error message in #61:

Creating New Project in an empty VS Code workspace from start to finish:

Issue with credentials
Repro

Open a new workspace
add a folder that will contain evidence eg reports
right click reports-> Create new Evidence project

Expected behaviour
No credentials are added in root folder
Actual
Credentials are added at the root folder (not inside reports folder).
These probably aren't harmful, but are confusing

@archiewood what do you mean by credentials? we don't modify any file or folder credentials anywhere in this vscode extension.
Are you referring to the ./evidence folder created it at the top level of the open workspace folder?

Are you referring to the ./evidence folder created at the top level of the open workspace folder?
Yes

In this case it is not used, as it should be inside the child directory

See most recent changes in #60 to address that. I will remove my settings.json copy from clone repo code.

Tagging #65 to track it for v1.1.0 release

@archiewood resolved your issue in the commit above. Also, please try creating new project from the built-in template. It's instant:

Yep works instantly for me as well. 🔥
Any reason we do not use this for the core "Create Evidence Project from template" command?

Did not get to it 🙂  See #63
Plus I was not sure how well it would work on the Mac and needed you to test it.
We can wrap it up in #63 today.


It is good to sort things out :)


kaldi fails to build on master

❯ nom-build -A kaldi
these derivations will be built:
  /nix/store/bm3r3nfv5w51dvqzfr5ix3piwvp8pq8f-kaldi-2020-12-26.drv
building '/nix/store/bm3r3nfv5w51dvqzfr5ix3piwvp8pq8f-kaldi-2020-12-26.drv' on<EMAIL_ADDRESS>unpacking sources
unpacking source archive /nix/store/m7iyn2s0fb3s9wq2lvcbcyx6ywa1wihj-source
source root is source
patching sources
configuring
fixing cmake files...
cmake flags: -DCMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_BUILD_TYPE=Release -DCMAKE_SKIP_BUILD_RPATH=ON -DBUILD_TESTING=OFF -DCMAKE_INSTALL_LOCALEDIR=/nix/store/sznh4kw5j4g7wzspiwlr9llpq1gllm7w-kaldi-2020-12-26/share/locale -DCMAKE_INSTALL_LIBEXECDIR=/nix/store/sznh4kw5j4g7wzspiwlr9llpq1gllm7w-kaldi-2020-12-26/libexec -DCMAKE_INSTALL_LIBDIR=/nix/store/sznh4kw5j4g7wzspiwlr9llpq1gllm7w-kaldi-2020-12-26/lib -DCMAKE_INSTALL_DOCDIR=/nix/store/sznh4kw5j4g7wzspiwlr9llpq1gllm7w-kaldi-2020-12-26/share/doc/kaldi -DCMAKE_INSTALL_INFODIR=/nix/store/sznh4kw5j4g7wzspiwlr9llpq1gllm7w-kaldi-2020-12-26/share/info -DCMAKE_INSTALL_MANDIR=/nix/store/sznh4kw5j4g7wzspiwlr9llpq1gllm7w-kaldi-2020-12-26/share/man -DCMAKE_INSTALL_OLDINCLUDEDIR=/nix/store/sznh4kw5j4g7wzspiwlr9llpq1gllm7w-kaldi-2020-12-26/include -DCMAKE_INSTALL_INCLUDEDIR=/nix/store/sznh4kw5j4g7wzspiwlr9llpq1gllm7w-kaldi-2020-12-26/include -DCMAKE_INSTALL_SBINDIR=/nix/store/sznh4kw5j4g7wzspiwlr9llpq1gllm7w-kaldi-2020-12-26/sbin -DCMAKE_INSTALL_BINDIR=/nix/store/sznh4kw5j4g7wzspiwlr9llpq1gllm7w-kaldi-2020-12-26/bin -DCMAKE_INSTALL_NAME_DIR=/nix/store/sznh4kw5j4g7wzspiwlr9llpq1gllm7w-kaldi-2020-12-26/lib -DCMAKE_POLICY_DEFAULT_CMP0025=NEW -DCMAKE_OSX_SYSROOT= -DCMAKE_FIND_FRAMEWORK=LAST -DCMAKE_STRIP=/nix/store/kmqs0wll31ylwbqkpmlgbjrn6ny3myik-binutils-2.35.1/bin/strip -DCMAKE_RANLIB=/nix/store/kmqs0wll31ylwbqkpmlgbjrn6ny3myik-binutils-2.35.1/bin/ranlib -DCMAKE_AR=/nix/store/kmqs0wll31ylwbqkpmlgbjrn6ny3myik-binutils-2.35.1/bin/ar -DCMAKE_C_COMPILER=gcc -DCMAKE_CXX_COMPILER=g++ -DCMAKE_INSTALL_PREFIX=/nix/store/sznh4kw5j4g7wzspiwlr9llpq1gllm7w-kaldi-2020-12-26 -DKALDI_BUILD_TEST=off -DBUILD_SHARED_LIBS=on
-- The C compiler identification is GNU 10.3.0
-- The CXX compiler identification is GNU 10.3.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /nix/store/2qmkkrkk2d1jvin6iy8yvfh7iaawyqwm-gcc-wrapper-10.3.0/bin/gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /nix/store/2qmkkrkk2d1jvin6iy8yvfh7iaawyqwm-gcc-wrapper-10.3.0/bin/g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found PythonInterp: /nix/store/dqxic3j7csd4ywn94n4smmnz55p039g3-python3-3.9.6/bin/python (found version "3.9.6")
-- Running gen_cmake_skeleton.py
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Looking for sgemm_
-- Looking for sgemm_ - found
-- Found BLAS: /nix/store/8ms61phzj3al5axdsciy8b0c5xxnxxgn-openblas-0.3.17/lib/libopenblas.so
-- Looking for cheev_
-- Looking for cheev_ - found
-- A library with LAPACK API found.
CUDA_TOOLKIT_ROOT_DIR not found or specified
-- Could NOT find CUDA (missing: CUDA_TOOLKIT_ROOT_DIR CUDA_NVCC_EXECUTABLE CUDA_INCLUDE_DIRS CUDA_CUDART_LIBRARY)
CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required):
  Compatibility with CMake < 2.8.12 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- Configuring done
-- Generating done
-- Build files have been written to: /build/source/build/openfst-download
[ 11%] Creating directories for 'openfst'
[ 22%] Performing download step (git clone) for 'openfst'
[ 33%] Performing update step for 'openfst'
CMake Error at /build/source/build/openfst-download/openfst-prefix/tmp/openfst-gitupdate.cmake:25 (message):
  Failed to get the hash for HEAD:

make[2]: *** [CMakeFiles/openfst.dir/build.make:130: openfst-prefix/src/openfst-stamp/openfst-update] Error 1
make[1]: *** [CMakeFiles/Makefile2:83: CMakeFiles/openfst.dir/all] Error 2
make: *** [Makefile:91: all] Error 2
CMake Error at cmake/third_party/get_third_party.cmake:18 (message):
  Build step for openfst failed: 2
Call Stack (most recent call first):
  CMakeLists.txt:162 (get_third_party)

-- Configuring incomplete, errors occurred!
See also "/build/source/build/CMakeFiles/CMakeOutput.log".
See also "/build/source/build/CMakeFiles/CMakeError.log".
builder for '/nix/store/bm3r3nfv5w51dvqzfr5ix3piwvp8pq8f-kaldi-2020-12-26.drv' failed with exit code 1

cc @Mic92

Bisected to
3c7fbeaf4ab650eab91a3f8d14b0a71858c55900 is the first bad commit
commit 3c7fbeaf4ab650eab91a3f8d14b0a71858c55900
Author: Tobias Mayer<EMAIL_ADDRESS>Date:   Mon Aug 2 21:11:14 2021 +0200

    Revert "Revert "cmake: 3.19.7 -> 3.21.0""

    This reverts commit bd57a30d1ba907783e73fe1d887bf62b8a7c1760.

 .../cmake/application-services.patch               | 26 ++++++++++------------
 .../tools/build-managers/cmake/default.nix         |  5 ++---
 2 files changed, 14 insertions(+), 17 deletions(-)

This is an error when calling git rev-parse HEAD.
We should fix git wrapper.


OTA Update

The library works great on its own!
I have tried to add OTA capability to my code from the Arduino BasicOTA example.
The OTA update is super slow unless I remove matrix.begin(...
Has anyone got this working with OTA?
Thanks

Nope. No issues with OTA here, plenty of people have it working fine.  Probably an issue with that library.
I just use: https://github.com/espressif/arduino-esp32/tree/master/libraries/HTTPUpdate

I also had lots of problems with OTA updates being really unreliable, slow and failing almost all the time while using the dma matrix library.
I fixed it by disabling the dma output stream once the update starts by calling dma_display->stopDMAoutput(); in the ArduinoOTA.onStart() callback of the OTA library. Apparently the dma stream and its interrupts were messing with the TCP connection reliability (I saw lots of TCP retransmissions in Wireshark during the update). To reset the ESP32 to a known state after the update, call ESP.restart(); in the ArduinoOTA.onError() and ArduinoOTA.onend() callback functions.


Update timeout for .github/workflows/node.js.yml

This is an automated pull request to update default timeouts for all jobs in .github/workflows/node.js.yml that do not currently contain a default timeout property.
Please review these changes closely to ensure that all jobs have sufficient time to run. If a job needs more time, please add a timeout property to that job to override the organization default.
Additionally, please be attentive to unintended changes to the workflow YAML file, as the parser is not perfect.
Lastly, note that it is up to the reviewer to merge this pull request and delete the PR branch once they are satisfied with the changes.

 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.


Testing significantly slows down with more tests

In order to reduce the impact of added tests in the same file, this PR limits the number of tests run in parallel to 4.
Without changes on the current main commit, this was the effective limit, as there were not VM tests that had more than 4 tests. But in #307 many more tests were added.
Limiting concurrent test runs to 4 should help alleviate the added time, especially for windows.

See https://github.com/rust-osdev/bootloader/pull/309#issuecomment-1372045670


emit event as const by default, add _mut variants.

This doesn't change the observe-side.

It seems better to default to non-mut by default and things that require mut have a _mut suffix.

seems like a good change to me & the rust way (using _mut)

Not sure which things to do further ... the observe side needs a lot of work, but this part here works as it is.

Did some of the changes you proposed. If there's anything else, do let me know :D


chore(deps): update dependencies

:tada: This PR is included in version 5.0.0-beta.6 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 5.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Search panel overlaps other parts of UI

on fsdf dataset level interface, the search part overlaps with other parts, e.g. https://linked.fsdf.org.au/dataset/electrical-infrastructure

Re-raise in FE repo if issue w/ new Vue.js FE.


How many ASVs describe a species and does that number plateau with number of genomes?

We have previously seen that the number of ASVs per copy of the rRNA gene is about 0.6. This means that if a genome has 10 copies of the 16S rRNA gene, we would expect to see about 6 different versions of the gene within that genome. Across genomes from the same species, we know that the number of copies of the gene is pretty consistent. So, if we look at multiple genomes from the same species, will we see the same versions of the gene or will we see new versions of the gene? To answer this, we would like to look at the relationship between the number of ASVs found in a species per number of genomes in the species versus the number of genomes. Besides looking at the full-length sequences, let's also look at the V4, V3, V4-V5.

It would be great to have a table that indicates the number of ASVs for each region for each species along with number of genomes for that species and its average number of rrn copies in our dataset.


Fix missing array close bracket

closes #207

Hi Prajwal,
Thanks for the PR!
This test case looks like a test for conforming to the TOML spec and not a test for the Python API. Those test cases belong in the language independent TOML test suite.


Core Reconciler tests and easy-to-reuse Resolver test harnesses

Feature request
Testing reconcilers requires quite a bit of setup code which we don't have yet for this project. This is an important short-term problem for three different classes of test:

The core ResolutionRequest reconciler, though relatively small, needs thorough test coverage
The "resolver framework" needs to have the contracts (interfaces) it exposes tested to ensure they work consistently for all resolvers.
Resolver developers need a pain-free way of spinning up a test harness so that they can quickly add coverage to new resolvers.

Use case
Primarily concerned here with supporting developers of new resolvers by giving them a pain-free-as-possible way for them to exercise their resolver code quickly and easily.
Since a resolver is just a reconciler under the hood hopefully we can find a way to provide a Resolver Test Harness that is general purpose for anyone's resolver development.
Inspiration
The Tekton Pipelines unit test suite includes a plethora of setup code that performs all the necessary injection gubbins to support testing their Reconcilers. This might be a good first place to look for inspiration: https://github.com/tektoncd/pipeline/blob/main/test/controller.go

/assign


[Bug]

The problem
I'm not sure if i'm using this right, so might not really be a bug.
Upon adding this to Hacs, i get 2 new integrations, asus router and asus wrt.

What's the difference between the 2 ?
Asusrouter seems to auto discover my RT-ax86u, all good.
What do i fill in, router or access point ?
Finally, whichever i choose, it seems to only 'see' 25 devices? i currently have 87 connections to my access point. How do i see that? (i'm really interested in monitoring this, your tool seems to be perfect for this).

Thanks for your help!
Your device model
rt-ax86u
Firmware type
Stock
Firmware version
latest (non-beta)
Integration version with the issue
latest, just downloaded from hacs
Method of the integration installation
HACS
What version and type of Home Assistant installation do you use
latest, non beta channel
Is there anything useful in the logs?
No response
Diagnostics information
No response
Additional information
No response

Hello,
AsusWRT is an in-built into HA integration.
AsusRouter will show in your HA by its name and the discovered device is the one from this integration.
The two integrations are built on completely different backend. AsusRouter is using the same API as the Asus mobile app or the Web UI. AsusWRT is using SSH or Telnet connection.
AsusRouter provides many more sensors and controls
You should probably use the Router mode. This is the mode suitable for most of the users. Different modes are just providing different sets of information (in order to not create empty sensors if the device cannot provide such an info or it is by default wrong)
Do you see only 25 device trackers? This might be connected to the way HA is creating device tracker entities. Please, check that there are no other entities just in a "disabled" state - you will need to enable them

Ah ok so asus wrt is not yours?
Yeah I was hoping to see the amount of devices connected but it shows 25 MAC addresses only

From: Yevhenii Vaskivskyi @.>
Sent: 25 June 2023 12:36
To: Vaskivskyi/ha-asusrouter @.>
Cc: atv2016 @.>; Author @.>
Subject: Re: [Vaskivskyi/ha-asusrouter] [Bug] (Issue #601)
Hello,
AsusWRT is an in-built into HA integration.
AsusRouter will show in your HA by its name and the discovered device is the one from this integration.
The two integrations are built on completely different backend. AsusRouter is using the same API as the Asus mobile app or the Web UI. AsusWRT is using SSH or Telnet connection.
AsusRouter provides many more sensors and controls
You should probably use the Router mode. This is the mode suitable for most of the users. Different modes are just providing different sets of information (in order to not create empty sensors if the device cannot provide such an info or it is by default wrong)
Do you see only 25 device trackers? This might be connected to the way HA is creating device tracker entities. Please, check that there are no other entities just in a "disabled" state - you will need to enable them
—
Reply to this email directly, view it on GitHubhttps://github.com/Vaskivskyi/ha-asusrouter/issues/601#issuecomment-1606050653, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEBCFUZ3GWJ6H2EZZYQGUXDXNAPDLANCNFSM6AAAAAAZSBCSZE.
You are receiving this because you authored the thread.Message ID: @.***>

Hello. Sorry for the late reply.
Please, check how many connected devices are shown in the connected devices sensor. Its value is just a number and it has an attribute devices with the list of everything connected at the moment.
Does it show the same number of devices as the Web UI of the router?

Snapshot example

In case you are still experiencing issues with connected devices, please, reopen it or open a new one for any different problem with the integration.


[feature] currentcolor option in color palette

Request to add option to set the color currentcolor.
Useful in website:

to set SVG color in ancestor mark-up
to allow for site theming (ie: switching from light to dark mode)

? eyedropper icon?

The library itself doesn't really address things like color, it just generates the points of a polygon. Do you mean in the example project (ie perfect-freehand.com?)


Use local recorded dataset if exists

What this does
Explain what this PR does. Feel free to tag your PR with the appropriate label(s).
Use local lerobot dataset if it exists.
Case happened when we recorded dataset with --push-to-hub 0 --local-files-only 1 and then want to train with it, without this change, there could be exception like:
huggingface_hub.errors.RepositoryNotFoundError: 401 Client Error. (Request ID: Root=1-67726fa1-235cf0064b60bb1e645fb4cf;f9c85308-8970-46a9-bfbb-5a760a981530)

which is caused by default local_files_only=False in class LeRobotDataset .
Examples:

Title
Label

Enhance
Use existing local recorded dataset if exist

How it was tested
Explain/show how you tested your changes.

No current tests breaking

How to checkout & try? (for the reviewer)
Provide a simple way for the reviewer to try out your changes.
Examples with SO100:

Record dataset

python lerobot/scripts/control_robot.py record \
  --robot-path lerobot/configs/robot/so100.yaml \
  --single-task "SO100 pick and place" \
  --fps 30 \
  --repo-id xuaner233/so100_pick_and_place \
  --tags "so100 pick" \
  --warmup-time-s 5 \
  --episode-time-s 30 \
  --reset-time-s 10 \
  --num-episodes 2 \
  --push-to-hub 0 \
  --local-files-only 1

Then trying to train with just recorded dataset:

python lerobot/scripts/train.py \
    dataset_repo_id=xuaner233/so100_pick_and_place \
    policy=act_so100_real \
    env=so100_real \
    hydra.run.dir=outputs/train/act_so100_pick_and_place \
    hydra.job.name=act_so100_pick_and_place \
    device=cuda

Thanks in advance for review!
Possible reviewers: @jess-moss @Cadene @aliberts


Update opening names

Maybe as a PR to lichess itself? If not, find a LT way

Doing it on the client would not work for various reasons. Best is to try to update the openings at https://github.com/lichess-org/chess-openings

I am updating the opening names using a tool now, but they are parallel to the opening names lichess uses.


Please add "Azure DevOps" to repo for searchability

Cannot find the repo unless searching for "VSTS"

Added in PR #122

There is also https://help.github.com/articles/classifying-your-repository-with-topics/ which might help too


chore: upgrade confluent platform dependencies version to 7.2.1

Use the same version as the the commons-for-apache-kafka-connect for confluent platform avro libraries
https://github.com/aiven/commons-for-apache-kafka-connect/blob/master/build.gradle#L88
Should fix #189.

Please note that the Confluent platform dependency is used only in integration tests, so it's very unlikely it'll fix any non-test related issue. Am I missing something?

I didn't notice that it was only use in the integration tests, sorry i'm more familiar with maven.
Does it makes sense that I see some 4.1.4 jars included in the plugin  ?
[kafka@kafka-cluster-connect-fcfd748c7-hr5wj connectors]$ ls -l aiven-kafka-connect-gcs-0.9.0/ | grep 4.1.4
-rw-r--r-- 1 root root   23920 Jul 19  2021 common-config-4.1.4.jar
-rw-r--r-- 1 root root   20789 Jul 19  2021 common-utils-4.1.4.jar
-rw-r--r-- 1 root root   35234 Jul 19  2021 kafka-avro-serializer-4.1.4.jar
-rw-r--r-- 1 root root   38992 Jul 19  2021 kafka-connect-avro-converter-4.1.4.jar
-rw-r--r-- 1 root root   52411 Jul 19  2021 kafka-schema-registry-client-4.1.4.jar

Does it makes sense that I see some 4.1.4 jars included in the plugin ?

Thanks for noticing. They shouldn't in fact be included as they're expected to be provided by the target Kafka installation. They must have leaked somehow. We will remove them.


Further Yaml unicode issues

Continue on from #3419

Starting to suspect an issue with the Start/End index markers that SnakeYaml reports to us when unicode is involved; as shown in the output following https://github.com/openrewrite/rewrite/pull/3421/commits/0a26f95127f4eec8dc4b0c6503e82b39fc7bd26c.
By their own admission in the Mark class JavaDoc, they don't use the Mark much themselves:

It's just a record and its only use is producing nice error messages. Parser does not use it for any other purposes.

We're relying on those Mark indices to set lastEnd, with some accommodations here and there for various elements.
Not sure enough yet to report an issue with those to SnakeYaml, but something to explore / verify / reject / counteract.

Fixed in https://github.com/openrewrite/rewrite/pull/3507


percent for width and height

is it possible use % for dimension ?

+1

I'd like if i could set a % for colWidth


Updating nix-channel with sudo fails

Issue description
Running sudo nix-channel --update fails on osx 10.11.3 with unable to check ‘https://nixos.org/channels/nixpkgs-unstable’. Running without sudo doesn't have this issue and updates properly.
Maybe this is expected behaviour, but then the message is totally misleading for an nix beginner.
Steps to reproduce
Install nix with curl https://nixos.org/nix/install | sh and run sudo nix-channel --update
Technical details

System: osx 10.11.3
Nix version: 1.11.2
Nixpkgs version: 16.09pre80183.551296a

This might be due to the fact that sudo clears the environment, does that work better with sudo -E?

Thx, but this leads to following warning:
# sudo -E nix-channel --update
downloading Nix expressions from ‘https://nixos.org/releases/nixpkgs/nixpkgs-16.09pre80183.551296a//nixexprs.tar.xz’...
warning: the group ‘nixbld’ specified in ‘build-users-group’ does not exist
downloading ‘https://nixos.org/releases/nixpkgs/nixpkgs-16.09pre80183.551296a//nixexprs.tar.xz’... [6160/7141 KiB, 1223.9 KiB/s]
unpacking channels...
warning: the group ‘nixbld’ specified in ‘build-users-group’ does not exist

Creating the group (with sudo dscl . -create /Groups/nixbld and rebooting) didn't help.
Will this cause problems?

For single-user installations of Nix, I don't think it makes any difference.
Looks like the original issue was resolved, so I'm going to close this.


Indicate log output file path

When the log is specified in the config, indicate that there is logged output when something fails.

closed by 1603980c2cc39ca893b62fd6ef82ee949bb7cc39


Syndicats get one shot & explode instantly by mouse traps

Description
Syndicats will die/explode instantly after touching an activated mouse trap.
Additional context
I have no god damn clue if this is intended or not, but it sure does make syndicats not worth the TC knowing this. All I have to do is throw a mouse trap and they're dead instead of wasting a few bullets.

Yeah this is because the curve that controls the damage is super steep! The less you weigh the more damage the traps do. Cats only weigh like ~6 kelograms so the damage is very high.
I did some more testing and only two mousetraps is enough to gib a normal cat! I guess the fix is either to make cats weigh more or make the damage falloff steeper.

Syndicats are supposed to be immune to these step triggers, so when the fix gets it it'll be fixed

Fixed by  #31011


Device Cluster/HA Modeling: Put High-Level Domain Model Together, Present (Spike)

TODO

Create domain model representation of Device Cluster based on requirements in #1892
Create data-sets from real world examples:

Pair of firewalls
VRRP group of top-of-rack switches
Spine & Leaf (if possible)

Present for review with Architecture Team & community feedback

Outcome

Stories are added to #1892 to implement agreed upon design

Design accepted in #2615, details in #1892


bump-cask-pr: add support for :latest

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[ ] Have you successfully run brew tests with your changes locally?

This is a follow-up PR to #7986
Allows for updating a cask from an old version to :latest, or from :latest to a new version
Related: Homebrew/homebrew-cask#89077

not sure if its interesting just wanted to mention i got this in BigSur
Error: cannot load such file -- ruby-progressbar
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.6.0/gems/rubocop-0.90.0/lib/rubocop/formatter/fuubar_style_formatter.rb:3:in `<top (required)>'
/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.6.0/gems/rubocop-0.90.0/lib/rubocop.rb:590:in `require_relative'
/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.6.0/gems/rubocop-0.90.0/lib/rubocop.rb:590:in `<top (required)>'
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
/usr/local/Homebrew/Library/Homebrew/style.rb:76:in `run_rubocop'
/usr/local/Homebrew/Library/Homebrew/style.rb:52:in `check_style_impl'
/usr/local/Homebrew/Library/Homebrew/style.rb:15:in `check_style_and_print'
/usr/local/Homebrew/Library/Homebrew/cask/cmd/style.rb:24:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/cmd/abstract_command.rb:89:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/cmd.rb:237:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/cmd.rb:165:in `run'
/usr/local/Homebrew/Library/Homebrew/cmd/cask.rb:14:in `cask'
/usr/local/Homebrew/Library/Homebrew/brew.rb:119:in `<main>'
Error: `brew cask style --fix` failed!

Doesn't seem to related to this pull request (Could you open an issue for this?)

Big Sur beta is officially unsupported, so diagnosing and fixing the issue in a PR is the way to go please @core-code.


Progress when importing dump

When importing a torrent dump, this is what's outputted:
[~/bitcannon]$ ./bitcannon_linux_amd64 ./dump.txt.gz
[OK!] Connecting to Mongo at <IP_ADDRESS>
[OK!] Attempting to parse ./dump.txt.gz
[OK!] File opened
[OK!] Extension is valid
[OK!] GZip detected, unzipping enabled
[OK!] Reading initialized
[OK!] Reading completed
      X torrents imported
      Y torrents skipped

It's not an issue for small dumps, but when they're larger, there's no progress indication. I'd be nice if BitCannon could display a progress indicator, like this:
[OK!] Added torrents: 100/35000
or
[OK!] Added torrents: 23% (ETA: 03:15)
It's not indispensable of course, but I think it'd be good to know.

I've been thinking about this for a while and I wanted to use the go loading bar called pb, but the way I am currently reading files with a scanner, I don't think I can get my progress in the files (how many bytes it has read so far) without totalling up the bytes as it goes along, and even then it would be way off because that would total up the progress in uncompressed bytes and I can only get the size of the compressed gz file.
I really want to add this though, and I hope I'll be able to find some method to do this. I think I would need to find a way to get the size of a gz without uncompressing it, because it reads it while its uncompressing, so I'm pretty sure it only knows the uncompressed size after it's done.

Makes sense, yep. It probably would be easier to add it for uncompressed dumps first, but most people are going to use compressed ones, so...Well, anyway, glad to hear it's being considered, thanks!

Just importing some dailies and thought of this too..

glad to hear it's being considered, thanks!

:D

Of course! Unfortunately I still have to finish some core functions like auto scraping and perhaps category management, but this should be about next.

if you're brave, a public copy of BitCannon

Do you know of any public instances yet? (I'm interested in starting one) I only just got around reading your thread on /r/DataHoarder (used to mod there, started the irc) you should stop by! We're #DataHoarder on Freenode

I think I saw someone put an ip of a public instance in the comments of some article about it, but I think he just wanted people to be able to see what the ui was like. I'm not aware of any public instance that anybody's put out to be used, and I think it would be great if you wanted to make one!
In the interest of making it production ready, I have tried to make all the changes I needed to the database as early as possible, so I hope clearing the database between releases won't be necessary (I haven't changed anything so far, and I'm getting close to the next release).
Let me know if you do make a public instance, perhaps I can put a link somewhere!

Let me know if you do make a public instance, perhaps I can put a link somewhere!

Still playing around but I've spoken to a few people about hosting it, just researching site apis and finding what's available while you bash away making this project ever more sexy!

Tip: I would advise against downloading full backups as files larger than 500mb can take half an hour or more to import even on fast computers

Improving performance is a current issue that is being worked on

What is the limiting factor when importing these files?

Importing is slow and searches have been slowing down because of the addition of sorting by seeders. My benchmarks are as follows:
Importing: 1,000 torrents per second from a gz file - 1:20 for 6.3 million
Page loads: Searches and the browse categories run in roughly 1 second, everything else is instant
Scraping: Currently at 100 torrents per second - ~12 hours for 6 million
My hardware is as follows:
AMD FX-4300 quad at 4 GHz
Apple 120GB SSD
32GB DDR3 Ram
Network: 110Mbit/s or ~12MB/s
It could vary depending on specs and how many torrents you import - After scraping the 6 million torrents from kickass, I found that 75% of the torrents have 0 seeders, so if you were only interested in active torrents, speeds could increase a lot.

I found that 75% of the torrents have 0 seeders, so if you were only interested in active torrents, speeds could increase a lot.

That would make more sense for a hosted instance I think, hmm. But locally I just want to get all the torrents.

I can definitely do this with:
http://stackoverflow.com/questions/24562942/golang-how-do-i-determine-the-number-of-lines-in-a-file-efficiently
1.5 gigs in 5-10 seconds, should be a very bearable pause at the beginning of the import, then I should be able to show a progress bar.


fix(version): update ngx-login-client to 0.6.21

@fabric8cd snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-704.int.rdu2c.fabric8.io


Filetype associations don't affect explorer icons

VSCode Version: 1.10.2
OS Version: Windows 10

Steps to Reproduce:

Set files.associations to include .mak and .Mak files as makefiles
Set workbench.iconTheme to "vs-seti"
Open a folder containing a make file with a name of the form *.mak (e.g., qswlib.mak)
Observe that the generic plain text icon is shown, rather than the "M" makefile icon.

So, in my settings.json I have (among other settings):
"files.associations": {
    "*.mak": "makefile",
    "makefile": "makefile",
    "Makefile": "makefile",
    "*.Mak": "makefile"
},
"[makefile]": {
      "editor.insertSpaces": false
},
"workbench.iconTheme": "vs-seti"

In my current open folder (or directories within that folder) I have several makefiles.
One named "makefile" is correctly detected as a makefile (as shown by the "Makefile" in the status bar), and shows the "M" icon. Tabs are inserted, as expected:

Another, named "qswlib.mak" is also correctly detected as a makefile (as shown by the "Makefile" in the status bar) and tabs are correctly inserted, but the "M" icon is not displayed:

I can reproduce. The user association seems to work when opening files, but the explorer icon doesn't  seem to get the makefile-lang-file-icon rule.

@aeschli isn't this a CSS issue? I do set the classes properly for the label:

It's a seti theme issue. It only associates makefiles with the filename, not the extensions

Fixed

Thanks for the quick fix -- you guys continue to rock!


CEM

Hi, I noticed there are some problems with running CEM.

Here the last index should be 7:
https://github.com/google/trajax/blob/67fd5ed4867914f1ce1ab78819551c12206a7773/trajax/optimizers.py#L753
(similar in random shooting: https://github.com/google/trajax/blob/67fd5ed4867914f1ce1ab78819551c12206a7773/trajax/optimizers.py#L818)

Default hyperparameters should be frozendict
https://github.com/google/trajax/blob/main/trajax/optimizers.py#L685-L692

Would you like a PR for this?
Regards,

Good catch! Feel free to send a PR.

I suspect that I might be having a similar issue with using the cem and random_shooting methods. I receive the error:
Traceback (most recent call last):
  File "XX/trajax/tests/optimizers_test.py", line 850, in testCEM1
    X_opt, U_opt, obj, = optimizers.random_shooting(
  File "XX/trajax/trajax/optimizers.py", line 1160, in random_shooting
    controls = gaussian_samples(random_key, mean, stdev, control_low,
ValueError: Non-hashable static arguments are not supported, as this can lead to unexpected cache-misses. Static argument (index 5) of type <class 'dict'> for function gaussian_samples is non-hashable.

when trying to use random_shooting. I will investigate and make a PR for this, if I can fix it quickly enough.
I'll attach the method that I added to OptimizersTest to demonstrate this behavior.
testCEM1.txt


Question: How to express/support nested JSON objects?

Not really sure if this should be questioned regarding the scope of json api, but we are struggling to find a proper way. It think it is somehow related to this issue on the ember data issue tracker: https://github.com/emberjs/data/issues/53. The discussion is about how ember data would be able to extract/define certain parts of a json payload as other model types then the main resource.
The current json api spec has the "links" key to describe relationships of a resource document, but in json api there is nothing really a way to express the concept of "embedded records". According to @wycats:

... there are really fundamentally two kinds of embedded records

Embedded records that are included with the primary record purely for efficiency. Otherwise, they have their own IDs and can be saved separately.

Embedded records that are conceptually a part of the primary record. They may not have their own IDs and may not be saved separately.

That's the research i have done related to the issue we are trying to resolve, now i will try to explain with an example. We have a very abstract api that allows use to define dynamic properties for a document of certain resource_type. Each of these properties has a meaningful name and also a kind which defines how the value should be interpreted.
The following example is a json api representation without doing anything special with properties. We define a document of rescoure type "foobar_with_addresses_and_places" which has the properties: name (string), my_addresses (collection of address types) and places (another collection of address types but with different meaning because of the the name places).
{
   "resources":[
      {
         "id":1,
         "resource_type":"foobar_with_addresses_and_places",
         "properties":{
            "name":{
               "kind":"string",
               "value":"Foobar"
            },
            "addresses":{
               "kind":"collection",
               "value_type":"address",
               "values":[
                  {
                     "id":1,
                     "street":"Antwerpsesteenweg 5",
                     "city":"Antwerpen",
                     "country":{
                        "code":"BE",
                        "name":"Belgium"
                     },
                     "href":"http://myapi.com/addresses/1"
                  },
                  {
                     "id":2,
                     "street":"Mechelsesteenweg 25",
                     "city":"Mechelen",
                     "country":{
                        "code":"BE",
                        "name":"Belgium"
                     },
                     "href":"http://myapi.com/addresses/2"
                  }
               ]
            },
            "places":{
               "kind":"collection",
               "value_type":"address",
               "values":[
                  {
                     "id":3,
                     "street":"Tisseltsesteenweg 5",
                     "city":"Tisselt",
                     "country":{
                        "code":"BE",
                        "name":"Belgium"
                     },
                     "href":"http://myapi.com/addresses/3"
                  },
                  {
                     "id":4,
                     "street":"Liersesteenweg 25",
                     "city":"Lier",
                     "country":{
                        "code":"BE",
                        "name":"Belgium"
                     },
                     "href":"http://myapi.com/addresses/4"
                  }
               ]
            }
         },
         "links":{}
      }
   ],
   "linked":{},
   "meta":{}
}

The above output to me seems not to be really nice and could be expressed (according to my believe:)) in many other ways. Below is just one of them that would makes the most sense to us. It uses the "link" object definition of the spec to define nested collections in a conform way.
{
   "resources":[
      {
         "id":1,
         "resource_type":"foobar_with_addresses_and_places",
         "properties":{
            "name":"Foobar", // not caring about the kind in this case anymore
            "my_addresses":{
               "ids":[1,2],
               "href":"http://myapi.com/addresses/{id}",
               "type":"addresses"
            },
            "places":{
               "ids":[3,4],
               "href":"http://myapi.com/addresses/{id}",
               "type":"addresses"
            }
         },
         "links":{

         }
      }
   ],
   "linked":{ // maybe this is not the correct section to but them, maybe another name would be better?
      "addresses":[
         {
            "id":1,
            "street":"Antwerpsesteenweg 5",
            "city":"Antwerpen",
            "country":{
               "code":"BE",
               "name":"Belgium"
            },
            "href":"http://myapi.com/addresses/1"
         },
         {
            "id":2,
            "street":"Mechelsesteenweg 25",
            "city":"Mechelen",
            "country":{
               "code":"BE",
               "name":"Belgium"
            },
            "href":"http://myapi.com/addresses/2"
         },
         {
            "id":3,
            "street":"Tisseltsesteenweg 5",
            "city":"Tisselt",
            "country":{
               "code":"BE",
               "name":"Belgium"
            },
            "href":"http://myapi.com/addresses/3"
         },
         {
            "id":4,
            "street":"Liersesteenweg 25",
            "city":"Lier",
            "country":{
               "code":"BE",
               "name":"Belgium"
            },
            "href":"http://myapi.com/addresses/4"
         }
      ]
   },
   "meta":{

   }
}

I can understand that this is really a specific use case and that the spec cannot really cater to this abstractness. But since ember data is going to support some kind of way to define nested objects the json api sepc could come with a recommendation. Any feedback on this is welcome :)

This is now covered under the attributes section of the specification. If this is not sufficient, please create a thread @ http://discuss.jsonapi.org


installed extensions pane only sized for two extensions

VSCode Version: Code - Insiders 1.17.0-insider (5316a2d916b504cc627eb68e119e6b99ea7ad5e5, 2017-10-03T15:39:46.348Z)
OS Version: Windows_NT x64 6.1.7601
Extensions:

Extension
Author (truncated)
Version

vscode-eslint
dba
1.3.2

githistory
don
0.2.3

prettier-vscode
esb
0.24.0

vscode-console-wrapper
fab
0.4.0

debugger-for-chrome
msj
3.3.1

vscode-icons
rob
7.14.0

The "installed extensions" pane is only sized to show two extensions (no matter how many extensions are installed).  It can be manually resized, but upon closing vscode and reopening it will be back to a height that only displays two extensions again.  Not sure what commit changed this, but I believe it was something recent.  I would think it should default to be sized to show all installed extensions, or at least be split half and half with the "recommended extensions" pane.
Steps to Reproduce:

Make sure vscode is completely closed
Open vscode, navigate to the extensions pane, and notice there are only two installed extensions visible
Manually resize the pane to show all installed extensions, and then close vscode
Re-open vscode, navigate to the extensions pane, and notice there are only two installed extensions visible again

Reproduces without extensions: Yes

@joaomoreno I could reproduce this.

Open extensions viewlet

Update the sashes

Close the window

Open new window

See extensions viewlet sashes are not restored

Any idea ?

Sounds like the storage scope is wrong. Did you check that?
https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/browser/parts/views/viewsViewlet.ts#L611

Storage scope is Workspace if Workbench State is not empty otherwise Global. It looks correct to me.

Reproduces with:

Set view size
Hide sidebar
Reload
Show sidebar

Sizes are not restored.


[4.0.0-beta.15] no-margin doesn't work for ion-label in an ion-item-divider

Bug Report
Ionic Info
Ionic:

   Ionic Framework               : @ionic/angular 4.0.0-beta.15

Describe the Bug
After upgrade from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>the CSS utility attribute "no-margin" doesn't work on the ion-label in an ion-item-divider.
Steps to Reproduce
Add
<ion-item-divider color="primary">
 <ion-label no-margin>

Hello World

 </ion-label>
</ion-item-divider>

and the margins will not be removed by no-margin.
Related Code
https://codepen.io/anon/pen/GwJaXd
Expected Behavior
Working sample with<EMAIL_ADDRESS>https://codepen.io/anon/pen/ZmGNMY

Having the same problem inside . Definitely new to beta 15.


added webdriver type function

Motivation/Description of the PR
Adding a type function to Webdriver, when fillField is not a valid option to use.
Applicable helpers:

[x] Webdriver

[ ] Puppeteer

[ ] Nightmare

[ ] REST

[x] Appium

[ ] Protractor

[ ] TestCafe

Resolves #2185

Type of change

[ ] Breaking changes
[x] New functionality
[ ] Bug fix
[x] Documentation changes/updates
[ ] Hot fix
[ ] Markdown files fix - not related to source code

Checklist:

[x] Tests have been added
[x] Documentation has been added (Run npm run docs)
[x] Lint checking (Run npm run lint)
[x] Local tests are passed (Run npm test)

Cool, we will need the same function for other drivers but let's have this one to start!


Introduce optional components

This PR introduces an extra option to cozystack configmap. It allows to enable components that are optional to specific bundle name, example usage:
bundle-enable: telepresence,external-dns,external-secrets-operator

Summary by CodeRabbit

New Features

Added optional attributes to several release entries, allowing for more flexible deployment configurations.
Enhanced Helm release generation logic to consider both enabled and disabled states for components.
Improved namespace management by incorporating checks for optional components based on enablement and disablement.

Bug Fixes

Updated dependencies for external-dns to include cilium and kubeovn.

Documentation

Clarified the configurability of deployment components with the introduction of optional attributes.

In general, some kind of overengineering feature, it is not very clear what it is for, if you can simply disable this or that module within the bundle.

This feature is intended only for optional components, now telepresence, external-dns, external-secrets-operator charts will not be enabled by default.


why is the BLEU score of the translate result  so bad？

I can gain 50.8% accuracy on training set and 40.6% accuracy on validation set with WMT14 ch-en,but the translate result can only gain 1% BLEU score,and i find many sentence have the same beginning words or Phrases.Have you test the BLEU score when you got the model?
[ Epoch 9 ]

(Training)   ppl:  42.43964, accuracy: 50.856 %, elapse: 98.557 min
(Validation) ppl:  33.06820, accuracy: 40.699 %, elapse: 0.026 min

I also found the similar questions...but I didn't know why

What is WMT'14 ch-en? I am not aware of such a data set.

What is WMT'14 ch-en? I am not aware of such a data set.

Sorry,I was wrong,my data set is got from NIST.

@qtxue @GZJAS
I also get the similar problem.
the size of dataset may  cause this phenomenon.

We trained on the standard WMT 2014 English-German dataset consisting of about 4.5 million
sentence pairs

u can find this sentence in Attention Is All You Need.
And, u can download dataset

could i have the code of caculating bleu score part,i have some problem at that,thanks^_^

Sorry for the confusion, I made the beam search now more concise now.
Please take a look on the newest code, Thanks.


PV many-to-many matching bug

Issue seen in a user deployment today.
Context: using external prometheus & ksm. Looks like honor_labels wasn't being picked up at the time.
I1212 23:10:30.865117       1 costmodel.go:1514] Unable to get PV Data: found duplicate series for the match group {namespace="monitoring", persistentvolumeclaim="prometheus-k8s-db-prometheus-k8s-0"} on the left hand-side of the operation: [{namespace="monitoring", persistentvolumeclaim="prometheus-k8s-db-prometheus-k8s-0", storageclass="kube-prometheus", volumename="pvc-cecbfa89-ff84-4697-8526-388f2997cbf6"}, {namespace="monitoring", persistentvolumeclaim="prometheus-k8s-db-prometheus-k8s-0", storageclass="kube-prometheus", volumename="pvc-f8582b29-c5d0-11e9-a1a0-0600db351482"}];many-to-many matching not allowed: matching labels must be unique on one side

Confirmed that this particular issue could break cluster costs...

We were able to successfully recreate after downgrading to ksm v1.5

Added new ksm version check to help users catch and avoid this issue.


haskell-ng: fix naming conflicts between buildDepends and pkgconfigDepends

In (the automatically generated) hackage-packages.nix, some packages won't build because of improper naming of their dependencies.
For example, the gio package is defined as follows:
  "gio" = callPackage
    ({ mkDerivation, array, base, bytestring, containers, glib
     , gtk2hs-buildtools, mtl
     }:
     mkDerivation {
       # (...)
       buildDepends = [ array base bytestring containers glib mtl ];
       buildTools = [ gtk2hs-buildtools ];
       pkgconfigDepends = [ glib ];
       # (...)
     }) { inherit (pkgs) glib;};

Here, the name glib is used in both pkgconfigDepends and buildDepends, which is wrong since the former expects the C library derivation, while the latter expects the haskell package derivation. I guess the intention was to let callPackage look-up the glib haskell derivation, but here it is explicitly fed with pkgs.glib.
There are multiple other impacted packages, but since fixing the hackage-packages.nix generator should fix them all, I won't bother enumerating them :) .

Yes, you are right. This issue is recorded in https://github.com/NixOS/cabal2nix/issues/136 and I'm working on a fix.


Component: Checkbox/Radio

Working on this now!

Updates:

Refactoring Input/HelpText to a dedicated HelpText component. This will allow for better general use with existing components (Input, Select), as well as for Checkbox and Radio
Creating a generic Choice component, which will serve as the skeleton for Checkbox and Radio


Login fixes

Hey @rbelmega,
Something went wrong with the build.
TravisCI finished with status errored, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.
View build log
TravisBuddy Request Identifier: 51642a00-f4a9-11e9-9e2b-01a46d152451


Plugin doesn't working on WebStorm

Describe the bug
Plugin doesn't working on WebStorm
To Reproduce
Steps to reproduce the behavior:

git clone -b grpc https://gitlab.com/wickedev/amki-web
amki-web project open in WebStorm (2019.2.3)
Does not recognize proto file in WebStorm (src/protos/hello.proto)

Expected behavior
Syntax highlighting and autocomplete work in WebStorm as well as IntelliJ
Screenshots
WebStorm 2019.2.3

WebStorm 2019.2.3

IntelliJ 2019.2.2

Plugin (please complete the following information):

OS: Mac
Plugin version: 0.13.0
IDE: WebStorm 2019.2.3

Additional context
React Project
Thanks for your efforts

This issue is closed as plugin is not supported anymore.
Please switch to https://github.com/jvolkman/intellij-protobuf-editor.


Fixed quad stiffness for acoustic case.

Quad stiffness should be fixed for a rotated mesh. Need a mesh to test it...
Also made error check for exact solution much tighter for regression testing.

Indeed:

Dear PETSc 'maint' branch users,
In anticipation of the next 3.7 release of petsc - I've updated
'maint' branch in petsc git repository to 3.7 pre-release changes.
If you 'git pull' on maint branch - you would get these 3.7
pre-release changes.
To stay on 3.6 - you can switch to 'maint-3.6' branch.
git fetch
git checkout maint-3.6
I apologize for any inconvenience this has caused.

http://lists.mcs.anl.gov/pipermail/petsc-announce/2016/000051.html


Ignite-cli Project Installation Error: CommandError: Cannot find module 'ajv/dist/compile/codegen'

Describe the bug
Hello, Was interested in exploring this framework by creating a project and trying it out for myself.
Unfortunately, creating my demo project failed with the following error and I could not find any reference to this issue being raised on GitHub.
CommandError: Cannot find module 'ajv/dist/compile/codegen'
Please see my screenshot below of trying to build my ignite project using the latest code.
Note: I do not have ignite-cli installed in my computer
Doing some digging, i found two articles on a solution.

https://stackoverflow.com/questions/78743456/how-can-i-fix-this-cannot-find-module-ajv-dist-compile-codegen-require-stack
https://github.com/ajv-validator/ajv/issues/2443

But these fixes requires a package.json dependancy fix from ^6 to ^8, which is outside my scope for ignite.
So before I abandon this exploration of ignite, I thought i would post what i experienced and give the community a chance to resolve.
Any suggestions on next steps?
Text of installation and error below
LMIT-MacBook-Air!valor [~/Documents/Projects/my-react-native-studio]>npx ignite-cli@latest new ignite-expo-ble-app
(node:97871) ExperimentalWarning: Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)

:white_check_mark: What bundle identifier? · com.spartanlync.ignite_expo_ble_app
:white_check_mark: Where do you want to start your project?  (Y/n) · Yes
:white_check_mark: Remove demo code? We recommend leaving it in if it's your first time using Ignite (y/N) · No
:white_check_mark: Which package manager do you want to use? · npm
:white_check_mark: Do you want to install dependencies? (Y/n) · Yes
:white_check_mark: [Experimental] Expo Router for navigation? (y/N) · Yes
:white_check_mark: [Experimental] the New Architecture? (y/N) · Yes

                        .;;,.  .clll.
                         .clll,  ,llll.      ...
                          .,;,.   ;lllc'.,.  .';cllllc,
   .',,.                  ...    .'',,. .:lllllllll. .;lllc:;clll,
   .llll,            .,...;cllll:.   ,llll, .llllllc,,'  clll:'.,cllc.
   ,llll'      ......;::. 'llcclllllllll' ,llll,  .llll.  ,lllllllll:'
   ,llll.   .;clllllclll. 'llllc,..,llll, :llll.  'llll.  ,lllc,''..
   ;llll.   :llllc:cllllc. ,llll.  .llll, .lllll.  ,lllc...  ,lll:...';:.
  .llllc.  ;lll;.  :lll,  ;lll;   'llll, .llllc.  ,llllcll' .:lllllllll,
  .llll,  'lll:   .clll,   :lll,   ,llll. 'llll,  'lllllcc'  ';::::;'.
  .llll,  ,lll:  .llll' .llll,   ;llll. ,llll,   .....       .',..
  ,llll. 'llll:,,:cllll. .lllc.   .''.. ... ....',;      ..',,:::;'..
  ,llll.  'clllllllllll.   .....      ..,::cllllc.   .',:clllc;,'.
  :llll.     ',;,'.;lllc...,;:clll; ..',:cllllllllll:,;clllllc;,'.
  llll:       ...'cllllllllllllll::cllllllc;,',cllllllllc;'..
  llll,  ..,clllllllll::,,.,lllllllc:,'...    :lllllc,..
  c:;,. .cllllc:;:llll.   ,ll:;,..        ;ll:,..
       :lll,.  .clll,    ..        .,..
        :lll:,,cllll,
      .cllllllllc'
       .'cllll:.

  █ Creating ignite-expo-ble-app using Ignite 10.0.4
  █ Powered by  ∞ Infinite Red  (https://infinite.red/)
  █ Package Manager: npm
  █ Bundle identifier: com.spartanlync.ignite_expo_ble_app
  █ Path: /Users/valor/Documents/Projects/my-react-native-studio/ignite-expo-ble-app
  ────────────────────────────────────────────────────

  🖨  3D-printing a new React Native app
  :art: Getting those last few details perfect
  :yarn: Installing npm dependencies (wow these are heavy)
  :gear: Configuring app.json
  :x: Generating native template via Expo Prebuild

The following error occurred:

  (node:98427) ExperimentalWarning: Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
(node:98464) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
Git status is dirty but the command will continue because the terminal is not interactive.
Warning: Root-level "expo" object found. Ignoring extra keys in Expo config: "name", "displayName", "ignite"
Learn more: https://expo.fyi/root-expo-object
CommandError: Cannot find module 'ajv/dist/compile/codegen'
Require stack:
- /Users/valor/Documents/Projects/my-react-native-studio/ignite-expo-ble-app/node_modules/ajv-keywords/dist/definitions/typeof.js
- /Users/valor/Documents/Projects/my-react-native-studio/ignite-expo-ble-app/node_modules/ajv-keywords/dist/keywords/typeof.js
- /Users/valor/Documents/Projects/my-react-native-studio/ignite-expo-ble-app/node_modules/ajv-keywords/dist/keywords/index.js
- /Users/valor/Documents/Projects/my-react-native-studio/ignite-expo-ble-app/node_modules/ajv-keywords/dist/index.js
- /Users/valor/Documents/Projects/my-react-native-studio/ignite-expo-ble-app/node_modules/schema-utils/dist/validate.js
- /Users/valor/Documents/Projects/my-react-native-studio/ignite-expo-ble-app/node_modules/schema-utils/dist/index.js
- /Users/valor/Documents/Projects/my-react-native-studio/ignite-expo-ble-app/node_modules/expo-router/plugin/build/index.js
- /Users/valor/Documents/Projects/my-react-native-studio/ignite-expo-ble-app/node_modules/expo-router/app.plugin.js
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>- /Users/valor/Documents/Projects/my-react-native-studio/ignite-expo-ble-app/node_modules/expo/config-plugins.js
- /Users/valor/Documents/Projects/my-react-native-studio/ignite-expo-ble-app/plugins/withSplashScreen.ts
- /Users/valor/Documents/Projects/my-react-native-studio/ignite-expo-ble-app/app.config.ts
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>- /Users/valor/Documents/Projects/my-react-native-studio/ignite-expo-ble-app/node_modules/@expo/cli/build/bin/cli
- /Users/valor/Documents/Projects/my-react-native-studio/ignite-expo-ble-app/node_modules/expo/bin/cli

  Consider opening an issue with the following information at:
  https://github.com/infinitered/ignite/issues/new?template=bug_report.yml&labels=bug

  ⠧  Gathering system and project details  Unable to gather system and project details.

Screenshot of installation and error below

Ignite version
10.0.4
Additional info
LMIT-MacBook-Air!valor [~/Documents/Projects/my-react-native-studio/ignite-expo-ble-app]>npx ignite-cli doctor
(node:9791) ExperimentalWarning: Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
Need to install the following packages:
<EMAIL_ADDRESS>Ok to proceed? (y) y

npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
System
  platform           darwin
  arch               arm64
  cpu                8 cores               Apple M3
  directory          ignite-expo-ble-app   /Users/valor/Documents/Projects/my-react-native-studio/ignite-expo-ble-app
/Users/valor/.npm/_npx/e31027f3785124a8/node_modules/gluegun/build/index.js:15
    throw up;
    ^

SyntaxError: Unexpected token '(', "(node:1013"... is not valid JSON
    at JSON.parse (<anonymous>)
    at /Users/valor/.npm/_npx/e31027f3785124a8/node_modules/ignite-cli/build/tools/packager.js:242:33
    at /Users/valor/.npm/_npx/e31027f3785124a8/node_modules/ignite-cli/build/tools/packager.js:322:54
    at step (/Users/valor/.npm/_npx/e31027f3785124a8/node_modules/ignite-cli/build/tools/packager.js:44:23)
    at Object.next (/Users/valor/.npm/_npx/e31027f3785124a8/node_modules/ignite-cli/build/tools/packager.js:25:53)
    at fulfilled (/Users/valor/.npm/_npx/e31027f3785124a8/node_modules/ignite-cli/build/tools/packager.js:16:58)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)

Node.js v23.0.0

As a quick workaround, if you install ajv as a devDependency in your project, you can force things to work:
npm install --save-dev ajv@^8 --legacy-peer-deps
npm run ios

That worked for me on my reproducer, but it's not really addressing the root issue.

Thanks for the response.
As a newbie, I am still a bit confused as to how to apply your suggestion.
npx ignite-cli@latest new ignite-expo-ble-app
npm run ios

Keep in mind, I only ran one automated command that is supposed to build the boilerplate project
npx ignite-cli@latest new ignite-expo-ble-app
So after one command fails, and I patch the interrupted installation with your suggestion
How do I resume the operation where that one automated command process failed?
Do I just
cd ignite-expo-ble-app
npx ignite-cli@latest new .

Is it supposed to pick up where it left off, with my manually patched package.json?
Please advise.

Yea, I followed my own suggestion.
Unfortunately the project creation did not resume, but failed with another error.
LMIT-MacBook-Air!valor [~/Documents/Projects/my-react-native-studio/ignite-expo-ble-app]>npx ignite-cli@latest new .
(node:20374) ExperimentalWarning: Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)

The project name can only contain alphanumeric characters and underscore, but must not begin with a number.

So this patch / fix somehow needs to be applied to the package.json, BEFORE I can run
npx ignite-cli@latest new ignite-expo-ble-app

Hey @spartanlync - I think I've figured out the issue(s). I was able to reproduce the errors you hit, and resolve them locally. I think there are actually three intersecting bugs. Two of them are from Ignite, and one requires a small adjustment on your side.

In our experimental support for Expo Router, we are encountering some kind of peer dependency problem, as seen in https://github.com/expo/expo/issues/29150.
Your original bundle identifier has some invalid characters in it (I think you posted it in Slack, but not here). I'll provide an alternate suggestion for you, but underscores like _ are invalid characters for bundle identifiers.
We have a few import bugs in the experimental Expo Router support, but they're easy to fix.

That said, here are a series of steps that I believe will fix your issues. I was able to get an Ignite project with your chosen settings running on my own local environment with these steps. We will still want to resolve the peer dependencies and template issues on our end, but hopefully this unblocks you, and anyone else trying to use the experimental support for Expo  Router.
Step by step
First, remove your existing project with rm -rf ignite-expo-ble-app. This will delete files, so if you've done some work, move it to another location instead of deleting so you can pull that work over. I get the sense you haven't made any changes yet, so it's probably easiest to start from a blank slate.
Next, run npx ignite-cli@latest new ignite-expo-ble-app with these options:
✅ What bundle identifier? · com.igniteexpobleapp
✅ Where do you want to start your project?  (Y/n) · Yes
✅ Remove demo code? We recommend leaving it in if it's your first time using Ignite (y/N) · No
✅ Which package manager do you want to use? · npm
✅ Do you want to install dependencies? (Y/n) · Yes
✅ [Experimental] Expo Router for navigation? (y/N) · Yes
✅ [Experimental] the New Architecture? (y/N) · Yes

Notice the updated bundle identifier: com.spartanlync.igniteexpobleapp rather than your original com.spartanlync.ignite_expo_ble_app. I think those underscores were the follow-up issue you ran into. The Ignite CLI will probably promp with com.igniteexpobleapp, which would be suitable as well.
I think the root of your original issue is that there's some kind of peer dependency problem with ESLint and Expo Router. So go into the directory with cd ignite-expo-ble-app. Then run npm install --legacy-peer-deps. This is a bit of a hack, but from what I can tell, it resolves the issue. We will have to address the root cause on our end.
Up next, let's force your project to have the latest version of ajv with npm install --save-dev ajv@^8 --legacy-peer-deps. This will make ajv a direct devDependency in your project, so the resolution will use the appropriate version across all sub-dependencies. Again, this is a hack and we will need to fix the root cause, but hopefully this unblocks you for now.
Finally, we have some issues in our experimental templates. We'll have to update those, but you can fix it in your own project locally. In src/app/_layout.tsx, you'll need to make two changes:

On line 18: change require("src/devtools/ReactotronConfig.ts") to  require("../../app/devtools/ReactotronConfig")
On line 21: change export { ErrorBoundary } from "@/components/ErrorBoundary/ErrorBoundary" to export { ErrorBoundary } from "@/screens/ErrorScreen/ErrorBoundary"

Then you should be able to get the app running, assuming your React Native development environment is correctly set up: https://reactnative.dev/docs/environment-setup. You can run npm run ios or npm run android and things should build and run. Here's a screenshot of it working on my machine:

Let me know if you experience any additional issues. Sorry for the inconvenience. Experimental features often have some sharp edges. We will smooth 'em down!

I think this may be related to what we had to do in https://github.com/infinitered/ignite/issues/2818, but from what I can tell that code hasn't changed or regressed. I'm going to double check to make sure --legacy-peer-deps is getting called from npm with the experimental flags as well.

Ok, so we're definitely calling --legacy-peer-deps as expected. But perhaps the legacy peer dependency resolution works for the initial problem in https://github.com/infinitered/ignite/issues/2818, but breaks this behavior for ajv with ESLint when we choose Expo Router and install with npm.
I think we can just add ajv as a devDependency and smooth this over. I'll put together a PR on that one.

Hey @coolsoftwaretyler, following your suggestions I was successful in getting the demo app running
I don't feel comfortable trusting this project until your suggested patches to

Overriding ajv as a devDependency
Fixing the templates
So that npx ignite-cli@latest new is successful and all post-install tests validate the installation

I will explorer the framework to understand how it works, but will hold off on using it for my next project until it's Expo integration is more stable
Thanks for all your help, and glad i could contribute to a better product

Thanks @spartanlync. Sorry it wasn't a good fit and hopefully you'll consider us again soon.

Closed by #2842

@frankcalise - one more PR before we can close this, I think - gotta fix a template bug:

Finally, we have some issues in our experimental templates. We'll have to update those, but you can fix it in your own project locally. In src/app/_layout.tsx, you'll need to make two changes:
On line 18: change require("src/devtools/ReactotronConfig.ts") to require("../../app/devtools/ReactotronConfig")
On line 21: change export { ErrorBoundary } from "@/components/ErrorBoundary/ErrorBoundary" to export { ErrorBoundary } from "@/screens/ErrorScreen/ErrorBoundary"

I'll send a PR sometime this week or the weekend for that.

 The paths are working. Re-closing! Sorry for the noise.

Hello. So I have abandoned the test project.
Newbie Question?
How will I know (or find out) when your fixes have been released into a new build, so that I can test by regenerating a new test?project?
Thanks for your attention on this matter!

Hey @spartanlync - we have a GitHub releases page that will have information about new releases. You can subscribe to it by "watching" the repository with custom settings.

OK. So I configure watching for #2842 (ajv fix), and future PR's for the template fixes?

I think the template fixes were unnecessary, and my local setup was giving me a false negative. I have been working off the latest branch of Ignite tonight and unable to reproduce.
I think if you configure alerts for the next release, that should be sufficient.

Got it. Thanks


projection

PROJ4 & EPSG projections do not work well when making a map containing an "outline" layer

From what I understand (in https://observablehq.com/@fil/proj4js-d3):

For EPSG:3031, which is centered on the South Pole, things are a bit more complicated, as a direct application breaks a few things (the Sphere, which should be in pale yellow, is not drawn). The reason for this is that, in d3, clipAngle is calculated from the projection’s rotate (in this case, [0,0]), but here we would like it to be calculated from the projection’s center (the South Pole).


Blazor Server - Error on Service Initialization

We are trying to use Blazing.Mvvm on Blazor Server. When registering the service with builder.Services.AddMvvmNavigation(); it throws an exception during build because the AspNetCore.Components.NavigationManager is registered as Scoped instead of a Singleton. Of course we could manually register the MvvmNavigation as Scoped, but what impact would this have? Not sure if your MvvmNavigationManager would operate properly if Scoped.
Getting the following error:
System.AggregateException: 'Some services are not able to be constructed (Error while validating the service descriptor 'ServiceType: Blazing.Mvvm.Components.IMvvmNavigationManager Lifetime: Singleton ImplementationType: Blazing.Mvvm.Components.MvvmNavigationManager': Cannot consume scoped service 'Microsoft.AspNetCore.Components.NavigationManager' from singleton 'Blazing.Mvvm.Components.IMvvmNavigationManager'.)'
Information on how the Default Services are registered:
https://learn.microsoft.com/en-us/aspnet/core/blazor/fundamentals/dependency-injection?view=aspnetcore-7.0

@bbunderson I originally built the library to support WebAssembly (WASM) only for my own use and have shared it with others. With the release of .Net 8.0 imminent, I need to look at supporting the new interactive WebApp project.
You are right about Blazor Server. Scoped does not affect WASM projects. I have made the change and quickly put together a sample ServerSide project. I will release a new Nuget package once I have completed testing. However, for now, if you need early access for your own testing, check out the server branch.

I have found some time this afternoon to add multi-targeting to the Blazing.Mvvm for .Net 7.0 & 8.0RC2 + added a new Auto Blazor WebApp to test out the new Server/WebAssembly framework. You can try it out in the new DotNet8RC2 branch.

We have been prototyping various ways of using the Community Toolkit MVVM. Your library makes everything so elegant and addresses all the issues we have run in to. We are really just using the MvvmComponentBase and ViewModelBase at this time. We are using Blazor FluentUI and so we are not really using the MvvmNavigationManager. Two thumbs up on creating this! Thank you.
I do have a recommendation regarding the registration of service. You could put an option for HostingModel. (This is how Blazor FluetUI handles it.)
builder.Services.AddMvvmNavigation(options =>
{
    options.HostingModel = BlazorHostingModel.Server;
});

@bbunderson Glad that you find it useful.
As for your recommendation, can you create a branch off the  server branch and create a pull request? I am more than happy to look at including it.


Add GeoJS annotation layer for autofilling GeoJSON search field

Resolve #194
requires #182

Merging. This currently supports only searching with one polygon at a time. We can improve in later PRs if desired


proposal: GF designspace wizard

I'm wondering whether we should have a tool which creates designspaces so they're compliant with our spec? Currently, it's a fiddly job which imo we should automate. It should also work on glyphsapp source files.

All in favor!  As far as I remember, this has come out a few times on different meetings, as it would ease the process of e.g. setting bits of info specified from the config file.
Unless you are thinking of something different for the implementation and I'm completely wrong here.