Ilmbase enable cxx14, thread pool improvements

Given VP18 is c++14, this is a few commits that enable c++14 in both cmake and autoconf, with a mechanism to disable and force IlmBase to continue to be strictly c++03 compliant.
Credit / Other pull request notes: I started this to add the thread pool optimizations, which we would like. However, this should be considered an alternate implementation of pull request #55 , and I didn't realize it at the time, but provides similar c++11 related dynamic exception fixes as #93, #236, and #243 , so there might be conflicts there. Finally, this should make #170 obsolete with a more complete fix - it would appear @lgritz and I have similar perf traces for loading tiles... :)
Includes:

configure / cmake changes
dynamic exception macro to fix compile warnings in Imath
IlmThread enables use of std::thread, std::mutex
ThreadPool uses c++11 atomic, shared_ptr (when enabled) to provide lighter weight thread safe contention when appropriate, cleanups, and reducing lock contention in both scenarios
At the same time, an API to enable a user to replace the global thread pool is proposed, with no change to existing API, only additions. This is used internally to provide a minimal overhead, completely lock-free task processing when numThreads is set to 0 (which also happens to be the default for the OpenEXR library)
A std::condition_variable based Semaphore is available when in c++11 mode

note: I did NOT switch semaphore to only use std::condition_variable/std::mutex - only when semaphores are not available. low level semaphores tend to be faster when dispatching things in a sequence, as this pool tends to do, so blindly switching to condition_variable should only be done when semaphores are not available...

For those that are on C++11 but can't yet switch to C++14, it'd be nice to be able to take advantage of the C++11 parts of this patch. Would it maybe be useful to add C++11 as an option? I suspect most of this patch is already fine with C++11, and the few C++14 bits could revert to C++03 code paths when compiling for C++11?

The only change that is c++14 specific are the compile options in the autoconf / cmake file. I've just submitted an addition to the cmake / autoconf that makes those more options than only c++14. The default should be C++14 to align with VFX Platform 2018.

What's the merit to keeping any of this (moving forward) C++03 compatible?
http://www.vfxplatform.com/ has specified C++11 as a floor since 2016.

there are many consumers of ilmbase / EXR, many of them not tied in any way to the VFX platform - and was not sure all of them would want to or be ready to embrace c++11, it wasn't difficult to provide the option, so seemed like maximum flexibility.

Modulo consensus on Larry's point, I think this looks ready to go.
My personal bias is to remove the C++03 compatibility and request that users of older systems stick with an older OpenEXR release.
The reason I feel that way is that I feel that if we want to retain that compatibility, then it should be part of the testing matrix and CI, otherwise every commit runs the risk of breaking back compat, or I should say carries the onus of extra programming and testing on the maintainer's part. If it's practical I'm favor of less work :] My two cents.

