Dotfiles improvements

SpaceVim

~add ctrl+p short cut to spacevim~ not needed if using denite layer

if has('python3')
    let g:ctrlp_map = ''
    nnoremap <silent> <C-p> :Denite file_rec<CR>
endif

~disable right alt 2 & 3 since is needed to UK + PT keyboards~ alacritty issue
save default configuration even if not automated, since SpaceVim changes fast

TMUX

Investigate rendering issues in TMUX in new computer

Install scripts

Add alacritty to the downloads scripts
Remove not used packages from the scripts
Add steps for zplug installation
Add vscode when working with others
Simplify scripts so it can run only some parts (like setting up github and git only)
Add scripts to download the list of brew and cask when migrating computers
Update the scripts to create work folder and personal folder and set different email for those folders

Alacritty

Include yml with the same font as SpaceVim
Include yml with # fix

updated the branch with the latests configuration


Rename "Adjust range" to "Trim range"

Fixes
This pull request fixes #2630
Description
Renames the title of the job that trims the range of the selected log to make it more clear that it actually trims the log.
Type of change

[ ] Bugfix
[ ] New feature (non-breaking change which adds functionality)
[x] Enhancement of existing functionality
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Impacted Areas in Application

[x] Frontend
[ ] API
[ ] WITSML
[ ] Desktop
[ ] Other (please describe)

Checklist:
Code quality

[x] I have self-reviewed my code
[x] No new warnings are generated

Test coverage

[x] New code is covered by passing tests

Further comments

Hi, may I ask who you are and what interest you have in this application?
There are also a couple of places in the TrimLogObjectModal where the text should be changed.

Hello @eliasbruvik, I'm Ishaan Shaikh, a student and I have recently developed an interest in the open source community. I came across this repository and found an issue which I can fix.


Plugin fails to build docs because of duplicate tags

In the doc file there are duplicate tags comment-box-lines in lines 400 and 587. According to the table of contents, it seems that the tag in line 400 should be comment-box-line instead.

Fixed, thank you :)


Node is not deleted from the tree when window is closed

Describe the bug
When I close any window, its space is not reclaimed by siblings.
https://youtu.be/5JPp_Tts4tM how it happens for me.
$aerospace list-windows --workspace 5 --format "%{window-id} |  %{window-title} | %{app-bundle-id} | %{app-name}"
gives me
7247 |   | com.googlecode.iterm2 | iTerm2
7250 |  mkutsevol@mkutsevol-mac:~ | com.googlecode.iterm2 | iTerm2
7152 |  mkutsevol@mkutsevol-mac:~ | com.googlecode.iterm2 | iTerm2

This happens for any app, not just the terminal.
But if I have 2 different apps on a workspace, and I close one, it behaves correctly.
I'd expect the ||| split to turn into || split after the middle one is closed.
It doesn't matter which one I close, if it's on the edge or inside. Type of layout doesn't matter also.
Configuration of aerospace is the default one from the docs.
Versions:
aerospace CLI client version: 0.15.2-Beta b6cf82771f245ab7349a93baf8709e171537ff58
AeroSpace.app server version: 0.15.2-Beta b6cf82771f245ab7349a93baf8709e171537ff58
Displays have separate spaces is disabled.
macOS is 15.0.1 (24A348) running on mac studio 2023 with 3 monitors.
Output of aerospace debug-windows I clicked that empty space in the middle. It was a different run of the same reporducer, not the one on the recording.
com.googlecode.iterm2.window.46 windowId: 46
com.googlecode.iterm2.window.46 workspace: 3
com.googlecode.iterm2.window.46 treeNodeParent: AppBundle.TilingContainer
com.googlecode.iterm2.window.46 recognizedAsDialog: false
com.googlecode.iterm2.window.46 AXTitle: Optional(aerospace debug-windows)
com.googlecode.iterm2.window.46 AXRole: Optional(AXWindow)
com.googlecode.iterm2.window.46 AXSubrole: Optional(AXStandardWindow)
com.googlecode.iterm2.window.46 AXFocused: Optional(0)
com.googlecode.iterm2.window.46 AXFullScreen: Optional(0)
com.googlecode.iterm2.window.46 AXFrame: Optional(<AXValue 0x600003480640> {value = x:-2560.000000 y:-1760.000000 w:2560.000000 h:2839.000000 type = kAXValueCGRectType})
com.googlecode.iterm2.window.46 AXPosition: Optional(<AXValue 0x600002fb1860> {value = x:-2560.000000 y:-1760.000000 type = kAXValueCGPointType})
com.googlecode.iterm2.window.46 AXGrowArea: nil
com.googlecode.iterm2.window.46 AXMinimizeButton: AXUIElement {
com.googlecode.iterm2.window.46      AXRole: Optional(AXButton)
com.googlecode.iterm2.window.46      AXTitle: nil
com.googlecode.iterm2.window.46      AXSubrole: Optional(AXMinimizeButton)
com.googlecode.iterm2.window.46      AXEnabled: Optional(1)
com.googlecode.iterm2.window.46      AXParent: AXUIElement(windowId=46, title="aerospace debug-windows", role="AXWindow", subrole="AXStandardWindow")
com.googlecode.iterm2.window.46      AXTopLevelUIElement: AXUIElement(windowId=46, title="aerospace debug-windows", role="AXWindow", subrole="AXStandardWindow")
com.googlecode.iterm2.window.46      AXWindow: AXUIElement(windowId=46, title="aerospace debug-windows", role="AXWindow", subrole="AXStandardWindow")
com.googlecode.iterm2.window.46      Ignored: AXFrame, AXSize, AXFocused, AXHelp, AXPosition, AXRoleDescription
com.googlecode.iterm2.window.46 }
com.googlecode.iterm2.window.46 AXDocument: nil
com.googlecode.iterm2.window.46 AXSections: [
com.googlecode.iterm2.window.46         Optional({
com.googlecode.iterm2.window.46             SectionDescription = Content;
com.googlecode.iterm2.window.46             SectionObject = "<AXUIElement 0x600002ffa7f0> {pid=984}";
com.googlecode.iterm2.window.46             SectionUniqueID = AXContent;
com.googlecode.iterm2.window.46         }),
com.googlecode.iterm2.window.46         Optional({
com.googlecode.iterm2.window.46             SectionDescription = "Top Level Navigator";
com.googlecode.iterm2.window.46             SectionObject = "<AXUIElement 0x600002ffa280> {pid=984}";
com.googlecode.iterm2.window.46             SectionUniqueID = AXTopLevelNavigator;
com.googlecode.iterm2.window.46         })
com.googlecode.iterm2.window.46 ]
com.googlecode.iterm2.window.46 AXCloseButton: AXUIElement {
com.googlecode.iterm2.window.46      AXRole: Optional(AXButton)
com.googlecode.iterm2.window.46      AXTitle: nil
com.googlecode.iterm2.window.46      AXSubrole: Optional(AXCloseButton)
com.googlecode.iterm2.window.46      AXEnabled: Optional(1)
com.googlecode.iterm2.window.46      AXParent: AXUIElement(windowId=46, title="aerospace debug-windows", role="AXWindow", subrole="AXStandardWindow")
com.googlecode.iterm2.window.46      AXTopLevelUIElement: AXUIElement(windowId=46, title="aerospace debug-windows", role="AXWindow", subrole="AXStandardWindow")
com.googlecode.iterm2.window.46      AXWindow: AXUIElement(windowId=46, title="aerospace debug-windows", role="AXWindow", subrole="AXStandardWindow")
com.googlecode.iterm2.window.46      Ignored: AXFrame, AXSize, AXFocused, AXHelp, AXPosition, AXRoleDescription, AXEdited
com.googlecode.iterm2.window.46 }
com.googlecode.iterm2.window.46 AXMain: Optional(1)
com.googlecode.iterm2.window.46 AXActivationPoint: Optional(<AXValue 0x600002ff1830> {value = x:-2490.000000 y:-1746.000000 type = kAXValueCGPointType})
com.googlecode.iterm2.window.46 AXFullScreenButton: AXUIElement {
com.googlecode.iterm2.window.46      AXRole: Optional(AXButton)
com.googlecode.iterm2.window.46      AXTitle: nil
com.googlecode.iterm2.window.46      AXSubrole: Optional(AXFullScreenButton)
com.googlecode.iterm2.window.46      AXEnabled: Optional(1)
com.googlecode.iterm2.window.46      AXParent: AXUIElement(windowId=46, title="aerospace debug-windows", role="AXWindow", subrole="AXStandardWindow")
com.googlecode.iterm2.window.46      AXTopLevelUIElement: AXUIElement(windowId=46, title="aerospace debug-windows", role="AXWindow", subrole="AXStandardWindow")
com.googlecode.iterm2.window.46      AXWindow: AXUIElement(windowId=46, title="aerospace debug-windows", role="AXWindow", subrole="AXStandardWindow")
com.googlecode.iterm2.window.46      Ignored: AXFrame, AXSize, AXFocused, AXChildren, AXHelp, AXPosition, AXRoleDescription
com.googlecode.iterm2.window.46 }
com.googlecode.iterm2.window.46 AXProxy: nil
com.googlecode.iterm2.window.46 AXDefaultButton: nil
com.googlecode.iterm2.window.46 AXMinimized: Optional(0)
com.googlecode.iterm2.window.46 AXParent: Optional(<AXUIElement Application 0x600002f99b90> {pid=984})
com.googlecode.iterm2.window.46 AXTitleUIElement: AXUIElement(windowId=46, title=nil, role="AXStaticText", subrole=nil)
com.googlecode.iterm2.window.46 AXCancelButton: nil
com.googlecode.iterm2.window.46 AXModal: Optional(0)
com.googlecode.iterm2.window.46 AXZoomButton: AXUIElement {
com.googlecode.iterm2.window.46      AXRole: Optional(AXButton)
com.googlecode.iterm2.window.46      AXTitle: nil
com.googlecode.iterm2.window.46      AXSubrole: Optional(AXFullScreenButton)
com.googlecode.iterm2.window.46      AXEnabled: Optional(1)
com.googlecode.iterm2.window.46      AXParent: AXUIElement(windowId=46, title="aerospace debug-windows", role="AXWindow", subrole="AXStandardWindow")
com.googlecode.iterm2.window.46      AXTopLevelUIElement: AXUIElement(windowId=46, title="aerospace debug-windows", role="AXWindow", subrole="AXStandardWindow")
com.googlecode.iterm2.window.46      AXWindow: AXUIElement(windowId=46, title="aerospace debug-windows", role="AXWindow", subrole="AXStandardWindow")
com.googlecode.iterm2.window.46      Ignored: AXFrame, AXSize, AXFocused, AXChildren, AXHelp, AXPosition, AXRoleDescription
com.googlecode.iterm2.window.46 }
com.googlecode.iterm2.window.46 AXSize: Optional(<AXValue 0x600002f99b90> {value = w:2560.000000 h:2839.000000 type = kAXValueCGSizeType})
com.googlecode.iterm2.window.46 AXToolbarButton: nil
com.googlecode.iterm2.window.46 Ignored: AXChildrenInNavigationOrder, AXChildren, AXRoleDescription
com.googlecode.iterm2           AXRole: Optional(AXApplication)
com.googlecode.iterm2           AXTitle: Optional(iTerm2)
com.googlecode.iterm2           AXFunctionRowTopLevelElements: [
com.googlecode.iterm2           ]
com.googlecode.iterm2           AXFrame: nil
com.googlecode.iterm2           AXFocusedUIElement: AXUIElement(windowId=46, title=nil, role="AXTextArea", subrole=nil)
com.googlecode.iterm2           AXFrontmost: Optional(1)
com.googlecode.iterm2           AXExtrasMenuBar: nil
com.googlecode.iterm2           AXMainWindow: AXUIElement(windowId=46, title="aerospace debug-windows", role="AXWindow", subrole="AXStandardWindow")
com.googlecode.iterm2           AXFocusedWindow: AXUIElement(windowId=46, title="aerospace debug-windows", role="AXWindow", subrole="AXStandardWindow")
com.googlecode.iterm2           AXMenuBar: Optional(<AXUIElement 0x600002f99b90> {pid=984})
com.googlecode.iterm2           AXWindows: [
com.googlecode.iterm2               AXUIElement(windowId=46, title="aerospace debug-windows", role="AXWindow", subrole="AXStandardWindow"),
com.googlecode.iterm2               AXUIElement(windowId=910, title="mkutsevol@mkutsevol-mac:~", role="AXWindow", subrole="AXStandardWindow"),
com.googlecode.iterm2               AXUIElement(windowId=904, title="mkutsevol@mkutsevol-mac:~", role="AXWindow", subrole="AXStandardWindow")
com.googlecode.iterm2           ]
com.googlecode.iterm2           AXSize: nil
com.googlecode.iterm2           AXPosition: nil
com.googlecode.iterm2           Ignored: AXChildren, AXChildrenInNavigationOrder, AXEnhancedUserInterface, AXPreferredLanguage, AXRoleDescription, AXHidden

