Hero button

Description
Create the component as shown in the video attached below.
Animation Preview

Screenshot/Video:

https://github.com/user-attachments/assets/df63ee03-0abf-4b10-b856-044c8a56f1dd

[!NOTE]
Please refer to the Animata contributing guidelines available here for rules on how to contribute to the project. Let us know in the comments if you’re working on this issue, and feel free to ask any questions!

Requirements

Create a new animated component that matches the provided design.
Add example usage of the component in the documentation or storybook.
Add credits for any resources, references, or assets used, as specified in the Additional Resources section.

 Guidelines & Best Practices

Write reusable and clean code following the project’s style guide.
The component should be fully customizable. The user should be able to modify props such as duration, easing, color, and size where applicable.
Follow the Contributing Guidelines before submitting your pull request.

[!IMPORTANT]
To ensure more contributors have the opportunity to participate, we kindly request that:

Each contributor submits only one pull request related to this issue.
If you're interested in working on this issue, please comment below. We will assign the issue on a first-come, first-served basis.

Additional Resources
Referenced from: https://antimetal.com/

[!Tip]
Join our Discord community if you need help or have any questions. We're here to help you get started and guide you through the process. Join now

Hey @sudhashrestha, I would like to work on this feature. Could you assign it me ?

Hi @sudhashrestha, I would love to work on this issue, please assign me this and allow me to contribute to it

Hi @sudhashrestha  ,pls assign this issue to me if it is not completed

I have added PR #373 for this Issue , Please Review it


Removed deprecated GeoManager from inspectdb/ogrinspect output.

refs ea27e26b0907e74ab8d6c46a9694775a310fdc67

Command.gis_tables looks like it could also be removed.


MAVLink FTP List command allocates 40K of memory

@DonLakeFlyer The MAVLink FTP list command lead to this interesting memory pattern:
Before:
nsh> free
             total       used       free    largest
Mem:        225392     181552      43840      38336

After:
nsh> free
             total       used       free    largest
Mem:        225392  537201024       5504       1520

I didn't see the smoking gun in the code yet.

facepalm I do see it. Sec.


Added fan_state and fan_mode to thermostat driver

This is going to break stuff that writes to regular old 'fan', but I don't think there's enough apps doing that to warrant an explicit migration strategy.


How to send custom message with stages and attach html report

@YOU54F  I have a question about, how I can create a custom message and if is possible add at what stage of my ci pipeline is running this and who triggered it (idk if with Gitlab this is possible). as for I have is
"slack-report": "npx cypress-slack-reporter --report-dir './cypress/report/output.json' --custom-url './final-report/output.html' --ci-provider custom --vcs-provider none --verbose true ".
what I tried to do with custom-url is to get that .html as a clickable attachment in the message to get redirected to that but my slack message is the following:

@YOU54F Encountering the same issue. The custom url merges to the screenshot directory for the Test Report attachment/button
npx cypress-slack-reporter --report-dir cypress/reports/mochareports --ci-provider custom --custom-url ~/cypress/reports/mochareports/report.html

Custom url is the basepath for somewhere you are sorting artefacts if not
on circleci iirc
On Thu, 22 Jul 2021 at 15:39, Luisa Gloria @.***> wrote:

@YOU54F https://github.com/YOU54F Encountering the same issue. The
custom url merges to the screenshot directory for the Test Report
attachment/button
npx cypress-slack-reporter --report-dir cypress/reports/mochareports
--ci-provider custom --custom-url
~/cypress/reports/mochareports/report.html
[image: image]
https://user-images.githubusercontent.com/63622377/126657739-3fb0b1d0-930c-4988-a925-e4beea79a0d4.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/YOU54F/cypress-slack-reporter/issues/1034#issuecomment-884966202,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEYCJ4KCPOUK7WXUYO2YIM3TZAUSZANCNFSM46KVCKBQ
.

See here for info
https://github.com/YOU54F/cypress-slack-reporter/issues/497#issuecomment-630514390
It would probably be worth adding this into the readme. Would be happy to accept contributions if this works for you 🤘🏽

@luisaangelicag @HernanMinted ☝🏾 :)

Hi @YOU54F
checked the issue you linked above though it wasn't able to address my issue. i'm using the file location since i'm running the scripts locally too. will it be possible to use the root directory? from what i'm seeing, the custom-url appends to the screenshots directory

FYI,
I am going to support sending custom blocks in the new rollout, details to come soon, but it will allow users to send any number of structured (and typed) objects to the message builder, so it should be infinitely customisable

@luisaangelicag have you been able to fix this issue? may you share what was your path to make it work?

Just to clarify you cannot provide the --custom-url property a relative path from your machine.

If needs to be a valid web URL.
A link will need to appear like this  in slack to render
<http://sometesturl.com/pnggrad16rgb.png|Screenshot:- pnggrad16rgb.png>

Custom blocks coming soon, you'll be able to add as many of these as you want 👌🏾

BTW where are you expecting to serve your URL's from? if you provide the uri root for where your report is, you should be fine, with the current version

@YOU54F  Ohh I see, so my custom-url is not doing anything haha 🤣 , although my main concern here is that in my case, I can only see a certain amount of only Test passed (if all passed it shows me 141 even tho there are 200+ test that passed) and if it fails then it throws me Test passed: 0, what I'm seeing at least for Luisa side is that she have been able to split how many test passed, failed  and the total of tests that run, basically at first this is what I need right now, screenshots and video or html report would be a nice to have.

I'd need to see your report json file to understand why the numbers are incorrect.
or take your json and pipe it into jq
cat cypress/reports/html/index.json | jq .stats

{
  "suites": 2,
  "tests": 20,
  "passes": 20,
  "pending": 0,
  "failures": 0,
  "start": "2022-04-28T22:38:51.534Z",
  "end": "2022-04-28T22:39:28.478Z",
  "duration": 24373,
  "testsRegistered": 20,
  "passPercent": 100,
  "pendingPercent": 0,
  "other": 0,
  "hasOther": false,
  "skipped": 0,
  "hasSkipped": false
}

They are extracted here
https://github.com/YOU54F/cypress-plugins/blob/c4b4a29d7a40fc9618b12f569184be64b43fb80f/src/slack/slack-alert.ts#L536-L550
and built into the message here
https://github.com/YOU54F/cypress-plugins/blob/c4b4a29d7a40fc9618b12f569184be64b43fb80f/src/slack/slack-alert.ts#L381-L444
Also --report-dir './cypress/report/output.json' this should be a directory, which is why the flag is called --report-dir, drop the /output.json

Is there a way to add also the skipped test into the report? or are taken as Error for the webhook?
the --custom-url for screenshots, since I'm using gitlab for CI/CD you can access the artifacts but then you have to download them to see them, in this case I would need to put them on a server in order to actually see the link correctly to it right?

@YOU54F not sure if this needs a separate issue ticket, but I've encountered issues viewing the generated HTML report. It's just blank upon clicking the Test Report, but inspecting the page shows that the test report details are there

The OP issue should hopefully be resolved by a new flag --useOnlyCustomUrl along with your custom-url http://sometesturl.com/
https://github.com/YOU54F/cypress-plugins/issues/1216


Return only Tags + DefaultValue + Declarative pipeline

Adds support to return only Tags
Adds support to define defaultValue
Support image-tag-parameter-plugin in the declarative pipeline

return only tag is a good idea
Maybe the pugins should set a second variable ending with _TAG bye default
When using imageTag name: 'DOCKER_IMAGE'
DOCKER_IMAGE and DOCKER_IMAGE_TAG

return only tag is a good idea
Maybe the pugins should set a second variable ending with _TAG bye default
When using imageTag name: 'DOCKER_IMAGE'
DOCKER_IMAGE and DOCKER_IMAGE_TAG

Mind me asking if this even possible?
I mean I have not seen a parameter plugin that exports 2 parameters from one?
Otherwise love the idea! (I mostly need to split the result of the current version into image name and tag for my use-case)

return only tag is a good idea
Maybe the pugins should set a second variable ending with _TAG bye default
When using imageTag name: 'DOCKER_IMAGE'
DOCKER_IMAGE and DOCKER_IMAGE_TAG

This should be a hidden or visible variable?
DOCKER_IMAGE = image + ":"+ tag? or only image name? Should include repository name?
DOCKER_IMAGE_TAG = only tag

I would say a hidden variable.
DOCKER_IMAGE = image + ":"+ tag
DOCKER_IMAGE_TAG = only tag

Okay, I had some time and played around a bit with this idea of additional environment exposure.
To my surprise, it was quite a lot simpler than I imagined this. See my tagSplit branch for a POC.
I could open a PR with this or if @Reuuke wants to take this and merge it into their PR would be fine with me too.
Just let me know what to do :wink:

What did I do in that branch:

added a customer ParameterValue type that exposes 2 additional environment variables (in total 3)

parameterName the image+tag (e.g.: openjdk:11-slim)
parameterName_IMAGE the image name only (e.g.: openjdk)
parameterName_TAG the tag of the image only (e.g.: 11-slim)

add a copy of the StringParameterValue value.jelly so that this new ParameterValue can be rendered in the parameter view of a build job
some minor tweaks (add .editorconfig and move sort location)

Oh and yes I am aware and sure that this could have been handled much more elegantly than my POC.
So if you have suggestions I am all ear or if you want to use it maybe give it another sanity/style check.

Okay, as you can see by the mention of this PR in my latest commit, I have incorporated some of the code of this PR into my POC tagSplit branch.
I did this to get the rebuild-plugin to behave and select the previously selected value.
If @Reuuke is okay with it and @maduma is okay with my "solution" to export additional envVars to export the image tag on itself, then I would open an alternative PR to this PR with what is currently in my tagSplit branch.

tagSplit

Yes, I am completely satisfied with your solution.

tagSplit

Yes, I am completely satisfied with your solution.

I was more asking for your permission to use the parts of your could, but I am happy you like my solution :grin:


Neuralynx annotations from 0.7.1 to 0.8 dev

Guys, please, I can't figure it out myself, the annotations are different
In version 0.7.1 with any number of channels, everything is correct:

In version 0.8 dev (Master HEAD by now) with two channels:

In version 0.8 dev (Master HEAD by now) with one channels:

???

OK, false alarm, the required field has now been moved from "annotations" to "array_annotations"

Excatly all annoations that array like with the one dimenssion matching the datat itself are moved to array_annotation. With this when slicing array_annotation are also sliced.


perf: Add pagination to components where it might be needed

Some api endpoints use pagination, which i ignore most of the time.
To ensure proper scaling, I want to implement proper pagination sometime in the future.