My opinion also would be to move the floor up to C++11. People on C++03 can keep using OpenEXR 2.2 (or, let's face it, they are likely not current on that, either) indefinitely.

Is there a corresponding change missing from the OpenEXR part with this, or have I missed something?
With g++ 5.4 (system compiler), with latest head of develop, IlmBase builds fine with CMake, but then OpenEXR doesn't due to not having c++11 enabled within the OpenEXR build:
/usr/include/c++/5/bits/c++0x_warning.h:32:2: error: #error This file requires compiler and library support for the ISO C++ 2011 standard. This support must be enabled with the -std=c++11 or -std=gnu++11 compiler options.
If I hackily add:
SET(CMAKE_CXX_FLAGS_RELEASE "-std=c++11")
to OpenEXR's CMakeList.txt
It then builds fine and I can use it. Given there's the Force C++03 (which might be taken out?) that looks like it needs to be set if you want C++03, I'd assume C++11 would be the default with this (or at least the platform compiler default is?) so that OpenEXR can use IlmBase? Or should whatever's building OpenEXR externally set -std=c++11 within the OpenEXR build?

I think the corresponding logic just hasn't been added to OpenEXR yet. There should be a corresponding entry in configure.ac.

Yeah, Kimball confirmed that to me today.
Fair enough - I guess I just expected to be able to pull and it to work, but I guess it's the develop branch for a reason :)


User config inconsistency with snap packages

Required information

Distribution: ubuntu 18.04
The output of "lxc info" or if that fails:

config: {}
api_extensions:
- storage_zfs_remove_snapshots
- container_host_shutdown_timeout
- container_stop_priority
- container_syscall_filtering
- auth_pki
- container_last_used_at
- etag
- patch
- usb_devices
- https_allowed_credentials
- image_compression_algorithm
- directory_manipulation
- container_cpu_time
- storage_zfs_use_refquota
- storage_lvm_mount_options
- network
- profile_usedby
- container_push
- container_exec_recording
- certificate_update
- container_exec_signal_handling
- gpu_devices
- container_image_properties
- migration_progress
- id_map
- network_firewall_filtering
- network_routes
- storage
- file_delete
- file_append
- network_dhcp_expiry
- storage_lvm_vg_rename
- storage_lvm_thinpool_rename
- network_vlan
- image_create_aliases
- container_stateless_copy
- container_only_migration
- storage_zfs_clone_copy
- unix_device_rename
- storage_lvm_use_thinpool
- storage_rsync_bwlimit
- network_vxlan_interface
- storage_btrfs_mount_options
- entity_description
- image_force_refresh
- storage_lvm_lv_resizing
- id_map_base
- file_symlinks
- container_push_target
- network_vlan_physical
- storage_images_delete
- container_edit_metadata
- container_snapshot_stateful_migration
- storage_driver_ceph
- storage_ceph_user_name
- resource_limits
- storage_volatile_initial_source
- storage_ceph_force_osd_reuse
- storage_block_filesystem_btrfs
- resources
- kernel_limits
- storage_api_volume_rename
- macaroon_authentication
- network_sriov
- console
- restrict_devlxd
- migration_pre_copy
- infiniband
- maas_network
- devlxd_events
- proxy
- network_dhcp_gateway
- file_get_symlink
- network_leases
- unix_device_hotplug
- storage_api_local_volume_handling
- operation_description
- clustering
- event_lifecycle
- storage_api_remote_volume_handling
- nvidia_runtime
- container_mount_propagation
- container_backup
- devlxd_images
- container_local_cross_pool_handling
- proxy_unix
- proxy_udp
- clustering_join
- proxy_tcp_udp_multi_port_handling
- network_state
- proxy_unix_dac_properties
- container_protection_delete
- unix_priv_drop
- pprof_http
- proxy_haproxy_protocol
- network_hwaddr
- proxy_nat
- network_nat_order
- container_full
- candid_authentication
- backup_compression
- candid_config
- nvidia_runtime_config
- storage_api_volume_snapshots
- storage_unmapped
- projects
- candid_config_key
- network_vxlan_ttl
- container_incremental_copy
- usb_optional_vendorid
- snapshot_scheduling
- container_copy_project
- clustering_server_address
- clustering_image_replication
- container_protection_shift
- snapshot_expiry
- container_backup_override_pool
- snapshot_expiry_creation
- network_leases_location
- resources_cpu_socket
- resources_gpu
- resources_numa
- kernel_features
- id_map_current
- event_location
- storage_api_remote_volume_snapshots
- network_nat_address
- container_nic_routes
- rbac
- cluster_internal_copy
- seccomp_notify
- lxc_features
- container_nic_ipvlan
- network_vlan_sriov
- storage_cephfs
- container_nic_ipfilter
- resources_v2
- container_exec_user_group_cwd
- container_syscall_intercept
- container_disk_shift
- storage_shifted
- resources_infiniband
- daemon_storage
- instances
- image_types
- resources_disk_sata
- clustering_roles
- images_expiry
- resources_network_firmware
- backup_compression_algorithm
- ceph_data_pool_name
- container_syscall_intercept_mount
- compression_squashfs
- container_raw_mount
- container_nic_routed
- container_syscall_intercept_mount_fuse
- container_disk_ceph
- virtual-machines
- image_profiles
- clustering_architecture
- resources_disk_id
- storage_lvm_stripes
- vm_boot_priority
- unix_hotplug_devices
- api_filtering
- instance_nic_network
- clustering_sizing
- firewall_driver
- projects_limits
- container_syscall_intercept_hugetlbfs
- limits_hugepages
- container_nic_routed_gateway
- projects_restrictions
- custom_volume_snapshot_expiry
- volume_snapshot_scheduling
- trust_ca_certificates
- snapshot_disk_usage
- clustering_edit_roles
- container_nic_routed_host_address
- container_nic_ipvlan_gateway
- resources_usb_pci
- resources_cpu_threads_numa
- resources_cpu_core_die
- api_os
- container_nic_routed_host_table
- container_nic_ipvlan_host_table
- container_nic_ipvlan_mode
- resources_system
- images_push_relay
- network_dns_search
- container_nic_routed_limits
- instance_nic_bridged_vlan
- network_state_bond_bridge
- usedby_consistency
- custom_block_volumes
- clustering_failure_domains
- resources_gpu_mdev
- console_vga_type
- projects_limits_disk
- network_type_macvlan
- network_type_sriov
- container_syscall_intercept_bpf_devices
- network_type_ovn
- projects_networks
- projects_networks_restricted_uplinks
- custom_volume_backup
- backup_override_name
- storage_rsync_compression
- network_type_physical
- network_ovn_external_subnets
- network_ovn_nat
- network_ovn_external_routes_remove
- tpm_device_type
- storage_zfs_clone_copy_rebase
- gpu_mdev
- resources_pci_iommu
- resources_network_usb
- resources_disk_address
- network_physical_ovn_ingress_mode
- network_ovn_dhcp
- network_physical_routes_anycast
- projects_limits_instances
- network_state_vlan
- instance_nic_bridged_port_isolation
- instance_bulk_state_change
- network_gvrp
- instance_pool_move
- gpu_sriov
- pci_device_type
- storage_volume_state
- network_acl
- migration_stateful
- disk_state_quota
- storage_ceph_features
- projects_compression
- projects_images_remote_cache_expiry
- certificate_project
- network_ovn_acl
- projects_images_auto_update
- projects_restricted_cluster_target
api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
- tls
environment:
  addresses: []
  architectures:
  - x86_64
  - i686
  certificate: |
    -----BEGIN CERTIFICATE-----
    MIICEjCCAZmgAwIBAgIRAPuC3h3xa7SMaBdWsLC/ldMwCgYIKoZIzj0EAwMwOTEc
    MBoGA1UEChMTbGludXhjb250YWluZXJzLm9yZzEZMBcGA1UEAwwQcm9vdEB0cm91
    bHduMDI2MjAeFw0yMDA4MDQwNzA4MjRaFw0zMDA4MDIwNzA4MjRaMDkxHDAaBgNV
    BAoTE2xpbnV4Y29udGFpbmVycy5vcmcxGTAXBgNVBAMMEHJvb3RAdHJvdWx3bjAy
    NjIwdjAQBgcqhkjOPQIBBgUrgQQAIgNiAATmkzpJ5cEZ2SlY36T7YXGusKCVbV7+
    0Sdjd8JNu2oZ4Clo4LOdviiGwDCs666YgGxtP6ZlhIMpmcFbpwInwWEgSkLA+w5K
    Msul+uzN40Us3I1818lxTF3yhj+mKX30olCjZTBjMA4GA1UdDwEB/wQEAwIFoDAT
    BgNVHSUEDDAKBggrBgEFBQcDATAMBgNVHRMBAf8EAjAAMC4GA1UdEQQnMCWCC3Ry
    b3Vsd24wMjYyhwR/AAABhxAAAAAAAAAAAAAAAAAAAAABMAoGCCqGSM49BAMDA2cA
    MGQCMCWZ6omwlc5WaxUmBsNScV7mKZfHKk2CILp5oAd5T2cGpimMpXzNi21RDhSI
    iKAyfQIwPcywAOmsvF8OoOeqgF43rka9y9mQeeTfMiO7/xf6HAzn6Q+WLaLJWk0i
    d8StRPQi
    -----END CERTIFICATE-----
  certificate_fingerprint: 67e0f1937c7f95a9b4a12fc06acc99fbb90c825684750a7eb25a96d631539a61
  driver: lxc | qemu
  driver_version: 4.0.6 | 5.2.0
  firewall: xtables
  kernel: Linux
  kernel_architecture: x86_64
  kernel_features:
    netnsid_getifaddrs: "true"
    seccomp_listener: "true"
    seccomp_listener_continue: "true"
    shiftfs: "false"
    uevent_injection: "true"
    unpriv_fscaps: "true"
  kernel_version: 5.4.0-59-generic
  lxc_features:
    cgroup2: "true"
    devpts_fd: "true"
    mount_injection_file: "true"
    network_gateway_device_route: "true"
    network_ipvlan: "true"
    network_l2proxy: "true"
    network_phys_macvlan_mtu: "true"
    network_veth_router: "true"
    pidfd: "true"
    seccomp_allow_deny_syntax: "true"
    seccomp_notify: "true"
    seccomp_proxy_send_notify_fd: "true"
  os_name: Ubuntu
  os_version: "18.04"
  project: default
  server: lxd
  server_clustered: false
  server_name: host
  server_pid: 10129
  server_version: "4.12"
  storage: dir
  storage_version: "1"

Issue description
The remote configs in the official snap package are stored in ~/snap/lxd/$VERSION/.config/lxc/config.yml.
If lxc remote add ... is run, the config will be written to this file. We internally provide an 'lxdhub' where one can
push and pull images from. Now on every update of the snap lxd package the configs are 'cleared' meaning the remotes are gone. This leads to (in my eyes) unexpected behaviour:
$ tail -v -n +0 $HOME/snap/lxd/*/.config/lxc/config.yml
==> ~/snap/lxd/18402/.config/lxc/config.yml <==
default-remote: local
remotes:
  images:
    addr: https://images.linuxcontainers.org
    protocol: simplestreams
    public: true
  local:
    addr: unix://
    public: false
aliases: {}

==> ~/snap/lxd/18884/.config/lxc/config.yml <==
default-remote: local
remotes:
  images:
    addr: https://images.linuxcontainers.org
    protocol: simplestreams
    public: true
  local:
    addr: unix://
    public: false
  roche:
    addr: https://some-remote.com:8443
    public: true
  roche-dev:
    addr: https://another-remote.com:8443
    auth_type: tls
    project: default
    protocol: lxd
    public: false
aliases: {}

==> ~/snap/lxd/19009/.config/lxc/config.yml <==
default-remote: local
remotes:
  images:
    addr: https://images.linuxcontainers.org
    protocol: simplestreams
    public: true
  local:
    addr: unix://
    public: false
  roche-dev:
    addr: https://some-remote.com:8443
    auth_type: tls
    project: default
    protocol: lxd
    public: false
aliases: {}

Steps to reproduce

Add remote
Upgrade snap
Config inconsistency

Information to attach

[ ] Any relevant kernel output (dmesg)
[ ] Container log (lxc info NAME --show-log)
[ ] Container configuration (lxc config show NAME --expanded)
[ ] Main daemon log (at /var/log/lxd/lxd.log or /var/snap/lxd/common/lxd/logs/lxd.log)
[ ] Output of the client with --debug
[ ] Output of the daemon with --debug (alternatively output of lxc monitor while reproducing the issue)

Can you report this at https://forum.snapcraft.io?
This is a snapd bug, on snap refresh, it's supposed to copy the last revision data to the new revision and then change the symlink to point to the new one. If it's getting you an empty directory as this suggests, it's a bug in snapd.
Closing the issue here as it's outside of LXD's control. Though one thing I've been considering doing is moving the config into common to avoid such issues from even being possible (would prevent rollback to older config but that's unlikely to be very used anyway).

Thanks for your help as always!
Reported here: https://forum.snapcraft.io/t/user-config-inconsistency-with-snap-packages/23382

For anyone having the same issue, $HOME different than /home/$USER (in my case /home/users/$USER) is not supported.

Oh, that's rather annoying... We'll definitely be looking at moving things to common as even with normal /home we've seen a few cases where this isn't handled properly...

That would be nice!


MTV-1548: VMs with Secure Boot cannot be migrated automatically

JIRA

MTV-1548
Created a snippet.
Added this snippet to the 2.7 Known Issues and also added to the Source virtual machine prerequisites.

Release Notes
Source virtual machine prereqs

![image](
![image](

PREVIEW

Source virtual machine prerequisites

2.7 Known issues

Looks sensible, although I think some VMs can be migrated successfully (albeit, SB won't be active on the target) so how about hedging a little: "... with Secure Boot enabled currently might be migrated automatically" ?

@rwmjones Thanks very much. Updated

Looks good!  There's no visible "approve" or similar button I can see, but I'm OK with the change.


RFC: option to only run certain queries in SSR

We could add something like cashay.query(queryString, {runOnSSR: false}) which would allow users to only run certain queries when rendering the HTML on the server.
My question is, would this ever be useful? Personally, I want to run every query on the server except those queries that are behind a login wall, but SSR doesn't see those anyways, so it's of no concern.
If you can think of a use case, let me know!

closing for now as i can see any use


Added How to Track Pageviews with GTM in a React-Redux app

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I have added tests that prove my fix is effective or that my feature works.
[x] I have added all necessary documentation (if appropriate)

What was done
Added documentation for GTM pageview tracking example
Associated Issues

list any associated issue numbers here

:heart: Thanks
Thanks for taking the time to help out with the project, it's much appreciated :slightly_smiling_face:

This is awesome, thanks so much @AmyScript! A couple of things though:
Your example is pretty specific to using GTM with Google Analytics, but you can (and people often do) use GTM with other analytics services.
I think this is a good starting point for something that I've wanted to do for a while. How do you feel about exporting your GTM + GA configuration and we can add it to the repo?
Here's what I'm talking about :point_down:

This is all under the Admin tab in GTM.
 All the Tags, Variables, and Triggers you created.
Basically what I'm thinking we could do is have a super simple getting started guide for using Redux Beacon with GTM and GA:

Set up Redux Beacon (eventsMap, and eventDefinition)
Import the GTM container (the .json file with all Tags, Variables, and Triggers)
Connect GTM to your GA account

And that's it!
I the future we could have configurations for more than just GTM + GA. We can have GTM + whatever:

Thoughts?

@ttmarek sounds good.  Let me get to that next week and revise the PR.


Add Travis CI support

Simple build test, laying the groundwork for more future test automation.

I've enabled travis on this repo now. ;)

Sweet, thanks @GrahamCampbell !


stub out more types/funcs to compile against golang.org/x/net/internal/socket

This is for tinygo-org/net/issues/14. Basically, trying to get apps which import golang.org/x/net/internal/socket to compile.
This PR covers the additions needed to src/net. There is a matching matching PR (tinygo-org/tinygo/pull/4035) in tinygo-org/tinygo for the "crypto/tls" package changes for tinygo-org/net/issues/14.

I'm going to close this PR since the work on tinygo-org/net/issues/14 is unresolved.  We can re-open if 14 resolves.


help needed

How to change the button color from violet to FFB6C1

Via ttjoin in the css file, these are simple things that I can't always help you with if you don't have even a simple programming experience


ci: Changes xcode version to latest stable

This changes the MacOS CI from using the latest XCode to latest-stable to avoid going to v16, which comes with Swift 6.0.0. This resolves the issues observed here: https://github.com/GraphQLSwift/Graphiti/pull/137#issuecomment-2177314720
It also adds Swift 5.10 to the Linux test matrix

Hi @paulofaria,
Do you have any news regarding the review of this PR ?
PR #137 is blocked until this one is approved.

Sorry! Completely missed this PR. LGTM!


table cell's vertical-align is changed to top in the printed pdf

Steps to reproduce
Tell us about your environment:

Puppeteer version<EMAIL_ADDRESS>Platform / OS version: Windows 10
URLs (if applicable):
Node.js version: v8.11.2

What steps will reproduce the problem?
Please include code that reproduces the issue.

Create a html file with below content for test. Place it on some place, e.g. E:\test.html.
testHTML.txt

Run below js to print a pdf file.
`const puppeteer = require('puppeteer');

puppeteer.launch().then(async browser => {
const page = await browser.newPage();
await page.goto('file:///E:/test.html');
await page.pdf({
path: 'page.pdf',
width: 1500,
height: 1000,
});
await browser.close();
});`

In the resulting pdf file, table cell's vertical-align is changed to top.
page.pdf

What is the expected result?
Do not change the table cell's vertical-align in the printed pdf.
What happens instead?
Table cell's vertical-align is changed to top in the printed pdf.

The expected pdf content for the provided sample html file should be as below.
page.pdf


cmd: add (Set|Get)BucketVersioning to object layer

Wires SetBucketVersioning and GetBucketVersioning with bucket-versioning-handler.go and replace original implementation. Also extends ObjectLayer interface with those two methods.

Change https://review.dev.storj.io/c/storj/gateway/+/11801 is a proof that its working :) that change is using this branch


APIGOV-17864 - fix yaml parsing of camel case paths

looks good!

@dfeldick - thanks for keeping me honest on that


Add Dan's fixes to string functions

See title. Tagging #180 .

In the head post of PR #185, you should edit it to include the phrases "Closes #182" or similar. That will auto close the issue once the branch gets merged in. It only works for the head post though (or in a commit message).


Bug: Custom plugin with lifespan breaks channel startup hook

Description
I wrote a simple plugin with a lifespan based on a context manager. When I add the custom plugin and the channels plugin, the channels plugin does not initialize properly. If I remove the lifespan from the custom plugin it works.
URL to code causing the issue
No response
MCVE
from litestar import Litestar, post
from litestar.testing import TestClient
from litestar.channels import ChannelsPlugin
from litestar.channels.backends.memory import MemoryChannelsBackend
from litestar.channels import ChannelsPlugin
from litestar.plugins import InitPluginProtocol
from contextlib import asynccontextmanager
from collections.abc import AsyncGenerator
import logging

@post("/publish_something")
async def handler(channels: ChannelsPlugin) -> None:
    channels.publish("test", "my_new_channel")

@asynccontextmanager
async def some_lifecycle(app: "Litestar") -> "AsyncGenerator[None, None]":
    logging.info("some startup")
    try:
        yield
    finally:
        logging.info("some shutdown")

class SomePlugin(InitPluginProtocol):
    def on_app_init(self, app_config: "AppConfig") -> "AppConfig":
        # comment this out and the startup works
        app_config.lifespan = [some_lifecycle]
        return app_config

with TestClient(
    app=Litestar(
        debug=True,
        plugins=[
            ChannelsPlugin(backend=MemoryChannelsBackend(history=0), channels=[], arbitrary_channels_allowed=True),
            SomePlugin(),
        ],
        route_handlers=[handler],
    )
) as client:
    client.post("/publish_something")

Steps to reproduce
1. Run the script
2. It errors out when hitting the publish_something route

Screenshots
"![SCREENSHOT_DESCRIPTION](SCREENSHOT_LINK.png)"

Logs
INFO - 2024-06-26 12:15:33,244 - root - bug - some startup
ERROR - 2024-06-26 12:15:33,255 - litestar - config - Uncaught exception (connection_type=http, path=/publish_something):
Traceback (most recent call last):
  File "/root/innovation-framework/.venv/lib/python3.12/site-packages/litestar/channels/plugin.py", line 144, in publish
    self._pub_queue.put_nowait((data, list(channels)))  # type: ignore[union-attr]
    ^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'put_nowait'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/root/innovation-framework/.venv/lib/python3.12/site-packages/litestar/middleware/_internal/exceptions/middleware.py", line 159, in __call__
    await self.app(scope, receive, capture_response_started)
  File "/root/innovation-framework/.venv/lib/python3.12/site-packages/litestar/_asgi/asgi_router.py", line 99, in __call__
    await asgi_app(scope, receive, send)
  File "/root/innovation-framework/.venv/lib/python3.12/site-packages/litestar/routes/http.py", line 80, in handle
    response = await self._get_response_for_request(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/innovation-framework/.venv/lib/python3.12/site-packages/litestar/routes/http.py", line 132, in _get_response_for_request
    return await self._call_handler_function(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/innovation-framework/.venv/lib/python3.12/site-packages/litestar/routes/http.py", line 152, in _call_handler_function
    response_data, cleanup_group = await self._get_response_data(
                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/innovation-framework/.venv/lib/python3.12/site-packages/litestar/routes/http.py", line 200, in _get_response_data
    else await route_handler.fn(**parsed_kwargs)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/innovation-framework/bug.py", line 14, in handler
    channels.publish("test", "my_new_channel")
  File "/root/innovation-framework/.venv/lib/python3.12/site-packages/litestar/channels/plugin.py", line 146, in publish
    raise RuntimeError("Plugin not yet initialized. Did you forget to call on_startup?") from e
RuntimeError: Plugin not yet initialized. Did you forget to call on_startup?
INFO - 2024-06-26 12:15:33,264 - httpx - _client - HTTP Request: POST http://testserver.local/publish_something "HTTP/1.1 500 Internal Server Error"
INFO - 2024-06-26 12:15:33,266 - root - bug - some shutdown

Litestar Version
2.9.1
Platform

[X] Linux
[ ] Mac
[ ] Windows
[ ] Other (Please specify in the description above)

[!NOTE]
While we are open for sponsoring on GitHub Sponsors and
OpenCollective, we also utilize Polar.sh to engage in pledge-based sponsorship.
Check out all issues funded or available for funding on our Polar.sh dashboard

If you would like to see an issue prioritized, make a pledge towards it!
We receive the pledge once the issue is completed & verified
This, along with engagement in the community, helps us know which features are a priority to our users.

Sorry, I figured it out:
app_config.lifespan = [some_lifecycle]
should be
app_config.lifespan += [some_lifecycle]


Docs bug

@sgugger there's a bug in the generated docs. The issue is that the "ID=" attribute in the HTML includes the "<code>" tags, so anchor hyperlinks don't work. for instance, this doesn't work:
http://dev.fast.ai/data.pipeline.html#Transform

Fixed and tested, see http://dev.fast.ai/data.pipeline.html#Pipeline


LICENSE for the repo

Could you please add a license to the repo? It will enable us use the package. Thanks!

Done


How do I work around this?

This causes the same error as https://github.com/ceph/go-ceph/issues/54

@subusc hi Subu, this is actually a bug of https://github.com/mulbc/homebrew-ceph-client. it should have been fixed by https://github.com/mulbc/homebrew-ceph-client/releases/tag/quincy-17.2.5-1 .

Thanks @tchaikov for noticing this and replying quickly.  @subusc since this is outside the scope of go-ceph project can you mind please closing this issue? Thanks.

Thanks a ton for the quick replies folks!
@tchaikov - this is not getting pulled with the default commands
 % brew tap mulbc/ceph-client
brew install ceph-client

I have tried multiple variants to get to the exact version - they're failing as well. How do I fix this?

 % brew extract --version=17.2.5_1 ceph-client mulbc/ceph-client
==> Searching repository history
Error: Could not find ceph-client! The formula or version may not have existed.
 % brew extract --version=17.2.5-1 ceph-client mulbc/ceph-client
==> Searching repository history
Error: Could not find ceph-client! The formula or version may not have existed.

 % brew tap mulbc/ceph-client
brew install https://raw.githubusercontent.com/mulbc/homebrew-ceph-client/5243db315d7541bd7e190dbc66d1237b2c815f68/ceph-client.rb
Error: Installation of ceph-client from a GitHub commit URL is unsupported! `brew extract ceph-client` to a stable tap on GitHub instead.

@phlogistonjohn I will right after this resolution! Thanks a ton!

@tchaikov FYI - downloading the ruby file locally also fails - with a similar error.
 % brew install ~/ceph-client.rb
Running `brew update --auto-update`...
==> Auto-updated Homebrew!
Updated 1 tap (homebrew/core).

Error: Failed to load cask: /Users/subramanian.sankarasubramanian/ceph-client.rb
Cask 'ceph-client' is unreadable: wrong constant name #<Class:0x00007f90269188f0>
Warning: Treating /Users/subramanian.sankarasubramanian/ceph-client.rb as a formula.
==> Downloading https://files.pythonhosted.org/packages/cb/7d/7e6bc4bd4abc49e9f4f5c4773bb43d1615e4b476d108d1b527318b9c6521/prettytable-3.2.0.tar.gz
Already downloaded: /Users/subramanian.sankarasubramanian/Library/Caches/Homebrew/downloads/4c52d4026151aa261d150292e430951006c98d7d72a89034ecea460b2f2c111b--prettytable-3.2.0.tar.gz
==> Downloading https://files.pythonhosted.org/packages/36/2b/61d51a2c4f25ef062ae3f74576b01638bebad5e045f747ff12643df63844/PyYAML-6.0.tar.gz
Already downloaded: /Users/subramanian.sankarasubramanian/Library/Caches/Homebrew/downloads/83f6bef3a0a4fd3d9559a85acb4ab73b0e4544f8542e67bf54929e86653356e9--PyYAML-6.0.tar.gz
==> Downloading https://files.pythonhosted.org/packages/89/38/459b727c381504f361832b9e5ace19966de1a235d73cdbdea91c771a1155/wcwidth-0.2.5.tar.gz
Already downloaded: /Users/subramanian.sankarasubramanian/Library/Caches/Homebrew/downloads/bc4d16c76a1cb1eecc9775864d059d1cfb00289c163bc86440fcd6eef95aa2d8--wcwidth-0.2.5.tar.gz
==> Downloading https://download.ceph.com/tarballs/ceph-17.2.5.tar.gz
Already downloaded: /Users/subramanian.sankarasubramanian/Library/Caches/Homebrew/downloads/b368830312f6eb917b2570de1804003eb370a49ca1887c698544c64b8c8c8313--ceph-17.2.5.tar.gz
==> Patching
Error: An exception occurred within a child process:
  Errno::EPERM: Operation not permitted @ dir_s_mkdir - /usr/local/opt/cython/libexec/lib/python3.10

Your latest issue is not go-ceph related and already reported here: https://github.com/mulbc/homebrew-ceph-client/issues/24. Please continue the conversation there.
Closing.


Dev

#11

Coverage: 81.495% (-1.1%) from 82.593% when pulling ca3e923bc6df3987d8ad8ad2094cbb0a87179a9a on dev into 64c9652d63e19d47d7515c24da85c481f9bea04c on main.


Allowing us access to the API Response

This will give use the API response for if there is a success or error.

@rex-remind101  I think so cause we can still get a 200 but an error frag so it would be helpful to have the request id there as well

you can use didFinishRequest to inspect the payload and throw an error in those cases.
https://github.com/remind101/AutoGraph/blob/cf2ecd10209aaf200e8d4ce4a89008a46eb4c288/AutoGraph/Request.swift#L25


Set the right permissions for robin home dir.

When creating the devcontainer image with Visual Studio Code the following log is generated:
[3296 ms] Start: Run in container:  (command -v getent >/dev/null 2>&1 && getent passwd 'robin' || grep -E '^robin|^[^:]*:[^:]*:robin:' /etc/passwd || true)
[3296 ms] Start: Updating configuration state
[3300 ms] Start: Setup shutdown monitor
[3300 ms] Forking shutdown monitor: /home/rwxr-xr-x/.vscode/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/shutdown/shutdownMonitorProcess /run/user/1000/vscode-remote-containers-772a03e1-6375-4e50-8846-bfc4d93218ab.sock dockerCompose Debug /home/rwxr-xr-x/.config/Code/logs/20231208T032057/window8/exthost/ms-vscode-remote.remote-containers<PHONE_NUMBER>484
[3304 ms] Start: Run in container: test -d /home/robin/.vscode-server
[3304 ms]
[3304 ms]
[3304 ms] Exit code 1
[3304 ms] Start: Run in container: test -d /home/robin/.vscode-remote
[3304 ms]
[3304 ms]
[3305 ms] Exit code 1
[3305 ms] Start: Run in container: test ! -f '/home/robin/.vscode-server/data/Machine/.writeMachineSettingsMarker' && set -o noclobber && mkdir -p '/home/robin/.vscode-server/data/Machine' && { > '/home/robin/.vscode-server/data/Machine/.writeMachineSettingsMarker' ; } 2> /dev/null
[3305 ms]
[3305 ms] mkdir: cannot create directory '/home/robin/.vscode-server': Permission denied
[3305 ms] Exit code 1
[3305 ms] Start: Run in container: cat /home/robin/.vscode-server/data/Machine/settings.json
[3306 ms]
[3306 ms] cat: /home/robin/.vscode-server/data/Machine/settings.json: No such file or directory
[3306 ms] Exit code 1
[3306 ms] Start: Run in container: test -d /home/robin/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e
[3306 ms]
[3306 ms]
[3306 ms] Exit code 1
[3306 ms] Start: Run in container: test -d /vscode/vscode-server/bin/linux-x64/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e
[3307 ms]
[3307 ms]
[3307 ms] Start: Run in container: mkdir -p '/home/robin/.vscode-server/bin' && ln -snf '/vscode/vscode-server/bin/linux-x64/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e' '/home/robin/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e'
[3307 ms]
[3307 ms] mkdir: cannot create directory '/home/robin/.vscode-server': Permission denied
[3308 ms] Exit code 1
[3309 ms] Command in container failed: mkdir -p '/home/robin/.vscode-server/bin' && ln -snf '/vscode/vscode-server/bin/linux-x64/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e' '/home/robin/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e'
[3310 ms] mkdir: cannot create directory '/home/robin/.vscode-server': Permission denied
[3310 ms] Exit code 1

setting the owner of the /home/robin folder to robin fixes the issue.

Bah, I should have left the devcontainer job running to continously validate this use case.


linkSocial cannot link to social accounts with different email

Is this suited for github?

[X] Yes, this is suited for github

To Reproduce

Create a user
Link a social account with a different email
error=email_doesn%27t_match shown in URL

Current vs. Expected behavior
Logged-in users should be able to link to social accounts in different emails
What version of Better Auth are you using?
1.0.20
Provide environment information
System:
OS: macOS 15.2
CPU: (8) arm64 Apple M1 Pro
Memory: 120.31 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 22.11.0 - ~/.n/bin/node
Yarn: 1.22.19 - ~/.n/bin/yarn
npm: 10.9.0 - ~/.n/bin/npm
pnpm: 9.15.0 - ~/.n/bin/pnpm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Browsers:
Safari: 18.2

Which area(s) are affected? (Select all that apply)
Backend
Auth config (if applicable)
import { betterAuth } from "better-auth"
export const auth = betterAuth({
emailAndPassword: {
enabled: true
},
});

Additional context
Afterward, users should be able to log in to accounts with different email addresses by binding social accounts without creating a new account.

Better Auth currently works with only one specific email per user. It does not support multiple emails for a single user.

I got it, thanks for your reply

Is there a supported plan, or can we submit a PR to modify this design? It's common for users to use different emails on different platforms, I don't think this is a user-friendly design.
Additionally, there's a related issue: once a user changes their GitHub email, logging in with the same GitHub account will be recognized as a new account, and they will no longer be able to access their previous account.

Oof yea this is a pretty big one. Almost everyone I know uses different emails for some different providers. Connecting a provider shouldn't require a matching email, it should simply attach that provider to the user and prevent that provider from being added to any other accounts

Is there a supported plan, or can we submit a PR to modify this design? It's common for users to use different emails on different platforms, I don't think this is a user-friendly design.

Managing multiple emails requires workarounds. It should probably be implemented as a plugin to avoid fundamental changes. But, if you have any ideas, I’m happy to take a look. Also open for a PR.

Additionally, there's a related issue: once a user changes their GitHub email, logging in with the same GitHub account will be recognized as a new account, and they will no longer be able to access their previous account.

yeah this should be reported separately. we should be able to link accounts based on the id returned from the provider.


related_images in images.google

each result in images.google have 7 related images and one related link, how i can download 7related images in each images result ?
i'm tried with --related_images but i think it only work with words not link

closing this as duplicate of #173


moleculer-elasticsearch invalid apiVersion

Getting the following error running moleculer-elasticsearch:
Invalid apiVersion "5.4", expected a function or one of 7.0, _default, 6.7, 6.6, 6.5, 6.4, 6.3, 6.2, 6.1, 6.0, 5.6, 2.4, 1.7, 0.90, 6.8, 7.1, 7.x, master

My service looks like this:
name: 'storyblok',
  mixins: [ESService],
  settings: {
    elasticsearch: {
      host: env.STORYBLOK_ELASTICSEARCH,
    },
  },
}

docker-compose:
version: '3.4'
services:
  elasticsearch:
    image: elasticsearch:5.5.0

Overwrite it in
name: 'storyblok',
  mixins: [ESService],
  settings: {
    elasticsearch: {
      host: env.STORYBLOK_ELASTICSEARCH,
      apiVersion: "5.6"
    },
  },
}


Correction for raw affiliation Institut Scientifique de Recherche Agronomique - INRA > AMAP >  >  >

Correction needed for raw affiliation Institut Scientifique de Recherche Agronomique - INRA > AMAP >  >  >
raw_affiliation_name: Institut Scientifique de Recherche Agronomique - INRA > AMAP >  >  >
new_rors: 00g218c19;020nks034
previous_rors: 00g218c19
works_examples: W2285306351
contact: 31770d8df8795cb08ce5f293ee63f8ef:dc843ad9a44c9b745262cfa6ac30daa857a3 @ inrae.fr

This issue was accepted and ingested by the OpenAlex team on 2024-11-18. The new affiliations should be visible within the next 7 days.


Following the license change, modify the boilerplates in crypto/pkcs7/

Merged.
b7617a3a99285596367990fba4f17ba10b7566b2 Following the license change, modify the boilerplates in crypto/pkcs7/


Data not updating

Hi,
Is there is a reason the google docs spreadsheet contains data as of the 29th, but the data in this repo is only as of the 27th? Ideally we'd love to be using the most current source, but the github repo is the easiest to work with from an automation perspective, so just wondering if we need to switch to the Google docs spreadsheet, or there is a plan to make sure the github repo stays current?
Thanks.

Sorry about that, resuming regular data updates now - I just updated the data in this repo. Will keep current to the Google docs spreadsheet going forward, with a delay of at most a few hours.

Thank you!

@rameezsadikot
You could also do like this to update your csv files.
curl https://covidtracking.com/api/states.csv -o states_current.csv
curl https://covidtracking.com/api/states/daily.csv -o states_daily_4pm_et.csv
curl https://covidtracking.com/api/states/info.csv -o states_info.csv
curl https://covidtracking.com/api/us.csv -o us_current.csv
curl https://covidtracking.com/api/us/daily.csv -o us_daily.csv
curl https://covidtracking.com/api/counties.csv -o counties.csv


Disable CocoaPods input and output paths in Xcode build phase and adopt new Xcode build system

https://github.com/flutter/flutter/commit/ef792fc30db2d062674c2a8a635cb8305c6433c4 was reverted with https://github.com/flutter/flutter/commit/9734f4ed43eef148a354ac4f1e7118883434e2d3 to wait for the minimum CocoaPods version to propagate through the macOS CI slaves.  They are now updated to 1.6.0.

This restores the revert from https://github.com/flutter/flutter/pull/33684.


More detailed error context

Hello! Digging ts-rest for the first time. I like the API a lot, feels cleaner than Zodios (and not even comparable to tRPC complexity). There's one thing I've noted.
In Zodios Server implementation the error response is contextualized:
{
  "context": "body"
  "error": [{"path": "filters", ...}, ...]
}

In Ts-Rest it's not clear WHICH part of request has the error:
{
  "issues": [{"path": ["filters"], ...}, ...]
}

^ it can be a path placeholder, a query variable or a body field. IMO either context like in Zodios should be present or (alternatively) path can be prepended with one of 3 clarifying constants, e.g.:
{
  "issues": [{"path": ["body", "filters"], ...}, ...]
}

What do you think?

This is already possible with all the server libraries through different options. Which server library are you using?

Thank you! After I learned it's possible it was easy to find a starting point here: https://ts-rest.com/docs/express/#request-validation-error-handling
Here's an example for other potential seekers:
createExpressEndpoints(contract, mainRouter, app, {
  requestValidationErrorHandler: (err, req, res, _next) => {
    return res.status(400).json({
      context: (
        err.body ? "body" :
        err.pathParams ? "pathParams" :
        err.query ? "query" :
        err.headers ? "headers" : "unknown"
      ),
      issues: err.body?.issues || err.pathParams?.issues || err.query?.issues || err.headers?.issues,
    })
  },
})

I'm shocked there's even a header validation 🤯 , great work Youssef!


Idnits generates false positive for figures with Unicode characters

I have draft that use Unicode characters in drawing (https://www.ietf.org/archive/id/draft-smn-idr-inter-domain-ibgp-03.txt). Running thus draft through https://author-tools.ietf.org/idnits results in 151 errors as follows:
"Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding"
Similar issue was opened in the past (issue #2574), which suppose to be fixed. However, false positive are still there.

The endpoint above is running the older idnits, not idnits3 which is under development.

OK. Sorry,
Let me close this issue, and open another issue for idnits2.
//Krzysztof

On Jun 4, 2024, at 19:42, Robert Sparks @.***> wrote:
The endpoint above is running the older idnits, not idnits3 which is under development.
—
Reply to this email directly, view it on GitHub https://github.com/ietf-tools/idnits/issues/34#issuecomment-2148077050, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUXPIBBGCKZOMYMI3D3CXUDZFX37ZAVCNFSM6AAAAABIYPVBJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBYGA3TOMBVGA.
You are receiving this because you authored the thread.

Closing this issue, and opening new issue for idnits2.


Create designs for data default views

Client would like to see curated data sets lists for: 1)resources and energy; 2) agriculture and food; 3) tourism.
There have been 2 options discussed so far:

[ ] 3 curated data lists for displayed in the main catalogues sections, together with the current list of datastes, displayed under an "all data" subsection.

[ ] 3 new tabs, at the top of the preview page, next to 'Data catalogue' and "My data" existing tabs. The display of all datasets, in the current catalogue would remain unchanged (as another way for discovering data).

Austrade has approved the new designs and would like them implemented in the prototype by 15th of October if possible. @steve9164 please assess the timeframe needed to have them done, so I can advise Austrade if 15th is not realistic.

I'll need a couple of days to properly estimate the overall time. As well as implementing multiple catalogues in tabs, this would require restructuring the catalogue for Ag & Food and Tourism.

@steve9164 you may want to look at something similar that was worked on previously to see if it's useful (I guess otherwise it may be time to close that one off if we're not going to use it): https://github.com/TerriaJS/terriajs/pull/2353

done


Add missing # to README of babble-bubbles

Add "#" to import

I am submitting

[ ] a new package
[ ] an update for a package

Description: Explain what the package does and why it's useful.

I have read and followed the submission guidelines and, in particular, I

[ ] selected a name that isn't the most obvious or canonical name for what the package does
[ ] added a typst.toml file with all required keys
[ ] added a README.md with documentation for my package
[ ] have chosen a license and added a LICENSE file or linked one in my README.md
[ ] tested my package locally on my system and it worked
[ ] excluded PDFs or README images, if any, but not the LICENSE

Thanks!


npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents

Laravel Mix Version: 4.0.12
Node Version (node -v):9.4.0
NPM Version (npm -v):5.6.0
OS:

Description:
When I run npm run production I get:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

Steps To Reproduce:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

It's only a warning.


[esp32] Post server initialization to the scheduler in examples

Problem
Directly initializing the server in the main task causes potential data race and stack overflow.
Fixes https://github.com/project-chip/connectedhomeip/issues/10430
Change overview
The initialization is now posted to the scheduler on ESP32 platforms.
Testing

Manually built and run the modified apps.
Github CI

@dhrishi @pan-apple PTAL

@pan-apple @bzbarsky-apple PTAL


Remove once_cell crate from dependencies

Which issue does this PR close?
N/A
Rationale for this change
This should be merged after https://github.com/apache/datafusion/pull/12601
When looking at https://github.com/apache/datafusion/pull/12601 I noticed that the once_cell crate is still listed as a dependency, but there are no usages of it in the codebase, aside from one test that could move to LazyLock instead.
What changes are included in this PR?
Remove the unused once_cell dependency and replace the usage of it with LazyLock.
Are these changes tested?
Tested by CI
Are there any user-facing changes?
No

Closing as we can't bump MSRV for now ref: https://github.com/apache/datafusion/pull/12601#issuecomment-2372731455


[RTL] Fix image click detection.

Fixes https://github.com/godotengine/godot/issues/70053

Thanks!


Refactor constants to Swift enums

Move some #define in Constants.h to Swift enums in Constants.swift. Now they can be used in both languages.

Hey @nielspl, thanks for this! Would it be possible to change the prefix for the new constants from MA to VNA? This is something I've slowly been doing in previous pull requests.
Thanks again!

Hi @josh64x2 , MA is renamed to VNA


Fixes KVM_EXIT_FAIL_ENTRY on Intel CPU

Not sure why does Intel violate this spec.
Fixes #905.

Just looking on the other KVM examples and see what are the different.

I confirm that it works. Now I'm on the Vulkan::update todo.

By the way, you plan to load the game executable by injecting a syscall into the vm?

Sorry I don't understand what you mean. We should do it the same way as the PS4 does, which is fork from thread0 then exec the mini-syscore.elf.

My question is answered. I did phrase it awkwardly though, I admit


fix: compile sdk without xcode error app extensions

fix: disable code for app extension targets
fix: cocoapods tracking SDK not compiling
Revert "Merge branch 'levi/fix-common-cocoapods' into levi/compile-notification-service"
fix: cocoapods compiling of SDK
disable config in app extensions
make config optional
got app to compile

Complete each step to get your pull request merged in. Learn more about the workflow this project uses.

[ ] Assign members of your team to review the pull request.
[ ] Wait for pull request status checks to complete. If there are problems, fix them until you see that all status checks are passing.
[ ] Wait until the pull request has been reviewed and approved by a teammate
[ ] After pull request is approved, and you determine it's ready add the label "Ready to merge" to the pull request. A bot will squash and merge the pull request for you after the label is added.

Pull request title looks good 👍. If this pull request gets merged, it will cause a new release of the software.
Example: If this project's latest release version is 1.0.0. If this pull request gets merged in, the next release of this project will be 1.0.1.
To merge this pull request, add the label Ready to merge to this pull request and I'll merge it for you.

Warnings

:warning:

I noticed file Tests/Tracking/APITest.swift was modified. That could mean that this pull request is introducing a breaking change to the SDK.
If this pull request does introduce a breaking change, make sure the pull request title is in the format:
<type>!: description of breaking change
// Example:
refactor!: remove onComplete callback from async functions

:warning:

I noticed file Tests/MessagingPushFCM/APITest.swift was modified. That could mean that this pull request is introducing a breaking change to the SDK.
If this pull request does introduce a breaking change, make sure the pull request title is in the format:
<type>!: description of breaking change
// Example:
refactor!: remove onComplete callback from async functions

:warning:

I noticed file Tests/MessagingPushAPN/APITest.swift was modified. That could mean that this pull request is introducing a breaking change to the SDK.
If this pull request does introduce a breaking change, make sure the pull request title is in the format:
<type>!: description of breaking change
// Example:
refactor!: remove onComplete callback from async functions

  Generated by :no_entry_sign: dangerJS against 4448c5a52578f39080dfb16693e68699b3431db9

:tada: This PR is included in version 1.2.0-alpha.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

Test this bug fix in your app by....

Installing 1.2.0-alpha.2 of the SDK into your Podfile.
Delete these lines of code from your Podfile as it's a current workaround.
pod install
Compile your app. See if Xcode builds without errors explain in this issue

:tada: This PR is included in version 1.2.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[QUESTION] Partially phased VCF as input

(I was unable to find an answer by reading the documentation.)
If an input VCF is partially phased, would Shapeit5 apply its phasing logic to all variants regardless they are phased or not?
Or, it would only try to phase the variants yet to be phased?

I am also wondering about this.
Taking the liberty to tag @odelaneau


Prevent xlsx shared strings file based caching

I'm currently updating my spout implementation from version 3 to 4 and I stumbled about a undocumented (and maybe unintended) breaking change.
For XLSX Shared Strings you have the class OpenSpout\Reader\XLSX\Manager\SharedStringsCaching\CachingStrategyFactory. This class trys to decide whether to use the InMemoryStrategy or the FileBasedStrategy. Previously this factory class was not final and extendable. We used this to prevent the usage of the FileBasedStrategy because it slows down to whole process extremly - we would rather let the script die instead of slowing it down. So previously we just extended the CachingStrategyFactory with our own class:
class CachingStrategyFactory extends \OpenSpout\Reader\XLSX\Manager\SharedStringsCaching\CachingStrategyFactory
{
    /**
     * Returns the best shared strings caching strategy.
     *
     * @param int|null $sharedStringsUniqueCount Number of unique shared strings (NULL if unknown)
     * @param string $tempFolder Temporary folder where the temporary files to store shared strings will be stored
     * @param HelperFactory $helperFactory Factory to create helpers
     * @return CachingStrategyInterface The best caching strategy
     */
    public function createBestCachingStrategy($sharedStringsUniqueCount, $tempFolder, $helperFactory)
    {
        return new InMemoryStrategy($sharedStringsUniqueCount);
    }
}

In version 4 the CachingStrategyFactory is now final and don't has any usable interfaces which could be used instead. The only way I could hack the old behaviour together would be to create a CachingStrategyFactory with a fake memory limit - something like this:
$cachingStrategyFactory = new CachingStrategyFactory(new MemoryLimit('1tb'));
$reader =  new XlsxReader(null, $cachingStrategyFactory);

I currently see three options to resolve this:

Remove the final from the CachingStrategyFactory class again.
Create a CachingStrategyFactoryInterface and replace the typehints for CachingStrategyFactory with the interface. This shouldn't break anything.
Add an option to the CachingStrategyFactory to enforce any CachingStrategy.

Option 2 would probably the cleanest solution. Option 1 is by far the easiest and fastest.

Create a CachingStrategyFactoryInterface and replace the typehints for CachingStrategyFactory with the interface. This shouldn't break anything.

I'd love to see a PR with this :+1:


fix java code style

What type of PR is this?

/kind cleanup

What this PR does / why we need it:
fix java code style

java Constructor default public
Arrays.asList(new String[] { "p", "n" }) => Arrays.asList("p","n")
change Notes kube to kubernetes
Which issue(s) this PR fixes:

Special notes for your reviewer:
Does this PR introduce a user-facing change?:
None

/assign @aledbf

