"time" be overwritten by metadata "time" when use Elixir 1.10 with GoogleCloudLoggingFormatter

First of all, thank you for this library!!
About the title. Elixir 1.10 integrate with Erlang's logger. And Erlang's logger has metadata "time" what has unixtime(microsecond) variable.
https://elixir-lang.org/blog/2020/01/27/elixir-v1-10-0-released/
https://erlang.org/doc/man/logger.html#timestamp-0

This allows us to provide tighter integration with Erlang/OTP’s new logger
This means that the logger level, logger metadata, as well as all log messages are now shared between Erlang and Elixir APIs.

google cloud logger formatter merge metadata and logger_json values, So logger_json's "time" be overwritten by metadata "time" value.
Is it the correct behavior?
My understanding that logger_json be expected "time" value is milliseconds.
I confirmed the behavior as below.
code
https://github.com/w1mvy/logger_json/commit/39395026d75b7f5fe4074d0d0b3eeb16d1faec8d
Elixir 1.9
%{"logging.googleapis.com/sourceLocation" => %{"file" => "/home/w1mvy/ghq/github.com/Nebo15/logger_json/test/unit/logger_json_google_test.exs", "function" => "Elixir.LoggerJSONGoogleTest.test logs binary messages/1", "line" => 59}, "message" => "hello", "severity" => "DEBUG", "time" => "2020-08-05T21:54:34.233Z"}

Elixir 1.10
%{"domain" => ["elixir"], "logging.googleapis.com/sourceLocation" => %{"file" => "/home/w1mvy/ghq/github.com/Nebo15/logger_json/test/unit/logger_json_google_test.exs", "function" => "Elixir.LoggerJSONGoogleTest.test logs binary messages/1", "line" => 59}, "message" => "hello", "severity" => "DEBUG", "time" =><PHONE_NUMBER>401128}

In my project,  change the order of merge. But, this change may be breaking change for some people who use metadata "message", "time", "severity".
https://github.com/w1mvy/logger_json/commit/dee65e40dff4cbae93d399d5e558fbfbd5c043b1
If this change is no problem, I can create pull request.

I think that change should not be a problem, but maybe a safer move, for now, would be to simply ignore :time key in the metadata in GCL logger. This way even if somebody has a hack that uses that "feature" the change still won't break their code.

@AndrewDryga thanks your comment.

for now, would be to simply ignore :time key in the metadata in GCL logger.

I created pull request with this change.
https://github.com/Nebo15/logger_json/pull/51


[BUG] ValueError in aCompCor

Running ds011
nipypecli crash /scratch/03843/crn_plab/fmriprep-ohbm-2/work/ds000011_R2.0.1/out/log/crash-20161215-131711-crn_plab-aCompCor.a4-a96c4457-b951-4f01-ab20-106caa44ba90.pklz

File: /scratch/03843/crn_plab/fmriprep-ohbm-2/work/ds000011_R2.0.1/out/log/crash-20161215-131711-crn_plab-aCompCor.a4-a96c4457-b951-4f01-ab20-106caa44ba90.pklz
Node: workflow_enumerator.09.ConfoundDiscoverer.aCompCor.a4
Working directory: /scratch/03843/crn_plab/fmriprep-ohbm-2/work/ds000011_R2.0.1/work/workflow_enumerator/09/ConfoundDiscoverer/_epi_..scratch..03843..crn_plab..fmriprep-ohbm-2..ds000011_R2.0.1..sub-09..func..sub-09_task-Singletaskweatherprediction_run-02_bold.nii.gz/aCompCor

Node inputs:

components_file = acompcor.tsv
generate_report = True
header = aCompCor
ignore_exception = False
mask_file = /scratch/03843/crn_plab/fmriprep-ohbm-2/work/ds000011_R2.0.1/work/workflow_enumerator/09/ConfoundDiscoverer/_epi_..scratch..03843..crn_plab..fmriprep-ohbm-2..ds000011_R2.0.1..sub-09..func..sub-09_task-Singletaskweatherprediction_run-02_bold.nii.gz/combine_rois/logical_or.nii.gz
num_components = 6
out_report = report.html
realigned_file = /scratch/03843/crn_plab/fmriprep-ohbm-2/work/ds000011_R2.0.1/work/workflow_enumerator/09/EPI_HMC/_epi_..scratch..03843..crn_plab..fmriprep-ohbm-2..ds000011_R2.0.1..sub-09..func..sub-09_task-Singletaskweatherprediction_run-02_bold.nii.gz/EPI_hmc/sub-09_task-Singletaskweatherprediction_run-02_bold_mcf.nii.gz
regress_poly_degree = 1
use_regress_poly = True

Traceback:
Traceback (most recent call last):
  File "/work/01329/poldrack/lonestar/software_lonestar5/crn-agave/anaconda/lib/python2.7/site-packages/nipype-0.13.0_gff36588.dev-py2.7.egg/nipype/pipeline/plugins/multiproc.py", line 52, in run_node
    result['result'] = node.run(updatehash=updatehash)
  File "/work/01329/poldrack/lonestar/software_lonestar5/crn-agave/anaconda/lib/python2.7/site-packages/nipype-0.13.0_gff36588.dev-py2.7.egg/nipype/pipeline/engine/nodes.py", line 367, in run
    self._run_interface()
  File "/work/01329/poldrack/lonestar/software_lonestar5/crn-agave/anaconda/lib/python2.7/site-packages/nipype-0.13.0_gff36588.dev-py2.7.egg/nipype/pipeline/engine/nodes.py", line 477, in _run_interface
    self._result = self._run_command(execute)
  File "/work/01329/poldrack/lonestar/software_lonestar5/crn-agave/anaconda/lib/python2.7/site-packages/nipype-0.13.0_gff36588.dev-py2.7.egg/nipype/pipeline/engine/nodes.py", line 607, in _run_command
    result = self._interface.run()
  File "/work/01329/poldrack/lonestar/software_lonestar5/crn-agave/anaconda/lib/python2.7/site-packages/nipype-0.13.0_gff36588.dev-py2.7.egg/nipype/interfaces/base.py", line 1085, in run
    runtime = self._run_wrapper(runtime)
  File "/work/01329/poldrack/lonestar/software_lonestar5/crn-agave/anaconda/lib/python2.7/site-packages/nipype-0.13.0_gff36588.dev-py2.7.egg/nipype/interfaces/base.py", line 1033, in _run_wrapper
    runtime = self._run_interface(runtime)
  File "/work/01329/poldrack/lonestar/software_lonestar5/crn-agave/anaconda/lib/python2.7/site-packages/niworkflows-0.0.4a0-py2.7.egg/niworkflows/common/report.py", line 45, in _run_interface
    ReportCapableInterface, self)._run_interface(runtime)
  File "/work/01329/poldrack/lonestar/software_lonestar5/crn-agave/anaconda/lib/python2.7/site-packages/nipype-0.13.0_gff36588.dev-py2.7.egg/nipype/algorithms/confounds.py", line 361, in _run_interface
    u, _, _ = linalg.svd(M, full_matrices=False)
  File "/work/01329/poldrack/lonestar/software_lonestar5/crn-agave/anaconda/lib/python2.7/site-packages/scipy/linalg/decomp_svd.py", line 112, in svd
    compute_uv=compute_uv, full_matrices=full_matrices)
  File "/work/01329/poldrack/lonestar/software_lonestar5/crn-agave/anaconda/lib/python2.7/site-packages/scipy/linalg/lapack.py", line 470, in _compute_lwork
    wi = routine(*args, **kwargs)
ValueError: On entry to DGESDD parameter number 10 had an illegal value
Interface ACompCorRPT failed to run.

I've got this in DS102 too

ds107 as well sub-01_task-onebacktask_run-02,  sub-45_task-oneback_run-02

Some bad values are sneaking into the mask

Happening in ds115 and ds119 too.

One subject on ds116.

Many of these errors were caused by coregistration issues (hopefully) solved in #294. Some could be related to #296.

After fixing the coregistration issues there is only one error, which turns out to be due to the epi file looking like this:

This is the same subject as reported in https://github.com/poldracklab/fmriprep/issues/291.
If you can confirm that this is the only case among the tested datasets we can close this issue.

I don't think this is still happening. I'll close it and then reopen if we see it again.


Minor fixes

A few things that bugged me.
Nothing too substantial, just make sure you're porting all commands to slash commands since discord's gonna start deprecating features that don't rely on that.

Seems good, Thanks for your contribution!


Unable to augment exported function from a module with a overload signature

TypeScript Version:  2.7.1

Search Terms: augment module function export
Code
// imports.ts
export function test(arg: number): any;
export function test(arg: number): any {
  return arg.toString();
}

// augmentations.ts
import { test } from './imports';

declare module './imports' {
  function test(arg: string): any; //  TS2384: Overload signatures must all be ambient or non-ambient.
}

test('foo');

Expected behavior: test function from imports.ts is augmented with overloaded string signature.
Actual behavior: TS2384 Error
I tried to hunt down this issue as I thought it previously existed but after numerous pages of other unrelated issues I gave up the hunt. I believe this issue has been around since the beginning of module augmentations, and perhaps it is by design. I suspect the problem is that there is no way to define a static module function as a module augmentation.
I have run into use cases where this ability would be very useful. Typically when a particular library lags behind in updating their type declarations, but deficiencies in the typings are not declared within a class or interface scope. The solution is typically to just hold back on updating typescript, until the library is properly updated (which can sometimes be long wait depending on how active the library is).

A work around for this issue has been determined to work for typescript 2.6.x+ by using // @ts-ignore above the augmentation line. This will tell the compiler to ignore the issue, but the typing system will still merge the overloaded signature.

I don't think this should be reported on TS... Rather at your 'ix/iterable/concat' package repository, following our discussion on TypeScript gitter

there will be a separate pull request for the ix module, their typings are incorrect and need to be patched. This issue is to address the inability to augment static function exports from a module.

I am not seeing this error locally, what am i missing?
c:\test\21566>type a.ts
import { test } from './a';

declare module './a' {
  function test(arg: string): any; //  TS2384: Overload signatures must all be ambient or non-ambient.
}

test('foo');
c:\test\21566>type b.ts
export function test(arg: number): any;
export function test(arg: number): any {
  return arg.toString();
}
c:\test\21566>tsc --v
Version 2.7.1

c:\test\21566>tsc

c:\test\21566>echo %ERRORLEVEL%
0

@mhegazy do you have those type commands reversed?
$ cat imports.ts
export function test(arg: number): any;
export function test(arg: number): any {
  return arg.toString();
}

$ cat augmentations.ts
import { test } from './imports';

declare module './imports' {
  function test(arg: string): any; //  TS2384: Overload signatures must all be ambient or non-ambient.
}

