Missing emit in props.coordinates watcher of marker.component.ts

Hey. I've noticed that the update:coordinates emit isn't triggered by the watcher of marker.component.ts.
Simple exemple :
In the following exemple the user coordinates are from a computed, so the coordinates props are dynamically updated.
  <MglMarker
    :coordinates="[user.longitude, user.latitude]"
    @update:coordinates="console.log"
  />

In the lib, I suggest to add the following :
watch(
  () => props.coordinates,
  (v) => {
    marker.value?.setLngLat(v)
    emit("update:coordinates", marker.value?.getLngLat())
  },
  { deep: true },
)

I've dont made a PR because I don't know if you want to fix this yourself, or simply if you want to enhance this behavior in an other way.

I want to listen to the coordinates changes to trigger a flyTo maplibre method when the coordinates are updated.
The @update:coordinates seems to be a good option to avoid to watch the value of coordinates located in my userStore.
<template>
  <MglMarker
    :coordinates="[
      userStore.userLocation.longitude,
      userStore.userLocation.latitude
    ]"
  >
    <template v-slot:marker>
      <div class="user-marker" />
    </template>
  </MglMarker>
</template>

<script setup lang="ts">
  import { MglMarker, useMap } from '@indoorequal/vue-maplibre-gl'
  import { useUserStore } from<EMAIL_ADDRESS>  import { computed, watch } from 'vue'
  import type { FlyToOptions } from 'maplibre-gl'

  const props = withDefaults(defineProps<{ cameraBearing?: number }>(), {
    cameraBearing: 0
  })

  const emit = defineEmits(['bearingNeedsUpdate'])

  const userStore = useUserStore()
  const mapInstance = useMap()

 // I want to avoid this watcher by an event from the marker.
  watch(userStore, updateCamera)

  function updateCamera() {
    emit('bearingNeedsUpdate')
    mapInstance.map?.flyTo({
      center: [
        userStore.userLocation.longitude,
        userStore.userLocation.latitude
      ],
      bearing: userStore.userLocation.heading
    })
  }
</script>

I believe it's cleaner to watch the store to update the center of the map. The source of truth is the store. The related code could also be in an upper component.
Still the documentation should at least be updated to document the current behavior.

I'm agreeing with you. Thanks for your feedback, and thanks to maintain this project, it's really useful for the open source community ! 🔥

I updated the documentation to avoid this confusion in the future.


Enables detection of other kind of BT modules

I wasn't able to find my device with the default filters so I thought this criteria broadening might be worth consideration.

Hi @erkkimon
Unfortunately, the file you're changing sourced from another repository: https://github.com/loginov-rocks/bluetooth-terminal
The change you're suggesting doesn't look to be in line with the purpose of the library. The connected device should be properly configured.


PXP-10038 Custom API calls

Jira Ticket: PXP-10038
New Features

Ability to make custom API calls as part of the access request process

Improvements

Use jsonschema to validate the configuration file

Dependency updates

Add jsonschema and mock dependencies

Awesome work. :applause: I had some questions/suggestions while reviewing though.


chore(develop): release 1.1.3

:robot: I have created a release beep boop
1.1.3 (2023-01-17)
Miscellaneous Chores

release 1.1.3 (2c898e1)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/JonDotsoy/demo-workspace/releases/tag/v1.1.3 :sunflower:


Newbs entering password on "Generate Wallet" when they have a hard wallet

I've seen this referenced by someone, "Don't enter a password at the generate wallet screen if you have a hard wallet!"
Then I had a co-worker do it he was just trying to intuitively figure it out.
I had to kindly tell them "you shouldn't have done that!!!"
Can we make the instructions more Newb friendly please?
Maybe some gray text, "(If you have a Ledger or Trezor, don't generate a new wallet here.)"

will be live in v3.6.4. thanks!


dna reference sequence <unknown id>

@EdGreen21 I see you uploaded a dna file to the website which again ended up with <unknown id> as the description - would you be able to send me this file (or attach here) so I can try to fix this?
Also would it make sense to use the original filename as a fallback if neither of the sequence parsing libraries find an id or description?

Most Snapgene files do not seem to use the  field, so fallback to filename would be ideal.
Attached are a number of files in various versions of snapgene *.dna format, as well as a linear DNA sequence that a user might submit if they only knew part of the sequence or - worst case - screwed up and didn't properly annotate their plasmids. @LArnoldt let's see how this affects the analysis
Example DNA files.zip

nice solution!


Target jmx named port

This is based on top of the currently open Auth #45 and podman builder #46 PRs.
The last two three commits in this branch replace the hardcoded exporter port number 8181 and JMX port number 9091 with named ports.
For the JMX target port of 9091, this is now used as a fallback rather than a hardcoded default. The service_controller still watches for new services to appear and for each new service it checks all of the defined service ports. If a port named "jmx" is found then the service is marked as a compatible target. If no "jmx" port is found but the 9091 port is found then it is also marked as compatible. If neither are found then the service is ignored as a potential target. Then, after the service_controller creates the FlightRecorder resource including this port number, the flightrecorder_controller (watching for new FlightRecorder CRs) reconcile is triggered, which uses this port number for establishing the target connection via ContainerJFR.
This part is still WIP since the default 9091 fallback port number constant is hardcoded in both controllers. I intend to resolve this by adding the port number to the FlightRecorder CRD, so that the service_controller can include the port number in the CR upon creation, and this way pass the port number to the flightrecorder_controller and avoid the duplicate fallback logic.
For the exporter 8181 port, the flightrecorder_controller assumes that the owned ContainerJFR instance will have a port named "export", which is simply the same existing port definition on 8181 as before, but renamed from "8181-tcp" to "export". This allows the controller to connect to the ContainerJFR instance even if the webserver port is changed in the future without requiring an update to the controller code.

Rebased.

Sure, I'll rename the port to something less likely to conflict.
Fair point on looking up the service again anyway, but now I'm also thinking maybe it still makes sense to keep the port number in the FlightRecorderSpec. This way the user can override it themselves if they need to. I can't really think of a good reason why that might be the case, but the flexibility is probably good to have. Maybe the user for some reason doesn't want to modify their configuration to name the port, and has something else already bound to port 9091 and JMX on some other port number?


Unrecognized Android Studio (or Android Support plugin for IntelliJ IDEA) version '202.76<IP_ADDRESS>86908', please retry with version 2020.3.1 or newer.

It looks you might be using IntelliJ IDEA instead, you should be using Android Studio to build this project, you can download it from the official webpage https://developer.android.com/studio

I used android studio but I have this problem:

It looks you are using the previous version to Arctic fox, you can download the latest one from here: https://developer.android.com/studio

Execution failed for task ':libraries:libuvccamera:ndkBuild'.
> A problem occurred starting process 'command 'null/ndk-build''

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

I got this problem

I have problem with ndk

This is probably because you are missing to define the ndk.dir property in local.properties. I have a pending refactor to not require this property

Have you published the fix?


Documentation example

Hi Liz! I've dropped module's usage example using RP. https://rakudist.raku.org/sparky/report/RakuPlay-1/1400
Feel free to use it as a base for a doc or just close this ticket.
Regards
Alexey

Added (slightly modified) to release 0.04.  Thanks!


chore(connlib): reduces noisy log-level on gateway when clients restart

Fixes #6372

Whoops, need the Changelog entry for this bugfix


Conan deps build

All dependency included in conan. Conan build   with  cmake parameter -DCONAN_DEPS=1
Cleaned up all mess with link libraries
Fixed  possibility of deadlock  during sending SIGTERM to nettracer in case of writing larger portion of data to stdout
Fixed correct headers to building bpf program

I've added a few comments here and there but all in all thanks for adding conan! That's awesome

All seems good :)


fix: refactor account initialization and mirror node setup from node command

Description
This pull request changes the following:

Isolate account initialization and mirror node setup from node command
Remove unnecessary socket cleanup code (_stopPortForwards) as the actual issue was with hedera-sdk-js:

See: https://github.com/hashgraph/hedera-sdk-js/issues/2194

Make node-command and account-command e2e tests independent from each other (i.e. use separate namespaces)
Remove unused function resetHapiDirectories to avoid test errors: https://github.com/hashgraph/solo/issues/151

Related Issues

Closes #143
Closes #116
Closes #153
Closes #165
Closes #151

Todo:

https://github.com/hashgraph/solo/issues/168
https://github.com/hashgraph/solo/issues/169

0.00% <0.00%> (ø)

src/commands/mirror_node.mjs 0.00% <0.00%> (ø)

Need to write test/e2e/mirror_node_e2e.test.mjs

:tada: This PR is included in version 0.22.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


How to get the number of arguments in a RuntimeFn?

I'm trying to recover the number of arguments in a RuntimeFn.
using GeneralizedGenerated
get_args(::GeneralizedGenerated.RuntimeFn{Args}) where Args = Args
numargs(ff::GeneralizedGenerated.RuntimeFn) = _get_numargs(get_args(ff),0)
_get_numargs(T,i) = length(T.parameters) >= 3 ? _get_numargs(T.parameters[3],i+1) : i

that works because
get_args(ff).parameters[3].parameters[3].parameters[3].parameters[3].parameters[1]

but is there something nicer?

If any issue raises in the future, please ping me until I made a reply!!!

No worries, thanks!


Detaches the MetadataServer life-cycle from RBAC provider.

See https://github.com/confluentinc/ce-kafka/pull/973.

@confluentinc It looks like @rigelbm just signed our Contributor License Agreement. :+1:
Always at your service,
clabot


Docs: update Select usage tab

Parent issue: https://github.com/carbon-design-system/carbon-website/issues/2085
As part of the fluid input update for Select, we needed to update the usage tab to use the new content template. These updates are being added first before adding the fluid input additions.

Closing as a duplicate
https://github.com/carbon-design-system/carbon-website/issues/3241


Default to escaping HTML content before passing to optional renderer

I believe that we should first html-escape the content before passing to the renderer:
https://github.com/executablebooks/markdown-it-amsmath/blob/master/src/index.ts#L35
There could be an optional parameter to turn off this functionality, but if we are letting users override the renderer I think we should default to doing so safely.

I believe that we should first html-escape the content before passing to the renderer

the content here is not HTML though; it is LaTeX, so I'm not sure if thats a good idea, e.g then a < b would become a < b. Can katex/mathjax handle that?

for the default renderer we could escape just in case, or better just encapsulate it in pre tags, so it cannot be interpreted unsafely

Quite right - sorry this was me getting back up to speed and having these tests in markdown-it-myst unexpectedly failing on me. On that package it is currently setup not to parse the math, but let that be done downstream in the browser (and not package/include katex).
I do think you are right that this is the responsibility of the renderer (default is already escaping, which is good). I will open another issue around documenting that explicitly.
To your points:

for the default renderer we could escape just in case, or better just encapsulate it in pre tags, so it cannot be interpreted unsafely

Pre tags are decorational only: https://stackoverflow.com/a/17882288/817791  still get executed in them, as well as </pre> 💥

the content here is not HTML though; it is LaTeX, so I'm not sure if thats a good idea, e.g then a < b would become a < b. Can katex/mathjax handle that?

Off hand, at least katex can handle that, yes.


[DOC][MINOR] Fix minor error in the code of graphx guide

What changes were proposed in this pull request?
Fix minor error in the code "sketch of pregel implementation" of GraphX guide
How was this patch tested?
N/A

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/4143/
Test PASSed.

Test build #97633 has started for PR 22780 at commit 35c77a5.

Test build #97633 has finished for PR 22780 at commit 35c77a5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/97633/
Test PASSed.

Merged to master/branch-2.4.


cdc sorter dir dose not release after removing task

What did you do?
tiup cdc cli changefeed remove --pd=http://IP:port --changefeed-id simple-replication-task
changefeed removes task, but cdc sorter dose not release.

