[Offline base maps] Add support for deleting areas

EDITED: We use reference counting to remove tile sources from the device when offline areas are deleted.
It also updates the offline area viewer to trigger deletions upon clicking the remove button.
I verified this behavior using the device file explorer and stetho--everything seems to be removed correctly.
Also fixes #573

@gino-m, @shobhitagarwal1612, @dturner, this is ready for a review! If anyone has the bandwidth

Added a few nits, but zooming out a sec:
Could finding non-overlapping areas be achieved by using either reference counting? i.e., increment a counter when a region is added, then decrement when the region is deleted, deleting tiles with count of zero? It should reduce the amount of code needed to maintain data consistency. Wdyt?

That would be a LOT simpler and I think it would work just fine. Thanks, Gino! I can revert and make this change instead.

Added a few nits, but zooming out a sec:
Could finding non-overlapping areas be achieved by using either reference counting? i.e., increment a counter when a region is added, then decrement when the region is deleted, deleting tiles with count of zero? It should reduce the amount of code needed to maintain data consistency. Wdyt?

That would be a LOT simpler and I think it would work just fine. Thanks, Gino! I can revert and make this change instead.

@scolsen I had a thought while falling asleep last night (🤔 ) - alternatively, could we just load all the tiles and tilesets into memory and identify which ones need to be deleted? There would rarely be more than a few hundred tiles imo.. wdyt?

Added a few nits, but zooming out a sec:
Could finding non-overlapping areas be achieved by using either reference counting? i.e., increment a counter when a region is added, then decrement when the region is deleted, deleting tiles with count of zero? It should reduce the amount of code needed to maintain data consistency. Wdyt?

That would be a LOT simpler and I think it would work just fine. Thanks, Gino! I can revert and make this change instead.

@scolsen I had a thought while falling asleep last night (🤔 ) - alternatively, could we just load all the tiles and tilesets into memory and identify which ones need to be deleted? There would rarely be more than a few hundred tiles imo.. wdyt?

I think that's valid too, but I do think reference counting will be simpler. W/ reference counting, the approach is roughly:
delete(area) -> getIntersectingTiles(area) -> filter(refCount <= 1) -> deleteTiles(filteredTiles)

Whereas I think the other approach requires:
delete(area) -> getAllAreas() -> map(lambdaArea : getIntersectingTiles(area)) {we now have a list of lists of tiles} -> flatten() -> filter(singleInstance {filter out any tiles that appear n > 1}) -> filter(tile isMember of getIntersectingTiles(area))

which I think will be more complicated. Unless there's a really strong reason for us to avoid adding another field in the DB I'd prefer the reference counting approach for its simplicity. Prior to this PR, there is no relationship between tiles+areas encoded anywhere, it's completely determined by the getIntersectingTiles() :: Area -> [Tile] function. I think because of that the in-memory approach is trickier to get right and possibly more brittle if we wind up changing the way we handle certain things.

which I think will be more complicated. Unless there's a really strong reason for us to avoid adding another field in the DB I'd prefer the reference counting approach for its simplicity. Prior to this PR, there is no relationship between tiles+areas encoded anywhere, it's completely determined by the getIntersectingTiles() :: Area -> [Tile] function. I think because of that the in-memory approach is trickier to get right and possibly more brittle if we wind up changing the way we handle certain things.

I agree. It also obviously scales better; this may be relevant if we end up with a dataset with many smaller titles (e.g., very high-res). Reference-counting SGTM!

@gino-m sorry for the delay--ready for another look! This also fixes #573, so two birds one stone on this one.

@gino-m ready for another looksee!

@scolsen Gentle ping! :)

@gino-m finally fixed, sorry for the delay!

A few readability suggestions, otherwise looks great! Note that build was failing on last CI run, but could have been do to the previous bad merge.

Yep, defining a function twice (the bad merge) is a compile time failure.

@gino-m one more check?!


Deploy and setup CD

We need to have a quick and efficient way of deploying multiformats.io when it changes.

we now have one thanks to the shiny makefile that is shared across all the websites! \o/

@diasdavid wait? How is the CD setup? Think you're confusing things here, this issue is referring to continuously deploying the website (on every commit, automatically deploy the website)


[AlwaysOnTop] Round corners on Windows 11

Summary of the Pull Request
https://user-images.githubusercontent.com/8949536/176469773-41a5cbb6-61d3-4065-80cc-b73377670efc.mp4

PR Checklist

[x] Closes: #15284
[ ] Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
[ ] Tests: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Dev docs: Added/updated
[ ] New binaries: Added on the required places

[ ] JSON for signing for new binaries
[ ] WXS for installer for new binaries and localization folder
[ ] YML for CI pipeline for new test projects
[ ] YML for signed pipeline

[ ] Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

Validation Steps Performed

How could anybody not like this?

How could anybody not like this?

Some people disabled rounded corners on Windows 11 manually.

Some people disabled rounded corners on Windows 11 manually.

Disabled corners are taken into account, as well as disabling while snapping to FZ zone.

Any reason for this not to go in?

Any reason for this not to go in?

I'm still getting a build to review on Windows 11. Close to reviewing it, though.


BugID: #1872:Add color sorter demo

[Detail]
Requirement description:
When objects of different colors are mixed together, separate them according to their colors is difficult.
Solution:
Based on esp32 board,we use tcs34725 color sensor to sort different color and we can see the statistic data on web application.
[Verified Cases]
Build Pass: py_engine_esp32_demo
Test Pass: esp32 demo

感谢提交 Pull Requests！
Thanks for submitting a pull request.

Security Check : 1315bfa2be70ef7bfb5d46a9bbb6ae71ad25b546

auto build success,number:248


⚠ Bofrost.ch has degraded performance

