Running InferenceClient in docker for TGI web interface

System Info
OS: Ubuntu 18.04
TGI version: latest
Information

[X] Docker
[ ] The CLI directly

Tasks

[X] An officially supported command
[ ] My own modifications

Reproduction
I have succesfully deployed TGI (https://github.com/huggingface/text-generation-inference) with LLama-2 using the standard command:
model=meta-llama/Llama-2-7b-chat-hf
volume=$PWD/data # share a volume with the Docker container to avoid downloading weights every run
token=<some_token>

docker run --gpus all --shm-size 1g -e HUGGING_FACE_HUB_TOKEN=$token -p 8080:80 -v $volume:/data ghcr.io/huggingface/text-generation-inference:latest --model-id $model --sharded true --num-shard 2

TGI Backend for the model is running on the Ubuntu 18.04.
In order to test requests I used following commands:

directly on the server:

curl <IP_ADDRESS>:8080/generate \
    -X POST \
    -d '{"inputs":"What is Deep Learning?","parameters":{"max_new_tokens":20}}' \
    -H 'Content-Type: application/json'

or
curl <IP_ADDRESS>:8080/generate \
    -X POST \
    -d '{"inputs":"What is Deep Learning?","parameters":{"max_new_tokens":20}}' \
    -H 'Content-Type: application/json'

where <IP_ADDRESS> is a Gateway of the Backend docker image.

on local machine:

curl <IP_ADDRESS>:8080/generate \
    -X POST \
    -d '{"inputs":"What is Deep Learning?","parameters":{"max_new_tokens":20}}' \
    -H 'Content-Type: application/json'

where <IP_ADDRESS> is an Ubuntu server IP address.
You can access API for testing requests from your local machine:
http://<IP_ADDRESS>:8080/docs/#/
where <IP_ADDRESS> is an Ubuntu server IP address.
Every curl worked as expected.
What I want to do is to build a docker container for the web interface and run it on Ubuntu 18.04 (same environment as TGI), so that it can be accessible on the local machine (basically using <IP_ADDRESS>:7860 IP address for accessing Web interface and port 7860). For this purposes I am using InferenceClient from huggingface_hub. Here is my script:
import gradio as gr
from huggingface_hub import InferenceClient

client = InferenceClient(model="http://<IP_ADDRESS>:8080")

SYSTEM_PROMPT = """<s>[INST] <<SYS>>
You are a helpful, respectful and honest assistant. Always answer as helpfully as possible, while being safe.
Your answers should not include any harmful, unethical, racist, sexist, toxic, dangerous, or illegal content.
Please ensure that your responses are socially unbiased and positive in nature.
If a question does not make any sense, or is not factually coherent, explain why instead of answering something not correct.
If you don’t know the answer to a question, please don’t share false information.
<</SYS>>
"""

def format_message(message: str, history: list, memory_limit: int = 3) -> str:
    """
    Formats the message and history for the Llama model.

    Parameters:
        message (str): Current message to send.
        history (list): Past conversation history.
        memory_limit (int): Limit on how many past interactions to consider.

    Returns:
        str: Formatted message string
    """
    # always keep len(history) <= memory_limit

    if len(history) > memory_limit:
        history = history[-memory_limit:]

    if len(history) == 0:
        return SYSTEM_PROMPT + f"{message} [/INST]"

    # Takes the last user question (history[0][0]) and last model answer history[0][1] from the history list
    formatted_message = SYSTEM_PROMPT + f"{history[0][0]} [/INST] {history[0][1]} </s>"

    # Handle conversation history: takes from history list starting from second element to the memory_limit
    for user_msg, model_answer in history[1:]:
        formatted_message += f"<s>[INST] {user_msg} [/INST] {model_answer} </s>"

    # Handle the current message
    formatted_message += f"<s>[INST] {message} [/INST]"

    return formatted_message

def inference(message, history):

    try:
        query = format_message(message, history)

        partial_message = ""
        for token in client.text_generation(
            query,
            max_new_tokens=512,
            temperature=.1,
            top_k=40,
            top_p=.9,
            repetition_penalty=1.18,
            stream=True):
            partial_message += token
            yield partial_message
    except Exception as e:
        # Print the exception to the console for debugging
        print("Exception encountered:", str(e))
        # Optionally, you can yield a message to the user
        yield f"An Error occured please 'Clear' the error and try your question again"

# Create and modify the theme to use Teal
theme = gr.themes.Default(primary_hue="teal").set(
    loader_color="#008080",  # Teal color for loader
)

gr.ChatInterface(
    inference,
    chatbot=gr.Chatbot(height=475),
    textbox=gr.Textbox(placeholder="Please ask me a Question...", container=False, scale=7),
    description="I am a general knowledge Chatbot that uses LLaMA 7B-Chat model from Meta.",
    title="A-Team chat: how can I help you?",
    examples=["What is the meaning of life?"],
    retry_btn="Retry",
    undo_btn="Undo",
    clear_btn="Clear",
    theme=theme,  # Apply the theme here
).queue().launch()

where <IP_ADDRESS> is a is a Gateway of the Backend docker image.
When I run docker image there is nor error, but unfortunately  I cannot access web interface on my local machine ( using <IP_ADDRESS>:7860).
But If I start the script locally without docker (python3 web.py), everything works well an I can use web interface using http://<IP_ADDRESS>:7860 route.
My Dockerfile:
# Use an official Python 3.9 image as the base image
FROM python:3.9

# Set the working directory to /app
WORKDIR /app

# Copy the requirements.txt file into the container at /app
COPY requirements.txt /app

# Install any needed packages specified in requirements.txt
RUN pip install -r requirements.txt

# Copy the web.py file into the container at /app
COPY web.py /app

# Make port 7860 available to the world outside this container
EXPOSE 7860

# Define the command to run your application
CMD ["python", "web.py"]

Docker commands:
docker build -t llama_chat .
docker run --security-opt seccomp:unconfined -p 7860:7860 -d llama_chat

requirements.txt
gradio==3.50.2
huggingface_hub==0.18.0

--security-opt seccomp:unconfined is a necessary workaround for Ubuntu 18.04, because otherwise docker run will give you errors.  (https://medium.com/nttlabs/ubuntu-21-10-and-fedora-35-do-not-work-on-docker-20-10-9-1cd439d9921)
Logs
No errors in logs

Expected behavior
Access InferenceClient web UI on the local machine.

I fixed the problem by setting server_name to "<IP_ADDRESS>" launch(server_name="<IP_ADDRESS>",server_port=7860)

你好，可以给我发一下完整的代码吗，非常感谢！

I fixed the problem by setting server_name to "<IP_ADDRESS>" launch(server_name="<IP_ADDRESS>",server_port=7860)

Hello, can you send me the complete code? Thank you very much!


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_bbv5fa_5l3/clone/recipe/meta.yaml:27: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_bbv5fa_5l3/clone/recipe/meta.yaml:39: missing_pip_check: For pypi packages, pip check should be present in the test commands
ERROR: /tmp/abs_bbv5fa_5l3/clone/recipe/meta.yaml:44: incorrect_license: The recipe's about/license key is not an SPDX compliant license or license exception, closest match: Apache-2.0
WARNING: /tmp/abs_bbv5fa_5l3/clone/recipe/meta.yaml:48: missing_description: The recipe is missing a description
Errors were found


Suggested steps to install on Ubuntu 22.04

Hi Gene,
Thank you again for making the useful wg-tool and sharing it with us! It really saves me a lot of time and brain cells to manage wg keys. I would like to share the steps I got it to work on Ubuntu 22.04. Feel free to include in your documentation to help others.

Assume these are already installed

apt-get install wireguard qrencode

Install necessary python3 packages for wg_tool:

$ sudo apt install python3 python-is-python3 python3-poetry python3-build \
  python3-installer python3-qrcode python3-tomli-w python3-tomli python3-netaddr

Build and install

$ git clone https://github.com/gene-git/wg_tool
$ cd wg_tool

$ sudo pip install hatchling

$ /usr/bin/python -m build --wheel --no-isolation

$ sudo ./scripts/do-install /

Getting wg and wg-tool to work

$ sudo -i
# cd /etc/wireguard

# wg-tool --init

# vi config/server/server.conf

Add the first set of users with wg-tool

# wg-tool --add_user --dns_search Mary:mac,iphone,ipad

# ln -s wg-configs/server/wg0.conf .

# systemctl enable wg-quick@wg0
# systemctl start wg-quick@wg0
# systemctl status wg-quick@wg0

# wg show

Add more users

# cd /etc/wireguard
# wg-tool --add_user --dns_search Joe:mac,iphone,ipad

# systemctl reload wg-quick@wg0

# wg show

# wg-tool --list_users

# wg-tool -rrpt

Also, I don't use PostUp scripts. I will persistent iptable rules
# apt install iptables-persistent
# systemctl status iptables
# systemctl enable iptables
# systemctl restart iptables

Change /etc/iptables/rules.v4
Note:

<IP_ADDRESS>/24 is used for wg subnet.
On Ubuntu ens3 is the default network device name

# == For Wireguard VPN ==
*nat
:PREROUTING ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
# -- NAT for vpn clients from wireguard
-A POSTROUTING -o ens3 -s <IP_ADDRESS>/24 -j MASQUERADE
COMMIT
# ---------------------
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -i lo   -j ACCEPT
-A INPUT -i wg+  -j ACCEPT
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -m state --state INVALID             -j DROP
# -- Wireguard ports
-A INPUT -i ens3 -p  udp -m multiport --dports 51820 -m state --state NEW -m limit --limit 10/sec --limit-burst 20 -j ACCEPT
-A INPUT -i ens3 -p icmp -m icmp --icmp-type 8 -m limit --limit 5/sec -j ACCEPT
# -- last as the default rule for input
-A INPUT -j DROP
# -- forward --
-A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -m state --state INVALID             -j DROP
-A FORWARD -i wg+  -s <IP_ADDRESS>/24          -j ACCEPT
-A FORWARD -j REJECT --reject-with icmp-port-unreachable
# -- out --
-A OUTPUT -m state --state INVALID -j DROP
COMMIT
# == EOF ==

Run commands:
# systemctl restart iptables

# iptables -nvL
# iptables -t nat -nvL


Model is not learning on Clotho datasets

Hello,
Thank you for the great work and implementation. I have followed the instructions exactly in the Readme to train on Clotho dataset through
conette-train expt=[clotho_cnext_bl] pl=baseline
The only difference is that I specified cnext_bl_path=$HOME/.cache/torch/hub/checkpoints/convnext_tiny_465mAP_BL_AC**_70kit.pth**, which is the checkpoint that is downloaded when running prepare
However, the metrics are much worse. The fense score is 0.230 compared with the one reported in the paper 0.516, and the SPIDEr score is 0.085 compared with the 0.301. Do you know what might be the issue?
Thank you!

Hi!
Thanks for reporting this.
Seems like something is weird with the pretrained Convnext model, maybe the downloaded file is wrong.
Did you run the AAC model during 400 epochs with the default hyperparameters?

Hello,
Thank you for your prompt response. Yes I run the AAC model with the default hyper-parameters for 400 epochs.
I will test with your fix and let you know.

Hello,
I have tried training again on the dev branch after your fix. However, unfortunately, the problem is still there. Both validation and training loss are decreasing. Yet, they stay high in values and therefore the metrics are poor.
I am looking forward to hear your thoughts about this. Thank you for your help.

Sorry, the commit only fixed an error occurring while loading Convnext, and I forgot you would have this message here. The problem hasn't been fully resolved yet, and I am still looking into it.

No worries. Thank you very much for your help and I am looking forward for the fix.

Hello,
Do you any updates on this?
Also, do you know if the issue is only with the baseline model, or the conette model too (e.g train CoNeTTE on AC+CL+MA+WC, specialized for CL)?

The problem is linked to the CNext model not loading correctly, and the wrong checkpoint being loaded. This means that the pre-processed audio features in the HDF files are invalid, which has an impact on the CNext-trans and CoNeTTE models. I have fixed the loading, and I am now checking whether the audio features are properly calculated.

Hello,
Thank you very much. Yes! this seems to fix the issue.
I can confirm that training on CL and testing on CL obtained fense 0.508 compared to 0.516 in the paper, and spider 0.296, compared to 0.301 in the paper, which is very close.
Thank you again. I am closing the issue for now.


Question: What are next steps for ERR_MOUNT_NESTED? (Workers Pipeline depth = 32)

I bumped into ERR_MOUNT_NESTED when I tried to do the following
root
  - A
  - B
  - C
    - D

I see that this was originally added as a safeguard ~9mo ago: https://github.com/cloudflare/miniflare/commit/adc67e5b817f547b0ceab80b480025f0608a588b#diff-30c9b4cbdb8daac14a1c0d306ba87bcea041b2d1df84345de2e4aa09fa962ac5R77-R88
Yet now (since May'22) Workers have declared pipeline depth of 32 which makes ERR_MOUNT_NESTED a behaviour mismatch:
https://github.com/cloudflare/cloudflare-docs/pull/4354/files#diff-e439dfcf56456d5d944044101fc930e93be3b50a3bee03226f31db5796d47972R47
@mrbbot what was the original cause for not supporting nesting? I mean but for the obvious "too early to take care about it"/"more important things to cover first")?

@mrbbot OK, so now, when you rephrased it I understood what "all mounts are automatically accessible" actually mean in:
https://github.com/cloudflare/miniflare/blob/76bc1a64efc07e65a4ab5e98e50e25889f65999d/docs/src/content/core/mount.md?plain=1#L78-L80
In order to make it work I had to

Declare the d binding on root level

# ./root/wrangler.toml

[miniflare.mounts]
a = "./a"
b = "./b"
c = "./c"
+ d = "./d"

I'm not 100% happy about it, but that's OK for now.
I guess I'll scan directories and just pass the non-direct ones (or all of them) via --mount in order to omit the hard-coding

move the mounts in C from top-level to environment

# ./c/wrangler.toml

- [miniflare.mounts]
+ [env.dev.miniflare.mounts]
d = "../d"

adjust the dev script I have in package.json

{
  "scripts": {
-    "dev": "miniflare --live-reload --debug --modules dist/index.mjs",
+    "dev": "miniflare --wrangler-env dev --live-reload --debug --modules dist/index.mjs",
  }
}

After doing both it worked **and** I still can run `C` in `dev` environment with `D` mounted there (not loosing which was actually my aim).
If I propagate that to my whole setup (intended to be ~15 workers with up to 4 levels of nesting at the moment) it seems like it's just fine.

Thanks once again for pointing me in right direction


[WIP] Restart after install page

Currently Gitea will simply try to run normally after the install page has completed. This unfortunately doesn't quite work with duplicate log entries and other problems.
This PR causes Gitea to completely restart after the install page has been run.
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

Codecov Report

Merging #12696 into master will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master   #12696      +/-   ##
==========================================
- Coverage   43.31%   43.30%   -0.01%
==========================================
  Files         645      646       +1
  Lines       71527    71567      +40
==========================================
+ Hits        30981    30994      +13
- Misses      35540    35555      +15
- Partials     5006     5018      +12

Impacted Files
Coverage Δ

cmd/web.go
0.00% <0.00%> (ø)

modules/graceful/manager.go
27.10% <0.00%> (-1.93%)
:arrow_down:

modules/graceful/manager_unix.go
32.74% <0.00%> (-3.90%)
:arrow_down:

modules/graceful/restart.go
0.00% <0.00%> (ø)

routers/install.go
0.00% <0.00%> (ø)

routers/private/manager_unix.go
0.00% <0.00%> (ø)

modules/util/timer.go
42.85% <0.00%> (-42.86%)
:arrow_down:

modules/sync/unique_queue.go
38.77% <0.00%> (-6.13%)
:arrow_down:

modules/notification/mail/mail.go
34.48% <0.00%> (-3.45%)
:arrow_down:

modules/notification/ui/ui.go
80.55% <0.00%> (-2.78%)
:arrow_down:

... and 13 more

Continue to review full report at Codecov.

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


Large, very spammy log file generation

It's logging mostly the same line thousands of times per game session, sometimes leading the log file to bloat to over 100mb. Not a big deal, the mod seems to work properly. Just thought it very odd. Here's the line it spams constantly.
[2024-09-10 11:35:39.344] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.360] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.377] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.394] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.410] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.427] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.443] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.460] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.477] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.493] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.510] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.527] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.543] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.560] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.577] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.593] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.610] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.627] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.644] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.660] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.677] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.694] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.710] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.727] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.744] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.760] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1
[2024-09-10 11:35:39.777] [SMTVFix] [info] Set CVARS: Set r.DefaultFeature.AntiAliasing to 1

