Include header files and .lib files generated with VS 2022: MSVC fail to link

Bug Report
Current behavior:
I built used CMake to generate the Visual Studio project successfully.
I built the Visual Studio solution and all 7 builds in the solution were successful and created Debug and Release versions of the .lib files.
I included the .lib files generated in my project and the include folder provided in the source code but failed to link any of the functions with the libraries. Here are the error messages:
Build started at 4:44 AM...
1>------ Build started: Project: LibraryTest, Configuration: Debug x64 ------
1>main.cpp
1>C:\Users\chris\source\repos\LibraryTest\LibraryTest\vendor\dogecoin\libdogecoin.h(464,9): warning C4068: unknown pragma 'GCC'
1>(compiling source file 'main.cpp')
1>C:\Users\chris\source\repos\LibraryTest\LibraryTest\vendor\dogecoin\libdogecoin.h(465,9): warning C4068: unknown pragma 'GCC'
1>(compiling source file 'main.cpp')
1>C:\Users\chris\source\repos\LibraryTest\LibraryTest\vendor\dogecoin\libdogecoin.h(467,9): warning C4068: unknown pragma 'GCC'
1>(compiling source file 'main.cpp')
1>main.obj : error LNK2019: unresolved external symbol "void __cdecl dogecoin_ecc_start(void)" (?dogecoin_ecc_start@@YAXXZ) referenced in function main
1>main.obj : error LNK2019: unresolved external symbol "void __cdecl dogecoin_ecc_stop(void)" (?dogecoin_ecc_stop@@YAXXZ) referenced in function main
1>C:\Users\chris\source\repos\LibraryTest\x64\Debug\LibraryTest.exe : fatal error LNK1120: 2 unresolved externals
1>Done building project "LibraryTest.vcxproj" -- FAILED.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
========== Build completed at 4:44 AM and took 01.050 seconds ==========

Please help. I've been trying to have libdogecoin work around a year now but end up coming back to check if it is stable enough to work on MSVC. This is the closest I've ever gotten it to work. I am trying to accept Dogecoin in my own projects and keep hitting a roadblock. I've compiled other libraries before for game development and never had an issue I couldn't figure out on my own.
Expected behavior
I expect to link the .lib files in my Visual Studio project and include the dogecoin/libdogecoin.h header file at the very list and be able to not get any linking errors.
Steps to reproduce:
I wrote the simplest of codes to test the compilation:
// Dependencies | std
#include <iostream>

// Dependencies | dogecoin
#include <dogecoin/libdogecoin.h>

int main(int argc, char* argv[]) {
	std::cout << "Program operating" << std::endl;

	dogecoin_ecc_start();
	dogecoin_ecc_stop();

	std::cout << "Program operating" << std::endl;
}

I used CMake to build the VS solution, opened and built the VS solution, copied the dogecoin.lib file into my test project, and finally linked the .lib files and the include folder into my project.
Screenshots

libdogecoin commit

Machine specs

OS: Windows 11 Pro
CPU: Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz   3.60 GHz
RAM: 64.0 GB (63.9 GB usable)
Disk size: 1 Tb x 2
Disk Type (HD/SDD): 2 SSDs installed in the mother board

Extra information
Here is the output that was printed when the VS solution was created:
Selecting Windows SDK version 10.0.22621.0 to target Windows 10.0.22631.
CMake Deprecation Warning at CMakeLists.txt:22 (cmake_minimum_required):
Compatibility with CMake < 3.5 will be removed from a future version of
CMake.
Update the VERSION argument  value or use a ... suffix to tell
CMake that the project does not need compatibility with older versions.
-- Selecting Windows SDK version 10.0.22621.0 to target Windows 10.0.22631.
fatal: not a git repository (or any of the parent directories): .git
--
--         ---( Libevent 2.1.12-stable )---
-- Available event backends:
-- CMAKE_BINARY_DIR:         C:/Users/chris/Desktop/libdogecoin-0.1.3-dev/src/libevent/build
-- CMAKE_CURRENT_BINARY_DIR: C:/Users/chris/Desktop/libdogecoin-0.1.3-dev/src/libevent/build
-- CMAKE_SOURCE_DIR:         C:/Users/chris/Desktop/libdogecoin-0.1.3-dev/src/libevent
-- CMAKE_CURRENT_SOURCE_DIR: C:/Users/chris/Desktop/libdogecoin-0.1.3-dev/src/libevent
-- PROJECT_BINARY_DIR:       C:/Users/chris/Desktop/libdogecoin-0.1.3-dev/src/libevent/build
-- PROJECT_SOURCE_DIR:       C:/Users/chris/Desktop/libdogecoin-0.1.3-dev/src/libevent
-- CMAKE_MODULE_PATH:        C:/Users/chris/Desktop/libdogecoin-0.1.3-dev/src/libevent/cmake/
-- CMAKE_COMMAND:            C:/Program Files/CMake/bin/cmake.exe
-- CMAKE_ROOT:               C:/Program Files/CMake/share/cmake-3.27
-- CMAKE_SYSTEM:             Windows-10.0.22631
-- CMAKE_SYSTEM_NAME:        Windows
-- CMAKE_SYSTEM_VERSION:     10.0.22631
-- CMAKE_SYSTEM_PROCESSOR:   AMD64
-- CMAKE_SKIP_RPA
TH:         NO
-- CMAKE_VERBOSE_MAKEFILE:   FALSE
-- CMAKE_C_FLAGS:            /DWIN32 /D_WINDOWS /W3
-- CMAKE_BUILD_TYPE:         Release
-- CMAKE_C_COMPILER:         C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.39.33519/bin/Hostx64/x64/cl.exe (id MSVC, clang 0, GNUC 0)
-- CMAKE_AR:                 C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.39.33519/bin/Hostx64/x64/lib.exe
-- CMAKE_RANLIB:             :
-- Configuring done (0.1s)
-- Generating done (0.1s)
-- Build files have been written to: C:/Users/chris/Desktop/libdogecoin-0.1.3-dev/src/libevent/build
MSBuild version 17.9.8+b34f75857 for .NET Framework
1>Checking Build System
Building Custom Rule C:/Users/chris/Desktop/libdogecoin-0.1.3-dev/src/libevent/CMakeLists.txt
event_core_static.vcxproj -> C:\Users\chris\Desktop\libdogecoin-0.1.3-dev\src\libevent\build\lib\Release\event_core.lib
Building Custom Rule C:/Users/chris/Desktop/libdogecoin-0.1.3-dev/src/libevent/CMakeLists.txt
event_extra_static.vcxproj -> C:\Users\chris\Desktop\libdogecoin-0.1.3-dev\src\libevent\build\lib\Release\event_extra.lib
Building Custom Rule C:/Users/chris/Desktop/libdogecoin-0.1.3-dev/src/libevent/CMakeLists.txt
event_static.vcxproj -> C:\Users\chris\Desktop\libdogecoin-0.1.3-dev\src\libevent\build\lib\Release\event.lib
Building Custom Rule C:/Users/chris/Desktop/libdogecoin-0.1.3-dev/src/libevent/CMakeLists.txt
Options used to compile and link:
USE_TESTS      = 1
WITH_TOOLS     = ON
WITH_NET       = ON
WITH_LOGDB     = ON
WITH_UNISTRING = ON
WITH_WALLET    = ON
USE_SSE2       = OFF
USE_TPM2       = ON
TEST_PASSWD    = OFF
openenclave    = OFF
library type   = Static
Configuring done (1.3s)
Generating done (0.1s)

Hello! Wrap your libdogecoin.h include with extern "C" since it's a C standard library. You can find some examples of C++ usage in the address.md: libdogecoin/address.md.

Were you able to resolve your issue @InTimeTechnologies? Thanks!

I'm going to go ahead and close this issue. Use extern if you're building with C++:
extern "C" {
#include "libdogecoin.h"
}


Add support for authSource connection string option

Connection string options are not supported at the moment, I would really like to have support for the authSource option.
Example:
  var mongodbUri = 'mongodb://user:pass@localhost/my_test_db?authSource=admin';

The "authAdmin" option makes it easier to centralize user management in a single database instead of creating users for/inside each database (users are created in admin but are given roles on other databases).
To test this, create a new user like this (copy paste when logged in with admin rights to mongodb shell):
use admin
db.createUser(
  {
    user: "dbuser",
    pwd: "dart",
    roles: [ { role: "readWrite", db: "my_test_db" } ]
  }
)

And after that it should be possible to connect and authenticate with this connection URI:
var uri = 'mongodb://dbuser:dart@localhost/my_test_db?authSource=admin';

From the command line the connection command looks like this (run "use my_test_db" after connected):
mongo --authenticationDatabase admin --username dbuser --password dart localhost

I have tried to look at the code how to add this but have not completely figured it out, at first we need to save the options part of the uri on the ServerConfig object. That should be easy inside _parseUri() since we can use 'uri.queryParameters["options"]' to get the options string parsed and ready to go. But after that I'm not sure where it should be passed on to the server or how to do that part... Do you think it would be rather simple to use that string or is it complicated @vadimtsushko?
Read more about connection string options here:

http://docs.mongodb.org/manual/reference/connection-string/#connections-connection-options

Hi, Robert.
I'll look at this. Can not give a concrete time when though, I'm a little time strapped right now

Okay, I understand, let me know if there is something I can do to help!

Hi, Robert. Last commit added authSource connection option to current (dev) version.
Could you check it on your scenarios?

Hi Vadim, I have tried this for my scenario and it works good. I don't follow fully on the testing, but maybe you mean because current testing uses mongolab and they simply don't use authSource? For a local mongodb instance that you control it should not be any harder than writing tests involving auth in general I think.
Either way I think the code needed for this looks pretty straight forward, if normal auth works authSource should work as well, not a huge problem if we don't have an explicit test at this point I think.

it's landed in 0.2.5-beta


Allow to specify formatter when invoking editor.action.formatSelection

I would like to configure a key binding to format the selection with Prettier.
However, the default formatter is configured to not be Prettier and I cannot change that.
I know there is "Format Selection With...", but I don't want to select Prettier every time.
This is what I have in mind:
{
    "key": "ctrl+shift+alt+f",
    "command": "editor.action.formatDocument",
    "args": {
      "formatter": "prettier"
    }
  },

Unfortunately, such formatter arg does not exist yet.

However, the default formatter is configured to not be Prettier and I cannot change that.

If you cannot change that than it is a strong signal that shouldn't be using it


[Feature Request] Add docstrings for constructors

To improve the experience for developers in IDEs, please fully describe all constructor parameters.
For example, please describe the parameters for AzureOpenAIModelConfiguration and OpenAIModelConfiguration. Currently only their types are shown. A string description and example can be very helpful.

I don't believe any more input is needed from me. (The stalebot in this repo seems to be tuned to respond really quickly to perceived stalneness, btw).


Add license

Great extension! I noticed that the extension has no license file. This makes it tricky for others to use the extension since the license is unknown.
https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository

Added!


Include file path only

