[Run, tracker] calculator (mage nuget) having calculation issues

Environment
PowerToys version: 0.18.1
PowerToy module for which you are reporting the bug (if applicable): Power Run

Example 1 : digits after the decimal point
Example: type "123 * 4.56"
Result = 560,8800000000001
Probably an an issue with the signing of the number, since the total amount of digits is 16, or converting binary to decimal. When using one negative number, the result = -560,8800000000001.

Example 2 : no operator
Example: type "123 456"
Result = 56088
No operator is used here. I know that multliplication may be implied between numbers and constants, or between numbers and (other things in) brackets, but not between numbers only. Also, spaces may sometimes be used in big numbers as thousands separators.
Suggestion: Spaces between only numbers should be ignored (like treated as thousands separators). Unless somebody else has a better idea?

Maybe the math code of the open-sourced Windows Calculator could be a good fit here, because it has solved problems like in example 1. It is written in C++, though, and I don't know how much work would be required for using it outside calc.exe.

This is probably gonna sound like a rookie comment, but using open source Windows code that is already out there, sounds pretty obvious to me. Re-inventing things that already have been made in/for a similar situation sounds like a lot of "wasted" time and energy? 🤓

Related to #3488 and #2265

One interesting thing I noticed is that example 1 doesn't happen with more complex calculations (maybe when brackets are involved?)

I gets weird even for simple additions.

More strangeness  when entered 39.9 .... why is it proposing a different number?

Can I ask for an update? Still new issues coming in. What's the plan?

xref https://github.com/microsoft/PowerToys/issues/3764

in calculator plugin, Mages looks like it is doing some type of odd casting.
Works

2+2.1
2+2.1111

Incorrect

2+2.11
2+2.111

var result = MagesEngine.Interpret(query.Search); is what does the calc.

This should be resolved in our 0.21.1 release of PowerToys.  https://github.com/microsoft/PowerToys/releases/tag/v0.21.1 to download it.


Add SAML, Docker docs

Fixes #960
Fixes #959
Fixes #913
Fixes #746
Fixes #794
Fixes firezone/product#483

Pull Request Test Coverage Report for Build 7c4b072885de69f79983191c78bde7ea0bbc67a5-PR-961

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

Totals

Change from base Build aab77656a745fbfcd87936f672d61bd94a876ed8:
0.0%

Covered Lines:
1063

Relevant Lines:
1569

💛  - Coveralls

Merging to stage 0.6.0


Unable to activate after update 1.21 update

On startup I get this error in the debug console:
Activating extension `siegebell.scope-info` failed:  Cannot find module 'c:\Program Files (x86)\Microsoft VS Code\resources\app\node_modules\vscode-textmate\release\main.js'
extensionHostProcess.js:453
Here is the error stack:  Error: Cannot find module 'c:\Program Files (x86)\Microsoft VS Code\resources\app\node_modules\vscode-textmate\release\main.js'
extensionHostProcess.js:453
	at Function.Module._resolveFilename (module.js:470:15)
	at Function.Module._load (module.js:418:25)
	at Function.J.Y.t.getExtensionPathIndex.then.o._load (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:671:784)
	at Module.require (module.js:498:17)
	at Module.patchedRequire [as require] (c:\Program Files (x86)\Microsoft VS Code\resources\app\extensions\git\node_modules\diagnostic-channel\dist\src\patchRequire.js:14:46)
	at require (internal/module.js:20:19)
	at Object.<anonymous> (C:\Users\Mike\.vscode\extensions\siegebell.scope-info-0.2.0\out\src\text-mate.js:3:12)
	at Object.<anonymous> (C:\Users\Mike\.vscode\extensions\siegebell.scope-info-0.2.0\out\src\text-mate.js:22:3)
	at Module._compile (module.js:571:32)
	at Object.Module._extensions..js (module.js:580:10)

From https://github.com/Microsoft/vscode/issues/36997
To make your extension entirely compatible with a distribution of VSCode that uses ASAR, and to make your extension work with both VSCode stable and VSCode insiders, you will need to try to load from two paths... Something like the following:
function getNodeModule(moduleName) {
  try {
    return require(`${vscode.env.appRoot}/node_modules.asar/${moduleName}`);
  } catch(err) { }
  try {
    return require(`${vscode.env.appRoot}/node_modules/${moduleName}`);
  } catch(err) {}
  return null;
}

Oh hey! I was just thinking I would have to abandon this extension and remove the scope feature from prettify-symbols-mode... THANKS!

I was just about to post the same: https://github.com/Microsoft/vscode/issues/46281#issuecomment-376907056

I was in the middle of developing an extension that relied on scope-info when the update happened so I opened an issue here and on vscode.


*: Build APIv2 spec using go-swagger, annotate endpoints

PR: https://github.com/cockroachdb/cockroach/pull/62560
From release notes:

