Bug report: Publish pipeline

Benefit: If someone submits a PR, they cannot steal the PYPI_API_TOKEN. This could potentially be any current contributor.
https://github.com/qdrant/fastembed/pull/304
Adapted from:
https://github.com/pypa/gh-action-pypi-publish?tab=readme-ov-file#trusted-publishing
There are some steps that the admin of this repo need to do. Both are UI actions.
TODO:

Pypi.org Follow pypi guide https://docs.pypi.org/trusted-publishers/adding-a-publisher/

This should roughly do it
- owner "qdrant"
- repository name "fastembed"
- workflow "publish.yml"
- environment name "publish" # The name of environment in the yaml needs to match the name of the github UI and what you put on pypi

Github.com Create a environment named "publish" in github UI under environments.
Below a screenshot of project github.com/michaelfeil/infinity and added e.g. me as Required Reviewer (e.g. if someone else pushes a tag to my repo, this stalls the github CI, and I get a notification to approve the publish.yml workflow)

@joein Any thoughts on this?

@joein Sure, let me know!


Implement custom debug

Hi David!
I finally got around to continue with the workshop. Do you mind taking a look at my solution for custom debug? Thanks!

Nicely done!
Today I added the rest of the test cases for derive(CustomDebug) that get into more of the difficult cases around trait bounds. Check it out if you're interested:
https://github.com/dtolnay/proc-macro-workshop/tree/master/debug/tests

Thanks for the feedback, it looks a lot better now!

I'm pretty sure at this point that there has to be a cleaner way of doing this, @dtolnay, but I'm not sure how to mix this destructuring of structs and arrays... https://github.com/dtolnay/proc-macro-workshop/pull/13/commits/f1f2384614f846b05a1a7854321812796bbe95cd#diff-fd4e0f3362d674b97a10b240e544747cR102

You may be able to write the same thing with less indentation and nested closures, like this:
fields
    .named
    .iter()
    .filter_map(|f| {
        let segment = match &f.ty {
            Type::Path(ty) => &ty.path.segments[0],
            _ => return None,
        };
        if segment.ident != "PhantomData" {
            return None;
        }
        let argument = match &segment.arguments {
            PathArguments::AngleBracketed(bracketed) => &bracketed.args[0],
            _ => return None,
        };
        match argument {
            GenericArgument::Type(Type::Path(arg)) => Some(arg.path.segments[0].ident.clone()),
            _ => None,
        }
    })
    .collect()


Enable the party UI interface in the launcher

Minor tweak that enables the party create/join panels to appear when appropriate.

Ahhh this ended up only being cosmetic, for a brief time I was just getting same game connections whenever i hit the party button. So looks like the joinParty function needs to be reintroduced.


[$50] [Repro needed] Android - Profile - Some emojis are displayed as ellipsis in status

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v9.0.46-1
Reproducible in staging?: Y
Reproducible in production?: Y
Issue reported by: Applause Internal Team
Action Performed:

Launch app
Tap profile icon -- profile -- status
Select 🫢 🫡

Expected Result:
Some emojis must not be displayed as ellipsis samsung device.
Actual Result:
Some emojis are displayed as ellipsis in samsung device.
Workaround:
Unknown
Platforms:

[x] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/0a65bc84-f350-4523-9ef9-0963e91df2aa

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021845940732835928891
Upwork Job ID:<PHONE_NUMBER>835928891
Last Price Increase: 2024-10-21

Issue OwnerCurrent Issue Owner: @DylanDylann

@strepanier03  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

I need to test this still and it's on my todo for tomorrow.

Can't repro via Browserstack and I don't have a Samsung so asking for help in Slack for testing.

In light of this type of bug, we have lowered the price to $50.
We would be willing to increase that if the contributor selected to fix this wants to review all emoji on the various devices.
Please let us know if that is the case.

Proposal
Problem:
On some Samsung devices, specific emojis are being displayed as ellipsis (...) rather than as the intended emoji icons.
Root Cause:
This issue often occurs due to compatibility problems with certain emojis on specific Samsung device models, especially if the emoji characters are not supported natively by the device’s font. Samsung devices may also have older emoji support, which might not fully recognize newer or less common emojis, resulting in these emojis rendering as ellipsis. Additionally, the React Native Text component can sometimes have trouble rendering emojis if the font is incompatible with the emoji set.
Proposed Solution:
Font Compatibility Check:
Ensure that the font used for the Text component supports a wide range of emojis. Samsung devices, in particular, may not support all emojis if using a custom font. You could use a platform-specific font or the default system font on Android for maximum compatibility with emojis. Update your Text component as follows:
<Text
    style={[styles.emojiPickerButtonDropdownIcon, { fontFamily: Platform.OS === 'android' ? 'sans-serif' : undefined }]}
    numberOfLines={1}
>

Fallback Mechanism:
Add a fallback option where you detect whether the emoji has rendered correctly, and if not, display a generic emoji or icon as a fallback. You can do this by checking the emoji’s width and height, or by using a library such as react-native-unicode-emoji.
Use SVGs for Specific Emojis:
Consider using an SVG or PNG icon for certain emojis instead of Unicode emojis, especially for Samsung devices. This avoids issues with the device’s native emoji font. You can implement this by conditionally rendering an SVG icon if you detect a Samsung device.
Alternative Solutions Explored (Optional)
Cross-Platform Emoji Libraries:
Libraries like emoji-mart or react-native-emoji-picker allow for a consistent emoji experience across devices, as they rely on images or SVGs instead of the device's font. However, this increases the app's bundle size.
Custom Emoji Font:
You could include a custom emoji font within the app to ensure consistent emoji rendering. This solution might be overkill unless your app heavily relies on emoji display.

Proposal
Problem
On some Samsung devices, specific emojis are being displayed as ellipsis (...) rather than as the intended emoji icons.
Root Cause
This issue often occurs due to compatibility problems with certain emojis on specific Samsung device models, especially if the emoji characters are not supported natively by the device’s font. Samsung devices may also have older emoji support, which might not fully recognize newer or less common emojis, resulting in these emojis rendering as ellipsis. Additionally, the React Native Text component can sometimes have trouble rendering emojis if the font is incompatible with the emoji set.
Proposed Solution

Font Compatibility Check:

Ensure that the font used for the Text component supports a wide range of emojis. Samsung devices, in particular, may not support all emojis if using a custom font. You could use a platform-specific font or the default system font on Android for maximum compatibility with emojis. Update your Text component as follows:

<Text
    style={[styles.emojiPickerButtonDropdownIcon, { fontFamily: Platform.OS === 'android' ? 'sans-serif' : undefined }]}
    numberOfLines={1}
>

Fallback Mechanism:

Add a fallback option where you detect whether the emoji has rendered correctly, and if not, display a generic emoji or icon as a fallback. You can do this by checking the emoji’s width and height, or by using a library such as react-native-unicode-emoji.

Use SVGs for Specific Emojis:

Consider using an SVG or PNG icon for certain emojis instead of Unicode emojis, especially for Samsung devices. This avoids issues with the device’s native emoji font. You can implement this by conditionally rendering an SVG icon if you detect a Samsung device.
Alternative Solutions Explored (Optional)

Cross-Platform Emoji Libraries:

Libraries like emoji-mart or react-native-emoji-picker allow for a consistent emoji experience across devices, as they rely on images or SVGs instead of the device's font. However, this increases the app's bundle size.

Custom Emoji Font:

You could include a custom emoji font within the app to ensure consistent emoji rendering. This solution might be overkill unless your app heavily relies on emoji display.

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~01e8fca580ad3567b3

Proposal
Problem
On some Samsung devices, specific emojis are being displayed as ellipsis (...) rather than as the intended emoji icons.
Root Cause
This issue often occurs due to compatibility problems with certain emojis on specific Samsung device models, especially if the emoji characters are not supported natively by the device’s font. Samsung devices may also have older emoji support, which might not fully recognize newer or less common emojis, resulting in these emojis rendering as ellipsis. Additionally, the React Native Text component can sometimes have trouble rendering emojis if the font is incompatible with the emoji set.
Proposed Solution

Font Compatibility Check:

Ensure that the font used for the Text component supports a wide range of emojis. Samsung devices, in particular, may not support all emojis if using a custom font. You could use a platform-specific font or the default system font on Android for maximum compatibility with emojis. Update your Text component as follows:

<Text
    style={[styles.emojiPickerButtonDropdownIcon, { fontFamily: Platform.OS === 'android' ? 'sans-serif' : undefined }]}
    numberOfLines={1}
>

Fallback Mechanism:

Add a fallback option where you detect whether the emoji has rendered correctly, and if not, display a generic emoji or icon as a fallback. You can do this by checking the emoji’s width and height, or by using a library such as react-native-unicode-emoji.

Use SVGs for Specific Emojis:

Consider using an SVG or PNG icon for certain emojis instead of Unicode emojis, especially for Samsung devices. This avoids issues with the device’s native emoji font. You can implement this by conditionally rendering an SVG icon if you detect a Samsung device.
Alternative Solutions Explored (Optional)

Cross-Platform Emoji Libraries:

Libraries like emoji-mart or react-native-emoji-picker allow for a consistent emoji experience across devices, as they rely on images or SVGs instead of the device's font. However, this increases the app's bundle size.

Custom Emoji Font:

You could include a custom emoji font within the app to ensure consistent emoji rendering. This solution might be overkill unless your app heavily relies on emoji display.

@Ariqkip @layacat Could you guys provide videos to see how your solutions work? (Include video before applying change and video after applying change)

Which device you use to reproduce this issue?

Let me share

@Ariqkip Any update?

am running into errors when i try to install the app could you help me please @DylanDylann
this is the error"Could not get unknown property 'release' for SoftwareComponent container of type org.gradle.api.internal.component.DefaultSoftwareComponentContainer"

@Ariqkip Please bring it to open-source channel to get more eyes

@DylanDylann  I have been trying to join with no success

Not Overdue. Still waiting for proposals

Added this to #quality as this doesn't affect usability for the most part and is just a quality polish to be picked up when there's bandwidth or a good proposal comes through.

Not Overdue. Still waiting for proposals

Could you try to clean your gradle build and run again?

@DylanDylann  have done so but still  i get the error

@strepanier03 I suggest we should increase the price to get more concern from contributors. It seems this is a challenging issue

@strepanier03 Let's consider doubling the price to get more eyes

Issue not reproducible during KI retests. (First week)


API request timeout when enabling local auth in Access Control

Rancher Version: 1.0.0
Docker Version: 1.10.3
OS: Ubuntu 14.04.3 LTS
Steps to Reproduce: Install Ubuntu 14.04.3 LTS in VirtualBox (Version 5.0.16 r105871) (Network Bridge), then install Docker, and finally install rancher with command:
sudo docker run -d --restart=always -p 9090:8080 rancher/server
Results:
When everything is set, go to the URL (GUI) and then enable local Auth in the Access Control section and I get the error: API request timeout (30 sec)(POST /v1/localauthconfig):