Should be fixed in v0.9.8a
I've also added a limit on log file size to 10MB to stop this kind of thing from happening again.


Improve navigation between Plan and Admin areas

Create a more intuitive way to switch between plan and admin areas by, e.g.:

add "Admin area" tab to main menu bar
remove "Admin area" from top right drop-down menu
add "Plan area" or "View plans" tab to main menu bar when in Admin area
It's not clear to users that DMPonline logo takes you back to My plans dashboard (after signing in)

Pivotal ticket: https://www.pivotaltracker.com/story/show/120873081
Screenshots of DMPonline Plan and Admin areas

closing as this is encompassed by changes within #161


Project name with camel case name and digits fails to initialize

A project called AoC01 fails to perform the first execution with a
Module local.Ao_C_01.Main not found.

error and obviously looks broken in GUI:

Seems like #8649 has not completely addressed all normalization issues.
The only workaround is currently to provide an explicit config property:
normalized-name: AoC01

Cannot reproduce it on the current develop. @hubertp if you were using the dev build, did you rebuild the project manager?

hmm, couldn't reproduce either anymore. I will reopen if I encounter this again.


Calibration fails for phospho-enriched TMT run

I'm trying to run calibration on a published phospho-enriched TMT dataset, and all but two of the files fail to calibrate. Has anyone else tried to run calibration on such a dataset or know why it's failing?

Posting them to \bison\share\Projects\MetaMorpheusPhosphoTmtU2OS

The search works great without the calibration, so no rush on this one. It's something to check out down the road.

Can you include a calibration toml and database? I need more info.

I'm adding the original database and the partial results to the folder. (I didn't let the run finish, so I could start running other things.) Thanks for looking into this!

I ran G-PTM-D before the calibration in this run because I knew calibration failed in the past... I was wondering if it was because there weren't enough phosphos annotated in the database for the phospho-enriched run. It turns out a similar number of files failed with or without GPTMD.
The GPTMD results are included in the folder.

It looks like the TMT mods don't have a chemical formula added. Calibration uses this information to calculate the accurate mass and discards the identification if it's not present. For this dataset, that means it has to have an N-terminal acetyl and no lysines, which is pretty rare. I'll try to add the chemical formulas for the TMT mods.

Maybe you can get something close. But, unfortunately, neither TMT nor any of the other so-called isobaric tags are truly isobaric at high resolution. They are isobaric enough to be selected together for fragmentation. But there still equal. We don't want them to be relatively miscalibrated becasue the spacing between the various diagnostic ions is the key for quant.

Thanks for finding that out, Zach, and good point, Michael.
I suppose we could calculate the chemical formula for each of the multiplex-labeled peptides, and then they would get aggregated by IsotopicDistribution based on the resolution. But we'd want to report the MS1 identification as one peptide, not an ambiguous ID between the multiplex-labeled peptides.

I talked with Rob about this and he suggested we supplant the chemical formula with an averagine model for TMT (and other cases). I'm trying this right now to see if the calibration improves your data or if it makes it worse.
I'm pretty sure the TMT labels are the exact same mass. There is no neucode difference.

you could be right. i might have mixed things up. best to double check for higher multplexing though. 11plex

Still working their magic with just 4 carbons and 1 nitrogen for TMT11

Hi Anthony,
Because the intact mass for all of these labels is identical, we can just add the chemical formula to tmt.txt (located in MetaMorpheus\EngineLayer\Mods\tmt.txt
I've attached an updated version here that you can use as a short term solution.
I've also opened a PR to update the file.
This is still going to be an issue for iTRAQ, since those masses do have the neutron-binding energy mass differences. We could use averagine to model the theoretical isotopic distribution, but we'll still be stuck with the issue of ensuring that all of the observed MS1 peaks are being assigned to the correct theoretical MS1 peaks.
This is a big undertaking, but will be important for the calibration of anything that uses these small mass differences (iTRAQ, DiLeu, neucode SILAC)
tmt.txt

PrecursorMassTolerance = "±34.6907 PPM"
ProductMassTolerance = "±5.1149 PPM"
Oof. Okay, that's not great. I'll look again.

This is bizzare. I was expecting it to shift the distribution 30 ppm, but it smeared it

Thanks for sharing the plots. That is bizarre!


variances in typescript checking times

Hi
I've only started playing with craco and this plugin tonight, so I may well be missing something pretty obvious.
We have a large CRA typescript project which I'm experimenting with. The craco.config.js looks as follows:
// craco.config.js
const SpeedMeasurePlugin = require("speed-measure-webpack-plugin");
const CracoEsbuildPlugin = require("craco-esbuild");
const smp = new SpeedMeasurePlugin();
const { ProvidePlugin } = require('webpack');

module.exports = {
  webpack: {
    configure: (webpackConfig) => smp.wrap(webpackConfig),
  },
  plugins: [
    {
      plugin: CracoEsbuildPlugin,
    }
  ],

};

If I disable CracoEsbuildPlugin and run
GENERATE_SOURCEMAP=false INLINE_RUNTIME_CHUNK=false IMAGE_INLINE_SIZE_LIMIT=0 NODE_OPTIONS=--max-old-space-size=4096 craco build

I get the following
 SMP  ⏱
General output time took 1 min, 33.73 secs

 SMP  ⏱  Plugins
TerserPlugin took 37.81 secs
ForkTsCheckerWebpackPlugin took 21.21 secs
IgnorePlugin took 3.79 secs
ESLintWebpackPlugin took 2.19 secs
OptimizeCssAssetsWebpackPlugin took 0.752 secs
HtmlWebpackPlugin took 0.13 secs
ManifestPlugin took 0.005 secs
MiniCssExtractPlugin took 0.002 secs
InterpolateHtmlPlugin took 0.001 secs
DefinePlugin took 0.001 secs
ModuleNotFoundPlugin took 0 secs

 SMP  ⏱  Loaders
babel-loader took 29.52 secs
  module count = 2247
modules with no loaders took 7.43 secs
  module count = 119
mini-css-extract-plugin, and
css-loader, and
postcss-loader took 2.43 secs
  module count = 1
css-loader, and
postcss-loader took 1.39 secs
  module count = 6
url-loader took 0.097 secs
  module count = 1
html-webpack-plugin took 0.023 secs
  module count = 1

with CracoEsbuildPlugin enabled I'm seeing
 SMP  ⏱
General output time took 1 min, 27.34 secs

 SMP  ⏱  Plugins
ForkTsCheckerWebpackPlugin took 1 min, 4.92 secs
IgnorePlugin took 2.31 secs
ESLintWebpackPlugin took 1.89 secs
HtmlWebpackPlugin took 0.116 secs
ManifestPlugin took 0.006 secs
MiniCssExtractPlugin took 0.006 secs
InterpolateHtmlPlugin took 0.001 secs
ModuleNotFoundPlugin took 0 secs
DefinePlugin took 0 secs

 SMP  ⏱  Loaders
modules with no loaders took 15.49 secs
  module count = 1780
esbuild-loader took 11.15 secs
  module count = 522
mini-css-extract-plugin, and
css-loader, and
postcss-loader took 1.8 secs
  module count = 1
css-loader, and
postcss-loader took 1.1 secs
  module count = 6
url-loader took 0.116 secs
  module count = 1
html-webpack-plugin took 0.015 secs
  module count = 1

so whilst esbuild is quiker (yay!) ForkTsCheckerWebpackPlugin is approx 3 times longer and modules with no loaders twice as long
I'm stumped as to why I'm seeing such a difference here - does anyone have any ideas?
Thanks!

I'm bumping this as I encountered the same problem as @pollen8 ..


Task name generation

In version 3.X the retry logic is the Laravel built-in solution.
After upgrading to 3.5.0 I faced to the following problem.

Job was created and sent to the Cloud Tasks.
Laravel handler was called but job processing failed (due to application error).
When the new (retry) job was constructed, the task name was unchanged. However, sending it Cloud Task failed because a queue cannot contain two tasks with the same name in a short period of time.

As a result, the job failed then disappeared.
Google\ApiCore\ApiException
{
    "message": "The task cannot be created because a task with this name existed too recently. For more information about task de-duplication see https:\/\/cloud.google.com\/tasks\/docs\/reference\/rest\/v2\/projects.locations.queues.tasks\/create#body.request_body.FIELDS.task.",
    "code": 6,
    "status": "ALREADY_EXISTS",
    "details": []
}

I created a small patch, and it works perfectly.
diff --git a/src/CloudTasksQueue.php b/src/CloudTasksQueue.php
index c066687..2cda3d4 100644
--- a/src/CloudTasksQueue.php
+++ b/src/CloudTasksQueue.php
@@ -197,7 +197,7 @@ class CloudTasksQueue extends LaravelQueue implements QueueContract
             $this->config['project'],
             $this->config['location'],
             $queueName,
-            $displayName . '-' . $payload['uuid']
+            $displayName . '-' . $payload['uuid'] . '-' . ($payload['internal']['attempts'] ?? 0)
         );
     }

Thanks, will check this later!

Also seen this live in production. I think it might be more prudent to append a timestamp?

OK, I created a Pull Request. I added a timestamp at the end (because it seems more unique), but I'm questioning if adding the attempt number is better (because it's also unique + it prevents duplicate creation of the same attempt - if that ever happens).
Curious to know other opinions so I'll wait for a bit and maybe merge it by Friday otherwise. Thanks!

Should be fixed in v3.5.1!


Updating warning to use warning syntax

Warning was wrapped in "alert" instead of using the actual WARNING wrapper

Thanks for the PR Jason!  Should reach the live site in ~20 min


Advance Snyk parser to parse SCA output

Take a look at this dicussion: https://github.com/DefectDojo/django-DefectDojo/discussions/8489

Snyk has four different modules now, snyk code, snyk container, snyk IaC and snyk Open Source, current defectdojo is only supporting snyk open source, could you please add support for snyk code as well which is the sast engine for snyk, please find the attached json output for snyk code here
vuln.json

Sure. If you also have output from the other modules available, we can also make a parser for these.

Thanks I will try to get the output from them as well, If you could point me to some documentation or guidance on how to create these parsers, that would be very helpful

I can create the parser, I created multiple parsers in the past already.

cool, I am working on generating the reports from other modules, I will share with you over the weekend

This is the output for snyk container
container_vuln.json

Snyk container already works by default. I tested it.

This can be closed @mtesauro

@manuel-sommer just curious if snyk code parser now works? I can only see information about Open source and container?

https://github.com/DefectDojo/django-DefectDojo/pull/9289

Test it out, it should


Data Types in Solidity

Project title
Data types in Solidity
Project Description
An Ultimate guide on data types of Solidity, A great place to get started with solidity and its data types.
Domain

[] Solidity
[] Python
[] JavaScript
[] Golang
[] Other, feel free to mention below

Are you contributing under any open-source program ?
SSOC

I would like to work on this issue.

@ASHISHKUMAR2411   this issue can be done in the previous issue that is #50

Okay Great, I will do that, I first thought to keep them in separate files as First about Data types and then about modifiers, events, etc. Nevertheless i will create in one file

@TripathiShyaamal are u including all this in your study material that mentioned above

Ya I'll be including these.

@ASHISHKUMAR2411 sorry but this issue will be cover in #46


[Runtime] Disable prespecialized metadata if we have overridden images.

We need to check for overridden images on every image load, otherwise XCTest (among others) may dlopen() an image that pulls in something that is overridden, at which point the prespecialized metadata won't match the image we loaded.
rdar://125727356

Explanation: We need to turn off prespecialized metadata if we've overridden an image in the shared cache.
Original PR: #72833
Reviewed by: @mikeash
Risk: Low. Disabling prespecialized metadata just reverts us to the original code path.
Resolves: rdar://125727356
Tests: We don't have a specific test for this.

@swift-ci Please test macOS platform


fix large file test and ignore size on windows

I defined a temporary directory for the client and added a save path argument for the PUT cases.
Add delay after put large file.
Since Windows does not seem to support the SIZE command, I have ignored it.
I have merged these changes into my main branch, and the CI works fine.
However, it is important to note that when PUT is given only one argument, which is the client's local file path, it can be difficult to distinguish whether the received argument is the client path or the desired save path.

Wow thank you very much I was testing windows using the GitHub actions so it was taking alot of time,
Can you make sure Linux is stable since sometimes it fails the test and sometimes it works so I want to make sure it is stable before releasing


update to current MongoDB versions for integration tests

Seems like the tarball for 3.0.9 went away and broke one of the builds. Maybe.

Or maybe it was 3.2.3. Either way it's… bad.

So, I guess that wasn't it. Can anyone explain this persistent error, only in the MongoDB 3.2 build?
https://travis-ci.org/quasar-analytics/quasar/jobs/154912156#L241
Maybe it's secondary to the real failure?

Of course this turned out not to have anything to do with the broken builds, but it's probably a good idea to keep current on these MongoDB releases anyway.

Current coverage is 72.16% (diff: 100%)

Merging #1379 into master will decrease coverage by <.01%

@@             master      #1379   diff @@
==========================================
  Files           215        215
  Lines         12234      12234
  Methods       11973      11973
  Messages          0          0
  Branches        118        118
==========================================
- Hits           8830       8829     -1
- Misses         3404       3405     +1
  Partials          0          0

Powered by Codecov. Last update 4f2a046...2bc53eb


chore(deps): update docker.io/library/golang docker tag to v1.19.11

A very lightly edited cherry-pick of commit 93e613e to try and ensure that renovate doesn't attempt to autoclose it.

/test-backport-1.11

/test-1.19-4.9

/test-1.21-4.9

/test-1.19-4.9


Add support for artillery processor configuration

Artillery has the concept of processor for adding custom logic before/after query executions. I noticed this doesn't work in serverless-artillery. Digging a bit further it seems that artillery converts the processor value in the script into functions outside of the artillery-core project. I'm not sure why they do that, but the relevant few lines are of code can be found here. In order to get this feature to work in serverless-artillery, the equivalent procedure has to happen in the handler.js lambda. So I extended it to do just that and now I can have custom Javascript in my tests which is great!
One small issue is that the pre-commit script does not allow dynamic require so current code fails pre-commit. If you want to support this feature you will have to relax that.
[edit: direct link to the line of code]

I added some tests for this. While adding them, I realized that because of the way the processor loading works it would be a problem if for some reason loadProcessor were called multiple times on same script. So I added an additional guard against that and a test to cover it.
Also, saw your comment on that artillery-core project. Hopefully this will be addressed in core in the future so you can always have feature parity with artillery.

Thanks @gcuni, appreciate the tests!  Great changes.


Usage of void and replacement with core::convert::Infallible