Please help.
Thank you!
Related issues you could find
I failed to find anything. It makes me think that I'm missing something obvious. Please help :)

FWIW I have those tiling options in Desktop&Dock disabled.

I suspect that
            if window.observe(destroyedObs, kAXUIElementDestroyedNotification) && in MacWindow.swift never gets notification of windows closing.
But I can't properly confirm, as I don't have access to a mac machine on which it works.
And this is the first time I look at apple apis. I either don't know where docs are, or they really don't have anything beyond "An accessibility object was disposed of." as description of this notification.
Another piece of observation: if I completely close iTerm, so that the app really quits, and then open it again, it will position itself correctly on all available space.

I got some progress, but I don't know what I'm doing :D
It's not a solution, it's narrowing down what is happening, but I'll run it locally, as I killed yabai and I don't want back. AeroSpace just works better :)
So, if I add
    private func garbageCollectWindows() {
        // This is hilariously bad compared to notification driven way.
        // I have no idea if the check for absence of attributes means that the window is actually closed,
        // that's what I gathered from running it in debugger.
        MacWindow.allWindows.lazy.filter { $0.app == self }.forEach {
            if $0.axWindow.attrs.isEmpty{
                $0.garbageCollect()
            }
        }
    }

    static func garbageCollectClosedWindows() {
        for app in Array(allAppsMap.values) {
            app.garbageCollectWindows()
        }
    }

to MacApp.swift, and then call it from gc() on every refresh after MacApp.garbageCollectTerminatedApps() then I get the behavior I expect. It reclaims space. I didn't notice any strange sideeffects, but a) test was really limited in time b) I don't have all the possible strange apps installed.

Duplicate of #445

I didn't notice any strange sideeffects, but a) test was really limited in time

If you lock the screen, all windows attrs becomes empty. You unlock the screen and windows don't preserve their workspace assignment

I didn't notice any strange sideeffects, but a) test was really limited in time

If you lock the screen, all windows attrs becomes empty. You unlock the screen and windows don't preserve their workspace assignment

Thanks for looking into it @nikitabobko! And for writing this savior of macos that makes it useable! :D
So I went to sleep with a release build that had those changes running. It locked the screen because I was away for a long time. There are no logs in that piece of code so I can't tell if it executed it for every window or not, but I can't see any strange behavior from the machine. All windows were on correct monitors. I can manage windows with hotkeys. I tried moving focus on one workspace, jumping to different workspace on the same monitor and to different monitor, resizing windows, moving windows. And then I tried closing a window of iTerm. And it behaved as it should, I didn't notice anything at all. Then I tried locking the screen myself, and I also didn't experience any effects at all. It works.

Duplicate of https://github.com/nikitabobko/AeroSpace/issues/445

It says

(e.g. if user quickly closes several windows in a row)

For me it's every time, very consistently. I don't have to do it quickly. And I don't have to do multiple in a row. It just never fires the kAXUIElementDestroyedNotification. And I also had a breakpoint in the callback there, it was never hit.

release.tgz
that's a release build of the tip of master branch with my changes, if anyone wants to check if that works. It's an archive with the .release folder.  https://github.com/nikitabobko/AeroSpace/blob/main/install-from-sources.sh#L17-L23 is the part that needs to be executed to install, boiling down to:

unpack, it will create .release folder
uninstall existing version, and -dev if you have it
brew install --cask ./.release/aerospace-dev.rb

I wonder if that will work for your case also, @juandazapata.

@mkutsevol if you want to share code, please share links to commits in your fork instead of sharing compiled binaries.

git diff https://gist.github.com/mkutsevol/bf4567a7e5b7818245847e644965fc55
The meaningful part of the code is above in this thread.
I found it to be tedious to get it to compile, setup env. So a binary is useful if folks want to spend 10 minutes testing, not an hour setting up the build env for it.

After several days with my changes I definitely see that sleeping (logoff) does something to it, as @nikitabobko said earlier. But with my config, where workspaces are pinned to monitors and windows are pinned to workspaces in config, it doesn't matter much. I lose ordering of terminal windows after a break, but that I can live with, compared to the app being unusable for me. So the changes I had are just trading one problem for another, it's not a fix of any kind. I'll sit & wait for a proper solution :D


Searching algorithm in cpp

I want to contribute code of binary search and linear search in cpp . Could you please assign it to me under hactoberfest23.

can you please assign this issue to me i want to solve this issue by divide and conquer approach

I want to solve this issue_please assign me this.

Please assign this issue to me under hactoberfest23.
I can contribute with linear search and binary search code in cpp.Will also add comment wherever necessay and make user-friendly code.
Thank you


Conflicts with Amazon WorkSpaces

Thank you for the hard works making Karabiner compatible with macOS Sierra! It works perfectly for me except that it seems that Karabiner-Elements conflicts with Amazon WorkSpaces. Karabiner used to play very well with the WorkSpaces, but after I upgrade to Sierra and switch to Karabiner-Elements, I can no longer type in WorkSpaces. The current workaround for me is to quit Karabiner-Elements before connecting to my remote desktop.
Could you please help solving this problem? I'm glad to provide any debugging information if needed.

