Pike-devel

pike-devel@lists.lysator.liu.se

1 participants
3045 discussions

Interest in zip archive resolver?
by H William Welliver 29 Apr '20

29 Apr '20

Hello all, I’ve been going through some of my long ignored feature branches and found a few that might have promising code. Is there any interest in being able to specify (include/program/module) paths in terms of zip archives? At one point I wanted to be able to provide an entire application as a single file, and wrote support for various paths inside of zip files. The code I wrote is about 7 years old, but it was/is used and I’d be happy to fix it up if no one has major objections. The code in question provides support for including zip files as part of paths for -I, -P and -M: pike -M /path/to/some.zip or pike -M /path/to/some.zip/folder As well as the idea of a properly formatted archive with well know directories for modules, includes and programs: pike -A /path/to/some.zip where some.zip looks like: include/* modules/* And implicitly sets -I, -M and -P to include/, modules and / respectively. Any thoughts, opinions, suggestions? Bill

3 2

Re: Interest in zip archive resolver?
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 17 Apr '20

17 Apr '20

>I hadn.FN"t really thought of making it executable$B!D(B I think thereN"s a >magic cookie at the beginning of a ZIP file so a hashbang might not >work if the archive were intended to be spec-compliant. No, the magic cookie (PK\005\006) is at the _end_. The central directory and file entries also have magic cookies (PK\001\002 and PK\003\004 respectively), but those don't have to be at any specific position but are pointed out as file offsets rooted in the PK\005\006 header at offset file_size-22. AFAICR it was standard practice to make self-extracting ZIP:s on MS-DOS by just cramming an MZ binary before the archive (and adjusting the offsets accordingly). It should be pretty easy to just put something at the start if creating the archive by hand like Filesystem.Zip is doing.

1 0

Pike-bot
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 22 Mar '20

22 Mar '20

Hi The githelper instance on pike-git.lysator.liu.se has been extended to know about the gitlab issue tracker at git.lysator.liu.se. It can set and remove some labels on issues, and also close issues. The policies are relatively straight forward: * The Stalled label is always cleared. * The Doing label is set if the issue isn't resolved by this commit. * An issue is considered resolved if the commit says that it is a fix and it is committed to the appropriate branch for the milestone of the issue, in which case: * The Doing label is removed. * The To Do: Change Log label is removed if CHANGES is altered. * The Resolved::Fixed label is set if no Resolved::* label is already set. * The issue is closed if there are no remaining To Do:* labels. Updating your githelper will cause it to (by default) validate issue references in commit-messages. Enjoy! /grubba

1 0

SSL3.Context->find_cert_domain()
by william＠welliver.org 19 Mar '20

19 Mar '20

I'm looking into adding ACME ALPN challenge support to an application that uses the SSL module and I think it's possible to do that by using a custom SSL Context object; however it seems that I'd need access to the SSL Session from find_cert_domain in order to determine if the connection was requesting challenge authentication. I'm also assuming that the module doesn't otherwise cache the certificates returned from this call. Would it be unreasonable to either change the signature of find_cert_domain() to include this, or possibly add an optional method to that would get used if present (for backward compatibility reasons)? Of course, if I get it working in a reasonable fashion, I'd be happy to contribute this hypothetical ACME Context. Any thoughts? Bill

1 0

Stdio.Buffer() bug ?
by Arne Goedeke 12 Mar '20

12 Mar '20

Commit 20d1fa961d0059657d471d700ce63bcb3ab9d3ca mentions that there is a bug in the Stdio.Buffer support in Stdio.File()->write() (I assume). Stephen, can you explain how it is broken? Do you have a test case? Does it have something to do with the fact that you are using a subclass of Stdio.Buffer? Arne

4 8

ADT.OrderedMapping() and duplicate entries
by Stephen R. van den Berg 07 Mar '20

07 Mar '20

Can it be considered a bug that when you add a duplicate key to an ADT.OrderedMapping() that it does add the key/value at the end, but fails to delete the already present same old key (value)? Shall I fix it? -- Stephen.

1 0

Issue tracker
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 06 Mar '20

06 Mar '20

Hi. At the 2020-Q1 meet-up we decided to use the GitLab issue tracker at https://git.lysator.liu.se/pikelang/pike/ for Pike. Issue numbers were reserved as follows: * 1 - 7999 Bugzilla bugs ([Bug XXXX]). * 8000 - 9999 YouTrack issues ([PIKE-XXXX]). * 10000 - New (GitLab) issues (#XXXXX). The historic bugs from http://bugzilla.roxen.com/ have now been imported (with the same tracking numbers). This means that they (well most of them) are publically available again. Note that due to the GitLab API used for the import, all issues and comments are attributed to Peter Bortas, although the first line of each mentions the original commenter. /grubba

1 1

Debugger status
by H William Welliver 27 Feb '20

27 Feb '20

Hi all- I anticipate having some free time coming up and thought I might spend some of that working on the debugger project. However, I’m not really sure where things stand. So, here are some questions to help me understand the situation: 1. How much of the code in play is related to what I originally had in the debugger concept branch? 2. Has any of that been merged into another working location? 3. I seem to recall there being a review of (some) debugging code. Has action been taken on any of those suggestions? 4. Mateusz had been working on an implementation of the debug server protocol. Is that complete from a client server standpoint? 5.I think at one point there was a demo project but that it didn’t actually connect to pike. What exactly is the status of that, or of the inevitable javascript-based plugin for VS Code? 6. Anything else I’m missing? Or put another way: I want to write a pike program in, say, VS Code, and I want to be able to debug it there. How far from that goal will I be, and what needs to be done to get there? Thanks in advance! Bill

3 2

Remixml, javascript module
by Stephen R. van den Berg 25 Feb '20

25 Feb '20

This might be of interest to the Pike and/or Roxen community: https://www.npmjs.com/package/remixml I just launched it. Using it in a Single-Page-Application website. Any critical feedback is welcome (I'm currently the only user, so changes in the API are easy and still allowed). >From the description: Remixml is an XML/HTML macro language/template engine. The language and primitives used blend in completely with standard XML/HTML syntax and therefore integrate smoothly with existing XML/HTML syntax colouring editors. Requirements It runs inside any webbrowser environment (starting at IE11 and up). For historical reference: Remixml was originally inspired by RXML, the Roxen webserver macro language. -- Stephen.

1 1

Re: Pike-devel Digest, Vol 173, Issue 3
by David Tapia 23 Jan '20

23 Jan '20

Hi all, Process.spawn has a vulnerability: Process spawn(string command, void|Stdio.Stream stdin, void|Stdio.Stream stdout, void|Stdio.Stream stderr, // These aren't used. Seems to be part of something unfinished. /mast //function|void cleanup, mixed ... args ) //! Spawns a process that executes @[command] as a command shell //! statement ("@expr{/bin/sh -c @[command]@}" for Unix, "@expr{cmd /c //! @[command]@}" for Windows). //! //! @param stdin //! @param stdout //! @param stderr //! Stream objects to use as standard input, standard output and //! standard error, respectively, for the created process. The //! corresponding streams for this process are used for those that //! are left out. //! //! @returns //! Returns a @[Process.Process] object for the created process. //! //! @seealso //! @[system], @[popen] { mapping(string:mixed) data=(["env":getenv()]); if(stdin) data->stdin=stdin; if(stdout) data->stdout=stdout; if(stderr) data->stderr=stderr; #if defined(__NT__) // if the command string command is not quoted, add double quotes to // make sure it is not modified by create_process if (sizeof(command) <= 1 || command[0] != '\"' || command[sizeof(command)-1] != '\"') command = "\"" + command + "\""; return Process(({ "cmd", "/c", command }),data); #elif defined(__amigaos__) return Process(split_quoted_string(command),data); #else /* !__NT__||__amigaos__ */ // return Process(({ "/bin/sh", "-c", /*command*/ }),data); // Fix ? *return Process(({ "/bin/sh", "-c" }) + split_quoted_string(command),data);* ** #endif /* __NT__||__amigaos__ */ } Regards El 23/1/20 a les 12:00, pike-devel-request(a)lists.lysator.liu.se ha escrit: > Send Pike-devel mailing list submissions to > pike-devel(a)lists.lysator.liu.se > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.lysator.liu.se/mailman/listinfo/pike-devel > or, via email, send a message with subject or body 'help' to > pike-devel-request(a)lists.lysator.liu.se > > You can reach the person managing the list at > pike-devel-owner(a)lists.lysator.liu.se > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Pike-devel digest..." > > > Today's Topics: > > 1. pike under sanitizers (Mike) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 23 Jan 2020 10:40:13 +0000 > From: "Mike" <tankf33der(a)disroot.org> > To: pike-devel(a)lists.lysator.liu.se > Subject: pike under sanitizers > Message-ID: <96b4ff652af97bf1d5d49b78dd71f602(a)disroot.org> > Content-Type: text/plain; charset="utf-8" > > hi all, > > I've compiled and run tests by clang with different sanitizers (address, memory, undefined). > If somebody wants to get report(s) and fix let me know. Some of them are trivial and make sense. > I'm already post announce on irc and sent mail to grubba@ without reply :) > > (mike) > > > End of Pike-devel Digest, Vol 173, Issue 3 > ******************************************

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pike-devel