feat: add overflow visible to modal

CAR-6445 - Date selection dropdown is cut off and makes the modal scrollable

Before

After

Test

Go to https://car6445.carforyou-dealerhub-web.branch.carforyou.ch/it/listings/type/lookup
Start listing process
Select make/model
Click weiter to open modal
In the modal open the month dropdown

I changed the initial implementation


@pika/plugin-bundle-node: does nothing, because the !isFull

Any more insight what that isFull param is on the build({ isFull }) is?
When comment it out, everything works and there is final dist-node/index.bundled.js

Oh wow, yea that's old. I don't think any other plugins still listen to that option. It was meant to be a flag to switch between a quick "dev" build and a larger "full" build for production. You can turn it on by running npx @pika/pack --publish, but really it should be removed in favor of some sort of named pipeline solution thats been discussed in other issues.

Removed here: https://github.com/pikapkg/builders/commit/df673312d40243e5bb00c6fd72a5696613575363


[Request] Improve cluster description

Embbed distance matrix for mainand sub clusters in dedicated JSON field.
Add tree calculation and embbed tree in a dedicated JSON field.
Add a global cluster which describes therelationship and distances between main clusters.

For conveniencethe distance matrix will be encoded as a JSON record entry, which does not preserve indices. Since it is a matrix, preserving col names only is enough.
"distances": [
    {
        "id1": "0",
        "id2":  "10"
    },
    {
        "id1": "10",
        "id2": "0"
    }
]

Trees will be left to a reporting module.
Reason for this is that it tend to bloat the JSON records (and database) with information that is already embedded in the distance matrix.


Requires latest libstdcxx-ng

Solution to issue cannot be found in the documentation.

[X] I checked the documentation.

Issue
In my existing matplotlib environment, I installed contourpy from conda-forge, but it failed to import due to missing C++ symbols. In a clean environment, it works fine, but I can replicate the failure by installing older libstdcxx-ng:
$ conda create -n cp python=3.8 contourpy libstdcxx-ng==11.2.0
$ conda activate cp
(cp) $ python -c 'import contourpy'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/root/.conda/envs/cp/lib/python3.8/site-packages/contourpy/__init__.py", line 4, in <module>
    from ._contourpy import (
ImportError: /root/.conda/envs/cp/lib/python3.8/site-packages/contourpy/../../../libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /root/.conda/envs/cp/lib/python3.8/site-packages/contourpy/_contourpy.cpython-38-x86_64-linux-gnu.so)

So contourpy should either be built against the oldest possibly libstdcxx-ng, or should require a minimum version in the package metadata.
Installed packages
# packages in environment at /root/.conda/envs/cp:
#
# Name                    Version                   Build  Channel
_libgcc_mutex             0.1                 conda_forge    conda-forge
_openmp_mutex             4.5                       2_gnu    conda-forge
bzip2                     1.0.8                h7f98852_4    conda-forge
ca-certificates           2<IP_ADDRESS>          ha878542_0    conda-forge
contourpy                 1.0.2            py38h43d8883_2    conda-forge
ld_impl_linux-64          2.36.1               hea4e1c9_2    conda-forge
libblas                   3.9.0           14_linux64_openblas    conda-forge
libcblas                  3.9.0           14_linux64_openblas    conda-forge
libffi                    3.4.2                h7f98852_5    conda-forge
libgcc-ng                 12.1.0              h8d9b700_16    conda-forge
libgfortran-ng            12.1.0              h69a702a_16    conda-forge
libgfortran5              12.1.0              hdcd56e2_16    conda-forge
libgomp                   12.1.0              h8d9b700_16    conda-forge
liblapack                 3.9.0           14_linux64_openblas    conda-forge
libnsl                    2.0.0                h7f98852_0    conda-forge
libopenblas               0.3.20          pthreads_h78a6416_0    conda-forge
libstdcxx-ng              11.2.0               h1234567_0
libuuid                   2.32.1            h7f98852_1000    conda-forge
libzlib                   1.2.11            h166bdaf_1014    conda-forge
ncurses                   6.3                  h27087fc_1    conda-forge
numpy                     1.22.3           py38h99721a1_2    conda-forge
openssl                   3.0.3                h166bdaf_0    conda-forge
pip                       22.1.1             pyhd8ed1ab_0    conda-forge
python                    3.8.13          ha86cf86_0_cpython    conda-forge
python_abi                3.8                      2_cp38    conda-forge
readline                  8.1                  h46c0cb4_0    conda-forge
setuptools                62.3.2           py38h578d9bd_0    conda-forge
sqlite                    3.38.5               h4ff8645_0    conda-forge
tk                        8.6.12               h27826a3_0    conda-forge
wheel                     0.37.1             pyhd8ed1ab_0    conda-forge
xz                        5.2.5                h516909a_1    conda-forge
zlib                      1.2.11            h166bdaf_1014    conda-forge

Environment info
active environment : cp
    active env location : /root/.conda/envs/cp
            shell level : 2
       user config file : /root/.condarc
 populated config files : /usr/share/conda/condarc.d/defaults.yaml
                          /root/.condarc
          conda version : 4.11.0
    conda-build version : not installed
         python version : 3.10.0.final.0
       virtual packages : __linux=5.17.7=0
                          __glibc=2.34=0
                          __unix=0=0
                          __archspec=1=x86_64
       base environment : /usr  (read only)
      conda av data dir : /usr/etc/conda
  conda av metadata url : None
           channel URLs : https://conda.anaconda.org/conda-forge/linux-64
                          https://conda.anaconda.org/conda-forge/noarch
                          https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /var/cache/conda/pkgs
                          /root/.conda/pkgs
       envs directories : /root/.conda/envs
                          /usr/envs
               platform : linux-64
             user-agent : conda/4.11.0 requests/2.27.1 CPython/3.10.0 Linux/5.17.7-200.fc35.x86_64 fedora/35 glibc/2.34
                UID:GID : 0:0
             netrc file : None
           offline mode : False

@QuLogic If I look at the metadata of the contourpy package that you installed:
$ conda search -i "contourpy[channel=conda-forge]==1.0.2" | grep "contourpy 1.0.2 py38h43d8883_2" -A 18
contourpy 1.0.2 py38h43d8883_2
------------------------------
file name   : contourpy-1.0.2-py38h43d8883_2.tar.bz2
name        : contourpy
version     : 1.0.2
build       : py38h43d8883_2
build number: 2
size        : 224 KB
license     : BSD-3-Clause
subdir      : linux-64
url         : https://conda.anaconda.org/conda-forge/linux-64/contourpy-1.0.2-py38h43d8883_2.tar.bz2
md5         : b28aa61bda641e608bf89518f60d015f
timestamp   : 2022-05-19 10:04:08 UTC
dependencies:
  - libgcc-ng >=10.3.0
  - libstdcxx-ng >=10.3.0
  - numpy >=1.16
  - python >=3.8,<3.9.0a0
  - python_abi 3.8.* *_cp38

it shows that there is already a minimum version requirement on libstdcxx-ng. Your reproducer is using a later version than this minimum requirement, which should be fine but isn't, but this is a different problem. Or am I missing something here?

Closing due to lack of response.


masthead logo alt attribute

Can we have the masthead logo alt attribute populated with the "site.title" ?

Good idea. I'll take a look.

On line 8 of _includes/masthead.html, this should work:
-
+

commit and push! ;-)

Adding the site title as alternate text for the logo is overkill and unnecessary. Right after the logo the site title appears, so for screen readers they're going to see it twice.
Alternate text should be used to describe the image. In this case it's not adding any additional context and is simply "decoration", which is why it's omitted.

This remains an issue with automated accessibility tests, i.e., Lighthouse: https://web.dev/link-name/?utm_source=lighthouse&utm_medium=cli
I could add an exception to my assertions config that skip that failing test, but I can't as I need to ensure I catch other instances of this accessibility issue throughout my site.
I agree with you point about duplicate text for screen readers. Would it therefore be possible to allow us to define our own alt text for the Masthead logo in _config.yml, thus avoiding duplication of site title name? Something like "Company logo" or "Photo of xxx".


Ping ICMPv6

i tried several ipv6 addresses, which are all ping-able via desktop, receiving errors with ping tool. Does anyone share the same issue?
I can provide screen shots of mobile app:

with the desktop result(within the same network):
ping 201:6b27:e4b8:de94:228c:d7f3:a313:a1e2

PING 201:6b27:e4b8:de94:228c:d7f3:a313:a1e2(201:6b27:e4b8:de94:228c:d7f3:a313:a1e2) 56 data bytes
64 bytes from 201:6b27:e4b8:de94:228c:d7f3:a313:a1e2: icmp_seq=2 ttl=64 time=1162 ms
64 bytes from 201:6b27:e4b8:de94:228c:d7f3:a313:a1e2: icmp_seq=3 ttl=64 time=494 ms

Originally posted by @immartian in https://github.com/isontheline/pro.webssh.net/discussions/673#discussioncomment-3083663

Hello @immartian 👋
A fix should be available tomorrow.

fantastic, look forward

@immartian Please find a fix on the latest beta release here :

it works like a charm. Thanks for the crafting.

Thank you so much @immartian for your feedback 🙏


[AutoComplete] innerDivStyle not being passed down to MenuItem children

Description
Looking at this line in the AutoComplete code, it reads as though not all props are being passed down from AutoComplete at the highest level to its lower-level children. Specifically, one cannot pass in a prop for innerDivStyle to, for example, try to change the font size inside of the MenuItem(s) in the Menu in the AutoComplete.
Images & references

Recommended Solution
From looking at the code, it seems as though the styles for those MenuItem(s) should be combining the innerDivStyle prop, if passed in by the user, with styles.innerDiv.
I've been using the library for awhile (huge thank you for supporting it so thoroughly!), but that doesn't mean I haven't missed something. I have checked the GH issues, SO, and other resources and haven't found anyone dealing with this specifically yet. If this is already supported, would be great to know what the usage is. Specific use case:
Using an AutoComplete, but want to change the font-size of the MenuItems in the popover menu that comes with AutoComplete.
Thanks!
Versions

