Selecting days 1-11 of the month changes the format in the display field from DD/MM/YYYY to MM/DD/YYYY

Date From:{{pikaday-input locale=en value=dateFrom  format='DD/MM/YYYY' class="form-control" name="dateFrom" onSelection=(action 'onChangeDateFrom') }}

In the date field using the above code, if a user selects a date between the 1st and 11th of the month the format of the date in the displpay field reverts from DD/MM/YYYY to MM/DD/YYYY. The date picker then behaves as if this is the selected date (ie if the user clicks back into the field, it will display the month from the MM/DD/YYYY format.)
I have these values being placed as query parameters in the URL string and they are inserted there correctly in a DD-MM-YYYY format, but even if the param is correct the field still displays the MM/DD/YYYY format.

check my comment in https://github.com/edgycircle/ember-pikaday/issues/162

Thank you for your response but I'm not quite sure how I can implement your recommendation in the above. I don;t have a fixed value I can pass in the moment(value) section because this is happening immediately when a user clicks into the date field.
Are you able to provide any advice on implementing your solution to the helper code in the OP?

Hi,
Same issue here but we found that ember-pikaday works well with DD-MM-YYYY and DD*MM*YYYY format but not with DD/MM/YYYY (it reverses to MM/DD/YYYY): perhaps an interpretation issue with / :thinking:


feat: Add a subtype?: string property to ExcalidrawElement.

This PR just adds an optional subtype property to ExcalidrawElement.  See #6958 and #6037 for details.

@DanielJGeiger  I am not sure if we should this change and merge it  to master before the other PRs, will merging this first help in any way ?

@ad1992 #6973 is a subset of #6037.  #6936 stages maintenance of #6037 like master stages development of release.  So, merging #6973 would help merge the other PRs.

@ad1992 #6973 is a subset of #6037. #6936 stages maintenance of #6037 like master stages development of release. So, merging #6973 would help merge the other PRs.

@ad1992 @dwelle Maybe I was unclear, I opened #6973 to help begin the review of MathJax support (#6037).

See #6037 instead for the full PR.


Create 0000-01-02-outoftheoffice9.md

https://github.com/outoftheoffice9/github-slideshow/pull/4#partial-pull-merging


ci(e2e): add Codecov secret for main wf

Issue or need
Badge wasn't reflecting the coverage increase after taking into account E2E tests coverage in #679 . After digging a bit, seems that the issue is that the secret isn't passed in the main workflow file

Proposed changes
Pass the secret

Quick reminders

🤝 I will follow Code of Conduct
✅ No existing pull request already does almost same changes
👁 Contributing docs are something I've taken a look at
📝 Commit messages convention has been followed
💬 TSDoc comments have been added or updated indicating API visibility if API surface has changed.
🧪 Tests have been added if needed. For instance, if adding new features or fixing a bug. Or removed if removing features.
⚙ API Report has been updated if API surface is altered.

#693  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @davidlj95 and the rest of your teammates on  Graphite


Couldn't load ASP.NET website automatically

Azure DevOps work item: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1265977
Testcases Affected
All scenarios via debug with VSCode.
Repro Steps

Create a folder and create a new console app. :

mkdir Angular
cd Angular
dotnet new angular

Open the folder with VSCode.

code .

Install C# extension.
Add required assets manually.
a. Open the Visual Studio Code command palette (View->Command Palette)Open the Visual Studio Code command palette (View->Command Palette)
b. run the command: '.NET: Generate Assets for Build and Debug'.
Press F5 and select '.NET Core'.
Update the argument of 'Program'.

Update:

Press F5 to start debugging.

ACTUAL
Couldn't load the website automatically.
EXPECTED
The program running correctly and load web site automatically.
INVESTIGATION
The web site display correctly when I tried to open it manually with listening URL in debug console window:

@NTaylorMullen: This sounds like it is by design. What is your full launch.json?

@NTaylorMullen:

@gregg-miskelly sorry for the delay. I wasn't able to reproduce so I pinged the CTI team who originally filed the issue. I'll close this for now until there's a follow up on the other side.

Had this issue today working through an Microsoft ASP.NET tutorial. Browser fails to launch automatically when debugging. Found the issue to be "serverReadyAction" in auto generated launch.json. It had the pattern as:
               "pattern": "\\\\bNow listening on:\\\\s+(https?://\\\\S+)"
too many backslashes?.... It work after changing it to:
               "pattern": "\\bNow listening on:\\s+(https?://\\S+)"
for reference:
https://github.com/OmniSharp/omnisharp-vscode/blob/master/debugger-launchjson.md#starting-a-web-browser

@submodify do you have repro steps?

Was following this tutorial:
https://docs.microsoft.com/en-us/aspnet/core/tutorials/razor-pages/razor-pages-start?view=aspnetcore-5.0&tabs=visual-studio-code
Basically this (from the VS Code terminal):
dotnet new webapp -o RazorPagesMovie
code -r RazorPagesMovie
then hitting CTRL-F5 to debug. This doesn't launch the browser automatically as expected.
Looking at the generated launch.json , the "serverReadyAction" pattern is showing:
"pattern": "\\\\bNow listening on:\\\\s+(https?://\\\\S+)"
changing it to this works as expected:
                "pattern": "\\bNow listening on:\\s+(https?://\\S+)"
Windows 10
VS Code: 1.53.2
.NET 5.0.103
C# Extension 1.23.9


[Request for Protected Variable]  Page 99000889 "Machine Center Load"

Can the Variables PeriodType and AmountType be made protected on page 99000889 Machine Center Load?
This variables are user set on the page as fields so it would be deniable to be able to see what the user has set for extensibility.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Seemingly normal fine-tuning leads to dummy model

Seeing weird behavior in https://github.com/h2oai/h2ogpt/issues/376

maybe related to
8b127fae2bcdfc69266ce35f917a096fe5824a48
a67cf173979bf513b344ca3834ba22718fea393f
dea3fdd9f44ed585d9a89b678dffb9411b055494

forgot to pass --prompt_type=human_bot


[FEATURE] Rewrite BedAura

Is your feature request related to a problem? Please describe.
Current BedAura is a quick port from old phobos
Describe the solution you'd like
Rewrite module entirely (also add Bed item to Offhand)
Additional context
https://www.youtube.com/watch?v=hztFjFovFEw

Beds were only used on old 5b and 1.13+ servers i dont really see a use for bed aura rn


Readme file - added team info and github links for team members

Description
Updated ReadMe to include our team info and github links

it keeps all the previous teams info and adds our team as an addition


simplify maxAlignment

Because max is gigantic!

I don't know the relative costs... using runtime foreach structures would generate a considerably larger AST, but there's a high cost to template instantiations that I don't know how to trade against AST volume and CTFE overhead.

What about static foreach compared to CTFE foreach?

What about static foreach compared to CTFE foreach?

No difference at all. That's why we converted a lot of CTFE foreach to static foreach (clearer intent).

I just did a whole heap of tests. CTFE foreach substantially beat static foreach every time.
Can you produce evidence that they cost the same? It would seem that converting to static foreach might not be a good idea...

Sure see e.g. https://github.com/dlang/phobos/pull/5729
Maybe "not measurable in a build of Phobos" would have been the better wording.

It would seem that converting to static foreach might not be a good idea...

The real perf difference is negligible and static clearly shows intent. Also if you use static foreach you don't need to create the extra function. Did your tests consider this?

Sorry I wanted to link to https://github.com/dlang/phobos/pull/5989 (things are a bit hard to do with your phone only)

Also if you use static foreach you don't need to create the extra function. Did your tests consider this?

Yes, I compared the sensible implementation of each style. Just that static foreach was substantially slower in all my test cases.
I'm not sure how the function is a major problem?

Can you drop a gist of the tests you wrote? This seems to be a very interesting behaviour, as I would have expected that both static foreach and ctfe foreach would have (aprox) the same performance, with the observation that static foreach states the intent more clearly.
Since this seems to not be the case, I'd say it's an issue (bug?).

To measure timing differences I needed long loops, but I don't know how to measure overhead for short loops... we need a best-practice doc.

A best practice doc would be a good addition. There is also this idioms page

To measure timing differences I needed long loops, but I don't know how to measure overhead for short loops... we need a best-practice doc.

Best-practice for Phobos is to use static foreach as there's no noticable difference in the real world and it reads better.

there's no noticable difference in the real world

Erm... phobos can be extremely slow if you're not careful. And it doesn't help that everything in phobos seems to pull in everything else in phobos for good measure.
But anyway, is this fine? I don't think a super implementation is possible without ... expression.

So, is this bad?

I'm still in favour of the static foreach instead of the template recursion, as foreach will be faster

How would you write this with static foreach? You can't accumulate values from one loop iteration into the next...

I had to make the helper so I could use m as an "accumulator"

I just saw @UplinkCoder 's comment, as it was posted while I was typing the code suggestion.
To make it CTFE foreach, just remove the static from the static foreach inside the helper.

