[BUG] jsonable_encoder crash

Describe the bug
The jsonable_encoder crashes rightfully when passing a list of postgres Records, it's certainly a mis usage on my end, but I think that is something that would be interesting maybe to add in that function

Crash log
Connected to pydev debugger (build 183.5429.31)
backend_1_f0c43d42b730 | WARNING:root:email-validator not installed, email fields will be treated as str.
backend_1_f0c43d42b730 | To install, run: pip install email-validator
backend_1_f0c43d42b730 | DEBUG:app.app:postgresql://postgres:postgres@db:5432/fastapi_dev
backend_1_f0c43d42b730 | INFO:uvicorn:Started server process [1]
backend_1_f0c43d42b730 | INFO:uvicorn:Waiting for application startup.
backend_1_f0c43d42b730 | INFO:uvicorn:Uvicorn running on http://<IP_ADDRESS>:8000 (Press CTRL+C to quit)
backend_1_f0c43d42b730 | Traceback (most recent call last):
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 78, in jsonable_encoder
backend_1_f0c43d42b730 |     encoder = ENCODERS_BY_TYPE[type(obj)]
backend_1_f0c43d42b730 | KeyError: <class 'sqlalchemy.sql.base.ColumnCollection'>
backend_1_f0c43d42b730 |
backend_1_f0c43d42b730 | During handling of the above exception, another exception occurred:
backend_1_f0c43d42b730 |
backend_1_f0c43d42b730 | Traceback (most recent call last):
backend_1_f0c43d42b730 |   File "/opt/.pycharm_helpers/pydev/_pydevd_bundle/pydevd_trace_dispatch_regular.py", line 145, in __call__
backend_1_f0c43d42b730 |     if not is_stepping and cache_key in cache_skips:
backend_1_f0c43d42b730 | RecursionError: maximum recursion depth exceeded in comparison
backend_1_f0c43d42b730 | Fatal Python error: Cannot recover from stack overflow.
backend_1_f0c43d42b730 |
backend_1_f0c43d42b730 | Thread 0x00007f5d9ffa9ae8 (most recent call first):
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/threading.py", line 300 in wait
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/threading.py", line 552 in wait
backend_1_f0c43d42b730 |   File "/opt/.pycharm_helpers/pydev/pydevd.py", line 128 in _on_run
backend_1_f0c43d42b730 |   File "/opt/.pycharm_helpers/pydev/_pydevd_bundle/pydevd_comm.py", line 320 in run
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/threading.py", line 917 in _bootstrap_inner
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/threading.py", line 885 in _bootstrap
backend_1_f0c43d42b730 |
backend_1_f0c43d42b730 | Thread 0x00007f5da00acae8 (most recent call first):
backend_1_f0c43d42b730 |   File "/opt/.pycharm_helpers/pydev/_pydevd_bundle/pydevd_comm.py", line 382 in _on_run
backend_1_f0c43d42b730 |   File "/opt/.pycharm_helpers/pydev/_pydevd_bundle/pydevd_comm.py", line 320 in run
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/threading.py", line 917 in _bootstrap_inner
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/threading.py", line 885 in _bootstrap
backend_1_f0c43d42b730 |
backend_1_f0c43d42b730 | Thread 0x00007f5da01afae8 (most recent call first):
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/threading.py", line 300 in wait
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/queue.py", line 179 in get
backend_1_f0c43d42b730 |   File "/opt/.pycharm_helpers/pydev/_pydevd_bundle/pydevd_comm.py", line 459 in _on_run
backend_1_f0c43d42b730 |   File "/opt/.pycharm_helpers/pydev/_pydevd_bundle/pydevd_comm.py", line 320 in run
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/threading.py", line 917 in _bootstrap_inner
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/threading.py", line 885 in _bootstrap
backend_1_f0c43d42b730 |
backend_1_f0c43d42b730 | Current thread 0x00007f5da6097b88 (most recent call first):
backend_1_f0c43d42b730 |   File "/opt/.pycharm_helpers/pydev/_pydevd_bundle/pydevd_trace_dispatch_regular.py", line 145 in __call__
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/sqlalchemy/sql/operators.py", line 425 in __getitem__
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/sqlalchemy/sql/elements.py", line 707 in operate
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/sqlalchemy/sql/operators.py", line 432 in __getitem__
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 83 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 96 in jsonable_encoder
backend_1_f0c43d42b730 |   File "/usr/local/lib/python3.7/site-packages/fastapi/encoders.py", line 54 in jsonable_encoder
backend_1_f0c43d42b730 |   ...
fastapi_appfactory_backend_1_f0c43d42b730 exited with code 139
Aborting on container exit...

To Reproduce
Here's my simple app, I want to test the databases package from starlette
import logging
from typing import List

from fastapi import FastAPI

from app import settings
from app.settings import database
from app.models import notes, NoteIn

logger = logging.getLogger(__name__)
logger.setLevel(logging.DEBUG)

logger.debug(settings.DATABASE_URL)
app = FastAPI()

app.debug = settings.DEBUG

@app.on_event("startup")
async def startup():
    await database.connect()

@app.on_event("shutdown")
async def shutdown():
    await database.disconnect()

@app.get("/")
async def root():
    logger.debug(database)
    return {"message": "Hello World"}

@app.get("/notes", response_model=List[NoteIn])
async def list_notes():
    query = notes.select()
    results = await database.fetch_all(query)
    # content = [
    #     {"text": result["text"], "completed": result["completed"]} for result in results
    # ]
    # return content
    return results

@app.post("/notes")
async def add_note(note: NoteIn):
    query = notes.insert().values(**note.dict())
    await database.execute(query)
    return note

Should you want I may give you the full gitlab repo address that can reproduce it simply with a docker-compose, instead of copying all files :)
Expected behavior
If I return content instead of results in the list_notes route I got no problem, so that one workaround.
Another workaround is to return
    return [r._row for r in results]
but i don't like much using private attributes
I got the feeling that results, being a list of databases.backends.postgres.Record it might be rightfully "parsed" by jsonable_encoder by adding another if isinstance(obj, blablabla): check
So maybe not a bug, but a possible enhancement ;)
when using DatabaseMiddleware, the fetchall method (note, no underscore in it) return a list of asyncpg.Records which the encoder parsed fine: results = await request.database.fetchall(query)
now we got a list of databases.backends.postgres.Record
Environment:

OS: debian buster
FastAPI Version [e.g. 0.3.0], get it with: 0.5.0

import fastapi
print(fastapi.__version__)

Python version, get it with: 3.7.2

python --version

Additional context
Add any other context about the problem here.

The problem was because Record didn't have an __iter__() method. But it does now (in recent versions).
So, it should work as is now.
I just added docs here: https://fastapi.tiangolo.com/tutorial/async-sql-databases/ :tada: :rocket:
And these same docs are being tested to confirm (and assure) it works correctly.


Set active driver should group logs performed on the browser

All logs after set active driver hold be indented
set active driver ALPHA
    do something
    do something else
set active driver BRAVO
    do something new

Abandoning this feature


Queries over installation

Hi Giulio / All,
I tried to get +liftover going on our systems but found location of a couple of files needs to be detailed -- could anybody point to me?
They are 1kGP_high_coverage_Illumina.sites.vcf.gz,, hs1.fa -- I made attempt to replace them as in here, https://cambridge-ceu.github.io/csd3/applications/bcftools.html#120
As documented files are stored in $HOME/GCRh38 where our system has a limit on $HOME I tried to get them elswhere. In particular, the *.so files are with bin which appears to be available through LD_LIBRARY_PATH as well?
Your comments are greatly appreicated,
JIng Hua

Thank you for the heads up. I need to fix the documentation but to generate the sites only file, this command will do (but it will take a long time):
wget ftp://ftp.1000genomes.ebi.ac.uk/vol1/ftp/data_collections/1000G_2504_high_coverage/working/20220422_3202_phased_SNV_INDEL_SV/1kGP_high_coverage_Illumina.chr{{1..22}.filtered.SNV_INDEL_SV_phased_panel,X.filtered.SNV_INDEL_SV_phased_panel.v2}.vcf.gz
for chr in {1..22} X; do
  if [ $chr == "X" ]; then sfx=".v2"; else sfx=""; fi
  bcftools view --no-version -Ou -c 2 1kGP_high_coverage_Illumina.chr$chr.filtered.SNV_INDEL_SV_phased_panel$sfx.vcf.gz | \
  bcftools annotate --no-version -Ou -x ID,QUAL,FILTER,^INFO/AC,^INFO/AN,^INFO/END,^FMT/GT | \
  bcftools sort -o 1kGP_high_coverage_Illumina.chr$chr.bcf -Ob -T ./bcftools. --write-index
done

bcftools concat --no-version -Ou 1kGP_high_coverage_Illumina.chr{{1..22},X}.bcf | \
  bcftools view --no-version -G -Ob -o 1kGP_high_coverage_Illumina.sites.bcf --write-index

You don't need to store files in the $HOME/GCRh38 directory as any directory of your choice will do. This directory is in the documentation but it is not in the plugins code
As for the *.so files, say you want to run score.so located in the directory /path/to/bcftools/plugins, you can run it as follows (four different options):
export BCFTOOLS_PLUGINS=/path/to/bcftools/plugins && bcftools +score
export BCFTOOLS_PLUGINS=/path/to/bcftools/plugins && bcftools plugin score
bcftools +$BCFTOOLS_PLUGINS/score.so
bcftools plugin $BCFTOOLS_PLUGINS/score.so

You can also compile BCFtools with a default plugin directory which will be hard coded in the binary, but this is not required

Thanks for the feedback -- indeed it appears possible to redinfe HOME to make install there. I did this in a rush without much thinking and I will try your script possibly in SLURM.

