The paging file is too small for this operation to complete

Issue Description
We get the following error when creating a container with external database (I assume the database does not matter): docker.exe: Error response from daemon: hcsshim::CreateComputeSystem b335320a7bcd16cd03b0332db53afd108be43253ef8fbfd0528e89d58061d7f2: The paging file is too small for this operation to complete.
Environment

Windows Server 2019
February 2020 Update downloaded but deferred
Container with -memory 10G, -isolation hyperv (in prep. for the update)
Existing database (attaching container)
Pulled image to ensure it is current (BC SaaS 16.0.10855.0-de-ltsc2019)

The same works without specifying "-isolation hyperv".
The full command
					New-BCContainer `
						-accept_eula `
						-accept_outdated `
						-assignPremiumPlan `
						-imageName $dockerImageName `
						-containerName $instanceBaseName `
						-licenseFile $licenseFile `
						-auth NavUserPassword `
						-Credential $cred `
						-memoryLimit 10G `
						-isolation hyperv `
						-shortcuts None `
						-useTraefik `
						-useSSL `
						-PublicDnsName $dnsName `
						-additionalParameters $additionalParameters `
						-databaseServer $databaseServer `
						-databaseInstance $databaseInstance `
						-databaseName $instanceBaseName `
						-databaseCredential $dbCred `
						-myScripts $additionalScripts `
						-Verbose `
						-Debug;

$additionalParameters is empty.
$additionalScripts is empty.
The Log
WARNING: Container name should not exceed 15 characters
VERBOSE: Perform operation 'Enumerate CimInstances' with following parameters, ''namespaceName' = root\cimv2,'className' = Win32_OperatingSystem'.
VERBOSE: Operation 'Enumerate CimInstances' complete.
NavContainerHelper is version <IP_ADDRESS>
NavContainerHelper is running as administrator
Host is Microsoft Windows Server 2019 Datacenter - ltsc2019
Docker Client Version is 19.03.4
Docker Server Version is 19.03.4
Disabling SSL on the container as you have configured -forceHttpWithTraefik
Using image bcinsider.azurecr.io/bcsandbox-master:16.0.10855.0-de-ltsc2019
PublicDnsName is dev-dockerbc.host.de
Removing C:\ProgramData\NavContainerHelper\Extensions\docker-favcontainer
Creating Container docker-favcontainer
Version: 16.0.10855.0-de
Style: sandbox
Platform: 15.0.39761.0
Generic Tag: <IP_ADDRESS>
Container OS Version: 10.0.17763.914 (ltsc2019)
Host OS Version: 10.0.17763.1039 (ltsc2019)
Using locale de-DE
Using hyperv isolation
Adding special CheckHealth.ps1 to enable Traefik support
Disabling the standard eventlog dump to container log every 2 seconds (use -dumpEventLog to enable)
Using license file D:\ProgramData\dockerbc\16.0.10855.0-de-ltsc2019\Temp\fafc7227-c455-49ed-ae06-c9495537b413.flf
Files in C:\ProgramData\NavContainerHelper\Extensions\docker-favcontainer\my:

AdditionalOutput.ps1
CheckHealth.ps1
license.flf
MainLoop.ps1
SetupNavUsers.ps1
Creating container docker-favcontainer from image bcinsider.azurecr.io/bcsandbox-master:16.0.10855.0-de-ltsc2019
9bc27e9fdc19195c01df4753ecccc8e91c2c35e8466084b503377380088aa22f