Hello, I've noticed a crate named void is used for infallible situations. However, since Rust 1.34.0, we have Infallible, which performs this task. Am I missing something, or could the void type the crate offers be replaced by this type?

The missing pieces is the ResultVoidExt trait which gives us the handy void_unwrap() method.
core already has an equivalent in the making, called into_ok() but unfortunately this is still unstable.
So far, my take on the situation was to wait on stabilization of into_ok() and switch then.  That is, unless the use of void proves to be problematic for downstream users in some place.  If that is the case, please speak up :)

See also https://github.com/rust-embedded/embedded-hal/issues/329
At least in embedded-hal 0.2.x there were some instances of void too. https://github.com/rust-embedded/embedded-hal/pull/150/files so regardless of what void_unwrap alternative to use, I think a migration to embedded-hal 1.0 should drop the void crate too.

Nice, thanks for digging into this!  I wasn't aware of the unwrap-infallible crate until now - I'd be totally on board with replacing void with unwrap-infallible here in avr-hal.
You are right, the best time is probably when adopting e-h 1.0 - until then I think the disruption is not worth it...


Add the "vercanard" CV template

Disclaimer: I wrote this template (but I think it is fine to add our own work to the list, please tell me if it is not)

Thanks for the awesome contribution @elegaanz !  I really like the template :)


Refactor messaging

Refactor/rename messaging folders, files, and code to better coordinate and understand message flow.
Note: There is a related issue for creating a Manifest folder with separate manifests for each browser type.
https://github.com/blockstack/stacks-wallet-web/issues/1206
Questions/concerns:

App seems misused in our naming, or at least it is unclear.
Why do we sometimes use the backgroundPort and other times not?

Tasks:

[x] Remove extension folder and restructure so we clearly define context of the script (scripts folder)
[x] Rename message-bus to content-script
[x] Remove Background folder and rename index to background
[x] Relocate popup.ts to scripts folder
[x] Refactor message-types to clearly define what message type goes with which context

[x] Separate Methods into InternalMethods and ExternalMethods
[x] Remove unused walletResponse from methods
[x] Rename walletRequest to something more inline with the other internal methods for the vault, getWallet?
[x] Rename MessageFromApp to VaultActions (bc the vault is setup like a reducer)

Proposing these changes?

I'm personally not a fan of "scripts" as the name for the folder. to me, scripts typically refer to files that run to help with build/ci work, and not to do with the application itself. Why move away from "extension"?

I think bc this folder supports the messaging scripts, mainly the background and content-script. We referenced MetaMask and they had it setup using a scripts folder structure. I definitely think is could be better. Maybe, messaging?  It seems like the entire repo is the extension so it seemed a bit off to name one folder that?

When I look at it being used in imports, I don't like just scripts either.

Agree on not using scripts. I suggested removing away from extension. This was a relic from when we also had the app, I thought. I think everything should be in src and categorised by JS context. background, context, wallet/popup, inpage.

Ok, I misunderstood that part. So, each one of those would be it's own folder in src?

I ended up changing the folder to messaging and pushed it up. Definitely open to reverting it though ...just was experimenting a bit.

I think I'll try another version today separating them by contexts and see how that goes.

For me personally when it comes to organization of this repo, this is what I'd like
src
  common
  background
  content-scripts
  inpage
  app

common: anything shared between 2+ contexts (background/inpage/app)
background: anything to do with the background context\
background: anything to do with the content-scripts context
inpage: anything to do with the inpage context
app: the react frontend for the extension

Something else we should try to consider is we should form the structure of the directories to map to entry points in our wepback config https://github.com/blockstack/stacks-wallet-web/blob/main/webpack/webpack.config.base.js#L81-L85
This is helpful reading: https://developer.chrome.com/docs/extensions/mv3/architecture-overview

Yep, I like that ...I think that is the direction Kyran wanted us to go in too. I'll refactor today and reorganize it this way ...makes sense to me for sure. Thanks for the feedback.

O yeah, this is a lot better! Will push up changes soon. I didn't move stuff into an app folder yet but definitely can.


[CosmosDB] Consistency level is too low

The CosmosDB KV code uses "bounded staleness"
consistency (or a bit lower in tests using a local
emulator).  This was already discussed in the review of
#5915, so we need to read carefully here...
I could find nothing about scan-after-write; this is potentially important
for our list-after-write consistency in staging.
Really all these consistency levels talk about cross-region consistency,
except for serializability.  Bounded staleness seems to be too low in
extreme circumstances.  It guarantees "correct" reads in a MongoDB sense, of
a single session giving correct results.  In the single-region case this is
the worrying paragraph:

For a single-region account, Bounded Staleness provides the same write
consistency guarantees as Session and Eventual Consistency. With Bounded
Staleness, data is replicated to a local majority (three replicas in a
four replica set) in the single region.

For session consistency:

In session consistency, within a single client session, reads are
guaranteed to honor the read-your-writes, and write-follows-reads
guarantees. This guarantee assumes a single “writer” session or sharing
the session token for multiple writers.

But we have multiple client sessions on different cluster members.  I see
nothing about this avoiding stale reads.  Indeed this StackOverflow
answer says that it can happen with bounded staleness.
So in practice the lakeFS application sees session consistency.  But that
means different cluster members can see different data.  I don't see
anywhere that says anything useful about
I suspect that we need strong consistency (unfortunately).

Assignees: please go over it and let me know that I'm wrong :-/

Single region write will be replicated for at least 3/4 replicas in the same region.
Because of the following:
Reads when using Bounded Staleness returns the latest data available in that region by reading from two available replicas in that region. Since writes within a region always replicate to a local majority (three out of four replicas), consulting two replicas return the most updated data available in that region.

It means we will get read after write - we always get the latest.
(Also based on the notes and the following: https://learn.microsoft.com/en-us/answers/questions/116045/azure-cosmosdb-consistency-understanding-bounded-s)

As the one who wrote the code ;) I agree with @nopcoder .
But the easiest way to settle this is with our kvtest suite. CosmosDB emulator is off by default since linux support is horrible, but it's a matter of replacing creds to make it working against a real CosmosDB database. It would be easy to prove inconsistencies using the suite with the existing tests, or new ones if necessary.

I've been thinking about it some more, and both you and I are correct.

The implementation described should give single-object consistency.  Docs don't say this, though.  So read-after-write will work.

The implementation described might not give listing consistency.  I think that we may be able to write an object and not manage to list it.  But all my examples are only for listing across two pages.
AFAICT we never perform call KV listing twice for a single API call, so we should be OK there, too.

But if single-object consistency is enough, we should be to use a much lower consistency level.  The docs do guarantee consistency equivalent to session consistency!

Keeping open.


Synchronize write to a buffer in BufferedReadStream

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: arkrasik sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@galvesribeiro - Want to put a 2nd set of eyes on this?

I've followed the thread while you where reviewing.
@arkrasik please sing the CLA and we are good 😄

Thanks again


Generate secret key pairs and addresses offline

Is there a demo of Java？ Thank you very much.

Can we close this please


[tool_crash] FileSystemException: Cannot create link, OS Error: Incorrect function., errno = 1

Command
flutter pub get

Steps to Reproduce

...
...
...

Logs
FileSystemException: Cannot create link, OS Error: Incorrect function.
, errno = 1
#0      _Link.throwIfError (dart:io/link.dart:254:7)
#1      _Link.createSync (dart:io/link.dart:182:5)
#2      ForwardingLink.createSync (package:file/src/forwarding/forwarding_link.dart:20:16)
#3      ForwardingLink.createSync (package:file/src/forwarding/forwarding_link.dart:20:16)
#4      _createPlatformPluginSymlinks (package:flutter_tools/src/flutter_plugins.dart:1055:12)
#5      createPluginSymlinks (package:flutter_tools/src/flutter_plugins.dart:985:5)
#6      refreshPluginsList (package:flutter_tools/src/flutter_plugins.dart:1087:5)
<asynchronous suspension>
#7      FlutterProject.ensureReadyForPlatformSpecificTooling (package:flutter_tools/src/project.dart:357:5)
<asynchronous suspension>
#8      PackagesGetCommand.runCommand (package:flutter_tools/src/commands/packages.dart:337:7)
<asynchronous suspension>
#9      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1297:27)
<asynchronous suspension>
#10     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#11     CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#12     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:339:9)
<asynchronous suspension>
#13     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#14     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:285:5)
<asynchronous suspension>
#15     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:115:9)

[✓] Flutter (Channel stable, 3.13.0, on Microsoft Windows [Version 10.0.22621.2134], locale it-IT)
    • Flutter version 3.13.0 on channel stable at C:\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision efbf63d9c6 (5 days ago), 2023-08-15 21:05:06 -0500
    • Engine revision 1ac611c64e
    • Dart version 3.1.0
    • DevTools version 2.25.0

[✓] Windows Version (Installed version of Windows is version 10 or higher)

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at C:\Android\SDK
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = C:\Android\SDK
    • Java binary at: C:\Program Files\Android\Android Studio\jbr\bin\java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-b2043.56-10027231)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[✓] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.7.1)
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
    • Visual Studio Community 2022 version 17.7.34009.444
    • Windows 10 SDK version 10.0.22621.0

[✓] Android Studio (version 2022.3)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-b2043.56-10027231)

[✓] VS Code (version 1.81.1)
    • VS Code at C:\Users\Rafael Azevedo\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.70.0

[✓] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.22621.2134]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 115.0.5790.173
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 115.0.1901.203

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Flutter Application Metadata
Type: app
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: efbf63d9c66b9f6ec30e9ad4611189aa80003d31
Plugins
path_provider-2.1.0
path_provider_android-2.1.0
path_provider_foundation-2.3.0
path_provider_linux-2.2.0
path_provider_windows-2.2.0

Closing this as a duplicate of https://github.com/flutter/flutter/issues/66224


data-sveltekit-replacestate does not work for #hash links

Describe the bug
When clicking on a hash link that has the data-sveltekit-replacestate attribute, the expected behavior is to update the URL without pushing a new history entry. However, the bug causes the history object to be pushed even when the data-sveltekit-replacestate attribute is used, resulting in unexpected navigation history behavior.
Reproduction
https://stackblitz.com/edit/sveltejs-kit-template-default-jsaxq9
Steps to reproduce the behavior:

Create a new SvelteKit project or open an existing one
Add a hash link with the data-sveltekit-replacestate attribute, like the following: <a data-sveltekit-replacestate href="#c">c</a>
Start the development server and navigate to the page containing the hash link
Click on the link with the attribute
Observe the URL change and the browser's navigation history

