Error running mongoclient

error while running mongoclient on Manjaro
symbol SSLv3_client_method, version OPENSSL_1.0.0 not defined in file libssl.so.1.0.0 with link time reference

Hello
thanks for the feedback, going to check that.

Hello again,
I've checked that, by installing Manjaro to my virtual machine and it worked like a charm. I guess issue is related with you. Could you please try to install openssl ? (just to try)
Cheers

Thank you for your response i already tried that but  no sucess.
Error:
  ivoribeiro@ivo-manjaro  ~/Packages/Mongoclient-linux-x64  ./Mongoclient INFO  electrify:index:  initializing INFO  electrify:plugins:  use  mongodb INFO  electrify:plugins:  use  nodejs INFO  electrify:plugins:  use  socket INFO  electrify:index:  start INFO  electrify:plugins:  start INFO  electrify:plugins:mongodb:  starting mongo... /home/ivoribeiro/Packages/Mongoclient-linux-x64/resources/app/bin/mongod: /usr/lib/libcrypto.so.1.0.0: no version information available (required by /home/ivoribeiro/Packages/Mongoclient-linux-x64/resources/app/bin/mongod) /home/ivoribeiro/Packages/Mongoclient-linux-x64/resources/app/bin/mongod: /usr/lib/libssl.so.1.0.0: no version information available (required by /home/ivoribeiro/Packages/Mongoclient-linux-x64/resources/app/bin/mongod) /home/ivoribeiro/Packages/Mongoclient-linux-x64/resources/app/bin/mongod: /usr/lib/libssl.so.1.0.0: no version information available (required by /home/ivoribeiro/Packages/Mongoclient-linux-x64/resources/app/bin/mongod) /home/ivoribeiro/Packages/Mongoclient-linux-x64/resources/app/bin/mongod: relocation error: /home/ivoribeiro/Packages/Mongoclient-linux-x64/resources/app/bin/mongod: symbol SSLv3_client_method, version OPENSSL_1.0.0 not defined in file libssl.so.1.0.0 with link time reference

Could you please download non-ssl mongod binary and replace this:
/home/ivoribeiro/Packages/Mongoclient-linux-x64/resources/app/bin/mongod
with this mongod binary:
https://www.mongodb.com/dr/fastdl.mongodb.org/linux/mongodb-linux-x86_64-3.4.0.tgz/download

It worked :) but why ?

Probably meteor's mongod instance was needed an openssl binary which you don't have, but it's not needed for mongoclient since it's not using SSL while connecting to its own mongodb. I'm glad it worked :)


Unnecessary strictNullChecks errors for nested property access protected by type predicate

Bug Report
TypeScript shows strictNullChecks errors for "possible 'null'" and "possible 'undefined'" values along a property access chain, even though the code is protected by a type predicate using optional chaining that guarantees the property access chain is valid.
🔎 Search Terms
NonNullable type predicate optional chaining
🕗 Version & Regression Information

This is the behavior in every version I tried (from 3.7.5. to 4.9.0 nightly), and I reviewed the FAQ for entries about type system behaviour, type guards and save navigation operator.

⏯ Playground Link
Playground Link: Provided
💻 Code
type SomeType = {
  prop?: {
    nestedProp?: string
  }
}
declare function someRandomFunc(...args: any[]): SomeType | null;
const isDefinedAndNotNull = <T,>(val: T | null | undefined): val is NonNullable<T> => val != null;

const instance = someRandomFunc();

if (isDefinedAndNotNull(instance?.prop?.nestedProp)) {
  // Unexpected strictNullChecks errors on the line below:
  // - instance: Object is possibly 'null'
  // - instance: Object is possibly 'undefined'
  // - prop: Object is possibly 'undefined'
  someRandomFunc(instance.prop.nestedProp);
}

if (
  isDefinedAndNotNull(instance) &&
  isDefinedAndNotNull(instance?.prop) &&
  isDefinedAndNotNull(instance?.prop?.nestedProp)
  ) {
  // No strictNullChecks errors here, but too much unnecessary code above
  someRandomFunc(instance.prop.nestedProp);
}

Compiler Options
{
  "compilerOptions": {
    "strict": true,
    "noImplicitAny": true,
    "strictNullChecks": true,
    "strictFunctionTypes": true,
    "strictPropertyInitialization": true,
    "strictBindCallApply": true,
    "noImplicitThis": true,
    "noImplicitReturns": true,
    "alwaysStrict": true,
    "esModuleInterop": true,
    "declaration": true,
    "experimentalDecorators": true,
    "emitDecoratorMetadata": true,
    "target": "ES2017",
    "jsx": "react",
    "module": "ESNext",
    "moduleResolution": "node"
  }
}

🙁 Actual behavior
TypeScript emits errors about possible null / undefined values along a property access chain.
This is unexpected as the code is guarded by a type predicate.
🙂 Expected behavior
No strictNullChecks errors.

This seems like an expected limitation, given that checking the value of a property doesn't narrow the containing object in general (except for discriminated unions).  I note that there are potentially multiple steps of inference required:

instance?.prop?.nestedProp is known to not be undefined, therefore
instance?.prop must also be non-nullish, therefore
instance must also be non-nullish

It would indeed be nice if this pattern worked, but I don't know if the control-flow analysis machinery as it exists today is capable of making these inferences.

Duplicate of #34974.

As pointed out in the dupe'd issue, this works if you write the type check inline:
if (instance?.prop?.nestedProp != null) {
  someRandomFunc(instance.prop.nestedProp);  // saul goodman
}

So ignore my comment above - TS can do the necessary inferences, it's just that NonNullable<T> is opaque to it.

Thanks for the comments. @RyanCavanaugh's comments on the original issue gives me hope this might be fixed in the future, and there's no need for me to leave this duplicate issue open.


T3C Race Condition Update

There currently exists a scenario, and happens in production environments, where the use of a boolean flag alone causes a race condition when setting/unsetting the upd_pending and reval_pending flags associated with servers.