Added documentation for Cluster API v2 endpoints. [#62560][#62560] {% comment %}doc{% endcomment %}

@taroface, not sure if there's anything new here.

This is the work done by @itsbilal to generate the original spec file for the Cluster API. For the v21.1 docs, we used the spec built from this code on master, though this code itself hadn't made it in to 21.1. No action is needed.

Thanks, @mikeCRL. Closing.


Basic framework

New test harness, based on proxyquire/sinon with all logic hidden in a dedicated library
Basic middleware loading logic
100% coverage and JsLint compliant, yay :3

Coverage remained the same at 100.0% when pulling 212d4c70569ac7123ed7aa0b7a2c3e0726d0ae7f on dev into 11f896745cd4ff6952acb24b88a1b69be6bb1b24 on master.


When will the rest of the code be released

Thanks for Jiaman! I have the same question!

Hi,
actually, the other parts of the code are already in the model file, for example, for motion interpolation, there's https://github.com/lijiaman/hm-vae/blob/main/seq_two_hier_sa_vae.py#L1270   currently, this file is kind of redundant, I haven't cleaned it up. will try to clean the code a bit, but if you are looking for the code for interpolation, motion completion, they are already in this file.

OK， thank you!
Jiaman @.***> 于2022年6月30日周四 15:21写道：

Hi,
actually, the other parts of the code are already in the model file, for
example, for motion interpolation, there's
https://github.com/lijiaman/hm-vae/blob/main/seq_two_hier_sa_vae.py#L1270
currently, this file is kind of redundant, I haven't cleaned it up. will
try to clean the code a bit, but if you are looking for the code for
interpolation, motion completion, they are already in this file.
—
Reply to this email directly, view it on GitHub
https://github.com/lijiaman/hm-vae/issues/1#issuecomment-1170860189, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ALL6UZ6AZV5CYMEV5TCGUBLVRVDH7ANCNFSM5Y2J4VKA
.
You are receiving this because you commented.Message ID:
@.***>


How to specify colspan in a row ?

What version of React-Table are you using?
Your bug may already be fixed in the latest release. Run yarn upgrade react-table!
v6.7.6
What bug are you experiencing, or what feature are you proposing?
Unable to specify colspan in a row. Need to specify a colspan of 4 in a 7 column row.
What are the steps to reproduce the issue?
NA

Sorry - you can't. ReactTable is not a "normal" table and has no support for colspan or rowspan.

I was able to get this effect by using the getTdProps prop on the table by passing it this function and hiding the columns that I wanted:
customTdProps = (state, rowInfo, column, instance) => {
let className = 'meeting__td'
const columnsNotHidden = ["col0", "col6", "col7", "col8", "col9" ]
if (rowInfo && rowInfo.original && this.isTopic(rowInfo.original) && columnsNotHidden.indexOf(column.id) === -1 ) {
className = ${className} hide-me;
}
  return {className};

};


It is hard to guess the behavior of the yank subcommand of  the publish command for non-native speakers

The name of the yank subcommand of the publish command is confusing enough for me to make my interface package yanked unintentionally.  The names of commands should be clear so that non-native English speakers can guess their behavior with less effort.
I understand yank means "making it unavailable for use" in this context, but I need 5 English-Japanese dictionaries and 15mins
to find the meaning.

Thanks for pointing this out as confusing. Do you think it should be renamed? Or just requires clearer description and messaging in the CLI?

Thanks for sharing the context.

Do you think it should be renamed? Or just requires clearer description and messaging in the CLI?

I believe the subcommand requires more clearer description in the help messages, at least.
As for the changing name, the following words popped up in my mind:

revoke
disable
drop
deactivate

In #290 PR, added a confirmation message that defaults to no
`Yank` revokes a version, making it unavailable. It is permanent and cannot be reversed.
Yank `{version}` of `{package}`?

Not sure that this fully resolves this issue, but hopefully an improvement.

Another reference: https://pypi.org/help/#yanked


feat: Made the github webhook content_type and insecure_ssl option types vars

Description
Made the github webhook content_type and insecure_ssl option types vars
Motivation and Context

Some environments may need to temporarily set environments up with a self-signed certificate and disabling SSL checks and the content type is a requirement for the github webhook to deliver successfully.
    content_type = var.webhook_content_type
    insecure_ssl = var.webhook_insecure_ssl

Breaking Changes

No
How Has This Been Tested?

[X] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[X] I have tested and validated these changes using one or more of the provided examples/* projects

[X] I have executed pre-commit run -a on my pull request

Pre-commit check validations run prior to PR:
Terraform fmt............................................................Passed
Terraform validate.......................................................Passed
Terraform docs...........................................................Passed
Terraform validate with tflint...........................................Passed
check for merge conflicts................................................Passed

@dynamike thanks for the info. Checked that over, added the changes and pushed them, thanks for that.


FlatOpc: line break at the end of binary part format

Hi, I have a question about the next method:
https://github.com/OfficeDev/Open-XML-SDK/blob/main/src/DocumentFormat.OpenXml/Packaging/OpenXmlPackage.FlatOpc.cs#L140-L159
According to the old blog post from Eric White:

the string must be broken into lines of 76 characters, and there must not be a line break at the beginning or end of the data

But the linked code adds a line break at the end of the data.
Also, the logic of this method is not obvious from my point of view.
If it is a bug then it might be simplified a bit:
const int maxLineLength = 76;

var str = Convert.ToBase64String(byteArray);

var sb = new StringBuilder();
for (var i = 0; i < str.Length; i += maxLineLength)
{
    if (i > 0)
    {
        sb.AppendLine();
    }

    sb.Append(str.Substring(i, System.Math.Min(maxLineLength, str.Length - i)));
}

return sb.ToString();

Hi @f1nzer
      It appeared the code snipped that was attached is working as expected.

       byte[] byte1 = {2, 4, 6, 8, 10,
               12, 14, 16, 18, 20};

        const int maxLineLength = 76;
        var str = Convert.ToBase64String(byte1);

        var sb = new StringBuilder();
        for (var i = 0; i < str.Length; i += maxLineLength)
        {
            if (i > 0)
            {
                sb.AppendLine();
            }

            sb.Append(str.Substring(i, System.Math.Min(maxLineLength, str.Length - i)));
        }

        Console.WriteLine(sb.ToString());

I am getting the following output:
AgQGCAoMDhASFA==
What would be your expectation that code should do?

@hunyu the attached code snippet is what I want to suggest instead of how it is implemented right now.
Please check the link: https://github.com/OfficeDev/Open-XML-SDK/blob/main/src/DocumentFormat.OpenXml/Packaging/OpenXmlPackage.FlatOpc.cs#L140-L159

Hi @f1nzer
I am totally agreed. Code snipped you suggested and provided is much simpler. Once we released Open XML SDK update, I will bring this up to the team and see if we can consider what you suggested. Thank you very much for your time.
Hung-Chun Yu
Microsoft Open Specifications Support.


Explore/document service principal permissions requirements

It is likely that certain deployment patterns will require owner level permissions for deployment.  One option might be to give an SP write permissions on the sub for roles.  This task should look at where owner is required and document the options.
In most enterprise situations, engineers are likely going to have locked down permissions/limited access.

Closing as this appears to be done.

@jmspring


Comment zipper functions. Fix foldr1

foldr1 used foldl1, fixed typo

@kubaracek run elm-format over the code to make CI pass elm-format --yes src

Thanks a lot!


Treat URL references the same way as :doc:

Currently URL reference
`example page <https://example.com>`_.

are converted into "example page" and the URL is neglected. This PR improves on this behavior such that the reference is converted into
"example page" [1]
...

 Referenced URLs:

  1. https://example.com
  2. ....

That is: we now treat URL reference similar to the way the :doc: role is handled.

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:

@azmeuk Thanks for testing :) Merging now.


Automated cherry pick of #4013: fix: network-addresses add created_at column

Cherry pick of #4013 on release/2.13.
#4013: fix: network-addresses add created_at column

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.13@efad765). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.13   #4015   +/-   ##
==============================================
  Coverage                ?   6.94%
==============================================
  Files                   ?     505
  Lines                   ?   85039
  Branches                ?       0
==============================================
  Hits                    ?    5906
  Misses                  ?   78632
  Partials                ?     501

Flag
Coverage Δ

#aFlag
6.94% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/networks.go
0.55% <0%> (ø)

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 efad765...fff2218. Read the comment docs.

/lgtm
/approve


[SPARK-7749] [SQL] [WIP] Fixes partition discovery for non-partitioned tables

When no partition columns can be found, we should have an empty PartitionSpec, rather than a PartitionSpec with empty partition columns.
This PR together with #6285 should fix SPARK-7749.

Merged build triggered.

Merged build started.

Test build #33151 has started for   PR 6287 at commit 19ae41e.

Test build #33151 has finished for   PR 6287 at commit 19ae41e.

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

Merged build finished. Test FAILed.

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

Merged build triggered.

Merged build started.

Test build #33157 has started for   PR 6287 at commit fc56656.

Test build #33157 has finished for   PR 6287 at commit fc56656.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #33171 has started for   PR 6287 at commit 5aa87ea.

Test build #33171 has finished for   PR 6287 at commit 5aa87ea.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #33245 has started for   PR 6287 at commit c4949be.

Test build #33245 has finished for   PR 6287 at commit c4949be.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #33250 has started for   PR 6287 at commit a799ff3.

Test build #33250 has finished for   PR 6287 at commit a799ff3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

LGTM. I am merging it to master and branch 1.4.


Crash on Windows 10 - Race condition with CrashHandler recreation and Enumerating GPU threads

Description
RenderDoc official build v1.15 crashes on Windows 10 Enterprise after a while, the windows sessions needs to stay open for a day or two. It requires a fresh reboot to work again. Then I found out if I rebuild from source code the crash never happens and I discovered that the CrashHandler itself is the culprit.
Resuming short: you need to join all GPU enumerating threads BEFORE deleting the existing CrashHandler. Looks like after a while the enumerating GPU threads become slower and slower and a race condition causes the crash because the crash handler have been deleted and not yet recreated when it hits in another thread:
WrappedID3D11Device *wrappedDev = new WrappedID3D11Device(device, initParams);
that itself will call for a CrashHandler that dies in a pure virtual call.
We are hitting it with remote desktop I don't know if is part of que equation, I cannot go to studio now until the pandemic ends
I think you need a join here:
    if(existing)
    {
      CrashHandler *crash = ((CrashHandler *)existing);
      m_PipeName = crash->m_PipeName;
      mem = crash->m_ExHandler->QueryRegisteredAppMemory();
      RDCLOG("Re-using crash-handling server %s", m_PipeName.c_str());
      SAFE_DELETE(existing);
    }

Steps to reproduce
Leave the windows session open for a few days, running a remote session with Remote Desktop and then run RenderDoc official build (with CrashHandler active)
Environment
It doesn't matter the version if I build myself with #define RENDERDOC_OFFICIAL_BUILD 1 I get the same issue

RenderDoc version: 1.15 (but also found in 1.12)
Operating System: Windows 10 Enterprise
Graphics API: D3D11, D3D12, Vulkan, RTX2080 SUPER

It does not matter the driver or video card. A colleague got same issue on a GTX1080

Thanks for digging into this. I've had one or two crash reports that in retrospect are presumably this bug, but I never got any repro steps and I couldn't work backwards from the minidump to see what went wrong. I'm surprised I haven't run into this myself, but I guess it depends entirely on how that race condition ends up working out.

Looking at it in more detail I suspect it was maybe the crash handler recreate that was taking longer over time, rather than GPU enumeration. Either way, I was able to make it happen reliably with some judicious sleeps, and after rearranging the order of things so the recreate happens immediately before kicking off the GPU enumeration instead of immediately after it fixed the crash. I've also added some locking around recreating the handler just in case this happens somewhere else in future.


get aligned length from diamond SAM output

this is for the calculation of alignment coverage.

this is already addressed in #66


AWS infrastructure

The cloud computing side of FOREST needs attention.

Transfer to S3
Continuous deployment pipeline

AWS CodeDeployment service requires an appspec.yml file to allow it to know how to install/run FOREST

Travis CI can be used to trigger CodeDeploy on commit

CodeDeploy and CodePipeline AWS services have been developed to deploy https://forest.informaticslab.co.uk on every commit of master
The Rose suite has been migrated to transfer data to the RMED AWS buckets


Add Formatter.register method that requires all modules in formatters dir

Hey Rob,
I've moved out the formatter to the content-formatter module.
However, I did keep the formatters.js file, but it just contains this currently:
require('./css');
require('./html');
require('./js');

module.exports = require('content-formatter');

Mainly so that everywhere that is wanting to use the formatter doesn't have to do the work of registering the modules.
I'm on the fence about if this is the right strategy, but overall, I think it allows both options (load the formatter without registering, or load it with registering).
Could you send the register additions over to the content-formatter repo, and then resolve the merge issues with the other items?
Thanks Rob :)


Mass-bidding on Alphonso Davies - error

I was mass bidding on Alphonso Davies and it started bidding on players which arent Davies. It also massively over bid on all of those cards by about 8k each.
Did i do something wrong in setting it up?

Oh no! Only use the autobidder on players with ONE version of their card - ie they can't have an in form or UCL, they just have a base card version.
Sorry this happened but please make sure to read the pop up notice when adding players (it says this exactly), or any pop up messages in general.
I'm going to add a function that doesn't let the bot start if a player with multiple versions is added.. again sorry this happened

Haha I saw it and it didn't even register with me that he had more than one card 🙈. I will continue to test now

Haha I saw it and it didn't even register with me that he had more than one card 🙈. I will continue to test now

I've now tried it with Jonny Evans, who only has one card. It bought 3 cards at 9900 each. Something funky is going on haha

F
Can you upload your gui_logs.txt?
And do you know if it bid the absurd amount while searching the TM or while on the watch list

gui_logs.txt

F
Can you upload your gui_logs.txt?
And do you know if it bid the absurd amount while searching the TM or while on the watch list

it happened while on the tm. I was watching the webapp.

Taking a look now, sorry again

Can you send my player_list.txt? I've tried replicating this error so many times and never catch it. It looks like you were bidding on other players before Evans, did it bid properly on them and only happened to Evans or no

Can you send my player_list.txt? I've tried replicating this error so many times and never catch it. It looks like you were bidding on other players before Evans, did it bid properly on them and only happened to Evans or no

I closed down the GUI and reopened, then deleted other players it bid on
player_list.txt

About to push out a massive update that should fix all of this! Hope you'll give it another try... it won't look that much different but the backend is completely reworked and concurrent bot objects can't be created which is what caused the issue here

Yep happy to keep testing when you need! Let me know when you have pushed the update!

Just uploaded... now it lets you know if the bot has stopped, when the Start Autobidder button pops back up.
So to stop the bot during its execution just interrupt and if it fights back (esp when searching for players) just fight some more and it'll eventually break.
Let me know if the bidding error happens
Also there's a feature that minimizes bid wars which could be good if you're not making much profit

I've been testing on and off over the last few weeks, and its seriously good! I cant really find many faults, and I can virtually leave it unwatched to do its thing! Good job and Thanks!

That's awesome! Thanks man!


Company register spec

In the company_register.component.test the core of test is expectation about the success message and if the user were pushed from current page to companies list page.
This test just the way he is, apparently, doesn't make sense to be an simple test, instead we have to consider test it as e2e, because he is testing more than one component, more than one page. Furthermore, this test is about the admin flow of register a new company. If make sense to project, I can add this spec and fix the other broken tests

Closing this once this PR - Issue 48 | Fix broken tests #66 implements the e2e tests for Company Register


Avoid NPE on spreadsheetDrawing row tags

Ignore xdr:row tags. Fixes #59.

Sorry for the delay, the holidays kind of killed my free time for a while. This looks good to me, thanks for including a unit test!


Update all example yaml snippets in virtualserver.md

... to reflect the actual configuration based on all previous exercises in the labs. There are a number of resources missing.
https://github.com/f5devcentral/modern_app_jumpstart_workshop/blob/783649e0d46aa5ad34242aef9184ff3c42caaf60/docs/ingress/virtualserver.md?plain=1#L108

Read through the virtualserver.md file once again. The way the directions read makes me think this is unnecessary to do. Close?

Closing.


Create prepare-commit-msg git hook

Detailed description
Currently I only support pre-push and pre-commit. Next plan is to allow running artisan commands during the prepare-commit-msg git hook.
Context
Possible implementation

[ ] create bash file in src/hooks named prepare-commit-msg.sh, and can use the others as a template.
[ ] edit config/hooks.php and add a new array key config for the pre-commit-msg hook.
[ ] create a new command in src/Commands/CommitHooks named PrepareCommitMessage, which extends CommitHookCommand. The getConfigKey function should be implemented to point to the configuration key created in the previous step.
[ ] ensure that this new command is made available
[ ] add the new prepare-commit-msg.sh file to the list of files to be copied over.

Thanks @today- !


Adding HTTP/2 Support

Closes #543

Reviewer Notes - WIP

The first commit is the addition of the ls-hpack contrib. It provides the HPACK parser for HTTP/2 HEADERS frames.
The second commit adds scopeLogHex() to generate hexdumps to the logging destination. This proved handy while working on the HTTP/2 frame parsing and it seems like it could be useful later. I also added some scopeLog*() macros to make logging a little more compact.

ToDo

[ ] Handle HTTP/2 frames in the same payload as the HTTP/1 upgrade response
[ ] Make searching case-insensitive when scanning the HTTP/1 header block for content-length, upgrade, and connection headers.
[ ]


GitVersion not working in Ubuntu 20.04

Description
When the ubuntu-latest VM image switched to 20.04 we started getting the following error from GitVersion:
System.TypeInitializationException: The type initializer for 'LibGit2Sharp.Core.NativeMethods' threw an exception. ---> System.DllNotFoundException: Unable to load shared library 'git2-572e4d8' or one of its dependencies. In order to help diagnose loading problems, consider setting the LD_DEBUG environment variable: libgit2-572e4d8: cannot open shared object file: No such file or directory
There was another error logged in the preceding step to install the .NET Core SDK:
get-os-distro: Error: Distribution specific OS name and version could not be detected: UName = Linux
This error didn't fail the install of .NET Core, but it seemed to make it so it didn't recognize what version of Linux it was running on. In the step's log it listed this as the version:
Primary:linux-x64 Legacy:-x64
Where in the previous build it listed this:
Primary:linux-x64 Legacy:ubuntu.18.04-x64
We are unsure if the two are connected, but changing the VM over to windows-latest fixed both issues.
Area for Triage:
Unknown
Question, Bug, or Feature?:
"Bug"
Virtual environments affected

[ ] Ubuntu 16.04
[ ] Ubuntu 18.04
[x] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11.0
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

Expected behavior
GitVersion runs successfully
Actual behavior
Bug displayed above
Repro steps
Failed build - Only preserved for a week.

Have an azure devops environment with the GitVersion extension
Run this pipeline template (.yml file)

jobs:
- job: Semver
  pool:
    vmImage: 'ubuntu-latest'
  steps:
  - task: UseDotNet@2
    displayName: 'Use .NET Core sdk (for GitVersion)'
    inputs:
      packageType: sdk
      version: 2.1.x

  - task: GitVersion@5
    displayName: 'GitVersion'
    inputs:
      configFilePath: '$(Build.SourcesDirectory)/GitVersion.yml'

the same here!

Hello everyone, I think this issue related to GitVersion. It was fixed in new release (5.6.0) for ubuntu 20.04. You can try to use this snippet:
  - task: UseDotNet@2
    displayName: 'Use .NET Core sdk (for GitVersion)'
    inputs:
      packageType: sdk
      version: 5.x
  - task: gitversion/setup@0
    inputs:
      versionSpec: '5.6.0'
  - task: gitversion/execute@0
    inputs:
      useConfigFile: true
      configFilePath: '$(Build.SourcesDirectory)/GitVersion.yml'

Another way change ubuntu image to 18.04, because previously builds were run on ubuntu 18.04 and it worked.

Hello everyone. We're going to deploy new image with GitVersion (5.6.0) on January.

Hello everyone, I think this issue related to GitVersion. It was fixed in new release (5.6.0) for ubuntu 20.04. You can try to use this snippet:
  - task: UseDotNet@2
    displayName: 'Use .NET Core sdk (for GitVersion)'
    inputs:
      packageType: sdk
      version: 5.x
  - task: gitversion/setup@0
    inputs:
      versionSpec: '5.6.0'
  - task: gitversion/execute@0
    inputs:
      useConfigFile: true
      configFilePath: '$(Build.SourcesDirectory)/GitVersion.yml'

Another way change ubuntu image to 18.04, because previously builds were run on ubuntu 18.04 and it worked.

Hello Dmitry, Thanks a lot, I put the tasks as you suggested and It worked to me in Ubuntu 20.04

Hello everyone. Sorry for confusion, we do not preinstall gitversion for ubuntu. If you have any concerns feel free to reopen the issue.

Hello everyone. Sorry for confusion, we do not preinstall gitversion for ubuntu. If you have any concerns feel free to reopen the issue.


align version to Camel

fixes https://issues.apache.org/jira/browse/CAMEL-20959
Version in pom.xml is changed to 4.4.0-SNAPSHOT as the recipes are migrating to Camel 4.4.x

I changed version to 4.7.0-SNAPSHOT to reflect the newest recipes from Camel 4.6 to Camel 4.7


adding more robust main.py testing

Currently disabled for CUDA because it only produces black images on my vm and on builder.
Adds support for any model listed in model_config.json. However, any additions to model_config.json will need to be added to the golden images in order to work correctly. Alternatively I can change this to fail the builder if a new golden value isn't added.
Stable diff v1 also appears to be broken on ToM
Any failures in image comparison will be automatically uploaded to gs://shark_tank/testdata/builder
Note that any file 842b is a black image.  (failure)

Let's fix v1 and the CUDA builds and expand the testing. Ok to fail build if golden image is missing. Just suggest the remedy


Create nightly builds of OSM w/ Helm charts

The goal of this task is to create nightly releases with Helm charts etc.
These will be picked up by soak/perf test infrastructure and validation results will be emitted for each nightly build.
A subsequent release candidate will be cut from the nightly build after soak tests show our confidence with some significance that the software works well.

All of the setup for this is done. I've talked with @allenlsy before about how to enable these when we need them.


PLEASE don't mess with already-released tarballs.

Hi.
This is the second time that i know of.
Please please please, once you have made a release, and uploaded release tarballs,
DO NOT TOUCH THEM. Ever. For any reason whatsoever. Make new release.
18 days ago https://github.com/zeux/pugixml/releases/download/v1.9/pugixml-1.9.tar.gz
had SHA512=f97941941d98a1a056087edc0dde6376bf2cc12ce4523b67a2f2ec5ae0895c2a2e55da32fcca6a997f1a0d918c5f39564167da0a07ce0d7da92880ad8631c31e
now, it is 853a9d985aae537391c6524d5413ef4de237d99d96cc58ea7fe7152f786df1e408cdacd2e4387697e23c3e67cdc1d42b29de554501309eae16d86edd0e24785f
This is really not cool. It is unclear whether there is a MITM, a typo in the checksum that was saved,
or something else :/

I'm not sure how to check the upload history but this release clearly wasn't re-released. I'm not sure what happened here.

This file was updated on August 20:
https://github.com/Homebrew/homebrew-core/blob/master/Formula/pugixml.rb
It lists d156d35b83f680e40fd6412c4455fdd03544339779134617b9b28d19e11fdba6 as the SHA256. This matches what I can compute from a file I just downloaded:
zeux@SM-ARSENY3:/mnt/c/Users/arseny/Downloads$ openssl sha512 pugixml-1.9.tar.gz
SHA512(pugixml-1.9.tar.gz)= 853a9d985aae537391c6524d5413ef4de237d99d96cc58ea7fe7152f786df1e408cdacd2e4387697e23c3e67cdc1d42b29de554501309eae16d86edd0e24785f
zeux@SM-ARSENY3:/mnt/c/Users/arseny/Downloads$ openssl sha256 pugixml-1.9.tar.gz
SHA256(pugixml-1.9.tar.gz)= d156d35b83f680e40fd6412c4455fdd03544339779134617b9b28d19e11fdba6

Are you sure the SHA512 you have recorded was correct?

Same SHA256 is recorded here:
https://patchwork.ozlabs.org/patch/927119/
My conclusion is that you have incorrectly recorded the SHA512 previously. Just to reiterate, the only instance of reupload was the timestamp fix applied to .tar.gz of 1.8.0 (I think?) - no files have been reuploaded since and they won't be in the future.

I don't remember repacking it at least..
/usr/src# sha512sum pugixml-1.9.tar.gz
f97941941d98a1a056087edc0dde6376bf2cc12ce4523b67a2f2ec5ae0895c2a2e55da32fcca6a997f1a0d918c5f39564167da0a07ce0d7da92880ad8631c31e  pugixml-1.9.tar.gz
/usr/src# ls -lah pugixml-1.9.tar.gz
-rw-r--r-- 1 lebedevri lebedevri 543K Oct  6 21:42 pugixml-1.9.tar.gz

pugixml-1.9.tar.gz

Ok - I see what's going on. The SHA512 you had in mind was for this:
https://github.com/zeux/pugixml/archive/v1.9.tar.gz
Not for this:
https://github.com/zeux/pugixml/releases/download/v1.9/pugixml-1.9.tar.gz
The former is the source package that GitHub automatically makes, that just archives every single file in the repository.
The latter is the release package that I build - these contain only files that are relevant to the end users, with the correct newlines per platform (.zip is different from .tar.gz - not sure if GitHub archive behaves the same way).

I have come to the same conclusion at the same time :/
$ wget https://github.com/zeux/pugixml/archive/v1.9.tar.gz
--2018-10-24 21:40:28--  https://github.com/zeux/pugixml/archive/v1.9.tar.gz
Resolving github.com (github.com)... <IP_ADDRESS>, <IP_ADDRESS>
Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://codeload.github.com/zeux/pugixml/tar.gz/v1.9 [following]
--2018-10-24 21:40:29--  https://codeload.github.com/zeux/pugixml/tar.gz/v1.9
Resolving codeload.github.com (codeload.github.com)... <IP_ADDRESS>, <IP_ADDRESS>
Connecting to codeload.github.com (codeload.github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/x-gzip]
Saving to: ‘v1.9.tar.gz’

v1.9.tar.gz                                                             [   <=>                                                                                ] 542.46K   626KB/s    in 0.9s

2018-10-24 21:40:31 (626 KB/s) - ‘v1.9.tar.gz’ saved [555480]

$ wget https://github.com/zeux/pugixml/archive/v1.9.zip
--2018-10-24 21:40:36--  https://github.com/zeux/pugixml/archive/v1.9.zip
Resolving github.com (github.com)... <IP_ADDRESS>, <IP_ADDRESS>
Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://codeload.github.com/zeux/pugixml/zip/v1.9 [following]
--2018-10-24 21:40:37--  https://codeload.github.com/zeux/pugixml/zip/v1.9
Resolving codeload.github.com (codeload.github.com)... <IP_ADDRESS>, <IP_ADDRESS>
Connecting to codeload.github.com (codeload.github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/zip]
Saving to: ‘v1.9.zip’

v1.9.zip                                                                [    <=>                                                                                ] 610.72K   662KB/s    in 0.9s

2018-10-24 21:40:39 (662 KB/s) - ‘v1.9.zip’ saved [625376]

$ sha512sum v*
f97941941d98a1a056087edc0dde6376bf2cc12ce4523b67a2f2ec5ae0895c2a2e55da32fcca6a997f1a0d918c5f39564167da0a07ce0d7da92880ad8631c31e  v1.9.tar.gz
6fe52b7b086b32310d7a939352c4b1732d6a53425029d376c169c796721144a1db82b6b5476e99c483ab674097a47584dc83f31dd39ee381f13ea4271b50c843  v1.9.zip

Indeed, i messed up here, i'm sorry.

It's unfortunate that GitHub serves the v1.9.tar.gz file using the pugixml-1.9.tar.gz name - at least that's what happens if I open the link in Chrome. Sort of understandable - they probably want the repo-specific name so that it's more convenient for the users - but unfortunately as a result the downloaded names are exactly the same.


Get The Length of an Array - The count() Function

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[ ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@imamwahyudi1995 Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


Add support for hexagon-unknown-linux-musl

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @gnzlbg (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

@bors: r+
LGTM. Do you know if qemu supports hexagon ? If so, it might be worth it to try to set up a docker container that runs libc tests for this target under qemu-user like we do for the other targets.

:pushpin: Commit 214d32d2656831c06ad8d3943402670166e34cab has been approved by gnzlbg

:hourglass: Testing commit 214d32d2656831c06ad8d3943402670166e34cab with merge a9b130b8fd1364f37308e49b9ae21a86d37b53fc...

:broken_heart: Test failed - checks-travis

@bors: retry

:hourglass: Testing commit 214d32d2656831c06ad8d3943402670166e34cab with merge 2b01f7e67322175e05f25325e6e941aa9a3ddeae...

:sunny: Test successful - checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-travis, status-appveyor
Approved by: gnzlbg
Pushing 2b01f7e67322175e05f25325e6e941aa9a3ddeae to master...

@bors: r+
LGTM. Do you know if qemu supports hexagon ? If so, it might be worth it to try to set up a docker container that runs libc tests for this target under qemu-user like we do for the other targets.

No upstream support yet but we'll be working on that soon.  Once it's present there we can add it.
Do you know how the qemu package(s) are installed for the CI?  Does it just use the distro release of qemu?  I ask because it would probably take quite a while after upstreaming before we saw it in an Ubuntu/Debian release.

Do you know how the qemu package(s) are installed for the CI? Does it just use the distro release of qemu? I ask because it would probably take quite a while after upstreaming before we saw it in an Ubuntu/Debian release.

I think we could just install the latest released qemu from a third-party repository, at least, until the required qemu version starts being shipped by the distro.


[Feature Request] Add year and album total track to metadatas

Hi!
Would be great to have track album/release YEAR and TOTALTRACKS in the file metadatas as well 🙏

I've dug into the year a little and the tag is passed all the way through to music-tag but doesn't appear to get added. Seems like this has been an issue with music-tag for a while https://github.com/KristoforMaynard/music-tag/issues/10, but it might be os/software based instead of a problem with the module


BACKPORT - fix docs for Deliveryservice/sslkeys/generate and deliveryservice/ssl…

…keys/add.  This fixes #1001.
(cherry picked from commit 9577cb6522e708605c78d8d54ffb958b84ce1576)

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/442/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/398/


Fix background image

Apply background image only where captcha and icons are displaying and that too before the input area.
Captcha content and icons should display over the image.
Size of Background-image of captcha should vary depending on the captcha content.

so here do we need to add a different background image for the captcha or the same one we used as background

assign me to this task

did you mean it in this way,if yes please assign this to me.
Screenshot:

@Pudi-Sravan The change is correct but you have exchanged both the image.

@syamjir  @Pudi-Sravan is currently working on this issue.

@AdityaSinha2305 ok thank u .

@AdityaSinha2305 could you please once go through the changes and merge if everything looks good.
i have first sent a pr for the alignment and next for this background.

@AdityaSinha2305 i think this issue has been already resolved and merged so i think this can be closed


need a built-in way to dump kernel file

Diagnozing a front-end issue (e.g. #32204) might require looking at kernel file. Unfortunately we don't have a reliable way to do it right now.
We need to provide tools to dump kernel

[ ] as part of the SDK
[ ] as part of Flutter frontend_server

/cc @kmillikin @aam

We have a visualization/editing/debugging tool that we intended for this purpose but we haven't put it in the SDK.  It might just need an owner.

How does this relate to pkg/vm/tool/dump_kernel ?


[release-0.50] Make names of access tests around test_id:2921 unique

This is a manual cherry-pick of #7673
/assign dhiller
NONE

/retest-required

/lgtm

/approve


zaz: 1.0.0 -> 1.0.1

Motivation for this change
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-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)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 117581 at c3b5f7c6 run on x86_64-linux 1

1 package built successfully:

zaz

1 suggestion:

warning: unclear-gpl
gpl3 is a deprecated license, please check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/games/zaz/default.nix:53:5:
   |
53 |     license = licenses.gpl3;
   |     ^


Unknown property: "getSelectedVertices" in #Struct:skinOps() with 'Find wights conflict' utility

hi. the script is great. I was able to skin character and put into the game just in 2 evenings.
now I want to improve the skin but when I try to use 'Find wights conflict' utility I'm getting this error over and over:
skin_weigths_error.txt
maybe I don't use it right?

I will take a look at it

It's fixed in version 0.8.3


Action Style not supported in cards in Teams

Docs Build status updates of commit 4193871:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/task-modules-and-cards/cards/cards-reference.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit f586daa:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/task-modules-and-cards/cards/cards-reference.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


⚠ ClamAV has degraded performance

In bb10aef, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 615 ms

Resolved: ClamAV performance has improved in 68609f4 after 13 minutes.


Travis: ignore PHP deprecation notices for stable PHPCS releases

The unit tests will fail when a PHP warning/notice/deprecation notice is encountered.
Deprecation notices thrown by already released PHPCS versions won't get fixed anymore (in that version), so failing the unit tests on those is moot and will skew the reliability of the Travis results.
To see the effect you'd need to check the Travis logs for the PHP 7.4 builds and compare them with a recent build on another branch, like https://travis-ci.org/WPTRT/WPThemeReview/builds/561796063 .

Oh and I forgot to mention:
The PR also makes it so this repo gets unit tested against WPCS develop as the "high" version, not master which is the latest release.
Testing against the latest release means we don't get early warning about upstream changes we need to account for in the sniffs in this repo, while we should.
Note: I've not changed the WPCS branch being used for the CS check of the code in this repo.
It makes more sense for the CS changes to be done on stable WPCS releases and not every time something changes upstream.


keypoints drift from their true positions

Thanks for the amazing dataset.
I'm using Matlab to check the keypoints of randperson_subset (randperson_subset_point.txt). From my understanding, there are 9 pairs of (x,y), and start from the 3rd pair is the body keypoints, therefore I plot them on the corresponding images. However, I observed some keypoints are drifted from their true positions. Can you shed some insights on how to get the positions correct?
Examples of drifts:

Apart from the above question, I'm curious if the visualibity of the keypoints can be obtained (since there are occlusions in the images)?

Thank you for your attention.
There is indeed a key point offset problem when the character moves, which may be because the character moves too fast or rendered too many characters. We currently have no rules for finding offset points, so we have not dealt with this problem. Maybe create a new video with slow movement and decrease the number of characters will help.
As for the person-to-person occlusion of key points, it can be judged by the z value of the point coordinates, which is provided in the original data (video folder). Environmental occlusion can evaluate the occlusion by comparing the z-values of people in different positions or record the z-values of environmental occlusion objects in a new video.


it would be better if there were a list for the modes

I got confused when I opened it..
it would be better if you can do a list when I Right-Click to show me the different modes
another thing , there is no an option for deleting the stuff
.....
hopefully I could contribute with you soon , just started learning about Qt ,
the project is awesome by the way!

Hi :D I don't understand what modes mean. Care to explain?
deleting stuff is in progress: issue #66
Would love to see pull requests from you soon, and thank you :D

I just meant the  <Select , Draw , ... > options 😄
just meant something like that one in the center.

okay so you think it's a good idea to have a context menu having all the tools like select and draw. Well from a usability point of view I don't think that's what most users would expect. Context menus usually contain options regarding the currently selected item. so it can for example have delete, cut and copy.
What's wrong with having the tools in the toolbar at the top?


Fixed the translation of the question id

Hello, I would like to help translate in Indonesian.

Please translate full questions, not just headlines.


Issue with Kernel 4.4.103-36 and DKMS <IP_ADDRESS>

Followed the advice of this comment to get the module to compile in the displaylink-install. Here is a diff:
--- ../evdi_fb.c        2017-10-06 05:58:54.000000000 -0500
+++ evdi_fb.c   2017-12-18 14:36:25.458211744 -0600
@@ -229,7 +229,7 @@
                ret =
                    dma_buf_begin_cpu_access(
                        ufb->obj->base.import_attach->dmabuf,
-#if KERNEL_VERSION(4, 6, 0) > LINUX_VERSION_CODE
+#if KERNEL_VERSION(4, 6, 0) < LINUX_VERSION_CODE
                        0, ufb->obj->base.size,
 #endif
                        DMA_FROM_DEVICE);
@@ -247,7 +247,7 @@

        if (ufb->obj->base.import_attach)
                dma_buf_end_cpu_access(ufb->obj->base.import_attach->dmabuf,
-#if KERNEL_VERSION(4, 6, 0) > LINUX_VERSION_CODE
+#if KERNEL_VERSION(4, 6, 0) < LINUX_VERSION_CODE
                                       0, ufb->obj->base.size,
 #endif

Hopefully this will help if anyone else runs into the same issue. A better solution might be to just change the KERNEL_VERSION(4, 6, 0) to KERNEL_VERSION(4, 4, 0).

Some time has passed. I hope we have solved already all problems with 4.4 compilation :) Will close this issue.


compileSkip setting analogous to testSkip

+1 I like the idea!

hopefully when we make this a real plugin starting tomorrow, we will use normal task.enabled = false.
this causes some issues, which I'm fixing (one sec...)

@advayDev1 - thanks for contributing, I only changed the description to make "compileSkip" the first word in the description.

@brunobowden  - sorry, commit race.  please merge in #82  as well


fix: fix an incorrect typescript definition

resolves #42

Update the readme for getAuthStatus :) still uses the old type.

Update the readme for getAuthStatus :) still uses the old type.


Undocumented config option "now"

I want to modify the default date that it's handled by the instance as "today", so the calendar starts in another year/month but without anything selected.
So I tried to look at the documentation and I didn't found anything and googling around I found a comment about instance.now and it turns out that setting in my element data-now = "yyyy-MM-dd" does exactly what I want.
So the request is just to add it to https://flatpickr.js.org/options/
Thank you very much.

I think it would help slightly if you shared a code example of how you use that. Not least, as I admit, reading your issue I am not clear on that at all as it hinges on interpreting setting in my element data-now = "yyyy-MM-dd" does exactly what I want., which, even as a native English speaker I am failing at ;-).

This is what I'm talking about:
<input type="text" placeholder="'Today' is 2021-3-28" class=date data-now='2021-3-28'>
You can see that the input opens with 2021-03 as the month selected by default and it marks the 28th with a circle as it happens by default with "Today"
https://jsfiddle.net/AlfonsoML/aetpgo5d/4/
Someone that is able to explain this properly should add it to the docs so other people can learn about this little feature.


Rembg integration

The pull request integrates u2-net background removal. So you can remove the background before or after the depth is calculated. It allows you to save the background removed image, and a bk/white mask. default is set to off.
There's one line that might cause trouble on Windows
os.environ["U2NET_HOME"] = str(bg_model_dir)
this line tells rembg where to look for the model.
I haven't fully tested with 3dinpaint or stereo images. An alpha channel is added if using pre-depth calculate which might cause issues with them.
Removing the background before calculating depth for certain images can really improve the details.
depth with background removed

depth with normal background

orginal

There's also u2-net clothing segmentation, but that seems a little out of scope for the moment.

just noticed this is breaks the depth tab.

Hey, great! Looks like a clean integration, I've not tested it yet, does it work on Windows ?

I don't have a Windows machine. It should work. I just noticed there was quite a few stackoverflow questions about Windows and os.environ , but most are related to permanently setting environment variable.
It should still work without the line. It would just download the models to ~/.u2net folder instead of the webui's /model folder

Hey sorry for the delay, I've been a bit preoccupied .. Will merge asap.


Security and implementation

This project looks awesome! I was wondering: can one get an overview of how much of LaTeX it implements? Is it based on some other implementation? Are all the LaTeX commands it supports in one and the same file, or are they spread out?
Second question: are there any security implications from using this library? Does it allow any shell escaping or system calls, or that kind of thing? I know TeX is its own programming language and has commands like \input.

can one get an overview of how much of LaTeX it implements?

Currently not. I'm planning to make a table to show supported commands.

Is it based on some other implementation? Are all the LaTeX commands it supports in one and the same file, or are they spread out?

This project implemented based on the TeX algorithm (part of it, the primitive \def, \xdef are not supported now), no other dependencies required. You can check the directory src/core out.

are there any security implications from using this library?

Honestly, I'm not 100% sure, but any suggestions are appreciated.


Warning fixed for another PR

Warning fixed for PR https://github.com/MicrosoftDocs/azure-dev-docs-pr/pull/1299

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

Hi @v-hearya - This pull request was opened in the public repo. It looks like you have worked in the private repo before. Would you make this content update in the private repo instead? Thank you! We'll close this PR.


[Removal]: Modern Candy Goose

Hotspot Name
Modern Candy Goose
Hotspot b58 Address
112NDR8GrsQAJemBznfMCsm7TfcQwTbSDWXW9f4SD73KVSaq8b4T
Discord Handle
Icenor#9568
Hotspot Manufacturer
Bobcat
Removal Reason
I have not taken any action aimed at cheating. I don't know what is the reason for my inclusion in the denylist.
Modifications
No
Extra forwarders
No
Extra antennas
No
Additional Information

We have taken into account this removal request in the next iteration of the denylist. It may take some time before it's processed. This is an automated comment due to the volume of addition and removal requests. A future tool is in the works to provide more insight into the analysis approach made by the Helium team and community members that maintain this list.


st7789 and st7735 Support for ili9XXX hybrid driver

Support ST7789 and ST7735 displays for the ESP32 LVGL MicroPython bindings. It was tested with TTGO T-Display, TTGO TWatch-2020, generic eBay ST7735, m5stack core, and core2 devices. See https://github.com/russhughes/lv_st7789 for lv_examples modified to run with this driver.

@russhughes I've reviewed your changes and tested it with a ili9341 display. Everything looks good!
What do you think about my suggestion above? :

Perhaps your "configs" scripts could be used as drivers for specific boards?
A user who uses a specific board might appreciate being able to simply import a display driver script instead of configuring all the parameters to match the board.

I think that would be helpful to people, where should they go?

I think that would be helpful to people, where should they go?

Maybe we can think of these "config" scripts as "Board Support Modules" - Python modules per board that import and initialize everything related to that board (usually display and input drivers, but could also be other things).
We can create a new boards/ directory under lv_binding_micropython root and put them there. Later we could freeze them on lv_micropython for each board (with their related drivers).
One comment though. I'm not sure it's a good idea to initialize the display upon import, like you did in your "config" modules.
It doesn't give the user a chance to configure anything. Sometimes it makes sense to configure the display differently for the same board, for example to control landscape/portrait display or use the async event loop.

Merged!
Thank you for your contribution.
If you decide to contribute the board configuration scripts, feel free to open another PR.


npm install throws: "node postinstall shell-init: error retrieving current directory"

Tried install with sudo but no luck. Can provide logs if needed.
`/usr/local/bin/football -> /usr/local/lib/node_modules/footballcli/cli.js

<EMAIL_ADDRESS>postinstall /usr/local/lib/node_modules/footballcli/node_modules/spawn-sync
node postinstall

shell-init: error retrieving current directory: getcwd: cannot access parent directories: Permission denied
path.js:1142
cwd = process.cwd();
^
Error: EACCES: permission denied, uv_cwd
at Error (native)
at Object.resolve (path.js:1142:25)
at startup (bootstrap_node.js:127:32)
at bootstrap_node.js:509:3
/usr/local/lib
└── (empty)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>postinstall: node postinstall
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'node postinstall'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the spawn-sync package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node postinstall
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs spawn-sync
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls spawn-sync
npm ERR! There is likely additional logging output above.
npm ERR!      /Users/Tobi/.npm/_logs/2017-05-05T00_02_41_132Z-debug.log
`

@TobiMadeIt Thank you for reporting this. Could you please try installing it with sudo, i.e. sudo npm install -g footballcli?

I did. Mentioned this in OP btw

@TobiMadeIt Is this happening during install or during usage?

This happens on initial install. My npm version is 4.4.1

@TobiMadeIt Please share your node version, OS and log file created.

node -v is 6.9.5
macOS 10.12.4
Log file is attached.
football.txt

@TobiMadeIt Pretty sure it's not the issue of this package. On searching, one can see multiple instances of reporting this issue. This issue might also depend on the way node was installed (as mentioned in some reported Github issues). Could you please try solution mention here?

I just tried that with no luck. I'm still getting the exact same error. I did some prior research as well. Multiple cases pointed to the package attempting to reference node legacy(node) instead of nodejs. Could that apply to this case?

@TobiMadeIt Try it out. You might also want to give this a try.

I'm a bit wary of

sudo chown -R $USER /usr/local

There doesn't seem to be a straight forward way of reverting the changes and there's a lot of talk warning against leaving things that way security wise.
I did try this

sudo chown -R $USER ~/.npm

but that didn't help

@TobiMadeIt Apologies for the delay in replying. Is this still relevant? Were you able to fix it?

@TobiMadeIt I'm closing this issue. If you're still facing this, let me know and I will reopen this.


Introduce browser support

Remove util.inherits
Create a build target for browsify
DefaultTransporter should be able to detect env and change behavior accordingly.
Discovery cache should be auto switched off.

@rakyll as of today there's no way to add google apis in a Webpack/Browserify bundle? didn't find anything yet

This library will remain Node.js-only. To access Google APIs from the browser, use the Google API Client Library for JavaScript

that's what I thought @jmdobry , unfortunatly it's not really clear how to integrate this library inside a webpack bundle as it seems the methods are somehow loaded lazily by discoveryUrls.

I don't think you can integrate it into a webpack bundle


There is one more pattern of this in the static block at the end of the file; do you want to replace this as well? Might be good then to make peeked() package-private to avoid a synthetic accessor method (I assume).

There is one more pattern of this in the static block at the end of the file; do you want to replace this as well? Might be good then to make peeked() package-private to avoid a synthetic accessor method (I assume).
Maybe at that point it might also make sense to merge peeked() and doPeek() into one method?
(I am not a member of this project; the maintainers will probably give you more in-depth feedback)
Originally posted by @Marcono1234 in https://github.com/google/gson/pull/2083#pullrequestreview-894213652

Hi


feat(mesh): collection page add comment modal

Feature

Add comment modal for collection desktop page - figma
(refactor): Story comment components support collection
(refactor): Story pickers modal support collection
(fix): avatar keep loading fetching wrong fallback image

Asana link

因 @tyc67 休假的關係，先不請 yc review。


Sparse .var() getting wrong fill values

This has come up in CI (example: https://github.com/dask/dask/pull/6896/checks?check_run_id=1831740059) when testing with newer versions numpy 1.20.
Some of the sparse tests are marked with xfail and a sparse issue.
https://github.com/dask/dask/blob/0bb8766d659ba77805ba75cb43ee0c39ed760f25/dask/array/tests/test_sparse.py#L40-L44
The sparse issue was closed a long time ago and I think at this point the xfail is masking a dask issue.
Minimal Complete Verifiable Example:
import dask.array as da
import sparse

x = da.random.random((2, 3, 4), chunks=(1, 2, 2))
x[x < 0.8] = 0

y = x.map_blocks(sparse.COO.from_numpy)

y.var().compute()

---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-2-b23e571e73a3> in <module>
      7 y = x.map_blocks(sparse.COO.from_numpy)
      8
----> 9 y.var().compute()

~/dask/dask/base.py in compute(self, **kwargs)
    279         dask.base.compute
    280         """
--> 281         (result,) = compute(self, traverse=False, **kwargs)
    282         return result
    283

~/dask/dask/base.py in compute(*args, **kwargs)
    561         postcomputes.append(x.__dask_postcompute__())
    562
--> 563     results = schedule(dsk, keys, **kwargs)
    564     return repack([f(r, *a) for r, (f, a) in zip(results, postcomputes)])
    565

~/dask/dask/threaded.py in get(dsk, result, cache, num_workers, pool, **kwargs)
     74                 pools[thread][num_workers] = pool
     75
---> 76     results = get_async(
     77         pool.apply_async,
     78         len(pool._pool),

~/dask/dask/local.py in get_async(apply_async, num_workers, dsk, result, cache, get_id, rerun_exceptions_locally, pack_exception, raise_exception, callbacks, dumps, loads, **kwargs)
    485                         _execute_task(task, data)  # Re-execute locally
    486                     else:
--> 487                         raise_exception(exc, tb)
    488                 res, worker_id = loads(res_info)
    489                 state["cache"][key] = res

~/dask/dask/local.py in reraise(exc, tb)
    315     if exc.__traceback__ is not tb:
    316         raise exc.with_traceback(tb)
--> 317     raise exc
    318
    319

~/dask/dask/local.py in execute_task(key, task_info, dumps, loads, get_id, pack_exception)
    220     try:
    221         task, data = loads(task_info)
--> 222         result = _execute_task(task, data)
    223         id = get_id()
    224         result = dumps((result, id))

~/dask/dask/core.py in _execute_task(arg, cache, dsk)
    119         # temporaries by their reference count and can execute certain
    120         # operations in-place.
--> 121         return func(*(_execute_task(a, cache) for a in args))
    122     elif not ishashable(arg):
    123         return arg

~/dask/dask/array/reductions.py in moment_agg(pairs, order, ddof, dtype, sum, axis, computing_meta, **kwargs)
    776
    777     totals = _concatenate2(deepmap(lambda pair: pair["total"], pairs), axes=axis)
--> 778     Ms = _concatenate2(deepmap(lambda pair: pair["M"], pairs), axes=axis)
    779
    780     mu = divide(totals.sum(axis=axis, **keepdim_kw), n, dtype=dtype)

~/dask/dask/array/core.py in _concatenate2(arrays, axes)
    334         return arrays
    335     if len(axes) > 1:
--> 336         arrays = [_concatenate2(a, axes=axes[1:]) for a in arrays]
    337     concatenate = concatenate_lookup.dispatch(
    338         type(max(arrays, key=lambda x: getattr(x, "__array_priority__", 0)))

~/dask/dask/array/core.py in <listcomp>(.0)
    334         return arrays
    335     if len(axes) > 1:
--> 336         arrays = [_concatenate2(a, axes=axes[1:]) for a in arrays]
    337     concatenate = concatenate_lookup.dispatch(
    338         type(max(arrays, key=lambda x: getattr(x, "__array_priority__", 0)))

~/dask/dask/array/core.py in _concatenate2(arrays, axes)
    334         return arrays
    335     if len(axes) > 1:
--> 336         arrays = [_concatenate2(a, axes=axes[1:]) for a in arrays]
    337     concatenate = concatenate_lookup.dispatch(
    338         type(max(arrays, key=lambda x: getattr(x, "__array_priority__", 0)))

~/dask/dask/array/core.py in <listcomp>(.0)
    334         return arrays
    335     if len(axes) > 1:
--> 336         arrays = [_concatenate2(a, axes=axes[1:]) for a in arrays]
    337     concatenate = concatenate_lookup.dispatch(
    338         type(max(arrays, key=lambda x: getattr(x, "__array_priority__", 0)))

~/dask/dask/array/core.py in _concatenate2(arrays, axes)
    338         type(max(arrays, key=lambda x: getattr(x, "__array_priority__", 0)))
    339     )
--> 340     return concatenate(arrays, axis=axes[0])
    341
    342

~/conda/envs/dask-38-np12/lib/python3.8/site-packages/sparse/_common.py in concatenate(arrays, axis, compressed_axes)
   1246         from ._coo import concatenate as coo_concat
   1247
-> 1248         return coo_concat(arrays, axis)
   1249     else:
   1250         from ._compressed import concatenate as gcxs_concat

~/conda/envs/dask-38-np12/lib/python3.8/site-packages/sparse/_coo/common.py in concatenate(arrays, axis)
    157     from .core import COO
    158
--> 159     check_consistent_fill_value(arrays)
    160
    161     arrays = [x if isinstance(x, COO) else COO(x) for x in arrays]

~/conda/envs/dask-38-np12/lib/python3.8/site-packages/sparse/_utils.py in check_consistent_fill_value(arrays)
    437     for i, arg in enumerate(arrays):
    438         if not equivalent(fv, arg.fill_value):
--> 439             raise ValueError(
    440                 "This operation requires consistent fill-values, "
    441                 "but argument {:d} had a fill value of {!s}, which "

ValueError: This operation requires consistent fill-values, but argument 1 had a fill value of 0.0, which is different from a fill_value of 0.23179967316658565 in the first argument.

Environment:

Dask version: master
Sparse version: 0.11.2

Thanks for tracking this @jsignell. Digging into var briefly it looks like the origin of non-zero fill_values stems from
https://github.com/dask/dask/blob/5166be6f15d9d04c6d9948db1b67a7f1b09b1a3e/dask/array/reductions.py#L696
where A is a sparse array with fill_value=0 and u is a NumPy array.
In [42]: sparse.__version__
Out[42]: '0.11.2'

In [43]: s
Out[43]: <COO: shape=(5, 5), dtype=float64, nnz=7, fill_value=0.0>

In [44]: s - np.array([0.123])
Out[44]: <COO: shape=(5, 5), dtype=float64, nnz=7, fill_value=-0.123>

cc @hameerabbasi for visibility

If you manage to get a repro-er with just sparse, do let me know.

Ah, I see. It's best to just do s - np.float64(0.123).

I ran into this issue again yesterday. It turns out to be a pretty big problem when trying to use sparse arrays with dask, in that any kind of reduction will likely fail. @vttrifonov are you still interested in opening a PR with some of the work you have done?

I did come up with a solution and even started working up a PR, but things became hairy and I did not follow up. Let me explain
Short story
There does not seem to be a calculation of central moments which works for both sparse and dense matrices.
Long story
I will give an example with variance (second central moment). It can be computed in two ways

V(X) = E(X-E(X))^2
V(X) = E(X^2) - E(X)^2

The first is what is implemented at the moment in reductions.py and works for dense matrices but not for sparse (the subtraction of mean wreaks havoc on sparsity).
The second works for sparse matrices. In theory, this also works for dense, but the calculation is numerically unstable: if we have a matrix with entries which fluctuate a bit around some very large value the squares lead to overflow and wrong results. Subtracting the mean as in the first method, resolves this because the values that are being squared can be much smaller. There is actually a unit test which tests for this and it fails for the second method.
The situation is easily generalizable to higher moments. See Wiki Central Moment.
As far as I can tell, if you want to offer out-of-the-box moment calculations which work for both dense and sparse matrices, you need both methods such that moment calculations default to 1 for dense matrices and 2 for sparse. Perhaps the user can also select which one to use.
Given all of these “complications” I did not mess submitting a PR, but if there is an interest I can work up a preliminary version (e.g. in a separate sparse_reductions.py file) that then will need to be connected with the rest of dask in a graceful way.


Bring in latest multus image for CVE remediation

Summary and Scope

Fixes: https://jira-pro.its.hpecorp.net:8443/browse/CASMPET-5862

ncn-m001:~ # kubectl get po -n kube-system kube-multus-ds-rq822 -o yaml | grep image.*cni*
    image: artifactory.algol60.net/csm-docker/stable/ghcr.io/k8snetworkplumbingwg/multus-cni:v3.9.3
    image: artifactory.algol60.net/csm-docker/stable/ghcr.io/k8snetworkplumbingwg/multus-cni:v3.9.3
    image: artifactory.algol60.net/csm-docker/stable/ghcr.io/k8snetworkplumbingwg/multus-cni:v3.9.3

ncn-m001:~ # kubectl get po -A | grep multus
kube-system   kube-multus-ds-b69n8               1/1     Running   0          13m
kube-system   kube-multus-ds-c522m               1/1     Running   0          13m
kube-system   kube-multus-ds-csx4j               1/1     Running   0          13m
kube-system   kube-multus-ds-rq822               1/1     Running   0          13m
kube-system   kube-multus-ds-x7zrq               1/1     Running   0          13m

ncn-m001:~ # crictl images | grep multus
artifactory.algol60.net/csm-docker/stable/ghcr.io/k8snetworkplumbingwg/multus-cni            v3.9.1              fa00a8f836cb8       170MB
artifactory.algol60.net/csm-docker/stable/ghcr.io/k8snetworkplumbingwg/multus-cni            v3.9.3              5494352f99256       83.7MB

Issue Type

Bugfix Pull Request

Prerequisites

[x] I have included documentation in my PR (or it is not required)
[x] I tested this on internal system (if yes, please include results or a description of the test)
[x] I tested this on a craystack system (if yes, please include results or a description of the test)
[ ] I tested this on a vagrant environment (if yes, please include results or a description of the test)

Idempotency
Yes
Risks and Mitigations
Low

Just an FYI after looking at these changes.  There is code in Mercury that perhaps can be adapted over to CSM.  That code parses the helm charts and then automatically generates the docker/index.yaml file based on the images in the helm charts.  So in Mercury this PR will only be a one-line change to update the helm chart version in platform.yaml.  See https://github.hpe.com/hpe/hpc-mercury/tree/master/src/baremetal/bin/registry.  In there:

parse_images extracts all the images from the charts
rev_map_images and scripts/rev_map_images.py generate the docker/index.yaml file based on the image list


Error scanning netflix history

I saw there was a patch recently to fix some a scan problem with netflix. I downloaded the release version (The way you guys do releases is confusing as you seem to be updating the old release tag. I think it's the release up-to commit 185e85ce360c097703f20ef68590eb0dd5406ddc).
I load this into FireFox (108.0.2 (64-bit)) as a temp extension
I run the history sync for netflix and it runs for a little while then throws an error.
From the devtools console:
[UTS] Failed to load history.  So if you need me to provide extra info or anything let me know.

I don't see anything wrong with the JSON itself, the format looks exactly like mine. I copied it to my instance manually and the history loaded perfectly fine.

Since it gets to Page 12 of your history and then has an issue out of nowhere, I was wondering if maybe it has something to do with the rate limiter, but I was unable to replicate the issue as the API requests are quite sparse and I can load way past Page 12.
From the error, it seems like it's a network request issue, as it doesn't even get an HTTP status code; so fetching the page fails completely.
Could you check what the Network tab for the extension looks like when it fails? Do you see the request for &pg=12 and is it successful (what's the status and payload)?

Filter on viewingactivity here:

Hey, sorry I forgot I'd tried this and logged this issue.
Pulled the latest code, debugged, ran fine this time. Managed to do like 4 years of history. I don't know if I was hitting a rate limit or if something has changed it the code but its working fine for me now.


Hide monthly option

Part of https://github.com/gratipay/inside.gratipay.com/issues/1160 and includes #4650.
Producing a newsletter is going to be work! Let's not overcommit ourselves.
P.S. I also looked at https://stackoverflow.com/a/39878233 for removing the value from the enum, but it left the enum with size 4 still vs. 3 as I'd expect and it made me not want to muck with pg system tables.

[ ] change base back to master

LGTM, merge when green.

Rebased now that #4650 is in, base changed to master.


Initial pkg/backup test refactoring

This PR is for an initial set of refactoring of the pkg/backup tests.  It defines a test harness struct and replaces the existing resource filtering tests, along with a handful of other test cases.
Definitely want to get feedback on the patterns demonstrated here, as I'll be continuing to refactor additional tests in pkg/backup and pkg/restore along these same lines.

Ha. I was having such trouble understanding this file and now I know why! Yes, I'd go with 'Backupfor this method name andBackupBuilder` for type. Naming it after the thing that it returns is idiomatic Go too.

Backup() works for me, or if folks want it to be consistent across different Builder types, it could be Result() or similar.
Re: struct name - BackupBuilder would result in backup.BackupBuilder when used outside the package, which is not great.
If it's not clear - the purpose of types like this is to make it more succinct to construct objects -- it avoids all of the cruft of Go struct literals.  The pattern of returning the builder from each method makes it easy to just chain method calls together.  It's often useful in tests since this needs to be done over and over again, but can be useful in normal code too.

Thanks for the explanations.
Agree that we should avoid backup.BackupBuilder so Builder works for me.

OK, I think I addressed all the comments so far.


Creating messages database seeds

User story
Who: As a developer
What: I want to have some default messages in the database
Why: so that we can work with those
Implementation details

Add some messages maybe like 10 from different users

this task already finished .


🐛 Parse error for jsonc files

VS Code version
1.90.2
Extension version
2.3.0
Biome version
1.8.3
Operating system

[ ] Windows
[X] macOS
[ ] Linux

Description

It seems like the extension is trying to parse jsonc files as json files.
Steps to reproduce
update biome from 1.7.3 to 1.8.3
Expected behavior
should work
Does this issue occur when using the CLI directly?
No
Logs
`Biome Trace` is empty

It's very difficult to triage the issue without information.
Can you please at least share the contents of the file? Can you check if you can replicate the issue in the playground?

Hi, since this is related to extension, probably can't repro it in the playground.
I think any repo using biome with jsonc file should able to repro it.
e.g. https://github.com/repobuddy/repobuddy/tree/biome-jsonc
pnpm i and open a jsonc file should be sufficient.

What does your editor detect the file as? Are you sure that you don't have some kind of mapping that tells VS Code that the .jsonc extension is a JSON file? I can't reproduce the issue when opening the recommended.jsonc file from your repo.

What does your editor detect the file as? Are you sure that you don't have some kind of mapping that tells VS Code that the .jsonc extension is a JSON file? I can't reproduce the issue when opening the recommended.jsonc file from your repo.

That's strange. Are you on MacOS, and the extension shows that it is using biome 1.8.3?
I don't have setting that map jsonc to json.
It is detected as jsonc

I confirmed the issue also occurs in linux (wsl, ubuntu) and Windows 11

I am sorry @unional, I tried it myself and I can't replicate the issue. So it's possible is something in your internal settings (probably in settings.json). Please provide a minimal reproduction.

It is really weird. Another repo in the same system, same biome 1.8.3.
And that works fine.
Will need to look deeper on what's causing it.
Pasting an image here for reference:

I am going to close this, as we can't replicate it.
Again, I advise you to check your settings.json (project, workspace and user).
Feel free to open it again once you manage to provide a reproduction and some logs from the Daemon (instructions are attached to the template when you create the issue)

I found out what the problem is.
biome parses json as jsonc by default.
Since that would causes false positives,
my presets disable that by default:
{
  "json": {
    // `biome` treat `json` as `jsonc` by default.
    // That causes false positives and should be avoided.
    "parser": {
      "allowComments": false,
      "allowTrailingCommas": false
  }
}

https://github.com/repobuddy/repobuddy/blob/main/packages/biome/recommended.jsonc#L16-L20
Now the problem is,
biome is not parsing json as jsonc by default.
It is actually using the same parser to parse json and jsonc.
i.e. by doing "allowComments": false,
I actually also turn off comment support for jsonc files.
IMO this is a bug.
As for why do you not getting the error,
it is because my top level biome.json is doing extends like this:
{
  "extends": ["@repobuddy/biome/recommended"]
}

You need to run pnpm install first to hook up the node_modules.

Biome doesn't parse JSON files as JSONC files. Did you read this somewhere in our docs? However, some files get a particular treatment, which we document here: https://biomejs.dev/guides/configure-biome/#well-known-files

As for why you don't get the error,
it is because my top level biome.json is doing extends like this

And that's why it's important to provide a reproduction.
Can you please provide a minimal reproduction?  It's possible it is a bug, I haven't understood yet what's the issue and where it is.

https://github.com/repobuddy/repobuddy/tree/biome-jsonc
here is the minimal repro. The top level biome.jsonc only has:
{
	"$schema"<EMAIL_ADDRESS>	"json": {
		// `biome` treat `json` as `jsonc` by default.
		// That causes false positives and should be avoided.
		"parser": {
			"allowComments": false,
			"allowTrailingCommas": false
		}
	}
}

and it fails by itself:

That's not a minimal reproduction, that's a project. The reason why we ask for a minimal reproduction is because we can remove all the noise from a project, and make sure that there aren't other factors at play.

https://github.com/cyberuni/biome-jsonc

I can reproduce the issue seen in the screenshot using the reproduction repo, however I'm moving this to the main repo as it's not an issue with the extension.


Multi NIC integration test

Note: for some reason the internal DNS server (metadata.google.internal)
is not registering the hostname from the secondary NIC so this test only
works if the common subnetwork is setup on the primary NIC.

/ok-to-test

rebase done.

It would be better if the tests did not depend on any existing resources to exist (where it makes sense).
For the multinic tests it would be better to create the networks that test needs (daisy should automatically tear them down at the end of the workflow). I can increase network quota as needed

oh, ok, so then I could add Network creation on daisy. I'll get my hands on it soon.


Leverage TLS between all the components

This prototype should demonstrate how to leverage TLS between all the components and possibly use TLS client auth to limit communication between components.

Attempting to understand the scope of this project. Are you trying to solve the following question?
https://groups.google.com/forum/#!topic/kubernetes-users/ktw3lcjfkKs

@andrewwebber In many ways yes. Check the TLS use case on the home page of this repo. In this case using the unique token each Pod uses vault to generate short-lived unique sets of TLS certs that can be used for either TLS servers or clients, which also support TLS mutual auth between Pods.


use h5netcdf xarray engine

closes #65

Nice, looks good.
It's a shame that there isn't an xarray config option. I did find this but it seems nothing came of it.
Maybe add the change to the changelog?

Thanks for the review. I added changes to the changelog.


cffi.VerificationError: CompileError: command 'gcc' failed with exit status 1

anaconda3/envs/py27t04/include/python2.7 -c _roi_crop.c -o ./_roi_crop.o
In file included from /home/wangzhonghao/anaconda3/envs/py27t04/lib/python2.7/site-packages/torch/utils/ffi/../../lib/include/THC/THC.h:4:0,
from _roi_crop.c:493:
/home/wangzhonghao/anaconda3/envs/py27t04/lib/python2.7/site-packages/torch/utils/ffi/../../lib/include/THC/THCGeneral.h:12:18: fatal error: cuda.h: 没有那个文件或目录
compilation terminated.
Traceback (most recent call last):
File "build.py", line 36, in
ffi.build()
File "/home/wangzhonghao/anaconda3/envs/py27t04/lib/python2.7/site-packages/torch/utils/ffi/init.py", line 184, in build
_build_extension(ffi, cffi_wrapper_name, target_dir, verbose)
File "/home/wangzhonghao/anaconda3/envs/py27t04/lib/python2.7/site-packages/torch/utils/ffi/init.py", line 108, in _build_extension
outfile = ffi.compile(tmpdir=tmpdir, verbose=verbose, target=libname)
File "/home/wangzhonghao/anaconda3/envs/py27t04/lib/python2.7/site-packages/cffi/api.py", line 723, in compile
compiler_verbose=verbose, debug=debug, **kwds)
File "/home/wangzhonghao/anaconda3/envs/py27t04/lib/python2.7/site-packages/cffi/recompiler.py", line 1526, in recompile
compiler_verbose, debug)
File "/home/wangzhonghao/anaconda3/envs/py27t04/lib/python2.7/site-packages/cffi/ffiplatform.py", line 22, in compile
outputfilename = _build(tmpdir, ext, compiler_verbose, debug)
File "/home/wangzhonghao/anaconda3/envs/py27t04/lib/python2.7/site-packages/cffi/ffiplatform.py", line 58, in _build
raise VerificationError('%s: %s' % (e.class.name, e))
cffi.VerificationError: CompileError: command 'gcc' failed with exit status 1

By modifying the header file of make.sh, add the following in front of the file.
export PATH=/usr/local/cuda-8.0/bin${PATH:+:${PATH}}
export CPATH=/usr/local/cuda-8.0/include${CPATH:+:${CPATH}}
export LD_LIBRARY_PATH=/usr/local/cuda-8.0/lib64${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}


Angular and http get json

I always have problem with http request to json files.
jQuery .ajax or .getJson work everytime. but with Angular you have to try multiples ways until you may finally find the right one to get that json file.
Alway the same thing.
With Angular you have to get used to see message like:

XMLHttpRequest cannot load
has been blocked by CORS policy
No 'Access-Control-Allow-Origin' header is present on the requested resource
Possibly unhandled rejection

I just did a php fille with json header and callback and it's alway work the first time with jQuery, but Angular, you have to try multiples bizarre things to get it work, 2 hours on it and it doesn't work, but 5 minutes with jQuery and it's done.

Closing since this is not actionable. Happy to reopen and investigate if you can provide a way to reproduce the problem.
If this is a usage problem (and not an AngularJS issue/bug), you can use one of the general support channels.
(FWIW, I've never heard of people having difficulties fetching JSON data with AngularJS. In fact there have been complains about it not being straight-forward to send/receive non-JSON data. That said, we are always interested in improving developer ergonomics if you can point out specific, reproducible problems/difficulties.)


Setting Up Syntex is in "Settings" > "Organizational Knowledge", not Files and Content

the document at this section:
https://docs.microsoft.com/en-us/microsoft-365/contentunderstanding/set-up-content-understanding#to-set-up-sharepoint-syntex
should say organisational knowledge, and not Files and Content, when you are about to setup Automate content understanding

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

ID: 215aae2b-deef-07f9-03cf-009006b8cabb
Version Independent ID: bb7fd949-ff1a-dc43-d454-3fa2c4d938db
Content: Set up SharePoint Syntex
Content Source: microsoft-365/contentunderstanding/set-up-content-understanding.md
Product: microsoft-365-enterprise
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

@davidsrhans Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/3467. Once the author approves the changes will be live in 48 hours.
Thanks
Sri

@msbemba Thank you very much for the contribution and sharing this explanation. @davidsrhans Hope the comment added in PR  is helpful for you. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


armv6 support

Previously i did some changes personally by changing to alpine images (debian not supporting armv6 anymore), local build, and it works on this cpu. now that this repo have officially added alpine images, please add support to armv6 cpu.
Tested using RPi zero W and running fine.
edit: on second tought, it seems that bcrypt and sqlite is not build when using github CI, thus its server is "not set up correctly"

If you can get the image build to work on GitHub Actions, please open a PR to add it!

This has been added in #182, thanks for sorting it out and cleaning up the actions @intiplink!


Electricity to/from grid (year 1) does not match lifetime

It's a bit confusing that hourly kWh and lifetime kW "electricity to/from grid" are different in these results for the MiniGrid AC case of the DC_AC_Connected.sam test file -- lifetime hourly is zero for all time steps, as I think it should be due to the grid outage for all time steps (this is true in this branch and SAM 2021.12.02 r1):

Originally posted by @cpaulgilman in https://github.com/NREL/ssc/issues/780#issuecomment-1083691218

A few notes prior to punting this to the patch: the year 1 variables in question are set in utility rate 5. The result of the grid outage computations in cmod_grid is that gen gets exported to the grid, leading to this scenario racking up net metering credits:

This is incorrect, as net metering credits cannot be earned when the grid is down. Proposed solution involves adding grid_outage as a variable to utility rate 5.


⚠ Bofrost.de has degraded performance

In 8bdde81, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1039 ms

Resolved: Bofrost.de performance has improved in 0ae5898 after 6 minutes.


Coordinates of Points in Inspector [Improvement]

As is, when I click on a point, I have no way of knowing its coordinates.
Could this be integrated with the Unity Inspector, so that these points can be moved around by changing the x, y, z coordinates in the Inspector (just like one can for everything else in Unity)?

I found out that this was added in the develop branch.

This has now been added to the main branch. Clicking on a point will now bring up a vector3 field in the inspector. (Thanks to Keenan)


Updating to 5.13.1

@matzew I think npm-shrinkwrap needs to be updated as well ;)

@matzew If you rebase with master you should be able to generate the skrinkcrap with rm -rf node_modules && npm cache clean && npm install --production && npm shrinkwrap

@sebastienblanc of course, that does not work!
the npm "tool" just drives me nuts

@sebastienblanc @odra looks like the pre scripts are not Mac friendly ?
getting:
rm -rf node_modules/ && npm i --production && npm i<EMAIL_ADDRESS>&& npm cache clean && npm shrinkwrap
npm WARN package.json<EMAIL_ADDRESS>No repository field.

><EMAIL_ADDRESS>preinstall /Users/matzew/Work/FeedHenry/TEMPLATES/wfm-auth
> chmod +x scripts/preinstall.sh && scripts/preinstall.sh

npm ERR! code 1

@matzew It could be an issue with npm (I was able to run it in my mac), could you please try to run the command ´npm install -g node-pre-gyp´?
Also, are you using node with nvm or did you install it with homebrew?

nvm --version
0.31.1
the npm install -g node-pre-gyp worked fine :-)
JOY! :)
On Fri, Jul 1, 2016 at 10:09 PM, Leonardo Rossetti<EMAIL_ADDRESS>
wrote:

@matzew https://github.com/matzew It could be an issue with npm (I was
able to run it in my mac), could you please try to run the command ´npm
install -g node-pre-gyp´?
Also, are you using node with nvm or did you install it with homebrew?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/feedhenry-raincatcher/raincatcher-demo-cloud/pull/9#issuecomment-230036905,
or mute the thread
https://github.com/notifications/unsubscribe/AAJnzjZR__opnBp43sbxZgkAV_4DlCYxks5qRXPggaJpZM4JC6Gs
.

--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf

but, yeah... the my "rm -rf node_modules && npm cache clean && npm install
--production && npm shrinkwrap" continues to fail!
pure joy!
On Fri, Jul 1, 2016 at 11:01 PM, Matthias Wessendorf<EMAIL_ADDRESS>wrote:

nvm --version
0.31.1
the npm install -g node-pre-gyp worked fine :-)
JOY! :)
On Fri, Jul 1, 2016 at 10:09 PM, Leonardo Rossetti <
<EMAIL_ADDRESS>wrote:

@matzew https://github.com/matzew It could be an issue with npm (I was
able to run it in my mac), could you please try to run the command ´npm
install -g node-pre-gyp´?
Also, are you using node with nvm or did you install it with homebrew?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/feedhenry-raincatcher/raincatcher-demo-cloud/pull/9#issuecomment-230036905,
or mute the thread
https://github.com/notifications/unsubscribe/AAJnzjZR__opnBp43sbxZgkAV_4DlCYxks5qRXPggaJpZM4JC6Gs
.

--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf

--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf

@matzew You need to remove the shrinkwrap file before  generating a new one, so the correct command order would be:
rm -rf node_modules && npm cache clean && rm npm-shrinkwrap.json && npm install --production && npm shrinkwrap

Ok, updated this:
alias shrinkcrap='rm -rf node_modules && npm cache clean && rm npm-shrinkwrap.json && npm install --production && npm shrinkwrap'

😄
thanks, @odra