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

wamp_session: set_exception on the correct future #229

Merged
merged 2 commits into from
Jan 27, 2022

Conversation

jgriffiths
Copy link
Contributor

Currently the start future is incorrectly signaled, probably cut'n'paste from the start method above.

@oberstet
Copy link
Contributor

ah, right! thanks for contributing, I've enabled CI to run (only required on your 1st contribution) .. it runs into CI unfort. (not related to this PR):

Error: Unable to process command '::set-env name=CC::gcc-10' successfully.
Error: The `set-env` command is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting the `ACTIONS_ALLOW_UNSECURE_COMMANDS` environment variable to `true`. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/
Error: Unable to process command '::set-env name=CXX::g++-10' successfully.
Error: The `set-env` command is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting the `ACTIONS_ALLOW_UNSECURE_COMMANDS` environment variable to `true`. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

@oberstet
Copy link
Contributor

so essentially, we need to change

if [ "${{ matrix.compiler }}" = "gcc" ]; then

according to

https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-environment-variable, as of

Starting today runner version 2.273.5 will begin to warn you if you use the add-path or set-env commands. We are monitoring telemetry for the usage of these commands and plan to fully disable them in the future.

https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

@jgriffiths
Copy link
Contributor Author

Hi @oberstet I've pushed an attempted fix for the CI, I will iterate should it prove insufficient, thanks.

@oberstet
Copy link
Contributor

well, the environment vars are indeed needed;) so the syntax in the github job control needs a change:

echo "{environment_variable_name}={value}" >> $GITHUB_ENV

also, in doing so, we need to ensure that the job meta variable matrix.version is properly inserted into the value set for the env var ..

@jgriffiths
Copy link
Contributor Author

The env vars have been set correctly via the env: section, the problem appears to be that using gcc rather than g++ to link a c++executable doesn't include stdlib in the linker flags. As above, I'll iterate to get it working.

@jgriffiths jgriffiths force-pushed the session_wrong_future branch 2 times, most recently from 7b228ce to 95529ad Compare January 27, 2022 00:43
@jgriffiths
Copy link
Contributor Author

OK, the non-conan builds are passing. conan seems to be broken by conan-io/conan#8788

I'm out of time for fixing the other CI issues as I'm not familiar with conan and don't use windows.

@oberstet
Copy link
Contributor

oberstet commented Jan 27, 2022

alright, I have found this https://blog.conan.io/2021/09/03/conancenter-declare-bintray-obsolete.html

let me see if I can add that to your PR and try using

https://conan.bintray.com [OLD] => https://center.conan.io [NEW]

@oberstet oberstet merged commit a9bc73a into crossbario:master Jan 27, 2022
@oberstet
Copy link
Contributor

that has worked #230

thanks for contributing!

@jgriffiths
Copy link
Contributor Author

Thanks!

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.

2 participants