Action in loop

After modifying this:

export const updateCurrentUser: UpdateCurrentUser<Partial<User>, User> = async (args, context) => {
  if (!context.user) {
    throw new Error('Usuario no autenticado');
  }

  const {
    firstName,
    lastName,
    gender,
    age,
    height,
    currentWeight,
    trainingGoal,
    experienceLevel,
    trainingFrequency,
    sessionDuration,
    healthConditions,
    equipmentAccess,
    dietaryPreferences,
    availableTime,
    exercisePreference
  } = args;

  const updatedUser = await context.entities.User.update({
    where: { id: context.user.id },
    data: {
      firstName,
      lastName,
      gender,
      age: age !== undefined ? parseInt(age.toString()) : undefined,
      height: height !== undefined ? parseFloat(height.toString()) : undefined,
      currentWeight: currentWeight !== undefined ? parseFloat(currentWeight.toString()) : undefined,
      trainingGoal,
      experienceLevel,
      trainingFrequency,
      sessionDuration,
      healthConditions,
      equipmentAccess,
      dietaryPreferences,
      availableTime,
      exercisePreference
    }
  });

  return updatedUser;
};

Based on

model User {
  id        String   @id @default(uuid())
  createdAt DateTime @default(now())

  email               String?  @unique
  username            String?  @unique
  lastActiveTimestamp DateTime @default(now())
  isAdmin             Boolean  @default(false)

  stripeId           String?   @unique
  checkoutSessionId  String?
  subscriptionStatus String? // 'active', 'canceled', 'past_due', 'deleted'
  subscriptionPlan   String? // 'hobby', 'pro'
  sendNewsletter     Boolean   @default(false)
  datePaid           DateTime?
  credits            Int       @default(3)
  firstName           String?
  lastName            String?
  gender              Gender   @default(OTHER)
  age                 Int?
  height              Float?
  currentWeight       Float?
  trainingGoal        TrainingGoal?
  experienceLevel     ExperienceLevel?
  trainingFrequency   TrainingFrequency?
  sessionDuration     SessionDuration?
  healthConditions    String?
  equipmentAccess     EquipmentAccess?
  dietaryPreferences  DietaryPreference?
  availableTime       AvailableTime?
  exercisePreference  ExercisePreference[]

  gptResponses        GptResponse[]
  contactFormMessages ContactFormMessage[]
  tasks               Task[]
  files               File[]
  weightLogs          WeightLog[] // Relación uno a muchos con registros de peso
  workouts  Workout[] // Relación de uno a muchos con rutinas
    monthlyPlans MonthlyPlan[] // Relación de uno a muchos con los planes mensuales

}

I get:

[ Server ] POST /operations/update-current-user 200 11.305 ms - 809
[ Server ] GET /auth/me 304 6.430 ms - -
[ Server ] POST /operations/update-current-user 200 10.870 ms - 809
[ Server ] GET /auth/me 304 6.616 ms - -
[ Server ] POST /operations/update-current-user 200 11.727 ms - 809
[ Server ] GET /auth/me 304 6.926 ms - -
[ Server ] POST /operations/update-current-user 200 13.249 ms - 809
[ Server ] GET /auth/me 304 9.781 ms - -
[ Server ] POST /operations/update-current-user 200 14.145 ms - 809
[ Server ] GET /auth/me 304 5.962 ms -

It is running all the time in a loop. https://gyazo.com/b4e078f0823fd7901889df19929de06b

Gyazo

Gyazo Screen Video

12 Replies

kapa.ai•2mo ago