Logs
No response
System Info
Not applicable

Severity
annoyance
Additional Information
No response

I think i know why this is happening:
We have the following options element which contains:
https://github.com/sveltejs/kit/blob/5191e165b75f5616bd6b4aadf9d8a6c52e75c562/packages/kit/src/runtime/client/client.js#L1530
It returns an object which contains replace_state, which is a boolean. It activates whenever we click on  a div which contains data-sveltekit-replacestate. It will return options.replace_state as true This is working as expected.
But we have a problem, because whever we click, the logic of only updating the hash will update.That will trigger the pushHistory Which is the following
https://github.com/sveltejs/kit/blob/5191e165b75f5616bd6b4aadf9d8a6c52e75c562/packages/kit/src/runtime/client/client.js#L1564-L1592
Even if options.replace_state is true, it will always enter this itf condition and push the store because of the stores.page.set. It will never reach the expected navigate function which has the logic of triggering the replaceHistory.
This is the function that is expected to replace the state with replaceState
https://github.com/sveltejs/kit/blob/5191e165b75f5616bd6b4aadf9d8a6c52e75c562/packages/kit/src/runtime/client/client.js#L1580-L1593

@vicentematus thanks for the explanation. Are you planning to release this?

@vicentematus thanks for the explanation. Are you planning to release this?

No sir, im not currently working on it. Its free to work on it if you want (or anyone else reading this) 🤖

+1 I ran into this too. Would be nice to have a fix. What I did was just use the format href="?showModal" rather than href="#showModal" with data-sveltekit-replacestate which works as expected.

Sorry this flew under the radar. I managed to see it thanks to a GitHub browser extension I just installed that sorts issues by comment date.


The same account with different roles entered different items, menu display error

Bug recurrence operation:

A project, the role is admin, project Settings have advanced Settings menu;

Then switch to project B, the role is operator, and there is no advanced setting menu in project Settings;

Finally click back to the A project, the advanced Settings are gone.

Hi @caojiele , thanks for reaching out here. I cannot reproduce this issue in the latest release. please let us know your environment as detailed as possible.

hi @caojiele , thanks for pointing it. But IMO this is not an issue of DevOps. I prefer you creating it under kubesphere/kubesphere.

hi @caojiele , thanks for pointing it. But IMO this is not an issue of DevOps. I prefer you creating it under kubesphere/kubesphere.

#4109

hi @caojiele , thanks for pointing it. But IMO this is not an issue of DevOps. I prefer you creating it under kubesphere/kubesphere.

OK, I've recreated it.


generate: allow passing - for stdout output

What does this PR change? What problem does it solve?
Allow generating shell completions to stdout by supplying - as file name. Since generating completions to stdout for multiple shells does not make sense, enforce - is supplied only once.

Was the change previously discussed in an issue or on the forum?
Closes #2511.

Checklist

[x] I have read the contribution guidelines.
[x] I have enabled maintainer edits.
[x] I have added tests for all code changes.
[x] I have added documentation for relevant changes (in the manual).
[x] There's a new file in changelog/unreleased/ that describes the changes for our users (see template).
[x] I have run gofmt on the code in all commits.
[x] All commit messages are formatted in the same style as the other commits in the repo.
[x] I'm done! This pull request is ready for review.

Thank you for your review! I applied your suggestions with some minor modifications to make the code compile.


fetchBot is failing - profiles aren't getting refreshed

⠦ Fetching omegaup/omegaup's contributors...Promise {
  <rejected> TypeError: Cannot read property 'login' of null
    at fetchRepoContributors (/home/ubuntu/ghuser.io/db/fetchRepos.js:223:57)
    at process._tickCallback (internal/process/next_tick.js:68:7) }
/home/ubuntu/ghuser.io/db/impl/scriptUtils.js:9
      throw e;
      ^

TypeError: Cannot read property 'login' of null
    at fetchRepoContributors (/home/ubuntu/ghuser.io/db/fetchRepos.js:223:57)
    at process._tickCallback (internal/process/next_tick.js:68:7)

Vanished, closing for now.


JBPM-5374 - Process instance doesn't exit an Embedded SubProcess in an AdHoc process

@krisv could you please review?

+1

merged manually to keep the commits


chore: 添加 release create to trigger publish site

Checklist

[ ] npm test passes
[ ] tests and/or benchmarks are included
[ ] commit message follows commit guidelines

Description of change

Pull Request Test Coverage Report for Build 721258093

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.06%) to 93.593%

Totals

Change from base Build 697843160:
0.06%

Covered Lines:
10914

Relevant Lines:
11310

💛  - Coveralls


Update configure-pod-configmap.md

When following the Chinese doc, I found some translation issues. According to the English page, I fix the issues that I can find.

some translate error. eg key means 键, not 密钥, volumes means 数据卷, not 容器
some Chinese sentences don't make sense, replaced with the normal Chinese way

Nice.
/lgtm
/approve


Problem with Booleanize,

Boolean from godot core or from the script is always false
To Reproduce create a method in GDNative with boolean arg and pass true from gdscript, recived variable will be false
pretty sure this is cause by 85641c5

Fixed,


Authorization Issue

Unity 2021.1.10f1
Followed steps in Setup and created an app in Spotify.
Clicking "Sign In" brings me to the "Allow Access" page in Chrome (or Safari), but clicking "Accept" leads me to a 403 error.
I have the same callback URI listed in Unity and on the Spotify developer app settings.
Tried several different ports with the same result.
Reese

This is due to newer versions of macOS reserving port 5000 for something else. See here:
https://stackoverflow.com/questions/70913242/access-to-localhost-was-denied-you-dont-have-authorisation-to-view-this-page-h
Easy fix is just to change the port number.
Would suggest to the package owner to use a different default port or document this somewhere.
Additionally, the server port is not actually exposed on PKCEAuthConfigView.cs which makes the port a bit of a pain to change, as it is serialized but not exposed, so changing the default value in the script actually doesn't change the serialized values already on the scene.


Adding selection to the WebScreenshot workflow.

Great idea Vitor!
I installed it but didn't used it as it wanted to be able to select one part of my screen not take a screenshot of all the screen.
Is such a feature on your roadmap?

I’m a bit confused by the title and content of the request (they seem to contradict).
To be clear, are you asking for an equivalent to ⌘⇧3?

I didn't knew screenshot could only mean "all the screen".
I should have said "being able to upload to Imgur a selected area of the screen".

But that’s exactly what it does. In fact, you can only select an area of the screen. The workflow doesn’t support taking screenshots of the whole screen.

So this is perfect.
Case closed ;-)

Just curious though, why does the WebScreenshot workflow not have a CMD+SHIFT+3 counterpart? @vitorgalvao

Though I can add it, I haven’t done so yet for a number of reasons.
⌘⇧3 is way less common and useful. Particularly if you want a workflow to quickly upload screenshots, it’s unlikely you’ll want the whole screen. For the rare cases when you do want it, with ⌘⇧4 you can essentially achieve the same the same effect by selecting the whole screen (though yes, you might not find it ideal).
So we start with an issue of practicality in implementation. I use a third-party script to upload the screenshots1. It lacked some things I wanted for this workflow, so I’ve been submitting them and discussing others.
Most (if not all) of those I could’ve just done on my end, but I haven’t for two main reasons: it’s actually better to just contribute to the main tool, making it not only more robust for this workflow but for everyone else that uses it in other capacities, and because I’d be working around it instead of with it, making my own code and maintenance that much harder.
⌘⇧3, which is something I considered before, would actually have been a bore to implement, in the previous iteration. However, with the refactoring I made recently to add resampling, it would actually be trivial to implement. The reason I haven’t done so is clarity. Though I build workflows to scratch my own itches (not always, as some were made by request, and others for proofs of concept or experiments to push Alfred’s limitations to their limits), I try to design them to be as clear and usable by others as possible2.
When you have a bunch of Alfred keywords, being clear with intent is easy. With hotkeys, not so much. It’s fine if you as a user have to look at the left side of workflows (keywords, script filters) to understand what does what, as those sections are built in a way that you can understand them by reading their non-code contents. However, If you’re forced to read the right side of workflows (a bunch of code blocks) and look at how things work, that is a worse experience (and may be terrifying if you don’t understand and are afraid you’ll mess up the code).
Hotkeys are weird in that regard. They are on the left side and activate other options, but there’s no way to understand what they do unless you look at the right side. For that reason, I try to make it so that if I have a hotkey connecting somewhere, I’ll have at least a keyword or script filter connecting there as well, something that gives you a clue. In this case, however, that wouldn’t make sense, as the whole point is to be able to do it fast with a hotkey. But I already have two hotkeys that you need to know, and adding support for ⌘⇧3 would add two more (two because of resampling), and I feel that will make it more complex in a way that isn’t worth it.
So I’ll add the option if there’s a demand for it, but likely3 won’t otherwise.
That’s probably way more context than expected, but I hope it makes sense as to why this works the way it does currently.

1 I used another app for months before actually working on this for release. That workflow was really rough in many areas (like detecting errors) but worked well enough, which is why is just let it linger on for my own needs before working on it for this release,
2 Which partially explains why some are unreleased, like the old version of this one. Others are unreleased either because they are so specific to my needs they would be of value to virtually nobody else, or because they’re so simple (but still useful) that even non-coders could easily recreate them.
3 Still thinking about it.


Updates CONTRIBUTING.md

