Fix for potential issue with context broker policies

Cerfoglg commented 1 year ago

Proposed changes

Checking for post requests to avoid issue with retrieving data

Fixes #186 Fixes #185

Types of changes

What types of changes does your code introduce to the project: Put an x in the boxes that apply

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] I have signed the Contributor License Agreement
[x] I have updated the RELEASE NOTES
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

"Martel Open Source Software Individual Contributor License Agreement"

"Contributing to Anubis"

"Anubis Release Notes"

github-actions[bot] commented 1 year ago

CLA Assistant Lite bot All contributors have signed the CLA ✍️

Cerfoglg commented 1 year ago

This is not a fix for the issue of the token potentially getting dropped as reported by one user, but I was unable to recreate said issue on my side, and I can't locate an exact reason with the code or current setup, so unless we get more information or further test, we can't pinpoint that particular issue. This pull will fix the nil errors of LUA

c0c0n3 commented 1 year ago

I have read the CLA Document and I hereby sign the CLA

orchestracities / anubis