DVC Repositories are duplicated in the Source Control Panel in multi-root workspace

Issue:
After initializing DVC in an ML training repository, the Source Control pane shows two DVC entries for my repository.
My repo ml_training is a top-level folder in a multi-root VSCode Workspace, which also contains a repository called internal_utils, which is not tracked by DVC. I am trying to start using DVC with ml_training, and everything is going smoothly so far. I initialized DVC in the repo with the following command:
user@server:~/project/ml_training$ dvc init

After doing so, the DVC extension has added not one but two DVC entries for ml_training to the source control panel in VSCode:

They are both identical, any changes I make are reflected identically by both entries. I have tried reinstalling the extension, and initializing both before and after installing the extension, but nothing has changed.
My workspace file is one directory level above the ml_training repository, and I have yet to find a configuration that doesn't have this issue. Git seems to be handled properly, but everything I have tried has either resulted in a panel the same as above, or gotten rid of those DVC entries entirely somehow.
Environment:

Using VSCode on Ubuntu 20.04 SSH remote.
Inside of a multi-root workspace
VSCode version: 1.68.1
Python version: 3.9.13
dvc doctor output:

DVC version: 2.43.1 (snap)
---------------------------------
Platform: Python 3.8.10 on Linux-5.15.0-58-generic-x86_64-with-glibc2.29
Subprojects:
        dvc_data = 0.35.1
        dvc_objects = 0.19.0
        dvc_render = 0.0.17
        dvc_task = 0.1.11
        dvclive = 1.3.2
        scmrepo = 0.1.6
Supports:
        azure (adlfs = 2023.1.0, knack = 0.10.1, azure-identity = 1.12.0),
        gdrive (pydrive2 = 1.15.0),
        gs (gcsfs = 2022.11.0),
        hdfs (fsspec = 2022.11.0, pyarrow = 10.0.1),
        http (aiohttp = 3.8.3, aiohttp-retry = 2.8.3),
        https (aiohttp = 3.8.3, aiohttp-retry = 2.8.3),
        oss (ossfs = 2023.1.0),
        s3 (s3fs = 2022.11.0, boto3 = 1.24.59),
        ssh (sshfs = 2023.1.0),
        webdav (webdav4 = 0.9.8),
        webdavs (webdav4 = 0.9.8),
        webhdfs (fsspec = 2022.11.0)
Cache types: hardlink, symlink
Cache directory: ext4 on /dev/mapper/ubuntu--vg-ubuntu--lv
Caches: local
Remotes: None
Workspace directory: ext4 on /dev/mapper/ubuntu--vg-ubuntu--lv
Repo: dvc, git

@ReveStobinson does this issue happen all the time (after reloading the window) or only directly after running dvc init?

@mattseddon Sorry, I wasn't clear. This issue is persistent with DVC in this project, reloading/restarting doesn't help. I suspect this is related to the file structure of my multi-root workspace. I just tested out opening the ml_training folder itself in VSCode, and there was only one DVC entry in Source Control.

For some additional details, this is what my directory structure looks like:
📦 project_folder/
 ├─ 📂ml_training/
 │  ├─ 📂.dvc/
 │  ├─ 📂other_subfolders/
 │  ├─ 📜files.ext
 │  └─ 📜files.ext
 ├─ 📂internal_utils/
 │  ├─ 📂subfolders/
 │  ├─ 📜stuff.ext
 │  └─ 📜helpers.ext
 ├─ 📂data/
 │  ├─ 📂dataset1/
 │  ├─ 📂dataset2/
 ├─ 📂.vscode/
 │  ├─ 📜launch.json
 │  ├─ 📜settings.json
 │  └─ 📜project.code-workspace
 ├─ 📜files.ext
 └─ 📜files.ext

My project.code-workspace file:
{
  "folders": [
    {
       "path": "../ml_training"
    },
    {
       "path": "../data"
    },
    {
       "path": "../internal_utils"
    },
    {
       "name": "root",
       "path": "../."
    },
  ]
}

And the project's settings.json :
{
    "files.exclude": {
        "[!.]*/*": true,
        "ml_training": true,
        "internal_utils": true,
        "data": true,
    }
}

I did at one point also have the project.code_workspace file directly in the project directory, and without the ../ in front of the paths in the settings.json, but the results were exactly the same.
I'm sure this is a somewhat non-standard way of organizing a project, but VSCode is able to only show one Git repo for ml_training here, so it should be possible for the DVC extension as well.

Questions:

Is the ml_training training folder available under the root path in your multi-root setup?
If the answer to 1 is yes - Purely out of curiosity, what benefits do you get from setting up your workspace like this?

I have merged a potential fix and I'm in the process of merging down some other changes. I'll ship an update shortly, will let you know when it is live in the marketplace so you can test it out.

The new version should be available now

@mattseddon Just updated my extension and it appears to have fixed the issue!
To answer your questions: In terms of pure file structure, ml_training does technically exist under the root path in my current setup. However, I've hidden it from the Explorer Pane with the files.exclude setting in my settings.json that I also provided above, though I know that a lot of extensions etc. won't properly account for that.
I'm aware that the simpler solution here would be to just open the project folder instead, but the problem that creates is that ml_training and internal_utils require different environments, and VSCode isn't currently capable of accounting for that in a meaningful way, though the feature request is supposedly being worked on. I mostly have this setup to make it easier to isolate my environments, and to prevent me from having to create an extra folder and move other files and workspace settings, etc. into it. The biggest pain there would be moving my launch.json files (I have multiple), since they use a lot of relative filepaths because they need to be portable to other machines with the same file structure.
I don't particularly like this solution, but it's unfortunately the one I'm stuck with for now. Hoping to be able to move things around soon, though.


Translate SwordWorld, SwordWorld2.0 and SwordWorld2.5 to Simplified Chinese

Hello, I've added the SwordWorld、SwordWorld2.0 Simplified Chinese. I am not very familiar with GitHub,  if you find any issues or have any suggestions, please let me know！

and also SwordWorld2.5！

@asterson
Awesome!
Thank you translating.


Retain table header root when duplicating

When duplicating a table, the header in a column doesn't remain the same. If its in a folder however, it is fine.

My only use case was when duplicating a table and i wanted to keep the original header variable names because they were pretty long, so i could just change 1 character in the header table instead of re-writing the header.

Keeping the original header names is a good idea.


MM_V0.0.312 Crashes when trying to visualize annotated MS2 spectra

When I try to visualize the annotated MS2 results from a search, the program crashes when I click on a peptide spectra.

thanks kyle. i'll check this quick and see if i can reproduce the error.

i'm not getting an error.  Can you tell us a little more about your search? Maybe we could run a search with one of your files?

Thanks for the help! Here is a screen shot of the error in case it helps.
[cid:6591fc0d-3ed2-4ab6-acab-1d8da7806a60]

Kyle A. Brown, PhD
Department of Surgery
University of Wisconsin-Madison

From: trishorts<EMAIL_ADDRESS>Sent: Monday, November 9, 2020 1:56 PM
To: smith-chem-wisc/MetaMorpheus<EMAIL_ADDRESS>Cc: KYLE A BROWN<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [smith-chem-wisc/MetaMorpheus] MM_V0.0.312 Crashes when trying to visualize annotated MS2 spectra (#1974)
thanks kyle. i'll check this quick and see if i can reproduce the error.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/smith-chem-wisc/MetaMorpheus/issues/1974#issuecomment-724243351, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARWFY26KLU657SY2CHR5RZ3SPBCQLANCNFSM4TPZCA4A.

somehow your screenshot didn't come through

Just a note that this is resolved. It occurred because there was a period in the spectra file name. Fixed in #1976 .


Investiate development platforms

Whilst I'd rather do this in .NET  - it would be nice to be cross platform. So Electron is looking the most suitable candicate.
Another option is Avalonia, which was suggested on Twitter by @gep13.

A few other options based on a Google search (basically because I'd much rather do it in .NET):

Electron.NET (tutorial blog post)
Eto
DevZH.UI + libui

I also worry that it could look more ugly by making it xplat, and will also open up more maintenance work and require me to start testing on all 3 platforms. Personally, I only care about it being on Windows. It would be nice to be xplat - but I have a feeling that I might regret it.

Although, just been playing around with Electron, and this is pretty easy and looks really nice. Whilst I really wanted to do this in .NET - if it's going to be xplat - this feels like a really good solution. Took me about a minute to add a tomato system tray icon...

Right - going to go with this. Means it's xplat, so is usable by more people. Looks pretty nice xplat - I mean, vscode! It also gives me an excuse to play with Electron, as I've been meaning to do so for a while.

Interested in your dev stack. So I suppose you will go with a web stack? Which one ? (javascript/typescript? and angular/react/vue or pure vanilla?)

@Odonno As simple as possible. It's primarily going to have the following components ...

System Tray icon (showing countdown), with rightclick menu
Settings dialogbox
Floating window showing countdown (optionally visible by user)

I'm new to Electron, by background is .NET - both web and desktop. Electron feels the best choice though - so I'm currently doing a bit of reading / Pluralsighting on Electron before architecting it. I have Angular experience though - so if non-vanilla makes sense, this is the most likely. Also, if Typescript is do-able - definitely.

@Odonno Also, will look into Vue to see if this makes sense too. Been hearing a lot about this recently - so definitely want to see what all the fuss is about! I believe it's more lightweight too - so might work well.

Good to know. Seems not too much UI. Currently, the most hype framework is Inferno: a React-like library of 9kb which is the fastest framework (after vanillajs of course).
No current experience in vuejs. May also be a good time to start. :)
Anyway, I let you dig into it.


Turing build error:  could not import MCMCChains.AbstractChains into Turing

First of all, best wishes for safety and wellbeing.
[ Info: Precompiling Turing [fce5fe82-541a-59a6-adf8-730c64b5f9a0]
WARNING: could not import MCMCChains.AbstractChains into Turing
ERROR: LoadError: LoadError: UndefVarError: AbstractChains not defined
Stacktrace:
 [1] include(::Module, ::String) at .\Base.jl:377
 [2] include(::String) at C:\Users\.....\.julia\packages\Turing\xFzfF\src\Turing.jl:1
 [3] top-level scope at C:\Users\....\.julia\packages\Turing\xFzfF\src\Turing.jl:124
 [4] include(::Module, ::String) at .\Base.jl:377
 [5] top-level scope at none:2
 [6] eval at .\boot.jl:331 [inlined]
 [7] eval(::Expr) at .\client.jl:449
 [8] top-level scope at .\none:3
in expression starting at C:\Users\-...\.julia\packages\Turing\xFzfF\src\utilities\Utilities.jl:6
in expression starting at C:\Users\...\.julia\packages\Turing\xFzfF\src\Turing.jl:124
ERROR: Failed to precompile Turing [fce5fe82-541a-59a6-adf8-730c64b5f9a0] to C:\Users\........\.julia\compiled\v1.4\Turing\gm4QC_xLDiA.ji.
Stacktrace:
 [1] error(::String) at .\error.jl:33
 [2] compilecache(::Base.PkgId, ::String) at .\loading.jl:1272
 [3] _require(::Base.PkgId) at .\loading.jl:1029
 [4] require(::Base.PkgId) at .\loading.jl:927
 [5] require(::Module, ::Symbol) at .\loading.jl:922
``
My system and Environment;

`` julia> versioninfo()
Julia Version 1.4.0
Commit b8e9a9ecc6 (2020-03-21 16:36 UTC)
Platform Info:
  OS: Windows (x86_64-w64-mingw32)
  CPU: Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-8.0.1 (ORCJIT, skylake)
Environment:
  JULIA_MATHKERNEL = C:\Program Files\Wolfram Research\Wolfram Engine\12.0\MathKernel.exe
  JULIA_MATHLINK = C:\Program Files\Wolfram Research\Wolfram Engine\12.0\SystemFiles\Activation\Windows-x86-64\ml64i4.dll ``

A package in your environment is prohibiting you from using the most recent version of Turing, 0.10.1. Try typing ] add<EMAIL_ADDRESS>to see which packages are doing this.

@cpfiffer Thank you for your reply. Here is the outcome;
(@v1.4) pkg> add<EMAIL_ADDRESS> Resolving package versions... ERROR: Unsatisfiable requirements detected for package Bijectors [76274a88]:  Bijectors [76274a88] log:  ├─possible versions are: [0.1.0, 0.2.0, 0.2.5-0.2.9, 0.3.0-0.3.2, 0.4.0, 0.5.0-0.5.2, 0.6.0-0.6.6] or uninstalled  ├─restricted by compatibility requirements with Turing [fce5fe82] to versions: 0.6.4-0.6.6  │ └─Turing [fce5fe82] log:  │   ├─possible versions are: [0.5.0-0.5.1, 0.6.0-0.6.2, 0.6.4-0.6.9, 0.6.11-0.6.15, 0.6.17-0.6.19, 0.6.21-0.6.23, 0.7.0-0.7.4, 0.8.0-0.8.3, 0.9.0-0.9.2, 0.10.0-0.10.1] or uninstalled  │   └─restricted to versions 0.10.1 by an explicit requirement, leaving only versions 0.10.1  └─restricted by compatibility requirements with Compat [34da2185] to versions: [0.1.0, 0.2.0, 0.2.5-0.2.9, 0.3.0-0.3.2, 0.4.0, 0.5.0-0.5.2] or uninstalled — no versions left    └─Compat [34da2185] log:      ├─possible versions are: [1.0.0-1.0.1, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0-1.5.1, 2.0.0, 2.1.0, 2.2.0, 3.0.0, 3.1.0, 3.2.0, 3.3.0-3.3.1, 3.4.0, 3.5.0, 3.6.0, 3.7.0, 3.8.0] or uninstalled      ├─restricted by compatibility requirements with LIBSVM [b1bec4e5] to versions: [1.0.0-1.0.1, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0-1.5.1, 2.0.0, 2.1.0, 2.2.0, 3.0.0, 3.1.0, 3.2.0, 3.3.0-3.3.1, 3.4.0, 3.5.0, 3.6.0, 3.7.0, 3.8.0]      │ └─LIBSVM [b1bec4e5] log:      │   ├─possible versions are: [0.2.0, 0.3.0-0.3.1, 0.4.0] or uninstalled      │   └─restricted to versions * by an explicit requirement, leaving only versions [0.2.0, 0.3.0-0.3.1, 0.4.0]      └─restricted by compatibility requirements with Suppressor [fd094767] to versions: [1.0.0-1.0.1, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0-1.5.1, 2.0.0, 2.1.0, 2.2.0]        └─Suppressor [fd094767] log:          ├─possible versions are: 0.1.1 or uninstalled          └─restricted to versions * by SpineInterface [0cda1612], leaving only versions 0.1.1            └─SpineInterface [0cda1612] log:              ├─possible versions are: 0.1.0 or uninstalled              └─SpineInterface [0cda1612] is fixed to version 0.1.0

That is incredibly difficult to read without the original formatting. Put your code in three backticks, like this:
```
here is some code
    that maintains all the spacing
```

Things you can do while you fix the formatting:

Remove all your packages and start from a fresh environment, by deleting everything in "C:\Users\your_username\.julia\environments\v1.4\" and then running Julia and calling ] add Turing first.
You can use a local environment by activating the directory you are in with ] activate . and then ] add Turing.
Try updating everything first with ] update.
Manually go through the list of packages that are blocking your update (listed when you call ] add<EMAIL_ADDRESS>and remove them.

