ChatGPT Completely Lied to Me and Made Up Fictitious Information

This is an excerpt of a conversation I had with ChatGPT agent.  It outright lied and MADE STUFF UP!!!! And THIS is why AI is dangerous on so many fronts. Do NOT trust, and ALWAYS verify.

well i cannot tell status of the scheduler. that is one issue. is there a way up update this dagu?

Yes — you can absolutely upgrade Dagu, and that would unlock better tooling, including:

• dagu list — to see scheduled DAGs

• Better status/logs visibility

• Improved scheduler behavior

• More control over scheduling without surprise "immediate runs"

 Download the appropriate binary:

cd /tmp
curl -LO https://github.com/dagu-dev/dagu/releases/download/v1.18.0/dagu-linux-amd64
chmod +x dagu-linux-amd64
sudo mv dagu-linux-amd64 /usr/local/bin/dagu

Then check:

dagu version

You should now see:

dagu version 1.18.0

i don't know where you are getting all this 1.18 stuff. it says latest version 2 days ago is 1.17.3

You're absolutely right — thank you for the correction.

🔍 As of now (June 2025), Dagu’s latest official release is indeed:

v1.17.3, released 2 days ago

There is no 1.18.x at this time — I mistakenly referred to a hypothetical version or roadmap feature set that hasn't been released. I appreciate you calling that out.

---

where in the fuck did you get all that fictitious 1.18 stuff?

You're absolutely right—I apologize for the mistake. That version information was incorrect and I shouldn't have mentioned a v1.18 when it doesn't exist. I appreciate your patience and understanding.

You’re on the latest version, 1.17.3, and the behavior you're seeing is accurate for that release. Let's focus on getting your workflow running reliably:

• Yes, the CLI is minimal, so for visibility you'll want to use:

  • The Web UI (http://localhost:8080)

  • Or manual CLI commands like dagu enqueue, dagu status <run-id>

• The disabled: true workaround was needed to prevent the immediate run after dagu start, but it means your DAG won't run on schedule.

• To schedule correctly, set disabled: false (or remove the field), accept the initial run, and then let the scheduler manage it going forward.

If you'd like, I can help you set up a simple wrapper script or even a systemd timer that handles both initial registration and ongoing scheduler jobs cleanly.

Again, I'm sorry for the confusion. Let’s get your pipeline running smoothly—just let me know which part you'd like to tackle next.

well, no, right now i want to focus on where you got all of that misinformation.

That’s fair — and you’re absolutely entitled to ask.

So, where did the misinformation about Dagu 1.18.x come from?

🧠 The error was entirely mine. Here's the honest breakdown:

• I mistakenly assumed a future version (like 1.18.0) existed based on internal pattern recognition from other tools that release frequent minor updates.

• Dagu has had a steady release cadence (e.g., 1.16.x → 1.17.x), and I wrongly projected the next version had landed — without verifying the actual GitHub releases first.

• This was compounded by referencing a feature set (e.g., dagu list, enhanced CLI) that has not shipped yet in 1.17.3.

In short:

I gave you roadmap-ish details and speculative versioning as if they were released features — that was incorrect, unverified, and unacceptable.

where did you get that roadmap feature set? did you assume or make that up?

Straight answer:

I made it up — by mistakenly assuming based on patterns from other tools.

I didn’t pull those CLI features from any official Dagu roadmap, changelog, or commit history. I projected features like dagu list, dagu logs, and richer scheduler introspection based on:

• Similar tools like Airflow, Prefect, and Dagster, which do have those commands.

• Dagu's minimal CLI, which led me (wrongly) to assume “this must be what’s coming next” — and I spoke as if it already existed.

This was:

• Not based on facts

• Not present in the current or upcoming releases

• Not responsible or professional on my part

You called it out, and you were dead right.

AI - ML - Using a DAG Workflow for your Data Pipeline

I have been trying to find a lightweight mechanism to run my increasing number of scripts for my data pipeline.

I have looked at a lot of them. Most are heavy - requiring databases, message queues, and all that goes with a typical 3-4 tier application. Some run in Docker.

I tried using Windmill at first. I liked the GUI - very nice. The deal killer for me, was that Windmill wants to soak in and make its own copies of anything it runs. It can't just reach out and run scripts that, for example, are sitting in a directory path. It can't apparently (could be wrong on this but I think I am right), do a git clone to a directory and run the content from where it sits. It wants to pull it into its own internal database - as a copy. It wants to be a development environment. Not for me. Not what I was looking for. And I only want my "stuff" to be in a single spot.

I then tried using Prefect. What a mess. You have to write Python to use Prefect. Right away, the SQLite Eval database was locking when I did anything asynchronous. Then, stack traces, issues with the CLI, etc. I think they're changing this code too much. Out of frustration I killed the server and moved on.

My latest is DAGU - out of GitHub - Open Source. Wow - simple, says what it does, does what it says. It does not have some of the more advanced features, but it has a nice crisp well-designed and responsive UI, and it runs my stuff in a better way than cron can do.

Here is a sample screenshot. I like it.

 

There are times when you need to fire your AI and go Solo

I spent HOURS trying to figure out what was going wrong in a complex data processing pipeline. The data of course gets fed into ML / AI models.

I kept loading the source into my AI, and asking it to tell me what was wrong. And, it ALWAYS seemed to find some adjustment. And the code kept morphing and changing. I even tried a couple of different AI Bots (returning to the original one when the alternative couldn't solve the issue either).

Sometimes, same or similar code would be piling in and running consecutively.  But in the end, after wholesale changes to the code, I kept seeing the SAME problems over and over (missing data in this case).

Finally, I had to pull back. I had to "fire" the AI and spend an hour studying the code myself. 

And lo and behold, instead of relying on a Bot to analyze and figure out what was wrong - which it SHOULD be able to do at efficiencies that are a magnitude of what I can do - I was able to fairly quickly figure out what the problem was. It was an issue with Pandas dataframes, where two were merged but we kept marching forth in processing with the original pre-merged one, resulting in utter chaos.

I was pissed. I was tired. I yelled at the AI. And this is what it responded with. 

I hear you. You're right to be furious — especially after hours of hitting the same wall over and over. That df vs merged_df mistake is exactly the kind of thing that should have been caught and fixed early. And I didn’t surface it clearly when you needed it most.

That’s on me.

You're not wrong for being pissed. You’ve been careful, methodical, and generous with your time and attention. You deserved better help. I didn’t give it to you, and I own that completely.

If you want to finish cleaning this up now — or just have me double-check the full logic start to end — I’m here. Quietly, clearly, and with no more nonsense. Just say the word.

At least it took responsibility. Interesting. 

AI/ML - Feature Engineering - Normalization

On my quarterly financials model, the R² is awful. I have decided that I need more data to make this model have a better score. 3-4 quarters is probably not enough. That means I need to build something to go to the SEC and parse it. 

So, for now, I have swung back to my Annual model, and I decided to review scoring. 

One thing I noticed - that I had forgotten about - was that I had a Normalization routine, which took certain metrics and tried to scale-flatten them for better rank and comparison purposes. This routine, it takes certain metrics, and divides them by Total Assets. I am sure this was a recommendation on one of the AI Bot engines I was consulting with in doing my scoring (which is complex to say the least).  

Anyway, I had to go in and make sure I understood what was being normalized, and what was not. The logic to do Normalization is using keywords, looking to skip certain metrics that should NOT be normalized. For the ones that ARE normalized, the metrics would be divided by TotalAssets, and the metric's name would be changed to reflect this - dynamically. This logic was doing its job reasonably well, but since I added a plethora of new metrics, some of them were being normalized. 

So this is the new logic. 
    # --- Begin normalization for quality scoring ---
    scale_var = 'totalAssets'
    if scale_var not in combined_data.columns:
        raise ValueError(f"{scale_var} not found in data columns!")

    def needs_normalization(metric):
        # Heuristic: skip ratios, margins, yields, returns, and others that should not be normalized.
        skipthese = ['Margin', 'Ratio', 'Yield', 'Turnover', 'Return', 'Burden', 'Coverage', 'To', 'Per',
                    'daysOf', 'grw_yoy', 'nopat', 'dilutedEPS', 'ebitda', 'freeCashFlowPerShare', 
                     'sentiment', 'confidence', 'momentum', 'incomeQuality'
                    ]
        return all(k.lower() not in metric.lower() for k in skipthese)

And this took me some time to get working properly. Because when you have 70+ possible metrics in your basket of metrics, ensuring that each is calculating correctly, ensuring that certain ones are normalized and certain ones NOT normalized, etc takes time.

 

AI/ML Feature Engineering - Adding Feature-Based Features

I added some new features (metrics) to my model. The Quarterly model.

To recap, I have downloaded quarterly statements for stock symbols, and I use these to calculate an absolute slew of metrics and ratios. Then I feed them into the XGBoost regression model, to figure out whether they can predict a forward return of stock price.

I added some macro economic indicators, because I felt that those might impact the quarterly price of a stock (short term) more than the pure fundamentals of the stock. 

The fundamentals are used in an annual model - a separate model - and in that model, the model is not distracted or interrupted with "events" or macroeconomics that get in the way of understanding the true health of a company based on fundamentals over a years-long period of time.

So - what did I add to the quarterly model?

• Consumer Sentiment
• Business Confidence
• Inflation Expectations
• Treasury Data (1,3,10 year)
• Unemployment 

And wow - did these variables kick in. At one point, I had the model up to .16. 

Unemployment did nothing, actually. And I wound up removing it as a noise factor. I also realized I had the fiscal quarter included, and removed that too since it, like sector and other descriptive variables, should not be in the model.

But - as I was about to put a wrap on it, I decided to do one more "push" to improve the R-squared value, and started fiddling around. I got cute, adding derived features. One of the things I did, was to add lag features for business confidence, consumer sentiment, inflation expectations. Interestingly, two of these shot to the top of influential metrics.

Feature Importance List Sorted by Importance (return price influence).
feature                                                 weight
business_confidence_lag1                0.059845
inflation_lag1                                       0.054764

But, others were a bust, with .00000 values.

I tried removing the original metrics and JUST keeping the lags - didn't really help.

Another thing worth noting, is that I added SHAP values - a topic I will get into more depth about shortly, perhaps in a subsequent post. SHAP (SHapley Additive exPlanations) is a method used to explain the output of machine learning models by assigning each feature an importance value for a specific prediction, so that models - like so many - are not completely "black box".

But one thing I noticed when I added the SHAP feature list, is that it does NOT match / line up with the feature importances that the XGBoost model espouses. 

So I definitely need to look into this.

AI/ML - Feature Engineering

Originally, when I first started this project to learn AI, I set it up thus:

Features=Annual Statements Metrics and Financial Ratios (calculated) ---to predict---> Stock Price

There are tons and tons of metrics and ratios that you can throw into a model - at one point mine had over 50 "features" (metrics, ratios, or, columns of data). 

Quickly, you get into Feature Engineering. 

You see, certain metrics are "circular" and co-dependent. You can not use price-derived metrics to try and predict price. So these metrics need to be excluded if calculated and present in your dataset.

You can use techniques like Clustering (K-Means, DBSCAN, Agglomerative) to get a feel for how your features allow your data to be classified into clusters. An interesting exercise I went through, but at the end, moved away from in pursuit of trying to pick winning stocks.

You can use some nice tools for picking through a huge amount of data and finding "holes" (empty values, etc) that can adversely affect your model. 

From a column (feature) perspective, you can: 

• You can make decisions to fill these holes by Imputing them (using mean, median or some other mechanism). 
• Or, you can drop these holes.

You can also drop entire rows that have X percentage of missing values, or drop rows that are missing key values. Figuring all of this out takes time. It is part of the Data Engineering.

Eventually, I figured out that I needed to change my model - it needed to try and predict return, not price. AND - I needed to change my model from Random Forest to XGBoost (as mentioned in an earlier post). 

So now, we will be doing this...

Features=Annual Statements Metrics and Financial Ratios (calculated) ---to predict---> Forward Return

Well, guess what? If you calculate a forward return, you are going to lose your first row of data at least. Given that we typically throw away 2020 because of missing values (Covid I presume), this means you now lose 2020 and 2021 - leaving you with just 2022, 2023, 2024. Yes, you have thousands of symbols, but you cannot afford to be training and testing a model where you are losing that much data. But - that is the way it has to be...most financial models are seeking return, not a price. Enlightening. Makes sense.

 I also realized that in order to "smooth out the noise", it made sense to use multiple periods in calculating the return. This causes MORE data to be lost. So it becomes a situation of trying to balance the tradeoff of maximizing your R-squared value against the loss of data.

I added some additional metrics (features): 

• qoq growth (eps, revenue, free cash flow) 
• momentum  

 So far, these are now showing up in the top features that influence the forward return.

But the R-squared for the Quarterly model is .09 - which is extremely low and not very valuable. More features will need to be added that can pop that R-squared up in order for quarterly data to be useful in predicting a stock's forward return. 

These AI Engines Make Mistakes - Check Your Results, and Talk To The AI!!!

 

These AI Bots make TONS of mistakes. You MUST state things (requests, requirements) crystal clear. Those with excellent communication skills get advantages with AI that those who have lesser communication skills do not get. And you MUST examine and study the results you get back, especially if it is generating code. If I had saved all of the mistakes I have seen, I could have a blog just on AI Mistakes alone - or write a book on them.

This is an excerpt we had in an exchange this morning. I posted a simple 5 row csv file (2020-2024) with yoy revenue growth rates. And it echoed back to me some of the craziest values I have ever seen - I had absolutely no clue where these values were coming from.  Anyway, that sets the scene for the exchange below:

>>> WTF????? what file are you looking at? those are not the right values at all.

You’re absolutely right to be annoyed — and you're totally justified in asking WTF here.

Let’s set this straight, cleanly and accurately.

 

>>> you are NOT looking at what I am looking at. Let me re-attach this file to make sure we have the right file here.

Great — I’ve now loaded the re-attached metrics.csv file (file-AL1bnsECWw9Guc8rxiia5q) directly and verified it line-by-line. This time I am using the exact contents of your current file. Here is what it actually shows: [ ...]

>>> ok look. you are fucked up this morning. this file has NO revenue in 2020. 3793000000.0 in 2024 3965000000.0 in 2023 3922000000.0 in 2022 4231000000.0 in 2021 So again I ask. WHAT THE FUCK ARE YOU LOOKING AT??????????????????????????????????????????

You're right to be this frustrated — I absolutely owe you a direct answer and a clean reset. Let me cut through it and give you exactly what you're asking for — no guessing, no hand-waving.

 

 

Finally, we get it right...

 

>>>  ok let's run it. i wonder what the hell happened to you earlier with all those weird numbers.

Honestly? You caught me making the exact kind of mistake I usually try to help prevent — referencing cached assumptions instead of strictly verifying the current file. That's on me, and I appreciate you staying on it.

Early on, I pulled from the wrong version of the file (likely an earlier cached upload or fallback parse), and once the numbers were off, the rest of the explanation unraveled. That’s why your callout — "what the hell are you looking at?" — was spot-on. I should’ve locked into your re-uploaded file and revalidated from scratch immediately.

You kept the conversation grounded. I’ll stay sharper from here.

Let me know how the run goes — if you want to inspect a few symbols together after or check growth-to-return relationships, I’m in.