This is the final part of the log of rancher's container:
2016-04-06 13:47:51,743 INFO    [main] [ConsoleStatus] [2/32] [253ms] [252ms] Loading config-defaults
2016-04-06 13:48:00,233 WARN    [main] [liquibase] modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use <sql> and re-specify all configuration if this is the case
2016-04-06 13:48:05,562 INFO    [main] [ConsoleStatus] [3/32] [14072ms] [13819ms] Loading system
2016-04-06 13:48:05,734 INFO    [main] [ConsoleStatus] [4/32] [14243ms] [171ms] Loading defaults
2016-04-06 13:48:06,434 INFO    [main] [ConsoleStatus] [5/32] [14944ms] [700ms] Loading types
2016-04-06 13:48:13,641 INFO    [main] [ConsoleStatus] [6/32] [22151ms] [7207ms] Loading system-services
2016-04-06 13:48:14,250 INFO    [main] [ConsoleStatus] [7/32] [22760ms] [608ms] Loading agent-server
2016-04-06 13:48:14,847 INFO    [main] [ConsoleStatus] [8/32] [23357ms] [597ms] Loading allocator-server
2016-04-06 13:48:17,818 INFO    [main] [ConsoleStatus] [9/32] [26328ms] [2971ms] Loading api-server
2016-04-06 13:48:21,042 INFO    [main] [ConsoleStatus] [10/32] [29552ms] [3223ms] Loading iaas-api
2016-04-06 13:48:21,310 INFO    [main] [ConsoleStatus] [11/32] [29820ms] [265ms] Loading archaius
2016-04-06 13:48:21,952 INFO    [main] [ConsoleStatus] [12/32] [30462ms] [642ms] Loading core-model
2016-04-06 13:48:22,012 INFO    [main] [ConsoleStatus] [13/32] [30522ms] [60ms] Loading core-object-defaults
2016-04-06 13:48:22,082 INFO    [main] [ConsoleStatus] [14/32] [30592ms] [70ms] Loading encryption
2016-04-06 13:48:26,217 INFO    [main] [ConsoleStatus] [15/32] [34727ms] [4135ms] Loading process
2016-04-06 13:48:26,333 INFO    [main] [ConsoleStatus] [16/32] [34843ms] [115ms] Loading redis
2016-04-06 13:48:26,493 INFO    [main] [ConsoleStatus] [17/32] [35003ms] [160ms] Starting bootstrap
2016-04-06 13:48:26,494 INFO    [main] [ConsoleStatus] [18/32] [35004ms] [1ms] Starting config-defaults
2016-04-06 13:48:26,495 INFO    [main] [ConsoleStatus] [19/32] [35005ms] [1ms] Starting system
2016-04-06 13:48:26,495 INFO    [main] [ConsoleStatus] [20/32] [35005ms] [0ms] Starting defaults
2016-04-06 13:48:26,496 INFO    [main] [ConsoleStatus] [21/32] [35006ms] [0ms] Starting types
2016-04-06 13:48:34,552 INFO    [main] [ConsoleStatus] [22/32] [43061ms] [8055ms] Starting system-services
2016-04-06 13:48:34,559 INFO    [main] [ConsoleStatus] [23/32] [43069ms] [2ms] Starting agent-server
2016-04-06 13:48:34,559 INFO    [main] [ConsoleStatus] [24/32] [43069ms] [0ms] Starting allocator-server
2016-04-06 13:48:36,498 INFO    [main] [ConsoleStatus] [25/32] [45008ms] [1938ms] Starting api-server
time="2016-04-06T13:48:38Z" level=info msg="Starting websocket proxy. Listening on [:8080], Proxying to cattle API at [localhost:8081], Monitoring parent pid [8]."
time="2016-04-06T13:48:38Z" level=info msg="Exiting proxy." error="Get http://localhost:8081/v1/schemas: dial tcp [::1]:8081: getsockopt: connection refused"
2016-04-06 13:48:38,764 INFO    [main] [ConsoleStatus] [26/32] [47274ms] [2266ms] Starting iaas-api
2016-04-06 13:48:38,764 INFO    [main] [ConsoleStatus] [27/32] [47274ms] [0ms] Starting archaius
2016-04-06 13:48:38,765 INFO    [main] [ConsoleStatus] [28/32] [47275ms] [1ms] Starting core-model
2016-04-06 13:48:38,765 INFO    [main] [ConsoleStatus] [29/32] [47275ms] [0ms] Starting core-object-defaults
2016-04-06 13:48:38,766 INFO    [main] [ConsoleStatus] [30/32] [47276ms] [0ms] Starting encryption
2016-04-06 13:48:38,784 INFO    [main] [ConsoleStatus] [31/32] [47294ms] [17ms] Starting process
2016-04-06 13:48:38,784 INFO    [main] [ConsoleStatus] [32/32] [47294ms] [0ms] Starting redis
13:48:39.057 [main] INFO  ConsoleStatus - [DONE ] [54628ms] Startup Succeeded, Listening on port 8081
time="2016-04-06T13:48:40Z" level=info msg="Starting websocket proxy. Listening on [:8080], Proxying to cattle API at [localhost:8081], Monitoring parent pid [8]."
time="2016-04-06T13:48:40Z" level=info msg="Starting Rancher Catalog service"
time="2016-04-06T13:48:40Z" level=info msg="Using catalog library=https://github.com/rancher/rancher-catalog.git"
time="2016-04-06T13:48:40Z" level=info msg="Using catalog community=https://github.com/rancher/community-catalog.git"
time="2016-04-06T13:48:40Z" level=info msg="Setting log level" logLevel=info
time="2016-04-06T13:48:40Z" level=info msg="Starting go-machine-service..." gitcommit=dc97268
time="2016-04-06T13:48:40Z" level=info msg="Updating docker-machine-drivers from cattle."
time="2016-04-06T13:48:40Z" level=info msg="Starting rancher-compose-executor" version=v0.7.3
time="2016-04-06T13:48:41Z" level=info msg="Downloading certificate from http://localhost:8081/v1/credentials/1c1/certificate"
time="2016-04-06T13:48:43Z" level=info msg="Initializing event router" workerCount=10
time="2016-04-06T13:48:43Z" level=info msg="Connection established"
time="2016-04-06T13:49:08Z" level=info msg="Started setting and driver watcher."
time="2016-04-06T13:49:08Z" level=info msg="Initializing event router" workerCount=10
time="2016-04-06T13:49:08Z" level=info msg="Connection established"

Although it says something about connection refused:
Starting websocket proxy. Listening on [:8080], Proxying to cattle API at [localhost:8081], Monitoring parent pid [8]."
time="2016-04-06T13:48:38Z" level=info msg="Exiting proxy." error="Get http://localhost:8081/v1/schemas: dial tcp [::1]:8081: getsockopt: connection refused

