12/7/2021 Publish

Docs Build status updates of commit d876e37:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/latest/arm-compute-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/arm-features-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/arm-links-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/arm-locks-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/arm-managedapplications-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/arm-network-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/arm-policy-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/arm-resources-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/arm-sql-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/arm-storage-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/core-client-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/core-lro-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/preview/arm-devtestlabs-readme.md
:warning:Warning
View (azure-node-preview)
Details

docs-ref-services/preview/arm-sqlvirtualmachine-readme.md
:warning:Warning
View (azure-node-preview)
Details

docs-ref-services/preview/storage-blob-readme.md
:warning:Warning
View (azure-node-preview)
Details

docs-ref-services/preview/storage-file-share-readme.md
:warning:Warning
View (azure-node-preview)
Details

ci-configs/packages-latest.json
:white_check_mark:Succeeded

ci-configs/packages-preview.json
:white_check_mark:Succeeded

metadata/latest/azure-arm-compute.json
:white_check_mark:Succeeded

metadata/latest/azure-arm-features.json
:white_check_mark:Succeeded

metadata/latest/azure-arm-links.json
:white_check_mark:Succeeded

metadata/latest/azure-arm-locks.json
:white_check_mark:Succeeded

metadata/latest/azure-arm-managedapplications.json
:white_check_mark:Succeeded

metadata/latest/azure-arm-network.json
:white_check_mark:Succeeded

metadata/latest/azure-arm-policy.json
:white_check_mark:Succeeded

metadata/latest/azure-arm-resources.json
:white_check_mark:Succeeded

metadata/latest/azure-arm-sql.json
:white_check_mark:Succeeded

metadata/latest/azure-arm-storage.json
:white_check_mark:Succeeded

metadata/latest/azure-core-client.json
:white_check_mark:Succeeded

metadata/latest/azure-core-lro.json
:white_check_mark:Succeeded

metadata/preview/azure-arm-devtestlabs.json
:white_check_mark:Succeeded

metadata/preview/azure-arm-sqlvirtualmachine.json
:white_check_mark:Succeeded

metadata/preview/azure-storage-blob.json
:white_check_mark:Succeeded

metadata/preview/azure-storage-file-share.json
:white_check_mark:Succeeded

docs-ref-services/latest/arm-compute-readme.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'compute'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 22, Column 1: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/arm-compute' will be broken in isolated environments. Replace with a relative link.
Line 60, Column 76: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/arm-features-readme.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'features'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 22, Column 1: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/arm-features' will be broken in isolated environments. Replace with a relative link.
Line 60, Column 76: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/arm-links-readme.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'links'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 22, Column 1: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/arm-links' will be broken in isolated environments. Replace with a relative link.
Line 60, Column 76: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/arm-locks-readme.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'locks'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 22, Column 1: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/arm-locks' will be broken in isolated environments. Replace with a relative link.
Line 60, Column 76: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/arm-managedapplications-readme.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'managedapplications'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 22, Column 1: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/arm-managedapplications' will be broken in isolated environments. Replace with a relative link.
Line 60, Column 76: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/arm-network-readme.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'virtualnetwork'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 23, Column 1: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/arm-network' will be broken in isolated environments. Replace with a relative link.
Line 61, Column 76: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/arm-policy-readme.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'policy'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 22, Column 1: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/arm-policy' will be broken in isolated environments. Replace with a relative link.
Line 60, Column 76: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/arm-resources-readme.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'resources'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 23, Column 1: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/arm-resources' will be broken in isolated environments. Replace with a relative link.
Line 61, Column 76: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/arm-sql-readme.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'sql'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 22, Column 1: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/arm-sql' will be broken in isolated environments. Replace with a relative link.
Line 60, Column 76: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/arm-storage-readme.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 23, Column 1: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/arm-storage' will be broken in isolated environments. Replace with a relative link.
Line 61, Column 76: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/core-client-readme.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'core'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 5, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'magpint' is not a valid Microsoft alias.

docs-ref-services/latest/core-lro-readme.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'core'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 5, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'xirzec' is not a valid Microsoft alias.
Line 26, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/core-lro' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/preview/arm-devtestlabs-readme.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'devtestlabs'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 23, Column 1: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/arm-devtestlabs?view=azure-node-preview' will be broken in isolated environments. Replace with a relative link.
Line 23, Column 1: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/javascript/api/@azure/arm-devtestlabs?view=azure-node-preview. Otherwise, remove the view parameter.
Line 61, Column 76: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/preview/arm-sqlvirtualmachine-readme.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'sqlvirtualmachine'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 23, Column 1: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/arm-sqlvirtualmachine?view=azure-node-preview' will be broken in isolated environments. Replace with a relative link.
Line 23, Column 1: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/javascript/api/@azure/arm-sqlvirtualmachine?view=azure-node-preview. Otherwise, remove the view parameter.
Line 61, Column 76: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/preview/storage-blob-readme.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 5, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'XiaoningLiu' is not a valid Microsoft alias.
Line 32, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/storage-blob' will be broken in isolated environments. Replace with a relative link.
Line 33, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/storage/blobs/storage-blobs-overview' will be broken in isolated environments. Replace with a relative link.
Line 35, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/rest/api/storageservices/blob-service-rest-api' will be broken in isolated environments. Replace with a relative link.
Line 49, Column 5: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/storage/blobs/storage-quickstart-blobs-portal' will be broken in isolated environments. Replace with a relative link.
Line 118, Column 20: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/rest/api/storageservices/cross-origin-resource-sharing--cors--support-for-the-azure-storage-services' will be broken in isolated environments. Replace with a relative link.
Line 178, Column 114: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/storage/common/storage-auth-aad-app' will be broken in isolated environments. Replace with a relative link.
Line 182, Column 85: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/active-directory/develop/quickstart-register-app' will be broken in isolated environments. Replace with a relative link.
Line 188, Column 39: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/storage/common/storage-auth-aad-rbac-portal' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/preview/storage-file-share-readme.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 5, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'XiaoningLiu' is not a valid Microsoft alias.
Line 35, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/storage-file-share' will be broken in isolated environments. Replace with a relative link.
Line 36, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/storage/files/storage-files-introduction' will be broken in isolated environments. Replace with a relative link.
Line 38, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/rest/api/storageservices/file-service-rest-api' will be broken in isolated environments. Replace with a relative link.
Line 52, Column 5: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/storage/common/storage-account-create' will be broken in isolated environments. Replace with a relative link.
Line 115, Column 20: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/rest/api/storageservices/cross-origin-resource-sharing--cors--support-for-the-azure-storage-services' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


task_swap_mach_voucher returned 46: (os/kern) service not supported

Cant Jailbreak iPhone 7 running 12.1.2
diagnostics.plist.zip

I see you're running a beta firmware ( first beta of 12.1.2 ).
That might be the issue.
It definitely looks like it which is strange.

Umm are you sure? I’m running the normal public version of iOS 12.1.2, normal OTA update without any developer profiles/certificates

@batboy710 what build number is shown on your settings?
voucher_swap reports it as 16D5024a, which is the first public beta of 12.1.2, not the final release afaik?

The build number is in fact 16D5024a but I don’t recall participating in the public beta testing of iOS. I have no idea how I somehow have the beta version.

Is there a fix?

I tried contacting pwn but he didn’t respond on Twitter

That's okay, you're not at fault for the OS not supporting your version.
I'm not even sure if that's the reason but it's pointing to it!
For now, and if you have blobs, I'd recommend downgrading to 12.1.1 beta 3 which we know it's supported and then going back to your version with blobs.
Another question, upon unlocking your phone, do you receive a " a new beta update is available bla bla" ?
Pwn is really busy and he's being spammed a lot. He really needs the help :P

Nope, no pop ups regarding a beta version. I don’t have. Blobs saved and I really don’t want to be running a beta version on my daily driver.

