profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/joshfriend/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Josh Friend joshfriend @MichiganLabs Grand Rapids Michigan

jacebrowning/memegen 737

The free and open source API to generate memes.

jacebrowning/template-python 507

A template for new Python libraries.

citizenlabsgr/elections-api 7

API for voter registration status and sample ballots in Michigan.

jacebrowning/dropthebeat 6

Music sharing using Dropbox.

joshfriend/bunnypedia 4

A companion guide to the card game Killer Bunnies

joshfriend/arm-project-template 1

Bare metal setup for ARM projects. Includes a makefile, linker scripts, and startup files

joshfriend/atlas 1

Webhook bot to integrate Atlassian products such as JIRA with Slack.

pull request commentpyenv/pyenv

GitHub actions tests

I didn't disable it, but it's probably for the best given the Travis CI security incident, although I don't know how to revoke the github API key or whatever travis is using to create releasees for tags

native-api

comment created time in 4 days

pull request commentpyenv/pyenv

GitHub actions tests

Any reason you kept the Travis CI config around still?

native-api

comment created time in 5 days

issue openedhashicorp/terraform-provider-aws

Not possible to import `aws_iot_policy` where policy name contains underscore characters

<!--- Please note the following potential times when an issue might be in Terraform core:

If you are running into one of these scenarios, we recommend opening an issue in the Terraform core repository instead. --->

<!--- Please keep this note for the community --->

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

<!--- Thank you for keeping this note for the community --->

Terraform CLI and Terraform AWS Provider Version

Terraform v1.0.3
on darwin_amd64
+ provider registry.terraform.io/hashicorp/aws v3.34.0

Affected Resource(s)

<!--- Please list the affected resources and data sources. --->

  • aws_iot_policy

Terraform Configuration Files

resource "aws_iot_policy" "example" {
  name = "example_name"
  policy = jsonencode({ ... })
}

Debug Output

Error: error reading IoT Policy (arn:aws:iot:<region>:<account>:policy/example_policy): InvalidRequestException: 1 validation error detected: Value 'arn:aws:iot:<region>:<account>:policy/example_policy' at 'policyName' failed to satisfy constraint: Member must satisfy regular expression pattern: [\w+=,.@-]+

Expected Behavior

Policy should be imported

Actual Behavior

Policy failed to import due to current name matching a regex somewhere

Steps to Reproduce

Run terraform import aws_iot_policy.example arn:aws:iot:<region>:<account>:policy/example_name

created time in 18 days

push eventMichiganLabs/aws-elastic-beanstalk-cli

Mingran Peng

commit sha eaff5e536bc77a26387b93535a3d5d62326b69c8

Change IAM document for China region

view details

Mingran Peng

commit sha 90b9dd20f1506818380da533736e91319bf6e1cf

Update CHANGES.rst and increment version to 3.20.1 cr: https://code.amazon.com/reviews/CR-53644713

view details

Mingran Peng

commit sha b27b68012501ea4982783827052e9609932b65af

Modifed jenkin test scripts and update pip version

view details

Mingran Peng

commit sha 90bac5c1b209ded8e32d1b80dccb9e6f9edcf7f9

Update pip version

view details

Mingran Peng

commit sha 119cbca31c11b3662da6de7324d9f4391f5106e3

Update botocore requirement to comply with aws cli

view details

Mingran Peng

commit sha fb1c5d3b7531ebd6796fe536785a0a7392b22205

Update CHANGES.rst and increment version to 3.20.1

view details

Josh Friend

commit sha f3ffc155fc3e5cb65d565e40da1422bf493764b5

Don't require needlessly specific versions of six

view details

push time in a month

push eventMichiganLabs/aws-elastic-beanstalk-cli

Mingran Peng

commit sha eaff5e536bc77a26387b93535a3d5d62326b69c8

Change IAM document for China region

view details

Mingran Peng

commit sha 90b9dd20f1506818380da533736e91319bf6e1cf

Update CHANGES.rst and increment version to 3.20.1 cr: https://code.amazon.com/reviews/CR-53644713

view details

Mingran Peng

commit sha b27b68012501ea4982783827052e9609932b65af

Modifed jenkin test scripts and update pip version

view details

Mingran Peng

commit sha 90bac5c1b209ded8e32d1b80dccb9e6f9edcf7f9

Update pip version

view details

Mingran Peng

commit sha 119cbca31c11b3662da6de7324d9f4391f5106e3

Update botocore requirement to comply with aws cli

view details

Mingran Peng

commit sha fb1c5d3b7531ebd6796fe536785a0a7392b22205

Update CHANGES.rst and increment version to 3.20.1

view details

push time in a month

push eventMichiganLabs/ci-images

Josh Friend

commit sha 18f2ed7b833f831b74a9308bf547d5d6b00d6428

Add zip to python image

view details

