Lower replicas setting for low-nodecount deployments

Swift in Liberty or newer started refusing devicecount < $((zones*replicas)),
which is totally sensible, but wasn't ensured by the test environment

https://github.com/crowbar/crowbar-openstack/pull/746 is needed for gating to pass, right?

@jsuchome to unbreak the PR gating I've already merged the crowbar/crowbar-openstack#746 change into the packages.

PR gating is beyond swift deployment -> works

 (5) S53P4 switch swift to Newton version


Donate action broken

Clicking on donate navigates to a URL that seems to be infinitely redirecting or reloading (on Firefox Focus at least).

I have added an issue to the web page repository


is this support for torrent ?

No unfortunately not.
It only supports http/https.

thanks

But you could create a pull request :)


npm run preinstall in authorize-idp

Description
Running npm install or npm run preinstall leads to a permissions error.
To Reproduce

Run
npm install

or
npm run preinstall

See error
$ npm run preinstall

><EMAIL_ADDRESS>preinstall
> npm list<EMAIL_ADDRESS>-g || npm install<EMAIL_ADDRESS>-g

/usr/local/lib
└── (empty)

npm ERR! code EACCES
npm ERR! syscall symlink
npm ERR! path ../lib/node_modules/pem-jwk/bin/pem-jwk.js
npm ERR! dest /usr/local/bin/pem-jwk
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, symlink '../lib/node_modules/pem-jwk/bin/pem-jwk.js' -> '/usr/local/bin/pem-jwk'
npm ERR!  [Error: EACCES: permission denied, symlink '../lib/node_modules/pem-jwk/bin/pem-jwk.js' -> '/usr/local/bin/pem-jwk'] {
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'symlink',
npm ERR!   path: '../lib/node_modules/pem-jwk/bin/pem-jwk.js',
npm ERR!   dest: '/usr/local/bin/pem-jwk'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

npm ERR! A complete log of this run can be found in: /Users/dchiesa/.npm/_logs/2024-03-02T01_44_13_832Z-debug-0.log

Additional Context
I ran this on MacOS with
$ npm --version
9.8.1

Expected behavior
install or preinstall should work.  In fact there is no need to require global installation of the pem-jwk module.
The script that uses the module (deploy-authorize-idp-access-tokens.sh ) can easily reference it from node_modules.

have to run with sudo
sudo npm install as the preinstall script is installing the module globally


Bump html_query_plan to 2.6

Fixes https://github.com/Microsoft/azuredatastudio/issues/3491.  See https://github.com/anthonydresser/html-query-plan/pull/8 for details.

vbump-only, merging


Change Default Overlay Keybind

Description
Every time I type sentences using proper capitalization, I accidentally open the overlay because of the delay/speed of still holding shift while hitting space. This happens frequently when I start a sentence with "I ", everytime.
Reproduction steps
Try to type a sentence starting with a capital I and not open the overlay (Ie: steam friend messages).
Screenshot
Not Needed.
If it's required that the overlay must have a key bind, absolutely fine. but PLEASE let me change it from shift+space to something else as I've uninstalled this app multiple times out of pure rage and re-installed it out of pure necessity!
Thanks!

You can already change this

@Kvan7 maybe I'm overlooking something fundamental, but what does that asterisk imply? I've tried changing the overlay bind and it seemingly doesn't do anything.
I'll try again though shortly! Apologies if this does work and I'm doing it wrong

Make sure you hit save in the bottom right, otherwise it won't do anything

what does that asterisk imply?

 Was just trying to unbind and assumed it meant it couldn't be changed.

All good! Glad it worked out!


working with timeline and modal

dear all,
I trying to work with time line inside of a modal with no success, is there a known issue about it?

Have u placed a Z index on the timeline and still u did not see anything ?


macOS asks for permission to use the microphone

Bevy version
0.13.2
[Optional] Relevant system information
macOS Sonoma 14.5
MacBook Pro 13" M2
What you did
When I run the game on macOS from the terinal, RustRover and the compiled binary.
What went wrong
It works but macOS asks for microphone permission.
Additional information

Does this happens with Bevy examples?

I tried volumetric_fog and it happened there too.

can't reproduce on my Mac

I can remember running into this while running Foxtrot on my macOS, which surprised me. I'll check if I can reproduce this with the given example.

I can confirm I can reproduce the bug. I thought I couldn't at first, but then realized that I already had disallowed my terminal to use the microphone, so no new popup came up. Steps to reproduce:

compile volumetric_fog on main
download a fresh iTerm2, because a new app doesn't have any previous security and access settings on my machine
run the previously compiled example on iterm:

results in:

My machine:

I used tccutil to reset the microphone permission for the terminal app. That way the permission prompt shows up again when I run a bevy app (cargo run --example volumetric_fog on main).
For macOS' Terminal the command is tccutil reset Microphone com.apple.Terminal. Alternatively for WezTerm: tccutil reset Microphone com.github.wez.wezterm

I managed to narrow this down to the function default_output_device in cpal which gets called via AudioPlugin → AudioOutput::default → OutputStream::try_default.
cpal::default_host().default_output_device();

Marking as blocked since this seems like a cpal issue then. Unless we can pass some magic parameters.

Is there an upstream issue for this?

Yeah @bash was kind enough to investigate :)


Ctrl + Shift + letter keybinds not working

Lapce Version
0.2.0
System information
Arch Linux, Hyprland wm on Wayland
Describe the bug
Binding i.e. Toggle Line Comment to Ctrl + Shift + a does nothing. Binding to Ctrl + Alt + a does work as expected. Binding to Ctrl + Alt + F8 does work properly.
Additional information
Maybe shift key and letter capitalization could be the problem?

Are you using lapce 0.2.0 ? Not 100% sure but I think this is already fixed on latest master.

Stable release 0.2.0 from arch repository. I'll try building the git master, will close if its fixed.

Works with nightly so ill close this :+1:


Add support for annotations into Schema

Using macros, we should pick up and store annotations on case classes, enumerations (sealed traits), and the individual terms that make up them (fields in case classes, cases of enumerations).
This way, without macros, users of Schema can peer into and alter behavior based on annotations.

@jdegoes Going to start work on this one. A couple of questions though:

Do we want to preserve the annotations when going from CaseClassN -> GenericRecord (ie when calling CaseClassN.structure)? I could see where we might want to hand on to them if we use the generic representation as an intermediate encoding when do migrations between case class versions.
If we want to encode annotations in GenericRecord, should we allow them to be specified when manually constructing a GenericRecord

I think we want to preserve the annotations in the conversion, and because individual fields can have annotations, we'll probably need to store that data in either a tuple or a wrapper data type that stores both the schema of the field as well as its (field-specific) annotations.

I think we should allow the user to attach annotations to something constructed by hand.


adding generate_arn()

#939  Added the missing generate_arn() to rdscluster.py

this mechanism for obtaining the account id is different in current trunk, effectively account id always populated in options.


eslint: Enable sort-imports rule

I figure we should enable this before we have lots of imports.
Testing Plan: Dev server

Yeah, this is great, feel free to merge once it passes CI.


[PROJECT] Collective Dashboard Overview

An overview page should address the issue that as a collective admin, I currently lack an overview of what is going on in my projects and events. A goal of this project is for a collective admin to be able to answer:

In which projects and events do I have money
Which projects and events have recurring contributions
Which projects and events have pending expenses

By default, the collective overview page needs to handle when a collective has a large number of projects or events. This is a default functionality and not an edge case.

It should be possible to create a new project or event directly from the collective overview page
When a project or event is created from the overview page, I go through the entire creation flow without leaving the dashboard

Halaman ikhtisar harus mengatasi masalah bahwa sebagai admin kolektif, saat ini saya tidak memiliki gambaran umum tentang apa yang terjadi dalam proyek dan acara saya.  Ini adalah fungsi default dan bukan kasus Edge.

Proyek atau acara baru dapat dibuat langsung dari halaman ikhtisar kolektif
Ketika sebuah proyek atau acara dibuat dari halaman ikhtisar, saya menjalani seluruh alur pembuatan tanpa meninggalkan dasbor

https://github.com/opencollective/opencollective/issues/7215

https://github.com/opencollective/opencollective/issues/7215

This week

[ ] Add API resolver for Balance time series
[ ] Add API resolver for Total amount spent time series
[ ] Finalize and merge latest frontend changes

Status in the last week of the cycle
Outcomes
Collective admins can answer:

[x] Where in the collective and its projects and events do I have money?
[ ] Does the collective and its projects and events have recurring contributions?

We decided to de-prioritize this for a later iteration.

[x] Does the collective and its projects and events have pending expenses?
[x] Which financial activities have happened recently in my collective and its projects and events?

There is an activity log on the overview page. We still need sub-account activities from the main account timeline.

Collective admins can take the following actions:

[x] Create new projects through the overview page.

A minimal implementation where the +New button takes you to the existing Project or Event creation flow. This is not ideal, as it takes you out of the dashboard. This should be addressed in a future project around managing Accounts on the Dashboard.

[ ] Open a modal that allows emptying, archiving, or deleting a project or event.

We de-prioritized the modal. Instead, selecting "Archive account" takes you to the settings page /advanced that allows emptying and archiving.


../seat.c:573:14: error: ‘struct wlr_drag_icon’ has no member named ‘is_pointer’

I just rebuilt wlroots from master.
$ meson build
The Meson build system
Version: 0.49.2
Source dir: /home/bbigras/cage
Build dir: /home/bbigras/cage/build
Build type: native build
Project name: cage
Project version: 0.0.1
Native C compiler: cc (gcc 8.2.0 "cc (Debian 8.2.0-21) 8.2.0")
Build machine cpu family: x86
Build machine cpu: i686
Found pkg-config: /usr/bin/pkg-config (0.29)
Dependency wlroots found: YES 0.3.0
Dependency wayland-protocols found: YES 1.17
Dependency wayland-server found: YES 1.16.0
Dependency pixman-1 found: YES 0.36.0
Dependency xkbcommon found: YES 0.8.2
Library m found: YES
Program wayland-scanner found: YES (/usr/bin/wayland-scanner)
Configuring config.h using configuration
Message:
Cage 0.0.1

    xwayland: 0

