AppVeyor for VS 2017/2015 | Travis for g++ 7/6/5 , clang++ 3.7/3.8/3.9/4.0

All of the old test harnesses should be placed into "Allowed Failures" buckets, including VS 2015. This will let us know what commit exactly breaks a certain compiler level, albeit it would mean tests would take an additional hour to complete in the cloud (mostly because of additional XCode imaging setup).

[ ] Travis CI:

[ ] g++ 5.3
[ ] g++ 5.4
[ ] g++ 6.3
[ ] g++ 7.1
[ ] clang++ 3.6
[ ] clang++ 3.7
[ ] clang++ 3.8
[ ] clang++ 3.9
[ ] clang++ 4.0

[ ] AppVeyor:

[ ] Visual Studio 2015, Latest (allowed failure)
[ ] Visual Studio 2017, Latest

All older tests should be bundled up as "allowed failures"

The current matrix for installing and setting up Lua and stuff is going to be hard to manage to extend to all these compilers and services...
I think I need to re-architect how I grab our Lua version and how I grab the compiler, especially for things working off Ubuntu Trusty. Either that, or perhaps it's time to work with Docker for the Linux-based stuff, so I can have cleaner images...? Our build times will increase by quite a bit, but it will allow me to have access to higher versions of G++ and clang++ without hitting ppa repo links.

So right now, I have my own VS 2017 projects locally that I use to run the test suite and all. But, I need to have something that generates a VS 2017/2015 project for AppVeyor.
It... looks like it's CMake time, at least for the tests.

@ThePhD #23 sources may still be useful.

Note to self.
We should test Lua 5.1, 5.2, 5.3 and JIT on the latest compiler for each major platform (Windows, OSX, Linux).
Then, we should use the latest Lua (5.3) and test it across all of the compilers listed above. That way, we have less semi-duplicate entries and still cover a wide berth of compilers and architectures.

Latest release makes some very good headway into properly testing on all architectures and platforms, eliminating many of the issues with attempting to use REQUIRE_THROWS through the Lua API: https://github.com/ThePhD/sol2/releases/tag/v2.18.0
Next step is to actually overhaul the entire testing framework. The goal is to get acquainted with CMake, and use Docker to spin up the latest Ubuntu. The goal is to also download the lua version we want directly from the website, compile, and then build the Lua we need directly to build our tests against. @Nava2 's sources will help greatly with achieving this... but, for now.
I'm going to take a nap...

This is super useful in CMake builds:
https://github.com/LuaDist/lua
Use ExternalProject_Add() https://cmake.org/cmake/help/v3.2/module/ExternalProject.html
I could look at this if you'd like a hand.

#493 does all the heavy lifting.
When I merge that, I'll update the test harnesses all at once to use the new cmake stuff. If it works, then I can probably scrap all the ninja stuff I have, wee!

The PR for the CMakeLists has been committed.
Now it's just getting docker going to make it easy to pick a distro to use, in combination with getting appveyor up and running too...

This issue hasn't been forgotten, it's just tough to do properly.
I'm defining an external project using CMake to pull an exact version of Lua straight off their download FTP. This allows me to (flexibly) pull a target and then build it. It also enables Appveyor to be less strange, since the idea of a unified place to dump dynamic libraries, executables, headers and static/import libraries isn't exactly standardized on Windows and it would not be able to find a Lua install on Appveyor (probably).
It's been an... adventure. Hopefully I can commit something in the new few days...

test@testvb [09:10:51 PM] [~/build-sol2]
-> % ctest
Test project /home/test/build-sol2
        Start   1: tests
  1/126 Test   #1: tests ....................................   Passed    0.99 sec
        Start   2: tests_single
  2/126 Test   #2: tests_single .............................   Passed    0.99 sec
        Start   3: any_return
  3/126 Test   #3: any_return ...............................   Passed    0.00 sec
        Start   4: any_return.single
  4/126 Test   #4: any_return.single ........................   Passed    0.00 sec
        Start   5: basic
  5/126 Test   #5: basic ....................................   Passed    0.00 sec
        Start   6: basic.single
  6/126 Test   #6: basic.single .............................   Passed    0.00 sec
        Start   7: calling_lua_functions
  7/126 Test   #7: calling_lua_functions ....................   Passed    0.00 sec
        Start   8: calling_lua_functions.single
  8/126 Test   #8: calling_lua_functions.single .............   Passed    0.00 sec
        Start   9: config
  9/126 Test   #9: config ...................................   Passed    0.01 sec
        Start  10: config.single
 10/126 Test  #10: config.single ............................   Passed    0.01 sec
        Start  11: container_usertype_as_container
 11/126 Test  #11: container_usertype_as_container ..........   Passed    0.01 sec
        Start  12: container_usertype_as_container.single
 12/126 Test  #12: container_usertype_as_container.single ...   Passed    0.01 sec
        Start  13: containers
 13/126 Test  #13: containers ...............................   Passed    0.00 sec
        Start  14: containers.single
 14/126 Test  #14: containers.single ........................   Passed    0.01 sec
        Start  15: containers_as_table
 15/126 Test  #15: containers_as_table ......................   Passed    0.00 sec
        Start  16: containers_as_table.single
 16/126 Test  #16: containers_as_table.single ...............   Passed    0.01 sec
        Start  17: coroutine
 17/126 Test  #17: coroutine ................................   Passed    0.00 sec
        Start  18: coroutine.single
 18/126 Test  #18: coroutine.single .........................   Passed    0.01 sec
        Start  19: coroutine_state
 19/126 Test  #19: coroutine_state ..........................   Passed    0.00 sec
        Start  20: coroutine_state.single
 20/126 Test  #20: coroutine_state.single ...................   Passed    0.01 sec
        Start  21: customization
 21/126 Test  #21: customization ............................   Passed    0.01 sec
        Start  22: customization.single
 22/126 Test  #22: customization.single .....................   Passed    0.01 sec
        Start  23: customization_convert_on_get
 23/126 Test  #23: customization_convert_on_get .............   Passed    0.00 sec
        Start  24: customization_convert_on_get.single
 24/126 Test  #24: customization_convert_on_get.single ......   Passed    0.00 sec
        Start  25: dynamic_object
 25/126 Test  #25: dynamic_object ...........................   Passed    0.01 sec
        Start  26: dynamic_object.single
 26/126 Test  #26: dynamic_object.single ....................   Passed    0.01 sec
        Start  27: environment_snooping
 27/126 Test  #27: environment_snooping .....................   Passed    0.01 sec
        Start  28: environment_snooping.single
 28/126 Test  #28: environment_snooping.single ..............   Passed    0.01 sec
        Start  29: environment_state
 29/126 Test  #29: environment_state ........................   Passed    0.00 sec
        Start  30: environment_state.single
 30/126 Test  #30: environment_state.single .................   Passed    0.01 sec
        Start  31: environment_state_2
 31/126 Test  #31: environment_state_2 ......................   Passed    0.01 sec
        Start  32: environment_state_2.single
 32/126 Test  #32: environment_state_2.single ...............   Passed    0.00 sec
        Start  33: environments
 33/126 Test  #33: environments .............................   Passed    0.00 sec
        Start  34: environments.single
 34/126 Test  #34: environments.single ......................   Passed    0.01 sec
        Start  35: environments_on_functions
 35/126 Test  #35: environments_on_functions ................   Passed    0.00 sec
        Start  36: environments_on_functions.single
 36/126 Test  #36: environments_on_functions.single .........   Passed    0.01 sec
        Start  37: functions
 37/126 Test  #37: functions ................................   Passed    0.01 sec
        Start  38: functions.single
 38/126 Test  #38: functions.single .........................   Passed    0.00 sec
        Start  39: indirect_function_calls
 39/126 Test  #39: indirect_function_calls ..................   Passed    0.01 sec
        Start  40: indirect_function_calls.single
 40/126 Test  #40: indirect_function_calls.single ...........   Passed    0.00 sec
        Start  41: multi_results
 41/126 Test  #41: multi_results ............................   Passed    0.01 sec
        Start  42: multi_results.single
 42/126 Test  #42: multi_results.single .....................   Passed    0.01 sec
        Start  43: optional_with_iteration
 43/126 Test  #43: optional_with_iteration ..................   Passed    0.01 sec
        Start  44: optional_with_iteration.single
 44/126 Test  #44: optional_with_iteration.single ...........   Passed    0.01 sec
        Start  45: overloading
 45/126 Test  #45: overloading ..............................   Passed    0.00 sec
        Start  46: overloading.single
 46/126 Test  #46: overloading.single .......................   Passed    0.01 sec
        Start  47: overloading_with_fallback
 47/126 Test  #47: overloading_with_fallback ................   Passed    0.00 sec
        Start  48: overloading_with_fallback.single
 48/126 Test  #48: overloading_with_fallback.single .........   Passed    0.00 sec
        Start  49: pairs
 49/126 Test  #49: pairs ....................................   Passed    0.01 sec
        Start  50: pairs.single
 50/126 Test  #50: pairs.single .............................   Passed    0.00 sec
        Start  51: pairs_with_raw_functions
 51/126 Test  #51: pairs_with_raw_functions .................   Passed    0.01 sec
        Start  52: pairs_with_raw_functions.single
 52/126 Test  #52: pairs_with_raw_functions.single ..........   Passed    0.01 sec
        Start  53: protected_functions
 53/126 Test  #53: protected_functions ......................   Passed    0.00 sec
        Start  54: protected_functions.single
 54/126 Test  #54: protected_functions.single ...............   Passed    0.01 sec
        Start  55: require
 55/126 Test  #55: require ..................................   Passed    0.00 sec
        Start  56: require.single
 56/126 Test  #56: require.single ...........................   Passed    0.00 sec
        Start  57: runtime_additions
 57/126 Test  #57: runtime_additions ........................   Passed    0.01 sec
        Start  58: runtime_additions.single
 58/126 Test  #58: runtime_additions.single .................   Passed    0.01 sec
        Start  59: script_error_handling
 59/126 Test  #59: script_error_handling ....................   Passed    0.01 sec
        Start  60: script_error_handling.single
 60/126 Test  #60: script_error_handling.single .............   Passed    0.00 sec
        Start  61: self_from_lua
 61/126 Test  #61: self_from_lua ............................   Passed    0.01 sec
        Start  62: self_from_lua.single
 62/126 Test  #62: self_from_lua.single .....................   Passed    0.01 sec
        Start  63: singleton
 63/126 Test  #63: singleton ................................   Passed    0.01 sec
        Start  64: singleton.single
 64/126 Test  #64: singleton.single .........................   Passed    0.00 sec
        Start  65: stack_aligned_function
 65/126 Test  #65: stack_aligned_function ...................   Passed    0.01 sec
        Start  66: stack_aligned_function.single
 66/126 Test  #66: stack_aligned_function.single ............   Passed    0.00 sec
        Start  67: static_variables
 67/126 Test  #67: static_variables .........................   Passed    0.01 sec
        Start  68: static_variables.single
 68/126 Test  #68: static_variables.single ..................   Passed    0.01 sec
        Start  69: tables
 69/126 Test  #69: tables ...................................   Passed    0.01 sec
        Start  70: tables.single
 70/126 Test  #70: tables.single ............................   Passed    0.00 sec
        Start  71: usertype
 71/126 Test  #71: usertype .................................   Passed    0.00 sec
        Start  72: usertype.single
 72/126 Test  #72: usertype.single ..........................   Passed    0.00 sec
        Start  73: usertype_advanced
 73/126 Test  #73: usertype_advanced ........................   Passed    0.01 sec
        Start  74: usertype_advanced.single
 74/126 Test  #74: usertype_advanced.single .................   Passed    0.01 sec
        Start  75: usertype_automatic_operators
 75/126 Test  #75: usertype_automatic_operators .............   Passed    0.00 sec
        Start  76: usertype_automatic_operators.single
 76/126 Test  #76: usertype_automatic_operators.single ......   Passed    0.00 sec
        Start  77: usertype_bitfields
 77/126 Test  #77: usertype_bitfields .......................   Passed    0.00 sec
        Start  78: usertype_bitfields.single
 78/126 Test  #78: usertype_bitfields.single ................   Passed    0.01 sec
        Start  79: usertype_call_from_c++
 79/126 Test  #79: usertype_call_from_c++ ...................   Passed    0.01 sec
        Start  80: usertype_call_from_c++.single
 80/126 Test  #80: usertype_call_from_c++.single ............   Passed    0.01 sec
        Start  81: usertype_dynamic_getter_setter
 81/126 Test  #81: usertype_dynamic_getter_setter ...........   Passed    0.01 sec
        Start  82: usertype_dynamic_getter_setter.single
 82/126 Test  #82: usertype_dynamic_getter_setter.single ....   Passed    0.01 sec
        Start  83: usertype_initializers
 83/126 Test  #83: usertype_initializers ....................   Passed    0.01 sec
        Start  84: usertype_initializers.single
 84/126 Test  #84: usertype_initializers.single .............   Passed    0.00 sec
        Start  85: usertype_simple
 85/126 Test  #85: usertype_simple ..........................   Passed    0.01 sec
        Start  86: usertype_simple.single
 86/126 Test  #86: usertype_simple.single ...................   Passed    0.00 sec
        Start  87: usertype_special_functions
 87/126 Test  #87: usertype_special_functions ...............   Passed    0.00 sec
        Start  88: usertype_special_functions.single
 88/126 Test  #88: usertype_special_functions.single ........   Passed    0.00 sec
        Start  89: usertype_var
 89/126 Test  #89: usertype_var .............................   Passed    0.00 sec
        Start  90: usertype_var.single
 90/126 Test  #90: usertype_var.single ......................   Passed    0.00 sec
        Start  91: variables
 91/126 Test  #91: variables ................................   Passed    0.00 sec
        Start  92: variables.single
 92/126 Test  #92: variables.single .........................   Passed    0.00 sec
        Start  93: variadic_args
 93/126 Test  #93: variadic_args ............................   Passed    0.00 sec
        Start  94: variadic_args.single
 94/126 Test  #94: variadic_args.single .....................   Passed    0.00 sec
        Start  95: functions_all
 95/126 Test  #95: functions_all ............................   Passed    0.00 sec
        Start  96: functions_all.single
 96/126 Test  #96: functions_all.single .....................   Passed    0.00 sec
        Start  97: functions_easy
 97/126 Test  #97: functions_easy ...........................   Passed    0.00 sec
        Start  98: functions_easy.single
 98/126 Test  #98: functions_easy.single ....................   Passed    0.00 sec
        Start  99: make_tables
 99/126 Test  #99: make_tables ..............................   Passed    0.00 sec
        Start 100: make_tables.single
100/126 Test #100: make_tables.single .......................   Passed    0.00 sec
        Start 101: multiple_returns_from_lua
101/126 Test #101: multiple_returns_from_lua ................   Passed    0.00 sec
        Start 102: multiple_returns_from_lua.single
102/126 Test #102: multiple_returns_from_lua.single .........   Passed    0.00 sec
        Start 103: multiple_returns_to_lua
103/126 Test #103: multiple_returns_to_lua ..................   Passed    0.00 sec
        Start 104: multiple_returns_to_lua.single
104/126 Test #104: multiple_returns_to_lua.single ...........   Passed    0.00 sec
        Start 105: namespacing
105/126 Test #105: namespacing ..............................   Passed    0.00 sec
        Start 106: namespacing.single
106/126 Test #106: namespacing.single .......................   Passed    0.00 sec
        Start 107: opening_a_state
107/126 Test #107: opening_a_state ..........................   Passed    0.00 sec
        Start 108: opening_a_state.single
108/126 Test #108: opening_a_state.single ...................   Passed    0.00 sec
        Start 109: opening_state_on_raw_lua
109/126 Test #109: opening_state_on_raw_lua .................   Passed    0.00 sec
        Start 110: opening_state_on_raw_lua.single
110/126 Test #110: opening_state_on_raw_lua.single ..........   Passed    0.00 sec
        Start 111: running_lua_code
111/126 Test #111: running_lua_code .........................   Passed    0.00 sec
        Start 112: running_lua_code.single
112/126 Test #112: running_lua_code.single ..................   Passed    0.00 sec
        Start 113: running_lua_code_low_level
113/126 Test #113: running_lua_code_low_level ...............   Passed    0.00 sec
        Start 114: running_lua_code_low_level.single
114/126 Test #114: running_lua_code_low_level.single ........   Passed    0.00 sec
        Start 115: self_call
115/126 Test #115: self_call ................................   Passed    0.00 sec
        Start 116: self_call.single
116/126 Test #116: self_call.single .........................   Passed    0.00 sec
        Start 117: set_and_get_variables
117/126 Test #117: set_and_get_variables ....................   Passed    0.00 sec
        Start 118: set_and_get_variables.single
118/126 Test #118: set_and_get_variables.single .............   Passed    0.00 sec
        Start 119: set_and_get_variables_exists
119/126 Test #119: set_and_get_variables_exists .............   Passed    0.00 sec
        Start 120: set_and_get_variables_exists.single
120/126 Test #120: set_and_get_variables_exists.single ......   Passed    0.00 sec
        Start 121: tables_and_nesting
121/126 Test #121: tables_and_nesting .......................   Passed    0.00 sec
        Start 122: tables_and_nesting.single
122/126 Test #122: tables_and_nesting.single ................   Passed    0.00 sec
        Start 123: userdata
123/126 Test #123: userdata .................................   Passed    0.00 sec
        Start 124: userdata.single
124/126 Test #124: userdata.single ..........................   Passed    0.00 sec
        Start 125: usertypes
125/126 Test #125: usertypes ................................   Passed    0.00 sec
        Start 126: usertypes.single
126/126 Test #126: usertypes.single .........................   Passed    0.01 sec

100% tests passed, 0 tests failed out of 126

Total Test time (real) =   2.73 sec

It's beautiful.

At long laaast: https://ci.appveyor.com/project/ThePhD/sol2/build/2.19.0-49

TODO:

[ ] LuaJIT in-house build using LuaJITBuild.cmake rather than trying to finagle with the sources themselves
[ ] Use docker + travis-ci to get going rather than trying to muck around with travis's image restrictions and the like (just ensure build time is under 5 minutes)

docker makes me extremely sad.

What's broken? Usually docker makes things smoother, specially compared to travis default image

@henriquegemignani Environment variables and their transfer to the docker-compose and docker runners is extremely fragile and does not follow what it says in the documentation.
The docs state that if I have a docker-compose file, all I need to do is specify the environment variable without a name under the environment: block, and its value (if it exists) will be transferred over.
It is NOT doing that for me.
Not to mention that environment variables set in docker-compose build by my build script are not preserved in the image, and when I do docker-compose run test they just disappear, so I have to make sure that docker-compose build has the same environment variables, and then use -e "VAR=VAL" for each and every environment variable I want to pass through.
Suffice to say, I am not having a good time with this.

What are you using docker-compose for, in the context of a CI build?
I'll admit I haven't used docker-compose that well. I usually just build images and then either use something to push, or an ad-hoc script do run then.
Are these variables in the environment: block accessible during the run step, at least?

@henriquegemignani My problem was that I was using docker-compose.
Not anymore, though.
Most blogs and articles about docker-compose shipped it as the way to run your tests easily, wrapping up multiple setups in one easy call to docker-compose up, a script in the middle, and then docker-composer down.
The problem with this is that this was for -- as reading deeper provided me with -- dealing with when you needed to have multiple services isolated and then taken care of. I had no such need, so my docker compose was just being spun up, only for me to take it down the next command. docker-compose and docker also are not very honest with how variables are propagated from the .env file, --env-file, --env/-e commands passed to the build and work stages.
docker-compose up's environment variables are NOT made available during docker build image ...: this was truly bad because the environment variables did not show up unless I explicitly propagated them through. Similarly, docker build image ... did NOT take any of my environment variables into the build of the Dockerfile: rather, I had to pass them as --build-arg "NAME=VALUE", name them in the Dockerfile with ARG NAME, and then also pass each named arg into ENV NAME=${NAME} for it to FINALLY show up in my docker build image and affect the scripts run in my Dockerfile.
But don't stop there, because this has NOTHING to do with docker run {image name}, whereupon you need to pass the exact same environment variables AGAIN. And the best part is, of course, docker run ... and docker build image -- contrary to the docs -- do NOT default environment variable values that you name without a value (e.g., --env MY_VAR) to the value in the shell. Indeed: I explicitly ran export GCC_VERSION=7 in the shell, called docker run sol2:ci --env GCC_VERSION, and it did not propogate the value of GCC_VERSION. In fact, GCC_VERSION didn't exist at all, which was super, duper great to debug for a good day and a half of free time.
Oh. And don't forget: VOLUME doesn't work on VirtualBox shared folders. Why? Who knows: the virtual box bug for this has been open for some 3, 4 years now. And so instead of making a sol2:ci image that references a folder that already exists without copying, I had to debug by throwing in the entire sol2 repo -- and all my testing files that are ignored by .gitignore -- into Docker's image to get going. Thankfully, I later learned they have .dockerignore, which is pretty much exactly like .gitignore, so I could avoid some copy time. But even then, without VOLUME, every time I needed to test environment vars? Well, time to copy into Docker. Then build the docker image. Then wait for something to happen after sudo apt-get install ... runs for the 400th time with the 8 dependencies I have, plus any branches taken because of the decisions made by environment variables.
All in all, now that I've figured it out I'm just never going to touch it. At least CMake made sense when I figured it out: Docker just has esoteric behavior and straight up violates its own documentation at times, and the only way to get anything done with it is to specify every option, every command, every command line with rigor and intense study.
I would say I feel like a wizard, but all I feel like is a sap. I also dislike travis-ci for not just... you know. Making their Ubuntu LTS images standardize on the latest. But they're a business and I'm sure they have business reasons for dragging their feet and making it opt-in.
Either way, I never want to CI this repo again for all of 2018. Which is a shame, because I still need to write a CMake script to build LuaJIT, which uses its own complex series of specifically invoked command line arcanery per-platform...
Can't wait.