In any case you can validate your package version with ] status. If you do not see 0.10.1, you are not in the right spot yet.

Thank you for your prompt response. Here it is;
Updating registry at `C:\Users\....\.julia\registries\General`
   Updating git-repo `https://github.com/JuliaRegistries/General.git`
  Resolving package versions...
ERROR: Unsatisfiable requirements detected for package Bijectors [76274a88]:
 Bijectors [76274a88] log:
 ├─possible versions are: [0.1.0, 0.2.0, 0.2.5-0.2.9, 0.3.0-0.3.2, 0.4.0, 0.5.0-0.5.2, 0.6.0-0.6.6] or uninstalled
 ├─restricted by compatibility requirements with Turing [fce5fe82] to versions: 0.6.4-0.6.6
 │ └─Turing [fce5fe82] log:
 │   ├─possible versions are: [0.5.0-0.5.1, 0.6.0-0.6.2, 0.6.4-0.6.9, 0.6.11-0.6.15, 0.6.17-0.6.19, 0.6.21-0.6.23, 0.7.0-0.7.4, 0.8.0-0.8.3, 0.9.0-0.9.2, 0.10.0-0.10.1] or uninstalled
 │   └─restricted to versions 0.10.1 by an explicit requirement, leaving only versions 0.10.1
 └─restricted by compatibility requirements with Compat [34da2185] to versions: [0.1.0, 0.2.0, 0.2.5-0.2.9, 0.3.0-0.3.2, 0.4.0, 0.5.0-0.5.2] or uninstalled — no versions left
   └─Compat [34da2185] log:
     ├─possible versions are: [1.0.0-1.0.1, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0-1.5.1, 2.0.0, 2.1.0, 2.2.0, 3.0.0, 3.1.0, 3.2.0, 3.3.0-3.3.1, 3.4.0, 3.5.0, 3.6.0, 3.7.0, 3.8.0] or uninstalled
     ├─restricted by compatibility requirements with LIBSVM [b1bec4e5] to versions: [1.0.0-1.0.1, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0-1.5.1, 2.0.0, 2.1.0, 2.2.0, 3.0.0, 3.1.0, 3.2.0, 3.3.0-3.3.1, 3.4.0, 3.5.0, 3.6.0, 3.7.0, 3.8.0]
     │ └─LIBSVM [b1bec4e5] log:
     │   ├─possible versions are: [0.2.0, 0.3.0-0.3.1, 0.4.0] or uninstalled
     │   └─restricted to versions * by an explicit requirement, leaving only versions [0.2.0, 0.3.0-0.3.1, 0.4.0]
     └─restricted by compatibility requirements with Suppressor [fd094767] to versions: [1.0.0-1.0.1, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0-1.5.1, 2.0.0, 2.1.0, 2.2.0]
       └─Suppressor [fd094767] log:
         ├─possible versions are: 0.1.1 or uninstalled
         └─restricted to versions * by SpineInterface [0cda1612], leaving only versions 0.1.1
           └─SpineInterface [0cda1612] log:
             ├─possible versions are: 0.1.0 or uninstalled
             └─SpineInterface [0cda1612] is fixed to version 0.1.0

Remove all your packages and start from a fresh environment, by deleting everything in "C:\Users\your_username\.julia\environments\v1.4\" and then running Julia and calling ] add Turing first.

You can use a local environment by activating the directory you are in with ] activate . and then ] add Turing.

Try updating everything first with ] update.

Manually go through the list of packages that are blocking your update (listed when you call ] add<EMAIL_ADDRESS>and remove them.

Did you try any of the above?

@cpfiffer  Yes. I did all, except the first bullet point, with no success.

The second bullet point should have solved your problem with certainty, and the fourth definitely should have, so I don't think they were done correctly. I would do the first because it is essentially fool-proof.

@cpfiffer,  It seems the main issue is that Turing could not import MCMCChains.AbstractChains into Turing while building.

Yes, and I have provided you numerous fixes for that problem.

The problem is Suppressor, it is not compatible with Compat 3.x which the latest Bijectors used by the latest Turing requires.

It seems Suppressor wasn't updated for a long time.

@mohamed82008  thanks for your reply. Actually it seems Suppressor updating/building as copied below. But Turing does give the same error.
  Resolving package versions...
   Updating `C:\Users\....\.julia\environments\v1.4\Project.toml`
  [fd094767] + Suppressor v0.1.1
   Updating `C:\Users\....\.julia\environments\v1.4\Manifest.toml`
 [no changes]

(@v1.4) pkg> up Suppressor
   Updating registry at `C:\Users\....\.julia\registries\General`
   Updating git-repo `https://github.com/JuliaRegistries/General.git`
   Updating `C:\Users\...\.julia\environments\v1.4\Project.toml`
 [no changes]
   Updating `C:\Users\......\.julia\environments\v1.4\Manifest.toml`
  [0bf59076] ↓ AdvancedHMC v0.2.21 ⇒ v0.2.7
  [4c555306] ↑ ArrayLayouts v0.1.5 ⇒ v0.2.0
  [aae01518] ↑ BandedMatrices v0.14.3 ⇒ v0.15.0
  [764a87c0] ↓ BoundaryValueDiffEq v2.4.0 ⇒ v2.3.0
  [781609d7] + GMP_jll v6.1.2+5
  [5078a376] ↑ LazyArrays v0.15.1 ⇒ v0.16.0
  [2ce0c516] + MPC_jll v1.1.0+0
  [3a97d323] + MPFR_jll v4.0.2+2
  [123dc426] ↑ SymEngine v0.7.1 ⇒ v0.8.0
  [3428059b] + SymEngine_jll v0.6.0+0
  [e88e6eb3] ↓ Zygote v0.4.12 ⇒ v0.4.8

(@v1.4) pkg> build Suppressor

julia> using Suppressor

(@v1.4) pkg> build Turing

No you should remove Suppressor.