Build targets in project: 1
Option werror is: True [default: true]
Found ninja-1.8.2 at /usr/bin/ninja
bbigras@debian:~/cage$ ninja -C build
ninja: Entering directory `build'
[4/8] Compiling C object<EMAIL_ADDRESS>FAILED<EMAIL_ADDRESS>cc -Icage@exe -I. -I.. -I/usr/local/include -I/usr/include/libdrm -I/usr/include/pixman-1 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -Werror -std=c11 -g -DWLR_USE_UNSTABLE -Wall -Wundef -Wno-unused-parameter -DDEBUG  -MD -MQ<EMAIL_ADDRESS>-MF<EMAIL_ADDRESS>-o<EMAIL_ADDRESS>-c ../seat.c
../seat.c: In function ‘drag_icon_update_position’:
../seat.c:573:14: error: ‘struct wlr_drag_icon’ has no member named ‘is_pointer’
  if (wlr_icon->is_pointer) {
              ^~
../seat.c:578:49: error: ‘struct wlr_drag_icon’ has no member named ‘touch_id’
    wlr_seat_touch_get_point(seat->seat, wlr_icon->touch_id);
                                                 ^~
../seat.c: In function ‘seat_create’:
../seat.c:731:35: error: ‘struct <anonymous>’ has no member named ‘new_drag_icon’
  wl_signal_add(&seat->seat->events.new_drag_icon, &seat->new_drag_icon);
                                   ^
[5/8] Compiling C object<EMAIL_ADDRESS>ninja: build stopped: subcommand failed.

I develop Cage against the latest wlroots tag, which as of yesterday was 0.3. I should probably add a little note to the README to make this explicit!

Thanks!


add some names for #53

Coverage remained the same at 61.903% when pulling 2b12caf39cf371515bdd05ac3b2447df9d1cd242 on jay20162016:master into dc9d5fa5e8493170428e51302eb4b6504d939ce0 on codecombat:master.


Cannot find module 'ipfs'

I seems there is some missing dependancies..  :  Cannot find module 'ipfs'
It doesn not work neithe when I download the ipfs package

Oh dang, the README hasn't been updated in a while.
It should instead look like
const IPFS = require('ipfs-core')
const makeIpfsFetch = require('ipfs-fetch')

const ipfs = await IPFS.create()
const fetch = await makeIpfsFetch({ipfs})

I'll update it in a sec.


No support for strict_types on PHP 7

Current implementation complains about unknown declare for strict_types. Also, if that line is commented, it further complains that default values with classes typehint should always be null, in a code like test(string $var = '') { }

Laravel 5.1 itself isn't PHP 7 ready at the moment. Right now IDE-helper has more important problems with PHP 5.x side of things, I don't think PHP 7 should have higher priority for early future.

Well, I've started using Laravel 5.1 with PHP7 and it didn't show any problems for now - but my project is still in its early stages. Also, Homestead have released support for PHP7 as well. So I guess it is, indeed, PHP7 ready.
Meanwhile, I do understand your point about this project. I don't think PHP7 should indeed have higher priority, but it's still a big issue nonetheless, that should be seen when the time arrive :)

I'd like to revive this issue as the _ide_helper.php file generated with php artisan ide-helper:generate copies declare(strict_types=1); from source files specified in config/ide-helper.php within the helper_files array. This leads to multiple declarations in the helper file, which isn't allowed by the PHP spec and therefore IDEs complain quite a bit.
It would probably be enough to also replace declare(strict_types=1); at the same time as <?php when including helper files here:
https://github.com/barryvdh/laravel-ide-helper/blob/32df0a3bc641aa225f7ec988c1d5a95509f20e28/src/Console/GeneratorCommand.php#L102-L108
It should be noted that there can be different notations (like declare(strict_types = 1);, which makes replacement by regex more suitable.

I can confirm this, but:
What is the real use-case for having the helper files define in here?
For me, PhpStorm already properly autocompletes this even without this in _ide_helper.php, simply because any vendor/ file is available for autocomplete anyway.


[#228] Implement Privacy Center client app

Purpose
Implements Next.js / React Privacy Center client app based on the fidesui-template repo. Demo here.
Note: because there is no hosted fidesops server any requests made through this UI will fail.
Changes

Creates clients directory at repo root
Implements Next.js client app
Implements testing strategy for Next app

Checklist

[ ] Applicable documentation updated (guides, quickstart, postman collections, tutorial, fidesdemo, database diagram)
[ ] Good unit test/integration test coverage
[ ] This PR contains a DB migration. If checked, the reviewer should confirm with the author that the down_revision correctly references the previous migration before merging
[ ] The Run Unsafe PR Checks label has been applied, and checks have passed, if this PR touches any external services

Ticket
Described by #228

This branch is a fork, so cannot access the secrets, hence the unsafe checks are failing


[FormRecognizer] Migrate to test-proxy

We needed to revert part of the changes introduced in https://github.com/Azure/azure-sdk-for-net/pull/25879 because tests using the DisableRequestBodyRecording scope would fail in Record mode (even though they work just fine when running Live).
Now we need to understand what exactly is causing the problem, fix it, and remove the useLegacyTransport: true argument we pass in the DocumentAnalysisLiveTestBase and FormRecognizerLiveTestBase constructors.
Note: the constructor changes mentioned above have only been applied in the feature/formrecognizer/v400b3 feature branch of the private repo for now. It will eventually be merged into the public repo.
Related discussion (private repo): https://github.com/Azure/azure-sdk-for-net-pr/pull/1562/files#r792266132

I can re-migrate once https://github.com/Azure/azure-sdk-tools/issues/2434 is addressed in Test Proxy.


MTL-2076 Switch to virtualenv

Summary and Scope

Fixes: MTL-2076

Issue Type

RFE Pull Request

This change brings in a few enhancements to the repository, and some fundamental changes to the Python Environment:

Addition of new promotion workflows that automatically create releases on GitHub for every tag. See Promotion workflows
Changing the RPM packaging from depending on PyPi packages from the OS package manager to instead using a virtualenv and managing its dependencies in an isolated manner. See virtualenv change

Promotion workflows
When a prerelease or release tag is pushed to the repository, a new GitHub Prerelease or Release is created.
When a new Prerelease is created, it will be marked as a prerelease.
When a new Release is created, it will be marked as the latest release.
In the future we can add logic for including the RPM assets in the release, for now I am working that logic out in another repository.
virtualenv change
This change switches libCSM to use a virtualenv, and in doing so it enables us to write Python code using non-native Python modules. Prior to this change, we were limited to the very small set of Python modules SUSE shipped in their Python3.9 and Python3.10 repositories. This change enables us to use any PyPi package (e.g. python310-kubernetes does not exist, so we can not use code that requires import kubernetes).
This new virtualenv environment will still depend on the base system installation of Python, respective to the Python version available in that distro.
Due to the fact that libCSM will no longer be using the OS package management for its dependencies, the name of the package has now changed.

python39-libcsm is now libcsm, and still only published to 15SP3 repos
python310-libcsm is now libcsm, and still only published to 15SP4 repos

Despite converging to the same name, each package will still require python39-base or python310-base to be installed. This is determined by which repository libcsm was pulled from. The SP3 libCSM will require python39-base, and the SP4 libCSM will require python310-base. This will scale for future distros, as we continue to build for their latest Python. For example below shows installing the SP3 version on an SP4 system where python39-base is not available will fail:
redbull-pit:~ # rpm -q python310-base
python310-base-3.10.8-1504<IP_ADDRESS>.x86_64
redbull-pit:~ # rpm -Uvh https://artifactory.algol60.net/artifactory/csm-rpms/hpe/unstable/sle-15sp3/libcsm/noarch/libcsm-0.0.3.dev2%2Bgfb2c70d-1.noarch.rpm
Retrieving https://artifactory.algol60.net/artifactory/csm-rpms/hpe/unstable/sle-15sp3/libcsm/noarch/libcsm-0.0.3.dev2%2Bgfb2c70d-1.noarch.rpm
error: Failed dependencies:
        python39-base is needed by libcsm-0.0.3.dev2+gfb2c70d-1.noarch
redbull-pit:~ # rpm -Uvh https://artifactory.algol60.net/artifactory/csm-rpms/hpe/unstable/sle-15sp4/libcsm/noarch/libcsm-0.0.3.dev2%2Bgfb2c70d-1.noarch.rpm
Retrieving https://artifactory.algol60.net/artifactory/csm-rpms/hpe/unstable/sle-15sp4/libcsm/noarch/libcsm-0.0.3.dev2%2Bgfb2c70d-1.noarch.rpm
Preparing...                          ################################# [100%]
Updating / installing...
   1:libcsm-0.0.3.dev2+gfb2c70d-1     ################################# [100%]

Prerequisites

[ ] I have included documentation in my PR (or it is not required)
[x] I tested this on internal system (if yes, please include results or a description of the test)
[ ] I tested this on a vshasta system (if yes, please include results or a description of the test)

Idempotency

Risks and Mitigations

This is missing an update to the documentation for using libCSM python.

This is missing an update to the documentation for using libCSM python.

Done.


[5.6] Allow running tests from a command plugin (#4002)

This is a WIP cherry-pick of https://github.com/apple/swift-package-manager/pull/4002.  Rationale and risk assessment for nominating for 5.6 to be added.

@swift-ci test

@swift-ci please test

@swift-ci please test


RFE: add button to randomize the playing field

The shell offers a button to randomize the playing field (with a confirmation dialog to make sure you don't press it on accident). We should also have this in the web frontend. It works by sending a RandomizeField message with no arguments to the refbox, although I don't know whether the websocket backend already supports that.

It does support it. Will do


How to load Video within ASYNC?

protected void onPostExecute(Void aVoid) {
            // How am I suppose to add youTubePlayer.loadVideo(videoId, 0);
            super.onPostExecute(aVoid);
        }

Hi so I am currently using ASYNC and I would like to use youTubePlayer.loadVideo(videoId, 0); within the onPostExecute method how am I able to do this thank you any help is appreciated.

I have resolved the issue thank you.


LEARN TO CODE STOP USING CURSOR!!!!

Instead of spending time on repetitive tasks or trying to write reusable code for other projects (which rarely ever happens), you can create quick, one-off, and practical code with minimal effort.
Proper use of these tools can also provide you with clean snippets of code to get your tasks done quickly. These pieces can later serve as puzzle pieces you can incorporate into other projects.


Can't import a Gliffy file twice from my device

Preflight Checklist

[ x] I agree to follow the Code of Conduct that this project adheres to.
[ x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Describe the bug
I'm trying to import a Gliffy diagram from my Device into an empty draw.io drawing.
This only works once. When I try to do this a second time, it doesn't work anymore. Nothing happens. No errors on the console either.
Or in the same diagram, or in a new/other diagram in the same Chrome browser. Same issue.
The only way I can make it work again is "Clear Site Data" using the Developer tools and reload the diagram again and do an "Authorize" again (the big blue button appears again).
Then I can import 1 diagram and we're back to square one.
To Reproduce
Steps to reproduce the behavior:

Go to 'Import in the menu', select 'Device..'
Select the gliffy file from your device
The file will import and a diagram is rendered and saved
Now do this again (in a new drawing, an existing one, ..)
When the file is selected from Device nothing happens anymore

Expected behavior
The file is each time uploaded and converted to a draw.io diagram
draw.io version (In the Help->About menu of the draw.io editor):

I use draw.io using https://app.diagrams.net (so not in Confluence)

Desktop

Chrome Version 80.0.3987.149 (Official Build) (64-bit)
Firefox 72.0.2 (64-bits) (same issue)
Mac OS Catalina, 10.15.3

Can you try again. Is should be fixed

It works now, but I had to perform a "Clear Site Data" once more (probably to reload the fixes?)

Thx for the quick help!!


49 chat implementation

This is a pull request for implementing the chat. Since I'm still not able to do any testing, I would love for the reviewers to check that everything is working correctly before merging into main. If some problems emerge, they are probably caused by not having deviceList and statusField (which were in the old version) included in the chat. I have tried to comment everything related to the use of those components out but just wanted to say this to help the process of reviewing.

Code looks good from what I know. I haven't been able to test connecting with another device, but transitions and clicking work as they should when I run it on the emulator


Fix python API for new linear disassembly structure

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


[Bug] Not all tasks visible all the time

When I first loaded in the addon, the alchemy header wasn't visible at all.
I reloaded, now the header is visible, but not the tasks underneath:

Only after reloading again it shows the tasks properly.

I guess you could cache the info? Save the highest recorded info returned by C_TradeSkillUI.GetProfessionInfoBySkillLineID(skillLineID) 🤔

This should be better in v<IP_ADDRESS>:

can get the latest skill level once again
puts an annoying pink message when it needs you to open a profession (mostly enabling Dragonflight profession chores)
doesn't overwrite the known skill level for a pre-current profession


Update to sqlx 0.8

Dear all,
Can you please consider updating axum_session_sqlx (its Cargo.toml) to use the newly released sqlx 0.8.0?
Thanks.

will get on this. Thanks for letting me know they released the next version

This has been completed s of commit c4e2c238939efc0ab1b820c6ad828cd0201ab9b3 and published to crates.io


stop using tmpdir() due to runtime inconsistencies

This is a fix for https://github.com/talonhub/community/issues/966, which makes it possible to use nix environments in vscode and still have command client / server work.
I haven't actually tested this on windows, as I don't have it, so I'm not sure if the path I used is sufficient. This will have a corresponding pull request for community, and unfortunately this means that things will break for people that don't update both at the same time.
Its also worth noting that in the issue 966 above, there was a suggestion to use XDG_RUNTIME_DIR on Linux, which I had implemented and tested originally. However, when looking into snaps I ran across https://forum.snapcraft.io/t/rethinking-how-we-handle-xdg-runtime-dir/22223 which suggests that they may want to change snaps to no longer have access to the same XDG_RUNTIME_DIR folder. If they actually ever implemented that then this would break, so in the end I opted not to use it.
There's also per user temp directories on mac, which you can query using getconf DARWIN_USER_TEMP_DIR, but I decided not to keep that code in the end since it keeps the mac/linux case simpler both using /tmp, especially in light of not using XDG_RUNTIME_DIR in the end.

Looks fine with some comments.
Also, we need to figure out backwards compatibility here. The command-server VSCode extension will be updated automatically by VSCode, whereas the Talon side requires a manual git pull.
The VSCode extension creates the communication directory on init. I think the easiest / most robust thing to do is to
* create both old and new directories on init

* every time the client hits the keystroke that triggers a read, look in both directories for `request.json` and use the newer one (or the only one that exists if only one exists)

There are plenty of ways to optimise that approach, but I think that's a robust way to start. cc/ @lunixbochs

I updated the windows folder here to use .comms to match the other side.
I also added code for handling backwards compatibility as suggested above, and have tested it on both the old and new folders (on Linux only so far) and confirmed it works.
I did briefly run into an issue when testing back and forth over and and over again that sometimes cursorless thinks it can't find hat markers and that lasts for some amount of time (maybe the minute timeout?), which I seems to be related to the prePhrase signaling, though I'm not very familiar with how that code works yet. The hat errors would eventually go away and then it would work normally.
I think that might have been due to some stale data being present in the signaling folder though, as it's not happening for me anymore. But I thought I'd mention it in case it helps ring any alarm bells while you're reviewing the changes.

I made a bunch of changes code because the order in commandRunner is really important, and it needs to be as clear as possible what's happening there. This code is really subtle, so I wanted NativeIo and commandRunner to be as simple as possible. @lunixbochs and I spent a bunch of time working out the different possible ways things could fail so I want to preserve that order
Lmk if my changes don't make sense
I tested commands and prePhrase signal on both community main and https://github.com/talonhub/community/issues/966

btw @bjaspan your abstraction is already paying off 🙌

Tested it and it works well on my end too, and without the hat warnings I had run into. Also looks good to me.

Looks like you dropped the .comms folder here but not on the talon side? I'm on the mobile app so can't add a comment directly on the change it seems.

Looks like you dropped the .comms folder here but not on the talon side? I'm on the mobile app so can't add a comment directly on the change it seems.

I don't think so. Maybe have another look on desktop?

Ah ya I see now, disregard.

Just to say that I've tested this PR with neovim on Windows and it works fine:
2024-06-10 16:58:39 INF loadExtension(command-server): start
2024-06-10 16:58:39 INF Creating communication dir C:\Users\User\AppData\Roaming\talon\.comms\neovim-command-server
2024-06-10 16:58:39 INF Creating communication dir C:\Users\User\AppData\Local\Temp\neovim-command-server
2024-06-10 16:58:39 INF loadExtension(command-server): done

Rebased this finally because vscode likes to occasionally ignore my don't auto-update extension settings sometimes and clobber the custom 0.9 extension I use with this fix. Still will need to be tweaked depending on how #27 develops.


Make CookieName of CookieTempDataProvider configurable

The name of the cookie seems to be fixed, while other components (Antiforgery, Session, ...) are open for alternatives. Making this configurable seems to be a breaking change, since there is already a public static property exposing that fixed value, though.
Is there any reason why this is "hard-coded"? Can we make it configurable instead?
I could prepare a PR for that.

@axelheer this seems reasonable. If you send a PR we can certainly review it for consideration in 2.0.0.


Test connection does not work when supplying just the machine name

Since we only append protocol and port on Save

We can do it on the "lost focus" instead.


Refactored code

Made the code a bit shorter and used some newer C# stuff like C# 8.0 Null Coalescing Assignment.

Made changes requested.


install error

Caused by: java.lang.UnsupportedClassVersionError: com/c301/plugin/commit/CreateCommitAction has been compiled by a more recent version of the Java Runtime (class file version 61.0), this version of the Java Runtime only recognizes class file versions up to 55.0

Caused by: java.lang.UnsupportedClassVersionError: com/c301/plugin/commit/CreateCommitAction has been compiled by a more recent version of the Java Runtime (class file version 61.0), this version of the Java Runtime only recognizes class file versions up to 55.0

Okay, I will fix it in the next two days, please pay attention to the update record at that time


[chore](thrift exception) do not log message in thrift exception

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall


Remove NVVM-specific pass from XPU pipeline.

We run tritongpu-accelerate-matmul pass with capability=0 executing transformations that are specific to Nvidia's MMA op version 1. This adds bf16-to-f32 conversion ops for XPU target causing compilation failure due to missing conversion patterns.
Supporting such conversion makes the test_masked_load_shared_memory test pass (#279) but DPAS supports BF16 type and we want it to be used in the end. So I propose to remove this pass from our pipeline. It doesn't seem to have anything useful for us (DPAS-related code there doesn't seem to make any transformations). DPAS-specific transformations should be done in a separate XPU-specific pass rather than added to the existing NVVM-specific one.
This PR transforms compilation failure (#158) into runtime failure (incorrect kernel results) and causes no new failures in core tests.

@ienkovich Please investigate the operators/test_matmul.py failures.

As discussed in https://github.com/intel/intel-xpu-backend-for-triton/pull/279, closing this PR.


Add explanation as to if and when it is acceptable to bundle Patient Resources in ITI-65

The MHD Spec is unclear as to whether Submitting DocumentReferences with bundles Patients is allowed.
There is an example showing this, but the verbage is a bit unclear:
"Patient would typically only be allowed by the Document Recipient in PUSH interaction situations, but may be accepted for other reasons at the discretion of the Document Recipient actor policy."
https://profiles.ihe.net/ITI/MHD/ITI-65.html#23654121-bundle-resources
Apparently this refers to "Bundled Patients" but the sentence above is very ambiguous.
Also it is not clear, what constitutes a "PUSH interaction situation" and whether this is within the scope of ITI-65 or not.
see Zulip discussion: https://chat.fhir.org/#narrow/stream/179223-ihe/topic/MHD.20bundled.20vs.2E.20contained.20Patient

Agree wit the need. I welcome recommended text changes to make these points more clear.

do we need to allow for subject.identifier and not subject.reference? such as for regions with a national identifier?


Document file system options-reading behavior of .transform() and options.babelrc

[ ] When babel.transform() is called with an options.filename value that is an absolute pathname, Babel attempts to read options from the file system (.babelrc and presumably package.json).

[x] That behavior can be toggled off with {babelrc: false}. On slack sebmck confirmed the behavior and that the option is public API.

babelrc is documented currently. I'm guessing it must also apply to checking package.json for config too though? That's not documented.


Documenting Fields?

Is there a plan to implement field-level documentation?
It's not super typesafe, but honestly providing a function of String -> Maybe Text that is called with each field inside the GQLType class could work.

if you are using template haskell for gql types then you can document types with gql syntax.
schema.gql
"""
Description for Deity
"""
type Deity {
  """
  Description for name
  """
  name: String!
  power: String @deprecated(reason: "some reason for")
}

another way with just strings is unsafe. but  there is one way that could work.
you could try it with template haskell. i don't know if it works.
idea is to define function that takes template haskell names and converts it to string for introspection.
fieldDescriptions ::  Proxy a -> [(TH.Name,Text)]

{-# LANGUAGE TemplateHaskell   #-}

data Deity = Deity
  { fullName ::  Text
  , power    :: Maybe Text
  } deriving (Generic,GQLType)

instance GQLType Deity where
    fieldDescriptions = [
       ('fullName, "Description for name")
     ]

Using Template Haskell names for labels would work, but I don't think that really gains much safety as there's no association between the label and the parsed type, so it's basically like using a string anyway. I think that it would be okay to be not-as-typesafe because we're just doing documentation, and the only way to do this type-safely is probably some super gross higher-kinded-data thing that would make writing the rest of the application very annoying.

Actually, if type safety is desired, it is probably possible to write something like this with GADTs and what Generic gives you:
data FieldTag (struct :: Type) (tag :: Type) where
  FieldTag :: (HasField field symbol, KnownSymbol field) => Proxy field -> tag -> FieldTag struct field tag
  -- ^ Use something similar to HasField from https://hackage.haskell.org/package/generic-lens-<IP_ADDRESS>/docs/Data-Generics-Product-Fields.html

Then the field names would have type [FieldTag Diety Text] or similar. But this is kinda hard to use, maybe.

as long description is not security relevant. api can be like:
fieldDescriptions ::  Proxy a -> [(Text,Text)]

implemented in: #513
getDescriptions :: f a -> Map Text Description
  getDescriptions _ = mempty

@AnthonySuper please close this. issue if it works for you


[dv/spi_device] Change logic to bit

As mentioned at #1545, clean up logic type as bit is better
Signed-off-by: Weicai Yang<EMAIL_ADDRESS>

Not sure  understand. Why is bit better? I would think logic is better for interface agents.

Not sure I understand. Why is bit better? I would think logic is better for interface agents.

interface is using logic, seq/seq_item is bit, as I don't expect to drive x/z from seq. And x/z is checked in monitor.


Bug fix 3.8/merkle tree bump seq issue

Scope & Purpose
Fix potential issues with revision trees getting out of sync with the underlying collection data.
Add chaos recovery tests

[x] :hankey: Bugfix (requires CHANGELOG entry)
[ ] :pizza: New feature (requires CHANGELOG entry, feature documentation and release notes)
[ ] :fire: Performance improvement
[ ] :hammer: Refactoring/simplification
[x] :book: CHANGELOG entry made

Backports:

[x] No backports required

Testing & Verification

[x] The behavior in this PR was manually tested
[x] This change is already covered by existing tests, such as recovery.
[x] This PR adds tests that were used to verify all changes:

[x] Added new integration tests (recovery)

[ ] http://jenkins01.arangodb.biz:8080/job/arangodb-ANY-matrix/68/
[ ] http://jenkins01.arangodb.biz:8080/job/arangodb-ANY-components-and-drivers/10/


Error Only valid bearer authentication supported, reason: None??

Hey I was getting info about a single track while I got this error
my code is
from spotipy import oauth2,spotify
re=oauth2.SpotifyClientCredentials(client_id=id,client_secret=sec).get_access_token()
spo = Spotify(re)
url = spo.track("https://open.spotify.com/track/3fHNjvF6AU1LXVez0wnFvw")
print(url)

And I am getting following error
HTTP Error for GET to https://api.spotify.com/v1/tracks/3fHNjvF6AU1LXVez0wnFvw returned 400 due to Only valid bearer authentication supported
Traceback (most recent call last):
  File "/home/anishgowda/.local/lib/python3.8/site-packages/spotipy/client.py", line 245, in _internal_call
    response.raise_for_status()
  File "/home/anishgowda/.local/lib/python3.8/site-packages/requests/models.py", line 943, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://api.spotify.com/v1/tracks/3fHNjvF6AU1LXVez0wnFvw

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/anishgowda/.local/lib/python3.8/site-packages/spotipy/client.py", line 339, in track
    return self._get("tracks/" + trid, market=market)
  File "/home/anishgowda/.local/lib/python3.8/site-packages/spotipy/client.py", line 291, in _get
    return self._internal_call("GET", url, payload, kwargs)
  File "/home/anishgowda/.local/lib/python3.8/site-packages/spotipy/client.py", line 261, in _internal_call
    raise SpotifyException(
spotipy.exceptions.SpotifyException: http status: 400, code:-1 - https://api.spotify.com/v1/tracks/3fHNjvF6AU1LXVez0wnFvw:
 Only valid bearer authentication supported, reason: None

Read the documentation: https://spotipy.readthedocs.io/en/2.18.0/#client-credentials-flow

spo = Spotify(auth=re['access_token'])

While this works, it is not recommended because the access token will not be automatically refreshed when it expires after an hour. As shown in the README, this is how you should initialize Spotify:
sp = spotipy.Spotify(auth_manager=SpotifyOAuth(client_id="YOUR_APP_CLIENT_ID",
                                               client_secret="YOUR_APP_CLIENT_SECRET",
                                               redirect_uri="YOUR_APP_REDIRECT_URI",
                                               scope="user-library-read"))

Elements of answer provided here https://github.com/plamere/spotipy/issues/828


[SPARK-34749][SQL] Simplify CreateNamedStruct

What changes were proposed in this pull request?

This is a follow-up of https://github.com/apache/spark/pull/31808 and simplifies its fix to one line (excluding comments).
Why are the changes needed?

code simplification
Does this PR introduce any user-facing change?

no
How was this patch tested?

N/A

cc @dongjoon-hyun @maropu

Test build #136078 has started for PR 31843 at commit 52846d4.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40661/

Test build #136078 has finished for PR 31843 at commit 52846d4.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Could you fix the relevant UT failure?
[info] - dereference *** FAILED *** (335 milliseconds)
[info]   == FAIL: Plans do not match ===
[info]   !'Filter struct(a, 'a, b, 'b)[b]   'Filter named_struct(NamePlaceholder, 'a, NamePlaceholder, 'b)[b]
[info]    +- OneRowRelation                 +- OneRowRelation (PlanTest.scala:161)

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136078/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40683/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136101/

The scala 2.13 failure is unrelated. Can you take another look? @dongjoon-hyun @maropu , thanks!

The scala 2.13 failure is unrelated. Can you take another look? @dongjoon-hyun @maropu , thanks!

https://github.com/apache/spark/pull/31862 seems can fix this.

Thanks! Merged to master.

The commit has a conflict with branch-3.1, so could you open a backport PR for the fix?


[qtbase] framework is only supported on dynamic osx

@autoantwort, thanks for your PR, please get failure logs here.


iphoneX  has default padding when setting top

Issue
after setting top, the page has default padding on iPhoneX. After scrolling, it disappears
Environment
react-native :  0.47.1

Expected
no padding. ScrollView works fine.
Sample

Code
class Test extends React.PureComponent {
    render() {
        return (
            <KeyboardAwareScrollView style={{flex: 1, top: isIphoneX() ? -45 : -20}}>
                <Image
                    resizeMode="contain"
                    source={require('./../../resource/test.png')}
                />
            </KeyboardAwareScrollView>
        )
    }
}

Hack
set automaticallyAdjustContentInsets default true, and after several seconds, reset to false.

Can you try to wrap your component in SafeAreaView?

@alvaromb we were on low version of react-native (0.47.1)～


Add ability to modify browser viewport size - 900x600 is too small for modern UI testing

Which API Provider are you using?
Anthropic
Which Model are you using?
Claude 3.5 Sonnet
What happened?
The browser's viewport is set to 900x600px - a non-standard size that doesn't match real user devices. This causes UI automation tests to interact with elements at incorrect positions, as the layout differs significantly from what real users see.
Expected behavior: Elements should be positioned where actual users would find them (using standard desktop resolution of 1280px+ width).
Actual behavior: With 900x600px viewport, elements are rendered in different positions due to responsive design adjustments, making automated UI testing unreliable.
https://github.com/cline/cline/blob/0d256239f37a556ec7230da4e4f217c2c90dcd3c/src/services/browser/BrowserSession.ts#L61-L64
Steps to reproduce

Launch browser using computer use

Relevant API REQUEST output
No response
Additional context
No response

and to add to the issue, it also often does not see things that would be in the interface when viewed on a more modern resolution as it is just outside of the frame, leading to many false positives when debugging.

Thank you for opening the ticket, browser configurations are coming including viewport size

Any updated on this? Just can't wait! Thanks for all the effort! :)

Any updates ?


tf.io.decode_image(img, channels=3) outputs 4 channels when reading 4-channel BMP

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution: Windows 10
TensorFlow installed from (source or binary): binary (pip)
TensorFlow version: 2.2.0
Python version: 3.7.7

Describe the current behavior
When reading in a 4-channel BMP:

tf.io.decode_image(img, channels=3) gives shape (..., ..., 4) instead of (..., ..., 3)
tf.io.decode_bmp(img, channels=3) gives the following error

Traceback (most recent call last):
  File "channels.py", line 44, in <module>
    loop()
  File "channels.py", line 14, in loop
    img = tf.io.decode_bmp(img, channels=3)
  File "C:\Users\mattchee\Miniconda3\lib\site-packages\tensorflow\python\ops\gen_image_ops.py", line 899, in decode_bmp
    _ops.raise_from_not_ok_status(e, name)
  File "C:\Users\mattchee\Miniconda3\lib\site-packages\tensorflow\python\framework\ops.py", line 6653, in raise_from_not_ok_status
    six.raise_from(core._status_to_exception(e.code, message), None)
  File "<string>", line 3, in raise_from
tensorflow.python.framework.errors_impl.InvalidArgumentError: channels attribute 3 does not match bits per pixel from file 4 [Op:DecodeBmp]

I'm following this guide to load images efficiently so tf.keras.preprocessing.image.load_img(img_path, color_mode="rgb") is not an option.
Describe the expected behavior
This is inconsistent with tf.io.decode_image(img, channels=3) and tf.io.decode_png(img, channels=3) which give shape (..., ..., 3) when reading a 4-channel PNG.
Both tf.io.decode_image(img, channels=3) and tf.io.decode_bmp(img, channels=3) would be expected to give shape (..., ..., 3) when reading in a 4-channel BMP.
Standalone code to reproduce the issue
img = tf.io.read_file(img_path)
img = tf.io.decode_bmp(img, channels=3)
print(img.shape) # This prints (1080, 1920, 4)

@mchanchee Can you share a sample bmp file to reproduce the issue?

Can you also test with tf-nightly. There has been a refactoring of tf.io.decode_image recently which I think covers this issue too.

Thank you for reporting the issue. It appears to be an inherent issue with decode_bmp op. I will look into it and loop back with updates.

@yongtang @hyeygit Thank you for looking into it. I've added a sample BMP file to the issue description

I've tried it with tf-nightly 2.4.0-dev20200708 and it's all good.
Thank you very much for fixing the issue!

Again, thank you for reporting, also for confirming that the issue is fixed!


[FEATURE]: Add moderation status to profile page

Feature for…
Frontend
What is the problem you want to solve?
As a user I'd like to know my moderation status, so that I can understand what capabilities I have access to on the site.
How do you want to solve the problem?

I propose to solve the problem by adding a read-only field to the profile which indicates whether the the user has moderator rights or not (in case the use doesn't the field can be hidden).
Alternatives include:

Not adding anything: it's already obliquely clear from the existence of the 'Moderator' menu item that the user is a moderator.
Adding a section for 'badges'. It could be quite cool to have badges for things like 'author' (after posting a story), 'moderator', 'profile complete'. But these could also be seen as manipulative.
Adding an enrolment process for moderators. This could be useful in other ways, and maybe makes highlighting moderator status more redundant.

I propose simply adding a field to the profile, as it's a relatively straightforward change that can be iterated on later.

Other comments
No response

Would it make sense therefore to close this issue, given there are higher priority tasks, and at any rate it might make more sense to wait until/if it fits into something broader (e.g. badges for other reasons)?

Yeah, let's do that! 👍


fs: fs_open will only copy flags into fs_file_t structure on success

The fs_open copies open flags into fs_file_t structure for use with
other VFS API calls; the commit moves the operation into success path.
Signed-off-by: Dominik Ermel<EMAIL_ADDRESS>

@de-nordic, what is the reason for this change ? Couldn't there be a failure that does need to set the flags ?

@de-nordic, what is the reason for this change ? Couldn't there be a failure that does need to set the flags ?

Generally it is better to avoid changing objects given as argument to a function on error paths, when possible.
In this case, because the check for zdp being already used happens later in code, the failed fs_open will be changing flags for already opened file.

@de-nordic, what is the reason for this change ? Couldn't there be a failure that does need to set the flags ?

Generally it is better to avoid changing objects given as argument to a function on error paths, when possible. In this case, because the check for ~zdp~ zfp being already used happens later in code, the failed fs_open will be changing flags for already opened file.

In general I agree that it is better to avoid changing objects as arguments to a function on error paths.
But maybe in this case it is done intentionally, suppose a file is opened as rw, do some change and then keep the location and modify the file to ro. With the current implementation,  reopen the file with the new flag and ignore a "already open" error. With the new implementation it would be required to close the file, and reopen as ro and search for the correct position to continue.

But maybe in this case it is done intentionally, suppose a file is opened as rw, do some change and then keep the location and modify the file to ro. With the current implementation, reopen the file with the new flag and ignore a "already open" error. With the new implementation it would be required to close the file, and reopen as ro and search for the correct position to continue.

No, it is not expected to call fs_open() on same file object without initializing the object to blank state in between. see https://docs.zephyrproject.org/latest/reference/file_system/index.html?highlight=fs_open#c.fs_file_t_init

But maybe in this case it is done intentionally, suppose a file is opened as rw, do some change and then keep the location and modify the file to ro. With the current implementation, reopen the file with the new flag and ignore a "already open" error. With the new implementation it would be required to close the file, and reopen as ro and search for the correct position to continue.

Unfortunately here it was, undocumented and unintended, side-effect.

But maybe in this case it is done intentionally, suppose a file is opened as rw, do some change and then keep the location and modify the file to ro. With the current implementation, reopen the file with the new flag and ignore a "already open" error. With the new implementation it would be required to close the file, and reopen as ro and search for the correct position to continue.

No, it is not expected to call fs_open() on same file object without initializing the object to blank state in between. see https://docs.zephyrproject.org/latest/reference/file_system/index.html?highlight=fs_open#c.fs_file_t_init

Exactly where does it say that it is not expected to do this. My example above is a perfectly valid case where the open would return -EBUSY but the flag would be changed.

Exactly where does it say that it is not expected to do this. My example above is a perfectly valid case where the open would return -EBUSY but the flag would be changed.

You are elevating my programmer's error (committed here cac07629bfcd8fc2105da9a739118361e9ff630b) into a feature. It was never my intention to allow fs_open to allow to change flags on open file.
I do not think that successful operation should be followed with error code, and in case of changing flags that would be the case.
The change of flags happens on VFS level only and is not passed down to a driver level, which may require re-opening the file to change flags internally, so the change in open flags is superficial only and may lead to driver errors from succeeding calls.

You are elevating my programmer's error (committed here cac0762) into a feature. It was never my intention to allow fs_open to allow to change flags on open file. I do not think that successful operation should be followed with error code, and in case of changing flags that would be the case. The change of flags happens on VFS level only and is not passed down to a driver level, which may require re-opening the file to change flags internally, so the change in open flags is superficial only and may lead to driver errors from succeeding calls.

I had no intend to do this, but after going through the code again, I'm really wondering if it is necessary (and wanted) to create the flags "state" at the vfs level. This state only creates difficulties and might lead to mismatch between vfs level and driver level. I think this introduces unnecessary doubles checks on the vfs level and the driver level.

You are elevating my programmer's error (committed here cac0762) into a feature. It was never my intention to allow fs_open to allow to change flags on open file. I do not think that successful operation should be followed with error code, and in case of changing flags that would be the case. The change of flags happens on VFS level only and is not passed down to a driver level, which may require re-opening the file to change flags internally, so the change in open flags is superficial only and may lead to driver errors from succeeding calls.

I had no intend to do this, but after going through the code again, I'm really wondering if it is necessary (and wanted) to create the flags "state" at the vfs level. This state only creates difficulties and might lead to mismatch between vfs level and driver level. I think this introduces unnecessary doubles checks on the vfs level and the driver level.

I might've been too quick merging here @Laczen, sorry. If this is indeed a mistake we can revert it.


feat: PLS-431

Details

Updated dependencies
Used seal-node:oss-module-update

Breaking Changes
References
https://jira.sealsystems.de/jira/browse/PLS-431
Introduction to Pull Requests

Please read before submitting your first pull request!

Thank you for creating a pull request. We really appreciate your effort!
Here is some information to help you integrate your changes as easily as possible into the next release.
Title Field
The title is one of the most important aspects of a pull request. The content is shown in CHANGELOG.md and release notes. Therefore, be sure to summarize your changes in a short but catchy sentence. Others should be able to easily get an idea of your changes.
By adding keywords at the beginning of the title, you can control the process of merging and releasing your pull request. Here is the list of all available keywords:

WIP:
It is highly recommended to open a pull request as soon as possible. This allows discussions during code development and not just criticism after work is done.
Please start a new pull request with the prefix WIP:. This signals to others that is is not yet ready to be merged into the master branch. It also prevents our bot from merging. (See section "Merging into Master" below)
After the changes and the pull request description have been completed, remove this prefix. In this case, review requests may be automatically generated to ensure, e.g., the compatibility of your description with our release notes format.

feat:
A pull request with this prefix in its title is marked as a new feature. In general this creates a minor release when merging the pull request into the master branch. A label with the expected release type is added to the pull request.

fix:
A pull request with this prefix in its title is marked as a bugfix. In general this creates a patch release when merging the pull request into the master branch. A label with the expected release type is added to the pull request.

chore:
A pull request with this prefix in its title is marked as a maintenance change. In general this creates a patch release when merging the pull request into the master branch. A label with the expected release type is added to the pull request. Only CHANGELOG.md, but not our release notes, will be updated with information about the pull request.

You can specify the kind of pull request when you create a new one. But do not forget to prefix it with WIP:. Here is an example title for such a pull request:
WIP: feat: My super cool new feature

After finishing the work, you can simply remove WIP:.
Please do not format the Title field with Markdown.
Description Field
Besides this introduction, the description field also contains sections with the following headings which contribute to CHANGELOG.md and release notes:

Details
Sometimes it is not possible to explain a change with a single short line in the Title field. In this case, you can add a more detailed description in the Details section.
You may add several paragraphs if needed and unlike the Title field, you can format the content with Markdown.

Breaking Changes
Please fill out this section if and only if your changes affect the public Interface. This creates a major release when merging the pull request into the master branch. Breaking changes are shown in an additional section of CHANGELOG.md and release notes. So two headings will be created: One for the bugfix/feature itself and one for the breaking changes.
All information for the Details section also applies here, with one important exception:
In contrast to the Details section, the first line is used as a title for the breaking change. Therefore, please add a short description first and append paragraphs for more information if needed. Do not start with a large paragraph and do not format the first line.
Here is an example of a longer text for a breaking change:

This is a brief description of the breaking change (without a punctuation mark and formatting)
In another paragraph, I add detailed information of steps needed to adapt to the new interface. I can also format this paragraph using Markdown.
I can add as many paragraphs as needed.

The first line is shown as a heading and the following paragraphs as normal text.
Use this section only to describe the changes to the interface and how to adapt to the new version. Use the Details section to provide information about the bugfix/feature itself.

References
Here you can enter links to Jira oder Github. This allows you to provide more information about the background of your code changes.
Add one link per line without any other text.

Please make sure that you leave a blank line between the headings and the beginning and end of your text.
Merging into Master
After all reviews have been successfully completed, you are ready to merge your pull request into the master branch. This is only possible if all required automated tests pass.
You cannot use the green "Merge" button. Instead you must add a special comment containing only the following command:
/merge

This causes our merge bot to merge the pull request using a commit message consisting of the various pieces of information in the Title and Description fields.
The branch is automatically deleted after a successful merge. If you do not have permissions to commit to the repository, a comment containing an error message is created.

/merge

:tada: This PR is included in version 2.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[MINT-3000] Model Plan Automatic Status Email Notification

MINT-3000
Description

[!NOTE]
Though the ticket for MINT-3000 includes both email notification and Faktory job, as backend engineers we have decided to split this work up so that @StevenWadeOddball will be doing the Faktory job component separately while I capture the email template in this PR.

Email template implementation
Wiring to integrate the new model plan suggested phase template into the template service
Added tests for the new email template

How to test this change

Run scripts/dev email
Validate the corresponding emails received on mailcatcher at localhost:1085

PR Author Checklist

[x] I have provided a detailed description of the changes in this PR.
[x] I have provided clear instructions on how to test the changes in this PR.
[x] I have updated tests or written new tests as appropriate in this PR.
[x] Updated the Postman Collection if necessary.

PR Reviewer Guidelines

It's best to pull the branch locally and test it, rather than just looking at the code online!
When approving a PR, provide a reason why you're approving it

e.g. "Approving because I tested it locally and all functionality works as expected"
e.g. "Approving because the change is simple and matches the Figma design"

Don't be afraid to leave comments or ask questions, especially if you don't understand why something was done! (This is often a great time to suggest code comments or documentation updates)
Check that all code is adequately covered by tests - if it isn't feel free to suggest the addition of tests.

Thanks @OddTomBrooks, can you target the feature branch instead of main please? feature/MINT-1905_notification_to_model_leads_to_update_status.  Note, the scope of the faktory PR is just the boiler plate faktory logic (running cron job, making batch job and standard jobs). Once merged, it will be ready for you to implement the business logic of determining if an email should be checked, and to send an email or not.

@OddTomBrooks , this should target feature/MINT-1905_notification_to_model_leads_to_update_status now right? The other branch is for the modal on the front end right?

@OddTomBrooks , there are a couple things left to address, but they can be accomplished in a future PR since this has been merged.


Advert Rotator

Changes

The sidebar ad is now a partial partials/support-ad.html
Content for the ad is stored in a JS array of objects located in static/js/docs-interactions.js
Ad content is injected at page ready, and is randomized between the two ads
Aesthetic of ads designed to match the ones I designed for the new website
The mask that appears on mobile devices when you open the sidebar now has a gradient that matches its product

Preview:

Ads for new website, for comparison

LGTM!  @kostasb, are they any build-related issues that could come up?

@rkuchan It is live now and looks good.


Add useful mint data

Description

Add items remaining / items available info.
Add price (in SOL) to "Mint" button.
Ignoring IDE data folder.

Before:

After:

Type of change

[x] New feature

How Has This Been Tested?

[x] Developer Tools

Built and ran using yarn start.

Similar functionality has been merged, so I'm going to close this. One thing that users need to be aware of is this information requires RPC calls which aren't alway reliable during a heavy mint. Also worth knowing this reflects just one browsers view, not global state (ie other people minting doesn't affect the counts you're looking at)


Disable Requestlogs

HI!,
anybody can tell me how can I disable the API request logs?

I'd accept a PR on this. I don't have time to code this at the moment.

@YeraDR Can't you just ignore AuditPolicy and not use it at all? Isn't that the one which creates requestlogs?


Is the previous version still available?

I preferred the previous version of Scale Workshop as I could get a really good delay effect and was more used to the interface.  Thank you.

Yes: https://sevish.com/scaleworkshop1/

That's great - many thanks!

Leaving this issue open for now. Might add a link to version 1 in the app directly later.


Cannot read property 'replace' of undefined.

[Angular 7]
Anyone having same issue?

Hello,
I have exactly the same error this one occurred after mid my navbar outside the router-outlet.
But I do not know how to solve it: /

@mateuszbem @Vincent-Valembois can you please include example code with steps to reproduce this issue, thanks

Same issue here, I have the  and  on different components


Allow writeConnectionSecretToRef to be compatible with SQL community provider

What problem are you facing?
Using the community provider for SQL can't connect to the cluster created if we reference the secrets generated by writeConnectionSecretToRef to the provider because it will search for password and username instead of master_username and attribute.master_password (as is required in their doc) so it requires so manual action modifying the secret and can't be solved in a GitOps way.
How the secrets should be stored:
apiVersion: v1
kind: Secret
data:
  endpoint: xxxxxx
  password: xxxxxx
  port: xxxxxx
  readerEndpoint: xxxxxx
  username: xxxxxx

How are the secrets stored:
apiVersion: v1
kind: Secret
data:
  endpoint: xxxxxx
  attribute.master_password: xxxxxx
  port: xxxxxx
  readerEndpoint: xxxxxx
  master_username: xxxxxx

How could Official AWS Provider help solve your problem?
Enabling a feature to allow configuring how that secret or parameters should be stored, thus allowing the choice to save the connection with a username and password to be compatible with the community SQL provider like other community providers do.

Hi @Keralin,
I'm a little skeptical about this issue, changing these fields will cause breaking API changes. It seems more logical to fix this on the provider-sql side.

@turkenf I think the issue here is that an RDS Cluster resource does not publish the connection details using the keys expected by other components https://github.com/crossplane/crossplane-runtime/blob/master/apis/common/v1/resource.go#L25-L44
I guess it would be possible to keep publishing the current custom_ fields (like master_password), but to publish also the standard ones. Is that an option?

Related: #778

/fresh

/fresh

FYI https://github.com/crossplane-contrib/provider-upjet-aws/issues/1578


Feature/Fluent ToolTip

What does the pull request do?

Also added:

New pseudo class ToolTip :open
SetWindowManagerAddShadowHint(false) is now called on tooltip, so it could be with transparent borders on Win32.

Still missed:

Opacity transition doesn't work on ToolTip closing, because we don't wait for animation before we call .Close(). Fixing this issue will affect default style. I will add it to https://github.com/AvaloniaUI/Avalonia/issues/4039
There is no ToolTip shadow, seems like it should be implemented with BoxShadow. But all another popups should also support it for consistency. I will add it to https://github.com/AvaloniaUI/Avalonia/issues/4039

Fixed issues
Part of https://github.com/AvaloniaUI/Avalonia/issues/3950

I also added some tests for ":open" just for case


Set the flush threshold on a per-segment basis

Set the LLC realtime segment flush threshold on a per-segment basis
according to the maximum number of partitions consumed by replicas. For
example, if some replicas for a new segment are consuming three
partitions and some are consuming four, the new segment will have a
flush threshold equal to the per-table row flush threshold divided by
four.
This ensures that even if the number of Kafka partitions increases,
there is still an upper bound on the number of rows held in memory
before being flushed to disk.

Current coverage is 64.29% (diff: 98.14%)

Merging #893 into master will increase coverage by 0.11%

@@             master       #893   diff @@
==========================================
  Files           731        731
  Lines         34585      34658    +73
  Methods           0          0
  Messages          0          0
  Branches       5291       5302    +11
==========================================
+ Hits          22199      22284    +85
+ Misses        10816      10808     -8
+ Partials       1570       1566     -4

Powered by Codecov. Last update 72bfca4...9f3ed17


Error: Failed to parse selector: .layout-2/24

I am trying to find a component with class .layout-2/24 but I get an error:
Error: Failed to parse selector: .layout-2/24

The error seems to revolve around the \
Escaping it does not seem to fix the issue either, eg: .layout-2\/24
Any idea how to fix this please?

Is that actually a valid class name?

I believe so, yes
Currently, it does not allow for a / anywhere within the class name

/ is not a valid character in a CSS class name.
The grammar is shown here: https://www.w3.org/TR/CSS22/grammar.html#scanner
The grammar says a css class is:

a dot
followed by IDENT

An IDENT is:

One to many of:

a-z, or
A-Z, or
0-9, or
_, or
-, or
a unicode escape sequence (eg \FF), or
any non-hex character that is escaped (eg \x), or
any character above octal 240 (0xA0 in hex)

But the first character must not be 0-9

And so:
/ is not one of the explicitly allowed characters, and has the hex value 0x2F - 0x2F is less than 0xA0. So is not allowed, according to the spec.
That said, escaping it as .layout-2\/24 would be allowed by the grammar. But that would need to be on both sides (as the class in rendered output, and in the selector passed to .find()) - enzyme expects the classes to match naïvely, so it would not return the element/component with one side escaped and the other unescaped, because as far as it is concerned, foo and f\oo are different.
But. The code that throws the underlying error is in rst-selector-parser (which was created for enzyme). The regex in rst-selector-parser does not handle escapes at all. So that is the place that needs updating to handle escaped characters, if the Enzyme team decides to support this use case.

In that case, an issue should be filed there, and this can be closed. Thanks for the legwork!


help with redirect

hello
trying to follow yr setup but I got stuck here:
https://accounts.spotify.com/authorize?client_id={CLIENTID}&response_type=code&scope=user-read-currently-playing,user-read-recently-played&redirect_uri=http://localhost/callback/
After login it always gives me
INVALID_CLIENT: Invalid client
Any idea?

my bad sorry, a typo :/


CSmartTable doesn't rerender table after updating items

Windows 10 21H1
Chrome 104
Problem:
After updating items, table rendering items by LIFO principle.
If on the start we have 2 rows, after adding another one - there is still 2 rows, but content of the rows was changed
After refresh will rendered all rows
First condition:

Row was added and change first in the list

After refresh

actual


Discord messages not correctly formatted/delivered

What did you do?

Set up kube-stack on a k8s cluster (Alertmanager deployed via Prometheus Operator)
Configured Alertmanager for discord notifications following the official blog article guide

What did you expect to see?
Discord notifications correctly delivered
What did you see instead? Under which circumstances?
Alertmanager cannot deliver the message, prints the error log:
ts=2023-10-30T16:27:09.440Z caller=dispatch.go:352 level=error component=dispatcher msg="Notify for alerts failed" num_alerts=4 err="discord/discord[0]: notify retry canceled due to unrecoverable error after 1 attempts: unexpected status code 400: {\"embeds\": [\"0\"]}"

Such response from Discord means that some Embeds are bad configured, so I guess the JSON payload created is not well formatted. Couldn't find a way to debug the created payload (via logLevel=debug)
Here's the simple alert I'm testing which always trigger the alert (as stated via the UI too):
- alert: TestAlert
  expr: |
    test_metrics_count > 1
  for: 1m
  labels:
    severity: critical
  annotations:
    title: "Test Alert"
    description: "Test Alert"

Environment

System information:
Linux 5.15.117 x86_64

Alertmanager version:

alertmanager, version 0.26.0 (branch: HEAD, revision: d7b4f0c7322e7151d6e3b1e31cbc15361e295d8d)
  build user:       root@df8d7debeef4
  build date:       20230824-11:11:58
  go version:       go1.20.7
  platform:         linux/amd64
  tags:             netgo

Prometheus version:

prometheus, version 2.47.1 (branch: HEAD, revision: c4d1a8beff37cc004f1dc4ab9d2e73193f51aaeb)
  build user:       root@4829330363be
  build date:       20231004-10:31:16
  go version:       go1.21.1
  platform:         linux/amd64
  tags:             netgo,builtinassets,stringlabels

Alertmanager configuration file:

global:
  resolve_timeout: 5m
inhibit_rules:
- equal:
  - namespace
  - alertname
  source_matchers:
  - severity = critical
  target_matchers:
  - severity =~ warning|info
- equal:
  - namespace
  - alertname
  source_matchers:
  - severity = warning
  target_matchers:
  - severity = info
- equal:
  - namespace
  source_matchers:
  - alertname = InfoInhibitor
  target_matchers:
  - severity = info
receivers:
- name: "null"
- discord_configs:
  - send_resolved: true
    webhook_url: https://discord.com/api/webhooks/.../...
  name: discord
route:
  group_by:
  - alertname
  - job
  group_interval: 5m
  group_wait: 30s
  receiver: discord
  repeat_interval: 12h
  routes:
  - matchers:
    - alertname =~ "InfoInhibitor|Watchdog"
    receiver: "null"
  - matchers:
    - severity =~ "critical|error|warning|info"
    receiver: discord
templates:
- /etc/alertmanager/config/*.tmpl

Prometheus configuration file:
Not relevant

Logs:

ts=2023-10-30T16:27:09.440Z caller=dispatch.go:352 level=error component=dispatcher msg="Notify for alerts failed" num_alerts=4 err="discord/discord[0]: notify retry canceled due to unrecoverable error after 1 attempts: unexpected status code 400: {\"embeds\": [\"0\"]}"

According to this that Discord error message pops up on a various type of format errors, the most frequent one is an empty embed field. I am now trying to do a bit of reverse engineering and modifying a the template to see if that's the case

After some changes in the template, I was able to make it works, so I can confirm it's due to some empty fields in the embeds
title: >-
  [{{ .Status | toUpper }}
  {{ if eq .Status "firing" }}: {{ .Alerts.Firing | len }}{{ end }}]
  {{ with (index .GroupLabels.SortedPairs.Values 0) }}
  {{ . }}
  {{ end }}
message: |-
  {{ if and .Alerts.Firing (gt (len .Alerts.Firing) 0) }}
  {{- range .Alerts.Firing }}
  {{- if gt (len .Annotations) 0 }}
  {{ range .Annotations.SortedPairs }}
  - {{ .Name }}: {{ .Value }}
  {{- end }}
  {{- else }}
  (No Annotations)
  {{- end }}
  {{- end }}
  {{- end }}

Obviously this is a slim version (I don't need all of the infos) but my suggestion was to check for the fields in the code and not in the template and maybe add a default string - for missing values

After some changes in the template, I was able to make it works, so I can confirm it's due to some empty fields in the embeds
title: >-
  [{{ .Status | toUpper }}
  {{ if eq .Status "firing" }}: {{ .Alerts.Firing | len }}{{ end }}]
  {{ with (index .GroupLabels.SortedPairs.Values 0) }}
  {{ . }}
  {{ end }}
message: |-
  {{ if and .Alerts.Firing (gt (len .Alerts.Firing) 0) }}
  {{- range .Alerts.Firing }}
  {{- if gt (len .Annotations) 0 }}
  {{ range .Annotations.SortedPairs }}
  - {{ .Name }}: {{ .Value }}
  {{- end }}
  {{- else }}
  (No Annotations)
  {{- end }}
  {{- end }}
  {{- end }}

Obviously this is a slim version (I don't need all of the infos) but my suggestion was to check for the fields in the code and not in the template and maybe add a default string - for missing values

@dnnnvx Where should I put the settings to use with discord?

@dnnnvx Where should I put the settings to use with discord?

(Note that I'm using the kube-prom-stack chart) in the alertmanager values you need to add a discord receiver (I ended up using the slack title/text templates):
alertmanager:
  ...
  receivers:
    ...
    - name: discord
      discord_configs:
        - webhook_url: "https://discord.com/api/webhooks/..."
          send_resolved: true
          title: '{{ template "slack.title" . }}'
          message: '{{ template "slack.text" . }}'

I ran into the same issue, and I think it is related to missingkey=zero option in the template parser.
So each field should be tested before being used.

Duplicate of #3310 and fixed by #3597? Currently unreleased, though.

Duplicate of #3310 and fixed by #3597? Currently unreleased, though.

I don't think it's the same, #3310 is about limits, here's the issue is about missing proper fields checks, so each field needs to be manually checked (while that's not the case with, for example, Slack)

My understanding is the error message is identical.
ts=2023-10-30T16:27:09.440Z caller=dispatch.go:352 level=error component=dispatcher msg="Notify for alerts failed" num_alerts=4 err="discord/discord[0]: notify retry canceled due to unrecoverable error after 1 attempts: unexpected status code 400: {\"embeds\": [\"0\"]}"

How can we be sure it's not the same? I recognise there has been some triaging here, and changing the template has worked for you. It does confuse me however, as the actual Discord integration works okay.
Could you verify you can still reproduce the issue with quay.io/prometheus/alertmanager:main@sha256:889198464d4f78f7b0781d5ab76fa7c97a054dc3ba0f00395b1a4efdb9f7edd4?
https://quay.io/repository/prometheus/alertmanager/manifest/sha256:889198464d4f78f7b0781d5ab76fa7c97a054dc3ba0f00395b1a4efdb9f7edd4

Sorry @uhthomas you're right, I was looking at the wrong log- I deployed alertmanager in my cluster with that SHA and it seems to work fine, no error for now. The error I found (the reason of this PR) was not for each alert, so I'll continue to keep an eye on it. For now, seems to be solved with that version!

Received 2 new errors tonight and both were displayed successfully, so I think it can be market as a duplicate. Thanks again!

Duplicate of https://github.com/prometheus/alertmanager/issues/3310 and fixed by https://github.com/prometheus/alertmanager/pull/3597


Duplo 26030 Ingress host property of rules can't be removed in Terraform

Overview
Host field in rule block of duplocloud_k8_ingress doesnt show diff on change
Summary of changes
Fixed non removal of host field in rule block of ingress resource
This PR does the following:

Removed compute attribute fro host field of duplocloud_k8_ingress resource
...

Testing performed

[ ] Using unit tests
[ ] Manually, on my local system
[ ✔] Manually, on a remote test system

Describe any breaking changes

...

Task linked: DUPLO-26030 Ingress host property of rules can't be removed in Terraform


fix: revert CPK has-one associatedFields

Issue #

Description

We recently added this change https://github.com/aws-amplify/amplify-swift/pull/2734 expecting codegen to generate  has-one with associatedFields in https://github.com/aws-amplify/amplify-codegen/pull/541. We were working through some implementation details in https://github.com/aws-amplify/amplify-swift/pull/2737 that no longer depends on has-one to have associatedFields. This change is to revert it until we identify an actual need to move forward with the codegen changes.
General Checklist

[ ] Added new tests to cover change, if needed
[ ] Build succeeds with all target using Swift Package Manager
[ ] All unit tests pass
[ ] All integration tests pass
[ ] Security oriented best practices and standards are followed (e.g. using input sanitization, principle of least privilege, etc)
[ ] Documentation update for the change if required
[ ] PR title conforms to conventional commit style
[ ] New or updated tests include Given When Then inline code documentation and are named accordingly testThing_condition_expectation()
[ ] If breaking change, documentation/changelog update with migration instructions

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #2750 (51b3e10) into v1 (9ce0c58) will decrease coverage by 6.48%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##               v1    #2750      +/-   ##
==========================================
- Coverage   64.37%   57.90%   -6.48%
==========================================
  Files         720      627      -93
  Lines       22742    16615    -6127
==========================================
- Hits        14641     9621    -5020
+ Misses       8101     6994    -1107

Flag
Coverage Δ

API_plugin_unit_test
66.78% <ø> (ø)

AWSPluginsCore
73.34% <100.00%> (ø)

Amplify
51.31% <100.00%> (+0.04%)
:arrow_up:

Analytics_plugin_unit_test
72.43% <ø> (ø)

Auth_plugin_unit_test
83.80% <ø> (ø)

DataStore_plugin_unit_test
?

Geo_plugin_unit_test
57.87% <ø> (ø)

Predictions_plugin_unit_test
33.61% <ø> (ø)

Storage_plugin_unit_test
59.55% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...Model/Internal/Schema/ModelSchema+Definition.swift
58.82% <ø> (+2.92%)
:arrow_up:

...Model/Internal/Schema/ModelField+Association.swift
45.83% <100.00%> (-1.11%)
:arrow_down:

...e/AWSPluginsCore/Model/Support/Model+GraphQL.swift
74.80% <100.00%> (ø)

...insCore/Model/Support/QueryPredicate+GraphQL.swift
74.63% <100.00%> (ø)

Amplify/Categories/Hub/HubFilter.swift
52.63% <0.00%> (-5.27%)
:arrow_down:

...s/AWSHubPlugin/Internal/HubChannelDispatcher.swift
94.11% <0.00%> (-2.95%)
:arrow_down:

...goryPlugin/Storage/SQLite/ModelSchema+SQLite.swift

...SMutationDatabaseAdapter+MutationEventSource.swift

...eCategoryPlugin/Storage/StorageEngineAdapter.swift

...ategoryPlugin/Storage/SQLite/Statement+Model.swift

... and 90 more

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


Changelog doesn't include notes for 1.7.4

Even a simple statement like "this is a bugfix release, and nothing should have broken" helps. (Yes, I understand that semver says effectively the same thing. Still, I appreciate the reassurance, and I don't know for sure that this project uses semver.)

Yes sorry I forgot to add the changelog item for 1.7.4.
Should be in the repository now.

Thank you!


Display Carto icon gallery in Storybook

Story: https://app.shortcut.com/cartoteam/story/302497/tooling-display-carto-icon-gallery-in-storybook
Autolink: [sc-302497]

Useful to see the available icons (avoid duplicities when you add a new one) and reveal SvgIcon component options.

@zbigg I did also the migration to styled in the new story file...
My idea indeed is to have some shared styled components for Storybook because, in most of the files, I ended up using the same set of them. I'll progressively migrate all makeStyles in stories in the same way.
Thanks for your review!


TEST: RAW.py data (000)

A buffer has been added  and  also an index has been added.
To be tested:
1. Check if any double chunk are printed in the terminal.
2. Check if the index has been displayed inside the terminal.

Everything tested. Another bug found when using the hard restart button. It seems like when doing that the buffer is not clear completely. Solved by using the buffer clear in the lost connection error


Error when running truffle unbox optimism

Hi, could you please point out if this is my misunderstanding or if something is causing this issue on your side?
Attaching the error message.
$ truffle unbox optimism
This directory is non-empty...
? Proceed anyway? (Y/n)
Starting unbox...
=================

? Proceed anyway? Yes
✓ Preparing to download box
✓ Downloading
npm ERR! code ERR_INVALID_ARG_TYPE
npm ERR! The "from" argument must be of type string. Received undefined

npm ERR!
Error: Command failed: npm install --loglevel=error && touch .env
npm ERR! code ERR_INVALID_ARG_TYPE
npm ERR! The "from" argument must be of type string. Received undefined

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/eli/.npm/_logs/2022-05-23T20_37_05_269Z-debug-0.log

    at checkExecSyncError (node:child_process:828:11)
    at Object.execSync (node:child_process:899:15)
    at Object.installBoxDependencies (/usr/local/lib/node_modules/truffle/build/webpack:/packages/box/dist/lib/utils/unbox.js:139:1)
    at Object.setUpBox (/usr/local/lib/node_modules/truffle/build/webpack:/packages/box/dist/lib/utils/index.js:52:1)
    at /usr/local/lib/node_modules/truffle/build/webpack:/packages/box/dist/box.js:183:1
    at Generator.next (<anonymous>)
    at fulfilled (/usr/local/lib/node_modules/truffle/build/webpack:/packages/box/dist/box.js:5:43)
Truffle v5.5.15 (core: 5.5.15)
Node v16.15.0

Hi @timofeli thanks for reaching out! I see in your output that you are unboxing into a non-empty directory. When I attempt the command in an empty directory everything appears to work as expected. Can you try this in an empty directory and let me know if it works? Thanks!

@fainashalts Thank you for your prompt reply!
I just did it and had the same error.
`eli@eli-XPS-13-9360:~/test2$  truffle unbox optimism
Starting unbox...
✓ Preparing to download box
✓ Downloading
npm ERR! code ERR_INVALID_ARG_TYPE
npm ERR! The "from" argument must be of type string. Received undefined
npm ERR!
Error: Command failed: npm install --loglevel=error && touch .env
npm ERR! code ERR_INVALID_ARG_TYPE
npm ERR! The "from" argument must be of type string. Received undefined
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/eli/.npm/_logs/2022-05-24T06_30_31_985Z-debug-0.log
at checkExecSyncError (node:child_process:828:11)
at Object.execSync (node:child_process:899:15)
at Object.installBoxDependencies (/usr/local/lib/node_modules/truffle/build/webpack:/packages/box/dist/lib/utils/unbox.js:139:1)
at Object.setUpBox (/usr/local/lib/node_modules/truffle/build/webpack:/packages/box/dist/lib/utils/index.js:52:1)
at /usr/local/lib/node_modules/truffle/build/webpack:/packages/box/dist/box.js:183:1
at Generator.next (<anonymous>)
at fulfilled (/usr/local/lib/node_modules/truffle/build/webpack:/packages/box/dist/box.js:5:43)

