Debugger (GDB) aborting when inspecting custom data type pointers

Hi all,
I have just come across some unexpected behaviour when using GDB, vscode-cpptools and Modern Fortran.
Issue
Debugger aborts when inspecting (or hovering if using FORTRAN IntelliSense) a pointer of a custom data type. This has to be a relatively new bug (last month or so) since it was working perfectly fine before.
I suspect it has something to do with how GDB or Natvis (the thing behind cppdbg) attempts to dereference custom Fortran types, because if I recall correctly for C++ you can dereference a pointer in GDB by print *(type *)variable, however in Fortran this does not seem to be the case and you have to encapsulate this with an artificial array print *((type *)variable)@1, which is what is causing the debugger to abort.
Can people confirm that the example posted below also breaks for them in debug mode, and if so try and I will try to fix it or raise it as an issue to vscode-cpptools.
Possible solution
I think passing to GDB the option set print symbol off might be enough to circumvent this given that VS Code registers the address as HEX_ADDRESS <a>, which disappears when symbols are off. Although I am not sure if it will have other adverse effects or how to even set that option in through launch.json
Minimal example
mwe.f95, compile with gfortran -g mwe.f95 -o mwe.f95
program mwe
  !> MWE where GDB aborts when hovering over pointers of custom types

  implicit none

  type foo
    integer, dimension(:), pointer :: mat => null()
  end type foo

  type(foo), dimension(2), target :: a
  type(foo), pointer :: p => null()
  integer :: i

  do i = 1, size(a)
    allocate(a(i)%mat(5))
  end do

  ! Inspecting or Hovering over this, causes GDB to abort
  p => a(1)

  print*, i ! <-- Place breaking point here

end program mwe

launch.json
{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "FORTRAN (gdb) Launch",
            "type": "cppdbg",
            "request": "launch",
            "program": "${workspaceFolder}/mwe.o",
            "args": [],
            "stopAtEntry": false,
            "cwd": "${workspaceFolder}",
            "environment": [],
            "externalConsole": false,
            "MIMode": "gdb",
            "setupCommands": [
                {
                    "description": "Enable pretty-printing for gdb",
                    "text": "-enable-pretty-printing",
                    "ignoreFailures": true
                }
            ],
            "logging": {
                "engineLogging": true,
                "moduleLoad": true,
                "exceptions": true
            }
        }
    ]
}

