[Fix #13099] Make Style/RedundantRegexpArgument respect the EnforcedStyle of Style/StringLiterals

Fixes #13099.
This PR makes Style/RedundantRegexpArgument respect the EnforcedStyle of Style/StringLiterals. Also, combine the way to get the EnforcedStyle from Style/StringLiterals into StringLiteralHelp.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Is there anything preventing this MR to be merged?

@akimd Only lack of time. :-)


failed make launch to CARLA 0.9.13

CARLA version: 0.9.13
Platform/OS: Ubuntu 18.04
Problem you have experienced: Print error while make launch
What you expected to happen: make launch
Other information (documentation you consulted, workarounds you tried):
Hello!
I knew that update new version CARLA on the current week.
So I was updating it yesterday, but it's not working.

Please give me an advice. Thank you.

i have the seem error.

the same error

Hi all, for the new 0.9.13 version it is necessary to update the engine code. Otherwise you will find these compilation errors.

What if can i reinstall Unreal Engine 4.26? Will it be clear?
I don't know exactly what you mean engine code..

Yeah! It's work.
I have reinstalled Unreal Engine 4.26.2
CARLA Version : 0.9.13
Thanks.

the same error

@Isak-toast Where to download  Unreal Engine 4.26.2 ?  the lastest version is 4.26.1 ?


Train NeuS on indoor scene

Hi,
I want to train SDF-based models on indoor scenes (with Replica dataset for now), so I started with NeuS to have a baseline. The RGB reconstruction is descent (~23 dB after a few hoors of training) but once I export the mesh from the trained model, the mesh is catastrophic. There is basically nothing, only kind of bubbles of points. I tried tuning the bias parameter as I read that it can have some impact but with no sucess.
Is my issue something that somebody had already seen ? Is there some other parameters I should look up to ?
Thanks a lot

Hi, NeuS's reconstruction on indoor scene won't be good, maybe you could enable monocular depth and normal loss. You can also refer to https://github.com/autonomousvision/monosdf for more details.


Add pharokka as a toot to galaxy

I would like to add pharokka as a toot to galaxy. In order to write the wrapper, I would need a small DB that can be added for the test case. Could you provide a minimal example of the DB, that can be used for this purpose. The DB would need to allow for the execution of the tool, the output does not need to be meaningful. The real DB can be added to galaxy instance later.

Hi Paul,
I would absolutely love this and would really appreciate you doing it! I’ll sort this out tomorrow, how small would the DB need to be? Perhaps it may better to continue this discussion over email if you prefer<EMAIL_ADDRESS>.
George

There we go https://usegalaxy.eu/?tool_id=toolshed.g2.bx.psu.edu%2Frepos%2Fiuc%2Fpharokka%2Fpharokka%2F1.2.1%2Bgalaxy1&version=1.2.1 galaxy1


how to properly add notificator?:)

Hi,
Sorry for the silly question, but can anyone advise how to properly add notificator to Alfred's workflow?

Add the script anywhere you want inside the Workflow’s directory and call it with Bash, or Zsh, or from whichever language you’re using.
Unless you’re building a Workflow with code, use Alfred’s native object.


[FEATURE] Add an example to use models from TheBloke

Describe the solution you'd like
It would be interesting to have an example showing how to use downloadable models directly.
Describe alternatives you've considered
I've considered using ooglaboogla or other user-interfaces to do the download, but I'd like to have a local solution, scriptable from the commandline to automate the testing of newly released models
Additional context
Here's what I've tried:
from transformers import AutoTokenizer
from auto_gptq import AutoGPTQForCausalLM
import logging