What did you expect to see?
changefeed removes task, the cdc's data will release.
What did you see instead?
cdc sorter dir dose not release after removing task.
Versions of the cluster
v6.4.0 arm

by the design
/close


Bump the version of peaklets

What does the code in this PR do / what does it improve?
Following: https://github.com/AxFoundation/strax/pull/716
Can you briefly describe how it works?
Can you give a minimal working example (or illustrate with a figure)?
Please include the following if applicable:

[ ] Update the docstring(s)
[ ] Update the documentation
[ ] Tests to check the (new) code is working as desired.
[ ] Does it solve one of the open issues on github?

Notes on testing

Until the automated tests pass, please mark the PR as a draft.
On the XENONnT fork we test with database access, on private forks there is no database access for security considerations.

All italic comments can be removed from this template.

Coverage: 93.608% (-0.01%) from 93.619% when pulling 1acdebd9a4bf15f4a84e7211dfe189a99667f8ca on peaks_bump_hits into c73fe9175db8e7dd04f0205d5166c649bc47fef1 on master.


regex_error at initialization

When loading Jamoma on Raspberry Pi 2 (armv7) I got those errors :
regex_error caught: The code was error_brack with expression "([-\w]+):/"
regex_error caught: regex_error caught: The code was error_brack with expression "[.]"

they come from here : https://github.com/jamoma/JamomaCore/blob/feature/enable-Pd-build/Foundation/library/source/TTRegex.cpp#L41
So it seems that mExpression = new TTExpression(anExpression, regex_constants::extended); throw an exception.
This happens on a fresh native build of JamomaPuredata on Raspberry Pi 2.
Any hint on how to fix that ?

What compiler are you using?

gcc 4.8.2 for native compilation
and arm-linux-gnueabihf-gcc 4.9.2 for cross-compilation

gcc 4.9.2 works fine for native compilation on Linux x86_64

I got the same on Jessie (previous was on Wheezy) with a native build with GCC 4.9.2.

does anyone have an idea how to solve this ?
or at least what it means and what are the consequences ?

this error disappeared on Raspberry Pi
maybe with a system update
so I close the issue


Minor edits to code comments.

Made edits to the code comments to conform to MSDN style.

This is oob file from VS template. We should not go through all of the tokenhelper.cs instances cross all of the samples, rather fix the file in the template.


Benchmark to show that byte buffer copy is size-independent

Byte buffer copy is not a deep copy, it's just a referencing. People don't need to fear its performance impact if they need it.

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

[trickle] No significant performance differences

[trickle] No significant performance differences

There already is a comment on the API but I wanted a way to make sure that we didn't forget for ourselves either.

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,026,842      Total (=)      2,026,842

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,324,726      Total (=)     11,324,726

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,026,842      Total (=)      2,026,842

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,324,725      Total (>)     11,324,721

 No significant differences in binary sizes

API comment added in #17510 but I'd still like this one to be considered

[microbenchmarks] No significant performance differences

[microbenchmarks] No significant performance differences

Right, so has the side effect of making sure that we don't screw this up in the future, correct? I can envision a circumstance under which grpc_byte_buffer ceases to exist in the future and we'll have to spin our own copy and other types of operators so we had better not screw them up when that time comes.

Ack, good point

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,026,842      Total (=)      2,026,842

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,324,730      Total (=)     11,324,730

 No significant differences in binary sizes

[microbenchmarks] No significant performance differences


Can't resize window from top / title bar

I'm using Nightly build 2018-08-28 23:06:03 on WIndows.
You can't resize the window from the top. You can resize from left, right and bottom (and the bottom corners). Resizing from the top or top corners does not work. Actually you can't resize on left or right either when the mouse is on the title bar. So I guess it has something to do with the title bar.

I can drag from the top-right corner, but not in the location you'd expect:

Ah, I see. It works above the three icons. It also works in the corner on the left, if you move he cursor to exactly the right spot.
Anyway, it would be nice if it would work on the entire top and actually in the corner.

This is native behavior for Electron with the non-native frame we use so I can't easily change this. If you really want that to work

Thanks. I found where this was hidden. One small nitpick: when you change the setting to use native frame it says that the application has to be restarted to activate this. But at the same time the exit button (and minimise and maximise too) were hidden. Of course Ctrl-W worked, but I think it would be better to leave these three buttons in place until the application was closed.


Pipenv installs incorrect version of package

My pipfile and pipfile.lock both specify an explicit version of Django - 1.8.11. Locally, using python3 on a Mac, this install works fine. On Travis, using python2 on linux, Django 1.11.12 is installed instead.
Travis: $ python -m pipenv.help output
Pipenv version: '11.10.1'
Pipenv location: '/home/travis/virtualenv/python2.7.14/lib/python2.7/site-packages/pipenv'
Python location: '/home/travis/virtualenv/python2.7.14/bin/python'
Other Python installations in PATH:

2.7: /home/travis/virtualenv/python2.7.14/bin/python2.7
2.7: /home/travis/virtualenv/python2.7.14/bin/python2.7
2.7: /opt/pyenv/shims/python2.7
2.7: /usr/bin/python2.7
3.4: /usr/bin/python3.4m
3.4: /usr/bin/python3.4
3.6: /opt/pyenv/shims/python3.6
2.7.14: /home/travis/virtualenv/python2.7.14/bin/python
2.7.14: /opt/pyenv/shims/python
2.7.6: /usr/bin/python
2.7.14: /home/travis/virtualenv/python2.7.14/bin/python2
2.7.14: /opt/pyenv/shims/python2
2.7.6: /usr/bin/python2
3.4.3: /opt/pyenv/shims/python3
3.4.3: /usr/bin/python3
PEP 508 Information:

{'implementation_name': 'cpython',
 'implementation_version': '0',
 'os_name': 'posix',
 'platform_machine': 'x86_64',
 'platform_python_implementation': 'CPython',
 'platform_release': '4.14.12-041412-generic',
 'platform_system': 'Linux',
 'platform_version': '#201801051649 SMP Fri Jan 5 16:50:54 UTC 2018',
 'python_full_version': '2.7.14',
 'python_version': '2.7',
 'sys_platform': 'linux2'}

System environment variables:

TRAVIS_UID
rvm_version
PYTHONDONTWRITEBYTECODE
TRAVIS
_JAVA_OPTIONS
PIPENV_IGNORE_VIRTUALENVS
TRAVIS_STACK_LANGUAGES
JRUBY_OPTS
VIRTUAL_ENV
SHELL
TRAVIS_PULL_REQUEST_BRANCH
PYENV_SHELL
TRAVIS_BRANCH
TRAVIS_PULL_REQUEST_SLUG
HISTSIZE
NVM_BIN
RBENV_SHELL
MANPATH
JAVA_HOME
_system_type
TRAVIS_SECURE_ENV_VARS
MY_RUBY_HOME
STRIPE_TEST_ORGANIZATION_PUBLISHABLE_KEY
RUBY_VERSION
PIP_DISABLE_PIP_VERSION_CHECK
HOSTNAME
DATABASE_URL
_system_version
TRAVIS_COMMIT_RANGE
GOPATH
CONTINUOUS_INTEGRATION
GOROOT
rvm_path
TRAVIS_REPO_SLUG
USER
PS1
PS4
container
STRIPE_TEST_APPLICATION_ID
SHLVL
TRAVIS_PULL_REQUEST_SHA
MERB_ENV
JDK_SWITCHER_DEFAULT
STRIPE_TEST_PUBLISHABLE_KEY
GIT_ASKPASS
TRAVIS_FILTERED
GEM_PATH
HAS_ANTARES_THREE_LITTLE_FRONZIES_BADGE
TRAVIS_EVENT_TYPE
DWOLLA_TEST_USER_ACCESS_TOKEN
PIP_PYTHON_PATH
DWOLLA_TEST_USER_USER_ID
DWOLLA_TEST_ORGANIZATION_ACCESS_TOKEN
TRAVIS_TAG
DWOLLA_TEST_APPLICATION_KEY
TRAVIS_BUILD_NUMBER
PYENV_ROOT
TRAVIS_STACK_FEATURES
_system_name
DWOLLA_TEST_ORGANIZATION_REFRESH_TOKEN
TRAVIS_SUDO
MIX_ARCHIVES
TRAVIS_BUILD_ID
NVM_DIR
TRAVIS_STACK_NAME
HOME
TRAVIS_PULL_REQUEST
LANG
TRAVIS_COMMIT
_
TRAVIS_STACK_JOB_BOARD_REGISTER
_system_arch
MYSQL_UNIX_PORT
CI
rvm_prefix
DEBIAN_FRONTEND
TRAVIS_PRE_CHEF_BOOTSTRAP_TIME
TRAVIS_COMMIT_MESSAGE
IRBRC
TRAVIS_STACK_TIMESTAMP
CASHER_DIR
STRIPE_TEST_ORGANIZATION_USER_ID
TRAVIS_STACK_NODE_ATTRIBUTES
RACK_ENV
PERLBREW_HOME
GEM_HOME
HAS_JOSH_K_SEAL_OF_APPROVAL
PYTHON_CFLAGS
COMPOSER_NO_INTERACTION
DWOLLA_TEST_USER_REFRESH_TOKEN
NVM_CD_FLAGS
TRAVIS_BUILD_STAGE_NAME
PERLBREW_BASHRC_VERSION
PATH
DWOLLA_TEST_USER_PIN
TRAVIS_ALLOW_FAILURE
TERM
TZ
STRIPE_TEST_ORGANIZATION_ACCESS_TOKEN
MALLOC_ARENA_MAX
HISTFILESIZE
TRAVIS_OSX_IMAGE
rvm_bin_path
STRIPE_TEST_SECRET_KEY
RAILS_ENV
PERLBREW_ROOT
TRAVIS_JOB_NUMBER
PYTHON_CONFIGURE_OPTS
DWOLLA_TEST_APPLICATION_SECRET
DWOLLA_TEST_ORGANIZATION_USER_ID
DWOLLA_TEST_ORGANIZATION_PIN
LC_ALL
TRAVIS_JOB_ID
TRAVIS_PYTHON_VERSION
PAGER
OLDPWD
TRAVIS_LANGUAGE
TRAVIS_BUILD_DIR
HISTCONTROL
PWD
TRAVIS_OS_NAME
ELIXIR_VERSION
rvm_pretty_print_flag
Traceback (most recent call last):
File "/opt/python/2.7.14/lib/python2.7/runpy.py", line 174, in _run_module_as_main
"main", fname, loader, pkg_name)
File "/opt/python/2.7.14/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
File "/home/travis/virtualenv/python2.7.14/lib/python2.7/site-packages/pipenv/help.py", line 89, in
main()
File "/home/travis/virtualenv/python2.7.14/lib/python2.7/site-packages/pipenv/help.py", line 48, in main
print(u'Pipenv–specific environment variables:')
UnicodeEncodeError: 'ascii' codec can't encode character u'\u2013' in position 6: ordinal not in range(128)
The command "python -m pipenv.help" failed and exited with 1 during .

Local: $ python -m pipenv.help output
Pipenv version: '11.10.1'
Pipenv location: '/usr/local/lib/python3.6/site-packages/pipenv'
Python location: '/usr/local/opt/python3/bin/python3.6'
Other Python installations in PATH:

2.7: /usr/bin/python2.7

2.7: /usr/bin/python2.7

3.6: /usr/local/bin/python3.6m

3.6: /usr/local/bin/python3.6

2.7.10: /usr/bin/python

3.6.3: /usr/local/bin/python3

PEP 508 Information:
{'implementation_name': 'cpython',
 'implementation_version': '3.6.3',
 'os_name': 'posix',
 'platform_machine': 'x86_64',
 'platform_python_implementation': 'CPython',
 'platform_release': '17.5.0',
 'platform_system': 'Darwin',
 'platform_version': 'Darwin Kernel Version 17.5.0: Mon Mar  5 22:24:32 PST '
                     '2018; root:xnu-4570.51.1~1/RELEASE_X86_64',
 'python_full_version': '3.6.3',
 'python_version': '3.6',
 'sys_platform': 'darwin'}

System environment variables:

TERM_PROGRAM
TERM
SHELL
TMPDIR
Apple_PubSub_Socket_Render
TERM_PROGRAM_VERSION
TERM_SESSION_ID
USER
SSH_AUTH_SOCK
PATH
PWD
LANG
XPC_FLAGS
XPC_SERVICE_NAME
HOME
SHLVL
LOGNAME
SECURITYSESSIONID
_
__CF_USER_TEXT_ENCODING
PYTHONDONTWRITEBYTECODE
PIP_PYTHON_PATH

Pipenv–specific environment variables:
Debug–specific environment variables:

PATH: /usr/local/Cellar/node/9.6.1/bin/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/Postgres.app/Contents/Versions/latest/bin
SHELL: /bin/bash
LANG: en_US.UTF-8
PWD: /Users/******/projects/django-brambling

Contents of Pipfile ('/Users/******/projects/django-brambling/Pipfile'):
[[source]]

url = "https://pypi.python.org/simple"
verify_ssl = true
name = "pypi"

[packages]

django = "==1.8.11"
pytz = "==2015.2"
sqlparse = "==0.1.14"
unicode-slugify = "==0.1.3"
libsass = "==0.9.1"
django-libsass = "==0.4"
django-appconf = "==1.0.1"
django-compressor = "==1.5"
django-countries = "==3.4.1"
django-filter = "==0.12.0"
django-grappelli = "==2.7.3"
dj-database-url = "==0.4.2"
pillow = "==2.8.1"
django-daguerre = "==2.1.2"
django-floppyforms = "==1.6.1"
django-localflavor = "==1.1"
stripe = "==1.35.0"
requests = "==2.10.0"
dwolla = "==2.0.7"
django-talkback = "==0.1.2"
djangorestframework = "==3.3.0"
openpyxl = "==2.2.6"
jdcal = "==1.0.1"
unicodecsv = "==0.14.1"
markdown = "==2.6.5"
bleach = "==1.4.2"
"html5lib" = "==0.9999999"
django-bootstrap = {git = "https://github.com/littleweaver/django-bootstrap.git", editable = true, ref = "bootstrap3"}
django-zenaida = {git = "git://github.com/littleweaver/django-zenaida.git", editable = true, ref = "master"}
mock = "==1.0.1"
factory-boy = "==2.4.1"
tox = "==1.8.1"
virtualenv = "==12.0.6"
py = "==1.4.26"
vcrpy = "==1.7.4"
pyyaml = "==3.11"
wrapt = "==1.10.5"
"contextlib2" = "==0.4.0"
sendgrid = "==2.2.1"
sendgrid-django = "==2.0.0"
smtpapi = "==0.3.1"
python-http-client = "==1.2.3"
gunicorn = "*"
django-debug-toolbar = "==1.4"
django-debug-toolbar-template-timings = "==0.6.4"
"psycopg2" = "*"

[dev-packages]

[requires]

python_version = "2.7"

