Add option to load stickers from file path

Is your feature request related to a problem? Please describe.
I would like to be able to load custom images as stickers instead of the ones that come with the theme.
Describe the solution you'd like
Some sort of option to point to either an individual custom sticker (which applies to all themes) or a folder with custom stickers appropriately named. Ex: Using a folder which contains a file called "emilia_light.png", I point the plugin to this folder and when I use the Emilia Light theme my sticker override is used instead of the default.
Describe alternatives you've considered
I tried replacing the images in the config dokiThemeAssets and although it will work one time, it does not persist. After restarting my custom image is replaced.
Additional context
My apologies if there is already a way to do this that I have missed.

I tried replacing the images in the config dokiThemeAssets and although it will work one time, it does not persist. After restarting my custom image is replaced.

Yeah, so I've got things set up to where if I change the master sticker everyone's sticker will update. So your other sticker is different from the master, so it gets updated with master. This way I could make changes without having to release a new version of the theme.
I can see the override working for one theme, but if you switch between themes, what should it do? Should it use an override, should it use the default? Does the sticker not change ever (you just set one and done like the background image)? Things that have to be considered.
Easiest thing right now, since you found the assets directory, it could just be configured to not check for updates (however, that feels like a :adhesive_bandage: fix )
You're also telling me there is a cuter Emilia sticker than this?

Yeah, so I've got things set up to where if I change the master sticker everyone's sticker will update. So your other sticker is different from the master, so it gets updated with master. This way I could make changes without having to release a new version of the theme.

I think that makes sense, does that mean the stickers are pulled from the github on startup assuming they don't match?
I was thinking a solution to multiple themes would just be checking for the file name so even though my picture may be of a Zero Two, I name the file "emilia_light" or the file name for the sticker depending on my desired theme and it would replace that specific themes sticker. With maybe the ability to disable custom stickers in the settings in which case I would get the default again. That's the best solution I can think of, however I'm sure if you were to implement this feature you would find a good way to do it.

You're also telling me there is a cuter Emilia sticker than this?
Obviously there nothing cuter, however one might need to replace her with a lower tier waifu in order to focus on the code :smile:

my picture may be of a Zero Two....lower tier waifu

I just got done watching Darling in the Franxx. Zero Two is S tier and my new best girl .
I was actually planning on adding her (and Mai Sakurajima) this month. Relevant theme request https://github.com/doki-theme/doki-master-theme/issues/43
After that I'll think about what I want to do to solve this.

does that mean the stickers are pulled from the github on startup assuming they don't match?

In a sense, yes, there is a couple of times it checks. It checks to see if the MD5 hash matches the hash stored in my CDN, if they don't match, it will overwrite your local content with the content from the CDN.

I was actually planning on adding her (and Mai Sakurajima) this month.

I love both of them, can't wait to see their themes!

After that I'll think about what I want to do to solve this.

Awesome! Thanks for taking into consideration my suggestion and for the awesome plugin!

@0SoggyMustache0

Easiest thing right now, since you found the assets directory, it could just be configured to not check for updates (however, that feels like a adhesive_bandage fix )

I went with this first pass  :point_up: (it was a quick win before publishing the new updates)
I added doki.theme.update.assets registry action, when disabled the plugin will not update local assets. You can toggle this feature via help > Find Action... > doki.theme.update.assets
BTW, you can save a gif as zero_two_light.png and can get this (not saying you should, but you can!)

I'll leave this issue open for the time being, I have another idea how to solve it and it may enable me to add more themes too. But that's for later.

Thanks! Much appreciated!


(ORCH-1235) Add code_id to environment catalog requests

Similar to agent catalog requests, we now add code id for the given
environment to environment catalog requests.
This extends the logic for determining the request environment to now check
both the :environment URL segment as well as the "environment" query param.
If environment is part of the URL, we favor that over a conflicting query
param.