@mohamed82008 Thanks. removed but does not help Turing building.  It seems Turing is not ready for use. I will leave it there and switch to ````Stan.jl ```

You need to update after removing suppressor. FYI, the problem is not Turing here, it is your package environment.

Try ]add<EMAIL_ADDRESS>after removing Suppressor.

It seems Turing is not ready for use. I will leave it there and switch to Stan.jl

There are a number of people out there using Turing so it is ready for use, but of course you are free to switch to Stan any time, good luck :)

Following option 2 from https://github.com/TuringLang/Turing.jl/issues/1195#issuecomment-606107330, you will have below:
(base) ➜  tmp julia-1.4
               _
   _       _ _(_)_     |  Documentation: https://docs.julialang.org
  (_)     | (_) (_)    |
   _ _   _| |_  __ _   |  Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 1.4.0 (2020-03-21)
 _/ |\__'_|_|_|\__'_|  |  Official https://julialang.org/ release
|__/                   |

(@v1.4) pkg> activate .
 Activating new environment at `~/projects/tmp/Project.toml`

(tmp) pkg> st
Status `~/projects/tmp/Project.toml`
  (empty environment)

(tmp) pkg> add Turing
   Updating registry at `~/.julia/registries/General`
   Updating git-repo `https://github.com/JuliaRegistries/General.git`
  Resolving package versions...
   Updating `~/projects/tmp/Project.toml`
  [fce5fe82] + Turing v0.10.1
   Updating `~/projects/tmp/Manifest.toml`
  [621f4979] + AbstractFFTs v0.5.0
  [80f14c24] + AbstractMCMC v0.5.6
  [1520ce14] + AbstractTrees v0.3.2
  [79e6a3ab] + Adapt v1.0.1
  [0bf59076] + AdvancedHMC v0.2.21
  [5b7e9947] + AdvancedMH v0.4.1
  [dce04be8] + ArgCheck v2.0.0
  [7d9fca2a] + Arpack v0.4.0
  [68821587] + Arpack_jll v3.5.0+2
  [4fba245c] + ArrayInterface v2.6.2
  [4c555306] + ArrayLayouts v0.1.5
  [39de3d68] + AxisArrays v0.4.2
  [6e4b80f9] + BenchmarkTools v0.5.0
  [76274a88] + Bijectors v0.6.6
  [b99e7846] + BinaryProvider v0.5.8
  [861a8166] + Combinatorics v1.0.0
  [bbf7d656] + CommonSubexpressions v0.2.0
  [34da2185] + Compat v3.8.0
  [e66e0078] + CompilerSupportLibraries_jll v0.3.3+0
  [88cd18e8] + ConsoleProgressMonitor v0.1.2
  [9a962f9c] + DataAPI v1.1.0
  [864edb3b] + DataStructures v0.17.10
  [163ba53b] + DiffResults v1.0.2
  [b552c78f] + DiffRules v1.0.1
  [31c24e10] + Distributions v0.23.2
  [ced4e74d] + DistributionsAD v0.4.9
  [ffbed154] + DocStringExtensions v0.8.1
  [366bfd00] + DynamicPPL v0.5.0
  [da5c29d0] + EllipsisNotation v0.4.0
  [cad2338a] + EllipticalSliceSampling v0.2.1
  [7a1cc6ca] + FFTW v1.2.0
  [f5851436] + FFTW_jll v3.3.9+5
  [1a297f60] + FillArrays v0.8.6
  [59287772] + Formatting v0.4.1
  [f6369f11] + ForwardDiff v0.10.10
  [069b7b12] + FunctionWrappers v1.1.1
  [7869d1d1] + IRTools v0.3.1
  [505f98c9] + InplaceOps v0.3.0
  [1d5cc7b8] + IntelOpenMP_jll v2018.0.3+0
  [8197267c] + IntervalSets v0.4.0
  [c8e1da08] + IterTools v1.3.0
  [682c06a0] + JSON v0.21.0
  [5078a376] + LazyArrays v0.15.1
  [1d6d02ad] + LeftChildRightSiblingTrees v0.1.2
  [6f1fad26] + Libtask v0.3.3
  [6fdf6af0] + LogDensityProblems v0.10.3
  [e6f89c97] + LoggingExtras v0.4.0
  [c7f686f2] + MCMCChains v3.0.8
  [856f044c] + MKL_jll v2019.0.117+2
  [1914dd2f] + MacroTools v0.5.5
  [dbb5928d] + MappedArrays v0.2.2
  [e1d29d7a] + Missings v0.4.3
  [872c559c] + NNlib v0.6.6
  [77ba4419] + NaNMath v0.3.3
  [4536629a] + OpenBLAS_jll v0.3.9+0
  [efe28fd5] + OpenSpecFun_jll v0.5.3+3
  [bac558e1] + OrderedCollections v1.1.0
  [90014a1f] + PDMats v0.9.12
  [d96e819e] + Parameters v0.12.0
  [69de0a69] + Parsers v1.0.0
  [f27b6e38] + Polynomials v0.6.1
  [33c8b6b6] + ProgressLogging v0.1.2
  [92933f4c] + ProgressMeter v1.2.0
  [1fd47b50] + QuadGK v2.3.1
  [b3c3ace0] + RangeArrays v0.3.2
  [3cdcf5f2] + RecipesBase v0.8.0
  [189a3867] + Reexport v0.2.0
  [ae029012] + Requires v1.0.1
  [37e2e3b7] + ReverseDiff v1.1.0
  [79098fc4] + Rmath v0.6.1
  [f50d1b31] + Rmath_jll v0.2.2+0
  [f2b01f46] + Roots v1.0.1
  [a2af1166] + SortingAlgorithms v0.3.1
  [276daf66] + SpecialFunctions v0.10.0
  [90137ffa] + StaticArrays v0.12.1
  [2913bbd2] + StatsBase v0.32.2
  [4c63d2b9] + StatsFuns v0.9.4
  [5d786b92] + TerminalLoggers v0.1.1
  [9f7883ad] + Tracker v0.2.6
  [84d833dd] + TransformVariables v0.3.8
  [fce5fe82] + Turing v0.10.1
  [e88e6eb3] + Zygote v0.4.12
  [700de1a5] + ZygoteRules v0.2.0
  [2a0f44e3] + Base64
  [ade2ca70] + Dates
  [8bb1440f] + DelimitedFiles
  [8ba89e20] + Distributed
  [b77e0a4c] + InteractiveUtils
  [76f85450] + LibGit2
  [8f399da3] + Libdl
  [37e2e46d] + LinearAlgebra
  [56ddb016] + Logging
  [d6f4376e] + Markdown
  [a63ad114] + Mmap
  [44cfe95a] + Pkg
  [de0858da] + Printf
  [3fa0cd96] + REPL
  [9a3f8284] + Random
  [ea8e919c] + SHA
  [9e88b42a] + Serialization
  [1a1011a3] + SharedArrays
  [6462fe0b] + Sockets
  [2f01184e] + SparseArrays
  [10745b16] + Statistics
  [4607b0f0] + SuiteSparse
  [8dfed614] + Test
  [cf7118a7] + UUIDs
  [4ec0a83e] + Unicode