/assign @idvoretskyi

/lgtm


[🎭] UI harmonization towards facelifted design

Some old screens as well as all screens newly added during GSoC 2019 might currently not be in visual harmony with the facelifted/UX-improved designs by @MarcRler. Their components should be checked for compliance and if needed be reworked towards the same Material design and usability goals.

[x] accounting
[x] address
[x] address-create
[x] address-select
[x] administration
[x] basket
[x] challenge-solved-notification
[ ] challenge-status-badge
[x] delivery-method
[x] deluxe-user
[x] error-page
[x] forgot-password
[x] oauth
[x] order-completion
[x] order-history
[x] order-summary
[x] payment
[x] payment-method
[x] photo-wall
[x] product-details
[x] product-review-edit
[x] purchase-basket
[x] recycle
[x] saved-address
[x] saved-payment-methods
[ ] score-board
[x] server-started-notification
[ ] token-sale
[x] track-result
[x] user-details
[x] wallet

@bkimminich I'd like to work on this issue. Just wanted to know if I am guessing it right?

all the components u have mentioned are to be refactored (in terms of UI)

the improved designs should be similar to or in concordance with "facelifted/UX-improved designs by @MarcRler"

Where can I get the idea about "facelifted/UX-improved designs" And once I get this, all I have to do is improve each component's UI