Contents of Pipfile.lock ('/Users/******/projects/django-brambling/Pipfile.lock'):
{
    "_meta": {
        "hash": {
            "sha256": "d52723785433ec049f8233dd6ee7ad289f4edab567492d5ba8984ea7e5430ad5"
        },
        "host-environment-markers": {
            "implementation_name": "cpython",
            "implementation_version": "0",
            "os_name": "posix",
            "platform_machine": "x86_64",
            "platform_python_implementation": "CPython",
            "platform_release": "17.4.0",
            "platform_system": "Darwin",
            "platform_version": "Darwin Kernel Version 17.4.0: Sun Dec 17 09:19:54 PST 2017; root:xnu-4570.41.2~1/RELEASE_X86_64",
            "python_full_version": "2.7.10",
            "python_version": "2.7",
            "sys_platform": "darwin"
        },
        "pipfile-spec": 6,
        "requires": {
            "python_version": "2.7"
        },
        "sources": [
            {
                "name": "pypi",
                "url": "https://pypi.python.org/simple",
                "verify_ssl": true
            }
        ]
    },
    "default": {
        "bleach": {
            "hashes": [
                "sha256:58a2c153c0b5450695c34ce2eddc23fb3ee476b31a878e6a5c24c75fd1ed4d89",
                "sha256:56018a17d1488eb1a1e18e7cdddcaea24d3c7b3704172e356f6916c577f4fd9e"
            ],
            "version": "==1.4.2"
        },
        "contextlib2": {
            "hashes": [
                "sha256:55a5dc78f7a742a0e756645134ffb39bbe11da0fea2bc0f7070d40dac208b732"
            ],
            "version": "==0.4.0"
        },
        "dj-database-url": {
            "hashes": [
                "sha256:e16d94c382ea0564c48038fa7fe8d9c890ef1ab1a8ec4cb48e732c124b9482fd",
                "sha256:a6832d8445ee9d788c5baa48aef8130bf61fdc442f7d9a548424d25cd85c9f08"
            ],
            "version": "==0.4.2"
        },
        "django": {
            "hashes": [
                "sha256:54be9d6eab6cc0e2da558c12aea6cff7d5a0124c8a470e1ff61134ba9ed37f20",
                "sha256:ec148be73548da090dd76c2e8c57c98e8b1e84f2cb87500b9be5420187a435fb"
            ],
            "version": "==1.8.11"
        },
        "django-appconf": {
            "hashes": [
                "sha256:3d9bc963d8008ae151d6c664f9fd55442705ea9b9e6d7ce77cdd40bf92d91f3a",
                "sha256:ba1375fb1024e8e91547504d4392321795c989fde500b96ebc7c93884f786e60"
            ],
            "version": "==1.0.1"
        },
        "django-bootstrap": {
            "editable": true,
            "git": "https://github.com/littleweaver/django-bootstrap.git",
            "ref": "5f3fb1d1d9dd57aff8de08a224a1540b7c8df1fc"
        },
        "django-compressor": {
            "hashes": [
                "sha256:516866224ec33bf227f79718c0b154debf2967fe249c12d721bbe2c45ecbe34c",
                "sha256:0189fd1dbf87d802f4e4e21ebc9220f29bbb7771b252a958ad6119f61453e22e"
            ],
            "version": "==1.5"
        },
        "django-countries": {
            "hashes": [
                "sha256:23c6b5455a2e68ed02601cee0d3c80481965d0c3a6bd2f07ca56902b0a4c55a6",
                "sha256:5bdda9d2c3473b519371428d88517f29befad7e35dfc489e8b0f95cb2aa941dc"
            ],
            "version": "==3.4.1"
        },
        "django-daguerre": {
            "hashes": [
                "sha256:f9563b918fd2e17aba4d9fa12d8e4644953a4958609dcc21d311a9ab1429c65a"
            ],
            "version": "==2.1.2"
        },
        "django-debug-toolbar": {
            "hashes": [
                "sha256:852a37b80df9597048591ebc87d0ce85a4edceaef015dc5360ad89cc5960c27b",
                "sha256:0cbae8760f4851d480a70b72ace5b075f8191ecf899bc97427715e50fb0e90b9"
            ],
            "version": "==1.4"
        },
        "django-debug-toolbar-template-timings": {
            "hashes": [
                "sha256:5d5ddb2ba1da4c861952fbc910a5acc1dc26424c94409157d90b98febdb26da8"
            ],
            "version": "==0.6.4"
        },
        "django-filter": {
            "hashes": [
                "sha256:8b6459e58dbf6f67384707be6724a0a88db6709764bc2eb9de265a52dc441ccb"
            ],
            "version": "==0.12.0"
        },
        "django-floppyforms": {
            "hashes": [
                "sha256:11c23fc0a910a73a59c44a9eda687e385870dd69242dbcbf77558e7dd78c4d16"
            ],
            "version": "==1.6.1"
        },
        "django-grappelli": {
            "hashes": [
                "sha256:230a9c83c28c9ba563df9583bd212354ef262689fb1467cb28d80229fd1f5ccf"
            ],
            "version": "==2.7.3"
        },
        "django-libsass": {
            "hashes": [
                "sha256:9fc3d90623810565d482b7e4b4f8414a5f886fd6f39705adb27fdead012ded6c",
                "sha256:e22d1aacbc4865260df8a22999eb1dbab6847ee6abe6d2dd2108c547a3c3fb99"
            ],
            "version": "==0.4"
        },
        "django-localflavor": {
            "hashes": [
                "sha256:afd6627cd0fd396824e44a5e4f7bfe9c8d7a45d9bf09b4db2c0683d92681ba93",
                "sha256:3b5503b512248af661cf91e4f402327619ffc3bc5b3b0ea774a969ed3bf84594"
            ],
            "version": "==1.1"
        },
        "django-talkback": {
            "hashes": [
                "sha256:32242f51274128c51a319f976a2613a2062a16fafaaa075321efb7f7397e1d82"
            ],
            "version": "==0.1.2"
        },
        "django-zenaida": {
            "editable": true,
            "git": "git://github.com/littleweaver/django-zenaida.git",
            "ref": "fef8a6ac9a4aeb47d23351cbdc1d2add3aa0032a"
        },
        "djangorestframework": {
            "hashes": [
                "sha256:3cc9960bcfa19bfdc8c789d3865ea2b100a90917ac16f803ad99e45421ec8b4c",
                "sha256:29803ff85b1f2105bcf49bd4c790d2b319196b78c88c70624d8ac931dd7647af"
            ],
            "version": "==3.3.0"
        },
        "dwolla": {
            "hashes": [
                "sha256:23d5b665ccd2ac212d3fb4a59ce43f4c97931fca1432d0559071a98693f238c3"
            ],
            "version": "==2.0.7"
        },
        "factory-boy": {
            "hashes": [
                "sha256:d7012499e52de5a4413e22aed51df8948533685452dfe16b41001f28f9ce5b1c"
            ],
            "version": "==2.4.1"
        },
        "gunicorn": {
            "hashes": [
                "sha256:75af03c99389535f218cc596c7de74df4763803f7b63eb09d77e92b3956b36c6",
                "sha256:eee1169f0ca667be05db3351a0960765620dad53f53434262ff8901b68a1b622"
            ],
            "version": "==19.7.1"
        },
        "html5lib": {
            "hashes": [
                "sha256:2612a191a8d5842bfa057e41ba50bbb9dcb722419d2408c78cff4758d0754868"
            ],
            "version": "==0.9999999"
        },
        "jdcal": {
            "hashes": [],
            "version": "==1.0.1"
        },
        "libsass": {
            "hashes": [
                "sha256:a73453079866dad63b9073ac7a03059a9a8d41d051ea05401960d0d0a692b8d3",
                "sha256:17701c6357ee1471199b4683cb209399ae80ae33f598eb8608e1e3725a1b9f91",
                "sha256:0f6d0079a631eb00772200086a11efb72dbecf675188d1e0b9d650efa6edde9e",
                "sha256:d55b599d5bec2e29fd30573fdc3c8d9c39d539ee31bbb87693c4ec3e5cb2a452",
                "sha256:2ca8adb71ef5ccdad123bfbb37effb9321317de7365d118cf52ebe1a7b15b8f3",
                "sha256:bfc6a3d503cca077617ff7a9f156a5725b82ae5bb863bf0d447b73df99b326d7",
                "sha256:5189c65abd69437a90dbba642e0e798ee31cf76354f5e0bc397d78bdf03c877b",
                "sha256:3ae2430b65b43f196276b50e176975c2578d0e5d7c8ffb0aedc7637162b9954e",
                "sha256:82ce26c75474eb681bf1e1c30c6e805901b25a03e635d93e12db67cc6c861b78",
                "sha256:10c7f0aaaec78f2ec5ed4e318067b8494b605b8d45544362fa68d096fad0ec58"
            ],
            "version": "==0.9.1"
        },
        "markdown": {
            "hashes": [
                "sha256:8d94cf6273606f76753fcb1324623792b3738c7612c2b180c85cc5e88642e560",
                "sha256:a59fdbcec28f79ad9842ea7f74cde5a02e14a3025836e0bc66c4fc48596ce2ca"
            ],
            "version": "==2.6.5"
        },
        "mock": {
            "hashes": [
                "sha256:b839dd2d9c117c701430c149956918a423a9863b48b09c90e30a6013e7d2f44f",
                "sha256:8f83080daa249d036cbccfb8ae5cc6ff007b88d6d937521371afabe7b19badbc"
            ],
            "version": "==1.0.1"
        },
        "openpyxl": {
            "hashes": [
                "sha256:0e580133106976da044b5861231283fb4e1b2d439787e0f668f28eb2dfd7468e"
            ],
            "version": "==2.2.6"
        },
        "pillow": {
            "hashes": [
                "sha256:33857a509bef5024a930858727f394b3474ffd37cf92d6b106509bf8962c5d81",
                "sha256:a7464b99a107d5e242ae4030edf8fffc050b84a6fc517ab8af09efb763c9bb35",
                "sha256:109eaaa9e1c53084e24961bb60b5a61f7398970d0c3c859959b0d029c5208fed",
                "sha256:5184fcd235e0c032553cb71a816f2275eec2b8d1e60bf5c7eb42542d8386c2d1",
                "sha256:cdccedfc37e1e4c3d4c9360747d938b8cc2420af8898b6c2629500c179731a1e",
                "sha256:ee8ae884a0418a7147edd8b5540eefb4926c1f8b0caa6785b9a5550bd7055f52",
                "sha256:9776042ede2050cc224db1e139a815a17fc9754a2624ec8853d0afd84366d073",
                "sha256:d15f69a9f3e9d0f2cb439c2834803b9b0649cb38123b9e0a5277cdb1d5997dc1",
                "sha256:540e4cddf981569f2acf1013dec860c793e31babd6bc4ba46e1804403bfc8b36",
                "sha256:2267fbbf8393e298c1b2ce7c397c75e88e8489265153070ec51d956b9ecac8dc",
                "sha256:455d04e21451b30b1774a00fe4ea83c74613605540690de63411e75334a80bfd",
                "sha256:2d0440fdc8d725a493771cce488a72cfd452b3b53c6743586f7e92f84984ebc7",
                "sha256:c26f0857fdedb23ef08acdb2fdfee15271af717299483cf4ef41f47c604fbda1",
                "sha256:38b4d893a446e077886474f953c5aa8dc6f90f47a8da31eff63b16d294d03c00",
                "sha256:433563b48ac01d52e4fde150f9e07634f58ee66009ae4aec2cdfb84f3d5438be",
                "sha256:6f1561c647ee91a439c50e9576cb20920a3be9776fdf16ac2aef5249177b7010",
                "sha256:5463bde2b3483cd45f43b3c6a3034a781f3ca2d2ccd0f90676222fbebf67d12d",
                "sha256:4d97a54a2ed380cd630ae3362f169b5336b48f8368861a34490d75c813c67cb7",
                "sha256:d292c95aba085fcb0ff839129b84ebb8c964bba68d42ba5673db1aa9de5b0874",
                "sha256:c431d17c324eccd9c99aa1abb506c8cdcfa41e28d114ea95074f819c0648a0f3",
                "sha256:3a207c6783a6a1fd8a958a50598268365550775864878bba6b864e9b8d643218",
                "sha256:74f6954513c1c476f1e8e241d3c047e3067ca9ff1ae7f97a5cc9d1cf6e819b9a",
                "sha256:fe1aa622147ef7384f491a8b9921e9ebe26f6f135a8f38b5aa3091d4f502e4cf",
                "sha256:38388af06183e9b201331ff2124eaa3919cf9d7720075fdccf6b57f217db0d82",
                "sha256:8760c118a0215eba163f7782110e7efcdbb15f8a7321f3f61c5ac0dbbb12c996",
                "sha256:02ac80fce72e37fe1825d346737414dc07ba5267eba269e4a9c38112ce7190a0",
                "sha256:2b5ae249ad44a4913f420868e5bd54885c79c6f178b308fdf2710e7282645ae5",
                "sha256:7a2ecd3edc5ae8d300c1718fae94f3b06c5347caa1f8835163378621d2c9b1d8",
                "sha256:26c8401a5155c2f6bca34116b7249e6f3afb6f0137e2cefce6ca1fe1e495d02b",
                "sha256:1203fbe337d56e27c360243ec36f5054ffced473f66c4cf26924cd20f9d225b8",
                "sha256:c5563fc8f42d9ec527af5da6b2ed58a738fb74197b1e5e40d7fda05d5a0330f6",
                "sha256:c015c9ec756fded7606b25c311510d631ca7774c085a5954884720d10444e0b8",
                "sha256:5a60d78c11d3d054867714decb3605705ce4ea64388dacd1ebcfd6311af2cd55",
                "sha256:a30e6f5f7a1afba81c75e79805f0f806a4c36d70e4d22f290e3b11c268395e36",
                "sha256:00d72776e62d66c88ed01eb67680ed24d9db679071a1ade365c25ccf7a945db5",
                "sha256:4363b52527c263e77f5b18c3dfffd15ae454edf0c4457197ecbe29863a651938"
            ],
            "version": "==2.8.1"
        },
        "psycopg2": {
            "hashes": [
                "sha256:aeaba399254ca79c299d9fe6aa811d3c3eac61458dee10270de7f4e71c624998",
                "sha256:1d90379d01d0dc50ae9b40c863933d87ff82d51dd7d52cea5d1cb7019afd72cd",
                "sha256:36030ca7f4b4519ee4f52a74edc4ec73c75abfb6ea1d80ac7480953d1c0aa3c3",
                "sha256:7cbc3b21ce2f681ca9ad2d8c0901090b23a30c955e980ebf1006d41f37068a95",
                "sha256:b178e0923c93393e16646155794521e063ec17b7cc9f943f15b7d4b39776ea2c",
                "sha256:fe6a7f87356116f5ea840c65b032af17deef0e1a5c34013a2962dd6f99b860dd",
                "sha256:6f302c486132f8dd11f143e919e236ea4467d53bf18c451cac577e6988ecbd05",
                "sha256:888bba7841116e529f407f15c6d28fe3ef0760df8c45257442ec2f14f161c871",
                "sha256:932a4c101af007cb3132b1f8a9ffef23386acc53dad46536dc5ba43a3235ae02",
                "sha256:179c52eb870110a8c1b460c86d4f696d58510ea025602cd3f81453746fccb94f",
                "sha256:33f9e1032095e1436fa9ec424abcbd4c170da934fb70e391c5d78275d0307c75",
                "sha256:092a80da1b052a181b6e6c765849c9b32d46c5dac3b81bf8c9b83e697f3cdbe8",
                "sha256:f3d3a88128f0c219bdc5b2d9ccd496517199660cea021c560a3252116df91cbd",
                "sha256:19983b77ec1fc2a210092aa0333ee48811fd9fb5f194c6cd5b927ed409aea5f8",
                "sha256:027ae518d0e3b8fff41990e598bc7774c3d08a3a20e9ecc0b59fb2aaaf152f7f",
                "sha256:363fbbf4189722fc46779be1fad2597e2c40b3f577dc618f353a46391cf5d235",
                "sha256:d74cf9234ba76426add5e123449be08993a9b13ff434c6efa3a07caa305a619f",
                "sha256:32702e3bd8bfe12b36226ba9846ed9e22336fc4bd710039d594b36bd432ae255",
                "sha256:8eb94c0625c529215b53c08fb4e461546e2f3fc96a49c13d5474b5ad7aeab6cf",
                "sha256:8ebba5314c609a05c6955e5773c7e0e57b8dd817e4f751f30de729be58fa5e78",
                "sha256:27467fd5af1dcc0a82d72927113b8f92da8f44b2efbdb8906bd76face95b596d",
                "sha256:b68e89bb086a9476fa85298caab43f92d0a6af135a5f433d1f6b6d82cafa7b55",
                "sha256:0b9851e798bae024ed1a2a6377a8dab4b8a128a56ed406f572f9f06194e4b275",
                "sha256:733166464598c239323142c071fa4c9b91c14359176e5ae7e202db6bcc1d2eb5",
                "sha256:ad75fe10bea19ad2188c5cb5fc4cdf53ee808d9b44578c94a3cd1e9fc2beb656",
                "sha256:8966829cb0d21a08a3c5ac971a2eb67c3927ae27c247300a8476554cc0ce2ae8",
                "sha256:8bf51191d60f6987482ef0cfe8511bbf4877a5aa7f313d7b488b53189cf26209"
            ],
            "version": "==2.7.4"
        },
        "py": {
            "hashes": [
                "sha256:28dd0b90d29b386afb552efc4e355c889f4639ce93658a7872a2150ece28bb89"
            ],
            "version": "==1.4.26"
        },
        "python-http-client": {
            "hashes": [
                "sha256:f866df885580617f2f86553bc2ce454468df951d288ca99d52c542ae424dda18",
                "sha256:3f25f2431c61dfbe494470d671672b2c6c86a9bcd24c340259e86813fe3dd5ac"
            ],
            "version": "==1.2.3"
        },
        "pytz": {
            "hashes": [
                "sha256:f8a813af15ac5e68b52dfc2a0aaa41b1c9b5cfa8e15fa9cf754837f74af74d74",
                "sha256:08e8e012bb06237aea5781c1afdeef00590d4cebdb0c098439f8f2eb3046331b",
                "sha256:2fe74abd1b6d18f93c121558c94c34133881f73f1ec005809b4a9db756a5a91f",
                "sha256:5e77e68293879fdd9a7b9ff37a0cc9123294b020cba189a8c1b6922cd9f703b5",
                "sha256:358b05a0c2605c15cf8337d17016eb95afeaad07c900df9c2cde76e2194a9258",
                "sha256:374106e01ccdaca4f7fbeec7164c016d92684f05aa38feb1d507dd2fb789ef1f",
                "sha256:40913c6bfeba1e6b1aef5366db6a74c36253e51a65600e8b770aed7bf7b9d23f",
                "sha256:6549f19811bfd147517ae68b9d25d89a0207dd308c7a334bd419514e36875c2b",
                "sha256:fe69c915863fe0f24c00d61a4bfa5ebd0fa08d859db3a1cfcb3fb20f1a67dd45",
                "sha256:3e15b416c9a2039c1a51208b2cd3bb4ffd796cd19e601b1d2657afcb77c3dc90",
                "sha256:73daf0eb44ad929ad56972ad30938cb231b725b27dff105b7168e7b4491e0452",
                "sha256:93f81122d86983cbb056cd12ca7de39d760b6f3e3060e43eff5c5e2034516fa2"
            ],
            "version": "==2015.2"
        },
        "pyyaml": {
            "hashes": [
                "sha256:c36c938a872e5ff494938b33b14aaa156cb439ec67548fcab3535bb78b0846e8",
                "sha256:e3bc2528c3a0f396908b5f8784795f3f7b62e8b2573c2db736addccfb22449e4",
                "sha256:ca129663271174f9783e1177195e4288945a504db89f5c3889da75e0abbd0a67",
                "sha256:d44be6e77802ea845911e000e29d781ba2900a0fe3b38fc0f5b74f5f77d2e4f0",
                "sha256:2abbe0b237b42e075e5a59f90766c0a18cc29aea3baa7a152cc16f62fa556daa",
                "sha256:ad55a89cc264b74be59df9fdcea1dffd14f435d955eae2ac822a28563be2fe48",
                "sha256:e25c2074189eb72056778c88344f47e5e7378afd52da62014bb3e86efce947c1",
                "sha256:b54b4782da60c7dfe5d850524416dd03f3b9a516ed476ce1d5a2712cde75d683",
                "sha256:2db3d4c54d3eb47ad7169806e684d5243d4a14749cb9741ef5d1ac3291d67a1a",
                "sha256:3e8c104861b5839a36e6b30c2f964d6fbf4a2e2b87ae9c289da699b21e35c91b",
                "sha256:7a02d22209e41ba55bd8a65fa69ee593af30a857f6e33fc9c80589e6b477c36b",
                "sha256:d9b72815d3cdc5e1c3f1f44498a5e884fe4dcdb3f6428fa086e35af8160d2809",
                "sha256:c81b0cccf6b6bfc0432c1a96c07b64b76472118ec789bc4891447cc5298bd1c7",
                "sha256:19bb3ac350ef878dda84a62d37c7d5c17a137386dde9c2ce7249c7a21d7f6ac9"
            ],
            "version": "==3.11"
        },
        "requests": {
            "hashes": [
                "sha256:09bc1b5f3a56cd8c48d433213a8cba51a67d12936568f73b5f1793fcb0c0979e",
                "sha256:63f1815788157130cee16a933b2ee184038e975f0017306d723ac326b5525b54"
            ],
            "version": "==2.10.0"
        },
        "sendgrid": {
            "hashes": [
                "sha256:3346d44c74637f9e911246bda8685b379d6658a656a7ec75d6a28ec327b81769",
                "sha256:4d6ebcc532b2b8f2354b96ab52465b718dd8cde23914197bcb002320ea230fba"
            ],
            "version": "==2.2.1"
        },
        "sendgrid-django": {
            "hashes": [
                "sha256:cbd495a5d5a6a9bf39f798a40608b4fe3f488ae43df39f9077704ec3013acbac"
            ],
            "version": "==2.0.0"
        },
        "six": {
            "hashes": [
                "sha256:832dc0e10feb1aa2c68dcc57dbb658f1c7e65b9b61af69048abc87a2db00a0eb",
                "sha256:70e8a77beed4562e7f14fe23a786b54f6296e34344c23bc42f07b15018ff98e9"
            ],
            "version": "==1.11.0"
        },
        "smtpapi": {
            "hashes": [
                "sha256:dcc6f1c3960ff7bb7e8b9dfb0126c9b5456db9d81c44805659ea58dabd600c37"
            ],
            "version": "==0.3.1"
        },
        "sqlparse": {
            "hashes": [
                "sha256:e561e31853ab9f3634a1a2bd53035f9e47dfb203d56b33cc6569047ba087daf0"
            ],
            "version": "==0.1.14"
        },
        "stripe": {
            "hashes": [
                "sha256:1bd1b1e44666d9857672b57495728e93c275065054300656c84d3bd6cfaa648a",
                "sha256:92b85d28865e55dce2d550cd362ce072f3960b659751c9dbe733b8615064c18d",
                "sha256:c99babe980fbe923abe28c545db668a2b31ca75b8602aa759c760927ef9087dd"
            ],
            "version": "==1.35.0"
        },
        "tox": {
            "hashes": [
                "sha256:44ca1e038cb57fe40ac0dff8b67b258efe05517bf9b4b4b07035f8be830aac01"
            ],
            "version": "==1.8.1"
        },
        "unicode-slugify": {
            "hashes": [
                "sha256:34cf3afefa6480efe705a4fc0eaeeaf7f49754aec322ba3e8b2f27dc1cbcf650"
            ],
            "version": "==0.1.3"
        },
        "unicodecsv": {
            "hashes": [
                "sha256:018c08037d48649a0412063ff4eda26eaa81eff1546dbffa51fa5293276ff7fc"
            ],
            "version": "==0.14.1"
        },
        "unidecode": {
            "hashes": [
                "sha256:72f49d3729f3d8f5799f710b97c1451c5163102e76d64d20e170aedbbd923582",
                "sha256:8c33dd588e0c9bc22a76eaa0c715a5434851f726131bd44a6c26471746efabf5"
            ],
            "version": "==1.0.22"
        },
        "vcrpy": {
            "hashes": [
                "sha256:c558f50c20ec7a3e5d5d71c0e9701518dff959736f2a8e7f1f98798354e44e6e"
            ],
            "version": "==1.7.4"
        },
        "virtualenv": {
            "hashes": [
                "sha256:c420d686ac04eb9d30e3dc9898080f73008878fbbc367e2cda2568b9772f9fac",
                "sha256:db8c3c89d6a8369082530b3bd2084924357ae1216b239c387e576b814bab592f"
            ],
            "version": "==12.0.6"
        },
        "wrapt": {
            "hashes": [
                "sha256:99cbb4e3a3ea964df0cb1437261fc1198616ec872e7b501622f3f7f92fcd0833"
            ],
            "version": "==1.10.5"
        }
    },
    "develop": {}
}