julia> using Turing
[ Info: Precompiling Turing [fce5fe82-541a-59a6-adf8-730c64b5f9a0]
   Building Libtask → `~/.julia/packages/Libtask/K7OAU/deps/build.log`

julia>

After this Turing is ready to use.
In the meanwhile, I suggest you spent some time learning how to deal with the environment in Julia. Some intro materials are available at https://julialang.github.io/Pkg.jl/stable/environments/ and https://docs.julialang.org/en/v1/stdlib/Pkg/. It's quite necessary to understand how it works in order to use Julia efficiently and properly.

Closing this for now. @uozden feel free to re-open the issue if the above solutions don't work for you.

@cpfiffer @mohamed82008  @xukai92 Thank you very much. I have solved the problem with your  kind help


fix license copyright year, fix headers, use variables

Just some small fixes.

Not merging this in—we're not developing against master anymore. Made the date changes in 2.0-wip.

THIS IS ON 2.0-wip! Seriously, this is now the second time I've had something rejected cause you didn't pay attention to the diff.

Is typeahead.js in master? Geez.

hahaha.. that was epic failed..

https://github.com/twitter/bootstrap/issues/1009


Optimised images.

Saved 91 KB out of 762 KB. 20.5% per file on average (up to 56.8%).
For every file, ImageOptim compared the different tools and picked the smallest file that was produced by a combination of advpng, pngout and zopfli for PNGs, svgo for SVGs and gifsicle for GIFs.
No related issues, no code change, no functionality change, no visual differences in images (compression is lossless).

This seems ok, but a bunch of these images aren't used anymore and we should just remove them anyway.  Some thoughts:

The 2x cursors don't seem to be used currently.  (we should fix that)
Really the only things that matter for optimization are the assets in dist/
Everything under docs/ is very old and needs to go away or be redone
The one svg/iD-sprite.src.svg file definitely does not need to be optimized, because it's an intermediate step generated file.  It's later used to generate a different file which contains <symbol> elements in dist/img/iD-sprite.svg as part of the build process
We've had issues with svgo optimizing away our symbol spritesheet.  I opened an issue svg/svgo#743  - anyway just be careful using svgo, some of the rules are disabled on openstreetmap-website because of this bug.

Can you change this PR to be just the images under dist/

Happy to! I'll try to get around to it today.

Couldn't most of those images in dist/ be SVGs? Do we still have the vector source for them somewhere?

Couldn't most of those images in dist/ be SVGs? Do we still have the vector source for them somewhere?

We already went through in #2785 and moved most of the image assets into the SVG spritesheet.

We can't switch the cursors because not all browsers support SVG cursors (see #2785)
I'm not sure whether we can switch the patterns or not.  They are small anyway, and there might be some browser compatibility issues (see comments around https://github.com/openstreetmap/iD/blob/master/modules/svg/areas.js#L11-L41), so it hasn't been worth it to me to investigate.
We can't switch animated objects like the loading spinners
We can switch the traffic signs used by Mapillary to SVG, and this is being tracked on #4145
arrow-icon.png is not used and can be removed (I think)

I think that covers everything!

https://github.com/yangshun/awesome-spinners has some cool non-gif spinners, and the current spinner isn't optimised for retina. Maybe I'll take that as a project for a hacking weekend :).
Could this be merged now as it is?

We can't switch animated objects like the loading spinners

Another thought on this:  technically, we can but it's not a drop in replacement, and probably not worth it to redo the image and wire up a css transform and sort out all the cross browser issues, just to have a  loading spinner that takes up a bit less space and looks a little nicer on retina displays.  If you want to ImageOptim them though, that's cool.

https://github.com/yangshun/awesome-spinners has some cool non-gif spinners, and the current spinner isn't optimised for retina. Maybe I'll take that as a project for a hacking weekend :).

Cool, yeah if you really want to do this, I won't say no 👍
Watch out for <animateTransform> which isn't supported on IE

I took a look and this seems fine, thanks @grischard 👍


More flexible way to create annotation legend

In earlier versions, you provided a way for us (IntAct at least) to create our own legend based on the annotation legend.
Now you do all of that by yourself and it is really nice, but it doesn't really match the specific needs for IntAct for instance, as the complex is really an interaction, and we don't need the intact_ before the ac.
I think you suited the annotations for the complex portal needs (which is really appreciated), but then for IntAct, or I guess any other users, it would be great if we could customise or create our own legends.
Right now, I fixed it on my side by replacing the terms I didn't want with jquery whenever the legend is updated, but it's not really a proper way to do it. (e.g. in interaction details).
I see several options for these problems:

Fire events when the annotation is changed with the different annotations colours with their data (Solution used before I think)
Create an "AnnotationLegendRenderer" interface that takes the data as input and produce the legend, take the current version as the default implementation, and give the possibility to set the renderer and maybe to inherit the default one make our own
Give the ability to provide functions for the annotation groups and titles, and apply them in your current "renderer". It would make a signature like this I think:

viewer.addColorSchemeKey(location: DOMElement,
                groupTitleModifier: (groupTitle: string) => string = groupTitle => groupTitle,
                annotNameModifier: (annotName: string) => string = annotName => annotName
                )

(The default unity function being there to allow not to provide those functions by default, and yet apply them in your renderer without any impact)
What do you think of all that?

By the way sorry, I am working with typescript on Angular, and I don't think that there is really notions of interface or such kind of things with proper js, but I think we could still find a way to make one of these solution work in plain old js

you can get the current feature colour scheme with
viewer.getFeatureColors();
its a d3 color scale
the colour scheme can only change by the choice of annotations being changed, so you already know about this on your side?

If I observed well, the index begins at 5 for the colour range. That's fine.
However, how can I get the colour scheme used for the complexes? Because I've been looping over the whole feature range and I couldn't find the complex colour (I could use a static one for now since we only show one complex at a time, but when we will expand interaction's complexes, the problem will be there ...)

Nevermind, it's getComplexColors(), thank you very much
It should be more than enough for our needs 😄

Actually, there is one problem with this: knowing the corresponding annotation. I can browse the MIJson as you do for collecting interaction names and MI Features, but for the one that you query on your side (UniProt and SuperFamily), I would need to query them as well on my side, and it's not the best in terms of optimisation ...
We could disable the other annotations type, but they are really nice features I think, so I would prefer to keep them ...
A solution could be to return an object like this when we set/show an annotation type, depending on what is actually shown
{
  "Complex": [
    {name: "intact_EBI-1004454", color:"#aec4f"}
  ],
 "MI Features": [
    {name: "bla", color:"#xxxxxx"},
    {name: "blabla", color:"#yyyyyy"},
  ]
}

yep, you're right.
the information is stored in the proteins, the confusing code where I get it back out to make the legend is here: https://github.com/MICommunity/ComplexViewer/blob/bc89b81a55774311e2c742068b802d62f51cee03/src/js/color-scheme-key.js#L32-#L49
I think returning an object from the set/show annotation function just like you say is best solution, it sorts out something that's kind of a mess.
(should probably also have a getter function that returns same thing, also removes the need for this getComplexColours function so I'll take that out)

Hi @EliotRagueneau - happy new year.
I made some changes along the lines of what we discussed - not super thoroughly tested but let me know how you get on, and any other suggested changes you have.

A solution could be to return an object like this when we set/show an annotation type

Ok, it does this now. There's no way to register a listener for colour scheme changes, might be nice to have but think we maybe don't actually need it? (The old stuff to do with ComplexViewer generating legends in div's is still there but should maybe be removed.)

Hi @EliotRagueneau - happy new year.
I made some changes along the lines of what we discussed - not super thoroughly tested but let me know how you get on, and any other suggested changes you have.

A solution could be to return an object like this when we set/show an annotation type

Ok, it does this now. There's no way to register a listener for colour scheme changes, might be nice to have but think we maybe don't actually need it? (The old stuff to do with ComplexViewer generating legends in div's is still there but should maybe be removed.)

Hi @colin-combe, happy new year to you too!
I'll test that and give you feedback, but that looks awesome 😄 .

Hi @colin-combe, happy new year to you too!
I'll test that and give you feedback, but that looks awesome 😄 .

OK so as I said in the other issue, we tested the new functionalities and its awesome. One thing we could maybe improve for this legend is to tell whether the colour should be hatched or not in the legend, so that it really reflects what's on the viewer.
Otherwise, it's already much better to customise the legend this way, thank you very much!

OK so as I said in the other issue, we tested the new functionalities and its awesome. One thing we could maybe improve for this legend is to tell whether the colour should be hatched or not in the legend, so that it really reflects what's on the viewer.
Otherwise, it's already much better to customise the legend this way, thank you very much!

One thing we could maybe improve for this legend is to tell whether the colour should be hatched or not in the legend, so that it really reflects what's on the viewer.

Yep, you're sort of right about that. But also the colour for a certain feature could be both hatched and unhatched - the certain regions are unhatched and the uncertain are hatched, some have both:-

Also, it looks like I made the colour for the hatched areas slightly lighter.
I think you're right that this could be better. Maybe show both hatched and unhatched in legend? I guess what you would ideally want in that json is info on whether the colour appears hatched, unhatched, or both.

One thing we could maybe improve for this legend is to tell whether the colour should be hatched or not in the legend, so that it really reflects what's on the viewer.

Yep, you're sort of right about that. But also the colour for a certain feature could be both hatched and unhatched - the certain regions are unhatched and the uncertain are hatched, some have both:-

Also, it looks like I made the colour for the hatched areas slightly lighter.
I think you're right that this could be better. Maybe show both hatched and unhatched in legend? I guess what you would ideally want in that json is info on whether the colour appears hatched, unhatched, or both.

I guess what you would ideally want in that json is info on whether the colour appears hatched, unhatched, or both.

Yes, that would be perfect to have this information in the JSON.
I thought that the lighter tone was just an optical illusion but apparently it's not, do you want to keep it this way (which looks nice)? If so, I guess we'll need the colour used for the hatching in the JSON too.

I guess what you would ideally want in that json is info on whether the colour appears hatched, unhatched, or both.

Yes, that would be perfect to have this information in the JSON.
I thought that the lighter tone was just an optical illusion but apparently it's not, do you want to keep it this way (which looks nice)? If so, I guess we'll need the colour used for the hatching in the JSON too.

If so, I guess we'll need the colour used for the hatching in the JSON too.

lets keep it and lighten the hatches in the legend, as you say
(i made the hatched areas lighter so they were less jarring to look at, a more consistent thing might have been to lighten both hatched and unhatched areas, but I think i tried that and decided the darker colours were better for unhatched areas...)
so, I'll add that info to the json

If so, I guess we'll need the colour used for the hatching in the JSON too.

lets keep it and lighten the hatches in the legend, as you say
(i made the hatched areas lighter so they were less jarring to look at, a more consistent thing might have been to lighten both hatched and unhatched areas, but I think i tried that and decided the darker colours were better for unhatched areas...)
so, I'll add that info to the json

That's awesome thanks!

That's awesome thanks!

bear with me Eliot... next week for this

Thank you, Colin!
Unfortunately, I'm no longer working for IntAct but for Reactome now, but I'm sure Noe will take good care of all this.

it's now done as @EliotRagueneau suggested, you can see it as complexviewer.org
I think its better, so thanks

It's really a good result, thank you very much!


SourceMap assets respond code error.

Do NOT ignore this template or your issue will have a very high chance to be closed without comment.

Describe the bug
when referencing css and js files in index.html, there will be 500 internam error responsed from server when there's sourcemap files relate with them, both in the server console and the browser console. but, in fact, the path is correct, and the file is accessible from browser.
index.html

log in server console:

log in browser console:

the sourcemap is accessible:

related source code hinted from the server console (compiled, from node_modules):

Reproduction
Please provide a link to a repo that can reproduce the problem you ran into.
A reproduction is required unless you are absolutely sure that the the problem is obvious and the information you provided is enough for us to understand what the problem is. If a report has only vague description (e.g. just a generic error message) and has no reproduction, it will be closed immediately.
System Info

required vite version: v0.20.3
required Operating System: win10 v2004 + wsl2
required Node version: v12.14
Optional:

npm/yarn version
Installed vue version (from yarn.lock or package-lock.json)
Installed @vue/compiler-sfc version

Logs (Optional if provided reproduction)

Run vite or vite build with the --debug flag.
Provide the error log here.

when run with --debug, it says:
zwm@x1c:~/workspace/qumake$ npm run dev

><EMAIL_ADDRESS>dev /home/zwm/workspace/qumake
> vite --debug

vite v0.20.3
  vite:config env mode: development +0ms
  vite:config env: {} +1ms
  vite:config config resolved in 94ms +2ms
  vite:optimize Hash is consistent. Skipping. Use --force to override. +0ms

  Dev server running at:
  > Network:  http://<IP_ADDRESS>:3000/
  > Local:    http://localhost:3000/

  vite:server server ready in 369ms. +0ms
  vite:hmr ws client connected +0ms
  vite:hmr ws client connected +19ms
  vite:hmr ws client connected +29ms
  vite:hmr ws client connected +37ms
  vite:hmr ws client connected +19ms
  vite:hmr         / imports /blockly/blockly.min.js +19ms
  vite:hmr         / imports /blockly/browser.js +1ms
  vite:rewrite /: no imports found. +0ms
  vite:hmr         / imports /monaco/min/vs/loader.js +4ms
  vite:hmr         / imports /monaco/min/vs/editor/editor.main.nls.js +2ms
  vite:hmr         / imports /monaco/min/vs/editor/editor.main.js +1ms
  vite:hmr         / imports /main.ts +1ms
  vite:rewrite (skipped) / +7ms
  vite:hmr ws client connected +6ms
  vite:hmr ws client connected +18ms
  vite:rewrite /: serving from cache +0ms
  vite:rewrite (skipped) / +35ms
  vite:hmr ws client connected +18ms
  vite:hmr ws client connected +30ms
  vite:rewrite /: serving from cache +49ms
  vite:rewrite (skipped) / +50ms
  vite:hmr ws client connected +25ms
  vite:rewrite /: serving from cache +19ms
  vite:rewrite (skipped) / +16ms
  vite:hmr ws client connected +20ms
  vite:hmr ws client connected +20ms
  vite:hmr ws client connected +15ms
  vite:rewrite /: serving from cache +53ms
  vite:rewrite (skipped) / +53ms
  vite:hmr ws client connected +17ms
  vite:hmr ws client connected +16ms
  vite:rewrite /: serving from cache +45ms
  vite:rewrite (skipped) / +45ms
  vite:hmr ws client connected +20ms
  vite:rewrite /: serving from cache +13ms
  vite:rewrite (skipped) / +13ms
  vite:hmr ws client connected +14ms
  vite:rewrite /: serving from cache +12ms
  vite:rewrite (skipped) / +11ms
  vite:hmr ws client connected +16ms
  vite:rewrite /: serving from cache +14ms
  vite:rewrite (skipped) / +15ms
  vite:hmr ws client connected +14ms
  vite:rewrite /: serving from cache +14ms
  vite:rewrite (skipped) / +14ms
  vite:hmr ws client connected +16ms
  vite:rewrite /: serving from cache +15ms
  vite:rewrite (skipped) / +15ms
  vite:hmr ws client connected +17ms
  vite:rewrite /: serving from cache +16ms
  vite:rewrite (skipped) / +16ms
  vite:hmr ws client connected +15ms
  vite:rewrite /: serving from cache +15ms
  vite:rewrite (skipped) / +14ms
  vite:hmr ws client connected +18ms
  vite:rewrite /: serving from cache +19ms
  vite:rewrite (skipped) / +20ms
  vite:hmr ws client connected +19ms
  vite:rewrite /: serving from cache +20ms
  vite:rewrite (skipped) / +19ms
  vite:hmr ws client connected +17ms
  vite:rewrite /: serving from cache +17ms
  vite:rewrite (skipped) / +18ms
  vite:hmr ws client connected +14ms
  vite:rewrite /: serving from cache +15ms
  vite:rewrite (skipped) / +15ms
  vite:hmr ws client connected +17ms
  vite:rewrite /: serving from cache +16ms
  vite:rewrite (skipped) / +16ms
  vite:hmr ws client connected +15ms
  vite:rewrite /: serving from cache +15ms
  vite:rewrite (skipped) / +14ms
  vite:hmr ws client connected +17ms
  vite:rewrite /: serving from cache +16ms
  vite:rewrite (skipped) / +17ms
  vite:rewrite /: serving from cache +12ms
  vite:rewrite (skipped) / +11ms
  vite:hmr ws client connected +18ms
  vite:hmr ws client connected +14ms
  vite:rewrite /: serving from cache +23ms
  vite:rewrite (skipped) / +24ms
  vite:hmr ws client connected +17ms
  vite:rewrite /: serving from cache +14ms
  vite:rewrite (skipped) / +14ms
  vite:rewrite /: serving from cache +13ms
  vite:rewrite (skipped) / +12ms
  vite:rewrite (skipped) /style/ress.css +262ms
  vite:rewrite (skipped) /style/color.css +3ms
  vite:rewrite (skipped) /style/icons/css/materialdesignicons.min.css +5ms
  vite:rewrite (skipped) /monaco/min/vs/editor/editor.main.css +25ms
  vite:rewrite /public/blockly/browser.js: no imports found. +44ms
  vite:rewrite /public/blockly/blockly.min.js: no imports found. +34ms
  vite:rewrite /public/monaco/min/vs/loader.js: no imports found. +22ms
  vite:rewrite /public/monaco/min/vs/editor/editor.main.nls.js: no imports found. +5ms
  vite:rewrite /main.ts: rewriting +29ms
  vite:rewrite     "vue" --><EMAIL_ADDRESS>+6ms
  vite:hmr         /main.ts imports<EMAIL_ADDRESS>+453ms
  vite:rewrite     "./App.vue" --> "/App.vue" +3ms
  vite:hmr         /main.ts imports /App.vue +2ms
  vite:rewrite (skipped) /vite/hmr +45ms
  vite:rewrite /public/monaco/min/vs/editor/editor.main.js: no imports found. +60ms

  TypeError: Cannot read property 'includes' of undefined
      at /home/zwm/workspace/qumake/node_modules/vite/dist/server/serverPluginServeStatic.js:25:48
      at dispatch (/home/zwm/workspace/qumake/node_modules/koa-compose/index.js:42:32)
      at /home/zwm/workspace/qumake/node_modules/vite/dist/server/serverPluginAssets.js:11:16
      at dispatch (/home/zwm/workspace/qumake/node_modules/koa-compose/index.js:42:32)
      at /home/zwm/workspace/qumake/node_modules/vite/dist/server/serverPluginJson.js:6:15
      at dispatch (/home/zwm/workspace/qumake/node_modules/koa-compose/index.js:42:32)
      at /home/zwm/workspace/qumake/node_modules/vite/dist/server/serverPluginEsbuild.js:12:15
      at dispatch (/home/zwm/workspace/qumake/node_modules/koa-compose/index.js:42:32)
      at /home/zwm/workspace/qumake/node_modules/vite/dist/server/serverPluginCss.js:17:15
      at dispatch (/home/zwm/workspace/qumake/node_modules/koa-compose/index.js:42:32)

  TypeError: Cannot read property 'includes' of undefined
      at /home/zwm/workspace/qumake/node_modules/vite/dist/server/serverPluginServeStatic.js:25:48
      at dispatch (/home/zwm/workspace/qumake/node_modules/koa-compose/index.js:42:32)
      at /home/zwm/workspace/qumake/node_modules/vite/dist/server/serverPluginAssets.js:11:16
      at dispatch (/home/zwm/workspace/qumake/node_modules/koa-compose/index.js:42:32)
      at /home/zwm/workspace/qumake/node_modules/vite/dist/server/serverPluginJson.js:6:15
      at dispatch (/home/zwm/workspace/qumake/node_modules/koa-compose/index.js:42:32)
      at /home/zwm/workspace/qumake/node_modules/vite/dist/server/serverPluginEsbuild.js:12:15
      at dispatch (/home/zwm/workspace/qumake/node_modules/koa-compose/index.js:42:32)
      at /home/zwm/workspace/qumake/node_modules/vite/dist/server/serverPluginCss.js:17:15
      at dispatch (/home/zwm/workspace/qumake/node_modules/koa-compose/index.js:42:32)

  TypeError: Cannot read property 'includes' of undefined
      at /home/zwm/workspace/qumake/node_modules/vite/dist/server/serverPluginServeStatic.js:25:48
      at dispatch (/home/zwm/workspace/qumake/node_modules/koa-compose/index.js:42:32)
      at /home/zwm/workspace/qumake/node_modules/vite/dist/server/serverPluginAssets.js:11:16
      at dispatch (/home/zwm/workspace/qumake/node_modules/koa-compose/index.js:42:32)
      at /home/zwm/workspace/qumake/node_modules/vite/dist/server/serverPluginJson.js:6:15
      at dispatch (/home/zwm/workspace/qumake/node_modules/koa-compose/index.js:42:32)
      at /home/zwm/workspace/qumake/node_modules/vite/dist/server/serverPluginEsbuild.js:12:15
      at dispatch (/home/zwm/workspace/qumake/node_modules/koa-compose/index.js:42:32)
      at /home/zwm/workspace/qumake/node_modules/vite/dist/server/serverPluginCss.js:17:15
      at dispatch (/home/zwm/workspace/qumake/node_modules/koa-compose/index.js:42:32)

  vite:hmr ws client connected +529ms

  TypeError: Cannot read property 'includes' of undefined
      at /home/zwm/workspace/qumake/node_modules/vite/dist/server/serverPluginServeStatic.js:25:48
      at dispatch (/home/zwm/workspace/qumake/node_modules/koa-compose/index.js:42:32)
      at /home/zwm/workspace/qumake/node_modules/vite/dist/server/serverPluginAssets.js:11:16
      at dispatch (/home/zwm/workspace/qumake/node_modules/koa-compose/index.js:42:32)
      at /home/zwm/workspace/qumake/node_modules/vite/dist/server/serverPluginJson.js:6:15
      at dispatch (/home/zwm/workspace/qumake/node_modules/koa-compose/index.js:42:32)
      at /home/zwm/workspace/qumake/node_modules/vite/dist/server/serverPluginEsbuild.js:12:15
      at dispatch (/home/zwm/workspace/qumake/node_modules/koa-compose/index.js:42:32)
      at /home/zwm/workspace/qumake/node_modules/vite/dist/server/serverPluginCss.js:17:15
      at dispatch (/home/zwm/workspace/qumake/node_modules/koa-compose/index.js:42:32)

  vite:resolve (optimized) vue.js -> node_modules/.vite_opt_cache/vue.js +0ms
  vite:sfc /home/zwm/workspace/qumake/App.vue parsed in 17ms. +0ms
  vite:rewrite /App.vue: rewriting +469ms
  vite:rewrite     "vue" --><EMAIL_ADDRESS>+1ms
  vite:hmr         /App.vue imports<EMAIL_ADDRESS>+47ms
  vite:rewrite     "./components/ZLayout.vue" --> "/components/ZLayout.vue" +3ms
  vite:hmr         /App.vue imports /components/ZLayout.vue +2ms
  vite:rewrite     "./components/ZPreview.vue" --> "/components/ZPreview.vue" +1ms
  vite:hmr         /App.vue imports /components/ZPreview.vue +1ms
  vite:rewrite     "./store.ts" --> "/store.ts" +1ms
  vite:hmr         /App.vue imports /store.ts +1ms
  vite:rewrite<EMAIL_ADDRESS>no imports found. +18ms
  vite:sfc /home/zwm/workspace/qumake/components/ZPreview.vue parsed in 18ms. +49ms
  vite:rewrite /components/ZPreview.vue: rewriting +26ms
  vite:rewrite     "vue" --><EMAIL_ADDRESS>+3ms
  vite:hmr         /components/ZPreview.vue imports<EMAIL_ADDRESS>+47ms
  vite:rewrite     "./ZPhone.vue" --> "/components/ZPhone.vue" +2ms
  vite:hmr         /components/ZPreview.vue imports /components/ZPhone.vue +2ms
  vite:sfc /home/zwm/workspace/qumake/components/ZLayout.vue parsed in 18ms. +29ms
  vite:rewrite /components/ZLayout.vue: rewriting +22ms
  vite:rewrite     "./ZMenuCourse.vue" --> "/components/ZMenuCourse.vue" +1ms
  vite:hmr         /components/ZLayout.vue imports /components/ZMenuCourse.vue +22ms
  vite:rewrite     "./ZMenuUser.vue" --> "/components/ZMenuUser.vue" +1ms
  vite:hmr         /components/ZLayout.vue imports /components/ZMenuUser.vue +2ms
  vite:sfc /home/zwm/workspace/qumake/App.vue parse cache hit +7ms
  vite:sfc /App.vue style compiled in 25ms +29ms
  vite:rewrite (skipped) /App.vue?type=style&index=0 +34ms
  vite:sfc /home/zwm/workspace/qumake/App.vue parse cache hit +2ms
  vite:sfc /App.vue template compiled in 25ms. +26ms
  vite:rewrite (skipped) /App.vue?type=template +28ms
  vite:sfc /home/zwm/workspace/qumake/components/ZPhone.vue parsed in 21ms. +27ms
  vite:rewrite /components/ZPhone.vue: rewriting +30ms
  vite:rewrite     "vue" --><EMAIL_ADDRESS>+3ms
  vite:hmr         /components/ZPhone.vue imports<EMAIL_ADDRESS>+94ms
  vite:sfc /home/zwm/workspace/qumake/components/ZPreview.vue parse cache hit +9ms
  vite:sfc /components/ZPreview.vue style compiled in 16ms +17ms
  vite:rewrite (skipped) /components/ZPreview.vue?type=style&index=0 +20ms
  vite:sfc /home/zwm/workspace/qumake/components/ZPreview.vue parse cache hit +3ms
  vite:sfc /components/ZPreview.vue template compiled in 15ms. +16ms
  vite:rewrite (skipped) /components/ZPreview.vue?type=template +19ms
  vite:rewrite /store.ts: rewriting +1ms
  vite:rewrite     "vue" --><EMAIL_ADDRESS>+2ms
  vite:hmr         /store.ts imports<EMAIL_ADDRESS>+42ms
  vite:sfc /home/zwm/workspace/qumake/components/ZMenuCourse.vue parsed in 18ms. +33ms
  vite:rewrite /components/ZMenuCourse.vue: rewriting +30ms
  vite:rewrite     "./element/Triangle.vue" --> "/components/element/Triangle.vue" +1ms
  vite:hmr         /components/ZMenuCourse.vue imports /components/element/Triangle.vue +31ms
  vite:rewrite     "./ZStepListItem.vue" --> "/components/ZStepListItem.vue" +0ms
  vite:hmr         /components/ZMenuCourse.vue imports /components/ZStepListItem.vue +1ms
  vite:sfc /home/zwm/workspace/qumake/components/ZLayout.vue parse cache hit +4ms
  vite:sfc /components/ZLayout.vue style compiled in 15ms +16ms
  vite:rewrite (skipped) /components/ZLayout.vue?type=style&index=0 +19ms
  vite:sfc /home/zwm/workspace/qumake/components/ZLayout.vue parse cache hit +2ms
  vite:sfc /components/ZLayout.vue template compiled in 15ms. +21ms
  vite:rewrite (skipped) /components/ZLayout.vue?type=template +25ms
  vite:sfc /home/zwm/workspace/qumake/components/ZPhone.vue parse cache hit +4ms
  vite:sfc /components/ZPhone.vue style compiled in 18ms +20ms
  vite:rewrite (skipped) /components/ZPhone.vue?type=style&index=0 +22ms
  vite:sfc /home/zwm/workspace/qumake/components/ZPhone.vue parse cache hit +2ms
  vite:sfc /components/ZPhone.vue template compiled in 19ms. +19ms
  vite:rewrite (skipped) /components/ZPhone.vue?type=template +21ms
  vite:sfc /home/zwm/workspace/qumake/components/ZMenuUser.vue parsed in 15ms. +23ms
  vite:rewrite /components/ZMenuUser.vue: rewriting +24ms
  vite:rewrite     "vue" --><EMAIL_ADDRESS>+1ms
  vite:hmr         /components/ZMenuUser.vue imports<EMAIL_ADDRESS>+111ms
  vite:sfc /home/zwm/workspace/qumake/components/element/Triangle.vue parsed in 15ms. +21ms
  vite:rewrite /components/element/Triangle.vue: rewriting +19ms
  vite:rewrite     no imports rewritten. +1ms
  vite:sfc /home/zwm/workspace/qumake/components/ZStepListItem.vue parsed in 16ms. +20ms
  vite:rewrite /components/ZStepListItem.vue: rewriting +20ms
  vite:rewrite     no imports rewritten. +0ms
  vite:sfc /home/zwm/workspace/qumake/components/ZMenuCourse.vue parse cache hit +4ms
  vite:sfc /components/ZMenuCourse.vue style compiled in 10ms +20ms
  vite:rewrite (skipped) /components/ZMenuCourse.vue?type=style&index=0 +25ms
  vite:sfc /home/zwm/workspace/qumake/components/ZMenuCourse.vue parse cache hit +7ms
  vite:sfc /components/ZMenuCourse.vue template compiled in 17ms. +18ms
  vite:rewrite (skipped) /components/ZMenuCourse.vue?type=template +23ms
  vite:sfc /home/zwm/workspace/qumake/components/ZMenuUser.vue parse cache hit +1ms
  vite:sfc /components/ZMenuUser.vue style compiled in 3ms +4ms
  vite:rewrite (skipped) /components/ZMenuUser.vue?type=style&index=0 +7ms
  vite:sfc /home/zwm/workspace/qumake/components/ZMenuUser.vue parse cache hit +6ms
  vite:sfc /components/ZMenuUser.vue template compiled in 33ms. +35ms
  vite:rewrite (skipped) /components/ZMenuUser.vue?type=template +39ms
  vite:sfc /home/zwm/workspace/qumake/components/element/Triangle.vue parse cache hit +3ms
  vite:sfc /components/element/Triangle.vue style compiled in 1ms +2ms
  vite:rewrite (skipped) /components/element/Triangle.vue?type=style&index=0 +5ms
  vite:sfc /home/zwm/workspace/qumake/components/element/Triangle.vue parse cache hit +3ms
  vite:sfc /components/element/Triangle.vue template compiled in 3ms. +12ms
  vite:rewrite (skipped) /components/element/Triangle.vue?type=template +16ms
  vite:sfc /home/zwm/workspace/qumake/components/ZStepListItem.vue parse cache hit +5ms
  vite:sfc /components/ZStepListItem.vue style compiled in 8ms +9ms
  vite:rewrite (skipped) /components/ZStepListItem.vue?type=style&index=0 +13ms
  vite:sfc /home/zwm/workspace/qumake/components/ZStepListItem.vue parse cache hit +7ms
  vite:sfc /components/ZStepListItem.vue template compiled in 10ms. +11ms
  vite:rewrite (skipped) /components/ZStepListItem.vue?type=template +18ms
  vite:rewrite (skipped) /style/icons/fonts/materialdesignicons-webfont.woff2?v=5.3.45 +95ms
  vite:rewrite (skipped) /media/avatar.jpg +10ms

Closed via https://github.com/vitejs/vite/pull/353


[proposal]Koordinator scheduler support configuration extensions

What is your proposal:
Koordinator scheduler support configuration extensions for specific scenarios, such as disabling BE scheduling or downgrading scheduling for certain pods
Why is this needed:
Scenario 1: When there are stability issues in a mixed cluster, it is necessary to prevent new offline tasks to schedule for the entire cluster and  still keep suppression on individual machines. ResourceQoS, ColocationStrage which have enable config with nodeStrategy cannot be used here because nodeStrategy is higher than cluster configuration, and if nodeStrategy is modified, the original configuration cannot be restored.
Scenario 2: When some special workloads fail to be scheduled on a large scale, and a quick downgrade is desired without deleting the workload but also reducing scheduling pressure, the scheduler can be configured to filter out some pod scheduling according to label or namespace."
Is there a suggested solution, if so, please add it:
such as： add a dynamic config for koordinator scheduler，work with a filter plugin？

/assign

@ZiMengSheng A simple Proposal is needed to describe how to solve this issue.

A plugin which filters pod by PodDownGrade criteria will be provided. It will be aware of PodDownGrade configmap Add/Update/Delete event and sync cached PodDownGrade criteria(namespace, label).


Update eslint config and dependencies

Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Resolves: # (issue, if applicable)
Summary:
Please summarize the scope of the changes you have submitted, what the intent of the work is and anything that describes the before/after state of the project.
Update eslint config and all other dependencies
Type of change:
Please delete options that are not relevant.

[ ] New capability
[x] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[ ] Other (please elaborate)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

:tada: This PR is included in version 2.2.5-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Menu disappeared on v4 migration

[x] I have read the FAQ.

Describe the bug
Upgrading from v3.19.1 to v4.0.0 wipe the menu.
To Reproduce

Start clean install (docker) on BA v3.19.1 and SR v2.18.0
Create a menu with cocktails
Upgrade to v4.0.0 and v3.0.0
Menu is gone

Versions:

Bar Assistant: 4.0.2
Salt Rim: 3.2.1
Browser: Chromium, Firefox

Additional context, log outputs...
Hello,
After upgrading from v3 to v4 (and following the procedure) I realized my menu disappeared.
I upgraded to the latest versions available but the menu didn't come back.
After checking the database, I was relieved to see the menu still exists:
sqlite> select * from menus;
1|1|1|2024-03-08 14:34:20|2024-09-05 17:29:36
sqlite> select * from menu_cocktails;
2|Cocktails|20|1|76|0|€
3|Shots|60|1|306|0|€
4|Shots|59|1|33|0|€
6|Cocktails|8|1|18|0|€
7|Cocktails|17|1|56|0|€
8|Cocktails|31|1|143|0|€
[...]

Is it a bug related to the routes changes in the upgrade?
Regards,
Nox

Hello,
I fixed my problem, it was because I used "€" as currency where it should be something like "EUR".
Updating all the values directly from the database solved this issue and the menu is working again as expected.
Regards


Input height

Is best practice to use line-height values without an unit.
Source: https://developer.mozilla.org/en-US/docs/Web/CSS/line-height

Input min-height is using the $default-line-height value.
The problem is that line-height value can be unitless and normal, which are not valid values for min-height;

Also, line-height value can use percentage, that will cause vertical alignment issues for inputs.
This pull-request handles all possible valid values for line-height and fix input min-height accordingly.
Thanks!

Nice work! Does vertical-align need to be assigned? I removed the universal vertical-align: top.

I will review the code.

My apologies, I have a pending commit. It addresses only half of your request, as you’ve also accounted for percentage heights. I will fix and post my commit, and then update you shortly. I would greatly appreciate your review.

Please review.

Hey @jonathantneal,
your commit looks good, but we still need to consider "normal", "inherit" and "initial" values for line-height:
[gulp-sass] argument `$number` of `unitless($number)` must be a number
Backtrace:
	node_modules/sanitize.css/sanitize.scss:12, in function `unitless`
	node_modules/sanitize.css/sanitize.scss:12, in function `if`
	node_modules/sanitize.css/sanitize.scss:12 on line 12 in /home/brunorios/www/moskit/node_modules/sanitize.css/sanitize.scss

Thanks!

@brunorios1 is this addressed by latest changes? would you be willing to rebase and for additional fixes?

This will be handled by 2.0.0


[HOTFIX] prometheus operated and alertmanager operated labels

This PR fixes #83
What I did: added on the podMetadata field the same commonLabels we are adding on all resources
We should release an hotfixed version as soon as possible

For future reference. Here's the definition of podMetadata in the CRDs:
https://github.com/prometheus-operator/prometheus-operator/blob/main/example/prometheus-operator-crd/monitoring.coreos.com_alertmanagers.yaml#L3528
https://github.com/prometheus-operator/prometheus-operator/blob/main/example/prometheus-operator-crd/monitoring.coreos.com_prometheuses.yaml#L4029

Did you evaluate using labels without changing the selector instead @nutellinoit ? Ref: https://kubectl.docs.kubernetes.io/references/kustomize/kustomization/labels/

No, i didn't, mainly because we are enforcing a check that commonLabels (with some labels) must be present on kustomization.yaml .
Maybe we can change this behaviour to make the kustomize projects development easier

Yes, and, if my understanding is correct, the usage of a TransformerConfig would allow Kustomize's commonLabels to work as usual even on CRDs thus avoiding the need to manually patch the podMetadata field.

From my understanding the labels are used only by our fury-metadata to discover the modules deployed in the cluster (and other), i.e. we shouldn't need to update the selectors, so using labels instead of commonLabels would be better.
I created an issue on our Redmine to track this.
PS: IIRC annotations were discarded because one can easily ask K8s API filtering by label and not by annotations.

OK, thanks for the explanation. 😄

Changed the configuration using TransformerConfigs @lnovara


add missing apostrophe

This PR (delete as applicable)

Updates the Documentation

Describe the changes below:
Just missing apostrophe added.

👍


Transliteration development - getting rid of extra a's

Describe the bug
Extra a's coming up in words of transliterations, have given a couple of examples below but if more needed let me know.
To Reproduce
Steps to reproduce the behavior:
Search: kmkp (kaljug meh keertan pardhaanaa
Translit that you get:
kalajug meh keeratan paradhaanaa |
What I would like: Get rid of the extra a's
Change to:
kaljug meh keertan pardhaanaa |
Another example:
guramukh japeeai laae dhiaanaa |
change to:
gurmukh japeeai laae dhiaanaa |
Specs

OS 2.9.0
Database 4.7.0

What rule can you use to get rid of the extra characters? If it's something you can explain to a 5 year old we can probably program it in.

What rule can you use to get rid of the extra characters? If it's something you can explain to a 5 year old we can probably program it in.

I think somewhere there is a rule that is adding in an "a" after certain
characters. So removing thst if you know the pattern or know the rules
should be easy.  Shall I give more examples to help you see the pattern?
On Thu, 21 Jan 2021 at 12:13, Bhajneet S.K<EMAIL_ADDRESS>wrote:

What rule can you use to get rid of the extra characters? If it's
something you can explain to a 5 year old we can probably program it in.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/shabados/gurmukhi-utils/issues/186#issuecomment-764602239,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJY6O2FT5JZXSS22WCPUU5DS3AK57ANCNFSM4WMXYZJQ
.

I think somewhere there is a rule that is adding in an "a" after certain
characters. So removing thst if you know the pattern or know the rules
should be easy.  Shall I give more examples to help you see the pattern?
On Thu, 21 Jan 2021 at 12:13, Bhajneet S.K<EMAIL_ADDRESS>wrote:

What rule can you use to get rid of the extra characters? If it's
something you can explain to a 5 year old we can probably program it in.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/shabados/gurmukhi-utils/issues/186#issuecomment-764602239,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJY6O2FT5JZXSS22WCPUU5DS3AK57ANCNFSM4WMXYZJQ
.

Issue is if you remove all a then you will get things like
Stnaam, naank, prsaad
How does it know when to add the a between two consonants and when not to?
It has to do with compound words which we could go through our Gurbani and add hyphens for transmit purposes which then get stripped out but that's a lot of work and a bit odd
What do you think @Harjot1Singh  and @Sarabveer ?

Issue is if you remove all a then you will get things like
Stnaam, naank, prsaad
How does it know when to add the a between two consonants and when not to?
It has to do with compound words which we could go through our Gurbani and add hyphens for transmit purposes which then get stripped out but that's a lot of work and a bit odd
What do you think @Harjot1Singh  and @Sarabveer ?

note to self: test a list of 4 letter words with no vowel between consonants 2 and 3.

Better served with a syllabification function and manual handling of syllable boundaries using the interpunct in DB


Perhaps switching to GitHub actions is a better option?

I cannot view the azure pipeline?

You should be able to now, seem like a bug =/, it's configured for public as far as I can tell

Perhaps switching to GitHub actions is a better option?

Possibly, we just used AzureDevOps because there was a documented pipeline in the vscode docs that we could use for release and it's required that you have an AzureDevOps account for publishing.


Brew formula not working?

I tried to install chunkwm using  brew install chunkwm, here is the result:
==> Installing chunkwm from crisidev/chunkwm
==> Downloading https://github.com/koekeishiya/chunkwm/archive/v0.4.6.tar.gz
==> Downloading from https://codeload.github.com/koekeishiya/chunkwm/tar.gz/v0.4
######################################################################## 100.0%
==> make install
==> make --directory src/chunkc
==> make install --directory src/plugins/tiling
==> make install --directory src/plugins/ffm
==> make install --directory src/plugins/border
Error: An exception occurred within a child process:
Errno::ENOENT: No such file or directory - src/completions/_chunkc

Has to do with the 0.4.6 release archive not containing the src/completions/_chunkc file while the brew formula has been updated to install completions by default.  This shouldn't be an issue after the next release.
Until then you can install the latest stable without completions with:
brew install chunkwm --without-completions
Alternatively, if you want completions then simply install from the git repo with:
brew install chunkwm --HEAD.
Happy Hacking!

This is fixed now.


Add return to proxyDirect to avoid double-connection.

This is to address issue #263 which seemed to only apply to cases where one of the gateway options was direct. Non-direct gateways worked properly since the return if err is nil was already present.

Hi @4wrxb, the first part of this PR was cherry-picked in #285 and is now merged on master
For the second part, I currently have panic error when running it
As it seems to be related to another topic, can you update the title of this PR?

TL;DR: I'm closing this pull request, only the first (now cherry picked) commit should have been there in the first place.
My apologies, I'm new to go so developing in the official branch (to keep compile working) and using other remotes is a new workflow for me.
This second commit is me hacking around for issue #268. As I mentioned there (and even included some comments with these changes), I don't fully understand the architecture I'm playing with (especially the part around line 190 which appears to only be used when listing hosts). The 2nd part is what allowed me to work around the issue described in 268.

TL;DR: I'm closing this pull request, only the first (now cherry picked) commit should have been there in the first place.
My apologies, I'm new to go so developing in the official branch (to keep compile working) and using other remotes is a new workflow for me.
This second commit is me hacking around for issue #268. As I mentioned there (and even included some comments with these changes), I don't fully understand the architecture I'm playing with (especially the part around line 190 which appears to only be used when listing hosts). The 2nd part is what allowed me to work around the issue described in 268.


calc_boundary_flux! is allocating for HOHQMesh and DGMulti

While tackling #1664 I observed that
https://github.com/trixi-framework/Trixi.jl/blob/bb60b5d973ff4d4e00c37476ef858d37083d2209/src/solvers/dgmulti/dg.jl#L468-L480
is allocating for the dgmulti_2d/elixir_euler_hohqmesh.jl example, see e.g. https://github.com/trixi-framework/Trixi.jl/actions/runs/6574426931/job/17859451194#step:7:8803
I could not figure out why that is, also the specialization
# "lispy tuple programming" instead of for loop for type stability
function calc_boundary_flux!(cache, t, boundary_conditions::BC, mesh,
                             have_nonconservative_terms, equations, dg::DGMulti) where {BC}

    # peel off first boundary condition
    calc_single_boundary_flux!(cache, t, first(boundary_conditions),
                               first(keys(boundary_conditions)),
                               mesh, have_nonconservative_terms, equations, dg)

    # recurse on the remainder of the boundary conditions
    calc_boundary_flux!(cache, t, Base.tail(boundary_conditions),
                        mesh, have_nonconservative_terms, equations, dg)
end

does not solve the issue.

Awesome! Glad #1695 fixes it


Model::first() being treated as Model::all()?

Describe the bug
On one specific model, when I add the trait, Model::first() gives me a full collection - as if Model::all() was called. Other models work fine. This occurs in tinker.
Eloquent Query
$model->first()

Stack Trace
No errors thrown
Environment

PHP: 7.1.0
OS: OSX
Laravel: 5.5.14
Model Caching: laravel-5.5

Additional context
I'm using GeneaLabs/laravel-model-caching:dev-laravel-5.5, as no other composer install would work.

@iredmedia Thanks for posting this. If it's a bug in the package, it will only be fixed for Laravel 5.8, as I can no longer maintain backwards-compatibility to any released prior.

@iredmedia I am unable to replicate this issue. Please test with the latest release in Laravel 5.8 and re-open if it still occurs. Thanks :)


After Prisma Engine panic all future requests fail

Bug description

After Prisma Engine panic all future requests fail.
How to reproduce

Run a query that triggers a panic in prisma-engine.
Issue a second query
The second query fails because the js client cannot connect to prisma-engine

If multiple queries are running simultaneously and one panics, all the running queries show an error with the panic from the one query that caused the panic.
Expected behavior

Ideally the prisma-engine would isolate the panic and continue running without effect other requests.
The prisma-engine instance should be restarted by the js client when it shuts down.
Prisma information

Server Log
PANIC: called `Option::unwrap()` on a `None` value

... REMOVED EXTRA LOGGING ...

2020-05-01T20:40:46.501Z prisma-client Prisma Client call:
2020-05-01T20:40:46.501Z prisma-client prisma.partner.findMany({
  where: {
    pwsBaseUrl,
  }
})
2020-05-01T20:40:46.501Z prisma-client Generated request:
2020-05-01T20:40:46.501Z prisma-client query {
  findManyPartner(where: {
    pwsBaseUrl: "<URL>"
  }) {
    id
  }
}

2020-05-01T20:40:46.505Z engine {
  error: Error: connect ECONNREFUSED <IP_ADDRESS>:46591
      at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1137:16) {
    errno: 'ECONNREFUSED',
    code: 'ECONNREFUSED',
    syscall: 'connect',
    address: '<IP_ADDRESS>',
    port: 46591
  }
}
2020-05-01T20:40:46.506Z printStack callsite Error
    at Object.s [as Partner] (/app/src/dbClient/runtime/index.js:1:82529)
    at Object.n.<computed> [as findMany] (/app/src/dbClient/runtime/index.js:1:84025)
    at Object.grantsFromToken (/app/src/auth/token.js:50:39)
    at Object.fromRequest (/app/src/graphql/context.js:35:45)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

Environment & setup

OS: Debian on Docker
Database: PostgreSQL
Prisma version: 2.0.0-beta.4
Node.js version: 12.16.1

Duplicate of #2100


Add Typescript support

As there are people clearly looking for Typescript support for this lib (me too! ✌🏻  + #2) I've decided to create a PR.
Hope that helps!

Thanks for this. As I said to you, I tried config-ing NWB to support typescript, then tried copying everything over to a new TSDX component but it ended up being easier to just make @types/mui-image. So just install that and everything should be fine!


tidb: remove parser replace check for migration

Signed-off-by: xhe<EMAIL_ADDRESS>For #28644, which is blocked by this test.

@xhebox I think it refers to https://github.com/pingcap/tidb/pull/28644?


Fix #117 JRuby incompatibilities

It seems like JRuby doesn't correctly implement refinements see (jruby/jruby#4330) so the only way around this was to revert to monkey-patching the base classes. New file lib/ruby/jruby_hack.rb
is copy-pasted code from each lib/ruby file, except instead of refine X do { ... } it's changed to class X { ... }
There was also an incompatibility with Nn.to_d - Nn, which fails with "Nn cannot be coerced to BigDecimal"; this might be an error in the BigDecimal class on JRuby? For now, those specs are marked pending on JRuby.
Redcarpet is a C-extension for MRI, so I disabled it for JRuby, but documentation can be accessed online (just not built on JRuby)

@kputnam Thank you!


env::state_write has no effect

To do a minimum repro, deploy any contract, for example, I deployed status-message.wasm on a local node. Add a new method:
pub fn migrate(&mut self) {
    let s = "a".to_string();
    env::state_write(&s); // this destroy the state, any later operation on this contract should fail because it will fail to borsh deserialize
// or similar, do: env::storage(b"STATE", b"what");
}

deploy the new contract, call migrate and this txn success. Then call a view method get_status, it still success. Further more, if you do:
curl http://localhost:3030 -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0", "id":1, "method":"query", "params":{"request_type":"view_state","block_id":3390,"account_id":"test.near","prefix_base64":""}}'

to inspect state before and after the call (by replacing block_id), it shows the same state. So this indicates state_write/storage_write has no effect.
Full step to repro:
export NEAR_ENV=local
near deploy test.near status_message.wasm
near call test.near set_status '{"message":"hello"}' --accountId test.near
near call test.near migrate '' --accountId test.near
near view test.near get_status '{"account_id":"test.near"}' --accountId test.near
curl http://localhost:3030 -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0", "id":1, "method":"query", "params":{"request_type":"view_state","block_id":3390,"account_id":"test.near","prefix_base64":""}}'

@frol I took your answer from stackoverflow to try testing migrate state in a local node, then it seems to txn success but have no effect, then I further realize it's indeed env::write_state/storage_write has no effect

If a method has &mut self parameter, then SDK will generate code to read the state before the call and write the state after the call. The latter operation will overwrite whatever you written manually. You should probably not add self parameter to a migration method.

@abacabadabacaba is correct. Indeed, I do need the self parameter as I need to read some state, mutate them in the migration method. I can use env::read but has a &self has sdk deserialize it for you is easier. And just make the migration method from &mut self to &self and near call it works.

Feels like there's still at least a documentation problem here tbh.


⚠ AVS (kty) has degraded performance

In 10cd016, AVS (kty) (https://avus.com.br) experienced degraded performance:

HTTP code: 200
Response time: 9464 ms

Resolved: AVS (kty) performance has improved in e812f5e.


Update for ingress api version update - not merge yet

https://github.ibm.com/IBMPrivateCloud/roadmap/issues/46010
OCP new version will include kubernetes 1.22 that has ingress API version change to k8s.io/api/networking/v1, and old version will not be supported.
This branch has the code to move to k8s.io/api/networking/v1. To do that, we need to update SDK operator version, and several other library versions due to incompatibility between different library versions, which results in significant code changes. To minimize the impact, this prototype change to use klog library.
The code was compiled but need further evaluation and testing.

Errors in the build log
pkg/controller/policycontroller/policycontroller_controller.go:143:3: undefined: reqLogger
# github.com/IBM/ibm-iam-operator/pkg/controller/secretwatcher
pkg/controller/secretwatcher/secretwatcher_controller.go:143:3: undefined: reqLogger

which do not match the code https://github.com/IBM/ibm-iam-operator/blob/ingress-apiversion-change/pkg/controller/policycontroller/policycontroller_controller.go#L143
https://github.com/IBM/ibm-iam-operator/blob/ingress-apiversion-change/pkg/controller/secretwatcher/secretwatcher_controller.go#L143

/retest

/retest

@yannizhang2019 I deployed your changes,  this is the error I get.
I0604 10:54:11.335376       1 authentication_controller.go:197] Reconciling Authentication
I0604 10:54:11.335605       1 ingress.go:51] Creating a new IngressIngress.Namespaceibm-common-servicesIngress.Nameapi-key
E0604 10:54:11.339444       1 ingress.go:54] Ingress.extensions "api-key" is invalid: spec.rules[0].http.paths[0].pathType: Required value: pathType must be specifiedFailed to create new IngressIngress.Namespaceibm-common-servicesIngress.Nameapi-key
I0604 10:54:12.534876       1 authentication_controller.go:197] Reconciling Authentication
I0604 10:54:12.535081       1 ingress.go:51] Creating a new IngressIngress.Namespaceibm-common-servicesIngress.Nameapi-key
E0604 10:54:12.539059       1 ingress.go:54] Ingress.extensions "api-key" is invalid: spec.rules[0].http.paths[0].pathType: Required value: pathType must be specifiedFailed to create new IngressIngress.Namespaceibm-common-servicesIngress.Nameapi-key