push time in a month

issue commenteclipse/paho.mqtt.python

Loosing qos 2 messages on reconnect after process kill

In the "Known Limitations" section of the docs it says this:

When clean_session is False, the session is only stored in memory not persisted. This means that when client is restarted (not just reconnected, the object is recreated usually because the program was restarted) the session is lost. This result in possible message lost.

Since your python process died, so did all of the pending qos2 messages not yet ack'd by the broker

erik-neumann

comment created time in a month

issue commenthashicorp/terraform-provider-aws

aws_db_proxy subnet_ids

I was having these exact same issues, so I tried creating the RDS proxy in the web UI. I am 100% sure that all 6 of my subnets were listed when I clicked create, but afterwords, us-east-1e was missing. I tried this THREE TIMES with the same results, am I going insane? Does AWS have a bug? Maybe this isn't terraform's fault?

tburow

comment created time in 2 months

issue commentnedbat/coveragepy

pytest and multiprocessing: CoverageException: Can't combine line data with arc dat

One simple solution is to move your coverage.py settings into a .coveragerc file. If you do that, things work.

My project uses a .coveragerc file and coverage reporting still fails with this error what seems like 1 in 3 runs.

nedbat

comment created time in 2 months

PR closed pyenv/pyenv

Update install instructions for shell variables
  • modified commands for bash, zsh, fish shell installation instructions
+6 -6

1 comment

1 changed file

tonywang10101

pr closed time in 2 months

pull request commentpyenv/pyenv

Update install instructions for shell variables

Hey, thanks so much for this contribution and trying to make the install docs better!

$PYENV_ROOT/bin is actually the only thing users need to add to their $PATH to set up pyenv. The bin directory is actually where the pyenv command itself lives, so you need that in the PATH to start. Calling pyenv init --path then emits a directive that adds the shims path to the PATH, e.g. export PATH="/Users/josh/.pyenv/shims:${PATH}".

tonywang10101

comment created time in 2 months

PR opened aws/aws-elastic-beanstalk-cli

Don't require needlessly specific versions of six

Issue #, if available:

Basically a rehash of #38 since the problem was not actually fixed. It is not possible to install awsebcli alongside aws-sam-cli because they both pin the minor version of six to different things. Pipenv/poetry do not allow this and fail with some kind of error like "version solving failed.":

  SolverProblemError

      Because no versions of aws-sam-cli match >1.27.2,<2.0.0
   and aws-sam-cli (1.27.2) depends on aws-sam-translator (1.38.0), aws-sam-cli (>=1.27.2,<2.0.0) requires aws-sam-translator (1.38.0).
  (1) So, because aws-sam-translator (1.38.0) depends on six (>=1.15,<2.0), aws-sam-cli (>=1.27.2,<2.0.0) requires six (>=1.15,<2.0).

      Because awsebcli (3.19.4) depends on six (>=1.11.0,<1.15.0)
   and no versions of awsebcli match >3.19.4,<3.20.0 || >3.20.0,<4.0.0, awsebcli (>=3.19.4,<3.20.0 || >3.20.0,<4.0.0) requires six (>=1.11.0,<1.15.0).
      And because awsebcli (3.20.0) depends on six (>=1.11.0,<1.15.0), awsebcli (>=3.19.4,<4.0.0) requires six (>=1.11.0,<1.15.0).
      And because aws-sam-cli (>=1.27.2,<2.0.0) requires six (>=1.15,<2.0) (1), aws-sam-cli (>=1.27.2,<2.0.0) is incompatible with awsebcli (>=3.19.4,<4.0.0)
      So, because cirrus depends on both awsebcli (^3.19.4) and aws-sam-cli (^1.27.2), version solving failed.

Description of changes:

There's really no reason to fix the minor version of six, If a user needs something more specific, they can pin the version themselves, otherwise it should make no difference until the major version changes.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

+1 -1

0 comment

1 changed file

pr created time in 2 months

create barnchMichiganLabs/aws-elastic-beanstalk-cli

branch : six-version-fix

created branch time in 2 months

issue openedhashicorp/terraform-provider-aws

Lambda event source mapping waits for 5 minute creation retry timeout before surfacing permissions error

<!--- Please note the following potential times when an issue might be in Terraform core:

If you are running into one of these scenarios, we recommend opening an issue in the Terraform core repository instead. --->

<!--- Please keep this note for the community --->

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

<!--- Thank you for keeping this note for the community --->

Terraform CLI and Terraform AWS Provider Version

  • Terraform version v1.0.3
  • AWS provider version v3.34.0

Affected Resource(s)

  • aws_lambda_event_source_mapping

Terraform Configuration Files

resource "aws_lambda_event_source_mapping" "example" {
  event_source_arn = aws_sqs_queue.example.arn
  function_name    = aws_lambda_function.example.arn
}

Expected Behavior

