[CT-3263] [Feature] User space Jinja macro for converting DB API 2.0 type_codes into data_types

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature
Example prototype
https://github.com/dbt-labs/dbt-core/pull/8887#issuecomment-1779331994
Decision criteria for where adapters-related logic should live
From @MichelleArk here:

In case it's helpful, my decision criteria for where adapters-related logic should live boils down to:

If the implementation does not or should not vary by adapter -> dbt-core
If it's adapter specific + has only one objectively correct implementation -> adapter interface, implemented in python for maintainers to overwrite as necessary.

This is also easier to unit test for adapter maintainers!

If it's adapter specific + should be flexible to end-user tweaks and customizations -> adapter interface, implemented in jinja (user space) for end-users to customize entirely how they see fit for their dbt project.

As much as I'd like this mapping of type_code to data_type to have a single 'correct' implementation per adapter, I can see how user-defined types put a bit of a wrench in that. It may be possible to split the implementation into base types in python (could follow a similar pattern to https://github.com/dbt-labs/dbt-core/pull/8357) and user-defined types, but that may introduce more complexity than it's worth...

One possible approach (to be refined)

Create an adapter-specific base lookup table of type_code → data_type (within Python or Jinja)
Allow an adapter-specific supplemental lookup table of type_code → data_type (in user-space Jinja)
Create a dbt-core implementation that combines 1) and 2) above (with the latter taking precedence)
Use 3) above within adapter-specific data_type_code_to_name (Python) implementations (see here and here)

Alternative approach 1

As above
As above
Update get_column_schema_from_query to take 1) and 2) into account (with the latter taking precedence)

Alternative approaches 2 and 3
Same as the two approaches above, but with only a single adapter-specific lookup table (instead of separate base and supplemental lookup tables)
I haven't considered any of the above options deeply enough to have a preference yet.
Describe alternatives you've considered
The main alternative is doing these lookups with user-provided (or package-provided) macros.
The example prototype above can be entirely done by users without there being any interfaces added to dbt-core or adapters.
These macros can be defined in two places:

macros directory of the user's dbt project
within a dbt package installed by the user