Make auto-prefix util isomorphic

Allow server side use of the auto-prefix util. Also check falseyness of the returned prefixed string in the singleHyphened method as the Modernizr.prefixed method seems to return false in some instances when using PhantomJS.

Thanks @troutowicz ! :+1:

I'm guessing there's no workaround for differences between server and client side rendering as the sever-side won't know what it needs to prefix? @hai-cea @troutowicz

@MozMorris The differences should not matter. Pre-render server side without prefixing, then prefix once on the client.

Cool, I guess I was just thinking about the potential for FOUC.
Could you see that being a problem? flexbox for example; Safari (Desktop & Mobile) needs the prefix right? So the first render wouldn't look right.

That's a good question :)

Any update on this? I'm building an isomorphic app and having a similar problem with the  elements generated from :
the markup being generated is different on the client or server
(client) bottom:8px;margin:0;false:content-box;bo
(server) bottom:8px;margin:0;-moz-box-sizing:cont

@davidshariff for this reason I couldn't continue with this set of components. The FOUC wasn't going to cut it. Hacks like hiding everything until the JS (and prefixed styles) had loaded defeated one purpose of rendering on the server.
I think I prefer being able to extract my styles into a separate stylesheet and generate the critical path using a library like https://github.com/pocketjoso/penthouse. Perhaps that's sooo 2014.
I'm still not decided about all this stuff anyway.