test('foo');

$ ./node_modules/.bin/tsc --v
Version 2.7.1

$ ./node_modules/.bin/tsc augmentations.ts
src/types/augmentations.ts(4,12): error TS2384: Overload signatures must all be ambient or non-ambient.
src/types/augmentations.ts(4,12): error TS2394: Overload signature is not compatible with function implementation.

ah sorry, but that seems right to me.. augmentations is meant to change the behavior of something you can not control, e.g. a library you are importing, but if you control your function, why not add an overload to it?

Yea, sorry if it wasn't clear originally. The example is just proof of bug, in the use case I encountered this bug i don't have direct control of the source that requires the augmentation.

So was it in a .ts file or in in a.d.ts file?

it is a .ts file, but that's only because the project has a very strange setup and exposes its types through the ts source. But this is all for a module fetched via npm.

Then that is a bug for the declaration file really. I would recommend filing this on https://github.com/ReactiveX/IxJS/issues instead.

i think they are two separate issues. a broken module with bad type declarations, and the bug with the typescript compiler that prevents augmenting static function exports.

The idea here is to avoid undesired merges that might lead to surprises. and the rule is all overloads must look the same, e.g. can not have one exported and one not, similarly, can not have one ambient and one not.. again the rational is , if you are implementing the function, how can some other entity tell you what parameter types your function supposed to handle..
Faulty declaration files, are just that, faulty declaration files, and the right fix is to fix them not to patch over them.

i agree with your statements, but what happens when fixing them isn't possible (not that this is the case here). It just seems strange for this case given that if the compiler ignores the issue, the typing system is perfectly happy with the augmentation. Additionally, there is currently (afaik) no way to augment a static exported function from a module, i'm guessing your argument here is that you should never need to given proper type declarations.

i'm guessing your argument here is that you should never need to given proper type declarations.

not exactelly. I can disable the check.. the question is what is the value of the check. we originally added it to avoid surprises when you have a function with the same name as a global/imported function that you do not know is merging with your function. removing the check makes your scenario work, but also makes that issue go unchecked.
I am arguing that fixing one declaration package and keeping the check in place, in aggregate, has higher value for all language users.

yea that makes sense. My argument is more about not limiting ability to monkey patch dependencies that have gone stale and don't receive timely updates. Maybe the real answer here is to simply use the @ts-ignore directive for the few cases where this is relevant, as I am currently doing.

I think this issue must be closed at this stage of discussion, since... TypeScript is very ~reluctant~ prudent when it comes to bug-prone features.
The problem is real, removing it is error-prone. Thanks, //@ts-ignore can be a workaround.

@mhegazy feel free to close this at your leisure, I think we have come to a consensus for now.

The External label is really appropriate ? Since the issue have two aspect of which one is external

I came across this problem too.

One of this modules has the following signature:
export function createReducer<S, M = {}>(
  initialState: S,
  mapping: { [type: string]: (state: S, payload: any, meta: M) => S }
): any

Then, I created a redux-middleware which injects a meta data to actions. When using that middleware I want to overload the createReducer definition to specify the generic M. That way, every other module which uses the createReducer method will be given with a more specific type definition.
declare module "./helpers" {
  // @ts-ignore https://github.com/Microsoft/TypeScript/issues/21566
  function createReducer<S, M extends ActionMeta = ActionMeta>(
    initialState: S,
    mapping: { [type: string]: (state: S, payload: any, meta: M) => S }
  ): any;
}

By doing that I came across the ts error TS2384: Overload signatures must all be ambient or non-ambient.
It's true that I can control that helpers module, since it's a ts file in my source code, however, ideally, I want to keep that file agnostic so that, in the future, i could share among others projects.


./scripts/installErizo.sh run error

Double check that installUbuntuDeps.sh didn't returned any errors

@kekkokk  I've tried several times, or I can't do it

what version of ubuntu are you using?
'Cause currently only 14 is supported.
If you want to install in a 16 ubuntu you need some tweaking:
https://github.com/lynckia/licode/pull/1210

@kekkokk The version of ubuntu is 14.04


 perf(@angular-devkit/build-angular): cache polyfills virtual module result

This commit adds caching to the polyfills virtual modules to avoid module resolutions on rebuilds which can take up to 3 seconds in some cases. Whilst these are done async, these can still slow down the build slightly due to IO limits.

Note: this PR is on top of https://github.com/angular/angular-cli/pull/26045


Cache users

Dbeaver uses multiple connections at the same time, leading to multiple requests to Vault and multiple temporary users created.
Additionally, this is a problem for read replica databases that may not process new users in time and reject the authentication

https://developer.hashicorp.com/vault/docs/concepts/lease

Vault response is
curl --header "X-Vault-Token: aaaaaaa" https://example.com/v1/database/creds/readonly

{
    "request_id": "43f5a069-a414-b4df-d49b-242161516dfe",
    "lease_id": "zzzzzzzz",
    "renewable": true,
    "lease_duration": 1209600,
    "data": {
        "password": "yyyyyy",
        "username": "xxxxxx"
    },
    "wrap_info": null,
    "warnings": null,
    "auth": null
}

fixed in https://github.com/premium-minds/dbeaver-vault/pull/12


Fade slider

Hi,
As in slick there was a possibility to make the slider a fade slider, I was wondering how/if I could do the same in nuka ?
Thanks

Up

This would be ideal.


Invoice listeners

This introduces asynchronous listeners for many wallet backends (OpenNode, LNPay, LndRest, Spark, CLightning, LndWallet) and uses that to power webhooks on lnurlp.
It also fixes inconsistencies in LndRest and other minor issues, introduces httpx (we can remove requests later, as httpx replaces it very well and it has both sync and async modes), trio (I tried to do it with asyncio, please believe me, but it seems trio is better overall), quart_trio and changes specific dependencies for LndWallet (from lnd-grpc to lndgrpc and purerpc).
It is massive, but I think it is for the good.

Codecov Report

Merging #101 into master will decrease coverage by 1.71%.
The diff coverage is 24.11%.

@@            Coverage Diff             @@
##           master     #101      +/-   ##
==========================================
- Coverage   34.79%   33.08%   -1.72%
==========================================
  Files          27       27
  Lines        1253     1472     +219
==========================================
+ Hits          436      487      +51
- Misses        817      985     +168

Impacted Files
Coverage Δ

lnbits/core/views/api.py
38.23% <0.00%> (+4.05%)
:arrow_up:

lnbits/core/views/generic.py
34.14% <0.00%> (ø)

lnbits/db.py
31.81% <0.00%> (-3.19%)
:arrow_down:

lnbits/wallets/clightning.py
20.27% <10.20%> (-10.50%)
:arrow_down:

lnbits/wallets/lndrest.py
18.57% <10.86%> (-0.73%)
:arrow_down:

lnbits/wallets/lndgrpc.py
23.91% <17.33%> (-4.00%)
:arrow_down:

lnbits/wallets/opennode.py
25.75% <20.45%> (+0.75%)
:arrow_up:

lnbits/core/models.py
67.53% <25.00%> (-4.94%)
:arrow_down:

lnbits/wallets/spark.py
23.37% <26.66%> (-0.51%)
:arrow_down:

lnbits/wallets/lnpay.py
36.36% <32.14%> (-6.88%)
:arrow_down:

... and 8 more

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 e2f6c20...6d5fb22. Read the comment docs.

ACK

Wow, nice work, although got a few bugs
I tested the funding sources I had to hand, sending money in/out:

SOURCE
OUT
IN

LNPAY
✅
✅

LNBITSWALLET
✅
✅

LNTXBOT
❌
✅

OPENNODE
❌
❌

LNDWALLET
❌
❌

LNDWALLET
❌
❌

LNDREST
❌
❌

LNTXBOT: payment in course error/after page refresh funds seem to have gone out, but the amount doesn't match

OPENNODE: 'error_message' referenced before assignment/too many value to unpack/again after funds out error, the balance still drops by an amount that doesn't add up

