Get basis frequencies in interpolating frequency sweeps

Description of the feature
Methods for exporting field solutions, such as PostProcessor.export_field_file, require an intrinsics parameter that specifies the frequency at which the fields are calculated. To export the field solution at each frequency in a discrete frequency sweep, one can get a list of frequencies from SolutionData.instrinsics and run a for loop.
This does not work for an interpolating frequency sweep because SolutionData.instrinsics has all frequencies in the definition of the sweep, whereas field solutions are available only at the basis frequencies. There needs to be a way to get only the interpolation basis frequencies, for example, through a new attribute in SolutionData.
Steps for implementing the feature
No response
Useful links and references
No response

@pgurrala19 I've implemented in #1474
now Sweep has  properties: frequencies and basis_frequencies.
Example
hfss.setups[0].sweeps[0].basis_frequencies
hfss.setups[0].sweeps[0].frequencies

This methods works ONLY if solutions are present and project is saved as it is reading solution folder


New package: SDLCanvas v1.12.6

Registering package: SDLCanvas
Repository: https://github.com/Noremac11800/SDLCanvas.jl
Created by: @Noremac11800
Version: v1.12.6
Commit: 7671d70516314c5d27bca6c48ebdb6e6380b058e
Reviewed by: @Noremac11800
Reference: https://github.com/Noremac11800/SDLCanvas.jl/issues/2#issuecomment-1837331262

No merge


bug: Ambiguous reference ServiceLifetime

Hi,
looks like your version of the enum ServiceLifeTime collides with the one from MS

.NET = 8.0
LibVersion = 1.0.3

I also cannot increase the specification because the “ServiceLifeTime” is in the same namespace just from a different assembly.
Polyfills/Microsoft.Extensions.DependencyInjection.ServiceLifetime.cs

Hello @andreas-soroko,
I hope this message finds you well.
I wanted to inform you that I have fixed the issue regarding the collision with the .NET 8.0 ServiceLifetime enum. The problem was due to the ServiceLifetime visibility being set to public when it should have been internal. Additionally, I took the opportunity to update other classes and members to internal where public visibility was not necessary.
To apply these fixes, please update the package to the latest version.
Thank you, and please let me know if you encounter any further issues.
Best regards,
Jimmy Millo


🐞[BUG] Amount of parts different in dashboard, table and logs

Description

Occured on INT-A during R24.08 testing https://catena-x.atlassian.net/browse/CXTM-337:
The amount of parts is different in Dashboard, Part tables and logs.
Current behaviour
In the dashboard the amount of parts shown for Other Parts (Customer / Supplier) is 17:

When going to the parts table and filtering for Other Parts I get an amount of 13:

When triggering the IRS synchronization, the logs show different amounts as well:
2024-07-25T09:56:54.105Z  INFO 1 --- [ptorsExecutor-2] e.t.t.s.d.s.DecentralRegistryServiceImpl : Try to sync 15 assets asBuilt
2024-07-25T09:56:54.106Z  INFO 1 --- [ptorsExecutor-2] e.t.t.s.d.s.DecentralRegistryServiceImpl : Try to sync 8 assets asPlanned
Expected behavior

I expect the amount of parts to be identical. Or if there are errors, to be sufficiently informed.
Steps to reproduce the Bug

Reset environments
Import testdata
Trigger registry reload
Check dashboard, parts table and logs

Dashboard problem was fixed.
Log amount difference is due to an error in the test data which is irrelevant for the R24.08 release.

Upload of test data now shows the correct amount for own parts:
int a:

int b:

PR to resolve this issue:
https://github.com/eclipse-tractusx/traceability-foss/pull/1322


Add cable ID field to connections

Currently the power, console, and interfaces connections are defined the following way:
device_a,interface_a,device_b,interface_b,connection_status
It would be useful (at least to us) to be able to define a cable ID as we label all our connections/cables (including power and console).
It could also be in the form of a generic "notes/label" field, or allowing custom fields for connections.

@jeremystretch I looked for duplicates before opening that task, but couldn't find any. Could you point me to the one I should follow instead?
Thanks

Probably because it is related to #20

Searching the issues for "cable ID" shows duplicate issues #2271, #1291, and #589, all of which reference #20.


Create a link to docker.sock in the default location

Allow for the creation of a link to the docker.sock file in the default location.
A number of tools and partners are assuming this location and don't want
to have to configure it for the value defaulted in CFCR by the
docker-boshrelease
This would fix the issue opened by @mmanciop in https://github.com/cloudfoundry-incubator/kubo-release/issues/329.

FYI @cholick

Several companies building integrations (APM and security vendors) have run across the non-standard docker socket location as a source of friction. Some have configuration options to override it, but others don't. Even when there is a configuration option, it means that using this release requires special documentation. This would be a very useful change.

Pinging this for an update on when it may be merged or if there are reasons it will not be merged.  Thanks!

We just ran into this again when attempting to use LitmusChaos and would love to see this merged.


Find a interesting bug in code about include

VS Code Version:
OS Version:

Steps to Reproduce:
1.Now I use the newest VScode in Linux (debian deb version),when I include my .hpp file and this .hpp file include a qt headfile(QLineSeries),I find that "#include<my.hpp>" is wrong with rad line showing that
cant find QLineSeries.But in my.cpp,everything is OK.And,in the end I can run this program successfully.
2.So what happened , why,and how can I solve it?

Does this issue occur when all extensions are disabled?: Yes/No
Yes

my os is Ubuntu 20.10 and code version is 1.54.1 amd64

This sound like an issue with the CPP extension. Please report the issue with them.


. delete me plz

A fixed size buffer cannot be passed as an array to a method. It's unsafe and for me it's useless..

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

ID: f5e17dd8-f60c-5a5d-517f-61bb95e94667
Version Independent ID: c9d34513-107b-0b82-cf77-1dba0ee650cb
Content: Fixed Size Buffers - C# Programming Guide
Content Source: docs/csharp/programming-guide/unsafe-code-pointers/fixed-size-buffers.md
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

I'll close this issue, @jvanlangen. Thanks for letting us know.


Tooltips don't show up in code editor.

Godot version:

3.2.2
OS/device including version:

Windows 10 64bit
Issue description:

I don't see tooltips with variable types etc. in code editor.
Steps to reproduce:
Hover over anything in a script in code editor.
Minimal reproduction project:

Test.zip

This is not a bug. There are no tooltips in the script editor yet :slightly_smiling_face:


STOMP Headers Name Comparator

Motivation:
The HashingStrategy for DefaultStompHeaders was using the java .equals() method which would fail to compare String, AsciiString, and other CharSequence objects as equal.
Modifications:

Use AsciiString.CASE_SENSITIVE_HASHER for DefaultStompHeaders

Result:
DefaultStompHeaders work with all CharSequence objects.
Fixes netty#4247

@silvaran - Please verify.
@normanmaurer - FYI

Looks good.  Upcoming beta7 fixes my String/AsciiString header issue.

@Scottmitch just one tiny nit.. after that ship it

Cherry-picked 4.1 (7adc1f9) master (1c14e5b)
@silvaran - Thanks for reporting/verifying!


Gitter room

Have you thought about creating a Gitter room for ngmap for users to chat about issues?

I can create a gitter room, but I can't promise I will be available for chat.
Anyway, created one. https://gitter.im/allenhwkim/ngmap


2.2.2 click active crash

Hello, I couldn't see this in the list.
Android 9 oxygen os
August security patch
Oneplus 6t
Esteem 2.2.2
Popular page crash when selecting active
to recreate
When opening the app go to popular let trending load
In drop down select active.
It does not load
Select another type such as trending. This now also fails to load.
Select a different section such as hot, then go to active. Same behaviour crash and then all other popular pages fail to load.
Feed still loads correctly and so does profile.
Resolved by restarting app
Let me know if there is anything you want me to try.

This depends on what server you are connecting. Try selecting rpc.esteem.app server from Settings page. api.steemit.com server doesn't support those filters.

Thats done it. I didn't change the default server from when I installed the app. Should RPC be the default?


Added user posts page and applying new firebase design

cleanup : clearing some debugging strings
add : modal dialog for yes and no modal
update : logging out now uses confirmation dialog
refactor : renaming all modal related components
refactor : renaming input related components
fix : choose topic page redirections now are correct
refactor : simplifying user registration api modules
attempt : optimizing status placeholder application
clean up : cleaning console
clean up : minor console clean up
add : date-fns package
add : user/posts page and getting article by ids
add : modal routed hook
added : user/posts page also added article deletion
update : made the modal confirmation enter/space-able
update : minor ui fix
update : big update on firebase, applying new system design on how article is stored to the firebase
update : implemented the thing new firebase article design
update : applying article deletion with the new firebase design
fix : writing panel preview not showing the thumbnail
update : article page now works with the implementation of new firebase config
fix : article page now shows the proper article with newly firebase config applied
fix : fix redirection after creating article, also add to link to /user/posts
update : added search functionality  on user/posts

TODO : next

add intersection observer to load article content
add more detailed properties to post item mini

I don't think intersection observer on article page would be a great implementation. Because of comments and suggestion is already a lazy loaded component. If the users scroll down they might as well accidentally load the comments and suggestions.
Though i guess i can make the comments and suggestion only available if the content is already loaded.


RuntimeError: Found no NVIDIA driver on your system. Please check that you have an NVIDIA GPU and installed a driver from http://www.nvidia.com/Download/index.aspx