I don't think you were trying to use the environment variables for the usual docker flow. Checking the Dockerfile you commited along with the .travis.yml I don't think that's a good use for docker build.
If you want, I can make some improvements to your docker images. What I recommend. for running via travis:
Create a docker image that contains all your environment dependencies: in your case I believe that's only the compilers? Publish this image to Docker Hub, preferably using theirs automated image build.
On the travis.yml, you would just pull that image and then docker run, possibly mapping the code with volumes or just cloning inside the container.

I would certainly appreciate any pointers on what to do. I have no idea what I'm doing and I'm just trying to make it so I can docker build the right thing based on the environment variables I pass in right now. If I should pre-process this step and turn it into something done outside build time, that'd be nice too.


Publish move-core-types v0.0.4

Branch: testnet
I'm trying to build a StructTag, however I have no way to import the type, since all sui crates use the unpublished move-core-types v0.0.4 crates.
Publishing it would allow me to depend on it. Or, is the crate re-exported somewhere by one of the sui crates?
EDIT: Are we expected to have this in our Cargo.toml?
move-core-types = {git = "https://github.com/MystenLabs/sui", branch = "testnet"}

Hi @plafer, I assume you managed to figure it out, but if not, please feel free to create a new issue. Closing this #cleanup,


Failed to create GitLab release through API: Response code 403 (Forbidden)

Hi,
When running the following command:
semantic-delivery-gitlab --token xxxxxxxxx
I've got the following error:
semantic-delivery-gitlab failed for the following reason - Error: Failed to create GitLab release through API: Response code 403 (Forbidden)
My token have API right.
Thank you for your help.

Solved !
We need to have  'repository' property of package.json pointing on your repository !


The flutter create command should be allowed in some directories in the repo

Currently, there are multiple directories in the repo that contain the shims needed to run an app: dev/integration_tests, dev/manual_tests, and examples to name a few.
It would be helpful if, instead of preventing it outright, the flutter create command would allow itself to be run in a select subset of directories inside of the Flutter repo itself.  This would make updating the shims easier, but still protect new users from the confusion of creating their projects inside of the repo.

Context in https://github.com/flutter/flutter/issues/6480

Context in https://github.com/flutter/flutter/issues/6480


Add docker build for whisper-ctranslate2

This PR add a new build to create a Peertube runner image with whisper-ctranslate2.

All of this should be configurable using an environment variable.

There is now new environment variable to configure the engine, the engine path and the model to use.
See 3660840c5cfdc6813953cde5a55fbbbb8887b7f4
And I add in the tray to possibility to chose the model to use.


404 not found when start uploading

I did all as explained, i don't know what to do next, the problem i get is in the upload.php file, I get 404 not found :
this is shown in my console:
GET http://cich.local/upload.php?flowChunkNumber=1&flowChunkSize=1048576&flowCu…lowRelativePath=myimage.jpg&flowTotalChunks=1 404 (Not Found)
I did not modify the upload.php file. I thought i should use this together with the php-flow-server, but i couldn't integrate it with my laravel project, the composer didn't download anything.

To me it seems that the server-side works like this. The GET resource is called first to check whether the chunk has been deployed - if not - throw NOT_FOUND and then call the POST resource which should actually deploy the chunk.
I've noticed that the POST resource is not even called if NOT_FOUND is not thrown from the GET which seems odd as Exceptions are expensive and one shouldn't rely on them in order for the functionality to work properly.

Have we had a solution about this ? I get 404 when starting upload

Pass "testChunks:false" in the flow-init:

thanks @leefsmp ..........plz close post the solutions is right.

im using div flow-init="{target: 'app/main/upload', testChunks:false}" still getting
POST http://localhost:3000/app/main/upload 404 (Not Found).. what could be the problem>??  and relativePath is coming as filename only.. any solution to upload the file?

404 is an expected response, please read more here: https://github.com/flowjs/flow.js

thank you @AidasK but file is not getting stored inside upload folder.. it should get stored inside specified folder right ie./app/main/upload i have folder named 'upload'?? sorry if i am wrong.

