Kanban board Arrangement

Task distribution and work arrangement:

Project source code.
Kanban board setup.

Authors:

Anwar Hussaini.
Abdelaziz Mahdi.

Hi Team,
Good job so far! 👍🏻
There are some issues that you still need to work on to go to the next project but you are almost there!

Required Changes ♻

[ ] Please add the following card/issue to your kanban board, to match the template kanban given.

Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

[[# STATUS: APPROVED :green_circle: :clap:
Hello TEAM   ,
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:  .
Congratulations! 🎉  Keep up the good work 🥂
HIGHLIGHTS:

[x]  Your repo is professional  😎
[x] Descriptive P.R 💯
[x] Professional Readme file
[x] No linter errors
[x] Kanban Board setup correctly

Now you can merge this branch and move on :1st_place_medal:
Happy Coding cheers 🥇 💯

Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.]]


Added drag and drop libraries

And bade component to be used by asset-admin for its drag and drop file feature.
Please see https://github.com/silverstripe/silverstripe-asset-admin/issues/279 for more details

Tests are green on travis. Not sure why framework isn't up to date.


Discovery component - on by default in 0.72.0?

I don't have Discovery in my config files.

It wasn't in version 0.71.0
Has there been a change? or an error?

I’ve noticed this as well and if I comment out discovery - restart - the hass.io shortcut is gone from the UI and a 404 is thrown if I try and access the store. Uncomment it - restart and its back working again. This never happened in previous versions.

getting netdisco errors - all Discovery items supposedly ignored:
WARNING (Thread-9) [netdisco.ssdp] Error fetching description at 192.168....

Incorrect: Discovery was NOT in my configuration, yet the time stamp on entity_registry.yaml is updated to current time. Also there are netdisco errors in my log file, which relate to items not in my configuration.
To reproduce the issue, simply add something like a google cast, but don't alter any files. It will be discovered - which it shouldn't.


Restart loop detection

If the bot restarts ffrk multiple times in quick succession then it should disable istelf with a fault event notification.
Not sure what the exact criteria should be.  Maybe 10 times in 30 minutes or something like that.

Added in 6.5


Message file should have positional parameter (%1) instead of printf

format string (%s)
Tested by creating custom agent executable that forced failure of winutil.GetProgramDataDir()
Discovered that overall logging worked as planned; however, there was the typo in the message file.

Codecov Report

Merging #2760 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #2760      +/-   ##
=========================================
+ Coverage    57.1%   57.1%   +<.01%
=========================================
  Files         383     383
  Lines       24556   24556
=========================================
+ Hits        14022   14023       +1
  Misses       9610    9610
+ Partials      924     923       -1

Impacted Files
Coverage Δ

pkg/logs/auditor/auditor.go
71.12% <0%> (-0.71%)
:arrow_down:

pkg/logs/input/listener/tailer.go
90% <0%> (+4%)
:arrow_up:


Hotkey for silent aim toggle

Following ceramic420's idea, I think it would be great to add a feature where you can disable or enable the silent aim through a hotkey so that you don't need to open the gui to enable or disable the silent aim.

Yes add an hotkey

added


User specific abapGit settings

The abapGit settings dialog is global and afaik there are no user specific settings at the moment. For us it would make sense to make at least these two properties user specific (Yes, there are colleagues who don't prefer ADT ;-) ).

Maybe we can split the settings page into two sections with global and personal settings? Of course we need a user specific settings persistency first.
Any opinions on this? Or am I missing the obvious and this is already possible?

sounds good to me
There is already a user-specific object which most likely can be used for storing values, check Advanced -> Database Util
class zcl_abapgit_persist_migrate can be used for migration of values


Fix long project names breaking task layout

.
Please remember the Contributing Guidelines :heart:
:star2: What does this PR do?
Fixes #1400

:bug: Recommendations for testing
All changes should be tested across Chrome and Firefox.

Field overflow should be resolved as well now.


Update aka.ms links to point to Engineering Hub

Update the following links to point to the appropriate page in Engineering Hub. If a relevant page doesn't exist, determine whether the content belongs in Engineering Hub, and if so open a follow-up issue to migrate your content.

If I tagged you incorrectly, or if you're not the owner of the aka.ms link, please help us and tag the correct owner :) You can find a link owner by using the aka.ms hub.

aka.ms links to update

[x] https://aka.ms/azsdk/onboard @ladonnaq
[ ] https://aka.ms/azsdk/engage @ladonnaq
[ ] https://aka.ms/azsdk/apex/launch-criteria @ladonnaq
[ ] https://aka.ms/azsdk/APEX/exception @ladonnaq
[ ] https://aka.ms/azsdk/APIreadiness @ladonnaq
[ ] https://aka.ms/azsdk/onboarding/APEX/privatepreview/APIreadinessLC @ladonnaq
[ ] https://aka.ms/azsdk/APEX/GA/management-SDK-release-readiness @ladonnaq
[ ] https://aka.ms/azsdk/apex/publicpreview/dataplane/requirements @ladonnaq
[ ] https://aka.ms/azsdk/onboard/office-hours @ladonnaq
[x] https://aka.ms/azsdk/onboarding/informational @ladonnaq
[ ] https://aka.ms/azsdk/onboarding/dpinfomeeting @ladonnaq
[x] https://aka.ms/azsdk/onboarding/restapischedule @mikekistler
[x] https://aka.ms/azsdk/onboarding/archboardschedule @ronniegeraghty
[x] https://aka.ms/azsdk/releases/partnerinfo @ladonnaq
[ ] https://aka.ms/azsdk/release-checklist @czubair
[ ] https://aka.ms/azsdk/publishsdk
[ ] https://aka.ms/azsdk/mark-release-status @czubair

@ladonnaq We still have several aka.ms links that haven't been updated. Can you update so that they point to Engineering Hub? (Conversation in Teams meeting)

@maririos I will either delete or update any aka links that I own in Jan 2024.

@ladonnaq could you update when is the ETA for this work?

@ladonnaq could you update when is the ETA for this work?

I am just getting around to looking at the docs GitHub issues.  I will take care of either updating aka links or deleting if we no longer need them.

@maririos - 2 links remaining but the docs pages are still in Azure Devops. I was not sure if there was a reason they needed to stay in Azur Devops. So wanted to confirm before I created PRs to start a draft to move them to engineering hub.

[ ] https://aka.ms/azsdk/publishsdk (owner is laurent and adpleads. docs page in Azure Devops, should it be moved to engineering hub?)
[ ] https://aka.ms/azsdk/mark-release-status @czubair (Docs page in Azure Devops, should it be moved to engineering hub?)

@maririos - 2 links remaining but the docs pages are still in Azure Devops. I was not sure if there was a reason they needed to stay in Azur Devops. So wanted to confirm before I created PRs to start a draft to move them to engineering hub.

[ ]  https://aka.ms/azsdk/publishsdk (owner is laurent and adpleads. docs page in Azure Devops, should it be moved to engineering hub?)
[ ]  https://aka.ms/azsdk/mark-release-status @czubair (Docs page in Azure Devops, should it be moved to engineering hub?)

Nevermind I found the GitHub issues.  https://github.com/Azure/azure-sdk-tools/issues/7037 and https://github.com/Azure/azure-sdk-tools/issues/7036.

Thank you @ladonnaq :) I also added the specific link to update in the respective issues. We can close this!!!

Thanks @maririos!


IT-4019: Fix bucket name, remove obsolete ones

This PR removes the deploy permissions to *.accounts.sagebionetworks.org and fixes the one for dev.accounts.synapse.org.

Oops, meant https://sagebionetworks.jira.com/browse/IT-4019 . I changed the title.


release v3.3.0

v3.3.0
This release of reaction-identity is designed to work with v3.x of the Reaction API.
Chores

