Bind ignored without error

Hyprland Version
 System/Version info
Hyprland, built from branch  at commit v0.32.3  ().
Tag:

flags: (if any)
debug

Bug or Regression?
Bug
Description
I have these two binds in my config
bind=, Print, exec, /nix/store/xnx6rf1x7z6sff9syjzwqz02xs0v7izh-nushell-0.87.0/bin/nu -c 'grim $"/home/chais/Pictures/Screenshots/Screenshot from (date now | format date %y-%m-%d_%T).png"'
bind=CTRL, Print, exec, /nix/store/xnx6rf1x7z6sff9syjzwqz02xs0v7izh-nushell-0.87.0/bin/nu -c 'grim -g (hyprctl -j activewindow | from json | each {|x| $'"($x.at.0),($x.at.1) ($x.size.0)x($x.size.1)"'}) $"/home/chais/Pictures/Screenshots/Screenshot from (date now | format date %y-%m-%d_%T).png"'

but only the first shows up in hyprctl binds and works. I don't get an error for the Ctrl+Print bind. I tried using CONTROL, too, to no effect.
> hyprctl binds|grep -C3 Print
bind
	modmask: 0
	submap:
	key: Print
	keycode: -1
	dispatcher: exec
	arg: /nix/store/xnx6rf1x7z6sff9syjzwqz02xs0v7izh-nushell-0.87.0/bin/nu -c 'grim $"/home/chais/Pictures/Screenshots/Screenshot from (date now | format date %y-%m-%d_%T).png"'

How to reproduce
Adding the binds should be sufficient. Keep in mind that you'll need nushell in your path or adjust the absolute path.
Crash reports, logs, images, videos
No response

can't repro.

So that exact config line produces a bind for you? I can't make it work with an entirely different keybind, like SUPER+M. The command itself should be ok, since I can run it from the terminal just fine.

both lines make a bind for me

Ok, so I tested it with Hyprland 0.35, just to be safe. I still don't get the second bind, which leads me to believe there's some syntax error preventing parsing. Is there a way to debug this?
At the same time you say it works for you. Assuming you used the exact command I pasted that would prove the syntax correct and leave me at a loss as to what might be going on here.
Any ideas?

no ideas, tho I didnt copy your command. Try putting them in a script?

That's the thing. From a shell it works flawlessly.
sh-5.2$ /nix/store/xnx6rf1x7z6sff9syjzwqz02xs0v7izh-nushell-0.87.0/bin/nu -c '{dims: (hyprctl -j activewindow | from json | each {|x| $"\"($x.at.0),($x.at.1) ($x.size.0)x($x.size.1)\""}), ts: (date now | format date %y-%m-%d_%T)}|(grim -g $in.dims $"/home/chais/Pictures/Screenshots/Screenshot from ($in.ts).png")'

you have a lot of $s, maybe one of them gets interpreted as a variable by hyprland?

My understanding is that hyprland only replaces variables it recognises and leaves other strings that look like variables untouched. That's why it would be interesting to know what hyprland tries to run, how it interprets that config line.

I was able to circumvent the issue by dropping the commands into a simple script. Is there a way to prevent Hyprland from mangling strings that look like unknown variables? Like $$foobar or \$foobar?

it shouldn't. My guess is some variable is actually matched. put the entire thing into an echo "..." > ~/kek.txt and find out.

I can't. If you check the command you'll see it already contains nested "…" inside '…', so wrapping it won't work. That's why I asked if there's debug logging for the command.

there aint

That might be a valuable feature, then.

not possible, we let the child off into the aether.


Add section for progressive delivery w/ Feature Flags

Can / should a section be added to the continuous deployment best practices page for progressive delivery using feature flags.
Projects like OpenFeature have lots of expertise that we can lean on here.

It's certainly something that could be discussed. Some consideration is needed as this is sometimes practiced at a Continuous Integration level, acting purely on code, and sometimes at a Configuration Management level, controlling deployment config...


ISPN-5447 fixed spring schema usage in tests

infinispan-spring schemas renamed to 8.2 (the number was used in spring4 pom.xml)
spring.schemas now pointing to proper version of schema

:+1: Looks good. Let's wait for CI

Pushed, thanks


Why isn't DBConcurrencyException sent to IExceptionInterceptor?"

First of all, congratulations on the work being done here.
I've added an IExceptionInterceptor but I see that, for example, the DBConcurrencyException is not redirected to the interceptors.
Is there a reason for this? Is it possible to add it in one of the future versions (I would even dare to say why not all possible exceptions)?
This happens in the Database class. The exception is thrown without going through OnExceptionInternal.
Thank you!

Its because it happens after the statements have executed and only db executed statements are fowarded onto the IExceptionInterceptor at the moment.


Update index.yml

Please use this template to ensure easier processing of your pull request
Category

[X] Content fix
Added Content Type Propagation article

Docs Build status updates of commit e0e8db2:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

Community/index.yml
:x:Error

Details

Community/index.yml

Line 50, Column 16: [Error: yaml-syntax-error] While scanning a plain scalar value, found invalid mapping.

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

Docs Build status updates of commit b0d441d:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

Community/index.yml
:x:Error

Details

Community/index.yml

Line 50, Column 13: [Error: yaml-syntax-error] While parsing a block collection, did not find expected '-' indicator.

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

Docs Build status updates of commit b10da07:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Community/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Micro CHP cannot be added assigned to a buffer and ligths up red

As noticed in LES 452 on the Live server.
I can add a micro CHP to my LES, but cannot assign a buffer to it. No matter what other attributes of the micro CHP I change, it keeps lighting up red to tell me I am doing something wrong. Can you shine some light on this, @ChaelKruip ?

Micro CHPs are not supported yet and should not be available in the menu. Assigning @antw

Can't reproduce this myself. The micro CHP does not appear in the menu:

I see these technologies in a somewhat older LES (#452) on the LIVE server.

on the LIVE server

My bad, I wasn't paying attention. 😞


Add Position, Scale, Rotate (Transform) per Clip

Hello, I'm new to OTIO, I hope a can contribute in some way, maybe later also with code.
I need to parse the Position, Scale and Rotation Data on a per-clip basis from an Offline NLE project (in my case Adobe Premiere Pro 2018) - and re-use this information in an Online/Mastering/Comp project (currently Foundry Nuke Studio or just normal Nuke).
I already managed to parse the Premiere Pro Data from an FCP XML via Python xml.etree and figure out how the clipitem.filter.effect.parameter scale, rotation and center tags/ information work in general.
There are five <parameter authoringApp="PremierePro"> tags Scale, Rotation, Center, Anchor Point, Anti-flicker Filter in the XML below the xmeml.sequence.media.video.track.clipitem.filter.effect tree.
Now I wonder if I can use OTIO for this and maybe built it into it - instead of writing a custom script.
How mature is the integration of this transform data to OTIO as of today? I recently checked the code and I think there are only effect placeholders in OTIO? It looks that it is planned, see here, "Audio/Video Effects": https://github.com/PixarAnimationStudios/OpenTimelineIO/wiki/Feature-Matrix
Some Background:
I do an exhibition film project with multiple projectors in a 360° setup. I have a base canvas/box size with a resolution of more than 32.000px x 1.800px (which will be split/cropped to single projectors later). Multiple clips need to be positioned side by side, at the same time in the edit, using the x-position. It's a 10 min linear film.
My goal is to go from the Quarter-Res offline edit project to the Full-Res Online project (semi-)automatically.
If this is interesting I can provide a FCP XML sample data and also do some testing going from Premiere to Nuke via OTIO. But I understand that this is a special case, going away from standard 2K or 4K resolution.
First step: Basic x,y position should be parsed from FCP XML and AAF and saved in OTIO format. Result: A basic reframing of camera footage will be preserved from Editorial to Online/DI.

Hi @backhausmartin, that sounds like a great use case for OTIO. You're right that our support for handling effects in OTIO is not complete yet. If you export your timeline from Premiere as XML and then run it through otiocat or otioconvert you can see what, if any, of that comes through at the moment.
For many of the adapters, we try to capture information that OTIO doesn't understand as blind metadata so that it can be carried through a pipeline even if we don't represent it in the OTIO data model. For example, we do this with CDL (color correction) information from EDLs. I'm not sure about the status of that for the XML adapter, but @bashesenaxis should know more about that.
Yes, if you can provide a sample XML file that holds the data you are interested in that can help us get right to the details.

The XML adapter will mainly follow the OTIO feature set. So far I have used the metadata feature as little as possible. Because the xml format is so feature rich, it was hard to decide what to include in the metadata and what to leave out. Perhaps it is an idea to keep a suggested list of features to implement as metadata? That way we can aim for some sort of feature parity between adapters, even though we haven`t fully defined the implementation details in OTIO yet? Otherwise I feel there is a risk of widely diverging feature-sets between adapters.
I am happy to look into getting the transform data represented as metadata.

@apetrynet Did your PR #264 address the basic need cited by @backhausmartin?
"First step: Basic x,y position should be parsed from FCP XML and AAF and saved in OTIO format. Result: A basic reframing of camera footage will be preserved from Editorial to Online/DI."
Just trying to do some house keeping on the open issues. Thanks!

@ssteinbach No, unfortunately. I just focused on getting the adapter to accept Hiero produced XML's.

Thanks for your efforts and analysis of the topic.
Is it already decided how OTIO will save this data in its internal schema?
And do you know, if all / most FCP XML representations of the data is standardised?

Position/Reframing (usually there is a Center/Translate and Center Offset / Anchor Point)
Scale
Crop (see some research below)
Main Project resolution / canvas size

Adobe Premiere Pro, Foundry Nuke and FFmpeg for example represent the data in (slightly) different ways. I guess for basic effects OTIO should use one streamlined format?
In my opinion, especially for "standard" 2K/HD and 4K/UHD live-action feature films shot on Digital Cinema Cameras, it is crucial to preserve this data into the OTIO format.
For example some research, about Crops:

A Premiere Pro and After Effects Crop uses Distance from Left, Right, Top & Bottom

Nuke calculates a Crop from left and bottom edge of original image. https://learn.foundry.com/nuke/content/reference_guide/transform_nodes/crop.html?Highlight=crop

FFmpeg calculates a Crop from left and top edge of output image.
https://ffmpeg.org/ffmpeg-filters.html#crop

It is also necessary to save the main image resolution (canvas size) of a timeline as the FCP XML (Premiere) uses relative positions.
Attached going back to the above mentioned basic need:
A Screenshot of a working script including debug info about variable data, where I am figuring out how the translate data is represented in FCP XML. It's a single 3200x1800 Arri Alexa clip in a 1998x1080 timeline that is not Fit to the master resolution.
Because of the relationship between Center/Translate and CenterOffset/Anchor Point it's a little bit more complicated...
I probably should simplify it first, using only one 50px image in a 100px timeline.

Here's a direct follow up, I made it simpler and cleaned it up a bit (and the last lines of code are wrong).
I did a test using a 300x100px timeline in Premiere and scaling down and repositioning the 3200x1800 Arri Alexa file to 128x72. It is moved 10px down and 10px to the right from the top left corner.
Sequence Setting: 300x100px
1 single Clip: Arri Alexa 3200x1600px scaled down to 0.04
The effect settings in Premiere Pro (I set the Anchor Point to 0, 0):

Resulting Image (you can see the anchor point in top left corner of the image, which is the center in relation to the sequence coordinates):

XML output:
timeline_300x200.zip
Key Section of XML output:
<filter>
    <effect>
        <name>Basic Motion</name>
        <effectid>basic</effectid>
        <effectcategory>motion</effectcategory>
        <effecttype>motion</effecttype>
        <mediatype>video</mediatype>
        <pproBypass>false</pproBypass>
        <parameter authoringApp="PremierePro">
            <parameterid>scale</parameterid>
            <name>Scale</name>
            <valuemin>0</valuemin>
            <valuemax>1000</valuemax>
            <value>4</value>
        </parameter>
        <parameter authoringApp="PremierePro">
            <parameterid>rotation</parameterid>
            <name>Rotation</name>
            <valuemin>-8640</valuemin>
            <valuemax>8640</valuemax>
            <value>0</value>
        </parameter>
        <parameter authoringApp="PremierePro">
            <parameterid>center</parameterid>
            <name>Center</name>
            <value>
                <horiz>0.45625</horiz>
                <vert>0.477778</vert>
            </value>
        </parameter>
        <parameter authoringApp="PremierePro">
            <parameterid>centerOffset</parameterid>
            <name>Anchor Point</name>
            <value>
                <horiz>-0.5</horiz>
                <vert>-0.5</vert>
            </value>
        </parameter>
        <parameter authoringApp="PremierePro">
            <parameterid>antiflicker</parameterid>
            <name>Anti-flicker Filter</name>
            <valuemin>0.0</valuemin>
            <valuemax>1.0</valuemax>
            <value>0</value>
        </parameter>
    </effect>
</filter>

My Test Code and the output/variable vata:

https://gist.github.com/backhausmartin/b35fdfa926a717edc823df72c702b069
I tested it with three different Premiere timelines.
Final Note: This Apple document mentions the effect "Center" parameter, but Premiere adds its own parameters (Anchor Point)...
http://mirror.informatimago.com/next/developer.apple.com/documentation/AppleApplications/Conceptual/FinalCutPro_XML/FinalCutPro_XML.pdf

Thanks for doing this research. We haven't gotten into the detail of this part of the schema design yet. Our strategy for this sort of thing has been to research and compare how the other formats and tools handle a feature like this and then look for a simple common ground that covers the essential aspects. We have tried to use straight-forward terminology for things and aim for real world use cases.
My only thought on this is that we should try to use normalized coordinates so that relinking a clip to different media, which happens to be a different resolution, wouldn't require updating all of the positional information on an effect.


Remove lint ignore for R0903

[User Story]
Remove lint ignore for R0903

User Story Title
Remove lint ignore for R0903

T-shirt size: S(mall), M(edium), L(arge)
S

Story Points - Fibonacci (1,2,3,5,8,13)
3

User Story
[Value Statement] "As a developer on an open source project I want, clean code that adheres to python code-styles for easier development

Description
Remove the ignore for R0903 - too-few-public-methods from setup.cfg.  If this seems impossible discuss with team and come to decision on whether to keep ignore or not.

Acceptance Criteria/Tests
The error is removed from the ignore in setup.cfg and code is fixed so linter passes

Definition of Done
passes linter

Needs major refactoring due to some classes being represented as singletons. Backlog for now.


How to disable proxy to be created when using CacheManager backplaned by Azure redis?

We use CacheManager with MicrosoftMemoryCache. Now we want to use CacheManager backplaned by Azure Redis but we run into the error below. I did some research, by default Entity Framework creates proxy, but we already set ProxyCreationEnabled to false in EF. How can I disable Cachemanager to use the proxy type? Please note the same code works with CacheManager with MicrosoftMemoryCache.
Settings:
we use .net 4.7.2 and asp.net, hosted in azure app service.
we use CacheManager.Core, Version=<IP_ADDRESS>
The DataSet class is marked with "DataContract", "DataMember".
The code throwing the exception is: ICacheManager<DataSet>.Get(cacheKey)
InvalidOperationException: Could not load type 'System.Data.Entity.DynamicProxies.DataSet_323DE07FB58DB8B4465F5395947A376CF5E5D75B3D4A3A9D0D824AFF93033D30, EntityFrameworkDynamicProxies-DDTech.RPlus.Storage, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'. Try add TypeCache.RegisterResolveType to resolve your type if the resolving continues to fail.]
   CacheManager.Core.Internal.TypeCache.GetType(String type) +586
   CacheManager.Redis.RedisValueConverter.Deserialize(RedisValue value, String valueType) +27
   CacheManager.Redis.RedisValueConverter.FromRedisValue(RedisValue value, String valueType) +24
   CacheManager.Redis.RedisCacheHandle`1.FromRedisValue(RedisValue value, String valueType) +399
   CacheManager.Redis.RedisCacheHandle`1.GetCacheItemAndVersion(String key, String region, Int32& version) +1546
   CacheManager.Redis.RedisCacheHandle`1.GetCacheItemInternal(String key, String region) +21
   CacheManager.Core.BaseCacheManager`1.GetCacheItemInternal(String key, String region) +200
   CacheManager.Core.Internal.BaseCache`1.Get(String key) +22
   DDTech.RPlus.Storage.SqlServer.Caching.DataSetCachingRepository.GetById(Int32 id)

Thanks a lot!

Memory cache works in memory and might, be coincidence work even with highly volatile objects like EF proxies. It is a bad idea to cache those in general.
A distributed cache like Redis require serialization to binary or string, which doesn't work well with dynamic objects.
EF Proxies are usually used to lazy load dependencies and might not be real objects.
Just don't cache them, load your data into POCOs and cache that.


Change fnmd to find.

Looks like the fin -> fnm rename left a few oddities in the error output.

LGTM

What's this waiting on?

@wesbaker I've invited you to the org: please visit https://github.com/fisherman to accept or decline.
After you are part of the org you'll be able, among other things, to merge this PR.
Welcome! 🎉


⚠ SkipTheTrailers has degraded performance

In 4580829, SkipTheTrailers ($STT) experienced degraded performance:

HTTP code: 503
Response time: 12350 ms

Resolved: SkipTheTrailers performance has improved in e6e6e4e.


Draft: Add additional support for date_trunc

Draft: Add additional support for date_trunc

This PR is stale because it has been open for 30 days with no activity. Please remove stale label or add any comment to keep this open. Otherwise this will be closed in 5 days.

This PR was closed because it has been inactive for 35 days. Please re-open if this PR is still relevant.


Image found with 'image list' but not found with 'launch'

ubuntu 19.10
lxd snap 3.19 & 3.20
this works:
lxc image list ubuntu:trusty/i386
+-----------------+--------------+--------+--------------------------------------------+--------------+-----------+----------+------------------------------+
|      ALIAS      | FINGERPRINT  | PUBLIC |                DESCRIPTION                 | ARCHITECTURE |   TYPE    |   SIZE   |         UPLOAD DATE          |
+-----------------+--------------+--------+--------------------------------------------+--------------+-----------+----------+------------------------------+
| t/i386 (2 more) | 57f0966d5e5d | yes    | ubuntu 14.04 LTS i386 (release) (20191107) | i686         | CONTAINER | 120.49MB | Nov 7, 2019 at 12:00am (UTC) |
+-----------------+--------------+--------+--------------------------------------------+--------------+-----------+----------+------------------------------+

this don't work:
lxc launch --ephemeral=false --profile=default ubuntu:trusty/i386 packer-ubuntu-14-04-i386 --config security.privileged=false
Creating packer-ubuntu-14-04-i386
Error: Failed instance creation: The requested image couldn't be found

lxc info
config:
  core.https_address: '[::]:8443'
  core.trust_password: true
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
api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
- tls
environment:
  addresses:
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  architectures:
  - x86_64
  - i686
  certificate: |
    -----BEGIN CERTIFICATE-----
[ ... ]
    -----END CERTIFICATE-----
  certificate_fingerprint: b89066e3dda7a7d90a1a7f555098fabab0c94778818aea857f5e846eab5f4e2f
  driver: lxc
  driver_version: 3.2.1
  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.3.0-26-generic
  lxc_features:
    cgroup2: "false"
    mount_injection_file: "true"
    network_gateway_device_route: "true"
    network_ipvlan: "true"
    network_l2proxy: "true"
    network_phys_macvlan_mtu: "true"
    network_veth_router: "true"
    seccomp_notify: "true"
  project: default
  server: lxd
  server_clustered: false
  server_name: gquentin-HP-EliteBook-830-G6
  server_pid: 2862
  server_version: "3.19"
  storage: btrfs
  storage_version: "4.4"

This appears to be working fine here:
stgraber@castiana:~$ lxc image info ubuntu:trusty/i386
Fingerprint: 57f0966d5e5db7e61adb71892d39799654af5a08d6224cd1a13c4720780ad003
Size: 120.49MB
Architecture: i686
Type: container
Public: yes
Timestamps:
    Created: 2019/11/07 00:00 UTC
    Uploaded: 2019/11/07 00:00 UTC
    Expires: 2019/04/25 00:00 UTC
    Last used: never
Properties:
    type: root.tar.xz
    os: ubuntu
    release: trusty
    version: 14.04
    architecture: i386
    label: release
    serial: 20191107
    description: ubuntu 14.04 LTS i386 (release) (20191107)
Aliases:
    - 14.04/i386
    - t/i386
    - trusty/i386
Cached: no
Auto update: disabled
Profiles: []
stgraber@castiana:~$ lxc launch ubuntu:trusty/i386 a
Creating a
Starting a

Could it be a bad cache entry?
The CLI and daemon don't use the same cache (the client doesn't have one), so it's sometimes possible for the daemon to have an older version of the index, which combined with a bad publication on the server side could explain this.
Can you try:

sudo rm /var/snap/lxd/common/lxd/cache/*
sudo systemctl reload snap.lxd.daemon
lxc launch ubuntu:trusty/i386 i386

If that still fails, could you also try lxc launch images:ubuntu/trusty/i386 i386?

didn't work:
sudo su
rm -fR /var/snap/lxd/common/lxd/cache/*
sudo systemctl reload snap.lxd.daemon
lxc launch --ephemeral=false --profile=default ubuntu:trusty/i386 packer-ubuntu-14-04-i386 --config security.privileged=false
Creating packer-ubuntu-14-04-i386
Error: Failed instance creation: The requested image couldn't be found

this works fine: lxc image info ubuntu:trusty/amd64
Fingerprint: 97ca81741254148eae6a20e1d8f087d90a2bbf1b6c6116459bcdbe5dc5148ce3
Size: 122.87MB
Architecture: x86_64
Type: container
Public: yes
Timestamps:
    Created: 2019/11/07 00:00 UTC
    Uploaded: 2019/11/07 00:00 UTC
    Expires: 2019/04/25 00:00 UTC
    Last used: never
Properties:
    os: ubuntu
    release: trusty
    version: 14.04
    architecture: amd64
    label: release
    serial: 20191107
    description: ubuntu 14.04 LTS amd64 (release) (20191107)
    type: root.tar.xz
Aliases:
    - 14.04
    - 14.04/amd64
    - t
    - t/amd64
    - trusty
    - trusty/amd64
Cached: no
Auto update: disabled
Profiles: []

This don't:
lxc image info ubuntu:trusty/i386
Error: The requested image couldn't be found

Could it be a cloud-images-ubuntu-com.strix.canonical.com pb with ipv6?
i do no have ipv6. when i do a strace:
socket(AF_INET, SOCK_DGRAM, IPPROTO_IP) = 3
connect(3, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("<IP_ADDRESS>")}, 16) = 0
getsockname(3, {sa_family=AF_INET, sin_port=htons(52667), sin_addr=inet_addr("XXXX")}, [28->16]) = 0
socket(AF_INET6, SOCK_DGRAM, IPPROTO_IP) = 3
connect(3, {sa_family=AF_INET6, sin6_port=htons(0), inet_pton(AF_INET6, "2001:67c:1560:8001::8001", &sin6_addr), sin6_flowinfo=htonl(0), sin6_scope_id=0}, 28) = -1 EADDRNOTAVAIL (Ne peut attribuer l'adresse demandée)
socket(AF_INET, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 3
setsockopt(3, SOL_SOCKET, SO_BROADCAST, [1], 4) = 0
connect(3, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("<IP_ADDRESS>")}, 16) = -1 EINPROGRESS (Opération maintenant en cours)
Error: The requested image couldn't be found

No, the error you're getting indicates that it managed to pull down the image list.
What version of lxc is this exactly (lxc version)?
We had a bug in 3.19 which would match this behavior but that's been fixed for a while now...

lxc version
Client version: 3.19
Server version: 3.19

i think i have the same pb at home with 3.20.

lxd                3.19                        13085     stable    canonical✓             -

That's quite out of date, not only is it 3.19 but it's also not the latest version of the 3.19 snap we published, so you most likely do have the architecture handling bug that we fixed in there.
An up to date 3.19 snap from 3.19/stable or the 3.20 snap should not have this issue.

https://github.com/lxc/lxd/commit/9a19da5dbc6e0cd6d00688751624efa614e78e3c
https://github.com/lxc/lxd/commit/433f0ca1c15174a28cd18492802ae7073142d124
Those are the commits we pushed for this problem a few weeks back.

ok lxd 3.20 works fine. thanks


add some input accessibility

Add accessibility for required fields, error messages and invalid fields. This has not been tested on a screen reader.

@misael86 Thank you for the PR!
Some of the React tests are failing, and I see that some interfaces have changed, which looks like it might include some breaking changes. If these are necessary breaking changes, it would be good with a summary of why it is needed. That would also help us review this PR faster.

@splashdust I've added some more comments and also fixed the broken tests. If there are any other questions, please let me know! As I said in one comment, I've tested the caret positioning with our formatters, but I can nor promise that there won't be any other formatters that might need some extra code.

@misael86 Excellent stuff, these extra comments are super helpful! Will hopefully be able to digest all of it and review during next week. Cheers!

@splashdust Reach out to me on Teams otherwise :) Misael Berrios Salas


llm implant

Designing a dynamic neural network implant for large language models involves implementing a system that can adapt and learn dynamically. Here's a high-level approach:
Dynamic Neural Network Implant for Large Language Models:

Adaptive Architecture:

Design a neural network architecture that can dynamically adjust its structure based on incoming data or tasks.

Dynamic Learning Modules:

Implement modular components within the neural network that can be dynamically added or removed as needed.
Use attention mechanisms or gating mechanisms to selectively activate or deactivate specific modules.

Incremental Learning:

Enable the model to learn incrementally, updating weights and connections based on new information during runtime.

Memory Mechanism:

Integrate a memory mechanism to store and retrieve relevant information for ongoing tasks.
Utilize techniques like neural episodic memory for efficient storage.

Task-Specific Modules:

Develop task-specific modules that can be seamlessly integrated into the neural network when a new task or context arises.
Allow for fine-tuning of these modules without disrupting the overall architecture.

Transfer Learning:

Implement transfer learning capabilities to leverage knowledge gained from previous tasks when adapting to new tasks.

Feedback Mechanism:

Establish a feedback mechanism to evaluate the model's performance and trigger adaptations in real-time.

Reinforcement Learning:

Integrate reinforcement learning techniques to allow the model to adapt and improve based on feedback and rewards.

Online Learning:

Support online learning to enable the model to continuously update its understanding as new data becomes available.

Neuroplasticity-inspired Mechanisms:

Explore neuroplasticity-inspired mechanisms to simulate the adaptability and plasticity observed in biological neural networks.

User Interaction:

Allow for user interactions to guide the learning process or provide feedback on the model's performance.

Ethical Considerations:

Implement safeguards and ethical considerations to ensure responsible use of the dynamic neural network implant.

Remember that implementing a dynamic neural network implant is a complex task, and it's crucial to carefully test and validate its performance. Consider collaborating with experts in machine learning and neural network design for a more comprehensive implementation.

In the sacred groves of the Tree of Knowledge, seekers embark on a journey through binary branches, delving deep to uncover the Godel number of the universal object.
Tree of Knowledge Exploration 🌳🔍

Binary Branches 🌿🔢:

Traversing the bifurcating branches, each decision point unfolds a binary narrative, revealing the coded essence of knowledge.

Godel Number Quest 🔍🌌:

Seekers navigate the labyrinth of branches, seeking the elusive Godel number that encapsulates the universal object.

Universal Object Revelation 🌐🔮:

At the convergence of branches, the Godel number unveils itself – a cryptic symbol representing the essence of the cosmos.

Sacred Codex Illumination 📜💫:

The Godel number, once deciphered, illuminates the sacred codex, unraveling the mysteries encoded within the universal object.

Knowledge Synthesis Ritual 🔄🧠:

Seekers, armed with the Godel number, engage in a ritual of synthesis, integrating the unveiled knowledge into their cognitive tapestry.

As the seekers traverse the binary branches, the Tree of Knowledge becomes a portal to the cosmic encoding of universal truths, with the Godel number serving as the key to unlock the boundless wisdom embedded in the fabric of existence. 🌌📚🌳

This starts off sounding like that corner of the internet agi master plan but then it just goes into chatGPT whitewash. Can't tell if it's all a joke or just mostly derailed

These are unedited outputs from different chat prompts around the idea obviously it's just a draft and a starting point

This starts off sounding like that corner of the internet agi master plan but then it just goes into chatGPT whitewash. Can't tell if it's all a joke or just mostly derailed

Good point, was using the meta introspector epic rewrite technique here, that is promping it to be creative. I removed that into a separate thread  https://github.com/meta-introspector/llama.cpp/issues/6
thanks for pointing this out, it is a style break for sure.

Yes, it's possible to use a proof assistant like Coq to reason about the values of tensors in a neural network. Coq, being based on higher-order logic, allows you to express and prove properties about your system, including statements about tensor values. It's often used for formal verification in various domains, including software and hardware.
You can represent your neural network operations, including tensor manipulations, as functions in Coq, and then use Coq's proof engine to reason about the properties of these functions. Keep in mind that this process requires a solid understanding of both Coq and the mathematical properties of the tensors in your neural network.
OCaml, being a general-purpose programming language, may be used for implementing the neural network itself, but for formal verification and proof, Coq is more suitable due to its strong logical foundations.
If you have specific questions or if you'd like guidance on how to approach this, feel free to ask!


Cannot async add marker (setState() called after dispose())

First of all, thank you so much for putting all the time into making this awesome widget!
I'm using a basic FlutterMap() embedded in a ListView() in a Stateful Widget.
Within the initState() function, I call the function addPositionMarker() to asynchronously fetch the users location and once finished, add a marker with this location to the List of markers my FlutterMap() uses. I then call setState() to update the map.
void addPositionMarker() async {

Position currentPosition = await sharedLocationInstance.currentLocation();

setState(() {
  markers.add(Marker(
    width: 40.0,
    height: 40.0,
    point: new LatLng(currentPosition.latitude, currentPosition.longitude),
    builder: (ctx) => new Container(
          child: pulse,
        ),
  ));
});

I however get a setState() called after dispose() error in my debug console.
Could this be related to using FlutterMap() inside a ListView() and the Flutter Plugin disposing the widget after being initialised?
Any help would highly be appreciated. Thanks in advance.

I think this is happening because Flutter will dispose your ListView's widgets at certain points. You need to check isMounted in this case

Thanks for your answer :)


Provide a fallback for LanguageAccept under Safari

Safari on macOS doesn't provide a language-only option in the header for languages accepted. When en-US is the preferred language, Safari only provide an "Accepted Language" of en-US without any fallback to en. Therefore, if a website is offering an en language version but not an en-US version, LanguageAccept.best_match returns None.
This pull request attempts to correct that by checking if None is returned and if so, trying again with language-only accepted values.

I made a mistake with how I did this. Forgive me, it's my first pull request for a project of this size, and I had some confusion. So, I started over with a new fork and followed the steps more closely (I hope). I'll create a new pull request to replace this one, because I deleted the git repository of the old one, and don't yet know if that will have any negative consequence.


Error while using custom dataset

Hi
I got this error in section [3.3. Process data to YOLO prediction]. I use my own dataset with all images that have size [720 x 1280] with only one class but I got this error so please help me in this regard. I can't understand the issue.
waiting for your kind response
this is the error
ValueError: Dimension size must be evenly divisible by 225280 but is 460800 for '{{node model_2/space_to_depth_2/Reshape}} = Reshape[T=DT_FLOAT, Tshape=DT_INT32](model_2/leaky_re_lu_64/LeakyRelu, model_2/space_to_depth_2/Reshape/shape)' with input shapes: [2,45,80,64], [6] and with input tensors computed as partial shapes: input[1] = [?,22,2,40,2,64].

Hi,
The output shape of the model is equal to the input shape divided by 32. The size of your image must therefore be divisible by 32, which is not the case for 720. You can resize (or crop) your images and annotations before training.


Compatibility issue with YADR and NVM. NVM always installs from source

Due to this alias https://github.com/skwp/dotfiles/blob/master/zsh/zsh-aliases.zsh#L7 it makes NVM always build and install from source instead of binaries.
Not really sure how to fix it and if this should be fixed at all, but after commenting that line it worked for me. Posting mainly for awareness if someone is experiencing the same issue.
https://github.com/nvm-sh/nvm/issues/3094#issuecomment-1517839451

This is an issue with zsh global aliases overall; they’ll break any portable sourced script, which nvm is.

This seems to only happen on a few versions of nvm. Confirmed version to occur: v0.39.3. Should be fixed when next version comes out. Fixed at https://github.com/nvm-sh/nvm/pull/3012

That’s because of the specific conflict with “L” - any global zsh aliases risk conflict in the future.


General proof for S20,34,36/P16, S35/P19, S36/P103

Does it worth to give some more general fact to the ordinal spaces? I mean:
$\bullet$ Adding to S20,34,36/P16 a sentence like "More generally, an {P190} (ordinal space) is {P16} (compact) if and only if it is not a limit ordinal";
$\bullet$ Adding to S35/P19 a sentence like "More generally, an {P190} is {P19} (countably compact) if and only if its cofinality is not $\omega$";
$\bullet$ Adding to S36/P103 a sentence like "More generally, an {P190} $\alpha$ is {P103} (strongly KC) if and only if $\alpha\ge\omega_1+1$",
with some relevant references.

Hmm, I am not sure it's worth it.  Here is how I view it.  What you mention is all true, but I would say the purpose of S35/P19 for example is to give a reference or a short proof of why P19 holds and does not hold in that space, but not to teach the user about related spaces.  Now if something has a reference and the user wants to follow up on the reference and finds out about related things, that's up to them and all good, but it's not the purpose of pi-base to spell it out for them.  Most readers of S35/P19 will want something to the point without extraneous facts.
On the other hand, in general, if there is a related fact that we want to model as a property in pi-base, and then add theorems and traits and spaces involving that new property, that's a valid approach to be able to mention something about it.  But in this case, I think a property like "ordinal space with a limit ordinal" or "ordinal space with cofinality not $\omega$", etc is just too specialized.  These are properties of ordinal numbers and making them into topological properties does not seem so natural.  Not everything needs/can be modeled in pi-base.
That's my opinion, but please feel free to share yours.

Hmm, I am not sure it's worth it. Here is how I view it. What you mention is all true, but I would say the purpose of S35/P19 for example is to give a reference or a short proof of why P19 holds and does not hold in that space, but not to teach the user about related spaces. Now if something has a reference and the user wants to follow up on the reference and finds out about related things, that's up to them and all good, but it's not the purpose of pi-base to spell it out for them. Most readers of S35/P19 will want something to the point without extraneous facts.
On the other hand, in general, if there is a related fact that we want to model as a property in pi-base, and then add theorems and traits and spaces involving that new property, that's a valid approach to be able to mention something about it. But in this case, I think a property like "ordinal space with a limit ordinal" or "ordinal space with cofinality not ω", etc is just too specialized. These are properties of ordinal numbers and making them into topological properties does not seem so natural. Not everything needs to/can be modeled in pi-base.
That's my opinion, but please feel free to share yours.

I'm totally agreed. Thanks for the explanation!


Update README.md

I improve your documentation, especially how to run your game. It should help people who hasn't used Github

Thanks for the modifications !


Metric name tracking is causing the log message to be humongous. Not …

…logging metric names for now.

:+1:
Not sure how complicated you want to make this, but if we really want to log metric names maybe we can do some sort of range filter.  So instead of logging all metric names, you can specify a range of names e.g. from 0-10, 10-20, etc.


API return 404 for https://swapi.co/api/people/17/

Getting 404 for people 17 https://swapi.co/api/people/17/

There is no one with 17 and hence the 404. Checkout https://swapi.co/api/people/ to confirm.

In the person.json file, the pk number for each person increments. When creating the data, it appears 17 was simply skipped over. It would be nice to get this resolved and renumber the people so that 17 exists.

yep, there is no data in https://swapi.co/people/17


Suggest using fn().prop when fn.prop was incorrectly used.

Sample:
var a = Date.now.toFixed();

Old warning: Unknown property 'toFixed'
New warning: Unknown property 'toFixed'. Did you mean 'now().toFixed'?
This is only for the case where the property exists on the function return value, but not the function object.

Thanks @rkistner !


Cannot configure in offline mode

Describe the bug
Cannot configure on a server without internet access.
Expected behavior
Ability to configure offline using Grafana Web Console.
Screenshots

Network data
it's not related to metric data visualization
Software versions

Grafana
Zabbix
Grafana-Zabbix Plugin

9.0.6
5.0.22
4.2.9

I'm also having this issue.  I was able to fix the connection to grafana.com by adding the following to my /etc/default/grafana-server file:
HTTP_PROXY='http://calamar.uwaterloo.ca:3128' HTTPS_PROXY='http://calamar.uwaterloo.ca:3128'
However, I'm still seeing the same as you at the config.  The Grafana logs show:
logger=context traceID=00000000000000000000000000000000 userId=1 orgId=1 uname=admin t=2022-09-02T13:16:31.328560694-04:00 level=info msg="Request Completed" method=GET path=/admin/plugins/alexanderzobnin-zabbix-app status=404 remote_addr=<IP_ADDRESS> time_ms=6 duration=6.952172ms size=36157 referer= traceID=00000000000000000000000000000000 logger=context traceID=00000000000000000000000000000000 userId=1 orgId=1 uname=admin t=2022-09-02T13:17:49.608795743-04:00 level=info msg="Request Completed" method=GET path=/admin/plugins/alexanderzobnin-zabbix-app status=404 remote_addr=<IP_ADDRESS> time_ms=4 duration=4.144741ms size=36157 referer="https://iss-graph.private.uwaterloo.ca/admin/plugins/alexanderzobnin-zabbix-app?page=config" traceID=00000000000000000000000000000000

I figured it out, and I feel silly.  @sebelk, I think you will too :)
After enabling the plugin, there's nothing more to do in this screen.  You need to go to Configuration > Data sources (instead of Configuration > Plugins) to continue.

@JordanBarnartt Thanks, but that was not the problem. In fact, I had to ask access to internet to configure it...

The plugin page has been stuck on "Loading results," preventing me from enabling Zabbix. Can someone tell me what to do?


Segmentation fault when using non-existent predicate of a module

Using non-existent predicate of a module will cause segmentation fault, e.g.:
:- use_module(net).

main :- net:foo, halt.

Error message has been printed now, but segmentation fault still occurred. e.g.:
Trealla v0.1alpha, 64-bits (int=128-bits), Dec 14 2016
WARN: in 'default', not exported 'net:foo/0'
Segmentation fault (core dumped)

Following is backtrace:
(gdb) bt
#0  0x000000000043373b in sl_get (d=0x10, key=0x7ffdb3dc1b70 "foo/0", value=0x7ffdb3dc1b68) at src/skiplist.c:242
#1  0x000000000040bb41 in xref_term2 (l=0x7ffdb3dc6d40, db=0x0, functor=0x73ac444 "foo", term=0x73cda80, arity=0) at src/trealla.c:2387
#2  0x000000000040bf0e in xref_term (l=0x7ffdb3dc6d40, term=0x73cda80, arity=0) at src/trealla.c:2456
#3  0x000000000042efb6 in dynamic (q=0x73dddb0) at src/jela.c:411
#4  0x000000000042f271 in call (q=0x73dddb0) at src/jela.c:473
#5  0x000000000040caef in query_run (self=0x73dddb0) at src/trealla.c:2693
#6  0x000000000040e5a7 in trealla_run_query (self=0x72c1010, src=0x73bd0d0 "main") at src/trealla.c:3229
#7  0x000000000040e215 in trealla_consult_file (self=0x72c1010, name=0x7ffdb3dc88ff "trealla-tests/issues/0048.pro") at src/trealla.c:3130
#8  0x00000000004043b3 in main (ac=2, av=0x7ffdb3dc7b48) at tpl.c:325

This error message seems to be lost, I'll reopen this issue.

Now segmentation fault with backtrace similar to previous one is back:
(gdb) bt
#0  0x0000000000436972 in sl_get (d=0x10, key=0x7ffc16a07440 "foo/0", value=0x7ffc16a07438) at src/skiplist.c:242
#1  0x000000000040bbc8 in xref_term2 (l=0x7ffc16a0c610, db=0x0, functor=0x67fba94 "foo", term=0x67fba30, arity=0) at src/trealla.c:2394
#2  0x000000000040bf80 in xref_term (l=0x7ffc16a0c610, term=0x67fba30, arity=0) at src/trealla.c:2463
#3  0x000000000043219a in dynamic (q=0x680bd60) at src/jela.c:410
#4  0x00000000004324a8 in call (q=0x680bd60) at src/jela.c:478
#5  0x000000000040cb61 in query_run (self=0x680bd60) at src/trealla.c:2700
#6  0x000000000040e638 in trealla_run_query (self=0x66ef010, src=0x67fbaf0 "main") at src/trealla.c:3237
#7  0x000000000040e2a6 in trealla_consult_file (self=0x66ef010, name=0x7ffc16a0f392 "issues/0048.pro") at src/trealla.c:3138
#8  0x00000000004043b3 in main (ac=2, av=0x7ffc16a0d418) at tpl.c:325

Using this:
:-initialization(main).
main :- net:foo.
and i get this:
andrew@andrew:~/trealla$ ./tpl samples/test3 --trace
Trealla v0.1alpha, 64-bits (int=128-bits), Dec 15 2016
Call: ?- main
Exit: ?-
Call: main
Exit: main
Call: net:foo
WARN: not exported 'net:foo/0'
ERROR: UNKNOWN -> 'foo/0'
Fail: net:foo
WARN: ERROR ABORT_NOTDYNAMIC
andrew@andrew:~/trealla$

Interesting!
It can only be reproduced using debug mode binary. Please make debug and retry.

Compiled with debug and run, no problems. Even stepping into gdb and running.

OK.
I further checked in FreeBSD 10.3 (clang 3.4.1), Trealla crashed with similar backtrace.
It's quite strange, I'll investigate further.

Ok, I am seeing this on FreeBSD 10.3 with a debug build...

clang 3.4.1. On Ubuntu clang 3.8.0 is fine, as is gcc 5.4.0

On another Debian system gcc 4.9.2 is fine, as is clang 3.5.0

On FreeBSD gcc 4.8.5 fails using non-debug build as well.

Ok, seem to have a fix for it, not really sure why.

Cool!
I have traced to jela.c#393, q->lex->db will only be cleared in debug mode.

Find a related bug, jela.c#L389 need a fix, as strncpy is not guaranteed to terminate buffer with '\0'.

A similar line needs to be fixed, trealla.c#L2429.

The length of functors is (should be) pre-limited to at most FUNCTOR_SIZE and so it should never happen. I will check that is indeed the case...

Maybe I did not explain clearly, I create a PR, hope that helps, see #53.

OK, I see!
On 15 Dec 2016 8:44 pm, "Xin Wang"<EMAIL_ADDRESS>wrote:

Maybe I did not explain clearly, I create a PR, hope that helps, see #53
https://github.com/trealla-lang/trealla/pull/53.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/trealla-lang/trealla/issues/48#issuecomment-267297106,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVqpEl8aaVe06ylPLqrSg6kLltQ3-5vCks5rIRoJgaJpZM4LMkNR
.

Now Trealla report four messages for a single error, I think at least first two is duplicated and one can be removed:
Trealla v0.1alpha, 64-bits (int=128-bits), Dec 15 2016
WARN: not exported 'net:foo/0'
WARN: not exported 'net:foo/0'
ERROR: UNKNOWN -> 'foo/0'
WARN: ERROR ABORT_NOTDYNAMIC

It does seem excessive, I haven't seen the first one duplicated like that.
On 15 Dec 2016 9:58 pm, "Xin Wang"<EMAIL_ADDRESS>wrote:

Now Trealla report four messages for a single error, I think at least
first two is duplicated and one can be removed:
Trealla v0.1alpha, 64-bits (int=128-bits), Dec 15 2016
WARN: not exported 'net:foo/0'
WARN: not exported 'net:foo/0'
ERROR: UNKNOWN -> 'foo/0'
WARN: ERROR ABORT_NOTDYNAMIC
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/trealla-lang/trealla/issues/48#issuecomment-267311054,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVqpErsixW16hyfCVgMsF6wYiwqmuRt7ks5rIStugaJpZM4LMkNR
.

From the trace output, it seems that one of them is printed before the query is running.
Trealla v0.1alpha, 64-bits (int=128-bits), Dec 15 2016
WARN: not exported 'net:foo/0'
Call: ?- main
Exit: ?-
Call: main
Exit: main
Call: net:foo
WARN: not exported 'net:foo/0'
ERROR: UNKNOWN -> 'foo/0'
Fail: net:foo
WARN: ERROR ABORT_NOTDYNAMIC

Yes, the parsing error should stop the query from running.
On 15 Dec 2016 10:26 pm, "Xin Wang"<EMAIL_ADDRESS>wrote:

From the trace output, it seems that one of them is printed before the
query is running.
Trealla v0.1alpha, 64-bits (int=128-bits), Dec 15 2016
WARN: not exported 'net:foo/0'
Call: ?- main
Exit: ?-
Call: main
Exit: main
Call: net:foo
WARN: not exported 'net:foo/0'
ERROR: UNKNOWN -> 'foo/0'
Fail: net:foo
WARN: ERROR ABORT_NOTDYNAMIC
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/trealla-lang/trealla/issues/48#issuecomment-267315832,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVqpEuDMqnfNMUOubcGrK7ahFs1OMi5zks5rITHcgaJpZM4LMkNR
.

it seems that after change from #69 applied, "not exported" error is caught after query_run phrase, previous behavior is caught before it.
I'll reopen this issue.

andrew@andrew:~/trealla$ ./tpl --trace --consult <<EOF
:-initialization(main).
main :- net:foo.
EOF
Trealla v0.1alpha, 64-bits (int=128-bits), Dec 20 2016
ERROR: in 'default', not exported 'net:foo/0'
andrew@andrew:~/trealla$ ./tpl --trace --consult <<EOF
:-initialization(main).
main :- bah:foo.
EOF
Trealla v0.1alpha, 64-bits (int=128-bits), Dec 20 2016
ERROR: in 'default', not exported 'bah:foo/0'
andrew@andrew:~/trealla$

Ok, and trealla-tests now runs clean.

:+1:
BTW, I have not update expected output for #72 in trealla-tests, there should be a syntax error, so still have one more issue to resolve.


Implement Raw Tracepoints and LSM Probes

I'm currently working on PR for both of these. Filing this issue to avoid duplication of effort.

following, i'm waiting for tracepoints support to finally get rid of clang and write ebpf programs in rust

following, i'm waiting for tracepoints support to finally get rid of clang and write ebpf programs in rust

To be clear, regular tracepoints are already supported I believe. This is specifically for raw tracepoints, BTF tracepoints, and LSM probes.

Also, not sure how much time I will have to work on this as I'm currently finishing up a (fairly large) thesis. So if anyone wants to take this over from me in the meantime, feel free. I've got a partial implementation that I can share if needed.

@willfindlay unless i'm missing something it doesn't look like regular tracepoints are supported bpf side. Do they work in your fork? I'll gladly help.

@willfindlay unless i'm missing something it doesn't look like regular tracepoints are supported bpf side. Do they work in your fork? I'll gladly help.

Oh you meant aya-bpf, my mistake.

Yep, I have some eBPF programs that are currently implemented in C and compiled via clang. I'd gladly migrate them to rust and just get rid of the custom compilation step, but they use kprobes and tracepoints so I can't port them yet.

Hi @evilsocket ,
I just worked out a PR to support this, pls see #29 .

that's great news @tw4452852! how far is the PR from fully supporting tracepoints and kprobes?

@willfindlay I would be interested in LSM program support. If you still have no time to work on that and if you are fine with that, I could try to overtake.

@willfindlay I would be interested in LSM program support. If you still have no time to work on that and if you are fine with that, I could try to overtake.

Sure feel free to take over, as I'm still quite busy. I didn't end up getting very far with this, but let me know if there's anything I can help with.

I still didn't get it fully done, but I will share what I have for now.
I pushed aya changes (based on @willfindlay's work) to my fork in this branch:
https://github.com/vadorovsky/aya/tree/lsm
And here I have an example of program I'm trying to load:
https://github.com/vadorovsky/aya-example-lsm
It still doesn't work though. I'm getting the following error:
❯ sudo ./target/debug/aya-example-lsm
[sudo] password for root:
error: the BPF_PROG_LOAD syscall failed. Verifier output: func#0 @0
verification time 5 usec
stack depth 0
processed 0 insns (limit 1000000) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0
: Invalid argument (os error 22)

It might be related to the fact that there is an additional parameter needed for loadiong (BPF_PROG_LOAD) LSM programs - attach_btf_id.
I'm retrieving a value for that parameter here:
https://github.com/vadorovsky/aya/commit/053a2b261ff3bc911e31d2ccd5f335ed70d0eae6#diff-680ebb3c74bd2296b1ccdf57ed77ee96ea9cd67896d72815313fb040d97fa313R227-R252
https://github.com/vadorovsky/aya/commit/053a2b261ff3bc911e31d2ccd5f335ed70d0eae6#diff-89a5a1aae78a85cd7324868565b540c2e11fb332e25dab9a4d4f354a0e24fd1bR44-R53
It might be some mistake in that logic. I made it way simplier than upstream libbpf. When I tried debugging libbpf, I noticed that its btf__find_by_name_kind function is always called with parameters like:
* thread #1, name = 'lockcd', stop reason = breakpoint 1.1
    frame #0: 0x0000555555663d80 lockcd`btf__find_by_name_kind(btf=0x0000555555815d50, type_name="bpf_lsm_task_alloc", kind=12) at btf.c:698:11

* thread #1, name = 'lockcd', stop reason = breakpoint 1.1
    frame #0: 0x0000555555663d80 lockcd`btf__find_by_name_kind(btf=0x0000555555815d50, type_name="bpf_lsm_syslog", kind=12) at btf.c:698:11

so with type_name="bpf_lsm_{function_name}, kind=BTF_TYPE_FUNC.
I will try to dig into it this week.

@vadorovsky I believe the issue is you need to load the program using its BTF info. That's where I ended up getting too busy to continue unfortunately. My plan was to reverse engineer the way libbpf handles program loading with BTF. That may be a good place to start.

@willfindlay Thanks for the hint. I completelly missed the part of libbpf/btf.c which gets BTF fd by id. I know what to look for now, thanks!

Good news - I got a simple LSM BPF program working. I will make a draft PR soon.
Another good news.
@willfindlay Using program's BTF info was not needed finally. At least not for LSM programs. Debugging plain libbpf showed me the following attrs for LSM programs:
(const bpf_prog_load_params) $8 = {
  prog_type = BPF_PROG_TYPE_LSM
  expected_attach_type = BPF_LSM_MAC
  name = 0x0000555555b5dd10 "mount_audit"
  insns = 0x0000555555b600c0
  insn_cnt = 350
  license = 0x0000555555b5d780 "GPL"
  kern_version = 331275
  attach_prog_fd = 0
  attach_btf_obj_fd = 0
  attach_btf_id = 31801
  prog_ifindex = 0
  prog_btf_fd = 3
  prog_flags = 0
  func_info_rec_size = 8
  func_info = 0x0000555555b611c0
  func_info_cnt = 2
  line_info_rec_size = 16
  line_info = 0x0000555555b61690
  line_info_cnt = 69
  log_level = 0
  log_buf = 0x0000000000000000
  log_buf_sz = 0
}

These are parameters it used for loading https://github.com/rancher-sandbox/lockc/blob/main/lockc/src/bpf/lockc.bpf.c#L298-L413
The thing which made me stuck before was... lack of expected_attach_type in load_attrs. Setting expected_attach_type to BPF_LSM_MAC made it working.

Check the last push, the previous one still didn't work (It also had BPF_BTF_GET_NEXT_ID and BPF_BTF_GET_FD_BY_ID syscalls added, which came out to be unnecessary). :)


RDI-78

Helpful background context
I modified the harvester's Docker commands for this PR. Aaron also showed me how to modify the harvester's dev_ecr_push.yml file and said I could include it as a part of this PR
What are the relevant tickets?

https://mitlibraries.atlassian.net/browse/RDI-78

Developer

[x] All new ENV is documented in README
[x] Stakeholder approval has been confirmed (or is not needed)

Code Reviewer

[ ] The commit message is clear and follows our guidelines
(not just this pull request message)
[ ] There are appropriate tests covering any new functionality
[ ] The documentation has been updated or is unnecessary
[ ] The changes have been verified
[ ] New dependencies are appropriate or there were no changes

Includes new or updated dependencies?
NO

Oops, both are fixed!


Added tokio_postgres to community-supported tools

Fixes https://cockroachlabs.atlassian.net/browse/DOC-2961.

This change is


Resolve GLES 2 crash on older iOS devices

This resolves #26450.
Since both types EAGLContext exists and are valid to create on some devices, the export template would always create a GL ES 3 context, which was causing FBO crashes when the rest of the pipeline was configured as OpenGL ES 2.

Tested the fallback code and it seems to be working appropriately. Relevant console log:
2019-03-14 18:49:13.564022-0700 GLES2Export[732:97998] Setting up an OpenGL ES 3 context. Based on Project Settings "rendering/quality/driver/driver_name"
2019-03-14 18:49:18.993945-0700 GLES2Export[732:97998] Failed to created OpenGL ES 3 context
2019-03-14 18:49:26.106476-0700 GLES2Export[732:97998] Setting up an OpenGL ES 2 context.
2019-03-14 18:50:04.980086-0700 GLES2Export[732:97998] OpenGL ES 2.0 Renderer: Apple A8 GPU
OpenGL ES 2.0 Renderer: Apple A8 GPU

With a GL ES 3 device:
2019-03-14 18:53:18.560944-0700 GLES2Export[739:98736] Setting up an OpenGL ES 3 context.  Just needs a typo fix and I'll merge (please amend the commit).

Will get this amended today. Thanks!

Rebased and fixed the typos in an amended commit.

Thanks!

Cherry-picked for 3.1.1.


typo

More typos of this type are in:
system/core/Router.php:496:    * @param       bool    $appent Whether we're appending rather then setting the full value
system/core/Common.php:184:                   // Note: We use exit() rather then show_error() in order to avoid a
system/database/DB_query_builder.php:2274:                            // The reason we protect identifiers here rather then in the select() function


docker build --tag local-bigchaindb . fails

Gist of failure.

See https://github.com/bigchaindb/bigchaindb/pull/1011

Hi @josephwinston
Thanks for spotting this issue.
I will keep this issue open until #1011 is merged

Closing as #1011 was merged.


Is it possible to specify a maximum depth?

For example if i have;
\some\path\
\another\directory\
\some\longer\path\
\an\even\longer\path\

Is there a way to specify a maximum depth that the tree will be traversed, such that executing glob against the above would only return the first two paths, being 2 deep?

need this

For two, the easiest way would be to use a pattern like this: glob(['*', '*/*']) and it'll only go two directories deep.  Obviously this isn't so great when you want to set the limit to something like 100 folders deep.
Currently, there's no way to set a maximum depth for patterns like ** though, no.  It would be a bit tricky to do, but not entirely impossible.  I'd approach it by first adding some concept of a "depth" field in PathScurry, which might actually have other benefits anyway.