i understood that /upload is api name and not the folder.. i have used [https://github.com/flowjs/flow.js/tree/master/samples/Node.js] which has upload api and specified folder name in that.


wip: hatch

This pull request primarily focuses on transitioning the project to use Hatch for Python environment and build management, replacing previous tools like setuptools. It also includes updates to the documentation and configuration files to reflect this change.
Hatch will use uv under the hood for fast downloading, while hatch manages the orchestration of creating environment and running tasks.
This makes running tests locally much more reproducible to CI.
Docs will fail until this is merged and will updates docs deployment (otherwise updating now will make other branches fail).

@anthonywu, I'm not all that familiar with it, it does seem like the best choice to run different python versions and dep matrices locally.
Do you think you could be one of the reviewers? Would appreciate your expertise if you know it well.

@akshayka, yes that is much better. i will keep the docs and testing deps out of "[dev]" though, to encourage running them in the isolated envs


Support for render image other ways

Need some other way to print image in report. Ex. Img binary, base64, stream.

I'm not sure what you are asking.   The report itself is a PDF; so when you embed the image inside it; you get a image in any PDF viewer.

I found that i can use buffer for Rpt.image now. then this issue can close. But its not written in the document.


Update Pulumi projects to net6.0

.NET Core 3.1 is out of support on December 13th:
https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core
We've already stopped testing on .NET Core 3.1, and program gen has been targeting only 6.0 for a while now as well.
This updates the core porjects to only 6.0 as well.
We'll still want to do https://github.com/pulumi/pulumi/pull/11543 in pu/pu to update sdkgen.

hah null reference checks are now running, got some annotations to add it seems


Github and firewall issue?

OK, here's my newbie question: got to the point of creating my local repository. Got this error:
fatal:unable to access 'https://github.com/marillenkrapfen/nacis2015-map.git/': error: 140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
Is there any way I can change my configuration to allow this to work?
Thanks for the help.

I haven't seen this one before.
Can you provide some more information to help diagnose it?
What operating system are you on?  Are you using Git on the commandline or in a GUI client?
What operation were you doing when you got this message?
I did verify the URL that you are using, and it is correct.  This error is usually due to outdated SSL libraries on your computer, or incompatible versions between those on your computer and the ones on the server.

Thanks -- I have Windows 7 and have just followed the basic steps outlined in the project pages -- installed Git, used command line (Git Bash) to configure with my user name and email, then used git clone with my url to run the clone to my local machine. This is what runs into the error. I have attempted the cloning using the little GUI tool and it generates the same error. I have attempted to create the local repository in a couple of different places on my C:/ drive and got the same result. I see there is an ssl folder in the git install but I have not changed anything there. All the files are the most recent ones that came with the latest Git install.
Thanks for any thoughts.

@marillenkrapfen - Are you by chance using any of this on a closed network (or work machine)?
A resolution I happened upon says the following:

Turns out my company’s network suddenly blocked the IP and port number, thus not allowing me to access it. So, be sure to ping it from whatever network you’re on if you receive a similar issue.

Yes, I am and it is probable that there is a firewall issue -- I was hoping there might be a way to pass in the url or configure some sort of permissions file to get around the blockage. I just don't know where to begin with that, though, if it is possible.

@marillenkrapfen: Were you able to diagnose the problem?

No, I tried assigning a different port using the git bash console and that didn't work. I'm sure it is a firewall/proxy issue because my work environment pretty much completely blocks the outside world, but I was too busy with other work and I gave up. Thanks for asking -- if I ever hear of a way around this I will let you know.

Hey, got it -- you inspired me to try again and I found the right way to configure the proxy. I used this format:
git config --global http.proxy http://mydomain\myusername:mypassword@myproxyserver:8080
Then tried git clone again, and it worked.
Here is the webpage that gave it to me:
http://stackoverflow.com/questions/128035/how-do-i-pull-from-a-git-repository-through-an-http-proxy
Thanks to all for the input!

Hooray, that's great news! Thanks for sharing! :+1:

Closing since you were a :guitar::star2: and solved this!

:blush: :grinning:


AntiPattern getInitialState

Hi, whilst looking further at the component to possibly fix the serverside rendering issue I noticed the copyPropsToState - this seems like an antipattern why do this here?
https://facebook.github.io/react/tips/props-in-getInitialState-as-anti-pattern.html
getInitialState() {
return this.copyPropsToState(this.props);
},

Many components I see today still uses the antipattern. I have to rewrite their code.


Terminal hover positioning is unfriendly

have a long'ish link, like echo https://github.com/microsoft/vscode/pull/162335
mouse-hover over the number
:bug: the link hover appears left aligned, ignores my mouse x-coordinate, and forces me to move the cursor into it (which can be finicky)

https://user-images.githubusercontent.com/1794099/193029983-cc12425a-8d2f-4359-88a5-ee9e5ed74f8c.mov

The terminal does exactly what the editor does:

@daviddossett these are general editor hovers rules I think, for example it works well here as you read the symbol and info is directly above:

Not sure about the decision that went into that, but it's probably something around keyboard interaction being the typical way to trigger the hovers, which doesn't apply as much to links.

Do we know if there's a good reason we haven't respected the mouse position in the editor case? Seems like it would be a good idea to update both if there isn't one.

The reason was, as @Tyriar mentioned, to align the hover with the current word / symbol being hovered. Over the years, we've added a range property to a hover result, where a hover provider can express what range their hover applies to, and we moved to use that. Most of the times, that range is something sensible, like the current word/symbol. But I agree that this doesn't work very well if the range is a lot larger, if it begins far away from the mouse position or on a wrapped line, etc. This came up a lot over the years, I'll look into improving things.

Was able to repro this today on stable 1.95.3(f1a4fb) so the issue still exists.


How to close SSL verify?

Encountered with "Fatal error on SSL transport", and I am so confused in reading "sslproto.py", don't know how to cancel SSL.

Traceback (most recent call last):
File "E:\sankaku-main\venv\searchid.py", line 12, in
asyncio.run(main())
File "C:\Users\86188\AppData\Local\Programs\Python\Python310\lib\asyncio\runners.py", line 44, in run
return loop.run_until_complete(main)
File "C:\Users\86188\AppData\Local\Programs\Python\Python310\lib\asyncio\base_events.py", line 646, in run_until_complete
return future.result()
File "E:\sankaku-main\venv\searchid.py", line 9, in main
post = await client.get_post(post_id)
File "E:\sankaku-main\sankaku\clients\clients.py", line 315, in get_post
return mdl.Post(**response.json)
File "E:\sankaku-main\venv\lib\site-packages\pydantic\main.py", line 165, in init
pydantic_self.pydantic_validator.validate_python(data, self_instance=pydantic_self)
pydantic_core._pydantic_core.ValidationError: 1 validation error for Post
reactions
Extra inputs are not permitted [type=extra_forbidden, input_value=[], input_type=list]
For further information visit https://errors.pydantic.dev/2.3/v/extra_forbidden
Fatal error on SSL transport
protocol: <asyncio.sslproto.SSLProtocol object at 0x000001D56A140C10>
transport: <_ProactorSocketTransport fd=368 read=<_OverlappedFuture cancelled>>
Traceback (most recent call last):
File "C:\Users\86188\AppData\Local\Programs\Python\Python310\lib\asyncio\sslproto.py", line 690, in _process_write_backlog
self._transport.write(chunk)
File "C:\Users\86188\AppData\Local\Programs\Python\Python310\lib\asyncio\proactor_events.py", line 361, in write
self._loop_writing(data=bytes(data))
File "C:\Users\86188\AppData\Local\Programs\Python\Python310\lib\asyncio\proactor_events.py", line 397, in _loop_writing
self._write_fut = self._loop._proactor.send(self._sock, data)
AttributeError: 'NoneType' object has no attribute 'send'
Exception ignored in: <function _SSLProtocolTransport.del at 0x000001D56891B130>
Traceback (most recent call last):
File "C:\Users\86188\AppData\Local\Programs\Python\Python310\lib\asyncio\sslproto.py", line 321, in del
File "C:\Users\86188\AppData\Local\Programs\Python\Python310\lib\asyncio\sslproto.py", line 316, in close
File "C:\Users\86188\AppData\Local\Programs\Python\Python310\lib\asyncio\sslproto.py", line 599, in _start_shutdown
File "C:\Users\86188\AppData\Local\Programs\Python\Python310\lib\asyncio\sslproto.py", line 604, in _write_appdata
File "C:\Users\86188\AppData\Local\Programs\Python\Python310\lib\asyncio\sslproto.py", line 712, in _process_write_backlog
File "C:\Users\86188\AppData\Local\Programs\Python\Python310\lib\asyncio\sslproto.py", line 726, in _fatal_error
File "C:\Users\86188\AppData\Local\Programs\Python\Python310\lib\asyncio\proactor_events.py", line 151, in _force_close
File "C:\Users\86188\AppData\Local\Programs\Python\Python310\lib\asyncio\base_events.py", line 750, in call_soon
File "C:\Users\86188\AppData\Local\Programs\Python\Python310\lib\asyncio\base_events.py", line 515, in _check_closed
RuntimeError: Event loop is closed

import asyncio
from sankaku.clients import PostClient
async def main():
client = PostClient()
await client.login(access_token=r"") #censored
post_id: int = 34326859  # Here the ID of the post you interested in
post = await client.get_post(post_id)
print(post.file_url)
asyncio.run(main())

It worked fine several days ago, though.

According to following part in traceback I made a conclusion that an actual error is triggered because of new field in JSON response model from SankakuComplex servers:

pydantic_core._pydantic_core.ValidationError: 1 validation error for Post
reactions
Extra inputs are not permitted [type=extra_forbidden, input_value=[], input_type=list]
For further information visit https://errors.pydantic.dev/2.3/v/extra_forbidden

After updating some models (PageBook and Post models) I run library tests and all of them were passed. So i uploaded new version of sankaku to PyPI (v2.0.1).
Does your issue is still present after updating?

I' ve install the latest version of your sankaku package, but the problem still exsists

E:\s2\pythonProject\venv\Scripts\Scripts\python.exe E:\s2\pythonProject\test.py
Traceback (most recent call last):
File "E:\s2\pythonProject\venv\Scripts\lib\site-packages\sankaku\clients\clients.py", line 48, in _login_via_access_token
self._profile = await self._get_profile(access_token)
File "E:\s2\pythonProject\venv\Scripts\lib\site-packages\sankaku\clients\clients.py", line 65, in _get_profile
raise errors.SankakuServerError(
sankaku.errors.SankakuServerError: [401] Failed to get user profile: success=False, code=snackbar__common_unauthorized, error=snackbar__common_unauthorized, errorId=error_939fe9e3ebd73af3.

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "E:\s2\pythonProject\test.py", line 12, in
asyncio.run(main())
File "C:\Users\86188\AppData\Local\Programs\Python\Python39\lib\asyncio\runners.py", line 44, in run
return loop.run_until_complete(main)
File "C:\Users\86188\AppData\Local\Programs\Python\Python39\lib\asyncio\base_events.py", line 647, in run_until_complete
return future.result()
File "E:\s2\pythonProject\test.py", line 6, in main
await client.login(access_token=r"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOjEyNjIwMDQsInN1Ykx2bCI6MCwiaXNzIjoiaHR0cHM6Ly9jYXBpLXYyLnNhbmtha3Vjb21wbGV4LmNvbSIsInR5cGUiOiJCZWFyZXIiLCJhdWQiOiJjb21wbGV4Iiwic2NvcGUiOiJjb21wbGV4IiwiaWF0IjoxNjk0MzQ4MDg2LCJleHAiOjE2OTQ5NTI4ODZ9.hfQxLfQ9og2XMlrd1T5evh_EFttfZQBqIkU5-9mESuU")
File "E:\s2\pythonProject\venv\Scripts\lib\site-packages\sankaku\clients\clients.py", line 90, in login
await self._login_via_access_token(access_token)
File "E:\s2\pythonProject\venv\Scripts\lib\site-packages\sankaku\clients\clients.py", line 53, in _login_via_access_token
raise errors.AuthorizationError(e.status, **e.kwargs)
sankaku.errors.AuthorizationError: [401] Authorization failed: success=False, code=snackbar__common_unauthorized, error=snackbar__common_unauthorized, errorId=error_939fe9e3ebd73af3.
Fatal error on SSL transport
protocol: <asyncio.sslproto.SSLProtocol object at 0x000001FB220D92B0>
transport: <_ProactorSocketTransport fd=844 read=<_OverlappedFuture cancelled>>
Traceback (most recent call last):
File "C:\Users\86188\AppData\Local\Programs\Python\Python39\lib\asyncio\sslproto.py", line 690, in _process_write_backlog
self._transport.write(chunk)
File "C:\Users\86188\AppData\Local\Programs\Python\Python39\lib\asyncio\proactor_events.py", line 359, in write
self._loop_writing(data=bytes(data))
File "C:\Users\86188\AppData\Local\Programs\Python\Python39\lib\asyncio\proactor_events.py", line 395, in _loop_writing
self._write_fut = self._loop._proactor.send(self._sock, data)
AttributeError: 'NoneType' object has no attribute 'send'
Exception ignored in: <function _SSLProtocolTransport.del at 0x000001FB2094ECA0>
Traceback (most recent call last):
File "C:\Users\86188\AppData\Local\Programs\Python\Python39\lib\asyncio\sslproto.py", line 321, in del
File "C:\Users\86188\AppData\Local\Programs\Python\Python39\lib\asyncio\sslproto.py", line 316, in close
File "C:\Users\86188\AppData\Local\Programs\Python\Python39\lib\asyncio\sslproto.py", line 599, in _start_shutdown
File "C:\Users\86188\AppData\Local\Programs\Python\Python39\lib\asyncio\sslproto.py", line 604, in _write_appdata
File "C:\Users\86188\AppData\Local\Programs\Python\Python39\lib\asyncio\sslproto.py", line 712, in _process_write_backlog
File "C:\Users\86188\AppData\Local\Programs\Python\Python39\lib\asyncio\sslproto.py", line 726, in _fatal_error
File "C:\Users\86188\AppData\Local\Programs\Python\Python39\lib\asyncio\proactor_events.py", line 151, in _force_close
File "C:\Users\86188\AppData\Local\Programs\Python\Python39\lib\asyncio\base_events.py", line 751, in call_soon
File "C:\Users\86188\AppData\Local\Programs\Python\Python39\lib\asyncio\base_events.py", line 515, in _check_closed
RuntimeError: Event loop is closed
Process finished with exit code 1

Have you tried to login with username and password instead of access token?

Yeah, it is the access token's problem.
It changes over time, OMG.

(Lower line is the new access token.)


Widget for image captioning

Would have as input

Image

Would output

Text

This should be similar in implementation to the image classification widget.

I've implement ImageCaptioningWidget here.
input/request: identical to ImageClassificationWidget
const requestBody = { file }; // uploaded image
output/response: identical to TextGenerationWidget
[   {     "generated_text": "..."   } ]
Questions:

I've assumed ImageCaptioningWidget api contract (request and response specifications) from similar widgets. Please let me know if there's a better way to find api contracts for the widgets
What modelId should I supply here?
Would there be icon for ImageCaptioingWidget?
Is there a preferred way to mock/stub the api response?

That's very cool! Feel free to open a draft PR so we can discuss over code 😄

Your proposed API contract seems fine to me. I'll send a PR to add this pipeline (FYI @Narsil in case you have ideas)
At the moment we have no model for this task. You can remove it for the time being :)
Yes, we should have an icon. @julien-c any ideas?

LGTM too.

There are not "spec" like openAPI or something like it, aside from code right now.

@osanseviero removed ModelData from widgets/src/routes/index.svelte and opened a draft PR #115

Would there be icon for ImageCaptioingWidget?

Feel free to propose one @mishig25!

@mishig25 our icon style is from https://icones.js.org/collection/carbon (cc @gary149)

@osanseviero

At the moment we have no model for this task. You can remove it for the time being :)

Let's plan to add/build one otherwise this widget won't be terribly useful :)

Let's plan to add/build one otherwise this widget won't be terribly useful :)

Yeah, I'm on it right now :)
#114 added the pipeline to the API validation, now we need to add it to one of the docker images (I was thinking to a new Keras image).

@julien-c how does this one look: carbon:align-box-bottom-center ?

@mishig25 yeah looks good to me

@julien-c add the icon and pushed the changes


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-main" workflow

Codecov Report

Merging #589 (464d46b) into main (35ee28b) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main     #589   +/-   ##
=======================================
  Coverage   95.69%   95.69%
=======================================
  Files           1        1
  Lines         395      395
  Branches       53       53
=======================================
  Hits          378      378
  Misses         17       17

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Package is published with its development-only dependencies

The package shouldn’t be published with dependencies that are only used for development:
https://github.com/shakacode/sass-resources-loader/blob/ce2700db680bbe100a5f6b0b9edee5c740396dba/package.json#L37-L56
As far as I can see all of @babel/cli, @babel/preset-env, and babel-eslint are only used in development. They should be moved to devDependencies.

@thibaudcolas could you put this improvement and the one for #126 in a PR?

@Tomburgs, can you take this one?

Fixed a long time ago in #128.