Description
Adds a CONTRIBUTING.md file to make it easy for first-time visitors to contribute. I took inspiration from the CONTRIBUTING.md files from foundry and viem.
### Tasks
- [x] Add CONTRIBUTING.md -- this is for everyone (3rd-party contributors will need this)
- [x] Review README-DEV.md - deleted
- [x] Review RELEASE.md -- this is for internal use (3rd-party contributors won't need this)
- [x] Review SETUP.md -- deleted this file that was brough over from the monorepo (doesn't seem relevant anymore)

Other changes
Moves CONTRIBUTING.md file from the /.github directory to the top-level to make it easier for new contributors to find it. It will still be recognised by Github for various use cases.
Deleted README-DEV.md and SETUP.md, which are files that were brought over from the monorepo, and are now either out of date or not completely relevant. To avoid confusion, I removed these, but we can always complement the CONTRIBUTING.md file if needed.
Reviewed RELEASE.md, which is a file for internal use (i.e. 3rd-party contributors won't need this) that describes the release process. Fixed a couple typos to improve readability and reviewed the contents tie with our CONTRIBUTING.md.
Tested
N/A, only docs changes.
Related issues

https://github.com/celo-org/developer-tooling/issues/29

Backwards compatibility
N/A, only docs changes
Documentation
Yes, docs are updated with this PR.

I'll add a couple smaller edits to README


Use ES modules for Tailwind config

Decided to take a pass at this based on our conversation in Slack earlier—wound up being more straightforward than I thought it might 🙂
I think this should work pretty cleanly with both apps and addons, under the assumption that addons should probably specify a Tailwind prefix to avoid conflicts. The one exception is that Tailwind doesn't seem to provide an option not to include normalize.css, which means that we could potentially wind up with multiple copies of that floating around in the build.

Also, there were a few files in lib that didn't seem to be used for anything, but since I wasn't sure I just left them there.

Awesome! Dan you are the freakin man.
I was actually using ember-cli-tailwind/modules to generate the styleguide but I'm just going to separate each section into their own component, and import each module by itself. I'll push that commit onto here.

which I will also add tests for


[RFC] add substr_range and related methods

rendered
Related links:
APC
Pre-RFC - Contains very little discussion

Just letting you know since I'm not 100% sure if you understand how the ACP process works, but an ACP is sufficient for adding new APIs; you don't need to add an RFC. Generally, the order for libs changes is ACP (where feedback on how the API should look is ironed out), then an implementation in the standard library, then eventually it can be stabilised with an FCP if people are using the API and there aren't any additional concerns.
So, rather than closing the ACP, the next step that makes the most sense to me is to continue discussing this in the ACP, then submitting a PR to the rust repo with the implementation once the ACP is done.

Just letting you know since I'm not 100% sure if you understand how the ACP process works, but an ACP is sufficient for adding new APIs; you don't need to add an RFC. Generally, the order for libs changes is ACP (where feedback on how the API should look is ironed out), then an implementation in the standard library, then eventually it can be stabilised with an FCP if people are using the API and there aren't any additional concerns.
So, rather than closing the ACP, the next step that makes the most sense to me is to continue discussing this in the ACP, then submitting a PR to the rust repo with the implementation once the ACP is done.

I see. That makes sense.
I'm going to close this RFC then and reopen the ACP.
Thanks


💡[Feature]:  Image Art Generator using GANs

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
A deep convolutional generative adversarial network implemented in PyTorch! The project is designed to generate realistic images from random noise using the power of deep learning.
Use Case
This project illustrates the building of foundational GANs , one of the most powerful utilities of deep learning using Generator and Advisor networks. The training data for this project is obtained from the CIFAR-10 open dataset. This model can successfully generate human like art using the training it had went through.
Benefits
It utilizes the power of neural networks and uses two parallel , powerful networks to build image artworks that are appealing and realistic . It can further be scaled to build models like stable diffusion.
Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Please assign me this issue under GSSOC'24.


DNN handlers prevent incoming POST

DNN with 2 portals ID = 0 and 1
Add handler SSO.ashx for SSO implementation
Submit POST to SSO.ashx with URL for portal 0
In SSO.ashx Login user to portal id=1, assuming user belongs to portal 1. Then redirect to portal 1 URL,  Request returns .DOTNETNUKE cookie to browser
Close browser or not – not important
Submit another similar POST request to SSO.ashx with URL for portal 0
Problem: 2nd  POST request is not coming to  SSO.ashx because (likely) DNN handlers redirect with GET, and request GET coming to SSO.ashx.
This request clears .DOTNETNUKE cookie, so next 3rd POST will be successful and so on.
If POST submitted to portal 1, i.e. no portals switch, everything works properly

Have you tried adding SSO.ashx to any of the URL regex settings?  Or putting SSO.ashx inside a folder within DesktopModules?

Yes,
Location and URL based on … DesktopModules\SSO\Redirector.ashx
But copying to root folder makes no diffrerence
From: Brian Dukes<EMAIL_ADDRESS>Sent: Tuesday, December 18, 2018 12:57 PM
To: dnnsoftware/Dnn.Platform
Cc: Tarasyuk, Boris (Buck); Author
Subject: Re: [dnnsoftware/Dnn.Platform] DNN handlers prevent incoming POST (#2516)
Have you tried adding SSO.ashx to any of the URL regex settings? Or putting SSO.ashx inside a folder within DesktopModules?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/dnnsoftware/Dnn.Platform/issues/2516#issuecomment-448311429, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Ar2DAHoNv6AFIRcKbH9EpYqrVvgS6Sruks5u6SxSgaJpZM4ZYlkw.

If I am not mistaken, the authentication cookie is valid for the authenticated portal alias. I think the proper way for this use case is to setup portal groups and then you get a single authentication domain for multiple portals. Unfortunately, there is currently no UI to manage portal groups. @SCullman has built such a module and it works in Dnn 9 too (although not integrated in the persona bar) I have that module working fine on an old site upgraded to 9.3.2. There is also an old forum post about this at https://www.dnnsoftware.com/forums/threadid/536762/scope/posts/sso-using-site-group-editor I am closing this issue and recommend discussing this special case in the new forums https://dnncommunity.org/forums if discussions end up to being a bug in the platform please open a new issue with very clear steps and/or code sample to reproduce.


Scrapers: inconsistance in competition mapping in common.py

The competition mapping for "BEL First Division A" and "BEL First Division B"  are mapped to Germany.
In football-data there isn't a league file for the second division but only for Jupiler
below the code block:
COMPETITION_MAPPINGS = {
"BEL First Division A": {
"fbref": {
"slug": "37",
"stats": [
"standard",
"goalkeeping",
"shooting",
"playing_time",
"misc",
],
},
"footballdata": {"slug": "D2"},
"espn": {"slug": "ger.2"},
},
"BEL First Division B": {
"fbref": {
"slug": "69",
"stats": [
"standard",
"goalkeeping",
"playing_time",
"misc",
],
},
"footballdata": {"slug": "D2"},
"espn": {"slug": "ger.2"},
should be sufficient correct "footballdata": {"slug": "D2"}, to  "footballdata": {"slug": "B1"},
and remove the  part regarding  "BEL First Division B"
thank you for your very usefull project
Regards
Ale

Thanks for bug report, I’ll get that fixed and included in the next release

Should be fixed now in v0.8.0


Edit README

Some of the markdown comments haven't been done properly. There is a random UPDATE on line 14.
Also there is a whitecheck_mark which has not been implemented properly above the hacktoberfest stats link.

Hi, I would like to try on this.

:))))


Update Aqara_ZNSMBL11LM

@blakadder, it looks like you are not accepting this PR because of the proposed change to the sensor name 🙂
I changed the name because this is how the sensor is presented in the Aqara Home app:


feat(docs): elaborate Popover vs ToolTip

Overview

Elaborates on when to use Popover vs ToolTip in the Storybook docs.

PR Checklist

[ ] Related to designs:
[ ] Related to JIRA ticket: ABC-123
[x] I have run this code to verify it works
[x] This PR includes unit tests for the code change

📬Published Alpha Packages<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://61439fc94118f81175f8e759--gamut-preview.netlify.appDeploy Logs


Code formatting not functional after upgrade to Windows 10 1809

All forms of code formatting seem to be non-functional after upgrading to Windows 10 1809. I've managed to reproduce this error across two PCs and both stable and Insider builds, along with a clean reinstall of both versions (including deleting extensions and user data)

VSCode Version: 1.27.2 (user setup), 1.28.0-insider (user setup)
OS Version: Windows 10 17763.1

Steps to Reproduce:

Update Windows 10 to October 2018 (1809) update
Install relevant language extension to VS Code and optionally set up automatic formatting
Open or create new file (and assign it to a specific language)
Create obvious formatting error (e.g. excessive indentation)
Try to trigger formatting via keyboard shortcut or an automatic method (e.g. when saving)

Launching without extensions does not affect this error as the function relies on official extensions to provide the formatting.

Image shows an error stating that the document formatter is missing when it is installed and active, this error only appears on files that have not been previously saved. Nothing appears if it is a previously saved file, it just does not function. This appears to be happening regardless of language rather than specifically the C/C++ plugin

@CallumRaabe based on what you described, it looks like a C++ extension issue, please file issues there first.

I seem to have encountered a similar issue except in this code no longer opens at all.
When I open the program the cursor turns to the loading cursor and then.......
Nothing.
No white or black screen nothing.
So I decided to check the task manager and as I feared, when I double click vs code it appears for a second before disappearing.
It seems it definitely had something to do with the c++ extension because I remember Tinkering with it yesterday. However I don't know for sure if the windows 1809 has anything to do with but I installed it a few days ago so it definitely is suspect plus you factor in the news about it.
Am afraid I might have to Uninstall vs code but I'm definitely avoiding that for now, as I don't have a network connection to reinstall all my plugins..😧😧

I mentioned in my original post it didn't seem to be isolated to just the C/C++ extension, the same error occurs with C# and Java files (both brand new files and tests with my previous work) with their respective extensions installed from my testing on both my affected PCs, and the 'missing formatter' error appears to be appearing on existing files now (tested with C, C# and Java files)


installation

Encountered error while trying to install package
-> pycrypto
Has anyone else had issues like this? Did some research and getting mixed answers

yea i got the same error of pycrypto

install pycryptodome package


Added special introducer

New community manager added.
Ruca: 0x2d165e5191ef0674da2637b421a765bdb1f8d346
substrate.io: 0xa451fd5fcc0d389e0c27ff22845c0e17153f7dc8

Thank you guys :)


After Installtion module not working

Hello,
I installed module but after install i get error "Fatal error: Class 'Magento\Framework\DataObject' not found" in Sample\News\Controller\Router.php on line 115

This module is not yet compatible with the latest Magento 2 version. I'll do my best to make it compatible again.

ok thanks for your reply :)

@purvi123 Try again now. It should work.

@purvi123 It should work now.


Upload Error: px_uploader.py: No such file or directory

