Buggy Hyprland on fresh installed ArchLinux(not in virtual machine)

I installed ArchLinux, installed yay, installed Hyprland throw the guide on Github repo, installed alacritty and kitty terms, this is the list of issues:

After launching Hyprland in /dev/tty1, screen appears but font is  very small
There is a tip that pressing SUPER+T or SUPER+Enter will open alacritty or kitty. After pressing this keys nothing happened
On default launch with autogenerated configuration Hyprland shows the default wallpaper. I have black screen and thats all.
But I can leave from Hyprland pressing SUPER+M

I have black screen and thats all.

You did not follow the wiki then

After launching Hyprland in /dev/tty1, screen appears but font is very small

Font size for the HyprError is hardcoded, if you have a big monitor that is expected.

There is a tip that pressing SUPER+T or SUPER+Enter will open alacritty or kitty. After pressing this keys nothing happened

Do you have alacritty or kitty installed?
Generally, I'd recommend using the AUR if on Arch Linux. They're well maintained.

Will try with AUR package and update!

You did not follow the wiki then
I followed the wiki, I'm 100% sure.
Font size for the HyprError is hardcoded, if you have a big monitor that is expected
I'm trying to launch Hyperland on Honor Magicbook pro, its screen is 16' with 1920x1080.
Do you have alacritty or kitty installed?
Yes.

Tried to install throw packages from AUR( tried stable and git version)
Both are failed on message

Same for me since a few days.
only manually sudo make install works, but the PKGBUILD fails.

@ThatOneCalculator

do sudo make install then. Also, I'd recommend configuring your monitors prior to launching hyprland, if that happens. Furthermore, see the AUR package and make sure you have all the dependencies

I'd recommend configuring your monitors prior to launching hyprland

What you mean?

Installed with sudo make install, same issue

log and config please

cat ~/.config/hypr/hyprland.conf

########################################################################################
AUTOGENERATED HYPR CONFIG.
PLEASE USE THE CONFIG PROVIDED IN THE GIT REPO /examples/hypr.conf AND EDIT IT,
OR EDIT THIS ONE ACCORDING TO THE WIKI INSTRUCTIONS.
########################################################################################

autogenerated=1 # remove this line to get rid of the warning on top.

monitor=,1920x1080@60,0x0,1

input {
    kb_layout=
    kb_variant=
    kb_model=
    kb_options=
    kb_rules=

    follow_mouse=1
}

general {
    sensitivity=1.0 # for mouse cursor
    main_mod=SUPER

    gaps_in=5
    gaps_out=20
    border_size=2
    col.active_border=0x66ee1111
    col.inactive_border=0x66333333

    apply_sens_to_raw=0 # whether to apply the sensitivity to raw input (e.g. used by games where you aim using your mouse)

    damage_tracking=full # leave it on full unless you hate your GPU and want to make it suffer
}

decoration {
    rounding=10
    blur=1
    blur_size=3 # minimum 1
    blur_passes=1 # minimum 1, more passes = more resource intensive.
    # Your blur "amount" is blur_size * blur_passes, but high blur_size (over around 5-ish) will produce artifacts.
    # if you want heavy blur, you need to up the blur_passes.
    # the more passes, the more you can up the blur_size without noticing artifacts.
}

animations {
    enabled=1
    animation=windows,1,7,default
    animation=borders,1,10,default
    animation=fadein,1,10,default
    animation=workspaces,1,6,default
}

dwindle {
    pseudotile=0 # enable pseudotiling on dwindle
}

# example window rules
# for windows named/classed as abc and xyz
#windowrule=move 69 420,abc
#windowrule=size 420 69,abc
#windowrule=tile,xyz
#windowrule=float,abc
#windowrule=pseudo,abc
#windowrule=monitor 0,xyz

# example binds
bind=SUPER,Q,exec,kitty
bind=SUPER,C,killactive,
bind=SUPER,M,exit,
bind=SUPER,E,exec,dolphin
bind=SUPER,V,togglefloating,
bind=SUPER,R,exec,wofi --show drun -o DP-3
bind=SUPER,P,pseudo,

bind=SUPER,left,movefocus,l
bind=SUPER,right,movefocus,r
bind=SUPER,up,movefocus,u
bind=SUPER,down,movefocus,d

bind=SUPER,1,workspace,1
bind=SUPER,2,workspace,2
bind=SUPER,3,workspace,3
bind=SUPER,4,workspace,4
bind=SUPER,5,workspace,5
bind=SUPER,6,workspace,6
bind=SUPER,7,workspace,7
bind=SUPER,8,workspace,8
bind=SUPER,9,workspace,9
bind=SUPER,0,workspace,10

bind=ALT,1,movetoworkspace,1
bind=ALT,2,movetoworkspace,2
bind=ALT,3,movetoworkspace,3
bind=ALT,4,movetoworkspace,4
bind=ALT,5,movetoworkspace,5
bind=ALT,6,movetoworkspace,6
bind=ALT,7,movetoworkspace,7
bind=ALT,8,movetoworkspace,8
bind=ALT,9,movetoworkspace,9
bind=ALT,0,movetoworkspace,10