Outdated test page or transaction signing over deeplink constantly fails with "Network discrepancy" error

I'm trying the link generated by the test page. But I'm not able to sign because of "Network discrepancy" error appearing on every network I'm choosing in the network selector.
If you changed the deep link url format then update the test page accordingly.

It works if I add &networkId=ae_uat to example. I'm not sure that it should be mandatory (maybe wallet can use current network by default). Also networkId should be consistent with x-cancel, x-success, e.g. to be kebab-case.


PR for #886:  create tearsheet toggle view all

Contributes to #886
Adds the optional view all toggle to the create tearsheet. This toggle will display all of the pages together on one long scrolling page and will substitute the ProgressSteps component in the influencer, with the SideNav component from UIShell. The items in the SideNav can be used to navigate to the different sections and will scroll the page to a given section.
What did you change?
CreateTearsheet.js
CreateTearsheet.stories.js
CreateTearsheetSection.js
_create-tearhseet.scss
constants.js
_storybook-styles.scss
MultiStepWithSectionsTearsheet.js --> Used to render the story with the toggle
How did you test and verify your work?
Storybook

Somehow yarn offline files got added here when I was trying to get the tests to run again, I'm going to open a new PR.


perf: disable video on cypress tests by default

This speeds up the CI (no video recording + no video compression), we can still enable the video by reverting the flag locally.

replaced by https://github.com/Chainlit/chainlit/pull/27


update the about page

when we are on about page , the name of the website is not showing
please assign this work to me

Hi, I'd like to work on this issue. Please assign it to me.

please level this issue

this issue was resolved, so i am closing this issue.


The SP Configs in the Console Application Keeps Continuously Loading After Receiving Error Response From Backend

Describe the issue:
The SP Configs in the Console Application Keeps Continuously Loading After Receiving Error Response From Backend.
How to reproduce:

Do any change to the SP that results a failure from the backend.
Observe the error message
Observe the continuous loading state.

Expected behavior:
The loading state should stop and one of the following states should appear.

The original configs
The updated configs that we received an error from the backend.

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


[0.61.5] FlatList onEndReachedThreshold not working with horizontal prop

FlatList onEndReachedThreshold not working with horizontal={true} prop.
Description
Scrolling through horizontal FlatList to the right is ignoring onEndReachedThreshold={0.5} prop. onEndReached callback is executed when end is really reached so it is really poor experience for our users. Then need to go to the very end of list and then wait for load another page - it breaks "infinite scroll" feeling of the list.
React Native version:
System:
    OS: macOS 10.14.6
    CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
    Memory: 654.07 MB / 16.00 GB
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 10.19.0 - /usr/local/bin/node
    Yarn: 1.22.0 - /usr/local/bin/yarn
    npm: 6.13.7 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
    Android SDK:
      API Levels: 28, 29
      Build Tools: 28.0.3
      System Images: android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom, android-29 | Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom, android-29 | Google APIs Intel x86 Atom_64
  IDEs:
    Android Studio: 3.4 AI-183.6<IP_ADDRESS>92245
    Xcode: 11.3/11C29 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.9.0 => 16.9.0
    react-native: 0.61.5 => 0.61.5
  npmGlobalPackages:
    react-native-cli: 2.0.1

Steps To Reproduce

Create component with FlatList for example:

    <FlatList
      data={auctions}
      renderItem={renderListItem}
      horizontal
      onEndReachedThreshold={0.5}
      onEndReached={handleLoadMore}
    />

Setup log to handleLoadMore to see when it is called
Scroll to the right
Observe that handleLoadMore is called after right edge of the elements is reached instead after passing half of the list

Expected Results
Horizontal  should behave the same way as vertical one. It should respect onEndReachedThreshold prop.

I am having the same issue but with vertical scrolling.
"react": "16.13.1",
"react-native": "0.63.1"
onEndReached only gets called at the end of the list irrespective of onEndReachedThreshold value.

This issue was happened me.
"react": "16.13.1"
"react-native": "0.62.2"
However, it was not the right way to use it in the first place.
"onEndReachedThreshold" and "onEndReached" should be used with style's "height".
<FlatList       data={auctions}       renderItem={renderListItem}       horizontal       onEndReachedThreshold={0.5}       onEndReached={handleLoadMore}       style={{height: '100%'}}   // this />
I was so concerned about infinite scrolling that I completely lost sight of this possibility.
And I found that this can be used with  like....
<ScrollView nestedScrollEnabled={true}>  //Don't forget nestedScrollEnabled={true} in Android     <FlatList          nestedScrollEnabled={true}          style={{height: '100%'}}           ..........          ......     />   <ScrollView />

+1 @rashtell  @dkoprowski were you people able to fix this?


adds ability to override certain values based on context

This adds the ability in metdata_source to takes in a list of keys (identifies context) for overriding instance_metadata.
@jtai  @josephsofaer

We may want to skip the context_overrides option here so it doesn't display: https://github.com/airbnb/stemcell/blob/override-key/lib/stemcell/metadata_launcher.rb#L69

@jtai fixed

This looks good to me. Can you update the PR description to provide a more detailed usage example?

updated PR description.


Correct exception specification mismatch in Memory::Recycler::AddMark

Memory::Recycler::AddMark() is declared with no exception specification
but defined as throw(). Upcoming versions of MSVC will diagnose this
mismatch in /permissive- or C++17 modes. Add throw() to the
declaration to bring the declaration in line with the definition.

Could you rebase this PR on top of master? We have fixes for the CI issues that this PR has hit in master.

Rebased, thanks!

@joemmett Sorry for the delay -- could you rebase and resolve the conflict? Then I'll get this merged.

Rebased, but it looks like the newly added AddPreciselyTracedMark() function will have exactly the same issue. I've updated the PR to change this signature as well.

@joemmett Thanks!


Playtime Error

The playtime for users display as this, is there any fix to this?

Sure, it seems it is using the wrong time for those players, it is displaying the time wrong. Not quite sure why it is doing that. Can you provide me with line 3-6 from the database file of the three players you showed in your screenshot? You can find the database files in the  plugins/FreeRPG/PlayerDatabase folder of your server. The actual playernames are in line two of the files in the PlayerDatabase folder of your server, if you don't know which files belong to whom.
I am only interested in the following information: firstLogin, lastLogin, lastLogout, playTime.
I noticed the same behavior with my instance.

I checked my server and I have the same issue. I started looking in it, if you can post the different time stamps each player has that you showed in your screenshot, it would be great.
Check your server folder in /plugins/FreeRPG/PlayerDatabase. The files are named with the UUID of each player, if you want to get the real name, open the file and check the second line. There is the real player name that is being displayed in game. Only line 3-6 is important. So the files that say firstLogin, lastLogin, lastLogout, playTime.
I look what I can do.

Thanks


Code cleanup: split index into multiple files

I'm finding it difficult to search & parse through all of src/index.ts. Any chance this could be split up into more files with fewer areas of code each?

Closing out my old issues in repos that haven't had updates in a few years. Cheers!


As a computer science student, I want to track the status of my internship applications, including whether they are pending, accepted, or rejected,

so that I can easily monitor the progress of my applications.

edit-i-role i/<index of company> o/<outcome>

outcome: follow up, offered, ghosted, rejected, accepted ONLY

edit-i-task i/<index of task> o/<outcome>

outcome: follow up, offered, ghosted, rejected ONLY


Failed to run task "lint"

🐛 Describe the bug
A clear and concise description of what the bug is.
🔢 To Reproduce
Steps to reproduce the behavior:
run > task lint
Observed on VS Code (Windows)
💘 Expected behavior
Linting check works
📷 Screenshots

🖥 Setup

lasso-python version: [e.g. 1.5.1]
OS: Windows

ℹ Additional context
possible solution: remove python3 -m from the lint task in poetry file

@rao014 how should we proceed here? Do I understand to simply remove python3 -m and just do poetry ...?

@codie3611 It works now on my PC.
No idea why! Closing this issue.


GPT local copy

Is it possible to use this project on a local copy of the documentation?

Yes, indeed it works only with local copy of documentation


🐛 [Bug] Windows crash at runtime

Bug Description
I created a TRTorch 0.0.3 for Windows and have noticed it crashes at runtime when registering the operators.
Backtrace:

Schema:
trt::execute_engine(Tensor[] inputs, __torch__.torch.classes.tensorrt.Engine engine) -> Tensor[]
Function it dies in, while parsing schema:
https://github.com/pytorch/pytorch/blob/4a3aad354a14edb1337c6214c3d3870c136d5286/torch/csrc/jit/frontend/schema_type_parser.cpp#L307
To Reproduce
Steps to reproduce the behavior:

Use Windows
Use my precompiled TRTorch
Link to TRTorch

Prebuilt is available in PR #152 or for debug library:
trtorch-0.0.3-debug.zip
Expected behavior
Runs
Environment

Build information about the TRTorch compiler can be found by turning on debug messages

PyTorch Version (e.g., 1.0): 1.6.0-rc3
CPU Architecture: x64
OS (e.g., Linux): Windows
How you installed PyTorch (conda, pip, libtorch, source): libtorch
Build command you used (if compiling from source):
Are you using local sources or building from archives:
Python version: 3.7
CUDA version: 10.2
GPU models and configuration: RTX 2060
Any other relevant information:

I am currently working required updates to TRTorch to be compatible with 1.6.0. There are some issues i have hit from using the 0.0.3 branch. Perhaps that is the root cause? When I compiled on windows I used the 1.5.1 official build from pytorch.org. Ill see if i can replicate once the update is complete.

@narendasan Any update on the 1.6.0 compatibility? I guess that's what this bug is.

I just wrapped up the update to 1.6.0, so I can start to take a look at this. Do you have a short example program that can replicate this issue? Right now what I see is that some of the example applications we have seem to be able to start up properly without hitting this issue.

Every model I've tested seems to hit this issue. I couldn't find a way to not reproduce this.


Integrate LW with tmastr.seeds master token list

🗃 Github Issue Or Explanation for this PR. (What is it supposed to do and Why is needed)
Issue #1759
✅ Checklist

[ ] Github issue details are up to date for people to QA.
[ ] I have tested all my changes.

🕵♂ Notes for Code Reviewer
Technical explanations to help your peers review your work - including environments, credentials, etc.
This PR may be a bit immature for merge to mainline, but would benefit from review.
The principal changes are