I wasn't entirely sure what to do about the submodule. There's a change to Puppet to actually use the code id that's added to the request, and that change is necessary for the new integration test to pass, so I pulled it in. I also updated the PUPPET_BUILD_VERSION in the acceptance helper because a) other commits did that and b) it seems like it makes sense to keep the puppet-agent dependency and the puppet submodule versions in sync? The new puppet-agent shouldn't strictly be necessary for the acceptance tests to pass though (since I didn't change them).

:see_no_evil:

@nicklewis this is for post-burnside, presumably?

Yep, post-burnside.

@nicklewis what does this endpoint do in OSS?  Can discuss offline if that's preferable.
I'm pretty much +1 on this other than the minor nit/question above.
Also looks like it'll need a rebase.

@cprice404 This endpoint is available in OSS and behaves the same as in PE. It will compile and return the environment catalog for the specified environment, if the app_management setting is enabled in puppet.conf.
The corresponding puppet change happened in puppetlabs/puppet#5099.
Will add comment + rebase.

Rebased and added a comment explaining the reasoning about path component vs. query string parameter.

Updated to look at [:route-params :environment] and then [:params "environment"].

+1, @camlow325 if that looks ok to you feel free to merge.

:shipit:


[Suggestion] Windows Directory Paths

When installing LuaRocks in Windows, LR mimics the *nix structure. While the root of the tree may be changed, you cannot change the actual placement of packages without going to the config.lua file in the LR home directory.
Two suggestions:
##Should the default behavior map to the luaconf.h file?
PATH is !\\?.lua;!\\?\init.lua  (plus a !\\lua variant) and CPATH is the same. This hardwires modules to root in the executables directory and this is perfect for Windows. Adding a second tree to the user's roaming profile makes sense (as is already done in non-sandbox mode), but here again, I'd just stick to the Window's structure, in order to simplify things.
##Make setting CPATH and PATH tree structure accessible as command line option during installation.
Changing this setting in the config.lua file is not as obvious, or documented, as the normal installation process. In addition, it requires two steps. For sandbox applications, where LR is used as a developer tool for people packaging applications that use Lua, this is a bit of a pain. Typically, they want control over the tree structure and it makes automation scripts a bit more complicated.

I am having a problem with the luarocks path.
I ran
luarocks install inspect
and that generated the necessary files. Then I wrote this simple test code:
require "inspect"
assert(inspect(1) == "1")
assert(inspect("Hello") == '"Hello"')

and got this error
Program starting as '"E:\Anonamouse\ZeroBraneStudio\bin\lua.exe" -e "io.stdout:setvbuf('no')" "E:\Anonamouse\ZeroBraneStudio\myprograms\DemoInspectModule.lua"'.
Program 'lua.exe' started in 'E:\Anonamouse\ZeroBraneStudio\myprograms' (pid: 14776).
E:\Anonamouse\ZeroBraneStudio\bin\lua.exe: ...namouse\ZeroBraneStudio\myprograms\DemoInspectModule.lua:2: attempt to call global 'inspect' (a nil value)
stack traceback:
        ...namouse\ZeroBraneStudio\myprograms\DemoInspectModule.lua:2: in main chunk
        [C]: at 0x00402a57
Program completed in 0.04 seconds (pid: 14776).

I get the same error when I execute the same simple app directly in the console.(That tells me that PATH variable for lua is working)
The output of
 luarocks config

gives this:
C:\Program Files (x86)\Lua\5.1\lua: C:\Program Files (x86)\Lua\5.1\luarocks.lua:3: module 'luarocks.command_line' not found:
no field package.preload['luarocks.command_line']
no file 'C:\Program Files (x86)\LuaRocks\2.2\lua\luarocks\'
no file 'C:\Program Files (x86)\LuaRocks\2.2\lua\luarocks\init.lua'
no file 'C:\Program Files (x86)\LuaRocks\systree\share'
no file 'C:\Program Files (x86)\LuaRocks\systree\share\lua\5.1\luarocks\command_line.lua'
no file 'C:\Program Files (x86)\LuaRocks\systree\share\lua\5.1\luarocks\command_line\init.lua'
no file 'C:\Program Files (x86)\LuaRocks\systree\share\lua\5.1'
no file 'C:\Program Files (x86)\LuaRocks\systree\lib\lua\5.1\luarocks\command_line.dll'
no file 'C:\Users\Stefan\AppData\Roaming\LuaRocks\share\lua\5.1\luarocks\command_line.lua'
no file 'C:\Users\Stefan\AppData\Roaming\LuaRocks\lib\lua\5.1\luarocks\command_line.dll'
no file '.\luarocks\command_line.dll'
no file '.\luarocks\command_line51.dll'
no file 'C:\Program Files (x86)\Lua\5.1\luarocks\command_line.dll'
no file 'C:\Program Files (x86)\Lua\5.1\luarocks\command_line51.dll'
no file 'C:\Program Files (x86)\Lua\5.1\clibs\luarocks\command_line.dll'
no file 'C:\Program Files (x86)\Lua\5.1\clibs\luarocks\command_line51.dll'
no file 'C:\Program Files (x86)\Lua\5.1\loadall.dll'
no file 'C:\Program Files (x86)\Lua\5.1\clibs\loadall.dll'
no file '.\luarocks.dll'
no file '.\luarocks51.dll'
no file 'C:\Program Files (x86)\Lua\5.1\luarocks.dll'
no file 'C:\Program Files (x86)\Lua\5.1\luarocks51.dll'
no file 'C:\Program Files (x86)\Lua\5.1\clibs\luarocks.dll'
no file 'C:\Program Files (x86)\Lua\5.1\clibs\luarocks51.dll'
no file 'C:\Program Files (x86)\Lua\5.1\loadall.dll'
no file 'C:\Program Files (x86)\Lua\5.1\clibs\loadall.dll'
stack traceback:
    [C]: in function 'require'
    C:\Program Files (x86)\Lua\5.1\luarocks.lua:3: in main chunk
    [C]: ?

What am I missing?
I did notice a lot of the PATHs that get added refers to non existing directories. For example
 LUA_CPATH=.\?.dll;C:\Users\Stefan\AppData\Roaming\Lua\LuaRocks\lib\lua\5.1\?.dll

and under LUA_PATH
C:\Users\Stefan\AppData\Roaming\Lua\LuaRocks\lib\lua\5.1\?.dll
C:\Program Files (x86)\LuaRocks\2.2\lua\luarocks\init.lua
C:\Program Files (x86)\LuaRocks\systree\share\lua\5.1\?\init.lua
C:\Program Files (x86)\LuaRocks\systree\share\lua\5.1\?.lua
C:\Users\Stefan\AppData\Roaming\LuaRocks\share\lua\5.1\?.lua
C:\Program Files (x86)\LuaRocks\systree\lib\lua\5.1\?.dll
C:\Users\Stefan\AppData\Roaming\LuaRocks\lib\lua\5.1\?.dll

The PATHs I do have are:
C:\Program Files (x86)\LuaRocks\2.2\lua\luarocks\
C:\Program Files (x86)\LuaRocks\systree\share
C:\Program Files (x86)\LuaRocks\systree\share\lua\5.1
.\?.lua
.\?\init.lua

This article
http://www.thijsschreijer.nl/blog/?p=772

talks about installing the miniGNU compiler but the official docs for luarocks make no mention of that. I just used the install.bat file in the luarocks-2.2.1-win32 folder.
Is there a good way to get luarocks working on windows?

On 30 March 2015 at 14:24, stefangeorge<EMAIL_ADDRESS>wrote:

I am having a problem with the luarocks path.
I ran
luarocks install inspect
and that generated the necessary files. Then I wrote this simple test code:
require "inspect"
assert(inspect(1) == "1")
assert(inspect("Hello") == '"Hello"')
and got this error
Program starting as '"E:\Anonamouse\ZeroBraneStudio\bin\lua.exe" -e "io.stdout:setvbuf('no')" "E:\Anonamouse\ZeroBraneStudio\myprograms\DemoInspectModule.lua"'.
Program 'lua.exe' started in 'E:\Anonamouse\ZeroBraneStudio\myprograms' (pid: 14776).
E:\Anonamouse\ZeroBraneStudio\bin\lua.exe: ...namouse\ZeroBraneStudio\myprograms\DemoInspectModule.lua:2: attempt to call global 'inspect' (a nil value)
stack traceback:
...namouse\ZeroBraneStudio\myprograms\DemoInspectModule.lua:2: in main chunk
[C]: at 0x00402a57
Program completed in 0.04 seconds (pid: 14776).

inspect may not create a global (which is bad practice these days).
try swapping your first line for: local inspect = require "inspect"

@daurnimator seesm to be right. Where did you get that test code? maybe there is some outdated wiki page?

Your LUA_PATH is incomplete. You need C:\Program Files (x86)\LuaRocks\2.2\lua\?.lua, and you should change C:\Program Files (x86)\LuaRocks\2.2\lua\luarocks\init.lua to C:\Program Files (x86)\LuaRocks\2.2\lua\?\init.lua (but that's optional since LuaRocks doesn't use an init.lua file).

@daurnimator THANK YOU. Yes the local thing worked. The code example was from the "inspect" web page-just something to make sure inspect was loaded.
I would give you a SO type of ANSWER credit if this site permitted it. Or some kind of cred.
@siffiejoe Thank you for corrected the error of my path. I use an excellent windows path editor named Rapid Environment Editor (http://www.rapidee.com/en/about) It not only makes the path uber readable and editable, but highlights all the path entries where there is no file/folder in red. Why are there so many of those with luarocks?

@stefangeorge LuaRocks adds its own module locations to package.path/package.cpath to keep its own modules separate from the modules installed via LuaRocks. Also by default you get two separate rocks trees (one for users with admin privileges, one for users without), and vanilla Lua has multiple module search paths configured by default, too. But the main reason probably is that the elements in package.path/package.cpath are not valid paths but path templates. The ? in the path template is replaced by some module specific string to form the actual file to look for.

Can I also lob in a stone and point out that Mingw-w64 (the fork of Mingw that is more actively working with other projects) at least as far as the MSYS2 builds have a further issue in that they separate 32 and 64 bit targets into separate subdivisions of the base - typically C:\msys64 (or until May 2020 I think C:\msys32 though they're just dropping support for 32 bit Hosts for building code though not as targets).
This means that once one sorts out the misconfiguration currently for 32 bit targets ( https://github.com/msys2/MINGW-packages/issues/5928 ) if one is building a project that will include the lua C libraries built by luarocks {typically into the same directory as the executable} and one needs both sets (32 and 64-bit) of those binary libraries for two builds (32 and 64-bit, one native and one cross-compiling) of the target AND one uses the user option then the libraries of both bitnesses end up in the same user directory and since they have the same name this breaks the luarocks management of those libraries as the two variants try to control each others files:
Warning: C:/msys64/home/stephen/.luarocks/lib/lua/5.1/lfs.dll is not tracked by this installation of LuaRocks. Moving it to C:/msys64/home/stephen/.luarocks/lib/lua/5.1/lfs.dll~
I am still trying to work out how to tell two separate luarocks installs how to put their files and the libraries they install into the correct place when one of those places is a per-user location that I can have added to my LUA_PATH and LUA_CPATH environmental variables...


Add a test PQ image

It goes from 10% PQ signal level to 90%, so from ~0.33 cd/m² to ~4000 cd/m², uniformly in PQ space.
Created using:
convert -size 17x1 -depth 16 -define gradient:direction=East gradient:gray10-gray90 -sample 6400% pq_gradient.pgm
tools/cjxl -m -x color_space=Gra_D65_Rel_PeQ pq_gradient.pgm pq_gradient.jxl

What is the goal of this test image?
In non-HDR mode Chrome, this gets rendered in a probably very similar way as in HDR mode Chrome: as 17 shades of gray, getting brighter from left to right. So it's won't really help to know based on that image if your HDR is working or not...

What is the goal of this test image?
In non-HDR mode Chrome, this gets rendered in a probably very similar way as in HDR mode Chrome: as 17 shades of gray, getting brighter from left to right. So it's won't really help to know based on that image if your HDR is working or not...

At least on Linux, in non-HDR mode the first few steps are indistinguishable - and in HDR mode on Windows, the last few aren't distinguishable unless you have a very bright monitor.


Linewise history restore

I would like to request a feature in which line-wise history restore is available as a button in "Current Line Hovers".
This could be useful in the following scenarios for examples:

I did a lot of changes in and pushed in git over several commits.
I want to undo some of these changes which are distributed over several different commmits
I open gitlens view, and then I go line by line and then put the mouse cursor on the line to get the  "Current Line Hover".
I find in the "Current Line Hover" a history restore button. Each time I click it, it goes commit back in history only for this line.

Thanks a lot and keep up the Superhero work you are doing!
Best Regards
HS

@Safieddine90 If I understand correctly, I believe the Open Changes button here, would do what you are asking for.

But you can also use the Open Line Changes with Previous Revision command from the command palette to jump back to the line commit.
Let me know if you wanted something else.


PowerToys Run fuzzy search is space sensitive

Microsoft PowerToys version
0.56.1
Running as admin

[ ] Yes

Area(s) with issue?
PowerToys Run
Steps to reproduce
It seems that PowerToys Run implements fuzzy search but it doesn't work as expected.  The most popular fuzzy searcher (fzf) ignores spaces.  The fuzzy search in PowerToys Run seems to be space sensitive.
For example "vscode" does not match "Visual Studio Code":

But "v s code" does match "Visual Studio Code":

This odd fuzzy search behavior seems to be intended based on the current code.
https://github.com/microsoft/PowerToys/blob/3508301f06478e6ad6eae877b99a4b77307550cb/src/modules/launcher/Wox.Infrastructure/StringMatcher.cs#L46-L57
✔ Expected Behavior
I expected PowerToys Run fuzzy search to be case insensitive.  For example, I expected "vscode" to match "Visual Studio Code".
❌ Actual Behavior
PowerToys Run fuzzy search is case sensitive.  To match "Visual Studio Code" I need to search for "v s code".
Other Software
No response

We don’t have aliasing currently  v s and code all exist in “visual studio code” where “vscode” does not

Hi @crutkas.  Thank you for responding.  I don't think aliases/synonyms is the right solution here.  Aliases/synonyms need to be manually created/maintained.  I'm proposing a modification to the Power Toys Run fuzzy search algorithm to make it behave more similarly to other more popular fuzzy search algorithms like that implemented in fzf.   The PowerToys Run fuzzy search algorithm first breaks the string into substrings separated by whitespace.  I'm suggesting to not do this.  Or make it configurable.
The Windows Start Menu fuzzy search has the behavior I was expecting.

great discussion but honestly believe #15318 has the actual way they are doing it and it handles common misspellings.
A quick example of the style of fuzzy search not working is the following: "viscode" should do a hit would pop it up since "vis" and "code" would hit.  It does not.

still inclined to dup this against https://github.com/microsoft/PowerToys/issues/15318
/needinfo

@crutkas, thanks for taking the time to lay this all out.  I now see this as you do.
I reviewed #15318 more closely and took a look at appssynonyms.txt.  It's terrible lol.  I did find an entry for "vscode":
*|visual studio code	*|vscode	4061

Because Windows Start Menu Search matches "vscode" to "Visual Studio Code" but does not match "viscode", I agree, it does seem that Windows Start Menu Search uses appssynonyms.txt instead of a fzf-like fuzzy search.  Either of the following would satisfy my original expectations:

PowerToys Run behaves more like Windows Start Menu Search (via appssynonyms.txt) (#15318)
PowerToys Run behaves more like fzf

Please feel free to dupe against #15318.  Thank you.


HAWKULAR-518 : Fix tooltip cropped on "Update chart"

Also fixed it in other places where this was/might happen.
Took the chance to also do some general improvements and respect line length in affected files.

@ammendonca can you now rebase and resubmit, now that we should have things working...

Merged #637


tsup build hangs with ubuntu-latest

Description
Issue Summary
Since my build test job started to fail randomly since this week began, I investigated it and found out that:

when it uses ubuntu-latest version 20240304.1.0 it hangs in place,
when it uses ubuntu-latets version 20240225.1.0 it works just fine.

The build is pretty simple and takes usually no longer than 10 seconds, if not even less. It's triggered by running nx, which first runs build dependency. Here's an example of a job that I had to stop, as it hang for 40 minutes:
https://github.com/jkazimierczak/quizcamp/actions/runs/8165348642/job/22322341581?pr=34
Of course build and tests pass if it's run locally. It never failed with the previous version of the runner.
Important distinction - it's not the Build step which fails, but rather the tsup bulid inside of Run tests action's step:

Environment
Failing runner image:
Image: ubuntu-22.04
Version: 20240304.1.0

Succeeding runner image:
Image: ubuntu-22.04
Version: 20240225.1.0

System info - same for both:
Current runner version: '2.314.1'

Operating System
  Ubuntu
  22.04.4
  LTS

Runner Image Provisioner
  2.0.359.1

Repository & Workflow Files
Affected repository: https://github.com/jkazimierczak/quizcamp
Affected workflow file: https://github.com/jkazimierczak/quizcamp/actions/runs/8165348642/workflow
test.yml:
name: Tests

on:
  push:
    branches:
      - main
  pull_request:
    branches: ["*"]

jobs:
  unit-tests:
    name: Run unit tests
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v4

      - name: Build
        uses: ./.github/actions/build

      - name: Run tests
        run: pnpm test

./.github/actions/build:
name: "Build"

description: "Sets up repository"

runs:
  using: "composite"
  steps:
    - name: Check out source code
      uses: actions/checkout@v4

    - name: Set up pnpm
      uses: pnpm/action-setup@v2
      with:
        version: latest

    - name: Install Node.js
      uses: actions/setup-node@v4
      with:
        node-version: "20.11.0"
        cache: "pnpm"

    - name: Install dependencies
      shell: bash
      run: pnpm install

Additional context
I'm making my repository public for the time of this bug report. Feel free to fork the repo.
Platforms affected

[ ] Azure DevOps
[X] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[X] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[ ] macOS 14 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
20240304.1.0
https://github.com/jkazimierczak/quizcamp/actions/runs/8165348642/job/22322341581?pr=34
Is it regression?
https://github.com/jkazimierczak/quizcamp/actions/runs/8165278837/job/22322151833
Expected behavior
test action works and succeeds, just how it succeeded prior to update, with ubuntu-latest version 20240225.1.0.
Actual behavior
test runs, but halts at the build step of tsup. From there it never ends and has to be terminated manually and potentially restarted multiple times for the CI to pass.
Repro steps

Fork the repository.
Trigger any change to pickup.
If Run unit tests action is run with ubuntu-latest version 20240304.1.0, see if it succeeds past the tsup build command.

Tranferring to setup-node as it does not seem to be image-connected

Thank you for calling me.
This project is alive.
However, there was a need to organize the setting method for the language to be built. I'm currently working on another personal app. Thank you for your continued support as we will continue to make it public. If you would like to join us in this endeavor, please let us know in what areas you can help.
And please tell us about your background. Required for positions and development team composition. I would like to increase the development team to 20 people. This platform requires experts in 10-12 fields. Further details will be provided after you become a participant. Thank you. My contact information is<EMAIL_ADDRESS>This is<EMAIL_ADDRESS>

Hello @jkazimierczak! 👋 ,
Based on the details provided, it appears the setup-node action is correctly setting up Node.js version 20.11.0 as specified in your ./.github/actions/build workflow file.
The problem seems to occur later, during the Run tests step, which is independent of the setup-node action. There could be several possible reasons for this, including a bug in the test itself, a problem with the environment, or an issue with the dependencies. It might be helpful to investigate these areas.
Please Feel free to reach us out incase of any concerns. Thank you!

Hello @priyagupta108!
That's correct, although it started only after the runner was at the version of 20240304.1.0. At the time of opening the issue I haven't updated any of my dependencies, nor configs. I also run all of the checks locally before pushing, so I doubt that it was something wrong with the project environment itself. The only thing that changed was the version of the runner, thus I though that might be the cause.
After the runner was updated from 20240304.1.0 to newer version (such as 20240317.1.0), it hasn't happened again. I'm self-closing this for now, as this seemed like a momentary problem with the past version of runner, which probably won't be investigated further.


VPS IP page for KVM showing game firewall status and rules

There is a little bug, after returning to VPS list from IP settings there are still requests made to rules endpoint

I forgot saving interval ID, fixed.

Awesome work ! :+1:


Clean up rails autogenerated cruft

One example is the courses controller. Rails gives us new, edit, update, etc by default. I can't really think of a situation where a user would be modifying the courses directly, since the data should be coming in correctly from SIS (spoiler: it's currently not), so making modifications would really be one-off cases, and not actually part of the application.

Our test coverage is about to go through da roof


Check mCamera is not null before trying to access methods

When running in Android emulator, the app crashes due to error:
AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.hardware.Camera.setPreviewCallback(android.hardware.Camera$PreviewCallback)' on a null object reference
Checking for the reference makes testing a lot easier

Cheers!


Bulk actions for Problem list

It would be very useful to be able to perform actions in bulk on the problem list. So, we'll need some sort of multi-select, and buttons to perform the same action on everything selected.

I think it should go beyond just the problem list. I would love to see a general bulk edit option.
 Uploaded about 10, printed 3, liked 1. Now I need to go back add an 'esp32' and 'printed' tags to those projects, remove '!new' etc. I was hoping to find a list similar to the non-graphics 'main' page, with checkboxes and bottom-edit-columns. Maybe I'm doing this the hard way, but what I ended up with is: "open model, click edit, click tags, update them (lots of forced clicking on text), click save, hit back (edit page), hit back (results), repeat."
I would ideally just check them off a list, select their tags and hit save.

this would fantastic; i uploaded a file compressed on mac OS and it generates the __MACOS and the spotlight folders; so from 1 archive i'm having to purge hundreds of empty folders


Mutation testing of PUC Rio Lua stucks on 1406'th mutant out of 1841

How to reproduce

download lua source code (https://www.lua.org/ftp/lua-5.4.3.tar.gz) and unpack it
update CC options in src/Makefile:

--- src/Makefile        2021-04-24 18:38:42.314883151 +0300
+++ src/Makefile.orig   2021-04-24 18:38:35.026873188 +0300
@@ -6,7 +6,7 @@
 # Your platform. See PLATS for possible values.
 PLAT= guess

-CC= clang -fembed-bitcode -g
+CC= gcc -std=gnu99
 CFLAGS= -O2 -Wall -Wextra -DLUA_COMPAT_5_3 $(SYSCFLAGS) $(MYCFLAGS)
 LDFLAGS= $(SYSLDFLAGS) $(MYLDFLAGS)
 LIBS= -lm $(SYSLIBS) $(MYLIBS)

change dir to src and build Lua interpreter with make
run Mull in src directory:  mull-cxx -keep-executable -mutate-only -output=lua.mutated -compilation-flags="-isystem /usr/include/linux/" -linker-flags="-lm -Wl,-E -ldl" lua
download lua-Harness (git clone https://framagit.org/fperrad/lua-Harness)
set LUA env variable with path to mutated Lua binary (export LUA=/home/sergeyb/sources/lua-5.4.3/src/lua.mutated)
run testing: cd lua-Harness/test_lua && mull-runner $LUA -test-program=prove -- --exec="$LUA" 000-sanity.t

Expected
successful testing
Actual
testing stuck on 1406'th mutant (-debug option doesn't provide more details):
$ mull-runner $LUA --debug -test-program=prove -- --exec="$LUA" 000-sanity.t
[debug] Diagnostics: Debug Mode enabled. Debug-level messages will be printed.
[info] Warm up run (threads: 1)
       [################################] 1/1. Finished in 62ms
[info] Baseline run (threads: 1)
       [################################] 1/1. Finished in 55ms
[info] Running mutants (threads: 8)
       [########################--------] 1406/1841
<process is stalled>

Everything is ok when echo used as a test program:
$ mull-runner $LUA --debug -test-program=echo
Versions
sergeyb@pony:~/sources/lua-5.4.3$ mull-cxx --version
Mull: LLVM-based mutation testing
https://github.com/mull-project/mull
Version: 0.10.0-pr855
Commit: 84b5d8b
Date: 23 Apr 2021
LLVM: 11.0.0

it's interesting that mutated binary segfaults:
$ ./lua.mutated
Lua 5.4.3  Copyright (C) 1994-2021 Lua.org, PUC-Rio
> a = 1
Segmentation fault

The smallest crasher I could find so far:
mull-cxx \
  -keep-executable \
  -mutate-only \
  -output=lua.mutated \
  -mutators=cxx_post_inc_to_post_dec \
  -linker-flags="-lm -Wl,-E -ldl" \
  -include-path=lvm.c \
  lua

@ligurio I've finally managed to find the root cause behind this crash. I also have a rough idea how to fix it, so let's hope we can close this issue soon 🤞

(I should've linked the root cause explanation https://github.com/mull-project/mull/issues/961)

Turned out, I don't yet know how to implement a proper fix, so for the time being I'll add a check for functions using jump tables to not miscompile them.
I double checked, and with #963 merged you can build and run Mull against Lua.
I'll release a hotfix version in the next couple of days and will close this issue.
The root cause will be tracker separately in #961.

I'm trying to reproduce an issue with 0.15.1 and stuck with a problem "error: Unknown attribute kind (68) (Producer: 'LLVM12.0.1' Reader: 'LLVM 10.0.0')":
Change src/Makefile:
--- Makefile.orig       2022-01-31 13:55:04.759326427 +0300
+++ Makefile    2022-01-31 13:55:16.667338525 +0300
@@ -6,8 +6,9 @@
 # Your platform. See PLATS for possible values.
 PLAT= guess

-CC= gcc -std=gnu99
-CFLAGS= -O2 -Wall -Wextra -DLUA_COMPAT_5_3 $(SYSCFLAGS) $(MYCFLAGS)
+CC= clang-12 -fembed-bitcode -g
+MULL_FLAGS= -fexperimental-new-pass-manager -fpass-plugin=/usr/lib/mull-ir-frontend-12 -grecord-command-line
+CFLAGS= -O2 -Wall -Wextra -DLUA_COMPAT_5_3 $(SYSCFLAGS) $(MYCFLAGS) $(MULL_FLAGS)
 LDFLAGS= $(SYSLDFLAGS) $(MYLDFLAGS)
 LIBS= -lm $(SYSLIBS) $(MYLIBS)

Compile Lua:
sergeyb@pony:~/sources/lua-5.4.3/src$ make
Guessing Linux
make[1]: Entering directory '/home/sergeyb/sources/lua-5.4.3/src'
make all SYSCFLAGS="-DLUA_USE_LINUX" SYSLIBS="-Wl,-E -ldl"
make[2]: Entering directory '/home/sergeyb/sources/lua-5.4.3/src'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/sergeyb/sources/lua-5.4.3/src'
make[1]: Leaving directory '/home/sergeyb/sources/lua-5.4.3/src'
sergeyb@pony:~/sources/lua-5.4.3/src$ mull-cxx-12 -keep-executable -mutate-only -output=lua.mutated -compilation-flags="-isystem /usr/lib/llvm-12/lib/clang/12.0.1/include" -linker-flags="-lm -Wl,-E -ldl" -linker=clang++ lua
...
[info] Compiling original code (threads: 8)
       [################################] 33/33. Finished in 798ms
[info] Link mutated program (threads: 1)
[error] Cannot link program
status: Failed
time: 625ms
exit: 1
command: clang++ -lm -Wl,-E -ldl /tmp/mull-4eb88e.bc /tmp/mull-505f3b.bc /tmp/mull-1b1663.bc /tmp/mull-4710a4.bc /tmp/mull-76d4ed.bc /tm
p/mull-52e92a.bc /tmp/mull-4c5b26.bc /tmp/mull-ccd802.bc /tmp/mull-bbcec5.bc /tmp/mull-ce3b90.bc /tmp/mull-8da362.bc /tmp/mull-ba3096.bc
 /tmp/mull-34d564.bc /tmp/mull-54129b.bc /tmp/mull-5ab443.bc /tmp/mull-bbb231.bc /tmp/mull-1d9e2f.bc /tmp/mull-b17f5b.bc /tmp/mull-14063
3.bc /tmp/mull-85ea77.bc /tmp/mull-1b227b.bc /tmp/mull-444a3d.bc /tmp/mull-886719.bc /tmp/mull-5a750a.bc /tmp/mull-257860.bc /tmp/mull-3
75e2e.bc /tmp/mull-63fd34.bc /tmp/mull-1c6199.bc /tmp/mull-521c92.bc /tmp/mull-1ed4a6.bc /tmp/mull-33a4a1.bc /tmp/mull-698274.bc /tmp/mu
ll-8cc9c6.bc -o lua.mutated
stdout:
stderr: error: Unknown attribute kind (68) (Producer: 'LLVM12.0.1' Reader: 'LLVM 10.0.0')
1 error generated.
error: Unknown attribute kind (68) (Producer: 'LLVM12.0.1' Reader: 'LLVM 10.0.0')
...

@AlexDenisov, could you tell me how to resolve it?

@ligurio with the IR frontend, you no longer need mull-cxx. Just run mull-runner-12 against lua executable - it has all the mutant in it already.

@AlexDenisov Nice! Finally it works, thanks! :)
[info] Mutation score: 13%
[info] Total execution time: 130378ms


Does not open the folder

VSCode Version: 1.8.1
OS Version: win 10

Steps to Reproduce:

right click on any file and open it with visual studio.
click on explorer and it is said no folder opened which is a problem.
https://postimg.org/image/jpw8sbmsx/

if I have to use another file of the folder then I have to open the folder manually or I have to drag a file inside. I request to open the folder automatically as atom does. its easier to work.

When you select a single file then VS Code opens the single file. When you select a folder in the explorer then VS Code opens the folder. Therefore rather than opening a single file you should open its parent folder in VS Code.
Assigning the issue to @chrmarti he is looking into improving the getting started experience and mentioned this issue in a recent discussion.

@egamma I know that but I wanted to use VS code to peek files. It would be a nice feature to have and makes more scene rather than showing a open folder button inside vs code. Neither atom will be a easy to use option for peeking at files. But I love VS code more. :)

Related: #15654

Pushed #20671, which will use the .vscode folder as a hint that its folder should be opened. We have so far avoided always opening a folder, because that might not be what the user wants us to do. If we still decided to do that, we might put it behind a setting.

Closing as designed, I think our current behaviour is fine.


Docker upgrade fails

I'm using the version from AWS marketplace, and when I try to upgrade following the documentation:
docker exec -it sesdashboard-php-fpm composer install
I receive the following error message:
[Composer\Downloader\TransportException]
curl error 6 while downloading https://flex.symfony.com/versions.json: Could not resolve host: flex.symfony.com
It looks like it's using the old Flex infrastructure, are there instructions to update it?

Hello!
Unfortunately, I can't reproduce an error. Fresh install works fine, so maybe it is an issue with update flow.
There was another issue with Dockerfile for php recently, maybe they are related.
Please try git pull fresh changes again, make sure that composer.json, composer.lock, symfony.lock were updated with actual versions.
Run docker-compose build php-fpm --no-cache
And other steps from upgrade docs
$ docker exec -it sesdashboard-php-fpm composer install
$ docker exec -it sesdashboard-php-fpm ./bin/console doctrine:migrations:migrate -n
$ docker exec -it sesdashboard-php-fpm ./bin/console cache:clear
$ docker exec -it sesdashboard-php-fpm ./bin/console cache:warmup


KNN Classifier Issue

Hi,
I found this work very interesting and plan to work on similar topics. However I encounter some issues:
(1) For the fine-tuning example with Barlow Twins and CIFAR-100, should it be barlow.sh instead of barlow_distill.sh? Otherwise, we need to provide the pretrained model in order to successfully run the code.
(2) If I enable the the KNN online evaluation by setting disable_knn_eval = False, there was an issue showing empty test feature and expect argument in base.py line 432. I saw the previous closed issue saying the similar thing but it still appears even if I set a meaningful online_eval_batch_size = 256.
Thanks for your help!

Btw, is the linear evaluation support for CIFAR dataset?

Hi,

yes it was a typo, I have just fixed it.
Ok, can you provide the script you used and the full output error?

Offline linear evaluation does not improve on CIFAR so we just use online linear eval.

Thanks for your reply!
Basically, when I run the example script with Fine-tune Barlow on CIFAR: DATA_DIR=/path/to/data/dir/ CUDA_VISIBLE_DEVICES=0 python job_launcher.py --script bash_files/continual/cifar/barlow.sh. It shows up an error "File "cassle/methods/base.py", line 432, in training_step self.knn( and File "cassle/utils/knn.py", line 89, in compute test_features = torch.cat(self.test_features) RuntimeError: There were no tensor arguments to this function (e.g., you passed an empty list of Tensors), but no fallback function is registered for schema aten::_cat.  This usually means that this function requires a non-empty list of Tensors."
It seems that in base.py line 432, when we call self.knn(), only train_features/targets are specified and test_features/targets are missing, this cause the raised error. When I manually set self.disable_knn_eval = True, the code can run without error.
Thanks for your help!

I encountered the same error "File "cassle/methods/base.py", line 432, in training_step self.knn( and File "cassle/utils/knn.py", line 89, in compute test_features = torch.cat(self.test_features)...", And I did the same thing with @pp1016 to set --disable_knn_eval in bash file "barlow.sh",and another error was encountered:
Traceback (most recent call last):
File "main_pretrain.py", line 224, in
main()
File "main_pretrain.py", line 220, in main
trainer.fit(model, train_loaders, val_loader)
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 737, in fit
self._call_and_handle_interrupt(
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 682, in _call_and_handle_interrupt
return trainer_fn(*args, **kwargs)
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 772, in _fit_impl
self._run(model, ckpt_path=ckpt_path)
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 1195, in _run
self._dispatch()
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 1274, in _dispatch
self.training_type_plugin.start_training(self)
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/plugins/training_type/training_type_plugin.py", line 202, in start_training
self._results = trainer.run_stage()
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 1284, in run_stage
return self._run_train()
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 1314, in _run_train
self.fit_loop.run()
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/loops/base.py", line 145, in run
self.advance(*args, **kwargs)
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/loops/fit_loop.py", line 234, in advance
self.epoch_loop.run(data_fetcher)
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/loops/base.py", line 145, in run
self.advance(*args, **kwargs)
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/loops/epoch/training_epoch_loop.py", line 193, in advance
batch_output = self.batch_loop.run(batch, batch_idx)
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/loops/base.py", line 145, in run
self.advance(*args, **kwargs)
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/loops/batch/training_batch_loop.py", line 88, in advance
outputs = self.optimizer_loop.run(split_batch, optimizers, batch_idx)
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/loops/base.py", line 145, in run
self.advance(*args, **kwargs)
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/loops/optimization/optimizer_loop.py", line 215, in advance
result = self._run_optimization(
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/loops/optimization/optimizer_loop.py", line 266, in _run_optimization
self._optimizer_step(optimizer, opt_idx, batch_idx, closure)
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/loops/optimization/optimizer_loop.py", line 378, in _optimizer_step
lightning_module.optimizer_step(
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/core/lightning.py", line 1651, in optimizer_step
optimizer.step(closure=optimizer_closure)
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/core/optimizer.py", line 164, in step
trainer.accelerator.optimizer_step(self._optimizer, self._optimizer_idx, closure, **kwargs)
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/accelerators/accelerator.py", line 336, in optimizer_step
self.precision_plugin.optimizer_step(model, optimizer, opt_idx, closure, **kwargs)
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/plugins/precision/native_amp.py", line 85, in optimizer_step
closure_result = closure()
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/loops/optimization/optimizer_loop.py", line 160, in call
self._result = self.closure(*args, **kwargs)
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/loops/optimization/optimizer_loop.py", line 142, in closure
step_output = self._step_fn()
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/loops/optimization/optimizer_loop.py", line 449, in _training_step
check_finite_loss(result.closure_loss)
File "/home/zw/anaconda3/envs/cassle/lib/python3.8/site-packages/pytorch_lightning/loops/utilities.py", line 39, in check_finite_loss
raise ValueError(f"The loss returned in training_step is {loss}.")
ValueError: The loss returned in training_step is nan.
Is there any way to solve it? Thanks for your help! @DonkeyShot21

I was able to solve the issue.
In https://github.com/DonkeyShot21/cassle/blob/main/cassle/methods/base.py#L432 and https://github.com/DonkeyShot21/cassle/blob/main/cassle/methods/base.py#L464 there should be self.knn.update instead of self.knn. Calling metric() does metric.update() and then metric.compute() but in training_step and validation_step we only want to call update() as not all the data has been passed to the metric yet.
However, when I run the code with such fix the results are not as expected: for finetuning of BarlowTwins I get ~55% accuracy for online linear probe but only ~35% of knn accuraccy. According to the paper the difference should not be so high (ImageNet100 in Tab. 4 vs backbone eval in Tab. C).
Does anyone have a clue why the difference is so high? @DonkeyShot21 @vturrisi ?

Hi! I am not sure I understand the issue. Table C reports results using offline k-nn, while I think you are running online k-nn, am I right? Table 4 is linear evaluation, that is well known to be better than k-nn, especially with CNNs.

There are two main differences: (a) the features are collected with different parameter configs, (b) as you said, augmentations. While (a) should not be too bad at the end of training where the lr is very low, (b) is still a big issue. Normally people use no augmentations for knn afaik. Also remember that, especially on CIFAR, these augmentations are very strong and they corrupt images completely, in some cases they crop up to 3px x 3px. We never changed the hyperparams, so those that you linked should be correct.


feat: add type safe check when sending custom request / response types

This PR will give end developers more visiblity when a custom request / response type is not JSON.NET serializer safe. This check is only performed once when the custom type is first used. A JsonSerializationException is thrown when a type is considered unsafe.

This also may resolve #79 partially


Revert "TWEAK: disable inertia_errors (dev#1197) (#2)"

This reverts commit 2a72c36e61a7fff84f417fd71b2b15d4f7e8ee68.

 Remove session method name


Fix support for symfony 4.4 in SymfonyProfiler

Symfony 4.4 uses the older method getMasterRequest() instead of getMainRequest().   Since 4.4 is supported by this library at this time, I propose this change so it correctly works using symfony 4.4.

Thanks! I've tagged 1.0.1

@adrienbrault , thanks for merging it in!
Nice catch on the ProfilerMiddleware.
I admit I did not check the PHPStan first before committing.
I also did not check for the existence of a Contributing.md-file first, although I've checked this file in other projects I submitted patches for.  It can help new contributors on what checks will run and what is to be expected from a patch.
I'd like to express my thanks for this project, I find it very helpful to be able to profile commands and this library made it very easy to enable this. :+1:


CentOS 7 netcat droppin replacement 'nmap-ncat' does not work

CentOS 7 does not have the original netcat package, instead it provides a droppin (almost?) 'nmap-ncat' package: https://nmap.org/ncat/
This exposes a 'nc' binary, which does have the -U command. Unfortunately, it seems to expose the help message on stdout, not stderr which is assumed in https://github.com/ymnk/jsch-agent-proxy/blob/master/jsch-agent-proxy-usocket-nc/src/main/java/com/jcraft/jsch/agentproxy/usocket/NCUSocketFactory.java#L45

@stromnet Did you find a work around for this?

Good question, I don't actually remember if and how.. Not even sure what I was using it for!


Styles inheritance

This PR provides:

Usage of colors extracted from configuration instead of using scss variables
Unused scss variables removed
Login page background is added to Context in order to be configurable

Would it make sense to scan through commits and try to rebase them? Also, are any of these commits breaking changes?

Shall we add a wiki page explaining how to use those new variables and what is the outcome?

Would it make sense to scan through commits and try to rebase them? Also, are any of these commits breaking changes?

Yes
No

Shall we add a wiki page explaining how to use those new variables and what is the outcome?

Yes, I think I can document it for comfy usage, and also write the rules how to properly use colors in newly created components, so that we can avoid issues with broken color schemes.

Shall we add a wiki page explaining how to use those new variables and what is the outcome?

Yes, I think I can document it for comfy usage, and also write the rules how to properly use colors in newly created components, so that we can avoid issues with broken color schemes.

Please add documentation here https://github.com/energywebfoundation/origin/wiki/UI-Customizations

Looks good now 👍


How to get list of work items in azure boards using a command in Azure CLI

https://docs.microsoft.com/en-us/cli/azure/ext/azure-devops/boards/work-item?view=azure-cli-latest#ext_azure_devops_az_boards_work_item_show
refer to this above url I did not find any related command to list all work items

Not sure why you have logged and issue on this repo as it is not the home of Azure CLI - it's home is here I suggest you log the issue there.


Function to find all Resources of a specific type (to use with Fn::ForEach)

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request
An intrinsic function that can find all resources of a specific type. A bonus would be an ability to filter them based upon a Logical Id pattern or even other properties.
Tell us about the problem you are trying to solve. What are you trying to do, and why is it hard?
Example use case:
I would like to add an AWS::Logs::SubscriptionFilter for every AWS::Logs::LogGroup defined in my template.  Every property is the same for the SubscriptionFilter except for the Logical Id, and the LogGroupName.  This seems like a great use case for Fn::ForEach, if I could just get the list of Logical Ids for the LogGroups.  One other note: the LogGroups may have some variability so I cannot drive their creation using a list or map (and so do not have that to drive the creation of the SubscriptionFilter resources).  I have been unable to find a satisfactory solution in CloudFormation examples or documentation.
Without this I end up having to maintain and copy/paste a lot of boilerplate configuration and run the risk of missing a SubscriptionFilter for a LogGroup.
Are you currently working around this issue?
I am currently copying and pasting the same AWS::Logs::SubscriptionFilter block and then changing the resource id and LogGroupName.
What is the expected behavior with this new feature
Rather than having to do something like this (simplified example)
AWSTemplateFormatVersion: '2010-09-09'
Transform:
- AWS::LanguageExtensions
- AWS::Serverless-2016-10-31
Description: Example to demonstrate need

Globals:
  Function:
    Runtime: nodejs16.x

Resources:
  FirstFunction:
    Type: AWS::Serverless::Function
    Properties:
      Architectures:
        - arm64
      MemorySize: 128
      CodeUri: .
      Handler: index.handler

  FirstFunctionLogGroup:
    Type: AWS::Logs::LogGroup
    Properties:
      LogGroupName: !Sub "/aws/lambda/${FirstFunction}"

  FirstFunctionLogSubscriptionFilter:
    Type: AWS::Logs::SubscriptionFilter
    Properties:
      DestinationArn: !Sub arn:aws:lambda:${AWS::Region}:${AWS::AccountId}:function:common-log-ingestion
      FilterPattern: ''
      LogGroupName: !Ref FirstFunctionLogGroup

  SecondFunction:
    Type: AWS::Serverless::Function
    Properties:
      Architectures:
        - x86_64
      MemorySize: 256
      CodeUri: .
      Handler: index.handler

  SecondFunctionLogGroup:
    Type: AWS::Logs::LogGroup
    Properties:
      LogGroupName: !Sub "/aws/lambda/${SecondFunction}"

  SecondFunctionLogSubscriptionFilter:
    Type: AWS::Logs::SubscriptionFilter
    Properties:
      DestinationArn: !Sub arn:aws:lambda:${AWS::Region}:${AWS::AccountId}:function:common-log-ingestion
      FilterPattern: ''
      LogGroupName: !Ref SecondFunctionLogGroup

I am envisioning something like this (in this case I am driving both the LogGroup and the SubscriptionFilter off of the Function resources):
AWSTemplateFormatVersion: '2010-09-09'
Transform:
- AWS::LanguageExtensions
- AWS::Serverless-2016-10-31
Description: Example to demonstrate need

Globals:
  Function:
    Runtime: nodejs16.x

Resources:
  FirstFunction:
    Type: AWS::Serverless::Function
    Properties:
      Architectures:
        - arm64
      MemorySize: 128
      CodeUri: .
      Handler: index.handler

  SecondFunction:
    Type: AWS::Serverless::Function
    Properties:
      Architectures:
        - x86_64
      MemorySize: 256
      CodeUri: .
      Handler: index.handler

  # Iterate over each AWS::Serverless::Function (bonus: Logical Id matching pattern "^.*Function")
  # and for each Function create a LogGroup and SubscriptionFilter for that group
  Fn::ForEach::FunctionLogGroups:
    - FunctionLogicalId
    - Fn::FindResources:
        Type: AWS::Serverless::Function
        Pattern: ^.*Function
    - "${FunctionLogicalId}LogGroup":
        Type: AWS::Logs::LogGroup
        Properties:
          LogGroupName: !Sub "/aws/lambda/${FunctionLogicalId}"

      "${FunctionLogicalId}SubscriptionFilter":
        Type: AWS::Logs::SubscriptionFilter
        Properties:
          DestinationArn: !Sub arn:aws:lambda:${AWS::Region}:${AWS::AccountId}:function:common-log-ingestion
          FilterPattern: ''
          LogGroupName: !Ref ${FunctionLogicalId}LogGroup

Additional context
This could save time and prevent issues caused by copy/paste errors and omissions.
Attachments

I like this idea, but until something like that is supported, you could potentially create log and subscription resources from the same Collection parameter, in a single Fn::ForEach loop.

I think either support for yaml anchors and tags, or an expansion of the SAM globals section (https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-specification-template-anatomy-globals.html) would be a cleaner solution for this

I like this idea, but until something like that is supported, you could potentially create log and subscription resources from the same Collection parameter, in a single Fn::ForEach loop.
EDIT: Maybe you've said that approach wouldn't work for your use case? If so, would you mind elaborating on why, maybe with an example? I'm wondering whether it would work if you included some conditions in your loop, to cover variations.

I will be giving this a try for my use case to see if it is good enough.  My concern about using a collection was that I might miss the name of a Lambda resource or perhaps typo the name (the latter would probably fail fast).  I lose the resource "type" connection and the ability to automatically include any new Lambda resources that are added without needing to copy and past the names.

I think either support for yaml anchors and tags, or an expansion of the SAM globals section (https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-specification-template-anatomy-globals.html) would be a cleaner solution for this

I don't think globals would quite cover the use case, YAML anchors are an interesting idea, though I would like the ability to override certain properties (like names of things), and overriding the whole property might not be what is needed.

My concern about using a collection was that I might miss the name of a Lambda resource or perhaps typo the name (the latter would probably fail fast). I lose the resource "type" connection and the ability to automatically include any new Lambda resources that are added without needing to copy and past the names.

Makes sense - In was basing my suggestion on what you said here ...

I would like to add an AWS::Logs::SubscriptionFilter for every AWS::Logs::LogGroup defined in my template.

But I now see you later clarified ...

I am driving both the LogGroup and the SubscriptionFilter off of the Function resources

Either way, I like the concept of the intrinsic function you propose. Please let us know how your testing goes - if you get something working, I'd love to see an example snippet.


seaborn

If one is up for it, it would be great to get the viz compatible with seaborn as it is become more and more standard for scientific plotting.
At the moment, we still get some weird viz every now and then: e.g. the evoked plot lines are behind the grid.

What do you think?

Sounds good. Probably just need to uniformly bump up our z values

I like seaborn, I think it's a great lib. I'd be willing to contribute to this.
But note seaborn is basically a one-man job, and thus it's sometimes not always as responsive as one could wish for.

Apart from what Jona says,
I think we probably agree that wed don't want to use Seaborn as default or
use it in our examples. It's very easy anyways to use it yourself and we
should not add more dependencies and I really prefer to get viz right at a
diagnostic level. We don't want beautiful but functional plots that really
confront you with the reality of your data instead of making you dream. You
can easily leverage the existing Python eco-system to make beautiful plots
for your papers.
However I agree that we should make it as easy as possible to use 3rd party
viz libraries such as Seaborn, ggplot, mpld3, bokeh, plotly et al.
If this means to adjust a few defaults I'm fine with this. But it should
not interfere with standard "ugly" default matplotlib-style diagnostic
plotting.
This also means that we should not optimize things for Seaborn only, there
are many potentially interesting 3rd party libraries.
On Sat, Feb 20, 2016 at 1:41 AM, jona-sassenhagen<EMAIL_ADDRESS>wrote:

I like seaborn, I think it's a great lib. I'd be willing to contribute to
this.
But note seaborn is basically a one-man job, and thus it's sometimes not
always as responsive as one could wish for.
—
Reply to this email directly or view it on GitHub
https://github.com/mne-tools/mne-python/issues/2919#issuecomment-186468005
.

+1
On Friday, 19 February 2016, Denis A. Engemann<EMAIL_ADDRESS>wrote:

Apart from what Jona says,
I think we probably agree that wed don't want to use Seaborn as default or
use it in our examples. It's very easy anyways to use it yourself and we
should not add more dependencies and I really prefer to get viz right at a
diagnostic level. We don't want beautiful but functional plots that really
confront you with the reality of your data instead of making you dream. You
can easily leverage the existing Python eco-system to make beautiful plots
for your papers.
However I agree that we should make it as easy as possible to use 3rd party
viz libraries such as Seaborn, ggplot, mpld3, bokeh, plotly et al.
If this means to adjust a few defaults I'm fine with this. But it should
not interfere with standard "ugly" default matplotlib-style diagnostic
plotting.
This also means that we should not optimize things for Seaborn only, there
are many potentially interesting 3rd party libraries.
On Sat, Feb 20, 2016 at 1:41 AM, jona-sassenhagen <
<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>>
wrote:

I like seaborn, I think it's a great lib. I'd be willing to contribute to
this.
But note seaborn is basically a one-man job, and thus it's sometimes not
always as responsive as one could wish for.
—
Reply to this email directly or view it on GitHub
<
https://github.com/mne-tools/mne-python/issues/2919#issuecomment-186468005
.

—
Reply to this email directly or view it on GitHub
https://github.com/mne-tools/mne-python/issues/2919#issuecomment-186475174
.

looks like an easy fix for a new contributor. I'll mark this issue (bumping up the zorder) as easy and change the title if @kingjr is okay with it. I agree with Denis that our plots are more meant for diagnostics rather than "publication-ready".

isn't someone working on mne.io.raw_to_publication? that pr is very welcome ;)

+1 but it has to work for all input file formats, experimental paradigms,
and destination journals

mne.io.raw_to_publication(fname, journal='Nature')

mne.io.raw_to_publication(fname, journal='Nature')

journal="Nature" should be default, shouldn't it?

But don't add it to the raw objet, ok?
On Sun, Feb 21, 2016 at 7:36 PM, Jean-Rémi KING<EMAIL_ADDRESS>wrote:

mne.io.raw_to_publication(fname, journal='Nature')
journal="Nature" should be default, shouldn't it?
—
Reply to this email directly or view it on GitHub
https://github.com/mne-tools/mne-python/issues/2919#issuecomment-186896232
.


Replacing MT with xoroshiro128+

As per request, I've made the commits against develop instead of master. Otherwise, this is identical to PR #28.

The comment on the commit probably refers to earlier changes - that was my bad. I fixed an overflow issue in the implementation, but when I committed, I only mentioned other unrelated changes.
The suggestion for extracting a random Boolean value is a bit puzzling - given the statistical strength of xoroshiro128+, using the method you described should work fine. I suspect this is Vigna being overly-cautious more than anything. As far as avoiding the 'everywhere-zero' problem, I deliberately xor the incoming seed with some random bytes. While it is theoretically possible to end up with an everywhere-zero result, it is extremely difficult, especially since I also initialize half of the RNG state with the bitwise complement of the input.
My main motivation for this change was that MT is a really slow PRNG, and xoroshiro128+ is just as good statistically, but runs faster and needs less state (as well as being considerably less complex). I'm a bit of an obsessive perfectionist in this regard, and it seemed like a very easy improvement. My own tests bear out a significant speedup (based on the tests provided).

(I'm still expecting to merge this as part of the next release, barring running into major issues, but have been busy with work and haven't gotten back to it yet.)

I'm expecting to merge this PR this soon; I've finally got time to work on this again.
From experiments so far, I see that simple numeric seeds (0, 1, ...) do take a couple steps to get mixed well, but I could use the hash of the provided seed.

@silentbicycle To avoid the problem of bad seeds, I use the advice given here and XOR the seed with 16 static random bytes in the code I've submitted.

Xoroshiro128+ has been deprecated in favor of Xoshiro256**, so I'm probably going to switch it out for that in the 0.5.0 release, or possibly PCG instead. In any case, de-coupling the RNG and generalizing the comments was useful. Thanks.
(The 0.5.0 release has taken a while, because there's a ton of rework for multi-core support.)

After some further testing (after merging the 0.4.4 release back into 0.5.0's develop) I think I'm going to revert this -- even with the current initialization, Xoroshiro128+ is causing a bunch of misc. test failures, particularly for tests that check that some large number of trials should always discover at least one failure. (Some of these are in the 11 you alluded to in #28.)
After changing the RNG again, there really isn't anything left of your changes in this PR. I'm still going to mention in the CHANGELOG that you helped with switching to a faster RNG, though.


Issue in About Section

Describe the bug
I noticed a safe area issue in the about section which makes it less attractive while scrolling.
To Reproduce
Steps to reproduce the behavior:

Run the app on VSCode or any other IDE of your choice. View the app through your emulator or mobile device(I viewed it on a Google Pixel 4 Emulator)
Navigate to the 4th page(About Section) in the bottom navigation bar to view the issue.

Expected behavior
The text widget 'About the Dev' shouldn't be seen in the safe area while scrolling as compared to other sections.
Screenshots

If possible, I would love to work on this issue and solve it as soon as possible

Sure please do go ahead. I'm assigning this issue to you.

Hey if the issue is still open i want to work on this

@Harryalways317 I think @aikanshboyal is currently working on it


Cannot access release notes

The release notes link on the website and the Github release page does not work:
https://groups.google.com/forum/#!topic/ninja-build/nY5Kb7zUvcg
Saying:
The group does not exist or you do not have permission to access it.

Does this link work?
https://groups.google.com/d/msg/ninja-build/nY5Kb7zUvcg/FIIn5j6-EwAJ

Nope, same issue.
You can probably test that in an incognito tab.

You're right, the group settings were messed up. Should work now :)
Thanks for creating the issue.

Thanks for the quick fix!


Implement Routing

@yokuze thanks! Back to you.

Back to you. Here's the diff for easier re-review:
jrthomer@lappy ~/git-clones/silvermine/lambda-express
[ routing ] $ git diff origin/routing..
diff --git a/src/chains/MatchAllRequestsProcessorChain.ts b/src/chains/MatchAllRequestsProcessorChain.ts
index 9139881..e6a147c 100644
--- a/src/chains/MatchAllRequestsProcessorChain.ts
+++ b/src/chains/MatchAllRequestsProcessorChain.ts
@@ -1,12 +1,7 @@
 import ProcessorChain, { IRequestMatchingProcessorChain } from './ProcessorChain';
-import { ErrorHandlingRequestProcessor } from '../interfaces';

 export class MatchAllRequestsProcessorChain extends ProcessorChain implements IRequestMatchingProcessorChain {

-   public constructor(subprocessors: ErrorHandlingRequestProcessor[]) {
-      super(subprocessors);
-   }
-
    public matches(): boolean {
       return true;
    }
diff --git a/tests/integration-tests.test.ts b/tests/integration-tests.test.ts
index f2456d4..d14109c 100644
--- a/tests/integration-tests.test.ts
+++ b/tests/integration-tests.test.ts
@@ -209,7 +209,7 @@ describe('integration tests', () => {
          testWithLastResortHandler(404, '404 Not Found', [ 'X-Path' ]);
       });

-      it('does not affect on already-registered routes when toggled, but does affect routes after toggle', () => {
+      it('has no affect on already-registered routes when toggled, but does affect routes added after toggle', () => {
          expect(app.routerOptions.caseSensitive).to.eql(false);
          app.enable('case sensitive routing');
          expect(app.routerOptions.caseSensitive).to.eql(true);

Looks great!
There was an odd random build failure: https://travis-ci.com/silvermine/lambda-express/jobs/177513237#L478, but just on the Node 10 job 😕
Doesn't seem to be related to the code though.

A similar build failure happened yesterday, too. I restarted the job you linked to and it worked this time.


ES6 module exports  on .vue files

Hello and thank you for making this, it looks very promising.
I tried getlibs on a Vue + TypeScript project and got some trouble with single file components .vue files
index.html:
<!DOCTYPE html>

Loading...

main.ts:
import Vue from 'vue'
import App from './components/App.vue'

new Vue({
	el: '#app',
	render: h => h(App)
})

App.vue:
<template>

		Hello {{ name }}

</template>

gives me
Error: module is not defined
  Evaluating http://localhost:5000/components/App.vue
  Evaluating http://localhost:5000/main.ts
  Loading ./main.ts`

The App.vue!transpiled file :
(function(System, SystemJS) {"use strict";

System.register([], function (_export, _context) {
   "use strict";

   return {
   	setters: [],
   	execute: function () {
   		_export("default", {
   			data: function data() {
   				return { name: "Vue" };
   			}
   		});

   		module.exports.template = "\r\n\t
\r\n\t\tHello {{ name }}\r\n\t
\r\n";
   	}
   };
});
})(System, System);

It looks like it should export with _export.template instead of module.exports.template

At the moment .vue loader works only with es5/require() syntax. Basically it just tries to inject the template property into module.exports object. I'll see if I can do something simple for es6/typescript.

I've changed .vue loader so that ES6 import/export should work now. However it will be transpiled by babel instead of typescript at the moment. That I still have to fix.

Thanks, I can confirm that it is now working with export default.
I let you close this issue when you are done

Not sure if it is a regression or if it is not supported at the moment, but the


Trouble aliasing Squarespace domain.

Hi all,
I am following the steps here and  here using a Squarespace domain but I am having some issues running
now alias deployment [domain] :(
Here is everything that I've done and has worked:

now domains add --external tokenfort.com
Added the TXT record in Squarespace with the key from above
now domains add --external tokenfort.com (success!)
now alias my-deployment-eyhxcwtevc.now.sh tokenfort.com fails provisioning the certificate.

now alias nextjs-oabaobunyc.now.sh tokenfort.com
> tokenfort.com is a custom domain.
> Verifying the DNS settings for tokenfort.com (see https://zeit.world for help)
> Verification OK!
> Provisioning certificate for tokenfort.com
> Error! Unknown error: Error: Invalid challenge response for tokenfort.com. Make sure the DNS rec
ords are correct.
Error: Invalid challenge response for tokenfort.com. Make sure the DNS records are correct.
    at module.exports.EventEmitter.createCert.domain.retry (C:\snapshot\now-cli\lib\index.js:787:1
7)
    at process._tickCallback (internal/process/next_tick.js:109:7)

As per another issue I read, I ran now create cert tokenfort.com but got a similar error:
now cert create tokenfort.com
> Error! Unexpected error. Please try again later. (Invalid challenge response for tokenfort.com.
Make sure the DNS records are correct.)

So maybe I figured I should try changing the nameservers, which I did:

But I get the same error running now alias. Not sure what I've done wrong :(
Thanks for the help.

You need to add your domain without the --external flag so that it points to the zeit.world nameservers.

Remove your domain now domain rm your-domain
Re-add your domain now domain add your-domain
Alias your deployment again now alias deployment-url your-domain

And just wait for DNS to propagate 🙂

Thanks @bntzio. You were a great help. Much appreciated!


is there a equation support?

Question
I am coding a project about formulas. I want to write the formulas in LaTeX format in my word plugin as in the equation feature. At first I tried to put $$ at the beginning, but then I realized that I had to translate it on my own by pressing the equations button, which is word's own feature. I couldn't find any information in the docs about converting it to an equation. How can I do this or when will it be available?

Hi @devmdeniz,
Thanks for reaching out. The Office JS APIs do not currently have support for the Word equation feature. I'd recommend that you submit a feature request to the Microsoft 365 Developer Platform Tech Community.  There, we can gauge community need and interest in new features and prioritize them accordingly.
I'm going to close this issue, since there is nothing actionable to be done in the samples.


Update d2l-enrollments

Just fixes a margin, nothing too exciting.

Not actually required - this change already got pulled into BSI, yay floating versions!


MG-2117 - Remove repository errors from API layer

What type of PR is this?
This is a feature that removes removes repository errors from the api response and only the service error and api errors are sent as part of the response. All errors are logged and can be evaluated from the service logs.
What does this do?
Ensures only errors from the service and api are sent as part of the API response, and leaves repo errors at service level.
Which issue(s) does this PR fix/relate to?

Resolves #2117
Related to #1998

Have you included tests for your changes?
No
Did you document any new/modified feature?
No
Notes

@WashingtonKK
In users/service.go repoerr are returned by service function ,
Could you please change to respective service error and handle them  as you did for other service

For the below request, I get error {"error":"","message":"view entity failed"}
curl --location 'http://localhost/users/tokens/issue' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--data '{
        "identity": "some-random-string",
        "secret": "12345678"
}'

Lets create a separate ticket for this problem.

For the change secret requets, If we send wrong password  like below
curl --location --request PATCH 'http://localhost/users/secret' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer <TOKEN>' \
--data '{
  "old_secret": "wrong-old-password",
  "new_secret": "new-password"
}'

we get response like below
{
    "error": "",
    "message": "failed to issue token"
}

lets address these also in new ticket

Issue token doesn't return proper error
What were you trying to achieve?
Login to Magistrala with unknow / invalid user identity
curl --location 'http://localhost/users/tokens/issue' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--data '{
        "identity": "unknown-users-indentity",
        "secret": "12345678"
}'

What are the expected results?
HTTP/1.1 401 Unauthorized
{
    "error": "",
    "message": "invalid user id or secret"
}

What are the received results?
HTTP/1.1 400 Bad Request
{
    "error": "",
    "message": "view entity failed"
}


VidScheme allow disperse to reuse work done in commit_only

A significant fraction of the work of commit_only is duplicated in disperse. ie. computing polynomial commitments (dominant cost!), bytes_to_field, and possibly other things.
commit_only should return additional data beyond the commitment. At a minimum, it should also return the polynomial commitments
disperse should take a (optional) argument for pre-computed polynomial commitments.
Need to update VidScheme trait with these API changes, then update ADVZ impl to conform.
VidScheme is supposed to be abstract, so we can't just add a poly_commits: Option<Vec<KzgCommit<E>>> arg to disperse. Instead we could add yet another assoc type to VidScheme called DisperseHelperData or whatever. The proposal is something like
trait VidScheme {
  // ...
  type DisperseHelperData: Clone + Debug + DeserializeOwned + Eq + PartialEq + Hash + Serialize + Sync;
  fn commit_only<B>(&self, payload: B) -> VidResult<(Self::Commit, Self::DisperseHelperData)>
  fn disperse<B>(&self, payload: B, helper_data: Option<Self::DisperseHelperData>) -> VidResult<VidDisperse<Self>>
  // ...
}

cc @elliedavidson for visibility.

Discuss: If we change VidScheme trait then we also need to change everything downstream that depends on it. That will be a lot of work. 😕  An alternative is to make only additive changes to VidScheme. ie. new methods commit_only_with_helper_data and disperse_with_helper_data
@akonring If we do make breaking API changes then we should open PRs for everything downstream that will break. In order to do so we need to test everything locally via cargo patch directives.

I don't have a strong opinion on this. I see that breaking changes to VidScheme trait will add more downstream complications but on the other hand adding new methods creates a less clean trait interface. Maybe there are other reasons to not introduce new methods?

We already have an instance of the subtrait pattern with PayloadProver: VidScheme. I suggest we repeat that pattern for VidSchemeWithHelperData: VidScheme. (But please choose a better name!) We'll see how it looks in review and seek more opinions then.

Preliminary design of the sub-trait below:
//! Trait for additional functionality in Verifiable Information Retrieval (VID)
//! for precomputation of specific data that allows for calling
//! methods using the data to save computation for the callee.

use core::fmt::Debug;

use super::{VidDisperse, VidResult, VidScheme};
use ark_std::hash::Hash;
use serde::{de::DeserializeOwned, Serialize};
/// Allow for precomputation of certain data for [`VidScheme`].
pub trait Precomputable: VidScheme {
    /// Precomputed data that can be (re-)used during disperse computation
    type PrecomputeData: Clone + Debug + Eq + PartialEq + Hash + Sync + Serialize + DeserializeOwned;

    /// Similar to [`VidScheme::commit_only`] but returns additional data that
    /// can be used as input to `disperse_precompute` for faster dispersal.
    fn commit_only_precompute<B>(
        &self,
        payload: B,
    ) -> VidResult<(Self::Commit, Self::PrecomputeData)>
    where
        B: AsRef<[u8]>;

    /// Similar to [`VidScheme::disperse`] but takes as input additional
    /// data for more efficient computation and faster disersal.
    fn disperse_precompute<B>(
        &self,
        payload: B,
        data: Self::PrecomputeData,
    ) -> VidResult<VidDisperse<Self>>
    where
        B: AsRef<[u8]>;
}

Currently, looking into the implementation: figure out the data we want to re-use and how to satisfy Serialize + DeserializeOwned for this data. Feedback is welcome.

Looks pretty good. Notes:

data arg of disperse_precompute should probably be a reference type &Self::PrecomputeData
which data to re-use: For ADVZ this will be just a single field poly_commits: Vec<KzgCommit<E>>,, exactly like in the Common struct.
you can use Common as a model for how to satisfy serde traits. I suspect it'll look something like

#[derive(CanonicalSerialize, CanonicalDeserialize, Derivative, Deserialize, Serialize)]
#[derivative(
    Clone(bound = ""),
    Debug(bound = ""),
    Eq(bound = ""),
    Hash(bound = ""),
    PartialEq(bound = "")
)]
pub struct PrecomputeData<E>
where
    E: Pairing,
{
    #[serde(with = "canonical")]
    poly_commits: Vec<KzgCommit<E>>,
}

Because there's no H type param it might be possible to eliminate the derivative attribute with all the bound = "" fields and instead put all those trait bounds into the conventional derive attribute.


More detailed prerequisited installation

I'm new at go, but trying to do sth.
I've installed latest go 1.8.3 and it works, but which next requisites do you mean?
Could you provide at least link so i can find them?
Is go etcd client for v3, this: https://github.com/coreos/etcd/tree/master/clientv3 ?
And what about go docker?
I tried to install go etcd client for v3 but got this error:
work/src/github.com/coreos/etcd/clientv3/client.go:236: dialer.DialContext undefined (type *net.Dialer has no field or method DialContext)
and made it this far.
At this point you have this, which does not provide sufficient information for a noob like me:
1.1.1. Prerequisites
Go 1.7 or higher
Go docker client v17.03
Go etcd client for v3

We'll update all installation instructions on next week.
For this version - all is on active development stage, so I'll close this.
On next week we should complete it.


How to add additional Performance counters in InsightsMetrics table like Perf table

Hello,
This doc seems to be missing information on how to add additional performance counters in the new VMInsights InsightsMetrics table like you can do the the now legacy Perf table that is configured in Log Analytics Data source blade.
If Azure Monitor for VMs it the new way to monitor the performance of a VM, how can we add / get the extra performance counters that are on the VM into this table for Analysis? i.e. ASP.NET Applications(*)\Requests/Sec These will be in the Perf table but not the InsightsMetrics but there is no documentation on how to add them?

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

ID: a2e09b30-7e2a-7b34-9b99-0e05a85aaa14
Version Independent ID: 9b0d3bcb-6c56-25be-db0a-4fbd62dd924d
Content: How to chart performance with Azure Monitor for VMs - Azure Monitor
Content Source: articles/azure-monitor/insights/vminsights-performance.md
Service: azure-monitor
Sub-service: ****
GitHub Login: @bwren
Microsoft Alias: bwren

@ricohomewood  Thanks for your comment. We will review your request and get back to you.

@ricohomewood As per my understanding, when you upgrade VMInsights , all the data will be stored in InsightsMetrics. For more information, kindly refer this document.
@bwren Can you please provide your insights on this issue?

@ricohomewood As per my understanding, when you upgrade VMInsights , all the data will be stored in InsightsMetrics. For more information, kindly refer this document.
@bwren Can you please provide your insights on this issue?

Yes, but that's not my question?
The issue is that the additional performance counters are not in this new table and there is nothing in the docs that tells you how to add them? i.e. in Log Analytics:
Log Analytics > Advanced Settings > Data > Windows Performance Counters
These counters only log to the Perf table and when you upgrade to the VMInsights agent, I would expect these to be honored and added to the InsightsMetrics table but they are not, suggesting there is no feature parity between this and the new agents making the migration to the new VMInsights agents non tenable.
Unless there is somewhere else you add additional performance counters to log into the new InsightsMetrics table? Hence this issue as its not in the docs?
Would I be right in saying that the above location for setting Performance Counters should now be logging into this new table? If so, that doesn't work.

@ricohomewood Apologies for late response. As of now, additional performance counters are being logged in Perf table and the option to enable performance counters to InsightMetrics table is in the roadmap for the next three months.
Hope this answers your question. We will update you on this thread once its available. As there are no further documentation changes, we will close the issue for now. If there are any questions , kindly revert and we will very glad to assist you.

Hello @SwathiDhanwada-MSFT Has this been implemented yet? You noted it was on the roadmap to be delivered over the next 3 months back in May. If not do you have a ETA when this will be delivered so we can move to using this preferred agent?
Thanks

@ricohomewood Thanks for following up on this. As per latest information, the ETA  for sending counters to InsightsMetrics is expected to be completed by the end of 2020.


[Bug] Integration tests don't work on non-x86

Description
Our integration tests fail on other architectures. Here are some things we need to do to:

[x] Fix a bug in our Dockerfile where TARGETARCH is not honored since it is not scoped locally. This causes us to use only amd64 artifacts. - #695
[ ] Remove dependency on ghcr.io/oci-playground/registry:v3.0.0-alpha.1 since its only available for amd64 architectures. Since the notion of OCI Artifact Manifests have seemingly been rejected from the v1.1.0 Image Spec I don't think we need a v1.1.0 compliant registry at least until the v1.1.0 spec has been finalized. We can then remove any tests that use this image - https://github.com/awslabs/soci-snapshotter/blob/801acef5adc5f7976fa7b482e1b1f829e6ee6097/integration/push_test.go#L133 and then set the default registry to be registry:2 here https://github.com/awslabs/soci-snapshotter/blob/801acef5adc5f7976fa7b482e1b1f829e6ee6097/integration/util_test.go#L423
[ ] We have 2 tests that specifically use an amd64 variant of rabbitmq- TestPullWithAribtraryBlobInvalidZtocFormat() and TestPushAlwaysMostRecentlyCreatedIndex(). We should change them to use tags that support multiple architectures.

Steps to reproduce the bug
Run the integration tests on non x86 arch.
Describe the results you expected
Integration tests should work with different architectures.
Host information

OS:
Snapshotter Version:
Containerd Version:

Any additional context or information about the bug
No response

We have 2 tests that specifically use an amd64 variant of rabbitmq- [...] We should change them to use tags that support multiple architectures.

Those tags should be historic and static, not versions that might see backports or other new pushes.

For the second issue, I think we can just skip that test on ARM for now.

@Kern-- Just skipping the test that uses the 1.1 registry is not sufficient. The image and container in question are also used in composeBuildTemplate which is used in TestMain's call to setup(). https://github.com/awslabs/soci-snapshotter/blob/bde429dbb4bc08c3b80920909df240b812a87c62/integration/main_test.go#L129 This can probably also be skipped on other arch, but is nontrivial.
Also the Dockerfile will need to be modified to not attempt to pull the image in question on the wrong arch.
I'd like to discuss re-estimating this.


Android/iOS fixes

Various fixes made while working on the product demo / app template.

Cleaned up how the UI scaling factor is retrieved from the OS and separate it from an application defined scaling factor that can be passed into egui separately

Fix SDLmain not being linked against correctly for android

Embed all direct wgpu dependencies hosted on chainblocks repos

Additionally I made some changes in how the android package is built, it is now managed through CMake too in order to have a bit more flexibility and a smoother workflow without having go through the gradle process.
The script is included through a submodule in cmake/android-cmake/Android.cmake

@guusw merge this?


enable eslint in amqp-common

This will run the eslint against amqp-common package
This uses the central .eslintrc.json config file for eslint rules
This will generate eslint reports for each package in our CI pipelines and will not fail the builds on linting issues
@Azure/azure-sdk-eng @ramya-rao-a @bterlson

/azp run azure-sdk-for-js - client


Fix docs

Looks like commands and options have be changed a bit.
Also, mongo storage seems to be no longer available out of the box.

Thx


Enable go modules

Go modules are becoming a de-facto standard in the Go community and adding go.mod files with metadata helps projects which may consume this repository as a dependency in deciding how to pin transitive dependencies and how to resolve conflicts.
This is a result of the following commands:
go mod init
go get ./...
go mod tidy

in a clean Go 1.11.5 environment.

Thank you!


[GLUTEN-946] Upgrade arrow version to 10.0.1

What changes were proposed in this pull request?
Current arrow version of 10.0.0-SNAPSHOT does not exist in Maven Central Repository, so upgrade to 10.0.1.
Fix https://github.com/oap-project/gluten/issues/946
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

@leoluan2009 10.0.0-SNAPSHOT is from Gluten's forked Arrow branch https://github.com/oap-project/arrow/tree/backend_velox_main.
It was on the plan to move to 11.0.0 and before that we can just hold off updating a patch version like 10.0.0 -> 10.0.1. Some required changes like this one which landed into 11.0.0 could be necessary if we dropped our forked Arrow repository.

be necessary if we dropped our fo

@zhztheplayer  how much modification we still need to apply to Arrow if we upgrade to Arrow 11? Can we use patch instead of private arrow?

Not much. I would expect no modification is needed from Gluten's code. But that needs a try.

Let's close this one and upgrade to Arrow11


Support "open file in github" in linux

Don't merge yet. We need a aditional config that i don't know how to do it. See: #170 and this

@avelino @lerrua , how to proceed?


Crash on FreeBSD

Hyprland coredumps on FreeBSD 13.2, not displaying any logs or anything. /tmp/hypr doesn't get created either. I only have the coredump file

this is what I got from gdb
(gdb) file /usr/local/bin/Hyprland
Reading symbols from /usr/local/bin/Hyprland...
(No debugging symbols found in /usr/local/bin/Hyprland)
(gdb) core Hyprland.core
[New LWP 100792]
warning: Could not load shared library symbols for [vdso].
Do you need "set solib-search-path" or "set sysroot"?
Core was generated by `Hyprland'.
Program terminated with signal SIGABRT, Aborted.
Sent by thr_kill() from pid 1128 and user 1001.
#0  0x000000082cccbc5a in thr_kill () from /lib/libc.so.7
(gdb) bt
#0  0x000000082cccbc5a in thr_kill () at /lib/libc.so.7
#1  0x000000082cc446d4 in raise () at /lib/libc.so.7
#2  0x000000082ccf5a59 in abort () at /lib/libc.so.7
#3  0x000000082acbce39 in  () at /lib/libcxxrt.so.1
#4  0x00000000002daf05 in main ()

@jbeich this is some bsd voodoo

Likely missing XDG_RUNTIME_DIR. See also downstream notes (more context).
Alternatively, to get a useful backtrace rebuild the port and some of the direct dependencies with WITH_DEBUG=1.

Likely missing XDG_RUNTIME_DIR. See also downstream notes (more context).
Alternatively, to get a useful backtrace rebuild the port and some of the direct dependencies with WITH_DEBUG=1.

My bad for not reading the handbook :p
That did help a bit, but I was getting permission errors for /var/run; mounting it as tmpfs resolved this problem, but now I'm getting this error:
ld-elf.so.1: Shared object "libwayland-server.so.0" not found, required by "Hyprland"
am I missing some dependency?

libwayland-server.so.0 is part of wayland package, already installed by Hyprland. The error is due to missing /var/run/ld-elf.so.hints (generated by ldconfig) when you've mounted tmpfs over /var/run instead of /var/run/user.
Wayland chapter likely has many such inaccuracies. I did help review but writing docs is hard.

libwayland-server.so.0 is part of wayland package, already installed by Hyprland. The error is due to missing /var/run/ld-elf.so.hints (generated by ldconfig) when you've mounted tmpfs over /var/run instead of /var/run/user.
Wayland chapter likely has many such inaccuracies. I did help review but writing docs is hard.

Thank you! I was wondering why I was running in circles there. It works now, though I had to manually create a directory for my UID.

I had to manually create a directory for my UID

Use pam_xdg package to create /var/run/user/<UID> automatically. Alternatively, consolekit2 (elogind ancestor) can do the same and is recommended if something else (KDE, SDDM, etc) already uses it.


Add simple set of captured names to nested ParseNodeFnc

Each ParseNodeFnc has an IdentPtrSet which holds the set of names captured by the function. Captured names are ones which are referenced inside the function but not declared within the function.
Implement this by intercepting name references at PushPidRef and keep the name reference in the set of captured names for the current nested function. Remove any names from the captured name list which do not have dangling references after we've bound the pid ref stack for a nested function. When finished parsing a nested function, add the set of captured names onto the parent functions' captured name set.
Gate the feature via a ParseType flag and allow a forcing config option (CreateParserState).
Example captured name set:
let x, y, z;
function foo() {
  function bar() {
    return x;
  }
  function baz(x) {
    return y;
  }
  function bat() {
    {
      let z;
      return z;
    }
  }
}

// captured name sets
// foo: [x, y]
// bar: [x]
// baz: [y]
// bat: []

I'm curious, how will we use this?

@tcare -- In a couple of ways. It allows us to skip scanning of previously scanned nested deferred functions and maintain correctness of stable closures. It also allows us to limit the work done on undeferral of those functions.

@pleath sounds great :) We could definitely improve some of the readability of the parser by using this too.

@dotnet-bot test OSX static_osx_osx_debug please

@dotnet-bot test OSX static_osx_osx_test please


srcset fix for gifs. waiting for search

some leftover stuff from the larger search pr
@keybase/react-hackers

:mag_right: The commits f1695417ebc3...a4dbf53e552a introduced some visual changes on linux:

Added: Search-Waiting

:mag_right: The commits f1695417ebc3...5be1c07361f6 introduced some visual changes on linux:

Added: Search-Waiting

:mag_right: The commits f1695417ebc3...2bd985cd5456 introduced some visual changes on linux:

Added: Search-Waiting

:mag_right: The commits f0caa342d2e6...378b3f5dc326 introduced some visual changes on linux:

Added: Search-Waiting

:+1:


Provision Spark Master and Slave as a service

The Spark is currently provisioned and started only once and does not start after machine reboot. It will be better to deploy it as a service with automated start.

Solved by #102


write doc about message module

I dont kown why Build check is faild. I didn't change anything else in the code except for the docstring section.

This error is from the latest version of pytest-asyncio extension. I have reduced it to make it run well.

I fetch the latest version from origin master, Build succeed and run well.


Workflow graph disappearing after node deletion

After I delete a single node in my workflow, after refresh sometimes the workflow graph is never rebuilt. The samples and processes still exist.
I'll add more information if I find a pattern for when it does and doesn't happen.
This really hurts my attempts to get data in, because if I make a mistake, sometimes I have to delete the whole experiment and start over.

After more investigation, I think it happens when I attempt to delete a non-leaf node. The operation fails, but I think it puts the whole workflow into an error state.


Document logging options (via DEBUG env var)

When using Prisma Client, you can set different log levels via the DEBUG env var. This needs to be documented. Eg.: DEBUG=prisma-client or DEBUG=*

We use the popular nodejs logging library debug: https://www.npmjs.com/package/debug
Many other packages like express also use the same library. So when you initialize `debug, you give your debugger a namespace like shown below:
const debug = require('debug')('prisma-client')

and it is shown in the debug output when you enable it via the DEBUG environment variable:

So DEBUG=* enables all the debug loggers and DEBUG=prisma-client only enables the debug output for Prisma namespace. The two major namespaces that we use in the client right now are prisma-client and engine so you can only enable debug output from these using DEBUG=prisma-client,engine.
Also, if you want to force the debug output regardless of the DEBUG env, you can pass the debug option in the Prisma client constructor like so new PrismaClient({ __internal: {debug: true}})

Documented via: https://github.com/prisma/prisma2/pull/1801/files


build failed due to metrics test not updated

Failed tests:
  TestMetricsConfig.test:41 expected:<true> but was:<false>

caused by fix of https://github.com/ServiceComb/ServiceComb-Java-Chassis/issues/327

This issue is fixed by
https://github.com/ServiceComb/ServiceComb-Java-Chassis/commit/47414d0a61cbde901168bc79229161bfbbf39e85


Feature Request: Support concurrency in helmfile.yaml

Hey,
There are some setups where we want to override the concurrency setting to 1, and would like to do that declaratively in our helmfile.yaml.
Would that be something you could support?

Actually; i can achieve what I need to do with needs :)


[Storage] Fixed cspell typos in storage-datalake

Description
fix https://github.com/Azure/azure-sdk-for-python/issues/22677
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

No worries, I am happy to contribute 😄


want to add new game

The game wants to add: Drag and Drop Game
This is a game where different colors of cards will appear and we have to drag them and drop them into the similar one.
Kindly assign this issue to me under GSSOC'23.

Hi @Jranii , I am assigning this issue to you, kindly complete your work within a week. Good luck for your work.

@panwar8279 I want to contribute.Please assign me this issue


Sample Based Robust Control

Resolving https://github.com/aarontrowbridge/QuantumCollocation.jl/issues/89
Preparing the initial structure of the notebook with proper documentation.

Progress Update:

Created Ensemble of Quantum Systems, Sampled Via Normal Distribution
Created UnitarySmoothPulseProblem for each quantum system
Creating Direct Sum Problems from above problems (2), Trying to solve this

In the meantime, I am reading the documentation for add_suffix and learning about how manually recreating the NamedTrajectory container along with 3. Glue the trajectory together with the right dynamics.
Thanks a lot @andgoldschmidt for  https://github.com/aarontrowbridge/QuantumCollocation.jl/issues/89#issuecomment-2143541610! I followed your comments and created the initial notebook. I have incorporated step 1 and step 2 from your comments at the moment to get started.
Kindly please download the notebook and please let me know how I am doing? Thanks!

Progress Update:

Created the Draft for function SampleBasedControlProblem based on the suggested implementation guidelines in step 3 and step 4. I am passing ensemble of quantum systems to this function after sampling.
I have utilized the add_suffix in a way that is used in the UnitaryDirectSumProblem.
I get this error when I try to  solve!: ArgumentError: Provided trajectories must have fixed timesteps. This is because of the way I am merging suffix trajectories using direct_sum. I would be grateful if you have a look at the draft function SampleBasedControlProblem from the notebook!

Anyhow,

Kindly please download the notebook and please let me know how I am doing? Thanks a lot!

In the meantime, I will try to read the UnitaryDirectSumProblem for further clarification.

Progress Update:

Completed step 3: Making the integrators we need for each quantum system in our ensemble using for loop and add_suffix!

What's left is step 2: I did create Named Tragectories for all the quantum systems in the ensemble using add_suffix . But having some trouble in combining them via direct sum and add suffix to get one shared control.

Hi @Fe-r-oz, closing this PR until it is ready to be reviewed by a maintainer. In the meantime, please use the issues page to keep up our discussion!


[Setting] Improve setting UI based on mobile App

Is your feature request related to a problem? Please describe.

The Sync setting UI is the same as that of the mobile app

Hi @gaupoit ,
Setting UI implemented on this ticket, I just screenshot for it:


DNS Lookup

Is your feature request related to a problem? Please describe.
Quite often I want the IP address of a website or I want to know who an IP address belongs to
Describe the solution you'd like
I have written a script that asks if you want to do a DNS forward lookup or reverse lookup. Based on that it will either lookup the IP or the domain connected to the IP
Describe alternatives you've considered
You can use websites to do this but the script is more fun!
Additional context

Happy to work on this if assigned to me.