Merge develop into staging, 2024-Feb-01 edition

This is mostly so we can deploy the new concordances API as soon as possible (also so we can show Jan what it looks like on Staging in advance of it going to Production).

Staging server is updated! All tests are passing, and the concordances API is working as expected! Going to wait until tomorrow, when we can confirm that cron ran update_cached_concordances, to let Jan know.

I've just confirmed that our concordances file is up-to-date! I just emailed Jan to give him a link to our documentation and let him examine the output of the API.


Move texture reader attributes into separate Texture object

This pull request seperates the reading and the object/business logic of the Texture2D reader into 2 files.

Makes the code easier to understand (reader does reading, object does business logic) and also because some other readers in the future might need objects for cleaner code, why not do this one too?

Did you re-test?

oops did i break something


Version 0.5.11

Landed in https://github.com/metarhia/do/commit/11cf574656877dd337a8a85c59fc93db0f8e950b


RestyResolver for nested paths

Fixes #206.
There has been some discussion about fixing RestyResolver to work with nested paths. I've bumped into this issue multiple times trying to create a new API with Connexion.
After looking over the regex, it seems that parsing would become extremely complicated. Going the more basic route, I feel str.split() can cover most of the situations and using conditionals can be more maintainable and easier to read for newcomers.
Hopefully the new test cases can clearly demonstrate what is handled by this code change. Do let me know if this is not the intended behaviour or if something must be changed. Feel free to take whichever parts of the code or test cases that would be beneficial to the project.
Changes proposed in this pull request:

Support nested paths
Define a custom module name separator

Hey @e4r7hbug is this issue something you're still interested in working on, or can I close it out?
There have been a lot of changes to connexion since June.

Sorry for the late reply! Since it sounds like I need to spend some time getting myself updated on the latest changes, I agree on closing this for now. I'll try opening another Pull Request in the future if it's still needed. Thanks for checking in!

I am very interested in this happening! Go go go!


Updated provider.tf.j2 as per update on terraform

Removed version = "~>2.0" from the provider block. It has been added under main.tf.j2 inside the required providers block.

Added the changes into anxious-bing-patch-2


Error when using [input] types and variables with a mutation

Bug description
When creating a mutation to insert a large, multi-nested payload via a variable, I use an input type of [product_insert_input] which Hasura defines. Artemis cannot generate types for this (I am not sure types are needed as they are already defined) and the generated code has an error: The name 'product_insert_input' isn't a type so it can't be used as a type argument. Try correcting the name to an existing type, or defining a type named 'product_insert_input'.
I can see the input type [product_insert_input] appears to be defined correctly in the gql schema.
"""
input type for inserting data into table "product"
"""
input product_insert_input {
  barcode: String
  brand: brand_obj_rel_insert_input
  brandId: Int
  countryAlpha2Packaged: String
  countryAlpha2ProductOf: String
  countryPackaged: country_obj_rel_insert_input
  countryProductOf: country_obj_rel_insert_input
  createdAt: timestamptz
  createdBy: String
  id: Int
  ingredients: productIngredients_arr_rel_insert_input
  name: String
  updatedAt: timestamptz
  updatedBy: String
  weightGrams: Int
}

I'll freely admit I could be doing this all the wrong way too! What is the correct way to work with complex nested mutations using variables and have it play nice with Artemis?
Specs
Artemis version: artemis: ^6.2.1-beta.1

build.yaml:
targets:
  $default:
    sources:
      - lib/**
      - lib/graphql/**
    builders:
      artemis:
        options:
          schema_mapping:
            - schema: lib/graphql/schema/koalaroo.schema.graphql
              queries_glob: lib/graphql/data/**/**.graphql
              output: lib/graphql/graphql_api.dart
          scalar_mapping:
            - graphql_type: timestamptz
              custom_parser_import: 'package:koalaroo_app/services/artemis_timeconvert.dart'
              dart_type: DateTime

Artemis output:
https://paste.ubuntu.com/p/Njj385DX4Q/

GraphQL schema:
https://paste.ubuntu.com/p/vQkBzybZZB/

GraphQL query:
mutation addProduct($product: [product_insert_input!]!) {
  insert_product(objects: $product, on_conflict: {constraint: product_pkey, update_columns: barcode}) {
    affected_rows
    returning {
      id
    }
  }
}

variable payload:
{
    "product": {
        "name": "Reflex Ultra White TEST",
        "barcode": "9311995002018",
        "countryAlpha2Packaged": "AU",
        "countryAlpha2ProductOf": "AU",
        "weightGrams": 3000,
      "brandId": 7,
        "ingredients": {
            "data": [
                {
                    "countryAlpha2": "AU",
                    "percentage": 70,
                    "desc": "au TEST demo data"
                },
                {
                    "countryAlpha2": "NZ",
                    "percentage": 30,
                    "desc": "Nz demo data"
                }
            ]
        }
    }
}

I've just seen https://github.com/comigor/artemis/issues/145 - best to close this and follow on that issue :)

Cool, I'll reopen #145 and take a look!


Yarn failure with Drupal 11

With Drupal 11, I am seeing yarn fail at the end of ddev poser with a suggestion to use corepack. Help wanted on adapting to this. I know DDEV did some work to make this easier but work is needed here too, it seems. The error I see happens with latest released DDEV

DDEV automatically detects D11 and enables corepack_enable in that case.
ddev config --update will automatically detect and change.

For now I have removed the yarn call from ddev poser so this issue is moot. I'll close it in a few days.


Current user based index data

Closes #204
On top of @JoshSmith's #207

@npendery
Sorry about this, but it seems we'll have to close the PR without merging. We wanted to mirror the rails api here, but once we took another good look, we concluded it doesn't make sense to do it that way.
Here's what rails does:
if id_params.present?
  user_skills = UserSkill.includes(:skill, :user).where(id: id_params)
elsif current_user.present?
  user_skills = UserSkill.includes(:skill, :user).where(user_id: current_user.id)
else
  user_skills = []
end

To put it in words, if the client provides a list of ids it wants, they get that back. If they don't, then if they are authenticated, they get all of their own records back.
The reality is, they shouldn't need to explicitly fetch their own records. They should get a list of ids with their user payload, and then simply fetch those records using these ids.
If there anything, we might eventually need a user_filterinstead of a current_user_filter, meaning the client would provide a user_id to filter by. For now, though, we can close this and see if there's anything that needs fixing client-side.


Address #1174 & prevent inputToolbar-positioning regression

Track the state of first-responder when the interactive pop gesture begins
Restore the first-responder state when pop gesture ends/cancels
This contains the main idea from PR #1175

Moving "[self jsq_addActionToInteractivePopGestureRecognizer:NO];" to viewDidDisappear

But at the same time maintains the inputToolbar in the right position in the case of a interactive-pop cancel/failure.

Thanks @walsh2000 !

@jessesquires
Long weekend... I just got around to dealing with your notes.
Hopefully this is now in shape :)
:facepunch: :muscle:


dev-doctor - if path to go.mod invalid, look in current directory

Minor annoyance/issue
If $GOPATH is not set, make dev-doctor tries to construct a path to go.mod that may not exist depending on Go configuration, does not check that the path exists, and as a consequence, fails later on.
This extremely mini PR changes dev-doctor to actually validate that the expected path for go.mod exists, and IF it does not, as a last resort, look for go.mod in the current directory (where make is executed from), to support building with Go module-style non-opinionated source root locations.
This won't change behavior for anyone using the existing style, but now it won't break for everyone using contextless/non-global Go source root (e.g. pure Go modules style)
To repro:

Clone cilium repo to an arbitrary location outside of $GOPATH/GOROOT as supported by current Go.
e.g. cd /Host/Source && git clone git@github.com:cilium/cilium.git
Observe failure:

[bleggett@lima-fedora cilium]$ make dev-doctor
go version 2>/dev/null || ( echo "go not found, see https://golang.org/doc/install" ; false )
go version go1.20.2 linux/arm64
go run ./tools/dev-doctor
panic: cannot read go version from go.mod: open /home/bleggett.linux/go/src/github.com/cilium/cilium/go.mod: no such file or directory

goroutine 1 [running]:
main.rootCmdRun(0x39a340?, {0x3d2630?, 0x0?, 0x0?})
        /Host/Source/cilium/tools/dev-doctor/rootcmd.go:62 +0x20d4
github.com/spf13/cobra.(*Command).execute(0x39a340, {0x4000098200, 0x0, 0x0})
        /Host/Source/cilium/vendor/github.com/spf13/cobra/command.go:944 +0x5ac
github.com/spf13/cobra.(*Command).ExecuteC(0x39a340)
        /Host/Source/cilium/vendor/github.com/spf13/cobra/command.go:1068 +0x340
github.com/spf13/cobra.(*Command).Execute(...)
        /Host/Source/cilium/vendor/github.com/spf13/cobra/command.go:992
main.main()
        /Host/Source/cilium/tools/dev-doctor/main.go:13 +0x24
exit status 2
make: *** [Makefile:665: dev-doctor] Error

With current Go+module, it is not required to set $GOPATH, and cloning repos to $GOPATH/src (or $[default_GOPATH]/src if unset) is also not required.
Cilium image builds and other make targets also seem fine with this.
Result with fix

cd ~/Source && git clone git@github.com:cilium/cilium.git
make dev-doctor

[bleggett@lima-fedora cilium]$ make dev-doctor
go version 2>/dev/null || ( echo "go not found, see https://golang.org/doc/install" ; false )
go version go1.20.2 linux/arm64
go run ./tools/dev-doctor
RESULT    CHECK           MESSAGE
warning   os/arch         linux/arm64
ok        uname           Linux lima-fedora 6.2.7-200.fc37.aarch64 #1 SMP PREEMPT_DYNAMIC Fri Mar 17 16:24:22 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux
ok        root-dir        found /Host/Source/cilium
ok        make            found /usr/bin/make, version 4.3
ok        go              found /usr/local/go/bin/go, version 1.20.2
ok        tparse          found /home/bleggett.linux/go/bin/tparse, version 0.12.1
ok        clang           found /usr/bin/clang, version 15.0.7
ok        docker-server   found /usr/bin/docker, version 23.0.1
ok        docker-client   found /usr/bin/docker, version 23.0.1
ok        docker-buildx   found /usr/bin/docker, version 0.10.2
ok        ginkgo          found /home/bleggett.linux/go/bin/ginkgo, version 1.16.5
ok        golangci-lint   found /home/bleggett.linux/go/bin/golangci-lint, version 1.52.2
ok        docker          found /usr/bin/docker, version 23.0.1
ok        helm            found /usr/local/bin/helm, version 3.11.3
ok        llc             found /usr/bin/llc, version 15.0.7
failed    vagrant         exit status 1
info      virtualbox      virtualbox not found in $PATH
info      vboxheadless    vboxheadless not found in $PATH
ok        pip3            found /usr/bin/pip3, version 22.2.2
ok        cfssl           found /home/bleggett.linux/go/bin/cfssl, version dev
ok        cfssljson       found /home/bleggett.linux/go/bin/cfssljson, version dev
ok        docker-group    user bleggett in docker group