create a datasource http api to pull token model metadata from tmastr.seeds contract. (tmastr latest merge was https://github.com/JoinSEEDS/seeds-smart-contracts/pull/466 ). Metadata is served from tmastr as explicit fields (e.g. contract, token symbol) combined with JSON data (e.g. logo image url). Only the SEEDS token is hard-coded into the token_models.dart file; all others (e.g. HYPHA, TLOS, STARS) are imported from tmastr.seeds.
define a JSON schema and use it to validate the metadata set from the tmastr contract. TBD: finalize a location for the schema. It is currently in token_models.dart file as a string literal but should be accessible broadly within the Seeds ecosystem (including 3rd party web apps).
Support logo and background images served from general web urls, in addition to LW assets. TBD: expand schema to allow two or more alternative sources, e.g. asset & url? Also TBD: check error handling when web image access times out.
Support "Seeds ecosystem approved token" concept recommended by Seeds Currency Working Group.
Make the code "token contract aware" so that it does not assume that token symbols are unique over the Telos blockchain.

Note tmastr.seeds is not yet deployed to mainnet; for testing purposes seeds_scopes.dart references rainboissuer (a random mainnet account I own) where I have installed the tokensmaster contract.
🙈 Screenshots

token balance card with "approved" mark
send token screen

👯♀ Paired with
"nobody" yet but I would benefit from having a partner

@n13  can you review this pr pls

Abandoning this PR, will resubmit from a branch within this repo.


Support running HttpApi locally

Issue #, if available: #1641
Why is this change necessary?
This changes is necessary in order to make HttpApi event type work with sam local start-api.
How does it address the issue?

Currently sam doesn't support HttpApi because it only extract resource with type AWS::Serverless::Function and AWS::Serverless::Api, this changes add AWS::Serverless::HttpApi to be extracted from the template.yaml
Construct event v2.json from flask request

What side effects does this change have?
Did you change a dependency in requirements/base.txt?
If so, did you run make update-reproducible-reqs
No
Checklist:

[ ] Write Design Document (Do I need to write a design document?)
[x] Write unit tests
[x] Write/update functional tests
[ ] Write/update integration tests
[x] make pr passes
[x] Write documentation

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Example template:
Resources:
    HTTPAPIGatewayLogGroup:
        Type: AWS::Logs::LogGroup
        Properties:
            LogGroupName: HTTPAPIGatewayLogGroup
            RetentionInDays: 1

    HTTPAPIGateway:
        Type: AWS::Serverless::HttpApi
        Properties:
            AccessLogSettings:
                DestinationArn: !GetAtt HTTPAPIGatewayLogGroup.Arn
                Format: '{"requestId": "$context.requestId", "userAgent": "$context.identity.userAgent", "httpMethod": "$context.httpMethod", "path": "$context.path", "status": "$context.status", "protocol": "$context.protocol", "integrationStatus": "$context.integrationStatus", "responseLatency": "$context.responseLatency" }'
            FailOnWarnings: true

    LambdaLoginPage:
        Type: AWS::Serverless::Function
        Properties:
            FunctionName: LoginPage
            Description: >
                A function to handle /login
            MemorySize: 128
            Timeout: 3
            CodeUri: app/
            Handler: controllers.login_page
            Runtime: python3.8
            Events:
                HTTPMethodGET:
                    Type: HttpApi
                    Properties:
                        ApiId: !Ref HTTPAPIGateway
                        Path: /login
                        Method: get
                        TimeoutInMillis: 3000

To run HttpApi locally:
sam local start-api

For example on windows:
(samcli-dev) PS C:\Users\bayu\pyk\streamers-serverless> .\samcli-dev\Scripts\sam.exe local start-api
Mounting LambdaLoginPage at http://<IP_ADDRESS>:3000/login [GET]
You can now browse to the above endpoints to invoke your functions. You do not need to restart/reload SAM CLI while working on your functions, changes will be reflected instantly/automatically. You only need to restart SAM CLI if you update your AWS SAM template
2020-04-25 21:47:40  * Running on http://<IP_ADDRESS>:3000/ (Press CTRL+C to quit)
2020-04-25 21:47:43 <IP_ADDRESS> - - [25/Apr/2020 21:47:43] "GET / HTTP/1.1" 403 -
2020-04-25 21:47:43 <IP_ADDRESS> - - [25/Apr/2020 21:47:43] "GET /favicon.ico HTTP/1.1" 403 -
Invoking controllers.login_page (python3.8)

Fetching lambci/lambda:python3.8 Docker container image......
Mounting C:\Users\bayu\pyk\streamers-serverless\.aws-sam\build\LambdaLoginPage as /var/task:ro,delegated inside runtime container
START RequestId: af2687b6-7ca5-1794-302d-1faa63af6e0c Version: $LATEST
END RequestId: af2687b6-7ca5-1794-302d-1faa63af6e0c
REPORT RequestId: af2687b6-7ca5-1794-302d-1faa63af6e0c     Init Duration: 332.88 ms        Duration: 4.33 ms       Billed Duration: 100 ms Memory Size: 128 MB     Max Memory Used: 24 MB
2020-04-25 21:47:55 <IP_ADDRESS> - - [25/Apr/2020 21:47:55] "GET /login HTTP/1.1" 200 -
2020-04-25 21:47:55 <IP_ADDRESS> - - [25/Apr/2020 21:47:55] "GET /favicon.ico HTTP/1.1" 403 -

I'm waiting a review from the maintainers.
I saw many peoples are wanted this feature #1641 , the temporary solution is to install this branch using the following command:
pip install git+https://github.com/pyk/aws-sam-cli.git@develop

Then run:
sam local start-api

Make sure to uninstall the previous sam-cli.

Can confirm that this is working locally for me 👍 thanks again @pyk

Can confirm that this is working locally for me  thanks again @pyk

me too

Hello @pyk
I thank you very much.
I'm really looking forward to using HttpApi. I tried it as @pyk provided a temporary solution. However, CORS was not available. I have created a pull request so that CORS can be configured with HttpApi, so please check.

I’m curious to know what’s blocking this merge? It keeps becoming ready then again goes into conflict mode.

@picosam It seems timeout(?) causing make pr test failed in 2 environments:

I hope I can rerun the test to validate this.

Can you push an empty commit? git commit --allow-empty -m "trigger build"
Looking at the build logs the two builds failed at different steps without any apparent error message. Could this simply be a build server instability? That said, looking at the commits on this PR it seems that 10 out of 12 builds have failed so far.
Someone with experience on developing for sam-cli might be able to tell if that does indeed indicate an issue with the code or not.

@mistaecko done 👍

Thank you @pyk, I sure hope someone's going to review this and merge it once and for all.

@pyk Tried the temporary solution

pip install git+https://github.com/pyk/aws-sam-cli.git@run-httpapi-locally

and noticed that Payload format version 1.0* always seems to be used when running using sam local start-api.
Is this expected?
*) https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations-lambda.html

Can someone review and approve this ?

I confirm local installation described at https://github.com/awslabs/aws-sam-cli/pull/1942#issuecomment-644063266 works for me

@pyk Tried the temporary solution

pip install git+https://github.com/pyk/aws-sam-cli.git@run-httpapi-locally

and noticed that Payload format version 1.0* always seems to be used when running using sam local start-api.
Is this expected?
*) https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations-lambda.html

I confirm the payload version 1.0 seems to be used; even with HttpApi.
Looks like the PR is missing a new payload definition in https://github.com/awslabs/aws-sam-cli/tree/develop/samcli/lib/generated_sample_events/events/apigateway

Still desperately waiting for this to be merged.

So this really useful PR sits idle since April without any feedback from AWS ? This is really kind of demotivating for developers to even start contributing.

@awsjeffg is there anything we can maybe do to help out?

@picosam nothing currently but thanks for the nudge. We're evaluating this and other popular github issues for sam and sam cli as part of a post-1.0 review process. What I would say about this type of issue generally is that we ( AWS ) need to be crisp in terms of what we support in emulation locally and why, as there are potential issues with providing something for local development that does not behave like the hosted service in subtle ways. This issue and others like it are in this grey area.

As a developer I would be extremely happy with a version that works even on just a small subset of the real features. Most of the use cases I see are simple api endpoints that do not use any advanced features. The local emulation does not need to be a perfect replica of the actual hosted service.
Our current solution is keeping both http api and api gateway code in the template and switching between them by commenting and uncommenting parts of the template. Any minimal support for http api would be better than this...

On the flipside, according to this earlier comment, if I understand correctly, this PR only uses payload version 1.0 no matter what though.
The latest payload version can barely be called an advanced feature that's missing I think...
So surely this PR is not even mergeable right now...?
I appreciate AWS, as they are, being thorough in making sure that the local emulation is being brought up to a good standard.
Hopefully this is high priority to get this one up to scratch though, because it would ease a lot of people's pain trying to develop for what AWS say are the latest tools - HTTP APIs aren't in beta anymore, they should have proper tooling support so that we can confidently adopt them...

Hello @pyk
I sent a PR to address the issue of "payload Format Version", so please check.

I can see merging is blocked because of conflicts. So desperate for this change. I would attempt to resolve the merge conflicts if I knew anything about Python.
AWS - this is key functionality, can't you get involved and progress this.

@Hobbit71 thanks for the feedback - we're looking into taking this change and adding some additional changes to provide this feature, hopefully in the next couple of months.

@pyk
There are couple of PRs (https://github.com/pyk/aws-sam-cli/pull/5, https://github.com/pyk/aws-sam-cli/pull/6) on your repo that are related to this change. Could you please merge them, and update this PR so we can merge it to our repo.

@moelasmar Done 👌

@moelasmar I make a few changes, please review it 🙇♂

@pyk Can you please also merge pyk#7 to your branch before we merging it? Thanks!

Thanks so much @pyk for the contribution!

Yes @pyk thanks so much for contributing, and for your patience!

you are welcome guys! 🙇

So will it be part of the next release? :)

Yes!

It would be great to also have the accompanying #2334 merged!