coredump info

           PID: 647 (Hyprland)
           UID: 1000 (ryan)
           GID: 1000 (ryan)
        Signal: 11 (SEGV)
     Timestamp: Sun 2022-06-26 19:28:42 MSK (8min ago)
  Command Line: Hyprland
    Executable: /usr/local/bin/Hyprland
 Control Group: /user.slice/user-1000.slice/session-1.scope
          Unit: session-1.scope
         Slice: user-1000.slice
       Session: 1
     Owner UID: 1000 (ryan)
       Boot ID: 01310bef6e9a48a8a64d8e293469636a
    Machine ID: 91cc405d8103487994c26e577626d5fe
      Hostname: MagicBook
       Storage: /var/lib/systemd/coredump/core.Hyprland.1000.01310bef6e9a48a8a64d8e293469636a.647.1656260922000000.zst (present)
     Disk Size: 2.4M
       Message: Process 647 (Hyprland) of user 1000 dumped core.

                Module linux-vdso.so.1 with build-id 0a9dd56f2d1d7d248eeef56d29e78f6fddab09d4
                Module libicudata.so.71 with build-id 4fef196388e678deb881978139e125e20ee2d94d
                Module libicuuc.so.71 with build-id 633fdc0c5385d916571f6140e7a978ad0630ef55
                Module libxml2.so.2 with build-id 8cdf00fa954d9a27f2f184c4d354cb14677446ac
                Module libncursesw.so.6 with build-id b9917757481e6fa6097e2a1f31f5bb5eaf138c4e
                Module libedit.so.0 with build-id 4b0babfcad161c2ad0af6e59e2493258db23a331
                Module libdrm_nouveau.so.2 with build-id b2c524cff6f5c2985e856447f3b043e4fcf0c621
                Module libdrm_amdgpu.so.1 with build-id c640056cb2a0368cf57821d3f0536154248ae845
                Module libelf.so.1 with build-id c09e357a1a3b061bf219bcfb243ca31b175e77fa
                Module libdrm_radeon.so.1 with build-id 8ebce86cd4f588778560618c8861b6d760fcb39a
                Module libsensors.so.5 with build-id dc8b2c1c0d8525411aca188ea3cc3fb86d381d30
                Module libLLVM-13.so with build-id 90a760361bef9d2de117d7e696dad26fc4cb24f4
                Module iris_dri.so with build-id 6640a80b65a3329e89a44a2c2cf51eace1d088ff
                Module libxshmfence.so.1 with build-id d9b3ce4edb0b6a0818bcc57dda020d2da5e3c895
                Module libxcb-sync.so.1 with build-id 13025f6de23a271636ad321c77eda98801e62e8e
                Module libxcb-dri2.so.0 with build-id 7bde0abc84135ae6258a8d1d130864071c2cc327
                Module libX11-xcb.so.1 with build-id f92352eae0a30aea89d11beb22367fa985288925
                Module libglapi.so.0 with build-id 59fe4217d88289c67ebb7bbac4e02aeeaafa7fc7
                Module libEGL_mesa.so.0 with build-id c65800d57ff48ab33d0f38d4c0a1f6e095086ad7
                Module libgpg-error.so.0 with build-id 4738b8a9478177c202cccd64e0eb65d3dea2bfae
                Module libbrotlicommon.so.1 with build-id acfd597a977c8087bb6184383daae2e828a9ce42
                Module libblkid.so.1 with build-id 140694a62d8d4d07c6c320a501f948dd1b389d73
                Module liblz4.so.1 with build-id e63600ab23b2f6997f42fac2fa56e1f02ce159a1
                Module libzstd.so.1 with build-id ab54c2881f53ab314e134f3e08c76d504376dd5d
                Module liblzma.so.5 with build-id 28b40c7af8098a66af6ee093b6986b91cad7694d
                Module libgcrypt.so.20 with build-id 8bf3cb884124273640de797a3e77d86c98434ea4
                Module libcap.so.2 with build-id 21b00ab76bb16fde56fd741f07233c78069f0579
                Module libgudev-1.0.so.0 with build-id 460465b63a086d945124662363191903c0002793
                Module libbrotlidec.so.1 with build-id 66c54e9301f7e102ecc1d88547e5f0e8a056fe22
                Module libbz2.so.1.0 with build-id 919597c477c9b2cb9cdbb7745ed6494ac0e6da60
                Module libpthread.so.0 with build-id 95ae4f30a6f12ccbff645d30f8e1a3ee23ec7d36
                Module libdatrie.so.1 with build-id 6fe3b6ece2c8e7d11869fa051375128d8f808f58
                Module libmount.so.1 with build-id 4436aeea0cd8c01b5a77969e0531184f8b3513ce
                Module libgmodule-2.0.so.0 with build-id 3b42a54783f0665e688370b6c57238c05822c50e
                Module libsystemd.so.0 with build-id a220b34e873e29bb116d88be0bf11fac7089ef4d
                Module libexpat.so.1 with build-id 113bb5a3e9ad856801bfcfc029102c9bdc13d67e
                Module libXdmcp.so.6 with build-id d864159ab0008415667db8d5f251696d75c90df2
                Module libXau.so.6 with build-id 60db1eac70f819bea9d4c366603c1583067510b4
                Module libwacom.so.9 with build-id 1fc3438938e7017596beb2e3483ce3af72c4f492
                Module libevdev.so.2 with build-id 09eb82a0dfca98325f54b3918875cff09a5c1428
                Module libmtdev.so.1 with build-id 862cf8d5b0a0dd4d4d225e17f54be93ab9c3b34e
                Module libXrender.so.1 with build-id 42e386d2acf3cde61081959d9671ca74acfb3edc
                Module libXext.so.6 with build-id 17beadf1cb40d41ab36629db3b4eed74110678a7
                Module libX11.so.6 with build-id 310f8f1b8d7457d326407e0eb794353c62769b73
                Module libpng16.so.16 with build-id 2dc0bce07f199bf983c07a05fb95a6f4af83a9b3
                Module libz.so.1 with build-id fefe3219a96d682ec98fcfb78866b8594298b5a2
                Module libgraphite2.so.3 with build-id ce58945ebb55b86d3a4e717b6eae29efc4720d8e
                Module libfreetype.so.6 with build-id f89dd5502e75aca28fb5c3ccd0dbd26fe822bfef
                Module libpcre.so.1 with build-id 845483dd0acba86de9f0313102bebbaf3ce52767
                Module libthai.so.0 with build-id a7ac5010b4275c49308021200d23690533952702
                Module libfribidi.so.0 with build-id fe9f35ac2a0074108c8306c517793f7279bd9b37
                Module libgio-2.0.so.0 with build-id bc795ed533f1b5c20cdc8600cf855216d692087f
                Module libfontconfig.so.1 with build-id 36be6951b8c1e42a7dd05684a37400fc8ef9147c
                Module libpangoft2-1.0.so.0 with build-id c2c09f789578900f61b7fca4a4311d8b94d9a750
                Module libffi.so.8 with build-id f0a9586cf0f42d2b9971bd1065ca3a6b19f4a2c2
                Module libGLdispatch.so.0 with build-id de981c020bd9dbdc159b11f4a2a541310cc3b8d5
                Module ld-linux-x86-64.so.2 with build-id 0effd0e43efa4468d3c31871c93af0b7f3005673
                Module libxcb-errors.so.0 with build-id 0d6ee255fc30b6a86856b9f1a96491f12a1cacaf
                Module libxcb-res.so.0 with build-id cd3dbd6dd9e412a002d1be5ae0ec0d85650542ba
                Module libxcb-icccm.so.4 with build-id 5eb9288df14c7f50af1e8db26c37e19d78bf0978
                Module libxcb-composite.so.0 with build-id e8b69e2806d928f66445390cc50ab33a0b98bef0
                Module libseat.so.1 with build-id 51f74c96a4dd3748925954d1cc5fc6c52f051866
                Module libxcb-xinput.so.0 with build-id 409ee697e2b16243bf1fc6429e672f2359033388
                Module libxcb-xfixes.so.0 with build-id e231a68d00ee4cfa12a2c31e755a9e2c1e7be450
                Module libxcb-shm.so.0 with build-id 828fec4d856e2710e732ea8d92c3f250c807b1c2
                Module libxcb-render-util.so.0 with build-id 32609134bf1b73183d07a66f6bd65c94b4542460
                Module libxcb-render.so.0 with build-id b1ca498d665807ab0ccdafbe8070853efd058173
                Module libxcb-present.so.0 with build-id 8ed389d9cd6ad7110fbb00c93b32e0efaa71a6b1
                Module libxcb-dri3.so.0 with build-id 088c750254cc139e7d62b8a3fc7795a138447ccf
                Module libvulkan.so.1 with build-id 2ce03c12244f56834b41c55da5d48a4adfa1069a
                Module libgbm.so.1 with build-id 2d19445ada22baa929dacc575cc1f627650f9009
                Module libudev.so.1 with build-id 541e6841430a5ee36134325ec0ce669c2c0b9053
                Module libc.so.6 with build-id 60df1df31f02a7b23da83e8ef923359885b81492
                Module libgcc_s.so.1 with build-id 0e3de903950e35ae59a5de8c00b1817a4a71ca01
                Module libm.so.6 with build-id 1b7296ef9fd806e47060788389293c824b09ad72
                Module libstdc++.so.6 with build-id b3eaebcb5369487562e52dd8d016c9cd77f80c54
                Module libxcb.so.1 with build-id 13d677412a71468381b11092915d231f664d18d3
                Module libinput.so.10 with build-id 9de57b91e0d1d09e53606692e2c51c8b31d3dfe1
                Module libxkbcommon.so.0 with build-id 6cf66eead3fcc20fe5df10162bfbcdcdc8b2a183
                Module libEGL.so.1 with build-id 30b30de54f2f848a7b8bed469349c9a7ab1b7c22
                Module libdrm.so.2 with build-id 658072e933ab3de11aea1408bdf4e72dd6e80255
                Module libcairo.so.2 with build-id a222d042e56108d2786ece7bf291b56ba2069591
                Module libharfbuzz.so.0 with build-id c58fe082cbde02fc176e3c3663a6d81386eb5027
                Module libglib-2.0.so.0 with build-id f1d15261ce1317b9003a1f0957d5a528d063f630
                Module libgobject-2.0.so.0 with build-id a7dfc5c24acdbd0bcc40e3a427f917f679eef0d1
                Module libpango-1.0.so.0 with build-id 7e27c1e46a1d958f6b16e1ba199f8bdb3f100566
                Module libpangocairo-1.0.so.0 with build-id b65f507d9e33adfbd19369acef5e5a0a2422c6d1
                Module libwayland-cursor.so.0 with build-id 647d92328111682fb15bff1c20a4c9368414857c
                Module libwayland-client.so.0 with build-id 95e7368b400dd57e3db2a5c385de71c7dca08879
                Module libwayland-server.so.0 with build-id 5526cec43774a83c7ab8c7ff820eea8b28880d51
                Module libGLESv2.so.2 with build-id ecba6a192965463cb000c68b97e51a1c760457de
                Module libOpenGL.so.0 with build-id b674d36fbce1bed29b54247cf4e25e0f3c64ff13
                Module libpixman-1.so.0 with build-id d2170a3ac106c2a68597bf7910ab04b1cdd69c14
                Module libwlroots.so.11032 with build-id 4f626f4b3f5c01fc122bce8930143573b7e4de90
                Module Hyprland with build-id 0431eaa4efa392580cf2c95e7a7ae754e9b273b0
                Stack trace of thread 647:
                #0  0x000055c44875bded _ZN6Events23listener_monitorDestroyEPvS0_ (Hyprland + 0x7dded)
                #1  0x000055c44876eccb _Z13handleWrappedP11wl_listenerPv (Hyprland + 0x90ccb)
                #2  0x00007fbe4a23c04c wlr_signal_emit_safe (libwlroots.so.11032 + 0x9404c)
                #3  0x00007fbe4a2036b2 wlr_output_destroy (libwlroots.so.11032 + 0x5b6b2)
                #4  0x00007fbe4a1ed8fd destroy_drm_connector (libwlroots.so.11032 + 0x458fd)
                #5  0x00007fbe4a1e9fe5 backend_destroy.part.0 (libwlroots.so.11032 + 0x41fe5)
                #6  0x00007fbe4a1f7735 handle_display_destroy (libwlroots.so.11032 + 0x4f735)
                #7  0x00007fbe4a0b2137 wl_display_destroy (libwayland-server.so.0 + 0xc137)
                #8  0x000055c448719347 _ZN11CCompositor11cleanupExitEv.part.0 (Hyprland + 0x3b347)
                #9  0x000055c448781e10 _ZN15CKeybindManager12exitHyprlandENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (Hyprland + 0xa3e10)
                #10 0x000055c44878a112 _ZNSt17_Function_handlerIFvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEEPS6_E9_M_invokeERKSt9_Any_dataOS5_ (Hyprland + 0xac112)
                #11 0x000055c4487848b7 _ZN15CKeybindManager14handleKeybindsERKjS1_ (Hyprland + 0xa68b7)
                #12 0x000055c448792526 _ZN13CInputManager13onKeyboardKeyEP22wlr_keyboard_key_eventP9SKeyboard (Hyprland + 0xb4526)
                #13 0x000055c44876eccb _Z13handleWrappedP11wl_listenerPv (Hyprland + 0x90ccb)
                #14 0x00007fbe4a23c04c wlr_signal_emit_safe (libwlroots.so.11032 + 0x9404c)
                #15 0x00007fbe4a2234f0 wlr_keyboard_notify_key (libwlroots.so.11032 + 0x7b4f0)
                #16 0x00007fbe4a1f2571 handle_keyboard_key (libwlroots.so.11032 + 0x4a571)
                #17 0x00007fbe4a1f169b handle_libinput_readable (libwlroots.so.11032 + 0x4969b)
                #18 0x00007fbe4a0b184a wl_event_loop_dispatch (libwayland-server.so.0 + 0xb84a)
                #19 0x00007fbe4a0b2047 wl_display_run (libwayland-server.so.0 + 0xc047)
                #20 0x000055c44870d52a main (Hyprland + 0x2f52a)
                #21 0x00007fbe49429290 n/a (libc.so.6 + 0x29290)
                #22 0x00007fbe4942934a __libc_start_main (libc.so.6 + 0x2934a)
                #23 0x000055c448719095 _start (Hyprland + 0x3b095)

                Stack trace of thread 651:
                #0  0x00007fbe49489119 n/a (libc.so.6 + 0x89119)
                #1  0x00007fbe4948b920 pthread_cond_wait (libc.so.6 + 0x8b920)
                #2  0x00007fbe464b292c n/a (iris_dri.so + 0xb292c)
                #3  0x00007fbe464ac02c n/a (iris_dri.so + 0xac02c)
                #4  0x00007fbe4948c54d n/a (libc.so.6 + 0x8c54d)
                #5  0x00007fbe49511874 __clone (libc.so.6 + 0x111874)

                Stack trace of thread 654:
                #0  0x00007fbe49489119 n/a (libc.so.6 + 0x89119)
                #1  0x00007fbe4948b920 pthread_cond_wait (libc.so.6 + 0x8b920)
                #2  0x00007fbe464b292c n/a (iris_dri.so + 0xb292c)
                #3  0x00007fbe464ac02c n/a (iris_dri.so + 0xac02c)
                #4  0x00007fbe4948c54d n/a (libc.so.6 + 0x8c54d)
                #5  0x00007fbe49511874 __clone (libc.so.6 + 0x111874)

                Stack trace of thread 655:
                #0  0x00007fbe49489119 n/a (libc.so.6 + 0x89119)
                #1  0x00007fbe4948b920 pthread_cond_wait (libc.so.6 + 0x8b920)
                #2  0x00007fbe464b292c n/a (iris_dri.so + 0xb292c)
                #3  0x00007fbe464ac02c n/a (iris_dri.so + 0xac02c)
                #4  0x00007fbe4948c54d n/a (libc.so.6 + 0x8c54d)
                #5  0x00007fbe49511874 __clone (libc.so.6 + 0x111874)

                Stack trace of thread 653:
                #0  0x00007fbe49489119 n/a (libc.so.6 + 0x89119)
                #1  0x00007fbe4948b920 pthread_cond_wait (libc.so.6 + 0x8b920)
                #2  0x00007fbe464b292c n/a (iris_dri.so + 0xb292c)
                #3  0x00007fbe464ac02c n/a (iris_dri.so + 0xac02c)
                #4  0x00007fbe4948c54d n/a (libc.so.6 + 0x8c54d)
                #5  0x00007fbe49511874 __clone (libc.so.6 + 0x111874)

                Stack trace of thread 661:
                #0  0x00007fbe49489119 n/a (libc.so.6 + 0x89119)
                #1  0x00007fbe4948b920 pthread_cond_wait (libc.so.6 + 0x8b920)
                #2  0x00007fbe464b292c n/a (iris_dri.so + 0xb292c)
                #3  0x00007fbe464ac02c n/a (iris_dri.so + 0xac02c)
                #4  0x00007fbe4948c54d n/a (libc.so.6 + 0x8c54d)
                #5  0x00007fbe49511874 __clone (libc.so.6 + 0x111874)

                Stack trace of thread 656:
                #0  0x00007fbe49489119 n/a (libc.so.6 + 0x89119)
                #1  0x00007fbe4948b920 pthread_cond_wait (libc.so.6 + 0x8b920)
                #2  0x00007fbe464b292c n/a (iris_dri.so + 0xb292c)
                #3  0x00007fbe464ac02c n/a (iris_dri.so + 0xac02c)
                #4  0x00007fbe4948c54d n/a (libc.so.6 + 0x8c54d)
                #5  0x00007fbe49511874 __clone (libc.so.6 + 0x111874)

                Stack trace of thread 660:
                #0  0x00007fbe49489119 n/a (libc.so.6 + 0x89119)
                #1  0x00007fbe4948b920 pthread_cond_wait (libc.so.6 + 0x8b920)
                #2  0x00007fbe464b292c n/a (iris_dri.so + 0xb292c)
                #3  0x00007fbe464ac02c n/a (iris_dri.so + 0xac02c)
                #4  0x00007fbe4948c54d n/a (libc.so.6 + 0x8c54d)
                #5  0x00007fbe49511874 __clone (libc.so.6 + 0x111874)

                Stack trace of thread 657:
                #0  0x00007fbe49489119 n/a (libc.so.6 + 0x89119)
                #1  0x00007fbe4948b920 pthread_cond_wait (libc.so.6 + 0x8b920)
                #2  0x00007fbe464b292c n/a (iris_dri.so + 0xb292c)
                #3  0x00007fbe464ac02c n/a (iris_dri.so + 0xac02c)
                #4  0x00007fbe4948c54d n/a (libc.so.6 + 0x8c54d)
                #5  0x00007fbe49511874 __clone (libc.so.6 + 0x111874)

                Stack trace of thread 659:
                #0  0x00007fbe49489119 n/a (libc.so.6 + 0x89119)
                #1  0x00007fbe4948b920 pthread_cond_wait (libc.so.6 + 0x8b920)
                #2  0x00007fbe464b292c n/a (iris_dri.so + 0xb292c)
                #3  0x00007fbe464ac02c n/a (iris_dri.so + 0xac02c)
                #4  0x00007fbe4948c54d n/a (libc.so.6 + 0x8c54d)
                #5  0x00007fbe49511874 __clone (libc.so.6 + 0x111874)

                Stack trace of thread 667:
                #0  0x00007fbe494d7fd5 clock_nanosleep (libc.so.6 + 0xd7fd5)
                #1  0x00007fbe494dcb97 __nanosleep (libc.so.6 + 0xdcb97)
                #2  0x000055c448780805 _ZZN13CEventManager11startThreadEvENKUlvE_clEv (Hyprland + 0xa2805)
                #3  0x00007fbe498d6183 execute_native_thread_routine (libstdc++.so.6 + 0xd6183)
                #4  0x00007fbe4948c54d n/a (libc.so.6 + 0x8c54d)
                #5  0x00007fbe49511874 __clone (libc.so.6 + 0x111874)

                Stack trace of thread 665:
                #0  0x00007fbe494d7fd5 clock_nanosleep (libc.so.6 + 0xd7fd5)
                #1  0x00007fbe494dcb97 __nanosleep (libc.so.6 + 0xdcb97)
                #2  0x000055c44878b717 _ZN14CThreadManager6handleEv (Hyprland + 0xad717)
                #3  0x000055c44878b78d _ZNSt6thread11_State_implINS_8_InvokerISt5tupleIJZN14CThreadManagerC4EvEUlvE_EEEEE6_M_runEv (Hyprland + 0xad78d)
                #4  0x00007fbe498d6183 execute_native_thread_routine (libstdc++.so.6 + 0xd6183)
                #5  0x00007fbe4948c54d n/a (libc.so.6 + 0x8c54d)
                #6  0x00007fbe49511874 __clone (libc.so.6 + 0x111874)

                Stack trace of thread 664:
                #0  0x00007fbe49489119 n/a (libc.so.6 + 0x89119)
                #1  0x00007fbe4948b920 pthread_cond_wait (libc.so.6 + 0x8b920)
                #2  0x00007fbe464b292c n/a (iris_dri.so + 0xb292c)
                #3  0x00007fbe464ac02c n/a (iris_dri.so + 0xac02c)
                #4  0x00007fbe4948c54d n/a (libc.so.6 + 0x8c54d)
                #5  0x00007fbe49511874 __clone (libc.so.6 + 0x111874)

                Stack trace of thread 658:
                #0  0x00007fbe49489119 n/a (libc.so.6 + 0x89119)
                #1  0x00007fbe4948b920 pthread_cond_wait (libc.so.6 + 0x8b920)
                #2  0x00007fbe464b292c n/a (iris_dri.so + 0xb292c)
                #3  0x00007fbe464ac02c n/a (iris_dri.so + 0xac02c)
                #4  0x00007fbe4948c54d n/a (libc.so.6 + 0x8c54d)
                #5  0x00007fbe49511874 __clone (libc.so.6 + 0x111874)

                Stack trace of thread 663:
                #0  0x00007fbe49489119 n/a (libc.so.6 + 0x89119)
                #1  0x00007fbe4948b920 pthread_cond_wait (libc.so.6 + 0x8b920)
                #2  0x00007fbe464b292c n/a (iris_dri.so + 0xb292c)
                #3  0x00007fbe464ac02c n/a (iris_dri.so + 0xac02c)
                #4  0x00007fbe4948c54d n/a (libc.so.6 + 0x8c54d)
                #5  0x00007fbe49511874 __clone (libc.so.6 + 0x111874)

                Stack trace of thread 662:
                #0  0x00007fbe49489119 n/a (libc.so.6 + 0x89119)
                #1  0x00007fbe4948b920 pthread_cond_wait (libc.so.6 + 0x8b920)
                #2  0x00007fbe464b292c n/a (iris_dri.so + 0xb292c)
                #3  0x00007fbe464ac02c n/a (iris_dri.so + 0xac02c)
                #4  0x00007fbe4948c54d n/a (libc.so.6 + 0x8c54d)
                #5  0x00007fbe49511874 __clone (libc.so.6 + 0x111874)

                Stack trace of thread 650:
                #0  0x00007fbe49489119 n/a (libc.so.6 + 0x89119)
                #1  0x00007fbe4948b920 pthread_cond_wait (libc.so.6 + 0x8b920)
                #2  0x00007fbe464b292c n/a (iris_dri.so + 0xb292c)
                #3  0x00007fbe464ac02c n/a (iris_dri.so + 0xac02c)
                #4  0x00007fbe4948c54d n/a (libc.so.6 + 0x8c54d)
                #5  0x00007fbe49511874 __clone (libc.so.6 + 0x111874)

                Stack trace of thread 666:
                #0  0x00007fbe4951321f accept (libc.so.6 + 0x11321f)
                #1  0x000055c44874ff53 _ZZN7HyprCtl18startHyprCtlSocketEvENKUlvE_clEv.constprop.0 (Hyprland + 0x71f53)
                #2  0x00007fbe498d6183 execute_native_thread_routine (libstdc++.so.6 + 0xd6183)
                #3  0x00007fbe4948c54d n/a (libc.so.6 + 0x8c54d)
                #4  0x00007fbe49511874 __clone (libc.so.6 + 0x111874)

                Stack trace of thread 652:
                #0  0x00007fbe49489119 n/a (libc.so.6 + 0x89119)
                #1  0x00007fbe4948b920 pthread_cond_wait (libc.so.6 + 0x8b920)
                #2  0x00007fbe464b292c n/a (iris_dri.so + 0xb292c)
                #3  0x00007fbe464ac02c n/a (iris_dri.so + 0xac02c)
                #4  0x00007fbe4948c54d n/a (libc.so.6 + 0x8c54d)
                #5  0x00007fbe49511874 __clone (libc.so.6 + 0x111874)
                ELF object binary architecture: AMD x86-64

