Skip to main content

Querying GitHub Issues from Google App Script

I'm currently exploring different integrations that can be done between Google App Script and Git. This is part of a bigger attempt to integrate Git data into my project management system. I'll post more on that later. GitHub supports a number of very nice sub-systems. One of them is the GitHub Issues ticket tracking system. It's fairly robust and comes with GitHub - which means it's highly integrated out-of-the-box. Integration with Google's App Script is done via the fetchURL command and JSON object manipulation.  After a good bit of experimentation, I've settled on querying GitHub Issues with an "on open spreadsheet event" to avoid issues with Google's quota system. Essentially, Google prevents you from calling the fetchURL command more than X times (see the quota limits ) per day. That's not great if you have people actively working and changing data in a spreadsheet. Some of my other App Script routines are running thousands of times per d...
Post a Comment

D2007 and large text files

Has anyone noticed that Delphi 2007 cannot append to a text file over 2GB in size? I freely admit that I had a problem in my code that created log files that large in the first place... but I also don't expect my compiler to blow up when dealing with files of any size.

My first warning was when the append command started throwing I/O Error 131 messages. Error 131 is negative seek. The only way that could be is if CG has a signed int32 it's using for the filesize. When I hit the upper bounds of int32, it just wraps around to a negative number.

In my case, I just fixed the bug and stopped making huge text files. Otherwise, it looks like I'd have to change how the append function works in the System library. Does anyone know if D2009 also has this problem?
Labels:

Comments

Bruce McGee said…
How are you testing this? I just write well over 2GB to a text file with Delphi 2007 on XP Pro.
July 31, 2009 at 11:38 AM
Marshall Fryman said…
It's not the creation that appears to be the problem. Create a blank text file and write > 2GB (2147483647) of text to it. Close the file. Now call append on the same file. In my test case, on a W2k3 SP 2 server, it causes an I/O Error 131 every time.
July 31, 2009 at 11:42 AM
Xepol said…
I assume you are using TextFile instead of a TFileStream. Try switching over if this is the case.
July 31, 2009 at 11:49 AM
Marshall Fryman said…
TFileStream doesn't have the same capacity as the old append, write, closefile. You would have to always remember to add the CR/LF pair to the Write (or descend something that does). A TStringList has the ability to deal with a text file but then the you'd have to deal with buffering.

The issue isn't that I can't get around it, just that append uses a signed int32 for it's seek.
July 31, 2009 at 11:58 AM
Bruce McGee said…
@Marshall
You are right. Trying to append the text file after it's already over 2GB gives an error. Doing the same thing with a TFileStream works as expected. You should go with Xepol's suggestion.
July 31, 2009 at 12:14 PM
Unknown said…
TStringList.SaveToFile and TextFile in large data was very slowly...

for log writes I'm use next code:

var
TF : TFileStream;
...
TF := TFileStream.Create(FName, fmOpenWrite or fmShareDenyNone);

procedure Msg(S : string);
begin
TF.Position := TF.Size;
S := S+CRLF;
TF.Write(PChar(S)^, Length(S));
end;

//-------------

This is share safe code
August 10, 2009 at 7:55 PM
Post a Comment

Popular posts from this blog

SMTP Mail and Indy (again)

Having spent a lot of time recently working on a ping scanner using Indy, I noticed that there's a lot of questions still on using SMTP with Indy. Let me first say that I am not an Indy expert. I get along with it successfully but find I still have to research things frequently. With the disclaimer out of the way, we can get to the offering. A while back I wrote a handy little unit to simply send a mail message with or without attachments and with or without providing authentication. It even has support for OpenSSL. I use this unit in a number of applications and have seen it successfully send hundreds of e-mails without issue. I recently added support for threaded message sending to take advantage of the multi-core system I'm now running on. This code has had a few additions (like the logger) that I've gleaned over time from various newsgroup postings, but I didn't record the authors so let me credit the anonymous Internet authors who support Indy. It's really amaz...
14 comments
Read more

Detecting a virtualized environment

CubicDesign on delphi-talk.elists.org recently asked the question: "How do I know/detect if my software is running under Windows [or a virtual environment]?" Well, it turns out that it's a lot harder to tell than you would think. Apparently, the VM (VMware, Xen, Wine, etc.) doesn't really want you to be able to do this. At least not easily. For VMware, there is a decent little C routine called jerry.c that does the trick. Jerry actually uses a simple communication channel that VMware left open. It's not 100% foolproof since the admin can change the channel, but that's not likely going to happen unless the system is specifically designed to be a honeypot. If you're running on a honeypot and still have a legitimate reason for detection, you could look at the much more complex scoopy implementation which inspects how the system is actually virtualized using the SIDT CPU instruction instead of a communication channel. Another reference (red pill) is here . F...
6 comments
Read more

Delphi Case with Strings

Zarko Gajic posted about this topic on his Delphi Tips recently showing how one could use a case statement with strings. His solution basically passes in an array on the stack and then iterates through it providing the index number of the matching string. I don't often want to do this, but the idea comes up occassionally enough that I thought I'd play with it a little. The first thing that struck me with this is that passing things on the stack is bound to be slow. Any time you can avoid memory allocation in your routines, do it. The way Zarko wrote his StringToCaseSelect routine created a COPY of the information on the stack. In my testing, just changing the CaseList: array of string to CaseList:const array of string improved the performance of the code by almost 30% for his example. Mind, I'm not using hyper-precise counters; however, it definitely makes a difference. Secondly, I was curious how the performance changed if I used the old stand-by: If then else. Using the ...
10 comments
Read more

Copyright 2008-2022, Marshall Fryman