Error
1: (28647) <-1050-var-list-children --simple-values "var12" 0 1000
1: (28648) ->~"/build/gdb-kAlH5B/gdb-8.1/gdb/value.c:3116: internal-error: value* value_primitive_field(value*, LONGEST, int, type*): Assertion `PROP_CONST == TYPE_DATA_LOCATION_KIND (type)' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nQuit this debugging session? "
/build/gdb-kAlH5B/gdb-8.1/gdb/value.c:3116: internal-error: value* value_primitive_field(value*, LONGEST, int, type*): Assertion `PROP_CONST == TYPE_DATA_LOCATION_KIND (type)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session?
1: (28648) ->~"(y or n) [answered Y; input not from terminal]\n"
1: (28648) ->&"\nThis is a bug, please report it."
(y or n) [answered Y; input not from terminal]
1: (28649) ->&"  For instructions, see:\n<http://www.gnu.org/software/gdb/bugs/>."
1: (28649) ->&"\n\n"
1: (28649) ->~"/build/gdb-kAlH5B/gdb-8.1/gdb/value.c:3116: internal-error: value* value_primitive_field(value*, LONGEST, int, type*): Assertion `PROP_CONST == TYPE_DATA_LOCATION_KIND (type)' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nCreate a core file of GDB? "
1: (28649) ->~"(y or n) [answered Y; input not from terminal]\n"
/build/gdb-kAlH5B/gdb-8.1/gdb/value.c:3116: internal-error: value* value_primitive_field(value*, LONGEST, int, type*): Assertion `PROP_CONST == TYPE_DATA_LOCATION_KIND (type)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) [answered Y; input not from terminal]
1: (28875) Shell exited, stop debugging
Stopping due to fatal error: AggregateException: One or more errors occurred.

Log
1: (159) LaunchOptions<LocalLaunchOptions xmlns='http://schemas.microsoft.com/vstudio/MDDDebuggerOptions/2014'
1: (181) LaunchOptions  ExePath='/home/gn/Code/Fortran/mwe.o'
1: (181) LaunchOptions  WorkingDirectory='/home/gn/Code/Fortran'
1: (181) LaunchOptions  ExeArguments=''
1: (181) LaunchOptions  MIMode='gdb'
1: (182) LaunchOptions  MIDebuggerPath=''
1: (182) LaunchOptions  WaitDynamicLibLoad='false'
1: (182) LaunchOptions>
1: (182) LaunchOptions    <SetupCommands>
1: (182) LaunchOptions        <Command IgnoreFailures='true' Description='Enable pretty-printing for gdb'>-enable-pretty-printing</Command>
1: (182) LaunchOptions    </SetupCommands>
1: (182) LaunchOptions</LocalLaunchOptions>
1: (268) DbgCmd:echo $$ > /tmp/Microsoft-MIEngine-Pid-4ec4b9g8.xvs ; cd "/home/gn/Code/Fortran" ; DbgTerm=`tty` ; set -o monitor ; trap 'rm "/tmp/Microsoft-MIEngine-In-jg5t1r37.t63" "/tmp/Microsoft-MIEngine-Out-kpuzq7o8.tlz" "/tmp/Microsoft-MIEngine-Pid-4ec4b9g8.xvs" "/tmp/Microsoft-MIEngine-Cmd-bjcu5us9.tjv"' EXIT ; "/usr/bin/gdb" --interpreter=mi --tty=$DbgTerm < "/tmp/Microsoft-MIEngine-In-jg5t1r37.t63" > "/tmp/Microsoft-MIEngine-Out-kpuzq7o8.tlz" & clear; pid=$! ; echo $pid > "/tmp/Microsoft-MIEngine-Pid-4ec4b9g8.xvs" ; wait $pid;
1: (286) Wait for connection completion.
1: (387) ->=thread-group-added,id="i1"
1: (389) ->~"GNU gdb (Ubuntu 8.1-0ubuntu3.2) <IP_ADDRESS>80409-git\n"
1: (389) ->~"Copyright (C) 2018 Free Software Foundation, Inc.\n"
1: (389) ->~"License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law.  Type \"show copying\"\nand \"show warranty\" for details.\n"
1: (390) ->~"This GDB was configured as \"x86_64-linux-gnu\".\nType \"show configuration\" for configuration details."
1: (390) ->~"\nFor bug reporting instructions, please see:\n"
1: (390) ->~"<http://www.gnu.org/software/gdb/bugs/>.\n"
1: (390) ->~"Find the GDB manual and other documentation resources online at:\n<http://www.gnu.org/software/gdb/documentation/>.\n"
1: (390) ->~"For help, type \"help\".\n"
1: (390) ->~"Type \"apropos word\" to search for commands related to \"word\".\n"
1: (390) ->(gdb)
1: (394) <-1001-gdb-set target-async on
1: (394) ->1001^done
1: (394) ->(gdb)
1: (396) 1001: elapsed time 2
1: (404) <-1002-enable-pretty-printing
1: (404) ->1002^done
1: (404) ->(gdb)
1: (404) 1002: elapsed time 0
1: (404) <-1003-interpreter-exec console "set pagination off"
1: (405) ->=cmd-param-changed,param="pagination",value="off"
1: (405) ->1003^done
1: (405) ->(gdb)
1: (405) 1003: elapsed time 0
1: (405) <-1004-gdb-set auto-solib-add on
1: (406) ->1004^done
1: (406) ->(gdb)
1: (406) 1004: elapsed time 0
1: (406) <-1005-gdb-set solib-search-path /home/gn/Code/Fortran:
1: (406) ->1005^done
1: (406) ->(gdb)
1: (406) 1005: elapsed time 0
1: (406) <-1006-gdb-set stop-on-solib-events 1
1: (406) ->1006^done
1: (406) ->(gdb)
1: (406) 1006: elapsed time 0
1: (406) <-1007-environment-cd /home/gn/Code/Fortran
1: (407) ->1007^done
1: (407) ->(gdb)
1: (407) 1007: elapsed time 0
1: (407) <-1008-file-exec-and-symbols /home/gn/Code/Fortran/mwe.o
1: (408) ->1008^done
1: (408) ->(gdb)
1: (408) 1008: elapsed time 1
1: (410) <-1009-interpreter-exec console "show architecture"
1: (410) ->~"The target architecture is set automatically (currently i386:x86-64)\n"
1: (410) ->1009^done
1: (411) ->(gdb)
1: (411) 1009: elapsed time 0
1: (412) <-1010-break-insert -f main
1: (412) ->1010^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x0000000000000c97",func="main",file="mwe.f95",fullname="/home/gn/Code/Fortran/mwe.f95",line="24",thread-groups=["i1"],times="0",original-location="main"}
1: (412) ->(gdb)
1: (415) 1010: elapsed time 3
1: (422) Send Event AD7EngineCreateEvent
1: (424) Send Event AD7ProgramCreateEvent
1: (470) ShellPid=15505
1: (470) DebuggerPid=15507
1: (491) <-1011-break-insert -f mwe.f95:22
1: (491) ->1011^done,bkpt={number="2",type="breakpoint",disp="keep",enabled="y",addr="0x0000000000000c18",func="mwe",file="mwe.f95",fullname="/home/gn/Code/Fortran/mwe.f95",line="22",thread-groups=["i1"],times="0",original-location="mwe.f95:22"}
1: (491) ->(gdb)
1: (492) 1011: elapsed time 1
1: (499) <-1012-symbol-list-lines /home/gn/Code/Fortran/mwe.f95
1: (499) ->1012^done,lines=[{pc="0x00000000000008ea",line="1"},{pc="0x00000000000008f6",line="10"},{pc="0x00000000000009c8",line="14"},{pc="0x00000000000009e3",line="15"},{pc="0x0000000000000b2b",line="16"},{pc="0x0000000000000bfb",line="14"},{pc="0x0000000000000c09",line="16"},{pc="0x0000000000000c0a",line="20"},{pc="0x0000000000000c18",line="22"},{pc="0x0000000000000c7d",line="24"},{pc="0x0000000000000c88",line="24"},{pc="0x0000000000000c97",line="24"},{pc="0x0000000000000cc5",line="0"}]
1: (499) ->(gdb)
1: (501) 1012: elapsed time 1
1: (505) Send Event AD7BreakpointBoundEvent
1: (544) Send Event AD7LoadCompleteEvent
=thread-group-added,id="i1"
GNU gdb (Ubuntu 8.1-0ubuntu3.2) <IP_ADDRESS>80409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
Warning: Debuggee TargetArchitecture not detected, assuming x86_64.
=cmd-param-changed,param="pagination",value="off"
1: (548) <-1013-exec-run
1: (548) ->=thread-group-started,id="i1",pid="15513"
1: (549) ->=thread-created,id="1",group-id="i1"
1: (552) ->=breakpoint-modified,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x0000555555554c97",func="main",file="mwe.f95",fullname="/home/gn/Code/Fortran/mwe.f95",line="24",thread-groups=["i1"],times="0",original-location="main"}
1: (552) ->=breakpoint-modified,bkpt={number="2",type="breakpoint",disp="keep",enabled="y",addr="0x0000555555554c18",func="mwe",file="mwe.f95",fullname="/home/gn/Code/Fortran/mwe.f95",line="22",thread-groups=["i1"],times="0",original-location="mwe.f95:22"}
1: (552) ->=library-loaded,id="/lib64/ld-linux-x86-64.so.2",target-name="/lib64/ld-linux-x86-64.so.2",host-name="/lib64/ld-linux-x86-64.so.2",symbols-loaded="0",thread-group="i1",ranges=[{from="0x00007ffff7dd5f10",to="0x00007ffff7df4b50"}]
1: (552) <-1014-thread-info 1
1: (556) <-1015-symbol-list-lines /home/gn/Code/Fortran/mwe.f95
1: (566) ->1013^running
1: (566) ->*running,thread-id="all"
1: (566) 1013: elapsed time 18
1: (566) ->(gdb)
1: (566) ->1014^done,threads=[{id="1",target-id="process 15513",name="mwe.o",state="running",core="0"}]
1: (566) ->(gdb)
1: (567) 1014: elapsed time 14
1: (569) ->~"Stopped due to shared library event (no libraries added or removed)\n"
1: (570) ->*stopped,reason="solib-event",thread-id="1",stopped-threads="all",core="0"
1: (570) ->1015^done,lines=[{pc="0x00005555555548ea",line="1"},{pc="0x00005555555548f6",line="10"},{pc="0x00005555555549c8",line="14"},{pc="0x00005555555549e3",line="15"},{pc="0x0000555555554b2b",line="16"},{pc="0x0000555555554bfb",line="14"},{pc="0x0000555555554c09",line="16"},{pc="0x0000555555554c0a",line="20"},{pc="0x0000555555554c18",line="22"},{pc="0x0000555555554c7d",line="24"},{pc="0x0000555555554c88",line="24"},{pc="0x0000555555554c97",line="24"},{pc="0x0000555555554cc5",line="0"}]
1: (570) ->(gdb)
1: (570) Send Event AD7ProcessInfoUpdatedEvent
1: (570) Send Event AD7ThreadCreateEvent
Stopped due to shared library event (no libraries added or removed)
1: (581) 1015: elapsed time 24
1: (581) <-1016-interpreter-exec console "shell echo -e \\\\033c 1>&2"
1: (582) Send Event AD7BreakpointUnboundEvent
1: (582) Send Event AD7BreakpointBoundEvent
1: (583) ->1016^done
1: (583) ->(gdb)
1: (584) 1016: elapsed time 2
1: (584) <-1017-gdb-set stop-on-solib-events 0
1: (584) ->1017^done
1: (584) ->(gdb)
1: (584) 1017: elapsed time 0
1: (588) <-1018-interpreter-exec console "info sharedlibrary"
1: (588) ->~"From                To                  Syms Read   Shared Object Library\n"
1: (588) ->~"0x00007ffff7dd5f10  0x00007ffff7df4b50  Yes         /lib64/ld-linux-x86-64.so.2\n"
1: (588) ->1018^done
1: (588) ->(gdb)
1: (589) 1018: elapsed time 1
1: (591) Send Event AD7ModuleLoadEvent
Loaded '/lib64/ld-linux-x86-64.so.2'. Symbols loaded.
1: (592) <--exec-continue
1: (592) ->^running
1: (592) ->*running,thread-id="all"
1: (592) ->(gdb)
1: (593) ->=library-loaded,id="/usr/lib/x86_64-linux-gnu/libgfortran.so.4",target-name="/usr/lib/x86_64-linux-gnu/libgfortran.so.4",host-name="/usr/lib/x86_64-linux-gnu/libgfortran.so.4",symbols-loaded="0",thread-group="i1",ranges=[{from="0x00007ffff7a0f680",to="0x00007ffff7bad707"}]
1: (594) ->=library-loaded,id="/lib/x86_64-linux-gnu/libc.so.6",target-name="/lib/x86_64-linux-gnu/libc.so.6",host-name="/lib/x86_64-linux-gnu/libc.so.6",symbols-loaded="0",thread-group="i1",ranges=[{from="0x00007ffff76262d0",to="0x00007ffff779eeac"}]
1: (594) ->=library-loaded,id="/usr/lib/x86_64-linux-gnu/libquadmath.so.0",target-name="/usr/lib/x86_64-linux-gnu/libquadmath.so.0",host-name="/usr/lib/x86_64-linux-gnu/libquadmath.so.0",symbols-loaded="0",thread-group="i1",ranges=[{from="0x00007ffff73c7420",to="0x00007ffff73ee9fb"}]
1: (594) ->=library-loaded,id="/lib/x86_64-linux-gnu/libm.so.6",target-name="/lib/x86_64-linux-gnu/libm.so.6",host-name="/lib/x86_64-linux-gnu/libm.so.6",symbols-loaded="0",thread-group="i1",ranges=[{from="0x00007ffff7032a80",to="0x00007ffff70f11d5"}]
1: (594) ->=library-loaded,id="/lib/x86_64-linux-gnu/libgcc_s.so.1",target-name="/lib/x86_64-linux-gnu/libgcc_s.so.1",host-name="/lib/x86_64-linux-gnu/libgcc_s.so.1",symbols-loaded="0",thread-group="i1",ranges=[{from="0x00007ffff6e11ac0",to="0x00007ffff6e2236d"}]
1: (817) ->=breakpoint-modified,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x0000555555554c97",func="main",file="mwe.f95",fullname="/home/gn/Code/Fortran/mwe.f95",line="24",thread-groups=["i1"],times="1",original-location="main"}
1: (820) ->~"\n"

1: (820) ->~"Breakpoint 1, main (argc=1, argv=0x7fffffffdbc1) at mwe.f95:24\n"
1: (820) ->~"24\tend program mwe"
Breakpoint 1, main (argc=1, argv=0x7fffffffdbc1) at mwe.f95:24
1: (820) ->*stopped,reason="breakpoint-hit",disp="keep",bkptno="1",frame={addr="0x0000555555554c97",func="main",args=[{name="argc",value="1"},{name="argv",value="0x7fffffffdbc1"}],file="mwe.f95",fullname="/home/gn/Code/Fortran/mwe.f95",line="24"},thread-id="1",stopped-threads="all",core="1"
24	end program mwe
1: (829) <-1019-thread-info
1: (830) ->1019^done,threads=[{id="1",target-id="process 15513",name="mwe.o",frame={level="0",addr="0x0000555555554c97",func="main",args=[{name="argc",value="1"},{name="argv",value="0x7fffffffdbc1"}],file="mwe.f95",fullname="/home/gn/Code/Fortran/mwe.f95",line="24"},state="stopped",core="1"}],current-thread-id="1"
1: (830) ->(gdb)
1: (830) 1019: elapsed time 1
1: (834) <-1020-interpreter-exec console "info sharedlibrary"
1: (834) ->~"From                To                  Syms Read   Shared Object Library\n"
1: (834) ->~"0x00007ffff7dd5f10  0x00007ffff7df4b50  Yes         /lib64/ld-linux-x86-64.so.2\n"
1: (834) ->~"0x00007ffff7a0f680  0x00007ffff7bad707  Yes         /usr/lib/x86_64-linux-gnu/libgfortran.so.4\n"
1: (834) ->~"0x00007ffff76262d0  0x00007ffff779eeac  Yes         /lib/x86_64-linux-gnu/libc.so.6\n"
1: (834) ->~"0x00007ffff73c7420  0x00007ffff73ee9fb  Yes         /usr/lib/x86_64-linux-gnu/libquadmath.so.0\n"
1: (834) ->~"0x00007ffff7032a80  0x00007ffff70f11d5  Yes         /lib/x86_64-linux-gnu/libm.so.6\n"
1: (834) ->~"0x00007ffff6e11ac0  0x00007ffff6e2236d  Yes         /lib/x86_64-linux-gnu/libgcc_s.so.1\n"
1: (834) ->1020^done
1: (835) ->(gdb)
1: (835) 1020: elapsed time 0
1: (835) Send Event AD7ModuleLoadEvent
Loaded '/usr/lib/x86_64-linux-gnu/libgfortran.so.4'. Symbols loaded.
1: (835) Send Event AD7ModuleLoadEvent
Loaded '/lib/x86_64-linux-gnu/libc.so.6'. Symbols loaded.
1: (835) Send Event AD7ModuleLoadEvent
Loaded '/usr/lib/x86_64-linux-gnu/libquadmath.so.0'. Symbols loaded.
1: (835) Send Event AD7ModuleLoadEvent
Loaded '/lib/x86_64-linux-gnu/libm.so.6'. Symbols loaded.
1: (835) Send Event AD7ModuleLoadEvent
Loaded '/lib/x86_64-linux-gnu/libgcc_s.so.1'. Symbols loaded.
1: (839) <-1021-stack-list-frames 0 1000
1: (839) ->1021^done,stack=[frame={level="0",addr="0x0000555555554c97",func="main",file="mwe.f95",fullname="/home/gn/Code/Fortran/mwe.f95",line="24"},frame={level="1",addr="0x00007ffff7626b97",func="__libc_start_main",file="../csu/libc-start.c",fullname="/build/glibc-2ORdQG/glibc-2.27/csu/../csu/libc-start.c",line="310"},frame={level="2",addr="0x000055555555480a",func="_start"}]
1: (840) ->(gdb)
1: (840) 1021: elapsed time 1
1: (846) <-1022-break-delete 1
1: (846) ->1022^done
1: (846) ->(gdb)
1: (846) 1022: elapsed time 0
1: (846) Send Event AD7EntryPointEvent
1: (848) <--exec-continue
1: (848) ->^running
1: (848) ->*running,thread-id="all"
1: (848) ->(gdb)
1: (848) ->=breakpoint-modified,bkpt={number="2",type="breakpoint",disp="keep",enabled="y",addr="0x0000555555554c18",func="mwe",file="mwe.f95",fullname="/home/gn/Code/Fortran/mwe.f95",line="22",thread-groups=["i1"],times="1",original-location="mwe.f95:22"}
1: (848) ->~"\n"
1: (848) ->~"Breakpoint 2, mwe () at mwe.f95:22\n"
1: (848) ->~"22\t  print*, i ! <-- Place breaking point here\n"
1: (848) ->*stopped,reason="breakpoint-hit",disp="keep",bkptno="2",frame={addr="0x0000555555554c18",func="mwe",args=[],file="mwe.f95",fullname="/home/gn/Code/Fortran/mwe.f95",line="22"},thread-id="1",stopped-threads="all",core="1"

Breakpoint 2, mwe () at mwe.f95:22
22	  print*, i ! <-- Place breaking point here
1: (849) <-1023-stack-list-frames 0 1000
1: (850) ->1023^done,stack=[frame={level="0",addr="0x0000555555554c18",func="mwe",file="mwe.f95",fullname="/home/gn/Code/Fortran/mwe.f95",line="22"},frame={level="1",addr="0x0000555555554cbe",func="main",file="mwe.f95",fullname="/home/gn/Code/Fortran/mwe.f95",line="24"},frame={level="2",addr="0x00007ffff7626b97",func="__libc_start_main",file="../csu/libc-start.c",fullname="/build/glibc-2ORdQG/glibc-2.27/csu/../csu/libc-start.c",line="310"},frame={level="3",addr="0x000055555555480a",func="_start"}]
1: (850) ->(gdb)
1: (850) 1023: elapsed time 1
1: (853) Send Event AD7BreakpointEvent
Execute debugger commands using "-exec <command>", for example "-exec info registers" will list registers in use (when GDB is the debugger)
1: (896) <-1024-stack-list-arguments 0 0 3
1: (897) ->1024^done,stack-args=[frame={level="0",args=[]},frame={level="1",args=[name="argc",name="argv"]},frame={level="2",args=[name="main",name="argc",name="argv",name="init",name="fini",name="rtld_fini",name="stack_end"]},frame={level="3",args=[]}]
1: (897) ->(gdb)
1: (897) 1024: elapsed time 1
1: (900) <-1025-stack-select-frame 1
1: (901) ->1025^done
1: (901) ->(gdb)
1: (902) 1025: elapsed time 1
1: (902) <-1026-var-create - * "argc"
1: (904) ->1026^done,name="var1",numchild="0",value="1",type="integer(kind=4)",thread-id="1",has_more="0"
1: (905) ->(gdb)
1: (905) 1026: elapsed time 2
1: (905) <-1027-var-delete var1
1: (906) ->1027^done,ndeleted="1"
1: (906) ->(gdb)
1: (906) 1027: elapsed time 0
1: (907) <-1028-var-create - * "argv"
1: (909) ->1028^done,name="var2",numchild="1",value="0x7fffffffdbc1",type="PTR TO -> ( character(kind=1) )",thread-id="1",has_more="0"
1: (909) ->(gdb)
1: (909) 1028: elapsed time 2
1: (909) <-1029-var-delete var2
1: (910) ->1029^done,ndeleted="1"
1: (910) ->(gdb)
1: (910) 1029: elapsed time 0
1: (910) <-1030-stack-select-frame 2
1: (910) ->1030^done
1: (910) ->(gdb)
1: (910) 1030: elapsed time 0
1: (910) <-1031-var-create - * "main"
1: (911) ->1031^done,name="var3",numchild="0",value="0x555555554c88 <main>",type="int (*)(int, char **, char **)",thread-id="1",has_more="0"
1: (911) ->(gdb)
1: (911) 1031: elapsed time 0
1: (911) <-1032-var-delete var3
1: (911) ->1032^done,ndeleted="1"
1: (911) ->(gdb)
1: (911) 1032: elapsed time 0
1: (911) <-1033-var-create - * "argc"
1: (912) ->1033^done,name="var4",numchild="0",value="1",type="int",thread-id="1",has_more="0"
1: (912) ->(gdb)
1: (912) 1033: elapsed time 0
1: (912) <-1034-var-delete var4
1: (912) ->1034^done,ndeleted="1"
1: (912) ->(gdb)
1: (912) 1034: elapsed time 0
1: (912) <-1035-var-create - * "argv"
1: (913) ->1035^done,name="var5",numchild="1",value="0x7fffffffd7b8",type="char **",thread-id="1",has_more="0"
1: (913) ->(gdb)
1: (913) 1035: elapsed time 0
1: (913) <-1036-var-delete var5
1: (913) ->1036^done,ndeleted="1"
1: (913) ->(gdb)
1: (913) 1036: elapsed time 0
1: (913) <-1037-var-create - * "init"
1: (914) ->1037^done,name="var6",numchild="0",value="<optimised out>",type="int (*)(int, char **, char **)",thread-id="1",has_more="0"
1: (914) ->(gdb)
1: (914) 1037: elapsed time 0
1: (914) <-1038-var-delete var6
1: (914) ->1038^done,ndeleted="1"
1: (914) ->(gdb)
1: (915) 1038: elapsed time 0
1: (915) <-1039-var-create - * "fini"
1: (915) ->1039^done,name="var7",numchild="0",value="<optimised out>",type="void (*)(void)",thread-id="1",has_more="0"
1: (915) ->(gdb)
1: (915) 1039: elapsed time 0
1: (915) <-1040-var-delete var7
1: (915) ->1040^done,ndeleted="1"
1: (915) ->(gdb)
1: (916) 1040: elapsed time 0
1: (916) <-1041-var-create - * "rtld_fini"
1: (916) ->1041^done,name="var8",numchild="0",value="<optimised out>",type="void (*)(void)",thread-id="1",has_more="0"
1: (916) ->(gdb)
1: (916) 1041: elapsed time 0
1: (916) <-1042-var-delete var8
1: (916) ->1042^done,ndeleted="1"
1: (916) ->(gdb)
1: (916) 1042: elapsed time 0
1: (916) <-1043-var-create - * "stack_end"
1: (917) ->1043^done,name="var9",numchild="0",value="0x7fffffffd7a8",type="void *",thread-id="1",has_more="0"
1: (917) ->(gdb)
1: (917) 1043: elapsed time 0
1: (917) <-1044-var-delete var9
1: (917) ->1044^done,ndeleted="1"
1: (917) ->(gdb)
1: (917) 1044: elapsed time 0
1: (1357) <-1045-stack-select-frame 0
1: (1358) ->1045^done
1: (1358) ->(gdb)
1: (1360) 1045: elapsed time 2
1: (1360) <-1046-stack-list-variables 0
1: (1360) ->1046^done,variables=[{name="a"},{name="i"},{name="p"}]
1: (1360) ->(gdb)
1: (1360) 1046: elapsed time 0
1: (1372) <-1047-var-create - * "a"
1: (1380) ->1047^done,name="var10",numchild="2",value="[2]",type="Type foo (2)",has_more="0"
1: (1380) ->(gdb)
1: (1380) 1047: elapsed time 8
1: (1380) <-1048-var-create - * "i"
1: (1386) ->1048^done,name="var11",numchild="0",value="3",type="integer(kind=4)",thread-id="1",has_more="0"
1: (1386) ->(gdb)
1: (1386) 1048: elapsed time 5
1: (1387) <-1049-var-create - * "p"
1: (1391) ->1049^done,name="var12",numchild="1",value="0x555555756040 <a>",type="PTR TO -> ( Type foo )",has_more="0"
1: (1391) ->(gdb)
1: (1391) 1049: elapsed time 4

I have confirmed the issue across fresh installs of VS Code and VS Code Insiders in Ubuntu 18.04 and 20.4, hence I have went ahead and escalated the issue to vscode-cpptools, track here

I can confirm that this is an actual bug with GDB, see tracker here: https://sourceware.org/bugzilla/show_bug.cgi?id=23051 and a patch has been fixed although from what I can tell it is still not in any of the releases (9.2) as of this time.
So if anyone else encounters this bug you will need at least a version greater than 9.2 or simply checkout the current version of GDB and build from source.
Latest current version is <IP_ADDRESS>01009-git and I can confirm the bug has been patched.


Illegal instructions (SSE4) in go1.19+ -race builds (fails on some Intel Atom cores)

What version of Go are you using (go version)?

go version go1.19rc1 linux/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
linux/amd64
What did you do?
go build -race generates SSE4 instruction(s) that are executed on non-SSE4 capable CPUs (old Intel Atom).
(pinsrq specifically)
go1.18 works as expected
What did you expect to see?
program should run
What did you see instead?
crash, no output, fails in early runtime:
$ ./program
Illegal instruction

using gdb:
Program received signal SIGILL, Illegal instruction.
0x0000000000431737 in __sanitizer::SizeClassAllocator32LocalCache<__sanitizer::SizeClassAllocator32<__sanitizer::AP32> >::Refill(
__sanitizer::SizeClassAllocator32LocalCache<__sanitizer::SizeClassAllocator32<__sanitizer::AP32> >::PerClass*, __sanitizer::SizeC
lassAllocator32<__sanitizer::AP32>*, unsigned long) ()

...
   0x0000000000431726 <+406>:   movdqa %xmm1,%xmm0
   0x000000000043172a <+410>:   mov    $0x14,%edx
   0x000000000043172f <+415>:   shl    $0x4,%rax
   0x0000000000431733 <+419>:   shl    $0xa,%rdi
=> 0x0000000000431737 <+423>:   pinsrq $0x1,%rax,%xmm0
   0x000000000043173e <+430>:   mov    %rsi,%rax
   0x0000000000431741 <+433>:   add    $0x1,%rsi
   0x0000000000431745 <+437>:   movups %xmm0,0x8(%rbx,%rdi,1)

Sounds like we need an -march when building the race detector.
I see this only in the linux .syso. The others seem fine for some reason.

This was done intentionally in https://reviews.llvm.org/D106948
I'm not sure if there's anything we can do here. We could conceivably remove that patch and rebuild, but I'm not sure what the implications would be. Presumably just performance? The other OSes don't bump up the requirement, so it presumably still works without it.
The other option would be to require sse4 when running with -race. In that case, we should provide a better error message.
@dvyukov

Getting rid of the -msse=4.2 does fix the problem, and introduces no others that I can see. We should probably revert the Go parts of the tsan patch I mentioned.
@thanm This hasn't reached the windows .syso yet, but it will once the changes you're working on land. We should coordinate the rollback so we don't introduce a sse41 dependency in the new windows .syso.

It looks to me like the low-power Atom cores didn't support this until 2013 and in some cases 2016.
Might it be possible to have slower fallback paths should they be required?  These older cores are still quite prevalent in some places.

I suspect a runtime switch will be too expensive. Besides the load-check-branch itself, inlining both version or adding a call will break register alloc.
A separate build of syso files is possible, though. Theoretically we could provide both syso files and select one during linking...
Or just provide a fallback version somewhere on the side and tell people to copy it over.
A proper runtime check in the tsan runtime would be good. The info should be somewhere in CPUID, right?

A separate build of syso files is possible, though. Theoretically we could provide both syso files and select one during linking...

Yes, we could condition on the GOAMD64 version. Currently only the compiler looks at that, but the linker could also.

A proper runtime check in the tsan runtime would be good. The info should be somewhere in CPUID, right?

Yes. There's probably a whole set that are required by -m=sse4.2. Go has code to read them in internal/cpu/cpu_x86.{go,s}.
Do you know how much adding -msse4.2 helps? I'd rather just leave it out and not have people need to jump through hoops. Especially at this point in the release cycle for 1.19. We can get fancier for 1.20.

Running some randomly selected TensorFlow C++ tests with -msse4.2:
test 1: Stats over 100 runs: max = 65.4s, min = 13.8s, avg = 39.5s, dev = 11.9s
test 2: Stats over 100 runs: max = 164.0s, min = 77.9s, avg = 96.5s, dev = 11.8s
test 3: Stats over 100 runs: max = 77.8s, min = 13.7s, avg = 39.3s, dev = 16.0s
test 4: Stats over 100 runs: max = 21.8s, min = 8.2s, avg = 13.9s, dev = 2.9s
test 5: Stats over 100 runs: max = 37.9s, min = 22.5s, avg = 28.6s, dev = 3.8s

without -msse4.2:
test 1: Stats over 100 runs: max = 111.6s, min = 13.2s, avg = 43.7s, dev = 18.4s
test 2: Stats over 100 runs: max = 134.7s, min = 80.4s, avg = 106.3s, dev = 8.9s
test 3: Stats over 100 runs: max = 89.0s, min = 17.3s, avg = 50.2s, dev = 17.4s
test 4: Stats over 100 runs: max = 25.0s, min = 9.8s, avg = 16.9s, dev = 3.1s
test 5: Stats over 100 runs: max = 43.9s, min = 20.4s, avg = 30.4s, dev = 5.1s

For avg time this is -9.6%, -9.2%, -21.7%, -17.8%, -5.9% with -msse4.2.

I'm ok with a ~15% slowdown, to keep -race working on older processors.
We can come up with GOAMD64 versioning scheme for 1.20.

I'll put together an LLVM CL for this later in the week.

Sent https://reviews.llvm.org/D129482 with change to Go build scripts.

LLVM change is submitted.  I will work on sending another CL that updates the linux, freebsd, and darwin syso images.

OK, I am going to submit CL 416857, which should resolve this. Note that this updates darwin, freebsd, and linux. The current windows/amd64 syso is old enough that it shouldn't have the problem, and for openbsd/netbsd there are other things blocking the update.

@thanm thanks! I confirm this is working.


St-pages doesn't work properly on Streamlit Cloud environment

I have an app with a very simple structure. I use st-pages there and everything works fine on my server. However when I send it to the Streamlit cloud, the pages names aren't rendered properly.
I know it may be related to environment, because the app works on my server, however maybe something can be changed to support Streamlit cloud as well?
Here is my code and deployed app:
https://github.com/patrykpalej/Real-Estate-Market-Analysis-dashboard/
https://real-estate-market-pl.streamlit.app/
Btw. I tried to setup my app with multiple combination in terms of setting PYTHONPATH, append sys.path etc. It looks like the behaviour was indeterministic, because sometimes it works, sometimes it doesn't and I cannot tell what's wrong and why.

I'm not really sure why this is happening, but I think it has something to do with the fact that importing this file actually runs some code, because if I move the connection_string code inside of the fetch_and_preprocess it works for me. I would recommend doing that in general -- don't make importing a module actually run code.
I would also highly recommend you look into st.secrets for your credentials, rather than using os.environment https://docs.streamlit.io/streamlit-community-cloud/deploy-your-app/secrets-management, but that's probably unrelated.

You mean such a change? -> https://github.com/patrykpalej/Real-Estate-Market-Analysis-dashboard/blob/master/functions/data_loading.py
I rebooted the app in the cloud after push but pages names still aren't visible. Did you mean that it works for you locally or in the cloud? In my local environment it works as well. The only problem is in the streamlit cloud.
I will try st.secrets, havn't heard about it before.

Heyo I have the same problem.
It seems to apply the layout wide but nothing else.
https://github.com/Yelinz/commute-city-triangulation/blob/777ea3f66416d21277b48713788cde1f8391bf75/main.py#L19
https://commute-triangulation.streamlit.app/

@blackary I had the same problem and solved it adding "is_section=true" at the last page of my page list.
Seems that for it to work on Streamlit Cloud now at least 1 page has to have "is_section=true". If none have it doesn't work.

This is very likely resolved in the latest release of st-pages


Pull request as the new scrum master

Hey Mr. Mort,
Heres my team's updated pull request, I re-forked your repo and made the changes and added features, there should be no errors.

This was easy for you!  Thanks.


Ruby LSP Rails error: uninitialized constant RubyLsp::Rails::Server::ActiveRecord

Ruby version
3.2.2
Code snippet
No response
Description
Is anyone else encountering "Ruby LSP Rails error: uninitialized constant RubyLsp::Rails::Server::ActiveRecord" which blocks them from being able to use the formatting feature of the language server?
My application uses bundle and rbenv, and rubocop is active in my repo.
Also, this issue has only started recently. Everything was working as supposed until a few days ago.

 I really enjoy the formatting tool.
Thanks!
Expected output
Being able to run a Format Document and have it work.

Also,
gem update ruby-lsp
Updating installed gems
Nothing to update
Gems already up-to-date: ruby-lsp

gem update ruby-lsp-rails
Updating installed gems
Nothing to update
Gems already up-to-date: ruby-lsp-rails

:wave: Is your app a Rails app that doesn't use ActiveRecord?
I suspect we need to update https://github.com/Shopify/ruby-lsp-rails/blob/618d267d920e8a3c944134f5b1e0acf344fea3af/lib/ruby_lsp/ruby_lsp_rails/server.rb#L32 to handle that case.


Look at ... statsforecast

https://github.com/Nixtla/statsforecast

Steps:

Create colab notebook example hello_statsforecast  (similar to hello_divinity)
Make a pull request at timeseries-notebooks

OR ... maybe we just use it via sktime

Duplicate.


Preview is zoomed on Android

The camera preview is very zoomed in, but when I take a photo it comes out normal. This only happens on Android. Is this a bug, or is there any way to control the zoom?
I have also noticed if I set the height of the preview to around 300, it's not zoomed in, but the higher the height, the more zoomed in it gets.
I'm using Camera Plus with Nativescript Vue. I've implemented it like so:
app.js
import Camera from './components/Camera';
const CameraPlus = require("@nstudio/nativescript-camera-plus");

Vue.registerElement('CameraPlus', () => CameraPlus.CameraPlus);

const app = new Vue({
  template: `
        <Frame>
            <Camera />
        </Frame>`,
  components: {
    Camera,
  },
});

app.$start();

camera.vue
<template lang="html">
  <Page>
      <CameraPlus></CameraPlus>
  </Page>
</template>

Tested on Android 9 and 10 with Camera Plus v3.0.7

I am also face this issue and my workaround is to using camera plus version 2.2.7 instead.
But another issue is if you run it on android below 5.1 or 5.0 it will crashed the app.

Fixed: https://github.com/nstudio/nativescript-camera-plus/commit/b24997c918df8ceafb73443708a58708be46d5ed feel free to reopen :- update to 3.1.x


GSSOC'24 : Want to add project under web development

Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like.
I want to add "YogaInfo" static website. This can be basic web development project.
Describe alternatives you've considered.
Tech stack: HTML, CSS
Add any other context or screenshots about the feature request here.
No response

@Yashoda2003 Share screenshots for better understanding.

Screenshot of YogaInfo website


update zsync2 - Report status message failed digest verification

update zsync2 - Report status message failed digest verification #143

Cool thanks,


Hud10837/raster layer file kotlin

Another tiny kotlin conversion! This one turned out very small because I've completely removed the permission requests at runtime due to the scoped storage. Main concern is the offline data section in the readme, which I tried to shorten up.
@Rachael-E can you do a first review? Thanks!

@Rachael-E that's everything changed now, thanks for that! Can you take another look?

Thanks for that! @sorenoid can you take a second look?


Classify blocks as handwritten or printed text

🚀 The feature
It would be good to have a classifier internally which can distinguish blocks as handwritten or printed text. This is useful because most of the documents that I have seen has both the elements and while sometimes handwritten is important that the treatment of handwritten data is done differently than printed text data.
Motivation, pitch
I am working on extracting text from medical documents which has some parts such as hospital and doctor details as printed text and medicine name and dosage as hand written text. I would want to be able to treat them differently while running text extraction.
Alternatives
No response
Additional context
https://github.com/awslabs/handwritten-text-recognition-for-apache-mxnet
No response

We are internally working on handwritten text recognition, it could indeed useful to work as well on a classifier to determine the type of the text above the text recognition model.

Did anyone make any progress on this feature?

@charlesmindee we're keenly interested in the handwritten text recognition feature as well. Has there been any progress or can you provide an estimated timeline?


I did the HACS installation, but then what...?

I don't know if this project has been abandoned or not, but after adding the repository to HACS as "integration", I then searched for it, installed it and rebooted HA.
Now I am lost because I don't know what's the next step...? 🤔

https://github.com/smartHomeHub/SmartIR#platform-setup-instructions

Once you add it to configuration.yaml and restart, you'll see a new entity in HA. If not, you might have some kind of configuration issue. This is how mine looks and I've been using it just fine for my thermostats

Thanks @devbyaccident found it finally! 😁


add a small utility that prepends a timestamp to each line of output …

…of another program

usage example:
vmstat 1 5 | ./bin/timestamper.py

lgtm, did you notice any overhead with this timestamper approach ? Specially for the formatting...

No, and I don't think we will...at least for the initial use case I have in mind and the way it handles output logging.  I could make this a lot more complicated but have chosen not to for the time being.


SubscriptOutOfBounds error rolling over context menu item Extract Method

Per discussions in #feedback channel on discord ...
Mac 11.4 BigSur, GlamorousToolkitOSX64-v0.8.751
Reproduction Case:

Open Playground and debug 3+4
Inside debugger, expand 2nd frame
Right mouse then open context menu
Roll down over menu items. When trying to roll over Extract Method option, get SubscriptOutOfBounds error.

Video:
https://user-images.githubusercontent.com/36212516/125140148-b9c87280-e0c6-11eb-93a7-3d2c6612465b.mov
Stack:
20210709_Glamorous_menu_bug.txt

Thanks!


JSONNull is being emitted for optional values

// To parse the JSON, add this file to your project and do:
//
//   let coordinate = try? JSONDecoder().decode(Coordinate.self, from: jsonData)

import Foundation

struct Coordinate: Codable {
    let latitude, longitude: Double?
}

// MARK: Encode/decode helpers

class JSONNull: Codable {
    public init() {}

    public required init(from decoder: Decoder) throws {
        let container = try decoder.singleValueContainer()
        if !container.decodeNil() {
            throw DecodingError.typeMismatch(JSONNull.self, DecodingError.Context(codingPath: decoder.codingPath, debugDescription: "Wrong type for JSONNull"))
        }
    }

    public func encode(to encoder: Encoder) throws {
        var container = encoder.singleValueContainer()
        try container.encodeNil()
    }
}

Wow! We found a GitHub bug (that this issue was closes by the PR).

I'm guessing they're only searching for a string like "Fix(es)? #9999", and don't care whether it's in an unchecked box.

Could you guys provide a documentation how to use JSONNull class, please?


[Question] When I build my RN App with Xcode in Release mode, the build fails: RCTLog.h not found

I had created the main.jsbundle  with this command:
react-native bundle --dev false --entry-file index.ios.js --platform ios --bundle-output main.jsbundle
My header search paths on Release:
$(SRCROOT)/../react-native/React (recursive)
$(SRCROOT)/../node_modules/react-native/React (recursive)
$(SRCROOT)/../../React (recursive)
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include (non-recursive)
$(inherited) (non-recursive)
And yes, the file RCTLog.h exists in this folder:
/node_modules/react-native/React/Base
RN: 0.19.0
RN-Cli: 0.1.10
xCode: 7.2.1
iPhone: 6
iOS: 9.2.1

@facebook-github-bot label iOS

Hi there!
A couple of ideas:

You might want to try updating to the latest version of React Native -- we always have a bunch of bugfixes in each release.
This is probably a question better suited for StackOverflow :)

Best of luck!


Remove anything related to eduGAIN

This issue is imported from pivotal - Originaly created at Mar 27, 2019 by Thijs Kinkhorst
We don't want EB to be producting eduGAIN metadata. Remove anything related to eduGAIN metadata production (also config settings ).

Phase 1: Remove the bulk of the eduGAIN data from Corto. Some aspects have been left in place as they had been used for other purposes over time (EdugainDocument) https://github.com/OpenConext/OpenConext-engineblock/pull/767.
Phase 2: this should allow us to further clean up the Corto metadata classes including the leftover EdugainDocument class. As we are moving all of the logic into the new codebase. (Michiel Kodde - Sep 30, 2019)

We opted for the safe two stage removal.
Opened a 6.2 ticket to remove the remaining eduGAIN fields from the project
https://www.pivotaltracker.com/story/show/168893683 (Michiel Kodde - Oct 2, 2019)


visualize

Thanks for your excellent work，can you tell me how to visualize the result？

Hi, thanks for your interest. We follow the code in Forecast-MAE to do visualization. And there are some basic tools in argo repo.


Confusing paragraph in Configure Spiffs wiki

In the wiki for configuration:
"Now, you need to define the spiffs logical page size. The logical page size must be an integer multiple of the logical block size. You probably want several pages (>16) per block in order to utilize the flash efficiently. A logical page is the smallest data holder element in spiffs."
This doesn't really make sense to me. How can the logical page size be an integer multiple of the logical block size? You would not be able to have more pages than blocks if that were the case.

Oops. It should say The logical block size must be an integer multiple of the logical page size.
Thanks for the headsup.


How do you install and run the program?

Hi,
I'm trying to run that program but there are no guidance for installation.
Can you provide one please?
Cheers,

Download files and run  file (.sln) with Visual Studio.


Can I merge Javascript files into one file?

Hello,
Can I merge hyphen.js and many Javascript patterns files into one?
Thank you!
Gustavo

Hi @gusbemacbe,
Technically you can merge many pattern files together, every pattern collection will live in hyphenationPatterns[Locale_code] variable, for example hyphenationPatternsEnGb or hyphenationPatternsDe; or can be imported using AMD or Node import.
var hyphenationPatternsDe = require('patterns/de');

Then you initiate your hyphenate function with createHyphenator
var hyphenate = createHyphenator(hyphenationPatternsDe);

I updated to GitHub pages. I copied these codes and pasted into HTML file and it did not work. I also copied the codes from your JSFiddle demo and it did not work either. I do not know why. My template got ugly and I do not know how to fix it.
Please, check my HTML file:
https://github.com/gusbemacbe/bootstraphyphen/blob/master/teste.html
And to view the page:
https://gusbemacbe.github.io/bootstraphyphen/teste.html

@gusbemacbe there's a resource loading problem on your demo page, press F12 and check the Console tab in your browser

I'm using a Mac and F12 took me to the Dashboard. What is the button in Mac?

I got. Here's the console result.

Do I have to change HTTP to HTTPS?
And how to fix the Github links?

@gusbemacbe I made a Pull request for your demo page, merge it with your project

@gusbemacbe in short, you should load files from other origins through https protocol and use root paths './' to load local files

I merged, but the texts disappeared. I thought that with adding of id= home ka doesn't work for multiples attributes in an id.

@gusbemacbe I opened an issue in your project, lets continue conversation there


Error with username in channel

WARN There was an error sending a matrix event SyntaxError: Invalid regular expression: /Smiley  =)/: Unmatched ')'
WARN There was an error sending a matrix event     at DiscordBot.HandleMentions (/root/matrix-appservice-discord/build/src/bot.js:228:33)
WARN There was an error sending a matrix event     at DiscordBot.MatrixEventToEmbed (/root/matrix-appservice-discord/build/src/bot.js:132:35)
WARN There was an error sending a matrix event     at DiscordBot.<anonymous> (/root/matrix-appservice-discord/build/src/bot.js:148:32)
WARN There was an error sending a matrix event     at next (native)
WARN There was an error sending a matrix event     at fulfilled (/root/matrix-appservice-discord/build/src/bot.js:4:58)
WARN There was an error sending a matrix event     at process._tickCallback (internal/process/next_tick.js:109:7)

Looks like I might not be escaping these properly. I'll take a look

For reference: This is preventing messages from being sent. The error only occurs when a matrix message is received. Discord -> Matrix is fine

Update: this seemingly breaks all outbound messages to discord, even for unrelated channels/guilds.

This appears to be fixed. Closing


⚠ Minecraft has degraded performance

In 76e439f, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 972 ms

Resolved: Minecraft performance has improved in c21492d.


opsctl open -a cloudprovider for CAPA and CAPG clusters

opsctl needs updating to support CAPA and CAPG clusters when performing opsctl open -a cloudprovider

I will split this issue into 2 separate ones because the implementation is probably going to be different between CAPA & CAPG.


Design and implement ability to fetch ops earlier on boot

Problem statement:

With snapshot caching in ODSP driver, we load (most of the time) from old snapshot.
We pause op processing not to impact boot perf
When ops are resumed, we make request to storage to get up-to-date, but it is short circuited in driver and ops from snapshot are returned. Only when we connect to socket and realize the gap we issue another request to storage to fill in the gap.

This leads to very visible and long delay (reported by users) in getting up-to-date.
The potential solution could look something like that:

When booting container, immediately request ops. I.e. it should be not tied to non-paused state.
We should change driver API to be explicit about end marker. I.e. instead of DeltaManager assuming that if less than 2000 ops are returned that means there are no more ops, the interface should convey if there are more ops available or not as part of return result.

existing logic around less than 2K ops returned moves into drivers.
When ODSP driver satisfies ops using data in snapshot, it always returns end: false, and runtime asks for more, resulting in request to real storage.

Note that this is not breaking change, as changes are in the same layer (loader).

Note that this is not breaking change, as changes are in the same layer (loader).

This item is addressed by PR https://github.com/microsoft/FluidFramework/pull/4905
The only remaining piece is 2K granularity / fetching many chunks concurrently - tracked by issue https://github.com/microsoft/FluidFramework/issues/5211


Add plugin to remove style and AngularJS directives

There are many HTML tags which are not used to index a page. For example color of an element does not affect the search result. This plugin removes such attribute and tags:

color
draggable
width
height
style

The AngularJS plugin removes directives from the HTML code. Here is a list of them:

ng-controller|data-ng-controller
ng-app|data-ng-app
ng-style
ng-class
...

Interesting! I don't think this is something we want to enable by default with our Prerender server but feel free to host this as your own plugin that people can easily pull into their Prerender server.
Our goal is to render the full HTML of the page and leave it as-is for the crawlers, even if some of those tags aren't used for indexing. We haven't had any complaints yet on page sizes being too big after rendering.
Thanks for making this though!

Dear @thoop
Thanks to your response. However, the rendered page is about 2M and some crawler (such as Bing) warned me about the file size. I add this one to my instance to reduce the size of the file size.
Thank you so much.

Glad it worked well for you! Feel free to publish it as a standalone plugin that can be installed with an npm install and used in the prerender server that way.


(Feature) #1460 User should have clear instructions to share link

Description
Add a new screen for send/receive transaction confirmation.
About #1460
How Has This Been Tested?
You should be running on the Web:
Try to send or request a specific amount of G$ and go to the last step (confirmation).
See the new screen.
Checklist:

[x] PR title matches follow: (Feature|Bug|Chore) Task Name
[x] My code follows the style guidelines of this project
[x] I have followed all the instructions described in the initial task (check Definitions of Done)
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have added reference to a related issue in the repository
[x] I have added a detailed description of the changes proposed in the pull request. I am as descriptive as possible, assisting reviewers as much as possible.
[x] I have added screenshots related to my pull request ( for frontend tasks)
[x] I have pasted a gif showing the feature.
[x] @mentions of the person or team responsible for reviewing proposed changes

Video:
https://drive.google.com/a/nordwhale.com/file/d/1DR-HuAnG4U_97qmTLiMyVEcIO0LYGuhf/view?usp=drivesdk
Screenshots:

Browser
Simulators

@LiavGut

@LiavGut where in the image you shared is it not distributed equally?
please mark on the image the spaces you want to be equal

@LiavGut where in the image you shared is it not distributed equally?
please mark on the image the spaces you want to be equal

@sirpy the image I've shared earlier is the one that I've fixed.

@LiavGut See updated screenshots:


Added handlebars-layouts to the in-the-wild list

I've written a set of helpers which implement layout blocks similar to Jade, Jinja, Swig, Twig, and others. It seems to be gaining some popularity (around 10k npm downloads per month at present) and I would be honored to have it included in the in-the-wild list in case it may prove useful to others.

Thank you kindly!

Released in 3.0.3


How disable gesture?

How disable gesture in single view controller?

Hi @Viher-Sano,
If you don't want to use Pan Gesture then you can disable it from FAPanelConfigurations using "canRecognizePanGesture". Just set this property to false.
Thanks & Regards

Thanks!


Update to latest dependencies

Description
Prepare kn-plugin-source-kafka to next release.
Changes

Upgrade kn-source-pkg to latest master
Upgrade relevant knative.dev depdencies

/retest

/lgtm
/approve


How do I link to a file?

I have used some code from an external package which is not exported and I would like to create some link/see reference to it so others will know where this is coming from and if it is maybe exported in the future to remove it.
Is using @see the right way? I could not find anything about js/tsdoc and file urls. But @link in this case does not really get the file url correctly because of the at in angualr and asks for some hash.

maybe you cna try the import("node_modules...forms.js") syntax

But I do not want to import something just tell the next person that this is copied from there because it is not exported.

Any solution please post here. It's the most relevant answer to Google search. https://google.com/?q=tsdoc+link+to+file

in vscode u can use :
file://./ to link to any file (after the file:// u need a . for relative files)
aside from that you cna try the markdown syntax test but ive only gotten that one to work with absolute paths

At this time, it does not seem supported:
https://tsdoc.org/pages/tags/link/
I can confirm that the solution from @jonnytest1 works on the command block for vs-code,

but the tooltip doesn't recognize the format

It might be useful if a team mostly uses vs-code, although it would be nice to have something native in the spec.

ok i did a bit more testing :
you can
 /**
   * @see [test](./file.ts)
   */

this link appears in the tooltip

How is this still an issue? Just tried it and none of the suggestions above work in Windows. :(

Agreed. Would be a nice feature to have or atleast a recommended work around that works

Any progress? I'm not big on the idea of an import that is otherwise useless.

Is there solution for this in 2024? This issue is quite crippling good people who want to write good docs for the rest of us :)

Combine https://github.com/microsoft/tsdoc/issues/250#issuecomment-1125377668 and https://github.com/microsoft/tsdoc/issues/250#issuecomment-1125894137 into
/**
 * @see [file://./file.ts](./file.ts)
 */

and you'll get something that works in editor as well as in tooltip.
Though using @link and an import type might be enough while being less ugly, since import type should not affect any runtime behavior.


escape special characters in test filepath (#114)

This escapes special characters to allow tests to be run even if they have special characters in the test file filepath.
This fixes the issue when running the development (debugging mode). I've attempted to add a test, although I was unable to get the tests on master passing as-is, so I've not made much progress with this. My concern with the addition of this test is that it might just be ignored if the new behaviour is reverted, and as it won't be run it won't fail.

@MGough thx for your contribution. Test-Suite is not working yet. Needs some work.


CommonsChunkPlugin "names" order-importance confusion

As per #1016 it appears that the order of names in CommonsChunkPlugin is important and can cause a lot of confusion.
Webpack  version: 1.13.1.
For example I was trying to separate react and react-dom into their own files.
Entry:
const entry = {
   ...,
   'reactlib': ['react'],
   'reactdomlib': ['react-dom']
};

Config A:
new webpack.optimize.CommonsChunkPlugin({
    names: [
        "reactlib",
        "reactdomlib"
    ],
    minChunks: Infinity
})

(with Config A reactdomlib gets quite big, and reactlib very small)
Config B:
new webpack.optimize.CommonsChunkPlugin({
    names: [
        "reactdomlib",
        "reactlib"
    ],
    minChunks: Infinity
})

Configs A and B produce different results (B appears to be correct, "reverse" order as per #1016).
But "reverse" exactly with respect to what?
This can really trip people up so I think we should mention something about it on the documentation page.
Can someone please explain what's going on there?
My goal is to have the flexibility to have separate files for each library (i.e. react.js, react-router.js, react-dom.js) or to arbitrarily combine (i.e. react and react-dom and react-router go into react.js).
Edit: Fixed react-router typo to react-dom

@webpack-bot I hate those bots...


CSG: Shapes created and then re-parented don't work correctly

Godot version:
Built from current master
OS/device including version:
Windows 7
GTX 760
Issue description:
Adding a CSG shape to the root of a scene, setting the operator, and then re-parenting it to another CSG shape results in the operation not working in the editor (it seems okay when the scene is run).
Steps to reproduce:

Add spatial root node
Add CSG shape
Add another CSG shape to the root of the scene and set it's operation to subtract or intersect
Reparent that CSG shape to the first one and notice how it has the incorrect effect

Minimal reproduction project:

I've noticed the same issue. You can work around it by closing the scene and then opening it again.

Happens to me too.

Same thing happened to me when I added a CSG scene to another scene.


Issue with k8s.io/docs/tutorials/hello-minikube/

This is a...

[ ] Feature Request
[ ] Bug Report

Problem:
The Minikube dashboard does not work and not possible to continue after that.
Proposed Solution:
Page to Update:
https://kubernetes.io/...

dup of #12968


LAFuture.collect / LAFuture.collectAll with empty list parameter is never satified

Hi,
One of the usages of collect/collectAll is to pass a sequence using sequence-to-vararg conversion e.g. LAFuture.collect(seqOfFutures: _*). In the corner case the seqOfFutures could be an empty list. In this case collect/collectAll is never satisfied, because f.foreach will never execute given function.
I've prepared PR reproducing problem and fixing it: #1654.

As per our contributing guidelines we ask that non-committers start a thread on the mailing list before opening tickets. If you can open up a thread we can confirm the issue and ask for the PR. :)

Yes, but also according to guideline "We will accept pull requests represents (...) Small changes, enhancements, or bug fixes to Lift’s code", but sure I can start a thread on mailing list.

Yep, and I think it's likely we'll be able to accept this PR :) If you look at the bullet above it, it explicitly mentions that the PR needs to be related to an issue discussed on the mailing list beforehand; I'll update the contribution guidelines to make it clear that a PR must meet all of the listed criteria.

I was thinking that the only one of this criteria was needed. Sorry for my misunderstanding :)

On the contrary, thanks for making it clear what the misunderstanding was so we could fix it!


Failed to install aderyn

Additional Context
I ran cargo uninstall aderyn. Then, I clicked on Install button provided by VSCode extension. After a while, I got this error

Also, the logs are empty. I only see Aderyn Output Channel Initialized

Did you resolve this @TilakMaddy ? I'm going to add some more error feedback today.

I tried this flow on a windows machine and got the same issue.
I then installed aderyn manually from a bash shell.
Then tried running again and got the issue #30 .
I noticed that running aderyn --version in a bash shell within VSCode worked, but in a powershell and cmd, it did not.


Running nuxt on interface different from localhost

First Check

[X] This is not a feature request
[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the Mealie documentation, with the integrated search.
[X] I already read the docs and didn't find an answer.

What is the issue you are experiencing?
Running this command line works (access to mealie from local LAN etc) when run from different shell, but not from honcho:
$ cd frontend && yarn start -H $(hostname) -p 3001

Deployment
Other
Deployment Details
macOS
Mealie Version
1.0 beta

Found one additional error. The command line needs to use dev instead of start otherwise the production system is started:
$ yarn dev -H $(hostname) -p 3001

But it still does only work if run in a different shell. Really strange.


DiskPool Metrics Exporter - add committed size in bytes

chore: update controller dependency
Signed-off-by: Tiago Castro<EMAIL_ADDRESS>
feat(exporter/diskpool): add committed size in bytes
This is useful for thin provisioning to determine if a pool is overcommitted.
Signed-off-by: Tiago Castro<EMAIL_ADDRESS>

bors merge

bors cancel

bors merge


docker.auth.auth.load_config: File doesn't exist

Error:
docker-compose --verbose build
compose.config.config.find: Using configuration files: .\docker-compose.yml
docker.auth.auth.load_config: File doesn't exist
Traceback (most recent call last):
File "", line 3, in
File "compose\cli\main.py", line 61, in main
File "compose\cli\main.py", line 110, in perform_command
File "compose\cli\command.py", line 35, in project_from_options
File "compose\cli\command.py", line 110, in get_project
File "compose\cli\command.py", line 85, in get_client
File "site-packages\docker\api\daemon.py", line 76, in version
File "site-packages\docker\utils\decorators.py", line 47, in inner
File "site-packages\docker\client.py", line 140, in _get
File "site-packages\requests\sessions.py", line 477, in get
File "site-packages\requests\sessions.py", line 465, in request
File "site-packages\requests\sessions.py", line 573, in send
File "site-packages\requests\adapters.py", line 415, in send
requests.exceptions.ConnectionError: ('Connection aborted.', error(10061, 'No connection could be made because the target machine actively refused it'))
docker-compose returned -1
docker.auth.auth.load_config: File doesn't exist

this looks like a docker-compose connection error. Look at these threads:

https://github.com/docker/machine/issues/3163
https://github.com/docker/compose/issues/2495

My guess is either the proxy or env var problems mentioned in those threads.

Problem is it lost the configuration, but how do you recreate it?

Please try the tips mentioned in the thread. This is a docker setup/configuration issue not specific to this project.


Manually populate missing metadata items

First identify what is to be fake populated, share this with the team to agree then implement.
Manual population of metadata, based on our best guesses, so that useful information can be used in user research.
Tag status as draft, to indicate this is information we have put in.
Data should look as real as possible
If we don't know fields we should leave them blank
Reformat metadata extract into format that Data Hub expects
Script to upload metadata into Data Hub, not using our registration API
Pick data products which already have descriptions

Somewhat blocked on https://github.com/ministryofjustice/data-platform/issues/3048 but I can start putting a spreadsheet together

Stuff to populate see (https://docs.google.com/spreadsheets/d/1O1EjO96lyqDbyuzFWU8SNBky3b7tKM8dccZVS7-_t9g/edit#gid=784169301)
Data product and table level:

Description
Owners
Domains (already set for data product but not showing up for tables)

Table level:

Row count
Column descriptions

Custom properties:

dpiaRequired
dpiaLocation
retentionPeriod
Sensitivity level

Ignore for now

s3Location
possible custom property for last data update
sourceDatasetName
sourceDatasetLocation

Can we bulk update properties via the command line, or do we need to write another script for this?

https://datahubproject.io/docs/cli/#user-user-entity this looks useful for adding some data owners
We can interact with individual data products using this one https://datahubproject.io/docs/cli/#dataproduct-data-product-entity
For tables, there are enough that we will probably need to script it. We need to

identify which assets are missing which fields
come up with our best guess for the missing metadata
update the assets

I wonder if we could use the file sink to dump to file, then edit the files, then load it back in ???

How to import data from remote datahub into local datahub lite for debugging and data wrangling
lite_sink.yaml:
pipeline_name: datahub_source_1
datahub_api:
  server: "https://data-platform-datahub-catalogue-dev.apps.live.cloud-platform.service.justice.gov.uk/api/gms"
  token: "eyJhbGciOiJIUzI1NiJ9.eyJhY3RvclR5cGUiOiJVU0VSIiwiYWN0b3JJZCI6Ik1hdC5Nb29yZSIsInR5cGUiOiJQRVJTT05BTCIsInZlcnNpb24iOiIyIiwianRpIjoiNWM4ZmUyMGUtMTcyMi00NzFhLThjNDYtZGVjNjE5MjM3ODI1Iiwic3ViIjoiTWF0Lk1vb3JlIiwiaXNzIjoiZGF0YWh1Yi1tZXRhZGF0YS1zZXJ2aWNlIn0.RfDihGQA3QqxzhufAyQLS4-8KiVuFdwQ0CEJlPwYx7s"
source:
  type: datahub
  config:
    include_all_versions: false
    pull_from_datahub_api: true
sink:
  type: datahub-lite

datahub ingest -c lite_sink.yaml

datahub lite ls

See https://datahubproject.io/docs/datahub_lite/

How to export data from remote datahub into a big json file
Same as above, just replace the sink with
sink:
  type: file
  config:
    filename: ./datahub_export.json

Example output:
[
{
    "entityType": "dataset",
    "entityUrn": "urn:li:dataset:(urn:li:dataPlatform:glue,nomis.offender_contact_persons,PROD)",
    "changeType": "UPSERT",
    "aspectName": "browsePaths",
    "aspect": {
        "json": {
            "paths": [
                "/prod/glue/nomis"
            ]
        }
    },
    "systemMetadata": {
        "lastObserved":<PHONE_NUMBER>978,
        "runId": "datahub-2024_02_05-10_15_54",
        "lastRunId": "no-run-id-provided"
    }
},
{
    "entityType": "dataset",
    "entityUrn": "urn:li:dataset:(urn:li:dataPlatform:glue,nomis.offender_contact_persons,PROD)",
    "changeType": "UPSERT",
    "aspectName": "datasetKey",
    "aspect": {
        "json": {
            "platform": "urn:li:dataPlatform:glue",
            "name": "nomis.offender_contact_persons",
            "origin": "PROD"
        }
    },
    "systemMetadata": {
        "lastObserved":<PHONE_NUMBER>979,
        "runId": "datahub-2024_02_05-10_15_54",
        "lastRunId": "no-run-id-provided"
    }
},
{
    "entityType": "dataset",
    "entityUrn": "urn:li:dataset:(urn:li:dataPlatform:glue,nomis.offender_contact_persons,PROD)",
    "changeType": "UPSERT",
    "aspectName": "browsePathsV2",
    "aspect": {
        "json": {
            "path": [
                {
                    "id": "nomis"
                }
            ]
        }
    },
    "systemMetadata": {
        "lastObserved":<PHONE_NUMBER>980,
        "runId": "datahub-2024_02_05-10_15_54",
        "lastRunId": "no-run-id-provided"
    }
},
{
    "entityType": "dataset",
    "entityUrn": "urn:li:dataset:(urn:li:dataPlatform:glue,nomis.offender_contact_persons,PROD)",
    "changeType": "UPSERT",
    "aspectName": "dataPlatformInstance",
    "aspect": {
        "json": {
            "platform": "urn:li:dataPlatform:glue"
        }
    },
    "systemMetadata": {
        "lastObserved":<PHONE_NUMBER>981,
        "runId": "datahub-2024_02_05-10_15_54",
        "lastRunId": "no-run-id-provided"
    }
},
{
    "entityType": "dataset",
    "entityUrn": "urn:li:dataset:(urn:li:dataPlatform:glue,nomis.offender_contact_persons,PROD)",
    "changeType": "UPSERT",
    "aspectName": "datasetProperties",
    "aspect": {
        "json": {
            "customProperties": {},
            "description": "",
            "tags": []
        }
    },
    "systemMetadata": {
        "lastObserved":<PHONE_NUMBER>982,
        "runId": "datahub-2024_02_05-10_15_54",
        "lastRunId": "no-run-id-provided"
    }
},
{
    "entityType": "dataset",
    "entityUrn": "urn:li:dataset:(urn:li:dataPlatform:glue,nomis.offender_contact_persons,PROD)",
    "changeType": "UPSERT",
    "aspectName": "schemaMetadata",
    "aspect": {
        "json": {
            "schemaName": "offender_contact_persons",
            "platform": "urn:li:dataPlatform:glue",
....

This thread includes the source of the common platform metadata, may be useful for filling in missing information https://asdslack.slack.com/archives/CH935DZGS/p1678203340379569

DBT ingestion is currently
source:
    type: dbt
    config:
        manifest_path: 'https://mojap-derived-tables.s3.eu-west-1.amazonaws.com/prod/run_artefacts/run_time%3D2024-01-30T07%3A35%3A49/target/manifest.json?response-content-disposition=inline&X-Amz-Security-Token=IQoJb3JpZ2luX2VjEFEaCWV1LXdlc3QtMiJIMEYCIQDN%2BnV1cIYKwElcJ6aIv3JlB67F0Kru%2BvwbOO7TyjMqtAIhAO3oYimobCVdSN6dNwIagfcd11efYgiVZD40Rt9H0FszKvgDCBoQAxoMNTkzMjkxNjMyNzQ5Igy1Zihb274TpbttXZwq1QNNxdNMQsXVK05ABRbcBT6QKpjDcIudz%2F%2BdY5IlJXFMkKVHjz3yRsiccheu%2F%2FR8cy3O4hTu62enLBgpWepOQM6YZElFv895VUYVvsn6aLQ%2BrrEWU9yDRWjINFRAp9FeOrxC41NgIsDncPxjpd5XQKa5TuPTzjT%2BHcotuy%2Bj5n%2BA16f9sXG5vdPvX7oCh4tcTBdHdWUlE%2B5OgNumylrl8LuSMJHrxn5jQXSgA91Eg5JXpK1LphCVG1FBLoZCgL5%2F%2FciDGGWslrCU8kWcLSvXmYZi%2F7e9I9WCvbJGMfYP0O37X51uK4mMM1PemL9mn8QD01sP5pQ3CliiHjgfcdmP4rx8bZyvgyIc17kyYAS4BstGYRSA8QNwXqFTb6RGiDAZLeDbGsD%2Bm6MrIPPb6fbRxOiLrZ0N9lszVkC5W%2Bl%2Fhyd9xogP79QONdPppTXendkNkixKyLo1fwkltxP%2B6i0xOVlPUa09NOD1Nj0JUIqtzJzdYZAFx%2BoJWZuF4IWVHii4btCYzooWLLEl7Osn%2BxFR%2BPOikMqwFg7d7skflyjadsfurQAayfkxJEqcEi%2FMqZ6ESCE0AmqmjJhR4ybhRsH5u3GXUMmK2cNqWElRLv84jx0jtjFQ96U9MNHM5K0GOpMCoJ2Ofy0xccZwHhPbS2hXHacqmD0RhvlAv5QfEj4hsuMNnGJVS02qfOaYcHE8mgJfWyKzK8DfUQBtLshcfeHtizcaomR%2FBwIcnFdEgj0CKqJ62geVLnAoHrEoHJ0MqjXeij6HVmWXCvOScr3VCnoB88IEvm4sobn2ua9mgKtwRq3z3p%2FdfZ7VJrovL%2FynhqptCOb6aFbu5SmpmDPbpVd9M0yCGxfGrB%2FHF9f42asvm62ZtV8MaArJ3GrVZjhcfo0BBRoO5YsYQ6a3jocomK3drnKvQI7zvV0vHa6GmiiXOL%2FD25GsuACnXkUfWpJxKupGWPYq8rmKR0yaryT%2BOmafK62XTDt1qi%2BroQY6m03H8A1aALg%3D&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20240130T164430Z&X-Amz-SignedHeaders=host&X-Amz-Expires=43200&X-Amz-Credential=ASIAYUIXP4BWSH6USAO2%2F20240130%2Feu-west-1%2Fs3%2Faws4_request&X-Amz-Signature=ad654521811b2b2e8ec3344f62b5c427133ac7a8583c12ed2f634c9d7a467ebe'
        catalog_path: 'https://mojap-derived-tables.s3.eu-west-1.amazonaws.com/prod/run_artefacts/run_time%3D2024-01-30T07%3A35%3A49/target/catalog.json?response-content-disposition=inline&X-Amz-Security-Token=IQoJb3JpZ2luX2VjEFEaCWV1LXdlc3QtMiJIMEYCIQDN%2BnV1cIYKwElcJ6aIv3JlB67F0Kru%2BvwbOO7TyjMqtAIhAO3oYimobCVdSN6dNwIagfcd11efYgiVZD40Rt9H0FszKvgDCBoQAxoMNTkzMjkxNjMyNzQ5Igy1Zihb274TpbttXZwq1QNNxdNMQsXVK05ABRbcBT6QKpjDcIudz%2F%2BdY5IlJXFMkKVHjz3yRsiccheu%2F%2FR8cy3O4hTu62enLBgpWepOQM6YZElFv895VUYVvsn6aLQ%2BrrEWU9yDRWjINFRAp9FeOrxC41NgIsDncPxjpd5XQKa5TuPTzjT%2BHcotuy%2Bj5n%2BA16f9sXG5vdPvX7oCh4tcTBdHdWUlE%2B5OgNumylrl8LuSMJHrxn5jQXSgA91Eg5JXpK1LphCVG1FBLoZCgL5%2F%2FciDGGWslrCU8kWcLSvXmYZi%2F7e9I9WCvbJGMfYP0O37X51uK4mMM1PemL9mn8QD01sP5pQ3CliiHjgfcdmP4rx8bZyvgyIc17kyYAS4BstGYRSA8QNwXqFTb6RGiDAZLeDbGsD%2Bm6MrIPPb6fbRxOiLrZ0N9lszVkC5W%2Bl%2Fhyd9xogP79QONdPppTXendkNkixKyLo1fwkltxP%2B6i0xOVlPUa09NOD1Nj0JUIqtzJzdYZAFx%2BoJWZuF4IWVHii4btCYzooWLLEl7Osn%2BxFR%2BPOikMqwFg7d7skflyjadsfurQAayfkxJEqcEi%2FMqZ6ESCE0AmqmjJhR4ybhRsH5u3GXUMmK2cNqWElRLv84jx0jtjFQ96U9MNHM5K0GOpMCoJ2Ofy0xccZwHhPbS2hXHacqmD0RhvlAv5QfEj4hsuMNnGJVS02qfOaYcHE8mgJfWyKzK8DfUQBtLshcfeHtizcaomR%2FBwIcnFdEgj0CKqJ62geVLnAoHrEoHJ0MqjXeij6HVmWXCvOScr3VCnoB88IEvm4sobn2ua9mgKtwRq3z3p%2FdfZ7VJrovL%2FynhqptCOb6aFbu5SmpmDPbpVd9M0yCGxfGrB%2FHF9f42asvm62ZtV8MaArJ3GrVZjhcfo0BBRoO5YsYQ6a3jocomK3drnKvQI7zvV0vHa6GmiiXOL%2FD25GsuACnXkUfWpJxKupGWPYq8rmKR0yaryT%2BOmafK62XTDt1qi%2BroQY6m03H8A1aALg%3D&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20240130T164402Z&X-Amz-SignedHeaders=host&X-Amz-Expires=43200&X-Amz-Credential=ASIAYUIXP4BWSH6USAO2%2F20240130%2Feu-west-1%2Fs3%2Faws4_request&X-Amz-Signature=b352908d72597b667f98f50113c3549b13c772adae33cbc9ee1c78f3bd370dfa'
        target_platform: s3
        entities_enabled:
            test_results: No
            seeds: No
            snapshots: No
            models: Yes
            sources: No
            test_definitions: No
        node_name_pattern:
            allow:
                - '.*oasys_set$'
                - '.*oasys_section$'
                - '.*oasys_question$'
                - '.*oasys_answer$'
                - '.*oasys_assessment_group$'
                - '.*offender$'
                - '.*ref_question$'
                - '.*prison_population_history__imprisonment_spells$'
                - '.*prison_population_history__jicsl_lookup_ao_population_nart$'
                - '.*derived_delius__components_at_latest$'
                - '.*derived_delius__components_at_comm$'
                - '.*derived_delius__components_at_term$'
                - '.*derived_delius__contacts$'
                - '.*derived_delius__court_appearances$'
                - '.*derived_delius__court_reports$'
                - '.*derived_delius__first_release$'
                - '.*derived_delius__releases$'
                - '.*derived_delius__sentences_at_disp$'
                - '.*derived_delius__sentences_at_latest$'
                - '.*derived_delius__sentences_at_term$'
                - '.*derived_delius__upw_appointments$'
                - '.*common_platform_derived__all_offence_fct$'
                - '.*common_platform_derived__cases_fct$'
                - '.*common_platform_derived__crown_trials_fct$'
                - '.*common_platform_derived__def_hearing_summary_fct$'
                - '.*common_platform_derived__defendant_summary_fct$'
                - '.*common_platform_derived__disposal_summary_fct$'
                - '.*common_platform_derived__sjp_all_offence_fct$'
                - '.*common_platform_derived__sjp_defendant_summary_fct$'
                - '.*common_platform_derived__sjp_disposal_summary_fct$'
                - '.*common_platform_derived__sjp_session_summary_fct$'
                - '.*lookup_offence_v2__cjs_offence_code_to_ho_offence_code$'
                - '.*lookup_offence_v2__ho_offence_codes$'
                - '.*lookup_offence_v2__offence_group$'
                - '.*lookup_offence_v2__offence_group_code$'
                - '.*lookup_offence_v2__offence_priority$'
        stateful_ingestion:
            remove_stale_metadata: true

We could automate the adding of owners via https://datahubproject.io/docs/generated/ingestion/sources/dbt/#dbt-meta-automated-mappings or https://datahubproject.io/docs/metadata-ingestion/docs/transformer/dataset_transformer/#pattern-add-dataset-ownership
We can add fixed properties using https://datahubproject.io/docs/metadata-ingestion/docs/transformer/dataset_transformer#simple-add-dataset-datasetproperties

Following discussion with UR we will also do the following before datahub is ready for UR testing.

Remove datasets from datahub that have not been assigned to a data product - Most likley a handful of the dbt models ingested.
Add in an ideal data product, i.e. one that isn't based on what we have now but more what we are aiming to get to.
Add in civil timeliness publication metadata. This should be available in s3 in the data-platform-development account's metadata bucket

Tag examples of well documented data

You can do negative filtering for views, so I would make a needsDocumentation tag, add it to everything, then remove it from the good ones, and create a 'not needsDocumentation' view

Make dataset location = to where you'll find it, e.g. the analytical platform

WhereToAccessDataset field name? (to remove ambiguity)


CODE - Create Automated Test File

Create Automated Test File
User Story
As the lead developer, I would like to create an automated file to provide unit tests so that the code can be tested incrementally as it is developed
Requirements

Create a new .js file named index.test.js
File must test for website functionality via smoke tests (Checking for title, dropdowns, inputs and conversion rate)
Utilise Github Actions to automate testing

Further Notes
With further testing functionality is available within the web. Further proof to be commented

To test that the site works correctly, each required feature is checked for via the following code:

Resulting in:

Initial test of each core area functional - Further testing to take place upon the coding of the js file.
To be marked as complete as initial testing completed

Moved as the automation aspect is required

Workflow file now exists:

Automatic testing completed. Ticket complete

Adding note that now for each commit it is checked:


how do i install the library?

go get or your preferred dependency manager (e.g., glide, godep)

Thanks! @yl2chen


Invalid property: GtkApplicationWindow.window-position

(nwguitest.exe:5140): Gtk-ERROR **: 14:05:33.817: failed to add UI: .:7:39 Invalid property: GtkApplicationWindow.window-position
error: process didn't exit successfully: target\debug\nwguitest.exe (exit code: 0xc0000409, STATUS_STACK_BUFFER_OVERRUN)

Because there is no such property. Not sure what I am supposed to do with such an unclear issue other than closing it.


Cassandra GetDomain still fetches result after DeleteDomain

Describe the bug
If we run the Cassandra unit test multiple time for MetadataPersistenceSuiteV2, the test is failing with this weird issue. An error is expected but got nil. This is happening because delete is not deleting the record although the request is sucessful.
To Reproduce
Is the issue reproducible?
Yes
Steps to reproduce the behavior:
I have included some print statement and uploaded a branch aanish/cassandra-delete-issue
Please pull this branch.
Then run the Cassandra unit test for MetadataPersistenceSuiteV2 from https://github.com/uber/cadence/blob/58879efb2d6486d3edfedf502fd0cefd045f50fe/common/persistence/persistence-tests/cassandra_test.go#L44
Run this multiple times. You would get the test failing with these outputs.
Delete domain completed delete-domain-test-name 5f085e78-5bd4-4428-80a3-69a945c70cef
Get domain complete <nil> delete-domain-test-name 5f085e78-5bd4-4428-80a3-69a945c70cef
As you can see the delete is completed but it is still getting the domain with same Id. Actually the GetDomain should have returned EntityNotExistError.

@anish531213 I ran this test suite 10 times on master and it passed every time? Is it possible you changed something in the clean up or test logic?


[BUG] Received tool input did not match expected schema

Describe the bug
We encountered a situation where action.toolInput is passed as a string, while the tool expects an object. Historically, action.toolInput was passed directly, but a recent change seems to have introduced the isXML flag for a specific use case. However, only one agent sets isXML to true, while others don't utilize this flag.
The issue occurs when action.toolInput is provided as a string, but the tool expects an object.
Questions:

Is it incorrect for the tool to expect an object in this context?
Or, is it wrong for action.toolInput to be a string when the tool expects an object?
Should there be logic that wraps the string into an object when needed?

Looking forward to any insights or guidance on this behavior!
To Reproduce
Steps to reproduce the behavior:

Create a flow like in the attached JSON
create a folder and paste the path in the folder with files tool.
add some documents
Ask the bot a question about something within the documents that were upserted
Will be displayed the message: 'Received tool input did not match expected schema'

Expected behavior
The chatbot should be able to respond by reading the documents
Flow
chatflow_bug Chatflow.json
Setup
Installation npm flowise start
Flowise Version  2.1.2
OS Windows 24h2
Browser Brave
Node 22.9.0

isXML is only used when you have an XML agent. In your case you have Conversation Agent, which shouldnt trigger the check. Can you try ToolAgent and see?

You also need to upsert your data first: https://docs.flowiseai.com/use-cases/upserting-data
By just having Read Tool is only able to read a simple txt file


Improve Hashing section in README

Show the core concept of wrapping a MessageDigest instance into an ImmutableMessageDigestObject.

Get rid of the exception salad in README under Hashing.

Get rid of the exception salad in README under Hashing.


Get feedback from more people on newsletter draft.

@katiewhite360 , please add more people to the draft each weeks, there are a few mistakes again that slipped through today.
It's ok to make a newsletter every 3 weeks if 2 weeks is too short. We've always did things slowly but right, and not in a hurry.

Will do.
Is the material still being gathered here?

Is the material still being gathered here?

Should be, just people seem to not contribute, and here in Berkeley we've been meeting for all of last week, and still a lot this week, so didn't had a chance to collect material.
Also I can't and shouldn't be the only one to do that.
@ellisonbg any idea of who we can put on gathering material ?

I fully agree that we can't have the collection/gathering be just one
person. Initially, it is going to have to be the entire core team (the
folks at the dev meeting). I don't see how we would delegate this to a
person outside this team as they are the ones who know everything going on.
Eventually, Jamie may have a good perspective on everything that is
happening, but we aren't there yet. My recommendation is to have myself and
@fperez work with Katie to send out an email to the core team every 2 weeks
with a reminder.
On Thu, Apr 7, 2016 at 9:59 AM, Matthias Bussonnier <
<EMAIL_ADDRESS>wrote:

Is the material still being gathered here?
Should be, just people seem to not contribute, and here in Berkeley we've
been meeting for all of last week, and still a lot this week, so didn't had
a chance to collect material.
Also I can't and shouldn't be the only one to do that.
@ellisonbg https://github.com/ellisonbg any idea of who we can put on
gathering material ?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/jupyter/newsletter/issues/22#issuecomment-206993966

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

Perhaps adding a reminder at the bottom of the weekly Dev Meeting HackPad for folks to make suggestions would be helpful as a weekly reminder.

Yes! That is a perfect context for it as it already has a lot of that
content. Might also make sense for us to start asking folks to submit stuff
from their dev meeting report.
On Mon, Apr 11, 2016 at 5:51 PM, Carol Willing<EMAIL_ADDRESS>wrote:

Perhaps adding a reminder at the bottom of the weekly Dev Meeting HackPad
for folks to make suggestions would be helpful as a weekly reminder.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/jupyter/newsletter/issues/22#issuecomment-208649792

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

No additional ideas were contributed today but we can keep trying for a few more weeks. Participation in this weeks meeting was fairly low so that may be to blame.
@katiewhite360  the Hackpad collection for Dev Meetings is here in case you're not familiar: https://jupyter.hackpad.com/collection/zCqMrBELzrv

OK let's postpone the newsletter for this week - that will also give us
time to iterate on the process and tools
On Tue, Apr 12, 2016 at 2:20 PM, Ana Ruvalcaba<EMAIL_ADDRESS>wrote:

No additional ideas were contributed today but we can keep trying for a
few more weeks. Participation in this weeks meeting was fairly low so that
may be to blame.
@katiewhite360 https://github.com/katiewhite360 the Hackpad collection
for Dev Meetings is here in case you're not familiar:
https://jupyter.hackpad.com/collection/zCqMrBELzrv
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/jupyter/newsletter/issues/22#issuecomment-209107771

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

Here are a few:

Talk Python to Me podcast: Min and Matthias https://talkpython.fm/episodes/show/44/project-jupyter-and-ipython Has a good section on the history of Jupyter. Also a transcript is available.

Release of nbconvert https://groups.google.com/forum/#!topic/jupyter/Ea51RPt4FSU

Talks from first data science meetup at BIDs during the Dev Meeting https://bids.berkeley.edu/resources/videos/berkeley-data-science-meetup-all-about-jupyter

@parente's 10 New Reasons to use Jupyter in 10 minutes slide deck

Fantastic @willingc
Has a Medium account been made? Content can go in anytime

I am working on getting the passwords required to do that
Sent from my iPhone

On Apr 12, 2016, at 9:57 PM, Katie White<EMAIL_ADDRESS>wrote:
Fantastic @willingc
Has a Medium account been made? Content can go in anytime
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

Thanks @ellisonbg. I had no idea what the Medium account was.

Perfect, I'll have the content ready to go in when it's set up.

@katiewhite360 Don't leave me in suspense! What are you using the Medium account for?

@katiewhite360 :dog: :cat: :fish: :snake: I wonder if there is a Jupyter notebook about pets somewhere?

We are trying Medium for publishing the newsletter because it takes a few steps out of the process (github>google docs>mailchimp>publish). It can be drafted, edited, published, and shared in the same place.

Makes sense to me @katiewhite360  Simplify all the things! Also, it's used quite a bit by open source bloggers and small publications.
Oh and I didn't find a notebook yet on pets but one link that came up was http://www.jesshamrick.com/2011/05/18/an-introduction-to-classes-and-inheritance-in-python/ @jhamrick :smile:

Everybody loves cats and dogs!

-1 on Medium.

I don't have a problem with Medium, and if it simplifies the workflow for
the folks doing the bulk of this work, I have no objections.
Matthias, do you see any major problems with it that are show stoppers? If
not, I suggest we let the team move forward with it for now, and see how it
goes.
My only question is in a different direction... Do we really have enough
content and bandwidth to do it every other week? I have the feeling we are
a bit overwhelmed as it is, and perhaps a monthly frequency might be easier
at least for a while?
On Wed, Apr 13, 2016, 01:01 Matthias Bussonnier<EMAIL_ADDRESS>wrote:

-1 on Medium.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/jupyter/newsletter/issues/22#issuecomment-209292725

Matthias, do you see any major problems with it that are show stoppers? If
not, I suggest we let the team move forward with it for now, and see how it
goes.

Just giving my take on that, last time I tried Medium, it was not that great either
for multiple collaborators, and it is one more things to keep track of.
And it looks as another blog while we already have ghost.
If you want to try Medium, feel free to do so.

The issues that Medium solves are this:

It allows content to be authored in a single place rather than 3 (Google
Docs for draft, Mail Chimp, and another place for archive).
It handles both web based subscription/archiving and emailing those who
are subscribed (like mail chimp)
It has a notion of a publication that was editors and authors - this is
exactly the editorial cycle that we have been missing with Ghost (which we
were going to use for our archives).
It not has a really nice API (I am going to have students work on a
notebook to Ghost tool this summer).
Right now there are a lot of things that Katie and Ana can't do well
because of GitHub. We need to stop recommending GitHub for non-coding
staff. It is a waste of time and leads to frustration.
Medium now allow custom subdomains (newsletter.jupyter.org)
Medium can allow for third party authors to submit content to
publications for review and publication. Perfect for guest blog posts (if
we were to migrate the blog as well).
The content editor in Medium is amongst the best on the web - for
non-coding people

All we are asking at this point is that we try Medium - not to actually
publish a real newsletter, but for Katie and Ana to try the tool out and
see if it actually fixes the problems they have been having.
On Wed, Apr 13, 2016 at 1:38 AM, Fernando Perez<EMAIL_ADDRESS>wrote:

I don't have a problem with Medium, and if it simplifies the workflow for
the folks doing the bulk of this work, I have no objections.
Matthias, do you see any major problems with it that are show stoppers? If
not, I suggest we let the team move forward with it for now, and see how it
goes.
My only question is in a different direction... Do we really have enough
content and bandwidth to do it every other week? I have the feeling we are
a bit overwhelmed as it is, and perhaps a monthly frequency might be easier
at least for a while?
On Wed, Apr 13, 2016, 01:01 Matthias Bussonnier<EMAIL_ADDRESS>wrote:

-1 on Medium.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/jupyter/newsletter/issues/22#issuecomment-209292725

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/jupyter/newsletter/issues/22#issuecomment-209305367

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

Hi all, I've opened a PR with a draft of a planning notebook. If you find it useful for framing discussion, please use it in the notebook form or another form.
We have so much talent in this group and many balls to juggle. I want to make sure that we're being mindful of listening to each other's thoughts and seeing ideas from different perspectives. Simply, I wish to foster team communication at a pace that doesn't lead to burnout, tries to minimize unintentionally leaving people out of the loop, and avoids demotivating others. The notebook is merely a suggestion or catalyst to even better team ideas and actions.

cc/ @jamieshq FYI

Ok, given that:
a) Matthias objection wasn't strenuous nor based on a show-stopper issue.
b) There seems to be real interest in trying out Medium by the folks
carrying a lot of this burden, and it seems to address real issues we do
have.
I'd like to call it to move forward with trying it out for the newsletter.
I know we're bad at calling decisions, so let me try to help with that at
least :)
If we end up super-duper-happy with it after a few months of using it for
that, we can rethink the blog itself, but let's not worry about that for
now.

Almost concurrently we Fernando sending this out - I sent out a message to
those folks directly working on the newsletter with information about us
trying out medium. For now. I don't even think we want to commit to using
it officially. Katie has some questions about how it will work for
something like this - we will probably just do a private test run with a
few people and if that goes well, think about doing it for a published
newsletter (with a custom subdomain, have Cameron design us a banner, pick
colors, etc.).
On Wed, Apr 13, 2016 at 3:41 PM, Fernando Perez<EMAIL_ADDRESS>wrote:

Ok, given that:
a) Matthias objection wasn't strenuous nor based on a show-stopper issue.
b) There seems to be real interest in trying out Medium by the folks
carrying a lot of this burden, and it seems to address real issues we do
have.
I'd like to call it to move forward with trying it out for the newsletter.
I know we're bad at calling decisions, so let me try to help with that at
least :)
If we end up super-duper-happy with it after a few months of using it for
that, we can rethink the blog itself, but let's not worry about that for
now.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/jupyter/newsletter/issues/22#issuecomment-209678337

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>