requests are paginated currently on the "list passages" and "list all entities" data tables only
the "case study" screen uses a limit of 200 when fetching associated passages, which is not great performance-wise unfortunately:time curl "https://mmp.acdh-dev.oeaw.ac.at/api/stelle/?use_case=5&limit=200"
real    0m7,559s

also: https://github.com/acdh-oeaw/mmp-frontend/blob/6bf797521287f904c4b9befc5060a3cea2490374/src/components/KeywordDetail.vue#L38

maybe we need an additional endpoint to query passages by text by author

won't fix


Remove year from breadcrumbs, Rising Graduate and Emerging Scholar landing pages

 Remove year from Rising Graduate Scholars and Emerging Scholars landing pages.


LLM Observability: Add optional Langfuse support

Hi! We use the app extensively, but it lacks LLM observability functionality. There should be an easy way to gather user interactions within the AOAI app. Langfuse is an open-source LLM observability platform that supports prompt logging. It offers native integration with OpenAI library which can be achieved by adding just a few lines of code to the underlying Python script. I am wondering whether it would be feasible to add optional Langfuse support into the app, as it seems that only minimal changes are required (a few variables for the Azure Web App and few lines in the AOAI app code). If this is ok, I can attempt to create a pull request for it.

Very interesting, I hadn't seen that before, and there's a lot of interest in observability. I think we'd want to get Langfuse deployed on Azure to make sure it was viable for devs to host it on our infrastructure. It looks like that'd be fairly straightforward using Azure Container Apps and the Postgres ACA Add-on, for example. Are you hosting Langfuse on Azure or using their cloud-based version?

@pamelafox, we are hosting Langfuse on Azure as Azure Web App and using Azure PostgreSQL - Flexible Server. Azure Container Apps would be another option. It was very simple to deploy, here is the guide.

Have a look at https://github.com/Azure-Samples/azure-search-openai-demo/issues/1318 as well, we're considering adding this to improve the Application Insights traces for OpenAI

Langfuse maintainer here. There are many teams running Langfuse on Azure in prod, mostly on (1) Azure Container Instances + Azure PostgreSQL or (2) everything in Kubernetes.
Let me know if I can help with anything here @aiakubovich @pamelafox

From my experiment, the changes to this repo are pretty minimal - just setting the env variables and changing the import in app.py - and we can just document those in docs/.

Let me know if there's something I can help with.

What I'm more interested in is making it super easy to deploy langfuse to Azure using the Azure Developer CLI (azd up). I've started that at https://github.com/pamelafox/langfuse-azure but have some TODOs. One thing that would help is if we could specify the database password separately from the URL, so that we can store those with secret-specific mechanisms. I could also store the entire database URI as a secret, but it's nice when you can view the rest in plaintext.

That's awesome, I'd love to reference https://github.com/pamelafox/langfuse-azure in our self-hosting docs to make it easier for others to get started on Azure (once you are done with it) – if that's ok for you.

Instead of DATABASE_URL, you can also use DATABASE_HOST, DATABASE_USERNAME, DATABASE_PASSWORD and DATABASE_NAME.
Self hosting docs

This was added to langfuse specifically to support external secret management to e.g. rotate secrets easily on Kubernetes. Does this solve for your use case on Azure to specify DATABASE_PASSWORD independently?

Thank you! I've got the basic deployment working now. Next step is to add in authentication via AAD, as Azure customers will prefer that, I think.
@aiakubovich Did you all go with AAD for your deployment? Just curious.

@pamelafox, yes, we added few env variables from Azure Active Directory to the Azure Web App config page based on Langfuse self-host guide and now we able to see Azure button on Langfuse UI and it works well for authentication via AD.
Also question regarding this repo - any plans in changing the import in app.py to support Langfuse by default?

Here are some screenshots from the langfuse on ACA deployment:

That's from this repo:
https://github.com/pamelafox/langfuse-azure
Still WIP as you can see from the TODOs, but basic deployment works.
Question for @marcklingen: Is it expected that the traces show null for input/output/metadata?
@aiakubovich We wouldn't make that change across the board, as we want all add-ons like this to be optional (even Azure monitor is optional, though we now default to true as its negligible costs). We could potentially add it as an option based off an env variable, which would look something like this code inside setup_clients:
if (os.getenv("LANGFUSE_HOST")):
   from langfuse.openai import AsyncOpenAI, AsyncAzureOpenAI

For now I'd like to get langfuse-azure template done, document that, and see what feedback we get.

@marcklingen Also wondering why "Time to first token" would be empty?

FYI, I showed Langfuse on Azure in a livestream today-
https://youtube.com/live/Q169GFD_9PI?feature=share
The repo is here:
https://github.com/Azure-Samples/langfuse-on-azure
I'll add documentation here about that repo shortly.

@pamelafox Just checked out the livestream, thanks for featuring and integrating https://github.com/langfuse!

Question for @marcklingen: Is it expected that the traces show null for input/output/metadata?

Yes, the openai monkeypatch integration is the easiest to get started with to log single generations (llm calls, embeddings) to Langfuse. Most users expand to complete traces with more spans (eg for retrieval) or additional events (eg other non-llm api calls). See a full guide here: https://langfuse.com/docs/tracing

Also wondering why "Time to first token" would be empty?

Good one, just created an issue to add this to our openai integration when streaming: https://github.com/langfuse/langfuse/issues/1330

By the way, just added a link to Azure-Samples/langfuse-on-azure to our self-hosting guide to make deploying to Azure easier for others as well. thanks again!
https://langfuse.com/docs/deployment/self-host#azure
Change: https://github.com/langfuse/langfuse-docs/commit/d81a69e8d647f4fef0f607eba0c53b0756f783a9

Hi @marcklingen and @pamelafox - This looks like an older thread, but I was wondering if anyone has been able to get the new Langfuse Observe decorators working with the llm 'generation' in this backend app of this repo?
I'm new to decorators and the methods used to call the Azure OpenAI chat and embeddings in this enterprise chat app. I'm struggling to get the observe decorator to show token usage in this backend app.
Thanks for all that you both do!

Hi @marcklingen
I ended up finding a very simple solution after reading through the Langfuse documentation: https://langfuse.com/docs/integrations/openai/python/structured-outputs
All I had to do is change this line:
https://github.com/Azure-Samples/azure-search-openai-demo/blob/009d5e13ba5f9f14bcca684d7a47e1d28fd9023e/app/backend/app.py#L31
From:
from openai import AsyncAzureOpenAI, AsyncOpenAI
To:
from langfuse.openai import AsyncAzureOpenAI, AsyncOpenAI
Now I am seeing the generations in the langfuse dashboard.
Thanks again for your quick response.


Task21

Find the temperature of few cities and print the results into Excel.

SourceCode/2024/May 2024/Bhavya/Task 29/project.json
Main.xaml
Log Message not used in workflow Main. Using Log Message activities is important both during development and after release. They help understanding the flow path which is very useful for maintenance and, when an error occurs, to easily identify the source and the cause.
Sequence
Names of activities should give a clear indication of how they are being used. Default names are usually too generic. Please avoid duplicate names. Code contains 2 instances of "Sequence" with different display names. Consider renaming them to something more descriptive.
Kill Process
Names of activities should give a clear indication of how they are being used. Default names are usually too generic. Please avoid duplicate names. Code contains 2 instances of "Kill Process" with different display names. Consider renaming them to something more descriptive.
Throw
Names of activities should give a clear indication of how they are being used. Default names are usually too generic. Please avoid duplicate names. Code contains 2 instances of "Throw" with different display names. Consider renaming them to something more descriptive.
Again Read the Input file
Names of activities should give a clear indication of how they are being used. Default names are usually too generic. Please avoid duplicate names. Code contains 2 instances of "Again Read the Input file" with different display names. Consider renaming them to something more descriptive.
Try Catch, Throw, Kill Process, and Again Read the Input file
Check if it could be easier to understand what the activity does by adding a more descriptive title. Most activities have default names that don't provide much context. Try using more descriptive titles to help with maintenance and debugging.
Score: 5

SourceCode/2024/May 2024/Bhavya/Task 30/project.json
Main.xaml
Log Message not used in workflow Main.
Using Log Message activities is important both during development and after release. They help understanding the flow path which is very useful for maintenance and, when an error occurs, to easily identify the source and the cause. 4/5
Read Range Workbook.xaml
Activity Read Range Workbook has a default name.
Check if it could be easier to understand what the activity does by adding a more descriptive title. 3/5
ForEach Row in Data Table.xaml
Activity For Each Row in Data Table has a default name.
Check if it could be easier to understand what the activity does by adding a more descriptive title. 3/5
Throw.xaml
Activity Throw has a default name.
Check if it could be easier to understand what the activity does by adding a more descriptive title. 3/5
If.xaml
Activity If has a default name.
Check if it could be easier to understand what the activity does by adding a more descriptive title. 3/5
Message Box.xaml
Activity Message Box has a default name.
Check if it could be easier to understand what the activity does by adding a more descriptive title. 3/5
Score: 4/15

SourceCode/2024/May 2024/Bhavya/Task 31/project.json
Main.xaml
Log Message not used in workflow Main.
Using Log Message activities is important both during development and after release. They help understanding the flow path which is very useful for maintenance and, when an error occurs, to easily identify the source and the cause.
Score: 5/5
No issues found

IMAP Mail Messages
Activity Get IMAP Mail Messages has a default name.
Check if it could be easier to understand what the activity does by adding a more descriptive title.
Score: 4/5
Please consider renaming this activity with a more descriptive name.

Password
Activity Get Password has a default name.
Check if it could be easier to understand what the activity does by adding a more descriptive title.
Score: 4/5
Please consider renaming this activity with a more descriptive name.

Message Box
Activity Message Box has a default name.
Check if it could be easier to understand what the activity does by adding a more descriptive title.
Score: 4/5
Please consider renaming this activity with a more descriptive name.

For Each
Activity For Each has a default name.
Check if it could be easier to understand what the activity does by adding a more descriptive title.
Score: 4/5
Please consider renaming this activity with a more descriptive name.
Total Score: 18/20
Please address the above suggestions and update your PR.

SourceCode/2024/May 2024/Bhavya/Task 32/project.json
Main.xaml

The Log Message activity is not used in the workflow. It's essential for understanding the flow path and identifying errors.
The Assign display name is defined multiple times (3). This should be avoided, as it can make it harder to understand what each activity does.

Score: 4/5
Note: Please review your naming conventions and consider adding more descriptive titles for activities.

SourceCode/2024/May 2024/Bhavya/Task 33/project.json
Main.xaml
Log messages are important for understanding the workflow flow path during development and after release. They help with maintenance and error identification.
No issues found in this file.
Score: 5/5