logging.basicConfig(format="%(asctime)s %(levelname)s [%(name)s] %(message)s", level=logging.INFO, datefmt="%Y-%m-%d %H
:%M:%S")
quantized_model_dir="guanaco-65B-GPTQ"
repo_id = f"TheBloke/{quantized_model_dir}"
tokenizer = AutoTokenizer.from_pretrained(repo_id, use_fast=True)
model = AutoGPTQForCausalLM.from_quantized(repo_id, device="cuda:0", use_safetensors=True)

print(tokenizer.decode(model.generate(**tokenizer("auto_gptq is", return_tensors="pt").to(model.device))[0]))

This downloads 2 files (quantize_config.json and config.json) then errors out with:
FileNotFoundError: Could not find model in TheBloke/guanaco-65B-GPTQ due to raise FileNotFoundError(f"Could not find model in {model_name_or_path} : " + model_name_or_path) in auto_gptq/modeling/_base.py", line 721
The missing files are visible on https://huggingface.co/TheBloke/guanaco-65B-GPTQ/tree/main

Hi Charlotte
The issue is that most of my models use a custom model file name. Therefore AutoGPTQ has to be told what model file to download.
On my recent GPTQ uploads I have started including example AutoGPTQ code, exactly like you suggest.  But I've not yet gone back to add that to the slightly older repos.
Here's that example code as it should be for Guanaco 65B:
from transformers import AutoTokenizer, pipeline, logging
from auto_gptq import AutoGPTQForCausalLM, BaseQuantizeConfig
import argparse

model_name_or_path = "TheBloke/guanaco-65B-GPTQ"
model_basename = "Guanaco-65B-GPTQ-4bit.act-order"

use_triton = False

tokenizer = AutoTokenizer.from_pretrained(model_name_or_path, use_fast=True)

model = AutoGPTQForCausalLM.from_quantized(model_name_or_path,
        model_basename=model_basename,
        use_safetensors=True,
        trust_remote_code=False,
        device="cuda:0",
        use_triton=use_triton,
        quantize_config=None)

prompt = "Tell me about AI"
prompt_template=f'''### Human: {prompt}
### Assistant:'''

print("\n\n*** Generate:")

input_ids = tokenizer(prompt_template, return_tensors='pt').input_ids.cuda()
output = model.generate(inputs=input_ids, temperature=0.7, max_new_tokens=512)
print(tokenizer.decode(output[0]))

# Inference can also be done using transformers' pipeline

# Prevent printing spurious transformers error when using pipeline with AutoGPTQ
logging.set_verbosity(logging.CRITICAL)

print("*** Pipeline:")
pipe = pipeline(
    "text-generation",
    model=model,
    tokenizer=tokenizer,
    max_new_tokens=512,
    temperature=0.7,
    top_p=0.95,
    repetition_penalty=1.15
)

print(pipe(prompt_template)[0]['generated_text'])

The key difference being the addition of the model_basename.
I'm not sure PanQiWei is going to want to add an example to AutoGPTQ, given there are already generic examples of how to download models.  But I  am already including it with my newer model READMEs  and will prioritise updating all my older GPTQ READMEs to include this example. Hopefully I will get that done this week.


certstrap 0.1.0 (new formula)

This adds the certstrap formula to head-only. Will push to homebrew
stable if square decides to tag a release.
refs Homebrew/homebrew #45280

==> audit problems
homebrew/head-only/certstrap:
 * Description is too long. "name: desc" should be less than 80 characters.
Length is calculated as homebrew/head-only/certstrap + desc. (currently 93)

Sorry for the late response.
We’re deprecating this repository and won’t accept new formulae. It seems like upstream recently tagged a release for this so you should be able to submit it to the core repository instead. Thanks!


Make find_case_number_docket_template appearance conditional on going down case.net branch?

I understand now why this template still shows even when user did not select case.net path. We want to encourage them to find the case number. Closing as not planned.


Modbus TCP server with different Unit IDs

I'm submitting a question to get some help
I have a Modbus TCP server acting as a gateway for slave devices.
The server has an IP address and each slave has a Unit ID.
I am using node-red-contrib-modbus. I want to set up a test server that can simulate my real-world device and test the coils in the slave devices independently.
I have set up a write to UNIT IDs coils 1-4 and set up Reads from coils 1-4
When I write to one of the Unit IDs the value appears on all the Unit IDs not just the one, I wrote to.
When I read from the server the buffers read the same values on all Unit IDs.
I cannot get the coils on each UNIT ID to act independently.
I have tried both TCP and RTU-BUFFERED types on the client with no difference.
I would appreciate any advice to be able to read and write to the server and see the different Unit IDs with different values.
Thanks for your help.
Below is a flow to reproduce what I am doing.
[{"id":"3e64b5bd.d952ea","type":"modbus-server","z":"81ec175d.437d98","name":"BMS","logEnabled":false,"hostname":"<IP_ADDRESS>","serverPort":"502","responseDelay":100,"delayUnit":"ms","coilsBufferSize":10000,"holdingBufferSize":10000,"inputBufferSize":10000,"discreteBufferSize":10000,"showErrors":false,"x":270,"y":40,"wires":[[],[],[],["7cd35ce0.0c4634"]]},{"id":"11d44fc6.f22bd","type":"inject","z":"81ec175d.437d98","name":"","topic":"","payload":"","payloadType":"date","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":120,"y":40,"wires":[["3e64b5bd.d952ea"]]},{"id":"7cd35ce0.0c4634","type":"debug","z":"81ec175d.437d98","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","x":490,"y":60,"wires":[]},{"id":"9cce7256.a8396","type":"modbus-write","z":"81ec175d.437d98","name":"UNIT ID 1 Fault","showStatusActivities":true,"showErrors":true,"unitid":"1","dataType":"Coil","adr":"0","quantity":"1","server":"bd31c2d6.405ec","x":280,"y":140,"wires":[[],["e1fa5c1d.e0c5e"]]},{"id":"73d539fc.034288","type":"inject","z":"81ec175d.437d98","name":"True","topic":"","payload":"true","payloadType":"bool","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":110,"y":120,"wires":[["9cce7256.a8396"]]},{"id":"e1fa5c1d.e0c5e","type":"debug","z":"81ec175d.437d98","name":"","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","x":490,"y":140,"wires":[]},{"id":"2ae3012.7f829fe","type":"modbus-write","z":"81ec175d.437d98","name":"UNIT ID 1 CMD","showStatusActivities":false,"showErrors":false,"unitid":"1","dataType":"Coil","adr":"1","quantity":"1","server":"bd31c2d6.405ec","x":280,"y":260,"wires":[[],["b23f5f1a.3ad05"]]},{"id":"3c67f7be.edb8a8","type":"inject","z":"81ec175d.437d98","name":"True","topic":"","payload":"true","payloadType":"bool","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":110,"y":240,"wires":[["2ae3012.7f829fe"]]},{"id":"b23f5f1a.3ad05","type":"debug","z":"81ec175d.437d98","name":"","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","x":490,"y":260,"wires":[]},{"id":"4fd62eed.4cf9d","type":"modbus-write","z":"81ec175d.437d98","name":"UNIT ID 2 Fault","showStatusActivities":false,"showErrors":false,"unitid":"2","dataType":"Coil","adr":"0","quantity":"1","server":"bd31c2d6.405ec","x":280,"y":380,"wires":[[],["c506517b.f2eab"]]},{"id":"370bbb70.cda454","type":"inject","z":"81ec175d.437d98","name":"True","topic":"","payload":"true","payloadType":"bool","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":110,"y":360,"wires":[["4fd62eed.4cf9d"]]},{"id":"c506517b.f2eab","type":"debug","z":"81ec175d.437d98","name":"","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","x":490,"y":380,"wires":[]},{"id":"5c68dc43.dba214","type":"modbus-write","z":"81ec175d.437d98","name":"UNIT ID 2 CMD","showStatusActivities":false,"showErrors":false,"unitid":"2","dataType":"Coil","adr":"1","quantity":"1","server":"bd31c2d6.405ec","x":280,"y":500,"wires":[[],["26a327dd.d61b38"]]},{"id":"94b5c0e0.cafb1","type":"inject","z":"81ec175d.437d98","name":"True","topic":"","payload":"true","payloadType":"bool","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":110,"y":480,"wires":[["5c68dc43.dba214"]]},{"id":"26a327dd.d61b38","type":"debug","z":"81ec175d.437d98","name":"","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","x":490,"y":500,"wires":[]},{"id":"edb5d773.ba8318","type":"modbus-write","z":"81ec175d.437d98","name":"UNIT ID 3 Fault","showStatusActivities":false,"showErrors":false,"unitid":"3","dataType":"Coil","adr":"0","quantity":"1","server":"bd31c2d6.405ec","x":900,"y":140,"wires":[[],["ed152390.37192"]]},{"id":"c8b2f175.343ea","type":"inject","z":"81ec175d.437d98","name":"True","topic":"","payload":"true","payloadType":"bool","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":730,"y":120,"wires":[["edb5d773.ba8318"]]},{"id":"ed152390.37192","type":"debug","z":"81ec175d.437d98","name":"","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","x":1110,"y":140,"wires":[]},{"id":"60cb488b.7845b8","type":"inject","z":"81ec175d.437d98","name":"False","topic":"","payload":"false","payloadType":"bool","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":730,"y":180,"wires":[["edb5d773.ba8318"]]},{"id":"988d202b.0d8e6","type":"modbus-write","z":"81ec175d.437d98","name":"UNIT ID 3 CMD","showStatusActivities":false,"showErrors":false,"unitid":"3","dataType":"Coil","adr":"1","quantity":"1","server":"bd31c2d6.405ec","x":900,"y":260,"wires":[[],["6efb46a8.ced388"]]},{"id":"a2689cb4.baa78","type":"inject","z":"81ec175d.437d98","name":"True","topic":"","payload":"true","payloadType":"bool","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":730,"y":240,"wires":[["988d202b.0d8e6"]]},{"id":"6efb46a8.ced388","type":"debug","z":"81ec175d.437d98","name":"","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","x":1110,"y":240,"wires":[]},{"id":"ffd6e866.8ad168","type":"inject","z":"81ec175d.437d98","name":"False","topic":"","payload":"false","payloadType":"bool","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":730,"y":300,"wires":[["988d202b.0d8e6"]]},{"id":"70a311c3.ad4c3","type":"modbus-write","z":"81ec175d.437d98","name":"UNIT ID 4 Fault","showStatusActivities":false,"showErrors":false,"unitid":"4","dataType":"Coil","adr":"0","quantity":"1","server":"bd31c2d6.405ec","x":900,"y":380,"wires":[[],["9adc79a5.7609d8"]]},{"id":"38f73f6f.cc0b9","type":"inject","z":"81ec175d.437d98","name":"True","topic":"","payload":"true","payloadType":"bool","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":730,"y":360,"wires":[["70a311c3.ad4c3"]]},{"id":"9adc79a5.7609d8","type":"debug","z":"81ec175d.437d98","name":"","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","x":1110,"y":360,"wires":[]},{"id":"c164d4c6.de2198","type":"inject","z":"81ec175d.437d98","name":"False","topic":"","payload":"false","payloadType":"bool","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":730,"y":420,"wires":[["70a311c3.ad4c3"]]},{"id":"ab9b09e0.9b77c8","type":"modbus-write","z":"81ec175d.437d98","name":"UNIT ID 4 CMD","showStatusActivities":false,"showErrors":false,"unitid":"4","dataType":"Coil","adr":"1","quantity":"1","server":"bd31c2d6.405ec","x":900,"y":500,"wires":[[],["ae8f1533.3aa2a8"]]},{"id":"9c609fed.a28e9","type":"inject","z":"81ec175d.437d98","name":"True","topic":"","payload":"true","payloadType":"bool","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":730,"y":480,"wires":[["ab9b09e0.9b77c8"]]},{"id":"ae8f1533.3aa2a8","type":"debug","z":"81ec175d.437d98","name":"","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","x":1110,"y":460,"wires":[]},{"id":"6a79feb1.c2606","type":"inject","z":"81ec175d.437d98","name":"False","topic":"","payload":"false","payloadType":"bool","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":730,"y":540,"wires":[["ab9b09e0.9b77c8"]]},{"id":"7961661d.09e688","type":"modbus-flex-getter","z":"81ec175d.437d98","name":"Read_MB","showStatusActivities":false,"showErrors":false,"logIOActivities":false,"server":"716ecd11.6a2384","useIOFile":false,"ioFile":"","useIOForPayload":false,"x":1020,"y":700,"wires":[[],["7ad52f9a.ff38f"]]},{"id":"329ec0ae.73d1b","type":"inject","z":"81ec175d.437d98","name":"Read","topic":"","payload":"true","payloadType":"bool","repeat":"","crontab":"","once":false,"x":110,"y":700,"wires":[["9d8d150f.236938"]]},{"id":"8b974a86.37eeb8","type":"function","z":"81ec175d.437d98","name":"Read_UNIT ID_Ft_Rt_1_4","func":"msg.topic = "AHU"\n\nvar ID = msg.unit\n\nmsg.payload = {  \n'fc': 1, \n'unitid': ID, \n'address': 0 , \n'quantity': 2 } \nreturn msg;","outputs":1,"noerr":0,"x":640,"y":700,"wires":[["1e97989d.315ad7"]]},{"id":"9d8d150f.236938","type":"function","z":"81ec175d.437d98","name":"ID_generator","func":"var m_out=[]; //array for message objects\nvar unitID=0;\nfor (i=1;i<5;i++){\n    \n    unitID=i; //add count \n    var newmsg={unit:unitID,topic:"Unit"+unitID}\n    m_out.push(newmsg);\n}\nreturn[m_out];","outputs":1,"noerr":0,"x":270,"y":700,"wires":[["2a656679.d4004a"]]},{"id":"2a656679.d4004a","type":"switch","z":"81ec175d.437d98","name":"1-4 UNIT ID","property":"unit","propertyType":"msg","rules":[{"t":"btwn","v":"1","vt":"num","v2":"4","v2t":"num"}],"checkall":"true","repair":false,"outputs":1,"x":430,"y":700,"wires":[["8b974a86.37eeb8"]]},{"id":"7ad52f9a.ff38f","type":"debug","z":"81ec175d.437d98","name":"","active":true,"console":"true","complete":"payload","x":1200,"y":700,"wires":[]},{"id":"1e97989d.315ad7","type":"delay","z":"81ec175d.437d98","name":"","pauseType":"rate","timeout":"1","timeoutUnits":"seconds","rate":"5","nbRateUnits":"1","rateUnits":"second","randomFirst":"1","randomLast":"5","randomUnits":"seconds","drop":false,"x":850,"y":700,"wires":[["7961661d.09e688"]]},{"id":"b62ad208.c2ad9","type":"inject","z":"81ec175d.437d98","name":"False","topic":"","payload":"false","payloadType":"bool","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":110,"y":540,"wires":[["5c68dc43.dba214"]]},{"id":"b8f2b696.455898","type":"inject","z":"81ec175d.437d98","name":"False","topic":"","payload":"false","payloadType":"bool","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":110,"y":420,"wires":[["4fd62eed.4cf9d"]]},{"id":"8e723a00.c73908","type":"inject","z":"81ec175d.437d98","name":"False","topic":"","payload":"false","payloadType":"bool","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":110,"y":300,"wires":[["2ae3012.7f829fe"]]},{"id":"423e7f15.4999","type":"inject","z":"81ec175d.437d98","name":"False","topic":"","payload":"false","payloadType":"bool","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":110,"y":180,"wires":[["9cce7256.a8396"]]},{"id":"bd31c2d6.405ec","type":"modbus-client","z":"","name":"BMS","clienttype":"tcp","bufferCommands":true,"stateLogEnabled":false,"tcpHost":"<IP_ADDRESS>","tcpPort":"502","tcpType":"TPC-RTU-BUFFERED","serialPort":"/dev/ttyUSB","serialType":"RTU-BUFFERD","serialBaudrate":"9600","serialDatabits":"8","serialStopbits":"1","serialParity":"none","serialConnectionDelay":"100","unit_id":2,"commandDelay":1,"clientTimeout":1000,"reconnectTimeout":2000},{"id":"716ecd11.6a2384","type":"modbus-client","z":"","name":"BMS","clienttype":"tcp","bufferCommands":true,"stateLogEnabled":false,"tcpHost":"<IP_ADDRESS>","tcpPort":"502","tcpType":"TPC-RTU-BUFFERED","serialPort":"/dev/ttyUSB","serialType":"RTU-BUFFERD","serialBaudrate":"9600","serialDatabits":"8","serialStopbits":"1","serialParity":"none","serialConnectionDelay":"100","unit_id":"","commandDelay":"1","clientTimeout":"1000","reconnectTimeout":"2000"}]

Device :
Linux: v
- Name: IOT 2040 running Linux Yocto
- Version:2.1

Description of the connecting Modbus system:

Name   : JACE 8000
Version: Niagara 4: 4.1
Vendor : Tridum
Link   : https:// https://www.tridium.com/~/media/tridium/enterprisesecurity/documents/jace 8000 ds new tridium.ashx?la=es-mx

node-red-contrib-modbus version: ``
node --version =v0.20.5

Maybe use a Flex-Server?
If you could provide your flow properly formated (code tags would be nice). I could have a look.

Thanks for the reply.
I tried the Flex-Server but was not able to resolve the issue.
I had success testing the node-red flow using a third party Modbus slave simulator.


setup.py crashes when get_config_var returns None

In the 1.5.9 tag, if get_config_var returns None, the built of the given extension will fail deep in the guts of searching for include files. This is found in two places, once for the _speedups extension (~line 179), and once for the _vectorized extension (~line 204).
My suggestion is to build the include_dirs lists outside of the DistutilsExtension constructor arguments, and perform None Checks, something like:
include_dirs = [id for id in include_dirs if id is not None]

@Andyjo07 since the release of 1.5.9 we've removed the use of get_config_var()
https://github.com/Toblerity/Shapely/commit/fddbb0d15cdc8086b168eb627e36390686312abb
I don't think a filter for None will be needed now.


Is it possible to programatically jump to page?

Sure, use a PageController then animateToPage. PageViewIndicator should follow it through pageIndexNotifier.


Push to swift registry fails with: error parsing content-length

I am trying to get registry with swift storage driver to work, but I get an error when pushing (when using filesystem storage driver, everything works as excepcted).
Docker versions
 $ docker version
Client:
 Version:      1.9.0
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   76d6bc9
 Built:        Tue Nov  3 17:29:38 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.9.0
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   76d6bc9
 Built:        Tue Nov  3 17:29:38 UTC 2015
 OS/Arch:      linux/amd64

$ docker info
Containers: 53
Images: 369
Server Version: 1.9.0
Storage Driver: aufs
 Root Dir: /www/docker/docker/aufs
 Backing Filesystem: extfs
 Dirs: 477
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.18.19-zen
Operating System: Debian GNU/Linux 8 (jessie)
CPUs: 24
Total Memory: 1.96 GiB
Name: td-jessie
ID: RTOO:4YNE:INVH:TTNN:W5YV:2TYZ:NCCT:7SYD:AZFB:EZKT:ZN6R:7L5B
Username: dohnto
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

$ docker exec swift_registry_1 registry -v
registry github.com/docker/distribution v2.2.0

The command line you used to launch your Registry
I use docker-compose
registry:
        image: registry:2.2.0
        ports:
                - 11111:5000
        volumes:
                - ./config.yml:/config.yml
        command: /config.yml

config.yml:
version: 0.1
log:
  fields:
    service: registry
storage:
    cache:
        blobdescriptor: inmemory
    swift:
        username: registry_test:registry_test
        password: pass
        authurl: http://swift/auth/v1.0
        container: swift
        insecureskipverify: true
        rootdirectory: /swift/object/name/prefix
http:
    addr: :5000
    secret: "secret"
    headers:
        X-Content-Type-Options: [nosniff]
health:
  storagedriver:
    enabled: true
    interval: 10s
    threshold: 3

Reproducer
$ docker tag ubuntu localhost:11111/pes
$ docker push localhost:11111/pes
The push refers to a repository [localhost:11111/pes] (len: 1)
e9ae3c220b23: Image already exists
a6785352b25c: Image already exists
0998bf8fb9e9: Image push failed
error parsing content-length: strconv.ParseInt: parsing "": invalid syntax

Docker daemon log
DEBU[0094] Calling POST /v1.21/images/localhost:11111/pes/push
INFO[0094] POST /v1.21/images/localhost:11111/pes/push?tag=
DEBU[0094] Trying to push localhost:11111/pes to https://localhost:11111 v2
DEBU[0094] Error getting v2 registry: Get https://localhost:11111/v2/: tls: oversized record received with length 20527
DEBU[0094] Trying to push localhost:11111/pes to http://localhost:11111 v2
DEBU[0094] Checking "" against graph.Repository{"latest":"e9ae3c220b23b699cb5e6914af806219b028c78d5cf6fed8eeca98ffaa8c9b43"}
DEBU[0094] Pushing repository: pes:latest
DEBU[0094] Pushing layer: e9ae3c220b23b699cb5e6914af806219b028c78d5cf6fed8eeca98ffaa8c9b43
DEBU[0094] Pushing layer: a6785352b25c7398637e5ab5a6e989b8371f5dfdf72d9a6cdb00742f262a223e
DEBU[0094] Pushing layer: 0998bf8fb9e9a5603891f2bfc059555ea8f655c54fe0322f62ea7cb33120b445
DEBU[0094] Not continuing with error: error parsing content-length: strconv.ParseInt: parsing "": invalid syntax

Given that the filesystem driver works ok, there is something up with your swift setup.  It looks like a Content-Length headers is not being sent with the response.
How are you running swift?  Can you provide the registry and swift logs?

@RichardScothern Is this error coming from the client? Is this happening when the client is redirected to swift? Perhaps, we should modify that error message to include url and indicate that the target endpoint doesn't have a content-length header.

The error message is misleading - it almost certainly does mean that the header is missing (rather than empty).  I will improve the message.

Thank you for your answers. I dont know where to go next. I dont have really access to the swift. There is nothing in the registry log, and I checked all the files in swift, and they all have Content Length correctly set.
Can you determine, which communication is failing? Is it between the docker client and swift or docker registry and swift or even docker registry and docker client?

hi @dohnto : the error is raised by the code in the docker client.  The registry sets the headers correctly and, as you noted, it works fine with non-swift storage backends.  So, the working hypothesis is that the registry is redirecting the client to swift, which is not sending the required header.  Unfortunately, it's difficult to debug without more information.  For instance without the requested registry logs, I cannot validate the above assumption (it would log a redirect being issued).
Which version of swift are you using?
I'm a little confused about your assertion that all the files in swift have a correct content length.  What exactly do you mean?  If you don't have access to swift, are you able to use a proxy to sniff the headers off the connection?

Ok, I will close this issue. The problem was a varnish cache standing before swift, which sometimes (when requesting HEAD of a file) did not returned content-length.
Thank you all for help.

@dohnto I think we still have a bug here. Let's track this to get the header parsing fix to give an actionable error message. It likely took some investigation to hunt down the varnish issue.

I face the same issue with ali oss.
config.yml
storage:
    cache:
        blobdescriptor: inmemory
    delete:
        enabled: true
    redirect:
        disable: ture

# docker push myregistry:5000/hello-world:1.0.0
The push refers to a repository [<IP_ADDRESS>:5000/hello-world] (len: 1)
0a6ba66e537a: Image push failed
error parsing content-length: strconv.ParseInt: parsing "": invalid syntax

When I enable the redirect, I can push successful.
config.yml
storage:
    cache:
        blobdescriptor: inmemory
    delete:
        enabled: true
    redirect:
        disable: false

# docker push myregistry:5000/hello-world:1.0.0
The push refers to a repository [<IP_ADDRESS>:5000/hello-world] (len: 1)
0a6ba66e537a: Pushed
b901d36b6f2f: Pushed
1.0.0: digest: sha256:ca706f4f5c1e75033c0d9743b5b015f046ae1b645fe18ad3ef35a79c52652825 size: 2743

@firelyu Please don't post on every open issue that is similar to yours. These issues have been characterized and closed out. The correct venue for troubleshooting is either through the mailing list or IRC.
As indicated above, check that whatever is serving your registry content sets the Content-Length header. This will also be fixed in the next version of docker, so waiting may be sufficient.

Sure. Got it.

在 2016年1月23日，上午3:49，Stephen Day<EMAIL_ADDRESS>写道：
@firelyu https://github.com/firelyu Please don't post on every open issue that is similar to yours. These issues have been characterized and closed out. The correct venue for troubleshooting is either through the mailing list or IRC.
As indicated above, check that whatever is serving your registry content sets the Content-Length header. This will also be fixed in the next version of docker, so waiting may be sufficient.
—
Reply to this email directly or view it on GitHub https://github.com/docker/distribution/issues/1235#issuecomment-174025522.


The resource definition variable description is comfused

Describe the bug

Steps to reproduce

add resource definition matching rule 1 with: terraform-alicloud-rds-mysql
add resource definition matching rule 2 with: terraform-aws-rds-mysql
double-check the input description, could find the alicloud link, it is comfused while use aws

4. create an environment with aws connector
5. then create a resource with the definition created just now, could still find the alicoud link in description

Result
Expected behavior

Environment

Walrus version:

Additional context
Add any other context about the problem here.

Now, the generated definition schema is based on the expectation that common variables in each template are homogenous. If the description is provider specific, we are not able to generate a general description. However, users who manage resource definitions can customize it by modifying the UI schema.

Environment

Walrus version: v0.5.1

Test Result:
Related to https://github.com/seal-io/walrus/pull/1652.

When there are no completely identical and full sentences in the description:

When there are completely identical and full sentences in the description:


Document query on map property

I was able to create a property of DTDL type Map, and query it with SELECT * FROM digitaltwins T where T.propertyname.mapKey = 'mapValue'. This feature is undocumented - it would be very useful to document it.

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

ID: a9ee1efe-19d2-31f5-fa74-78809d965085
Version Independent ID: 699a0893-ee40-069c-270c-18e2623bbf39
Content: Query the twin graph - Azure Digital Twins
Content Source: articles/digital-twins/how-to-query-graph.md
Service: digital-twins
GitHub Login: @baanders
Microsoft Alias: baanders

@algattik Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Hi @algattik,
I've added a tip specific to Map-type properties in PR #147326.
Since this adds the requested information, I'll have Git automatically close this issue when the PR is merged. Feel free to comment back in this thread with additional comments or questions and we can always reopen if necessary.
Thank you!

Hi @algattik - I am trying to query a dictionary in ADT Explorer using your query but am failing to produce results.  Just want to verify this query still works.  I can provide more details of the issue if needed.

Hi @JGroot , this type of map query should still work.
Here's an example I just created to test it (screenshot is taken after running the query shown, so the testTwin is the result of the query).

Thank you for your quick response @baanders!  Your screenshot helped a lot. Turns out my issue was because my key name starts with a number:

Using letters first

The tool tip doesn't say it can't start with a number:

Would it be possible to update the documentation to say something like 'Keys must start with alpha characters to work in query?"

Thank you @JGroot for the detailed information!
The product team has shared a workaround for this situation: wrap the key name that starts with a number in [[ ]], as you do for reserved keywords in the query language.

I'm adding this information to the document in this pull request: https://github.com/MicrosoftDocs/azure-docs-pr/pull/229266
Thanks for your help to make the documentation on this topic more complete!

Confirmed this works!  Thank you so much for your help @baanders !


Swift build always fetches packages first

Describe the bug
In a project with multiple Package.swift files, e.g.: monorepos with multiple packages, the task Build Debug Run always does a full swift package resolve, which leads to very high build iteration times.
To Reproduce
Steps to reproduce the behavior:

Create a directory with multiple Vapor projects (only reproducible if the packages have multiple products, one of which at least is an executable)
Debug Build both projects
Change one line in one file and build again

You should see that a package resolve happens again, even though it should be cached.
Expected behavior
Not resolving packages, especially if they are fresh. I am sure there is a mechanism behind caching and at which point a new resolve should happen, but it's every single time right now.
Environment

OS: macOS, but with VSCode devcontainers in a Ubuntu 22.04 Docker Container with Swift
Swift version (output of swift --version): 5.8.1
Visual Studio Code version: 1.81.1
vscode-swift version: 1.5.0

I have seen this, but it doesn't seem to happen 100%
If you are using devcontainers could you try a devcontainer based off the latest development build of swift 5.9. There is a fix in 5.9 which might fix this issue for you. If you could verify it, that would be great.

@adam-fowler I can try but I won't be able to switch for everyday development before 5.9 is released as the whole setup depends on 5.8.
Is there no way to fix this temporarily, even if it's a hack?
I'll try 5.9 and let you know if it makes a difference.

If you run swift package update while VSCode isn't running I imagine that will fix the issue.
But it would be really helpful if you tried 5.9 beforehand to see if that resolved the issue.

@adam-fowler Swift 5.9 did not fix it. Not even with 1.6.0 of vscode-swift.

Ok so the fix in 5.9 didn't resolve your issue. Hmmm
I think I'm going to need a little more info. You say you have multiple Package.swift files. Can you provide your exact project structure. eg
Package1
  Package.swift
  ...
Package2
  Package.swift
  ...

One other thing to test. If you go to the settings and disable sourcekit-lsp do you still get the same issue?

Closing as I've had no response


Allow merging streams in one stream group.

This works as one part of the whole multi-stream feature, which is proposed in this PR, but can also be used independently.
In TensorFlow, there are at least three streams in one stream group: 1 compute stream, 1 h2d stream, and 1 d2h stream. This is designed to overlap the computation and memory copy on GPU. However, for some copy-frequent and launch-bound models, there are significant stream-synchronization overhead caused by the frequent switching between the three kinds of streams. So, let the operations use the same stream may bring acceleration. This PR provides an option to do so, just by setting the environment variable TF_GPU_STREAM_MERGE=true.

Hi @ezhulenev Can you please review this PR ? Thank you!

Adding @jyingl3 here because I'm not super familiar with this part of TF.

Discussed with @chuanhaozhuge. Chuanhao is working on changes related to GPU so will let Chuanhao review this PR.


Move cucumber feature tests to RSpec

Bring form inline with business volunteer form.
Trello: https://trello.com/c/XKGA3LTd/175-move-cucumber-feature-tests-to-rspec

Force-pushed to trigger CI again now it's fixed.

I admire your patience for every one of these feature tests for every step!

Thanks @issyl0 (with a y) - does feel a bit groundhog day.


Add window/application lifecycle delegation for desktop shells

Example use case: A document-based Flutter application should be able to prevent a window from being closed (e.g., with an alert) if the document corresponding to that window is unsaved.
At the very least plugins need to be able to register for application and window lifecycle events (as they can for application lifecycle on iOS), but we may want to consider making system channels for the most common cases.

Would this use the AppLifecycleState and State<LifecycleWatcher> or would it be some other mechanism (just asking to understand better)?

The specific case that this was originally filed for was delegation, not just observation, so at least some new mechanism would be needed. Supporting the existing lifecycle structure might be part of it though.

Implementation of AppLifecycleState would be great. My use-case: auto-close/lock of open files when the app is in the background/idle for some time. Would be the easiest way to detect when the user hasn't interacted with the app for some time. (ie. inactive vs resumed)

Implementation of AppLifecycleState would be great. My use-case: auto-close/lock of open files when the app is in the background/idle for some time. Would be the easiest way to detect when the user hasn't interacted with the app for some time. (ie. inactive vs resumed)

"Idle" isn't a clear, OS-defined application state, and would not be part of this. If you want to do something based on the user not interacting with the app for a while, that is something you would need to implement yourself based on what "idle" means to your use case.

I'm aware, but i think AppLifecycleState would be part of this? And my use case is when window is not in focus (i guess that would probably equal to AppLifecycleState.inactive), app is idle  :) would be perfectly fine for this

Foreground/background would likely be exposed, but on at least some systems it's possible for users to interact with background windows, so maps poorly to "idle".
If what you want is foreground/background notifications, then yes, this issue is relevant, but that maps poorly to the use case you described ("to detect when the user hasn't interacted with the app for some time").

@stuartmorgan sorry to spam this issue, what exactly do you mean with interacting with background windows? I guess it's possible to scroll in background windows, or have hover effects - do you mean this with interacting? I assume it's not possible anywhere to actively tap buttons or send keyboard events? 🤔
it's also possible that idle is not the right word 😅 I have also thought about listening on keyboard and/or mouse events but wasn't quite able to figure out how to add global listeners (I assumed somewhere between SystemChannels.mouseCursor / keyEvent and GestureBinding but kind of hit a dead end there since most seem to only allow a single callback. In the end I thought simply detecting the app getting inactive would fit my problem easier anyway and would be nicely mapped to how it could work on mobile as well).

I assume it's not possible anywhere to actively tap buttons or send keyboard events?

This assumption is not correct, at least on macOS.

But how can we respond to AppLifeCycle events in desktop? Will this be available soon or its not implemented for any specific reason?

But how can we respond to AppLifeCycle events in desktop?

Currently you cannot, thus this issue. If you need a short-term workaround you can wire up the behaviors you need via platform channels in your own application.

Will this be available soon

There is no specific timeline for it. Anyone interested in accelerating the process is welcome to submit PRs.

or its not implemented for any specific reason?

It is not implemented because the Flutter team has finite engineering resources.

cc @cbracken this seems like table stakes for a desktop stable release. thoughts?

This also prevents desktop apps to react to loss and gain of window focus.
See e.g. https://github.com/flutter/flutter/issues/103446 and https://github.com/flutter/flutter/issues/105230

This has been completed. See AppLifecycleListener and the related classes.


Fail to download from T411

Hi i tried to use the T411 part to find torrents, it's working well.
But when i try to download the torrent it's failling
I call
torrentSearch.downloadTorrent(cachedTorrent) .then(buffer => { 				_logger.debug (buffer ); 			}) 			.catch(err => { 				console.log(err); 			});
With the torrent object  as follow
title=47.meters.down.2017.french.720p.bluray.x264-lost.mkv, time=23 heures, seeds=232, peers=91, size=3.27 Go, desc=https://t411.si/torrents/55551/47-meters-down-2017-french-720p-bluray-x264-lost-mkv, provider=T411
And i got the error Error: options.uri is a required argument at /torrent-search-api/lib/torrent-provider.js:181:42

There were some changes on T411, I fixed a selector.
Upgrade to 1.0.17 and it should be good.


Permission cancel/ renew

How can I switching permission / access to calendar for example by switching cupertino switch? I see that we can set the permission only once, after that there is no possibility to set it back to initial state.

I presume you're on iOS right?
The app itself can't do anything once the user has denied permission. All you can do is point your user to iOS settings and ask them to change it there.
However you can detect if the permission is denied, and display a suitable dialog to your user.

ok perfect thank you for fast response.


verdadero-falso-test: Agrego tests y excepciones para VerdaderoFalsoClasico

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@dd08ef1). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop       #5   +/-   ##
==========================================
  Coverage           ?   76.38%
  Complexity         ?       30