Actually setenv in module definition is equivalent to your export under Bash, so it is as indicated. The script for 1kGP_high_coverage_Illumina.sites.bcf generation took ~6hr on our system., which is presumbly (?) used in
cftools norm --no-version -Ou -m+ 1kGP_high_coverage_Illumina.sites.bcf |
bcftools +liftover --no-version -Ou --
-s $public_databases/dbsnp/GCA_000001405.15_GRCh38_no_alt_analysis_set.fna
-f $public_databases/GRCh37_reference_fasta/hs1.fa
-c $public_databases/dbsnp/hg38ToHs1.over.chain.gz |
bcftools sort -o 1kGP_high_coverage_Illumina.sites.hs1.bcf -Ob --write-index
but I got error message: on AC and again warning if with
bcftools norm --no-version -Ou -m+ 1kGP_high_coverage_Illumina.sites.bcf |
bcftools annotate -x INFO/AC -Ou |
bcftools +fill-tags -Ou -- -t AC |
bcftools +liftover --no-version -Ou - --
-s $public_databases/dbsnp/GCA_000001405.15_GRCh38_no_alt_analysis_set.fna
-f $public_databases/GRCh37_reference_fasta/hs1.fa
-c $public_databases/dbsnp/hg38ToHs1.over.chain.gz |
bcftools sort -o 1kGP_high_coverage_Illumina.sites.hs1.bcf -Ob -- -T ./bcftools --write-index

If you used the command above to generate the 1kGP_high_coverage_Illumina.sites.bcf file, then this should be a file without genotypes. You cannot fill the AC tags without genotypes, but if you followed the instructions I sent you should not have to as you should already have that tag. Also notice  that bcftools +fill-tags -- -t AC is terribly slow and bcftools +fill-AN-AC is recommended instead