CHECK          HINT
vboxheadless   run "VBoxHeadless --help" to diagnose why vboxheadless failed to execute

See https://docs.cilium.io/en/latest/contributing/development/dev_setup/.
exit status 1
make: *** [Makefile:665: dev-doctor] Error 1

Resynced with main, should be gtg


Create Comment Function Inside Post

Description
As a user, I want to comment on a post

A comment can contain hashtag(s)
A hashtag occurrence in a comment is counted in trending hashtags calculation

Tasks

[x] Write unit test for Post model & controller
[x] Create insert comment function in Post model
[x] Create insert comment method in Post controller

Closed with f3448725874e3ebfdab5a44181f97b0f57af05bb


Update index.md

Testing

Hai im trying merge this pull request by accidentally close it on the first try


[Bug Fix]: Correct permission naming from 'UPDATE_APPLICATION' to 'EDIT_APPLICATION'

Description
This PR fixes a bug where the incorrect permission UPDATE_APPLICATION was being used. It has been updated to the correct permission EDIT_APPLICATION to ensure consistent access control across the application.
Related Issue
Closes AGE-539
Changes

Updated permission from UPDATE_APPLICATION to EDIT_APPLICATION in relevant parts of the codebase.

What to QA

Verify that actions requiring the EDIT_APPLICATION permission work correctly and that no access issues are introduced.

@aybruhm can you please sync with @zenUnicorn for QA

I have been able to QA the fix.
The app rename works perfectly.
cc: @mmabrouk @aybruhm


LOI/LRI ACKs MVP

User Story
As a ReportStream ETOR sender I want message confirmation ACKs sent to me following industry standard LOI/LRI specification to ensure the timely delivery of my data
Description/Use Case
A number of pilot partners have asked us if we support ACK messaging and some have even specified if it follows the ACK implementation following the LOI/LRI spec. The CDC has noticed the need as well as wants to support more industry standardization so has asked us as part of their annual goals to implement the ACKs component of the LOI/LRI spec. Eventually they or our sender partners will probably want the full ACK implementation but for now have agreed to an MVP that just implements the Basic Synchronous Accept ACKs for our Submission API following the needs of our ETOR partner Flexion. Their exact requirements are provided in the dev notes.
Risks/Impacts/Considerations
Risks: piloting the MVP will require an engaged partner willing to setup the API connection and debug the response. Currently that partner is Flexion and they seem engaged. They also have to agree with us on the contents of the ACK message and nail down requirements in a timely manner for us to test and launch before the quarter is through.
Dev Notes
Flexion ETOR ACK Requirements: https://cdc.sharepoint.com/:w:/r/teams/OLSS_ETOR_ReportStream/Shared Documents/ReportStream ETOR ACK Requirements.docx?d=we5a9fae68cd24c99a757f027562c1737&csf=1&web=1&e=x3lgDZ
HL7 over HTTP spec: http://v2plus.hl7.org/2021Jan/hl7-over-http.html
Epic's Orders & Results LRI ORM spec documentation: https://cdc.sharepoint.com/:b:/t/ReportStream/EchwA7-zxUFArPsluFSbZnIBJe4O9oYwzGjgvy5vAm-tPQ?e=ZP7ji6
Epic's Orders & Results ELR spec documentation:https://cdc.sharepoint.com/:b:/t/ReportStream/ETXO5yfN0NtGqOOKrbrVMpYBibSFFRj_duOXsi9qfjH76w?e=HsnptB
Acceptance Criteria

[ ] Flexion can send a test order message and gets back a valid HL7 ACK message
[ ] The ACK message contains the MSH and MSA fields outlined in the ETOR ACK Requirements doc

@jsutantio No, unless Flexion has issues and needs changes but that can be a different epic/tickets imo.


Make plugins that use data.json more robust

Plugins that use data.json crap out, for the most part, if it isn't right or isn't there. We should provide a way to make these plugins more robust.

Closed via 7467e1d8b0749c06fdd793fde5e0e1103e9d071f.


fix nbx for vanilla

not printing 'nan's

it also prints 'nan' / 'inf' in a weird way on windows

propose that the min/max is like the atom box, which when = 0 makes it unlimited


ci: revamp release(rc) processes

Description:
Revamp the full release process, and try to make it more robust and easy to use while still being secure at the same time.
Related Issue:
#62
Type of change:
Please delete options that are not relevant.

[x] Other minor changes (workflow, GitHub configs, etc.)

Checklist:

[ ] All code follows the project's coding style and conventions.
[ ] I have performed a self-review of my own code.
[ ] My changes generate no new warnings or errors.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding updates to the documentation.

:tada: This PR is included in version 0.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


any reason not to use partisan?

I was wondering why you were not using partisan for the peer service. Any reason for it?

closing after our yesterday discussion.

Where was the discussion?
On Wed, Feb 13, 2019, 2:53 AM Benoit Chesneau<EMAIL_ADDRESS>wrote:

closing after our yesterday discussion.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/vitorenesduarte/ldb/issues/59#issuecomment-463095472,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACvi6gsn7T-eEYun3W5OYslQH2u12_Lks5vM8R2gaJpZM4a1lHP
.

Twitter messages; here's the summary:
I've implemented this simple peer service for another project and ended up porting it to ldb.
Using partisan was not an option since we wanted to have total control on what we were doing and be able to change/break things as needed.


Async interceptor or authenticator

Is there any way to do interception or authentication of request async? Get password from user, use it to obtain token an then retry the call?

This is a better question for StackOverflow. This tracker is for bug reports with test cases and feature requests only.


Unexpected TypeError: Cannot read property 'apply' of undefined