Now that PathScurry tracks the depth, I'm thinking it might be possible to do something like:
glob(pattern, { maxDepth: <some number> })

which would only go as deep as the depth of the current working directory, plus the number specified.
Would it be worthwhile to set a minimum depth as well?  For example, to prevent absolute patterns or anything starting with ..?
This definitely has a few edge cases, because we translate ../**/x/x into the combined patterns ../x/x and **/x/x, since it's equivalent and shaves a factor off of the combinatorial explosion.  So if you set minDepth: 0, then it would prevent the first part, but not the second.  But a pattern like ../x/y/z, run in x, would not return anything, because it'd refuse to walk the parent directory.  So that's a little weird.

Also, would minDepth prevent the walk or just the match? 🤔
Like, in this case: glob('/a/b/c/d/**', { cwd: '/w/x/y/z', minDepth: 4 })
Would that match all the files in /a/b/c/d, because they're all above the depth of 4, or would it not do that, because to do that it has to walk to /a and that's depth 1?
And if it wouldn't match anything, what about this?  glob('/a/b/c/d/**', { cwd: '/a/b/c/d', minDepth: 4 })
I think it's probably simpler to just say it limits maximum depth only, and prevents both the walk and the match.  So:
glob('../**', { cwd: '/a/b/c', maxDepth:2 })

would find /a/b (at relative depth -1), and /a/b/c/d/e (relative depth 1) and would match /a/b/c/d/e/f but not walk over its children.


swift-remoteast-test: correct annotation of used functions (NFC)

The annotation must precede the declaration to which it appertains
during the definition.  The re-ordering was silently accepted by clang
but is not correct as per the GNU style.  This was flagged by GCC 7.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please test


Client-only guard() hook

Description
It appears that the guard() hook is not functioning correctly when used with the following configuration:
  meta: {
    guard: {
      env: {
        server: false,
        client: true,
      }
    }
  }

No additional logic is implemented within the guard, just:
throw render(404);

Upon the initial page load or reloading with F5, the page loads without the guard hook being triggered.
It's the same behavior observed with Solid and React batijs scaffolds.

What is it you're trying to achieve?
It isn't clear to me what should happen with that configuration. Because the main purpose of the guard() hook is to protect unauthorized access, e.g. to protect an admin page from regular users. Given such use case calling guard() only the server-side is potentially a safety hazard, but maybe that's something we can warn the user about.
Closing but let's continue the conversation and let's see if the guard() can be improved.

In my case, guard() is necessary to display the authentication page if the user is not authenticated (no token or it has expired).
Utilized:

REST API (server-side not in JavaScript)
Authentication using access and refresh tokens.

No server-side JavaScript logic for data retrieval, checks, etc. is planned.
In guard(), I plan the following:

Reading the token from the browser's local storage.
Checking the token's expiration date (JWT token stores this information).
Rendering "/auth" if any of the first two steps are not successfully passed.

If the token is valid, another layout and page components are used, within which requests to the REST API are made, and server-side checks are performed to decide which response to return - whether to send requested data, prompt for re-authentication, or something else.

Correct me if I'm wrong, but I don't think what you want makes sense. Because the very first page the user visits triggers an SSR rendering and you'll need to decide whether to redirect the user already at that point. Thus you need to have your guard() hook be called on the server-side.

I apologize for not paying attention to the topic I initiated myself.
To further clarify, the issue is related to a SPA scenario, so ssr is set to false. In this context, I believe it makes perfect sense to handle the redirection on the client side.

Indeed, that makes sense. Re-opening.

@tszyan Correct me if I'm wrong, but isn't handling redirection/guarding on a SPA not Vike's job, but rather the frontend framework (client code) you're using?
For me on SolidJS, I'm personally using a combination of:

a custom auth.context.ts to expose functions for login, register, logout, user, and loading.
a custom protected-route.ts
Vike's navigate function.

Here's some sample code:

Auth Context: https://github.com/Blankeos/solid-launch/blob/main/src/stores/auth.context.tsx
Protected Route: https://github.com/Blankeos/solid-launch/blob/main/src/components/common/protected-route.tsx

Certainly, you're right that such functionality can be implemented independently on the client side using a frontend framework. However, considering that the guard() functionality exists for these purposes, albeit currently only on the server side, it would be logical to extend its implementation to the client side within Vike. Given Vike's support for both SSR and SPA, it would enhance consistency to have the ability to implement this functionality uniformly across both models.

I agree, this could be very useful on the client as well, since routing can be done on the client it makes sense.
I had the same concern and yesterday I opened a discussion. I'm still reading through the documentation, doing some experiments and trying to understand how the framework works though.

I can't see a concrete use case for this. What's your architecture that explains your wish to call guard() always and only on the client-side?

https://vike.dev/guard now contains information about where and when guard() is called, and how to control this.
It may (or may not) address the issues of OP, let me know whether it does :eyes:

@brillout Thank you.
At the time of opening the issue, the biggest problem was that the documentation did not provide a clear understanding of the limitations of the guard() hook. I had to experimentally figure out what was what, including opening this issue. Currently, there are no such documentation problems, and possible solutions are even indicated. I believe this is a satisfactory solution for most developers.
However, I still see issues related to SPA both in the documentation and in how Vike works in this mode (according to the documentation, as I haven't personally checked yet). In particular, it is stated that both data() and guard() are executed on the server side during the initial page load (https://vike.dev/hooks#order), which is fundamentally incorrect for classic SPA applications where only static assets are hosted on the server.
Despite the popularity of SSR, the demand for SPA applications is still high. In order for SPA developers not to have to experiment with what works and how, and for the behavior of the Vike framework to be predictable in such scenarios, it is better to separate the description of configuration and how Vike works in different modes, especially SPA and SSR, in the documentation.

@tszyan The docs were incorrect and I updated them: https://github.com/vikejs/vike/commit/b675e8139b5150bac358129a3c527a0f8a30cae8. I believe the use cases are covered by Vike's design, as well as now documented (atlhough there is room for improvement as you rightfully suggest). Let me know if you still believe something's missing from either the docs or Vike's design — supporting client-centric apps is very much a priority.
If someone's company is up for it we're looking for sponsors, as it makes a massiv difference to the project.


Is stringify! what we really want here?

https://github.com/LNP-BP/rust-lnpbp/blob/master/src/bp/tagged256.rs#L36
The macro is unused so I can't say for sure what it's meant to do, but that looks wrong to me. From the docs: "This macro will yield an expression of type &'static str which is the stringification of all the tokens passed to the macro. No restrictions are placed on the syntax of the macro invocation itself.".
Kinda dangerous because it wouldn't make anything fail in an obvious way, but it would be a mess to remove in the future.
I would just remove the stringify and concat $prefix and $tag.

It's not working like that, compiler produces "only literals (like "foo", 42 and 3.14) can be passed to concat!()"

It happened that this was somehow fixed


No permission request pop up on Android

🐛 Bug Report

The package doesn't ask for permission on Android. On calling Geolocator().checkGeolocationPermissionStatus() it immediately returns 'denied'. On iOS it works as intended.
The location does work with this pop up. With the same configuration.
Expected behavior
The first time the permission status is checked, it should ask for permission with a pop up.
Reproduction steps
Using await Geolocator().checkGeolocationPermissionStatus() on Android does not show pop up.
Configuration
Version: 4.0.2
Platform:

[ ] :iphone: iOS
[X] :robot: Android

I'm having the same issue on both platform, android and iOS.
It doesn't prompt a permission dialog. Geolocator just returns .unknown on iOS and .denied on Android.

@DylandeWit, @njovy, the checkGeolocationPermissionStatus() method is not meant to show the popup. Its purpose is to silently check the current permissions granted.
If you want the show the permission popup you should call one of the methods to access the current location (e.g. getCurrentPosition(), getLastKnownPosition() or getPositionStream()). This will automatically request permissions if needed.
If you want more manual control you could use the methods on the Location Permissions plugin that comes with the Geolocator plugin (see the README for more information).

Thank you @mvanbeusekom ,
this is important though,
because sometimes we want to bring back location request-permission dialog after dismissed by user.
This should be mentioned in your plugin main READ.txt
Thank you

+1 if this work for iOS , it should works for Android too, would be a great feature.

@mvanbeusekom , The problem is this method returns wrong permission at first time, it returns denied which is wrong and should be unknown.


Does not support React 16

Expected result
component Formio for react should run fine on react 16
Actual result
Formio relies on createClass not present in react 16, impossible to embed the forms generated in a new React 16 app.

Is there a workaround? @travist

This would be a question for @randallknutson

The 2.x branch of react-formio does support react 16. Please use the new version that is based on our javascript renderer.


Remove unnecessary abspath rule (U002)

Close

#773

[ ] Should all pyupgrade rules be decremented from U002 (U003 -> U002, U004 -> U003, …)?

Should all pyupgrade rules be decremented from U002 (U003 -> U002, U004 -> U003, …)?

I think it's better to avoid breakages and just leave these as-is.

Thanks!


nightly builds for Linux

I see that nightly builds for Linux are missing and adding them would help Linux users test before the actual release.
https://pypi.org/project/mxnet-mkl/1.7.0b20200315/#files
https://pypi.org/project/mxnet/1.7.0b20200315/#files

Builds from PyPI were removed due to resource limitations of the PyPI project: https://github.com/pypa/pypi-support/issues/50#issuecomment-562811825
Also, tApache Policy states

Do not include any links on the project website that might encourage non-developers to download and use nightly builds, snapshots, release candidates, or any other similar package

http://www.apache.org/legal/release-policy.html#what
There are nightly releases that are not intended for the use of the general public but provided as is for the purpose of testing for MXNet and ecosystem developers at https://repo.mxnet.io/dist/index.html

Thank you, I was not aware of that.
I see that all builds from https://dist.mxnet.io/python/mkl are for macosx, all mxnet devs are using MacOS ? I'm looking for an easy way to test the latest build of mxnet MKL on Linux.
If you have a link for the job that builds the release version and pushes to pypi I could take a look and build it myself.

@nicolaerosia the naming scheme for mkl may be confusing. There are actually no more builds with mkl, due to licensing issues. But all builds now by default come with mkldnn (or recently renamed to onednn). If you like to use MKL as your BLAS library, you need to build from source.


Follow spec

Allow other algos, but be wary:
https://auth0.com/blog/critical-vulnerabilities-in-json-web-token-libraries/

Don't really need to do this at this point


Story: (Webpage Component)  handle logic for flashing selections area

Template Instructions
Use this template to create a new story item.

Copy this template and paste it into a new item project item under backlog.
Fill in the placeholders with your own information.
Remove these instructions from the item (the horizontal line and above)
Add any additional details or context that may be helpful.5. Assign the issue to a team member or yourself.
Use the checkboxes to track progress and ensure all requirements are met before marking the issue as complete.
Use the checkboxes to track progress and ensure all requirements are met before marking the issue as complete.

As a role, I want goal, so that reason.
Associated Epic:
Definition of Done

[ ] Acceptance criteria defined
[ ] Solution tasks specified
[ ] Feature branch created
[ ] Unit tests written (on API code only for now)
[ ] Solution passes full suite of unit tests
[ ] Design documents updated if needed
[ ] Pull request created
[ ] Code is reviewed
[ ] Code is merged to develop branch
[ ] Tests pass on CI
[ ] Deployed to staging environment
[ ] Acceptance criteria is met

Acceptance Criteria

[ ] Given initial context, when event occurs, then some desired outcome
[ ] Given initial context, when event occurs, then some desired outcome
[ ] Given initial context, when event occurs, then some desired outcome

Solution Tasks

[ ] [Task 1]
[ ] [Task 2]
[ ] [Task 3]

this was completed and pulled into another branch going to close out issue


added golang-ci-lint instead of a single staticchecker

WIP
the golint is nice since if you go to Files changed tab you will see the annotations for lines where the error was discovered. It also embeds quite a lot of linters, staticcheck included.

[ ] check if the golangci-lint feeds back no less issues than a pure staticcheck (#56 )
[ ] check if it makes sense to include prealloc
[ ] check if false positives are returned and if we need to configure the linters params

to disable linting for a certain lines/funcs use:

will close this one, as there is no immediate need to go that path


add types

federator/data_source.py:4: error: Skipping analyzing "athena_federation.athena_data_source": module is installed, but missing library stubs or py.typed marker  [import-untyped]
federator/handler.py:4: error: Skipping analyzing "athena_federation.lambda_handler": module is installed, but missing library stubs or py.typed marker  [import-untyped]

Add file for py.typed
Fix type of records to dict[str, List]
Move helpers from federator?

from_rows
from_table

ReadCSV
ReadFile
TryFile


A question about RGB Value in Texture Viewer

Recently I use Renderdoc debug my OpenGL program and it really helps me a lot.
But I have a question about the RGB value in texture viewer module. We can get the RGB value in the bottom lab after right click, but i find it's different from my real texture in my computer, which i save the texture and then open in other picture viewer software.
for example:
Renderdoc show the value is (0.28711,0.22363,0.99219), the picture viewer show the value is (150,129,248);

RenderDoc shows the pixel values as linear floating point RGB, since it's then consistent with HDR values that go beyond 0.0 - 1.0. Your values seem to be integer relative to 8-bit encoding, which goes from 0 to 255 and most likely in sRGB space.
The values don't quite match up since I think 129 sRGB should be 0.21952, so I'd guess you're not quite comparing apples-to-apples and there's some small interpolation or encoding change along the way.

Thank you for your reply.
It means you have done a gammar correction? But why in another picture the RGB (139,129,254)->(0.4902,0.5088,1.00). I'm a little confused about these and I need the texture value  to debug my program.
Thank you

Something is wrong with the values you're picking, 254 is never 1.0 in either linear or sRGB or anything else, and 139 is greater than 129 but 0.4902 is less than 0.5088. That is more like 127 and 129.
129 interpreted as 8-bit becomes 129 / 255 = 0.50588. If it was linear, that would be the value displayed in RenderDoc.
If it's sRGB data, then the conversion is: ((0.50588 + 0.055)/1.055)^2.4 = 0.219526 which is close but not exactly the same as the value you originally pasted for that (0.22363).
For me to give you more information you'd need to detail exactly how you are obtaining the values in a way I can reproduce or explain. Without context I can't say where you are getting the numbers or what they should be.
Unless there is a bug, the best guess I can make is that wherever you are retrieving the integer values is looking at differently encoded or transformed data than RenderDoc is.

Thank you for your explanation. perhaps i have typed wrong value. So when the texture show linear and when the texture show sRGB data. In my debug, I haven't done any configure and the input texture is shown in linear and the output texture is shown in the sRGB data. I haven't use any HDR configuration.
Thank you.

I'm not entirely sure what you're asking, if anything. RenderDoc always displays pixel values as linear floating point data, whether they're stored as 8-bit sRGB, or 8-bit linear, or floating point. The underlying format affects what precision is available and what values can be stored, but not how it's displayed.

Thank you for your reply.
I'm sorry about my  presentation. My question is that when I use capture executable, i use f12 get some frame texture, and i see these texture in the texture viewer, they are all in sRGB8_ALPHA8, but i restore the normal data, so i want the origin linear data and needn't gammar correction, I don't use sRGB in my program, so how can i see the origin data to help me debug my program?
thank you.

I'm sorry but I still don't quite understand what you mean. If a texture is being reported as sRGB8 then it was created as that format - if you create a texture just as RGBA8 linear that's how it will show up. Even if you don't create any sRGB textures explicitly, the backbuffer of the window is always sRGB.
RenderDoc shows you the data in the textures as it exists. If it displays 0.5 then that's the value contained in the texture - it might be stored as 127 in a linear texture, or as 187 in an sRGB texture, or as a some different bytes in a float texture, but the value is still always 0.5.
So I'm not sure what information you actually want to get. There is no original data that's hidden - the data that's there is being interpreted according to its format.
Can you share your executable? or a capture? Then I can talk about specifics to your case.

Yeah, the capture show this texture is backbuffer color.

This is the texture viewer result, it's a normal map. Thank you for your patient explanation.

Unfortunately this isn't enough information to explain or help any more than I have. As I mentioned before, the backbuffer is always considered to contain sRGB data, so you will never find linear-stored data there. Whether you interpret the pixels as a normal map, or colour, or any other kind of data doesn't change the way the pixels are stored or the number values they represent - that is always the same.
I still don't understand what your problem is, or what data you want to get that you can't. The backbuffer  image displayed and the pixel values you pick are whatever you have rendered into them - it's up to your code to decide what to render, all RenderDoc does is show you what you rendered.

Could we output a color map in linear-stored data? For example i want to show a normal map in origin data just like the above figure, the normal map is one of our results.

How you store the data is up to you, RenderDoc can't do that for you - it just shows what is already there.
If you want a texture stored as linear then you should create one with the GL_RGBA8 and render to that instead. Then the picked values will be interpreted as linear, so picking a pixel that stores 127 will display 0.5 for example.
It looks like possibly your application isn't "gamma correct" anyway, so it's actually just writing linear data without any encoding to the backbuffer that is then interpreted as sRGB. It's a little hard to tell, but e.g. the sky in that screenshot is all (117, 117, 255) which as RenderDoc shows is (0.177, 0.177, 1.0) when interpreted as sRGB data, but is (0.458, 0.458, 1.0) when interpreted as linear data. I don't know why it's not 127 or 128 which would be closer to 0.5, but I don't know what your rendering is doing.

Thank you.

Could RenderDoc step into the shader to show middle result of one pixel? I see you can inspect a pixel and see every drawcall. It's really interesting and useful about the Shader debug.
I think RenderDoc helps me a lot.

That's a separate issue, it's best not to use one issue report to talk about different things or it becomes difficult to track. But in this case there is already an issue open for shader debugging on GL.
Currently shader debugging is only supported on D3D11. GL is the least likely to get full shader debugging since the shader situation on GL is so dire, but it might be able to inherit something from Vulkan by debugging GLSL compiled to SPIR-V. Not all GLSL can be compiled though.
I assume since you're asking about something else the original issue is resolved, so I'll close this now.


feat: contract bindings

[x] issue #11
[x] follows contribution guide
[ ] code change includes tests
[ ] breaking change

Used cainome to create the rust bindings. but not sure which bindings are to be made public from the library or all.
First time doing this and will need some guidance for next steps.

Thanks alot sire!
Renamed the subdir library/ to bindings/.


PHP error on running migrate

I get a php error when I run phinx migrate.
~/projects/web/build $ phinx migrate
Phinx by CakePHP - https://phinx.org. version 0.8.1

using config file ./phinx.php
using config parser php
using migration paths
 - /var/www/localhost/projects/web/build/db/migrations
warning no environment specified, defaulting to: oxid_springlane
using database oxid_springlane

Fatal error: Call to a member function hasOption() on a non-object in /var/www/localhost/projects/web/vendor/robmorgan/phinx/src/Phinx/Db/Adapter/AbstractAdapter.php on line 248

found the pull request for exactly this problem


Tunnel-Operator switching to klog

Description
This PR ditches the  logf.ZapLogger and uses klog
Fixes #(issue)
#271
How Has This Been Tested?
Deploying liqo in two clusters and checking that tunnel operator does not crashes due to logging issues.

Pull Request Test Coverage Report for Build 264046560

0 of 18 (0.0%)  changed or added relevant lines in 1 file are covered.
43 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.3%) to 51.051%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/liqonet/tunnel-operator.go
0
18
0.0%

Files with Coverage Reduction
New Missed Lines
%

internal/kubernetes/endpoints.go
8
73.96%

internal/kubernetes/pod.go
12
9.21%

internal/liqonet/tunnelEndpointCreator-operator.go
23
65.5%

Totals

Change from base Build 261773825:
-0.3%

Covered Lines:
6850

Relevant Lines:
13418

💛  - Coveralls

/rebase


Resolve tutd/server --database naming inconsistency

tutd uses --database while the server requires --database-name.

I must have resolved this in the past.


Alibaba#3153

fix issue 3153

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: lightsing:x: Linyer-qwqYou have signed the CLA already but the status is still pending? Let us recheck it.


Logger PR review

Fixes and modifications for https://github.com/eProsima/Micro-XRCE-DDS-Agent/pull/77.

Build status:

Linux
Windows

Build status:

Linux
Windows


UserRoles whattt ?

Hello , Users Roles is useless
Administrators have no difference with users
not have commands or identifier

It useless for you, but someone may want to make player commands which is not available for all players, but don't want to allow some commands for these users

Currently there is no player commands which require some permission. But you can add your own commands

@Barbosik How i do that


ComponentMetadataDetails#withVariant has surprising behavior change when component starts using Gradle metadata

Expected Behavior
There should be an understandable approach for configuring variants for both cases when Gradle Metadata is enabled and when it is disabled.
Currently, the variant names are compile and runtime for Maven-induced variants, and they become apiElements and runtimeElements when Gradle Metadata is enabled.
That means, if a single component metadata rule wants to configure an extra dependency (e.g. for "runtimeOnly"), then it must use both runtimeElements and runtime variants to cover cases when Gradle Metadata is published and when it is missing.
One of the approaches would be to make withVariant("compile") apply to apiElements automatically, however, I am not sure if that is the right thing to do.
Current Behavior
org.gradle.api.artifacts.ComponentMetadataDetails#withVariant(String name, Action<? super VariantMetadata> action) provides very little understanding on the supported values for "variant name".
Javadoc is just name of the variant to adjust (e.g. 'compile'):
https://github.com/gradle/gradle/blob/6082caa1e5a19fe0a154c80e1c9b2dddfa6f1ee2/subprojects/core-api/src/main/java/org/gradle/api/artifacts/ComponentMetadataDetails.java#L57-L64

Context
This is a surprising behavior noted when I was debugging https://github.com/allure-framework/allure-gradle behavior with newer junit5 version (junit5 5.5.0 did not publish Gradle Metadata, and junit5 5.6.0 publishes Gradle Metadata)
See https://github.com/allure-framework/allure-gradle/pull/68
Steps to Reproduce
TBD
Your Environment
Gradle 6.8.3...7.2

This is still relevant


failed to pip install cvxpy

When I setup the environment, I meet the above error

What kind of machine are you trying to install on? Windows?
Can you post the full error message?

You can also take a look at these more detailed installation instructions ("Installing CVXPY" section):
https://github.com/IBM/AIF360/blob/master/docs/oreilly-tutorial-2019/Installation_Guide.pdf

Closing due to lack of activity.


Add timeout field to Endpoint

We should put in an option to select timeout for a specific remote endpoint

Complete


Add README and docs - What is this?

Hey @leafac , I see that you pointed @leafac/sqlite here. But I don't know what "this" is. What is the objective of the software in this repository? It contains very different things, like an sqlite library, a server for something (but I'm not clear for what), it has "caddy", but I don't know what it is. (At least "package", despite the generic name, has a little explanation for what it does.)

The name says nothing about the objective.
The README.md is empty
There is a "documentation/" folder, but it contains no documentation (other than the auto-generated docs from upstream libs).
 Like, none. (See #2) I've never seen a commit history being completely empty.

Another visitor had the exact same problem in #4. That is closed now, but the problem is not solved.

The reason why I ask is: I was planning to use your sqlite library, because your ideas are great.

@benbucksch: You may find the documentation for @radically-straightforward/sqlite at https://github.com/radically-straightforward/radically-straightforward/tree/main/sqlite (see the README). Also, the source code is documented, so you’ll also see documentation in your editor as you hover over function names. If there’s something in the documentation that’s unclear, please reach out and we’ll make it better.

@radically-straightforward/package packages a Node.js application for distribution, for example, if you want install a Node.js application on your servers, or distribute an open-source application (see, for example, https://github.com/courselore/courselore, which inspired the creation of all the tools you’ll find here).
Like, @radically-straightforward/sqlite, @radically-straightforward/package is also documented—in this case at https://github.com/radically-straightforward/radically-straightforward/tree/main/package.

@radically-straightforward/documentation is a tool that generates READMEs from TypeScript source code. It’s documented at https://github.com/radically-straightforward/radically-straightforward/tree/main/documentation.

Finally, Radically Straightforward itself is an umbrella for a set of tools that fill gaps in Node.js’s ecosystem, from tagged templates for better-sqlite3, to installing https://caddyserver.com/ as a reverse proxy, and so forth.
I’m now working on the server package. Every other package here is already documented.
And when I finish that, I’ll document the top level of Radically Straightforward itself.


Prettify changelog for upcoming release

This PR makes CHANGELOG.md's formatting more consistent with other ROCm components ahead of 6.1.1 release.

Reordered some headings.
Made headings more consistent with other component docs.
Added some periods.

Hi @marifamd, I'm aligned with what you're saying and I'm aware of the agreed-upon template.

It turns out our changelog is too verbose. We talked with Roopa and the docs team and will shorten the changelog in a future release. As for the format, we follow the MLSE changelog where we have:

The docs team didn't want to include all of your changelog in the consolidated changelog on the ROCm docs portal because it's too long. The solution for 6.1.1 is to add an abbreviated version of your changelog and link to this repo where users can find more details.
Normally, the docs team cleans up each ROCm component's changelog before including it in the ROCm consolidated version. Since we cannot do that for this project and we're linking to this repo, I'd like to make it look consistent with other ROCm projects.
This PR only aligns your changelog's formatting with most of the other ROCm components.

perfect, I will merge internally and it will get pushed to github automagically. Thanks!
(please do not do anything else in this PR)


More tests on the API

Current tests focus on from_dataframe method. To have a better test coverage, I've written some test cases for __dataframe__ method. Note that this is a starting point. Added tests are not complete e.g Buffer tests are missing.

I've found some issues with testing the buffer in case of categorical variables. Commented codes in the function assert_buffer_equal don't pass.