Here is the error message:
$ make intel_aerofc-v1_default upload
ninja: Entering directory `/cygdrive/c/PX4/home/Firmware/build/intel_aerofc-v1_default'
[3/4] uploading px4
Copying files to Aero board (root@<IP_ADDRESS>)...
The authenticity of host '<IP_ADDRESS> (<IP_ADDRESS>)' can't be established.
ECDSA key fingerprint is SHA256:xMmdPK4036rjoNP2mFfKF5j3KhO4QF8An2QnfAUY9s4.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '<IP_ADDRESS>' (ECDSA) to the list of known hosts.
<EMAIL_ADDRESS>password:
intel_aerofc-v1_default.elf                                                           100%   13MB  20.6MB/s   00:00
/cygdrive/c/PX4/home/Firmware/boards/intel/aerofc-v1/scripts/px_uploader.py: No such file or directory
FAILED: boards/intel/aerofc-v1/CMakeFiles/upload
cd /cygdrive/c/PX4/home/Firmware/build/intel_aerofc-v1_default/boards/intel/aerofc-v1 && /cygdrive/c/PX4/home/Firmware/boards/intel/aerofc-v1/scripts/aero_upload.sh /cygdrive/c/PX4/home/Firmware/build/intel_aerofc-v1_default/intel_aerofc-v1_default.elf
ninja: build stopped: subcommand failed.
make: *** [Makefile:171: intel_aerofc-v1_default] Error 1
I have tried several times on different computer, same issue.

Looks like a regression after the board restructure.

The boards are able to provide their own custom upload now. https://github.com/PX4/Firmware/blob/master/boards/intel/aerofc-v1/CMakeLists.txt
I can review this on an aero this weekend.

Looks like the aero upload script needs to know the path to px_uploader.py under Tools/ and not under the boards scripts directory.
https://github.com/PX4/Firmware/blob/master/boards/intel/aerofc-v1/scripts/aero_upload.sh#L43

@dagar Thanks, let me try the new script. Should I re-clone and re-make it?

I moved the py file to that folder, and now I have this issus:
/dev/ttyS1:
Updating firmware on AeroFC
Traceback (most recent call last):
File "/root/px_uploader.py", line 880, in
main()
File "/root/px_uploader.py", line 736, in main
fw = firmware(args.firmware)
File "/root/px_uploader.py", line 122, in init
self.desc = json.load(f)
File "/usr/lib/python2.7/json/init.py", line 291, in load
**kw)
File "/usr/lib/python2.7/json/init.py", line 339, in loads
return _default_decoder.decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 364, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.7/json/decoder.py", line 382, in raw_decode
Firmware updated
Restarting router
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
Finished.

I have the same issue with the "ValueError: No JSON object could be decoded" Any progress here?

I figured it out. In my case, I was trying to flash the ".elf" file when it should have been the ".px4" file from the make command.
Hope that helps others!

Hi @trexgerratt How did you managed to select the ".px4" binary instead of the ".elf"?

I think this has been resolved in latest master, right?

I just cloned master and tried uploading it to my Intel drone and I've been having the exact same issue as @trexgerratt had. So far I haven't found a fix, but I'll try specifying the .px4 file for px_uploader.py

@skamano can you check #11075?


sqlite3.OperationalError: unable to open database file

I'm using this component in my HomeAssistant installation and when it's configured it throws this exception:
2017-12-04 11:42:21 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up platform coinmarketcap
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/homeassistant/helpers/entity_component.py", line 171, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT, loop=self.hass.loop)
  File "/usr/lib/python3.6/asyncio/tasks.py", line 358, in wait_for
    return fut.result()
  File "/usr/lib/python3.6/asyncio/futures.py", line 245, in result
    raise self._exception
  File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.6/dist-packages/homeassistant/components/sensor/coinmarketcap.py", line 55, in setup_platform
    CoinMarketCapData(currency, display_currency).update()
  File "/usr/local/lib/python3.6/dist-packages/homeassistant/components/sensor/coinmarketcap.py", line 133, in update
    convert=self.display_currency)
  File "/usr/local/lib/python3.6/dist-packages/coinmarketcap/core.py", line 54, in ticker
    response = self.__request('ticker/' + currency, params)
  File "/usr/local/lib/python3.6/dist-packages/coinmarketcap/core.py", line 28, in __request
    response_object = self.session.get(self.base_url + endpoint, params = params, timeout = self.request_timeout)
  File "/usr/local/lib/python3.6/dist-packages/coinmarketcap/core.py", line 21, in session
    self._session = requests_cache.core.CachedSession(cache_name='coinmarketcap_cache', backend='sqlite', expire_after=120)
  File "/usr/local/lib/python3.6/dist-packages/requests_cache/core.py", line 68, in __init__
    self.cache = backends.create_backend(backend, cache_name, backend_options)
  File "/usr/local/lib/python3.6/dist-packages/requests_cache/backends/__init__.py", line 50, in create_backend
    return registry[backend_name](cache_name, **options)
  File "/usr/local/lib/python3.6/dist-packages/requests_cache/backends/sqlite.py", line 28, in __init__
    self.responses = DbPickleDict(location + extension, 'responses', fast_save=fast_save)
  File "/usr/local/lib/python3.6/dist-packages/requests_cache/backends/storage/dbdict.py", line 58, in __init__
    with self.connection() as con:
  File "/usr/lib/python3.6/contextlib.py", line 81, in __enter__
    return next(self.gen)
  File "/usr/local/lib/python3.6/dist-packages/requests_cache/backends/storage/dbdict.py", line 70, in connection
    con = sqlite.connect(self.filename)
sqlite3.OperationalError: unable to open database file

A few other users are experiencing the same issue here: https://github.com/home-assistant/home-assistant/issues/9907

Hello,
thanks for reporting this, I had no idea the home-assistant project was using this library. Unfortunately there's nothing I can do as the error seems to come from the home-assistant codebase.
I'll keep an eye out and if nobody fixes this I'll try and come up with a PR downstream.
Cheers.

Hi, I am having the same issue without using home-assistant.
I just followed this example: http://blockxchain.org/2017/05/29/importing-altcoin-data-with-python-and-the-coinmarketcap-api/
Thanks!

Hello @franlab,
can you share the exact code you're using (either on Pastebin or in a gist) so I can have a closer look. I've not been able to reproduce this error so far.
Cheers.

Hello @mrsmn thanks for the response.
This is my code:
https://pastebin.com/EMg73zu8
and here is the code I am using to run the api within a llinux daemon: https://pastebin.com/9xA6hFbr which I borrowed from: http://web.archive.org/web/20131017130434/http://www.jejik.com/articles/2007/02/a_simple_unix_linux_daemon_in_python/

Hey @franlab,
thanks for sharing, I'll look into the issue over the weekend. I have an idea where the error might come from, I'll need to do some testing.
Cheers.

Hello again,
so I was able to get a look at the code @franlab posted: the codebase looks sane but keeps on complaining that it can't open the DB file. Adding a manual path (for example /home/<user>/coinmarketcap) to the class instanciation doesn't seem to cut it.
If I had to take a guess I'd say it's the voodoo-black-magic forking of the daemon class that's at fault but I'll have to pdbit to be sure.

@mrsmn I see that you have been using request_cache but the path for sqlite  db cache is / (not correct) when Python is running under wsgi daemon processes, it would be nice to set that location from this library as well. Example on how it is being done in Django: https://github.com/allianceauth/allianceauth/issues/224#issuecomment-177646284. This would solve permission issues.

Thanks @themightydeity, I'll look into it over the weekend. 👍

It might not be a full solution, but changing the backend to memory on this line solves the problem for me.
Leaving it off will have it use sqlite if it's available, and fallback to memory if it's not (according to the docs) so that might be an option as well.


iOS build fails on MacOS

Describe the bug
The Ios app fails to run with the following error message:
/AvaloniaPerformanceTest/avaloniax.iOS/AppDelegate.cs(13,6): error CS0012: The type 'UIResponder' is defined in an assembly that is not referenced. You must add a reference to assembly 'Xamarin.iOS, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=84e04ff9cfb79065'. [/AvaloniaPerformanceTest/avaloniax.iOS/avaloniax.iOS.csproj]

To Reproduce
I just created a new Avalonia app from CLI.
It can be reproduced with the following repository: https://github.com/byme8/AvaloniaPerformanceTest

Run command in avaloniax.iOS folder: dotnet run

Expected behavior
The app launched in the simulator

OS: Mac 12.4
Version 0.10.999-cibuild0019213-beta
Dotnet 6.0.302

See https://github.com/AvaloniaUI/avalonia-dotnet-templates/issues/94#issuecomment-1157100714
You need to use latest possible SDK and latest possible avalonia nightly to keep in compatible.


chore: mention automatic config setup with Gradle

We can add note that haul init will do it for you and leave those notes there as well

Should be better now

Looks good 👍


expose env_vars argument from start_kong

Summary
We're starting up kong for integration tests for our custom plugins using the start_kong method implemented in spec/helpers.lua. We need to be able to set environment variables as our plugin is using some custom environment variables. Currently the only way through the start_kong method to set env vars is to prefix them with KONG_. I noticed that kong_exec, which start_kong calls has an env_vars option that would work perfectly for us. I would like for that argument to also be available from start_kong.

use helpers.setenv(name, value) and helpers.unsetenv(name)

also, try:
git clone https://github.com/kong/kong.git
cd kong/spec
ldoc .
open docs/index.html

(does need ldoc to be installed)

After thinking about this a second time, I think @Tieske's proposal is good enough. It is more verbose than a tailor-made parameter in start_kong; but verboseness isn't always undesirable on tests. I will close this issue. @nathanloyer please reopen if this is not satisfying enough.


Enable option to add/display new namespaces in selected project by default

Rancher versions:
rancher/rancher 2

Can you describe the steps you take and what happens and what you expect to happen so we can use that to determine how to handle/fix this?

If namespaces are created externally (kubectl) they are not added to any of the projects. Is it possible to define default project for new namespaces?

Merging into https://github.com/rancher/rancher/issues/15820


Not working!

@iSaulX I've tried the same. But, this approach doesn't seem to work

Hi! This extensions only work with this type of PopUp

This happen before you get restricted to play videos. I keep working to found  a way to avoid this.
Tip: (If you have another google account. switch, play one video and then come back to your original account) :P


⚠ ClamAV has degraded performance

In 99f3bca, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 215 ms

Resolved: ClamAV performance has improved in fd8d4d0.


Add test coverage and package publication to build

Also update build version to 1.0.1-SNAPSHOT to avoid clashing with 1.0.0 release in Maven central.

Code Climate test coverage now working with latest change to Travis file.


RuntimeError: CUDA error: CUBLAS_STATUS_ALLOC_FAILED when calling cublasCreate(handle)

Hello!
I forked your Repo on an AWS g4dn machine and tried to train it using model - roberta-large for the SST2 classification task. It gave me a CUDA error. I tried reducing the batch size from 8-4 as well and it still didn't work. Any suggestions on how to run it ?

Hi, could you list the detailed information, like torch & cuda version and device information here?
BTW, it might help if you try run on CPU first to identify the problem; would you like to test it by setting use_gpu to no in your config file?

Hello!
I forked your Repo on an AWS g4dn machine and tried to train it using model - roberta-large for the SST2 classification task. It gave me a CUDA error. I tried reducing the batch size from 8-4 as well and it still didn't work. Any suggestions on how to run it ?

Hello , I met the same problem when I used the roberta model.  By the way, it would not raise this error when use bert model. So how did you solve this problem? Thanks very much!

Would you provide more details, like the traceback information? BTW for the error you might refer to this link:https://stackoverflow.com/questions/61473330/cuda-error-cublas-status-alloc-failed-when-calling-cublascreatehandle
It seems the error is about model's output dimension (and for bert and roberta the dimensions might be different). As I mentioned you can debug using CUDA_LAUNCH_BLOCKING=1 or set use_gpu as no in the config to debug on cpu, which helps you in locating the issue.

Would you provide more details, like the traceback information? BTW for the error you might refer to this link:https://stackoverflow.com/questions/61473330/cuda-error-cublas-status-alloc-failed-when-calling-cublascreatehandle
It seems the error is about model's output dimension (and for bert and roberta the dimensions might be different). As I mentioned you can debug using CUDA_LAUNCH_BLOCKING=1 or set use_gpu as no in the config to debug on cpu, which helps you in locating the issue.

Well , this is the traceback information:

Would you provide more details, like the traceback information? BTW for the error you might refer to this link:https://stackoverflow.com/questions/61473330/cuda-error-cublas-status-alloc-failed-when-calling-cublascreatehandle
It seems the error is about model's output dimension (and for bert and roberta the dimensions might be different). As I mentioned you can debug using CUDA_LAUNCH_BLOCKING=1 or set use_gpu as no in the config to debug on cpu, which helps you in locating the issue.

Well , this is the traceback information:

Thanks. ALBERT/BERT was used in our experiment. I'll look into this later with RoBERTa model.


Wrong XPATH for Workday Azure Integration

Hey, it seems that for the new API v30+ there is an error on #21 - FacilityLocation
current state: wd:Worker/wd:Worker_Data/wd:Organization_Data/wd:Worker_Organization_Data[translate(string(wd:Organization_Data/wd:Organization_Type_Reference/wd:ID[@wd:type='Organization_Type_ID']),'abcdefghijklmnopqrstuvwxyz','ABCDEFGHIJKLMNOPQRSTUVWXYZ')='FACILITY']/wd:Organization_Reference/@wd:Descriptor 0
the 0 at the end seems to be an issue, as Azure gives out an error upon saving the config changes.
And the 0 at the end is the only thing changing in this specific XPATH which leads me to believe it is an error (also, without this 0 everything is working fine for me)

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

ID: 27710bf3-6226-4d04-cd85-3bdd1fb44d3d
Version Independent ID: b1ef7b4e-b539-4ff3-4c25-454d7e8c6836
Content: Workday attribute reference
Content Source: articles/active-directory/app-provisioning/workday-attribute-reference.md
Service: active-directory
Sub-service: app-provisioning
GitHub Login: @kenwith
Microsoft Alias: kenwith

@jochot
Thanks for your feedback! We will investigate and update as appropriate.

Thanks! I made a pull request to remove that. https://github.com/MicrosoftDocs/azure-docs-pr/pull/128438


Add gas limit override option for contract deployments

I've had some deployment failures due to running out of gas on deployment when a constructor is invoked. In some cases the intrinsic gas limit is off by a factor of 10. This change allows the developer to override the calculated model if necessary, without breaking the API.

Codecov Report

Merging #128 (683f6a8) into main (19e7c20) will decrease coverage by 0.05%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##             main     #128      +/-   ##
==========================================
- Coverage   99.74%   99.68%   -0.06%
==========================================
  Files          67       67
  Lines        3855     3857       +2
==========================================
  Hits         3845     3845
- Misses         10       12       +2

Impacted Files
Coverage Δ

lib/eth/client.rb
99.35% <66.66%> (-0.65%)
:arrow_down:

lib/eth/client/ipc.rb
93.33% <0.00%> (-6.67%)
:arrow_down:

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


feat: enable preferring attributions in attribution view

Summary of changes
In this PR we enable preferring attributions in the attribution view. If an attribution has multiple resources, a warning is shown and the user is asked for confirmation.
This PR also fixes a bug in the previous implementation of preferring globally. The originIds, that an attribution is preferred over, weren't computed for all resources of the attribution. Instead, only the resource that was selected when the attribution was preferred globally, was taken into account.
Context and reason for change
In #2270 preferring attributions globally was enabled. Consequently, it should be possible to prefer attributions in attribution view as well.
How can the changes be tested
added two e2e tests
and unit test that checks if the correct origin ids are computed if an attribution is attached to multiple resources

Two requests:
1. Could we split this PR into two parts? First part just fixing the bug you're describing. Second part enabling preferring attributions in attribution view.

2. Could you please create a separate GitHub issue exactly describing the bug you're fixing and also how to reproduce it. Right now, I'm not sure how I can even test that the bug was really fixed.

Sure! I only discovered the bug while I was working on this ticket. But it should be possible to sort things out.
Created #2370. This is not a bug that is visible in the front end. The data stored in the backend is just incomplete. Nothing fails. And the data is not used to display anything. So, I am not sure how to test this either. Also wanted to ask you about that...


ngx-datatable-column and non camelCase JSON property

I'm submitting a ...  (check one with "x")
[x ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, post on Stackoverflow or Gitter

Current behavior
If we use a ngx-datatable-column to specify definition of columns (and take actions accordingly, such as display a column based on a property), then values from ngx-datatable-cell-template need to be camelCase. I couldn't find a way to have values bound to prop
Expected behavior
I would expect that the JSON model can be non camelCase, in the stackblitz commentNONCAMEL values should appear as well
Reproduction of the problem
I created a reproduction here:
https://stackblitz.com/edit/angular-3fjfsb
Values coming from the non camel-case property is not fetched (or I couldn't find a documented way/example)
What is the motivation / use case for changing the behavior?
Business case where I need to use ngx-datatable-column to display certain columns, and where response from the backend does contain properties which are non camelCase (to be specific, "commentCRO")
Please tell us about your environment:
Windows 10,

Table version:
ngx-datatable 13.1.0

Angular version:
Angular 5 (but stackblitz example  is running on 6),

Browser:
All

Language: [all | TypeScript X.X | ES6/7 | ES5]
All

Having the same issue

Was this ever fixed, this is such a silly problem and has consummed of a lot of time from devs trying to debug.

It is not actually a bug, you just use it incorrectly. We had exactly the same problem.
The answer sits here: https://github.com/swimlane/ngx-datatable/blob/5eed8493fa016bcbf49f7fe7d9bc39e41916a4e7/docs/api/column/inputs.md?plain=1#L9
The column model has a name property and prop property. prop is used to get the value to display. name has a different purpose. But if you do not specify prop, the libs tries to do you a favour and figure it out from the name property by camel casing it.
See here: https://github.com/swimlane/ngx-datatable/blob/5eed8493fa016bcbf49f7fe7d9bc39e41916a4e7/projects/swimlane/ngx-datatable/src/lib/utils/column-helper.ts#L25
So instead of setting the name for the column, you should set prop. Your blitz can be fixed easily by changing this line:
 <ngx-datatable-column name="{{col.prop}}" *ngIf="col.display"
to this:
 <ngx-datatable-column prop="{{col.prop}}" *ngIf="col.display"
in your app.component.html file.


weird font thing

https://waddle.succ.world/i/vvoh.png
its like i dunno showing a weird font thing thats unreadable how do i fix it

Change language, type lang en-US and press Enter key.


Error 429: Too many requests

Receiving this error as soon as I search postal code (so after you click on a campaign, and search for a postal code). This means that nothing is loading as it times me out from the api as seen in the screenshot below.

I think the issue is the following code as it keeps sending requests to API which then makes it time out (I could be wrong). We also need to update this to send the whole member object, not just the name.
        async handleRepClick (member) {
            try{
                this.repName = `Dear ${member.name}`;
                this.shouldRender = false;
                //from campaign id find template id and then make get request with template id
                var campaignId =this.$route.params.campaignId;

                const versions = await axios.get(
                    'https://murmuring-headland-63935.herokuapp.com/api/Letter_Versions/'+ campaignId
                    );

                let latestVersion = versions.data[versions.data.length - 1].template_id;

                const letter = await axios.get(
                    'https://murmuring-headland-63935.herokuapp.com/api/lob/templates/' + latestVersion
                    );
                this.letterBody = letter.data.versions[0].html;
                this.isStep2 = true;

            } catch(e){
                console.error(e);
            }

        },

@mahrsbar I have updated the rate limit for now which should allow you to proceed with dev work. But, looks like we are making a lot of calls for each rep even before on click.


[System.Buffers.Helpers] Add new library

Description

Adding a new library System.Buffers.Helpers with an IBitConverter interface and both Big and Little Endian implementations

Motivation and Context

Provides an IBitConverter so data can be converted from and to byte[] in Big or Little Endian manner.
Comes in utile when received data is encoded in another Endian way.
Usage will be in:
-- MulticastDNS: networking data is (should be) Big Endian
-- Protobuf might receive data encoded in either Big or Little Endian

How Has This Been Tested?

Unit tests have been provided
Screenshots
Types of changes

[ ] Improvement (non-breaking change that improves a feature, code or algorithm)
[ ] Bug fix (non-breaking change which fixes an issue with code or algorithm)
[x] New feature (non-breaking change which adds functionality to code)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Config and build (change in the configuration and build system, has no impact on code or features)
[ ] Dependencies (update dependencies and changes associated, has no impact on code or features)
[x] Unit Tests (add new Unit Test(s) or improved existing one(s), has no impact on code or features)
[ ] Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

[x] My code follows the code style of this project (only if there are changes in source code).
[ ] My changes require an update to the documentation (there are changes that require the docs website to be updated).
[ ] I have updated the documentation accordingly (the changes require an update on the docs in this repo).
[x] I have read the CONTRIBUTING document.
[x] I have tested everything locally and all new and existing tests passed (only if there are changes in source code).
[x] I have added new tests to cover my changes.

Summary by CodeRabbit

New Features

Introduced a new category labeled "system" for better organization within the project.
Added a versioning file to manage project releases and dependencies.

Chores

Created a new packages.lock.json file to specify project dependencies and their versions.

@josesimoes are we ready to merge? :-)