hyprland log, not the coredump. https://github.com/hyprwm/Hyprland/blob/main/docs/ISSUE_GUIDELINES.md#obtaining-the-hyprland-log

[LOG] Hyprland init finished.
[LOG] Creating the CHyprError!
[LOG] Creating the KeybindManager!
[LOG] Creating the AnimationManager!
[LOG] Created a bezier curve, baked 200 points, mem usage: 3.20kB, time to bake: 19.25µs. Estimated average calc time: 0.00µs.
[LOG] Creating the ConfigManager!
[LOG] Creating the ThreadManager!
[LOG] Creating the InputManager!
[LOG] Creating the CHyprOpenGLImpl!
[LOG] Creating the Hypr OpenGL Renderer!
[LOG] Using: OpenGL ES 3.2 Mesa 22.1.2
[LOG] Vendor: Intel
[LOG] Renderer: Mesa Intel(R) UHD Graphics (CML GT2)
[LOG] Reloading the config!
[LOG] Supported extensions size: 149
[LOG] Created a bezier curve, baked 200 points, mem usage: 3.20kB, time to bake: 9.93µs. Estimated average calc time: 0.00µs.
[LOG] Hypr socket started at /tmp/hypr/_1656261911/.socket.sock
[LOG] Shaders initialized successfully.
[LOG] Creating the HyprRenderer!
[LOG] Creating the XWaylandManager!
[LOG] Registered signal for owner 23253fd0: 23254008 -> 2162e540 (owner: XWayland Manager)
[LOG] Registered signal for owner 23253fd0: 23254018 -> 2162e520 (owner: XWayland Manager)
[LOG] CHyprXWaylandManager started on display :0
[LOG] Creating the LayoutManager!
[LOG] Creating the EventManager!
[LOG] Creating the HyprDebugOverlay!
[LOG] Registered signal for owner 2294d750: 2294d778 -> 2162e0d0 (owner: Backend)
[LOG] Registered signal for owner 23136430: 23136480 -> 2162e090 (owner: XDG Shell)
[LOG] Registered signal for owner 231364b0: 231364c8 -> 2162e070 (owner: WLRCursor)
[LOG] Registered signal for owner 231364b0: 231364d8 -> 2162e050 (owner: WLRCursor)
[LOG] Registered signal for owner 231364b0: 231364e8 -> 2162e030 (owner: WLRCursor)
[LOG] Registered signal for owner 231364b0: 231364f8 -> 2162e010 (owner: WLRCursor)
[LOG] Registered signal for owner 231364b0: 23136508 -> 2162dff0 (owner: WLRCursor)
[LOG] Registered signal for owner 2294d750: 2294d768 -> 2162dfd0 (owner: Backend)
[LOG] Registered signal for owner 2294d1c0: 23139e48 -> 2162df70 (owner: Seat)
[LOG] Registered signal for owner 2294d1c0: 23139e58 -> 2162df50 (owner: Seat)
[LOG] Hypr socket 2 started at /tmp/hypr/_1656261911/.socket2.sock
[LOG] Registered signal for owner 2294d1c0: 23139e98 -> 2162def0 (owner: Seat)
[LOG] Registered signal for owner 2294d1c0: 23139ea8 -> 2162ded0 (owner: Seat)
[LOG] Registered signal for owner 23138060: 23138080 -> 2162e0b0 (owner: LayerShell)
[LOG] Registered signal for owner 231263f0: 23126410 -> 2162e0f0 (owner: OutputLayout)
[LOG] Registered signal for owner 2313a1a0: 2313a1d8 -> 2162df30 (owner: OutputMgr)
[LOG] Registered signal for owner 2313a1a0: 2313a1e8 -> 2162df10 (owner: OutputMgr)
[LOG] Registered signal for owner 2313a280: 2313a2b0 -> 2162deb0 (owner: InhibitMgr)
[LOG] Registered signal for owner 2313a280: 2313a2c0 -> 2162de90 (owner: InhibitMgr)
[LOG] Registered signal for owner 2313a4c0: 2313a4d8 -> 2162df90 (owner: PointerConstraints)
[LOG] Registered signal for owner 2313a000: 2313a030 -> 2162de70 (owner: XDGDecoMgr)
[LOG] Registered signal for owner 2313a6c0: 2313a6f0 -> 2162dfb0 (owner: VirtPtrMgr)
[LOG] Registered signal for owner 22a4ccf0: 22a4cd00 -> 2162de50 (owner: WLRRenderer)
[LOG] Running on WAYLAND_DISPLAY: wayland-0
[LOG] Attached a keyboard with name Power Button
[LOG] Registered signal for owner 232b8a10: 2330db78 -> 232b8a18 (owner: Keyboard)
[LOG] Registered signal for owner 232b8a10: 2330db68 -> 232b8a80 (owner: Keyboard)
[LOG] Registered signal for owner 232b8a10: 2330da48 -> 232b8ae8 (owner: Keyboard)
[LOG] Attempting to create a keymap for layout  with variant  (rules: , model: , options: )
[LOG] Set the keyboard layout to  and variant to  for keyboard "Power Button"
[LOG] New keyboard created, pointers Hypr: 232b8a10 and WLR: 2330da28
[LOG] Attached a keyboard with name Video Bus
[LOG] Registered signal for owner 232acca0: 233144e8 -> 232acca8 (owner: Keyboard)
[LOG] Registered signal for owner 232acca0: 233144d8 -> 232acd10 (owner: Keyboard)
[LOG] Registered signal for owner 232acca0: 233143b8 -> 232acd78 (owner: Keyboard)
[LOG] Attempting to create a keymap for layout  with variant  (rules: , model: , options: )
[LOG] Set the keyboard layout to  and variant to  for keyboard "Video Bus"
[LOG] New keyboard created, pointers Hypr: 232acca0 and WLR: 23314398
[LOG] Attached a keyboard with name Video Bus
[LOG] Registered signal for owner 23317860: 23375948 -> 23317868 (owner: Keyboard)
[LOG] Registered signal for owner 23317860: 23375938 -> 233178d0 (owner: Keyboard)
[LOG] Registered signal for owner 23317860: 23375818 -> 23317938 (owner: Keyboard)
[LOG] Attempting to create a keymap for layout  with variant  (rules: , model: , options: )
[LOG] Set the keyboard layout to  and variant to  for keyboard "Video Bus"
[LOG] New keyboard created, pointers Hypr: 23317860 and WLR: 233757f8
[LOG] Attached a keyboard with name Power Button
[LOG] Registered signal for owner 23376b90: 2339b638 -> 23376b98 (owner: Keyboard)
[LOG] Registered signal for owner 23376b90: 2339b628 -> 23376c00 (owner: Keyboard)
[LOG] Registered signal for owner 23376b90: 2339b508 -> 23376c68 (owner: Keyboard)
[LOG] Attempting to create a keymap for layout  with variant  (rules: , model: , options: )
[LOG] Set the keyboard layout to  and variant to  for keyboard "Power Button"
[LOG] New keyboard created, pointers Hypr: 23376b90 and WLR: 2339b4e8
[WARN] Unrecognized input device plugged in: Lid Switch
[LOG] Attached a mouse with name Logitech Wireless Mouse
[LOG] Registered signal for owner 23108710: 233d7fc0 -> 231087a8 (owner: Mouse)
[LOG] New mouse created, pointer WLR: 233d7fa0
[LOG] Attached a keyboard with name ov9734_azurewave_camera: ov9734
[LOG] Registered signal for owner 2339c880: 233d8738 -> 2339c888 (owner: Keyboard)
[LOG] Registered signal for owner 2339c880: 233d8728 -> 2339c8f0 (owner: Keyboard)
[LOG] Registered signal for owner 2339c880: 233d8608 -> 2339c958 (owner: Keyboard)
[LOG] Attempting to create a keymap for layout  with variant  (rules: , model: , options: )
[LOG] Set the keyboard layout to  and variant to  for keyboard "ov9734_azurewave_camera: ov9734"
[LOG] New keyboard created, pointers Hypr: 2339c880 and WLR: 233d85e8
[LOG] Attached a mouse with name ELAN2204:00 04F3:30F5 Mouse
[LOG] Registered signal for owner 233e5f60: 23412cc0 -> 233e5ff8 (owner: Mouse)
[LOG] New mouse created, pointer WLR: 23412ca0
[LOG] Attached a mouse with name ELAN2204:00 04F3:30F5 Touchpad
[LOG] Registered signal for owner 231004c0: 23413490 -> 23100558 (owner: Mouse)
[LOG] New mouse created, pointer WLR: 23413470
[LOG] Attached a keyboard with name Huawei WMI hotkeys
[LOG] Registered signal for owner 233b0e00: 23413c08 -> 233b0e08 (owner: Keyboard)
[LOG] Registered signal for owner 233b0e00: 23413bf8 -> 233b0e70 (owner: Keyboard)
[LOG] Registered signal for owner 233b0e00: 23413ad8 -> 233b0ed8 (owner: Keyboard)
[LOG] Attempting to create a keymap for layout  with variant  (rules: , model: , options: )
[LOG] Set the keyboard layout to  and variant to  for keyboard "Huawei WMI hotkeys"
[LOG] New keyboard created, pointers Hypr: 233b0e00 and WLR: 23413ab8
[LOG] Attached a keyboard with name AT Translated Set 2 keyboard
[LOG] Registered signal for owner 233eb580: 2344d7f8 -> 233eb588 (owner: Keyboard)
[LOG] Registered signal for owner 233eb580: 2344d7e8 -> 233eb5f0 (owner: Keyboard)
[LOG] Registered signal for owner 233eb580: 2344d6c8 -> 233eb658 (owner: Keyboard)
[LOG] Attempting to create a keymap for layout  with variant  (rules: , model: , options: )
[LOG] Set the keyboard layout to  and variant to  for keyboard "AT Translated Set 2 keyboard"
[LOG] New keyboard created, pointers Hypr: 233eb580 and WLR: 2344d6a8
[WARN] No rule found for eDP-1, trying to use the first.
[LOG] Registered signal for owner 232b6650: 23486820 -> 232b6778 (owner: )
[LOG] Registered signal for owner 232b6650: 234868c0 -> 232b67e0 (owner: )
[LOG] Applying monitor rule for eDP-1
[LOG] Monitor eDP-1: requested<EMAIL_ADDRESS>found available mode: 1920x1080@60008mHz, applying.
[LOG] Monitor eDP-1 -> destroyed all render data
[LOG] Monitor eDP-1 layers arranged: reserved: 0.000000 0.000000 0.000000 0.000000
[LOG] Added new monitor with name eDP-1 at 0,0 with size 1920x1080, pointer 234866e0
[LOG] New monitor: WORKSPACEID 1, exists: 0
[LOG] Hyprland is ready, running the event loop!

