Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue862 - implemented multi media bids #993

Closed
wants to merge 49 commits into from
Closed

Issue862 - implemented multi media bids #993

wants to merge 49 commits into from

Conversation

muncha
Copy link
Contributor

@muncha muncha commented Aug 7, 2019

This is a correction to closed PR #965. The "forceBanner" flag is removed, and as suggested by @hhhjort, multiple bid requests are being added to the stack for multimedia.

…in keeping the indexes straight in MakeRequests. I've added back a couple of test cases, which now pass.
@muncha
Copy link
Contributor Author

muncha commented Aug 28, 2019

@mansinahar LGTM, again.

@stale
Copy link

stale bot commented Sep 4, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Sep 4, 2019
@muncha
Copy link
Contributor Author

muncha commented Sep 4, 2019

@hhhjort @mansinahar Thank you for all of your help on this. I hope that your very helpful advice was not the result of too much frustration on your part. I'm wondering where we're at on this, considering:

  • Since getting to where I had incorporated all of @mansinahar 's comments (~28th), Beachfront has gotten a real RTB video endpoint set up for this. In another branch, off of this one, I have everything set up to handle that endpoint, as well as the one here. A lot of the streamlining and optimization changes in this PR made that a pretty straight forward task.
  • There are test cases that really should have passed but were instead giving me weird errors. Removing them got validation.sh to pass, but obviously either something's wrong with the test cases or with the bidder.

Should I put in issues for those? Is there anything else with this PR? Should it be merged, or should it be closed in favor of a PR that covers the points above?

@stale stale bot removed the stale label Sep 4, 2019
@mansinahar
Copy link
Contributor

@muncha This just got delayed due to the long holiday weekend. I will find some time to get a review on this tomorrow.

@muncha
Copy link
Contributor Author

muncha commented Sep 5, 2019

@mansinahar no worries - I've got one of these problematic test cases worked out (I wasn't including the status in the mockResponse - doh) and close on the other, I hope. So I'll push when I have both of those, and I'll save my RTB video implementation for another PR.

@mansinahar
Copy link
Contributor

@muncha Awesome! Just lemme know when it is ready to review again and I will be happy to take a look. Thanks :)

…em was that an empty adapters.RequestData was being added. Also added test case unmarshal-error-but-another-good-video.json, which throws and tracks the unmarshal error and dumps that bad one, then adds and requests the good video imp.
@muncha
Copy link
Contributor Author

muncha commented Sep 5, 2019

@mansinahar LGTM

@hhhjort
Copy link
Collaborator

hhhjort commented Sep 9, 2019

Is this ready for review now?

@muncha
Copy link
Contributor Author

muncha commented Sep 10, 2019

Yes, please.

@stale
Copy link

stale bot commented Sep 17, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Sep 17, 2019
@muncha
Copy link
Contributor Author

muncha commented Sep 20, 2019

@hhhjort - I'm not sure if this should be merged to master of if it should wait for my next PR, which includes all of this. It's no rush as far as I'm concerned. Unless there is a reason to merge as far as repo history sanity or similar, I'd think wait. My next PR enables options for ADM vs. nurl responses on video. I should have that pushed in the next day or two. Assuming waiting, should I go ahead and close this?

@stale stale bot removed the stale label Sep 20, 2019
@hhhjort
Copy link
Collaborator

hhhjort commented Sep 20, 2019

i am good with waiting

@mansinahar
Copy link
Contributor

@muncha I am good with waiting too. Let's close this once you have the other PR up

@muncha
Copy link
Contributor Author

muncha commented Sep 26, 2019

I'm closing this and submitting a new pull request which includes these changes and adds the ability to return AdM or nurl responses for video.

@muncha muncha closed this Sep 26, 2019
SyntaxNode pushed a commit that referenced this pull request Oct 22, 2019
This is on top of the changes from #993, which has not been merged, and this pretty much wraps up the major changes that we are doing for now. In addition to giving the titular choice, this makes a simple guess at device type and security.
tgeeting pushed a commit to triplelift/prebid-server that referenced this pull request Oct 23, 2019
This is on top of the changes from prebid#993, which has not been merged, and this pretty much wraps up the major changes that we are doing for now. In addition to giving the titular choice, this makes a simple guess at device type and security.
katsuo5 pushed a commit to flux-dev-team/prebid-server-1 that referenced this pull request Dec 1, 2020
This is on top of the changes from prebid#993, which has not been merged, and this pretty much wraps up the major changes that we are doing for now. In addition to giving the titular choice, this makes a simple guess at device type and security.
katsuo5 pushed a commit to flux-dev-team/prebid-server-1 that referenced this pull request Dec 2, 2020
This is on top of the changes from prebid#993, which has not been merged, and this pretty much wraps up the major changes that we are doing for now. In addition to giving the titular choice, this makes a simple guess at device type and security.
katsuo5 pushed a commit to flux-dev-team/prebid-server-1 that referenced this pull request Dec 4, 2020
This is on top of the changes from prebid#993, which has not been merged, and this pretty much wraps up the major changes that we are doing for now. In addition to giving the titular choice, this makes a simple guess at device type and security.
@muncha muncha deleted the issue862 branch December 29, 2020 17:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants