🇨🇷Costa Rica @kporras07

Hi @kreynen,

I looked into this and the only way I was able to reproduce it was when I tried to add a key with a machine name that already exists.

I kept looking into this and noticed that this doesn't happen exclusively with pantheon_secrets but (I think) with any provider plugin that doesn't input a value. For example I was able to reproduce it with environment provider.

I think this is most likely to be an issue with Key but I haven't had the time to pinpoint the exact issue but with these findings I'm pretty sure this is not a pantheon_secrets thing.

If you have any additional information or steps to reproduce that could help point in the direction of an actual pantheon_secrets bug that would be super helpful.

Thanks!

Hi @srjosh
Thanks! I went ahead and made this in GitHub so that we could run our tests there. 1.0.6 was just released with D11 compatibility

New release will be published soon. Closing this. Thanks everyone!

Thanks! This looks great!

I'll be tagging a new release soon

Hi!

Thanks for reporting this. The fix was included in 1.0.4 as a new option when you create a key to specify that it's base64 encoded so that it gets decoded when getting the value.

Hi!

Just created a PR to fix this: https://github.com/pantheon-systems/pantheon_secrets/pull/17

Will merge and release soon :)

smustgrave → credited kporras07 → .

Hi!

Thanks for reporting. This fix was included in the recent release: https://www.drupal.org/project/pantheon_secrets/releases/1.0.2 →

Thanks for your contributions.

Although I love coding standard; this is only docs files and I don't see a lot of value in following standards in MD files where I prefer readability over standards.

I'm going to close this issue as works as designed.

This is awesome info! Thanks

Hi @bob.hinrichs

Could you please provide steps to reproduce this issue? Also, if you have any special contrib module that should be taken into consideration to reproduce this issue, that would be great.

Thanks!

Thanks! Committed

That's part of how the connection is setup between the different servers in Pantheon. If you keep having issues with your search, for this specific case, I recommend you to contact support so they can get some visibility into your site. If support determines this is actually an issue with the module, they will provide some more info and we will be able to handle it here.

hmmm that error looks like a server issue but I don't think there have been any recent outages on the Solr service. Are you sure this is related to upgrading the module and not to any other config change or something? I would attempt to rollback the module update to confirm that this issue is coming from updating the module

Hi @tripodcreative!

Could you please make sure you open a support ticket so that we can get some eyes on your site?

Please make sure you include as much info as possible. Also, if there is some more info you can include in this space, that may also work.

Thanks!

Thanks for the update. Closing issue.

kporras07 → created an issue.

I agree with @richardbporter on this.

Try

terminus drush [MACHINE-NAME-OF-SITE].[ENV-NAME] -- config:set pantheon_advanced_page_cache.settings --input-format=yaml   "override_list_tags" "false"

and hopefully it will start working as expected.

Hi @Adrianm6254 looking at this more closely, it's not straightforward for us to reproduce this issue but looking at the stack trace, I think we got a fix. Could you please test this PR https://github.com/pantheon-systems/pantheon_advanced_page_cache/pull/49 and let us know if it works?

Also, if you could provide steps to reproduce that would be great? (IIUC, I think a cache operation should happen during the updb so maybe some code that does that or some contrib module would be great pointers here)

Thanks! This was committed and released in 8.1.2