==========================================
  Files              ?       12
  Lines              ?       72
  Branches           ?        3
==========================================
  Hits               ?       55
  Misses             ?       16
  Partials           ?        1

Continue to review full report at Codecov.

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


[FLINK-30411] Validate empty JmSpec and TmSpec

What is the purpose of the change
This PR validates FlinkDeployment without jobManager or taskManager spec. Currently, FlinkDeployment gets stuck in UPGRADING state if you don't specify jobManager or taskManager spec.
By adding validation, helm install directly fails.
Example: basic.yaml
apiVersion: flink.apache.org/v1beta1
kind: FlinkDeployment
metadata:
  name: basic-example
spec:
  image: flink:1.15
  flinkVersion: v1_15
  flinkConfiguration:
    taskmanager.numberOfTaskSlots: "2"
  serviceAccount: flink
  job:
    jarURI: local:///opt/flink/examples/streaming/StateMachineExample.jar
    parallelism: 2
    upgradeMode: stateless

Brief change log

Validate FlinkDeployment without jobManager or taskManager spec.

Verifying this change
This change added tests and can be verified as follows:

Extended existing unit test for the change as part of the PR
Manually verified by removing jobManager and taskManager from examples/basic.yaml

Before change - ensured FlinkDeployment gets stuck in UPGRADING state.
After change - helm install example/basic.yaml fails with error message. Reverting back the file deploys the job successfully.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changes to the CustomResourceDescriptors: no
Core observer or reconciler logic that is regularly executed: no

