I'm Microsoft Research Institute. When I add a custom backbone, I will be prompted with an error of no registration

Thanks for your error report and we appreciate it a lot.
Checklist

I have searched related issues but cannot get the expected help.
I have read the FAQ documentation but cannot get the expected help.
The bug has not been fixed in the latest version.

Describe the bug
A clear and concise description of what the bug is.
Reproduction

What command or script did you run?

A placeholder for the command.

Did you make any modifications on the code or config? Did you understand what you have modified?
What dataset did you use?

Environment

Please run python mmdet/utils/collect_env.py to collect necessary environment information and paste it here.
You may add addition that may be helpful for locating the problem, such as

How you installed PyTorch [e.g., pip, conda, source]
Other environment variables that may be related (such as $PATH, $LD_LIBRARY_PATH, $PYTHONPATH, etc.)

Error traceback
If applicable, paste the error trackback here.
Traceback (most recent call last):
File "./tools/train.py", line 189, in
main()
File "./tools/train.py", line 162, in main
test_cfg=cfg.get('test_cfg'))
File "/home/kny/code/cell/mmdet/models/builder.py", line 58, in build_detector
cfg, default_args=dict(train_cfg=train_cfg, test_cfg=test_cfg))
File "/home/kny/anaconda3/envs/mmd/lib/python3.7/site-packages/mmcv/utils/registry.py", line 212, in build
return self.build_func(*args, **kwargs, registry=self)
File "/home/kny/anaconda3/envs/mmd/lib/python3.7/site-packages/mmcv/cnn/builder.py", line 27, in build_model_from_cfg
return build_from_cfg(cfg, registry, default_args)
File "/home/kny/anaconda3/envs/mmd/lib/python3.7/site-packages/mmcv/utils/registry.py", line 55, in build_from_cfg
raise type(e)(f'{obj_cls.name}: {e}')
KeyError: "CascadeRCNN: 'EfficientNet is not in the models registry'"
ERROR:torch.distributed.elastic.multiprocessing.api:failed (exitcode: 1) local_rank: 0 (pid: 51212) of binary: /home/kny/anaconda3/envs/mmd/bin/python
Traceback (most recent call last):
File "/home/kny/anaconda3/envs/mmd/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/home/kny/anaconda3/envs/mmd/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/home/kny/anaconda3/envs/mmd/lib/python3.7/site-packages/torch/distributed/launch.py", line 193, in
main()
File "/home/kny/anaconda3/envs/mmd/lib/python3.7/site-packages/torch/distributed/launch.py", line 189, in main
launch(args)
File "/home/kny/anaconda3/envs/mmd/lib/python3.7/site-packages/torch/distributed/launch.py", line 174, in launch
run(args)
File "/home/kny/anaconda3/envs/mmd/lib/python3.7/site-packages/torch/distributed/run.py", line 713, in run
)(*cmd_args)
File "/home/kny/anaconda3/envs/mmd/lib/python3.7/site-packages/torch/distributed/launcher/api.py", line 131, in call
return launch_agent(self._config, self._entrypoint, list(args))
File "/home/kny/anaconda3/envs/mmd/lib/python3.7/site-packages/torch/distributed/launcher/api.py", line 261, in launch_agent
failures=result.failures,
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
A placeholder for trackback.

Bug fix
If you have already identified the reason, you can provide the information here. If you are willing to create a PR to fix it, please also leave a comment here and that would be much appreciated!

KeyError: "CascadeRCNN: 'EfficientNet is not in the models registry'"
you should add EfficientNet in init.py and more details you can refer to https://mmdetection.readthedocs.io/en/v2.18.1/tutorials/customize_models.html

KeyError: "CascadeRCNN: 'EfficientNet is not in the models registry'"
you should add EfficientNet in init.py and more details you can refer to https://mmdetection.readthedocs.io/en/v2.18.1/tutorials/customize_models.html

I do, an err  occur
File "/home/kny/code/cell/mmdet/models/necks/fpn.py", line 153, in forward
assert len(inputs) == len(self.in_channels)

Hello, I got the same error:
sys.platform: linux
Python: 3.7.12 | packaged by conda-forge | (default, Oct 26 2021, 06:08:53) [GCC 9.4.0]
CUDA available: True
GPU 0: Tesla T4
CUDA_HOME: /usr/local/cuda
NVCC: Build cuda_11.0_bu.TC445_37.28845127_0
GCC: gcc (Debian 8.3.0-6) 8.3.0
PyTorch: 1.10.1+cu111
PyTorch compiling details: PyTorch built with:
  - GCC 7.3
  - C++ Version: 201402
  - Intel(R) Math Kernel Library Version 2020.0.0 Product Build 20191122 for Intel(R) 64 architecture applications
  - Intel(R) MKL-DNN v2.2.3 (Git Hash 7336ca9f055cf1bfa13efb658fe15dc9b41f0740)
  - OpenMP 201511 (a.k.a. OpenMP 4.5)
  - LAPACK is enabled (usually provided by MKL)
  - NNPACK is enabled
  - CPU capability usage: AVX512
  - CUDA Runtime 11.1
  - NVCC architecture flags: -gencode;arch=compute_37,code=sm_37;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_80,code=sm_80;-gencode;arch=compute_86,code=sm_86
  - CuDNN 8.0.5
  - Magma 2.5.2
  - Build settings: BLAS_INFO=mkl, BUILD_TYPE=Release, CUDA_VERSION=11.1, CUDNN_VERSION=8.0.5, CXX_COMPILER=/opt/rh/devtoolset-7/root/usr/bin/c++, CXX_FLAGS= -Wno-deprecated -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -fopenmp -DNDEBUG -DUSE_KINETO -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DSYMBOLICATE_MOBILE_DEBUG_HANDLE -DEDGE_PROFILER_USE_KINETO -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-sign-compare -Wno-unused-parameter -Wno-unused-variable -Wno-unused-function -Wno-unused-result -Wno-unused-local-typedefs -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-psabi -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Wno-stringop-overflow, LAPACK_INFO=mkl, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, TORCH_VERSION=1.10.1, USE_CUDA=ON, USE_CUDNN=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=ON, USE_MPI=OFF, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON,

TorchVision: 0.11.2+cu111
OpenCV: 4.5.5
MMCV: 1.4.4
MMCV Compiler: GCC 7.3
MMCV CUDA Compiler: 11.1
MMDetection: 2.20.0+ff9bc39

I followed Tutorial 4: Customize Models exactly except for that my mobilenet.py is a duplicate of mobilenet_v2.py. Also I replaced MobileNetV2 with MobileNet in the file. I also added the following line in __init__.py.
from .mobilenet import MobileNet

To test, I replaced MobileNetV2 with MobileNet in configs/yolo/yolov3_mobilenetv2_mstrain-416_300e_coco.py.
Since the new backbone is same as MobileNetV2, I thought I can use the same pretrained model. So I ran the following snippet:
from mmdet.apis import init_detector, inference_detector

config_file = 'configs/yolo/yolov3_mobilenetv2_mstrain-416_300e_coco.py'
# download the checkpoint from model zoo and put it in `checkpoints/`
# url: https://download.openmmlab.com/mmdetection/v2.0/faster_rcnn/faster_rcnn_r50_fpn_1x_coco/faster_rcnn_r50_fpn_1x_coco_20200130-047c8118.pth
#checkpoint_file = 'ckpts/faster_rcnn_r50_fpn_1x_coco_20200130-047c8118.pth'
checkpoint_file = 'ckpts/yolov3_mobilenetv2_mstrain-416_300e_coco_20210718_010823-f68a07b3.pth'
device = 'cuda:0'
# init a detector
model = init_detector(config_file, checkpoint_file, device=device)
# inference the demo image
inference_detector(model, 'demo/demo.jpg')

But the following error occurs:
---------------------------------------------------------------------------
KeyError                                  Traceback (most recent call last)
/opt/conda/lib/python3.7/site-packages/mmcv/utils/registry.py in build_from_cfg(cfg, registry, default_args)
     51     try:
---> 52         return obj_cls(**args)
     53     except Exception as e:

~/mmdetection/mmdet/models/detectors/yolo.py in __init__(self, backbone, neck, bbox_head, train_cfg, test_cfg, pretrained, init_cfg)
     20         super(YOLOV3, self).__init__(backbone, neck, bbox_head, train_cfg,
---> 21                                      test_cfg, pretrained, init_cfg)
     22

~/mmdetection/mmdet/models/detectors/single_stage.py in __init__(self, backbone, neck, bbox_head, train_cfg, test_cfg, pretrained, init_cfg)
     31             backbone.pretrained = pretrained
---> 32         self.backbone = build_backbone(backbone)
     33         if neck is not None:

~/mmdetection/mmdet/models/builder.py in build_backbone(cfg)
     19     """Build backbone."""
---> 20     return BACKBONES.build(cfg)
     21

/opt/conda/lib/python3.7/site-packages/mmcv/utils/registry.py in build(self, *args, **kwargs)
    211     def build(self, *args, **kwargs):
--> 212         return self.build_func(*args, **kwargs, registry=self)
    213

/opt/conda/lib/python3.7/site-packages/mmcv/cnn/builder.py in build_model_from_cfg(cfg, registry, default_args)
     26     else:
---> 27         return build_from_cfg(cfg, registry, default_args)
     28

/opt/conda/lib/python3.7/site-packages/mmcv/utils/registry.py in build_from_cfg(cfg, registry, default_args)
     44             raise KeyError(
---> 45                 f'{obj_type} is not in the {registry.name} registry')
     46     elif inspect.isclass(obj_type):

KeyError: 'MobileNet is not in the models registry'

During handling of the above exception, another exception occurred:

KeyError                                  Traceback (most recent call last)
/tmp/ipykernel_2770/1667732121.py in <module>
      8 device = 'cuda:0'
      9 # init a detector
---> 10 model = init_detector(config_file, checkpoint_file, device=device)
     11 # inference the demo image
     12 inference_detector(model, 'demo/demo.jpg')

~/mmdetection/mmdet/apis/inference.py in init_detector(config, checkpoint, device, cfg_options)
     38     config.model.pretrained = None
     39     config.model.train_cfg = None
---> 40     model = build_detector(config.model, test_cfg=config.get('test_cfg'))
     41     if checkpoint is not None:
     42         checkpoint = load_checkpoint(model, checkpoint, map_location='cpu')

~/mmdetection/mmdet/models/builder.py in build_detector(cfg, train_cfg, test_cfg)
     57         'test_cfg specified in both outer field and model field '
     58     return DETECTORS.build(
---> 59         cfg, default_args=dict(train_cfg=train_cfg, test_cfg=test_cfg))

/opt/conda/lib/python3.7/site-packages/mmcv/utils/registry.py in build(self, *args, **kwargs)
    210
    211     def build(self, *args, **kwargs):
--> 212         return self.build_func(*args, **kwargs, registry=self)
    213
    214     def _add_children(self, registry):

/opt/conda/lib/python3.7/site-packages/mmcv/cnn/builder.py in build_model_from_cfg(cfg, registry, default_args)
     25         return Sequential(*modules)
     26     else:
---> 27         return build_from_cfg(cfg, registry, default_args)
     28
     29

/opt/conda/lib/python3.7/site-packages/mmcv/utils/registry.py in build_from_cfg(cfg, registry, default_args)
     53     except Exception as e:
     54         # Normal TypeError does not print class name.
