Paket doesn't properly respect MonoAndroid7.0 dependencies on Xamarin.Forms package

Description
Xamarin.Forms >= 2.3.4 depends Xamarin.Android.Support.* packages >= 23.3, but for MonoAndroid1, it is pinned at exactly 23.3.
Paket always assumes it needs to be exactly 23.3
Repro steps
This paket.dependencies file will fail:
content: none
redirects: on
source https://www.nuget.org/api/v2/

nuget Xamarin.Forms <IP_ADDRESS>
nuget Xamarin.Android.Support.Design <IP_ADDRESS>

Expected behavior
Same as NuGet, both packages must install, as they're compatible
Actual behavior
Paket version 5.96.1
Resolving packages for group Main:
 - Xamarin.Android.Support.Design is pinned to <IP_ADDRESS>
 - Xamarin.Forms is pinned to <IP_ADDRESS>
Performance:
 - Resolver: 2 seconds (1 runs)
    - Runtime: 317 milliseconds
    - Blocked (retrieving package details): 317 milliseconds (2 times)
    - Blocked (retrieving package versions): 1 second (2 times)
 - Average Request Time: 448 milliseconds
 - Number of Requests: 16
 - Runtime: 3 seconds
Paket failed with
-> There was a version conflict during package resolution.
     Resolved packages:
      - Xamarin.Android.Support.Design <IP_ADDRESS>
     Conflict detected:
      - Dependencies file requested package Xamarin.Android.Support.Design: <IP_ADDRESS>
      - Xamarin.Forms <IP_ADDRESS> requested package Xamarin.Android.Support.Design: 23.3

     Please try to relax some conditions or resolve the conflict manually (see http://fsprojects.github.io/Paket/nuget-dependencies.html#Use-exactly-this-version-constraint).

Known workarounds

Use NuGet
Don't use Xam.Support > 23.3

Event specifying == doesn't work, with nuget Xamarin.Android.Support.v7.AppCompat == <IP_ADDRESS>:
Conflict detected:       - Dependencies file requested package Xamarin.Android.Support.v7.AppCompat: == <IP_ADDRESS>       - Xamarin.Android.Support.Design <IP_ADDRESS> requested package Xamarin.Android.Support.v7.AppCompat: <IP_ADDRESS>       - Xamarin.Forms <IP_ADDRESS> requested package Xamarin.Android.Support.v7.AppCompat: 23.3

@forki it seems like finally they got us ;)

oh myy...

what's the scoop?

So I guess you don't want to build for MonoAndroid1? I guess you might be able to filter that with framework restrictions ..

Paket by default/design tries to find a global solution of packages valid to compile for all frameworks. It will not (like Nuget) allow different versions of a single package.
Paket tells you that such a solution doesn't exist for your specified dependencies...
So you can either change your version or tell paket you don't care about monoandroid framework

== on the other hand should work as well if applied to the correct packages, but you basically will have an unsound resolution in that case.

Ah, so simple. Works :)
content: none
redirects: on
source https://www.nuget.org/api/v2/

nuget Xamarin.Forms <IP_ADDRESS> framework: MonoAndroid7.0
nuget Xamarin.Android.Support.Design == <IP_ADDRESS>
nuget Xamarin.Android.Support.v7.AppCompat == <IP_ADDRESS>

to make it very clear: This is abuse of the concept of a package.  I wished MS would be more careful...


feat: data viewer table for screenpipe data

/closes #969
/claim #969

this is wrong
it should be outside tauri, it's a pipe not in tauri
also should not require rust code and missing UI table

can you fix? i want to merge this ASAP, taking a 15h flight in a few hours, hopefully before

@louis030195
Moved to a pipe and added ui-monitoring table
https://github.com/user-attachments/assets/54ad74c5-07a9-4049-abb8-1979a7028e62

/approve


fix(User): Handle defined errors

This should fix the issues with camperbot and reduce the noise to opbeat

Eager to QA and merge this. Since this is touching a lot of critical production code I'd prefer to QA over Skype/hangouts so I can drill down into each change, understand its consequences, and ask about potential edge cases.

We've QA'd this together and are confident these changes shouldn't introduce any new issues.


fix: Restart buildkit after containerd when provisioning

Issue #, if available: Fixes #412
Description of changes:

Previously, only containerd was restarted after configuring it to use the data on the persistent disk. This changes the UUID of the server worker. BuildKit also needs to be restarted to use the proper UUID. See issue for why this is important.

Testing done:

Local testing

[x] I've reviewed the guidance in CONTRIBUTING.md

License Acceptance
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Seems like all of the errors on the tests are similar to this:
Finch Container Development E2E Tests save an image when the images exist should save multiple images with --output option
/Users/ec2-user/go/pkg/mod/github.com/runfinch/common-tests@v0.7.0/tests/save.go:73
  7ad7d303eef13a1d2f7cea1b13e6f5ad271e72836ed8b7104e705a8d60d74290
  No containers to be removed
  9977826e0d1d
  No images to be removed
  889f8d4032e4d9758db5fde95109c1028b52b51739f15b112690c6a150abf9a4
  bridge
  host
  none
  No networks to be removed
  2023-06-27 16:30:21.873538484 +0000 UTC finch /images/create {"name":"localhost:58043/alpine:latest"}
  cdfb4bbd2199
  2023-06-27 16:30:22.605963755 +0000 UTC finch /images/create {"name":"public.ecr.aws/docker/library/alpine:3.13"}
  469b6e04ee18
  time="2023-06-27T16:30:22Z" level=fatal msg="failed to get reader: content digest sha256:25f523f0e93b2b5fa676c15d91b90f08ee4de7a160874e6c52ea452929d5a7cc: not found"
  time="2023-06-27T16:30:22Z" level=fatal msg="exit status 1"
  [FAILED] in [It] - /Users/ec2-user/go/pkg/mod/github.com/runfinch/common-tests@v0.7.0/command/command.go:122 @ 06/27/23 16:30:22.866

Wondering if its because of the way the public.ecr.aws/docker/library/alpine:3.13 repo is cached in our local registry. Taking a look.

Been seeing some of these failures across a few different PRs. Potentially not related to your changes.

I reran the CI on #455, and it didn't hit these errors. I think its something related to this one

The tests are failing here on this PR and on the finch-core repo. The similarity? Both are now running with synced containerd/buildkit worker UUIDs. Looking into when this started happening.

I've pulled your changes down locally, verified that the UUIDs are matching, but can't reproduce the e2e test locally.
These tests have been failing on finch-core since e2e tests were added. The difference between finch and finch-core e2e tests is that finch-core e2e 1/ runs a slightly different Fedora VM and 2/ runs tests with nerdctl as the test subject rather than finch.

Both are now running with synced containerd/buildkit worker UUIDs

True, but for some reason the Fedora VM used in finch-core e2e tests doesn't require this buildkit systemd service ordering change to enforce that UUID match... see https://github.com/runfinch/finch-core/blob/eaeaa96443a633d49d51143373650a93ab83a467/e2e/fedora.yaml#L148-L150
Here's my results using https://github.com/runfinch/finch-core/blob/main/e2e/fedora.yaml:
[giinglis@lima-finch finch-core]$ uname -a
Linux lima-finch 6.1.18-200.fc37.aarch64 #1 SMP PREEMPT_DYNAMIC Sat Mar 11 16:03:54 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux
[giinglis@lima-finch finch-core]$ sudo ctr info
{
    "server": {
        "uuid": "226df813-f172-43e2-ba4f-97d015bdca4d",
        "pid": 1794,
        "pidns":<PHONE_NUMBER>
    }
}
[giinglis@lima-finch finch-core]$ sudo buildctl debug workers --format "{{json .}}" | jq -r '. | .[].labels'
{
  "org.mobyproject.buildkit.worker.containerd.namespace": "default",
  "org.mobyproject.buildkit.worker.containerd.uuid": "226df813-f172-43e2-ba4f-97d015bdca4d",
  "org.mobyproject.buildkit.worker.executor": "containerd",
  "org.mobyproject.buildkit.worker.hostname": "lima-finch",
  "org.mobyproject.buildkit.worker.network": "host",
  "org.mobyproject.buildkit.worker.selinux.enabled": "false",
  "org.mobyproject.buildkit.worker.snapshotter": "overlayfs"
}

The changes in this PR do what we expect, which is sync the UUIDs for buildkit and containerd. finch save is where we are seeing CI failures. The high level behavior of finch save -o file.tar image1 image2 should work - by that mean both nerdctl and docker have this feature. Still investigating why we're seeing these test failures in save once UUIDs are synced...

tl;dr for CI issues here is garbage collection labels not being set properly. I got to the bottom of it and opened an issue on nerdctl https://github.com/containerd/nerdctl/issues/2372, but in reality this is a bug with buildkitv0.11.x . The bug has been patched in https://github.com/moby/buildkit/pull/3972 which was included in buildkitv0.12.0 which was released just yesterday: https://github.com/moby/buildkit/releases/tag/v0.12.0.
Opened up https://github.com/containerd/nerdctl/pull/2374 to upgrade nerdctl's buildkit to v0.12.0. Let's keep this PR open until we have both a new nerdctl release with the upgrade and a new Lima release pointing to the new nerdctl release.

Should be able to rebase and re-run CI now #521 has been merged with dependency upgrades

Should be able to rebase and re-run CI now #521 has been merged with dependency upgrades

Just rebased 🤞

Benchmarking steps:

git clone https://github.com/apache/couchdb-docker.git (just an example image with a lot of / large layers)
cd couchdb-docker/3.3.2
clear all layers / images finch system prune -a -f
regular build with Finch 0.7.0 time finch build -t couchdb .

the time is 49s on my PC

clear all layers / images again finch system prune -a -f
do build with options that simulate the fix time finch build -t couchdb --output 1. type=image,unpack=true .

time is 37s on my PC

49/37 = 1.33, so 33% increase in performance


[HW] Jeferson Vaz dos Santos

Name: Jeferson Vaz dos Santos
Email<EMAIL_ADDRESS>Linkedin Profile: https://www.linkedin.com/in/jefo2k/
Attach the homework screenshots below for both step II and step III:

The first image is not correct, it is not showing the select before de deletion. This is the right one:

Thank you!

You may need to attach "Congratulations!" screenshots from https://www.datastax.com/node/3272 and https://www.datastax.com/dev/scenario/try-it-out-cassandra-query-language-cql as well, @jefo2k .

Hello, Jeferson, well done! You did the CQL Console part of the homework.
But to complete it, please head to the two short courses as in the 'homework' section of the README, finish them, and post their "congratulations" screenshot. Then we will be able to award you the badge!
Thank you!


Egg Writer: Support exporting of tags

The biggest feature missing from this is tags. I've added the most commonly used (or any that for some reason i have had to use throughout the past couple of years maintaining my own local fork of the plugin)
This is best used in conjunction with a plugin that provides a simple interface for adding and validating panda3d tags - I am working on a plugin for that separately unless you think having that feature would fit into this.
Currently supported tags:
Scalar Tags:
Tags that are written to the egg as <Scalar> tag { value }

collide-mask
into-collide mask
from-collide mask
alpha
bin
scroll_u
scroll_v
decal
draw_order
occluder
fps