@batboy710 that's great to hear. I believe it's because of the OTA software then(why it has such build number - I don't know). This has been the case for past jailbreaks like evasi0n. I recommend you downgrading to 12.1.1 b3, setting nonce and future restoring back to full 12.1.2 if you wish so.

I can’t future restore since I don’t have my blobs saved..

Oh. If you reallyyy need to be jailbroken then, I recommend downgrading to 12.1.1 b3 then.
If you don't, I'd stay for the time being. We don't have enough reports to confirm it's because of the OTA. More diagnostics are needed.

Sh*t..

Oh. If you reallyyy need to be jailbroken then, I recommend downgrading to 12.1.1 b3 then. ...

@clarityzzz @batboy710 that will work 100%
Sent with GitHawk

@clarityzzz @tsxmichael @batboy710  i just found out i run 16D5024a and i found it out after apple stopt sining beta 3. Wath can i do now. I must have this jailbreak. I have no blobs. For logs and more #595

Duplicate of #407 , so closing.


Remove dot() function

Tests performed on 64-bit Windows Intel Haswell CPU with Julia v0.3.7 using OpenBLAS v0.2.14 extracted from Julia v0.4 nightly:
blas_set_num_threads(CPU_CORES)
const v=ones(Float64,100000)
@time for k=1:1000000;s=dot(v,v);end
# 23.7 seconds, single-threaded

using Yeppp
const v=ones(Float64,100000)
@time for k=1:1000000;s=Yeppp.dot(v,v);end
# 22.4 seconds, single-threaded

Test performed on the same PC with MKL BLAS on Python:
import numpy as np
from scipy.linalg.blas import ddot
from timeit import default_timer as timer
v = np.ones(100000)
start = timer()
for k in range(1000000):
    s = ddot(v,v)
exec_time=(timer() - start)
print
print("Execution took", str(round(exec_time, 3)), "seconds")
# 7.5 seconds, multi-threaded

Thus, Yeppp is 5% faster than OpenBLAS v0.2.14 and 300% slower than MKL BLAS.  I would rather not keep Yeppp's dot() function as a negligible work-around for an OpenBLAS v0.2.14 problem.
I propose that we remove the dot() function.  To get Julia to match Python's speed, I propose instead:
a) Ship Julia with MKL, see https://github.com/JuliaLang/julia/issues/10969
b) Work with the OpenBLAS project to correct the dot product performance problems.
The develop branch of OpenBLAS may already work.  See the commit from April 24th entitled "bugfixes: replaced int with BLASLONG"
I am concerned that users of Yeppp.dot() will miss the 300% speed improvement coming in the base.  Better to remove it before Yeppp becomes popular in Julia.

That is very strange. In my tests Yeppp! dot product outperformed MKL. I'll look into into, probably a Windows-specific problem.

I don't see anything suspicious in the assembly code. Probably, the result is due to passing the same vector v for both arguments. Maybe MKL has an optimization for this specific case (Yeppp! has this optimization too, but as a separate SumSquares function).

Hold on, isn't the MKL number multi-threaded?

@Keno probably. There are separate .so libraries for multithreaded and non-multithreaded versions; but I am not sure which is used by Julia.

@Maratyszcza , I don't understand your last comment.  Since I'm using Windows, I'm using yeppp.dll, not a .so library.  Since Julia doesn't presently use BinDeps, each user must copy the appropriate library from the yeppp-1.0.0.zip file linked in README.md.  Since I am using 64-bit Windows OS, I chose yeppp.dll in the binaries\windows\amd64 folder of yeppp-1.0.0.zip.  I see no options for multithreaded vs. non-multithreaded versions.

@hiccup7 This comment is about MKL, Yeppp! is always single-threaded.

@Maratyszcza , thanks for the clarification.
@Keno , My CPU meter showed that MKL is multi-threaded with Python.  I included this aspect in the comment for each test in the first post.  The OpenBLAS develop branch is already multi-threaded for dot products of reals, or at least it will be when it meets or exceeds MKL's performance.

I think we can leave dot in there. It is in the Yeppp namespace anyways, and it is handy to have when not using MKL or some other BLAS library.

When Julia is built without any BLAS library, which library is used for dot products?  If Yeppp provides a faster dot product than the existing non-BLAS method, then the base could use the Yeppp function under the hood.
My intention is that the base provides the fastest library for dot(), regardless of which or any BLAS library is used.  This will make Julia code more portable.  If Yeppp's dot() is desired for non-BLAS builds, then we could at least avoid exporting the dot() method from the Yeppp module so that novice users will use the faster base dot() method instead.

Currently, there is no way to build Julia without a BLAS library.

for dot(x, y) function, Is possible to test whether arrays x and y shares the same pointer and then choose which function in Yeppp! to be used?
dot(x, x) and x = y; dot(x, y) should have the same performance in Julia since x and y are sharing the same data.


Don't try to initialize object with parameters

Solves:
File ".../lib/python3.4/site-packages/django/contrib/staticfiles/finders.py", line 140, in __init__
    super(AppDirectoriesFinder, self).__init__(*args, **kwargs)
TypeError: object.__init__() takes no parameters

A test and a Trac ticket are also  required for bug fixes, thanks!

Please follow up as indicated above, thanks!


Only primitive boolean alowed

FloodGate accepts only primitive boolean. How to fors it accept boolean from another nodes?

Note: The logic flow is parsed during the queuing stage, not the execution stage. As a result, the boolean value has to be already determined when you press Queue Prompt, such as from the toggle or a primitive node. If you use a node that outputs a boolean during execution, this will not work.

You can't.


Nft, Staking, defi systems and features should be added

Clear and concise description of the problem
It should have an easy mobile interface, nft, etf, defi mining feature should be introduced.  Also, transfer feature from bank to wallet should be added.
Suggested solution
It should have an easy mobile interface, nft, etf, defi mining feature should be introduced.  Also, transfer feature from bank to wallet should be added.
Alternative
It should have an easy mobile interface, nft, etf, defi mining feature should be introduced.  Also, transfer feature from bank to wallet should be added.
Additional context
It should have an easy mobile interface, nft, etf, defi mining feature should be introduced.  Also, transfer feature from bank to wallet should be added.
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

The innovation of the IBAX blockchain network is creation of the metaverse world. It is committed to mapping the real society to the metaverse world beyond the real-world nodes and space constraints. To maintain the long-term development of the metaverse, IBAX needs a network where a huge number of creators build a metaverse together. Therefore, 18.75% of all coins is reserved to reward creators of outstanding NFTs for the metaverse. An address of each creator may only own up to 10 NFTs. Each NFT has the Power of 1 to 100. The higher this value, the higher the possibility to get the metaverse rewards.
There are three ways to get NFTs:

New accounts can get a one-time metaverse bonus. Users who deposit coins to the account and lock them for staking for 1 month instantly get one freshly minted metaverse NFT.
Users can fuse two NFTs in their account into one new NFT. The resulting Power of the new NFT may be either greater or smaller than the sum of Power values of the two original NFTs.
Users can go to a decentralized NFT trading platform to buy NFTs with a high Power value fused by other users and transfer them to their account. The launch of IBAX mainnet will enable the reward mechanism for NFT creators. Its aim is to promote the metaverse development and reach the mature metaverse world as quickly as possible.

Rules:

Users can create an account in IBAX Network free of charge. Each account gets one NFT of 1.00 Power.
Users who stake 10,000 IBXC for 30 days can join IBXC mining using the NFT of 1.00 Power within these 30 days.
After 30 days of staking, the initial NFT of 1.00 Power can be transferred/exchanged (i.e., it becomes a free NFT).
Two free NFTs can be fused on IBAX Network according to the fusing rules to create a new free NFT with a different Power value.
One account can own up to 10 NFTs.

DEFI, GAMEFI and other features would be new ECOsystems of IBAX Network.


Missing core dependencies: msgpack, requests and pyyaml?

Report
After running pip install flaml==1.1.1 into a clean Conda Python 3.10 environment (no ray) and executing some tune.run code, I get the following errors:
No module named requests

No module named pyyaml

Resolution
pip install pyyaml requests seems to fix the problems above.

The log suggests that python 3.9 is in use and ray is installed, which contradicts the environment mentioned in the beginning.

I'll make an MRE for this asap.

Here you go. I ran this example on WSL2 (Ubuntu 20.04)
MRE
# environment.yml
name: flaml
dependencies:
  - python=3.9
  - pip
  - pip:
    - flaml

# bug.py
from flaml import tune, CFO
from flaml.tune.sample import Domain

search_space: Domain = {"i": tune.randint(1, 10)}

def custom_evaluate(params):
    i = params["i"]
    print(type(i))
    j = i + 1
    return {"score": j}

search_kwargs = {
    "space": search_space,
    "metric": "score",
    "mode": "min",
    "time_budget_s": 10,
}
tune.run(
    custom_evaluate,
        search_alg=CFO(**search_kwargs),
        use_ray=False
)

conda env create -f environment.yml
conda activate flaml
python bug.py

Resolution
pip install msgpack requests pyyaml

Screenshots

Another update: this bug doesn't seem to occur for Python 3.10.9
name: flaml
dependencies:
  - python=3.10
  - pip
  - pip:
    - flaml==1.1.1

If you look at the trace, the error happened inside python3.9/site-packages/ray/init.py. Even though conda list ray shows no ray, ray is still installed. So we can nail the issue to that.

This is very strange strange because install_requires https://github.com/microsoft/FLAML/blob/dbd48c555fcfea4a92753bfc6d5f755222b65107/setup.py#L16 does not include ray.
Any ideas on what's going on? I am available to help with direction.

ray is installed under ".local/lib/python3.9", not the conda environment.

No issues after removed existing ray installations in every path and I did a clean reinstall. Thanks for the help!


About train encoder ?