[LOG] Callback 8b3c7f80 -> 233eb580, Keyboard removed.
[LOG] Callback 8b3c7f80 -> 233eb580, Keyboard removed.
[LOG] Destroyed keyboard 233eb580
[LOG] Callback 8b3c7f80 -> 233b0e00, Keyboard removed.
[LOG] Callback 8b3c7f80 -> 233b0e00, Keyboard removed.
[LOG] Callback 8b3c7f80 -> 233b0e00, Keyboard removed.
[LOG] Destroyed keyboard 233b0e00
[LOG] Callback 8b3c7f80 -> 231004c0, Mouse removed.
[LOG] Callback 8b3c7f80 -> 233e5f60, Mouse removed.
[LOG] Callback 8b3c7f80 -> 2339c880, Keyboard removed.
[LOG] Callback 8b3c7f80 -> 2339c880, Keyboard removed.
[LOG] Callback 8b3c7f80 -> 2339c880, Keyboard removed.
[LOG] Destroyed keyboard 2339c880
[LOG] Callback 8b3c7f80 -> 23108710, Mouse removed.
[LOG] Callback 8b3c7f80 -> 23376b90, Keyboard removed.
[LOG] Callback 8b3c7f80 -> 23376b90, Keyboard removed.
[LOG] Callback 8b3c7f80 -> 23376b90, Keyboard removed.
[LOG] Destroyed keyboard 23376b90
[LOG] Callback 8b3c7f80 -> 23317860, Keyboard removed.
[LOG] Callback 8b3c7f80 -> 23317860, Keyboard removed.
[LOG] Callback 8b3c7f80 -> 23317860, Keyboard removed.
[LOG] Destroyed keyboard 23317860
[LOG] Callback 8b3c7f80 -> 232acca0, Keyboard removed.
[LOG] Callback 8b3c7f80 -> 232acca0, Keyboard removed.
[LOG] Callback 8b3c7f80 -> 232acca0, Keyboard removed.
[LOG] Destroyed keyboard 232acca0
[LOG] Callback 8b3c7f80 -> 232b8a10, Keyboard removed.
[LOG] Callback 8b3c7f80 -> 232b8a10, Keyboard removed.
[LOG] Callback 8b3c7f80 -> 232b8a10, Keyboard removed.
[LOG] Destroyed keyboard 232b8a10

you're not using the latest commit I am afraid, and if this is an old laptop, you might want to use the legacyrenderer build (see the wiki)

you're not using the latest commit I am afraid

$ git pull

Already up to date

if this is an old laptop
This notebook was released this year, Intel i5-10210U and NVIDIA Geforce MX350. I don't think that it is old :)

hm, weird.

do you have all of these?
Also, try configuring your monitor:
monitor=eDP-1,1920x1080@60,0x0,1

do you have all of these?

Checked, everything is installed

Also, try configuring your monitor

Done, but without progress

out of ideas then. Kitty is clearly attempted to be opened, clearly visible in the logs. No clue why nothing is rendered. You can try asking around on the discord server if anyone has had a similiar issue, but I haven't, and everything seems in order.

@vaxerski I have some progress

Its dolphin file manager

use something like qt5ct and kvantum to set up QT themes. GTK can be set by lxappearance or manually using the GTK_THEME envvar

IT WOOOOORKS!!!!!

great, I'll add that to the wiki then.
Happy it works now! =)

Oh yeah, and i have one more warning
When in config you  have autogenerated=1 the alert is pointing to SUPER+Enter to open kitty and SUPER+T to open alacritty
But there is only one keybinding in autogenerated config for terminal, SUPER+Q for kitty

oops

fixed

Cool!

Luck for you to continue Hyprland, its great thing bro)


[Program]: Write a PHP program to find the adjoint of a matrix

Description
Write a PHP program to find the adjoint of a matrix
The adjoint of a square matrix A is the transpose of the matrix of cofactors of A. The adjoint of a matrix A is denoted as A*.
Input  :
1 2 3
4 5 6
7 8 9

Output :
[[-3, 6, -3], [6, -12, 6], [-3, 6, -3]]

How to contribute

Save the solution in program/program/find-the-adjoint-of-a-matrix/program/find_the_adjoint_of_a_matrix.php file

!assign


Create Detailpage for each Product

Value Proposition
As a user
I want to click on the "info-Button" to see more informations of the product
So that i can see the quantity and preparation
Description

Acceptance Criteria

[ ] the user can click on the info-button to go to the detail page
[ ] when he clicks on "Add to Cart" the product is put into the shopping cart
[ ] if he clicks on "Back to Products" he gets back to the product page

Tasks
(for developers team)

[ ] create new feature branch ("AddDetailPage")
[ ] extend the database with a description for each product
[ ] add onClick function to the info-button
[ ] create a detail page on which the clicked product is displayed
[ ] create two buttons with the llink and add functions

Complexity
L

Will the detail page have its own url?

yes, that is the plan for now


Corrade and Magnum on Linux

To get corrade and magnum working on Linux I had to do a minor change.

Extension ".exe" was assumed for executable.
Removed default feature magnum[windowlesswglapplication] which is Windows only

I have tested it on few examples and it worked without a problem. However, a more through examination to test all possible plugins and extensions is probably necessary.

 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.:x: lecopivo sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@lecopivo ohoo, thanks!
Removing the windows-specific default feature makes sense for now, however in the long run I actually wanted to have system-specific Default-Features (so picking one enabled-by-default application for every system, but -- a question for vcpkg developers: is there a possibility to specify  Default-Features  or a list of Features differently for each system (Windows, Linux, macOS)?

Oh, um, just in case I wasn't clear and it's blocking the merge (sorry): from my side it's completely fine to merge the changes in their current form.

@alexkaratarakis @ras0219-msft any chance to get this merged? :) Thanks a lot!

Sorry for taking so long on this and thanks for the PR!
Unfortunately, the portfile isn't a "full" CMake context, so some settings like CMAKE_EXECUTABLE_SUFFIX aren't available :(

Ah, I see.
Thanks a lot for the merge! :+1:


Release/v2.32.2

Submisison Checklist

[ ] Run tests: ./runCmdStanTests.py src/test
[ ] Declare copyright holder and open-source license: see below

Summary:
Merge release/v2.32.2 into develop
Intended Effect:
How to Verify:
Side Effects:
Documentation:
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company):
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

