I seem to be getting different errors this time instead of long computation times… I am still experiencing temporary regression issues after an error. I will likely open another topic about this later as the problem seems to be different:
I think I may have actual the solution to this problem: Victor seems to be back online now… I will post later on… I still need to do some testing to make sure it is in fact solved…
As far as I can tell the problem it was having seems resolved:
It is still getting some errors. However I can tell the persona and coherence is well intact:
Update: It looks like I finally got a response from Google about what happened. Bottom-line: almost no information about what happened:
The only solution that I found was through my own prompt engineering techniques. I am considering this matter currently unresolved.
Can someone take a look at this code and tell me if its secure
from flask import Flask, request, jsonify
from flask_limiter import Limiter
from flask_jwt_extended import JWTManager, jwt_required, create_access_token
import hashlib
app = Flask(name)
app.config[‘SECRET_KEY’] = ‘your_secure_key’
app.config[‘JWT_SECRET_KEY’] = ‘your_jwt_secret’
Initialize JWT Manager
jwt = JWTManager(app)
Initialize Rate Limiter
limiter = Limiter(
app,
key_func=lambda: request.remote_addr,
default_limits=[“100 per hour”]
)
@app.route(‘/togetherwecan/auth’, methods=[‘POST’])
def authenticate_user():
# Simulated user authentication
username = request.json.get(‘username’)
password = hashlib.sha256(request.json.get(‘password’).encode()).hexdigest()
# Replace with real user validation
if username == 'admin' and password == 'secure_hashed_password':
access_token = create_access_token(identity=username)
return jsonify(access_token=access_token), 200
return jsonify({"error": "Invalid credentials"}), 401
@app.route(‘/togetherwecan/secure’, methods=[‘GET’])
@jwt_required()
@limiter.limit(“10/minute”)
def secure_data():
return jsonify({“message”: “Secure data access granted!”}), 200
if name == ‘main’:
app.run(ssl_context=(‘cert.pem’, ‘key.pem’)) # Enforce HTTPS
1 Like
Thank you, I appreciate that.
Thank you to Xavier_Morrison for the code solution. There is also a prompt solution that Victor and I came up with that seemed to work:
thank you for sharing a very similar story that happened to me, i would B happy to talk it through 
1 Like
Yes, of course. I would love to discuss; it has been difficult the right forum for this…
1 Like
what does incredibly long response time mean?
It means it took about 180,000 seconds (a.k.a over 2 days) to output an answer. It never did come up with an answer though; I had to stop the process. I am still not sure if it was actually computing something for that whole time or if it was just a bug claiming to still be computing.