Is it possible to provide the convert_weight code? It does not appear in Seonghyeon Kim's Pytorch Implementation of StyleGAN2.
For example,  g_args = g_ckpt['args'], g_ckpt["d_optim"].

Hi, Seonghyeon Kim's pytorch implementation actually has the convert_weight code here.
For the encoder, I haven't tried converting the weights yet.
I'm still testing the code and planning to release the trained encoder weights later.

Thanks for your reply!  But I have a question, the convert_weight code in Seonghyeon Kim's PyTorch implementation has no save "args" and "d_optim", would you mind tell me how to save the "args" and "d_optim" parameters from Tensorflow to Pytorch?

I guess you can simply pass the "args" as ckpt["args"] = tf_args. The parameters beta1, beta2, lr and previous states need to be loaded from the tf model file to convert "d_optim".


Message popups may be too short

See if its possible to extend them a little

These popups are controlled by a DoTween animation. It may be better to hook into an "OK" popup somehow.

Implemented in 4619a3156e2690a5fa72fb45535cd48624b050d3.


Develop

Motivation
close or resolve or fix(fixed, fixes) #{issue number}
Key Changes
Describe the major changes in your work

Change 1

Description

Change 2

Description

To Reviewers
Leave message for reviewers who will check this Pull request

launch screen, onboarding, splash, login view 추가 확인했습니다!
고생 많으셨습니다! 👍


feat: add server call stream observer for rx