All components not listed above are considered "facelifted" and can serve as examples.

In general the goal is a consistent look and feel that is in accordance with https://material.io/design/ guidelines.

Thanks for help!
I'll split the work  into number of PRs, one for each component

This is part of the upcoming OWASP Projects Summit work items.

@MarcRler, I just noticed that the screen flow when doing a deluxe-upgrade is a bit weird: It's logging you out, throwing you back to the login screen and not showing any confirmation message that you successfully upgraded. I won't open a separate ticket for it, as the deluxe-user screen is not yet done, but please take a look at this when you get to it. Thanks!

@MarcRler I'll not merge the current facelift for the upcoming v10.1.0 which will hopefully be released tomorrow, we'll save it for one of the next releases, ok?

Let's try the motivational tweet approach to get this one eventually resolved for good... https://twitter.com/owasp_juiceshop/status/1283530731097030658 👼

@bkimminich could I take the accounting component?
Thanks!

Sure, @rene-ph! 👍

I would like to take care of the deluxe user page

Whereby the page looks good so far. I just see that the payment options need some rework (at least in Safari).

Just merged the divider fixes on My Payment Options into develop. Thanks, @MarcRler!

The following are the only remaining screens which have not yet been tackled in the facelifting initiative:
Token Sale

Accounting

Order History

Deluxe User
(looks good to me, but if someone can think of any improvement, go ahead)

Score Board and Challenge-Status-Badge
(the toughest nut to crack design and usability wise, as performance cannot degrade any further)

Server-Started and Challenge-Solved Notifications

The following are the only remaining screens which have not yet been tackled in the facelifting initiative:
Token Sale

Accounting

Order History

Deluxe User
(looks good to me, but if someone can think of any improvement, go ahead)

Score Board and Challenge-Status-Badge
(the toughest nut to crack design and usability wise, as performance cannot degrade any further)

Server-Started and Challenge-Solved Notifications

Happy new year, @MarcRler! Would you by any chance be up to review and update the Token Sale and/or Order History screens? I think for the Score Board we need to plan a bit more time, maybe even make that a GSoC project for 2021. So I'd probably open a separate ticket for that and close this once the last two other screens are done.

Happy new year, @MarcRler! Would you by any chance be up to review and update the Token Sale and/or Order History screens? I think for the Score Board we need to plan a bit more time, maybe even make that a GSoC project for 2021. So I'd probably open a separate ticket for that and close this once the last two other screens are done.

hey @bkimminich I would like to work order-history component

hey @bkimminich I would like to work order-history component

hey @bkimminich I would like to work on token sale component

hey @bkimminich I would like to work on token sale component

hey @bkimminich I would like to work on token sale component

Awesome, feel free to! Please try to keep not just the visual end result but the HTML and SCSS structure too, as similar to other screens as possible.

hey @bkimminich I would like to work on token sale component

Awesome, feel free to! Please try to keep not just the visual end result but the HTML and SCSS structure too, as similar to other screens as possible.

Completed except for Score Board, which will be promoted as a GSoC 2021 project instead.

Completed except for Score Board, which will be promoted as a GSoC 2021 project instead.


updateStrategy in nginx-ingress-controller cannot be zero

Hi!
while we were installing the module version 1.13.1 we had the following problem:
DaemonSet.apps "nginx-ingress-controller-internal" is invalid: spec.updateStrategy.rollingUpdate.maxUnavailable: Invalid value: intstr.IntOrString{Type:0, IntVal:0, StrVal:""}: cannot be 0