Documentation

Does this pull request introduce a new feature? no

@gyfora how do you think we should fix this?

@gyfora how do you think we should fix this?

@morhidi @gyfora I added further validations with configs set through flinkConfiguration. It does make the validation logic a little complicated. Do you suggest any alternative approach?
Besides helm validations, the deployment gets stuck in UPGRADING state due to ClusterDeploymentException. Should it fail the deployment instead upon encountering  ClusterDeploymentException a fixed number of times? Even after the validations in this PR, the deployment can still go into this state by setting insufficient memory.

I am still a bit torn on this PR. This adds quite a lot of complexity to the validation with some risks involved. Maybe we should just leave it as it is?

Agreed on the added complexity, given the scope of the issue. Only additional benefit we get out of processSpecFromConfig from TM/JM utils is validating different combinations of flinkConfiguration, example: https://github.com/apache/flink-kubernetes-operator/pull/487#discussion_r1059562798.
I am totally fine closing the PR unless you have any alternative approach in mind.


CNDB-9681: Use rerankk as limit and disable cassandra.sai.reduce_topk_across_sstables by default

This is a temporary hack to mitigate a regression introduced with
https://github.com/datastax/cassandra/pull/1107
reduce_topk_across_sstables sounds like a good improvement but it is actually introducing a performance regression in the workload used in https://github.com/riptano/cndb/issues/9681
The effect of disabling reduce_topk_across_sstables in the first case further improves hybrid performance. In the previous prod image, we would always ask for rerank results from JVector (so, 100 gets turned into something like 299). Now, we search for 299 but only return the 100 best across the boundary. This is designed to improve performance in the case where all results are permitted, with the idea that the penalty of asking for more is quite small. It seems we underestimated this penalty. This means we need dramatically more requeries in the hybrid case, compounded by reduce_topk_across_sstables, which reduces the limit proportionally to the size of the sstable/total sstables.
The patch is originally contributed by @jkni