Single Value Tags
Tags that are written to the egg as <TagName> { value }

ObjectType
Collide
Billboard
Switch
DCS

"Special" Tags
Tags that don't follow a repeatable pattern

SwitchCondition
Instance

Issue resolved from PR #4


Onlyoffice App 1.1.5 on Nextcloud 12 does not save settings for Onlyoffce docker server

Hello,
I am running Nextcloud 12.0.3 on Ubuntu 16.04 with the Onlyoffice 1.1.5 app. If I enter my domain and secret in the settings page and click save, I get the following error (Onlyoffice is running in a Docker container on a Fedora 26 server):
{"reqId":"WgSVQX8AAQEAABPClAUAAAAN","level":1,"time":"2017-11-09T18:50:01+01:00","remoteAddr":"<IP_ADDRESS>","user":"user","app":"onlyoffice","method":"PUT","url":"\/owncloud\/apps\/onlyoffice\/ajax\/settings","message":"Set default formats: {\"docx\":\"true\",\"xlsx\":\"true\",\"pptx\":\"true\",\"ppsx\":\"true\",\"txt\":\"false\",\"csv\":\"false\"}","userAgent":"Mozilla\/5.0 (X11; Linux x86_64; rv:52.9) Gecko\/20100101 Goanna\/3.4 Firefox\/52.9 PaleMoon\/27.6.0","version":"<IP_ADDRESS>"}
{"reqId":"WgSVQX8AAQEAABPClAUAAAAN","level":1,"time":"2017-11-09T18:50:01+01:00","remoteAddr":"<IP_ADDRESS>","user":"user","app":"onlyoffice","method":"PUT","url":"\/owncloud\/apps\/onlyoffice\/ajax\/settings","message":"Set opening in a same tab: false","userAgent":"Mozilla\/5.0 (X11; Linux x86_64; rv:52.9) Gecko\/20100101 Goanna\/3.4 Firefox\/52.9 PaleMoon\/27.6.0","version":"<IP_ADDRESS>"}
{"reqId":"WgSVbn8AAQEAABPBBTEAAAAK","level":1,"time":"2017-11-09T18:50:45+01:00","remoteAddr":"<IP_ADDRESS>","user":"user","app":"onlyoffice","method":"PUT","url":"\/owncloud\/apps\/onlyoffice\/ajax\/settings","message":"SetDocumentServerUrl: https:\/\/server\/","userAgent":"Mozilla\/5.0 (X11; Linux x86_64; rv:52.9) Gecko\/20100101 Goanna\/3.4 Firefox\/52.9 PaleMoon\/27.6.0","version":"<IP_ADDRESS>"}
{"reqId":"WgSVbn8AAQEAABPBBTEAAAAK","level":1,"time":"2017-11-09T18:50:45+01:00","remoteAddr":"<IP_ADDRESS>","user":"user","app":"onlyoffice","method":"PUT","url":"\/owncloud\/apps\/onlyoffice\/ajax\/settings","message":"SetDocumentServerInternalUrl: ","userAgent":"Mozilla\/5.0 (X11; Linux x86_64; rv:52.9) Gecko\/20100101 Goanna\/3.4 Firefox\/52.9 PaleMoon\/27.6.0","version":"<IP_ADDRESS>"}
{"reqId":"WgSVbn8AAQEAABPBBTEAAAAK","level":1,"time":"2017-11-09T18:50:46+01:00","remoteAddr":"<IP_ADDRESS>","user":"user","app":"onlyoffice","method":"PUT","url":"\/owncloud\/apps\/onlyoffice\/ajax\/settings","message":"SetStorageUrl: ","userAgent":"Mozilla\/5.0 (X11; Linux x86_64; rv:52.9) Gecko\/20100101 Goanna\/3.4 Firefox\/52.9 PaleMoon\/27.6.0","version":"<IP_ADDRESS>"}
{"reqId":"WgSVbn8AAQEAABPBBTEAAAAK","level":1,"time":"2017-11-09T18:50:47+01:00","remoteAddr":"<IP_ADDRESS>","user":"user","app":"onlyoffice","method":"PUT","url":"\/owncloud\/apps\/onlyoffice\/ajax\/settings","message":"Set secret key","userAgent":"Mozilla\/5.0 (X11; Linux x86_64; rv:52.9) Gecko\/20100101 Goanna\/3.4 Firefox\/52.9 PaleMoon\/27.6.0","version":"<IP_ADDRESS>"}
{"reqId":"WgSVbn8AAQEAABPBBTEAAAAK","level":0,"time":"2017-11-09T18:50:47+01:00","remoteAddr":"<IP_ADDRESS>","user":"user","app":"onlyoffice","method":"PUT","url":"\/owncloud\/apps\/onlyoffice\/ajax\/settings","message":"CommandRequest on check: {\"error\":0,\"version\":\"<IP_ADDRESS>\"}","userAgent":"Mozilla\/5.0 (X11; Linux x86_64; rv:52.9) Gecko\/20100101 Goanna\/3.4 Firefox\/52.9 PaleMoon\/27.6.0","version":"<IP_ADDRESS>"}
{"reqId":"WgSVd38AAQEAABRlKlcAAAAS","level":0,"time":"2017-11-09T18:50:47+01:00","remoteAddr":"<IP_ADDRESS>","user":"--","app":"onlyoffice","method":"GET","url":"\/owncloud\/apps\/onlyoffice\/empty?doc=L2NobU9NVEF4NURCcU5iZlpaczZTMk1rNzF6WG5oRlBpV0REVHFBU21Ccz0\/eyJhY3Rpb24iOiJlbXB0eSJ9","message":"Download empty","userAgent":"--","version":"<IP_ADDRESS>"}
{"reqId":"WgSVd38AAQEAABRlKlcAAAAS","level":1,"time":"2017-11-09T18:50:47+01:00","remoteAddr":"<IP_ADDRESS>","user":"--","app":"onlyoffice","method":"GET","url":"\/owncloud\/apps\/onlyoffice\/empty?doc=L2NobU9NVEF4NURCcU5iZlpaczZTMk1rNzF6WG5oRlBpV0REVHFBU21Ccz0\/eyJhY3Rpb24iOiJlbXB0eSJ9","message":"Download empty with invalid jwt: Expired token","userAgent":"--","version":"<IP_ADDRESS>"}
{"reqId":"WgSVeX8AAQEAABQvbGQAAAAI","level":0,"time":"2017-11-09T18:50:49+01:00","remoteAddr":"<IP_ADDRESS>","user":"--","app":"onlyoffice","method":"GET","url":"\/owncloud\/apps\/onlyoffice\/empty?doc=L2NobU9NVEF4NURCcU5iZlpaczZTMk1rNzF6WG5oRlBpV0REVHFBU21Ccz0\/eyJhY3Rpb24iOiJlbXB0eSJ9","message":"Download empty","userAgent":"--","version":"<IP_ADDRESS>"}
{"reqId":"WgSVeX8AAQEAABQvbGQAAAAI","level":1,"time":"2017-11-09T18:50:49+01:00","remoteAddr":"<IP_ADDRESS>","user":"--","app":"onlyoffice","method":"GET","url":"\/owncloud\/apps\/onlyoffice\/empty?doc=L2NobU9NVEF4NURCcU5iZlpaczZTMk1rNzF6WG5oRlBpV0REVHFBU21Ccz0\/eyJhY3Rpb24iOiJlbXB0eSJ9","message":"Download empty with invalid jwt: Expired token","userAgent":"--","version":"<IP_ADDRESS>"}
{"reqId":"WgSVe38AAQEAABRgeEUAAAAN","level":0,"time":"2017-11-09T18:50:51+01:00","remoteAddr":"<IP_ADDRESS>","user":"--","app":"onlyoffice","method":"GET","url":"\/owncloud\/apps\/onlyoffice\/empty?doc=L2NobU9NVEF4NURCcU5iZlpaczZTMk1rNzF6WG5oRlBpV0REVHFBU21Ccz0\/eyJhY3Rpb24iOiJlbXB0eSJ9","message":"Download empty","userAgent":"--","version":"<IP_ADDRESS>"}
{"reqId":"WgSVe38AAQEAABRgeEUAAAAN","level":1,"time":"2017-11-09T18:50:51+01:00","remoteAddr":"<IP_ADDRESS>","user":"--","app":"onlyoffice","method":"GET","url":"\/owncloud\/apps\/onlyoffice\/empty?doc=L2NobU9NVEF4NURCcU5iZlpaczZTMk1rNzF6WG5oRlBpV0REVHFBU21Ccz0\/eyJhY3Rpb24iOiJlbXB0eSJ9","message":"Download empty with invalid jwt: Expired token","userAgent":"--","version":"<IP_ADDRESS>"}
{"reqId":"WgSVbn8AAQEAABPBBTEAAAAK","level":3,"time":"2017-11-09T18:50:54+01:00","remoteAddr":"<IP_ADDRESS>","user":"user","app":"onlyoffice","method":"PUT","url":"\/owncloud\/apps\/onlyoffice\/ajax\/settings","message":"CommandRequest on check error: Im Dokumentenservice ist ein Fehler aufgetreten: Error while downloading the document file to be converted.","userAgent":"Mozilla\/5.0 (X11; Linux x86_64; rv:52.9) Gecko\/20100101 Goanna\/3.4 Firefox\/52.9 PaleMoon\/27.6.0","version":"<IP_ADDRESS>"}
{"reqId":"WgSVbn8AAQEAABPBBTEAAAAK","level":1,"time":"2017-11-09T18:50:55+01:00","remoteAddr":"<IP_ADDRESS>","user":"user","app":"onlyoffice","method":"PUT","url":"\/owncloud\/apps\/onlyoffice\/ajax\/settings","message":"Set default formats: {\"docx\":\"true\",\"xlsx\":\"true\",\"pptx\":\"true\",\"ppsx\":\"true\",\"txt\":\"false\",\"csv\":\"false\"}","userAgent":"Mozilla\/5.0 (X11; Linux x86_64; rv:52.9) Gecko\/20100101 Goanna\/3.4 Firefox\/52.9 PaleMoon\/27.6.0","version":"<IP_ADDRESS>"}
{"reqId":"WgSVbn8AAQEAABPBBTEAAAAK","level":1,"time":"2017-11-09T18:50:55+01:00","remoteAddr":"<IP_ADDRESS>","user":"user","app":"onlyoffice","method":"PUT","url":"\/owncloud\/apps\/onlyoffice\/ajax\/settings","message":"Set opening in a same tab: false","userAgent":"Mozilla\/5.0 (X11; Linux x86_64; rv:52.9) Gecko\/20100101 Goanna\/3.4 Firefox\/52.9 PaleMoon\/27.6.0","version":"<IP_ADDRESS>"}

Download empty with invalid jwt: Expired token
Check the time on both servers

Thanks, that worked. Is it possible to make the error message more precise?

JWT error is described: Expired token


Issue with EXCEPTION System.UnauthorizedAccessException

