Use clip.exe if exists for copying to Windows clipboard in WSL.

When I select and press y it doesn't leave the selection, is it working for you? I'm using win32yank on NeoVim and it's workinf fine for copy and paste.

This works for me with tmux 2.3 used on Arch Linux in WSL.
Could it be <prefix>+y overwritten by accident? I have the following from the output of my <prefix>+?:
bind-key    -T prefix     y                run-shell -b /home/lukew/.tmux/plugins/tmux-yank/scripts/copy_line.sh

@lukewang1024 wow, just checking alwsl again and since last time I checked they managed to get a nice sponsorship. I plan to switch as soon as I feel it more stable, are you having any instability?
I'll check my command output as soon as I boot Windows again.

@lukewang1024 it works! The issue was this recent merge https://github.com/tmux-plugins/tmux-yank/pull/82#issuecomment-298272754.

@oblitum Basically I use WSL for tmux, zsh, tig & web npm toolchains and alwsl works pretty fine so far. Worth a shot I bet;)

@lukewang1024 just out of curiosity, I've just give it a day to try. It's not for prime time, many issues, for example https://github.com/Microsoft/BashOnWindows/issues/1878 is annoying, I dunno which programs will fail on that, right now locale-gen failed but there was a way out, clang is unusable.


Processing fstab with mount -a failed.

Version
Microsoft Windows [Version 10.0.19045.2311]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Fedora 37
Other Software
Docker Desktop (Windows), version 4.14.1
Repro Steps

Import Fedora

wsl --import Fedora C:\wsl\Fedora .\fedora.tar

Run Fedora

wsl -d Fedora

Expected Behavior
Fedora runs properly giving Zsh prompt.
E.g.:
/mnt/c/Windows/System32>

Actual Behavior
Gives the error message and then the prompt.
E.g.:
Processing fstab with mount -a failed.

/mnt/c/Windows/System32>

Diagnostic Logs
Logs and fedora.tar: https://drive.google.com/drive/folders/194_UR8_V21zvYcfCHkqFL-W6CxYF7rTq?usp=share_link
This error happens only on the store version of WSL.

I added the following to /etc/wsl.conf and the error no longer shows but this just disables fstab instead of solving the problem:
[automount]
mountFsTab=false

I don't use fstab so this works for me.

I have faced the same error this morning while installing it, now I fixed it.
I did import the wrong .tar file that was inside the Fedora Container Base 37.
you should import the one inside it named layer.tar

First unregister your distro

wsl --unregister Fedora

And get the layer.tar

Fedora-Container-Base-37-20221023.n.0.x86_64.tar.xz the downloaded tar file
└📁Fedora-Container-Base-37-20221023.n.0.x86_64.tar
⠀└📂09c9c4cd1e139b8f74d60ce71c9b603e446cf45cb7a5a4841a175cce9a4851d6
⠀⠀└layer.tar get this one
⠀⠀└...
⠀└.....json
⠀└....
⠀└....

Then import it.

Hope this help.

/etc/wsl.conf

Where?

I am having the same problem on ubuntu 22.04 with zsh installed. ubuntu was installed via --import
I didn't get this problem initially. Getting this after a couple of days of setting it up. Not sure why exactly..
How can the /etc/wsl.conf be edited ? Getting permission errors when editing from explorer.

I am having the same problem on ubuntu 22.04 with zsh installed. ubuntu was installed via --import
I didn't get this problem initially. Getting this after a couple of days of setting it up. Not sure why exactly..
How can the /etc/wsl.conf be edited ? Getting permission errors when editing from explorer.

You can edit /etc/wsl.conf from terminal
sudo nano /etc/wsl.conf

But I would advise you to just blank /etc/fstab
sudo nano /etc/fstab

Then delete everything and save. In nano save is Ctrl + O or Ctrl + S and exit is Ctrl + X.

Hi. Not sure if still actual but I have just fixed the issue on my PC. This may come from the fact that you have docker desktop installed like I do. Please run wsl -l -v. If you can see something like

docker-desktop-data
docker-desktop
Fedora

this can cause the issue you had described. I would like to bring to your attention to the asterisk at the docker-desktop-data. This means the default distro. In our case this would be totally wrong. Please run wsl --setdefault Fedora. This worked for me, and I hope this will work for you too.

@alekssmacuks that's it. Thanks!


Foreign key field is not being set when using a nested create for a one-to-one relation

Bug description
Foreign key value is not being set when using a nested create for a one-to-one relation.
How to reproduce

Create the following schema:

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

generator client {
  provider = "prisma-client-js"
}

model Company {
  id       String    @default(cuid()) @id
  payments Payment[]
}

model Visit {
  id      String   @default(cuid()) @id
  payment Payment?
}

model Payment {
  id        String  @default(cuid()) @id
  company   Company @relation(fields: [companyId], references: [id])
  companyId String
  visit     Visit?  @relation(fields: [visitId], references: [id])
  visitId   String?
}

Create a company (need the id for the next step)

Run the following script

const { PrismaClient } = require('@prisma/client')

const prisma = new PrismaClient()

const main = async () => {
  const newVisit = await prisma.visit.create({ data: {} })

  await prisma.visit.update({
    data: {
      payment: {
        create: {
          company: { connect: { id: '{{ company id here }}' }}
        }
      }
    },
    where: { id: newVisit.id }
  })
}

main()
  .then(() => console.log('Done 🎉'))
  .catch(err => console.log(err))
  .finally(() => prisma.disconnect())

Check the database - payment.companyId will be set, however payment.visitId is still NULL, despite the payment being created within a visit update. There's no way to connect that payment to visit, since the nested create does not allow a direct visit connection (since it's part of a visit update).

Without the company connection it works, so it's perhaps something to do with connecting to multiple parents?
Expected behavior
Payments created within an update visit mutation should be connected to the visit.
Environment & setup

OS: Mac OS
Database: PostgreSQL
Prisma version: 2.2.2
Node.js version: 14.5.0

Note also it does work if changed to a one-many relationship, where a visit has many payments.

I can reproduce this with 2.4.0-dev.14

@divyenduz Just hit this again in another situation.  Any chance of a fix anytime soon?

@jwld Thanks for raising this. It is marked as a candidate so it might get picked up soon.

Appreciate the response, thanks!

Have hit this in a third situation, so still an issue in 2.8. As usual it requires some funky workarounds. Apologies for spamming but just to indicate that this is quite a pervasive issue for us.

A fix will be available in version 2.11.


Please provide a UMD export type

Hello, it would be great if you add support for UMD export types, currently only CJS and ESM exist in the core library this prevents anyone from using the library via a CDN

We will support it in the next version.


[Bug] Unable to use extensions

Hi. First, thank you for your great work on this package.
I'm trying to use codemirror extensions but almos all of them results in the same error in the console:
Error: Unrecognized extension value in extension set ([object Object]). This sometimes happens because multiple instances of @codemirror/state are loaded, breaking instanceof checks.
I tried uninstalling the @codemirror/state or updating to its last version but none of that worked.
To reproduce just try to add the @codemirror/history extension to the bare bones example.

Did you call @codemirror/basic-setup for the extension? In that case, it is not necessary because it is included.
Also, @codemirror/history seems to have been migrated to @codemirror/commands because the repository is locked. Please change to this and try.

