2024-W25

• Sheet view not working as expected,
• Sticky for tabs and controller,
• Post change set request here,
• By mistake I commited the changes in Git to another branch, consolidated branch I created for deployment, now doing cherrypick of that commit, this is a good use case of cherry pick, 7fc56fbf8daed90babc53b951d2814f5067ca962
• Product: Kyle Moore, Bhavnesh Diwan
  Description:We want this flag as part of enabling Sheetview feature in Ontario region once deployment of release 24.23 over Ontario label on 19th June is done for prod environment. We have completed sanity of our changes in beta environment as well. Also have a go ahead from product on this. We want this flag as part of pre-preparation if teams found any issue after enabling Sheetview feature in Ontario region once deployment of release 24.23 over Ontario label on 19th June is done for prod environment. We have completed sanity of our changes in beta environment as well. Also have a go ahead from product on this.
• DynaCon (prod) | Changeset #281445 (env.works)
• 4388 is current and 5326 is || to it, diff of endpoints
• 4450 is the MS2 US for Headshot feature
• Sports/MarketConfig like Sheetview flag
• SGP- same game parlay
• Neetu is checking 5476 merge conflict  while Gayathri Eruvuri is addressing new comment on 2644
• Pipeline steps

UpdateImageProperties

The UpdateImageProperties method is called twice in the UploadImage method for different reasons:

1. First Call to UpdateImageProperties:

   • This initial call retrieves the current values of the specified image properties (imagePropertyValue and imageIdPropertyValue) from the ParticipantImageInfo object.
   • These values are then used for the subsequent operations, such as uploading the image and potentially deleting the old image.

2. Second Call to UpdateImageProperties:

   • After uploading the image, if the upload response contains a new file name (response.FileName), the image properties in the ParticipantImageInfo object need to be updated with these new values.
   • This second call ensures that the ParticipantImageInfo object reflects the latest image information after the upload operation.

Here’s a simplified view of why each call is necessary:

• First Call: Retrieve existing values for processing.
• Second Call: Update values with new information if available.

The redundancy you see in the UpdateImageProperties method regarding the repeated case “Headshot” needs correction. However, the structure of calling the method twice in UploadImage is correct for its intended purpose.

• 4212 - Can we push today?
• 4115- get it done
• 4057- get update
• Outright market- Webtrack
• Kiran is saying we can reduce the story story points further.
• CG we can give 2 days but we should be in time with dev.
• 4115- do follow up Kiran told
• Kiran: Who will be doing analysis?
• Gromming: 5480, 5326, 5324 (RFC),
• dynacon Health config changes,
• 
• Datalayer plugin for chrome.
• Followups are taking long time and they shouldn’t be developers work to ping in every thread and ask for recent update.
• 3440
• I need to start taking the scrum calls.

Dev

Todo

• Pritam check theme video. ✅ 2024-08-20
• Dikshit get comments of Naveen ✅ 2024-08-20
• 5354- Catch up at 2 to get meeting details and get analysis started. ✅ 2024-08-20
• After call post meeting link for 5480

Questions

• Q. Why is 4528 assigned on Akshay’s name?
• Q. Why have procedures getting used to retrieve data in Sports Admin? and Why have they being placed in Sportsbook.Dal.Impl namespace?
• Q. CDS where the interaction with Sports Admin is taking place? In CDS Sports Admin module in Sports adminfacade.
• Q. How to see PR links in Jira ticket?
• Q. Is the communication between CDS and Sports Admin happening byprotobuff?
• Q. What are other teams?