Here's some hints that I found in Karabiner-Elements' log:
[2016-09-30 16:40:05.078] [grabber] [warning] There are pressed down keys in Apple Internal Keyboard / Trackpad. Please release them.
[2016-09-30 16:40:06.087] [grabber] [warning] There are pressed down keys in Apple Internal Keyboard / Trackpad. Please release them.
[2016-09-30 16:40:07.088] [grabber] [warning] There are pressed down keys in Apple Internal Keyboard / Trackpad. Please release them.
[2016-09-30 16:40:08.090] [grabber] [warning] There are pressed down keys in Apple Internal Keyboard / Trackpad. Please release them.
[2016-09-30 16:40:09.095] [grabber] [warning] There are pressed down keys in Apple Internal Keyboard / Trackpad. Please release them.
[2016-09-30 16:40:10.085] [grabber] [warning] There are pressed down keys in Apple Internal Keyboard / Trackpad. Please release them.

I'm getting those log entries while the WorkSpaces is connected.

I also have this issue.

Confirming this is a blocker as well.
Workspaces Version: <IP_ADDRESS>2 ( 10/13/16 )
Karabiner Elements Version: 0.90.68
I'm unable to corroborate @haochenx 's logs however I'll add that the trackpad / mouse operations are perfectly normal, only the keyboard is impacted.
If there are additional debugging steps I could perform please let me know.

@tekezo this issue is still occurring, is there any other information I could provide that would help triage this?

+1. Karabiner is an amazing piece of software. However, since upgrading to Karabiner-Elements and Sierra, the keyboard stops responding when in Amazon Workspaces. I can confirm that mouse and / or trackpad continue to operate normally - this only affects the keyboard (internal as well as external).

Maybe related to #447

This has been going on since before Elements and Sierra; pretty sure this is not a new issue to either Seil+Karabiner or the OS. One other set of notes: if Karabiner-Elements is running when I start Workspaces, I get no keyboard input inside the Workspaces host OS. Even if I quite K-E, Workspace keyboard inputs won't work. I have to restart Workspaces.
If I start Workspaces without K-E running, keyboard works inside Workspaces; then if I start K-E, keyboard stops working inside Workspaces; then if I quit K-E, keyboard resumes working. With this second scenario, I don't have to restart Workspaces to get the keyboard working again. It's not a workaround per se, but it is different behavior based upon which application was running first.

With Karabiner 10.22 on El Capitan, the keyboard worked in Workspaces but the Karabiner mappings (Fn<->LControl swap in my case) were not in effect.  I just upgraded to Karabiner-Elements 11 yesterday, still on El Capitan, and now I am experiencing this issue - keyboard doesn't work at all in the WorkSpaces client.  Big bummer...

Issue for me on High Sierra as well
Maybe an workaround option would be to have a program exclude list for Karabiner (and possibly others like Discord, according to the linked issue above) where it doesn't bind the keyboard into that program when it's running but carries on as normal with other programs, not sure if this is possible with the keybinding framework in macOS?

Just counteracting the stale vacuum bot.  This is still an issue for me on High Sierra.

I was stuck with this issue for a while.  However, now, I am able to work around this issue by using an external keyboard and toggling the USB switch on my USB-C hub which corresponds to the keyboard.  I know this sounds really strange.  I was having a hard time reproducing the workaround because I couldn't figure out what order of events lead to me being able to use the keyboard and run Karabiner Elements.  But this seems to be it:

Connect Mac to USB hub
Log in to Workspace (keyboard does not work once inside Workspace)
Toggle power switch on USB hub (my hub has 4 ports and 4 power switches, so I toggle the one for the keyboard)
External keyboard now works (on board keyboard does not work)

I hope this helps someone.

If the issue still exists it should not be closed.

FYI, On Karabiner 12.1.0 I do not appear to have this problem any more.
I can run Karabiner, open the Amazon workspaces client and -- huzzah -- type into the workspace.

I'm not sure which change/upgrade resulted in the problem being resolved for me, but I can confirm that with macOS 10.13.6, Karabiner-Elements 12.1.0, and WorkSpaces client <IP_ADDRESS>7 (2018-08-29) I am no longer experiencing this problem.  Further, key remapping appears to be in effect!

Confirming that 12.1.0 seems to fix it as well! This is a great day!!!

I have the same issue, but I don't know whether the culprit is Karabiner. I tried quitting Karabiner and it didn't work. The only fix was a restart, it sometimes works after a restart. The problem seems to be in Amazon Workspaces.


[Session] Doesn't work session in PostgreSQL

What steps will reproduce the problem?
Doesn't work session in PostgreSQL 12.2
What is the expected result?
Authorization via session DB
Quite a strange bug, because it is simple, but however my problem is not solved... I updated the framework to 2.0.38 and switched to php74. After updating the backend application that stores sessions in files is working. But the frontend application which stores sessions in the database, refuses. Can't figure out why ... Did even direct authentication:
php public function actionLogin()
{
    $user = User::findOne(261);
    Yii::$app->user->login($user,1000*60*60*24);

    if (!Yii::$app->user->isGuest) {
        return $this->redirect('index');
        ///return $this->redirect(Yii::$app->homeUrl);
    }
}

php public function actionIndex()
{
    var_dump(123);
    var_dump(Yii::$app->user->identity);
    die();

    return $this->actionLogin();
}

It gets to the page. This means that he will authorize it for 1 second. And in Index it already disappears after the request. In this case, sessions in the database are created and they are not expired.
Config for session component
'session' => [
    'class' => 'yii\web\DbSession',
    'timeout' => intval(@$params['sessionTimeout']) ?: 180 * 60, // 180 мин
    'sessionTable' => '{{%auth_session}}',
    'writeCallback' => function ($session) {
        $loginTime = null;
        if (!Yii::$app->user->isGuest) {
            $loginTime = Yii::$app->user->identity->getLastLogin();
        }
        return [
            'user_id' => Yii::$app->user->id ?: 0,
            'ip' => Yii::$app->request->userIP,
            'login_time' => $loginTime,
        ];
    }
],

This file works. This commit breaks my functionality.
What do you get instead?
Logout in one second
Additional info

Q
A

Yii version
2.0.38

PHP version
7.4

Operating system
CentOS

This commit breaks my functionality

What's the schema of your session table?

create table auth_session
(
    id         varchar(60)  default ''::character varying not null
        constraint auth_session_pk
            primary key,
    expire     integer      default 0,
    data       text         default ''::text,
    user_id    integer      default 0,
    login_time timestamp(0),
    ip         varchar(255) default ''::character varying
);

Aha. Seems the issue is likely about data structure. Here's current one:
https://github.com/yiisoft/yii2/blob/master/framework/web/migrations/schema-pgsql.sql

Changed the type, but it didn't solve the problem
create table auth_session
(
    "id"  varchar(256) not null,
    "expire" integer,
    "data"   bytea,
    "login_time" timestamp(0),
    "ip" varchar(255)
     primary key ("id")
);

How to reproduce the error?

Install Yii2 Advanced for documentation
Select web server Nginx and setting configuration from documentation
Install PostgreSQL 12.2
run command in console: php yii migrate --migrationPath=/var/www/yii2-test/vendor/yiisoft/yii2/web/migrations
config main.php:

return [
    'aliases' => [
        '@bower' => '@vendor/bower-asset',
        '@npm'   => '@vendor/npm-asset',
    ],
    'vendorPath' => dirname(dirname(__DIR__)) . '/vendor',
    'components' => [
        'cache' => [
            'class' => 'yii\caching\FileCache',
        ],
        'session' => [
            'class' => DbSession::class,
            'timeout' => 180 * 60, // 180 мин
            'sessionTable' => '{{%session}}',
        ],
    ],
];

Login user

public function actionLogin()
    {
        var_dump(Yii::$app->user->identity);

        $identity = User::findOne(261);
        Yii::$app->user->login($identity);

        die();
    }

The first page update will return null, and the second should return the authorized user, but in my case it also returns null

Alright. It is highly likely it is a valid bug. We need to reproduce it now and it seems we have all the prerequisites.

Very well! How can I help?

Right now you can't. We need to allocate some time to do the actual test locally, do git bisect to find the commit in question etc.

Can you show your User class.

I using User model from Yii advanced template.

@Myks92 I've tried it with instructions in https://github.com/yiisoft/yii2/issues/18326#issuecomment-708053477:

Got advanced app template.
Initialized it with dev environment.
Pointed DB to a Postgres instance.
Adjusted config to use DbSession.
Applied migrations (both application and session table ones).
./yii serve --docroot frontend/web/.
Opened frontend in the browser.
Registered a user.
Activated it.
Logged in keeping "remember me" off.
Got to other pages. Session is valid, application works well.

So overall I cannot reproduce the issue. It must be either something in your application or server config or extra options that you haven't provided.


lodash 3.8.0

Hi,
I am wondering if dagre v0.7.2 will be compatible with lodash 3.8.0? (it's currently on 2.4.1)
Thanks,
Sixin

It does not appear to be. There are three failing tests when bumping lodash to 3.8.0.

oh :(
is there a plan to upgrade lodash anytime soon?

Version is 3.9.3 now.

The lib support 3.10.0, but there is a bug in the test system that fail to deeply compare arrays. Please read as follows, the expected and actual parts are the same:
286 passing (525ms)
4 failing

version should match the version from package.json:
AssertionError: expected {} to equal '0.7.3-pre'
at Context. (test/version-test.js:6:39)

acyclic greedy run does not change an already acyclic graph:
AssertionError: expected [ Array(4) ] to deeply equal [ Array(4) ]

expected - actual
"v": "a"
"w": "b"
}
{

"v": "a"

"w": "c"

}

{
"v": "b"
"w": "d"
}
{

"v": "a"
"w": "c"
}
{
"v": "c"
"w": "d"
}
]