See, that's the only way I can think to write it, and I'm pretty sure it's worse than my PR.
My PR will gain from caching of leaf and near-leaf instantiations. The binary-subdivision means on long lists, the leaf instantiations are likely to be common, so you are only likely to pay a new-instantiation cost for the nodes near the root of the expansion tree, which is a logN cost. static foreach is strictly O(N) on every instantiation.

Incidentally, operator ... from C++ would make D compile a lot faster, because it would replace staticMap, and functions like this could be fully CTFE resolved.

just remove the static from the static foreach inside the helper

I thought non-static foreach on type tuples was deprecated and replaced by static foreach exclusively now?
I've received errors insisting that I use static foreach in old code... but I don't remember the exact context.


Project Implementation

Project Implementation
Overview
This document outlines the steps and approach for implementing the project selected in Week 2. The project aims to develop a Generative AI-based chatbot for medical prescription issuing. The chatbot will utilize a large language model (LLM) trained on extensive datasets of documented symptoms, diseases, and treatments, allowing users to interact with the AI to receive advice or potential prescription suggestions for common conditions.
Step-by-Step Plan
1. Data Collection (Week 3-4)

Objective: Gather and curate data related to major diseases and their corresponding symptoms, treatments, and medications. Focus will be on conditions such as Diabetes, Hypertension, Asthma, and Chronic Kidney Disease.
Tasks:

Research medical databases and gather clinical data for the mentioned major disease.
Structure the data into categories: symptoms, treatments, medications, lifestyle advice.
Ensure the data covers common cases as well as edge cases for more comprehensive training.

2. Model Training (Week 5-6)

Objective: Fine-tune a large language model (LLM) to specialize in handling medical data related to the selected diseases.
Tasks:

Preprocess the gathered data and format it for LLM training.
Fine-tune the LLM on the curated dataset, emphasizing medical terminology and patient interaction.
Validate the chatbot’s responses using test cases and adjust the model parameters for accuracy.

3. User Interface Development (Week 7-8)

Objective: Build an intuitive interface that users can interact with to consult the AI-based chatbot.
Tasks:

Develop a web or mobile interface for user interaction.
Implement features such as symptom input, prescription suggestions, and condition explanations.
Ensure the design is user-friendly, accessible, and adheres to privacy/security standards.

4. Backend Implementation (Week 7-9)

Objective: Set up the backend architecture to handle chatbot interactions, store user data securely, and maintain smooth system operations.
Tasks:

Set up a server to run the trained chatbot model.
Alternatively, if we may utilize Discord's JDA to create a discord based chatbot
Besides that we can use a framework with django to make a simple web based chatbot..
Implement secure data handling for user inputs and chatbot responses.
Create a database for logging interactions and storing necessary information (while maintaining user anonymity).

5. Testing and Validation (Week 10-11)

Objective: Ensure the chatbot provides accurate and reliable advice by running extensive tests.
Tasks:

Use a variety of user queries to test the chatbot’s effectiveness in providing appropriate medical advice.
Validate the chatbot’s performance using medical professionals for feedback.
Optimize performance based on test results, adjusting model outputs and refining the dataset.

6. Launch and Evaluation (Week 12)

Objective: Launch the chatbot and evaluate its performance in real-world scenarios.
Tasks:

Deploy the chatbot for public use or within a controlled environment for beta testing.
Collect user feedback and monitor performance metrics.
Continue to update and improve the chatbot based on user experiences.

Conclusion
This project will be implemented in a structured, phased approach, starting with data collection and leading to model training, interface development, and testing. The goal is to deliver a reliable, AI-based medical chatbot that can assist users in symptom analysis and potential prescription suggestions for common medical conditions.

Issue Submissions

[!important]
If there are any issues you need to submit related to a certain issue mentioned in the roadmap, please continue it as a discussion under the threads here. However, if there are any sub-issues under the main one mentioned here, it is to be made under that issue instead.

Sub-Issues:
For any sub-issues or specific concerns that fall under the main issue, please create a new submission within the relevant issue thread. This helps maintain clarity and allows for better tracking of the problem's scope.
Why is this important?
Keeping related discussions in the same thread enhances collaboration and reduces redundancy, allowing the development team to respond more efficiently.


Want to add solution of Birthday Gift Question

Aim
want to add solution of this question of codechef in c++ :
https://www.codechef.com/LTIME96C/problems/TWINGFT
Assign me this issue under LGM-SOC

What is the objective of the Script

Details

What the features will your script have

Programming language

[ ] C
[x] C++
[ ] Java
[ ] Python

I want to add solution of this question in java language as a participant of an LGM SOC 21 can you assign this to me also.

Go Ahead @Anuradha0501


Release version incorrectly incremented

The problem
Hello,
Like requested in the issue #838 I open a new bug.
Like I said, we practice the trunk base development and we release from trunk.
We use Python Semantic Release with Gitlab and we have a specific configuration file with a little more commit type.
We have a first job to make pre-release versions and a second to make final release versions.
Until PSR 9.5.0 we have no problem, but since 9.6.0 the incrementation of pre-release version is not incremented on the last release version:
I have a pre-release version 0.2.0-beta.3 and I make an 0.2.0 release version on the same branch.
I release a patch and PSR make me a 0.2.0-beta.4. And when I make the release I have a 0.2.1 release version.
In resume: 0.2.0-beta.3 -> 0.2.0 -> 0.2.0-beta.4 -> 0.2.1
Expected behavior
I have a pre-release version 0.2.0-beta.3 and I make an 0.2.0 release version on the same branch.
I release a new pre-release patch 0.2.1-beta.1 and after a couple of beta version I make a release 0.2.1.
I would like: 0.2.0-beta.3 -> 0.2.0 -> 0.2.1-beta.1 -> 0.2.1
Environment
We use a docker image based on python:3.12-alpine and versions are:
/ # python --version
Python 3.12.3
/ # pip --version
pip 24.0 from /usr/local/lib/python3.12/site-packages/pip (python 3.12)
/ # semantic-release --version
semantic-release, version 9.7.1
/ # pip freeze
annotated-types==0.6.0
certifi==2024.2.2
charset-normalizer==3.3.2
click==8.1.7
click-option-group==0.5.6
dotty-dict==1.3.1
gitdb==4.0.11
GitPython==3.1.43
idna==3.7
importlib_resources==6.4.0
Jinja2==3.1.4
markdown-it-py==3.0.0
MarkupSafe==2.1.5
mdurl==0.1.2
pydantic==2.7.1
pydantic_core==2.18.2
Pygments==2.18.0
python-gitlab==4.4.0
python-semantic-release==9.7.1
requests==2.31.0
requests-toolbelt==1.0.0
rich==13.7.1
setuptools==69.2.0
shellingham==1.5.4
smmap==5.0.1
tomlkit==0.12.4
typing_extensions==4.11.0
urllib3==2.2.1
wheel==0.43.0
/ #

We use poetry for our projects.
Configuration
PSR configuration:
[tool.semantic_release]
version_toml = ["pyproject.toml:tool.poetry.version"]
commit_message = "chore(release): {version}"
tag_format = "{version}"

[tool.semantic_release.branches.main]
match = "(main|master)"
prerelease = false
prerelease_token = "beta"

[tool.semantic_release.commit_parser_options]
allowed_tags = ["build", "chore", "ci", "docs", "feat", "fix", "perf", "style", "refactor", "revert"]
minor_tags = ["feat"]
patch_tags = ["build", "chore", "ci", "fix", "perf", "style", "refactor", "revert"]

[tool.semantic_release.changelog]
template_dir = "semantic_template"
changelog_file = "CHANGELOG.md"
exclude_commit_patterns = ["build", "chore", "ci", "docs", "perf", "refactor", "revert", "style"]

[tool.semantic_release.remote]
name = "origin"
type = "gitlab"

Build-system configuration:
[build-system]
requires = ["poetry-core"]
build-backend = "poetry.core.masonry.api"

Logs
logs for the command: semantic-release -vv version --prerelease --no-push:
psr_logs.txt
Additional context
Until PSR 9.6.0 everything works perfectly. We are actually blocked on version 9.5.0.
Copy of your message:
Initially looking at your git history, it looks like PSR is behaving as expected if the commits are parsed with the AngularParser (ie. Conventional Commit standard). build and chore do not trigger a version bump unless otherwise configured. By default only a fix and perf commit type trigger a patch bump.

Separately, I'm not sure what you meant by the statement: releases are based on tag and not on a specific branch. PSR selects the prerelease token & prerelease value and whether or not it should release based on which branch it is on. Common usage of trunk based developers use the default branch to release or use ReleaseFlow branching to have separate branches to perform releases. Ultimately though, PSR will not automatically be able to determine if it should be a prerelease or a regular release if you are releasing these from the same branch. Manual intervention via command line arguments can make this possible.

Thanks for your time.
Best Regards.

@JeromeCheviet, I think I know the answer now based on what changed from 9.5 to 9.6. I probably should have made it a breaking change just in case but you live and learn. I am very sorry it messed up your workflow.
If you could try swapping --prerelease with --as-prerelease and it should return to your expected result.

