- Pharo-users - lists.pharo.org

Bootstrap3 to Bootstrap 4
by Jeff Gray Aug. 15, 2019

Aug. 15, 2019

I have moved my code from using Bootstrap 3 to Bootstrap 4. There were a few updates I had to make and overall it seems cleaner. The one thing I can't seem to convert is informSuccess. There doesn't seem to be an equivalent in Bootstrap 4. For now I am using the vanilla Seaside inform, which is ok but it doesn't look bootstrappy. My use case is when I have performed an action on a page, then I want to display a message and then redirect to a different page. ie on a "I forgot My Password" page I send an email to the entered address. Then I display a message to say that the email was sent. When the user clicks ok they are redirected to the login page. Is there a better way to handle this than with an inform? -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

1 0

Re: [Pharo-users] bloc segfault
by Peter H. Meadows Aug. 14, 2019

Aug. 14, 2019

C stack backtrace & registers: rax 0x00fc67e4 rbx 0x7ffca58b6430 rcx 0x021b3de0 rdx 0x02186a68 rdi 0x7ffca58b64e0 rsi 0x7ffca58b64e0 rbp 0x7ffca587e6a0 rsp 0x7ffca587e610 r8 0x7ffca587e6b0 r9 0x00000075 r10 0x0000000e r11 0x000131b8 r12 0x02991ed9 r13 0x00000000 r14 0x00000000 r15 0x00000000 rip 0x0045efc9 *./pharo-vm/lib/pharo/5.0-201901051900/pharo(interpret+0x1a99)[0x45efc9] ./pharo-vm/lib/pharo/5.0-201901051900/pharo[0x41b0d3] ./pharo-vm/lib/pharo/5.0-201901051900/pharo[0x41cb2e] /lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7fc766bf2890] ./pharo-vm/lib/pharo/5.0-201901051900/pharo(interpret+0x1a99)[0x45efc9] ./pharo-vm/lib/pharo/5.0-201901051900/pharo[0x468be6] ./pharo-vm/lib/pharo/5.0-201901051900/pharo(interpret+0x246)[0x45d776] ./pharo-vm/lib/pharo/5.0-201901051900/pharo(main+0x2fa)[0x41a5ba] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7fc766810b97] ./pharo-vm/lib/pharo/5.0-201901051900/pharo[0x41a8e4] [0x0] Smalltalk stack dump: 0x7ffca58b64e0 I Array(ExternalFunction)>invokeWithArguments: 0x21b3de0: a(n) Array 0x7ffca58b6520 M MozClipper>primPushClipRectangleX:y:width:height: 0x2187658: a(n) MozClipper 0x7ffca58b65a0 I FFICalloutAPI>function:module: 0x21878d0: a(n) FFICalloutAPI 0x7ffca58b65f0 I MozClipper(Object)>ffiCall: 0x2187658: a(n) MozClipper 0x7ffca58b6638 I MozClipper>primPushClipRectangleX:y:width:height: 0x2187658: a(n) MozClipper 0x7ffca58b6698 I MozClipper>pushRectangle: 0x2187658: a(n) MozClipper 0x7ffca58be0e8 I Rectangle>spartaClipOn:with: 0x2187448: a(n) Rectangle 0x7ffca58be138 I MozClipper(SpartaClipper)>push: 0x2187658: a(n) MozClipper 0x7ffca58be180 I MozClipper(SpartaClipper)>by:during: 0x2187658: a(n) MozClipper 0x7ffca58be1e0 M MozClipperTests>testPureClip 0x2162060: a(n) MozClipperTests 0x7ffca58be220 I MozClipperTests(TestCase)>performTest 0x2162060: a(n) MozClipperTests 0x7ffca58be250 M [] in MozClipperTests(TestCase)>runCase 0x2162060: a(n) MozClipperTests 0x7ffca58be290 M BlockClosure>ensure: 0x2164020: a(n) BlockClosure 0x7ffca58be2d8 I MozClipperTests(TestCase)>runCase 0x2162060: a(n) MozClipperTests 0x7ffca58be310 M [] in TestExecutionEnvironment>runTestCaseSafelly: 0x2162218: a(n) TestExecutionEnvironment 0x7ffca58be340 M BlockClosure>on:do: 0x2163f00: a(n) BlockClosure 0x7ffca58be388 M [] in TestExecutionEnvironment>runTestCaseSafelly: 0x2162218: a(n) TestExecutionEnvironment 0x7ffca58be3b8 M BlockClosure>on:do: 0x2163d78: a(n) BlockClosure 0x7ffca58be408 I TestExecutionEnvironment>runTestCaseSafelly: 0x2162218: a(n) TestExecutionEnvironment 0x7ffca58be448 M [] in TestExecutionEnvironment>runTestCase: 0x2162218: a(n) TestExecutionEnvironment 0x7ffca58be488 M BlockClosure>ensure: 0x2163c78: a(n) BlockClosure 0x7ffca58be4c8 M [] in TestExecutionEnvironment>runTestCase: 0x2162218: a(n) TestExecutionEnvironment 0x7ffca58be508 M BlockClosure>ifCurtailed: 0x2163b78: a(n) BlockClosure 0x7ffca58be550 I TestExecutionEnvironment>runTestCase: 0x2162218: a(n) TestExecutionEnvironment 0x7ffca58be598 I CurrentExecutionEnvironment class>runTestCase: 0x25025a8: a(n) CurrentExecutionEnvironment class 0x7ffca58be5e0 I MozClipperTests(TestCase)>runCaseManaged 0x2162060: a(n) MozClipperTests 0x7ffca58be618 M [] in TestResult>runCase: 0x2160f10: a(n) TestResult 0x7ffca58be648 M BlockClosure>on:do: 0x2163450: a(n) BlockClosure 0x7ffca58be698 I TestResult>runCase: 0x2160f10: a(n) TestResult 0x7ffca58b7fb8 I MozClipperTests(TestCase)>run: 0x2162060: a(n) MozClipperTests

