CUDA detection failed.

Hello, I am getting the following error, cuda version I am running is below. I am trying to run dreambooth stable diffusion on a p3.2xlarge Ubuntu instance and installed cuda 11.7. Not sure how to get the versions to align. Thanks for any and all help.
================================================================================
CUDA SETUP: CUDA runtime path found: /usr/local/cuda/lib64/libcudart.so
CUDA SETUP: Highest compute capability among GPUs detected: 7.0
CUDA SETUP: Detected CUDA version 120
CUDA SETUP: TODO: compile library for specific version: libbitsandbytes_cuda120_nocublaslt.so
CUDA SETUP: Defaulting to libbitsandbytes.so...
CUDA SETUP: CUDA detection failed. Either CUDA driver not installed, CUDA not installed, or you have multiple conflicting CUDA libraries!
CUDA SETUP: If you compiled from source, try again with make CUDA_VERSION=DETECTED_CUDA_VERSION for example, make CUDA_VERSION=113.
Traceback (most recent call last):
File "/home/ubuntu/train_dreambooth.py", line 840, in
main(args)
File "/home/ubuntu/train_dreambooth.py", line 551, in main
import bitsandbytes as bnb
File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/init.py", line 6, in
from .autograd._functions import (
File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/autograd/_functions.py", line 5, in
import bitsandbytes.functional as F
File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/functional.py", line 13, in
from .cextension import COMPILED_WITH_CUDA, lib
File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/cextension.py", line 41, in
lib = CUDALibrary_Singleton.get_instance().lib
File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/cextension.py", line 37, in get_instance
cls._instance.initialize()
File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/cextension.py", line 27, in initialize
raise Exception('CUDA SETUP: Setup Failed!')
Exception: CUDA SETUP: Setup Failed!
Traceback (most recent call last):
File "/usr/local/bin/accelerate", line 8, in
sys.exit(main())
File "/usr/local/lib/python3.10/dist-packages/accelerate/commands/accelerate_cli.py", line 45, in main
args.func(args)
File "/usr/local/lib/python3.10/dist-packages/accelerate/commands/launch.py", line 1104, in launch_command
simple_launcher(args)
File "/usr/local/lib/python3.10/dist-packages/accelerate/commands/launch.py", line 567, in simple_launcher
raise subprocess.CalledProcessError(returncode=process.returncode, cmd=cmd)
subprocess.CalledProcessError: Command '['/usr/bin/python3', 'train_dreambooth.py', '--pretrained_model_name_or_path=runwayml/stable-diffusion-v1-5', '--pretrained_vae_name_or_path=stabilityai/sd-vae-ft-mse', '--output_dir=/content/stable_diffusion_weights/zwx', '--revision=fp16', '--with_prior_preservation', '--prior_loss_weight=1.0', '--seed=1337', '--resolution=512', '--train_batch_size=1', '--train_text_encoder', '--mixed_precision=fp16', '--use_8bit_adam', '--gradient_accumulation_steps=1', '--learning_rate=1e-6', '--lr_scheduler=constant', '--lr_warmup_steps=0', '--num_class_images=50', '--sample_batch_size=4', '--max_train_steps=800', '--save_interval=10000', '--save_sample_prompt=photo of zwx man', '--concepts_list=concepts_list.json']' returned non-zero exit status 1.
root@ip-172-31-67-186:/home/ubuntu# nvidia-smi
Sun Jan 29 17:40:16 2023
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 510.108.03   Driver Version: 510.108.03   CUDA Version: 11.6     |
|-------------------------------+----------------------+----------------------+

Im having the same issue did you find a fix?

I have the same issue and I wanna know how you fix it thanks

@Broccolitop @HBX-hbx what are you all running the script on?


[CU-8687dqkqq] Defaults to Pony Diffusion XL when remixing with any Pony resource as base model

Task linked: CU-8687dqkqq Pony Resources in Generator


ETOR-TI specific alerts and alert groups documentation review

Problem statement
ETOR has an ask to create an alert group and alerts specific to ETOR so that alerts relating to ETOR-TI use case can be sent directly to Flexion-ETOR alert slack channels
What you need to know
Requirements and a basic design document has been created and needs review by RS.
Requirements and design document: https://docs.google.com/document/d/17iYjMWS6nGdsDR2pZlUhZRHNauMCO6Kv2xqi1Ny69y0/edit?tab=t
Acceptance criteria

[ ] Review and provide feedback on requirements and design documents

error rendering markdown. creating new ticket


Microsoft Operating system 12 option to mass convert mass files to e.g. word or excel

Wish we have the option to easily future convert mass files (e.g. pdf) into mass files (e.g. word).  instead alternative we could convert on a single unit by single unit conversion.

@forozco1 great idea! Please track it here in the user voice system so you can socialize it and get votes: https://office365.uservoice.com/search?filter=ideas&query=pdf conversion
Apparently, others have been discussing this idea as well. Some suggest Acrobat Pro has a feature called Action Wizard. https://community.adobe.com/t5/acrobat/how-do-i-convert-multiple-pdf-to-word-documents/td-p/9262319?page=1
https://community.adobe.com/t5/acrobat/batch-convert-pdf-to-word/td-p/4527671?page=1
#please-close

@forozco1 great idea! Please track it here in the user voice system so you can socialize it and get votes: https://office365.uservoice.com/search?filter=ideas&query=pdf conversion
Apparently, others have been discussing this idea as well. Some suggest Acrobat Pro has a feature called Action Wizard. https://community.adobe.com/t5/acrobat/how-do-i-convert-multiple-pdf-to-word-documents/td-p/9262319?page=1
https://community.adobe.com/t5/acrobat/batch-convert-pdf-to-word/td-p/4527671?page=1
#please-close


DeltaLake & Iceberg: Atomic table update discovery

Discover if there's a way to atomically alter a table using DeltaLake or Iceberg.

@Jonathan-Rosenberg would you mind expanding on this? What's the lakeFS use-case under the hood?


Adding Github Actions

Will need to investigate webhooks for GHA to deliver payloads.

@mperrin and @Witchblade101 I am tagging you two as reviewers for discussion about these changes. I have gotten in touch with @jneu to discuss how to pass the github secrets for the user name and password to upload pysiaf to pypi when we release new versions of the software. @jneu said that we should be good to go on his end but before pulling the lever myself I wanted to see if anyone else had any thoughts since we can't release or using travis anymore.

@shanosborne has agreed to take a look at this. Thank you Shannon! I am hoping this is straight forward 👍

Also another note. After you merge this PR and re-trigger the CI in the other open PRs, you'll still see that the Travis CI check is still expected before merging. To update this, you'll go into Settings > Branches, and for each branch, edit it, scroll down to "Require status checks to pass before merging", and from the "Status checks that are required", delete the Travis CI rule and add each of the github actions builds (I think based on your setup there will be one build per python version). I believe that you won't be able to add the github actions tests until they've been run at least 1x.

@shanosborne when I look under my local fork, I don't see any runs kicking off. Do you think this is because the travis rule is blocking it?
https://github.com/mfixstsci/pysiaf/actions/new

@mfixstsci Right, nothing is running because you don't have a PR open. Open a PR for this branch on your personal fork and that should kick off the CI

@mfixstsci Right, nothing is running because you don't have a PR open. Open a PR for this branch on your personal fork and that should kick off the CI

https://github.com/mfixstsci/pysiaf/pull/2
Hmmm, like this? Because I don't see the checks or the workflow runs showing up.

Yes, a PR like that is exactly what I did and it triggered the CI automatically. You can see my attempts at adding GHA on my  fork of webbpsf here https://github.com/shanosborne/webbpsf/pull/3 and on my fork's Actions tab (back to the last page)
For me, it auto-triggered the CI and then gave me an error because I implemented something wrong. My best guess is that it's not triggering because something in the file is wrong. Maybe the on: push/pull request part. Try setting it like on: [push, pull_request] and see if that helps it recognize that it should start.

@shanosborne that makes sense. It looks like it's only triggered on the default branch as of right now!

@shanosborne looks like the tests are all passing. I added some flags to not run some tests that write and delete directories etc. I am sure there is something I could do here to fix this but I don't want to hold this PR up.
https://github.com/mfixstsci/pysiaf/actions/runs/1234993349
Assuming the publish-to-pypi job looks good, could we merge?

@shanosborne @Witchblade101 thank you for reviewing. I merged the request and all of the tests are passing:
https://github.com/spacetelescope/pysiaf/actions


List-group: Branded

Fixes #1452.
On hold until design review of specs.

Notes:

The focus state doesn't have the correct appearance in this PR. It will be corrected in the focus dedicated PR #1437

In the #Flush paragraph, it might be useful to add a design callout saying that this flush variant shall be used inside a container with a top and a bottom border, to have at the end the same design as illustrated on the design specifications.
--> Design specifications illustration:

--> Boosted illustration:

In the #contextual-classes paragraph second example, the design specifications have to be checked with designers for the color of icons on the different interactive states (hover, pressed/active, ...) for what they've described for the light version is not consistent with what they've described for the dark version. In the light version, the icons keep the same color no matter the state when they change color in the dark version.

In List-group.md file,  paragraph #custom-content, the police size of <small>And some small print.</small> shall be 16px and not 14px.

* paragraph `#custom-content`, the police size of `<small>And some small print.</small>` shall be 16px and not 14px.

I don't think so, we don't have specs for this specific case + <small> should display a font-size of 14px. Maybe only a callout should do the trick ? Linked to #1199.

* paragraph `#checkboxes-and-radios`, I think the checkbox/radio button left margin should be 10px and not more, for in the design specification "Numbered", the number has a left margin of 10px. To me, it the same type of case.

Spoke together and we'll propose a shifted design for a design review: padding-left: 15px for every variant even Numbered.

Adding what was said in design spec meeting:

The specs for active states is great for the dark variant and should be backported to the white variant. -> Nothing to change atm
Flush variant should stay as-is but we might introduce some examples to show how to build the different variants. -> Open another issue to tackle it ?

Please see #1467. Closing this one.


python311Packages.casbin: 1.31.2 -> 1.32.0

Diff: https://github.com/casbin/pycasbin/compare/refs/tags/v1.31.2...v1.32.0
Changelog: https://github.com/casbin/pycasbin/blob/v1.32.0/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 262030 run on x86_64-linux 1

4 packages built:

python310Packages.casbin
python310Packages.casbin.dist
python311Packages.casbin
python311Packages.casbin.dist


fix typo in prometheus doc

should be exchange instead of queue

@elelayan Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

“@pivotal-cla This is an Obvious Fix

@elelayan This Pull Request contains an obvious fix. Signing the Contributor License Agreement is not necessary.

@elelayan you have updated the 4.1 version of the site. I have applied the same change to the 4.0 (current) version. It should be live in a few minutes.
Thank you for contributing to RabbitMQ docs.

thanks for the quick merge


Prepare systems: btk

Input submission checklist

[x] created a directory for each system based on the template directory
[x] named and placed the directory with the following pattern: input_structures/prepared_structures/<set_name>/<system_name>

For each submitted directory:

[x] filled in system preparation details in the PREPARATION_DETAILS.md file
[x] added a PDB file with the protein named protein.pdb
[x] removed any cofactors from the PDB file and placed them in cofactors.sdf
[x] did not re-protonate the residues, but left protonation state of the protein unchanged
[x] kept cystallographic waters and metals in the PDB file
[x] tested the PDB and, if available, cofactors.sdf file using the input validation script
[x] copied over the ligands SDF file to a file named ligands.sdf and removed any duplicate binding modes or protonation states, keeping the more favorable state

Summary of changes

Licensing agreement

[x] I agree to release these inputs under the combined MIT and CCBY SA 4.0 licenses of this repository

No, it just has the btk. I mistakenly thought we had to use the same name for all the systems. Hannah has since straightened me out about this.  We removed the tyk2 manually since it had already been added to the repository. Sorry for the confusion.  Sent from iPhoneOn Aug 12, 2024, at 2:47 AM, Irfan Alibay @.***> wrote:
@IAlibay approved this pull request.
This looks good to me, but it only contains the BTK system, should the TYK2 system also be present?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


Optimize acyclic_coloring

@gdalle
I have the result of all benchmarks tonight:
Problem 1/38: pwtk
size(A) = (217918, 217918) | nnz(A) = 11524432
Column coloring: 180
timer: 1.79020499
Star coloring: 108
timer: 13.128444092
Acyclic coloring: 53
timer: 10.576655852

Problem 2/38: Lin
size(A) = (256000, 256000) | nnz(A) = 1766400
Column coloring: 12
timer: 0.416505455
Star coloring: 11
timer: 0.571455992
Acyclic coloring: 7
timer: 0.679195734

Problem 3/38: bmw3_2
size(A) = (227362, 227362) | nnz(A) = 11288630
Column coloring: 336
timer: 1.909149565
Star coloring: 135
timer: 12.342920864
Acyclic coloring: 71
timer: 7.814760165

Problem 4/38: fcondp2
size(A) = (201822, 201822) | nnz(A) = 11294316
Column coloring: 120
timer: 1.629666569
Star coloring: 111
timer: 12.638892798
Acyclic coloring: 66
timer: 9.962901677

Problem 5/38: halfb
size(A) = (224617, 224617) | nnz(A) = 12387821
Column coloring: 141
timer: 1.787561872
Star coloring: 117
timer: 13.807083961
Acyclic coloring: 60
timer: 9.373287101

Problem 6/38: hood
size(A) = (220542, 220542) | nnz(A) = 9895422
Column coloring: 103
timer: 1.600294055
Star coloring: 89
timer: 9.353391648
Acyclic coloring: 55
timer: 7.042590133

Problem 7/38: troll
size(A) = (213453, 213453) | nnz(A) = 11985111
Column coloring: 387
timer: 1.776546394
Star coloring: 108
timer: 15.771867829
Acyclic coloring: 57
timer: 11.172261877

Problem 8/38: CO
size(A) = (221119, 221119) | nnz(A) = 7666057
Column coloring: 380
timer: 1.098667786
Star coloring: 264
timer: 10.609647166
Acyclic coloring: 152
timer: 10.034654336

Problem 9/38: Ga41As41H72
size(A) = (268096, 268096) | nnz(A) = 18488476
Column coloring: 837
timer: 9.074174242
Star coloring: 565
timer:<PHONE_NUMBER>23
Acyclic coloring: 391
timer: 42.176475158

Problem 10/38: Si87H76
size(A) = (240369, 240369) | nnz(A) = 10661631
Column coloring: 560
timer: 2.414487114
Star coloring: 283
timer: 31.736568593
Acyclic coloring: 176
timer: 17.317734069

Problem 11/38: BenElechi1
size(A) = (245874, 245874) | nnz(A) = 13150496
Column coloring: 78
timer: 2.017972905
Star coloring: 71
timer: 15.331120981
Acyclic coloring: 42
timer: 11.372123778

Problem 12/38: 3Dspectralwave2
size(A) = (292008, 292008) | nnz(A) = 12935272
Column coloring: 202
timer: 2.544826437
Star coloring: 102
timer: 23.922568767
Acyclic coloring: 39
timer: 21.942924515

Problem 13/38: thermomech_dM
size(A) = (204316, 204316) | nnz(A) = 1423116
Column coloring: 15
timer: 0.166520177
Star coloring: 11
timer: 0.939707582
Acyclic coloring: 7
timer: 0.426854618

Problem 14/38: offshore
size(A) = (259789, 259789) | nnz(A) = 4242673
Column coloring: 48
timer: 0.713105461
Star coloring: 29
timer: 2.755919986
Acyclic coloring: 14
timer: 2.444392949

Problem 15/38: citationCiteseer
size(A) = (268495, 268495) | nnz(A) = 2313294
Column coloring: 1318
timer: 1.174781763
Star coloring: 213
timer: 4.72819425
Acyclic coloring: 65
timer: 5.304618855

Problem 16/38: coAuthorsCiteseer
size(A) = (227320, 227320) | nnz(A) = 1628268
Column coloring: 1372
timer: 0.225162009
Star coloring: 106
timer: 1.35290398
Acyclic coloring: 87
timer: 1.622949863

Problem 17/38: coAuthorsDBLP
size(A) = (299067, 299067) | nnz(A) = 1955352
Column coloring: 336
timer: 0.352591368
Star coloring: 128
timer: 1.804727382
Acyclic coloring: 115
timer: 2.229698357

Problem 18/38: delaunay_n18
size(A) = (262144, 262144) | nnz(A) = 1572792
Column coloring: 23
timer: 0.09778755
Star coloring: 17
timer: 0.578770509
Acyclic coloring: 7
timer: 0.565640443

Problem 19/38: kron_g500-logn18
size(A) = (262144, 262144) | nnz(A) = 21165908
Column coloring: 49163
timer:<PHONE_NUMBER>72
Star coloring: 4310
timer: 2552.233228622
Acyclic coloring: 1978
timer: 2286.58141312

Problem 20/38: rgg_n_2_18_s0
size(A) = (262144, 262144) | nnz(A) = 3094566
Column coloring: 35
timer: 0.242767916
Star coloring: 27
timer: 1.539946026
Acyclic coloring: 19
timer: 1.372478875

Problem 21/38: m14b
size(A) = (214765, 214765) | nnz(A) = 3358036
Column coloring: 42
timer: 0.695000404
Star coloring: 32
timer: 2.418476703
Acyclic coloring: 18
timer: 1.97721004

Problem 22/38: HTC_336_4438
size(A) = (226340, 226340) | nnz(A) = 783496
Column coloring: 7393
timer: 0.670305142
Star coloring: 7394
timer: 1.025649588
Acyclic coloring: 7393
timer: 18.691909322

Problem 23/38: HTC_336_9129
size(A) = (226340, 226340) | nnz(A) = 762969
Column coloring: 7393
timer: 0.43779486
Star coloring: 7394
timer: 0.927538927
Acyclic coloring: 7393
timer: 17.519127616

Problem 24/38: CurlCurl_1
size(A) = (226451, 226451) | nnz(A) = 2472071
Column coloring: 25
timer: 0.184289404
Star coloring: 18
timer: 0.835749483
Acyclic coloring: 10
timer: 0.872502701

Problem 25/38: al2010
size(A) = (252266, 252266) | nnz(A) = 1230482
Column coloring: 76
timer: 0.099341865
Star coloring: 26
timer: 0.451601529
Acyclic coloring: 9
timer: 0.439798963

Problem 26/38: az2010
size(A) = (241666, 241666) | nnz(A) = 1196094
Column coloring: 137
timer: 0.118326504
Star coloring: 23
timer: 0.626197685
Acyclic coloring: 9
timer: 0.515600282

Problem 27/38: co2010
size(A) = (201062, 201062) | nnz(A) = 974574
Column coloring: 120
timer: 0.077927899
Star coloring: 27
timer: 0.329383883
Acyclic coloring: 8
timer: 0.328657502

Problem 28/38: ga2010
size(A) = (291086, 291086) | nnz(A) = 1418056
Column coloring: 85
timer: 0.106496096
Star coloring: 20
timer: 0.595135744
Acyclic coloring: 10
timer: 0.750242026

Problem 29/38: ia2010
size(A) = (216007, 216007) | nnz(A) = 1021170
Column coloring: 49
timer: 0.13893868
Star coloring: 20
timer: 0.631229113
Acyclic coloring: 8
timer: 0.312675323

Problem 30/38: in2010
size(A) = (267071, 267071) | nnz(A) = 1281716
Column coloring: 54
timer: 0.098204586
Star coloring: 17
timer: 0.614488292
Acyclic coloring: 8
timer: 0.593226184

Problem 31/38: ks2010
size(A) = (238600, 238600) | nnz(A) = 1121798
Column coloring: 54
timer: 0.080683371
Star coloring: 22
timer: 0.487037616
Acyclic coloring: 7
timer: 0.364857674

Problem 32/38: la2010
size(A) = (204447, 204447) | nnz(A) = 980634
Column coloring: 581
timer: 0.074684536
Star coloring: 22
timer: 0.509073618
Acyclic coloring: 11
timer: 0.350915202

Problem 33/38: mn2010
size(A) = (259777, 259777) | nnz(A) = 1227102
Column coloring: 311
timer: 0.0967323
Star coloring: 20
timer: 0.53852985
Acyclic coloring: 9
timer: 0.539063858

Problem 34/38: nc2010
size(A) = (288987, 288987) | nnz(A) = 1416620
Column coloring: 83
timer: 0.109021197
Star coloring: 21
timer: 0.680753053
Acyclic coloring: 11
timer: 0.711910232

Problem 35/38: ok2010
size(A) = (269118, 269118) | nnz(A) = 1274148
Column coloring: 65
timer: 0.098862618
Star coloring: 22
timer: 0.720965241
Acyclic coloring: 8
timer: 0.504435829

Problem 36/38: tn2010
size(A) = (240116, 240116) | nnz(A) = 1193966
Column coloring: 89
timer: 0.104763846
Star coloring: 24
timer: 0.747861327
Acyclic coloring: 9
timer: 0.41374581

Problem 37/38: va2010
size(A) = (285762, 285762) | nnz(A) = 1402128
Column coloring: 102
timer: 0.110662316
Star coloring: 21
timer: 0.521112078
Acyclic coloring: 11
timer: 0.793464474

Problem 38/38: wi2010
size(A) = (253096, 253096) | nnz(A) = 1209404
Column coloring: 60
timer: 0.094892928
Star coloring: 21
timer: 0.586021114
Acyclic coloring: 10
timer: 0.401114694


Make SubImage immutable and add SubImageMut

There's currently only one SubImage type which requires the parent image reference to be mutable. Creating a subimage of an immutable image isn't possible, despite this having obvious use cases. The standard Rust pattern of parallel mutable and immutable accessor types (eg. IterMut and Iter) could be used here. Rename current SubImage with the mutable access to the parent image to SubImageMut and add a new SubImage type that takes an immutable parent reference and only provides read access.

Totally supports this.
I was surprised to see &mut in SubImage's new() method or in GenericImage's sub_image() method.
I associate a SubImage with a slice into a vector for example. It is possible to have a slice to a immutable vector so I though SubImage would work on immutable images too.

The SubImage API seems to have changed recently. I haven't looked into it in more detail yet but maybe it resolves this issue and this can be closed?

I was ready to open a new issue when I stumbled upon it. The documentation is still missing...


Latest conda's libgnutls (version 3.5.19) broken on OSX

This is the reason for the test failure on OSX.
Reported https://github.com/conda-forge/gnutls-feedstock/issues/3.
Pinning to 3.5.17 should fix the issue.

Fixed upstream.


Meus Recursos

Description of the new feature / enhancement
Novidades
Scenario when this would be used?
Atualizações
Supporting information
Avisos

Could you please clarify a bit more, what kind of feature you want to see?
/needinfo


fix(expandable table): safari bug

Describe pull-request
Switched visibility collapse to display:none. Collapse has bad browser support.
Solving issue
Fixes: AB#3025
How to test

Go to storybook link below
Check in Components -> Data table -> Expandable rows
Check that the row can hide/expand correctly.
Make sure to test in safari/firefox.

Suggested test steps

[ ] Browser testing (Chrome, Safari, Firefox)
[ ] Keyboard operability
[ ] Interactive elements have labels.
[ ] Storybook controls
[ ] Design/controls/props is aligned with other components
[ ] Dark/light mode and variants
[ ] Input fields – values should be displayed properly
[ ] Events

Screenshots
Additional context

Had a look in Safari(Version 14.1.2 (166<IP_ADDRESS>.6), and this is how it looks there:

Nice catch! Looks like we are using 'appearence:none' which lacks support in your version. Only 0.81% usage but might be good to fix. I'll commit a fix :)


Clarify whether/how to integrate the SecurityManager

Currently the whole config approach assumes that all the information is available in the whole ClassLoader/application.
If someone want's to guard against such an access, then this should best be done via the SecurityManager. But how to integrate this best?

We might also end up with coming to the conclusion that we don't want to define this in the spec and leave it to the implementations whether they want to have it.


Manage omnibus config api timeout error

Added Timeout exception & error message

I can throw the exception the way you suggested, from where we will return the message, Is it handle at front end hide.?


P4RT-1.1 , update DUT links from 2 to 4

Changed metadata.textproto from TESTBED_DUT_ATE_2LINKS to TESTBED_DUT_ATE_4LINKS, to have a better chance of different nodes getting selected during run.

Pull Request Functional Test Report for #1913 / 2ea8dba57496e7ea46ff4eeb910be57e9e271e5d
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

P4RT-2.1: P4RT Election

Cisco 8000E

P4RT-2.1: P4RT Election

Cisco XRd

P4RT-2.1: P4RT Election

Juniper cPTX

P4RT-2.1: P4RT Election

Nokia SR Linux

P4RT-2.1: P4RT Election

Openconfig Lemming

P4RT-2.1: P4RT Election

Help

@rsindhujha you're modifying p4rt-2.1 instead of p4rt-1.1 (which is stated in the subject). Is this intended?

@rsindhujha you're modifying p4rt-2.1 instead of p4rt-1.1 (which is stated in the subject). Is this intended?

Thanks for pointing out @LimeHat. My bad, modified the wrong file. Fixed it now.

Actually, hold on, I'm not sure the point of this PR. The testbed should specify what the test requires, and this test only request 2 links, right?

On Juniper ptx10001, with 2 port topology there are  chances that both ports are picked from the same FAP. To help ports getting picked from multiple FAPs increasing it to 4 port topology helps.

We are fixing this internally hence the pull is not required anymore, closing!


Recipes

Need recipe for skyroot charm and ideally a new recipe for aegisalt charm (maybe rename to uplander charm, since every charm will have been infused with aegisalt?) so that people arent hecked if they come to the uplands without materials for an aegisalt charm

I'd considered bringing up the idea of a charm update after the vegetation update is finished, since I feel like we need more resources available before we can really deep-dive into charms. My ideas for the prospective Charm Update are as follows:
All charms should be split into their base material and an item that infuses them with an effect, with Skyroot logs used as the most basic material for the weakest charm, and more resources added in further updates. Using better materials means the charm will last longer, and potentially even have stronger potion effects.
For the effect items, I've considered Cloud Daisies being used for slow-falling (which is what they give when used for Suspicious Stew as of right now), and Zephyr Onions being used for regeneration. I don't know what should give Jump Boost, probably a drop from a neutral mob?
For instance, the current Aegisalt Charm would be crafted with a Skyroot log and a Cloud Daisy, and it'd be renamed to something along the line of "Skyroot Charm of Slow Falling", sort of like how potions work.
As for new materials, I've considered what I've been calling Cloudsteel. In essence, clouds spawn near the surface area, and they can be collected with a new tool and condensed into an ingot, which could then be used for crafting charms. I've also considered a charm tier which can't be crafted by players, and only found in dungeon chests, which would incentivise exploration.
That's a lot of stuff to dump on a pretty small recipe issue, but what do you guys think?

I like it


Create a new tag version from the PR that updates permisson_handler

Create a new tag version from this PR (https://github.com/nizwar/screen_capture_event/pull/7) in pub.dev.
So we can use this reference in the pubspec.yml instead of git reference.

same here.
I'm using it by fork this repo


Dont break inittab completely

Append to it instead of creating it from scratch as it has some defaults that are needed for the correct working of the system like openrc starting and so on

merging directly as its needed for alpine


Test F.layer_normalization with large eps

Thanks to #4744, test with larger eps passes, which I mentioned at https://github.com/chainer/chainer/pull/4744#issuecomment-388045474.  I also confirmed the new test failed before merging the fix.

I fixed syntax errors in Python 2.

LGTM!


[Table]  in Selectable Cell Should Take Height of a Cell as for Hitbox

http://jsfiddle.net/bzkzhp39/1/
If there is table with a selectable cell, and there a other cell in same row with content with bigger width, hitbox of  don't take the full height of a cell, but leaves some space on the top and bottom edges
So you see that cell can be selected because of grey background hover, but  onclick fires only when clicking in the center

I've experienced similar problem. Here is some lines of code;

Link

The .selectable class seems overriding some parent attributes.


IPv6 support for BIOS APIs

This issue is related to Ipv6 support for Bios socket source/sink APIs.
I am using opnessl v 0.9.8za and observed Bios API support only IPv4.
OpenSSL/0.9.8za/Src/crypto/bio/bss_conn.c +202
case BIO_CONN_S_CREATE_SOCKET:
/* now setup address */
memset((char *)&c->them,0,sizeof(c->them));
c->them.sin_family=AF_INET;
c->them.sin_port=htons((unsigned short)c->port);
l=(unsigned long)
((unsigned long)c->ip[0]<<24L)|
((unsigned long)c->ip[1]<<16L)|
((unsigned long)c->ip[2]<< 8L)|
((unsigned long)c->ip[3]);
c->them.sin_addr.s_addr=htonl(l);
c->state=BIO_CONN_S_CREATE_SOCKET;
I am planing to add support for Ipv6.
Please confirm if this patch will be acceptable in OpenSSL.

IPv6 support will not be added to 0.9.8. Only important security fixes are being applied to that branch, and support will end completely at the end of this year. @kroeckx has been working on equivalent patches for the master branch. You should check with him before doing work on IPv6 support.


Please add a possibility to switch the light off in homekit when it disconnects (this is for people with old-school wall switches)

Hi!
Describe the idea or improvement
When my yeelight light disconnected from the line with old-school wall switch,  Mode-Day switch is on and light is 100% on too in HomeKit.
Describe the solution you'd like
Please add some option as its done here: Optional per light configuration: offOnDisconnect?: boolean (optional) - switch the light off in homekit when it disconnects (this is for people with old-school wall switches) how its done in https://github.com/cellcortex/homebridge-yeelighter/blob/master/README.md
Additional context

Hi, I do not quite understand the issue. When the light disconnects and the plugin cannot reach it anymore then the status should change to off, does that not happen?

yes, not happen

MiHome:

I noticed that also with other plugins, i think that this is an issue with the new home app which does not properly update the status. As soon as you disconnect your light and the plugin cannot reach it, the light will always return status off, just somehow the home app does not pick it up...

It's my mistake, HB was not on the local network, the connection to the lamps was only through MiCloud.
BTW, it's possible to change the name Mode-Day/Mode-Nights to just Day/Night in plugin?

The names come from the miot spec, you can edit the switches in homekit and change the to what you want, just keep in mind that after a restart it will reset so you would need to rename it again.


Add support for params to contain lists, dicts

This is already on the radar from discussion of resubmit parameters.
At the moment the tpv will not load a parameter that is a dict or a list.  Some parameters that would not be supported at the moment are resubmit, container_override, container_resolvers

Fixed in: https://github.com/galaxyproject/total-perspective-vortex/pull/21


Add --init-alloc-size parameter for fast initial allocation

Often, it is useful to first allocate a big chunk of memory
before continuing to gradually allocate smaller chunks
to cuase stress.
For example, let's say that someone is trying to hit a
certain memory limit of 5GB. In such a case, it is often
useful to first allocate 4GBs in one big chunk fastly,
and then continue stressing the system using allocation
size of 16MB each 5 seconds.
After this PR, the following is possible:
stress -mem-total 5Gi -mem-alloc-size 16Mi -mem-alloc-sleep 5s -init-alloc-size 4Gi
p.s. basing this PR on https://github.com/vishh/stress/pull/5. Will remove once this PR is merged.

@vishh would be happy if you could take a look.


Implement file exists check for executable

In https://github.com/pyansys/pydpf-core/blob/7d0c59796baac823702e38dcc0dcb74098844af0/ansys/dpf/core/server.py#L509 we don't check if the dpf server executable actually exists prior to running it.  This appears to be version dependent and leads to a not so helpful traceback:
>>> model = Model(r'c:\static.rst')

Traceback (most recent call last):

  File "<pyshell#11>", line 1, in <module>

    model = Model(r'c:\static.rst')

  File "C:\Users\<redacted-user>\AppData\Local\Programs\Python\Python39\lib\site-packages\ansys\dpf\core\model.py", line 49, in __init__

    server = dpf.core._global_server()

  File "C:\Users\<redacted-user>\AppData\Local\Programs\Python\Python39\lib\site-packages\ansys\dpf\core\server.py", line 62, in _global_server

    start_local_server()

  File "C:\Users\<redacted-user>\AppData\Local\Programs\Python\Python39\lib\site-packages\ansys\dpf\core\server.py", line 177, in start_local_server

    server = DpfServer(ansys_path, ip, port,as_global= as_global, load_operators = load_operators)

  File "C:\Users\<redacted-user>\AppData\Local\Programs\Python\Python39\lib\site-packages\ansys\dpf\core\server.py", line 281, in __init__

    launch_dpf(ansys_path, ip, port)

  File "C:\Users\<redacted-user>\AppData\Local\Programs\Python\Python39\lib\site-packages\ansys\dpf\core\server.py", line 473, in launch_dpf

    process = subprocess.Popen(run_cmd,

  File "C:\Users\<redacted-user>\AppData\Local\Programs\Python\Python39\lib\subprocess.py", line 951, in __init__

    self._execute_child(args, executable, preexec_fn, close_fds,

  File "C:\Users\<redacted-user>\AppData\Local\Programs\Python\Python39\lib\subprocess.py", line 1420, in _execute_child

    hp, ht, pid, tid = _winapi.CreateProcess(executable, args,

FileNotFoundError: [WinError 2] The system cannot find the file specified

Would be great to implement a version and/or file exists check.

good point @akaszynski yes, we should do this

@akaszynski we are checking if the directory exists:
https://github.com/pyansys/pydpf-core/blob/7d0c59796baac823702e38dcc0dcb74098844af0/ansys/dpf/core/server.py#L488-L509
Does that seem good to you?

@akaszynski, any update?


I can't select processes if i selection begins with text

Brief description of your issue
When i try to select multiple processes selection fails if  i start highlighing with field thaqt has text in it.
Steps to reproduce (optional)

mouse highlight multiple processes starting with field that has text in it
it doesn't work.

Expected behavior (optional)
No response
Actual behavior (optional)
No response
Environment (optional)
Version: 3.0.4905 (2b70d0a)
Microsoft Windows [Version 10.0.22000.675]

You need to use the control key+click or shift key+click selection methods. The drag select won't work in a number of cases.


Is there an error in the code about loss in train.py?

Excuse me, I would like to ask why both loss1 and loss2 in train.py are using l_ri_mag? Shouldn't loss2 use l_wav_mag instead?

I have to confess that it is just an unfinished implementation. I tried to implement the original paper under the single-channel situation. The original paper is based on multi-channel, but I didn't have a relevant dataset. So it is just an imperfect reimplementation. I did not strictly follow the original paper. I guess the only valuable part of this repo is the model.py, which is according to the paper. Due to the lack of the dataset, and I just want to focus on single-channel, I will not complete it in the future. Sorry. Back to your question, I guess you are right! It is my fault.


Added styling for github logo #24

@OsafAliSayed please mention the issue number here with # so that it will be automatically closed

Done please review and let me know if further changes are required.

mention the issue number please so it will automatically close.


panic: index out of range

When I start the program, then go to browser http://myip:9633/metrics
The program raise an error.
Here is the log:
➜  bin git:(master) ✗ sudo ./smartctl_exporter --config=./config.yaml
[Warning] S.M.A.R.T. output reading error: exit status 1
[Warning] The device self-test log contains records of errors. [ATA only] Failed self-tests outdated by a newer successful extended self-test are ignored.
[Error] /dev/sda: Unknown USB bridge [0x0951:0x1666 (0x1075)]
[Error] smartctl returned bad data for device /dev/sda
[Warning] S.M.A.R.T. output reading error: exit status 4
[Warning] SMART status check returned 'DISK OK' but we found that some (usage or prefail) Attributes have been <= threshold at some time in the past.
[Info] Starting on <IP_ADDRESS>:9633/metrics
[Warning] S.M.A.R.T. output reading error: exit status 1
[Warning] The device self-test log contains records of errors. [ATA only] Failed self-tests outdated by a newer successful extended self-test are ignored.
[Error] /dev/sda: Unknown USB bridge [0x0951:0x1666 (0x1075)]
[Error] smartctl returned bad data for device /dev/sda
[Error] Too early collect called for device /dev/sdb
panic: runtime error: index out of range

goroutine 38 [running]:
main.(*SMARTctlInfo).mineVersion(0xc3af64)
	/home/pi/smartctl_exporter/smartctlinfo.go:46 +0x4c0
main.(*SMARTctlInfo).Collect(0xc3af64)

Here are my dir structure
➜  bin git:(master) ✗ tree ./
./
├── config.yaml
└── smartctl_exporter

0 directories, 2 files

Here are the content of config.yaml
smartctl_exporter:
  bind_to: "<IP_ADDRESS>:9633"
  url_path: "/metrics"
  fake_json: no
  smartctl_location: /usr/local/sbin/smartctl
  collect_not_more_than_period: 120s
  devices:
  - /dev/sda
  - /dev/sdb
  #- /dev/sdc
  #- /dev/sdd
  #- /dev/sde
  #- /dev/sdf

The smartctl version is:
➜  bin git:(master) ✗ smartctl --version
smartctl 7.2 2020-12-30 r5155 [armv7l-linux-5.10.17-v7l+] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

smartctl comes with ABSOLUTELY NO WARRANTY. This is free
software, and you are welcome to redistribute it under
the terms of the GNU General Public License; either
version 2, or (at your option) any later version.
See http://www.gnu.org for further details.

smartmontools release 7.2 dated 2020-12-30 at 16:48:30 UTC
smartmontools SVN rev 5155 dated 2020-12-30 at 16:49:18
smartmontools build host: armv7l-unknown-linux-gnueabihf
smartmontools build with: C++14, GCC 8.3.0
smartmontools configure arguments: [no arguments given]

I am seeing this same issue. Pretty much the same config as you, also running on armv7l (openwrt 19.07.7)
here is my config yaml in /etc/smartctl_exporter.yaml:
smartctl_exporter:
bind_to: "<IP_ADDRESS>:9633"
url_path: "/metrics"
fake_json: no
smartctl_location: /usr/sbin/smartctl
collect_not_more_than_period: 40s
devices:

/dev/sda

I have the binary in /usr/bin
smartctl 7.0 2018-12-30 r4883 [armv7l-linux-4.14.221] (localbuild)
It seems to run fine for a moment, and sometimes I get to see the metrics in the browser. Here is the error:
Mon May  3 11:18:26 2021 daemon.info smartctl_exporter[3795]: [Error] Too early collect called for device /dev/sda
Mon May  3 11:18:26 2021 daemon.err smartctl_exporter[3795]: panic: runtime error: index out of range [0] with length 0
Mon May  3 11:18:26 2021 daemon.err smartctl_exporter[3795]:
Mon May  3 11:18:26 2021 daemon.err smartctl_exporter[3795]: goroutine 12 [running]:
Mon May  3 11:18:26 2021 daemon.err smartctl_exporter[3795]: main.(*SMARTctlInfo).mineVersion(0x21d3f64)
Mon May  3 11:18:26 2021 daemon.err smartctl_exporter[3795]:    /home/mark/Code/smartctl_exporter/smartctlinfo.go:46 +0x530
Mon May  3 11:18:26 2021 daemon.err smartctl_exporter[3795]: main.(*SMARTctlInfo).Collect(...)
Mon May  3 11:18:26 2021 daemon.err smartctl_exporter[3795]:    /home/mark/Code/smartctl_exporter/smartctlinfo.go:35
Mon May  3 11:18:26 2021 daemon.err smartctl_exporter[3795]: main.SMARTctlManagerCollector.Collect(0x2090980)
Mon May  3 11:18:26 2021 daemon.err smartctl_exporter[3795]:    /home/mark/Code/smartctl_exporter/main.go:37 +0x180
Mon May  3 11:18:26 2021 daemon.err smartctl_exporter[3795]: github.com/prometheus/client_golang/prometheus.(*wrappingCollector).Collect.func1(0x200a140, 0x2090980)
Mon May  3 11:18:26 2021 daemon.err smartctl_exporter[3795]:    /home/mark/go/pkg/mod/github.com/prometheus/client_golang@v1.7.1/prometheus/wrap.go:127 +0x30
Mon May  3 11:18:26 2021 daemon.err smartctl_exporter[3795]: created by github.com/prometheus/client_golang/prometheus.(*wrappingCollector).Collect
Mon May  3 11:18:26 2021 daemon.err smartctl_exporter[3795]:    /home/mark/go/pkg/mod/github.com/prometheus/client_golang@v1.7.1/prometheus/wrap.go:126 +0x4c
Mon May  3 11:18:26 2021 daemon.info procd: Instance smartctl_exporter::instance1 s in a crash loop 6 crashes, 5 seconds since last crash
Did you manage to resolve your issue?

When I start the program, then go to browser http://myip:9633/metrics
The program raise an error.
Here is the log:
➜  bin git:(master) ✗ sudo ./smartctl_exporter --config=./config.yaml
[Warning] S.M.A.R.T. output reading error: exit status 1
[Warning] The device self-test log contains records of errors. [ATA only] Failed self-tests outdated by a newer successful extended self-test are ignored.
[Error] /dev/sda: Unknown USB bridge [0x0951:0x1666 (0x1075)]
[Error] smartctl returned bad data for device /dev/sda
[Warning] S.M.A.R.T. output reading error: exit status 4
[Warning] SMART status check returned 'DISK OK' but we found that some (usage or prefail) Attributes have been <= threshold at some time in the past.
[Info] Starting on <IP_ADDRESS>:9633/metrics
[Warning] S.M.A.R.T. output reading error: exit status 1
[Warning] The device self-test log contains records of errors. [ATA only] Failed self-tests outdated by a newer successful extended self-test are ignored.
[Error] /dev/sda: Unknown USB bridge [0x0951:0x1666 (0x1075)]
[Error] smartctl returned bad data for device /dev/sda
[Error] Too early collect called for device /dev/sdb
panic: runtime error: index out of range

goroutine 38 [running]:
main.(*SMARTctlInfo).mineVersion(0xc3af64)
	/home/pi/smartctl_exporter/smartctlinfo.go:46 +0x4c0
main.(*SMARTctlInfo).Collect(0xc3af64)

Here are my dir structure
➜  bin git:(master) ✗ tree ./
./
├── config.yaml
└── smartctl_exporter

0 directories, 2 files

Here are the content of config.yaml
smartctl_exporter:
  bind_to: "<IP_ADDRESS>:9633"
  url_path: "/metrics"
  fake_json: no
  smartctl_location: /usr/local/sbin/smartctl
  collect_not_more_than_period: 120s
  devices:
  - /dev/sda
  - /dev/sdb
  #- /dev/sdc
  #- /dev/sdd
  #- /dev/sde
  #- /dev/sdf

The smartctl version is:
➜  bin git:(master) ✗ smartctl --version
smartctl 7.2 2020-12-30 r5155 [armv7l-linux-5.10.17-v7l+] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

smartctl comes with ABSOLUTELY NO WARRANTY. This is free
software, and you are welcome to redistribute it under
the terms of the GNU General Public License; either
version 2, or (at your option) any later version.
See http://www.gnu.org for further details.

smartmontools release 7.2 dated 2020-12-30 at 16:48:30 UTC
smartmontools SVN rev 5155 dated 2020-12-30 at 16:49:18
smartmontools build host: armv7l-unknown-linux-gnueabihf
smartmontools build with: C++14, GCC 8.3.0
smartmontools configure arguments: [no arguments given]

I did not put this down. This open PR fixed it for me:
https://github.com/Sheridan/smartctl_exporter/pull/18

Same issue on current git master:
root# ./smartctl_exporter --config=./smartctl_exporter.yaml
[Info] Starting on <IP_ADDRESS>:9633/metrics
[Error] Too early collect called for device /dev/sda
[Error] Too early collect called for device /dev/sdb
[Error] Too early collect called for device /dev/sdc
[Error] Too early collect called for device /dev/sdd
[Error] Too early collect called for device /dev/sde
[Error] Too early collect called for device /dev/sdf
[Error] Too early collect called for device /dev/sdg
[Error] Too early collect called for device /dev/sdh
[Error] Too early collect called for device /dev/sdi
[Error] Too early collect called for device /dev/sdj
[Error] Too early collect called for device /dev/sdk
[Error] Too early collect called for device /dev/sdl
panic: runtime error: index out of range [0] with length 0

goroutine 63 [running]:
main.(*SMARTctlInfo).mineVersion(0xc0003c3ec0)
	/home/baryluk/prometheus/smartctl_exporter/smartctlinfo.go:46 +0xbf6
main.(*SMARTctlInfo).Collect(...)
	/home/baryluk/prometheus/smartctl_exporter/smartctlinfo.go:35
main.SMARTctlManagerCollector.Collect(0xc0003ba000)
	/home/baryluk/prometheus/smartctl_exporter/main.go:37 +0x23a
github.com/prometheus/client_golang/prometheus.(*wrappingCollector).Collect.func1(0xc00021a690, 0xc0003ba000)
	/home/baryluk/go/pkg/mod/github.com/prometheus/client_golang@v1.7.1/prometheus/wrap.go:127 +0x3d
created by github.com/prometheus/client_golang/prometheus.(*wrappingCollector).Collect
	/home/baryluk/go/pkg/mod/github.com/prometheus/client_golang@v1.7.1/prometheus/wrap.go:126 +0x6b
root# ls -l /dev/sd
sda   sda1  sdb   sdb1  sdc   sdc1  sdd   sdd1  sde   sde1  sdf   sdf1  sdg   sdg1  sdh   sdh1  sdh2  sdi   sdi1  sdj   sdj1  sdk   sdk1  sdl   sdl1  sdm   sdm1  sdn   sdn1

There is a bug.

When https://github.com/Sheridan/smartctl_exporter/blob/e27581d56ad80340fb076d3ce22cef337ed76679/readjson.go#L94 returning an empty Json object {}
In https://github.com/Sheridan/smartctl_exporter/blob/e27581d56ad80340fb076d3ce22cef337ed76679/smartctlinfo.go#L46 it is failing because there is no validation for empty jsonVersion and smartctlVersion variables.

@Sheridan Максим, почини пожалуйста, людям очень надо! ;)
To fix it either, the validation must be added, or instead of an empty Json must be returned something like {"json_format_version":[0,0],"smartctl": {"version": [0,0]}
OR simply update YAML config with
  collect_not_more_than_period: 0s

and this problem will be resolved, because readjson.go will always return correct Json object.
@Sheridan would you please fix it? Thanks!

I think this may be fixed with the latest release.

The panic: runtime error: index out of range crash in mineVersion was fixed in #93. The Too early collect called for device error was fixed by the caching thing in #18.


Add support for future pay scales

User need
As a member of hiring staff
I need to only see current pay scales
So that I am up-to-date with the job market
Adds #current scope to PayScale which is any records that have a start date earlier than today and an end date later than today.

 Add support for future payscales


Total Budget

Total Budget
User Story
AS A business owner
I WANT to be able to view and manage the departments, roles, and employees in my company
SO THAT I can organize and plan my business
Acceptance Criteria
GIVEN a command-line application that accepts user input
WHEN I choose 'Get Total Budget By Department'
THEN I am presented with the total utilized budget of a department—in other words, the combined salaries of all employees in that department.

This has been completed


brightness filter bug

if pixels value over 255, I guess that occur overflow.
I think that bacause of ndarray. need to check.

fixed #11


DuplicateKeyError in meta.yaml

When using ruamel_yaml module in python script I get DuplicateKeyError exception. Key = summary. So as you can see you have 2 concurrent summary keys in about section of meta.yaml. Please fix it.

Additionally, about.dev_url is duplicated too.


Train models for each major entity class

Need to train models for each major entity class: PRGE, LIVB, DISO, CHED. The first three are fairly straight-forward. As for the last, there are multiple levels of granularity to the entity annotations, for now, might just cheat and collapse everything under the CHED tag.
For relations, we are at the mercy of what datasets are available. Right now, we could train a model for adverse drug events using the ADE corpus.
There should be a base and large version for each model. In the case of BERT, this would correspond to whether the BERT base or large model was used. Any model not implemented should raise a NotImplementedError (see #155).
Finally, the model names should follow a convention. Maybe [model-name]-[entity or relation]-[base or large], e.g. bert-for-ner-prge, bert-for-ner-prge-lg. See PyTorch Transformers or SpaCy for inspiration.
BERT
Entities

[ ] Train PRGE-base
[ ] Train PRGE-large
[ ] Train LIVB-base
[ ] Train LIVB-large
[ ] Train DISO-base
[ ] Train DISO-large
[ ] Train CHED-base
[ ] Train CHED-large

Relations

[ ] Train ADE

Too bad the project is dead, it seemed like a great tool.
Thanks for the pointers.


Question about the roadmap or TODOs

Is there a roadmap or are there any TODOs regarding the development? After checking the code, it looks like main components such as FD and memberlist are there.  I am interested in this project but do not find related information in contributing.md or the issues section in github.
Thanks

Hi @chlin501,
Yes most of components are in place.
The biggest part left is testing. I tried to run this on k8 with 100 nodes and it was working pretty reasonable but again it should be done in more scientific way - experiment, logs and conclusions.
Next is adding reasonable logging and metrics. Since logging and metrics are part of the core in 2.0 probably we need to migrate first.
It would great if you will help me because recently I don't have that much time for this project. let me know if you are interested we can connect on Discord or Zoom.

Hi @pshemass I sent you a message in Discord but maybe you are not using it; so posting it here as well. I am interested in this, and would like to work on those tasks. How can I connect you through Discord or Zoom? Thanks.


Adding Unit Tests for Timer

Resolves #423

Coverage increased (+0.2%) to 83.372% when pulling e3114dda126a68b5464c4651ff313c0d5712249e on HuangDave:timer_unit_test into d7b4ef4973e18227dfbe62be0f4dd514f23d8cd6 on kammce:master.

CI is broken for one of the OSX images. I'll go and fix that. I think you should be able to merge this yourself without me. But if you cannot ping me when the changes are made and I can force merge it in.


[Bug]the conversion algorithm starts failing when you switch branches in GIT connected apps. You need to manually refresh the page for the algorithm to work

https://www.loom.com/share/e99f1e2ded4b491bb879c62cc1872a83

@nayan-rafiq need your help on this one, The save layout call is returning 500, with just internal server error. Don't have much information in the error to debug this.


[ROCM] Add Thrust support

This adds rocThrust support for our rocm backend, which can be used for sorting and scan.
https://github.com/ROCmSoftwarePlatform/rocThrust
Use "rocm -libs=thrust" to enable thrust based sort and scan.
contrib/rocthrust/thrust.cc code is identical to contrib/thrust/thrust.cu used by CUDA backend. The same thrust code works on both CUDA and AMD.
@mbrookhart @csullivan @antinucleon

@tkonolige @mbrookhart Thanks for review, it should be ready to go. This can be used for benchmarking the new TIR sort @mbrookhart is cooking.

@mbrookhart Yes, I wanted to reuse thrust.cu as is, by adding the following to ROCM.cmake:
file(GLOB CONTRIB_THRUST_SRC src/runtime/contrib/thrust/*.cu)

But unlike for CUDA, cmake doesn't recognize that this .cu file needs to be compiled by the same CXX compiler (hipcc), so it will not be compiled. I think CMake has a special support for NVCC and .cu file.

Maybe pytorch people have a solution to the duplication problem. But my cmake-fu is too low and I have no interest in learning about cmake :)

@tkonolige @csullivan Any other change requests or are you happy?

@masahi You can use set_source_files_properties(src/runtime/contrib/thrust/thrust.cu PROPERTIES LANGUAGE CXX).

Great set_source_files_properties worked! I removed rocthrust/thrust.cc, the same thrust.cu is used by CUDA and rocm now cc @mbrookhart

Thanks @mbrookhart @tkonolige @csullivan


Restore ci-link

Selector update

Is it supposed to appear before the "Private" label?

@kidonng I don't know. I don't remember how it was before

https://github.com/sindresorhus/refined-github/blob/6842f86e937502476997206d0003e17d703dd513/source/features/ci-link.tsx#L29
So the location hasn't changed, it just lacks an appropriate margin.


Code for segmenting a single image

With the original segment anything all I have to do to segment a single image is downloading the checkpoint and running
from segment_anything import SamPredictor, sam_model_registry
sam = sam_model_registry["<model_type>"](checkpoint="<path/to/checkpoint>")
predictor = SamPredictor(sam)
predictor.set_image(<your_image>)
masks, _, _ = predictor.predict(<input_prompts>)

How can I do something similar in FastSAM3D? I downloaded the FastSAM3D checkpoint and have a 3D image with prompts ready. How do  use FastSAM3D to segment my image using my prompts?

You could use infer.sh, and modify the parameter as you want.
vp means visualization path you want to output, tdp mean the image you want to used for segmenting.
python validation.py --seed 2023
-vp ./results/vis_sam_med3d
-tdp data/initial_test_dataset/total_segment -nc 1

Regarding this issue, I have my data set in the specified format and have saved the FastSam3D checkpoint locally. When I run infer.sh I experience errors when loading the model. They are regarding missing encoder blocks. Additionally, when looking through the validation.py file I notice many functions refer to tuning the model. In my case, I do not want to tune the model. I want to test the model's segmentation on my data. Any help with this would be greatly appreciated.
Here is my error message below.
RuntimeError: Error(s) in loading state_dict for Sam3D:
Missing key(s) in state_dict: "image_encoder.blocks.0.norm1.weight", "image_encoder.blocks.0.norm1.bias", "image_encoder.blocks.0.attn.rel_pos_d", "image_encoder.blocks.0.attn.rel_pos_h", "image_encoder.blocks.0.attn.rel_pos_w", "image_encoder.blocks.0.attn.qkv.weight", "image_encoder.blocks.0.attn.qkv.bias", "image_encoder.blocks.0.attn.proj.weight", "image_encoder.blocks.0.attn.proj.bias", "image_encoder.blocks.1.norm1.weight", "image_encoder.blocks.1.norm1.bias", "image_encoder.blocks.1.attn.rel_pos_d", "image_encoder.blocks.1.attn.rel_pos_h", "image_encoder.blocks.1.attn.rel_pos_w", "image_encoder.blocks.1.attn.qkv.weight", "image_encoder.blocks.1.attn.qkv.bias", "image_encoder.blocks.1.attn.proj.weight", "image_encoder.blocks.1.attn.proj.bias", "image_encoder.blocks.6.norm1.weight", "image_encoder.blocks.6.norm1.bias", "image_encoder.blocks.6.attn.rel_pos_d", "image_encoder.blocks.6.attn.rel_pos_h", "image_encoder.blocks.6.attn.rel_pos_w", "image_encoder.blocks.6.attn.qkv.weight", "image_encoder.blocks.6.attn.qkv.bias", "image_encoder.blocks.6.attn.proj.weight", "image_encoder.blocks.6.attn.proj.bias", "image_encoder.blocks.6.norm2.weight", "image_encoder.blocks.6.norm2.bias", "image_encoder.blocks.6.mlp.lin1.weight", "image_encoder.blocks.6.mlp.lin1.bias", "image_encoder.blocks.6.mlp.lin2.weight", "image_encoder.blocks.6.mlp.lin2.bias", "image_encoder.blocks.7.norm1.weight", "image_encoder.blocks.7.norm1.bias", "image_encoder.blocks.7.attn.rel_pos_d", "image_encoder.blocks.7.attn.rel_pos_h", "image_encoder.blocks.7.attn.rel_pos_w", "image_encoder.blocks.7.attn.qkv.weight", "image_encoder.blocks.7.attn.qkv.bias", "image_encoder.blocks.7.attn.proj.weight", "image_encoder.blocks.7.attn.proj.bias", "image_encoder.blocks.7.norm2.weight", "image_encoder.blocks.7.norm2.bias", "image_encoder.blocks.7.mlp.lin1.weight", "image_encoder.blocks.7.mlp.lin1.bias", "image_encoder.blocks.7.mlp.lin2.weight", "image_encoder.blocks.7.mlp.lin2.bias", "image_encoder.blocks.8.norm1.weight", "image_encoder.blocks.8.norm1.bias", "image_encoder.blocks.8.attn.rel_pos_d", "image_encoder.blocks.8.attn.rel_pos_h", "image_encoder.blocks.8.attn.rel_pos_w", "image_encoder.blocks.8.attn.qkv.weight", "image_encoder.blocks.8.attn.qkv.bias", "image_encoder.blocks.8.attn.proj.weight", "image_encoder.blocks.8.attn.proj.bias", "image_encoder.blocks.8.norm2.weight", "image_encoder.blocks.8.norm2.bias", "image_encoder.blocks.8.mlp.lin1.weight", "image_encoder.blocks.8.mlp.lin1.bias", "image_encoder.blocks.8.mlp.lin2.weight", "image_encoder.blocks.8.mlp.lin2.bias", "image_encoder.blocks.9.norm1.weight", "image_encoder.blocks.9.norm1.bias", "image_encoder.blocks.9.attn.rel_pos_d", "image_encoder.blocks.9.attn.rel_pos_h", "image_encoder.blocks.9.attn.rel_pos_w", "image_encoder.blocks.9.attn.qkv.weight", "image_encoder.blocks.9.attn.qkv.bias", "image_encoder.blocks.9.attn.proj.weight", "image_encoder.blocks.9.attn.proj.bias", "image_encoder.blocks.9.norm2.weight", "image_encoder.blocks.9.norm2.bias", "image_encoder.blocks.9.mlp.lin1.weight", "image_encoder.blocks.9.mlp.lin1.bias", "image_encoder.blocks.9.mlp.lin2.weight", "image_encoder.blocks.9.mlp.lin2.bias", "image_encoder.blocks.10.norm1.weight", "image_encoder.blocks.10.norm1.bias", "image_encoder.blocks.10.attn.rel_pos_d", "image_encoder.blocks.10.attn.rel_pos_h", "image_encoder.blocks.10.attn.rel_pos_w", "image_encoder.blocks.10.attn.qkv.weight", "image_encoder.blocks.10.attn.qkv.bias", "image_encoder.blocks.10.attn.proj.weight", "image_encoder.blocks.10.attn.proj.bias", "image_encoder.blocks.10.norm2.weight", "image_encoder.blocks.10.norm2.bias", "image_encoder.blocks.10.mlp.lin1.weight", "image_encoder.blocks.10.mlp.lin1.bias", "image_encoder.blocks.10.mlp.lin2.weight", "image_encoder.blocks.10.mlp.lin2.bias", "image_encoder.blocks.11.norm1.weight", "image_encoder.blocks.11.norm1.bias", "image_encoder.blocks.11.attn.rel_pos_d", "image_encoder.blocks.11.attn.rel_pos_h", "image_encoder.blocks.11.attn.rel_pos_w", "image_encoder.blocks.11.attn.qkv.weight", "image_encoder.blocks.11.attn.qkv.bias", "image_encoder.blocks.11.attn.proj.weight", "image_encoder.blocks.11.attn.proj.bias", "image_encoder.blocks.11.norm2.weight", "image_encoder.blocks.11.norm2.bias", "image_encoder.blocks.11.mlp.lin1.weight", "image_encoder.blocks.11.mlp.lin1.bias", "image_encoder.blocks.11.mlp.lin2.weight", "image_encoder.blocks.11.mlp.lin2.bias".
size mismatch for image_encoder.blocks.2.attn.rel_pos_d: copying a param with shape torch.Size([15, 128]) from checkpoint, the shape in current model is torch.Size([15, 64]).
size mismatch for image_encoder.blocks.2.attn.rel_pos_h: copying a param with shape torch.Size([15, 128]) from checkpoint, the shape in current model is torch.Size([15, 64]).
size mismatch for image_encoder.blocks.2.attn.rel_pos_w: copying a param with shape torch.Size([15, 128]) from checkpoint, the shape in current model is torch.Size([15, 64]).
size mismatch for image_encoder.blocks.3.attn.rel_pos_d: copying a param with shape torch.Size([15, 128]) from checkpoint, the shape in current model is torch.Size([27, 64]).
size mismatch for image_encoder.blocks.3.attn.rel_pos_h: copying a param with shape torch.Size([15, 128]) from checkpoint, the shape in current model is torch.Size([27, 64]).
size mismatch for image_encoder.blocks.3.attn.rel_pos_w: copying a param with shape torch.Size([15, 128]) from checkpoint, the shape in current model is torch.Size([27, 64]).
size mismatch for image_encoder.blocks.4.attn.rel_pos_d: copying a param with shape torch.Size([15, 128]) from checkpoint, the shape in current model is torch.Size([27, 64]).
size mismatch for image_encoder.blocks.4.attn.rel_pos_h: copying a param with shape torch.Size([15, 128]) from checkpoint, the shape in current model is torch.Size([27, 64]).
size mismatch for image_encoder.blocks.4.attn.rel_pos_w: copying a param with shape torch.Size([15, 128]) from checkpoint, the shape in current model is torch.Size([27, 64]).
size mismatch for image_encoder.blocks.5.attn.rel_pos_d: copying a param with shape torch.Size([15, 128]) from checkpoint, the shape in current model is torch.Size([15, 64]).
size mismatch for image_encoder.blocks.5.attn.rel_pos_h: copying a param with shape torch.Size([15, 128]) from checkpoint, the shape in current model is torch.Size([15, 64]).
size mismatch for image_encoder.blocks.5.attn.rel_pos_w: copying a param with shape torch.Size([15, 128]) from checkpoint, the shape in current model is torch.Size([15, 64]).


Mdtraj convert

Description
I wrote this code initially to be able to quickly convert old legacy hoomdxml files to mbuild compounds (without some of the losses of info from mdtraj or mdanalysis).  This is just a quick code to load an mdtraj trajectory into the hoomdxml_reader system class, so I don't have to end up changing the codes that rely upon this library when dealing with a hoomd gsd file.
Note: While mbuild does allow you to convert from mdtraj to a compound, the gsd files (for hoomd) I'm dealing with keep causing some issues (as it is treating the entire system as one giant molecule that has 44K sites). I don't really want all molecules merged into a single compound, but rather each molecule exported to it's own separate compound.  I'll explore the conversion issue in mbuild later.
Edit:  While a function to parse a mdtraj trajectory was added, it seemed easier to just add in a function to directly read gsd files (since mdtraj does not consider all relevant information in the gsd file).  I will take this general code and create a PR in mbuild as it seems to be lacking a native gsd reader.
Todos
Notable points that this PR has either accomplished or will accomplish.

[x] set up System class based on an mdtraj trajectory.
[x] add tests
[x] improve doc strings

Status

[ ] Ready to go

Codecov Report

Merging #6 (ca5fa81) into main (0823bf7) will decrease coverage by 12.82%.
The diff coverage is 58.11%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files


fix(decision-article): remove unnecessary css placeholder

Overview
This PR removes an unnecessary css rule which showed an alternative type of placeholder in decision articles.
Before
https://github.com/user-attachments/assets/49f753eb-7f5f-4c0d-b91d-4bd1d73b2899
After

connected issues and PRs:
None
How to test/reproduce

Start the dummy app
Insert a decision with an article
Remove the placeholder within the article
Ensure that no css-placeholder is shown

Challenges/uncertainties
This was probably a remnant of the article-structures POC where I tried out css placeholders.
Checks PR readiness

[x] UI: works on smaller screen sizes
[x] UI: feedback for any loading/error states
[x] Check if dummy app is correctly updated
[x] Check cancel/go-back flows
[x] changelog
[x] npm lint
[x] no new deprecations

Maybe we should also remove the say-empty class from the structure?
{{if this.isEmpty "say-empty" ""}}


Add vector database semantic search chain

basically a wrapper on this (https://github.com/hwchase17/langchain/blob/master/examples/embeddings.ipynb) that synthesizes the found documents to come up with an answer
i will actually probably tackle this this weekend (bc its blocking a demo i want to get out), but happy to pair it if you have time this weekend


Iterate over all events providing all information available

Adressing #212 , I think it would just be better to provide an iterator that yields all events, providing what information is available.
So a non triggered event would only contain mc_shower and mc_event (and possibly the photons) while a triggered event would additionally contain the telescope data / array trigger information.
Like this, the simulated events info could be generated in the same event loop as the normal analysis.

I like it.

Yes this would be perfect


Referece search query does not triger on punctuation characters

If I invoke "find refrences" when the cursor is on a puncuation character, the editor seems to bypass the server and says "no results" without making any requests:

However, there are valid cases to invoke "find usages" on a punctuation character:

in languages with operator overloading, searching for usages of + is a pretty natural thing to do
In Kotlin, searching for ( in data class Point(val x, val y) will search for constructor calls (this is the feature we are trying to mimic in rust-analyzer)

I've tested and in Emacs I can ref-search punctuation. It's interesting that goto definition does not try to check if thing at point is an identifier.

Moving to VS Code since the LSP client library doesn't receive the call in the first place.


templates: replace alpine with alpine-image

The old ISO9660-based alpine template is still available as alpine-iso.
 Merging,


Tensor-Parallelism general support

This PR provides support for model parallelism during inference without the need for injecting the kernels.
Add the PR in DeepSpeed-Example branch and verify the tensor-parallelism functionality on different model architectures:

Bert
Roberta
GPT2
GPT-Neo
GPT-J
Wav2vec2
T5

cc: @stas00 @hyunwoongko

I will analyze this today and apply it to oslo. thank you.
cc @stas00 @RezaYazdaniAminabadi

I will analyze this today and apply it to oslo.
cc @stas00 @RezaYazdaniAminabadi

Thanks a lot @hyunwoongko for the thorough review on this PR. I will use some of your feedback to make this stronger.


PLY surface not showing colors

Using NGL 2.4.0, I loaded the outname.ply from EDTSurf using the examples/webapp.html but it only display the surface in white.

Did this used to work in older versions of NGL? (I never used PLY surfaces properly, though I helped with some of the porting recently).
Looking at the code we don't parse the color data in PLYLoader, though the parser is capable of doing so (it's explicitly disabled).

I don't think it worked, at least it is the same using the 2.0 from the web.
Where in the code disabled?


Tag consumer version before publishing pacts

The webhooks are not firing correctly because the tags have to belong on the consumer version before the pact is published.
The call to create the tag will auto create the relevant pacticipant.

Related to https://github.com/pact-foundation/pact_broker/issues/270

Version 3.6.8 has been released with this fix

Thanks!


Misleading aws_ssm_parameter_store ERROR message when IAM permissions are lacking

Cookbook version
7.5
Chef-client version
12.22
Platform Details
AWS EC2 ubuntu and aws linux
Scenario:
When I attempt to use aws_ssm_parameter_store on an instance with a locked down IAM role/profile that didn't permit SSM:GetParameter IAM permissions, an ERROR: value is required is thrown. I think the error message should point to IAM permissions.
Steps to Reproduce:
Run an
aws_ssm_parameter_store 'get decrypted_value' do
  name '/testkitchen/EncryptedStringDefaultKey'
  return_key 'decrypted_value'
  with_decryption true
  action :get
end

on an ec2 instance that has an IAM profile/role that doesn't permit SSM:GetParameter
Expected Result:
An error message pointing to the IAM permissions issue would be nice.
Actual Result:
Received an ERROR: value is required message.

I'm guessing whats needed is after the request: https://github.com/chef-cookbooks/aws/blob/v8.0.3/resources/ssm_parameter_store.rb#L50 we should check if we were able to sucessfully retrieve and throw a better error message before trying to assign it.


Improve element type inference

I made some changes to the element.ts to make typescript smarter causing less as casts.
I also separated Avatar and TaskList from the other elements so that you don't need to write logic to extract them from the other elements.
Open to any feedback!

LGTM, @tpatel could you review also?

I love that you've moved the Avatar and Tasklist states outside of the element state ❤
Can you share why you've moved the optional url from the TElement to each element?

I love that you've moved the Avatar and Tasklist states outside of the element state ❤
Can you share why you've moved the optional url from the TElement to each element?

I originally did that because I added Input Widget elements (see PoC PR) that didn't have a url property. Right now you can probably put it back into the base class but I imagine that in the future elements will arrive again that don't have a url.

Thanks for sharing your explanation! Could you move the url back into the element? The reason is that at the moment, we are setting a url when we persist an element:
https://github.com/Chainlit/chainlit/blob/ba72a06ac733dda65de19a5212d262dfbbff4f30/src/chainlit/element.py#L86
So all elements become files with a url, and you use the element url when viewing a conversation in the history tab.

I've added url back into the element.


README: Update with the new pink noise file

The new addition of pink noise is not shown in the README.

Resolved.


Deblock

Setup for the loop filter.  This adds some infrastructure we might as well start using soon, and given the massive rebases and work going on in parallel in nearby code, no need to hold off for a completed loop filter megamerge.
As of now, no functional change.

On Wed, Aug 22, 2018 at 12:14 PM Yushin Cho<EMAIL_ADDRESS>wrote:

@ycho approved this pull request.

Can you please consider renaming 'loop_filter' more specifically so
that they stand for deblock only and not for other kinds of loop filters,
such as CDEF and Loop Restoration?
The "DeblockState;" is nice example.

I had actually renamed absolutely everything, and the complete naming
disconnect with the spec (mostly what I'm implementing from) was becoming
progressively harder to follow.  But I think I will in fact rename things
more thoroughly as I continue.

You might also consider put all loop filter code in new separate file,
src/deblock.rs, as is with CDEF.

I am in fact doing that.  Existing pattern had this code go into lib.rs
er... encoder.rs instead.  I wanted that to land because the rest is mostly
standalone in deblock.rs.


'Why' output for blacklisted user appends http: even when there is no link

When a user is blacklisted via the API rather than from chat, the 'why' data for the post states that the user was blacklisted by metasmoke. However, Smokey assumes that it will be recieving a link, so it automatically adds http: (shouldn't it prepend https: instead?). This means that sometimes the output says

Blacklisted for < bla > (< MS post >) by http:metasmoke

FOR SCIENCE

Also for science


Make use of responseType=blob conditional

At the moment, the polyfill sets responseType='blob' unconditionally.
However, for the purpose of using <link rel="preload" for non-blob responses, the above responseType shouldn't be set in some cases.
I'm not sure which way is the best, maybe adding a responseType to supports object and then exposing it for modification on fetch similarly to polyfill = true would make sense?

Related to, and possible duplicate of, #481.

t

Since https://github.com/github/fetch/pull/752 was merged, we no longer unconditionally set the responseType to blob.
I'll close this issue as I believe it is now resolved. If it is still an issue please comment and I will reopen and investigate :-)


Docker container for nodes?

Hello,
Has any work been done on a node image?
Thanks.

@loth
do you mean the docker image for cloudstack-agent service ?
I wonder how the cloudstack-agent process in docker container perform some command on the kvm  host, for example virsh, qemu, some scripts, shell commands.

Yeah for the agent service, basically so we can dockerize a full hypervisor
Openstack does this in this project https://github.com/openstack/kolla maybe worth a look?

Yeah for the agent service, basically so we can dockerize a full hypervisor
Openstack does this in this project https://github.com/openstack/kolla maybe worth a look?

@loth
interesting
as I understand, some services like cloudstack-agent, libvirt (and other dependencies) are running in the container, while vms are running on the hypervisor, is it right  ?

Yes i believe they expose the qemu-kvm device to a special container which houses the VMs

I see. you want a docker container to mock a kvm host and create vms inside it, right ?
for test purpose, it should be feasible.  I think nobody will use it in production :smile:

Maybe I am wrong
cloudstack agent looks like a combinaton of nova, neutron, it also manages volumes ( by libvirt or access storage directly).
It looks kolla can create containers for libvirt and openvswitch. I am able to manage vms on a kvm host using libvirt.
However, for neutron and storage, I do not find a doc saying they can use containers .
If we run cloudstack-agent in a container, it is difficult to manage the network and storage configurations.


Cannot recreate container with multiple networks

Bug description
When trying to "recreate" a container on multiple networks, whether via UI or webhook, I receive a 500 error.
{"message":"Error updating service","details":"create container error: Error response from daemon: Container cannot be connected to network endpoints: bridge, price"}

Expected behavior
Recreate as designed.
Portainer Logs
No applicable logs.
Steps to reproduce the issue:

Create a user bridge network.
Add a new container, put it on the default bridge network.
Attach it to the bridge network you made in step (1).
Try to recreate it

Technical details:

Portainer version: BE 2.17.1
Docker version (managed by Portainer): 23.0.1
Platform (windows/linux): Linux ARM
Command used to start Portainer: docker run -d -p 8000:8000 -p 9443:9443 --name portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ee:latest
Browser: Brave v1.50.114
Use Case: Using Portainer in a Commercial setup.
Have you reviewed our technical documentation and knowledge base? Yes

Additional context
I noticed there were some related issues. One commenter in #8507 reports it, but that issue is a combination of several issues that lead to the same status code. It is also reported in the comments of #2185, but that issue is closed.

@allen-pattern
Related:  https://github.com/portainer/portainer/issues/8507#issuecomment-1442767817
We have an internal issue logged to address.  I do not yet have a timeline or release.
Thanks!

This seems to be fixed in 2.18.1. Thanks!

Is this fix not implemented in the CE version? I have this exact issue on version 2.18.4 Community Edition.
Have to remove all but one network before rebuilding / editing a container, very annoying for development!
Cheers

CE 2.19.0
Still facing this issue, having to use a stack for everything, otherwise I lose the secondary network when restarting.

Same issue here. i have Portainer CE 2.19.4. trying to upgrade from CE to BE. everytime i change the license. the updater container gets an error: "error":"Unable to create new container: Error response from daemon: Container cannot be created with multiple network endpoints: Apps, bridge","time":1711227796,"caller":"/home/runner/work/portainer-updater/portainer-updater/dockerstandalone/update.go:75


Show More errors bug

I am not able to expand lists of error cells using the report, both on the site and through command line generated html. Using Test B errors.csv

Sorry, repeat issue on other repository


Inconsistent ESM adherence causes ERR_MODULE_NOT_FOUND

When I run npm i solid-swr && node -e 'const {useSwr} = import("solid-swr");' nodejs throws the following error. I experience this error in node 18, 20, and 22. I believe this is because this package uses "type": "module" in package.json, but also ships .js as an extension throughout the dist directory (instead of .mjs). Renaming the appropriate files to .mjs fixes the problem, but this may be undesirable for other reasons.
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/home/taylor1791/src/tmp/node_modules/solid-swr/dist/core' imported from /home/taylor1791/src/tmp/node_modules/solid-swr/dist/index.js
    at finalizeResolution (node:internal/modules/esm/resolve:257:11)
    at moduleResolve (node:internal/modules/esm/resolve:913:10)
    at defaultResolve (node:internal/modules/esm/resolve:1037:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:650:12)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:599:25)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:582:38)
    at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:241:38)
    at ModuleJob._link (node:internal/modules/esm/module_job:132:49) {
  code: 'ERR_MODULE_NOT_FOUND',
  url: 'file:///home/taylor1791/src/tmp/node_modules/solid-swr/dist/core'
}

I discovered this problem while I was using vitest. If any tested file imports solid-swr the same error occurs since vitest appears to follow nodejs' module resolution algorithm.

Thanks for the issue!
Yeah this is because I wanted to avoid adding extra build steps into the library, right now i just run tsc and publish that.
To fix this i would need to use some 3rd party bundler to ship both esm and cjs, maybe you have some suggestions on what to use?

Or maybe i can try to specify tsc to build different versions,
In any case ill check it out

My experiments indicate that your strategy will work (as long as you run npm run build before publishing). I couldn't test with your branch because it didn't contain the dist directory and the "files": ["dist"] property in package.json prevented npm from installing the src directory.
This was my first time seeing tsup to solve this problem, but it seems like a reasonable wrapper around esbuild and rollup. I was a little bit surprised to see it generate chunk-DZDTB73T.js, but I don't think there is anything wrong with it.

Its not a branch but a version tag, like i wrote you should be able to npm i my previous comment

@tronikelis The<EMAIL_ADDRESS>version works great!

nice, I simplified the package.json a bit, can you try npm i<EMAIL_ADDRESS>as well?
If it's good then I'll merge it as 5.0.2

I reviewed #65 and believe it will work well. I also installed<EMAIL_ADDRESS>verify it actually works well in the node repl and in vitest.


Respect method access-levels

class public Test

    method private doTest()
    methodend
classend

t! = new Test()
t!.d...

Originally posted by @StephanWald in https://github.com/BBx-Kitchen/bbj-language-server/issues/74#issuecomment-2340177699

The documentation says:

Only methods with an appropriate access level for the given context will be available - public methods will always be available, private methods are only available when writing code within their class, and protected methods are available within their class and any subclasses.

@dhuebner @StephanWald An idea: We could link the methods without respecting the access-level but add a validation when the access-level is not correct.
The other way would be to exclude symbols from the current scope depending on the context. Then, accessing a private method from an outer class would result in a linking error instead of a validation that the access-level forbids this.
I think the last one is easier to implement, whereas the first gives better messages in my eyes.

@Lotes

We could link the methods without respecting the access-level but add a validation when the access-level is not correct.

I prefer this option as it provides a better user experience. The validation could be like this:
The method <some_methode> from the type <some_type> is not visible

@StephanWald I solved the access-levels for methods and fields (instance or static variations) in #200 . We also made an observation, that nested classes are not possible within BBj.
But Java can contain nested classes and I think there might be some gaps in the language server. Can you check how relevant nested classes are for you and create new issues for found gaps? I am thinking of nested classes like Map.Entry.
🙏


[VCQ][DevDiv_VSO][VSCode][Webview views are proposed api]

MS PM
Daniel Ye

MOR PM
Jan Baltus (Moravia IT)

String Resource ID
0; "src/vs/workbench/api/browser/viewsExtensionPoint.webviewViewsRequireProposed"

Source String
Webview views are proposed api and are only supported when running out of dev or with the following command line switch: --enable-proposed-api

Subtenant
VSCode

Source Control Link

Filename
vscode-workbench\vs_workbench.xlf

Question
Does running out of dev mean, not having enough developer? Or does it mean something else?

Additional details

Core Team Response

This string was removed when we finalized the API. Let me know if you see it come up again for some reason


fix: incorrect package.json main/module

This project look so cool!
When I build with vite, it occurs the error
[commonjs--resolver] Failed to resolve entry for package "@newfrgmnt/harmony". The package may have incorrect main/module/exports specified in its package.json.
error during build:
Error: Failed to resolve entry for package "@newfrgmnt/harmony". The package may have incorrect main/module/exports specified in its package.json.

The package.json is
{
  "name": "@newfrgmnt/harmony",
  "version": "1.0.2",
  "main": "./build/index.js",
  "module": "./build/index.mjs",
  "types": "./build/index.d.ts",
}

but build dir are
@newfrgmnt/harmony/build
├── index.cjs
├── index.d.cts
├── index.d.ts
└── index.js

1 directory, 4 files

Thus I modify the package.json main/module to correct file.

Thanks! ✨


A suggestion: supported platform versions

Hey,
I found this 👇🏼

I would I like to add it to all SwiftKitz repos. It's fine ?
Can you please provide me with all the supported platform versions ? or could you please guide me to an easy way to find the supported platform versions ?
Thanks.

Thanks, but I think it's not worth adding and maintaining for now.
Sent from my iPhone

On Sep 26, 2017, at 5:25 PM, Mariam AlJamea<EMAIL_ADDRESS>wrote:
Hey,
I found this 👇🏼
I would I like to add it to all SwiftKitz repos. It's fine ?
Can you please provide me with all the supported platform versions ? or could you please guide me to an easy way to find the supported platform versions ?
Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

As you like.
Sent from my iPhone

On Sep 26, 2017, at 7:26 PM, Maz Jaleel<EMAIL_ADDRESS>wrote:
Thanks, but I think it's not worth adding and maintaining for now.
Sent from my iPhone

On Sep 26, 2017, at 5:25 PM, Mariam AlJamea<EMAIL_ADDRESS>wrote:
Hey,
I found this 👇🏼
I would I like to add it to all SwiftKitz repos. It's fine ?
Can you please provide me with all the supported platform versions ? or could you please guide me to an easy way to find the supported platform versions ?
Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Please when it's the time please tell me to do it, I will be glad to help.
Thanks.

I found a way to find the supported platform versions, For example: Appz, supported platform versions are as follow:

iOS 8.0+
tvOS 9.0+
watchOS 2.0+

TYT, when it's the time give me the agreement to do them to all SwiftKitz repos.


Poseidon2 Hash

Just to note , on comparing generated asm code against horizen implementation I see https://discourse.llvm.org/t/rfc-cmov-vs-branch-optimization/6040 kind of optimization opportunity in plonky2 generated posiden2 code.


[stable/sonatype-nexus] Add openshift routes

Problem:
No resource to create openshift routes.
Solution
Add routes for both services.
What this PR does?
Adds new routes for both docker and nexus(proxy) service.

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/assign @rjkernick

@rjkernick any updates on this?

/ok-to-test

@rjkernick any updates on this?

/lgtm


Live preview does not work with domains and docker builds

Describe the Bug
More context, see Discord; https://discord.com/channels/967097582721572934/1301603163329265718
The main issue that I have, is that while having NEXT_PUBLIC_SERVER_URL=http://localhost:3001, the live preview functionality works fine. However, when changing it to NEXT_PUBLIC_SERVER_URL=http://test.<IP_ADDRESS>.sslip.io:3001, it does not work anymore.
*.<IP_ADDRESS>.sslip.io is a wildcard DNS for - in this case - 127.0.01.
Most of the code are 1-1 of the website template, when it comes to live preview.
Branch: https://github.com/Thijmen/thijmen.dev/tree/payload-livepreview-issue
Link to the code that reproduces this issue
https://github.com/Thijmen/thijmen.dev/tree/payload-livepreview-issue
Reproduction Steps

Clone my repository and check out branch payload-livepreview-issue.
Copy .env.example to .env
Toggle the NEXT_PUBLIC_SERVER_URL to the second one (so value should be http://localhost:3001.
Run docker compose up -d to start the Postgres database container.
Build the image with the provided ./build.sh script. You may need to run chmod +x build.sh
5.1. Seeing how I structured my initial seeding, you need to run this twice. The first build should fail on some email field.
Once build, start the container with executing ./start.sh. You may need to run chmod +x start.sh first.
Go to the backend to http://localhost:3001/admin with<EMAIL_ADDRESS>as email, password as password (as per .env).
7.1. Edit the first project (http://localhost:3001/admin/collections/projects/1) and press "Live Preview".
7.2. Make changes in the "Detail" tab (content editor) and see that it will be reflected in the preview.
Now, stop the start.sh script and make changes to .env. Ensure that NEXT_PUBLIC_SERVER_URL=http://test.<IP_ADDRESS>.sslip.io:3001 is now uncommented.
Build the docker image again with ./build.sh.
Run the container with ./start.sh
Run the same steps as step 7, but then with http://test.<IP_ADDRESS>.sslip.io:3001/admin (and the same credentials)
Notice that the live preview wont update.

Which area(s) are affected? (Select all that apply)
area: core, area: templates
Environment Info
Binaries:
Node: 20.12.2
npm: 10.5.0
Yarn: 1.22.22
pnpm: 9.12.2
Relevant Packages:
payload: 3.0.0-beta.118
next: 15.0.1
@payloadcms/db-postgres: 3.0.0-beta.118
@payloadcms/email-nodemailer: 3.0.0-beta.118
@payloadcms/graphql: 3.0.0-beta.118
@payloadcms/live-preview: 3.0.0-beta.118
@payloadcms/live-preview-react: 3.0.0-beta.118
@payloadcms/next/utilities: 3.0.0-beta.118
@payloadcms/plugin-cloud: 3.0.0-beta.118
@payloadcms/plugin-cloud-storage: 3.0.0-beta.118
@payloadcms/plugin-form-builder: 3.0.0-beta.118
@payloadcms/plugin-nested-docs: 3.0.0-beta.118
@payloadcms/plugin-redirects: 3.0.0-beta.118
@payloadcms/plugin-seo: 3.0.0-beta.118
@payloadcms/richtext-lexical: 3.0.0-beta.118
@payloadcms/translations: 3.0.0-beta.118
@payloadcms/ui/shared: 3.0.0-beta.118
react: 19.0.0-rc-65a56d0e-20241020
react-dom: 19.0.0-rc-65a56d0e-20241020
Operating System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 24.0.0: Tue Sep 24 23:37:25 PDT 2024; root:xnu-11215.1.12~1/RELEASE_ARM64_T6030
Available memory (MB): 36864
Available CPU cores: 12

Closed; it appears that once you leave "localhost" as domain, you need to provide a valid SSL connection as NextJS sends some secure cookies when entering live-preview/draft modus.


added missing parameter: gtdTime + test

Coverage increased (+0.002%) to 99.249% when pulling 6d4caa7dbcaf6276217f4ce1f7428e4f8a2888e5 on gtd-fix into aec5560c95a67546334d1e37fd0a8fdcf840aea5 on master.

Coverage increased (+0.002%) to 99.249% when pulling 769f693598994ddd083bc8fa1fa9926130c87a2a on gtd-fix into aec5560c95a67546334d1e37fd0a8fdcf840aea5 on master.

closes #93


Suggestion for another type of economy

Hello
I thought this plugin had ceased to exist, thanks for updating it!
Could you add compatibility with the V-MultiEconomies plugin please?
plugin: https://www.spigotmc.org/resources/v-multieconomies-multiple-customizable-economies-1-8-1-19.105322/
have a nice day
:)

It would be up to them to integrate properly with Vault. Once they integrate with Vault, you'd have your integration.


Change how we handle bulk sync notifications vs. real-time notifications

An example would be waking PC up from sleep and receiving a TON of notifications. We should make it so if the bulk update finds > x new messages, we just dispatch a single notification for it (and we update the chat list once). Rather than sending x new message notifications and updating the chat x times, which is expensive and can cause lag

Issue created by BlueBubbles Bot in the BlueBubbles commnity on behalf of @zach in #feedback.

Fixed


Backend/unittest fix

Fix unitest for database.py, models.py, and schemas.py.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.


Support IgnoreType in parse

Add IgnoreType to the Feature
https://github.com/alibaba/fastjson/issues/1047

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.姜禹 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Improvement: create documentation index page

Create an index page in the documentation folder of the repository, to mimic the behavior of http://www.stylecop.com/docs/. The filename of the index page must be such that it shows up on top of the list in GitHub.

Would be very helpful. :+1:


Use TrimSpace to instead of Trim

String.Trim(string, " ") can only get ride of the blank, but actully we need
to remove all leading and trailing white space include "\t" for example.
Prior to this patch, one can login with "[Tab][Tab]username", and it will
not be considered as the same with "username".
Signed-off-by: Hu Keping<EMAIL_ADDRESS>

LGTM if janky is happy

LGTM


Added HDF31 Messaging management blueprint containing kafka

Added blueprint for HDF31 Messaging management. It included kafka, zookeeper and ambari metrics. No additional changes were needed on cloudbreak side as blueprint just worked out of the box.

Thank you for the PR.


final cran release items

This version made it to CRAN so going to merge and deal with failing tests if those are real later.


Updated MidiMonitor project to use binary framework

D'oh!

So there's a bunch of new stuff in this PR now, mostly related to new methods to select inputs.

Lots of good stuff here, thanks!


Passing cucumber tags in test runner class returning features as null instead of filtered tests based on tags

QAF Version
2.1.13

Note: only the latest version is supported

Steps To Reproduce
1. I have a TestNG runner class which is having features, glue, tags and plugin key-value pairs under cucumber options
2. I have testng.xml file wherein I have mentioned this TestNG runner class and executed it
3. During execution I observed that features are showing as null i.e. when you pass tag names in TestNg runner class, features shows as null.
4. Now I commented the tag names in TestNg runner class and again executed my testng.xml file. This time it executed everything and could see the features showing as scenario names.

Expected behavior
When we pass tag names in TestNG runner class, it should execute only those features having that tag name i.e. features should not be null
Actual behavior
Features are showing as null when you pass tag names in TestNG runner class.
Is the issue reproducible on runner?
Yes

[ ] QAS
[x] Maven
[ ] Gradle
[ ] Ant
[ ] Eclipse

P.S. I tried to execute the TestNG runner class without passing tags which executes all the features i.e. passing tags in TestNG Runner class not working correctly.

If my understanding is correct, you are using cucumber runner. In that case it is out of scope for qaf as nothing related to qaf. I would suggest to use qaf ghekin factory instead.

Hi,
My requirement is mentioned as below:
I want to generate JSON output of the test report which would be imported into test management tool in JIRA (test Management integration).
How can I achieve this using Gherkinfactory?
So, I have created the runner class.
Here is my code snippet.
Code Snippet from TestNG.XML file:

Code Snippet from runner class (runTest.java):
**package com.quantum.steps;
import cucumber.api.CucumberOptions;
import cucumber.api.testng.AbstractTestNGCucumberTests;
@CucumberOptions(
features = {"src/main/resources/scenarios"},
glue = {"com.quantum.steps"},
tags = {"@mastercard"},
plugin = {"json:target/cucumber.json"}
)
public class runTest extends AbstractTestNGCucumberTests {
}**
I am calling the runner class in testng.xml file addition to Gherkinfactory because of which it ignores the feature and tags that are passed. If I don’t use Gherkinfactory how can I generate the json output that is generated via plugin in cucumberoptions?
Thanks.
Regards,
Nikhil Agrawal

you should use either qaf gherkin factory or cucumber runner. when you will use cucumber runner as it is not of qaf we can't fix issues with it. On other hand when you are using gherkin factory it will generate qaf json and testNG xml report but not cucumber report.
In that case you can use qaf gherkin and

Check with test management tool support team, if they have support for TestNG xml or qaf json report. For example QTM4J is similar test management tool that supports TestNG, QAF, Junit, Cucumber and other report formats. OR
Alternately you can ask them to provide a TestNG report listener to generate report int the format that Test Management tool expect or you can write one own your own.

Keep in mind that what you are using is not TestNG report listener. The reporting listener should work only with TestNG (or qaf) without any of the cucumber dependencies.

closing inactive issue. Please post your questions in users group if required further help.


Resolve issue #86

Write unit tests for org.trebol.jpa.services.conversion

please label "hacktoberfest-accepted" if its good :)

thanks so much for your effort! I'm putting together a changelist right now and will add more comments as I progress

Hi @bglamadrid ,
Do you have discord?Maybe we can connect and improve the rest of the code

Sure, hit me up with an e-mail and I'll give you my discord id 👌


Docker build fails due to binutils version

The image build failed with the following error:

ERROR: unsatisfiable constraints:
binutils-2.33.1-r0:
breaks: world[binutils=2.32-r0]

I could build it only after changing to binutils=2.33.1-r0 (instead of 2.32-r0) in the Dockerfile

Thanks, could you provide a PR?

Done
https://github.com/EugenMayer/docker-image-unison/pull/9

Thank you! I guess we do not need a new release yet, since it will only fail on rebuild, which is fixed on master now.
Are you fine with that

Sure. That's fine :)