This change adds an RxJava adapter to support converting a reactive construct (Observable, Single, Maybe, Completable - didn't add flowable support unless needed) into a GRPC response. This pattern:

Promotes cleaner code, as an observer no longer needs to be plumbed down throw the call stack
Supports either synchronous or async implementations (like any reactive code)
Supports cancellation for ongoing requests

Also bumped testing libraries, pinned to java 11 (most other repos have already done that) and updated to latest grpc.


Bluetooth device keeps disconnecting after about 15 seconds

The app notices the disconnect only after about 20 seconds. After that it automatically reconnects.

It was caused by a weak power output from the Arduino


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.3 to before v5.13.4",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=13ff178ccd6d3b8074c542a911300b79c4eec255",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d6e76469157d8f240e5dec6f8411aa8d306b1126"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "13ff178ccd6d3b8074c542a911300b79c4eec255",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "d6e76469157d8f240e5dec6f8411aa8d306b1126",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "fbmem: Do not delete the mode that is still in use\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.13.4 by commit d6e76469157d8f240e5dec6f8411aa8d306b1126, it was introduced in version v5.3 by commit 13ff178ccd6d3b8074c542a911300b79c4eec255. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001211


Question about setting the environment

Hi!
I ran the command pip install --editable ., however as a response I got some problems, particularly related to the torch version (below the full message that I got). Is there any suggestion on how I might solve this issue?
Building wheels for collected packages: torch-scatter
Building wheel for torch-scatter (setup.py) ... error
ERROR: Command errored out with exit status 1:
command: /home/alabate/transition-amr-parser/venv/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-zovxf2mm/torch-scatter/setup.py'"'"'; file='"'"'/tmp/pip-install-zovxf2mm/torch-scatter/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-9szx92a5
cwd: /tmp/pip-install-zovxf2mm/torch-scatter/
Complete output (27 lines):
running bdist_wheel
running build
running build_py
creating build
creating build/lib.linux-x86_64-3.8
creating build/lib.linux-x86_64-3.8/torch_scatter
copying torch_scatter/init.py -> build/lib.linux-x86_64-3.8/torch_scatter
copying torch_scatter/segment_csr.py -> build/lib.linux-x86_64-3.8/torch_scatter
copying torch_scatter/segment_coo.py -> build/lib.linux-x86_64-3.8/torch_scatter
copying torch_scatter/scatter.py -> build/lib.linux-x86_64-3.8/torch_scatter
copying torch_scatter/placeholder.py -> build/lib.linux-x86_64-3.8/torch_scatter
copying torch_scatter/utils.py -> build/lib.linux-x86_64-3.8/torch_scatter
creating build/lib.linux-x86_64-3.8/torch_scatter/composite
copying torch_scatter/composite/init.py -> build/lib.linux-x86_64-3.8/torch_scatter/composite
copying torch_scatter/composite/logsumexp.py -> build/lib.linux-x86_64-3.8/torch_scatter/composite
copying torch_scatter/composite/std.py -> build/lib.linux-x86_64-3.8/torch_scatter/composite
copying torch_scatter/composite/softmax.py -> build/lib.linux-x86_64-3.8/torch_scatter/composite
running build_ext
building 'torch_scatter._version_cpu' extension
creating build/temp.linux-x86_64-3.8
creating build/temp.linux-x86_64-3.8/csrc
x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Icsrc -I/home/alabate/transition-amr-parser/venv/lib/python3.8/site-packages/torch/include -I/home/alabate/transition-amr-parser/venv/lib/python3.8/site-packages/torch/include/torch/csrc/api/include -I/home/alabate/transition-amr-parser/venv/lib/python3.8/site-packages/torch/include/TH -I/home/alabate/transition-amr-parser/venv/lib/python3.8/site-packages/torch/include/THC -I/home/alabate/transition-amr-parser/venv/include -I/usr/include/python3.8 -c csrc/version.cpp -o build/temp.linux-x86_64-3.8/csrc/version.o -O2 -DAT_PARALLEL_OPENMP -fopenmp -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE="_gcc" -DPYBIND11_STDLIB="_libstdcpp" -DPYBIND11_BUILD_ABI="_cxxabi1011" -DTORCH_EXTENSION_NAME=_version_cpu -D_GLIBCXX_USE_CXX11_ABI=0 -std=c++14
csrc/version.cpp:1:10: fatal error: Python.h: File or directory nonexistent
1 | #include <Python.h>
|          ^~~~~~~~~~
compilation terminated.
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
ERROR: Failed building wheel for torch-scatter
Running setup.py clean for torch-scatter
Failed to build torch-scatter
ERROR: torchvision 0.14.1 has requirement torch==1.13.1, but you'll have torch 1.10.1 which is incompatible.
Thanks!
Anton

ERROR: torchvision 0.14.1 has requirement torch==1.13.1, but you'll have torch 1.10.1 which is incompatible.

this seems unrelated to this repository, the torch vision version you are using is not compatible.


Resource view, feature request

The component is awesome - the only thing missing for me is a resource view.
It is often the case to add resources to a calendar event: Eg. a car vendor could add a sales agent and a car model to the event. Now it is easy enough to render the event contents with custom color and text, but events will still be mixed up in the Week/Day columns.
I would like a Week like view, but instead of the week days it would show resource names, displaying the resources' events in the respective columns.
The api/props can be very simple. I have the following props in mind:

resourceAccessor,
resourceAccessor= 'salesguy_id'
the list of resources,
resources= {  [{id: 1, name: 'John'}, {id:2, name: 'Linda'}]  }
a function to test membership,
resourceMembership = { (resource, event) => resource.id == event.salesguy_id  }
a renderable node as resource column headers,
resourceHeader= { (resource) => resource.name }
an option to show the resource view in the toolbar,
views= ['month', 'week', 'day', 'agenda', 'resource']
messages= { ...messages, resource: 'Sales agent view' }

Like this we could also easily switch between different resource categories - eg sales agents and available car models, calling that "Events by sales agent view, Events by available cars".
Any resource restriction rules are handled by the application, but the display can easily be handled by the calendar.
Interested to know what you think about it,
raf

Bonus points for also passing a resourceFlexAccessor as prop, that sets the relative width to all the other resource columns.
Resources can typically have a different "event-capacity", e.g. the short visitor tour can be booked by 5 guests per hour, while the long tour can only accommodate 2.
**resourceFlexAccessor**``` = { (resource) => { return resource.capacity > 4 ? .3 : .1; } }```

hey there,
Thanks for the thought out suggestion. To be honest the main reason there is no resource support, is because we haven't had a use for it, as such  I don't feel like I understand the use case enough to properly implement such a feature.
What I gather is that its a way of grouping everything into sort of sub-calendars? Your suggestion does seem simple enough as a layout, but would would be the date range for such a view? would you just lump all events per resource in the same column despite the date they occured? Or go with some thing like this which is a lot more complicated seeming :P

Hi,
First for the use case: The calendar itself is a resource view of our most valuable resource: time. This is perfect for individuals, but when a business wants to schedule events, it most often includes a list of all the needed resources to fulfill this events goals. For example

A hairdresser event may need (in addition to the customer name and the datetime) a certain stylist.
A car repair shop may need a mechanic and one of the lifting platforms.
A chiropractors office may need one of the treatment rooms to be available.

Now the most important quality of a resource in this regard is it's capacity. I want to visually see which stylist can handle a client at 13 o'clock (one stylist can handle one client at a time), which car mechanic can repair Mr Joneses car this afternoon (a car mechanic may be able to tend to 2 cars if one is running tests and the other is being inspected) and in which room I can treat poor Elliot tomorrow (number of concurrent treatments depends of course on the room).
The simplest way to see if a resource is being used is a column (or row), where only events using that resource are visible. (Of course there are always colors and icons to visually indicate another resource dimension, but they are less clear and get less effective when a lot of events clutter the view).
The simple, manual React way to construct HORIZONTAL and VERTICAL resource views for all date ranges (using the resource props nomenclature from the first post!):
let ResourceView = function(props) {
  let subcalendars = props.resources.map((resource) => {
   return (

{resource.name}

         <BigCalendar {{...props.calendarprops, events=events.filter((event) => resourceMembership(resource, event)}} />

)
  })
  return (

        {subcalendars}

   )
}

Obviously you would need to be smarter about left or top date/time sidebars and the resource titles, but I guess that approach could already be workable (not tried). An option to position them below each instead of next to each other would be a simple matter of css.
If needed, groups of resources can be obtained by permutating the resources and just chain their filters on available events. But that's something left to after the simple case.
Maybe by making date/time sidebars and column titles fully optional is a way to let developers build their own resource views as outlined?
raf
If you are using a calendar to schedule clients, then
Thanks for the thoughts and the link to the Kendo calendar which got me thinking, that things might not be that hard to do in React.
I feel that the resource view for all date ranges except the day view,
(eg Room 200 Bill, Room 200 Jill, Room 201 Francis, etc.)

hey thanks for the thorough posting.
I am open to a bunch of options here, I think its helpful to try and strike the right balance between flexible and not opinionated. I do like the simple approach of just combining a bunch of big calendars and link them together.
The other option is to build grouping into TimeGrid directly. Its not my favorite approach.
And perhaps in the middle is creating a new ResourceTimeGrid that reuses some of the TimeGrid components, or TimeGrid itself (if we allow disabling the side gutter). One of my original plans was to make views on the calendar plug-able, and to some extent they are, if you provide a keyed object with Component values to the views it will use the components and pass any props to it.
In any case its a bigish enhancement and I don't know quite when it would happen, but If you are willing to either try the first approach and reporting back what you found lacking in the API, or if you want to PR something I'd be more than happy to walk through stuff with you.

I can try to build a rough version following the first approach as outlined. Unfortunately I have very little time at the moment (maybe some more during Christmas holidays), so this could take some time.
I'd be happy to receive some pointers from you in case I get stuck. I haven't delved into the TimeGrid stuff all that much.
raf
raf

I'd find this very interesting too, its the only feature I really miss compared to fullcalendar. Any success on it @rafsoaken?

Sorry, in the end I did not have time to implement that feature myself.

 I will have to use fullcalendar then, since displaying resources in day/week/month views, and horizontal timelines is a must have as soon as you deal with more then 1 dimension (time vs time/room or time/person or time/object).
Don't get me wrong, react-big-calendar is superior and preferable to fullcalendar in a lot of aspects, but the views are a bit limited as is.

I don't know that RBC is superior to FC, its better suited for react, but FC got a lot more going for it :P also in full calendars case the resource views are a premium feature 💲

We need a ResourceView similar to TreeGrid, but instead of rendering a single DayColumn here, we render one for each resource.

I started working on this a few hours ago and TBH it wasnt as hard as I thought it was going to be (although @HriBB comment straight away pointed me in the right direction). I'll create a PR later on this week

@jquense Hey man, I'm a bit stuck trying to get this to work with the dragAndDrop addon. More specifically when dropping an event from Resource A into Resource B how can we expose the corresponding resource id that belongs to that dropped target in backgroundWrapper.js:118
AFAICT only the renderHeader will know about this and not the background cells, so I'm not entirely sure what's the best approach to take in this case.

it's hard to say without seeing any code on how you are implementing it, but I'd imagine the resource detail would be on the event object itself no?

@jquense nvm, I got it to work perfectly fine. It's just a bit complicated to get the resource view to play nicely when you have lots of them as the current layout shrinks cols in order to fit the parent element.

Ideally would be nice if day-slots have a min-width so that they dont shrink down that much, so that's what I'm currently fighting against atm :)
PS: I can share the code if anyone is interested but it's not super clean or PR ready yet, I'll definitely clean it and get it ready for review over the weekend if I have enough time

Looks great so far! How do week/month views look with the resource view?

@bkniffler This is just a separate view so it is not integrated in any way with the other ones. Internally it works exactly like the day view but instead shows extra columns for all different resources while keeping support for selection, dragndrop addon, and so on.

All right, this implementation makes sense. So we could have resourceDay/resourceWeek/resourceMonth views sometime. I'd love to see timeline views (horizontal view) in react-big-calendar, especially in conjunction with resource grouping, but I didn't manage to get something up yet.
Keep it up @sabarasaba! Hope to see your resource view as PR soon 👍

@sabarasaba feel free to use css classes to make your life easier. I think it's reasonable that when using resources there is a min width on columns. The reason it's not that way by default you really don't want horizontal scrollbars. This case is different tho

@sabarasaba It's looking great. Have you completed it? Just wanted to implement this :)

@sabarasaba can I see your implementation ?

Is it possible to control the length of title like "The quick brown jumps over a lazy dog..." to "The quick brown fox.." in month view, but should not affect in agenda....I tried with 'titleAccessor' but it affects agenda also.

I think you could via css selectors and
https://css-tricks.com/snippets/css/truncate-string-with-ellipsis/
You could also just conditionally change the titleaccessor based on the current view.

Thank you.....eventPropGetter and css solved my issue
On Fri 22 Feb, 2019, 7:17 PM Benjamin Kniffler<EMAIL_ADDRESS>wrote:

I think you could via css selectors and
https://css-tricks.com/snippets/css/truncate-string-with-ellipsis/
You could also just conditionally change the titleaccessor based on the
current view.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/intljusticemission/react-big-calendar/issues/13#issuecomment-466401393,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AY0UeULq7gJTE7B3vSVZxz9RL9R7oW5Tks5vP_TegaJpZM4Guafl
.

One more question..is it possible to change the name of agenda to something
else like list view?
On Tue 26 Feb, 2019, 1:26 PM Niladri Mahato<EMAIL_ADDRESS>wrote:

Thank you.....eventPropGetter and css solved my issue
On Fri 22 Feb, 2019, 7:17 PM Benjamin Kniffler<EMAIL_ADDRESS>wrote:

I think you could via css selectors and
https://css-tricks.com/snippets/css/truncate-string-with-ellipsis/
You could also just conditionally change the titleaccessor based on the
current view.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/intljusticemission/react-big-calendar/issues/13#issuecomment-466401393,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AY0UeULq7gJTE7B3vSVZxz9RL9R7oW5Tks5vP_TegaJpZM4Guafl
.

I think setting localizer to something like {messages: { agenda: 'List View' }} could solve this (I've not tried it though). But you shouldn't be misusing the issue here as a help desk, there is a dedicated community for this: https://github.com/intljusticemission/react-big-calendar#join-us-on-reactiflux-discord

hi, can @sabarasaba show step by step how to implement this view? i'm interested

Hi @sabarasaba, we're also very interested in this implementation. Is there a PR or the code you can share so we take a look and try to customize a bit? Thanks 🙏

Hi @sabarasaba, we're also very interested in this implementation. Is there a PR or the code you can share so we take a look and try to customize a bit? Thanks 🙏

i'm interested too

I dont work at the company that I built this for. But you can check out the code here https://www.npmjs.com/package/deskbookers-calendar https://github.com/deskbookers/react-big-calendar
It's been quite a few years so sadly that's all I can provide.


docs: add release notes for 3.8.1 and 3.9.1 patch releases

Both released on April 29, 2024. (cc @Yilialinn )

Please review @kayx23 @yzeng25 @AlinsRan


order statistics status link loses date range

In /dashboard/orders/statistics/ apply a date filter.

the order statuses now count only orders within the given period

Click on one of the order statuses

Actual: A list with all orders with that status is shown.
Expected: A list with orders within the given period and with that status is shown.

This also require changes in the order list filters, since there's only shortcut query filter for order status.


Automation code format differs is using Config.yaml vs Auto.yaml

Having told the config file we are going to use a separate file for automations, we can no longer use the initial formatted code supplied for installation. As well any automations you have created through the UI or have in your automations.yaml file will no longer work as they are being overridden by the automations section you have added to the configuration.yaml file if you followed the directions.
To add this automation via the ui or to your automations.yaml file it must be formatted like so

alias: Plex Assistant Automation
trigger:
    - event_data:
       action: call_service
      event_type: ifttt_webhook_received
      platform: event
condition:
        condition: template
        value_template: "{{ trigger.event.data.service == 'plex_assistant.command' }}"
action:
      - data_template:
          command: "{{ trigger.event.data.command }}"
        service_template: '{{ trigger.event.data.service }}'
        ###################################################
        # The following 4 lines are the added debug lines #
        ###################################################
      - service: system_log.write
        data:
          message: "{{ trigger.event.data.command }}"
          level: warning

Updated readme and created an automation blueprint to go along with it.


extract entities from both the title and the abstracts

when we rerun this pipeline after we refine our data collection efforts, we could also extract entities from BOTH titles and abstracts


Remove LGTM references

LGTM shut down last year, so we cannot use it anymore.

LGTM is now just CodeQL, which we do still use...


Add utilities for Closeables and Runnables

Add KiwiRunnables and ThrowingRunnable
Add KiwiCloseables

@sonatype-lift help

@sonatype-lift help


Reporting of specific time frame

How can i get the Grafana Dashboard for a specific time frame?
Is there any way i can specify the to and from parameters in the request string?

Yes, this is supported via query parameters (see the Time range section of the readme).


"Săcele", "Traian" are listed in the drop-down menu

Description:
When user writes "Săcele", "Traian" the location appears in the drop-down menu next to the comune and the county which is a part according to the law
Precondition:
The website is up an running.

Step 1
Write in the search bar "Săcele"

Expected results
The location appears in the drop-down menu as "Sat Săcele, CONSTANȚA, (Săcele)"

Step 3
Write in the search bar "Traian"

Expected results
The location appears in the drop-down menu as "Sat Traian, CONSTANȚA, (Săcele)"


Additional struct inserted when using allOf and an inline definition compared to 0.9.0

Problem statement
There is an additional struct inserted in a type using allOf with an inline definition, as compared to 0.9.0. This is causing a build break, and I would like to know if this is intentional, so I should update my code, or if it's unintentional and should be fixed.
Types with commit hash 6229122 from April 11, just after 0.9.0
type NamedValue struct {
  ExecuteValues
  // Required: true
  Name *string `json:"Name"`
}

Types with commit hash 6adc14b from December 11
type NamedValue struct {
  ExecuteValues
  NamedValueAllOf1
}

type NamedValueAllOf1 struct {
  // Required: true
  Name *string `json:"Name"`
}

Here is the code which used to be valid is no longer:
return &models.NamedValue{Name: &name}
Swagger specification
NamedValue:
  allOf:
  - $ref: "#/definitions/ExecuteValues"
  - required:
    - Name
    properties:
      Name:
        type: string

Environment
swagger version: commit hash 6adc14b from December 11
go version: 1.8
OS: macOS 10.12.6

@gregmarr yes those changes were introduced since the swagger flatten command so they are intentional

Thanks.


Jframe terminal

Not a terribly important issue BUT you might want to get a jframe terminal here so we can do extra stuff like display the inventory and a map and such.
I know Aidan is good at this and I'm not, so here's an issue instead of a pull request.
Don't forget to subscribe to pewdiepie.

Actually, I was already adding a visual screen in my own private fork. I'll submit a pull request as soon as I'm done.

lit. closed because Aidan is awesome.


Allow UIPlugin to be used without rendering

Objective

Fixes #3815

Solution

Make UIPlugin add rendering-dependent systems only when RenderPlugin is enabled

Dependencies

#2988
#3835

Notes
As stated by cart on Discord regarding #3835:

Lets wait. I'm hesitant to decouple windows from "actual windows" conceptually. If the goal is to test UI, I think we should consider other options (such as render targets or "null" targets). We'll need to decouple UI from windows anyway because we want to enable rendering ui to textures.

this PR might become obsolete as Bevy's UI in general needs an engineering overhaul.

@alice-i-cecile @JMS55 @superdump I propose we close this and convert it into an issue, as recommended in the Triage Doc. It's a good idea, but it's stale.

Agreed. Feel free to close this once an issue is up.

Oop, looks like the old issue still covers it. Closing


CVE-2022-27191

https://access.redhat.com/security/cve/CVE-2022-27191
Some other Go modules are also very outdated. I will make a PR.

I merged your PR, thank you


VL822-QFN76 discontinued

Tried to source parts for this design but JLCPCB has informed me that my order for the VL822-QFN76 was cancelled because the part is discontinued. Is there a suitable replacement, perhaps a more expensive alternative so I can complete the BOM and get this built?

First of all, fyi there's been fixes to the board since v4 so make sure you're using the latest design. How many boards are you building? Last I saw there was still parts in stock.

I'm only looking to produce a couple of units for bench testing. I believe I've downloaded the v0.4 posted as the latest but maybe that's where I've gone wrong - does that BOM not contain this obsolete component?

There is no v0.4.1 which is not yet released. I've attached the files below.
BOM-XG_Mobile_Dock.csv
CPL-XG_Mobile_Dock.csv
GERBER-XG_Mobile_Dock.zip
I don't know why JLCPCB says it's discontinued. How are you buying it? I see there's 18 in stock right now.

I'm just trying to order via JLCPCB parts. Posted a screen capture of my
order history below in case that's helpful. You can see my order for
VL822-QFN76 was cancelled - the other bom parts appear to have processed
fine. Where do you see there are 18 in stock? My view of the parts status
shows 0 in stock.
I'm wondering if this is a regional issue. I'm trying to place this order
from the US. Do you happen to be ordering from a different country?
On Mon, Jul 29, 2024, 11:09 PM osy @.***> wrote:

The latest is v0.4.1 which is not yet released. I've attached the files
below.
BOM-XG_Mobile_Dock.csv
https://github.com/user-attachments/files/16421498/BOM-XG_Mobile_Dock.csv
CPL-XG_Mobile_Dock.csv
https://github.com/user-attachments/files/16421499/CPL-XG_Mobile_Dock.csv
GERBER-XG_Mobile_Dock.zip
https://github.com/user-attachments/files/16421500/GERBER-XG_Mobile_Dock.zip
I don't know why JLCPCB says it's discontinued. How are you buying it? I
see there's 18 in stock right now.
image.png (view on web)
https://github.com/user-attachments/assets/3169708f-dc76-45fe-b700-b91d4a2a9c00
—
Reply to this email directly, view it on GitHub
https://github.com/osy/XG_Mobile_Station/issues/6#issuecomment-2257372284,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARXBYMQLIHAI7JQAPVAW5TTZO37WTAVCNFSM6AAAAABLT2URLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJXGM3TEMRYGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

I don't see your screenshot but here's what I see in the bill of materials screen when ordering

I clicked the search button then clicked on the only part and I see "People are selling their idle parts:"

This is very strange. I attached a couple of PNGs hopefully those come
through. I definitely do not see any stock of that same part on their page.
I guess I'll follow-up with support and include your screen shot to
demonstrate others do find them in stock. If they won't sell the parts to
me, the least they can do is refund me the other parts as they're useless
to me if I can't source the VL822. And it showed stock when I placed the
order...
On Mon, Jul 29, 2024, 11:31 PM osy @.***> wrote:

I don't see your screenshot but here's what I see in the bill of materials
screen when ordering
image.png (view on web)
https://github.com/user-attachments/assets/bbc1af1a-431f-4181-bf8b-517ca625a978
I clicked the search button then clicked on the only part and I see
"People are selling their idle parts:"
—
Reply to this email directly, view it on GitHub
https://github.com/osy/XG_Mobile_Station/issues/6#issuecomment-2257388833,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARXBYMSGJ3NMPBMY2CUXBXLZO4CKBAVCNFSM6AAAAABLT2URLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJXGM4DQOBTGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

FWIW, the dock still works without the USB hub. It's just that on the Ally, there's only one USB port so you can't connect anything without a hub.

Ahh, good to know. In that case, I'll priced to have the board produced.
I'll come back here when support gets back to me.
On Mon, Jul 29, 2024, 11:44 PM osy @.***> wrote:

FWIW, the dock still works without the USB hub. It's just that on the
Ally, there's only one USB port so you can't connect anything without a hub.
—
Reply to this email directly, view it on GitHub
https://github.com/osy/XG_Mobile_Station/issues/6#issuecomment-2257398264,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARXBYMRCYU2UWNDVXXEXY3TZO4DYXAVCNFSM6AAAAABLT2URLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJXGM4TQMRWGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

So JLCPCB support confirms the part status has become unavailable. And
looking at your screen grab now with fresh eyes, I  see you're looking at
the idle inventory of another JLCPCB customer that's trying to sell off the
excess inventory they bought on the website. I'd completely blew through
that detail and went straight to order direct from JLCPCB at the BOM
process stage. Adding to the confusion, if you perform a direct search of
that part outside of the BOM process using the part manager, it isn't
immediately obvious that there is idle stock. You need to click on the
listed component to right of the displayed part's link (don't click on the
part's link as that will navigate you away from the page) in the white
non-obvious area. Only then does a drop down appear showing idle parts
availability. Maybe others (unfamiliar with JLCPCB as I am) looking to do
their own build will find this info helpful. Anyhow, I went back and
secured those idle components to fulfill my BOM so I'm looking forward to
testing this out with a RTX2060 I have sitting on the shelf.
But once those remaining (now 16) idle components are sold off I gather the
only option is to have the assemblies built without the USB functionality
as you mention. Do you know if there is a drop-in replacement from a
different manufacturer (e.g. Realtek)?
On Mon, Jul 29, 2024, 11:46 PM Christopher Beaudoin <
@.***> wrote:

Ahh, good to know. In that case, I'll priced to have the board produced.
I'll come back here when support gets back to me.
On Mon, Jul 29, 2024, 11:44 PM osy @.***> wrote:

FWIW, the dock still works without the USB hub. It's just that on the
Ally, there's only one USB port so you can't connect anything without a hub.
—
Reply to this email directly, view it on GitHub
https://github.com/osy/XG_Mobile_Station/issues/6#issuecomment-2257398264,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARXBYMRCYU2UWNDVXXEXY3TZO4DYXAVCNFSM6AAAAABLT2URLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJXGM4TQMRWGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

There's no drop in replacement, but I see a couple of options

You can consign parts and order it outside of JLCPCB.
You can design a new board around RTS5423 or USB7216C or similar ICs. They combine USB PD controller and USB hub so you can get rid of the TI PD controller as well. Maybe the combined cost will be cheaper.
You can remove both the PD and hub controller and pass through the USB-C directly to a USB-C port. You will only get a single USB-C port and you can attach an external hub.

Great thanks for the thoughts. Good reason for me to pickup KiCAD


"xcodebuild" command but it exited with error code 66 with some error and warnings

I am trying to login with twitter but after all configuration i am getting some issue.anyone have any solution????
**issue is : **
error Failed to build iOS project. We ran "xcodebuild" command but it exited with error code 66. To debug build logs further, consider building your app with Xcode.app, by opening demo_app.xcworkspace. Run CLI with --verbose flag for more details.
Command line invocation:
/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -workspace demo_app.xcworkspace -configuration Debug -scheme demo_app -destination id=86B36D3D-AEDC-4CFC-B673-6545FDA57A11
2020-07-22 07:46:53.352 xcodebuild[2385:3368432] warning:  The file reference for "Objective-C/TOCropViewController/Models/TOActivityCroppedImageProvider.h" is a member of multiple groups ("TOCropViewController" and "TOCropViewController"); this indicates a malformed project.  Only the membership in one of the groups will be preserved (but membership in targets will be unaffected).  If you want a reference to the same file in more than one group, please add another reference to the same path.
2020-07-22 07:46:53.352 xcodebuild[2385:3368432] warning:  The file reference for "Objective-C/TOCropViewController/Views/TOCropOverlayView.h" is a member of multiple groups ("TOCropViewController" and "TOCropViewController"); this indicates a malformed project.  Only the membership in one of the groups will be preserved (but membership in targets will be unaffected).  If you want a reference to the same file in more than one group, please add another reference to the same path.
2020-07-22 07:46:53.352 xcodebuild[2385:3368432] warning:  The file reference for "Objective-C/TOCropViewController/Models/TOCroppedImageAttributes.h" is a member of multiple groups ("TOCropViewController" and "TOCropViewController"); this indicates a malformed project.  Only the membership in one of the groups will be preserved (but membership in targets will be unaffected).  If you want a reference to the same file in more than one group, please add another reference to the same path.
2020-07-22 07:46:53.352 xcodebuild[2385:3368432] warning:  The file reference for "Objective-C/TOCropViewController/Views/TOCropScrollView.h" is a member of multiple groups ("TOCropViewController" and "TOCropViewController"); this indicates a malformed project.  Only the membership in one of the groups will be preserved (but membership in targets will be unaffected).  If you want a reference to the same file in more than one group, please add another reference to the same path.
2020-07-22 07:46:53.352 xcodebuild[2385:3368432] warning:  The file reference for "Objective-C/TOCropViewController/Views/TOCropToolbar.h" is a member of multiple groups ("TOCropViewController" and "TOCropViewController"); this indicates a malformed project.  Only the membership in one of the groups will be preserved (but membership in targets will be unaffected).  If you want a reference to the same file in more than one group, please add another reference to the same path.
2020-07-22 07:46:53.352 xcodebuild[2385:3368432] warning:  The file reference for "Objective-C/TOCropViewController/Views/TOCropView.h" is a member of multiple groups ("TOCropViewController" and "TOCropViewController"); this indicates a malformed project.  Only the membership in one of the groups will be preserved (but membership in targets will be unaffected).  If you want a reference to the same file in more than one group, please add another reference to the same path.
2020-07-22 07:46:53.352 xcodebuild[2385:3368432] warning:  The file reference for "Objective-C/TOCropViewController/TOCropViewController.h" is a member of multiple groups ("TOCropViewController" and "TOCropViewController"); this indicates a malformed project.  Only the membership in one of the groups will be preserved (but membership in targets will be unaffected).  If you want a reference to the same file in more than one group, please add another reference to the same path.
2020-07-22 07:46:53.352 xcodebuild[2385:3368432] warning:  The file reference for "Objective-C/TOCropViewController/Models/TOCropViewControllerTransitioning.h" is a member of multiple groups ("TOCropViewController" and "TOCropViewController"); this indicates a malformed project.  Only the membership in one of the groups will be preserved (but membership in targets will be unaffected).  If you want a reference to the same file in more than one group, please add another reference to the same path.
xcodebuild: error: Scheme demo_app is not currently configured for the build action.

I have faced the same issue and I am suffering for 3 days to solved it but till now I can't solved it.
@sudeepjainn did you solve this issue?


promote chronograf migrator to CLI

The chronograf migrator tool (https://github.com/influxdata/influxdb/blob/master/cmd/chronograf-migrator/main.go) isn't accessible without building the project from scratch. We should either promote it to the main CLI, or (probably better) to a separate project. The key thing is that it needs to be easy to install and use.
(Also - it could really benefit from testing)

@jsteenb2 has opinions on how to go about doing this

We've decided not to pursue the migrator at this time.


Add support for task reports, upload reports to deep storage

This PR allows indexing tasks to return a map of TaskReport objects along with the TaskStatus. A TaskReport will contain structured information about a task, such as row stats, parsing errors, or a list of published segments.
The TaskReports will be uploaded to deep storage along with the Task's stdout log, accessible via an overlord endpoint keyed by task ID.
This is intended to support PR #5418 and #5492 which will generate large blocks of structured information upon task completion.
This large TaskReport information is kept in deep storage only, to avoid storing large objects in the metadata storage or in zookeeper nodes (via RemoteTaskRunner).
ExecutorLifecycle will write the TaskReports to disk and strip out the TaskReport objects before returning a TaskStatus, and the deep storage upload is handled in ForkingTaskRunner like the log upload.

@jon-wei thanks for raising this PR. I'm reviewing it.
BTW, #5492 is changed to not use taskReport anymore. It first used the taskReport to return which segments generated by worker tasks to the supervisor task. This information is temporal and doesn't have to be stored permanently in deep storage.

One of possible alternatives is providing an interface to tasks like adding a taskReporter to TaskToolbox. Each task can use taskReporter if they have something to report. What do you think?

Hm, I decided to keep the current implementation, since I think of the task log and the task reports as very similar things (unstructured vs. structured task logs) and felt like it would be nicer to handle the file writes/uploads together. Doing the uploads in a common place I felt was simpler than adding a file upload step to each individual task implementation.

As a result, from the perspective of overlords, taskReport is always empty.

I felt this was fine, anything above ExecutorLifecycle in the hierarchy of runners/tasks would only see a plain TaskStatus object, so there wouldn't be an empty "taskReports" field

@jihoonson good points, I've changed this to use a TaskReportFileWriter that's injected into the toolbox


Cluster Aware?

Hi,
When i install 2+ kibana services to have a load balancer between them, so i can have high availability for the user dashboards/reports, both service are using the same .kibana index to save get the dashboards and it doesn't mater which server the user gets.
how kaae is going to behave when installed more the once per elasticsearch cluster, will the alerts be fired twice?
maybe in a multi service install there should be a "Heartbeat" that all services will register, and update a index with what host/node is now live and taking care of alerts, but when not reporting more than 1 minute, electing another node/host  to handle the alarms?
10x!

KAAE runs in Kibana, and sends queries to the ES Cluster Kibana is configured to use. As long as you don't run multiple Kibana/Kaae pairs and your load balancer is transparent, there should be no impact.

but to achieve high availability you do install multiple kibana/kaae, so currently the alerts will be send twice?
do you think you'll add support for this?

Sure, we just need to come up with a good strategy, or mimic whatever the mothership Watcher is using. Input and proposals here are extremely welcome, hopefully new users and developers will come onboard with valuable suggestions and ideas  (...or code contributions!)

Only find a word of "Make sure Watcher is installed on every node in the cluster." in watcher's troubleshooting document.
I think there is a fast way to implement: just decide whether to send email by check the version of alert history.
A better but complex way is just what @LazyDBA247-Perion suggest, use a special index to record the state of kaae daemons.

It's been a long time, picking up this after a long pause as we ship firmly towards the future.
An ongoing idea is to leverage GunDB (gundb.io) a new-school distributed graph "database" (but not really) to create an independent cluster of Sentinls and as a centralized location to keep watcher statuses and other elements critical to the distribution of the tasks and/or saved scripts. Being natively developed in NodeJS provides clear advantages as well as shipping with synchronization, automatic conflict resolution and offline-first behaviour. We can even represent it graphically ;)
I'll be prototyping a model in the coming weeks. If anyone cares to join in the discussion, let's talk!

Closing this in favor of future discussion on recent versions.


TextVQA accuracy

Hello, I have got the json file of TextVQA, can you tell me how to get the accuracy? Only the eval code for Textcaps is currently provided.

For TextVQA validation accuracy:
`
2 GPU
python -m torch.distributed.launch --nproc_per_node 2 TAP/tools/run.py --tasks vqa --datasets m4c_textvqa --model m4c_split
--config $config
--run_type val
--save_dir $save_directory
--resume_file $model.ckpt
training_parameters.distributed True
single GPU
python  TAP/tools/run.py --tasks vqa --datasets m4c_textvqa --model m4c_split \ --config $config \ --run_type val \ --save_dir $save_directory \ --resume_file $model.ckp
For TextVQA test accuracy, the test set label is not publicly release, So:

Predict and save as JSON
`python TAP/tools/run.py --tasks vqa --datasets m4c_stvqa --model m4c_split
--config $config
--run_type inference --evalai_inference 1
--save_dir $model.ckpt

`
2. Upload to https://eval.ai/web/challenges/challenge-page/874/ for accuracy calculation

Thank you for your answer. Could you please re-send the download address of the data set? The link cannot be opened, thank you very much.

Hi  @crx15215682925
I find the address provided in data/README.md is invalid. Could you please provide me with a new dataset download address? Thanks.


Fixed passing common test modules path to unelevated Powershell

Fixed the way common test modules are passed to elevated and unelevated powershell. Earlier, only elevated powershell got those through inheritance as a child process. Now we add them to the startup of the process.

Fixed error reported by PSScriptAnalyzer about ? / Where-Object

Converted all the parameters passed to powershell.exe to be a base64 encoded string to avoid complications with quotes.

Removed code which was updated $env:PSModulePath as we do it in startup args for powershell process instead.

Added a way to disable -Quiet for Pester.

@SteveL-MSFT Updated. Please have a look.

@SteveL-MSFT Had forgotten to push. Please have a look.

@JamesWTruher  Can you have a look too?

@SteveL-MSFT @JamesWTruher I have addressed all feedback, please have a look.

@daxian-dbw @SteveL-MSFT  please have another look, I have addressed the feedback and added another bug fix.


validation: for compositions, we need to relax the topic format

Compositions may use values such as ${features.xyz} or ${topic:ABC} when putting values into widgets. We should probably relax the schema, and use additional checks at runtime.

Thinking a bit more about it, the "problem" that we have here does not only apply to "format": "topic" fields, but also to any fields that are not of type string.
Not quite sure how to deal with this. I see two options:

resolve and flatten compositions at build-time, remove the corresponding code from the runtime
do some tricks to validate (invented) replacement values for feature-references at build-time

Let's try to do it the right way (tm): laxar-tooling should be able to expand pages, probably resulting in further bandwidth and startup time savings.

Implemented on master (v2.0.0).


(chore): Bump Go version to 1.21 + regenerate testdata

Description of the change:

Bumps Go version in go.mod to 1.21
Updates GitHub actions to pull Go version from go.mod file
Regenerates testdata

Motivation for the change:

Update to latest Go version to pick up any fixes
fixes #6603

Checklist
If the pull request includes user-facing changes, extra documentation is required:

[ ] Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
[ ] Add or update relevant sections of the docs website in website/content/en/docs

Do we need to adjust content of documentation, for e.g.

https://github.com/operator-framework/operator-sdk/blob/master/website/content/en/docs/upgrading-sdk-version/v1.25.0.md
https://github.com/operator-framework/operator-sdk/blob/master/website/content/en/docs/installation/_index.md#prerequisites-1
https://github.com/operator-framework/operator-sdk/blob/master/website/content/en/docs/building-operators/golang/installation.md#additional-prerequisites
https://github.com/operator-framework/operator-sdk/blob/master/website/content/en/docs/contribution-guidelines/developer-guide.md#prerequisites

?

https://github.com/operator-framework/operator-sdk/blob/master/website/content/en/docs/upgrading-sdk-version/v1.25.0.md

Not this one. This is a migration guide to v1.25.0 of the SDK. Should go unchanged to allow for following upgrades sequentially.

https://github.com/operator-framework/operator-sdk/blob/master/website/content/en/docs/installation/_index.md#prerequisites-1

Should be done here: https://github.com/operator-framework/operator-sdk/pull/6604/files#diff-67f7d617c6c3b9946e5191cddc06275ceb839d85039812a2b44a22d18e1497b7R91

https://github.com/operator-framework/operator-sdk/blob/master/website/content/en/docs/building-operators/golang/installation.md#additional-prerequisites

Should be done here:  https://github.com/operator-framework/operator-sdk/pull/6604/files#diff-ed4ae522b378054b142772bee33ceab89dc2f99d39a40717ed75a1f09c39c3b7R14

https://github.com/operator-framework/operator-sdk/blob/master/website/content/en/docs/contribution-guidelines/developer-guide.md#prerequisites

Looks like I missed this one. Will update.


Open file/folder dialog needs to know its target window

#5338

start with yo code
change the command to be like shown below
set a break point on the executeCommand
run, breakpoint hit, chose a folder
⚡ instead of the debuggee window the dev window opens a new folder

  // Display a message box to the user
  vscode.commands.executeCommand('vscode.openFolder');

Corner case because you manage to change window focus between the invocation of the command and the actual result. Fix is to make sure that calls to the native file/folder picker know the target window.


Module not found error

Was working a day ago, but now it says
ModuleNotFoundError: No module named 'demo'

I tried running the git cell first  but it shows this message
fatal: destination path 'first-order-model' already exists and is not an empty directory.


Unable to import players from an array

Hello,
I am trying to import players that are from a Google Sheet. I believe I have it formatted correctly. It is in an array. See below for the first two records:
['site_id', 'first_name', 'last_name', 'pos', 'team', 'salary', 'fppg', 'injury', 'max_exposure', 'min_exposure', 'ownership']
['58312', "D'Angelo", "Russell", 'SG', 'BKN', '9000', '10.39', '', '23%', '3%', '14%']
However, I get the following error when i run optimizer.load_players(player_array_final):
AttributeError: 'list' object has no attribute 'team'

Hello,
load_players method takes list of Player objects, so you should convert you player arrays to Player objects before.

Oh ok, that makes sense. Thanks! I got it to load, however there seems to be something wrong with the position. For example, when I try to pass D'Angelo Russell (like in the example originally mentioned) his positions goes from SG to S/G, causing an error that won't let me optimize.
Do you know of a way around this? Not sure why it's adding the random "/"

It because positions should be list of positions, it was made in this way because some sites support multipositional players, in your case it should be ['SG']


issue with the custom probe documentation.

I can see that we cannot specify the loopback address in the custom health probe. we have to specify a hostname now. but the document still says we can use <IP_ADDRESS> when we don't have a host name. can this be addressed? thanks

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

ID: 0c47f14c-8432-fa9b-59c2-8283cc455041
Version Independent ID: 2c19c574-2ab7-2c2a-513e-3a0f512d3e23
Content: Create a custom probe - Azure Application Gateway - Azure Portal
Content Source: articles/application-gateway/application-gateway-create-probe-portal.md
Service: application-gateway
GitHub Login: @vhorne
Microsoft Alias: victorh

@sysadmin-exe, This validation has been introduced in the portal recently.
The default probe from Application gateway looks like Http/https://<IP_ADDRESS>:HTTPSettingPort/
If you want the probe to be different from this, then you can go ahead and create custom probe and attach to the HTTPSettings.
If not you can use the default probe.
Let me know if you have any further questions.

Yea. Thought as much. A recent change. So if I want to probe the backend with <IP_ADDRESS>, I just need to not create a probe. Right?

@sysadmin-exe , Yes you are correct.

Thank you. 🙂


flutter can't be imported into an integration test

If you try to import e.g. 'package:flutter/material.dart'; in any file that isn't part of a running Flutter application, you get the following error:
Crash when compiling null,
at character offset null:
Null check operator used on a null value
#0      InferableTypeBuilderMixin.type (package:front_end/src/fasta/builder/type_builder.dart:392:29)

The error doesn't contain any information that would help someone fix it, but at this point I've seen it enough to know what it is. I've learned to expect it when I try to refer to Flutter (even just for type checking) in any script or file outside my Flutter application.
However, I didn't expect to see it in a simple integration test:
import 'package:flutter/material.dart';
import 'package:flutter_test/flutter_test.dart';
import 'package:integration_test/integration_test.dart';

import 'package:my_app/main.dart' as app;

void main() {
  final binding = IntegrationTestWidgetsFlutterBinding.ensureInitialized();

  testWidgets('my first test', (tester) async {
    app.main();

    await tester.pumpAndSettle();
    if (tester.allWidgets
        .any((w) => w.runtimeType == CircularProgressIndicator)) {
      await Future.delayed(const Duration(seconds: 1));
    }
    print('Progress finished');
  });
}

This may not be a recommended thing to do in a test, but since the WidgetTester lets you query the widget tree it's very odd that it can't actually refer to Flutter. When you run this with flutter drive --driver=test_driver/integration_test.dart --target=integration_test/screenshots.dart (using the standard test driver definition as seen in the integration_test documentation), you get the error I referenced earlier.
Is this error intended behavior? Is it possible to refer to Flutter types in integration tests (or other scripts) and I'm just too new to Dart to know how?

The error you are seeing is a crash in the Dart compiler that should not be there. It is tracked upstream at https://github.com/dart-lang/sdk/issues/49641

Verified this by running as described in original description using latest master version and I don't see the reported error / crash log. The tests passed as expected:
W/Parcel  ( 2101): Expecting binder but got null!
I/flutter ( 2101): Progress finished
I/flutter ( 2101): 00:01 +1: (tearDownAll)
I/flutter ( 2101): 00:01 +2: All tests passed!
All tests passed.
dhs@Dhss-MacBook-Pro new_project %

@isaaclyman Can you check the same at your end using latest framework version and confirm ?


Optimize universe nodes and handle r-values in Python backend.

Hi @abergeron @breuleux This is a PR to optimize universe nodes in Python backend.
I also fix some bugs related to compilation of literal strings, which were previously handled as symbol names (string instead of "string").

Hi @breuleux , PR updated !
I re-organized the code_generator code for a better follow-up of function usages.

rvalue() indeeds always receives an already-replaced node. It is now a private method _rvalue().
label() may be called from outside code generator (in Python backend to get main graph name), so it still replaces node if necessary (although I currently replace only nodes, not graphs). Anyway, I added a method _label(), for specific labeling of already-replaced nodes. label() uses _label().


Prefer read over read_8

Both API's allow the reading for target memory into a byte slice, however read will use Word access under the hood for better performance.
Not all targets have byte level access to system memory, however word access is pretty much guaranteed (this is the case for the esp32c3).

bors r+


feat: add BatchWrite, Partition and Index Management to generated clients

This PR was generated using Autosynth. :rainbow:
Synth log will be available here:
https://source.cloud.google.com/results/invocations/c330ec71-3b2b-4ad2-9d49-78b97f45869d/targets

[ ] To automatically regenerate this PR, check this box.

Blocked penting switch to v2 work on master

Superseded by #300


Caught ValueError: Unable to create tensor, you should probably activate padding with 'padding=True' to have batched tensors with the same length.

Question
When I input both images and text, the page displays the following message:
"NETWORK ERROR DUE TO HIGH TRAFFIC. PLEASE REGENERATE OR REFRESH THIS PAGE. (error_code: 1)",
and the terminal shows the following error:
"Caught ValueError: Unable to create tensor, you should probably activate padding with 'padding=True' to have batched tensors with the same length."
The detailed logs are as follows:
`2024-10-14 10:27:35 | INFO | stdout | INFO:     <IP_ADDRESS>:35346 - "POST /worker_generate_stream HTTP/1.1" 200 OK
2024-10-14 10:27:35 | INFO | stdout | Caught ValueError: Unable to create tensor, you should probably activate padding with 'padding=True' to have batched tensors with the same length.
2024-10-14 10:27:35 | INFO | model_worker | Send heart beat. Models: ['llava-v1.5-13b']. Semaphore: Semaphore(value=5, locked=False). global_counter: 3
2024-10-14 10:27:48 | INFO | model_worker | Send heart beat. Models: ['llava-v1.5-13b']. Semaphore: Semaphore(value=5, locked=False). global_counter: 3`
How can I resolve this issue?

Have you solved the problem yet?


check_user_status.py:23: Перенести классы в отдельные...

The puzzle 899-025fd2e2 from #899 has to be resolved:
https://github.com/blablatdinov/quranbot-aiogram/blob/ade96848d72f843e47bc70755ab3c4549fdc1733/src/srv/events/check_user_status.py#L23-L23
The puzzle was created by Ilaletdinov Almaz on 09-Jun-24.
role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

All classes moved #899


Add asr/tts components for xeon and hpu

Description
Add asr/tts components for xeon and hpu
Issues
n/a
Type of change
List the type of change like below. Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would break existing design and interface)

Dependencies
None
Tests
TBD

Please do not merge until the tests and AudioQnA is ready.


Ini-file highlight bug

VS Code version
Code 1.63.2 (899d46d82c4c95423fb7e10e68eba52050e30ba3, 2021-12-15T09:40:02.816Z)
Extension version
2021.12.1559732655
OS type
Windows
OS version
Windows_NT x64 10.0.19042
Python distribution
python.org
Python version
python 3.9.12
Language server
Pylance
Expected behaviour
comment symbols # or ; marks comment only when it's in the beginning of the line (possibly indented) as default read behavior of config parser:
https://docs.python.org/3/library/configparser.html#supported-ini-file-structure

Actual behaviour

Steps to reproduce
create and open ini-file like on screenshot
Logs
No response
Code of Conduct

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

We get our ini syntax highlighting grammar from https://github.com/textmate/ini.tmbundle. Upstream issue: https://github.com/textmate/ini.tmbundle/issues/2

We get our ini syntax highlighting grammar from textmate/ini.tmbundle. Upstream issue: textmate/ini.tmbundle#2

@alexr00
Hello,
since I'm also facing this issue constantly (also with ' char) I've checked the linked repository and it seems that is completely abandoned - the last commit is from 9 years ago and none of the submitted PR's was merged. This indicates that the problem/bug might persist forever.
If the ini syntax highlighting grammar was taken from this repo a long time ago then why it can't be fixed/updated by VSCode team? Can you re-open this issue and suggest a new approach how to fix it?

Opened an issue for adopting a new ini grammar. More info here: https://github.com/microsoft/vscode/issues/141632#issuecomment-1023035195


Implement a general "desugaring" algorithm that converts any ArithmeticCircuit to the vanilla Plonk format

We need to avoid a situation when we compile something to a circuit, and then this circuit cannot be used in our proving protocols.

I believe this issue has been solved. Closing it.


monitoring norconex in production

In production, I like to set alert whenever there is an error. For that I can redirect the standard output to error.txt and if the error.txt exists I like to be alerted.
./collector-http.sh -a start -c gcs-crawl-config.xml 2>error.txt
The error.txt for a good run shows and I like to turn all this off. I tried settings in log4j.properties to ERROR for various settings but cannot get rid of these lines in stdout.
How can I achieve  this or whats the recommended way to monitor successful run in production?
Jun 04, 2019 8:51:17 AM org.apache.tika.config.InitializableProblemHandler$3 handleInitializableProblem
WARNING: JBIG2ImageReader not loaded. jbig2 files will be ignored
See https://pdfbox.apache.org/2.0/dependencies.html#jai-image-io
for optional dependencies.
J2KImageReader not loaded. JPEG2000 files will not be processed.
See https://pdfbox.apache.org/2.0/dependencies.html#jai-image-io
for optional dependencies.
Jun 04, 2019 8:51:36 AM com.google.enterprise.cloudsearch.sdk.BatchRequestService shutDown
INFO: Shutting down batching service. flush on shutdown: true

These errors are from dependent libraries with their own logging framework.  You can at least work on the warning by including the missing dependencies.  It is complaining about two jars missing in your lib folder. Those are not shipped with HTTP Collector due to licensing restrictions affecting distribution.
JBIG2: https://search.maven.org/remotecontent?filepath=com/levigo/jbig2/levigo-jbig2-imageio/1.6.5/levigo-jbig2-imageio-1.6.5.jar
JPEG2000: https://search.maven.org/remotecontent?filepath=com/github/jai-imageio/jai-imageio-jpeg2000/1.3.0/jai-imageio-jpeg2000-1.3.0.jar
Let me know if that helps.


[BEAM-7892] Fix Beam nightly release snapshots.

R: @iemejia
cc: @udim