Material-UI: 15.4.0 (but pretty sure this is present in most recent 16.0
React: 15.3.2
Browser: Chrome

I was about to make a PR for this issue, but I just found out how to proceed: you must use the menuProps prop to pass down props to the <Menu> component, in this case menuItemStyle. Example:
<AutoComplete menuProps={{menuItemStyle: {color: 'red'}}}>

@antoinerousseau Thanks!

Thanks @antoinerousseau!! That was not immediately obvious, but very glad the usage is simple! Many thanks!

@marcacyr @antoinerousseau i'm getting Unknown prop innerDivStyle on  tag when i do something like --
<AutoComplete
 style={styles.filterSearch}
 inputStyle={styles.filterSearchText}
 menuProps={{innerDivStyle: {wordWrap: 'break-word',whiteSpace: 'initial',}}}
 dataSource={questions.questions
 ? questions.questions.map((q,i) => {
    return {
       value: <MenuItem value={q.id} key={i} primaryText={q.name}/>,
       text: q.name
    };
  })
 : []}/>

@nsuthar0914
<AutoComplete  style={styles.filterSearch}  inputStyle={styles.filterSearchText}  dataSource={questions.questions  ? questions.questions.map((q,i) => {     return {        value: <MenuItem style={ {wordWrap: 'break-word',whiteSpace: 'initial'}} value={q.id} key={i} primaryText={q.name}/>,        text: q.name     };   })  : []}/>

I've come across this issue now in several use cases and was wondering if it would be possible to expose the innerDivStyle from the AutoComplete menuProps, specifically for the use case of text overflow and adding an ellipsis. I realize that there is a "solution" above but in my opinion having to manually pass in a list of MenuItem components is a lot of extra work for what should be a simple property? Correct me if I'm wrong, but I can definitely see this being useful. Thanks!


Add LibreTube

Added the LibreTube icon, I'd love to see it included in lawnicons :)

closes #569

To fit with the style of the other icons, I think you should use a stroke instead of a fill :)

Alright, thanks for your feedback. I resized it now as suggested.

Whoops, sorry for rerequesting your review.

Applied your suggested SVG, I agree that the geometry looks more balance now.
I bet you would be faster by force pushing your changes instead of always requesting them.
Thank you for all your work, I really appreciate your help :)

Cheers for applying the edits! While it would certainly speed things up if I applied my suggestions directly, I prefer to allow the author of the pull request to evaluate the suggestions and express their thoughts on them. Design is in large part a subjective matter, so I’m open to discussing ideas. Thanks for contributing!


Discussion deployment

Hello,
I have a few questions. I am not an expert of Openshift so correct me if I don't use appropriate term.
Which openshift version is used? 3 and 4 compatible?
Is it possible to launch deployment from an Openshift Node ? I think I can do it for example with python API.
My use case is to listen for a change in the registry of mlflow and when a model appears in stagging/Production I want to launch a deployment on Openshift on another node.
I don't use AWS for storage. Is it mandatory ? I have another storage system.
Do you think we can deploy few models on the same node ? Or I need to make a specific application for that ?
Thanks for your contribution!

To answer question: on AWS dependency.
https://github.com/BIX-Digital/mlflow-openshift/blob/1909191503ec2071d6f1f4e79cd859e7d7ad15e2/mlflow_openshift/utils.py#L26

Hi @slamer59!
First, sorry for the delay on answering, we are on a besteffort mode :)
Regarding OpenShift clusters versions compatibility, so far we have fully tested it on OpenShift 3 and in the next days we are going to validate its behaving as expected also in OpenShift 4. We will update the docs once we have it confirmed.
Regarding launching deployments from an OpenShift node, I do not see any caveat on that meanwhile you have the right secrets/configs in place.
Regarding the AWS storage, so far as you can see in the template here:
https://github.com/BIX-Digital/mlflow-openshift/blob/1909191503ec2071d6f1f4e79cd859e7d7ad15e2/mlflow_openshift/templates/deploy_with_auth.yml#L119
the setup expects to connect to an S3-like storage.
This means that by default this is not supported but we can easily add other storage types. Let us know if you want to contribute on this.

Thanks for your feedback.
Really interersting.
I develop an mlflow-jfrog-artifactory (I wish to release...)
I think there is only a small trick to make it more general with any artifact store. I will think about it.
I read that yaml can read another yaml. Maybe ?
https://stackoverflow.com/a/52676097/4989371
I keep you posted

closing this issue since there has not been activity for more than a year


[Question] is Locksmithd able to check components have stared up correctly ?

Hi,
We are running a K8s cluster with 3 ETCD nodes and 3 Worker nodes on Flatcar. The Worker nodes have the flatcar-reboot-operator installed.
The whole cluster upgraded from 3760.2.0 to 3815.2.0 and the Docker daemon failed to start up. The reason for that was an old config we had in daemon.json.
failed to start daemon: error initializing graphdriver: overlay2: unknown option overlay2.override_kernel_check: overlay2
{
 "log-driver": "json-file",
 "log-opts": {
   "max-size": "30m",
   "max-file": "5"
 },
 "storage-driver": "overlay2",
 "storage-opts": [
   "overlay2.override_kernel_check=true"
 ]
}

Removing  "overlay2.override_kernel_check=true" fixed the issue.
The problem we are having is the fact that all flatcar nodes did upgrade successful from a point of view of the OS. As mentioned the
ETCD nodes have locksmithd setup and restart at a specific time. So what happened, is Flatcar was restarted. The Locksmithd daemon came up and released the lock I guess, but docker didn't start up, then the next box continued with the upgrade, and we ending up with no ETCD up.
Is there any good solution to make sure the boxes are not being bounced until docker is up ? I guess for the worker nodes the flatcar-operator would prevent a reboot of the next box if the previous didn't come up ?
Thanks for any advise and feedback.