Hey @WardBrian I've added excludeFile('stan/lib/stan_math/lib/*') as a new exception.


What does --numworkers do?

What does --numworkers do?

--num_workers will set the corresponding property of the Dataloaders. You can check its exact purpose within the torch documentation. It basically sets the number of threads used by the Dataloaders.

--num_workers will set the corresponding property of the Dataloaders. You can check its exact purpose within the torch documentation. It basically sets the number of threads used by the Dataloaders.

So setting them as the ammount of cpu cores is a good choice?

You indeed should take the number of cpus into consideration (I often limit the number of workers a bit lower than the total of available cpus in case some operations are using multithreading)  , but also the amount of ram. I have no heuristics to find the right number of workers given the amount of memory, but you will have memory errors if the number of workers is too high, so I just make tests until it works.


database issue

I am using the latest version of streama 1.7.2 .
The first entry in database in field "other videos" is not ok here , not matter if i try to delete it or change the filename in it i am always without success .
This means that file is not registered in database when i upload it , but all other data is there , like the picture to that field and etc ....
When i try to delete it says ok but in reality is not ok , it is still there and dont get out .
I want to know where is database stored (is those .db files next to jar executable?) and how to open it ro remove that entry manually .
How can i open the database / or how can i delete that entry manually , because by the web interface is not working .
Note : all other entrys are ok and if i delete any other using web interface it works .

http://www.h2database.com/html/quickstart.html

Thank you TheNocturnalDev for the tip .
does anyone here knows the username and password used by streama app to connect to the database ?

Got it , it is in this file https://github.com/streamaserver/streama/blob/master/grails-app/conf/application.yml
it is "root" only for production


DataTables Core Bug when ColReorder is enabled

Test Case: http://live.datatables.net/xijeqige/2/edit
In the example above, I'm adding a text box to the cell through the createdCell callback and then checking if the row data (array or object) has changed.
Steps to reproduce the issue:

Change the value of any text box.
In the console, one can see that the row data still has the value and not the text box html.
Reorder any column by dragging the column into a different position.
Change the value of any text box.
In the console, one can see that the row data now has the text box html and not the value.

Please note that this issue appears only when reordering a column.

Thanks for posting this - I'm going to move it to ColReorder as it isn't a DataTables issue, but rather ColReorder.
New issue.


Migrations: Seed Data

In EF6, this was accomplished using DbMigrationsConfiguration.Seed(), but migrations configurations don't exist in EF7.

How is Seed method handled in EF7?
protected override void Seed(MyContext context){}

@hbopuri - There isn't a first class API for this at the moment (though this work item is tracking adding one in the future). Currently you would just write code in app startup to handle seed data.

@rowanmiller wasn't  override seed  part of earlier EF versions? is EF7 a upgraded version of earlier versions or a completely newly designed from scratch?
HaBo Rocks
Harsha Bopuri

@hbopuri - It's a major version and has breaking changes in it. These breaking changes are larger than we would typically do in a release, but you can read more about the reasoning behind what we are doing here http://blogs.msdn.com/b/adonet/archive/2014/10/27/ef7-v1-or-v7.aspx.

@rowanmiller Will this feature ship with the RTM? And totally agree with @giggio suggestion.

@heathyates - Not sure if we'll get a seed method equivalent into initial RTM. It is super easy to write the login in your app start code in the meantime.

@rowanmiller - It is easy to write a seed method using the app startup code. However, all the samples that I could find incorrectly use EnsureCreatedAsync and as a result fail to load the seed data. What is missing is a way to determine if the DbContext is correctly configured and has the model applied that matches the seed data requirement. This could be solved by having a way to detect if a particular Migration has been applied to the datastore.

@jwdavidson I have not experienced a failure to load the seed data and I use EnsureCreatedAsync. Has the mvc music store failed for you? I'm not implying I don't believe you or your claim, but confused as to what samples are not working for you? Would be interested in duplicating what you have observed myself. :-)

@jwdavidson do you want to apply migrations during startup to ensure the database is up to date? If so, context.Database.AsRelational().ApplyMigraions() is the API to do this.

@heathyates - The case where EnsureCreatedAsync is when it returns true, which it does when the database was not previously created and/or the initial migration has not be loaded to the database. After that if you want to load seed data which uses a second migration then it will fail as  EnsureCreatedAsync will return false.
@rowanmiller - the suggested ApplyMigrations() process may enable the seed function to be reliably processed from the startup code. I will try that tomorrow and let you know.

@rowanmiller - the following code block seems to do exactly what I want: ensure the database exists and the relevant migrations have been applied
using (DbContext db = (DbContext)serviceProvider.GetService<ApplicationDbContext>()) {
    if (!db.Database.AsRelational().Exists()) {
        db.Database.AsRelational().Create();
    }
    db.Database.AsRelational().ApplyMigrations();
}

After this any data insertion routines may be safely added. Thanks.

@jwdavidson you should be able to remove the existence check and creation. ApplyMigrations() will take care of creating the database if it doesn't exist.
using (DbContext db = (DbContext)serviceProvider.GetService<ApplicationDbContext>()) {
    Database.AsRelational().ApplyMigrations();
}

@rowanmiller - Yes, that works as advertised, just not used to doing something like this without an "if" validation. Thanks again

@rowanmiller
Any blogpost on database initialization and seeding using EF7? Where is up to?

@weitzhandler good discussion on the best pattern for the moment going on at https://github.com/aspnet/EntityFramework/issues/3070

Clearing the milestone after talking about this with @DamianEdwards and @rowanmiller. It is really hard to find the right place to do seeding, in particular in an ASP.NET application. We should at least consider trying to have a solution for RTM.

I Always use seed data for system records that have identity values outside the range of the identity. Mostly I use negative values and have the identity simply start at 1. I then know which values are for what "system" data, which is also the same across all instances of the databases. As part of seeding, but also in general how could you insert a record with an identity PK with a given PK value. In effect will inserting records with -- adhoc IDENTITY INSERT ON -- be supported or what workaround would you suggest?.

@summer600 it requires a little bit of a workaround, but you can do this already - http://docs.efproject.net/en/latest/saving/explicit-values-generated-properties.html#explicit-values-into-sql-server-identity-columns. If you set a value on a PK property (i.e. it's not just the CLR default for the property type) then EF Core will attempt to write that to the database for you.

@divega

Clearing the milestone after talking about this with @DamianEdwards and @rowanmiller. It is really hard to find the right place to do seeding

Were you referring to seeding before\after each migration or even for a single seed? I'm curious to know why it is so complicated, is it not as easy as just running the DML SQL scripts after running the DDL migration scripts?

We should at least consider trying to have a solution for RTM.

(If you referred to seed per migration) I think so too, 90~% of the times I had to change the structure of my tables I also had to run DML migration scripts.
As a temporary solution, I would write the raw SQL inside the migration with
migrationBuilder.Sql(@"{{DoMagicHere}}");

That comment was referring to the fact that in EF Core we don't have a pattern or API to run seeding (single method or not) after applying migrations. That sends users looking for ways to execute the seeding logic when the application runs, but that itself has lots of issues and no generally correct solution.

A problem with seeding on startup: When having multiple app nodes, how can you avoid all app nodes trying to seed the database at once?

@geirsagberg use a flag in a configuration table and lock it.

Ended up wrapping the seeding in a TransactionScope with IsolationLevel.Serializable, looking good so far.

Actually, using a TransactionScope does not work at all, because EF does not yet support ambient transactions; I get the errror An ambient transaction has been detected. Entity Framework Core does not support ambient transactions.

Sorry to jump in on this but doing seeding on startup etc ins't going to fly no one will do that in prod. In EF 6 we had DbMigrationsConfiguration and this was called post migration by update-database. The neat thing is update-database can be called as part of your continuous deployment process ensuing that your servers (think multiple instances Azure) are in the correct state to receive the update and it's done as part of migrations. I would suggest the same pattern.
To workaround this I've just been adding migrations to do seed data so I know they will be called by update-database during CD. And a good by-product is that I can rollback seed data in the same way as I do for table structure.

To workaround this I've just been adding migrations to do seed data so I know they will be called by update-database during CD. And a good by-product is that I can rollback seed data in the same way as I do for table structure.

I really like this approach, as it also means you don't have to worry about checking for existing data etc. You know your seed logic will only run once per database... and the seed data will go thru the schema transformations etc. of following migrations.

@rowanmiller  I wrote it 8 months ago :smile
https://github.com/aspnet/EntityFramework/issues/629#issuecomment-186800686

As a temporary solution, I would write the raw SQL inside the migration

I like the idea of adding migrations to seed the DB. It makes a lot of sense for all the reasons @DalSoft mentioned.
I'm currently seeding on startup and not only does it add extra time whenever you run it, it feels wrong. The vast majority of the time, the database is already seeded and it adds unnecessary overhead on startup which means it takes me extra time whenever I want to debug it (which is often).
It would be really nice to figure out a way to access the DB context from the migration, but I suppose changes to the context in the future could break past migrations, which makes that untenable. It would at least be nice to not have to write the SQL directly.
Maybe there could be an additional argument for the CreateTable function that takes an array of anonymous row objects like so:
migrationBuilder.CreateTable(
    name: "Foo",
    columns: table => new
    {
        FooID = table.Column<int>(nullable: false)
            .Annotation("SqlServer:ValueGenerationStrategy", SqlServerValueGenerationStrategy.IdentityColumn),
        Name = table.Column<string>(maxLength: 50, nullable: false),
        SortOrder = table.Column<int>(nullable: false)
        /* More columns */
    },
    constraints: table =>
    {
        table.PrimaryKey("PK_Foo", x => x.FooID);
    },
    seedData: new [] {
        new {
            Name = "Bar",
            SortOrder = 1
        },
        new {
            Name = "Baz",
            SortOrder = 2
        }
    });

Then there could also be additional functions for inserting / updating / removing on the model builder using the same structure.

How would one have seed data in migrations that are also environment specific? e.g. for dev only. Or is that not really a pattern.

@DamianEdwards migrations are just code that executes, so you can easily write conditional logic to only add seed data if <insert whatever mechanism you want to switch on>.

BTW I think we do still want a higher level seed data mechanism that allows you to use your model to specify the data (and could have a native understanding of environments)... I just meant that adding seed data inline in migrations is also a good pattern with some benefits.

@rowanmiller How do you inject the environment name to the migration?