Expected result
The version of django specified & locked is installed.
Actual result
A different version is installed. I can't provide verbose logs because they're over 4MB large and travis won't even save the whole thing.
Steps to replicate
I'm not sure how to replicate this, since it works fine locally. Here's the repository I'm working on at a commit where this is breaking on travis. Here's the related travis build that's failing.
The commands that travis is running (some purely for debug information) are:
install:
- pip install pipenv
- pipenv --version
- pipenv install
- pipenv graph
- psql --version
- pipenv run pip install flake8==3.3.0
before_script:
- psql -c 'drop database if exists brambling_test;' -U postgres
- psql -c 'create database brambling_test;' -U postgres
- pipenv run flake8 brambling
script:
- python -c "from pipenv.environments import user_cache_dir; print user_cache_dir('pipenv')"
- pipenv run python -c "import django; print django.VERSION"
- "pipenv run ./manage.py test --verbosity=2 brambling"

Please note that pipenv graph, which runs immediately after pipenv install already shows the incorrect version of django installed.

pipenv run python manage.py test... is a better way to handle running manage.py commands, ./command invocation is not guaranteed to work as you think it will
This actually should be pretty simple--

You are using PIPENV_IGNORE_VIRTUALENVS=1 which is a good idea on travis
However, travis by default uses a bunch of pyenv installs, so you need to also set PIPENV_DONT_USE_PYENV=1
I would recommend just also setting PIPENV_VENV_IN_PROJECT as well.

That's what our own tests do.  Our travis file looks like this:
sudo: false
dist: trusty
language: python
python:
  - "3.6"
  - "2.7"
env:
  global:
    - PYPI_VENDOR_DIR='./tests/pypi/'
    - GIT_ASK_YESNO='false'
    - PYTHONIOENCODING='utf-8'
  matrix:
    - TEST_SUITE='not install'
    - TEST_SUITE='install'
      PYTEST_ADDOPTS='--cache-clear'

install:
  - "pip install --upgrade pip"
  - "pip install -e . --upgrade --upgrade-strategy=only-if-needed"
  - "pipenv install --dev"
  - 'pip install -e "$(pwd)" --upgrade'
  - 'pipenv install --system --dev'

script:
  - 'pipenv run time pytest -v -n 4 -m "$TEST_SUITE" tests'
sudo: false
dist: trusty
language: python
python:
  - "3.6"
  - "2.7"
env:
  global:
    - PYPI_VENDOR_DIR='./tests/pypi/'
    - GIT_ASK_YESNO='false'
    - PYTHONIOENCODING='utf-8'
  matrix:
    - TEST_SUITE='not install'
    - TEST_SUITE='install'
      PYTEST_ADDOPTS='--cache-clear'

install:
  - "pip install --upgrade pip"
  - "pip install -e . --upgrade --upgrade-strategy=only-if-needed"
  - "pipenv install --dev"
  - 'pip install -e "$(pwd)" --upgrade'
  - 'pipenv install --system --dev'

script:
  - 'pipenv run time pytest -v -n 4 -m "$TEST_SUITE" tests'

Let me know if this helps!

Thanks for responding so quickly. I tried adding the suggested env vars and explicitly running python, but am still getting the same result: https://travis-ci.org/dancerfly/django-brambling/builds/372783297
In case it's relevant, it doesn't seem like either suggested env var is used in your travis.yml file.

I can also now confirm that if I limit the dependencies to just django, the installation works fine.

I get the correct version of django as long as I don't install either of the git dependencies.

Minimal pipfile to get this error case on travis:
[[source]]
url = "https://pypi.python.org/simple"
verify_ssl = true
name = "pypi"

[packages]
django = "==1.8.11"
django-bootstrap = {git = "https://github.com/littleweaver/django-bootstrap.git", editable = true, ref = "bootstrap3"}

[dev-packages]

[requires]
python_version = "2.7"

I see what's going on here, it's prioritizing the resolution of the VCS dependencies (we don't typically recommend listing non-top-level dependencies like django unless it's absolutely necessary) -- in your case I think you should take these out of editable mode -- I can see that the second dependency needs django-floppyforms and django-talkback so you should put those in your Pipfile to make sure they wind up in your lockfile also.
Basically this will stop the resolver from attempting to find the dependencies of the git-referenced packages and putting them in the lockfile.
The other option is to just put these in dev-packages and the version pinned in packaages should be preferred
Let me know if that works

@techalchemy Thanks again for your quick response! :-)
The django-brambling repository is a project repository, not a reusable package. We use it to deploy our servers, so it's imperative that the Pipfile.lock is honored, even if we have git dependencies. In this case, our pipfile.lock correctly listed django 1.8.11 as the locked version, but django 1.11.12 was installed despite that.
More generally, I would also expect that explicitly stating a requirement for a particular version of a package would have precedence over all subdependencies of packages I might list, no matter what order things are listed in.
I'm not quite clear from your responses in this thread whether these are acknowledged as bugs or if they're seen as user error. It's pretty clear in my mind that they are bugs, but I would love to get confirmation one way or another?
Regarding the structuring suggestions:
My understanding of install_requires has always been that it's intended for open-source packages, to ensure that dependencies are automatically installed via pip, not for setting up a virtual environment with specific packages for a deploy; since this is for a project repo, I'm hesitant to use install_requires. Are you saying that install_requires is used by pipenv as a "base" for the requirements listed in the two package sections? That isn't something I've ever noticed in the documentation, but maybe I missed it?
The reason that I have tox and django-debug-toolbar in [packages] is because in the past when I've put them in [dev-packages] and then installed dev packages, they've conflicted with the non-dev installed packages. For example, if I put django in [packages] at 1.8.11 and django-debug-toolbar in [dev-packages], I end up with django 2.0 installed, as a dependency of django-debug-toolbar.