It's true, but even using just basic-setup, that has both history and its keymap, I can't undo anything :(
OBS: I'm using the full example and version 0.3.5

The search popup that appears with CTRL + F is working, so it's not immediately clear why only history doesn't work.
It may be interfering with some processing on the vue side, and it seems that it will take time to isolate the problem.

It was solved in 0.3.6 and 0.1.6.
From this version, load basic-setup with basic prop.
<code-mirror v-model="text" basic />

In 0.6.0 or later, @codemirror/basic-setup is no longer needed.
If it is included in the package of the project you are using, it may not work properly. Please remove the package.

I have same problem with `"vue-codemirror6": "^1.3.2"`

I have same problem with "vue-codemirror6": "^1.3.2"

I saved.
delete node_modules,pnpm-lock.yaml and reinstall ,its work


fix: Resolve issues with offline linter + add tests

https://github.com/argoproj/argo-workflows/pull/10059 was tested in very specific cases it seems (sorry about that 😬), because a couple things are wrong:

Linting directories does not work anymore
Resolving references in a namespace which doesn't show up in the given args, panics

In this PR, I fix those issues but I also add functional tests that checks that all of these cases work from the cmd level
I did not add to the argo/lint/lint_test.go tests and instead put the tests earlier down the line because the current tests do not cover the creation and configuration of the offline client (which is the part that is failing here, the actual linter was not modified in the PR above)

[x] Create the PR as draft .
[x] Run make pre-commit -B to fix codegen and lint problems.
[x] Sign-off your commits (otherwise the DCO check will fail).

[x] "Fixes #" is in both the PR title (for release notes) and this description (to automatically link and close the issue).
[x] Add unit or e2e tests. Say how you tested your changes. If you changed the UI, attach screenshots.
[x] Github checks are green.
[x] Once required tests have passed, mark your PR "Ready for review".

Thanks for merging @alexec.
FYI, I have now been able to test this internally (we use a combination of CronWorkflows, WorkflowTemplates and ClusterWorkflowTemplates, with refs between each other) and have not seen any errors. We will start using it in our CI pipeline very soon.


A11y: Info link next to date format dropdown has invalid UIA name

Describe the bug
The info link next to the date format dropdown on the appearance page has an invalid UIA name (single unicode character in the private UTF space). Instead it should have an appropriate UIA name describing it's purpose.
To Reproduce
Steps to reproduce the behavior:

Open appearence on settings page
Visit info link next to date format with narrator
Observe announcement: ""

Expected behavior
UIA name should be descriptive.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Insider Build 10.0.20262 Build 20262
App version: <IP_ADDRESS>

This issue should be resolved with #2574.


Population terminalGateGid is undefined

https://github.com/primitybio/cellengine-python-toolkit/blob/c12ab312448c833a5274945f6d2cfacc6ced3666/cellengine/payloads/population.py#L22
should be terminalGateGid with a G

Whoops, typo

Whoops, typo


Ignition config example from documentation makes a service fail

I am currently fighting my way through CoreOS's sometimes broken documentation and this trouble made me waste yet another 2h of my time. Maybe I can spend a few more minutes to help somebody else save this time.
Basically, check these out:
https://coreos.com/blog/introducing-ignition.html
https://github.com/coreos/ignition/blob/master/doc/examples.md
Both of them have an example with a systemd unit config:
[Unit]\nConditionFirstBoot=yes\n\n[Service]\nType=oneshot\nExecStart=/usr/bin/unzip /home/core/coreos_production_image_pcr_policy.zip -d /home/core\n\n[Install]\nWantedBy=multi-user.target
Unfortunatelly, the '\n' symbols make systemd fail the service with an error message: "Invalid section header". If you simply specify the config as follows (removing the \n's), the service starts without a hiccup:
[Unit]
ConditionFirstBoot=yes

[Service]
Type=oneshot
ExecStart=/usr/bin/unzip /home/core/coreos_production_image_pcr_policy.zip -d /home/core

[Install]
WantedBy=multi-user.target

Please fix the docs.
Thanks,
Simon

Newline literals are not valid JSON. The blog post you are referring to is demonstrating how to use Ignition. I get the sense that you are not actually using this tool directly. How are you creating these unit files?
The documentation for Ignition: https://coreos.com/ignition

Yeah, you were right. I used single quotes in a PHP script to generate the config. Of course it put literal \n in the string...

https://coreos.com/validate/ is a great tool for validating the output of your PHP scripts.


Syntax error for (

I get a syntax error for ( in ordinary text:
\section{Structure of this work}
\label{sec:structure}
abc (asf) sf
    ^

The pdf renders right so I think this should not be an issue. Note that I'm using UTF-8 in my latex sources (and also configured latex correspondingly).

I think this issue duplicates  #14 . If this is fixed already, this issue can be closed.


daedalus: emit errors to stderr rather than stdout

This is aimed at making daedalus a bit easier to use in shell scripting contexts.

Okay, great. How about I open a ticket to do an audit for that?


Make Export of statistics/annotations more responsive

Currently on a large source, you'd click one of the buttons on the export page, and your browser would start spinning as it waited for the request to finish. For a decent amount of data, it takes long enough that you could grab a cup of coffee and a snack (as the page used to say). I imagine there are also sources where you'd wait until you woke up the next morning. All the while, the browser tab is still spinning and there is no indication of when it'll finish.

[ ] The export request should be an Ajax request, so that the browser window doesn't say "waiting for response..." the entire time.
[ ] There should be a progress indicator on the page, perhaps based on number of images processed. A text percentage at minimum; preferably a progress bar too.
[x] See if we can speed up the export functions. I'd start by checking the number of database queries involved. (PR #581)

Seems with the move to the image browse page we no longer warn users the export might take a long time. I think we need to add that back in.

Well, the warning's hidden away in the '?' button. But yeah, it should be more prominent again.

[ ] See if we can speed up the export functions. I'd start by checking the number of database queries involved.

Significant speedup achieved in PR #581, so I decided we can check off this item unless indicated otherwise by future observations.


versitygw: init at 1.0.8

Closes https://github.com/NixOS/nixpkgs/issues/355253
Add versitygw to nixpkgs, an s3 gateway.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@Aleksanaa Did a rebase wrong and messed up the other branch, here is the new one with all the changes

@ofborg build versitygw


Add MultiSelect.size

@jsignell The PR I promised. I'll merge this pretty much immediately but there's a few more PRs I want to finish off before tagging 0.2.0a7.

Codecov Report

Merging #149 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #149      +/-   ##
==========================================
+ Coverage   90.02%   90.02%   +<.01%
==========================================
  Files          30       30
  Lines        4472     4473       +1
==========================================
+ Hits         4026     4027       +1
  Misses        446      446

Impacted Files
Coverage Δ

panel/widgets.py
97.61% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


brew install fails on macos-latest runner

Describe the bug
The brew install command fails on the macos-latest github-hosted runner:
==> Upgrading<EMAIL_ADDRESS>  3.10.8 -> 3.10.9

==> Pouring<EMAIL_ADDRESS>Error: The `brew link` step did not complete successfully
The formula built, but is not symlinked into /usr/local
Could not symlink bin/2to3
Target /usr/local/bin/2to3
already exists. You may want to remove it:
  rm '/usr/local/bin/2to3'

To force the link and overwrite all conflicting files:
  brew link --overwrite<EMAIL_ADDRESS>
To list all files that would be deleted:
  brew link --overwrite --dry-run<EMAIL_ADDRESS>
Possible conflicting files are:
/usr/local/bin/2to3 -> /Library/Frameworks/Python.framework/Versions/3.11/bin/2to3
/usr/local/bin/idle3 -> /Library/Frameworks/Python.framework/Versions/3.11/bin/idle3
/usr/local/bin/pydoc3 -> /Library/Frameworks/Python.framework/Versions/3.11/bin/pydoc3
/usr/local/bin/python3 -> /Library/Frameworks/Python.framework/Versions/3.11/bin/python3
/usr/local/bin/python3-config -> /Library/Frameworks/Python.framework/Versions/3.11/bin/python3-config

See this log for an example:
https://github.com/jbms/sphinx-immaterial/actions/runs/3820568912/jobs/6499217543
Skipping brew update seems to fix the problem.

@all-contributors please add @jbms  for bug, idea.

@jbms
Released in v1.2.0 with additional functionality to correct this issue.
Thnaks!

@dhimmel This problem is not resolved by the default behavior.
The macos-skip-brew-update flag must be set to true.
- name: Setup Graphviz
  uses: ts-graphviz/setup-graphviz@v1
  with:
    # Skip to run brew update command on macOS.
    macos-skip-brew-update: 'true' # defalt false

@dhimmel
I created a PullRequest so that others can see how to fix it :+1:
https://github.com/related-sciences/nxontology/pull/24

@all-contributors please add @dhimmel  for question.


Add toolbar position persistence

cool!

Has it been removed from current version ?

@AnthoPakPak It shouldn't be, did you find any issues on the current version?

@matrush Oh, indeed I was getting Flex through Cocoapods, and copy/paste the line in the Readme
pod 'FLEX', '~> 2.0', :configurations => ['Debug']
but it seems that the current version is 2.4, so I think this version will have this code included :)


#271 Use event references in VoidHook and OnAwakeHook

This commit adds the possibility to trigger mono hook events from an instaniater

The belonging issue is #271

Sorry, had to revert this pull request because it's a breaking change and belongs to v5. Could you open a new pull request targeting the v5 branch?

Sure, I've created a new PR #288  for v5


Possible to add support for metric units?

I have been interested in using this add-on for my Symbaroum campaign, however most maps are measured in meters in that system. Typically PCs can move 10m, and each square is 2x2m. Any way you could add metric support, or a way for users to manually adjust the name of units and unit distance per square? Thanks!

You can do this by going to the Scene Configuration, in the Grid tab. Look for Grid Scale: distance and units. You might also want to go to the Elevation Ruler settings and change the "Round Distance to Multiple" to something other than 0.


Replaced reference from V3 to AProtocol

In future PHP Bolt library will change protocol classes and it won't be using chain of responsibility anymore. Each protocol version class won't be extending the previous one. It will change because changes between versions are not consistent. Therefore this php client needs to be prepared for this change.
I updated version check in the code with fn version_compare.

Just doing a cursory glance at the lint tests: it starts to complain about undefined methods. It shouldn't be a big deal. We need to typehint the protocol in phpdoc as V3|V4|V4_1|V4_2|V4_3|V4_4 before it stops yelling at us. Looks like you didn't actually break anything! :tada:

Your Lint doesn't like it.

If interface reference will be used instead of abstract class will lint still complain about missing methods?

Yes, if the methods aren't defined, it will. Psalm is really strict

There are two complaints from Psalm I cannot solve until the actual new version is implemented.
Consider this PR a draft until the new Bolt version has been released


helmDefaults.kubeContext ignored

Seems that a regression in v0.70.0 is causing helmDefaults.kubeContext to be ignored and is always using the current k8s cluster.
repositories:
  - name: incubator
    url: https://kubernetes-charts-incubator.storage.googleapis.com
  - name: weaveworks
    url: https://weaveworks.github.io/flux
  - name: bitnami
    url: https://charts.bitnami.com

environments:
  shared:
    values:
      - ../../env/cluster/shared.yaml

helmDefaults:
  kubeContext: arn:aws:eks:eu-west-1:1234:cluster/foo
  tls: true
  tillerNamespace: kube-system

An invalid kubeContext does not cause any issues. Switching context manually through kubectl config use-context hides the issue.

@michaelgeorgeattard Thanks for reporting!
Unforunately I'm unable to reproduce this with both the latest and v0.70.0:
$ tail -n100 *
==> helmfile.yaml <==
helmDefaults:
  kubeContext: arn:aws:eks:eu-west-1:1234:cluster/foo
  tls: true
  tillerNamespace: kube-system

environments:
  shared:
    values:
      - shared.yaml

releases:
- name: podinfo
  chart: sp/podinfo

==> shared.yaml <==

$ helmfile -e shared diff
Comparing podinfo sp/podinfo
in ./helmfile.yaml: failed processing release podinfo: helm exited with status 1:
  Error: could not get Kubernetes config for context "arn:aws:eks:eu-west-1:1234:cluster/foo": context "arn:aws:eks:eu-west-1:1234:cluster/foo" does not exist

$ helmfile-v0.70.0 -e shared diff
Comparing podinfo sp/podinfo

in ./helmfile.yaml: failed processing release podinfo: helm exited with status 1:
  Error: could not get Kubernetes config for context "arn:aws:eks:eu-west-1:1234:cluster/foo": context "arn:aws:eks:eu-west-1:1234:cluster/foo" does not exist

Do you have any idea how I can reproduce it?

@michaelgeorgeattard Do you have tillerless: true set for your releases? In that case the issue would be #642

@mumoshu No I do not have tillerless: true set.
Diff fails correctly, however helmfile --interactive apply always works and ignores kubeContext.
$ helmfile --version
helmfile version v0.75.0

$ cat helmfile.yaml
repositories:
  - name: weaveworks
    url: https://weaveworks.github.io/flux

helmDefaults:
  kubeContext: random_123$
  tls: true

releases:
  - name: flux
    chart: weaveworks/flux
    version: 0.9.5
    namespace: management
    values:
      - helmOperator:
          create: true
          createCRD: true
          tls:
            secretName: "helm-client-certs"
            verify: false
            enable: true
            keyFile: "tillerkey"
            certFile: "tiller"

$ helmfile --interactive diff
Adding repo weaveworks https://weaveworks.github.io/flux
"weaveworks" has been added to your repositories

Updating repo
Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
...Successfully got an update from the "weaveworks" chart repository
...Successfully got an update from the "incubator" chart repository
...Successfully got an update from the "rig" chart repository
...Successfully got an update from the "stable" chart repository
...Successfully got an update from the "bitnami" chart repository
Update Complete.

Comparing flux weaveworks/flux
in ./helmfile.yaml: failed processing release flux: helm exited with status 1:
  Error: could not get Kubernetes config for context "random_123$": context "random_123$" does not exist

$ helmfile --interactive apply

ALWAYS WORKS

@michaelgeorgeattard Thanks for the additional info!
I think I've spotted it - On my machine helm diff is missing --kube-context flag only when it is run as a part of helmfile apply. helm diff run by helmfile diff and helm upgrade run by helmfile apply regardless of --interactive seems to have correct --kube-context provided.
Would it be the case for you as well?
I'd appreciate it if you could run helmfile like helmfile --log-level=debug to see actual helm commands it's running.

@mumoshu Thank you for helping me debug this issue :-)
Indeed helmfile apply seems to be missing --kube-context argument when calling helm diff upgrade:
$ helmfile --log-level=debug diff
processing file "helmfile.yaml" in directory "."
first-pass rendering starting for "helmfile.yaml.part.0": inherited=&{default map[] map[]}, overrode=<nil>
first-pass uses: &{default map[] map[]}
first-pass produced: &{default map[] map[]}
first-pass rendering result of "helmfile.yaml.part.0": {default map[] map[]}
vals:
map[]
defaultVals:[]
second-pass rendering result of "helmfile.yaml.part.0":
 0: repositories:
 1:   - name: weaveworks
 2:     url: https://weaveworks.github.io/flux
 3:
 4: helmDefaults:
 5:   kubeContext: random_123$
 6:   tls: true
 7:
 8: releases:
 9:   - name: flux
10:     chart: weaveworks/flux
11:     version: 0.9.5
12:     namespace: management
13:     values:
14:       - helmOperator:
15:           create: true
16:           createCRD: true
17:           tls:
18:             secretName: "helm-client-certs"
19:             verify: false
20:             enable: true
21:             keyFile: "tillerkey"
22:             certFile: "tiller"

merged environment: &{default map[] map[]}
Adding repo weaveworks https://weaveworks.github.io/flux
exec: helm repo add weaveworks https://weaveworks.github.io/flux
exec: helm repo add weaveworks https://weaveworks.github.io/flux: "weaveworks" has been added to your repositories

"weaveworks" has been added to your repositories

Updating repo
exec: helm repo update
exec: helm repo update: Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
...Successfully got an update from the "weaveworks" chart repository
...Successfully got an update from the "incubator" chart repository
...Successfully got an update from the "rig" chart repository
...Successfully got an update from the "stable" chart repository
...Successfully got an update from the "bitnami" chart repository
Update Complete.

Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
...Successfully got an update from the "weaveworks" chart repository
...Successfully got an update from the "incubator" chart repository
...Successfully got an update from the "rig" chart repository
...Successfully got an update from the "stable" chart repository
...Successfully got an update from the "bitnami" chart repository
Update Complete.

worker 1/1 started
worker 1/1 finished
worker 1/1 started
Comparing flux weaveworks/flux
exec: helm diff upgrade --allow-unreleased flux weaveworks/flux --version 0.9.5 --tls --namespace management --values /tmp/values680979826 --kube-context=random_123$
exec: helm diff upgrade --allow-unreleased flux weaveworks/flux --version 0.9.5 --tls --namespace management --values /tmp/values680979826 --kube-context=random_123$:
worker 1/1 finished
err: release "flux" in "helmfile.yaml" failed: failed processing release flux: helm exited with status 1:
  Error: could not get Kubernetes config for context "random_123$": context "random_123$" does not exist
in ./helmfile.yaml: failed processing release flux: helm exited with status 1:
  Error: could not get Kubernetes config for context "random_123$": context "random_123$" does not exist

$ helmfile --log-level=debug --interactive apply
processing file "helmfile.yaml" in directory "."
first-pass rendering starting for "helmfile.yaml.part.0": inherited=&{default map[] map[]}, overrode=<nil>
first-pass uses: &{default map[] map[]}
first-pass produced: &{default map[] map[]}
first-pass rendering result of "helmfile.yaml.part.0": {default map[] map[]}
vals:
map[]
defaultVals:[]
second-pass rendering result of "helmfile.yaml.part.0":
 0: repositories:
 1:   - name: weaveworks
 2:     url: https://weaveworks.github.io/flux
 3:
 4: helmDefaults:
 5:   kubeContext: random_123$
 6:   tls: true
 7:
 8: releases:
 9:   - name: flux
10:     chart: weaveworks/flux
11:     version: 0.9.5
12:     namespace: management
13:     values:
14:       - helmOperator:
15:           create: true
16:           createCRD: true
17:           tls:
18:             secretName: "helm-client-certs"
19:             verify: false
20:             enable: true
21:             keyFile: "tillerkey"
22:             certFile: "tiller"

merged environment: &{default map[] map[]}
Adding repo weaveworks https://weaveworks.github.io/flux
exec: helm repo add weaveworks https://weaveworks.github.io/flux
exec: helm repo add weaveworks https://weaveworks.github.io/flux: "weaveworks" has been added to your repositories

"weaveworks" has been added to your repositories

Updating repo
exec: helm repo update
exec: helm repo update: Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
...Successfully got an update from the "weaveworks" chart repository
...Successfully got an update from the "incubator" chart repository
...Successfully got an update from the "rig" chart repository
...Successfully got an update from the "stable" chart repository
...Successfully got an update from the "bitnami" chart repository
Update Complete.

Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
...Successfully got an update from the "weaveworks" chart repository
...Successfully got an update from the "incubator" chart repository
...Successfully got an update from the "rig" chart repository
...Successfully got an update from the "stable" chart repository
...Successfully got an update from the "bitnami" chart repository
Update Complete.

worker 1/1 started
worker 1/1 finished
worker 1/1 started
Comparing flux weaveworks/flux
exec: helm diff upgrade --allow-unreleased flux weaveworks/flux --version 0.9.5 --tls --namespace management --values /tmp/values621735097 --detailed-exitcode
exec: helm diff upgrade --allow-unreleased flux weaveworks/flux --version 0.9.5 --tls --namespace management --values /tmp/values621735097 --detailed-exitcode:

DIFF IS SHOWN HERE

@michaelgeorgeattard Thanks! #682 will fix that.


Fix errors in zigbee push state

Description:
This PR fixes two separate issues when using the zigbee component.
Issue 1
When the XBee is configured to broadcast samples (i.e. Sampling Rate > 0), you get the following errors in the HA log on a routine basis:
Dec 30 14:22:14 hal hass[7184]: Traceback (most recent call last):
Dec 30 14:22:14 hal hass[7184]:   File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run
Dec 30 14:22:14 hal hass[7184]:     result = self.fn(*self.args, **self.kwargs)
Dec 30 14:22:14 hal hass[7184]:   File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/zigbee.py", line 296, in handle_frame
Dec 30 14:22:14 hal hass[7184]:     self._state = self._config.state2bool[sample[pin_name]]
Dec 30 14:22:14 hal hass[7184]: KeyError: False

The issue is sample[pin_name]] is a Boolean (indicating the state of the pin), but self._config.state2bool is a dict keyed by state (a pin state obj). The solution is to convert the state to its matching Boolean before lookup.
Issue 2
When using more than one pin on a single XBee, and that XBee is configured to broadcast samples (i.e. Sampling Rate > 0), you get the following errors in the HA log on a routine basis:
Dec 30 14:22:14 hal hass[7184]: Traceback (most recent call last):
Dec 30 14:22:14 hal hass[7184]:   File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run
Dec 30 14:22:14 hal hass[7184]:     result = self.fn(*self.args, **self.kwargs)
Dec 30 14:22:14 hal hass[7184]:   File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/zigbee.py", line 291, in handle_frame
Dec 30 14:22:14 hal hass[7184]:     sample = frame['samples'].pop()

The issue is the list pop() done on zigbee:py:291 removes the samples from the frame. When the dispatcher runs that code block for the next pin, samples is empty, causing the error. The solution is to not pop().
Example entry for configuration.yaml:
zigbee:
  device: /dev/ttyUSB0
  baud: 9600

switch:
  - name: Example 1
    platform: zigbee
    pin: 1
    address: 0013A2004150F5AC
    on_state: high
  - name: Example 2
    platform: zigbee
    pin: 2
    address: 0013A2004150F5AC
    on_state: high

Checklist:
If the code communicates with devices, web services, or third-party tools:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass

Hi @SteveEasley,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!


Is this added to the template configuration file?

Yes, you need to add this node to the private template. When importing a project, you need to check whether the corresponding Zipkin package has been imported. Service a and service B need to have the corresponding Zipkin opened and imported. After reporting, you can see the specific data.
Java = > java can be used. Other mixed language calls are temporarily unknown.

是的，在私有模板里面要加上这个节点，项目引入的时候，要察看是否已经 引入对应的zipkin包，服务A、服务B都要有对应的zipkin的开启和引入，上报后就可以看得到具体的数据了。
java =>java的可以，其他的语言混合调用暂时未知。


Add workflow to update version in README

In #94, the ASFHyP3/actions version number used in the README examples was bumped to the next expected version, but that version has not yet been released, so none of the examples in the default branch's README currently work.
A similar issue occurs when we release and then don't circle back to update the example version, causing our examples to lag behind the latest release.
We can "fix" this by more rapidly releasing, but either way, there's a manual version update step that is annoying.
This adds a GitHub Action workflow to change all the examples in the README to use the latest version tag anytime a new tag is pushed.
I've used the sed command in this action to reset the version numbers in the README to the current release version so we can watch it in action.

Technically, the README for the specific tag will still always be 1 version behind, but since we don't typically know the version number until the release PR, this is the simplest way to automatically keep the default branch's README,  which is the default docs, up to date
We could trigger this workflow instead on PRs to main and use bump2version like in our release workflow to predict the next version based on the PR labels, but we'd (1) have to push directly to develop and (2) handle label changes.
All of which is manageable but seems more complicated than necessary...

Sounds good. Yeah I don't think being on tag behind is that big of a deal.


bug: keyboardActiveElement is undefined if keyboard started from an input inside a popup

Greetings @gabrielmuresan!
My sensors indicate that you need to update your issue through our custom issue form. We are now requiring all issues to be submitted this way, to ensure that we have all of the information necessary to fix them as quickly as possible.
Click Here To Update Your Issue
I will have no choice but to close this issue if it is not resubmitted through the form. Please fill out the rest of the form, so that I may use my friendly robot powers to assist you.
Thank you!

Dup of https://github.com/driftyco/ionic/issues/3586.


Extensions adding characters to beginning of name to manipulate store ranking

The Addons Catalog sorts extension listings by alphabetizing the name of the extension. Some extension authors have decided to take advantage of this by adding characters like !, *, and + to the front of their extension names so that they are put at the top of the extension store.

Examples
The first two rows of the extension store have some pretty obvious examples of this:

Edge Name
Chrome Name
Firefox Name

! 1 Chat for Every Website: Relay
Relay: Chat on Every Website
Relay: Chat on Every Website

! Global Speed (Youtube, Netflix, etc)
Global Speed (Youtube, Netflix, Reddit, etc)
Global Speed (Youtube, Netflix, Reddit, etc)

! Live Hero
Live Hero
Live Hero

The Microsoft Edge Addons Catalog Developer Policies state:

You must not attempt to cheat users, the system or the ecosystem. There is no place in our Microsoft Edge Addons for any kind of fraud; be it ratings and review manipulation, credit card fraud or other fraudulent activity.

Ranking manipulation clearly is a violation of this principle. I believe that Microsoft should add a policy disallowing this behavior.

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

ID: a7819ec4-6bf9-b550-431b-07e5f7692150
Version Independent ID: e3493b50-4f7a-b3a8-465a-6d494fecb3e0
Content: Microsoft Edge Addons Catalog Developer Policies - Microsoft Edge Development
Content Source: microsoft-edge/extensions-chromium/store-policies/developer-policies.md
Product: microsoft-edge-chromium
GitHub Login: @MSEdgeTeam
Microsoft Alias: msedgedevrel

Looks like the sorting method has been changed.


[DO-NOT-MERGE]spring-cloud: add support to enable/disable MSI (#1523)

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

hi @leonard520 is there any change between this PR with previous PR? that one was reviewed and approved already

hi @leonard520 is there any change between this PR with previous PR? that one was reviewed and approved already

They are the same except I raise the version number to 0.2.4 in this one

thanks for clarification. Then just ping us when the PR is ready to merge, thanks. @leonard520

@yungezz @fengzhou-msft The backend is ready. Please help to merge the code. Thanks!

Could you please add a brief description for this PR and link the previous same PR that is reviewed?

#1671 https://github.com/Azure/azure-cli-extensions/pull/1523

/azp run

/azp run


[FEATURE] Mirror IDF and ADDF repos to China Gitee

Is your feature request related to a problem? Please describe.
Our largest customers are very active in China. Unfortunately, public github is completely blocked in China. Therefore they cannot git reference modules from awslabs github even though they would like to. They are trying to figure out how to leverage Seedfarmer modules in China and considering complicated solutions like self mirroring etc.
Describe the solution you'd like
I would like awslabs to maintain a mirror of idf-modules and addf-modules in China's public github (https://gitee.com/oschina). Basically when the IDF team cuts a release to github, they can additionally cut a release to Gitee or another chinese git provider, and make it accessible to seedfarmer projects in China.
Describe alternatives you've considered
Self-managed mirrors from public github
Additional context
Add any other context or screenshots about the feature request here.

We have not found this to be viable


Plots return "invalid quartz() device size" when initially rendered

When the UMAP plot loads for the first time on startup, the following error is returned: invalid quartz() device size. When the app is hosted on shinyapps.io, this error displays as Error in <Anonymous>: invalid 'width' argument.

This has no longer been observed with the plots in tabs we're planning to keep in the app.


Unable to pan past the antimeridian

The main Leaflet map doesn’t let you pan east or west past the antimeridian, unless you pan far enough that it jumps all the way to the other hemisphere. This makes it awkward to view Alaska, particularly the Aleutians.
It looks like we explicitly disable panning beyond ±180 degrees longitude as part of a fix for misaligned terrain when panning beyond ±90 degrees latitude. Or maybe that’s about the element geometry being overlaid on the map?
https://github.com/OpenHistoricalMap/ohm-website/blob/025da9c6975ef7128d9998334431f6667de11f0b/app/assets/javascripts/index.js#L37
Overpass turbo doesn’t have this option set, but I haven’t seen any issues with misaligned layers there.

I believe this was a side effect of this issue, https://github.com/OpenHistoricalMap/issues/issues/353, but maybe there's a better way to solve the problem in that old ticket than we figured out in 2022

If we think that issue is caused by Leaflet, we might want to follow up in Leaflet’s issue tracker. Regardless, limiting the latitude is a good idea; we just don’t really need to limit the longitude. Setting the maxBounds to [[-90, -360], [90, 360]] should do the trick, allowing you to pan freely horizontally but not vertically.


ElastiCache Cluster CRD does not create a K8s secret

What happened?

When creating a CacheCluster CRD for redis, no kubernetes secret is created containing the details required for establishing a connection to redis, e.g.
endpoint url
port
authtoken or username+password

Refer to the bug which is there in community edition
https://github.com/crossplane-contrib/provider-aws/issues/551
How can we reproduce it?

---
apiVersion: elasticache.aws.upbound.io/v1beta1
kind: Cluster
metadata:
  name: "test-cache-cluster"
spec:
  forProvider:
    region: us-east-1
    tags:
      Application: TEST-UM
      Group: QA
      Environment: QA
    engine: redis
    nodeType: cache.t2.micro
    numCacheNodes: 1
    parameterGroupNameRef:
      name: "test-cache-param-grp-1"
    subnetGroupNameRef:
      name: "test-cache-sn-grp1"
    securityGroupIds:
    - sg-004209965c448fbe3
  providerConfigRef:
    name: qa-proconf

  writeConnectionSecretToRef:
    name: cache-cluster-qa-redis-secret
    namespace: test

# k get -n test secret cache-cluster-qa-redis-secret

NAME                             TYPE                                DATA   AGE
cache-cluster-qa-redis-secret   connection.crossplane.io/v1alpha1   0      30h

What environment did it happen in?

Universal Crossplane Version: 1.10.1

Provider Version: provider-aws:v0.20.0

Kubernetes version : Server Version: version.Info{Major:"1", Minor:"24+", GitVersion:"v1.24.7-eks-fb459a0", GitCommit:"c240013134c03a740781ffa1436ba2688b50b494", GitTreeState:"clean", BuildDate:"2022-10-24T20:36:26Z", GoVersion:"go1.18.7", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes distribution : AWS EKS

I am seeing this issue as well, any update here?

@aiell0, you can add additional sensitive fields to config/elasticache/config.go, and open a PR. We can evaluate the fields you want on the PR.
For more details: Additional Sensitive Fields and Custom Connection Details

this is implemented with: https://github.com/crossplane-contrib/provider-upjet-aws/pull/1322


Config for text values + formatting

hello could you add text editing to the config for possible translations and changing the color of the text?

that is already planned in CodedSMPUtils, and i don't think i'll be updating FabricTPA more than bugfixes for now
will leave this issue open though

what is codedsmputils .. is it a future mod including tpa, warp, pvp and homes?

yep, it is. i'm slowly making progess on it, but i have prostponed it for the last month as uni exams are nearing...
the repo for it is https://github.com/CodedSakura/CodedSMPUtils, and you can follow progess in my Discord server https://discord.gg/BkKG6nx6rG


Adds RackHD Web UI section to User Guide

So far it only explains how to configure api endpoint setting, and provides links.

@heckj @benbp @DavidjohnBlodgett @tldavies

I think this addresses #174

:+1:

:+1:


Add a display block that shows unrelated blocks side by side

Create new class of DisplayBlock
Add display block to all places like schema and relevant wiring stuff
Test out with dogfooding

Could it instead be a reporting feature? And have it print out all blocks and their info?

What if there was an optional math spec key for display blocks or something and this one had the ability to make folders and different mixes of reports and stuff


[local_auth] sticky auth causes the authentication prompt to display twice on some devices

I came across this issue using the example code from the plugin package page: https://pub.dev/packages/local_auth/example on the One Plus 7 Pro device running Android 10. When sticky auth is enabled it causes the prompt to display twice, even if you're correctly authorized the first time, after the second prompt, it goes back to your app view, see screen recording:
https://user-images.githubusercontent.com/1798070/114744432-fac21c80-9d4d-11eb-9886-b76ab9fdbfb7.mp4
environment:
  sdk: ">=2.12.0 <3.0.0"

dependencies:
  flutter_bloc: ^7.0.0
  bloc: ^7.0.0
  provider: ^5.0.0
  equatable: ^2.0.0
  http: "^0.13.1"
  shared_preferences: "^0.5.3+4"
  flutter_flavorizr: ^1.0.9
  url_launcher: ^5.0.3
  json_annotation: ^3.0.1
  path_provider: ^1.6.14
  local_auth: ^1.1.4
  flutter:
    sdk: flutter
  cupertino_icons: ^1.0.0

dev_dependencies:
  build_runner: ^1.8.0
  flutter_launcher_icons: "^0.8.0"
  json_serializable: ^3.2.5
  flutter_test:
    sdk: flutter

Hi @adamk22
Thanks for filing the issue, I can't reproduce it on Oneplus 8 (Android 11).
The issue might be device-specific, here is the preview

Can you please try the official sample by cloning its repo
git clone https://github.com/NevercodeHQ/triage-examples.git
open plugins\packages\local_auth\example and run the app on your device

@TahaTesser Thank you for your quick response.
I'm also experiencing this in the example app from the official repo (https://github.com/flutter/plugins). I wasn't able to use git repo you mentioned (got a 404)
As you can see in the recording, authenticating by biometrics (bottom button) works like its intended, runs once. However, using the upper button, the authenticate button, it prompts twice even after the first correct authorization.
https://user-images.githubusercontent.com/1798070/114846681-3526ca80-9ddd-11eb-92d3-530f90fca21d.mp4

Hi @adamk22
I tried both buttons, stick auth only shows once, it might be device specific

@adamk22
The next step is to see if a non-flutter android app has the same issue on the One Plus 7 Pro device that you have.

@cyanglaz i have several banking apps that i believe are non flutter that use a similar technique for local authentication and is working just fine. The example app is the first time i experienced an issue like this. If you have an app that you know of that I can try to confirm, let me know and I'll give it a try.

@adamk22 Thanks for the information. Based on what you've said, I think it might be a real bug in the plugin. I'm going to tentatively label it as P4. I have gotten chance to look into this issue in detail yet.

Even I'm facing this issue with one plus 6t. Currently making the stickyAuth false solves the issue. But we have a release of an update this week. Hope the issue gets resolved soon.

I have the same issue on a Galaxy A41 with Android 10. Btw. it was still working in version 1.1.0 (and still is if I switch back) but it is not working in 1.1.5 . I haven't tested in which version  in between it was broken. But according to the changelog 1.1.1 sound like a candidate "Update flutter_plugin_android_lifecycle dependency to 2.0.1 to fix an R8 issue on some versions."

@TahaTesser any updates on the issue? For now, as I mentioned previously I have made the sticky false and release the update. Keep us updated on the issue. Thanks.

Happens on OnePlus 5 too, with the latest version. With sticky false the problem does not happen.

Any solution for this issue?
Same problem here.

Any update on this?

Any update on this issue?

Any update on this I am facing same issue on this pub

i have the same issue on galaxy s9 with android 10.

Same issue on HuaWei Mate20


Collegeboard MC Reflection 2021

This is my reflection for the 2021 APCSP Exam.
Overall Score:

Question 26:

Reflection: This is a pretty simple question, I think I messed it up because I was thinking of which one a parallel computing system would be good for. The option I chose is like the exact definition of what parallel computing is, and so I picked that. I have to read the question more carefully next time.
Question 27:

Reflection:
Question 29:

Reflection: This question was such a simple mistake 🤦. I didn't see that the values were given for j and k in the beginning. So, I just guessed. I really have to start reading the questions.
Question 30:

Reflection:
Question 39:

Reflection:
Question 41:

Reflection:
Question 55:

Reflection:

Collegeboard

Oops, my bad Tanav

No worries!


Ansible validation of PHP fails when using PHP 7.0?

I set up 3 VMs for PHP 5.5, 5.6, and (attempting) 7.0 to replicate the set up from your excellent article at http://www.jeffgeerling.com/blogs/jeff-geerling/benchmarking-drupal-8-php-7-vs-hhvm. (I'm doing the same thing only comparing D7/Backdrop).
I made 3 copies of the config.yml, then ran once for PHP 5.5, again for PHP 5.6, and finally for PHP 7.0. The final time however, Ansible is failing the geerlingguy.php task:
==> drupalvm70: TASK [geerlingguy.php : Ensure PHP packages are installed.] ********************
==> drupalvm70: failed: [localhost] => (item=[u'php5', u'php5-mcrypt', u'php5-cli', u'php5-common', u'php5-curl', u'php5-dev', u'php5-fpm', u'php5-gd', u'php-pear', u'php-apc', u'libpcre3-dev']) => {"cache_update_time": 0, "cache_updated": false, "failed": true, "item": ["php5", "php5-mcrypt", "php5-cli", "php5-common", "php5-curl", "php5-dev", "php5-fpm", "php5-gd", "php-pear", "php-apc", "libpcre3-dev"], "msg": "'/usr/bin/apt-get -y -o \"Dpkg::Options::=--force-confdef\" -o \"Dpkg::Options::=--force-confold\"   install 'php5' 'php5-mcrypt' 'php5-cli' 'php5-common' 'php5-curl' 'php5-dev' 'php5-fpm' 'php5-gd' 'php-pear' 'php-apc' 'libpcre3-dev'' failed: E: Unable to correct problems, you have held broken packages.\n", "stderr": "E: Unable to correct problems, you have held broken packages.\n", "stdout": "Reading package lists...\nBuilding dependency tree...\nReading state information...\nSome packages could not be installed. This may mean that you have\nrequested an impossible situation or if you are using the unstable\ndistribution that some required packages have not yet been created\nor been moved out of Incoming.\nThe following information may help to resolve the situation:\n\nThe following packages have unmet dependencies:\n php-pear : Depends: php-cli\n", "stdout_lines": ["Reading package lists...", "Building dependency tree...", "Reading state information...", "Some packages could not be installed. This may mean that you have", "requested an impossible situation or if you are using the unstable", "distribution that some required packages have not yet been created", "or been moved out of Incoming.", "The following information may help to resolve the situation:", "", "The following packages have unmet dependencies:", " php-pear : Depends: php-cli"]}

It looks like it's validating that PHP 5 was installed, but I've specified that I want php_version: "7.0" in the config.yml file. Included in its entirely below:
---
# `vagrant_box` can also be set to geerlingguy/centos6, geerlingguy/centos7,
# geerlingguy/ubuntu1204, parallels/ubuntu-14.04, etc.
vagrant_box: geerlingguy/ubuntu1404
vagrant_user: vagrant
vagrant_synced_folder_default_type: rsync

# If you need to run multiple instances of Drupal VM, set a unique hostname,
# machine name, and IP address for each instance.
vagrant_hostname: drupalvm70.dev
vagrant_machine_name: drupalvm70
vagrant_ip: <IP_ADDRESS>

# Allow Drupal VM to be accessed via a public network interface on your host.
# Vagrant boxes are insecure by default, so be careful. You've been warned!
# See: https://docs.vagrantup.com/v2/networking/public_network.html
vagrant_public_ip: ""

# A list of synced folders, with the keys 'local_path', 'destination', and
# a 'type' of [nfs|rsync|smb] (leave empty for slow native shares). See
# http://docs.drupalvm.com/en/latest/extras/syncing-folders/ for more info.
vagrant_synced_folders:
  # The first synced folder will be used for the default Drupal installation, if
  # build_makefile: is 'true'.
  - local_path: ~/Sites/drupalvm
    destination: /var/www/html
    type: rsync
    create: true

# Memory and CPU to use for this VM.
vagrant_memory: 1024
vagrant_cpus: 2

# The web server software to use. Can be either 'apache' or 'nginx'.
drupalvm_webserver: apache

# Set this to false if you are using a different site deployment strategy and
# would like to configure 'vagrant_synced_folders' and 'apache_vhosts' manually.
build_makefile: false

# Set this to false if you don't need to install drupal (using the drupal_*
# settings below), but instead copy down a database (e.g. using drush sql-sync).
install_site: false

# Settings for building a Drupal site from a makefile (if 'build_makefile:'
# is 'true').
drupal_major_version: 7
drupal_core_path: "/var/www/html"
drupal_domain: "{{ vagrant_hostname }}"
drupal_site_name: "Drupal7"
drupal_install_profile: standard
drupal_enable_modules: [ ]
drupal_account_name: admin
drupal_account_pass: admin
drupal_mysql_user: drupal
drupal_mysql_password: drupal
drupal_mysql_database: drupal

# Additional arguments or options to pass to `drush site-install`.
drupal_site_install_extra_args: []

# Cron jobs are added to the root user's crontab. Keys include name (required),
# minute, hour, day, weekday, month, job (required), and state.
drupalvm_cron_jobs: []
  # - {
  #   name: "Drupal Cron",
  #   minute: "*/30",
  #   job: "drush -r {{ drupal_core_path }} core-cron"
  # }

# Drupal VM automatically creates a drush alias file in your ~/.drush folder if
# this variable is 'true'.
configure_local_drush_aliases: false

# Apache VirtualHosts. Add one for each site you are running inside the VM. For
# multisite deployments, you can point multiple servernames at one documentroot.
# View the geerlingguy.apache Ansible Role README for more options.
apache_vhosts:
  - servername: "{{ drupal_domain }}"
    documentroot: "{{ drupal_core_path }}"
    extra_parameters: |
          ProxyPassMatch ^/(.*\.php(/.*)?)$ "fcgi://<IP_ADDRESS>:9000{{ drupal_core_path }}"

  - servername: "adminer.{{ vagrant_hostname }}"
    documentroot: "{{ adminer_install_dir }}"
    extra_parameters: |
          ProxyPassMatch ^/(.*\.php(/.*)?)$ "fcgi://<IP_ADDRESS>:9000{{ adminer_install_dir }}"

  - servername: "xhprof.{{ vagrant_hostname }}"
    documentroot: "{{ php_xhprof_html_dir }}"
    extra_parameters: |
          ProxyPassMatch ^/(.*\.php(/.*)?)$ "fcgi://<IP_ADDRESS>:9000{{ php_xhprof_html_dir }}"

  - servername: "pimpmylog.{{ vagrant_hostname }}"
    documentroot: "{{ pimpmylog_install_dir }}"
    extra_parameters: |
          ProxyPassMatch ^/(.*\.php(/.*)?)$ "fcgi://<IP_ADDRESS>:9000{{ pimpmylog_install_dir }}"

  - servername: "{{ vagrant_ip }}"
    serveralias: "dashboard.{{ vagrant_hostname }}"
    documentroot: "{{ dashboard_install_dir }}"

apache_remove_default_vhost: true
apache_mods_enabled:
  - expires.load
  - ssl.load
  - rewrite.load
  - proxy.load
  - proxy_fcgi.load

# Nginx hosts. Each site will get a server entry using the configuration defined
# here. Set the 'is_php' property for document roots that contain PHP apps like
# Drupal.
nginx_hosts:
  - server_name: "{{ drupal_domain }}"
    root: "{{ drupal_core_path }}"
    is_php: true

  - server_name: "adminer.{{ vagrant_hostname }}"
    root: "{{ adminer_install_dir }}"
    is_php: true

  - server_name: "xhprof.{{ vagrant_hostname }}"
    root: "{{ php_xhprof_html_dir }}"
    is_php: true

  - server_name: "pimpmylog.{{ vagrant_hostname }}"
    root: "{{ pimpmylog_install_dir }}"
    is_php: true

  - server_name: "{{ vagrant_ip }} dashboard.{{ vagrant_hostname }}"
    root: "{{ dashboard_install_dir }}"

nginx_remove_default_vhost: true
nginx_ppa_use: true

# MySQL Databases and users. If build_makefile: is true, first database will
# be used for the makefile-built site.
mysql_databases:
  - name: "{{ drupal_mysql_database }}"
    encoding: utf8
    collation: utf8_general_ci

mysql_users:
  - name: "{{ drupal_mysql_user }}"
    host: "%"
    password: "{{ drupal_mysql_password }}"
    priv: "{{ drupal_mysql_database }}.*:ALL"

# Comment out any extra utilities you don't want to install. If you don't want
# to install *any* extras, make set this value to an empty set, e.g. `[]`.
installed_extras:
  # - adminer
  # - drupalconsole
  # - mailhog
  # - memcached
  # - nodejs
  # - pimpmylog
  # - redis
  # - ruby
  # - selenium
  # - solr
  # - varnish
  # - xdebug
  # - xhprof

# Add any extra apt or yum packages you would like installed.
extra_packages:
  - unzip

# `nodejs` must be in installed_extras for this to work. Valid examples: "0.10",
# "0.12", "4.x", "5.x".
nodejs_version: "0.12"
nodejs_npm_global_packages: []

# `ruby` must be in installed_extras for this to work.
ruby_install_gems_user: "{{ drupalvm_user }}"
ruby_install_gems: []

# You can configure almost anything else on the server in the rest of this file.
extra_security_enabled: false

drush_version: "master"
drush_keep_updated: true
drush_composer_cli_options: "--prefer-dist --no-interaction"

firewall_allowed_tcp_ports:
  - "22"
  - "25"
  - "80"
  - "81"
  - "443"
  - "4444"
  - "8025"
  - "8080"
  - "8443"
  - "8983"
firewall_log_dropped_packets: false

# PHP Configuration. Currently-supported versions: 5.5, 5.6, 7.0.
php_version: "7.0"
php_memory_limit: "192M"
php_display_errors: "On"
php_display_startup_errors: "On"
php_realpath_cache_size: "1024K"
php_sendmail_path: "/usr/sbin/ssmtp -t"
php_opcache_enabled_in_ini: true
php_opcache_memory_consumption: "192"
php_opcache_max_accelerated_files: 4096
php_max_input_vars: "4000"

# Drupal VM defaults to using PHP-FPM with either Apache or Nginx. If you wish
# to instead use Apache + mod_php with an Ubuntu base box, make sure you add
# libapache2-mod-php5 to `extra_packages` elsewhere in this config file.
php_enable_php_fpm: true
php_fpm_listen: "<IP_ADDRESS>:9000"

composer_path: /usr/bin/composer
composer_home_path: "/home/{{ drupalvm_user }}/.composer"
composer_home_owner: "{{ drupalvm_user }}"
composer_home_group: "{{ drupalvm_user }}"
# composer_global_packages:
#   - { name: phpunit/phpunit, release: '@stable' }

# Run specified scripts after VM is provisioned. Path is relative to the
# `provisioning/playbook.yml` file.
post_provision_scripts: []
  # - "../examples/scripts/configure-solr.sh"

# MySQL Configuration.
mysql_root_password: root
mysql_slow_query_log_enabled: true
mysql_slow_query_time: 2
mysql_wait_timeout: 300
adminer_install_filename: index.php

# Varnish Configuration.
varnish_listen_port: "81"
varnish_default_vcl_template_path: templates/drupalvm.vcl.j2
varnish_default_backend_host: "<IP_ADDRESS>"
varnish_default_backend_port: "80"

# Pimp my Log settings.
pimpmylog_install_dir: /usr/share/php/pimpmylog
pimpmylog_grant_all_privs: true

# XDebug configuration. XDebug is disabled by default for better performance.
php_xdebug_default_enable: 0
php_xdebug_coverage_enable: 0
php_xdebug_cli_enable: 1
php_xdebug_remote_enable: 1
php_xdebug_remote_connect_back: 1
# Use PHPSTORM for PHPStorm, sublime.xdebug for Sublime Text.
php_xdebug_idekey: PHPSTORM
php_xdebug_max_nesting_level: 256

# Solr Configuration (if enabled above).
solr_version: "4.10.4"
solr_xms: "64M"
solr_xmx: "128M"

# Selenium configuration.
selenium_version: 2.46.0

# Other configuration.
dashboard_install_dir: /var/www/dashboard
known_hosts_path: ~/.ssh/known_hosts

Is is possible that having set up PHP 5.5 and 5.6 VMs first may be contaminating this new VM? I did make sure to give each a different Vagrant machine name, hostname, ports, etc. This is likely a "me" problem than a bug with the script, but I'm not sure. Any ideas?

For PHP 7 in particular (on Ubuntu, at least), there's one additional change—you have to update the php_packages variable too: http://docs.drupalvm.com/en/latest/other/php-7/
Good to know Drupal VM is working for Backdrop! If someone can contribute a docs page in the 'other' folder (maybe alongside where the Drupal 6 special instructions are), I'd be happy to merge it so you can give people another option for local installs.

Ahhhh, I just found that! Good gravy.
I think this would be worthwhile adding that information directly into config.yml if it's not possible to automatically support it. Definitely 2 hours of life I'm not getting back. Or at the very least include a link to the documentation. This understates the requirements a bit:
# PHP Configuration. Currently-supported versions: 5.5, 5.6, 7.0.
php_version: "5.6"

It implies that just changing to "7.0" would do the job.

Good to know Drupal VM is working for Backdrop! If someone can contribute a docs page in the 'other' folder (maybe alongside where the Drupal 6 special instructions are), I'd be happy to merge it so you can give people another option for local installs.

That would be great! Yes Drupal VM works 100% with Backdrop, I haven't had any issues at all (other than installing PHP 7 itself). I'll be publishing a blog post once I get it all benchmarked. Thanks for paving the way with your article. I tried to do this once before with an AWS script but it was incredibly buggy and difficult to set up multiple PHP versions on the same OS. It's great to have this tool available. Thanks!

PR to add a URL to the PHP 7 docs: https://github.com/geerlingguy/drupal-vm/pull/541.

In config.yml - php version is mentioned as 5.6 and still
I am getting this error

~~~~~~~~~~*
==> drupalvm: TASK [geerlingguy.php : Ensure PHP packages are installed.] ********************
==> drupalvm: failed: [localhost] (item=[u'php7.0-common', u'php7.0-cli', u'php7.0-dev', u'php7.0-fpm', u'libpcre3-dev', u'php7.0-gd', u'php7.0-curl', u'php7.0-imap', u'php7.0-json', u'php7.0-opcache', u'php7.0-xml', u'php7.0-mbstring', u'php-sqlite3', u'php-apcu']) => {"failed": true, "item": ["php7.0-common", "php7.0-cli", "php7.0-dev", "php7.0-fpm", "libpcre3-dev", "php7.0-gd", "php7.0-curl", "php7.0-imap", "php7.0-json", "php7.0-opcache", "php7.0-xml", "php7.0-mbstring", "php-sqlite3", "php-apcu"], "msg": "No package matching 'php7.0-common' is available"}
==> drupalvm:
==> drupalvm: RUNNING HANDLER [geerlingguy.firewall : restart firewall] **********************
==> drupalvm:
==> drupalvm: RUNNING HANDLER [geerlingguy.apache : restart apache] **************************
==> drupalvm:
==> drupalvm: RUNNING HANDLER [geerlingguy.mysql : restart mysql] ****************************
==> drupalvm: 	to retry, use: --limit @/vagrant//provisioning/playbook.retry
==> drupalvm:
==> drupalvm: PLAY RECAP *********************************************************************
==> drupalvm: localhost                  : ok=89   changed=28   unreachable=0    failed=1
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
~~~~~~~~~~*
After this error i did

vagrant ssh
sudo apt-get update
exit
vagrant provision

Still same error is being displayed.
Any help is appreciated :)

@npralhad would you mind posting your config.yml?

@oxyc please have a look at my message one more time. I have update the config.yml snippet.

Are you using Drupal VM 3.0.0? To use PHP 5.6 starting with 3.0.0 you will need to set some other variables as well. http://docs.drupalvm.com/en/latest/other/php-56/#ubuntu-1404

Thanks very much for this information. I will try this out and will update accordingly. :)

@geerlingguy http://docs.drupalvm.com/en/latest/other/php-7/ link is broken. Is there another link? TY.

@sshrestha-navarts - That documentation page is gone because Drupal VM now defaults everything to PHP 7. There's a new page in place for PHP 5.6 in case you want to downgrade to that version: http://docs.drupalvm.com/en/latest/other/php-56/


Is it possible to train from multiple data directory?

Hello, i am curious for new yolo nas model. I am new to super gradient. Is it possible to train a model on custom dataset which are prepared in yolov5/8 format specially in multiple directories?

Hi @hardikdava!
When you say multiple directory, do you mean different for train/val and images/labels (which is the default yolov5/8 format) ?
        data_dir
        ├── train
        │   ├── images
        │   │      ├─ 0001.jpg
        │   │      ├─ 0002.jpg
        │   │      └─ ...
        │   └── labels
        │          ├─ 0001.txt
        │          ├─ 0002.txt
        │          └─ ...
        └── val
            ├── images
            │      ├─ 434343.jpg
            │      ├─ 434344.jpg
            │      └─ ...
            └── labels
                   ├─ 434343.txt
                   ├─ 434344.txt
                   └─ ...

We support this case and this is what we have been using in our demo notebooks.
Or something less common, where you would want to use images/labels from 2 different folders each (train_part_1/images + train_part_2/images), like in the following:
        data_dir
        ├── train_part_1
        │   ├── images
        │   │      ├─ 0001.jpg
        │   │      ├─ 0002.jpg
        │   │      └─ ...
        │   └── labels
        │          ├─ 0001.txt
        │          ├─ 0002.txt
        │          └─ ...
        └── train_part_2
            ├── images
            │      ├─ 434343.jpg
            │      ├─ 434344.jpg
            │      └─ ...
            └── labels
                   ├─ 434343.txt
                   ├─ 434344.txt
                   └─ ...

This case is not supported out of the box, but you can simply create a 3rd folder that would concatenate both into the same structure as the first case, and then use the code provided in our demo notebooks.
If it's something else, feel free to show the structure of the dataset you are talking about :)

Thank you for your reply @Louis-Dupont . I want to train as per second option (train_part_1/images + train_part_2/images). I will accumulate all the data then try to run it. But thank you for your reply again.


updated version to the 2.2

please build from this branch and give the plugin to Lorinda for testing..


class tymon do not exist for any route require token login

I'm submitting a ...

[ yes] bug report
[ ] feature request
[ ] support request
[ ] other (Please specify)

hi, i face this error, may take a look thanks.
Route::get('auth/user', function (Request $request) {
return 'yo';
})->middleware('auth:api');
http://localhost:8000/api/auth/user  --> display error

hi  i just change to
})->middleware('jwt.auth');
instead of
})->middleware('auth:api');
then it works,
may i know why use 'auth:api'  ?