In b163d2f, Bofrost.ch (https://www.bofrost.ch) experienced degraded performance:

HTTP code: 200
Response time: 1373 ms

Resolved: Bofrost.ch performance has improved in 3edc657.


Cloudimage build not saving images to registry

What happened:
when i build cloudimage with dashboard, the dashboard docker image was pulled BUT NOT saved to registry:
here's the build log:
root@DESKTOP-QUTIMPM:~/sealer/cloudimage# sealer build -t mykubernetes:v1.19.8 .
2022-03-22 14:39:44 [INFO] [build_image.go:131] start to check the middleware file
2022-03-22 14:39:44 [INFO] [build_image.go:89] run build layer: COPY dashboard.yml manifests
2022-03-22 14:39:44 [INFO] [build_image.go:89] run build layer: CMD kubectl apply -f manifests/dashboard.yml
2022-03-22 14:39:44 [INFO] [build_image.go:122] exec all build instructs success
Pulling image: docker.io/kubernetesui/dashboard:v2.2.0
Pulling image: docker.io/kubernetesui/metrics-scraper:v1.0.6
48d79e554db6: Download complete
47a33a630fb7: Download complete
5c4ee6ca42ce: Download complete
7cccffac5ec6: Download complete
62498b3018cb: Download complete
7f06704bb864: Download complete
Status: images save success
2022-03-22 14:42:42 [WARN] [build_image.go:220] no rootfs diff content found
2022-03-22 14:42:45 [INFO] [build_image.go:206] save image mykubernetes:v1.19.8 success
2022-03-22 14:42:45 [INFO] [lite_builder.go:107] save image mykubernetes:v1.19.8 to image system success
root@DESKTOP-QUTIMPM:~/sealer/cloudimage# sealer images
+------------------------------------------------------------------+----------------------+---------------------+----------+
|                             IMAGE ID                             |      IMAGE NAME      |       CREATE        |   SIZE   |
+------------------------------------------------------------------+----------------------+---------------------+----------+
| 52c3b10849c852649e66c2f7ed531f05bd97586ab61fa2cc82b4e79d80484b82 | kubernetes:v1.19.8   | 2022-03-20 12:27:48 | 787.81MB |
| 98f470b1364b00b07d706adee478a7a6e224ffcc1854081576479da7218c14b1 | mykubernetes:v1.19.8 | 2022-03-22 14:42:45 | 787.82MB |
+------------------------------------------------------------------+----------------------+---------------------+----------+

and the kubefile:
root@DESKTOP-QUTIMPM:~/sealer/cloudimage# cat Kubefile
FROM kubernetes:v1.19.8
COPY dashboard.yml manifests
CMD kubectl apply -f manifests/dashboard.yml

What you expected to happen:
dashboard images saved to registry
Anything else we need to know?:
Environment:

sealer version (use sealer version): v0.7.1
OS (e.g: cat /etc/os-release): WSL2
Kernel (e.g. uname -a): Linux 4.19.84-microsoft-standard x86_64 x86_64 x86_64 GNU/Linux

@kakaZhou719 the image size is same..

@glongzh ,seems the container images layer not save while.  does your host support overlay2 ?show  result of cmd lsmod | grep overlay

@glongzh ,seems the container images layer not save while. does your host support overlay2 ?show result of cmd lsmod | grep overlay

nope, ubuntu in wsl2 show empty for lsmod | grep overlay and overlay mod can not be loaded...
root@DESKTOP-QUTIMPM:~/sealer# lsmod | grep overlay
root@DESKTOP-QUTIMPM:~/sealer# modprobe overlay
modprobe: FATAL: Module overlay not found in directory /lib/modules/4.19.84-microsoft-standard

we use overlay2 mechanism  to collect changes of each layers, if no overlay2, will save image failed.

OK. It's better to add this system prerequisite to the document.

OK. It's better to add this system prerequisite to the document.

yes, i will add this prerequisite later.

#1291 fix this


Fix multielements

Fixes #973 and some additional bugs introduced sometime before #955.
Tests:

Draw and resize every shape
Draw and resize and rotate an arrow and line (2 point)
Draw and resize mutielement lines and arrows
Export preview
Save file
Reload file, resize curves
Resize mutielement line in multiplayer
Load the 1000 square json, draw a curve, UX is smooth
Alt-drag works. Shift click works.

The UX isn't perfect -- I think we should flip the element if you switch to negative width -- but it's better than the previous behavior.

This fixes #661

#661 also deals with negative resizing. If we close that one, we should open a new one for that feature (and probably close https://github.com/excalidraw/excalidraw/pull/759 since this won't be usable anymore I think).


fix: RetrofitFragment "Log with User Info:" button now uses correct inputs

Both buttons in the RetrofitFragment use the "Log contributors of:" editText fields instead of using the fields next to each button respectively.

@marukami much appreciate the fixes you sent my way. Cheers!


Make static site for the list

In issue #36, @jhnsntmthy suggested making a static website for this list. We can discuss that here.
I would like it if it used Jekyll without any plugins so that we can just push to GitHub without build it host it on GitHub Pages.

If you would like to use Jekyll plugins, I would be happy to host it on Aerobatic for you. We could use any of the free CI services to build the site.

I'd rather not use plugins. And I can't think of any reason why we would need one. Thanks though.


Dedicated sub-site for Copilot chat

Provide additional content on Copilot chat. It should include:

What it does
How it works
And how to extend it

Copilot chat is retired


[Bug] Profile view broken

Getting user profile view gets the wrong ID from profile.

The IDs for profiles are either reversed or offset by 1 (trying to get admin profile gets me id-1 with id 1.)

Sorry Django was strange, it now works (after 3d database clean)


Delete specification/timeseriesinsights/data-plane/Microsoft.TimeSeri…

…esInsights/preview directory

Removing Azure Time Series Insights Preview API from docs as we have GA API since July 2020 and preview API will be depreciated.

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[x] Other, please clarify
Removing Preview API

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[ ] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Hi @Sandip-Raiyani. Preview swaggers that are no longer supported can be removed 90 days after the GA became available.

@tjprescott Yes, we can remove this now since our service is available in GA since July 2020

@JeffreyRichter this service has been GA for a year. Could you approve the breaking change to remove this Swagger?

The swagger has problems with it; look here: https://github.com/Azure/azure-rest-api-specs/pull/15394/checks

@JeffreyRichter this PR is simply removing swagger. There are no changes except deleting the old preview Swagger.

I can't add the"approved-breaking change" label because there is no breaking change.

Hmm... interesting point. Even the logs say there's no breaking change. I created an issue in their repo:
https://github.com/Azure/openapi-diff/issues/212
@lmazuel, can you override the CI here and merge this change?

It is possible that it is not allowing since public docs might be referring it? Error doesn't show that reason though. Also, doc build seems to be succeeded.
https://docs.microsoft.com/en-us/rest/api/time-series-insights/dataaccess(preview)/model-settings
Line 5456
https://github.com/Azure/azure-docs-rest-apis/blob/master/mapping.json
I have created a PR there as well to remove it from Public Docs
https://github.com/Azure/azure-docs-rest-apis/pull/3905

Based on discussion, I can force merge it. Ping me on Teams if we need to revert the deletion.


Use noop meter provider when otel metrics are disabled

See https://github.com/synadia-io/nex/pull/112


Nintendo switch

Describe the feature
Any chance of this being built for Nintendo switch
with a controller navigable interface?
Describe the use case
No response
Additional information
No response

Probably not going to happen as the chromium browser is not ported to the switch. There is barely a functioning webbrowser available so the chances are very low at the moment.


Create Counting_Squares.py

added the program Counting_Squares.py

Have you read the Contributing Guidelines on Pull Requests?
Yes
Description
Added a program to python/cp which calculates the total number of squares present in a grid, including all the axes.
(Write your answer here.)
Checklist

[ ✔  ] I've read the contribution guidelines.
[ ✔  ] I've checked the issue list before deciding what to submit.
[ ✔  ] I've edited the README.md and link to my code.

Related Issues or Pull Requests
issue : #2340

Duplicated PR. Here is the one in review https://github.com/TesseractCoding/NeoAlgo/pull/2501


INFRA-132389 Enable GHA

Enable git hub actions

Hi, our team needs the Spring boot 3 support PR which is communicated to be blocked due to this Pull Request, is there an ETA for this one?


Store secrets outside of Terraform code and have the Lambdas pull them in

Based on https://github.com/domain-protect/domain-protect/pull/199
We should move the management and configuration of secrets used by the Lambdas to call third-party servies outside of the Terraform code and state. There are a couple of options such as 'AWS Secrets Manager' and 'AWS Systems Manager Parameter Store' with the latter being the simpler and cheaper option.
This would introduce a new resource eg. aws_ssm_parameter and also require code changes to pull the secret on function init.

good idea


dependency of dependency cannot be inlined

Describe the bug
I'm using vue-echarts which depends on echarts in my vite project.
I've add echarts in deps.inline but vitest still throws the following error:
SyntaxError: Unexpected token 'export'
 ❯ Object.compileFunction https:/vitest-dev-vitest-fhmvl9.w.staticblitz.com/blitz.ad37e903755d89e0f5d9999e69be73a0c6cb6bcc.js:6:341311
 ❯ wrapSafe https:/vitest-dev-vitest-fhmvl9.w.staticblitz.com/blitz.ad37e903755d89e0f5d9999e69be73a0c6cb6bcc.js:6:218270
 ❯ Module._compile https:/vitest-dev-vitest-fhmvl9.w.staticblitz.com/blitz.ad37e903755d89e0f5d9999e69be73a0c6cb6bcc.js:6:218638
 ❯ Module._extensions..js https:/vitest-dev-vitest-fhmvl9.w.staticblitz.com/blitz.ad37e903755d89e0f5d9999e69be73a0c6cb6bcc.js:6:219666
 ❯ Module.load https:/vitest-dev-vitest-fhmvl9.w.staticblitz.com/blitz.ad37e903755d89e0f5d9999e69be73a0c6cb6bcc.js:6:217692
 ❯ Module._load https:/vitest-dev-vitest-fhmvl9.w.staticblitz.com/blitz.ad37e903755d89e0f5d9999e69be73a0c6cb6bcc.js:6:215263

Module /home/projects/vitest-dev-vitest-fhmvl9/node_modules/echarts/core.js:20 seems to be an ES Module but shipped in a CommonJS package. You might want to create an issue to the package "echarts" asking them to ship the file in .mjs extension or add "type": "module" in their package.json.

As a temporary workaround you can try to inline the package by updating your config:

// vitest.config.js
export default {
  test: {
    deps: {
      inline: [
        "echarts"
      ]
    }
  }
}

if I add 'vue-echarts' in deps.inline, another error is thrown:
Error: ENOENT: no such file or directory, open<EMAIL_ADDRESS> ❯ Object.openSync ../../../node:fs:585:3
 ❯ readFileSync ../../../node:fs:453:35
 ❯ ../../../file:/D:/Solutions/online_monitor_front/node_modules/.pnpm/vitest@0.14.1_jsdom@19.0.0+sass@1.32.13/node_modules/vitest/dist/chunk-vite-node-externalize.d492e389.mjs:9042:26
 ❯ printStack ../../../file:/D:/Solutions/online_monitor_front/node_modules/.pnpm/vitest@0.14.1_jsdom@19.0.0+sass@1.32.13/node_modules/vitest/dist/chunk-vite-node-externalize.d492e389.mjs:9127:32
 ❯ printError ../../../file:/D:/Solutions/online_monitor_front/node_modules/.pnpm/vitest@0.14.1_jsdom@19.0.0+sass@1.32.13/node_modules/vitest/dist/chunk-vite-node-externalize.d492e389.mjs:9040:3
 ❯ processTicksAndRejections ../../../node:internal/process/task_queues:96:5
 ❯ async DefaultReporter.printTaskErrors ../../../file:/D:/Solutions/online_monitor_front/node_modules/.pnpm/vitest@0.14.1_jsdom@19.0.0+sass@1.32.13/node_modules/vitest/dist/chunk-vite-node-externalize.d492e389.mjs:7618:7
 ❯ async DefaultReporter.reportSummary ../../../file:/D:/Solutions/online_monitor_front/node_modules/.pnpm/vitest@0.14.1_jsdom@19.0.0+sass@1.32.13/node_modules/vitest/dist/chunk-vite-node-externalize.d492e389.mjs:7564:7
 ❯ async DefaultReporter.onFinished ../../../file:/D:/Solutions/online_monitor_front/node_modules/.pnpm/vitest@0.14.1_jsdom@19.0.0+sass@1.32.13/node_modules/vitest/dist/chunk-vite-node-externalize.d492e389.mjs:7455:5
 ❯ async DefaultReporter.onFinished ../../../file:/D:/Solutions/online_monitor_front/node_modules/.pnpm/vitest@0.14.1_jsdom@19.0.0+sass@1.32.13/node_modules/vitest/dist/chunk-vite-node-externalize.d492e389.mjs:8245:5
 ❯ async Vitest.report ../../../file:/D:/Solutions/online_monitor_front/node_modules/.pnpm/vitest@0.14.1_jsdom@19.0.0+sass@1.32.13/node_modules/vitest/dist/chunk-vite-node-externalize.d492e389.mjs:10631:5
 ❯ async ../../../file:/D:/Solutions/online_monitor_front/node_modules/.pnpm/vitest@0.14.1_jsdom@19.0.0+sass@1.32.13/node_modules/vitest/dist/chunk-vite-node-externalize.d492e389.mjs:10468:7
 ❯ async Vitest.runFiles ../../../file:/D:/Solutions/online_monitor_front/node_modules/.pnpm/vitest@0.14.1_jsdom@19.0.0+sass@1.32.13/node_modules/vitest/dist/chunk-vite-node-externalize.d492e389.mjs:10472:12
 ❯ async Vitest.start ../../../file:/D:/Solutions/online_monitor_front/node_modules/.pnpm/vitest@0.14.1_jsdom@19.0.0+sass@1.32.13/node_modules/vitest/dist/chunk-vite-node-externalize.d492e389.mjs:10399:5
 ❯ async startVitest ../../../file:/D:/Solutions/online_monitor_front/node_modules/.pnpm/vitest@0.14.1_jsdom@19.0.0+sass@1.32.13/node_modules/vitest/dist/chunk-vite-node-externalize.d492e389.mjs:11133:5

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: {
  "code": "ENOENT",
  "errno": -4058,
  "path"<EMAIL_ADDRESS>  "syscall": "open",
}

Reproduction
stackblitz.com/edit/vitest-dev-vitest-fhmvl9
System Info
System:
    OS: Windows 10 10.0.22000
    CPU: (6) x64 Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz
    Memory: 5.41 GB / 15.86 GB
  Binaries:
    Node: 16.15.1 - D:\Program Files\nodejs\node.EXE
    Yarn: 1.22.17 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 8.11.0 - D:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22000.120.0), Chromium (102.0.1245.33)
    Internet Explorer: 11.0.22000.120
  npmPackages:
    @vitejs/plugin-legacy: ^1.8.2 => 1.8.2
    vite: ^2.9.10 => 2.9.10
    vitest: ^0.14.1 => 0.14.1

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