..
Drop files to upload them to session storage
Disk
77.33 GB available
[1]
22s
#koneksi kegoogle drive-
from google.colab import drive
drive.mount('/content/drive/')
Mounted at /content/drive/
[2]
0s
%cd /content/drive/MyDrive/cangkehdetection
/content/drive/MyDrive/cangkehdetection
[ ]
Download data
!git clone https://github.com/sovit-123/fasterrcnn-pytorch-training-pipeline.git
[3]
0s
%cd fasterrcnn-pytorch-training-pipeline
/content/drive/MyDrive/cangkehdetection/fasterrcnn-pytorch-training-pipeline
[5]
1m
Install the Requirements library for image detection-
!pip install -r requirements.txt
Looking in indexes: https://pypi.org/simple, https://us-python.pkg.dev/colab-wheels/public/simple/
Requirement already satisfied: albumentations>=1.1.0 in /usr/local/lib/python3.9/dist-packages (from -r requirements.txt (line 2)) (1.2.1)
Requirement already satisfied: ipython in /usr/local/lib/python3.9/dist-packages (from -r requirements.txt (line 3)) (7.34.0)
Collecting jupyter
Downloading jupyter-1.0.0-py2.py3-none-any.whl (2.7 kB)
Requirement already satisfied: matplotlib in /usr/local/lib/python3.9/dist-packages (from -r requirements.txt (line 5)) (3.7.1)
Requirement already satisfied: opencv-python>=<IP_ADDRESS> in /usr/local/lib/python3.9/dist-packages (from -r requirements.txt (line 6)) (<IP_ADDRESS>)
Requirement already satisfied: opencv-python-headless>=<IP_ADDRESS> in /usr/local/lib/python3.9/dist-packages (from -r requirements.txt (line 7)) (<IP_ADDRESS>)
Requirement already satisfied: Pillow in /usr/local/lib/python3.9/dist-packages (from -r requirements.txt (line 8)) (8.4.0)
Requirement already satisfied: PyYAML in /usr/local/lib/python3.9/dist-packages (from -r requirements.txt (line 9)) (6.0)
Requirement already satisfied: scikit-image in /usr/local/lib/python3.9/dist-packages (from -r requirements.txt (line 10)) (0.19.3)
Requirement already satisfied: scikit-learn in /usr/local/lib/python3.9/dist-packages (from -r requirements.txt (line 11)) (1.2.2)
Requirement already satisfied: scipy in /usr/local/lib/python3.9/dist-packages (from -r requirements.txt (line 12)) (1.10.1)
Collecting torch==1.12.0
Downloading torch-1.12.0-cp39-cp39-manylinux1_x86_64.whl (776.3 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 776.3/776.3 MB 2.1 MB/s eta 0:00:00
Collecting torchvision==0.13.0
Downloading torchvision-0.13.0-cp39-cp39-manylinux1_x86_64.whl (19.1 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 19.1/19.1 MB 65.6 MB/s eta 0:00:00
Requirement already satisfied: numpy in /usr/local/lib/python3.9/dist-packages (from -r requirements.txt (line 15)) (1.22.4)
Collecting protobuf<=3.20.1
Downloading protobuf-3.20.1-cp39-cp39-manylinux_2_5_x86_64.manylinux1_x86_64.whl (1.0 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.0/1.0 MB 60.5 MB/s eta 0:00:00
Requirement already satisfied: pandas in /usr/local/lib/python3.9/dist-packages (from -r requirements.txt (line 17)) (1.4.4)
Requirement already satisfied: tqdm in /usr/local/lib/python3.9/dist-packages (from -r requirements.txt (line 18)) (4.65.0)
Collecting wandb
Downloading wandb-0.14.2-py3-none-any.whl (2.0 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.0/2.0 MB 82.0 MB/s eta 0:00:00
Requirement already satisfied: tensorboard in /usr/local/lib/python3.9/dist-packages (from -r requirements.txt (line 22)) (2.12.1)
Collecting torchinfo
Downloading torchinfo-1.7.2-py3-none-any.whl (22 kB)
Requirement already satisfied: pycocotools>=2.0.2 in /usr/local/lib/python3.9/dist-packages (from -r requirements.txt (line 28)) (2.0.6)
Collecting setuptools==59.5.0
Downloading setuptools-59.5.0-py3-none-any.whl (952 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 952.4/952.4 KB 63.3 MB/s eta 0:00:00
Collecting torchmetrics
Downloading torchmetrics-0.11.4-py3-none-any.whl (519 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 519.2/519.2 KB 38.4 MB/s eta 0:00:00
Requirement already satisfied: typing-extensions in /usr/local/lib/python3.9/dist-packages (from torch==1.12.0->-r requirements.txt (line 13)) (4.5.0)
Requirement already satisfied: requests in /usr/local/lib/python3.9/dist-packages (from torchvision==0.13.0->-r requirements.txt (line 14)) (2.27.1)
Requirement already satisfied: qudida>=0.0.4 in /usr/local/lib/python3.9/dist-packages (from albumentations>=1.1.0->-r requirements.txt (line 2)) (0.0.4)
Collecting jedi>=0.16
Downloading jedi-0.18.2-py2.py3-none-any.whl (1.6 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.6/1.6 MB 78.0 MB/s eta 0:00:00
Requirement already satisfied: pexpect>4.3 in /usr/local/lib/python3.9/dist-packages (from ipython->-r requirements.txt (line 3)) (4.8.0)
Requirement already satisfied: backcall in /usr/local/lib/python3.9/dist-packages (from ipython->-r requirements.txt (line 3)) (0.2.0)
Requirement already satisfied: pygments in /usr/local/lib/python3.9/dist-packages (from ipython->-r requirements.txt (line 3)) (2.14.0)
Requirement already satisfied: traitlets>=4.2 in /usr/local/lib/python3.9/dist-packages (from ipython->-r requirements.txt (line 3)) (5.7.1)
Requirement already satisfied: pickleshare in /usr/local/lib/python3.9/dist-packages (from ipython->-r requirements.txt (line 3)) (0.7.5)
Requirement already satisfied: prompt-toolkit!=3.0.0,!=3.0.1,<3.1.0,>=2.0.0 in /usr/local/lib/python3.9/dist-packages (from ipython->-r requirements.txt (line 3)) (3.0.38)
Requirement already satisfied: decorator in /usr/local/lib/python3.9/dist-packages (from ipython->-r requirements.txt (line 3)) (4.4.2)
Requirement already satisfied: matplotlib-inline in /usr/local/lib/python3.9/dist-packages (from ipython->-r requirements.txt (line 3)) (0.1.6)
Collecting qtconsole
Downloading qtconsole-5.4.2-py3-none-any.whl (121 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 121.2/121.2 KB 14.8 MB/s eta 0:00:00
Requirement already satisfied: jupyter-console in /usr/local/lib/python3.9/dist-packages (from jupyter->-r requirements.txt (line 4)) (6.1.0)
Requirement already satisfied: ipykernel in /usr/local/lib/python3.9/dist-packages (from jupyter->-r requirements.txt (line 4)) (5.5.6)
Requirement already satisfied: ipywidgets in /usr/local/lib/python3.9/dist-packages (from jupyter->-r requirements.txt (line 4)) (7.7.1)
Requirement already satisfied: nbconvert in /usr/local/lib/python3.9/dist-packages (from jupyter->-r requirements.txt (line 4)) (6.5.4)
Requirement already satisfied: notebook in /usr/local/lib/python3.9/dist-packages (from jupyter->-r requirements.txt (line 4)) (6.4.8)
Requirement already satisfied: python-dateutil>=2.7 in /usr/local/lib/python3.9/dist-packages (from matplotlib->-r requirements.txt (line 5)) (2.8.2)
Requirement already satisfied: packaging>=20.0 in /usr/local/lib/python3.9/dist-packages (from matplotlib->-r requirements.txt (line 5)) (23.0)
Requirement already satisfied: cycler>=0.10 in /usr/local/lib/python3.9/dist-packages (from matplotlib->-r requirements.txt (line 5)) (0.11.0)
Requirement already satisfied: pyparsing>=2.3.1 in /usr/local/lib/python3.9/dist-packages (from matplotlib->-r requirements.txt (line 5)) (3.0.9)
Requirement already satisfied: importlib-resources>=3.2.0 in /usr/local/lib/python3.9/dist-packages (from matplotlib->-r requirements.txt (line 5)) (5.12.0)
Requirement already satisfied: fonttools>=4.22.0 in /usr/local/lib/python3.9/dist-packages (from matplotlib->-r requirements.txt (line 5)) (4.39.3)
Requirement already satisfied: contourpy>=1.0.1 in /usr/local/lib/python3.9/dist-packages (from matplotlib->-r requirements.txt (line 5)) (1.0.7)
Requirement already satisfied: kiwisolver>=1.0.1 in /usr/local/lib/python3.9/dist-packages (from matplotlib->-r requirements.txt (line 5)) (1.4.4)
Requirement already satisfied: PyWavelets>=1.1.1 in /usr/local/lib/python3.9/dist-packages (from scikit-image->-r requirements.txt (line 10)) (1.4.1)
Requirement already satisfied: networkx>=2.2 in /usr/local/lib/python3.9/dist-packages (from scikit-image->-r requirements.txt (line 10)) (3.0)
Requirement already satisfied: tifffile>=2019.7.26 in /usr/local/lib/python3.9/dist-packages (from scikit-image->-r requirements.txt (line 10)) (2023.3.21)
Requirement already satisfied: imageio>=2.4.1 in /usr/local/lib/python3.9/dist-packages (from scikit-image->-r requirements.txt (line 10)) (2.25.1)
Requirement already satisfied: joblib>=1.1.1 in /usr/local/lib/python3.9/dist-packages (from scikit-learn->-r requirements.txt (line 11)) (1.1.1)
Requirement already satisfied: threadpoolctl>=2.0.0 in /usr/local/lib/python3.9/dist-packages (from scikit-learn->-r requirements.txt (line 11)) (3.1.0)
Requirement already satisfied: pytz>=2020.1 in /usr/local/lib/python3.9/dist-packages (from pandas->-r requirements.txt (line 17)) (2022.7.1)
Requirement already satisfied: psutil>=5.0.0 in /usr/local/lib/python3.9/dist-packages (from wandb->-r requirements.txt (line 21)) (5.9.4)
Collecting setproctitle
Downloading setproctitle-1.3.2-cp39-cp39-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (30 kB)
Requirement already satisfied: Click!=8.0.0,>=7.0 in /usr/local/lib/python3.9/dist-packages (from wandb->-r requirements.txt (line 21)) (8.1.3)
Collecting GitPython!=3.1.29,>=1.0.0
Downloading GitPython-3.1.31-py3-none-any.whl (184 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 184.3/184.3 KB 21.9 MB/s eta 0:00:00
Collecting docker-pycreds>=0.4.0
Downloading docker_pycreds-0.4.0-py2.py3-none-any.whl (9.0 kB)
Requirement already satisfied: appdirs>=1.4.3 in /usr/local/lib/python3.9/dist-packages (from wandb->-r requirements.txt (line 21)) (1.4.4)
Collecting pathtools
Downloading pathtools-0.1.2.tar.gz (11 kB)
Preparing metadata (setup.py) ... done
Collecting sentry-sdk>=1.0.0
Downloading sentry_sdk-1.19.1-py2.py3-none-any.whl (199 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 199.2/199.2 KB 21.0 MB/s eta 0:00:00
Requirement already satisfied: google-auth<3,>=1.6.3 in /usr/local/lib/python3.9/dist-packages (from tensorboard->-r requirements.txt (line 22)) (2.17.1)
Requirement already satisfied: tensorboard-plugin-wit>=1.6.0 in /usr/local/lib/python3.9/dist-packages (from tensorboard->-r requirements.txt (line 22)) (1.8.1)
Requirement already satisfied: tensorboard-data-server<0.8.0,>=0.7.0 in /usr/local/lib/python3.9/dist-packages (from tensorboard->-r requirements.txt (line 22)) (0.7.0)
Requirement already satisfied: werkzeug>=1.0.1 in /usr/local/lib/python3.9/dist-packages (from tensorboard->-r requirements.txt (line 22)) (2.2.3)
Requirement already satisfied: wheel>=0.26 in /usr/local/lib/python3.9/dist-packages (from tensorboard->-r requirements.txt (line 22)) (0.40.0)
Requirement already satisfied: google-auth-oauthlib<1.1,>=0.5 in /usr/local/lib/python3.9/dist-packages (from tensorboard->-r requirements.txt (line 22)) (1.0.0)
Requirement already satisfied: absl-py>=0.4 in /usr/local/lib/python3.9/dist-packages (from tensorboard->-r requirements.txt (line 22)) (1.4.0)
Requirement already satisfied: grpcio>=1.48.2 in /usr/local/lib/python3.9/dist-packages (from tensorboard->-r requirements.txt (line 22)) (1.53.0)
Requirement already satisfied: markdown>=2.6.8 in /usr/local/lib/python3.9/dist-packages (from tensorboard->-r requirements.txt (line 22)) (3.4.3)
Requirement already satisfied: six>=1.4.0 in /usr/local/lib/python3.9/dist-packages (from docker-pycreds>=0.4.0->wandb->-r requirements.txt (line 21)) (1.16.0)
Collecting gitdb<5,>=4.0.1
Downloading gitdb-4.0.10-py3-none-any.whl (62 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 62.7/62.7 KB 7.8 MB/s eta 0:00:00
Requirement already satisfied: rsa<5,>=3.1.4 in /usr/local/lib/python3.9/dist-packages (from google-auth<3,>=1.6.3->tensorboard->-r requirements.txt (line 22)) (4.9)
Requirement already satisfied: cachetools<6.0,>=2.0.0 in /usr/local/lib/python3.9/dist-packages (from google-auth<3,>=1.6.3->tensorboard->-r requirements.txt (line 22)) (5.3.0)
Requirement already satisfied: pyasn1-modules>=0.2.1 in /usr/local/lib/python3.9/dist-packages (from google-auth<3,>=1.6.3->tensorboard->-r requirements.txt (line 22)) (0.2.8)
Requirement already satisfied: requests-oauthlib>=0.7.0 in /usr/local/lib/python3.9/dist-packages (from google-auth-oauthlib<1.1,>=0.5->tensorboard->-r requirements.txt (line 22)) (1.3.1)
Requirement already satisfied: zipp>=3.1.0 in /usr/local/lib/python3.9/dist-packages (from importlib-resources>=3.2.0->matplotlib->-r requirements.txt (line 5)) (3.15.0)
Requirement already satisfied: parso<0.9.0,>=0.8.0 in /usr/local/lib/python3.9/dist-packages (from jedi>=0.16->ipython->-r requirements.txt (line 3)) (0.8.3)
Requirement already satisfied: importlib-metadata>=4.4 in /usr/local/lib/python3.9/dist-packages (from markdown>=2.6.8->tensorboard->-r requirements.txt (line 22)) (6.1.0)
Requirement already satisfied: ptyprocess>=0.5 in /usr/local/lib/python3.9/dist-packages (from pexpect>4.3->ipython->-r requirements.txt (line 3)) (0.7.0)
Requirement already satisfied: wcwidth in /usr/local/lib/python3.9/dist-packages (from prompt-toolkit!=3.0.0,!=3.0.1,<3.1.0,>=2.0.0->ipython->-r requirements.txt (line 3)) (0.2.6)
Requirement already satisfied: idna<4,>=2.5 in /usr/local/lib/python3.9/dist-packages (from requests->torchvision==0.13.0->-r requirements.txt (line 14)) (3.4)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.9/dist-packages (from requests->torchvision==0.13.0->-r requirements.txt (line 14)) (2022.12.7)
Requirement already satisfied: charset-normalizer~=2.0.0 in /usr/local/lib/python3.9/dist-packages (from requests->torchvision==0.13.0->-r requirements.txt (line 14)) (2.0.12)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in /usr/local/lib/python3.9/dist-packages (from requests->torchvision==0.13.0->-r requirements.txt (line 14)) (1.26.15)
Requirement already satisfied: MarkupSafe>=2.1.1 in /usr/local/lib/python3.9/dist-packages (from werkzeug>=1.0.1->tensorboard->-r requirements.txt (line 22)) (2.1.2)
Requirement already satisfied: tornado>=4.2 in /usr/local/lib/python3.9/dist-packages (from ipykernel->jupyter->-r requirements.txt (line 4)) (6.2)
Requirement already satisfied: ipython-genutils in /usr/local/lib/python3.9/dist-packages (from ipykernel->jupyter->-r requirements.txt (line 4)) (0.2.0)
Requirement already satisfied: jupyter-client in /usr/local/lib/python3.9/dist-packages (from ipykernel->jupyter->-r requirements.txt (line 4)) (6.1.12)
Requirement already satisfied: widgetsnbextension~=3.6.0 in /usr/local/lib/python3.9/dist-packages (from ipywidgets->jupyter->-r requirements.txt (line 4)) (3.6.4)
Requirement already satisfied: jupyterlab-widgets>=1.0.0 in /usr/local/lib/python3.9/dist-packages (from ipywidgets->jupyter->-r requirements.txt (line 4)) (3.0.7)
Requirement already satisfied: jupyter-core>=4.7 in /usr/local/lib/python3.9/dist-packages (from nbconvert->jupyter->-r requirements.txt (line 4)) (5.3.0)
Requirement already satisfied: mistune<2,>=0.8.1 in /usr/local/lib/python3.9/dist-packages (from nbconvert->jupyter->-r requirements.txt (line 4)) (0.8.4)
Requirement already satisfied: jinja2>=3.0 in /usr/local/lib/python3.9/dist-packages (from nbconvert->jupyter->-r requirements.txt (line 4)) (3.1.2)
Requirement already satisfied: bleach in /usr/local/lib/python3.9/dist-packages (from nbconvert->jupyter->-r requirements.txt (line 4)) (6.0.0)
Requirement already satisfied: lxml in /usr/local/lib/python3.9/dist-packages (from nbconvert->jupyter->-r requirements.txt (line 4)) (4.9.2)
Requirement already satisfied: beautifulsoup4 in /usr/local/lib/python3.9/dist-packages (from nbconvert->jupyter->-r requirements.txt (line 4)) (4.11.2)
Requirement already satisfied: defusedxml in /usr/local/lib/python3.9/dist-packages (from nbconvert->jupyter->-r requirements.txt (line 4)) (0.7.1)
Requirement already satisfied: nbformat>=5.1 in /usr/local/lib/python3.9/dist-packages (from nbconvert->jupyter->-r requirements.txt (line 4)) (5.8.0)
Requirement already satisfied: tinycss2 in /usr/local/lib/python3.9/dist-packages (from nbconvert->jupyter->-r requirements.txt (line 4)) (1.2.1)
Requirement already satisfied: pandocfilters>=1.4.1 in /usr/local/lib/python3.9/dist-packages (from nbconvert->jupyter->-r requirements.txt (line 4)) (1.5.0)
Requirement already satisfied: jupyterlab-pygments in /usr/local/lib/python3.9/dist-packages (from nbconvert->jupyter->-r requirements.txt (line 4)) (0.2.2)
Requirement already satisfied: entrypoints>=0.2.2 in /usr/local/lib/python3.9/dist-packages (from nbconvert->jupyter->-r requirements.txt (line 4)) (0.4)
Requirement already satisfied: nbclient>=0.5.0 in /usr/local/lib/python3.9/dist-packages (from nbconvert->jupyter->-r requirements.txt (line 4)) (0.7.3)
Requirement already satisfied: pyzmq>=17 in /usr/local/lib/python3.9/dist-packages (from notebook->jupyter->-r requirements.txt (line 4)) (23.2.1)
Requirement already satisfied: terminado>=0.8.3 in /usr/local/lib/python3.9/dist-packages (from notebook->jupyter->-r requirements.txt (line 4)) (0.17.1)
Requirement already satisfied: nest-asyncio>=1.5 in /usr/local/lib/python3.9/dist-packages (from notebook->jupyter->-r requirements.txt (line 4)) (1.5.6)
Requirement already satisfied: Send2Trash>=1.8.0 in /usr/local/lib/python3.9/dist-packages (from notebook->jupyter->-r requirements.txt (line 4)) (1.8.0)
Requirement already satisfied: argon2-cffi in /usr/local/lib/python3.9/dist-packages (from notebook->jupyter->-r requirements.txt (line 4)) (21.3.0)
Requirement already satisfied: prometheus-client in /usr/local/lib/python3.9/dist-packages (from notebook->jupyter->-r requirements.txt (line 4)) (0.16.0)
Collecting qtpy>=2.0.1
Downloading QtPy-2.3.1-py3-none-any.whl (84 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 84.9/84.9 KB 10.8 MB/s eta 0:00:00
Collecting smmap<6,>=3.0.1
Downloading smmap-5.0.0-py3-none-any.whl (24 kB)
Requirement already satisfied: platformdirs>=2.5 in /usr/local/lib/python3.9/dist-packages (from jupyter-core>=4.7->nbconvert->jupyter->-r requirements.txt (line 4)) (3.2.0)
Requirement already satisfied: jsonschema>=2.6 in /usr/local/lib/python3.9/dist-packages (from nbformat>=5.1->nbconvert->jupyter->-r requirements.txt (line 4)) (4.3.3)
Requirement already satisfied: fastjsonschema in /usr/local/lib/python3.9/dist-packages (from nbformat>=5.1->nbconvert->jupyter->-r requirements.txt (line 4)) (2.16.3)
Requirement already satisfied: pyasn1<0.5.0,>=0.4.6 in /usr/local/lib/python3.9/dist-packages (from pyasn1-modules>=0.2.1->google-auth<3,>=1.6.3->tensorboard->-r requirements.txt (line 22)) (0.4.8)
Requirement already satisfied: oauthlib>=3.0.0 in /usr/local/lib/python3.9/dist-packages (from requests-oauthlib>=0.7.0->google-auth-oauthlib<1.1,>=0.5->tensorboard->-r requirements.txt (line 22)) (3.2.2)
Requirement already satisfied: argon2-cffi-bindings in /usr/local/lib/python3.9/dist-packages (from argon2-cffi->notebook->jupyter->-r requirements.txt (line 4)) (21.2.0)
Requirement already satisfied: soupsieve>1.2 in /usr/local/lib/python3.9/dist-packages (from beautifulsoup4->nbconvert->jupyter->-r requirements.txt (line 4)) (2.4)
Requirement already satisfied: webencodings in /usr/local/lib/python3.9/dist-packages (from bleach->nbconvert->jupyter->-r requirements.txt (line 4)) (0.5.1)
Requirement already satisfied: attrs>=17.4.0 in /usr/local/lib/python3.9/dist-packages (from jsonschema>=2.6->nbformat>=5.1->nbconvert->jupyter->-r requirements.txt (line 4)) (22.2.0)
Requirement already satisfied: pyrsistent!=0.17.0,!=0.17.1,!=0.17.2,>=0.14.0 in /usr/local/lib/python3.9/dist-packages (from jsonschema>=2.6->nbformat>=5.1->nbconvert->jupyter->-r requirements.txt (line 4)) (0.19.3)
Requirement already satisfied: cffi>=1.0.1 in /usr/local/lib/python3.9/dist-packages (from argon2-cffi-bindings->argon2-cffi->notebook->jupyter->-r requirements.txt (line 4)) (1.15.1)
Requirement already satisfied: pycparser in /usr/local/lib/python3.9/dist-packages (from cffi>=1.0.1->argon2-cffi-bindings->argon2-cffi->notebook->jupyter->-r requirements.txt (line 4)) (2.21)
Building wheels for collected packages: pathtools
Building wheel for pathtools (setup.py) ... done
Created wheel for pathtools: filename=pathtools-0.1.2-py3-none-any.whl size=8807 sha256=ce341c5849e5e6a3c8e4b833e3b11c039a73e68dc3da1279e37853635e92362b
Stored in directory: /root/.cache/pip/wheels/b7/0a/67/ada2a22079218c75a88361c0782855cc72aebc4d18d0289d05
Successfully built pathtools
Installing collected packages: pathtools, torchinfo, torch, smmap, setuptools, setproctitle, sentry-sdk, qtpy, protobuf, jedi, docker-pycreds, torchvision, torchmetrics, gitdb, GitPython, wandb, qtconsole, jupyter
Attempting uninstall: torch
Found existing installation: torch 2.0.0+cu118
Uninstalling torch-2.0.0+cu118:
Successfully uninstalled torch-2.0.0+cu118
Attempting uninstall: setuptools
Found existing installation: setuptools 67.6.1
Uninstalling setuptools-67.6.1:
Successfully uninstalled setuptools-67.6.1
Attempting uninstall: protobuf
Found existing installation: protobuf 3.20.3
Uninstalling protobuf-3.20.3:
Successfully uninstalled protobuf-3.20.3
Attempting uninstall: torchvision
Found existing installation: torchvision 0.15.1+cu118
Uninstalling torchvision-0.15.1+cu118:
Successfully uninstalled torchvision-0.15.1+cu118
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
torchtext 0.15.1 requires torch==2.0.0, but you have torch 1.12.0 which is incompatible.
torchdata 0.6.0 requires torch==2.0.0, but you have torch 1.12.0 which is incompatible.
torchaudio 2.0.1+cu118 requires torch==2.0.0, but you have torch 1.12.0 which is incompatible.
tensorflow 2.12.0 requires protobuf!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.20.3, but you have protobuf 3.20.1 which is incompatible.
googleapis-common-protos 1.59.0 requires protobuf!=3.20.0,!=3.20.1,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.19.5, but you have protobuf 3.20.1 which is incompatible.
google-cloud-translate 3.8.4 requires protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.19.5, but you have protobuf 3.20.1 which is incompatible.
google-cloud-language 2.6.1 requires protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.19.5, but you have protobuf 3.20.1 which is incompatible.
google-cloud-firestore 2.7.3 requires protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.19.5, but you have protobuf 3.20.1 which is incompatible.
google-cloud-datastore 2.11.1 requires protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.19.5, but you have protobuf 3.20.1 which is incompatible.
google-cloud-bigquery 3.4.2 requires protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.19.5, but you have protobuf 3.20.1 which is incompatible.
google-cloud-bigquery-storage 2.19.1 requires protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.19.5, but you have protobuf 3.20.1 which is incompatible.
google-api-core 2.11.0 requires protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.19.5, but you have protobuf 3.20.1 which is incompatible.
cvxpy 1.3.1 requires setuptools>65.5.1, but you have setuptools 59.5.0 which is incompatible.
arviz 0.15.1 requires setuptools>=60.0.0, but you have setuptools 59.5.0 which is incompatible.
Successfully installed GitPython-3.1.31 docker-pycreds-0.4.0 gitdb-4.0.10 jedi-0.18.2 jupyter-1.0.0 pathtools-0.1.2 protobuf-3.20.1 qtconsole-5.4.2 qtpy-2.3.1 sentry-sdk-1.19.1 setproctitle-1.3.2 setuptools-59.5.0 smmap-5.0.0 torch-1.12.0 torchinfo-1.7.2 torchmetrics-0.11.4 torchvision-0.13.0 wandb-0.14.2
[6]
1m
!pip install torch==2.0.0
Looking in indexes: https://pypi.org/simple, https://us-python.pkg.dev/colab-wheels/public/simple/
Collecting torch==2.0.0
Downloading torch-2.0.0-cp39-cp39-manylinux1_x86_64.whl (619.9 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 619.9/619.9 MB 2.4 MB/s eta 0:00:00
Collecting nvidia-cuda-nvrtc-cu11==11.7.99
Downloading nvidia_cuda_nvrtc_cu11-11.7.99-2-py3-none-manylinux1_x86_64.whl (21.0 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 21.0/21.0 MB 63.4 MB/s eta 0:00:00
Collecting nvidia-cuda-runtime-cu11==11.7.99
Downloading nvidia_cuda_runtime_cu11-11.7.99-py3-none-manylinux1_x86_64.whl (849 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 849.3/849.3 KB 56.1 MB/s eta 0:00:00
Requirement already satisfied: filelock in /usr/local/lib/python3.9/dist-packages (from torch==2.0.0) (3.10.7)
Requirement already satisfied: jinja2 in /usr/local/lib/python3.9/dist-packages (from torch==2.0.0) (3.1.2)
Collecting nvidia-cusparse-cu11==<IP_ADDRESS>
Downloading nvidia_cusparse_cu11-<IP_ADDRESS>-py3-none-manylinux1_x86_64.whl (173.2 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 173.2/173.2 MB 7.3 MB/s eta 0:00:00
Requirement already satisfied: typing-extensions in /usr/local/lib/python3.9/dist-packages (from torch==2.0.0) (4.5.0)
Collecting nvidia-nvtx-cu11==11.7.91
Downloading nvidia_nvtx_cu11-11.7.91-py3-none-manylinux1_x86_64.whl (98 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 98.6/98.6 KB 13.6 MB/s eta 0:00:00
Collecting nvidia-cufft-cu11==<IP_ADDRESS>
Downloading nvidia_cufft_cu11-<IP_ADDRESS>-py3-none-manylinux1_x86_64.whl (168.4 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 168.4/168.4 MB 7.4 MB/s eta 0:00:00
Collecting nvidia-cuda-cupti-cu11==11.7.101
Downloading nvidia_cuda_cupti_cu11-11.7.101-py3-none-manylinux1_x86_64.whl (11.8 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 11.8/11.8 MB 84.9 MB/s eta 0:00:00
Requirement already satisfied: sympy in /usr/local/lib/python3.9/dist-packages (from torch==2.0.0) (1.11.1)
Collecting nvidia-curand-cu11==<IP_ADDRESS>
Downloading nvidia_curand_cu11-<IP_ADDRESS>-py3-none-manylinux1_x86_64.whl (54.6 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 54.6/54.6 MB 12.4 MB/s eta 0:00:00
Requirement already satisfied: networkx in /usr/local/lib/python3.9/dist-packages (from torch==2.0.0) (3.0)
Requirement already satisfied: triton==2.0.0 in /usr/local/lib/python3.9/dist-packages (from torch==2.0.0) (2.0.0)
Collecting nvidia-cublas-cu11==<IP_ADDRESS>
Downloading nvidia_cublas_cu11-<IP_ADDRESS>-py3-none-manylinux1_x86_64.whl (317.1 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 317.1/317.1 MB 4.0 MB/s eta 0:00:00
Collecting nvidia-cudnn-cu11==<IP_ADDRESS>
Downloading nvidia_cudnn_cu11-<IP_ADDRESS>-2-py3-none-manylinux1_x86_64.whl (557.1 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 557.1/557.1 MB 2.7 MB/s eta 0:00:00
Collecting nvidia-nccl-cu11==2.14.3
Downloading nvidia_nccl_cu11-2.14.3-py3-none-manylinux1_x86_64.whl (177.1 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 177.1/177.1 MB 6.2 MB/s eta 0:00:00
Collecting nvidia-cusolver-cu11==<IP_ADDRESS>
Downloading nvidia_cusolver_cu11-<IP_ADDRESS>-2-py3-none-manylinux1_x86_64.whl (102.6 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 102.6/102.6 MB 9.9 MB/s eta 0:00:00
Requirement already satisfied: setuptools in /usr/local/lib/python3.9/dist-packages (from nvidia-cublas-cu11==<IP_ADDRESS>->torch==2.0.0) (59.5.0)
Requirement already satisfied: wheel in /usr/local/lib/python3.9/dist-packages (from nvidia-cublas-cu11==<IP_ADDRESS>->torch==2.0.0) (0.40.0)
Requirement already satisfied: cmake in /usr/local/lib/python3.9/dist-packages (from triton==2.0.0->torch==2.0.0) (3.25.2)
Requirement already satisfied: lit in /usr/local/lib/python3.9/dist-packages (from triton==2.0.0->torch==2.0.0) (16.0.0)
Requirement already satisfied: MarkupSafe>=2.0 in /usr/local/lib/python3.9/dist-packages (from jinja2->torch==2.0.0) (2.1.2)
Requirement already satisfied: mpmath>=0.19 in /usr/local/lib/python3.9/dist-packages (from sympy->torch==2.0.0) (1.3.0)
Installing collected packages: nvidia-nvtx-cu11, nvidia-nccl-cu11, nvidia-cusparse-cu11, nvidia-curand-cu11, nvidia-cufft-cu11, nvidia-cuda-runtime-cu11, nvidia-cuda-nvrtc-cu11, nvidia-cuda-cupti-cu11, nvidia-cublas-cu11, nvidia-cusolver-cu11, nvidia-cudnn-cu11, torch
Attempting uninstall: torch
Found existing installation: torch 1.12.0
Uninstalling torch-1.12.0:
Successfully uninstalled torch-1.12.0
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
torchvision 0.13.0 requires torch==1.12.0, but you have torch 2.0.0 which is incompatible.
Successfully installed nvidia-cublas-cu11-<IP_ADDRESS> nvidia-cuda-cupti-cu11-11.7.101 nvidia-cuda-nvrtc-cu11-11.7.99 nvidia-cuda-runtime-cu11-11.7.99 nvidia-cudnn-cu11-<IP_ADDRESS> nvidia-cufft-cu11-<IP_ADDRESS> nvidia-curand-cu11-<IP_ADDRESS> nvidia-cusolver-cu11-<IP_ADDRESS> nvidia-cusparse-cu11-<IP_ADDRESS> nvidia-nccl-cu11-2.14.3 nvidia-nvtx-cu11-11.7.91 torch-2.0.0
[7]
17s
!pip install git+https://github.com/gautamchitnis/cocoapi.git@cocodataset-master#subdirectory=PythonAPI
Looking in indexes: https://pypi.org/simple, https://us-python.pkg.dev/colab-wheels/public/simple/
Collecting git+https://github.com/gautamchitnis/cocoapi.git@cocodataset-master#subdirectory=PythonAPI
Cloning https://github.com/gautamchitnis/cocoapi.git (to revision cocodataset-master) to /tmp/pip-req-build-ojbw02d9
Running command git clone --filter=blob:none --quiet https://github.com/gautamchitnis/cocoapi.git /tmp/pip-req-build-ojbw02d9
Running command git checkout -b cocodataset-master --track origin/cocodataset-master
Switched to a new branch 'cocodataset-master'
Branch 'cocodataset-master' set up to track remote branch 'cocodataset-master' from 'origin'.
Resolved https://github.com/gautamchitnis/cocoapi.git to commit 20291f19c46a8d11935862bc9e449a1b72ec25ed
Preparing metadata (setup.py) ... done
Building wheels for collected packages: pycocotools
Building wheel for pycocotools (setup.py) ... done
Created wheel for pycocotools: filename=pycocotools-2.0-cp39-cp39-linux_x86_64.whl size=398095 sha256=94723d5ce3fca91072d2832e8579000019a077fbabd5edf0c6c4db10f27932f7
Stored in directory: /tmp/pip-ephem-wheel-cache-n06x8qwe/wheels/a6/5f/ec/1eaf8c69abab5724baee819736e6d30adad774deb60736413b
Successfully built pycocotools
Installing collected packages: pycocotools
Attempting uninstall: pycocotools
Found existing installation: pycocotools 2.0.6
Uninstalling pycocotools-2.0.6:
Successfully uninstalled pycocotools-2.0.6
Successfully installed pycocotools-2.0
[11]
0s
#membuat file YAML (konfigurasi datatrain)-
%%writefile data_configs/clove_2023.yaml
Direktori gambar dan label harus relatif terhadap train.py ()
TRAIN_DIR_IMAGES: 'custom_data/train'
TRAIN_DIR_LABELS: 'custom_data/train'
VALID_DIR_IMAGES: 'custom_data/valid'
VALID_DIR_LABELS: 'custom_data/valid'
Masukkan nama classs
CLASSES: [
'background',
'clove', 'rubbish'
]
Jumlah class yang dijadikan object (object classes + 1 for background class in Faster RCNN).
NC: 3
Pertanyaan apakan akan menyimpan prediksi set validasi saat pelatihan jika ya ketik "True" dan jika tidak ketik "False"
SAVE_VALID_PREDICTION_IMAGES: True
Writing data_configs/clove_2023.yaml
[13]
50s
install library
!pip install vision_transformers
Looking in indexes: https://pypi.org/simple, https://us-python.pkg.dev/colab-wheels/public/simple/
Collecting vision_transformers
Downloading vision_transformers-<IP_ADDRESS>.tar.gz (38 kB)
Preparing metadata (setup.py) ... done
Requirement already satisfied: torch>=1.10 in /usr/local/lib/python3.9/dist-packages (from vision_transformers) (2.0.0)
Requirement already satisfied: torchvision in /usr/local/lib/python3.9/dist-packages (from vision_transformers) (0.13.0)
Requirement already satisfied: nvidia-cuda-runtime-cu11==11.7.99 in /usr/local/lib/python3.9/dist-packages (from torch>=1.10->vision_transformers) (11.7.99)
Requirement already satisfied: nvidia-cusparse-cu11==<IP_ADDRESS> in /usr/local/lib/python3.9/dist-packages (from torch>=1.10->vision_transformers) (<IP_ADDRESS>)
Requirement already satisfied: typing-extensions in /usr/local/lib/python3.9/dist-packages (from torch>=1.10->vision_transformers) (4.5.0)
Requirement already satisfied: nvidia-nccl-cu11==2.14.3 in /usr/local/lib/python3.9/dist-packages (from torch>=1.10->vision_transformers) (2.14.3)
Requirement already satisfied: nvidia-cublas-cu11==<IP_ADDRESS> in /usr/local/lib/python3.9/dist-packages (from torch>=1.10->vision_transformers) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-nvtx-cu11==11.7.91 in /usr/local/lib/python3.9/dist-packages (from torch>=1.10->vision_transformers) (11.7.91)
Requirement already satisfied: nvidia-curand-cu11==<IP_ADDRESS> in /usr/local/lib/python3.9/dist-packages (from torch>=1.10->vision_transformers) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cufft-cu11==<IP_ADDRESS> in /usr/local/lib/python3.9/dist-packages (from torch>=1.10->vision_transformers) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cuda-cupti-cu11==11.7.101 in /usr/local/lib/python3.9/dist-packages (from torch>=1.10->vision_transformers) (11.7.101)
Requirement already satisfied: jinja2 in /usr/local/lib/python3.9/dist-packages (from torch>=1.10->vision_transformers) (3.1.2)
Requirement already satisfied: nvidia-cudnn-cu11==<IP_ADDRESS> in /usr/local/lib/python3.9/dist-packages (from torch>=1.10->vision_transformers) (<IP_ADDRESS>)
Requirement already satisfied: triton==2.0.0 in /usr/local/lib/python3.9/dist-packages (from torch>=1.10->vision_transformers) (2.0.0)
Requirement already satisfied: filelock in /usr/local/lib/python3.9/dist-packages (from torch>=1.10->vision_transformers) (3.10.7)
Requirement already satisfied: nvidia-cusolver-cu11==<IP_ADDRESS> in /usr/local/lib/python3.9/dist-packages (from torch>=1.10->vision_transformers) (<IP_ADDRESS>)
Requirement already satisfied: networkx in /usr/local/lib/python3.9/dist-packages (from torch>=1.10->vision_transformers) (3.0)
Requirement already satisfied: sympy in /usr/local/lib/python3.9/dist-packages (from torch>=1.10->vision_transformers) (1.11.1)
Requirement already satisfied: nvidia-cuda-nvrtc-cu11==11.7.99 in /usr/local/lib/python3.9/dist-packages (from torch>=1.10->vision_transformers) (11.7.99)
Requirement already satisfied: setuptools in /usr/local/lib/python3.9/dist-packages (from nvidia-cublas-cu11==<IP_ADDRESS>->torch>=1.10->vision_transformers) (59.5.0)
Requirement already satisfied: wheel in /usr/local/lib/python3.9/dist-packages (from nvidia-cublas-cu11==<IP_ADDRESS>->torch>=1.10->vision_transformers) (0.40.0)
Requirement already satisfied: lit in /usr/local/lib/python3.9/dist-packages (from triton==2.0.0->torch>=1.10->vision_transformers) (16.0.0)
Requirement already satisfied: cmake in /usr/local/lib/python3.9/dist-packages (from triton==2.0.0->torch>=1.10->vision_transformers) (3.25.2)
Requirement already satisfied: requests in /usr/local/lib/python3.9/dist-packages (from torchvision->vision_transformers) (2.27.1)
Requirement already satisfied: pillow!=8.3.*,>=5.3.0 in /usr/local/lib/python3.9/dist-packages (from torchvision->vision_transformers) (8.4.0)
Collecting torch>=1.10
Using cached torch-1.12.0-cp39-cp39-manylinux1_x86_64.whl (776.3 MB)
Requirement already satisfied: numpy in /usr/local/lib/python3.9/dist-packages (from torchvision->vision_transformers) (1.22.4)
Requirement already satisfied: MarkupSafe>=2.0 in /usr/local/lib/python3.9/dist-packages (from jinja2->torch>=1.10->vision_transformers) (2.1.2)
Requirement already satisfied: charset-normalizer~=2.0.0 in /usr/local/lib/python3.9/dist-packages (from requests->torchvision->vision_transformers) (2.0.12)
Requirement already satisfied: idna<4,>=2.5 in /usr/local/lib/python3.9/dist-packages (from requests->torchvision->vision_transformers) (3.4)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in /usr/local/lib/python3.9/dist-packages (from requests->torchvision->vision_transformers) (1.26.15)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.9/dist-packages (from requests->torchvision->vision_transformers) (2022.12.7)
Requirement already satisfied: mpmath>=0.19 in /usr/local/lib/python3.9/dist-packages (from sympy->torch>=1.10->vision_transformers) (1.3.0)
Building wheels for collected packages: vision_transformers
Building wheel for vision_transformers (setup.py) ... done
Created wheel for vision_transformers: filename=vision_transformers-<IP_ADDRESS>-py3-none-any.whl size=48431 sha256=64be1b21506d11b9bba0bf2d026e79cfff9fc4133238bf701a865cc4e191d9bb
Stored in directory: /root/.cache/pip/wheels/1d/86/13/31f5fe3a4f2bc3dd24af79c12d5f732256e5047cb70d7485ef
Successfully built vision_transformers
Installing collected packages: torch, vision_transformers
Attempting uninstall: torch
Found existing installation: torch 2.0.0
Uninstalling torch-2.0.0:
Successfully uninstalled torch-2.0.0
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
torchtext 0.15.1 requires torch==2.0.0, but you have torch 1.12.0 which is incompatible.
torchdata 0.6.0 requires torch==2.0.0, but you have torch 1.12.0 which is incompatible.
torchaudio 2.0.1+cu118 requires torch==2.0.0, but you have torch 1.12.0 which is incompatible.
Successfully installed torch-1.12.0 vision_transformers-<IP_ADDRESS>
[15]
1m
Old
!python train.py --model fasterrcnn_mobilenetv3_large_fpn --data data_configs/clove_2023.yaml --epochs 40 --no-mosaic --name training_old --seed 42
Not using distributed mode
wandb: Currently logged in as: auliadarnilasarii97 (mandev). Use wandb login --relogin to force relogin
wandb: Tracking run with wandb version 0.14.2
wandb: Run data is saved locally in /content/drive/MyDrive/cangkehdetection/fasterrcnn-pytorch-training-pipeline/wandb/run-20230409_064846-ws99a2ql
wandb: Run wandb offline to turn off syncing.
wandb: Syncing run training_old
wandb: ⭐ View project at https://wandb.ai/mandev/fasterrcnn-pytorch-training-pipeline
wandb: 🚀 View run at https://wandb.ai/mandev/fasterrcnn-pytorch-training-pipeline/runs/ws99a2ql
device cuda
2023-04-09 06:48:47.993981: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2023-04-09 06:48:49.286339: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
Creating data loaders
/usr/local/lib/python3.9/dist-packages/torch/utils/data/dataloader.py:557: UserWarning: This DataLoader will create 4 worker processes in total. Our suggested max number of worker in current system is 2, which is smaller than what this DataLoader is going to create. Please be aware that excessive worker creation might get DataLoader running slow or even freeze, lower the worker number to avoid potential slowness/freeze if necessary.
warnings.warn(_create_warning_msg(
Number of training samples: 1470
Number of validation samples: 179
Building model from scratch...
/usr/local/lib/python3.9/dist-packages/torchvision/models/_utils.py:208: UserWarning: The parameter 'pretrained' is deprecated since 0.13 and will be removed in 0.15, please use 'weights' instead.
warnings.warn(
/usr/local/lib/python3.9/dist-packages/torchvision/models/_utils.py:223: UserWarning: Arguments other than a weight enum or None for 'weights' are deprecated since 0.13 and will be removed in 0.15. The current behavior is equivalent to passing weights=FasterRCNN_MobileNet_V3_Large_FPN_Weights.COCO_V1. You can also use weights=FasterRCNN_MobileNet_V3_Large_FPN_Weights.DEFAULT to get the most up-to-date weights.
warnings.warn(msg)
Downloading: "https://download.pytorch.org/models/fasterrcnn_mobilenet_v3_large_fpn-fb6a3cc7.pth" to /root/.cache/torch/hub/checkpoints/fasterrcnn_mobilenet_v3_large_fpn-fb6a3cc7.pth
100% 74.2M/74.2M [00:00<00:00, 88.0MB/s]
Traceback (most recent call last):
File "/content/drive/MyDrive/cangkehdetection/fasterrcnn-pytorch-training-pipeline/train.py", line 539, in
main(args)
File "/content/drive/MyDrive/cangkehdetection/fasterrcnn-pytorch-training-pipeline/train.py", line 331, in main
model = model.to(DEVICE)
File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/module.py", line 927, in to
return self._apply(convert)
File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/module.py", line 579, in _apply
module._apply(fn)
File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/module.py", line 579, in _apply
module._apply(fn)
File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/module.py", line 579, in _apply
module._apply(fn)
[Previous line repeated 1 more time]
File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/module.py", line 602, in _apply
param_applied = fn(param)
File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/module.py", line 925, in convert
return t.to(device, dtype if t.is_floating_point() or t.is_complex() else None, non_blocking)
File "/usr/local/lib/python3.9/dist-packages/torch/cuda/init.py", line 217, in _lazy_init
torch._C._cuda_init()
RuntimeError: Found no NVIDIA driver on your system. Please check that you have an NVIDIA GPU and installed a driver from http://www.nvidia.com/Download/index.aspx
wandb: Waiting for W&B process to finish... (failed 1). Press Control-C to abort syncing.
wandb: 🚀 View run training_old at: https://wandb.ai/mandev/fasterrcnn-pytorch-training-pipeline/runs/ws99a2ql
wandb: Synced 5 W&B file(s), 0 media file(s), 0 artifact file(s) and 0 other file(s)
wandb: Find logs at: ./wandb/run-20230409_064846-ws99a2ql/logs

Hello @darnilasariaulia
I am a bit confused. So, can you tell me finally which torch version you are using?


discrepancy between the expected(doc) and actual results with Pong+DQN

[x] I have marked all applicable categories:

[ ] exception-raising bug
[x] RL algorithm bug
[ ] system worker bug
[ ] system utils bug
[ ] code design/refactor
[ ] documentation request
[ ] new feature request

[x] I have visited the readme and doc
[x] I have searched through the issue tracker and pr tracker
[x] I have mentioned version numbers, operating system and environment, where applicable:import ding, torch, sys
print(ding.__version__, torch.__version__, sys.version, sys.platform)

v0.4.6 1.12.0 3.7.13 (default, Mar 29 2022, 02:18:16)  [GCC 7.5.0] linux
I used the code and configuration files provided in the repository to run the example "atari/pong+dqn" as described in the example. However, the results I obtained were different from the expected results and took significantly longer to run.
here is the config file, I only change the exp name
pong_dqn_config = dict(
    exp_name='exp/pong/dqn_seed0',
    env=dict(
        collector_env_num=8,
        evaluator_env_num=8,
        n_evaluator_episode=8,
        stop_value=20,
        env_id='Pong-v4',
        #'ALE/Pong-v5' is available. But special setting is needed after gym make.
        frame_stack=4,
    ),
    policy=dict(
        cuda=True,
        priority=False,
        model=dict(
            obs_shape=[4, 84, 84],
            action_shape=6,
            encoder_hidden_size_list=[128, 128, 512],
        ),
        nstep=3,
        discount_factor=0.99,
        learn=dict(
            update_per_collect=10,
            batch_size=32,
            learning_rate=0.0001,
            target_update_freq=500,
        ),
        collect=dict(n_sample=96, ),
        eval=dict(evaluator=dict(eval_freq=4000, )),
        other=dict(
            eps=dict(
                type='exp',
                start=1.,
                end=0.05,
                decay=250000,
            ),
            replay_buffer=dict(replay_buffer_size=100000, ),
        ),
    ),
)
pong_dqn_config = EasyDict(pong_dqn_config)
main_config = pong_dqn_config
pong_dqn_create_config = dict(
    env=dict(
        type='atari',
        import_names=['dizoo.atari.envs.atari_env'],
    ),
    env_manager=dict(type='subprocess'),
    policy=dict(type='dqn'),
)
pong_dqn_create_config = EasyDict(pong_dqn_create_config)
create_config = pong_dqn_create_config

and my result

Compared with the result showed in the doc, it is really confusing

Could you please provide any guidance on how to troubleshoot the problem or suggest any known issues related to this example? Thank you.

We will conduct the reproducible experiment about this config in two days.

As is shown above, I run the same config with 3 different seeds, the final results are similar to yours. I check the commit history and don't find the obvious config modifcation. In the next few days, I will check related code implementations and adjust some hyper-parameters. You can keep track of this issue.

As is shown above, I run the same config with 3 different seeds, the final results are similar to yours. I check the commit history and don't find the obvious config modifcation. In the next few days, I will check related code implementations and adjust some hyper-parameters. You can keep track of this issue.

Thanks for the effort!
It is great see your result. Actually your worst result with blue curse is also far better than mine as shown below. The orange curve is trained with the best ckpt from blue curve which was canceled due to accident. It still takes 14M steps. And for default PPO config(I also just change the exp name), it seems to be too slow, so I give up training longer.

I have checked the old log in server and find the curve shown in doc is the DQN+priority version. Then I validate this argument in 2 seeds and get the obvious improvement, which is shown in figure below.

You can try to set priority=True in this config and rerun the experiment.

@zhixiongzh You should only set priority=True and keep priority_IS_weight=False. Because if we enable priority_IS_weight, we also need to adjust learning rate together.

I find a problem about the performance gap. In the old version, DI-engine uses PongNoframeskip-v4 as env_id, but when we updated the version of gym==0.25.1, we modified this env_id to Pong-v4. This difference of these two env_ids is described in gym's doc:

Pong-v4 will bring some extra randomness to the env, so our original config will show some performance gap. I suggest you should modify the env_id and rerun the experiment. And I will also rerun it to check the result.


Wayland WM detection

pfetch-rs uses libmacchina for window manager detection, which currently relies on wmctrl being installed and the user running X11. I added detection with xprop in https://github.com/Macchina-CLI/libmacchina/commit/8f94e1f68ec860155e4087b634e97426f1f2a593 ~, but there was no new release since then.~ This ~also~ does not fix detection on Wayland

Related PR: https://github.com/Macchina-CLI/libmacchina/pull/164

Is there any reason for this issue to still be open? From what I can tell this works, or at least with well known ones like Sway and Hyprland (I only tested on these two).

Added in https://github.com/Macchina-CLI/libmacchina/pull/164/ and 55991bceeec0eba5b95bc7272f41f6a1ac8a6bdc

I run hyprland so I can test for you when this is added

I run hyprland so I can test for you when this is added

It should already work since version 2.8.1, I just forgot to close this issue. You can try it out like this:
PF_INFO="ascii title os host uptime pkgs memory shell editor wm de palette" pfetch

wm and de both work

I run hyprland so I can test for you when this is added

Oh I had already tested this with practically every wayland WM and DE I had installed (Hyprland, Sway, Plasma 6, GNOME, Wayfire, COSMIC Epoch, Cinnamon (Wayland Experimental) and a couple others) before editing my comment.


Update README.md

Ground rules:

Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
Pull Requests sent without claiming and referencing the Issue will not be entertained.
Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Issues:
Create a link to the CONTRIBUTING.md file and the License file in the README file.
Change Code Status to working.

what things you want to be added/deleted from the README.md

@Rishabh04-02 update the links to the other issues that'll be added. For example add the link of a License which will be added.

@Rishabh04-02 click on this link .

#6


Is FreeOTP dead/abandoned?

Looking at the android store listing and the issues here, the app hasn't been updated in like 4 years and lots of people claim development has been abandoned. However, the renaissance project appears to be active and it looks like someone made a new commit only a couple of months ago.
TL;DR: What is the current status of development on this app?

Yes, clearly abandoned.
From what I can see, this is an actively maintained alternative: https://github.com/andOTP/andOTP

On the iOS side there has been some progress. The Android project is in need of someone to take over active development.
I am currently looking after the Android PRs, but don't have time to take on the big feature work in the Renaissance project.

Use the Microsoft Authenticator it has cloud backup

Use the Microsoft Authenticator it has cloud backup

Got the source to it?

There has been commits in May 2020 so it is still active. Last accepted PR was in July 2020.
Maybe there is no big improvement needed for now and this might be the reason of no big update, but it was definitely still active after your question.


[error] with e -dl parameters

i tested e module with -dl parameters :
when the dl  have four domain ,it's work well ,when the numbers more than 400 accared error : 19503 killed

It may be that the computer memory is insufficient, I will try to optimize this problem later

The new version has been updated to fix this problem


Getting Error when installing using requirements.txt

Hey Tom

, I am trying to get the results of your trained models in my local machine. When I am trying to install dependencies using "python -m pip install -r requirements.txt", I am getting the following error. Can u help me out here? Thanks :)

Hi, please update your local repo with git pull and try again :)

I am new to git. So, can u write the command please? Or is it better to download the source code of torchseq and manually install it?

Sorry - I mean, update the separator repo. Running git pull in that working directory should do the trick. I've updated the requirements.txt file, it should work now.

Okay. Now I am getting some errors with the torch and the versions mentioned in your torchseq repo are different from these, right?

Yes, that's strange - the requirements.txt should be pointing at torch==1.8.0 (although it should work fine with 1.7 or 1.9 too).
Could you try installing torchseq manually? Clone the torchseq repo, then run this from the torchseq directory, with your separator env activated:
pip install -r requirements.txt
pip install -e .

Hey I just saw that only torch version having some error. So installed it manually from torch stable versions. Used the following command
pip install torch==1.7.0+cpu -f https://download.pytorch.org/whl/torch_stable.html
then re-run requirements.txt again. I hope we can close this issue. But I am getting some errors with the model now, Will open a new issue now. Is that okay? Thanks :)

Ok great :)


WIP KIP-709: Implement batching for fetchOffsets

This implements the AdminAPI portion of KIP-709: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173084258. The request/response changes was implemented in https://github.com/apache/kafka/pull/10954.
It updates the Admin APIs associated with the OffsetFetch API. This PR deprecates the old single group ID API and adds new APIs to take in multiple groups at a time for fetching consumer group offsets.

Thank you for the reviews @rajinisivaram and @dajac. As discussed offline, I have split this PR into 2: 1 for the request/response side of things, and will open another one for the AdminAPI side of things, as we still need to finalize some portions of the API. Since it would be good to get the request/response side of things into the 3.0 release, I have opened that portion of the changes in https://github.com/apache/kafka/pull/10962. I will keep this PR for the Admin API changes and will update it as the comments have suggested. Once we have finalized the Admin API design, we can come back to this PR.

Closing this in favor of https://github.com/apache/kafka/pull/10964

@rajinisivaram @dajac I just sent out a proposal for the Admin APIs to the mailing list, regarding ListConsumerGroupOffsetsOptions. For now I've closed this pull request in favor of https://github.com/apache/kafka/pull/10964.


Added ungrouping X if grouped

it works well but i guess may be small enhancements will improve the the user experience
change X text to icon (same color) as search table or clear dropdown display X only if the column has grouped by enabled.

Fixed the Suggestions, Please have a look.
Thank you!!!


Not seeing the new switches from 1.0 update

I am now on 1.1 and you are on a roll! Are these switches available now or are they still in development. I read the change log and it appears i should be seeing 4 different switches for the vacuum.

still fixing, but you will have to clean your cache for them to appear. (use cleanCache option )

what is the best way to use cleanCache?

add option in your config.json "cleanCache":true on tou plugin config section.
Restart homebridge
Remove option in your config or set it to false.
0.1.2 on its way ... will stay there for tonight ;p

Would you be able to help show me where exactly “cleancache”:true is placed in the config file?

Would you be able to help show me where exactly “cleancache”:true is placed in the config file?

like this :
"platforms": [
  {
    "platform": "HomebridgeDeebotEcovacs",
    "email"<EMAIL_ADDRESS>    "password": "toto",
    "countryCode" : "FR",
    "cleanCache": true
  }
]

@mattson16 is it ok now ?

i've got it fixed now. i ended up having to set up the homebridge server again but it's all good now.

MAy I ask if everything is working with your deebot ?


[weed mount] panic

Describe the bug
weed mount panic when read data. weed mount log:

System Setup

List the command line to start "weed master", "weed volume", "weed filer", "weed s3", "weed mount".
OS version
Ubuntu 18.04.5 LTS
output of weed version
version 30GB 3.22 7c58e9782a373438be6836dea90874db7c55bd32 linux amd64
Based on release version 3.22, I added some PR. See: https://github.com/seaweedfs/seaweedfs/compare/3.22...paochiang:seaweedfs:3.22-r3.1.0-fixread

Expected behavior
no panic
Additional context
product environment, it's hard to reproduce

Thanks for reporting! this should have been fixed in https://github.com/seaweedfs/seaweedfs/pull/3527

Thanks for reporting with details! this should have been fixed in #3527

@chrislusf
It's not right, because the version I used(https://github.com/paochiang/seaweedfs/tree/3.22-r3.1.0-fixread) has added this fix(https://github.com/paochiang/seaweedfs/commit/cec3f033202c84dd71d8f7b13c0dc922357462ed).

Hard to tell. The rc.downloaders is surely initialized. and chunkView should never be nil either.

What is the use case it was running?

What is the use case it was running?

Deep learning, model training.

what is the read write pattern?

Sorry, I didn't know that.  I'll ask next week, but I'm not sure if I can get the useful information.

what is the read write pattern?

There are append write and sequential read modes, but it is not clear if there are other modes.

@chrislusf
I looked up all the weed mount logs, new Panic found in weed mount:

seaweed code: https://github.com/paochiang/seaweedfs/tree/3.22-r3.1.0-fixread

the branch is missing a few changes. For example, the SwapFileChunk ReadDataAt() is missing a read lock.

Thank you, I will do a check.


🐛 [firebase_crashlytics] 'Flutter/Flutter.h' file not found

Bug report
When I run on iOS I get this error from Crashlytics
FLTFirebaseCrashlyticsPlugin.h:8:9: 'Flutter/Flutter.h' file not found
FLTFirebaseCorePlugin.h:8:9: 'Flutter/Flutter.h' file not found
Steps to reproduce
I am using the master channel version of flutter
I am using the master channel version of crashlytics
I am using a real device
  firebase_crashlytics:     git:       url: git://github.com/FirebaseExtended/flutterfire       path: packages/firebase_crashlytics/firebase_crashlytics
Expected behavior
To run
Additional context

Flutter doctor

[✓] Flutter (Channel master, 2.1.0-13.0.pre.199, on Mac OS X 10.15.6 19G2021
    darwin-x64, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Xcode - develop for iOS and macOS
[✗] Chrome - develop for the web (Cannot find Chrome executable at
    /Applications/Google Chrome.app/Contents/MacOS/Google Chrome)
    ! Cannot find Chrome.
Does the issue presist if you use the latest pub versions instead?

firebase_crashlytics.podspec  is missing s.dependency 'Flutter'
https://github.com/FirebaseExtended/flutterfire/blob/09277c49bb3a10208a2e117d149a4fbffc9bfb7a/packages/firebase_crashlytics/firebase_crashlytics/ios/firebase_crashlytics.podspec#L33-L34
https://github.com/flutter/flutter/pull/78592 stopped trying to link Flutter to pods that don't declare it as a dependency.  Also reported in duplicate https://github.com/flutter/flutter/issues/78969.

That's the only podspec I see that's missing s.dependency 'Flutter' or s.dependency 'FlutterMacOS'.


Adding Gradle related file extensions

Describe the feature
Adding Gradle related file extensions(.gradle, .gradle.kts)
Any alternative you've considered ?
Adding it in gradle side plugin settings
but in this way, it is harder to keep the consistency between the two
cc @minwoox

How do you say, @mathieucarbou ?

Yes, sure. Please send a PR :-)


Bot Offline

Seemed to have turned off sometime around 3 p.m. EST. Any idea how to fix?

Back online now! That was strange...

I have restarted the bot, usually that helps. Thanks for the heads up.


When i build with xcode i am getting this error

Make sure to check the existing issues in this repository
If there is no issue for your problem, tell us about it
Please, ensure your title is less than 63 characters long and starts with a capital
letter.
Please, provide the following version numbers that your issue occurs with:

CLI: (run tns --version to fetch it)
Cross-platform modules: (check the 'version' attribute in the
node_modules/tns-core-modules/package.json file in your project)
Runtime(s): (look for the "tns-android" and "tns-ios" properties in the package.json file of your project)
Plugin(s): (look for the version numbers in the package.json file of your
project and paste your dependencies and devDependencies here)

Please, tell us how to recreate the issue in as much detail as possible.
Describe the steps to reproduce it.
Is there any code involved?

provide a code example to recreate the problem
(EVEN BETTER) provide a .zip with application or refer to a repository with application where the problem is reproducible.

Closing as not enough information s provided


Keyword parameters and multiple statement analysis

What does this PR do?

Allows multiple query parameter patterns at the same time.
Replaces all strings with dummy ones of the same length and ignores comments when searching for parameters, fixing the need to manually specify all keywords with keywords=[...]
Replaces begin and commit with a comment, else the file is actually executed against the DB (caused me some headaches!).
Allows multiple prepared statements analysis if a separator pattern is provided, fixes https://github.com/UniqueVision/plpgsql-lsp/issues/12. Detects duplicated statements.
Updated textmate with common query parameter patterns and pg catalog functions

Is it tested? How?

Updated keyword parameters tests and pending multiple statement tests
Posting this here in case you're considering merging and have some feedback. So far it's been working correctly in my own scripts (mostly regular sql queries and migration files and some plpgsql). With some tests and refactoring I think this would be a nice addition instead of having a separate extension
Example:
"plpgsqlLanguageServer.keywordQueryParameterPatterns": [
    "@{keyword}",
    "sqlc\\.arg\\('{keyword}'\\)",
    "sqlc\\.narg\\('{keyword}'\\)",
  ],
  "plpgsqlLanguageServer.statementSeparatorPattern": "-- name:[\\s]+.*",

Thanks for the great feature suggestion!!
We have received input from others and there is certainly a need for control by comments.
We would like to make a release after the comments have been corrected.

Hi @danicc097
The migrationsFolder option has nothing to do with this PR.
I want to merge this PR only as a multiple statement parsing function, please remove the migrationsFolter option and create a new PR.

@danicc097
We released v2.9.0.


About evaluation on P3M500

Hi, thnaks for releasing the great repo and paper.
I evaluate matteformer and vitmatte (both using pretrained weight) on P3M500, but both model's MSE error (times 1e3, computed on unknown areas) are 10 times of your result in Table 4, so are you scaling 1e2 for mse error in unknown areas?

Hi, thanks for your question.
The evaluation code given by ViTMatte evaluates MSE on only trimap unknown region. However, since the methods in Table 4 are not all trimap guided, it is unfair to evaluate in that way. So our results are evaluated in the whole image.
As ViTMatte for instance, for same the inference result, MSE would be 13.17 in unknown regions and be 1.24 in the whole image.

Hi, thnaks for releasing the great repo and paper. I evaluate matteformer and vitmatte (both using pretrained weight) on P3M500, but both model's MSE error (times 1e3, computed on unknown areas) are 10 times of your result in Table 4, so are you scaling 1e2 for mse error in unknown areas?

Hi, thanks for your question.
The evaluation code given by ViTMatte evaluates MSE on only trimap unknown region. However, since the methods in Table 4 are not all trimap guided, it is unfair to evaluate in that way. So our results are evaluated on the whole image.
As ViTMatte for instance, for same the inference result, MSE would be 13.17 on unknown regions and be 1.24 on the whole image.


Feature Request: Don't reset timer until tab is visible for a few seconds

I often use the mouse wheel to scroll through my tabs. It looks like when I scroll over an inactive tab it resets the timer.

+1

+1 It is very useful feature for some users

+1


[ci skip] [cf admin skip] NO_CI adding bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I've added bot automerge as instructed in #10.
Merge this PR to enable bot automerging.
Fixes #10

@conda-forge-admin please rerender


build and release linux/amd64 images

use beefier 8-core runners for building linux/amd64, linux/arm64 and linux/ppc64le images
Closes #1341

ready to go!


"nox-review wip" fails with "_gdbm.error: Malformed database file header"

Issue description
nox-review wip fails with _gdbm.error: Malformed database file header.
Steps to reproduce
On NixOS 18.09:

cd to a clone of https://github.com/NixOS/nixpkgs
nix-shell -p nox --run "nox-review wip --against HEAD^"

Expected
The builds affected by the last commit are being tested.
Observed
Traceback (most recent call last):
  File "/nix/store/ffpdsda5hm017fx48170ad2wxhllk3r4-nox-0.0.6/bin/.nox-review-wrapped", line 12, in <module>
    sys.exit(cli())
  File "/nix/store/7v2xsnl1svflfqm73hnbbmhmm4mvwi0s-python3.6-click-6.7/lib/python3.6/site-packages/click/core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "/nix/store/7v2xsnl1svflfqm73hnbbmhmm4mvwi0s-python3.6-click-6.7/lib/python3.6/site-packages/click/core.py", line 697, in main
    rv = self.invoke(ctx)
  File "/nix/store/7v2xsnl1svflfqm73hnbbmhmm4mvwi0s-python3.6-click-6.7/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/nix/store/7v2xsnl1svflfqm73hnbbmhmm4mvwi0s-python3.6-click-6.7/lib/python3.6/site-packages/click/core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/nix/store/7v2xsnl1svflfqm73hnbbmhmm4mvwi0s-python3.6-click-6.7/lib/python3.6/site-packages/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/nix/store/7v2xsnl1svflfqm73hnbbmhmm4mvwi0s-python3.6-click-6.7/lib/python3.6/site-packages/click/decorators.py", line 17, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/nix/store/ffpdsda5hm017fx48170ad2wxhllk3r4-nox-0.0.6/lib/python3.6/site-packages/nox/review.py", line 71, in _
    f(*args, **kwargs)
  File "/nix/store/ffpdsda5hm017fx48170ad2wxhllk3r4-nox-0.0.6/lib/python3.6/site-packages/nox/review.py", line 106, in wip
    attrs = differences(packages_for_sha(sha),
  File "/nix/store/bkfmsfnzpvgy07ajis3zwpslic75g7pg-python3.6-dogpile.cache-0.6.7/lib/python3.6/site-packages/dogpile/cache/region.py", line 1270, in decorate
    should_cache_fn)
  File "/nix/store/bkfmsfnzpvgy07ajis3zwpslic75g7pg-python3.6-dogpile.cache-0.6.7/lib/python3.6/site-packages/dogpile/cache/region.py", line 864, in get_or_create
    async_creator) as value:
  File "/nix/store/bkfmsfnzpvgy07ajis3zwpslic75g7pg-python3.6-dogpile.cache-0.6.7/lib/python3.6/site-packages/dogpile/lock.py", line 186, in __enter__
    return self._enter()
  File "/nix/store/bkfmsfnzpvgy07ajis3zwpslic75g7pg-python3.6-dogpile.cache-0.6.7/lib/python3.6/site-packages/dogpile/lock.py", line 86, in _enter
    value = value_fn()
  File "/nix/store/bkfmsfnzpvgy07ajis3zwpslic75g7pg-python3.6-dogpile.cache-0.6.7/lib/python3.6/site-packages/dogpile/cache/region.py", line 819, in get_value
    value = self.backend.get(key)
  File "/nix/store/bkfmsfnzpvgy07ajis3zwpslic75g7pg-python3.6-dogpile.cache-0.6.7/lib/python3.6/site-packages/dogpile/cache/backends/file.py", line 220, in get
    with self._dbm_file(False) as dbm:
  File "/nix/store/hy65mn4wjswqih75gfr6g4q3xgqdm325-python3-3.6.6/lib/python3.6/contextlib.py", line 81, in __enter__
    return next(self.gen)
  File "/nix/store/bkfmsfnzpvgy07ajis3zwpslic75g7pg-python3.6-dogpile.cache-0.6.7/lib/python3.6/site-packages/dogpile/cache/backends/file.py", line 215, in _dbm_file
    "w" if write else "r")
  File "/nix/store/hy65mn4wjswqih75gfr6g4q3xgqdm325-python3-3.6.6/lib/python3.6/dbm/__init__.py", line 94, in open
    return mod.open(file, flag, mode)
_gdbm.error: Malformed database file header

This also occurs without --against HEAD^ if there are uncommitted changes.
Technical details

system: "x86_64-linux"
host os: Linux 4.14.76, NixOS, 18.09.932.09195057114 (Jellyfish)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.1.1
channels(root): "nixos-18.09.932.09195057114"
channels(das-g): ""
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

iirc nox has a cache in /tmp, remove it and everything should work.

Yep, that worked:
rm /tmp/nox.dbm.${USER}

I guess nox could attempt that itself or at least give a hint, but that'd probably be more of a feature request for https://github.com/madjar/nox, so I'm closing this bug report.


[Service Modal Routes 2a of 3] DCOS-12423: Show marathon errors in service config display

Service Modal Routes 1 of 3: https://github.com/dcos/dcos-ui/pull/1828 Merged!
Service Modal Routes 2a of 3: https://github.com/dcos/dcos-ui/pull/1853
Service Modal Routes 2b of 3: https://github.com/dcos/dcos-ui/pull/1871
This PR ensures that we do display marathon errors on the service configuration page, when they emerge.

Diff for review can be found here: https://github.com/dcos/dcos-ui/compare/mlunoe/feature/DCOS-12423-add-routes-for-the-new-create-service-modal...mlunoe/feature/DCOS-12423-add-routes-for-the-new-create-service-modal-2?expand=1 Merged!

Run unit tests

Run unit tests

LGTM :shipit:

Run integration tests

Run integration tests

Ok, rebased this guy! @MatApple would ❤ some 👀 on this :one: so we can make sure to display marathon errors if they are present!

This is btw. related to this issue I discovered: https://github.com/dcos/dcos-ui/pull/1830/files#r102314678

Run integration tests

@mlunoe - integration test is failing:
164 passing (9m)
24 pending
1 failing

Service Form Modal Picker should have three options to choose from:
CypressError: Timed out retrying: expected [ Array(4) ] to deeply equal [ Array(3) ]
at Object.cypressErr (http://localhost:4200/__cypress/static/js/cypress.js:5719:15)
at Object.throwErr (http://localhost:4200/__cypress/static/js/cypress.js:5684:22)
at Object.throwErrByPath (http://localhost:4200/__cypress/static/js/cypress.js:5711:21)
at $Cy._retry (http://localhost:4200/__cypress/static/js/cypress.js:6654:26)
at http://localhost:4200/__cypress/static/js/cypress.js:8920:28
at tryCatcher (http://localhost:4200/__cypress/static/js/vendor.js:46486:31)
at Promise._settlePromiseFromHandler (http://localhost:4200/__cypress/static/js/vendor.js:44621:31)
at Promise._settlePromiseAt (http://localhost:4200/__cypress/static/js/vendor.js:44697:18)
at Promise._settlePromises (http://localhost:4200/__cypress/static/js/vendor.js:44813:14)
at Async._drainQueue (http://localhost:4200/__cypress/static/js/vendor.js:42180:16)
at Async._drainQueues (http://localhost:4200/__cypress/static/js/vendor.js:42190:10)
at MutationObserver.Async.drainQueues (http://localhost:4200/__cypress/static/js/vendor.js:42018:14)

That is because of this error unrelated to this PR: https://github.com/dcos/dcos-ui/pull/1953

Rebased off of master where the fix has now merged

Was just about to merge! Haha

Run integration tests


Also mark notification as seen when reacting/replying

https://github.com/lbryio/lbry-desktop/pull/4923/files marks it as read, but I still saw the count with bell icon

I noticed it marked it as read on one device notification list, but not the other (until I refreshed). Does it not get these updates from the push service?


Use Declaration Merging Instead of Generics

Description
The current API uses generics, which makes it hard to deal with it on multiple layers. Especially from a pilet POV its a huge pain.
We need a better way - that originates the API already from piral-core and only extends it all the way.
Background
Right now the app shell should / would alias the "final" API and use it in generics. As such MyAppShellApi becomes a thing. It should not be. It will prevent cross Piral solutions (pilets) independent of any pattern libraries or other dependencies - just because the APIs are named differently (but share the same core or are even 100% the same).
Discussion
This will have an impact on how pilet API extensions are written. The intention here is not to make things more complicated or worse, but to simplify.
By using declaration merging we are on the road to have a single Piral instance only (which makes sense - multiple instances are academic anyway).

Landed in develop.


Updating from having children to having nil children doesn't remove children

This is something I hit in Rojo trying to upgrade to Roact 1.0!
When an update causes a change from:
Roact.createElement("Parent", nil, { Child = Roact.createElement("Folder") })

to
Roact.createElement("Parent", nil, nil)

the Child folder won't be removed. If children is specified as an empty table instead, the object appears to be removed.
Here's the relevant component in Rojo: https://github.com/LPGhatguy/rojo/blob/1e130971269367da2f58c8a78b464cfcd26650af/plugin/src/Components/App.lua#L82-L142
Changing line 83 from local children to local children = {} fixes the Rojo bug.

There's two ways we can fix this, I think:

Default children to {} in createElement
Thread the nil through the reconciler and unmount everything when the element has nil children, skipping the diffing work.

I'm leaning towards the latter but the former would also work for fixing this.

I don't love the first option, since I think leaf elements are pretty plentiful. It'd be a shame to give them an extra unused table!
I think the second option might just boil down to fixing our child table iterator stuff to just return nil when the input is nil, and everything else should just work itself out, right?

This issue was introduced by ea822f62ec11be3f979344cc34e03b81e48b0b53.

Perfect, we should be able to just revert that?
I think it was a perf improvement change.

opened a PR to revert that commit in #210.


Add pa-ur locale (Punjabi Shahmukhi - Urdu script)

We already support pa, Punjabi Gurmukhi, a language used in Punjab,
India. This is to add pa-ur, Punjabi Shahmukhi, a language used in
Punjab, Pakistan, that uses the Urdu script.
More information on the two languages can be found on this Wikipedia
page: https://en.wikipedia.org/wiki/Punjabi_language
The reason pa-ur was chosen as locale code is that pa is the
language code for Punjabi and ur is the script subtag for Urdu. More
information on this can be found on this Mozilla developer docs page:
https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/lang#Language_tag_syntax
Docs followed: https://docs.publishing.service.gov.uk/manual/add-translation-whitehall.html
Zendesk ticket: https://govuk.zendesk.com/agent/tickets/4371686
Related PRs:

https://github.com/alphagov/whitehall/pull/5915
https://github.com/alphagov/government-frontend/pull/1942
https://github.com/alphagov/govuk-content-schemas/pull/1034
https://github.com/alphagov/content-store/pull/791
https://github.com/alphagov/publishing-api/pull/1883

For those interested, I've got some thoughts here https://github.com/alphagov/publishing-api/pull/1899#discussion_r576183338 as to which code I think we should have used.


yt cats or yt dogs loading .001% of the time

yt cats or yt dogs loading .001% of the time
running yt cats or yt dogs worked one time for each doing this for no thumbnail or thumbnail.
I tried this like over 30 or more times.

I am new to Linux trying to switch over from windows. Learning about all the power app for Linux.
I love your add on for YouTube.
Any way to make the searching... load faster with results?
Thank you.
P.S. the thumbnails are working now.
You Rock!

Hi @PingLH , thank you again, YOU are breathtaking! haha
It is now fixed :)


Modify color models that expect INTs to allow floats as well

Color models like CMYK, for instance, are currently expecting integer values but there is no reason they cannot use float values as well. To be more flexible, convert those functions to allow either.

What do you think that the conversion functions should output? Ints or floats? Maybe Chameleon.convert/1 should have an optional third argument that's a keyword list to specify?

I am accustomed to seeing INTs used for RGB, CMYK, and HSL. My first inclination is to return which ever data type is input, so if you require float precision we return a float back, otherwise you give us ints, and we give you ints back.

I have a use case where I'd like to force ints regardless of input. The reason is that the hardware that's receiving the color only takes integers, so I'd like to guarantee integers without having to call round manually. On the other hand, for colorspace conversions that use RGB as an intermediate step, I'd want the RGB step to avoid rounding even if it's given integers.

ok, that makes sense.
It might make sense to make an optional 3rd arg (map) for convert now called opts.
The first available option could be float_precision: BOOL (or another name). What do you think @fhunleth ?

I was thinking the invocation would look like this:
Chameleon.convert(input_color, Chameleon.RGB, precision: :float)

I'm not sure that :precision is the right name, but I like it better than :type. I switched it from a boolean in case there's ever a reason have another value.

yes! i like that.
trying to think ahead to other possible values - the ones we know about today are int and float, but is it possible a future use would desire an output in base 16? or base 2?
Also, since (I think) we agreed that calculations internally should avoid rounding, i think this setting really refers to output precision. Ergo, maybe the setting is named "output_format" ?

I like the "output_" part and I waffle between "output_format" and "output_type".
I'm realizing that there's another option and that's to define a different color type. For example, there could be Chameleon.RGBf where the r, g, and b values are floats that go between 0 and 1. That would match OpenGL's RGB formats and seems like it would get rid of multiplications and divisions by 255 in many conversions. For example, https://github.com/supersimple/chameleon/blob/v2/lib/chameleon/cmyk.ex#L80-L82 could be changed to convert to Chameleon.RGBf.
Then there could be Chameleon.RGB8 which would be the common 8 bit per component that is currently called Chameleon.RGB. It could always return integers and I think that would be totally fine and expected. It seems harmless for Chameleon.RGB8 to accept floats between 0-255 if the user provides them.

I like that idea of making new models.
That would follow the current conventions, and give the user to specify the format on input or output, as well as making the options virtually infinite.
I would like to be opinionated by retaining Chameleon.RGB and having that delegate to its default output (RGB8)

Sounds good.
I'm fully on board with Chameleon.RGB being RGB8. I think it would be a surprise if it wasn't for most users.
Regarding RGB8, I misnamed it. The name I've seen most often for it (after RGB) is RGB888.

sounds good. perhaps just an interface that delegates RGB8 and RGB888 to RGB will be best


: How do I use it in my code? I didn't see an export code feature.

Upper left corner -> file -> Export -> Export to VS 2019


Send the Survey Form data to API server?

Been trying to submit the survey form data to API server just like the widget form. However I am not successful so far as I am running into issues every time. Just wondering if anyone has tried & has any suggestions ?

Show me your code.
@keshavmesta

Make sure you are dispatching your action correctly.

Yes, all I had to do was connect the react component to the redux store. Had missed to include someActions here:
@connect(   state => ({     saveError: state.topics.saveError,   }),   {...someActions, initialize})


[request] add  page.waitForFocus(selector);

when i try to get element ,
in my case it may be in the middle of the page ,
i try to do this ,
await page.waitForSelector(selector );
await page.focus( selector );
await page.click(selector);

but i get this
Error Scrape: Node is either not visible or not an HTMLElement

because the selector was not visible ant this moment ,
i there any way to sure if element is focused at this moment ?

await page.waitForSelector(selector, visible: true);

it work to find the element in the page ,
but if you want to click it , the element must be in the view ,
and await page.waitForSelector(selector, visible: true);
not scroll it to be visible in the view of the page .
to reproduce it , try to click element ,that in the page ,
but not visible in the view " it may in the end of the page"

The click method should scroll the element into view.
Code: https://github.com/xvrh/puppeteer-dart/blob/master/lib/src/page/js_handle.dart#L350
Documentation: https://github.com/xvrh/puppeteer-dart/blob/master/doc/api.md#pageclick
This code is also working for me:
import 'package:puppeteer/puppeteer.dart';
import 'package:shelf/shelf.dart' as shelf;
import 'package:shelf/shelf_io.dart' as shelf;

void main() async {
  var server = await shelf.serve((request) async {
    if (request.url.path == '') {
      return shelf.Response.ok('''

<button>Button</button>
''', headers: {'content-type': 'text/html'});
    } else {
      return shelf.Response.ok('');
    }
  }, 'localhost', 0);

  var browser = await puppeteer.launch(headless: false);
  var page = await browser.newPage();

  await page.goto('http://localhost:${server.port}', wait: Until.networkIdle);

  await page.click('button');

  await server.close();
  await browser.close();
}

Can you provide a small reproducible example so I can better understand?

thanks for your time ,
it work after change from Until.networkIdle to Until.load


[Backport 17.03] Adding ipam options to ipam driver requests

Backport PR:https://github.com/docker/swarmkit/pull/2324

@nishanttotla @stevvooe @abhi  for the review.
NOTE: I had to nuke the api_client_test.mock.go file because has dependencies on types not anymore in docker, I checked master and I did not see the code there, let's see if it actually breaks something maybe some test.

NOTE: I had to nuke the api_client_test.mock.go file because has dependencies on types not anymore in docker, I checked master and I did not see the code there, let's see if it actually breaks something maybe some test.

Yea, that is kind of a problem. It will break the tests. What version of docker are you bringing in?

@stevvooe let's see this one how it goes, but basically I researched which was the PR that fixed the API name change in the swarmkit history and was:https://github.com/docker/swarmkit/pull/1876
and I backported this one too to remove that error. Let's see if now pass clean.
This seems to be enough to cleanly have a green CI.

@fcrisciani can we add a healthy number of comments here indicating why these changes were done, and a link to this PR? It may turn out to be useful in the future.

@nishanttotla the PR backported is the one that I put in the top description, in the commits there is also the reference to the master commit that got ported. I can copy paste the same description of the original PR here, or is there also some other information that you consider useful?

@fcrisciani I just meant a comment in networkallocator.go in the code either linking to this PR or a short description of this change, and that it diverges from the master branch. Not super critical though, just nice to have.

@nishanttotla @stevvooe PTAL

@fcrisciani close this out ?

Is this even needed at this point ? Its been open since Nov

@anshulpundir @nishanttotla not worth anymore, 17.03 is going EOL next month


Upgrade to dotnet 5

I have upgraded the project to dotnet5.
This did unfortunately have breaking changes so I fixed those as well.

Think the problem you see with "breadking" changes, is caused by you "upgrading" to NLog 5.0-beta.
You should stay away from NLog 5.0-beta/prerelease, since they were early attempts to support NetCore. But then Microsoft introduced NetStandard2 and then NLog 4.5 could be made. See also "What happend to NLog 5?" https://nlog-project.org/2017/12/20/nlog-4-5-is-near.html
https://www.nuget.org/packages/NLog.Targets.ElasticSearch ver. 7.5.0 works just fine with Net50.


Updated logic for unfurl

The current implementation for the unfurl is not working as expected. Unfortunately, I was having some trouble testing my code before merging, and sorry about that. With the current code, the unfurl is always set to True because of the dummy line as follows:
this.enableUnfurl = slackReporterConfig.enableUnfurl || true
Moved the logic to use disableUnfurl instead and hopefully that will fix the issue.

thanks @miguelofbc , released in 1.1.16
https://github.com/ryanrosello-og/playwright-slack-report/releases/tag/1.1.16


feat: update to use python distro

Which problem is this PR solving?

need for python distro in egs

Short description of the changes

update Tiltfile to set service name for python services
set honeycomb endpoint as default backup
use new distro in python namae service
remove debug env var for flask
update dockerfile with opentelemetry-instrument command

note: this should be updated with the beta package once available

EGS cloned to a new macOS arm64 host that has never run EGS before
cd the_clone/
git switch team.use-python-distro
cp .envrc_example .envrc
add an API key to .envrc
cd python/
asdf install
cd ..
tilt up py
wait for tilt services to come up
poke the curl greeting tilt resource

👇🏻
An Trace

stop tilt
cd python/
docker-compose up --detach
wait for docker services to be up
curl http://localhost:7007/greeting

👇🏻
An Trace


Add dye mass inventory over time

modification that would generate a dye mass inventory over time

output and plot "int.cz.dz" for x,y,z

Assumptions;

dye concentration is in g/m^3
dx, dy, and dz are in meters and represent the volume of the cell with a given concentration

Calculations

Calculate the volume in each cell;
volume_cell = dx * dy * dz (dz in has water level adjustments in it?)
Calculate the mass in each cell;
dye_mass_cell =  volume_cell * concentation_cell
Sum the mass in all cells and the result is one mass for every timestep.


Fix: Remove the action restriction of initComponentExtraCluster

What type of PR is this?
/kind bug

What this PR does / why we need it:
Remove the action restriction of initComponentExtraCluster
Which issue(s) this PR fixes:

Fixes #119
Special notes for reviewers:
@x893675 @Xvv-v

Does this PR introduced a user-facing change?

None

Additional documentation, usage docs, etc.:

@x893675 @Xvv-v

Codecov Report

Merging #126 (18ff86b) into master (6e3615b) will increase coverage by 0.00%.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master     #126   +/-   ##
=======================================
  Coverage   11.78%   11.79%
=======================================
  Files          98       98
  Lines       15108    15106    -2
=======================================
  Hits         1781     1781
+ Misses      13092    13090    -2
  Partials      235      235

Impacted Files
Coverage Δ

pkg/apis/core/v1/utils.go
55.05% <0.00%> (+0.38%)
:arrow_up:

/close


Implement missing race condition fix from master

What is the goal of this PR?
We patched a race condition that caused transactions to hang during closing a while ago but the patch was never released and only exists in master. During debugging of a new issue, we rediscovered the same problem, but are now more sure about the nature of the bug and a more correct fix. However, we are also certain that the original fix has proven itself to be stable, so in the interest of keeping master the same as the latest release, we are going to release the original fix as 1.8.3.
What are the changes implemented in this PR?

Add synchronized to transceiver methods to ensure that no calls result in a race condition.

Ok this works for now, but please make sure we link the proper fix in master to this PR so we know the real solution. I think it would be preferable that you submit and and write up the description in the PR on master @adammitchelldev 👍


Feed the backend URL into vite from a .env file

This fixes #18

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

Project coverage is 80.34%. Comparing base (d91e470) to head (d28d1f0).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #25   +/-   ##
=======================================
  Coverage   80.34%   80.34%
=======================================
  Files           4        4
  Lines         229      229
=======================================
  Hits          184      184
  Misses         45       45

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.