at Context. (test/acyclic-test.js:32:52)

acyclic dfs run does not change an already acyclic graph:
AssertionError: expected [ Array(4) ] to deeply equal [ Array(4) ]

expected - actual
"v": "a"
"w": "b"
}
{

"v": "a"

"w": "c"

}

{
"v": "b"
"w": "d"
}
{

"v": "a"
"w": "c"
}
{
"v": "c"
"w": "d"
}
]

at Context. (test/acyclic-test.js:32:52)

acyclic unknown-should-still-work run does not change an already acyclic graph:
AssertionError: expected [ Array(4) ] to deeply equal [ Array(4) ]

expected - actual
"v": "a"
"w": "b"
}
{

"v": "a"

"w": "c"

}

{
"v": "b"
"w": "d"
}
{

"v": "a"
"w": "c"
}
{
"v": "c"
"w": "d"
}
]

at Context. (test/acyclic-test.js:32:52)

cool, maybe we can try to fix the tests if that's the only thing blocking the update?

@sheymann thanks for digging into it.
I looked at the test, and it looks like it is written correctly:
          expect(_.sortBy(results, ["v", "w"])).to.eql([
            { v: "a", w: "b" },
            { v: "a", w: "c" },
            { v: "b", w: "d" },
            { v: "c", w: "d" }
          ]);

The test expects that the results, sorted by "v" and then by "w", would equal the sorted array specified. It seems that the previous behavior for _.sortBy has changed in a way that is not entirely clear, as it is no longer returning the results sorted.
A simple test confirms:
_.sortBy([{ v: "a", w: "b" }, { v: "c", w: "d" }, { v: "a", w: "e"}], ["v", "w"])
// =>
// [ { v: 'a', w: 'b' },
//  { v: 'c', w: 'd' },
//  { v: 'a', w: 'e' } ]

It's possible I was misusing _.sortBy, but it's not obvious on quick inspection how. Once we figure this out we need to do a pass and make sure _.sortBy is not used incorrectly elsewhere, in a way that is not detected by a test.

Looking  a little closer at the doc it looks like they dropped support for multi-key sorts. so the above would need to be something like _.sortBy(_.sortBy(results, "w"), "v").
Will look through the code for this pattern as I get time. Happy to take a pull request if someone wants this sooner.

Maybe try using sortByAll
from v 3.0.0 changelog:

Moved support for sorting by multiple properties from _.sortBy to _.sortByAll

Perfect! That should be straightforward to fix tonight. Thanks teodragovic!

Fixed in v0.7.3


Programmatically set ontintcolor

Hello,
I tried setting the ontintcolor programatically, this doesn't seem to work. only through storyboard.
self.paperSwitch1.onTintColor = UIColor(red: 241/255, green: 196/255, blue: 15/255, alpha: 1)
self.setupColorSwitch()

I set this in the viewDidLoad function but it doesn't seem work, anyone now a solution?

Thank you


Trouble selecting an email for a GenArt review

Describe the issue
I generally email my GenArt reviews and then in the tracker I use the option to select an email when closing out the review request.
In the case of draft-ietf-rtgwg-net2cloud-problem-statement after doing the above I decided to revise my review. So I emailed the revised review and then went to Datatracker and asked to Correct Review. Then I once again checked the box to select an email. It showed me several to choose from. The one I want is the first of these.
But it won't let me select it! So I'm stuck!
Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

It looks like you might have worked around this?

On 3/26/23 1:09 AM, Robert Sparks wrote:

It looks like you might have worked around this?

Yes. I pasted the review text into the review page rather
than referencing the email.
Thanks,
Paul

—
Reply to this email directly, view it on GitHub
https://github.com/ietf-tools/datatracker/issues/5395#issuecomment-1483997941, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACAPKD6NSUBIFMPASJKVRETW57FQ5ANCNFSM6AAAAAAWELU4YQ.
You are receiving this because you authored the thread.Message ID:
@.***>

We'll address the block of your use case still - thanks for reporting it.


Eloquent performance extremely slow when cast to JsonResource

Laravel Version
11.24.1
PHP Version
8.3.12
Database Driver & Version
MySQL 8.0.27
Description
I see to many calls of Illuminate\Database\Eloquent\Model::getCasts
Looks like this functions calls each time when access to any attributes and never cached.
Steps To Reproduce
SPX_ENABLED=1 SPX_AUTO_START=0 php artisan tinker

$devices = Device::query()->limit(157)->get();
Auth::login(SystemUser::first());
$x = DeviceListResource::collection($devices);
$x->resolve(); //Avoid n+1 request increasing time in test result

{
    spx_profiler_start();
    $x->resolve();
    spx_profiler_stop();
}

*** SPX Report ***

Global stats:

  Called functions    :     8.6M
  Distinct functions  :      653

  Wall time           :    1.86s
  ZE memory usage     :    5.4MB

Flat profile:

 Wall time           | ZE memory usage     |
 Inc.     | *Exc.    | Inc.     | Exc.     | Called   | Function
----------+----------+----------+----------+----------+----------
  237.6ms |  212.5ms |  161.3MB |  161.3MB |   421.1K | Illuminate\Database\Eloquent\Model::getCasts
  894.6ms |  185.7ms |  652.4KB |  -57.5MB |   319.1K | Illuminate\Database\Eloquent\Model::transformModelValue
  163.1ms |  104.9ms |   57.5MB |   57.5MB |   279.3K | Illuminate\Database\Eloquent\Model::getDates
   64.7ms |   64.7ms |       0B |       0B |   317.7K | Illuminate\Database\Eloquent\Model::hasAttributeGetMutator
   66.1ms |   59.7ms |    8.6KB | -112.8KB |      157 | Illuminate\Database\Connection::Illuminate\Database\{closure}
   52.7ms |   39.3ms |       0B |       0B |   279.3K | Illuminate\Database\Eloquent\Model::usesTimestamps
  188.0ms |   16.0ms |   33.4KB |   33.4KB |    38.3K | 1@Illuminate\Support\Collection::Illuminate\Support\Traits\{closure}
  103.7ms |   12.0ms |  652.4KB |       0B |    31.8K | Illuminate\Database\Eloquent\Model::castAttribute
  172.0ms |   10.4ms |       0B |       0B |    12.9K | data_get
   96.7ms |    6.5ms |    1.3MB |  304.9KB |      157 | App\Http\Resources\System\Device\SystemBaseDeviceResource::toArray

DeviceListResource looks like this, but this is common issue, you can also use any Eloquent collection and just call ->where() to see the problem
class DeviceListResource extends JsonResource
{
    public function toArray($request): array
    {
        return [
            'serialNumber' => $this->serial_number,
            ...
        ];
    }
}

Hey there,
While this may be a legitimate issue, can you first try posting your problem or question on one of the support channels below? If this issue can be definitively identified as a bug, feel free to open up a new issue with a link to the original one and we'll gladly help you out.

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

Thanks!

@crynobone I wouldn't rush to close it. To display 157 devices inside Laravel, 1 function is called half a million times


Update menu button column docs

Pull Request
🤨 Rationale
Update the storybook example and docs for the menu-button table column to include:

A better example of the expected use case that shows the selected item with a check mark next to the selected menu item
Documentation about using the menu-button column vs the action menu

Resolves the comments from https://github.com/ni/nimble/pull/2204#discussion_r1670905005
👩💻 Implementation
Update storybook story
🧪 Testing
Verified the updated story works as expected
✅ Checklist

[ ] I have updated the project documentation to reflect my changes or determined no changes are needed.

@m-akinc, will you buddy this PR for me?


Remove support for Spark 3.0.0

This removes support for Spark 3.0.0, updating the minimum Spark version to Spark 3.0.1.  The spark300 and spark300emr shim projects are removed along with SparkShims methods that were only needed to implement compile differences between Spark 3.0.0 and Spark 3.0.1.  Documentation references to Spark 3.0.0 were also updated to use Spark 3.0.1 instead.

@revan2 I noticed the supported_ops doc updated when I copied the First and Last behavior from spark301 shim into the base shim.  I kept the behavior unchanged, but I'm not sure it's what is intended, so it would be good to get some input there.
@nartal1 I updated the audit code and scripts to reflect the removal of the spark300 shim, if you could give some feedback on those changes that would be appreciated.

build

Spark 3.1.1 tests failed because it was trying to lookup TimeSub which was removed in that version.  I refactored the shim expressions handling to explicitly call this out.  In the process I also realized that the Firstand Last expressions no longer need to be in the shims after 3.0.0 is removed, so I moved those aggregation expressions back into the common code.

build

@nartal1 I updated the audit code and scripts to reflect the removal of the spark300 shim, if you could give some feedback on those changes that would be appreciated.
The changes for audit scripts LGTM. Thanks @jlowe .


[Event Hubs Processor] Tune Log Levels for Storage