Closed


Update Beacon create modal and instance fetching semantics

What
These changes fix instance fetching under a beacon. Previously, we were sending the Name field of the beacon docker instance instead of the Alias. The alias field is now required for beacon creation. See the Add Beacon modal under /beacons. Since all fields are required for a beacon create, we now provide validation errors before sending the request over. These only check for the existence of the fields, not their format (i.e. no regex to check for a valid IP format)
How

Modified all links from {{ instance.Name }} to {{ instance.Alias }} coming back from the lighthouse response.
Validation errors are handled partially by angular - the form itself is assigned a $scope attribute used to store validation state. These values are checked and used determine if an error style needs to be applied to a form group.
As a bonus, removed the now unused instances.html template, since this functionality is now under control of the beacons page.

Dependency
Must be merged after https://github.com/lighthouse/lighthouse/pull/45 is merged into lighthouse/master.
Example validation error

@lighthouse/owners I'd like to look into handling form validation in the "angular way" tomorrow to catch an empty alias and the like, but this is ready for a first glance.

@theMagicalKarp @zach-taylor This is ready for a full review and test. Note the beacon create modal no longer fades in or out and does not change the background color when shown. I had trouble finding a way to reconcile the angular validation states with the auto-dismiss feature of the modal. The "right" way would be to create a directive that can monitor scope attributes and modify the DOM accordingly, but I figured a simple scope boolean ($scope.submitting) would suffice for now.

+1

+1


Default operator behaviour '=' instead of specified in field.operators

Hi,
If you will specify a custom operator, the default operator value will be '=' instead of '===' and it will still be the same even if you pick manually after initialization.
    {
        name: 'status',
        label: 'Status',
        operators: [ {name: '===', label: 'is'} ],
        valueEditorType: 'radio',
        values: [
            { name: 'active', label: 'Active' },
            { name: 'paused', label: 'Paused' }
        ]
    }

UPDATE: SOLVED
    getOperators works as expected

    getOperators={(field) => {
      return fieldOperatorMap[field];
    }}

We still need to fix the issue with the operators though, so I'm reopening this issue.

This is fixed with commit 5ad9da5d; released in version 3.8.1.


List of images being saved incorrectly

I upgraded from netlify-cms 2 to decap-cms 3. I have a line in my config to create lists of images:
      - label: "Headshot"
        name: "images"
        widget: list
        summary: "{{fields.image}}"
        field: { label: Image, name: image, widget: image }

In decap 3 but not netlify-cms 2, this saves incorrectly. I want it to produce "image": [ "/file.jpeg" ] in the content file (which is JSON in case that matters) but instead it produces "image": [ [ "/file.jpeg" ] ].

Hi @carlmjohnson, sorry it took a while, been busy elsewhere. This should be fixed in latest version (3.0.8), do you mind trying and confirming?
Thanks

Yes, it appears to work now.


#292 Correct broken link in install instructions page that returns 404

Description Of Changes
Link in the instruction text pointed to: https://docs.chocolatey.org/en-us/choco/installation which caused 404
Correction of url was done: https://docs.chocolatey.org/en-us/choco/setup
To verify change you find it in the Option 2 - Updated PowerShell and .NET section of Setup/Install documnetation
try {
  # Set TLS 1.2 (3072) as that is the minimum required by Chocolatey.org
  # Use integers because the enumeration value for TLS 1.2 won't exist
  # in .NET 4.0, even though they are addressable if .NET 4.5+ is
  # installed (.NET 4.5 is an in-place upgrade).
  [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072
} catch {
  Write-Warning 'Unable to set PowerShell to use TLS 1.2. This is required for contacting Chocolatey as of 03 FEB 2020. https://blog.chocolatey.org/2020/01/remove-support-for-old-tls-versions/. If you see underlying connection closed or trust errors, you may need to do one or more of the following: (1) upgrade to .NET Framework 4.5+ and PowerShell v3+, (2) Call [System.Net.ServicePointManager]::SecurityProtocol = 3072; in PowerShell prior to attempting installation, (3) specify internal Chocolatey package location (set $env:chocolateyDownloadUrl prior to install or host the package internally), (4) use the Download + PowerShell method of install. See https://docs.chocolatey.org/en-us/choco/installation for all install options.'
}

iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))

Motivation and Context
Resolved pointed issue in https://github.com/chocolatey/docs/issues/292. Installation instructions currently send user to page that doesn't help them out.

Testing

[x] I have previewed these changes using the Docker Container or another method before submitting this pull request.

Change Types Made

[x] Minor documentation fix (typos etc.).
[ ] Major documentation change (refactoring, reformatting or adding documentation to existing page).
[ ] New documentation page added.
[ ] The change I have made should have a video added, and I have raised an issue for this.

Issue #

Change Checklist

[ ] Requires a change to menu structure (top or left hand side)/
[ ] Menu structure has been updated

Related Issue
Fixes https://github.com/chocolatey/docs/issues/292

Thank you for this PR @LeaDevelop. Overall it looks good. There are a few things we'd like to adjust with it that you wouldn't have known about. If you are in a position to get these changes done, we'd appreciate it, but if you're not they are little things that we also can get fixed up for you:
* It's no where near your changes here, so GitHub won't let me put the suggestion in. Instead I'll add it here: To ensure that any existing scripts with this URL embedded in them will work, we'd like to add another `RedirectedFrom` to this file. Could you update the preamble and add a new line after line 8 to include: `- en-us/choco/setup`?

* As well, would you mind rewording your commit message to line up with https://github.com/chocolatey/choco/blob/develop/CONTRIBUTING.md#prepare-commits? In particular, the message itself is ever so slightly too long, and the issue number should be wrapped in parens.

Sure can do, will take care of it in next 2 days 👍🏻

Done both requested corrections and pull request title edit - made sure id is in between ()

Thanks for getting this fixed up @LeaDevelop. My apologies for taking so long to review it. I also noticed today when merging it that I had inadvertently requested the wrong RedirectFrom. So I got that fixed up.
I also rebased against master which eliminates the merge commits as they're not needed here.


off-topic - would you like help create a package for symbolic representation of sets?

Given your profile and obvious interest for the intersection of math, python, and symbolic computation: would you be interested in creating a package for symbolic representation of sets?
I've been looking for sth like this for:

domain and domain validation of parameters in scikit-learn-like packages
for symbolic representation of the domains of probability distributions, in skpro: https://github.com/sktime/skpro

Hey 👋
it seems really interesting.
Do you have already some code on what you would like, or do you have a road-map/project plan on how the package should look like and what are the feature/IPA you are expecting?
PS (Off-topic): thanks for your other contributions (the PR and the suggestions). I will look deeply into them as soon as possible :-)

Do you have already some code on what you would like, or do you have a road-map/project plan on how the package should look like and what are the feature/IPA you are expecting?

Not in too much detail, but in essence I would like a symbolic representation language with eager computations for containedness, cardinality, and possibly other things like volumne/mass and expectation-like integrals.
I'd imagine the python counterpart of:

set6, another package I've designed for this purpose in R: https://joss.theoj.org/papers/10.21105/joss.02598
the Wolfram sets and symbolic logic module: https://www.wolframalpha.com/examples/mathematics/logic-and-set-theory
sth I'm not sure about: the hypothesis package has a set language to define domains for tests, but it is not explicitly symbolic: https://hypothesis.readthedocs.io/en/latest/settings.html

Architecturally:

sets would be parametric objects, inheriting from scikit-base BaseObject,
skpro distributions get an attribute "domain"

From a roadmap perspective, therefore, it would be crucial to cover first:

the reals, integers, and natural numbers
finite part of Borel algebra over reals
finite sets of integers and arbitrary objects
composition: Cartesian product sets, power sets

Another related location is sklearn.utils._param_validation, which has a primitive language to define sets for parameter constraints.

It seems really interesting.
But why a package and not just a module in skpro?  From what I see the main purpose of this project will be to serve the skpro distributions right?
If then we are happy, we could make it a proper package.

But why a package and not just a module in skpro? From what I see the main purpose of this project will be to serve the skpro distributions right?

Agreed, that might be a sensible starting point, and then one could spin it out, if other people are using it.

Ok
Can we create a branch and we start working on it? Once we are happy with that we can merge, ok?
Do you have in mind a name for the module/package?

I was reading the documentation about how SymPy implements sets (here). The API seems very interesting. Did you have taken in consideration their implementation for skpro or it doesn't have the functionalities you want to have?

very interesting point - I have not thought about this carefully, but perhaps the sympy sets module is sufficient for the use cases I have in mind.
There is even a statistics module with lots of distributions and support for composites: https://docs.sympy.org/latest/modules/stats.html
but that is not sufficient for the use case of tabular distribution representation and eager methods.
Perhaps some kind of a hybrid approach would work?
On the other hand, sympy is quite heavy as a dependency, for a use case where we do not need symbolic reasoning, simplification, evaluation, etc, but only representation mainly.
I think it's worth writing up the scope more precisely before we decide either way. I'll open an issue in skpro to discuss - given that you affirmed that you are interested, we can continue to scope options there?