I'm getting an exception and don't understand why. The sample code is cut down from the original, but the line in question starts let subscription=. This code is within a method so only occurs on the server side.
The failing line within Meteor subscribe():
return Meteor.subscribe.apply(Meteor, [name].concat(args.concat([{...
Here's the exception and traceback:
Exception while invoking method 'someMethod' TypeError: Cannot read property 'apply' of undefined
at subscribe (c:\Build\myapp\node_modules\meteor-rxjs\dist\bundles\index.umd.js:609:36)
at Observable._subscribe (c:\Build\myapp\node_modules\meteor-rxjs\dist\bundles\index.umd.js:628:30)
at ZoneOperator.call (c:\Build\myapp\node_modules\meteor-rxjs\dist\bundles\index.umd.js:695:23)
at Observable.subscribe (c:\Build\myapp\node_modules\rxjs\Observable.js:42:22)

Here's my code within a Meteor method:
	let list = MyCollection.find(aselector);
    let subscription= MeteorObservable.subscribe("publishedList, selector).zone().subscribe( () => {

      list = MyCollection.find(selector);
      let myArray = list.fetch();
      let item: MyItem = myArray.length > 0? myArray[0]: null;
	});

As pointed out in another forum, the issue is that subscribes are not needed in methods. Correcting the code to
let item: MyItem = MyCollection.findOne(selector);
My misunderstanding.


Include Spring Boot sample project

Closing as issue tracking will be done on the cloud-spring-boot repo https://github.com/Kentico/cloud-spring-boot


Fix memleak in the toMap helper function

https://github.com/timsneath/win32/blob/220c807d765518eb7d0216e59c9a13b0bebcfdce/lib/src/winrt/internal/map_helpers.dart#L23-L31
... we can also free the pArray pointer as it's only used when constructing a Map (Line 29, while iterating over to the IKeyValuePair's key and value getters). After that, we don't need pArray at all. Therefore, we can safely free it in a finally block.
Originally posted by @halildurmus in https://github.com/timsneath/win32/issues/563#issuecomment-1279341820

I couldn't figure out from the code where pArray is allocated. Does our code allocate it or just receive memory that WinRT owns?  Is that something that we as the caller are responsible for freeing? https://learn.microsoft.com/en-us/uwp/api/windows.foundation.collections.ivectorview-1.getmany?view=winrt-22621 didn't seem to give me a strong clue that we should be freeing it...


Request Statistics Heading Alignment Issue

Describe the bug
Whilst viewing a given test run in jtlreporter, specifically under the "Request Statistics", it seems the headings are mis-aligned with the actual values below.

Notice how there is a random '0' at the end of this example test run, which should be beneath error rate.
Here is the output of the bzt taurus command correctly showing the percentiles:
+---------------+---------------+
| Percentile, % | Resp. Time, s |
+---------------+---------------+
|           0.0 |         0.159 |
|          50.0 |         0.209 |
|          90.0 |         0.239 |
|          95.0 |         0.256 |
|          99.0 |         0.301 |
|          99.9 |         0.496 |
|         100.0 |         0.496 |
+---------------+---------------+
15:11:55 INFO: Request label stats:
+---------+--------+---------+--------+-------+
| label   | status |    succ | avg_rt | error |
+---------+--------+---------+--------+-------+
| example |   OK   | 100.00% |  0.213 |       |
+---------+--------+---------+--------+-------+

It seems we're missing a median value, as the 50th percentile of 209ms, is now reported under the 90th percentile, and so on hence the misalignment of fields.  This maybe because we include a few additional fields in our jtl csv output:
    csv-jtl-flags:
      bytes: true
      sentBytes: true

To Reproduce
Steps to reproduce the behavior:
Use the following example bzt file to generate a kpi.jtl and then upload to local install of jtlreporter (we're running 4.8.9):
execution:
- hold-for: 120s
  scenario: simple

modules:
  console:
    disable: true
  jmeter:
    gui: false
    properties:
      server.rmi.ssl.disable: true
      log_level: ERROR
    path: ~/.bzt/jmeter-taurus/current/bin/jmeter
    download-link: https://archive.apache.org/dist/jmeter/binaries/apache-jmeter-{version}.zip
    version: 5.5  # minimal supported version of JMeter is 2.9
    force-ctg: true   # true by default
    detect-plugins: true
    csv-jtl-flags:
      bytes: true
      sentBytes: true

settings:
  check-updates: false

scenarios:
  simple:
    requests:
     - label: "example"
       url: https://www.google.com/

Expected behavior
Statistics to appear under correct headings.

Hi @kierangirvan ! This should be fixes in the newest version

Hi @ludeknovy
I've just upgraded to the latest version, and the heading issue is now resolved, see below:

Thank you for your quick turnaround.


typo disconnect method

disconnect(): void {
this.socket.disconect();
}
should be
disconnect(): void {
this.socket.disconnect();
}

Thanks for pointing that out it is fixed in https://github.com/triniwiz/nativescript-socketio/commit/3a56c1fd84bd9f9ac21530fc01566939852918d8


Dill fails to serialize globals in windows

This error pops up in Windows
>>> import dask.bag as db
>>> b = db.from_sequence([1, 2, 3])
>>> q = 5
>>> list(b.map(lambda x: x + q))
NameError: global name 'q' is not defined

This is because dill doesn't serialize globals well.  Somewhat related to https://github.com/uqfoundation/dill/issues/98

I believe the better link is: https://github.com/uqfoundation/dill/pull/86 -- which is essentially resolved through my edits to the referenced PR, but not applied (due to lack of time on my part as of late).

@mrocklin : do you have access to a windows box? Both the referenced issues are closed, may be fixed.

This works for me if I set the recurse flag in dill
dill.settings['recurse'] = True

but continues to fail otherwise.  Either we should set this flag in dask, which might be a bit invasive, or we should wait until this is set by default in dill.  My understanding from @mmckerns was that there were still some concerns about setting this flag by default.

I've tested, and can confirm the behavior that @mrocklin sees on windows.
Please see the discussion thread here:
https://github.com/uqfoundation/dill/issues/115
and the linked issues:
https://github.com/uqfoundation/dill/issues/105
https://github.com/uqfoundation/multiprocess/issues/6

Dask now uses cloudpickle instead of dill for multiprocessing. Closing.


Azure sg2 - clone, edit and delete functionality

please review.  will squash to a single commit before PR to spinnaker/master

LGTM


.ply data loader should support 2D point cloud & meshes

Our current DataLoader supports only 3D point clouds, which is by far the most user requested thing, but plys can do more!

Related: https://github.com/rerun-io/rerun/issues/6808


[mesheryctl] Moved update flag to utils/constants

Signed-off-by: Ashish Tiwari<EMAIL_ADDRESS>Description
Currently update flag is randomly defined in check_test in system package. Moving this to a utils/constants for a more ubiquitous use.
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

@piyushsingariya  unit tests are failing because somehow in workflow ,its looking for tests files in github.com/layer5io/
Can you see why is it happening?

this constant should be placed under the root/constants package. utils/constants contains repository level constants.
FYI:- many constants that are supposed to be only used my mesheryctl are in process to be shifted under root/constants package.

this constant should be placed under the root/constants package. utils/constants contains repository level constants.
FYI:- many constants that are supposed to be only used in mesheryctl are in process to be shifted from utils package to root/constants package.

Cool, will make the changes


getting errors installing

I should have all dependencies, theano enabled for opencl.
running
pip install -r requirements.txt
I get
pip install -r requirements.txt
Requirement already satisfied (use --upgrade to upgrade): Cython==0.23.4 in ./venv/lib/python2.7/site-packages (from -r requirements.txt (line 1))
Collecting h5py==2.5.0 (from -r requirements.txt (line 2))
  Using cached h5py-2.5.0.tar.gz
Collecting Keras==0.3.2 (from -r requirements.txt (line 3))
Requirement already satisfied (use --upgrade to upgrade): numpy==1.10.4 in ./venv/lib/python2.7/site-packages (from -r requirements.txt (line 4))
Collecting Pillow==3.1.1 (from -r requirements.txt (line 5))
Collecting PyYAML==3.11 (from -r requirements.txt (line 6))
Collecting scipy==0.17.0 (from -r requirements.txt (line 7))
  Using cached scipy-0.17.0.tar.gz
Requirement already satisfied (use --upgrade to upgrade): six==1.10.0 in ./venv/lib/python2.7/site-packages (from -r requirements.txt (line 8))
Obtaining Theano from git+git://github.com/Theano/Theano.git@954c3816a40de172c28124017a25387f3bf551b2#egg=Theano (from -r requirements.txt (line 9))
  Skipping because already up-to-date.
Building wheels for collected packages: h5py, scipy
  Running setup.py bdist_wheel for h5py ... error
  Complete output from command /home/alex/image-analogies/venv/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-g7OTWL/h5py/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" bdist_wheel -d /tmp/tmpImCcmFpip-wheel- --python-tag cp27:
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib.linux-x86_64-2.7
  creating build/lib.linux-x86_64-2.7/h5py
  copying h5py/highlevel.py -> build/lib.linux-x86_64-2.7/h5py
  copying h5py/__init__.py -> build/lib.linux-x86_64-2.7/h5py
  copying h5py/ipy_completer.py -> build/lib.linux-x86_64-2.7/h5py
  copying h5py/version.py -> build/lib.linux-x86_64-2.7/h5py
  creating build/lib.linux-x86_64-2.7/h5py/_hl
  copying h5py/_hl/base.py -> build/lib.linux-x86_64-2.7/h5py/_hl
  copying h5py/_hl/selections.py -> build/lib.linux-x86_64-2.7/h5py/_hl
  copying h5py/_hl/__init__.py -> build/lib.linux-x86_64-2.7/h5py/_hl
  copying h5py/_hl/selections2.py -> build/lib.linux-x86_64-2.7/h5py/_hl
  copying h5py/_hl/group.py -> build/lib.linux-x86_64-2.7/h5py/_hl
  copying h5py/_hl/datatype.py -> build/lib.linux-x86_64-2.7/h5py/_hl
  copying h5py/_hl/attrs.py -> build/lib.linux-x86_64-2.7/h5py/_hl
  copying h5py/_hl/dims.py -> build/lib.linux-x86_64-2.7/h5py/_hl
  copying h5py/_hl/dataset.py -> build/lib.linux-x86_64-2.7/h5py/_hl
  copying h5py/_hl/files.py -> build/lib.linux-x86_64-2.7/h5py/_hl
  copying h5py/_hl/filters.py -> build/lib.linux-x86_64-2.7/h5py/_hl
  creating build/lib.linux-x86_64-2.7/h5py/tests
  copying h5py/tests/__init__.py -> build/lib.linux-x86_64-2.7/h5py/tests
  copying h5py/tests/common.py -> build/lib.linux-x86_64-2.7/h5py/tests
  creating build/lib.linux-x86_64-2.7/h5py/tests/old
  copying h5py/tests/old/test_dataset.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
  copying h5py/tests/old/test_h5.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
  copying h5py/tests/old/test_h5p.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
  copying h5py/tests/old/test_file.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
  copying h5py/tests/old/__init__.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
  copying h5py/tests/old/test_h5f.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
  copying h5py/tests/old/test_selections.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
  copying h5py/tests/old/test_objects.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
  copying h5py/tests/old/test_dimension_scales.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
  copying h5py/tests/old/test_slicing.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
  copying h5py/tests/old/test_attrs_data.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
  copying h5py/tests/old/test_base.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
  copying h5py/tests/old/test_h5t.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
  copying h5py/tests/old/test_datatype.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
  copying h5py/tests/old/common.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
  copying h5py/tests/old/test_attrs.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
  copying h5py/tests/old/test_group.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
  creating build/lib.linux-x86_64-2.7/h5py/tests/hl
  copying h5py/tests/hl/test_dataset_swmr.py -> build/lib.linux-x86_64-2.7/h5py/tests/hl
  copying h5py/tests/hl/test_file.py -> build/lib.linux-x86_64-2.7/h5py/tests/hl
  copying h5py/tests/hl/__init__.py -> build/lib.linux-x86_64-2.7/h5py/tests/hl
  copying h5py/tests/hl/test_dims_dimensionproxy.py -> build/lib.linux-x86_64-2.7/h5py/tests/hl
  copying h5py/tests/hl/test_dataset_getitem.py -> build/lib.linux-x86_64-2.7/h5py/tests/hl
  copying h5py/tests/hl/test_attribute_create.py -> build/lib.linux-x86_64-2.7/h5py/tests/hl
  running build_ext
  Autodetection skipped [libhdf5.so: cannot open shared object file: No such file or directory]
  ********************************************************************************
                         Summary of the h5py configuration

      Path to HDF5: None
      HDF5 Version: '1.8.4'
       MPI Enabled: False
  Rebuild Required: False

  ********************************************************************************
  Executing api_gen rebuild of defs
  Executing cythonize()
  Compiling /tmp/pip-build-g7OTWL/h5py/h5py/defs.pyx because it changed.
  Compiling /tmp/pip-build-g7OTWL/h5py/h5py/_errors.pyx because it changed.
  Compiling /tmp/pip-build-g7OTWL/h5py/h5py/_objects.pyx because it changed.
  Compiling /tmp/pip-build-g7OTWL/h5py/h5py/_proxy.pyx because it changed.
  Compiling /tmp/pip-build-g7OTWL/h5py/h5py/h5fd.pyx because it changed.
  Compiling /tmp/pip-build-g7OTWL/h5py/h5py/h5z.pyx because it changed.
  Compiling /tmp/pip-build-g7OTWL/h5py/h5py/h5.pyx because it changed.
  Compiling /tmp/pip-build-g7OTWL/h5py/h5py/h5i.pyx because it changed.
  Compiling /tmp/pip-build-g7OTWL/h5py/h5py/h5r.pyx because it changed.
  Compiling /tmp/pip-build-g7OTWL/h5py/h5py/utils.pyx because it changed.
  Compiling /tmp/pip-build-g7OTWL/h5py/h5py/_conv.pyx because it changed.
  Compiling /tmp/pip-build-g7OTWL/h5py/h5py/h5t.pyx because it changed.
  Compiling /tmp/pip-build-g7OTWL/h5py/h5py/h5s.pyx because it changed.
  Compiling /tmp/pip-build-g7OTWL/h5py/h5py/h5p.pyx because it changed.
  Compiling /tmp/pip-build-g7OTWL/h5py/h5py/h5d.pyx because it changed.
  Compiling /tmp/pip-build-g7OTWL/h5py/h5py/h5a.pyx because it changed.
  Compiling /tmp/pip-build-g7OTWL/h5py/h5py/h5f.pyx because it changed.
  Compiling /tmp/pip-build-g7OTWL/h5py/h5py/h5g.pyx because it changed.
  Compiling /tmp/pip-build-g7OTWL/h5py/h5py/h5l.pyx because it changed.
  Compiling /tmp/pip-build-g7OTWL/h5py/h5py/h5o.pyx because it changed.
  Compiling /tmp/pip-build-g7OTWL/h5py/h5py/h5ds.pyx because it changed.
  Compiling /tmp/pip-build-g7OTWL/h5py/h5py/h5ac.pyx because it changed.
  [ 1/22] Cythonizing /tmp/pip-build-g7OTWL/h5py/h5py/_conv.pyx
  [ 2/22] Cythonizing /tmp/pip-build-g7OTWL/h5py/h5py/_errors.pyx
  [ 3/22] Cythonizing /tmp/pip-build-g7OTWL/h5py/h5py/_objects.pyx
  [ 4/22] Cythonizing /tmp/pip-build-g7OTWL/h5py/h5py/_proxy.pyx
  [ 5/22] Cythonizing /tmp/pip-build-g7OTWL/h5py/h5py/defs.pyx
  [ 6/22] Cythonizing /tmp/pip-build-g7OTWL/h5py/h5py/h5.pyx
  [ 7/22] Cythonizing /tmp/pip-build-g7OTWL/h5py/h5py/h5a.pyx
  [ 8/22] Cythonizing /tmp/pip-build-g7OTWL/h5py/h5py/h5ac.pyx
  [ 9/22] Cythonizing /tmp/pip-build-g7OTWL/h5py/h5py/h5d.pyx
  [10/22] Cythonizing /tmp/pip-build-g7OTWL/h5py/h5py/h5ds.pyx
  [11/22] Cythonizing /tmp/pip-build-g7OTWL/h5py/h5py/h5f.pyx
  [12/22] Cythonizing /tmp/pip-build-g7OTWL/h5py/h5py/h5fd.pyx
  [13/22] Cythonizing /tmp/pip-build-g7OTWL/h5py/h5py/h5g.pyx
  [14/22] Cythonizing /tmp/pip-build-g7OTWL/h5py/h5py/h5i.pyx
  [15/22] Cythonizing /tmp/pip-build-g7OTWL/h5py/h5py/h5l.pyx
  [16/22] Cythonizing /tmp/pip-build-g7OTWL/h5py/h5py/h5o.pyx
  [17/22] Cythonizing /tmp/pip-build-g7OTWL/h5py/h5py/h5p.pyx
  [18/22] Cythonizing /tmp/pip-build-g7OTWL/h5py/h5py/h5r.pyx
  [19/22] Cythonizing /tmp/pip-build-g7OTWL/h5py/h5py/h5s.pyx
  [20/22] Cythonizing /tmp/pip-build-g7OTWL/h5py/h5py/h5t.pyx
  [21/22] Cythonizing /tmp/pip-build-g7OTWL/h5py/h5py/h5z.pyx
  [22/22] Cythonizing /tmp/pip-build-g7OTWL/h5py/h5py/utils.pyx
  building 'h5py.defs' extension
  creating build/temp.linux-x86_64-2.7
  creating build/temp.linux-x86_64-2.7/tmp
  creating build/temp.linux-x86_64-2.7/tmp/pip-build-g7OTWL
  creating build/temp.linux-x86_64-2.7/tmp/pip-build-g7OTWL/h5py
  creating build/temp.linux-x86_64-2.7/tmp/pip-build-g7OTWL/h5py/h5py
  x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -DH5_USE_16_API -I/tmp/pip-build-g7OTWL/h5py/lzf -I/opt/local/include -I/usr/local/include -I/home/alex/image-analogies/venv/local/lib/python2.7/site-packages/numpy/core/include -I/usr/include/python2.7 -c /tmp/pip-build-g7OTWL/h5py/h5py/defs.c -o build/temp.linux-x86_64-2.7/tmp/pip-build-g7OTWL/h5py/h5py/defs.o
  In file included from /home/alex/image-analogies/venv/local/lib/python2.7/site-packages/numpy/core/include/numpy/ndarraytypes.h:1781:0,
                   from /home/alex/image-analogies/venv/local/lib/python2.7/site-packages/numpy/core/include/numpy/ndarrayobject.h:18,
                   from /home/alex/image-analogies/venv/local/lib/python2.7/site-packages/numpy/core/include/numpy/arrayobject.h:4,
                   from /tmp/pip-build-g7OTWL/h5py/h5py/api_compat.h:26,
                   from /tmp/pip-build-g7OTWL/h5py/h5py/defs.c:279:
  /home/alex/image-analogies/venv/local/lib/python2.7/site-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:15:2: warning: #warning "Using deprecated NumPy API, disable it by " "#defining NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
   #warning "Using deprecated NumPy API, disable it by " \
    ^
  In file included from /tmp/pip-build-g7OTWL/h5py/h5py/defs.c:279:0:
  /tmp/pip-build-g7OTWL/h5py/h5py/api_compat.h:27:18: fatal error: hdf5.h: File o directory non esistente
  compilation terminated.
  error: command 'x86_64-linux-gnu-gcc' failed with exit status 1

  ----------------------------------------
  Failed building wheel for h5py
  Running setup.py clean for h5py
  Running setup.py bdist_wheel for scipy ... done
  Stored in directory: /home/alex/.cache/pip/wheels/76/aa/e2/031ee833b4abfd33d8620e4bc36f8178b95cfcf36ec550a6b9
Successfully built scipy
Failed to build h5py
Installing collected packages: h5py, scipy, Theano, PyYAML, Keras, Pillow
  Running setup.py install for h5py ... error
    Complete output from command /home/alex/image-analogies/venv/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-g7OTWL/h5py/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-x5IHF0-record/install-record.txt --single-version-externally-managed --compile --install-headers /home/alex/image-analogies/venv/include/site/python2.7/h5py:
    running install
    running build
    running build_py
    creating build
    creating build/lib.linux-x86_64-2.7
    creating build/lib.linux-x86_64-2.7/h5py
    copying h5py/highlevel.py -> build/lib.linux-x86_64-2.7/h5py
    copying h5py/__init__.py -> build/lib.linux-x86_64-2.7/h5py
    copying h5py/ipy_completer.py -> build/lib.linux-x86_64-2.7/h5py
    copying h5py/version.py -> build/lib.linux-x86_64-2.7/h5py
    creating build/lib.linux-x86_64-2.7/h5py/_hl
    copying h5py/_hl/base.py -> build/lib.linux-x86_64-2.7/h5py/_hl
    copying h5py/_hl/selections.py -> build/lib.linux-x86_64-2.7/h5py/_hl
    copying h5py/_hl/__init__.py -> build/lib.linux-x86_64-2.7/h5py/_hl
    copying h5py/_hl/selections2.py -> build/lib.linux-x86_64-2.7/h5py/_hl
    copying h5py/_hl/group.py -> build/lib.linux-x86_64-2.7/h5py/_hl
    copying h5py/_hl/datatype.py -> build/lib.linux-x86_64-2.7/h5py/_hl
    copying h5py/_hl/attrs.py -> build/lib.linux-x86_64-2.7/h5py/_hl
    copying h5py/_hl/dims.py -> build/lib.linux-x86_64-2.7/h5py/_hl
    copying h5py/_hl/dataset.py -> build/lib.linux-x86_64-2.7/h5py/_hl
    copying h5py/_hl/files.py -> build/lib.linux-x86_64-2.7/h5py/_hl
    copying h5py/_hl/filters.py -> build/lib.linux-x86_64-2.7/h5py/_hl
    creating build/lib.linux-x86_64-2.7/h5py/tests
    copying h5py/tests/__init__.py -> build/lib.linux-x86_64-2.7/h5py/tests
    copying h5py/tests/common.py -> build/lib.linux-x86_64-2.7/h5py/tests
    creating build/lib.linux-x86_64-2.7/h5py/tests/old
    copying h5py/tests/old/test_dataset.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
    copying h5py/tests/old/test_h5.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
    copying h5py/tests/old/test_h5p.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
    copying h5py/tests/old/test_file.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
    copying h5py/tests/old/__init__.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
    copying h5py/tests/old/test_h5f.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
    copying h5py/tests/old/test_selections.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
    copying h5py/tests/old/test_objects.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
    copying h5py/tests/old/test_dimension_scales.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
    copying h5py/tests/old/test_slicing.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
    copying h5py/tests/old/test_attrs_data.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
    copying h5py/tests/old/test_base.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
    copying h5py/tests/old/test_h5t.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
    copying h5py/tests/old/test_datatype.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
    copying h5py/tests/old/common.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
    copying h5py/tests/old/test_attrs.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
    copying h5py/tests/old/test_group.py -> build/lib.linux-x86_64-2.7/h5py/tests/old
    creating build/lib.linux-x86_64-2.7/h5py/tests/hl
    copying h5py/tests/hl/test_dataset_swmr.py -> build/lib.linux-x86_64-2.7/h5py/tests/hl
    copying h5py/tests/hl/test_file.py -> build/lib.linux-x86_64-2.7/h5py/tests/hl
    copying h5py/tests/hl/__init__.py -> build/lib.linux-x86_64-2.7/h5py/tests/hl
    copying h5py/tests/hl/test_dims_dimensionproxy.py -> build/lib.linux-x86_64-2.7/h5py/tests/hl
    copying h5py/tests/hl/test_dataset_getitem.py -> build/lib.linux-x86_64-2.7/h5py/tests/hl
    copying h5py/tests/hl/test_attribute_create.py -> build/lib.linux-x86_64-2.7/h5py/tests/hl
    running build_ext
    Autodetection skipped [libhdf5.so: cannot open shared object file: No such file or directory]
    ********************************************************************************
                           Summary of the h5py configuration

        Path to HDF5: None
        HDF5 Version: '1.8.4'
         MPI Enabled: False
    Rebuild Required: False

    ********************************************************************************
    Executing cythonize()
    building 'h5py.defs' extension
    creating build/temp.linux-x86_64-2.7
    creating build/temp.linux-x86_64-2.7/tmp
    creating build/temp.linux-x86_64-2.7/tmp/pip-build-g7OTWL
    creating build/temp.linux-x86_64-2.7/tmp/pip-build-g7OTWL/h5py
    creating build/temp.linux-x86_64-2.7/tmp/pip-build-g7OTWL/h5py/h5py
    x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -DH5_USE_16_API -I/tmp/pip-build-g7OTWL/h5py/lzf -I/opt/local/include -I/usr/local/include -I/home/alex/image-analogies/venv/local/lib/python2.7/site-packages/numpy/core/include -I/usr/include/python2.7 -c /tmp/pip-build-g7OTWL/h5py/h5py/defs.c -o build/temp.linux-x86_64-2.7/tmp/pip-build-g7OTWL/h5py/h5py/defs.o
    In file included from /home/alex/image-analogies/venv/local/lib/python2.7/site-packages/numpy/core/include/numpy/ndarraytypes.h:1781:0,
                     from /home/alex/image-analogies/venv/local/lib/python2.7/site-packages/numpy/core/include/numpy/ndarrayobject.h:18,
                     from /home/alex/image-analogies/venv/local/lib/python2.7/site-packages/numpy/core/include/numpy/arrayobject.h:4,
                     from /tmp/pip-build-g7OTWL/h5py/h5py/api_compat.h:26,
                     from /tmp/pip-build-g7OTWL/h5py/h5py/defs.c:279:
    /home/alex/image-analogies/venv/local/lib/python2.7/site-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:15:2: warning: #warning "Using deprecated NumPy API, disable it by " "#defining NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
     #warning "Using deprecated NumPy API, disable it by " \
      ^
    In file included from /tmp/pip-build-g7OTWL/h5py/h5py/defs.c:279:0:
    /tmp/pip-build-g7OTWL/h5py/h5py/api_compat.h:27:18: fatal error: hdf5.h: File o directory non esistente
    compilation terminated.
    error: command 'x86_64-linux-gnu-gcc' failed with exit status 1

    ----------------------------------------
Command "/home/alex/image-analogies/venv/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-g7OTWL/h5py/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-x5IHF0-record/install-record.txt --single-version-externally-managed --compile --install-headers /home/alex/image-analogies/venv/include/site/python2.7/h5py" failed with error code 1 in /tmp/pip-build-g7OTWL/h5py/

I guess it has something to do with some depricated apis or some missing file, but I really don't get what I should do.
Any help?

Hmm not sure, [http://stackoverflow.com/questions/24744969/installing-h5py-on-an-ubuntu-server](possibly this is your problem)? sudo apt-get install libhdf5-dev

it worked!
on my gpu I get decent results, but on my cpu server, despite being a VERY powerful one it takes ages...on the same server CNNMRF works good.
I guess I'll go with amazon cloud g2.large .
I noticed a minor ''bug'' in your readme.
the blurry skull is A, the system learns A->A' and then applies it to B to obtain B'. amazing.
if you look up at Trump and the sea I think A and A' have switched sides.
it should go from the first green/red/blue image to the ''natural'' and then apply the transformation to the second rgb image obtaining the result. in that order it seems wrong and it's incosistent with trump. Am I wrong?

Sweet, hit me up via email or twitter (@awentzonline) if you make something you want to share. Regarding CPU performance, someone recently added notes to the readme about using openmp. They suggested these environment variables:

THEANO_FLAGS='openmp=1,openmp_elemwise_minsize=<min_tensor_size>' OMP_NUM_THREADS=<cpu_num>

I'm not sure what the sweet spot is for min_tensor_size. Also http://deeplearning.net/software/theano/tutorial/multi_cores.html might be helpful.
Good point about the readme images. I had originally ordered them in that way because I thought it would be simpler to initially understand. I'm working on an overhaul of the examples.


Fix issue with label traefik.backend.loadbalancer.stickiness.cookieName

What does this PR do?
Fix issue using label traefik.backend.loadbalancer.stickiness.cookieName at rancher provider.
When label traefik.backend.loadbalancer.stickiness.cookieName is used with rancher provider,
get errors message
18/11/2017 13:28:59time="2017-11-18T12:28:59Z" level=error msg="template: :14:24: executing "" at <getStickinessCookieN...>: wrong number of args for getStickinessCookieName: want 2 got 1"
Motivation
https://github.com/rawmind0/rancher-traefik/issues/57

@rawmind0 could you change to base branch of this PR to 1.4 and rebase on the branch 1.4 ?

Raul, thanks for responding so quickly to my question with a PR.
In the meantime, I want to clarify proper usage of stickiness.  I also tried just specifying
traefik.backend.loadbalancer.stickiness=true
by itself, without specifying cookieName.  I get the same error in the logs
 executing "" at <getStickinessCookieN...>: wrong number of args for getStickinessCookieName: want 2 got 1"
and stickiness is not enabled.
So my question is, is there some workaround for me to enable stickiness with Rancher?
Thanks again for your help with this!

@ldez changed base to V1.4 and merged.

@rawmind0 You have make a mistake, you should not have done a merge but a rebase.
I will fix that.

@rawmind0 next try to not use your master to do a PR. 😉
Sorry to be forced to rebase your master on our v1.4 branch.

@trauts2 you can use the deprecated option traefik.backend.loadbalancer.sticky

It works!  Thanks Ludovic.  I'll switch to the non-deprecated version when
it hits the release.
On Sat, Nov 18, 2017 at 3:46 PM, Ludovic Fernandez<EMAIL_ADDRESS>
wrote:

@trauts2 https://github.com/trauts2 you can use the deprecated option
traefik.backend.loadbalancer.sticky
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/containous/traefik/pull/2423#issuecomment-345473704,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD0TaNPgwC76_r7vhKrDnaXYdMvZRCKJks5s31BFgaJpZM4Qi_hI
.


[ALLUXIO-2207] Use a range query to limit data fetched by Swift InputStream

This addresses JIRA https://alluxio.atlassian.net/browse/ALLUXIO-2207.

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/Alluxio-Pull-Request-Builder/11214/
Test PASSed.

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/Alluxio-Pull-Request-Builder/11229/
Test PASSed.

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/Alluxio-Pull-Request-Builder/11230/
Test PASSed.

@madanadit This looks good aside from the question about reading beyond the range.

@calvinjia Thanks for the review!. I have modified the behavior to openStream again in case a chunk boundary has been reached.

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/Alluxio-Pull-Request-Builder/11243/
Test PASSed.

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/Alluxio-Pull-Request-Builder/11245/
Test PASSed.

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/Alluxio-Pull-Request-Builder/11246/
Test PASSed.

@madanadit did a pass and left some comments

@jsimsa The JOSS javadoc is out of date. AbstractRange has 'long' fields: https://github.com/javaswift/joss/blob/bf0b8e411a1022e167e034ba4c3482670d46b6fe/src/main/java/org/javaswift/joss/headers/object/range/AbstractRange.java.
Unfortunately MidPartRange (https://github.com/javaswift/joss/blob/bf0b8e411a1022e167e034ba4c3482670d46b6fe/src/main/java/org/javaswift/joss/headers/object/range/MidPartRange.java) casts 'int' into 'long' fields. That is why I created this class.
I have refactored to store 'length' instead of 'endPos' in AbstractRange.length field, and modified the getTo method in SwiftRange accordingly.

@jsimsa @calvinjia I've addresses all the comments. Please have another look. Thanks!.

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/Alluxio-Pull-Request-Builder/11262/
Test PASSed.

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/Alluxio-Pull-Request-Builder/11263/
Test PASSed.

LGTM

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/Alluxio-Pull-Request-Builder/11264/
Test PASSed.

LGTM

@calvinjia @jsimsa I mentioned the invariant as a comment. This should be good to go now. Thanks for the discussion.


hpo_term was not being added to annotations

The hpo_term was not being added to self._annotations when the add_term function was given an HPO ID. When the phenopacket was created at the end, none of the added terms were showing.
I believe that this will fix that issue!

@lnrekerle Thanks!


The memory [M] buttons do not work ...

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

tap any number : 55
Swipe left to open the scientific functions
Tap on [MS] and the value "55" is not stored :
swipe right to hide the menu and clear the screen from any values.
Swipe left again to show scientific functions
Tap on [MR] and the value "55" will not show.
Tapping [M+] and/or [M-] does not do anything.

Expected behavior
The memory [M] buttons [MS], [MR], [M+] and [M-] buttons should store, restore, add and deduct the actual value displayed on screen, which is not happening.
Android (please complete the following information):

Device: [Samsung Galaxy S20+ 5G]
OS: Android 13, One UI 5.1
App Version : 2.4.4

@Vectord2000 Memory functions would work when there is expression in the result state. As per your steps, since you havn't started any calculation with number 55, there is no value in storing it into [MS]. Try doing this:

write: 55 + 2
Open advanced panel, tap [MS] and then close the panel. The result of the expression, i.e., 57 is copied over to the memory.
Clear all the expressions.
Open advanced panel, tap [MR]. This will restore the number 57 from the memory.
You can similarly try using [M+] & [M-]


Ttrigger add/remove contact actions properly in Chips demo

thanks @pauln for this 👍 I had these changes locally during my testing but I think things have gotten a little bit lost with the length of time this has been "in progress" 😂


Bug: Blank Subjects Don't Work with Checkboxes

The fallback empty subject does not work if checkboxes are selected.
Expected Result:
Activity Report ...checkbox details
Actual Result:
: ...checkbox details
Related to #18 Bug: Blank Subjects Don't Work
https://github.com/aljawaid/KanboardEmailHistory/blob/da33b58edc77adb0c341695f0c16ac7dbe3650c6/Action/EmailTaskHistory.php#L68

$this->getParam('email_subject') is expecting a value from the field, so it returns blank.

[ ] Need to adjust the code to account for checkboxes WITH blank/fallback subjects


[Fix] Fix typo 'metirc'

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Fixing a typo so that the instruction becomes more clear
Modification
Please briefly describe what modification is made in this PR.
I've fixed the misspelled word 'metirc' as 'metric' in mmcls/datasets/base_dataset.py
BC-breaking (Optional)
Does the modification introduce changes that break the backward compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here and update the documentation.
Checklist
Before PR:

[ ] Pre-commit or other linting tools are used to fix the potential lint issues.
[ ] Bug fixes are fully covered by unit tests, the case that causes the bug should be added in the unit tests.
[ ] The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
[ ] The documentation has been modified accordingly, like docstring or example tutorials.

After PR:

[ ] If the modification has potential influence on downstream or other related projects, this PR should be tested with those projects, like MMDet or MMSeg.
[ ] CLA has been signed and all committers have signed the CLA in this PR.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Azad Baykara seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Error when doing yarn run dist

yarn run app is successful but not the dist.
[154] ./lib/index.js 3.99 kB {0} [built]
    + 300 hidden modules
electron-builder 18.3.5
Rebuilding native production dependencies for linux:ia32
Rebuilding native dependency node-pty
Error: /usr/local/bin/node exited with code 1
Output:
make: Entering directory '/home/slim/gitRepos/branchesgits/hyper/app/node_modules/node-pty/build'
  CXX(target) Release/obj.target/pty/src/unix/pty.o
pty.target.mk:92: recipe for target 'Release/obj.target/pty/src/unix/pty.o' failed
make: Leaving directory '/home/slim/gitRepos/branchesgits/hyper/app/node_modules/node-pty/build'

Error output:
gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| linux | x64
gyp info spawn /usr/bin/python2
gyp info spawn args [ '/usr/local/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/home/slim/gitRepos/branchesgits/hyper/app/node_modules/node-pty/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/usr/local/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/slim/.electron-gyp/.node-gyp/iojs-1.6.11/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/home/slim/.electron-gyp/.node-gyp/iojs-1.6.11',
gyp info spawn args   '-Dnode_gyp_dir=/usr/local/lib/node_modules/npm/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=/home/slim/.electron-gyp/.node-gyp/iojs-1.6.11/<(target_arch)/iojs.lib',
gyp info spawn args   '-Dmodule_root_dir=/home/slim/gitRepos/branchesgits/hyper/app/node_modules/node-pty',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.' ]
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
In file included from /usr/include/errno.h:28:0,
                 from /home/slim/.electron-gyp/.node-gyp/iojs-1.6.11/deps/uv/include/uv-errno.h:25,
                 from /home/slim/.electron-gyp/.node-gyp/iojs-1.6.11/deps/uv/include/uv.h:48,
                 from ../../nan/nan.h:46,
                 from ../src/unix/pty.cc:20:
/usr/include/features.h:367:25: fatal error: sys/cdefs.h: No such file or directory
compilation terminated.
make: *** [Release/obj.target/pty/src/unix/pty.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:258:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:194:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
gyp ERR! System Linux 4.4.0-81-generic
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/slim/gitRepos/branchesgits/hyper/app/node_modules/node-pty
gyp ERR! node -v v7.9.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
error Command failed with exit code 1.

    at ChildProcess.childProcess.once.code (/home/slim/gitRepos/branchesgits/hyper/node_modules/electron-builder-util/src/util.ts:135:14)
    at Object.onceWrapper (events.js:293:19)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:194:7)
    at maybeClose (internal/child_process.js:899:16)
    at Socket.<anonymous> (internal/child_process.js:342:11)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:191:7)
    at Pipe._handle.close [as _onclose] (net.js:510:12)
From previous event:
    at spawn (/home/slim/gitRepos/branchesgits/hyper/node_modules/electron-builder-util/src/util.ts:103:3)
    at /home/slim/gitRepos/branchesgits/hyper/node_modules/electron-builder/src/yarn.ts:117:7
    at runCallback (timers.js:672:20)
    at tryOnImmediate (timers.js:645:5)
    at processImmediate [as _immediateCallback] (timers.js:617:5)
From previous event:
    at /home/slim/gitRepos/branchesgits/hyper/node_modules/electron-builder/src/yarn.ts:115:27
From previous event:
    at rebuild (/home/slim/gitRepos/branchesgits/hyper/node_modules/electron-builder/out/yarn.js:93:22)
    at /home/slim/gitRepos/branchesgits/hyper/node_modules/electron-builder/src/yarn.ts:16:11
    at Generator.next (<anonymous>)
    at runCallback (timers.js:672:20)
    at tryOnImmediate (timers.js:645:5)
    at processImmediate [as _immediateCallback] (timers.js:617:5)
From previous event:
    at installOrRebuild (/home/slim/gitRepos/branchesgits/hyper/node_modules/electron-builder/out/yarn.js:33:21)
    at /home/slim/gitRepos/branchesgits/hyper/node_modules/electron-builder/src/packager.ts:419:13
    at Generator.next (<anonymous>)
From previous event:
    at Packager.installAppDependencies (/home/slim/gitRepos/branchesgits/hyper/node_modules/electron-builder/out/packager.js:496:11)
    at /home/slim/gitRepos/branchesgits/hyper/node_modules/electron-builder/src/packager.ts:246:20
    at Generator.next (<anonymous>)
From previous event:
    at Packager.doBuild (/home/slim/gitRepos/branchesgits/hyper/node_modules/electron-builder/out/packager.js:389:11)
    at /home/slim/gitRepos/branchesgits/hyper/node_modules/electron-builder/src/packager.ts:185:52
    at Generator.next (<anonymous>)
    at runCallback (timers.js:672:20)
    at tryOnImmediate (timers.js:645:5)
    at processImmediate [as _immediateCallback] (timers.js:617:5)
From previous event:
    at Packager.build (/home/slim/gitRepos/branchesgits/hyper/node_modules/electron-builder/out/packager.js:284:11)
    at /home/slim/gitRepos/branchesgits/hyper/node_modules/electron-builder/src/builder.ts:198:33
    at Generator.next (<anonymous>)
From previous event:
    at build (/home/slim/gitRepos/branchesgits/hyper/node_modules/electron-builder/out/builder.js:70:21)
    at Object.<anonymous> (/home/slim/gitRepos/branchesgits/hyper/node_modules/electron-builder/out/cli/build-cli.js:71:41)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.runMain (module.js:605:10)
    at run (bootstrap_node.js:423:7)
    at startup (bootstrap_node.js:147:9)
    at bootstrap_node.js:538:3
error Command failed with exit code 255.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I ran into this same issue and spent sometime figuring it out. This line gives away the issue:
/usr/include/features.h:367:25: fatal error: sys/cdefs.h: No such file or directory
Turns out to be an issue missing some c libraries you need to build for other architectures (32bit / 64bit). Here's where I got that idea from. You have the libraries for your system, which is why you can run the app, but had issues with the dist. To fix the issue on my system (Ubuntu) I ran  sudo apt-get install g++-multilib, so you would probably need to do something similar.


Add a Gitter chat badge to README.md

hawkw/seax now has a Chat Room on Gitter
@hawkw has just created a chat room. You can visit it here: https://gitter.im/hawkw/seax.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Current coverage is 100.0%

Merging #96 into master will not affect coverage as of 011cb2f

@@            master     #96   diff @@
======================================
  Files            1       1
  Stmts            2       2
  Branches         0       0
  Methods          0       0
======================================
  Hit              2       2
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff

Powered by Codecov


Invest flow tweaks for low liqudity protection

Description
Adds a couple of warnings/errors for low liquidity pools - according to "quick wins" design here: https://www.figma.com/file/S5p30cxomV6gIyRZJMrvb3/Add-liquidity?node-id=802%3A6347

Added a "low liquidity" warning if the total liquidity is less than 50K.
Added "zero amount" assets to be shown in the preview screen (along with sorting them by their fiat value).
Added a new "rekt" error that disallows the user to continue.

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Dependency changes
[ ] Code refactor / cleanup
[ ] Documentation or wording changes
[ ] Other

How should this be tested?
Please provide instructions so we can test. Please also list any relevant details for your test configuration.

[ ] Easiest to test is to tweak the values locally to see the different warnings/errors.

Visual context
Please provide any relevant visual context for UI changes or additions. This could be static screenshots or a loom screencast.
Checklist:

[x] I have performed a self-review of my own code
[x] I have requested at least 2 reviews (If the PR is significant enough, use best judgement here)
[x] I have commented my code where relevant, particularly in hard-to-understand areas
[x] If package-lock.json has changes, it was intentional.
[x] The base of this PR is master if hotfix, develop if not

@garethfuller I've changed it


Option to not cache empty tile respones

Hi all
We are using Tegola in front of PostGIS, and encounter empty tiles, from time to time.
While it can be debated whether or not empty tiles should be cached or not in principle (personally, I don't think an app should cache not found responses), we did encounter scenarios where  the cache contained empty stale entries (tiles containing empty responses) and purging it manually was the only way to reacquire valid tiles
Looking at the configuration, I couldn't find an option to avoid caching for empty responses.
We tried using both the postgis and mvt_postgis provider (with latter supposedly bypassing tegola's MVT generation layer, to the best of my understanding), but we're still caching empty tiles.
Is there a way to configure/achieve this behavior?

@sheinbergon I would need to look into what PostGIS returns when a tile is empty. I'm not sure if they:

return NULL1
return 0 bytes
return the tile layer encoded but with 0 geometries

Option 1 and 2 could have a check added and we could make this configurable. I'm not sure how we would know if a tile is empty if scenario 3 is the case.

While it can be debated whether or not empty tiles should be cached or not in principle (personally, I don't think an app should cache not found responses),

This also depends on how you're using tegola. If you pre-seed all your tiles you might want the empty tiles so things play nice with client side libraries. IIRC, the reason tegola handles "not found" tiles the way it does is because client side libraries were not expecting 404 responses from the server. Are you encountering a different scenario? What UI library are you using?

@ARolek thank you for responding.
At least when using mvt_postgres PostGIS returns an empty response,Looking at what the query does, it results in empty response, so it should be 2
I believe Tegola  just takes the empty results and transforms it to an empty FeatureCollection. By the time it reaches the caching middleware response it's just a byte array, so we should probably add some sort of an empty tile indication and avoid caching based on it
As for your second question, we are using (for this particular use-case) mapbox. Just to clarify, I didn't say we should return null responses to the client, only that I want to have the option to not cache that in case it represents an empty vector tile ( no features)

I believe Tegola just takes the empty results and transforms it to an empty FeatureCollection.

tegola does not transform anything here. it stores the the tile data it receives from postgis. we could check the length of it and optionally avoid caching but still service those empty ones to avoid errors.
That however would mean that consecutive calls will perform database lookups. I would like to avoid that, so it would definitely have to be optional/default:false.

That sounds like a great approach. Opt out by default is also good.

That however would mean that consecutive calls will perform database lookups

This is a key point. By non caching the "empty" tile, you're increasing the database load.
@sheinbergon can you elaborate a bit more on your situation? Did tegola cache an "empty" tile, but then later your dataset had data in that area and it wasn't be refetched?

@ARolek we're well aware of it.
What you mentioned is exactly our use case -  we have completely static database we wan't to serve MVT tiles from, and we encountered some scenarios of stale cache, empty tiles on different zoom levels contained no data, and only deleting from our Redis cache resolved the issue. While we could have very long discussion about debugging the cause of such behaviors/issues, it'd be much simpler to just ignore them empty tiles

@sheinbergon you mentioned redis cache. Have you considered just using the TTL in redis to expire the tiles? https://github.com/go-spatial/tegola/tree/master/cache/redis#properties

@ARolek, yes we know Redis has this option. However:

We'll be increasing the database to a much bigger degree, depnding on the actual TTL (longer times, means users my experience absent tiles longers).
We may want to move away from Redis, as it's costly
Area of intersets usually display contigues populated tiles blocks. We have no intreset in expiring those, only cases we get zero feature tiles, so database load is not expected to increase by much.

Honestly, going that path kind of feels like using  a 5 KG hammer to drive a nail through a wooden board, that's why we avoided it thus far

we have a completely static database we want to serve MVT tiles from, and we encountered some scenarios of stale cache

this is odd, or I don't understand you correctly. if the dataset is static, why would you have issues with empty tiles? either they contain the data of your static dataset, or your dataset does not provide data for them.
in that case there's an issue with tegola i would rather before anything else. :)

While I agree with you, I was just looking for a simple fix to work around these Tegola issues. We wound up disabling cache all together

While I agree with you, I was just looking for a simple fix to work around these Tegola issues. We wound up disabling cache all together

We wound up disabling cache all together

Nice! How's this working out so far? Are you using a CDN at all for short lived caching?


Change several image inputs type from string to int.

JIRA: PDC-1101

:+1:
By the way, are you aware the author e-mail address in the commit is a bit weird?

+1

:+1:

It will be excellent by providing a unit test.

@lubomir thanks for pointing this out. it seems the name and email address were configured automatically based on my username and hostname. Fixed it.

@erichuanggit ok. added it.

Looks good to me.


CA-343280: Extended proxy authentication.

There are some .Net classes for parsing/creating Http headers, could those be used instead of parsing the string manually? https://docs.microsoft.com/en-us/dotnet/api/system.net.http.headers?view=net-5.0


Replace banner link in README.md

Continued from #907

Coverage remained the same at 98.958% when pulling 685def08348115503d5d9de323f641d62782e423 on KarandikarMihir:bfix/change-banner into 3515b78bbe2e6102774a21c3e787fde995b82f94 on mxstbr:dev.

Thank you!

I'm glad that you merged :)


Error writing null values to table.

I've been using this code very successfully for some months now but have just encountered a problem with writing null values into a table. I've created a simple test table and script as listed below. The table has one column called columna and it's a float datatype which permits null values and the default value is NULL. There are no indexes on the column. Writing a value of, for example 0.0,  works OK but I get an error if the value is set to None.
import time
import network
import upymysql
import upymysql.cursors

wlan = network.WLAN(network.STA_IF)

def wifi():
    wlan.active(True)
    wlan.connect("ssid", "password")

    retries = 10
    while  retries > 0:
        if wlan.status() < 0 or wlan.status() >= 3:
            break
        retries -= 1
        time.sleep(1)

    if wlan.status() == 3:
        print("Wifi connected")
    else:
        print("Wifi connection failed")
        flashLed()

def connect_sql():
    connection = upymysql.connect(host='<IP_ADDRESS>',
       user='user',
       password='password',
       port=3307,
       db='MogWeather',
       charset='utf8mb4',
       cursorclass=upymysql.cursors.DictCursor)
    return connection

def main():
    wifi()
    connection = connect_sql()

    value = 0.0
    sql = ("INSERT INTO test (columna)"
    "VALUES (%s)")
    data = (value)
    connection.cursor().execute(sql, data)
    connection.commit()

    value = 0.0
    sql = ("INSERT INTO test (columna)"
    "VALUES (%s)")
    data = (None)
    connection.cursor().execute(sql, data)
    connection.commit()

if __name__ == "__main__":
    main()

>>> %Run -c $EDITOR_CONTENT
Wifi connected
Traceback (most recent call last):
  File "<stdin>", line 54, in <module>
  File "<stdin>", line 50, in main
  File "/lib/upymysql/cursors.py", line 163, in execute
  File "/lib/upymysql/cursors.py", line 311, in _query
  File "/lib/upymysql/connections.py", line 815, in query
  File "/lib/upymysql/connections.py", line 1036, in _read_query_result
  File "/lib/upymysql/connections.py", line 1319, in read
  File "/lib/upymysql/connections.py", line 983, in _read_packet
  File "/lib/upymysql/connections.py", line 399, in check_error
ValueError:
>>>

I think it may be an issue with your code.  You're not passing a tuple, in the first instance you're passing a float and in the second instance a NoneType I suspect that the function is overloaded and can either handle an iterable or a value but may stick on the None.  Try putting a comma after value in data = (value) to get data = (value, ) and see if that works.

Thank you for the reply.
Slightly modified code for clarity:
def main():
    wifi()
    connection = connect_sql()

    sql = ("INSERT INTO test (columna)"
    "VALUES (%s)")
    data = 1.0
    print(sql)
    print(data)
    connection.cursor().execute(sql, data)
    connection.commit()

    sql = ("INSERT INTO test (columna)"
    "VALUES (%s)")
    data = None
    print(sql)
    print(data)
    connection.cursor().execute(sql, data)
    connection.commit()

Output:
Wifi connected
INSERT INTO test (columna)VALUES (%s)
1.0
INSERT INTO test (columna)VALUES (%s)
None
Traceback (most recent call last):
  File "<stdin>", line 56, in <module>
  File "<stdin>", line 52, in main
  File "upymysql/cursors.py", line 163, in execute
  File "upymysql/cursors.py", line 311, in _query
  File "upymysql/connections.py", line 815, in query
  File "upymysql/connections.py", line 1036, in _read_query_result
  File "upymysql/connections.py", line 1319, in read
  File "upymysql/connections.py", line 983, in _read_packet
  File "upymysql/connections.py", line 399, in check_error
ValueError:

Have also tried with data=(None) and data=(None,) and it gives the same error.
So it looks like the execute function accepts either a single value or a tuple but the presence of a None as either causes it to fail.

Does it make sense to trap None and convert to 'NULL'?  If that's the right answer you could do it in user code, or we could patch the library to do the conversion.

If I execute:
    sql = (f'INSERT INTO test (columna) VALUES (NULL)')
    connection.cursor().execute(sql)
    connection.commit()

Then the row with a null column is inserted correctly.
The problem seems to be in the implementation of connection.cursor().execute(sql, data)
Any python None values in the data tuple are not handled correctly. Perhaps they are converted to "None" in the SQL string that is ultimately executed and NOT converted to "NULL"?
I can work around this by formatting an SQL string and using the connection.cursor().execute(sql) version of the call having substituted any None values with NULL. In an ideal world connection.cursor().execute(sql, data) should handle this itself (as seems to happen in the pure python version of mysqldb). It seems to be the generally accepted practice that using placeholders and a tuple of data values is preferable to guard against SQL injection so I'd like to try and use that version. In the absence of a fix  it would be advisable to document this limitation.
Regardless of that I'd like to thank you for doing the port from python to micropython as, as best I can tell, it's the only version available and in my case it gave a good solution. At least until I decided to change columns to allow nulls!


Windows build exe using MS VS 2009 (solution is small patch to define missing var)

<EMAIL_ADDRESS>commented:

Which version of PhantomJS are you using? Tip: run 'phantomjs --version'.
HEAD
What steps will reproduce the problem?

try building following instructions on wiki for windows exe.

What is the expected output? What do you see instead?
Build works
Which operating system are you using?
Windows Server 2003 x64
Did you use binary PhantomJS or did you compile it from source?
source
Please provide any additional information below.

FIX for me copied from :http://code.google.com/p/google-breakpad/issues/detail?id=465
src/client/windows/handler/exception_handler.cc
#if _MSC_VER >= 1400  // MSVC 2005/8
+#ifndef STATUS_INVALID_PARAMETER
+#define STATUS_INVALID_PARAMETER            ((DWORD   )0xC000000DL)
+#endif
// static
void ExceptionHandler::HandleInvalidParameter(const wchar_t* expression, const wchar_t* function

Disclaimer:
This issue was migrated on 2013-03-15 from the project's former issue tracker on Google Code, Issue #738.
:star2:   3 people had starred this issue at the time of migration.

Outdated. Minimal supported versions are MSVC2012 and above.


fixed page selector dots colors/dimensions

Issue: https://github.com/project-vagabond/covid-green-app/issues/351

Looks good to me. Unfortunately there's another ticket around accessibility of this progress (colors and size). This issue though is done.

Specifically https://github.com/project-vagabond/covid-green-app/issues/351


Restart issue

I've seen this happen sometimes on my clones, what happens is:

Reset scripts kicks in
Init scripts starts kaboom in the middle of reset script
The server completly breaks, sometimes with a few missing plugins, sometimes with no plugins at all, sometimes it ends up in a restart loop (the classic "The server is temporarily down for maintenance. Please try again later!"), etc.

This also happens on the official kaboom sometimes.
My fix for this is currently editing ~/framework/script/stop.sh and adding:
pkill -9 init.sh
pkill -9 java
pkill -9 server.sh
pkill -9 alivecheck.sh

This also happened to me before, please merge this!

yeah it also happened to me before

This also happened to me before, please merge this!
It's not a PR, I'm just asking mathias to make a better solution since I feel like mine is glitchy and wouldn't work all of the times.

Bump @kaboombot

Bumping after 7 minutes now?

@kaboombot wanna play on kaboom.pw??

Bumping after 7 minutes now?

You seem to not notice issues if I don't mention you


say type incorrectly inferred as never when using SlackEventMiddlewareArgs<'pin_added'>

Description
The SlackEventMiddlewareArgs type contains a say property that is set to type SayFn if the event contains a channel property or a item.channel property. The PinAddedEvent type does have an item.channel property, however the WhenEventHasChannelContext returns never nonetheless.
For example, the following code causes the TS error

error TS2349: This expression is not callable. Type 'never' has no call signatures.

but while running the code, you can clearly see that say correctly exists as a function:
async function handlePinAdded(
  { say }
    : SlackEventMiddlewareArgs<'pin_added'>): Promise<void> {
  await say("message");
}

I noticed that the PinAddedEvent.item property is a Record<string, unknown>, so it may be that the WhenEventHasChannelContext type function always returns never due to the unknown, but I'm not entirely clear on how that field populates. The ReactionAddedEvent also has this problem, likely because its item property is a union type of ReactionMessageItem | ReactionFileItem | ReactionFileCommentItem and only ReactionMessageItem has a channel field.
As a positive case, using SlackEventMiddlewareArgs<'message'> works correctly and TS infers say to be a SayFn.
What type of issue is this? (place an x in one of the [ ])

[x] bug
[ ] enhancement (feature request)
[ ] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version: 3.11.x
node version: 14.x
OS version(s): macOS Big Sur 11.6.6
Steps to reproduce:

Register an event handler on your app (for example,  app.event('pin_added', handlePinAdded);
Inside the function, attempt to infer the type of the say property on the event.
Call say('some message);' inside the event handler.

Expected result:
TS correctly infers the type of say to be SayFn and transpiles without errors.
Actual result:
TS incorrectly infers the type of say to be never.
Attachments:

Thanks for reporting this @wickerpopstar and for providing some repro steps. Let me take a look see and see if we can introduce a fix.

Hi @wickerpopstar! Can you try adding AllMiddlewareArgs to the type definition and see if that corrects the type resolution issue? Here's a related issue

@srajiang Thanks for the suggestion! I actually do have that in my real code, but I removed it to keep the example simple. Unfortunately, it doesn't resolve the issue as the AllMiddlewareArgs interface only contains context, logger, client, and next in its definition.

@wickerpopstar Thanks for reporting this issue. I found that this is a bug that affects pin_added and pin_removed event use cases. Here is a fix for it: https://github.com/slackapi/bolt-js/pull/1473


[CT-2037] Parsing: model ‘deprecation_date’ attribute

Parse deprecation_date: Optional[str], as configured in a model yaml property file. Should be available as a model node attribute in the manifest.
Validation

deprecation_date should be a valid datetime format(potentially configurable at the project-level?) or a special ’never’/‘unplanned’ string value
All versioned models with latest:false must declare a deprecation_date.
Only versioned models can have a non-null deprecation_date

potentially configurable at the project-level?

Yeah, this would be a vote in favor of implementing deprecation_date as a standard config (unlike version or latest).

Only versioned models can have a non-null deprecation_date

I don't think we need to enforce this. While all non-latest versioned models must be deprecated, I think a model could declare its own forthcoming deprecation, even if it's not versioned.
Taken together, I think there's a fair argument for deprecation_date as a config. It's definitely related to version/latest, conceptually and for certain validation steps, but users could also make use of it independently of model versioning.

Will we throw an error if we are past the deprecation date? #6870 mentions warnings if the date exists but it's unclear what happens after the date is in the past.

Closing in favor of implementation issue: https://github.com/dbt-labs/dbt-core/issues/7433


Undefined index: name : When >> composer install  [Date: 24-12-2020]

Script @php artisan package:discover handling the post-autoload-dump event returned with error code 1

readme header:
- Currently outdated – Update is planned – No current date


when i execute command python manange.py createdb --noinput then error occur on freebsd 12

I have a failed deployment on freebsd 12, if mezzanine doesn't support deploy on freebsd 12, ignore this issue :blush:  .
Below is the traceback info:
python3.6 manage.py createdb --noinput
Operations to perform:
Apply all migrations: admin, auth, blog, conf, contenttypes, core, django_comments, forms, galleries, generic, pages, redirects, sessions, sites, twitter
Running migrations:
Applying contenttypes.0001_initial... OK
Applying auth.0001_initial... OK
Applying admin.0001_initial... OK
Applying admin.0002_logentry_remove_auto_add... OK
Applying contenttypes.0002_remove_content_type_name... OK
Applying auth.0002_alter_permission_name_max_length... OK
Applying auth.0003_alter_user_email_max_length... OK
Applying auth.0004_alter_user_username_opts... OK
Applying auth.0005_alter_user_last_login_null... OK
Applying auth.0006_require_contenttypes_0002... OK
Applying auth.0007_alter_validators_add_error_messages... OK
Applying auth.0008_alter_user_username_max_length... OK
Applying sites.0001_initial... OK
Applying blog.0001_initial... OK
Applying blog.0002_auto_20150527_1555... OK
Applying blog.0003_auto_20170411_0504... OK
Applying conf.0001_initial... OK
Applying core.0001_initial... OK
Applying core.0002_auto_20150414_2140... OK
Applying django_comments.0001_initial... OK
Applying django_comments.0002_update_user_email_field_length... OK
Applying django_comments.0003_add_submit_date_index... OK
Applying pages.0001_initial... OK
Applying forms.0001_initial... OK
Applying forms.0002_auto_20141227_0224... OK
Applying forms.0003_emailfield... OK
Applying forms.0004_auto_20150517_0510... OK
Applying forms.0005_auto_20151026_1600... OK
Applying forms.0006_auto_20170425_2225... OK
Applying galleries.0001_initial... OK
Applying galleries.0002_auto_20141227_0224... OK
Applying generic.0001_initial... OK
Applying generic.0002_auto_20141227_0224... OK
Applying generic.0003_auto_20170411_0504... OK
Applying pages.0002_auto_20141227_0224... OK
Applying pages.0003_auto_20150527_1555... OK
Applying pages.0004_auto_20170411_0504... OK
Applying redirects.0001_initial... OK
Applying sessions.0001_initial... OK
Applying sites.0002_alter_domain_unique... OK
Applying twitter.0001_initial... OK
Creating default site record: <IP_ADDRESS>:8000 ...
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/django/db/backends/utils.py", line 63, in execute
return self.cursor.execute(sql)
File "/usr/local/lib/python3.6/site-packages/django/db/backends/sqlite3/base.py", line 331, in execute
return Database.Cursor.execute(self, query)
sqlite3.OperationalError: no such table: django_site__old
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "manage.py", line 14, in
execute_from_command_line(sys.argv)
File "/usr/local/lib/python3.6/site-packages/django/core/management/init.py", line 363, in execute_from_command_line
utility.execute()
File "/usr/local/lib/python3.6/site-packages/django/core/management/init.py", line 355, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/local/lib/python3.6/site-packages/django/core/management/base.py", line 283, in run_from_argv
self.execute(*args, **cmd_options)
File "/usr/local/lib/python3.6/site-packages/django/core/management/base.py", line 330, in execute
output = self.handle(*args, **options)
File "/usr/local/lib/python3.6/site-packages/mezzanine/core/management/commands/createdb.py", line 61, in handle
func()
File "/usr/local/lib/python3.6/site-packages/mezzanine/core/management/commands/createdb.py", line 109, in create_pages
call_command("loaddata", "mezzanine_required.json")
File "/usr/local/lib/python3.6/site-packages/django/core/management/init.py", line 130, in call_command
return command.execute(*args, **defaults)
File "/usr/local/lib/python3.6/site-packages/django/core/management/base.py", line 330, in execute
output = self.handle(*args, **options)
File "/usr/local/lib/python3.6/site-packages/django/core/management/commands/loaddata.py", line 69, in handle
self.loaddata(fixture_labels)
File "/usr/local/lib/python3.6/site-packages/django/core/management/commands/loaddata.py", line 117, in loaddata
connection.check_constraints(table_names=table_names)
File "/usr/local/lib/python3.6/site-packages/django/db/backends/sqlite3/base.py", line 290, in check_constraints
column_name, referenced_column_name,
File "/usr/local/lib/python3.6/site-packages/django/db/backends/utils.py", line 80, in execute
return super(CursorDebugWrapper, self).execute(sql, params)
File "/usr/local/lib/python3.6/site-packages/django/db/backends/utils.py", line 65, in execute
return self.cursor.execute(sql, params)
File "/usr/local/lib/python3.6/site-packages/django/db/utils.py", line 94, in exit
six.reraise(dj_exc_type, dj_exc_value, traceback)
File "/usr/local/lib/python3.6/site-packages/django/utils/six.py", line 685, in reraise
raise value.with_traceback(tb)
File "/usr/local/lib/python3.6/site-packages/django/db/backends/utils.py", line 63, in execute
return self.cursor.execute(sql)
File "/usr/local/lib/python3.6/site-packages/django/db/backends/sqlite3/base.py", line 331, in execute
return Database.Cursor.execute(self, query)
django.db.utils.OperationalError: Problem installing fixtures: no such table: django_site__old

I have de same problem.

I have found this issue is caused by the sqlite, is a bug in the new version of sqlite. may be the last version of sqlite has been fixed it. :laughing:

This is related to this issue in Django: https://code.djangoproject.com/ticket/29182.
It is caused by a new behavior introduced in sqlite 3.26.
Django has patched it in latest 2.0 and 2.1, but mezzanine does not support Django 2 yet.
The easiest fix is to not use sqlite - switch to postgres, mysql, etc. Alternatively, downgrade sqlite to < 3.26.
@xuanchengli please change the title to "no such table: django_site__old" so that others running into it can see this issue.

This still seems to be a problem.  Maybe the documentation can be updated if the default install is broken for many systems?

I'm running into the same problem is there already a fix?

#1956 has been merged and Mezzanine 5.0 supports Django 2+ 🎉


Fix typo in haproxy.cfg.erb

Description
Fixes typo in listen section, makes previously unprintable expressions, printable in http-request, http-response and default_backend.

@akmalabbasov awesome catch, thank you, can you throw together a test for this?

@rshade will do!

@tas50 thanks for info, fixed now.

Thanks for the quick fix there and for adding tests to this


FilterProvider limited by EventEmitter maxListeners?

We are using the ProviderEngine with truffle-contract - works great.  Thank you!
In our application, however, we use a lot of filters (like > 20).  And we are getting the dreaded possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
If I go in to the FilterProvider code and set the max listeners on the _ready stoplight, our problem is resolved.
My hypothesis is that when a block comes in and the asyncBlockHandlers are invoked, they are likely calling eth_getFilterChanges which are all calling _ready.await(), thus overflowing the stoplight listener list.
I'd propse that the FilterProvider take an option 'maxFilters' that can be bumped and we set the max listeners to that value || 25 (higher than the default event emitter).
I'll submit a PR shortly.

fixed here https://github.com/MetaMask/provider-engine/pull/217


Allocator protocol support?

In the light of https://wg21.link/p2047, should the quantity and quantity_point provide allocator protocol support? In other words, are there any important use cases for representation types that use dynamic allocation?

FYI @johnmcfarlane, @mathiaskreutz

Hmm, "BigInt" with allocator support? No idea, too be honest, whether that's a thing.

We did not have consensus to continue pursuing the following papers:

An allocator-aware optional type (P2047R6)
-- Extract from https://www.reddit.com/r/cpp/comments/112ef9t/202302_issaquah_iso_c_committee_trip_report_c23/.

Yes, I was there in the room when this proposal was discussed. It seems that we have plenty of people that love allocators and want to put them everywhere, and even more that hate them 😉

We do not like allocators 😃


Fix broken tests

Currently, all tests rely on AWS-hosted test data that appears to no longer exist. For now these tests have been marked as broken and are skipped in the CI, but they need to be fixed.

For the testing of generating a cice grid from mom, this is fixed by #6
For test_corners, we could find a "Core" grid file to use as test data, or it should be able to test this using a mocked grid or a test MOM grid.


Fulfill the GitHub Community Standards

Since EiffelVis is an open source project, I believe it is paramount to complete the GitHub Community Standards, found in Insights -> Community Standards to ease the way of working for potential contributors who stumble upon this repository.

Templates and a code of conduct? Seems a bit overkill for this, won't spend time on something nobody will use


Nostr coordinator publisher

The PR introduces an automatic coordinator publisher based on the protocol. The feature can be enabled/disabled in the config.

@lontivero what can I do with this?

Just to have a CI running asap I created another package output that build everything. It shouldn't be like that, it should reuse the output that we already have for the backend but I didn't have time for that. The one that build everything for the CI uses the deps-all.nix instead of the deps.nix which is used for the backend dependencies only.

Fixed most of the review comments, although I didn't have time for testing, will do it later. Draft until then.


New action request: snok/install-poetry

Action name
uses: snok/install-poetry
Reasons
snok/install-poetry

Intended usage
snok/install-poetry

I have checked the internal marketplace for similar actions and couldn't find one that works for us.

[X] I have checked the internal marketplace first

:robot: Found these results:

Check
Results
Links

CodeQL on the forked repo
:white_check_mark:
CodeQL run

Security scan:

Check
Result

No Dependabot configuration found
⛔

No CodeQL Init found
⛔

No CodeQL Analyze found
⛔

:robot: Found these results:

Check
Results
Links

CodeQL on the forked repo
:white_check_mark:
CodeQL run

Security scan:

Check
Result

No Dependabot configuration found
⛔

No CodeQL Init found
⛔

No CodeQL Analyze found
⛔

:robot: Check completed with result: ✅
Found 0 Dependabot security vulnerabilities:
0 where high and 0 where moderate.
Use this link to verify the alerts.


Multiple instances of a Fragment.

If we select a Fragment form the NavigationBar which is already open a new instance of the fragment is created. This causes unnecessary extra use of memory.
This needs to be fixed.
I'm sending a PR for this.

@garg-anuj
This has been fixed, closing this.


ci: update native-image testing to GraalVM 21

Update the native-image GitHub Actions flow to test against GraalVM 21 instead of GraalVM 20.
The change of the org.graalvm.sdk:graal-sdk to org.graalvm.sdk:nativeimage is a rename described here: https://www.graalvm.org/release-notes/JDK_21#refactoring-graalvm-sdk

@kkriske before i can look into this i may need you to help me on https://github.com/xerial/sqlite-jdbc/actions/runs/6391166703/job/17345891110
i added slf4j-api as a dependency, and it seems to be breaking the native build.

@gotson You can try and follow the exception, and add --trace-class-initialization=org.slf4j.LoggerFactory and --trace-class-initialization=ch.qos.logback.classic.Logger to the native-image arguments. That should give more insights. Since it's logger related it's probably got to do something with static logger fields in build-time classes.
I'm currently on a work trip so it'll be a week before I can look at it more closely.

@gotson You can try and follow the exception, and add --trace-class-initialization=org.slf4j.LoggerFactory and --trace-class-initialization=ch.qos.logback.classic.Logger to the native-image arguments. That should give more insights. Since it's logger related it's probably got to do something with static logger fields in build-time classes.
I'm currently on a work trip so it'll be a week before I can look at it more closely.

Thanks, i think i managed to fix it via https://github.com/xerial/sqlite-jdbc/commit/89dbda1bb21bc7df004419edb32e26f17bbb0e19
hopefully i did the right thing ! CI is now green.

hopefully i did the right thing ! CI is now green.

config in maven just for tests should be fine. I would argue against adding RuntimeClassInitialization.initializeAtBuildTime(LoggerFactory.class); to the feature. You shouldn't directly configure anything outside your own codebase, this can conflict with the existing configuration of an end user (or from logback itself if they decide to bundle one) which would prevent them from using sqlite-jdbc.
It's especially dangerous to mark external things for build-time initialization because you're not in charge of what code will be run (maybe the end user overrides the version) and this could have unintended consequences.
In the end the user will also get the same build error you got, and they'll have to fix it in the way they want.
I'll take a look next week if there's anything I can do to prevent the error it alltogether.

@gotson I've put my take on the build issue in this PR: https://github.com/xerial/sqlite-jdbc/pull/985