@gdoron it would be hard to get IHostingEnvironment in (as you'd have to override the components that create migrations). So the best bet would probably be to check the environment variable... not ideal, and something we could look at improving, but it would work at the moment.

@DamianEdwards @gdoron @rowanmiller I have had to solve this very problem today! I have a workaround that allows you to take the environment switch e.g. update-database -environment production and inject that into the migration. As @gdoron suggested a environment variable is the way to go, but the way I have done it works with the dotnet CLI so that it can be used as in my CD pipeline.

Looking forward to reading that, be sure to update here once it's ready!

@atrauzzi @DamianEdwards @gdoron @rowanmiller Here is my (belated) post on how I went about getting seeding and migrations working with the environment switch.
http://www.dalsoft.co.uk/blog/index.php/2016/12/13/entity-framework-core-seeding-using-migrations/

Hi @rowanmiller, Are we going to bring this feature in near future?

@yasin-uohyd this is not currently planned for an upcoming release.

@rowanmiller Can I ask for a brief clarification on this comment?

To workaround this I've just been adding migrations to do seed data so I know they will be called by update-database during CD. And a good by-product is that I can rollback seed data in the same way as I do for table structure.

I really like this approach, as it also means you don't have to worry about checking for existing data etc. You know your seed logic will only run once per database... and the seed data will go thru the schema transformations etc. of following migrations.

This seems like our best option for now. To clarify, are you referring here to running inline SQL during migrations via the migrationBuilder?

@jammerware yes, that is correct

I collected some scenarios based on our existing EF6 data seeding implementation and our current GitHub discussions, and I'm proposing this solution that addresses most of them. It’s different from what we had, and it enables interesting scenarios that we didn’t cover before.
If you've been waiting for this feature, please give your input whether you think it's a good idea or you think it won't work for you!
Examples
Please refer to this gist. It has three examples of seed data in OnModelCreating and what the scaffolded migration looks like. Each example builds on top of the previous one showing how we would generate the required insert, update or delete instructions (based on the current snapshot).
Proposal

We add a SeedData (or similar) method to Entity<TModel> that takes a TModel[]

Optionally taking an alternateKey: TModel => property
Users are able to use files if they convert them to objects (e.g. Json.Deserialize)

We add CRUD methods to MigrationBuilder

This can be used standalone, but it also supports scaffolding

We save metadata for the rows we are tracking in the snapshot
We diff the seed data as part of the dotnet ef migrations add command
We scaffold the CRUD statements as part of the migration
Optionally, We teach InMemory to read seed data

E.g. DbContext.ReadSeedData()???

Optionally, we teach MigrationBuilder which environment it's running in to conditionally run seeding
Optionally, we add SeedDataFromJson or similar helpers

Remarks

This takes the benefits of static typing of Configuration.Seed and extends it with migrations support.
This introduces a nicer API for people who want to migrate data but don't need to keep track, who were previously using raw SQL
This allows to easily read seed data from a file, a common feature in other ORMs which we never had (as long as it can be converted to model entities, it can be any source or format and we're completely agnostic)
This allows to easily seed an InMemory database for testing by just inserting the seeded objects to the internal collections
This can be exported as SQL along the schema migrations for publishing

Proposed implementation steps

First PR adds migration operations, which can be used standalone

InsertRows
DeleteRows
UpdateRows
CreateTable.WithRows

Second PR adds scaffolding

Entity<TModel>

SeedData(TModel[] data, Func alternateKey = null)

dotnet ef migrations add

Diff seed data with previous snapshot
Update snapshot
Scaffold migration code with CRUD operations

More PRs could follow up for the optional items, which are based on these new features but aren't needed for data seeding

@tinchou This is interesting, however I don't think it addresses something that always holds me up when I think about strongly / generically typing the seeds. That is: what happens if we remove the Population property from Country? Your previous migrations will no longer compile against the new version of the Country class. Perhaps we could do it with dynamic objects where the property names match column names, but I don't see any way of getting around this issue and keeping it strongly-typed.

@rmarskell there are two steps here:

We have strongly-typed data in the model, which you must keep up to date in order to compile
We have anonymous objects / untyped data in the migrations themselves

Does this address your concern or am I missing something?

Ah, I see. In my head I was reading those OnModelCreating boxes as migrations. Haha. That makes now. I like this a lot.
So, in your OnModelCreating would we manually be duplicating the change we made in the seed migration or is this just two different ways to do it?

OnModelCreating has the current data.  If you keep it under source control then seed data will be in sync with your code.
We want to scaffold the data motion operations automatically for you, as we do with schema changes. We plan to have a snapshot of your seed data and diff it to generate the operations.
You can also use the API to manually migrate data, but that won't be tracked since it's not part of the model. It is similar to what people currently do with raw SQL.

Hello everyone! The feature is working pretty well now and you can give it a try :).

Clone https://github.com/tinchou/entityframework
Drop the contents of this zip on EF's root folder: SeedDataDemo.zip
cd SeedDataDemo
dotnet ef database update
dotnet run

Note: Some steps will take a while since they compile EF (and not only the demo project).
Feel free to play around with it, test stuff, report bugs, etc.. Off the top of my head I can mention the following gotchas:

We don't support navigations
We need you to specify the object IDs, otherwise it'll generate an invalid temporary value

Thanks!

did u really have to change the wole thing while developping .Net Core? this is just complicating our good habit. just spent 30 mins on this while i was supposed to think about other important stuff, instead still trying.to find how to SEED DATA.....

We're very transparent on what features are missing on EF Core, and if this is an important part of your application you should consider using EF6.
EF Core is a new framework, and so we're not attached to the old design. We can keep it when it makes sense, but we can choose to change it when can be improved. I'm confident the new design will cover all previous use cases and more (many that have been raised here and in other issues). The proposal was shared very early on to ensure anyone can call out if they see any problem, and I encourage you to share any concerns you have.

For EF Core I think we should draw a line under seeding as a separate thing. And instead have a lightweight helper available in migrations that allows you to do seeding (with the functionality outlined in the proposal). That way you can have a up and a down 'seed', more importantly the seed data works like a migration avoiding the pitiful mentioned by @rmarskell if the table changes over time.
I've used the technique I outlined in my blog (which I would now do over how I did it in EF6) post in two prod deployments one of which is for a large company, and I've found extending your seed data using a migration rather than having one seed class to rule them all has paid off, as doing this I'm confident that seeding will always work no matter what environment or build I'm targeting.

@cedriclange EF Core is new rather than iterative improvement over EF6 - hopefully once your over the initial learning curve your see that it's aiming to quicker and more lightweight than previous versions.

The problem is that migration itself has some serious issues.
For example you can't make it work if there is no start up project. A total annoyance.

@weitzhandler yes but you can work around that by creating a separate data startup project example
https://gist.github.com/DalSoft/8684d8be9566221ca7b1b8e962db241f#file-program-cs

You can't make it work if there is no start up project. A total annoyance.

Agreed. We've done everything we can in EF Core's tools to work around the limitations .NET Standard and .NET Core class libraries, but it can still be painful at times. We'll continue to do everything we can in our tools to make the experience as delightful as possible. We also work closely with to the .NET Core SDK team and let them know where we're hitting limitations.

@DalSoft Is this another project in the solution, or things added to the various current project files?
@bricelam Thanks for your sympathy!

What is the delivery forecast?

Final version? EF Core 2.
Nightly version? I'm hoping to get https://github.com/aspnet/EntityFramework/pull/7824 merged soon, I'd think no later than next Friday.

Final version? EF Core 2 ?

Yes. There will be an EF Core version 2 released sometime this year. It'll include this feature and others that we're working on. You can take a look at them if you search by issues with the filter milestone:2.0.0

Here's a solution for running the seed method during Startup as suggested using DI. This example also uses Identity. https://gist.github.com/mombrea/9a49716841254ab1d2dabd49144ec092

@DalSoft

yes but you can work around that by creating a separate data startup project example
https://gist.github.com/DalSoft/8684d8be9566221ca7b1b8e962db241f#file-program-cs

Will it work in an ASP.NET Core project using EF6.1.3? Unfortunately I can't work with EFCore just yet.

@weitzhandler the concept would work on EF6 but the code would probably need re-working slightly.
@mombrea I would strongly suggest separating seeding from the Web project. I've had problems with doing this on production and advise all my clients to use a separate project that can invoked as part of your CD pipeline, rather than by the web project directly.

@DalSoft thanks for the tip, I will look at another way of triggering the seed data. What type of problems did you see in production when it was being called during Startup?

@mombrea expected stuff longer app start.
Unexpected stuff a dev leaving a entity migration in the source and it being run on app startup. Making it part of CD enforces principle of least surprise, you know when you migration and seeding are taking place and you can test it as appropriate.

Yes. There will be an EF Core version 2 released sometime this year. It'll include this feature and others that we're working on. You can take a look at them if you search by issues with the filter milestone:2.0.0

What is the current solution/workaround while waiting for 2.0? Im currently using ASP.NET Core/ EF Core.
Cheers guys and understand fully this is a blank slate project 👍

@garfbradaz, I am using this workaround:
1 - Create a partial class with the same name of the migration class.
2 - In that partial class i create a method SeedDataBase that receives one argument of type MigrationBuilder
3 - In the migration class, in the end of the Up method, i call this.SeedDataBase(migrationBuilder)
4 - Inside the methods SeedDataBase , i call just migrationBuilder.Sql("INSERT INTO (...)");
Hope it helps.

@brunoalreis Would it be possible to use your workaround when running against two different database servers? I.E., is it possible to detect inside the migration whether your connecting to an MSSQL database vs. a PostgreSQL database?

@jceddy, I think you can. I have two different scenarios, in two different applications. In one i am using Sqlite and in the other i am using PostgreSQL. In the Sqlite migrationBuilder.ActiveProvider has "Microsoft.EntityFrameworkCore.Sqlite" and in the PostgreSQL migrationBuilder.ActiveProvider has "Npgsql.EntityFrameworkCore.PostgreSQL". Don't know if is the best way to check database type, but it works.

@jceddy take a look at my post on EF Core seeding.
If you use my technique you can pass environment switches, and more importantly just use the normal EF context. This means you don't have to do a custom SQL for each provider.

@brunoalreis @DalSoft I ended up creating an empty migration after the initial schema creation one and added code to seed data in the empty migration.

I'm a bit late to the party, but I wanted to give the EF Core team input on my requirements for seeding or DbContext data initialization. Perhaps entity SeedData could be made to work for me, but I can't wait for release 2.1.
I feel that the APIs for DbContext data initialization should be added to DbContext. A simple
DbContext.MigrateToLatestVersion( IDbContextInitializer initializerClass, IServiceProvider serviceProvider )

which utilizes DbContext.Database.Migrate() and after which  calls the seed( dbContext, serviceProvider ) method in the initializer class.
The DbContextInitializer class then has full reign to manipulate the context and persist changes to the repository.
Reading through this issue, this looks like the initial solution proposed by @rowanmiller . It's simple and easy to implement.


Only include cache-control: max-age on css and images.

Issue:
What I did

How to test

Checklist

For all PR's

[ ] I've added relevant changes to the project Readme if needed.
[ ] I've updated the documentation site as needed.
[ ] I have added unit tests to cover my changes (if not applicable, please state why in a comment)

For new components only

[ ] I have added a story covering all variants
[ ] I have checked a11y tab in storybook passes
[ ] Any events are emitted on the event bus

I think we need to flip the order of these items.


Adding new keyboard shortcuts for IntelliTrace stepback

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/debugger/how-to-use-intellitrace-step-back.md
:white_check_mark:Succeeded

docs/debugger/media/intellitrace-step-back-icons-description.png
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


MM-46959 Update prepare-docker-build job to not delete product files

Now that GitLab CI seems to be building the server and everything correctly, we just need to make sure that the product files aren't deleted by the web app when we're doing PR builds. After this, we should be able to enable Boards as a product on test servers.
I also took the opportunity to add a few comments and extra log messages to CircleCI so that you can figure out where the server for any given PR build comes from
Ticket Link
https://mattermost.atlassian.net/browse/MM-46959
Release Note
NONE

@hmhealey - gentle reminder to merge this before you leave for PTO :)


Remove spurious differences between hardforks

Currently there are a number of spurious differences between forks. This means that tools like diff can't be used to their full potential.
For example the only difference between Istanbul and Muir Glacier should be the value of BOMB_DELAY_BLOCKS and MAINNET_FORK_BLOCK. The actual diff is:
diff -u src/ethereum/istanbul/__init__.py src/ethereum/muir_glacier/__init__.py
--- src/ethereum/istanbul/__init__.py	2022-07-11 13:51:15.223853555 +0100
+++ src/ethereum/muir_glacier/__init__.py	2022-07-11 13:51:15.223853555 +0100
@@ -1,8 +1,8 @@
 """
-Ethereum Istanbul Hardfork
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+Ethereum Muir Glacier Hardfork
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

-The Eighth Ethereum hardfork.
+The Ninth Ethereum hardfork.
 """

-MAINNET_FORK_BLOCK = 9069000
+MAINNET_FORK_BLOCK = 9200000
Common subdirectories: src/ethereum/istanbul/__pycache__ and src/ethereum/muir_glacier/__pycache__
diff -u src/ethereum/istanbul/spec.py src/ethereum/muir_glacier/spec.py
--- src/ethereum/istanbul/spec.py	2022-09-13 16:13:25.178809923 +0100
+++ src/ethereum/muir_glacier/spec.py	2022-09-13 16:13:25.178809923 +0100
@@ -61,7 +61,7 @@
 GAS_LIMIT_MINIMUM = 5000
 GENESIS_DIFFICULTY = Uint(131072)
 MAX_OMMER_DEPTH = 6
-BOMB_DELAY_BLOCKS = 5000000
+BOMB_DELAY_BLOCKS = 9000000
 EMPTY_OMMER_HASH = keccak256(rlp.encode([]))

diff -u src/ethereum/istanbul/spec.py.rej src/ethereum/muir_glacier/spec.py.rej
--- src/ethereum/istanbul/spec.py.rej	2022-09-12 14:43:20.633086763 +0100
+++ src/ethereum/muir_glacier/spec.py.rej	2022-09-12 14:43:20.633086763 +0100
@@ -1,5 +1,5 @@
---- src/ethereum/istanbul/spec.py
-+++ src/ethereum/istanbul/spec.py
+--- src/ethereum/muir_glacier/spec.py
++++ src/ethereum/muir_glacier/spec.py
 @@ -877,15 +877,11 @@ def calculate_block_difficulty(
      # bomb has no effect prior to block 200000 we pretend it existed from
      # genesis.
diff -u src/ethereum/istanbul/trie.py src/ethereum/muir_glacier/trie.py
--- src/ethereum/istanbul/trie.py	2022-07-11 13:51:15.223853555 +0100
+++ src/ethereum/muir_glacier/trie.py	2022-07-11 13:51:15.223853555 +0100
@@ -29,8 +29,8 @@
     cast,
 )

-from ethereum.constantinople import trie as previous_trie
 from ethereum.crypto.hash import keccak256
+from ethereum.istanbul import trie as previous_trie
 from ethereum.utils.ensure import ensure
 from ethereum.utils.hexadecimal import hex_to_bytes

Common subdirectories: src/ethereum/istanbul/utils and src/ethereum/muir_glacier/utils
Common subdirectories: src/ethereum/istanbul/vm and src/ethereum/muir_glacier/vm

This has improved since this was first opened, but there are still some spurious differences:
diff '--color=auto' -U0 -r src/ethereum/istanbul/utils/address.py src/ethereum/muir_glacier/utils/address.py
--- src/ethereum/istanbul/utils/address.py      2024-11-12 10:32:05.622539227 -0500
+++ src/ethereum/muir_glacier/utils/address.py  2024-11-12 10:32:05.695871742 -0500
@@ -12 +12 @@
-Address specific functions used in this istanbul version of
+Address specific functions used in this muir_glacier version of
@@ -85 +85 @@
-    address: `ethereum.istanbul.fork_types.Address`
+    address: `ethereum.muir_glacier.fork_types.Address`
diff '--color=auto' -U0 -r src/ethereum/istanbul/utils/hexadecimal.py src/ethereum/muir_glacier/utils/hexadecimal.py
--- src/ethereum/istanbul/utils/hexadecimal.py  2024-11-12 10:31:43.646116322 -0500
+++ src/ethereum/muir_glacier/utils/hexadecimal.py      2024-11-12 10:31:43.782781479 -0500
@@ -13 +13 @@
-Istanbul types.
+Muir Glacier types.
diff '--color=auto' -U0 -r src/ethereum/istanbul/utils/message.py src/ethereum/muir_glacier/utils/message.py
--- src/ethereum/istanbul/utils/message.py      2024-11-12 10:31:43.649449619 -0500
+++ src/ethereum/muir_glacier/utils/message.py  2024-11-12 10:31:43.786114776 -0500
@@ -12 +12 @@
-Message specific functions used in this istanbul version of
+Message specific functions used in this muir_glacier version of
@@ -66 +66 @@
-    message: `ethereum.istanbul.vm.Message`
+    message: `ethereum.muir_glacier.vm.Message`
diff '--color=auto' -U0 -r src/ethereum/istanbul/vm/interpreter.py src/ethereum/muir_glacier/vm/interpreter.py
--- src/ethereum/istanbul/vm/interpreter.py     2024-11-12 10:31:43.676115991 -0500
+++ src/ethereum/muir_glacier/vm/interpreter.py 2024-11-12 10:31:43.819447741 -0500
@@ -162 +162 @@
-    evm: :py:class:`~ethereum.istanbul.vm.Evm`
+    evm: :py:class:`~ethereum.muir_glacier.vm.Evm`
@@ -217 +217 @@
-    evm: :py:class:`~ethereum.istanbul.vm.Evm`
+    evm: :py:class:`~ethereum.muir_glacier.vm.Evm`


Incorrect cgroup paths in /proc when running RKE on RancherOS

RancherOS Version: (ros os version)
1.5.5
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
AWS (Official AMI)
Hello,
Setting up an RKE cluster through Rancher UI with a RancherOS node pool shows that cgroup paths in /proc/<pid>/cgroup are mostly incorrect for all containers created by K8S, referring paths that do not exist.
Issue does not occur on another node pool running Ubuntu.
For instance, checking PODs managed by Rancher itself:
ingress-nginx   nginx-ingress-controller-69t4v            1/1     Running     0          55m     <IP_ADDRESS>    vboulineau-rancher-worker1          <none>           <none>
ingress-nginx   nginx-ingress-controller-tw2xc            1/1     Running     0          30m     <IP_ADDRESS>   vboulineau-rancher-worker-ubuntu1   <none>           <none>