opened here: https://github.com/sktime/skpro/issues/244

Closing as the discussion is moved to skpro repository


Emulator wrapper fixes

fix: emulator should always get non-empty command line arguments (regression from https://github.com/wix/detox/pull/690)
fix: detox fails to start when another emulator is running
feat: logging emulator output on errors

Regarding (2), there was an issue (likely on Linux, but not sure if it is the reason) with a race condition.
tail.on("line", function(data) { was called too late, when the promise had already rejected.
Since the function was returning return promise; without a catch (e.g. return promise.catch(function () {), the promise._cpResolve() call was happening too late inside tail.on, when the consumer of boot logic actually had gotten into a negative conditional branch.

@rotemmiz , done.

@rotemmiz , the build is green.


Any update for this project?

As i can see in simplcommerce, the modular  architecture has a little bit cha.ged since this repo was open. Can you pleasd update it. Or create a new one based on simplcommerce modular concept.
Thanks in advance

https://github.com/molaie/TryModulra2.0


testing(run): add test retries to Cloud Run Image Processing, Logging Manual, and Sigterm

Description
This adds retries to various Cloud Run service e2e tests. However, none of these are fixes for currently open flakes. This is suggested as a general good practice to preempt future flakes.
Like this PR? It is extending an existing pattern in the Cloud Run E2E tests, and has been created in parallel with #3296 and #3298 to keep scope contained.
Checklist

[x] I have followed Contributing Guidelines from CONTRIBUTING.MD
[x] Tests pass:   go test -v ./.. (see Testing)
[x] Code formatted:   gofmt (see Formatting)
[x] Vetting pass:   go vet (see Formatting)
[ ] These samples need a new API enabled in testing projects to pass (let us know which ones)
[ ] These samples need a new/updated env vars in testing projects set to pass (let us know which ones)
[ ] This sample adds a new sample directory, and I updated the CODEOWNERS file with the codeowners for this sample
[ ] This sample adds a new Product API, and I updated the Blunderbuss issue/PR auto-assigner with the codeowners for this sample
[x] Please merge this PR for me once it is approved

Replacing this with an implementation using #3251


Incorrect time zone format in xsd:dateTime for Redshift's TIMESTAMP data type

Ontop 5.1.2 produces syntactically invalid xsd:dateTime literals from Redshift's TIMESTAMP data type.
Ontop maps the timestamp 1984-03-28 00:00:00.0 to "1984-03-28T00:00:00+00"^^xsd:dateTime. The time zone fragment of this literal is invalid. The syntactically correct literal is "1984-03-28T00:00:00+00:00"^^xsd:dateTime.

Thanks @jindrichmynarz for reporting the issue. We faced a similar issue with DuckDB recently, where we had to use a regexp_replace to add the minutes of the time zone when they were implicitly 00.
See the changes on the  class DuckDBDBFunctionSymbolFactory in the commit 6216b5

Fixed by https://github.com/ontop/ontop/tree/bugfix/order-by-values


[$1000] Textinput is not focused in chat after visiting conceirge help

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to Settings
Click workspace
Choose a workspace
Click ? and then Get Assistance
Click chat with concierge
See that the textinput isn't focused (you have to manually click into it to begin typing)

Expected Result:
Text input should be focused
Actual Result:
Text input is not focused
(Also navigate other chats and their text input is not focused)
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: 1.3.31-2
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Text input is not focused after visiting coneirge help.webm
https://github.com/Expensify/App/assets/43996225/aa6f2326-5a98-4155-8187-8bc869d791a9
Expensify/Expensify Issue URL:
Issue reported by: @Habtamu-Asefa
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1686984617296819
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01f42405b3f19296c4
Upwork Job ID:<PHONE_NUMBER>531503104
Last Price Increase: 2023-06-29

Proposal
Please re-state the problem that we are trying to solve in this issue.
Textinput is not focused in chat after visiting conceirge help.
What is the root cause of that problem?
Compose is focused when below condition is true.
https://github.com/Expensify/App/blob/6183609c577f2310928bb4e8ee23b52f6dd28e00/src/pages/home/report/ReportActionCompose.js#L194
But after visiting conceirge help, props.modal.isVisible, i.e. modal.isVisible onyx data is not set to false, so compose is not focused.
What changes do you think we should make in order to solve the problem?

We should set modal.isVisible onyx data set to true by calling onCloseButtonPress function after visiting conceirge help.
                        {this.props.shouldShowGetAssistanceButton && (
                            <Tooltip text={this.props.translate('getAssistancePage.questionMarkButtonTooltip')}>
                                <PressableWithoutFeedback
                                    onPress={() => {
                                        this.props.onCloseButtonPress();
                                        Navigation.navigate(ROUTES.getGetAssistanceRoute(this.props.guidesCallTaskID))
                                    }}
                                    style={[styles.touchableButtonImage]}
                                    accessibilityRole="button"
                                    accessibilityLabel={this.props.translate('getAssistancePage.questionMarkButtonTooltip')}
                                >
                                    <Icon src={Expensicons.QuestionMark} />
                                </PressableWithoutFeedback>
                            </Tooltip>
                        )}

What alternative solutions did you explore? (Optional)
None.

Hi, thank you for your post.
I have worked on your problem and I hope I understood it correctly.
Please take a look at the attached file and let me know if you have any questions or feedback.
https://github.com/Expensify/App/assets/119021741/fbef49ee-d528-46dc-809d-dd669d287d51
Best regards.

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~01d5e86a0f892dfc8f

Adding "Hold" in title
Linked to https://github.com/Expensify/App/issues/15992
Switched to Weekly since it's blocked

@fedirjh do you think we can entertain proposals on this issue, or should I remove the Help Wanted label until the tracking GH is taken on?
I think we should decide based on whether or not we think it's possible to fix this independently from the tracking GH. Would be good to avoid a scenario in which we deploy a fix today and have to re-do that fix (or update that fix) in the future.

Chatted via DM with Fedi and we think this should be held. I removed the Help Wanted label.

still held

Note: I'm going OOO for ~2 weeks and making this Monthly because I don't foresee movement in the short term. If something changes, please remove my assignment & re-apply the Bug label to get a fresh BZ assigned to guide it forward.

Here is my proposal.

I'm re-assigning this as part of my preparation for Sabbatical (starting tomorrow). In terms of next steps:

This is held on https://github.com/Expensify/App/issues/15992
Leaving as Weekly since it's blocked

Stil held on https://github.com/Expensify/App/issues/15992. Since that isn't assigned to anyone to work on, I'm going to move this to monthly.

Still on hold for https://github.com/Expensify/App/issues/15992

Tracking issue closed, let's get this one retested.

Issue is reproducible during KI retests.

Nice, let's close this out then

I reported this bug, will there be a bonus?

@bfitzexpensify hi, the issue is still happening. QA also says they can reproduce it.
I just updated my proposal based on the latest code and propose to fix this on some pages too where this issue is happening.

Reopening since I misread https://github.com/Expensify/App/issues/21401#issuecomment-1966990285 😅

OK, given it's happening on multiple pages as pointed out by @bernhardoj, I think this is something we should address

@fedirjh looks like we have a couple of old proposals, and an updated one from @bernhardoj - do any of those work?

Yes, the testing step is a bit outdated. You can find the Get Assistance in workspace invite page.

Thanks @bernhardoj - updated the testing steps in the OP

specifically using the browser's back button will not work as expected anymore.

Do you mean going back won't go back to the get assistance page? If yes, then that's the expected behavior. We want to close the RHP. You can test it with other RHP flows such as request money (for reference).

If you log the auto-focus value here,
https://github.com/Expensify/App/blob/faff990f6ce64fbef53712169b23788e3fd59ad0/src/pages/home/report/ReportActionCompose/ComposerWithSuggestions/ComposerWithSuggestions.tsx#L278-L279
the value will be false because the modal.isVisible value is stuck at true.
I found out that after we use live markdown (RNMarkdownTextInput) on the web, setting the autofocus prop to false doesn't work. It always auto-focus the input and looks like that happens because we are setting the selection here.
https://github.com/Expensify/react-native-live-markdown/blob/7c9d9b050874b8b2a0ef8d000304b428dc8ec0e8/src/MarkdownTextInput.web.tsx#L527-L533
Commenting the effect solves the auto-focus issue.
cc: @Skalakid @BartoszGrajdek I guess

OK, so are we good to close this out as no longer an issue?

We are currently blocked by a live markdown bug on the web, I have posted it on the tracking issue.

Held on https://github.com/Expensify/App/issues/36071

Still held

@fedirjh I don't have an answer to that. I thought they are going to handle it because @tomekzaw +1 my report (😂), but I don't see it's being added to the list. @tomekzaw can you share any plan for that issue specifically, if any? Or should I create an issue on the react-native-live-markdown repo?

@bernhardoj thanks for reporting the issue, I investigate it and come back to you with more details

Thanks @Skalakid

@bernhardoj The PR with the fix for the issue you reported has been just merged

@Skalakid thanks a lot!
I can confirm the text input issue is resolved.
I think we can update react-native-live-markdown and fix this issue in one PR.
@fedirjh

@Skalakid yes, that would be great

Hmm after bumping the react-native-live-markdown version the issue is reproducible again. To fix it we should apply @bernhardoj's proposal changes. Maybe let's bump the version of the package to 0.1.63 and add proposed changes in one PR? What do you think about it?

@Skalakid that works. I can do it after @fedirjh approves and I get assigned to this issue 👍

PR is ready
cc: @fedirjh

Reporting bonus payment is pending. @bfitzexpensify the issue was created while bug reporting was being compensated $250

Payment complete to @bernhardoj
Offer sent @Habtamu-Asefa
Please complete the BZ checklist @fedirjh and I'll finalise your payment.

@bfitzexpensify Thank you, I just accepted the offer.

Thanks @fedirjh. All payments complete, closing this out.


bind-mounts /dev in osd containers

This is needed in order to make ceph-disk work. Fixes #730

@ivotron thanks!


Fix linter

We are experiencing issues with the go linter, let's have a look if we can improve the situation with an upgrade.

Sorry, wrong repository... :see_no_evil:


Preserve client ips

I would like to run a home cluster and provide services like pihole and home assistant. Both products work a lot better if they get the real client ip addresses.
I used to use kube router and metal lb for this purpose. Is it possible to achieve the same result with your embedded load balancer and flannel network?

The embedded load balancer is just using iptables and will masquerade the IPs.  You are better off running kube-router or metal lb for that purpose.  Just add --no-deploy=servicelb to disable the builtin service LB.
If you get metallb or kube-router working with k3s I love to see how you did it. Eventually it would be great to cultivate a series of recipes/howtos to bolt on different components to k3s easily.

For kube-router you also do not need kube-proxy anymore. Therefore you might want to integrate kube-router instead of flannel in order to save RAM.

@ibuildthecloud have you looked into kube-router already?

I do like kube-router but i think defaulting to it would be too much of a change from what people are expecting, if they are just expecting vanilla k8s.  The kube-proxy really doesn't add much memory so it's not a huge concern.  The biggest issue is the performance hit.

I believe kube-router should work on k3s as is.  Please create a new issue if kube-router doesn't work and we will address that.  In terms of preserving client IPs, k3s doesn't change the behavior of k8s so this is really a more generic k8s question.

I do not think that you can run kube-router with k3s. Because you have to remove the kube-router daemon set and iptables rules. We would need an additional option like without kube-proxy otherwise there would be a conflict.


multi: split commits from loop repo

Pure code extraction from loop repo using git subtree split
Loop counterpart: https://github.com/lightninglabs/loop/pull/237

I don't know if the tagging is too much, because every merge will probably need a new tag?

@carlaKC: The version is weird because the commit you're referencing to isn't in the main repo yet. You have to add a rewrite in faraday's go.mod to use Joost's fork.

I don't know if the tagging is too much, because every merge will probably need a new tag?

We don't need to tag each merge, because go-mod can do pseudo versions. I think it might be helpful to tag the point where we split out from loop (maybe not) so that other projects using lndclient can just point to that version?

But after the first change to this repo, the need to switch to pseudo version anyway? Btw, after merge it looks like github.com/lightninglabs/lndclient v0.0.0-20200618064231-15628713b198
I am fine with tagging (which version to start with?), but don't think it is that useful.

Pushed tag v1.0.0.


Adjust centaur to sub workflow changes and add sub workflow tests

👍 Looks awesome, and I like the idea of using the <> identifier in the WDLs for testing sub-workflows.

:+1:

I'm going to wait for the Cromwell PR to be merged to merge this one or everyone's PRs will be red


Fix Search Paths / Argument List Too Long

Very similar to https://github.com/xxsnakerxx/react-native-flurry-analytics/pull/22
Without this, my app does not compile as the ** globbing on the entire project directory causes the Argument List Too Long error:
Argument list too long: recursive header expansion failed at /Users/nthompson/Documents/react-native/PROJECT_NAME/node_modules/react-native-google-signin/ios/../../../ios/build/Index/DataStore/v5/records/F4.

I'm facing the same issue

After add new lib as Firebase,  react-native-youtube or react-native-google-signin
I seen this problem again and I solved by:
Link React Native to Pod
pod "yoga", :path => "../node_modules/react-native/ReactCommon/yoga"   pod 'React', :path => '../node_modules/react-native', :subspecs => [     'BatchedBridge', # Required For React Native 0.45.0+     'Core',     'tvOS',     'DevSupport'   ]
Change HEADER_SEARCH_PATHS in projects have problem from
../node_modules/react-native
to
${SRCROOT}/../../../ios/Pods/React
delete folder: /DerivedData and rebuild poroject and never see it.

@huongnguyenvan

Does this solve only the first build or subsequent builds too? First clean builds always worked.

Change HEADER_SEARCH_PATHS in projects
Are you changing these in the projects files in the pods? If so, a clean install (for example on a continuous integration server) wont have those changes. Also if you delete your pods to reinstall them, you've added a manual step in getting your project working.

It would be nice for there to be a Podfile fix for this, but I think that @devfd needs to apply this PR's changes as it seems all other Pods do it this way...

I had the same issue. It got fixed after applying this patch.
Thank you @njt1982 .

@lucascarvalho you're welcome :)

@devfd are there still problems with maintenance of this repo? I understand that @Kerumen was going to pick up some slack, but there seems to be yet another serious lull in activity.
I'd be glad to sort through this and the 20+ pending to help make this repo suitable for use again.

Hello! This project recently got new maintainers and moved under React Native Community. We're trying to triage most of the issues and get this library we all use in to good shape.
We're discussing this since this is breaking change. thanks for you patience. I ended up with exactly the same solution at #393.


Explorer Database

I know this was gonna be Jordan's job, but I got tired of restarting the explorer and banged it out in two days. Sorry.
Previously, siad -M cge consumed about 2GB of memory, causing it to crash on many systems. Notably, it was crashing http://explore.sia.tech, filling up both its 2GB physical RAM and 2GB swap.
As of this PR, the explorer database now resides on disk, in a bolt database. siad -M cge consumes less than 10MB of RAM (!!). I found out that htop may be misleading for judging memory usage; it seems to include the mmap overhead of bolt. (The explorer database is about 2GB.) pmap -x $(pidof siad) gives more accurate results.
I tried to preserve the old logic as much as possible, but it's quite likely that a discrepancy or two has snuck in. I know for sure that the difficulty calculation has changed, and likely the estimated hashrate as well. I would appreciate some assistance in calculating those values correctly. The way we handle FileContractDiffs is pretty gross too. My gut says there's a much better way to do it.
The only major changes were to block facts. The old explorer kept a set of "current" facts, but the new model just maps each block to its facts. This broke one test (see TODO). Also, blockFacts now embeds a modules.BlockFacts. They only difference between the two is that blockFacts has an extra Timestamp field, and modules.BlockFacts has a redundant Difficulty field (can be calculated from the target).
Finally, I need to add code to handle subscription errors. Restarting from 0 seems sensible, but the existing database needs to be wiped first.
Oh yeah -- no new tests added. :I
I've run it locally and confirmed that it functions as expected, but obviously some rigorous testing would be better.
ALSO: I think I may have identified what was "pushing the explorer over the edge" and causing it to crash. If you ask it about the zero hash, it will report every transaction containing the zero hash, which is... a lot. Even with the DB, memory and CPU usage spike for multiple minutes.
We could triage this by intercepting the zero hash in the API, but I'm not sure what the best behavior is long-term.

Instead of banning the zero hash we could ban any lookup that would result in a very large number of results. Naively we could do:
if bucket.Stats().KeyN > maxNumResults {
    return errBucketTooLarge
}
err = bucket.ForEach(func(k, v []byte)  error {
//...
})

for every occurrence of bucket.ForEach. Note sure if this is the best way, but it has the benefit of preventing someone from bringing down our explorer by creating many transactions with any particular unlock hash, not just the zero hash. maxNumResults is also then configurable.

I was thinking we should just throw the explorer onto a more powerful machine, give it 4GB of RAM and a more powerful CPU. I'm guessing you know this, but I'm not really ready for this PR, as we've got a bunch of other stuff to do, and this is definitely increasing our bug surface area before we've fixed all of the other bugs.
As a team, we need to stop implementing things until we've got better repo-wide testing.

If I can fix the hashrate estimation, I'd at least like to run this on the staging site. It consumes so little memory that it shouldn't affect the stability of the current explorer.

hashrate calculation should be more accurate now. It's still not identical to the current explorer though:

Height
Old
New
Error

10000
560350946316
573642705124
+2.372%

20000
666536537025
676929199543
+1.559%

30000
339321673650
347801577794
+2.499%

40000
436082194618
445230600687
+2.098%

Could be as simple as an off-by-one error in the estimation window.

I believe the discrepancy is caused by the conditionals wrapping the old explorer hash rate logic:
if e.blockchainHeight > hashrateEstimationBlocks {
    //...
}

The hash rates for the first hashrateEstimationBlocks are never added to the hash rate.

The difficulty calculation now matches the old explorer exactly, yes?

Can we change the estimated hashrate window from 60 blocks to 200 blocks?

ok. Good enough.


task#2

Note that the argo crd has been included as a yaml file and should maybe
moved to avoid accidental installation into k8s clusters.

@JaneRM97 you will have to look at the commit on this branch for a proper description of what is going on. I am not sure how to get Github to use the commit as a PR description yet.
I am curious to hear if the changes and commit message makes sense. Most of the changes are auto generated, all of the manual changes are in the controllers directory.


[Bugfix] Destroy PP groups properly

Small bug fix to properly delete PP groups when destroy_model_parallel is called.

cc: @youkaichao

Hey @youkaichao test failure looks unrelated - can you comment?

I'm working on https://github.com/vllm-project/vllm/pull/5293 , after that, we don't need separate code for pp and tp anymore. No more copy-pasting. Code will be shared for pp and tp.

Ok, in that case I'll let you decide whether you want to merge this or not. IMO it's relatively safe to merge this in the mean time as it's just a small bugfix, but might not matter either way.


Hide the "Win rates" section if there is no win rates

Actual: I the user don't have any win rates, I can see "Win rates" section on the Profile page

Expected: I the user don't have any win rates yet, hide the "Win rates" section on the Profile page

Can you assign this to me I will try to work on this issue.
Thank You!!!!


Encoding of properties files is ISO-8859-1

Java properties files are assumed to be ISO-8859-1 (latin-1) encoded.

Thanks!


Upgrade to Django 1.11 or 2.0?

Any chance this package will be updated to work with Django 1.11 or 2.0?
I get a
Reverse for 'messages_inbox' not found. 'messages_inbox' is not a valid view function or pattern name.
after the update to Django 1.11.

Yes, there's a chance ... There even is a Pull Request open, where I commented what needs to be changed, but the opener never updated it:
https://github.com/arneb/django-messages/pull/102
If you want to fix the PR, I will merge it.
My time is currently very limited, so I cannot do everything alone, sorry!

I've done the minimum updates to run with Django 2.0+ in PR #105. They are the same changes as imdiegoestevez made in PR #102, minus the things they have not corrected.

should be fixed in 0.6.0


[FEATURE]: Please make document for error controll is required.

Describe what you want
Please make document for error controller is required.
I want controll Drizzle Error

heeeeeeeeeeelp


[5.4] Fix scheduler callbacks

I noticed the scheduler callbacks dont currently call the before callbacks?
I think that is an oversight, as I cant see any reason to not try and call them. I did some local testing - and it works perfectly fine with before callbacks included...

This was already added on master.

@taylorotwell - huh, didnt notice that.
Any reason not to apply it to 5.4 though? Seems like a bug fix?


native-federation-typescript host plugin needs polyfilling for Array.prototype.at()

Adding NativeFederationTypeScriptHost plugin to my simple react + webpack (webpack-cli served) setup results in the following error:
[webpack-cli] TypeError: e.split(...).at is not a function
    at U (/home/app/node_modules/@module-federation/native-federation-typescript/dist/chunk-XV6C425D.js:1:737)
    at /home/app/node_modules/@module-federation/native-federation-typescript/dist/chunk-XV6C425D.js:1:935
    at Array.reduce (<anonymous>)
    at z (/home/app/node_modules/@module-federation/native-federation-typescript/dist/chunk-XV6C425D.js:1:911)
    at T (/home/app/node_modules/@module-federation/native-federation-typescript/dist/chunk-XV6C425D.js:1:1058)
    at /home/app/node_modules/@module-federation/native-federation-typescript/dist/chunk-XV6C425D.js:2:1652
    at Object.apply (/home/app/node_modules/unplugin/dist/index.js:1397:36)
    at createCompiler (/home/app/node_modules/webpack/lib/webpack.js:73:12)
    at create (/home/app/node_modules/webpack/lib/webpack.js:134:16)
    at webpack (/home/app/node_modules/webpack/lib/webpack.js:158:32

Looking at the compiled chunk-XV6C425D.js, the originating line is this one:
https://github.com/module-federation/universe/blob/cdfe13aed086d48eaf86dbae08df82870b9a514f/packages/native-federation-typescript/src/configurations/hostPlugin.ts#L9
Which, I think is not supported in ES2022. For compatibility, can this be polyfilled to ES5 or replaced with traditional arr.length - 1 indexing?
Attached below is my tsconfig:
{
  "compilerOptions": {
    "sourceMap": true,
    "target": "es2015",
    "downlevelIteration": true,
    "jsx": "react",
    "module": "esnext",
    "moduleResolution": "node",
    "experimentalDecorators": true,
    "declaration": false,
    "removeComments": true,
    "noImplicitReturns": true,
    "noUnusedLocals": false,
    "strict": true,
    "allowJs": true,
    "skipLibCheck": false,
    "esModuleInterop": true,
    "allowSyntheticDefaultImports": true,
    "forceConsistentCasingInFileNames": true,
    "resolveJsonModule": true,
    "isolatedModules": false,
    "noEmit": false,
    "preserveConstEnums": true,
    "lib": [
      "dom",
      "dom.iterable",
      "esnext"
    ]
  },
  "include": [
    "src"
  ],
  "exclude": [
    "dist",
    "node_modules"
  ]
}

Sorry for necro-bumping, but can we get a versioned release with this change soon?

@ScriptedAlchemy I'm not able to release, can you do it please?
Even native-federation-tests should be released

sure thing will do, what error are you getting on native federation release?


tabnine: 3.1.1 -> 3.2.63

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[x] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 108621 1

2 packages built:

tabnine
vimPlugins.completion-tabnine

Result of nixpkgs-review pr 108621 1

2 packages built:

tabnine
vimPlugins.completion-tabnine

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108621 run on x86_64-linux 1

2 packages built:

tabnine
vimPlugins.completion-tabnine

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108621 run on x86_64-linux 1

2 packages built:

tabnine
vimPlugins.completion-tabnine

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108621 run on x86_64-darwin 1

1 package built:

tabnine

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108621 run on x86_64-darwin 1

1 package built:

tabnine

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108621 run on x86_64-linux 1

2 packages built:

tabnine
vimPlugins.completion-tabnine

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108621 run on x86_64-linux 1

2 packages built:

tabnine
vimPlugins.completion-tabnine


Adapt TilingComposite to Pegasus architecture

Right now the TilingComposite is only defined for Chimera-structured hardware graphs.
See also #294

It would make sense to have a simpler DisplacementComposite or AutomorphicComposite that attempts to move/rotate an embedding on the processor. This would have independent value for noise reductions (same reason as SRT).  The TilingComposite would reuse these transformations (accumulating them subject to no intersection)
.


Unnecessarily stores updates and wastes disk space

Microsoft PowerToys version
all versions
Running as admin

[ ] Yes

Area(s) with issue?
General, Installer
Steps to reproduce
Installed PowerToys and leave it over time
✔ Expected Behavior
Cleans out older update installers
❌ Actual Behavior
Wastes disk space by leaving update installers under C:\Users\[username]\AppData\Local
Other Software
No response

@yuyoyuppe, @davidegiacometti
Don't we clean up?

/bugreport

Starting from 0.59 old setups are expected to be removed after the update.
@gbraad how are you updating PowerToys? From the settings or manually? A bug report may be useful here.

Yes, we should clean up the old version files, I'll verify. @gbraad could it be a privilege issue?

Admin and only user, so unlikely.

I have since removed powertoys. I remember it asked me from time to time, but I don't regularly install the updates especially as the usage was minimal. It autostarter launcher and fancy ones (though not used). I would expect these apps trigger the update process.

I remember it asked me from time to time, but I don't regularly install the updates

Am I understanding that you used an older version? What was the latest you actually installed? As mentioned above: recent installations/version do clean up.

Indeed, this was fixed in 0.59.0 or 0.59.1, so from the user comments it looks like PowerToys ended up not getting updated to one of these versions.


Outdated dependency

Hello,
Please upgrade the "tempfile" dependency from ^1.1.0 to the at least 4.0.0 or the latest 5.0.0 if possible.
"process-streams" relies on "tempfile", but older versions ofr "tempfile" are dependant on an older version of "uuid", which is buggy and is deprecated. Seems like "tempfile" dropped uuid as a dependancy in version 4.0.0.
So, the warning is not there with "tempfile" 4.0.0 (and 5.0.0)
Thank you!
Screenshot of the uuid dependency deprecation warning:

Fixed in version 1.0.3


controls/codec: add few HEVC & VPx encoder controls

I am so sorry, I've just realized that somehow I've only uploaded the H264 controls. Here are the rest of them
This changes introduces safe wrappers over few HEVC, VP8, VP9 encoder controls, namely:

V4L2_CID_MPEG_VIDEO_HEVC_MIN_QP
V4L2_CID_MPEG_VIDEO_HEVC_MAX_QP
V4L2_CID_MPEG_VIDEO_HEVC_LEVEL
V4L2_CID_MPEG_VIDEO_HEVC_PROFILE
V4L2_CID_MPEG_VIDEO_VP8_PROFILE
V4L2_CID_MPEG_VIDEO_VP9_PROFILE
V4L2_CID_MPEG_VIDEO_VPX_MIN_QP
V4L2_CID_MPEG_VIDEO_VPX_MAX_QP

No worries - thank you!


Functionality to support emitting Kafka Events for tracking

Dear DIL maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
Description
This request consists of including metrics/events as part of DIL. In this initial commit we'll be emitting events from different stages of job execution. These events can be helpful in identifying critical aspects such as network bottle necks, automatic integration points such as number of flows, formats, functionalities etc for reporting purposes. The metadata can also be used for troubleshooting purposes as well
We need a reporter/client to emit the events built. This PR includes Kafka Based event implementation which uses Open source li-kafka-clients. Users can create their own Reporter by implementing EventReporter Interface.
All the Events have a generic schema CdiTrackinhEvent where metadata holds off of the essential information in the form of a Map. The name column is used for filtering the type of event.
To include a new event, building an event can be included inside the EventHelper class.
Tests

The functionality is tested with Kafka internal environment.
Included a Simple Integration Test along with a sample pull file to reference essential properties to turn on metrics

To use the metrics use following properties
ms.metrics.enabled=true
ms.kafka.events.topic.name=<YourTopicName pereferred name CdiTrackingEvent>
bootstrap.servers=kafka.test.company.com:<port>
value.serializer=io.confluent.kafka.serializers.KafkaAvroSerializer
kafka.schemaRegistry.class=org.apache.gobblin.kafka.schemareg.LiKafkaSchemaRegistry
kafka.schemaRegistry.url=http://schemaregistry.test.company.com:<port>/schemaRegistry/schemas

Include SSL properties as defined in Kafka Documentation if you want to connect to Kafka through secured connection
Next Steps

Support for Events using Kafka Rest Client
Support to accept Kafka SSL properties with ms.ssl
Create more events such as pagination, workunit retry, end-of-job event

Yogesh will address comments in a separate PR.


Confusing red color for my custom runner

🐛 Bug Report
If your jest runner hashes to an unfortunate value, its test suites are marked with a red badge that at first glance looks like they are failing. I spent an hour trying to figure out what about my tests was failing.
To Reproduce
Have a runner named something that hashes to 'red' from https://github.com/facebook/jest/blob/master/packages/jest-config/src/color.ts#L21
Expected behavior
I don't think a test runner should show me red text unless something went wrong.
I can send a PR that removes red, green, and yellow from the colors that the test runner can hash, as each of those colors imply something about the tests. However that greatly increases the chances that two test runners will collide with the same color.
Through this I've learned about setting displayName: {color, name}, which is really cool. But this override is required by everyone that uses my runner, otherwise they will get a scary red name. I'd have to add a line about it in the docs. I'd rather just tweak my name until it hashes to cyan. If I could set the color from the runner itself that would be cool.
Maybe it would be simplest to just have one color for non-default runners? Or leave everything white by default?

Letting a runner set a default color makes sense to me. E.g. iOS runners might want some white thing and Android green.
I also don't think we should reuse any colors that the default reporter uses (even though it increases the chances of collisions), so removing yellow, green and red SGTM.
@jeysal @thymikee thoughts on this one?

removing yellow, green and red SGTM
👍

We could add black and gray instead, but I'm a bit sad that the color vibrance that people get by default will go away.
Is the output really that bad? You get a red/green-background all-caps PASS/FAIL right next to the display name.
Re runner default colors, makes sense to me.
I guess this would be taken from something require('runnerPath').color or so.

Related: https://github.com/facebook/jest/issues/9459