Keep full source file path - this is nice for e.g. Debug output sinks. We can rely on the const char * _file_path  to remain valid (FILE macro).
Possibly one could even move the splitting of the filename to the sink and save the _file member?

please pull latest from masters so the travis build works

:+1:


Unhandled prefetch abort: breakpoint debug exception (0x222) at 0x00000000

Morning,
running Debian on
Linux pibroker 5.15.61-v7l+ #1579 SMP Fri Aug 26 11:13:03 BST 2022 armv7l GNU/Linux
with all updates installed enabling the adapter leads to:
Unhandled prefetch abort: breakpoint debug exception (0x222) at 0x00000000
filling up the logs very fast:
-rw-r-----   1 root     adm             1.7G Aug 30 20:26 kern.log
-rw-r-----   1 root     adm             1.7G Aug 31 07:29 syslog
Size has been reached within one hour.
In addition the adapter is eating 100% of one CPU

Disabling the map seems to be a Workaround

32 or 64bis OS? maybe same as #487 ?

32 Bit, standard Debian for Raspberry 4B

for 32 bit there is the needed canvas lib not compiled. Do change to 64 bit or use the adapter without map.

Changing to 64 bit is not that easy - especially for ONE  library not being ported (yet). I would recommend to adjust the readme to reflect that 32 bit apparently is not supported.

I can add some hints i  the readme

@ch90045 I had the same problem but I could solve it by switching the kernel to 64-bit.
With these instructions, it only took me two minutes and since then I haven't had any more problems with this error.

Thank you, mI will take this link in the readme

Thanks, nice to know. I took the long route of reinstall but this may be something to consider for my other Pi's


How to create an OR query?

When I execute the following search from the shell:
curl -XGET http://localhost:9200/documents/document/_search?q=content:Christopher

I get some search results.
However when I execute this:
    Tire.search 'documents' do
      query do
        boolean do
          should { string "title:*Christopher* " }
          should { string "content:*Christopher* " }
        end
      end
  end

I am not getting any results. The above query converts to the following curl query by the way:
url -X GET 'http://localhost:9200/documents/_search?pretty=true' -d '{'query':
{'bool':{'should':[
{'query_string':{'query':'title:*Christopher* '}},
{'query_string':{'query':'content:*Christopher* '}}]}}}'

Any ideas what am I missing here?

Hello,
I think * aren't necessary. Try something like:
Tire.search 'documents' do
  query do
    boolean(:minimum_number_should_match => 1) do
      should { string "title:Christopher" }
      should { string "content:Christopher" }
    end
  end
end

Is this working? I have this
boolean(minimum_number_should_match: 2) do
should { string("e_name:#{search[:name]}") } unless search[:name].blank?
should { string("e_name:#{search[:last_name]}") } unless search[:last_name].blank?
end
Even though I am only sending one param (name) it returns all of the matches, what I am doing wrong? Am i missing something?


What should we create for our project?

Good question.  I checked out a few youtube videos of previous CS6440 presentations.  The EHR aspect looks interesting.

EHR is fine by me :+1:


exceptions.GQLException: [{'message': 'service error', 'path': ['claimDropRewards']}]

05:15:17: Fatal error encountered:
05:15:17:
05:15:17: Traceback (most recent call last):
05:15:17:   File "main.py", line 155, in main
05:15:17:   File "twitch.py", line 587, in run
05:15:17:   File "twitch.py", line 648, in _run
05:15:17:   File "inventory.py", line 259, in claim
05:15:17:   File "inventory.py", line 142, in claim
05:15:17:   File "inventory.py", line 158, in _claim
05:15:17:   File "twitch.py", line 1387, in gql_request
05:15:17: exceptions.GQLException: [{'message': 'service error', 'path': ['claimDropRewards']}]
05:15:17:
05:15:17: Exiting...
05:15:18:
05:15:18: Application Terminated.
05:15:18: Close the window to exit the application.

Duplicate of #590.


Use HTTP POST for recording metrics

Use HTTP POST for recording metrics
Use body-parser library to set req.body
Updated readme instructions for curl

This change is

BTW the Travis failures look to be the same as the regular metrics branch.  We should fix this later but I'm thinking of doing that in a separate pull request.  The errors are:
Running "ts:moduleEnv" (ts) task
Compiling...
...
Using tsc v1.8.10
build/src/metrics/adaptors/datastore_use_events_repository.ts(1,25): error TS2307: Cannot find module 'gcloud'.
build/src/metrics/adaptors/datastore_use_events_repository_test.ts(1,25): error TS2307: Cannot find module 'gcloud'.
build/src/metrics/metrics_server/index.ts(1,26): error TS2307: Cannot find module 'express'.
build/src/metrics/metrics_server/index.ts(2,25): error TS2307: Cannot find module 'gcloud'.
build/src/metrics/metrics_server/server.ts(1,29): error TS2307: Cannot find module 'body-parser'.
build/src/metrics/metrics_server/server.ts(2,26): error TS2307: Cannot find module 'express'.
build/src/metrics/metrics_server/server.ts(3,25): error TS2307: Cannot find module 'gcloud'.
build/src/metrics/metrics_server/use_service.ts(1,26): error TS2307: Cannot find module 'express'.
build/src/metrics/model/metrics_report.ts(102,19): error TS2304: Cannot find name 'Set'.
build/src/metrics/tools/datastore_load_sample.ts(1,1): error TS6053: File '/home/travis/build/uProxy/uproxy/build/src/metrics/typings/globals/csv-parse/index.d.ts' not found.
build/src/metrics/tools/datastore_load_sample.ts(4,25): error TS2307: Cannot find module 'gcloud'.
build/src/metrics/tools/datastore_load_sample.ts(5,28): error TS2307: Cannot find module 'csv-parse/lib/sync'.
build/src/metrics/tools/generate_report.ts(1,25): error TS2307: Cannot find module 'gcloud'.

Change looks good. I have a few small comments.
On the error: Typings need to be installed in order for this to work. We should create a npm install script that does the typings installation.

Reviewed 5 of 5 files at r1.
Review status: all files reviewed at latest revision, 2 unresolved discussions, some commit checks failed.