Truffle v5.5.15 (core: 5.5.15)
Node v16.15.0
`

Seems to be an issue with the version of node and changes between major versions.  I received same error as @timofeli when using node v17.4.0. Seems they are using 16.15.0 when testing above. When downgrading to a lower version of node 12.22.12 the unbox worked successfully.  I removed the node_modules directory from this repo to allow the post install script to execute and it seems to work as intended.  Here is open PR with the change to fix this issue: https://github.com/truffle-box/optimism-box/pull/25

@timofeli your issue should now be resolved as https://github.com/truffle-box/optimism-box/pull/26 is merged with the fix.

Hello @timofeli so sorry I lost track of this. Looks like @beakerfm was able to help get this resolved. I'm going to close this issue but please feel free to open a fresh one if you encounter any other issues! Thanks!


Hooks layout & scaffolding

Fix https://github.com/konveyor/forklift-ui/issues/571

@vconzola, please review. All screens are availlable with Surge preview of this PR but the empty hook for HooksPage which I added to this PR's description.

@gildub The only things I see concern the create hook button. The label should just be "Create" (context is obvious from the page title), and it's not vertically aligned with the filter and pagination controls. Otherwise, LGTM.

@gildub Yeah, sorry about that - my mistake. The button label should stay as "Create hook" on the empty state page, but change to "Create" above the table.

@vconzola our other pages have that button with the resource type in it ("create plan/mapping" and "add provider"). Should we change those too?

SoB. I don't know why I did that. It's easier to make hooks be consistent than to change a bunch of other stuff. So let's keep the button text as "Create hook". Sorry for the churn @gildub .

@vconzola it's pretty trivial to change the button text, if you want us to do it right on the other pages.

@vconzola, not a worry, let's keep the button in the HookTable as "Create Hook" then.

@gildub Just make "hook" lowercase - "Create hook"

@gildub since a lot of my stuff above is uncertain pending the discussion on Friday, if you just address the rest I'll merge it as-is and we can follow up to address those points.

@mturley, thank for your review, I've addressed comments relevant prior the hook discussion.


UI Issue

Description
The history of cases timeline and suggestions for search bar coincide with each other.
To Reproduce
Steps to reproduce the behavior:

Go to 'Go to any date in history'
Click on 'search bar'
See error

Expected behavior
A clear distinction should be seen between suggestions and timeline
Screenshots

Duplicates #2225


Correct integer division in pow modifiers

Summary
These would have been evaluted to the integer 0 instead of the intended floating-point value 0.5.

Details and comments
Fix #528

Me too - I actually wrote this PR before Lev made that issue, but after I had to run off very quickly at the end of the TSC meeting I didn't have time to push it.  Happy to switch to whichever.

I'll put in a +0.5 for switching to 0.5 as slightly nicer looking.


Gradle 5.4.1

Gradle 5.4.1 update.

You don't have to close every PR, if you want to add new commits. Commits will be added automatically to the PR.

Thanks for the hint, actually I am new to github)
On Wed, 19 Jun 2019, 10:40 SimonIT<EMAIL_ADDRESS>wrote:

You don't have to close every PR, if you want to add new commits. Commits
will be added automatically to the PR.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/libgdx/libgdx/pull/5673?email_source=notifications&email_token=AFULZW3EHURQ6BOQYPNFCCTP3HIHRA5CNFSM4HZGJNO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYA3JPI#issuecomment-503428285,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFULZW6S25BT7BEW2GQGUMDP3HIHRANCNFSM4HZGJNOQ
.

Please update PR description with the platform and IDE combinations you have tried this on.
We need to make sure every backend works on every major IDE we support, which is at very least, Intellij and eclipse. Minimum is that all backends work on command line.

@mr-gri3ves are you still working on this?

@dargonforce Hey, unfortunately I am very busy at the moment, I'll be freed from 2 weeks, and of course, I'll work on this issue.

see https://github.com/libgdx/libgdx/pull/5700

Thanks for your efforts @mr-gri3ves . I have updated master myself.


MS-Celeb-1M splits filenames

Could you please share the filenames used for the train/test splits of Ms-Celeb-1M?
The paper mentions (Sec 4.1) creating 10 random splits. To be consistent with your results, it would be very useful if you give the list of files in each split.
thank you!

@AruniRC Hi, the splits have already been shared. You can find them in https://github.com/yl-1993/learn-to-cluster/issues/2 or README (the second [optional]).


Report queries using graphql don't work for all kinds of quantities/costs

Opening an issue to discuss resolving this problem.
Currently, we have graphql support in abacus. However, due to the strongly typed nature, this doesn't quite work on all possible metrics. The current report schemas assign a GraphQLFloat to both the cost and quantity. This definitely is not always the case as seen in something like the memory metric from our linux-container sample. The cost and quantity in that metric are objects.
Using the queries from the reporting unit tests
        // Query with no sub selections in quantity
        const query1 = '{ resource_instance(organization_id: ' +
          '"org", consumer_id: "con", resource_instance_id: "ins", ' +
          'plan_id: "basic", metering_plan_id: "basic-test-metering-plan", ' +
          'rating_plan_id: "basic-test-rating-plan", pricing_plan_id: ' +
          '"test-pricing-basic", time:<PHONE_NUMBER>000) { organization_id, ' +
          'consumer_id, resource_instance_id, plan_id, ' +
          'accumulated_usage { metric, windows { quantity }}}}';

        // Query with sub selections in quantity
        const query2 = '{ resource_instance(organization_id: ' +
          '"org", consumer_id: "con", resource_instance_id: "ins", ' +
          'plan_id: "basic", metering_plan_id: "basic-test-metering-plan", ' +
          'rating_plan_id: "basic-test-rating-plan", pricing_plan_id: ' +
          '"test-pricing-basic", time:<PHONE_NUMBER>000) { organization_id, ' +
          'consumer_id, resource_instance_id, plan_id, ' +
          'accumulated_usage { metric, windows { quantity { consumed }}}}}';

In the first query, since, an object is not a float, GraphQL returns null as the result. The second query, causes GraphQL to return with a list of errors since the subselection itself was never defined in the schema and thus an invalid query.

One possible way of achieving with a slight change to the schema is utilizing a list of key/value pairs for quantity/cost. Using:
{
  "consuming": 5,
  "consumed": 0,
  "since":<PHONE_NUMBER>000
}

as an example, this could easily be represented as:
[
['consuming', 5],
['consumed', 0],
['since',<PHONE_NUMBER>000]
]

I think there's a couple of things to consider here though:

If the quantity/cost is changed to a list of key/value pairs, how would we go about returning a flat scalar like some metrics return right now?
This won't account for an even more nested structure

To accommodate for the 2nd point, I'm wondering if having an input like this would work:
[
['consuming', 'now', 5],
['consuming', 'then', 1],
['consumed', 'now', 200],
['consumed', 'then', 0]
]

which would result in:
{
  "consuming": {
    "now": 5,
    "then": 1
  },
  "consumed": {
    "now": 200,
    "then": 0
  }
}

And potentially, a scalar could be represented as
[[null, 500]]

Since aggregator would be the one writing these docs, odd inputs that mix the various scenarios detailed above together shouldn't come up as actual data.
Thoughts?

Fixing this by adding an new anyType type (mapped to an anyOf JSON type and a GraphQLScalarType GraphQL type) to our schema module, then changing the types of usage quantity and cost to that new anyType.

See commits e27cb03, 2d48ea1 and 9641607 for the code changes.


code cleanup

Mute unused arguments for cobra command in main function

Thanks for your first contribution! I would more great PRs like this! 🚀


added OpenSUSE Leap 15.4 in HCL

This PR adds the Packer plan for OpenSUSE Leap 1.4
The code is written in Hashicorp Configuration Language instead of JSON

Thank you :+1: