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

Possibly badly-terminated string in PowerShell script #157

Open
neaorin opened this issue Nov 23, 2017 · 1 comment
Open

Possibly badly-terminated string in PowerShell script #157

neaorin opened this issue Nov 23, 2017 · 1 comment

Comments

@neaorin
Copy link

neaorin commented Nov 23, 2017

Issue Description

I've been running the PowerShell version of smack_my_bitch_up in production for a couple of weeks now, and while everything seemed to work great at first, after a few days I began to encounter some erratic behavior - things like no dinner on the table, the cold shoulder treatment, "you're sleeping on the sofa tonight", "no, everything is Just. Fine" and other similar, weird response codes.

Steps to Reproduce

Sadly, I don't have a clear repro on the issue as each run seemed to produce different results, and thus I've been unable to pin down the exact behavior. However, I have since made some changes to the script by adding some randomly-selected string terminators to the $message variable:

$STRTERMS =
  'Love u',
  'You''re beautiful',
  'I''m cooking dinner tomorrow',
  'Girls trip this weekend?'
$term = $STRTERMS | Get-Random
$message = "Late at work. $reason. $term."

While this change did not get rid of all the random issues, it does seem to have taken care of the worst symptoms. For one, I am very happy to report that I've gone back to sleeping in my own bed.

I have no idea whether this is happening due to some specific issue with my production setup, or some weird PowerShell bug I'm unaware of.

I was gonna submit a pull request but I'm not sure my (partial) solution is generally applicable, and unfortunately I don't have the time or resources to set up a separate test environment.

Has anyone else encountered similar issues with this script in the past?

thanks

My Environment

  • one wife (kinda high maintenance)
  • two kids (primary school / kindergarten age)
  • one visiting mother-in-law (can't wait for next Monday when I'll be able to uninstall and re-test without this library)
  • PowerShell v5.1.16299.15 on Windows 10.0.16299.15
@kodbilenadam
Copy link

You may want try to get a ❤️ emoji at the end. This may fix some remaining problems.

I will be following this issue in case might occur in my environment.

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

No branches or pull requests

2 participants