I tried moving things to install_requires, as suggested, and it resulted in none of those dependencies getting installed by pipenv, so that seems like it unfortunately is not the solution (unless I'm doing something wrong).

After further investigation, this seems to be (partially) a race condition issue. If I introduce a delay before installing the VCS dependencies, or use --sequential, the correct version of django is installed.
The other half of this is that VCS dependencies (unlike any other dependency) do not use --no-deps, which makes the race condition possible.
So yeah - workaround is: use --sequential or run install multiple times.

The django-brambling repository is a project repository, not a reusable package. We use it to deploy our servers, so it's imperative that the Pipfile.lock is honored, even if we have git dependencies.

Reusability and being a package don't have anything to do with one another, being reusable doesn't require being a package, and being a package doesn't imply that a thing is reusable.  Many teams use local packaging environments to install their own software in production or testing, or to insulate individual dependencies.

In this case, our pipfile.lock correctly listed django 1.8.11 as the locked version, but django 1.11.12 was installed despite that.

I agree. That is a desirable outcome.

More generally, I would also expect that explicitly stating a requirement for a particular version of a package would have precedence over all subdependencies of packages I might list, no matter what order things are listed in.

I actually disagree with this, lets use an example.  Say you install Package A and Package B==1.0.  And say for instance Package A has a strict pin itself depending on Package B>=1.1. You're suggesting some kind of weighting given to the dependency graph based on how close to the top a version is, but that doesn't really work because you may simply be installing a broken environment. We can't simply trust that your version is correct.
In this case your version (1.8) does satisfy the other dependencies, so it's just an issue of how the resolver itself works, which is that it finds the best satisfying dependency and moves on rather than storing the context (which is actually a difficult problem in and of itself).  We have an open issue that would allow for per-package overrides which helps with this kind of thing (#1921)
This is a resolution order issue and I agree it should be handled correctly. While I understand this may seem simple, in fact it isn't, or it would be working correctly :) That's why we try to let the resolver handle this instead of using strict pins.

I'm not quite clear from your responses in this thread whether these are acknowledged as bugs or if they're seen as user error. It's pretty clear in my mind that they are bugs

They are most certainly bugs, that's why we have open issues addressing them and flattening the dependency graph is not something you will get out of pip either, which is also order-sensitive when installing requirements.txt. I am offering you paths to solve the problem while we nail down the resolution issues.

My understanding of install_requires  has always been that it's intended for open-source packages, to ensure  that dependencies are automatically installed via pip, not for setting  up a virtual environment with specific packages for a deploy; since this  is for a project repo, I'm hesitant to use install_requires.

install_requires has nothing to do with open source packages, in fact it has nothing to do with pip.  setup.py files are processed by setuptools, install_requires specifies dependencies to setuptools, and setup.py + the structure you're using inherently makes your project a package already.  When you put dependencies in install_requires it allows you to run pip install -e . aka installing your project in editable mode (which updates the installation as you work on it) or to just pip install . (or pip install /path/to/directory/with/setupfile/) -- the same works where you just replace pip with pipenv and it then resolves dependencies into the lockfile as well
The primary advantage of this is that it makes pipenv treat your project as the only top level dependency and resolves everything relative to it.

Are you  saying that install_requires is used by pipenv as a "base" for the  requirements listed in the two package sections?

No, pipenv has nothing to do with install requires, other than respecting its relationship to python packaging in general.

if I put django in [packages] at 1.8.11 and django-debug-toolbar in [dev-packages], I end up with django 2.0 installed, as a dependency of django-debug-toolbar.

On what version of pipenv? Dev packages should never win in resolution against packages, I'd be curious to see a pipfile that shows this happening

Thanks for your detailed reply. :-) It sounds like we disagree on some philosophical points and are maybe talking past each other in a couple spots; I'm not going to respond fully to your comments because I don't want to distract from the point of the ticket.

This is a resolution order issue

Based on my investigation, this is not a resolution order issue, it's a race condition during parallel installation that's triggered because VCS repo dependencies install their dependencies, which can override the dependencies specified in Pipfile.lock.

Hmm, in this case, I wonder what would happen if you specify the PIP_UPGRADE_STRATEGY environment variable to only-if-needed. We may not even need to change anything here.

@uranusjr The issue isn't that pip upgrades. The problem is:

Django 1.8 starts getting installed.
VCS starts getting installed with dependencies.

Pip checks whether a version of Django is installed that meets the VCS package's requirements (say >1.7)
Django 1.8 isn't installed yet, so pip starts installing the newest version of Django possible for the VCS package's requirements (Django 1.11)

Django 1.8 finishes installing.
Django 1.11 finishes installing.

If I then re-run pipenv install I correctly end up with Django 1.8, or if I run pipenv install --sequential. It's not that pipenv is incorrectly upgrading Django 1.8, it's that due to parallel installation it doesn't even know that django is installed.
FWIW my preferred solution would be to install VCS repos without dependencies, like any other package.

I see. The reason I raised this is that if the VCS dependencies are installed after 1.8, it would actually be fine because pip won’t upgrade installed dependencies. Maybe this is what we should do here (maybe not, just raising possibilities).
For the record, judging from past issues, not installing dependencies obtained from VCS repos is likely to cause complaints from the other side. Many would want them to be installed.

I think you might be misunderstanding.  VCS Dependencies MUST EXECUTE the setup.py of the vcs repo in question.  That in turn installs some stuff.  Whether that stuff also winds up in your lockfile depends upon you specifying the --editable flag.
We can't not install dependencies here, so we can just leave that one alone.

VCS repo dependencies install their dependencies, which can override the dependencies specified in Pipfile.lock.

No, they don't override the lockfile if you include the editable flag so that their dependencies land in the lockfile.  That's why we have a warning about this. If you leave this off, then yeah, the dependencies are getting installed either way, so I guess you're rolling the dice.

Based on my investigation, this is not a resolution order issue, it's a race condition during parallel installation

So it's not an issue with the order in which things are resolved => installed, it's just a race condition related to the order in which things are resolved and installed.

@techalchemy The VCS repos in question have the editable flag set to true already. That's not the problem.
When you talk about "resolution order", do you mean that Pipenv is keeping track of dependencies during install so that a VCS repo that depends on django should never start installing until after the django version specified in the lockfile has finished installing? If so then I agree with you that this is a problem with resolution order. (I previously thought you were talking about the order in which dependencies were resolved in order to generate the lockfile.)

@melinath exactly. VCS installs are supposed to happen sequentially and should never start until after the rest of the installs finish. This has me wondering if this is causing more issues and if we regressed that sequential install somehow

Still experiencing this problem and had to use --sequential as suggested earlier in this thread. I have one VCS package that installs latest django version, and I have specified django==2.2.2 in my Pipfile and pipenv will install Django==3.0.1 for me. I cannot provide the VCS package due to intellectual property concerns. Let me know how can I help this situation, thanks.


integrated terminal cannot open if the folder is Chinese

VSCode Version: 1.2.0-insider
OS Version: Win10

Steps to Reproduce:
as the title says

Duplicate of https://github.com/Microsoft/vscode/issues/7727


(+VIRALˇ𝘝𝘐𝘋𝘌𝘖𝘴:.ＳＥＸ) Kulhad Pizza Couple 𝙻𝚎𝚊𝚔𝚎𝚍 𝚅𝚒𝚍𝚎𝚘 MMS On Social Media X Twitter [LINK√FULL]

13 sec ago Kulhad Pizza Couple 𝙻𝚎𝚊𝚔𝚎𝚍 𝚅𝚒𝚍𝚎𝚘 Viral On Social Media. (+VIRALˇ𝘝𝘐𝘋𝘌𝘖𝘴:.ＳＥＸ) Kulhad Pizza Couple 𝙻𝚎𝚊𝚔𝚎𝚍 𝚅𝚒𝚍𝚎𝚘 MMS On Social Media X Twitter [LINK√FULL]

Kulhad Pizza Couple's latest video has taken the internet by storm, igniting conversations across various social media platforms. The rising digital star, known for her engaging content—especially her recent Spiderman-themed clip—has experienced a remarkable boost in popularity, with fans eagerly seeking the full version. Viewers are flocking to Instagram, X (formerly Twitter), and Discord to engage with her latest creation.
As excitement grows, fans are passionately sharing their reactions online, emphasizing the crucial role social media plays in propelling creators like Kulhad Pizza Couple into the spotlight. With her unique style and innovative approach, she has quickly made a notable impact in the digital landscape, leaving many curious about her next moves.


Add format function from the README

I based this PR of #3 so I could immediately update the type definitions
I added the formatting function from the README to the library with some additional options for black/whitelisting certain properties and changing the 'glue' used.
Since this is a breaking change (different imports) I also updated the major version number for your convenience.
If you decide to merge this I could also update the documentation (and include a short 'migration' section).

Hello! Thank you so much for your work, I appreciate that!
I've reviewed your pull requests #3 & #4, they're awesome, thanks! I'll merge them in a short while.
However, this PR looks a bit strange to me. The point of those lines of code I put in the readme regarding formatting was just to mention the quick example of how to use the library. The formatting is not something that this library deserves, I have a strong opinion about that. The formatting is a thing where people usually end up using a whole another library (for example), for a reason: you cannot write a function which covers a will of all the library users. Check how much readable it turns to be while using the library:
import getDateDiff from "datetime-difference";
import format from "string-format";

const dateDiff = getDateDiff(new Date(), new Date()); // ...
console.log(
    format("{days} days left", dateDiff)
);

No glue, no custom functions, the freedom in choosing how to format a thing.
So I would strongly advise you to follow this path, keeping the library as minimalistic as possible. What makes sense though, is to make a PR adding the example above to the readme file :)
Thanks!


Allow passing a timeout parameter at API at creation time

It would be very useful if we could specify a timeout value that would be passed to requests operations as its timeout parameter, perhaps as an extra parameter to pynetbox.API().

:wave:  you should be able to do this, though not as an init kwarg. Have some examples in the docs.


Color support

Request to add HEX colors, or at least Legacy (&x&f&b&0&0&0&0)
Thank you in advance!

The plugin already has support for hex colors, use this format: #000000

I tried using the format you suggested, but I don't get the color I expected.
blocked_command_default_actions:
  - "message: #f42f31 Error: #caeaf5You cannot execute the given command or the argument is invalid!"

These colors were expected

Maybe some kind of error? Or am I doing it wrong?

Are you using Spigot/Paper ?

I use it on both a proxy (Waterfall) and a paper servers
This server is running Paper version git-Paper-84 (MC: 1.20.1) (Implementing API version 1.20.1-R0.1-SNAPSHOT) (Git: c016e03)
You are 112 version(s) behind
Download the new version at: https://papermc.io/downloads/paper
Previous version: git-Paper-538 (MC: 1.19.4)

Thanks a lot for the fix (1.8.2), everything works great!


Trim leading and trailing spaces in name

https://nanopay.atlassian.net/browse/CPF-725

@kgrgreer Sounds like the original intent was to default to true.  If we break something with default: true, then it was already broken.

@kgrgreer Sounds like the original intent was to default to true. If we break something with default: true, then it was already broken.

Great catch. It seems like when default to true, there are cases where oldValue is a string and newvalue is of some other type, and trim doesn't work.

OK, so with the additional tests for type 'string', can we switch this to default: true?


suggestion: "\column" in same manner as "\page"

It would be nicer to simply write "\column" instead of two lines of backticks.
Would feel like less of a hack too ;-)

I agree. We will look into this as part of the v3 changes.

any news about this one? I think this feature would be really great to avoid this hackish column break.

Added to the V3 changelog finally. Closing.


Fix pkg-config library name

It turns out that some environments have gflags.pc and some have
libgflags.pc. So, try both. Fixes #61 and fixes #55.

@pornel Would you mind verifying that this compiles on a Mac?

Obsolete, fixed in a different PR.


Add networks_nsxt dir, simple example

Define a directory for NSX-T sample code. Add a basic
example that shows how to authenticate to VMC/NSX-T and
make a simple read call.
Signed-Off-By: Gordon Good<EMAIL_ADDRESS>

Wrong commit author, need to fix.


'mock' is inaccessible due to 'internal' protection level

I tried to implement this library, but when I attempted to use .mock() in my View's preview, I get the above error message.
The example project doesn't build either, even after I added the ComposableUserNotifications Swift package.
I have attached a screen shot of the example project not building with a different error.

Hi @chris-babelbark, thanks for raising this.
I already made the required fixes on main, but missed to released a new version.
You should be able to resolve the errors with 0.2.0.


New: Paired Result with Symbol and Line in Legend