On node vboulineau-rancher-worker1, we can see:
4628 www-data nginx: master process /usr/local/openresty/nginx/sbin/nginx -c /etc/nginx/nginx.conf

Checking cgroup paths for this process, we'll get:
[rancher@vboulineau-rancher-worker1 ~]$ cat /proc/4628/cgroup
11:name=systemd:/kubepods/besteffort/pod7e241a28-b013-481e-9e00-cbe6f00b5eaf/6b5583d73d20fa6da209e4d628a0c27395815f6613cb0a2c7e0e5b64507b210c
10:cpuset:/docker/8ec3e6062e1825067fddaa64bfb839cb47579b4bfe49c4dd9d486ff81c35a479/kubepods/besteffort/pod7e241a28-b013-481e-9e00-cbe6f00b5eaf/6b5583d73d20fa6da209e4d628a0c27395815f6613cb0a2c7e0e5b64507b210c
9:net_cls,net_prio:/docker/8ec3e6062e1825067fddaa64bfb839cb47579b4bfe49c4dd9d486ff81c35a479/kubepods/besteffort/pod7e241a28-b013-481e-9e00-cbe6f00b5eaf/6b5583d73d20fa6da209e4d628a0c27395815f6613cb0a2c7e0e5b64507b210c
8:memory:/docker/8ec3e6062e1825067fddaa64bfb839cb47579b4bfe49c4dd9d486ff81c35a479/kubepods/besteffort/pod7e241a28-b013-481e-9e00-cbe6f00b5eaf/6b5583d73d20fa6da209e4d628a0c27395815f6613cb0a2c7e0e5b64507b210c
7:blkio:/docker/8ec3e6062e1825067fddaa64bfb839cb47579b4bfe49c4dd9d486ff81c35a479/kubepods/besteffort/pod7e241a28-b013-481e-9e00-cbe6f00b5eaf/6b5583d73d20fa6da209e4d628a0c27395815f6613cb0a2c7e0e5b64507b210c
6:cpu,cpuacct:/docker/8ec3e6062e1825067fddaa64bfb839cb47579b4bfe49c4dd9d486ff81c35a479/kubepods/besteffort/pod7e241a28-b013-481e-9e00-cbe6f00b5eaf/6b5583d73d20fa6da209e4d628a0c27395815f6613cb0a2c7e0e5b64507b210c
5:devices:/docker/8ec3e6062e1825067fddaa64bfb839cb47579b4bfe49c4dd9d486ff81c35a479/kubepods/besteffort/pod7e241a28-b013-481e-9e00-cbe6f00b5eaf/6b5583d73d20fa6da209e4d628a0c27395815f6613cb0a2c7e0e5b64507b210c
4:pids:/docker/8ec3e6062e1825067fddaa64bfb839cb47579b4bfe49c4dd9d486ff81c35a479/kubepods/besteffort/pod7e241a28-b013-481e-9e00-cbe6f00b5eaf/6b5583d73d20fa6da209e4d628a0c27395815f6613cb0a2c7e0e5b64507b210c
3:hugetlb:/docker/8ec3e6062e1825067fddaa64bfb839cb47579b4bfe49c4dd9d486ff81c35a479/kubepods/besteffort/pod7e241a28-b013-481e-9e00-cbe6f00b5eaf/6b5583d73d20fa6da209e4d628a0c27395815f6613cb0a2c7e0e5b64507b210c
2:perf_event:/docker/8ec3e6062e1825067fddaa64bfb839cb47579b4bfe49c4dd9d486ff81c35a479/kubepods/besteffort/pod7e241a28-b013-481e-9e00-cbe6f00b5eaf/6b5583d73d20fa6da209e4d628a0c27395815f6613cb0a2c7e0e5b64507b210c
1:freezer:/docker/8ec3e6062e1825067fddaa64bfb839cb47579b4bfe49c4dd9d486ff81c35a479/kubepods/besteffort/pod7e241a28-b013-481e-9e00-cbe6f00b5eaf/6b5583d73d20fa6da209e4d628a0c27395815f6613cb0a2c7e0e5b64507b210c
0::/

Only the 11:name=systemd one has the correct path. All others are prefixed by /docker/8ec3e6062e1825067fddaa64bfb839cb47579b4bfe49c4dd9d486ff81c35a479
This path /sys/fs/cgroup/<group>/docker/8ec3e6062e1825067fddaa64bfb839cb47579b4bfe49c4dd9d486ff81c35a479 does not exist.
However, this id does not come from nowhere, it's the container id of the console container in the system Docker daemon:
[rancher@vboulineau-rancher-worker1 ~]$ sudo docker -H unix:///var/run/system-docker.sock ps
CONTAINER ID        IMAGE                              COMMAND                  CREATED             STATUS              PORTS               NAMES
8ec3e6062e18        rancher/os-console:v1.5.5          "/usr/bin/ros entryp…"   About an hour ago   Up About an hour                        console

So it has probably something to do with the specific way RancherOS runs containers.
I'm not sure it's a bug, but it's definitely causing issues as several monitoring solutions rely on raw cgroup metrics to provide reliable statistics about container workloads.
If you don't believe it's a bug, maybe you'd be able to help understand the underlying mechanisms that explain this behaviour and a way for us to have a reliable way to get cgroups from process.
For reference, on Ubuntu, we get:
ubuntu@vboulineau-rancher-worker-ubuntu1:~$ cat /proc/10106/cgroup
12:hugetlb:/kubepods/besteffort/podadd72969-60f6-4776-ae6b-ddd7a7cbb72e/83ec66cb85cb7bf1fbee10c375b2e0adacc814ddbed74d2096873be39a000da4
11:blkio:/kubepods/besteffort/podadd72969-60f6-4776-ae6b-ddd7a7cbb72e/83ec66cb85cb7bf1fbee10c375b2e0adacc814ddbed74d2096873be39a000da4
10:net_cls,net_prio:/kubepods/besteffort/podadd72969-60f6-4776-ae6b-ddd7a7cbb72e/83ec66cb85cb7bf1fbee10c375b2e0adacc814ddbed74d2096873be39a000da4
9:perf_event:/kubepods/besteffort/podadd72969-60f6-4776-ae6b-ddd7a7cbb72e/83ec66cb85cb7bf1fbee10c375b2e0adacc814ddbed74d2096873be39a000da4
8:freezer:/kubepods/besteffort/podadd72969-60f6-4776-ae6b-ddd7a7cbb72e/83ec66cb85cb7bf1fbee10c375b2e0adacc814ddbed74d2096873be39a000da4
7:rdma:/
6:cpuset:/kubepods/besteffort/podadd72969-60f6-4776-ae6b-ddd7a7cbb72e/83ec66cb85cb7bf1fbee10c375b2e0adacc814ddbed74d2096873be39a000da4
5:pids:/kubepods/besteffort/podadd72969-60f6-4776-ae6b-ddd7a7cbb72e/83ec66cb85cb7bf1fbee10c375b2e0adacc814ddbed74d2096873be39a000da4
4:cpu,cpuacct:/kubepods/besteffort/podadd72969-60f6-4776-ae6b-ddd7a7cbb72e/83ec66cb85cb7bf1fbee10c375b2e0adacc814ddbed74d2096873be39a000da4
3:devices:/kubepods/besteffort/podadd72969-60f6-4776-ae6b-ddd7a7cbb72e/83ec66cb85cb7bf1fbee10c375b2e0adacc814ddbed74d2096873be39a000da4
2:memory:/kubepods/besteffort/podadd72969-60f6-4776-ae6b-ddd7a7cbb72e/83ec66cb85cb7bf1fbee10c375b2e0adacc814ddbed74d2096873be39a000da4
1:name=systemd:/kubepods/besteffort/podadd72969-60f6-4776-ae6b-ddd7a7cbb72e/83ec66cb85cb7bf1fbee10c375b2e0adacc814ddbed74d2096873be39a000da4
0::/system.slice/containerd.service

we are also running into this issue and would like to know if this is us or Rancher...

@vboulineau @heimdull As you mentioned, this issue is an issue due for monitoring solutions like Datadog. I believe the underlying Datadog chart requires this to be set in that particular way.
I'm not sure how much effort it'd be to update it in order to get a Datadog working.

I think you will need to add /sys/fs/cgroup to the system-volumes service that both the docker and console system services effectively --volumes-from if I am not mistaken.

@dweomer I added this to my cloud init file:
rancher:
services:
system-volumes:
volumes:
- /sys/fs/cgroup:/sys/fs/cgroup
-snip-
and after restarting the nodes it looks like Datadog now has access to what it needs !! Thanks

Hi @heimdull ,
This does not fix the issue for us, could you confirm that you were missing the container metrics from the containers live view page in DataDog ?
We tried doing as you suggested in many ways including:
sudo ros config set rancher.services.system-volumes.volumes [/sys/fs/cgroup:/sys/fs/cgroup]
But we are still missing the metrics and we can see a lot of the following errors:
2020-03-22 12:40:38 UTC | PROCESS | DEBUG | (pkg/util/containers/metrics/cgroup_metrics.go:34 in Mem) | Missing cgroup file: /host/sys/fs/cgroup/memory/docker/d1647bd70a38c6e1dd8975cde6410cad6c96f2be5c60346aad9d4c55f2291e5e/kubepods/besteffort/podf6f278fb-bba2-491d-b61e-653179149451/70759db11e426a0d4323e1229754312f80fa5a5a99b0f0806ad83f20d340f53f/memory.stat 2020-03-22 12:40:38 UTC | PROCESS | DEBUG | (pkg/util/containers/metrics/cgroup_metrics.go:188 in CPU) | Missing cgroup file: /host/sys/fs/cgroup/cpu,cpuacct/docker/d1647bd70a38c6e1dd8975cde6410cad6c96f2be5c60346aad9d4c55f2291e5e/kubepods/besteffort/podf6f278fb-bba2-491d-b61e-653179149451/70759db11e426a0d4323e1229754312f80fa5a5a99b0f0806ad83f20d340f53f/cpuacct.stat

This did resolve the issue for us. We did not see metrics then I added the cgroup to system-volumes and now we have cpu/memory metrics in datadog. I added the setting through my cloud init file and rebuilt all the nodes with the new setting.

I successfully validated the workaround, note that you cannot just overwrite the rancher.services.system-volumes.volumes key as other volumes are in there too.
I did not find any way to have an auto-merge, so you'd basically need to take default + /sys/fs/cgroup
With latest version this is what the file looks:
rancher:
  services:
    system-volumes:
      volumes:
      - /dev:/host/dev
      - /etc/docker:/etc/docker
      - /etc/hosts:/etc/hosts
      - /etc/logrotate.d:/etc/logrotate.d
      - /etc/resolv.conf:/etc/resolv.conf
      - /etc/ssl/certs/ca-certificates.crt:/etc/ssl/certs/ca-certificates.crt.rancher
      - /etc/selinux:/etc/selinux
      - /lib/firmware:/lib/firmware
      - /lib/modules:/lib/modules
      - /run:/run
      - /usr/share/ros:/usr/share/ros
      - /var/lib/boot2docker:/var/lib/boot2docker
      - /var/lib/rancher/cache:/var/lib/rancher/cache
      - /var/lib/rancher/conf:/var/lib/rancher/conf
      - /var/lib/rancher:/var/lib/rancher
      - /var/lib/waagent:/var/lib/waagent
      - /var/log:/var/log
      - /var/run:/var/run
      - /sys/fs/cgroup:/sys/fs/cgroup

@dweomer What about adding this mount is the default configuration?

Hi @vboulineau,
Thanks for your input. Could you clarify the following:
When you say "auto-merge" - do you refer to updating the exiting ros config while the VM is running using  ros config export my-config  and then manually update the config and merge it using ros config merge -i my-config followed by a rebooting of the VM ?
Secondly, did you validate the workaround by creating a new VM with the cloud-init file you pasted or you rebuild/reconfigured an existing VM ?
Thank you very much, this would be extremely helpful for us!!

I did not export but I applied with ros config merge -i my-config, with my-config being the file I pasted in previous reply.
And rebooted the VM.


Revert "Refactor analysis benchmark and collect more data"

Reverts flutter/flutter#20169
This broke devicelab.

Landing on red to fix build.


[1135] Amended trainee export to be on

Context
:shipit:
Guidance to review
look at boolean

 Enable export in production

May as well remove the explicit toggle in the other envs if it's on by default


Audio lags behind by .5 seconds on Factorio

Decreasing the latency value as described in https://github.com/i-rinat/apulse/issues/51#issuecomment-298900599, to something like 1000 or even 100 seems to alleviate the issue. No idea if this has any adverse effects or what the optimal value could be (maybe even 0?).
Further testing definitely required.
Also ping @i-rinat: Have you done any additional research into PA latency since that comment?

I've encountered this problem as well. Definitely an environment variable for tweaking this would be super helpful.

Any progress here? Many programs are affected, not just Factorio, which renders some applications practically unusable. I've done some tests of my own, and modifying the latency value in src/apulse-context.c has no effect.


StorageBackendMemory should check for registered TypeAdapters

During tests, I use StorageBackendMemory to not having to go through the file system. So far, so good. However, after all my tests passed, my app still crashed at runtime, because I did not register a TypeAdapter (although I read that it is required in the documentation), since my tests passed fine without it.
I then checked the hive code and saw that the error is thrown from BinaryWriterImpl, which gets invoked from StorageBackendVm.writeFrames. Since this method is basically a no-op in the StorageBackendMemory the exception does never happen during tests.
It would be great if StorageBackendMemory could be adapted to do mimic StorageBackendVm as close as possible. For this case, it would be enough to simply mimic the writeFrames method of StorageBackendVm, but do not actually write to the underlying file – i.e. do everything up until the try block. This would ensure that the TypeAdapeters get checked properly.
Reference:
https://github.com/hivedb/hive/blob/a536cf1190bf18c0e213a31e7ba160c9c760b5f0/hive/lib/src/backend/vm/storage_backend_vm.dart#L120-L124

I believe a whole new backend should be created for this. I see StorageBackendMemory more like a storage option if you want to save data only for one lifetime of your app (maybe navigation state or something).
Turning the objects into bytes and then turning those bytes back into objects is unnecessary in this case.
So maybe leave StorageBackendMemory as-is and create a new StorageBackendVmStub (or something with a better name)?

What's the benefit of using hive for temporary storage in memory compared to simply storing the state in an object? To me it looked like StorageBackendMemory is specifically provided for testing purposes, but maybe that is not the (only?) reason it was added.
Nevertheless, a separate backend implementation would also be fine with me.

Storing them in the memory means you can still access boxes throughout your app without passing references through your widgets or implementing a singleton on your own. Also, live updates are great.


End Cities not spawning

Trying to create a private modpack for my friends and I and when I test the End out, it looks amazing, but upon using the "/locate" command to find an end city, it says there are none. I've spent about an hour just flying around trying the command, and nothing. The only way to get an End City to spawn is to disable BetterEnd, which I really don't want to do, because it looks so good and makes everything 100x better, so I was wondering why this is happening??
Some Information (if it helps):
End Mods -

BYG
Nullscape
BetterEnd

World Generation

BetterX

Hi, please don't use the old tracker for issues, use only the new one

@nbdTyler Hi have you been able to solve this problem?
If yes, please tell me how


Category filter for clear icon

Prerequisites

[X] I have read the Contributing Guidelines.
[X] I have not leaked any internal/restricted information like screenshots, videos, code snippets, links etc.

What happened?
Select the category don't select any value, click on clear icon button, not clearing the category item from search.

What type of frontend framework are you seeing the problem on?
Angular
Which version of iX do you use?
2.0.4
Code to produce this issue.
1) Lets take category example from https://ix.siemens.io/webcomponent-examples/dist/preview-examples/category-filter.html?theme=theme-brand-dark,
2) Category filter that have categories like 'vendor' and 'product'
3) Select the one of the category, don’t select the value
4) click on clear icon button, not clearing the category item from search.

5) Kindly refer https://community.siemens.com/t/category-filter-for-clear-icon/1709

Duplicate issue #1268


AHK V1 convert to V2 Error when code have variables with $ header.

Error output example:
Error: This line does not contain a recognized action.

Text:	$WinID := WinExist("A")
Line:	29
File:	C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\ctrl+g-admin_newV2.ahk

The program will exit.

The function of the code is to use "Ctrl+G" key in the "Save as" or "Open" windows to jump to the using folder in File Explorer or Total Commander when using AHK v1:

AHK v1 code:
(Code comes from https://meta.appinn.net/t/topic/3743/34 by xml123)
Loop, %0%  ; For each parameter:
  {
    param := %A_Index%  ; Fetch the contents of the variable whose name is contained in A_Index.
    params .= A_Space . param
  }
ShellExecute := A_IsUnicode ? "shell32\ShellExecute":"shell32\ShellExecuteA"

if not A_IsAdmin
{
    If A_IsCompiled
       DllCall(ShellExecute, uint, 0, str, "RunAs", str, A_ScriptFullPath, str, params , str, A_WorkingDir, int, 1)
    Else
       DllCall(ShellExecute, uint, 0, str, "RunAs", str, A_AhkPath, str, """" . A_ScriptFullPath . """" . A_Space . params, str, A_WorkingDir, int, 1)
    ExitApp
}

#SingleInstance Force
#NoEnv
;#Warn  ; Enable warnings to assist with detecting common errors.
SendMode Input
SetBatchLines -1
SetWorkingDir %A_ScriptDir%

#IfWinActive ahk_class #32770		; Open/Save dialog

^g::								; Control-g
{
	$WinID := WinExist("A")

;---------------[ File Explorer ]----------------------------------------

	For $Exp in ComObjCreate("Shell.Application").Windows	{
		$This := $Exp.Document.Folder.Self.Path
		Menu ContextMenu, Add,  %$This%, Choice
		Menu ContextMenu, Icon, %$This%, shell32.dll, 5
	}

;	Clean up
	$Exp := ""

;---------------[ Total Commander ]--------------------------------------

;	Total Commander internal codes
	cm_CopySrcPathToClip  := 2029
	cm_CopyTrgPathToClip  := 2030

	ClipSaved := ClipboardAll
	Clipboard := ""

	SendMessage 1075, %cm_CopySrcPathToClip%, 0, , ahk_class TTOTAL_CMD

	If (ErrorLevel = 0) {
			Menu ContextMenu, Add
			Menu ContextMenu, Add,  %clipboard%, Choice
			Menu ContextMenu, Icon, %clipboard%, shell32.dll, 5
	}

	SendMessage 1075, %cm_CopyTrgPathToClip%, 0, , ahk_class TTOTAL_CMD

	If (ErrorLevel = 0) {
			Menu ContextMenu, Add,  %clipboard%, Choice
			Menu ContextMenu, Icon, %clipboard%, shell32.dll, 5
	}

	Clipboard := ClipSaved
	ClipSaved := ""

;---------------

	Menu ContextMenu, Show
	Menu ContextMenu, Delete

}

#IfWinActive
Return

;_____________________________________________________________________________
;
					Choice:
;_____________________________________________________________________________
;

	$FolderPath := A_ThisMenuItem
;	MsgBox Folder = %$FolderPath%

	Gosub FeedExplorerOpenSave

return

;_____________________________________________________________________________
;
					FeedExplorerOpenSave:
;_____________________________________________________________________________
;

	WinActivate, ahk_id %$WinID%

;	Read the current text in the "File Name:" box (= $OldText)
	ControlGetText $OldText, Edit1, A
	ControlFocus Edit1, A

;	Go to Folder
	Loop, 5
	{
		ControlSetText, Edit1, %$FolderPath%, ahk_id %$WinID%		; set
		Sleep, 50
		ControlGetText, $CurControlText, Edit1, ahk_id %$WinID%		; check
		if ($CurControlText = $FolderPath)
			break
	}

	Sleep, 200
	ControlSend Edit1, {Enter}, A
	Sleep, 50

;	Insert original filename
	If !$OldText
		return

	Loop, 5
	{
		ControlSetText, Edit1, %$OldText%, A		; set
		Sleep, 50
		ControlGetText, $CurControlText, Edit1, A		; check
		if ($CurControlText = $OldText)
			break
	}

return

The Generated Code has no change to the line of the example error.
$WinID := WinExist("A")--->$WinID := WinExist("A")

I feel you can fix many bugs when correcting the generated code of this script. Thank you!

In v2, variables names and functions and the like can no longer start with the $ character
https://www.autohotkey.com/docs/v2/v2-changes.htm#names

Names cannot start with a digit and cannot contain the following characters which were previously allowed: @ # $. Only letters, numbers, underscore and non-ASCII characters are allowed.

What do you suggest it get converted to?
If we simply remove the $ or @ or # then the new variable name without that preceeding character might conflict with another variable name elsewhere in the script. Maybe its better to just output a comment into the converted v2 script instructing the user to do a mass find/replace to change the variable name

You can use the awesomeness of AHK unicode support and replace the ASCII values with fullwidth unicode ones
# → ＃
@ → ＠
$ → ＄
(or make it triple ＄＄＄ to reduce the chance of collision some UID )

We could replace invalid characters with _ and to avoid conflict add AHKv1v2_ to the start?

Maybe its better to just output a comment into the converted v2 script instructing the user to do a mass find/replace to change the variable name.

Probably best solution, doing mass replace can cause issues similar to #115

@eugenesvk I did some testing with your unicode characters and they don't seem to work? Am I using them wrong?

I don't see the char/version you use (is it $ or ＄?)
But it works just fine here (all dollars signs are ＄ unicode ones) on 2.0.10
＄WinID := WinExist("A")
msgbox('＄WinID=' ＄WinID)

I can run it is VSCode but not QuickConverter, strange
I wonder if the characters are converted from unicode to ascii?

is you default launcher AHK v2?

Yes, could it be because the quickconverter binary is 32-bit?


[SPARK-17204][CORE] Fix replicated off heap storage

(Jira: https://issues.apache.org/jira/browse/SPARK-17204)
What changes were proposed in this pull request?
There are a couple of bugs in the BlockManager with respect to support for replicated off-heap storage. First, the locally-stored off-heap byte buffer is disposed of when it is replicated. It should not be. Second, the replica byte buffers are stored as heap byte buffers instead of direct byte buffers even when the storage level memory mode is off-heap. This PR addresses both of these problems.
How was this patch tested?
BlockManagerReplicationSuite was enhanced to fill in the coverage gaps. It now fails if either of the bugs in this PR exist.

Test build #71022 has started for PR 16499 at commit e49aeca.

Test build #71022 has finished for PR 16499 at commit e49aeca.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test PASSed.

@rxin, can you recommend someone I reach out to for help reviewing this PR?

Ideally I think @joshrosen is the person to take a look

Josh, can you take a look at this when you have a chance?

also cc @sameeragarwal

Test build #73223 has started for PR 16499 at commit 320b548.

Test build #73226 has started for PR 16499 at commit 25923f3.

Test build #73223 has finished for PR 16499 at commit 320b548.

This patch passes all tests.
This patch does not merge cleanly.
This patch adds no public classes.

Test build #73226 has finished for PR 16499 at commit 25923f3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Build finished. Test PASSed.

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

Merged build finished. Test PASSed.

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

Test build #74127 has started for PR 16499 at commit 45eb006.

I looked into simply cleaning up the StorageUtils.dispose method to only dispose memory-mapped buffers. However, I did find legitimate uses of that method to dispose of direct/non-memory-mapped buffers. So I kept the behavior of that method as-is. Instead, I added a new method—unmap—which will dispose of memory-mapped buffers only, and added calls to that method where appropriate. At the end of the day, I only found one case where we specifically wanted an "unmap" behavior instead of the other broader disposal behavior. (That case being the one what was causing corruption of replicated blocks in the first place.)
I also found a new memory management bug in BlockManager introduced by the encryption support. In the original codebase, it disposes of a buffer unsafely. I think part of the problem is the documentation of the ChunkedByteBuffer.toByteBuffer method uses the word "copy" in describing what that method does. I expanded and made that method's documentation more precise to clarify that sometimes that method does not return a copy of the data. In those cases, it is not safe to dispose the returned buffer.
I found that there were no uses of ByteBufferInputStream where automatic buffer disposal was called for. Therefore, I dropped that support from that class to guard against unsafe usage. If someone really wants to actually use automatic buffer disposal in ByteBufferInputStream they can—carefully—re-add that support. I think that that's generally unsafe. And, like I said, nothing in the codebase was using it anyway except where it was used incorrectly.

Test build #74127 has finished for PR 16499 at commit 45eb006.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test PASSed.

thanks, merging to master/2.1!
@mallman can you send a new PR for 2.0? thanks!

@mallman can you send a new PR for 2.0? thanks!

Will do. Do I need to open a new JIRA ticket for that?

You do not need to open the new JIRA. You can still use the same JIRA number

Backport PR is #17390