chore(deps): Bump bcrypt from 3.0.7 to 5.0.0 (#37)
chore(deps): Bump node-fetch from 2.6.0 to 2.6.1 (#41)
chore(deps): Bump bl from 2.2.0 to 2.2.1 (#40)
chore: update to Meteor 1.11.1 (#42)

Contributors
Thanks to @loan-laux for contributing to this release! 🎉

@focusaurus @manueldelreal mostly small version bumps. bcrypt is a big jump, but no breaking changes as far as they have documented.


Question about unit exposure loss

Hi, could you please explain the unit exposure loss in the paper?
In the paper, eq(8) says "C = g(ln(e) + ln(t))" and eq(12) says "Lu = l2(g(0) -C0)"
When ln(e) + ln(t) == 0, both e and t are 1. If this is the case, should we calculate C0 to be the average pixel value when t == 1ms?

Hi, this loss is meticulously designed to align the CRF curves across all three channels when e=1 and t=1, thereby regulating the white balance effectively. For a more comprehensive understanding, kindly refer to Sections 2.1 and 2.6 of this paper https://www.pauldebevec.com/Research/HDR/debevec-siggraph97.pdf.

Thanks so much!


[Bug]: After backup, how to restore data to another milvus?

Current Behavior
After backing up data, I cannot restore it to another milvus. When I connect to another milvus, the backup is not displayed.
Expected Behavior
No response
Steps To Reproduce
No response
Environment
No response
Anything else?
No response

The current test result is that it is possible to import the milvus backup into the original milvus. I don't know how to import it into another milvus.

@neblen You should move the backup data from source milvus's storage to target milvus's storage. Change the config according to your target cluster and do restore.


pre-iterate plugins

Description
This a micro-optimization that works by assuming that plugins don't change (and they shouldn't), and it becomes a larger improvement when dealing with greater amount of plugins
Type of change

[x] New feature (non-breaking change which adds functionality)

Test Environment:

OS: Windows 10 & macOS v11.3
@envelop/core: v0.1.4
NodeJS: v14.16.1 & v16.0.0

Checklist:

[x] I have followed the CONTRIBUTING doc and the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented on my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

This is great. Thank you @PabloSzx .
I was thinking about wrapping callbacks functions in a wrapping API, so it will be something like that:
const afterCb = hooks.onParse(parseCbs);

// ...

afterCb();

This way the code will be a bit more clean and without the for loops in the main file - what do you think?

Codecov Report

Merging #167 (45aeed4) into main (56e53eb) will increase coverage by 0.45%.
The diff coverage is 97.46%.

@@            Coverage Diff             @@
##             main     #167      +/-   ##
==========================================
+ Coverage   77.97%   78.42%   +0.45%
==========================================
  Files          24       24
  Lines         572      584      +12
  Branches       98      100       +2
==========================================
+ Hits          446      458      +12
  Misses        126      126

Impacted Files
Coverage Δ

packages/core/src/create.ts
76.44% <97.46%> (+1.44%)
:arrow_up:

Continue to review full report at Codecov.

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


Tool tip on "Send notifications" is that of "Run in background"

Issue

Tool tip on "Send notifications" is that of "Run in background"

Screen recording
https://user-images.githubusercontent.com/49612/182038419-30504ebb-e570-43a3-9879-4b47d17a6723.mov

Well spotted, fixed!


update flet example

fix flet example flet version issue
change some small things to make it easer for others

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Using template subscriptions throws an error in the client when reacting on iron-router

So I am using Template subscription where I am reacting on one of the parameters of the URL and it turns out whenever I then navigate to a page that changes the main template, it throws an error in the client console that reads:
Error: Can't call View#subscribe from inside the destroyed callback, try calling it inside created or rendered.
Example of how I am using it:
Template.myTemplate.onCreated(function() {
    this.autorun(function(c) {
        var myParam = Router.current().params.myParam;
        // some logic to determine what sources to subscribe to
        self.subscribe("mySubscription", options);
    });
});

This issue is related to autorun still executing when 'myTemplate' has been destroyed. This should be done automatically since you are calling this.autorun which is core to meteor and not iron:router. I'd add an onDestroyed method to see what is going on, but you could fix this yourself by calling c.stop() within your autorun function based on the path. Another option would be to simply call stop() on the returned Computation object from this.autorun() within an onDestroyed method.


Enforcing no-merge policy

Whenever rustbot see a merge commit in a PR, it can notify the contributor about no-merge policy.

Maybe resolved by 542f03df57cbaafa1de79e010a8bd723f9960607


Final price functionality to display the discounted price

Hello Dmytro,
There is a default price was listing even if there is a special price is available. The changes contain a functionality that checks the availability of a special price and replaces the price.
Does this close any currently open issues?
Add sales price for products #92

@all-contributors please add @qualwebs to code

thanks, @qualwebs


add link-handling to GPX

The gpx/wpt element has a possible link subelement, which may contain a link to further information.

http://www.topografix.com/GPX/1/1/#type_wptType
http://www.topografix.com/GPX/1/1/#type_linkType

The simpliest form of the elemt seems "<link href='http://some.uri/" />"
If the link-element exists, the href content should be placed as link (with multi-language-text '[...]') to the end of the popup description of the generated marker.
Example: the following tag
<wpt> ...
   <link href="http://more.info/" />
</wpt>

should generate the following at the end of the markups popup text:

[...]

I will suppose a patch for that, soon.    ...    see PR #236

Fixed by #236


style: rename object returned with error

This PR renames Error response object to Failure
The idea is to avoid ambiguous ErrorError in generated client code.
This does not change the JSON format sent between client and server.
cc @aschmahmann @andrew

Linting is failing due to the Error schema no longer existing where previously referenced.

@jacobheun fixed – ok to merge and tag it as v0.1.1 so @andrew and @aschmahmann  can re-generate clients with updated object names?


packaging/CMakeLists.txt:3: Lines should be <= 80 characters long [linelength]

alfredh@debian:~/git/re$ ~/.local/bin/cmakelint packaging/CMakeLists.txt
packaging/CMakeLists.txt:3: Lines should be <= 80 characters long [linelength]
Total Errors: 1

I am wondering why this error it not picked up by cmakelint in .github/workflows ?
proposed fix:
diff --git a/packaging/CMakeLists.txt b/packaging/CMakeLists.txt
index 10eb858..0a402e4 100644
--- a/packaging/CMakeLists.txt
+++ b/packaging/CMakeLists.txt
@@ -1,6 +1,6 @@
 set(CPACK_PACKAGE_NAME libre)
 set(CPACK_PACKAGE_VENDOR baresip)
-set(CPACK_PACKAGE_DESCRIPTION_SUMMARY "Generic library for real-time communications with async IO support")
+set(CPACK_PACKAGE_DESCRIPTION_SUMMARY "Library for Real-Time Communications")
 set(CPACK_PACKAGE_INSTALL_DIRECTORY ${CPACK_PACKAGE_NAME})
 set(CPACK_PACKAGE_VERSION_MAJOR ${PROJECT_VERSION_MAJOR})
 set(CPACK_PACKAGE_VERSION_MINOR ${PROJECT_VERSION_MINOR})

Looks like cmakelint parses only the root CMakeLists.txt, I added a find search. #320

oh, that is nice!
I have one additional question regarding CMake.
For example in retest we have:
##############################################################################
#
# Module/Package Includes
#

find_package(OpenSSL)

would it be possible to add a find_package for re/rem here ?
find_package(libre)

would it be possible to add a find_package for re/rem here ?

Yes that should be possible. I will take a look.


Use pip-compile to lock development dependencies

It's important to have a consistent development environment between developers and CI so that dependency specific issues can be identified.
This is not the same as setting the versions that are used in production, which are still bound by the constraints in setup.py
An alternative would be to use Poetry, which is probably a good idea anyway to be honest as that would bring this project in line with other Kit Team projects. (i.e good for volunteers as we have a more consistent dev experience)

I want to keep the dev install close to the production install so that there is confidence that there will be consistent behaviour.


Inmem mutation API fix to only return ID(string or  []string)

Description of the PR
Fixes #1196
PR Checklist

[ ] All commits have a Developer Certificate of Origin (DCO) -- they are generated using -s flag to git commit.
[ ] All new changes are covered by tests
[ ] If GraphQL schema is changed, make generate has been run
[ ] If collectsub protobuf has been changed, make proto has been run
[ ] All CI checks are passing (tests and formatting)
[ ] All dependent PRs have already been merged

Looks like there's some merge editor artifacts still around, could you help resolve them? Thanks @arorasoham9 !


[red-knot] cleanup doc comments and attributes

Make cargo doc -p red_knot_python_semantic --document-private-items run warning-free. I'd still like to do this for all of ruff and start enforcing it in CI (https://github.com/astral-sh/ruff/issues/12372) but haven't gotten to it yet. But in the meantime I'm trying to maintain it for at least red_knot_python_semantic, as it helps to ensure our doc comments stay up to date.
A few of the comments I just removed or shortened, as their continued relevance wasn't clear to me; please object in review if you think some of them are important to keep!
Also remove a no-longer-needed allow attribute.
(This is just a collection of cleanups I made in passing while working on type narrowing; splitting them out to reduce the size of that PR.)

You could consider adding cargo doc -p red_knot_python_semantic --document-private-items to the CI step to prevent new regressions.


workspace crate source hashes are different between nix 2.3 and later versions

crate2nix generates things like these in Cargo.nix:
      "tsu-mini-std" = rec {
        crateName = "tsu-mini-std";
        version = "0.1.0";
        edition = "2021";
        # We can't filter paths with references in Nix 2.4
        # See https://github.com/NixOS/nix/issues/5410
        src = if (lib.versionOlder builtins.nixVersion "2.4pre20211007")
          then lib.cleanSourceWith { filter = sourceFilter;  src = ../tsu-mini-std; }
          else ../tsu-mini-std;
        dependencies = [
          {
            name = "fxhash";
            packageId = "fxhash";
          }
        ];

      };

On nix 2.3.x and presumably older, this crate ends up depending on its sources (obviously) like so:
[nix-develop]$ nix-store -q -R /nix/store/4y4rb2x1w2ypj5zz1685nhpvhkwwmfhn-rust_tsu-mini-std-0.1.0.drv | tail -n 3
/nix/store/a87gw94pj9l5z1zr4b4bd6hxrcj6y1dg-source
/nix/store/7hvhcn49lynz15s267phv4ph5g2yy7ms-rust_tsu-mini-std-0.1.0.drv
/nix/store/4y4rb2x1w2ypj5zz1685nhpvhkwwmfhn-rust_tsu-mini-std-0.1.0.drv

On modern nix (I'm using 2.9 pre), it looks like this:
[nix-develop]$ nix-store -q -R /nix/store/68cjkl39fdqf49nmym9d0h1ml44bf9r2-rust_tsu-mini-std-0.1.0.drv | tail -n 3
/nix/store/4i4av9wvdx6djid9phrwqp2vnc2r69pr-tsu-mini-std
/nix/store/giw1vm6k33vv2fc2gg7qlq0sg6wshqx9-rust_tsu-mini-std-0.1.0.drv
/nix/store/68cjkl39fdqf49nmym9d0h1ml44bf9r2-rust_tsu-mini-std-0.1.0.drv

The content of /nix/store/a87gw94pj9l5z1zr4b4bd6hxrcj6y1dg-source and /nix/store/4i4av9wvdx6djid9phrwqp2vnc2r69pr-tsu-mini-std is identical! The only thing that's different is the name which changes the hash which then changes hash of everything upstream. I guess since nix 2.4, the ../path syntax gets a proper name as path: lib.cleanSourceWith uses this name if present. I guess on nix 2.3 the name is missing so the "source" default gets used. I was unable to locate the exact commit which caused the change as there are a lot of these between 2.3.16 and 2.4 though it doesn't matter much anyway.
One very simple thing we can do to make the hashes identical again is this:
diff --git a/nix/Cargo.nix b/nix/Cargo.nix
index df38fa2af..795b88012 100644
--- a/nix/Cargo.nix
+++ b/nix/Cargo.nix
@@ -24352,7 +24352,7 @@ rec {
         # We can't filter paths with references in Nix 2.4
         # See https://github.com/NixOS/nix/issues/5410
         src = if (lib.versionOlder builtins.nixVersion "2.4pre20211007")
-          then lib.cleanSourceWith { filter = sourceFilter;  src = ../tsu-mini-std; }
+          then lib.cleanSourceWith { filter = sourceFilter;  src = ../tsu-mini-std; name = "tsu-mini-std"; }
           else ../tsu-mini-std;
         dependencies = [
           {

This makes the source be /nix/store/4i4av9wvdx6djid9phrwqp2vnc2r69pr-tsu-mini-std even on nix 2.3 and everything is happy: binary caching keeps working for people on 2.3 and 2.9 all the same.
I guess then maybe crate2nix should unconditionally (or based on command line flag) insert this attribute with the crate name? This gives consistent results across more versions which seems nice/desirable.

Probably something like this enough, but as per #224 I don't really know how to update the tests etc...
diff --git a/crate2nix/templates/Cargo.nix.tera b/crate2nix/templates/Cargo.nix.tera
index 64f8403..73da725 100644
--- a/crate2nix/templates/Cargo.nix.tera
+++ b/crate2nix/templates/Cargo.nix.tera
@@ -125,7 +125,7 @@ rec {
         # We can't filter paths with references in Nix 2.4
         # See https://github.com/NixOS/nix/issues/5410
         src = if (lib.versionOlder builtins.nixVersion "2.4pre20211007")
-          then lib.cleanSourceWith { filter = sourceFilter;  src = {{crate.source.LocalDirectory.path | safe}}; }
+          then lib.cleanSourceWith { filter = sourceFilter;  src = {{crate.source.LocalDirectory.path | safe}}; name = {{crate.crate_name}}; }
           else {{crate.source.LocalDirectory.path | safe}};
         {%- elif crate.source.Git %}
         workspace_member = null;

I guess we don't want crate name but the dir name of the source... whichever, should be easy

I found even more problems with this nix 2.3 codepath: for example, it'll remove .gitignore from the workspace crates while later versions will not: this is due to current sourceFilter behaviour...
Rather than trying to keep fixing it, I'm just adding an assert in our codebase that >= 2.4 is used. So I no longer really care about this ticket either.


Handle SFPlan deletion for single cluster

Pull Request Test Coverage Report for Build 6052

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.01%) to 87.78%

Files with Coverage Reduction
New Missed Lines
%

broker/core/utils/src/commonFunctions.js
1
86.47%

Totals

Change from base Build 6051:
-0.01%

Covered Lines:
9756

Relevant Lines:
10721

💛  - Coveralls

Validation on k8s cluster: n-1 is succeeded.

Validation on k8s cluster: n is succeeded.

Validation on k8s cluster: n-2 is succeeded.

Validation on k8s cluster: n+n+n is succeeded.

Validation on k8s cluster: n is succeeded.

Validation on k8s cluster: n-1 is succeeded.

Validation on k8s cluster: n-2 is succeeded.

Validation on k8s cluster: n is succeeded.

Validation on k8s cluster: n-1 is succeeded.


Gson and jackson

There is a note in the build file that we should pick one instead of using both. I would like to offer a third alternative: neither. Kotlin's native JSON serialization tooling is pretty good, and it would probably be simplest to just use that. Also removes two more dependencies. Thoughts @vitorpamplona ?

We should use whichever is faster while using fewer resources (memory/CPU). The app is parsing 1000 jsons a second, so every millisecond counts.

We need to make sure escaping follows what other Nostr clients are signing otherwise the parse, format functions break the hash check.

I think it'll be worth trying. Gson uses reflection and is generally slower. Kotlinx serialization is the fastest when it comes to working with strings, usually. I'll make a branch for testing, anyway. Not hard to swap things over.

Keep in mind we are bypassing reflection with our own deserializers.

@vitorpamplona I have kotlinx.serialization working on a branch at least for the events (replaced gson so far, did not do jackson yet).
Would be great if you could do whatever benchmarks you like. Seems to work alright, everything looks normal in the app, but testing is not extensive so kind of hard to say for sure. One test currently broken, not sure why.
https://github.com/maxmoney21m/amethyst/tree/test/json-serializer

hum... this one we should really be sure it's better before merging. We might do a benchmark module for the app. We can download a good number of events (say... export from somebody's use/profile into a file) and use those as benchmark, measuring time, memory and energy used.

This leads me to want to separate the .services.model package into it's own library and stress test the hell out of it.

We have settled with Jackson. It's still the fastest and less memory-consuming option to parse the JSON.


Buffer() Deprecation Warning, when installing a  extension manually on code insiders

VSCode Version:1.53.0-insider (user setup)
OS Version:Windows_NT x64 10.0.19042
Commit: b99487f4168ba70369edfb8629303be0d3979d4b

Steps to Reproduce:

Get .vsix file from store, I used https://marketplace.visualstudio.com/items?itemName=MS-CEINTL.vscode-language-pack-de , since VSCode can't auto update this right now.
Manually install the extension via code-insiders --install-extension MS-CEINTL.vscode-language-pack-de-1.53.1.vsix

Result:
code-insiders --install-extension MS-CEINTL.vscode-language-pack-de-1.53.1.vsix

Installing extensions...
(node:24484) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
Extension 'MS-CEINTL.vscode-language-pack-de-1.53.1.vsix' was successfully installed.

Does this issue occur when all extensions are disabled?: Yes
with disabled extensions:
code-insiders  --disable-extensions --install-extension MS-CEINTL.vscode-language-pack-de-1.53.1.vsix
Installing extensions...
(node:15644) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
Extension 'MS-CEINTL.vscode-language-pack-de-1.53.1.vsix' was successfully installed.

/duplicate
#82524


Permission denied to access property "apply"

Has been fixed before here https://github.com/bugsnag/bugsnag-js/issues/608
Describe the bug
In our production environment, we have error reports:

Permission denied to access property "apply"

Line: if (typeof prevOnError === 'function') prevOnError.apply(this, arguments);
Source<EMAIL_ADDRESS>Environment

Bugsnag version: 7.1.0
Browser framework version (if any):

React: 16.12.0

Browser version (e.g. chrome, safari): Firefox 102-106.0.0
Device (e.g. iphonex):

Linux
WIndows 10

Hi @bhmeister - would you mind updating to the latest version of bugsnag-js to see if this helps resolve the issue please? The latest version is https://github.com/bugsnag/bugsnag-js/releases/tag/v7.18.2.
If the issue persists after updating we can investigate this further - it would be handy if you can share a full stacktrace/reproduction steps at that stage too please 👍

I can say that it's still happening in 7.18.0. Don't know how to reproduce. Only additional info I can provide is that a few milliseconds before this bug gets recorded there are breadcrumbs such as these:
errorClass: Error
errorMessage: too much recursion
severity: error

errorClass: Error
errorMessage: ResizeObserver loop completed with undelivered notifications.
severity: error

Not sure if this is related or where this is coming from. It could be on our own end but then I'm not sure how it would influence bugsnag. Maybe it's a browser thing (only Firefox affected)...
So far it appears though that the volume has gone down since updating to 7.18.0.

Hi @bhmeister,
Thanks for the update. Without a reproduction case for us to work with its going to be difficult for us to continue investigating this. I presume this error does not appear in the Bugsnag dashboard? How often is this occurring? Perhaps you could share your Bugsnag configuration code along with any callbacks you are implementing? Are you doing anything non standard in its or your project setup?

Without a reproduction case for us to work with its going to be difficult for us to continue investigating this.

Understandable.

I presume this error does not appear in the Bugsnag dashboard?

It does.

How often is this occurring?

150 all-time events in a 5 month window. Active user base is around 100k. Only 10 users are affected though. So I'm going to assume the problem is on their end. I can not share any more details on configuration. We're doing nothing out of the ordinary.
Happy to close this, thanks.

Hi @bhmeister - if you're able to write into<EMAIL_ADDRESS>with a link to these errors in your Bugsnag dashboard, we can investigate this further from there 👍

Going to close this out. Do let us know if you are able to reproduce this reliably and we can reopen


Automate does not export tags with client runs

Automate does not export tags with client runs
Automate can show tags while on the web gui's Client Runs page but doing the following:
- Select a node that has been tagged
- Navigate to Attributes
- Find tags array and expand it
- Tag will show in array as expected
However if the Client Runs data is exported to json by  clicking the Download JSON link, the same node will now not have any elements in the tags array within the json. The tags array still shows but is always null and will look like this.
"tags": null

To Reproduce
Steps to reproduce the behavior:
- Navigate to the web gui's Client Runs page
- Click the download button
- Click Download JSON
- Open the json and locate the tags for a node which has a tag defined as found in the web gui the method outlined above.
- Despite having tags in the web gui, the tags array will be null like so: "tags": null
- If the tag is searched for. It will not be found any where else in the exported json.
Expected behavior
Tags which are on the gui should show somewhere inside the exported json data, preferably in the tags array.
Versions (please complete the following information):

OS: macOS
Browser: chrome
Automate Build Number<PHONE_NUMBER>0747

Additional context
I have also exported the client run data via a curl using an API as documented. I found that this downloads the exact same json (no deltas) so it doesn't seem to be an issue with the way the web gui or browser downloads the file.

Thank you for submitting this bug!
I will try to reproduce it in the dev environment and get back to you.  I hope it is an easy fix.

I am seeing the same problem locally. I will see if it is an easy fix.

@tommybonobo turns out there was an easy fix for the problem! https://github.com/chef/automate/pull/1578.
Thank you again for submitting the bug.


As the user, I can sync my timetable to my own personal calendar so that I can refer to my schedule.

Hmm instead of sync with our own calendar, i think export is better since we are using javafx and java


Ingress controller does not work out of the box when installing the Helm chart and configuring AMBASSADOR_ID

Describe the bug
I encountered some problems while trying to get Emissary-ingress to act as an Ingress controller after installing Emissary-ingress using the Helm chart and configuring AMBASSADOR_ID:

Helm - generated IngressClass is missing the required getambassador.io/ambassador-id annotation
If AMBASSADOR_ID is set then the annotation getambassador.io/ambassador-id should be included in the IngressClass generated by the Helm chart, otherwise the IngressClass will be ignored (source).
Fixed by #5221

Helm - misleading option to specify IngressClass controller value
The chart IngressClass template was added in https://github.com/emissary-ingress/emissary/issues/3975 (PR). Although a part of the suggested solution was to specify the controller class (default is getambassador.io/ingress-controller), the solution only touched the IngressClass and not other references; this means that Emissary-ingress still requires the controller value to be getambassador.io/ingress-controller, so it makes sense to remove the option to configure this value from the chart as changing it would not work.
Not really important, can be ignored.

Emissary-ingress - Ingress controller - it should be unnecessary to specify ambassador-id on both Ingress and IngressClass
If AMBASSADOR_ID is set, there's currently a requirement that the getambassador.io/ambassador-id annotation must be set on both the Ingress and the IngressClass (if used instead of the deprecated kubernetes.io/ingress.class annotation). Setting the annotation on either Ingress or the assigned IngressClass should be sufficient.

To Reproduce
Steps to reproduce the behavior:
(I can't remember if it was necessary to restart Emissary-ingress pods after changing Ingress and/or IngressClass in the steps below)

Install Emissary-ingress using the Helm chart and specify AMBASSADOR_ID (in my case I have two installations in the same namespace, one for internal traffic and the other for public-facing services)
Set up an Ingress and assign the generated IngressClass to spec.ingressClassName (don't add the getambassador.io/ambassador-id annotation yet)
If the generated IngressClass has the getambassador.io/ambassador-id annotation then the expected behavior is that the Ingress is handled, but the Ingress is not handled by Emissary-ingress in this case (Ingress controller requires the annotation on both Ingress and IngressClass)
Add the getambassador.io/ambassador-id annotation to the Ingress
Observe that the Ingress is still not handled by Emissary-ingress unless you also have the annotation on the IngressClass
Add the getambassador.io/ambassador-id annotation to the IngressClass and observe that Emissary-ingress now picks up the Ingress

Expected behavior
The Ingress should be handled by Emissary-ingress at step 3 (with annotation on IngressClass but not on Ingress) and after step 4 (with annotation on Ingress and with or without the annotation on IngressClass).
Versions (please complete the following information):

Emissary: 3.3.0
Helm chart v8.3.0
Kubernetes environment: kOps
Version: k8s v1.23

Additional context
Documentation might also need an update, but since that's a different repository I'll provide a separate PR for that.

I'm experiencing this exact problem - it'd be very nice for spec.ingressClassName to work as expected here - it's what basically every helm chart in existence has hooks into for ingress

I've opened a new PR #5221 to fix the missing getambassador.io/ambassador-id annotation for the generated IngressClass.
Note that the docs for Ingress controller is a bit out of date/confusing.

You must create your Ingress resource with the correct ingress.class.
Emissary-ingress will automatically read Ingress resources with the annotation kubernetes.io/ingress.class: ambassador.

Kubernetes 1.18 introduced the IngressClass resource to the existing networking.k8s.io/v1beta1 API.

The ingress.class annotation has been deprecated for a while, 1.18 was EOL 2 years ago, so I think it would be better to provide docs using spec.ingressClassName instead.
For an Ingress to be controlled by Emissary Ingress it needs spec.ingressClassName, and if you're setting AMBASSADOR_ID the annotation getambassador.io/ambassador-id. It's possible to set the IngressClass generated by Emissary Ingress as cluster default so you won't have to add this to each of your Ingresses, but you'll need to add the getambassador.io/ambassador-id annotation on the Ingress anyway, at least for now.
In my original PR I wanted to remove the need for the annotation on the Ingress, since we can get it from the IngressClass, but I wasn't able to get it to work. Ideally that would also be fixed.

I've scratched out point 1 and 2 from the issue description as 1 has been fixed and 2 isn't very important, leaving just point 3, remove requirement to have AMBASSADOR_ID annotation on both IngressClass and Ingress as long as it's present on one of them.


Set ingest processor supports copying from one field to another

Description
When using template snippets like {}, the rendered result is always string, not the original field type, in order to implement copying from one field to another, this PR adds a new parameter named copy_from for set processor which can be set to one of the field in the incoming document, and the value of that field will be copied deeply and assigned to the specified field.
copy_from and value are mutually exclusive, either of them can be set.
Related Issues
https://github.com/opensearch-project/OpenSearch/issues/10134
Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff
[x] Commit changes are listed out in CHANGELOG.md file (See: Changelog)
[x] Public documentation issue/PR created

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

The failed test is a flaky test, there's an issue tracking it.

Flaky test : https://github.com/opensearch-project/OpenSearch/issues/2775.

@gaobinlong I restarted gradle check and checked the boxes in the description for you, but please do go through the checklist

@dblock thanks, now all checks have passed yet, could you help to review this PR?

Not very familiar with this part of the code, maybe another maintainer can take a look?

Could anyone help to review this PR? It's been opened for months.

Why we are not introducing dedicated CopyProcessor (or CopyFromProcessor)?

While I get that the set processor is often used for "simple" copying cases (e.g. as a way of "flattening" an input document), I'm inclined to agree with @reta that this behavior is distinct enough that it probably warrants its own processor.
As a bonus, since you know that the source is definitely going to be another field, you could (for example) add a remove_original parameter to the new processor to let it behave like a "field move", rather than a field copy.

Why we are not introducing dedicated CopyProcessor (or CopyFromProcessor)?

While I get that the set processor is often used for "simple" copying cases (e.g. as a way of "flattening" an input document), I'm inclined to agree with @reta that this behavior is distinct enough that it probably warrants its own processor.
As a bonus, since you know that the source is definitely going to be another field, you could (for example) add a remove_original parameter to the new processor to let it behave like a "field move", rather than a field copy.

OK, implementing a new processor makes things simpler, and will not confuse users, I'll open another PR to implement CopyProcessor, thanks!

Close this PR because https://github.com/opensearch-project/OpenSearch/pull/11870 has been merged.


Change particle attributes only responds when window is resized

I'm using particles.js as a background. When a button is clicked, it calls a GSAP timeline, which in turn calls a custom function to change the particles attributes. After clicking the button, the original particles disappear, other elements animate in, but the new particles only appear after resizing the window (opening chrome dev tools or actually resizing the nav window). Anybody have any issues with this?
Here's the function:
function pJSColorChange() {
window.pJS_GUI = window.pJSDom[0].pJS;
pJS_GUI.particles.number.value = 200;
pJS_GUI.particles.size.value = 14;
pJS_GUI.particles.size.anim.enable = true;
pJS_GUI.particles.size.anim.speed = 30;
pJS_GUI.particles.color.value = "#c5b358";
}

I do it like this:

pJSDom[0].pJS.particles.color.value = "#433e3e";
pJSDom[0].pJS.fn.particlesRefresh()


field code completion for buffer handle references

In OEDT, you can add an annotation to the source
@Table(name="hBuffer", table="Customer).
That allows OEDT then to provide code-completion after
hBuffer::
for field names of the Customer table.
Very useful in cases, where you're certain about the actual table used in a buffer handle or to access common fields.

I assume that the name attribute is there because method / function parameters can't be annotated ?

I guess so


Support HTTP POST/PUT JSON schema

Resolution to: https://github.com/apache/incubator-pinot/issues/4603
Sample usage:
curl -X POST --header 'Content-Type: application/json'  -d '{
"schemaName": "transcript",
"dimensionFieldSpecs": [
{
"name": "studentID",
"dataType": "STRING"
},
{
"name": "firstName",
"dataType": "STRING"
},
{
"name": "lastName",
"dataType": "STRING"
},
{
"name": "gender",
"dataType": "STRING"
},
{
"name": "subject",
"dataType": "STRING"
}
],
"metricFieldSpecs": [
{
"name": "score",
"dataType": "FLOAT"
}
]
}' 'http://localhost:9000/schemas/validate'

Codecov Report

Merging #4639 into master will decrease coverage by 0.02%.
The diff coverage is 33.33%.

@@             Coverage Diff              @@
##             master    #4639      +/-   ##
============================================
- Coverage     64.49%   64.47%   -0.03%
  Complexity       32       32
============================================
  Files          1076     1076
  Lines         56068    56190     +122
  Branches       8184     8203      +19
============================================
+ Hits          36162    36226      +64
- Misses        17239    17301      +62
+ Partials       2667     2663       -4

Impacted Files
Coverage Δ
Complexity Δ

...ller/api/resources/PinotSchemaRestletResource.java
39.18% <33.33%> (-1.4%)
0 <0> (ø)

...a/manager/realtime/RealtimeSegmentDataManager.java
50% <0%> (-25%)
0% <0%> (ø)

...pinot/server/realtime/ControllerLeaderLocator.java
68.65% <0%> (-24.12%)
0% <0%> (ø)

...altime/ServerSegmentCompletionProtocolHandler.java
35.11% <0%> (-15.27%)
0% <0%> (ø)

...e/pinot/common/utils/FileUploadDownloadClient.java
71.68% <0%> (-6.63%)
0% <0%> (ø)

...ot/common/protocols/SegmentCompletionProtocol.java
87.28% <0%> (-5.21%)
0% <0%> (ø)

...apache/pinot/controller/LeadControllerManager.java
70.13% <0%> (-3.82%)
0% <0%> (ø)

...pinot/core/operator/docidsets/OrBlockDocIdSet.java
84.9% <0%> (-3.78%)
0% <0%> (ø)

...e/operator/dociditerators/MVScanDocIdIterator.java
57.14% <0%> (-3.18%)
0% <0%> (ø)

...er/api/resources/LLCSegmentCompletionHandlers.java
32.24% <0%> (-2.86%)
0% <0%> (ø)

... and 29 more

Continue to review full report at Codecov.

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


Fleshed out the benchmarks section of the README.md file

Flesh out the benchmarks section of the README.md file by adding more metrics and performance test results.
Thank you

I don't think it would hurt comparing this framework with other popular python frameworks of which Django leads the pack. It will give them a reason to want to switch. Also ASGI branch of this repo is giving me some errors whenever I try to run it. Waiting for Kenneth to answer my questions about this so I can proceed on further benchmark tests.
Thank you

To consider: we’ll want to run multi-process, which we can easily do but isn’t happening out of the box just yet. (I’ll get it sorted next week)
Run against master. ASGI support is in.

Will do asap


GraphIQL + Express "endpointURL" not working to connect to Apache+PHP webserver

I want to use GraphIQL (nodejs) to connect to a PHP server (Apache + PHP) with a /graphql endpoint. Below is the code fragment I am trying, using "endpointURL" to point to the Apache web server on port 80. The problem is the Apache logs do not show any HTTP requests coming from nodejs (direct requests to Apache using CURL etc work and print Apache log messages).

var express          = require('express');
var graphiqlExpress  = require('graphql-server-express').graphiqlExpress;

var url = 'http://<IP_ADDRESS>/graphql';

var app = express();
app.use('/', graphiqlExpress({
  endpointURL: url,
}));

app.listen(4000);

Accessing http://<IP_ADDRESS>:4000/ brings up the GraphIQL UI. Accessing http://<IP_ADDRESS>/graphql brings up the endpoint, with a HTTP request appearing in the Apache log file. But trying to run any GraphIQL query shows no HTTP request arriving in the Apache log file plus I get the message "TypeError: Failed to fetch". I assume this means it is not fetching the schema etc from the "endpointURL" being provided.
I found https://stackoverflow.com/questions/40451636/inspecting-a-remote-graphql-endpoint-with-graphiql, but "endpointURL" seems to be an easier way. Am I using endpointURL correctly? What is the easiest way to use GraphIQL with a remote server? Thank you!

Note: I found "endpointURL" mentioned on pages such as https://libraries.io/github/polacekpavel/graphqlworkshop.
And the following seems to work. Just not sure if this is the "right" way to do it.
// Run GraphIQL (the GraphQL IDE) on port 4000

var express          = require('express');
var graphiqlExpress  = require('graphql-server-express').graphiqlExpress;
var buildClientSchema  = require('graphql/utilities').buildClientSchema;
var introspectionQuery = require('graphql/utilities').introspectionQuery;
var request            = require('sync-request');

var url = 'http://<IP_ADDRESS>/graphql';

var response = request('POST', url, { qs: { query: introspectionQuery } });
// Assuming we're waiting for the above request to finish (await maybe)
var introspectionResult = JSON.parse(response.body.toString('utf-8'));
var schema = buildClientSchema(introspectionResult);

var app = express();
app.use('/', graphiqlExpress({
  schema: schema
}));

app.listen(4000);

I am going to close this - I did not realize at the time GraphIQL is available as a Chrome app on their store. That was trivial to get up and going and avoids this whole issue.


Update README.md with link to XojoToAppImage project

Added XojoToAppImage tool link to the compiled applications section of the README document.
Project found here: XojoToAppImage

Reminds me that I had dabbled in REALbasic in the late 90s 👍

It's been fun working with in 2024, they recently went free for Linux people too. Thanks for the merge!


feat: detailed product page

Related Issue
Closes: #701
Changes made 👷🏻♂
Hi @tamalCodes I have tried to show data of a single product. So Right now data is getting render from database but I saw data on every other page is statically render, so only if you have data on you database with the slug same as in your static data.js file then only can see result.
Note : You can try to store data with 'pr1' slug in your db.
I tried to get data from db, because in one of your response on the issue was "It make no sense if data is not rendered dynamically."
But if you want I can change to static.
Screenshots  📸

@JatinBhargava , please fill up the Pull request template in a detailed manner.

@JatinBhargava , can you show me a screen cast where the data is rendered dynamically for separate products ?


No option to focus on a transactional Modal

Detailed description

Describe in detail the issue you're having.

There is no property to focus on an element in a Modal.

Is this a feature request (new component, new icon), a bug, or a general issue?

Feature request

Is this issue related to a specific component?

Modal

What did you expect to happen? What happened instead? What would you like to see changed?

I expected the first element (TextInput, Dropdown, etc) in the Modal to be focused when opening, or the primary button to be focused if there are no other elements inside the Modal.

What browser are you working in?

Chrome version 65

What version of the Carbon Design System are you using?

Latest

What offering/product do you work on? Any pressing ship or release dates we should be aware of?

IBM Cloud Account. No pressing release dates.
Steps to reproduce the issue

Find an org in a Bluemix account, go to the overflow menu and click rename
In this case, the TextInput should have focus.
For a case without TextInput or other elements, go to the Remove Domain modal under Domains > click the overflow menu > Remove from Org
In this case, the Remove button (primary button) should have focus.
Additional information

I currently have a workaround solution in place locally, and as such would be willing to make the necessary changes on Carbon instead.

Hi @akim316 seems that you got a great point! And we are welcome for contribution - It'd be great if the first focusable element can be made configurable (like what the vanilla version does) if you want to got forward with the implementation. Thanks!


how to use claude 3.5 sonnet as out of the box as possible?

(this issue is partly a testing ground for an ai tool)
@ellipsis-dev please add to the README how to use claude 3.5 sonnet with leancopilot on a mac (over cloud).

Thank you @alok , is the test done yet? Also curious what is the outcome :)
By the way, if there is really a demand to use any new external model with LeanCopilot by its API, the easiest approach should be to follow a similar pipeline as PR #97 to use Lean Copilot's external model support feature.

Apparently a repo owner has to invoke the bot, though i'd be happy to pay the $20 to try it for a month for the repo. The annoying thing about #97 is needing to run the python server, which is not quite out of the box.


Feature: Project standards

Summary
This branch creates a GitHub action to run some CMD checks on the R code.
Check

[ ] The checks pass.
[ ] The R CMD badge is added to the README.md.

Note
Currently failing because the DESCRIPTION file is not in this branch but in #4 .

@martinctc Could you help me add the R CMD check badge back into the README.md, please?


There are no test manifests for edge-installer and tar-installer

The format request map doesn't specify these image types, thus test manifest cannot be generated for these image types.
cc @achilleas-k

An edge installer test manifest requires pulling an edge commit to put into the ISO as payload.  We could have a test override for it (like we do for ostree parameters) just to be able to generate a test manifest to run through the pipeline generator and detect changes.  I think we discussed it (very briefly) with @teg when the installer was first introduced and we decided it's not necessary (at least then).
For the tar-installer we should probably add one.  I'm working on some tests (and fixes) for that now so I'll include it in the changes.

Test manifest for tar-installer added in #1524


Training Time

Thank you for your team's work. It may be because the issue from transfuser repository mentioned that the model only needs to be trained for 1 day with 8 2080ti, so I thought that the training of transfuser++ with little architectural change would only take about the same time, but when I use an a100(40G) to train the NC model, it seems that it takes 6 days. I want to know the specific training time of transfuser++,  it doesn’t seem to be mentioned in the paper.

As discussed in section 3.4 in the paper, TransFuser++ uses 6x larger training budget than TransFuser (2x due to 2 stage training and 3x due to using 3x more data).
An additional compute increase that might be not quite as apparent is that we use the larger camera image from the TCP paper. This increases forward and backward time in the CNN for both the reproduced TransFuser and TransFuser++ (compared to the old repository).
Don't remember exactly how long it took to train TF++ but something on the order of 3 days on 4x A100 (40G), so your training time on 1 A100 seems reasonable assuming you are training in the scaled setting.

That makes sense, thank you again


Microsoft Debugger Engine plugin skeleton implementation

I'd like to continue this work directly in master.

nice!


Field Variable support in Word document

Hi  developers!  does the current library support domain variable manipulation on Word?
Like the code in the Microsoft.Office.Interop.Word library, for example:
ApplicationClass WordApplication = new ApplicationClass();
object paramMissing = Type.Missing;
object openfileName = Path.Combine(Directory.GetCurrentDirectory(), "1.docx");

Document WordDocument = WordApplication.Documents.Open(openfileName);
WordDocument.Variables["cnname"].Value = "My Custom Variable!!!!!";
WordDocument.Fields.Update();
 WordDocument.Save();
WordDocument.Close();
WordApplication.Quit();
```.cs

field variable looks to be a advanced feature in Word. I'm not sure what's your purpose. If you use it to replace texts, you can take a look at this example.

very happy to receive your reply, I just want to simply use domain variables to achieve certain functions. The way to replace characters has some limitations, so I would like to ask whether NPOI currently supports this function. If not, will it be supported in the future?

I'm not so familiar with this field variable function. If it's VBA feature, I'm afraid NPOI will not support that because NPOI doesn't have any VBA runtime simulator.

你这个功能后来实现了吗？


[stable/openvpn] Mitigate SWEET32 OpenVPN vulnerability by using more secure cipher.

In order to migitgate SWEET32 vulnerability in OpenVPN, configure the server and the clients to use AES-256-CBC cipher instead of the default BF-CBC cipher.
For more info see https://community.openvpn.net/openvpn/wiki/SWEET32

@joe1chen - Thanks for this.  Please sign the linux foundation agreement so we can test and merge.

Please fix CLA within one week.

Closing as stale. Feel free to reopen if/when you decide to work on this again.


[BEAM-11589] Migrated root build.gradle file to Kotlin script.

Migrated root build.gradle file to Kotlin script.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @TheNeuralBit


Code cleanup & perf gains

tl;dr I changed some words leading to 38 methods being deleted

Changed visibility of many variables/methods to protected to reduce
synthetic method generation
Reduced redundant method calls
Changed extended for loops to normal for loops
Initialized size of some arraylists to minimize amount of
reallocating needed to add new elements
Added double-checking for singletons

Impact of the resulting changes:
Before:

After:

Done.


Can't use photo callback without cameraFragmentResultListener

Looking at the code you need to callsetResultListener even if you pass in a callback into takePhotoOrCaptureVideo in order to get the callback called.

"bien vu !"  it's fixed, I made some other fixes and will publish again


⚠ Bofrost.hr has degraded performance

In bb7efd0, Bofrost.hr (https://www.bofrost.hr) experienced degraded performance:

HTTP code: 200
Response time: 2635 ms

Resolved: Bofrost.hr performance has improved in 7c78f62.


Add character limit to TextArea on Note add/edit window prompt

Added character limit when typing notes. Currently set to 150 max.
Improved data validation for note add and note edit commands.

Resolves #227

Coverage decreased (-0.3%) to 56.202% when pulling f3978841c0c8829c0038dafa4400a1a27ff94cdd on jomcruz93:add-character-limit-text-area into 1f66994b79d9158994bfb53939d3dc12ed80c2c5 on CS2113-AY1819S1-T16-1:master.


Improve text-opacity

Clear and concise description of the problem
text-opacity-{x} is a Windi rule that introduces an extra variable to control text opacity.
This variable could enable us to control text opacity separately from color, which would be useful, but implementation is lacking. We can only use this variable as an alternate syntax for Tailwind text-{color}/{opacity}:

Windi, uses variable

Tailwind, single class, doesn't require variable

Separation of color and opacity is quite interesting if we could change them separately. For example reduce opacity to de-emphasize some text while preserving the current color.

  Useful idea: dim text.
  This is NOT 50%.

  Less useful, but also an idea.
  This is NOT 50% either.

Intuitively you could expect these to work, but neither does. Let's see why.
First the generated CSS:
.text-red {
  --un-text-opacity: 1;
  color: rgb(248 113 113 / var(--un-text-opacity));
}

.text-opacity-50 {
  --un-text-opacity: 0.5;
}

The outer text-opacity does not apply to inner text-red, because text-red resets --un-text-opacity to 1.
I don't think this is a very useful use-case, so for compatibility purposes I'd say we could keep it unchanged.
The other scenario is useful and the reason why it doesn't work is subtle:
CSS properties inherit their computed value, not their source expression!
So the span.text-opacity-50 inherits the computed color: rgb(248 113 113 / 1). It does not have a dependency on any variable and changing --un-text-opacity at this level has no effect.
Setting both rules on the same element only works because text-opacity-50 is declared after text-red in CSS stylesheet, so it's declaration of --un-text-opacity "wins". Using both class on the same element seems a little wasteful when we can use a single class, constant text-red/50.
Suggested solution
I tweaked the rules as follow:
/* Variant 1: full support for independent opacity control top-down and bottom-up */

.text-red {
  /* removed: --un-text-opacity: 1 */
  --un-color:  rgb(248 113 113); /* added */
  color: rgb(248 113 133 / var(--un-text-opacity));
}

.text-red/50 {
  --un-color:  rgb(248 113 113); /* added as well, to be able to use /opacity syntax and still tweak color inside */
  color:  rgb(248 113 113 / 0.5);
}

.text-opacity-50 {
  --un-text-opacity: 0.5;
  color: rgb(from var(--un-color) r g b / 0.5); /* added, force re-computing the color */
}

/* Variant 2: text-red resets opacity to 1 for back-compat, so controlling opacity higher up in DOM is not possible */

.text-red {
  /* removed: --un-text-opacity: 1 */
  --un-color:  rgb(248 113 113); /* added */
  color: rgb(248 113 133); /* removed / var(--un-text-opacity) */
}

.text-red/50 {
  --un-color:  rgb(248 113 113); /* added */
  color:  rgb(248 113 113 / 0.5);
}

.text-opacity-50 {
  color: rgb(from var(--un-color) r g b / 0.5); /* added */
}

Removing --un-text-opacity from text-red enables top-down cascade of opacity.
As I said it's not the most useful use case so might be kept in if we want to minimize breakage.
Notice that if we keep this backward compatible behavior, --un-text-opacity is not necessary at all and can be dropped. When both text-red text-opacity-50 are declared on the same element, the new color rule of the later takes over (as it's declared after text-red, same reasoning as previously).
Introducing a new variable --un-color to text-color rules lets us re-compute the color property in child elements that use text-opacity, enabling opacity to affect colors picked higher up.
Alternative
If you want to be able to dim elements by reducing their opacity, while keeping any current color, I don't see any other way to achieve this.
You might think that this style could be a cheap solution: rgb(from currentColor r g b / 0.5).
It's actually valid CSS that works when assigned to any property... except color.
The problem is that using currentColor inside color property creates a circular reference that doesn't work :(
Additional context
Other rules work identically, in particular bg-red and bg-opacity-50.
I'd say they would benefit from the same change.
It also opens up new uses cases, for example I'd love being able to darken a background when mouse is pressed (e.g. on a button, or a clickable items).
If there was a variable --un-bg-color then I could create a rule active:bg-darken-10.
Validations

[X] Read the Contributing Guidelines.
[X] Read the README.md of using the package.
[X] Already used the Interactive Docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

You can already kind of do this using the direct children selector, the text inside the div need to be in actual elements though like p or span. They also need to be direct children.
play


[Sema] Disregard reference storage types when inferring associated types from witnesses.

Resolves SR-6097.

@swift-ci Please smoke test and merge


Ayden new silver supporter

Added Ayden to the silver sponsors section - resolves https://github.com/techqueria/website/issues/822
Deploy preview: https://deploy-preview-834--techqueria.netlify.app/supporters/

✅ By submitting this PR, I have verified the following

[x] Checked to see if a similar PR has already been opened 🤔

[x] Reviewed the contributing guidelines 🔍

[ ] Added my name to the bottom of the list under the Contributors section in the README.md with a link to my personal website or GitHub profile 👥 (Optional)

Adding this here so it can be seen in the list of issues that there is a pull request for this one. Resolves #822

Adding this here so it can be seen in the list of issues that there is a pull request for this one. Resolves #822

@all-contributors please add @michellbrito for adding silver sponsor

@all-contributors please add @michellbrito for adding silver sponsor

@all-contributors please add @michellbrito for maintenance

@all-contributors please add @michellbrito for maintenance

lgtm

lgtm


Migrate to FlashList

Apparently users have reported crashes while scrolling through waves too fast, my guess is there is a performance bottleneck because of processing renderHTMLs in a long list of waves.
As suggested by @gamingumar, we can migrate FlatList to FlashList as a quick remedy to improve performance, later we can also consider optimising item renderer

[x] First Migrate CommentsView.tsx, that component is also used to render waves
[x] Migrate postComments.tsx, this component renders comment made to a post in post details screen
[x] Migrate PostsListContainer.tsx, use to render post feeds

https://github.com/ecency/ecency-mobile/pull/2771


TreeShaking not working in webpack 4.5.0

Bug report
Just tried the tree shaking feature but it looks not working, checkout code here: https://github.com/galenyuan/tree-shake
What is the current behavior?
when I try to import { moduleA } from './test-module/esm', cli told me [only some exports used: moduleA] but nothing changed in bundle file.

and when I try to import { moduleA } from 'test-module/esm', cli told me nothing and same bundle file in dist.js
If the current behavior is a bug, please provide the steps to reproduce.
https://github.com/galenyuan/tree-shake
npm install
npm start

What is the expected behavior?
should have /* unused harmony export _functionname_ */ comment in bundle file

Other relevant information:
webpack version: 4.5.0
Node.js version: 8.11.2
Operating System: macOS
Additional tools: -

This is working as expected. A minimizer is now able to remove moduleB via DCE. Enable minimizing to see the effect.


[Blazor] Unhandled exception. System.ArgumentException: Comments cannot be stored in a JsonDocument

Describe the bug
I using the latest SDK (3.0.100-preview7-012627) and created a simple Blazor Server-Side App with
dotnet new blazorserverside, build it and run it and then I get this error:
Unhandled exception. System.ArgumentException: Comments cannot be stored in a JsonDocument, only the Skip and Disallow comment handling modes are supported. (Parameter 'readerOptions')
   at Microsoft.Extensions.Configuration.FileConfigurationProvider.HandleException(Exception e)
   at Microsoft.Extensions.Configuration.FileConfigurationProvider.Load(Boolean reload)
   at Microsoft.Extensions.Configuration.FileConfigurationProvider.Load()
   at Microsoft.Extensions.Configuration.ConfigurationRoot..ctor(IList`1 providers)
   at Microsoft.Extensions.Configuration.ConfigurationBuilder.Build()
   at Microsoft.Extensions.Hosting.HostBuilder.BuildAppConfiguration()
   at Microsoft.Extensions.Hosting.HostBuilder.Build()
   at BlazorServerSideApp1.Program.Main(String[] args) in D:\Workspaces\_playground\Blazor\BlazorServerSideApp1\Program.cs:line 18

Program.cs Line 18:

To Reproduce
Steps to reproduce the behavior:

create a new Blazor Server-Side app with dotnet new blazorserverside -n {nameOfProject}
run dotnet build
run dotnet run
See error

Expected behavior
Kestrel should run without any error.
Additional context
dotnet --info:
.NET Core SDK (reflecting any global.json):
 Version:   3.0.100-preview7-012627
 Commit:    86a2e1fec8

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.18362
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\3.0.100-preview7-012627\

Host (useful for support):
  Version: 3.0.0-preview7-27826-01
  Commit:  d41f5ea7cc

.NET Core SDKs installed:
  2.1.700 [C:\Program Files\dotnet\sdk]
  2.1.800-preview-009696 [C:\Program Files\dotnet\sdk]
  2.2.300 [C:\Program Files\dotnet\sdk]
  3.0.100-preview7-012627 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.0.0-preview7.19325.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.0.0-preview7-27826-01 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.0.0-preview7-27826-01 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

cc @BrennanConroy

There are a couple breaking changes in corefx that we haven't consumed yet, and as a result weird things like this happen.
We'll be consuming the corefx changes later today and hopefully by tomorrow there will be a new sdk that works.

SDK 3.0.100-preview7-012687 is working so far. Thanks!


kubernetes: 1.10.5 -> 1.11.3

Motivation for this change
Since https://github.com/NixOS/nixpkgs/pull/45670 will not make it to 18.09, I'm PR'ing the kubernetes package separately. I'd like it if this could be backported to NixOS 18.09.
Even though this PR has no module updates, the main purpose of issue #43882 was to upgrade to v1.11, thus:
closes #43882
@srhb ping
Things done
NixOS tests for rbac and dns runs clean.
I've also tested this with a three node cluster in Google Cloud and it turns out that the existing kubernetes module works seamlessly with the 1.11.3 package, although some of the k8s components yield warnings for deprecated flags.

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[X] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Fits CONTRIBUTING.md.

Success on aarch64-linux (full log)
Attempted: kubernetes
Partial log (click to expand)
strip is /nix/store/y4ymnvgxygpq05h03kyzbj572zmh6zla-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/q17786b5b5zfbvrmxf7jmiy55xy8rifn-kubernetes-1.11.3-man
checking for references to /build in /nix/store/q17786b5b5zfbvrmxf7jmiy55xy8rifn-kubernetes-1.11.3-man...
shrinking RPATHs of ELF executables and libraries in /nix/store/cqqs70riij9k63pklbq8a5i2f1abjlc7-kubernetes-1.11.3-pause
shrinking /nix/store/cqqs70riij9k63pklbq8a5i2f1abjlc7-kubernetes-1.11.3-pause/bin/pause
strip is /nix/store/y4ymnvgxygpq05h03kyzbj572zmh6zla-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/cqqs70riij9k63pklbq8a5i2f1abjlc7-kubernetes-1.11.3-pause/bin
patching script interpreter paths in /nix/store/cqqs70riij9k63pklbq8a5i2f1abjlc7-kubernetes-1.11.3-pause
checking for references to /build in /nix/store/cqqs70riij9k63pklbq8a5i2f1abjlc7-kubernetes-1.11.3-pause...
/nix/store/fn5liqgvy3yjq77jksp2y8ajanqclnyc-kubernetes-1.11.3

Success on x86_64-linux (full log)
Attempted: kubernetes
Partial log (click to expand)
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/465g2lxzl9asczpbl3k6fgmrqqnawhds-kubernetes-1.11.3-man
checking for references to /build in /nix/store/465g2lxzl9asczpbl3k6fgmrqqnawhds-kubernetes-1.11.3-man...
shrinking RPATHs of ELF executables and libraries in /nix/store/9rg029r9aqgzj4ciggqhcy5xsj87zb6f-kubernetes-1.11.3-pause
shrinking /nix/store/9rg029r9aqgzj4ciggqhcy5xsj87zb6f-kubernetes-1.11.3-pause/bin/pause
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/9rg029r9aqgzj4ciggqhcy5xsj87zb6f-kubernetes-1.11.3-pause/bin
patching script interpreter paths in /nix/store/9rg029r9aqgzj4ciggqhcy5xsj87zb6f-kubernetes-1.11.3-pause
checking for references to /build in /nix/store/9rg029r9aqgzj4ciggqhcy5xsj87zb6f-kubernetes-1.11.3-pause...
/nix/store/bzcvswk3asyf91a2rdqldx3mdihy7kgv-kubernetes-1.11.3

@GrahamcOfBorg test kubernetes.rbac.singlenode kubernetes.dns.singlenode kubernetes.rbac.multinode kubernetes.dns.multinode

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: tests.kubernetes.rbac.singlenode, tests.kubernetes.dns.singlenode, tests.kubernetes.rbac.multinode, tests.kubernetes.dns.multinode
Partial log (click to expand)

Cannot nix-instantiate `tests.kubernetes.dns.singlenode' because:
error: attribute 'singlenode' in selection path 'tests.kubernetes.dns.singlenode' not found

Cannot nix-instantiate `tests.kubernetes.rbac.multinode' because:
error: attribute 'multinode' in selection path 'tests.kubernetes.rbac.multinode' not found

Cannot nix-instantiate `tests.kubernetes.dns.multinode' because:
error: attribute 'multinode' in selection path 'tests.kubernetes.dns.multinode' not found

Success on x86_64-linux (full log)
Attempted: tests.kubernetes.rbac.singlenode, tests.kubernetes.dns.singlenode, tests.kubernetes.rbac.multinode, tests.kubernetes.dns.multinode
Partial log (click to expand)
machine1: exit status 0
test script finished in 83.14s
cleaning up
killing machine1 (pid 597)
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: Could not remove ctl dir '/build/vde1.ctl': Directory not empty
/nix/store/np2c4zfrrhrjg4772arh5dbjpjc3g3iv-vm-test-run-kubernetes-rbac-singlenode
/nix/store/99nncfp5nq5jlgp77dlzi57930j00df4-vm-test-run-kubernetes-dns-singlenode
/nix/store/47iax0npzcxjizirmzcsrciryjkvyx1y-vm-test-run-kubernetes-rbac-multinode
/nix/store/96h5fg49s29wpwkw5qpxh76bz8hhm9lk-vm-test-run-kubernetes-dns-multinode


inheritance + nested_attributes + strong_params

I have the following code skeleton where a Column embeds_many Contents of types Image and Map:
class Column
  include Mongoid::Document

  embeds_many: contents
  accepts_nested_attributes_for :contents, allow_destroy: true
end

class content
  include Mongoid::Document

  field :description
end

class Image < Content
  field :src, type: String
end

class Map < Content
  field :latitude, type: String
  field :longitude, type: String
end

Now I want to pass a JSON from my view to the columns_controller to create a column with two contents; image and map.
I attempted passing the following hash:
{'column' => 'contents_attributes' => [{_type: 'Image', description: 'image description', src: 'path/to/image'}, {_type: 'Map', description: 'map description', latitude: '25.3321', longitude: '35.32423'}]}

the column_params method is:

def column_params
  params.require(:column).permit(:_id, contents_attributes: [:_id, :_type, :description, :src, :latitude, :longitude])
end

The above raised the following error:
Attempted to set a value for '_type' which is not allowed on the model Content.

and if I manually add the _type field to the Content class, it also raise while permitting the subclasses' attributes

as a workaround in the file lib/mongoid/relations/builders/nested_attributes/many.rb I changed the creation of the object in the method process_attributes at line 109 to be
klass = attrs[:_type].try(:constantize) || metadata.klass
existing.push(Factory.build(klass, attrs)) unless destroyable?(attrs)

instead of
existing.push(Factory.build(metadata.klass, attrs)) unless destroyable?(attrs)

and this solved my problem.


Fix three typos in the TruePrims algorithm

Eliminated the miss-spelled totalVisted - it is never read.
Corrected the '==' (compare) to '=' (assign) when deriving passage costs.

Thanks for spotting the typos. I am keeping in totalVisited because I think it is useful for the user to be able to access it.


Support docker

This is very ambitious for me now. But I would like to have a try. I need much help from online resources now.

Currently, this is not a challenge. What matters is the situation of using this.

For years, the situation has become rather different. So docker is not intended for this package.


Can't get the background color in neovim terminal emulator

From the documentation, we know that neovim embeds a VT220/xterm terminal emulator based on libvterm.
But, termbg currently can't get background color in neovim terminal emulator.
Environment:

Neovim version: v0.5.0-dev

Reproduce step:

Open neovim without config file: nvim -u NONE
Open terminal in neovim via :terminal
Run cargo run in nvim terminal emulator

The output is:
Check terminal background color
  Term : XtermCompatible
  Color: detection failed Timeout { source: Timeout }
  Theme: detection failed Timeout { source: Timeout }

libvterm may not support to query background color through OSC 11.
I tried like below, but no response.
$ printf "\x1b]11;?\x1b\\"

If libvterm doesn't support the query, termbg can't get background color.

I tried to run neovim built with DEBUG=1, and got below:
libvterm: Unhandled OSC 11;?

This shows libvterm doesn't support OSC 11 query yet.


checklist ignores model update when value is array or object

Bug Report
The following field (without a validator) cannot be updated via the model. No errors or warnings are logged:
{ "label":"ANR",
  "model":"or.anr",
  "type":"checklist",
  "listBox":true,
  "values": [
      {"name":"a", "value":[1,2]},
      {"name":"b", "value":[2,2]}
   ] }

model.or.anr = [[1,2]]; // fails to check "a"

If you would like a jsfiddle demo, let me know.
Docs do not say that name/value checklist items cannot handle array/object values.
Suggested fix: store the schema's name/value objects in the model's values array, and locate them by name using findIndex(function(i){ return i.name === theName }).

Version: 2.2.0
Browser: FF 59 (latest)
Language: Firefox default JS

I'd like to claim this

I'd like to claim this


Can't import the 'Battery Healthy' dashboard on Grafana

Hello,
This is a great project. But I have a issue.

When importing the dashboard by importing jason, the following error occurs: Import failed: JSON -> JS Serialization failed: Unexpected token '<',"<!DOCTYPE"…is not valid JASON
Importing the dashboard by pasting the raw code is successful, but all the section of the dashboard displays "No data", and an error is displayed in the upper left corner of each section: db query error:xx:invalid input syntax for type Jason

Anyone can help me to fix it.

Hi,
Could you confirm, in order to have context, what Kind of installation of TeslaMate are you using? (docker/standalone).
It's strange about the option 1, I guess you download the file locally and import as file. Option 2 should be the same, because is the same file. So, if it loads from RAW, it should work, unless you are using an instance of Grafana which data source is not TeslaMate (postgressql database).
Can you confirm that you are having this issue only with the Battery health dashboard or it's the same behaviour with the other ones?

Thanks for your reply.
I installed Teslamate on my NAS using docker-compose. It is installed according to the official instructions. Here is the link
https://docs.teslamate.org/docs/installation/docker/
As you said， I downloaded the file ‘BatteryHealth.json' locally and imported it as a file for option 1. Is this incorrect?
To clarify, the default dashboards work well. Here are the pictures.

Hello, it's so strange.  The other thing I was wondering is if you have tried to import other dashboards to see if the same thing happens to you. Let me know.
About the Battery Health, on the screen that you show I see something curious and that is that it has read the current soc at the bottom. But not the rest. Could you go to the setting of the dashboard and see if the variables are getting values? Is the right DataSource selected?


0.5.2: sphinx 4.0.3 warnings

During build are emmited warning like below:
+ /usr/bin/python3 setup.py build '--executable=/usr/bin/python3 -s'
running build
running build_py

><EMAIL_ADDRESS>preinstall /home/tkloczko/rpmbuild/BUILD/sphinx_rtd_theme-0.5.2
> bin/preinstall.js

><EMAIL_ADDRESS>install /home/tkloczko/rpmbuild/BUILD/sphinx_rtd_theme-0.5.2/node_modules/node-sass
> node scripts/install.js

Cached binary found at /home/tkloczko/.npm/node-sass/4.14.1/linux-x64-83_binding.node

><EMAIL_ADDRESS>postinstall /home/tkloczko/rpmbuild/BUILD/sphinx_rtd_theme-0.5.2/node_modules/node-sass
> node scripts/build.js

Binary found at /home/tkloczko/rpmbuild/BUILD/sphinx_rtd_theme-0.5.2/node_modules/node-sass/vendor/linux-x64-83/binding.node
Testing binary
Binary is fine
npm WARN<EMAIL_ADDRESS>No repository field.
npm WARN<EMAIL_ADDRESS>No license field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 896 packages from 501 contributors and audited 967 packages in 11.177s

26 packages are looking for funding
  run `npm fund` for details

found 477 vulnerabilities (381 low, 64 moderate, 32 high)
  run `npm audit fix` to fix them, or `npm audit` for details
WARNING: [Bourbon] [Deprecation] `box-sizing` is deprecated and will be removed in 5.0.0. We suggest using an automated prefixing tool, like Autoprefixer.
         on line 10 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate`
         from line 17 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate-for-prefixing`
         from line 422 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecated-upcoming.scss, in mixin `box-sizing`
         from line 16 of node_modules/wyrm/sass/wyrm_core/_reset.sass
         from line 25 of stdin

WARNING: [Bourbon] [Deprecation] `transition` is deprecated and will be removed in 5.0.0. We suggest using an automated prefixing tool, like Autoprefixer.
         on line 10 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate`
         from line 17 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate-for-prefixing`
         from line 7 of node_modules/bourbon/app/assets/stylesheets/css3/_transition.scss, in mixin `transition`
         from line 31 of node_modules/wyrm/sass/wyrm_core/_font_icon_defaults.sass
         from line 32 of stdin

WARNING: [Bourbon] [Deprecation] `transition` is deprecated and will be removed in 5.0.0. We suggest using an automated prefixing tool, like Autoprefixer.
         on line 10 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate`
         from line 17 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate-for-prefixing`
         from line 7 of node_modules/bourbon/app/assets/stylesheets/css3/_transition.scss, in mixin `transition`
         from line 102 of node_modules/wyrm/sass/wyrm_core/_alert.sass
         from line 35 of stdin

WARNING: [Bourbon] [Deprecation] `user-select` is deprecated and will be removed in 5.0.0. We suggest using an automated prefixing tool, like Autoprefixer.
         on line 10 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate`
         from line 17 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate-for-prefixing`
         from line 2 of node_modules/bourbon/app/assets/stylesheets/css3/_user-select.scss, in mixin `user-select`
         from line 67 of node_modules/wyrm/sass/wyrm_core/_button.sass
         from line 36 of stdin

WARNING: [Bourbon] [Deprecation] `transition` is deprecated and will be removed in 5.0.0. We suggest using an automated prefixing tool, like Autoprefixer.
         on line 10 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate`
         from line 17 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate-for-prefixing`
         from line 7 of node_modules/bourbon/app/assets/stylesheets/css3/_transition.scss, in mixin `transition`
         from line 69 of node_modules/wyrm/sass/wyrm_core/_button.sass
         from line 36 of stdin

WARNING: [Bourbon] [Deprecation] `transition` is deprecated and will be removed in 5.0.0. We suggest using an automated prefixing tool, like Autoprefixer.
         on line 10 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate`
         from line 17 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate-for-prefixing`
         from line 7 of node_modules/bourbon/app/assets/stylesheets/css3/_transition.scss, in mixin `transition`
         from line 227 of node_modules/wyrm/sass/wyrm_core/_form.sass
         from line 38 of stdin

WARNING: [Bourbon] [Deprecation] `box-sizing` is deprecated and will be removed in 5.0.0. We suggest using an automated prefixing tool, like Autoprefixer.
         on line 10 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate`
         from line 17 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate-for-prefixing`
         from line 422 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecated-upcoming.scss, in mixin `box-sizing`
         from line 234 of node_modules/wyrm/sass/wyrm_core/_form.sass
         from line 38 of stdin

WARNING: [Bourbon] [Deprecation] `box-sizing` is deprecated and will be removed in 5.0.0. We suggest using an automated prefixing tool, like Autoprefixer.
         on line 10 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate`
         from line 17 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate-for-prefixing`
         from line 422 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecated-upcoming.scss, in mixin `box-sizing`
         from line 240 of node_modules/wyrm/sass/wyrm_core/_form.sass
         from line 38 of stdin

WARNING: [Bourbon] [Deprecation] `transition` is deprecated and will be removed in 5.0.0. We suggest using an automated prefixing tool, like Autoprefixer.
         on line 10 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate`
         from line 17 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate-for-prefixing`
         from line 7 of node_modules/bourbon/app/assets/stylesheets/css3/_transition.scss, in mixin `transition`
         from line 283 of node_modules/wyrm/sass/wyrm_core/_form.sass
         from line 38 of stdin

WARNING: [Bourbon] [Deprecation] `transition` is deprecated and will be removed in 5.0.0. We suggest using an automated prefixing tool, like Autoprefixer.
         on line 10 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate`
         from line 17 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate-for-prefixing`
         from line 7 of node_modules/bourbon/app/assets/stylesheets/css3/_transition.scss, in mixin `transition`
         from line 383 of node_modules/wyrm/sass/wyrm_core/_form.sass
         from line 38 of stdin

WARNING: [Bourbon] [Deprecation] `transition` is deprecated and will be removed in 5.0.0. We suggest using an automated prefixing tool, like Autoprefixer.
         on line 10 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate`
         from line 17 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate-for-prefixing`
         from line 7 of node_modules/bourbon/app/assets/stylesheets/css3/_transition.scss, in mixin `transition`
         from line 394 of node_modules/wyrm/sass/wyrm_core/_form.sass
         from line 38 of stdin

WARNING: [Bourbon] [Deprecation] `transform` is deprecated and will be removed in 5.0.0. We suggest using an automated prefixing tool, like Autoprefixer.
         on line 10 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate`
         from line 17 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate-for-prefixing`
         from line 2 of node_modules/bourbon/app/assets/stylesheets/css3/_transform.scss, in mixin `transform`
         from line 493 of node_modules/wyrm/sass/wyrm_core/_form.sass
         from line 38 of stdin

WARNING: [Bourbon] [Deprecation] `transform` is deprecated and will be removed in 5.0.0. We suggest using an automated prefixing tool, like Autoprefixer.
         on line 10 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate`
         from line 17 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate-for-prefixing`
         from line 2 of node_modules/bourbon/app/assets/stylesheets/css3/_transform.scss, in mixin `transform`
         from line 495 of node_modules/wyrm/sass/wyrm_core/_form.sass
         from line 38 of stdin

WARNING: [Bourbon] [Deprecation] `transform` is deprecated and will be removed in 5.0.0. We suggest using an automated prefixing tool, like Autoprefixer.
         on line 10 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate`
         from line 17 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate-for-prefixing`
         from line 2 of node_modules/bourbon/app/assets/stylesheets/css3/_transform.scss, in mixin `transform`
         from line 497 of node_modules/wyrm/sass/wyrm_core/_form.sass
         from line 38 of stdin

WARNING: [Bourbon] [Deprecation] `transform` is deprecated and will be removed in 5.0.0. We suggest using an automated prefixing tool, like Autoprefixer.
         on line 10 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate`
         from line 17 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate-for-prefixing`
         from line 2 of node_modules/bourbon/app/assets/stylesheets/css3/_transform.scss, in mixin `transform`
         from line 499 of node_modules/wyrm/sass/wyrm_core/_form.sass
         from line 38 of stdin

WARNING: [Bourbon] [Deprecation] `transform` is deprecated and will be removed in 5.0.0. We suggest using an automated prefixing tool, like Autoprefixer.
         on line 10 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate`
         from line 17 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate-for-prefixing`
         from line 2 of node_modules/bourbon/app/assets/stylesheets/css3/_transform.scss, in mixin `transform`
         from line 501 of node_modules/wyrm/sass/wyrm_core/_form.sass
         from line 38 of stdin

WARNING: [Bourbon] [Deprecation] `transform` is deprecated and will be removed in 5.0.0. We suggest using an automated prefixing tool, like Autoprefixer.
         on line 10 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate`
         from line 17 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate-for-prefixing`
         from line 2 of node_modules/bourbon/app/assets/stylesheets/css3/_transform.scss, in mixin `transform`
         from line 503 of node_modules/wyrm/sass/wyrm_core/_form.sass
         from line 38 of stdin

WARNING: [Bourbon] [Deprecation] `transform` is deprecated and will be removed in 5.0.0. We suggest using an automated prefixing tool, like Autoprefixer.
         on line 10 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate`
         from line 17 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate-for-prefixing`
         from line 2 of node_modules/bourbon/app/assets/stylesheets/css3/_transform.scss, in mixin `transform`
         from line 505 of node_modules/wyrm/sass/wyrm_core/_form.sass
         from line 38 of stdin

WARNING: [Bourbon] [Deprecation] `transition` is deprecated and will be removed in 5.0.0. We suggest using an automated prefixing tool, like Autoprefixer.
         on line 10 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate`
         from line 17 of node_modules/bourbon/app/assets/stylesheets/_bourbon-deprecate.scss, in mixin `-bourbon-deprecate-for-prefixing`
         from line 7 of node_modules/bourbon/app/assets/stylesheets/css3/_transition.scss, in mixin `transition`
         from line 248 of src/sass/_theme_layout.sass
         from line 45 of stdin

Browserslist: caniuse-lite is outdated. Please run the following command: `npm update`
Hash: 2e769a286cbbca41dd0a
Version: webpack 4.41.5
Time: 8540ms
Built at: 07/10/2021 2:35:21 PM

Python Version: 3.8.11
Sphinx Version: 4.0.3
RTD Theme Version: 0.5.2

Additionally during build documentation sphinx shows some other warnings
+ /usr/bin/python3 setup.py build_sphinx -b man --build-dir build/sphinx
running build_sphinx
Running Sphinx v4.0.3
loading translations [en]... done
making output directory... done
loading intersphinx inventory from https://docs.readthedocs.io/en/latest/objects.inv...
loading intersphinx inventory from http://www.sphinx-doc.org/en/stable/objects.inv...
intersphinx inventory has moved: http://www.sphinx-doc.org/en/stable/objects.inv -> https://www.sphinx-doc.org/en/master/objects.inv
building [mo]: targets for 0 po files that are out of date
building [man]: all manpages
updating environment: [new config] 10 added, 0 changed, 0 removed
reading sources... [100%] installing
/home/tkloczko/rpmbuild/BUILD/sphinx_rtd_theme-0.5.2/docs/demo/demo.rst:261: WARNING: Footnote [4] is not referenced.
/home/tkloczko/rpmbuild/BUILD/sphinx_rtd_theme-0.5.2/docs/demo/demo.rst:267: WARNING: Footnote [11] is not referenced.
/home/tkloczko/rpmbuild/BUILD/sphinx_rtd_theme-0.5.2/docs/demo/demo.rst:18: WARNING: Undefined substitution referenced: "problematic".
/home/tkloczko/rpmbuild/BUILD/sphinx_rtd_theme-0.5.2/docs/demo/demo.rst:261: WARNING: Unknown target name: "5".
/home/tkloczko/rpmbuild/BUILD/sphinx_rtd_theme-0.5.2/docs/demo/demo.rst:304: WARNING: Unknown target name: "body elements".
/home/tkloczko/rpmbuild/BUILD/sphinx_rtd_theme-0.5.2/docs/demo/demo.rst:316: WARNING: Unknown target name: "hyperlink reference without a target".
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
writing... python-sphinx_rtd_theme.3 { installing configuring contributing changelog demo/structure demo/demo demo/lists_tables demo/api demo/long } /home/tkloczko/rpmbuild/BUILD/sphinx_rtd_theme-0.5.2/docs/demo/demo.rst:275: WARNING: citation not found: nonexistent
/home/tkloczko/rpmbuild/BUILD/sphinx_rtd_theme-0.5.2/docs/demo/lists_tables.rst:: WARNING: "table cell spanning" not supported
/home/tkloczko/rpmbuild/BUILD/sphinx_rtd_theme-0.5.2/docs/demo/lists_tables.rst:: WARNING: "table row spanning" not supported
/home/tkloczko/rpmbuild/BUILD/sphinx_rtd_theme-0.5.2/docs/demo/lists_tables.rst:: WARNING: "table row spanning" not supported
/home/tkloczko/rpmbuild/BUILD/sphinx_rtd_theme-0.5.2/docs/demo/lists_tables.rst:: WARNING: "table cell spanning" not supported
/home/tkloczko/rpmbuild/BUILD/sphinx_rtd_theme-0.5.2/docs/demo/lists_tables.rst:: WARNING: "table cell spanning" not supported
/home/tkloczko/rpmbuild/BUILD/sphinx_rtd_theme-0.5.2/docs/demo/lists_tables.rst:: WARNING: "table cell spanning" not supported
done
build succeeded, 13 warnings.

Duplicate of #1142


Support SonarQube analysis in the Gradle task.

Hi @HSAR, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

LGTM


chore: add missing copyright header

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (7f21551) to head (58e1a68).
Report is 2 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master      #431   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           42        42
  Lines         3672      3672
=========================================
  Hits          3672      3672

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


fix: get working directory via IOM API

Summary
Fix #1119
Get working directory via IOM API instead of SAS log
Testing
Tested with COM and IOM connections and the result can be fetched correctly.

Update the sasv9.cfg and add -pagesize 15 at C:\Program Files\SASHome\SASFoundation\9.4 to reproduce the issue.
It has no error if trying the same in the PR branch.


fix: sequence+set typing

closes #5

Codecov Report

Merging #6 (2873041) into master (d95d549) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master       #6   +/-   ##
=======================================
  Coverage   97.30%   97.30%
=======================================
  Files          14       14
  Lines         297      297
=======================================
  Hits          289      289
  Misses          8        8

Flag
Coverage Δ

unittests
97.30% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

magic_filter/magic.py
99.34% <100.00%> (ø)

magic_filter/util.py
73.33% <100.00%> (ø)


EKS kubernetes 1.21 actually uses coredns 1.8.4

This is evidenced by this build log in our testing:
msg="Upgrading current deployed
version of coredns
(602401143452.dkr.ecr.us-east-1.amazonaws.com/eks/coredns:v1.8.4-eksbuild.1)
to match expected version
(602401143452.dkr.ecr.us-east-1.amazonaws.com/eks/coredns:v1.8.3-eksbuild.1)."

(Source build: https://app.circleci.com/pipelines/github/gruntwork-io/terraform-aws-service-catalog/4924/workflows/638807f6-71cd-43fc-b1a5-7cda5472b544/jobs/14589/steps)

Thanks for review! Merging now.