---> 55         raise type(e)(f'{obj_cls.__name__}: {e}')
     56
     57

KeyError: "YOLOV3: 'MobileNet is not in the models registry'"

Restarting my Jupyter Notebook kernel solved the issue. :-)
@xianglei3, I guess your issue is now with your code?

Feel free to create a new issue if you still meet problems


feat(internal): add internal::MergeOptions()

Also changed CheckExpectedOptions to use doxygen-style /** */ comments since it was wrong and looked funny next to MergeOptions() w/ the doxygen-style comments.

This change is

nit: you probably thought about it, but consider Options MergeOptions(Options a, Options b).

I did. Flipped a coin and it landed on the other side. But returning a value is probably a bit nicer, so changed.


Invalid content /en/shelley/get-started/installing-and-running-the-cardano-node/building-the-node-using-nix/

Where does the issue occur?
https://testnets.cardano.org/en/shelley/get-started/installing-and-running-the-cardano-node/building-the-node-using-nix/
Describe the issue
Item 3 shows the wrong command argument, which has an extra "s" on --nix-extra-conf-files
./install-nix.sh --daemon --nix-extra-conf-files nix.conf
Expected changes
A clear and concise description of what you expected to change.
Additional context
Add any other context about the problem here.

this has been updated, thank you for your feedback.

this has been updated, thank you for your feedback.

resolved by https://github.com/cardano-foundation/testnets-cardano-org/pull/437

resolved by https://github.com/cardano-foundation/testnets-cardano-org/pull/437


Amend cAdvisor collector

This PR does three things:

Add a docker_host field that regexp-collects the non-qualified hostname of the API endpoint
Remove the "name" tagk, as it is essentially superfluous vs. docker_id field
Add a config variable "ShortContainerIds" to limit the docker_id field to 12 character container ids, which is what is shown for docker ps command and saves opentsdb tagv working-space (we don't really need those ultra long container ids, do we?)

Before this is merged, I'd really like input from @nickethier on his motivations behind having name and docker_id being distinct tagk's.  Please comment at your convenience, thanks!

The rational behind using the name tagk was for use with kubernetes. K8s embeds some meta data like the pod name and I'd into the container name. See https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/dockertools/docker.go#L216
I believe k8s now uses docker labels so we could do 1 of 2 things if we want to remove name.

If the name starts with the k8s prefix then parse out the k8s attributes as their own tags.
Add an option to enable consuming the docket labels as independent tags.

Thoughts?

/cc @mathpl

I actually have an upcoming PR related to this which I think you could benefit from. The idea is to do a bit of post processing on tags to get the best value out of the collected data independently of a specific collector, it applies for cadvisor generated tags but we also use it for data generated by the snmp collector. Here's an example config file which I think would replicate the behavior you want:
filter = [ 'cadvisor' ]
hostname = 'k8s-1.my.corp'

[[Cadvisor]]
    URL='http://localhost:4194/'

[[TagOverride]]
    CollectorExpr = 'cadvisor'
    [TagOverride.MatchedTags]
        docker_name = 'k8s_(?P<container_name>[^\.]+)\.[0-9a-z]+_(?P<pod_name>[^\.]+)'
        docker_id = '^(?P<docker_id>.{12})'
        host = '^(?P<docker_host>[^\.]+)'
    [TagOverride.Tags]
        name = ''
        docker_name = ''
        provider = 'kubelet'

Which would yields:
{"metric":"container.cpu.usage","timestamp":1451493764,"value":2349620289,"tags":{"container_name":"my-container-name-in-pod","docker_host":"k8s-1","cpu":"12","docker_id":"8d6ecb2a8b2c","host":"k8s-1.my.corp","pod_name":"my-pod-name","provider":"kubelet"}}

I didn't take the time to look at getting dockers labels for tags but I believe pod labels are not applied to containers yet. From my testing they don't show up in the cadvisor api responses.
I agree name could be removed. Do you think this could work for you?

I like where you're going with this pr, @mathpl!  If your PR is accepted then it would really make my changes superfluous.  I'll wait to see where it goes!


Use prettier for code formatting

This PR:

installs prettier and adds Alchemy's configuration file, as well as an ignore file
adds a prettier --check step to the yarn lint workflow that runs in CI
adds a prettier --write step available as yarn format
adds some documentation about how and when to format your code
formats everything using prettier

I went ahead and let it format the markdown, yaml, etc. figuring why not 🤷🏻

Awesome! So stoked to have this up and running here. I love prettier.
One question: do we need to ignore package.json? I have run into situations where prettier will format it, then yarn/npm will reformat it when running install. I don't know if that still happens today, maybe prettier is smarter than that now.
Our .prettierignore internally is pretty small:
package.json
node_modules

Good call. I added some stuff to the .prettierignore and reformatted/rebased accordingly.


Profile styling

Add styling to user profile page

Coverage remained the same at 14.873% when pulling d052c86ac3b6f1e9d34e34e31ba43a931429a125 on profile-styling into 5319cb0d1f3a2c1721e8125c14403b2970a1e48e on master.

Coverage remained the same at 14.873% when pulling f24da48a0df7b9ff5b3ff073f38818a875953315 on profile-styling into 5319cb0d1f3a2c1721e8125c14403b2970a1e48e on master.

Coverage remained the same at 14.873% when pulling 4fb99b01b4a6b35135cec0539c5ead03184cb22c on profile-styling into 5319cb0d1f3a2c1721e8125c14403b2970a1e48e on master.

Coverage remained the same at 14.873% when pulling 8b312c4cfe9c5b3e2e624559bab64169c8dde487 on profile-styling into 5319cb0d1f3a2c1721e8125c14403b2970a1e48e on master.


Change ElectronContainer getMainWindow() to always return the first created window

Fixes #87

We have to pretend there is a concept of a main window in Electron apps by simply returning the first window that is created.

What if the first window was a splash or a login window...?

@psmulovics I'm thinking of removing getMainWindow() completely now and expect user to always use getWindowBy*.  For browser it doesn't work (#42) either.

You can softly demand marking a window the mainwindow somehow?

I'm starting to think the concept of a main window shouldn't even be assumed at the framework level.  It only applies to OpenFin and even there it can be an issue as some apps have an initial main window that is never visible.

As discussed, will provide an api for dev to register a main window and add lifecycle activity events and other features through this registration.  A good use case of this addition is to be able to quit an Electron app when the "main" window is closed.

I want to try and match this behavior on OpenFin and the browser too.  For OpenFin, allow you to specify a different window as main if your current main window is always hidden.


Support non-consecutive node ids

This puts less constraint on what is a valid model. However, Graphs.jl only supports a node list1:n. We could add a mapping dict, but more mapping dicts make the code harder to follow.

Closed in favor of https://github.com/Deltares/Ribasim/issues/694.


Depend on 4.1.1 version of RMQ connection

Thanks for contributing to Logstash! If you haven't already signed our CLA, here's a handy link: https://www.elastic.co/contributor-agreement/

LGTM™

@andrewvc does logstash Gemfile.lock need to be updated before we can upgrade to these newer versions?  I'm having a hard time getting the fixes using logstash-plugin update


Account creation fails when the --logo-url flag is omitted.

Description:
When attempting to create an account without specifying the --logo-url flag, the operation fails because the logo_url field is set as non-nullable. This field should be optional, and account creation should proceed without requiring a logo URL.
Expected Behavior:
The logo_url field should be nullable, allowing account creation even when the --logo-url flag is not provided.
Steps to Reproduce:
Attempt to create an account using the command without the--logo-urlflag.
Observe the failure due to the non-nullable logo_url field.
Suggested Fix: Update the account model to make the logo_url field optional.

Closed by #1167.


[test](jdbc postgresql case)add jdbc test case for postgresql

Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[x] No
[ ] I don't know

Has unit tests been added:

[y] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[x] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[x] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[x] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 35.87 seconds
load time: 485 seconds
storage size:<PHONE_NUMBER>6 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221110110411_clickbench_pr_43408.html

LGTM


create project pages from github issues project proposals

use github issue labels to create project pages. labels like accepted would work for this.
xref: https://github.com/BioEcoOcean/metadata-tracking-dev/issues/6
See
https://github.com/BioEcoOcean/metadata-tracking-dev/blob/0980b1e26640a9539d303510581c75fbfae651bf/.github/workflows/gha_generate_pr.yml#L3-L6
https://github.com/BioEcoOcean/metadata-tracking-dev/blob/0980b1e26640a9539d303510581c75fbfae651bf/.github/workflows/gha_generate_pr.yml#L22-L24
Action would live at https://github.com/mgrover1/hackathon-template-cookiecutter/tree/main/{{cookiecutter.hackathon_repo_name}}/.github/workflows so new repo's would have it available.

Something to start with:
name: Create project page and Create Pull Request

on:
  issues:
    types:
      - labeled

jobs:
  auto_new_resource_add_pr:
    if: contains(github.event.issue.labels.*.name, 'accepted')
    runs-on: ubuntu-latest
    steps:
      - name: Check Out Repository
        uses: actions/checkout@v4

      - name: Setup Micromamba ${{ matrix.python-version }}
        uses: mamba-org/setup-micromamba@v2
        with:
          environment-file: environment.yml
          init-shell: bash

      - name: Parsing issue, generate markdown
        shell: bash -l {0}
        run: python generate_pr_from_issue.py
      - name: Create Pull Request
        uses: peter-evans/create-pull-request@v7
        with:
          token: ${{ secrets.GITHUB_TOKEN }}
          commit-message: "Create new project page via GitHub Actions"
          committer: GitHub<EMAIL_ADDRESS>          author: ${{ github.actor }} <${{ github.actor<EMAIL_ADDRESS>          branch: new_project_#${{ github.event.issue.number }}
          title: "new project PR by GHA based on issue #${{ github.event.issue.number }}"
          body: |
            A project that is contributed by the user through issue submission. It has triggered a GitHub Action workflow that generate this PR. Refer to issue #${{ github.event.issue.number }}.
            Merging this PR will close #${{ github.event.issue.number }}.
          delete-branch: true
          labels: new project

myst allows for glob parameters in TOC description.
https://github.com/mgrover1/hackathon-template-cookiecutter/blob/60c97b2e6bb73dac746fcec74bd52fd59c11375e/{{cookiecutter.hackathon_repo_name}}/myst.yml#L13-L18
Ideally, this action would read from the issue, generate a .md, stick it in a projects/ folder. Then, myst should automatically pick it up and build into the website.

closed with #20


Remove duplicates without losing only copy? Update filenames for dupes from all providers without deletion?

Apologies if this is already documented somewhere, but I'm looking to be able to do the following:

Update existing files with new names as their tags are updated from providers (eg. when an unnamed character becomes named, etc.)
Use the same naming convention that is currently being used per site (I don't want them all to use tags from a single provider, I want each provider to use their own tags) [As a result I doubt the "Rename existing images" feature will work as that uses a single provider to derive all tags with which to rename files]
Dupes are allowed across different providers, but NOT within the same provider

My naming convention is: %search%/%websitename%/%date:format=yyyy-MM-dd hh.mm.ss% - %character% - %copyright% - %md5%.%ext%
Currently I have a bunch of dupes due to files having their tags updated, but I'm noticing that some art is actually being removed so I can't simply delete + redownload things, otherwise I'd be losing the files that are deleted from the providers.
So far I've tried a software called dupeGuru, but it's random whether it deletes the dupes with up-to-date filenames or the dupes with old filenames. It does me no good if it deletes the dupes with updated filename since those will simply redownload.
The way I have it set up is I simply run my download list every so often to update my folders with new content. Is there an easier way to go about updating my folders? I couldn't find instructions on how to use "Monitors" so I haven't touched that so far.

Related: #2000


Add Azure Log Analytics Connection

Issue Type: Feature Request
Would be awesome if we could create an azure sentinel log analytics workspace connection.

+1 on this.  This is a great little tool and I have been using it for Kusto Detective Agency! We ingest logs at work into LA/Sentinel and I'd love to be able to query those without opening up sentinel sometimes.
You can technically add AI/LA workspaces to azure data explorer.. but our environment we can't create those clusters. For Kusto Detective Agency I it seems like you should be able to also connect to these sources/clusters directly.
Query data in Azure Monitor using Azure Data Explorer explains how you can connect to a LA workspace which likely works - it's basically this URL:
https://ade.loganalytics.io/subscriptions//resourcegroups//providers/microsoft.operationalinsights/workspaces/
everything after https://ade.loganalytics.io is just the resource ID of the Log Analytics workspace. It seems like this would be possible. I tried but there's clearly some error checking going on here that's being triggered


hard triplet convergence

I use triple loss between data of two modalities to reduce the distance between different modalities of the same class and increase the distance between different modalities  of different class. But when I use batch_all loss, the valid set loss has not changed; now using hard_loss, the valid set loss still has not changed. What is the reason? I found some answers that triplet is difficult to converge. What do you do to deal with triplet loss convergence?

why u closed this issue
---Original---
From: "Joakim @.>
Date: Sat, Sep 24, 2022 16:10 PM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [NegatioN/OnlineMiningTripletLoss] hard triplet convergence(Issue #16)
Closed #16 as completed.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Because I don't really have a good answer for you, and it's not strictly related to the library.


POS GO freezing when barcode scanning

Please list the package(s) involved in the issue, and include the version you are using
retail-ui-extensions v1.7.0
Describe the bug
When using the Scanner API on a POS UI Extension app.
When the scanner is used to scan a barcode, the Shopify POS GO device freezes.
The merchant reports that when this happens the scanner turns off and the device had a popup that said "restart device to use scanner".
Steps to reproduce the behavior:

Create a JavaScript POS UI Extension and deploy to POS GO device
Subscribe to the scanner api.scanner.scannerDataSubscribable.subscribe
Load the Camera Scanner Component if there is a camera source
Attempt to scan a barcode
POS Go device freezes

Expected behavior
POS Go device should support scanning barcodes without freezing or device errors.
Additional context
I added monitoring to capture what page the user is on and any possible exceptions etc and it hasn't reported any so I believe this is a lower level issue with either the scanner library or POS GO device.

This was caused by rendering the camera scanner, without checking if there was a camera source. I'll close the bug as working as intended.
Would it be possible for the CameraScanner to not crash the device if that's the case?

This was caused by rendering the camera scanner, without checking if there was a camera source. I'll close the bug as working as intended.
Would it be possible for the CameraScanner to not crash the device if that's the case?


Update alpine, golang, gosu, gotask to latest versions

Describe the pull request
Updating alpine, golang, gosu and gotask.
My initial problem is ca-certficates not being up to date so a checkout from a git repository using letsencrypt is failing:
2023/11/11 23:37:59 [ INFO] ASoulDocs 1.0.0+dev
2023/11/11 23:37:59 [TRACE] Reloading https://repos.fbpx.io/chix/docs.git...
2023/11/11 23:37:59 [TRACE] Cloning https://repos.fbpx.io/chix/docs.git...
2023/11/11 23:37:59 [FATAL] [...ig/asouldocs/internal/cmd/web.go:47 runWeb()] Failed to init store: reload: clone "https://repos.fbpx.io/chix/docs.git": exit status 128 - Cloning into 'data/docs'...
fatal: unable to access 'https://repos.fbpx.io/chix/docs.git/': SSL certificate problem: self signed certificate

For reference:
Docker Golang Alpine Image:
https://hub.docker.com/_/golang/tags?page=1&name=alpine
Gotask releases:
https://github.com/go-task/task/releases
Gosu releases:
https://github.com/tianon/gosu/releases
Link to the issue:
Checklist

[ x] I agree to follow the Code of Conduct by submitting this pull request.
[ x] I have read and acknowledge the Contributing guide.
[ x] I have added test cases to cover the new code.

Closing, the update is not solving my problem.


Join using column selection error

Steps to reproduce the behavior (Required)
CREATE TABLE t0 (
v1 bigint DEFAULT NULL,
v2 bigint DEFAULT NULL,
v3 bigint DEFAULT NULL
)

select * from t0 x,t0 y inner join t0 z using(v1)

Expected behavior (Required)
Translate to select * from (select * from t0 x,t0 y) t inner join t0 z on t.v1 = z.v1
Analyze Error : Column 'v1' is ambiguous
Real behavior (Required)
Translate to select * from t0 x,t0 y inner join t0 z on y.v1 = z.v1
StarRocks version (Required)
Master

Passed validation,close this issue.
mysql> select * from t0 x,t0 y inner join t0 z using(v1);
ERROR 1064 (HY000): Column 'v1' is ambiguous


fix: Take care of clientlaunch.d include on Suse

The only real usable Suse package is this: https://software.opensuse.org/download.html?project=home%3Ajochenbecker&package=xymon-client
However it misses to include clientlaunch.d into clientlaunch.cfg, so configured monitors are not picked up.
This PR changes that, by including it for Suse and making it optional for other OS.

#9 should be merged first and then merged into this one to fix the failing kitchen tests...
Please go there first :)


picture in paper

hello, authors. what you have done in paper is really impressive, it is very useful for my study. And i am wondering how to make the network image in your paper, if it is handy for you.Thanks!

Hi, thank you for your interest in our work! We use PowerPoint to draw network images.


Adding breaking change label to container

Summary
It checks and adds the breaking-change label to the container that is created by the build-container action.
It also adds a label with the commit-hash to the container.

Release Note

Documentation

Example of a build with this configuration:

Do you think we can merge it? @cpanato @haydentherapper


Prepare/1.4.2

Added 2 commits to backport the changes to translations and view templates from the upcoming SDK 1.5.2.
Those changes are the same as the changes between 1.5.1 and 1.5.2.

Additonal commits reviewed. Looks good to me.


cleanup workspace service generator AST parsing

In #64, we added some AST tree parsing to rewrite the serverless.common.ts file during generators. Would be nice to clean this up somehow and make it a bit less ugly and more resilient to future-proofing.
Thanks to @ktrz for the initial help with this effort!

@ktrz suggested that https://github.com/phenomnomnominal/tsquery might be a suitable solution for cleaning up the implementation IF it can allow for manipulation of the returned node. Needs some investigation to confirm.

Digging into tsquery, it doesn't seem like a viable option for manipulation. However, I did come across https://github.com/dsherret/ts-morph/tree/latest/packages/ts-morph that does seem to support query and manipulation of the TypeScript AST. Going to experiment with this next time I look into this issue.

Talked to Colum Ferry about this - he suggested just reading the file in as a string then using ts-query to query and manipulate as a string rather than tree parsing the file.


You get turbo-deleted after dying in the recycler.

I just delete the recycler, lol

Fixed by #2882

Fixed by #2882


[Cherry-pick][Enhancement] Add sample size to session var when getting hive partition statistics

… statistics
What type of PR is this：

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
https://github.com/StarRocks/starrocks/pull/12700
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

starrocks_be_unittest succeeded.

run starrocks_fe_unittest

run starrocks_tscancode


Moves Discord Command parsing to Load phase from init phase

The skript parser calls init when parsing the structures for the first time, but before the structures are actually loaded. So because CommandFactory.add() uses SkriptUtils.loadCode(trigger, CommandEvent.class) when creating the CommandObject it causes the trigger code to be loaded before any function references have been registered (as that happens in the preload phase.
Fixes https://github.com/DiSkyOrg/DiSky/issues/173

oops

LGTM, thanks for your contribution! ❤


Can't access any pins above pin 29 (counting from 0)

On the RP2040, I have 40 total gpio pins, but bank0 only has pins 0 through 29 in it. How can I access pins above this? I need to do this for some pimoroni goodies that use pins 30+. Sorry for the bother!

Hi @ramenspazz!
I see you already closed the ticket, so I guess you found the answer yourself.
In case somebody has the same question and finds the ticket: The RP2040 only has 30 "normal" GPIO pins, the pins 0-29 in bank 0 that you already found.
In addition, there are 6 QSPI pins that are usually used for flash access. On a hypothetical device not using any flash, they could be used as additional GPIO pins. I don't know of any of-the-shelf boards using such a setup. If you know one, please tell us!

For the record: I'm not aware of any off-the-shelf boards either. I pulled the flash chip off an Adafruit Feather RP2040 [which, at the time, had the largest flash chip I could find on an off-the-shelf board] and soldered magnet wires to the pads when I was testing my GPIO code.


Logger overloads generated by T4

Great improvement in code quality, the logger methods for the six levels (Trace, Debug, Info etc) are now generated with a T4 template.
This will reduce the code of lines that should be maintained and guarantees the consistency between the overloads. The lines of code in the Logger class reduces from ~2000 to ~500 + ~300 (T4 template)
T4 templates are run build time and the T4 generator is built in VIsual Studio 2012+
The output is with compared with a text diff and nothing has changed in the signature of the methods (= the same methods, the same parameter names, the same attributes)
PS: there was only 1 change, beside some spaces, the code of Error<TArgument> was inconsistent. This is now fixed. (see screenshot, left=old, right=new)

Note did this change to easily implement #431 in the near future.

Probably the T4 is too fancy to handle.
Issue 1
The "sync projects" corrupts the .csproj files. (NLog.proj /t:SyncProjectItems)
before
    <Compile Include="Logger1.cs">
      <AutoGen>True</AutoGen>
      <DesignTime>True</DesignTime>
      <DependentUpon>Logger.tt</DependentUpon>
    </Compile>

after
    <Compile Include="Logger1.cs" />

Issue 2
The unit test SourceCodeTests.VerifyNamespacesAndClassNames cannot handle this. It's convenient to only add the template code in the template file. So another file is generated with the Logger class. This is no problem, because for this case Microsoft gave us partial classes.
To bad this unit test is so picky.

PR is ready for merge

When can we expect a new release with the exception logging fix?

2 June
See https://github.com/NLog/NLog/milestones


extract.js - pretty mode should sort properties alphabetically

I disagree.  extract.js is included to prove the library works, and it works as such.
These 'value-add' features should be are for another project.
I feel this is a back-end library and should be for the protocol and documentation only.

In order for people working on other projects to leverage the library fully, it needs to make deciphering the replays content as easy as possible. The documentation is part of that, but reading extracted files manually to get a feel of them is another.
If someone just wants to dump data to be exploited elsewhere, not using the --pretty option outputs a one-line file with a direct JSON representation of the data.
If someone wants to have a manual look at the inside of a file, they can add the --pretty option to add new lines and indent. The original library also sorted the properties alphabetically, I suppose for readability reasons. As the --pretty option is not intended for optimized code but for debugging and exploration in the first place, it has all it's place here.

Done 8204114e35a059d3d6069cc3f63a42cd843e0a7d.


WIP-- Updates for Elasticsearch 2.4

This covers the changes in cfgov-refresh needed for ES 2.4, with a few incidental extra's:
It's worth noting, there will be a PR for the 'knowledgebase' package, with some minor indexing tweaks.
Additions

Docker-compose file that spins up MySQL 5.7 and Elasticsearch 2.4, for local development purposes.

Removals

the 'pages' sheerlike indexer (and the SHEER_PROCESSORS setting entirely)

Changes

allow sheerlike to proceed when there's not a SHEER_PROCESSORS setting.
updates the 'elasticsearch' and 'django-haystack' packages

Testing

coming soon

Notes

Todos

Checklist

[ ] PR has an informative and human-readable title
[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the front end playbook
[ ] Passes all existing automated tests
[ ] New functions include new tests
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated
[ ] Reviewers requested with the Assignee tool :arrow_right:

Docker-compose file that spins up MySQL 5.7 and Elasticsearch 2.4, for local development purposes.

if you squint, it's like docker-compose.yml isn't even there!

knowledgebase changes are at: [GHE]/CFPB/knowledgebase/pull/213

After some internal discussion, it seems like we should move forward with 2.3 for now.


fs/mnemofs: Fix extra log unused value error.

Fix the unused value error for when extra logs are OFF.
Summary
This PR fixes the unused value error when extra logs are configured to be OFF in mnemofs. This issue occurs because initially the MFS_EXTRA_LOG was defined to be nothing when configured OFF, but configured to be finfo when turned on.
This meant when it was OFF, the contents inside the () were still present, but without the macro wrapper, which caused the compilation error.
Impact
The users can now turn OFF the extra logs without compilation errors.
Testing
The error was recognized by this GitHub action.
I confirm that changes are verified on local setup and works as intended:
Build Host(s): OS (Linux), CPU(Intel), compiler(GCC 13).
Target(s): arch(sim), sim:mnemofs.

@xiaoxiang781216 Here's the CI fix to #14445.


Enable Limited Cache

Description
Changes proposed in this pull request:

Enable limited cache.

Related issue(s)

/test pull-btp-manager-build

@ralikio that was wrong place to be updated


Describe output is empty?

Hello,
I updated to v0.4.12 and tried changing my format to '%describe%%-branch%%-dirty%' but I get output -slave-dirty?

Can you show me the output from both git describe and git describe --tags at the command line?

I get 1.0.3-617-g51de158 and 1.0.3-617-g51de158 respectively.

Looks like there was a problem with publishing. Please try again with 0.4.13?

0.4.13 fixes the output!

Cool, thanks for the report, and sorry for the trouble!


Add synchronization in deactivating users.

Currently there is no synchronization between users table and deactivated users table ,when admin deactivates a user from Users table they have to reload the page for it to show in Deactivated users table. Similarly if they reactivate a user from Deactivated users table it is not shown in Users table without reloading the page.
https://github.com/zulip/zulip/assets/91622060/d71c89c7-561e-446e-a8eb-6ba3ece636d4

CZO thread

@zulipbot claim

@shubham-padia did this get fixed as part of merging the panels? If so, we should close this and #29926.

Yes, this has been fixed as part of merging the panels. Should be good to close.


How to do VQA task by image url with ?

I can use "vis_processor" method to get the embedding of the image manually(through url)  on , like the method used  in .
(refer: https://huggingface.co/internlm/internlm-xcomposer2-7b).
However, I tried the same way on , it doesn't work.
could you give some examples to solve the issue?
@panzhang0212  @yhcao6

https://github.com/open-compass/VLMEvalKit/blob/main/vlmeval/vlm/xcomposer/xcomposer2_4KHD.py#L60
you could define the text and image, and the image resolution freely with this function, this repo also supports many mainstream VQA benchmarks.


⚠ Jenkins Plugins Artifactory has degraded performance

In 9e426fb, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 2576 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 2d5fa32.


[cloud_functions]: Getting DEADLINE_EXCEEDED but no trace of the call on the backend

Is there an existing issue for this?

[X] I have searched the existing issues.

Which plugins are affected?
Cloud Functions
Which platforms are affected?
Android
Description
We are happy users of cloud_functions SDK but sometimes it happens that the library just stops executing calls to callable functions, even though:

it was working just fine few minutes before
Firebase Auth token is valid
other users can access the function just fine, even from the same network

The error thrown is just DEADLINE_EXCEEDED after the specified time
I/flutter (15750): [CloudFunctionsClient] [firebase_functions/deadline-exceeded] DEADLINE_EXCEEDED
I/flutter (15750): [CloudFunctionsClient]
I/flutter (15750): [CloudFunctionsClient] #0      StandardMethodCodec.decodeEnvelope (package:flutter/src/services/message_codecs.dart:648:7)
I/flutter (15750): [CloudFunctionsClient] #1      MethodChannel._invokeMethod (package:flutter/src/services/platform_channel.dart:334:18)
I/flutter (15750): [CloudFunctionsClient] <asynchronous suspension>
I/flutter (15750): [CloudFunctionsClient] #2      MethodChannelHttpsCallable.call (package:cloud_functions_platform_interface/src/method_channel/method_channel_https_callable.dart:22:24)
I/flutter (15750): [CloudFunctionsClient] <asynchronous suspension>
I/flutter (15750): [CloudFunctionsClient] #3      HttpsCallable.call (package:cloud_functions/src/https_callable.dart:49:37)
I/flutter (15750): [CloudFunctionsClient] <asynchronous suspension>
I/flutter (15750): [CloudFunctionsClient] #4      CloudFunctionsClient.appLaunch (package:cloud_functions_client/src/cloud_functions_client.dart:775:22)
I/flutter (15750): [CloudFunctionsClient] <asynchronous suspension>
...
I/flutter (15750): [CloudFunctionsClient]
I/flutter (15750): [CloudFunctionsClient] #0   StandardMethodCodec.decodeEnvelope (package:flutter/src/services/message_codecs.dart:648:7)
I/flutter (15750): [CloudFunctionsClient] #1   MethodChannel._invokeMethod (package:flutter/src/services/platform_channel.dart:334:18)
I/flutter (15750): [CloudFunctionsClient] #2   <asynchronous suspension>
I/flutter (15750): [CloudFunctionsClient] #3   MethodChannelHttpsCallable.call (package:cloud_functions_platform_interface/src/method_channel/method_channel_https_callable.dart:22:24)
I/flutter (15750): [CloudFunctionsClient] #4   <asynchronous suspension>
I/flutter (15750): [CloudFunctionsClient] #5   HttpsCallable.call (package:cloud_functions/src/https_callable.dart:49:37)
I/flutter (15750): [CloudFunctionsClient] #6   <asynchronous suspension>
I/flutter (15750): [CloudFunctionsClient] #7   CloudFunctionsClient.appLaunch (package:cloud_functions_client/src/cloud_functions_client.dart:775:22)
I/flutter (15750): [CloudFunctionsClient] ⛔ appLaunch failed

Reproducing the issue
It's quite tricky to reproduce the issue, it may happen during debugging, but when it occurs it's just difficult to capture any debug traces outside of the above exception.
My implementation typically is quite simple
      final user = firebaseAuth.currentUser;
      if (user == null) {
        throw Exception('User is not authenticated');
      }

      // check if token is valid
      final tokenResult = await user.getIdTokenResult();
      if (tokenResult.token == null) {
        throw Exception('User token is not valid');
      }

      final result = await functions
          .httpsCallable(
        'nameOfTheFunction',
        options: HttpsCallableOptions(timeout: const Duration(seconds: 30)),
      )
          .call<Map<String, dynamic>>(
        {
          'appBuild': appBuild,
          'userAgent': userAgent,
        },
      );

Firebase Core version
2.31.1
Flutter Version
3.24.4
Relevant Log Output
No response
Flutter dependencies

Expand Flutter dependencies snippet

Dart SDK 3.5.4
Flutter SDK 3.24.4
visible_app 24.11.3

dependencies:

- cloud_functions_client 1.0.0+1 [cloud_functions equatable firebase_auth flutter json_annotation log watcher]
- cloud_storage_client 1.0.0+1 [equatable file firebase_auth firebase_storage flutter log path rxdart]
- firebase_auth 4.19.6 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_core 2.31.1 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_crashlytics 3.4.18 [firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface flutter stack_trace]
- firebase_messaging 14.9.0 [firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web flutter meta]
- flutter 0.0.0 [characters collection material_color_utilities meta vector_math sky_engine]

transitive dependencies:

- cloud_functions 4.7.5 [cloud_functions_platform_interface cloud_functions_web firebase_core firebase_core_platform_interface flutter]
- cloud_functions_platform_interface 5.5.27 [firebase_core flutter meta plugin_platform_interface]
- cloud_functions_web 4.9.5 [cloud_functions_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins]
- firebase_auth_platform_interface 7.2.7 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 5.11.6 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser meta web]
- firebase_core_platform_interface 5.0.0 [collection flutter flutter_test meta plugin_platform_interface]
- firebase_core_web 2.17.0 [firebase_core_platform_interface flutter flutter_web_plugins meta web]
- firebase_crashlytics_platform_interface 3.6.25 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_dynamic_links 5.4.17 [firebase_core firebase_core_platform_interface firebase_dynamic_links_platform_interface flutter meta plugin_platform_interface]
- firebase_dynamic_links_platform_interface 0.2.6+25 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_platform_interface 4.5.33 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_web 3.8.3 [_flutterfire_internals firebase_core firebase_core_web firebase_messaging_platform_interface flutter flutter_web_plugins meta web]
- firebase_storage 11.7.6 [firebase_core firebase_core_platform_interface firebase_storage_platform_interface firebase_storage_web flutter]
- firebase_storage_platform_interface 5.1.21 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_storage_web 3.9.6 [_flutterfire_internals async firebase_core firebase_core_web firebase_storage_platform_interface flutter flutter_web_plugins http meta web]
- http_multi_server 3.2.1 [async]
- http_parser 4.0.2 [collection source_span string_scanner typed_data]
- http_profile 0.1.0

Additional context and comments
I know that my firebase sdk is quite old compared to the current version, but maybe something comes to your mind that could potentially explain the issue? Do you recall any fixes between 2.31.1 and current version that could resolve it? Migrating to the current version would be a bit inconvenient for us right now.

Hi @orestesgaolin, thanks for the report. I wasn't able to reproduce the issue on my end. It might be related to a timeout, so increasing the timeout could be a potential solution, though I'm not entirely sure. You might also find it helpful to check out this Reddit thread, as some of the suggested solutions there might address your issue.


Changes to support CUDA 7.0

This requires llvmlite with llvm 3.6 even though CUDA 7.0 uses LLVM 3.4.

Is there a separate LLVM 3.6 branch for Numba we need to merge along with this PR?

No, this uses https://github.com/numba/llvmlite/tree/llvm3.6

LLVM 3.6 is now the default in llvmlite master.

should this PR also bump the conda requirements for the cudatoolkit?

Do you mean the conda build requirements?  It should grap the latest.  No version was specified.
https://github.com/numba/numba/blob/master/buildscripts/condarecipe.jenkins/meta.yaml#L35


What guarantees for partially unspecified code?

If every type were either @Nullable or @NonNull, fully sound checking would be solvable by direct extension of the rules of the Java type system ("not less sound than Java itself" :) ). In the presence of @NullnessUnspecified or legacy code we have discussed many examples, but I'm not sure we're striving for the same level of guarantees.
After re-checking how Eclipse performs in this respect, I should say we are using a number of "common-sense" heuristics, but we (obviously) cannot guarantee that a warning free program is free of NPE.
The story towards users is: as long as unspecified types are involved, analysis is "best-effort". To get stronger guarantees, @NonNullByDefault must be used everywhere. (That's why we optionally raise a warning when any package is not annotated @NonNullByDefault).
The literature about gradual typing (which is in a way what we are trying here) has approaches with much more specific goals than the above. E.g., in "Well-typed programs can’t be blamed" the authors present a system, where blame assignment in case of an error will always point fingers towards the untyped part of the program. I seem to recall, however, that their approach does not cover mutable state (correct me if I'm wrong). Maybe other research about gradual typing will come in handy?
In my understanding, shared access to mutable state is the core of the problems we are facing here. Any object that is referenced both from specified and unspecified portions of the program will likely allow the unspecified portion to modify the object in ways that will break the specified portion. If we raise warnings for every data flow creating such shared access, then we will raise a lot of warnings, probably more than users would want.
A weaker description of a goal could be: analysis in the presence of unspecified parts is not more unsafe than similar structures with a mix of generics and raw types. This goal should provide a clear picture of what rules to check, but is it a good story to tell users? I'm undecided in this issue.
Do others have a clear and feasible idea of what we can promise regarding a program that is not fully annotated but warning free by our checkers?

Chris, is this issue the right place to track any current design decisions we need to make?

One way to view this is as a duplicate of #115 (except, you know, that #115 came later :)).
This issue did raise more detailed questions, but then the conclusion of #115 was something like "Let's not get into the detailed questions." Or at least it was "Let's not get into the detailed questions more than we already do by defining rules for 'unspecified nullness' in the first place?" I think we have a pretty good story for how tools/users can pick a point on the spectrum from "Well-typed programs can’t be blamed" to "Hope for the best." And if JSpecify succeeds to the point that someone wants to explore this formally, that would make for an interesting read.


Settings to not save when using DB transactions

Thanks for this great library.
I current have my settings stored in the database.
I am having a problem where I am using a Database transaction, and the setting does not save, it will only save if I do it outside of the transaction.
Is this a limitation with this package that you cannot save settings (in database) using a DB Transaction?
Thanks

Hey! There's nothing in the library that should cause the behavior you're seeing. Are you sure you're simply not committing the transaction?

same issue


Question: With stickiness = false is there still stickiness is a single request?

If stickiness = false, I know that the same db connection will not be used for subsequent requests but I am unclear what the behavior is during a single request.
For example:
user = User.find(1) #would go to some reader
user.posts.create(:text, "hello") #master
posts = user.posts.all #would this go to master or a reader?

So would user.posts.all stick to master or would it grab a reader?
If it does not stick for the request then could we get that behavior by turning stickiness on but setting master_ttl = 0 (or near 0)?

I did some testing of this today and this is what I found:
If stickiness = false then it does NOT stick during a single request.  So in my example above posts = user.posts.all would go to a reader.
If stickiness = true and master_ttl is set to a very low number (i tried 0.01) then it will stick for the entire request (even if longer than master_ttl).

That's my understanding as well. Stickiness is a concept between SQL calls. Setting it to false (or using the block) might be right in a situation with known writes that have nothing to do with the reads, for example.
maybe there's a case to be made for cookie=false (or some better name) to not do it between requests.

@drewB  thanks for the proactive investigation to your own question!

Thanks for confirming what I saw.
Yes, I think that is where the ambiguity is.  Cause it isn't really between SQL calls (see https://github.com/taskrabbit/makara/issues/206). It is between requests where request #1 is the first one to make a write sql call.  Maybe just an improvement to the README would clear things up.  I will create a PR to try and clear that up.


SAKIII-5104 - Follow up on additional code review

https://jira.sakaiproject.org/browse/SAKIII-5104

Verified and merged.


Event: Message may not receive variable when sent to self

When using the do_message/event_message opcodes in a single program card, the event is reliably triggered, but the variable provided is not consistently received.
Test program is https://gist.github.com/shabble/206d1a12da537647603f3cf414307942
Place in a processor in slot 1, with item-slot 2 containing a network identifier bound to the same processor.
Execute with signal vec2.
If there is only a single CPU, or if exclusive mode is enabled, the message event handler will not receive the variable.
If >1 CPU is available (and not exclusive) the variable will be received and printed as expected.
If 2 CPUs are present and a second program listens for the event, both will receive it, but only one will be passed the variable. More CPUs (possibly N+1) means both will receive the var.
I'm not 100% sure what I'd expect to happen here, probably either:
a) it's queued like any other event when there aren't any cores available, and runs after the caller sequence completes
b) it's dropped if there are no cores, so the handler doesn't fire at all.
In either case, getting the event but not the associated variable seems odd/wrong.
Version:

minecraft 1.10.2
rftoolsctrl-1.1x-1.6.4.jar

I found the reason for the bug. The problem was that events that cannot be handled immediatelly gets pushed on a queue. And they are executed when there is an available core. The problem is that the parameter is ignored in that case. I will fix this for next release


Backup not working following the guides

Actions before raising this issue

[X] I searched the existing issues and did not find anything similar.
[X] I read/searched the docs

Steps to Reproduce
Hi,
I need to upgrade as soon as possible my CVAT version (actually working in 2.11.2) to the newest one. Before doing it, I've tried to backup the data following the guides. I run these commands:

$ mkdir backup
$ docker run --rm --name temp_backup --volumes-from cvat_db -v $(pwd)/backup:/backup ubuntu tar -czvf /backup/cvat_db.tar.gz /var/lib/postgresql/data
$ docker run --rm --name temp_backup --volumes-from cvat_server -v $(pwd)/backup:/backup ubuntu tar -czvf /backup/cvat_data.tar.gz /home/django/data
$ docker run --rm --name temp_backup --volumes-from cvat_elasticsearch -v $(pwd)/backup:/backup ubuntu tar -czvf /backup/cvat_events.tar.gz /usr/share/elasticsearch/data

This threw the following error:
tar: Removing leading `/' from member names
tar: /usr/share/elasticsearch/data: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors

How can I make the backup? Are the three commands actually updated to work with the new versions?
Thanks in advance,
Manuel

@azhavoro may you please look at the issue?

@bsekachev I think the problem is that the backup guide documentation has not been updated since elasticsearch was replaced by clickhouse. I am similarly trying to create a backup and the only reference I can find to elasticsearch is in the changelog.md for version 1.3.0.
@mmoyano-sigmacognition You might be able to backup the events by doing the following, but I recommend spinning up a fresh CVAT instance before deleting your existing one and attempting a restore first to confirm that you are able to recreate the events data:
docker run --rm --name temp_backup --volumes-from cvat_clickhouse -v $(pwd)/backup:/backup ubuntu tar -czvf /backup/cvat_events.tar.gz /var/lib/clickhouse/

It might also be a good idea to back up the cvat_vector and cvat_grafana services' volumes too because per the release notes for version 2.4.0 (the first reference to clickhouse I was able to find):
"Improved analytics and enriched it with the following features: log collection from UI and server, exceptions collection, user activity visualization, aggregation of user and job working time, and log filtering for debugging purposes. Analytics are now based on ClickHouse + Vector + Grafana."
To create an archive for those services' volumes run the following two commands:
docker run --rm --name temp_backup --volumes-from cvat_vector -v $(pwd)backup:/backup ubuntu tar -czvf /backup/cvat_vector.tar.gz /etc/vector/vector.toml

And
docker run --rm --name temp_backup --volumes-from cvat_grafana -v $(pwd)backup:/backup ubuntu tar -czvf /backup/cvat_grafana.tar.gz /var/lib/grafana/dashboards/

Those last two might not be necessary, but it can't hurt. I think the grafana one specifically would be saving any dashboard settings you may have configured, but that is just speculation on my part and I have no idea what the vector.toml volume is storing and whether or not it is required to properly restore events data. Maybe one of the devs can chime in as I am by no means an expert, but I am quite confident cvat_elasticsearch is a deprecated component no longer used in the recent releases.


EC:<IP_ADDRESS> aconitate hydratase

Further to a previous discussion in 2011 (#8602):
EC:<IP_ADDRESS>
Name: aconitate hydratase
Reaction: citrate <=> D-threo-isocitrate
Comment: Besides interconverting citrate and cis-aconitate, it also interconverts cis-aconitate with isocitrate and, hence, interconverts citrate and isocitrate.
RHEA xref: RHEA:10336
We currently have 3 GO terms relating to EC:<IP_ADDRESS> aconitate hydratase - here's a summary:

GO:0003994 aconitate hydratase activity xref: EC:<IP_ADDRESS>, RHEA:10336
-- this is for the overall reaction: citrate <=> D-threo-isocitrate
-- 55 GO EXP annotations, 52,576 RHEA annotations in UP)
GO:0047780 citrate dehydratase activity xref EC:<IP_ADDRESS>, RHEA:10228
-- this is for the first sub-reaction: citrate = cis-aconitate + H2O
-- 0 GO EXP annotations, 1 RHEA annotation in UP
GO:0052633 isocitrate hydro-lyase (cis-aconitate-forming) activity xref: RHEA:22144
-- this is for the second sub-reaction: cis-aconitate + H2O = D-threo-isocitrate
-- 0 GO EXP annotations, 2 RHEA annotations in UP)

I'd suggest we obsolete the two sub-reaction terms (GO:0047780 and GO:0052633).
However, if there's a good reason for keeping them, then EC:<IP_ADDRESS> should be a narrowMatch xref on both GO:0047780 and GO:0052633.
And regardless, please add MetaCyc:RXN-14047 as an xref to GO:0003994
==
id: GO:0003994 (55 EXP annotations)
name: aconitate hydratase activity
namespace: molecular_function
def: "Catalysis of the reaction: citrate = isocitrate. The reaction occurs in two steps: (1) citrate = cis-aconitate + H2O, (2) cis-aconitate + H2O = isocitrate. This reaction is the interconversion of citrate and isocitrate via the labile, enzyme-bound intermediate cis-aconitate. Water is removed from one part of the citrate molecule and added back to a different atom to form isocitrate." [EC:<IP_ADDRESS>, GOC:pde, GOC:vw]
comment: This is a process composed of two reactions represented by the terms 'GO:0052632 : citrate hydro-lyase (cis-aconitate-forming) activity' and 'GO:0052633 : isocitrate hydro-lyase (cis-aconitate-forming) activity'.
synonym: "aconitase activity" EXACT []
synonym: "cis-aconitase activity" RELATED [EC:<IP_ADDRESS>]
synonym: "citrate hydro-lyase activity" BROAD [EC:<IP_ADDRESS>]
synonym: "citrate(isocitrate) hydro-lyase (cis-aconitate-forming)" RELATED [EC:<IP_ADDRESS>]
synonym: "citrate(isocitrate) hydro-lyase activity" RELATED [EC:<IP_ADDRESS>]
xref: EC:<IP_ADDRESS>
xref: RHEA:10336
is_a: GO:0016836 ! hydro-lyase activity
id: GO:0047780 (0 EXP annotations)
name: citrate dehydratase activity
namespace: molecular_function
alt_id: GO:0052632
def: "Catalysis of the reaction: citrate = cis-aconitate + H2O." [EC:<IP_ADDRESS>]
comment: This term is also a sub-reaction of 'aconitate hydratase activity ; GO:0003994 (EC:<IP_ADDRESS>)'.
synonym: "aconitate hydratase activity" BROAD [EC:<IP_ADDRESS>]
synonym: "citrate hydro-lyase (cis-aconitate-forming)" RELATED [EC:<IP_ADDRESS>]
synonym: "citrate hydro-lyase (cis-aconitate-forming) activity" EXACT []
synonym: "citrate hydro-lyase activity" BROAD [EC:<IP_ADDRESS>]
xref: EC:<IP_ADDRESS>
xref: KEGG_REACTION:R01325
xref: MetaCyc:ACONITATEDEHYDR-RXN
xref: RHEA:10228
is_a: GO:0016836 ! hydro-lyase activity
relationship: has_part GO:0003994 ! aconitate hydratase activity
id: GO:0052633 (0 EXP annotations)
name: isocitrate hydro-lyase (cis-aconitate-forming) activity
namespace: molecular_function
def: "Catalysis of the reaction: cis-aconitate + H2O = isocitrate." [EC:<IP_ADDRESS>, GOC:pde, GOC:vw, MetaCyc:ACONITATEHYDR-RXN]
synonym: "aconitate hydratase activity" BROAD [EC:<IP_ADDRESS>]
synonym: "cis-aconitase activity" BROAD [EC:<IP_ADDRESS>]
synonym: "citrate hydro-lyase activity" BROAD [EC:<IP_ADDRESS>]
synonym: "citrate(isocitrate) hydro-lyase (cis-aconitate-forming)" BROAD [EC:<IP_ADDRESS>]
synonym: "citrate(isocitrate) hydro-lyase activity" BROAD [EC:<IP_ADDRESS>]
xref: KEGG_REACTION:R01900
xref: MetaCyc:ACONITATEHYDR-RXN
xref: RHEA:22144
is_a: GO:0016836 ! hydro-lyase activity
relationship: has_part GO:0003994 ! aconitate hydratase activity

@deustp01 This relates to our earlier discussion about sub-reactions

Dear all,
The proposal has been made to obsolete GO:0047780 citrate dehydratase activity and GO:0052633 isocitrate hydro-lyase (cis-aconitate-forming) activity. The reason for obsoletion is that these represent sub-reactions. There are no annotations to these terms; these terms are not in any subsets. There are mappings to RHEA, EC and KEGG.
You can comment on the ticket: https://github.com/geneontology/go-ontology/issues/26091
Thanks, Pascale


Generate operator protos

A less ambitious variation of #20722 to try to unblock folks

@howardjohn - this was really not all that less ambitious. It was just more impatient.

/cherrypick release-1.5

@ostromart: new pull request created: #20850

In response to this:

/cherrypick release-1.5

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Issue with menu overlapping header

Fixed issue that happend when .mdl-menu resided within
.mdl-layout__content wrapper.
The header got overlapped, so I added position relative to the
.mdl-layout__content wrapper.
See diffrence here:
https://jsfiddle.net/hbqo0z8e/1/

I signed it!

Woah. We had this visual bug before and had no idea where it was coming from.
Thanks for the PR, @jonathanprehn. I won‘t merge this right away as I’m not sure that’s the actual solution, but having an isolated test case is great and I’ll look into it.

Glad I could help :-)
I'm pretty sure it has to do with what the z-index relates to.
The containing wrapper with position absolute or relative is in my case the .mdl-layout and this is a problem since it also contains the header.

Perhaps better to remove the z-index:1 on the .mdl-layout__content.
It also seems to do the trick.

I’ll assign @sgomes, but he’s on vacation right now. Please be patient :)

I hit this problem today.. The issue is not with menu though.  It happens even when you just place any button inside "mdl-layout__content".
The fix looks good. Thanks @jonathanprehn

Assigned to the 1.1 milestone. Friendly ping @sgomes on a review.

Oh wow, sorry; I'd totally missed it. LGTM, thanks @jonathanprehn!


rust-lang/rust: "failed to switch build data" messages

Steps I did to reproduce:
Open compiler/rustc_hir/src/hir.rs with this suggested config from the dev guide:
{
    "rust-analyzer.checkOnSave.overrideCommand": [
        "./x.py",
        "check",
        "--json-output"
    ],
    "rust-analyzer.rustfmt.overrideCommand": [
      "./build/x86_64-unknown-linux-gnu/stage0/bin/rustfmt"
    ],
    "rust-analyzer.cargo.runBuildScripts": false,
    "rust-analyzer.procMacro.enable": true
}

and it did this and showed a sad popup in the corner:
[ERROR rust_analyzer::reload] failed to switch build data: cargo check failed:
error: could not compile `crc32fast`

To learn more, run the command again with --verbose.
error: build failed

Why would it do such a thing? This error looks similar to what cargo check in r-l/r would fail like.... pokes through r-a code, patches in a debug log (it would be nice if we could spit this out automatically, but my patch here requires rust-lang/rust#44434):
[DEBUG project_model::build_data] run cargo in Some("/home/jade/dev/rust") with ["check", "--quiet", "--workspace", "--message-format=json", "--manifest-path", "/home/jade/dev/rust/Cargo.toml", "--all-targets"]

So from what I can understand, project_model::build_data is calling cargo check with its own generated command, which it should not do in r-l/r and probably some other places, in spite of there being a configured checkOnSave.overrideCommand. I'm not sure how this should be handled, but I'm filing it to document it as an issue with r-l/r.
cc #8915

Setting procMacro.enable to true (contrary to the dev guide) overrides the runBuildScripts setting (as the documentation for the setting mentions), so cargo check will be run.

Oh, shoot. I mixed that up while looking for the proc macro issues :/ oops.


Print e3sm diags output

Remove buffering to ensure errors are printed in the log file. Resolves #13.

@golaz This is ready for review.  The first four commits are from #2.
The actual change is to add -u which turns off buffering. I was concerned this would slow down the task, but this doesn't appear to be the case.
The alternative option is what I've commented out in that commit: using flush(). Unfortunately, that option seems to only work occasionally, whereas -u will consistently print the full error stack trace.


SpherePointer to cache TryGetNearGraspPoint

Describe the bug
SpherePointer leverages TryGetNearGraspPoint() for many commonly used properties (i.e IsNearObject and IsInteractionEnabled). These properties are called multiple times which causes the TryGetNearGraspPoint and resulting Physics.CheckSphere to be redundantly called everytime.
To reproduce
Read SpherePointer.cs => IsNearObject & IsInteractionEnabled
Expected behavior
For a given frame update, the results of TryGetNearGraspPoint and Physics.CheckSphere could potentially be cached. The checksphere may be problematic if objects are instantiated during an update loop. But the TryGetNearGrapsPoint should not be altering.
Screenshots
If applicable, add screenshots to help explain your problem.
Your Setup (please complete the following information)

Unity Version [e.g. 2018.3.11f1]
MRTK Version [e.g. v2.0]

Target Platform (please complete the following information)

HoloLens
HoloLens 2
WMR immersive
OpenVR

Additional context
Add any other context about the problem here.

fixed.


[Package Update] dep – for Linux et al.

dep is already in 0.5.0 with some significant changes.

Not true :innocent: ...it was updated already, I just didn't do update channel before.
Thanks!


[Task] Create GUI for app in SceneBuilder

Description of work
Create GUI for app in SceneBuilder
Acceptance Criteria
Look at building the S.outs below into SceneBuilder
    Scanner scanner = new Scanner(System.in);
    System.out.print("Enter the chatter's name: ");
    String name = scanner.nextLine();

    System.out.print("Enter the donation amount: ");
    double amount = scanner.nextDouble();

    scanner.nextLine(); // Consume newline

    System.out.print("Enter the donation message: ");
    String message = scanner.nextLine();


[FEATURE REQUEST] Adding Max Value to Point Resources

Love all the buttons in the point items (stamina, mana, etc), is it possible to have the max value show up somewhere?
It would be nice to see both current and max values

Hi @SirJohn13
Version 0.8.1 should have those info.
I've made a change in those button.
Now left click decrease points and right click increase (in the logic of the game, doomed for example does the opposity way)
I'll keep it open in case the new behaviour causes confusion.

Looks and works great, thanks!
Nice touch with the pop-up tooltip


Filter fileds when display content of the message with iso8583.Describe

We may create an option that will enable masking of the card number when we dump messages. That may be useful for logging, etc.

Could we pass a flag / config value to toggle whether to mask such fields or not?
I imagine users of this lib may want to print out this value for testing / debugging

Yeah, I see this as an option.

I would hope the same flag could be passed back into #103 so that those errors which will be passed out of the library could be masked by default as well. By default, PII data wouldn't be returned unless the library was in verbose or debug mode.
Maybe we need a list of fields that we want to mask?
Field 02: PAN (Primary account number)
Field 20: Primary account number extended
Field 35: Track 2 data
Field 36: Track 3 data
Field 45: Track 1 data
Field 52: PIN (Personal Identification Number)
Field 55: EMV TLV data (this is a nested tree and should have its own config)

I think because of the different meanings of the fields in different specs, we can't rely on the field number.
Maybe, as idea, we can add Mask field into the Spec:
		2: field.NewString(&field.Spec{
			Length:      19,
			Description: "Primary Account Number",
			Enc:         encoding.ASCII,
			Pref:        prefix.ASCII.LL,
                        Mask:      macking.PAN,
		}),

package macking

type Masker func(string) string

var PAN Masker = func(number string) string {
  if number == "" || len(number) < 5  {
    return ""
  }

  in := []byte(number)
  return fmt.Sprintf("%s%s%s", in[:1], strings.Repeat("*", 6), in[len(in)-4:])
}

My assumption, that then we can mask data in errors, logs, describe.Message using provided Mask.
P.S. We can use something like https://pkg.go.dev/github.com/ggwhite/go-masker to avoid our own implementations of different masking functions.

Adding some more ideas so we can resume work on filtering data when we dump messages...
I'm looking at it from two perspectives:

as a user of our Go package
as a user of the CLI

1. For the Go package user
Currently, we have Describe method:
iso8583.Describe(os.Stdout, msg)

we can make Describe to be a variadic function that accepts optional filters for the fields:
iso8583.Describe(os.Stdout, msg, FilterField("2", PANFilter), FilterField("59", WhateverFilter))

I have a working POC here for Describe method: https://go.dev/play/p/xqmH4nB0Qse
2. For the CLI user
Currently, we have the describe command for which we can add filter argument(s) like this:
./iso8583 describe --filter 2:pan --filter 59:pan mgs.dat

Also, it would be good to filter fields of the composite fields as well (in my POC, it works with int IDs, not strings)

This looks pretty useful and there's prior art in the ACH package. We have fixed field positions so we can avoid having to specify the field # to mask. The decision to mask a field is passed through an Opts struct.
https://pkg.go.dev/github.com/moov-io/ach/cmd/achcli/describe

Yea, it's pretty common to use an int and masking to pass along several flags. The ...args option works as well and is easier to understand.
https://github.com/golang/go/blob/go1.19.3/src/text/tabwriter/tabwriter.go#L168-L208
I like having a default set of masking flags, especially if the card brands use the same fields we could mask by default.
The idx:type mapping of fields makes sense to me and can easily have a Go api.


Page CF_ChildFilesPage does not exist

1 - Version Installed 1.3
2 - Followed setup video, added Opportunities, Contacts as the "Child Objects" on the Account page setup. Works as expected in lightning
3 - Add "View Related files" on Account page.  Click Button and receive the following error, "Page CF_ChildFilesPage does not exist".
I've checked permissions, all profiles have access to this visualforce page. If I click on "preview" of the actual page I see the followig:
Set Up in lightning:

I did an inspect/console and am receiving the following error:

Top of the error is this:
logo180.png:1 GET https://login.salesforce.com/17181/logo180.png 404 (Not Found)


Update Crossbar template and examples

After merging Dave's fork back in, the following likely needs updates:

https://github.com/crossbario/crossbar/tree/master/crossbar/templates/hello/cpp
https://github.com/crossbario/crossbarexamples/tree/master/hello/cpp
https://github.com/crossbario/crossbarexamples/tree/master/hello/cpp_tls
https://github.com/crossbario/crossbarexamples/tree/master/sharedregs/cpp

Issue migrated to https://github.com/crossbario/crossbar/issues/374


clippy: readonly_write_lock

Problem
some changes for bumping Rust version: https://github.com/anza-xyz/agave/pull/1309

but looks like we fetching this lock intentionally.
Summary of Changes
keep it!

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 82.8%. Comparing base (af6930d) to head (789814d).
Report is 5 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##           master    #1336     +/-   ##
=========================================
+ Coverage    81.6%    82.8%   +1.2%
=========================================
  Files         867      867
  Lines      368900   368898      -2
=========================================
+ Hits       301052   305580   +4528
+ Misses      67848    63318   -4530


Norwegian is displayed as unknown locale

Description
"no-NO" region tag is displayed as an unknown locale because the region tag does not match the region tag supported by Windows.
The documentation seems to have multiple tags used in the region. (nb-NO nn-NO)
Also, although not listed, no-NO seems to be used in some cases.
Steps To Reproduce
No response
Expected behavior
Displayed as Norwegian.
DevToys Version
Version <IP_ADDRESS> | X64 | DEBUG | main | 80bb4f02
Relevant Assets/Logs
Microsoft Docs : Available languages for Windows

Thanks for the feedback! I just updated Crowdin and fixed it :)


fix/#6423 Update total hours in emissions evaluation report

Replace the total hours field with total OP time in emission error details report, emission evaluation report and emission printout report.
Updated function in rpt_factility_information.sql to populate the Total OP Time field value and removed Total Hours field.

It was determined that the stated change is invalid.  Showing the Total Op Hours for an emission report would be inaccurate if the emission report contains more than one location.  This pull-request will be closed.


experience/3794: fixed rendering of (seemingly) duplicated items

This PR works around a rest-hooks bug that was causing the facilities results to render as duplicated and unsorted, even though the JSON response was solid. This is all @kevinhaube 's work, btw, i'm just taking the credit. Thanks, man!
Test Steps:

Login as admin
On the Daily Data page, click on a report that has multiple tests from multiple facilities
Facilities reporting table is always ordered by Organization with no duplicated rows

Some examples of pages this is fixing:

on staging: ca-dph
on prod: il-phd

Changes

FacilitiesTable.tsx only
before

after

Checklist
Testing

[x] Tested locally?
[x] Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
[x] (For Changes to /frontend-react/...) Ran npm run lint:write?
[ ] Added tests?

Process

[ ] Are there licensing issues with any new dependencies introduced?
[ ] Includes a summary of what a code reviewer should test/verify?
[ ] Updated the release notes?
[ ] Database changes are submitted as a separate PR?
[ ] DevOps team has been notified if PR requires ops support?

Fixes

#issue - List GitHub issues this PR fixes

To Be Done
Create GitHub issues to track the work remaining, if any

#issue

Specific Security-related subjects a reviewer should pay specific attention to

Does this PR introduce new endpoints?

new endpoint A
new endpoint B

Does this PR include changes in authentication and/or authorization of existing endpoints?
Does this change introduce new dependencies that need vetting?
Does this change require changes to our infrastructure?
Does logging contain sensitive data?
Does this PR include or remove any sensitive information itself?

If you answered 'yes' to any of the questions above, conduct a detailed Review that addresses at least:

What are the potential security threats and mitigations? Please list the STRIDE threats and how they are mitigated

Spoofing (faking authenticity)

Threat T, which could be achieved by A, is mitigated by M

Tampering (influence or sabotage the integrity of information, data, or system)
Repudiation (the ability to dispute the origin or originator of an action)
Information disclosure (data made available to entities who should not have it)
Denial of service (make a resource unavailable)
Elevation of Privilege (reduce restrictions that apply or gain privileges one should not have)

Have you ensured logging does not contain sensitive data?
Have you received any additional approvals needed for this change?

Pull reviewers stats
Stats for the last 30 days:

User
Total reviews
Median time to review
Total comments

MauriceReeves-usds
35
12h 56m
11

cwinters-usds
21
13h 48m
6

carlosfelix2
15
3h 7m
63

brick-green-agile6
15
1h 10m
3

TomNUSDS
14
1h 17m
18

jimduff-usds
13
13h 59m
2

sean-usds
12
14m
3

jbiskie
7
1h 9m
0

kevinhaube
5
16h 44m
1

jorg3lopez
5
2h
1

sethdarragile6
5
9m
0

JosiahSiegel
4
33m
2

oslynn
4
20h 19m
19

rhood23699
3
1h 57m
0

clediggins-usds
3
1h 36m
0

whytheplatypus
2
21h 41m
4

ahay-agile6
2
1d 22h 26m
0

RickHawesUSDS
2
3d 10h 21m
0

jeremy-page
1
21h 35m
0

victorialb-usds
1
2d 20h 38m
1

jh765
1
2h 54m
0

@sethdarragile6 I enlisted Tom's help; it did come down to the .pk for each. It'll replace all entities with the same PK to the most recent entry (i.e. why we got 2 of the second CLIA: SA item)

thank you @kevinhaube AND @TomNUSDS for helping us get to the most elegant fix!! Ready for re-review


Update host.json

Thanks for the great tutorial, it was really helpful.
This fix will allow it to work with the latest version of Azure Functions Core Tools.

Thank you!


Get cIRI database path from configuration variables

Fixes #132

Add db_path

Test Plan:
CI must pass

@wusyong Thank you for this really great PR !
A general comment, could you make this option reside under the cIRI conf instead of the consensus conf ?

Why are the initial databases files 44k ? Are they really empty, containing only the schema ?
I think they should be 20480 bytes.

Sorry, didn't aware they were modified when testing.

Thanks @wusyong this is very useful. Good first PR !


DOC: scipy.stats.lognorm — SciPy v1.12.0.dev Manual

Issue with current documentation:
The document says "lognorm takes s as a shape parameter for s".
However, It seems that you can set σ and μ by lognorm(s=σ, scale=math.exp(μ)).
I confirmed it seems to work properly:
import math
from scipy.stats import lognorm
import matplotlib.pyplot as plt

sigma = 1
mu = 0

lgnrm: lognorm = lognorm(s=sigma, scale=math.exp(mu))  # DistHolder.generate_log_normal_dist(10, 10 ** 2 * 1.0000005)

x = [v / 10 for v in range(30)]
y = [lgnrm.pdf(v) for v in x]
plt.plot(x, y)
plt.show()

reffered https://en.wikipedia.org/wiki/Log-normal_distribution
Idea or request for content:
"lognorm takes s as a shape parameter and scale as a scale parameter, like a formmath.exp(mu)".
I think it's better that changing arg names and math.exp() is not needed, as following:
lognorm(sigma=sigma, mu=mu)

Additional context (e.g. screenshots, GIFs)
No response

The documentation already points out the connection between the lognormal and normal distribution.

Suppose a normally distributed random variable X has mean mu and standard deviation sigma. Then Y = exp(X) is lognormally distributed with s = sigma and scale = exp(mu).

We cannot change the variable name in a backward compatible way with the existing distribution infrastructure.

The documentation already points out the connection between the lognormal and normal distribution.

Suppose a normally distributed random variable X has mean mu and standard deviation sigma. Then Y = exp(X) is lognormally distributed with s = sigma and scale = exp(mu).

OK, but  "lognorm takes s as a shape parameter for s" seems confusing to mean that lognorm has only s parameter. The way to set mu and sigma can't be understood at a glance on following page, either.
https://stackoverflow.com/questions/8870982/how-do-i-get-a-lognormal-distribution-in-python-with-mu-and-sigma/13837335
How about to add a description "If you know mu and sigma, you can initialize by lognorm(s=sigma, scale=math.exp(mu))".

We cannot change the variable name in a backward compatible way with the existing distribution infrastructure.

Changing names is difficult but how about adding variables?

s is the only "shape" parameter. The location and scale parameters, loc and scale, are common to all SciPy distributions. The next paragraph of the documentation explains that part.
"If you know mu and sigma..." may not be understood by all readers. Presumably these refer to the mean and standard deviation of the underlying normal distribution, but that would need to be explicit. Writing documentation that is immediately understood by everyone is challenging. You are welcome to submit a PR with your suggestion, though.

Changing names is difficult but how about adding variables?

That is also challenging with the current infrastructure. I  will be addressing this and other concerns as part of https://github.com/scipy/scipy/issues/15928, which I am working on almost full time this month.

I've documented this request specifically in gh-15928 so I'm sure to review it again as I'm working.

@lamrongol Does gh-18995 help address this issue?

@mdhaber I think users can't find the constructor with sigma and mu at a glance  by https://github.com/scipy/scipy/pull/18995/commits/fec08e1ccf6b68cc0234b30070f2bfe6e9f96842 .
Is it difficult to add an example to the top of page?


Update and refresh 'Sponsorships' page

Update and refresh 'Sponsorships' page

Removed MyMonero, JetBrains, Dome9, Kitware, Navicat and Araxis. Added Tari Labs, Globee and Macstadium
Used bigger boxes for bigger contributors (currently Tari Labs and Globee)
Removed redundant titles, improved styiling and added details about what is being sponsored
Added sanitised referrer policy for all external links
Added logos for Globee, Tari Labs and Macstadium
Moved images to their own folder in /img/sponsors

Based on #1169
Closes #896
Closes #1168
preview:

Is it possible to vertically center the "Fork Networking" image / text?

Verticalli aligned blocks and edited symas' description (ass suggested by @hyc in https://github.com/monero-project/monero-site/issues/896#issuecomment-685776667)

Rebased

$5150 is a bit weird, I doubt CDN prices are static, how about simply 5000? :P

That's the amount fluffypony reported. I think he has direct access to those bills so he knows the specific amount, wouldn't change to a generic number when we have a specific amount reported :)

Adapted to #1145 and fixed a link.
Note that this PR should be merged after #1169.

Rebased


Add openbox as a simple window manager

Currently with no window manager it's not possible to close any pop-ups from the torch server without closing the entire program process. Adding a window manager will make the mod/plugin menus more accessible.

Hey @jeppevinkel, LGTM. Thanks for the PR!


Added Realm plugin compatibility for Xcode 7.3

This PR adds the necessary compatibility UUID to the Realm plugin project in order for it to be accepted by Xcode 7.3.

Thanks for the PR, @TimOliver! We'll need you to accept our Contributor License Agreement before we can merge your contributions.
Cheers,
The robots and humans at Realm

:+1:


drivers: adc: adc_mcux_adc16: Allow ADC_REF_VDD_1 reference option

Only ADC_REF_INTERNAL ADC reference option is allowed in adc_mcux_adc16 driver. Some NXP SoCs have also VDDA option. Enable ADC_REF_VDD_1 option in driver.
The option is selectable in Devicetree using zephyr,reference ADC channel property, the voltage is configurable using zephyr,vref-mv property. It is used by ADC API function adc_raw_to_millivolts_dt for milivolts calculation.

@anangl, kindly review


Single S3Client::simple() spawns 16 threads

Single instance of S3Client::simple() crates many threads (thread 1 and 18 are my):
* thread #1: tid = 0x20f1ae, 0x0000000100086350 s3turbo-376da65fa3e7be4a`_$LT$rusoto_s3..generated..S3Client$LT$P$C$$u20$D$GT$$u20$as$u20$rusoto_s3..generated..S3$GT$::upload_part::hcdf21a85c2fb97b0(self=0x000000010324a190, input=0x00007ffeefbf8480) at generated.rs:25736, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
  thread #2: tid = 0x20f1e5, 0x00007fff7d57ba1e libsystem_kernel.dylib`__psynch_cvwait + 10
  thread #3: tid = 0x20f1e6, 0x00007fff7d57cbf2 libsystem_kernel.dylib`kevent + 10
  thread #4: tid = 0x20f1e7, 0x00007fff7d57ba1e libsystem_kernel.dylib`__psynch_cvwait + 10, name = 'hyper-dns0'
  thread #5: tid = 0x20f1e8, 0x00007fff7d57ba4e libsystem_kernel.dylib`__psynch_mutexwait + 10, name = 'hyper-dns1'
  thread #6: tid = 0x20f1e9, 0x00007fff7d57ba4e libsystem_kernel.dylib`__psynch_mutexwait + 10, name = 'hyper-dns2'
  thread #7: tid = 0x20f1ea, 0x00007fff7d57ba4e libsystem_kernel.dylib`__psynch_mutexwait + 10, name = 'hyper-dns3'
  thread #8: tid = 0x20f1eb, 0x00007fff7d57ba1e libsystem_kernel.dylib`__psynch_cvwait + 10, name = 'hyper-dns0'
  thread #9: tid = 0x20f1ec, 0x00007fff7d57ba4e libsystem_kernel.dylib`__psynch_mutexwait + 10, name = 'hyper-dns1'
  thread #10: tid = 0x20f1ed, 0x00007fff7d57ba4e libsystem_kernel.dylib`__psynch_mutexwait + 10, name = 'hyper-dns2'
  thread #11: tid = 0x20f1ee, 0x00007fff7d57ba4e libsystem_kernel.dylib`__psynch_mutexwait + 10, name = 'hyper-dns3'
  thread #12: tid = 0x20f1ef, 0x00007fff7d57ba1e libsystem_kernel.dylib`__psynch_cvwait + 10, name = 'hyper-dns0'
  thread #13: tid = 0x20f1f0, 0x00007fff7d57ba4e libsystem_kernel.dylib`__psynch_mutexwait + 10, name = 'hyper-dns1'
  thread #14: tid = 0x20f1f1, 0x00007fff7d57ba4e libsystem_kernel.dylib`__psynch_mutexwait + 10, name = 'hyper-dns2'
  thread #15: tid = 0x20f1f2, 0x00007fff7d57ba4e libsystem_kernel.dylib`__psynch_mutexwait + 10, name = 'hyper-dns3'
  thread #16: tid = 0x20f1f3, 0x00007fff7d57c292 libsystem_kernel.dylib`__workq_kernreturn + 10
  thread #17: tid = 0x20f1f4, 0x00007fff7d57c292 libsystem_kernel.dylib`__workq_kernreturn + 10
  thread #18: tid = 0x20f201, 0x00007fff7d57d14a libsystem_kernel.dylib`read + 10, name = 'input_reader'

Bulk of them are Hyper DNS resolver threads as created with HttpsConnector::new(4, handle). This is probably OK. What I did not expect to see is 3 group of this threads per 1 S3Client. This suggests that single S3Client uses 3 HyperClients?
I could not find the other two clients in the source code - one is created with default dispatcher as expected.
There also will be one thread for default Reactor and this stays one no matter how many clients I have as expected.
What I am doing here is multipart upload with one S3Client::simple() and one part upload running. Running multiple part uploads in parallel with single S3Client does not change this picture which is good.

So the 3 clients you see are broken down in the following way:

One client for the request dispatcher
One client for the container credentials provider
One client for the instance metadata provider

It's worth noting that rusoto creates these 16 threads once, and they will be shared between all instances of AWS clients that you create via ::simple. So in other words this is a constant number of threads independent of the number of AWS clients in use.
Is the number of threads created a problem for you?
If so, there could be a way to re-use the same hyper client across the dispatcher and the two providers. In order to achieve that, InstanceMetadataProvider and ContainerProvider would need to gain a constructor to create them using an existing hyper::Client, and then the reactor code in rusoto_core would need to be changed to create only a single client and re-use when creating request dispatcher and credentials provider.

Oh, yeah, you're right!
The downside to making HyperClient a lazy_static is that all these threads will then stick around indefinitely, as opposed to just the single reactor thread.
Also I think eventually I'd want to get rid of all the global state when we integrate with the new tokio which provides a default event loop thread.
Wrapping the AWS client into an Rc or Arc seems like a good way to work around this for now!

Also I think eventually I'd want to get rid of all the global state when we integrate with the new tokio which provides a default event loop thread.

Yeah I think this is the way to go. Thanks for the clarifications. I will stick with Rc<S3Client> for now.


Where did vuex go?

Version
6.0.0-beta.6
Browser and OS info
Chrome / Mac
Steps to reproduce
Open vue-devtools, where is Vuex?
What is expected?
I expect to be able to see all of my state, and list of the mutations that happen like I used to in the previous vue devtools.
What is actually happening?
I can't see my app state, only the state of vuex at a selected component level.

Duplicate of #1268


chore(notion): exclude notion fdw from next release

What kind of change does this PR introduce?
This PR is to exclude Notion FDW from next release, as it is not mature enough and we will rewrite it using the new Wasm framework.
What is the current behavior?
N/A
What is the new behavior?
Exclude Notion FDW just for now.
Additional context
N/A

Was notion fdw released to customers before? If yes, what happens to projects which have notion fdw enabled?


Improvements to Shielding Process

Potentially resolve issue: https://github.com/z-classic/z-nomp/issues/146
New console message: Cleared opidCount,... can be seen when recover from above issue.
Shielding Process Tip: walletInterval in pool_config is the shielding process interval. It is important this be set to a larger time than it takes for your CPU to perform z_sendmany operations. There is a console message to warn about this: Increase walletInterval in pool_config...

Improved balance rounding and conversions for listUnspent and listUnspentZ
Extra error detection in RPC callback for listUnspent and listUnspentZ
Do not process balances equal to or less than fee in sendTToZ and sendZToT
Clear opidCount when daemon reports no operations in progress.
Default paymentInterval to 3 minutes if missing from pool config.
Warn users on paymentInterval less than 3 minutes.
Force paymentInterval no less than 1 minute to reduce RPC work queue.
Default walletInterval to 1 minute if missing from pool config.
Force walletInterval no less than 1 minute to reduce RPC work queue.

I'm going to test this.. let you know

testing this now, will let you know outcome

Can the latest addition make a difference?? I still have issues, even with interval at 5 minutes..

So, a few blocks pending to pay can stuck the payment process?

This still gives me some problems with HUSH, even after putting payment interval at 15 minutes
i think i fixed the issue, i put this in my wallet's conf and now the problem went away for now:
rpcworkqueue=64


Update 17.union-tagged.zig

Make it clearer that they are captured values and not type names or union properties

I can see what you're going for here, but I decided against it as byte and float aren't zig types, and "Val" might make people think that primitive values are being captured, when it's pointers being captured.


Proxy Policy

Background
Users need to be able to use Azure libraries and services from behind proxies. Some languages and environments, e.g. Python's urllib.request and web browsers, have in-built support for proxies. Others, including Node, have no in-built support and so we must provide it.
HTTP proxying is relatively straightforward and commonly acheived. However, users of alternative protocols such as AMQP will still require proxy support somehow even if it requires setup on their end.
Below are two proposals that are not mutally exclusive.
Proposal 1
Azure libraries auto-detect proxy settings based on the presence of environment variables:

HTTP_PROXY: proxy for http requests
HTTPS_PROXY: proxy for https requests
NO_PROXY: a comma-separated list of hostnames that bypass the proxy

These environment variables are already in wide use in the *nix ecosystem - Python's urllib.request, tools like Curl, and browsers on Linux and possibly Mac OS respect these environment variables. It may be nice for us to use them when we find them without any interaction from the user.
Proposal 2
Azure libraries are configured via a proxy parameter to the pipeline. ms-rest implements this already for http clients, and this is similar to how AWS and GCP get support for HTTP proxies in Node (GCP seems to have a configuration parameter, AWS asks you to override the HTTP Agent with a proxying agent).
This option would also allow a user to override their system settings if proposal 1 is accepted.
For non-HTTP services, proxying is less straightfoward as it is a protocol-specific activity. I think there are a couple options:

Allow for configuring protocol-specific proxies via hostname + port similar to HTTP, so if a user has e.g. amqproxy running someplace they can use it with minimal configuration
Do not support programmatic proxying of non-http protocols and rely on e.g. SSH tunneling instead

I like proposal 2 (with support for configuring non-HTTP proxies via options). Proposal 1 I'm not sure about and am curious what others thoughts are.

Proxy requirements were added to the general guidelines.


Drop support for Python 3.8 (10/2024)

Python 3.8 reaches EOL in 10/2024.
Refs:

https://devguide.python.org/versions/#supported-versions
#648

yes, this is a good one.
Maybe we should spread this info into the community so that instance admins can do (or prepare for) an upgrade. Except for upgrading the Python installation on the OS there shouldn't be any troubles AFAIK..

No more security patches should be argument enough, right?

I think we should support 3.8 as long as we can. I think when we ditched 3.6 and 3.7 it was beacause we wanted to use pyproject.toml. Updating the VM where RDMO is running is troublesome, and it will keep people from updating RDMO.

I don't see the connection of these topics. But I am still in favor of dropping EOL versions.
This topic will re-appear every time, when a new major versions is released and an older version is dropped. The RDMO dependencies will then continuously drop their support for EOL versions. Meaning RDMO is stuck with old versions of dependencies.
Ref: #742

because of this
          We can drop it. Now that I discovered `uv` for Python installs I am less worried about this.

Originally posted by @jochenklar in https://github.com/rdmorganiser/rdmo/issues/1206#issuecomment-2506415469
and this https://github.com/rdmorganiser/rdmo-docs/pull/56 ;)
For Django I think that RDMO will upgrade only from LTS(4.2) to LTS(5.2).

Okay, so this means green light for dropping 3.8?
How about the versioning of RDMO? Is this something for the release 2.3.0? Or do you consider this a breaking change?

However, after potentially dropping 3.8 (@jochenklar), we should still be testing against a minimum python version right?
Do we bump it to 3.9 or 3.10 already?

Well we should test 3.9 and 3.13 (which I think breaks now, but this is for another issue). See https://endoflife.date/python

I can do this. 3.13 was not installable recently due to the large number of dependencies that need to be 3.13-ready as well.

Awesome, thanks! Yes, I get some errors with brew on the Mac, which is rolling release (that's why I started to look into uv ...). We probably just need to wait until the dependencies are fixed.

we should then also add the attribute requires-python = '>=3.9' to the pyproject.toml

I know. :)