Cache config (T3C) checks and sees the queue flag is set (Say it's false)
Cache config (T3C) starts running
Updates are queued in Traffic Ops (Set flag to true)
Cache config (T3C) un-sets the flag (Set flag back to false)
The new update is not applied.

To address this race condition, rather than relying on a boolean flag, the use of timestamps will help ensure the last time either update or revalidate requests were set and/or applied. However, to ensure both forward and backward compatibility, we need to maintain the use of the booleans while utilizing timestamps.
Most notably, 4 fields will be added when queuing update/revals. As well as CRUD related calls involving servers. These four fields are:
"configUpdateTime":"1969-12-31T17:00:00-07:00"
"configApplyTime":"1969-12-31T17:00:00-07:00"
"revalUpdateTime":"1969-12-31T17:00:00-07:00"
"revalApplyTime":"1969-12-31T17:00:00-07:00"

Which Traffic Control components are affected by this PR?

Documentation
Traffic Control Cache Config (T3C, formerly ORT)
Traffic Control Client (Go clients)
Traffic Ops
Traffic Portal
unknown

What is the best way to verify this PR?

All unit tests should pass.
All API integration tests should pass.
If desired, manual testing by hitting the endpoints for /server (GET, PUT, POST, and DEL) to ensure the correct validation logic is performed with or without the added fields to the request. All responses should contain the 4 new fields as well as the two original upd_pending and reval_pending flags.
If this is a bugfix, which Traffic Control versions contained the bug?

PR submission checklist

[x] This PR has tests
[x] This PR has documentation - Documentation may or may not be included in this first PR
[x] This PR has a CHANGELOG.md entry
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

I restarted CiaB and t3c tests; both fail consistently. I can't tell from the limited logs of the CiaB why it's failing for sure, but I'd bet anything it's because t3c is crashing, for the same reason its tests are failing - stack trace:
    to_updater_test.go:40: t3c-request failed: exit status 2: stdout:  stderr: INFO: config.go:202: 2022-03-08T05:12:18.575778433Z: loading old config took 400ns
        INFO: config.go:179: 2022-03-08T05:12:18.575806233Z: using old config for IMS requests
        INFO: t3c-request.go:46: 2022-03-08T05:12:18.575813432Z: configuration initialized
        INFO: client.go:75: 2022-03-08T05:12:18.575820332Z: URL: 'https://to_server:443' User: 'admin' Pass len: '6'
        INFO: client.go:83: 2022-03-08T05:12:18.57596943Z: TO URL string: 'https://to_server:443'
        INFO: client.go:84: 2022-03-08T05:12:18.57603403Z: TO URL: 'https://to_server:443'
        INFO: client.go:91: 2022-03-08T05:12:18.576473124Z: Logging in to Traffic Ops '[<IP_ADDRESS>]' with Cookie
        INFO: getdata.go:79: 2022-03-08T05:12:18.576502024Z: Getting data 'update-status'
        panic: interface conversion: interface {} is *tc.ServerUpdateStatus, not *tc.ServerUpdateStatusV4

        goroutine 1 [running]:
        github.com/apache/trafficcontrol/cache-config/t3cutil/toreq.(*TOClient).GetServerUpdateStatus.func1({0x705aa0, 0xc00026da00})
        	/tmp/go/src/github.com/apache/trafficcontrol/cache-config/t3cutil/toreq/clientfuncs.go:729 +0x4d7
        github.com/apache/trafficcontrol/cache-config/t3cutil/toreq/torequtil.GetRetry(0x0, {0xc0000a2c60, 0x24}, {0x705aa0, 0xc00026da00}, 0xc00021f678)
        	/tmp/go/src/github.com/apache/trafficcontrol/cache-config/t3cutil/toreq/torequtil/torequtil.go:52 +0x147
        github.com/apache/trafficcontrol/cache-config/t3cutil/toreq.(*TOClient).GetServerUpdateStatus(0xc00009cee8, {0x7ffd64f0296d, 0xf}, 0x0)
        	/tmp/go/src/github.com/apache/trafficcontrol/cache-config/t3cutil/toreq/clientfuncs.go:724 +0x19c
        github.com/apache/trafficcontrol/cache-config/t3cutil.GetServerUpdateStatus({{0x7ffd64f0296d, 0xf}, {0x7ffd64f02994, 0xd}, 0xc00009cee8, 0x1, 0xb2d05e00, {0x7ffd64f0292c, 0x6}, {0x7ffd64f0290f, ...}, ...})
        	/tmp/go/src/github.com/apache/trafficcontrol/cache-config/t3cutil/getdata.go:71 +0x8c
        github.com/apache/trafficcontrol/cache-config/t3cutil.WriteServerUpdateStatus({{0x7ffd64f0296d, 0xf}, {0x7ffd64f02994, 0xd}, 0xc00009cee8, 0x1, 0xb2d05e00, {0x7ffd64f0292c, 0x6}, {0x7ffd64f0290f, ...}, ...}, ...)
        	/tmp/go/src/github.com/apache/trafficcontrol/cache-config/t3cutil/getdata.go:133 +0x59
        github.com/apache/trafficcontrol/cache-config/t3cutil.WriteData({{0x7ffd64f0296d, 0xf}, {0x7ffd64f02994, 0xd}, 0xc00009cee8, 0x1, 0xb2d05e00, {0x7ffd64f0292c, 0x6}, {0x7ffd64f0290f, ...}, ...})
        	/tmp/go/src/github.com/apache/trafficcontrol/cache-config/t3cutil/getdata.go:84 +0x3a2
        main.main()
        	/tmp/go/src/github.com/apache/trafficcontrol/cache-config/t3c-request/t3c-request.go:66 +0x31e
    types.go:58: ---- DeleteTestTypes ----
    ```


Add ability to set custom prefix for internal fields

This allows setting the prefix used for FullSerializers internal fields such as $ref and $type. This is useful when interacting with systems that have restrictions on the characters which can be used in key names.

Thanks! I'm happy to merge once the two comments are addressed.

I've changed it to compute the field names once on object instantiation.

Thanks!


Crash when reading invalid/malformed key string

Hi,
I'm reading a key from string stored in DB, but if the key is malformed, the following code crashes the app without throwing any error.
let rsaKey = try RSAKey.public(pem: key)
let signer = JWTSigner.rs512(key: rsaKey)
_ = try JWT<JWTIdentity>(from: identityHeader, verifiedUsing: signer)

Specifically the fault line is:
let rsaKey = try RSAKey.public(pem: key)

Error message:

Fatal error: Unexpectedly found nil while implicitly unwrapping an Optional value

If the key is well formed the error is not throwed...
Any idea?

It's working after fix.
Thanks!


New version

⚠ EDIT THIS TEMPLATE AND REMOVE THIS MESSAGE WHEN YOU'RE DONE ⚠
About
Write a few sentences describing the bug you've found. Be as concise as possible.

Minecraft version: 1.16.5
Server software: Paper
Plugin version: 2.5.0-pre1

When and why?
Always. I'm trying to put the transport on the ground, but it doesn't work. No interactions, just shows commands. I wanted to install the plugin because of a new type of equipment - boats, but it didn't work with them either.
Documentation
I don't even know what can be applied here...

This is a known bug and will be fixed in pre2:

Boats haven't been introduced yet


[master] Upgrade to latest dependencies

Cron. -knative-prow-robot
/cc knative-sandbox/networking-wg-leads
/assign knative-sandbox/networking-wg-leads
Produced via:
./hack/update-deps.sh --upgrade --release v0.21
./hack/update-codegen.sh

Details:
bumping knative.dev/networking 45b7ed1...e24bdfe:
  > e24bdfe upgrade to latest dependencies (# 350)
  > ab1235e Bump a few assorted dependencies to their latest versions (# 349)
bumping knative.dev/pkg 4b2ae07...a02dcff:
  > a02dcff Bump a few assorted dependencies to their latest versions (# 2013)

/lgtm
/approve


stm32f4: switch GPIO to new ioregs macro

Switch stm32f4 to new ioregs macro along with GPIO interface changes.
If you could throw this on hardware really quickly that would be cool since I don't have a board right now so I haven't done anything but just run the test suite which is admittedly very minimal (though it is improving).

Tested on my discovery board and it works!


frame: response, extend QueryResult Rows

At the moment row is []byte in need too be parsed to a slice of cql values

When this is fixed we can think of adding QueryResult methods like single_row and more interestingly single_row_typed possibly with generics.


Improve python executable path determination

Instead of assuming bin/python3 we now use the name of the testenv's interpreter (eg, python3.6). This should fix #7.

Codecov Report

Merging #19 into master will not change coverage.
The diff coverage is 0%.

@@         Coverage Diff          @@
##           master   #19   +/-   ##
====================================
  Coverage       0%    0%
====================================
  Files           1     1
  Lines          34    32    -2
  Branches        4     3    -1
====================================
+ Misses         34    32    -2

Impacted Files
Coverage Δ

src/tox_venv/hooks.py
0% <0%> (ø)
: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 81e416b...2cfdb76. Read the comment docs.

noticed this in #pylib -- not sure how similar the approach is, but you might find this useful

noticed this in #pylib

I did not know #pylib was a thing. Neat.

not sure how similar the approach is, but you might find this useful

Thanks. I didn't follow the code completely, but I think pre-commit is doing something slightly different. In this case, we specifically need to find the executable in the virtualenv's base/real Python installation.


add compatibility for SiteOrigin CSS plugin

https://wordpress.org/plugins/so-css/

Compatibility description meta.
title: SiteOrigin CSS
description: Enabled support for CSS files generated by SiteOrigin CSS.
constant: WP_STATELESS_COMPATIBILITY_SOCSS

@ewsopp Done


VM two NICs

@jimdial,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

#sign-off


Unable to install gpu version properly

Description

I am trying to install the gpu support for lightgbm, however after installation I still am unable to use it in python.
Would you be so kind as to assist in understanding what is going wrong.
I receive this error in python:
LightGBMError: GPU Tree Learner was not enabled in this build.
Please recompile with CMake option -DUSE_GPU=1
This seems to be because when I run the code:
make -j4
I receive this error:
make: *** No targets specified and no makefile found.  Stop.
My build file has no makefile, and I am unsure why.

Reproducible example

These are my command logs:
C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages>cd C:\PyEnvs\FYP\FYPEnvironment\Scripts
C:\PyEnvs\FYP\FYPEnvironment\Scripts>activate.bat
(FYPEnvironment) C:\PyEnvs\FYP\FYPEnvironment\Scripts>cd C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages
(FYPEnvironment) C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages>git clone --recursive https://github.com/microsoft/LightGBM
Cloning into 'LightGBM'...
remote: Enumerating objects: 29239, done.
remote: Counting objects: 100% (102/102), done.
remote: Compressing objects: 100% (77/77), done.
remote: Total 29239 (delta 50), reused 43 (delta 21), pack-reused 29137
Receiving objects: 100% (29239/29239), 20.49 MiB | 10.61 MiB/s, done.
Resolving deltas: 100% (21699/21699), done.
Submodule 'include/boost/compute' (https://github.com/boostorg/compute) registered for path 'external_libs/compute'
Submodule 'eigen' (https://gitlab.com/libeigen/eigen.git) registered for path 'external_libs/eigen'
Submodule 'external_libs/fast_double_parser' (https://github.com/lemire/fast_double_parser.git) registered for path 'external_libs/fast_double_parser'
Submodule 'external_libs/fmt' (https://github.com/fmtlib/fmt.git) registered for path 'external_libs/fmt'
Cloning into 'C:/PyEnvs/FYP/FYPEnvironment/Lib/site-packages/LightGBM/external_libs/compute'...
remote: Enumerating objects: 21733, done.
remote: Counting objects: 100% (5/5), done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 21733 (delta 1), reused 3 (delta 1), pack-reused 21728
Receiving objects: 100% (21733/21733), 8.51 MiB | 9.68 MiB/s, done.
Resolving deltas: 100% (17567/17567), done.
Cloning into 'C:/PyEnvs/FYP/FYPEnvironment/Lib/site-packages/LightGBM/external_libs/eigen'...
remote: Enumerating objects: 118861, done.
remote: Counting objects: 100% (540/540), done.
remote: Compressing objects: 100% (179/179), done.
remote: Total 118861 (delta 362), reused 534 (delta 361), pack-reused 118321
Receiving objects: 100% (118861/118861), 103.16 MiB | 15.85 MiB/s, done.
Resolving deltas: 100% (98197/98197), done.
Cloning into 'C:/PyEnvs/FYP/FYPEnvironment/Lib/site-packages/LightGBM/external_libs/fast_double_parser'...
remote: Enumerating objects: 781, done.
remote: Counting objects: 100% (180/180), done.
remote: Compressing objects: 100% (66/66), done.
remote: Total 781 (delta 124), reused 131 (delta 103), pack-reused 601
Receiving objects: 100% (781/781), 833.45 KiB | 7.38 MiB/s, done.
Resolving deltas: 100% (395/395), done.
Cloning into 'C:/PyEnvs/FYP/FYPEnvironment/Lib/site-packages/LightGBM/external_libs/fmt'...
remote: Enumerating objects: 31695, done.
remote: Counting objects: 100% (51/51), done.
remote: Compressing objects: 100% (24/24), done.
remote: Total 31695 (delta 24), reused 38 (delta 19), pack-reused 31644
Receiving objects: 100% (31695/31695), 13.84 MiB | 10.38 MiB/s, done.
Resolving deltas: 100% (21467/21467), done.
Submodule path 'external_libs/compute': checked out '36350b7de849300bd3d72a05d8bf890ca405a014'
Submodule path 'external_libs/eigen': checked out '3147391d946bb4b6c68edd901f2add6ac1f31f8c'
Submodule path 'external_libs/fast_double_parser': checked out 'ace60646c02dc54c57f19d644e49a61e7e7758ec'
Submodule 'benchmark/dependencies/abseil-cpp' (https://github.com/abseil/abseil-cpp.git) registered for path 'external_libs/fast_double_parser/benchmarks/dependencies/abseil-cpp'
Submodule 'benchmark/dependencies/double-conversion' (https://github.com/google/double-conversion.git) registered for path 'external_libs/fast_double_parser/benchmarks/dependencies/double-conversion'
Cloning into 'C:/PyEnvs/FYP/FYPEnvironment/Lib/site-packages/LightGBM/external_libs/fast_double_parser/benchmarks/dependencies/abseil-cpp'...
remote: Enumerating objects: 21051, done.
remote: Counting objects: 100% (129/129), done.
remote: Compressing objects: 100% (88/88), done.
remote: Total 21051 (delta 49), reused 112 (delta 40), pack-reused 20922
Receiving objects: 100% (21051/21051), 12.82 MiB | 10.38 MiB/s, done.
Resolving deltas: 100% (16408/16408), done.
Cloning into 'C:/PyEnvs/FYP/FYPEnvironment/Lib/site-packages/LightGBM/external_libs/fast_double_parser/benchmarks/dependencies/double-conversion'...
remote: Enumerating objects: 1358, done.
remote: Counting objects: 100% (202/202), done.
remote: Compressing objects: 100% (110/110), done.
remote: Total 1358 (delta 110), reused 157 (delta 84), pack-reused 1156
Receiving objects: 100% (1358/1358), 7.15 MiB | 9.35 MiB/s, done.
Resolving deltas: 100% (882/882), done.
Submodule path 'external_libs/fast_double_parser/benchmarks/dependencies/abseil-cpp': checked out 'd936052d32a5b7ca08b0199a6724724aea432309'
Submodule path 'external_libs/fast_double_parser/benchmarks/dependencies/double-conversion': checked out 'f4cb2384efa55dee0e6652f8674b05763441ab09'
Submodule path 'external_libs/fmt': checked out 'b6f4ceaed0a0a24ccf575fab6c56dd50ccf6f1a9'
(FYPEnvironment) C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages>cd lightgbm
(FYPEnvironment) C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\LightGBM>mkdir build
(FYPEnvironment) C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\LightGBM>cd build
(FYPEnvironment) C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\LightGBM\build>cmake -A x64 -DUSE_GPU=1 -DBOOST_ROOT=C:/local/boost_1_81_0 -DBOOST_LIBRARYDIR=C:/local/boost_1_81_0/lib64-msvc-14.3 -DOpenCL_LIBRARY="C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v12.1/lib/x64/OpenCL.lib" -DOpenCL_INCLUDE_DIR="C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v12.1/include" ..
'cmake' is not recognized as an internal or external command,
operable program or batch file.
(FYPEnvironment) C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\LightGBM\build>set PATH=C:\Program Files\CMake\bin;%PATH%
(FYPEnvironment) C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\LightGBM\build>cmake
Usage
cmake [options]
cmake [options]
cmake [options] -S  -B
Specify a source directory to (re-)generate a build system for it in the
current working directory.  Specify an existing build directory to
re-generate its build system.
Run 'cmake --help' for more information.
(FYPEnvironment) C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\LightGBM\build>cmake -A x64 -DUSE_GPU=1 -DBOOST_ROOT=C:/local/boost_1_81_0 -DBOOST_LIBRARYDIR=C:/local/boost_1_81_0/lib64-msvc-14.3 -DOpenCL_LIBRARY="C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v12.1/lib/x64/OpenCL.lib" -DOpenCL_INCLUDE_DIR="C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v12.1/include" ..
-- Building for: Visual Studio 17 2022
-- Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.22621.
-- The C compiler identification is MSVC 19.33.31630.0
-- The CXX compiler identification is MSVC 19.33.31630.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.33.31629/bin/Hostx64/x64/cl.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.33.31629/bin/Hostx64/x64/cl.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found OpenMP_C: -openmp (found version "2.0")
-- Found OpenMP_CXX: -openmp (found version "2.0")
-- Found OpenMP: TRUE (found version "2.0")
-- Looking for CL_VERSION_3_0
-- Looking for CL_VERSION_3_0 - found
-- Found OpenCL: C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v12.1/lib/x64/OpenCL.lib (found version "3.0")
-- OpenCL include directory: C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v12.1/include
-- Found Boost: C:/local/boost_1_81_0 (found suitable version "1.81.0", minimum required is "1.56.0") found components: filesystem system
-- Performing Test MM_PREFETCH
-- Performing Test MM_PREFETCH - Failed
-- Performing Test MM_MALLOC
-- Performing Test MM_MALLOC - Failed
-- Looking for inet_pton
-- Looking for inet_pton - found
-- Configuring done (8.9s)
-- Generating done (0.1s)
-- Build files have been written to: C:/PyEnvs/FYP/FYPEnvironment/Lib/site-packages/LightGBM/build
(FYPEnvironment) C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\LightGBM\build>make
make: *** No targets specified and no makefile found.  Stop.
(FYPEnvironment) C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\LightGBM\build>make -j4
make: *** No targets specified and no makefile found.  Stop.
(FYPEnvironment) C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\LightGBM\build>cmake --build . --target ALL_BUILD --config Release
MSBuild version 17.3.1+2badb37d1 for .NET Framework
Checking Build System
Building Custom Rule C:/PyEnvs/FYP/FYPEnvironment/Lib/site-packages/LightGBM/CMakeLists.txt
c_api.cpp
lightgbm_capi_objs.vcxproj -> C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\LightGBM\build\lightgbm_capi_objs.dir\Re
lease\lightgbm_capi_objs.lib
Building Custom Rule C:/PyEnvs/FYP/FYPEnvironment/Lib/site-packages/LightGBM/CMakeLists.txt
boosting.cpp
cuda_score_updater.cpp
gbdt.cpp
gbdt_model_text.cpp
gbdt_prediction.cpp
prediction_early_stop.cpp
sample_strategy.cpp
cuda_utils.cpp
bin.cpp
config.cpp
config_auto.cpp
cuda_column_data.cpp
cuda_metadata.cpp
cuda_row_data.cpp
cuda_tree.cpp
dataset.cpp
dataset_loader.cpp
file_io.cpp
json11.cpp
metadata.cpp
parser.cpp
train_share_states.cpp
tree.cpp
cuda_binary_metric.cpp
cuda_pointwise_metric.cpp
cuda_regression_metric.cpp
dcg_calculator.cpp
metric.cpp
linker_topo.cpp
linkers_mpi.cpp
linkers_socket.cpp
network.cpp
cuda_binary_objective.cpp
cuda_multiclass_objective.cpp
cuda_rank_objective.cpp
cuda_regression_objective.cpp
objective_function.cpp
cuda_best_split_finder.cpp
cuda_data_partition.cpp
cuda_histogram_constructor.cpp
cuda_leaf_splits.cpp
cuda_single_gpu_tree_learner.cpp
data_parallel_tree_learner.cpp
feature_parallel_tree_learner.cpp
gpu_tree_learner.cpp
linear_tree_learner.cpp
serial_tree_learner.cpp
tree_learner.cpp
voting_parallel_tree_learner.cpp
cl_version.h: CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 300 (OpenCL 3.0)
cl_version.h: CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 300 (OpenCL 3.0)
cl_version.h: CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 300 (OpenCL 3.0)
cl_version.h: CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 300 (OpenCL 3.0)
cl_version.h: CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 300 (OpenCL 3.0)
lightgbm_objs.vcxproj -> C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\LightGBM\build\lightgbm_objs.dir\Release\ligh
tgbm_objs.lib
Building Custom Rule C:/PyEnvs/FYP/FYPEnvironment/Lib/site-packages/LightGBM/CMakeLists.txt
Creating library C:/PyEnvs/FYP/FYPEnvironment/Lib/site-packages/LightGBM/Release/lib_lightgbm.lib and object C:/Py
Envs/FYP/FYPEnvironment/Lib/site-packages/LightGBM/Release/lib_lightgbm.exp
_lightgbm.vcxproj -> C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\LightGBM\Release\lib_lightgbm.dll
Building Custom Rule C:/PyEnvs/FYP/FYPEnvironment/Lib/site-packages/LightGBM/CMakeLists.txt
main.cpp
application.cpp
Creating library C:/PyEnvs/FYP/FYPEnvironment/Lib/site-packages/LightGBM/Release/lightgbm.lib and object C:/PyEnvs
/FYP/FYPEnvironment/Lib/site-packages/LightGBM/Release/lightgbm.exp
lightgbm.vcxproj -> C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\LightGBM\Release\lightgbm.exe
Building Custom Rule C:/PyEnvs/FYP/FYPEnvironment/Lib/site-packages/LightGBM/CMakeLists.txt
(FYPEnvironment) C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\LightGBM\build>cd C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\LightGBM\python-package
(FYPEnvironment) C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\LightGBM\python-package>setup.py install
(FYPEnvironment) C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\LightGBM\python-package>python setup.py install
running install
Starting to compile the library.
Starting to compile with MSBuild from existing solution file.
Compilation with MSBuild from existing solution file failed.
Starting to compile with Visual Studio 17 2022 (x64).
running build
running build_py
creating build
creating build\lib
creating build\lib\lightgbm
copying lightgbm\basic.py -> build\lib\lightgbm
copying lightgbm\callback.py -> build\lib\lightgbm
copying lightgbm\compat.py -> build\lib\lightgbm
copying lightgbm\dask.py -> build\lib\lightgbm
copying lightgbm\engine.py -> build\lib\lightgbm
copying lightgbm\libpath.py -> build\lib\lightgbm
copying lightgbm\plotting.py -> build\lib\lightgbm
copying lightgbm\sklearn.py -> build\lib\lightgbm
copying lightgbm_init_.py -> build\lib\lightgbm
running egg_info
creating lightgbm.egg-info
writing lightgbm.egg-info\PKG-INFO
writing dependency_links to lightgbm.egg-info\dependency_links.txt
writing requirements to lightgbm.egg-info\requires.txt
writing top-level names to lightgbm.egg-info\top_level.txt
writing manifest file 'lightgbm.egg-info\SOURCES.txt'
reading manifest file 'lightgbm.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
no previously-included directories found matching 'build'
warning: no files found matching '.txt'
warning: no files found matching '.so' under directory 'lightgbm'
warning: no files found matching 'compile\cmake\IntegratedOpenCL.cmake'
warning: no files found matching '.so' under directory 'compile'
warning: no files found matching 'compile\external_libs\compute\CMakeLists.txt'
warning: no files found matching '' under directory 'compile\external_libs\compute\cmake'
warning: no files found matching '' under directory 'compile\external_libs\compute\include'
warning: no files found matching '' under directory 'compile\external_libs\compute\meta'
warning: no files found matching '.dll' under directory 'compile\windows\x64\DLL'
warning: no previously-included files matching '.py[co]' found anywhere in distribution
warning: no previously-included files found matching 'compile\external_libs\compute.git'
writing manifest file 'lightgbm.egg-info\SOURCES.txt'
copying lightgbm\VERSION.txt -> build\lib\lightgbm
copying lightgbm\py.typed -> build\lib\lightgbm
running install_lib
copying build\lib\lightgbm\basic.py -> C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\lightgbm
copying build\lib\lightgbm\callback.py -> C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\lightgbm
copying build\lib\lightgbm\compat.py -> C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\lightgbm
copying build\lib\lightgbm\dask.py -> C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\lightgbm
copying build\lib\lightgbm\engine.py -> C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\lightgbm
copying build\lib\lightgbm\libpath.py -> C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\lightgbm
copying build\lib\lightgbm\plotting.py -> C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\lightgbm
copying build\lib\lightgbm\py.typed -> C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\lightgbm
copying build\lib\lightgbm\sklearn.py -> C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\lightgbm
copying build\lib\lightgbm\VERSION.txt -> C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\lightgbm
copying build\lib\lightgbm_init_.py -> C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\lightgbm
Installing lib_lightgbm from: ['C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\LightGBM\python-package\compile\Release\lib_lightgbm.dll', 'C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\LightGBM\Release\lib_lightgbm.dll']
copying C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\LightGBM\python-package\compile\Release\lib_lightgbm.dll -> C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\lightgbm
byte-compiling C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\lightgbm\basic.py to basic.cpython-39.pyc
byte-compiling C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\lightgbm\callback.py to callback.cpython-39.pyc
byte-compiling C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\lightgbm\compat.py to compat.cpython-39.pyc
byte-compiling C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\lightgbm\dask.py to dask.cpython-39.pyc
byte-compiling C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\lightgbm\engine.py to engine.cpython-39.pyc
byte-compiling C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\lightgbm\libpath.py to libpath.cpython-39.pyc
byte-compiling C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\lightgbm\plotting.py to plotting.cpython-39.pyc
byte-compiling C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\lightgbm\sklearn.py to sklearn.cpython-39.pyc
byte-compiling C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\lightgbm_init_.py to init.cpython-39.pyc
running install_egg_info
Copying lightgbm.egg-info to C:\PyEnvs\FYP\FYPEnvironment\Lib\site-packages\lightgbm-<IP_ADDRESS>-py3.9.egg-info
running install_scripts
Environment info
Python 3.9.13
CUDA Version 12.1
Nvidia GeForce RTX 3070
Driver Version: 531.41
Windows 11
Other things tried:
-DUSE_CUDA=1 doesnt work either
make -j4 doesnt seem to work as seen above

Sorry for the delayed response.
It's difficult to tell from what you've provided, but I think you missed a step (running cmake .. from inside the build/ directory). Please consult https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax to learn how to format text on GitHub.
Please also see https://github.com/microsoft/LightGBM/issues/5897#issuecomment-1567656771 for some more information on how to install the GPU-enabled version of the Python package.


Make --lint work with Lint/UnneededDisable

Currently, running rubocop --lint on the RuboCop source code gives a number or reports from Lint/UnneededDisable. That's not good.
By letting --lint be an alias for --only Lint, we take advantage of the logic that's already in place for handling of --only in Lint/UnneededDisable.

:+1:


Release/2.0.0

Changes Unknown when pulling 963eaf6efa5d30651b2d2c7bd0b54c0ccc0529b9 on release/2.0.0 into ** on master**.


Cannot sign in through google+

I am trying to get Google+ sign in working from the android app, but I ended up with a "Sign-in Error" from the app (Unknown error.  Please try again later) while the Facebook and username/email sign in works properly.
The server respond to the app's request with a 400 Bad request error: {"error_description": "access_token is not valid", "error": "invalid_grant"}
However, When I try to sign in with Google+ through the web interface, it works perfectly.
I did all of these :

http://edx.readthedocs.io/projects/edx-installing-configuring-and-running/en/latest/mobile.html

I followed this and set up the Google section:
GOOGLE:
   ENABLED: true
   GOOGLE_PLUS_KEY: <Client ID set up in google API credentials>

I looked the whole code up for GOOGLE_PLUS_KEY and found no usage for it.

I added the google-oauth2 backend on the LMS side: /admin/third_party_auth/oauth2providerconfig/

I'm not sure what to try next.  Is there something I'm missing?
Thanks!
UPDATE
And here's the app's log:
10-06 10:39:44.042 19154-19154/org.edx.mobile D/org.edx.mobile.social.ISocial: Scopes= oauth2:https://www.googleapis.com/auth/plus.login https://www.googleapis.com/auth/userinfo.email
10-06 10:39:44.042 19154-19154/org.edx.mobile D/org.edx.mobile.view.LoginActivity: network state changed
10-06 10:39:44.043 19154-19957/org.edx.mobile D/org.edx.mobile.social.ISocial: Fetching google oauth2 token ...
10-06 10:39:44.043 19154-19154/org.edx.mobile D/org.edx.mobile.util.NetworkUtil: Wifi is connected
10-06 10:39:44.063 19154-19154/org.edx.mobile I/Timeline: Timeline: Activity_idle id: android.os.BinderProxy@391f5fb5 time:189812637
10-06 10:39:45.113 19154-19154/org.edx.mobile D/org.edx.mobile.social.ISocial: Google oauth2: accessToken: *****
10-06 10:39:45.113 19154-19154/org.edx.mobile D/org.edx.mobile.social.SocialLoginDelegate: Google logged in; token= ****
10-06 10:39:45.157 19154-8984/org.edx.mobile D/OkHttp: --> POST https://courses.edraak.org/oauth2/exchange_access_token/google-oauth2/ HTTP/1.1
10-06 10:39:45.157 19154-8984/org.edx.mobile D/OkHttp: Content-Type: application/x-www-form-urlencoded
10-06 10:39:45.157 19154-8984/org.edx.mobile D/OkHttp: Content-Length: 189
10-06 10:39:45.157 19154-8984/org.edx.mobile D/OkHttp: User-Agent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; C6602 Build/10.7.A.0.222) Edraak/org.edx.mobile/0.8.2
10-06 10:39:45.157 19154-8984/org.edx.mobile D/OkHttp: Authorization: ******
10-06 10:39:45.157 19154-8984/org.edx.mobile D/OkHttp: access_token=****&client_id=******
10-06 10:39:45.157 19154-8984/org.edx.mobile D/OkHttp: --> END POST (189-byte body)
10-06 10:39:48.362 19154-8984/org.edx.mobile D/OkHttp: <-- 400 BAD REQUEST https://courses.edraak.org/oauth2/exchange_access_token/google-oauth2/ (3204ms)
10-06 10:39:48.362 19154-8984/org.edx.mobile D/OkHttp: Cache-Control: no-store
10-06 10:39:48.362 19154-8984/org.edx.mobile D/OkHttp: Content-Language: ar
10-06 10:39:48.362 19154-8984/org.edx.mobile D/OkHttp: Content-Type: application/json
10-06 10:39:48.362 19154-8984/org.edx.mobile D/OkHttp: Date: Thu, 06 Oct 2016 07:39:38 GMT
10-06 10:39:48.362 19154-8984/org.edx.mobile D/OkHttp: Pragma: no-cache
10-06 10:39:48.362 19154-8984/org.edx.mobile D/OkHttp: Server: nginx
10-06 10:39:48.362 19154-8984/org.edx.mobile D/OkHttp: Set-Cookie: sessionid=*******; Domain=.edraak.org; expires=Thu, 20-Oct-2016 07:39:38 GMT; httponly; Max-Age=1209600; Path=/; secure
10-06 10:39:48.363 19154-8984/org.edx.mobile D/OkHttp: Vary: Accept-Language, Cookie
10-06 10:39:48.363 19154-8984/org.edx.mobile D/OkHttp: X-Frame-Options: SAMEORIGIN
10-06 10:39:48.363 19154-8984/org.edx.mobile D/OkHttp: Content-Length: 76
10-06 10:39:48.363 19154-8984/org.edx.mobile D/OkHttp: Connection: keep-alive
10-06 10:39:48.363 19154-8984/org.edx.mobile D/OkHttp: OkHttp-Sent-Millis:<PHONE_NUMBER>778
10-06 10:39:48.363 19154-8984/org.edx.mobile D/OkHttp: OkHttp-Received-Millis:<PHONE_NUMBER>362
10-06 10:39:48.363 19154-8984/org.edx.mobile D/OkHttp: {"error_description": "access_token is not valid", "error": "invalid_grant"}
10-06 10:39:48.363 19154-8984/org.edx.mobile D/OkHttp: <-- END HTTP (76-byte body)
10-06 10:39:48.374 19154-19154/org.edx.mobile E/org.edx.mobile.view.LoginActivity: org.edx.mobile.http.HttpResponseStatusException
                                                                                at org.edx.mobile.authentication.LoginAPI.finishSocialLogIn(LoginAPI.java:112)
                                                                                at org.edx.mobile.authentication.LoginAPI.logInUsingGoogle(LoginAPI.java:100)
                                                                                at org.edx.mobile.social.SocialLoginDelegate$ProfileTask.call(SocialLoginDelegate.java:202)
                                                                                at org.edx.mobile.social.SocialLoginDelegate$ProfileTask.call(SocialLoginDelegate.java:161)
                                                                                at roboguice.util.SafeAsyncTask$SafeAsyncTaskAndroidCallable.doInBackground(SafeAsyncTask.java:163)
                                                                                at roboguice.util.AndroidCallableWrapper.doDoInBackgroundThread(AndroidCallableWrapper.java:113)
                                                                                at roboguice.util.AndroidCallableWrapper.run(AndroidCallableWrapper.java:41)
                                                                                at roboguice.util.AndroidCallable.run(AndroidCallable.java:20)
                                                                                at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:422)
                                                                                at java.util.concurrent.FutureTask.run(FutureTask.java:237)
                                                                                at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
                                                                                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
                                                                                at java.lang.Thread.run(Thread.java:818)
                                                                                at dalvik.system.VMStack.getThreadStackTrace(Native Method)
                                                                                at java.lang.Thread.getStackTrace(Thread.java:580)
                                                                                at roboguice.util.AndroidCallable.<init>(AndroidCallable.java:12)
                                                                                at roboguice.util.SafeAsyncTask$SafeAsyncTaskAndroidCallable.<init>(SafeAsyncTask.java:160)
                                                                                at roboguice.util.SafeAsyncTask.newTask(SafeAsyncTask.java:156)
                                                                                at roboguice.util.SafeAsyncTask.future(SafeAsyncTask.java:66)
                                                                                at roboguice.util.SafeAsyncTask.execute(SafeAsyncTask.java:94)
                                                                                at roboguice.util.SafeAsyncTask.execute(SafeAsyncTask.java:90)
                                                                                at org.edx.mobile.social.SocialLoginDelegate.onSocialLoginSuccess(SocialLoginDelegate.java:133)
                                                                                at org.edx.mobile.social.SocialLoginDelegate$1.onLogin(SocialLoginDelegate.java:53)
                                                                                at org.edx.mobile.social.google.GoogleOauth2$FetchGoogleTokenTask.onPostExecute(GoogleOauth2.java:117)
                                                                                at android.os.AsyncTask.finish(AsyncTask.java:636)
                                                                                at android.os.AsyncTask.access$500(AsyncTask.java:177)
                                                                                at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:653)
                                                                                at android.os.Handler.dispatchMessage(Handler.java:102)
                                                                                at android.os.Looper.loop(Looper.java:211)
                                                                                at android.app.ActivityThread.main(ActivityThread.java:5389)
                                                                                at java.lang.reflect.Method.invoke(Native Method)
                                                                                at java.lang.reflect.Method.invoke(Method.java:372)
                                                                                at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1020)
                                                                                at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:815)

Silly question! Are you using the ProdRelease variant? We have had trouble on some of the other build flavors.

Thanks @BenjiLee, that solves the issue, It just was not obvious, sorry for that.
Closing now..

It's not obvious at all!

Why does google login not work with other build flavors? Any Idea?

@Vinayak-Bhat I have not personally set it up but I think it might to do with the way the app is registered to a remote server from Google that verifies the login.

@BenjiLee  Thanks for the tip. I had indeed missed configuring android app credentials in google developer console.

I know this is pretty old issue but maybe it will help someone. It't not working on debug build because app then is using default android keystore when you change to prodRelease app starts to use your custom keystore (its path is defined in .gradle files in project). This has impact because when configuring google or facebook logging options on their websites (google api console or facebook developer console site) you giving them SHA-1 or key hash and this are values which are generated from keystore, so when you change keystore these values are not same and logging in just can't work.

@TPiotr yep that's the thing each white label project should update the SHA-1 hashes on their Google/Facebook console for debug and release for the logins to work in both situations.


PS-2089 Output files tagging with "Use file storage only"

https://keboola.atlassian.net/browse/PS-2089
Requires https://github.com/keboola/output-mapping/pull/82

Koukal jsem, ze testy na use_file_storage_only jsou jen pro Synapse/ABS workspace. To je schvalne? U jinuch to se to pouzit neda?

Koukal jsem, ze testy na use_file_storage_only jsou jen pro Synapse/ABS workspace. To je schvalne? U jinuch to se to pouzit neda?

ne, to nemá být nijak vázaný na synapse

Just not sure (as mentioned in the comment above) whether the test should be in the general suite rather than the synapse one.

I had a feeling that the test was a bit unstable, but couldn't really replicate it - and I don't see any reason why it would be (the sleeps are there), so let's see it in action.


How to draw a bezier curve by using spline?

Hello, I am a beginner using AutoCAD and this SDK. I would like to know how to write code to generate a 3rd order Bézier curve. Here is my code that can normally generate a DXF file. However, when this file is opened in CAD, it shows a straight line and CAD crashes quickly.
CadDocument doc = new CadDocument();
var curve = new Spline
{
	Degree = 3,
};
curve.FitPoints.Add(CSMath.XYZ.Zero);
curve.FitPoints.Add(new CSMath.XYZ(100.0, 100.0, 0.0));
curve.ControlPoints.Add(new CSMath.XYZ(0.0, 100.0, 0.0));
curve.ControlPoints.Add(new CSMath.XYZ(0.0, 100.0, 0.0));
doc.Entities.Add(curve);
using (DxfWriter writer = new DxfWriter("test.dxf", doc, false))
{
	writer.OnNotification += Common.NotificationHelper.LogConsoleNotification;
	writer.Write();
}

Perhaps the problem lies in that the corresponding SplineFlags have not been set, or I got confused about the differences between Knots/FitPoints/ControlPoints. Anyone can help me out?

I had mistaken the meaning of knots/control points/fit points... Now I get it OK.


App crashes when run from cmd-line (as opposed to start)

Describe the bug
App crashes when run from cmd-line (as opposed to start)
Steps to reproduce the bug

Steps to reproduce the behavior:

Create a new C# project using instructions at https://aka.ms/winui (Try WinUI3).
Use MSIX packaged app template
Launch sample app from Start Menu <- OK
Right click sample app in Task Mgr "Open File Location" to find .exe path
In cmd-prompt run app .exe - e.g. c:\Path\To\MyApp.exe <- PROBLEM app will crash
Dump show crash not in app code but in WinUI code

0d coreclr!RaiseTheExceptionInternalOnly+0x29a
0e coreclr!RealCOMPlusThrowWorker+0x31
0f coreclr!RealCOMPlusThrow+0x8d
10 coreclr!RealCOMPlusThrow+0x99
11 coreclr!TryCallMethod+0x1160f6
12 coreclr!RuntimeTypeHandle::CreateInstance+0x26d
13 System_Private_CoreLib!System.RuntimeType.CreateInstanceDefaultCtorSlow+0x48
14 System_Private_CoreLib!System.RuntimeType.CreateInstanceDefaultCtor+0xd3
15 System_Private_CoreLib!System.Activator.CreateInstance<System.__Canon>+0x3e
16 Microsoft_WinUI!WinRT.WeakLazy<_IApplicationStatics>.get_Value+0xb0
17 Microsoft_WinUI!Microsoft.UI.Xaml.Application._IApplicationStatics.get_Instance+0x38
18 Microsoft_WinUI!Microsoft.UI.Xaml.Application.Start+0x19
19 MyApp!MyApp.Program.Main+0xf2
This blocks automation and GUI Unit Testing say with something like WinAppDriver & Appium to test WinUI3 app
Expected behavior
AppSDK app launched from command prompt does not crash
Version Info
0.5.7
NuGet package version:
0.5.7

Windows app type:

UWP
Win32

Yes

Windows 11 version
Saw the problem?

Insider Build (22141.1000)
Yes

Device form factor
Saw the problem?

Desktop
Yes

Additional context

Transferring to the WindowsAppSDK repo to see about getting a message when trying to directly launch the .exe of a packaged app.

Also, I wonder if this will be supported in 1.0? The docs / roadmap seem to imply it will.
Here is how I arrived at that conclusion but feel free to correct the docs or me if I am wrong.

The roadmap https://github.com/microsoft/WindowsAppSDK/blob/main/docs/roadmap.md lists AppLifeCycle as Experimental for 0.8 and supported for 1.0
AppLifeCycle docs - https://github.com/microsoft/WindowsAppSDK/issues/111
Talk about this scenario and say things like the following

This proposal will allow users to activate any app by double-clicking it in file explorer, or typing in a path in a command window.
Must

5. In the Win32 world, it is normal to activate an app by calling CreateProcess (or ShellExecute), specifying the filesystem path to the executable file. When the user double-clicks an executable file in File Explorer, this uses that same mechanism. When the user types in an executable file name into a command window, the same thing happens
6. We will provide a converged GetActivatedEventArgs which will get all args, regardless of activation kind -- including both traditional command-line activation and also the richer UWP activation objects. This will be available to all apps.

Interestingly enough I just tried this on 0.8.1 stable - it seems to be halfway there now!

Now working in 0.8.1 - Launch from cmd-line - now works! - C:\Program Files\WindowsApps\MyApp_<IP_ADDRESS>_x64__ms1afnmeykq8t\MyAppUI\MyAppUI.exe
Still not working. Launch in explorer (for the same file path) and you get "Windows cannot access the specified device, path, or file. You may not have appropriate permissions to access the item"

You can use an app execution alias insider your appx manifest if CLI launch is crucial to your app.

AppLifecycle and unpackaged apps are supported as of 1.0

Hi @DrusTheAxe -
I see that this issue is closed, but could you possibly provide a bit more detail on your final comment "AppLifecycle and unpackaged apps are supported as of 1.0"?
Today I built a WinUI3 unpackaged app and, while I'm able to double click on it to start it from File Explorer, I cannot start it up from a cmd prompt or script.  I do see the comments above about IApplicationActivationManager, so that's something I intend to try.
But if you have any more info on unpackaged apps deployment for Windows App SDK 1.0, I would be grateful to hear them.
Thanks very much.

Today I built a WinUI3 unpackaged app

Using the 1.0 Stable release (not experimental or preview or previous releases)?
Unpackaged apps require Dynamic Dependencies and the Bootstrapper API e.g. MddBootstrapInitialize(), which were introduced in 1.0. Won't work on earlier versions (e.g. 0.8).

while I'm able to double click on it to start it from File Explorer, I cannot start it up from a cmd prompt or script

Is it a normal cmd prompt or did you Run as Administrator (aka elevated)? The latter won't work in 1.0 (elevation support for unpackaged apps is coming in 1.1)
What version of Windows are you running on?

I do see the comments above about IApplicationActivationManager

That's only relevant if you're a packaged app. If you are then your application can be launched via AAM (same as when you clikc on the StartMenu tile for your packaged app, that calls AAM to launch the packaged app).
If you're unpackaged then AAM isn't relevant. It takes as input an ApplicationUserModelID (aka AppUserModelID aka AUMID aka application identity) per your manifested definition in your appxmanifest.xml. But that only exists if you're packaged. Unpackaged apps have no appxmanifest.xml and no package or application identity, thus no AUMID and thus AAM isn't relevant. CreateProcess, ShellExecute, desktop shortcuts (.LNK) and all the other classic Win32 mechanisms apply.

Hi Howard –
I’m using Microsoft.WindowsAppSDK, Latest stable 1.0.0, pub. 11/16/2021
The .exe I’m clicking on is in this release folder of the project: \bin\x64\Release\net6.0-windows10.0.19041.0\win10-x64
If I use File Explorer, the app starts up.
If I open a cmd prompt as admin, then I get the exception.
But (and I didn’t know this before your reply) if I now open a non-admin prompt, then the app starts with no problem.
And if run a cmd script, also as non-admin, the app will open there as well.
So, you have cleared the mystery, and it seems that the Windows App SDK 1.1 release will support elevated execution.  That is good to know.
The only other question I have is when we can expect that release.  If there is a roadmap you can point me to, that would be most appreciated.
Many thanks for your very helpful and quick response!
Best regards,
Robert Cohn
Other pertinent info:
Running Windows 10 20H2, OS Build 19042.1526
Using Visual Studio 2019 version 16.11.7
From: Howard Kapustein @.>
Sent: Tuesday, February 22, 2022 11:10 PM
To: microsoft/WindowsAppSDK @.>
Cc: Cohn, Robert @.>; Comment @.>
Subject: Re: [microsoft/WindowsAppSDK] App crashes when run from cmd-line (as opposed to start) (#1062)
[EXTERNAL]
Today I built a WinUI3 unpackaged app
Using the 1.0 Stable release (not experimental or preview or previous releases)?
Unpackaged apps require Dynamic Dependencies and the Bootstrapper API e.g. MddBootstrapInitialize()https://docs.microsoft.com/windows/windows-app-sdk/api/win32/mddbootstrap/nf-mddbootstrap-mddbootstrapinitialize, which were introduced in 1.0. Won't work on earlier versions (e.g. 0.8).
while I'm able to double click on it to start it from File Explorer, I cannot start it up from a cmd prompt or script
Is it a normal cmd prompt or did you Run as Administrator (aka elevated)? The latter won't work in 1.0 (elevation support for unpackaged apps is coming in 1.1)
What version of Windows are you running on?
I do see the comments above about IApplicationActivationManagerhttps://docs.microsoft.com/en-us/windows/win32/api/shobjidl_core/nn-shobjidl_core-iapplicationactivationmanager?redirectedfrom=MSDN
That's only relevant if you're a packaged app. If you are then your application can be launched via AAM (same as when you clikc on the StartMenu tile for your packaged app, that calls AAM to launch the packaged app).
If you're unpackaged then AAM isn't relevant. It takes as input an ApplicationUserModelID (aka AppUserModelID aka AUMID aka application identity) per your manifested definition in your appxmanifest.xml. But that only exists if you're packaged. Unpackaged apps have no appxmanifest.xml and no package or application identity, thus no AUMID and thus AAM isn't relevant. CreateProcess, ShellExecute, desktop shortcuts (.LNK) and all the other classic Win32 mechanisms apply.
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/WindowsAppSDK/issues/1062#issuecomment-1048499935, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AARCGQAAQQYF3VN3DDXQGB3U4SB3LANCNFSM5AMN6YUQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID: @.***>


when adding a blob, blob name is ignored and current date used as name instead

I am added a Blob using the addFile function. the name of the file then gets set to the current date.

there doesn't appear to be any way of over-ridding this behaviour (I am using the blob method in IE11 as adding a File object not working). Is there a way to set the filename after the upload (i've tried using setMetadata on the returned File but it had no effect)
debugging you can see that the blob has a name

FilePond tests if it's an instance of File or Blob, you can turn a Blob into a file using the following method:
var file = new File([myBlob], 'name.extension');

This might not work on older browsers, I'll see if I can adjust the logic so it tests for name and only sets the name and lastModifiedDate automatically if they're missing.

Just published version 1.8.1, should work now. Please confirm.

works like a dream @rikschennink. Thanks a million!

@kevduggan Fabulous! Thanks for confirming. :-)


Rename NixOS option names: 'host' to 'listenAddress'

The idea to do this kind of renaming came from discussion in https://github.com/NixOS/nixpkgs/pull/11897. (Basically, listenAddress is a more descriptive name.)
I initially felt it was a quite good idea, but now I'm not that enthusiastic. Several programs refer to their listen address as "host" anyway (so I do see why our modules often use "host"). I'm not sure if this PR falls into the bikeshed category or not, but the job is done and here it is :-D
WARNING: Only eval checked. I cannot guarantee that I didn't make a typo or forgot to update a dependent module (if such module(s) exist in the set I'm touching).
CC @garbas.

i'm +1 on merging this but would like somebody else to also comment on this.

Personally, I am slightly worried that by merging these changes we'll wreak total havoc on people's machines with all kinds of network services being broken, etc.
Anyhow, the patch has its heart at the right place, IMHO, and I don't see how we'll ever be able to discover any omissions unless we actually use the new code ... so I figure I'll put on my flame-resistant armor and see what happens. :pray:

"flame-resistant armor" :-D (thanks @peti)


Added buttons with changing colors

Added buttons with changing colors to index.html

Thanks for the PR. Buttons look dope. It has been merged.


fix missing symlink, harden masonry osx checks

Description

Resolves macOS app bundle verification issue.
Modifies masonry macOS checks to fail if any steps fail

Type of change

[x] Bug fix
[ ] New feature
[ ] Documentation update
[ ] Other

Checklist:

[x] I have followed the style guidelines of this project.~~
[x] I have performed a self-review of my own code.~~
[x] I have commented my code where applicable.~~
- [ ] I have updated the release notes.
- [ ] I have made corresponding changes to the documentation.
- [ ] I have added debugging support to my changes.
- [ ] I have added tests that prove my fix is effective or that my feature works.
- [ ] I have confirmed new and existing unit tests pass locally with my changes.
- [ ] I have added new baselines for any new tests to the repo.
[x] I have NOT made any changes to protocol or public interfaces in an RC branch.~~
[x] I have assigned reviewers (see VisIt's PR procedures for more information).~~

placed on develop with  #17349


Enhancement better error msg for follower fe

Proposed changes
Issue Number: close #16300
Problem summary
The error log msg for the FE follower's forward to master failure is ambiguous as seen, so we should clarify it.

Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[x] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run p0

run buildall

run p0

Hi @TangSiyang2001 , Could you please use text instead of image to show the issue?
And is there any show case after your modification?

Thanks for your contribution. As a gentle reminder, please show us the error msg output after applying this fix.

Thanks for your contribution. As a gentle reminder, please show us the error msg output after applying this fix.

Maybe you can try this:

Start two fe processes, and then show frontends to see which one is is the follower

set insert into timeout short enough to let the backend fail at timeout

Send an insert into SQL to the follower fe. When it times out, you should see the error

Hi @TangSiyang2001 , Could you please use text instead of image to show the issue? And is there any show case after your modification?

Sure, I'll modify the descriptions and get the show case.

Thanks for your contribution. As a gentle reminder, please show us the error msg output after applying this fix.

Maybe you can try this:
1. Start two fe processes, and then `show frontends` to see which one is is the follower

2. set insert into timeout short enough to let the backend fail at timeout

3. Send an insert into SQL to the follower fe. When it times out, you should see the error

Thank you for the guidance, I'll work in this way.

sql client log
mysql> insert into lineorder select * from lineorder limit 10000000;
ERROR 1105 (HY000): ForwardToMasterException, msg: org.apache.doris.qe.MasterOpExecutor$ForwardToMasterException: Forward statement 21 to Master TNetworkAddress(hostname:<IP_ADDRESS>, port:9020) failed, cause: Unknown exception

fe log
2023-02-27 01:02:15,733 WARN (mysql-nio-pool-6|140) [StmtExecutor.execute():630] execute Exception. stmt[22, 9bed44b1950b4351-b003c1e13820c44e]
org.apache.doris.qe.MasterOpExecutor$ForwardToMasterException: Forward statement 22 to Master TNetworkAddress(hostname:<IP_ADDRESS>, port:9020) failed, cause: Unknown exception
        at org.apache.doris.qe.MasterOpExecutor.forward(MasterOpExecutor.java:137) ~[doris-fe.jar:1.2-SNAPSHOT]
        at org.apache.doris.qe.MasterOpExecutor.execute(MasterOpExecutor.java:73) ~[doris-fe.jar:1.2-SNAPSHOT]
        at org.apache.doris.qe.StmtExecutor.forwardToMaster(StmtExecutor.java:695) ~[doris-fe.jar:1.2-SNAPSHOT]
        at org.apache.doris.qe.StmtExecutor.execute(StmtExecutor.java:497) ~[doris-fe.jar:1.2-SNAPSHOT]
        at org.apache.doris.qe.StmtExecutor.execute(StmtExecutor.java:425) ~[doris-fe.jar:1.2-SNAPSHOT]
        at org.apache.doris.qe.ConnectProcessor.handleQuery(ConnectProcessor.java:415) ~[doris-fe.jar:1.2-SNAPSHOT]
        at org.apache.doris.qe.ConnectProcessor.dispatch(ConnectProcessor.java:557) ~[doris-fe.jar:1.2-SNAPSHOT]
        at org.apache.doris.qe.ConnectProcessor.processOnce(ConnectProcessor.java:794) ~[doris-fe.jar:1.2-SNAPSHOT]
        at org.apache.doris.mysql.ReadListener.lambda$handleEvent$0(ReadListener.java:52) ~[doris-fe.jar:1.2-SNAPSHOT]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_352]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_352]
        at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_352]

However, since the socket timeout exception will be classified as type: unkonwn exception in thrift, rather than conn timeout in reality, the result will not be conn timeout still. But If we use  conn timeout msg to cover the unkonwn exception, that may hide the msg of other unkonwn exceptions, should I enhance it further @freemandealer ?


Cache Precompiled Packages for Faster Subsequent Updates

https://github.com/Miserlou/Zappa/blob/569a576c7d4f5f3959bf7c29a53694be84b2207a/zappa/zappa.py#L422
When using precompiled packages, it downloads them each time an update is called. During development, the updates could happen frequently. So saving these precompiled packages locally between updates could speed things up.

Was there ever an open PR for this? I feel like there was and its gone..

I don't remember seeing one.
Sent from my iPhone

On Jan 27, 2017, at 4:41 PM, Rich Jones<EMAIL_ADDRESS>wrote:
Was there ever an open PR for this? I feel like there was and its gone..
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Fix db racing creation

Multiple read sessions and write sessions may be prepared in advanced at creation time especially at some journal modes like wal, etc to expedite performance.
There is a chance of read/write sessions being created at roughly the same time which invokes onCreate() simultaneously.
CREATE TABLE IF NOT EXISTS is always the best practice for such a race condition.

@jasonwyatt this should fix what Satakshi reported.

@piotrswigon this should fix what Satakshi reported.


custom_dnt_phrases field added to TranslateTextRequest

The custom_dnt_phrases field has been added to the TranslateTextRequest message in the Riva NMT  service. This enhancement allows users to specify custom phrases and their translations and also the DNT (Do Not Translate) phrases for each translation request.

let's rebase it to release/2.18.0 branch

LGTM, will wait for rest of the testing to complete before merging.


Cropper component cannot move to the edges of an image when used inside a modal.

Describe the bug
I am using react-easy-crop with mantine components. Currently I am loading the cropper component inside a mantine modal. The issue is when the cropper is loaded inside a modal, I can't move it to the edges of the selected image (it's like padded). One thing I noticed is that when I open the modal and then open the console from the same window (from right, left or bottom), the above mentioned issue goes away.
To Reproduce
Steps to reproduce the behavior:

Go to https://codesandbox.io/s/fervent-pine-xiucoj
Click on 'Open cropping dialog'
Select an image from the file system
Try to move the cropper to edges of the image

Expected behavior
Should be able to move the cropper anywhere inside the selected image, so we can crop any part form that image.

This is due to the opening animation of the modal conflicting with the internal logic of the cropper to compute its size.
When you resize the window, it makes the cropper recomputes its size so that's why it fixes the issue.
You can fix this by changing the animation to fade to avoid the cropper size to change while the modal is opening.

Thank you so much. Closing this issue because it has resolved with the given solution.

oh my thank you. i could have spent hours on this, but luckily i only spent an hour xD

facing the same issue on shadcn dialog and no way to change the animation to fade

facing the same issue on shadcn dialog and no way to change the animation to fade

The point of shading/ui is to have the full control in the component code. The animation styles are inside the DialogContent component. Check the different state-open modifiers, there are some related to zoom and translation. Removing them should fix your issue.

Thank you for your response, if we have a method like resetCropSize() then we can easily call it after dialog or model open

One way to do this is to add a key prop to the Cropper and change its value (like an incrementing number) once the modal is open.
Otherwise, you can conditionally render the Cropper only when the modal is open.

One way to do this is to add a key prop to the Cropper and change its value (like an incrementing number) once the modal is open. Otherwise, you can conditionally render the Cropper only when the modal is open.

render cropper after the dialog gets open and with some(100 milliseconds) setTimeout delay resolved this issue

A nice way to avoid a flash from empty content to the Cropper is to render a plain image by default.


Save information about reparing, constructing and the number of ship slots in localStorage

We should store them in localStorage so that the next time users open the panel, these information will be loaded immediately.

ah true, except for repairing i think. it's called often enough even on home port screen
though yes construction and max slots we do need on local


Nullable DateTimeOffset is not parsed from Unix timestamp

I need a nullable utcDateTime property in TypeSpec, so I defined it like this:
/** The Unix timestamp (in seconds) for when the run was started. */
@encode("unixTimestamp", int32)
started_at: utcDateTime | null;

The generated property does correspond to a nullable DateTimeOffset, which is great:
public DateTimeOffset? StartedAt { get; }

But then, in the generated Deserialize method, I get the following:
if (property.NameEquals("started_at"u8))
{
    if (property.Value.ValueKind == JsonValueKind.Null)
    {
        startedAt = null;
        continue;
    }
    startedAt = property.Value.GetDateTimeOffset("O");
    continue;
}

Notice how there is no conversion from Unix timestamp. In other words, instead of:
startedAt = property.Value.GetDateTimeOffset("O");

it should be this:
startedAt = DateTimeOffset.FromUnixTimeSeconds(property.Value.GetInt64());

Interestingly, if I remove the union with null in the TypeSpec, it does correctly generate the call to DateTimeOffset.FromUnixTimeSeconds (but understandably I lose the nullability of the DateTimeOffset that I need).

The Write method might have a similar issue.

The encoding information missing when @encode on a property whose type is Union.
File issue https://github.com/microsoft/typespec/issues/2969 for typespec

I have found an issue that sounds similar, but I am not sure if it is actually related:
🔗 https://github.com/Azure/autorest.csharp/issues/4677

After adopt tcgc, this issue is resolved.


refactor

Codecov Report
Attention: 19 lines in your changes are missing coverage. Please review.

Comparison is base (44749d5) 53.00% compared to head (c767438) 65.56%.
Report is 1 commits behind head on main.

Files
Patch %
Lines

game.go
30.00%
7 Missing :warning:

loader.go
41.66%
6 Missing and 1 partial :warning:

main.go
0.00%
4 Missing :warning:

cmd.go
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##             main       #2       +/-   ##
===========================================
+ Coverage   53.00%   65.56%   +12.56%
===========================================
  Files           5        7        +2
  Lines         183      212       +29
===========================================
+ Hits           97      139       +42
+ Misses         86       71       -15
- Partials        0        2        +2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Consultation about package version of diffusers and huggingface-hub

Hi, @AnthonyHuo @YixiaoWang7
Thanks for your great work!
When I try the following command python train.py --config-name=train_diffusion_transformer_hybrid_workspace, the terminal outputs——
Error executing job with overrides: []
Error in call to target 'diffusion_policy.policy.diffusion_transformer_hybrid_image_policy.DiffusionTransformerHybridImagePolicy':
TypeError("__init__() missing 1 required positional argument: 'n_tasks'")
full_key: policy

I doubt it causing by wrong package version of diffusers and huggingface-hub :(
Can you tell me which package version of diffusers and huggingface-hub did you use?
Thanks for any help!
Best,
Charlie

Hello, I encountered the same issue. I placed the checkpoint in the local directory and encountered the following error when evaluating the model:
ImportError: cannot import name ‘cached_download‘ from ‘huggingface_hub.

After searching, this error message is usually related to mismatched versions of diffusers and huggingface-hub. How did you resolve this issue?
Thank you for your help!

Hi, @xiaopangxiexyg
I solved this issue by conda install diffusers=0.11.1 -c conda-forge and pip install huggingface-hub==0.24.6 :)


Bugs

2 bugs were noticed during the game:

For some reason, the helicopter's field of view does not work.
When I pause the game and switch to another application, for some reason I hear the game and can control it. I go in, and I'm not on pause anymore
A flaw:
The hydra does not show auto-aiming and sight at all. The same with an RPG with auto-aiming

3 bug: gang territories are not shown on the map in the game menu

Are you ignoring me?

While we're at it, add rocket launcher's crosshair to Hunter/Hydra's first person camera.

By the way, when will the new version be released?

Where are the updates...


Request: Ability to write snippets in yaml.

Hi there. I searched the issue history for this repo and wasn't able to find this. Please forgive me if it already exists!
This is just a friendly request for the suggestion box: Currently, we are only able to write snippets in json5. It would be nice to have the ability to write them in yaml to make adding and arranging snippets easier.
Wouldn't it be possible to load snippets in the same way as they are currently, but if .yml, .yaml files are found, just run them through a yaml parser (e.g. js-yaml) prior to consuming in vscode?
Thanks for considering! 😄

Unsure if that will happen. I don't see a significant advantage of using yaml over json over xml

I'd love to be able to write snippets in YAML.
The advantage of YAML of JSON is ergonomics.  The multi-line snippets as arrays in fully qualified JSON are painful to write.  It would be much easier and clearer to write the snippets in YAML, particularly if multi-line strings could be parsed into the array format on \n: eg:
- React Life Cycle:
    prefix: life
    body: >
      public componentWillMount() {}
      public componentDidMount() {}
      public componentWillReceiveProps(nextProps) {}
      public shouldComponentUpdate(nextProps, nextState) {}
      public componentWillUpdate(nextProps, nextState) {}
      public componentDidUpdate(prevProps, prevState) {}
      public componentWillUnmount() {}"

vs.
{
    "React: lifecycle": {
    "prefix": "life",
    "body": [
      "public componentWillMount() {}",
      "public componentDidMount() {}",
      "public componentWillReceiveProps(nextProps) {}",
      "public shouldComponentUpdate(nextProps, nextState) {}",
      "public componentWillUpdate(nextProps, nextState) {}",
      "public componentDidUpdate(prevProps, prevState) {}",
      "public componentWillUnmount() {}"
    ]
  },
}

As I noted over at https://github.com/Microsoft/vscode/issues/15140#issuecomment-304574987 Sublime and Atom make snippet authoring much nicer (note that many people agreed with reactions)

I think supporting multi-line snippets should definitely be a priority! I can't comment on any of the issues that are specifically asking for that as they've all been locked.
Thanks for the great tool :)

If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

Please reconsider.

Dropping by to add my passionate vote to reconsider this idea.
Snippets are fundamentally meant to be written by humans. And, directly from yaml.org's landing page...
What It Is: YAML is a human friendly data serialization
  standard for all programming languages.

It was created so that people can more easily deal with its syntax, which is the opposite of json or xml. I hope this gets a proper reconsideration.

I think this should be reopened / reconsidered. It's pretty hard to manage larger snippets when you have to keep worrying about putting quotes around each line of a snippet. A hacky alternative is to use something like this tool, but that just makes it hard in a different kind of way.


Mr learning speech

Docs Build status updates of commit 755deea:
:warning: Validation status: warnings

File
Status
Preview URL
Details

mixed-reality-docs/mrlearning-speechSDK-ch3.md
:warning:Warning
View
Details

mixed-reality-docs/mrlearning-speechSDK-ch4.md
:warning:Warning
View
Details

mixed-reality-docs/images/module4chapter1step10im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter1step11im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter1step12im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter1step13im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter1step15im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter1step18im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter1step19im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter1step1im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter1step20im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter1step21im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter1step22im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter1step3im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter1step4im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter1step7im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter1step9im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter2exampleim.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter2step1im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter2step2im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter3exampleim.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter3noteim.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter3step1im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter3step2im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4note2im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4noteim.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4step10im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4step11im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4step12im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4step13im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4step14aim.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4step14bim.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4step15im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4step16im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4step17im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4step19im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4step1aim.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4step1bim.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4step1cim.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4step20im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4step21im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4step22im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4step23im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4step24im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4step2im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4step3aim.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4step3bim.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4step6im.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4step8aim.PNG
:white_check_mark:Succeeded
View

mixed-reality-docs/images/module4chapter4step8bim.PNG
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.

mixed-reality-docs/mrlearning-speechSDK-ch3.md

Line 29: [Warning] Invalid file link:(~/placeholderlink).

mixed-reality-docs/mrlearning-speechSDK-ch4.md

Line 13: [Warning] Invalid file link:(~/linkgoeshere).
Line 133: [Warning] Invalid file link:(~/placeholderlink).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add DateRestrictions

Closes #92
Hey @fschulze :) Do you think you could do a round of code review ? Also, I haven't taken the time to try the new macaroons against (Test)PyPI, so if you want to give it a try, feel free :) (you can generate an unscoped token on TestPyPI, then use this PR to create 2 tokens with time restrictions: one that includes now and one that excludes now. PyPI should let you upload with the first one and not with the 2nd one)
Checklist:

[x] Tests

[ ] (not applicable?)

[x] Documentation

[ ] (not applicable?)

Wow, that was fast! I'm not sure when I will get to testing, as I'll be unavailable most of the time from June 1st to 15th.

Ok, then I'll do it on my side :)

d = datetime.datetime.now(tz=datetime.timezone.utc)
original_token = os.environ["TOKEN"]

TOKEN_A = pypitoken.Token.load(original_token).restrict(not_before=d, not_after=d+datetime.timedelta(days=1)).dump()

TOKEN_B = pypitoken.Token.load(original_token).restrict(not_before=d-datetime.timedelta(days=2), not_after=d-datetime.timedelta(days=1)).dump()

$ twine upload -r testpypi --verbose dist/ewjoachim-test-0-1000.tar.gz -u __token__ -p $TOKEN_A
Using configuration from /Users/joachim/.pypirc
Uploading distributions to https://test.pypi.org/legacy/
  dist/ewjoachim-test-0-1000.tar.gz (1.2 KB)
username set by command options
password set by command options
username: __token__
password: <hidden>
Uploading ewjoachim-test-0-1000.tar.gz
100%|████████████████████████████████████████████████████████████████████████████████████████| 3.68k/3.68k [00:00<00:00, 4.74kB/s]

View at:
https://test.pypi.org/project/ewjoachim-test-0/1000/

$ twine upload -r testpypi --verbose dist/ewjoachim-test-0-1000.tar.gz -u __token__ -p $TOKEN_B
Using configuration from /Users/joachim/.pypirc
Uploading distributions to https://test.pypi.org/legacy/
  dist/ewjoachim-test-0-1000.tar.gz (1.2 KB)
username set by command options
password set by command options
username: __token__
password: <hidden>
Uploading ewjoachim-test-0-1000.tar.gz
100%|████████████████████████████████████████████████████████████████████████████████████████| 3.68k/3.68k [00:00<00:00, 6.83kB/s]
Content received from server:

  <title>403 Invalid API Token: InvalidMacaroonError('invalid macaroon')</title>

403 Invalid API Token: InvalidMacaroonError('invalid macaroon')

  Access was denied to this resource.

Invalid API Token: InvalidMacaroonError('invalid macaroon')

HTTPError: 403 Forbidden from https://test.pypi.org/legacy/
Invalid API Token: InvalidMacaroonError('invalid macaroon')

Seems it's working as expected !

I hope it's ok, but I left a few comments on the commit introducing this. Nice work !


two primarykey one value default find first value

Q
A

Is bugfix?
yes/no

New feature?
yes/no

Breaks BC?
yes/no

Tests pass?
yes/no

Fixed issues
comma-separated list of tickets # fixed by the PR, if any

when table have two primarykey,I can't get model with restful url like this http://www.a.com/api/orders/5
bootstrap set 'GET api/orders/' => 'appapi/orders/view',

when table have two primarykey,I can't get model with restful url like this http://www.a.com/api/orders/5
bootstrap set 'GET api/orders/' => 'appapi/orders/view',

of course not, because you need to specify both parts of the key to get a valid result. specifying only one part is ambiguous and may return a wrong record. Can not accept this change.


More Social Media Links via Sidebar

Apologies if this should be straightforward, I'm new to Jekyll and playing around with your example project, just trying to quickly determine if I can add more social media links to the side navigation bar besides the email, twitter, github and rss feed that come as the default.  For instance, modifying the config.yml to the following:
author:
name: Dugan Nash
twitter: Towlette_Pettetucci
facebook: Towlette_Pettetucci
picture: https://api.adorable.io/avatars/285/johndoe.png
twitter_username: Towlette_Pettetucci
github_username: Towlette_Pettetucci
facebook_username: Towlette_Pettetucci
logo: /assets/icons/basically-basic-logo-light.svg
does not add a facebook link, so I am assuming there is no support for adding more links to the sidebar through the config, and I would have to write a rule in somewhere to populate the navigation sidebar with a facebook icon and link?  Could anyone point me in the correct direction for accomplishing this?

That's correct, it only supports Twitter and GitHub.
I built it as a replacement for Jekyll's default theme Minima, and that's all they include. If you want to add additional social networking links you can edit _includes/contact-list.html.
The icons are built using SVG so you'd need to add those as well.


runQuery() fails with timeout after some time of inactivity

Environment details

OS: Linux 4.15.0-64-generic #73~16.04.1-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux
Node.js version: v10.16.0
npm version: 6.11.3
@google-cloud/datastore version: 4.3.0

Steps to reproduce

Simple app mixing express and datastore:

"use strict";
const { Datastore } = require("@google-cloud/datastore");
const express = require("express");
const ds = new Datastore();
const app = express();
app.disable("etag");
app.set("trust proxy", true);
app.get("/", (req, res, next) => {
const q = ds.createQuery("Tasks").order("taskName");
return ds.runQuery(q).then((data) => {
console.log("Callback from runQuery()");
let entities = data[0];
return res.json(entities);
}).catch((err) => {
console.log("runQuery() failed:", err.message);
return next(err);
});
});
// Basic 404 handler
app.use((req, res) => {
res.status(404).send("Not Found");
});
// Basic other error handler
app.use((err, req, res, next) => {
console.log("500 Error:", err);
res.status(500).send(err.message || "Something is broken!");
});
if (module === require.main) {
// Start the server
const server = app.listen("8080", () => {
const port = server.address().port;
console.log(App listening on port ${port});
});
}
module.exports = app;

Start it as usual:
node app

Open in a browser:
http://localhost:8080/

You will get a list of entities.

Wait for more than 5 minutes. Do not stop the webapp and do not use the webapp.

Open in a browser again:
http://localhost:8080/

No results and after some time (very long) you will get the following errors:

runQuery() failed: Retry total timeout exceeded before any response was received
500 Error: { Error: Retry total timeout exceeded before any response was received
at repeat (./node_modules/google-gax/build/src/normalCalls/retries.js:80:31)
at Timeout.setTimeout [as _onTimeout] (./node_modules/google-gax/build/src/normalCalls/retries.js:113:25)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10) code: 4 }
Notes: it's repeatable in the cloud and running locally (all the environment details for the local run).
Thanks!

I'm facing the same issue with the exactly 5 minutes of inactivity...

using datastore 4.1.4 or under does not reproduces the bug, to be sure that you are using the right version do:
npm cache clean
rm -rf node_modules/ package-lock.json

Change your package json to use exactly version like:
{
    "dependencies": {
      "@google-cloud/datastore": "4.1.4",
    }
}

Remember that it must be "@google-cloud/datastore": "4.1.4", and not: "@google-cloud/datastore": "^4.1.4".
And finally, install packages with:
npm ci

do not use npm install

Can you do the test above, @rescan-dl ?

using datastore 4.1.4 or under does not reproduces the bug, to be sure that you are using the right version do:
npm cache clean
rm -rf node_modules/ package-lock.json

Change your package json to use exactly version like:
{
    "dependencies": {
      "@google-cloud/datastore": "4.1.4",
    }
}

Remember that it must be "@google-cloud/datastore": "4.1.4", and not: "@google-cloud/datastore": "^4.1.4".
And finally, install packages with:
npm ci

do not use npm install

well, at first time without package.lock, you must run npm install.

@dann95 I know that the older versions don't have the bug. Our other not-very-active webapp uses v4.1.3 without this problem.
Instead of library downgrading I decided to use a different work-around. I moved the global variable
const ds = new Datastore();
to the local scope for every HTTP request.

@rescan-dl are you using another @google-cloud libraries ?

@dann95 Yes, storage and pubsub.

in the company i work we are facing the same issue, and we use a lot of gcloud libs, such as storage, speech, stack driver.. and we see that also fixing datastore lib version we can still have same bug..

I can observe the same issue in my project. After 4-5 minutes of inactivity, my queries fails on runQuery().
"@google-cloud/datastore": "^4.3.0",
"@google-cloud/error-reporting": "^1.1.2",
"@google-cloud/storage": "3.3.1",

Moving "new Datastore()" solves the problem but I don't think that this is clean approach. Or maybe it is?
Thanks!

@Kamil7S ofc it isn't a nice idea, since datastore have a slow connection time.

@mrksbnch as we tested 4.1.4, but are you sure about the version u are installing ? like no ^ in package.json, cache clean, package-lock.json removed?

@alexander-fenster do you think this might be related to some of the gprc-js issues we've been seeing recently?

@bcoe Yes, it seems pretty much like that. All the issues that look like "it's all going well but then after some time everything stops working" point to https://github.com/grpc/grpc-node/issues/1064 at this time.
@rescan-dl @dann95 @mrksbnch Can you folks try it with the latest (released just minutes ago) @grpc/grpc-js v0.6.6 (just rm -rf node_modules package-lock.json && npm install), and let us know if it helps?  If it still fails, running your code with
export GRPC_TRACE=all
export GRPC_VERBOSITY=DEBUG

and sharing the results with us will be really appreciated.

@alexander-fenster I'm happy to test that. However, I'm not totally sure how the @grpc/grpc-js is related to the @google-cloud/datastore package. We currently only have a @google-cloud/datastore entry in the package.json file. Do we need to add @grpc/grpc-js separately?
@dann95 Yes, we updated package.json (without ^), package-lock.json and no cache. However, we were still seeing errors. We can probably give it a try again.

@alexander-fenster do you think this might be related to some of the gprc-js issues we've been seeing recently?

for sure, a developer from our team fixed the problem migrating from npm to yarn and set:
"resolutions": {
    "@grpc/grpc-js": "0.5.0",
    "google-auth-library": "5.2.2"
  }

@alexander-fenster I'm happy to test that. However, I'm not totally sure how the @grpc/grpc-js is related to the @google-cloud/datastore package. We currently only have a @google-cloud/datastore entry in the package.json file. Do we need to add @grpc/grpc-js separately?
@dann95 Yes, we updated package.json (without ^), package-lock.json and no cache. However, we were still seeing errors. We can probably give it a try again.

Well, also if we lock the version of datastore, it dependencies are declarated with "^" so we need to configure a resolution with npx or use yarn...
reference: https://github.com/googleapis/nodejs-datastore/blob/8e026af47b3232ca86c48e0b53ec14a0ea05463c/package.json#L51

@bcoe Yes, it seems pretty much like that. All the issues that look like "it's all going well but then after some time everything stops working" point to grpc/grpc-node#1064 at this time.
@rescan-dl @dann95 @mrksbnch Can you folks try it with the latest (released just minutes ago) @grpc/grpc-js v0.6.6 (just rm -rf node_modules package-lock.json && npm install), and let us know if it helps? If it still fails, running your code with the following environment variables set:
export GRPC_TRACE=all
export GRPC_VERBOSITY=DEBUG

and sharing the results with us will be really appreciated.

We will try.

@dann95 Thanks, I edited my previous comment: Adding @grpc/grpc-js separately (v0.6.6) seems to work for us thus far.

Using
"resolutions": {
    "@grpc/grpc-js": "^0.6.6"
}

as a temporary fix, works for me too.

Since v0.6.6 is the latest one, just doing rm -rf node_modules package-lock.json && npm install (for those of you who use npm) also brings the latest dependencies to you, including @grpc/grpc-js v0.6.6.
Thank you folks for confirming that it works for you!

working fine @alexander-fenster

@rescan-dl thanks for your patience, and for bringing this to our attention. Let us know if 0.6.6 also does the trick for you, and we can close this issue :+1:

@alexander-fenster "just doing rm -rf node_modules package-lock.json && npm install" worked for me. I'm closing the issue.


Resolve confusion around preview build versioning

In our announcements for Preview releases, we specify the build version in the tag and announcement text. However, this build version is the version of the Microsoft build which is not necessarily the same version that you would get as a result of a source-built SDK. This leads to confusion because the build versions do not align. See https://github.com/dotnet/source-build/discussions/3504#discussioncomment-6192224.
The reason for why the build versions don't align is due to Arcade behavior and described here: https://github.com/dotnet/source-build/issues/3248.
We should investigate ways to resolve this confusion and implement a solution.

Using stable versioning for our preview releases would also resolve this issue. cc @mmitche

Yes agreed that this would solve this problem (at least from an outward branding perspective)


#254: Just a couple of typo fixes

Refer to issue #254.
Minor error log typos that keep popping up in my build log.

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

@dostiharise Thank you for signing the Contributor License Agreement!


UAC tool added to Evidence Collection section

Signed-off-by: Thiago Lahr<EMAIL_ADDRESS>

Hey @tclahr
Looks like interesting project, but let's give it some time to gain traction (some github stars) before we add it to the list...


Webmail

Webmail client per instance

Something like https://roundcube.net/screens/

Push til after 1.0

moved to roadmap


feature/dot_header_colors

Should cover:
Task header color does not match task dot color #160
Supply does not change dot or header color according to status. #161

LGTM, thanks @kristysnet!