SourceCode/2024/May 2024/Bhavya/Task 34/project.json
ActivityFlowchart.xaml:

Rename activities to provide clear indication of how they are being used.
Avoid duplicate names for better readability.

Assign.xaml:

Same as above, rename activities to provide clear indication of how they are being used.
Avoid duplicate names for better readability.

Variable naming issues:

The variables add_result and sub_result do not follow the set pattern. Make sure all variables follow the naming convention.

Flowchart usage:

Flowchart should only be used in top layer for maintainability and readability reasons.
In this file, the flowchart is being used in a secondary layer, consider moving it to the top level.

Dependency packages:

Remove unused packages UiPath.Mail.Activities, UiPath.Testing.Activities, and UiPath.UIAutomation.Activities to improve process execution time.

Log Message usage:

The Log Message activity is not being used in this workflow. It's important for both development and after release, as it helps understanding the flow path which is very useful for maintenance and debugging.

Activity naming issues:

Activities Assign, Get Transaction Item, Log Message, and Set Transaction Status have default names. Consider renaming them to provide clear indication of how they are being used.

Potential infinite loop:

A potential infinite loop was detected in the Flowchart starting with activity Get Transaction Item. Make sure to add a termination condition or document your code if this is intentional.

Score: 5/5
Note: The issues listed above are related to naming conventions, flowchart usage, and dependency packages. Some issues require renaming activities, while others need removal of unused dependencies.

SourceCode/2024/May 2024/Bhavya/Task 29/project.json
Main.xaml
Log Message not used in workflow Main.
Using Log Message activities is important both during development and after release. They help understanding the flow path which is very useful for maintenance and, when an error occurs, to easily identify the source and the cause.
Sequence display name
Names of activities should give a clear indication of how they are being used. Default names are usually too generic. Please avoid duplicate names.
 Default names are usually too generic. Please avoid duplicate names.
Code contains 2: Kill Process, Throw
Throw display name
Names of activities should give a clear indication of how they are being used. Default names are usually too generic. Please avoid duplicate names.
Code contains 2: Again Read the Input file., Kill Process, Throw
Activity names

Activity Throw has a default name.: Check if it could be easier to understand what the activity does by adding a more descriptive title.
Activity Kill Process has a default name.: Check if it could be easier to understand what the activity does by adding a more descriptive title.
Activity Try Catch has a default name.: Check if it could be easier to understand what the activity does by adding a more descriptive title.

Score: 5/5

SourceCode/2024/May 2024/Bhavya/Task 30/project.json
Main.xaml
Log messages are not used in workflow Main. This makes it harder to debug and understand the flow path of the process.
Please add log messages throughout the workflow to make it easier to maintain and identify errors.
Read Range Workbook
The default name for this activity is unclear. Please consider adding a more descriptive title so that others can quickly understand what this activity does.
For Each Row in Data Table
The default name for this activity is unclear. Please consider adding a more descriptive title so that others can quickly understand what this activity does.
If
The default name for this activity is unclear. Please consider adding a more descriptive title so that others can quickly understand what this activity does.
Message Box
The default name for this activity is unclear. Please consider adding a more descriptive title so that others can quickly understand what this activity does.
Throw
The default name for this activity is unclear. Please consider adding a more descriptive title so that others can quickly understand what this activity does.
Score: 5/5

SourceCode/2024/May 2024/Bhavya/Task 31/project.json
Main.xaml
Log Message not used in workflow Main.
: Using Log Message activities is important both during development and after release. They help understanding the flow path which is very useful for maintenance and, when an error occurs, to easily identify the source and the cause.
Score: 5
Get Password.xaml
Activity Get Password has a default name.
: Check if it could be easier to understand what the activity does by adding a more descriptive title.
Score: 4
ForEach.xaml
Activity For Each has a default name.
: Check if it could be easier to understand what the activity does by adding a more descriptive title.
Score: 4
IMAP Mail Messages.xaml
Activity Get IMAP Mail Messages has a default name.
: Check if it could be easier to understand what the activity does by adding a more descriptive title.
Score: 4
Total Score: 17/20

SourceCode/2024/May 2024/Bhavya/Task 32/project.json
Main.xaml

Log Message not used in workflow Main. It's important to use log messages during development and after release to help understand the flow path, which is useful for maintenance and error identification.
Assign display name is defined many times. We should avoid duplicate names and make sure they give a clear indication of how they're being used.

Score: 5/5
Please add descriptive titles to activities and use log messages to improve workflow understanding.

SourceCode/2024/May 2024/Bhavya/Task 33/project.json
Main.xaml
The workflow Main contains a Log Message activity that is not used in the process. This can make it difficult to understand the flow path and identify any issues that might occur during execution.
Recommendation: Add log messages throughout the workflow to provide visibility into the process execution. This will help with maintenance, debugging, and troubleshooting.
Score: 4/5
Dependency Packages
The following dependency packages are not used in the project:

UiPath.Excel.Activities
UiPath.System.Activities
UiPath.Testing.Activities

Recommendation: Remove unused packages to improve process execution time and reduce complexity. This will also help avoid any potential issues with unnecessary dependencies.
Score: 4/5
Send SMTP Mail Message and Get Password Activities
The activities Send SMTP Mail Message and Get Password have default names. It would be helpful if these names were more descriptive to provide clarity on what the activities do.
Recommendation: Check if it could be easier to understand what the activity does by adding a more descriptive title.
Score: 4/5
Total Score: 12/15

SourceCode/2024/May 2024/Bhavya/Task 34/project.json
File: Performer.xaml

The Log Message display name is defined multiple times. It's recommended to use a consistent naming convention throughout the workflow.
The names of activities should provide clear indications of how they are being used. Default names are usually too generic and may cause confusion.

File: Dispatcher.xaml

The Log Message activity is not being used in the workflow. This activity plays an important role in understanding the flow path during development and after release, as it helps identify the source and cause of errors.
Consider removing unused activities to improve process execution time.

Score: 4/5
Please note that I have only reviewed the files mentioned (Performer.xaml and Dispatcher.xaml) and not all files in your PR.

SourceCode/2024/May 2024/Bhavya/Task 29/project.json
@github-pr-comment
Main.xaml:

Log Message not used in workflow Main.

Consider removing unused activities to improve code clarity and efficiency.

Activity Try Catch:

Default name detected, suggest renaming for better understanding.

Naming conventions are crucial for maintainability and debugging purposes.

Activity Throw:

Default name detected, suggest renaming for better understanding.

Consistent naming helps in identifying the purpose of each activity.

Sequence:

Display name defined multiple times (2), please avoid duplicates.

Clear names help in understanding the workflow's logic.

Kill Process:

Display name defined multiple times (2), please avoid duplicates.

Unique names facilitate debugging and maintenance tasks.

Again Read the Input file:

Display name defined multiple times (2), please avoid duplicates.

Consistent naming promotes a clear understanding of the process flow.

Score: 4/5

SourceCode/2024/May 2024/Bhavya/Task 30/project.json
Main.xaml
Log Message not used in workflow Main.
It's important to use Log Message activities during development and after release. They help understanding the flow path, which is very useful for maintenance and when an error occurs.
Activity If
The activity name is default. Could it be easier to understand what this activity does by giving it a more descriptive title?
Activity Throw
The activity name is default. Could it be easier to understand what this activity does by giving it a more descriptive title?
Score: 4/5
Please note that these are just suggestions and not code suggestions.

SourceCode/2024/May 2024/Bhavya/Task 31/project.json
Main.xaml
Log Message not used in workflow Main.

Please consider using Log Message activities throughout your workflow to help with understanding the flow path during development and after release. This will make maintenance and error tracking easier.

Activities:

Activity Get IMAP Mail Messages has a default name.: Could you rename this activity to something more descriptive?
Activity For Each has a default name.: Would a more descriptive title for this activity be helpful?
Activity Get Password has a default name.: Is it clear what this activity does? A more descriptive name might help.
Activity Message Box has a default name.: Is there a better name that would make this activity's purpose clearer?

Score: 5/5

SourceCode/2024/May 2024/Bhavya/Task 32/project.json
Main.xaml

Log Message not used in workflow Main.

Recommendation: Use Log Message activities to provide meaningful information about the flow path and help with debugging and maintenance.

Assign display name is defined many times (3). Current allowed threshold is 1.

Recommendation: Rename duplicate activity names to make them more descriptive and unique.

Overall Score: 4/5
Please note that I did not find any issues related to unused packages or missing Automation Hub URL. The suggestions provided are mainly focused on improving the readability and maintainability of the code by using meaningful log messages and renaming activities with default names.

SourceCode/2024/May 2024/Bhavya/Task 33/project.json
Main.xaml
Log messages are crucial for understanding the workflow's flow path during development and debugging. Adding more log messages would help identify the source and cause of errors.
Score: 4/5
No suggestions given for this file.
Total Score: 4/5

SourceCode/2024/May 2024/Bhavya/Task 34/project.json
Performer.xaml

The log message display name is defined multiple times, which exceeds the allowed threshold of 1. Please provide unique and clear names for each log message.
The activity flowchart has a default name, making it difficult to understand its purpose without additional context. Consider adding a more descriptive title.
Activities such as Get Transaction Item, Log Message, and Assign have default names, which can make the code harder to read and maintain. Provide more descriptive titles for these activities.

Readable Code

The code could be improved by providing clear and concise names for activities, variables, and flowcharts. This will make it easier to understand the purpose of each component.
The use of default names should be avoided in favor of more descriptive titles that provide context about what the activity is doing.

Naming Convention

Two variables (add_result and sub_result) do not follow the set naming pattern. Ensure all variables adhere to this convention.

Flowchart

A potential infinite loop has been detected, which could cause issues during execution. Review the flowchart and ensure that there is a termination condition or a clear purpose for the loop.
The flowchart is being used in a secondary layer, which can make the code harder to read and maintain. Consider moving it to the top layer.

Unused Dependencies

Three dependencies (UiPath.Mail.Activities, UiPath.Testing.Activities, and UiPath.UIAutomation.Activities) are not being used in the code. Remove unused packages to improve process execution time.

Dispatcher.xaml

The log message activity is not being used in this workflow. Review why it was added and consider removing or replacing it if it's not necessary.
Activities such as Read Range Workbook and Bulk Add Queue Items have default names, which can make the code harder to read and maintain. Provide more descriptive titles for these activities.

Score: 4/5

SourceCode/2024/May 2024/Bhavya/Task 29/project.json
Main.xaml
The Log Message activity is not used in the workflow. Using log messages during development and after release is important for understanding the flow path, which helps with maintenance and identifying errors.
Try Catch Activity, Throw Activity, Kill Process Activity, Again Read the Input file Activity
These activities have default names. Consider giving them more descriptive titles to help understand what each activity does.
Sequence Display Name
The Sequence display name is defined multiple times. You should avoid duplicate names and use a clear indication of how they are being used. Default names are usually too generic.
Score: 5/5