Account Id:
Application version: 5.2.70
Auth user Id:
Browser version:
City: Ottawa
Client IP address: <IP_ADDRESS>
Cloud role name:
CLR version: 3.0.0-preview7.19327.2+ac4ab6c990d5ebee49dc03397a2e199241021f26
Country or region: Canada
Device model: Precision 5510
Device type: PC
Environment: store
Event time: 7/31/2019, 2:06:03 PM
Exception type: System.UnauthorizedAccessException
Failed method: NuGet.Protocol.HttpCacheUtility+d__2.MoveNext
Network type: Ethernet
Operating system: Windows 10.0.18362
Operation Id:
Operation name:
Parent Id:
Problem Id: System.UnauthorizedAccessException at NuGet.Protocol.HttpCacheUtility+d__2.MoveNext
Sample Rate: 100
SDK version: dotnetc:2.10.0-31626
Session Id: 48d95c28-0d98-4b1f-894a-46686eb1f13e
Source of synthetic traffic:
State or province: Ontario
Telemetry type: exception
Thread culture: en-US
Time zone: Eastern Standard Time
UI culture: en-US
User Id: hvARreyv9doBCaXOwR/Gp0Mg3Q9twxa79FtUm61tNww=
WPF version: 4.8.0-preview7.19352.4+76573a9bb7ab5cd61dbf4456600631e63accf5c0
View this instance in the Azure portal<\a>
View similar exceptions in this time range<\a>

We should guard against this, though there's not much we can do but swallow it.


Using new .Net Core 3.0 IAsyncEnumerable

C# 8 introduced functionality to trivially use IAsyncEnumerable as described at this MSDN article. Unfortunately, the IReliableDictionary2 uses an internal representation of both IAsyncEnumerable and IAsyncEnumerator at Microsoft.ServiceFabric.Data.
Given that IReliableDictionary3 is still a work in progress, is there any chance it will be updated to utilize these new standard interfaces so keys can be trivially iterated with async foreach, especially since these are compatible with .NET Standard 2.0 and thus would fit well with the 8.x rollout described in the release notes to support .NET Core 2.0?

i've love to see SF using system.collections.generic.IAsyncEnumerable


Add role for clustermanagementaddon/finalizers

Add update permissions for clustermanagementaddon/finalizers. This is required by addon framework to operate clustermanagementaddons.

/approve


knowledge - When users closes the Please Sign In to continue page (without going thru the oauth flow), We are not able to present the oauth workflow again.

Steps to reproduce the problem:

Create an agent with knowledge from onedrive link.
When  presented with the Please Sign In to continue page , close this page without going thru the oauth flow.

This results in sync state being in "Pending"

Close this page.
The onedrive link will be shown in "Syncing" state. Use Edit option to launch the onedrive page .

We are stuck in the following state forever.

Expected Behavior:
User should be presented with the oauth workflow again.

I investigated this. You don't get stuck in this state forever, it will eventually recover. I will make changes such that it recovers more quickly.

This issue is not seen anymore. Oauth workflow is presented again in the scenario mentioned in the issue for both notion and onedrive.


Add getClientIP() to HTTPRequest

Adds the method getClientIP() to the HTTPRequest class.
Usage in handler function or middleware:
IPAddress clientIP = req->getClientIP();

Resolves:

#70

Tested works!


Update testnet with new values

Background
We have a laundry list of items which need to go into the new testnet.
Done when

[x]  New Validator Set whitelist (internal only - Taariq, Chase, Jason, Vera)
[x]  updated genesis file with starting grains for Volume users and validators

[x]  5 Billion GRAINs at genesis
[x]  250MM Grains each to control network

[x]  Jason Address
[x]  Vera Address
[x]  Chase Address
[x]  Taariq Address

[x]  Server Size: 16 GB RAM
[x]  Starting Addrbook: Post to Github

https://github.com/palomachain/testnet/blob/master/passerina/addrbook.json

[x]  Faucet: 500MM

[x]  Faucet: 100,000 GRAINs
[x]  CLI faucet
[x]  Faucet Front-end

@measure-fi can we do another checklist for today's testnet?

Updated Chain-ID to be announced at genesis
Updated Validator Minimum for staking: 1 GRAIN
Updated Denoms for GRAINs:  1 GRAIN == 1,000,000 ugrain

@taariq https://github.com/palomachain/paloma/issues/247


XDC_NETWORK not added to MASTER_COPIES and PROXY_FACTORIES in addresses.py

In the commit 46720973ea0af85ecae71694d870b6a4829e691a on January 23rd, the XINFIN_XDC_NETWORK constant was updated to XDC_NETWORK in the ethereum_network.py file. However, the corresponding change was not made in the safe/addresses.py file.
In safe/addresses.py, the XINFIN_XDC_NETWORK was removed from the MASTER_COPIES and PROXY_FACTORIES dictionaries, but it was not replaced with XDC_NETWORK. As a result, the library is unable to trace transactions on the XDC Network.
To resolve this issue, the following changes should be made in safe/addresses.py:

Add XDC_NETWORK to the MASTER_COPIES dictionary with the appropriate master copy address for the XDC Network.

Add XDC_NETWORK to the PROXY_FACTORIES dictionary with the correct proxy factory address for the XDC Network.

By making these changes, the safe-eth-py library will be able to properly trace transactions on the XDC Network.
Please update the safe/addresses.py file to include the XDC_NETWORK constant in the MASTER_COPIES and PROXY_FACTORIES dictionaries, ensuring consistency with the changes made in ethereum_network.py.

As we were having multiple issues adding addresses we added a new workflow for that, please use that template: https://github.com/safe-global/safe-eth-py/issues/new/choose
Sorry for the inconvenience


Setup help please

Hello,
I am really interested in trying out your framework. Could you elaborate a little bit more on the installation process please?
I did install Detectron2 and Fast-Transformer, but what should I do with DETR and Deformable-DETR, as you can't really install those as packages to your environment? Are these supposed to be added as submodules?
Thank you for your time.

Hi sorry, configs for running DQRF will be uploaded. You don't need Fast-Transformer module, as you can see here https://github.com/Hatmm/PED-DETR-for-Pedestrian-Detection/blob/20e3046a0a0701834befa4657e7db6b66adc9401/dqrf/ops/functions/local_attn.py#L156 you can obtain similar behavior by multiplying the weights of the self attention module by a binary mask where 1 correspond to the 100 nearest keys for each query. To train, don't forget to first convert you json using our provided code, then you can simply run train_net and specify the number of gpu and the path for you config for instance python $ROOT/train_net.py
--num-gpus $NUM_GPUS
--config-file $ROOT/configs/file.yaml


toolchain file specifies nightly, should specify a specific version of nightly

Specifying nightly uses the locally installed version of nightly, which may not have all necessary features. This also defeats the purpose of using a toolchain file, as users will compile using different versions from each other (the thing the toolchain file is intended to prevent). Instead, use a specific commit date, e.g. nightly-2023-01-01
It is also recommended that you document the supported rust version in the readme, so those of us with weird installs can compile more easily :)
E.g. Helios will not compile on versions without map_first_last feature, which was stabilized in rust 1.66.0 (which is only a month old!), and may not be present or active in earlier nightlies. Users who haven't updated their nightly in a month can't clone + compile without troubleshooting.
This could be a 1-line PR, but i didn't want to submit it without a discussion about it first 😅

Thanks for pointing this out. This makes sense to me. Do you want to open a PR to add a reasonable nightly version? If not I can do so.


Cannot read property 'name' of undefined

jspdf.min.js:202 Uncaught TypeError: Cannot read property 'name' of undefined
at j (jspdf.min.js:202)
at k (jspdf.min.js:202)
at k (jspdf.min.js:202)
at jspdf.min.js:202
at l (jspdf.min.js:202)
at d (jspdf.min.js:202)
at m (jspdf.min.js:202)
at Object.t.fromHTML (jspdf.min.js:202)
at generate (DVN.js:19)
at HTMLButtonElement.onclick (download.aspx:205)

We are closing this issue, because we won't support any longer fromHTML and addHTML.
Best Regards

To fix this issue, colspan must be removed from HTML code of table.
It worked for me, Hope will for you also.
Thanks & Regards


Add Batch Drawable in the Newest Version(0.3.2) doesn't Work Exactly in Android Studio.

When press the "Add" Button, it can only show images under the root directory.

This is a duplicate of #94

I just uploaded a new release to the JetBrains plugin repository. Hopefully it will be published by them soon.


When, if at all, is it safe to drop root in a daemon that uses pigpio?

There are lots of warnings that pigpio uses /dev/mem, and hence needs to run as root.  That's fine.
I'm building a C daemon that will use pigpio.  I'd rather not keep it running as root if there's an alternative.  Is there a point after which the devices are open, and hence it's possible for the daemon to drop root?  If so, when - directly after gpioInitialise(), for example?
Yes, I know that given write access to /dev/mem in the process, this is rather akin to shutting the stable door after the horse has ambled into the field, had a good meal and a nap, looked around, and galloped into the next county.  But let me secure the small things, eh? :-)

If you write your daemon using pigpiod_if you won’t need root privilege.

If you write your daemon using pigpiod_if you won’t need root privilege.

True.  Not convinced that reduces the attack surface, however - does pigpiod drop root once it's started?  If so, presumably I can look at its approach and do the same.
Given what I'm using this stuff for (factory automation), I'd also prefer to have the smallest possible amount of code to validate and the fewest possible moving parts in the solution.  I'm not a great fan of large machines going haywire on error and someone having to press the Big Red Mushroom Button and clean the mess off the floor :-).


Flush thread becomes bottle neck when use real S3.

We only have one flush thread to flush mem-tables of all shards, so files are written to S3 sequentially.
Because writing a single file to S3 latency is high(about 300ms),  If the write workload is heavy, it becomes the bottleneck, then the flush channel will be full, blocks the apply thread.
To solve this problem, we should concurrently write files to S3 and sequentially produce the result.

Fixed by https://github.com/ngaut/unistore/pull/616


init processor

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#5  👈
#4
#3
#2
#1
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @buffalojoec and the rest of your teammates on  Graphite


Request / Drag nearest point

As you might know, we can set the mode 'nearest' to trigger the hover action of the points and the tooltips.
options = {
    hover: {
        mode: 'nearest',
        intersect: false
    },
    tooltips: {
        mode: 'nearest',
        intersect: false
    }
};

It would be perfect that the drag action would work once the point is activated with the 'nearest' mode instead of actually needing to hover over the point.
Thank you

Hey three,
I think that would be awesome! However, I didn't have the time to think about what would be the best way to achieve this. If you got an idea it would be highly appreciated.
Best
Christoph

Hi @Shakarhaba, I've forked the project and added the feature, if you want to try check it out!

Thanks a lot @velthune for the great implementation ❤ I hope this is what @Shakarhaba was looking for, in any way it's a great addition. Will close this for now, please re-open if this doesn't answer the issue.


chore(main): release 1.2.1

:robot: I have created a release beep boop
1.2.1 (2024-06-30)
Bug Fixes