Hello @codejedi365 ,
I had tested with --as-prerelease with the version 9.7.2 and it perfectly working.
Thank you for your help.
I'm really sorry because I had read the changelog and seen this new option, but I thought both still worked (and I forgot about it later… ).
So it's my bad. Life is a long learning process :)
Best Regards.


Duplicated train stops are listed multiple times

Condense duplicated train stops into one entry.
There should be a number to indicate how many stops were condensed.

Fixed by a394c1413d4b0e6129a442a1df89b0b104ba8b06


Issue with 2.0.8 package

@riezebosch @jberezanski can one of you have a look at this?
https://chocolatey.org/packages/dotnetcore-runtime.install/2.0.8#files
Notice that the data.ps1 file still has a URL link to 2.0.7 download file.

As a side note, would it be possible to remove the AU update.ps1 files from the meta packages that are being pushed?
i.e. here:
https://chocolatey.org/packages/dotnetcore/2.0.8#files
https://chocolatey.org/packages/dotnetcore-runtime/2.0.8

According to the release . notes that is correct: https://github.com/dotnet/core/blob/master/release-notes/releases.json#L15-L16 😕

WAT!
That is in no way confusing!?!?  😢
So, does that mean that there were no underlying changes in the dotnetcore-runtime, but the overall version number got bumped?

@gep13  https://github.com/dotnetcore-chocolatey/dotnetcore-chocolateypackages/commit/dce9a6b6521c00d35374d7966b4cd74697a122e1 should fix the issue of Update.ps1 and json files being included in the nupkg's.

@riezebosch that is great! Thank you for getting that done! 👍

@riezebosch what was the outcome of this?  Has it been fixed?  If so, what was the issue?

I thought the package is correct because it points to the download location that Microsoft published? As soon as the will publish a new(er) version it will be updated again.

@riezebosch okay, so we are saying that there is nothing to do here.  2.0.8 of the outer package, still only install 2.0.7 of the inner one?

This is a MESS. A ROYAL MESS, even.
From https://github.com/dotnet/core/blob/master/release-notes/releases.json (fragments):

   "version-runtime": "2.0.8",
   "version-sdk": "2.1.200",
   "date": "05/08/18",
   "dlc-runtime": "https://download.microsoft.com/download/E/F/7/EF7302FE-4F84-4529-9E3A-893450F76501/",

   "runtime-win-x64.exe": "dotnet-runtime-2.0.7-win-x64.exe",

   "hosting-win-x64.exe": "DotNetCore.2.0.8-WindowsHosting.exe",

   "rps-win-x64.exe": "AspNetCore.2.0.8.RuntimePackageStore_x64.exe",

and

   "version-runtime": "2.0.7",
   "version-sdk": "2.1.105",
   "date": "04/17/18",
   "dlc-runtime": "https://download.microsoft.com/download/A/9/F/A9F8872C-48B2-41DB-8AAD-D5908D988592/",

   "runtime-win-x64.exe": "dotnet-runtime-2.0.7-win-x64.exe",

   "hosting-win-x64.exe": "DotNetCore.2.0.7-WindowsHosting.exe",

   "rps-win-x64.exe": "AspNetCore.2.0.7.RuntimePackageStore_x64.exe",

Notice that the runtime exe file name is the same, but the download url prefix is different.
From https://github.com/dotnet/core/blob/master/release-notes/README.md:

Latest Updates
You can download the latest updates for .NET Core.
.NET Core 2.0.7   <-- this links to https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.1.200-sdk-download.md

From https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.1.200-sdk-download.md:

You can download the Windows Server Hosting installer and run the following command from an Administrator command prompt: DotNetCore.2.0.7-WindowsHosting.exe (Updated to include ASP.NET Core 2.0.8)

and

If you need to install the Runtime Package Store separately, the following can be used.
AspNetCore.2.0.8.RuntimePackageStore_x64.exe

I've just tried installing https://download.microsoft.com/download/E/F/7/EF7302FE-4F84-4529-9E3A-893450F76501/dotnet-runtime-2.0.7-win-x64.exe and the installed runtime has 2.0.7 all over the place (folder paths, uninstall entries etc.), so it seems to be just a minor, in-place upgrade to 2.0.7 with no effect on version number (Sigh. Thanks, Microsoft.).
So, I believe that the .NET Core 2.0.8 release currently consists of:

a slightly updated 2.0.7 runtime
new WindowsHosting and RuntimePackageStore versions 2.0.8
new SDK version 2.1.200

I think what we should do is:

[ ] unlist dotnetcore-runtime.* 2.0.8 (because the version number is incorrect - there is no 2.0.8 runtime yet)
[ ] publish dotnetcore-runtime.* <IP_ADDRESS>80508 (package fix notation) with updated installer link
[ ] publish dotnetcore-windowshosting <IP_ADDRESS>80508 (package fix notation) with runtime dependency changed to dotnetcore-runtime.install <IP_ADDRESS>80508

This needs to be done manually, because our AU machinery is nowhere near the level of sophistication needed to handle this automatically...

Okay, a minor correction: the two dotnet-runtime-2.0.7-win-x64.exe files from both urls (from the 2.0.8 and 2.0.7 releases) have the same checksum, so the runtime is not slightly updated - it is, in fact, identical.
Revised TODO list:

[ ] unlist dotnetcore-runtime.* 2.0.8 (because the version number is incorrect - there is no 2.0.8 runtime yet)
[ ] publish dotnetcore-windowshosting <IP_ADDRESS>80508 (package fix notation) with runtime dependency changed to dotnetcore-runtime.install 2.0.7

@riezebosch What do you think? I can do this quickly.

@jberezanski I am very much happy to take a back seat on this one, and let you guys decide.  I am nowhere near up to speed on all of this to add anything of relevance.
Thanks you both for looking at this.

Shoot, I wrote too quickly without checking first: dotnetcore-windowshosting has no dependency on the runtime, so this package does not need fixing. Yay.
Therefore, all that remains to be done is unlisting the 2.0.8 runtime packages. I'll leave 2.0.8 in the streams info files (*.json) in the repo for now, so that the AppVeyor build does not try to do anything unwelcome. I doubt Microsoft will release a 2.0.8 runtime, I believe the next release will be 2.0.9.

Now chocolatey.org suddenly dislikes me and I am unable to unlist the packages - I got the "Error: Oh no, we broke something!" page after unchecking "List in search results" and clicking "Save" on https://chocolatey.org/packages/dotnetcore/2.0.8/Delete. Now I cannot even view https://chocolatey.org/packages/dotnetcore, because I keep getting "we broke something". Edge and Firefox. 😞
@gep13 could you please help and try unlisting dotnetcore, dotnetcore-runtime, dotnetcore-runtime.install and dotnetcore-runtime.portable versions 2.0.8?

@jberezanski hmm, I am seeing the same issues...
Give me some time and I will see if I can come up with anything...

@jberezanski the site is back up and running, and I have unlisted that package version.

Thanks! I have also successfully unlisted dotnetcore-runtime, dotnetcore-runtime.install and dotnetcore-runtime.portable versions 2.0.8. May I ask what the issue with the site was?

@jberezanski from time to time, due to excessive loads on the database, there are issues connecting to the database. we have to run maintenance on the database, to clean things up, in order for it to come back.

I see, thanks for explaining.


Configure cloudwatch logs for seedling server

Configuring a running system from AWS's docs
Will then add this to the to be built cf template

added this to IAM Role

{
      "Effect": "Allow",
      "Action": [
        "logs:CreateLogGroup",
        "logs:CreateLogStream",
        "logs:PutLogEvents",
        "logs:DescribeLogStreams"
    ],
      "Resource": [
        "arn:aws:logs:*:*:*"
    ]
  }

datetime_format = %Y-%m-%d %H:%M:%S.%f
ex 2015-08-03 19:32:02.592545

/etc/awslogs/awscli.conf
[plugins]
cwlogs = cwlogs
[default]
region = us-west-2

/etc/awslogs/awslogs.conf
[general]
state_file = /var/awslogs/state/agent-state

[/var/log/messages]
## Path of log file for the agent to monitor and upload.
file = /var/log/messages
## A batch is buffered for buffer-duration amount of time or 32KB of log events.
## Defaults to 5000 ms and its minimum value is 5000 ms.
buffer_duration = 5000
# Use 'end_of_file' to start reading from the end of the file.
# Use 'start_of_file' to start reading from the beginning of the file.
initial_position = start_of_file
## Name of the destination log group.
log_group_name = /var/log/messages
## Name of the destination log stream. You may use {hostname} to use target machine's hostname.
log_stream_name = {instance_id}
## Format specifier for timestamp parsing
datetime_format = %b %d %H:%M:%S

was getting unable to open database file in logs
Fix
$ sudo mkdir -p /var/awslogs/state

Next, test run: http://docs.aws.amazon.com/AmazonCloudWatch/latest/DeveloperGuide/EC2NewInstanceCWL.html
then take what's learned there and start the CF Template