hi @mikekuzak,
you should be able to add services you require to be running post-update as dependencies of update-engine (https://www.flatcar.org/docs/latest/setup/debug/manual-rollbacks/#automated-rollbacks).
Locksmithd has an After=update-engine.service requirement, so this should make sure locksmith does not let more nodes update if the required services don't start post-update.

I guess this should do the trick
 cat /etc/systemd/system/locksmithd.service.d/10-dependency-dockerd.conf

[Unit]
Requires=docker.service
After=docker.service
After=update-engine.service

I won't solve the problem to check if ETCD container is up without writing another systemd script checking for that .. but it's better than before I guess.

The drop-in should be on the update-engine.service instead of locksmithd.service so that the update is not considered "successful" too.


[Bug] [Dependency]: Import LabelingAgent is failing due to langchain and pydantic dependency issue with refuel-autolabel

Hi,
I tried importing LabelingAgent using below code :
from autolabel import LabelingAgent
getting pydantic error, please check full issue in attached file
Basically, issue is with langchain, it needs pydantic version >= 2, but this is not supported by refuel-autolable 0.0.15, when I tried to upgrade langchain (which supports pydantic>=2.0), again refuel-autolable 0.0.15 doesn't support langchain >=0.0.210
Using Python 3.9.18
OS: windows 11
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
langchain 0.0.226 requires pydantic<2,>=1, but you have pydantic 2.0 which is incompatible.
langchainplus-sdk 0.0.20 requires pydantic<2,>=1, but you have pydantic 2.0 which is incompatible.
refuel-autolabel 0.0.15 requires langchain==0.0.210, but you have langchain 0.0.226 which is incompatible.

`---------------------------------------------------------------------------
PydanticUserError                         Traceback (most recent call last)
Cell In[8], line 3
      1 import json
----> 3 from autolabel import LabelingAgent

File c:\users\hp\appdata\local\programs\python\python39\lib\site-packages\autolabel\__init__.py:3
      1 from importlib import metadata
----> 3 from .labeler import LabelingAgent
      4 from .utils import get_data
      5 from .dataset import AutolabelDataset

File c:\users\hp\appdata\local\programs\python\python39\lib\site-packages\autolabel\labeler.py:13
     10 from rich.console import Console
     11 from rich.prompt import Confirm
---> 13 from autolabel.cache import SQLAlchemyGenerationCache, SQLAlchemyTransformCache
     14 from autolabel.confidence import ConfidenceCalculator
     15 from autolabel.configs import AutolabelConfig

File c:\users\hp\appdata\local\programs\python\python39\lib\site-packages\autolabel\cache\__init__.py:2
      1 from .base import BaseCache
----> 2 from .sqlalchemy_generation_cache import SQLAlchemyGenerationCache
      3 from .sqlalchemy_transform_cache import SQLAlchemyTransformCache

File c:\users\hp\appdata\local\programs\python\python39\lib\site-packages\autolabel\cache\sqlalchemy_generation_cache.py:3
      1 from sqlalchemy.orm import sessionmaker
      2 from typing import Optional
----> 3 from autolabel.schema import GenerationCacheEntry
      4 from autolabel.database import create_db_engine
      5 from autolabel.data_models import Base

File c:\users\hp\appdata\local\programs\python\python39\lib\site-packages\autolabel\schema.py:6
      3 from typing import Any, Dict, List, Optional, Union
      5 import pandas as pd
----> 6 from langchain.schema import Generation
      7 from pydantic import BaseModel
      9 from autolabel.configs import AutolabelConfig

File c:\users\hp\appdata\local\programs\python\python39\lib\site-packages\langchain\__init__.py:6
      3 from importlib import metadata
      4 from typing import Optional
----> 6 from langchain.agents import MRKLChain, ReActChain, SelfAskWithSearchChain
      7 from langchain.cache import BaseCache
      8 from langchain.chains import (
      9     ConversationChain,
     10     LLMBashChain,
   (...)
     18     VectorDBQAWithSourcesChain,
     19 )

File c:\users\hp\appdata\local\programs\python\python39\lib\site-packages\langchain\agents\__init__.py:2
      1 """Interface for agents."""
----> 2 from langchain.agents.agent import (
      3     Agent,
      4     AgentExecutor,
      5     AgentOutputParser,
      6     BaseMultiActionAgent,
      7     BaseSingleActionAgent,
      8     LLMSingleActionAgent,
      9 )
     10 from langchain.agents.agent_toolkits import (
     11     create_csv_agent,
     12     create_json_agent,
   (...)
     21     create_vectorstore_router_agent,
     22 )
     23 from langchain.agents.agent_types import AgentType

File c:\users\hp\appdata\local\programs\python\python39\lib\site-packages\langchain\agents\agent.py:16
     13 from pydantic import BaseModel, root_validator
     15 from langchain.agents.agent_types import AgentType
---> 16 from langchain.agents.tools import InvalidTool
     17 from langchain.base_language import BaseLanguageModel
     18 from langchain.callbacks.base import BaseCallbackManager

File c:\users\hp\appdata\local\programs\python\python39\lib\site-packages\langchain\agents\tools.py:4
      1 """Interface for tools."""
      2 from typing import Optional
----> 4 from langchain.callbacks.manager import (
      5     AsyncCallbackManagerForToolRun,
      6     CallbackManagerForToolRun,
      7 )
      8 from langchain.tools.base import BaseTool, Tool, tool
     11 class InvalidTool(BaseTool):

File c:\users\hp\appdata\local\programs\python\python39\lib\site-packages\langchain\callbacks\__init__.py:3
      1 """Callback handlers that allow listening to events in LangChain."""
----> 3 from langchain.callbacks.aim_callback import AimCallbackHandler
      4 from langchain.callbacks.argilla_callback import ArgillaCallbackHandler
      5 from langchain.callbacks.arize_callback import ArizeCallbackHandler

File c:\users\hp\appdata\local\programs\python\python39\lib\site-packages\langchain\callbacks\aim_callback.py:4
      1 from copy import deepcopy
      2 from typing import Any, Dict, List, Optional, Union
----> 4 from langchain.callbacks.base import BaseCallbackHandler
      5 from langchain.schema import AgentAction, AgentFinish, LLMResult
      8 def import_aim() -> Any:

File c:\users\hp\appdata\local\programs\python\python39\lib\site-packages\langchain\callbacks\base.py:7
      4 from typing import Any, Dict, List, Optional, Union
... (54 lines left)

Hey @diljeet1994, with the new version, we have upgraded the langchain version and you should now be able to build autolabel. Let me know if you are still having issues!

Hi @rajasbansal ,
Thanks for the update, but please update the langchain to newer version that support pydantic>2.0 so that rest of the production level  code doesn't breaks, with your current update, langchain version is 0.0226 which supports pydantic < 2.
Please make this change cause it may give issue to lot of folks trying latest pydantic version for their apps.


Fix race issue with picoquic streams and other minor updates

Fixes stream race issue causing picoquic to close connections due to local error 5.
Also added the following:

Fixed debug logging in transport to be set when transport config enables debug
Added reusable publish send object buffer to avoid needless allocations for every object sent

Oh, linux is mad about a missing header <stdexcept> I think for those exceptions. Also looks like it's mad about some moves?

Thanks. Just made those changes. It's interesting because I didn't change those... but good to get fixed. :)


video image size

is there a way to specify a larger output size?
much thanks

See related issues #20 and https://github.com/tg-bomze/Face-Image-Motion-Model


don't send an ACK when receiving a packet that wouldn't be acked

There's a lower bound which packets get acknowledged in an ACK frame. When receiving a packet smaller than that bound, which was reported missing before, it's not necessary to immediately queue an ACK, since it wouldn't be included in the ACK frame anyway.
This seems to have a small positive effect on the transfer rate on lossy connections.

Codecov Report

Merging #1333 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master    #1333   +/-   ##
=======================================
  Coverage   90.52%   90.52%
=======================================
  Files         119      119
  Lines        8310     8310
=======================================
  Hits         7522     7522
  Misses        522      522
  Partials      266      266

Impacted Files
Coverage Δ

internal/ackhandler/received_packet_handler.go
97.1% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Can't find Zero-DCE onnx models

Issue Type
Bug
OS
Other
OS architecture
Other
Programming Language
Other
Framework
ONNX
Model name and Weights/Checkpoints URL
243_Zero-DCE-improved
Description
After download, I can't find the zero_dce_improved_480x640.onnx or another onnx file except of finnger_96x96.onnx
It seems that the data is uploaded to wasabisys server, but something is missing.
Relevant Log Output
No response
URL or source code for simple inference testing code
No response

https://s3.ap-northeast-2.wasabisys.com/pinto-model-zoo/243_Zero-DCE-improved/resources.tar.gz

Thank you, works as expected.


Jira integration and release-please results in "No user facing commits found"

No user-facing commits are found when we title our pull requests with a reference to Jira even when the notes of the squashed merge contain conventional commits. Our policy requires us to add the jira issue identifier to the title of the pull request and this will link the GitHub pull request and jira automatically.
Example pattern: "JIRA-1234: Adds a new feature that does interesting things"
Within the commits in the pull request, we may have additional conventional commits defined.
commit<PHONE_NUMBER>abcdef
Author: Me
Date: ...

   JIRA-1234: Adds a new feature that does interesting things

   * fix: fixes a bug with the ...

   * feat: Adds the new XYZ feature

Describe the solution you'd like
With some additional logging added to release-please, the CLI output shows that the merged pull requests are found and that the notes, like the example above, are seen, but the result remains that release-please reports "No user facing commits since ..."
I believe this may be because the conventional commit filter removes the candidate based on the title of the pull request. However, each of the pull requests should be a likely candidate for the changelog and a release.
Describe alternatives you've considered

Configuration settings to allow the pull request title to be used
Mechanism to enhance the processing of the squashed merge footer

I have noticed that if the title includes a conventional commit tag after the jira identifier, that release-please will sometimes , but not always, generate a pull request. Example: JIRA-1234: feat: Adds an awesome new feature

adding my 2 cents until we get a response from the maintainers on this issue:
What if you tried putting the jira issue key as a scope in the conventional commit? I know you get intermittent results with JIRA-1234: feat: something but what if you did feat(JIRA-1234): something? Most filtering implementations i've seen tend to be pretty permissive on scopes.

As @jtcressy said, put the Jira issue in the scope. We do it that way at our company, and it works perfectly fine. Automatic links from CHANGELOG.md to Jira works as well.


Submit CocoPod

Before we do this, @ecgreb made a good point we should probably start working on getting documentation on the mapzen main site.

Submitted.


Update author annotation

Pull Request Test Coverage Report for Build 357

2 of 2 (100.0%) changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.836%

Totals

Change from base Build 356:
0.0%

Covered Lines:
3142

Relevant Lines:
3459

💛  - Coveralls


Materials tag in HTML is highlighted as error from Angular Language Service

mat-slider tag is highlighted as error in HTML file:

Imported MatSliderModule in AppModule:

tsconfig.json

Using Angular 13.0.0 in VSCode version 1.62.1

Hello. I'm experiencing the same issue even if I'm using a different component library (Ionic).

VSCode version1.31.0
Project built on Angular 13
Angular Language service extension 0.900.5

To clarify: the issue is that VSCode hightlights as an error the components used even if bundling is correct (no problem whatsover when ng serve or ng build)

Closing this as it isn't a problem with the VS extension.


combineTemplate uses last property value when resubscribing

I've managed to stumble on some peculiar behavior in BaconJS. I'm not sure exactly how to describe it, but I've come up with a code sample which reproduces it, which is almost as good, right? :smile:
var stream = new Bacon.Bus();
var propBus = new Bacon.Bus();
var property = propBus.toProperty("test1").skipDuplicates();

// "Property changed to test1" - all is well
property.onValue(function (val) {
  return console.log("Property changed to " + val);
});

var combination = Bacon
  .combineTemplate({
    stream: stream.toProperty(null),
    property: property
  });

// "First take: Property via stream is test1" - still fine
combination.take(1).onValue(function (combo) {
  var property = combo.property;
  console.log("First take: Property via stream is " + property);
});

// "Property changed to test2" from first onValue() - as expected
propBus.push("test2");

// "Second take: Property via stream is test1" - This should be "test2", shouldn't it?
combination.take(1).onValue(function (combo) {
  var property = combo.property;
  console.log("Second take: Property via stream is " + property);
});

JSBin here
It seems that when resubscribing to the combination property, the old value of "property" is used. Curiously, if you comment out the stream: stream.toProperty(null), line, it works as expected.
Feel free to rename this issue if you can think of a good way to describe it!

This is the classic "why isn't my property updated" from FAQ. The combinationproperty is not updated when it has no listeners.

Shouldn't it use the latest value of property, though, when it gets a new subscriber?

It could and it this particular case might be patched to do so, but you still shouldn't rely on properties being updated while not having subscribers. In general, Properties and EventStreams as well do not listen to upstream changes without subscribers and mustn't do so.

But it's perfectly ok to ask and discuss this, of course!


Codeboard website giving error 500 on compilation

Have been seeing this error on the website for the past hour. I use codeboard for my live classes on programming. Is this something that was a scheduled maintenance job or an unexpected error? It would be great if anyone could tell me how to receive updates about such issues in the future.

Hi @harsh3195!
Thanks for reporting. The issue should be fixed now. Scheduled maintenance downtimes get announced on the website. In this case, it was a server crash that required manual intervention to fix. Sorry about the inconvenience.

The issue is fixed.  Thanks for the swift response. 👍


Moving packages

Is there a way to move packages from the GUI to another package folder? For example I want to move a package from the [SharedUnityPackagesDir] to [ProjectRoot]\Packages without having to go to the file explorer and do it myself.

Not right now though but could be useful I agree.   Not sure how the GUI would work to allow this though, because right now it only displays one package folder.


⚠ Spryr has degraded performance

In 85288ed, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 6512 ms

Resolved: Spryr performance has improved in f6bf066 after 25 minutes.


Daily email routine crashes app

The balance checking routine crashes the app when it is run.

@geoffturk
It works fine on my side. Please show me the instructions to reproduce the problem.

Sorry, I meant the daily email routine (title updated).


vim_bootstrap_updater.vim - 'cannot execute :python after using :py3'

This is my first time reporting a bug, so please excuse any protocols that I've breached.
System: Fedora 22 LXDE, with python2, python2-devel, python3, python3-devel installed.
Anyhow, upon starting up with the pre configured vimrc it'll pop out the annoying message:
E836: This Vim cannot execute :python after using :py3
E263: Sorry, this command is disabled, the Python library could not be loaded.
line    5:
E836: This Vim cannot execute :python after using :py3
E263: Sorry, this command is disabled, the Python library could not be loaded.
line    6:
E836: This Vim cannot execute :python after using :py3
E263: Sorry, this command is disabled, the Python library could not be loaded.

Quick fix done via changing ~/.vim/bundle/vim-bootstrap-updater/plugin/vim_bootstrap_updater.vim
python import sys
python import vim
python sys.path.append(vim.eval('expand("<sfile>:h")'))

to
python3 import sys
python3 import vim
python3 sys.path.append(vim.eval('expand("<sfile>:h")'))

This solution work for me. Thank's!

This solution works for me too. thanks @kendricktan

The above solution from @kendricktan just remove the vim errors at startup.
But you will still face some errors if you try to enter :VimBootstrapUpdate into vim.
So this short patch file to allow VimBootstrapUpdate to work with python3 (Fedora 22).
VimBootstrapUpdate.patch.zip

This became a problem on ubuntu 16.04 LTS too, because now, python3 is default in vim.

Is there a fix for this?, on ubuntu 14.04, changing python to python3 in vim_bootstrap_updater.vim does not fix the issue.

@rahulunair but ubuntu 14.04 has python as default.

This solution works to me on Ubuntu 16.04. Thx :)

Someone has a solution for the problem?
I try use the command :VimBootstrapUpdate and happens this below
Error detected while processing function VimBootstrapUpdate:
line   23:
E836: This Vim cannot execute :python after using :py3
E263: Sorry, this command is disabled, the Python library could not be loaded.

This solution work for me. I'm running Ubuntu 16.04 anw. Thanks :)

I used the neovim and works great after install the python support to neovim pip2 install neovim I guess needs only update the documentation

@lerrua You can close this issue.


To, too.

Something's up with travis right now

Something's up with travis right now

It's been happening since some time yesterday. Happening to Pod::To::HTML too: https://travis-ci.org/perl6/Pod-To-HTML/builds/104747418
I think we need to add ~/.rakudobrew/moar-nom/install/share/perl6/site/bin to PATH, but I'm unsure as to why, all of a sudden


Find out the minimum docker engine version Swarm supports?

Hi, All,
Using Swarm we are all very concerned about what is the minimum docker engine version Swarm supports.
In https://github.com/docker/swarm/blob/master/cluster/engine.go#L37, Swarm implies that
// Minimum docker engine version supported by swarm.
minSupportedVersion = version.Version("1.6.0")

While I tried with Swarm 1.2.3 and Docker 1.6.0, unfortunately there is some incompatibility  in the API. Swarm uses engine-api to connect with docker's API, while docker 1.6.0's API version is too old to support engine-api, such as /info API. Related issue #2150
And I tried docker 1.7.0, although the /info API will be OK, there is something wrong for engine-api to support docker 1.7.0's event API. Therefore, failed again.
docker 1.7.1 failed as well.
And I tried docker 1.8.0, it works fine with Swarm 1.2.3.
So, I think we should update minSupportedVersion in Swarm.
In addition we see that in CI, Swarm supports docker 1.9.0.
My environment:
~ $  docker version
Client:
 Version:      1.11.1
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   5604cbe
 Built:        Tue Apr 26 23:44:17 2016
 OS/Arch:      darwin/amd64

Server:
 Version:      swarm/1.2.3
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   HEAD
 Built:        <unknown>
 OS/Arch:      darwin/amd64

~ $  docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 0
Server Version: swarm/1.2.3
Role: primary
Strategy: spread
Filters: health, port, containerslots, dependency, affinity, constraint
Nodes: 1
 dao: <IP_ADDRESS>:2376
  └ ID: CZYK:SOH2:6LGU:NXZU:MLOA:RGP2:LAP4:G3JE:SXPB:SMO5:DMBL:L7RU
  └ Status: Pending
  └ Containers: 0
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 2.053 GiB
  └ Labels: executiondriver=native-0.2, kernelversion=3.13.0-24-generic, operatingsystem=Ubuntu 14.04 LTS, storagedriver=aufs
  └ UpdatedAt: 2016-06-05T11:51:01Z
  └ ServerVersion: 1.7.1
Plugins:
 Volume:
 Network:
Kernel Version: <unknown>
Operating System: darwin
Architecture: amd64
CPUs: 0
Total Memory: 0 B
Name: sunhongliangdeMacBook-Pro.local
Docker Root Dir:
Debug mode (client): false
Debug mode (server): false
WARNING: No kernel memory limit support

I think support for 1.6 should be dropped at the very least. 1.7 might stay for a while, depending on usage.

@nishanttotla
Yes, swarm should have ability to support wide versions of docker engine.
With docker 1.7.x, code below never returns.https://github.com/docker/swarm/blob/master/cluster/event_monitor.go#L37:
responseBody, err := em.cli.Events(context.Background(), types.EventsOptions{})

1.9 prefered


[improve][broker] Avoid using blocking calls for the async method checkTopicOwnership

Motivation
Avoid using blocking calls for the async method "checkTopicOwnership"
Modifications

Make checkOwnership to pure async.

Verifying this change

[x] Make sure that the change passes the CI checks.

Documentation

[x] no-need-doc

/pulsarbot rerun-failure-checks

/pulsarbot rerun-failure-checks

/pulsarbot rerun-failure-checks


Fixed typo

Which whcih is which?

@sparkitect : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@MSFTMan : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Package Manager

You should definitely add this package to PM

We know having this code in a package would be useful to you and other users. We are still evaluating the possibility of doing this transition soon. We'll let everyone know when that will happen. Thank you for your feedback and your patience.

Please see this other thread https://github.com/Unity-Technologies/NavMeshComponents/issues/172#issuecomment-741714518

It is now an experimental package for Unity 2019.4 or newer. Please follow this other discussion https://github.com/Unity-Technologies/NavMeshComponents/issues/172#issuecomment-808105998


Padding mask for BERT

Is it worth investing the effort to write a custom create_mask to handle padding? Can we even pass the padding information based on the input to the function?
Many thanks in advance,
Kevin

Would you mind adding a little more detail here? I think it depends on how you plan to do padding + masking but this should work and should be achievable with mask mod

The padding mask is created as follows, where the size is (batch_size, sequence_length) with varying sample lengths within a batch:
def generate_padding(input_id):
    '''
    Description:
    ------------
    Generate padding mask for target tensor.
    For tgt tensor, pad token is 0 and non-pad token is 1.
    Convert tgt tensor to boolean tensor,
    where pad token is True and non-pad token is False.
    Can also be applied to generate source padding mask.

    Parameters:
    -----------
    input_id: `torch.tensor`
        Tensor of input ids.

    Returns:
    --------
    pad: `torch.tensor`
        Boolean tensor of padding mask.
    '''
    pad = input_id == 0
    return pad

For the BERT mask, we apply it by setting the masked token to -100 which is subsequently ignored in the self-supervised masking loss (CE loss). Thus, we only provide the padding mask to the attention. Presumably, we have to write our own masking function for the padding mask, reshape and broadcast our mask and pass it to mask mod. Would you agree with that?

yeah I think that you would want a mask_mod that knows which tokens should be masked, somewhat similiar to this pattern: https://github.com/pytorch-labs/attention-gym/blob/75867424a1d4391bff49527029d3612a09dd67e2/attn_gym/masks/document_mask.py#L53
where you can prefill a tensor and use it as look up.

Can I make padding not attend to anything using FlexAttention padding? Would it improve inference speed?
Here is what I was thinking:
pad_mask: BoolTensor = (idx == pad_token)

def padding(b, h, q_idx, kv_idx):
    # do not attend to padding and padding should not attend to anything
    return pad_mask[b, q_idx] and pad_mask[b, kv_idx]

Thank you so much I will give it a try the next few days and will provide you with feedback here.

Hi, thank you very much for your excellent tutorials and resources!
I noticed that in the following line of code:
B, H, Q, KV = mask.shape

(https://github.com/pytorch/pytorch/blob/main/torch/nn/attention/flex_attention.py#L672C5-L672C29)
the mask is required to have 4 dimensions. My understanding is that the current implementation of create_block_mask only works if mask_mod has 4 dimensions. I was wondering if there is a way to pass a 2D mask of shape (b, s) for bidirectional self-attention instead?
Thank you very much in advance!


chore: upgrade playwright

We had pinned Playwright due to https://bugzilla.mozilla.org/show_bug.cgi?id=1832341. Finally getting around to adding a workaround for it since it seems like it's not getting fixed

oof. nice work


integrate jenkins as independent sub-module

https://github.com/zebrunner/jenkins-master
this repo should be added as sub-module into the qps-infra repo

done: https://github.com/qaprosoft/qps-infra/pull/239
testing scenario:

clone recursively qps-infra using develop branch
git clone --recurse-submodule --branch develop https://github.com/qaprosoft/qps-infra.git

configure it using setup interactive installer/configurator:
./zebrunner.sh setup
-> provide valid protocol, hostname and port
Note: final infra url should be like http://<IP_ADDRESS>:80

be able to login into the jenkins using admin/changeit

be able to register/scan repository and run api tests

Verified. Fixed.


How to specify advanced mount options

Mounts have advanced syntax in docker that can be used to prevent docker daemon from creating directories that don't exist on the host. See: https://docs.docker.com/storage/bind-mounts/
See https://github.com/moby/moby/pull/19953#issuecomment-898352765 comment on required syntax.
Is it possible to replicate this within "HostConfig" ?

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

ID: 7e02119b-094f-29ba-dd91-71702627cfa6
Version Independent ID: 48c4e621-56be-593e-a68f-9f74168bf0f5
Content: Use IoT Edge device local storage from a module - Azure IoT Edge
Content Source: articles/iot-edge/how-to-access-host-storage-from-module.md
Service: iot-edge
GitHub Login: @kgremban
Microsoft Alias: kgremban

Hello @YarekTyshchenko I am trying to understand the requirement in more detail.
Could you please confirm if you are configuring the local storage in the deployment manifest of Host Config section? like shown in below document/
Link module storage to device storage
Also,
Do you want to restrict the docker daemon on creating the non-existing directory on the host via Advanced options?

@SatishBoddu-MSFT Not exacly. I'm configuring storage for my own module, not iotedgeAgent or Hub. I have an edge appilcation that writes to an external disk. I want to make sure that if the external disk is not mounted, docker doesn't create those paths and start writing to root fs.
It would be good to have access to the advanced mounting options available in Docker.

@YarekTyshchenko - you can put anything from the Docker Engine API into the createOptions. Example - for your use case it might look like:
{
  "HostConfig": {
    "Mount": [
      {
        "Target": "/var/container-storage",
        "Source": "/var/host-storage",
        "Type": "bind",
        "ReadOnly": false
      }
    ]
  }
}

#please-close


[BUG] document file_unique_id

Nutgram version
latest
PHP version
8
Framework
No Framework
Cache driver
memory
OS
win
Dev environment
No response
Describe the bug
[2024-10-07 19:12:59] local.ERROR: The Document.file_unique_id property cannot accept null. {"exception":"[object] (SergiX44\Hydrator\Exception\InvalidValueException(code: 0): The Document.file_unique_id property cannot accept null. at D:\projects\telegram\bot\payamgir-new\vendor\nutgram\hydrator\src\Hydrator.php:406)
To Reproduce
[2024-10-07 19:12:59] local.ERROR: The Document.file_unique_id property cannot accept null. {"exception":"[object] (SergiX44\Hydrator\Exception\InvalidValueException(code: 0): The Document.file_unique_id property cannot accept null. at D:\projects\telegram\bot\payamgir-new\vendor\nutgram\hydrator\src\Hydrator.php:406)
Expected behavior
[2024-10-07 19:12:59] local.ERROR: The Document.file_unique_id property cannot accept null. {"exception":"[object] (SergiX44\Hydrator\Exception\InvalidValueException(code: 0): The Document.file_unique_id property cannot accept null. at D:\projects\telegram\bot\payamgir-new\vendor\nutgram\hydrator\src\Hydrator.php:406)
Screenshots
No response
Additional context
No response

If you don't want to take 2 minutes to fulfill the issue explaining how to reproduce the issue, we are not going to spend time on this.
Please resubmit the issue with the template fulfilled accordingly if still applicable.


ReduceLROnPlateau Scheduler documentation problem

In the documentation it's given that to use ReduceLROnPlateau Scheduler we should do it as:
# The ReduceLROnPlateau scheduler requires a monitor
def configure_optimizers(self):
   return {
       'optimizer': Adam(...),
       'scheduler': ReduceLROnPlateau(optimizer, ...),
       'monitor': 'metric_to_track'
   }

But there is no variable initialized as optimizer for 'scheduler': ReduceLROnPlateau(optimizer, ...),, so I did:
def configure_optimizers(self):
        optimizer = torch.optim.Adam(
            params=self.parameters(),
            lr=LEARNING_RATE,
            weight_decay=WEIGHT_DECAY
        )
        scheduler = torch.optim.lr_scheduler.ReduceLROnPlateau(
            optimizer,
            patience=1,
            verbose=True
        )
        return {
           'optimizer': optimizer,
           'scheduler': scheduler,
           'monitor': 'val_loss'
       }

But for some reason the Scheduler was not working. I created a Callback to check, but trainer.lr_schedulers gives an empty list.
So I tried:
def configure_optimizers(self):
        optimizer = torch.optim.Adam(
            params=self.parameters(),
            lr=LEARNING_RATE,
            weight_decay=WEIGHT_DECAY
        )
        scheduler = torch.optim.lr_scheduler.ReduceLROnPlateau(
            optimizer,
            patience=1,
            verbose=True
        )
        return {
           'optimizer': optimizer,
           'lr_scheduler': scheduler, # Changed scheduler to lr_scheduler
           'monitor': 'val_loss'
       }

And now it's working.

it's a minor doc typo. Mind send a fix?

Sure

Here is the pull request.

same problem with ver 1.3.2
    def configure_optimizers(self):
        if self.cfg.use_swa:
            self.optimizer = SWA(torch.optim.Adam(self.model.parameters(), lr=self.cfg.lr))
        else:
            self.optimizer = torch.optim.Adam(self.model.parameters(), lr=self.cfg.lr)

        if self.cfg.scheduler == 'plateau':
            self.scheduler = torch.optim.lr_scheduler.ReduceLROnPlateau(self.optimizer,
                                                                           mode='min',
                                                                           factor=0.2,
                                                                           threshold=0.01,
                                                                           patience=5)
        else:
            self.scheduler = torch.optim.lr_scheduler.CosineAnnealingLR(self.optimizer,
                                                                    T_max=self.cfg.t_max,
                                                                    eta_min=0,
                                                                    last_epoch=-1, #sets initial lr as lr.
#                                                                   eta_min=self.cfg.min_lr,
                                                                    verbose=True)

MisconfigurationException: configure_optimizers must include a monitor when a ReduceLROnPlateau scheduler is used. For example: {"optimizer": optimizer, "lr_scheduler": scheduler, "monitor": "metric_to_track"}

@TheStoneMX if I understand correctly you are attaching the scheduler to self instead you need to return your optimizers and schedulers.

Hi there and thanks for the response, I been trying to learn Lighting, can you show me how to do it? thanks

here are some docs: https://pytorch-lightning.readthedocs.io/en/latest/common/lightning_module.html?highlight=configure_optimizers#configure-optimizers

thanks!

thanks!

Solution : return {'optimizer': optimizer,
'scheduler':scheduler,'monitor':"metric_to_track",}


Support For Domain Hashes

General information

I am brand new to this library and had an idea/question.
I started hashing my pass directories in the event my system gets compromised and the person gets the urls for my acccounts, even though my usernames and passwords are still encrypted (just adding one more step to slow someone down).
Would it be possible for this app to search the pass store using a hash/salt (or just hash) based on the domain?
Thanks for a great library!

Hey, that's a curious question. First of all, I think hashing without a salt has almost no value, just consider that most domains consist only of 5-6 English letters + one of a very few common suffixes (like .com), and in the bitcoin era 10M/sec is a very generous bruteforce underestimation rate regardless of the hashing algorithm that you use - most consumer-rate GPUs will give you much faster bruteforce. And even with 10M/sec, 26^6/10M = 30 seconds to generate all hashes of all possible domain combinations in the given range.
Second of all, it won't be easy to implement this feature. Supporting a salt would mean adding a configuration option to the extension (which is easy) and communicating it to the native extension (which we don't support, and seems like can only be achieved if #20 ever gets implemented). Then there is a choice of a hashing algorithm, where we must support some kind of a selector, and again, adding it to the options and communicating the value to the native host.
Personally, I think this is a feature request that is hard to implement and won't be useful to a majority of pass users (especially if they use CLI and/or a phone app in addition to browserpass, which don't know anything about hashing of the names), so I'd tend to close this proposal as won't fix - if there is demand, we can always reopen.
Let me know your thoughts on the above.
P.S. I'm just thinking out loud, but if you really want to keep the hashed file names, you can create symlinks that you don't publish anywhere - maybe you can write yourself a small script to generate such symlinks given the password store and a salt. What I mean is the following, suppose your password store folder looks like this (MD5 with no salt is used in the example):
.password-store-files/
    a5ed434a3f5089b489576cceab824f25.gpg
    8afa6b470053a63a5ee45cfe9a52b055.gpg

Make a script that using the folder above generates a second folder with only symlinks:
.password-store/
    google.com.gpg -> ../.password-store-files/a5ed434a3f5089b489576cceab824f25.gpg
    github.com.gpg -> ../.password-store-files/8afa6b470053a63a5ee45cfe9a52b055.gpg

Browserpass will understand symlinks!
P.P.S. You might be interested in a somewhat similar feature request, where it was proposed to put url: github.com in the file itself and respect that in addition to the file name. This cannot be implemented because the extension would then require to decrypt every single file in your password store in order to determine if this entry matches the url.

Would it be possible to have another configuration file to store the url, like custom_urls.toml:
[domain1.com]
custom.auth.com

[domain2.com]
*.auth.com

That is probably the easiest way to solve, aside from caching the entire database and updating on file system changes.

This is simpler to implement, that's for sure - no need to communicate some hashing algorithms and salt between browser extension and the native app.
My concern would be that this is a custom solution that is not common, not supported by CLI pass or phone apps, and manual way "(1) decrypt cutsom_urls.toml, (2) remember the <custom_file_name>, (3) run pass show <custom_file_name>" is too painful to do every time - so as much as I would like to anonymize file names, I personally wouldn't use such solution.
One more idea that I'm personally evaluating is to store the .password-store directory on a LUKS-encrypted drive (which can encrypt file names too), and put it in Dropbox. That way locally you still see the normal names, pass and browserpass work as expected with no extra configuration, but on remote you cannot see the directory structure. I know Android phone can decrypt LUKS drive, not sure if I can integrate the decrypted drive into the Password Store app though.

Just a heads up, the next major version of browserpass will remember which passwords you used on which domains and show them next time in the popup.
So if you have a password entry called KDE Bugs.gpg and you navigate to bugs.kde.org, at first just like today browserpass will not show KDE Bugs among the list of passwords (to protect you from phishing attacks), however if you specifically search for KDE Bugs and use it to login, next time you open bugs.kde.org the entry KDE Bugs will be present in the popup.
So you will theoretically be able to use random names for your password entries 😄

Thank you and very much looking forward to the next version of browserpass. Where will it be saving the information and can it be easily backed up? Will there be a way to determine this information without using the browser, or a CLI wrapper to use it as well?

@braderhart It's stored (hashed) in the browser local storage as a JSON object. There is no specific method to back this up, but it can easily be copied out using the browser's developer console.
There is no way to easily obtain this without using the browser, and we do not provide a CLI wrapper for it.

@erayd Thanks for the info.


InnerPropagator.kt:46-48: this solution is naive,...

The puzzle 34-102b18e9 from #34 has to be resolved:
https://github.com/objectionary/deog/blob/46c3534e288fcb263b1165938e8859f229823b75/src/main/kotlin/org/objectionary/deog/steps/InnerPropagator.kt#L46-L48
The puzzle was created by @c71n93 on 17-Oct-23.
Estimate: 30 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@c71n93 please pay attention to this new issue.


Persistent Search Icon / Hint textbox

Would it be possible in a future release to expose some properties to change the Icon and the searchbox hint message ("Search")

I will consider this for the next release.


Use any instead of all for build number check.

@cdeepali Found that we should be using any here instead of all.

Codecov Report

Merging #102 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #102   +/-   ##
=======================================
  Coverage   95.71%   95.71%
=======================================
  Files           8        8
  Lines         583      583
=======================================
  Hits          558      558
  Misses         25       25

Flag
Coverage Δ

#unittests
95.71% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out 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 035395f...a9178e7. Read the comment docs.


Pipeline won't run when cdc.config file missing

Description of the bug
Line 184 in nextflow.config causes pipeline to fail because this file has not been included in the conf folder.
line 184: includeConfig 'conf/cdc.config'
We can remove this line, but then CDC users need to point to the cdc config file when they run the pipeline on Rosalind, and so we need to update README docs to indicate that.  Otherwise, we include that file in conf.  I can do whichever is preferred.
Command used and terminal output
nextflow run main.nf --indir /scicomp/groups-pure/Projects/scbs_mpob/JRowell_ick4/mpox_testing/paired/ --outdir /scicomp/groups-pure/Projects/scbs_mpob/JRowell_ick4/mpox_testing/results/ --project_name test -profile singularity,rosalind

File not found: /scicomp/home-pure/ick4/01.scripts/polkapox/conf/cdc.config

Relevant files
N/A
System information
No response

Suggest to remove includeConfig 'conf/cdc.config from nextflow.config. Readme already has some basic instruction for CDC users to add their own config:
https://github.com/CDCgov/polkapox?tab=readme-ov-file#running-on-cdc-cluster
Suggest to update this with generic example of how to also define config at runtime, eg:
-config /some/path/to/cdc.config

Done. Waiting to be able to test (missing mpxvgfa.sif)

Merged into master by @mikeyweigand


docs: correct parachain destination

Thanks for the contribution, however, we are currently removing the incentivized channel so related documentation will also be removed.
Please see this related PR:
https://github.com/Snowfork/snowbridge/pull/762


DVC client fails to move files

HKube micro-service
datasource-service
Describe the bug
DVC client fails to move files
In dvc versions 2.2 and 2.3 there is a bug that when moving a file the .meta field is not copied to the new .dvc file
the bug is in the new DVC client code
To Reproduce
Reproduced in unit test should move a file

should be ok when iterative/dvc#6200 is fixed

temp fix (pin dvc version to 2.1) #1302


In background state on ios on first time push is received OnNotificationReceived and OnReceived methods don't work

I am using mvvmcross framework, did setup according to your instructions, and everything works fine on ios and android on every state except the first time push received on ios in background state. I mean when you open app and then close. It will be the first time for app when it will receive background push. In device log I can see that app initialization is happening, but methods where to proceed push notification is not called. But second push works fine as I have said.
Also I can see such error:
Info (418) / iOS(GoogleUtilities): 6.22.0 - [Firebase/Core][I-COR000003] The default Firebase app has not yet been configured. Add [FIRApp configure]; (FirebaseApp.configure() in Swift) to your application initialization. Read more: https://goo.gl/ctyzm8.
Maybe that cause the problem? Does anyone faced with such problem?
Plugin version: 3.3.10
Ios version: 13.3.1

I have same problem also in foreground state.


ENH: generator expressions for builtin all and any

Closes #1991.

@Eric89GXL ready for review.

Let me know when tests pass, you have some problems with len

travis is not happy

@agramfort looks like a false negative.

Good for review / merge. Travis does not know that he is actually happy.

I restarted the failed Travis run, LGTM. If you don't feel like changing the lens to use sum it's fine by me

. If you don't feel like changing the lens to use sum it's fine by me

no let's do that, it's more elegant

Travis is worthless, but Appveyor has feedback:
https://ci.appveyor.com/project/Eric89GXL/mne-python/build/1.0.1416

@Eric89GXL looking more closely the latest commit is not really good. I'm removing it.

So good to go from your end, not going to use the sum trick?

So good to go from your end, not going to use the sum trick?

does not make sense for this use case, we're not summing numbers.

and sum(i for i, _ in enumerate(....)) is not really easier to read.

You're summing logicals, which should take up less memory than doing a len of a list that only gets the members for which the logical is true...

I was thinking of this case:
len([x for x in xx if x == 'foo'])

can be more efficiently computed as
sum(x == 'foo' for x in xx)

You're summing logicals, which should take up less memory than doing a len of a list that only gets the members for which the logical is true...

it was trings, not?

@Eric89GXL yes I know but that particular line was not producing logicals

This:
     n_kit_grads = len([ch for ch in chs
                        if ch['coil_type'] == FIFF.FIFFV_COIL_KIT_GRAD])

should be equivalent to this:
     n_kit_grads = sum(ch['coil_type'] == FIFF.FIFFV_COIL_KIT_GRAD for ch in chs)

I'm actually not sure which would be more efficient in all cases, but the second one at least uses a generator :)

Are you working on another commit? If not, I'll test locally and merge if all is good.

forgot to push

Cool, thanks


Retire istio/issue repo

We're not getting real value out of having istio/issue as a separate repo. It just leads to additional administration overhead. We should just use istio/istio to track all issues. It'd be great to nail this before 1.0 ships so we're on the right plan for all the new customers.
We should move all issues to the istio/istio repo, and then we can delete the istio/issue repo. We'll need to change a few "report a bug" links on istio.io accordingly.
@louiscryan @smawson @linsun @rshriram

+1, I think it had value when we had lots of repos, now that we have istio/istio as a monorepo it is fairly worthless.

+1. But let’s please not move and create more duplicates. Let the leads triage and close or manually copy the relevant issues or link to an existing issue. Meanwhile we can lock down the issues repo

I'll go ahead and change the "report a bug" links to point to istio/istio.
I'll also move the template from istio/issue to istio/istio.
On Wed, Jun 13, 2018 at 8:57 PM Shriram Rajagopalan <
<EMAIL_ADDRESS>wrote:

+1. But let’s please not move and create more duplicates. Let the leads
triage and close or manually copy the relevant issues or link to an
existing issue. Meanwhile we can lock down the issues repo
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/6266#issuecomment-397162967, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AVucHTFEJy_sHl_IVMx4Gx1ugbyHdHdJks5t8d8VgaJpZM4UnIu0
.

So:

Bug reporting links now point to istio/istio/issues

We now use GitHub's new templating controls. When you click "New Issue" in istio/istio, you now get asked whether you want to report a bug or a request a new feature, and you get type-appropriate templates.

The issue template on istio/issues was updated with a link to the istio/istio repo asking people to post issues there instead.

@rshriram I understand why you don't want to move them in bulk but the flip side is people opening new entries in the issues repo. As an example, 3 new ones were opened in the last 24 hours.
Not to mention we currently have ~160 open issues in that repo. It took 11 of us about 3 hours to close ~100 issues yesterday, I'm not sure when we will have a dedicated triage session next time. Why don't we move them all to istio/istio, achieve the issues repo and have leads continue to triage their areas over time?

Moving issues between repos unfortunately lose all labels. So they would
have to be reapplied.
On Thu, Jun 14, 2018 at 2:45 PM jasmine-jaksic<EMAIL_ADDRESS>wrote:

@rshriram https://github.com/rshriram I understand why you don't want
to move them in bulk but the flip side is people opening new entries in the
issues repo. As an example, 3 new ones were opened in the last 24 hours.
Not to mention we currently have ~160 open issues in that repo. It took 11
of us about 3 hours to close ~100 issues yesterday, I'm not sure when we
will have a dedicated triage session next time. Why don't we move them all
to istio/istio, achieve the issues repo and have leads continue to triage
their areas over time?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/6266#issuecomment-397448209, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AVucHQNAO2KlhCrJWlNpgbCIxQHdHu7Yks5t8tl1gaJpZM4UnIu0
.

The repo has been renamed to old_issues_repo, and description+template were updated to point people to istio/istio, so we're as close as we can get to deleting the repo outright, without moving items.


Ask about the dataset.

Could you provide a link to the dataset as the dataset organization in the code differs from the original ACDC dataset?

Thanks for your interest. Now, the inference is available. We will let you know immediately as soon as we open it, please keep attention. 😊

Thanks for your interest! Now, the inference is available. We will inform you immediately as soon as we open it, please keep attention on our project!😊

Hi @lsyyy20000830
Sorry to keep you waiting. We have released our generated data samples. If you are Chinese, please download data (generated rainy, snowy, and foggy images) from this Baidu Cloud link.
The Google Drive files are still uploading.


clickhouse final setting

1

This configuration does not seem to be effective in the latest version of ClickHouse <IP_ADDRESS>7

Please double check that setting is applied. Execute this command in clickhouse and paste output:
SELECT name, value, changed FROM system.settings WHERE name = 'final'
Also please check you using the correct config file for clickhouse server.

Please double check that setting is applied. Execute this command in clickhouse and paste output:
SELECT name, value, changed FROM system.settings WHERE name = 'final'
Also please check you using the correct config file for clickhouse server. You could also try to set it in users.xml file instead.

thanks. I put  it in the user.xml, that works


Clip cos(theta) to ensure that r^2 does not become negative

Clipping cos_theta to ensure r^2 does not become negative and avoids numerical errors.

Thank you for the fix, I will push this change to main.


[FEATURE] Refactor bpftime for Enhanced Extensibility and Maintainability

Issue Summary:
The current bpftime architecture intermingles code for different eBPF program types and backends, such as uprobe and syscall tracing, within the syscall-server.so. For example:

The attach_ctx class contains the uprobe and syscall code, and also maintain the state of eBPF virtual machines. https://github.com/eunomia-bpf/bpftime/blob/204f1154b8a0689a91307b87a9f4a41435077765/runtime/include/bpf_attach_ctx.hpp#L67-L77
The share memory also contains uprobe and syscall related attach infomation, which is calculated in the bpftime load time with the syscall-server.so. For instance: https://github.com/eunomia-bpf/bpftime/blob/d850554af7418f66991fff9be2363df22e2d450b/runtime/syscall-server/syscall_context.cpp#L459-L470 .  It may be better to have some API that allow the backend (Attach target) to control what kind of perf event should be mocked in userspace, and how to attach centain eBPF progs to these events (eg. XDP in userspace DPDK, nginx modules, plugins).

This design limits the addition of new attach backends and eBPF program types, and also complicates the codebase. A refactor is proposed to address these issues and set the stage for future enhancements.
Proposed Changes:

Decouple Syscall Server Responsibilities:

Restrict syscall-server.so and the daemon to only handle recording syscall traces and states, such as the creation of progs, maps, and links within the kernel.
Remove mixed responsibilities and allow for the loading of other eBPF program types.

Split Attach Context:

Separate attach context class into two distinct targets, runtime and attach_events
The runtime should offer two types of APIs:

An API for initializing and manage all progs and maps.
An API for customizing attach-related information processing and operations.

The developer can inherit attach_events class to implement their own event sources.

Temporary Feature Development Freeze:

Before the completion of the refactor, pause the addition of new features to avoid further complicating the current state.

Future-Proofing and Extensibility:

The refactor will facilitate the replacement of components like Frida, embedding runtime statically in other applications, and expanding to new domains such as GPU tracing, XDP and https://github.com/eunomia-bpf/bpftime/issues/158
Future modifications will be isolated to the attach context, simplifying updates and maintenance.

Rationale:
This refactor addresses fundamental design flaws that were not evident in the initial conception of bpftime. It aims to simplify the current codebase and prepare for more stable and scalable expansion. Although this entails a significant overhaul, it is manageable given the current code volume.
Next Steps:

Draft a detailed plan for the refactor, outlining the separation of responsibilities and the new API designs.
Address the current stability issues that have been exposed.
Establish a timeline for the refactor process, considering the complexity of the task.

Call for Input:
We welcome input from the community on this proposed refactor. Any insights or suggestions, especially regarding the decoupling of components and API design, would be highly appreciated.

Replacing of frida is already able through the attach manager (by subclassing)

Split attach manager into a seperate target
Attach manager itself is relatively independent to bpftime runtime. Split it into a seperate target, and remove the dependency of frida to runtime

What about attach_ctx class?
Is it possible to implement all uprobe/syscall related code outside of runtime target and runtime dir? If we can do that, is it a better solution?

What about attach_ctx class?
Is it possible to implement all uprobe/syscall related code outside of runtime target and runtime dir? If we can do that, is it a better solution?
And also, there are some attach related code in syscall transformer and syscall-server.so

The implementation of syscall trace is not compatible with attach manager(or let's call it uprobe attach manager)

uprobes: register a callback function at a certain function address, and waiting for calls to the callback
syscall trace: some foreign code(text transformer) would call a specified call back function, and this callback function would dispatch call to ebpf programs. No need to register callback

So I think we might syscall trace split attach implementation into another target, or call it syscall trace attach manager. Syscall trace callbacks should be registered to this target, and this target should provide a dispatch entry(The function that text transformer would call, when syscall was captured). And rename the current attach manager to uprobe attach manager, since it's only responsible for uprobes

Shall we come up with some better name for Uprobe attach manager? Maybe attach_ctx back or attach_target, attach_events?
Some background:

The eBPF runtime can be embedded in a shared memory, or compile and link with other applications as extensions. The runtime is responsible for load and manage the eBPF programs in the process.
There can be multiple eBPF attach methods at the same time, for example, uprobe and syscalls tracepoints Should be able to work together.
one eBPF program can be attached to multiple  targets or events, one event can have multiple eBPF programs attached to it.

So maybe we can have a design like this:

One attach_manager for managing all attach_ctx or attach_targets. The attached manager can have the unique ptr ownership of the runtime.
attach_ctx has a base class and some sub classes. For example, uprobe_attach_ctx class and  syscalls_attach_ctx. The attach_ctx should be able to access the shared memory through the runtime API, and also config what kinds of perf events or attached targets can be mocked in userspace, while others can be passed into the kernel.

These codes are all in the attach dir in project root.
Another problem is, how can we make the attach_targets config what kinds of perf events or attached targets can be mocked in userspace, while others can be passed into the kernel? If we don't want to hardcode it in the -server.so like what we did now.

So Maybe we can create two targets?

/attach/uprobe
/attach/syscalls

The attach is a new dir under the project root.
And the user can specify which one to compile with the runtime.

Sounds good. More attach implementation could be added in the future

Shall we come up with some better name for Uprobe attach manager? Maybe attach_ctx back or attach_target, attach_events?
Some background:

The eBPF runtime can be embedded in a shared memory, or compile and link with other applications as extensions. The runtime is responsible for load and manage the eBPF programs in the process.
There can be multiple eBPF attach methods at the same time, for example, uprobe and syscalls tracepoints Should be able to work together.
one eBPF program can be attached to multiple  targets or events, one event can have multiple eBPF programs attached to it.

So maybe we can have a design like this:

One attach_manager for managing all attach_ctx or attach_targets. The attached manager can have the unique ptr ownership of the runtime.
attach_ctx has a base class and some sub classes. For example, uprobe_attach_ctx class and  syscalls_attach_ctx. The attach_ctx should be able to access the shared memory through the runtime API, and also config what kinds of perf events or attached targets can be mocked in userspace, while others can be passed into the kernel.

These codes are all in the attach dir in project root.
Another problem is, how can we make the attach_targets config what kinds of perf events or attached targets can be mocked in userspace, while others can be passed into the kernel? If we don't want to hardcode it in the -server.so like what we did now.

This also soulds good. But the uprobe attach manager I mentioned above is only some classes that provide API to register a callback at a certain function. It has nothing to do with any eBPF stuff. Maybe a name like uprobe_attach_impl is more suitable for this part of code?

Shall we come up with some better name for Uprobe attach manager? Maybe attach_ctx back or attach_target, attach_events?
Some background:

The eBPF runtime can be embedded in a shared memory, or compile and link with other applications as extensions. The runtime is responsible for load and manage the eBPF programs in the process.
There can be multiple eBPF attach methods at the same time, for example, uprobe and syscalls tracepoints Should be able to work together.
one eBPF program can be attached to multiple  targets or events, one event can have multiple eBPF programs attached to it.

So maybe we can have a design like this:

One attach_manager for managing all attach_ctx or attach_targets. The attached manager can have the unique ptr ownership of the runtime.
attach_ctx has a base class and some sub classes. For example, uprobe_attach_ctx class and  syscalls_attach_ctx. The attach_ctx should be able to access the shared memory through the runtime API, and also config what kinds of perf events or attached targets can be mocked in userspace, while others can be passed into the kernel.

These codes are all in the attach dir in project root.
Another problem is, how can we make the attach_targets config what kinds of perf events or attached targets can be mocked in userspace, while others can be passed into the kernel? If we don't want to hardcode it in the -server.so like what we did now.

This also soulds good. But the uprobe attach manager I mentioned above is only some classes that provide API to register a callback at a certain function. It has nothing to do with any eBPF stuff. Maybe a name like uprobe_attach_impl is more suitable for this part of code?

And the attach manager you mentioned seems to be something that is responsible for "resolving perf event (or other equivalent), and allowing a certain event to call a certain ebpf program". Did I mis-understand what you said? If not, I think this thing is more suitable for the name attach manager, and should be split into individual targets.
But from another perspective, I still think uprobe_attach_impl should be split into an individual target. It has little dependency to other parts of bpftime. Splitting it into an individual can make the code base clearer, and would make it more convenient for other users that only want to use the uprobe implementation by us

Yes, uprobe_attach_impl should be split into an individual target.
Can you describe the full dependence of the modules you think may be correct?

What does ownership of runtime means? Is it something that holds all ownerships of compiled ebpf programs? (The ownership of maps are remained in the shm, and isn't held by anything, I think)

have a unique ptr in the code, and responsible for managing the open and close of the maps, compile and load the progs.

What does ownership of runtime means? Is it something that holds all ownerships of compiled ebpf programs? (The ownership of maps are remained in the shm, and isn't held by anything, I think)

have a unique ptr in the code, and responsible for managing the open and close of the maps, compile and load the progs.

Maps and programs are held in the shared memory, and may live longer than agent or syscall server. So maybe their ownership should not be limited by bpftime runtime?
"ownership" here means "stuff in the heap memory of a certain process that is required to operate shared memory". For example, the class bpftime_shm itself

Targets

uprobe_attach_impl: Implementation of uprobe attaches. Attaching to a specified address and waiting for callback. At /attach/uprobe/uprobe_attach_impl
text_segment_transformer: Same to the current target in that name. But moved to /attach/syscall/text_segment_transformer. Provide function to register a callback for syscall invocations.
syscall_attach_impl: Implementation of syscall attach. Providing a function to receive raw syscall events. And allow registering callbacks to a specified syscall id, or all syscalls. At /attach/syscall/syscall_attach_impl
base_attach_impl: Providing a set of headers which is an abstraction of attach implementations. The base pure virtual class should provide functions to iterate over attaches, or detach. Attaching API prototypes may not be provided in the base class, since attach arguments varies among different attach types. Should be at /attach/base_attach_impl
base_event_source: Provide a set of headers and base classes that define event source, which are things like load and compile an ebpf program, attach a uretprobe to function XYZ which will call ebpf program ABC, create an ebpf hash map, detach uretprobe with id XXX. With this we won't be limited to collect ebpf operations through libbpf. We can even use a nginx module as event source.  Should be at /attach/event_source/base_event_source
syscall_server_event_source: Provide events collected from mocked libbpf functions. This should be modified from the current syscall server. Should be at /attach/event_source/syscall_server_event_source
attach_manager: Holding all available attach implementation at runtime. Receive events from attach_event_source, and drive attach impls to do the underlying things. attach manager should hold the ownerships of compiled ebpf programs and corresponding virtual machines. It should also hold attach implementations. Should be in /attach/attach_manager

Is it better that you can first come up with a small example of how to use the new api to implement a new eBPF attach type (e.g. nginx module eBPF)?

Is it better that you can first come up with a small example of how to use the new api to implement a new eBPF attach type (e.g. nginx module eBPF)?

OK, I'll take it

Refer to https://github.com/eunomia-bpf/bpftime-new-api-poc for detailed POC
Other notes:

Avoid invasive nginx handler related APIs in bpftime codebase, such things could be implemented by exposing more low level APIs (such as manually managed extra data of attach target entry)

Instantiation of handler

prog_handler: The result of an instantiation of a prog handler is an instance of bpftime_prog, which includes a ready-to-execute ebpf virtual machine
perf event handler: The result of an instantiation of a perf event handler is an instance of attach_private_data. It's an abstract base class used to pass attach data to *_attach_impl, describing attach arguments (such as function offset of uprobe, syscall id of syscall trace, or a custom string for user-defined attach impls)
link handler: Usually the instantiation of a link handler would first lead to the instantiation of its related prog handler. After that, the process was determined by the user-registered instantiating handlers of different link type. For the built-in perf event link type, it would first instantiate the related perf event handler(to get the attach private data), then it would call *_attach_impls to register an native attach entry, and record the mapping from handler id to the native attach id. For the built-in uprobe_multi link type, no perf event is required. When instantiating a link of uprobe multi type, it would directly create attach_private_datas basing on arguments stored in the link (note that the creation of uprobe multi requires the registraion of uprobe/uretprobe attach impl). When instantiating a user-defined link type, it would directly call the user-registered instantiating function


Envoy/RateLimit - Memory Leak

Hello Guys,
We have a problem with memoryLeak Ratelimit.
In the following configuration scenario;

Application in AWS Fargate Service

4 Task Definition - Each instance with 3072MB of memory and 1024MB of CPU

Within each task, we have 3 containers with storage distributed like this;

Envoy - 1536MB
Envoy/Ratelimit - 1024MB

To control the cache we use redis

Datadog - 512MB

Our average request is ~50tps (transactions per second), at dawn we have several bachs running, so the volume is high.

Before we had a smaller configuration, but we had problems with the envoy/ratelimit server.
We would like to know if we have a recommended configuration for the volume of requests?
Regards.

cc @mattklein123 @wbpcode

Sorry not much information to work with here. Please get heap profiles that will help us determine where the leak is coming from. https://www.envoyproxy.io/docs/envoy/latest/faq/debugging/how_to_dump_heap_profile_of_envoy


SA1313 should not be rised when parameter is in record constructor

Such syntax
record RecordName(string ParamA, int ParamB);
should not match SA1313 rule.

sorry, missed that this is working in beta version, when it will be stable? we use records in production and don't want any beta dependencies.

don't want any beta dependencies

StyleCop Analyzers isn't a shipping dependency, so it doesn't fall into the same NuGet package analysis restrictions that other pre-release packages fall into. If you are just trying to check off a box saying there are no NuGet packages in the build with a -beta suffix, you can reference StyleCop.Analyzers.Unstable <IP_ADDRESS>1 instead of StyleCop.Analyzers 1.2.0-beta.321. Both packages are published at the same time.

Duplicate of #3232

maybe that information shoud be added to "C# language versions" in readme?


Support register ipv6 address to Nacos

我们鼓励使用英文，如果不能直接使用，可以使用翻译软件，您仍旧可以保留中文原文。
We recommend using English. If you are non-native English speaker, you can use the translation software.
Which Component
Nacos
Is your feature request related to a problem? Please describe.
Support register ipv6 address to Nacos
When I have both ipv4 and ipv6 address, SCA seems to register ipv4 address to Nacos, we provider an option for user to register either ipv4 , ipv6 or both.

I can take this,  assign me if in convenient.

i can do it


I am getting error just after importing @google-cloud/storage : Module not found: Error can't resolve 'child_process', how to fix?

I am getting error just after importing @google-cloud/storage
Environment details

OS: macOS Big Sur
Node.js version: v12.18.4
npm version:6.14.6
@google-cloud/storage version:^ 5.6.0
framework nuxt js version : Nuxt.js @ v2.14.7

Steps to reproduce

install @google-cloud/storage
yarn add @google-cloud/storageor npm install @google-cloud/storage --save
import it
const {Storage} = require('@google-cloud/storage');
const storage = new Storage({
keyFilename : path.join(__dirname, './file.json'),
projectId: "xxx-xxx-xxx"
});

just after that i got this error
ERROR in ./node_modules/google-auth-library/build/src/auth/googleauth.js Module not found: Error: Can't resolve 'child_process' in '/Users/xxx/xxxx/node_modules/google-auth-library/build/src/auth' ERROR in<EMAIL_ADDRESS>Module not found: Error: Can't resolve 'fs' in '/Users/xxx/xxxx/node_modules/@google-cloud/storage/build/src' ERROR in<EMAIL_ADDRESS>Module not found: Error: Can't resolve 'fs' in '/Users/xxx/xxxx/node_modules/@google-cloud/storage/build/src' ERROR in ./node_modules/configstore/node_modules/make-dir/index.js Module not found: Error: Can't resolve 'fs' in '/Users/xxx/xxxx/node_modules/configstore/node_modules/make-dir' ERROR in ./node_modules/google-auth-library/build/src/auth/googleauth.js Module not found: Error: Can't resolve 'fs' in '/Users/xxx/xxxx/node_modules/google-auth-library/build/src/auth' ERROR in ./node_modules/google-p12-pem/build/src/index.js Module not found: Error: Can't resolve 'fs' in '/Users/xxx/xxxx/node_modules/google-p12-pem/build/src' ERROR in ./node_modules/graceful-fs/graceful-fs.js Module not found: Error: Can't resolve 'fs' in '/Users/xxx/xxxx/node_modules/graceful-fs' ERROR in ./node_modules/gtoken/build/src/index.js Module not found: Error: Can't resolve 'fs' in '/Users/xxx/xxxx/node_modules/gtoken/build/src' ERROR in ./node_modules/write-file-atomic/index.js Module not found: Error: Can't resolve 'fs' in '/Users/xxx/xxxx/node_modules/write-file-atomic' ERROR in ./node_modules/http-proxy-agent/dist/agent.js Module not found: Error: Can't resolve 'net' in '/Users/xxx/xxxx/node_modules/http-proxy-agent/dist' ERROR in ./node_modules/https-proxy-agent/dist/agent.js Module not found: Error: Can't resolve 'net' in '/Users/xxx/xxxx/node_modules/https-proxy-agent/dist' ERROR in ./node_modules/http-proxy-agent/dist/agent.js Module not found: Error: Can't resolve 'tls' in '/Users/xxx/xxxx/node_modules/http-proxy-agent/dist' ERROR in ./node_modules/https-proxy-agent/dist/agent.js Module not found: Error: Can't resolve 'tls' in '/Users/xxx/xxxx/node_modules/https-proxy-agent/dist'
Thanks!

I'm having the same problem

Hi @noukaza and @Segrelove ,
I am struggling to reproduce this issue. How are you running this code? Also, can you paste your entire code snippet (including how you define path)?

hi @shaffeeullah
firstly you need to create a nuxt js project
npx create-nuxt-app my-app
✨  Generating Nuxt.js project in my-app
Project name: my-app
Programming language: JavaScript
Package manager: Yarn
UI framework: None
Testing framework: None
**Rendering mode: Universal (SSR / SSG)**
**Deployment target: Server (Node.js hosting)**

make sure to select Rendering mode: Universal (SSR / SSG) and Deployment target: Server (Node.js hosting)
if you start the project by typing yarn dev  everything will compile perfectly
now if you install google-cloud/storage
yarn add @google-cloud/storage

and import it anywhere in the project
for example inpages/index.vue
<script>
const {Storage} = require('@google-cloud/storage');
// or import {Storage} from '@google-cloud/storage';
export default {}
</script>

The library is named 'nodejs-storage'. There is no chance, that you will make it work in the browser. child-process is the core node.js module. https://nodejs.org/api/child_process.html

@eagleeye i already know that and that's why i'm using nuxtjs with SSR mode

This sounds like a fun thing with Nuxt that wants to use Webpack bundle even when running on the server side.  I found https://github.com/nuxt-community/dotenv-module/issues/11 which suggested that we could blocklist some Node modules for webpack, and they will magically start working on the Node side of the things. Try this in your nuxt.config.js:
  // Build Configuration: https://go.nuxtjs.dev/config-build
  build: {
    extend (config, ctx) {
        config.node = {
            fs: "empty",
            child_process: "empty",
            net: "empty",
            tls: "empty"
        };
    }
  }

My pages/index.vue that worked:
<script>
const storage = require('@google-cloud/storage');
console.log(storage);
// exports and other stuff here
</script>

Note: we have never tested this library with Nuxt. Consider this to be a "warranty void if seal broken" situation - let us know if anything does not work but fixing stuff might be complicated.

This sounds like a fun thing with Nuxt that wants to use Webpack bundle even when running on the server side.  I found https://github.com/nuxt-community/dotenv-module/issues/11 which suggested that we could blocklist some Node modules for webpack, and they will magically start working on the Node side of the things. Try this in your nuxt.config.js:
  // Build Configuration: https://go.nuxtjs.dev/config-build
  build: {
    extend (config, ctx) {
        config.node = {
            fs: "empty",
            child_process: "empty",
            net: "empty",
            tls: "empty"
        };
    }
  }

My pages/index.vue that worked:
<script>
const storage = require('@google-cloud/storage');
console.log(storage);
// exports and other stuff here
</script>

Note: we have never tested this library with Nuxt. Consider this to be a "warranty void if seal broken" situation - let us know if anything does not work but fixing stuff might be complicated.

Thanks @alexander-fenster for the solution! @noukaza please re-open this or leave a comment if this is still an issue.

Thanks @alexander-fenster for the solution! @noukaza please re-open this or leave a comment if this is still an issue.

oh so you can only use cloud storage in the backend. Nice to know.


fix port BindException

Codecov Report

Merging #5556 into master will decrease coverage by 0.09%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master    #5556     +/-   ##
===========================================
- Coverage     82.77%   82.67%   -0.1%
+ Complexity    11463    11449     -14
===========================================
  Files          1362     1362
  Lines         44497    44497
  Branches       5538     5538
===========================================
- Hits          36831    36790     -41
- Misses         5084     5122     +38
- Partials       2582     2585      +3

Impacted Files
Coverage Δ
Complexity Δ

...in/java/io/crate/lucene/match/CrateRegexQuery.java
43.47% <0%> (-34.79%)
4% <0%> (-4%)

...o/crate/analyze/SafeExpressionToStringVisitor.java
83.33% <0%> (-16.67%)
7% <0%> (-1%)

...in/java/io/crate/data/CollectingBatchConsumer.java
69.23% <0%> (-15.39%)
4% <0%> (-1%)

...ava/io/crate/planner/node/dql/join/NestedLoop.java
82.85% <0%> (-11.43%)
16% <0%> (-2%)

.../java/io/crate/blob/TransportDeleteBlobAction.java
75% <0%> (-5%)
4% <0%> (-1%)

...io/crate/protocols/postgres/types/VarCharType.java
87.5% <0%> (-4.17%)
9% <0%> (-1%)

...te/blob/pending_transfer/PutHeadChunkRunnable.java
76.71% <0%> (-4.11%)
12% <0%> (-2%)

...transport/executionphases/ExecutionPhasesTask.java
90.82% <0%> (-3.67%)
24% <0%> (ø)

...in/java/io/crate/breaker/RamAccountingContext.java
81.66% <0%> (-3.34%)
20% <0%> (-2%)

...ration/collect/collectors/LuceneBatchIterator.java
86.95% <0%> (-3.27%)
36% <0%> (-1%)

... 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 3d7200c...c73bb81. Read the comment docs.


Docs: broken link to "Set up DBT models & orchestrate DBT runs" tutorial

Describe the bug
From the Tutorials page, the link to "Set up DBT models & orchestrate DBT runs" is broken.
To Reproduce
Steps to reproduce the behavior:

Go to Tutorials
Click on Set up DBT models & orchestrate DBT runs.
The link (https://docs.mage.ai/integrations/dbt-models) does not exist and falls back to Overview page

Expected behavior
Tutorial page has the correct link (https://docs.mage.ai/tutorials/setup-dbt) instead.
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: [MacOS]
Browser [Chrome]
Version [Version 113.0.5672.126 (Official Build) (arm64)]

Smartphone (please complete the following information):
n/a
Additional context
Add any other context about the problem here.

Will fix ASAP

Fixed!

Fixed!

Thanks for the quick turn around. Was the link in README.md also fixed as well?  I was going to submit a PR but you beat me to it, thanks again.


egk goerli

I've used https://github.com/ethereum/staking-deposit-cli/files/10709746/staking_deposit-cli-d83c312-linux-amd64.tar.gz

Will investigate this later today. Appears that the GitHub action is not evaluating the conditional correctly. The submission looks valid.

I have manually reviewed the submission and found it to be valid. I investigate how to fix the GitHub actions that are causing a false alarms for goerli.


additionalProperties in OpenAPI 3.0 Spec?

Hi,
in my OpenAPI 2.0 version of swagger-autogen I use additionalProperties. I could not find any corresponding component in the swagger-autogen 3.0 Docs.
Is there any paralleling component for additionalProperties for swagger-autogen on OpenAPI 3.0?

I found that we can still use the '@definitions' and for these cases where we need the additionalProperties format.


Updates with joins in postgres

when compiling to mysql there is a clear syntax for joining to an update. However, in postgres the syntax for doing this is update...from, which from what I understand knex can't really support, because there can only be one primary table. is it possible to compile this ;
knex.from('table').update({a:knex.raw('othertable.a')}).join('othertable', 'othertable.b', 'table.b')

to this;
update table set a = othertable.a from othertable where othertable.b = table.b

particularly when the knex instance is for postgres? I understand that the syntax restricts us to inner joins, so limiting the join methods that work to innerJoin would be reasonable, but at the moment this just silently fails to add anything related to the join, and trying to add a from clause just changes the primary table.

knex doesn't support from clause for updates / deletes etc. it works only for select.
However you can do something this (there might be some syntax errors.. didn't run the query):
knex.from('table').update({
  a: knex('othertable').select('a').where('b', knex.raw('??', ['table.b'])
})

But from the issue I referenced and from here, knex does support joins on updates. what I'm asking for is particularly for postgres for that join to be compiled into a from, because that is the syntax postgres expects when using secondary tables on an update. I am not asking for any changes to the from function in knex, just that we use the join functions in knex to support postgres update from syntax.

@elhigu  particularly what I'm worried about is if we have more than one column that is being updated;
knex.from('table').update({
  a:knex.raw('othertable.a'),
  c:knex.raw('othertable.c')
}).join('othertable', 'othertable.b', 'table.b')

doing this as two subqueries would be really inefficient.

Probaly both are equally efficient. You can check query plan to if there is any difference. Usually postgresql wont do multiple subqueries in that case, if subqueries are the same and only selected column is changed. Databases work mysterious ways many times it impossible to tell from query syntax how efficient it will be.
I'm pretty sure there is already feature request in knex issues to support from clause for updates for postgresql, if not please open one. I haven't heard that anyone has been planning to implement it though :(

looks like that is here. Would it be unreasonable for me to try? I don't know what the culture around pushing code is for this.

All pull requests are very welcome! Requirements are listed in CONTRIBUTING.md. Basically PR should have code, tests for it (including integration test that makes sure that query actually does what it is supposed to do) and link to PR to documentation repo. Then I or someone else review the code and ask for changes if there is need to do some stuff in a different way and when everything looks good reviewer merge PR to master.

good to know! thank you.

This worked for me
	await knex( 'managers' ).update( {
		address: knex( 'clients' ).select( 'address' ).where( 'id', knex.raw( '??', ['managers.clientId'] ) ),
	} );

This works perfect:
const ratingsSubquery = model('rating').join('...').avg('..').as('r');

       knex('user')
        .update({ rating: model.raw('r.avg from ?', ratingsSubQuery) })
        .where('r.user_id', model.ref('user.id'));

Being able to substitute knex-built subqueries into raw queries is such a fantastic feature!