What we did was to add the following jsonPatch:
- op: replace
  path: /spec/updateStrategy/rollingUpdate/maxUnavailable
  value: 1

Kubernetes version : EKS 1.22

Thank you @lzecca78 , we found later that this field is not working on 1.22, but should work on 1.23+.
Your patch is the correct fix for the version 1.22


Ledger app 2.0.4 fails to sign

Several users are reporting signing failures when using Ledgers with Bitcoin app version 2.0.4. The error is:
{"error": "('0x6a80', 'Error in <BitcoinInsType.SIGN_PSBT: 4> command', '')", "code": -13}

I am unable to replicate the issue with speculos on self built app version 2.0.4. However I was able to replicate using a Nano S Plus with the released app binary.
cc @bigspider

Found it, Ledger doesn't like h in key origin info.

Hello, i have the same issue. My english is not very good, i don't understand if you have found a solution or not ?

i don't understand if you have found a solution or not ?

I am working on a fix.

Talk to Ledgerwallet Support on the Live support chat so that your issue can be looked into.

Talk to Ledgerwallet Support on the Live support chat so that your issue can be looked into.

I don't think it fix it completely.
I have some tests that were passing before but now, I tried to sign a PSBT in testnet and I got the same error.
Then tried to sign a PSBT in mainnet, it worked, but only for legacy addresses. For segwit I get same error.

@NicolasDorier do you have a failing PSBT from those tests?
Is the previous transaction included in the PSBT?

@NicolasDorier Do your PSBTs have mixed input script types (e.g. a P2WPKH and a P2TR)? Or do you have SIGHASH_DEFAULT set? If so, see #608 and #609 respectively. Those are issues with the Ledger apps and not something that HWI can particularly fix. Otherwise please open a new issue.

Will open new issue with PSBTs and mnemonic. I don't have SIGHASH_DEFAULT nor P2WPKH

So for record @achow101, the error is also sent if you are using segwit without the non_witness_utxo. (didn't check if that's the case for taproot)
This is a breaking change with their old app which merely show a warning.