## Additions to template

mv /etc/awslogs/awslogs.conf /etc/awslogs/awslogs.conf.stock
mv /etc/awslogs/awscli.conf /etc/awslogs/awscli.conf.stock
mkdir -p /var/awslogs/state

mv /home/ec2-user/kiln/config/cloudwatchLogs/awscli.conf /etc/awslogs/awscli.conf
mv /home/ec2-user/kiln/config/cloudwatchLogs/awslogs.conf /etc/awslogs/awslogs.conf

service awslogs start
chkconfig awslogs on


Check minimal state of charge

Possibly add lowest acceptable level to energy needed for next leg

Merged with minimum battery level issue


xds: Adds extension points to receive config update notifications

This is an experimental feature and the API will not be published at this time.
TODO:

add cluster_manager_impl_test
update broken tests

Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features: N/A
Signed-off-by: Ali Beyad<EMAIL_ADDRESS>

/assign @alyssawilk @adisuissa

/cc @goaway

/assign @lizan

https://github.com/envoyproxy/envoy/issues/21910 is also relevant here I think.

#21910 is also relevant here I think.

Good point, I referenced it in the change description.

@lizan friendly ping for your review of this PR, thanks!

/retest

@adisuissa I pushed a commit using a new XdsSourceId class that encapsulates the resource id state.  PTAL.

/retest

/retest

Overall LGTM, thanks! We can start with this and change things if the design changes down the road. /lgtm api
Should be reviewed by non-Googler. @mattklein123 / @alyssawilk to suggest a reviewer.

Thanks Adi!  Note: Lizan already approved as a non-Googler maintainer.

Yes @lizan can do the final approval.

Defer to @adisuissa for final merge.

Thanks for working through this one with me, @adisuissa !


Broken Tag detection

Hello @cometkim , while trying to update to v.0.6
I noticed an issue in the new query detection
we had a (ok, strange)
	const result = useFragment(
		spaceOrGroup.__typename === 'Space'
			? graphql`
					fragment SearchResult_space on Space {
						name
						thumbnailImage
						color
						spaceGroup {
							name
						}
					}
			  `
			: graphql`
					fragment SearchResult_spaceGroup on SpaceGroup {
						name
						color
						thumbnailImage
					}
			  `,
		spaceOrGroup,
	)

but those weren't recognized as needed ( with prod builds, ok with dev)
i'have extracted the fragments and now it's ok

Hey @eMerzh
Can you confirm if this issue is still reproducible?

Never mind, i got the case

Very nice,  thanks 👍


Add avahi service file under doc/

I needed one of these for my current project for lighttpd, so I thought it best to send it back upstream.

Thank you!
The configuration is fairly trivial.  Would you consider contributing the simple configuration without the Avahi GPLv2 license comment?
lighttpd is licensed under the BSD 3-clause.

Done.

And thanks for the thank you :)

@gstrauss is this ok now or are you worried about the license?

Looks fine.  I'll merge it this weekend.  Thanks!

Ok cool.


Amib1 ee 393 fix fetch bug

SonarCloud says no.  I wonder if we need a different approach - any HTTP status that isn't a success code should result in {success: false}, rather than the special-case of 500?


Merging design improvement branch with master + Logout button

I resolved lots of merge conflicts since the branch I implemented the redesign on was actually quite old. Because I didn't know how to merge it with #118 I created this PR to resolve all merge conflicts.
This branch should now be up to date and ready to merge with the upstream master branch.
Closes #118
Edit: Also adds a logout button to the settings page.

@lsc0498 is currently more deeply involved in our product’s design, so I recommend having Lennard review this PR as he is more capable of putting it in some broader context.


doc: 9 is listed as a prime in example code within spec

primes := []int{2, 3, 5, 7, 9,<PHONE_NUMBER>}

9 is not a prime.

Previously https://github.com/golang/go/issues/2870

For posterity:

It's a reference to a legendary article from the Journal of Irreproducible Results.

— @robpike

great reads: https://github.com/golang/go/issues/8830 https://github.com/golang/go/issues/10892 http://en.wikipedia.org/wiki/Paul_Erdős (esp. the last one)


Lint/InheritException false positive

Expected behavior
It should not give an offense unless we are inheriting from ::Exception
Actual behavior
It gives an offense when we inherit from classes named Exception within a module (i.e. classes that are not ::Exception.)
Steps to reproduce the problem
module MyModule
  class Exception < ::StandardError; end

  class AnotherError < Exception; end
end

RuboCop version
$ bundle exec rubocop -v
0.60.0

I feel this varies on Ruby's constant lookup and is out of scope of static analysis of rubocop. i.e. how will Rubocop figure out if MyModule has Exception class defined?


Ruby version for Heroku

Heroku doesn't like Ruby 2.3.5
seems to work if Gemfile.lock line 724  changed to:
RUBY VERSION
ruby 2.3.4p301

Helllo @cantino @dsander
Can you give us a suggestion to solve this problem?
remote: -----> Multipack app detected
remote: =====> Downloading Buildpack: https://github.com/cantino/heroku-selectable-procfile.git
remote: =====> Detected Framework: Selectable Procfile
remote: -----> Using deployment/heroku/Procfile.heroku as Procfile
remote: =====> Downloading Buildpack: https://github.com/heroku/heroku-buildpack-ruby.git
remote: =====> Detected Framework: Ruby
remote: -----> Compiling Ruby/Rails
remote:  !
remote:  !     An error occurred while installing ruby-2.3.5
remote:  !
remote:  !     Heroku recommends you use the latest supported Ruby version listed here:
remote:  !     https://devcenter.heroku.com/articles/ruby-support#supported-runtimes
remote:  !
remote:  !     For more information on syntax for declaring a Ruby version see:
remote:  !     https://devcenter.heroku.com/articles/ruby-versions
remote:  !
remote:  !
remote:  !     Debug InformationCommand: 'set -o pipefail; curl -L --fail --retry 5 --retry-delay 1 --connect-timeout 3 --max-time 30 https://s3-external-1.amazonaws.com/heroku-buildpack-ruby/cedar-14/ruby-2.3.5.tgz -s -o - | tar zxf - ' failed unexpectedly:
remote:  !
remote:  !     gzip: stdin: unexpected end of file
remote:  !     tar: Child returned status 1
remote:  !     tar: Error is not recoverable: exiting now
remote:  !
remote:  !     Push rejected, failed to compile Multipack app.
remote:
remote:  !     Push failed
remote: Verifying deploy...
remote:
remote: !       Push rejected to huggin.
remote:

I edited Gemfile.lock as indicated above and it works for me.

I downgraded the ruby version to 2.3.4 pushes to Heroku should work again. Thanks for reporting the issue @johnleeming

Many thanks @dsander

Oh, sorry for this, as a ruby developer I regularly use snapshot versions, and this one got somehow mingled into Gemfile.lock by mistake.

@knu No worries, I wasn't aware Heroku only supports specific ruby versions I assumed the ruby buildpack would use a version manager like rvm to install a requested version on demand.


Our Paths section - Improve design & responsiveness (issue #81)

resolving issue #81
I improved the design to better fit the figma, both in desktop and mobile view.
I also reorganized the files, and divided the component (similar to the be our friend component)

Paths component - the shell of the section, including the title and paths data
PathItem component - the single path item

This means i changed the import in the app/page.tsx to match the new location of the Paths component

@RoyTennenbaum
Yes I sent a DM to Efrat on discord but didn't get a response, so i decided to go with it. and like you said - worst case scenario we can always change it (:


:art: use downgrade jupyter-echarts master

as in subject. for now, let's submodule until we find a replacement.

Codecov Report

Merging #137 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #137   +/-   ##
=======================================
  Coverage   97.19%   97.19%
=======================================
  Files          61       61
  Lines        2106     2106
=======================================
  Hits         2047     2047
  Misses         59       59

Continue to review full report at Codecov.

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

That is the correct way!


evaluation

Hi,  dear Arrow, I have some questions as follow:

How to only do evaluation？
How to select a model when training on MSRVTT9K or do you just report the results of the final epoch(5th epoch)?

Hi @JewelChen2019,

Use --do_eval instead of --do_train to do evaluate only.
Report the best scores according to validation. It needs to uncomment L546.

Thanks.


YLXD41YL - mac address errors after 2024.10

Everything works fine o 2024.09. After updating to ver 2024.10 there are errors:
[D][esp-idf:000]: E (4412) system_api: Base MAC address from BLK3 of EFUSE version error, version = 77
Yaml:
substitutions:
  name: kuchnia-yeelight-ceiling

esphome:
  name: ${name}
  min_version: 2024.6.0

esp32:
  board: esp32doit-devkit-v1
  framework:
    type: esp-idf
    sdkconfig_options:
      CONFIG_FREERTOS_UNICORE: y
    advanced:
      ignore_efuse_mac_crc: true

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  use_address: <IP_ADDRESS>
  fast_connect: on
  manual_ip:
    static_ip: <IP_ADDRESS>
    gateway: <IP_ADDRESS>
    subnet: <IP_ADDRESS>

ota:
  - platform: esphome
    password: "XXXXX"

api:
  encryption:
    key: "XXXXX"

logger:

sensor:
  - platform: adc
    pin: GPIO36
    name: "${name} adc1"
    attenuation: 12db
  - platform: adc
    pin: GPIO32
    name: "${name} adc2"
    attenuation: 12db
#dodatkowe sensory
  - platform: wifi_signal
    name: "${name} WiFi Signal"
    update_interval: 300s
    device_class: "signal_strength"

output:
  - platform: ledc
    pin: GPIO19
    id: output_warm
    frequency: 4882Hz
  - platform: ledc
    pin: GPIO21
    id: output_cold
    frequency: 4882Hz
  - platform: ledc
    pin: GPIO23
    id: output_nightlight
    frequency: 19531Hz

light:
  - platform: monochromatic
    name: "${name}-nightlight"
    id: night_light
    output: output_nightlight
    gamma_correct: 0.7
    on_turn_on:
      - light.turn_off: ceiling_light
  - platform: cwww
    name: "${name}"
    id: ceiling_light
    cold_white: output_cold
    warm_white: output_warm
    cold_white_color_temperature: 6500 K
    warm_white_color_temperature: 2700 K
    constant_brightness: true
    gamma_correct: 0.4
    on_turn_on:
      - light.turn_off: night_light

You can upload old fw via ota. But you can't add it to ha

This is the same issue that https://github.com/esphome/issues/issues/6333 probably in the next release the ESPHome team will fix it.
You can fix it adding ignore_efuse_custom_mac
esp32:
  board: esp32doit-devkit-v1
  framework:
    type: esp-idf
    sdkconfig_options:
      CONFIG_FREERTOS_UNICORE: y
    advanced:
      ignore_efuse_mac_crc: true
      ignore_efuse_custom_mac: true

I've applied the required setting to the examples to avoid some hassle. Thanks for pointing out this issue and providing a solution!


How do you run the server?

Hello,
I can't figure out how to build this in a way that I later can run it. This is my first Rust thing ever. I have installed rustup and it got me cargo. I have run cargo build and it compiles everything, even if there are some deprecation warnings.
Running cargo run gives me:
a bin target must be available for `cargo run`

I've also tried cargo build --all-targets and the tests got my machine really hot, but still the same cargo run results.
I checked the video presentation linked in the README and saw the command cargo run --bin server -- -- used, but it gives me:
error: no bin target named `server`

I also looked at the Travis file and did the clippy things (w/o having the faintest idea about what I am doing), but same results.
Now I am out of ideas, and love me some clues.

Hi,

I have installed rustup and it got me cargo. I have run cargo build and it compiles everything, even if there are some deprecation warnings.

So far, so good!

a bin target must be available for cargo run

Cargo differentiates between libraries and binaries. Declarative-dataflow (the main directory) contains only the library. Check out the server/ directory for the server binary.
Clippy is a tool that checks our code for common issues / style problems. It's not required for the build to work.
Good luck!

Yes, that worked. Thanks!
I proposed an addition about this to the README. Maybe more non-rustians (or whatever you call yourselves :smile:) would benefit from that.

OK. So hadn't created the PR. Now I have proposed the add. 😏


use fuzzy instead of buildjet

Summary of changes
Changes introduced in this pull request:

use fuzzy instead of buildjet. It shouldn't require much of its resources and frees us completely from buildjet bills.

Reference issue to close (if applicable)

Closes
Other information and links

forest now has two runners, and fil-actor-states has one.

Codecov Report
All modified lines are covered by tests :white_check_mark:
:loudspeaker: Thoughts on this report? Let us know!.


Wik documentation howto

I forgot to push those changes :/

Can you double check the changes again @TheCedarPrince sorry for the mess


Adding History Functionality

Continuation of PR #184
https://developer.mozilla.org/en-US/docs/Web/API/History_API
It seems to me that the "history API" is a separate issue from the router (although other applications often try to combine them for some reason).

history.back(), history.forward() and history.go(int) seem like they belong in a "router" but the definitely don't belong in the routing service itself. Maybe we could have a "history" service which is kind of like the console service? I don't know how yew typically handles things like this.
history.pushState and history.replaceState seem super interesting to me since they can preserve an arbitrary state object through reloads. I didn't realize that this could be accomplished this way and it is super awesome! This should probably have a similar API to the storage services.

These could probably both be placed in a HistoryState service. I'm not 100% sure on what the API would look like though.

here is the Elm Navigation module, which this should probably be modeled after.
http://package.elm-lang.org/packages/elm-lang/navigation/latest/Navigation

The two main items in elm's Navigation are:
newUrl : String -> Cmd msg

    Step to a new URL. This will add a new entry to the browser history.

modifyUrl : String -> Cmd msg

    Modify the current URL. This will not add a new entry to the browser history.
    It just changes the one you are on right now.

Interestingly it returns the generic Cmd type. For yew, the equivalent type is found via:
type Html<CTX, MSG> = VNode<CTX, MSG>;

pub enum VNode<CTX, COMP: Component<CTX>> {...}

pub trait Component<CTX>: Sized + 'static {
    type Msg: 'static;
    type Properties: Clone + PartialEq + Default;

    ...
}

From personally using both yew and elm it seems to me that yew's "Msg" type is very different from elm's "Msg" type. They are both used similarly when within the user's library, but elm's Msg type seems somehow more... dynamic. Like elm can use it for things that are builtin to the library in some way.
I'm of the opinion that elm's approach here hampers learning -- being able to simply set window.location via a function or deal with the history directly within the update method is probably sufficient. Warnings should be placed in the docs to inform the user to not set history multiple times, but this is a secondary concern.
Another option would be to have Env have history/url modifying methods on it, but only allow those methods to be resolved once. Basically calling Env::set_location(url) would set an internal location, which would then get resolved once update had returned (and the same for the history object). We could even return an Err in the case it was set more than once (although this is probably unnecessary honestly, just overriding is probably sufficient).

closing as it looks like #184 will include history fiddling.


Emma

Emma Enkhtsetseg

I'm having compilation issues on my IDE with your submission, and getting the following error while running mvn install:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on project Assessment: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: There was an error in the forked process
[ERROR] org.apache.maven.surefire.testset.TestSetFailedException: Suite file /Users///take-home-webdriver-test/src/test/resources/runner/testng_suite.xml is not a valid file


StateDetection property TypeError

Hello,
I encountered an issue with your library; the code I used is the most basic one to run an example.
import MouseFollower from "mouse-follower";
import gsap from "gsap";

MouseFollower.registerGSAP(gsap);
const cursor = new MouseFollower();

Versions with this problem: 1.0.4 to 1.0.6
1.0.3 and below work fine.
Error details

Environment details
Edge 101.0.1210.53
React 18.1.0
Gsap 3.10.3 (3.10.4 doesn't solve this)
Sass 1.52.1

Hello! Thanks for the detailed report! Issue should be fixed in v1.0.7

Hello! Thanks for the detailed report! Issue should be fixed in v1.0.7

Yep, I confirm it's fixed.
Thank you very much! 👍🏻


Externalize bot messages

Messages are hardcoded in code, making changes impossible without recompilation.
Associate a key to each message and externalize it in a configurable file. Check if we can implement a manual i18n instead of relying only on azure translation service.

By default dotnet resource manager can't read resource file at runtime. but you should write a custom one like in this thread.
My suggestion is to follow the official documentation and this stackoverflow response.
We should wrap the IStringLocalizer interface usage like in the example for each module and put resx files inside a unique Resources shared folder.

In bot framework the culture can be read automaticatically from each request by using a custom middleware, for now we will not support that feature, but we leave that open for the future.

When using Rider's Localization Manager a Designer.cs file is auto-generated starting from the resx file. This file contains statically typed resources and can be referenced anywhere in the codebase. The official documentation recommend to use a decoupled way to read strings from the resx file, so we can safely delete these autogenerated files.
For more information look at this article on the previous way to use resources.

In resx file string, you cannot use \n and similar (They are read by string.Format like plain string). We can use placeholders for now to mitigate this problem


2023 housekeeping to dos

[ ] deploy gam macro model
[ ] streamline documentation of new data workflow
[ ] generate TP = 1 pseudo sample priors for reff

note TP = 2 override fix breaks "TP with/without vaccine plots", which are not in use at the moment


WebUI schema browser

Description
There should be a way to browse the schema in the WebUI.
I'm picturing an interface with collapsable/expandable tree elements, with a hierarchy of:

indexes
frames
views/fields

Success criteria (What criteria will consider this ticket closeable?)

[ ] There is a way to view the schema hierarchy in the WebUI, with indexes, frames, and fields all represented.

Moved to https://github.com/pilosa/webui/issues/


Snippets of code for each endpoint and langauge

As a user, I want to get snippets of code for each endpoint in each SDK language so that I can copy and paste the generated code and get going.

relates to docs. will decomp these when we approach building out a docs site generator.


Jwilaby/chatdown typescript

Proposed Changes
Converted Chatdown to use TypeScript for better organization and maintenance.

Pull Request Test Coverage Report for Build 1929

0 of 0   changed or added relevant lines in 0 files are covered.
14 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.09%) to 68.61%