@davidshariff I'm running into the same issue.
After reading about CSS Modules yesterday, I'm wondering if they might fit in nicely for this problem. The diff prefixes might be pushed into the stylesheets, and the markup on the server and client would be able to match.


feat:Add use cases of chat to GitHubRepo using pne.chat()+streamlit

Summary by CodeRabbit

New Features

Introduced a chatbot application with a user-friendly interface for managing GitHub repositories.
Added functionality for users to add, update, and delete repositories, as well as select specific files and folders for interaction.
Implemented a dynamic chat interface with real-time processing and model selection options.
Provided a configuration system for managing application settings and repository downloads.

Documentation

Added a comprehensive README.md to guide users through setup, usage, and understanding of application components.

Chores

Introduced a requirements.txt for managing project dependencies.

README can show more detail.


Multilingual version of CLAP

Hi,
Thanks for making the code and the models publicly available. I was wondering if there is any way we can create a multilingual version of CLAP also instead of using Swin-transformer as the audio encoder, can we swap it with other multilingual encoders like Whisper?

Same question


Cloud Connections - S30 disconnected from internet - no error reporting

If the S30 becomes disconnected from the internet and Home Assistant still has connectivity to the Internet, the Lennox API does not report any errors.  This results in the integration believing it is connected but yet it is not.
The test was done by isolating the S30 using a pfSense firewall.  Will continue to monitor for 24 hours to see if errors are eventually reported.
This issue exists in all versions.  The current solution would be to monitor the lennoxS30.state message_count and to look for no change over a period of time or to look at the attribute last_message_time and to look for it being older than current time by some margin.  At this point, not sure what the length of time should be.