Hi @puahyan
Thanks for the bug report
I can confirm that there's an issue, I'll work on a fix and deploy
Your fix didn't work for me, but the reason why this is required now is because dingo/api has been removed from the starter

Route::get('auth/user', function (Request $request) {
return 'yo';
})->middleware('auth.api');
protected $routeMiddleware = [
'auth.api' => \Tymon\JWTAuth\Middleware\GetUserFromToken::class,

auth.api, not auth:api

yeah true, this is a way of fixing it
However auth:api is supposed to use the api config on the default auth provider (check the config/auth.php)
I will try to solve the issue while keeping auth:api if not then I will use your fix
Thanks!

Fixed 😄


Add Jib integration

Add DockerClient via SPI in order to let Jib use Testcontainers' docker client

if Jib.from(String) is used the image is downloaded using Jib's http client. Jib.from(DockerDaemonImage) uses new JibDockerClient#inspect which will use RemoteDockerImage(DockerImageName) to allow image name substitution.

Also, classes now are in core module and the upgrade of jackson library is required in order to make it work with Jib.


Configure option to set Intel compilers correctly

When using the Intel toolchain, the compilers must be specified similar to the following:
CC=icc CXX=icpc FC=ifort F77=ifort ./configure ...
It would be more convenient if there were a single option to set the compiler variables.

Made an attempt to do this here:
https://github.com/cmcantalupo/geopm/tree/cmcantalupo-intel-chain-config
it doesn't work.

Might be able to handle with #633


Adding Rendered Notebook Diff Option

Fixes #14557.
Adds a setting (default is to use current behavior today -- which is a text-only preview) that can be selectively configured by users/workspaces to show a rendered notebook when in the diff editor. Note: this is not "full" diff support, where users can see line-by-line diffs; this just allows users to toggle a setting for whether they'd like to see text-based diffs or a full rendered notebook as a diff. It's the first step only 😄.
The current diff editor expects there to be a coreEditorWidget available to detect scroll changes: https://github.com/microsoft/azuredatastudio/blob/33a5078df5bdf5bab36aeef3456a899e4b8cb706/src/vs/editor/browser/widget/diffEditorWidget.ts#L551. Since this isn't the case for notebooks, that's why I have scrolling logic implemented.
https://user-images.githubusercontent.com/40371649/112395219-37ed3e80-8cbb-11eb-98cb-41045d787257.mp4

Pull Request Test Coverage Report for Build 684940748

26 of 38 (68.42%)  changed or added relevant lines in 7 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 43.279%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/workbench/contrib/notebook/browser/models/nodebookInputFactory.ts
4
5
80.0%

src/sql/workbench/contrib/notebook/browser/notebookEditor.ts
7
11
63.64%

src/sql/workbench/contrib/notebook/browser/models/diffNotebookInput.ts
7
14
50.0%

Totals

Change from base Build 684638300:
0.02%

Covered Lines:
25485

Relevant Lines:
53727

💛  - Coveralls

Should the original input be readonly? Right now I can edit both the original and modified notebooks in the diff view.

Yikes, great catch @lucyzhang929. Yes should be readonly.


Unable to serialize/deserialize std::io::Error

I am trying to implement a custom error with thiserror that needs to implement a serialization trait.
The custom error needs to translate errors for std::io::Error into the customPrintError
#[derive(Error, Debug, Serialize, Deserialize)]
pub enum PrintError {
  #[error("Connection Error: ")]
  Connection(#[from] std::io::Error)
}

But doing so gives the following error:
Connection(#[from] std::io::Error)
    |      ^ the trait `Serialize` is not implemented for `std::io::Error`

Given that std::io::Error is from the standard library, I won't be able to implement a custom Serialize/Deserialize in my project.
Is there a workaround for this?

You can use #[serde(with = "...")] to implement you own serialization routines for a specific field (here, PrintError::Connection.0). #[serde(remote = "")] might come in handy too.

I implemented serialization like so:
#[derive(Error, Debug)]
pub enum PrintError {
  #[error("Not able to connect")]
  ConnectionFailed(#[from] std::io::Error)
}

impl Serialize for PrintError {
  fn serialize<S>(&self, serializer: S) -> Result<S::Ok, S::Error>
      where
          S: serde::Serializer {
      serializer.serialize_str(self.to_string().as_ref())
  }
}

Is this approach okay?

If you only need to serialize your error in human-readable format (no further processing later), this looks good to me. I haven't checked if it compiles but I guess it does :sweat_smile:


Update TFvsPulumi with SEO recommendation

Swapping the Tag and H1 order
Description

@zchase per Jesse's recommendation


[SPARK-24243][CORE] Expose exceptions from InProcessAppHandle

What changes were proposed in this pull request?
Adds a new method to SparkAppHandle called getError which returns
the exception (if present) that caused the underlying Spark app to
fail.
How was this patch tested?
New tests added to SparkLauncherSuite for the new method.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

@vanzin could you take a look? I'm not sure if the same race conditions present in the other unit tests apply to the new ones since no SparkContext is being created. For now I didn't add any synchronization, but I can add some.

Can one of the admins verify this patch?

ok to test

Test build #94772 has started for PR 21849 at commit 7e3100e.

@vanzin addressed your comments and updated the PR

Test build #95481 has started for PR 21849 at commit d5d51d2.

Test build #95481 has finished for PR 21849 at commit d5d51d2.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95481/
Test FAILed.

It's safe to add a mima exception for that error since SparkAppHandle is not meant to be implemented by external code. So it's safe to add methods to it.

Test build #95488 has started for PR 21849 at commit a8bbd67.

Test build #95488 has finished for PR 21849 at commit a8bbd67.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95488/
Test FAILed.

Test build #95489 has started for PR 21849 at commit 9240b77.

Test build #95489 has finished for PR 21849 at commit 9240b77.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95489/
Test FAILed.


Model.from_db_value() signature change in Django 2.0

Hello.
I tried to apply django-oscar to my project.
But I found the following warning messages:  “RemovedInDjango30Warning: : Remove the context parameter from NullCharField.from_db_value() and UppercaseCharField.from_db_value(). Support for it will be removed in Django 3.0.
RemovedInDjango30Warning”
Seeing warning messages every time I run tests are by no means good, so I wonder if you are open to contributions regarding fixing this. If so, I will be glad to help.
Reproduce

I think that is the cause of the error is the  UppercaseCharField used in oscar/models/fields/__init__.py of from_db_value function.
And also NullCharField is the cause of the error used in oscar/models/fields/__init__.py of from_db_value function.

class NullCharField(CharField):
    """
    CharField that stores '' as None and returns None as ''
    Useful when using unique=True and forms. Implies null==blank==True.

    Django's CharField stores '' as None, but does not return None as ''.
    """
    description = "CharField that stores '' as None and returns None as ''"

    def __init__(self, *args, **kwargs):
        if not kwargs.get('null', True) or not kwargs.get('blank', True):
            raise ImproperlyConfigured(
                "NullCharField implies null==blank==True")
        kwargs['null'] = kwargs['blank'] = True
        super().__init__(*args, **kwargs)

    def contribute_to_class(self, cls, name, **kwargs):
        super().contribute_to_class(cls, name, **kwargs)
        setattr(cls, self.name, Creator(self))

    def from_db_value(self, value, expression, connection, context):
        value = self.to_python(value)
        # If the value was stored as null, return empty string instead
        return value if value is not None else ''

class UppercaseCharField(CharField):
    """
    A simple subclass of ``django.db.models.fields.CharField`` that
    restricts all text to be uppercase.

    Defined with the with_metaclass helper so that to_python is called
    https://docs.djangoproject.com/en/1.6/howto/custom-model-fields/#the-subfieldbase-metaclass  # NOQA
    """

    def contribute_to_class(self, cls, name, **kwargs):
        super().contribute_to_class(
            cls, name, **kwargs)
        setattr(cls, self.name, Creator(self))

    def from_db_value(self, value, expression, connection, context):
        return self.to_python(value)

    def to_python(self, value):
        val = super().to_python(value)
        if isinstance(val, str):
            return val.upper()
        else:
            return val

Technical details
Python   3.7.3
Django   2.2
pytest   4.4.0
django-oscar   2.0b1 (edited)

Thanks for reporting this. We would be grateful if you are able to make a PR to fix this!

Fixed in #3046


Make XR begin and end session asynchronous

Work will require the XrPlugin to have access to the task chain, so should be undertaken after the work to switch NativeEngine to us runtime global state stored with NAPI so that XrPlugin can take advantage of the same mechanism.

Begin session was made async as part of https://github.com/BabylonJS/BabylonNative/commit/45a1944f9403ec1f96daf3e11e451ce2eddcb6c6.

Closing for now. Reopen if we want to fix this.


Feature Request: MQTT Last Will and Testiment set values to 0 or unavalible

I notice when I shutdown my computer home assistant shows the last value it received from the mqtt service. This is a little annoying as it could be stuck at 8% CPU or In Use forever until the service is started again. And you really don't get any feedback that the computer is off. I am still new the MQTT but I think there is a Last Will and Testiment feature of MQTT that when the MQTT server looses communications it will set these last will and testament values.
It would be nice if we could set the values to 0 or unavailable so you can tell from Home assistant that the service/computer is shutdown or not working in someway.
Also just wanted to say thanks for an amazing program it has been very helpful so far you did a really good job on it.

Thanks for creating an issue! And thank you for the kind words.
This should indeed be implemented in some way and I'll give it some thought.

Thanks for creating an issue! And thank you for the kind words.
This should indeed be implemented in some way and I'll give it some thought.

Will message has been implemented and will be in the next release. This makes sensors and commands "Unavailable" in Home Assistant.

Will message has been implemented and will be in the next release. This makes sensors and commands "Unavailable" in Home Assistant.


[Tensor] Add outplace method for arithmetic ops

Add outplace ops with already allocated tensor.
Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #857. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #857. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.


Build CUDA for MFEM

Hello Everyone,
I am trying to build CUDA for MFEM but getting errors.

cmake /home/muhammad/Downloads/mfem-4.0 -DMFEM_USE_CUDA=YES

muhammad@muhammad-All-Series:~/Downloads/Build$ cmake /home/muhammad/Downloads/mfem-4.0 -DMFEM_USE_CUDA=YES
-- (optional) USER_CONFIG = /home/muhammad/Downloads/mfem-4.0/config/user.cmake
-- USE_XSDK_DEFAULTS = 'OFF'
-- The CUDA compiler identification is unknown
CMake Error at CMakeLists.txt:92 (enable_language):
No CMAKE_CUDA_COMPILER could be found.
Tell CMake where to find the compiler by setting either the environment
variable "CUDACXX" or the CMake cache entry CMAKE_CUDA_COMPILER to the full
path to the compiler, or to the compiler name if it is in the PATH.
-- Configuring incomplete, errors occurred!
See also "/home/muhammad/Downloads/Build/CMakeFiles/CMakeOutput.log".
See also "/home/muhammad/Downloads/Build/CMakeFiles/CMakeError.log".
Please kindly someone help.

As the CMake message suggests, you need to tell CMake where the CUDA compiler is. To do that add the following option to the cmake command line: -DCMAKE_CUDA_COMPILER=<path-to-nvcc> where <path-to-nvcc> is the absolute path to the CUDA compiler, nvcc.


.Del key on the numberpad.

Hello, Developer~!
On my keyboard, InputScope does not recognize the .Del key on the numberpad.
What settings do I need to modify?
Thank you.

Does it recognize it as anything at all? E.g. if you press Del many times, do statistics change on the keyboard page?

Does it recognize it as anything at all? E.g. if you press Del many times, do statistics change on the keyboard page?

I pressed the .Del key dozens of times, but no logs were saved in the InputScope. :(
InputScope doesn't recognize .Del key at all.

A few more questions:

What is the operating system?
How was InputScope installed?
What is the keyboard model?
What is the keyboard layout?

Windows 7 x64
InputScope_1.5_x64.exe in C:\Program Files\InputScope
Membrane PS/2 Samsung Keyboard.
http://img.danawa.com/prod_img/large/group_249/124741_1.jpg

To clarify: by keyboard layout I meant the OS keyboard language setting.

KOREAN - Microsoft IME
PS/2 Keyboard 103/106KEY

If you switch the layout to something else like English, does the result change?

I switched to "English (United States) - US keyboard" but the result is unchanged.

FIY, The Mousotron recognizes .Del key normally.
https://www.blacksunsoftware.com/mousotron.html

Can you try the following.

right-click on the taskbar icon and select "Show Python console"
in the console, copy-paste the following lines one by one, and press Enter after each:

import pynput

listener = pynput.keyboard.Listener(on_press=lambda k: print("%s -- %s -- %s" % (type(k), vars(k), k)))

listener.start()

If you press the Del key, what does it print?
(The printing can be stopped with running listener.stop() in the console.)

<class 'pynput.keyboard._win32.KeyCode'> -- {'vk': 110, 'char': None, 'is_dead': False, 'combining': None, '_flags': None, '_scan': 83} -- <110>

um... I found that Inputscope does not recognize the combo of ctrl and number keys. For example, ctrl+1 or ctrl+alt+0.

Confirmed. Will release a fixed version soon.

It’s such a relief to know that you fixed this issue.
um... There are 2 more special keys that inputscope does not recognize.
All Koreans use two special keys.
https://images2.imgbox.com/51/f5/nrKzSAKT_o.jpg
<class 'pynput.keyboard._win32.KeyCode'> -- {'vk': 25, 'char': None, 'is_dead': False, 'combining': None, '_flags': None, '_scan': 241} -- <25>
Key Name : ' Hanja '
Function : Replace Korean with Classical Chinese
<class 'pynput.keyboard._win32.KeyCode'> -- {'vk': 21, 'char': None, 'is_dead': False, 'combining': None, '_flags': None, '_scan': 242} -- <21>
Key name : ' KO/EN '
Function : Language switching (Korean ↔ English)
If you don’t mind, could you add those to inputscope too?

It is true that the Korean name for the second key is only called 'HanYeong' by Koreans.
But In my opinion, I think it's okay to call it Korean/English.

Can you try this in the console:
import pynput

on_press = lambda k: print("%s -- %s -- %s" % (type(k), vars(k), k))

w32filter = lambda a, b: print("<RAW virt %r scan %r flag %r>" % (b.vkCode, b.scanCode, b.flags)) if a == 256 else None

listener = pynput.keyboard.Listener(on_press=on_press, win32_event_filter=w32filter)

listener.start()

What does it print for the Korean specials?

Hanja : <RAW virt 25 scan 241 flag 1>
Han/Yeong : <RAW virt 21 scan 242 flag 1>

Can you try downloading and running https://erki.lap.ee/stuff/inputscope_1.6.dev8_x64.exe and see how it fares?
Numpad-Delete and the Korean keys should register now, and Ctrl+number combos as well.
I named the Korean keys as "IME Hanja/Kanji" and "IME Hangul/Kana".

Numpad-Delete	1
IME Kana/Hangul	2
IME Hanja/Kanji	3
It works like a charm!
I thought these were simple issues, but it seems to have been a longer journey than I thought.
Thank you for your hard work :)
By the way, Kana/Hangul?
As far as I know, Kana means Katakana in Japanese.
Korean keyboards do not have the special key to switch between Hangul and Katakana.
Han/Yeong only supports switching between Hangul and English.
And the Virustotal seems to recognize the dev version as a virus.
https://www.virustotal.com/gui/file/8b4f7ca70642e206cba75761d499b08e912fdc016fb68f42712c419a9e349413?nocache=1

Excellent that it all works now. I will make a public release soon; will keep this issue open until then. These were simple problems indeed, but I also had some other changes in the pipeline pending release.
I chose more generic names for the language keys, as I discovered that the same keys are used for similar language switching on Japanese keyboards as well (https://docs.microsoft.com/en-us/windows/win32/inputdev/virtual-key-codes). The name does not mean it switches between Kana and Hangul, but that it can toggle Hangul mode if Korean, or it can toggle Kana mode if Japanese.
By the way, I added an option for users to specify their own additional keys or override key names in the configuration file. So for example you can add to inputscope.ini:
CustomKeys = {21: "IME Han/Yeong", 25: "IME Hanja"}

The antivirus alerts, are, unfortunately, an eternal and expected pain. There is something about packaged Python apps that always triggers some antivirals, possibly because the methods for packing the executable code are similar to what some viruses use. And it is quite hopeless to get it all green; the false positives need to be reported to each antivirus separately, and some of them do not even have channels for this. The current report state is actually better than usual, only some rather no-name antivirals are raising an alert.
Ironic that Yandex and Kaspersky are still used in VirusTotal. The entire Russian Federation has been sanctioned by the western world in all possible ways, but hey, let's still use their antivirals..

Released v1.6, the problems above ought to be fixed now.


Breaking: Upgraded Babel to 7.0.0-beta.51

I upgraded the Babel dependencies to the latest beta versions and updated tests accordingly.
The main changes in this PR are:

Babel now supports the new decorators proposal by default, so we need to switch between the new and the old proposal. This is a breaking change.
To enable the legacy decorators proposal users should add a specific parser option:
{
  parserOptions: {
    ecmaFeatures: {
      legacyDecorators: true
    }
  }
}

Babel removed the support for Node 4 , so I propagated that here.

Flow has support for new syntax now, so I added new tests for it. It only support parsing for the moment. I'll add support for scope analysis soon.

@rubennorte published as v9.0.0-beta.1, thanks!


Proposal: Install helm plugin from archive

I'm opening this issue because I'm currently encountering the need to install helm plugins on clusters that don't have internet access. It would therefore be interesting if the helm plugin install command could use an archive as argument.
Currently, to get around the difficulty of installing the helm-mapkubeapis plugin, I'm running this subset of the command.
mkdir /root/.local/share/helm/plugins/helm-mapkubeapis
tar xzf helm-mapkubeapis_0.4.1_linux_amd64.tar.gz --directory /root/.local/share/helm/plugins/helm-mapkubeapis/
mkdir /root/.local/share/helm/plugins/helm-mapkubeapis/bin
mv /root/.local/share/helm/plugins/helm-mapkubeapis/mapkubeapis /root/.local/share/helm/plugins/helm-mapkubeapis/bin/

Can you describe in more detail the problem please
$ helm plugin install --help

This command allows you to install a plugin from a url to a VCS repo or a local path.

Usage:
  helm plugin install [options] <path|url>... [flags]

It should be possible to install a plugin from a path. Do you mean the path could be an archive? Rather than an
(unpacked) directory?

Yes, I'd like to be able to install a plugin via a path that happens to be an archive. Since plugin can be downloaded directly as archives, it makes more sense to use a path which is an archive. I am opening this proposal following a number of difficulties encountered in my attempt to install the helm-mapkubeapis plugin with a path. I've realized that the script that is executed to perform the install is not compliant with this method. As this plugin is part of the helm projects, I have opened this issue in order to make a functional improvement proposal, but also to better understand whether the guidelines that are proposed in the development of plugin are respected for this one.

Thanks for clarifying.I think reading from an achieve directly would be a nice improvement. A PR to support would be welcome.


Is there a a specified encoding that should be used with application/vnd.api+json responses?

I'm working with a web-service that implements a JSON-API, and there is no definitive encoding that is specified for the API responses, and the server doesn't return a content-disposition header with the encoding.
Realistically, I'm pretty sure the server here is responding in UTF-8, but the JSON spec allows UTF-8, UTF-16 or UTF-32 (ref), so it's ambiguous.
It'd be nice to have the standard either require a proper content-disposition header, or specify a encoding that must be used in the absence of any other response metadata.
Is this within the scope of the JSON-API specification? I'm not sure.

Basically, the various JSON specifications have never defined a way to provide information about the particular unicode encoding in use because this can be detected reliably by the client. This JSON specification offers instructions for doing so, assuming the sender properly leaves out the byte order mark. (You'll need to use more complicated logic if you want to handle the case that the BOM is, improperly, included.)
Alternatively, you could just use a JSON parser that handles this all for you :)


Update README.md

Fix typo for WithObservationStrategy

Pull Request Test Coverage Report for Build 837

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 0.0%

Totals

Change from base Build 836:
0.0%

Covered Lines:
0

Relevant Lines:
0

💛  - Coveralls

Thanks having spotted it @mimol91


Add publish for Actors with grpc and unit test cases

Signed-off-by: Diego Juarez<EMAIL_ADDRESS>Description
I added "publishing for actors" support by building events functions and requests that handle ActorType and ActorID. Also, I added unit test for that functionality.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close:  WIP Support pubsub for Actors #501
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[X] Code compiles correctly
[X] Created/updated tests
[ ] Extended the documentation

The tests here are expected to fail because they will run against a version of daprd that doesn't have the APIs you created.

Let's close and reopen to see if the tests run then.


Actions execute twice

Describe the bug
Is it normal to execute actions (in my case edit) when clicking the button in the dropdown? So that actions execute twice: first time when accessing edit page and second time when saving the edit.
Installed libraries and their versions

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>node version 18.5.0
npm version 8.12.1

To Reproduce
Steps to reproduce the behavior:

Go to 'http://localhost:port/admin/resources/Something'
Click on 'the dropdown next to a resource and chose edit'
Not necessary to edit something, just click 'save'
Action would have been executed twice

Expected behavior
Action to execute after I click save
Screenshots
In edit1 image I accessed edit
In edit2 image I saved the model and action executed again
In delete 1 image I clicked the delete all button
In delete2 image again the action executes second time

AdminJSOptions with schema
resources: [
  {
    resource: Product,
    options: {
      actions: {
          edit: {
            after: async (request) => {
              console.log(request)

              return request
            }
          },
          bulkDelete: {
             after: async (request) => {
               request.records.forEach((record) => {
                 fs.rmdir(
                   path.join(__dirname, '..', 'files/products', `${record.id}`),
                   { recursive: true },
                   (err) => {
                     if (err) {
                       console.error(err)
                     }
                   }
                 )
               })

               return request
             }
          }
        }
     }
   }
],

Desktop (please complete the following information if relevant):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information if relevant):

OS: Windows 10
Browser: Chrome

Additional context
Something like that happens when i use bulkDelete. The action executes when selecting and clicking delete all before clicking the confirm button in the modal that comes from the right.

Thank you!


Poor UX of "Restore password" form

The form which appears when restoring a password to a non-existent email looks bad:

The text box is not readable in dark mode
The "not found" message could be improved

To Reproduce

Go to login page
Click "forgot password"
Enter some totally invalid email into the text box and click "Send me instructions"

Browser
Opera, Win10

Fixed