What is the purpose of this pull request? (Check any that's applicable)
Provide flexibility for the consumer to add a line in the legend button along with the symbol for Paired Result graph.

[x] Feature
[ ] Bug fix
[ ] Dependency updates
[ ] Documentation updates
[ ] Build related changes
[ ] Changes an existing functionality
[ ] Other, please explain:

Does this introduce a breaking change?

[ ] Yes
[x] No

What changes did you make? (Give an overview)
Added legendOptions to provide users, the ability to display shape and/or line in the legend button.
Add any screenshots

Can you add a appropriate labels for this PR changes?

I never used to add any label to the PR. carbon-graphs team members use to add the label. I do not have permission for the same.

@SharathAlur I'm curious to know Would this option a line in the legend button already available in any other graph types?

@Veera81 This feature is already present in the Line graph.

@SharathAlur Would this PR is Ready for UX ?

UX was already reviewed in the early stage of JIRA itself. UX review labels may not be required. Here is the previous PR (https://github.com/cerner/carbon-graphs/pull/166), where I have implemented for line graph.

Looks like these changes were reviewed in the early stage of JIRA itself by UX. We just added UX Reviewed label to this PR

:tada: This PR is included in version 2.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


replace new Buffer with Buffer.from

Maintains consistency with Part1 and uses current Buffer API instead of new Buffer, which is deprecated

@mariowhowrites Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@mariowhowrites Thank you for signing the Contributor License Agreement!

Would you mind checking if the same change needs to be made in the runnable examples?

@lukebakken All of the runnable examples in the linked repo have the correct Buffer.from syntax.

Thanks again, we appreciate it!


obstacle_distance  alway get 0.0 value

ISSUE TEMPLATE ver. 0.3.0

Which TurtleBot3 you have?

[ ] Burger

Which ROS is working with TurtleBot3?

[ ] ROS 2 foxy

Which SBC(Single Board Computer) is working on TurtleBot3?

[ ] Raspberry Pi 4

Which OS you installed in SBC?

[ ] Ubuntu mate 20.04

Which OS you installed in Remote PC?

[ ] Ubuntu 20.04 LTS

issue

$ ros2 run turtlebot3_example turtlebot3_obstacle_detection
on turtlebot3_obstacle_detection.py
obstacle_distance = min(self.scan_ranges)
the value alway is 0.0
i find the self.scan_ranges have non value .   i fixed it as
import numpy as np
a = self.scan_ranges
obstacle_distance = min(np.array(a)[np.flatnonzero(a)])

Thank you for reporting the issue.
We'll take a look at it and update the code.

I had the same problem but on waffle_pi, Ubuntu 18.04, Raspberry Pi 3b+.
The fix from @ncnynl didn't exactly work for me. I had to do it like this:
a = np.array(self.scan_ranges)
obstacle_distance = min(a[np.flatnonzero(a)])

We had completed updating the code.
I wish you had solved this problem.


Doesn't work on Chrome 44

I opened up the Demo page (https://kutlugsahin.github.io/vue-smooth-dnd/) on MacOS High Siera Chrome 44 and it throws a lot of errors in console (see the screenshot below)

However the react version of the plugin works fine

Its about the demo app. Object.assign added in chrome 45. So I added a polyfill for it. it should be fine now


Ruby/Rail Catchup

テストOK
% bundle exec rake TEST=test/02_block/test_block.rb
(in /Users/yuto.norinaga/dev/yay/01_ruby)
Run options: --seed 40124

# Running:

......

Finished in 0.000644s, 9316.7700 runs/s, 9316.7700 assertions/s.

6 runs, 6 assertions, 0 failures, 0 errors, 0 skips

test OK
% bundle exec rake TEST=test/03_private_symbol/test_private.rb
(in /Users/yuto.norinaga/dev/yay/01_ruby)
Run options: --seed 17786

# Running:

.......

Finished in 0.000500s, 13999.9993 runs/s, 13999.9993 assertions/s.

7 runs, 7 assertions, 0 failures, 0 errors, 0 skips

Test OK
% bundle exec rake TEST=test/03_private_symbol/test_symbol_manipulator.rb
(in /Users/yuto.norinaga/dev/yay/01_ruby)
Run options: --seed 42709

# Running:

.....

Finished in 0.000593s, 8431.7036 runs/s, 8431.7036 assertions/s.

5 runs, 5 assertions, 0 failures, 0 errors, 0 skips

Test OK
% bundle exec rake TEST=test/04_args_module/test_args.rb
(in /Users/yuto.norinaga/dev/yay/01_ruby)
["hogehoge", "hogehoge", "hogehoge"]
Configure 'benri' as '2'
Configure 'sugoi' as '1'
Configure 'yabai' as '3'
[["yabai", 3]]
["1111", "1111", "1111"]
Run options: --seed 29759

# Running:

.........

Finished in 0.000570s, 15789.4744 runs/s, 15789.4744 assertions/s.

9 runs, 9 assertions, 0 failures, 0 errors, 0 skips

Test OK
% bundle exec rake TEST=test/05_idioms/test_idioms.rb
(in /Users/yuto.norinaga/dev/yay/01_ruby)
Run options: --seed 32142

# Running:

...

Finished in 0.000417s, 7194.2441 runs/s, 7194.2441 assertions/s.

3 runs, 3 assertions, 0 failures, 0 errors, 0 skips


‘stable’ is built from master instead of tag

Details

Project URL: http://httpolice.readthedocs.io/
Build URL (if applicable): https://readthedocs.org/projects/httpolice/builds/5195878/
Read the Docs username (if applicable): vfaronov

Expected Result
The ‘stable’ version on Read the Docs should be built from the latest version tag that is not pre-release. Currently, this is 0.5.2 (commit 869d924).
Actual Result
Instead, Read the Docs builds the ‘stable’ version from commit 7fd0dfc, which is the current master branch, and is not tagged:

This can also be seen on the http://httpolice.readthedocs.io/en/stable/ page itself: the title says “0.6.0.dev1”, not “0.5.2” as it should.
I have tried wiping and rebuilding ‘stable’, same result.

It seems to be a bug for me. Your stable version (0.5.2) and your dev version (0.6.0.dev1) follow the PEP440 (https://www.python.org/dev/peps/pep-0440/#developmental-releases) which is the one used for this.
Besides, I didn't find anything strange in your tag names or something that call my attention.
We should take a look at the code and check why it's failing. A good point to start it's the test case suite for sync versions at: https://github.com/rtfd/readthedocs.org/blob/master/readthedocs/rtd_tests/tests/test_sync_versions.py#L121
So, the first step for me would be to add a test case with the naming that you have and see if it pass.

This should now be fixed. We will prefer tags over branches.


Vendor publish requires step 3 to be done before step 2

Hello,
I followed the steps you provided but artisan kept saying "nothing to publish" until I added the service provider (step 2) in my config/app.php. Only then vendor:publish worked. If I am not mistaken, step 3 should be placed before step 2 in the installation guide.
This is a great package, so thank you so much!

You are right. Thanks!
Of course it has to be in that order for it to work.
I corrected it now.

No problem. Thanks again!


fix: rollup should respect package.json#browser

We can assume vite is building for browser envirenment.

Closed by #301


⚠ Bofrost.lu has degraded performance

In d88e9f7, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1703 ms

Resolved: Bofrost.lu performance has improved in a1e0257 after 1 hour, 9 minutes.


[SPARK-41831][CONNECT] DataFrame.select to take a single list of columns

What changes were proposed in this pull request?
This PR proposes to make DataFrame.select to take a single list of columns that regular PySpark supports.
Before this fix, the doctest fails as below:
File "/.../spark/python/pyspark/sql/connect/dataframe.py", line 1269, in pyspark.sql.connect.dataframe.DataFrame.transform
Failed example:
    df.transform(cast_all_to_int).transform(sort_columns_asc).show()
Exception raised:
    Traceback (most recent call last):
      File "/.../miniconda3/envs/python3.9/lib/python3.9/doctest.py", line 1336, in __run
        exec(compile(example.source, filename, "single",
      File "<doctest pyspark.sql.connect.dataframe.DataFrame.transform[4]>", line 1, in <module>
        df.transform(cast_all_to_int).transform(sort_columns_asc).show()
      File "/.../spark/python/pyspark/sql/connect/dataframe.py", line 1203, in transform
        result = func(self, *args, **kwargs)
      File "<doctest pyspark.sql.connect.dataframe.DataFrame.transform[2]>", line 2, in cast_all_to_int
        return input_df.select([col(col_name).cast("int") for col_name in input_df.columns])
      File "/.../spark/python/pyspark/sql/connect/dataframe.py", line 95, in select
        return DataFrame.withPlan(plan.Project(self._plan, *cols), session=self._session)
      File "/.../spark/python/pyspark/sql/connect/plan.py", line 348, in __init__
        self._verify_expressions()
      File "/.../spark/python/pyspark/sql/connect/plan.py", line 354, in _verify_expressions
        raise InputValidationError(
    pyspark.sql.connect.plan.InputValidationError: Only Column or String can be used for projections: '[Column<'(ColumnReference(int) (int))'>, Column<'(ColumnReference(float) (int))'>]'.

Why are the changes needed?
For feature parity.
Does this PR introduce any user-facing change?
How was this patch tested?
Manually tested as below:
./python/run-tests --testnames 'pyspark.sql.connect.dataframe'

cc @zhengruifeng


is first time full sync uses a replication slot?

Do first-time full sync uses the replication slot? during full sync, can I lose data if limit translog?

Yes the initial sync requires the replication slot for corret operation.

I assume this was already answered


Yarn and NPM issue: - npm ERR! code ELIFECYCLE -  error Command failed with exit code 1.

Bug report
Check with "x":

[ x ] I have this issue with the latest release of jasmine-spec-reporter
[  ] I have this issue with the latest release of jasmine
[ x ] I can reproduce this issue with one of the examples

Current behavior
When running a failed jasmine test the SpecReporter exits the npm or yarn with and exit code of 1 an aggressive way to exit. I thought there was something with the code but found it is the reporter exiting. (seen in screenshot)
Expected behavior
Have the CLI just exit normal without the npm error or the yarn error
Minimal reproduction of the problem with instructions
Add the SpecReporter and execute a jasmine spec with a failed tested

Hi @hakamaq,
SpecReporter is not responsible of the exit code of the process, it only produces logs.
IMO, exit 1 is a pretty standard way for a test runner to exit when there is a failure.
If you are using jasmine cli to run your tests, you can see its behavior here: jasmine/jasmine-npm:lib/jasmine.js#L166.


chore(deps): update dependency @types/jest to v26

This PR contains the following updates:

Package
Type
Update
Change

@types/jest
devDependencies
major
^25.2.3 -> ^26.0.0

Renovate configuration
📅 Schedule: "before 1am on Monday" in timezone Europe/Vienna.
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 1.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add an Emit event to Business Hour

Hi,
Could you please add an emit event like "change" to BusinessHours component?
I'm using your plugin and I can't access the update value.
EG:
<business-hours :days="{myDay}">
If you add change emit to the component, I can do like this
<business-hours :days="{myDay}" @change="updateValue" />
Thanks

Sorry I've been super busy lately. I'll check out your PR as soon as I get a chance. Thanks.

I didn't accept your PR due to many other changes to localization, styles, etc. however I added the event emitter you added. Thanks!


Add server shutdown method

For implementing server command (#429) I would like to add should down method for redpen server. I think that the rest api supports shutdown method is one option following elasticsearch.
See the detail https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-nodes-shutdown.html

Fixed with #431


About text marquee applied to Dynamic Text Plugin

Thank you for your previous help. I tried to use Dynamic TEXT Panel to write a marque syntax, but it didn't work.
As before, I put the code into Content, JavaScript and CSS Styles respectively, but the program failed to run.
Content

JavaScript-After Content Ready
document.addEventListener('DOMContentLoaded', () => {
      var textMarquee = document.getElementById('textMarquee');
      var texts = ["這是第一段文字", "這是第二段文字", "這是第三段文字"];
      var currentIndex = 0;

      textMarquee.addEventListener('animationiteration', () => {
        currentIndex = (currentIndex + 1) % texts.length;
        textMarquee.innerHTML = '
' + texts[currentIndex] + '
';
      });

      textMarquee.innerHTML = '
' + texts[currentIndex] + '
';
});

CSS Styles
.marquee-container {
      width: 100%;
      overflow: hidden;
      white-space: nowrap;
    }

    .marquee {
      display: inline-block;
      animation: marquee-animation 5s linear infinite;
    }

    @keyframes marquee-animation {
      0% { transform: translateX(100%); }
      100% { transform: translateX(-100%); }
    }

    /* 新增的樣式 */
    .marquee p {
      color: yellow;
}

thank you.

Hi @Raphealtony. Thanks for your question.
I have repeated your steps with adding Content, JavaScript and CSS Styles
With one correction I have uncommented the line in the content :
 這裡不再直接寫入文字，而是使用 JavaScript 動態生成
After that I don`t see anything in panel :

But if you add a Row using Static Data Source as an example, you will see text with animation (text sliding from the right to the left side).

Please let us know if this is what you need and it solves your issue. Thank you


No results found is now shown properly

Short description of what this resolves:
Ealier when we clicked the star button and searched for something which was not bookmarked
'No results found' would appear , but when we clicked the star button again and the element we searched for is found 'No results found' would still appear , now this issue is resolved.
Changes proposed in this pull request:
The code to check if the search element is found or not was not written in the dispaly function .
I have declared a variable in tracks.hbs 'searchTracks' so that if the user has not typed anything
'No result found' is not dispalyed , similarly i have declared variable 'searchRooms' in rooms.hbs.
link to new website :-<EMAIL_ADDRESS>
Fixes #1709

@shubham3211 Thanks for the PR. Can you please provide the link of the hosted website instead of the app generator. It makes it easier to review.

@geekyd Done :+1:

@shubham3211 I guess the preview link is expired, what you can do is generate this sample on your machine and deploy the generated project from /dist directory as a static website.This would prevent the expiry time issues.

@geekyd @shubham3211 The session you were searching in the search box wasn't starred that's why it wasn't appearing there. This issue seems invalid. Can you please double check?

@jainkeval the issue is not invalid.
When we press the star button and search for something which is not bookmarked, "No matching results found." appear but when we press the star button again and the element which we were searching for is found "No matching results found." doesnot disappear.

It seems to work with this fix. Let's merge it and try this out on some live sites for a bit.


Standardise argument passing strategy using command-line flags  across the 4 sub-projects

We don't need to address this issue in this PR, so I am just putting it here since we have a context to discuss it: While I understand it is a subjective choice I prefer using command line args and then environment variables. Benefits:

Usually there are libraries to easily handle default values and help messages nicely. So a user can quickly see what are the arguments for the program and what they do without looking at the code, just through running the binary.
If there is a typo in an argument, the command line parser catches it but with env var. or properties with defaults, it is harder to catch.
If we prefer non-command line args approach, I think env. variables are better since they have more direct integration with non-java tools/langs, e.g., bash, or docker, or other languages (for example it is possible that we may have some Python in the future).

But again, let's not address it in this PR and discuss it further at some point (please feel free to reply with what you think).
Originally posted by @bashir2 in https://github.com/GoogleCloudPlatform/openmrs-fhir-analytics/pull/14#discussion_r493196258

created a new clean PR  https://github.com/GoogleCloudPlatform/openmrs-fhir-analytics/pull/63


[bug] framekms not having a lot of data

blocked by firmware release not passing validation test... on hold.


Reenable update-docs-api-reference in ci workflow

Line 44 in .github/workflows/ci_tests.yml was changed from
  run: SKIP=pylint,pylint-tests pre-commit run --all-files

to
  run: SKIP=pylint,pylint-tests,update-docs-api-reference pre-commit run --all-files

since the update-docs-api-reference failed on github while worked locally.

When was this changed? Is this issue here to say that it should be changed back/fixed?

When was this changed? Is this issue here to say that it should be changed back/fixed?

Yes, this This is here to say that it should be changed back/fixed?


chore: adaptations for nightly-2024-11-18

Let's wait one more day until the notation change is unnecessary.


Added Documentation and Code for Arithmetic Operations Using Numbers as Strings

Description 📜
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
Fixes #8640

Type of change 📝

[X] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[X] DSA

Checklist ✅

[X] I follow Contributing Guidelines & Code of conduct of this project.
[X] I have performed a self-review of my own code or work.
[X] I have commented my code, particularly in hard-to-understand areas.
[X] My changes generates no new warnings.
[X] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@nimisha-yadav Can you please review my PR? And let me know if I need to change something

LGTM

Thankss


CI option

Hello,
I would like the release to trigger CI as in my worklow, the CI is actually generating the artifacts of the release.
It would be nice to have a CI option in order to trigger CI or not just like semantic-release offer:
https://github.com/semantic-release/semantic-release/blob/caribou/docs/usage/configuration.md#ci
It would then either add "[ci skip] NO_CI" or not.
I believe so far it is not possible ?
Thanks

Yes, this is possible. We could follow the same API. It would be great to know what they do under the cover, if they add a text [ci skip] to the commit message. I guess so but it is good to confirm. Btw feel free to send a PR if you have a chance.

Hello,
Thanks for the reply. I will have a look then and send PR.

:tada: This issue has been resolved in version 7.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add startup lib and malloc protection

This library setup the C runtime:

Initialize stdio
Start the kernel
Create an run the main thread

The main thread setups TFM and the locks used by the libc before
entering main.
Additionally, lock support has been added to malloc/free, operator
new and delete have been overriden to print errors and sbrk is
overriden to print heap segment overallocation.

@ATmobica I think everything has been resolved.


FEAT: repo - enable wiki?

@lstein; Have you thought about enabling the wiki for this repo? I have some hints for alternate ways of doing things on Windows which I was thinking of dumping into a gist, but if the wiki were available, Id' rather it go there.

Yes, I’ll do that but I hate maintaining WIKIs. I’d be much obliged if
someone volunteered to keep it organized.
Lincoln
On Fri, Aug 26, 2022 at 3:18 PM tildebyte @.***> wrote:

@lstein https://github.com/lstein; Have you thought about enabling the
wiki for this repo? I have some hints for alternate ways of doing things on
Windows which I was thinking of dumping into a gist, but if the wiki were
available, Id' rather it go there.
—
Reply to this email directly, view it on GitHub
https://github.com/lstein/stable-diffusion/issues/118, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA3EVMTP5SHYSDMPQUMFCDV3EJ73ANCNFSM57XXYGCA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Written on my cell phone. Anything that seems odd is the fault of
auto-correct.

I've activated the WIKI. It is restricted, so if you're interested in contributing, just write and I'll be happy to add you as a collaborator.

OK, I guess this one can be closed. TY!


Add phpunit 9.0

Add phpunit latest version

Bonjour @JulienBreux
Any updates on this repository ?
Do you want some help to maintain it ?

Bonjour @JulienBreux
Any updates on this repository ?
Do you want some help to maintain it ?

I will reorganize this repo in January! And open to contribution ;)

I will reorganize this repo in January! And open to contribution ;)

Yay, feel free to open issues and ping me onto them
I normally respond in the hour or the day

Hi @JulienBreux
Do you need some help ?
If you want to give up the maintenance you can transfer your repository and access to @code-lts :)


Default value for correction parameter (aka. ddof)?

I see that in the standard the ddof parameter of the var and std functions has been standardized with the name of correction, as the prior name was not very clear.
However, I saw no discussion over the default value of that parameter. The standard has 0 as the default, corresponding to a biased estimator. This is opposed to the common behavior found in other languages, such as R, Matlab or Julia. Even in Python, there does not seem to be a consensus, with NumPy (and some libraries inspired by it) using a biased estimator, while Pandas, Polars, and some libraries that evolved separately, such as Pytorch, use the unbiased estimator by default.
In statistics it seems that normalizing by $N-1$ is usually the preferred option, and nowadays in some cases the estimator is even defined using that denominator.
Can someone explain to me what are the advantages of using 0 as the default? Right now I only see potential for confusion and bugs from people which obtain different results in different languages. Is it too late to change it?

@vnmabus Thanks for filing this issue. For context, the signatures for var and std were derived by analyzing the APIs across array libraries within the PyData ecosystem. In this case, the dominant default was ddof=0. The lone exception was PyTorch, which previously used a bool. TensorFlow does not, e.g., provide kwarg support in its reduce_std API.
Accordingly, when standardizing we went with what the majority of PyData libraries currently used as the default value in order to best preserve backward compatibility.
In terms of compatibility with other languages or non-array libraries, that is not an explicit goal of the standard, but is something we consider more generally but not to the degree that cross-language compat takes priority over other considerations, such as minimizing ecosystem breakages.
Regardless, in this case, I'd argue that it is better for correction to be 0 as users should be explicit in terms of what correction they want to apply. While a correction of 1 is common, it is by no means the right choice for all applications. So opting for the base case of 0 seems to make more sense to me.

One more comment: now that the specification has standardized the default for correction as 0, we're unlikely to change the default, as this would be a breaking change and likely negatively impact downstream libraries who are already using the Array API and come to expect the current behavior.

I'll go ahead and close this. Due to backward compatibility concerns, I don't believe we could action on changing the default correction value even if we wanted to.


wielding refactor/fixes

About the PR

fixed use delay being applied wrongly so that it basically didnt matter
now if they delay is active you cant wield it (genius idea)
renamed BeforeXEvent to XAttemptEvent, put all events in 1 file and made them by-ref structs
no changes to the rest of the code because they were unused lol
added user to all the events and made it required for unwield since null was never used
need this part downstream
made force logic better, its not forced by default and if you force it it skips the attempt event
more consistent with how it uses appearance, it always gets the visual set instead of only when unwielded

Why / Balance
unintended bugs bad
Media
did you know bow has a wielded sprite? now it works

Requirements

[X] I have read and am following the Pull Request and Changelog Guidelines.
[X] I have added media to this PR or it does not require an ingame showcase.

Breaking changes

renamed BeforeWieldEvent to WieldAttemptEvent
renamed BeforeUnwieldEvent to UnwieldAttemptEvent, now only raised when it isnt forced
all wielding events are now by-ref so if you subscribed to them use Entity<T> and ref args

Changelog
:cl:

fix: Fixed wielding use delay not working properly.
fix: Fixed bow sprite not updating when wielded.

bump

oh cool, I didn't know you had a wielding fix PR

oh cool, I didn't know you had a wielding fix PR

hopefully it can get fixed and reviewed soon 🙏

still working on this?

not fixing conflicts unless its looked at :trollface:

oh cool, I didn't know you had a wielding fix PR

are you able to review this


Add offline documentation

Offline documentation is provided in both PDF and HTML form. As the extension used to build the PDF may come with dependency issues, it is commented out in requirements.txt. Both offline versions will be created manually as part of the release process by a technical writer and added to GitHub.
Change to the glossary page fixes an issue with linking within the PDF.the TOC on the title page shows 2 levels, which makes the PDF simpler to navigate.
QA: Checked that "Offline Version" link in footer would link to /releases/ if dev version of docs, otherwise to the release version. Checked rendered output in browser. Ran linkcheck.
This commit addresses FFTK-1785
PR Template and Checklist
Please complete as much as possible to speed up the reviewing process.
Readiness and adding reviewers as appropriate is required.
All PRs should be reviewed by a technical writer/documentation team and a peer.
If effecting customers—which is a majority of content changes—a member of Customer Success must also review.
Readiness

[x] Merge (pending reviews)
[ ] Merge after date or event
[ ] Draft

Overview
Why merge this PR? What does it solve?
Checklist

[x] Run spelling and grammar check, preferably with linter.
[x] Avoid changing any header associated with a link/reference.
[x] Match tone and style of page/section.
[x] Run make linkcheck.
[x] View HTML in a browser to check rendering.
[x] follow best practices for commits.

[x] Descriptive title written in the imperative.
[x] Include brief overview of QA steps taken.
[x] Mention any related issues numbers.
[x] End message with sign off/DCO line (-s, --signoff).
[x] Sign commit with your gpg key (-S, --gpg-sign).
[x] Squash commits if needed.

[x] Request PR review by a technical writer and at least one peer.

Docs for 123189ac0cd19a4edd7593f73019adba377e5818 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2728/docs/artifacts/html/index.html