I should receive immediate feedback as to whether the lambda function role has the permissions required to be able to attach the trigger. Creating a trigger through the web interface gives an immediate error message if the lambda role lacks sufficient permissions to attach the trigger.

Actual Behavior

Terraform waited 5 minutes for the aws_lambda_event_source_mapping to be created, then timed out and failed with an error message that The provided execution role does not have permissions to call GetQueueAttributes on SQS. I can see in the debug logs that for each request this error is returned, however, TF waits the WHOLE 5 minutes to surface this error to the user.

2021-07-27T16:07:44.127-0400 [INFO]  provider.terraform-provider-aws_v3.34.0_x5: 2021/07/27 16:07:44 [DEBUG] [aws-sdk-go] {"Type":"User","message":"The provided execution role does not have permissions to call GetQueueAttributes on SQS"}: timestamp=2021-07-27T16:07:44.127-0400
2021-07-27T16:07:44.127-0400 [INFO]  provider.terraform-provider-aws_v3.34.0_x5: 2021/07/27 16:07:44 [DEBUG] [aws-sdk-go] DEBUG: Validate Response lambda/CreateEventSourceMapping failed, attempt 0/25, error InvalidParameterValueException: The provided execution role does not have permissions to call GetQueueAttributes on SQS

Steps to Reproduce

  1. terraform apply

created time in 2 months

issue closedflask-restful/flask-restful

Memory issue or I am dumb

I was looking into flask-restful and blueprints. So I wanted json output as in flask-restful documentation;

from flask import Flask, Blueprint
from flask_restful import Api

app = Flask(__name__)
api_bp = Blueprint("api", __name__)
api = Api(api_bp)

@api.representation("application/json")
def out_json(data, code, headers=None):
    resp = api.make_response(json.dumps(data), code)
    resp.headers.extend(headers or {})
    return resp

@api.blueprint.route("/")
def home():
    message = "hello world"
    return out_json({"message":message}, 200)

app.register_blueprint(api_bp)

if __name__ == "__main__":
   app.run(debug=True)

when you run the above code and make a request to the server ie curl -sk "http://127.0.0.1:5000/" it consumes all the memory and you will not get the response from the server. I also observed that insane memory consumption continues even after you have cancelled the request. The server does not acknowledge that it has received the request however.

closed time in 2 months

collinsmarra

issue commentflask-restful/flask-restful

Memory issue or I am dumb

You did recursion in an infinite loop. api.make_response() calls the function that you registered with @api.representation, which is out_json(). out_json() calls api.make_response() and you should see now why this is a problem!

Either stick with the default json response formatter, or follow the docs on how to make one properly.

collinsmarra

comment created time in 2 months

pull request commentpyenv/pyenv

Remove PATH warning

The warning has served its purpose by now.

I can tell you it has not 😆

native-api

comment created time in 2 months

issue commentmicrosoft/appcenter

Distribute multiple app-ids from same AppCenter app

can this be repopened? just because nobody has commented doesn't mean we aren't still interested

kimbirkelund

comment created time in 2 months

issue commentmicrosoft/appcenter

Support logging of caught exceptions

(obligatory "bump" comment to keep this thread from being killed by the bot)

joshfriend

comment created time in 3 months

PR closed pyenv/pyenv

Fix install path issue for shims in readme

This is not necessarily a typo in the docs, it needs reviewing by a maintainer to ensure my problem is not specific to my installation

I think there is a mistake in the doc. Not sure why but the install path wasn't correct in my machine (macOS, installed with home-brew). This line is repeated for every possible install platform and it might be needed to update them as well.

before:
            echo 'export PATH="$PYENV_ROOT/bin:$PATH"' >> ~/.zprofile
after:
            echo 'export PATH="$PYENV_ROOT/shims:$PATH"' >> ~/.zprofile
+1 -1

1 comment

1 changed file

belgiancoder

pr closed time in 3 months

pull request commentpyenv/pyenv

Fix install path issue for shims in readme

/bin is correct, does your shell run pyenv init to set things up as described in the README?

belgiancoder

comment created time in 3 months

push eventflask-restful/flask-restful

Aeneas Jaißle

commit sha a2cf3a33992297110fd73742c3fbfbd7f819e5fb

add 0.3.8 release date in CHANGES.md (#921) * add 0.3.8 release date in CHANGES.md * Update CHANGES.md

view details

push time in 3 months

issue closedflask-restful/flask-restful

New GitHub release?

Hi, It's been 6 years without any release. It'd be great if there can be a new upstream release now. I need the version thingy for a project. Thanks!

closed time in 3 months

nileshpatra

issue commentflask-restful/flask-restful

New GitHub release?

the git tags show up on the releases list, idk what everyone is talking about here https://github.com/flask-restful/flask-restful/releases

nileshpatra

comment created time in 3 months