DO NOT MERGE:  extendr for polars 0.7.0rc (CRAN)

this PR tracks changes of a branch from pr473_553_555_566 which also rolls back libRsys 5.0 -> 4.0

so sorry wrong fork :/


pkg/report: make uvm_fault parsing more strict on OpenBSD

In order to avoid treating the following diagnostic printf as a panic[1]:
vmx_mprotect_ept: uvm_fault returns 14, GPA=0x200000

[1] https://syzkaller.appspot.com/bug?id=25f3ef919bf9f5d8a89e13b1ba5fec8ca56334be

test?

test?

Can you express a negative test where the output is not recognized as a panic?

test?

Can one express a negative test where the output is not recognized as a panic?

Yes, it's these files:
syzkaller$ grep -L "TITLE:" pkg/report/testdata/linux/report/*

Codecov Report

Merging #1673 into master will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1673   +/-   ##
=======================================
  Coverage   56.34%   56.34%
=======================================
  Files         147      147
  Lines       27513    27513
=======================================
  Hits        15502    15502
  Misses      11215    11215
  Partials      796      796

Impacted Files
Coverage Δ

pkg/report/openbsd.go
84.41% <ø> (ø)

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 a8c6a3f...f016f57. Read the comment docs.


[usage issue] any qq wechat group ?

usage issue
is there have any qq wechat group ?

Not yet, if there are any questions or solutions, please make a issue or pr.😁


[On Hold] Mistral GS Demo Benchmarking

GS e2e Demo
test uses batched real inputs and produces batched outputs
this test is looped (takes several batches of inputs, produces several batches of outputs)
test evaluates results of TT model against validation data in selected data set
test is documented
how to run test (commands to execute)
what does the model do (high-level explanation in a couple of sentences)
description of what is input and what is output
this demo should load inputs and expected outputs from a data set on Weka (TBD which one)

This PR is on hold until issue with Cache (https://github.com/tenstorrent-metal/tt-metal/issues/4344) is resolved.

With the new implementation of mistral this is no longer needed.


Add Node v18 to CI

This PR adds Node v18 to the CI configuration. actions/setup-node has also been updated to the latest version.
Fixes https://github.com/microsoft/TypeScript/issues/48825

IIRC we may have agreed that we want to test latest plus the last two LTS releases before that, so we would be replacing 17 here, not adding to it.

Yep 18 should just replace 17 as current active development version.

PR has been updated. The Azure pipeline needs to be updated -- it appears that this lives in a different repo?


Weird scores amplitude weightening after MCA rotation

The scores' amplitude changes after adjusting of n_modes and achieves unexpected values. Seems to originate from a wrong "dim" argument within the mca rotator class (dot product between scores and rotation matrix, dim = mode instead of dim = mode1)

Good catch @mschulzie will have a look into it!

transform of MCA class is affected by the sae bug; can be fixed the same way though


Priority queue with callbacks

Description
Changes proposed in this pull request:

queue with callbacks in order to use these for metrics gathering,
queue element wrapped with data tracking time spend in the queue

Related issue(s)

do not log as error, when there is no item

do not log as INFO, it is at most DEBUG


Update logo urls

Coverage remained the same at 66.887% when pulling 18dacee64bf4dc0068ed0fb274f02e03e8bb2acd on alanbernstein:image-url-fix into a7fcace1e94ec41141435f00c12ec0671242367e on pilosa:master.


Documentation for Use Cases

Create documentation that is complimentary to any existing Doxygen documentation for each supported use case.  Complimentary documentation should not be as technically detailed as the Doxygen documentation but should provide a scientist/user a good understanding of the use case.  In addition, prepare a description/definition of use case.
The documentation should either reside in it's own document, or be included in the METplus User's documentation- the location needs to be determined by the team.

Refer to Github Issue #254 (README template)

I believe this work is done when we created the 3.0 release with Sphinx Gallery documentation for each use case.


Update

More upstream updates, I guess implementing AI is on the roadmap now

gunna need testing for compatibility before it gets pushed

oh look here come the errors now


[camerax] Implement focus mode configuration

In the camera plugin API, there are two methods related to the configuration of the focus mode. These should be implemented in the CameraX plugin:

[ ] setFocusMode(....)
[ ] setFocusPoint(..)

Hello, is there an update on this issue? My company is unable to use this plugin until the issue is resolved.

Hello, is there an update on this issue? My company is unable to use this plugin until the issue is resolved.

I have just begun working on this feature; will update here when a PR is submitted for review.

Looking into how we may be able to replicate auto/locked Flutter-defined focus modes and a helpful discussion that I likely will need to implement this: https://groups.google.com/a/android.com/g/camerax-developers/c/VRsER_nHeHM?pli=1.

Working on implementing setFocusMode and it's not clear to me how to implement locked versus auto mode, so I want to write out my thoughts as of now so I can correct my assumptions as needed with this as a baseline.
Locked mode:
To implement locked mode in camera_android, we did something like
// When locking the auto-focus the camera device should do a one-time focus and afterwards
// set the auto-focus to idle. This is accomplished by setting the CONTROL_AF_MODE to
// CONTROL_AF_MODE_AUTO.
captureRequestBuilder.set(CaptureRequest.CONTROL_AF_MODE, CaptureRequest.CONTROL_AF_MODE_AUTO);
captureRequestBuilder.set(
  CaptureRequest.CONTROL_AF_TRIGGER, CaptureRequest.CONTROL_AF_TRIGGER_START);
captureSession.capture(captureRequestBuilder.build(), null, backgroundHandler);
captureRequestBuilder.set(
  CaptureRequest.CONTROL_AF_TRIGGER, CameraMetadata.CONTROL_AF_TRIGGER_IDLE);
captureSession.setRepeatingRequest(
  captureRequestBuilder.build(), null, backgroundHandler);

It's my understanding that this is what is going on under the hood in CameraX when we set an AF MeteringPoint via startFocusAndMetering.
Auto mode:
To implement auto mode in camera_android, we did something like
captureRequestBuilder.set(
    CaptureRequest.CONTROL_AF_MODE,
    recordingVideo
        ? CaptureRequest.CONTROL_AF_MODE_CONTINUOUS_VIDEO
        : CaptureRequest.CONTROL_AF_MODE_CONTINUOUS_PICTURE);
// Cancel existing AF state.
captureRequestBuilder.set(
    CaptureRequest.CONTROL_AF_TRIGGER, CameraMetadata.CONTROL_AF_TRIGGER_CANCEL);
captureSession.capture(captureRequestBuilder.build(), null, backgroundHandler);
// Set AF state to idle again.
captureRequestBuilder.set(
    CaptureRequest.CONTROL_AF_TRIGGER, CameraMetadata.CONTROL_AF_TRIGGER_IDLE);
captureSession.capture(captureRequestBuilder.build(), null, backgroundHandler);

To implement this with CameraX, I believe we will need to remove any AF MeteringPoints from any running FocusMeteringActions set via startFocusandMetering or, if we have only set AF MeteringPoints, cancel focus and metering altogether. This is because the continuous auto focus mode is CameraX's default mode.

It turns out that CameraX always uses auto focus mode, preferring CaptureRequest.CONTROL_AF_MODE for CaptureRequest. CONTROL_AF_MODE_AUTO, but may fallback to CONTROL_AF_MODE_CONTINUOUS_VIDEO/CONTROL_AF_MODE_CONTINUOUS_PICTURE based on the source code, and never sets CaptureRequest.CONTROL_AF_TRIGGER to CameraMetadata.CONTROL_AF_TRIGGER_IDLE.
To work around this, I'm going to (1) try implementing locked focus mode with Camera2 interop, and depending on the results of that and digging deeper into the philosophy of CameraX only using autofocus mode, (2) consider the pros/cons of not implementing locked focus mode.

I just tried using Camera2CameraControl to manually lock the focus mode, with two attempts:
Attempt 1 (fail):
I added the capture request options CameraMetadata.CONTROL_AF_TRIGGER_IDLE  for CaptureRequest.CONTROL_AF_TRIGGER with Camera2CameraControl.addCaptureRequestOptions, and I still saw autofocus.
Attempt 2 (success?):
I set the capture request options CaptureRequest.CONTROL_AF_MODE_AUTO for CaptureRequest.CONTROL_AF_MODE and CameraMetadata.CONTROL_AF_TRIGGER_IDLE for CaptureRequest.CONTROL_AF_TRIGGER with Camera2CameraControl.setCaptureRequestOptions, and it actually seemed to work, though I wonder how this may conflict with the default behavior.


Does not run before Yarn runs binaries

This plugin is great and works when Yarn invokes a script, but when Yarn invokes a binary provided by a package (e.g. yarn nx …) it doesn't run. To work around this I've made a script named the same as the binary e.g.
"scripts": {
  "nx": "nx"
}

However it would be great if this plugin could hook into binary execution too and run yarn install.

@exKAZUu amazing thank you! I'm having some trouble installing it though https://github.com/WillBooster/yarn-plugin-auto-install/issues/186#issuecomment-1881933777


adjust checks for core to better match c++ checks

The core checks were not setting the same image / tile size limits and not disabling reads at quite the same level.
Note: the core check does not read the entire image into a contiguous slice, so does not replicate the maximum deep sample checks in the same way, this is a source of potential false-negative failures
This should address OSS-Fuzz 66491 and 66489 (different forms of the same failure where a large sample size allocation was happening), and are only constrained memory (2.5Gb) issues.

belated comment to say that looks good to me too. I guess the core library is less memory hungry, so it could potentially load a larger image without going over any particular memory boundary.
I am under the impression that oss-fuzz doesn't (always) pass the same input to both the core check and the c++ check, since they are now separate tests it runs. So we may only see a report for one of the two failing due to oss-fuzz's memory limits, even though both would fail with that input.


Prioritise quoted phrases in search snippets.

Changes in this PR:
This goes with a marklogic PR which ensures that snippets containing quoted phrases in the query are given priority when they're displayed to users.
This PR provides the list of quoted phrases to marklogic (essentially impossible to do with marklogic's own regex engine), and also limits the number of matched phrases returned to 4 (the current default), as the number returned by marklogic itself has necessarily increased (we need to generate a larger amount of matches before prioritisation to ensure we catch any mentions of the quoted phrase).
Trello card / Rollbar error (etc)
https://trello.com/c/IQK3v7c5/1560-search-matching-text-should-reflect-search-query-in-quotations-over-other-words-in-search-results

 SEARCH: matching text should reflect search query in quotations over other words in search results


Interface extended to de-/prioritize value propagation and setting delay of frame cycle

For sending about 20 telemetry values it is not sufficient to send/handle all values in the same manner, if the physical interface speed is limited (9600Baud).
It is very helpful if some values (variometer) are send more often than others (e.g.: number of satellites). This is provided by a changed set value methods, with additional prio parameters.
Furthermore the new SetJetiSendCycle()-method, allows setting a less delay time than the current hardcoded 150ms, to reduce value transmission delay to a minimum.
Tests with the VarioGPS-Sensor code was very promising.
Regards
Rainer

Tests with more than 15 telemetry values (id > 15) forced problems. At the end a exBuf overflow forced the problems. Main problem was, that the buffer need one extra byte for id > 15 and the decision to handle one more value, was done on the wrong data, the bufLen of the current sensor and not of the next one.
So the preparation of the exBuf is reworked and works now without problems for all id.
Nevertheless there were problems sending some value of my variometer (rel. heigth in dcm). Analysis show, that on the workbench height of -1 dcm are send very often, but are ignored by the JetiExSensor.
I see no need for this behaviour, due to (now) exiting prio and disabling methods and the INVALID value -1 is now removed.
Regards Rainer


an update

Pull Request Test Coverage Report for Build 1321

0 of 41 (0.0%)  changed or added relevant lines in 3 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.05%) to 6.45%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/components/incubator/editingWorkspaceSideContent/DeploymentTab.tsx
0
9
0.0%

src/components/incubator/editingWorkspaceSideContent/ManageQuestionTab.tsx
0
14
0.0%

src/components/incubator/editingWorkspaceSideContent/QuestionTemplateTab.tsx
0
18
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/components/incubator/editingWorkspaceSideContent/QuestionTemplateTab.tsx
1
0.0%

src/components/incubator/editingWorkspaceSideContent/ManageQuestionTab.tsx
1
0.0%

Totals

Change from base Build 1320:
-0.05%

Covered Lines:
280

Relevant Lines:
3688

💛  - Coveralls


[all] Add overloads with primitive types to reduce overhead for bindings

Disclaimer: this is a mess.
What's wrong with raylib and their bindings
raylib currently provides several functions that accept or return custom structs, which can introduce marshalling costs for binding authors when working with languages outside of C. In fact, some bindings (at least for C#) provide low level access to raylib's function in order to not impact too much the performance.
Also, this will also constraint binding authors to follow raylib's structs. If we want to add additional properties to a struct we should create wrapper classes which will introduce additional overhead.
A possible solution
Ideally, to reduce this overhead and provide better performance and flexibility, raylib should provide overloads that use only primitive types as parameters or return values instead of raylib's own structs. For example if a function returns a struct, we should accept the struct's primitive data as pointers to avoid marshalling overhead, similarly, if a function accepts a struct we should pass that struct's individual primitive types.
Benefits:

Performance Improvement: By using primitive types, marshalling costs are eliminated, resulting in faster cross-language interactions.
Flexibility for Bindings Authors: This approach allows bindings authors to wrap the primitive values into their own classes or structs, potentially adding additional functionality or fitting them into language-specific paradigms.
Maintainability: This would allow bindings to stay lightweight and modular without forcing the usage of raylib's predefined struct layouts.

Example:
Instead of:
void DrawRectangleRec(Rectangle rec, Color color);

Provide an overload:
void DrawRectangleRecRaw(float x, float y, float width, float height, int r, int g, int b, int a);

This approach is more flexible and allows developers to handle their own struct definitions, reducing the dependency on raylib's specific structs while maintaining full compatibility with raylib's API.
Let me know your thoughts or concerns regarding this proposal.

@Odex64 I'm afraid it would imply adding many many function alternatives. Incrementing the maintenance cost and the overall complexity. I prefer to avoid that.


Beautified the code

Description

Types of changes

[x] Bug fix or improving code quality
[ ] New language
[ ] New feature

Checklist:

[ ] My code follows the code style of this project.
[ ] I have updated the documentation accordingly.

Explored the code and tried making it more readable


How to open ssl?

Hi,
I want to use Nginx to reverse proxy your ImageServer. I have to use https because my port 80 is banded. I have set the ssl property with my key and pem files in config/option.js as the offical docuemnt does, and I got error "502 Bad Gateway" when I request / url. How to open ssl correctly?

Sorry, I have solved this by change my nginx config file. I will close this issus now. Thanks.


Compiler warnings in generated POJOs

The server model POJO generation triggers javac compiler warnings when -Xlint:all is passed to the compiler.
build/generated/sources/graphqlGradlePlugin/com/example/graphql/viewmodel/Account.java:519: warning: [cast] redundant cast to Long
                        this.pendingReward = (java.lang.Long) pendingReward;

The generated Java code seems to have a lot of unnecessary checks that can be removed since the setter already defines the exact type:
@Override
public void setPendingReward(java.lang.Long pendingReward) {
    if (pendingReward == null || pendingReward instanceof java.lang.Long) {
        this.pendingReward = (java.lang.Long) pendingReward;
    } else {
        throw new IllegalArgumentException("The given pendingReward should be an instance of java.lang.Long, but is an instance of " + pendingReward.getClass().getName());
    }
}

I think the following would be equivalent:
@Override
public void setPendingReward(java.lang.Long pendingReward) {
    this.pendingReward = pendingReward;
}

That is right. And strange.
I'll dig in my history to find why this code is generated. The sample you provided is quite clear. But there my be other cases where it's useful. And if so, this code should only be generated in theses cases...

Ok,
I've checked that.
This control is useless in the case you've shown, of course.
But GraphQL allows things that are difficult to adapt in Java.
Here is a sample:
´´´
interface IP {
attr : String!
}
type TP implements IP {
attr : String!
}
interface I2 {
a: IP
}
type T2 implements I2 {
a: TP
}
´´´
T2 must implement both ´setA(IP)´ and ´setA(TP)´.
So you may call ´setA´ with a class of your own, that implement IP but is not an instance of TP.
But I was perhaps too careful.
I'll check if I can ease a little this control.
Étienne


Added ComprobanteRegimenFiscal Validator with tests

In this case you are asserting only one case. Could you please not use registerAsserts method to simplify?

Ok, there is no use of registerAsserts method now, since I am asserting only one case.

Thanks a lot!


location in included nginx proxy not working in 1.5.1

Summary
I just migrated from 1.2.2 to 1.5.1 (alpine) and we were using KONG_NGINX_PROXY_INCLUDE to inject a block like below and some more directives:
...

location /readiness {
  content_by_lua_block {
    ngx.say("OK")
  }
}

Steps To Reproduce

Create a file with the content above
Spin up kong 1.5.1 with KONG_NGINX_PROXY_INCLUDE set pointing to the file in step 1

Additional Details & Logs

Kong version (1.5.1)
Kong debug-level startup logs ($ kong start --vv)

kong           | 2020/05/15 13:57:31 [verbose] Kong: 1.5.1
kong           | 2020/05/15 13:57:31 [debug] ngx_lua: 10015
kong           | 2020/05/15 13:57:31 [debug] nginx: 1015008
kong           | 2020/05/15 13:57:31 [debug] Lua: LuaJIT 2.1.0-beta3
kong           | 2020/05/15 13:57:31 [verbose] no config file found at /etc/kong/kong.conf
kong           | 2020/05/15 13:57:31 [verbose] no config file found at /etc/kong.conf
kong           | 2020/05/15 13:57:31 [verbose] no config file, skip loading
kong           | 2020/05/15 13:57:31 [debug] reading environment variables
kong           | 2020/05/15 13:57:31 [debug] KONG_DATABASE ENV found with "off"
kong           | 2020/05/15 13:57:31 [debug] KONG_NGINX_PROXY_INCLUDE ENV found with "/nginx/proxy-include.conf"
kong           | 2020/05/15 13:57:31 [debug] KONG_NGINX_DAEMON ENV found with "off"
kong           | 2020/05/15 13:57:31 [debug] admin_access_log = "logs/admin_access.log"
kong           | 2020/05/15 13:57:31 [debug] admin_error_log = "logs/error.log"
kong           | 2020/05/15 13:57:31 [debug] admin_listen = {"<IP_ADDRESS>:8001","<IP_ADDRESS>:8444 http2 ssl"}
kong           | 2020/05/15 13:57:31 [debug] anonymous_reports = true
kong           | 2020/05/15 13:57:31 [debug] cassandra_consistency = "ONE"
kong           | 2020/05/15 13:57:31 [debug] cassandra_contact_points = {"<IP_ADDRESS>"}
kong           | 2020/05/15 13:57:31 [debug] cassandra_data_centers = {"dc1:2","dc2:3"}
kong           | 2020/05/15 13:57:31 [debug] cassandra_keyspace = "kong"
kong           | 2020/05/15 13:57:31 [debug] cassandra_lb_policy = "RequestRoundRobin"
kong           | 2020/05/15 13:57:31 [debug] cassandra_port = 9042
kong           | 2020/05/15 13:57:31 [debug] cassandra_refresh_frequency = 60
kong           | 2020/05/15 13:57:31 [debug] cassandra_repl_factor = 1
kong           | 2020/05/15 13:57:31 [debug] cassandra_repl_strategy = "SimpleStrategy"
kong           | 2020/05/15 13:57:31 [debug] cassandra_schema_consensus_timeout = 10000
kong           | 2020/05/15 13:57:31 [debug] cassandra_ssl = false
kong           | 2020/05/15 13:57:31 [debug] cassandra_ssl_verify = false
kong           | 2020/05/15 13:57:31 [debug] cassandra_timeout = 5000
kong           | 2020/05/15 13:57:31 [debug] cassandra_username = "kong"
kong           | 2020/05/15 13:57:31 [debug] client_body_buffer_size = "8k"
kong           | 2020/05/15 13:57:31 [debug] client_max_body_size = "0"
kong           | 2020/05/15 13:57:31 [debug] client_ssl = false
kong           | 2020/05/15 13:57:31 [debug] database = "off"
kong           | 2020/05/15 13:57:31 [debug] db_cache_ttl = 0
kong           | 2020/05/15 13:57:31 [debug] db_cache_warmup_entities = {"services","plugins"}
kong           | 2020/05/15 13:57:31 [debug] db_resurrect_ttl = 30
kong           | 2020/05/15 13:57:31 [debug] db_update_frequency = 5
kong           | 2020/05/15 13:57:31 [debug] db_update_propagation = 0
kong           | 2020/05/15 13:57:31 [debug] dns_error_ttl = 1
kong           | 2020/05/15 13:57:31 [debug] dns_hostsfile = "/etc/hosts"
kong           | 2020/05/15 13:57:31 [debug] dns_no_sync = false
kong           | 2020/05/15 13:57:31 [debug] dns_not_found_ttl = 30
kong           | 2020/05/15 13:57:31 [debug] dns_order = {"LAST","SRV","A","CNAME"}
kong           | 2020/05/15 13:57:31 [debug] dns_resolver = {}
kong           | 2020/05/15 13:57:31 [debug] dns_stale_ttl = 4
kong           | 2020/05/15 13:57:31 [debug] error_default_type = "text/plain"
kong           | 2020/05/15 13:57:31 [debug] headers = {"server_tokens","latency_tokens"}
kong           | 2020/05/15 13:57:31 [debug] log_level = "notice"
kong           | 2020/05/15 13:57:31 [debug] lua_package_cpath = ""
kong           | 2020/05/15 13:57:31 [debug] lua_package_path = "./?.lua;./?/init.lua;"
kong           | 2020/05/15 13:57:31 [debug] lua_socket_pool_size = 30
kong           | 2020/05/15 13:57:31 [debug] lua_ssl_verify_depth = 1
kong           | 2020/05/15 13:57:31 [debug] mem_cache_size = "128m"
kong           | 2020/05/15 13:57:31 [debug] nginx_admin_directives = {}
kong           | 2020/05/15 13:57:31 [debug] nginx_daemon = "off"
kong           | 2020/05/15 13:57:31 [debug] nginx_http_directives = {{value="TLSv1.1 TLSv1.2 TLSv1.3",name="ssl_protocols"}}
kong           | 2020/05/15 13:57:31 [debug] nginx_http_ssl_protocols = "TLSv1.1 TLSv1.2 TLSv1.3"
kong           | 2020/05/15 13:57:31 [debug] nginx_http_status_directives = {}
kong           | 2020/05/15 13:57:31 [debug] nginx_http_upstream_directives = {{value="60s",name="keepalive_timeout"},{value="100",name="keepalive_requests"},{value="60",name="keepalive"}}
kong           | 2020/05/15 13:57:31 [debug] nginx_http_upstream_keepalive = "60"
kong           | 2020/05/15 13:57:31 [debug] nginx_http_upstream_keepalive_requests = "100"
kong           | 2020/05/15 13:57:31 [debug] nginx_http_upstream_keepalive_timeout = "60s"
kong           | 2020/05/15 13:57:31 [debug] nginx_optimizations = true
kong           | 2020/05/15 13:57:31 [debug] nginx_proxy_directives = {{value="/nginx/proxy-include.conf",name="include"}}
kong           | 2020/05/15 13:57:31 [debug] nginx_proxy_include = "/nginx/proxy-include.conf"
kong           | 2020/05/15 13:57:31 [debug] nginx_sproxy_directives = {}
kong           | 2020/05/15 13:57:31 [debug] nginx_stream_directives = {}
kong           | 2020/05/15 13:57:31 [debug] nginx_user = "nobody nobody"
kong           | 2020/05/15 13:57:31 [debug] nginx_worker_processes = "auto"
kong           | 2020/05/15 13:57:31 [debug] origins = {}
kong           | 2020/05/15 13:57:31 [debug] pg_database = "kong"
kong           | 2020/05/15 13:57:31 [debug] pg_host = "<IP_ADDRESS>"
kong           | 2020/05/15 13:57:31 [debug] pg_max_concurrent_queries = 0
kong           | 2020/05/15 13:57:31 [debug] pg_port = 5432
kong           | 2020/05/15 13:57:31 [debug] pg_semaphore_timeout = 60000
kong           | 2020/05/15 13:57:31 [debug] pg_ssl = false
kong           | 2020/05/15 13:57:31 [debug] pg_ssl_verify = false
kong           | 2020/05/15 13:57:31 [debug] pg_timeout = 5000
kong           | 2020/05/15 13:57:31 [debug] pg_user = "kong"
kong           | 2020/05/15 13:57:31 [debug] plugins = {"bundled"}
kong           | 2020/05/15 13:57:31 [debug] prefix = "/usr/local/kong/"
kong           | 2020/05/15 13:57:31 [debug] proxy_access_log = "logs/access.log"
kong           | 2020/05/15 13:57:31 [debug] proxy_error_log = "logs/error.log"
kong           | 2020/05/15 13:57:31 [debug] proxy_listen = {"<IP_ADDRESS>:8000","<IP_ADDRESS>:8443 http2 ssl"}
kong           | 2020/05/15 13:57:31 [debug] real_ip_header = "X-Real-IP"
kong           | 2020/05/15 13:57:31 [debug] real_ip_recursive = "off"
kong           | 2020/05/15 13:57:31 [debug] router_consistency = "strict"
kong           | 2020/05/15 13:57:31 [debug] router_update_frequency = 1
kong           | 2020/05/15 13:57:31 [debug] service_mesh = false
kong           | 2020/05/15 13:57:31 [debug] ssl_cipher_suite = "modern"
kong           | 2020/05/15 13:57:31 [debug] ssl_ciphers = "ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256"
kong           | 2020/05/15 13:57:31 [debug] status_access_log = "off"
kong           | 2020/05/15 13:57:31 [debug] status_error_log = "logs/status_error.log"
kong           | 2020/05/15 13:57:31 [debug] status_listen = {"off"}
kong           | 2020/05/15 13:57:31 [debug] stream_listen = {"off"}
kong           | 2020/05/15 13:57:31 [debug] trusted_ips = {}
kong           | 2020/05/15 13:57:31 [debug] upstream_keepalive = 60
kong           | 2020/05/15 13:57:31 [verbose] prefix in use: /usr/local/kong
kong           | 2020/05/15 13:57:31 [debug] loading subsystems migrations...
kong           | 2020/05/15 13:57:31 [verbose] retrieving cache schema state...
kong           | 2020/05/15 13:57:31 [verbose] schema state retrieved
kong           | 2020/05/15 13:57:31 [verbose] preparing nginx prefix directory at /usr/local/kong
kong           | 2020/05/15 13:57:31 [verbose] SSL enabled, no custom certificate set: using default certificate
kong           | 2020/05/15 13:57:31 [verbose] generating default SSL certificate and key

Kong error logs (/usr/local/kong/logs/error.log)

empty

Operating system

kong           | 2020/05/15 14:05:36 [notice] 1#0: built by gcc 9.2.0 (Alpine 9.2.0)
kong           | 2020/05/15 14:05:36 [notice] 1#0: OS: Linux 4.19.76-linuxkit
Note that the information above is from a simple docker-compose just using the environment variable directly in Kong's image.
I went through the changelog and couldn't find a mention of this being changed/removed :/
Could you please help me with this?
Update:

I tested adding a simple header in the file and it worked. So it's only related to the location block.

hello @LuanP, could you create a simple use case with kong prepare, i.e.:
KONG_NGINX_PROXY_INCLUDE=example.inc kong prepare
And let us know what error you are getting, and what did you expect instead?

Hi, I am closing this due to lack of activity. Please reopen if needed.


Setting babelrc to true isn't picking up .babelrc

I'm having an issue when doing:
babelOptions: {
    // doesn't work
    babelrc: true
},

This results in an unexpected token error as my test is attempting to parse code that requires multiple babel presets to parse (its a react component). This can easily be fixed by supplying the presets directly in the test config, or by adding the extends option like so:
babelOptions: {
    // this works
    presets: ["es2015", "stage-0", "react"],
    // this works too
    extends: path.resolve(__dirname, '..', '.babelrc'),
},

I'm wondering if I'm missing something here in regards to preferred approach when using a .babelrc? Looking through the code I don't see any logic around the babelrc boolean so I am unsure as to the desired experience here.
I would be happy to PR a fix if this indeed a bug, or update the documentation if I'm just missing something here. Thanks for this tool, it's super useful 👍

Thanks for this tool, it's super useful 👍

I'm glad you think so!

Looking through the code I don't see any logic around the babelrc boolean so I am unsure as to the desired experience here.

Correct, this just gets forward to babel.transform. So I'm unsure of what's going on here. If you want to add a console.log to make sure it's forwarding properly that'd be cool..... oh wait!
I just realized what's going on. I'm pretty sure that babel needs to know the filename to be able to resolve the babelrc. So we need to provide the filename as well. I'm unsure whether we could accomplish that from our perspective inside the tool, you may just have to do:
babelOptions: {
  babelrc: true,
  filename: __filename,
}

I think that should work. If it does, could you add a note in the documentation about this? Probably a pretty common error...
Actually, it may be a good idea to add an invariant if you specify babelrc: true and don't specify a filename. Could you Make a Pull Request for that?

Thanks for the response and absolutely! I'll get on that tonight.

I'm actually going to add a filepath property in part to support changes I'm making here. That'll have an impact here. The filepath in the babelOptions will default to the filepath provided for every test. I'll hopefully have this done soon. I'll let you know.

Sounds good, if the .babelrc relative to that filepath can be resolved into a filename for babel that would fix this issue. Throwing an invariant could still be an option but there might need to be a bit more logic involved as the existence of presets or plugins would make a .babelrc unnecessary even if the user has specified babelrc: true.

Let's see how the dust settles as @thejameskyle and I are both actively working on this package right now.

Quick question if you're around...
pluginTester({
  filename: __filename,
  tests: [
    {
      filename: '/some/path',
      // ...etc
    },
    {
      // should the filename here be derived from the filename of the root-level config?
      // or should it just be undefined as it currently is?
      code: 'blah',
    }
  ]
})

Note that if we do assume the filename is based on the root-level config, then you could unset that by doing: filename: undefined for any of the tests. I think this is the least surprising API so that's what I'm going to go with unless I hear from you :)

I think that will work fine, if it helps at all here is how I ended up using it.

I decided that doing all that filename business was adding too much complexity and opted for the simpler solution. I added an example for it which I hope is helpful!


How does one get the "Project does not exist" prompt?

I installed SBT in order to play with the Lift framework. (The book I'm using is Lift in Action, by Manning Publications.)
The book was written while SBT was still at version 0.7, but when I installed SBT using MacPort, it installed the latest version of SBT (0.11). I figured that shouldn't be a problem, but I'm not sure how to figure out this one:
It seems that SBT used to prompt the user upon starting in a directory without a project, with the following prompt:
Shell output:

Project does not exist, create new project? (y/N/s)

When I run SBT in a new directory, all I get is:
Shell output:

[info] Set current project to default-a016fc (in build file: ... )
>

I explored the commands that show up under help, but nothing appears to change this default behavior, or at least I haven't been able to find it. How does one set SBT to prompt me about creating a new project?

HI @harrah have you been able to find a solution? I ran into the same problem.


Panel View doesn't work for Kindle Touch

Hi, I've got kindlegen.exe in the root folder of KCC.
Tried converting as per instructions (image -> rar -> cbr -> mobi), but the panel view will simply not trigger at all. The same issue persists with the samples that you've provided.
Attack on Titan from Amazon works fine, so maybe it's a metadata issue?
Can you please check?

Also, I didn't notice a Kindle Touch profile, so I tried converting with the profiles for both "Kindle" and "Kindle PW 1/2".

Kindle Touch should use "Kindle" profile.
Could you elaborate "doesn't work"? How you trying to use it?

Hey mate, yes I can.
I'll list my steps. Hopefully that will help.

Archive the manga images folder (just 1 chapter) to either .rar or .zip
Change the extension to .cbr for .rar and .cbz for .zip
Convert the .cbr or .cbz to .mobi via KCC (all options by default, Kindle profile)
Paste the resulting .mobi into the "documents" folder in Kindle
Open the file and double tap to activate the panel view
The page slightly extends in width (literally like 1%)
The panel window appears in the bottom right corner, but the page does not get zoomed in
As a result the panel window looks empty inside and by swiping to the next page, the current page flickers around 3-4 times
So basically it is interpreted as panel view, but the panels don't get zoomed in
So I get the same full scale page 4 times, instead of each of the 4 corners being zoomed in sequentially.

Thank you

And this problem appear in sample file too?

Yes, it also persists on Ubunchu!-K45.mobi

Apparently 4th generation of Kindle devices is also affected by unknown regression. Closing it as duplicate.

One more question. Which firmware version you use?

It's version <IP_ADDRESS>. I believe it's the latest for Touch.


fix SPS insertParticlesFromArray : now the positionFunction can be run

When restoring formerly saved particles (in an external storage or previously removed ones), if a positionFunction is associated to thoses particles, it can be executed back on the insertion in the SPS

fix on particle.copyToRef() in case of missing color in the target

The whatsnew file has not been updated in purpose : it's just a tiny fix on the very last feature that is not yet documented.

ok, just added 2 space caracters in the whatsnew file, so it's commited and all the tests should pass now


[improve-#13678] add filter in method of setMainJarName

Purpose of the pull request

this close #13678
add filter in method of setMainJarName

Brief change log
this close : #13678
Verify this pull request

@fuchanghai Have u submitted a PR to dev branch?

@fuchanghai Have u submitted a PR to dev branch?

Hi, @EricGao888, i think it's unnecessary to submit to dev, ref https://github.com/apache/dolphinscheduler/issues/13678#issuecomment-1457546588

@fuchanghai Have u submitted a PR to dev branch?

Hi, @EricGao888, i think it's unnecessary to submit to dev, ref #13678 (comment), WDYT?

Hi, @EricGao888, i think it's unnecessary to submit to dev, ref #13678 (comment), WDYT?

this branch copy from 3.1.5

@fuchanghai Have u submitted a PR to dev branch?

Hi, @EricGao888, i think it's unnecessary to submit to dev, ref #13678 (comment), WDYT?

Thanks again


fix: fix vote delegation

@tensojka I've fixed the the issues with vote delegation. Please review to be sure I'm going in the right direction before I add the tests. Thank you!

The code now compiles successfully, which was not the case initially. The initial issue was due to the absence of withdraw_delegation and delegate_vote declarations in the IProposals trait.
Additionally, there was an error in the code that retrieves the gov_token_addr. The incorrect line of code (line 400) was commented out:
// let gov_token_addr = self.get_governance_token_address();
This was corrected on line 401 with the following code:
let gov_token_addr = IGovernanceDispatcher { contract_address: get_contract_address() } .get_governance_token_address();
At this point, I have not yet written tests for the code. I just wanted to get your feedback before proceeding with writing the tests.

Still missing [] Delegate, vote and withdraw test
Otherwise LGTM!

Working on it!


rendering  component instead of native button

At the moment 'button' is hardcoded in the source code:
https://github.com/material-components/material-components-web-react/blob/master/packages/tab/index.tsx#L206
Would it be a good idea to support regular anchors?
The use case is to be able to render regular navigation links instead of a list of buttons with onClicks and navigation to a different url in javascript.
It would be enough if we just used the Button component instead of native html
Then something like this would be possible:
<Tab
  key={index}
  isFadingIndicator={isFadingIndicator}
  indicatorContent={indicatorContent}
  href="http://google.com"
  onClick={(event: React.MouseEvent<any>) => {
    event.preventDefault();
  }}
>
  Tab {num + 1}
</Tab>

as the Button component is conditionally rendering button or a based on whether the href property is falsy or not:
https://github.com/material-components/material-components-web-react/blob/master/packages/button/index.tsx#L77
Proposed solution:
https://github.com/material-components/material-components-web-react/compare/master...barteksekula:master

So we'd be using the Button component, but not the styles? Could we instead just use something like props.tag? See https://github.com/material-components/material-components-web-react/blob/master/packages/list/ListItem.tsx#L207

Sure, that's also an option. I just thought it would be better to just utilize the existing Button component, especially that Tab's props are based on HTMLButtonElement, if we expose Tag, even with default prop set to 'button' users will still be able to set it to an element that is not intended to be used inside a Tab Bar.
I just took a quick look how other material implementation does that and they all seem to render some kind of Button/ButtonBase component as the first child of Tab component.
Would you be willing to accept a contribution with that change? Just tell me which one do you prefer and I will do it (either Button component or Tag prop).
Thanks!

two alternatives:
export interface TabProps extends React.HTMLProps<HTMLButtonElement | HTMLAnchorElement> {
  active?: boolean;
  focusOnActivate?: boolean;
  isFadingIndicator?: boolean;
  indicatorContent?: React.ReactNode;
  minWidth?: boolean;
  isMinWidthIndicator?: boolean;
  stacked?: boolean;
  tag?: "button" | "a";
  previousIndicatorClientRect?: ClientRect;
  onInteraction?: () => void;
}

or just
export interface TabProps extends React.HTMLProps<HTMLElement> {
  active?: boolean;
  focusOnActivate?: boolean;
  isFadingIndicator?: boolean;
  indicatorContent?: React.ReactNode;
  minWidth?: boolean;
  isMinWidthIndicator?: boolean;
  stacked?: boolean;
  tag?: string;
  previousIndicatorClientRect?: ClientRect;
  onInteraction?: () => void;
}

both with
defaultProps = {
  ...
  tag: 'button',
  ...
}

@barteksekula yeah that makes sense there is a button base, however it was not designed to be used within the tabs component. That might be a good update for MDC Web (vanilla version).
The React Button also has logic specific to the button that the tab will never use, which adds unnecessary cruft to the tab. Can we go with Tag?
Also export interface TabProps extends React.HTMLProps<HTMLButtonElement | HTMLAnchorElement> { makes more sense to me. This way users will not use an unintended element.

Closing this since we merged #928


Map drag during polygon draw will add point with leaflet 1.0

Leaflet version I'm using: 1.0.3 and 0.7.2
Leaflet Draw version I'm using: master
Browser (with version) I'm using: chrome 56 / edge / ie11
OS/Platform (with version) I'm using: linux + windows

When using with leaflet 0.7.x you can move the map by dragging while drawing a polygon. With leaflet 1 you can also drag the map, but it will add a point where you click to start the drag.
Steps:

Start drawing a polygon
Click to add a point
Drag the map (mouse down, move, mouse up)

With leaflet 0.7 it will just to the drag, with leaflet 1 it will also add a point on the mouse down. I think the behaviour with 0.7 is the desired one.
See examples https://leaflet.github.io/Leaflet.draw/docs/examples/full.html and https://leaflet.github.io/Leaflet.draw/docs/examples-0.7.x/full.html

This example has the correct behavior with Leaflet 1.0.1+ffcfcc1 https://b3ncr.github.io/docs/examples/full.html but is version 0.4.2

The problem is in L.Draw.Polyline._onTouch. This simulates mouse down+up so directly adding a new point. This should not work on just touchstart, but on touchstart+touchend like mousedown+mouseup I guess. I'v been looking into this but I don't see any touchend events being fired. I have no good touch device to debug the touch handling.
For now I added this hack:
	var originalOnTouch = L.Draw.Polyline.prototype._onTouch;
	L.Draw.Polyline.prototype._onTouch = function( e ) {
		if( e.originalEvent.pointerType != 'mouse' ) {
			return originalOnTouch.call(this, e);
		}
	}
})();```

So on a desktop using a mouse it doesn't handle touch events. I need get a touch device to debug the touch handling.

If you are programatically enabling any drawing mode, you must put the aforementioned hack before your call to enable!
ie.
...
(function() {
var originalOnTouch = L.Draw.Polyline.prototype._onTouch;
L.Draw.Polyline.prototype._onTouch = function( e ) {
if( e.originalEvent.pointerType != 'mouse' ) {
return originalOnTouch.call(this, e);
}
}
})();
...
new L.Draw.Polygon(map, drawControl.options.polygon).enable();
Happy coding!

This issue has one more very unwanted side effect. It is possible to create invalid geometry with lines only one point long. If I click on "Draw a polyline" tool, then I create a point in the map and then I click on the point once more, the point disappears. It is not visible, but in the background, there is invalid geometry, which breaks when I use it in PostGIS.

I used the solution @richardhinkamp  provided, which works fantastically for allowing the map dragging without adding a node - however if my polyline revisits any of the previous nodes, I can no longer click on their noes to place the line. For example if my polyline is a loop (my project is making route cards for walks, so often loops are necessary), the line has to finish next to the start point, not over the top.

This work arounds works fine for desktop but unfortunately it still doesn't work for touch devices (chrome).

In you wan't to make this to work in a mobile device too, just add:

&& e.originalEvent.pointerType != 'touch'

Modify the script to this:
(function() {
	var originalOnTouch = L.Draw.Polyline.prototype._onTouch;
	L.Draw.Polyline.prototype._onTouch = function( e ) {
		if( e.originalEvent.pointerType != 'mouse'  && e.originalEvent.pointerType != 'touch' ) {
			return originalOnTouch.call(this, e);
		}
	}
})();

Behaviour of this changed with some newer Leaflet version. If I try the demo which has hardwired Leaflet 1.3.1, the issue is present. But when I update the Leaflet to 1.6.0, drawing polygon/polyline on desktop works fine.
But not on mobile - dragging the map still produces unwanted points. And I was not able to fix this by the suggested workarounds.

And I was not able to fix this by the suggested workarounds.

Make sure that tap handler is disabled.
E.g. create map with {tap: false} option.

@johnd0e Thanks, you are right. After that everything works perfectly.

The solution refers to Polyline... does this help with Polygon and Rectangle draw as well?
Drawing polygon works fine and during creation you can still hold mouse down to PAN.
But on rectangle the initial click is wonky and any slight drag of mouse causes it to end and create a super tiny rectangle.  So that's one issue.  The other issue is if you do get the rectangle draw to start... you cannot pan at all.  You can zoom but you can't pan.  Or at least in my app.  The simple demos online dont act this way so not sure what is causing it.


Support environment variables

I'd like to use an environment variable in the glsllint.glslangValidatorPath, but this does not seem to be supported.
{
  "glsllint.glslangValidatorPath": "${env:VULKAN_SDK}\\Bin\\glslangValidator.exe"
}

Great, thank you very much.


File with settings on mac and windows

I have file with settings (scss.yml, .jshintrc etc.) on Dropbox
It's possible / define this same files to usage on mac and windows (if yes - where or how?)

I'm not sure what this has to do with SublimeLinter3. Are you asking how to keep a config file—any config file—in sync between computers? What's wrong with git? We are on GitHub after all.

I wrote it here, because SublimeLinter have settings section.
I would define this same file config for mac and win by this way:
args: [
"--config", "/path/to/file"
]

but path to the file (which I have on dropbox) is dfferent on mac / win

Ah, I misunderstood your question. You're not asking how to share your config files between OSes, you're asking how to point to those shared config files in the same way between OSes.
Mac and Windows paths are quite different, so I'd guess that the only way to accomplish this would be through environment variables. You can check out the setting tokens section of the docs for how to use them.
For example, you could have a JSHINTRC environment variable that points to /Users/my-name/.jshintrc on Mac, and C:\Users\my-name\.jshintrc on Windows.
I'm not sure exactly what subset of environment variables are available to Sublime Text's python context, so this may not work after all. If it doesn't, I'm not sure how to help you :disappointed:

Actually, assuming your Dropbox directory is located at the same path relative to your home directory on both OSes, you may be able to do this:
{
  args: ["--config", "${home}/Dropbox/path/to/file"]
}

@jawshooah - it seems that the last code works. Thanks!

Glad to hear it :beers:


Deprecation Warning for Division Operator in Sass

Issue Summary:
I encountered a deprecation warning while using FontAwesome that's related to the use of the division operator (/) in Sass. This warning indicates that starting from Dart Sass version 2.0.0, using / for division outside of a calc() function is deprecated.
Recommendation:
The recommendation provided in the warning message is to use e
ither the math.div() function or calc() to perform division in Sass code.
Impact:
This deprecation warning affects the compatibility of FontAwesome with future versions of Dart Sass, potentially causing issues for users who rely on FontAwesome in their projects.
Steps to Reproduce:
Install FontAwesome and use it in a project.
Compile Sass code that uses the division operator (/) for division outside of a calc() function.
Observe the deprecation warning.
Are you working on this issue?
yes

@Arnabdaz  sir can u please review it! if possible assign me this issue!

@Arnabdaz sir can u please review it! if possible assign me this issue!

sure you can work on this issue go ahead

fixed by #214


rpc server can't detect port conflicting with other process

Is your feature request related to a problem? Please describe.
source version: v1.13.1
built with: bazel 0.19.2
language: cpp
I was trying to start my grpc server on an existing port, and I got no error message. Because other process is listening on that port, my server can't receive any requests. And I have tried to get the bound port of ServerBuilder::AddListeningPort after ServerBuilder::BuildAndStart like the comments of the interface describe, that I also get a non-zero port.
Then I read the source code, and finally find that SO_REUSEADDR is set to every socket fd, so that error of address already in used is ignored.
Describe the solution you'd like
An easy way to check whether server is listening correctly.

@yang-g : can you advise on how to know if server is listening on a shared port correctly?

@yann-yy I think what you meant to say is SO_REUSEPORT rather than SO_REUSEADDR?
If your environment does not have a way to provide a unused port for you, you can disable the SO_REUSEPORT via a server side channel argument.
For example, in C++, you can do the following to disable it:
builder.AddChannelArgument(GRPC_ARG_ALLOW_REUSEPORT, 0);

@yann-yy I think what you meant to say is SO_REUSEPORT rather than SO_REUSEADDR?
If your environment does not have a way to provide a unused port for you, you can disable the SO_REUSEPORT via a server side channel argument.
For example, in C++, you can do the following to disable it:
builder.AddChannelArgument(GRPC_ARG_ALLOW_REUSEPORT, 0);

This works for me, thanks a lot.


Fix dist/flowbite.js to not use arrow function

Describe the bug
On IE11 the dropdown does not work because of the use of arrow function.
To Reproduce
Steps to reproduce the behavior:

Go to IE11 https://flowbite.com/docs/components/dropdowns/
Open web console
See error

Expected behavior
Dropdown list should appear
Screenshot

Desktop (please complete the following information):

OS: Windows
Browser IE11
Version 1.4.5

Additional context
On my project I updated the first line in flowbite.js
/******/ (() => { // webpackBootstrap

with
/******/ (function() { // webpackBootstrap

The main goal for this is to have IE11 support.
I am not sure if the source files have support for IE11 ... or if the projects even want to support IE11.
For webpack.config.js, a quick fix is to use:
module.exports = {
    target: ["web", "es5"]
}

Hey @ioanacristinamarinescu  @adiroiban,
I'll look into this for the next version. Thank you!
@adiroiban: you can open a PR if you want to and I'll take a look at it.

Sure. I will create the PR.

PR https://github.com/themesberg/flowbite/pull/163
Many thanks for this nice project :)

Hey peeps,
The arrow function is no longer used for the dist files as of v1.6.0.
Please check out this resource for confirmation:
<EMAIL_ADDRESS>
Cheers,
Zoltan


V0p1p5b

Codecov Report

Merging #20 (00b1692) into master (d7cd54f) will decrease coverage by 0.37%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #20      +/-   ##
==========================================
- Coverage   59.05%   58.67%   -0.38%
==========================================
  Files           2        2
  Lines         127      121       -6
==========================================
- Hits           75       71       -4
+ Misses         52       50       -2

Impacted Files
Coverage Δ

src/read_data.jl
50.00% <0.00%> (ø)

src/thredds_servers.jl
100.00% <0.00%> (ø)

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 d7cd54f...00b1692. Read the comment docs.


Document errors with shared folders

This is an issue I found while trying out vagga trough OS X.
It's rather obvious in hindsight, but hey :).

Hi, looks nice addition. It's known thing but have never been placed in documentation. I have a few questions though:

Does setting storage-dir actually works on mac? As far as I remember it doesn't work on windows, because vagrant refuses to make symlinks in vagrant directory (i.e. we do them outside of storage-dir), so current best practice is something like this (documented in #53):

mkdir .vagga
sudo mount --bind /some/writable/folder .vagga

Usually, people are happy with vagrant vagga plugin which does that automatically. So do you think it's better to recommend a plugin, a mount --bind hack or storage-dir?

If you have a little more time it would be helpful to test vagga in docker for mac (#269) it would probably need same hacks, like mounting .vagga into linux file system and so on. But it has two important improvements:

It declares the support of inotify (so you can use auto-rebuild, hot-reload and similar techniques)
You don't have to run a separate virtual machine for each project you have a vagga.yaml for

Thanks, for your help. We definitely want to make vagga easier for OS X users.

Hi Paul,
I didn't even know about vagrant-vagga :). I will revise the section over the weekend.
Best,
Florian

On 10 Jun 2016, at 11:02, Paul Colomiets<EMAIL_ADDRESS>wrote:
Hi, looks nice addition. It's known thing but have never been placed in documentation. I have a few questions though:
• Does setting storage-dir actually works on mac? As far as I remember it doesn't work on windows, because vagrant refuses to make symlinks in vagrant directory (i.e. we do them outside of storage-dir), so current best practice is something like this (documented in #53):
mkdir .vagga
sudo mount --bind /some/writable/folder .vagga
• Usually, people are happy with vagrant vagga plugin which does that automatically. So do you think it's better to recommend a plugin, a mount --bind hack or storage-dir?
If you have a little more time it would be helpful to test vagga in docker for mac (#269) it would probably need same hacks, like mounting .vagga into linux file system and so on. But it has two important improvements:
• It declares the support of inotify (so you can use auto-rebuild, hot-reload and similar techniques)
• You don't have to run a separate virtual machine for each project you have a vagga.yaml for
Thanks, for your help. We definitely want to make vagga easier for OS X users.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Anyway, let me merge it as is and we can add more info later.


LSP spec suggests result=null is valid when there's an error, but JSON-RPC says this is not allowed

In ResponseMessage it has this:
	/**
	 * The result of a request. This can be omitted in
	 * the case of an error.
	 */
	result?: any;

This suggests that it's allowed to send null as result if there is an error (as opposed to omitting it). This is convenient for me, however I'm slightly nervous that clients may not handle this correctly, and may interpret a null result as meaning there was no error (and then not check the error property).
Assuming result=null is valid for an error, I think it should be made clearer in the spec that the error field takes precedence when both fields are present.

@dbaeumer (see above - I think this may need | null adding?)

(@dbaeumer Sorry for the spam, but this seems incorrect and I think it may have been overlooked - see above :-))

Yes, sorry overlooked it. Reading through the spec (https://www.jsonrpc.org/specification#response_object) I agree that null should be a valid result value.

Change the node implementation accordingly.


Cannot add again a scheduled query deleted from a pack

What version of fleet are you using (fleet version --full)?
fleet - version 2.5.0
branch: 	master
revision: 	8e77f4369a3d49005beebe08f6a7ac453810c586
build date: 	2020-01-26T22:02:00Z
build user: 	zwass
go version: 	go1.13.4
What operating system are you using?
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.4 LTS
Release:	18.04
Codename:	bionic
What did you do?
I want to add again a scheduled query that has been already added in a Pack and then deleted.
What did you expect to see?
The scheduled query should be added in the Pack
What did you see instead?
An error HTTP 500
And in the database, in table scheduled_queries, here there is the pack I want to update:
+----+---------------------+---------------------+---------------------+---------+---------+----------+----------+----------+---------+----------+---------+-------+-----------------------------------+-----------------------------------+-------------+
| id | created_at          | updated_at          | deleted_at          | deleted | pack_id | query_id | interval | snapshot | removed | platform | version | shard | query_name                        | name                              | description |
+----+---------------------+---------------------+---------------------+---------+---------+----------+----------+----------+---------+----------+---------+-------+-----------------------------------+-----------------------------------+-------------+
|  4 | 2020-03-16 13:50:21 | 2020-05-22 10:07:08 | NULL                |       0 |       3 |      123 |    86400 |        0 |       1 | linux    | NULL    |  NULL | Installed software list - Linux   | Installed software list - Linux   |             |
|  5 | 2020-03-16 13:50:34 | 2020-05-22 10:07:16 | NULL                |       0 |       3 |      124 |    86400 |        0 |       1 | darwin   | NULL    |  NULL | Installed software list - macOS   | Installed software list - MacOS   |             |
|  6 | 2020-03-16 13:50:51 | 2020-04-09 14:45:46 | 2020-04-09 14:45:46 |       1 |       3 |      135 |      300 |        1 |       0 | windows  | NULL    |  NULL | Installed software list - Windows | Installed software list - Windows |             |
| 14 | 2020-03-19 14:54:28 | 2020-06-12 15:22:31 | NULL                |       0 |       3 |      171 |    21600 |        1 |       0 | linux    | NULL    |  NULL | Web Browsers - Linux              | Web Browsers - Linux              |             |
+----+---------------------+---------------------+---------------------+---------+---------+----------+----------+----------+---------+----------+---------+-------+-----------------------------------+-----------------------------------+-------------+

I want to add again the query with the id 6

As a workaround, is this OK if I update the record in the database :
UPDATE scheduled_queries
SET deleted_at = NULL, deleted = 0
WHERE id = 6

This is a dupe of #2227.
Your workaround looks good.


Added the ability to skip certain collections when importing

So that you can do:
importer = TenantImporter.new(converter, tenant, skip: [:events, :scheduled_events])

Mainly for an import that Rod's asking for my help with for flcplano — they're trying to reimport to get 6 people who didn't import previously, but we've manually fixed their events for them so we don't want to go through that again.

Looks good. :+1:

..but I can't change labels :sob:


nz-menu-item doesn't work with CanDeactivate and current route

Reproduction link
https://stackblitz.com/github/nitrexx/ng-zorro-menu-bug
Steps to reproduce

Create 2 components with router
Create component with nz-menu with nzMatchRouter
Create Interface wiht CanDeactivate method
Implements Interface with CanDeactivateMethod in components and return false
Create guard for canDeactivate router paramater
Click on first item in menu, it will change a route to the component
Click on second item (canDeactivate returns false and route is same like in previous step), ng-menu-item change active item to the second item

What is expected?
It shouldn't change selected item in menu on click but on the route if I use nzMatchRouter
What is actually happening?
It changes selected menu item on click event and not depends on route

Environment
Info

ng-zorro-antd
8.4.1

Browser
google chrome Version 77.0.3865.120 (Official Build) (64-bit)

I have the same problem.
Is there any thing can me on this issue?

Maybe we should also listen NavigationCancel router event.


Multiple toolbar line requirements

I was able to add the 'multiple button rows' feature (#14) as a plugin, but it requires a few small changes to the core.
The first is that I add an id to the buttonset span of each plugin, so that it's addressable.
The second is an update to @rryter's previous pull request (#16) allowing the toolbar to stay at a fixed position instead of floating. The update allows the use of "top" instead of a numeric value for the y-offset, so that different toolbar heights (due to multiple lines) don't break the layout.

Could we use classes instead of IDs?

Definitely - would you just use the widgetname as the classname then (without the uuid)?
It's not likely that anyone already has a class named 'hallolists', I guess it would be possible though.

I would use paths, so for example .hallotoolbar .hallolists. That is unlikely to clash with on-site classes :-)


Add GoG support

Description of the Change

Modify Setup App to handle differences between Steam and GoG executable. Provide corresponding patch files for initial platform patching. Existing patches for "merged", "terraria" and "tModLoader" have been modified to handle the additional patching step.
Alternate designs

N/A
Why this should be merged into tModLoader

Benefits

GoG users can enjoy tModLoader
Possible drawbacks

On specific occasions changes in terraria project file may lead to merge conflicts.
Applicable Issues

N/A
Sample Usage

N/A

We want to keep things as consistent and reliable as possible we only want to decompile a single version. I think the purpose of your setup changes is to allow developing tML when decompiling the GoG version? If so we'd rather not incur the maintenance cost.
Is the only thing required to disable the steam check? If so I have a good plan

I think I understand your idea better now. You are correct the main difference is the Steam Social API. The other issue is some sort of UID in projectiles but your patches are removing that.
Based on that input all this probably can be handled with just project build settings to compile GoG exe.


add basics of v1/v2 comparitor

To compare what we get from V1 / V2.
Creates a bigger distinction between the V1 / V2 API service, too, which is where I suppose we might want to go.
If we start decoupling the query from the actual UI, I reckon we could actually have both running side by side.

Killing for #3684


BUG: read_parquet does not pass kwargs appropriately

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): macOS 12.2.1
Modin version (modin.__version__): b240370
Python version: 3.9.12
Code we can use to reproduce:

import modin.pandas as pd

# Won't work as intended with the memory_map parameter
pd.read_parquet("blah.parquet", engine="pyarrow", memory_map=True)

Describe the problem
read_parquet should work with standard parquet data, but may falter when engine-specific kwargs are passed into the call. We should try to handle these kwargs properly so that we maintain concordance with pandas behavior. There will most likely be some additional complexity for more complex kwargs passed in.

@pyrito What errors do we get when we pass kwargs like memory_map?

@mvashishtha no error because those never get passed down.

Currently we default to pandas in case of any engine-specific kwargs passed to read_parquet. @mvashishtha feel free to reopen if I missed something.