@NicolasDorier the new app is completely rewritten from scratch (and with a redisigned/incompatible API). I purposely added a number of limitations on what's allowed. In most cases, I don't expect the limitations to be relevant or even noticed (and limiting the user's behaviors to sane ones is useful for a number of reasons).
I wasn't aware that there is external software that still doesn't provide the non_witness_utxo, since it's been about two years that the segwit bug is known; I think I'll manage to add back the support (and the warning) by the next release (together with SIGHASH_DEFAULT support), since the severity of the segwit bug is rather limited after all.
On taproot, the non_witness_utxo is not required.

Update: version 2.0.6 of the app now allows signing segwitv0 transaction with no non_witness_utxo, with a warning.
SIGHASH_DEFAULT still planned for the next release.

confirming that version 2.1.1 fixes the above error message ( previous version 2.0.x )

A quick note : AFAIK, it is a confirmed compatibility issue with latest ledger firmware + ledger btc app and some multisig wallet like Sparrow.
As today, we just tested again, on september 6th : sparrow 1.6.6 with latest firmware for Ledger Nano S (2.1.0) still has this issue.  Same Issue with Ledger S+.
(The only 2.1.1 firmware release available is only for Ledger Blue)

@ididdid the current (2.0.6) version of the Ledger bitcoin app requires using SIGHASH_ALL instead of SIGHASH_DEFAULT. They are essentially equivalent in meaning, so it's safe to use SIGHASH_ALL.
Sparrow correctly uses SIGHASH_DEFAULT as the default choice, but I believe it is now possible to manually choose SIGHASH_ALL, and that should work. Please let me know if that is not the case, and I will investigate.
The upcoming version of the Ledger bitcoin app (ETA 1-2 months) will correctly support SIGHASH_DEFAULT as well.

I'm seeing the same on 2.0.6 of the Ledger bitcoin app and sparrow 1.7.0. I verified the PBST created used SIGHASH_ALL but I'm still seeing this error.

I'm seeing the same on 2.0.6 of the Ledger bitcoin app and sparrow 1.7.0. I verified the PBST created used SIGHASH_ALL but I'm still seeing this error.

Thanks for reporting!
That's strange − but the new Ledger bitcoin app (version 2.1.0) is coming within the next few weeks and it handles all sighash flags, so it will hopefully address this issue once and for all.

I'm seeing the same on 2.0.6 of the Ledger bitcoin app and sparrow 1.7.0. I verified the PBST created used SIGHASH_ALL but I'm still seeing this error.

False alarm. This ended up being unrelated to any issue with HWI or the bitcoin app for ledger. Turns out I had a misconfiguration in the sparrow wallet (correct XPUBs but a duplicate fingerprint for one of the signers). This was enough to get the 0x6a80 mentioned in the issue. After correcting the wallet I was able to sign again with a nano s plus and 2.0.6 bitcoin app.

How did you solve this problem of a duplicate fingerprint?

I had to get the fingerprints for all signing keys and configure the sparrow wallet with them. In this particular wallet I had setup to be watch-only and didn't intend to use for signing. Once I assigned the correct fingerprint to each signer, sparrow would correctly interface to the ledger bitcoin app to sign.


Add 'exclude_namespaces' also to SwaggerApiView

We are running the whole Django application in a subpath. When trying to exclude some url namespaces via "exclude_namespaces" settings only the suggested version works.

Thanks for this. Closing out as the new schema generator in DRF 3.4 is responsible for including/excluding url patterns.


”Corcova” is listed in the drop-down menu

Description:
"Corcova" is listed in the drop-down menu alongside its corresponding county and commune, according to the law.
Precondition:
The website is up an running.

Step 1
Type "Corcova" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Corcova, MEHEDINȚI".


CI: Use GitHub Actions along with AppVeyor

Currently, we use AppVeyor for Windows CI, but it takes about 20 minutes, and the test combination is not enough.
This PR enables GitHub Actions. The advantage of GHA is that it can run multiple jobs parallelly even with the free plan.
This tests the following combinations:

Compiler: MSVC 2019, MinGW-w64
Architecture: x64, x86
Features: HUGE, NORMAL
(Actually, two combinations are excluded from NORMAL to reduce the jobs.)

Other conditions are:

Enabled interfaces are Lua 5.4, Python 2.7, Python 3.8.
winpty is used for the terminal feature.
VIMDLL is enabled.

Each test takes less than 10 minutes. Here is the result:
https://github.com/k-takata/vim/actions/runs/186751314
The AppVeyor job is now simplified. It only tests MSVC 2010, x64, HUGE.
Now it takes about only 6 minutes.
https://ci.appveyor.com/project/k-takata/vim/builds/34360477
Note that GHA doesn't have MSVC 2010 installed. That's why we still need to use AppVeyor.
This also fixes v8.2.0388 which intended to enable PostScript but actually failed to enable it.

These tests appear to show up under "Actions" in github.  Can we get a link with an OK/fail status, like we have for the other CI jobs?

Open this page: https://github.com/vim/vim/actions?query=workflow%3A"CI+with+MSVC+and+MinGW-w64" .
You will find the "Create status badge" button on the top right part of the page.
I find that the text of the status badge is a bit long.
It seems that the text is taken from the "name:" part of the yaml file.

Ken Takata wrote:

Open this page: https://github.com/vim/vim/actions?query=workflow%3A"CI+with+MSVC+and+MinGW-w64" .
You will find the "Create status badge" button on the top right part of the page.
I find that the text of the status badge is a bit long.
It seems that the text is taken from the "name:" part of the yaml file.

Thanks.  I changed the name so it fits with the other badges.
Let's see how well this works.
--
From "know your smileys":
:-&	Eating spaghetti
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


Nightly build [DO NOT DELETE OR MERGE]

See pytorch/pytorch#26817 for what this does
CircleCI: https://app.circleci.com/pipelines/github/pytorch/audio?branch=nightly
FB only: Chronos job page: https://fburl.com/chronos/3ft16107 (click "Run Now" to manually trigger a nightly)

closing this in favor of https://github.com/pytorch/test-infra/actions/workflows/trigger_nightly.yml


Window despawns before PostUpdate

Bevy version
main (https://github.com/bevyengine/bevy/commit/1d5388eded1f999d7bfca0bea40011a1f60fac76)
What you did
Create a system that queries for Window in the PostUpdate system
What went wrong
This line right here in WindowPlugin:
https://github.com/bevyengine/bevy/blob/1d5388eded1f999d7bfca0bea40011a1f60fac76/crates/bevy_window/src/lib.rs#L126
The system that despawns the window entity runs during the Update system, this means there could be a situation where the window entity does not exist during the PostUpdate schedule. This happened to me and it caused a panic.
Additional information
This could be solved by putting the close_when_requested system in the Last or PostUpdate schedules instead. I don't know which is better though.

Possibly related: #7403

I've been messing around with window-related system schedules and I can't seem to fix the bug.
There's a lot of systems that require another system to do something which then triggers the system to do something, and that system requires another system, etc... It's confusing.

[ ] HCKR

This is still an issue as of b27896f.


Test if user list loads correctly.

profile karbaran namayesh dade nmishe

id to user list neshon dade nmishe

done


Sample code for PropertyDataCollection crashes

On this page, https://docs.microsoft.com/en-us/dotnet/api/system.management.propertydatacollection?view=dotnet-plat-ext-3.1, the sample code crashes on properties that don't have a description like Caption and Status.

This issue was moved to dotnet/dotnet-api-docs#5019


Added Java program Check If N and Its Double Exist

Hey there!, Thanks for submitting a PR to this repo
Please complete the following checklist for your PR to be approved. Mark the items by adding an x.
Example:  - [ ] Mark me as completed
To mark: - [x] Mark me as completed

[x ] My Pull Request adheres to the Contribution guidelines.
[ ] I have added readme.md and solution files in the appropriate folder.
[ x] The solution I have given is my own and not plagiarized in any form.
[x ] My solution passes all the testcases.
[ x] I have properly indented and documented my solution using comments.

If any of the above is unmarked, please make the necessary changes and then mark them so that you're PR can be approved and merged.

pls add comments in between the codes for better understanding.. and add readme.md with question link

@tomthomasvempala  the question is the same i just added the solution in java. so should i add the same link again? in the readme file

@thefool76 Please add a readme.md file with the problem link


add CLI arg to specify custom figlet font

allow user to specify custom figlet font path
will also need to make sure different "sized" fonts also respect the screen bounds

added with https://github.com/alefnull/dvd-term/commit/efa8bd09f9a36af2bd4c9d06d7b9ee0e5de48278.
works well in my limited testing so far. respects new font width/height and properly updates position based on them and the window bounds.
will test more with more fonts before updating releases.


Code for morphology is suboptimal and should be rewritten

Morphology functions are faster than their counterparts only because of parallel execution.  Very likely there is some bug that should be fixed

Current implementation has following drawbacks:

layout checks are unnecessary
border checks in get_pixel3d are unnecessary for footprint
border checks in get_pixel3d are unnecessary for inner pixels of input tensor

It is reasonable to figure out how last 2 problems are adressed in the original scipy code

closed by #31


Google play?

Hello
Will you publish it in Google play?

If you are interested I can try and do it for sure.

i am interested plus there is no other working app that works with private key or i have not find it.

Unfortunately you have to pay to upload an app to the Google Play Store. I added a compiled apk to the repo. You can download that and install it with this link: https://github.com/Belval/ki4a/raw/master/ki4a.apk

Thank you i will try it.
I found another app in the google play but i can not connect with private.key only with password.
https://play.google.com/store/apps/details?id=id.brooboox.sshtunnelmaker
Have you checked?


hjson icon in sidebar

Do you have a link/documentation on what IntelliJ expects to display an icon?

@laktak I know no more than you do - I could google it for you when I have time. (not sarcasm!)

I don't think it's possible but let me know if you find something.


Correction in the Mutual TLS section

[Enter feedback here]
Regarding this content here:
Another alternative for restricting incoming traffic is mutual TLS (mTLS). Manual TLS is a security protocol that ensures that both the client and server in communication are authenticated.
I believe the "Manual TLS" at the beginning of the second sentence should be "Mutual TLS"

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

ID: d6a78e94-c4d5-b382-7774-3fb3f1f7077d
Version Independent ID: d6a78e94-c4d5-b382-7774-3fb3f1f7077d
Content: General considerations for choosing an Azure container service - Azure Architecture Center
Content Source: docs/guide/container-service-general-considerations.md
Service: architecture-center
Sub-service: azure-guide
GitHub Login: @MarcosMMartinez
Microsoft Alias: julng

Good catch, Darrell. We'll take care of this.

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


Show project and viz name in viz list

Description

This adds the info to the backend needed for the ultimate design.
NOTE: the table render design still needs work.
NOTE: I'm not sure on the best way to avoid N+1 queries here. Please advise.
Test and Reproduce
Outline the steps to test or reproduce the PR here.

try endpoint, http://localhost:3000/visualizations.json?domain=library
see data for both heatmap and phylo tree
see correct titles for  heatmap and phylo tree
try same in viz list UI

I changed the PR so that the name of a visualization is stored in the database, eliminating the N+1 queries at read time. Likewise, the sample ids of a phylo tree are stored.
To make sense of the class, I refactored phylo tree methods such as job_command to be all private when not called outside the class  . Please sanity check.

Did you discuss this naming strategy with Jenn?

No, that's a good idea. @happyimadesignr: I came up with an auto naming algorithm for showing the heatmaps in the visualization list.   It will makes a string such as "Patient 016 (CSF) and 015 (CSF)" from the two samples "Patient 016 (CSF)", "Patient 015 (CSF)". What do you think?

Did you run a test phylo tree?

I ran it but it never seems to get past:  "Computation in progress. Please check back later!". Same in master. Can I test in staging or is the a better way?

Hey @gregdingle and @tfrcarvalho

I think it's nice to include the project name, but I would put it in the table column instead of the name. I don't thinking including the samples names in the title will be scalable for a lot of samples.
For Phylo trees, they already have a name, so it should display the name the user made.
For Heatmaps, I was thinking that it could just be called "Heatmap" or "Untitled Heatmap" and the user can name it. Then the table details will help differentiate the heatmaps from each other if the user doesn't explicitly name it. Or we can also have users name it when they save for the first time. For the minimum version, why don't we called it Heatmap and complete the table columns? What do you think?

https://chanzuckerberg.invisionapp.com/d/main#/console/16827472/350949082/preview

@happyimadesignr

I think it's nice to include the project name, but I would put it in the table column instead of the name.

Yea, that was always my intention. I didn't have time to add the columns when I first wrote this PR.

For Heatmaps, I was thinking that it could just be called "Heatmap" or "Untitled Heatmap" and the user can name it.

Ok, that will work, and is simpler. We can keep the auto name idea in mind for we add the ability to name heatmaps.
About the project name, how do you want to handle the case when there multiple projects for one visualization?


[FEATURE REQUEST] : I want to add documentation.md/yml File for GitHub ISSUE_TEMPLATES in Future Use

GSSOC'23 Contributor
Description
Is your feature request related to a problem? Please describe.
documentation.yml (Custom ISSUE_TEMPLATE):

The documentation.yml file serves as a custom ISSUE_TEMPLATE for your GitHub repository, specifically focused on documentation-related issues. When contributors or users of your project want to report documentation-related problems, improvements, or requests, they can create a new issue using this template.
The contents of documentation.yml could include prompts or guidelines to help users structure their documentation-related issue reports effectively. For example, it might ask them to provide specific details about the section/page of documentation they found confusing, suggest possible improvements, or even ask for clarifications about the issue they are experiencing.

Describe the solution you'd like

Only add that File is Our Solution

Describe alternatives you've considered

No alternatives

Additional Information
Context
Provide any additional context or information that helps explain the feature request.
Potential Implementation (optional)
If you have any ideas or suggestions on how the feature could be implemented, please share them here.
Screenshots or Mockups (optional)
If applicable, include any screenshots, mockups, or visual representations of the requested feature.
Priority (optional)
Please indicate the priority level of this feature request (e.g., High, Medium, Low).
Additional Notes (optional)
Add any other notes or comments about the feature request here.

Hi @Abhirup-02 . Please take a review on this Issue as soon as Possible. Thank You !


Params are non-assignable

struct Param(VALUE_TYPE) contains a const Config* config, which disables the assignment operator for the whole struct. Perhaps you meant const(Config)* config?

Or even immutable(Config)* config to state the intent more precisely. Turning const into immutable is a backwards-compatible change.

Although it can be made immutable I prefer not to do that - "const" allows more flexibility to change implementation if needed.


Global and Individual Enable/Disable flags for Management endpoints

Currently Steeltoe does not fully implement a Global and individual enable for management endpoints. While setting the global or individual tags is honored by the "cloudfoundry" actuator endpoint, the individual endpoints function as usual. In Spring boot actuator endpoint beans configured with enable false are not injected. In Steeltoe, the easiest thing to "Disable" is not Add the respective actuator. However in order to be more like with Springboot, it would be good to have the endpoints respect the enable/disable configuration flags, even though they were explicitly added in the DI setup.

Fixed by PR #24 , the commit is Fixed by https://github.com/SteeltoeOSS/Management/commit/aebe63be9910f1c80cbc087490a85a6cf140dbb5


Docker login with non-root artifactory path

This issue is about using docker login in combination with a private registry hosted on https://xxx/artifactory/docker-registry/.
Output of docker version:
$ docker version
Client:
 Version:      1.11.0
 API version:  1.23
 Go version:   go1.6.1
 Git commit:   4dc5990
 Built:        Thu Apr 14 00:24:28 UTC 2016
 OS/Arch:      darwin/amd64

Server:
 Version:      1.11.0
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   4dc5990
 Built:        Wed Apr 13 19:36:04 2016
 OS/Arch:      linux/amd64

Output of docker info:
Containers: 105
 Running: 1
 Paused: 0
 Stopped: 104
Images: 113
Server Version: 1.11.0
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 410
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 4.1.19-boot2docker
Operating System: Boot2Docker 1.11.0 (TCL 7.0); HEAD : 32ee7e9 - Wed Apr 13 20:06:49 UTC 2016
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 996.1 MiB
Name: default
ID: 5NOJ:34RG:XLCK:JKGF:GU6Y:JQPM:CHFX:VJ73:6MB7:KWYE:Z43I:XGQO
Docker Root Dir: /mnt/sda1/var/lib/docker
Debug mode (client): false
Debug mode (server): true
 File Descriptors: 17
 Goroutines: 37
 System Time: 2016-05-18T10:56:14.23235802Z
 EventsListeners: 0
Registry: https://index.docker.io/v1/
Labels:
 provider=virtualbox

Additional environment details (AWS, VirtualBox, physical, etc.):
OSX on Macbook Pro
Steps to reproduce the issue:

$ docker login https://xxx/artifactory/docker-registry/
Type username and password
Got the following response:

Error response from daemon: Get https://xxx/v1/users/: remote error: handshake failure

Describe the results you received:
Forget about the handshake failure, this is because the SSLVerifyClient policy in use.
What I am rather surprised of is Docker tries to fetch data from https://xxx/v1/users/ rather than https://xxx/artifactory/docker-registry/v1/users/.
Because we use artifactory, hubs and registries are not hosted at the root of the URL.
Is that the intended result?

As far as I'm aware, those paths are not configurable, and having them at the "root" is part of the specification; https://docs.docker.com/registry/spec/api/
Have you contacted Jfrog/Artifactory about this?

@oncletom: I think you've configured your Artifactory install incorrectly. The standard reverse proxy setup for Apache or Nginx in front of Artifactory redirects the Docker URLs as Docker expects them. As noted on https://www.jfrog.com/confluence/display/RTF/Configuring+a+Reverse+Proxy using a reverse proxy is required with Docker.
E.g. here's a snippit out of the Artifactory reverse proxy configuration generator for nginx:
    rewrite ^/$ /webapp/ redirect;
    rewrite ^//?(/webapp)?$ /webapp/ redirect;
    rewrite ^/(v1|v2)/(.*) /api/docker/$repo/$1/$2;

That's correct — plus we were facing an issue with cert-based authentication with a field containing an email address.
Thanks for your support :-)


docs(geometry): fix the error in visible status of Keypoint2d

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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 83.343%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5564

Relevant Lines:
6676

💛  - Coveralls


entering code and run in the interactive window is extremely slow

Version: 2020.1.58038 (13 January 2020)
I have a dataframe with shape of (810103, 26). If I type code and run a cell from the editor, everything is fine. But it will be extremely slow if I run code from the interactive window directly such as df.head(), df.columns. I can even make a screenshot without shortcut😂

Some of the advice here seems to alleviate the problem:
jupyter/notebook#3224
I typed this in to the interactive window:
%config Completer.use_jedi = False

and now it responds immediately. At least with the csv you mentioned above.

This fixed the issue for me as well.

Finally had a chance to profile the IPython kernel. The autocomplete from typing is hanging the kernel and preventing the execution of a cell. We should be able to fix this by interrupting the kernel if it's in the middle of autocompletion.

I experienced the same issue with slow executions with simple commands like .shape or .head().
However I also observed the following: I only experience the lag if I type the command into the IPython console, but if I select the command from the history it does not lag.

%config Completer.use_jedi = False

This actually solved the issue so far.

However I also observed the following: I only experience the lag if I type the command into the IPython console, but if I select the command from the history it does not lag.

This further points out what I found out while debugging. If you just up arrow on the history, it won't cause autocompletion to fire so the kernel won't be busy doing that when executing.

%config Completer.use_jedi = False
...solves  it for me as well. But I'm a little unclear on how to add this to startup commands, as @rchiodo suggests. Is this correct?
!
Capture

No, that was not correct. Jupyter: Run Startup Commands was throwing error about invalid type "expected Array". So, wrapping in brackets might work...at least it makes the error go away. Since this problem is sporadic and random, I won't immediately know if this fixed the issue.

this is a bit annoying..just to get the shape of a dataframe it takes a while

@nemar3 did you follow the advice above?
%config Completer.use_jedi = False

Either put this in your startup commands or run this first in the interactive window.

@rchiodo yes I did add it before and it didn't help then..but I added it again and now it seems to have helped...

Closing for now as it seems most issues have been resolved. Please enter a new bug if necessary.

This is not fixed. We still need to address this.

Longstanding bug, and the workaround seems to alleviate the situation for the most part. Moving to October.

Why don't we keep track of the pending completion requests & let users know that things are slowing down because of Jedi in the kernel & ask them to just turn this off.
Some (if not most, totally guessing here) users will want this, to get better completion.
Feel its better to let them know when things are slowing down & what they can do.
Just like in VS Code core, they let users know what extension is chewing up CPU process & slowing VS Code down, then Users can optionally blitz that extension. Similarly users can opt into disabling jedi completely (we can just add that into a startup command if they click yes and if they want they can go back and just remove that line from the settings.json startup commands)

Yeah I wanted an automated solution. We didn't originally just do make this a startup command because we never spent the time to investigate what the possible side effects of this were. Why is this not the default for jupyter in the first place?

ust make this a startup command because we never spent the time

I agree, we should get to the bottom of the issue, rather and applying a bandaid fix.

It looks like we already implemented the 'disable jedi for kernels'. Code is here.
https://github.com/microsoft/vscode-jupyter/blob/e567b896aec30a7bb811a3f7b135f4a96ea2f1df/src/client/datascience/jupyter/kernels/kernel.ts#L527
Closing this as I don't repro it anymore with that setting enabled.

I also had same problem. After some searching online, I think i found how this problem occured and how to alleviate it.
This long hangs occured after I updated my conda version and at the same time my ipykernel also needs to update to higher version. I guess it is because of the version of ipykernel. In my case is: 6.4.1.

create a new virtual env
set ipykernel version as 5.3.4
before run code in cell, run conda install jupyter. This ensure vscode will not upgrade your ipykernel directly.


feat: support context propagation through links

This pull request extends the rack instrumentation library to support context propagation through links.
Several libraries have this feature, for example que and otel-http  lib.
Our use case is simple, we want to connect our frontend & backend traces using links, as opposed to having the frontend be the source of the root span, as that's messing with our sampling. We have had our fork running in production for a while now, just thought to upstream it.
I'm basically brute-forcing my way through ruby, so any sort of style suggestion is welcome.

I think it should be ok as it is an option and the rationale behind it seems logical to me.
However, I do have a few formatting suggestions, which you may consider or ignore as you see fit.
if propagate_with_link&.call(request.env)
  links = prepare_span_links(parent_context)
  span = create_root_span(request, links)
else
  span = create_span(parent_context, request)
end

Additionally, I'm unsure whether option :propagate_with_link should be a callable or rather as an array of links (i.e. array of link is more restricted on options in my opinion).

@gwuah, what do you think about Ariel's comment?

Related suggestion that would have offered the same feature, and has a similar implementation in other SDKs (Go and JS, maybe others):
https://github.com/open-telemetry/opentelemetry-ruby-contrib/pull/130

Thanks, @arielvalentin for bringing this to the maintainers slack channel. What was the conclusion/next steps drawn from your conversation?

Thanks, @arielvalentin for bringing this to the maintainers slack channel. What was the conclusion/next steps drawn from your conversation?

I got very limited engagement on the topic with links to existing issues, which to be honest I have not read yet:
https://github.com/open-telemetry/opentelemetry-specification/pull/3877
https://github.com/open-telemetry/opentelemetry-specification/issues/3867
Something that is required by Golang library instrumentations is that users have to register specific endpoints to be traced or not and have more control over what handlers should ignore in the incoming trace headers and start a new trace.
That allows them more granular control of when to consider creating a new trace id as opposed to what something like Rack does where currently have a single Event Handler injected for all requests.
A lot of routing is also handled by the frameworks themselves and tend not to rely on Rack figuring out what needs to process a request.

Other instrumentation already use propagation_style, is there any reason this could not be done vs a callable proc?

@zacheryph

it's a callable because we want to dynamically enable/disable this feature, based on stuff in headers, etc.


feat: detect nurfiles as nu and add a sample nurfile

nur is a job runner, like just but on nu

seems good to me. thanks!


Started migration to scim bridge

@dependabot rebase

Codecov Report

Merging #396 (798e9dc) into master (2ef5c02) will decrease coverage by 1.83%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##           master     #396      +/-   ##
==========================================
- Coverage   62.77%   60.95%   -1.83%
==========================================
  Files          14       13       -1
  Lines         771      735      -36
==========================================
- Hits          484      448      -36
  Misses        277      277
  Partials       10       10

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


How to access other field of the model in custom serializer

How to access other field of the model from custom serializer
I need to deserialize to various data types based on the value of the type field. For ex. if type is "int" then i'll deserialize db value into an int, same way it'll be done for float, string and bool.

I've searched for this in the docs & the issues tab but I think I didn't found it.

Here's my model
type Setting struct {
	ID uint `json:"id" gorm:"primaryKey"`

	Key            string                   `json:"key" gorm:"type:varchar(80); not null;uniqueIndex;"`
	Value          serializers.SettingValue `json:"value" gorm:"type:text;"`
	Type           string                   `json:"type" gorm:"type:varchar(100); not null;"`
	// ....

	CreatedAt time.Time `json:"created_at" gorm:"type:datetime"`
	UpdatedAt time.Time `json:"updated_at" gorm:"type:datetime"`
}

Here's the serializer
type SettingValue struct {
	Val any `json:"val"`
}

// Scan implements schema.SerializerInterface (db out)
func (sv *SettingValue) Scan(ctx context.Context, field *schema.Field, dst reflect.Value, dbValue interface{}) (err error) {

	// find out the type (---- THIS step is crucial to determine the deserialization data type)
        dst.Elem().FieldByName("Type") // ""

        // becuse the following
        // fmt.Printf("dxx %#v \n", dst.Elem())
        // produces following (only ID & Key has value others are zero value, but the db has value for them
        //model.Setting{
	//	ID:0x1,
	//	Key:"test_1",
        //      Type: "",
	//	Value:serializers.SettingValue{Val:interface {}(nil)},
	//	// ...
	//	CreatedAt:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC),
	//	UpdatedAt:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC)
	//}

	// decode value base on the type

	switch val := dbValue.(type) {
	case []byte:
		sv.Val = bytes.NewBuffer(val).String()

	default:
		err = fmt.Errorf("unsupported data type (%T) in value", val)

	}

	return
}

// Value implements schema.SerializerInterface (db in)
func (*SettingValue) Value(ctx context.Context, field *schema.Field, dst reflect.Value, fieldValue interface{}) (interface{}, error) {
	sv, ok := fieldValue.(SettingValue)
	if !ok {
		return nil, errors.New("setting value field should be type of SettingValue")
	}

	var r any

	switch v := sv.Val.(type) {
	case string, int, uint, float64, bool:
		r = v
	default:
		return nil, fmt.Errorf("invalid value type %T in field %s", fieldValue, field.Name)
	}

	return r, nil
}

DB Values (response from the handler)
 [
      {
            "id": 1,
            "key": "test_1",
            "value": {
                "val": "27"
            },
            "type": "int",
            // ...
            "created_at": "2024-04-04T13:17:04+06:00",
            "updated_at": "2024-04-04T13:17:04+06:00"
        }
]

The document you expected this should be explained
This should be covered in details in: https://gorm.io/docs/serializer.html

Expected answer
First, I'm not getting why except ID & Key field all fields are empty when accessing from dst.Elem() in Scan fn. I expect to know how to get other fields value of the model from (this) custom serializer.
Another:
I've noticed if I do this sv.Val = val in the case []byte block the value in response gets base64 encoded. whats the reason could be?

I'm new in GO and GORM. Probably I'm doing something wrong. Please excuse it if possible. I've tried but failed to accomplish the task & lastly came here for help. As the case is not covered in the docs I think this'll be helpful for others, specially newbies like me. I'll highly appreciate it if anybody shade some light on this.
Thanks

Hi, I'll appreciate any help on this matter.

The values of other fields can be found in dst. If their values are empty, it might be because the custom serializer field were scanned before the other fields. this depends on the order of the query fields.

Thank you, In my case, this is the case (other fields are zero value). How to resolve this?


feat enhance the reading of number when illegal inputted

What this PR does / why we need it?
feat enhance the reading of number when illegal inputted
Summary of your change
add a valid flag to enable fail-fast when illegal number inputted
Please indicate you've done the following:

[ ] Made sure tests are passing and test coverage is added if needed.
[ ] Made sure commit message follow the rule of Conventional Commits specification.
[ ] Considered the docs impact and opened a new docs issue or PR with docs changes if needed.

Codecov Report
Patch coverage: 77.20% and project coverage change: -1.66% :warning:

Comparison is base (afac453) 73.23% compared to head (ce63265) 71.57%.

Additional details and impacted files
@@             Coverage Diff              @@
##               main    #1839      +/-   ##
============================================
- Coverage     73.23%   71.57%   -1.66%
+ Complexity    21492    20795     -697
============================================
  Files           646      634      -12
  Lines         87376    86747     -629
  Branches      19065    18879     -186
============================================
- Hits          63987    62093    -1894
- Misses        15469    16690    +1221
- Partials       7920     7964      +44

Files Changed
Coverage Δ

...alibaba/fastjson2/reader/ObjectReaderImplList.java
77.89% <ø> (-0.12%)
:arrow_down:

...ba/fastjson2/reader/ObjectReaderImplListInt64.java
76.05% <ø> (-0.66%)
:arrow_down:

...ain/java/com/alibaba/fastjson2/JSONReaderUTF8.java
65.75% <68.65%> (-4.18%)
:arrow_down:

...in/java/com/alibaba/fastjson2/JSONReaderUTF16.java
72.40% <85.50%> (-0.25%)
:arrow_down:

... and 83 files with indirect coverage changes

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

JSONReaderUTF8#readNumber0这个方法中还有没改的
} else if (ch == ',' || ch == '\r' || ch == '\n') {


refactor(users): refactor find_by_role_id_in_merchant_scope query for custom roles

Type of Change

[ ] Bugfix
[ ] New feature
[ ] Enhancement
[X] Refactoring
[ ] Dependency updates
[ ] Documentation
[ ] CI/CD

Description

Refactor the find_by_role_id_in_merchant_scope query to make it a generic query that uses only org_id and role_id as parameters.
Additional Changes

[ ] This PR modifies the API contract
[ ] This PR modifies the database schema
[ ] This PR modifies application configuration/environment variables

Motivation and Context

Closes 6702
How did you test it?

Using dashboard . All the below should work as before
Cases to test :

Create a custom role from dashboard
Invite someone for that custom role
signin via that custom-role-user
List roles and list roles at entity level

Checklist

[X] I formatted the code cargo +nightly fmt --all
[X] I addressed lints thrown by cargo clippy
[ ] I reviewed the submitted code
[ ] I added unit tests for my changes where possible

As this supposed to be intermediate PR, shouldn't you add Profile in RoleScope?

As this supposed to be intermediate PR, shouldn't you add Profile in RoleScope?
This is the intermediate PR to replace the queries first , and in the next PR where there is Custom role read i will add profile in role-scope