LNDWALLET
[2020-10-05 11:43:27 +0100] [21893] [INFO] Running on <IP_ADDRESS>:5000 over http (CTRL + C to quit)
/home/arcbtc/lnbits/lnbits/wallets/lndgrpc.py:122: RuntimeWarning: coroutine 'sleep' was never awaited
  trio.sleep(5)
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
ASGI Framework Lifespan error, continuing without Lifespan support
Traceback (most recent call last):
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/hypercorn/trio/lifespan.py", line 29, in handle_lifespan
    await invoke_asgi(self.app, scope, self.asgi_receive, self.asgi_send)
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/hypercorn/utils.py", line 219, in invoke_asgi
    await app(scope, receive, send)
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/quart/app.py", line 2068, in __call__
    await self.asgi_app(scope, receive, send)
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/quart/app.py", line 2091, in asgi_app
    await asgi_handler(receive, send)
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/quart_trio/asgi.py", line 114, in __call__
    break
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/trio/_core/_run.py", line 815, in __aexit__
    raise combined_error_from_nursery
  File "/home/arcbtc/lnbits/lnbits/core/tasks.py", line 68, in invoice_listener
    async for checking_id in WALLET.paid_invoices_stream():
  File "/home/arcbtc/lnbits/lnbits/wallets/lndgrpc.py", line 125, in paid_invoices_stream
    async with purerpc.secure_channel(
AttributeError: 'NoneType' object has no attribute 'secure_channel'
[2020-10-05 11:43:27 +0100] [21893] [ERROR] ASGI Framework Lifespan error, continuing without Lifespan support
Traceback (most recent call last):
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/hypercorn/trio/lifespan.py", line 29, in handle_lifespan
    await invoke_asgi(self.app, scope, self.asgi_receive, self.asgi_send)
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/hypercorn/utils.py", line 219, in invoke_asgi
    await app(scope, receive, send)
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/quart/app.py", line 2068, in __call__
    await self.asgi_app(scope, receive, send)
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/quart/app.py", line 2091, in asgi_app
    await asgi_handler(receive, send)
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/quart_trio/asgi.py", line 114, in __call__
    break
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/trio/_core/_run.py", line 815, in __aexit__
    raise combined_error_from_nursery
  File "/home/arcbtc/lnbits/lnbits/core/tasks.py", line 68, in invoice_listener
    async for checking_id in WALLET.paid_invoices_stream():
  File "/home/arcbtc/lnbits/lnbits/wallets/lndgrpc.py", line 125, in paid_invoices_stream
    async with purerpc.secure_channel(
AttributeError: 'NoneType' object has no attribute 'secure_channel'

LNDREST: UnsupportedProtocol
[2020-10-05 11:46:10 +0100] [22185] [INFO] Running on <IP_ADDRESS>:5000 over http (CTRL + C to quit)
ASGI Framework Lifespan error, continuing without Lifespan support
Traceback (most recent call last):
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/httpx/_exceptions.py", line 339, in map_exceptions
    yield
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/httpx/_client.py", line 1500, in _send_single_request
    (status_code, headers, stream, ext,) = await transport.arequest(
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/httpcore/_async/connection_pool.py", line 173, in arequest
    raise UnsupportedProtocol(f"Unsupported URL protocol {scheme!r}")
httpcore.UnsupportedProtocol: Unsupported URL protocol ''

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/hypercorn/trio/lifespan.py", line 29, in handle_lifespan
    await invoke_asgi(self.app, scope, self.asgi_receive, self.asgi_send)
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/hypercorn/utils.py", line 219, in invoke_asgi
    await app(scope, receive, send)
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/quart/app.py", line 2068, in __call__
    await self.asgi_app(scope, receive, send)
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/quart/app.py", line 2091, in asgi_app
    await asgi_handler(receive, send)
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/quart_trio/asgi.py", line 114, in __call__
    break
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/trio/_core/_run.py", line 815, in __aexit__
    raise combined_error_from_nursery
  File "/home/arcbtc/lnbits/lnbits/core/tasks.py", line 68, in invoice_listener
    async for checking_id in WALLET.paid_invoices_stream():
  File "/home/arcbtc/lnbits/lnbits/wallets/lndrest.py", line 116, in paid_invoices_stream
    async with client.stream("GET", url) as r:
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/httpx/_client.py", line 1827, in __aenter__
    self.response = await self.client.send(
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/httpx/_client.py", line 1397, in send
    response = await self._send_handling_auth(
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/httpx/_client.py", line 1435, in _send_handling_auth
    response = await self._send_handling_redirects(
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/httpx/_client.py", line 1467, in _send_handling_redirects
    response = await self._send_single_request(request, timeout)
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/httpx/_client.py", line 1500, in _send_single_request
    (status_code, headers, stream, ext,) = await transport.arequest(
  File "/usr/lib/python3.8/contextlib.py", line 131, in __exit__
    self.gen.throw(type, value, traceback)
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/httpx/_exceptions.py", line 356, in map_exceptions
    raise mapped_exc(message, **kwargs) from exc  # type: ignore
httpx.UnsupportedProtocol: Unsupported URL protocol ''
[2020-10-05 11:46:10 +0100] [22185] [ERROR] ASGI Framework Lifespan error, continuing without Lifespan support
Traceback (most recent call last):
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/httpx/_exceptions.py", line 339, in map_exceptions
    yield
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/httpx/_client.py", line 1500, in _send_single_request
    (status_code, headers, stream, ext,) = await transport.arequest(
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/httpcore/_async/connection_pool.py", line 173, in arequest
    raise UnsupportedProtocol(f"Unsupported URL protocol {scheme!r}")
httpcore.UnsupportedProtocol: Unsupported URL protocol ''

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/hypercorn/trio/lifespan.py", line 29, in handle_lifespan
    await invoke_asgi(self.app, scope, self.asgi_receive, self.asgi_send)
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/hypercorn/utils.py", line 219, in invoke_asgi
    await app(scope, receive, send)
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/quart/app.py", line 2068, in __call__
    await self.asgi_app(scope, receive, send)
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/quart/app.py", line 2091, in asgi_app
    await asgi_handler(receive, send)
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/quart_trio/asgi.py", line 114, in __call__
    break
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/trio/_core/_run.py", line 815, in __aexit__
    raise combined_error_from_nursery
  File "/home/arcbtc/lnbits/lnbits/core/tasks.py", line 68, in invoice_listener
    async for checking_id in WALLET.paid_invoices_stream():
  File "/home/arcbtc/lnbits/lnbits/wallets/lndrest.py", line 116, in paid_invoices_stream
    async with client.stream("GET", url) as r:
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/httpx/_client.py", line 1827, in __aenter__
    self.response = await self.client.send(
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/httpx/_client.py", line 1397, in send
    response = await self._send_handling_auth(
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/httpx/_client.py", line 1435, in _send_handling_auth
    response = await self._send_handling_redirects(
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/httpx/_client.py", line 1467, in _send_handling_redirects
    response = await self._send_single_request(request, timeout)
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/httpx/_client.py", line 1500, in _send_single_request
    (status_code, headers, stream, ext,) = await transport.arequest(
  File "/usr/lib/python3.8/contextlib.py", line 131, in __exit__
    self.gen.throw(type, value, traceback)
  File "/home/arcbtc/.local/share/virtualenvs/lnbits-95d1K1Xz/lib/python3.8/site-packages/httpx/_exceptions.py", line 356, in map_exceptions
    raise mapped_exc(message, **kwargs) from exc  # type: ignore
httpx.UnsupportedProtocol: Unsupported URL protocol ''

LndWallet is failing because of missing dependencies (but the code is not handling that as well as it should).
LndWalletRest seems to be failing because of a wrong LND_REST_ENDPOINTvariable, which expects an https:// prefix and I didn't change that part, but will introduce a safety net for it.

Yes, had to add change endpoint from <IP_ADDRESS>:8180 to https://<IP_ADDRESS>:8180
Getting some encodingHex error now.
Flask used to dump debig info into the terminal, is this something possible in Quart?

It's not Quart's fault. We have code catching that Exception and returning it as a normal HTTP error. Flask also doesn't dump errors when you catch them in the code like we do.
I'm against that, I think we should let lnbits crash.
To remove that crash handling part go on lnbits/core/views/api.py and remove the try...except block from api_payments_create_invoice, leave only the contents of the try part.

OpenNode is working now!

Ok, then I will merge.
Merge now, fix other bugs later.


more extensive tests are required

@rultor release, tag is 0.0.18

@rultor release, tag is 0.0.18

@yegor256 OK, I will release it now. Please check the progress here.

@rultor release, tag is 0.0.18

@yegor256 Done! FYI, the full log is here (took me 22min).


Can the wrongly deleted files be retrieved

Can the wrongly deleted files be retrieved？？？

Not for filer.
If using blob storage, it is possible.


Add pdm run commands for unit, spec, and integration

I'm adding some little helper scripts to make testing easier. I excluded integration from pdm run test since I'd like test to run locally.

Good idea 🤦 Will do!

Opened https://github.com/recap-build/recap/issues/355.


Jade

Emmet doesn't support Jade template engine - http://jade-lang.com/
I hope we can arrange that.

Anyone ever use this? I've had no luck with Jade at all

it just outputs html in sublime 3.
emmet with jade works in sublime 2 thought.

Exactly what I needed to hear -- thanks @morgondag !

Let's hope we can get Jade support for Emmet in ST3. Would increase dev speedx10

Just pushed another update, hope it helps


Infinite redirect when using [BVNetwork.NotFound.Core.NotFoundPage.NotFoundPage] Attribute

I am using the [BVNetwork.NotFound.Core.NotFoundPage.NotFoundPage] attribute on our ErrorPage controller action in Episerver 11 so that the response type is 404 instead of 200. However, when I use this attribute, it causes an infinite redirect.  In our web.config we are using errorMode="Custom" existingResponse="Replace"  for httpErrors. What could be causing the infinite redirects? If I manually set the response type to 404 instead of using the attribute, I still get the infinite redirects. It seems like 404 handler is catching the 404 error again and again.

@KidMojo What version of 404 handler are you using?

Hey @marisks , Can't believe I just found this. We are also annotating our controller with the not found attribute and our 404 pages are stuck in a redirect loop. We've just pushed version 11.4.0 into production and discovered this. Very odd as we are not seeing the same issue on inte or prep!
Any thoughts on what could be causing this?

With the help of EPiServer support we managed to fix our issue. The resolution was to remove all custom redirects, clean up the exported xml (in terms of removing a load of unneeded / old entries) and importing the result into the manager. We went from 5003 custom redirects down to 4427 and everything is working again now.


Bump version to 1.0.1

Update version in README and CHANGELOG, too. Can keep the same "initial release" bit.

LGTM


error (1)

Please paste the output of the following command here: sudo edit-chroot -all

name: xenial
encrypted: yes, locked
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...
Please describe your issue:
If known, describe the steps to reproduce the issue:

@epicwappy20,
You'll need to enter the password for your encrypted chroot so we can see the crouton version info.
Also, can you show us the command and output that throws that error, please?
Hope this helps,
-DennisLfromGA

chronos@localhost / $ sudo startxfce4
Enter encryption passphrase for xenial:
Entering /mnt/stateful_partition/crouton/chroots/xenial...
/usr/bin/startxfce4: Starting X server
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
X.Org X Server 1.19.6
Release Date: 2017-12-20
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-138-generic armv7l Ubuntu
Current Operating System: Linux localhost 3.8.11 #1 SMP Sun Jul 14 00:09:57 PDT 2019 armv7l
Kernel command line: cros_secure console= console= loglevel=7 init=/sbin/init cros_secure root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 2539520 verity payload=PARTUUID=b5cda4ae-e8c4-a645-b7c8-3b4379df4fe5/PARTNROFF=1 hashtree=PARTUUID=b5cda4ae-e8c4-a645-b7c8-3b4379df4fe5/PARTNROFF=1 hashstart=2539520 alg=sha1 root_hexdigest=3bfc672b009a3247d3cd8399a74f96ac53188553 salt=306427720380043295ff7f5e5f7ef68a81138057901e316471bd1520719b78b2" noinitrd vt.global_cursor_default=0 kern_guid=b5cda4ae-e8c4-a645-b7c8-3b4379df4fe5
Build Date: 25 October 2018  04:16:21PM
xorg-server 2:1.19.6-1ubuntu4.1~16.04.2 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/Xorg.crouton.1.log", Time: Sat Nov  9 15:03:51 2019
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.chromium.LibCrosService was not provided by any .service files
method return time=1573329831.918541 sender=:1.9 -> destination=:1.131 serial=5524 reply_serial=2
boolean true
MESA-LOADER: failed to retrieve device information
gbm: failed to open any driver (search paths /usr/lib/arm-linux-gnueabihf/dri:${ORIGIN}/dri:/usr/lib/dri)
gbm: Last dlopen error: /usr/lib/dri/exynos_dri.so: cannot open shared object file: No such file or directory
failed to load driver: exynos
EGL_MESA_drm_image required.
(EE)
Fatal server error:
(EE) AddScreen/ScreenInit failed for driver 1
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/tmp/Xorg.crouton.1.log" for additional information.
(EE)
Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.chromium.LibCrosService was not provided by any .service files
method return time=1573329833.002010 sender=:1.9 -> destination=:1.133 serial=5525 reply_serial=2
boolean true
(EE) Server terminated with error (1). Closing log file.
/usr/bin/xinit: giving up
/usr/bin/xinit: unable to connect to X server: Connection refused
/usr/bin/xinit: server error
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...

@epicwappy20,

Current Operating System: Linux localhost 3.8.11 #1 SMP Sun Jul 14 00:09:57 PDT 2019 armv7l

Without the croutonversion output we can't determine much more than you're using an ARM device and the xorg xmethod and that's failing.
My suggestion is to add the 'xiwi' xmethod and see if your xfce4desktop launches then.
Hope this helps,
-DennisLfromGA


Updates

It's GridStack receiving updates? the version 0.3.0 releases 6 months ago

Wondering the same here, is this project still maintained?

0.3.0? Latest according to NPM or GitHub releases is 0.2.6 I think.

Hey all! Good questions here.
We have definitely faltered in our support for gridstack. @troolee and I plan to speak soon about the future of gridstack. We will keep everyone informed!
Stay tuned.

Thank you very much for giving us an answer!
We are all waiting for new news,
This plugin is very useful for various web applications.

Any updates to this? I'd really like to use the grid-to-grid-dragging, may it be possible to publish the current dev status 0.3.0 as new update on npm?

As I mentioned in the other ticket, we'll flag v0.3.0 for release tomorrow!


Avoid having a big big file

It's a very good tool but it generate a really big file (for example, when we have 100 files to include).
It'd generate in several files by adding any option in command line.

So, you want an option in command line to split generated output into several files?

Exactly.

@ZaniaDeveloper ,
Since generated output is not suppose to be edited, why would you care for the size of output file?
Do you have use case where this will be helpful for other?
Since we have -include option, maybe you can split them by running go-bindata several times by using different input. How about that?

The generated files contains APIs like the function AssetNames(). With the big sized file, JetBrains (or another editor) just don't want parse 60000 lines and a 3Mo sized file. It's understandable cause a source has not to have a such size.
Therefore, its functions used in other files is not recognized and the editor say that it can't find these functions.
The -include can be a solution but i think i'm not the only one with this case, cause in real case, we'd like include plenty of embedded files. It's a repetitive work to generate several command to split file, that's become an heavy cost if we have to maintain that in several project.
So, i'll post a PR to fix it up.

Thank you for the merge.


Invalid cookiePolicy with a Punycode domain on FireFox / IE

Recently, gapi.auth2.init has started throwing Invalid cookiePolicy exception when accessed with a Punycode domain on FireFox / IE 11.
We looked into the JavaScript loaded from
https://apis.google.com/_/scs/apps-static/_/js/k=oz.gapi.ja.hHlKNQx3IPg.O/m=auth2/rt=j/sv=1/d=1/ed=1/am=AQ/rs=AGLTcCPkcJYG4bEfVbYtexC1oDHtRkFZGA/cb=gapi.loaded_0

and found the following code:
var c=window.location.hostname;
"single_host_origin"==a&&(a=window.location.protocol+"//"+c);
if("none"==a)return null;
var f=/^(https?:\/\/)([0-9.\-_A-Za-z]+)(?::(\d+))?$/.exec(a);
if(!f)throw new uO("Invalid cookiePolicy");

When the cookiePolicy (a above) is single_host_origin (the default value), this security check works expected on Chrome / Safari since the value window.location.hostname is in  Punycode.
However, this fails on FireFox / IE since the value is in Unicode and the regular expression does not match.
Even when a Punycode domain name (rather than a Unicode equivalent) is directly entered in the browser address bar, window.location.hostname in FireFox / IE returns a Unicode value.  Thus, we cannot avoid the exception.
We tried to specify cookiePolicy to be our Punycode domain (URI), in order to avoid the use of window.location.hostname in the above code, but another exception Invalid cookiePolicy domain is thrown immediately after the above code:
a=f[2];
var g=f[1],f={};
f.dotValue=a.split(".").length;
f.isSecure=-1!=g.indexOf("https");
f.domain=a;
a="."+a;
if(c.lastIndexOf(a)!== c.length-a.length)throw new uO("Invalid cookiePolicy domain");

This is checking if a Punycode domain is a substring of  window.location.hostname, and it cannot be true in FireFox / IE since window.location.hostname is in Unicode.
Is there any workaround we can make the Google authentication work again with a Punycode domain on FireFox / IE?
References:
FireFox has a tracker for this behavior but it is unresolved for 9 years.

Hey @ken1ma, thanks for raising this issue. I am very surprised that it is only a recent behavior as we haven't changed this logic in a long time. Are you sure this is a recent behavior?
Anyways, I agree we should address the Punycode issue. We'll work on that and I'll keep this thread updated.

Hello, @TMSCH.  We have no proof, but I seem to remember that we were able to sign in with a Punycode domain two weeks ago, and my testing team tells me the same.


Extract HLL related code to separate module

First stage required by https://github.com/druid-io/druid/issues/3864

HLL code was moved to hll module
collector.getStorageBuffer().duplicate() call replaced by collector.createStorageBufferCopy() (that was required because getStorageBuffer() has protected scope)
3 test cases moved from HyperLogLogCollectorTest.java to HyperUniquesAggregatorFactoryTest.java
imports updated accorss projects

further changes will be added in another PR

I'm pretty on board with this. It'll allow us to have different and possibly better versions of HLL

I don't think there's a need to have pluggable HLL variants (might as well be another aggregator type). But splitting is nice since it allows people that want to get HLLs out of (or into) Druid to use this module to serialize and deserialize them, same as is currently possible for datasketches.

CLA filled.
Thx for tip about ByteBuffer - HyperLogLogCollector updated with makeCollectorSharingStorage - ByteBuffer#duplicate() name is very misleading :/

👍

LGTM, thx @DaimonPl!


CTD after loading since 3/29

Describe the bug
On Friday, 3/26, I restarted my computer as I always do on Friday evenings. It wasn't used all weekend, but since I returned to it Mon 3/29, Runelite (and, in fact, even the Steam OSRS client) crash immediately upon loading. That is, plugins etc. will load but the moment RL's 'frame' displays, it crashes to desktop.
I have found that completely removing all graphics drivers will allow RL to open occasionally, but almost entirely at random. This, of course, isn't ideal as I'm unable to play practically any other game and causes RL to run very poorly.
To Reproduce
Launch RuneLite.
Expected behavior
RuneLite loading succesfully.
Screenshots
N/A
Environment (please complete the following information):

OS: Windows 10 Pro
RuneLite version: Whichever is current as of today.
Launcher version: Ditto

Additional context
jvm_crash_pid_18536.log

The issue tracker is not a support forum. Please join the Discord for questions of support.


Autocompletes doesn't pop up, and if it does it hangs after typing a few characters

In the video I first show that "Analytics" is a type that exists.
I then show that the autocomplete doesn't pop up.
I then show that the autocomplete hangs after typing a few characters.
What I also noticed is that the autocomplete only shows the "Loading..."  label after hitting the shortcut a few times (00:12).
Saw that there are some problems with .NET 6 so, thought that i might be important to know for you guys, that I am using .NET 6
https://user-images.githubusercontent.com/28401593/141700024-0b585fb6-c2e0-4d08-9ca8-3c64f0895b47.mov

This appears to be the same issue I posted about some time ago https://github.com/fsharp/FsAutoComplete/issues/805

Copying from the referenced issue in FSAC
@HerrNiklasRaab
If this is still a problem for you I have just updated the alternative vscode extension fsharp-langauge-server to support dotnet 6.0 and the latest f# stuff.
It has a few less features (Though I have been working on that) but the completion does work for me.
https://marketplace.visualstudio.com/items?itemName=faldor20.fsharp-language-server-updated

Fixed in 5.10


Node 12 fixes

Some commits are resulting in Node 12 errors and others, as seen in https://github.com/biglocalnews/warn-scraper/actions/runs/5943441558

Patched with https://github.com/biglocalnews/warn-scraper/compare/1.2.38...1.2.39


Merge df_endpoint_change branch to master

Purpose
As discussed with @nadeeshaan langserver/tooling related changes in df_endpoint_change have been accepted for langserver/tooling conflicts.
The other conflict was in examples/index.json related to JDBC client removal.

Closing in favor of https://github.com/ballerina-platform/ballerina-lang/pull/12263


Unable to import osmnx after having it installed with pip.

Problem description
I've installed osmnx with pip in a fresh virtual environment as described in the README:
pip install geopandas
pip install rtree
pip install osmnx

All three commands ran successfully.
After this, I've opened a python console, and tried to import the osmnx module:
import osmnx as ox

I get the following error message:
>>> import osmnx as ox
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/alex/osmnx/osmnx/lib/python3.6/site-packages/osmnx/__init__.py", line 9, in <module>
    from .buildings import *
  File "/home/alex/osmnx/osmnx/lib/python3.6/site-packages/osmnx/buildings.py", line 9, in <module>
    import geopandas as gpd
  File "/home/alex/osmnx/osmnx/lib/python3.6/site-packages/geopandas/__init__.py", line 1, in <module>
    from geopandas.geoseries import GeoSeries
  File "/home/alex/osmnx/osmnx/lib/python3.6/site-packages/geopandas/geoseries.py", line 12, in <module>
    from geopandas.base import GeoPandasBase, _series_unary_op, _CoordinateIndexer
  File "/home/alex/osmnx/osmnx/lib/python3.6/site-packages/geopandas/base.py", line 14, in <module>
    from rtree.core import RTreeError
  File "/home/alex/osmnx/osmnx/lib/python3.6/site-packages/rtree/__init__.py", line 1, in <module>
    from .index import Rtree
  File "/home/alex/osmnx/osmnx/lib/python3.6/site-packages/rtree/index.py", line 5, in <module>
    from . import core
  File "/home/alex/osmnx/osmnx/lib/python3.6/site-packages/rtree/core.py", line 125, in <module>
    raise OSError("Could not find libspatialindex_c library file")
OSError: Could not find libspatialindex_c library file

What operating system, architecture, Python version, and OSMnx version are you using?
Operating System: Arch Linux
Architecture: x86_64
Python version: 3.6.6
OSMnx version: 0.8.1
Output of pip list:
Package         Version
--------------- -----------
certifi         2018.4.16
chardet         3.0.4
click           6.7
click-plugins   1.0.3
cligj           0.4.0
cycler          0.10.0
decorator       4.3.0
descartes       1.1.0
Fiona           1.7.12
geopandas       0.3.0
idna            2.7
kiwisolver      1.0.1
matplotlib      2.2.2
munch           2.3.2
networkx        2.1
numpy           1.14.5
osmnx           0.8.1
pandas          0.23.3
pip             10.0.1
pyparsing       2.2.0
pyproj          <IP_ADDRESS>
python-dateutil 2.7.3
pytz            2018.5
requests        2.19.1
Rtree           0.8.3
setuptools      40.0.0
Shapely         1.6.4.post1
six             1.11.0
urllib3         1.23
wheel           0.31.1

Code that reproduces the issue
import osmnx as ox

after having it installed as I have...

This is an rtree installation issue. The OSMnx readme suggests using conda and conda-forge to install the dependencies as rtree is more complicated than that. If you want to install everything with pip, read the additional instructions to get rtree's dependencies installed here: http://toblerity.org/rtree/install.html

Ok, after installing spatialindex (version 1.8.5, I hope this is not a problem, because in your linked document it is suggested to install version 1.7.0) through the package manager of my distribution, it seems to work, at least I don't get this error message anymore after importing osmnx.
This is my solution:
sudo pacman -S spatialindex
pip install geopandas
pip install rtree
pip install osmnx

The last three commands have been executed in a virtual environment using virtualenv.
Although I think it's enough to do
pip install osmnx

after having installed spatialindex on my system, since it seems that the dependencies are retrieved by default, right?
Maybe this should be mentioned in the REDME.md. Something like this:
Installation with pip
Make sure to have geospatial installed on your system. Then run
pip install osmnx


Update Excel.Worksheet.Activate(even).md

Fix typo: As per the Range.Sort method up to 3 Key Order pairs can be accepted. Corrected named argument.
It's a moot point because it implicitly is doing the same thing, regardless I added Me to qualify the Range object and explicitly state which sheet the Range is on.

Docs Build status updates of commit 25bb69a:
:clock10: Pending: waiting for processors (10 builds ahead of you)
:warning: Docs Build is busy, currently there are 10 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 25bb69a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

api/Excel.Worksheet.Activate(even).md
:white_check_mark:Succeeded
View

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.


c source file, can't show 0b1000_0000 correctly.

In this pic, 0b1000_0000 is red, while 0b1 is green. Besides, IntelliCode will interpret 0b1000 as (int) 8, and another part will be 0.

 My bad, you can mock me for a long time.


Option for vehicle to delete/hide/make standard

Add options to delete/hide/make standard for a vehicle

Was added in 0.22.0


Remove the --progress flag

Newer versions of Docker no longer support the --progress flag on the docker build command. This causes Cross to fail when using versions of Docker such as 23 and 24.
For example:
docker --version
Docker version 24.0.5, build 24.0.5-0ubuntu1~22.04.1
cross build --target aarch64-unknown-linux-gnu
info: downloading component 'rust-std' for 'aarch64-unknown-linux-gnu'
info: installing component 'rust-std' for 'aarch64-unknown-linux-gnu'
unknown flag: --progress
See 'docker --help'.

I have removed the progress code from cross in this pull request, this error no longer occurs.

This pr solves a problem which doesn't exist, the situation here is unfortunate though.
We don't call docker build, we call docker buildx build , which absolutely does support --progress. The issue here is how docker handles error reporting. See https://github.com/cross-rs/cross/issues/1055
You should be getting an error message in the cross output suggesting how to fix this, which is to check that buildx/buildkit is available or to set CROSS_CONTAINER_ENGINE_NO_BUILDKIT=1

Yup, installing buildx got rid of the progress error. Do you think it would be reasonable for Cross to check if buildx is installed before trying to use it? That way a more helpful error message could be delivered to the user.

If you can find a good way to detect buildx, I'd be happy to include a check like that!

It looks like the docker buildx version command is a good candidate for testing installation. I wrote this function to test for buildx being installed, but I am not sure what the best place to call it from would be.
fn is_buildx() -> bool {
    let mut cmd = Command::new("docker");
    cmd.args(["buildx", "version"])
        .output()
        // if buildx is present, it will print the version and exit 0
        // if buildx is not present, it will print a warning and exit 1
        .map_or(false, |out| out.status.success())
}```


Add DLC items (WTRPINK and the panda objects)

It's always mildly bothered me that the pink water and panda DLC items are treated as custom and not what they are. Here's a first-pass at json descriptions for them. I left authors blank for the moment because while I strongly suspect it's the same as the stuff in the base game - Chris Sawyer and Simon Foster - I can't prove it just now and don't know whether it's better to put possibly-wrong attribution in there, or to omit it entirely.

They are by Chris Sawyer and Simon Foster. Fosters artwork is very recognisable and Chris Sawyer put them up for download at his own site.
I have classified these objects as 'OpenRCT2 official'. I don't think having both "Official RCT2 DLC" and "Official OpenRCT2 DLC" is very useful. That also means you should change the folder name and sourceGame parameter to "official".


Add option to listen on <IP_ADDRESS> instead of individually on all interfaces

I am suggesting to add an option to bind <IP_ADDRESS> to listen on all interfaces in SimpleTcpServer, instead of itemizing the interfaces and listening on each one individually. This would work well on Windows but might not be supported on all platforms, e.g. Linux, so you may need to make this configurable through an optional parameter, or have the check which OS at run time, or have it try <IP_ADDRESS> and fall back to individual interfaces if that fails. Thoughts?

What would be the advantages of <IP_ADDRESS> vs individual interfaces?

Avoids having to enumerate interfaces and listen separately on each, and dealing with any errors on each interface, but I guess that’s more of an internal detail (that I see as beneficial), not a use case. It’s how I usually bind on Windows by default, i.e. IPAddress.Any, unless configured otherwise.  If I’m not mistaken - and I could be wrong - it could also handle cases where a network interface comes online or gets reconfigured after the server has been started.
There are other differences; whether they are advantageous or not depends on context. Can be overridden by bindings for specific interfaces, when you want that. Will not silently override another service listening on same port, e.g. if the other service is listening on the same port on <IP_ADDRESS>, your bindings on each interface will take precedence, IIRC.


Alternate way to configure consistent alias rule

Currently the consistent alias rule takes a list of module names and the alias they should each use. What if instead the rule took a function with the type signature ModuleName -> Alias where Alias is
type Alias
    = DontCare
    | AlwaysNoAlias
    | AlwaysAlias String

Edit: To elaborate on why this is useful, in the code we have at work, we have a lot of modules and I'd like to be able to do something like, all elm-ui modules shouldn't be aliased. Or all modules under Shared.* should use the last part of their module name as an alias.

I completely agree with some type being a better way of configuring this - I had started making plans toward this when #15 didn't work out. Unfortunately I have lost all my notes on that so I need to flesh them out again.
One hold up is that I want to decide how to handle module shadowing. AlwaysAlias will happily handle importing Extras (as below), but @jfmengels and I would prefer not to allow any shadowing, which means needing a way to prevent the same module name or alias from being used (as in the above example).
-- NeverAlias
import Browser
-- AlwaysAlias "Browser"
import Browser.Extra as Browser

I do not think that DontCare is in the spirit of this rule. A module should either never be aliased or always aliased consistently - if you don't care then don't configure it and let the rule try to figure it out for you. The dream is that the rule needs as little configuration as possible and is able to tell from your code what 'consistent' is for your project. Configuring specific modules would then be most useful if you wanted to change an import and force the auto-fixes across the whole project.

I do not think that DontCare is in the spirit of this rule.

At work we've been using a very similar to this though it does allow for a DontCare choice. I think this is valuable when introducing this sort of rule to a team because it means you can incrementally restrict what import aliases to use. If we had to decide on how all imports would get aliased from the start the rule probably wouldn't be used.


#570 page designed

Related Issue
Closes #570

Description
designed a page for biography type books while adding books also added show more option if many books are there also made it responsive
Screenshots

Checklist

[x] My code adheres to the established style guidelines of the project.
[x] I have included comments in areas that may be difficult to understand.
[x] My changes have not introduced any new warnings.
[x] I have conducted a self-review of my code.

@rohansx please review this


Include identification metadata in query output

Track whether a user has provided an identification for a given feature. This answer should be included in the output from the query.

This is the 'annotated' column. Returned in query results as of 0f08b48


missing indicator of regex white/blacklisting in events listing

seems like the method should also take host, path, and somehow get the globalregex settings

A Blockable's state doesn't really relate to an event (or, for that matter, a host or a path). The Blockable is still not whitelisted even if it was permitted to run at a specific path on a specific host. This dissonance highlights the questionable security properties of path-based whitelisting: The execution path can often be manipulated by an attacker or by a curious/malicious insider and is not constant for a given binary.
That said, the current usage of the "Blockable state" doesn't always line up with what is desirable. Notably, the Blockable list page is really a listing of Events. Still, I think it might be valuable to maintain consistency in the display of the Blockable state for situation when, for example, the user runs a binary successfully, moves it, and runs it again only for it to be blocked. Telling the user that the binary is "whitelisted" is inconsistent with the actual policy.
Instead, what I might suggest would be to add a secondary UI indicator (e.g. an icon) that would convey the fact that the event's outcome was influenced by the binary path. This avoids muddling the user's understanding of policy while still providing the requisite information to explain the actions that took place.

ya I had forgotten that blockables don't have paths ;)  so ya it seems having an indicator on the events page makes a lot of sense.  I've renamed the issue accordingly.  thanks for feedback.

added in https://github.com/farmersbusinessnetwork/upvote/commit/c8b91ce50e14ed3cfba2b748effe7c210d94817f, closing in favor of https://github.com/google/upvote/issues/24


Suggested feature: blacklists

From Hantzu's thread -- also personally strongly believe in. A basic logical organization of groups in general, should be in any group management plugin in general.

Ttk has expressed multiple times he does not want this.

Why not? Or can you provide links to where so I can read why he doesn't from the quote?
A search on reddit does not reveal anything, maybe Ii'm using the wrong terms. In fact, it has you saying you were already working on implementing them a year ago?
http://www.reddit.com/r/Civcraft/comments/1dtkoh/suggestion_for_citadel/
Also this thread, where ttk is reported as not even knowing if we already had blacklists
http://www.reddit.com/r/Civcraft/comments/1fqt98/on_the_last_end_portal/

It allows Citadel to be easily used offensively. Not sure if its a good idea
On Tue Feb 03 2015 at 7:00:41 PM GavJenks<EMAIL_ADDRESS>wrote:

Why not? Or can you provide links to where so I can read why he doesn't
from the quote?
A search on reddit does not reveal anything, maybe Ii'm using the wrong
terms. In fact, it has you saying you were already working on implementing
them a year ago?
http://www.reddit.com/r/Civcraft/comments/1dtkoh/suggestion_for_citadel/
Also this thread, where ttk is reported as not even knowing if we already
had blacklists
http://www.reddit.com/r/Civcraft/comments/1fqt98/on_the_last_end_portal/
—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/NameLayer/issues/46#issuecomment-72770257.

I'm not sure I follow you. How does it allow citadel to become more offensive? It seems like exactly the opposite to me. You can already easily (and people do) spike vaults, for instance, with citadel as is. And whitelists are much more convenient for that, as well as for griefing and other offensive uses. Because you simply whitelist only yourself or your group of raiders / attackers, and it is now a problem for any and all other people.
Blacklist would be silly for spiking or griefing, because you'd have to add everybody in that town, and even then, some other guy from another town could just walk in and clean it all up.
Blacklist is inherently more optimistic, friendly, public-oriented, not the other way around. Or am I missing something?

it takes all the effort out of enforcing any sort of rules, lets imagine
you could have public goods that only bad people could not use, then there
is no dilemma on if you should make goods public. No interesting discussion
with public netherfactories enabling griefers or private ones restricting
the public
On Tue Feb 03 2015 at 7:11:07 PM GavJenks<EMAIL_ADDRESS>wrote:

I'm not sure I follow you. How does it allow citadel to become more
offensive? It seems like exactly the opposite to me. You can already easily
(and people do) spike vaults, for instance, with citadel as is. And
whitelists are much more convenient for that, as well as for griefing and
other offensive uses. Because you simply whitelist only yourself or your
group of raiders / attackers, and it is now a problem for any and all other
people.
Blacklist would be silly for spiking or griefing, because you'd have to
add everybody in that town, and even then, some other guy from another town
could just walk in and clean it all up.
Blacklist is inherently more optimistic, friendly, public-oriented, not
the other way around. Or am I missing something?
—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/NameLayer/issues/46#issuecomment-72771486.

Blacklists are easily bypassable by alts.
On Tue, Feb 3, 2015 at 5:12 PM, ttk2<EMAIL_ADDRESS>wrote:

it takes all the effort out of enforcing any sort of rules, lets imagine
you could have public goods that only bad people could not use, then there
is no dilemma on if you should make goods public. No interesting discussion
with public netherfactories enabling griefers or private ones restricting
the public
On Tue Feb 03 2015 at 7:11:07 PM GavJenks<EMAIL_ADDRESS>wrote:

I'm not sure I follow you. How does it allow citadel to become more
offensive? It seems like exactly the opposite to me. You can already
easily
(and people do) spike vaults, for instance, with citadel as is. And
whitelists are much more convenient for that, as well as for griefing and
other offensive uses. Because you simply whitelist only yourself or your
group of raiders / attackers, and it is now a problem for any and all
other
people.
Blacklist would be silly for spiking or griefing, because you'd have to
add everybody in that town, and even then, some other guy from another
town
could just walk in and clean it all up.
Blacklist is inherently more optimistic, friendly, public-oriented, not
the other way around. Or am I missing something?
—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/NameLayer/issues/46#issuecomment-72771486.

—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/NameLayer/issues/46#issuecomment-72771643.

Ttk, as erocs points out, there are alts, and there are also new griefers all the time. Blacklists on a portal would require somebody to constantly be vigilant against these, in exactly the same way that a whitelister has to be constantly vigilant of new citizens in the alliance or whatever who need access to the portal. Nor do I see how this is any less of an "interesting" of a choice -- it's just a rule that lies in between the other two (unreinforced vs. whitelist) on a continuum. It seems no less inherently interesting than, say, a moderate political system does compared to a right or left wing one. It has some of the risks and some of the benefits of each.

I still believe its too much perfect security, public resources should be
public, if you want things that selectivity deny people it should be more
costly than group management
On Tue Feb 03 2015 at 7:23:48 PM GavJenks<EMAIL_ADDRESS>wrote:

Ttk, as erocs points out, there are alts, and there are also new griefers
all the time. Blacklists on a portal would require somebody to constantly
be vigilant against these, in exactly the same way that a whitelister has
to be constantly vigilant of new citizens in the alliance or whatever who
need access to the portal. Nor do I see how this is any less of an
"interesting" of a choice -- it's just a rule that lies in between the
other two (unreinforced vs. whitelist) on a continuum. It seems no less
inherently interesting than, say, a moderate political system does compared
to a right or left wing one. It has some of the risks and some of the
benefits of each.
—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/NameLayer/issues/46#issuecomment-72772772.

Actually my point is that a Citadel blacklist is pointless because you'd
never be able to keep up with adding the new alts. A whitelist is
constrained in scope by only allowing explicit individuals access.
Blacklists for JukeAlert might be interesting as a way to have snitches
only alert if a specific set of individuals enters the alerting area.
Combined with the redstone pulse from the snitch it could create traps for
specific individuals.
On Tue, Feb 3, 2015 at 5:36 PM, ttk2<EMAIL_ADDRESS>wrote:

I still believe its too much perfect security, public resources should be
public, if you want things that selectivity deny people it should be more
costly than group management
On Tue Feb 03 2015 at 7:23:48 PM GavJenks<EMAIL_ADDRESS>wrote:

Ttk, as erocs points out, there are alts, and there are also new griefers
all the time. Blacklists on a portal would require somebody to constantly
be vigilant against these, in exactly the same way that a whitelister has
to be constantly vigilant of new citizens in the alliance or whatever who
need access to the portal. Nor do I see how this is any less of an
"interesting" of a choice -- it's just a rule that lies in between the
other two (unreinforced vs. whitelist) on a continuum. It seems no less
inherently interesting than, say, a moderate political system does
compared
to a right or left wing one. It has some of the risks and some of the
benefits of each.
—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/NameLayer/issues/46#issuecomment-72772772.

—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/NameLayer/issues/46#issuecomment-72774026.

I would also like to point out that blacklisting is effectively already possible with a very simple bot:

Keep a bot online at all times jumping occasionally or whatever, in a vault in the middle of nowhere.
Have it scan the online player list and notice instantly when anybody logs on via tab or chat-letter-tab (just like the skynet mod many people use). Immediately add them to a citadel group if they aren't already, unless they're on the blacklist stored clientside or on a website or something.

Including it as a feature is simply a convenience (and fairness to people without bots) courtesy to players, not even an actual functionally new feature per se.
(and I'm actually tempted to make that and share/sell it now that I thought it out here... not as an ultimatum lol, I just really want blacklist and realized I could probably do it in an evening or two)

...Also, we have one person saying "this is pointless you can never keep up and nobody would use it" and two other people saying "this is OP, everybody would use it and it's too easy and cheap for how awesome it is"
Different people saying "X will never work" for opposite reasons is often a green flag of a decently balanced idea =P

I'm saying citadel blacklisting is pointless and JukeAlert blacklisting
might have value. Please don't twist words.
Really I'm not sure why it hasn't been added if enough people want it and
can find a coder. I would just rather not remove effort from the current
deluge of bugs and the subsequent sharding effort. It seems there are
others helping now so we don't have to overload Rourke with this.
On Feb 3, 2015 6:06 PM, "GavJenks"<EMAIL_ADDRESS>wrote:

...Also, we have one person saying "this is pointless you can never keep
up and nobody would use it" and two other people saying "this is OP,
everybody would use it and it's too easy and cheap for how awesome it is"
Different people saying "X will never work" for opposite reasons is often
a green flag of a decently balanced idea =P
—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/NameLayer/issues/46#issuecomment-72777073.

@erocs It's so wonderful, I've spent my time reviewing instead of writing.

@erocs Also Unless I'm thinking of something else couldnt that be turned into snitch spamming?

We have rate limiting for snitch spamming. The only other thing we should
do for that is persistence for jamute.
On Feb 3, 2015 6:36 PM, "rourke750"<EMAIL_ADDRESS>wrote:

@erocs https://github.com/erocs Also Unless I'm thinking of something
else couldnt that be turned into snitch spamming?
—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/NameLayer/issues/46#issuecomment-72779851.

ah I legit did not see the distinction you were making being between citadel and jukealert, gotcha. Both/either would be useful to me.
I also certainly don't mean to be pushy or demanding with regard to timelines of actually implementing anything, and do plan at some point to finish figuring out the repositories to do some of the work on lots of things myself. Just debating feature value for now. If it were viewed positively but took 8 months due to low priority without "coding it yourself" then that would be fair and understandable.

The low priority work around here is all at the "Code it yourself" level,
thus why much of it gets dropped on the floor. For any dev work to be
completed there has to be a dev motivated to perform the work, not just
someone saying how nice something would be if it existed.
The next piece is, of course, whether or not the admins think it should be
active on the server. Unfortunately sometimes that isn't known until the
feature exists. Then when its examined and decided that it shouldn't be on
the server, devs can get agitated and demotivated even though their work
was useful by enabling a decision to be made.
On Tue, Feb 3, 2015 at 7:56 PM, GavJenks<EMAIL_ADDRESS>wrote:

ah I legit did not see the distinction you were making being between
citadel and jukealert, gotcha. Both/either would be useful to me.
I also certainly don't mean to be pushy or demanding with regard to
timelines of actually implementing anything, and do plan at some point to
finish figuring out the repositories to do some of the work on lots of
things myself. Just debating feature value for now. If it were viewed
positively but took 8 months due to low priority without "coding it
yourself" then that would be fair and understandable.
—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/NameLayer/issues/46#issuecomment-72786564.

If more devs speced their proposals before writing them we would probably
not only have a much easier time telling people what we did and did not
want on the server we would probably get better and more stable code in
general. But that's time consuming and boring so very few people do.
On Tue, Feb 3, 2015, 10:34 PM erocs<EMAIL_ADDRESS>wrote:

The low priority work around here is all at the "Code it yourself" level,
thus why much of it gets dropped on the floor. For any dev work to be
completed there has to be a dev motivated to perform the work, not just
someone saying how nice something would be if it existed.
The next piece is, of course, whether or not the admins think it should be
active on the server. Unfortunately sometimes that isn't known until the
feature exists. Then when its examined and decided that it shouldn't be on
the server, devs can get agitated and demotivated even though their work
was useful by enabling a decision to be made.
On Tue, Feb 3, 2015 at 7:56 PM, GavJenks<EMAIL_ADDRESS>wrote:

ah I legit did not see the distinction you were making being between
citadel and jukealert, gotcha. Both/either would be useful to me.
I also certainly don't mean to be pushy or demanding with regard to
timelines of actually implementing anything, and do plan at some point to
finish figuring out the repositories to do some of the work on lots of
things myself. Just debating feature value for now. If it were viewed
positively but took 8 months due to low priority without "coding it
yourself" then that would be fair and understandable.
—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/NameLayer/issues/46#issuecomment-72786564.

—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/NameLayer/issues/46#issuecomment-72789303.


efficiently load entire model from DB to memory

DBFlow Version: 4.0.0-beta7
Kotlin 1.1
Issue Kind (Bug, Question, Feature): Question
Please note if you are using Instant Run, there may be bugs where generated classes are not created. Ensure you are using the apt or kapt plugins and that incremental compilation is off.
Description:
My app has a LEAGUE model which holds a list of TEAMS, each of which contains a list of PLAYERS. My TEAM class contains a getMyPlayers() function annotated with @OneToMany() for Method.LOAD, while the PLAYER class contains a TEAM variable annotated with @ForeignKey(), as per the documentation
(I am using Kotlin, so the syntax is slightly different)
When the app starts, the entire LEAGUE model should get loaded into memory. It runs:
for (team in SQLite.select().from(Team::class.java).queryList()) {
  League.allTeams.add(team)
}

Because of the getMyPlayers() function (i.e. like getMyAnts() ), the above code automatically populates the Player list in each Team. However, it is inefficient, as it runs a SELECT for every team. A more efficient pattern would be like below, just one SELECT from Players, which reduced the load time by 80+% (I commented out the @OneToMany() block).
val playerList = SQLite.select().from(Player::class.java).queryList()
for (team in SQLite.select().from(Team::class.java).queryList()) {
  for (player in playerList.filter { it.myTeam.teamID == team.teamID } ) {
    team.Players.add(player)
  }
  League.allTeams.add(team)
}

However it seemed the app was not reliably aware of the relationships, I think because the "relationship" was assigned outside of DBFlow (sometimes a player could not say what team he belonged to, or vice versa -- especially after terminating the app then restarting, requiring a reload from DB).
Bottom line: is there a way to tell DBFlow to efficiently load the entire model into memory, while it maintains all the correct relationship information? The difference is an app startup time of 4-6 seconds vs under 1 second. Thank you.

dont use @OneToMany on significant loads. The relationship for that is a fake one - i.e. inserted as a convenience for the processor. you can still call getMyPlayers() manually, itll just happen when you call it.


sxstrace does not accept slashes

Running the example commands does not work; sxstrace just prints out its help.  However, if the slashes are replaced with dashes, the commands work.  The documentation should be updated so the parameter syntax is correct.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 00064275-ab46-02df-3c98-adc4c2f08db4
Version Independent ID: 18dee0ea-506d-83b7-02ca-cbf3589b64a2
Content: sxstrace
Content Source: WindowsServerDocs/administration/windows-commands/sxstrace.md
Product: windows-server-threshold
GitHub Login: @coreyp-at-msft
Microsoft Alias: coreyp

Forgot to mention my Windows version: 10.0.17763.316

You are totally right, I have the same issue and solution.

Thanks for your dedication to our documentation. If we have been unable to review your issue in a timely manner, we sincerely apologize for the delayed response. We have captured the informtion you have provided for review. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close


Do sections without headings count in calculating depth?

What is the level of the heading in

<h>What level am I?</h>

      <h>What about me?</h>

I think the answer currently is "one, two" but it isn't explicitly clear.
Consistently using terms from HTML like sectioning content and sectioning root would help.

Great question, and thanks @chaals for the additional advice.
First, would you help understand sectioning content a bit better? From sectioning content, here is the definition of sectioning content:

Sectioning content is content that defines the scope of headings and footers.

After this definition, these elements appear; are they sectioning elements? Are they all of them?

Because, in sectioning root, the example refers to an
 as "[a] heading of [the] explicit body section."
Does this mean  is also "sectioning content"?
Do you understand my confusion?

Yeah, I understand the confusion. Having worked through that section with some examples, I agree it's terrible to understand :(
Yes, article, aside, nav and section are all the "sectioning content elements". There are also sectioning roots...
Roughly, the algorithm means that nesting is defined in terms of sectioning content. h1-h6 elements without sectioning create an "implied section" - but that behaves somewhat bizarrely since it doesn't participate in the algorithm the same way sectioning content elements do :(
Likewise, sectioning roots behave a bit oddly. I didn't dig in all the way, and it seems the text is confused about it anyway.
My advice is that you should feel free to describe a different algorithm - maybe the one in HTML is not implemented just because it's horribly confusing - I have no idea. But you should be explicit in which elements you mean and how they work together, either by using the existing HTML definitions or by documenting the differences

I hadn’t noticed that  was a sectioning root alongside
, , <dialog>, <fieldset>,
, and .

These elements can have their own outlines, but the sections and headings inside these elements do not contribute to the outlines of their ancestors.

What was the motivation behind sectioning roots?
It’s confusing when  does not contribute to the outline of its ancestor and yet I’d consider it the top-most outline of the page’s content.

My advice is that you should feel free to describe a different algorithm

Maybe. I’d like to get further information that helps me understand the motivation behind sectioning roots and why each of those elements was chosen to be assigned as such.

Hey @chaals, on just one subject, would you be able to shed light on the motivation behind sectioning roots?

Not quickly, @hixie or perhaps @stevefaulkner may be able to tell you.
As far as I can tell, and this is basically as an observer:
details and dialog aren't quite "part of the page", unless you asked for them.
There isn't anything outside body so it would be a no-op making it a placeholder.
The others might include sectioned content - or a single heading - but at a level that means unless you are in them, you wouldn't really want to know. (This is a part that doesn't convince me, although I wouldn't want to die arguing the counter-case either - I think it's a subjective call, although perhaps there is some really clear data somewhere that leads "everyone" to the same interpretation).

Yes, article, aside, nav and section are all the "sectioning content elements". There are also sectioning roots...

Hm, how about header? Is its meaning even well-defined? The description from w3schools isn't exactly helpful: https://www.w3schools.com/tags/tag_header.asp


All Scenarios: The "Save" button should be disabled on the "Advanced data options" dialog for SQL Server data.

System Information (please complete the following information):
Windows OS: Windows-11-Enterprise-22H2
ML.Net Model Builder 2022: <IP_ADDRESS>0901 (Main Build)
Microsoft Visual Studio Enterprise: 2022(17.5.5)
.Net: 6.0, 7.0
Describe the bug

On which step of the process did you run into an issue:
The "Save" button should be disabled on the "Advanced data options" dialog for SQL Server data.

TestMatrix
https://testpass.blob.core.windows.net/test-pass-data/wikipedia-detox-250-line-data.tsv
To Reproduce
Steps to reproduce the behavior:

Select Create a new project from the Visual Studio start window.
Choose the C# Console App (.NET Core) project template.
Add model builder by right click on the project.
Select any scenario.
On Data page, choose the SQL Server data source.
Click the "Advanced data options..." link, you will see that the "Save" button is enabled.

Expected behavior
The "Save" button should be disabled on the "Advanced data options" dialog for SQL Server data.
Screenshot

Additional context
The bug is not repro for File data source.

The bug is not repro on the latest main build <IP_ADDRESS>5701.


add test for extra widget fields preserving data

these tests aren't in right now b/c the extra widgets are displayed with js, and selenium + js == big headache


[Bug]: input values getting truncated

Is there an existing issue for this?

[X] I have searched the existing issues

Description
User reported issue, and prima facie this seems to be unrelated to #12318

application has a form with some input fields and a submit button
when user enters some values in these widgets and clicks submit, an insert query is called
sporadically, the values from these inputs are truncated. For example, "Hotel" is stored as "Ho", and "200" is stored as "2"

please note: The user is directly using the format input1.text to access these values in the insert query, and they don't use any store values.
Some things we investigated along with the user:

the problems occurs randomly, on random fields
this is not related to delay time, because even if the user waits 1 minute before submitting the form, sometimes the truncated values are being persisted to the db

PS: I have a copy of the app json if needed.
Steps To Reproduce
explained above
Public Sample App
No response
Version
Cloud

It is dangerous bug when we we are building the critical application(related to financial apps),  Could you please fix this as soon as possible within some time or so.

@SidHiremath thank you for your comment. We are currently trying to find a way to reproduce this, do you see this issue in your apps as well? If yes, do you mind doing the following:

invite<EMAIL_ADDRESS>to your org
share the app link and steps to reproduce the error here

@sbalaji1192  Can you add steps to reproduce for this issue.

@Rishabh-Rathod I was able to repro this issue consistently by swiping the keys from 1 to 9 rapidly.

Steps to reproduce

Open Sample complex application ( Ask @Rishabh-Rathod for access )
Go to the “Configuration Details” page -> “Segmentation Config” tab.
Click on the “Add sample data” button to add data to the table.
Once data is populated, click on the “Edit” button inside the table to open the modal.
If you edit any Input in the modal, the binding is not getting reflected in the Text widget at the bottom.
Also noticed a lot of delay in loading the widgets and opening the modal

When tried swiping the keys from 1 to 9 rapidly, we saw the truncation issue was reproducible.

When this will be fixed?
Kindly request that this is something that should be fixed as early as possible or right away as it might cause data issue!

This is already worked on https://github.com/appsmithorg/appsmith/pull/13084 and the solution is in the testing phase.
This will soon be fixed in production.
@SidHiremath


No tests for ActionMailer interceptor integration

Thus I can't write any meaningful unit tests for #6

Not sure what tests you mean. The test suite does not mock the interceptors, ActionMailer executes InlineCssHook.delivering_email without any modifications.


PekkoPersistenceJdbcVersion 1.1.0-M1

see #83

Do I understand correctly that we want to tag v1.1.0-M0 after merging this, to flag that he next release of pekko-persistence-r2dbc after this change should be v1.1.0?

Do I understand correctly that we want to tag v1.1.0-M0 after merging this, to flag that he next release of pekko-persistence-r2dbc after this change should be v1.1.0?

Makes sense. It was an oversight not to have already added the v1.1.0-M0 tag. We've already got 1.1.0-M1 dependency on pekko-core.

I had the v1.1.0-M0 tag locally but forgot to push to git remote. Generally, we add that tag when we fork out the 1.0 build from main. I have pushed that tag now.


STM32U5xx crashes in startup file

I have followed this guide thoroughly and it worked great for MCUs I have worked so far with (F7 and F1), but with U5 I get some very-hard-to-explain behaviour. Build is flawless but debug is not. When entered the code execution stops at first instruction of startup file, then as soon as it runs to reach main, it crashes. Meaning it doesn't reach HardFault handler or any other fault handler. When I try stopping the execution debugger says it cannot stop and returns some undefined stack values.
The hardware I'm using:

ST-Link V3 MINI with 6 pin SWD connect
standalone STM32U535 (with SMPS)
3.3V power supply at the MCU with all the necessary minimum components

The software I'm using:

CMake and Ninja for build files
arm-none-eabi-gcc, version 12.3, the same one STM32CubeIDE uses
STM32CubeMX generated startup file, linker file, and HAL with main()

Although I tried closely replicate CubeIDE's build setup, mainly through build flags since the rest should be very similar, the CubeIDE project build and runs perfectly. Meaning debugger reaches main without issues. Although I tried reverse engineering all the flags CubeIDE uses but I don't, it still seems something greater is missing since program crashes anyway. I've also tried substantially increasing heap and stack size but without improvement.
My only suspects were that either instruction set is not recognized or stack pointer is corrupted somehow. Instruction set should be a valid one as I'm using -mthumb flag. If it would be a hard fault I could at least check the source, which I cannot. The other one, the stack pointer likely corrupted, I'm not sure about that. When the first instruction of startup file tries to be executed and crashes, the stack address should be loaded into a register R0 like for any other STM32 MCU. And given the default linker file, I wouldn't have a clue why proper stack initialization wouldn't work out as it should.
But if I use the same actual setup for STM32F103 MCU (with different HAL, startup, and linker files plus CPU flags and the same hardware), debugger reaches main without issues.
I have appended my VSCode custom setup and would greatly appreciate if someone could give it a look. I have tried every possibility I had in mind but all in vain.
test-vscode.zip

Here's the same setup that works but in CubeIDE.
test-cubeide.zip

Luka,
I compiled your project, and run it with NUCLEO-U545RE.

I used the cortex-debug and it worked flawlessly. I removed the hardcoded paths to compiler/GDB since I have mine in the PATH config.

We've seen problem like this in the past, if hardware was not done correctly, and then GDB connect from the vscode used different flags than the one in the CubeIDE. One of the problems could be missing/wrong VCAP capacitors config, that could crash the CPU if connected with high CPU frequency on the ST-Link/JTAG.
In the vscode launch, you may investigate the option below, to lower connect frequency:
"serverArgs": ["--frequency 4000"]

I'm not saying this will fix the issue, but it might be the solution.

Tilen,
Thanks for insightful tips. Regarding the hardware, given that CubeIDE manages to debug until main on my hardware I'm still convinced there's a way for me to do the same from VSCode.
The VCAP in my case is 2x2.2uF MLCC since it's the 100 pin package with SMPS in parallel to LDO. However, I did just notice that the two capacitors are not distributed between two pins but are only positioned at one pin. This is definitely my fault. Other connections should be fine since I also followed STM32U5 hardware design guide during design of hardware. Really helpful by the way!
Regarding lowering the frequency, to my understanding that argument should lower the debugging clock speed to 4kHz. If yes then it appears the communication speed is still pretty high. Here's the starting log from the gdb-server terminal:
 ------ Switching context -----  COM frequency = 3300 kHz Target connection mode: Default Reading ROM table for AP 0 @0xe00fefd0 Hardware watchpoint supported by the target  ST-LINK Firmware version : V3J15M7 Device ID: 0x455 PC: 0xbf989f4 ST-LINK detects target voltage = 3.30 V TrustZone: Inactive ST-LINK device status: HALT_MODE GDB session, device event: 6 Stm32Device, pollAndNotify running... Enter STM32_SystemReset() function  Enter STM32_InitAfterReset() function  NVIC_DFSR_REG = 0x0000000B NVIC_CFGFSR_REG = 0x00000000 GDB session, device event: 4 Accepted connection on port 50000... Debugger connected Waiting for debugger connection... Waiting for connection on port 50000... GDB session thread running GdbSessionManager, session started: 2 GDB session, device event: 3 GDB session, device event: 3 GDB session, device event: 1 GDB session, device event: 1 ST-LINK device status: RUN_MODE
In case you have further doubts regarding the hardware and have an extra minute, I've appended a schematic below. Check the "MCU supply" section for any irregularities. Except previously mentioned caps, all other are in their valid position next to relevant pins.
I will try adding missing capacitor (tantalum, not MLCC) to the relevant pin, as close as possible. If this doesn't work out then I will try to replicate  NUCLEO-U545RE's MCU related external components.
Props to your VSCode custom setup! Makes my embedded development experience more exciting :)
HMS100_SystemController-System controller.pdf

I don't see obvious mistakes on your schematics. As long as you didn't forget at least ona VDD11 cap, it should be fine. I don't know why you have C9 capacitor on your button (boot0). This I'd remove in general.

I have managed to try various speeds from 3300kHz down to 5kHz for GDB communication link. All of them failed. However, if neither of these clock settings would work then connection would have likely failed during establishing connection. Whereas in my case code execution stops at first instruction in startup file and then fails as it runs.

Then I don't think this is the issue. Btw, parameter is always in "kilohertz", so for instance --frequency 4000 means 4MHz. I think lowest you can do is 1.8MHz.

If it's relevant the stack undefined values are shown on the image below when I try to stop debugger after initial run. And if I chose to do anything else I get this: Could not step over: Cannot find bounds of current function (from exec-step --thread 1).

This is definitely strange, but since it worked on my Nucleo, I don't see a reason why it wouldn't worked on your side. Linker script seems just fine to me.

But if the CubeIDE manages to get the same piece of hardware working then the GDB communication speed isn't the main problem. Considering I use the lowest value for GDB communication speed CubeIDE is allowed to use.

Yeah, in general I agree.

Any other ideas? It's really strange that you get normal response with a NUCLEO evaluation board, meanwhile CubeIDE on my end proves my custom hardware is still able to run normally but not also VSCode setup, which in fact works for you.

Do you have by chance any TrustZone enabled? Disable it if you have it.

If -mthumb is valid then I don't see a reason code execution would crash at first instruction of startup file due to any build flags. Surely, none of flags could cause such severe aftereffects (except optimizations perhaps), right? And considering linker and startup files are the same, is there really anything else that would play major role at running the MCU besides the mentioned factors?

-mthumb is definitely the right approach.
What I can offer you is a Google Meet and we go through via screen sharing meeting and review the situation. In that case, ping me to +33662774291 (whatsapp for instance).

This issue has been resolved. The problem was the BOOT0 pin which was set for the MCU to start from bootloader (high state) rather than from main flash (low state). This can additionally be configured in STM32CubeProgrammer whether hardware BOOT0 is considered or software configuration bit is applied instead.
Another issue was the failure of MCU and ending up in hard fault handler when stepping over the __libc_init_array in startup file. As C++ was used in this project it appeared there was a bug in my code where constructor was accepting null pointer and constructor code was trying to dereference it. Therefore leading to hard fault.


Settings v2: do not build MSIX

📝 Provide detailed reproduction steps (if any)

See this comment for the description

Label Area-MSIX hasn't been used yet.

@yuyoyuppe is this still an issue?

no, we can close it


External links on disease pages

Link to DO for specific IDs e.g. http://disease-ontology.org/term/DOID%3A0070131/
I think it would be nice to link to malacards too because they conglomerate a lot of information for a disease but we probably can't do it easily from the DO ID.

I've added the link to DO on the pombase-dev term pages.  You'll need to reload.

thanks!


[AutoRelease] t2-sql-2023-02-17-16272(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/3823
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=1034
BuildTargetingString
azure-mgmt-sql
Skip.CreateApiReview
true

issue link:https://github.com/Azure/sdk-release-request/issues/3823


support cznic/ql backend

Repeat of #46 - closed without resolution.

Hi, thanks your feedback!
But it's really depends on how far cznic/ql goes and when would xorm supports it.
cc @lunny

It looks to me from what I can see that the issue raised against ql were addressed. It would probably be helpful if the blocking issues that are outstanding actually be listed.

I created a label standby so that people know we're waiting for third-party providers.

Just talked to the author of xorm(@lunny), and ql is almost ready for testing with Gogs, I'm not sure how far it would go(maybe stuck on some wried points), but will start working on it!
just a note of example use ql and xorm: https://github.com/go-xorm/admin

Sorry, I have renamed https://github.com/go-xorm/admin to https://github.com/go-xorm/dbweb. And use github.com/lunny/nodb instead ql to store meta data.

Sorry, I have renamed https://github.com/go-xorm/admin to https://github.com/go-xorm/dbweb. And use http://github.com/lunny/nodb instead http://github.com/cznic/ql to store meta data.

Such a bad guy!

This will not be supported as another better option is coming up. https://github.com/pingcap/tidb

Not good.
That's much younger, less well tested and I can see whole sections of code from other people's work used without attribution (@cznic, take a look at the btree package in kv).

Without attribution? They explecitly say thank you to @cznic and reference to him Oo
And it sounds much better from my point of view, especially the roadmap...

I'm sorry, but a trite sentence doesn't make up for removing the copyright notice on the file. How many other files have been similarly taken.
Roadmap is not implementation. I trust cznic's code because he has an excellent track record of quallity - ql is extensively tested, looking at tidb so far, I don't see that. Further, for a single machine install - why I filed the issue - a distributed db is overkill.

For me, waiting for ql or tidb is same. Both of them are not usable.

If they are the same, don't close the issue.

But we've waited too long for ql and no sign I can see xorm is going to support it fully. :sob:

But we've waited too long for ql and no sign I can see xorm is going to support it fully.

OK, that's a different issue. xorm is the problem.
Question for you, what is a the lowest golang/go issue number? How long has that been waiting?

OK, that's a different issue. xorm is the problem.

It is same in the Gogs's point of view, if xorm is not going to support it, Gogs is not going to, even if ql has all features that Gogs needs.

Question for you, what is a the lowest golang/go issue number? How long has that been waiting?

I don't know and don't need to know. There is no necessity of how long to stop waiting between two projects?

Issues are your memory. If you intentionally forget things because they haven't been done in time, they won't be done.

If you intentionally forget things because they haven't been done in time, they won't be done.

Yes, but decision has to be made.

Yup, I've made a decision.

I'm think sometimes ago for writing cznic/ql support. I don't like xorm and
prefer writing interface for getting and setting needed things. But I'm
switch to gitea, and prepare pr to gitea...
07 сент. 2015 г. 0:04 пользователь "Dan Kortschak"<EMAIL_ADDRESS>написал:

Yup, I've made a decision.
—
Reply to this email directly or view it on GitHub
https://github.com/gogits/gogs/issues/880#issuecomment-138125206.

@kortschak

(@cznic, take a look at the btree package in kv).

Thanks: https://github.com/pingcap/tidb/issues/45


teamchains: hidden chain tests, first batch

introduce determinism into all teamchains
allow to skip tests that aren't currently working
cover about ~13 good teamchain failures with hidden chains
simple_hidden, which is the happy path, to make sure it all works when correct
part 1, expect part 2 in another PR
Works with v1.0.6 of https://github.com/keybase/node-forge-sigchain, now live

I can ignore all the json files?

yes! they are auto-generated from the .iced files

Added your list to https://keybase.atlassian.net/browse/Y2K-434