This is not a bug, that you cannot inline dependency of a dependency. You need to inline both. Explanation:
When dependency is not inlined, it will use native import syntax, so we cannot intercept it afterwards. So, if the main dependency is not inlined, we don't control any import inside.
When you inline both, you still have an error, because vue-echarts is using require to import echarts, but echarts is shipped with ESM - this is the error in echarts (it should provide both CJS and ESM), or alternatively vue-echarts could also provide a valid ESM entry. More on that here: https://github.com/sheremet-va/dual-packaging (TLDR: vue-charts points to cjs entry that uses require - and we don't intercept it, it should provide a valid "exports" field in package.json)
The other error is interesting. Something failed, and we try to get a stacktrace, but for some reason file doesn't exist? Can you open a separate issue for this one? I think we are receiving the path to source mapped location, but location doesn't exist.

If you need an immediate solution, you can also add this to your vite config (deps should still be inlined):
  resolve: {
    mainFields: ["module"],
  },

But, please, open an issue with vue-charts and echarts to fix their exports field and build pipeline.

Closing issue, since the problem is with upstream packages.

Thanks @sheremet-va !
For those who meet similar issues from upstream packages, you can use https://github.com/milahu/patch-package to modify package.json in node_modules  while waiting for maintainers to fix the bug.

I solved this problem by following a few other threads and installing a dev dependency, "https://www.npmjs.com/package/@originjs/vite-plugin-commonjs"
Next I modified vitest.config.js as follows:
export default defineConfig({
  test: {
    environment: 'jsdom',
    deps: {
      inline: ['vue-echarts', 'echarts']
    },
    include: ['src/**/*.spec.js']
  },
  plugins: [
    vue({
      template: { transformAssetUrls }
    }),
    jsconfigPaths(),
    viteCommonjs(['vue-echarts'])
  ]
})

Hope it helps.


chore: update Uptrace version

The new version should perform better in this particular benchmark.
Also, enabled LZ4 compression in the official Go client example for more fairness.

Also, enabled LZ4 compression in the official Go client example for more fairness.

Should be disabled in all clients

$ hyperfine ch-bench-faster ch-bench-uptrace
Benchmark 1: ch-bench-faster
  Time (mean ± σ):     628.7 ms ± 129.6 ms    [User: 112.8 ms, System: 354.4 ms]
  Range (min … max):   429.6 ms … 841.2 ms    10 runs

Benchmark 2: ch-bench-uptrace
  Time (mean ± σ):     22.964 s ±  0.259 s    [User: 21.803 s, System: 1.381 s]
  Range (min … max):   22.557 s … 23.313 s    10 runs

Summary
  'ch-bench-faster' ran
   36.52 ± 7.54 times faster than 'ch-bench-uptrace'

$ /usr/bin/time -v ch-bench-uptrace
22.681s 500000000
        Command being timed: "ch-bench-uptrace"
        User time (seconds): 21.73
        System time (seconds): 1.32
        Percent of CPU this job got: 101%
        Elapsed (wall clock) time (h:mm:ss or m:ss): 0:22.79
        Average shared text size (kbytes): 0
        Average unshared data size (kbytes): 0
        Average stack size (kbytes): 0
        Average total size (kbytes): 0
        Maximum resident set size (kbytes): 6933544
        Average resident set size (kbytes): 0
        Major (requiring I/O) page faults: 0
        Minor (reclaiming a frame) page faults: 1749331
        Voluntary context switches: 11701
        Involuntary context switches: 125
        Swaps: 0
        File system inputs: 0
        File system outputs: 0
        Socket messages sent: 0
        Socket messages received: 0
        Signals delivered: 0
        Page size (bytes): 4096
        Exit status: 0

5G to 6GB RSS, 20x to 36x ratio (probably due to LZ4 which should be disabled by default)

I've removed the change the official CH client.

5G to 6GB RSS, 20x to 36x ratio (probably due to LZ4 which should be disabled by default)

It looks like you did not recompile the uptrace binary. Locally I see
ch-bench-official git:(fix/update-uptrace) go run .
7.402s 500000000

ch-bench-uptrace git:(fix/update-uptrace) go run .
6.671s 500000000

Yes, now it is much faster, great job :zap:


Can't find core javascript libraries

For some reason my atom-typescript highlights lines containing core javascript libraries like Number, Math, and window saying they aren't available. Is there a way to get typescript to recognize them?

I figured out my error. I had to set noLib: false. Sorry.


citibike_jinja example doesn't work

When I try to include the create_schema.j2 i get the following error:
Traceback (most recent call last):
File "/usr/local/bin/schemachange", line 8, in
sys.exit(main())
File "/usr/local/lib/python3.8/site-packages/schemachange/cli.py", line 865, in main
deploy_command(config)
File "/usr/local/lib/python3.8/site-packages/schemachange/cli.py", line 528, in deploy_command
content = jinja_processor.render(jinja_processor.relpath(script['script_full_path']), config['vars'], config['verbose'])
File "/usr/local/lib/python3.8/site-packages/schemachange/cli.py", line 132, in render
content = template.render(**vars).strip()
File "/usr/local/lib/python3.8/site-packages/jinja2/environment.py", line 1301, in render
self.environment.handle_exception()
File "/usr/local/lib/python3.8/site-packages/jinja2/environment.py", line 936, in handle_exception
raise rewrite_traceback_stack(source=source)
File "/builds/pts/data-products/bi-products/dwh/01_snowflake/schemachange/V1.3__deploy_addition_api_at.sql", line 3, in top-level template code
{% extends 'create_stage.j2' %}
jinja2.exceptions.TemplateNotFound: create_stage.j2
I would like to add files from modules wich are placed in a folder structure:

modules

db

tables

tabA.sql

Hello @romaain
Thank you for raising the issue with the demo example.

What command did you execute at the command line ?
Could you take a look at #110 to look at how the modules option is used?

Let us know if you are able to rerun the code based on the issue referred above.

This may help: https://github.com/HadesSnowflake/graupel/pull/1155


Trim not working

As a follow on to https://github.com/jaredpalmer/formik/issues/473
Well here is an example:
https://codesandbox.io/s/2jo7vox1n0
I have strict set to false. The validation for firstname detects whitespace and show a message but I don't want that, I want it to just trim the string and not show any message.

It seems a few folks are facing this issue, including me.

Also, check out format and parse.

Amazing update @johnrom
Until that is in, I've created a small set of helpers to solve this issue outside of Yup and Formik: https://www.npmjs.com/package/formik-yup

Here: https://github.com/jaredpalmer/formik/issues/473#issuecomment-593587854

@vleandersson, your answer got me closer to a solution but I found that the field validator was validating against the original input value - not the trimmed value.
What I discovered, is that you need to invoke handleBlur(event) before carrying out any modifications to the input value, otherwise Formik will disregard any value set via setFieldValue and use the original event value if handleBlur(event) is called after.
Example:
<input
  {...field}
  onBlur={(event) => {
    handleBlur(event);
    const trimmedValue = (event.target.value || '').replace(/\s+/g, '');
    setFieldValue(field.name, trimmedValue);
  }}
  id="name"
  disabled={isSubmitting}
  type="text"
  placeholder="Your name"
/>


make closing multiple tabs easier

it's really hard to close multiple tabs because the tabs don't have equal width (not that they should, tho)

Duplicate of #290. Let's monitor the resolution on that issue.


Added searching and sorting algorithms

Hello! I have added two codes on sorting algorithms. Kindly check them and consider for merging, thank you! Would love to contribute more.


Conflicts with vim-go

when I click ctrl + ] cmdline shows no room for queue

Startify doesn't map <c-]> and vim-go shouldn't set mappings for buffers where the filetype is not go.

It really got some problems with vim-go.
no room for queue and vim-go: no file information for file:///da nte/quic-go/stream.go

Why are you using <c-]> anyway? This plugin doesn't have such a mapping.


Wrong calculation of 7% chance for double artifacts

I am currently writing my own artifact sim with probabilities in preparation for my math and computer science finals and happened to stumble across your project. I checked the files and noticed that you calculate the chance for getting the desired artifact in one run (20 resin) the following way:
chance = 1 - (1- chance) * (1 - 0.07 * chance)
This confused me, as I first calculated the chance manually using chance = chance * 1.07 and got a different result than you, so I ran a simulation to confirm the matter:
I created 100 million random artifacts with a 7% chance to create two at once and logged the amount of Flowers I got: 21400206
This proves that the chance for getting an artifact with chance c in one run (20 resin) with a chance of 7% for double artifacts is indeed chance = chance * 1.07 instead of the formula you used.
This new formula can also be proven the following way:
0.93 * chance + 0.07 * (2*chance*(1-chance)+2*(chance)²)

93% chance to get 1 artifact (0.93*chance)
7% chance to get 2 artifacts (0.07*...)
-> getting at least one desired artifact from the drops: 2 * chance * (1-chance) + 2 * chance²
Simplifying this formula leads to chance = chance * 1.07 and calculates a probability of 21.4% for the aforementioned example (with chance = 0.2)

I have used * 1.07 originally, but then changed it.
https://www.reddit.com/r/Genshin_Impact/comments/p9mdgk/comment/ha0z1a2/?utm_source=share&utm_medium=web2x&context=3
Here's the comment that convinced me to use a different formula.
Let me know if it convinces you too, or if you can disprove it.

Thanks for your response. I did another calculation making use of tree diagrams and got the same formula that was suggested in the comment you linked. It turns out I had an error in my previous calculation where I used ... +2*(chance)²) while it should have been ...+chance². Simplifying that formula will then also lead to the one mentioned in the comment.
However, I also ran an artifact simulation many times over and over again: (Java)
private static void simulateArtifacts() {         List<String> ArtifactTypes = List.of("Flower", "Plume", "Sands", "Goblet", "Circlet");         String s1;         String s2;         int numOfDesiredArtifacts = 0;         int runs = 100000000;         for (int i = 0; i <= runs; i++) {             s1 = ArtifactTypes.get(Constants.randInt(0, ArtifactTypes.size() - 1));             if (Math.random() <= 0.07) {                 s2 = ArtifactTypes.get(Constants.randInt(0, ArtifactTypes.size() - 1));                 if (s2.equals("Flower")) numOfDesiredArtifacts++;             }             if (s1.equals("Flower")) numOfDesiredArtifacts++;         }         double p = (double) numOfDesiredArtifacts / (double) runs;         System.out.println(p);     }
Running this simulation returns a chance of 21.4% of receiving a Flower, which matches a base probability of 1.07.
Probability is confusing, I don't get this