Files with Coverage Reduction
New Missed Lines
%

packages/Chatdown/lib/index.js
1
95.26%

packages/Chatdown/bin/chatdown.js
13
84.25%

Totals

Change from base Build 1920:
-0.09%

Covered Lines:
4082

Relevant Lines:
5632

💛  - Coveralls

Tagged to 4.4, per @sgellock

This is now a bit stale, so I'm going to abandon this PR.  Let me know if you need a hug.


Update server.js

So i figured i add these comments to provide a comprehensive overview of each core function's purpose, parameters, flow, and usage context. Each section describes the key responsibilities and interactions of the function within the larger system.

This helps explaining the core functions of this server script

Just imo but might be better to put this on an md file right in root folder. I guess you mostly care about this if you're reading the codebase but an md might be more intuitive since I might not look to the bottom of a file.

agreed

architecture modules (~next week) should have extensive docs alongside every function, and every inference tracing back to which architecture module called it
aim is also to have meta-prompts to spin up new architectures faster ; ie. describe general purpose and have the legos put together ; docs for every existing process (starting next releases) will help towards the direction


Remove immutability to chains signing-secrets

Now that the secret is managed by an ExternalSecret, the secret should not be immutable so the secret can be synced.
rh-pre-commit.version: 2.2.0
rh-pre-commit.check-secrets: ENABLED

@gabemontero I'll slowly be adding back the changes that we needed to revert when I deprecated the creation of the signing-secrets. This change has been validated on infra-deployment in this PR.

Here are the links to the PRs that:

gives ownership of the signing-secret to ExternalSecret
sets the Orphan flag.