Summary
The focus of these changes is to tune the logging level for storage operations in order to reduce the large amount that get emitted for routine and expected operations, such as inspecting and renewing ownership for partitions.  These have been moved to verbose to reduce noise.

/check-enforcer evaluate


[FLINK-26369][doc-zh] Translate the part zh-page mixed with not be translated.

[FLINK-26369][doc-zh] Translate the part zh-page mixed with not be translated.

@1996fanrui @Jiabao-Sun PTAL

@leonardBang PTAL , Thank you~

@flinkbot run azure

@flinkbot run azure

Hi @GOODBOY008 , would you mind rebasing the master branch?
If I remember correctly, this ci isuue has been fixed in master branch.

@1996fanrui Branch has rebased, Thanks for your review.


kubemarine docker size become huge after ansible plugin update

ansible 4.2   11a01eaa4bff   15 hours ago    546MB
ansible 2.4  e5ac387a2e80   15 hours ago    235MB

koryaga@NomadLand:~/nc/src/kubemarine$ docker image history e5ac387a2e80 | grep pip3
<missing>      2 minutes ago   RUN |1 BUILD_TYPE= /bin/sh -c pip3 install -…   76.8MB    buildkit.dockerfile.v0
koryaga@NomadLand:~/nc/src/kubemarine$ docker image history 11a01eaa4bff | grep pip3
<missing>      4 minutes ago   RUN |1 BUILD_TYPE= /bin/sh -c pip3 install -…   388MB     buildkit.dockerfile.v0

Probably need to rework ansible plugin (helm also ?) to not assemble them into docker image.

@dmyar21   pls recheck after update to latest ansible

@koryaga
the current size of docker image with ansible 7.0 is 572MB


Version image collections bucket

As the new image collections bucket is the master store of this collection going forward, we need to enable versioning and version lifecycle management on the bucket.
Let's delete non-current versions after 30 days, like the editorial photography bucket.

This is already done: https://github.com/wellcometrust/platform/blob/master/miro_preprocessor/s3.tf#L44-L54

This is already done:
https://github.com/wellcometrust/platform/blob/master/miro_preprocessor/s3.tf#L44-L54


Fly to bounds tests

Tests to resolve #8367
Let me know what you think.
I made 3 different versions of the main test to demonstrate that the accuracy varies depending on the resulting zoom level.

@Belair34 Tests are failing

Weird, I could have sworn they were passing back then. Should be fixed now!

@mourner I increased the speed of the tests similar to in flyTo, and confirmed that they are still valid.


Add SOR/Kinch ranks

It could be pretty cool to see a page where you could view competitors ranked by SOR or Kinch using the competition results (ex. For kinch WR is replaced by best result at the comp, PR is replaced by best result from the competitor)
There is currently already this website that does this with kinch ranks, but it would be nice to have something that is on WCA live as well, especially for competitions where prizes may be given to the best all rounders.

Currently I would consider this out of the scope of WCA Live. We may revisit additional rankings in the future.
I imagine that one side effect of integrating SOR/Kinch directly into WCA Live (making them more prominent), could be that people sign up for more events just so that they can boost their score a bit (without caring much about those additional events). One could make an argument that this is a good thing, but that could also artificially slow down competitions, without actual benefits.


FOR NEXT's STEP -1 is not always working.

REM -- works!!!!!
FOR X AS BYTE = 1 to 5
print "1 to 5: " + str$(x)
NEXT
REM -- fails!!!!!
FOR X AS BYTE = 10 TO 5 STEP -1
print "step -1: " + str$(x)
NEXT

Not a bug.
All values in a FOR  TO  STEP  construct must be of the same type. In your case, this type is BYTE. Since -1 is an INT, it is converted to BYTE as 255.


'UNSPECIFIED' Value for 'hideleg[n]',  During Read-Only to Writable transition.

For 13 <=n <= 63,  value of hideleg/h[n] may become writable from being read only zero, when  mvien/h[n] or mideleg/h[n] transitions from zero to one.  Should the spec include a sentence saying value of hideleg/h[n] becomes UNSPECIFIED when hideleg/h[n] becomes writable?

I believe this situation is already covered by the RV Privileged ISA, Section 2.4, "CSR Field Modulation".  Note the first comment in that section:

As a special case of this rule, the value written to one CSR may control whether a field of a second CSR is writable (with multiple legal values) or is read-only.  When a write to the controlling CSR causes the second CSR's field to change from previously read-only to now writable, that field immediately gets an UNSPECIFIED but legal value, unless specified otherwise.

I believe this situation is already covered by the RV Privileged ISA, Section 2.4, "CSR Field Modulation". Note the first comment in that section:

As a special case of this rule, the value written to one CSR may control whether a field of a second CSR is writable (with multiple legal values) or is read-only.  When a write to the controlling CSR causes the second CSR's field to change from previously read-only to now writable, that field immediately gets an UNSPECIFIED but legal value, unless specified otherwise.

thanks, that should be okay.


bundle built-in crypto module

I can not figure out how to create a shared/vendor bundle that includes the crypto-browserify module so that it's not automatically included in my app bundle. (shaving 60kb or so off the size)
I tried adding
 "browser": {
    "crypto": "crypto-browserify"
  }

