November 2013 - swift-bugs - mailman3.cels.anl.gov

[Bug 1137] New: Foreach max threads possibly broken.
by bugzilla-daemon＠mcs.anl.gov 17 Nov '13

17 Nov '13

https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=1137 Summary: Foreach max threads possibly broken. Product: Swift Version: trunk Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Runtime AssignedTo: wozniak(a)mcs.anl.gov ReportedBy: hategan(a)mcs.anl.gov I ran this thing with foreach.max.threads set to a low number and it seemed like it only ran the first batch of jobs (i.e. foreach.max.threads x # of nested foreach loops), but then it got interrupted by an app error. So double check this. -- Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 1135] New: foreach steps
by bugzilla-daemon＠mcs.anl.gov 15 Nov '13

15 Nov '13

https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=1135 Summary: foreach steps Product: Swift Version: trunk Platform: PC OS/Version: Mac OS Status: NEW Severity: normal Priority: P2 Component: General AssignedTo: hategan(a)mcs.anl.gov ReportedBy: davidk(a)ci.uchicago.edu The script: foreach i in [10:10:0] { tracef("Iteration %i\n", i); } results in an infinite loop, where i always equals 10. foreach i in [10:20:-1] { tracef("Iteration %i\n", i); } This results in an infinite loop, with i decreasing forever. Should there be a check to only allow positive step values? -- Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 1131] New: Query workers through coasters
by bugzilla-daemon＠mcs.anl.gov 14 Nov '13

14 Nov '13

https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=1131 Summary: Query workers through coasters Product: Swift Version: trunk Platform: PC OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: Runtime AssignedTo: hategan(a)mcs.anl.gov ReportedBy: yadunandb(a)ci.uchicago.edu On clusters such as OSG, the ability to get a list of workers available to coaster-service and run setup scripts, or start shells on the workers would be very useful. Here's a list of functionality we'd like to see: - Query for a list of worker-ids, hostnames and statuses. - Run jobs on workers by addressing them with the worker-ids - Query for a list of jobs and statuses. - Separation between workers allocated through the same coaster service but associated with different runs / pools. - Broadcast a job to all workers These should be scriptable ( and hopefully also made available through the coaster-c-client) -- Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 1129] New: Documentation feedback
by bugzilla-daemon＠mcs.anl.gov 07 Nov '13

07 Nov '13

https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=1129 Summary: Documentation feedback Product: Swift Version: trunk Platform: PC OS/Version: Mac OS Status: ASSIGNED Severity: normal Priority: P2 Component: Documentation AssignedTo: davidk(a)ci.uchicago.edu ReportedBy: davidk(a)ci.uchicago.edu This is compiled form a list of suggestions from Roger Leroy Nelson on swift-support. General suggestions for the Swift documentation: - Highlight (perhaps with a distingishing forground or background color) the text in the code that is currently being described in the accompaning text. - I would strongly suggest applying text attributes such as bold and color to distingish: Swift keywords, operators, user identifiers, intrinsic functions/types/variables and Unix commands in the Swift code. [Also in the users manual use italics and/or underscore to indicate 'replace this with your identifier/code/whatever']. - Presumably identifiers cannot be Unix commands. I don't see in the User Guide variable naming limitations/conventions. - I didn't find in the documentation if system/environment variables available. Are they distinsuished with a prefix I.e. $? What about command line arguments? I started reading through the documentation in the order suggested. As I don't have a machine yet to install Swift on, so I didn't run the examples as instructed in the tutorial, but I don't think that would have help work through the items I found not well explained and confusing. I read through the tutorial trying not to refer to the user guide to get the first impressions, indeed the Documenation Web page implies one should read the tutorial first: "The User Guide provides more detailed reference documentation and background information on swift. It is assumed that the reader is already familiar with the material in the Quickstart and Tutorial documents." I record here my impressions and questions that came to my mind looking at the sample code and reading the text. [The question written here are rhetorical I am not asking for a reply to this posting]. 1. Introduction - Swift QuickStartGuide link is broken. - The section could be expanded to cover what problems Swift is designed to solve or simplify. I.e. what does Swift do that can't be done with basic Linux commands. Perhaps have a list of bullet points. Each of the bullet points should be covered and referred back to by the examples that illustrate the feature Swift provides. 2. Hello World. - How to run the program seems a little out of place/sequence here. (maybe move this to the end of the section, actually it is already covered in the QuickStart, which is implied to be read first: "Swift tutorial carries on where the Quickstart Guide leaves off," "It is assumed that the reader is already familiar with the material in the Quickstart and tutorial documents" - "The basic structure of this program is a type definition, an application procedure definition, a variable definition and then a call to the procedure." Is this the general structure of any program? - "First we define a new type, called messagefile. In this example, we will use this messagefile type for our output message." This seems more like a declaration to me, it even looks more like a forward declaration since I don't see any further qualifying information (type of what). - I presume message file would be any name of choosing - Move the sentence "Next we define a procedure called greeting." to before the "app .. { ... }" code snippet. - I see the word 'app' I am presuming it is a keyword declaring an 'application' as mentioned in section 3.2, but it could very easily be the name of the 'application'. [Actually no where in the tutorial document is 'app' defined. This really needs to be corrected. It is not even until section 2.4 of the USER GUIDE that it is said to be a keyword! And, no where is it defined what 'application' means in this context.] - I see {} so the language looks C-ish. What is the point of reference for approaching the language? Is there some other scripting language this is based off that I might relate to? - I see "app (messagefile t)" What's 't'? Hum, looks like procedure/function declaration, but the procedure is greeting(). I haven't been told what app is... Hum, is app() an intrinsic function of the switch language/system itself??? It appears to be associating the method with the type. My first impression with the 't' is it looks kind of like maybe a C++ template?? There is "type messagefile", maybe this informing the ?application? that greeting() is a member function of the messagefile type? so app(xx xxx) is the association mechanism. I read: "The actual file to use is specified by the return parameter, t." So 't' is not a type placeholder. So I am presuming that the procedure is returing a messagefile. So are we telling 'app' what greeting() will output/create. But I still don't know what is messagefile other than some sort of 'type'. [After reading all the way through the tutorial, I still have no idea what this part of the app statement is doing. And I don't understand why the variable 't'] [OK, I'm cheating now and skimming throught the user guide.... I still don't understand this mechanism.] - I read that the function is using the echo command. So I am presuming that everything between {} will be unix commands But I see "stdout=@filename(t)" which I don't recognize in any Unix shell script langauge. It appears stdout is being assigned the file name of v. [This construct is not intuitive]. I am curious why conventional Unix shell script redirection operators are not used. tr "[a-z]" "[A-Z]" < @filename(i) > @filename(o); or stdout=@filename(i); stdin=@filename(o); tr "[a-z]" "[A-Z]"; cat; where stdout and stdin remain associated with the named file until 'reassigned'. where "cat;" here would do the same thing as "cat @filename(i);" - And why are these double quotes in the Unix tr command argments? - At this point I would like to be introduced to the special characters. I.e. say that: @ denotes an intrinsic Swift function, [because I am thinking this is some Unix shell script construct that I don't know about. It is kind of Makefile-ish. ; is statement ?terminator?] I'm asking myself is stdout a Swift keyword or intrinsic variable? - I'm asking myself how is 't' associated with (messagefile t)? It is said to be a 'return parameter', A return parameter of my greeting() procedure? but it is a input parameter to the @filename() function. So does a procedure return the last statement thing processed? But wouldn't that be the return of echo? but the echo command doesn't return anything, and if it did it would be 0 (success) or a none zero value. I see: messagefile outfile <"hello.txt">; "Here we define a variable called outfile. " Again, here needs to be defined the <> ?operators? and a brief explaination as to how they are used (?in file system mapping?) which will be explained later. [Again I skim through the tutorial and the user guide, I find no definition of these. Indeed the <> quotation in further examples seems to have at least two semantic functions, and/or two syntactic forms, plus some HTML stuff, so this is rather confusing.] It would be helpful to include links to the user manual for the impatient reader. And/or statements saying something like "this will be explained below in section ___." Thank you for implementing my submitted comments and suggestions for the Swift documentation: Here are some additional suggestions. And I will send edits for some of the sections in separate emails. I still find reading this documentation to be a rather frustrating exercise although these are much improved from the previous version. Some additional general suggestions: For code snipit examples, I would suggest using identifier names that are clearly distingished from keywords. For example: int[auto] array The variable 'array' might be thought to be a keyword. I strongly suggest use syntax highlighting for the example code snippets . I know this might take a bit of editing work but it would be extremely helpful for the first time user. - normal text for user definitions identifier names, literal and figurative constants. - boldface for lexical elements (keywords operators, symbols). - italics for prototype (the user would replace this text with an actual identifier) -- Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 1127] New: Document Swift user interfaces
by bugzilla-daemon＠mcs.anl.gov 06 Nov '13

06 Nov '13

https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=1127 Summary: Document Swift user interfaces Product: Swift Version: trunk Platform: PC OS/Version: Mac OS Status: NEW Severity: normal Priority: P2 Component: Documentation AssignedTo: wozniak(a)mcs.anl.gov ReportedBy: davidk(a)ci.uchicago.edu Document Swift user interfaces (TUI, Swing), and how to do things like starting remote shells through coasters in tui mode -- Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 1125] New: Create a Windows site guide entry
by bugzilla-daemon＠mcs.anl.gov 06 Nov '13

06 Nov '13

https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=1125 Summary: Create a Windows site guide entry Product: Swift Version: unspecified Platform: PC OS/Version: Mac OS Status: ASSIGNED Severity: normal Priority: P2 Component: Documentation AssignedTo: davidk(a)ci.uchicago.edu ReportedBy: davidk(a)ci.uchicago.edu Create a Windows site guide entry -- Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0