src/metrics/typings.json, line 4 [r1] (raw file):

  "name": "uproxy-metrics",
  "globalDependencies": {
    "csv-parse": "registry:dt/csv-parse#1.1.0+20160602150508",

We need to keep the csv-parse typings for the dev tools.

src/metrics/metrics_server/use_service.ts, line 18 [r1] (raw file):

      if (!req.body) {
        console.error(`Request body not found. req = ${req}`);
        res.status(500);

We need to differentiate client error (4xx) from server errors (5xx).
If the body is empty or failed to parse, you should return a client error
It the body is absent (null, undefined), you should return a server error.
This may sound picky, but HTTP error codes are very important to get right, as they affect caching and client-side retry behavior, among other things.

Comments from Reviewable

Review status: all files reviewed at latest revision, 2 unresolved discussions, some commit checks failed.

src/metrics/typings.json, line 4 [r1] (raw file):
Previously, fortuna (Vinicius Fortuna) wrote…
> We need to keep the `csv-parse` typings for the dev tools.

Good catch, I accidentally deleted this

src/metrics/metrics_server/use_service.ts, line 18 [r1] (raw file):
Previously, fortuna (Vinicius Fortuna) wrote…
> We need to differentiate client error (4xx) from server errors (5xx).
> If the body is empty or failed to parse, you should return a client error
> It the body is absent (null, undefined), you should return a server error.
>
> This may sound picky, but HTTP error codes are very important to get right, as they affect caching and client-side retry behavior, among other things.

I agree with returning 400 or 500 depending if the error is from the client or server, but I think the current logic is correct.  If req.body is undefined or null then ```!req.body``` will be true.  However if req.body is {}, ```!req.body``` will be false, so we won't return a 500 here, but will instead return a 400 below because ```req.body.date``` will be undefined

Comments from Reviewable

Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

src/metrics/metrics_server/use_service.ts, line 18 [r1] (raw file):
Previously, dborkan wrote…
> I agree with returning 400 or 500 depending if the error is from the client or server, but I think the current logic is correct.  If req.body is undefined or null then ```!req.body``` will be true.  However if req.body is {}, ```!req.body``` will be false, so we won't return a 500 here, but will instead return a 400 below because ```req.body.date``` will be undefined

You are right, an empty object casts to true. I'm still learning Javascript and I thought it would cast to false.
What happens when the json is malformed? Which code path will it trigger?

Comments from Reviewable

Review status: all files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

src/metrics/metrics_server/use_service.ts, line 18 [r1] (raw file):
Previously, fortuna (Vinicius Fortuna) wrote…
> You are right, an empty object casts to true. I'm still learning Javascript and I thought it would cast to false.
>
> What happens when the json is malformed? Which code path will it trigger?

If I send bad JSON like "{blah}", the client gets the response:
```
HTTP/1.1 400 Bad Request
X-Powered-By: Express
X-Content-Type-Options: nosniff
Content-Type: text/html; charset=utf-8
Content-Length: 899
Date: Tue, 16 Aug 2016 18:09:49 GMT
Connection: keep-alive
SyntaxError: Unexpected token b    at Object.parse (native)    at parse (/Users/dborkan/github/uproxy-metrics/src/metrics/node_modules/body-parser/lib/types/json.js:88:17)    at /Users/dborkan/github/uproxy-metrics/src/metrics/node_modules/body-parser/lib/read.js:116:18    at invokeCallback (/Users/dborkan/github/uproxy-metrics/src/metrics/node_modules/raw-body/index.js:262:16)    at done (/Users/dborkan/github/uproxy-metrics/src/metrics/node_modules/raw-body/index.js:251:7)    at IncomingMessage.onEnd (/Users/dborkan/github/uproxy-metrics/src/metrics/node_modules/raw-body/index.js:307:7)    at emitNone (events.js:67:13)    at IncomingMessage.emit (events.js:166:7)    at endReadableNT (_stream_readable.js:905:12)    at doNTCallback2 (node.js:450:9)

and the server prints:

SyntaxError: Unexpected token b
at Object.parse (native)
at parse (/Users/dborkan/github/uproxy-metrics/src/metrics/node_modules/body-parser/lib/types/json.js:88:17)
at /Users/dborkan/github/uproxy-metrics/src/metrics/node_modules/body-parser/lib/read.js:116:18
at invokeCallback (/Users/dborkan/github/uproxy-metrics/src/metrics/node_modules/raw-body/index.js:262:16)
at done (/Users/dborkan/github/uproxy-metrics/src/metrics/node_modules/raw-body/index.js:251:7)
at IncomingMessage.onEnd (/Users/dborkan/github/uproxy-metrics/src/metrics/node_modules/raw-body/index.js:307:7)
at emitNone (events.js:67:13)
at IncomingMessage.emit (events.js:166:7)
at endReadableNT (_stream_readable.js:905:12)
at doNTCallback2 (node.js:450:9)

---

*Comments from [Reviewable](https://reviewable.io:443/reviews/uproxy/uproxy/2702)*
<!-- Sent from Reviewable.io -->

src/metrics/metrics_server/use_service.ts, line 18 [r1] (raw file):
Previously, dborkan wrote…
> If I send bad JSON like "{blah}", the client gets the response:
> ```
> HTTP/1.1 400 Bad Request
> X-Powered-By: Express
> X-Content-Type-Options: nosniff
> Content-Type: text/html; charset=utf-8
> Content-Length: 899
> Date: Tue, 16 Aug 2016 18:09:49 GMT
> Connection: keep-alive
>
> SyntaxError: Unexpected token b    at Object.parse (native)    at parse (/Users/dborkan/github/uproxy-metrics/src/metrics/node_modules/body-parser/lib/types/json.js:88:17)    at /Users/dborkan/github/uproxy-metrics/src/metrics/node_modules/body-parser/lib/read.js:116:18    at invokeCallback (/Users/dborkan/github/uproxy-metrics/src/metrics/node_modules/raw-body/index.js:262:16)    at done (/Users/dborkan/github/uproxy-metrics/src/metrics/node_modules/raw-body/index.js:251:7)    at IncomingMessage.onEnd (/Users/dborkan/github/uproxy-metrics/src/metrics/node_modules/raw-body/index.js:307:7)    at emitNone (events.js:67:13)    at IncomingMessage.emit (events.js:166:7)    at endReadableNT (_stream_readable.js:905:12)    at doNTCallback2 (node.js:450:9)
> ```
>
> and the server prints:
> ```
> SyntaxError: Unexpected token b
>     at Object.parse (native)
>     at parse (/Users/dborkan/github/uproxy-metrics/src/metrics/node_modules/body-parser/lib/types/json.js:88:17)
>     at /Users/dborkan/github/uproxy-metrics/src/metrics/node_modules/body-parser/lib/read.js:116:18
>     at invokeCallback (/Users/dborkan/github/uproxy-metrics/src/metrics/node_modules/raw-body/index.js:262:16)
>     at done (/Users/dborkan/github/uproxy-metrics/src/metrics/node_modules/raw-body/index.js:251:7)
>     at IncomingMessage.onEnd (/Users/dborkan/github/uproxy-metrics/src/metrics/node_modules/raw-body/index.js:307:7)
>     at emitNone (events.js:67:13)
>     at IncomingMessage.emit (events.js:166:7)
>     at endReadableNT (_stream_readable.js:905:12)
>     at doNTCallback2 (node.js:450:9)
> ```

Note the server trace is printed from within the body-parser code, not from our code, and we never get to our ```recordUse``` method when JSON.parse fails

Comments from Reviewable

:thumbsup:

Review status: all files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

src/metrics/metrics_server/use_service.ts, line 18 [r1] (raw file):
Previously, dborkan wrote…
> Note the server trace is printed from within the body-parser code, not from our code, and we never get to our ```recordUse``` method when JSON.parse fails

Awesome. Express takes care of that for us!

Comments from Reviewable


请修改import

请将
#import <disk_space/disk_space-Swift.h>
改为
#if __has_include(<disk_space/disk_space-Swift.h>)
#import <disk_space/disk_space-Swift.h>
#else
#import "disk_space-Swift.h"
#endif

@xtuck
Since this package hasn't been updated in 2 years and the maintainers haven't responded to any issues or pull requests, I created a new repository: https://github.com/activcoding/disk_space_2. The updated package, which should work, is available here: https://pub.dev/packages/disk_space_2.


Undocumented Extension Required - PHP 7.2 GMP

Just leaving a note for an update to the documentation and the install script. At least for PHP 7.2, the php7.2-gmp extension is required for the add flight menu to work, along with likely other things I haven't discovered yet. Only was able to discover this when enabling debug mode to see the reason for an error.
(1/1) RuntimeException
Missing BC Math or GMP extension.

Hmm, that's a weird one, well, for that menu at least. Thanks for the heads up


Refactor searchpromotions add and edit view to CBV

In this PR I've converted search promotions add view from FBV to CBV as a part of #8365 .

I will try to take a look at this but I know @laymonage is also actively working in this space (CBV adoption).
Thanks @rohitsrma !

Superseded by #12614.


Closing "Instagram Find it Free in the App Store" message kills feed

clicking the x to close this message causes the Instagram feed to disappear.  Only way to recover is to close ramme via the task manager in windows.

Thanks for reporting the issue. We'll look into it.

I guess I missed that banner in the latest fix. Will dive into it again.


(docs) Adding example to curl docs

Merging up from 5.2.x

Test FAILed

Test FAILed

CLA signed by all contributors.


Encrypt private metadata

Apps should encrypt & decrypt data stored in private metadata (zero trust).
Possibly MetadataManager can use encryption logic. SDK can provide default one, but optional implementation should be possible to provide

Rel https://github.com/saleor/saleor-app-template/pull/89


Run steps sequentially / retry when parallel steps exceed memory quota

Is this a BUG REPORT or FEATURE REQUEST?: BUG REPORT
What happened:
We set a requests.memory quota for the workflows namespace. Then we ran a workflow with parallel steps which together (but not singly) exceeded the quota. The workflow failed these steps with the following error in the workflow-controller:
time="2018-02-06T14:51:34Z" level=info msg="Updated phase Running -> Error" namespace=argo-workflows workflow=steps-6kgn6
time="2018-02-06T14:51:34Z" level=info msg="Updated message  -> pods \"steps-6kgn6-2822283003\" is forbidden: exceeded quota: argo-workflows-quota, requested: requests.memory=8256Mi, used: requests.memory=8256Mi, limited: requests.memory=12Gi" namespace=argo-workflows workflow=steps-6kgn6

What you expected to happen:
The steps should have been run sequentially and succeeded. If separate processes (i.e. other argo workflows) are causing the quota to be exceeded, argo should be able to retry.
How to reproduce it (as minimally and precisely as possible):
Set a requests.memory quota for the workflow namespace...
apiVersion: v1
kind: ResourceQuota
metadata:
  name: argo-workflows-quota
spec:
  hard:
    requests.memory: 12Gi

Submit the following workflow...
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: steps-
spec:
  entrypoint: hello-hello-hello

  templates:
  - name: hello-hello-hello
    steps:
    - - name: hello1
        template: whalesay
        arguments:
          parameters:
          - name: message
            value: "hello1"
    - - name: hello2a
        template: whalesay
        arguments:
          parameters:
          - name: message
            value: "hello2a"
      - name: hello2b
        template: whalesay
        arguments:
          parameters:
          - name: message
            value: "hello2b"

  - name: whalesay
    inputs:
      parameters:
      - name: message
    container:
      image: docker/whalesay
      command: [cowsay]
      args: ["{{inputs.parameters.message}}"]
      resources:
        requests:
          memory: 8Gi

Anything else we need to know?:
Environment:

Argo version:

$ argo version

argo: v2.0.0-beta1
BuildDate: 2018-01-18T22:06:03Z
GitCommit: 549870c1ee08138b20b8a4b0c026569cf1e6c19a
GitTreeState: clean
GitTag: v2.0.0-beta1
GoVersion: go1.9.1
Compiler: gc
Platform: linux/amd64

Kubernetes version :

$ kubectl version -o yaml

clientVersion:
buildDate: 2018-01-18T10:09:24Z
compiler: gc
gitCommit: 5fa2db2bd46ac79e5e00a4e6ed24191080aa463b
gitTreeState: clean
gitVersion: v1.9.2
goVersion: go1.9.2
major: "1"
minor: "9"
platform: linux/amd64
serverVersion:
buildDate: 2017-12-15T20:55:30Z
compiler: gc
gitCommit: 925c127ec6b946659ad0fd596fa959be43f0cc05
gitTreeState: clean
gitVersion: v1.9.0
goVersion: go1.9.2
major: "1"
minor: "9"
platform: linux/amd64

There is a retryStrategy field which will allow container steps to be retried in the event of a failure (unfortunately this does not have a backoff policy yet). Also, in 2.1, there will be a parallelism feature to limit the parallelism of a workflow and/or template. Will these satisfy your use case?
I don't think scheduling algorithms based on resources belongs in the controller because this is supposed to be the responsibility of an admission controller.

Thanks, hmmmm. I didn't know about retryStrategy or k8s Admission Controllers. From a quick read, I don't think that an Admission Controller would help much here. What we're trying to do is limit the resources that a particular namespace can use at one time, but not blocking a workflow unless a single step claims too many resources. This does sound more like the job a (custom?) scheduler should be doing, perhaps in combination with an Admission Controller which stops you submitting a pod which could never run given the scheduler quotas.

My team is in a similar boat right now too.
Jobs, StatefulSets, Deployments, etc all check the CPU and Memlimit quotas and retry until pods can be scheduled.
Parallelism doesn't satisfy our use case as we want to limit the total sum of work that a user has running vs limiting single workflows to a specified amount.

I believe PR https://github.com/argoproj/argo/pull/1096 is trying to solve this. Will try to revive this PR based on current master.

Hi, PR #1096 is closed but not because it was merged. I'm guessing the idea of limiting the parallel executions didn't take off ? Thanks

I closed that PR because it was inactive for 1 year. I believe that you can use the parallelism feature to achieve the same goal?

Indeed you can, it just took me a while to figure-out how.
For anyone else seraching :
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  name: my_workflow
  generateName: my_workflow
spec:
  parallelism: 2
 ...

Closed by https://github.com/argoproj/argo/pull/2385


set SortOrder before header on SAMTextWriter

fixes #21

Thanks for the patch!

Just ran into this.  Any chance you could cut a point release?

Yes, we'll do that, hopefully this weekend.


Fix the Python style guide on string formatting

Our current Python style guide says to use .format() to compose strings with formatted variables inside them, but based on this comment
https://github.com/bigchaindb/bigchaindb/pull/476#issuecomment-234239734
it seems that our Python style guide is wrong. I'm not sure when to use what now, so someone who understands that should update our Python style guide. @vrde I will assign this to you but feel free to assign it to someone else.

Is this specific to logging only?
With respect to logging, different formatting styles are available. See https://docs.python.org/3/howto/logging-cookbook.html#formatting-styles
and https://docs.python.org/3/library/logging.html#logging.basicConfig

@ttmc I think @vrde's comments were more specific to logging (which has its own set of best practices aside from string composition). PEP 3101 basically replaces the % operator with .format() wholesale.
We can add (or link to) some best practices for logging, but that might not fall inside the domain of the style guide.


Reactive Colours and Modal tweaks

Updates in this pull request

colours change reactively when colors variable changes from outside of the plugin, this allows you to use sessions to sync colour pallets across multiple editors and dynamically add colours as they are used
added native color picker to the modal input by switching out the input type depending on if its a color picker needed (detected by event type)
only load the modal html when its needed not on runtime to facilitate the above and save extra html load when may not be needed, rather than the current show/hide type.

This reads better imo. EDIT: Wouldn't need block too. @aam-git
  $: btns = colors
      .map((color) => ({ color }))
      .concat([{ text: '#', modal: true }]);

Nice, just updated the pull request to add this :)

lgtm. @nenadpnc Just noticed spaces are not consistent in the codebase. There is a mix of tabs, 2 spaces, and 4 spaces. After this is approved and merged, I can submit a PR to convert all to the js standard of 2 spaces.
EDIT: @aam-git If you change the indentation back to 2 spaces, it will de-noise the commit histories.

Done...  Odd, not sure why vscode did that, I don't normally let it format svelte files.


using the junit formatter doesnt work

using --format junit doesnt work because underneath gauntlt, cucumber wants a --dir passed to it.

any work arounds for this?

I am also facing the same issue, I need to generate the JUnit xml, however if I run the command without --out option it gives following error.
You must specify --out DIR for the junit formatter
If i provide --out parameter, then I get following error.
Error: unknown argument '--out'.
would someone please let me know how to generate the JUnit report

+1 Have the same issue.

I realize this doesn't really contribute to the fix of this issue, but for those held-up by this issue there is an easy workaround. In your working directory create the file './config/cucumber.config' and add the --out setting there ... for example:
default: --out /var/tmp/gauntlt/junit

I found that I had to use a fully-qualified path, but that is an easy problem to work around in your CI jobs. Hope that helps.

I believe this is fixed in https://github.com/gauntlt/gauntlt/pull/96


[🐛] Activity error

Description
When I try to call launchCamera, I get an error. If I pass an option object as argument, it returns Activity error in response.errorMessage. If I don't pass an option object, it returns Attempt to invoke interface method 'void.facebook.react.bridge.Callback.invoke(java.lang.Object[])' on a null object reference. But launchMediaLibrary works as expected.
How to repeat issue and example

calls launchCamera with or without options object

Solution
No idea.
Additional Information

Image Picker version: 3.1.4
React Native version: 0.61.5
Platform: iOS and Android
Development Operating System: MacOS

Show your code, options and callback is compulsory in the API.
What is your android target SDK and in which version of android are u running the app?

Show your code, options and callback is compulsory in the API.
What is your android target SDK and in which version of android are u running the app?

What is your android target SDK and in which version of android are u running the app?

Target SDK is 29 and running on Android 10.
I tried other library and I'm getting this error as well.  So I think that isn't a problem with this library, but with something in my project. So I'm going to close this issue. Anyway, thanks for your attention.

What is your android target SDK and in which version of android are u running the app?

Target SDK is 29 and running on Android 10.
I tried other library and I'm getting this error as well.  So I think that isn't a problem with this library, but with something in my project. So I'm going to close this issue. Anyway, thanks for your attention.

It's happening for me too, it's not related to project i think. Because the same build/apk working fine in android 10, not working in android 11. tried 2 different android 11.  Both camera and gallery not working. Tried the latest version: 3.1.4
It throws error:
errorMessage: "Activity error"
errorCode: "others"

It's happening for me too, it's not related to project i think. Because the same build/apk working fine in android 10, not working in android 11. tried 2 different android 11. Both camera and gallery not working. Tried the latest version: 3.1.4
It throws error:
errorMessage: "Activity error"
errorCode: "others"

@JakariaAmin
Target SDK 30 not supported change to 29.
Read this thread https://github.com/react-native-image-picker/react-native-image-picker/issues/1587

It's happening for me too, it's not related to project i think. Because the same build/apk working fine in android 10, not working in android 11. tried 2 different android 11. Both camera and gallery not working. Tried the latest version: 3.1.4

It's happening even on Android 10 for me. But only with camera option. Gallery opens without any problem. I tried other libraries, but without success. Same error.

@JakariaAmin
Target SDK 30 not supported change to 29.
Read this thread #1587

i have target SDK 29 but am  getting same issue , min SDK is 21
am testing on device with Android 7.0

Getting the same error with this:
        buildToolsVersion = "29.0.2"
        minSdkVersion = 23
        compileSdkVersion = 29
        targetSdkVersion = 29

launchCamera(
{
mediaType: 'photo',
maxHeight: 1024,
maxWidth: 1024,
quality: 0.5,
},
()=>{}
);
using version 3.2.1

anyone has find a fix for this problem?

on my case this only presents when the android device didn't have a Camera app installed. still, this error message could be improved

Got it working with
buildToolsVersion = "31.0.0-rc3"
minSdkVersion = 21
compileSdkVersion = 30
targetSdkVersion = 30
And a virtual device running with API level 29
But not working with a virtual device running with API level 30

I had to downgrade the compileSdkVersion and targetSdkVersion from 30 to 29 and the errors magically stopped. I tested on a physical device - Google Pixel 2. Upgrading the buildToolsVersion to 31 did not work for me. Camera and Gallery are both working fine now.
Before
ext {
buildToolsVersion = "30.0.3"
minSdkVersion = 21
compileSdkVersion = 30
targetSdkVersion = 30
}
After
ext {
buildToolsVersion = "30.0.3"
minSdkVersion = 21
compileSdkVersion = 29
targetSdkVersion = 29
}

I think there's something to do with this issue, but I'm not sure.


Animated Blocks Not Animating

I've made an animation, installed GeckoLib API, and told the block to play the animation when placed, yet it still doesn't animate. This is occuring to all of my animated blocks and items.
The procedure that occurs when placed by

Ignore that for whatever reason the gif is at half speed, the animation is actually 1.13 seconds long. Animation 0 is just two keyframes of nothing.

The animation not playing in-game. It instead places then waits 22.6 ticks and gets removed (Which is intended, but the lack of animation isn't.)

Your animation names are wrong

It doesn't seem like I can enter letters into the [play animation named (x) to the block at x y z] block though, only numbers

When you make the animation, rename the whole thing to 0 or 1, not just the last word.

Your animations are animation.popup.0 and 1, not 0 and 1.


build(deps): upgrade dependencies to fix vulnerable issues

Description
Upgrade the dependencies which cause vulnerability.

[ ] Tests for the changes have been added (for bug fixes / features)
[x] The commit message(s) follow conventional commits
[ ] Documentation has been added / updated (for bug fixes / features)
[x] Changes follow the contributing document.

Motivation and Context

To eliminate the vulnerable dependencies.
After upgrade

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Which merge strategy will you use?

[x] Squash
[ ] Rebase (REVIEW COMMITS)

Lets add a breaking change commit to signal this will be breaking changes.


Close input tag on helpfulness form addition to page template

This unclosed tag was throwing errors in the ePUB output.
Refs aspnet/Docs#1648

Hi @agjohnson, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

@danroth27  please review

Dup of #1648  fixed by 592d0b4f698e1cbff2358b91ceff8c389f7dd94b


⚠ Mobitopup has degraded performance

In d6fc599, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 3888 ms

Resolved: Mobitopup performance has improved in 1448312.


Add pre_exec_hooks

Functionality wise this works well. However I am unsure where to place this. I feel in the .docker_scripts directory it is too hidden. In the root directory it is to top level for its functionality. In the 02_devel_image directory it seems okay, but would need some further work to properly integrate/copy/apply it to the release images.
Maybe it could be time for a top level config directory?

I don't see the need to evaluate a list of files in a directory. if someone has a lot of calls that should be seperated, the files can still be called from the main hook script
I'd say we directly create more hooks and also a hooks folder on top level_
hooks/pre_exec.bash
hooks/post_exec.bash
hooks/pre_stop.bash
hooks/post_stop.bash
hooks/pre_delete.bash
hooks/post_delete.bash
Any more possible hooks?
Where we'd have to make sure e.g. pre/post_delete gets called not only on ./delete.bash but also when the old container gets deleted because a newer image is present
The example above are hooks for scripts in this repo, we could also have docker command based hooks: pre/post[run, start, exec, stop, delete]
What we could do in terms of folder organization is to just document the possibility to have these hooks but not provide the (empty) files in the main repo, so the scripts check if the hook script exists and is not, nothing is executed.


SDWebImage compiler warning

KenBurns.swift is giving me a compiler warning on line 165 because of the call to the deprecated SDWebView function setImageWith:placeholder:.
Instead use the sd_setImageWithURL:placeholderImage: function.

OK, submit a PR and I'll accept it.  Which version of SDWebImage are you using? The KenBurns podspec specifies ~> 3.8.1, but the latest is 4.0.0

For some reason the SDWebImage Info.plist says version 3.8.2 but I can see that KenBurns specifies 3.8.1. I've just recently taken over this project so I don't really know why this is but I guess updating KenBurns to use the new SDWebImage api will fix the issue.

Yeah @nannestad better to move forward than to stay on the earlier version. As for 3.8.2, I think it's because it's specified as ~> 3.8.1 which will be anything >= 3.8.1 and < 4.0.0 (locks to major version = 3 and minor+patch >= 8.1, which 3.8.2 falls under).

I can't see that the pod is updated with these changes: https://cocoapods.org/?q=kenburn Am I doing something wrong?

Yeah you're right. The ruby symbol prefix : was making the validation fail.  After this commit https://github.com/calm/KenBurns/commit/fe35a84657295a3128a713b2a45a163048409060 it worked and is now live:
Tylers-MacBook-Pro-2:KenBurns tsheaff$ pod spec lint

 -> KenBurns (0.2.8)

Analyzed 1 podspec.

KenBurns.podspec passed validation.

Tylers-MacBook-Pro-2:KenBurns tsheaff$ pod trunk push

[!] Found podspec `KenBurns.podspec`
Updating spec repo `master`
Validating podspec
 -> KenBurns (0.2.8)

Updating spec repo `master`

--------------------------------------------------------------------------------
 🎉  Congrats

 🚀  KenBurns (0.2.8) successfully published
 📅  May 9th, 09:48
 🌎  https://cocoapods.org/pods/KenBurns
 👍  Tell your friends!
--------------------------------------------------------------------------------


Adding many missing logo_URIs in chaininfo json files.

Utilized existing token logos, online sources, and generation of svgs from pngs.

@JeremyParish69 agreed on that, they are removed... we were working on a project where I needed them, but I'll omit them in this PR.


ci: Use GitHub Actions

instead of Travis-CI and Appveyor
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: link tbd.
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[x] CI related changes
[ ] Documentation content changes
[ ] tooling / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Appveyor is used for testing
Travis-CI is used for performance checks
Issue Number: N/A
What is the new behavior?
GitHub Actions is used for both testing and performance checks
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information
The run for this commit can be seen here https://github.com/nemchik/webpack-config-plugins/actions/runs/729587384

Thank you very much for your great work. I've merged your PR - even if I will still make some adjustments. (e.g. as a replacement for appveyor i would like to run the tests also on windows)

I didn't notice until checking just now, travis used to take over 40 minutes for performance tests, gha is doing it in under 10. Solid win!


Order Book and Broadcast Deposit

Adding the Order Book endpoint to the public client and the need for broadcasting signed deposits to the Ethereum network.

Pull Request Test Coverage Report for Build 57

26 of 29 (89.66%)  changed or added relevant lines in 6 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.3%) to 91.418%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

switcheo/ethereum/signatures.py
2
3
66.67%

switcheo/public_client.py
5
7
71.43%

Files with Coverage Reduction
New Missed Lines
%

switcheo/ethereum/signatures.py
1
26.67%

Totals

Change from base Build 51:
-0.3%

Covered Lines:
735

Relevant Lines:
804

💛  - Coveralls


fix NodeGpuCountChanged definition issue

Coverage remained the same at 34.223% when pulling 03dfa98c35480b8b124808976d1de58ba5552ba5 on suiguoxin:node-gpu-count into 11b92a1cac79647bb8521c9f57884e0ed9b6d17d on microsoft:master.


pasting behavior

Thanks for a great tool.  I'm running into an issue with pasting text.  I see the note in the README about it only working on active windows, but even if I make the window active first, I'm getting the right-click menu multiple times, once for each window.  I am using KiTTY.  Also, I tried using shift-insert  to paste, and while that works, it doesn't always send the text to all the connected windows.  Is there another way that text can be pasted?  Thanks for your help.

Currently there is no other way to paste things to all the connected windows. Because it works with PuTTY, I'll guess it must be an issue with KiTTY, which needs some more investigation and testing.

Thanks, here is a little more information:

My original issue started because under Window -> Selection, for "Action of mouse buttons", I had "Windows" selected, so that when I right-click, I get a menu.  When I do that even in regular PuTTY, I get the right-click menu multiple times.
If I switch back to "Compromise", when I right-click to paste in regular PuTTY, it doesn't always send the text to all connected windows.
Using shift-insert to paste, even in regular PuTTY, doesn't always send the text to all connected windows.


chore: custodian s3 RFC

This is an outline of how we can use the Custodian to inject s3 credentials in requests for launching notebook sessions for the specific project we discussed.
Please feel free to comment and to commit to this branch.

@martinfontanet could you please weigh in here on the RFC? If it looks good and is workable we should finalize it and merge.

I just added some changes to the diagram in #10.
Regarding the first question:
At the moment, the Custodian uses the Renku's Keycloak instance as IDP. It uses OpenID connect (from Renku Keycloak) to authenticate users at both the contract signature step and the session creation step, so it does not need any extra credentials. This means that the link only requires the necessary parameters to start a session with the Renku API (except the S3 credentials, which are handled by the Custodian).
This also partly answers the third question, as there are currently no users that are registered with the Custodian but not with Renku.

@olevski @martinfontanet what's the status here? would be nice to merge it if it's being used/implemented/considered, otherwise lets close it?

@rokroskar @martinfontanet has done some work on this as far as I know. Not sure where the code is or what the status is.

@rokroskar this is now up-to-date and ready to be merged.


Cursor covers the letter it is on

Description of the new feature/enhancement

Proposed technical implementation details (optional)

The cursor on the left is the active one, the one on the right is the one after I click on a letter. The active one seems to be covering the letter it is on. Is there a setting I don't know about that would let me see the letter?
Thank you!

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #1203 for more discussion.
/dup #1203


Errors are hidden by Lint warning when Powertools is enabled

Description
If Lint issues a warning, it will top the error, showing an orange squiggly instead of a red one and the only way to find out the underlying error is by running a full build.
In this screenshot, it is not clear that "Only functions may be marked inline" is actually an error and not a warning:

Or (totally hiding the actual syntax error):

Repro steps
You can see this in action in many ways, but this simple example is the one used in the screenshot:
let inline ( $# ) x = if isNull x then String.Empty else x

Or the following (without inline), totally hiding the error:
let ( $# ) x = if isNull x then String.Empty else x

Expected behavior
I would expect the error to have higher precedence when hovering over and when drawing the squiggly. In fact, this is what is shown when starting Visual Studio in /SafeMode:

Or:

There is more than one thing wrong with the code, result of using a disallowed operator character, but none of these errors is shown.
Actual behavior
The actual syntax errors are hidden. This can be seen in many situations where there is both a warning and an error on the same spot (and this happens a lot). This repro is just one of many ways to repro this.
Known workarounds
Run the build and inspect the build log. Or disable Lint integration. But that isn't really a workaround.
Related information

Visual Studio 2015, Update 3
Visual F# PoswerTools 2.5.6
F# 4.0

Problem has been verified by trying to repro with extensions disabled (i.e., /SafeMode).

We're not gonna fix bugs for VS 2015 and we are not gonna support VS 2017. I believe there will be FsLint integration in VS 2017 (via Roslyn Analyzers rs I think).

@vasily-kirichenko, that's a bummer, I wasn't aware. Could we add that somewhere when people make a report, for instance in the template? It would save the developers and reporters a lot of time (and frustrations afterwards).

@abelbraaksma Sorry for wasting your time :( Basically we are moving all the functionality to Visual F# Tools, about 70% done. So consider VFPT as deprecated.

@vasily-kirichenko, no, not a problem, I was just surprised. I see you edited the readme.md, thanks!


Support flowtype definition for flow-typed (WIP)

This is a flowtype definition for Vue.js
If this pull request does not need, feel free to close it.
Like a TypeScript, I would like to unite the way of providing these definition files.
Already in the flow directory,  as @evan have said in here,
but these definition files are defined that specialized in due to internal develop.
I feel these definition files don't give good development experimence to users, to say the least.
As well as typescript, I hope to provide the official flowtype definitions.
I'm considering the below specs:

Adding decls directory for flowtype definition
Put type definitions in the same directory structure as flow-typed
Testing type definitions with flow-bin (already installed with package.json)
Support from flowtype version of package.json

Hi @kazupon , thank you for this contribution.
I'm reporting my experience with integrating Flow with Vue. But I think this might be helpful to you.

(Flow) definition files don't give good development experimence to users

Providing good typing experience would be very hard in flow. Mainly due to flow's inherent expressiveness:
this-type: https://github.com/facebook/flow/issues/452
library augmentation: https://github.com/facebook/flow/issues/396
Without this -type, we cannot define Vue's methods/data option. Without augmentation, we cannot extend Vue's option object (which is a practice quite common in Vue community). These two are simply deal breakers.
Arguably TypeScript definition file does not provide decent experience (for now, will be better after TS2.3). But TS definition serves as a basic ground for library authors like vue-class-component.
Sadly, class component like approach utilizes stage-1 decorator syntax, which flow just ignores now. This simply means flow-definition isn't needed. 😞
Other typing approach like chain-api isn't doable in flow due to this-typing problem stated above.
Generally I would dare to say Flow is (naturally) React biased. It is very hard to integrate other frameworks with it...

@HerringtonDarkholme
Thank you for your advise!
When I'm implementing flow type definition of vue, I encountered to it.
In flow version, I feel so difficulty.
Flow and Vue API not are very compatible.  😞
In this reason, I'll pend this PR once.

@kazupon @HerringtonDarkholme, hello. I'm kinda confused on this topic. I'm seeing some flowtype defs in /flow directory of the vue (as well as vue-router) project. But in the mean time this PR is pended. What's the status of current definitions?

@StreetStrider
Sorry to confuse you. 🙇
Vue core or Vue official plugins have some flowtype definitions, But these are for internal developement. in this reason, I'll try to improve, As I have mentioned in the above, I have encountered difficulties.

@StreetStrider The definitions in the /flow directory of the vue and vue-router repositories are used during delevopment of those libraries - they offer typings of the internal APIs, and are not suited to be used by the users of those libraries because the public APIs are not sufficiently typed as of now.
As @HerringtonDarkholme explained, that is hard to do currently, without a possibilty to  type this in Flow.

I see. 🤔  the main obstacle is Flow does not allow determine this type as a part of function signature and Vue rely (heavily) on it. Why not just omit it? The rest of the signature will be under type control. This isn't ideal typedef but it is better than nothing at all.
In light of this extensively used in Vue architecture this would look worthless (defs will be weak), but I would satisfy any Flowtype defs for Vue becaue of facebook/flow#1548. tl;dr: you can't both import module and flow-ignore it, you'll get error in either case. I personally use stub for Vue which is created by flow-typed. It silences all errors but effectively checks nothing.

@kazupon, any updates on this? I'd enjoy using Flow type checking with Vue but it actually looks like they are interested only in React ecosystem atm.

This would be a nice feature indeed.

@kazupon any news about that? Thanks!

Until this-type: facebook/flow#452 and library augmentation: facebook/flow#396 are supported in Flow hardly can we take any further action.

@kazupon what about providing partial flow support for now? Is it possible?
I know, that we can not extend existing library definitions, but still. I am had some experiments to be able to annotate vue + vuex. I came up with something like this (oversimplifying here):
// @flow

interface Vue {
  $isServer: boolean;
  $on(event: string, callback: Function): any;
}

interface Vuex$Vue {
  $store: Object;
}

class MyComponent implements Vue, Vuex$Vue {
  $isServer = false
  $store = {}

  $on (event: string, callback: Function) {
  	callback(event)
  }
}

Link to playground: https://flow.org/try/#0PTAEAEDMBsHsHcBQiCWA7ALgUwE6QIYDGWoAagK4kDeiooAJCgM4DKuAbrgFygBGssaFnxoA3LQaw0ACiydMPJhhzoA5gBpQhfNGi8iAax4AxcmkIYUUgJQ8RAT3EBfZOmx4iJClgAe9b6A0dPRKsDhYPADyvABWWBbOyITQ+ExMoACy9gDCsAC2AA5SWJigKIVCeSUY6d6a3n4BQQzMbDicOKAAvKAE0ExYEiEYYSQ9VC50Q1KgsvIYispqmtq6+oRGoKbmljaBEgCQq3qGc9XWEi5OQA
You can join me with my attempts here: https://github.com/sobolevn/vue-flow-typed

Closing as we will be focusing on TS for userland type support.


Update use-spam-notifications-to-release-and-report-quarantined-messa…

…ges.md
Updating to reflect the ESN changes.

@nenonix @JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.


Tooltip margin problem

** Don't make a duplicate issue.
I have just searched but i could not find any related issue.
Describe the bug
As seen in the photo I added and the sample code snippet, when there is no padding/margin on the horizontal axis, the tooltip displays at the beginning and end go outside the screen.
To Reproduce
I added the example app.
Screenshots

Versions

which version of the Flutter are you using?
Flutter 3.13.7 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 2f708eb839 (10 months ago) • 2023-10-09 09:58:08 -0500
Engine • revision a794cf2681
Tools • Dart 3.1.3 • DevTools 2.25.0
which version of the FlChart are you using?
fl_chart: ^0.63.0

Example
import 'package:flutter/material.dart';
import 'package:fl_chart/fl_chart.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      debugShowCheckedModeBanner: false,
      home: Scaffold(
        body: SafeArea(
          child: ConstrainedBox(
            constraints: const BoxConstraints(
              maxHeight: 300,
            ),
            child: LineChart(
              LineChartData(
                lineBarsData: [
                  LineChartBarData(
                    isCurved: true,
                    color: const Color(0xFF191B1E),
                    barWidth: 4,
                    curveSmoothness: .5,
                    isStrokeCapRound: true,
                    spots: [
                      const FlSpot(0, 5),
                      const FlSpot(1, 6),
                      const FlSpot(2, 6),
                      const FlSpot(3, 6),
                      const FlSpot(4, 4),
                      const FlSpot(5, 7),
                      const FlSpot(6, 3),
                      const FlSpot(7, 6),
                      const FlSpot(8, 6),
                      const FlSpot(9, 8),
                      const FlSpot(10, 9),
                    ],
                    dotData: const FlDotData(
                      show: false,
                    ),
                    belowBarData: BarAreaData(
                      show: true,
                      gradient: const LinearGradient(
                        begin: Alignment.topCenter,
                        end: Alignment.bottomCenter,
                        colors: [
                          Color(0x35191B1E),
                          Color(0xFFFFFFFF),
                        ],
                      ),
                    ),
                  ),
                ],
                gridData: const FlGridData(
                  show: false,
                ),
                borderData: FlBorderData(
                  show: false,
                ),
                titlesData: const FlTitlesData(
                  show: false,
                ),
              ),
            ),
          ),
        ),
      ),
    );
  }
}

I have just found fitInsideHorizontally parameter inside touchTooltipData thank you.


array problems

This is a meta issue. Open a separate issue if you have something related. It will be aggregated appropriately.
There are some issues with the Array implementation right now. A community member is working on a rewrite, mostly in Elm, that will resolve the existing issues. The problems all stem from the fact that the implementation is done all in JS by a contributor and things are crazy in there.
Issues involving arrays include:

Array.append on larger arrays - #444, #205
Array.append can mutate first argument? - #691
Array.slice on arrays longer than 32 - #349, #474, #549
No SSCCE - #789

The ultimate fix will be the reimplemeted version.

@Skinney's new implementation has been merged. If there are new things, we should track via new issues.


"Malu Mierii", "Schela" are listed in the drop-down menu

Description:
When user writes ”Malu Mierii” and "Schela" the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Malu Mierii"

Expected results
The location appears in the drop-down menu as "Sat Malu Mierii, DÂMBOVIȚA (Glodeni)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Schela"

Expected results
The location appears in the drop-down menu as "Sat Schela, DÂMBOVIȚA (Glodeni)".


How to remove ic_launcher.png that appears before the animated splash?

React Native newbie here. So far no issues with the library itself. I need some advice on removing the app icon before the animated splash on Android. In the example .gif you can see the app starts straight with the splash.

Also, I would be very grateful if someone could tell me how to make the navigation and status bar white during the splash animation.

@Digital-Human-BK I don't understand and see any logo before the splash screen in your question.
In the case of iOS, Could you look at this issue? https://github.com/HwangTaehyun/react-native-lottie-splash-screen/issues/4#issuecomment-803745045
I've shared below my answer to the same issue about the status bar for you to look at.
https://github.com/HwangTaehyun/react-native-lottie-splash-screen/issues/6.


Create public beta release

If all tasks for version 2.0 are done, we should create a beta release to get some user feedback.

Let's aim to get this out by Monday?

Ok, let's target monday. It should be possible.

We should check our change log then.

We do really need to release 2.0 now 1.1 has been released. I will make sure the matcher changes I want to make are completed as soon as I can, as I really want that in 2.0, because then I can start to add loads of custom ones. As for you, what do you really want to get shipped in version 2 and what can be bumped?

We should fix the open bugs (#148, #142, #111), and we should implement #144, #138, and #41, because these tickets would probably cause breaking API changes after 2.0.

#148 (PR already merged) and #111 (PR open) have been fixed.
#111 comes with Jacoco and code coverage report, but some configuration is still needed. I think that it will be good for the project know the percent of code under test.
I view necessary, as you, implement those issues before 2.0 is released. I hope that I could help in everything I can

#41 I think we can bump, because configuration shouldn't break what we have, just will be an extra method on top.
#138 I will definitely finish in days. And then I need to look at #142 unless @aleixmorgadas wants to help.

Hi,
Which is the current status? I've made some pull request (already merged) to close some issues but they are still open, should I wait until the issues reflects the actual status?

I've voted to close #138. I'm looking at #142 now.

#142 should be good now. I'm happy to release 2.0 once it's merged in. It's been a long time coming and I think we need to get it out there. Even spek is starting to improve now :)

Closing this as we will be releasing 2.0 this weekend.


Updated flutter_bloc example to work with flutter_bloc lib v5

Updated flutter_bloc example to work with flutter_bloc lib v5
Added enhancements to extended_bloc example
Breaking changes

No

Fixes / Enhancements

Updated flutter_bloc example

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


Swap range slider of numerical filter for inverted data mapping

Release number or git hash: v4.1.1
Web browser version and OS: Chrome 86

Steps to reproduce

Open https://lineup.js.org/app_develop/#soccer
Age column -> more menu -> Data Mapping -> Inverted -> apply changes
Filter numerical filter by dragging the maximum border

Observed behavior
Default range and histogram:

With inverted data mapping:

The histogram and range in the column summary is inverted -> correct
The histogram in the side panel is inverted, but the ranges are not -> incorrect

It becomes even stranger when applying a filter:

The filter itself works correctly, all rows with a value > 22.80 are hidden
The histogram in the column summary and side panel are correct
However, it is confusing to drag the maximum range slider and the values are hidden to the left

The same applies to the filter dialog:

Expected behavior
I'd expect that the interactive filter is also inverted with the data mapping. Consequentially, the minimum and maximum range slider and the values below must be swapped. Then the behavior and representation would be correct again.

There always have been an mismatch between the histogram, filter, and bars.
As far as I remember, the filter operates on the data domain, whereas the bars and histogram operate in the normalized domain. In cases such as the inverted mapping this is directly visible as you have noted.
Thus, filtering the top X values in the data domain, will filter out the lowest X in the inverted normalized domain. While we can fix it for this simple inverted case, I don't know a general solution that works with arbitrary mapping methods.


Add context name in default logging

Breaking change

Proposed change

When using standard logging injected we no longer have the app name. This PR adds the context name on all logs using default ND logger.
Type of change

[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (which adds functionality to an existing integration)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Additional information

This PR fixes or closes issue: fixes #
This PR is related to issue:
Link to documentation pull request:

Checklist

[x] The code change is tested and works locally.
[x] Local tests pass. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the [development checklist][dev-checklist]
[x] The code compiles without warnings (code quality chek)
[ ] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated for www.home-assistant.io

Codecov Report

Merging #504 (2fc4ba0) into dev (80f3787) will decrease coverage by 0.07%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##              dev     #504      +/-   ##
==========================================
- Coverage   59.83%   59.76%   -0.08%
==========================================
  Files         139      139
  Lines        5859     5860       +1
  Branches      845      845
==========================================
- Hits         3506     3502       -4
- Misses       2068     2074       +6
+ Partials      285      284       -1

Flag
Coverage Δ

unittests
59.76% <0.00%> (-0.08%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...unner/Infrastructure/Config/SerilogConfigurator.cs
0.00% <0.00%> (ø)

....App/Common/Reactive/ObservableExtensionMethods.cs
52.17% <0.00%> (-13.05%)
:arrow_down:

...pp/NetDaemon.App/Common/Reactive/NetDaemonRxApp.cs
82.55% <0.00%> (-1.71%)
:arrow_down:

...rc/Daemon/NetDaemon.Daemon/Daemon/NetDaemonHost.cs
55.03% <0.00%> (+0.43%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 80f3787...2fc4ba0. Read the comment docs.


!usage

show user usage stats - some grep parsing + formatting of the ~/forever logs
Two syntax forms
!usage
!usage <target>

egrep -E ':\s(.*?)\s+(\![a-z]+\s+.*)' *.log


Handle JWT response data in userinfo endpoint

Closes #83

After this PR I want to go over the code again and update the type annotations to use friendlier syntax since Python 3.10

I've processed a bunch of feedback via #86 so that I can pull apart the changesets into more atomic commits


About  molochcapture

What is the principle of molochcapture implementation? Can the interface be deployed separately?

We use github for bug reports and feature requests, please use slack for questions


Categories

Description
Finished category component without live links.
Issue ticket number and link
N/A
Instructions
Clone project and run npm install, npm start.

Good job


bower install not working

Hi asafdav,
Please create a new release (or tag? not sure what Bower uses) to make the regular bower command work:
bower install ng-flags
At the moment, I am having to run the install with the latest commit hash:
bower install https://github.com/asafdav/ng-flags.git#8790b86bc9
On another note, are you planning to have the css files as part of the package, instead of the external dependency?
Regards,
Abie

Hi, thanks.
I release a new version. let me know if it works.


kdfs/hmacdrbg_kdf.c: Add checks for the EVP_MD_get_size()

Add checks for the EVP_MD_get_size() to avoid integer overflow and then explicitly cast from int to size_t.
Fixes: f3090fc710 ("Implement deterministic ECDSA sign (RFC6979)")

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

This pull request is ready to merge

merged, thank you for your contribution


adding functions to extract headers from context

Externalising functions that might be reused in other repos as well.  from:  (link)

Pull Request Test Coverage Report for Build 136

0 of 15 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-3.5%) to 77.778%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

options.go
0
15
0.0%

Totals

Change from base Build 133:
-3.5%

Covered Lines:
273

Relevant Lines:
351

💛  - Coveralls


Add math tutorials to the main tutorials branch

Adds the tutorials of the math section
List of tutorials:

Basic maths

Preview on how it renders:
Mathematics section main page

 Basic maths

@luisaFelixSalles can we scroll down in the out section here?

If not then some prints are missing

It seems there mismatches between code and output

How come?

@luisaFelixSalles can we scroll down in the out section here?  If not then some prints are missing

Yes we can, I think is just not in the print


🫂 Add Support for Local/P2P

[x] trigger distribution when on p2p host and single-player
[x] update signed box notification text to remain visible on host
[ ] come up with new strategy to revert text on shutdown
[ ] come up with new strategy to revert text when container is being accessed by player

OK so I've decided that with the release of 1.0, I'll be adding support for single-player and p2p in!
The update including this is nearly ready and is currently running without issue on 1.0 (b317) [latest_experimental]


Enable pop-to-click during 'wheel gaze'

I'd like to use pop for clicking while using 'wheel gaze'. Does this change interfere with any other use cases?

#431


UnhandledRejection: Navigation timeout of 30000 ms exceeded

UnhandledRejection: Navigation timeout of 30000 ms exceeded
how to solve this error, for digitalocean server

Hi @denidarmayana , Does this error still happen in the latest version of the server? If yes, how can I reproduce the error?

@denidarmayana
I could not reproduce the error. Try the latest version, if the error occurs, please open a new issue with more information.
WPPConnect Server(s): X.Y.Z
WPPConnect version(s): X.Y.Z
WA-JS version(s): X.Y.Z
WhatsApp version: X.YYYY.ZZ
Browser: Chrome XX / Chromium XX
OS: Windows X / OSX X.Y.Z
Node version: Node XY
MultiDevice (BETA): yes/no
And steps to reproduce the error.
Thanks


ability to hide UI, in landscape mode or otherwise

Playing with the AFrame demos (aframe.io) in mobile Safari, I really like how they switch to full-screen mode when you rotate the phone.  There are menus, decoration, etc., in portrait, but nothing in landscape.
At least in Mobile safari.   In argon, the URL bar is still there.
We should support this properly.  Can someone look into how this works on mobile safari?  It would be nice if we could support this, and enable apps to behave like this.  This also means we could support typical "cardboard" web apps more cleanly (allowing people to create website that support AR and VR).

Complete


AL functionalities not working on project cloned from git

Describe the bug
When al repository is downloaded form git, it is not treated as an al repository:

download symbols is not available
intellisense and code validation/formatting is not working
standard objects defninitions cannot be viewed (Object definition no avaialble)

To Reproduce
Steps and to reproduce the behavior:

Download al repository form git, al download symbols will not be avaialble when opened from vs code
Observe intellisense and code formatting not working
Misc: in my case it is a multi-root workspace.

Expected behavior
After cloning git al repo download symbols command should be avaiable, intellisense working, standard object definitions browsable, as we cannot run al go on a non-empty folder,
5. Versions:

AL Language: 6.1.352568
Business Central: 17

It has always worked fine for me. How are you downloading from Git, and how are you opening in VS Code?

Hello,
like in this example:

bc-XX folders are two seprate git repos
xx-App and xx-Test are separate extensions, 4 of them here
ive downloaded these 2 repos, added them to workspace, save the workspace

Your workspace should open "Common - App", "Common - Test", "Sales Items - App" and "Sales Items - Test" separately, so 4 workspaces not just 2 - which makes 1 app.json + .vscode folder per workspace.

I am closing this issue because it appears that it has been resolved. Please open a new issue if you believe this has not been resolved and reference the current issue.


im.OnDuplicateKeyUpdate does not separate the columns to update with a comma - MySQL

Version: v0.16.0
As the title, for the mysql im.OnDuplicateKeyUpdate, the generated query does not separate the columns to update with a comma. The query is therefore invalid and gives an error:
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near col_3 = ?
as there is no separating column after the col_2 assignment.
Example (assuming col_1 is a key field):
query := mysql.Insert(
    im.Into(mysql.Quote("my_table"), "col_1", "col_2, "col_3"),
    im.Values(mysql.Arg("val 1", "val 2", "val 3")),
    im.OnDuplicateKeyUpdate.SetCol("col_2", mysql.Arg("val 2")).SetCol("col_3", mysql.Arg("val_3")),
)

q, _, _ := query.Build()

fmt.Println(q)

The above results in the following query:
INSERT INTO `my_table` (`col_1`, `col_2`, `col_3`)
VALUES (?, ?, ?)
ON DUPLICATE KEY UPDATE
`col_2` = ?
`col_3` = ?

The expected query would be:
INSERT INTO `my_table` (`col_1`, `col_2`, `col_3`)
VALUES (?, ?, ?)
ON DUPLICATE KEY UPDATE
`col_2` = ?,
`col_3` = ?

The assumption is also that I am using this mod correctly.

Thanks for reporting this. It is now fixed in v0.17.0

Really appreciate the fast response!


librewolf: Fix checkver, update url & hash, added extract_dir, and fixed pre_uninstall/install.

Relates to https://github.com/ScoopInstaller/Extras/actions/runs/4682555879/jobs/8296555601#step:3:468

[x] I have read the Contributing Guide.

/verify


Problem setting up in-app billing: IabResult: 3, No suitable appstore was found (response: 3:Billing Unavailable)

com.badlogic.gdx.utils.GdxRuntimeException: java.lang.RuntimeException: Problem setting up in-app billing: IabResult: 3, No suitable appstore was found (response: 3:Billing Unavailable)
at com.*****$1.handleInstallError(PurchaseManager.java:125)
at com.badlogic.gdx.pay.android.openiab.PurchaseManagerAndroidOpenIAB$1$1.onIabSetupFinished(PurchaseManagerAndroidOpenIAB.java:249)
at org.a.a.f$4$1.onIabSetupFinished(OpenIabHelper.java:853)
at org.a.a.f.a(OpenIabHelper.java:940)
at org.a.a.f.b(OpenIabHelper.java:909)
at org.a.a.f.b(OpenIabHelper.java:84)
at org.a.a.f$4$2.run(OpenIabHelper.java:860)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:7325)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)
Caused by: java.lang.RuntimeException: Problem setting up in-app billing: IabResult: 3, No suitable appstore was found (response: 3:Billing Unavailable)
... 13 more

Hi there, I have implemented Gdx-Pay since 6-7 months till now. in some of my games.
And this one error is bugging me down.
I have followed every integration step and still having this issue.
There have been total 3,026 Reports of crashing when users trying to use the in-app purchase.
in my game https://play.google.com/store/apps/details?id=com.gw.studioz.racing.mountain.climb
    gdxPayVersion = '0.9.2'
    openIabVersion = '<IP_ADDRESS>'

in android it's

    compile "org.onepf:openiab:${openIabVersion}"
    compile "com.badlogicgames.gdxpay:gdx-pay-android:$gdxPayVersion"
    compile "com.badlogicgames.gdxpay:gdx-pay-android-openiab:$gdxPayVersion"
    compile "com.badlogicgames.gdxpay:gdx-pay-android-ouya:$gdxPayVersion"
    compile "com.badlogicgames.gdxpay:gdx-pay-android-amazon:$gdxPayVersion"

in core

compile "com.badlogicgames.gdxpay:gdx-pay:$gdxPayVersion"
compile "com.badlogicgames.gdxpay:gdx-pay-client:$gdxPayVersion"

manifest has

<!--Google Play-->
<uses-permission android:name="com.android.vending.BILLING" />
<!--Open Store-->
<uses-permission android:name="org.onepf.openiab.permission.BILLING" />
<!--Samsung Apps-->
<uses-permission android:name="com.sec.android.iap.permission.BILLING" />
<!--Nokia-->
<uses-permission android:name="com.nokia.payment.BILLING" />
<!--SlideME-->
<uses-permission android:name="com.slideme.sam.manager.inapp.permission.BILLING" />

It's running fine on my side, plus IAP is also working as I can see purchases in dashboard too.
But there are major crashes for some devices.
Can anyone please help me fixing this issue.  Am I missing something?
Note:
The integration wiki of gdx-pay has not been updated since long time.
The integration steps are shown by downloading and copying the jars not the gradle way.
If possible please update the wiki according to gradle integration so that no steps can be left out.
Thanks.

The openiab implementation is deprecated. Try gdx-pay-android-googleplay

hey, I know that it's been written in the updates but, there is no such instructions on how to or what components must be removed from or add to the gradle files.
to what you suggest, I already tried gdx-pay-android-googleplay
but the android project did close just after openning asking to add openiab lib.

To use android-googleplay, include the following dependencies:
dependencies {
    compile "com.badlogicgames.gdxpay:gdx-pay-client:${gdxPayVersion}"
    compile "com.badlogicgames.gdxpay:gdx-pay-android:${gdxPayVersion}"
    compile "com.badlogicgames.gdxpay:gdx-pay-android-googleplay:${gdxPayVersion}"
}

Do not include openiab in the same gradle subproject.
That should do everything.
Does this help?

Seems to be OpenIab related, user did not yet react.
If problems persist with gdx-pay-android-googleplay please file a new issue

Hi Kees,
I used the configuration you suggested.
dependencies {
compile "com.badlogicgames.gdxpay:gdx-pay-client:${gdxPayVersion}"
compile "com.badlogicgames.gdxpay:gdx-pay-android:${gdxPayVersion}"
compile "com.badlogicgames.gdxpay:gdx-pay-android-googleplay:${gdxPayVersion}"
}
But getting this error.
Error:Module 'com.badlogicgames.gdxpay:gdx-pay-android-googleplay:0.10.3' depends on one or more Android Libraries but is a jar.
Kindly help.

Hi Kees,
I used the configuration you suggested.
dependencies {
compile "com.badlogicgames.gdxpay:gdx-pay-client:${gdxPayVersion}"
compile "com.badlogicgames.gdxpay:gdx-pay-android:${gdxPayVersion}"
compile "com.badlogicgames.gdxpay:gdx-pay-android-googleplay:${gdxPayVersion}"
}
But getting this error.
Error:Module 'com.badlogicgames.gdxpay:gdx-pay-android-googleplay:0.10.3'
depends on one or more Android Libraries but is a jar.
Kindly help.
On Thu, Sep 1, 2016 at 11:58 PM, Kees van Dieren<EMAIL_ADDRESS>wrote:

Closed #112 https://github.com/libgdx/gdx-pay/issues/112.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/libgdx/gdx-pay/issues/112#event-775573893, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABp-7cQCC3dM1k7RjzA2OxGOZPKi1Ew4ks5qlxlDgaJpZM4JVE1_
.

--
Thanks and Regards
Abhishek Rai

See #108 for the solution


WebGL build with Unity plugin?

Hi,
I'm an engineer and trying to use MuJoCo with Unity for education.
My Windows builds works good, but is there any way to build WebGL project with Unity and Mujoco?
Thank you guys!

Not sure about Unity to WebGL specifically, but there's a good example of MuJoCo running rather well in a web browser.


When the pool has never had a scrub, date error occurs

When the pool has never had a scrub, we get this type of output:
check_zpool_scrub --pool=system --warning=777600 --critical=1209600
[: =: unexpected operator
usage: date [-jnRu] [-d dst] [-r seconds] [-t west] [-v[+|-]val[ymwdHMS]] ...
            [-f fmt date | [[[[[cc]yy]mm]dd]HH]MM[.ss]] [+format]
CRITICAL: The last scrub on zpool 'system' was performed on  | last_ago=1533918385 warning=777600 critical=1209600 progress=100 speed=0 time=0

[dan@tallboy:~] $ zpool status
  pool: system
 state: ONLINE
  scan: none requested
config:

	NAME           STATE     READ WRITE CKSUM
	system         ONLINE       0     0     0
	  mirror-0     ONLINE       0     0     0
	    gpt/disk0  ONLINE       0     0     0
	    ada1p3     ONLINE       0     0     0

errors: No known data errors
[dan@tallboy:~] $

Nice
$ ./check_zpool_scrub --pool=system --warning=777600 --critical=1209600
UNKNOWN: The pool has never had a scrub.

After I start the scrub on this pool which has never been scrubbed:
OK: The last scrub on zpool 'system' was performed on 2018-08-17.01:45:46

FYI , this system has been around since at least: Tue Feb 17 23:44 2015
.....

Once the scrub completed, the message changed to:
OK: The last scrub on zpool 'system' was performed on 2018-08-17.02:57:36

I keep thinking: should/could the plugin inform us when a scrub is in progress?

The plugin supports performance data:  | last_ago=1533918385 warning=777600 critical=1209600 progress=100 speed=0 time=0.
Did you think about something like that: in_progress=true or in_progress=1


What is the best practice to have a publisher within State?

When considering a large scale application, for example, we need to watch a remote config(Restful Json) change and popovers a modal view if isMaintainanceMode = true.
My question is: where is the best place to put a watch logic (via URLSession.shared.dataTaskPublisher within AppState?

struct Config {
  var isMaintainanceMode: Bool = false
}

struct AppState {
    var config: Config
}

You can put the login into reducer that returns side-effect using a Publisher.

How about this way?
extension AppState {
    struct System: Codable {
        var checker = SystemChecker()
    }
}

extension AppState.System {
    class SystemChecker: Codable {

                // Input
                @Published var config = MConfig()
                @Published var alerts: [MSystemAlert] = []

                // Output
                @Published var shouldShowSystemAlert = false

                var shouldShowSystemAlertPublisher: AnyPublisher<MSystemAlert?, Never> {
                    self.$alerts
                    .removeDuplicates()
                        .map { (alerts) -> MSystemAlert? in
                            //TODO, need to find out the timg for system maintainance, currently, we simply show it if alert exists
                            if alerts.count == 0 {
                                return nil
                            } else {
                                return alerts.first
                            }
                    }.eraseToAnyPublisher()
                }
}

And we call it in view
.onReceive(store.appState.system.checker.shouldShowSystemAlertPublisher) { alert in
            if alert != nil {
                self.systemAlertNotification = alert
                self.showSystemAlertNotification = true
            }
        }

It should work but in my understanding of the unidirectional flow, everything should go through the reducer.


Export Image doesn't work on private maps for org users in the editor

Steps to Reproduce

Being an org user and in the builder open a map.
Make the map private if it isn't already.
Click on Export Image
Export any selection of the map

Current Result
The map instantiation fails, so does the export
Expected result
The image exports

S/B 14966014 should be notified if this is fixed please.

@ztephm , could you notify S/B 14966014? I don't have support bee access anymore. Thanks!

done, thanks for fixing!


Update version from 0.0.103 to 0.0.104

This is an automated update of version in pyproject.toml. This action is performed by a Github Action from publish.yml.

updated version from 0.0.103 to 0.0.104, @SuleyNL pls review


more results on semantic segmentation

Could you release the results of BEiT-B+UperNet on cocostuff-10k and pascal context?

Hi, we haven't trained these models yet. We'll make it up later if we have time.


Handle cases when multiple DITs are used in a sequence

Currently the code does not work properly when different DITs are used in an OBJECT sequence.

Current implementation works from latest commit (ef70076baf5588692e616e68a0756d8da67d461a) works


Add testnet warning

This is a temporary warning that we're applying prior to federation while the testnet runs. Applies when visiting any instance that's not on main.

Web
Mobile

Added crazy watermarks on each post


[BUG] Example not working under wayland ("Failed to get x11 window for gtk window").)

Checklist before submitting an issue

[X] I have searched through the existing closed and open issues for eww and made sure this is not a duplicate
[X] I have specifically verified that this bug is not a common user error
[X] I am providing as much relevant information as I am able to in this bug report (Minimal config to reproduce the issue for example, if applicable)

Description of the bug
I used the example given in the docs, with nothing added. I tried removing each module, but there was no difference. Tried both with the wayland version present on the AUR and by manually building with the correct flags. In both cases there were no build errors. Follows the full error message:
failed to open window 'example'

Caused by:
        Failed to get x11 window for gtk window

The only steps I tried to troubleshoot have been reinstalling, making sure the flags were correct, and tinkering with the config (for example taking someone else's wayland config). Got the same error message:
failed to open window 'bar'

Cause by:
        Failed to get x11 window for gtk window

Any help would be appreciated :)
Reproducing the issue
Simply followed the installation steps
Expected behaviour
widgets/windows should launch
Additional context

Did you make sure to compile with the correct flags? If you are on Arch then https://aur.archlinux.org/packages/eww-wayland-git this might be your  best bet. On NixOS I had to install the eww-wayland package to stop getting this error.

That's the package I have currently installed (I run arch, btw). No luck :/

On Wayland, you'll need to explicitly specify the monitor the window should be on, see the docs for how to do so.

The only place where that error message may occur is in code that is only compiled when you're using X11 -- that error message can't happen when you're compiling eww for wayland

I changed nothing from when I reported this, and now it... magically works? Not sure what happened

I have the same issue, on eww-wayland, with the example bar.

Am I doing something wrong?
Apologies if I'm wasting time, but I have been at this for a few hours now, and am completely new to eww.

Welp, started working after doing nothing as well. Very weird.
Thanks!

If you initially built eww for x11, started the daemon (through eww open for example), then built the wayland version, calling eww will still communicate to the original eww daemon (the x11 one) unless it is shutdown or the config path is changed (starts another daemon). So this could be the reason

I have the very same issue. Tried to kill the daemon and start it back up again, tried to change the display to 0,1,2 and every monitor name of my 3 monitors. Also tried to reboot. Nothing worked. Any idea what's up?

I had a similar issue (eww was starting in XWayland) and it turns out that I was running eww open in a terminal inside VSCode (which runs on XWayland). Opening a terminal outside VScode and running eww open there made it work.


Use Bukkit's isPrimaryThread check to set event sync status

Replaced the hardcoded true for asynchronous event handling with a dynamic !Bukkit.isPrimaryThread() check across all event constructors. This ensures events can be called synchronous or asynchronous based on the server thread context.

I only changed that behavior for async events but in theory the sync only events wouldn't cause issues when called from an async context
This change allows users for example to hide holograms from a sync context (which is basically always the case when working with bukkit events)

Originally when implementing the events I think we did use !Bukkit.isPrimaryThread() but opted to enforce async context to ensure it's only possible to fire off the main thread.

I think you can't expect users to call methods async just because the implementation of the API calls an event.
Either make it possible to call them from anywhere or declare it in the javadocs for each method that it can't be called from within a sync context


create new entry in app.component.ts for the Logbook component

Work is complete and correct, code has been merged.


HTTP::Request docs

Thank you @straight-shoota for the comments.  I have updated the PR let me know if you get another chance to look at this.

@straight-shoota thanks for the review.  I have removed all the puts statements.


cargo test fails on a vanilla project

Cargo test fails on a vanilla/freahly init repo.
ie:
anchor init hello_anchor && cd hello_anchor && cargo test
output:
  Doc-tests hello_anchor
error[E0659]: `hello_anchor` is ambiguous (name vs any other name during import resolution)
  --> /home/utx0/Code/poc/hello_anchor/programs/hello_anchor/src/lib.rs:6:9
   |
6  | pub mod hello_anchor {
   |         ^^^^^^^^^^^^ ambiguous name
   |
   = note: `hello_anchor` could refer to a crate passed with `--extern`
   = help: use `::hello_anchor` to refer to this crate unambiguously
note: `hello_anchor` could also refer to the module defined here
  --> /home/utx0/Code/poc/hello_anchor/programs/hello_anchor/src/lib.rs:6:1
   |
6  | / pub mod hello_anchor {
7  | |     use super::*;
8  | |     pub fn initialize(ctx: Context<Initialize>) -> ProgramResult {
9  | |         Ok(())
10 | |     }
11 | | }
   | |_^
   = help: use `crate::hello_anchor` to refer to this module unambiguously

error: aborting due to previous error

For more information about this error, try `rustc --explain E0659`.
error: test failed, to rerun pass '--doc'

This is not ideal as you dont have access to doc test and possible other functions of standard cargo

Related https://github.com/project-serum/anchor/issues/109

cargo test --lib is one workaround


Issues about building MICM on Casper

I am trying to build MICM on Casper but encounter some issues. I need to manually revise the CMakeLists.txt file to resolve them:

The NETCDF_HOME env variable is not defined on Casper and thus the NETCDF module can not be found even if I have loaded it in my environment. The NETCDF env variable is defined on Casper and seems to work the same as NETCDF_HOME. Can we add it to the search path?
https://github.com/NCAR/micm/blob/9fdec9c39f70e094fa3225366118cca50a9dcfee/CMakeLists.txt#L16

The lib suffix in the search path should be changed to include. I am not sure why the container version still works since we are searching for header files here.
https://github.com/NCAR/micm/blob/9fdec9c39f70e094fa3225366118cca50a9dcfee/CMakeLists.txt#L44

Hi @sjsprecious
These are just the standard search paths. If they're not found here, you don't need to modify the CMakeLists.txt file, you can just set the paths in the call to cmake:
cmake -D NETCDF_INCLUDE_DIR=/path/to/netcdf/include \
      -D NETCDF_C_LIB=/path/to/libnetcdf \
      -D NETCDF_FORTRAN_LIB=/path/to/libnetcdff \
      -D JSON_INCLUDE_DIR=/path/to/jsonfortran/mod/files \
      -D JSON_LIB=/path/to/libjsonfortran \
      ..

Or you can set them in the CMake gui with:
ccmake ..

Or you can set the environment variables MICM looks for:
export NETCDF_HOME=/path/to/netcdf/home
export JSON_FORTRAN_HOME=/path/to/jsonfortran/home

By default, json-fortran includes the .mod files with the library in /usr/local/jsonfortran-compiler-version/lib on install. For example, in the container:
[root@668ce9b49fbb /]# ls /usr/local/jsonfortran-gnu-8.2.0/lib/
json_file_module.mod  json_parameters.mod        libjsonfortran.a       libjsonfortran.so.8.2.0
json_kinds.mod        json_string_utilities.mod  libjsonfortran.so      pkgconfig
json_module.mod       json_value_module.mod      libjsonfortran.so.8.2


Handle execute errors

1 of 2 PR to fix this https://github.com/apollostack/apollo-client/issues/1132

Thanks, I didn't realize execute could throw (I thought it would reject but can see from the docs that isn't the case)


Add documentation comments.

rdar://problem/40951342
Adds documentation comments to dispatch queue-related methods.

@swift-ci please test

@swift-ci please nominate
Explanation: adds documentation to dispatch queue-related methods
Scope: Swift libdispatch overlay
Radar: rdar://problem/40951342
Risk: low
Testing: None - documentation-only change.
There is also a corresponding change to swift-corelibs-libdispatch - see https://github.com/apple/swift-corelibs-libdispatch/pull/388

@swift-ci please nominate
Explanation: adds documentation to dispatch queue-related methods
Scope: Swift libdispatch overlay
Radar: rdar://problem/40951342
Risk: low
Testing: None - documentation-only change.


Resnet Minor Polished

Job d2l-zh/PR-612/2 is complete.
Check the results at http://preview.d2l.ai/d2l-zh/PR-612/

Job d2l-zh/PR-612/2 is complete.
Check the results at http://preview.d2l.ai/d2l-zh/PR-612/

Job d2l-zh/PR-612/1 is complete.
Check the results at http://preview.d2l.ai/d2l-zh/PR-612/

Job d2l-zh/PR-612/1 is complete.
Check the results at http://preview.d2l.ai/d2l-zh/PR-612/

Job d2l-zh/PR-612/3 is complete.
Check the results at http://preview.d2l.ai/d2l-zh/PR-612/

Job d2l-zh/PR-612/3 is complete.
Check the results at http://preview.d2l.ai/d2l-zh/PR-612/

Job d2l-zh/PR-612/4 is complete.
Check the results at http://preview.d2l.ai/d2l-zh/PR-612/

Job d2l-zh/PR-612/4 is complete.
Check the results at http://preview.d2l.ai/d2l-zh/PR-612/