1 0

bloc segfault
by Peter H. Meadows Aug. 14, 2019

Aug. 14, 2019

Inspiron-1545 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ===================================================== =============== GToolkit Installer ================== ===================================================== Library is already installed: - no Download directory: /home/phm/pharo3/pharo-local/gtoolkit-installer Installation directory: /home/phm/pharo3 Downloading https://dl.feenk.com/Moz2D/linux/development/x86_64/libMoz2D.so to File @ /home/phm/pharo3/pharo-local/gtoolkit-installer/libMoz2D_x86_64.so ... Progress . . . . . . . . . . . . . . . . . . . Done! Installing library to File @ /home/phm/pharo3/libMoz2D.so Gtk-Message: 22:13:02.305: Failed to load module "canberra-gtk-module" (pharo:15537): GLib-GObject-WARNING **: 22:13:02.509: cannot register existing type 'GdkDisplay' (pharo:15537): GLib-CRITICAL **: 22:13:02.513: g_once_init_leave: assertion 'result != 0' failed (pharo:15537): GLib-GObject-CRITICAL **: 22:13:02.513: g_type_register_static: assertion 'parent_type > 0' failed (pharo:15537): GLib-GObject-CRITICAL **: 22:13:02.513: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed (pharo:15537): GLib-CRITICAL **: 22:13:02.513: g_once_init_leave: assertion 'result != 0' failed Success! Moz2D is up and running :) Segmentation fault Wed Aug 14 22:31:06 2019 /home/phm/pharo3/pharo-vm/lib/pharo/5.0-201901051900/pharo Pharo VM version: 5.0-201901051900 Sat Jan 5 19:12:50 UTC 2019 gcc 4.8 [Production Spur 64-bit VM] Built from: CoInterpreter VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 With: StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 Revision: VM: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Sat Jan 5 20:00:11 2019 CommitHash: 7a3c6b64 Plugins: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Build host: Linux travis-job-f22c8934-2412-48ed-8180-7a42b62c7389 4.4.0-101-generic #124~14.04.1-Ubuntu SMP Fri Nov 10 19:05:36 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux plugin path: /home/phm/pharo3/pharo-vm/lib/pharo/5.0-201901051900 [default: /home/phm/pharo3/pharo-vm/lib/pharo/5.0-201901051900/] C stack backtrace & registers: rax 0x00000000 rbx 0x000527d8 rcx 0x023e78e0 rdx 0x00000149 rdi 0x00000000 rsi 0x00000000 rbp 0x00000000 rsp 0x7ffd19ea1560 r8 0x01b088b8 r9 0x0208b890 r10 0x0076c100 r11 0x027d2610 r12 0x08400041 r13 0x01b4fb86 r14 0x02441650 r15 0x0208b5b0 rip 0x00441ec0 */home/phm/pharo3/pharo-vm/lib/pharo/5.0-201901051900/pharo[0x441ec0] /home/phm/pharo3/pharo-vm/lib/pharo/5.0-201901051900/pharo[0x41b0d3] /home/phm/pharo3/pharo-vm/lib/pharo/5.0-201901051900/pharo[0x41cb2e] /lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7f07c6cfc890] /home/phm/pharo3/pharo-vm/lib/pharo/5.0-201901051900/pharo[0x441ec0] /home/phm/pharo3/pharo-vm/lib/pharo/5.0-201901051900/pharo(lookupOrdinaryreceiver+0x5f)[0x44222f] /home/phm/pharo3/pharo-vm/lib/pharo/5.0-201901051900/pharo(ceSICMiss+0x44)[0x49b104] [0x1a00571] [0x0] Smalltalk stack dump: 0x7ffd19eb2298 M Context>copyTo: 0x208b228: a(n) Context 0x7ffd19eb22e0 M Context>copyTo: 0x208b418: a(n) Context 0x7ffd19eb2338 I Context>copyTo: 0x208b360: a(n) Context 0x7ffd19eb2380 I MessageNotUnderstood(Exception)>freezeUpTo: 0x208b310: a(n) MessageNotUnderstood 0x7ffd19eb23c8 I MessageNotUnderstood(Exception)>freeze 0x208b310: a(n) MessageNotUnderstood 0x7ffd19eb2418 I BlCompositeErrorHandler(BlErrorHandler)>convertToHandledError:in: 0x84c9290: a(n) BlCompositeErrorHandler 0x7ffd19eb2470 I BlCompositeErrorHandler(BlErrorHandler)>handleError:in: 0x84c9290: a(n) BlCompositeErrorHandler 0x7ffd19eb24c0 M [] in BlCompositeErrorHandler(BlErrorHandler)>with:do:failed: 0x84c9290: a(n) BlCompositeErrorHandler 0x7ffd19eb24f8 M BlockClosure>cull: 0x1f9fc80: a(n) BlockClosure 0x7ffd19eb2548 I Context>evaluateSignal: 0x208b4d0: a(n) Context 0x7ffd19eb2590 I Context>handleSignal: 0x208b4d0: a(n) Context 0x7ffd19eb25d8 I MessageNotUnderstood(Exception)>signal 0x208b310: a(n) MessageNotUnderstood 0x7ffd19eb2628 I ExternalData(Object)>doesNotUnderstand: 0x20527d8: a(n) ExternalData 0x7ffd19ebf450 I Array(ExternalFunction)>invokeWithArguments: 0x208b208: a(n) Array 0x7ffd19ebf490 M MozPath>primStrokeBounds:rect: 0x20527f0: a(n) MozPath 0x7ffd19ebf4f0 M FFICalloutAPI>function:module: 0x206ad50: a(n) FFICalloutAPI 0x7ffd19ebf540 I MozPath(Object)>ffiCall: 0x20527f0: a(n) MozPath 0x7ffd19ebf588 I MozPath>primStrokeBounds:rect: 0x20527f0: a(n) MozPath 0x7ffd19ebf5e0 I MozPath>strokedBounds: 0x20527f0: a(n) MozPath 0x7ffd19ebf630 I [] in MozPath>strokedBoundsOn:with: 0x20527f0: a(n) MozPath 0x7ffd19ea8120 I SpartaStrokedBoundsCache>strokedBounds:ifAbsentPut: 0x2052a30: a(n) SpartaStrokedBoundsCache 0x7ffd19ea8170 I MozPath>strokedBoundsOn:with: 0x20527f0: a(n) MozPath 0x7ffd19ea81d0 I [] in SpartaLine>strokedBoundsOn:with: 0x1fa0118: a(n) SpartaLine 0x7ffd19ea8210 I SpartaStrokedBoundsCache>strokedBounds:ifAbsentPut: 0x1fa0138: a(n) SpartaStrokedBoundsCache 0x7ffd19ea8260 I SpartaLine>strokedBoundsOn:with: 0x1fa0118: a(n) SpartaLine 0x7ffd19ea82c8 I BlLine(BlGeometry)>strokedBoundsCentered:of:on: 0x84c9030: a(n) BlLine 0x7ffd19ea8320 I BlOutskirtsCentered>strokedBounds:of:on: 0x840f6e8: a(n) BlOutskirtsCentered 0x7ffd19ea8378 I BlLine(BlGeometry)>strokedBounds:of:on: 0x84c9030: a(n) BlLine 0x7ffd19ea83c0 M BlLineElement(BlElement)>visualBounds:on: 0x84c6b18: a(n) BlLineElement 0x7ffd19ea8400 M BlLineElement(BlElement)>visualBoundsOn: 0x84c6b18: a(n) BlLineElement 0x7ffd19ea8448 I BlLineElement(BlElement)>visualBounds 0x84c6b18: a(n) BlLineElement 0x7ffd19ea8488 M BlNullEffect(BlElementEffect)>effectBounds: 0x1f9ffa8: a(n) BlNullEffect 0x7ffd19ea84c0 M BlLineElement(BlElement)>effectBounds: 0x84c6b18: a(n) BlLineElement 0x7ffd19ea8518 I BlLineElement(BlElement)>invalidationBounds: 0x84c6b18: a(n) BlLineElement 0x7ffd19ea8568 I BlLineElement(BlElement)>invalidate 0x84c6b18: a(n) BlLineElement 0x7ffd19ea85c8 M BlLineElement(BlElement)>position:extent: 0x84c6b18: a(n) BlLineElement 0x7ffd19ea8628 M BlLineElement(BlElement)>applyLayoutSafelyIn: 0x84c6b18: a(n) BlLineElement 0x7ffd19ebe2b8 M [] in BlLineElement(BlElement)>applyLayoutIn: 0x84c6b18: a(n) BlLineElement 0x7ffd19ebe2e8 M BlockClosure>on:do: 0x1f9fb78: a(n) BlockClosure 0x7ffd19ebe328 M BlCompositeErrorHandler(BlErrorHandler)>with:do:failed: 0x84c9290: a(n) BlCompositeErrorHandler 0x7ffd19ebe370 M BlLineElement(BlElement)>applyLayoutIn: 0x84c6b18: a(n) BlLineElement 0x7ffd19ebe3a8 M BlLineElement(BlGeometryElement)>applyLayoutIn: 0x84c6b18: a(n) BlLineElement 0x7ffd19ebe3e0 M [] in BlBasicLayout>layout:in: 0x84c22a0: a(n) BlBasicLayout 0x7ffd19ebe428 M Array(SequenceableCollection)>do: 0x1f7db90: a(n) Array 0x7ffd19ebe460 M BlChildrenAccountedByLayout(BlChildrenSubset)>do: 0x1f7d390: a(n) BlChildrenAccountedByLayout 0x7ffd19ebe498 M BlBasicLayout>layout:in: 0x84c22a0: a(n) BlBasicLayout 0x7ffd19ebe4d8 M BlElement>onLayout: 0x84c0310: a(n) BlElement 0x7ffd19ebe530 M BlElement>applyLayoutSafelyIn: 0x84c0310: a(n) BlElement 0x7ffd19ebe570 M [] in BlElement>applyLayoutIn: 0x84c0310: a(n) BlElement 0x7ffd19ebe5a0 M BlockClosure>on:do: 0x1f7c3e8: a(n) BlockClosure 0x7ffd19ebe5e0 M BlCompositeErrorHandler(BlErrorHandler)>with:do:failed: 0x84c2388: a(n) BlCompositeErrorHandler 0x7ffd19ebe628 M BlElement>applyLayoutIn: 0x84c0310: a(n) BlElement 0x7ffd19ed1248 M [] in BlBasicLayout>layout:in: 0x1c70c78: a(n) BlBasicLayout 0x7ffd19ed1290 M Array(SequenceableCollection)>do: 0x1f7c078: a(n) Array 0x7ffd19ed12d8 I BlChildrenAccountedByLayout(BlChildrenSubset)>do: 0x1f7b800: a(n) BlChildrenAccountedByLayout 0x7ffd19ed1320 I BlBasicLayout>layout:in: 0x1c70c78: a(n) BlBasicLayout 0x7ffd19ed1370 I BlElement>onLayout: 0x1c63998: a(n) BlElement 0x7ffd19ed13d8 I BlElement>applyLayoutSafelyIn: 0x1c63998: a(n) BlElement 0x7ffd19ed1418 M [] in BlElement>applyLayoutIn: 0x1c63998: a(n) BlElement 0x7ffd19ed1448 M BlockClosure>on:do: 0x1f7a4a0: a(n) BlockClosure 0x7ffd19ed1488 M BlCompositeErrorHandler(BlErrorHandler)>with:do:failed: 0x1c70d78: a(n) BlCompositeErrorHandler 0x7ffd19ed14e0 I BlElement>applyLayoutIn: 0x1c63998: a(n) BlElement 0x7ffd19ed1528 I BlSpace>doUpdateLayout: 0x1c63b40: a(n) BlSpace 0x7ffd19ed1570 I BlSpace>doUpdateLayout 0x1c63b40: a(n) BlSpace 0x7ffd19ed15a8 M [] in BlSpace>doLayout 0x1c63b40: a(n) BlSpace 0x7ffd19ed15d8 M BlockClosure>on:do: 0x1f727f0: a(n) BlockClosure 0x7ffd19ed1630 I BlSpace>doLayout 0x1c63b40: a(n) BlSpace 0x7ffd19eb5238 M [] in BlSpaceFrameLayoutPhase>runOn: 0x1c9d2d8: a(n) BlSpaceFrameLayoutPhase 0x7ffd19eb5270 M BlockClosure>cull: 0x1f72390: a(n) BlockClosure 0x7ffd19eb52b0 M BlSpace>dispatchTimeEvent:during: 0x1c63b40: a(n) BlSpace 0x7ffd19eb5300 I BlSpaceFrameLayoutPhase>runOn: 0x1c9d2d8: a(n) BlSpaceFrameLayoutPhase 0x7ffd19eb5338 M BlSpaceFrame>runCurrentPhaseOn: 0x1c71028: a(n) BlSpaceFrame 0x7ffd19eb5380 I BlSpaceFrame>runOn: 0x1c71028: a(n) BlSpaceFrame 0x7ffd19eb53c8 I BlSpace>processPulse 0x1c63b40: a(n) BlSpace 0x7ffd19eb5408 I BlSpace>pulse 0x1c63b40: a(n) BlSpace 0x7ffd19eb5438 M [] in BlSpaceManager>pulse 0x1c71120: a(n) BlSpaceManager 0x7ffd19eb5480 M Array(SequenceableCollection)>do: 0x1c7b0f0: a(n) Array 0x7ffd19eb54c8 I BlSpaceManager>pulse 0x1c71120: a(n) BlSpaceManager 0x7ffd19eb5508 I BlUniverse>firePulse: 0x1c63e60: a(n) BlUniverse 0x7ffd19eb5550 I BlPulseLoop>firePulse 0x1c710c0: a(n) BlPulseLoop 0x7ffd19eb5580 M [] in BlPulseLoop>createLoopTask 0x1c710c0: a(n) BlPulseLoop 0x7ffd19eb55b0 M BlockClosure>repeat 0x1f68010: a(n) BlockClosure 0x7ffd19eb55f0 I [] in BlPulseLoop>createLoopTask 0x1c710c0: a(n) BlPulseLoop 0x7ffd19eb5630 I [] in BlockClosure>newProcess 0x1c7b1e0: a(n) BlockClosure Most recent primitives stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: = indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: **StackOverflow** stringHash:initialHash: compare:with:collated: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: basicNew basicNew stringHash:initialHash: **StackOverflow** stringHash:initialHash: stringHash:initialHash: **StackOverflow** stringHash:initialHash: stringHash:initialHash: **StackOverflow** stringHash:initialHash: primImagePath **StackOverflow** size indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: **StackOverflow** **StackOverflow** indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: primVmPath indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: **StackOverflow** indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: **StackOverflow** indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: perform: **StackOverflow** **StackOverflow** **StackOverflow** shallowCopy translate:from:to:table: stringHash:initialHash: translate:from:to:table: compare:with:collated: translate:from:to:table: stringHash:initialHash: translate:from:to:table: compare:with:collated: findFirstInString:inSet:startingAt: **StackOverflow** **StackOverflow** **StackOverflow** translate:from:to:table: stringHash:initialHash: translate:from:to:table: compare:with:collated: translate:from:to:table: stringHash:initialHash: translate:from:to:table: compare:with:collated: findFirstInString:inSet:startingAt: perform: class stringHash:initialHash: compare:with:collated: perform: class **StackOverflow** stringHash:initialHash: **StackOverflow** compare:with:collated: **StackOverflow** stringHash:initialHash: compare:with:collated: **StackOverflow** stringHash:initialHash: compare:with:collated: basicNew replaceFrom:to:with:startingAt: **StackOverflow** stringHash:initialHash: **StackOverflow** stringHash:initialHash: basicNew **StackOverflow** basicNew **StackOverflow** stringHash:initialHash: compare:with:collated: compare:with:collated: compare:with:collated: basicNew **StackOverflow** stringHash:initialHash: compare:with:collated: basicNew basicNew basicNew basicNew basicNew class stringHash:initialHash: basicIdentityHash basicIdentityHash basicNew basicNew **StackOverflow** stringHash:initialHash: **StackOverflow** parameterAt: stringHash:initialHash: setIsReadOnlyObject: stringHash:initialHash: = findSubstring:in:startingAt:matchTable: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: findSubstring:in:startingAt:matchTable: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: findSubstring:in:startingAt:matchTable: indexOfAscii:inString:startingAt: indexOfAscii:inString:startingAt: stringHash:initialHash: stringHash:initialHash: **StackOverflow** basicNew basicNew stringHash:initialHash: compare:with:collated: perform: newMethod:header: at:put: at:put: at:put: at:put: size **StackOverflow** class at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: objectAt:put: objectAt:put: objectAt:put: objectAt:put: objectAt:put: objectAt:put: objectAt:put: objectAt:put: stringHash:initialHash: stringHash:initialHash: objectAt:put: basicNew: instVarAt: instVarAt:put: instVarAt: instVarAt:put: objectAt:put: basicNew: instVarAt: instVarAt:put: instVarAt: instVarAt:put: objectAt:put: flushCache basicIdentityHash at: at: tempAt: tempAt: withArgs:executeMethod: instVarAt: instVarAt: instVarAt: basicNew **StackOverflow** findNextHandlerOrSignalingContext primitive primitive bitShift: bitShift: tempAt: class tempAt: basicNew shallowCopy shallowCopy shallowCopy stack page bytes 4096 available headroom 1988 minimum unused headroom 1568 (Segmentation fault) ./pharo-ui: line 11: 15537 Aborted (core dumped) "$DIR"/"pharo-vm/pharo" "$@"

1 0

SHA512 HMAC support in Pharo
by Jonathan van Alteren Aug. 14, 2019

Aug. 14, 2019

Hi all, For a client project we need support for SHA512 and SHA384 hashing and digital signatures with HMAC). Can anyone tell me if there is work (being) done on SHA512? We're on Pharo 7.0.3. At first, it didn't look too hard to refactor the SHA256 class in the System-Hashing package. That is... until I saw the use of ThirtyTwoBitRegister and the SHA256NonPrimitive and SHA256WithPrimitive classes in the Cryptography-SHA256 package. It seems to me that SHA512 will need a SixtyFourBitRegister class. Also, when I try to generate the constants on the fly with 64 bit values, the last 3 hexadecimal digits are zero (0). To me, this suggests that Pharo/Smalltalk might have issues working with 64 bit (float?) values. "(Integer primesUpTo: 312) collect: [:x | (((x raisedTo: 1/3) fractionPart) * (2.0 raisedTo: 64)) truncated hex]" Kind regards, Jonathan van Alteren Founding Member jvalteren(a)objectguild.com +31622500930

2 1

github.com/pharo-vcs/libgit2-pharo-bindings
by James Foster Aug. 14, 2019

Aug. 14, 2019

This package defines LGitCallback and provides an implementation of #âinitializeNullâ. It also provides an extension that has an implementation of #âbeNullâ. Where is the variable âthunkâ defined? Why is this in an extension? https://github.com/pharo-vcs/libgit2-pharo-bindings/blob/master/LibGit-Core… instance initialization initializeNull self beNull https://github.com/pharo-vcs/libgit2-pharo-bindings/blob/master/LibGit-Comp… *LibGit-Compatibility-Pharo7 beNull thunk := ExternalAddress null

1 0

[ANN] Pharo Pomodoro now on GitHub
by Torsten Bergmann Aug. 13, 2019

Aug. 13, 2019

I migrated my Pomodoro timer project to GitHub now: https://github.com/astares/Pharo-Pomodoro and you can load it using Catalog or script. I tested with Pharo 8. See also https://twitter.com/TorstenAstares/status/1161212424982290435 Bye T. And yes - additionally to my blog http://astares.blogspot.com you will also find my news on Twitter now https://twitter.com/TorstenAstares

4 5

Information on Spec development
by Cyril Ferlicot Aug. 13, 2019

Aug. 13, 2019

Hello everyone! This is an important update about the development of Spec. As you might have heard, we are working on Spec to release a new version in Pharo 8. One goal is to unify all Pharo interfaces behind one GUI framework and a second goal is to allow multiple back-ends (Morphic but also GTK, Bloc, ...). To reach those goals we have been updating the current version of Spec. We see now, however, that updating Spec directly creates troubles with migration. For example, we currently have a lot of deprecation warnings in Iceberg, because we can't update it without breaking Pharo 7 compatibility. After some discussions between the engineers working on Spec, here is our plan to improve the situation: We will copy all classes of Spec and rename them with the "Sp" prefix. (We will also ensure that every class of Spec started with the same prefix for consistency). For extensions methods, we will rename them to have a version different from Spec 1 (The spec from Pharo 7). Once done we will integrate this new version in Pharo 8. From there we will wait some weeks to let users who started to use the updated Spec change their projects to use this new Spec2. Finally, we will revert all changes that happened on Spec 1 and deprecate the packages. We hope this will make things easier for everyone. Have a nice day! -- Cyril Ferlicot https://ferlicot.fr

6 10

resetting iceberg
by Steve Quezadas Aug. 13, 2019

Aug. 13, 2019

I was playing around with the settings of iceberg and I must have messed up a setting or something because now when I open iceberg, I get a "object not found - no match for id". Is there a way to "reset the settings" of iceberg so I can at least open it back up? - Steve

1 0

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo Headless - Beta (Actually what is between Alpha and Beta)
by tesonep＠gmail.com Aug. 12, 2019

Aug. 12, 2019

Hi, The executables are not the same. We have 2 different now: the Stock VM (that is downloaded by the launcher, and it is the default download in Zero-conf), and the headless VM (this is downloaded by zero-conf when using vmLatestHeadless). Those platforms are not representative we currently have: OSX, Windows, and Linux all 64bits. We are working in ARM 32bits. In the near future, I will work on validating different flavors of Unix, but again It depends on the roadmap, and they are not there now. If someone requires some other platform we can talk to see how it can fit in the roadmap. Cheers, Pablo On Mon, Aug 12, 2019 at 10:03 AM Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > Yes. We will be testing these days and we will come back with more details. > > Two more questions: > - Is minheadlessVM now integrated in the regular VM binary or are the two different artifacts? > - Also are the platforms from https://github.com/pharo-project/opensmalltalk-vm/tree/pharo/platforms representative for minheadlessVM? > > Cheers, > Doru > > > > > On Aug 12, 2019, at 9:11 AM, tesonep(a)gmail.com wrote: > > > > Hi Doru, > > can you give us more insight of the errors? Because there should > > not be changes in the behavior of the VM. Maybe there are issues, we > > have used the Pharo tests as a guarantee and we are laking some tests. > > > > Cheers, > > Pablo. > > > > On Sun, Aug 11, 2019 at 9:04 PM Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> > >> Hi, > >> > >> > >> > >>> On Aug 11, 2019, at 5:29 PM, ducasse <stepharo(a)netcourrier.com> wrote: > >>> > >>> > >>> > >>>> On 11 Aug 2019, at 13:19, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >>>> > >>>> Excellent news! > >>>> > >>>> I should say that for GT we are currently using the minheadlessVM (Ronieâs work) out of the opensmalltalk-vm repo (https://bintray.com/opensmalltalk/vm/cog) and it works remarkably well. > >>>> > >>>> We started to play with your minheadlessVM. So far it looks like there are differences, although I am sure they are not large. > >>> > >>> like what? > >> > >> I do not know yet, but running GT in headless opens the window with the one from opensmalltalk-vm, but not with the new one. We did not yet look into details, but we will. > >> > >> Cheers, > >> Doru > >> > >> > >>>> So, what is the difference between the minheadlessVM built by you versus the one from opensmalltalk-vm? > >>>> > >>>> Cheers, > >>>> Doru > >>>> > >>>> > >>>>> On Aug 8, 2019, at 9:53 AM, tesonep(a)gmail.com wrote: > >>>>> > >>>>> TL;DR; > >>>>> ====== > >>>>> > >>>>> For the anxious, you can get real headless vm and image from zero-conf. > >>>>> > >>>>> $ wget get.pharo.org/64/80+vmHeadlessLatest | bash > >>>>> > >>>>> Zero conf scripts remain unchanged for users. > >>>>> > >>>>> However, if you are launching the VM by hand from the executable > >>>>> instead of the launcher scripts (pharo and pharo-ui) as in > >>>>> > >>>>> $ ./pharoexecutable Pharo.image > >>>>> > >>>>> the image will launch in headless mode and will not open a window. > >>>>> To launch it in headfull, you can use the --interactive argument after > >>>>> the image, which will make the image open a window using SDL2. > >>>>> > >>>>> $ ./pharoexecutable Pharo.image --interactive > >>>>> > >>>>> Long version > >>>>> ============ > >>>>> > >>>>> Hi, this mail is the happy intermediate result of the work that us, > >>>>> the Pharo Consortium Team, has been doing in the last couple of > >>>>> months. > >>>>> Our main objective is to have a real headless implementation of Pharo > >>>>> where all the responsibility to open or not a World window (or other) > >>>>> is handled by the image. > >>>>> For doing so we have done a series of modifications in the image and > >>>>> the VM side. > >>>>> We consider this is the path that Pharo 8 and following versions > >>>>> should follow, as it will severely improve server-side and command > >>>>> line Pharo and in building custom desktop applications. > >>>>> > >>>>> These modifications are available only in 64-bits machines (Windows, > >>>>> OSX, and Linux). > >>>>> ARM32 and 64bits headless is in the roadmap, but it is delayed because > >>>>> we have prioritized our three major platforms for this first couple of > >>>>> months. > >>>>> > >>>>> All this work is based in Opensmalltalk-VM and Ronnie's initial work > >>>>> on headless. > >>>>> We are really grateful to all the contributors in the history of this > >>>>> nice product. > >>>>> To achieve a real headless VM we have brought modifications in the > >>>>> source tree because most of the platform code to open and manipulate > >>>>> windows is not required anymore. > >>>>> Instead, we use the SDL2 library that implements a nice layer on top > >>>>> of the OS and allows us to manage on the image side through FFI. > >>>>> > >>>>> So this mail is now an open call for (beta?)testing. > >>>>> The sources of the current VM we are building are in the headless branch in > >>>>> https://github.com/pharo-project/opensmalltalk-vm > >>>>> And we have set up a CI that is both building and testing the VM in > >>>>> https://ci.inria.fr/pharo-ci-jenkins2/job/pharo-vm/job/headless/ > >>>>> > >>>>> For the future we have a lot of ideas, that will wait for another long > >>>>> email or a beer-talk @ESUG. > >>>>> We want to hear your ideas!! > >>>>> > >>>>> Image-Side Improvements > >>>>> ======================= > >>>>> > >>>>> - The image handles the creation or not of the main world window. > >>>>> - We incorporated the idea of World renderer, where different backends > >>>>> are used to render the world. > >>>>> - We have 3 backends: VM support (compatibility with non-headless > >>>>> VMs), and OSWindow with two backends: SDL and GTK3+. > >>>>> - The modifications in the image are fully backward compatible with > >>>>> the non-headless VM and are pushed since weeks in the latest 8.0 > >>>>> image. > >>>>> - We move the handling of events to the image side when using SDL and > >>>>> GTK3+, opening the door to a richer set of events and finer-grained > >>>>> control over them. > >>>>> - SDL and GTK versions are implemented using FFI calls. > >>>>> > >>>>> VM-Side Improvements > >>>>> ==================== > >>>>> > >>>>> - VMMaker code migrated to Tonel thanks to Feenk and included in the > >>>>> repository of the VM. > >>>>> - Making VMMaker execute in Pharo 7 and 8. > >>>>> - Removing GPL code from the VM repository (GDB). > >>>>> > >>>>> - Slowly adding new tests for the JIT / Slang and VMGeneration. > >>>>> - Restructuring of the source code. > >>>>> - A new simpler CMake build. > >>>>> - Generate VM code from Slang on each build. > >>>>> - A CI process to validate (including the run of the tests in Pharo > >>>>> and the ones adding to the VM). > >>>>> - Simplification of the codebase. > >>>>> > >>>>> - Maximize the reuse of code between the platforms (preferring the > >>>>> standard versions over the platform-specific). > >>>>> - Cleaning up duplicated code. > >>>>> - All the plugins are now external plugins. > >>>>> - The VM is now a dynamic library. This is a first step towards > >>>>> embedding Pharo into other applications. > >>>>> - The main executable is a thin frontend (you can change it or > >>>>> implement your own). > >>>>> > >>>>> - Removing unused plugins. > >>>>> - Improved crash dump. Especially the crash dump works now in Windows 64bits. > >>>>> - Dummy implementation of Security plugin (it is going away.... eventually). > >>>>> - Cleanup of SSL, UUID, and Socket plugin. > >>>>> > >>>>> - Cleanup of conditional code (Still to improve). > >>>>> - Improving the types used in the functions (we have to be neat to be > >>>>> multiplatform/multi-arch). > >>>>> - Improving the lookup of modules > >>>>> - Improving the logging of the VM > >>>>> - Improving the handling of VM arguments > >>>>> > >>>>> > >>>>> Thanks a lot for reading so long!! > >>>>> We hope you enjoy the VM and please tell us all the problems you find!! > >>>>> > >>>>> Pablo, Guille, and Esteban > >>>>> > >>>> > >>>> -- > >>>> feenk.com > >>>> > >>>> "Being happy is a matter of choice." > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>> > >>> > >>> > >> > >> -- > >> feenk.com > >> > >> "Speaking louder won't make the point worthier." > >> > >> > > > > > > -- > > Pablo Tesone. > > tesonep(a)gmail.com > > > > -- > feenk.com > > "What is more important: To be happy, or to make happy?" > > -- Pablo Tesone. tesonep(a)gmail.com

1 0

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo Headless - Beta (Actually what is between Alpha and Beta)
by tesonep＠gmail.com Aug. 12, 2019

Aug. 12, 2019

Hi Doru, can you give us more insight of the errors? Because there should not be changes in the behavior of the VM. Maybe there are issues, we have used the Pharo tests as a guarantee and we are laking some tests. Cheers, Pablo. On Sun, Aug 11, 2019 at 9:04 PM Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > > > > On Aug 11, 2019, at 5:29 PM, ducasse <stepharo(a)netcourrier.com> wrote: > > > > > > > >> On 11 Aug 2019, at 13:19, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> > >> Excellent news! > >> > >> I should say that for GT we are currently using the minheadlessVM (Ronieâs work) out of the opensmalltalk-vm repo (https://bintray.com/opensmalltalk/vm/cog) and it works remarkably well. > >> > >> We started to play with your minheadlessVM. So far it looks like there are differences, although I am sure they are not large. > > > > like what? > > I do not know yet, but running GT in headless opens the window with the one from opensmalltalk-vm, but not with the new one. We did not yet look into details, but we will. > > Cheers, > Doru > > > >> So, what is the difference between the minheadlessVM built by you versus the one from opensmalltalk-vm? > >> > >> Cheers, > >> Doru > >> > >> > >>> On Aug 8, 2019, at 9:53 AM, tesonep(a)gmail.com wrote: > >>> > >>> TL;DR; > >>> ====== > >>> > >>> For the anxious, you can get real headless vm and image from zero-conf. > >>> > >>> $ wget get.pharo.org/64/80+vmHeadlessLatest | bash > >>> > >>> Zero conf scripts remain unchanged for users. > >>> > >>> However, if you are launching the VM by hand from the executable > >>> instead of the launcher scripts (pharo and pharo-ui) as in > >>> > >>> $ ./pharoexecutable Pharo.image > >>> > >>> the image will launch in headless mode and will not open a window. > >>> To launch it in headfull, you can use the --interactive argument after > >>> the image, which will make the image open a window using SDL2. > >>> > >>> $ ./pharoexecutable Pharo.image --interactive > >>> > >>> Long version > >>> ============ > >>> > >>> Hi, this mail is the happy intermediate result of the work that us, > >>> the Pharo Consortium Team, has been doing in the last couple of > >>> months. > >>> Our main objective is to have a real headless implementation of Pharo > >>> where all the responsibility to open or not a World window (or other) > >>> is handled by the image. > >>> For doing so we have done a series of modifications in the image and > >>> the VM side. > >>> We consider this is the path that Pharo 8 and following versions > >>> should follow, as it will severely improve server-side and command > >>> line Pharo and in building custom desktop applications. > >>> > >>> These modifications are available only in 64-bits machines (Windows, > >>> OSX, and Linux). > >>> ARM32 and 64bits headless is in the roadmap, but it is delayed because > >>> we have prioritized our three major platforms for this first couple of > >>> months. > >>> > >>> All this work is based in Opensmalltalk-VM and Ronnie's initial work > >>> on headless. > >>> We are really grateful to all the contributors in the history of this > >>> nice product. > >>> To achieve a real headless VM we have brought modifications in the > >>> source tree because most of the platform code to open and manipulate > >>> windows is not required anymore. > >>> Instead, we use the SDL2 library that implements a nice layer on top > >>> of the OS and allows us to manage on the image side through FFI. > >>> > >>> So this mail is now an open call for (beta?)testing. > >>> The sources of the current VM we are building are in the headless branch in > >>> https://github.com/pharo-project/opensmalltalk-vm > >>> And we have set up a CI that is both building and testing the VM in > >>> https://ci.inria.fr/pharo-ci-jenkins2/job/pharo-vm/job/headless/ > >>> > >>> For the future we have a lot of ideas, that will wait for another long > >>> email or a beer-talk @ESUG. > >>> We want to hear your ideas!! > >>> > >>> Image-Side Improvements > >>> ======================= > >>> > >>> - The image handles the creation or not of the main world window. > >>> - We incorporated the idea of World renderer, where different backends > >>> are used to render the world. > >>> - We have 3 backends: VM support (compatibility with non-headless > >>> VMs), and OSWindow with two backends: SDL and GTK3+. > >>> - The modifications in the image are fully backward compatible with > >>> the non-headless VM and are pushed since weeks in the latest 8.0 > >>> image. > >>> - We move the handling of events to the image side when using SDL and > >>> GTK3+, opening the door to a richer set of events and finer-grained > >>> control over them. > >>> - SDL and GTK versions are implemented using FFI calls. > >>> > >>> VM-Side Improvements > >>> ==================== > >>> > >>> - VMMaker code migrated to Tonel thanks to Feenk and included in the > >>> repository of the VM. > >>> - Making VMMaker execute in Pharo 7 and 8. > >>> - Removing GPL code from the VM repository (GDB). > >>> > >>> - Slowly adding new tests for the JIT / Slang and VMGeneration. > >>> - Restructuring of the source code. > >>> - A new simpler CMake build. > >>> - Generate VM code from Slang on each build. > >>> - A CI process to validate (including the run of the tests in Pharo > >>> and the ones adding to the VM). > >>> - Simplification of the codebase. > >>> > >>> - Maximize the reuse of code between the platforms (preferring the > >>> standard versions over the platform-specific). > >>> - Cleaning up duplicated code. > >>> - All the plugins are now external plugins. > >>> - The VM is now a dynamic library. This is a first step towards > >>> embedding Pharo into other applications. > >>> - The main executable is a thin frontend (you can change it or > >>> implement your own). > >>> > >>> - Removing unused plugins. > >>> - Improved crash dump. Especially the crash dump works now in Windows 64bits. > >>> - Dummy implementation of Security plugin (it is going away.... eventually). > >>> - Cleanup of SSL, UUID, and Socket plugin. > >>> > >>> - Cleanup of conditional code (Still to improve). > >>> - Improving the types used in the functions (we have to be neat to be > >>> multiplatform/multi-arch). > >>> - Improving the lookup of modules > >>> - Improving the logging of the VM > >>> - Improving the handling of VM arguments > >>> > >>> > >>> Thanks a lot for reading so long!! > >>> We hope you enjoy the VM and please tell us all the problems you find!! > >>> > >>> Pablo, Guille, and Esteban > >>> > >> > >> -- > >> feenk.com > >> > >> "Being happy is a matter of choice." > >> > >> > >> > >> > >> > >> > >> > > > > > > > > -- > feenk.com > > "Speaking louder won't make the point worthier." > > -- Pablo Tesone. tesonep(a)gmail.com

1 0