@svenemtell I believe we've provided v2 payload support by merging another contribution from @WinterYukky that was merged into @pyk 's PR:
https://github.com/aws/aws-sam-cli/pull/1942/commits/25f0169132e7e6085aedf3111deea824cfda9f15
( unless I'm misunderstanding something )
If you are testing this new feature once SAM cli v.1.7 is released and find issues with payload versions, please file a new issue and mention me. We're hoping for EOD today for this release ( it was supposed to be yesterday actually but we had an internal issue and had to delay for a day )

@svenemtell  and, thanks for contributing that PR and sorry for taking this different path in getting these contributions merged, it ended up being the simplest thing to do.

And we're live! I know many people are excited about this new feature - please test it out and if you run into issues, please file and issue and @ me.

There's just one thing I don't really know if it's a bug or intentional. When I run my HttpApi locally and console.log the event object my routeKey is /auth/login:POST, but when I do the same thing on AWS Lambda it says POST /auth/login.

@tsndr log that bug! Seems like it could be a shallow fix. Does anything break as a result?

In my case it causes my "routing" to break. I'm using one lambda function to handle multiple endpoints, so I I'm doing this:
switch (event.routeKey) {
    case 'POST /auth/login':
        response = await require('./controllers/AuthController').login(event)
        break
    case 'GET /auth/user':
        response = await require('./controllers/AuthController').user(event)
        break
    case 'POST /auth/register':
        response = await require('./controllers/AuthController').register(event)
        break
}

Which might not be the cleanest solution, but it works for me.

@tsndr it's still a behaviour difference and we should try to address it. Can you please file an issue if you have time? And @ me so I get an email reminder.

In my case it causes my "routing" to break. I'm using one lambda function to handle multiple endpoints, so I'm doing this:
switch (event.routeKey) {
    case 'POST /auth/login':
        response = await require('./controllers/AuthController').login(event)
        break
    case 'GET /auth/user':
        response = await require('./controllers/AuthController').user(event)
        break
    case 'POST /auth/register':
        response = await require('./controllers/AuthController').register(event)
        break
}

Which might not be the cleanest solution, but works for me.

This issue is being worked on in #2345


Improved hint macro handling.

Stack:

#6624 ⬅
#6620
#6618
#6617
#6616

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

This change is


'RuntimeError: CUDA out of memory' on P100

Hi there,
I'm using Colab Pro to do some ML experiments and often fail to initialise the RN50x4 CLIP model. Sometimes I even have trouble getting the RN101 model to load up. RN50x16 has never worked in my experience. The notebook is running on a P100 GPU and mentions that "x4 and x16 models for CLIP may not work reliably on lower-memory machines".
I'm just wondering if I need an even more capable GPU (in terms of VRAM) or if there is some problem with the code? I'm not an expert with Tensorflow/ML so apologies if there's a simple solution to this.

Ah, sorry. The wording made it sound like it was possible on Colab. Thank you.


Update to use string splicing instead of substring

Substring-ing was deprecated in Swift 4. The recommended way now is to use string splicing.

@Nexuist Great! I guess we need to update the Travis' Xcode image too.


Move benchmark code from nox to bm_runner

Closes #281

Great stuff @stephenworsley -- thanks for your patience !


Add Hillstone VPN device information

Hi,
This is Yi from Hillstone Networks. I see my pull request was closed. If you need to start the validation process, please let us know. We also have office and colleagues in the Bay Area. You can contact<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Btw. As I don't see the Email of author on the profile page, I can only leave message on this thread. Not sure if it can reach the author in my previous request as it's closed. Could I have the contact info of the author for the following validation process if possible?
Thanks,
Yi

@jzhao0911 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Reaching out directly to start the validation process
#please-close


[DOCUMENTATION] Python client example uses old deprecated facets

what
https://openlineage.io/docs/client/python uses the deprecated from openlineage.client.facet import, rather than the newer from openlineage.client.facet_v2 import.
ideal
https://openlineage.io/docs/client/python is updated to use the latest facet module.

Hey @skrawcz thanks for the catch. Would you be open to providing a PR with the desired change? I’ll be happy to help if you encounter any blockers.

Hey @skrawcz thanks for the catch. Would you be open to providing a PR with the desired change? I’ll be happy to help if you encounter any blockers.

If I get something I'm happy with, sure. Are there docs on the latest facet module that could explain any differences from the old one?

I'm not sure if there are docs about it, but with the change to v2 facets they are being auto-generated from the spec so this is something you may look at. This transition to v2 is fixing any discrepancies from the spec that we might have had before with the manual implementation of python classes.

Hi @kacpermuda , I'm looking for how to auto generate v2 facets from spec, but didn't find any reference. Is the process documented anywhere?

Hi @kacpermuda , I'm looking for how to auto generate v2 facets from spec, but didn't find any reference. Is the process documented anywhere?

@zhaomuzhi, the process is not documented. It's being generated as pre-commit hook. See: https://github.com/OpenLineage/OpenLineage/blob/main/.pre_commit/generate-facets/generate.py
May I ask why would you like to auto generate the facets by yourself?

Hi @kacpermuda , I'm looking for how to auto generate v2 facets from spec, but didn't find any reference. Is the process documented anywhere?

@zhaomuzhi, the process is not documented. It's being generated as pre-commit hook. See: https://github.com/OpenLineage/OpenLineage/blob/main/.pre_commit/generate-facets/generate.py
May I ask why would you like to auto generate the facets by yourself?

I see. I'm adding my own facet for testing locally.I feel it would be very helpful if there's a documented way of doing that before I commit. I would like to verify if the spec I define is correct by looking at the generated python code.

@JDarDagran , I installed the pre-commit which got triggered when I commit, but I got this error, do you happen to know what's the issue?
[INFO] Installing environment for https://github.com/pre-commit/mirrors-prettier.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
An unexpected error has occurred: CalledProcessError: command: ('/Users/zhaomuzhi/src/OpenLineage/client/python/.venv/bin/python', '-mnodeenv', '--prebuilt', '--clean-src', '/Users/zhaomuzhi/.cache/pre-commit/repor6koy21y/node_env-default')
return code: 1
stdout: (none)
stderr:
    Traceback (most recent call last):
      File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/urllib/request.py", line 1348, in do_open
        h.request(req.get_method(), req.selector, req.data, headers,
      File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/http/client.py", line 1282, in request
        self._send_request(method, url, body, headers, encode_chunked)
      File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/http/client.py", line 1328, in _send_request
        self.endheaders(body, encode_chunked=encode_chunked)
      File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/http/client.py", line 1277, in endheaders
        self._send_output(message_body, encode_chunked=encode_chunked)
      File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/http/client.py", line 1037, in _send_output
        self.send(msg)
      File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/http/client.py", line 975, in send
        self.connect()
      File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/http/client.py", line 1454, in connect
        self.sock = self._context.wrap_socket(self.sock,
      File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/ssl.py", line 512, in wrap_socket
        return self.sslsocket_class._create(
      File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/ssl.py", line 1070, in _create
        self.do_handshake()
      File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/ssl.py", line 1341, in do_handshake
        self._sslobj.do_handshake()
    ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:997)

@zhaomuzhi your issue seems unrelated to the original issue. Please let's move to Slack or separate issue.
The error you've got also seems unrelated to OL code rather then some system setup (certifi maybe?)


學習資料結構與演算法 Heap / Priority Queue

寫 KM https://github.com/CAFECA-IO/KnowledgeManagement/issues/61
ref

taking 4 hrs
remaining 1 hr
KM

taking 1 hr


Does not support ref or null

Define a schema with a field that can either be a ref or null.
anyOf:
  - $ref: '#/components/schemas/X'
  - type: 'null'

Receive the following error
Value must be one of: array, boolean, integer, number, object, string. Received: "null"

Hello, @erezarnon.
The value null is not a valid type. This is per the spec at https://spec.openapis.org/oas/v3.0.3#data-types.
In the first paragraph under section 4.4 Data Types, you'll see that it says

null is not supported as a type (see nullable for an alternative solution

The OpenAPI Enforcer does support nullable for OpenAPI 3.0.x.
I hope that solves your problem, but if not please reach out again and I'll see if I can help out.

Yes. I had to use allOf  instead of just the $ref for nullable to work, which is weird, but it worled

I thought that maybe you'd put nullable inside of the X definition, but maybe that wasn't an option for you. Either way, I'm glad you were able to resolve it.


Wrong loaded path when refreshing the whole page

Correct wrong loaded path when refreshing the whole page

Corrected by adding  to the index.html page

:+1:


python generate.py encountered the error "RuntimeError: CUDA error: device-side assert triggered"

🐛 Bug

To Reproduce
Steps to reproduce the behavior (always include the command you ran):

Run cmd '....'

python -u .//generate.py processed_convai2_none/bin --path ./models_convai2/model_bert_encoder_embedding/checkpoint9.pt --beam 6 --nbest 6 --gen-subset valid --max-sentences 196 --max-tokens 5000 --max-len-b 25 --remove-bpe ' ##' --sampling --sampling-topp 0.9 --no-repeat-ngram-size 2 --temperature 0.7

processed_convai2_none/bin  is the data path, checkpoint9.pt is the model I have trained
2. See error
/opt/conda/conda-bld/pytorch_1579027003190/work/aten/src/ATen/native/cuda/MultinomialKernel.cu:256: void at::native::<unnamed>::sampleMultinomialOnce(long *, long, int, scalar_t *, scalar_t *, int, int) [with scalar_t = float, accscalar_t = float]: block: [2,0,0], thread: [0,0,0] Assertion `sum > accZero` failed.
Traceback (most recent call last):
  File ".//generate.py", line 11, in <module>
    cli_main()
  File "/home/research/haha/research-transfer-dialouge/fairseq/fairseq_cli/generate.py", line 269, in cli_main
    main(args)
  File "/home/research/haha/research-transfer-dialouge/fairseq/fairseq_cli/generate.py", line 36, in main
    return _main(args, sys.stdout)
  File "/home/research/haha/research-transfer-dialouge/fairseq/fairseq_cli/generate.py", line 145, in _main
    hypos = task.inference_step(generator, models, sample, prefix_tokens)
  File "/home/research/haha/research-transfer-dialouge/fairseq/fairseq/tasks/fairseq_task.py", line 356, in inference_step
    return generator.generate(models, sample, prefix_tokens=prefix_tokens)
  File "/home/research/miniconda3/envs/torch1.4/lib/python3.6/site-packages/torch/autograd/grad_mode.py", line 49, in decorate_no_grad
    return func(*args, **kwargs)
  File "/home/research/haha/research-transfer-dialouge/fairseq/fairseq/sequence_generator.py", line 161, in generate
    return self._generate(sample, **kwargs)
  File "/home/research/haha/research-transfer-dialouge/fairseq/fairseq/sequence_generator.py", line 310, in _generate
    scores.view(bsz, beam_size, -1)[:, :, :step],
  File "/home/research/haha/research-transfer-dialouge/fairseq/fairseq/search.py", line 272, in step
    beams_buf = torch.arange(0, beam_size).to(indices_buf).repeat(bsz, 1)
RuntimeError: CUDA error: device-side assert triggered

Code sample

Expected behavior
In the sequence_generator.py, when the step == max_len, the lprobs will be assigned -math.inf expect eos, we wish the generator generate the eos token.
if step >= max_len:
    lprobs[:, : self.eos] = -math.inf
    lprobs[:, self.eos + 1 :] = -math.inf

the following code
if self.no_repeat_ngram_size > 0:
    lprobs = self._no_repeat_ngram(tokens, lprobs, bsz, beam_size, step)

However，sometimes all elements of lprobs will be assigned -math.inf include eos
when running the code in search.py, I encountered the error, because all elements of lprobs is 0 in the following code, we can't use torch.multinomial to sample
indices_buf = torch.multinomial(
    probs.view(bsz * beam_size, -1),
    1,
    replacement=True,
).view(bsz, beam_size)

Environment

fairseq Version (e.g., 0.9 or master):0.9
PyTorch Version : 1.4
OS (e.g., Linux): Linux
How you installed fairseq (pip, source): source
Build command you used (if compiling from source):pip install --editable ./
Python version:3.6.10
CUDA/cuDNN version: 10.0
GPU models and configuration:
Any other relevant information:

Additional context

You'll want to re-run with the following environment variable: CUDA_LAUNCH_BLOCKING=1.  This should give you a more informative error message.

/opt/conda/conda-bld/pytorch_1579027003190/work/aten/src/ATen/native/cuda/MultinomialKernel.cu:256: void at::native::<unnamed>::sampleMultinomialOnce(long *, long, int, scalar_t *, scalar_t *, int, int) [with scalar_t = float, accscalar_t = float]: block: [4,0,0], thread: [0,0,0] Assertion `sum > accZero` failed.
THCudaCheck FAIL file=/opt/conda/conda-bld/pytorch_1579027003190/work/aten/src/THC/generic/THCTensorScatterGather.cu line=71 error=59 : device-side assert triggered
Traceback (most recent call last):
  File ".//generate.py", line 11, in <module>
    cli_main()
  File "/home/research/haha/research-transfer-dialouge/fairseq/fairseq_cli/generate.py", line 269, in cli_main
    main(args)
  File "/home/research/haha/research-transfer-dialouge/fairseq/fairseq_cli/generate.py", line 36, in main
    return _main(args, sys.stdout)
  File "/home/research/haha/research-transfer-dialouge/fairseq/fairseq_cli/generate.py", line 145, in _main
    hypos = task.inference_step(generator, models, sample, prefix_tokens)
  File "/home/research/haha/research-transfer-dialouge/fairseq/fairseq/tasks/fairseq_task.py", line 356, in inference_step
    return generator.generate(models, sample, prefix_tokens=prefix_tokens)
  File "/home/research/miniconda3/envs/torch1.4/lib/python3.6/site-packages/torch/autograd/grad_mode.py", line 49, in decorate_no_grad
    return func(*args, **kwargs)
  File "/home/research/haha/research-transfer-dialouge/fairseq/fairseq/sequence_generator.py", line 161, in generate
    return self._generate(sample, **kwargs)
  File "/home/research/haha/research-transfer-dialouge/fairseq/fairseq/sequence_generator.py", line 310, in _generate
    scores.view(bsz, beam_size, -1)[:, :, :step],
  File "/home/research/haha/research-transfer-dialouge/fairseq/fairseq/search.py", line 257, in step
    probs, dim=2, index=indices_buf.unsqueeze(-1)
RuntimeError: cuda runtime error (59) : device-side assert triggered at /opt/conda/conda-bld/pytorch_1579027003190/work/aten/src/THC/generic/THCTensorScatterGather.cu:71

You'll want to re-run with the following environment variable: CUDA_LAUNCH_BLOCKING=1. This should give you a more informative error message.

/opt/conda/conda-bld/pytorch_1579027003190/work/aten/src/ATen/native/cuda/MultinomialKernel.cu:256: void at::native::<unnamed>::sampleMultinomialOnce(long *, long, int, scalar_t *, scalar_t *, int, int) [with scalar_t = float, accscalar_t = float]: block: [4,0,0], thread: [0,0,0] Assertion `sum > accZero` failed.
THCudaCheck FAIL file=/opt/conda/conda-bld/pytorch_1579027003190/work/aten/src/THC/generic/THCTensorScatterGather.cu line=71 error=59 : device-side assert triggered
Traceback (most recent call last):
  File ".//generate.py", line 11, in <module>
    cli_main()
  File "/home/research/haha/research-transfer-dialouge/fairseq/fairseq_cli/generate.py", line 269, in cli_main
    main(args)
  File "/home/research/haha/research-transfer-dialouge/fairseq/fairseq_cli/generate.py", line 36, in main
    return _main(args, sys.stdout)
  File "/home/research/haha/research-transfer-dialouge/fairseq/fairseq_cli/generate.py", line 145, in _main
    hypos = task.inference_step(generator, models, sample, prefix_tokens)
  File "/home/research/haha/research-transfer-dialouge/fairseq/fairseq/tasks/fairseq_task.py", line 356, in inference_step
    return generator.generate(models, sample, prefix_tokens=prefix_tokens)
  File "/home/research/miniconda3/envs/torch1.4/lib/python3.6/site-packages/torch/autograd/grad_mode.py", line 49, in decorate_no_grad
    return func(*args, **kwargs)
  File "/home/research/haha/research-transfer-dialouge/fairseq/fairseq/sequence_generator.py", line 161, in generate
    return self._generate(sample, **kwargs)
  File "/home/research/haha/research-transfer-dialouge/fairseq/fairseq/sequence_generator.py", line 310, in _generate
    scores.view(bsz, beam_size, -1)[:, :, :step],
  File "/home/research/haha/research-transfer-dialouge/fairseq/fairseq/search.py", line 257, in step
    probs, dim=2, index=indices_buf.unsqueeze(-1)
RuntimeError: cuda runtime error (59) : device-side assert triggered at /opt/conda/conda-bld/pytorch_1579027003190/work/aten/src/THC/generic/THCTensorScatterGather.cu:71

I have same error.
invalid multinomial distribution (sum of probabilities <= 0)

I have same error.
invalid multinomial distribution (sum of probabilities <= 0)

have the same problem

Is there any way to avoid this?
For example, by adding some kind of modification to the logits before softmax.

This problem can be solved by assigning 1 to the eos element in fairseq/sequence_generator.py.
Before:
# handle max length constraint
if step >= max_len:
    lprobs[:, : self.eos] = -math.inf
    lprobs[:, self.eos + 1 :] = -math.inf

After:
# handle max length constraint
if step >= max_len:
    lprobs[:, : self.eos] = -math.inf
    lprobs[:, self.eos + 1 :] = -math.inf
    lprobs[:, self.eos] = 1

Have the same problem. Is there any solution that don't have to modify the source code of fairseq/sequence_generator.py?


Backport to Java 8

These are just the code changes - please advise how to adjust the release process.

This will not build properly unless security issues appeared in #100 will be resolved and backported here. Or we should make a release without security checks and disabling CVE plugin which I am not in favor of.

Since Java 8 libraries will work in Java 11 I think the simplest solution will be to backport the source code to Java 8 only for this release and then release it again with Java 11. Otherwise we would need to build a parallel Java 8 build with a separate branch only for one specific release.

This will not build properly unless security issues appeared in #100 will be resolved and backported here. Or we should make a release without security checks and disabling CVE plugin which I am not in favor of.

This PR should be merged after #100

Since Java 8 libraries will work in Java 11 I think the simplest solution will be to backport the source code to Java 8 only for this release and then release it again with Java 11. Otherwise we would need to build a parallel Java 8 build with a separate branch only for one specific release.

sounds good to me

Superseded by #102


Error with installation

Issue Template
Please use this template!
Initial Check

If the issue is a request please specify that it is a request in the title (Example: [REQUEST] more features). If this is a question regarding 'twint' please specify that it's a question in the title (Example: [QUESTION] What is x?). Please only submit issues related to 'twint'. Thanks.

Make sure you've checked the following:

[X] Python version is 3.6;

mbcrump@crumplinux:~$ python3 --version
Python 3.6.8

[X] Updated Twint with pip3 install --upgrade -e git+https://github.com/twintproject/twint.git@origin/master#egg=twint;

``

[X] I have searched the issues and there are no duplicates of this issue/question/request.

Command Ran

Please provide the exact command ran including the username/search/code so I may reproduce the issue.

twint

Description of Issue

Please use as much detail as possible.
I get the following error

Traceback (most recent call last):
  File "/home/mbcrump/.local/bin/twint", line 11, in <module>
    load_entry_point('twint', 'console_scripts', 'twint')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 480, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2693, in load_entry_point
    return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2324, in load
    return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2330, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/home/mbcrump/src/twint/twint/__init__.py", line 13, in <module>
    from . import run
  File "/home/mbcrump/src/twint/twint/run.py", line 5, in <module>
    from . import datelock, feed, get, output, verbose, storage
  File "/home/mbcrump/src/twint/twint/get.py", line 14, in <module>
    from .output import Tweets, Users
  File "/home/mbcrump/src/twint/twint/output.py", line 6, in <module>
    from .storage import db, elasticsearch, write, panda
  File "/home/mbcrump/src/twint/twint/storage/panda.py", line 2, in <module>
    import pandas as pd
  File "/home/mbcrump/.local/lib/python3.6/site-packages/pandas/__init__.py", line 19, in <module>
    "Missing required dependencies {0}".format(missing_dependencies))
ImportError: Missing required dependencies ['numpy']

I have tried uninstalling/installing numpy as well as panda. I've even tried cloning the repo and setting up from there to no avail.
Environment Details

Using Windows, Linux? What OS version? Running this in Anaconda? Jupyter Notebook? Terminal?

mbcrump@crumplinux:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.1 LTS
Release:        18.04
Codename:       bionic

I guess that the issue is on your end. I'll try to replicate your issue to see what a solution could be

I had  a similar error, the following helped me solve it:
conda uninstall numpy #pip uninstall numpy
sudo apt install python3-pip
sudo apt-get install libatlas-base-dev

Not sure why installing the third is required, but it surely helped me solve the error( maybe its a dependency).


Travis-ci: added support for ppc64le

Signed-off-by: Devendranath Thadi<EMAIL_ADDRESS>Added power support for the travis.yml file with ppc64le. This is part of the Ubuntu distribution for ppc64le. This helps us simplify testing later when distributions are re-building and re-releasing.

@glaslos waiting for your response regarding ppc64le code merging. Thanks!

@dthadi3 I'm not a maintainer of this project.
I'm not quite sure what the motivation is to add this. I think from a lumberjack point of view it's perfectly sufficient to just support amd64.

@glaslos Thanks for your response, yeah we are adding support for power(ppc64le) for future testing purpose.
@natefinch waiting for your response regarding ppc64le code merging. Thanks!


Get-PSAutoLabSetting

Get-PSAutolabsetting returns values for FreeSpaceGB and others with extra charaters '[92m'  '[0m'

If you are running this in the PowerShell ISE that is to be expected. Those are ANSI sequences that normally look like this in the regular console.  But I think I can add something to detect if running in the ISE.


Add OS version information for TLS 1.2 cipher suites

Better clarify the OS support for AFD's four TLS 1.2 cipher suites. For better security, Windows 10 customers should prefer the EDCHE cipher suites while Windows 7, 8, and 8.1 customers must use the DHE cipher suites.

@pshelton-skype : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@duongau - Please review. Thanks.

@ktoliver Please go ahead and merge this PR. Thank you!

@ktoliver - Can I get a merge, please?

Thank you!

@duongau If you could, type #sign-off in a comment in a PR to let us know it's ready for merge. Our queries for "approved" PRs return inconsistent results. But I know the queries find author sign-off. Thanks! 👍🏻

@duongau If you could, type #sign-off in a comment in a PR to let us know it's ready for merge. Our queries for "approved" PRs return inconsistent results. But I know the queries find author sign-off. Thanks! 👍🏻

@ktoliver I'll make sure to do that next time. Thank you for merging this one!