{"action":"created","issue":{"url":"https://api.github.com/repos/tapple/nsize-web/issues/435","repository_url":"https://api.github.com/repos/tapple/nsize-web","labels_url":"https://api.github.com/repos/tapple/nsize-web/issues/435/labels{/name}","comments_url":"https://api.github.com/repos/tapple/nsize-web/issues/435/comments","events_url":"https://api.github.com/repos/tapple/nsize-web/issues/435/events","html_url":"https://github.com/tapple/nsize-web/pull/435","id":379996391,"node_id":"MDExOlB1bGxSZXF1ZXN0MjMwMzAyNTkw","number":435,"title":"Update newrelic to 4.6.0.106","user":{"login":"pyup-bot","id":16239342,"node_id":"MDQ6VXNlcjE2MjM5MzQy","avatar_url":"https://avatars0.githubusercontent.com/u/16239342?v=4","gravatar_id":"","url":"https://api.github.com/users/pyup-bot","html_url":"https://github.com/pyup-bot","followers_url":"https://api.github.com/users/pyup-bot/followers","following_url":"https://api.github.com/users/pyup-bot/following{/other_user}","gists_url":"https://api.github.com/users/pyup-bot/gists{/gist_id}","starred_url":"https://api.github.com/users/pyup-bot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pyup-bot/subscriptions","organizations_url":"https://api.github.com/users/pyup-bot/orgs","repos_url":"https://api.github.com/users/pyup-bot/repos","events_url":"https://api.github.com/users/pyup-bot/events{/privacy}","received_events_url":"https://api.github.com/users/pyup-bot/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-11-12T23:39:43Z","updated_at":"2018-12-03T22:39:34Z","closed_at":"2018-12-03T22:39:34Z","author_association":"COLLABORATOR","pull_request":{"url":"https://api.github.com/repos/tapple/nsize-web/pulls/435","html_url":"https://github.com/tapple/nsize-web/pull/435","diff_url":"https://github.com/tapple/nsize-web/pull/435.diff","patch_url":"https://github.com/tapple/nsize-web/pull/435.patch"},"body":"\nThis PR updates [newrelic](https://pypi.org/project/newrelic) from **2.100.0.84** to **4.6.0.106**.\n\n\n\n<details>\n  <summary>Changelog</summary>\n  \n  \n   ### 4.6.0.106\n   ```\n   This release of the Python agent includes changes to the agent to enable monitoring of Lambda functions, improves the built-in Sanic instrumentation, and includes various bug fixes.\n\nThe agent can be installed using easy_install/pip/distribute via the Python Package Index or can be downloaded directly from the New Relic download site.\n\nFeatures\n\n\nMonitoring of Lambda functions\n\nThis release includes changes to the agent to enable monitoring of Lambda functions. If you are interested in learning more or previewing New Relic Lambda monitoring please email lambda_previewnewrelic.com.\nImprove naming of Sanic HTTPMethodView view handlers\n\nSanic views that were defined using the HTTPMethodView class were previously all named HTTPMethodView.as_view..view regardless of the actual class in use. The agent will now name transactions after the actual view handler class.\n\n\nBug Fixes\n\n\nFix ignored error reporting in CherryPy instrumention\n\nWhen missing query parameters, unexpected query parameters, unexpected positional arguments, or duplicate arguments were present in the CherryPy framework, a TypeError exception was recorded even when an ignored response status code (such as a 404) was generated. An error is no longer recorded when it results in the generation of an ignored status code.\nExcluding request.uri from transaction trace attributes hides it in the UI\n\nWhen request.uri is added to either attributes.exclude or transaction_tracer.attributes.exclude, the value will now no longer appear in the APM UI for transaction traces.\nAbility to disable sending request.uri as part of error traces\n\nError traces will now respect excluding request.uri when added to the attributes.exclude list in the newrelic.ini configuration file.\nFix tracing of functions returning generators\n\nWhen tracing generators whose parent traces have ended an error was seen in the logs &quot;Transaction ended but current_node is not Sentinel.&quot; This has now been fixed.\n   ```\n   \n  \n  \n   ### 4.4.1.104\n   ```\n   This release of the Python agent contains bug fixes.\n\nThe agent can be installed using easy_install/pip/distribute via the Python Package Index or can be downloaded directly from the New Relic download site.\n\nBug Fixes\n\n\nThe creation of sampled events sometimes raised an exception in Python 3\n\nWhen more events (Transaction, Transaction Error, Custom, or Span) were created than allowed per harvest period in Python 3, sometimes a TypeError: &#39;&lt;&#39; not supported between instances of &#39;dict&#39; and &#39;dict&#39; was raised. This issue has now been fixed.\n   ```\n   \n  \n  \n   ### 4.4.0.103\n   ```\n   This release of the Python agent introduces instrumentation for Sanic, and contains bug fixes.\n\nThe agent can be installed using easy_install/pip/distribute via the Python Package Index or can be downloaded directly from the New Relic download site.\n\nFeatures\n\n\nAdd instrumentation for Sanic framework\n\nData is now automatically collected for applications using the Sanic framework. Data for Sanic applications will appear in both APM and Insights. Additionally, cross application tracing and distributed tracing is supported for incoming requests for Sanic applications. In addition to service maps, Sanic applications will now show the calling application in transaction traces. See the instrumented packages page for more details.\n\n\nBug Fixes\n\n\nExplain plans were not generated when using psycopg2 named cursors\n\nWhen using named cursors in psycopg2, the agent attempted to generate an explain plan using the same named cursor. This resulted in a syntax error when the query was issued to the database. When using the default connection and cursor factories, the agent will now execute the explain query using only unnamed cursors.\nConvert bytes-like SQL statements to strings before obfuscating\n\nIf a bytes-like object is used instead of a string when making a SQL call, a traceback was seen in the logs with TypeError: cannot use a string pattern on a bytes-like object. This issue has now been fixed.\nSave settings to MessageTrace objects\n\nIf an external call using an instrumented http external library (for example requests) was used within a MessageTrace, a traceback was seen in the logs with AttributeError: &#39;MessageTrace&#39; object has no attribute &#39;settings&#39;. This issue has now been fixed.\n   ```\n   \n  \n  \n   ### 4.2.0.100\n   ```\n   This release of the Python agent introduces distributed tracing, adds improvement to our Pyramid instrumentation, adds support for custom CA bundles, and contains bug fixes.\n\nThe agent can be installed using easy_install/pip/distribute via the Python Package Index or can be downloaded directly from the New Relic download site.\n\nFeatures\n\n\nDistributed tracing support\n\nDistributed tracing lets you see the path that a request takes as it travels through your distributed system. By showing the distributed activity through a unified view, you can troubleshoot and understand a complex system better than ever before.\n\nDistributed tracing is available with an APM Pro or equivalent subscription. To see a complete distributed trace, you need to enable the feature on a set of neighboring services. Enabling distributed tracing changes the behavior of some New Relic features, so carefully consult the transition guide before you enable this feature.\n\nTo enable distributed tracing, add distributed_tracing.enabled = true to your newrelic.ini file or use the environment variable NEW_RELIC_DISTRIBUTED_TRACING_ENABLED=true.\nAdd support for tracing Pyramid tweens\n\nPyramid tweens are now automatically timed and added to the transaction detail view. The time spent in a Pyramid tween will be displayed in the transaction breakdown table and in the trace details of a transaction trace.\nProvide configuration option for custom CA bundle\n\nCustomers can now use the ca_bundle_path configuration option or set the NEW_RELIC_CA_BUNDLE_PATH environment variable to set the path to a local CA bundle. This CA bundle will be used to validate the SSL certificate presented by New Relic&#39;s data collection service.\n\n\nBug Fixes\n\n\nCustom Insights event data attached to transactions in excess of 100 events were omitted\n\nThe agent may have failed to send custom event data (record_custom_event) to insights when recorded as part of a Transaction containing over 100 custom events. This issue has now been corrected.\n   ```\n   \n  \n  \n   ### 4.0.0.99\n   ```\n   This release of the Python agent removes previously deprecated APIs, and removes support for Python 2.6 and Python 3.3.\n\nThe agent can be installed using easy_install/pip/distribute via the Python Package Index or can be downloaded directly from the New Relic download site.\n\nDeprecations\n\n\nRemoved previously deprecated APIs\n\nThe following APIs have been removed:\n\n\nTransaction.add_user_attribute (use Transaction.add_custom_parameter)\nTransaction.add_user_attributes (use Transaction.add_custom_parameters)\nwrap_callable (use FunctionWrapper)\n\nRemoved support for Python 2.6 and Python 3.3\n\nPython 2.6 and Python 3.3 are no longer supported. Please consider upgrading your application to a supported version of Python in order to continue to receive updates to the Python Agent.\n   ```\n   \n  \n  \n   ### 3.4.0.95\n   ```\n   This release of the Python agent adds support for Python 3.7 and contains various bug fixes.\n\nThe agent can be installed using easy_install/pip/distribute via the Python Package Index or can be downloaded directly from the New Relic download site.\n\nNew Features\n\n\nSupport Python 3.7\n\nThe New Relic Python Agent now supports Python 3.7.\n\n\nBug Fixes\n\n\nAgent raises a KeyError: &#39;NEW_RELIC_ADMIN_COMMAND&#39; exception causing a crash\n\nUnder certain conditions, using the newrelic-admin wrapper script could cause\nan application to crash shortly after startup with a KeyError exception. The\ncause of the crash has been addressed.\nAgent raises an AttributeError on Python 3 when using WSGI overrides with multiple app names\n\nWhen using WSGI environ overrides to specify multiple app names as described in the docs https://docs.newrelic.com/docs/agents/manage-apm-agents/app-naming/use-m... the agent will raise an AttributeError. This error has been corrected.\nAgent raises an AttributeError exception under rare conditions when halting a trace\n\nUnder certain rare conditions, the agent might raise an exception when trying\nto trace an external call in a transaction that has been forcibly halted.\nThe cause of the exception has been addressed.\nAgent raises a RuntimeError exception under particular conditions when using the Tornado r3 instrumentation\n\nWhen attempting to yield many times from a wrapped tornado.gen.coroutine\nwhen using Tornado&#39;s r3 instrumentation, a RuntimeError due to hitting\nthe maximum recursion limit can occur. The cause of this exception has\nbeen patched.\n   ```\n   \n  \n  \n   ### 3.2.2.94\n   ```\n   This release of the Python agent contains various bug fixes.\n\nThe agent can be installed using easy_install/pip/distribute via the Python Package Index or can be downloaded directly from the New Relic download site.\n\nBug Fixes\n\n\nImproved handling of celery max-tasks-per-child\n\nData recorded by the Python Agent may not have been reported when celery was operated with the max-tasks-per-child setting. All data is now reported independent of the max tasks per child setting.\nImprove support for PyMongo v3.x\n\nPyMongo v3 added many new methods on the pymongo.Collection object that did not exist in v2. These methods have now been instrumented. Calls to these methods will now appear in APM.\nScheduling tasks that run after a transaction ends causes an error\n\nCoroutines scheduled to execute after a transaction ends using create_task or ensure_future may have caused the runtime instrumentation error and subsequent crash:\n\nThe transaction already completed meaning a child called complete trace after the trace had been finalized.\n\nCoroutines that execute beyond the end of a transaction will no longer cause an error.\n   ```\n   \n  \n  \n   ### 3.2.1.93\n   ```\n   This release of the Python agent contains various bug fixes.\n\nThe agent can be installed using easy_install/pip/distribute via the Python Package Index or can be downloaded directly from the New Relic download site.\n\nBug Fixes\n\n\nDo not run explain plans for psycopg2 connections using the async_ kwarg\n\nAs &quot;async&quot; is now a keyword in Python 3.7, psycopg2 now allows &quot;async_&quot; as an alias for its &quot;async&quot; kwarg for psycopg2.connect as of psycopg2 v2.7.4. Previously, explain plans were attempted for these connections and a traceback would be seen in the logs. This has now been fixed.\nFix traceback when using callbacks as partials in pika consumers\n\nWhen passing a callback that is a functools partial to pika channel consumers, a traceback occurred in some instances. This issue has now been fixed.\ncx_Oracle database calls that use SessionPool objects were not recorded\n\nWhen using the cx_Oracle SessionPool interace, database transactions made through the acquired pool connection may not have been reported. Database transactions that using connections generated by SessionPool are now reported as expected.\nSQL targets for call statements may contain a period\n\nFor a SQL command like CALL foo.bar(:baz), APM would show metrics under the target name foo instead of the full name foo.bar. This has been fixed.\n   ```\n   \n  \n  \n   ### 3.2.0.91\n   ```\n   This release of the Python agent adds the request.uri attribute on transaction events in insights, adds built-in cheroot instrumentation, adds support for recording flask-restful/flask-restplus exceptions, and contains bug fixes.\n\nThe agent can be installed using easy_install/pip/distribute via the Python Package Index or can be downloaded directly from the New Relic download site.\n\nImproved Features\n\n\nAdd request.uri attribute to transaction and error events\n\nThe Python agent will now report request.uri as an attribute on transaction events and error events. To disable this feature, add request.uri to the attributes.exclude list in the newrelic.ini configuration file.\nRecord Flask RESTful and Flask RestPlus exceptions\n\nSince Flask RESTful and Flask RestPlus handle all errors that are raised in their handlers, these errors were not being captured by the normal Flask instrumentation in the Python agent. Exception handling has now been added for these two components.\nAdd instrumentation hooks for the Cheroot WSGI server\n\nAny customers using Cheroot with an unsupported application framework will now see data reported in New Relic APM.\n\n\nBug Fixes\n\n\nFix CherryPy ignore by status code for exceptions using reason phrases\n\nCherryPy accepts string values for HTTPError status (reason phrases). When creating HTTPError exceptions in this way, responses were not properly ignored by status code. Responses generated by HTTPError exceptions using reason phrases are now properly ignored.\nUsing send_file with Flask Compress middleware may have caused an application crash\n\nWhen using browser monitoring auto instrumentation on an application using Flask Compress, the use of the Flask send_file helper to send html files resulted in an application crash. This issue has now been resolved.\nFix incorrect parenting for traces of coroutines scheduled with asyncio gather/ensure_future\n\nCoroutines scheduled with asyncio gather/ensure_future may have been reported as being a child of the wrong function. This issue has now been corrected.\n   ```\n   \n  \n  \n   ### 3.0.0.89\n   ```\n   This release of the Python agent removes previously deprecated APIs, makes SSL communication with New Relic mandatory, and updates support for aiohttp middleware.\n\nThe agent can be installed using easy_install/pip/distribute via the Python Package Index or can be downloaded directly from the New Relic download site.\n\nDeprecations\n\n\nRemoved previously deprecated APIs\n\nThe following APIs have been removed:\n\n\ntransaction (use current_transaction)\nname_transaction (use set_transaction_name)\nApplication.record_metric (use Application.record_custom_metric)\nApplication.record_metrics (use Application.record_custom_metrics)\nTransaction.notice_error (use Transaction.record_exception)\nTransaction.record_metric (use Transaction.record_custom_metric)\nTransaction.name_transaction (use Transaction.set_transaction_name)\n\nDeprecate Transaction.add_user_attribute\n\nTransaction.add_user_attribute has been deprecated in favor of Transaction.add_custom_parameter. Transaction.add_user_attribute will be removed in a future release.\nDeprecate Transaction.add_user_attributes\n\nTransaction.add_user_attributes has been deprecated in favor of Transaction.add_custom_parameters. Transaction.add_user_attributes will be removed in a future release.\nDeprecate wrap_callable\n\nwrap_callable has been deprecated in favor of FunctionWrapper. wrap_callable will be removed in a future release.\nRemove data-source admin command\n\nThe platform API (used by newrelic-admin data-source) has been removed. Please use data sources in place of the platform API.\n\n\nSSL\n\nSSL connections to New Relic are now mandatory\n\nPrior to this version, using an SSL connection to New Relic was the default behavior. SSL connections are now enforced (not overrideable).\n\nAIOHTTP Updates\n\n\nAdd automatic tracing of AIOHTTP 3 middleware\n\nIn addition to the old-style middleware previously supported, the AIOHTTP 3 style middleware is now automatically traced as part of the AIOHTTP instrumentation package.\n   ```\n   \n  \n  \n   ### 2.106.1.88\n   ```\n   This release of the Python agent includes a fix for security bulletin nr18-07.\n\nThe agent can be installed using easy_install/pip/distribute via the Python Package Index or can be downloaded directly from the New Relic download site.\n   ```\n   \n  \n  \n   ### 2.106.0.87\n   ```\n   This release of the Python agent adds support for AIOHTTP version 3.\n\nThe agent can be installed using easy_install/pip/distribute via the Python Package Index or can be downloaded directly from the New Relic download site.\n\nImproved AIOHTTP Support\n\n\nSupport for AIOHTTP 3\n\nAIOHTTP major version 3 is now supported by the New Relic Python agent.\n   ```\n   \n  \n  \n   ### 2.104.0.86\n   ```\n   This release of the Python agent adds a deprecation warning for customers that disable SSL, and adds bugfixes for supported async frameworks that use asyncio.\n\nThe agent can be installed using easy_install/pip/distribute via the Python Package Index or can be downloaded directly from the New Relic download site.\n\nMandatory SSL\n\n\nDisabling SSL connections to New Relic has been deprecated\n\nSSL connections are enabled by default. In a future release, the option to\ndisable SSL will be removed.\n\n\nBug Fixes\n\n\nUsing asyncio.gather or asyncio.ensure_future now tracks transaction context\n\nPrior to this release, using asyncio.gather or asyncio.ensure_future may\nresult in certain traces (such as external calls) not being reported in the\ntransaction. Traces scheduled with asyncio.gather or asyncio.ensure_future\nfrom within the context of a transaction should now be properly attributed to\nthe transaction.\n   ```\n   \n  \n  \n   ### 2.102.0.85\n   ```\n   This release of the Python agent contains improvements to the time tracing API as well as bug fixes.\n\nThe agent can be installed using easy_install/pip/distribute via the Python Package Index or can be downloaded directly from the New Relic download site.\n\nTime Trace API Improvements\n\n\nTime trace APIs (such as function_trace) can now be used with coroutines\n\nThe following decorator APIs can now be used with native coroutines and generators:\n\n\nfunction_trace\ndatabase_trace\ndatastore_trace\nexternal_trace\nmessage_trace\nmemcache_trace\n\n\nExample:\n\nfunction_trace(name=&#39;my_coroutine&#39;)\nasync def my_coroutine():\n  await asyncio.sleep(0.1)\n\n\nBug Fixes\n\n\ngRPC instrumentation used on Python 2.x can cause a memory leak\n\nWhen using gRPC on Python 2, gRPC futures would not be garbage collected\nresulting in a memory leak. gRPC futures will now be garbage collected.\nInstrumentation for Dropbox v8.0 and newer caused error log messages\n\nDropbox client version 8.0 or higher raised instrumentation errors. These\nerrors did not prevent metrics on Dropbox from being sent. These errors have\nbeen removed.\nValues from negated ranges were sometimes added to ignore_status_codes\n\nNegated status codes not found in the current ignore_status_codes were \nadded if they were part of a range of values. This issue has been addressed.\n   ```\n   \n  \n</details>\n\n\n \n\n<details>\n  <summary>Links</summary>\n  \n  - PyPI: https://pypi.org/project/newrelic\n  - Changelog: https://pyup.io/changelogs/newrelic/\n  - Homepage: http://newrelic.com/docs/python/new-relic-for-python\n</details>\n\n"},"comment":{"url":"https://api.github.com/repos/tapple/nsize-web/issues/comments/443898006","html_url":"https://github.com/tapple/nsize-web/pull/435#issuecomment-443898006","issue_url":"https://api.github.com/repos/tapple/nsize-web/issues/435","id":443898006,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0Mzg5ODAwNg==","user":{"login":"pyup-bot","id":16239342,"node_id":"MDQ6VXNlcjE2MjM5MzQy","avatar_url":"https://avatars0.githubusercontent.com/u/16239342?v=4","gravatar_id":"","url":"https://api.github.com/users/pyup-bot","html_url":"https://github.com/pyup-bot","followers_url":"https://api.github.com/users/pyup-bot/followers","following_url":"https://api.github.com/users/pyup-bot/following{/other_user}","gists_url":"https://api.github.com/users/pyup-bot/gists{/gist_id}","starred_url":"https://api.github.com/users/pyup-bot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pyup-bot/subscriptions","organizations_url":"https://api.github.com/users/pyup-bot/orgs","repos_url":"https://api.github.com/users/pyup-bot/repos","events_url":"https://api.github.com/users/pyup-bot/events{/privacy}","received_events_url":"https://api.github.com/users/pyup-bot/received_events","type":"User","site_admin":false},"created_at":"2018-12-03T22:39:33Z","updated_at":"2018-12-03T22:39:33Z","author_association":"COLLABORATOR","body":"Closing this in favor of #460"}}
{"actor":{"display_login":"pyup-bot"}}