Thanks very much for the comments. I attempted to walk through the last chunk of your "Liftover VCFs" section, which is
bcftools norm --no-version -Ou -m+ 1kGP_high_coverage_Illumina.sites.vcf.gz |
bcftools +liftover --no-version -Ou --
-s $HOME/GRCh38/GCA_000001405.15_GRCh38_no_alt_analysis_set.fna
-f $HOME/hs1/hs1.fa
-c $HOME/hs1/hg38ToHs1.over.chain.gz
bcftools sort -o 1kGP_high_coverage_Illumina.sites.hs1.bcf -Ob --write-index
but went astray. As you can see that I am far from knowing bcftools enough, and therefor would try your notes above as well. BTW, the code you posted yesterday (wrapped in here, https://cambridge-ceu.github.io/csd3/applications/files/site.sb) did go through smoothly.

Again, you don't need to use bcftools +fill-AN-AC as it will not do anything on a file without genotypes. You are getting the INFO/AC is handled by AC rule message only because the field is in the header, but it will never be present if you remove it first from a VCF without genotypes. As for the warning, that is due to DEL/DUP variants in the VCF which will not always liftover properly as BCFtools/liftover is designed for SNVs and indels. CNVs cannot be easily lifted over in all scenarios

It looks I need to slow down and digest what bcftools does in these cases. Thanks very much for your time..


Use higher base internally for performance

I have noticed that e.g. the documentation explicitly says that the coefficient is single digits (base 10). For my use case, big.js's small size is great, but I'd also like the performance of bigdecimal.js. Is changing the internal base an option?
(Thanks for a great library!)

No, I want to keep this library as base 10. Thanks for the feedback.


Consider Howler 2.0 beta for audio

https://github.com/goldfire/howler.js/tree/2.0

The onload listener is noticeably slower than the one Buzz uses. Might still be worth using at some point. For now, consider using an abstract manager that devs can easily replace.

Closed in preference to https://github.com/ember-theater/ember-theater/issues/15


Refra[LocalStorage]: add unconvertible volume migrate refracture : make unconverible volume generate two replicas

… fix
Signed-off-by: jie.li<EMAIL_ADDRESS>
What this PR does / why we need it:
Refra[LocalStorage]: add unconvertible volume migrate refracture : make unconverible volume generate two replicas
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Codecov Report

Merging #323 (047b650) into main (db6c952) will decrease coverage by 0.51%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #323      +/-   ##
==========================================
- Coverage   16.10%   15.58%   -0.52%
==========================================
  Files          73       74       +1
  Lines        7657     7925     +268
==========================================
+ Hits         1233     1235       +2
- Misses       6301     6567     +266
  Partials      123      123

Impacted Files
Coverage Δ

...ocalvolumemigrate/localvolumemigrate_controller.go
10.00% <0.00%> (-0.72%)
:arrow_down:

...l-storage/member/controller/scheduler/resources.go
25.11% <0.00%> (ø)

...ge/member/controller/volume_migrate_task_worker.go
5.00% <0.00%> (-1.66%)
:arrow_down:

pkg/local-storage/member/csi/controller.go
0.00% <0.00%> (ø)

pkg/local-storage/member/node/config_manager.go
0.00% <0.00%> (ø)

pkg/local-storage/member/node/configer/drbd.go
0.92% <0.00%> (-0.06%)
:arrow_down:

.../local-storage/member/node/storage/executor_lvm.go
0.00% <0.00%> (ø)

...kg/local-storage/member/node/volume_task_worker.go
38.70% <ø> (+0.30%)
:arrow_up:

pkg/local-storage/utils/sysfs.go
0.00% <0.00%> (ø)

.../local-disk-manager/handler/localdisk/localdisk.go
20.25% <0.00%> (-0.53%)
:arrow_down:

... and 1 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Use ConPTY

The description says Windows 10 build 18309 or above is recommended.
It should be Windows 10 build 1809 instead of 18309.

It's version 1903, build 18309: https://en.wikipedia.org/wiki/Windows_10_version_history


Fix a bug that causes sources to stall

:notebook_with_decorative_cover: Description
To reproduce the bug, run the following commands without this fix:
vast start

while true; do
  sleep 30
  cat integration/data/suricat/eve.json
done | vast import suricata

PR to be taken over by @tobim, who as per our call has an idea for another improvement.
:memo: Checklist

[x] All user-facing changes have changelog entries.
[x] The changes are reflected on docs.tenzir.com/vast, if necessary.
[x] The PR description contains instructions for the reviewer, if necessary.

:dart: Review Instructions
n/t

It took me a while to understand the failed test. What happens is the reader returns with stalled after reading the initial lines. It is expected to return normally afterwards because the batch-timeout should trigger. With the changes in the first commit, that does not happen any more, because the subsequent rounds don't produce any data.
The original change was made to fix the blocking of the source actor. It was achieved by making read re-entrant. But while the time-point for last_batch_sent_ was moved to the readers state, the same wasn't done for the produced counter.
I believe the implementation of the readers can be simplified if read() gets a time-point at which it must exit from it's loop, and this time-point is managed in the source.

I can't review this as I've opened the PR, but here's some feedback on your changes @tobim:
I'd like to see better documentation on ec::stalled and ec::timeout. I did not immediately grok the difference when reading the comments currently above their definition.
Generally, this works aside from the unit tests as you mentioned.
For the proposed reader change, can you show the desired API first?

For the proposed reader change, can you show the desired API first?

I would like to avoid spending more cycles here right now. We have the input load-balancing epic in the backlog and we'll revisit the source and reader design at that point.

I implemented a workaround that fixes the immediate problems at the cost of a bit extra complexity. We plan to change the interaction between the source and reader to make it more straightforward soon, I hope this is acceptable in the meantime.

I tested this locally. @tobim feel free to approve. Changelog entry lgtm.


added sp-site creation and sp-site-tmp creation

Added two short PowerShell scripts for creating a SharePoint page using a template and creating the template file.

can you add a readme.md for each folder, where you describe, how to use & what to change?


Create an analysis pass for choosing grid shape

This will have to be a very primitive pass for the time being, but I think this issue should be used as an exercise for creating the boilerplate for an optimization pass.
Let's try to understand the MLIR way of doing this by having an analysis pass run: MLIR analysis pass: https://mlir.llvm.org/docs/Tutorials/DataFlowAnalysis/.
Definitely take a look at llvm-project source for other examples.
Separately, we should have a "dumb" pass that accepts the output from the analysis pass and applies the result.  I think we should strive to frame all of our optimization passes in this way, they should all run in 2 phases:

Complicated analysis pass, treats graph as immutble
Application pass that blindly does whatever the result from the analysis pass says to do

As a first step, let's take our 1x1 eltwise binary and try to put it on more cores.

This should have been resolved with #115 seems like there is a bug where linking isn't working between these two.

This should have been resolved with #115 seems like there is a bug where linking isn't working between these two.

Was just about to close it myself. Thanks!


fix: active language callout on header should be closed once losing focus

Description
active language callout on header should be closed once losing focus
Task Item
Closes #5293
Screenshots

Coverage increased (+0.01%) to 54.474% when pulling 04672b2d4af8fa0450551f1dc02a103da0ab75ab on liweitian:fixCalloutBug into 4fff914b74aca6836ff6034893b5b1c68db22596 on microsoft:main.

Judging by the recording:
Shouldn't the focus go to the popup content when "tab" is pressed while the popup is open?
Here's the sequence:
Press Tab, focus language button, press Enter, Open popup, press Tab: At this point the dropdown language should take the focus, right? (if the dropdown is enabled of course)

Judging by the recording:
Shouldn't the focus go to the popup content when "tab" is pressed while the popup is open?
Here's the sequence:
Press Tab, focus language button, press Enter, Open popup, press Tab: At this point the dropdown language should take the focus, right? (if the dropdown is enabled of course)

tried on main branch. If we have more than one languages, press tab will go to the drop down.


fix for issue Can not create a new meta key ENSPROD-8936

fix for issue , Can not create a new meta key, Jira:  ENSPROD-8936

https://github.com/Ensembl/ensembl-prodinf-masterdb/pull/16, PR needs to be merged first


Update rubocop-rails

For rubocop 1.12.1 and earlier, which support Ruby 2.4, update rubocop-rails to version 2.9.1, the last version supporting Ruby 2.4.
For later rubocop versions, update rubocop-rails to 2.11.2 (the latest as of the time of writing).
You might want to avoid updating rubocop-rails in channels that are already in use, but rubocop-1-12-1 and later should be OK to update because of #289 (PRs #281, #282, #283, #284, #285, #286, #287, #288).

Darn, this needed to happen before all of those PRs were merged, but I didn't write the issue in time.

@BrianHawley 😅 , WDYT of just updating rubocop-rails to 2.11.2 on the rubocop's latest version ? and update the previous ones only if needed ?

Doesn't help me, because I'm stuck on Ruby 2.4 for now. Still, it could help people who are able to use the latest version.

So, if you updated channels 1-12-1 and 1-18-3, that would do.
Okay. I think we can do that then.

Closed by PRs #292 and #294.


Make it obvious that a new cronjob needs to be applied

Adding a new cronjob via System -> Settings -> Cron does not automagically write it to crontab. This behavior could be miss-leading, since the button on the "Add pane" says "Save Changes".
We should either apply the changed cronjob immediately or make it really obvious that changed / new cronjobs need to be applied using the "Apply" button. Right now it looks like the button serves a reload or should be used when changing  the "Enabled" checkbox

Thanks... I ran into this myself today and never noticed the apply button :(


not find train_supervised.py

I don't know how to run this progrm,don't find train_supervised.py.

Hello, thanks for your interest in our work. The standard Dimma approach assumes first to train unsupervised (using artificially dimmed pairs) and later finetune the model in a supervised way (with real pairs). Please, keep in mind that skipping the unsupervised training might make a big difference when you have a small dataset with for example three training pairs.
However, if you want to skip the part with artificial pairs(it should be OK to do that for the full LOL dataset for instance), you can run just the finetune.py script alone. The only thing you need to do is to uncomment line 25 and comment line 26 in finetune.py, like that:
model = LitDimma(config=cfg)
# model = LitDimma.load_from_checkpoint(cfg.model.checkpoint, config=cfg)

This will create a new instance of the network instead of loading the checkpoint from unsupervised training.
Also, make sure to have the right dataset in ./data folder and use the proper config - for the whole LOL dataset it will be
python finetune.py --config="configs/LOL/stage2/large-lol-ft.yaml"

Feel free to ask if you have any more questions or encounter further issues, I am happy to help you.

I don't know how to run this progrm,don't find train_supervised.py.
你好，你解决这个问题了吗，我也没有找到这个文件

Hi, now I spot the problem. In the readme there is a typo - it should not be train_supervised but train_unsupervised. The typo is fixed, sorry for the trouble, and thank you for pointing that out, and thanks for your interest in our work.


qix observables internally throw error when receiving wrong data type?

idea behind qix observables is that they expect, and therefore rely on, values of type QixClass (or extended classes when implemented). therefore, when they get a value, before passing on next they should confirm it is the right type. if it isn't, they should error?

implemented this in a local branch; will publish once I get babel polyfill out @ #7

done in v0.3.0


Added OpenAI Chat template

Content must go through a pre-merge checklist.
Pre-Merge Content Checklist
This documentation has been checked to ensure that:

[ ] The title, template, and date` are all set
[ ] Does this PR have a new menu item (anywhere in templates/*.hbs files) that points to a document .md that is set to publish in the future? If so please only publish the .md and .hbs changes in real-time (otherwise there will be a menu item pointing to a .md file that does not exist)
[ ] File does not use CRLF, but uses plain LF (hint: use cat -ve <filename> | grep '^M' | wc -l and expect 0 as a result)
[ ] Has passed bart check
[ ] Has been manually tested by running in Spin/Bartholomew (hint: use PREVIEW_MODE=1 and run npm run styles to update styling)
[ ] Headings are using Title Case
[ ] Code blocks have the programming language set to properly highlight syntax and the proper copy directive
[ ] Have tested with npm run test and resolved all errors
[ ] Relates to an existing (potentially outdated) blog article? If so please add URL in blog to point to this content.

Thanks @teknicus
Will look at this next and get back to you as soon as possible.

Thanks @teknicus . I will merge this now - I am just going to move some of the content away from tags into keywords section which is also indexed for search capabilities.


cli command: project -> use

Not implemented: unikube project use
Compare to unikube orga use.

implemented by PR #23


Update and rename .py to Convert an array to reduced form.py

Hi @Jeet-programmer
Your code can't be merged as you are not assigned to any issue.
You can try to find new issues from 1st Feb.
Don't create any new issues, You can comment on new issues on 1st Feb. to get assigned.


Remove sensitive everywhere!

Hi, looks like you faced the same issue with opsworks as I did, but you did not remove sensitive in change_password action.

Merged, thanks!


^0.4.0 won't match the new execa version 0.5.0

https://github.com/npm/node-semver#caret-ranges-123-025-004

I will upgrade all my execa dependencies when I have some free time to do manual testing. Thanks though.


docs: api

What's added in this PR

API documentation

What else needs to be added/modified

Authentication
Circular schema reference (wip)

The PR doesn't run at all :Error An error occurred. Failed to load url ../../../components/keyboard.astro (resolved id: ../../../components/keyboard.astro) in /workspaces/d-docs/src/content/docs/tools/api.mdx. Does the file exist?

git pull should fix this

also why are so many files edited?
so no api route's and their related properties are needed?

Thanks, we have found another way to solve API.


feat: support i18n

stories that showed the signin with security key button under the password form

see https://github.com/ory/kratos/pull/3468


make sure you label images

make sure you label perf results in notebooks e.g. which resource did you use, what uinits ...

Sure professor .This is done


Messages.attachments have no attribute "data"

Hey guys, I want to extract data from my Gmail attachments. I am getting the messages but when I try to get a sample attachment I get the following error :-
File "/home/entro/.virtualenvs/AETSV/lib/python2.7/site-packages/django/contrib/auth/decorators.py", line 23, in _wrapped_view
return view_func(request, *args, kwargs)
File "/home/entro/projects/myproject/spreadsheets/views.py", line 67, in index
file_data = base64.urlsafe_b64decode(attachment['data'].encode('UTF-8'))
TypeError: 'HttpRequest' object has no attribute 'getitem'__
Here's my relevant code :-
for message in messages[:4]:
               try:
                   message = service.users().messages().get(userId='me', id=message['id']).execute()
                   print message['id'], message['snippet']
                   for part in message['payload']['parts']:
                       if part['filename']:
                           try:
                               print part['body']['attachmentId']
                               attachment = service.users().messages().attachments().\
                                   get(userId='me', messageId=message['id'], id=part['body']['attachmentId'])
                               file_data = base64.urlsafe_b64decode(attachment['data'].encode('UTF-8'))

Does this have anything to do with my scope? In any case, my scope is scope='https://www.googleapis.com/auth/spreadsheets https://mail.google.com/ '
'https://www.googleapis.com/auth/gmail.readonly',
Thanks in advance!

Oops! I forgot to add .execute() after the get function! My bad!


Right clicking on Triggers doesn't allow Script To

Issue Type: Bug
Open a database and table with a trigger.
Double clicking does nothing.
Right clicking doesn't bring up the menu like all other types of things like Views, functions etc.
It should bring up the ability to script to with the same options as Views and functions.
Azure Data Studio version: azuredatastudio 1.12.2 (c9bef82ace6c67190d0e83820011a2bbd1f793c1, 2019-10-11T04:56:40.634Z)
OS version: Windows_NT x64 10.0.18363

Closing as duplicate of https://github.com/microsoft/azuredatastudio/issues/2093.  I'll use that issue to track since it has more upvotes.  Thanks!


Getting denied error despite valid PAT when pulling image with Docker pull

Describe the bug
I'm getting a denied error even though I created a token with read:packages scope. I can't pull the image.
To Reproduce
Steps to reproduce the behavior:
1 - Create PAT with read:packages scope.
2 - Run docker login using the PAT you created.
3 - Observe if you can log in successfully.
4 - Run docker pull ghcr.io/gsoft-inc/azure-cli-credentials-proxy:latest.
4 - Observe the "denied" error
Expected behavior
I should be able to see that the docker pull command works successfully with the pat I created.

Hi @kadiralan , apologies for the delay and the GitHub packages authentication issue. We'll be publishing the image on Docker Hub soon, so no PAT will be needed.

Hi @kadiralan , I just wanted to let you know that we published the image on Docker Hub, so there will no longer be authentication issues: https://hub.docker.com/r/workleap/azure-cli-credentials-proxy
The README is up-to-date with the right image name. Thanks for your interest!


please look at issue #6976

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting that a supported site is broken
[X] I've verified that I'm running yt-dlp version 2023.03.04 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
No response
Provide a description that is worded well enough to be understood
hello. I am a new user and wanted to inform you about a partially broken extractor which would need fixing.
But it is for a NSFW site and if I post it here as my 1st issue, I will automatically get flagged and my profile hidden by github. So I cannot post the issue here. (The github bot apparently doesn't understand that this is a legitimate user action.)
I have posted the issue in https://github.com/yt-dlp/yt-dlp/issues/6976 but it doesn't publicly appear because my profile is hidden. Can you please look at the issue and greenlight it, so that it will appear publicly?
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
n/a

Github hides the issue from us too. Pls post the verbose log in a comment here. (or maybe in pastebin?)

Please do in pastebin
Pretty sure this issue will be hidden too if you directly paste it here

thanks for your help!
It's a nightmarish trip ...
If I paste it here, it gets banned apparently.
On pastebin I just got this, lol :

Pastebin’s SMART filters have detected potentially offensive or questionable content in your Paste.
The content you are trying to publish has been deemed potentially offensive or questionable by our filters, because of this you’re receiving this warning.
This Paste can only be published with the visibility set to "Private".

un-f....-believable ! : 🤦♂
Can you send me a link where I can paste the log ?

nevermind, I hope this works now:
https://privatebin.net/?b41a2cb52dfa16da#BxxtKCmb9UNePfYrL7rFi5baswnQ2GcQZNBkmyuSg71h
link expires in 3 days, so can you please copy/paste the log here? Thank you.

m3u8 based file formats cannot be downloaded anymore from Y0UP0RN
example URL and log:
yt-dlp https://www.youporn.com/watch/16279318/college-girl-makes-blowjob-in-the-campus-part-1-of-2-maryvincxxx/ -f- --ffmpeg-location ".\FFmpeg\bin" -vU
[debug] Command-line config: ['https://www.youporn.com/watch/16279318/college-girl-makes-blowjob-in-the-campus-part-1-of-2-maryvincxxx/', '-f-', '--ffmpeg-location', '.\\FFmpeg\\bin', '-vU']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>[17ba4343c] (win_exe)
[debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-10-10.0.19045-SP0 (OpenSSL 1.1.1k  25 Mar 2021)
[debug] exe versions: ffmpeg N-110185-gb564ad8eac-20230407 (setts), ffprobe N-110185-gb564ad8eac-20230407
[debug] Optional libraries: Cryptodome-3.17, brotli-1.0.9, certifi-2022.12.07, mutagen-1.46.0, sqlite3-2.6.0, websockets-11.0.2
[debug] Proxy map: {}
[debug] Loaded 1810 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp-nightly-builds/releases/latest
Available version<EMAIL_ADDRESS>Current version<EMAIL_ADDRESS>Current Build Hash: c6e73ff15a5c05d8938eb5d9bf1f38089f67b13671be1b4fa637fead35f217cd
[debug] Downloading _update_spec from https://github.com/yt-dlp/yt-dlp-nightly-builds/releases/latest/download/_update_spec
Updating to<EMAIL_ADDRESS>...
[debug] Downloading yt-dlp.exe from https://github.com/yt-dlp/yt-dlp-nightly-builds/releases/latest/download/yt-dlp.exe
[debug] Downloading SHA2-256SUMS from https://github.com/yt-dlp/yt-dlp-nightly-builds/releases/latest/download/SHA2-256SUMS
Updated yt-dlp to<EMAIL_ADDRESS>[debug] Restarting: yt-dlp "https://www.youporn.com/watch/16279318/college-girl-makes-blowjob-in-the-campus-part-1-of-2-maryvincxxx/" -f- --ffmpeg-location ".\FFmpeg\bin" -vU
[debug] Command-line config: ['https://www.youporn.com/watch/16279318/college-girl-makes-blowjob-in-the-campus-part-1-of-2-maryvincxxx/', '-f-', '--ffmpeg-location', '.\\FFmpeg\\bin', '-vU']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>[b079c26f0] (win_exe)
[debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-10-10.0.19045-SP0 (OpenSSL 1.1.1k  25 Mar 2021)
[debug] exe versions: ffmpeg N-110185-gb564ad8eac-20230407 (setts), ffprobe N-110185-gb564ad8eac-20230407
[debug] Optional libraries: Cryptodome-3.17, brotli-1.0.9, certifi-2022.12.07, mutagen-1.46.0, sqlite3-2.6.0, websockets-11.0.2
[debug] Proxy map: {}
[debug] Loaded 1810 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp-nightly-builds/releases/latest
Available version<EMAIL_ADDRESS>Current version<EMAIL_ADDRESS>Current Build Hash: cadb7b2a28baf48d018e06e68c5d78d809ed55a0e87ca4f5e476d8476494f28f
yt-dlp is up to date<EMAIL_ADDRESS>[YouPorn] Extracting URL: https://www.youporn.com/watch/16279318/college-girl-makes-blowjob-in-the-campus-part-1-of-2-maryvincxxx/
[YouPorn] college-girl-makes-blowjob-in-the-campus-part-1-of-2-maryvincxxx: Downloading JSON metadata
[YouPorn] college-girl-makes-blowjob-in-the-campus-part-1-of-2-maryvincxxx: Downloading webpage
[debug] Formats sorted by: hasvid, ie_pref, lang, quality, res, fps, hdr:12(7), vcodec:vp9.2(10), channels, acodec, filesize, fs_approx, tbr, vbr, abr, asr, proto, vext, aext, hasaud, source, id
[info] Available formats for 16279318:
ID           EXT  RESOLUTION │   FILESIZE   TBR PROTO │ VCODEC    VBR ACODEC  ABR
─────────────────────────────────────────────────────────────────────────────────
0            m3u8 unknown    │                  m3u8  │ unknown       unknown
240p-400k-0  m3u8 240p       │ ~ 19.68MiB  400k m3u8  │ unknown  400k unknown  0k
240p-400k-1  mp4  240p       │    8.20MiB  400k https │ unknown  400k unknown  0k
480p-2000k-0 m3u8 480p       │ ~ 98.39MiB 2000k m3u8  │ unknown 2000k unknown  0k
480p-2000k-1 mp4  480p       │   16.77MiB 2000k https │ unknown 2000k unknown  0k
720p-4000k-0 m3u8 720p       │ ~196.78MiB 4000k m3u8  │ unknown 4000k unknown  0k
720p-4000k-1 mp4  720p       │   35.36MiB 4000k https │ unknown 4000k unknown  0k

Enter format selector: 720p-4000k-0
[info] 16279318: Downloading 1 format(s): 720p-4000k-0
[debug] Invoking hlsnative downloader on "https://ev-h-ph.ypncdn.com/hls/videos/201901/27/204117571/720P_4000K_204117571.mp4/master.m3u8?burst=1200k&rate=214k&validfrom=1682955998&validto=1682970398&hdl=-1&hash=W1kVgLu6fUEQAdtTTlmFGWaXnrM%3D"
[hlsnative] Downloading m3u8 manifest
[hlsnative] Total fragments: 1
[download] Destination: College girl makes blowjob in the Campus (part 1 of 2) - MaryVincXXX [16279318].m3u8
[debug] File locking is not supported. Proceeding without locking
[download] 100% of   13.54KiB in 00:00:00 at 45.03KiB/s

The issue is that the extractor only expects mp4 and doesn't correctly process m3u8? Adding a determine_ext() test and extracting any m3u8 separately with argument ext='mp4' puts this important content in a correctly named container using the native downloader (as above).

solution: quit watching porn


Config multiple server in caddyfile failed with error "Parse error: Unknown directive"

1. What version of Caddy are you running (caddy -version)?
➜  caddy caddy -version
Caddy 0.8.3

2. What are you trying to do?
Using caddy to serve multiple server.
3. What is your entire Caddyfile?
localhost

log /data/caddy/access.log

errors {
    log /data/caddy/error.log
}

gzip

www.zaiqiuchang.com {
    root /data/www
}

zaiqiuchang.com {
    redir https://www.zaiqiuchang.com
}

api.zaiqiuchang.com {
    proxy / zqc-app1:1323
}

4.  What did you expect to see?
running
6. What did you see instead (give full error messages and/or log)?
2016/07/04 17:08:39 Caddyfile:11 - Parse error: Unknown directive 'www.zaiqiuchang.com'
7. How can someone who is starting from scratch reproduce this behavior as minimally as possible?

Hello @jaggerwang,
this should work
'''
localhost {
log /data/caddy/access.log
errors {
log /data/caddy/error.log
}
gzip
}
www.zaiqiuchang.com {
root /data/www
}
zaiqiuchang.com {
redir https://www.zaiqiuchang.com
}
api.zaiqiuchang.com {
proxy / zqc-app1:1323
}
'''

Hello @jaggerwang,
this should work:
localhost {

log /data/caddy/access.log

errors {
    log /data/caddy/error.log
}

gzip
}

www.zaiqiuchang.com {
    root /data/www
}

zaiqiuchang.com {
    redir https://www.zaiqiuchang.com
}

api.zaiqiuchang.com {
    proxy / zqc-app1:1323
}

Hello @jaggerwang,
"To configure multiple servers (virtual hosts) with a single Caddyfile, you must use curly braces around the server block:"

mysite.com {
	root /www/mysite.com
}

sub.mysite.com {
	root /www/sub.mysite.com
	gzip
	log ../access.log
}

https://caddyserver.com/docs/caddyfile

I've already read the doc, and I've already use curly braces around my server as the example. The doc is a little confuse to understand, and there is no full example, just pecies.

With the help of @elcore , I figured it out the correct way to config multiple servers with common config sharing.
➜  caddy cat Caddyfile
www.zaiqiuchang.com {
    import common.conf

    root /data/www
}

zaiqiuchang.com {
    redir https://www.zaiqiuchang.com
}

api.zaiqiuchang.com {
    import common.conf

    proxy / zqc-app1:1323
}

➜  caddy cat common.conf
log /data/caddy/access.log

errors {
    log /data/caddy/error.log
}

gzip

ping @mholt regarding documentation

Glad you got it fixed! :smile:
As for docs, they do say:

To configure multiple servers (virtual hosts) with a single Caddyfile, you must use curly braces around the server block.

I guess I should make the last word ("block") plural ("blocks") -- but it seems pretty clear to me. What is confusing?

@mholt I am experience the same problem and I also wonder how a full example would look, because this gives and error and is pretty simple:
localhost:2015

http://nginx.dev {
    proxy nginx
}

http://apache.dev {
    proxy apache
}

But fails with the weird error: 2016/08/08 19:36:06 /etc/Caddyfile:3 - Parse error: Unknown directive 'http://nginx.dev'

@kevinsimper  See above ^
I changed the wording on the docs to read "all the site blocks" 😛

👍 I think the docs need more full examples with sites also in 😄 Will submit PR


Thinking sphinx rspec unit test

How to test (rspec unit tests) search with thinking sphinx and database cleaner? If I use transaction strategy in database cleaner search doesn't work. If I use truncation strategy search work, but some other tests doesn't work. Show the sample code of test and cofiguration of database cleaner, thanks

For the configuration, I'd do something like this (and note that the order of the before(:each) callbacks matters).
RSpec.configure do |config|
  config.use_transactional_fixtures = false

  config.before(:each) do
    # Default to transaction strategy for all specs
    DatabaseCleaner.strategy = :transaction
  end

  config.before(:each, :sphinx => true) do
    # For tests tagged with Sphinx, use deletion (or truncation)
    DatabaseCleaner.strategy = :deletion
  end

  config.before(:each) do
    DatabaseCleaner.start
  end

  config.append_after(:each) do
    DatabaseCleaner.clean
  end
end

And then I'd tag specific specs to use Sphinx and the deletion/truncation strategy:
it "searches", :sphinx => true do
  # ...
end

This is now covered in the improved testing docs: http://freelancing-gods.com/thinking-sphinx/testing.html


symbol for IE hack was always ignored

as I code height:30px;*height:35px; to hack IE6/7, gulp-sass will compile it to only height:30px; without error.
I have no idea about it, is it a bug?
most projects still DO need to fit IE8- in China :(

Hello
That would be a libsass issue, not a gulp-sass one.
Check https://github.com/sass/libsass

@keats oh I see, but I just figure it out with using <!--[if IE 7 ]><html class="ie7"><! [endif]--> ,and I think this may be a better way to hack lower version of IE.
anyway thx!! xD


tests:ci:lpcxpresso55s06: portability.posix.common.newlib meet hard fault

Describe the bug
portability.posix.common.newlib meet hard fault
Please also mention any information which could help others to understand
the problem you're facing:
new lib can not be enabled for this platform
To Reproduce
Steps to reproduce the behavior:

mkdir build; cd build
cmake -DBOARD=lpcxpresso55s06 -DCONFIG_NEWLIB_LIBC=y ..
make
See error

Expected behavior
TEST PASS
Impact
newlib support
Logs and console output
*** Booting Zephyr OS build zephyr-v3.0.0-1108-ge65e26162199  ***

ASSERTION FAIL [((((size_t)32) << 10) - (((uintptr_t) (&_end)) - 0x20000000)) >= 2048] @ WEST_TOPDIR/zephyr/lib/libc/newlib/libc-hooks.c:129

	memory space available for newlib heap is less than the minimum required size specified by CONFIG_NEWLIB_LIBC_MIN_REQUIRED_HEAP_SIZE

E: r0/a1:  0x00000004  r1/a2:  0x00000081  r2/a3:  0x80000000

E: r3/a4:  0x00006809 r12/ip:  0x00000000 r14/lr:  0x000055a5

E:  xpsr:  0x49000000

E: Faulting instruction address (r15/pc): 0x0000b764

E: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0

E: Current thread: 0x20001960 (main)

E: Halting system

Environment (please complete the following information):

OS: (e.g. Linux, MacOS, Windows)
Toolchain (e.g Zephyr SDK, ...)
Commit SHA or Version used: zephyr-v3.0.0-1108-ge65e26162199

@dleach02 @mmahadevan108 @danieldegrasse


Sometimes not all comments displayed when coming from Notifications

Not all comments are displayed when I switch from notifications directly to comments.
See video. The video starts with me tapping on the bell and then tapping on the new notification.  This brings me to the comment area of a post and I see the new comment.  However, there are far too few comments that are displayed!  If I tap on "Oldest/newest" the actual number is displayed
Github doesnt support mp4, so zipped the video
20190429_134311.mp4.zip

Turns out this is as expected. There is a  "^ Older" button on the left which lets you load earlier comments.
Consider the case when comments are sorted oldest -> newest.
The idea is when coming from a notification, you are taken to that comment highlighted. Then you can press the button on top left to load previous comments, 5 at a time. You can keep pressing the button on the top left.. to go all the way to the oldest comment.


tpl/tplimpl: Fall back from publish date to date in RSS template

Improves #12438

Just to be clear, if we (I) fix #12438 -- then we can close this?

Closing in favor of https://github.com/gohugoio/hugo/pull/12633.


Case sensitivity in queries

It seems that knex (and therefore bookshelf) doesn't have any way to handle case sensitivity, which results in inconsistent results across the various supported databases.
SQLite is case sensitive by default.
MySQL it depends on collation, but usually case insensitive
PostGRES not sure ??
In a related issue in Ghost with regard to tag names which should be case sensitive unique, @halfdan mentioned that ActiveRecord (which I know a lot of newer bookshelf stuff is based upon) allows for this to be determined on a per-query basis:
http://edgeguides.rubyonrails.org/active_record_validations.html#uniqueness
At the moment, I can find no way to make specifically case insensitive or case sensitive queries across all 3 databases and so we're having to do a fetch all & process in JS. I also raised https://github.com/tgriesser/knex/issues/152 whilst investigating this previously in relation to email addresses.
Seems like a reasonably fundamental thing for working with multiple dbs? As per usual with bookshelf/knex I have no idea where to start looking at fixing this (see also https://github.com/tgriesser/knex/issues/46#issuecomment-33230040), so if anyone has guidance I'd love to help getting it fixed.

ping

I would love to see this implemented.

As a work around you can use whereRaw. Just make sure you sanitize!
For full case insensitive search on a column I am using the following:
.whereRaw('LOWER(column) LIKE ?', '%'+value.toLowerCase()+'%');

MySQL is case insensitive. The formatter needs to allow allow for LIKE BINARY and  `REGEXP BINARY

@jimmynavio +1 saved me some time with your workaround

I agree that having a portable case insensitive comparison where function would be great. I'm not sure exactly what it would look like.
I'm going to restore the 'PR Please' tag, @tgriesser.

+1

+1

+1

thanks @ jimmynavio thanks for solution to my issue

@jimmynavio Your solution works fine for me as long as the query does not contain a question mark (although the question mark character alone works, the problem only occurs if it is a combination of a question mark with other characters).
Error: Expected 126 bindings, saw 312\n    at replaceRawArrBindings (/.../node_modules/knex/lib/raw.js:99:11)\n    at Raw.toSQL
In knex/lib/raw.js I found a regular expression that replaces '?' with bindings (line 80, replaceRawArrBindings):
raw.sql.replace(/\?\??/g, function (match) {

I tried to change that expression to [^\]??? in order to be able to escape the question mark but without success (I get a "Syntax Error" for the resulting sql).
Any Idea on how to solve that problem? Or more specific, how can I search for a string that contains a question mark with knex.raw?

Looks like every dialect (mysql, postgres, mssql, sqlite3, oracle) supports lower(string) function so that sounds like good baseline. Also query compilers can be overridden for each dialect e.g. if one likes to use ilike for that on postgres or COLLATE NOCASE with sqlite3.
For explicitly case sensitive comparison... probably mysql is only db which isn't always case sensitive by default so it would need dialect specific implementation e.g by method @esatterwhite suggested.

+1 from this postgres user

That would be awesome. +1

Here's @jimmynavio 's workaround modified a bit 🍡
.whereRaw("LOWER(name) LIKE '%' || LOWER(?) || '%' ", searchText)

me too +1 !

One thing to keep in mind here is that queries using LOWER(column) will not use indexes created for that column, and so a full table scan will be performed, which is obviously bad for all search use cases.
The way to avoid this is to create a new index on LOWER(column), but most people won't know or think to do this.
That's why it's important to have overrides on a per dialect basis as @elhigu suggested, to provide safe and sensible defaults for different possible configurations.

@jcbize How to create new index in migrations with LOWER(column) ?

Also wondering if there's a way make a LOWER(column) index in Postgres from a knex migration - any insight?

don't the knex migrations basically have you just write SQL?
CREATE INDEX lower_column_idx ON table(lower(column))

I'm not really sure what actually should be done here. Since this issue doesn't propose API or tell exactly in which cases one should apply this case sensitivity.
If this is still wanted, please open new issue (and refer this one), which actually describes concrete use-cases and initial API proposal how things should work.

@elhigu you mention overriding  query compilers for each dialect here. Is there more information about this somewhere?

@lehni I'm not sure what are you looking for... the comment was  about internal implementation detail how that can be done in knex. It is not suitable way to workaround this issue. More information is when you look code of compilers of each dialect.

```sql
CREATE INDEX lower_column_idx ON table(lower(column))

can you help me on knex . while i have join operation and where clause need to capmare to the text filed with case insensitive .?

@vladinator1000 your solution works for me, thank you :)

If you wanna do an insensitive search, you can use ilike.
where('colume name', 'ILIKE', '%${search word}%')

will this break switching to sqlite and mysql ?

how can I do a case insensitive order by? with a raw query I could do ORDER BY lower("firstName"), lower("lastName")

It looks like I +1 request for this feature in 2016. I no longer remember
what a knex is. But I'd like to renew my +1, for old times' sake. Lets get
case insensitive order by in whatever this thing is!
On Thu, Mar 4, 2021 at 7:39 PM Andrew Blair<EMAIL_ADDRESS>wrote:

how can I do a case insensitive order by? with a raw query I could do ORDER
BY lower("firstName"), lower("lastName")
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/knex/knex/issues/233#issuecomment-791103948, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AABGJJF5RWMMONFTULVZUGTTCA76NANCNFSM4AN5JTLA
.

any newer issue addressing what to do with whereILike when underlying database does not support it?
i mean where lower(col) like lower('%val%') could be an option but would that be beneficial in any form?


On Success Chunk upload should be 202 Accepted in Documentation

there is a discrepancy within the documentation. Further down at line 4087 the patch chunk upload response status is 204. It appears 204 is the correct response status. not 202.

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "patch-1" git@github.com:wsmidt/distribution.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

It appears 204 is the correct response status. not 202.

I agree there is a discrepancy, but where do you see 204 as the correct value? Based on the code I would think 202 is correct https://github.com/docker/distribution/blob/master/registry/handlers/blobupload.go#L192

Ahh you are correct. Was testing against our internal registry (appears we are responding incorrectly with the 204). Looks like you are returning 202, updated the commit.

@wsmidt This needs to be changed in the docs/spec/api.md.tmpl. You can then generate docs/spec/api.md with make docs/spec/api.md.

If this hasn't been fixed already, it should be done at https://github.com/opencontainers/distribution-spec


chore(ci): Ensure lockfile is respected during MSRV testing

As a hack in cargo-hack, it doesn't respect lockfiles when doing MSRV testing unless --locked is passed in.
This adds that so we make sure we don't run into problems with newer, MSRV-imcompatible dependencies come out that break our build.
See

https://rust-lang.zulipchat.com/#narrow/stream/246057-t-cargo/topic/gix-ref.20CI.20error/near/423319798
https://github.com/taiki-e/cargo-hack/issues/234
https://github.com/taiki-e/cargo-hack/pull/236

https://rust-lang.zulipchat.com/#narrow/stream/246057-t-cargo/topic/gix-ref.20CI.20error/near/423319798

I didn't find out until recently that when doing MSRV testing, they blow away the lockfile because they assume you aren't committing your lockfile and they want to make sure they use a lockfile format that is compatible with your MSRV.

If this were the only reason, we could have changed that behavior without any problem, but unfortunately the fact that cargo has made incompatible lockfile changes in the past complicates problems.
Especially when running locally on a project with updated/uncommitted lockfiles, without this functionality, calling --rust-version/--version-range after a previous build has been generated by the latest cargo will cause the build to fail.
Ideally, I would like to determine on the cargo-hack side which older lockfile formats cause compatibility issues and call generate-lockfile only when necessary, but I'm not sure how much more complicated that would be.

Thanks!
@bors r+

:pushpin: Commit 0564365ff3c7ec47237f828c72fbf985535e0459 has been approved by ehuss
It is now in the queue for this repository.

:hourglass: Testing commit 0564365ff3c7ec47237f828c72fbf985535e0459 with merge 352d2f36430ce202a93e12f7bc5c77ef3e1747d2...

:sunny: Test successful - checks-actions
Approved by: ehuss
Pushing 352d2f36430ce202a93e12f7bc5c77ef3e1747d2 to master...

https://rust-lang.zulipchat.com/#narrow/stream/246057-t-cargo/topic/gix-ref.20CI.20error/near/423319798

I didn't find out until recently that when doing MSRV testing, they blow away the lockfile because they assume you aren't committing your lockfile and they want to make sure they use a lockfile format that is compatible with your MSRV.

If this were the only reason, we could have changed that behavior without any problem, but unfortunately the fact that cargo has made incompatible lockfile changes in the past complicates problems.

I don't see how what we said was different

Especially when running locally on a project with updated/uncommitted lockfiles, without this functionality, calling --rust-version/--version-range after a cargo update or a previous build by the latest cargo will cause the build to fail.
Ideally, I would like to determine on the cargo-hack side which older lockfile formats cause compatibility issues and call generate-lockfile only when necessary, but I'm not sure how much more complicated that would be.

FYI #12861 was merged which makes lockfile generation respect MSRV.
imo if working with a version older than that

If the lockfile exists.  Only generate the lockfile if it isn't present
Maybe add a --generate-lockfile flag to opt-in to the current behavior


still got nothing when writing nothing

even when nothing is commited!!!!

There's a bit of misconception. This is a feature, not a bug.


HDDS-11333. Avoid hard-coded current version in upgrade/xcompat tests

What changes were proposed in this pull request?
Replace hard-coded version number for current in upgrade and xcompat tests.
Only run EC compatibility test for current version.  Previously it was executed twice, once for both 1.3.0 and 1.4.0, but new-cluster.yaml ignores the version number.  EC test is to be improved in HDDS-11334 to cover multiple versions.
https://issues.apache.org/jira/browse/HDDS-11333
How was this patch tested?
CI:
https://github.com/adoroszlai/ozone/actions/runs/10430533094

Thanks @errose28 for the review.


feat: add discord stuff

Please describe the changes this PR makes and why it should be merged:
Status and versioning classification:

Code changes have been tested and working fine, or there are no code changes
This PR changes the library's interface (methods or parameters added)
This PR includes breaking changes (methods removed or renamed, parameters moved or removed)

Codecov Report

Merging #11 (9f1195b) into main (268ed26) will decrease coverage by 7.73%.
The diff coverage is 27.21%.

@@            Coverage Diff             @@
##             main      #11      +/-   ##
==========================================
- Coverage   64.39%   56.65%   -7.74%
==========================================
  Files          30       32       +2
  Lines         469      586     +117
  Branches       90      126      +36
==========================================
+ Hits          302      332      +30
- Misses        167      254      +87

Impacted Files
Coverage Δ

src/lib/Interpreter/Node.ts
50.00% <ø> (ø)

src/lib/Transformer/Object.ts
12.50% <0.00%> (ø)

src/lib/Transformer/String.ts
7.69% <0.00%> (ø)

src/lib/Transformer/DiscordJs.ts
6.49% <6.49%> (ø)

src/lib/Parsers/Format.ts
10.71% <10.71%> (ø)

src/lib/Interpreter/Lexer.ts
80.23% <89.65%> (+10.49%)
:arrow_up:

src/lib/Interpreter/Interpreter.ts
89.01% <100.00%> (ø)

src/lib/Parsers/index.ts
100.00% <100.00%> (ø)

src/lib/Transformer/index.ts
100.00% <100.00%> (ø)

... and 1 more

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


[SQL]Fix upsert SQL template for Postgres plugin

What changed?
Fixes issue #3482 and replace https://github.com/uber/cadence/pull/3484

Why?

How did you test it?
Integration test with local Postgres.
New test is added

Potential risks
Replace on conflict is already broken, so no more risks.

Do you plan to add more unit test before merge it?

Yep, a new test is added.


vue-tsc complains 'vue/jsx-runtime' type issue when using tsx in vue2.7

When I declare tsx within <script lang="tsx></script>", vue-tsc throw TS2307 error.
I have configure vueCompilerOptions.target to 2.7 but it cannot help.
I find the target check has gone in packages/vue-language-core/src/utils/directorySharedTypes.ts
Any why to fix it?

Hi @Fnxxxxo Can you provide me a minimal reproduction?

Hi @Fnxxxxo Can you provide me a minimal reproduction?

This is not a problem with Vue language tools. You can reproduce the problem in a .tsx file using the same code. For TS issues please raise them in the Vue Discord server.


[SR-125] Add rotate algorithm

Previous ID
SR-125

Radar
rdar://problem/19055052

Original Reporter
@gribozavr

Type
Improvement

Status
Reopened

Resolution

Additional Detail from JIRA

Votes
0

Component/s
Standard Library

Labels
Improvement, NewAPIRequest, StarterBug

Assignee
HarieshJay (JIRA)

Priority
Medium

md5: ccc424105bba16b3f829a36e196fe08d

Issue Description:
Swift needs a rotate algorithm, equivalent to std::rotate() in C++.

@natecook1000 I have taken a look at your Swift Evolution proposal. This seems like a pretty interesting issue to start with! Would you be ok with me picking this up where you left it? I would love to apply another proposal taking into account all the feedback received in the review

See earlier comments for tips. This needs an evolution proposal, by the way. If you are interested, I suggest reading though the previous proposal and its review stages.


Style Dictionary example not getting Font-family

The example that generates a sketch file from style dictionary isn't getting the right Fontfamily, right now it creates TextStyles that always have Helvetica as a family.

it needs to use fontName where I was trying fontFamily.
""font-family": style.getFontName()"


Unwanted Function Exported Causing Namespace Conflict

The new autorest.powershell has a breaking change in for the following Autorest versions:
'@autorest/powershell' (~3.0.0->3.0.421)
'@autorest/modelerfour' (4.15.414->4.15.414)
We had a "where" clause that is supposed to remove the conflicting command 'Update-AzsEncryption':
- where:
      verb: Update
      subject: SubscriptionEncryption
    remove: True

The old Autorest versions removed  'Update-AzsEncryption', but the new ones did not as it still ended up in our .psd1 file that was generated for our .nupkg. Here is our README.md:
https://github.com/Azure/azurestack-powershell/blob/master/src/Azs.Subscriptions.Admin/readme.md
This caused the commandlet namespace conflict error below:
PS C:\Users\Administrator>
Install-Module -Name Azs.Subscriptions.Admin -RequiredVersion 1.0.0 -Repository az-azs
PackageManagement\Install-Package : The following commands are already available on this
system:'Update-AzsEncryption'. This module 'Azs.Subscriptions.Admin' may override the existing commands. If you still
want to install this module 'Azs.Subscriptions.Admin', use -AllowClobber parameter.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\2.2.5\PSModule.psm1:9711 char:34
+ ... talledPackages = PackageManagement\Install-Package @PSBoundParameters
+                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (Microsoft.Power....InstallPackage:InstallPackage) [Install-Package],
   Exception
    + FullyQualifiedErrorId : CommandAlreadyAvailable,Validate-ModuleCommandAlreadyAvailable,Microsoft.PowerShell.Pack
   ageManagement.Cmdlets.InstallPackage

@dolauli followed up in a email
This change starts from m4 generator (3.0.+).
The root cause of the issue is in the operationId. Normally, the operationId should follow the format as below.
[group]-[operation]
But as you could see from the swagger, the operationId of update-AzsEncryption is without [group].
    "tags": [
      "Subscriptions"
    ],
    "operationId": "UpdateEncryption",

To follow the operationId naming rule, it should be changed to “Subscriptions-UpdateEncryption”. And I also find some other operationIds that do not follow this rule. E.g. RestoreData, CheckIdentityHealth.
And why this works in previous version is because in previous modeler, if [group] is not provided, we will use the value in “tags” as [group], but this behavior changed in m4, the [group] will be empty if it is not provided.

$key: ''  // here the value of $key is ‘’,  which is because the [group] is not provided in the operationId.
operations:

apiVersions:

version: '2015-11-01'
parameters:

Considering remodeler (m3) autorest team has stopped maintaining remodeler(m3). I strongly recommend your team starts to use the latest autorest.powershell based on m4.
For this specific issue, I think it should be easy to fix by adding [group] in the oeprationId.

Workaround provided.


A Pan-STARRS galaxy and photoz catalogue PS1-STRM

As part of our next big upgrade :
PS1-STRM: Neural network source classification and photometric redshift catalogue for PS1 3π DR1
https://arxiv.org/abs/1910.10167

06/JUL/22

this was not done for Lasair 3 so the title was changed accordingly
@smarttgit reported also that this is on @thespacedoctor 's to do list but it is no longer priority:1

24/OCT/24

reviewed at Lasair SE meeting and agreed low priority and stays on backlog


[CGP-351] Added a minilib for golden testing

This adds a nice way to do testing with nested folders of golden tests. See test/Pretty/Golden/Readable/StdLib for an example of tests structured this way.
Please let's not put golden files together with *.hs files which run tests, because this makes it hard to read our tests and annoying to navigate.
Besides this adds a Common module where common stuff for tests can be put. We have a lot of repetition in tests, so make sure it doesn't grow at least. Right now I expect at least this:
goldenVsDoc :: TestName -> FilePath -> Doc ann -> TestTree

to be useful.
CC'ing @michaelpj just to make sure he'll see this.

Nice idea!

Nice. I'll use these.


Update build.yml

This is to build windows binaries on the actions pane. This should allow for prereleases of autoscan for windows

Great addition. Thanks!


Always wrap CodeHilite code in  tags

Goal
Currently, the HTML generated by CodeHilite

looks like
stuff
  if you are using Pygments
looks like
stuff
 tags if you are not using Pygments.

See logic here: https://github.com/Python-Markdown/markdown/blob/master/markdown/extensions/codehilite.py#L106
I argue that we should always be using the nested  tags in both cases. The code in this PR makes the two cases consistent.
Background
So, backing up a bit:

 indicates that the enclosed text is computer code. It can be used inline. In other words, this is literally rendered with a code tag.

 indicates that the enclosed text's whitespace should be preserved. It creates a block.

Using them together?:

The following example shows how a block of code could be marked up using the pre and code elements.

var i: Integer; ...
from HTML Living Standard/HTML5

"To represent multiple lines of code, wrap the  element within a
 element. The  element by itself only represents a single phrase of code or line of code."
from MDN

Example
# This should render as just a
 tag.
# You get something like if you render with CodeHilite and you are using Pygments.
# This should render as a
 and  tag.
# You get something like if you render with CodeHilite and you **are not** using Pygments,
# and there is no way to opt out, but frankly, I think this is the right way to do it.
Note that there probably no visual difference in your browser, but the underlying HTML structure is different. Use your browser to inspect.
Rationale
We should always be wrapping our code blocks with code tags for a few reasons, I think:

Markdown specs (pick, your, poison) mandates  tags.
No matter which spec you look at, they're always referred to as code blocks. The output should match that.
In this very project, it's already hardcoded that the  tags get produced if you are not using Pygments, but otherwise using Pygments omits them. CodeHilite has been doing it this way for at least 9 years. If the community doesn't like this PR, we should at least be consistent in how we output nonetheless and figure out some other solution to give users control.
The HTML Living Standard, HTML5 and MDN suggest that blocks of code can be marked up with a code tag nested inside a pre tag.

Pygments further has been offering an opt-in keyword argument for  tag wrapping in its HTMLFormatter since version its 2.4 version released May 8, 2019, but we have not been utilizing it.

It offers designers and other consumers of HTML more structure to differentiate between code and other text that may be in the same
 tag.

Breakages

This is a backwards incompatible change for users that expect the output of CodeHilite while using Pygments to not have  tags. In my opinion, I think this will affect a low number of people because of the reasons listed in the rationale. Check the test string updates for how this will look.

For what it's worth, CodeHilite using  tags when no Pygments is present was introduced in a minor version, 2.1.0. I'm not saying that we should necessarily push this and break semantic versioning...again... but if there's some lower bar for this kind of change that I don't know about, then we might be ok.

Non-Breakages
Pygments since it's first major version release, 1.0 (again, current is 2.4.3), has been supporting arbitrary options being passed to its HTMLFormatter. With how this PR is coded, there should be no errors to users using the wrapcode option of at least that version, but the option will only have effect for people with Pygments >2.4.
This PR's Strategy

[x] Always pass in wrapcode=True to the Pygments HTMLFormatter
[x] Update tests
[x] Verify tests pass locally
[ ] Update docs and docstrings

Cool! I hadn't noticed that Pygments added this option. This has always bugged me about Pygments' output. Glad to see it added (in other words, I didn't need all that convincing but its now documented for others so your effort is not waisted).

Pygments since it's first major version release, 1.0 (again, current is 2.4.3), has been supporting arbitrary options being passed to its HTMLFormatter. With how this PR is coded, there should be no errors to users using the wrapcode option of at least that version, but the option will only have effect for people with Pygments >2.4.

That addresses my one concern. Thank you.

For what it's worth, CodeHilite using  tags when no Pygments is present was introduced in a minor version, 2.1.0. I'm not saying that we should necessarily push this and break semantic versioning...again... but if there's some lower bar for this kind of change that I don't know about, then we might be ok.

As it turns out, our next planned release is 3.2, so no problem there anyway.
Update the docs, including the release notes, and I'll merge this.

I updated the docs. Let me know if it's what you're looking for. (I also hope the force push was okay... do you prefer to squash on merge instead?)
Also, ...
As I've been working on this small section of CodeHilite, I have also noticed some gnarly other bits of it. There are options that only apply with/apply without/apply differently depending on Pygments/use_pygments, the Extension interface to it seems out of date with the underlying CodeHilite class (option set differs) and the docs in general could use a pass over.
I'd like to take some time to refactor it if you have the appetite for that.
I'd also like to make Pygments a required package for Python-Markdown to reduce complexity:

Aside from small things like  tags, there are a number of other differences between the code CodeHilite produces depending on Pygments, such as what classes get applied to what tags.
Instead of trying to replicate Pygments with a reduced feature set when it does not exist, I think we should be delegating to it.
There don't seem to be any other 3rd party packages apart from setuptools. How do you feel about requiring that?
This could also be an opportunity to round-out the header parsing logic since there's only one target: Pygments. This was kind of the issue with #822 .

Thoughts?

do you prefer to squash on merge instead

I squash except for those rare occasions were a PR contains a perfect commit.  However, I still used squash so I could add a technical note to the commit message. In other words, as long as the final product is good, I'll happy squash it. GitHub makes that easy with their web interface.

I'd like to take some time to refactor it if you have the appetite for that.

This extension is over a decade old, so yeah, it needs some updating/refactoring which I have not had time to work on. Reviewing some of the open issues/PRs (#334, #775, #652, #822 and perhaps others) will provide some insight into the planned direction. Feel free to ask questions or propose solutions in the various discussions in those issues/PRs.
Note that the extension serves two functions:

Provide a mechanism for defining the language of indented code blocks. This allows the user to add their own code-highlighting (perhaps via a JavaScript lib) separately. The idea is that we replicate the output and behavior of fenced code blocks for indented code blocks.
Highlight the code within all recognized code blocks, including any alternative code blocks provided by extensions. Obviously, this includes fenced code blocks, but should be able to work with code blocks produced by other third party extensions as well.

Note that the extension always performs function 1. However, function 2 can be optionally turned off by the user. Any refactor must maintain this division of functions.

I'd also like to make Pygments a required package for Python-Markdown

As long as CodeHilite is included with Python-Markdown I am not comfortable with this. We are proud of the fact that Python-Markdown has no dependencies (except Setuptools). Many users of Python-Markdown never use or need CodeHilite. Others may use CodeHilite for function 1 (as described above) but never need Pygments. Therefore, we should not require all users of Python-Markdown to have Pygments installed.
We have contemplated breaking extensions out into separate packages. If that were to happen at some point in the future, then yes, requiring Pygments as a dependency would make sense. Until then, I'd prefer to leave the requirement as-is. At this time, we are not planning on breaking out the extensions.


Add issue template for dataset requests

To make the HowTo-EUREC4A book issue tracker the central platform to communicate about datasets, this is one of several issue templates that shall make it easier for EUREC4A data users to request new documentation about datasets and request the addition of datasets to the eurec4a-intake catalog or the publication of a dataset in general.
The idea is that users try to find out the dataset contact person and that the core-team will contact them via email if they don't have a (known) GitHub-handle and are automatically notified about this issue. This way, it is ensured that dataset providers see the interest in their datasets.

@Geet-George @raphvog @d70-t what do you think?

@Geet-George @raphvog, any feedback? Sorry, I just want to see what you think of this. I have more ideas that I would like to deploy but this one would mark the beginning.

Dear Hauke, I think the issue template is great! Thanks a lot for putting it together. I just have the small comment made above.

Great suggestion @raphvog!


[docs] update logo for new branding

New logo featuring "released by Google"
Switched supporter from Nest to Google
Clarified README text for new branding

@Vyrastas, we should also update doc/Makefile.am to reflect the image file list change.

Ah yes, I forgot... fixed.


Generic model needs to be kept in place as buildup of immutable state…

… is based on generic model
Description
Related Issue

Motivation and Context
Prune of models was too aggressive, not considering the usecase for a generic model (environment agnostic) while it is being used for build up of immutable repository. This only hits once all 3 specialized models are present (e.g. configs dedicated to dev,stage & prod) - this overoptimization only hits in this case otherwise there was always the generic model left
How Has This Been Tested?
Adjusted unittests to cover the scenario found downstream during implementation - validation of concrete testproject scenario.
Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

@DominikSuess - did not have the time to review it, but please check the failing tests first.

I think the change is ok, but I'm not 100% sure. If the IT tests still work, I guess we are fine


[cPP CHANGE] FCS_STO_EXT.1 & Application Note 2

What is the change request for the cPP? Please describe.
I don't think it is allowed to specify the requirement to include FCP_COP.1/DataEncryption by the app note.
I am not certain about the last sentence in the app note that says other operations may be needed. If there are other possible options, they should be written in as a selection for that choice (i.e. make the example below a selection within the selection and list out the FCS SFRs that may be applicable).
Describe the solution you'd like
Change the SFR to the following (bold text used to show the change):

FCS_STO_EXT.1.1 The application shall [selection: not store any credentials, invoke the functionality provided by the platform to securely store [assignment: list of credentials], implement functionality to securely store [assignment: list of credentials] using FCS_COP.1/DataEncryption] to non-volatile memory.

Then remove this sentence from Application Note 2

If implement functionality to securely store credentials is selected, then the following components must be included in the ST: FCS_COP.1/DataEncryption.

Describe alternatives you've considered
N/A
Additional context
While the language may be tweaked (not sure about "using" in this phrase), this explicitly mandates that this needs to be done according to FCS_COP.1/DataEncryption.

Related to this issue and issue #28, the SD lists FCS_CKM.1 as a second option but this isn't in the PP's SFR. I think the reference in the SD was to the PBKDF that NIAP had in their AS PP so the SFR reference isn't accurate. Is the intent to disallow PBKDFs moving forward? If not, FCS_COP.1/DataEncryption would need to be selectable as using a PBKDF isn't encryption but has hashing requirements instead. There would also need to be an SFR for hashing like NIAP's FCS_CKM.1(3) Password Conditioning (but reformatted since it doesn't follow the CC standard of iterating an SFR).
This SFR may need some tweaking as using FCS_COP.1 or FCS_CKM.1(3) would cover the securing of credentials but not the storing of them. There should be an assignment to note the storage location similar to this:

FCS_STO_EXT.1.1 The application shall [selection: not store any credentials, invoke the functionality provided by the platform to securely store [assignment: list of credentials], implement functionality to securely store [assignment: list of credentials] in [assignment: storage locations] using [selection: FCS_COP.1/DataEncryption, FCS_CKM.1(3)]] to non-volatile memory.

We made the following change to the SFR:
FCS_STO_EXT.1.1 The application shall [selection: not store any credentials, invoke the functionality provided by the platform to securely store [assignment: list of credentials], implement functionality to securely store [assignment: list of credentials] according to [selection: FCS_COP.1/DataEncryption, FCS_CKM.1/Hash, FCS_CKM.1/KeyedHash] to non-volatile memory.
explicit PBKDF inclusion via it's own SFR is still being considered by the iTC.
@Kneckter Please open a PBKDF feature request if desired.


Help Document

Write a help document, based on the video script
First version of the help doc
https://docs.google.com/document/d/1A8T4IRLWb7tt75PsVJcWflrbHRKlmnL7YBvK3lnbaEA/edit
Video text
https://docs.google.com/document/d/1UvpqF3lRJim4oZTY5hOXQ8T6qH7lOj9QCGuv21EUHl4/edit#heading=h.qmkaxvr4by7

The help document is now complete.  It may be that we want to add some the words to describe the purpose of the ECDE at the top of the document.


Is there a way to access the socket that emitted event?

I need to broadcast whatever changes happened from user1 to user2 (working on the same document) , i couldn't access the socket that emitted the event i'm pretty sure i'm missing something. Thanks in advance.

+1 here


Centralise the Caption , Variable Size Post Shifting Fixing , Name fo…

✅ Name not repeating in caption

✅ Centralised the Caption

✅ Post having captions now has fixed size and can be expanded using Read More and Read Less

@narayan954 Please merge the pull request with the given changes so that I can work upon other issue !!

@narayan954 Please merge the pull request with the given changes so that I can work upon other issue !!

looking into it asap

@narayan954 Please merge the pull request with the given changes so that I can work upon other issue !!

mention the issue number, I'm telling you again

Thanks for the contribution, but please mention issue number and try formatting the code before committing. You may try prettier or any formatter


Rename MalformedNodeId to MalformedNodeIdException

Fixes #16
Changes proposed in this pull request:

Update composer.json
Rename MalformNodeId to MalformNodeIdException

Coverage remained the same at 50.256% when pulling 7423dec2859ee3e9bc30f0a5c7ae84337ae3f2ab on issue-16-rename-malformed-node-id into ae96c24bdd0b68e4bb6ada2257b95fffb0ad3867 on master.

Coverage remained the same at 50.256% when pulling 7423dec2859ee3e9bc30f0a5c7ae84337ae3f2ab on issue-16-rename-malformed-node-id into ae96c24bdd0b68e4bb6ada2257b95fffb0ad3867 on master.


[DNM]: test ci trigger on release-8.4

What is changed and how it works?

Issue Number: Close #xxx

What's Changed:

Related changes

[ ] PR to update pingcap/docs/pingcap/docs-cn:
[ ] Need to cherry-pick to the release branch

Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Release note

/retest

/retest

/retest


Added autocomplete-module-import

autocomplete-module-import
Search & install npm packages from import/require statements

@Shipow This is pretty cool.
If I were you I'd ask/beg/cajole https://github.com/spacegeek224/autocomplete-npm or atom devs if @spacegeek224 is unresponsive as that would be a much, much better name. Heck I'd even rename your package to autocomplete-npm-plus if all else fails.
I haven't tested it but I'd also work with https://atom.io/packages/autocomplete-modules to make sure your suggestions have less priority.
I won't ask you to do it in this PR but we do need an Autocomplete section if you want to set that up.

Hey thanks, these are nice suggestions. We'll see what we can do. I'll keep you posted.

FYI the link is a 404. atom- should be removed. @Shipow @mehcode

Hah. I guess that's what happens when I ignore the issue to add CI to this. Thanks for letting us know. Could you fix that @Shipow ?

I was mentioned here, I haven't checked notifications for a while, is there anything I can do about the apm package?

:wave: @spacegeek224 I actually don't know. I think the only way to transfer ownership of a name is to transfer the repository itself.
So steps for that would be:
1 - @spacegeek224 recreates https://github.com/spacegeek224/autocomplete-npm (yes I believe this step is necessary)
2 - @spacegeek224 transfers the repository to @Shipow

Sure!
Sorry I didn't see this earlier, I initially wanted to make my own autocomplete package, but then forgot about it.

Hello everyone 👋
I worked together with @Shipow on the autocomplete plugin, it would be really awesome to do this 👍
@spacegeek224, could you transfer the repository to me (@proudlygeek) instead? 👼
Thanks!

I already transferred it to @Shipow xD

@spacegeek224  Well I'm sorry but I missed the notification /o\

Would you do it again?
Thx \o/


404 at /cloud/ecs-integration.md

I found a broken link : https://docs.docker.com/cloud/ecs-integration.md
I arrived on this page through: https://docs.docker.com/language/nodejs/deploy/

Issue Fixed. Thank you for reporting the broken link.


WIP: diamond search motion estimation

Currently high precision motion vectors are enabled by default.

I definitely want this too, but can you rebase it on the fullpel only version?

My graphs were made at the default quantizer. Actually, the significant gain for some samples comes from the activation of the high precision motion vector inside the patches.
This is validated by these AWCY runs where I have enabled the high precision motion vectors:
https://beta.arewecompressedyet.com/?job=magsoft_test_high_precision_mv%402019-02-12T16%3A35%3A20.056Z&job=magsoft_diamond_me4_ref%402019-02-12T12%3A15%3A09.323Z
I do not think this pull request has a real interest.

Well, I probably went a bit too quick reanalysing the results.
I'll test what was suggested: adding the subpixel diamond motion estimation over the full pixel one.

Can you disable the high precision motion vector in this patch to isolate its effect?
You can always turn it on and/or add and enable corresponding code for that mode in separate patch.

Sure, I can do this. That would be interesting.
However, this patch conflicts with #873, which will probably be merged before. That is why it may be interesting to take from here the idea of subpixel diamond motion estimation and to rebase it above #873 as @tdaede suggested.

So, I updated this branch with sub-pixel diamond motion estimation above the full-pixel and this seems interesting regarding the encoding time.
Here are the new AWCY runs: https://beta.arewecompressedyet.com/?job=diamond_me4_test%402019-02-18T15%3A32%3A45.972Z&job=subpel_diamond_me2_high_prec%402019-02-18T14%3A32%3A07.187Z&job=subpel_diamond_me_ref%402019-02-18T14%3A29%3A36.872Z

subpel_diamond_me2_high_prec is the branch of this MR
diamond_me4_test is the #873 branch
subpel_diamond_me_ref is the master branch

I rebased the branch.
Here are the new AWCY runs:
https://beta.arewecompressedyet.com/?job=diamond_me2_ref%402019-02-20T10%3A29%3A40.010Z&job=diamond_me2_test%402019-02-20T12%3A53%3A26.595Z

Here are some updated AWCY runs:
https://beta.arewecompressedyet.com/?job=diamond_me2_test%402019-03-04T18%3A34%3A12.581Z&job=diamond_me2_ref%402019-03-04T18%3A34%3A42.544Z


Icon

Add material themed app icon

Hello @saltsoftdrink,
sorry for the missing reply. At this moment, the icon remain the current one, but I will consider to add a themed app icon in the future.
Thank you for your suggestion.


feat: create append only table on the retractable SOURCE FORMAT

Some users change the external append only table's changes with DEBEZIUM. Maybe we should allow to create append only table on the external source with non-append-only format and the behavior is ignoring all delete and update.

Offline discussion: @tabVersion says we can create a json source on the debezium topic


[5.1] Bring property wrappers up-to-date with the proposal under review

Bring property 3wrappers up-to-date with the current proposal under review, which includes:

Add support for composing multiple property wrappers
Rename value to wrappedValue, but support the old name with a warning + Fix-It
Allow both initial-value and explicit initialization to work together
Make the $ property internal when wrappedValue is present

Should fix rdar://problem/51576815

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - b450feaa7f8763de3480b2fcd7713255aebbc9ec