Alright I did some more testing and I think I figured it out.
chance * 1.07 is the amount of desired artifacts you will get per run, while the suggested formula returns the chance of getting at least one desired artifact per run.
Sorry about the confusion, you may close this thread now.


Handle malformed lines in checksum file

Behavior should match sha256sum

Added regex a while back. Slow but works.


home / about section

Description :
Tweaked the home page a bit in line with https://github.com/carletex/ghofund/issues/6#issue-2261804802.
For now added the about, how to use the section on the landing page itself, but we could totally move them to separate pages.
Please feel free to suggest any copy / any design changes!  🙌
I think maybe the hero title and desc should be changed
https://github.com/carletex/ghofund/assets/80153681/0e3e2842-f799-4ca4-ac6f-22bc4a7eae96

omg @technophile-04!! this is amazing, TYSM!
I love it. I was thinking we can add icons maybe on the key features, I'll find some more designs/ideas. For now we can merge these and I can make a new pr for the next iterations on the page!


lack of rpc reconnection for bitcoind backend

We've received a few reports of user's node's failing to recognize a channel as confirmed, or even spent. In all instances, users were using the bitcoind backend. Reporst seem to indicate the for some reason the connection to the bitcoind backend (both zmq and the json-rpc connection) were broken. We don't detect disconnects and automatically reconnect for the bitcoind backend as we do for btcd.
To remedy this the library we use for zmq (https://github.com/lightninglabs/gozmq) should be modified to detect disconnects, and automatically reconnect using exponential backoff. .
Related to #871, #857.

I think there is related problem but with more fresh version of lnd
https://github.com/lightningnetwork/lnd/issues/640#issuecomment-397193556


Make hidden_indexable_content indexable

All MOJ finders use a hidden_indexable_field which should be indexed by
Rummger but currently isn't.  This PR adds code that includes the field
in a document's indexable content, when the field is present.
NOTE: This functionality used to work so likely it is a regression
introduced when specialist publisher was rebuilt.

@tijmenb As per our discussion I've created an initial PR to look at getting hidden content indexed.

The build's failing because of the linter.  If you can run bundle exec govuk-lint-ruby -a, and push up the changes, then it should get a bit further @lgarvey.  (You only need to worry about fixing the warnings in the files in your PR)

Thanks Simon!


cmd/go: add a '-go' flag to 'go mod tidy'

I've been considering the migration paths for lazy loading (#36460).
 Similarly, if users instead run go mod edit -go=1.17 && go mod tidy, they may find that the selected versions of transitive dependencies have changed: relevant transitive requirements that were previously implicit may be pruned out entirely by lazy loading.
To ease the transition, I suggest that we add a -go flag to go mod tidy. It would function analogous to the -go flag to go mod tidy, as go mod tidy -go=1.17. Specifically, it would cause go mod tidy to:

Load the existing module dependency graph according to whatever go version is already present in the go.mod file.
Load the all package pattern per the go version indicated by the -go flag, using the module graph from (1).
Then, write tidy go.mod and go.sum files with the go version indicated by the -go flag, recording the dependencies used in (2).

The implementation work for this approach would be fairly minimal, and it would allow users to adopt lazy loading without any changes to the selected versions of relevant modules.
CC @jayconrod @matloob @rsc

Is this going to happen for 1.17?

Yes, I still plan to get this in for 1.17. (It should be a small change, and makes the migration path much smoother for #36460.)


Implement trigger clauses

Implement the following methods in trigger clauses

public Bool equals(Object).  Not implement in AndClauseInTrigger and OrClauseInTrigger, since the equability of clauses between 2 AndClauseInTrigger/OrClauseInTrigger instances depends on the use cases.
public JSONObject toJSONObject()
public int hashCode(). Not implement in AndClauseInTrigger and OrClauseInTrigger, same reason as equals method.

Add small tests for the above methods
Add small tests for implementation of Parcelable interface

@shinsuke-nara  fixed. Please confirm

@yongpingchen LGTM!


dfget stuck for long time

Bug report:
please see: https://github.com/dragonflyoss/Dragonfly/issues/1157
Expected behavior:
please see: https://github.com/dragonflyoss/Dragonfly/issues/1157
How to reproduce it:
please see: https://github.com/dragonflyoss/Dragonfly/issues/1157
Environment:

Dragonfly version:
OS:
Kernel (e.g. uname -a):
Others:

Hi, it's a bug in dragonfly 1 repository, is this problem solved in dragonfly2, thanks

I think it's a really serious problem, because it could affect the system stability, hope to receive your reply, thanks in advance

Dragonfly 1 will not be maintained, it is recommended to upgrade to dragonfly 2.


Upgrading to sinon 15.0.4

Upgrading core repo to sinon 15.0.4 to bring it in line with presentation

publishing pr to repro test failures in ci

@aruniverse I have a draft PR for the map-layers-formats leaks, I guess we no longer need it ?

@aruniverse I have a draft PR for the map-layers-formats leaks, I guess we no longer need it ?

if your pr fixes a leak and can merge before this one, why not keep it and get it through?

Reverting the @types/sinon update since this typescript check is failing even though it is executing correctly and tests are passing:

This was a valid error as previously sinon was inferring sinon.fake((id: string) => id) type as sinon.SinonSpy<any[], any>. After @types/sinon was bumped it started to correctly infer type as sinon.SinonSpy<[id: string], string>.
I fixed that type and bumped @types/sinon back up as it looks like you reverted it back only because of this one test.

Reverting the @types/sinon update since this typescript check is failing even though it is executing correctly and tests are passing:

This was a valid error as previously sinon was inferring sinon.fake((id: string) => id) type as sinon.SinonSpy<any[], any>. After @types/sinon was bumped it started to correctly infer type as sinon.SinonSpy<[id: string], string>.
I fixed that type and bumped @types/sinon back up as it looks like you reverted it back only because of this one test.

Awesome, thanks for pushing the fix!


Rendered Meshes now respect the gameObject's layer

I just changed the rendering scripts to use the gameObject's layer to render at, instead of defaulting to layer 0.
I did this in order to be able to hide the teleporting graphics in other cameras in a split-screen multiplayer environment.

https://youtu.be/tpmK_WJzEuQ Demonstration using the Display Mirror function of SteamVR

LGTM, very elegant solution using gameObject's render layer.


Consider asking whether user wants instructions for finding answers in summons and case.net in id: how to answer

I think it makes sense to explain to the user where they can find the answers up front, which we already basically do on this page for the summons.  We could ask if the user wants instructions for finding the information in the summons and petition, casenet, or both.
If we asked this upfront, we could avoid the interview problems caused by docket_review and make the instructions and pictures for both the summons and casenet conditional in one question block.  Also asking up front would make more sense in directing the tenant to use the name used by the landlord.

I am wondering if it may make more sense to wait to ask about mistakes in the tenant's name until we're first asking about technical defenses. Introducing the idea of having to open a separate website to answer questions may be a bit overwhelming at the beginning of the interview.

My understanding is this issue is closed and we will keep current location of case.net path


lacking release of 1.3.1

please tarball source and add wallet release in github (and maybe the binaries for people into that kinda thing)

also add it as branch tree

Just tried the linux version of http://coinmagi.org/bin/m-wallet-1.3.1/
I get the below error when starting the wallet:
QXcbConnection: XCB error: 170 (Unknown), sequence: 170, resource id: 90, major code: 146 (Unknown), minor code: 20
Segmentation fault (core dumped)

I added v1.3.1 release, and will make a branch as well.

v1.3.1 release branched.


Unify the url of submodule to https url

What problem does this PR solve?
Issue Number: close #4565
related https://github.com/pingcap/tiflash/pull/4566, https://github.com/pingcap/tiflash/pull/6828
Problem Summary:
What is changed and how it works?
Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/cc @JaySon-Huang @Lloyd-Pottiger

And also unify with ".git" or not?

And also unify with ".git" or not?

ok, updated.

/merge

/run-unit-test

/run-integration-test


Flags not working - When a flag is selected, instead of image, country code is showing

Hello,
Please can you help me fix this issue. Everything with emoji-button works great except for flags. When I select a flag, it shows its country code in the reference element instead of the image. Even in the emoji-button website its so. Kindly guide on how to fix this issue.

Thanks in advance !

What operating system are you running?
Emoji support varies between operating systems. In particular, if you are running Windows, that might explain why you are seeing the two letters. Microsoft intentionally does not support country flag emojis on any version of Windows.
There are other potential causes too, but it is most likely not an Emoji Button issue, unfortunately.
Can you go to this link, and see if the flags are rendering with just two letter codes there as well?
https://emojipedia.org/flag-andorra/
I believe you could get around this issue by using the Twemoji emojis, actually. Twemoji provides the emojis as image files that will look the same on all platforms (SVG files, I believe). So as long as your platform supports SVG - which I'm sure it does in 2021 😄 - you should see the flag emojis for the different countries. Take a look at the Twemoji documentation for Emoji Button and try that example: https://emoji-button.js.org/docs/styles/
Native emojis are rendered differently on different operating systems. It is up to the OS vendor to provide glyphs (images) for the various emoji Unicode sequences.
If you're at all curious about how it works in more detail, I wrote a blog post a while back that explains some of it.
Anyway, I hope this helps. I will close the issue for now since there really isn't anything that can be done about it from my end. Feel free to re-open or open another one if you have any other issues.
Thank you!


Support import of patch series

Add a command to import a patch series from a series of files, and make it the next version of a series (or a new series).  In addition to simplifying the process of turning a format-patched series into a git-series commit, this would also enable advanced workflows like "export series as patches, run sed, re-import series, git series commit".
Import should also support setting the baseline in the same step, to allow this rebase workflow:

Export all patches
Run sed on all patches to rename variable that was renamed upstream
git series import -b new-upstream patches
git series diff to review
git series commit

What about making import/export complete inverse functions of each another? I.e. cover letter (also with sub series, issue #33) and maybe unapplied patches (e.g. when importing a patch series that doesn't apply cleanly a la quilt push/pop) should not get lost. For all those we might need a git series export, which also writes a series file. And add a --series option or similar to import for that additional data.

@danvet Agreed.  Any git-series metadata should round-trip through import/export.
I don't think I need a series file quite yet; I can rely on format-patch's numbered files instead.  Quilt import/export would be a separate issue from git-series native import/export.

what about integreation with git-review, git-pw (patchwork)?


Grammar correction (lines 40 and 42)

Removed unnecessary capitalization.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] 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

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

Thanks for contributing to the freeCodeCamp repository. Congratulations on your first PR! 🎊
Look forward to more contributions from you! ✈


Validate headers on fixtures

Currently any fixture HTTP header problems are ignored because they are not validated. For example: 'Authorization': 'Token blah' would not get caught (it should be 'Authorization': ['Token blah'])

Ready for review.

:+1:


Course content cannot be fetched.

A course cannot be downloaded. While the program trying to fetch content, it is retrieve as none chapter and none lecture. I have tried every possible arguments/options but still same result. By the Way I am able to watch course on the platform. Also I can download it manually.
Course link:  https://www.udemy.com/course/learn-english-grammar-online/learn
Screenshots of the command line:

@Puyodead1


CLI output is misaligned on public page even when source md has proper alignment

Example:
See step 2: http://kubernetes.io/docs/admin/limitrange/
And then compare with the source markdown file:
https://github.com/derekwaynecarr/kubernetes.github.io/blob/60c239941387c1a91dde0b86184f28741f252bdb/docs/admin/limitrange/index.md#step-2-apply-a-limit-to-the-namespace
This can make many of our CLI examples hard to read.
@johndmulhausen - is this something you are aware of?

To clarify, the last two rows in the table render misaligned on public site.  I am not a good font person, but maybe its not using a monospace font?
$ kubectl describe limits mylimits --namespace=limit-example
Name:   mylimits
Namespace:  limit-example
Type        Resource      Min      Max      Default Request      Default Limit      Max Limit/Request Ratio
----        --------      ---      ---      ---------------      -------------      -----------------------
Pod         cpu           200m     2        -                    -                  -
Pod         memory        6Mi      1Gi      -                    -                  -
Container   cpu           100m     2        200m                 300m               -
Container   memory        3Mi      1Gi      100Mi                200Mi              -

Actually, this issue appears to only happen with Firefox.
Using Chrome, the page renders properly.


Making sure the lock was successfully acquired before going further.

Fix for the issue #77

Awesome, thanks Hugues. I think this should be good!
Will merge in and do some more testing later. Cheers!


Fix default address of NuGet v3 stream

Just a quickfix, untested. See #2053 for details.

thanks!


Uploading Flutter App to Google Play - Please upgrade to Billing Library version 3 or newer to publish this app. Learn More about Billing Library 3

When I uploading Flutter App to Google Play I get the following error "Please upgrade to Billing Library version 3 or newer to publish this app. Learn More about Billing Library 3"
I have updated my app/build.gradle file to use version 4 as below:
def billing_version = "4.0.0"
implementation "com.android.billingclient:billing:$billing_version"

Also I even tried removing this completely and I still get this error.  I have tried with and without using the:
  <uses-permission android:name="com.android.vending.BILLING" />
Permission.
Any help is appreciated!

Hi @jgarrett77
Can you please provide your flutter doctor -v and what version of in_app_purchases you're using?
Thank you

Below is flutter Doctor output:
[✓] Flutter (Channel stable, 2.2.3, on macOS 11.2.3 20D91 darwin-x64, locale en-US)
    • Flutter version 2.2.3 at /Users/jabari.garrett/Development/Tools/flutter
    • Framework revision f4abaa0735 (3 months ago), 2021-07-01 12:46:11 -0700
    • Engine revision 241c87ad80
    • Dart version 2.13.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/jabari.garrett/Library/Android/sdk
    • Platform android-31, build-tools 30.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.5, Build version 12E262
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.60.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.26.0

[✓] Connected device (1 available)
    • Chrome (web) • chrome • web-javascript • Google Chrome 94.0.4606.61

• No issues found!

I am using:
purchases_flutter: ^3.4.5
Thanks!

Hi @jgarrett77, you appear to be on an older version of flutter stable.
If possible, kindly upgrade to the latest version of stable and try again.
Also, it appears you're using a third party package. The purchases_flutter package is not maintained by the flutter team, so if you upgrade and you still run into the issue, I will advise that you file an issue with the purchases_flutter repo.
Kindly share your pubspec.yaml as well so that we might confirm if the issue is from another package or purchases_flutter.
Thank you

Here are my pubspec.yaml dependencies
cupertino_icons: ^1.0.0
  carousel_pro: ^1.0.0
  flutter_swiper : ^1.1.6
  carousel_slider: ^3.0.0
  badges: ^1.1.0
  http: ^0.13.3
  font_awesome_flutter: ^8.5.0
  fluttertoast: ^3.1.3
  custom_radio: ^0.1.2
  flutter_rating_bar: ^3.0.0
  page_transition: "^1.1.5"
  flutter_spinkit: ^3.1.0
  fancy_on_boarding: ^1.8.0-nullsafety.0
  flutter_svg: ^0.21.0-nullsafety.0
  amplify_flutter: '<1.0.0'
  amplify_auth_cognito: '<1.0.0'
  amplify_api: '<1.0.0'
  amplify_storage_s3: '<1.0.0'
  flutter_multiple_image_picker: ^0.0.1
  dropdown_formfield: ^0.1.3
  flutter_search_bar: ^2.1.0
  image_picker: ^0.8.0+3
  image_cropper: ^1.3.1
  progress_dialog: ^1.2.4
  wechat_assets_picker: ^5.5.4
  xml: ^5.0.0-nullsafety.1
  video_thumbnail: ^0.3.3
  image: ^3.0.2
  mime: ^1.0.0
  path_provider: ^2.0.2
  path: ^1.8.0
  chewie: ^1.0.0
  video_player: ^2.1.6
  flutter_image_compress: ^1.0.0
  flutter_local_notifications: ^8.1.1+1
  rxdart: ^0.27.1
  flutter_native_timezone: ^2.0.0
  provider: ^5.0.0
  shared_preferences: ^2.0.7
  dashed_circle: ^0.0.1
  skeleton_loader: ^2.0.0+4
  cached_network_image: ^3.1.0
  package_info_plus: ^1.0.5
  firebase_core: ^1.6.0
  video_compress: ^3.1.0
  youtube_player_flutter: ^8.0.0
  purchases_flutter: ^3.4.5
  url_launcher: ^6.0.10

Hi @jgarrett77, I can see that you've filed an issue with purchases_flutter, as such I'll be closing this issue for now.
If they redirect you back here, kindly link the issue and I'll reopen.
Thank you


Change the base url for fetching from neuromorpho

Based on the API docs we should use http://cng.gmu.edu:8080/api as the URL. This might fix some of the uptime issues we've faced in the past. Perhaps http://cng.gmu.edu:8080/api is still up when https://neuromorpho.org/api is down?

Sounds like a good idea to me, especially because currently http://cng.gmu.edu:8080/api is up and https://neuromorpho.org/api is down


null score and amount of ratings on obscure mangas

Before finding about this project, I tried parsing mangas on my own with Beautiful Soup on Python 3, and encountered a problem I see here as well. It seems that with some obscure mangas, the 'score' and 'scored_by' attributes are null due to a different formatting than what more popular ones use. Instead of being contained like usual,
6.75
235,
they are formatted in this way:

  Score:
  7.47

    1

  (scored by 15 users)
    ...

Hi @Sacules , thanks for the input! MAL finds itself not following standard HTML and is very inconsistent most of the time.
I'll go ahead and add a patch for this. You've already provided a snippet, but I still require the ID or link to the manga with such formatting for overall testing. Thanks!

I first noticed it on this one:
https://myanimelist.net/manga/96896/Tensai-tachi_no_Kyouen
PS: I also noticed I get 404 responses on this (https://myanimelist.net/manga/104346/Adventure_Broadcasting_Station), should I open an issue for it?

Awesome, thanks!
The latter one seems to be returning a parsing error "error": "date_format() expects parameter 1 to be DateTimeInterface, boolean given"
This is related to the abnormal date MAL is going with here Published: Jan 20, 1950 to 10, 1951, I'll go ahead and ping another related issue to this so no need to. #99

Fixed.


Add recursive dependency tracking to pynqmicroblaze

At the moment the user must import all libraries used by a microblaze program - even if one is only used as a dependency rather than directly. This commit removes that burden from the end user making the process more intuitive

Codecov Report

Merging #1127 into image_v2.6.0 will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff              @@
##           image_v2.6.0    #1127   +/-   ##
=============================================
  Coverage         48.69%   48.69%
=============================================
  Files                22       22
  Lines              3647     3647
  Branches            600      600
=============================================
  Hits               1776     1776
  Misses             1830     1830
  Partials             41       41

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 9651977...ee81fec. Read the comment docs.


Made culture specific to avoid language clashes

Opening PR to get actions triggered.
Still need to refactor before its ready.

Love it :^)


humble: add missing  include

Add cstdint include to humble.  related to #165 and #172

Given no response in quite a while here, I'm going to close this out.  As far as I can tell, the includes are proper here.  If you are still having a problem, please feel free to reopen and give us more information.


Make IIS tests runnable without publishing.

And cleanup web.config and apphost.config generation between IIS and IISExpress.

w3wp has
        -w <Root web config filename>
                 Optional root web config file to use.

argument that we can use to pass generated web.config in temporary location,

This is resolved via copying compiled output for publish.


int range not working

Hello, I am trying to specify range to int:
    @Fixture
    @Range(min = 1, max = 10)
    private int minNoOfFirstAidersRequiredInTeam;

But still, returned int value is not in range 1-10, any help would be appreciated, thank you!

Hi @MateuszMysliwiec thanks for the report.
I've tried to reproduce this but it works fine for me, so here's a few questions that would help diagnosing it:

Are you running @Rule public FixtureRule fr = FixtureRule.initFixtures() or FixtureAnnotations.initFixtures(this); which will initialise the @Fixture fields?
Are you definitely importing the correct annotations? They should be,

import com.flextrade.jfixture.annotations.Fixture;
import com.flextrade.jfixture.annotations.Range;

Which version of JFixture are you using? I can checkout that tag and try to reproduce it again
Can you reproduce this issue using long instead of int?

Thanks!

Hi @richkeenan, thank you for response.
I am using latest version of JFixture, and looks like I have misunderstood the "Cheat Sheet" guide because I am not using any of those mentioned here:
Are you running @Rule public FixtureRule fr = FixtureRule.initFixtures() or FixtureAnnotations.initFixtures(this); which will initialise the @Fixture fields?
Here is my workflow:

I am using JFixture to generate random/mock data for Database tables generated by Hibernate java framework.

I am doing it this way:
JFixture fixutre = new JFixture();
SomeEntity siteRequirement = fixture.create(SomeEntity.class);

And that is all, now inside SomeEntity class, I wanted to specify ranges for some variables, using add-notations specified in first post, answering your question, I checked and I am using correct imports, so it must be probably lack of @Rule you mentioned, but I still do not understand where shall I put it in my case, thank you again and sorry if I missed something.

Assuming SomeEntity is a production class, it shouldn't have @Fixture annotations in it. Remove jfixture dependency from production, and keep it only for test source set.
The @Fixture annotation is only processed by the rule or initFixtures.
The way you're creating your fixture object works without the annotation, but creates a full-range value as you observed.
Sometimes if you want a specific value you need to set it manually:
SomeEntity siteRequirement = fixture.create(SomeEntity.class);
siteRequirement.minNoOfFirstAidersRequiredInTeam = fixture.create().inRange(int.class, 1, 10)

If you want to create multiple of these objects but don't want to manually configure all the time, you can use fixture.customize().intercept(SomeEntity.class, ...) (or transform) to change the auto-generated object.


[ExternalInterfaces] Make fill non-hoistableLeafOp, hoist linalg init operands

This PR changes the HoistableOpInterface implementation for LinalgOps to make DPS init operands hoistable. If there is real computation on the init of a linalg op, then we would want to hoist that computation. The main way the current policy (not hoisting init operands) affects hoisting today is by preventing linalg.fill ops from being hoisted into splat constants, since the init operands are usually linalg.fill or tensor.empty. Since we want to preserve the behavior of not hoisting fills (and instead fusing them with consumers to handle in codegen), the interface implementation now treats fill ops as non-HoistableLeafOps.

This breaks the top_k e2e test, but it looks like the top_k lowering was broken to begin with, and constant folding the fills was "fixing" it by adding extra barriers at bufferization. I'm going to need to fix this before landing.

Thanks for taking care of this! I'd like to take an additional review after the topk issue is fixed, so I put a "request changes" for now.

I talked to Mahesh offline and we decided it would be okay to open this in an issue and disable the test for now in this PR. @krzysz00 offered to take a look when he has some time, but it might take a few days. Since topK is not very important we decided it is okay to disable the test to unblock GPU data tiling progress. WDYT?


Avoid rescuing argument error in next node blocks

I don't think it's a good idea to rescue from such a generic exception in our
next_node blocks. It hides real problems in our Ruby code and makes them look
as though the user has entered invalid data in the Smart Answer.
The rescuing of ArgumentError caused me problems twice recently. Once when I was
comparing a Date with a String and once when I was calling a method with
incorrect arguments. This change will mean that errors such as this cause the
application to fail fast.
>> Date.today < '2016-01-01'
ArgumentError: comparison of Date with String failed

>> def foo(arg); end
=> :foo
>> foo()
ArgumentError: wrong number of arguments (0 for 1)

The first two commits ("Raise InvalidResponse when parsing Integers in
Value#parse_input" and "Raise InvalidResponse when parsing Floats in
Value#parse_input") should have removed the only places where we were raising
an ArgumentError in response to bad user input.
We're still raising an ArgumentError from SmartAnswer::Calculators::VatPaymentDeadlines#last_payment_date and #funds_recevied_by. I haven't changed these because I don't believe this error will ever be raised by code in a next_node block. The error can only be raised by #last_payment_date and #funds_received_by if an option other than one of those listed in the multiple_choice options for the :how_do_you_want_to_pay? question is entered, and in that case the SmartAnswer::Question::MultipleChoice#parse_input method will raise an InvalidResponse exception first.
I ran all the regression tests locally against this change and didn't see any errors. That's no guarantee that we won't see problems if/when this is deployed to production.

It looks as if there may be other places explicitly raising ArgumentError which might need attention:

https://github.com/alphagov/smart-answers/blob/master/lib/smart_answer/calculators/vat_payment_deadlines.rb#L27
https://github.com/alphagov/smart-answers/blob/master/lib/smart_answer/calculators/vat_payment_deadlines.rb#L50
https://github.com/alphagov/smart-answers/blob/master/lib/smart_answer/question/base.rb#L28

Also I wonder whether it's worth inspecting the message of the legitimately rescued ArgumentErrors c.f. https://github.com/alphagov/smart-answers/blob/master/lib/smart_answer/question/date.rb#L75-L79
Apart from the above, this looks great to me! :+1:

It looks as if there may be other places explicitly raising ArgumentError which might need attention:

https://github.com/alphagov/smart-answers/blob/master/lib/smart_answer/calculators/vat_payment_deadlines.rb#L27

I've already addressed this in the description of this PR. Essentially, I don't think we need to worry about it.

https://github.com/alphagov/smart-answers/blob/master/lib/smart_answer/calculators/vat_payment_deadlines.rb#L50

This is the same as 1, above, so I don't think we need to worry about it. I've updated the description of this PR to include this case as well as 1.

https://github.com/alphagov/smart-answers/blob/master/lib/smart_answer/question/base.rb#L28

This ArgumentError exception will be raised if next_node is called without any arguments which seems OK to me. I'm only interested in exceptions that are raised while evaluating blocks passed to next_node.

Fair do's. Apologies if I missed the explanation in the PR description first time round.
Look good to me :+1:

Also I wonder whether it's worth inspecting the message of the legitimately rescued ArgumentErrors c.f. https://github.com/alphagov/smart-answers/blob/master/lib/smart_answer/question/date.rb#L75-L79

I guess my thinking was to replicate the rescue ArgumentError behaviour that was previously in Flow#process. I can see that it'd probably be better to explicitly rescue certain exceptions but I think we could attack that separately as it would lead to a slight change in behaviour.


python3Packages.cylp: init at 0.91.4

Motivation for this change
Adds the package requested here: https://github.com/NixOS/nixpkgs/issues/112353, and adds it as a dependency of CVXPY, so that it has access to another good solver.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 154026 run on x86_64-linux 1

18 packages built:

python38Packages.cvxpy
python38Packages.cylp
python38Packages.qiskit
python38Packages.qiskit-aer
python38Packages.qiskit-aqua
python38Packages.qiskit-finance
python38Packages.qiskit-ibmq-provider
python38Packages.qiskit-ignis
python38Packages.qiskit-optimization
python39Packages.cvxpy
python39Packages.cylp
python39Packages.qiskit
python39Packages.qiskit-aer
python39Packages.qiskit-aqua
python39Packages.qiskit-finance
python39Packages.qiskit-ibmq-provider
python39Packages.qiskit-ignis
python39Packages.qiskit-optimization

@Janik-Haag: I've abandoned this. Please feel free to go ahead and copy from my branch and make a new PR. I'll close this PR for now.


N-Queen Problem

I would like to add a code for N-queen problem under backtracking folder
I will do this with the help of recursion.
Programming language

[ ] C
[x] C++
[ ] Java
[ ] Python

Hi, I would like to code this solution in Java. Please assign this issue to me.

@div0510 mention the language

I am working on this issue using C++

@div0510 is it regarding permutations and combination in NQueen??

@Amit366  Sorry it was by mistake

Can I know my commit for n-queen using c++ was passed??

Yes it is merged

Thank you !! Had a great experience working with you.
May I know how can I add folder since I want to add code for different types of pattern

@div0510 u can create a separate issue for that and then create a folder named simple programs

Thanks I will surely try for this


adding SHUSHI token3

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

hello, Im trying to add my logo and name to this token, please tell me what i am doing wrong

Hi, your logo uri should have https://

hello i have corrected everything and am still getting an auto merge error?
any idea why? what can i do to correct this? i am on try number 5.....🙏
On Sun, Jan 16, 2022 at 10:08 PM NFTSOLANAGALLERY @.***>
wrote:

hello, Im trying to add my logo and name to this token, please tell me
what i am doing wrong
Hi, your logo uri should have https://
—
Reply to this email directly, view it on GitHub
https://github.com/solana-labs/token-list/pull/14360#issuecomment-1014096102,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXAHA7IWBOCMWQUGDPNROC3UWOB3XANCNFSM5MDRIYRQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

I can help stop wasting your time refer this zakimzf/profile#1


[TVMScript] IRBuilder methods for PrimFunc

This PR introduces remaining IRBuilder methods for PrimFunc.
Co-authored-by: yongwww<EMAIL_ADDRESS>

Any updates?

Any updates?

All have been updated.


Using command winget upgrade --all does not update some software and does not say why.

Brief description of your issue
Using command winget upgrade --all does not update some software and does not say why.
I can see in the log the real reason :

Installer [X64,wix,Machine,] not applicable: Installed package type 'exe' is not compatible with installer type wix, or with accepted type(s) wix

Steps to reproduce
winget upgrade --all
Nom                    ID                       Version Disponible Source
-------------------------------------------------------------------------
MiKTeX                 ChristianSchenk.MiKTeX   22.3    22.7       winget
Password Safe (64-bit) RonyShapiro.PasswordSafe 3.58.0  3.59.0     winget
2 des mises à niveau sont disponibles.

Expected behavior
It must update all these softwares or say why it can't.
I think wget should provide a command to reinstall the software in this case.
Actual behavior
Somme's software are skipped without any visible explanation.
Environment
Windows: Windows.Desktop v10.0.19044.1889
Architecture du système: X64
Package: Microsoft.DesktopAppInstaller v1.18.2091.

Many of these packages support "side-by-side" installation. If you run winget list you are likely to see more than one version present. We're working on enhancements to the upgrade flow to check and see if the latest version is already installed on the system to avoid displaying them again.

@rp1231 it may be a bug in the installer. What version does it display when you go to Windows Apps & Features? The version that is displayed by winget is the value in the registry reported by the installer.

That means that either it did an upgrade and didn't change the value, or there is a bug and it's not reporting the latest version correctly. It's also possible that the manifest is reporting the version incorrectly.
PackageIdentifier: JamieOConnell.MIDI-OX
PackageVersion: 7.02.373
MinimumOSVersion: <IP_ADDRESS>
InstallerType: exe
Scope: machine
InstallerSwitches:
  Silent: /auto /args="/quiet /norestart"
  SilentWithProgress: /auto /args="/passive /norestart"
Installers:
- Architecture: x86
  InstallerUrl: http://www.midiox.com/zip/midioxse.exe
  InstallerSha256:<PHONE_NUMBER>1764AEEDA2FDE8819B894B76243E233FD009D732193DAA9DB72385
```YAML

Any solution to dealing with an incorrect manifest file? Or maybe the developer hasn't uploaded the correct file in the download location?

@Trenly are you familiar with MIDI-OX? I'm not sure if the manifest is incorrect, or if the installer has a different version than the package.

Any solution to dealing with an incorrect manifest file? Or maybe the developer hasn't uploaded the correct file in the download location?

@Trenly are you familiar with MIDI-OX? I'm not sure if the manifest is incorrect, or if the installer has a different version than the package.

I'll take a look in a bit

It looks like a vanity URL so it might be any number of things that changed.

It looks like a vanity URL so it might be any number of things that changed.

It looks like a typo in the manifest, where 373 was used instead of 372. I've opened microsoft/winget-pkgs#78888 to fix the package, and also updated it to use the Marketing Version, with ARP Mapping.

@rp1231 take a look in Windows Apps & Features. If you look below the "name" of the package, you will see what version that package is reporting. That's the version we use for comparison during "upgrade". If the manifest has a different "packageVersion" from the "displayVersion" in the "AppsAndFeatures" section of the manifest, then a "marketing version" would be displayed to the user.
https://devblogs.microsoft.com/commandline/windows-package-manager-1-3/#new-version-reporting will explain a bit more with an example image.

Does winget uninstall BlenderFoundation.Blender --version 3.2.2 work? I'm wondering if their installer isn't cleaning up the old entries. We may need to add "uninstallPrevious" to the manifest to get the desired behavior.

That means there are still registry entries for 3.2.2, but the package may not be present if you don't see it in Windows Apps & Features. This may require a manual removal.

I'm glad that worked! I hope this helps others too. It might be worth asking them if they are aware and would be willing to improve their customer experience.

I saw same behavior with Microsoft.azure-iot-explorer several times.
winget upgrade listed the new available version and winget upgrade --all ignored the package.
In the first place I removed the package to install the new version. Today I first tried winget upgrade --id Microsoft.azure-iot-explorer what responded with "No applicable update found".  Afterwards I just installed the new version and the old one was removed as expected.

Noticed the same issues with some of my packages.
Nome                            Id               Versione     Disponibile  Origine
----------------------------------------------------------------------------------
MiKTeX                          MiKTeX.MiKTeX    22.8.28      22.10        winget
Webex                           Cisco.WebexTeams <IP_ADDRESS>81 <IP_ADDRESS>94 winget
Teams Machine-Wide Installer    Microsoft.Teams  <IP_ADDRESS>70   <IP_ADDRESS>361 winget
Dokan Library <IP_ADDRESS>0 Bundle dokan-dev.Dokany <IP_ADDRESS>0   <IP_ADDRESS>0   winget
4 aggiornamenti disponibili.

After checking, winget says that my Webex version is <IP_ADDRESS>81 and I can upgrade to <IP_ADDRESS>94, however after checking in the app it says that my version is <IP_ADDRESS>14, two version ahead of what winget thinks my version is...
Same thing happens with Teams, it says I'm at version <IP_ADDRESS>70 and I can go to <IP_ADDRESS>361, but mine is already at <IP_ADDRESS>63...

I have the same problem
`PS C:\Users\xxx> winget upgrade
Name                              Id                            Version   Available Source
WinRAR 6.11 (64-bit)              RARLab.WinRAR                 6.11.0    6.21.0    winget
WinSCP 5.21.6                     WinSCP.WinSCP                 5.21.6    5.21.7    winget
Remote Desktop Connection Manager Microsoft.Sysinternals.RDCMan 2.7.14060 2.92      winget
3 upgrades available.
PS C:\Users\xxx> winget upgrade --all
Name                              Id                            Version   Available Source
WinRAR 6.11 (64-bit)              RARLab.WinRAR                 6.11.0    6.21.0    winget
WinSCP 5.21.6                     WinSCP.WinSCP                 5.21.6    5.21.7    winget
Remote Desktop Connection Manager Microsoft.Sysinternals.RDCMan 2.7.14060 2.92      winget
3 upgrades available.
183 package(s) have version numbers that cannot be determined. Use --include-unknown to see all results.`

[Policy] Command-Upgrade
[Policy] Area-Output

Many of these packages support "side-by-side" installation. If you run winget list you are likely to see more than one version present. We're working on enhancements to the upgrade flow to check and see if the latest version is already installed on the system to avoid displaying them again.

That worked, thank you.
Turns out I had two installs of "Microsoft.DotNet.DesktopRuntime.7" and Powershell (9MZ1SNWT0N5D and Microsoft.PowerShell). Removing both and reinstalling one of the Microsoft.DotNet.DesktopRuntime.7 and Microsoft.Powershell fixed the issue.

@mdanish-kh suggested adding the AppsAndFeatures > InstallerType entry to set the nested installer type for the FireDaemon OpenSSL package, which had the same problem.

I think this happens when the installer type changes between versions winget doesn't know how to upgrade the package. Uninstall/install will resolve it, but that's obviously not ideal.


Correctly support SSLSession.getId() when using OpenSslEngine

Motivation:
At the moment SSLSession.getId() may always return an empty byte array when OpenSSLEngine is used. This is as we not set SSL_OP_NO_TICKET on the SSLContext and so SSL_SESSION_get_id(...) will return an session id with length of 0 if tickets are not used.
Modifications:

Set SSL_OP_NO_TICKET by default and only clear it if the user requests the usage of session tickets.
Add unit test

Result:
Ensure consistent behavior between different SSLEngine implementations.

@nmittler @Scottmitch PTAL

lgtm
since this is a change in behavior for how the OpenSslEngine previously behaved we should call this out in the release notes.

@Scottmitch +1

LGTM


ACHA agent?

Hi, I'm just curious that why ACHA agent is not included in this repo?

Thanks for the question. In this case, it would have been a significant effort to write a new version from scratch that was designed for public release.

Thanks for your reply, looking forward to see that 👍

Hello, are there any plans to release the ACHA agent in the near future?

There are no such plans.  It would require writing a new version from scratch, and would be a significant effort, like the Dopamine code release.


AsyncRiotAPI.getCurrentGame() returns null

AsyncRiotAPI.getCurrentGame() returns null and so handle() is never called

Right now, handle for currentGame() should be used to handle other API Exceptions besides 404s. Returning null when there is no current game is special behavior for this endpoint which was suggested due to the frequency of 404s from the endpoint. You should check if the game returned in perform() is null instead.

Okay, thanks.


Allow the default sorting to be set on individual resources

Example usage:
ActiveAdmin.register Post do
  default_sort :title_asc
end

Nice request. Now i have this:

undefined method `default_sort_attrs' for Admin::AdvicesController:Class

.rvm/gems/ree-1.8.7-2011.12@euro/bundler/gems/active_admin-1f033aff5ed9/lib/active_admin/resource_controller/collection.rb:52:in default_sort_attr
.rvm/gems/ree-1.8.7-2011.12@euro/bundler/gems/active_admin-1f033aff5ed9/lib/active_admin/resource_controller/collection.rb:66:in sort_order
.rvm/gems/ree-1.8.7-2011.12@euro/bundler/gems/active_admin-1f033aff5ed9/lib/active_admin/resource_controller/collection.rb:62:in active_admin_collection

@reignmaker Are you trying using the default_sort feature or do you just have an empty resource and are getting this during start up?

Hmm, this is working for me on 1.9.2 but not with 1.8.7. It seems to be something to do with defining the class attribute with the module. I'll keep investigating and see what I can come up with. Has anyone been able to define class attributes with a module in 1.8.7 before?

I just reverted the changes. I tested it locally with ruby 1.9.3 only.
@DMajrekar The sort order is already implemented as an attribute on Resource. I would rather see a method called sort_order which takes the order and the :if / :unless conditions. Also the logic should be implemented on Resource rather than ResourceController.

Thanks @pcreux. Is there a way to reopen this pull request, or if I push to the brach will it re-open it?

This should now be resolved. I've pushed the fixes but this pull request still seems closed. I'll open another one now.


Remove rank restrictions on loggers

🚀 Feature
Allow loggers to log on non rank 0 processes.
Motivation
We want to log system data across all ranks (e.g.  using a custom logger to log GPU memory, latency stats, etc). This is important if we want to detect stragglers or anomalous conditions in a rank.
Pitch
The trainer should not check that the process is on global rank 0 before calling the logger.
We already have rank_zero_experiment (https://github.com/PyTorchLightning/pytorch-lightning/blob/a64cc373946a755ce6c3aef57c1be607dfe29a0c/pytorch_lightning/loggers/base.py#L33) and @rank_zero_only decorating all loggers. We can simply remove the global zero checks in logger_connector.py here (https://github.com/PyTorchLightning/pytorch-lightning/blob/6b47cbe3ca8aa3fd82211bc9fa32e734753a6950/pytorch_lightning/trainer/connectors/logger_connector/logger_connector.py#L105-L109), and here (https://github.com/PyTorchLightning/pytorch-lightning/blob/6b47cbe3ca8aa3fd82211bc9fa32e734753a6950/pytorch_lightning/trainer/connectors/logger_connector/logger_connector.py#L180).
Alternatives
Additional context

@awaelchli @carmocca this is similar to last year when we lifted rank_zero_only restrictions for saving checkpoints

@edward-io thanks for this suggestion. The first occurrence you pointed out can probably be without the check for global zero but I'm not sure what the second one has to do with the loggers since it prints to stdout. What would you like to do there?

@awaelchli  good point, it might not be useful to print it out. I don't have a strong opinion, what about @ananthsub?

@awaelchli good point, it might not be useful to print it out. I don't have a strong opinion, what about @ananthsub?

it's fine to print out only on rank 0. the first one is the one which can be broadened, as #8608 does

Hey @ananthsub @awaelchli,
Could we imagine this designed inspired from Metrics.
Motivations:

Provide an option for users to log on all ranks if needed
Remove logging control within the LoggerConnector as each Logger will be responsible for it now.

from pytorch_lightning.utilities import rank_zero_only as rank_zero_only_fn

class BaseLogger

    def __init__(self, rank_zero_only: bool = True):
        self.rank_zero_only = rank_zero_only

        self.log_metrics = self._rank_zero_only_wrapper(self.log_metrics, rank_zero_only_fn)
        self.experiment = self._rank_zero_only_wrapper(self.experiment, rank_zero_experiment)

    def _rank_zero_only_wrapper(self, fn: Callable, decorator: Callback) -> Callable:

        @functools.wraps(fn)
        def wrapped_func(*args: Any, **kwargs: Any) -> Optional[Any]:
            return fn(*args, **kwargs)

        return decorator(wrapped_func) if self.rank_zero_only else wrapped_func


⚠ SolarOscp has degraded performance

In 9402564, SolarOscp ($SOLAROSCP_URL) experienced degraded performance:

HTTP code: 200
Response time: 230 ms

Resolved: SolarOscp performance has improved in 08ae439 after 7 minutes.


Defer charging fuel for bulk table and bulk memory operations

Fuel checks are still happening before the bulk operation execution but fuel charging only happens if those operations succeeded.
This make sense given that all of these bulk operations fail fast. So only if they succeeded they actually performed a lot of potential computation.

The diff coverage is 72.93%.

@@            Coverage Diff             @@
##           master     #676      +/-   ##
==========================================
+ Coverage   81.37%   81.41%   +0.04%
==========================================
  Files         100      100
  Lines        8386     8417      +31
==========================================
+ Hits         6824     6853      +29
- Misses       1562     1564       +2

Impacted Files
Coverage Δ

crates/wasmi/src/error.rs
58.62% <0.00%> (ø)

crates/wasmi/src/func/caller.rs
41.66% <0.00%> (ø)

crates/wasmi/src/store.rs
74.69% <16.66%> (-2.20%)
:arrow_down:

crates/wasmi/src/engine/executor.rs
95.43% <80.17%> (+0.53%)
:arrow_up:

crates/wasmi/src/memory/mod.rs
65.32% <100.00%> (-0.33%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Move all qa_* jobs to a file owned by devx loops and e2e testing teams

What does this PR do?
It moves job that deploy packages used in e2e tests to a separate file so we can attribute the correct ownership and devxloops can be aware of changes on these files

Motivation
Avoid modification on deploy jobs that we are not aware

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


osversion: add "Unmanifested" const

relates to https://github.com/microsoft/hcsshim/issues/1080

This const can (in most situations, unless you're expecting obsolete versions of Windows) used to check if a binary hasn't been manifested, so the OSVersion cannot be used.

So no idea if this makes sense;

Is (the REAL) 9200 still something that people may use?
Can this "unmanifested" version change? (was the version picked as "versions after this support manifesting, so if it's not manifested, assume the "last version before manifesting was introduced"?) <-- if so, perhaps that's worth including in the const's description.

Thought I'd open it as a PR, in case it makes sense
/cc @tianon @kevpar @jterry75

9200 didnt support containers. IMO we should panic. If you are calling this and get 9200 you are either A) unsupported Windows OS, B) unmanifested in which case you will not hit the code paths you expect. Both need to be handled with a quick "panic(STOP DOING THIS)" :)

^ btw, I think we can solve this with a quick once shell to cmd

You mean for version.Get() ? Need to check if there's no repos using this in (integration) test code (which usually isn't manifested) 🤔

Yea basically osversion.Get(), if 9200 do a cmd ver and get the ver cmd thinks it is. If thats a real ver like 18363 then store the 18363 etc.

Yea basically osversion.Get(), if 9200 do a cmd ver and get the ver cmd thinks it is.

Does cmd have a stable "API" to get this info?
FWIW; this is what we use as fallback in docker (perhaps could be an alternative);
https://github.com/moby/moby/blob/2400bc66ef6955760a331a2bff767d4fec244844/pkg/parsers/kernel/kernel_windows.go

oh, actually, I think that's the wrong one; that also requires manifested 🤔 let me check.

"Shell out to cmd /c ver in once" gets an eww from me, but I recall the "Read the registry key" approach (that containerd was using for code that wrapped a the hcsshim calls that needed different parameters on different builds) was the one that MS-internal querying rejected.
Either way, I agree that 9200 is fine to be special. There's no way code that is checking this version will have a sensible action for <IP_ADDRESS>00 apart from "fail noisily and fatally". I am assuming that's the full version returned by an unmanifested binary, i.e. the precise Server 2012/Windows 8 version, otherwise we'd be able to distinguish "Unmanifested" from "really Windows 8" and that would make things simpler.
Whether we should panic when we see 9200, or fail and give the caller an "Binary probably not manifested" error, is an interesting discussion. If all relevant code-paths that hit this inside hcsshim can expose an err, then I'd probably not panic inside hcsshim, so the caller can produce a more-useful "Did you build this binary yourself?" complaint, including checking non-canonical sources (Registry, FILEINFO of kernel32.dll, etc) to give better reports. panic in a library is very much not a friend-shaped solution.
(There was also a separate discussion about changing hcsshim APIs to either be version-specific, so that the caller must check the OS version when it matters, or allowing APIs to have the OS version injected in case the caller wants to override hcsshim's choice of canonical version info).

"Shell out to cmd /c ver in once" gets an eww from me

LOL! Yea, it's just a special case for 9200 I agree. At the end of the day even though when we asked @dcantah to ask internally and we were told Registry is not supported the truth is that we are doing it all over the place and it 100% works. So if we don't do cmd /c ver in a once, then let's just read the build number from the registry in a once when we get 9200 and then use it. It's going to work.

Whether we should panic when we see 9200, or fail and give the caller an "Binary probably not manifested" error, is an interesting discussion.

Reason I suggested panic is that the API for Get() today isn't an error API. So the only option we really have is to panic right?

I (still) don't have the code in front of me but it's possible that Docker and containerd only use osversion.Get or osversion.Build explicitly in their test-suites, to pick container image bases to use. I have a vague recollection that I was surprised to discover this was the case, assuming I'm remembering the correct API, and the actually-problematic uses were inside hcsshim APIs that were directly used.
In that case, breaking the Get API to support (build, err) seems reasonable, and even if I'm misremembering, this part of hcsshim probably isn't really API-stable in any important way, given that containerd.exe isn't manifested today, so it can't be using it directly.

Doing less than 5 minutes of research both are used.
Containerd is mostly absent of osversion outside of test cases. BTW the tests are manifested (or at least they used to be) (yours truly did it...). However they also use the reg key read workaround for CurrentBuild as proposed here.
For Docker they appear to use both. They use Get() and Build() and they do things like Get().MajorVersion > ... as well as Build() == osversion.V....
Given the usages here maybe we should add a new func Is(version) or IsAtLeast(version) or IsInRange(version, version)` etc so the caller can have simpler checks?
But I still propose we dont return an error even if we do the above. I want to write code like this:
if osversion.IsAtLeast(osversion.19H1) {
   // Do cool stuff
}

I dont want to have to write:
v, err := osversion.IsAtLeast(osversion.19H1)
if err != nil {
   // unmanifested
} else if v > osversion.19H1
   // Do cool stuff
}


Add State/Config filters to YANG Compare

Hi, it'd be cool to have a filter for state and config paths in the YANG Compare page.
Sometimes users can be interested to just look at the new configurable paths rather than having the whole set of new paths (config+state).

Thanks for adding this, there's just a small display bug. When selecting "RW - Config", it appears as "RW - State". Can you fix this ? Thanks!

@bclasse intention was to mention it is filtering Read Write State. But I see your point, what do you think would be a good common name for State and Config to represent the dropdown field?

@bclasse requested changes are live.


Remove @useView limitation with moduleId workaround

See line 282 in src/durelia-framework.ts
I see you have multiple redefinition of durandalSystem)["resolveObject"].
I merged in one function.

Good catch!
Thanks :-)


Changed the chat text showing the keyboard "leave" key to a label + Cleanup

Fixes #892

looks good to me

Atomic commits! Refactoring! Looks good.

This pull request is just about the cleanest I've ever seen! And the code looks good too :wink:
:+1: from me

now THIS looks more like Lua to me and less like QuakeC...

let's go then


Clean up CFeatures::dense_dot implementations

Currently, there is a ton of copy pasted code in CFeatures::dense_dot (in the .cpp).
This task is to use C++ (11) features to replace this with a templated version that avoids the heavily redundant code.
Or even use linalg as that will be faster.
Ask if you need a pointer to get started

I'll bite. Totally new to making open-source contributions and looking to start getting involved in the community. Any pointers would be appreciated!

This task requires a bit of C++ experience. First have a look at the code and see if you can find things you don't like. Then we can discuss

It's entirely possible that I'm not totally qualified for this fix as most of my experience lies outside of C++. It's a language I'd like to get more experience with, but at the same time I don't want to waste everyone's time floundering with an issue.

Thinking of taking a crack at this. @karlnapf did you mean the code in DenseFeatures.cpp, starting line 633?

yes, please go for it

try to use SIMD where possible (linalg)
avoid redundant code
templates are powerful

and please no manual template spezialization for different types of the dot products.


Cache-DSL to help get cache headers correct

Describe the feature
Caching HTTP resources is hard, and one of the things I love about Javalin is that it makes seemingly hard things easy. If we could create a simple, yet consise DSL to help creating correct cache headers, this could be used for end users both for static content as well as normal endpoints such as GETs. This'll help leverage cache behaviour in browsers, but also http clients that respects cache-headers.
Additional context
This could live as part of Javalin such as the Validation module.
Article about how cache headers work (and don't work):
https://csswizardry.com/2019/03/cache-control-for-civilians/
Relevant as the new static files API allows headers:
https://github.com/tipsy/javalin/issues/1223#issuecomment-830635531

@tipsy Also mentioned we could think about a DSL for CSP as it's equally hard to get right. There's a high effort to get this done correctly though, and we'd love to see if anyone would be interested before investing any time creating these :)

I'll work on this.

@shafique-md18 any progress? 😄

This has been open for more than a year with little to no interest, so I will close it.