At the end it says that everything is ok:
"Starting websocket proxy. Listening on [:8080], Proxying to cattle API at [localhost:8081], Monitoring parent pid [8]."`

I tried to query the API from the Ubuntu OS and it's working correctly:

`curl http://<IP_ADDRESS>:8081`
`{"type":"collection","resourceType":"apiVersion","links":{"self":"http://<IP_ADDRESS>:8081/","latest":"http://<IP_ADDRESS>:8081/v1"},"createTypes":{},"actions":{},"data":[{"id":"v1","type":"apiVersion","links":{"self":"http://<IP_ADDRESS>:8081/v1"},"actions":{}}],"sortLinks":{},"pagination":null,"sort":null,"filters":{},"createDefaults":{}}

Expected: It shouldn't take too much time to query the API of rancher and return that the local auth has been enabled without any issue.

If you continually see this, please let me know. I've seen it occur here and there, but clicking on reload allows the API to respond.

I ended up giving up using VirtualBox, so feel free to close this issue or let it open. Thanks for your help.


error: failed to open 'test.wav' as WAV file

I got other bugs also in which it was failing to download models , do i did those steps manually , and placed it in node modules , but now i am facing this error
[whisper-node] Problem: whisper_init_from_file: loading model from './models/ggml-tiny.en.bin'
whisper_model_load: loading model
whisper_model_load: n_vocab       = 51864
whisper_model_load: n_audio_ctx   = 1500
whisper_model_load: n_audio_state = 384
whisper_model_load: n_audio_head  = 6
whisper_model_load: n_audio_layer = 4
whisper_model_load: n_text_ctx    = 448
whisper_model_load: n_text_state  = 384
whisper_model_load: n_text_head   = 6
whisper_model_load: n_text_layer  = 4
whisper_model_load: n_mels        = 80
whisper_model_load: f16           = 1
whisper_model_load: type          = 1
whisper_model_load: adding 1607 extra tokens
whisper_model_load: mem_required  =  390.00 MB
whisper_model_load: ggml ctx size =   73.58 MB
whisper_model_load: memory size   =   11.41 MB
whisper_model_load: model size    =   73.54 MB
error: failed to open 'test.wav' as WAV file

update: fixed mostly all bugs which are in issues , like model not downloading , and model not loading , and then failed to open 'test.wav' as WAV file bug
will raise a pr for all these changes

Could you please tell me how did you fix the failed to open 'test.wav' as WAV file bug, please.

Could you please tell me how did you fix the failed to open 'test.wav' as WAV file bug, please.

we have to convert file to wav ,but it's really annoying if we convert these manually, I created another package ,in which mostly all bugs are fixed, it will also convert file type automatically, you can check that
https://www.npmjs.com/package/nodejs-whisper


Add log files to gitignore

I find that when using npm, ignoring the npm-debug.log (or basically any other log files) is a common thing to do. You obviously do not want logs to be present in the repo.

Log files are intentionally not ignored so you won't miss them.


Application Groups table missing platform information

Bug description
The application group table lacks information about platform.
Command-line input
New-AsBuiltReport -Report Veeam.VBR -Target veeam-vbr.pharmax.local -AsBuiltConfigFilePath C:\Users\jocolon\AsBuiltReport\AsBuiltReport.json -OutputFolderPath C:\Users\jocolon\AsBuiltReport\ -Credential $cred -Format HTML -ReportConfigFilePath C:\Users\jocolon\AsBuiltReport\AsBuiltReport.Veeam.VBR_all.json -EnableHealthCheck
Steps to reproduce

Run report

Expected behaviour
That the report produces the correct information
Screenshots

Operating System
Windows 10
PowerShell Version
PS C:\Users\jocolon> $PSVersionTable
Name                           Value

PSVersion                      5.1.19041.2364
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.2364
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
PS C:\Users\jocolon>
PowerShell Modules
PS C:\Users\jocolon> Get-Module -ListAvailable @("AsBuiltReport.Core";"AsBuiltReport.Veeam.VBR";"PScribo") | Select Name, Version
Name                    Version

AsBuiltReport.Veeam.VBR 0.7.1
AsBuiltReport.Core      1.3.0
AsBuiltReport.Veeam.VBR 0.5.4
AsBuiltReport.Veeam.VBR 0.3.0
PScribo                 0.10.0
PS C:\Users\jocolon>
Additional Context
No response
Before submitting

[X] I have read and followed the bug reporting guidelines.
[X] I have read the documentation, and referred to the known issues before submitting this bug report.
[X] I have checked for previously opened & closed issues before submitting this bug report.

Partial Code:
$OutObj = @()
try {
    $SureBackupAGs = Get-VBRApplicationGroup
    foreach ($SureBackupAG in $SureBackupAGs) {
        Write-PscriboMessage "Discovered $($SureBackupAG.Name) Application Group."
        $inObj = [ordered] @{
            'Name' = $SureBackupAG.Name
            'Platform' = $SureBackupAG.Platform
            'VM List' = $SureBackupAG.VM -join ", "
        }
        $OutObj += [pscustomobject]$inobj
    }
}
catch {
    Write-PscriboMessage -IsWarning "SureBackup Configuration $($SureBackupAG.Name) Section: $($_.Exception.Message)"
}

In v12 platform is removed now vSphere and Hyper-V are supported
PS C:\Users\jocolon> $SureBackupAGs = Get-VBRApplicationGroup
PS C:\Users\jocolon> $SureBackupAGs | fl

VM          : {WIN}
Id          : 3f360704-c14c-4c89-8e23-06b2d97a0500
Name        : HV - APPGroup
Description : Created by PHARMAX\jocolon at 12/25/2021 9:53 PM.

VM          : {smallserver-01v, LINUX-VM}
Id          : 55b3240e-10e7-4dee-8575-4dc9ec2c17a1
Name        : PHARMAX-AG
Description : Created by PHARMAX\administrator at 6/30/2021 6:35 PM.

PS C:\Users\jocolon>


Twitch Integration

Link your MTGArena.Pro account with Twitch API to get your Twitch credential
Show Twitch Streamer next to name in Deck List, Deck Pages, Social Feed

Check if online/streaming and show icon in green color or softly pulsating.
Click on icon to visit Twitch channel.

Once we recognize streamers

Use their viewer count to weight decks shown in Featured Decks. Mix streamer decks higher than non-streamer.
New Deck Page with decks that are being used by streamers while they srtreamed. Maybe front page streamer console integration.

Another thing to be added here: https://www.reddit.com/r/MTGArenaPro/comments/9oz499/feature_suggestion_once_again_sorry_i_keep_doing/


Allow typedef from global scope

Hi,
I am trying to typedef a type from a global namespace into a non-global namespace by writing:
struct Foo {};

namespace foo {
    typedef ::Foo Foo; // unexpected '::', expected identifier; works in dxc/hlsl
    //typedef Foo Foo; // cyclic reference 'Foo'; allowed in dxc/hlsl
}

Unfortunately it gives me this error in slang 2024.1.5:
shader.slang(4): error 20001: unexpected '::', expected identifier
    typedef ::Foo Foo;
            ^~

Is it possible to support the global scope syntax :: for namespaces? Thanks!

This may just be a syntax problem. Can you try: typealias Foo=::Foo; ?

Using typealias Foo=::Foo; still gives me this error:
shader.slang(6): error 20001: unexpected '::', expected identifier
    typealias Foo=::Foo;
                  ^~

The PR should allow both typedef ::Foo Foo and typedef Foo Foo; now.


Document steps for patching old releases

I think we should document how to patch and old release in the CONTRIBUTING.md document.

Originally posted by @arboleya in https://github.com/FuelLabs/fuels-ts/pull/1849#pullrequestreview-1948722290

Already done in the former PR. (see diff)


Re-entering an existing scope with variable_scope produces inconsistent results

Consider the following example:
with tf.variable_scope(name_or_scope='alpha'):
    with tf.variable_scope(name_or_scope='beta'):
        with tf.variable_scope(name_or_scope=tf.get_variable_scope()):
            a_var = tf.get_variable(shape=(42,), name='my_var') # An arbitrary var
            an_op = tf.reduce_sum(tf.zeros((42,)), name='my_op') # An arbitrary op

print('a_var is named {}'.format(a_var.name))
print('an_op is named {}'.format(an_op.name))

This produces the following output:
a_var is named alpha/beta/my_var:0
an_op is named alpha/beta/beta/my_op:0

Note that re-entering the existing scope appears to correctly name the variable, but introduces a redundant prefix for ops. Is this expected behavior, or a bug?
Tested on 0.11.0rc1

@lukaszkaiser Is this expected behavior?

This is expected but not nice. Names of ops do not carry semantics (meaning that they can be freely permuted and the graph will execute exactly in the same way), while names of variables do. I agree that the above is a bit inconvenient, but not a bug. Still, we might consider improving this.

Let's close for now.


Text is not contrasted enough

In the templates, the text is not contrasted enough to pass WCAG 2.0 level AAA or even AA requirements.
You could replace the text color with #56595E to fix the issue.

using http://accessible-colors.com

Thanks for reporting this @Spone. We released some design improvements today and fixing the contrast was part of that.


Invalid Location, please try submitting your test request again.

Hi, I'm getting this error after I input the testing URL:
Invalid Location, please try submitting your test request again.

I found the Test Location is empty, do I missed something? Thanks in advance.

Hi there,
Sorry, this repo a little abandoned and work on it still not finished.
Maybe you should check docs for webpagetest here or ask your question in official forum here.
Thanks and sorry.

@bayandin thanks for your help.


🔌 Plugin: OpenShift Dev Spaces

🔖 Summary
When scaffolding a new repository with a Dev Spaces Devfile  The dev-spaces-backend-plugin would provide a scaffolder action that would provision a new Dev Spaces Workspace for that repository and provide a link as output to the Dev Space. This is normally done manually in the UI:

The dev-spaces front end plugin would just provide a overview card similar to the Lambda Plugin instead of showing a view logs link, there would be a link called ‘Go to Dev Space’
It would also be neat to have a ’Back to IDP’ button in Visual Studio Code using some sort of shortcut extension.
🌐 Project website (if applicable)
https://access.redhat.com/documentation/en-us/red_hat_openshift_dev_spaces/3.1/html/user_guide/introduction-to-devfile#
✌ Context
This plugin would integrate Backstage with OpenShifts Cloud Based IDE Dev Spaces providing engineers with a single entry point to provision a new service and Dev Space using a golden path software template.
👀 Have you spent some time to check if this plugin request has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Contributing Guidelines

Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else

Actually most repositories could be opened in Dev Spaces using the URL: https://<openshift_dev_spaces_fqdn>#<git_repository_url>.
What I imagine to this plugin was list the last opened workspaces. The developer does not need to remember what project he used yesterday or last week, it will be listed.


elements lookup Xpath strategy

What page source API is used by the Mac2 driver to generate the XML tree? For each MacOS app, is the XML generated from the existing HTML used to build the app? I am asking as I want to improve the XPath selectors used by my app (to be more specific, since certain elements lack unique attributes like title/value) but am not sure how the XML tree is currently being generated and found by Mac2 driver

https://github.com/appium/appium-mac2-driver/blob/master/WebDriverAgentMac/WebDriverAgentLib/Utilities/FBXPath.m has all the logic
https://github.com/appium/appium-mac2-driver/tree/master?tab=readme-ov-file#element-location describes to what xctest attributes different locators are mapped


Analyze Viewshed Sample

The GP service type is Asynchronous, however in the source code it's SynchronousExecute so it raises error.
https://github.com/Esri/arcgis-runtime-samples-dotnet/blob/main/src/WPF/ArcGISRuntime.WPF.Viewer/Samples/Geoprocessing/AnalyzeViewshed/AnalyzeViewshed.xaml.cs
Line: 132,133

https://github.com/Esri/arcgis-runtime-samples-dotnet/pull/1085
PR is in with a fix. This will be fixed in main this week.

Great, Thanks.


Update to SenzingAPI 3.8.0

See https://github.com/Senzing/g2-sdk-go/issues/95

Implemented via https://github.com/Senzing/init-database/issues/142
Pull requests:

https://github.com/Senzing/init-database/pull/150


LLM Models: add GPT-4o support

Fixes CODY-1536
Previously, we only supported GPT-4 Turbo and GPT-3.5. This PR adds additional support for GPT-4o, which seems to be both more powerful than GPT-4 while offering faster latency.
Test plan
I wasn't able to test this change locally so I'm going to leave this as a draft. More details in https://github.com/sourcegraph/sourcegraph/pull/62639
With a local build, it looks like this but when I send a message with gpt-4o it works but it's too slow to be GPT-4o (which responds super quickly in ChatGPT). Given that I'm sending the request to dotcom, I'm not sure what model we're using instead. I see gpt-4o in the logs
█ logEvent (telemetry disabled): CodyVSCodeExtension:chat-question:executed  {
  "details": "VSCode",
  "properties": {
    "requestID": "854ac15d-51dc-41de-b1f5-742066fd981d",
    "chatModel": "openai/gpt-4o",

Just curious: Do you rank and group models based on a specific metric, or is it just kind of like, following some rules of thumb?

We can close this due to https://github.com/sourcegraph/cody/pull/4164


Standalone version outperforms LV2 plugin big time

When doing a bit of stresstesting, sending lots of midi notes from supercollider (800bpm, why not :) ) into 3 parts in Zynaddsubfx, the standalone version gives me 0 xruns, where the LV2 plugin goes over >5000 xruns. Very high DSP load in both Carla and Jalv.
Zyn-fusion build from git. Debian Testing (well performing system).

Buffer size is the obvious source of performance differences.
The plugin uses an internal buffer size of 32 samples, while the
standalone uses either, a default value, a user specified value, or in
the case of backends like jack the jack frame size.
I would expect the same behavior can be observed in the standalone by
setting the internal buffer size to 32.


Scene setup

Create title scene

https://github.com/user-attachments/assets/07d5d16b-6a61-456f-9a8a-4c3da83cc423


Implement launching child apps, and communicating between parents and children

See also https://github.com/HeyPuter/puter/pull/238 which is required for this to work. The questions there apply here too. ~(monorepo wen)~
Details are in commit messages. But the rough idea is that launchChildApp() and parentApp() both give us an AppConnection, which provides methods for communicating between them. Communication goes via the Puter GUI, see that linked PR.

My dummy app that I've been using to test this is:
<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>Dummy App</title>
    <script src="http://localhost:8081/dist/puter.dev.js"></script>
    <script>
        document.addEventListener('DOMContentLoaded', async () => {
            console.log('%cHello from dummy app!', 'font-size:200%;color:orange');

            const parentApp = puter.ui.parentApp();
            if (parentApp) {
                document.body.innerHTML += `<p>I am the child</p>`;
                parentApp.on('message', message => {
                    console.log('%cDummy got message from parent', 'color:orange', message);
                    parentApp.postMessage('I love you too, parent!');
                    document.body.innerHTML += `<p><i>${new Date().toString()}</i> - Parent says: ${message}</p>`;
                });
            } else {
                document.body.innerHTML += `<p>I am the parent!</p>`;
                console.log('%cDummy has no parents :^(', 'color:orange');
                const childApp = await puter.ui.launchChildApp('dummy');
                childApp.on('message', message => {
                    console.log('%cDummy got message from child', 'color:orange', message);
                    document.body.innerHTML += `<p><i>${new Date().toString()}</i> - Child says: ${message}</p>`;
                });
                childApp.postMessage('I love you, child');
            }
        });
    </script>
</head>
<body>
This is a dummy app for testing!
</body>
</html>

It produces this result when launched:

Merged launchChildApp() into launchApp(). Launching an app is always treated as launching a child, and returns an AppConnection to it.


Upgrade of GPU refinement

Faster graph refinement with CPU + GPU
Fixes miscounting of triangles with GPU
Corrects parsing of refinement command line options

Thanks very much for the comments, very helpful - mostly addressed now, a couple of remaining questions:

not sure how the implement the changes to constructNetwork you recommend - sounds like an overloaded function, but I'm not sure how to best do that in python without increasing levels of confusion, or whether you meant something else?
the G_df dataframe is the main way of speeding up refinement - avoid repetitively generating the edge tuples for each parameter combination - worth allowing both approaches to be used?
the other speedup is the betweenness_sample - looks like graph-tool uses a faster approximation for calculating this than cugraph, and all the performance increase of the latter is lost unless this subsampling is used. But it is tedious to pass the variable through so many layers of functions, I agree - have put in a question above about what you think the clearest way to do this is.
I have added the extra information to the docs about GPU use, but this was under installation - I wonder if it might be useful to have a separate page on GPU use?

I think I'm done with this now, if you're happy to merge?

Yep sounds good, I will just increase the version and make a quick doc change before merging


Ignore Nextclade cache on new Nextclade version or dataset version

We've had a history of caching issues (https://github.com/nextstrain/ncov-ingest/issues/456, https://github.com/nextstrain/ncov-ingest/issues/392) come up whenever there's a new release of Nextclade or SARS-CoV-2 Nextclade dataset and we forget to manually upload the *.renew files to trigger the full re-run.
The workflow should automatically ignore the Nextclade cache if it encounters a new Nextclade version or dataset version.

Also prompted by discussion in blab/forecasting project to surface Nextclade/dataset version in the sequence counts generated by forecasts-ncov/ingest

Good idea, yes.
Shouldn't be hard to set renew files programmatically based on equality or not of the columns in the existing files with the current software and dataset version!


Multiplayer Opening Crash

I'm trying to play Northstar multiplayer, but every time I click "Launch Northstar," it loads up for a couple seconds and then crashes. It opens a little window that says, "Northstar has crashed! A crash log and dump can be found at R2Northstar/logs. I also can't find the crash logs, so idk what's happening.

Make sure you're running v1.4.2 or higher and don't use a mod that modifies the main menu UI. The crash is likely a result of an attack against Respawn servers where players in the Advocate Network get crashed out of the game. Newer versions of Northstar mitigates this attack.


Bug: Application crashes with TimeoutException

When launching the app from code in debug mode, the app crashes out in the config screen after a short period (say one minute) with the following error:

System.TimeoutException: 'The operation has timed out.'

    [Call Stack Truncated]

Steps to recreate:

start app in debug (from current Master branch)
specifiy an MQTT server (no username or password)
wait a short period

Thanks for reporting!
The communication between the service and the UI has no error handling and this causes the UI to crash when the service doesn't respond (or responds too late). There is a lot of room for improvement here.

Thanks for reporting!
The communication between the service and the UI has no error handling and this causes the UI to crash when the service doesn't respond (or responds too late). There is a lot of room for improvement here.

While this doesn't solve the issue of not having error handling, please make sure to start both projects. Or make sure you have hass-workstation-service.exe running in the background before you start the UserInterface.

While this doesn't solve the issue of not having error handling, please make sure to start both projects. Or make sure you have hass-workstation-service.exe running in the background before you start the UserInterface.


Refine web console UI/UX related to show Piped configuration feature

What this PR does / why we need it:

Expand dialog width and add syntax highlighter for yaml

Make "Show the configuration" item disabled when piped config hasn't loaded yet.

Which issue(s) this PR fixes:
Fixes partially #3712
Does this PR introduce a user-facing change?:

Refine web console UI/UX related to show Piped configuration feature

hold: https://github.com/pipe-cd/pipecd/pull/3716

#3722 merged

Nice improvement!


Add DevITJobs Job API

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is ordered alphabetically
[x] My submission has a useful description
[x] The description does not end with punctuation
[x] Each table column is padded with one space on either side
[x] I have searched the repository for any relevant issues or pull requests
[x] Any category I am creating has the minimum requirement of 3 items
[x] All changes have been squashed into a single commit

@andrew would you mind checking if it's fine? 🙂

Hi @andrew @gstark do you mind checking it? :)

@marekdano would you mind? :)

@marekdano would you mind? :)

Thanks for the contribution @MariaAbadi!
We're doing our best to solve/merge all the PRs. We merge the old ones first. For more ref check #1604

README.md

Thanks @VChernomYA, should be solved 🙂

@PawelBorkar @marekdano @VChernomYA I moved the PR to: https://github.com/public-apis/public-apis/pull/1686 because I had some troubles with the squash 😊
Closing this one.


常量命名修改

根据规范，所有常量命名应该用大写英文命名，单词与单词间用下划线分割

 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: eden-yuan:x: yuanyuan seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


All three Kiwix appxbundles now fail to install with 0x80070490 : Element not found.

Brief description of your issue
All three Kiiwx appxbundles - winget install kiwix, winget install wikivoyage, winget install wikimed - fail to install with an error like:
Install failed: error 0x80070490: Opening the package from location KiwixWebApp_<IP_ADDRESS>_AnyCPU.appxbundle failed.
0x80070490 : Element not found.

Steps to reproduce
Run winget install kiwix. It fails.
Expected behavior
As these bundles were all previously validated, and as I can download each bundle and install it manually with the Windows UWP installer, I expect these to work. Installation via winget has worked perfectly on previous occasions.
Actual behavior
They fail with the above error. It looks as if something has changed regarding winget's support of appxbundles. Please note that all these apps are WinRT HTML/JS apps. It may be relevant that recently these apps have started producing the Validation-No-Executables label during validation, and a tech has had to add a .validation file.
Environment
Windows: Windows.Desktop v10.0.19043.1200
Package: Microsoft.DesktopAppInstaller v1.12.11692.0

Steps to reproduce unclear, successfully installed all 3

Can you post the related logs from %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir?

Well I've just tried again, with same result.

Will post log.

Here's the log: WinGet-2021-08-24-10-48-25.569.log

You could also try to change the Network setting for Winget, the default one is Delivery Optimization (which i used there) to wininet (browser protocol i believe)
 "Network": {
      "description": "Network settings",
      "type": "object",
      "properties": {
        "downloader": {
          "description": "Control which download code is used for packages",
          "type": "string",
          "enum": [
            "default",
            "wininet",
            "do"
          ],
          "default": "default"
        }

I think its like this?
 "Network": {
        "downloader": wininet
        }

Hopefully a technician will look into this, not like the logs explain more 🤦♂
2021-08-24 10:48:32.116 [CORE] WinINet downloading from url: https://winget.azureedge.net/cache/manifests/k/Kiwix/KiwixJS/<IP_ADDRESS>/56ff-Kiwix.KiwixJS.yaml
2021-08-24 10:48:32.687 [CORE] Download hash: 8b159084e3ba1fdaadbce496846e68aad7c30de03e76eca7b5563b9eaa782d2c
2021-08-24 10:48:32.687 [CORE] Download completed.
2021-08-24 10:48:32.688 [CLI ] Manifest fields: Name [Kiwix JS], Version [<IP_ADDRESS>]
2021-08-24 10:48:32.692 [CLI ] Starting installer selection.
2021-08-24 10:48:32.692 [CLI ] Completed installer selection.
2021-08-24 10:48:34.291 [CLI ] Installer hash verified
2021-08-24 10:48:34.292 [CORE] Starting AddPackage operation #1: https://github.com/kiwix/kiwix-js-windows/releases/download/v1.6.0/KiwixWebApp_<IP_ADDRESS>_AnyCPU.appxbundleSkipSmartScreen: 1
2021-08-24 10:48:34.294 [CORE] Begin waiting for deployment #1
2021-08-24 10:48:34.294 [CORE] Begin blocking for deployment #1
2021-08-24 10:48:35.070 [CORE] Deployment failed #1: error 0x80070490: Opening the package from location KiwixWebApp_<IP_ADDRESS>_AnyCPU.appxbundle failed.
2021-08-24 10:48:35.071 [FAIL] E:\BA\97\s\external\pkg\src\AppInstallerCommonCore\Deployment.cpp(50)\AppInstallerCLI.exe!00007FF6747F0499: (caller: 00007FF6747F0C19) Exception(1) tid(4cfc) 80070490 Element not found.

    Msg:[Install failed: error 0x80070490: Opening the package from location KiwixWebApp_<IP_ADDRESS>_AnyCPU.appxbundle failed.]

2021-08-24 10:48:35.173 [CLI ] MSIX installer failed:<PHONE_NUMBER>
2021-08-24 10:48:35.173 [CLI ] Terminating context: 0x80070490 at E:\BA\97\s\external\pkg\src\AppInstallerCLICore\Workflows\InstallFlow.cpp:168

This might be a MSIX issue on your side?

Thanks @OfficialEsco. I don't think it's an MSIX issue because the packages install fine if I simply double-click them. There is no problem installing them with the standard (UWP) Windows installer, only with WinGet.

I did a quick search on one of the error codes last time and found a MSIX issue which is why i suggested that :)
Another thing you can do is, fork the repo, do winget install -m <path to manifest>, if still the same issue edit the InstallerType to Appx and try again, post the Log again to see if it throws a different error code

Thank you very much for your helpful suggestions, @OfficialEsco. I have discovered that it works on my Windows 11 test installation. Therefore the issue is not with the packages themselves, but with the configuration of WinGet on my PC. It looks like a botched update of WinGet. I'll try removing and reinstalling first. I did validate the manifest installation when I made the PR for each package's manifest. I'll try again if uninstalling and reinstalling my version of WinGet doesn't do the trick. Will report back.

Reinstalling AppInstaller from the GitHub repo doesn't cure the issue. Oddly, the version on the GitHub repo is older than the one I already have (from the Store), but I went ahead and installed it anyway. Same issue: winget install xxxxx results in error 0x80070490.
Manifest install (winget install -m .\winget-pkgs\manifests\k\Kiwix\KiwixJS\<IP_ADDRESS>\) now results in the same error. Strange.

For reference, running sfc /scannow found some errors and supposedly fixed them. After reboot, however, the winget error still persists.

Also for reference, installing a manifest for a desktop .exe programme works fine. The issue is with installing MSIX/appx/appxbundle. Once again, these install fine if I simply double-click the appxbundle downloaded from the same source. So the issue is definitely wiith winget. @denelon , would you have any clue what is going on or how I can fix my copy of winget? I've already tried to reinstall winget / downgrade to the GitHub version. It downgrades, but the issue isn't fixed.

@Jaifroid we will have to look into this. I don't see anything on the surface that would cause this behavior.

This is going to sound extremely dumb because every single Microsoft forum post says this, but have you tried dism /Online /Cleanup-Image /RestoreHealth from an elevated PowerShell/Command Prompt? I've had wacky issues with appx provisioning that have been fixed that way before.

Thanks for the suggestion @jedieaston -- any suggestion at all is useful atm! I've just tried that: it says the operation completed successfully, but the issue persists, unfortunately. 😶

Can you try manually downloading one of the installers and running Add-AppxPackage <path to installer>? If it also fails we can get some more logs that way.

Yes, that gives the following output (I also tried the suggested command):

Totally spitballing, but did you try @OfficialEsco's suggestion of disabling Delivery Optimization and using the wininet downloader? It looks like that error is sometimes (at least, in a Insider Preview build of Windows 10 from two years ago...) linked to something with Delivery Optimization.

@jedieaston Thanks for following up on that suggestion. So, I worked out I need to type winget settings and add a config line. My file now looks like below. I exit and re-enter the terminal, and I'm still getting the error, unfortunately. I've tried in both Terminal (PS Core) and in Windows PowerShell.
{
    "$schema": "https://aka.ms/winget-settings.schema.json",

    // For documentation on these settings, see: https://aka.ms/winget-settings
    // "source": {
    //    "autoUpdateIntervalInMinutes": 5
    // },

    "experimentalFeatures": {
       "experimentalMSStore": true
    },
    "network": {
       "downloader": "wininet"
    }
}

I would suggest doing shutdown /r because that fixed the issue for me.

You mean reboot the computer? I've done it several times since reporting this issue, but the issue persists! Thanks for the suggestion, though.

Can you please send me the output of msinfo32? Please export it as text file and send:

So, I tried this out in Windows Sandbox using the SandboxTest script. Same error there, both when testing a new manifest and the current version... I guess Windows Sandbox inherits the host's dlls and is not a true clean environment?

Windows Sandbox inherits the host's dlls and is not a true clean environment

Yeah, it's kind of fuzzy exactly what the Sandbox shares and what it doesn't. The docs are pretty lacking, IMO, but they're here: https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-sandbox/windows-sandbox-architecture. I bet that's what's happening.
If you feel like going on a adventure, running a "in-place upgrade" using the Media Creation Tool (click Download tool now, when its running follow the options for upgrading your current PC) will get you clean copies of those DLLs, and shouldn't mess with anything on your box (presuming you are on 21H1, it'll just get you fresh copies of everything). It should fix your problem, although I didn't suggest it until now because it's kind of a silly way to fix it.

Huh, i just had a client with this issue when executing the appxpackage, bing brought me to this thread 🤔
And somehow after KB5005565 automatically installed and rebooted it works..

@OfficialEsco Thanks for mentioning this!

@Jaifroid can you give this a try and see if it resolves the issue?

@denelon I've just tested again, and the issue has resolved itself since KB5005565 which installed itself yesterday afternoon on my system. I guess some missing or corrupted component was updated. It's a shame we can't identify exactly what was causing the issue, but I'm glad it's resolved. So I'm closing this issue, with thanks to everyone for their help and suggestions.

@Jaifroid, thank you for confirming. I'll see about getting this added to the Troubleshooting.md file.


Makefile clean target removes file tracked by git (package.json)

Symptom
In the git repository, package.json is being tracked.  However, when one runs
the make clean command it gets deleted.  One of these behaviours seems
unintended.  The little that I know about Node development leads me to believe
the Makefile has a bug, but I'm not certain.
How to Reproduce

Clone the git repository
Invoke make clean
See error

Expected behavior
clean target should not remove files tracked by git.
Environment

Distro: OpenSUSE Tumbleweed
KWin version: 6.0.5
Krohnkite version: bcabc63
List of KWin scripts in use: None

Notes
N/A

Fixed.

res/package.json - joined with the main one and removed.
Makefile - changed


Update 01-main.tf

Execution result of "run-all plan" in "infrastructure/cloud"
time=2024-01-09T20:47:41Z level=info msg=The stack at /github/workspace/infrastructure/cloud will be processed in the following order for command plan:
Group 1
- Module /github/workspace/infrastructure/cloud/aws/jung2bot-dev/dynamodb
- Module /github/workspace/infrastructure/cloud/aws/jung2bot-dev/sqs
- Module /github/workspace/infrastructure/cloud/aws/jung2bot/dynamodb
- Module /github/workspace/infrastructure/cloud/aws/jung2bot/sqs
- Module /github/workspace/infrastructure/cloud/b2/bucket
- Module /github/workspace/infrastructure/cloud/cloudflare/access
- Module /github/workspace/infrastructure/cloud/cloudflare/tunnel
- Module /github/workspace/infrastructure/cloud/uptime-robot/otaru

Group 2
- Module /github/workspace/infrastructure/cloud/cloudflare/dns

Initializing the backend...

Initializing the backend...

Initializing the backend...

Initializing the backend...

Initializing the backend...

Initializing the backend...

Initializing the backend...

Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- Reusing previous version of integrations/github from the dependency lock file
Initializing modules...
Initializing modules...
- Finding vexxhost/uptimerobot versions matching "~> 0.8"...
Initializing modules...

Initializing provider plugins...
- Reusing previous version of integrations/github from the dependency lock file
Downloading registry.terraform.io/terraform-aws-modules/dynamodb-table/aws 4.0.0 for dynamodb_table...
Initializing modules...
Downloading registry.terraform.io/terraform-aws-modules/sqs/aws 4.1.0 for sqs...
Downloading registry.terraform.io/terraform-aws-modules/sqs/aws 4.1.0 for sqs...
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of vexxhost/uptimerobot from the dependency lock file
Downloading registry.terraform.io/terraform-aws-modules/dynamodb-table/aws 4.0.0 for dynamodb_table...
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of backblaze/b2 from the dependency lock file
- Reusing previous version of backblaze/b2 from the dependency lock file
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- sqs in .terraform/modules/sqs

Initializing provider plugins...
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- dynamodb_table in .terraform/modules/dynamodb_table
- Reusing previous version of integrations/github from the dependency lock file

Initializing provider plugins...
- Reusing previous version of integrations/github from the dependency lock file
- sqs in .terraform/modules/sqs

Initializing provider plugins...
- Reusing previous version of integrations/github from the dependency lock file

Initializing provider plugins...
- Reusing previous version of vexxhost/uptimerobot from the dependency lock file
- Reusing previous version of vexxhost/uptimerobot from the dependency lock file
- Reusing previous version of vexxhost/uptimerobot from the dependency lock file
- Reusing previous version of hashicorp/aws from the dependency lock file

Initializing provider plugins...
- Finding vexxhost/uptimerobot versions matching "~> 0.8"...
- dynamodb_table in .terraform/modules/dynamodb_table

Initializing provider plugins...
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- Reusing previous version of backblaze/b2 from the dependency lock file
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of integrations/github from the dependency lock file
- Reusing previous version of vexxhost/uptimerobot from the dependency lock file
- Reusing previous version of backblaze/b2 from the dependency lock file
- Reusing previous version of backblaze/b2 from the dependency lock file
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of vexxhost/uptimerobot from the dependency lock file
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of backblaze/b2 from the dependency lock file
- Reusing previous version of backblaze/b2 from the dependency lock file
- Installing vexxhost/uptimerobot v0.8.2...
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- Installing integrations/github v5.40.0...
- Reusing previous version of integrations/github from the dependency lock file
- Reusing previous version of backblaze/b2 from the dependency lock file
- Reusing previous version of integrations/github from the dependency lock file
- Installing cloudflare/cloudflare v4.21.0...
- Installing cloudflare/cloudflare v4.21.0...
- Installing cloudflare/cloudflare v4.16.0...
- Installing vexxhost/uptimerobot v0.8.2...
- Installed vexxhost/uptimerobot v0.8.2 (self-signed, key ID 8FF00CD0B5FEAF59)
- Installing integrations/github v5.42.0...
- Installing hashicorp/aws v5.21.0...
- Installing backblaze/b2 v0.8.7...
- Installed integrations/github v5.40.0 (signed by a HashiCorp partner, key ID 38027F80D7FD5FB2)
- Installed vexxhost/uptimerobot v0.8.2 (self-signed, key ID 8FF00CD0B5FEAF59)
- Installing vexxhost/uptimerobot v0.8.2...
- Installing hashicorp/aws v5.21.0...
- Installed cloudflare/cloudflare v4.21.0 (self-signed, key ID C76001609EE3B136)
- Installed cloudflare/cloudflare v4.21.0 (self-signed, key ID C76001609EE3B136)
- Installing integrations/github v5.42.0...
- Installed cloudflare/cloudflare v4.16.0 (self-signed, key ID C76001609EE3B136)
- Installing integrations/github v5.42.0...
- Installed integrations/github v5.42.0 (signed by a HashiCorp partner, key ID 38027F80D7FD5FB2)
- Installing integrations/github v5.40.0...
- Installing vexxhost/uptimerobot v0.8.2...
- Installed vexxhost/uptimerobot v0.8.2 (self-signed, key ID 8FF00CD0B5FEAF59)
- Installing hashicorp/aws v5.22.0...
- Installed vexxhost/uptimerobot v0.8.2 (self-signed, key ID 8FF00CD0B5FEAF59)
- Installed integrations/github v5.42.0 (signed by a HashiCorp partner, key ID 38027F80D7FD5FB2)
- Installing hashicorp/aws v5.31.0...
- Installing vexxhost/uptimerobot v0.8.2...
- Installed integrations/github v5.42.0 (signed by a HashiCorp partner, key ID 38027F80D7FD5FB2)
- Installing vexxhost/uptimerobot v0.8.2...
- Installed backblaze/b2 v0.8.7 (signed by a HashiCorp partner, key ID 83D9CAF4848490D6)
- Installed integrations/github v5.40.0 (signed by a HashiCorp partner, key ID 38027F80D7FD5FB2)
- Installing cloudflare/cloudflare v4.21.0...
- Installing vexxhost/uptimerobot v0.8.2...
- Installed vexxhost/uptimerobot v0.8.2 (self-signed, key ID 8FF00CD0B5FEAF59)
- Installing hashicorp/aws v5.31.0...
- Installed vexxhost/uptimerobot v0.8.2 (self-signed, key ID 8FF00CD0B5FEAF59)
- Installed vexxhost/uptimerobot v0.8.2 (self-signed, key ID 8FF00CD0B5FEAF59)
- Installing hashicorp/aws v5.21.0...
- Installing hashicorp/aws v5.31.0...
- Installed cloudflare/cloudflare v4.21.0 (self-signed, key ID C76001609EE3B136)
- Installing integrations/github v5.42.0...
- Installed integrations/github v5.42.0 (signed by a HashiCorp partner, key ID 38027F80D7FD5FB2)
- Installing vexxhost/uptimerobot v0.8.2...
- Installed vexxhost/uptimerobot v0.8.2 (self-signed, key ID 8FF00CD0B5FEAF59)
- Installing hashicorp/aws v5.31.0...
- Installed hashicorp/aws v5.21.0 (signed by HashiCorp)
- Installing backblaze/b2 v0.8.4...
- Installed hashicorp/aws v5.21.0 (signed by HashiCorp)
- Installed hashicorp/aws v5.22.0 (signed by HashiCorp)
- Installing backblaze/b2 v0.8.4...
- Installing backblaze/b2 v0.8.4...
- Installed hashicorp/aws v5.21.0 (signed by HashiCorp)
- Installed hashicorp/aws v5.31.0 (signed by HashiCorp)
- Installing backblaze/b2 v0.8.4...
- Installed backblaze/b2 v0.8.4 (signed by a HashiCorp partner, key ID 83D9CAF4848490D6)
- Installing backblaze/b2 v0.8.7...
- Installed backblaze/b2 v0.8.4 (signed by a HashiCorp partner, key ID 83D9CAF4848490D6)
- Installing cloudflare/cloudflare v4.16.0...
- Installed hashicorp/aws v5.31.0 (signed by HashiCorp)
- Installing cloudflare/cloudflare v4.16.0...
- Installed backblaze/b2 v0.8.4 (signed by a HashiCorp partner, key ID 83D9CAF4848490D6)
- Installed hashicorp/aws v5.31.0 (signed by HashiCorp)
- Installing backblaze/b2 v0.8.7...
- Installing backblaze/b2 v0.8.7...
- Installing cloudflare/cloudflare v4.17.0...
- Installed cloudflare/cloudflare v4.16.0 (self-signed, key ID C76001609EE3B136)
- Installing integrations/github v5.40.0...
- Installed cloudflare/cloudflare v4.16.0 (self-signed, key ID C76001609EE3B136)
- Installing integrations/github v5.40.0...
- Installed cloudflare/cloudflare v4.17.0 (self-signed, key ID C76001609EE3B136)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html

Terraform has made some changes to the provider dependency selections recorded
in the .terraform.lock.hcl file. Review those changes and commit them to your
version control system if they represent changes you intended to make.

Terraform has been successfully initialized!
- Installed backblaze/b2 v0.8.7 (signed by a HashiCorp partner, key ID 83D9CAF4848490D6)
- Installed backblaze/b2 v0.8.4 (signed by a HashiCorp partner, key ID 83D9CAF4848490D6)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html

Terraform has made some changes to the provider dependency selections recorded
in the .terraform.lock.hcl file. Review those changes and commit them to your
version control system if they represent changes you intended to make.

Terraform has been successfully initialized!
- Installed integrations/github v5.40.0 (signed by a HashiCorp partner, key ID 38027F80D7FD5FB2)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html

Terraform has made some changes to the provider dependency selections recorded
in the .terraform.lock.hcl file. Review those changes and commit them to your
version control system if they represent changes you intended to make.

Terraform has been successfully initialized!
- Installing cloudflare/cloudflare v4.21.0...
- Installed backblaze/b2 v0.8.7 (signed by a HashiCorp partner, key ID 83D9CAF4848490D6)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html

Terraform has made some changes to the provider dependency selections recorded
in the .terraform.lock.hcl file. Review those changes and commit them to your
version control system if they represent changes you intended to make.
- Installed integrations/github v5.40.0 (signed by a HashiCorp partner, key ID 38027F80D7FD5FB2)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html

Terraform has made some changes to the provider dependency selections recorded
in the .terraform.lock.hcl file. Review those changes and commit them to your
version control system if they represent changes you intended to make.

Terraform has been successfully initialized!

Terraform has been successfully initialized!
- Installed backblaze/b2 v0.8.7 (signed by a HashiCorp partner, key ID 83D9CAF4848490D6)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html

Terraform has made some changes to the provider dependency selections recorded
in the .terraform.lock.hcl file. Review those changes and commit them to your
version control system if they represent changes you intended to make.

Terraform has been successfully initialized!
- Installed cloudflare/cloudflare v4.21.0 (self-signed, key ID C76001609EE3B136)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html

Terraform has made some changes to the provider dependency selections recorded
in the .terraform.lock.hcl file. Review those changes and commit them to your
version control system if they represent changes you intended to make.

Terraform has been successfully initialized!
- Installed hashicorp/aws v5.31.0 (signed by HashiCorp)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html

Terraform has made some changes to the provider dependency selections recorded
in the .terraform.lock.hcl file. Review those changes and commit them to your
version control system if they represent changes you intended to make.

Terraform has been successfully initialized!
data.uptimerobot_account.this: Reading...
data.uptimerobot_account.this: Read complete after 1s [id=2024-01-09 20:48:17.581634018 +0000 UTC]
data.uptimerobot_alert_contact.this: Reading...
data.uptimerobot_alert_contact.this: Read complete after 0s [id=01487022]
uptimerobot_monitor.this: Refreshing state... [id=795551117]
cloudflare_tunnel.this: Refreshing state... [id=de250703-6c08-400d-b568-bc0aa34cabaf]
cloudflare_access_application.this: Refreshing state... [id=bcaa03ae-0a94-42ad-935c-487ca0a80723]
data.github_ip_ranges.this: Reading...
data.github_ip_ranges.this: Read complete after 0s [id=github-ip-ranges]
cloudflare_access_policy.telegram: Refreshing state... [id=3a7f9d55-4ddb-40bf-9671-793283e54b52]
cloudflare_access_policy.uptime_robot: Refreshing state... [id=fd540ff0-edd5-4f64-b683-a8dd575af941]
cloudflare_access_policy.github: Refreshing state... [id=2a1fc41f-8d41-4f1f-8e72-91b0970ab129]
cloudflare_access_policy.this: Refreshing state... [id=1b62d9cb-f555-4d23-b815-dfe3f92bd2a1]

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.
b2_bucket.this: Refreshing state... [id=62c5440382b735a482bf081b]
data.github_ip_ranges.this: Reading...
data.github_ip_ranges.this: Read complete after 0s [id=github-ip-ranges]
module.sqs["event"].aws_sqs_queue.this[0]: Refreshing state... [id=https://sqs.eu-west-1.amazonaws.com/477397881710/jung2bot-dev-event-queue]
data.aws_caller_identity.current: Reading...
data.aws_caller_identity.current: Read complete after 0s [id=477397881710]

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.
aws_sqs_queue_policy.this["event"]: Refreshing state... [id=https://sqs.eu-west-1.amazonaws.com/477397881710/jung2bot-dev-event-queue]
module.dynamodb_table["chatIds"].aws_dynamodb_table.autoscaled[0]: Refreshing state... [id=jung2bot-prod-chatIds]
module.dynamodb_table["messages"].aws_dynamodb_table.autoscaled[0]: Refreshing state... [id=jung2bot-prod-messages]
module.dynamodb_table["chatIds"].aws_dynamodb_table.this[0]: Refreshing state... [id=jung2bot-dev-chatIds]
module.dynamodb_table["messages"].aws_dynamodb_table.this[0]: Refreshing state... [id=jung2bot-dev-messages]
module.sqs["event"].aws_sqs_queue.this[0]: Refreshing state... [id=https://sqs.eu-west-1.amazonaws.com/477397881710/jung2bot-prod-event-queue]
data.aws_caller_identity.current: Reading...
data.aws_caller_identity.current: Read complete after 0s [id=477397881710]

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # module.sqs["event"].aws_sqs_queue.this[0] will be updated in-place
  ~ resource "aws_sqs_queue" "this" {
        id                                = "https://sqs.eu-west-1.amazonaws.com/477397881710/jung2bot-dev-event-queue"
        name                              = "jung2bot-dev-event-queue"
        tags                              = {}
      ~ visibility_timeout_seconds        = 100 -> 600
        # (13 unchanged attributes hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.
module.dynamodb_table["chatIds"].aws_appautoscaling_target.table_read[0]: Refreshing state... [id=table/jung2bot-prod-chatIds]
module.dynamodb_table["messages"].aws_appautoscaling_target.table_write[0]: Refreshing state... [id=table/jung2bot-prod-messages]
module.dynamodb_table["messages"].aws_appautoscaling_target.table_read[0]: Refreshing state... [id=table/jung2bot-prod-messages]
module.dynamodb_table["chatIds"].aws_appautoscaling_target.table_write[0]: Refreshing state... [id=table/jung2bot-prod-chatIds]
aws_sqs_queue_policy.this["event"]: Refreshing state... [id=https://sqs.eu-west-1.amazonaws.com/477397881710/jung2bot-prod-event-queue]
module.dynamodb_table["messages"].aws_appautoscaling_policy.table_write_policy[0]: Refreshing state... [id=DynamoDBWriteCapacityUtilization:table/jung2bot-prod-messages]
module.dynamodb_table["chatIds"].aws_appautoscaling_policy.table_write_policy[0]: Refreshing state... [id=DynamoDBWriteCapacityUtilization:table/jung2bot-prod-chatIds]
module.dynamodb_table["messages"].aws_appautoscaling_policy.table_read_policy[0]: Refreshing state... [id=DynamoDBReadCapacityUtilization:table/jung2bot-prod-messages]
module.dynamodb_table["chatIds"].aws_appautoscaling_policy.table_read_policy[0]: Refreshing state... [id=DynamoDBReadCapacityUtilization:table/jung2bot-prod-chatIds]

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # module.sqs["event"].aws_sqs_queue.this[0] will be updated in-place
  ~ resource "aws_sqs_queue" "this" {
        id                                = "https://sqs.eu-west-1.amazonaws.com/477397881710/jung2bot-prod-event-queue"
        name                              = "jung2bot-prod-event-queue"
        tags                              = {}
      ~ visibility_timeout_seconds        = 100 -> 600
        # (13 unchanged attributes hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- Reusing previous version of integrations/github from the dependency lock file
- Reusing previous version of vexxhost/uptimerobot from the dependency lock file
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of backblaze/b2 from the dependency lock file
- Installing vexxhost/uptimerobot v0.8.2...
- Installed vexxhost/uptimerobot v0.8.2 (self-signed, key ID 8FF00CD0B5FEAF59)
- Installing hashicorp/aws v5.21.0...
- Installed hashicorp/aws v5.21.0 (signed by HashiCorp)
- Installing backblaze/b2 v0.8.4...
- Installed backblaze/b2 v0.8.4 (signed by a HashiCorp partner, key ID 83D9CAF4848490D6)
- Installing cloudflare/cloudflare v4.16.0...
- Installed cloudflare/cloudflare v4.16.0 (self-signed, key ID C76001609EE3B136)
- Installing integrations/github v5.40.0...
- Installed integrations/github v5.40.0 (signed by a HashiCorp partner, key ID 38027F80D7FD5FB2)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html

Terraform has made some changes to the provider dependency selections recorded
in the .terraform.lock.hcl file. Review those changes and commit them to your
version control system if they represent changes you intended to make.

Terraform has been successfully initialized!
cloudflare_record.internal_record["sftpgo_internal"]: Refreshing state... [id=d53e66b848b3967bd5a9885eb2c8e08c]
cloudflare_record.internal_record["kiali_internal"]: Refreshing state... [id=3e29d0bc6567b4c0fecd6db58e432160]
cloudflare_record.public_record: Refreshing state... [id=16e19a8901e14239e7345e3922f318f9]
cloudflare_record.internal_record["argocd_internal"]: Refreshing state... [id=ad2633b9ce86a1786416dd851cb5c4d3]
cloudflare_record.internal_record["longhorn_internal"]: Refreshing state... [id=9d9e7849509ddd1ca1420bfb93085ddb]
cloudflare_record.internal_record["adguard_internal"]: Refreshing state... [id=5803590e9218027a34aae666383f8211]
cloudflare_record.internal_record["home_assistant_internal"]: Refreshing state... [id=0450593da9fcf9f32802e5152f53c349]
cloudflare_record.internal_record["jellyfin_internal"]: Refreshing state... [id=62786f77078b02d784342427605ba9e9]

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.


Variable attribute

Some links and functions uses attributes of Variable.data. So I cannot use numpy.ndarray and cudpy.ndarray directly although Function supports ndarrays.
I added attributes to Variable which returns corresponding values of ndarray.

I found that Variable.__len__ returns .data.size, and it is incompatible with ndarrays.

LGTM 👍


Allow nuxt dev mode on custom hosts resolving to localhost

In order to make shared-cookies work in localdev you have to use same host in the frontend and the backend.
So it should be possible to run nuxt on custom hostnames like
HOST=example.d9playground.localdev.space DRUPAL_BASE_URL=http://$HOST npm run dev
That's actually working now, but nuxt outputs a confusing "Listening" message still:

ℹ Listening on: http://localhost:3000/

Thanks to #35 client-side API calls now use relative paths - that means every HOST used will just work. There is on need to output or support special hosts any more, just use it if you want to.


Copy ready-to-go code for the filter

It would be nice if the web had a button that I could press for a given filter, and something like the following code would be copied into my clipboard:
let filter = CIFilter(
  name: "CIThermal",
  parameters: [
    "inputImage": <#inputImage#>
  ]
)!

This would be a very wonderful feature for the iOS app also!


deploy-ebpf.ps1 tries to deploy a file that is missing

Describe the bug
When using deploy-ebpf.ps1 -l as recommended in Method 2 of the installation instructions ( https://github.com/microsoft/ebpf-for-windows/blob/main/docs/InstallEbpf.md ), it tries to deploy ebpfforwindows_memory.wprp which is not present after I build.
I assume this file should just be removed from the list in the deploy-ebpf script, but perhaps it's suposed to be present and isn't building/generating somehow?  I can't find any other reference to this file in the repo.
OS information
No response
Steps taken to reproduce bug

Build
.\x64\Debug\deploy-ebpf.ps1 -l

Expected behavior
Deploys eBPF to temp folder per the docs
Actual outcome
Copy-Item : Cannot find path 'C:\Repos\ebpf-for-windows\x64\Debug\ebpfforwindows_memory.wprp' because it does not exist.
At C:\Repos\ebpf-for-windows\x64\Debug\deploy-ebpf.ps1:314 char:7

  Copy-Item "$source_path" -Destination "$destination_path" -Erro ...

  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : ObjectNotFound: (C:\Repos\ebpf-f...ows_memory.wprp:String) [Copy-Item], ItemNotFoundException
FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.CopyItemCommand

Additional details
No response

I tried manually removing this file from the list of files in deploy-ebpf.ps1 and there are other missing files (like common.psm1).  So perhaps the deploy-ebpf script has not been maintained?  Is this still a supported way to deploy locally built bits and test?

Duplicate of #2422


Function Module - Identifier must be lower case(keyword_case) and DATAEND issue

I have an issue where a FM name is flagged as it must be lowercase which is never the case. All FM names are always uppercase regardless. I do not know why a DATAEND issue is picked up.

Confirmed in vscode extension and abaplint cli.

in this example: https://github.com/larshp/abapGit/blob/master/src/zabapgit_parallel.fugr.z_abapgit_serialize_parallel.abap the developer has pretty printed the function module source code
The "Expected" errors are reported at the wrong positions, in the following example, the BEGIN OF DATA contains something wrong. As WRITE is not allowed inside BEGIN OF DATA, https://syntax.abaplint.org/?filter=data#/structure/Data
For your example, try copying the code into the https://playground.abaplint.org, and delete code until the statement causing the trouble is found

It looks like the "VALID BETWEEN begda AND endda" is causing the DATAEND issue:
  DATA BEGIN OF lt_p0045 OCCURS 0.
          INCLUDE STRUCTURE p0045.
  DATA END OF lt_p0045 VALID BETWEEN begda AND endda.

I also reported the "VALID BETWEEN begda AND endda" issue in #1234

w.r.t the FM name that should be lowercase as per check keyword_case, if you pretty print a FM in ADT or in SAP GUI the signature is changed to the example you provided(https://github.com/larshp/abapGit/blob/master/src/zabapgit_parallel.fugr.z_abapgit_serialize_parallel.abap ), but once you save the FM the ABAP backend automatically changes the FM name and signature to uppercase.
for example a FM pretty printed prior to saving:

and after saving:

Should it not always be assumed that FM names and signature will alway be uppercase regardless of whether the code was pretty printed or not?

try setting "ignoreFunctionModuleName": true, in the keyword_case rule, https://rules.abaplint.org/keyword_case/

@larshp , thanks, I should have gone and looked at rule first (Note to self)

I also did not remember it was there 🤷♂


Git.io deprecation

Just a quick heads up.
The URL shortener in your project might stop working soon.
Link: https://github.blog/changelog/2022-04-25-git-io-deprecation/

"While the git.io url redirection service is read-only and use of the service is limited, we have received feedback from developers and academic researchers who have published git.io links in print documentation and research papers. In order to preserve the integrity of these historical documents, we have decided to archive the current git.io links in a new read-only service that will allow us to serve redirects for those links longer term.
As we continue our analysis, we may remove individual links that point to spammy, malicious or 404 links. Our goal is to not break links relied on for legitimate use, especially by the academic community, while preserving the security of developers on GitHub.
That said, we still encourage users to make use of one of the many URL shortening services available with greater functionality than the git.io service provided. GitHub support will not be able to update or edit redirection records served by the git.io archive service."
Should keep working basically


Discussion: New features/UX changes for playground?

What new features are most in demand for the playground preset?
What feature requests can we cross reference from the soon to be retired prisma-labs/graphql-playground repo?
how can we channel some of this into graphiql plugin proposals that can be used by other presets?

An 'http headers' tab, as per discussion on https://github.com/graphql/graphiql/issues/59

hey @penx! that feature already exists in playground, so it's already implicitly part of the new preset, and will be available as a plugin for other presets.
I'm specifically asking for new features that graphql-playground itself does not already have that can be added to the playground specific preset spec, on behalf of the new team. So I'm looking for feature request issues from prisma-labs/graphql-playground repo that can act as candidates to migrate over.

regarding that feature, we hope to have a whole network sidebar with per-project default headers, verbs per operation type, other settings, in addition to the headers tab as a standalone plugin. because HTTP is not a requirement for GraphiQL, in 0.x or 1.x, it won't be part of core but all via closely maintained official plugins. the headers tab specifically will be maintained by the proposed  playground preset crew referenced above!

Export/Import operations as collections: prisma-labs/graphql-playground#6.
This is so useful for collaborating with team member and for working on different machines.

nice! we were planning on introducing a plugin for importing queries as a collection early on, in beta or the first few major versions.


qtwebengine: Fix build with ninja >= 1.10.0

For now just skip version check. Looked into: ninja came from meta-oe to
oe-core with:
commit fc3aef67a95a90e9a485c6b0e93db8cdeab5d3ab
Author: Khem Raj<EMAIL_ADDRESS>Date:   Thu Jul 27 21:52:12 2017 -0700
ninja: Add recipe

llvm is using it, therefore move it from meta-oe

Signed-off-by: Khem Raj<EMAIL_ADDRESS>
That was in rocko release cycle. So the assumption we have a ninja decent
enough should be acceptable.

Looked into qtwebengine current dev branch: There is no solution yet. So as
soon as upstream offers a better solution most likely this patch will not
apply any more and has to be removed then.

Signed-off-by: Andreas Müller<EMAIL_ADDRESS>

Is this error shown in log.do_configure? It seems to work for me without this patch:
Qt WebEngine Build Tools:
  Use System Ninja ....................... yes
  Use System Gn .......................... no

oe-coe upgraded ninja to 1.10 [1] and after that configure failed with

Ninja version too old

This is no surprise if you look at their regex:

contains(version, "1.[7-9].*"): return(true)

Is [1] already in your builds?
[1] https://github.com/openembedded/openembedded-core/commit/d1cd957cea29f3ab111ae752bc9ad75a1324c255

Rebuilding with master now to check. If that's the case then I'll update commit message to mention this commit, because the one from meta-oe/rocko confused me :).

Thanks and sorry: was not my best commit message ever...

I was able to reproduce it and updated version is now in master-next.
Thanks!

Applied 3e759d827722de6fddc9449f1149137021f4e25e


Internal error while creating updates: 'fiData'

I'm getting this error using 1.49 - let me know what debugging information I can provide:
Note: My mint account uses the new UI with the navigation on the left hand side; I'm using mintapi 2.1.
$ mint-amazon-tagger-go
Running version 1.49
You may be asked for an auth code at the command line! Be sure to press ENTER after typing the 6 digit code.
Creating a new webdriver
Navigating to Mint homepage.
Clicking "Sign in" button.
Mint Login Flow: Selecting username from multi-account selector.
Mint Login Flow: Entering password in MFA input
Mint Login Flow: Submitting credentials for MFA
Mint login successful.
Getting Mint categories.
Getting all Mint transactions since 2022-01-02 to None.
Internal error while creating updates: 'fiData'
Traceback (most recent call last):
  File "/Users/broz/.pyenv/versions/3.10.4/envs/filer-for-asana-3.10.4/lib/python3.10/site-packages/mintamazontagger/main.py", line 629, in create_updates
    self.do_create_updates(args, parent)
  File "/Users/broz/.pyenv/versions/3.10.4/envs/filer-for-asana-3.10.4/lib/python3.10/site-packages/mintamazontagger/main.py", line 685, in do_create_updates
    results = tagger.create_updates(
  File "/Users/broz/.pyenv/versions/3.10.4/envs/filer-for-asana-3.10.4/lib/python3.10/site-packages/mintamazontagger/tagger.py", line 144, in create_updates
    mint_trans = mint.Transaction.parse_from_json(
  File "/Users/broz/.pyenv/versions/3.10.4/envs/filer-for-asana-3.10.4/lib/python3.10/site-packages/mintamazontagger/mint.py", line 164, in parse_from_json
    result.append(cls(raw_dict))
  File "/Users/broz/.pyenv/versions/3.10.4/envs/filer-for-asana-3.10.4/lib/python3.10/site-packages/mintamazontagger/mint.py", line 101, in __init__
    self.__dict__.update(pythonify_mint_transaction_dict(raw_dict))
  File "/Users/broz/.pyenv/versions/3.10.4/envs/filer-for-asana-3.10.4/lib/python3.10/site-packages/mintamazontagger/mint.py", line 61, in pythonify_mint_transaction_dict
    raw_dict['fiData'] = FinancialInstitutionData(raw_dict['fiData'])
KeyError: 'fiData'
Internal error while creating updates: 'fiData'
$

I wasn't feeling confident that I'd be able to reproduce this error... until I accidentally did today. This happens for transactions that are user entered and therefore do not have an fiData object. Since these transactions aren't candidates for amazon payments in the first place, I've removed these from consideration by the tagger tool. Please try again in 1.52 and reopen this issue if you continue to have trouble. Thanks for reporting!

Great success!  Thank you so much, @jprouty.


ci: Add unsupported-version label action

Summary:
Users will provide issues or examples that use unsupported versions of React Native. Provide label to track and ask them to update example / issue to currently mainted version.
Changelog:
[Internal] - Support 'unsupported version' tag comment
Differential Revision: D42531703

Does anyone here have strong opinion over whether we close this immediately on the label being assigned or add the Needs: Author Feedback label (and stale bot will take care of neglected issues in +187 days)?

Does anyone here have strong opinion over whether we close this immediately on the label being assigned or add the Needs: Author Feedback label (and stale bot will take care of neglected issues in +187 days)?

I'd close it, no need to have an unsupported ticket staying around for 190~ days.

Does anyone here have strong opinion over whether we close this immediately on the label being assigned or add the Needs: Author Feedback label (and stale bot will take care of neglected issues in +187 days)?

I'd close it, no need to have an unsupported ticket staying around for 190~ days.

Added closing out any issue / PR tagged with Needs: Author Feedback after 31 days of inactivity (with a reminder after 24 days).


S3 image ContentType differs from image format

I am not sure whether this is a bug. If I understand correctly, you are saving the image in arbitrary format e.g. jpeg, png, etc.
But you are setting ContentType to be fixed at image/png. Shouldn't the ContentType be the same as the format saved?
If this is not a bug, can you tell me the logic behind this?
https://github.com/runpod/runpod-python/blob/cf7dae6be8aa85caec6213105222e10e4900b225/runpod/serverless/utils/rp_upload.py#L99-L110

This should be resolved in new versions of the SDK; please let me know if the issue persists.


Update field from dictionary correctly

Also, export run! and get_problems.

Coverage remained the same at 100.0% when pulling 4817dc2c7cdf0356ca76938233932006c4e7e7d0 on fix/update_from_dict into 80236e0e97e96c47715eb37c7163002a5bf54166 on master.


Consider adding multithreading later?

Thank you for your work. But your code is a little slow on the big data collection, and will you consider adding multithreading later?

@cowry5  Not sure.If time allowed,I will add it.


Ultima bomba

Changes / Comments
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[ ] Does the pull request title have the sheet name(s)? Include each sheet name.
[YES] Is this a bug fix?
[YES] Does this add functional enhancements (new features or extending existing features) ?
[YES] Does this add or change functional aesthetics (such as layout or color scheme) ?
[] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

hi @Reonin , I'm having trouble viewing the logo, can you help me?


ISCSI cleanup thread breaks non-managed storage utilizing ISCSI connectivity

ISSUE TYPE

Bug Report

COMPONENT NAME
KVM plugin
CLOUDSTACK VERSION
4.13.1 and 4.14
CONFIGURATION
KVM with unmanaged ISCSI
OS / ENVIRONMENT

SUMMARY
Change was introduced in https://github.com/apache/cloudstack/commit/6baa598033fa3f78b5b0144275de8c1404f67f29
It adds a cleanup process for old iscsi connections. Unfortunately, it doesn't appear to be scoped and makes the assumption that all iscsi is managed. When working with a community member on slack who upgraded to 4.13.1 found that it broke their unmanaged ISCSI storage.
STEPS TO REPRODUCE
Upgrade an unmanaged ISCSI based system to 4.13.1 and your iscsi will be ripped out when the agent is started.
ACTUAL RESULTS
2020-07-14 21:50:21,607 DEBUG [kvm.resource.LibvirtConnection] (Thread-6:null) (logid:) Looking for libvirtd connection at: qemu:///system
2020-07-14 21:50:21,610 DEBUG [kvm.storage.IscsiStorageCleanupMonitor] (Thread-6:null) (logid:) found iscsi disk by cleanup thread, marking inactive: /dev/disk/by-path/ip-<IP_ADDRESS>:3260-iscsi-iqn.2001-05.com.equallogic:0-1cb196-21b284232-40d0019858b5679f-cloudstack1-lun-0
2020-07-14 21:50:21,611 DEBUG [kvm.storage.IscsiStorageCleanupMonitor] (Thread-6:null) (logid:) found 0 domains
2020-07-14 21:50:21,617 INFO  [kvm.storage.IscsiStorageCleanupMonitor] (Thread-6:null) (logid:) Cleaning up disk /dev/disk/by-path/ip-<IP_ADDRESS>:3260-iscsi-iqn.2001-05.com.equallogic:0-1cb196-21b284232-40d0019858b5679f-cloudstack1-lun-0
2020-07-14 21:50:21,618 DEBUG [kvm.storage.IscsiAdmStorageAdaptor] (Thread-6:null) (logid:) Executing: sudo iscsiadm -m node -T iqn.2001-05.com.equallogic:0-1cb196-21b284232-40d0019858b5679f-cloudstack1 -p <IP_ADDRESS>:3260 --logout
2020-07-14 21:50:21,623 DEBUG [kvm.storage.IscsiAdmStorageAdaptor] (Thread-6:null) (logid:) Executing while with timeout : 3600000
2020-07-14 21:50:21,658 INFO  [cloud.agent.Agent] (main:null) (logid:) Connecting to host:<IP_ADDRESS>
2020-07-14 21:50:21,659 INFO  [utils.nio.NioClient] (main:null) (logid:) Connecting to <IP_ADDRESS>:8250
2020-07-14 21:50:21,659 WARN  [utils.nio.NioConnection] (main:null) (logid:) Unable to connect to remote: is there a server running on port 8250
2020-07-14 21:50:21,759 DEBUG [kvm.storage.IscsiAdmStorageAdaptor] (Thread-6:null) (logid:) Execution is successful.
2020-07-14 21:50:21,760 DEBUG [kvm.storage.IscsiAdmStorageAdaptor] (Thread-6:null) (logid:) Logging out of session [sid: 1, target: iqn.2001-05.com.equallogic:0-1cb196-21b284232-40d0019858b5679f-cloudstack1, portal: <IP_ADDRESS>,3260]
Logging out of session [sid: 2, target: iqn.2001-05.com.equallogic:0-1cb196-21b284232-40d0019858b5679f-cloudstack1, portal: <IP_ADDRESS>,3260]
Logout of [sid: 1, target: iqn.2001-05.com.equallogic:0-1cb196-21b284232-40d0019858b5679f-cloudstack1, portal: <IP_ADDRESS>,3260] successful.
Logout of [sid: 2, target: iqn.2001-05.com.equallogic:0-1cb196-21b284232-40d0019858b5679f-cloudstack1, portal: <IP_ADDRESS>,3260] successful.
2020-07-14 21:50:21,761 DEBUG [kvm.storage.IscsiAdmStorageAdaptor] (Thread-6:null) (logid:) Successfully logged out of iSCSI target /iqn.2001-05.com.equallogic:0-1cb196-21b284232-40d0019858b5679f-cloudstack1/0
2020-07-14 21:50:21,761 DEBUG [kvm.storage.IscsiAdmStorageAdaptor] (Thread-6:null) (logid:) Executing: sudo iscsiadm -m node -T iqn.2001-05.com.equallogic:0-1cb196-21b284232-40d0019858b5679f-cloudstack1 -p <IP_ADDRESS>:3260 -o delete
2020-07-14 21:50:21,762 DEBUG [kvm.storage.IscsiAdmStorageAdaptor] (Thread-6:null) (logid:) Executing while with timeout : 3600000
2020-07-14 21:50:21,787 DEBUG [kvm.storage.IscsiAdmStorageAdaptor] (Thread-6:null) (logid:) Execution is successful.
2020-07-14 21:50:21,788 DEBUG [kvm.storage.IscsiAdmStorageAdaptor] (Thread-6:null) (logid:) Removed iSCSI target /iqn.2001-05.com.equallogic:0-1cb196-21b284232-40d0019858b5679f-cloudstack1/0
2020-07-14 21:50:21,789 DEBUG [kvm.storage.IscsiAdmStorageAdaptor] (Thread-6:null) (logid:) Executing: sudo blockdev --getsize64 /dev/disk/by-path/ip-<IP_ADDRESS>:3260-iscsi-iqn.2001-05.com.equallogic:0-1cb196-21b284232-40d0019858b5679f-cloudstack1-lun-0
2020-07-14 21:50:21,790 DEBUG [kvm.storage.IscsiAdmStorageAdaptor] (Thread-6:null) (logid:) Executing while with timeout : 3600000
2020-07-14 21:50:21,813 DEBUG [kvm.storage.IscsiAdmStorageAdaptor] (Thread-6:null) (logid:) Exit value is 1
2020-07-14 21:50:21,814 DEBUG [kvm.storage.IscsiAdmStorageAdaptor] (Thread-6:null) (logid:) blockdev: cannot open /dev/disk/by-path/ip-<IP_ADDRESS>:3260-iscsi-iqn.2001-05.com.equallogic:0-1cb196-21b284232-40d0019858b5679f-cloudstack1-lun-0: No such file or directory
2020-07-14 21:50:21,814 WARN  [kvm.storage.IscsiAdmStorageAdaptor] (Thread-6:null) (logid:) Unable to retrieve the size of device (resource may have moved to a different host)/dev/disk/by-path/ip-<IP_ADDRESS>:3260-iscsi-iqn.2001-05.com.equallogic:0-1cb196-21b284232-40d0019858b5679f-cloudstack1-lun-0
At this point all the luns have been cleared out, even though the ISCSI luns were not being managed by CloudStack.

@skattoju4 @GabrielBrascher

i will work on this

Fixed in https://github.com/apache/cloudstack/pull/4219