It would be easier if dbt can provide base implementations and documentation though.
Who will this benefit?
A primary use-case is being able to properly display the actual/expected data types when contract enforcement fails (c.f. https://github.com/dbt-labs/dbt-core/pull/8887).
A two-fer-one use-case is direct usage of get_column_schema_from_query (like described in https://github.com/dbt-labs/dbt-core/issues/8877) so that Column.data_type contains legit data types.
This will benefit users of dbt-postgres that have data types like money, uuid, etc that don't automatically have a type_code lookup within psycopg2. It also would cover the case of geometry within the postgis distribution of postgres as well as user-defined types.
There might be other adapters besides dbt-postgres that have similar needs.
Are you interested in contributing this feature?
No response
Anything else?
No response

@graciegoheen and @jtcohen6 discussed the following in in a video call earlier today:
Impact & utility
This seems primarily for users of postgres-based data platforms that support user-defined types or other atypical types (geography, money, etc). It might not be widely useful outside of dbt-postgres.
Priority
While this wouldn't be a high-priority for us, we're generally in favor of surfacing a macro that users can override that contains their own translation table.
Refinement
Marking as "Refinement" to determine which precise approach we'd like to take. The easiest would be a supplemental definition like this that takes precedence over any other definition (using "merge" rather than "clobber"):
{# Define your lookup table here #}
{% macro get_type_code_lookup_table() %}
  {% set lookup_table = {
      '790': 'MONEY',
      '2950': 'UUID',
  } %}
  {{ return(lookup_table) }}
{% endmacro %}


Need to validate statements on fallback order

there is conflicting info on line about fallback order.  This article says we go immediately to the next in fallback order if one source is not available.  Other docs and my understanding is that we only go to hte next in the list when signatures are considered "out of date."
https://docs.microsoft.com/en-us/microsoft-365/security/defender-endpoint/manage-outdated-endpoints-microsoft-defender-antivirus?view=o365-worldwide#set-the-number-of-days-before-protection-is-reported-as-out-of-date

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

ID: 0f9be21b-f9c7-5022-4389-5f860847ffb3
Version Independent ID: 42a36c44-baf3-419d-b4ff-0a205f2ac8f8
Content: Manage how and where Microsoft Defender Antivirus receives updates
Content Source: microsoft-365/security/defender-endpoint/manage-protection-updates-microsoft-defender-antivirus.md
Product: m365-security
Technology: mde
GitHub Login: @denisebmsft
Microsoft Alias: deniseb

@denisebmsft Please help us in resolving this issue. Thanks

Greetings! We are working on this. Expect an update soon.

Thank you @jrhi for the feedback. I have updated the article, and the changes will be live later today. Please let me know if there are any other issues.


Fix empty service tree view

Add missing onCreateGroup property.

I've checked it out and it fixes the issue 👍


not sure how to add publons link

Not sure what information I need to link to publons. My URL is researcher/ rather than author/
https://publons.com/researcher/1387840/timothy-bartley/

Hi @bartleyt,
Now supported is supported in your .yaml file:
publons: 1387840/timothy-bartley/

I did it for you.


Adding useHermes tag in the documentation

Issue - https://github.com/microsoft/react-native-windows/issues/7426
Microsoft Reviewers: Open in CodeFlow

thanks @imrishabh18 ! Would you mind updating the same file in the versioned_docs/version-0.64 directory?

Thank you @imrishabh18 for your contribution! We really appreciate it!


Add wet/dry functionality for the Multilayer SWE in 1D

This PR adds wet/dry functionality to the ShallowWaterMultiLayerEquations1D.
The new functionality includes support for shock-capturing, a positivity-limiter and the new hydrostatic_reconstruction_ersing_etal as well as corresponding tests and examples.
The general strategy follows the implementation of the ShallowWaterEquationsWetDry1D. However, in contrast to the ShallowWaterEquationsWetDry1D the positivity-limiter is applied layerwise and only acts on the water heights h (the momentum remains unchanged) and a velocity desingularization is applied to avoid numerical problems near dry states. The specific implementation of the positivity-limiter is still experimental and might change.
The new hydrostatic reconstruction can be used to create an entropy-stable and well-balanced scheme if the surface flux is set to
surface_flux = (FluxHydrostaticReconstruction(FluxPlusDissipation(flux_ersing_etal, DissipationLocalLaxFriedrichs()), hydrostatic_reconstruction_ersing_etal),
                FluxHydrostaticReconstruction(flux_nonconservative_ersing_etal, hydrostatic_reconstruction_ersing_etal))

It seems that the Mac CI tests are failing due to too strict tolerances. We should keep an eye on this because it would be very annoying (and concerning) if we need to soften the tolerances on so many tests.

It seems that the Mac CI tests are failing due to too strict tolerances. We should keep an eye on this because it would be very annoying (and concerning) if we need to soften the tolerances on so many tests

I have softened the tolerances in 2857753d5373484df8c3da743e1a28e5144b09a5 and the CI now passes (at least in the recent run). I do not really see another alternative to fix the tests.
I also think the tolerance changes are reasonable. Only elixir_shallowwater_multilayer_beach.jl required a pretty high tolerance atol=1e-5, but this is in line with the tolerance atol=1e-7, set in elixir_shallowwater_beach.jl. The higher value is probably necessary, since the test runs until t=0.25 instead of t=0.05.

I am not sure why these lines are not reported as being covered. Any ideas @ranocha or @sloede ?

Because we never call real(equations) in a standard setup? I guess you could get also get rid of this if you don't use it

I am not sure why these lines are not reported as being covered. Any ideas @ranocha or @sloede ?

Because we never call real(equations) in a standard setup? I guess you could get also get rid of this if you don't use it

@ranocha These lines are definitely called during testing and the respective function calls also show up as covered, so we expect coverage. The same problem also appears for a similar function nlayers(equations).


Don't print a trailing space on steps with table args

Fixes #1787 🙂

Not sure what those failures about, from the logs it doesn't look like any tests or linter rules are actually failing?

@camjackson - I will take a look at this PR.
I am currently looking at a fix for #318 and I want to wrap that before I look at this, I assume there could be some overlap.

Thanks for approving and merging, @sriv and @zabil! When can we expect to see a new version of the extension published with this change?

Hey @camjackson - gauge 1.1.6 is out and it includes this change -https://github.com/getgauge/gauge/releases/tag/v1.1.6
Thanks again for the contrib!


Error loading GPU renderer (GT: 0.00 GHz) even when satisfying the configuration checklist

Thanks for your work in advance. I cannot acquire hardware decode and would like to ask for your help.
GPU:
Intel i5-6500 (HD530), NVIDIA GTX1060
Pre-requisite:

Renamed GFX0 to IGPU, injected Intel with 0x19120001 (connector-less)
IOVARendererID presented under nvAccelerator (under PEG0@1 → IOPP → GFX0@0)
GVA info: Successfully connected to the Intel plugin, offline Gen9 (followed by AVDCreateGPUAccelerator: Error loading GPU renderer VDADecoderCreate failed. err: -12473)
IMEI presented
No overrides
Mac model as iMac17,1 (Board-ID: Mac-DB15BD556843C820)
Have shikigva=4 in boot flags (Lily 1.2, NvidiaGraphicsFixup 1.2, Shiki 2.1)

Problem:
GT: 0.00 GHz in Intel Power Gadget
VDADecoderChecker returned:
GVA info: Successfully connected to the Intel plugin, offline Gen9
AVDCreateGPUAccelerator: Error loading GPU renderer
VDADecoderCreate failed. err: -12473
An error was returned by the decoder layer. This may happen for example because of bitstream/data errors during a decode operation. This error may also be returned from VDADecoderCreate when hardware decoder resources are available on the system but currently in use by another process.
VDADecoderCreate failed. err: -12473
Would you please point me some directions in enabling QuickSync for my hackintosh?
Attachment:
iMac.ioreg
EFI

Hi, well, such an error happens when Shiki fails to patch AppleGVA.framework to enable NVIDIA compatibility (that's what shikigva=4 does). To prove it you could replace it manually and see if it fixes things.
Before that, however, I would like you to try running VDADecoderChecker in 3 different ways and post all the output you get here:
DYLD_PREBIND_DEBUG=1 DYLD_SHARED_CACHE_DONT_VALIDATE=1 /path/to/vdadecoderchecker
DYLD_PREBIND_DEBUG=1 /path/to/vdadecoderchecker
DYLD_PREBIND_DEBUG=1 DYLD_SHARED_REGION=avoid /path/to/vdadecoderchecker

If at least one of the commands prints that hardware acceleration is fully supported, it is probably worth stopping at that point. Otherwise do the following steps to check with manually patched AppleGVA:

Disable Lilu and all the plugins (this is just in case, it should not be really necessary but better to do it).
Download a patched AppleGVA.framework for 10.12.6
Install it

sudo su
cd /System/Library/PrivateFrameworks/
mv AppleGVA.framework AppleGVA.framework.org
unzip -q /path/to/AppleGVA.framework.org.zip
codesign --deep -fs - AppleGVA.framework
chown -R root:wheel AppleGVA.framework
chmod -R 755 AppleGVA.framework
update_dyld_shared_cache -force
reboot

Reenable Lilu with the plugins and see if it fixed things for you

Most likely it will work, so the only thing to do will be to restore the original AppleGVA.framework and understand why it does not get patched dynamically. Unfortunately it is not an easy task, since many system issues (for example, the most common case is a corrupted/missing dyld shared cache or broken signature) will lead to this.

Thanks for you quick feedback! I did the testings as stated and got the following results:

DYLD_PREBIND_DEBUG=1 DYLD_SHARED_CACHE_DONT_VALIDATE=1 /path/to/vdadecoderchecker
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/VideoDecodeAcceleration.framework/Versions/A/VideoDecodeAcceleration
dyld: image not prebound, so could not use prebinding in /Users/kctsangab/Documents/Hackintosh/VDADecoderChecker
dyld: image not prebound, so could not use prebinding in /System/Library/Extensions/AppleIntelSKLGraphicsVADriver.bundle/Contents/MacOS/AppleIntelSKLGraphicsVADriver
GVA info: Successfully connected to the Intel plugin, offline Gen9
dyld: image not prebound, so could not use prebinding in /System/Library/Extensions/GeForceVADriverWeb.bundle/Contents/MacOS/GeForceVADriverWeb
AVDCreateGPUAccelerator: Error loading GPU renderer
VDADecoderCreate failed. err: -12473
An error was returned by the decoder layer. This may happen for example because of bitstream/data errors during a decode operation. This error may also be returned from VDADecoderCreate when hardware decoder resources are available on the system but currently in use by another process.
VDADecoderCreate failed. err: -12473

DYLD_PREBIND_DEBUG=1 /path/to/vdadecoderchecker
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/VideoDecodeAcceleration.framework/Versions/A/VideoDecodeAcceleration
dyld: image not prebound, so could not use prebinding in /Users/kctsangab/Documents/Hackintosh/VDADecoderChecker
dyld: image not prebound, so could not use prebinding in /System/Library/Extensions/AppleIntelSKLGraphicsVADriver.bundle/Contents/MacOS/AppleIntelSKLGraphicsVADriver
GVA info: Successfully connected to the Intel plugin, offline Gen9
dyld: image not prebound, so could not use prebinding in /System/Library/Extensions/GeForceVADriverWeb.bundle/Contents/MacOS/GeForceVADriverWeb
AVDCreateGPUAccelerator: Error loading GPU renderer
VDADecoderCreate failed. err: -12473
An error was returned by the decoder layer. This may happen for example because of bitstream/data errors during a decode operation. This error may also be returned from VDADecoderCreate when hardware decoder resources are available on the system but currently in use by another process.
VDADecoderCreate failed. err: -12473

DYLD_PREBIND_DEBUG=1 DYLD_SHARED_REGION=avoid /path/to/vdadecoderchecker
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libsystem_kernel.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libsystem_m.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libsystem_blocks.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/libc++abi.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/libc++.1.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/libobjc.A.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libdispatch.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libsystem_sandbox.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libmacho.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libsystem_notify.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libsystem_symptoms.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libsystem_trace.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libsystem_dnssd.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libcorecrypto.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libcommonCrypto.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libsystem_networkextension.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libsystem_configuration.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libsystem_network.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libsystem_info.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libsystem_asl.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libxpc.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/liblaunch.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libsystem_c.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libkeymgr.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libunwind.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libcompiler_rt.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libsystem_malloc.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libdyld.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libsystem_platform.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libsystem_pthread.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libcache.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libquarantine.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libcopyfile.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libremovefile.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libsystem_coreservices.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libsystem_coretls.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libsystem_secinit.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/libSystem.B.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/libenergytrace.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/libbsm.0.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/libDiagnosticMessagesClient.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/libicucore.A.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/libz.1.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
dyld: image not prebound, so could not use prebinding in /usr/lib/system/libkxld.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
dyld: image not prebound, so could not use prebinding in /usr/lib/libauto.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/libpcap.A.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/libcoretls.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/libOpenScriptingUtil.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/libpam.2.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/libsqlite3.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/libbz2.1.0.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/liblzma.5.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/libxml2.2.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/libxar.1.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/Security.framework/Versions/A/Security
dyld: image not prebound, so could not use prebinding in /usr/lib/libcoretls_cfhelpers.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/libnetwork.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
dyld: image not prebound, so could not use prebinding in /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport
dyld: image not prebound, so could not use prebinding in /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
dyld: image not prebound, so could not use prebinding in /usr/lib/libarchive.2.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/liblangid.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/libCRFSuite.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
dyld: image not prebound, so could not use prebinding in /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC
dyld: image not prebound, so could not use prebinding in /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji
dyld: image not prebound, so could not use prebinding in /usr/lib/libiconv.2.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/libcmph.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling
dyld: image not prebound, so could not use prebinding in /usr/lib/libmarisa.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/libChineseTokenizer.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/libcompression.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
dyld: image not prebound, so could not use prebinding in /usr/lib/libmecabra.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
dyld: image not prebound, so could not use prebinding in /usr/lib/libxslt.1.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync
dyld: image not prebound, so could not use prebinding in /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
dyld: image not prebound, so could not use prebinding in /usr/lib/libheimdal-asn1.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/libresolv.9.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
dyld: image not prebound, so could not use prebinding in /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/GSS.framework/Versions/A/GSS
dyld: image not prebound, so could not use prebinding in /usr/lib/libcups.2.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
dyld: image not prebound, so could not use prebinding in /System/Library/PrivateFrameworks/GPUCompiler.framework/libmetal_timestamp.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/Metal.framework/Versions/A/Metal
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
dyld: image not prebound, so could not use prebinding in /usr/lib/libdscsym.dylib
dyld: image not prebound, so could not use prebinding in /usr/lib/libspindump.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia
dyld: image not prebound, so could not use prebinding in /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/VideoDecodeAcceleration.framework/Versions/A/VideoDecodeAcceleration
dyld: image not prebound, so could not use prebinding in /Users/kctsangab/Documents/Hackintosh/VDADecoderChecker
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
dyld: image not prebound, so could not use prebinding in /System/Library/PrivateFrameworks/AppleGVA.framework/AppleGVA
dyld: image not prebound, so could not use prebinding in /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment
dyld: image not prebound, so could not use prebinding in /System/Library/PrivateFrameworks/DSExternalDisplay.framework/Versions/A/DSExternalDisplay
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay
dyld: image not prebound, so could not use prebinding in /usr/lib/libFosl_dynamic.dylib
dyld: image not prebound, so could not use prebinding in /System/Library/PrivateFrameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders
dyld: image not prebound, so could not use prebinding in /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage
dyld: image not prebound, so could not use prebinding in /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
dyld: image not prebound, so could not use prebinding in /System/Library/PrivateFrameworks/SkyLight.framework/SkyLight
dyld: image not prebound, so could not use prebinding in /System/Library/Extensions/AppleIntelSKLGraphicsVADriver.bundle/Contents/MacOS/AppleIntelSKLGraphicsVADriver
GVA info: Successfully connected to the Intel plugin, offline Gen9
dyld: image not prebound, so could not use prebinding in /System/Library/Extensions/GeForceVADriverWeb.bundle/Contents/MacOS/GeForceVADriverWeb
dyld: image not prebound, so could not use prebinding in /System/Library/Extensions/AppleIntelSKLGraphicsVAME.bundle/Contents/MacOS/AppleIntelSKLGraphicsVAME
Hardware acceleration is fully supported

For the third test, it does stated "Hardware acceleration is fully supported".
Does it mean I can try the patched AppleGVA provided by you?
Once again, thanks for your work and help.

Ok, I understand what is going wrong now. Unlike CoreFP AppleGVA resides in shared cache, and a patch applied to it does not reach all the apps but only select ones (iTunes and QuickTime by default). A proper fix will require a broader research in Lilu user patcher, which I am not going to do for 1.2.0 for stability reasons.
As for now there could be 3 workarounds:

Use a patched AppleGVA.framework, that will work, though it is a rather undesired solution (since you have to disassemble each AppleGVA.framework received from OS update and patch it differently all the time)
Launch the software you need via terminal like this:

DYLD_SHARED_REGION=avoid /path/to/program.app/Contents/MacOS/program

Have most common software added to Shiki, so that it patches it automatically until a proper solution is implemented. This one is probably not so bad, but you need to tell me the software you need with absolute paths to executables.

Thanks for the workarounds! I accidentally found it working by force updating dyld_shared_cache (sudo update_dyld_shared_cache -force). After rebooting, VDADecoderChecker produced the following result:
GVA info: Successfully connected to the Intel plugin, offline Gen9
Hardware acceleration is fully supported
I believe hardware acceleration is somehow working right now (tested with IINA). However, streaming videos from Apple Music still doesn't work and it breaks Netflix video. I will try the workarounds you provided and run more testings.

Alright, I guess I will close it for now then.

I have the exactly same issue, unfortunately updating dyld_shared_cache does not work for me, I need to replace a patched AppleGVA.framework


[Bug] Property 'default 'does not exist on type '{}' when using CldUploadWidget let:open

Bug Report
When following the video tutorial at Svelte Cloudinary Upload Widget site, an error occurred in Visual Studio Code with the following:
Property 'default' does not exist on type '{}'.ts(2339)
const open: any

Though the website actually works fine and the code to upload image to cloudinary works perfectly, the code however produces a warning that is shown by the Visual Studio Code.

Is this a regression?

I am not too sure.
Steps To Reproduce the error

Here is the code snippet of my current code:
<script lang="ts">
    import type { PageData } from './$types';
    import { Button } from '$lib/components/ui/button';
    import { Input } from '$lib/components/ui/input'
    import * as Form from '$lib/components/ui/form';
    import SuperDebug, { superForm } from 'sveltekit-superforms';
    import { toast } from 'svelte-sonner';
    import { goto } from '$app/navigation';
    import { formSchema } from './schema';
    import { zodClient } from 'sveltekit-superforms/adapters';
    import FormField from '$lib/components/ui/form/form-field.svelte';
    import { FormInput } from 'lucide-svelte';
    import { CldUploadButton, CldUploadWidget, CldImage, getCldImageUrl } from 'svelte-cloudinary';

const onUpload = (result:any, widget:any) => {
        // onChange(result.info.secure_url);
        if (result.event == "success") {
            info = result.info;
            secure_url = result.info.secure_url
            toast.success('Upload image to CLOUD successful!');
            $formData.link = result.info.secure_url
        } else if (result.event === "error") {
            error = result.error.status
        }
        widget.close()
    };

</script>

. . . .

        <CldUploadWidget uploadPreset={uploadPresetKey} {onUpload} let:open>
            <Button on:click={open}>
                Upload Test
            </Button>
        </CldUploadWidget>

Expected behaviour

I expected that because of the warning from the Visual Studio Code, the bug makes the actual button not usable, but instead it actually works fine as intended like in the video without any problems. The Visual Studio Code was just showing an error, but the code itself works? I have no idea how that works.
Screenshot or Video Recording

Your environment

OS: Windows 11 Version 23H2 (OS Build 22631.3447) x64
Node version: v.20.12.1
bun version: v1.1.4
Browser name and version: Microsoft Edge 124.0.2478.67 (Official build) (64-bit)

Unfortunately some types are a little broken in v1. I'm working on v2 at the moment which fixes all of these bugs, so will keep this open for tracking :pray:

Will be released in #112


VSCode build is broken

see https://code.visualstudio.com/docs/python/environments#_environment-variable-definitions-file
and https://github.com/microsoft/vscode-python/wiki/Activate-Environments-in-Terminal-Using-Environment-Variables
First problem: python venv is now loaded before build commands are issued. And buildenv refuses to run since already executed from a venv.
Second problem: activation scripts are not executed anymore, so it breaks the buildenv paradigm. Typically completion setup is not executed, etc...

See also how to integrate vscode shell script
https://code.visualstudio.com/docs/terminal/shell-integration
Maybe in another buildenv extension?


Module parse failed: Unexpected token (161:57)

Bug Report

Module parse failed: Unexpected token (161:57)
You may need an additional loader to handle the result of these loaders.

Describe the bug

React compile error after installing the library

Minimal Reproduction

fresh install yarn add yahoo-finance2

Environment
Browser or Node: Node
Node version (if applicable):  v15.6.0
Npm version: 7.4.0
Library version (e.g. 1.10.1):  1.14.4
Additional Context
error
ReactJS       | ./node_modules/yahoo-finance2/dist/esm/src/lib/validateAndCoerceTypes.js 161:57 ReactJS       | Module parse failed: Unexpected token (161:57) ReactJS       | File was processed with these loaders: ReactJS       |  * ./node_modules/react-scripts/node_modules/babel-loader/lib/index.js ReactJS       | You may need an additional loader to handle the result of these loaders. ReactJS       | | /* istanbul ignore next */ ReactJS       | |  ReactJS       | > const logObj = typeof process !== "undefined" && process?.stdout?.isTTY ? obj => console.dir(obj, { ReactJS       | |   depth: 4, ReactJS       | |   colors: true

I have same issue when using Vue.js. I guess babel help this problem but I don't know how exactly.


[Snyk] Upgrade markdown-to-jsx from 7.4.5 to 7.4.7

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade markdown-to-jsx from 7.4.5 to 7.4.7.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 2 versions ahead of your current version.
The recommended version was released 22 days ago, on 2024-04-13.

Release notes

Package name: markdown-to-jsx

7.4.7 - 2024-04-13Patch Changes

7603248: Fix parsing isolation of individual table cells.
f9328cc: Improved block html detection regex to handle certain edge cases that cause extreme slowness. Thank you @ devbrains-com for the basis for this fix 🤝

7.4.6 - 2024-04-05Patch Changes

a9e5276: Browsers assign element with id to the global scope using the value as the variable name. E.g.:
 can be referenced via window.analytics.
This can be a problem when a name conflict happens. For instance, pages that expect analytics.push() to be a function will stop working if the an element with an id of analytics exists in the page.
In this change, we export the slugify function so that users can easily augment it.
This can be used to avoid variable name conflicts by giving the element a different id.
import { slugify } from 'markdown-to-jsx';
options={{
slugify: str => {
let result = slugify(str)
return result ? '-' + str : result;

}
}}

7.4.5 - 2024-03-22Patch Changes

f5a0079: fix: double newline between consecutive blockquote syntax creates separate blockquotes
Previously, for consecutive blockquotes they were rendered as one:
Input
> Block A.1
> Block A.2

> Block B.1
Output

Block A.1

Block A.2

Block.B.1

This is not compliant with the GFM spec which states that consecutive blocks should be created if there is a blank line between them.

    from markdown-to-jsx GitHub release notes

Commit messages

Package name: markdown-to-jsx

acd970d Version Packages (#571)
a502174 fix: handle incomplete table-like syntax better
7603248 fix: table cell parsing isolation
f9328cc fix: adjusted block html regex to avoid perf issues
dcc457e chore: revert prettier
ede3cd8 Version Packages (#567)
a9e5276 Export `slugify` function (#566)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

https://github.com/DTS-STN/secure-client-hub/pull/641


Add a visual representation of data assessment to the section

here it would be great to have a visual on how this mapping looks in practice, as an example

Added! c4be9e5
https://github.com/OpenInternet/SAFETAG/blob/master/content/adids/data_assessment/backup-matrix-example.png


Creating container DO NOT need runtime anymore in kata-shim-v2?

Since kata support containerd shimv2 API #572, creating a container via kata-shim-v2 do not need kata-runtime anymore, but i don't think this is a good idea. It breaks the containerd original architecture. see https://github.com/crosbymichael/dockercon-2016/blob/master/Creating Containerd.pdf
I did some test by kata-shim-v2, it will cause zombie process in container because kata-shim-v2 does not listen SIGCHLD and reap child process. The reason there is zombie in container maybe kata-agent not set CHILD SUBREAPER, So It is not associated with kata-shim-v2, my bad.

Hi @BetaXOi, Any comments?

Hi @BetaXOi, I spent some time to investigate this issue, and found that:
1: kata agent does set CHILD SUBREAPER in https://github.com/kata-containers/agent/blob/ca9d52094d41af3e43f41b88388e9ce11222c8c6/agent.go#L626
2: For the zombie issue, it's latest's kernel feature, not a bug.
In fact, you can also reproduce the zombie process in runC with host kernel later than 4.11.
and what you had saw on runC without the zombie process must be on the kernel older than 4.11.
What triggered this difference is this kernel patch: https://lkml.org/lkml/2017/1/30/630
I think you had misunderstood the kernel's feature  "CHILD SUBREAPER".  Actually The child subreaper cannot
reap a child from different pid namespace. Read from the latest kernel source codes https://elixir.bootlin.com/linux/latest/source/kernel/exit.c#L603, the logic to find a process's reaper is below:

give them to another thread in it's parent's  thread group, if such a member exists.
give it to the first ancestor process which prctl'd itself as a
child_subreaper for its children in the same pid namespace.
give it to the init process (PID 1) in our pid namespace

That's why kernel reparent the child process to container's (PID 1) process instead of the shim/kata-agent process.
@bergwolf  @gnawux @sboeuf  WDYT?

Thanks for the clarification, @lifupan.
Yes, as @lifupan said,  it's a feature, it's not a bug 😂
The zombies are caused by abusing of the kernel defect which has been fixed in new kernels, and they are not related to any kata features.
However, as there are users depending on the fixed behavior, I think we should document this case at least.

@BetaXOi
but i don't think this is a good idea. It breaks the containerd original architecture. see https://github.com/crosbymichael/dockercon-2016/blob/master/Creating Containerd.pdf

What you referenced was presented in 2016, and the shimv2 was introduced in containerd in 2018 ( containerd/containerd#2434), and the containerd PR was self-documented.
In the issue #485, which was implemented in #572, we discussed with containerd guys including Michael Crosby and made sure the implementation followed the latest containerd principles and architecture. The future runtimes were encouraged to implement the shimv2 API instead of the non-standard and too process dedicated runC compatible command line interface.
Hope my words could help you understand where the shimv2 came from, @BetaXOi .


Q.when() is not resolved synchronously while Q() is

I have a code similar to this in one of my tests.
var Q=require('q');

var staticWhen=Q.when(1);
var staticQ=Q(1);

function printStatusInfo(prom){
    console.log(prom.isPending());
    console.log(prom.isFulfilled());
    console.log(prom.inspect());
}

printStatusInfo(staticWhen);
printStatusInfo(staticQ);

and this outputs
staticWhen
true
false
{ state: 'pending' }

staticQ
false
true
{ state: 'fulfilled', value: 1 }

Only if you wait for the next tick you can have the static when promise fulfilled, while the static Q is fulfilled from the beginning.
I think this can be a problem if you substitute Q.when() for Q(), for example in a test that synchronously assert that the promise is fulfilled. Maybe it should be pointed in the docu that they behave differently in this case, because in the first paragraph of the reference says that they are equivalent.

Hmm the docs first paragraph sais Q.when(X,Y) is equivalent to Q(X).then(Y). That is slighly different from saying Q.when(X) is equivalent to Q(X). It also states:

which will accept either a promise or a non-promise, and in the latter case create a fulfilled promise first

Maybe you can help me understand: If it is known that .then(Y) is fulfilled on the next tick then that means Q(X) has to be instantanious? So the behaviour can't change under those conditions? Because in my limited understanding making Q.(X) pending would make Q(X).then(Y) take two ticks... I'm not sure if that is accurate or if that is even breaking any expectations.
Have you checked whether Q(X).then() behaves equivalent to Q.when(X)?
I agree a clarification would be in order because neither the main readme nor the wiki docs are clear on the expected behaviour of when(X), only when(X,Y) is clearly defined right now.


Moving: VivaldiTechnologies.Vivaldi version 6.5.3206.48

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest

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

Microsoft Reviewers: Open in CodeFlow

Sequence contains no elements

https://github.com/microsoft/winget-pkgs/issues/133371

(Automated response - build 655.)

Automatic Validation ended with:

2024-01-25T09:43:44.0141484Z Processing manifest: manifests\v\VivaldiTechnologies\Vivaldi\6.5.3206.48
2024-01-25T09:43:44.0151073Z -----------------------------------------------------
2024-01-25T09:43:44.0157319Z Status: Started
2024-01-25T09:43:44.0165436Z Manifest file is Deleted
2024-01-25T09:43:45.0449190Z Status: Completed
2024-01-25T09:43:45.0450365Z ##[error] Result: Failed
2024-01-25T09:43:45.0452474Z ##[error] Sequence contains no elements
2024-01-25T09:43:45.0454514Z ##[error]Manifest Validation Failed

(Automated response - build 655.)

@wingetbot run

Sequence contains no elements

https://github.com/microsoft/winget-pkgs/issues/133371

(Automated response - build 657.)


Question about moving children out of elements and remark about non ES6 syntax

Now we have this in all app components.
My question, is there a reason behind moving children out of the element and then removing that element? This seems detrimental to the initial performance (while the idea may have been to make a dom tree more shallow for future performance, correct me if I'm wrong)

Also, linter immediately complains about these things (these are just some remarks, I'm not complaining):

If you are using ngOnInit() in the component, the class must implement OnInit interface
All component class names must be suffixed with Component
If variables are not reassigned, you should use const instead of var (actually, you should never use var nowadays)

So, I fixed up the class and ended up with this:

Thank you for your feedback. We use this because we face problems with angular tags and flex layout.
We improve this functions in next release.

In release 1.0.2 the ngOnInit() function was removed in the components, but styles was not updated, so now the layout is pretty messed up. That because the parent of component with flex layout (for example app-footer) has not display: flex property.

I briefly checked the diff of the latest commit and it seems to be moving in the right direction. I will try to pull the seed project and check it out my self in a couple of days.


Reduce vertex count in distortion mesh construction by using indexing

The distortion-mesh calculations in ComputeDistortionMesh() produce a set of vertices for triangles, which means that there are about 6 times as many vertices as needed.  This slows down the calculations of unstructured mesh inputs by calling DistortionCorrectTextureCoordinate() 6 times as often as needed.
Another approach would be to return both a vertex vector and an index vector and then use index buffers to specify the vertices multiple times.  This will require updates to RenderManagerD3DBase.cpp and RenderManagerOpenGL.cpp to make use of the indexed mesh types.

Fixed by mdutton3, merged into master and in commit b46e9fc173a502cfaf6e122f18ef2d9c15944f85


(PDB-1034) Remove old packaging system

DO NOT MERGE: this is simply for review now, we'll need to get the ezbake source stuff working before this can be merged.
This removes the old packaging system and its files.

I'm going to stop the PR testing on this one, because I know it will fail.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/548/

I'm going to bundle this into the main patch, as a separate commit for visibility.


Update wiki

https://github.com/monarch-initiative/MAxO/wiki/DOSDP-pattern-creation-and-edits
@LCCarmody  @matentzn
can we delete the struck through text here?
e.g.
RUN RELEASE

Of course! I removed that specific instance. Just delete whatever you don't need but for the future:
don't use wikis.. Just use the normal mkdocs pattern we use everywhere. This way, we have histories of our documentation and can retrieve past edits if ever necessary.. No need to make a move now!

Thanks. Closing issue. Will change to mkdocs in the future.


Add German translations

Add German translations for #78.

Danke schön! I appreciate your contribution.

No problem! Thanks for making such an awesome extension!


SSLv3 errors

I've experienced issues regarding ssl on py2.7, py3.4.3, py 3.5. Its fixed on pypy3.2.4 though.
Is there a clean way to do it?

7 year later, I guess that this is outdated so I'm closing this one.

🤣🎉


Made minor formatting correction in readme; added folder containing i…

…mages for the wiki.

Looks good. Thanks


Add upper-level domain for ESTIA

Master of Science BIHAR, Big Data & AI: https://www.estia.fr/formations/formations-longues-diplomantes/msc-bihar
Engineering Degree: https://www.estia.fr/formations/ingenieur-generaliste-international

@eishkina-estia Thank you for your patience while waiting for a review and processing your request. Pull request merged.


[7.0] No available engine for Illuminate\Database\Eloquent\Relations\BelongsToMany

Summary of problem or feature request
When using a BelongsToMany relation, I get a "No available engine for Illuminate\Database\Eloquent\Relations\BelongsToMany" error.

Code snippet of problem
Datatables code that works:
 return Datatables::of(TargetList::findOrFail($id)->users())->make(true);

I get this error with:
public function users()
    {
        return $this->belongsToMany('App\TargetUser');
    }

I don't get an error if I change that to:
public function users()
    {
        $ids = \DB::table('target_list_target_user')->where('target_list_id', '=', $this->id)->pluck('target_user_id');
        return TargetUser::where('hidden', false)->whereIn('id', $ids);
    }

System details
Ubuntu 16.04, PHP 7.0, Laravel 5.4, Laravel-Datatables 7.0

Can you try adding this line on datatables.php config and check if it works?
'builders' => [
    Illuminate\Database\Eloquent\Relations\BelongsToMany::class => 'eloquent',
    ...
]

Or maybe lets use the Relation class so that it will handle any relations?
Can you please also try removing:
Illuminate\Database\Eloquent\Relations\BelongsToMany::class => 'eloquent',

and replace it with
Illuminate\Database\Eloquent\Relations\Relation::class => 'eloquent',

Please update to v7.0.2 and force publish the config. Thanks!


Unexpected assertion fail for union type with optional fields

📝 Summary
Type equality (assert, is, etc.) with certain union objects with optional fields is parsed as non-equal.

Typia Version: 5.3.0-dev.20231127-2
Expected behavior: Typia should select the correct object for matching
Actual behavior: Typia decides the object does not match the intersection type.

interface A {
	name?: "A";
	someBool: true;
}
interface B {
	name?: "B";
	someBool: boolean | undefined;
}

It seems that Typia only validates that the body matches A and doesn't check whether it matches B. This problem resolves itself if someBool is required as non-undefined, or if name is required.
I believe that A | B (see below) should match given that TypeScript doesn't have any issues with the following:
const body = {
	name: "B",
	someBool: true,
} satisfies A | B;

⏯ Playground Link
💻 Code occuring the bug
import typia from "typia";

interface A {
	name?: "A";
	someBool: true;
}
interface A_NonOptional {
	name: "A";
	someBool: true;
}
interface B {
	name?: "B";
	someBool: boolean | undefined;
}
interface C {
	name?: "C";
	someBool: boolean;
}

// Throws (Incorrect; should match B)
const A_and_B = typia.assert<A | B>({
	name: "B",
	someBool: true,
});

// Doesn't throw (Correct)
const A_NonOptional_and_B = typia.assert<A_NonOptional | B>({
	name: "B",
	someBool: true,
});

// Doesn't throw (Correct)
const A_and_C = typia.assert<A | C>({
	name: "C",
	someBool: true,
});

Succeeded to fix this bug.
Will try to fix #885 bug, but if needs lots of time, then will publish immediately.
Thanks for reporting.


AST: Canonicalize types with respect to generic signature when mangling

In the following example, the two declarations should have
the same mangled type:
protocol P {
  associatedtype P
}

func f1<T : P>(_: T) -> T.P where T.P == Int {}
func f2<T : P>(_: T) -> Int where T.P == Int {}

To ensure this is the case, canonicalize the entire
GenericFunctionType before taking it apart, instead of
canonicalizing structural components of it.

@swift-ci Please smoke test

@bitjammer I think the test failure might be your changes?

Yes, that was me. I already fixed this, though? I cherry-picked my change to the swift-4.0-branch and stable branch. Hm ... looking.

Yeah, that was https://github.com/apple/swift-lldb/commit/991790c9ae10790639752dd3df05812f1e0a85a6 . It looks like it's checking out the stable branch, too.

@swift-ci Please smoke test Linux

Huh. I'm amazed we didn't notice this before. Thanks!


SSIM calculation mistake.

https://github.com/Lightning-AI/torchmetrics/blob/a31417ca1bc4a47ca093c22e3f2f2b5e6843d58a/src/torchmetrics/functional/image/ssim.py#L164C1-L170C72
Before the convolution, we already applied same padding to the image
        preds = F.pad(preds, (pad_w, pad_w, pad_h, pad_h), mode="reflect")
        target = F.pad(target, (pad_w, pad_w, pad_h, pad_h), mode="reflect")

So ssim_idx_full_image will share the same shape as original image, there is no need to take the padding out again, otherwise it will result in losing information on edge.
    ssim_idx_full_image = ((2 * mu_pred_target + c1) * upper) / ((mu_pred_sq + mu_target_sq + c1) * lower)

    if is_3d:
        ssim_idx = ssim_idx_full_image[..., pad_h:-pad_h, pad_w:-pad_w, pad_d:-pad_d]
    else:
        ssim_idx = ssim_idx_full_image[..., pad_h:-pad_h, pad_w:-pad_w]

Also, the kernal_size is a input parameter while gauss_kernel_size is calculated based on input parameter sigma. If we call the function without gaussian kernel, the padding size will still calculated based on gauss_kernel_size rather than kernal_size.
    gauss_kernel_size = [int(3.5 * s + 0.5) * 2 + 1 for s in sigma]

    pad_h = (gauss_kernel_size[0] - 1) // 2
    pad_w = (gauss_kernel_size[1] - 1) // 2

Hi @petertheprocess, thanks for raising this issue.
It does seem like both are errors. Feel free to create a PR correcting this :)


Adding a new rebus

Associated Issue: #
Summary of Changes

change 1
Adding a new rebus "cupcake"  | #182

Pull Request Test Coverage Report for Build 987

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

Totals

Change from base Build 937:
0.0%

Covered Lines:
158

Relevant Lines:
180

💛  - Coveralls

Done!


how about dsp effects

have you considered adding dsp to the equalizer ?

Digital Signal Processing is a very large area of study that has many implications on fields like audio, so you'll have to be more specific about what you're thinking about. Assuming you're just referring to audio effects in general, the only feature I'm planning to look into at this time is a Virtualizer.


Implement DefaultHeaders.HeaderEntry.equals()

Motivation:
HeaderEntry.equals() inherets Object.equals() which simply check if two objects are the same.
So it returns false even when two HeaderEntry objects have the same name and value.
Modifications:
Implement HeaderEntry.equals() that follows the specification of Map.Entry.equals().
https://docs.oracle.com/javase/9/docs/api/java/util/Map.Entry.html#equals-java.lang.Object-
Result:
HeaderEntry.equals() returns true if two HeaderEntry objects have the same name and value.

@ryu1-sakai please fix check style error and ping me once done.

@normanmaurer fixed the following error. Thanks!
DefaultHeaders.java:1180:42: 'cast' is not followed by whitespace.

@ryu1-sakai did you sign our ICLA ?: https://netty.io/s/icla

@normanmaurer ICLA also done. Thank you for the instruction.

@normanmaurer I made the following two modifications

s/Map.Entry/Map.Entry<?, ?>/
Added asserts for the hashCode() to the test

Cherry-picked into 4.1 (c1d0d88f0ae50ce38f00daa9bf7039c1a8bf9a80).
@ryu1-sakai thanks!

Simply followed the Map.Entry.hashCode() specification
https://docs.oracle.com/javase/9/docs/api/java/util/Map.Entry.html#hashCode--


Query for events in last 5min only

Hi, wondering if theres a way to limit alerts for events that occured in last 5 min only
right now my rule is querying an index, and its pulling thousands of hits, but these are historical
is there any way to limit search to current timestamp minus 5 min? Cant figure out how to limit the search timeframe to last X min,
name: SDP DEV - errors
is_enabled: false

# Alert on x events in y seconds
type: frequency

# Alert when this many documents matching the query occur within a timeframe
num_events: 1

# num_events must occur within this amount of time to trigger an alert
timeframe:
  minutes: 5

filter:
- query:
    query_string:
      query: |
        host.hostname:web05 AND (log.file.path:*MessagingService*.log OR log.file.path:*general.log)
        AND (message:"*ERROR*" OR message:"*error*" OR message:"*Error*")

index: filebeat-*

# if errors continue send a new alert after x minutes
realert:
  minutes: 0

query_key:
  - log.file.path

look
https://github.com/Yelp/elastalert/issues/3178


Cleaned up model, added proper units

Company Info

Avnet
avnet.com
https://github.com/Avnet

IoT Plug and Play Device Info

Avnet Azure Sphere Starter Kit
Azure Sphere MCU
Azure Sphere SDK

Model Submission Goals

Device certification
Presence in the Certified Device catalog
IoT Central integration
Demo applications for Azure Sphere Workshop students

Code Owners & Reserved Names

@bawilless

Note on this PR
You can just take the new file (overwrite the old file), no need to merge.  The interfaces have not changed, so the version has not changed.

If you can delete the rev1 file, that would be good.  It's not proper DTDL V2.

If you can delete the rev1 file, that would be good.  It's not proper DTDL V2.

@bawilless we cannot delete interfaces that have been already been merged.

@bawilless we cannot delete interfaces that have been already been merged.


Make deprecation warning actionable

As it currently stands, this deprecation warning is un-actionable. The warning suggests a way to "resolve" the deprecation but that's not exactly right.

@wpolicarpo @packrat386 @philostler Sorry for the ping but the PRs are looking stale. Also #110 could be merged as part of this. Happy to help maintain if you guys are too busy.

Coverage decreased (-5.8%) to 91.389% when pulling e9b119030ea7a8b9bd3316399626c99ea1ffde9e on trev:actionable-deprecation into 4f6da310f2311aa2d5bbea983bd17776d041c61a on philostler:develop.

Coverage decreased (-5.8%) to 91.389% when pulling e9b119030ea7a8b9bd3316399626c99ea1ffde9e on trev:actionable-deprecation into 4f6da310f2311aa2d5bbea983bd17776d041c61a on philostler:develop.

Coverage decreased (-5.8%) to 91.389% when pulling 4e8c48d6ec9cbaccbe20341fb8606e828db800f0 on trev:actionable-deprecation into 4f6da310f2311aa2d5bbea983bd17776d041c61a on philostler:develop.

Coverage decreased (-5.8%) to 91.389% when pulling 4e8c48d6ec9cbaccbe20341fb8606e828db800f0 on trev:actionable-deprecation into 4f6da310f2311aa2d5bbea983bd17776d041c61a on philostler:develop.

Coverage decreased (-5.8%) to 91.389% when pulling b8995b05e9ad9fa02794ca479ba0e2c7277da99d on trev:actionable-deprecation into 4f6da310f2311aa2d5bbea983bd17776d041c61a on philostler:develop.

Coverage increased (+0.3%) to 97.5% when pulling 7433d0ffd96a3aaa9e6def8694ee18cad0811c47 on trev:actionable-deprecation into 4f6da310f2311aa2d5bbea983bd17776d041c61a on philostler:develop.

The tests are failing on Ruby < 2.2 because Sidekiq 5+ requires Ruby >= 2.2.2.
What I suggest we do is:

Adjust this PR so that it's only using Sidekiq < 5.0.0 and only has the deprecation change and patch version bump: https://github.com/philostler/rspec-sidekiq/pull/126/commits/e9b119030ea7a8b9bd3316399626c99ea1ffde9e & https://github.com/philostler/rspec-sidekiq/pull/126/commits/b8995b05e9ad9fa02794ca479ba0e2c7277da99d
Create a new PR that removes the deprecation warning and makes have_enqueued_sidekiq_job the default, update gem dependencies to use latest Sidekiq, remove support for Ruby < 2.2.2 and finally bump version to 4.0.0

If that sounds good, let me know and I'll affect the changes.

@wpolicarpo @packrat386 @philostler Sorry to ping again. A 👍  or 👎  would be great if my previous message sound reasonable.

This looks good, thanks @trev!
Anything we can do/help with to get this shipped?

Hey @tisba, I'm happy to affect the changes as it's a quick easy job but I can't get any of the maintainers to get back to me. I've emailed them as well. @wpolicarpo @packrat386 @philostler -- ping again :)

On that note, do you have any objection to me just merging #128, it seems like those 2 PRs do the same thing.

@packrat386 I took the best of both worlds as his PR was missing stuff https://github.com/philostler/rspec-sidekiq/pull/131

Closing in favour of #130 #131 & #132 which once merged together will result in passing tests and resolve multiple issues.


Search in selection

(Originally referenced from #89)
One thing I use a lot in Sublime Text is replacing all instances of some text inside the selection (e.g. copy a chunk of HTML, change specific bits on the new copy).
What would the equivalent of that be in Zed? I guess a command that limits the search to the selection would do the trick; then Find:All and I'm good.

Coming from vim I'm missing this functionality as well, and I'm on board with the suggested solution above.


WIP 14 feat user profile

Implements/Fixes(DELETE THE WRONG ONE) #
If your PR is not WIP, Please check if your PR fulfills these requirements

[ ] The PR title follows the guidelines

Which part of the project does this PR belongs to ?
What is the current behavior ?
Does this PR introduce a breaking change ?
Other information

i dont even know what you are doing


Manifests for deployment on "any" Kubernetes cluster (i.e. minikube)

As an admin I want to be able to deploy kubevirt with a simple kubectl command

KubeVirt aims to be a Kubernetes add-on. As a first step it hould be possible to deploy KubeVirt to an existing cluster using a single kubectl command call.
I.e. like
kubectl apply kubevirt.io/kubevirt.yaml

We might want to have automation which is creating manifests based on the manifests from the main repository.

Issues to track, to accomplishe this:

Support arbitrary namespaces: #249
Add permissions to the deployment yamls: #301
Move kubevirt components into their own namespace: #300

Also looking into this (ansible + openshift + kubernetes addon stack).

Another issue, interesting for consistent KubeVirt bootstrapping is #314 , though not necessarily related to that task.

The ongoing effort for deployment can be seen in these repositories:

https://github.com/petrkotas/openshift-env
https://github.com/cynepco3hahue/kubevirt-ansible

And on adams blog:

http://adam.younglogic.com/2017/06/kubevirt-on-origin/
https://adam.younglogic.com/2017/08/custom-kubevirt-manifests/
http://adam.younglogic.com/2017/08/deploying-kubevirt-on-origin-master/


don't export ErrorView element at top level, we don't want to break Atom

Codecov Report

Merging #86 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #86   +/-   ##
=======================================
  Coverage   89.96%   89.96%
=======================================
  Files          18       18
  Lines         299      299
=======================================
  Hits          269      269
  Misses         30       30

Continue to review full report at Codecov.

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


*feat: Implemented Callback Business Logic

Documentation of Log-Messages for CDC is still missing and needs to be added.

Log message documentation has been added


Need more details about SBC logs

It's cool that the doc says, refer to the SBC Logs. I am new to all of this and don't have a clue about where I can find SBC logs. I gather that they may be Session Border Controller logs, and they may be located there.... by where (directory) etc.?

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

ID: 9374347d-42cb-4955-6eac-3efd04eef66d
Version Independent ID: 985dbd00-b456-13c3-5928-b423084d3a87
Content: Monitor and troubleshoot Direct Routing
Content Source: Teams/direct-routing-monitor-and-troubleshoot.md
Service: msteams
GitHub Login: @CarolynRowe
Microsoft Alias: crowe

@Jmartinez589  Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@Jmartinez589 the SBCs are a piece of hardware, they should save their files like the routers does, so I think they handle its own logs files.
Here's a list of supported:
https://docs.microsoft.com/en-us/microsoftteams/direct-routing-border-controllers

@Jmartinez589  Thank you for submitting feedback and contributing to the docs. We are currently investigating this.


use getUser instead of listUsers

BACKEND PULL REQUEST
Related Issue

Currently we are performing listUsers to fetch a single user given their email, but there is getUser available to fetch a single user given you have either the user id or the login username (email).

Changes Proposed

Replace all listUsers with getUser, which should be up to date immediately unlikelistUsers

Additional Information
Testing

Deployed on dev7 with Johanna's changes with undelete user to refetch the user.

https://github.com/CDCgov/prime-simplereport/assets/10108172/db6e5b6f-03b3-49d5-a9d6-536f4a856cb6

Ohhh this is what you were trying to explain that day? So this will return the user information without the delay of record issue?

Ohhh this is what you were trying to explain that day? So this will return the user information without the delay of record issue?

This is something new I learned on Friday, but yes this will return user information immediately.


Regex filter

I'd like to filter some posts based on the title, as they're activities or events with specific formats.
This will be easier to do with a way to configure multiple regex to filter the posts of a sub.

For now it's possible to filter urls with regex, check https://github.com/daniel-lxs/BotIt#readme


Question on 'disable' for search engines

Are we disabling for the site or for the search query?

Do you see a "disable" button?
There should always be a "Disable for this site" button and also a "Disable for this search" button for search engines if the current search is triggering a block.

So I think it is happening is that b/c the search engine itself is blocked, one never sees the 'disable for this search' button, even if the search would be blocked itself. Is that correct?

You can only see "disable for this search" button if the search query is a match with our list.
But this button is not visible, for example, if you search "credit card" on google, because the search itself can't trigger a block.

Right, but for the case where BOTH the site and query are blocked, one sees only the 'disable for this site' button

Can you provide your search link? I can still see "disable for this search" if I change my search engine to google.com.hk

https://www.google.com.hk/search?ei=FvwNWry3MIKy0ATn-6DoBg&q=grass+mud+horse+&oq=grass+mud+horse

For the link above, the issue seems be caused by the extra "+" before "oq=grass+mud+horse"
Please check the fix here: https://github.com/dhowe/ChinaEye/pull/74


Include DNS Configuration for the domain

Hi
I'm getting errors when joindomain extension runs
I googled and lots of others are having same issue.
Please include this as well in this tutorial so others don't get into this trap
Thanks
Maqsood

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

ID: 970202b7-165f-18df-e928-c47c45a18755
Version Independent ID: d5393b62-4211-72f5-fc7a-363f68f6d8a2
Content: Windows Virtual Desktop host pool Azure portal - Azure
Content Source: articles/virtual-desktop/create-host-pools-azure-marketplace.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

@maqsoodahmad
Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.

@maqsoodahmad
Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.

@Heidilohr
Can you please check and add your comments on this doc update request as applicable.

@Heidilohr
Can you please check and add your comments on this doc update request as applicable.

Thanks for the feedback. We do have this sentence: "The DNS servers of the virtual network you selected should be configured to use the IP of the domain controller" and in the Prerequisites article (https://docs.microsoft.com/en-us/azure/virtual-desktop/prerequisites) "Make sure this virtual network can connect to your domain controllers and relevant DNS servers if you're using AD DS or Azure AD DS, since you'll need to join session hosts to the domain."
#please-close


Show the Custodian error message rather than the vague ASE message upon VASP errors

What new feature would you like to see?
When Custodian can't fix a VASP run, the job fails as expected. However, ASE returns an extremely vague message (just reporting the error code) rather than the Custodian error data from stderr. An example is shown below. It would be more convenient if the full Custodian error log were displayed on VASP failures.
File /global/common/software/matgen/rosen/miniconda/envs/quacc/lib/python3.10/site-packages/quacc/recipes/vasp/core.py:255, in _base_job()
    252 flags = merge_dicts(defaults, calc_swaps, remove_nones=False)
    254 atoms.calc = Vasp(atoms, preset=preset, **flags)
--> 255 atoms = run_calc(atoms, copy_files=copy_files)
    257 return vasp_summarize_run(atoms, additional_fields=additional_fields)

File /global/common/software/matgen/rosen/miniconda/envs/quacc/lib/python3.10/site-packages/quacc/runners/calc.py:68, in run_calc()
     65 atoms, tmpdir, job_results_dir = _calc_setup(atoms, copy_files=copy_files)
     67 # Run calculation via get_potential_energy()
---> 68 atoms.get_potential_energy()
     70 # Most ASE calculators do not update the atoms object in-place with a call
     71 # to .get_potential_energy(), which is important if an internal optimizer is
     72 # used. This section is done to ensure that the atoms object is updated with
     73 # the correct positions and cell if a `geom_file` is provided.
     74 if geom_file:
     75     # Note: We have to be careful to make sure we don't lose the converged
     76     # magnetic moments, if present. That's why we simply update the
     77     # positions and cell in-place.

File /global/common/software/matgen/rosen/miniconda/envs/quacc/lib/python3.10/site-packages/ase/atoms.py:730, in get_potential_energy()
    727     energy = self._calc.get_potential_energy(
    728         self, force_consistent=force_consistent)
    729 else:
--> 730     energy = self._calc.get_potential_energy(self)
    731 if apply_constraint:
    732     for constraint in self.constraints:

File /global/common/software/matgen/rosen/miniconda/envs/quacc/lib/python3.10/site-packages/ase/calculators/abc.py:24, in get_potential_energy()
     22 else:
     23     name = 'energy'
---> 24 return self.get_property(name, atoms)

File /global/common/software/matgen/rosen/miniconda/envs/quacc/lib/python3.10/site-packages/ase/calculators/calculator.py:502, in get_property()
    499     if self.use_cache:
    500         self.atoms = atoms.copy()
--> 502     self.calculate(atoms, [name], system_changes)
    504 if name not in self.results:
    505     # For some reason the calculator was not able to do what we want,
    506     # and that is OK.
    507     raise PropertyNotImplementedError('{} not present in this '
    508                                       'calculation'.format(name))

File /global/common/software/matgen/rosen/miniconda/envs/quacc/lib/python3.10/site-packages/ase/calculators/vasp/vasp.py:326, in calculate()
    321     errorcode = self._run(command=command,
    322                           out=out,
    323                           directory=self.directory)
    325 if errorcode:
--> 326     raise calculator.CalculationFailed(
    327         '{} in {} returned an error: {:d}'.format(
    328             self.name, self.directory, errorcode))
    330 # Read results from calculation
    331 self.update_atoms(atoms)

CalculationFailed: vasp in . returned an error: 1
```

This has to be patched upstream in ASE...


Can not disable security component

Bug description
If disable security component with --set security.enabled=false option, the citadel deployment will not be created, which makes istio.io/key-and-cert controller not running.
Almost all components mount secret to /etc/certs created by citadel. So, if citadel not running, other components got an error for starting.
I think it is a bug.
Affected product area (please put an X in all that apply)
[ ] Configuration Infrastructure
[ ] Docs
[X] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[X] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
Other components work well without citadel.
Steps to reproduce the bug
helm template ./istio --set security.enabled=false --namespace istio-system
[root@kebe-dev-m1 ~]# kubectl -n istio-system describe po istio-galley-f4fcb5dc4-mkvp5
...
Events:
  Type     Reason       Age               From                  Message
  ----     ------       ----              ----                  -------
  Normal   Scheduled    25s               default-scheduler     Successfully assigned istio-system/istio-galley-f4fcb5dc4-mkvp5 to kebe-dev-n1
  Warning  FailedMount  9s (x6 over 24s)  kubelet, kebe-dev-n1  MountVolume.SetUp failed for volume "certs" : secret "istio.istio-galley-service-account" not found

Version (include the output of istioctl version --remote and kubectl version)
istio 1.3.0 kubernetes 1.15.3
How was Istio installed?
helm
Environment where bug was observed (cloud vendor, OS, etc)
Additionally, please consider attaching a cluster state archive by attaching
the dump file to this issue.

This seems working as intended. Its not clear what is expected - you disabled citadel and things that depend on citadel stopped working. Please reopen with more info if there is more details you can provide

@howardjohn I ran into this with a minimal install of only pilot and the sidecar injector; the sidecar injector fails for the same reason as galley above. I'm very new to Istio, but that was unexpected behavior based on my grasp of what the sidecar injector is doing.
It looks istio/install is tackling some of these things (e.g. https://github.com/istio/installer/blob/master/istio-control/istio-autoinject/values.yaml#L21-L24 for the sidecar injector), but as someone new to istio I'm finding it tough to determine what does depend on citadel and what doesn't.

@pinkertonpg please see the minimal example values file. You can install with -f install/kubernetes/helm/istio/values-istio-minimal.yaml and things will work. I think sidecar injector requires citadel for now


Missing wheels for M1 (Mac ARM) architecture

Expected behavior and actual behavior.
I expected to be able to install fiona with pip in python 3.9 on an M1 (arm architecture) Mac.
Steps to reproduce the problem.
pip install fiona raises the following error:
❯ pip install fiona
Collecting fiona
  Using cached Fiona-1.8.21.tar.gz (1.0 MB)
    ERROR: Command errored out with exit status 1:
     command: /Users/thomas/.asdf/installs/python/3.9.9/bin/python3.9 -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/yt/z22_f0896l74f8gs3_20vc_00000gn/T/pip-install-456dvi2q/fiona_ecb5449ed2884c3db55434cbb048b28b/setup.py'"'"'; __file__='"'"'/private/var/folders/yt/z22_f0896l74f8gs3_20vc_00000gn/T/pip-install-456dvi2q/fiona_ecb5449ed2884c3db55434cbb048b28b/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /private/var/folders/yt/z22_f0896l74f8gs3_20vc_00000gn/T/pip-pip-egg-info-tq10nup4
         cwd: /private/var/folders/yt/z22_f0896l74f8gs3_20vc_00000gn/T/pip-install-456dvi2q/fiona_ecb5449ed2884c3db55434cbb048b28b/
    Complete output (2 lines):
    Failed to get options via gdal-config: [Errno 2] No such file or directory: 'gdal-config'
    A GDAL API version must be specified. Provide a path to gdal-config using a GDAL_CONFIG environment variable or use a GDAL_VERSION environment variable.
    ----------------------------------------
WARNING: Discarding https://files.pythonhosted.org/packages/67/5c/4e028e84a1f0cb3f8a994217cf2366360ca984dfc1433f6171de527d0dca/Fiona-1.8.21.tar.gz#sha256=3a0edca2a7a070db405d71187214a43d2333a57b4097544a3fcc282066a58bfc (from https://pypi.org/simple/fiona/). Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.

Operating system
Mac OS X 12.2.1.
This is in the same vein as #1028. It would be great to add arm architecture support so that fiona and its 247 downstream packages can be used on arm :)
The linux arm package is of interest for mac as well, since docker images that run on the M1 architecture will run arm arch linux. (So if you run a docker image natively on M1 mac, the current linux package will not be installed)

Fiona 1.8.21 wheels for x86_64 manylinux2014 and macos (10.10) only were built on GitHub actions using https://github.com/sgillies/fiona-wheels.
In the M1 case, we're mainly blocked by the lack of free CI with native M1 workers. Cross-compilation is, in theory, possible, and I've done it for the GEOS library, but there are a lot of unknowns for the deep stack of libraries that GDAL depends on.
For the time being: use packages from conda-forge. The conda-forge project's mission is to build packages. You can even sponsor the project with money to do it. The Fiona project is not currently on a mission to build packages for every available platform.


High Score showing with penalties?

A 3rd party reported to me that the TOA high scores appeared to be including penalties, though the Game Manual says that the high score (for ranking 2nd tiebreaker) should be computed without penalties. Can you doublecheck to make sure that the TOA high score for each team in the rankings is computed as per the Game Manual requirements?

Thanks, fixed


[crashtracker] Add option to collect symbols in process

What does this PR do?
Restores the option to collect symbols in process that was removed in https://github.com/DataDog/libdatadog/pull/401
Motivation
I removed it because I thought nobody was using it. Turns out Python was.  Putting it back in.
Additional Notes
Anything else we should know when reviewing?
How to test the change?
Modified crashtracker.c to use the new enum, and got this output
{
  "counters": {
    "unwinding": 0,
    "not_profiling": 0,
    "collecting_sample": 0,
    "serializing": 0
  },
  "metadata": {
    "profiling_library_name": "crashtracking-test",
    "profiling_library_version": "12.34.56",
    "family": "crashtracking-test",
    "tags": []
  },
  "os_info": {
    "os_type": "Macos",
    "version": {
      "Semantic": [
        13,
        6,
        6
      ]
    },
    "edition": null,
    "codename": null,
    "bitness": "X64",
    "architecture": "arm64"
  },
  "siginfo": {
    "signum": 11,
    "signame": "SIGSEGV"
  },
  "stacktrace": [
    {
      "ip": "0x1050eb8b0",
      "names": [
        {
          "colno": 5,
          "filename": "/Users/daniel.schwartznarbonne/.cargo/registry/src/index.crates.io-6f17d22bba15001f/backtrace-0.3.71/src/backtrace/libunwind.rs",
          "lineno": 105,
          "name": "backtrace::backtrace::libunwind::trace::hcb64546259faca6e"
        },
        {
          "colno": 5,
          "filename": "/Users/daniel.schwartznarbonne/.cargo/registry/src/index.crates.io-6f17d22bba15001f/backtrace-0.3.71/src/backtrace/mod.rs",
          "lineno": 66,
          "name": "backtrace::backtrace::trace_unsynchronized::h449c2c234be2c879"
        },
        {
          "colno": 5,
          "filename": "/Users/daniel.schwartznarbonne/go/src/github.com/DataDog/libdatadog/crashtracker/src/collectors.rs",
          "lineno": 33,
          "name": "datadog_crashtracker::collectors::emit_backtrace_by_frames::h20a469c27d4d2bc2"
        }
      ],
      "sp": "0x16b2adaa0",
      "symbol_address": "0x1050eb8b0"
    },
    {
      "ip": "0x1050eb3bc",
      "names": [
        {
          "colno": 18,
          "filename": "/Users/daniel.schwartznarbonne/go/src/github.com/DataDog/libdatadog/crashtracker/src/crash_handler.rs",
          "lineno": 335,
          "name": "datadog_crashtracker::crash_handler::handle_posix_signal_impl::h3172de2881f81748"
        },
        {
          "colno": 13,
          "filename": "/Users/daniel.schwartznarbonne/go/src/github.com/DataDog/libdatadog/crashtracker/src/crash_handler.rs",
          "lineno": 214,
          "name": "datadog_crashtracker::crash_handler::handle_posix_sigaction::h79e38b5f86459741"
        }
      ],
      "sp": "0x16b2adb20",
      "symbol_address": "0x1050eb3bc"
    },
    {
      "ip": "0x1a8002a24",
      "names": [
        {
          "name": "__platform_memmove"
        }
      ],
      "sp": "0x16b2adbe0",
      "symbol_address": "0x1a8002a24"
    },
    {
      "ip": "0x104b53d90",
      "names": [
        {
          "name": "_main"
        }
      ],
      "sp": "0x16b2adc10",
      "symbol_address": "0x104b53d90"
    }
  ],
  "incomplete": false,
  "timestamp": "2024-05-15T16:30:02.475145Z",
  "uuid": "4b30b3b0-16c1-422d-a3a7-6471fede99a0"
}

Codecov Report
Attention: Patch coverage is 0% with 52 lines in your changes are missing coverage. Please review.

Project coverage is 66.14%. Comparing base (8e73294) to head (924e40d).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #430      +/-   ##
==========================================
- Coverage   66.28%   66.14%   -0.14%
==========================================
  Files         187      187
  Lines       23118    23166      +48
==========================================
  Hits        15324    15324
- Misses       7794     7842      +48

Components
Coverage Δ

crashtracker
19.34% <0.00%> (-0.97%)
:arrow_down:

datadog-alloc
98.37% <ø> (ø)

data-pipeline
51.45% <ø> (ø)

data-pipeline-ffi
0.00% <ø> (ø)

ddcommon
81.23% <ø> (ø)

ddcommon-ffi
74.93% <ø> (ø)

ddtelemetry
53.72% <ø> (ø)

ipc
81.27% <ø> (ø)

profiling
76.83% <ø> (ø)

profiling-ffi
60.05% <ø> (ø)

serverless
0.00% <ø> (ø)

sidecar
29.37% <ø> (ø)

sidecar-ffi
0.00% <ø> (ø)

spawn-worker
54.98% <ø> (ø)

trace-mini-agent
69.12% <ø> (ø)

trace-normalization
97.79% <ø> (ø)

trace-obfuscation
95.74% <ø> (ø)

trace-protobuf
25.64% <ø> (ø)

trace-utils
68.85% <ø> (ø)


[BREAKING] Require Node.js 20.11.x/>=21.2.0 and npm >=10

BREAKING CHANGE:
Support for older Node.js and npm releases has been dropped.
Only Node.js 20.11.x and >=21.2.0 as well as npm v10 or higher are supported.

coverage: 94.606% (-0.002%) from 94.608%
when pulling 70d0364a5a48318442e49ec5f1e7c110df23c689 on node-20
into 1484d357756ad550cc01de793138b25cd3c6b713 on main.


Small warning when compiling with emscripten

Just a small detail, when compiling with emscripten I got a warning:
cgltf.h:446:3: warning: redefinition of typedef 'cgltf_node' is a C11 feature [-Wtypedef-redefinition]

typedef can be just avoided in the struct definition because it has already been defined previously.
I can send a PR if you want.

PR would of course be appreciated. :-) Otherwise I’ll look into it next week.

This issue can be closed now that #75 has been merged :slightly_smiling_face:


Project failed to build, can I still use?

Hi, my project has failed to build due to too many methods, can I use this tool to pinpoint the culprit?  I'm not sure how to run it given I don't have an APK file, thanks!

Depending on your build process is structured, you could point at the .jar that is created as in input to the dex-ing process. You could also roll back the change that put you over the method limit, and see where the most number of methods were before that point.


responsivereactgrid : how to use callbacks like onDragStart,onResizeStart

Please only submit bugs to this tracker. If you have a feature request, please implement it. This is free software and the author is busy with other projects.
Please use the CodeSandbox Template to demonstrate your bug. It is much easier for us to help you if you do.

@kavyakongara have you got answer for this issue?
Way to use callbacks like onDragStart,onResizeStart


Add getAccountBuildStatus

Adds the account build status, including build minutes, to the API docs.
Closes #271

does this match what our private generated open api definition looks like?

Good point, I'll add a corresponding annotation in Bitballoon.

Good point, I'll add a corresponding annotation in Bitballoon.


some clang errors during type parsing not propagated back to the UI

Most notably --taget=bogustarget is one example, but there may be more. We should investigate and identify which errors are not being passed up and fix them.

Looks like there are cases where the compiler invocation can fail to parse but no errors are reported. Uncertain why, but clang_svcs.cpp:1731

Fixed in builds >= 4.1.4926 by just adding an extra error message when parsing fails but no errors are printed


Handle to_account transfers in split transactions

I have one more for you.
Problem
It looks like when a transaction is a transfer (indicated by [Account Name] in the category field, it is handled properly and the account name is applied to the to_account field and the category is left None.
However, if this kind of transfer occurs in a split, it isn't handled the same way. In the Split, the account name is assigned to category and not to_account.
Here's an example transaction in the "Checking" account. It is a $10 transfer with $9 going to the "Savings" account as a transfer, and $1 going to a Cash category.
^
D9/ 4'24
U-10.00
T-10.00
PSome Payee
L--Split--
S[Savings]
$-9.00
SCash
$-1.00
^

Here's how that is currently parsed.
>>>print(qif.accounts["Checking"].transactions["Bank"][6].splits[0])

Split:
    Amount: -9.00
    Category: [Savings]
    Percent: 90.000000000

Suggested Solution
See https://github.com/isaacharrisholt/quiffen/compare/main...lcmcninch:quiffen:split_to_account for my suggested solution.
In Transaction.from_list, when parsing a split transaction, we apply the same logic as when parsing a non-split transaction. Look for the opening bracket "[". If found, set to_account instead of category. With that change, I now get:
print(qif.accounts["Checking"].transactions["Bank"][6].splits[0])
Split:
    Amount: -9.00
    To Account: Savings
    Percent: 90.000000000

Thoughts? If you agree, I can submit a PR.

Looks good!

Perfect, will-do. Thanks again!


Something went wrong during completion. Reason: 'NoneType' object is not subscriptable

Got no Errors during the installation, when I try sending messages in the bot it responds with:

dude, remember to issue the following command to update the python packages.
pip3 install -r requirements.txt

@churchmice what actions in bot lead to such behaviour?

Well Imma close the isse because it gets solved by using what @churchmice suggested. Thanks dude!


BambooStorage.Internal should provide API for transactions

Currently, we need several methods:
areTransactionsSupported()
beginTransaction()
setTransactionSuccessful()
endTransaction()

Just like pure SQLiteDatabase
Will be useful for #40 put(collection) and delete(collection) operations

@nikitin-da I'll take it, I have several hours to do it

ok


Application window does not maximize / resize

The application window is of fixed size. Therefore it does not scale elegantly to various screens.
Work toward this issue: https://github.com/PovertyAction/PII_detection/tree/resizing-window

Resolved by 0.1.2, though only the window resizes, the content does not


FAQ dropdown arrows

Fix FAQ arrows not appearing:

This looks to be fixed. I will close this issue for now to clean up this tab.

p.s. the "+" rotating to a "x" is actually quite cool, good job!


Cannot join the lobby when in LAN mode

same as topic

bumping this issue, support for LAN mode would be appreciated
— as a developer, fixing MoreCompany-specific bugs/incompatibilities is nearly impossible when i can't spin up several clients in LAN mode to test with

bump

Fixed in v1.8.0+

hang on

@CoolLKKPS The only thing that mod has that MoreCompany doesn't for LAN is custom usernames and the option to choose the port.
Having two mods that add a custom popup to the join button is always going to conflict with each other for example you probably won't see the option to specify the max player count.

The only thing that mod has that MoreCompany doesn't for LAN is custom usernames and the option to choose the port.
Having two mods that add a custom popup to the join button is always going to conflict with each other for example you probably won't see the option to specify the max player count.

i just thinking if we make a LC server just like Minecraft server, we can have over 100+ people in the same server, the problem is tools (or mods), they just conflict each other and so hard to do it
back to the question, recently MoreCompany add LAN support, but if i have LCDirectLAN, it just override the MoreCompany UI, since MoreCompany only provide IP address option to connect, so i don't think that's enough, override the MoreCompany UI LAN UI should be fine

i don't think i have to imagine that, Among Us can also do 100+ people lobby. everything can happen, ok still, i don't have enough resource to create a real custom server, but i believe one day it should be can happen

but for now, this issue should be fixed, so i will close this issue


FAIL with Fontbakery lastest version although I have the latest version

Observed behaviour
When I run bakery with gftools from terminal I have this FAIL :
🔥 FAIL: Do we have the latest version of FontBakery installed?
com.google.fonts/check/fontbakery_version

🔥 FAIL Unable to detect what's the latest version of FontBakery available. Maybe we're offline? Please check Internet access and try again.

I don't understand why, I have the lastest version.
Although when I run Fontbakery from the platfrom, this check transform into :
com.google.fonts/check/ftxvalidator_is_available Is the command `ftxvalidator` (Apple Font Tool Suite) available?

WARN Could not find ftxvalidator.

I installed ftxvalidator but apparently it doesn't find the path to it, and whatever I have seen in the issues, I don't manage to make it work. I have Mac Mojav 10.14.6 and installed the fontools pack that is supposed to match the OS version.

I'm confused. You mention two different checks here:

com.google.fonts/check/fontbakery_version
com.google.fonts/check/ftxvalidator_is_available

Sorry, I thought it could highlight a difference of set up, because there are both from the "Family Check", I don't have a ftxvalidator fail when I run FB from the terminal. So I thought it might be linked somehow?

no, these checks are unrelated.
I'll look at these checks implementations to see if I can spot something wrong.

Although when I run Fontbakery from the platform, this check transform into :

@RosaWagner what is "the platform"? Is it Font Bakery Dashboard?

Is it Font Bakery Dashboard?

YEP

no, these checks are unrelated.

Haha Okay ^^ I shall reopen one the related issue then.

Is it Font Bakery Dashboard?
YEP

Just FYI, Font Bakery Dashboard runs on the Google Cloud. We don't have (simple) access to MacOS machines from there, so we can't run ftxvalidator, which is Mac only.

AAAAAH OK, makes sense

I'm closing this one as it seems to be a duplicate of #2966