ci: issue with release workflow (#17) (2cf4b6a)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.2.1
:sunflower:


Instructions on how to build sqlite3.exe

Windows support with sqlite3.exe
cmd
scoop install llvm openssl-mingw llvm-mingw
cargo build --release -p mvsqlite` Works on Windows 11.
cd mvsqlite/mvsqlite
# Tinkering with shims see zip.
gcc -O2 -o sqlite3 sqlite3.c shell.c shim.c preload.c -L../target/release -LC:/Users/elee/scoop/apps/openssl-mingw/current/lib64 -lmvsqlite -lssl -lcrypto -lWs2_32 -lbcrypt -lUserenv -lntdll
set RUST_LOG=info
set MVSQLITE_DATA_PLANE=http://localhost:7000
sqlite3.exe test
.vfslist
  2022-10-19T05:05:35.621924Z  INFO mvsqlite: mvsqlite initialized, default_sector_size: 8192
    at mvsqlite\src\lib.rs:174

SQLite version 3.39.3 2022-09-05 11:02:23
Enter ".help" for usage hints.
sqlite> .vfslist
vfs.zName      = "mvsqlite"  <--- CURRENT
[...]

mvsqlite.zip
We are assuming that the fdb and mvstore is in an ubuntu os. That they've been started and the admin interface has been used to create a test database.
Other notes
The dependencies openssl-devel are required for ssl and crypto. Might be able to use mbedtls.

I made partial godot engine sqlite module. It's partial because it doesn't store the rust code. It fetches the static library from the Windows 11 filesystem.
https://github.com/V-Sekai/godot-sqlite/tree/mvsqlite

I told godot to do a listing of the database tables.

Closing because I am using this and it appears to work for me.


Fix for gma android failing assert

Description
Fix for gma android failing assert

Testing
None.

Type of Change
Place an x the applicable box:

[x] Bug fix. Add the issue # below if applicable.
[ ] New feature. A non-breaking change which adds functionality.
[ ] Other, such as a build process or documentation change.

Notes
NativeAd's getIcon() for android and icon() for iOS are nullable API methods and this indicates that ads returned will not always guarantee the availability of an icon asset. This PR relaxes the restriction which expects an icon asset at all times and processes the contents of an icon asset, only when a valid icon image asset is returned by andriod/iOS layers.
Ref: https://developers.google.com/admob/ios/api/reference/Classes/GADNativeAd#icon
Also updates the integration test to look for a large image asset rather than an icon asset, as the test ad unit ids are always expected to return a valid large image asset on a successful ad load.

Could you add a more detailed description to the PR about what was causing the assert and what this fix does?

Added a bit of explanation in the description about the failing assert.


UI doesn't hide when entering fullscreen on Tizen

Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
v2.5.6
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from master?
Didn't test
Are you using the demo app or your own custom app?
Demo app
If custom app, can you reproduce the issue using our demo app?
What browser and OS are you using?
Tizen 2017
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
What are the manifest and license server URIs?
Any asset
What did you do?

Load asset
Click fullscreen button on UI
Don't move cursor

What did you expect to happen?
UI should hide after going to fullscreen.
What actually happened?
UI remains visible until you move the cursor again.

@TheModMaker does this only repro on Tizen?

I saw this on Tizen and didn't see this on Desktop, so probably.

@joeyparrish I checked this problem doesn't exist on Chrome or Firefox browser  OS-Ubuntu.


[MBL-1208] Part 1: Initial ConfirmDetailsViewController | Shipping Location + Pledge/Bonus Steppers

📲 What
Part 1 in the breakdown of adding a new Confirm Details Screen
When a user selects an option in the rewards screen, navigate to the new screen.

To keep these PRs small, the new view controller, right now, only displays the shipping location selector and pledge/bonus steppers. See the designs for reference.

🤔 Why
This screen will allow backers to confirm their pledge info before reaching the final checkout screen. This allows us to call PCP validation mutations before creating stipe intents and initializing the payment sheet.
🛠 How
This initiative is time-sensitive and is part of our more complicated and very important checkout flow. With that in mind, I'm choosing to follow existing patterns closely rather than spending more time refactoring or using new patterns like SwiftUI or Combine.
Navigation sources: RewardAddOnSelectionViewController and RewardsCollectionViewController
👀 See

✅ Acceptance criteria

[x] Navigating to new VC when selecting a $1 pledge with no reward only shows the pledge stepper
[x] Navigating to new VC when selecting a pledge with a digital reward and no add-ons shows only the bonus stepper
[x] Navigating to new VC when selecting a pledge with a physical reward and no add-ons shows the shipping dropdown selector and bonus stepper
[x] Navigating to new VC when selecting a pledge with a physical reward that includes add-ons shows the static dropdown info and bonus stepper

⏰ TODO

[x] Unit tests for the view model. This is pretty involved so I wanted to get the review on this started in the meantime
Part 2 will be all about adding the pledge total section https://github.com/kickstarter/ios-oss/pull/1970

          1 Warning

:warning:
Big PR

  Generated by :no_entry_sign: Danger

          1 Warning

:warning:
Big PR

  Generated by :no_entry_sign: Danger

          1 Warning

:warning:
Big PR

  Generated by :no_entry_sign: Danger

          1 Warning

:warning:
Big PR

  Generated by :no_entry_sign: Danger

          1 Warning

:warning:
Big PR

  Generated by :no_entry_sign: Danger

          1 Warning

:warning:
Big PR

  Generated by :no_entry_sign: Danger

@amy-at-kickstarter Thanks for your comments. Your re-structure suggestions are super valid. I think that it's ok to move on with this for now though. I want this flow to be an early candidate for SwiftUI/Combine re-work, which will address a lot of these concerns and I'd like to only address blocking comments for now to keep PCB progressing

@amy-at-kickstarter Thanks for your comments. Your re-structure suggestions are super valid. I think that it's ok to move on with this for now though. I want this flow to be an early candidate for SwiftUI/Combine re-work, which will address a lot of these concerns and I'd like to only address blocking comments for now to keep PCB progressing

Yup, I'm fine with that. Just want to have some thoughts on the record for any future work we end up still doing in ReactiveSwift!


What is the required data / subscriptions to routes when autopublish is removed?

Specifically I can't seem to find any info on how to get the reset password stuff to work when you remove auto publish.
Any help would be greatly appreciated

This should work out-of-the-box when you remove autopublish. What issues are you running into?
To get reset password to work, you need to configure a mail server.

The routes don't load, I get 'did you forget to call this.next()' when I click on the reset link

That shouldn't be an issue of useraccounts package itself I think... Check your onBeforeAction hooks on your iron routes. I also can't imagine this having anything to do with autopublish, unless maybe the subscriptions are failing?

I tried removing all of my onbefore actions and i still can't get it to work. What publications are required for the password reset token to work?

Ok I got it sorted out. There was indeed another file with a before action which was the problem.
However if someone does want to know how to configure the routes with iron router when you have an app that requires a user for every route you have to configure reset password like this:
AccountsTemplates.configureRoute('resetPwd', {
  waitOn: function(){
    return Meteor.subscribe('enrolledUser',this.params.paramToken);
  },
  data: function(){
    if(Meteor.userId())  Router.go('root');
    else return Meteor.users.findOne();
  }
});

And your enrolledUser publication:
Meteor.publish('enrolledUser', function(token) {
  check(token, Match.Any);
  return Meteor.users.find({"services.password.reset.token": token}, {fields: {_id: 1}});
});

I'm pretty sure you don't need anything like that to get your reset password route to work.
It's just the official Accounts API that lets you veryfy tokens
Lets try with the bootstrap boilerplate (after autopublish removal...) which was updated to use the lates versions of useraccounts packages...


Q&A RAG pipeline with MongoDB, Hugging Face and Llama3

What does this PR do?
Description of Changes: This update introduces an integrated pipeline using Retrieval-Augmented Generation (RAG) with MongoDB and Hugging Face's open-source Llama3 model for advanced question answering systems. The implementation covers the setup of a MongoDB database, data ingestion, vector search, and leveraging Llama3 for generating responses. These modifications aim to showcase how combined database and NLP technologies can improve data retrieval and processing capabilities for complex queries.
Motivation and Context: This change was motivated by the need to demonstrate practical applications of combining cutting-edge NLP models with modern database systems for educational and development purposes in the fields of AI and data science.
Dependencies:

datasets for loading and processing the data.
pandas for data manipulation.
pymongo for interacting with MongoDB.
sentence_transformers for generating text embeddings.
transformers for accessing pre-trained models from Hugging Face.

Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[X ] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a Github issue? Please add a link
to it if that's the case.
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

Thanks for contributing 🎉!

@HamidShojanazeri Thanks for reviewing very quickly.
I have made the modifications and suggested changes.
Richmond

@jeffxtang Thanks for pointing out these issues.
I have addressed them and added screenshots where appropriate.

Thanks @RichmondAlake for the changes and the screenshots. I tried following steps under Atlas UI (there're 10!) but got lost - I already logged in and completed the survey then I clicked Try Free and it asked me to Sign up/in again - with Sign in I saw the Overview - Create a deployment page, but the instructions with 10 steps page was no longer visible...
The RAG and Llama 3 parts look good, but I'm afraid many users will probably be stuck in the Mongodb setup...
Is there another simpler way to to showing MongoDB for this use case? A while ago I downloaded some Mongodb locally on Mac to use it with Llama 2, which worked pretty easily (the setup process and integration).
I can approve this PR if you're fine with the current DB setup process.

@jeffxtang thanks for your comment.
Please move forward with merging the PR.
I will work on the experience with the docs with our internal team.
Thanks for the review


Accept resource groups with sub_region under IPM

Specific context is transmission zones within ipm regions. Might have other uses.

Codecov Report

Merging #148 (988d02f) into develop (4b0213f) will decrease coverage by 0.10%.
The diff coverage is 0.00%.

:exclamation: Current head 988d02f differs from pull request most recent head 7c3b7fb. Consider uploading reports for the commit 7c3b7fb to get more accurate results

@@             Coverage Diff             @@
##           develop     #148      +/-   ##
===========================================
- Coverage    18.83%   18.73%   -0.10%
===========================================
  Files           18       18
  Lines         3101     3118      +17
===========================================
  Hits           584      584
- Misses        2517     2534      +17

Impacted Files
Coverage Δ

powergenome/nrelatb.py
6.47% <0.00%> (-0.02%)
:arrow_down:

powergenome/resource_clusters.py
12.84% <0.00%> (-0.59%)
:arrow_down:

powergenome/GenX.py
0.00% <0.00%> (ø)

...owergenome/run_powergenome_multiple_outputs_cli.py
0.00% <0.00%> (ø)

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 4b0213f...7c3b7fb. Read the comment docs.


signal.spectrogram doesn't change nperseg to length of window

From the mailing list, an issue with nperseg not adjusting to window in signal.spectrogram (https://mail.scipy.org/pipermail/scipy-dev/2016-November/021620.html):
from scipy.io import wavfile
from scipy.signal import slepian # i.e. 'DPSS' window used for FFT
from scipy.signal import spectrogram

FFT_SIZE = 512
FFT_OVERLAP = FFT_SIZE - 32
win_dpss = slepian(FFT_SIZE, 4/FFT_SIZE) #shape =

[rate,data] = wavfile.read('a_file_you_have.wav')
f,t,spec = spectrogram(data, rate, window=win_dpss, noverlap=FFT_OVERLAP)

@rgommers @Eric89GXL working on a fix now

Fixed by 93a0ea9


Downloaded DESM File Name Issue: Does Not Use the Full Specification Name and Concatenates the Mapper Name with and Incomplete Specification Name

This needs to be a priority 1 issue that goes along with the in progress export-related issues. In this case, it was a pain to have to go back and re-download and rename due to the downloaded file not having the full name. Seems like a quick fix.
When a mapping is downloaded, the name of the file is not correct.  It concatenates the name of the mapper and only part of the schema name.  This file name should be Open Badges 2.0 (1EdTech) - Issuer. It should not be what is seen in the download screenshot.  This issue cause me to have to keep track and rename each downloaded file to remove the mappers name and identify the full name of the specification.

As seen via, copy/paste below and the screenshot below the title is incorrect.
dcterms:title: "Nate Otto - Open Badges (1EdTech) - Micro-credential Specification",

I believe Phil has identied the name as an issue in respect to removing the name of the mapper. This issue shows that the full name of the specification is not used with the download and needs to be used everywhere in the UI and with the downloaded data.

@excelsior let me know if this leads to any file name conflicts

yes to removing the mappers name from the file name
I think it may need to be more just the title. (I'm not 100% sure what is in the title)
do you mean mapping version or schema version? Probably yes to both. Schema versions are important and it would help avoid name clashes if the date of mapping were in the file name.

We probably don't need the organization in the file name.
Can we not have spaces or brackets in file names please?

Ah, sorry, @excelsior  I think I misunderstood Q2. If you were asking what to put into the dc:title (rather than the other way how to use what was in it), then «project name»+«abstract class»+«schema name»+«schema version» (which is similar to now but without any person's name and in different order. That order will help group mappings when displayed alphabetically.
Add the last mod date to that at the end and I think you have the file name.

@excelsior Phil's concatenation for the title is what we should see via the UI and the downloaded file.


Fix aggregate temporal

Partial fix of https://github.com/Open-EO/openeo-processes-dask/issues/27
I added exceptions handling for aggregate_temporal and aggregate_temporal_period.

Test is failing because the temporal dimension set in the test data is t but in the code we set it to time the default value. @LukeWeidenwalker let me know how we should address this.

Ah, this will be easily fixed after https://github.com/Open-EO/openeo-processes-dask/pull/20 is merged - I think just set it to t for the time being to satisfy the tests, we won't be doing any deployments of this until the accessor is merged anyways!

Closing since @LukeWeidenwalker included the fixes in the commit https://github.com/Open-EO/openeo-processes-dask/commit/b3f1184c106b018021b09b0be195268c0960722b


Textures are bugged to by the LWJGL engine

When you start minecraft with the forbidden magic mod, minecraft crashes, everything works fine without it
log:
[00:17:52] [main/INFO]: Setting user: NaKaTa_
[00:17:54] [Client thread/INFO]: LWJGL Version: 2.9.1
[00:18:03] [Client thread/INFO]: Reloading ResourceManager: Default
[00:18:04] [Sound Library Loader/INFO]: Sound engine started
[00:18:05] [Client thread/INFO]: Created: 16x16 textures/blocks-atlas
[00:18:05] [Client thread/INFO]: Created: 16x16 textures/items-atlas
[00:18:09] [Client thread/INFO]: Stopping!

I start Minecraft with the mod just fine without any problems.  This log doesn't even tell me anything.


tests: add test cases for FTP logging

This PR adds tests for FTP logging. See (3093)[https://github.com/OISF/suricata/pull/3093]

Continued in #106


darkhttpd: 1.13 -> 1.14

Description of changes
https://github.com/emikulic/darkhttpd/releases/tag/v1.14
Fixes CVE-2020-25691.
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)
[ ] 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.11 Release Notes (or backporting 22.05 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 run on x86_64-linux 1

1 package built:

darkhttpd

<!--
To help with the large amounts of pull requests, we would appreciate your
reviews of other pull requests, especially simple package updates. Just leave a
comment describing what you have tested in the relevant package/service.
Reviewing helps to reduce the average time-to-merge for everyone.
Thanks a lot if you do!
<p>List of open PRs: https://github.com/NixOS/nixpkgs/pulls
Reviewing guidelines: https://nixos.org/manual/nixpkgs/unstable/#chap-reviewing-contributions
-->

Thank you for the quick response!


How to bulk update for only given documents

Hello All,
https://docs.microsoft.com/en-us/azure/cosmos-db/bulk-executor-dot-net#bulk-update-data-in-azure-cosmos-db
From above URL, I saw how to update all documents in cosmos DB. But I have to update only list of documents which i gave as input to bulkExecutor.BulkUpdateAsync.
So i am interested in updating only given documents not for all documents. is it possible?

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

ID: 14e425a8-0912-7516-b0e4-485f903c4003
Version Independent ID: 6d44d779-e35f-8101-3427-ebf59015a956
Content: Using bulk executor .NET library to perform bulk operations in Azure Cosmos DB
Content Source: articles/cosmos-db/bulk-executor-dot-net.md
Service: cosmos-db
GitHub Login: @tknandu
Microsoft Alias: ramkris

@vetrivelmp Thanks for your feedback! We will investigate and update as appropriate.

@vetrivelmp As part of the document you are referencing, there are two sections pertaining to the Bulk Executor.
Bulk import data to Azure Cosmos DB
And you have the Bulk update data in Azure Cosmos DB
.
The C# Example provides an update:
updateOperations.Add(nameUpdate); updateOperations.Add(descriptionUpdate);
The C# sample does not include a filter to identify the documents targeted for a bulk update but, you can include one to meet your needs.

@vetrivelmp We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

Was the question ever answered?  It doesn't seem so.  Yes, the documentation still does not show how to only update a select few documents.  But not sure why this is closed then?  Is this possible?  If so, how?

@jakehockey10 Thank you for bringing this to my attention. I believe at the time this functionality was verbally communicated without an example provided. Let me revisit this but did want to provide what is likely the method that will need to be used: See the Upsert a Document example from the Cosmos DB .NET SDK Document level examples.

Providing an update: .NET V3 SDK provides a bulk support feature. This article describes the required steps to migrate an existing application's code that uses the .NET bulk executor library to the bulk support feature in V3 of the .NET SDK.
You need to create tasks for each operation. There is no single method that will take your list of documents or operations as an input parameter, but rather, you need to create a Task for each operation you want to execute in bulk.

@Mike-Ubezzi-MSFT Thanks for the response.  Embarrassing, but I was using V3 in my API and went down to V2 for my ETL project because I thought that was the only place I could do bulk operations with the BulkExecutor library.
I appreciate you bringing this to my attention.  It has been a long day converting everything over to V3, but I'm glad I did it.
So is V2 BulkExecutor not worked on any more?  Was updating only a subset of the documents ever implemented for BulkExecutor?

@SnehaGunda and @markjbrown This is an older GitHub issue where there has been some bulk support introduced to the .NET v3 SDK. Is it desired to migrate away from BulkExecutor and leverage the bulk support now available in the newer versions of the SDK?

Yes, customers should migrate from the old bulk executor and use .NET SDK v3. There is a Migration Project that may be helpful.
There are also Samples  available as well.
You can do any point CRUD operation using Bulk. It's simply a flag in the ClientOptions. If you want to Upsert documents you can do that if you want. Doesn't matter.


Migration problem with DEV-Profil

Issue description
Hi.
I'm trying to migrate my Iota from IOTA Light Wallet 2.5.7.
After the migration I realized that I had created a developer profile. The IOTA are not available as credits.
The latest transaction is an entry "Fund migration 28 Dez 2021" and i get the message
"Your funds will become availiable shortly". What do I have to do to get my iota back?
Any advice would be greatly appreciated.
Thank you!
Firefly version
1.3.0
OS details
Windows 7
Can the issue be reliably reproduced?
No
Steps to reproduce the issue
1.Create a Developer Profil
2.Migrate IOTA from Light Wallet 2.5.7.
3.
...
Expected behaviour
I get the Iota on my wallet.
Actual behaviour
I am waiting for the fund
Errors
Tue, 28 Dec 2021 21:25:02 GMT
LatestAccountIsEmpty: can't create accounts when the latest account doesn't have message history and balance
Tue, 28 Dec 2021 21:24:54 GMT
LatestAccountIsEmpty: can't create accounts when the latest account doesn't have message history and balance
Tue, 28 Dec 2021 19:12:42 GMT
StrongholdError: failed to perform action: Engine Error: Crypto Error: error in algorithm XCHACHA20-POLY1305, Unable to read snapshot. Please try another password.``

Log out of the developer profile and create a new profile without the developer modus activated.
If you have accidentally created a developer profile and did send funds to an "atoi1" address you have not lost your funds.
To make these funds accessible you need to use the "recover a wallet" function in Firefly while creating a new profile.
Create a "non-developer" profile and use the 24 words that you have saved from your "developer profile" to restore this new profile (non-developer).
Your funds will show up in this new profile.
Also, please update from Windows 7 since this is not supported anymore.

Hi there,
thank you very much for the quick help. The bug was fixed with their instructions.

Glad to hear! Please mark this issue as solved and close it :)


Fix for doc generation failing  on repeated compilations

For #40.
This means docgen will succeed when the files already exist. It will overwrite, always using the newest version of the docs.

@codingupastorm Awesome, thanks for putting this up!
I'll take a look shortly to double check everything works fine with our larger build setup, but everyone is going to be really happy to have this fixed.


Missing player amounts

In the lag debug results you didn't write how many players are in the storage and are currently online, which makes comparing this to other methods harder. Could you please add how many players are stored and how many are online?

Yea, this is true. I would like to do a more in-depth analysis. I ran the function rx.playerdb:test/summon_50_players which uses carpet mod to summon 49 fake players (and then I'm the 50th). Then, in each player's storage for EntityDB, PlayerDB, and their EnderChest (an item w/ stick), I store 5 copies of an inventory full of diamond swords for some fake data.
Then, I run my get and get/saves on a execute as @a for this test. In the future, I'd like to test a bit more depth, but if you'd like, feel free to run your own tests and I can add them to the README.md (or make a PR)!

I've updated the lag results recently and in my upcoming 0.8 update, I'll try to make a better post. Do you have any suggestions on how to gauge performance and help compare w/ other methods?

Closing w/ lack of response. You can reopen later


Use valid instead of total

Reading v2alpha1 spec I see the total is still there from v1.
Maybe it's a nit, but I suggest using valid instead for reasons that I've explained here.
Essentially, the formula for SLI is:
good / valid x 100
The distinction between valid and total enables the users to see the possibility to scope their optimization effort to what they see in their area of responsibility and control as well as preventing false alerts for things that are clearly not.

Hey @alexewerlof, thanks for bringing this up :) (and the other issue)
We're planning next community meeting between 3th and 7th of June (18:00 UTC).
You can either let me know here which day(s) suit you best or vote directly on our Slack, there's an invite link at the bottom of https://openslo.com/

We discussed this today and decided not to change the standard because:

It's too late. This small change has massive ramifications to implementation
"Total" seems to be the convention in other tools as well
Although "valid" is used in the SRE books, total is easier to understand

I think this is not to be closed just yet - discussion is ongoing on Slack

I think this is not to be closed just yet - discussion is ongoing on Slack

I'll move my thoughts in here, slack is nasty and blures old messages in free version.
During the community meeting we I have been pro changing the name to valid instead of total. I will rephrase my arguments to have all arguments on board, but after sleeping with this idea I have changed my mind a bit. I think this discussion is important, because our current arguments doesn't solve the case, at some point we may come back to the idea of changing the name again.
My argumentation was that we serve as guideline, we guarantee that using our spec will be the correct way of describing SLOs as code. Because of that I think we should use the best naming as possible.
As my previous argument is still valid, I think we should keep the name total. Arguments provided in @alexewerlof article, are interesting but probably should be solved by picking different SLI or actually be reflected in SLO. SLI should be metric that reflects how users see your system. It doesn't mean that you didn't have control over an incident, because your vendor had an incident, if your users couldn't use your system, they don't really care.
I hope that @alexewerlof will not feel offended that I will use his arguments to describe my point. I think article is great, it describes the problem in a way that it is easy to understand, is relatable and most importantly it serves as great starting point for discussion!
Here I'm citing article mentioned before in Issue.

Correctly, chosen SLI should be total requests made by users of the system. We can see in here there was a problem with picking correct SLI. But this are still total requests that users have made.

Example: request latency

❌ Latency of all requests to our backend (API, static, etc.)

✔ Latency of API calls excluding the health check

I'm not sure whether both of this are correct SLIs. High priority can be really subjective term and SLO can be actually misleading, probably I'd focus on Availability in here.

Another example: incident resolution time

❌ Time to resolve an incident

✔ Time to resolve high priority incidents

Website uptime is actually great SLI. Users do not care about your vendors, if they are failing it should be reflected on your SLO. If you are below your objectives, probably you should consider changing them, move to highly available solution etc.

Another example: website uptime

❌ Website uptime

✔ Uptime minus the cloud provider downtime minus outage due to maintenance planned windows

When your API fails it fails, show it on SLO. I think this is the same situation as described in previous point. Do something w with it, most of the time you are able to focus on it.

❌ User facing API success rate (our API may fail due to our dependencies)

✔ User facing API success rate for errors that are not due to failure in our dependencies or content that the team doesn’t control

Nature of DDoS is that it is hard to differentiate from actual users that are not malicious. Show it on SLO. If you have too many attacks, SLO should tell you that it is time for investing into attack mitigation solutions.

❌ All API calls

✔ Authenticated API calls (we don’t want to be punished for DDoS attacks or any other unintended usage of the API surface)

It was said few times already picking correct SLI is the hardest part of creating SLO. I think this shows it the best, SLI should in simple, but in the same time show how users see your system,  it isn't simple thing to do. Suggesting users to use valid events only suggest that they should sometime cut part of them because we couldn't do anything about it, this is really subjective thing and it can lead to the situation when users don't want to use your system because it isn't reliable, but all your SLOs are about their threshold.
Sorry for requesting to reopen this issue to actually propose keeping things the same :D and big thanks to Alex for bringing this discussion!

Reading the examples, I am actually even more in favor of total than before.
The reason is that total always represents the actual total of whatever you are trying to measure, and it doesn't matter if that includes or doesn't include a DDoS attack - that's up to you. valid in this case IS actually "scoping" what the user could consider more than total, IMO
For example, in the case of website uptime, I also disagree. You should design your system INCLUDING your cloud provider downtime/SLA, because you can't actually provider higher results than the infrastructure that you depend on provides. And the developers implementing SLOs for their services should be acutely aware of this fact.
Same as ✔ User facing API success rate for errors that are not due to failure in our dependencies or content that the team doesn’t control - this just honestly makes no sense? User doesn't care if his error is because of you or your dependency - he got an error and that's it. If you wanna monitor purely what your service is doing, you should create another SLO for that.

You're right @fourstepper. Maybe it wasn't phrased good enough but I wanted to say that I have changed my mind after thinking about it bit more and we should stick to total,  I just expanded the reasoning beyond reasons said before. Sorry for all confusion, I'll close Issue now 🙏

It's all good, I'm glad we got to discuss this :)


Corporate Console - Whitelisting Update Email - Issues with the email content and whitelist needs to updated to Approved List

Background
<Niru 24-Apr-2020> Also as per latest changes whitelist needs to updated to Approved List

Launch Corporate Console
Login as nirupamavmentee2
Click on company NotSignedInCLAManagerCompTest
Click on Manage whitelist for project ProjectActivityLogTest
Add email<EMAIL_ADDRESS>for Email Whitelist

Email is sent to the employee
Issue1
Observed that content says " added to the whitelist of None". Not sure what has to be displayed instead of None. Appropriate content has to be displayed in the email

Issue2

Grammar in the email should be corrected
Email content says "This is to inform you that you have added " but I think it should be "This is to inform you that you have been added "

@nirupamav will review on the 04/08/2020 stakeholder.

The output of the email review meeting was that we are going to update the email content to form a standardized response - including:

standardized subject lines - e.g. subj line would start with: "EasyCLA System Notice: ..." or something similar
The body would contain the problem statement
The body would state the result of issue/what's affected
The body would contain a call to action/how to resolve statement
The body would identify how to get additional help
The body would contain a consistent sign-off statement

Verified email satisfies the agreed upon standardized response

The old v1 console is deprecated and removed.


Waiting for interdependent resources to become ready

Describe the problem/challenge you have
I have two resources that are part of an app. Resource A will not be ready without resource B, and resource B will not become ready without resource A. I'd like to know for kapp deploy when both resources are ready.
If I define no wait rules or change rules then everything will come up, but I don't know when that happens via kapp.
If I define wait rules, then I know when both resources are up, but there's a race condition where one of the resource could be not ready and fail the kapp deploy.
If I define a change rule, then I can ensure that resource A is created before resource B. But because resource A will never become ready without resource B, I can't also specify a wait rule, as resource B will never be created as resource A is never ready.
More specific details below.
Describe the solution you'd like
I'd like a way to order the upsert of resources via a change rule to wait for the resource to be "seen" without needing to wait for all of the wait rule conditions. Waiting for the resource to be created/updated on the api may be sufficient, or if a wait rule defines supportsObservedGeneration: true wait for the generations to match.
Anything else you would like to add:
Slack thread
My specific use case involves trying to deploy a Knative Service (S) and a ServiceBinding (SB) resource. The S will crash loop until the SB is ready. The SB will not become ready until the S exists.
Prereqs:

Install Knative Serving
Install Service Bindingskapp deploy -a service-bindings -f https://github.com/vmware-labs/service-bindings/releases/download/v0.6.0/service-bindings-0.6.0.yaml

Create a MySQL servicekapp deploy -a mysql -f https://gist.github.com/scothis/f65bd3ec45bd42ca89b1a554442c7cdc/raw/467d84237f582c6615ae1f7543d30d3a5015f2c6/mysql.yaml

Gist with config I'm attempting to use. Has both wait rules and a change rule defined. It will fail as is.
kapp deploy -a workload -f https://gist.github.com/scothis/f65bd3ec45bd42ca89b1a554442c7cdc/raw/467d84237f582c6615ae1f7543d30d3a5015f2c6/app.yaml

Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.

My specific use case involves trying to deploy a Knative Service (S) and a ServiceBinding (SB) resource. The S will crash loop until the SB is ready. The SB will not become ready until the S exists.

So we would need a different version of change group and change rules, and rather than waiting for the dependee to be ready, we just wait for it to exists.
I will think more about it while going through the examples and gist in detail.

exists can get a bit sticky, especially for updates. I was thinking something like seen might be better, so if a resource has  supportsObservedGeneration set to true, then we can wait for the observed generation to match the generation. That we we can know the resource has at least been reconciled even if the resource is not ready.
It might also be useful to have the ability to order the condition checks, so even if there's a wait rule for a resource, the check could be deferred until another resource is ready.
Is "ready" the right term within kapp?

i see this as whether waiting phase is blocking (currently) vs non-blocking (wanted in this case).

Waiting for the resource to be created/updated on the api may be sufficient, or if a wait rule defines supportsObservedGeneration: true wait for the generations to match.

this is an interesting bit. in your example is it required for "The SB will not become ready until the S exists." to work out. im trying to think of examples where "partial waiting" would be necessary (which does shift idea of blocking-vs-non-blocking a bit).

@scothis I followed the steps mentioned by you to reproduce the issue and I noticed that an ExternalService and an Ingress are created once the S and SB are in the desired state. So, I was wondering if you would be able to use the exists annotation on the ExternalService and wait for it's existence instead of waiting for S and SB. I did try this out and it seems to be working but I am not sure if the creation of the ExternalService is something that you would be able to rely on.
Gist that I used for the deployment.

@praveenrewar I haven't used the exists annotation before, but I don't see how that would solve the race condition that exists between the S and SB resources becoming ready. The existence of a child resource it not an indication that the parent resource is completely ready, but is certainly part of that resource becoming ready.

but I don't see how that would solve the race condition that exists between the S and SB resources becoming ready

Does the race condition occur even when S and SB are deployed together (without any change rules)?
I am exploring the non-blocking behaviour suggested by @cppforlife, and I saw this error in the SB description
Warning  UpdateFailed  34s (x14 over 75s)  servicebinding-controller  Failed to update status for "spring-petclinic-db": admission webhook "defaulting.webhook.bindings.labs.vmware.com" denied the request: mutation failed: cannot decode incoming new object: json: unknown field "subresource"
I will take a look at it again in some time but let me know if you have seen it before and able to resolve it.

Does the race condition occur even when S and SB are deployed together (without any change rules)?

The race surfaces when defining wait rules for either resource, as either resource may flip to Ready=False before the system stabilizes on Ready=True

I saw this error in the SB description

I haven't seen this particular error before. Do you have any other context for how it surfaced?

The race surfaces when defining wait rules for either resource, as either resource may flip to Ready=False before the system stabilizes on Ready=True. You should be able to simulate this by removing either resource from the app being deployed.

I see. In my case, the SB is not getting updated, so I am not able to simulate the exact behaviour, but if try to deploy the S alone, it does indeed wait indefinitely for the SB.

Do you have any other context for how it surfaced?

I actually followed the steps mentioned by you on a minikube cluster. I will try to deploy it on a fresh cluster again and see if the problem persists.

Warning UpdateFailed 34s (x14 over 75s) servicebinding-controller Failed to update status for "spring-petclinic-db": admission webhook "defaulting.webhook.bindings.labs.vmware.com" denied the request: mutation failed: cannot decode incoming new object: json: unknown field "subresource"

I was able to get rid of this ^ issue on a gke cluster.
I have one question related to the ordering of (S) and (SB) though.

My specific use case involves trying to deploy a Knative Service (S) and a ServiceBinding (SB) resource. The S will crash loop until the SB is ready. The SB will not become ready until the S exists.

Based on this, my assumption was that we would want to create the (S) first, wait for it to be seen, create the (SB) and then wait for both the resources to be ready. But based on the change rule defined defined in the gist, we are trying to create the (SB) first, which I think would lead to an immediate failure.
Is it just that the you were experimenting with the change rules and it's not exactly how you want it to be, or is there something that I have missed.

Proposing the addition of a new condition for the ServiceBinding resource in https://github.com/servicebinding/spec/pull/218
If we can wait for this status condition to become true in a change-group, we can side step the race condition between resource for their health wait rules.


1.1.0a1: JSONExportableRootDict()

Codecov Report
Attention: 10 lines in your changes are missing coverage. Please review.

Comparison is base (b1fb6b4) 77.58% compared to head (9193bbb) 78.40%.
Report is 6 commits behind head on main.

Files
Patch %
Lines

src/pydantic_exportables/jsonexportable.py
87.67%
9 Missing :warning:

tests/test_exportable_importable.py
97.72%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #17      +/-   ##
==========================================
+ Coverage   77.58%   78.40%   +0.81%
==========================================
  Files          10       10
  Lines        1053     1139      +86
==========================================
+ Hits          817      893      +76
- Misses        236      246      +10

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


[archiveorg] Wayback Machine archives of YouTube videos

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.10.29. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2018.10.29

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[x] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', 'https://web.archive.org/web/20140915015235/http://www.youtube.com/watch?v=9bZkp7q19f0&feature=youtu.be']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2018.10.29
[debug] Git HEAD: 0753f1e
[debug] Python version 3.6.5 (CPython) - Linux-4.18.16-gentoo-x86_64-AMD_Athlon-tm-_II_X4_630_Processor-with-gentoo-2.4.1
[debug] exe versions: ffmpeg 3.3.6, ffprobe 3.3.6
[debug] Proxy map: {}
[generic] watch?v=9bZkp7q19f0&feature=youtu: Requesting header
WARNING: Falling back on generic information extractor.
[generic] watch?v=9bZkp7q19f0&feature=youtu: Downloading webpage
[generic] watch?v=9bZkp7q19f0&feature=youtu: Extracting information
[debug] Default format spec: bestvideo+bestaudio/best
[debug] Invoking downloader on 'https://web.archive.org/web/20140915015235/http://www.youtube.com/annotations_invideo?cap_hist=1\\u0026cta=2\\u0026video_id=9bZkp7q19f0'
ERROR: unable to download video data: HTTP Error 404: NOT FOUND
Traceback (most recent call last):
  File "/usr/lib64/python3.6/site-packages/youtube_dl/YoutubeDL.py", line 1908, in process_info
    success = dl(filename, info_dict)
  File "/usr/lib64/python3.6/site-packages/youtube_dl/YoutubeDL.py", line 1847, in dl
    return fd.download(name, info)
  File "/usr/lib64/python3.6/site-packages/youtube_dl/downloader/common.py", line 364, in download
    return self.real_download(filename, info_dict)
  File "/usr/lib64/python3.6/site-packages/youtube_dl/downloader/http.py", line 341, in real_download
    establish_connection()
  File "/usr/lib64/python3.6/site-packages/youtube_dl/downloader/http.py", line 109, in establish_connection
    ctx.data = self.ydl.urlopen(request)
  File "/usr/lib64/python3.6/site-packages/youtube_dl/YoutubeDL.py", line 2211, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
  File "/usr/lib64/python3.6/urllib/request.py", line 532, in open
    response = meth(req, response)
  File "/usr/lib64/python3.6/urllib/request.py", line 642, in http_response
    'http', request, response, code, msg, hdrs)
  File "/usr/lib64/python3.6/urllib/request.py", line 570, in error
    return self._call_chain(*args)
  File "/usr/lib64/python3.6/urllib/request.py", line 504, in _call_chain
    result = func(*args)
  File "/usr/lib64/python3.6/urllib/request.py", line 650, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 404: NOT FOUND

These are all the same video (http://www.youtube.com/watch?v=9bZkp7q19f0):

Single video (2013-02-15): https://web.archive.org/web/20130215123412/http://www.youtube.com/watch?v=9bZkp7q19f0&feature=youtu.be
Single video (2014-09-15): https://web.archive.org/web/20140915015235/http://www.youtube.com/watch?v=9bZkp7q19f0&feature=youtu.be
Single video (2016-05-19): https://web.archive.org/web/20160519124739/https://www.youtube.com/watch?v=9bZkp7q19f0&feature=youtu.be
Single video (2018-05-08): https://web.archive.org/web/20180508055752/https://www.youtube.com/watch?v=9bZkp7q19f0&feature=youtu.be

YouTube videos archived within the Wayback Machine on archive.org, don't seem to be supported. I hazard a guess that supporting this may tricky because YouTube may change significantly depending on which date is chosen.
I don't see the point in playlists or related videos being supported, since there are low odds that any given video in a playlist is archived.

Duplicate of #13655.


Added methods for Support Fragments

It'd be great to be able to use this with the Support lib versions of Fragments.

see #10


sdk: python: Add a few more tests

Easy win from porting test examples from the Go SDK[^1].

Fixed mutability issue in query builder
Fixed default timeout being too low

[^1]: It's also good that you can reuse buildkit's cache between Go and Python's tests since they are producing the same build instructions!
Signed-off-by: Helder Correia

While this error is unrelated to this PR, I couldn't check if this works not just your machine:

I was following sdk/python/README.md.

That's because the SDK isn't provisioning the engine yet. See 1) in

https://github.com/dagger/dagger/issues/3642#issuecomment-1302054382

I pushed 2 tiny changes, but still no cigar:

As a follow-up PR, we should add these Python tests as a GitHub Workflow - WDYT?

I pushed 2 tiny changes, but still no cigar:

You need to run the engine with the sdk's workdir for the tests: go run ./cmd/cloak dev --workdir sdk/python
When you run generate you should then run lint:fmt to keep consistent output

As a follow-up PR, we should add these Python tests as a GitHub Workflow - WDYT?

Yes, it's on the list, just waiting for you 😛

I have a few more tests on the way.

The mypy warnings are expected for now. Not in scope for next release.


Configuration files should not be tracked

I think it would be nice to remove the config files from git. Rename them to config.example.ini instead, and have people make their own config files from those.
It just makes it easier to keep using git pull without having to fix config files every time (or use a similarly unhandy solution).

You can pass environment variables by adding system-environment vars:
check this: https://github.com/exodus4d/pathfinder/issues/175#issuecomment-222334819
So you don´t have to care about the environment.ini any longer. I use this setup for multiple installations and testing instances of PF.
There is just one Issue with this. Cronjobs are triggerd by CLI (async). To make cronjobs working with this setup you have to set them up as "real" OS-system vars. But this is just something for advanced users :)


Enforce Connection Mode Direct

Product and Version [VS/VSCode]: Both VS and VSCode
OS Version [macOS/Windows]:  Both
Live Share Extension Version:  Latest
Target Platform or Language N/a
Steps to Reproduce / Scenario:

Enable the ability to force users to operate the product in direct mode only as to prevent unauthorized sharing of code to third parties either through policies or some other mechanism

This is a really great product, and I see a lot of value in its features from an internal perspective.  My security team is looking to lock it down to internal only without completely blocking the endpoint *.servicebus.windows.net:443.
Any ideas or guidance is appreciated.

@cwoodworth Hey! Thanks for reaching out. We’ve heard this request a few times, and definitely want to enable team/organization-wide policy enforcement in the future. In the meantime, blocking our cloud relay may be the best way to guarantee that only direct mode can be used. If it would be valuable, we could provide you with the DNS hosts of the Live Share relays, so that you didn’t need to block Azure Service Bus entirely.
@jasongin Can you think of a better recommendation? Also, could you confirm that if our relay was blocked by a firewall, that it wouldn’t prevent a direct connection from successfully happening? (e.g. would the Share operation fail if it couldn’t reach the relay?)

Can you think of a better recommendation?

Nothing right now. As mentioned, we have discussed how we might build support for these sort of enterprise policies in the future, but there are no immediate plans.

could you confirm that if our relay was blocked by a firewall, that it wouldn’t prevent a direct connection from successfully happening?

Yes. The direct connection is attempted first, so blocking the relay servers will not cause any problem for direct connections.

@jasongin Thanks for confirming that!
@cwoodworth We’ll use this issue to track implementing the centralized policy enforcement. In the meantime, it would be great to know if blocking the relay servers would be an acceptable workaround for your team to adopt Live Share. Let me know if it would be helpful to get the specific list of DNS hosts, or if blocking *.servicebus.windows.net:443 is sufficient. Thanks!

Sorry I need to correct my statement above. (For some reason I was thinking only about the potential of joining being blocked.)
If the relay servers are blocked, then the share operation will fail when using the default "auto" connection mode. VSLS hosts would have to change their connection mode to "direct" in order to successfully share. And then joiners would be informed that was the only possible way to connect to the session, so they would not even try connecting to the relay.

@lostintangent It would be great if I could get the specific DNS servers as my team was very against blocking the entire set of relays.  Thanks for all your help, and the quick response.

@jasongin @lostintangent Any update on this?  Let me know if another forum for communication is preferred.

@lostintangent is there any update on a process for organizations enforcing direct mode or should I email you?

Now that VS2019 is out and ships with this by default, I'm also interested in an administrative way to block the relay.  Is blocking *.servicebus.windows.net:443 still the best option here?

Yes @lostintangent, it would be very helpful to have the specific list of DNS hosts to block. We looked into blocking *.servicebus.windows.net:443, but that's a bid of a broad brush and we had other services that relied on that.

Hello!
Are there any updates on centralized policy enforcement, that would not rely on blocking network trafic since that is not always possible with our remote workers, who are numerous in this period of time =). We use our corporate Azure AD accounts to connect to liveshare, so the best solution for our organization would be to rely on that to inherit some mandatory settings such as Direct-connect mode. Thank you for your help!

Hello!
Same as @mfjerome here.

Pinging here that we're also interested in this. Would love our team to be able to use this, but we cannot communicate through MS's commercial endpoints due to our policies. At best, we can only use endpoints that are within Azure GCC High or greater.
Can you publish the actual DNS endpoints that we should block to prevent our folks from using the relay, and reliably ensuring only relay works?  Alternatively, perhaps a registry/gpo method that we can use to enforce the setting to only allow direct?

Forcing direct connection mode is now possible in VS via group policies. Please refer to https://learn.microsoft.com/en-us/visualstudio/liveshare/use/policies-visual-studio for more information.

Thank you so much @nandiniYeltiwar!!!

Closing this as we have VS support. to support VS Code, we first need https://github.com/microsoft/vscode/issues/151948.


MoveStatus watch method error

In the MoveStatus _notify_watchers method, if the fraction calculation causes an exception, fraction is set to None and the next if statement causes an error if None is passed into np.isnan.
import numpy as np
a = None
print(np.isnan(a))

ufunc 'isnan' not supported for the input types, and the inputs could not be safely coerced to any supported types according to the casting rule ''safe''

Closed by https://github.com/bluesky/ophyd/pull/795


Tests fail in current master (golang 1.8 in docker build)

docker build -t test . on CI fails:
9:09:29 PM --- PASS: TestTXTRegistry/TestApplyChanges/No_prefix (0.00s)
9:09:29 PM PASS
9:09:29 PM ok github.com/kubernetes-incubator/external-dns/registry 1.031s
9:09:33 PM # github.com/kubernetes-incubator/external-dns/source
9:09:33 PM source/service_test.go:1017: not enough arguments in call to NewServiceSource
9:09:33 PM have (*"github.com/kubernetes-incubator/external-dns/vendor/k8s.io/client-go/kubernetes/fake".Clientset, string, string, string, bool)
9:09:33 PM want (kubernetes.Interface, string, string, string, string, bool)
9:09:33 PM FAIL github.com/kubernetes-incubator/external-dns/source [build failed]
9:09:33 PM make: *** [test] Error 2
9:09:33 PM Makefile:35: recipe for target 'test' failed
9:09:34 PM The command '/bin/sh -c make test' returned a non-zero code: 2

Seems to be caused by merging #324


Amortise edit processing

With this change, instead of processing each edit immediately, the server now accumulates edits and waits 500ms (we could make the precise value configurable) since the last edit before it starts processing them. This is done in the watchdog in order to amortise both worker restarts when the header is being edited, as well as non-header edit processing in the corresponding file worker. CC @Kha @mhuisi

For documentation purposes: I mentioned a while ago that perhaps we should handle these kind of things in the client instead, but it seems that the VSCode client only supports amortized changes for full changes, not incremental ones (cf. vscode-languageserver/client.ts#L1031).
Judging from this comment, this is by design.

For documentation purposes: I mentioned a while ago that perhaps we should handle these kind of things in the client instead, but it seems that the VSCode client only supports amortized changes for full changes, not incremental ones (cf. vscode-languageserver/client.ts#L1031).
Judging from this comment, this is by design.

perhaps we should handle these kinds of things in the client instead

Unfortunately as far as I can tell this is not at all part of the LSP spec, so we cannot expect every client to implement it, so we have to do it in the server. Of course there will be custom extensions like infoview which are also not in the spec, but it would be nice to still comply to the standard whenever we can.

perhaps we should handle these kinds of things in the client instead

Unfortunately as far as I can tell this is not at all part of the LSP spec, so we cannot expect every client to implement it, so we have to do it in the server. Of course there will be custom extensions like infoview which are also not in the spec, but it would be nice to still comply to the standard whenever we can.


Enable changing the version without restart

I am using the versions to store related but separate datasets in https://git.embl.de/pape/covid-em.
It would be great if one could switch between those without restarting the plugin.

I am using the versions to store related but separate datasets...

Maybe using versions for this is not the right thing to do, is it?
Maybe we can find another way? Let's talk on the phone...

We discussed to rename what we call version now to dataset.
So there will be a datasets.json. And then we allow to change between datasets from the gui.
(For now, we only allow for one active dataset; later on when the GUI is unified into a single window, we can enable showing multiple at once.)

As we have just discussed, we will change the datasets.json layout a bit:
{
  "dataset": ["ds1", "ds2", ...]
  "default": "ds2"
}

So that we know which dataset to open by default to get rid of the initial dataset choosing menu.
The "default" field should be optional, if it's not there we just choose one of the datasets.

let me know once you have this somewhere then I can test loading it.

As long as the autophagosomes one is on gitlab I would suggest the covid-em is our playground.

It's the other way! Autophagosoms are on github and they are our playground.
I have updated this repo now: added a second dataset and updated the datasets.json:
https://github.com/constantinpape/autophagosomes-clem


Flatten associative binary operations.

This reduces stack depth for long chained expressions.
Fixes #1236

Can you have a look at the smoke-tests that became less happy (and apparently found things not covered by any tests)

verible-verilog-format still crashes on the long expression generated with the script in #1236, but that seems to be due to some nested allocation in common/formatting/state_node.h in a very deeply nested stack; so there probably something is still allocated recursively.
But that should probably be fixed in a separate PR.

Codecov Report

Merging #1246 (837bca4) into master (10ca4f6) will increase coverage by 0.00%.
The diff coverage is 100.00%.

:exclamation: Current head 837bca4 differs from pull request most recent head 0345026. Consider uploading reports for the commit 0345026 to get more accurate results

@@           Coverage Diff           @@
##           master    #1246   +/-   ##
=======================================
  Coverage   92.75%   92.76%
=======================================
  Files         338      338
  Lines       23259    23277   +18
=======================================
+ Hits        21574    21592   +18
  Misses       1685     1685

Impacted Files
Coverage Δ

verilog/CST/expression.cc
96.55% <100.00%> (+0.12%)
:arrow_up:

verilog/CST/expression.h
100.00% <100.00%> (ø)

verilog/parser/verilog_token_classifications.cc
100.00% <100.00%> (ø)

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 10ca4f6...0345026. Read the comment docs.


Tile server user guide

Tile server user guide
!story G18.3
!component docs

Work a little on this but with talking with Aaron I am to far a head of writing the doc. Still a lot of changing happening.

Working on the Doc. Was able to see the new UI's and ran some tests. This will help me on writing the steps and how to lay out the format. Thinking we should only have one doc with will have all of the roles in it.

Completed User Guide and waiting review.

mpg to review

now a dup of #164 in omar-agc-pm repo


Library: power, UART, I2C, RS232 components...

Library: power, UART, I2C, RS232 components...
Description
New and fixed library modules.
Also extended ElectricPower and some other fixes and additions.
new:

B0505 isolated DCDC converter
CH344x quad usb uart bridge
DE-9 RS232 connector
ISO1540 isolated RS485 tranceiver
PowerMux base module
TPS2116 Power mux
RS232 tranceiver
CH342F dual usb uart bridge
AP2552W6
INA288
ElectricalRCFilter
USB2514B ref design
ResistorVoltageDivider

additions:

ElectricPower fused function
ElectricPower sink trait

Checklist
Please read and execute the following:

[x] My code follows the coding guidelines of this project
[x] My PR title is following the contribution guidelines
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation (if applicable)
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works (if applicable)
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[x] I ran Black to format my code

Code of Conduct
By submitting this issue, you agree to follow our Code of Conduct:

[x] I agree to follow this project's Code of Conduct

@iopapamanoglou assert_once is broken (as you said). It does not work when you use more than 1 of the same module that uses a function with asser_once. e.g. in the tests...
commented it out for now


[D3D9] Oblivion freezes after 1-2 minutes of game play unless music is disabled

The Elder Scrolls IV: Oblivion will freeze after a few minutes of game play unless music is disabled by setting bmusicenabled=0 in Oblivion.ini.
If winegstreamer is enabled, it will produce a long string of error messages until the application freezes. If winegstreamer is disabled using a DLL override in the Wine Configuration menu, there are no more error messages, yet the freeze still occurs, and just as quickly.
It makes no difference whether or not Oblivion is run from within a virtual desktop or not.
This problem does not occur if the game is run from a Crossover Office 19.01 bottle with 'Performance Enhanced Graphics' enabled, yet Crossover may be using an older version of DXVK which does not yet support DirectX 9 games (Crossover also still features the bug where the PC's skin is pitch black irrespective of the settings the player uses in the character creation menu).
The problem also does not occur if the game is run from a Crossover Office 19.01 bottle which does not have 'Performance Enhanced Graphics' enabled, and thus uses WineD3D instead.
###Software information
The Elder Scrolls IV: Oblivion - Game of the Year Edition Deluxe (GOG version)
System information

GPU: AMD Vega56
Driver: AMDGPU, Mesa 20.0.0-devel - padoka PPA
Wine version: 5.2
DXVK version: 1.5.4

Apitrace and log file(s)
These will be added as soon as possible. I need to change my setup to produce new ones as I have been experimenting to find out what was causing the freezes.

This isn't our bug. Please make an issue with Wine.

It's not happening on Wine Staging 5.2 / DXVK 1.5.4 (latest master), at least not with an Nvidia card. I've been playing for 30 minutes now. Although I haven't ever seen it run out of memory so far, I guess it may be related to #1318, especially if you're using a lot of mods.

This isn't our bug. Please make an issue with Wine.

Thanks for your reply. I realised after posting that this bug likely had a different origin; I've just created a new Wine prefix without DXVK, and the same problem occurs. Need to report this with the Wine developers, as you said.

I found it to be some sort of codec issue, I installed   K-Lite Codec Pack and it is running alright now.         https://codecguide.com/download_k-lite_codec_pack_full.htm


Fix to not leave any garbage.

This realize optional arguments.
{
    "echo": "echo args are",
    "foo": "run-s \"echo -- {1}\" --"
}

The current specification and implementation are strange.
Since users can not be avoided, it is no exaggeration to say that bug.
$ npm run foo
> run-s "echo -- {1}" --
> echo args are "{1}"

args are "{1}"

On the other hand, this p-r's result is
$ npm run foo
> run-s "echo -- {1}" --
> echo args are

args are

Again, the user still have a way to pass-through {1} as is.

I'm sorry. I'm in fixing the tests.

Thank you for this PR.
I'm sorry for late response. I was busy for past several days.
Implement looks good to me.
It has backward compatibility if it keeps placeholders when arguments are nothing. So I released it as a minor version.
But this is a breaking change, so it needs a major version.

I apologize that I had overlooked.
To tell the truth, I noticed a look at the test you have added after it had been released.

If it removed placeholders when arguments are nothing, it was a breaking change because the behavior of npm-run-all "foo {0}" will be changed even if it's before the release of current placeholders feature.
I'll merge this PR within a few days.
Indeed, if placeholders remain, it's bad.

Yes, I knew it.
Thank you again.
BTW, I have thought hasPlaceholder cheking is not useful and over optimization.
I just follow your code that is hasArguments checking.

@mysticatea
Any update on this? In fact, the placeholder is useless until resolve this problem.
Thank you for your hard work!

I'm sorry, just I have been busy.
My plan is:

now I'm working on #53.
after I finish it, I will merge this and work on #54.
then I will release 3.0.0.

If so, the v2.x's user cannot use the placeholder feature does not?
Because v2.x has such a bug bellow.
{
  "list": "run-s \"ls {@}\" --",
  "ls": "ls"
}
$ npm run list
ls: cannot access '{@}': No such file or directory
$ npm run list ./
# no problem

I think #50 does not mean a breaking change of spec but just a bugfix which is needed to >=v2.2.0.
#50 is necessary in order to ensure that v2.x's user can use the placeholder feature correctly.

This PR is a breaking change.
Because {1} had not been removed before placeholders feature is added.

I agree with you as long as you decided so.
But then, almost all of the bug-fixes become breaking change to a greater or lesser.
So still, I think it is the bug of implementation not that of specification.
I'm looking forward to release of v3 to be able to use placeholder feature, since it could not be used in v2.x.
Best Regards.


crud plugin: onSaved not firing

In 3.0.0-alpha.29, the onSaved callback for the crud plugin doesn't seem to fire.
See codesandbox. Note that on adding item to todo list the console log from create appears, but not the one from onSaved

Thanks @mdj-uk and sorry for the delay! It seems to be an issue with as: "array". I've reproduced it and will try to fix it.

This is fixed in alpha.40. Thanks for the report!

Thanks!


(feature request)  Allow us to change "more" and "less" text

My bad, It is already threre, Just not mentioned on the readme. Closing the issue but update to the readme will be helpful for others :).

Will do, thanks for the feedback!


Rename ServiceConfig interface & default ServiceConfig implement's name

Rename change :
1.ServiceConfigIf -> ServiceConfig
2. ServiceConfig -> DefaultServiceConfig

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.vito.he seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.