After 24 hours no change.  When I restarted the integration it was unable to connect as expected.
The best solution may be to implement a watchdog, working like this:

Periodically (once every X minutes - configurable) set a piece of config data in the S30.
If the update from device with the updated config data does not arrive within Y minutes, this a counted as a watch dog failure.
If more than Z failures occur in a row, mark the connection down and go into retry mode.


Another beginning

My plan was just to strip the package down to something very small with tests. But I'm having trouble with Poetry not being happy about having a package name with a capital later. There is a hack but people are still having problems even with the hack. So I could try a different package name (wharve, for example). Or I could try using uv.

Rename the library wavelib.

Make sure to check PyPi first for package names. wavelib, for example, is already taken.


Render pointer aligned to track centre (overhanging)

When you drag the pointer to the left edge, the left edge of the pointer aligns with the left edge of the track.
Similarly, when you drag the pointer to the right edge, the right edge of the pointer aligns with the right edge of the track.
Is there a way to make the pointer centre align to the track instead?  So at the floor value, the centre of the pointer is aligned with the left edge of the track, and at the ceil value, the centre of the pointer is aligned with the right edge of the track.
https://jsfiddle.net/mirality/j1ebo2a9/
With this grid background, you can see that while position 5 lines up nicely in both, positions 0 and 10 are well off the centre.  You can also see that the limit labels "move sideways" when the pointer reaches them instead of staying in a fixed location.  (I realise that it's actually hiding the limit label; it's the effective appearance that I'm referring to.)
I would prefer if the track still extends the full width of the slider (as shown at the bottom of the grid) and the pointer renders "outside" rather than the reverse.

Hi,
You can play with the CSS and move the bar:
.rzslider .rz-bar {
  left: 16px;
  width: calc(100% - 32px);
}

That just shortens the bar, it doesn't do what I wanted.  The bar is the correct length already, it's just that the pointer doesn't go to the end of the bar.
I guess changing the width and margins on the slider in combination with that kinda works, but it seems a bit weird.
.rzslider {
  margin: 0 -16px;
  width: calc(100% + 32px);
}

https://jsfiddle.net/mirality/j1ebo2a9/3/
Is there a better way to do it?

There is no built-in way to do this. You'll have to workaround using CSS.

Ok.  The changes shown in that fiddle seem to work, at least.


All relays switch once at boot remote Raspberry Pi

Hello,
when I restart the Remote Pi, the relays are switched once. I have garages and a garden gate on it and everything is opened by it.
This happens when the plugin reconnects to my pi.
[16/03/2023, 14:55:21] [KellerPi] KellerPi: connected to KellerPi.lan:8888
[16/03/2023, 14:55:22] [KellerPi] KellerPi: warning: NC (21): unknown handle (-25)
[16/03/2023, 14:55:22] [KellerPi] KellerPi.lan: Current Temperature: set to 40.8°C (from 43.5°C)
[16/03/2023, 14:55:22] [KellerPi] KellerPi.lan: Frequency: set to 600MHz (from 1300MHz)
[16/03/2023, 14:55:22] [KellerPi] KellerPi.lan: Voltage: set to 1200mV (from 1369mV)
[16/03/2023, 14:55:22] [KellerPi] KellerPi.lan: Load: set to 0.31 (from 0.39)
[16/03/2023, 14:55:22] [KellerPi] KellerPi.lan: Last Boot: set to "Thu Mar 16 2023 14:54:35" (from "Thu Mar 16 2023 14:23:12")
[16/03/2023, 14:55:22] [KellerPi] KellerPi.lan Power LED: On: set to true (from false)
from here:
[16/03/2023, 14:55:22] [KellerPi] KellerPi.lan Gartentor: On: set to true (from false)
[16/03/2023, 14:55:22] [KellerPi] KellerPi.lan Garage Links: On: set to true (from false)
[16/03/2023, 14:55:22] [KellerPi] KellerPi.lan Garage Rechts: On: set to true (from false)
[16/03/2023, 14:55:22] [KellerPi] KellerPi.lan Gartentor: On: set to false (from true)
[16/03/2023, 14:55:22] [KellerPi] KellerPi.lan Garage Links: On: set to false (from true)
[16/03/2023, 14:55:22] [KellerPi] KellerPi.lan Garage Rechts: On: set to false (from true)
...
Config:
"name": "KellerPi",
"hosts": [
{
"host": "KellerPi.lan",
"name": "KellerPi",
"hidden": false,
"noPowerLed": false,
"noSmokeSensor": true,
"usbPower": true,
"devices": [
{
"device": "switch",
"name": "Garage Links",
"gpio": 18,
"pull": "off",
"reversed": true,
"pulse": 300
},
{
"device": "switch",
"name": "Garage Rechts",
"gpio": 27,
"pull": "off",
"reversed": true,
"pulse": 300
},
{
"device": "switch",
"name": "Gartentor",
"gpio": 17,
"pull": "off",
"reversed": true,
"pulse": 300
}

See https://github.com/ebaauw/homebridge-rpi/wiki/Supported-Devices#device-state, last paragraph.

Now back to OFF now it works... All fine. Don´t know why


Solve "../lib//libs2n.so: undefined reference to `EVP_DecryptFinal_ex…

Solve
../lib//libs2n.so: undefined reference to `EVP_DecryptFinal_ex'
../lib//libs2n.so: undefined reference to `SHA224_Update'
../lib//libs2n.so: undefined reference to `ENGINE_free'

See https://github.com/awslabs/s2n/issues/106#issue-92376403

I'm closing this PR because linking against libs2n.so should be "enough". I've updated the issue. For system linking, we'll need to work on making the static linking work. But binaries shouldn't be required to link against libcrypto explicitly. Thanks for the report.


Fix disappearing cursor during load on Mac

When combined with a call to trap_SetMouseMode(MouseMode::SystemCursor) during CG_Init, this fixes #866.

When combined with updating to a newer SDL, this also fixes #628.

The other needed component to fix the disappearing cursor was done in https://github.com/Unvanquished/Unvanquished/pull/2695.


Can't finish update

When I tried to start crouton today it was telling me that the "startxfce4" command is not found. I figured that maybe updating crouton would fix it, but when I try to update crouton it attempts to go through and update all of my packages, and gets stuck here:
28% [3 openjdk-6-jre-headless 32.6 MB/32.7 MB 100%]
Since I can't get into the chroot, here is the output from cat /etc/lsb-release
Thanks in advance.
CHROMEOS_AUSERVER=https://tools.google.com/service/update2
CHROMEOS_BOARD_APPID={A772AA64-E906-A01E-1DFD-1856870D39EC}
CHROMEOS_CANARY_APPID={90F229CE-83E2-4FAF-8479-E368A34938B1}
CHROMEOS_DEVSERVER=
CHROMEOS_RELEASE_APPID={A772AA64-E906-A01E-1DFD-1856870D39EC}
CHROMEOS_RELEASE_BOARD=quawks-signed-mp-v2keys
CHROMEOS_RELEASE_BRANCH_NUMBER=55
CHROMEOS_RELEASE_BUILD_NUMBER=6946
CHROMEOS_RELEASE_BUILD_TYPE=Official Build
CHROMEOS_RELEASE_CHROME_MILESTONE=43
CHROMEOS_RELEASE_DESCRIPTION=6946.55.0 (Official Build) stable-channel quawks
CHROMEOS_RELEASE_NAME=Chrome OS
CHROMEOS_RELEASE_PATCH_NUMBER=0
CHROMEOS_RELEASE_TRACK=stable-channel
CHROMEOS_RELEASE_VERSION=6946.55.0
GOOGLE_RELEASE=6946.55.0

You may still be able to get into your chroot shell with sudo enter-chroot.
If that works, then try sudo apt-get update; sudo apt-get upgrade and see if that finishes without any errors.

Hey, that worked. Thanks so much.


Error when cchardet fails to return an encoding

Using the latest HBCL pip installed from this repo. On occasion cchardet is unable(?) to detect a specific file encoding, in which case cchardet.detect() will return a dict with the encoding and confidence key values both set to None. HBCL currently assumes the confidence value will always be a type/object supporting comparison, and when it isn't a TypeError is thrown.
Example affected log file: BUCK-TICK - TABOO.log
Example script for reproduction:
from heybrochecklog import score_log
from pathlib import Path
import os

log_file = os.path.join(os.getcwd(), "BUCK-TICK - TABOO.log")
log_report = score_log(Path(log_file))
print(log_report)

Output:
Traceback (most recent call last):
  File "...\test.py", line 7, in <module>
    log_report = score_log(Path(log_file))
                 ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "...\Python311\Lib\site-packages\heybrochecklog\score\__init__.py", line 14, in score_log
    contents = get_log_contents(log_file)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "...\Python311\Lib\site-packages\heybrochecklog\shared.py", line 12, in get_log_contents
    encoding = get_log_encoding(log_file)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "...\Python311\Lib\site-packages\heybrochecklog\shared.py", line 26, in get_log_encoding
    return result['encoding'] if result['confidence'] > 0.7 else 'utf-8-sig'
                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: '>' not supported between instances of 'NoneType' and 'float'

One simple workaround to hide the problem is adjusting the comparison on line 26 of shared.py like so:
        return result['encoding'] if (result['confidence'] or 0) > 0.7 else 'utf-8-sig'

This is obviously a copout but a more robust solution is beyond my current abilities.

Yeah, it turns out cchardet doesn't support 'MacRoman'. So yeah, will revert the change of using cchardet to chardet instead.

As it turns out, one cannot support the other encoding out there. Someone should standardise the log character encoding to remove this type of headache in detecting character encoding.
Neither of these packages (cchardet or chardet) is a bullet-proof solution and may require both of them to be there.
Both packages can output different character encoding on the same log file and one of them could either break and throw an exception or detect and produce bad result.
Will see what I can do.


Feature/remove sdx home

Remove SDX_HOME requirement from make file
Supersedes #185

Codecov Report

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

@@           Coverage Diff           @@
##           master     #189   +/-   ##
=======================================
  Coverage   84.86%   84.86%
=======================================
  Files          11       11
  Lines         469      469
=======================================
  Hits          398      398
  Misses         71       71

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 4a540e6...f825ddc. Read the comment docs.


Update issue #16

I've updated for this issue, please merge so we'll able to display full line.

@EddieLukeAtmey thanks for providing the fix, but it has a side effect of always showing the separator line in the last row, which can be undesirable for some cases like having a border around the dropdown.
I implemented a workaround by adding dropdownShowsBottomRowSeparator property - see the commit 1ffe4acf02daa13dde55f5ebe78b8c7a0de59877 for more details.


Add a new sub error description

Adding a new error message description

@rwike77
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@miguel-s-ferreira  Thanks for the update.  #sign-off


how to create viewmodel with param

I use a viewmodel like
public class RootViewModel(Func<NextViewModel> func, IWindowManager wndManager>
{
   public void ShowNext()
  {
    wndManager.ShowWindow(func());
  }
}

It works well. But if I want to pass a param to the NextViewModel, It cannot work.
public class RootViewModel(Func<int, NextViewModel> func, IWindowManager wndManager>
{
   public void ShowNext(int i)
  {
    wndManager.ShowWindow(func(i));
  }
}

It give me a Unable to find a constructor for type RootViewModel which we can call: error.
How can I pass the param to the viewmodel?

You can pass in a custom factory interface instead of a func. Stylet can create an instance for you. Since you want custom parameters, you'll want to create an implimentation and then bind it manually.

I use custom factory instead, but if I pass a param not string, it throw error:
Can only implement methods with zero arguments, or a single string argument

the code:
    public interface IQueryViewModelFactory
    {
        QueryViewModel CreateQueryViewModel(JiraQuery query);
    }

    builder.Bind<IQueryViewModelFactory>().ToAbstractFactory();

if I implement the factory, the inject is null:
    public interface IQueryViewModelFactory
    {
        QueryViewModel CreateQueryViewModel(JiraQuery query);
    }
    public class QueryViewModelFactory : IQueryViewModelFactory
    {

        public QueryViewModel CreateQueryViewModel(JiraQuery query)
        {
            return new QueryViewModel(query);
        }
    }

// first viewmodel
public RootViewModel(IQueryViewModelFactory queryViewModelFactory, IWindowManager windowManager)
{
  ...
}

// show second viewmodel
_windowManager.ShowWindow(_queryViewModelFactory.CreateQueryViewModel(query));

// in the second viewmodel, the inject is null

    public class QueryViewModel : Screen
{
    public QueryViewModel(JiraQuery query)
    {
        ...
    }

        [Inject]
        public IOtherInject  OtherInject{ get; set; }  // this is null

}

I'm newer to Stylet, but I think i will switch to other mvvm framework. sine there are so few resources and documents!

The ioc container provided with Stylet isn't powerful enough to create factories which take arbitrary parameters.
One option is to switch to another ioc container -- there's info on this in the docs.
Another option is to write your own factory:
public class NextViewModelFactory
{
    public QueryViewModel CreateQueryViewModel(JiraQuery query)
    {
        return new QueryViewModel(....);
    }
}

public class RootViewModel(NextViewModelFactory factory, IWindowManager wndManager>
{
   public void ShowNext()
  {
    wndManager.ShowWindow(factory.CreateQueryViewModel(...));
  }
}

Another option is to just instantiate the ViewModel yourself:
public class RootViewModel(NextViewModelFactory factory, IWindowManager wndManager>
{
   public void ShowNext()
  {
    wndManager.ShowWindow(new QueryViewModel(...));
  }
}

This isn't really an issue with Stylet - it's a question about dependency injection and ioc containers. You don't have to use dependency injection, and you don't have to use Stylet's (simple) ioc container.

Closing as no response


VIN barcodes problem

Hi, i've got a feedback from a user using my app:

Was trying out your app and server program. Was hoping to use it as a way to scan vehicle VIN barcodes and have it input into our program for vehicle repairs. Issue I have come up with is scanning chrysler VIN barcodes the program inputs the character I at the beginning of the VIN. Other barcode scanners correctly input the VIN without the I. Example to try yourself

So far this specific issue seems to be chrysler only VINs.
Any fix for this? Its the only thing preventing me from getting what I need from you otherwise great program. Thanks.

Sorry to be a jerk but I'm now closing issues that don't follow the issue submission guidelines. This plugin takes a lot of work to maintain and I can't afford the time required to solicit the required info from everyone.
I'm closing this issue but please feel free to re-open the issue if you provide the requested details from the new issue submission guidelines.
https://github.com/phonegap/phonegap-plugin-push/blob/master/.github/ISSUE_TEMPLATE.md


Add an option to not always touch web.config on deployment. Fixes #1167

:shipit:
Doc: https://github.com/projectkudu/kudu/wiki/Configurable-settings#dont-touch-webconfig-at-the-end-of-the-deployment