to my package.json but that doesn't work
What seems to work is if I add crypto to my package.json, but crypto is NOT the module browserify uses (it seems it's some other javascript implementation)
how can I add the crypto-browserify to my shared bundle properly?

Assuming you're running a recent version of browserify, you don't have to
modify the browser field at all, require('crypto') will automatically get
crypto-browserify
On Dec 29, 2015 5:30 PM, "Jason Swearingen"<EMAIL_ADDRESS>wrote:

I can not figure out how to create a shared/vendor bundle that includes
the crypto-browserify module so that it's not automatically included in my
app bundle. (shaving 60kb or so off the size)
I tried adding
"browser": {
"crypto": "crypto-browserify"
}
to my package.json but that doesn't work
What seems to work is if I add crypto to my package.json, but crypto is
NOT the module browserify uses (it seems it's some other javascript
implementation)
how can I add the crypto-browserify to my shared bundle properly?
—
Reply to this email directly or view it on GitHub
https://github.com/substack/node-browserify/issues/1467.

yes it does, the problem is that it's always put in my app.bundle.js file, which adds 60kb to it.
I'd like to put crypto (and all the builtins actually, but crypto is the biggest) into a vendor-shared.bundle.js file, but can not figure how to do this.  It's always added to my app.bundle.js file.

fyi, i'm following the multiple-bundles tutorial here: http://fettblog.eu/gulp-browserify-multiple-bundles/

It's always put into your bundle because its required by your code.
You can try setting crypto to "false" in your package.json and bundling it
separately.
On Dec 29, 2015 5:55 PM, "Jason Swearingen"<EMAIL_ADDRESS>wrote:

fyi, i'm following the multiple-bundles tutorial here:
http://fettblog.eu/gulp-browserify-multiple-bundles/
—
Reply to this email directly or view it on GitHub
https://github.com/substack/node-browserify/issues/1467#issuecomment-167901918
.

Thanks for the tip, but unfortunately it has no effect.  Here's what I added to my package.json
  "browser": {
    "crypto": false
  }

The only impact i have is if I include the actual npm crypto module.  That seems to override the browserify auto-bundling of crypto-browserify.  Otherwise no matter what I try, ```crypto-browserify is always added to my bundle.
If I turn off all built-ins, crypto-browserify isn't bundled of course, but it never finds a crypto module to use, even if I add crypto-browserify explicitly in my package.json

maybe the issue is that my app.js file doesn't actually reference the crypto module.  it's a nested dependency by some other module I'm loading.   So these "browser field" settings don't seem to work.

sigh nope, that's not it.  I explicity include crypto and it's still getting loaded up.
I'd venture to guess that multiple-bundling of the builtins just doesn't work.  probably not ever considered to be tested :(

my hacky workaround:
in my gulp file:

when creating the shared bundle, I rename crypto-browserify to crypto via the b.require(path,{expose:id}) function.
when creating my app bundle, I set crypto as an external.

it works, but obviously not ideal.

If you can create a gist using just the browserify API of what you wanted
to do, we might have a better idea of what to consider changing.
Sorry it isn't working out of the box right now.
On Dec 29, 2015 7:02 PM, "Jason Swearingen"<EMAIL_ADDRESS>wrote:

my hacky workaround:
in my gulp file:

when creating the shared bundle, I rename crypto-browserify to crypto
via the b.require(path,{expose:id}) function.

when creating my app bundle, I set crypto as an external.

it works, but obviously not ideal.
—
Reply to this email directly or view it on GitHub
https://github.com/substack/node-browserify/issues/1467#issuecomment-167912780
.

something like this, hope it helps.   this is just the normal creating 2 bundles logic (shared + app bundles) but also doing the part i mentioned about (renaming the module id's of things like crypto-browserify to crypto)
package.json
...
"dependencies":{
"crypto-browserify":"latest"
}
...

gulpfile.ts
...
/**
 *    // get all node components ids and use 'resolve' to resolve
  // the ids to their full path, which we need for require()
 */
function getNPMPackageIds(baseDir: string) {
    try {
        // read package.json and get dependencies' package ids
        var packageManifest = require(path.normalize(path.join(baseDir, './package.json')));
        //var xlibPackageManifest = require(path.normalize(path.join(rootPath, "../xlib", './package.json')));

        var packageKeys = _.keys(packageManifest.dependencies);
        //var xlibKeys = _.keys(xlibPackageManifest.dependencies);
        return packageKeys;//.concat(xlibKeys);
    } catch (e) {
        console.log("!!!!!!!!!  missing package.json! in " + baseDir);
        // does not have a package.json manifest
        return [];
    }
}
/**
 *  hack workaround for browserify inability to shared-bundle built-in modules.  see https://github.com/substack/node-browserify/issues/1467#issuecomment-167901918
 *  these modules are installed in the blib project, but need to have their module-id's changed so that browserify doesn't inject it into the app bundle.
 */
function getFinalBlibPackageId(id: string):string {
    //console.log("\tBLIBS= \t" + id);
    switch (id) {
        case "crypto-browserify":
            return "crypto";
            break;
        case "path-browserify":
            return "path";
            break;
        case "stream-browserify":
            return "stream";
            break;
        case "zlib-browserify":
            return "zlib";
            break;
        case "http-browserify":
            return "http";
            break;
        case "https-browserify":
            return "https";
            break;
        case "os-browserify":
            return "os";
            break;
        case "timers-browserify":
            return "timers";
            break;
        default:
            return id;
    }
}

var packages = getNPMPackageIds(".");
var vendorLibrariesToExclude: string[] = [];

    _.forEach(packages , (id) => {
        var resolvedPath = nodeResolve.sync(id);
        id = getFinalPackageId(id);

        b.require(resolvedPath, {
            // exposes the package id, so that we can require() from our code.
            // for eg:
            // require('./vendor/angular/angular.js', {expose: 'angular'}) enables require('angular');
            // for more information: https://github.com/substack/node-browserify#brequirefile-opts
            expose: id,
        });
        vendorLibrariesToExclude.push(id);
    });

///////////////////////////
///////  create shared bundle
var browserifyOptions = {}; //set options to something for the shared.bundle.js
var b = browserify(browserifyOptions);
b.bundle();

///////////////////////////
//////// create app bundle
var browserifyOptions = {}; //set options to something for the app.bundle.js
var b = browserify(browserifyOptions);
//////////////////////////////////////
// specify our vendor bundled modules as external
for (var i = 0; i < vendorLibrariesToExclude.length; i++) {
    b.external(vendorLibrariesToExclude[i]);
}
b.bundle();
...

Hello @jasonswearingen. When @terinjokes suggested

a gist using just the browserify API

he very likely didn't mean

a gulpfile
something with a bunch of commented-out code
something written in a non-JS language

and likely meant an actual gist (which can be cloned, though if it were me I'd suggest a regular repo). I'm mentioning this because an example like this makes it more work for someone to help you (and therefore makes it less likely someone will). Providing something minimal and focused is much more conducive to anything happening.
It's besides the point, but why would you use a switch instead of a simple map POJO for those module names?

@jmm

there are 3 lines of commented code.  the rest is documentation.  fyi i cleaned this up quite a bit.
if you look at the code you'll see i actually am just dealing with browserify functionality.   nothing in there is gulp related.
you'll be hard pressed to see anything non-JS-language in that code.    a couple id:string like things that are pretty self explanatory.

This should be very easy for a browserify contributor understand the workaround....   if not, well sorry I gave it my best shot.  sorry i only work with browserify via gulp, and my actual gulpfile is very very complicated.
re switch, a POJO would be slightly better, but hindsight 20/20 I suppose.

@jasonswearingen woah, why are you recursing over all of your package's dependencies and requiring them? You should probably simply require your entry file (likely something like "index.js" or "entry.js" or "app.js"), and browserify would automatically resolve any dependencies you have (and you can still exclude whatever you're considering to be vendor libraries).

@jmm i like gists, they don't clutter up my repositories list, so they tend to stick around longer (in case someone down the road ends up wanting to review). But personal preference, and I'd happily work with either :smile_cat:

@terinjokes I've had a hard time warming up to them for some reason. One thing I don't like is that it doesn't seem to be possible to create an empty one and just push the content to it. For people providing repros for most non-trivial things it'd definitely be better than embedding the code in a comment, but with the seeming emphasis on entering the file content via a web form I wonder how people do with making repros that actually run.

@terinjokes ,   not recursing, but looping (i can still see why that would in general be bad)
This "find all 3rd party modules" logic is part of the multi-bundle workflow.  it's so all those modules can be found so they can be put in the shared-vendor.bundle.js  and then excluded from app.bundle.js
sorry again about not including a gist.  never used them, nor browserify by itself, so creating one for this would take many many hours :(
PS: I see the "multiple bundles" link I posted earlier is actually for creating multiple app bundles at the same time.   totally not related to creating shared-vendor bundles!  here's the right link to the tutorial I followed to create shared bundles:  https://github.com/sogko/gulp-recipes/tree/master/browserify-separating-app-and-vendor-bundles  @terinjokes this is where I got the getNPMPackageIds() function from.


[DOC]: Dataset Documentation Inside the Data Folder

How would you describe the priority of this documentation request
High
Describe the future/missing documentation
Although we have documentation about datasets used for model training, testing, and validation as part of the model cards, it would be useful to have this information easily accessible as part of the data folder (https://github.com/nv-morpheus/Morpheus/tree/branch-22.11/examples/data). It is difficult to determine where data is coming from if you don't know to go look at the individual model cards.
Where have you looked?
The information is available in the model cards (https://github.com/nv-morpheus/Morpheus/tree/branch-22.11/models), but it should be replicated as part of the data folder.
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I have searched the open documentation issues and have found no duplicates for this bug report

To prevent us from needing to duplicate the info (and maintain two locations as things change), would it suffice to have a clean readme pointing users to the right place? Something like below.

About
This folder contains the datasets used for model training - to learn more about each dataset please check the readme(link) in the model cards folder.

Ransomware
etc

Happy to get a quick PR in to cover this if that's a good solution.


Remove async-content placeholder and query the correct element

Fixes #1896
Screenshot

@wellcometrust/experience-dev here it is without the whitespace changes: https://github.com/wellcometrust/wellcomecollection.org/pull/1922/files?w=1

Saying that - this is a live bug, so it can go in, but can we come up with a solution to both?

Yep, I'd like to solve the underlying issue, but my chops weren't there to do so yesterday. I'll merge this then have another look.


F* generates invalid Z3 input: wrong # of args passed to fuel_instrumented

F* sometimes generates invalid input to Z3, leading to errors like this one:
test8.fst(62,2-62,4): (Error 276) Unexpected output from Z3: (error "line 138265 column 39: Wrong number of arguments (1) passed to function (declare-fun Test8.t2_to_t1.fuel_instrumented (Fuel Term) Term)")

Here's the file that leads to the above error:
module Test8

open FStar.Sequence.Ambient
open FStar.Sequence.Base

let map_correct (#a: Type) (#b: Type) (f: a -> b) (s: seq a) (s': seq b) : Type0 =
    length s' = length s
  /\ (forall (i: nat{i < length s}). index s' i == f (index s i))

let rec map (#a: Type) (#b: Type) (f: a -> b) (s: seq a) : Tot (s': seq b{map_correct f s s'}) (decreases rank s) =
  if length s = 0 then
    empty
  else
    append (singleton (f (index s 0))) (map f (drop s 1))

let rec map_refine #a #b #p
                   ($f: (x:a { p x } -> b)) //the $ allows type inference at the call site to infer p
                   (s:seq a {forall x. contains s x ==> p x })
  : Tot (s': seq b{length s = length s' /\ (forall (i:nat). i < length s ==> index s' i == f (index s i))}) (decreases rank s)
  = if length s = 0 then
      empty
    else
      let hd = index s 0 in
      let tl = drop s 1 in
      assert (rank tl << rank s);
      append (singleton (f hd)) (map_refine f tl)

#push-options "--__no_positivity"

noeq type t1 =
| T1Empty: t1
| T1Array: (elements: seq t1) -> t1

noeq type t2 =
| T2None: t2
| T2Array: (elements: seq t2) -> t2

#pop-options

let rec t2_to_t1 (x: t2) : Tot t1 (decreases rank x) =
  match x with
  | T2None -> T1Empty
  | T2Array elements ->
      assert (forall element. contains elements element ==> rank element << rank elements);
      T1Array (map_refine t2_to_t1 elements)

let t2_to_t1_equivalent_to_map (x: t2)
  : Lemma (ensures (let value = t2_to_t1 x in
                    match x with
                    | T2Array elements -> value == T1Array (map t2_to_t1 elements)
                    | _ -> True))
          [SMTPat (t2_to_t1 x)] =
  let value = t2_to_t1 x in
  match x with
  | T2Array elements ->
      assert (equal (T1Array?.elements value) (map t2_to_t1 elements))
  | _ -> ()

let lem (x1: t2) (x2: t2)
  : Lemma (requires t2_to_t1 x1 == t2_to_t1 x2)
          (ensures x1 == x2) =
  ()

Thanks for getting it down to this standalone example ... much appreciated!

Minimizing further, seems like any partially applied recursive function in a lemma is encoded incorrectly with fuel arguments, even though we have specific support in the encoding for "fuel instrumented tokens" for partially applied recursive functions. Recording the minimization here ... now for a fix.
module Test8

#push-options "--query_stats"
assume
val seq : Type0 -> Type0

assume
val map (#a: Type)
        (#b: Type)
        (f: a -> b)
        (s: seq a)
  : Tot (seq b)

//mark it recursive, even though it really isn't
let rec t2_to_t1 (x: nat) : Tot nat = 0

let t2_to_t1_equivalent_to_map (x: seq nat) (y:seq nat)
  : Lemma (ensures (map t2_to_t1 x == y))
          [SMTPat (t2_to_t1 0)] //this is just to force the lemma to be SMT encoded
  = admit()

//This is just to trigger an SMT query
let test (x:nat) = assert (x = 0)


Font doesn't render properly

I have installed fonts that supports italics. But when i use neovim, the fonts are not render correctly. Please tell me what is wrong. It does not face this problem before.
INCLUDING CASCADIA CODE

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #9381 for more discussion.
/dup #9381


Add player to an existing project

Is there a problem if I want to add the player to an existing project?

You can do anything you want, as the Unlicense allows basically any usage. However the code is messy and any heavy lifting is done by ExoPlayer which you usually need to learn on how to work with anyway. So I would suggest starting with clean ExoPlayer and probably reusing parts from NewPipe and/or other players.


[composer] disable xdebug on composer runs

[ ] diable xdebug temporary for Composer runs to avoid slow downs

Notes:

zend_extensions can not be disabled from the CLI, when invoking php.exe
its also not possible to override this value by a .user.ini
we need to modify the php.ini or provide a standalone php.ini for composer runs
[ ] lets go with modify: disable xdebug (if it is on) in php.ini before running Composer and return to the state it was before the Composer run

[ ] save old state
[ ] turn off
[ ] return to old state

composer.bat uses the following call:
%~dp0..\php\php.exe -c php.ini-composer %~dp0composer.phar --working-dir=%cd% %*
Its a dead simple one liner with the following intentions behind it:

when the composer.bat file is executed, we are in "\bin\composer"
then php is called in the "\bin\php" folder.

that allows to switch PHP versions by renaming a versionized PHP folder to just "PHP".

with a custom php.ini for composer runs.

the custom ini is needed to disable xdebug
and disabling xdebug is needed for performance reasons during the composer run

php executes the composer.phar
but we set the working dir for composer to the invocation path of the batch file

which is the project folder, were you call composer.bat

May you please give a more detailed, step-by-step explanation on disabling xdebug while running composer? Thus, you will achieve what many other "secret clan" coders aren't able to. I don't know for what reason I couldn't find any thorough, simple, follow-along instruction on completing this task. Not all programmers know all the minor steps, yet. Thanks.

May you please give a more detailed, step-by-step explanation on disabling xdebug while running composer?

Yes, sure! But here i can only repeat myself to answer your question.

Please let me cite my answer from StackOverflow: http://stackoverflow.com/a/33928053/1163786

My suggestion is to write a little invocation helper for running Composer.

The helper is a bash or batch script calling PHP with a custom php.ini, especially configured for Composer. Lets call it: php.ini-composer.
You could copy your current php.ini and adjust it for the Composer run, by removing xdebug or commenting it out, like so: ;zend_extension = "/path/to/my/xdebug.so".
While you are at it: setting memory_limit=-1 is helpful, too.
The full command looks like so on Windows: php.exe -c php.ini-composer composer.phar %*

Then read the step-by-step explanation of what the command does from my post above (https://github.com/WPN-XM/WPN-XM/issues/487#issuecomment-157451028).

I've also provided an implementation (see the commits). You don't even need follow-along instructions. You just need to copy the relevant files (custom php ini and composer.bat).

I hope you get it done. Feel free to ask, if you need additional support.
Best, Jens


Test EC head lookback

It flaked in CI:
 --- FAIL: TestF3WithLookback (10.56s)
    f3_test.go:77:
        	Error Trace:	/home/runner/work/go-f3/go-f3/test/f3_test.go:77
        	Error:      	Condition never satisfied
        	Test:       	TestF3WithLookback

The test normally takes 0.5s so bumping the time is not a solution.


Weird bug in Higher Rank Trait Bounds resolutions

Stumbled on a weird compilation error triggered by sprs "presence"  (??).
The following project fails to build unless extern crate sprs is commented: https://github.com/hhirtz/sprs-hrtb-bug/blob/master/src/lib.rs
Of course the compilation error does not come from this line: it will appear if sprs is used elsewhere in the cargo project. (e.g. you can replace "extern crate" with type Hi = sprs::CsMatView<'static, u32>; to trigger the error).
Happens on
cargo 1.55.0 (32da73ab1 2021-08-23) with sprs 0.11.0 and sprs 0.10.0
cargo 1.49.0 (d00d64df9 2020-12-05) with sprs 0.11.0
cargo 1.42.0 (86334295e 2020-01-31) with sprs 0.10.0

sprs 0.9.0 works fine

https://github.com/vbarrielle/sprs/commit/d2f0da76df51be6e81839b04ed64c5121a2ec640 is the first bad commit

Might be related to https://github.com/rust-lang/rust/issues/85063


[AKS] Add --network-dataplane to az aks update command

Add the --network-dataplane flag to the az aks update command. This will allow customers to update an existing cluster to enable Azure CNI Powered by Cilium

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

AKS

LGTM, however, since the command is currently not practically available, do you really want to merge the PR?

Thanks! I think it's okay to merge it ahead of the rollout, but I'm also okay waiting if that's what we usually do.

Updated to include a live test running in eastus.

@FumingZhang this should be ready for review now, could you please take a look? Thanks!

Queued live test pipeline to validate the change.

LGTM, live test validation passed but CI failed, maybe update the recording file (from pipeline artifact) may fix the issue as I couldn't check detailed error message at this moment.

rebased onto main and used test_aks_migrate_cluster_to_cilium_dataplane.yaml downloaded from the live test pipeline artifacts. Let's see if CI passes...

hmm, still failing. The errors I'm seeing in the build output are:
E           AssertionError: Can't overwrite existing cassette ('/mnt/vss/_work/1/s/src/aks-preview/azext_aks_preview/tests/latest/recordings/test_aks_trustedaccess_rolebinding.yaml') in your current record mode ('once').
E           AssertionError: Can't overwrite existing cassette ('/mnt/vss/_work/1/s/src/aks-preview/azext_aks_preview/tests/latest/recordings/test_aks_create_and_update_outbound_ips.yaml') in your current record mode ('once').

These look unrelated to my changes? Not sure how to fix them, would appreciate any advice.

hmm, still failing. The errors I'm seeing in the build output are:
E           AssertionError: Can't overwrite existing cassette ('/mnt/vss/_work/1/s/src/aks-preview/azext_aks_preview/tests/latest/recordings/test_aks_trustedaccess_rolebinding.yaml') in your current record mode ('once').
E           No match for the request (<Request (GET) [https://management.azure.com/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/MC_clitest000001_cliakstest000001_westus2/providers/Microsoft.Compute/virtualMachineScaleSets?api-version=2023-03-01>](https://management.azure.com/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/MC_clitest000001_cliakstest000001_westus2/providers/Microsoft.Compute/virtualMachineScaleSets?api-version=2023-03-01%3E)) was found.
E           Found 1 similar requests with 1 different matcher(s) :
E
E           1 - (<Request (GET) [https://management.azure.com/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/MC_clitest000001_cliakstest000001_westus2/providers/Microsoft.Compute/virtualMachineScaleSets?api-version=2022-11-01>).](https://management.azure.com/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/MC_clitest000001_cliakstest000001_westus2/providers/Microsoft.Compute/virtualMachineScaleSets?api-version=2022-11-01%3E).)
E           Matchers succeeded : ['method', 'scheme', 'host', 'port', 'path']
E           Matchers failed :
E           _custom_request_query_matcher - assertion failure :
E           None

E           AssertionError: Can't overwrite existing cassette ('/mnt/vss/_work/1/s/src/aks-preview/azext_aks_preview/tests/latest/recordings/test_aks_create_and_update_outbound_ips.yaml') in your current record mode ('once').
E           No match for the request (<Request (PUT) [https://management.azure.com/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/clitest000001/providers/Microsoft.Network/publicIPAddresses/cliakstest000003?api-version=2022-11-01>](https://management.azure.com/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/clitest000001/providers/Microsoft.Network/publicIPAddresses/cliakstest000003?api-version=2022-11-01%3E)) was found.
E           Found 1 similar requests with 1 different matcher(s) :
E
E           1 - (<Request (PUT) [https://management.azure.com/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/clitest000001/providers/Microsoft.Network/publicIPAddresses/cliakstest000003?api-version=2022-05-01>).](https://management.azure.com/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/clitest000001/providers/Microsoft.Network/publicIPAddresses/cliakstest000003?api-version=2022-05-01%3E).)
E           Matchers succeeded : ['method', 'scheme', 'host', 'port', 'path']
E           Matchers failed :
E           _custom_request_query_matcher - assertion failure :
E           None

I think these test cases were expecting api-version=2022-11-01 but got a newer API version instead.
These failures look unrelated to my changes? Not sure how to fix them, would appreciate any advice.

Yeah, some recordings are broken by API version bump of some dependent commands. Fixed in PR #6557. Please rebase from main once the PR is merged.

@zhoxing-ms this PR is ready for review, could you please take a look? Thanks!

@FumingZhang Could you please help review this PR again?

@FumingZhang Could you please help review this PR again?

The change looks good to me :shipit:

@zhoxing-ms @FumingZhang would either of you be able to merge the PR? I don't have permission to merge it. Thanks!


Implicitly convert XML rval to string

Implicitly convert XML rval to string
Add test

Close #2459

@lzybkr could continue code review?

@lzybkr Do you have any other comments or concerns regarding this PR?

@lzybkr Thanks for code review and great comments!


Beryl Gem Missing Block form

Beryl gem has no block item it compresses to.

This issue / recipes will be fixed within the next release of the modpack.


lib doesn't match src?

I noticed some stuff is very different between the two folders, e.g. there's no enableDragSelection function in src, but there is in lib.

The regions plugin file in ./lib includes the WaveSurfer.Region plugin which includes the enableDragSelection you mention. This is not present in the ./src version of the file because there the WaveSurfer.Region plugin is only required.
BTW, the wavesurfer.js main file (i.e. what you get when you require('wavesurfer.js')) is not included in any build file anymore since I couldn't get it to work with the plugin components and the main wrapper component.
But this should definitely be documented better.
Also I think the ./lib directory should be removed from source control.


Issue with "SlackBlockBuilder" in @site/docs/reference/scripts/slack-block-builder.md

Describe the problem
We have a playbook and that playbook contains 3 tasks

SlackBlockBuilder  -> Send notification to slack
GetSlackBlockBuilderResponse  -> Get user response and set it to context data
ParseSlackBlockBuilderResponse  -> parse slack blocks

#Issue01:-
we successfully able to send slack notifications but most of the time we are not able to get the response back on xsoar
#Issue02:-
we are trying to send 100 slack notifications via incident,  we are able to get all notifications on slack but not able to get the response back on xsoar

Page: SlackBlockBuilder
Source: https://github.com/demisto/content/blob/master//Packs/Slack/Scripts/SlackBlockBuilder/README.md

Screenshots

Environment

OS: Linux
Browser: Firefox
Browser Version: 128.0.3 (64-bit)

Suggested fix

Hey @sachinI-metron
I'm closing this issue since this repository is only for documentation. If you have problems with the playbook, please open a support ticket.

Hi @MosheEichler
Thank you for the reply
Could you please tell me where I can create the support ticket?
Thanks

Hey @sachinI-metron
Please reach the support team here https://support.paloaltonetworks.com/Support/Index


Centimeter labels for Crop units

Are there are other areas I missed? Next we need to come up with a good way to respect user unit preferences along with translating units and measurement strings.

This closes #453, but we'll need a new issue for respecting user preferences.
This also temporarily handles #466

Changes Unknown when pulling ad10755878e34ce4c602f1b6c80167b627ddefba on warpling:master into ** on openfarmcc:master**.


Add mergify rule for failed PR checks

Description
Added initial documentation and a rule to address stalled merge queues.  Please verify carefully
Both yamllint and Dashboard configuration editor have validated the configuration syntax
Fixes # (issue)
Type of change
What is it?

[X] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[X] Documentation update
[ ] Tests update
[ ] Refactor

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I run go fmt ./... to check that my code is properly formatted
[ ] I run go vet ./... to check that my code is free of common Go style mistakes

Codecov Report

Merging #1068 (bb12c0b) into main (26791fc) will increase coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1068      +/-   ##
==========================================
+ Coverage   31.53%   31.57%   +0.03%
==========================================
  Files          46       46
  Lines        5600     5600
==========================================
+ Hits         1766     1768       +2
+ Misses       3585     3584       -1
+ Partials      249      248       -1

Impacted Files
Coverage Δ

pkg/services/devices.go
59.48% <0.00%> (+0.39%)
:arrow_up:

Continue to review full report at Codecov.

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

Test results are available in Ibutsu. The test run IDs are:
be722f9d-60cd-4886-abdc-2583e154d94d
fb776934-cdf8-4661-8d0e-e83eea27cba6

@mergifyio unqueue

@mergifyio requeue

@mergifyio refresh


docs(style-guide): fix merge issues

LGTM, @naomiblack please have a look.

pulling now

pulled ... ran it ... LGTM


Delete CONTRIBUTING.md

We don't get external contributions and this file is confusing, inconsistent, noise.
https://trello.com/c/iYNuFHCm/259-remove-contributingmd-files-from-repos

This also seems to be a maintained contributors file, it’s linked to from the readme and contains useful information that’ll be lost.
Also not inconsistent/confusing noise


Unable to open built projects from MRTK RC1

Overview
Downloading a fresh MRTK RC1 project cannot run on HoloLens, and results in errors in the Unity Editor. Built is, however, still "Successful"
Expected Behavior
Built projects should be runnable on HoloLens.
Actual Behavior
Nothing appears on HoloLens. Not even Unity splash screen. However the app is clearly open, as you can "exit" the app once it's open.
Unity errors:
Quite lengthy, and I couldn't make the markup work as intended so you get this pastebin: https://pastebin.com/dubghPDG
And these are the other follow up issues. As you can see the built is claimed successful despite these errors:

Steps to reproduce
We removed OpenVR through the package manager, as we only need the HoloLens working part (and it was kinda frustrating with the constant opening of SteamVR whenever we tried to run the project) aside from that, we kept it pretty vanilla.

Just download MRTK RC1
Make a scene with a cube
Built it for HoloLens x86
Built the project on the HoloLens from visual studio, Release x86
When it says "Ready" nothing shows up. Not even Unity Splash screen.

Unity Editor Version
2018.3.8f1
Mixed Reality Toolkit Release Version
MRTK V2, RC1
Sidenote:
Another thing we discovered in the RC1 is that In order to change scene and have the camera be persistent, we had to add this line to the focusprovider script CreateUIRaycastCamera: uiRaycastCamera.transform.SetParent(GameObject.FindWithTag("MainCamera").transform);
This was not necessary in the beta release, as it was already done for us. Is there a reason for this?

Hi Avalin, thanks for filing the bug! MRTK RC1 needs a newer Windows SDK to build a UWP. You need Windows SDK 18362+.
We are working on updating MRTK to not require the new Windows SDK so you can still build for the old HoloLens.

Duplicate of #3801

Hi Julenka,
Thank you for your reply! I should have probably noted that we did install the Windows 10 Insider Preview OS along with the Windows SDK 18362. We also ran Windows Update alongside this and installed everything it suggested, and finally we also made it through the trouble of installing the Developer Mode packages in this version of Windows which seemingly required some tweaking to work. Despite all the effort, issues remains the same so I'm afraid there's more to it, (or we missed a step, maybe)?
We attempted to build it on an emulator today (Version 10.0.17763.134, as there does not seem to be a version 10.0.18362 available yet), however on this we get an error that says "The emulator is unable to verify that the virtual machine is running", an error that seemingly either has to do with Hyper-V not being activated (it is) or Developer Mode not activated (it also is), but maybe it have to do with deprecation then?
And that's noted, I will post on stackoverflow next time :)

Hi Avalin, I encounter the problem building HoloLens 1 with MRTK ,with Windows SDK 18363, nothing appearing on my HoloLens screen, but when I try audio demos, there actually women sounds(it works), I wonder could we have a talk about the settings of the problems<EMAIL_ADDRESS>

I'm having the same problems, the microphone permissions pop up and that is it.

@hanfengsunshine The issue is caused by leaving WSA Holographic Remoting Suported checked when you build.  After spending hours of testing in Unity and side loading to test, We were able to figure this out.

@hanfengsunshine The issue is caused by leaving WSA Holographic Remoting Suported checked when you build. After spending hours of testing in Unity and side loading to test, We were able to figure this out.

Do you mean I need to tick this WSA Holographic Remoting Supported, like in the attached pic?

Thank you!


Add relay warning for validators

fixes #657
preview:

and it links to this page: https://docs.helium.com/mine-hnt/validators/mainnet/deployment-guide/

great catch! I fixed it in a way that should in theory work for all TabNavs :)


java: Added java examples for some sensors

Signed-off-by: Stefan Andritoiu<EMAIL_ADDRESS>

Thanks a lot, merged!


Reduce DB size by 6.4487x

I was able to compress persistent hyperDB databases by 6.4487x by using pickle and gzip. Note this breaks backward compatibility for legacy hyperDB users.

Incredible work Paras! LGTM.


Clarification needed on "Incentivizing Hackers" section

Upon such an exploit, the validator and delegators will become inactive, HackPunishmentRatio (default 5%) of everyone's atoms will get slashed, and HackRewardRatio (default 5%) of everyone's atoms will get rewarded to the hacker's bounty address. The validator must recover the remaining atoms by using their backup key.

Who is "everyone" here?

i wondered this too. i assume it meant "the validator and the validator's delegators" not "everyone"

Yes, the validator and the validator's delegators.