新しい投稿

查找

お知らせ
· 2024年11月7日

[Global Masters] Halloween Contest Results!

Thank you to everyone who joined our Spooky Stories Contest 👻 on Global Masters and shared your eerie tales with us! We loved diving into your mysterious, thrilling, and downright spooky stories. It was tough to pick just one winner, but we finally have a standout story to celebrate.

   

 And the winners are... 

🎉 Congratulations to @Robert Barbiaux and @Caro 
 Each of you has earned a spooky bonus of 500 points!

🏆Story by @Robert Barbiaux 

Twenty years ago, because of a software bug, I had to sort digital photos into the appropriate folders by eyeing them one by one, in the dead of the night. Those pictures came from a pathology lab macroscopy department, some of them are still haunting me and sending chills down my spine.

🏆Story by @Caro 

I once identified a bug in the codebase that had gone unnoticed for almost fifteen years. Looking at that old code felt like looking at the ghost of coders past. Truly spooky to imagine how it remained undetected for so long.

Feeling that eerie shiver? 👀💀
But it’s not just the winning stories that deserve attention! Here are some other very captivating entries from our participants:

Story by @Jason Neate 

In late October, as a student struggling to get a COBOL assignment to compile. I asked my tutor for help, but she was busy. Two days later, she sat down with me as I walked her through the code, explaining every stage. Mid-sentence, I froze, stunned. I turned to her, a look of horror in my eyes, and managed to stammer, “I.. I.. forgot a full stop. Slowly, I turned back to the screen, added the missing full stop, and hit "compile." It compiled. My tutor called it her “Fastest code review ever!”

Story by @Alessandra Carena 

I found the culprit behind our crashing app—a rogue print("Here!") statement buried in a function. Easy fix, right? I deleted it, saved, redeployed… but the logs still print “Here! Here! Here!”. A real nightmare! Finally, we discovered an old, hidden script on the test server, containing the original print("Here!"). We deleted it, refreshed the logs… silence at last. The bug was gone, but the horror lingers on.

Story by @Guillermo Velasco 

*Teams Notification Alert*

Story by @Vishal Pallerla 

Once, I rushed to fix a minor bug in the one of the tables in Prod SQL Server. I updated something using an update query UPDATE table SET column ='value'; I ran it forgetting the WHERE clause which updated entire table instead of just one record that was supposed to. My heart raced as I realized it and updated the data from back up, learning the hard way the importance of double-checking queries.

Story by @Danny Wijnschenk 

oops, i passed the *dead* line !

Happy Halloween, and stay tuned for more exciting activities!

P.S. Not a Global Masters member yet? Join the program here using your InterSystems SSO credentials.

1 Comment
ディスカッション (1)2
続けるにはログインするか新規登録を行ってください
お知らせ
· 2024年11月6日

VS Code スニペットを IPM _ ZPM パッケージとして共有する

VS Code には強力なスニペット機能が備わっており、Marketplace は開発者がスニペットを公開して使用できる方法を提供しています。 ただし、Marketplace での公開は面倒である上、InterSystems コーダーを対象としたスニペットは、現実的には Marketplace の訪問者のごく少数にしか興味を持たれません。

このことから、oex-vscode-snippets-template を作成する発想を得ました。InterSystems 開発者向けのコードスニペットを公開するための専用リポジトリを作成する GitHub テンプレートです。

ディスカッション (0)0
続けるにはログインするか新規登録を行ってください
記事
· 2024年11月6日 2m read

第十三章 本地进程间通信(管道) - 用于进程间通信的 READ 命令

第十三章 本地进程间通信(管道) - 用于进程间通信的 READ 命令

用于进程间通信的 READ 命令

语法

READ:pc readargument,...

READ 从管道读取数据。

其中reargument可以是:

formatting-mode
string
variable:timeout
*variable:timeout
variable#n:timeout

I格式化模式参数与管道一起使用。 I 参数允许对命名管道发出定时READ,而不会丢失跟随在一个部分记录中的任何数据。错误。当在READ上使用此参数时, READ会忽略消息。

默认情况下,I格式化模式的值处于关闭状态。如果在没有超时的情况下在READ命令中包含此参数,则进程将挂起,直到有数据要处理。

ディスカッション (0)1
続けるにはログインするか新規登録を行ってください
お知らせ
· 2024年11月6日

Concurso de Tutoriais Técnicos InterSystems IRIS - Prazo Prorrogado!

Olá Comunidade! 

Para você que não conseguiu finalizar o seu tutorial ou aos que pretendem concorrer com mais de um tutorial, temos uma grande surpresa.
Estamos estendendo o prazo do nosso concurso até o dia 24 de Novembro


 

Isso mesmo! Agora você não tem mais desculpa de ficar de fora.
Participe do nosso último concurso de 2024, e concorra aos super prêmios enquanto compartilha conhecimento com a Comunidade de Desenvolvedores. 

Esperamos por ótimos tutoriais! 😃

ディスカッション (0)1
続けるにはログインするか新規登録を行ってください
質問
· 2024年11月6日

Histogram data being pushed to github

There are a select few in the group that have been using Github as a Local Client push to a Repository setup in GitHub. Questions were brought up today about the security, and possible issues when it comes to data being pushed in this method.

Looking over code we have noticed that there is Histogram data within some of the class files that could be considered a security issue. Does anyone else have concerns with the Histogram data being within the class files pushed up to github?

1 Comment
ディスカッション (1)2
続けるにはログインするか新規登録を行ってください