SourceCode/2024/May 2024/Bhavya/Task 30/project.json
Main.xaml
Log Message not used in workflow Main.
Using Log Message activities is important both during development and after release. They help understanding the flow path which is very useful for maintenance and, when an error occurs, to easily identify the source and the cause.
Score: 5/5
Activity If
Activity has a default name.
Check if it could be easier to understand what the activity does by adding a more descriptive title.
Activity Throw
Activity has a default name.
Check if it could be easier to understand what the activity does by adding a more descriptive title.
Score: 5/5
Total Score: 10/10

SourceCode/2024/May 2024/Bhavya/Task 31/project.json
Comments for Pull Request
Activities Names

Get IMAP Mail Messages: Please consider renaming this activity to something more descriptive, like "Retrieve Email Inbox Contents" or "Fetch IMAP Emails". This will make it easier for others (and yourself) to understand what the activity does.
Get Password: Similarly, please rename this activity to something like "Obtain Authentication Credentials" or "Fetch Login Password". This will provide clarity on its purpose.
For Each: Rename this activity to something more descriptive, such as "Iterate Through Collection" or "Loop Through Items". This will help others understand the workflow's intent.

Log Messages

The log message activities are not being used in the workflow. Please consider adding log messages at key points to aid in debugging and understanding the flow path. This is important for both development and maintenance purposes.

NoFile

There is no file specified. Please check the project settings and ensure that an Automation Hub URL is defined. This is a required setting for your organization's project.

Score: 5/5
Please address these suggestions to improve the code review.

SourceCode/2024/May 2024/Bhavya/Task 32/project.json
Main.xaml

Log Message not used in workflow Main.
Please add log messages to help understanding the flow path and identify errors when they occur.

 Please rename these activities with more descriptive titles that indicate what each activity does.
Avoid duplicate names by giving each activity a unique and clear name.

Score: 4/5
Note: I did not provide code as suggestions for review, but instead focused on providing simple and actionable feedback to the developer.

SourceCode/2024/May 2024/Bhavya/Task 33/project.json
Here's my review:
Main.xaml

Log Message not used in workflow Main.

This is an important finding! It means that your log messages are not being used, which makes debugging and maintenance harder. Please consider using these messages to provide insight into the flow of your process. This will help you understand what's happening at runtime and make it easier to identify issues when they arise.
Main.xaml

Activity Send SMTP Mail Message has a default name.
Activity Get Password has a default name.

These activities have default names that don't convey much information about what they do. It would be helpful to rename them to something more descriptive, like "Send Email Notification" or "Retrieve User Credentials". This will make your workflow easier to understand and maintain.
Score: 4/5
Note: I did not provide individual suggestions for code review, as per your request.

SourceCode/2024/May 2024/Bhavya/Task 34/project.json
ActivityFlowchart.xaml

The Activity Flowchart has a default name. Consider adding a more descriptive title to make it clearer what this activity does.

Assign.xaml

Assign display name is defined many times. Limit the number of definitions to avoid confusion.
Some activities have generic names that don't indicate their purpose. Consider renaming them for better understanding.

GetTransactionItem.xaml

The Activity Get Transaction Item has a default name. Add a more descriptive title to clarify its function.

LogMessage.xaml

Log Message display name is defined many times. Limit the number of definitions to avoid confusion.
Some activities have generic names that don't indicate their purpose. Consider renaming them for better understanding.

Variable.xaml

The variables add_result and sub_result do not follow the set naming pattern. Ensure all variable names adhere to the convention.

Flowchart.xaml

A potential infinite loop is detected in the Flowchart. Add a termination condition or document your code to prevent this issue.
The Flowchart should only be used in the top layer for maintainability and readability reasons.

Dispatcher.xaml

Log Message not used in workflow Dispatcher. This activity helps understanding the flow path, which is essential during development and after release.

ReadRangeWorkbook.xaml

The Activity Read Range Workbook has a default name. Add a more descriptive title to clarify its function.

BulkAddQueueItems.xaml

The Activity Bulk Add Queue Items has a default name. Add a more descriptive title to clarify its function.

Score: 5/5
Please make the necessary changes and provide an updated pull request for review.

@Bhavyajetty2
Task -21
Code verified.
Task -29
Code verified.
Task -30
Code verified.
Task -31
Code verified.


add a callNode2nix similar to callCabal2nix

