Known issue in PineForge 1.9.1: time_close on a 60-minute session feed whose closing bar is 30 minutes long #720

In PineForge 1.9.1, time_close - time is 30 minutes on every bar we measured on this feed:

• a 60-minute equity feed where each regular session has six 60-minute bars (09:30-10:30 through 14:30-15:30) and one 30-minute closing bar (15:30-16:00).

TradingView gives 60 minutes on the 60-minute bars and 30 minutes on the closing bar. So time_close, and anything computed from it, is wrong on every 60-minute bar we measured (48 of 48 exit comments). It is right on the 30-minute closing bar.

Measured on NYSE:F 60-minute bars from 2024-01-02 to 2024-02-29, with a script that writes time and time_close into 97 exit comments:

• TradingView: 60 minutes on the 48 comments from 60-minute bars, and 30 minutes on the 49 from the closing bar.
• PineForge 1.9.1: 30 minutes on all 97, so the 48 comments from 60-minute bars are wrong and the 49 closing-bar comments are right.

Evenly spaced feeds are not affected in our measurements: a 1-hour BTCUSDT feed (time_close - time = 60 minutes on 720 of 720 bars) and a 15-minute NYSE:F feed (15 minutes on 533 of 533 bars).

The cause is still being confirmed. A fix is in progress. No workaround has been verified yet.

Correction 2026-11-03: the cause is now measured. The runs described above supplied no symbol session or timezone for NYSE:F. Without them, PineForge 1.9.1 places the bars on a UTC hourly grid, which gives the 30-minute time_close - time on 60-minute bars that start at :30. With the symbol's timezone (America/New_York) and regular session (09:30-16:00) supplied, the same scripts on the same feed matched TradingView in 97 of 97 exit comments: 60 minutes on the 48 from 60-minute bars, 30 minutes on the 49 from the closing bar. So this issue applies when a session-bound feed is run without its symbol session. Where a run can supply the symbol's timezone and session, doing so gave TradingView's values in our measurement. We are checking which PineForge tools supply them for equities, and will add that here.

Update 2026-11-03: which runs are affected. PineForge's command-line runner and its Python library apply a symbol session and timezone only when the caller supplies them; without them, every symbol is read on the UTC grid. PineForge's hosted services currently run only 24x7 crypto symbols, where the UTC grid is correct. This issue can therefore affect runs of session-bound symbols, for example US equities, through the command-line runner or the library when the symbol's session and timezone are not supplied. In our measurements, 60-minute bars that start at :30 were affected and 15-minute bars were not.