Here are the links to the PRs that:
* [gives ownership of the signing-secret to ExternalSecret](https://github.com/redhat-appstudio/infra-deployments/pull/3276)

* [sets the Orphan flag](https://github.com/redhat-appstudio/infra-deployments/pull/3288).

yep those are the guys
does it make sense to add some comment in the script noting those items dependencies for the signing secret stuff in this repo?

/retest

/retest

ok I'll watch the test logs live, see if I can ascertain what is up
/retest

also, given the validation that has already occurred in https://github.com/openshift-pipelines/tektoncd-results/pull/65 I'm inclined to merge this if these pipeline-service CI issues cannot be sorted out, but let's see how much triage process I can make today.
fwiw, the 2 current test jobs have been stuck in deploy-cluster for about 25 minutes as I type

So this error was repeated server times in deploy-pipeline-service:
Error from server (Only privileged service accounts may access): admission webhook "ingress-config-validation.managed.openshift.io" denied the request: Only privileged service accounts may access
command terminated with exit code 1
Failed to execute dev_setup.sh script, retrying ...
+ echo 'Failed to execute dev_setup.sh script, retrying ...'
+ sleep 5

but the task was ultimately deemed successful.
Then, test-pipeline-service failed quickly with:
[chains]
+ kubectl apply -k /workspace/source/operator/test/manifests/test/tekton-chains -n plnsvc-tests
serviceaccount/chains-test created
rolebinding.rbac.authorization.k8s.io/chains-test-edit-rolebinding created
rolebinding.rbac.authorization.k8s.io/chains-test-scc-rolebinding created
error: resource mapping not found for name: "simple-copy" namespace: "plnsvc-tests" from "/workspace/source/operator/test/manifests/test/tekton-chains": no matches for kind "Pipeline" in version "tekton.dev/v1"
ensure CRDs are installed first
command terminated with exit code 1
+ exit 1

which tells me the deploy-pipeline-service really did fail as the CRDs are not there
attaching the logs for others, I'll start looking at them in detail
deploy-pipeline-service.log
test-pipeline-service.log


otlp_config_linux.yaml - add otlphttp for metrics

Description: Add example how to send metrics over otlphttp
Link to Splunk idea: Based on created example for https://github.com/signalfx/tracing-examples/pull/169
Testing: Tested in https://github.com/signalfx/tracing-examples/pull/169
Documentation: N/A?

I think this could be the doc that could host the PR's contents: https://docs.splunk.com/observability/en/gdi/opentelemetry/components/otlphttp-exporter.html


Font Issue

is this example application still works? i got wired fonts and can not find out whats going on, on the screen.

I've cleaned up the example a bit and removed the broken font material


DO NOT MERGE: Test Elasticsearch index cleanup

Do not merge this PR as it is for testing the GitHub actions integration for #1302.

Testing actions on PR close.


fix broken link signalr-overview.md

Learn Build status updates of commit 56ec141:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

Line 0, Column 0: [Error: git-clone-failed] Failure to clone the repository `https://github.com/Azure-Samples/cognitive-services-speech-sdk#master`. This could be caused by an incorrect repository URL, please verify the URL on the Docs Portal (https://ops.microsoft.com). This could also be caused by not having the proper permission the repository, please confirm that the GitHub group/team that triggered the build has access to the repository.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

#sign-off

Learn Build status updates of commit a565a9b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/azure-signalr/signalr-overview.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


end-to-end test (release): Error: snapshot id 4 not found

Describe the bug
https://buildkite.com/risingwavelabs/main-cron/builds/1891#_
2024-02-23T16:23:34.102298669Z  INFO risingwave_ctl::common::context: clean up context
--
  | Error: snapshot id 4 not found
  | Backtrace:
  | 0: msg<alloc::string::String>
  | at ./.cargo/registry/src/index.crates.io-6f17d22bba15001f/anyhow-1.0.75/src/error.rs:83:36
  | 1: {async_fn#0}
  | at ./src/meta/src/backup_restore/restore.rs:125:39
  | 2: {async_fn#0}
  | at ./src/meta/src/backup_restore/restore.rs:191:49

Error message/log
No response
To Reproduce
No response
Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
No response
Additional context
No response

happened again: https://buildkite.com/risingwavelabs/main-cron/builds/1892#018ddbd9-a6b3-4fb9-a810-a783dc623508

https://buildkite.com/risingwavelabs/main-cron/builds/1893#018de100-0460-4447-9322-3a78228ac398

link #15320?

This is an expected error during test. I'll suppress it.


@webdev03 it is neccesary that this feature be added. Please continue to write it.

@webdev03 it is neccesary that this feature be added. Please continue to write it.
Originally posted by @JaydenDev in https://github.com/JaydenDev/Catalyst/pull/127#issuecomment-1005137092
Sorry I won't

@webdev03 it is neccesary that this feature be added. Please continue to write it.
Originally posted by @JaydenDev in #127 (comment)
Sorry I won't

ok fine then, btw if I really wanted to I could force merge it but I won't. Also reply to the post instead of making issue posts please.

I couldn't reply, the button didn't work. You locked it.

ok...?


Reviews section can be added

Reviews section can be added to help the user get more trust your website

can u please assign this issue to me ?


[GH-15885] Migrate changeCSS() to CSS variable in utils/utils.jsx, ln. 613

Summary

Remove changeCss() for .nav-pills__unread-indicator svg.
This is no longer required as CSS variable --mention-color is already used.
https://github.com/mattermost/mattermost-webapp/blob/c3f01ee92ca30d6bedf62aa93b6e117efd37f9a4/sass/layout/_sidebar-left.scss#L421
Ticket Link

Fixes https://github.com/mattermost/mattermost-server/issues/15885

Hello @tony-ho,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

Thanks for this, @tony-ho! You're right that its already in _sidebar-left.scss, but would you also mind adding it to _legacy-sidebar-left.scss? If you disable the new sidebar (Account Settings > Sidebar), it won't color the icon properly

Thanks @calebroseland, good pickup. I've added the fill property in _sidebar-left.scss.

QA for this PR will be done when the campaign branch is merged to master.


No Progress Data on upload

While uploading a file through "put", the object returned by "progress" event doesn't have "transferred" data.
Example:
this is always returned when i console.log progress data:
{ filename: '/test.zip',
  action: 'put',
  total: 268295573,
  transferred: undefined }

any other comment about this?

sergi, can you please help? I need this to build a progressbar of put (send exist file to other server).
All solutions that are here written, will not work and your script return allwas 'transfered: undefined' and i use the current version.
Then i tried to modify the emitProgress Function but nothing tests will work :(
I have added an entry to the object with test: data.test, andthe put function send now data.test with content 'hello world' but on ftp.on("progress" myfun) is nothing to see =(
a chunk is ok, i need not exact data, the final call will at the end say is all ok or not.
Im very happy if you can create a little update and include this.
Best regards, stefan


[lz4] Patch for CVE-2021-3520

Fixes potential memory corruption

See https://nvd.nist.gov/vuln/detail/CVE-2021-3520 for more details
This is the upstream patch by Jasper Lievisse Adriaanse.
Commit message of upstream patch: "Fix potential memory corruption with negative memmove() size"
Merged upstream pull request https://github.com/lz4/lz4/pull/972

Which triplets are supported/not supported? Have you updated the CI baseline?

No change to triplets.

Does your PR follow the maintainer guide?

Yes

Please sign the CLA first.

Please sign the CLA first.

Done. Note that Jasper Lievisse Adriaanse is the author of the upstream patch.

 Thanks for your help.

Please merge this to master. @dan-shaw  @Cheney-W


[New Feature] Add native laravel pagination

I have a table with 1k rows and I want to use native laravel pagination.
I don't know if is posible right now?
Something like:
$this->crud->setFromDb()->paginate(15);

Pagination docs: https://laravel.com/docs/5.4/pagination
Thanks.

Hi @juanem1 ,
I think $this->crud->enableAjaxTable() will help you out.
Cheers!

Hey, my idea is use the native pagination instead of ajax pagination.

Ok, reopened it :-)
What would be the benefit of using native pagination instead of ajax pagination?

Benefit is we don't have all the enableAjaxTable bugs ;-)
https://github.com/Laravel-Backpack/CRUD/issues/411

@adbmdp this does not avoid the issues occuring with the Ajax table.  When sorting or searching models, any fake columns created would still cause errors, because Laravel couldn't sort or query a column that wasn't in the DB.  You'd still have to load all of the models every time, and in fact I think the existing method of paginating is far better since you can navigate pages without reloading, and Laravel would have to load the models anyway.
This would still be a new feature but I think AJAX would be the preferred method of doing for any use case I can think of.

@jsiebach Can you recommend a simple method of returning to a certain page when editing a record, then? Because I need that in an app I'm building.

Sure - using the DataTables JS documentation, if you pass along a parameter to the constructor called displayStart, the pagination will start there.  So if you want to start with item 100, you could use the URL http://example.dev/admin/model?displayStart=100
Then edit your list.blade.php file like so (3 new lines close to the end):
      @if ($crud->ajaxTable())
      "processing": true,
      "serverSide": true,
      "ajax": {
          "url": "{{ url($crud->route.'/search').'?'.Request::getQueryString() }}",
          "type": "POST"
      },
          @if(Request::has('displayStart'))
          "displayStart": <?php echo intval(Request::get('displayStart')) ?>
          @endif
      @endif

Thanks. Now to propagate those pages to the edit view :)

I believe this issue has run its course.


Update builder.md

Builder interface has Color function(not Paint)

Closing this since there is an open pull request for the same change #95

Closing this since there is an open pull request for the same change #95


Tag a 1.3 release

Would be great if you could tag a 1.3 release so that a versioned release with the changes since 1.2 is available on packagist.
Thanks!

+1
Don't want to use code that has atrophied for 2.5 years, but would also prefer to not ride the dev tip. Composer/Satis can mark a particular changeset, but it is much better for the maintainer to tag the changeset than to choose something arbitrary.
While it may not be a sexy new feature, the project management work is just as helpful!

See #274


Update balenaio optimization timeout

Change default value for optimizationTimeout from 1 hour to 5.5 hours. This change is needed for the scheduler to run via automated github action. Runners use only 2 CPUs and 1 hour is not sufficient to reach a decent proposal for a schedule.
Change-type: patch

@balena-ci I self-certify!


Please add a License

If I didn't miss something, there is no license specified for the code in this repository.  Legally, this means that no one (except you, of course) is allowed to use it in any way.
As you put it on GitHub, I assume that this is not your intention.  So to give users more certainty how they can use this script, it would be great if you could add some license.  If you are not sure, which license to choose, this site may help: https://choosealicense.com

Thank you for the comment. Sorry for taking me this long to reply. I don't check this repo that often.
I added the MIT license.
If I understand correctly it means anyone can do whatever they want with this code and I am not liable and don't guarantee anything.
Hope this helps. Please let me know if you need anything else.

Thanks a lot!


Re-enable JUnit 4 and JUnit 3 unit tests

Looks like this was broken in #3233. With the addition of JUnit 5, the existing unit tests got ignored (note the sharp drop in overall coverage in the Codecov report). This PR should restore those old tests to full functionality.
Fixes #3270

I have no idea why the Mac test failed or why the codeclimate check is stuck. Is there a way to redo the checks? Should I push a dummy commit?

I have no idea why the Mac test failed or why the codeclimate check is stuck

The first seems to be a race condition happening from time to time. Only happens on Mac CI, not related to your commit. No clue about the second one. Nothing to worry about though, this doesn't prevent the merge. I will wait till the end of the week before merging to give @davidjgonzalez to have a look as well.


Script comparison question.

Have you, or are you aware of anyone who has data on which of these scripts perform best in terms of privacy, performance, etc. I would like to quickly determine which of these to use without making a bunch of VM's to run and then test each one using different criteria. If there is nothing online that fulfills this need I guess I can do this and possibly I'll make a video. Thanks if you have anything to provide.

I haven't tried all of them and can't recommend any one in particular. Different people understand different things when it comes to Windows Privacy. For example, a lot of these scripts will disable Windows Update. I personally would never disable Windows Update, but I also respect someone else's decision to do that.
So what I do is keep my own script (personalized based on my needs) that I built with inspiration from all the ones I have listed here.
Especially given the sensitive nature of the topic (privacy) I recommend you do the same (manually review each script's implementation and pick the pieces that jive with your personal view on privacy).


Center mode problem when there are few slides

I am using slick in center mode to create a carousel where the user can make a selection by moving their desired choice to the center spot.
It works as expected when I have many items:

However, with fewer slides than the number of items to display, it doesn't quite work as I would expect:

I would expect the user to be able to move an item to the center spot, even if there are less slides than the number set to display. In addition, in the three slide case, there seem to be two slides that have the center-slide class assigned to them, neither of them in the center spot, which doesn't make sense to me.
Is this working as intended or a bug(s)?

Could you tell me which lines you comment from  slick.js? I have the same problem

@jullermss, I am no longer using slick.js, it became unecessary for our needs. As code have changed the lines I mentionend are  no longer the same. I suggest you looking for the expressions I mentioned.

Has this issue been fixed?
I'm looking at the current code at https://github.com/kenwheeler/slick/blob/master/slick/slick.js but it looks like the issue is still here. I tested this version in a jsfiddle and I could still reproduce it. In this jsfiddle, clicking on the arrows does nothing when there are 3 panels, but works properly when there are 4 panels (you need to manually add a panel to test this).
I'm currently having the issue on a project I'm working on. We want center mode to work the same way no matter how many slides we have, be it 2 or 200. We're using slick.js version 1.3.15 and I can get around it by patching slick.js like @waltermacambira did: https://gist.github.com/blaiz/4d0b29820c46661ed333
If I understand the logic correctly, when the number of slides is less than or equal to the slidesToShow setting, slick.js basically doesn't use the regular center-mode but instead just shows all slides at once. It seems like it shouldn't be difficult to add a new setting to disable this behavior. I could fork the repo and give it a try. What do you think?

I'm having the same issue. Any updates?

I've the same issue. With a few item, slider don't center.

I just ran into this as well.  If there are too few slides to be a carousel, I need to center the items on screen.

I just came up with a quick solution to suit my needs.
In the Slick.prototype.initUI function, add the following:
    if( _.slideCount <= _.options.slidesToShow ) {
        _.$slider.addClass('slick-no-slide');
    }

This adds a .slick-no-slide class to the slick carousel if there are less slides than the slidesToShow option.  Then add the following CSS which will then override the width setting of .slick-track (it will be set to the width of the number of slides otherwise), switch the slides to display inline-block and not float, and center them.  This works for my scenario but you may need to alter the CSS to suit your needs.
.slick-no-slide .slick-track {
    width: 100% !important;
    text-align: center;
}

.slick-no-slide .slick-slide {
    float: none;
    display: inline-block;
}

I think the good thing with this solution is it's CSS based, so it should be easily tailored to fit whatever the end case is rather than having JavaScript make assumptions for you.
I'm happy to create a PR with this if you'd like, just let me know.

:+1: +1

Up :)

Have the same issue.

@kenwheeler Are there some news? You wrote, that you're thinking about making it an option. That would be really nice. Furthermore it would be nice to have the option for centerMode, if length > 1 -> show arrows to center the active item. Thanks for your work.

+1, we are really struggling with this, in many projects. We need a fix

I fixed (read: hacked) it by using the following code:
function Gallery__set_current() {
    slick = $('.Gallery__navigation ul').slick('getSlick');
    var slideCount = slick.slideCount;
    var slidesToShow = slick.options.slidesToShow;

    if(slideCount <= slidesToShow) {
        $('.Gallery__navigation ul .slick-slide').removeClass('slick-current')
            .eq(Gallery__current().data('slick-index')).addClass('slick-current');
    }
}

if the slideCount is less than or equal to the amount of slidesToShow, it will manually set the slick-current class.
Gallery__current().data('slick-index') <- This part of code gets the data-slick-index from the main slick slider.

Optimized from @rcrisp
function checkSlickNoSlide {
var elm = $('.slick-nav'),
getSlick = elm.slick('getSlick');
if(getSlick.slideCount <= getSlick.options.slidesToShow) {
elm.addClass('slick-no-slide');
}
else {
elm.removeClass('slick-no-slide');
}
}
checkSlickNoSlide is called on slick's event afterChange
CSS (Less):
.slick-no-slide {
.slick-slide {
float: none;
display: inline-block;
}
.slick-track {
width: 100% !important;
text-align: center;
.transform(~"inherit !important");
}
}

Up o/

+1

+1

@kenwheeler Any updates here?

almost 2 years and nobody fixed this ?

Is there a related stable PR somewhere?

i found this https://github.com/kenwheeler/slick/pull/1901

I'm not quite sure I have the same issue as you guys, but I found another alternative if this is indeed a part of someone's troubles.
My issue is that I am using slick on a wordpress site and the number of slides is dynamic according to however many images the user adds to a wordpress ACF field.  So a slider on one page may have 8 slides or may have 2 slides.
So to solve this I just query the amount of children of my slick slider:
var numSlides = $('my-slider').children().length

And then I create a conditional based upon how many slides I want to show so in my case I want there to always be 3 slides showing using center mode.  To make this work I write:
numSlides > 3 ? slides = 3 : slides--;

Then I can use this to init my slider:
$('my-slider).slick({
    slidesToShow: numSlides,
    cetnerMode: true
})

Note this is only if you want to have infinite sliding. In the case where there is 2 slides the above example will show a duplicate slide where the center is unique and the 2 slides to the left and right are the same.
It's a pretty specific use case but it might help someone.
Cheers

Here is my solution same of some before.
Add some if statements in  Slick.prototype.initUI = function () {

if (_.slideCount <= _.options.slidesToShow) {
            _.$slider.addClass('slick-no-slide');
        }
        else {
            _.$slider.removeClass('slick-no-slide');
        }

If you want to show more elements than you have slider will have no-slide class.
Then add your css file.

.slick-no-slide .slick-track {
    width: 100% !important ;
    text-align: center !important;
    transform: inherit !important;
}
.slick-no-slide .slick-slide {
    float: none !important;
    display: inline-block !important;
}

Similar kind of issue. It also appears to be adding "slick-center" to two slides at the same time. I want to highlight the central nav slide.
Fiddle here: https://jsfiddle.net/SparrowWoods/nu3psa1g/

@hadnazzar Thanks, here solved my problem.

doesn't seem that way.

@yenkute

Please try to add "margin: auto" like this picture.

Any news on this? Issue is still happening when using centerMode: true with the number slides <= than the attribute slidesToShow.
Meanwhile I manually remove the "slick-center" class on each element after the plugin is initialized but it feels a bit... dirty :/
Thanks, keep up the good job!

@fparent you mean to say that the removing the slick-center class gets the job done?

in my case yes because I'm using the class mainly for styling purpose

Adds a custom CSS:
.slick-track {
    margin-left: 0;
    margin-right: 0;
}

Here is my solution same of some before.
Add some if statements in Slick.prototype.initUI = function () {

if (_.slideCount <= _.options.slidesToShow) {
            _.$slider.addClass('slick-no-slide');
        }
        else {
            _.$slider.removeClass('slick-no-slide');
        }

If you want to show more elements than you have slider will have no-slide class.
Then add your css file.

.slick-no-slide .slick-track {
    width: 100% !important ;
    text-align: center !important;
    transform: inherit !important;
}
.slick-no-slide .slick-slide {
    float: none !important;
    display: inline-block !important;
}

Nice it's works

I just came up with a quick solution to suit my needs.
In the Slick.prototype.initUI function, add the following:
    if( _.slideCount < _.options.slidesToShow ) {
        _.$slider.addClass('slick-no-slide');
    }
    else {
        _.$slider.removeClass('slick-no-slide');
    }

This adds a .slick-no-slide class to the slick carousel if there are less slides than the slidesToShow option. It will remove the class if this changes (ie breakpoint settings change).
Then add the following CSS which will then override the width setting of .slick-track (it will be set to the width of the number of slides otherwise), switch the slides to display inline-block and not float, and center them. This works for my scenario but you may need to alter the CSS to suit your needs.
.slick-no-slide .slick-track {
    width: 100% !important;
    text-align: center;
}

.slick-no-slide .slick-slide {
    float: none;
    display: inline-block;
}

I think the good thing with this solution is it's CSS based, so it should be easily tailored to fit whatever the end case is rather than having JavaScript make assumptions for you.
I'm happy to create a PR with this if you'd like, just let me know.

Thanks  man :)


Bump dcos-metrics version

High Level Description

This change bumps the commit hash of the dcos-metrics module so that the STATSD_UDP_HOST and STATSD_UDP_PORT envvars are exposed to tasks running on the Mesos default executor (dcos/dcos-metrics#106).

Related Issues

None

Checklist for all PR's

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here: This merely changes a reference to a commit in another repo that has not seen any interface changes. Existing tests have coverage.
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Change log from the last version integrated (this should be a link to commits for easy verification and review): commit
[x] Test Results: results
[x] Code Coverage (if available): coverage

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and Review Process
What is the review process and when will my changes land?
All PRs require 2 approvals using github's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

@mesosphere-mergebot label ready for review

@mesosphere-mergebot bump-ee

@spahl @klueska @jgehrcke Reviews plz


differentiate between NamedType and NonNullType when merging field de…

…finitions. Fix tests to account for NonNullTypes

Thanks @lastmjs! This looks great. We'll review it some time this week.

@lastmjs I just came from your blog post and issue on Prisma and ran into this bug.  Pulled in your commit just to see if I could get it to work and it did!  Thanks!  And its pretty amazing when fixes come in just in time from the community.


Receiving forbidden error when running search function

I have created this function:
@objc fileprivate func search() {
    let test = Track.search(queries: [.queryString("hello")]) { [weak self] response in

        if case .failure(let error) = response.response {
            dump(error)
        } else {
            print("Success")
        }
    }
}

When I press a button that executes this function, the error is:
"-Soundcloud.SoundcloudError.forbidden"
What are the possible reasons for this error?

Could you tell me how you have added this library to your project? If via Cocoapods what exactly does your podfile look like? thanks!

Closing this for inactivity. Please reopen if necessary.


Add flag "ophan-model-default-access: public"

Add a generic flag in tspconfig.yaml that TCGC would read, to make all models as public, without the need for @access.
EventGrid is a no operation SDK, and today there is a clear maintenance cost that for every single event, we need to add
@access to it. It doesn't seem costly or risky to have a flag to explain the default behavior of orphan model (by default no access), something like:
ophan-model-default-access: public

## Effect of `default-access=private(default)|public` Flag.

| Flag State              | Model with Public Usage  | Model with Private Usage | Model without Usage |
|-------------------------|--------------------------|--------------------------|---------------------|
| `default-access=public` | Public                   | Private                  | Public              |
| `default-access=private`| Public                   | Public                   | Private             |

## Effect of `default-usage=Usage.none(default)|Usage.input|Usage.output` Flag.

| Flag State              | Model with Public Usage | Model with Private Usage | Model without Usage |
|-------------------------|-------------------------|--------------------------|---------------------|
| `default-usage=none`    | Used                    | Used                     | Not Used            |
| `default-usage=input`   | Used                    | Used                     | Used                |

closing in favor of #1299, #1300


Support additional where clause on Hive metadata extractor

Summary of Changes
Supporting additional filtering on Hive metadata extractor
Tests
Integration test performed.
Documentation
N/A
CheckList
Make sure you have checked all steps below to ensure a timely review.

[x] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[x] PR includes a summary of changes.
[x] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[x] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does

[x] PR passes make test
[x] I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message"

Codecov Report

Merging #131 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #131      +/-   ##
==========================================
+ Coverage   83.05%   83.06%   +0.01%
==========================================
  Files          56       56
  Lines        2785     2787       +2
  Branches      285      285
==========================================
+ Hits         2313     2315       +2
  Misses        381      381
  Partials       91       91

Impacted Files
Coverage Δ

...builder/extractor/hive_table_metadata_extractor.py
96.15% <100%> (+0.15%)
:arrow_up:

Continue to review full report at Codecov.

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


Error while running npm run serve

Getting following error while trying npm run serve
><EMAIL_ADDRESS>serve /path-to/bot/voice_tets/rasa-voice-interface
> vue-cli-service serve --open

sh: vue-cli-service: command not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR<EMAIL_ADDRESS>serve: `vue-cli-service serve --open`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>serve script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Thanks for the issue, @tabergma will get back to you about it soon!
You may find help in the docs and the forum, too 🤗

Thanks @sara-tagger.
Looking forward for response. Let me know if you need any details from me to reproduce the issue.
Note : This is happening on my Ubuntu machine. On mac it is working fine.