The full error
docker.exe: Error response from daemon: hcsshim::CreateComputeSystem 9bc27e9fdc19195c01df4753ecccc8e91c2c35e8466084b503377380088aa22f: The paging file is too small for this operation to complete.
(extra info: {"SystemType":"Container","Name":"9bc27e9fdc19195c01df4753ecccc8e91c2c35e8466084b503377380088aa22f","Owner":"docker","IgnoreFlushesDuringBoot":true,"LayerFolderPath":"D:\ProgramData\Docker\
windowsfilter\9bc27e9fdc19195c01df4753ecccc8e91c2c35e8466084b503377380088aa22f","Layers":[{"ID":"259914a6-aba4-596c-acac-17526744b153","Path":"D:\ProgramData\Docker\windowsfilter\0d685f95a4d675f7ff4dd
e3af609128cc43aefb4f810e5314f46043336bb1252"},{"ID":"82ae3fb6-9a3e-5829-8b0b-232da37b90ba","Path":"D:\ProgramData\Docker\windowsfilter\2b873b186df8c03de350c79fe9c22b1797e39aadc7cd3052ae7969ff1de84541"}
,{"ID":"c2be29b4-881e-5b22-84bc-1fd5e4d82844","Path":"D:\ProgramData\Docker\windowsfilter\5948072e53a6abef85589b8e9ee15da130279f0142d8ade3148051b8c43a4408"},{"ID":"fc07c80c-f002-5c20-84b4-d29b83516798"
,"Path":"D:\ProgramData\Docker\windowsfilter\d5d0a1cb815023234b89afba6bc740f01f4896e0992900f98e7dfa83cbdb7390"},{"ID":"9f94f90f-787a-54b2-bfec-d5ffac9e8e79","Path":"D:\ProgramData\Docker\windowsfilt
er\24bba0fb15f8c592b9572db1d151627b5fa5d82242bf50c5fcfcdb9a69d6c1f1"},{"ID":"69e18a00-bd29-5335-aff0-09f190d6cd24","Path":"D:\ProgramData\Docker\windowsfilter\7c45ab70c9f36449d81f919b56860445a470f1112
06c053d39067001e6223a99"},{"ID":"5dbfe29f-d6d5-580a-8bd1-1b61876e1546","Path":"D:\ProgramData\Docker\windowsfilter\9f0f2bbfe48231da3da32783148f63a69ae70096f889d5df803edb360574e7e0"},{"ID":"9db8b9bb-af7
f-56e5-aace-0e7f3ae38aa4","Path":"D:\ProgramData\Docker\windowsfilter\4fb6eaf0a18f174d660edaf8b8f1d2e4a0ef74349b4a4f9dd64216ab038cb4d6"},{"ID":"30334b43-1fd5-5614-aff6-8066b0539655","Path":"D:\Program
Data\Docker\windowsfilter\591f2954c9dbef957e49308a18e73b4ee17c615b4cba54121cedd7d1b6b31228"},{"ID":"428e95bf-7b60-59fa-9906-669aa9b6329f","Path":"D:\ProgramData\Docker\windowsfilter\7110db5e67edf514
1bc882ed65530dae6ee4030dd5a15a3c8dd9760495a02869"},{"ID":"b98d8c4e-65bc-552c-8e6f-f55655bc52e2","Path":"D:\ProgramData\Docker\windowsfilter\9d59673cee869a7e104b8659976960ff5de9a5d16e30e7bb7651f9e269c1e
980"},{"ID":"a411d75f-0441-5474-bf0d-72f25433ca2a","Path":"D:\ProgramData\Docker\windowsfilter\173d32c52d98ed53eeedbc24633c0dc25a7689ccca2c9e1967cd6e4b7fefe8d8"},{"ID":"3be5e309-52e8-597a-ab65-6586b10d
af15","Path":"D:\ProgramData\Docker\windowsfilter\946d754739b316387d5556354761985db9af83727d8d54e6c8cb46b137ff2861"},{"ID":"45c4dd92-ae84-5d54-a191-d3931fdbb4e0","Path":"D:\ProgramData\Docker\window
sfilter\aa37896313740150752080908b1f1750742d9b966181f59b46f1bcb0079d19f7"},{"ID":"82929919-5d3a-54c9-98d8-b2c29416ba55","Path":"D:\ProgramData\Docker\windowsfilter\8ffab254ec5b92dfba4f2411b8836ca3facc
7021a9de114ca6beeb1344fb89b1"},{"ID":"bb3806cc-95d5-5524-93ff-a85de180e5ce","Path":"D:\ProgramData\Docker\windowsfilter\ce46a2a064217dfe00f69040f0670eb611c7b70a6b7d6b1655cda2998c126684"},{"ID":"464967b
b-845a-548d-94ad-db88c1cbbeb0","Path":"D:\ProgramData\Docker\windowsfilter\50350eaa15cfbf739503ff2d423ac9f5f444e8db1c7ce8a2bd06a1bd0a7519dd"},{"ID":"4493513d-a8ae-5a9e-a0ef-c47eec904b0f","Path":"D:\Pr
ogramData\Docker\windowsfilter\194af027099cd48c99b6954dad8782b01dc08fbd084a470fd9649b1ffd8a1b0a"},{"ID":"bc2dae32-6a9f-51b3-b722-7a38d742026a","Path":"D:\ProgramData\Docker\windowsfilter\e6d6398c7fe
67d54933f1d1e46031b28c7db0f04e30bd49a4d2a0f7646035ba1"},{"ID":"9965fae1-756c-54db-ac10-7ce711b17cae","Path":"D:\ProgramData\Docker\windowsfilter\03132b825f1fd26c566d90bc24812460c394bba81f2630634debb4f6
3dfa0fb8"},{"ID":"4ee20c3f-8ca6-58f0-80e4-ad5093773e4c","Path":"D:\ProgramData\Docker\windowsfilter\790bff7e1acca9fc7fccfc035a724a8edf1a056e5181e6d69ab5ec639622fa5e"},{"ID":"0cbd5805-4ab2-51f3-baf8-847
cf89fc690","Path":"D:\ProgramData\Docker\windowsfilter\e9c8be338a74775c6653f47191bb0be502c6d9d373548b07ccf537e075b8bb6a"},{"ID":"fc723184-5cc3-53aa-989d-0db3fc78cb15","Path":"D:\ProgramData\Docker\w
indowsfilter\79827a2e94dbfb82b761c64430b2372c535335a8048a29334774abc7e87e9857"},{"ID":"813cd7c0-1f06-5f8c-95a7-2dd1e4be169a","Path":"D:\ProgramData\Docker\windowsfilter\ea2fc743722e5728e32af15ade1ad57
1fdfccecfa81ba5482d0fb3024e2e1413"},{"ID":"8d7c7ea9-1242-53b4-9aa8-82f200b4ac92","Path":"D:\ProgramData\Docker\windowsfilter\cffff297fd9aef21294735c05d965e2ad048516a49b398930aad9bac9be6fe79"},{"ID":"be
4db4fb-f0a3-5bdc-b129-38207d019f0c","Path":"D:\ProgramData\Docker\windowsfilter\f844007f0f1a38ff07e4096582b40f2eaae7c2bdf59f9e333bdee6768619d2cc"},{"ID":"17f64337-ebcb-5742-b852-72527afcf0ef","Path":"D
:\ProgramData\Docker\windowsfilter\d6db18600c9917ff7cc38c26a7afd0d2431c9f9de80d3f0105edafa0e54e015e"},{"ID":"547fec42-7967-5f04-abef-4d93c13bfe62","Path":"D:\ProgramData\Docker\windowsfilter\5901c4
446c00d7a8d552cfa5e2ace5f74a2b0a3e61463707cfd95695361ba9aa"},{"ID":"f767efc5-431c-5f6f-95e2-c7c9cfb9e977","Path":"D:\ProgramData\Docker\windowsfilter\368a14941846d00b069a31fcd1d9b2463b2b2b8fe7154843830
e2a64d0930158"},{"ID":"c18090bb-8c2c-5fcd-becf-e325ef6470a4","Path":"D:\ProgramData\Docker\windowsfilter\1c3c3e419b270234f310bcd1c814ab2a30c1bb9e0813846ef2b0617cf43c3b7e"},{"ID":"633fc4ca-6bee-5485-84c
4-790c5d10779c","Path":"D:\ProgramData\Docker\windowsfilter\0965ac701d60fcb6ab857c9eeb295c0f6902c689c0ed67b5c957fe31296c9ccc"},{"ID":"d53a962a-8551-5daf-a0a5-8bb9ca186d65","Path":"D:\ProgramData\Dock
er\windowsfilter\71a4ed9b5079e4a748a15a413b3760d9624871d31a76fa7983674308259e0042"},{"ID":"7c0de9a4-19f7-51ab-b157-bf9a0deea36c","Path":"D:\ProgramData\Docker\windowsfilter\1d0773e899ea59102bb64714b3
d4e73ce3157ed3af31eb926418f408fc1edcda"},{"ID":"b4d214db-07ab-599c-825f-8bd0c6bf466c","Path":"D:\ProgramData\Docker\windowsfilter\50214b2611d04d9dbe7f49ce95e0acfa343947b58aeafff54a8691a28c4f59b8"},{"ID
":"5f32298c-fbe7-5383-8ff8-835c0c962b18","Path":"D:\ProgramData\Docker\windowsfilter\4aad68b4338e7cfe60d6b5dd014302b2630039e5d614b2394895ffff992c7ff0"},{"ID":"18e3bd22-447b-549c-a8c2-e355a9924a24","Pat
h":"D:\ProgramData\Docker\windowsfilter\0ce69927edae447c537a0dc7d30a990e9531cd3f778814d03cc927625abbb86e"}],"MemoryMaximumInMB":10240,"HostName":"dev-dockerbc","MappedDirectories":[{"HostPath":"d:\prog
ramdata\dockerbc\16.0.10855.0-de-ltsc2019","ContainerPath":"c:\dockerbc","ReadOnly":false,"BandwidthMaximum":0,"IOPSMaximum":0,"CreateInUtilityVM":false},{"HostPath":"c:\programdata\navcontainerhelper",
"ContainerPath":"c:\programdata\navcontainerhelper","ReadOnly":false,"BandwidthMaximum":0,"IOPSMaximum":0,"CreateInUtilityVM":false},{"HostPath":"c:\programdata\navcontainerhelper\extensions\docker-cl
ustersorting\my","ContainerPath":"c:\run\my","ReadOnly":false,"BandwidthMaximum":0,"IOPSMaximum":0,"CreateInUtilityVM":false}],"HvPartition":true,"EndpointList":["19894C0B-4F2A-4CDA-885D-923335F1960F"],
"HvRuntime":{"ImagePath":"D:\ProgramData\Docker\windowsfilter\4aad68b4338e7cfe60d6b5dd014302b2630039e5d614b2394895ffff992c7ff0\UtilityVM"},"AllowUnqualifiedDNSQuery":true}).
ExitCode: 125
Commandline: docker run --env PublicDnsName=dev-dockerbc.host.de --env licenseFile="c:\run\my\license.flf" --name docker-favcontainer --hostname docker-favcontainer --env auth=NavUserPassword --en
v username="admin" --env ExitOnError=N --env locale=de-DE --env databaseServer="atlas2.internal.x3.net" --env databaseInstance="dev2017" --volume "C:\ProgramData\NavContainerHelper:C:\ProgramData\NavContai
nerHelper" --volume "C:\ProgramData\NavContainerHelper\Extensions\docker-favcontainer\my:C:\Run\my" --isolation hyperv --restart unless-stopped --memory 10G --env enableApiServices=Y --env databaseName="m
x365-favcontainer" --env useSSL=N --env securePassword=76492d1116743f0423413b16050a5345MgB8AGMANQB1ADQAQwBLAEwAZABHAFEAdgBFAEEATQBRADMAZQA2AGQASgBUAHcAPQA9AHwAOQA1ADkAZABkAGIANwAxAGIAMQAxADcAMQBjADEAYgAx
ADIANgA2AGIAMQAwAGMANgA5AGUAMABhADcAMwBiAA== --env passwordKeyFile="c:\run\my\aes.key" --env removePasswordKeyFile=Y --env databaseUsername=dockerbcDeployment --env databaseSecurePassword=76492d1116743f0423
413b16050a5345MgB8AEYAVwByAHIAQQBCAGgAaABvAHUATABkAEcAMAAxAC8AMQA1AFcAVgAyAEEAPQA9AHwANAAzADUANAA4ADcAMAAxADQAMQA2ADkAMQAwAGEAMQAxADIAMgAzADAAMABlADEAMAAyADEAYwBmAGMAMAA0ADEAMQAxAGUAZABmADcAYQAyADcAMgA5ADI
AMgBiADEANgAzADgAMQA5ADgAMwA3ADQAZQAxADgANQBiADYAMAA= --env encryptionSecurePassword=76492d1116743f0423413b16050a5345MgB8AEYAVwByAHIAQQBCAGgAaABvAHUATABkAEcAMAAxAC8AMQA1AFcAVgAyAEEAPQA9AHwANAAzADUANAA4ADcA
MAAxADQAMQA2ADkAMQAwAGEAMQAxADIAMgAzADAAMABlADEAMAAyADEAYwBmAGMAMAA0ADEAMQAxAGUAZABmADcAYQAyADcAMgA5ADIAMgBiADEANgAzADgAMQA5ADgAMwA3ADQAZQAxADgANQBiADYAMAA= -v D:\ProgramData\dockerbc\16.0.10855.0-de-ltsc20
19:c:\dockerbc -e customNavSettings=PublicODataBaseUrl=https://dev-dockerbc.host.de/docker-favcontainerrest/odata,PublicSOAPBaseUrl=https://dev-dockerbc.host.de/docker-favcontainersoap/ws,Pu
blicWebBaseUrl=https://dev-dockerbc.host.de/docker-favcontainer --hostname dev-dockerbc -e webserverinstance=docker-favcontainer -e publicdnsname=dev-dockerbc.host.de -l "traefik.protocol=ht
tp" -l "traefik.web.frontend.rule=PathPrefix:/docker-favcontainer" -l "traefik.web.port=80" -l "traefik.soap.frontend.rule=PathPrefix:/docker-favcontainersoap;ReplacePathRegex: ^/docker-favcontainersoap
(.) /BC$1" -l "traefik.soap.port=7047" -l "traefik.rest.frontend.rule=PathPrefix:/docker-favcontainerrest;ReplacePathRegex: ^/docker-favcontainerrest(.) /BC$1" -l "traefik.rest.port=7048" -l "traefik.d
ev.frontend.rule=PathPrefix:/docker-favcontainerdev;ReplacePathRegex: ^/docker-favcontainerdev(.*) /BC$1" -l "traefik.dev.port=7049" -l "traefik.dl.frontend.rule=PathPrefixStrip:/docker-favcontainerdl"
-l "traefik.dl.port=8080" -l "traefik.dl.protocol=http" -l "traefik.enable=true" -l "traefik.frontend.entryPoints=https" --env accept_eula=Y --env accept_outdated=Y --detach bcinsider.azurecr.io/bcsandbox-
master:16.0.10855.0-de-ltsc2019 at at , C:\Dev\dockerbc.ps1: line 415
Info
As mentioned, the same works without specifying "-isolation hyperv". I want to clarify this BEFORE I install the updates and before we cannot access all our machines anymore.

How much memory do you have on the host?

48 GB, 12 GB free currently. Could this depend on the 10G memory somehow? Does it make sense to reduce it to 8GB for testing?

And what is the paging file on the host set to?
(Have never seen this before)

Completely automatic. Was 9GB this morning if I remember correctly.

Host OS Version: 10.0.17763.1039 (ltsc2019)
1039 is February Update - but since you are running Hyperv that shouldn't matter.
If you lower the number of parameters and lower the memorylimit - is there a point where it works?

Hmm, it still works without hyperv and the update itself is put on hold. There is only a security update installed, not the other one.
It seems that it works with "-memoryLimit 8G". ...And now, back to 10G, it still works with "-isolation hyperv". With almost the same resources on the host. How can that be?
The whole morning it did not work. We did not restart docker or the host in the meantime. Strange. Can you please keep the issue open for one week, I will keep an eye on our deployments and let you know if I am able to damage it again :/

OK

I have a 64GB machine on 1909.
Just tried to see how many Hyperv containers I could create with 20G memorylimit.
In the old days, creating a hyperv container with 20G memorylimit would allocate 20G memory.
Turns out it still does - it just allocates them in the pagefile and only keeps the allocated memory in memory - pretty smart if you ask me.
I had a some other images running and after 2 images my machine looks like:

111G out of 113G pagefile used.
creating one more fails with: The paging file is too small for this operation to complete.
pagefile=auto never creates a pagefile larger than physical memory * 2 and even though I had 30+ GB free memory - I could not create another 20G container.
Removing one container:

Removing all containers:

Not sure what the allocated memory is, but it kind of makes sense...

Wow, Freddy! Thank you for that detailed analysis! Indeed, that makes sense, knowing the part about the page file allocation and automatic = max. 2x physical RAM.
I remember we had >10 containers running, but some of them still in process isolation. 48 RAM * 2 = 96 page file would allow 9 containers with hyperv isolation and 10G.
That's it! I have now reduced maxMemory to 5G (+ 3G in case of the test framework). Probably we can reduce it by 1-2 GB over time if it runs stable now.
Definitely something you can add to the readme.
Thanks again, Freddy! 1 out of 100 problems solved/demystified. 99 to go :)

problem fixed here : https://youtu.be/Oh6dga-Oy10

problem fixed here : https://youtu.be/Oh6dga-Oy10

Thanks this worked prefectly


Use last block for rolling node snapshot

Waiting for dependancies on https://github.com/octo-technology/tezos-link/pull/79


(gh-680)[openstack] enable support for multiple regions

Add optional :openstack_region config key to tell beaker which region to use.
Add support for non-floating IPs, if the machine is provisioned automagically with one.
Fixes #680

Can one of the admins verify this patch?

Please associate your commit with a gh issue number like (gh-xxx).
@electrical, how does this look to you?

Review comment still current.

Can one of the admins verify this patch?

Review comments still current, will close out next week due to inactivity.

Closing due to inactivity.

Here's your associated beaker jira bug:
https://tickets.puppetlabs.com/browse/BKR-27


include ExcludeInboundPorts and ExcludeOutboundPorts parameters

Q
A

Bug fix?
no

New feature?
yes

API breaks?
no

Deprecations?
no

Related tickets

License
Apache 2.0

What's in this PR?

ExcludeOutboundPorts and  ExcludeInboundPorts is configurable.
Why?

add new parameters in Istio CRD
Additional context

necessary to configure the ports where not to capture egress traffic
Checklist

[x] Implementation tested
[x] Error handling code meets the guideline
[x] Logging code meets the guideline
[x] User guide and development docs updated (if needed)

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

Thank you for your PR, @hcavarsan!
I think it's all good, I just have one suggestion regarding the description of the fields as you can see below. (I got the wording from here: https://preliminary.istio.io/latest/docs/reference/config/annotations/) If you agree with that change, pls regenerate the CRDs as well.

done @Laci21, thanks!


Undo system

Problem
Currently if you make a change, such as deleting a column, there is no way to get it back.
Solution
Undo system that caches the tableState operations preformed. Uses the same hotkeys as Obsidian ctrl + z, ctrl + shift + z
Additional details
No response

@raybb @icebruce added in 6.9.0

TODO

add undo for filter rules
add redo implementation for tag-cell-add-command

Fantastic!! Thank you :)


Forge command not found even when proving it is available

[build]
pre-build = [
	"apt-get -y install apt-transport-https ca-certificates",
	"curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -",
	"echo 'deb https://dl.yarnpkg.com/debian/ stable main' | tee /etc/apt/sources.list.d/yarn.list",
	"apt-get update && apt-get -y upgrade && apt-get install -y libclang-dev pkg-config protobuf-compiler nodejs yarn",
	"curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y --profile minimal",
	". /root/.cargo/env",
	"cargo install --git https://github.com/foundry-rs/foundry --profile local --locked forge",
	". /root/.cargo/env",
	"forge --help"
]

I have the following pre-build script and able to see the output of forge --help.
Once my application gets to the step where there is a build.rs that uses forge, the cross build fails with forge not installed
fn generate_abis() -> Result<(), Box<dyn error::Error>> {
    run_command(
        Command::new("forge")
            .arg("build")
            .arg("--root")
            .arg("./contracts"),
        "https://getfoundry.sh/",
        "generate ABIs",
    )
}

Any help solving this would be greatly appreciated

ah nice yeh I will give that a go thank you!

also, I'd like to voice my dislike for this solution :3 better solution would be a pre-compiled forge binary that you simply download

@Emilgardis yeh I would like to do that but the GLIBC issues do not allow it on the default ubuntu container in cross-rs

I think this should work
# Cross.toml
[build.env]
dockerfile = "Dockerfile.forge"

# Dockerfile.forge
FROM ghcr.io/foundry-rs/foundry:latest as foundry

ARG CROSS_BASE_IMAGE
FROM $CROSS_BASE_IMAGE
COPY --from=foundry /usr/local/bin/forge /usr/local/bin/forge

ooo that would be much cleaner if I could get it to work
I am getting the following error when I add that to my cross.toml
#2 [internal] load build definition from Dockerfile.forge
#2 transferring dockerfile: 221B done
#2 DONE 0.0s
Dockerfile.forge:6
--------------------
   4 |
   5 |     ARG CROSS_BASE_IMAGE
   6 | >>> FROM $CROSS_BASE_IMAGE
   7 |     COPY --from=foundry /usr/local/bin/forge /usr/local/bin/forge
--------------------
ERROR: failed to solve: base name ($CROSS_BASE_IMAGE) should not be blank
Error:
   0: could not run container
   1: when building custom image
   2: when building dockerfile
   3: `docker buildx build --progress auto --label 'org.cross-rs.for-cross-target=aarch64-unknown-linux-gnu' --label 'org.cross-rs.runs-with=x86_64-unknown-linux-gnu' --label 'org.cross-rs.workspace_root=/home/runner/work/rundler/rundler' --tag localhost/cross-rs/cross-custom-rundler:aarch64-unknown-linux-gnu-c9fbe --build-arg 'CROSS_DEB_ARCH=arm64' --build-arg 'CROSS_BASE_IMAGE=ghcr.io/cross-rs/aarch64-unknown-linux-gnu:main' --file Dockerfile.forge --output 'type=docker' /home/runner/work/rundler/rundler` failed with exit status: 1

interesting, it's clearly passing the build arg --build-arg 'CROSS_BASE_IMAGE=ghcr.io/cross-rs/aarch64-unknown-linux-gnu:main' so it should work fine

can you try FROM ${CROSS_BASE_IMAGE} maybe?

ooohh! Sorry, I forgot how dockerfiles work...
ARGS for FROM need to be specified upfront...
ARG CROSS_BASE_IMAGE
# Dockerfile.forge
FROM ghcr.io/foundry-rs/foundry:latest as foundry

FROM $CROSS_BASE_IMAGE
COPY --from=foundry /usr/local/bin/forge /usr/local/bin/forge

ok I got further with that update however I get a weird error
#7 extracting sha256:211eac2d596e7b81f6f8a379c1ca93b747ce4e063388cd28949156bc7fcaed85 done
#7 DONE 19.9s

#8 [stage-1 2/2] COPY --from=foundry /usr/local/bin/forge /usr/local/bin/forge
#8 DONE 2.6s

#9 exporting to docker image format
#9 exporting layers
#9 exporting layers 1.6s done
#9 exporting manifest sha256:bca5fec824b98b01fa68cfad86ccd65f555afdf842d0346d8fdb847bf20ff0bf done
#9 exporting config sha256:b78c04d8d3442c2835f11a5ad6a6e5c449c6427a064a435141acc9b48ffec4ac done
#9 sending tarball
#9 ...

#10 importing to docker
#10 DONE 25.2s

#9 exporting to docker image format
#9 sending tarball 33.7s done
#9 DONE 35.4s
#0 building with "cross-builder" instance using docker-container driver

#1 [internal] load build definition from Dockerfile.aarch64-unknown-linux-gnu-custom
#1 transferring dockerfile: [271](https://github.com/alchemyplatform/rundler/actions/runs/6671060091/job/18132202267#step:8:272)B done
#1 DONE 0.0s

#2 [internal] load metadata for localhost/cross-rs/cross-custom-rundler:aarch64-unknown-linux-gnu-c9fbe
#2 ERROR: failed to do request: Head "http://localhost/v2/cross-rs/cross-custom-rundler/manifests/aarch64-unknown-linux-gnu-c9fbe": dial tcp <IP_ADDRESS>:80: connect: connection refused
------
 > [internal] load metadata for localhost/cross-rs/cross-custom-rundler:aarch64-unknown-linux-gnu-c9fbe:
------
Dockerfile.aarch64-unknown-linux-gnu-custom:2
--------------------
   1 |
   2 | >>>                 FROM localhost/cross-rs/cross-custom-rundler:aarch64-unknown-linux-gnu-c9fbe
   3 |                     ARG CROSS_DEB_ARCH=
   4 |                     ARG CROSS_CMD
--------------------
ERROR: failed to solve: localhost/cross-rs/cross-custom-rundler:aarch64-unknown-linux-gnu-c9fbe: failed to do request: Head "http://localhost/v2/cross-rs/cross-custom-rundler/manifests/aarch64-unknown-linux-gnu-c9fbe": dial tcp <IP_ADDRESS>:80: connect: connection refused
Error:
   0: could not run container
   1: when building custom image
   2: when pre-building
   3: `docker buildx build --progress auto --label 'org.cross-rs.for-cross-target=aarch64-unknown-linux-gnu' --label 'org.cross-rs.runs-with=x86_64-unknown-linux-gnu' --label 'org.cross-rs.workspace_root=/home/runner/work/rundler/rundler' --tag localhost/cross-rs/cross-custom-rundler:aarch64-unknown-linux-gnu-c9fbe-pre-build --build-arg 'CROSS_CMD=apt-get -y install apt-transport-https ca-certificates
      curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -
      echo '\''deb https://dl.yarnpkg.com/debian/ stable main'\'' | tee /etc/apt/sources.list.d/yarn.list
      apt-get update && apt-get -y upgrade && apt-get install -y libclang-dev pkg-config protobuf-compiler nodejs yarn' --build-arg 'CROSS_DEB_ARCH=arm64' --file /home/runner/work/rundler/rundler/target/aarch64-unknown-linux-gnu/Dockerfile.aarch64-unknown-linux-gnu-custom --output 'type=docker' /home/runner/work/rundler/rundler` failed with exit status: 1

looks like a strange local host error

ugh, will have to investigate that, I think I know the cause.
for now, just remove any commands in pre-build and use RUN apt-get update && apt-get install my-dependency if you need to install something

yeh no worries I think I can do that. Will let you know how it goes. Thanks for the help!

Adding build dependencies to the forge docker container worked until it ran into a permissions issue
Resolving deltas: 100% (129/129), done.
Failed to install solc 0.8.22: Permission denied (os error 13)
Error:
Permission denied (os error 13)
Error: "Failed to generate ABIs."
warning: build failed, waiting for other jobs to finish...
make[1]: *** [Makefile:39: build-aarch64-unknown-linux-gnu] Error 101
make[1]: Leaving directory '/home/runner/work/rundler/rundler'
make: *** [Makefile:44: docker-build-latest] Error 2
Error: Process completed with exit code 2.
When I run it locally using sudo it works but my github action does not like when I use sudo due to the cargo install and the PATH

i'm not sure I understand? That doesn't seem related to cross.

Yeh its not specific to cross I think, just a permissions error in the docker custom container

error: failed to run custom build command for `rundler-types v0.1.0-beta (/home/runner/work/rundler/rundler/crates/types)`

Caused by:
  process didn't exit successfully: `/target/release/build/rundler-types-ed3a290aef67a0d1/build-script-build` (exit status: 1)
  --- stdout
  cargo:rerun-if-changed=contracts/lib
  cargo:rerun-if-changed=contracts/src
  cargo:rerun-if-changed=contracts/foundry.toml

  --- stderr
  fatal: detected dubious ownership in repository at '/home/runner/work/rundler/rundler'
  To add an exception for this directory, call:

  	git config --global --add safe.directory /home/runner/work/rundler/rundler

  Error: "Failed to update submodules."

Have you seen this happen in the contianers if the repo needs to import submodules?

This seems related, don't know how to fix
https://github.com/actions/checkout/issues/766

We pull in git submodules to be used for code generation using forge, but this looks like it will be a new error going forward so I will just remove the git submodule stuff from build.rs and I think it should be fine

thank you!


Invalid edition [free] for addon rias/statamic-data-import

Statamic Version: 3.2.31
Hello, I attempted to install this package, but upon installation an error is thrown when attempting to access the Addon via the Statamic Control Panel:
Invalid edition [free] for addon rias/statamic-data-import

Try to set it via : composer require rias/statamic-data-import


Don't call closeHandler if it is nil

Issue: #852 closeHandler callback can be nil in an initializer

@swift-ci test

@swift-ci Please test Windows

@ahoppen My pleasure. Great project!


Validate extension safety only on dynamic frameworks

Summary
Only validate the dynamic frameworks (those with apple_common.AppleDynamicFramework) when calling the partials.extension_safe_validation_partial partial. This mimics the rules_apple approach more correctly:
https://github.com/bazelbuild/rules_apple/blob/eb5c03a606b103e9f8b72de954103eb00cf127f7/apple/internal/ios_rules.bzl#L1049-L1053
Discovered this issue when playing around with rules_apple_linker and our app extensions since it's provided as a deps entry but not a classic example of what would be there.

Somewhat stupidly, this was already merged as part of https://github.com/bazel-ios/rules_ios/commit/9a705f8f5a9b1fdfcf9ae987a5b513e3d92f9ade. 🤦


defaultContentLanguage error in site without English

Hi there,
This is probably related to issue 4298.
My site has only one language which is not English. In my config.toml, these are my language settings:
# Language Configuration
defaultContentLanguage = "fr"

[languages]
  [languages.fr]
    lang = "fr"
    languageName = "Français"
    weight = 0

My site builds fine on hugo < 0.32. On 0.32 and 0.33 I got the panic: proc not found error. Now on 0.34 (linux/amd64) I'm getting Error: site config value "en" for defaultContentLanguage does not match any language definition even though the site is configured only in French.
Is this a bug, or did I maybe do something wrong with language configuration?
Many thanks for all your work.

Can you try Hugo 0.35? I remember doing some additional testing (and I suspect also fixing this) in relations to the "language toggle" feature.

Sorry for not getting back any sooner. Still the same problem in 0.35 and 0.36.

...and I didn't mean to close the issue, either... :-S

I can confirm the same problem: using hugo v. 0.35 in a language other than English I get the same error message.
In my case I solved it replacing languageCode = "es" in my config.toml file by defaultContentLanguage = "es"

Same issue here with version 0.78.2


Midis

Do you think you can put the midis for all the songs you made in Fl Studio shit? I'm just looking for the Arch one to make a cover from it but if you can put the other midis in, that would be helpful.

download the arch flp and go to the voices patterns

Oh ok. Thanks.


Evaluating SCHISM BMI as a NextGen Formulation

Short description explaining the high-level reason for the new issue.
Steps to compile SCHISM model, BMI shared libraries, and BMI driver to test functionality (single thread)

Please go ahead and download my latest forked version of SCHISM, which includes a BMI directory in the following pathway on GitHub: https://github.com/jduckerOWP/schism_NWM_BMI/tree/BMI_Branch
Inside the forked version of my SCHISM branch above, please follow the instructions highlighted in the README.md file to compile the SCHISM mode, BMI shared libraries, and the SCHISM BMI driver.
Once you have completed these steps, please go ahead and comment on this issue and I will provide a small SCHISM model setup to test the BMI driver for NextGen initiatives moving forward. We can go back and forth on requests needed by the model engine team to integrate the SCHISM BMI as a functioning model within the current NextGen model engine framework.

Updated documentation and Wiki pages have been created as a guide for compiling SCHISM source code and the BMI. Please refer to this moving forward SCHISM_BMI_wiki_pages

Documenting where Jason and I have gotten with this:

I installed the necessary packages in a clean Ubuntu docker container

build-essential
cmake
make
gfortran
libnetcdf-dev
libnetcdf-mpi-dev
libnetcdff-dev
libopenmpi-dev
netcdf-bin

And linked

ln -s /usr/bin/python3 /usr/bin/python

because the SCHISM build system runspython in one or two spots to pre-process some things.

Enabled these variables in SCHISM to get behavior compatible with our intended BMI usage:

OLDIO
USE_ATMOS
USE_NWM_BMI

For library compilation to use -fPIC to appropriately produce code that can be loaded with dlopen(), rather than appending that to the CMAKE_{C,CXX,Fortran}_Flags variables (which produced build errors for me because of ; appearing in the resulting compilation command lines), I inserted

add_compile_options("-fPIC")

In the top-level SCHISM CMakeLists.txt

I posted one change to Jason's branch to replace literal directory paths with a CMake variable path pointing at the project source directory, https://github.com/jduckerOWP/schism_NWM_BMI/pull/1

After clearing all of the above, Jason and I looked into the BMI implementation code and discussed initialization and coupling data flow. There's a challenge posed by the time integration scheme that SCHISM uses, in that it wants the atmospheric forcing values for a timestep ahead of its own execution. As initially written, the SCHISM BMI implementation takes input for variables with names Foo_t0 and Foo_t1corresponding directly to its internal structure, and exposes those to the driver (eventually, the ngen model engine). My sense was that this would require an excess of special-case code in the model engine to properly feed SCHISM forcings data, so we instead decided to expose the relevant input variables without_t0/_t1` elaboration, and have the first step initialize both arrays. Jason is revising that now.
We also checked our mutual understanding of the coupling scheme between inland hydraulics and SCHISM. For now, we expect to have SCHISM strictly downstream of the coastal outflows from the inland hydraulic routing, with the routing unaffected by the water levels SCHISM predicts at the coastline. This will at least allow for a demonstration of the external data flows of the fully coupled system, with refinement to possible two-way coupling able to be developed later.

Hi Phil, I've gone ahead and finished all the required tasks on my end for you to move forward with the SCHISM BMI test case scenario as a NextGen formulation. The completed tasks are highlighted below:

Revised the SCHISM BMI implementation to only advertise a single variable that will dynamically deal with internal SCHISM fields of "t0" and "t1". For the time being, the assumption here will be during the first hour of the model run, fields will remain statics (t0=t1) until NextGen model engine can advertise the following of hour of fields from other respective models. Revisions to the bmischism.f90 and the SCHISM BMI driver test (schism_BMI_driver_test.f90) were pushed into the development branch that you have previously compiled SCHISM_BMI_Branch
A Lake Champlain BMI model setup (includes BMI configuration file) has been precompiled for your NextGen formulation test with the SCHISM model itself. I've zipped up the entire model setup and you can download it through my Google Driver here: SCHISM_Lake_Champlain_BMI_Model_Setup
To support the offshore water levels for the SCHISM Lake Champlain model setup, we've had to develop a Python BMI application that will essentially advertise regridded water level fields to the boundary nodes of the SCHISM mesh. I've constructed this application essentially mimicking the ngen/extern/test_bmi_py directory within the ngen repository to create this required Python BMI to support realistic offshore water level fields for the SCHISM model. I've zipped up and uploaded the Python BMI application to the Google drive, which can be downloaded here for you: SCHISM_USGS_BMI_py_application

Once you've taken a look at all the products I've provided here, I would be happy to meet with you again at your convivence to game plan the NextGen formulation setup you intend to implement with the SCHISM Lake Champlain BMI model setup moving forward. Thanks again Phil for your work on this topic.

Here are some notes on how the current code aligns with the conventions for BMI that ngen presently expects. These observations are not necessarily requests for or intentions to change, so much as discussion points.
https://github.com/NOAA-OWP/ngen/blob/master/doc/BMIconventions.md
Re "Time Control"

The init config can specify a model_start_time other than 0, while the framework expects models to always treat that as 0. I expect we'll need to change this in the not-too-distant future, to align with time-stamped forcings, hot-starts, data assimilation, and so forth. Also, the variable isn't used for anything meaningful besides get_start_time
The init config can specify model_end_time, which is also unused for anything meaningful except `get_end_time
There's both a dt from schism_glbl, and a time_step_size defined in the BMI interface. If SCHISM has an internal notion of its time step, it's probably preferable to maintain a single point of truth and just set/reference that

For the sake of guiding work on integrating SCHISM with NextGen (mostly stuff I expect to be doing), here's a broad list of things that I see needing to get done along the way

[ ] Define and parse realization config structure for coastal models
[ ] Check (non-resource) constraints on loading multiple coastal model instances within a single process
[ ] Define how MPI processes will be mapped to coastal model instances
[ ] Implement sub-communicator creation in SCHISM
[ ] Call sub-communicator creation from ngen
[ ] Design/implement BMI 'coastal realization' formulation, analogous to catchment formulations
[ ] Add code to call coastal realizations from ngen (providing input variables, recording output variables, multi-process coordination, etc)

I'll open and link issues for some of these as I approach them.

Based on the change in #712, SCHISM won't have to create any sub-communicator at all. It'll just get the handled passed by the framework, and use it directly, since it'll be in the form the MPI Fortran bindings expect.

The SCHISM BMI code will eventually get merged to the schism-dev/schism-esmf. The blocking step is having our MPI code in the BMI code, so I'll prioritize that.

After digging into the ESMF MPI_Finalize issues, I checked and SCHISM has a very similar issue - its parallel_finalize unconditionally calls MPI_Finalize. That's actually all it does, so we could just drop the call to parallel_finalize from the BMI finalize routine, but that would not necessarily be a durable solution.


1.21.0 update breaks php 7.1 compatibility

This Line doesn't work in PHP 7.1:
protected static ?array $configParserOptions = null;
https://github.com/Shardj/zf1-future/blob/818e5609fa7acc41a2ea5cdd708144004b6f070b/library/Zend/Application.php#L70

Sorted https://github.com/Shardj/zf1-future/commit/51dd353ba28a3ae59143301c0d50da4849a46986

release-1.21.1 has the fix


ScanIndexForward doesn't show up immediately in the query preview

Describe the bug
ScanIndexForward doesn't show up immediately in the query preview.
To Reproduce

Visit http://localhost:8080.
Switch from SCAN to QUERY.
Type anything in the partition key to show the query preview.
Toggle the Sort ascending box.
Toggling should affect the query preview, but it doesn't. However, if the RUN button is clicked, the preview block will show the change immediately.

Expected behavior
Toggling should affect the query preview.
Screenshots

Desktop:

macOS Sonoma 14.5
Firefox 133.0.3 (aarch64)
kritishdhaubanjar/dynamodb-dashboard:v1.13.0 @ DockerHub

Additional context
None

As you reported, seems like the Preview is not reacting to the checkbox in UI. It appears when you Run the query. :thinking: . Let me fix that. Thanks!
https://github.com/user-attachments/assets/b670d35f-010a-4dbc-a921-ed8c5669797a

Fixed in https://github.com/kritish-dhaubanjar/dynamodb-dashboard/commit/d77ab0de28c128a160ee5775df5609fd9a439ee5


Create new alternative syntax

In tourjs they put attributes on the DOM elements themselves. Although I believe this is something I considered, it reduces the capabilities of the content (such as the ability to put HTML into the tooltips) however it makes it easier to find the highlighted DOM elements.

Maybe instead of putting the 'tooltip' content on each element, we can keep the 'list' isolated and just have a  or

Closing since #9 has a more fleshed out example


ports command in the compose file are reversed

Walked through this today and noticed that it doesn't work as-is.  "Error connecting to database".  It appears that the port command is transposed. I switched the ports to "80:8000" and all is well.  The setting is incorrect in the github repo as well.
docs : https://docs.docker.com/compose/compose-file/#ports

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

ID: b2472d79-baad-f202-75dc-c0d7c08e5c49
Version Independent ID: 7816cf1e-2264-e365-4d5c-b1fc9f7d08fe
Content: Create multi-container app in Web App for Containers - Azure App Service
Content Source: articles/app-service/containers/tutorial-multi-container-app.md
Service: app-service
GitHub Login: @msangapu
Microsoft Alias: msangapu

@rbmathis Thanks for the feedback! We are currently investigating and will update you shortly.

@rbmathis We encountered the same issue. We have assigned the doc author as a result.
@msangapu Is this related to the port forwarding changes that we had discussed a few weeks back? I am having the same issue as the customer.

Hi team, the sample is correct. It should be host:container. I'm not aware of any changes to the platform. Let me test and get back to you.

Hi team, I was not able to repro this issue. The configuration shown in this article hasn't changed for over a year. Let me know if you're still having this issue.

#please-close


[refactor] Improve Function and ImportModule

In this PR, the following improvements are introduced:

In wasmedge-sys, improve the design of Function and ImportModule.
Correspondingly, Func, ImportObjectBuilder, VmBuilder and Store in wasmedge-sdk are refactored.

Hello, I am a code review bot on flows.network.
It could take a few minutes for me to analyze this PR. Relax, grab a cup of coffee and check back later. Thanks!

@L-jasmine Thanks for the review!


Missing CreateEmailOptions type in exports

Hello ! I've just noticed that Type CreateEmailOptions has been removed recently, I'd like to know why, otherwise I have an alternative to this type :
type CreateEmailOptions = Parameters<typeof resend.emails.create>[0]

Have a nice day

^ +1

yes pleaseeeeee, creating a generic helper function is quite a common use case for these types

Yes, why has it been removed?

Thanks for reporting this, let's definitely re-add. Can one work on PR on this?

#122

Just expose all I/O types related to the public API.

// src/index.ts
export { Resend } from './resend';
export { ErrorResponse  } from './interfaces';
export { CreateEmailOptions } from "./emails/interfaces/create-email-options.interface";

is all we need, do I really need to create a PR for this?

Hi, can we merge #305 ? And maybe export other types as well (CreateEmailRequestOptions , CreateEmailResponse)

We still can't use the latest version of the node client (without weird workarounds) and are forced to stay on<EMAIL_ADDRESS>just because of this.
It would be great to expose CreateEmailOptions and CreateEmailResponse.
Do you think it would be possible to expose these types along with adding the statusCode key to ErrorResponse (it's currently missing)? @bukinoshita @zenorocha

Here is a workaround for the latest version (3.2.0 as of now):
import {Resend, ErrorResponse as ErrorResponseType} from 'resend';

type CreateEmailOptions = Parameters<typeof Resend.prototype.emails.send>[0];
type CreateEmailResponse = Awaited<ReturnType<typeof Resend.prototype.emails.send>>;
type ErrorResponse = ErrorResponseType & {statusCode: number};
type ResendResponse = CreateEmailResponse | ErrorResponse;

For anyone using pnpm, you can path resend package and export all the types you need.
Run pnpm path resend@<version>
Update dist/index.d.ts file in the extracted folder to export the types you want.
Then run pnpm patch-commit <path to the extracted directory>
At the end restart your ts server.

#396 appears to resolve this


Fix encoding issues during download

Pull Request Checklist
Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.
Before submitting, make sure you've checked the following:

[x] Target branch: Please verify that the pull request targets the dev branch.
[x] Description: Fix this https://github.com/open-webui/open-webui/discussions/6480
[ ] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
[ ] Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
[ ] Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
[ ] Testing: Have you written and run sufficient tests for validating the changes?
[x] Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
[x] Prefix: To cleary categorize this pull request, prefix the pull request title, using one of the following:

BREAKING CHANGE: Significant changes that may affect compatibility
build: Changes that affect the build system or external dependencies
ci: Changes to our continuous integration processes or workflows
chore: Refactor, cleanup, or other non-functional code changes
docs: Documentation update or addition
feat: Introduces a new feature or enhancement to the codebase
fix: Bug fix or error correction
i18n: Internationalization or localization changes
perf: Performance improvement
refactor: Code restructuring for better maintainability, readability, or scalability
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)
test: Adding missing tests or correcting existing tests
WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry
Description
When I upload a chinese file and want to download it, it will raise error:
{
    "detail": "[ERROR: Error getting file content]"
}

The reason is that the method calling Starlette is incorrect. There is no need to pass a header parameter when use FileResponse, only filename needs to be passed, and Starlette will handle it internally.
Related discussions: https://github.com/open-webui/open-webui/discussions/6480
Related PR with Starlette:

https://github.com/encode/starlette/pull/792
https://github.com/encode/starlette/pull/790

Content-Disposition": 'attachment; is required for security purposes. Feel free to open a new PR!

If filename passed in, Starlette will automatically concatenate  Content Disposition ':'attachment.
https://github.com/encode/starlette/pull/792/files

Content-Disposition": 'attachment; is required for security purposes. Feel free to open a new PR!


Cannot interact with the map on Android (v2.2.9 - ionicv1)

I'm submitting a ...  (check one with "x")

[ ] question
[X ] any problem or bug report
[ ] feature request

If you choose 'problem or bug report', please select OS:  (check one with "x")

[ X] Android
[ ] iOS

cordova information:  (run $> cordova plugin list)
com.googlemaps.ios 2.6.0 "Google Maps SDK for iOS"
com.telerik.plugins.nativepagetransitions 0.6.5 "Native Page Transitions"
cordova-plugin-camera 2.2.0 "Camera"
cordova-plugin-crosswalk-webview 1.7.2 "Crosswalk WebView Engine"
cordova-plugin-device 1.1.2 "Device"
cordova-plugin-googlemaps 2.2.9 "cordova-plugin-googlemaps"
cordova-plugin-inappbrowser 1.6.1 "InAppBrowser"
cordova-plugin-statusbar 2.4.1 "StatusBar"
ionic-plugin-keyboard 2.2.0 "Keyboard"
Current behavior:
I'm using ionic v1.
After "plugin.google.maps.Map.getMap(div)" call, map is frozen (i cannot touch neither interact with it). It happens only on android. Map div has a data-tap-disabled="true" attribute (even I've not set it).
If I try to call map.setClickable(true) or any other method on plugin, i got the error log below (see attached screenshot)
Expected behavior:
On IOS everything is fine, I can interact with the map normally. It should be ok even in Android (it was before last update from previous version)
Related code, data or error log (please format your code or data):

Please share your project files on github.

Hi, unfortunately I cannot share my project.
It's a very big project so I don't know if I can arrange a demo.
I'll do the best as I can.
Will be a video ok? Or you need the code?

Will you see a video to a doctor when you have a health problem?

Hi,
I see your point, it tooks me a while to arrange a demo ( i should remove a lot of code, and unuseful things). I've invited you to the demo project (it comes with everything in it, modules, plugings etc..)
Just run "ionic run android" to see it on your device/emulator.
Thank you for your support.

Sorry for late response, and thank you for sharing your project.
I have tried to build your project, but your project requires kind of old environment, such as Gradle 2.2
For the reason, I couldn't build your project.
I will try this tomorrow again, but I appreciate if you update the environment.

Hi,
any news? Did you finally find out a way to build the project?
I've tried to update gradle, but it breaks my build.

No luck so far. I can't build your project.

I've just made a commit with a gradle extra which should give you compatibility with old plugin. Please try again to make the build and let me know if this solve your issue.

Sorry to bother you, still facing same issue...

No, it is too much old. I can't build your app.

Regarding of the error message, it means you tried to something before the map is ready.
For example, all methods of dynamic class (except Map.getMap() method) have to run after the MAP_READY event.
In your code, you write like this:
map = plugin.google.maps.Map.getMap(div,{ ... });
map.setVisible(true);
map.setMyLocationEnabled(false);
map.setMapTypeId(plugin.google.maps.MapTypeId.ROADMAP);

map.addEventListener(plugin.google.maps.event.MAP_READY, onMapReady);

Well, this is bad code syntax (at this time).

You have to write like this:
map = plugin.google.maps.Map.getMap(div,{ ... });
map.addEventListener(plugin.google.maps.event.MAP_READY, onMapReady);

function onMapReady() {
  map.setVisible(true);
  map.setMyLocationEnabled(false);
  map.setMapTypeId(plugin.google.maps.MapTypeId.ROADMAP);
}

The plugin v2.0 to v2.1.x executes all methods when you write the code exactly.
However, from the plugin v2.2.0, this maps plugin contains internal command queue, and execute the methods one by one.
This prevents unexpected errors from app developers.
That's why you can't run the same code with the latest version.

Well, there is one more information.
I wrote Well, this is bad code syntax (at this time). in the above comment.
The meaning of (at this time) indicates the code syntax would be changed in the next version.
Since this plugin takes callback as the second argument (like map.addMarker({...}, callback), the application code would become kind of messy.
In the next version, the maps plugin allows without the callback (like var marker = map.addMarker({...})), even without MAP_READY.

So the conclusion is, with the v2.2.9, your code is wrong, but your code is correct with the next version.

Hi, I've moved that lines inside the event, the error has gone away (no problem on refactoring the code until the new version).
Unfortunately, the map still remains unresponsive to touch events.
Probably this is due to anything else, could it be crosswalk with those lines in config.xml?
<preference name="xwalkVersion" value="22+"/>
<preference name="xwalkCommandLine" value="--disable-pull-to-refresh-effect"/>
<preference name="xwalkMode" value="embedded"/>
<preference name="xwalkMultipleApk" value="true"/>
<preference name="xwalkZOrderOnTop" value="true"/>

Try to remove this line <preference name="xwalkZOrderOnTop" value="true"/>

Unfortunately removing this line has no effect.

Um, unfortunately, I have no idea, because I can't build your project.
I strongly recommend you to start creating new project.

It's crosswalk.
I've removed all code, leaving only the getMap.
I've removed also other plugins (leaving only crosswalk and mapsplugin).
Removing also crosswalk, the map becomes responsive to touch events.
I think it is related in some way to "xwalkZOrderOnTop" preference.
It should be "true" in previous version of this plugin to make the map clickable as said

https://github.com/mapsplugin/cordova-plugin-googlemaps-doc/blob/master/v1.4.0/Installation/crosswalk/README.md
https://github.com/crosswalk-project/cordova-plugin-crosswalk-webview/pull/65

Maps plugin seems to ignore it. Is it possible or am I wrong?
Thank you.

Crosswalk is already deprecated, and recent devives have enough power without Crosswalk.

As I said, is Crosswalk.
I understand you do not support compatibility for Crosswalk, so I'm planning to remove it and see what happens, as I'm not able to solve this problem by myself. My concern is that I'll miss some functionality on old devices, which, unfortunately are still on the market and use old webviews.
If you could give me an hint on what to try to solve this issue, it would be appreciated.
If not, I can understand and I'll figure it out my best options.

Well, even if you still want to support older devices, the maps plugin does not support older version less than Android 4.4.

That's true.
Thank you for your time, I'll probably go removing crosswalk and going up to 4.4 version as minimum supported.
Have a nice day.

I have the same issue and there is no crosswalk in my app. However the maps becomes unresponsive in android version 7.0, maps version 2.2.9. It works fine on all other devices. Please help


Cleanup proguard configuration

Remove custom KotlinX Serialization config as it's already provided, see https://github.com/Kotlin/kotlinx.serialization#android.
Delete empty config files.

@SimonMarquis Always good to see redundant code being deleted, thanks.
For any other readers, the kotlinx.serialization rules are here so don't need to be in NiA: https://github.com/Kotlin/kotlinx.serialization/blob/master/rules/common.pro


Extract event ABI when encoding

Summary
It is possible to extract a type safe item from an ABI. Currently, we duplicate the TransactionAdded event from the DelayModifier ABI in the relative encoder. This extracts it instead.
Changes

Tweak format of existing event encoder.
Extract TransactionAdded from DelayModifier ABI.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall first build on tx-added-encoding at 90.759%

Totals

Change from base Build<PHONE_NUMBER>5:
90.8%

Covered Lines:
7656

Relevant Lines:
8093

💛  - Coveralls


[Feature]: adding a new page to display all contributors✨

@param-code i can improve the contributors page.

i can covert this to :

can you assign me this issue,

@param-code i can improve the contributors page.

i can covert this to :

can you assign me this issue,

Okay.Let's see what you can do.All the Best!!


How to save face pictures？

You need to cut the areas on the bitmaps manually. The library does not provide such functionality at the moment.


Fixed README to link the correct Clonkk github profile

The README was pointing some poor soul who happens to use the same name :smile:

oops... thanks for fixing this! 😄
actually in order to merge ideally you should change the index.nim file and run nim r docs\index (so that it will be correctly regenerate both the index.html and README.md file, you will need also to install nimoji for that). If you want to try, you are most welcome, otherwise let me know and I will do it!

Ah I didn't see you were generating the README file.

thanks, what you did is correct. the CI is failing because the testing framework has some bugs:

as a first issue the CI it is not clear what the issue is (I should improve on that).
anyway I think the issue is the fact that when you generate the document the repo link in top right of the document goes to your fork and not to the upstream repo.

for the moment a manual fix of the problematic line could be done (I will add a note in the code), but I have to think of something better to improve UX for contributors...

damn, now CI is being very picky (two whitespace issues and I have no idea where they come from). I really feel bad about it.

Ah, I use neovim and it automatically trim whitespace in file when I save them. Could be that ?

Ah, I use neovim and it automatically trim whitespace in file when I save them. Could be that ?

yes, for the end of file whitespace it is most likely that. Maybe it also removed the other whitespace which appears mid document (which I have no clue why is there...)?

Closing for a cleaner branch https://github.com/pietroppeter/nimib/pull/42


[✨] Qwik does not recover from network failure

Which component is affected?
Qwik Runtime
Describe the bug
What I did:

npm install
npm run preview
In the chrome window that opens, I go to the developer tools, under the network tab, and set throttling to offline
I click on TODO demo 📝. Nothing happens
I then set throttling to No throttling
I click on TODO demo 📝 again. Nothing happens

What I expect:
At step 6, I expect the todo demo to load and work fine.
What actually happens:
At step 6, nothing happens.
Reproduction
https://github.com/swoutch/qwik-recover-offline
Steps to reproduce

npm install
npm run preview
In the chrome window that opens, go to the developer tools, under the network tab, and set throttling to offline
click on TODO demo 📝. Nothing happens
set throttling to No throttling
click on TODO demo 📝 again. Nothing happens

System Info
System:
    OS: macOS 13.0.1
    CPU: (8) arm64 Apple M1
    Memory: 162.73 MB / 8.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 19.3.0 - ~/.nvm/versions/node/v19.3.0/bin/node
    Yarn: 1.22.18 - ~/.nvm/versions/node/v12.22.1/bin/yarn
    npm: 9.2.0 - ~/.nvm/versions/node/v19.3.0/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 109.0.5414.119
    Firefox: 104.0.2
    Safari: 16.1
  npmPackages:
    @builder.io/qwik: 0.19.0 => 0.19.0
    @builder.io/qwik-city: 0.3.0 => 0.3.0
    undici: 5.20.0 => 5.20.0
    vite: 4.1.2 => 4.1.2

Additional Information
I'm not sure which qwik component is responsible for that, so I chose qwik runtime randomly

This is an enhancement, no framework can manage this offline behaviour

We moved this issue to qwik-evolution repo to create a RFC discussion for this.
Here is our Qwik RFC process thanks.


Deploy error 'Is a directory (os error 21)' occurs when special char in project path

Describe the bug
The Supabase CLI fails to deploy Edge Functions when the project path contains special characters (#). The error message suggests a directory issue, but the actual problem is the special characters in the path.
To Reproduce
Steps to reproduce the behavior:

Create a project directory containing special characters (e.g., /Users/username/Documents/#project/#app/)
Initialize a Supabase project in this directory
Create an Edge Function: supabase functions new my-function
Create a simple Edge Function in index.ts
Try to deploy using: supabase functions deploy my-function --project-ref [your-project-ref]
Observe the deployment error

Expected behavior
Either:

The deployment should work correctly with special characters in the path
Or the CLI should provide a clear error message indicating that special characters in the path are not supported

Screenshots
Error output:

Error output searchable:
supabase functions deploy [my-function] --no-verify-jwt --project-ref [my-project-ref]
Bundling Function: [my-function]
Error 'Is a directory (os error 21)' contains boxed error of unknown type:
  Os { code: 21, kind: IsADirectory, message: "Is a directory" }
Error: failed to create the graph

Caused by:
    Is a directory (os error 21)
error running container: exit 1
Try rerunning the command with --debug to troubleshoot the error.

System information

OS Version: macOS
CLI Version: 1.219.2
Docker Version: Latest

Additional context

Moving the project to a path without special characters resolves the issue
The error occurs in the Deno bundler when trying to access the function's index.ts file
This is a path handling issue that affects deployments on macOS when the project path contains '#' characters

I can confirm I've been able to reproduce, but with only two specials chars so far: # and ?, but other specials characters such as $ or % work well. Which lead me to think there is something on with shell path escaping.
The binding to the container that run the edge-runtime for bundling seems correct so the issue might actually come from the path normalization within the container bundling logic. I'm suspecting that maybe this is where things goes wrong: https://github.com/supabase/edge-runtime/blob/main/crates/sb_core/util/fs.rs#L208
Will investigate.


Set the path where all memories are saved

Currently we have default values in storage classes, like LTMSQLiteStorage. We should probably adjust the pipeline to move defaults up then, otherwise we'll have multiple places with default values.

I agree with you. Do you want me to do this as part of this PR ?

@arnaudgelas that would be awesome! Happy to streamline the review process.

@gvieira  Consider merging first #743, then you can review this one

Hey @arnaudgelas, thanks for the Pull Request.
Can you take a moment to check if this is still relevant, I'm saying because there were a lot of changes in regards to the Memory part of the project. Also, there are a lot of conflicts across the PR so maybe would be good to start a new branch from the main or resolve them. Let us know if you need any help and we’ll sort it out together.
Thanks!

Disclaimer: This review was made by a crew of AI Agents.
Code Review Comment for PR #542
Overview
This pull request introduces significant improvements to the crewAI project by addressing code quality issues and updating memory storage path configurations. The changes enhance maintainability and promote best practices.
Code Quality Findings
1. Pre-commit Error Fixes

Unused Imports: It's great to see the cleanup of unused imports across different modules. This helps in reducing the overall memory footprint and improves code readability.
__all__ Declarations: The introduction of __all__ in __init__.py files is a commendable move. It clearly defines the public API of the modules:# src/crewai/__init__.py
__all__ = ["Agent", "Crew", "Process", "Task"]

Code Formatting: The formatting of the with statement in fileHandler.py is improved for consistency:# Improved formatting
with open(self._path, "a", encoding="utf-8") as file:

Logger Improvements: Adding the missing datetime import in logger.py enhances logging accuracy.

2. Memory Storage Path Configuration

Centralized Configuration: Centralizing memory path management boosts flexibility in handling storage paths. The function get_memory_paths is a solid addition:def get_memory_paths(memory_path: Path | None = None) -> tuple[Path, Path, Path]:

Memory Initialization: The updated memory initialization in the Crew class enhances the encapsulation and management of memory usage.

Historical Context from Related PRs
It would be beneficial to refer to related PRs that may have previously addressed memory management or module structure since these changes build upon those foundations. Referencing those decisions can provide insights into the design choices made. However, due to technical constraints, I couldn't fetch that data directly.
Implications for Related Files
A notable impact of these changes will likely be felt in files directly interacting with the Crew, memory management, and logging:

Memory Management Files: Files like entity_memory.py, long_term_memory.py, and short_term_memory.py all relate closely to the changes made. Ensure that they align with the new configurations and utilize the updated memory management functions effectively.
Logger Module: Increased accuracy in logging will help in tracking memory states and errors, so it's critical to test thoroughly.

Specific Improvement Suggestions

Type Hints: Adding type hints enhances code clarity:
def log(self, level: str, message: str, color: str = "bold_green") -> None:

Docstrings: Consider implementing comprehensive docstrings for all new functions and classes:
def get_memory_paths(memory_path: Path | None = None) -> tuple[Path, Path, Path]:
    """
    Get the paths for different types of memory storage.
    Args:
        memory_path: Optional custom path for memory storage
    Returns:
        Tuple containing paths for long-term, short-term, and entity memory
    """

Error Handling: Implement error handling for memory path creation to guard against filesystem issues:
try:
    memory_path.mkdir(parents=True, exist_ok=True)
except Exception as e:
    raise RuntimeError(f"Failed to initialize memory paths: {str(e)}")

Validation of Memory Path Permissions:  Adding additional validation checks for memory path accessibility will further solidify the reliability of this system:
def validate_memory_path(path: Path) -> None:
    """
    Validate that the memory path is writable and accessible.
    """
    if not os.access(path.parent, os.W_OK):
        raise PermissionError(f"No write permission for memory path: {path}")

Conclusion
The modifications proposed in this pull request significantly improve both code quality and memory management functionality. The suggested improvements will further enhance robustness and clarity. Overall, excellent work on navigating these critical areas of the codebase!
Let's continue to build on this momentum toward cleaner and more modular code.

I will work on it next week

@gvieira @joaomdmoura I am looking forward to reading your reviews/comments


docusaurus.config.ts: Redirect docs to docs/latest

Tested and works: go to the https://redirect-docs-to-docs-latest.headlamp.pages.dev/docs/ , it should redirect to https://redirect-docs-to-docs-latest.headlamp.pages.dev/docs/latest .

I guess it needs to be deployed? This is 404 https://headlamp.dev/docs


PDO: support more fetch modes

[x] PDO::FETCH_BOTH
[x] PDO::FETCH_ASSOC
[x] PDO::FETCH_NUMERIC
[x] PDO::FETCH_KEY_PAIR PdoStatement->fetch*()
[ ] PDO::FETCH_KEY_PAIR in Pdo->query()
[x] PDO::FETCH_COLUMN in PdoStatement->fetch*()
[ ] PDO::FETCH_COLUMN in Pdo->query()
[ ] PDO::FETCH_GROUP
[ ] PDO::FETCH_UNIQUE
[x] PDO::FETCH_CLASS in PdoStatement->fetchAll()
[x] PDO::FETCH_CLASS in PdoStatement->fetchObject()
[ ] PDO::FETCH_CLASS in Pdo->query()
[ ] PDO::FETCH_CLASS in PdoStatement->setFetchMode*()
[ ] PDO::FETCH_OBJ
[ ] PDO::FETCH_INTO
[ ] PDO::FETCH_FUNC

See

https://www.php.net/manual/en/pdostatement.fetch.php
https://www.php.net/manual/en/pdostatement.fetchall.php
https://phpdelusions.net/pdo/fetch_modes#FETCH_COLUMN

relevant in

$pdo->query($query, $fetchMode);
$stmt->setFetchMode($fetchMode)
$stmt->fetch($fetchMode)

relevant code parts:
https://github.com/staabm/phpstan-dba/blob/4d442193a977424c78dc66de0ca65e50d84b40ff/src/PdoReflection/PdoStatementReflection.php#L49-L55
https://github.com/staabm/phpstan-dba/blob/4d442193a977424c78dc66de0ca65e50d84b40ff/src/PdoReflection/PdoStatementReflection.php#L96-L121
and adding corresponding tests in
https://github.com/staabm/phpstan-dba/blob/main/tests/default/data/pdo.php

PDO::FETCH_CLASS support would also be nice IMO

@xPaw since you are using some fetch types we do not yet support type-inference for: do you plan working on the missing fetch-modes?
I will support you in case there are questions left.

I don't currently have plans to look into that, sorry.

One thing worth pointing out is that some of the FETCH constants are actually flags, and not unique modes (thus they can be combined with some modes).
See here:
https://github.com/php/php-src/blob/bf9b774327f139f5770ea87797b933b603f979de/ext/pdo/php_pdo_driver.h#L65-L87

One thing worth pointing out is that some of the FETCH constants are actually flags, and not unique modes (thus they can be combined with some modes).

good point.
feel free to provide failing unit tests or open issues with concrete examples of things you used/found in the wild.
I am not interessted in adding every theoretical possible combination, but just those things people actually use


"Swap left command key and left control key in Wineskin" No longer works in El Capitan

Apparently somebody has already reported this issue here, https://groups.google.com/forum/#!topic/osx-karabiner/dQrvcRaCAnE
but for some reason that person never responded back when asked to provide private.xml and bundle identifier..
Well, here is mine.zip, I really hope this can get fixed.

The setting works well on my machine.
Please show me the App tab in EventViewer when you activate Wineskin app.
https://pqrs.org/osx/karabiner/document.html.en#eventviewer

(Random thought: is it possible that it is an issue affecting only some Wineskin apps?)

I am using Crossover. Is there a way I can make it work with apps on Crossover?

Karabiner requires apps be an OS X bundle forms to detect the application switching.
If these apps are bare binaries, we should wrap them by properly way.
(eg. There are possibiliity to solve by making a wrapper app by Automator.)


Model the client secret as an interface

Osin's current architecture assumes that the client secret will always be available in cleartext, and that validation of the client secret will be accomplished by simple string comparison.  My project, however, required that we treat client secrets in the same way we would a user password — they must be salted and hashed before being stored in a database.
This pull request introduces the Secret interface type, which defines a Validate(string) bool method to validate the client secret specified in an OAuth request.  This interfaces enables consumers of the osin package to define customized methods of validating client credentials.  The old, cleartext-based method is preserved in the new DefaultSecret type.

+1

Fixed by #103


Browserstack: iPhone 7 not found

Not sure why, but as soon as I try to do mobile testing, it tells me, that any device (iPhone 7, Samsung Galaxy S8 etc.) listed on browserstack could not be found. https://www.browserstack.com/automate/capabilities
Could not open connection: Could not find device: iPhone 7 (Behat\Mink\Exception\DriverException)

My capabilities:
            browser_stack:
                capabilities:
                    browserstack-tunnel: true
                    acceptSslCerts: true
                    browserstack-debug: false
                    device: 'iPhone 7'
                    os_version: '10.3'

Other configurations like ...
                capabilities:
                    browserstack-tunnel: true
                    acceptSslCerts: true
                    browserstack-debug: false
                    os: Windows
                    os_version: '7'
                    browser: IE
                    browserVersion: '10'

... are working like charm. Only device does not work.
Does anybody know why? Is anything missing in my configuration?

I suggest you to contact Browserstack to ask them what is the right device capability to specify for Selenium for these devices.

Answer is simple: If there is a real device, you can't test it emulated.
So even if you try to send "real_device: false" it wont work


Quota Error: Rate Limit Exceeded

We are using the Google Analytics Java API v3-rev116-1.20.0.
Once we have performed the authorisation step, we try to get the list of accounts using this code: analytics.management().accountSummaries().list().execute();
We have some users with a large list of accounts (in one example 647) and for these users they are getting the following 403 forbidden error:
Reason 403 Forbidden
{
"code" : 403,
"errors" : {{
"domain" : "global"
"message" : "Quota Error" : "Quota Error: Rate Limit Exceeded"
"reason" : "rateLimitExceeded"
}}
"message" : "Quota Error: Rate Limit Exceeded"
}
Is there a way for us working around this issue?

This tracker is for the library itself, not for generic analytics issues. I'd suggest making an issue on Stack Overflow with the google-analytics-api tag.

If we log into the Query Explorer: https://ga-dev-tools.appspot.com/query-explorer the request works correctly without any errors displayed.
This suggests to me that it is not a generic Analytics issue but an issue with the Java library connecting to the Analytics service.
When we try to retrieve the list of accounts using the following code:
analytics.management().accountSummaries().list().execute();
we are not in control of the request rate, this looks like a limitation of the library.
The above code works correctly for users with a smaller amount of accounts and only throws this exception when the user has a large amount of accounts (i.e. 647 in the above example).

The execute only issues one request. Does query-explorer work for the large accounts?

Yes, query explorer does work for large accounts.
The Java API does not, as it throws the exception mentioned when executing the following line of code.
analytics.management().accountSummaries().list().execute();
We did do a WireShark of the TLS traffic and the above line of code did seem to cause multiple requests, although we couldn't see what those request were due to it being over TLS.

@ejona86 Will this be re opened? Do you need anymore details?


Update version: GiulioSorrentino.CBriscola.WPF version 0.7.1

Checklist for Pull Requests

[ ] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

I'm sorry making you work so hard, but github translated again "trump suit" with "trump seed", and i find all my offline copies modified.
This version says "trump suit" not "trump seed", as my last that github has modified, and so must be.
Thanks.


SupportsListingInGroupByTag#listByTag is stripping the resource tags

I'm trying to fetch the resources with a specific tag from a resource group.
If I'm calling Azure.genericResource.listByTag then the resources in the list don't have any tags associated with them.
If I do the same thing but using listByGroup then the resources have the associated tags.
listByTag should just search for the specified tags, it should remove them.
I'm using 1.0.0-beta4.1

@clguimanMSFT are you still facing the issue or did you manage to move past it?

I haven't used the SDK in a while, but you should investigate and see if the API behavior described is what users would expect


Adds a number identifier to all mobs except players

About the PR
This adds a generic number identifier to all mobs so that griefers can be identified.
This is in response to getting reports of carps and ticks not following salvage rules so now we can identify them easier since players can report them by number. Extended it to include all generic passive mobs to identify unruly farm animals etc.
Screenshots

Changelog

:cl:

add: Added a number identifier to all mobs. Now it's easier to report rule breaking ghost roles such as ticks and carp.

Oh jesus god yes please this is very needed


Add shaded fraction (FS) calculation for true-tracking on flat terrain

Is your feature request related to a problem? Please describe.
It would be useful to have a shaded fraction calculation for true-tracking on flat terrain. It could be used in modeling thin film projects with (approximately) linear power loss due to self-shade.

Describe the solution you'd like
An implementation of equations 1-6 in Lorenzo 2011 [1], where inputs are:

tracker rotation angle (true-tracking, not backtracking)
ground coverage ratio
solar azimuth
solar elevation

And the output is shaded fraction (0-1) of each shaded row.
Describe alternatives you've considered
Custom implementations would not be difficult, but a built-in function would be nice. More robust versions that can account for non-horizontal tracker rotation axis, non-flat terrain, etc., would be nice, but are more difficult.
Additional context
Here's the description we used in a 2023 PVRW poster on the topic [2], adapted from [1]:
Calculate the ideal tracker angle,
ω = arctan(cos(θA) * sin(θel) / sin(θA))
where θel is solar elevation and θA is solar azimuth. Then calculate the shaded fraction of the array, FS, as
FS = max[0, (1-cos(ω)/GCR)]
where GCR is the row spacing divided by tracker table width.
[1] E. Lorenzo, L Narvarte, and J Muñoz. 2011. "Tracking and back-tracking". Progress in
Photovoltaics: Research and Applications 19: 747-753. https://doi.org/10.1002/pip.1085
[2] I. Azad, W. Hobbs, "Improved PV expected energy modeling with a simple self-shading model". NREL PVRW 2023. (proceedings pending)
[3] K. Anderson, W. Hobbs. "Improved CdTe PLR Estimates: Self-Shading and Spectral Mismatch". NREL PVRW, 2022. https://www.osti.gov/biblio/1846944

Wow I actually have code already ready for this including flipped terrain. I’m presenting it in a poster at pvpmc in may! Shall we compare?

@williamhobbs & @AdamRJensen I’ll send you my Jupiter notebooks and post a or here. @jdnewmil has looked it over too

@AdamRJensen and @mikofski, thanks for the quick replies! @cwhanse saw our poster at PVRW and suggested that this, along with https://github.com/pvlib/pvlib-python/issues/1690, could make for a good pvlib addition.
I like @AdamRJensen's  ideas:

I think the math would be relatively simple also for calculating shading for conditions where the actual tracker rotation
angle is not necessarily equal to true tracking. This would be a more general implementation and useful for more scenarios, e.g., it could be used for fixed-tilt systems.

@mikofski - should "flipped terrain" in your comment be "sloped terrain"?
What I proposed above also does not allow for anything other than North-South aligned trackers, which is not ideal.

Ha yes auto correct! (Shakes first!)

Is this already in pvlib.bifacial.infinite_sheds here?

Is this already in pvlib.bifacial.infinite_sheds here?

I'm quite confident that @cwhanse is correct. It certainly seems like Equation 32 of @kanderso-nrel's report on Slope-Aware Backtracking for Single-Axis Trackers

Is this already in pvlib.bifacial.infinite_sheds here?

#717 originally had that code as a public function in pvlib.shading but later changed it to be private.  I can't quite remember why.  Maybe we couldn't quickly agree on a public interface and didn't want to hold up the rest of the PR.

It certainly seems like Equation 32

This infinite_sheds function implements a special case of it where the axis tilt and cross-axis slope are zero, I believe.
One limitation of Eq 32 is that it assumes the shaded and shading rows are tracking together (i.e. they have the same rotation angle).  I have a generalized equation that addresses that limitation but it does not yet appear in any publication.  I think whatever we implement now should have an eye towards being extendable in the future to that generalization (probably just adding a kwarg for the second rotation angle).


Refresh_node(obj) freezes the page on large tree

Hi,
I have a problem with refresh_node() function. The tree is very large, but it shouldn't be a problem of this case because it should only send new ajax request for newest data - and it doesn't. I don't know what that function is exactly doing before it goes to the ajax function in tree configuration? At the moment it freezing page and do some strange stuff before it goes to the ajax. Any ideas how to help me?
Best regards,
Mario

When you refresh a node all its children are redrawn (if visible), this is probably what hangs your browser but I can not help you further without a demo.


AMR Panel Summary - blank for both icons

this may be due to the data inconsistency. cannot reproduce after Maulik's clean up.


Negative pending_duration, total_duration, and index in RCalendar. _find_time_completion for BPIC15_1

RCalendar. _find_time_completion fails in this test case, https://github.com/AutomatedProcessImprovement/pix-framework/blob/bpic15/tests/pix_framework/calendar/test_resource_calendar.py#L385-L395, by having negative pending_duration, total_duration, and index.
The new test case is in the bpic15 branch only.
@orlenyslp could you please take a look?

I already fixed the bug and pushed the update to the repository. The problem was in the function "generate_sample" in the "distribution" file, which generated a negative number in some cases for some distributions. I added the extra validation, so if the value is negative, the mean value is returned instead, or (max-min) / 2, or 0, depending on whether the corresponding attributes are valid. See the "_replace_negative_value" function on lines 106-113 and the validation on lines 102-103.


[#151801883] Remove Tim from admin users and merge keys.

Tim has left the team... 😿
How to review

Code review
Verify that the key being removed is indeed Tim's

Who can review
Not me.

Thats my key, looks good to merge 😢

Goodbye Tim. You are and will be missed!


Windows Service topic enhancements

Fixes #10836

Call out use of admin command shell when running commands.
Explicitly grant Log on as a service privilege to the user account.
Call out MSA as an alternative approach with AD. Confirm that I chose a good link for that scenario.
Call out default password expiry of six weeks.

I'd call using an MSA as the recommended way

It never came up before for this topic. If that's what we're going to do, then I'll open a new issue. Since this PR fixes a known 🐞 WRT Log on as a service, I recommend we go ahead and get this in now.
Who will make the call on this going with an MSA-based approach?
If we do, my very brief look seemed to indicate that Win10 needs some kind of install (MMC bits?) or something ... is that correct? If so, the push-back would be that the topic should maintain its current approach for Win10 and add a whole section for MSA. However if Win10 is good-to-go with MSA OOB, then sure, we could drop the current approach in favor of MSA. Either way tho, engineering should make the call on exactly what to cover ... not a small green dinosaur. :smile:

Agreed. Let's get this in first.
I'm ambivalent on the MSA issue and willing to let that slide as it's not that important.

@blowdart

@blowdart Yes, that was the original ask on https://github.com/aspnet/Docs/issues/10833. I'll re-open that, but I can't do it in the near future. I have 3.0 breath'in down my neck.
😨 🔥 🐲

@Rick-Anderson


Popup with GridBox not work on IE and EDGE

Hi i try this code, but isnt work on ie and edge, its works perfectly on Firefox
example_its_works_on_firefox.txt
Any can help me, i can see on debug ui the divs and data corresponding on the grid.
Thanks a lot.

I use the demo for combinations, and prove with .load and both works perfect. I will close.


fix bip109 minimum version criteria

Proposed fix for incorrect bip109 tallying in getblockchaininfo RPC.

added fixes from previous review comments:

use testnet
introduce a min_chain_len for test which does not need full window
fix obsolete comments / dead code
remove obsolete case #5a which was a dup of #2, rename #5b to #5

Great fix, thanks!


doc: release notes: Add board related release notes

Added details on new ARM boards, removal of panther board support on
x86 and arc, and dts.fixup changes.
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

Codecov Report

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

@@            Coverage Diff            @@
##           master   #6484      +/-   ##
=========================================
+ Coverage    53.2%   53.2%   +<.01%
=========================================
  Files         436     436
  Lines       41353   41353
  Branches     7937    7937
=========================================
+ Hits        22001   22002       +1
+ Misses      16128   16127       -1
  Partials     3224    3224

Impacted Files
Coverage Δ

kernel/posix/pthread.c
63% <0%> (+0.5%)
:arrow_up:

Continue to review full report at Codecov.

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


Redesign landing page

Added About page
Added Contact page
Updated Home page
Fixes #70

Also try to reduce the text size for smaller devices as it is same for every breakpoints.

Hey @kauxp, i have reviewed the code, done the changes as mentioned and learn along the way.

Hey @kauxp, what's the progress?

I am actively working on it.

Please review the changes.

Hey @kauxp, when i am running the application, its giving me error:

This is because the files are not present where you importing.

Fix this.

The above issue is in almost every page. Fix it asap and test it before pushing it.

I have pushed the changes.

When running the application it showing this issue as its missing page.ts in app directory. Also there are other issues also.

Hey @kauxp, I am merging this PR as i already given a lot time on this. I don't want to extend this PR it already taken more than a month for a UI. Try to work on your skills.

@kauxp also i have added necessary labels so that you can get points.


Add option to disable input

Hi, thank you for great package!
It would be great, if component gave option to disable inputs via prop. I am new to contributing to open source, but will try to help you out!

Hi @amazzat, I just added the option in version 3.1.1


image_picker and WRITE_EXTERNAL_STORAGE

Hi, I work for a bank and the security doesn't allow the app to use the WRITE_EXTERNAL_STORAGE and READ_EXTERNAL_STORAGE.
I realized that this permission was added to the manifest of my app.
Is there a way to avoid this permission using the image_picker plugin?

Hi @rlecheta,
What api level does your app target ?
Per the plugin's official documentation, for api > 29, no configuration is required and for api <= 29, there's a flag android:requestLegacyExternalStorage="true".
If you are on api <=29, you may try to set above flag to false and see if you see any issues while using the plugin.

Hi, with this flag:
android:requestLegacyExternalStorage="false"
My build never completes, it complains something about the cloud_firestore plugin:
Launching lib/main.dart on Android SDK built for x86 in debug mode...
Running Gradle task 'assembleDebug'...
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:processDebugResources'.

A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
Android resource linking failed
android/app/src/main/AndroidManifest.xml:14:5-57:19: AAPT: error: attribute android:requestLegacyExternalStorage not found.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 11s
The built failed likely due to AndroidX incompatibilities in a plugin. The tool is about to try using Jetfier to solve the incompatibility.
Running Gradle task 'assembleAarRelease'...
Building plugin flutter_money_formatter...
Running Gradle task 'assembleAarRelease'...
✓ Built build/app/outputs/repo.
Building plugin cloud_firestore...
Exception: The plugin cloud_firestore could not be built due to the issue above.
In my build.gradle I have:
minSdkVersion 21
targetSdkVersion 29

Hi, with this flag:
android:requestLegacyExternalStorage="false"
My build never completes, it complains something about the cloud_firestore plugin:
Launching lib/main.dart on Android SDK built for x86 in debug mode...
Running Gradle task 'assembleDebug'...
FAILURE: Build failed with an exception.
What went wrong:
Execution failed for task ':app:processDebugResources'.
A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
Android resource linking failed
android/app/src/main/AndroidManifest.xml:14:5-57:19: AAPT: error: attribute android:requestLegacyExternalStorage not found.
Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
Get more help at https://help.gradle.org
BUILD FAILED in 11s
The built failed likely due to AndroidX incompatibilities in a plugin. The tool is about to try using Jetfier to solve the incompatibility.
Running Gradle task 'assembleAarRelease'...
Building plugin flutter_money_formatter...
Running Gradle task 'assembleAarRelease'...
✓ Built build/app/outputs/repo.
Building plugin cloud_firestore...
Exception: The plugin cloud_firestore could not be built due to the issue above.
In my build.gradle I have:
minSdkVersion 21
targetSdkVersion 29

Hi @rlecheta @rlechetaudemy with WRITE_EXTERNAL_STORAGE and READ_EXTERNAL_STORAGE entries intact in manifest file, do you get any error while building or does it prohibit to use image_picker plugin ?

Hi, it throws the same exception, with or without the WRITE/READ permissions. Now my manifest is like this and I got the same error:

@rlecheta,
Usually if you have minSdkVersion 21 and targetSdkVersion 29, then you won't explicitly need to specify the permissions in manifest.
I am on same settings and tried the official image_picker plugin example on latest Stable (1.20.1). When I try to access gallery or camera, it by default asks you for the permission as below:

Hi @darshankawar , sure it works like you explained. But please, read again what I explain in the first post.
The problem is that I didn't put the WRITE/READ permission in my Manifest, but during the manifest merge, the plugin put it there. If you Analyse your apk, you are going to see both permissions there, even if you don't wanna it.
My app doesn't pass the security requirements of my company because that.
It's very important that Flutter plugins doesn't put any unnecessary permissions on the Manifest if they are not necessary.
And finally, we are talking about some official plugin.

This will probably need for analysis, so keeping this issue open.

Hi @rlecheta
For now, only way to avoid this using image_picker locally in your project and removing the permission line
I don't think write permission would be removed from the package itself
Closing as there is an easy solution to this. If you disagree, please write in the comments and I will reopen it.
Thank you


Autoload

Fixes #354

I would generate a plugin.js file like that with the init command instead of adding dir plugin path support.
'use strict'

const path = require('path')
const autoload = require('@fastify/autoload')

module.exports = async function (app) {
  app.register(autoload, { dir: path.join(__dirname, 'plugins') })
  app.register(autoload, { dir: path.join(__dirname, 'routes') })
}

It seems useful to me to have a few folders for plugins. Like plugins and routes.

I plan to add support for an array of files and folders too. Folks are really confused by having to register a separate plugin when using Fastify. I want to avoid it in Platformatic (and be more opinionated).

It's more flexible. I can pass some options, set up a prefix for the whole folder, etc.

The options will be passed through to autoload, so it has all the options autoload has.

If the array is supported, then ok.

This is ready for review now. THe PR description has been updated.


Update singletons.md

fixing typo

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @jamesmunns (or someone else) soon.
Please see the contribution instructions for more information.


Formally describe bundled and triggered changes (workflows)

KGCL has the concept of

kgcl:ComplexChange
kgcl:SimpleChange

Simple changes are atomic at the level of KGCL. E.g. kgcl:NodeMove could be broken down into a removed edge and add edge. However, NodeMove is still considered atomic/simple (it just so happens that there are potential rewrite rules for some change types). And of course at the RDF level this may involve many triples but that doesn't concern us here
Currently some KGCL implementations will trigger multiple changes from a single change. For example, in oak running apply on obsoletion will trigger removal of logical axioms and renaming as per (not particularly formally represented) OBO best practice, and similar to existing 'workflows' in Protege. It seems reasonable that we should try and formally represent this common workflow in KGCL.
In fact for obsoletions, the kgcl:Configuration class allows for the specification of an obsoletion policy, implemented as ObsoletionPolicyEnum - but there is no formal connection between the PVs and the logic.
Other ontologies may have more bespoke rules. See for example https://wiki.geneontology.org/Ontology_meeting_2024-04-08#Triggering_multiple_actions???
I don't think it makes sense to represent specific ontology rules in KGCL, but we may want some kind of mechanism for representing rules in general.
Currently the semantics of things like diff are not well defined here. I think when doing a diff we want a way to optionally "roll up" triggered changes. E.g. the renaming of "foo" to "obsolete foo" is not interesting in the way other renames are, same with "edge deletions". Currently oak hardwires a rule that these are ignored in the diff but this is not very satisfactory.
I propose we include a slot "triggers" or "triggered by" that could be used to better represent at the instance level triggered changes. This allows for a separation of concerns. diff calculation could infer these given two ontologies and an obsoletion policy (for example). Diff reporting could simply report these according to user preference.
We may also want to consider a rule language. e.g. to say "if change of type X happens, and the instance x has value v, then trigger change of type Y...". There are many interesting directions to go here but interesting is not necessarily good, we want this to be easy to implement in both oak and java-kgcl. Something like SPARQL construct would be easy to implement but would we run into expressivity issues?

I am mildly reticent to the idea of having configurable rules describing how exactly changes should be performed. I would much rather stay at the level of having configuration options, with the meaning of each option being appropriately described in the spec and hardcoded by the implementations.
That is, for all changes that may be performed in slightly different ways (for example obsoletion, where some ontologies may want to add an "obsolete" label and some may not, some ontologies may want to remove referencing axioms and some others may prefer to keep them, etc.), we gather the different possible behaviours, and we add as many configuration options in kgcl:Configuration to represent all those behaviours.

but there is no formal connection between the PVs and the logic.

I don’t think there needs to be a formal connection. As long as the PV is described clearly enough in plain English.

We may also want to consider a rule language […] we want this to be easy to implement in both oak and java-kgcl. Something like SPARQL construct would be easy to implement

I don’t know about OAK, but a SPARQL-based rule language would not be easy to implement in KGCL-Java. KGCL-Java uses the OWL API as backend, and AFAIK there is no “easy” way to execute SPARQL query against the OWL API – for example, the way ROBOT does it is basically by dumping the entire OWL ontology as a Turtle file, loading it into Jena, running the SPARQL query, dumping the updated graph as a Turtle file, and reloading it into the OWL API… It works, sure, but it’s pretty ugly and I will certainly not replicate that in KGCL-Java.

Thanks! On reflection I agree with all this
On Tue, Apr 2, 2024 at 12:34 PM Damien Goutte-Gattat <
@.***> wrote:

I am mildly reticent to the idea of having configurable rules describing
how exactly changes should be performed. I would much rather stay at the
level of having configuration options, with the meaning of each option
being appropriately described in the spec and hardcoded by the
implementations.
That is, for all changes that may be performed in slightly different ways
(for example obsoletion, where some ontologies may want to add an
"obsolete" label and some may not, some ontologies may want to remove
referencing axioms and some others may prefer to keep them, etc.), we
gather the different possible behaviours, and we add as many configuration
options in kgcl:Configuration to represent all those behaviours.
but there is no formal connection between the PVs and the logic.
I don’t think there needs to be a formal connection. As long as the PV is
described clearly enough in plain English.
We may also want to consider a rule language […] we want this to be easy
to implement in both oak and java-kgcl. Something like SPARQL construct
would be easy to implement
I don’t know about OAK, but a SPARQL-based rule language would not be
easy to implement in KGCL-Java. KGCL-Java uses the OWL API as backend, and
AFAIK there is no “easy” way to execute SPARQL query against the OWL API –
for example, the way ROBOT does it is basically by dumping the entire OWL
ontology as a Turtle file, loading it into Jena, running the SPARQL query,
dumping the updated graph as a Turtle file, and reloading it into the OWL
API… It works, sure, but it’s pretty ugly and I will certainly not
replicate that in KGCL-Java.
—
Reply to this email directly, view it on GitHub
https://github.com/INCATools/kgcl/issues/70#issuecomment-2032533376, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAMMOOZPOJFQUUCVPHA7ILY3LMZXAVCNFSM6AAAAABFLHWJU2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZSGUZTGMZXGY
.
You are receiving this because you authored the thread.Message ID:
@.***>


fix Disable revoke 'admin' from 'admin'

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

If we revoke 'admin' from 'admin' before this change, what will happen?

run buildall