Hi @NEROX. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- Based on the information provided, it seems like your updateCurrentUser action is being called in a loop, which is why you're seeing the repeated POST requests to /operations/update-current-user in your server logs. This behavior is likely not due to the action implementation itself, but rather how and where it's being called in your application. You might want to check the part of your code where this action is being invoked. It could be that it's placed inside a loop, or it's being triggered repeatedly due to some state changes or side effects. Unfortunately, without more information about the rest of your code, it's hard to provide a more specific solution. As for debugging, you can indeed add console.log statements in your action to print out more information. This can help you understand when and why the action is being called. For error handling in actions, you can use the HttpError class provided by Wasp. This allows you to throw errors with specific HTTP status codes and messages, which can be helpful for debugging. Here's an example from the Wasp documentation (https://wasp-lang.dev/docs/data-model/operations/actions#error-handling):

import { HttpError } from 'wasp/server'  
  
export const createTask = async (args, context) => {  
 throw new HttpError(  
 403, // status code  
 "You can't do this!", // message  
 { foo: 'bar' } // data  
 )  
}

import { HttpError } from 'wasp/server'  
  
export const createTask = async (args, context) => {  
 throw new HttpError(  
 403, // status code  
 "You can't do this!", // message  
 { foo: 'bar' } // data  
 )  
}

If you're still having trouble, you might want to ask for help on the Wasp Discord server (https://discord.com/channels/686873244791210014/1215945587841831033) or open an issue on the Wasp GitHub repository (https://github.com/wasp-lang/wasp/issues). ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @NEROX, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

NEROXOP•2mo ago

@kapa.ai It's used here:



  const handleChange = (name: keyof FormData, value: string | string[] | ExercisePreference[]) => {
    if (name === 'exercisePreference') {
      setFormData(prev => ({ ...prev, [name]: value as ExercisePreference[] }));
    } else {
      setFormData(prev => ({ ...prev, [name]: value }));
    }
  };

const handleSubmit = async (e: React.FormEvent) => {
    e.preventDefault();
    try {
      await updateCurrentUser({
        ...formData,
        age: formData.age ? parseInt(formData.age) : undefined,
        height: formData.height ? parseFloat(formData.height) : undefined,
        currentWeight: formData.currentWeight ? parseFloat(formData.currentWeight) : undefined,
        exercisePreference: formData.exercisePreference as ExercisePreference[]
      });
      // Redirect or show success message
    } catch (error) {
      console.error('Error updating user:', error);
    }
  };

kapa.ai•2mo ago

Let me check the knowledge base for you. One moment! :books: ---------------------- Based on the provided code, it seems like the updateCurrentUser action is being called when a form is submitted. The form data is passed to the action as arguments. If the form data for age, height, and currentWeight exist, they are parsed to integers or floats respectively. The exercisePreference is cast to an array of ExercisePreference. The try/catch block is used to handle any errors that might occur during the execution of the updateCurrentUser action. If an error occurs, it is logged to the console. The issue you're experiencing, where the updateCurrentUser action is being called in a loop, might be due to how the handleSubmit function is being used in your application. If this function is being called repeatedly, it would result in the updateCurrentUser action being called in a loop as well. You might want to check where and how the handleSubmit function is being invoked in your application. Make sure it's not being called inside a loop or being triggered repeatedly due to some state changes or side effects. If you're still having trouble, you might want to ask for help on the Wasp Discord server (https://discord.com/channels/686873244791210014/1215945587841831033) or open an issue on the Wasp GitHub repository (https://github.com/wasp-lang/wasp/issues). ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @NEROX, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

NEROXOP•2mo ago

@kapa.ai In a form:

<form onSubmit={handleSubmit} className="space-y-6">
          <div className="grid grid-cols-2 gap-4">
            <Input
              label="First Name"
              value={formData.firstName}
              onChange={(e) => handleChange('firstName', e.target.value)}
              className="w-full dark:bg-gray-800 dark:text-white...."
            />

kapa.ai•2mo ago

Let me check the knowledge base for you. One moment! :books: ---------------------- The handleSubmit function is being used as the event handler for the form's onSubmit event. This means that when the form is submitted (usually by clicking a submit button), the handleSubmit function is called. In the handleSubmit function, the updateCurrentUser action is called with the current form data. This action is used to update the current user's data. The handleChange function is used as the event handler for the onChange event of the input field. This means that whenever the user types into the input field, the handleChange function is called with the new value of the input field. The handleChange function updates the formData state with the new value of the input field. The formData state holds the current values of all the fields in the form. Here's a simplified version of your code to illustrate this:

<form onSubmit={handleSubmit}>
  <input
    value={formData.firstName}
    onChange={(e) => handleChange('firstName', e.target.value)}
  />
  <button type="submit">Submit</button>
</form>

<form onSubmit={handleSubmit}>
  <input
    value={formData.firstName}
    onChange={(e) => handleChange('firstName', e.target.value)}
  />
  <button type="submit">Submit</button>
</form>

In this code: - When the user types into the input field, the handleChange function is called with the new value of the input field. - When the user clicks the "Submit" button, the form is submitted and the handleSubmit function is called. - The handleSubmit function calls the updateCurrentUser action with the current form data. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @NEROX, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

NEROXOP•2mo ago

@kapa.ai but why is the action geting called every second y an infinite loop? Which files or could be causing this?

kapa.ai•2mo ago

Let me check the knowledge base for you. One moment! :books: ---------------------- The issue you're experiencing, where the updateCurrentUser action is being called in a loop, is likely not due to the action or the handleSubmit function itself, but rather how and where these are being used in your application. Here are a few things you could check: 1. Form submission: Ensure that the form is not being submitted repeatedly. This could happen if there's some code that's programmatically triggering the form's submit event. 2. State changes: If the formData state changes, it could potentially trigger a re-render of your component, which might cause the form to be submitted again. Check if there's any code that's updating the formData state continuously. 3. Side effects: If you're using React hooks like useEffect in your component, ensure that they're not causing the form to be submitted repeatedly. For example, if you have a useEffect that's dependent on the formData state and submits the form as a side effect, it could cause an infinite loop. 4. Parent component: Check the parent component that's rendering the form. If the parent component is re-rendering for some reason, it could cause the form to be submitted again. Without more information about the rest of your code, it's hard to provide a more specific solution. If you're still having trouble, you might want to ask for help on the Wasp Discord server (https://discord.com/channels/686873244791210014/1215945587841831033) or open an issue on the Wasp GitHub repository (https://github.com/wasp-lang/wasp/issues). ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @NEROX, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

NEROXOP•2mo ago

@kapa.ai I'm pretty sure it's due to updatecurrentuser's action, check it out: //@src/user/operations.ts

export const updateUserById: UpdateUserById<{ id: string; data: Partial<User> }, User> = async (
  { id, data },
  context
) => {
  if (!context.user) {
    throw new HttpError(401);
  }

  if (!context.user.isAdmin) {
    throw new HttpError(403);
  }

  const updatedUser = await context.entities.User.update({
    where: {
      id,
    },
    data,
  });

  return updatedUser;
};

export const updateCurrentUser: UpdateCurrentUser<Partial<User>, User> = async (args, context) => {
  if (!context.user) {
    throw new Error('Usuario no autenticado');
  }

  const {
    firstName,
    lastName,
    gender,
    age,
    height,
    currentWeight,
    trainingGoal,
    experienceLevel,
    trainingFrequency,
    sessionDuration,
    healthConditions,
    equipmentAccess,
    dietaryPreferences,
    availableTime,
    exercisePreference
  } = args;

  const updatedUser = await context.entities.User.update({
    where: { id: context.user.id },
    data: {
      firstName,
      lastName,
      gender,
      age: age !== undefined ? parseInt(age.toString()) : undefined,
      height: height !== undefined ? parseFloat(height.toString()) : undefined,
      currentWeight: currentWeight !== undefined ? parseFloat(currentWeight.toString()) : undefined,
      trainingGoal,
      experienceLevel,
      trainingFrequency,
      sessionDuration,
      healthConditions,
      equipmentAccess,
      dietaryPreferences,
      availableTime,
      exercisePreference
    }
  });

  return updatedUser;
};

kapa.ai•2mo ago

Let me check the knowledge base for you. One moment! :books: ---------------------- The updateCurrentUser action you've shared seems to be correctly implemented. It checks if a user is authenticated, extracts the necessary fields from the arguments, and then calls the update method on the User entity to update the user's data in the database. The infinite loop issue you're experiencing is likely not due to the action itself, but rather how and where it's being used in your application. Here are a few things you could check: 1. Form submission: Ensure that the form is not being submitted repeatedly. This could happen if there's some code that's programmatically triggering the form's submit event. 2. State changes: If the formData state changes, it could potentially trigger a re-render of your component, which might cause the form to be submitted again. Check if there's any code that's updating the formData state continuously. 3. Side effects: If you're using React hooks like useEffect in your component, ensure that they're not causing the form to be submitted repeatedly. For example, if you have a useEffect that's dependent on the formData state and submits the form as a side effect, it could cause an infinite loop. 4. Parent component: Check the parent component that's rendering the form. If the parent component is re-rendering for some reason, it could cause the form to be submitted again. Without more information about the rest of your code, it's hard to provide a more specific solution. If you're still having trouble, you might want to ask for help on the Wasp Discord server (https://discord.com/channels/686873244791210014/1215945587841831033) or open an issue on the Wasp GitHub repository (https://github.com/wasp-lang/wasp/issues). ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @NEROX, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

NEROXOP•2mo ago

@kapa.ai and this?:

  useEffect(() => {
    if (user) {
      const lastSeenAt = new Date(user.lastActiveTimestamp);
      const today = new Date();
      if (today.getTime() - lastSeenAt.getTime() > 5 * 60 * 1000) {
        updateCurrentUser({ lastActiveTimestamp: today });
      }
    }
  }, [user]);

kapa.ai•2mo ago

Let me check the knowledge base for you. One moment! :books: ---------------------- The useEffect hook you've shared is set to run whenever the user object changes. Inside the hook, it checks if the user exists and then calculates the difference between the current time and the user's lastActiveTimestamp. If the difference is greater than 5 minutes (5 * 60 * 1000 milliseconds), it calls the updateCurrentUser action to update the lastActiveTimestamp to the current time. This could potentially cause an infinite loop if the updateCurrentUser action is causing the user object to change, which in turn triggers the useEffect hook again. Here's how it could happen: 1. The useEffect hook runs because the user object has changed. 2. The updateCurrentUser action is called, which updates the lastActiveTimestamp in the database. 3. The updated user data is fetched from the database, causing the user object to change. 4. Because the user object has changed, the useEffect hook runs again, and the cycle repeats. To fix this, you could add a condition to check if the lastActiveTimestamp needs to be updated before calling the updateCurrentUser action. This would prevent unnecessary updates and avoid the infinite loop. Here's an example:

useEffect(() => {
  if (user) {
    const lastSeenAt = new Date(user.lastActiveTimestamp);
    const today = new Date();
    // Only update if the difference is greater than 5 minutes
    if (today.getTime() - lastSeenAt.getTime() > 5 * 60 * 1000) {
      // Only call the action if the lastActiveTimestamp is different
      if (user.lastActiveTimestamp !== today) {
        updateCurrentUser({ lastActiveTimestamp: today });
      }
    }
  }
}, [user]);

useEffect(() => {
  if (user) {
    const lastSeenAt = new Date(user.lastActiveTimestamp);
    const today = new Date();
    // Only update if the difference is greater than 5 minutes
    if (today.getTime() - lastSeenAt.getTime() > 5 * 60 * 1000) {
      // Only call the action if the lastActiveTimestamp is different
      if (user.lastActiveTimestamp !== today) {
        updateCurrentUser({ lastActiveTimestamp: today });
      }
    }
  }
}, [user]);

This code will only call the updateCurrentUser action if the lastActiveTimestamp is different from the current time, preventing unnecessary updates. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @NEROX, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

NEROXOP•2mo ago

✅ Solved (Claude): The problem seems to be in the way the data update is being handled. The current version is trying to update all the fields every time, even if they haven't changed. This may be causing unnecessary updates and triggering the loop you are experiencing. The solution does the following: Creates an updateData object that will only contain the fields that actually need to be updated. Iterates over the properties of args and only includes in updateData those that are not undefined. Specifically handles the cases of age, height, and currentWeight to ensure that they are correctly converted to numbers. Updates the user with only the fields that have changed.

Gaming

Programming

Action in loop