Issue description
I am trying to package https://github.com/iamcco/markdown-preview.nvim (tried another preview plugin before but it would show an empty preview ;s ). This one relies on node packages so I've dived into the node ecosystem (also because I would be interested in fetching node packages for coc.nvim ).
My understanding (since the doc is so short: https://nixos.org/nixpkgs/manual/#node.js-packages) is that one needs to write a generate.sh and pkgs.json  (taking pkgs/development/web/remarkjs/ as an example) and calling generate.sh will generate nodepkgs.nix node-env.nix.
My question is then:

can I just skip the previous steps and do node.withPackages(p: [] ) ?
would it be possible to add a callNode2nix as callCabal2nix ? this would allow to alleviate some workload and generate the code from the source pacakges.json instead of providing ours ?

@teto No specific reason. It's just I'm not completely familiar with callCabal2nix and what it offers.
But I assume your use case is to add an NPM package as a dependency to another project?

callCabal2nix is just a convenience, what I am really interested in is to be able to generate a node environments based on vim plugin requirements. All the popular coc-* and all the markdown viewers involve node packages. Due to the difficulty of creating an environment from them, we are limited to build only tagged releases as opposed to from source, and even then I still have problems such as https://github.com/iamcco/markdown-preview.nvim/issues/168.
There is also https://github.com/NixOS/nixpkgs/pull/84225

No related to the issue but to markdown-preview, did you manage to package it @teto ?
I actually don't have my vim config on nix, and I found that I can't use this plugin because it requires running the plugin binary. Completely off topic, but can NixOS run binaries without relying on patchelf?

@Pablo1107 I kinda avoid any node related packages since I found them hard to use/package on nixos. I've packaged https://github.com/NixOS/nixpkgs/pull/84213 instead.

@teto any ideas on how I could make this work? https://discourse.nixos.org/t/how-to-override-coc-vim-plugin/7991
It is somewhat similar and I'm kind of running in circles at the moment... :|

I found this implementation of callNode2Nix searching on github, but there's no LICENSE on that project. it's basically it calls node2nix on the buildPhase and copies to $out on installPhase

I suppose buildNpmPackage fills the role. closing.


RuntimeError: checkpoint url or path is invalid

Hi. Thank you for your wonderful project.
However I dhave not success to run it:
C:\Users\mikazmaj\SeeSR\pipelines\pipeline_seesr.py:42: FutureWarning: Importing `DiffusionPipeline` or `ImagePipelineOutput` from diffusers.pipeline_utils is deprecated. Please import from diffusers.pipelines.pipeline_utils instead.
  from diffusers.pipeline_utils import DiffusionPipeline
/encoder/layer/0/crossattention/self/query is tied
/encoder/layer/0/crossattention/self/key is tied
/encoder/layer/0/crossattention/self/value is tied
/encoder/layer/0/crossattention/output/dense is tied
/encoder/layer/0/crossattention/output/LayerNorm is tied
/encoder/layer/0/intermediate/dense is tied
/encoder/layer/0/output/dense is tied
/encoder/layer/0/output/LayerNorm is tied
/encoder/layer/1/crossattention/self/query is tied
/encoder/layer/1/crossattention/self/key is tied
/encoder/layer/1/crossattention/self/value is tied
/encoder/layer/1/crossattention/output/dense is tied
/encoder/layer/1/crossattention/output/LayerNorm is tied
/encoder/layer/1/intermediate/dense is tied
/encoder/layer/1/output/dense is tied
/encoder/layer/1/output/LayerNorm is tied
Loading default thretholds from .txt....
--------------
preset/models/ram_swin_large_14m.pth
--------------
Traceback (most recent call last):
  File "C:\Users\mikazmaj\SeeSR\test_seesr.py", line 265, in <module>
    main(args)
  File "C:\Users\mikazmaj\SeeSR\test_seesr.py", line 168, in main
    model = load_tag_model(args, accelerator.device)
  File "C:\Users\mikazmaj\SeeSR\test_seesr.py", line 125, in load_tag_model
    model = ram(pretrained='preset/models/ram_swin_large_14m.pth',
  File "C:\Users\mikazmaj\SeeSR\ram\models\ram_lora.py", line 325, in ram
    model, msg = load_checkpoint_swinlarge(model, pretrained, kwargs)
  File "C:\Users\mikazmaj\SeeSR\ram\models\utils.py", line 296, in load_checkpoint_swinlarge
    raise RuntimeError('checkpoint url or path is invalid')
RuntimeError: checkpoint url or path is invalid

Sorry for quistion.
I was able to use project when downloaded model to:
https://huggingface.co/spaces/xinyu1205/recognize-anything/blob/main/ram_swin_large_14m.pth
BEST IMAGE SUPER RESOLUTION I have ever seen! Thank you very much! Wish you all the best Sir!

Thanks for youre attention!


Update documentation

Changes include:

update the .gitignore and README.md files;
add LICENSE file (MIT License);
move the installation of scripts to the end to decrease rebuilding of layers when scripts are changed;
move scripts to a separate sub-directory;
fix permissions on ecr-get-login.sh.

This change is

.gitignore, line 13 at r1 (raw file):

\#*#

# JetBrains Rider

Maybe change this to "JetBrains IntelliJ-based". It's likely someone would actually use PyCharm or IntelliJ to open this repo rather than Rider.

Dockerfile, line 27 at r1 (raw file):

USER user
WORKDIR /home/user
ENV PATH /usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/user/.local/bin

Is it possible to prepend to the existing $PATH if that is the intent rather than duplicating the entire contents?

Dockerfile, line 1 at r1 (raw file):

FROM ubuntu:focal

I personally find it easier to read ubuntu:20.04 as I find it's hard to keep up with the codenames and remember which year they were released.

Dockerfile, line 4 at r1 (raw file):

LABEL maintainer="Jim Grady<EMAIL_ADDRESS>
# Install AWS-CLI version 2

Could we add a URL reference to the docs where you pulled these commands from? That way, if they ever change someone has a quick way to look them up.

Dockerfile, line 2 at r1 (raw file):

FROM ubuntu:focal
LABEL maintainer="Jim Grady<EMAIL_ADDRESS>

It would be helpful to add a GitHub Actions CI job that verified that the Dockerfile builds successfully (helpful to spot errors in future PRs).
This is very simple to do with GitHub Actions and an example is here: https://github.com/sillsdev/TheCombine/blob/e376a137f06d4e970fecb99e635cb2e2a64f7416/.github/workflows/frontend.yml#L38

README.md, line 1 at r1 (raw file):

The Docker image is based off of `ubuntu:focal` and adds:

I think it would be helpful to add a link to where this is stored in Docker Hub: https://hub.docker.com/r/sillsdev/aws-kubectl
Also perhaps provide a short example on how someone is expected to use this in a derived image?
FROM sillsdev/aws-kubectl
# Set ENV variables
# etc.

README.md, line 3 at r1 (raw file):

The Docker image is based off of `ubuntu:focal` and adds:

- aws-cli version 2;

The default docker pull command that is shown on Docker Hub doesn't work yet because there isn't a latest tag. Do you think we should add that to make experimenting with this image easier for prospective users?

 docker pull sillsdev/aws-kubectl
Using default tag: latest
Error response from daemon: manifest for sillsdev/aws-kubectl:latest not found: manifest unknown: manifest unknown

README.md, line 1 at r1 (raw file):
Previously, jmgrady (Jim Grady) wrote…
Done.

I was thinking to put this information into the README so that if someone browses the GitHub repo they can see immediately a link to where the image is hosted on Docker Hub.
What do you think?


Add C++savvy API over Bootstrap's Flat-C API

Experimental C++ API over the Bootstrap Flat-C API.  This is experimental to garner feedback on the API.
Provides equivalent goodness as the C# API does for .NET developers -- overloading, automatic call to Shutdown, yadda yadda. Notably:

All symbols in the Microsoft::Windows::ApplicationModel::DynamicDependency::Bootstrap namespace
TryInitialize() returns HRESULT vs Initialize() throws exceptions
*Initialize() overloaded for convenience
Shutdown() for completeness
AutoShutdown class for use by folks directly using MddBootstrapInitialize() e.g.

RETURN_IF_FAILED(MddBootstrapInitialize(...));
Microsoft::Windows::ApplicationModel::DynamicDependency::Bootstrap::AutoShutdown bootstrapShutdown;

AutoInitialize class wrapping up all the above e.g.

Microsoft::Windows::ApplicationModel::DynamicDependency::Bootstrap::AutoInitialize bootstrapInitialize;

or
Microsoft::Windows::ApplicationModel::DynamicDependency::Bootstrap::AutoInitialize bootstrapInitialize(0x00040002, "experimental7");

As-is it assumes #include <WindowsAppSDK-VersionInfo.h> occurs before #include <MsixDynamicDependency.h>. An open question for feedback: Should it? If we #include the version info header do we also need to make it optional?
Another Q: [Try]Initialize(majorMinor, versionTag) takes optional parameters for both. Is that a bad thing? Remove the optional parameters? If anything's specified everything needs to be or should it assume versionTag=null and minVersion=<IP_ADDRESS>? e.g. is TryInitialize(0x01234567) better as
inline HRESULT TryInitialize(uint32_t majorMinor)
{
    return TryInitialize(majorMinor, nullptr, PackageVersion());
}

or the current
inline HRESULT TryInitialize(uint32_t majorMinor)
{
    return TryInitialize(majorMinor, WINDOWSAPPSDK_RELEASE_VERSION_TAG_W, WINDOWSAPPSDK_RELEASE_VERSION_UINT64);
}

?
Should [Try]Initialize() be overloaded to accept PackageVersion and uint64_t version? And uint16_t major, minor, build, revision? i.e. PackageVersion is accepted as a parameter but raw values are also OK?
The spec will be updated later (before moving this out of experimental) after feedback and validation/refinement of the design has occurred.

/azp run

@emrdev is added to the review. #Closed


The recipe about "serving a virtual file" doesn't quite work as-is

[x] Read the docs.
[x] Use Vite >=2.0. (1.x is no longer supported)
[ ] If the issue is related to 1.x -> 2.0 upgrade, read the Migration Guide first.

Describe the bug
The recipe in https://vitejs.dev/guide/api-plugin.html#serving-a-virtual-file isn't quite right, I think.
The id binding passed to the resolveId and load hooks, will not be === to @my-virtual-file. id is preceded by a forward slash while virtualFileId is not.
Hence the browser's request for this virtual file fails (or curl http://localhost:3000/@my-virtual-file) fails, which is probably not what the script intended.
Reproduction
Sorry, I don't have time for a from-scratch reproduction recipe.

A reproduction is required unless...

Yup, I am fully aware of this and understand if you close this immediately. It's fairly easy to work around the problem: either add a slash to the string constant or use laxer matching.
System Info

vite version: latest bleeding edge (0633dabaf3afc99d551796640adb3aee0adee6e8)
Operating System: linux
Node version: 15
Package manager (npm/yarn/pnpm) and version: 7 something

...did you even try it? Please make sure to actually try it before opening issues.

...did you even try it? Please make sure to actually try it before opening issues.

...did you even try it? Please make sure to actually try it before opening issues.

And please, there's no need to doubt that.  I wouldn't have reported this issue if I hadn't tried it.  I'm working with it now, though not exactly with that recipe, something equivalent.

Aliases are meant for JS import specifiers, not for raw URLs.

Aliases are meant for JS import specifiers, not for raw URLs.
That's not clear from the guide at all.  It says "serve a virtual file"

And even your comment isn't very clear: what are "aliases" in this specific context? alias in the config object?

My bad, I meant custom resolveId resolvers. Conceptually, they work for any valid JS import specifiers. They work when imported from JS as I have demonstrated, because Vite automatically converts them into valid URLs and converts them back to their original value before going into the load phase.

Conceptually, they work for any valid JS import specifiers. They work when imported from JS as I have demonstrated, because Vite automatically converts them into valid URLs and converts them back to their original value before going into the load phase. But you can't expect to visit them directly in the browser from a URL, because well they are not valid URLs.

I suggest you make that clear in https://vitejs.dev/guide/api-plugin.html#serving-a-virtual-file.  There's only a very mild suggestion that that is their only valid use.

They work when imported from JS as I have demonstrated

In this case I'm dealing with an HTML script tag with type=module tag if that makes a difference. That HTML is itself written dynamically in the transformIndexHtml hook.  I don't think there should be much difference to the import case you mention, but as I said there are multiple ways to work around it.
Thanks for the clarification.

The reason it's not working for you is because transformIndexHtml is a post-transform by default, which means any script you injected in it will not get processed by Vite.
See, this is why a reproduction is so important because of all these missed context.

See, this is why a reproduction is so important because of all these missed context.

Mr. You, there's no need to be condescending for a second time here, is there?  I'm coming to this issue becasue there is a sentence in your guide's that says "serving a virtual file", which led me to believe it described a strategy for serving files that have no direct representation in the file system. No where are these subtlesties about "import-only" mentioned. Furthermore, with  few adaptations, it does indeed present that useful strategy I spoke of.
So, in my view, ,  the problem of lack of context applies equally -- if not more -- to your work, not mine.
That said, rest assured I am an experienced software developer and maintainer of open source projects myself and I prize reproduction recipes very much.

I don't think asking for reproductions is being condescending. If you insist that ignoring the requirement was justified we can stop this discussion and you are welcome to stop using my software.

I don't think asking for reproductions is being condescending.

It's not.  But lecturing me about why they are making you lose your time is.

Guess I shouldn't have wasted the time to begin with.


Perform an interrupted time-series analysis - 86cuvkvyy

From: https://app.clickup.com/t/86cuvkvyy
Using the extracted forecasts and its confidence interval, perform an interrupted time-series analysis for counterfactual data after COVID-19.Relevant articles to read further:https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5407170/https://bmcmedresmethodol.biomedcentral.com/articles/10.1186/s12874-021-01235-8https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7818488/https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7231782/

Cancel the interrupted time-series analysis plan


Need webtorrent cli installed

To stream/download using webtorrent, user must have webtorrent-cli installed

yaah that's the case


Missing classes on prod

When I run yarn run dev, everything works perfectly.
But when running yarn run prod then the stylesheet does not include classes like text-blue-lighter and a lot of other classes.
Any ideas?

Can you share a repository that reproduces this? Are you using Purgecss or
similar?
On Sun, Mar 4, 2018 at 11:50 AM Mark Topper<EMAIL_ADDRESS>wrote:

When I run yarn run dev, everything works perfectly.
But when running yarn run prod then the stylesheet does not include
classes like text-blue-lighter and a lot of other classes.
Any ideas?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tailwindcss/tailwindcss/issues/409, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AEH3bJqbVAGFaSopuWuBR_9Iy3uM6F9vks5tbBtSgaJpZM4SbZzm
.

Closing as it's more or less impossible this is a Tailwind issue and rather a build config issue. Happy to help troubleshoot still if you can provide a reproduction.


add rbac authorization

WIP.
Please note that the table structure has been redesigned, is significantly different from the previous one, and is not forward compatible

WIP.

WIP.

Hi, @downdawn
please review!
Other TODO works will start in other medium processes

GTM


Optional coprocessor pathfinding

Provide an alternative method of pathfinding that will run AD* on a coprocessor instead of on a separate thread on the rio.
This should be provided as a pre-compiled cross-platform binary so it can work on pretty much any coprocessor connected to the robot network.
This probably needs a separate repo.

Created repo here
Very work in progress


Fix CLI Error when there is no windows project

Running master (at https://github.com/facebook/react-native/commit/260d68bf8b39cf0fda71fd76490dd86a3373d8ea) I noticed react-native link fails when there is no windows project due to a bug in the code that fetches windows project configs (introduced https://github.com/facebook/react-native/commit/445182c7076593863bcf7dd191d2c4285d6c4b22).
There's a guard to return early if csSolution (the relative path of the windows solution) is null but it needs to be a line earlier, because path.join errors when passed a non-string.
Tested locally on a non-windows project, react-native link errored previously and now succeeds.

GAH!  Thanks @rh389 - sorry I thought it was tested and sure.  Thank you!

@facebook-github-bot shipit


fix: package dependencies should resolve aliased packages

Relates to #510
This PR performs a lookup against each of the dependency table items that also checks a package key. This may need additional validation for cases like https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#renaming-dependencies-in-cargotoml where the packages are not in fact the same. Perhaps a better identifier in the graph should be used to identify equality?

One additional example validation might be, checking that the path key is also set.
dep_one = { version = "0.1.0", path = "dep1", package = "dep1" }

i.e. would be updated but
dep_one = { git = "git@github.com:some_org/dep_one.git", package = "dep1" }

would not.


Add support second wheel for horizontal scroll

Adding support to horizontal scroll by second wheel, 4d wheel and touchpad.
Tested on
OS: Linux with Plasma 5 (X11 session)
Devices:

MX Master 3
touchpad ELAN1200:00 04F3:30BA

Need test on

Mouses with 4D wheel (like g502)
Mouses without 4D and second wheels

Can this be merged? It is a must on Linux laptops. Not ideal, but better than nothing. Doesn't scroll to the end tho, so if some function has long and short lines and cursor is located in a short line, it would let me scroll for only 1 "tick" past the end of that short line. And therefor long line cannot be seen without manually scrolling it with the cursor.


Relax protected namespace config default

Closes https://github.com/pydantic/pydantic/issues/10315
Decided not to warn on method overrides, as that's an incredibly common practice in Python, and type checking does enough warning here in cases of incompatibility.

I think this should be ready for review. Given https://github.com/pydantic/pydantic/pull/10493, I actually don't think it's necessary that we add model_fields, model_extra, etc to the protected_namespaces default:
from pydantic import BaseModel
from typing import Any

class User(BaseModel):
    model_fields: list[str]
    model_computed_fields: list[str]
    model_extra: dict[str, Any]
    model_fields_set: set[str]

user = User(id=1, name='John Doe', model_fields=['id', 'name'])
print(repr(user))
"""
/Users/programming/pydantic_work/pydantic/pydantic/_internal/_fields.py:190: UserWarning: Field name "model_fields" in "User" shadows an attribute in parent "BaseModel"
  warnings.warn(
/Users/programming/pydantic_work/pydantic/pydantic/_internal/_fields.py:190: UserWarning: Field name "model_computed_fields" in "User" shadows an attribute in parent "BaseModel"
  warnings.warn(
/Users/programming/pydantic_work/pydantic/pydantic/_internal/_fields.py:190: UserWarning: Field name "model_extra" in "User" shadows an attribute in parent "BaseModel"
  warnings.warn(
/Users/programming/pydantic_work/pydantic/pydantic/_internal/_fields.py:190: UserWarning: Field name "model_fields_set" in "User" shadows an attribute in parent "BaseModel"
  warnings.warn(
User(model_fields=['id', 'name'], model_computed_fields={}, model_extra=<property object at 0x1057aaf70>, model_fields_set=<property object at 0x1058e9ad0>)
"""

I've also enabled support for compiled patterns, though I don't think that's necessary, as all other overrides are methods - which are standard practice to override, and you'll get type checking warnings if signature isn't compatible or b) warnings if something conflicts with the protected namespaces.


⚠ Cioos Pacific CKAN Sitemap has degraded performance

In dd09235, Cioos Pacific CKAN Sitemap (https://catalogue.cioospacific.ca/sitemap/sitemap-1.xml) experienced degraded performance:

HTTP code: 200
Response time: 14130 ms

Resolved: Cioos Pacific CKAN Sitemap performance has improved in 7736029 after 10 minutes.


fix: git repo url should have .git suffix

This url is used in the RPA and it's used for Tekton git resolver. All the RPAs in konflux-release-data repo use the .git suffix and it's also what's used
as an example in Tekton docs.
For context, a user recently hit an issue:
https://github.com/konflux-ci/release-service-catalog/pull/759
We had a bug that caused an issue with the .git suffix. But e2e didn't expose the problem because the .git suffix was not there.
Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
Issue ticket number and link
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist:

[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[x] I have updated labels (if needed)

/approve
/lgtm

This file isn't in our directory so my approval doesn't count :upside_down_face:

This file isn't in our directory so my approval doesn't count 🙃

So sad 😭 @jinqi7 can you take a look please?


detect low power mode by autoplay

see: https://twitter.com/joshgkirk/status/1636724932091559938?s=46&t=lbfkligB4KPEwmjmZ7pm6A
should be useful for fingerprinting, or garbage/lie detecting (claims not low battery but is low battery via this method)

Interesting. I wonder how it performs on slower devices. Battery API fingerprints are not that great and may not be worth checking for anomalies. It's useful as a yes or no charging fingerprint and connecting patterns in a short-term session. But, this is a nice technique.


/AzurePipelines run

/AzurePipelines run

@mohsha-msft Updated the changes to not return the error when the request id is missing (as err was not expected by the tests). How can I run the tests locally?

@semk ,
Thanks for reaching out and I appreciate your contribution.
As for your query about running the test suite locally, you need to setup these environment variables
ACCOUNT_NAME
ACCOUNT_KEY
BLOB_STORAGE_ACCOUNT_NAME
BLOB_STORAGE_ACCOUNT_KEY
PREMIUM_ACCOUNT_NAME
PREMIUM_ACCOUNT_KEY
SECONDARY_ACCOUNT_NAME
SECONDARY_ACCOUNT_KEY
APPLICATION_ID
CLIENT_SECRET
TENANT_ID

Most of the test cases will work with just the first two (ACCOUNT_NAME and ACCOUNT_KEY)
Please specify them and you can run the tests locally.
Reach out for more help :)


Clicking on "join us on Discord to collaborate!" doesn't work

Clicking on "join us on Discord to collaborate!" on the ReadMe page takes me to an "Invite Invalid" page.

The expected behaviour is that I can join the discord server. Perhaps the link (https://discord.com/invite/zE8guNfG49) has expired?

I opened a PR that should fix this:
https://github.com/etheralpha/project-sunshine/pull/22


feat(experimental): add pin

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Refactoring
[ ] Build or CI related changes
[ ] Tests related changes
[ ] Documentation content changes

What is the new behavior?

https://github.com/taiga-family/taiga-ui/assets/12021443/e123ebde-3d21-4aa0-a6cf-acc3658d4b3f

на ревью
1. Для чего нужны тайтл и сабтайтл? Может просто сделать :first-line? Не может же быть сабтайтла без тайтла.
2. tui-pin-dot может сделать через color, а не background?
3. tui-pin-selected может быть без точки? Может её зашить внутрь?
4. tui-pin-icon точно нужен? Нельзя как-то без него обойтись? Что там может быть, кроме него, почему этот внешний вид не зашит сразу?

@waterplea

I'll wait for your suggestions
Do you mean that the component name will be different?  <tui-cursor-map /> instead of <tui-cursor pointer />
Do you mean that the component name will be different?

before
<tui-pin>
   Title

   Subtitle
</tui-pin>

after?

   <tui-pin src="image" />
   Title

   Subtitle
</tui-pin>

Open state should be positioned around the bottom with top content not affecting it in terms of layout.
does it have to be absolute positioning?

You mean

    <tui-pin src="img" tuiPinInteractive></tui-pin>
    <tui-pin tuiPinInteractive>123</tui-pin>
    <tui-pin tuiPinInteractive>5</tui-pin>
    <tui-pin tuiPinInteractive>23</tui-pin>

or just
    <tui-pin src="img" tuiPinInteractive></tui-pin>
    <tui-pin tuiPinInteractive>123</tui-pin>
    <tui-pin tuiPinInteractive>5</tui-pin>
    <tui-pin tuiPinInteractive>23</tui-pin>

@waterplea hello, please review me

Height is a bit off:

Maybe you can use the new tuiTitle component here? Perhaps style it with ::ng-deep or disable style encapsulation for pin.
Image is missing the white border (the is one if Figma):

Small pin has the blue border around image and not in Figma:

Small pin in Figma has 2 modes of icon, could you add this example too? Note that image with white background has a smaller icon:

I think that is because the blue border is actually a border so the content inside gets smaller.
Here how I think this could work. Border would be 0 solid by default, so it inherits color and people can just modify border-width if they need:

Here's the open state:

::before and ::after will be made of just the border, which inherits the border color. ::after will inherit box-shadow too. ::before will use SVG mask to have the desired shape, and it will also cover the box-shadow on the host so it is only visible on the small circle below. The blue border can be extended using border-width. Minimum of 2px which is currently there is part of the SVG mask and cannot be made smaller, I check with designers. In case of image we can make it's height a bit smaller so that box-shadow is visible and those 2px of white are there.

@waterplea hello, please review me

there's something wrong with the animation in safari
https://github.com/taiga-family/taiga-ui/assets/46284632/8454d5c9-d530-488f-92b8-f3ec6d1f65b1


Use new MapIt in Staging

This is to switch Staging to use the new MapIt servers.  Once we have run the set of tests detailed in the Trello card, we will have greater confidence that the switch over in Production will go smoothly.  We envisage that the environments will be different for a few days.
This supersedes this PR which we will redo:
https://github.com/alphagov/govuk-puppet/pull/4220
Trello card detailing tests:
https://trello.com/c/2KngFMJL/352-final-tests-before-switching-over-to-use-new-mapit-in-production

This branch is out-of-date with the base branch

It's OK now :-)

This is correct as of latest master which right now is 650c6366be94f219276b870604e9585ec166db2d :+1:


Bump to version 0.2.10

Short description

Bump to version 0.2.10
Proposed changes

Bump version in VERSION.txt, __init__.py and README.rst
Update release notes

New release was generate on
https://pypi.org/project/xhtml2pdf/0.2.10/
Thanks @timoludwig  for you help


PR template

#63
Pull Request Description
Description:
This pull request introduces a Pull Request (PR) template to the project. The purpose of the PR template is to standardize and improve the quality of pull request submissions by ensuring that contributors provide the necessary information. The template guides contributors to summarize their changes, link related issues, include testing details, and provide any relevant screenshots.

Added a pull_request_template.md file under the .github/template directory.
The template includes sections for description, key changes, related issues, screenshots, testing, types of changes, and a checklist for contributors.

Key Changes:

[x] Added: .github/template/pull_request_template.md

Related Issue(s)
No related issues were resolved by this pull request.
Screenshots (if applicable)
No screenshots are applicable for this PR.
Testing
Not applicable. This change only adds a markdown file that will be used when creating pull requests.
Type of Changes

[x] Documentation update (adding a PR template)

Checklist

[x] I have read the contribution guidelines
[x] My code follows the project’s coding style
[x] I have performed a self-review of my code
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works (N/A)
[x] All new and existing tests passed (N/A)

Additional Notes
This PR template aims to improve the pull request process by making it easier for contributors to submit consistent, detailed, and high-quality PRs.

Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch. After resolving the conflicts, please open a new PR for review.
Thank you!


Current Browser Versions?

So I was hoping that this somehow used some sort of auto updating or remote resource for the currently updated browser versions.
The website http://browser-update.org/ shows that the current versions of Chrome and Firefox for example are <100; they have been >100 for a bit now.
While this tool seems great, it almost feels pointless if it's not auto-updating with browser releases and this can be even worse potentially if you're self-hosting if they're hard coded in the script?

As of today http://browser-update.org/ lists the following versions as current:
Edge 118
Firefox 120
Safari 16
Chrome 119
Which is wrong, the current versions are:
Edge 123
Firefox 124
Safari 17
Chrome 123
Can you please update this, so that the current versions are correct?

Updated the versions.
The versions are manually updated every 1-3months. I tried auto-updating but it makes more sense to manually check that everything is right. I think it should be more prioritized to not have false positive notifications instead of being up to date to the very day.


ARIA compatible & keyboard navigation

Hi @damusnet! The plugin looks great, thanks for open sourcing it!
Do you plan to add keyboard navigation and make it ARIA-ready for accessibility?

Hi @oyeanuj, thanks for your kind words.
Unfortunately I stopped maintaining this plugin a while back and for the foreseeable future.
Maybe check out react-swipeable-views?
However, I will do my best to try and merge any PR if you wish to contribute.


Add renovatebot as a dependency management option

The otel upstream repos for java and android are using Renovatebot. It as a few advantages, including combined PRs and maintenenance of a summary issue for dependencies. I'd like to switch over to it in our splunk java GDI repos as well.

I have read the CLA Document and I hereby sign the CLA

recheck


Render templating code inside highlight tag

Hi 👋
Thanks for the great plugin!
I am currently looking at moving a Jekyll site to Eleventy, where we have a pattern page with a code block showing that pattern's HTML:
_code.html (file)
{% highlight html %}
  {% include folder-example/file-example %}
{% endhighlight %}

With Jekyll, this will actually include the file and output the HTML inside the file:
/pattern (web page)

Hello, I am a pattern

This is great, as any changes made to the code get reflected in the pattern code block for developers to see.
With the plugin, it actually renders out what is exactly contained inside the {% highlight %} tag:
_code.liquid (file)
{% highlight html %}
  {% include folder-example/file-example %}
{% endhighlight %}

/pattern (web page)
{% include folder-example/file-example %}

Obviously the plugin is doing its job, but is there a way the plugin could render out the templating language that is being used, instead of literally displaying what is written (easier to say than to actually do it)?
Or would you recommend creating a custom filter to render whatever has been written?
Many thanks 👍

Hey Ben,
I think you can use the Nunjucks Paired Shortcode version of the highlight shortcode. Paired shortcodes let you nest template content inside of shortcodes, and would render output as you're expecting. Understandably, this would mean using Nunjucks instead of Liquid, which makes migrating from Jekyll a bit more of a pain.
However, it looks like the Nunjucks Paired Shortcode is being loaded using the universal Paired Shortcode syntax, meaning it should work inside Liquid templates, too. I'm not sure how to explicitly use the "Paired Shortcode" version instead of the "Liquid Shortcode" version, unfortunately.

Hey @jordanthornquest
Thanks for the tip!
While migrating the project to Nunjucks is something to work on in the future (the project has a lot of files and the focus is moving off Jekyll), your link to the Paired shortcodes did help!
For future reference for anyone, this is what I ended up doing:
eleventy.js (file)
eleventyConfig.addPairedLiquidShortcode('showCode', function (code) {
 const html = ...formatting code

  return `${html}`;
});

_code.liquid (file)
{% showCode %}
  {% include folder-example/file-example %}
{% endshowCode %}

/pattern (web page)

Hello, I am a pattern

@benbrehaut am I right in understanding that your final solution was not using this syntax highlighting plugin in the first place?

Hey @rijkvanzanten, so sorry for the late reply!
You are correct, in the end, we just used Prism.js and passed in the file contents to it, and it returned the formatted code.
Attached example
.eleventy.js
const Prism = require('prismjs');

module.exports = function (eleventyConfig) {
    eleventyConfig.addPairedLiquidShortcode('showCode', function (content) {
        prismloadLanguages(['html'])
        const html = Prism.highlight(content, Prism.languages.html, 'html');

        return `<figure class="highlight"><pre><code class="language-html">${html}</code></pre></figure>`;
    });
}

Hey @rijkvanzanten, so sorry for the late reply!
You are correct, in the end, we just used Prism.js and passed in the file contents to it, and it returned the formatted code.
Attached example
.eleventy.js
const Prism = require('prismjs');

module.exports = function (eleventyConfig) {
    eleventyConfig.addPairedLiquidShortcode('showCode', function (content) {
        prismloadLanguages(['html'])
        const html = Prism.highlight(content, Prism.languages.html, 'html');

        return `<figure class="highlight"><pre><code class="language-html">${html}</code></pre></figure>`;
    });
}


Descriptive message for errors related to unknown http2 streams

Motivation:
When unknown http2 stream error occurs, It is hard to analyze root cause since only streamId is provided in message.
Modification:
Add frame type, endOfStream flag (where applicable) to error message.
Result:
More descriptive error messages.

@mostroverkhov good idea! Thanks


Implemented auto translate module with free API connection using Retrofit

API documentation: https://github.com/LibreTranslate/LibreTranslate

You will get a :gift: after you show in a test that your code works.


sol::optionalsol::function aborts when constructed from non-function

I am trying to safely call a function in a table. From the reading variables tutorial I expected sol::optional to be nullopt when the given value cannot be converted to the contained type. However, the following program causes an abort when assigning func.
#define CATCH_CONFIG_MAIN
#include "catch.hpp"
#include "sol.hpp"

TEST_CASE("optional<function> is created from integer") {
    sol::state state{};
    sol::table table = state.create_table_with("func", 42);
    sol::optional<sol::function> func = table["func"]; // SIGABRT
    REQUIRE(func == sol::nullopt);
}

An error occurred and panic has been invoked: stack index -1, expected function, received number: must be a function or table or a userdata (type check failed in constructor)

Storing lookup results in sol::optional<sol::function> works fine in cases where the value is either nil or a function, however, it breaks for values of other types. A possible workaround would be to do the lookup and invocation through a safe_script call, however I would like to avoid invoking the parser in this code. This abort should at least be documented in the linked tutorial section, since it is not intuitive from the given examples.
I am using Lua 5.3.4 (compiled as C), Sol 2.20.0, Catch 2.1.0 and C++17. My compiler is g++ 7.3.0 and I'm on Linux. Code is compiled using CMake with CMAKE_BUILD_TYPE=Debug. Compiling in release mode doesn't print the error message but Catch reports that the REQUIRE fails.

Yeah, there seems to be some problems around sol::optional that I need to look into. I'm at a conference right now, so this will be solved a little bit later.
Sorry about this! As a work around, you can pull out sol::object and then use obj.as<> to convert after doing an is<> check. It's ugly, but it's just a workaround for the next few days if you really need to get going. I would suggest putting it inside of a function so you can tear it out in a few days.


PM::TableViewCell functionality

As discussed offline with ye olde @GantMan, any chance of sneaking ProMotion's Table Cell functionality in?  Our app is heavy-custom-cells in iOS.
Even starting with a blank cell view & stylesheet would :+1: and enough to get me going.
Exciting times!

making great progress on this.

Thank you for your hard work.  I've got this up & running in our app.  :+1:

:shipit:


Multimodel Agent to support user_speech_committed and agent_speech_committed events

Currently they are supported on Python but not Node yet.

user speech committed is trivial, but agent speech committed depends on #99

We need this for transcriptions because the user can send written chat messages (outside of LiveKit) as well. It's the last remaining piece before we can start testing with users. The entire app built around it, including accepting payments, is done (at least in MVP form). Would love this ASAP.


Fix javadocs issues

Addresses TAMAYA-154
This adds some missing javadoc parameters.

Closed via https://github.com/apache/incubator-tamaya-sandbox/commit/cac421bda9aafc28e8171c8a3d2eb581586e5a13


Add TwoFactorRequirementEnabled to Organization

Thank you, @eperm. Please run gofmt on github/orgs.go and then push the updated version.
See our CONTRIBUTING.md file for more information.

LGTM.
Merging.


tests: fix coverage

Fix for #132

Codecov Report

Merging #139 (3c47993) into master (307235f) will increase coverage by 22.12%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master     #139       +/-   ##
===========================================
+ Coverage   32.68%   54.81%   +22.12%
===========================================
  Files          68       68
  Lines        4479     4479
  Branches        0      727      +727
===========================================
+ Hits         1464     2455      +991
+ Misses       3015     1802     -1213
- Partials        0      222      +222

Impacted Files
Coverage Δ

lona/middlewares/lona_messages.py
58.33% <0.00%> (-16.67%)
:arrow_down:

lona/middlewares/sessions.py
77.77% <0.00%> (-8.89%)
:arrow_down:

lona/default_views.py
75.00% <0.00%> (-3.13%)
:arrow_down:

lona/response_parser.py
59.52% <0.00%> (ø)

lona/static_file_loader.py
75.86% <0.00%> (+3.44%)
:arrow_up:

lona/events/input_event.py
50.00% <0.00%> (+3.84%)
:arrow_up:

lona/view_runtime.py
51.54% <0.00%> (+9.25%)
:arrow_up:

lona/view_runtime_controller.py
57.89% <0.00%> (+10.52%)
:arrow_up:

lona/worker_pool.py
50.00% <0.00%> (+11.11%)
:arrow_up:

lona/middleware_controller.py
80.45% <0.00%> (+13.79%)
:arrow_up:

... and 44 more

Continue to review full report at Codecov.

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

@sobolevn I broke coverage upload with the first patch. Also the pytest.ini had to be cleaned up.

@sobolevn, @maratori: thanks for your help and review!


PatNet: Fix footer to properly adapt web and mobile view

Change-Id: I0d3eebe0b0ff4fbca4245896c029816e05ecd503

Code Review comments can be found at https://gerrithub.io/q/I0d3eebe0b0ff4fbca4245896c029816e05ecd503


Implement new tls tracing method behind stirling cli flag (feature toggle)

Summary: Implement new tls tracing method behind stirling cli flag (feature toggle)
The tls tracing method added in this PR determines a connection's identity (socket fd) through a different mechanism from our existing tracing. Instead of relying on struct offsets of user space data structures, it accesses the socket fd via the underlying socket syscalls while SSL_write / SSL_read calls occur. This is a prerequisite to support BoringSSL because its rolling release style makes the previous method of user space offsets untenable. This has the added benefit of reducing our maintenance cost for our existing OpenSSL tracing. Assuming future versions of OpenSSL maintain the same contract, we will not require any code changes to support them -- Pixie will gain OpenSSL v3 support once this new tracing is the default (as mentioned in the later testing).
Our assumption is that the applications that explicitly set the socket fd on the SSL struct (the applications supported by our previous tracing technique) -- nginx, python all use Openssl with its native BIO interface. In order to verify that assumption, this change will be feature flagged and monitored carefully as its enabled on internal clusters. A future change will add metrics for volume of tls traffic traced to verify there is no loss of instrumentation coverage between the new and old method.
Relevant Issues: #692
Type of change: /kind feature
Test Plan: Verified the following

[x] New test passes with enable_openssl_v3_testing config setting enabled (P336). This verifies that the new tracing technique and the feature toggle are functional since our previous tracing does not support OpenSSL v3
[x] Existing openssl_trace_bpf_test and netty_tls_trace_bpf_test passes (P335). This is explicitly mentioned since openssl_trace_bpf_test is still disabled #699

My understanding is that there's two flags to control the new behaviour: a build time flag and a runtime flag

@JamesMBartlett regarding your comment above, is the build time flag you are referencing the enable_openssl_v3_testing config setting? If not, can you please identify what you are referencing?
The enable_openssl_v3_testing setting is temporary and only intended for running tests. If kLibSSLMatchers was configurable at runtime, I would have opted for the test to override its entries rather than using a build setting.
This new method of tls tracing should provide the same coverage as our existing method, meaning that a PEM should trace the same amount of bytes before and after the change. However, I want to verify that assumption. In order to test that, I intend to roll out the new implementation while keeping our supported tls tracing targets constant (OpenSSL v3 must remain disabled as the feature toggle is enabled). Once the new implementation is fully rolled out and the coverage is validated against our existing method, we can remove the config setting and release OpenSSL v3 support.

Moving this back to a draft since there is some additional testing the Stirling team wants to do prior to pushing forward with this.

@etep this is ready for review again.


Need defer reply on /sacrifice & /trade

🐛 Bug Report
Basically anywhere the Not sacrificed filter is used you need to defer the reply due to wait times
prior example: https://github.com/oldschoolgg/oldschoolbot/issues/3684 (bank)
fixed this way: https://github.com/oldschoolgg/oldschoolbot/pull/3854

Done in next update


fix: dropdown ChevronLeft position

📑 Description
Move the ChevronLeft to the left side of the button.
✅ Checks

[x] My pull request adheres to the code style of this project
[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required
[x] All the tests have passed
[x] My pull request is based on the latest commit/version

ℹ Additional Information

Thank you for the quick reply. Merged.


RadSideDrawer 4.0.0 not opening on playground.

here is playground link https://play.nativescript.org/?template=play-ng&id=IGa87M
i'm also attaching the local project zip file
drawer.zip
both are identical but on playground it is not working as expected.
we can't open drawer from component and also when drawer is opened by swiping it doesn't show over navigation  bar.
i had implemented sidedrawer as a root element in app.component.html

@bhavincb thank you for reporting this issue. The PlayGround is wrapping the test code in the Preview application which is causing the difference in the behavior. We will investigate the possibilities to improve the sidedrawer behavior at the root level.
However, you should not worry because the exported code will work exactly as expected on real device and emulators.

hii @NickIliev ,
yes downloaded code works fine in local environment. but people checking new feature from documentation on play ground might be confused and may think that this feature is broken.

@bhavincb, thanks for submitting this issue.
After further investigation it turns out that it is related to the<EMAIL_ADDRESS>module used in the Playground. This issue is resolved in<EMAIL_ADDRESS>I will let you know once we update the Preview app.

@bhavincb, we have published a new version of the Preview app which should resolve the issue with the sidedrawer component.


checkboxes not appearing

go to: https://affiliates.nordvpn.com/
see that the 2nd checkbox (cookie policy) is not visible.

I noticed same thing on twitter site

That bugs seems to be fixed on latest builds . Feel free to reopen the issue if necessary


🎉 Update all the things 🔥

This does too much.

7,8/10 bad PR message
Most of the changes are good but a number of pages/links currently don't work

some images I ran into, like shadow progression on /appendix/weapons-per-powertype/shadow and steam laser mkI
appendix->weapons->arcane/rift/tactical
-law/MPCT
also not sure where it originated but typo on slmk-page, has 2 titles of mkII

assuming these changes are still part of WIP PR, but noting to be sure


App Transport Security and no images - only placeholders

Using xcode 7.1/iOS8 and trying to open Remote Data Store Tableview, I got the message "The resource could not be loaded because the App Transport Security policy requires the use of a secure connection". So I changed static NSString * const APIBaseURLString = @"http://obscure-refuge-3149.herokuapp.com"; ... to https. Now I get the table view but instead of images there are only placeholders (default avatar).

Anyway I don't get images neither in Data Store TableView. Then inside I changed the images http with https and I got the images...
It seems that json is OK, BUT the returned links of images are http and not https ....
[{"user":{"id":1,"name":"Apu Nahasapeemapetilon","imageURL":"http://obscure-refuge-3149.herokuapp.com/images/Apu_Nahasapeemapetilon.png"}},{"user":{"id":7,"name":"Bart Simpsons","imageURL":"http://obscure-refuge-3149.herokuapp.com/images/Bart_Simpsons.png"}},{"user":{"id":8,"name":"Homer Simpsons","imageURL":"http://obscure-refuge-3149.herokuapp.com/images/Homer_Simpsons.png"}},{"user":{"id":9,"name":"Lisa Simpsons","imageURL":"http://obscure-refuge-3149.herokuapp.com/images/Lisa_Simpsons.png"}},{"user":{"id":2,"name":"Maggie Simpsons","imageURL":"http://obscure-refuge-3149.herokuapp.com/images/Maggie_Simpsons.png"}},{"user":{"id":3,"name":"Marge Simpsons","imageURL":"http://obscure-refuge-3149.herokuapp.com/images/Marge_Simpsons.png"}},{"user":{"id":4,"name":"Montgomery Burns","imageURL":"http://obscure-refuge-3149.herokuapp.com/images/Montgomery_Burns.png"}},{"user":{"id":5,"name":"Ned Flanders","imageURL":"http://obscure-refuge-3149.herokuapp.com/images/Ned_Flanders.png"}},{"user":{"id":6,"name":"Otto Mann","imageURL":"http://obscure-refuge-3149.herokuapp.com/images/Otto_Mann.png"}}]
Also the (http as well as https) images are there ...

I've just fixes this issue.
Thanks for reporting it.


ZBus Error

This is probably an issue on my side but you're more knowledgeable than me on this stuff.
I used to have a Linux CI/CD (on GitHub Actions) working perfectly fine to run this, but ever since a few days ago, I've been having the error:

Error { kind: Zbus(Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })) }

I'm assuming this means there's some kind of config file that's missing somewhere to enable the notification system through dbus. I don't know much about Zbus/Dbus but seeing from your own config, simply having libdbus-1-dev should be enough?
So I'm wondering if maybe something changed in notify-rust related to that? And if not, maybe you have some insight for what I could look into?
Thanks

You technically only need libdbus-1-dev if you're compiling with the dbus-rs dependency enabled, that is no longer the default. AFAIK zbus is completely independent of what you might have on your system (@zeenix might be able to confirm this statement).
With these "No such file or directory" errors it's always a bit hard to tell, sometimes you get those when the programm is trying to shell out or open a socket, maybe dbus/zbus have to use a specific system file (virtual file) to connect to the bus and it can't find that. You can tell, at this point I can really only speculate, unless you have a proper backtrace.
BTW: for these kinda issues I enabled Discussions feature in this repo, maybe we should take it over there.

AFAIK zbus is completely independent of what you might have on your system (@zeenix might be able to confirm this statement).

Confirmed. We only require DBUS_SESSION_BUS_ADDRESS to be correctly set for the session bus and the bus to be actually running.

You technically only need libdbus-1-dev if you're compiling with the dbus-rs dependency enabled, that is no longer the default.

@hoodie Maybe it's time to reduce the complexity and drop the dbus-rs dep and code all together?

I've been a bit reluctant to remove it, I mostly because I've had a user or two in the past who asked me not to update the MSRV because their shipping the library in some distribution, and zbus is usually pretty up with compiler features.

I've been a bit reluctant to remove it, I mostly because I've had a user or two in the past who asked me not to update the MSRV because their shipping the library in some distribution, and zbus is usually pretty up with compiler features.

Fair enough. I've actually been trying not to use the latest and greatest features but sometimes there are new std API that I needed 2 years ago so it's hard to not jump on them as soon as they're stabalized. :) Having said that, I'm not planning on using latest features in 2.0 cycle.


nginx: Suppress proxy warnings when the proxy itself sent the request.

This is common in cases where the reverse proxy itself is making health-check requests to the Zulip server; these requests have no X-Forwarded-* headers, so would normally hit the error case of "request through the proxy, but no X-Forwarded-Proto header".
Add an additional special-case for when the request's originating IP address is resolved to be the reverse proxy itself; in these cases, HTTP requests with no X-Forwarded-Proto are acceptable.
CZO discussion

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Looks great, merged, thanks @alexmv!

Backported in https://github.com/zulip/zulip/pull/26750.


Logo proposal

Hey, my aim is make my portfolio better with contribute on open source projects in field of graphic. If you interested I can make a logo design for Detox. I can show my portfolio if you interested. I am waiting your feedback! Have a nice day.
Best Regards,
Baran Pirincal
Visual Communication Designer

YESS!!!!!!!!!!!!!!!!!!!!!!!!!!

@rotemmiz Do you have an idea or suggestion about design&decision. Should design contain letters of Detox or is it not necessary?

Not really an expert in the field, but I think the logo should be a drawing, no text.
Something that may translate into an icon or sticker in a good way.

We had a few ideas in the past, but non translated in a good way to a logo, I don't want to limit anything.
What did you have in mind ?

@rotemmiz Actually I will examine your project firstly. After that I will share my first experiments with you. If you want to show any object, metaphor or something like that you can share with me. It will be better for me

Please no juices or drinks. 😜

BTW, thank you for offering this. We are humbled by such an offer!

@LeoNatan @rotemmiz
Hey, you're welcome. I made my first experiment, what do you think about?
I tried to make a logo design that translate into an icon or sticker as you said. However, please feel free to say any request,idea and feedback.

Thanks for working on this!
We’ve discussed this a little internally and were thinking that maybe an automation robot could fit this project. What do you think?

@LeoNatan You're welcome. Sorry for delay, I was too busy last week. I will work on Automation robot. It would be better, have a nice day!

Hey Guys, was just thinking as the name is DetOX, how about a logo modified from an illustration of an ox face and if we could fit in "D" as an illustration on the same, it would then need no text as well. Just by looking at the logo we could make out its Detox.
PS: I'm not an expert in Graphic / Logo Designs, just a thought struck to the mind and shared the same. Please ignore if it doesn't make any sense.

💔