EquiBloc Creative Ventures.md

PROJECT NAME:
EquiBloc Creative Ventures
Team Name: Sirius Africa
Payment Address: (Ethereum) : 0xe07767abe76de87C1DbF7D9d281805d7678A0ce6
Level: 2
OVERVIEW
Tagline: Transforming Africa's Creative Landscape with Blockchain Innovation
Description: Sirius Africa is revolutionizing Africa's creative industry by providing a blockchain-powered platform that offers structured equity financing to content creators, bridging the existing funding gap. Our platform accumulates industry data to streamline the process and recommend strategic partnerships, enhancing the entire creative ecosystem.
Integration with Substrate / Polkadot / Kusama: Sirius Africa envisions integrating with the Substrate framework to leverage the scalability, interoperability, and security features it offers. This integration will enable us to create a robust and scalable blockchain infrastructure tailored to Africa's unique creative landscape.
Team's Interest: Our team is deeply motivated to address the lack of structured equity financing in Africa's creative industries. We see the transformative potential of blockchain technology in democratizing access to funding and catalyzing growth. With a decade-long commitment to enhancing digital and physical infrastructure in the creative sector, we are driven to pioneer this innovative solution and reshape Africa's creative landscape for the better.
Project Details
Our project's expected final state is a fully functional blockchain-powered platform that facilitates structured equity financing for Africa's creative industries. This platform will provide creatives with access to funding, streamline the equity financing process, and offer data-driven recommendations for strategic partnerships.
Patents and Share Screen Video Call:
Sirius Africa holds several patents poised to revolutionize the creative industry:

Patent for novel methods of using blockchain technology to facilitate equity financing.
Patent for innovative algorithms or techniques for evaluating and determining the value of equity stakes in creative projects.
Patent for new methods of managing and distributing equity financing within a multi-channel network structure.
I am eager to discuss these patents in detail during a share screen video call session. Unfortunately, I am currently unable to share patent documents due to our ongoing state of development.
Transition to USDT and Project Deck:
Excitingly, we've recently embarked on a strategic journey by transitioning from E-naira to USDT, ensuring enhanced stability throughout our progress. To delve into the depth of our ongoing project, I encourage you to explore our current project deck: Project Deck Link.
Commitment to Industry Infrastructure:
For over a decade, we've dedicated ourselves to strengthening both digital and physical infrastructure within Africa's creative sectors. To witness a compilation of our initiatives and achievements, I invite you to explore our Data Room: Data Room Link.
Your exploration of these resources will provide further insight into our vision and commitment to transforming Africa's creative landscape.

Relevant Submissions:
Data Models/API Specifications: We will provide detailed data models and API specifications outlining how user data, funding transactions, and industry data will be structured and interact within our platform.
Technology Stack: Our technology stack will include blockchain (Substrate), AI (machine learning models), web development frameworks, and cloud infrastructure.
Core Components/Protocols: We will deploy core components such as user authentication, smart contract-based funding, data analytics, and recommendation algorithms.
PoC/MVP: We will present a Proof of Concept (PoC) or Minimum Viable Product (MVP) showcasing essential features like user registration, funding transactions, data accumulation, and basic recommendation functionality.
Clarification on Limitations:
Our project will not provide traditional banking services or investment advice. While we facilitate equity financing, we will not engage in active fund management. Additionally, our platform will not guarantee financial outcomes for users, as investment returns are subject to market dynamics. We will not offer legal advisory services or professional design assistance, as we intend to leverage AI to assist content creators in these areas.
Ecosystem Fit:
Project Positioning:
Sirius Africa integrates into the Polkadot/Substrate/Kusama ecosystem as a blockchain-powered platform tailored for Africa's creative industry. Our innovative solution addresses the absence of structured equity financing in the continent's creative sectors. By leveraging blockchain technology, we aim to create a secure, transparent, and accessible ecosystem for funding creative projects.
Target Audience:
Our primary audience includes dApp developers, creators in Africa's creative industries, and potential investors seeking exposure to the region's creative scene. Additionally, our platform opens doors for UI/UX designers, as we emphasize user-friendly experiences for all participants in the ecosystem.
Meeting Key Needs:
Sirius Africa's project addresses the critical need for structured equity financing within Africa's creative sectors. By providing a blockchain-based platform, we empower creators to access funding opportunities that were previously scarce or unavailable. This bridges the gap between creators and investors, fostering growth and innovation within the industry.
Comparison to Similar Projects:
While there are existing projects in related ecosystems, such as blockchain-based financing platforms, there is a dearth of solutions catering specifically to Africa's creative industries. Sirius Africa stands out by focusing on this niche, combining blockchain and AI to transform an underserved sector. Our emphasis on equity financing, industry data accumulation, and tailored recommendations sets us apart.
Differences from Similar Projects:
Unlike projects in related ecosystems that may not be region-specific, Sirius Africa is uniquely poised to cater to Africa's creative landscape. We provide a holistic solution that encompasses equity financing, data-driven insights, and AI-powered recommendations. Our focus on enhancing local industries and addressing challenges specific to Africa sets us apart from more generalized solutions.
Team members

Name of team leader - Dazi Ezekiel-Zang
Names of team members

Contact

Contact Name: Full name of the contact person in your team- Japheth Jonathan
Contact Email: Contact email -<EMAIL_ADDRESS>Website: https://siriusafrica.com/project/

Contact

Contact Name: Full name of the contact person in your team-  Dazi Ezekiel-Zang
Contact Email: Contact email - info#siriusafrica.com
Website: https://siriusafrica.com/project/

Contact

Contact Name: Full name of the contact person in your team-   Afam Ojemeni
Contact Email: Contact email -<EMAIL_ADDRESS>Website: https://siriusafrica.com/project/

Contact

Contact Name: Full name of the contact person in your team-   Wura Alake
Contact Email: Contact email -<EMAIL_ADDRESS>Website: https://siriusafrica.com/project/

Legal Structure

Registered Address: 1 Ikota Road, Ajah, Lekki, Lagos State, Nigeria.
Registered Legal Entity: Sirius Africa InLtd.

Team's Experience:
Our team is uniquely poised to drive the success of this innovation, bringing together a diverse range of expertise to ensure a seamless execution:
Japheth Jonathan, Chief Technology Officer:
Japheth is a seasoned expert in app, Web3, AI, and blockchain development. With an impressive track record of single-handedly engineering successful blockchain products, his hands-on approach and innovative mindset are instrumental in delivering cutting-edge solutions. Japheth's technical proficiency, coupled with his academic background in Project Management and Computer Science, empowers him to manage projects effectively.
Dazi Ezekiel-Zang, Founder/CEO:
Dazi is a visionary executive committed to leveraging blockchain technology and AI to revolutionize Africa's creative media industries. His deep understanding of digital and physical infrastructure's potential fuels our mission to create a unified market powered by blockchain innovation. Dazi's strategic insights and visionary leadership guide our organization's direction, ensuring we remain at the forefront of technological advancements.
Afam Ojemeni, Chief Adviser:
Afam contributes over 15 years of software development experience, particularly in multinational and international government contexts. As an Engineering Manager with Amazon, Afam leads teams in creating solutions that impact millions worldwide. His expertise in scalable software solutions ensures our systems are robust and reliable, driving our technological advancements.
Wura Alake, Chief Marketing Officer:
Wura's strong background in media/PR, along with her experience with the Lagos State Government, enriches our marketing and communication strategies. As the Founder/CEO of Iwabiwura, she brings valuable insights into effectively reaching and engaging our target audience. Wura's experience in public administration and deep understanding of the African market amplify our organization's ability to connect.
The team's diverse skills, rich experience, and deep market understanding position us for success. With technical prowess, visionary leadership, and strategic marketing acumen, we are ready to navigate challenges and seize opportunities within Africa's creative financing landscape. Our innovative drive ensures that our project thrives and delivers substantial impact.
Team Code Repos
Currently, we do not have any active team code repositories on GitHub. We are in the process of developing our projects and will provide GitHub repositories once they are available. Thank you for your understanding.
Team LinkedIn Profiles
Certainly, here are the LinkedIn profiles of your team members:

Afam Ojemeni: https://www.linkedin.com/in/afamoj/
Japheth Jonathan: https://ng.linkedin.com/in/japheth-jonathan-8a503920b
Dazi Ezekiel-Zang: https://www.linkedin.com/in/dazi-ezekiel-zang-79335279/
Wura Alake: https://ng.linkedin.com/in/wuraoladamilolaalake

Development Status
Our journey has been a blend of in-house efforts and industry engagement. A significant part of our work has been conducted internally, including feasibility studies that gauge the industry landscape. We've also orchestrated global campaigns that garnered enthusiastic support from creatives in the diaspora, amplifying our project's reach. While detailed write-ups regarding our endeavors can be found in our Data Room, we've been actively engaged in shaping the project's direction and conducting research to underpin its viability. Visit our Data Room to explore the comprehensive documentation that reflects our commitment and progress: https://drive.google.com/drive/u/0/folders/1RcNrptPDYAERe5EVstJNUpAH1SJfzgn_ .
Development Roadmap 🔩
Overview:

  MVP Development and Launch ($20,000):

Hiring developers and engineers for MVP creation: $10,000
Design and User Experience: $5,000
Quality Assurance and Testing: $3,000
Marketing and Initial User Engagement: $2,000

  Strategic Partnerships and Software Development ($10,000):

Collaboration with Algo Coding Expert for advanced software: $6,000
Engaging Software Development Experts: $3,000
Software Development Planning: $1,000

  Team Building and Technical Expertise Enhancement ($5,000):

Recruitment of Essential Team Members: $3,000
Training and Skill Enhancement: $2,000

  Equity Financing Integration and Growth Strategy ($5,000):

Implementation of Blockchain-Based Equity Financing: $3,000
Outlining Growth Strategy for User Base and Revenue: $2,000

Project Metrics:

Total Estimated Duration: 4 months
Full-Time Equivalent (FTE): 8 FTE (Average number of full-time employees working throughout the project)
Total Costs: $40,000 USD

Future Plans for EquiBloc Creative Ventures
Short-Term:
In the immediate future, our focus is on rapid development and deployment of our MVP. We intend to use the grant funds to hire skilled developers and engineers to create a robust MVP that showcases the core functionality of our blockchain-based equity financing platform. This MVP will serve as the foundation for our platform's launch and user engagement.
Enhancement is critical to our approach. We plan to continuously refine the user experience based on user feedback and real-world usage. We also aim to establish strategic partnerships, collaborating with experts in algorithmic coding to refine our software's functionality and enhance its efficiency.
Promotion and user adoption are paramount. Our marketing efforts will be geared towards generating awareness among creatives in Africa's diverse creative industries. We plan to host targeted campaigns, webinars, and engagement events to onboard users and create a vibrant user community.
Long-Term:
Our long-term vision is to establish EquiBloc Creative Ventures as the go-to platform for equity financing in Africa's creative industries. We envision a comprehensive ecosystem where creatives can seamlessly access funding, network, and receive strategic support for their projects.
We are committed to staying at the forefront of technological advancements, consistently integrating new AI and blockchain capabilities to enhance our platform's features and security. Our team's ongoing collaboration with experts in software development will drive continuous innovation, ensuring that our platform remains cutting-edge.
To sustain growth and relevance, we plan to diversify our services to cater to evolving industry needs. This includes expanding our offering to encompass not only equity financing but also additional services such as mentorship, advisory, and talent matchmaking.
In conclusion, our short-term focus is on developing, enhancing, and promoting the MVP, while our long-term goals involve establishing EquiBloc Creative Ventures as a holistic ecosystem that catalyzes growth, innovation, and financial access within Africa's creative industries.
Payment Address (Eth): 0xe07767abe76de87C1DbF7D9d281805d7678A0ce6
How did you hear about the Grants Program?
I learned about the Grants Program through industry sources and gained further insights from the Web3 Foundation website.
Additional Information :
Our team has already conducted extensive feasibility studies and global campaigns to gauge industry interest and gather support. While we are not currently able to share patent documents due to our ongoing development, we have three pending patents that will significantly enhance our project's innovation.
We have not received financial contributions from other teams at this stage. This application is our first grant proposal within the Web3 ecosystem.
We have not applied for previous grants related to this specific project. However, our team members have successfully secured private grants and funding for various projects in the past from Belraf Limited and Pompey Residence, showcasing our ability to execute and deliver on our commitments.
Our commitment to filling the void in equity financing within Africa's creative industries has driven us to this point, and we are excited to continue our journey with the support of the Grants Program. Thank you for considering our application.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

EquiBloc Creative Ventures.md.pdf

Hi David,
I wanted to let you know that we've uploaded a new file with our updated
project details and concrete deliverables. We've also incorporated our
entries into the default deliverables as you suggested. Thanks again for
your guidance!
Best regards,
Dazi
On 2023-08-16 12:29, David Hawig wrote:

@Noc2 requested changes on this pull request.
Thanks for your interest in our grants program. But could you add a
new file with your application rather than directly changing our
template? Also, we need concrete deliveries and see the mandatory
default deliverables of the template.
--
Reply to this email directly, view it on GitHub [1], or unsubscribe
[2].
You are receiving this because you authored the thread.Message ID:
@.***>
Links:
[1]
https://github.com/w3f/Grants-Program/pull/1911#pullrequestreview-1581112433
[2]
https://github.com/notifications/unsubscribe-auth/BB56BINF4NK5RMO3X6Z7H53XVT7QXANCNFSM6AAAAAA3SV2AS4

@Dazi01 please also revert the changes in the application-template.md doc.

Done.

Thanks for your questions; these are very insightful.
The Data Accumulation module plays a pivotal role in our strategy to
unleash the latent potential of the creative industry by aggregating
essential data. It collects information about various aspects of funded
creative projects, including expenses, collaborations, logistics, and
affiliations with organizations. This data is then securely stored on
the blockchain, ensuring its transparency and integrity.
Equity financing contracts are indeed ink! smart contracts. These
contracts outline the conditions under which creative projects obtain
funding through "cosmic credits." These credits serve as units of
measurement for equity financing, not actual cryptocurrencies. To
convert 'cosmic credits' into actual currency (USDT), a detailed project
plan and robust data must be provided. These smart contracts not only
facilitate fund disbursement but also stimulate data accumulation. When
creatives decide to convert their cosmic credits to USDT, they must
input intricate information about project plans, collaborators,
expenses, and organizational specifics. This data, along with the cosmic
credits, is recorded on the blockchain, creating a comprehensive and
current repository of information.
The Data Accumulation module and equity financing contracts complement
each other to ensure creatives receive funding while concurrently
contributing data that enhances our understanding of the creative
landscape. This data accumulation process aims to address the industry's
data gap and establish us as a reliable source of information. By doing
so, we bridge a significant void in equity financing within Africa's
creative sector.
Best,
Dazi
On 2023-08-20 02:28, David Hawig wrote:

@Noc2 requested changes on this pull request.
Thanks for the update. I have a few quick questions regarding the
application itself. What exactly is the DataAccumulation module doing,
and how is it storing the data? And what are equity financing
contracts? Are these ink! smart contracts?
--
Reply to this email directly, view it on GitHub [1], or unsubscribe
[2].
You are receiving this because you were mentioned.Message ID:
@.***>
Links:
[1]
https://github.com/w3f/Grants-Program/pull/1911#pullrequestreview-1585816132
[2]
https://github.com/notifications/unsubscribe-auth/BB56BIPIP4DNWEFVTRDUOY3XWG4ABANCNFSM6AAAAAA3SV2AS4

Thanks for your questions; these are very insightful.
The Data Accumulation module plays a pivotal role in our strategy to
unleash the latent potential of the creative industry by aggregating
essential data. It collects information about various aspects of funded
creative projects, including expenses, collaborations, logistics, and
affiliations with organizations. This data is then securely stored on
the blockchain, ensuring its transparency and integrity.
Equity financing contracts are indeed ink! smart contracts. These
contracts outline the conditions under which creative projects obtain
funding through "cosmic credits." These credits serve as units of
measurement for equity financing, not actual cryptocurrencies. To
convert 'cosmic credits' into actual currency (USDT), a detailed project
plan and robust data must be provided. These smart contracts not only
facilitate fund disbursement but also stimulate data accumulation. When
creatives decide to convert their cosmic credits to USDT, they must
input intricate information about project plans, collaborators,
expenses, and organizational specifics. This data, along with the cosmic
credits, is recorded on the blockchain, creating a comprehensive and
current repository of information.
The Data Accumulation module and equity financing contracts complement
each other to ensure creatives receive funding while concurrently
contributing data that enhances our understanding of the creative
landscape. This data accumulation process aims to address the industry's
data gap and establish us as a reliable source of information. By doing
so, we bridge a significant void in equity financing within Africa's
creative sector.
Best,
Dazi
On 2023-08-20 02:28, David Hawig wrote:

@Noc2 requested changes on this pull request.
Thanks for the update. I have a few quick questions regarding the
application itself. What exactly is the DataAccumulation module doing,
and how is it storing the data? And what are equity financing
contracts? Are these ink! smart contracts?
--
Reply to this email directly, view it on GitHub [1], or unsubscribe
[2].
You are receiving this because you were mentioned.Message ID:
@.***>
Links:
[1]
https://github.com/w3f/Grants-Program/pull/1911#pullrequestreview-1585816132
[2]
https://github.com/notifications/unsubscribe-auth/BB56BIPIP4DNWEFVTRDUOY3XWG4ABANCNFSM6AAAAAA3SV2AS4

Thanks for the update. I have a few quick questions regarding the application itself. What exactly is the DataAccumulation module doing, and how is it storing the data? And what are equity financing contracts? Are these ink! smart contracts?

Thanks for your questions; these are very insightful.
The Data Accumulation module plays a pivotal role in our strategy to
unleash the latent potential of the creative industry by aggregating
essential data. It collects information about various aspects of funded
creative projects, including expenses, collaborations, logistics, and
affiliations with organizations. This data is then securely stored on
the blockchain, ensuring its transparency and integrity.
Equity financing contracts are indeed ink! smart contracts. These
contracts outline the conditions under which creative projects obtain
funding through "cosmic credits." These credits serve as units of
measurement for equity financing, not actual cryptocurrencies. To
convert 'cosmic credits' into actual currency (USDT), a detailed project
plan and robust data must be provided. These smart contracts not only
facilitate fund disbursement but also stimulate data accumulation. When
creatives decide to convert their cosmic credits to USDT, they must
input intricate information about project plans, collaborators,
expenses, and organizational specifics. This data, along with the cosmic
credits, is recorded on the blockchain, creating a comprehensive and
current repository of information.
The Data Accumulation module and equity financing contracts complement
each other to ensure creatives receive funding while concurrently
contributing data that enhances our understanding of the creative
landscape. This data accumulation process aims to address the industry's
data gap and establish us as a reliable source of information. By doing
so, we bridge a significant void in equity financing within Africa's
creative sector.
Best,
Dazi

See our FAQ as well: https://grants.web3.foundation/docs/faq#what-activitiespositions-do-you-fund

@Dazi01 I'm closing this due to inactivity. LMK in case you'd like to improve the proposal, and we can reopen it.


Remove record meeting feature

https://trello.com/c/tIUj1fqn/748-3-remove-record-meeting-feature
Description
This feature was rarely used (8 meetings in total registered since go live, 3 of which were erroneously meetings instead of phone calls or comments), and has not been used by anyone since January 2020. Therefore we have decided to deprecate the feature.
Existing data will continue to work for now.

Checklist:

[x] Have you documented your changes in the pull request description?
[ ] Does the change present any security considerations?
[ ] Is any gem functionality overloaded? Eg: Devise controller methods being overloaded.
[ ] Has acceptance criteria been tested by a peer?
[x] Has the CHANGELOG been updated? (If change is worth telling users about.)

👍
Should we remove the rspec factory for the model at this point too?

I think we still need this as we still need to support the display of meeting data.


Crash report: Whomp's fortress, chomping flowers

Sorry I'm not super familiar with git. A pull request probably isn't the right place to report this, but hopefully you'll see it. In the level called whomp's fortress (1star door to the right of the main stairs), there is a crash that happens if you walk past one of the chomping flowers. If the flower wakes up and then you walk away, the entire app crashes and when you reenter the app is outs you at the start screen.

This repository is for the decompilation project of SM64, not the PC port. The repository for the PC port is at https://github.com/sm64-port/sm64-port ; you should probably report issues on that repository's discord server.

I was seeing this bug on the android app export of Mario 64. Where would be
the right place to report that?
On Sun, Sep 27, 2020, 12:06 PM nim from KA<EMAIL_ADDRESS>wrote:

This repository is for the decompilation project of SM64, not the PC port.
The repository for the PC port is at
https://github.com/sm64-port/sm64-port ; you should probably report
issues on that repository's discord server.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/n64decomp/sm64/pull/49#issuecomment-699675111, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABTASOJWNW6AETKZFCEB5J3SH6EMNANCNFSM4R3ALIQQ
.

Not sure where the right place is. Try the repository that nim linked, though.


common: temporarily disable DHE

until make it possible to use generated DH parameters per installation.
speidy concern about using static DH parameters:
https://github.com/neutrinolabs/xrdp/commit/1690950cc89220366a4dea0495a6948b2f248c33#r27897446

Lets merge this for now, it also breaks compatibility becuase of OpenSSL 1.1.0 API changes

oh and we should #if 0 the function get_dh2236() as well so xrdp builds ok with newer gcc.

Okay, will do it  later.

SSL_CTX_set_dh_auto is a good idea for openssl 1.1.0 and newer, very simple, no user interaction needed. But I don't get what do you mean with "add a backport". Do you mean use it with older openssl versions?
Also a small note: is SSL_CTX_set_dh_auto just going to use precomputed keys anyway? You cannot generate DH keys on the fly, it takes too long. To my best understanding even Apache httpd mod_ssl uses the builtin openssl per-generated keys, when a dhparam is not provided (note: it is provided inside the cert file, which basically means almost nobody even knows it's there). See
https://github.com/apache/httpd/blob/2b9e9b4c4226c22d9f5c489661507e7547de051c/modules/ssl/ssl_engine_init.c#L108

Regarding the next release, I'm going to disable non-EC DHE because speidy concerns about static DH parameters. I think static DH params are OK as I mentioned before [1] but not 100% sure.
Also, I agree with enricotagliavini overall. To make per-install DH params will resolve concern about static DH params but I don't think spending time on that is worth the effort. I don't object doing that but I don't because ECDHE is enough at least in my case.
[1] https://github.com/neutrinolabs/xrdp/commit/1690950cc89220366a4dea0495a6948b2f248c33#r27899026


refactor: rename Spec to the Intent

What type of PR is this?
/kind refactor

What this PR does / why we need it:
rename Spec to the Intent
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Additional documentation e.g., design docs, usage docs, etc.:

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

41 of 50 (82.0%)  changed or added relevant lines in 25 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.07%) to 75.536%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/cmd/apply/options.go
2
3
66.67%

pkg/engine/operation/diff.go
0
1
0.0%

pkg/engine/operation/parser/spec_parser.go
0
1
0.0%

pkg/engine/runtime/terraform/tfops/workspace.go
0
1
0.0%

pkg/generator/appconfiguration/generator/monitoring/monitoring_generator.go
1
3
33.33%

pkg/cmd/spec/generator.go
3
6
50.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.07%

Covered Lines:
6938

Relevant Lines:
9185

💛  - Coveralls


VPC Flow Log Template

This PR implements a CloudFormation template for deploying VPC flow logs into member accounts.

Hold off merge until e2e test.

Hold off merge until e2e test.

Successful run 18/11


chore: update initial schema generation guide

What kind of change does this PR introduce?
Bug fix
What is the new behavior?

update initial schema generation guide
fix analytics startup due to missing schema

Additional context
Add any other context or screenshots.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 60.602%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4127

Relevant Lines:
6810

💛  - Coveralls


Add Support for Tracing

Context
The tracing crate enables more robust instrumentation of Rust programs compared to basic logging. With this patch, we introduce the tracing crate into AKD and only enable it when the tracing feature is specified. By default, the feature is disabled and we continue to leverage basic logging.
In addition to adding tracing based logging and instrumentation throughout the akd lib (i.e. not akd_core), various grammatical and organizational improvements were made in areas where tracing was being added. Notably, the log_metrics functions which exist throughout the storage layer were updated to simply log with info level instead of taking an argument to specify the level. Rationale being that the log_metrics functions are only called when the runtime_metrics feature is enabled and info is a fair median to assume.
Testing
Since no major functional changes were made, the changes were tested via existing automated tests with various different feature flags being passed to toggle tracing on and off.

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

Project coverage is 87.91%. Comparing base (3ce5335) to head (3f18b6b).
Report is 18 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #453      +/-   ##
==========================================
- Coverage   88.61%   87.91%   -0.71%
==========================================
  Files          39       38       -1
  Lines        9109     8192     -917
==========================================
- Hits         8072     7202     -870
+ Misses       1037      990      -47

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


[Bug]fix: split autoslim different checkpoint has equal model size

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
autoslim get subnet by split_checkpoints is wrone.
Modification
module.weight = nn.Parameter(temp_weight.data.clone())
module.bias = nn.Parameter(module.bias.data[:out_channels].clone())

BC-breaking (Optional)
Does the modification introduce changes that break the backward compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here and update the documentation.
Checklist
Before PR:

[x] Pre-commit or other linting tools are used to fix the potential lint issues.
[x] Bug fixes are fully covered by unit tests, the case that causes the bug should be added in the unit tests.
[x] The modification is covered by complete unit tests. If not, please add more unit tests to ensure the correctness.
[x] The documentation has been modified accordingly, like docstring or example tutorials.

After PR:

[x] If the modification has potential influence on downstream or other related projects, this PR should be tested with those projects, like MMDet or MMSeg.
[x] CLA has been signed and all committers have signed the CLA in this PR.

Hi @Hiwyl, thank you very much for your pr.
OpenMMLab use pre-commit hook to avoid issues of code style.
This PR currently fails lint checks.
You can use the following two commands to get started with the pre-commit hook quickly.
pip install pre-commit
pre-commit run --all-files

The installation of pre-commit may be affected by the network.
If you are inconvenient to use pre-commit, you can contact us, and my colleagues can directly fix the lint in your branch.

Has been updated.

LGTM if passed CI


Building a JVM in Rust

Hi all,
I've been exploring this project, and I find it fascinating! I'm currently learning Rust, and I would love to build a JVM in Rust, inspired by what you've done here with Go. However, I'm still developing my knowledge of both Rust and JVM internals.
Could you recommend any resources, books, or videos that would help me deepen my understanding? Any guidance on how to approach building a JVM, particularly the core components to focus on, would be much appreciated.
Thanks in advance for your advice and for sharing such an interesting project!

hello，已经收到了~


Wrong subtitles

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I remove or skip any mandatory* field

Checklist

[X] I'm asking a question and not reporting a bug or requesting a feature
[X] I've looked through the README
[X] I've verified that I'm running yt-dlp version 2023.01.06 (update instructions) or later (specify commit)
[X] I've searched the bugtracker for similar questions including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Please make sure the question is worded well enough to be understood
For some reason the subtitles that I download are all wrong and fked up
Also... is yt-dlp not able to handle image based subtitles?
Provide verbose output that clearly demonstrates the problem

[ ] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

The command I used was
yt-dlp --merge-output-format mkv --write-auto-sub -f "bestvideo+bestaudio[ext=m4a]/best" https://youtu.be/73gyp4i7Qeo```

The subtitles in the output are just all messed up....

Do not abuse the "Question" template to post incomplete bug reports.
Properly fill out an appropriate issue form


go1.9: Bump go1.9 default to go1.9

Should the 1.8 refs in the README be updated as part of this?

(similar to https://github.com/heroku/heroku-buildpack-go/pull/173)

@danp Fixed.


Mend: add missing postinstall script

Hey, I just made a Pull Request!
Added missing postinstall script to the mend workspace.
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Can't merge, but I can confirm that almost all workspaces has this setup.

We are looking at a few options around this right now before we merge this one.

sorry @NormanWenzelWSS, I don't think this PR will help as we have an issue with releases at the moment. But https://github.com/backstage/community-plugins/pull/1913 will definitely help releasing your plugin.


Need to upgrade std for Deno 1.2.0

There seems some breaking change on Deno from 1.1.x to 1.2.0.
It needs to upgrade std from 0.60.0 or before to 0.61.0.

[ ] denofunc
[ ] deno-zip
[x] oak
https://github.com/oakserver/oak/issues/200

Fixed with https://github.com/anthonychu/azure-functions-deno-worker/commit/0d4d073a1903c2dd9623c40323e8a516a6d6c196

Thanks @anthonychu !


Typescript bug

With the latest update, I am now getting the following error message:
[tsc] node_modules/@material/mwc-linear-progress/mwc-linear-progress-base.d.ts(1,23): error TS2688: Cannot find type definition file for 'resize-observer-browser'.
[tsc] node_modules/@material/mwc-linear-progress/mwc-linear-progress-base.d.ts(35,31): error TS2304: Cannot find name 'ResizeObserver'.

This should be fixed in 19.0.1


Avoid import from resource_registry at top of file

I saw an issue about this, and since I had just done a similar solution for DAB RBAC I wanted to just go in and try to make it look more standard.
For the root problem, I might need some help understanding how galaxy_ng feature flags work.
https://github.com/ansible/galaxy_ng/blob/2f19483e1a7564afece88557833119969e255857/galaxy_ng/app/dynaconf_hooks.py#L67
This linked code sure strongly suggests that, in some cases, the resource_registry app might not be installed. If that's the case, then this would likely be the right kind of fix.

I tried to do this as a @property but the Hub class doesn't directly subclass, so that's not so obvious, there's not really a big benefit from code reuse. So I set it back to the original (fairly dumb) method.

If we are not in a rush for this it would be nice if we can up the coverage just a bit.

I tried. I wound up adding some tests, but they're much more marginal.
Looking at it for a few minutes, I realized that there is no way to easily solve the problem of joint testing with galaxy_ng. That is a big ball of yarn that I will not be able to help with efficiently right now. I already had some similar tests, but this gets more of the new method interface directly. It's something.

This will probably become defunct with https://github.com/ansible/django-ansible-base/pull/477 changes


Update global-storage-operators.md

Description
Fixed syntax error: added (a) in borrow_global(a).g
Also fixes pnpm fmt issues.
Checklist

Do all Lints pass?

[x] Have you ran pnpm spellcheck?
[x] Have you ran pnpm fmt?
[x] Have you ran pnpm lint?

Thanks, can you ensure the same is in nextra?

Of course! Just did.


Splunk native support #1698

fixes https://github.com/apache/camel-quarkus/issues/1698
Requires https://github.com/apache/camel/pull/5217 to be merged (currently approved)
Tests use Splunk server with free licence started via docker- see SplunkTestResource .

new GenericContainer("splunk/splunk:8.1.2")
.withEnv("SPLUNK_LICENSE_URI", "Free")

As is stated here,

If you want to run Splunk Enterprise to practice searches, data ingestion, and other tasks without worrying about a license, Splunk Free is the tool for you.

free version version could be used without any consequence. But I'd like to mention it here, for the case, that I'm wrong and we should not use it.
[ ] An issue should be filed for the change unless this is a trivial change (fixing a typo or similar). One issue should ideally be fixed by not more than one commit and the other way round, each commit should fix just one issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful and properly spelled subject line and body. Copying the title of the associated issue is typically enough. Please include the issue number in the commit message prefixed by #.
[ ] The pull request description should explain what the pull request does, how, and why. If the info is available in the associated issue or some other external document, a link is enough.
[ ] Phrases like Fix # or Fixes # will auto-close the named issue upon merging the pull request. Using them is typically a good idea.
[ ] Please run mvn process-resources -Pformat (and amend the changes if necessary) before sending the pull request.
[ ] Contributor guide is your good friend: https://camel.apache.org/camel-quarkus/latest/contributor-guide.html

@JiriOndrusek you'll need to rebase on the latest camel-master. I had to force push the branch to fix some issues.

@jamesnetherton  thanks, It's rebased now

Test failure is caused by some problems with maven:

Could not transfer artifact com.google.guava:guava:jar:14.0.1 from/to central (https://repo.maven.apache.org/maven2)

@aldettinger Thanks for the hints. It helped a lot and now the code looks much better. All requested changes are fixed.


⚠ Bofrost.nl has degraded performance

In 72b4bf1, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 2813 ms

Resolved: Bofrost.nl performance has improved in af28be0 after 12 minutes.


process.extractBests and usage of __str__

I am trying to drop-in replace a project that depends on the last version of fuzzywuzzy prior to the name change. This is needed after hitting this issue.
The project uses process.extractBests.  I noticed that rapidfuzz does not include process.extractBests.
Is process.extract a drop in replacement for that old function?
I tried using process.extract and realized that the project was relying on the __str__ of objects passed into the choices argument being read.  Later in the code, the variable is used like an object.  (this allowed the dev to easily use the object and refer to the string for comparison)
rapidfuzz does not seem to look at a given __str__ for an object.  Is this on purpose? Or perhaps FW should not have done this?
I mention the two above because I believe the goal is for the FW api to be fully available in RF. I do not know if the above use of the FW api was unusual or an anti-pattern though.

Thank you for that feedback, Max!
I'll have another run at this, and if I run into difficulty re-open this issue. I saw #333 and appreciate that, I had seen #26 and presumed the function previously existed but was obviated.


Add atmega168 feature to target ATmega168 chip running with its internal 8MHz oscillator

I'm working on a project based on an ATmega168 chip without an external oscillator and therefore using its own internal 8MHz oscillator.
These changes introduce a new feature to be able to target this chip.
However, the changes made in the PR for adding an internal-clock feature (https://github.com/Rahix/avr-hal/pull/443) may be a better way to achieve what I want. With this I could use both the 'nano168' and 'internal-clock' features to get the same result.

You are using the ATmega168 directly, instead of a prebuilt Arduino/SparkFun/etc. dev-board, right?  For such situations, you shouldn't use arduino-hal and instead depend on atmega-hal directly.  That way, you are not bound to a specific clock selection or similar.
Fortunately for you, someone is currently contributing examples of how to use atmega-hal directly.  See PR #524.


Torus: If user closes login modal, we display a modal without useful information.

Since this is an actual error case, we should either display something real here, or just go back to the normal page as if you never tried to log in. I'm pretty sure this is just a dev/debug message but it may need to be handled.
I think we should just assume this was a chosen close and not show any error.
@andrewdamelio can you remove?

for all errors from the sdk or just the one about clicking decline?

Specifically clicking decline / closing the window. Other SDK errors we should probably still show with some better copy above it.
something like:
There was an error while attempting to log in with {{ wallet }}. Please try again, and if it is still not working checkout the help center for logging in.

Error: {{ error_message }}

@Chwy5 thoughts?

Sound good to me....I would leave it short
There was an error while attempting to log in with {{ wallet }}. Please try again.


fix gh200 tests on main

tested at https://buildkite.com/vllm/ci/builds/10786#0193d218-43c9-497e-8925-0a498b7f7220


install with brew?

Hi I can't get it to work yet (how to install?), possible to get a brew install command?

Hi @strages,
There is currently no brew (OSX) or any other packet (linux, bsd) available.
What you need to do is clone the repository:
git clone https://github.com/cytopia/ffscreencast
cd ffscreencast

# copy binary to system
sudo cp bin/ffscreencast /usr/local/bin
# or to your local bin dir (if it exists)
cp bin/ffscreencast ~/bin

During the first start it will also create a configuration file in: ~/.config/ffscreencast/ffscreencastrc where you can alter default values.

Anybody willing to add this to homebrew?

Brew install command added  brew install cytopia/tap/ffscreencast
Still awaiting official homebrew package (brew install ffscreencast). Hopefully it will be added soon.

nice


Wrong PointLight2D position on parallax layers when camera is active

Godot version
v4.0.alpha12.official [2c11e6d9e]
System information
macOS, Linux and Windows 10
Issue description
The PointLight2D position on parallax layers is off when a camera is active.
In my example, a flashlight is attached to the player.
When camera is disabled the light illuminate the parallax layer at the right position:

When camera is enabled the light position is off:

Video of the minimal reproduction project:
https://user-images.githubusercontent.com/1422403/179389256-7b54426c-4857-4525-87da-0ed712e618e9.mov
Steps to reproduce
How to use the minimal reproduction project:

'arrows' to move player
'enter' to toggle on/off the camera

Minimal reproduction project
parallax-light2d-camera-bug.zip

Can you reproduce this with the same setup on 3.4.4?

@Calinou on 3.4.4 it works correctly.
I found this issue while porting a project from 3.4 to 4.0


No password when calling the eth_sendTransaction RPC method

Now we extract wallet data on every request, not permanently ('unlock' feature), therefore we need also a wallet password.

@splix Should we hide the password in logs, it can be not so simple?

For example we can add it similar to https://github.com/paritytech/parity/wiki/JSONRPC-personal-module#personal_sendtransaction

@splix we have three possibilities: just add a password as additional parameter to JSON, use HTTP POST header, or HTTP POST Authorization-Header?

HTTP Authentication: Basic and Digest Access Authentication

But another way to 1. generate session secret key between wallet and connector and 2. use X-KeyHmac to encode passphrase.

@elaineo can you please add a new input field for passphrase and include it in JSON RPC request as  X-Passphrase http header in base64 encodded format?

@dulanov maybe it's better to reuse standard Authorization header?

@splix I think that would be preferable too

PR #44

CORS support both variant - in preflight request (OPTION) we can return which HTTP Headers is suported by Access-Control-Allow-Headers or by Access-Control-Allow-Credentials: true declare basic authentification, so i will try to patch jsonrpc to return that attribute (Access-Control-Allow-Credentials: true) for CORS preflight request, details you can find (here)[https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS].

An opened issue in jsonrpc crate - https://github.com/paritytech/jsonrpc/issues/114

@elaineo that issue is actual only for emerald-rs, not for wallet ;)


Support multiple temporary folders; Support tmp folder on class level.

Multiple temporary folders are supported by using the ParameterContext
as key of the Store.

Do not destroy temporary folder prematurely when used on class level
(@BeforeAll), instead of method level (@BeforeEach). This is done by
implementing ClosableResource, which requires JUnit Jupiter at version
5.1.

Further Comments
Sorry for having two different changes in one pull request. I just wanted to give back my local changes to the extension, without putting too much work into it. Feel free to merge or to close :)
By depending on version 5.1 of JUnit Jupiter, this drastically simplifies the implementation of the TemporaryFolderExtension, as TemporaryFolder.close() now automatically gets called when the ExtensionContext dies. Before, the temporary folder got destroyed on @AfterEach, which was a problem when the folder was used at class level by the unit test.
I deleted the TemporaryFolderExtensionMetaTest, because it tests removed methods of the extension and I was too lazy to write a test for the changes I did to the extension.
By using the ParameterContext as the key of the store, multiple instances of TemporaryFolder are now supported, as the context is different for each parameter index.
Again, feel free to merge or not merge any of my changes or be inspired by them :)

Coverage decreased (-0.07%) to 97.396% when pulling 895c3e43cce1a89459117068c7f8c424b8359235 on ChristianCiach:master into 29bc44c8d6b2f8bdc629d7660b1477197797cd29 on glytching:master.

Thanks for the PR.
Are there any tests covering this change? If I understand the change correctly then I'd expect to see tests covering the following scenarios:

When declaring a class level TemporaryFolder ...

The same instance is used by all tests in the class
This instance is destroyed after execution of the test case

When declaring a method level TemporaryFolder ...

This instance is destroyed after execution of the test method

@glytching See my edited comment above. Sorry, I won't add unit tests for the changes. I did these changes for work and just wanted to give back my modifications without additional work on my side.

Ok, I'll take it from there.
Thanks again.

Covered by https://github.com/glytching/junit-extensions/pull/12.
Thanks for your help.


Quick deprecated patch

Update deprecated values, update lazy load & set width / height

I signed the CLA, just need to re-run check


Priority: Get datastore to drop files that are no longer published in the Registry

Describe the bug
Files which have been removed from the Registry should also be removed from the Datastore.
There are example of USAID's file e.g. for Brunei and Canada that are no longer published.
However, they are in the datastore and are therefore still being received by the IATI Validator and getting a validation result
To Reproduce
Steps to reproduce the behavior:

Go to https://iatidatastore.iatistandard.org/api/datasets/7447/?format=json
Click on see brunei file details
Go to the IATI Registry: https://www.iatiregistry.org/publisher/usaid?q=brunei&sort=metadata_modified+desc
See that no file exists

Expected behavior
I expect the datastore to reflect the data present in the IATI Registry. If a file is removed, the corresponding data should also be removed from the datastore.

Another instance of this is SIDA's 389.xml file.

Another instance of this is SIDA's 389.xml file.

Planned for January 2-3 days.

Planned for January 2-3 days.

Just wondering if this is close to completion? The retaining of old files makes it very difficult to assess whether the DS has refreshed. For example, if a publisher's files start failing schema validation and not being refreshed in the DS, the DS is still retaining the old data. Then if the publisher fixes the issue and the file starts to pass schema validation, it is very difficult to check as to whether the data has actually then refreshed in the DS. As a data user, there needs to be a clear line here so happy this is being resolved but would love an update! Thanks!

I will be picking up the ticket soon, an intern worked on this briefly but did not finish before the end of their internship, I'll be contacting them and seeing what the state of the objective is!

Will be picked up today

So, the PR is done, but will only be merged once the new function from #2561 is

Thanks for the update @siemvaessen. Please can we leave the issue open until it's live on production? Then the tech team can sign off, issue gets closed and we pay the invoice :)


Windows: flutter upgrade: now flutter 'command not found' ... flutter gone!

I can't do a flutter doctor because flutter is gone.

Things to try:
1.Open the folder where you have installed flutter
2.Open Terminal , try running flutter doctor, if that works, add the folder to path again

We're closing this issue because it seems to be a question or request for help rather than a clearly reproducible bug, regression or new feature request.
Good places to ask questions or work through problems where you're more likely to get a fast response include:

Stack Overflow
Gitter
Flutter Community Slack

Thanks for using Flutter!


⚠ Bofrost.lu has degraded performance

In 11cac4b, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1719 ms

Resolved: Bofrost.lu performance has improved in 4f81b52 after 6 minutes.


License Info missing

There's no license info here, and not sure if this has to do with the MetaMask license fiasco or not. It's a cool project, but really a nonstarter for anyone to use safely from a legal perspective if it doesn't have a license.
Soruce: https://choosealicense.com/no-permission/
So would be nice to know the stance and planned roadmap of this project, or better yet just a license.

missing license file added, MIT
let me know what you think of lavamoat @D-Nice

missing license file added, MIT
let me know what you think of lavamoat @D-Nice


[wt] Fix port for Android and iOS

Upstream PR: https://github.com/emweb/wt/pull/206

[x] Changes comply with the maintainer guide
[ ] SHA512s are updated for each updated download
[ ] The "supports" clause reflects platforms that may be fixed by this new version
[ ] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

All features are tested successfully in the following triplet:
x86-windows
x64-windows
x64-windows-static

The usage test passed on x64-windows (header files found):
wt provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(wt CONFIG REQUIRED)
    # note: 4 additional targets are not displayed.
    target_link_libraries(main PRIVATE Wt::Wt Wt::Dbo Wt::HTTP Wt::Test)

There has been no response from upstream for three months, so this PR is continued.

I think we could merge this under our cooldown period rules but I don't think the patch is correct. I left comments in the upstream PR.

(I don't think we need to give upstream an entire month for subsequent changes)

The upstream merged https://github.com/emweb/wt/pull/206 last week, please continue your PR.

Ping @bold84

Closing this PR since it seems that no progress is being made. Please ping us to reopen if work is still being done. Replaced by https://github.com/microsoft/vcpkg/pull/38063.


Thumbnail not updated

I have a 2K doorbell (T8210).
When the doorbell rings the proper events are generated. The picture (camera.doorbell) is not updated however.
It only shows the latest thumbnail when I restart Home Assistant.
This issue was also mentioned in Bropat's repo (closed because it works a designed).
The image is retrieved when the ring event is raised, however the backend is not serving the picture because it's not ready yet.
It it possible to make configurable delay and/or retry method while retrieving the thumbnail?
The image.doorbell_event_image is updated properly.....

whenever the image is downloaded by add-on, it sends an update notification to integration and integration is fetching the new one. If there is a delay (and I know there is some), we cannot fix it.
what do you want to retry exactly because everything is updated properly and eventually.

The only problem that I have right now is, that the camera.doorbell entity is not updated with the latest image.
You probably can replace the camera.doorbell image with image.doorbell_event_image if it originates from the same event.

I have the same issue here with version 8 (latest). The thumbnails are not updating unless I reload the integration. If it’s not reloaded, there is no image once the cameras have been activated.

All your push notifications (motion, person, ringing etc) are enabled?

A before and after of the two cameras I have, top image on HA dashboard is after I have loaded the integration, bottom image on HA dashboard is after I have clicked and looked at the live feed, then stopped the p2p stream. I have all necessary entities enabled, as far as I can tell.

When the first integration is loaded, the camera gets the latest event picture.
There is a separate sensor image.camera_last_event which holds any further event pictures from camera.
Camera itself holds last streaming frame after initial reload.
If you are using the YAML on readme file, it handles the transition between image and camera depending on streaming status. You are not using it

There is a separate sensor image.camera_last_event which holds any further event pictures from camera.
Camera itself holds last streaming frame after initial reload.

Where do you get the image.camera.last_event sensor? I searched for "image." in entities but only event image ones are shown:

I think I see something similiar - the images on the preview in HomeAssistant are rather obsolete
Example with the doorbell (S330 dual camera) even though that one has gotten alarms today - while the picture is from 2 days ago.

And I have had Home Assistant restartet 30 mins ago

The question is : is there a way to update the camera thumbnail with the last event_image ?


ci: set prerelease bit for GH releases

Description

Test

Additional Information
Tradeoff

Potential improvement

Superseded by https://github.com/kubewarden/audit-scanner/pull/72.


Issues deploying on EKS Windows Nodes

Hi team, in working with a user deploying to EKS Windows Node Groups, we ran into a few items that caused the deployment to fail using default chart values.
In order to deploy successfully we needed to make customizations to the chart, that like should be done by default, or included in documentation:
Update SecurityContext:
We had to update security context to use ContainerAdministrator user for windows.
 # To collect container logs and journald logs, it will run the agent as a root user.
  # To run it as non root user, uncomment below `securityContext` options.
  # Setting runAsUser and runAsGroup to a non root user enables an init container that patches group
  # permissions of container logs directories on the host filesystem to make logs readable by this non root user.

  securityContext:
    windowsOptions:
      runAsUserName: ContainerAdministrator

Then we had to create a new secret to not step on the old one. Although I assume in docs we could advise how to point to the existing one already created by first deploying the linux chart...
secret:
  create: true
  name: "splunk-otel-collector-windows"
  # Specifies whether secret provided by user should be validated.
  validateSecret: true

Thank you @matthewmodestino, I too had been struggling to make Windows on EKS work since 0.42 and this magic agent.securityContext value is indeed the fix.  It seems this should either be incorporated into the Windows documentation or keyed off the isWindows value since I don't think any other security options work under Windows.
I think the general direction for the secret problem is to fully deploy the collector chart twice, once for Linux and once for Windows (assuming you have both kinds of nodes).  That's most easily done by using a different namespace like "splunk-win", so this conflict won't happen and you can just manage them separately.
I also found that the default agent memory limit was just a bit too low under Windows to work reliably, although YMMV.

That's another good point, I did find that both the liveness probe guidance in the chart was key, and did see instances where upping the resource limits was helpful.
# This tells the kubelet that it should wait for x seconds before performing the first probe.
# This is required in case you are using windows worker nodes.
# It is recommended to keep it a 60-second window but it depends on cluster specification.
readinessProbe:
  initialDelaySeconds: 0
livenessProbe:
  initialDelaySeconds: 0

@matthewmodestino thanks for reporting this. I've created another issue for secret name conflict https://github.com/signalfx/splunk-otel-collector-chart/issues/439

@atoulme I think the bug is fixed and windows containers should be running for EKS. I think we can close this.

@VihasMakwana thanks for completing this ticket, closing this ticket.


Duplicate toasts from notebook format on save

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

VS Code Version:
Version: 1.78.0-insider (user setup)
Commit: 3e0b354932b8ddeb099c68ed3b7dfac25350dde2
Date: 2023-04-06T05:20:25.265Z
Electron: 22.4.3
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.25330
Sandboxed: Yes
OS Version: Windows 11

Steps to Reproduce:

Enable the setting Notebook › Format On Save with latest Python (v2023.7.10961009) and Jupyter (v2023.4.1000961023) pre-releases
ctrl+s in a notebook
Receive what appear to be duplicate notifications

The reason this is occurring is due to format request for each cell. Typically there is one file that user triggers formatting, in the notebook case formatting is triggered for each cell. So, we show the first prompt (to switch to extensions), then when formatting is called the second time, it detects that we are already waiting on user for the first prompt, we fall back to old behavior. Old code, looks for black doesn't find it show it shows its prompt.

Fixed via https://github.com/microsoft/vscode-python/pull/21138


AttributeError: 'VisionTransformer' object has no attribute 'seg_num'

请教各位，训练过程没问题，测试报属性错误：
$ CUDA_VISIBLE_DEVICES=3 python main.py -c applications/PP-Care/configs/timesformer_MRI.yaml --test -w "./output/TimeSformer_MRI/TimeSformer_MRI_best.pdparams"
/home/yxs/PaddleVideo-develop/paddlevideo/loader/pipelines/augmentations_ava.py:24: DeprecationWarning: NEAREST is deprecated and will be removed in Pillow 10 (2023-07-01). Use Resampling.NEAREST or Dither.NONE instead.
'nearest': Image.NEAREST,
/home/yxs/PaddleVideo-develop/paddlevideo/loader/pipelines/augmentations_ava.py:25: DeprecationWarning: BILINEAR is deprecated and will be removed in Pillow 10 (2023-07-01). Use Resampling.BILINEAR instead.
'bilinear': Image.BILINEAR,
/home/yxs/PaddleVideo-develop/paddlevideo/loader/pipelines/augmentations_ava.py:26: DeprecationWarning: BICUBIC is deprecated and will be removed in Pillow 10 (2023-07-01). Use Resampling.BICUBIC instead.
'bicubic': Image.BICUBIC,
/home/yxs/PaddleVideo-develop/paddlevideo/loader/pipelines/augmentations_ava.py:27: DeprecationWarning: BOX is deprecated and will be removed in Pillow 10 (2023-07-01). Use Resampling.BOX instead.
'box': Image.BOX,
/home/yxs/PaddleVideo-develop/paddlevideo/loader/pipelines/augmentations_ava.py:28: DeprecationWarning: LANCZOS is deprecated and will be removed in Pillow 10 (2023-07-01). Use Resampling.LANCZOS instead.
'lanczos': Image.LANCZOS,
/home/yxs/PaddleVideo-develop/paddlevideo/loader/pipelines/augmentations_ava.py:29: DeprecationWarning: HAMMING is deprecated and will be removed in Pillow 10 (2023-07-01). Use Resampling.HAMMING instead.
'hamming': Image.HAMMING
Warning! No module named 'paddlenlp', [paddlenlp] package and it's dependencies is required for ActBERT.
Warning! No module named 'lmdb', [lmdb] package and it's dependencies is required for ActBERT.
Warning! No module named 'paddlenlp', [paddlenlp] package and it's dependencies is required for ActBERT.
Warning! No module named 'lmdb', [lmdb] package and it's dependencies is required for ActBERT.
Warning! No module named 'paddlenlp', [paddlenlp] package and it's dependencies is required for ActBERT.
[01/26 16:17:00] DATASET :
[01/26 16:17:00]     batch_size : 4
[01/26 16:17:00]     num_workers : 4
[01/26 16:17:00]     test :
[01/26 16:17:00]         data_prefix :
[01/26 16:17:00]         file_path : /home/yxs/PaddleVideo-develop/data/PP-Care/datasets/AV133/test_res2.txt
[01/26 16:17:00]         format : MRIDataset
[01/26 16:17:00]     test_batch_size : 8
[01/26 16:17:00]     train :
[01/26 16:17:00]         data_prefix :
[01/26 16:17:00]         file_path : /home/yxs/PaddleVideo-develop/data/PP-Care/datasets/AV133/train_res2.txt
[01/26 16:17:00]         format : MRIDataset
[01/26 16:17:00]     valid :
[01/26 16:17:00]         data_prefix :
[01/26 16:17:00]         file_path : /home/yxs/PaddleVideo-develop/data/PP-Care/datasets/AV133/test_res2.txt
[01/26 16:17:00]         format : MRIDataset
[01/26 16:17:00] ------------------------------------------------------------
[01/26 16:17:00] GRADIENT_ACCUMULATION :
[01/26 16:17:00]     global_batch_size : 64
[01/26 16:17:00] ------------------------------------------------------------
[01/26 16:17:00] METRIC :
[01/26 16:17:00]     name : CenterCropMetric_MRI
[01/26 16:17:00] ------------------------------------------------------------
[01/26 16:17:00] MODEL :
[01/26 16:17:00]     backbone :
[01/26 16:17:00]         attention_type : divided_space_time
[01/26 16:17:00]         depth : 12
[01/26 16:17:00]         embed_dim : 768
[01/26 16:17:00]         epsilon : 1e-06
[01/26 16:17:00]         img_size : 224
[01/26 16:17:00]         in_channels : 1
[01/26 16:17:00]         mlp_ratio : 4
[01/26 16:17:00]         name : VisionTransformer
[01/26 16:17:00]         num_heads : 12
[01/26 16:17:00]         patch_size : 16
[01/26 16:17:00]         pretrained : /home/yxs/PaddleVideo-develop/data/PP-Care/ViT_base_patch16_224_pretrained.pdparams
[01/26 16:17:00]         qkv_bias : True
[01/26 16:17:00]         seg_num : 8
[01/26 16:17:00]     framework : RecognizerTransformer_MRI
[01/26 16:17:00]     head :
[01/26 16:17:00]         in_channels : 768
[01/26 16:17:00]         name : TimeSformerHead
[01/26 16:17:00]         num_classes : 2
[01/26 16:17:00]         std : 0.02
[01/26 16:17:00] ------------------------------------------------------------
[01/26 16:17:00] OPTIMIZER :
[01/26 16:17:00]     learning_rate :
[01/26 16:17:00]         gamma : 0.9
[01/26 16:17:00]         learning_rate : 0.005
[01/26 16:17:00]         milestones : [20, 29]
[01/26 16:17:00]         name : MultiStepDecay
[01/26 16:17:00]     name : Adam
[01/26 16:17:00]     weight_decay :
[01/26 16:17:00]         name : L2
[01/26 16:17:00]         value : 5e-05
[01/26 16:17:00] ------------------------------------------------------------
[01/26 16:17:00] PIPELINE :
[01/26 16:17:00]     test :
[01/26 16:17:00]         decode :
[01/26 16:17:00]             name : MRIDecoder
[01/26 16:17:00]         sample :
[01/26 16:17:00]             linspace_sample : True
[01/26 16:17:00]             name : Sampler
[01/26 16:17:00]             num_seg : 8
[01/26 16:17:00]             seg_len : 1
[01/26 16:17:00]             valid_mode : True
[01/26 16:17:00]     train :
[01/26 16:17:00]         decode :
[01/26 16:17:00]             name : MRIDecoder
[01/26 16:17:00]         sample :
[01/26 16:17:00]             linspace_sample : True
[01/26 16:17:00]             name : Sampler
[01/26 16:17:00]             num_seg : 8
[01/26 16:17:00]             seg_len : 1
[01/26 16:17:00]             valid_mode : False
[01/26 16:17:00]     valid :
[01/26 16:17:00]         decode :
[01/26 16:17:00]             name : MRIDecoder
[01/26 16:17:00]         sample :
[01/26 16:17:00]             linspace_sample : True
[01/26 16:17:00]             name : Sampler
[01/26 16:17:00]             num_seg : 8
[01/26 16:17:00]             seg_len : 1
[01/26 16:17:00]             valid_mode : False
[01/26 16:17:00] ------------------------------------------------------------
[01/26 16:17:00] epochs : 30
[01/26 16:17:00] log_interval : 20
[01/26 16:17:00] log_level : INFO
[01/26 16:17:00] model_name : TimeSformer_MRI
[01/26 16:17:00] save_interval : 5
W0126 16:17:00.539693 27400 gpu_resources.cc:61] Please NOTE: device: 0, GPU Compute Capability: 7.5, Driver API Version: 11.0, Runtime API Version: 10.2
W0126 16:17:00.545255 27400 gpu_resources.cc:91] device: 0, cuDNN Version: 7.6.
Traceback (most recent call last):
File "main.py", line 144, in
main()
File "main.py", line 124, in main
test_model(cfg, weights=args.weights, parallel=parallel)
File "/home/yxs/anaconda3/envs/paddle/lib/python3.7/site-packages/decorator.py", line 232, in fun
return caller(func, *(extras + args), **kw)
File "/home/yxs/anaconda3/envs/paddle/lib/python3.7/site-packages/paddle/fluid/dygraph/base.py", line 354, in _decorate_function
return func(*args, **kwargs)
File "/home/yxs/PaddleVideo-develop/paddlevideo/tasks/test.py", line 88, in test_model
outputs = model(data, mode='test')
File "/home/yxs/anaconda3/envs/paddle/lib/python3.7/site-packages/paddle/fluid/dygraph/layers.py", line 930, in call
return self._dygraph_call_func(*inputs, **kwargs)
File "/home/yxs/anaconda3/envs/paddle/lib/python3.7/site-packages/paddle/fluid/dygraph/layers.py", line 915, in _dygraph_call_func
outputs = self.forward(*inputs, **kwargs)
File "/home/yxs/PaddleVideo-develop/paddlevideo/modeling/framework/recognizers/base.py", line 53, in forward
return self.test_step(data_batch)
File "/home/yxs/PaddleVideo-develop/paddlevideo/modeling/framework/recognizers/recognizer_transformer_MRI.py", line 68, in test_step
num_views = imgs.shape[3] // self.backbone.seg_num
File "/home/yxs/anaconda3/envs/paddle/lib/python3.7/site-packages/paddle/fluid/dygraph/layers.py", line 1123, in getattr
return object.getattribute(self, name)
AttributeError: 'VisionTransformer' object has no attribute 'seg_num'
请教各位，训练过程没问题，测试过程 报属性错误

训练使用的是PP-Care中的Timesformer模型，训练过程无问题，测试过程报错
测试代码：
python main.py -c applications/PP-Care/configs/timesformer_MRI.yaml --test -w "./output/TimeSformer_MRI/TimeSformer_MRI_best.pdparams"
报错：
AttributeError: 'VisionTransformer' object has no attribute 'seg_num'
自己排错是recognizer_transformer_MRI.py文件中 self.backbone.seg_num无seg_num属性，但yaml文件中有该参数
请问应该如何修改代码呢？

需要将yaml文件中的seg_num改成num_seg

@huangjun12 非常感谢您的指点，旧问题已解决。yaml文件已改，且将recognizer_transformer_MRI.py中test_step函数的seg_num改为num_seg，但产生了新问题：AssertionError: Input image size (8224) doesn't match model (224224).
自己排错是recognizer_transformer_MRI.py中test_step函数中的for循环中view的维度不对应vit.py中的维度，仍未解决
希望等得到您的进一步指点

CUDA_VISIBLE_DEVICES=2 python main.py -c applications/PP-Care/configs/timesformer_MRI_wr.yaml --test -w "./output/TimeSformer_MRI_8/TimeSformer_MRI_best.pdparams"
/home/yxs/PaddleVideo-develop/paddlevideo/loader/pipelines/augmentations_ava.py:24: DeprecationWarning: NEAREST is deprecated and will be removed in Pillow 10 (2023-07-01). Use Resampling.NEAREST or Dither.NONE instead.
'nearest': Image.NEAREST,
/home/yxs/PaddleVideo-develop/paddlevideo/loader/pipelines/augmentations_ava.py:25: DeprecationWarning: BILINEAR is deprecated and will be removed in Pillow 10 (2023-07-01). Use Resampling.BILINEAR instead.
'bilinear': Image.BILINEAR,
/home/yxs/PaddleVideo-develop/paddlevideo/loader/pipelines/augmentations_ava.py:26: DeprecationWarning: BICUBIC is deprecated and will be removed in Pillow 10 (2023-07-01). Use Resampling.BICUBIC instead.
'bicubic': Image.BICUBIC,
/home/yxs/PaddleVideo-develop/paddlevideo/loader/pipelines/augmentations_ava.py:27: DeprecationWarning: BOX is deprecated and will be removed in Pillow 10 (2023-07-01). Use Resampling.BOX instead.
'box': Image.BOX,
/home/yxs/PaddleVideo-develop/paddlevideo/loader/pipelines/augmentations_ava.py:28: DeprecationWarning: LANCZOS is deprecated and will be removed in Pillow 10 (2023-07-01). Use Resampling.LANCZOS instead.
'lanczos': Image.LANCZOS,
/home/yxs/PaddleVideo-develop/paddlevideo/loader/pipelines/augmentations_ava.py:29: DeprecationWarning: HAMMING is deprecated and will be removed in Pillow 10 (2023-07-01). Use Resampling.HAMMING instead.
'hamming': Image.HAMMING
Warning! No module named 'paddlenlp', [paddlenlp] package and it's dependencies is required for ActBERT.
Warning! No module named 'lmdb', [lmdb] package and it's dependencies is required for ActBERT.
Warning! No module named 'paddlenlp', [paddlenlp] package and it's dependencies is required for ActBERT.
Warning! No module named 'lmdb', [lmdb] package and it's dependencies is required for ActBERT.
Warning! No module named 'paddlenlp', [paddlenlp] package and it's dependencies is required for ActBERT.
[01/31 14:55:13] DATASET :
[01/31 14:55:13]     batch_size : 4
[01/31 14:55:13]     num_workers : 4
[01/31 14:55:13]     test :
[01/31 14:55:13]         data_prefix :
[01/31 14:55:13]         file_path : /home/yxs/PaddleVideo-develop/data/PP-Care/datasets/AV133/wrtest_res3.txt
[01/31 14:55:13]         format : MRIDataset
[01/31 14:55:13]     test_batch_size : 4
[01/31 14:55:13]     train :
[01/31 14:55:13]         data_prefix :
[01/31 14:55:13]         file_path : /home/yxs/PaddleVideo-develop/data/PP-Care/datasets/AV133/wrtrain_res3.txt
[01/31 14:55:13]         format : MRIDataset
[01/31 14:55:13]     valid :
[01/31 14:55:13]         data_prefix :
[01/31 14:55:13]         file_path : /home/yxs/PaddleVideo-develop/data/PP-Care/datasets/AV133/wrtest_res3.txt
[01/31 14:55:13]         format : MRIDataset
[01/31 14:55:13] ------------------------------------------------------------
[01/31 14:55:13] GRADIENT_ACCUMULATION :
[01/31 14:55:13]     global_batch_size : 64
[01/31 14:55:13] ------------------------------------------------------------
[01/31 14:55:13] METRIC :
[01/31 14:55:13]     name : CenterCropMetric_MRI
[01/31 14:55:13] ------------------------------------------------------------
[01/31 14:55:13] MODEL :
[01/31 14:55:13]     backbone :
[01/31 14:55:13]         attention_type : divided_space_time
[01/31 14:55:13]         depth : 12
[01/31 14:55:13]         embed_dim : 768
[01/31 14:55:13]         epsilon : 1e-06
[01/31 14:55:13]         img_size : 224
[01/31 14:55:13]         in_channels : 1
[01/31 14:55:13]         mlp_ratio : 4
[01/31 14:55:13]         name : VisionTransformer
[01/31 14:55:13]         num_heads : 12
[01/31 14:55:13]         num_seg : 8
[01/31 14:55:13]         patch_size : 16
[01/31 14:55:13]         pretrained : /home/yxs/PaddleVideo-develop/data/PP-Care/ViT_base_patch16_224_pretrained.pdparams
[01/31 14:55:13]         qkv_bias : True
[01/31 14:55:13]     framework : RecognizerTransformer_MRI
[01/31 14:55:13]     head :
[01/31 14:55:13]         in_channels : 768
[01/31 14:55:13]         name : TimeSformerHead
[01/31 14:55:13]         num_classes : 2
[01/31 14:55:13]         std : 0.02
[01/31 14:55:13] ------------------------------------------------------------
[01/31 14:55:13] OPTIMIZER :
[01/31 14:55:13]     learning_rate :
[01/31 14:55:13]         gamma : 0.9
[01/31 14:55:13]         learning_rate : 0.005
[01/31 14:55:13]         milestones : [20, 29]
[01/31 14:55:13]         name : MultiStepDecay
[01/31 14:55:13]     name : Adam
[01/31 14:55:13]     weight_decay :
[01/31 14:55:13]         name : L2
[01/31 14:55:13]         value : 5e-05
[01/31 14:55:13] ------------------------------------------------------------
[01/31 14:55:13] PIPELINE :
[01/31 14:55:13]     test :
[01/31 14:55:13]         decode :
[01/31 14:55:13]             name : MRIDecoder
[01/31 14:55:13]         sample :
[01/31 14:55:13]             linspace_sample : True
[01/31 14:55:13]             name : Sampler
[01/31 14:55:13]             num_seg : 8
[01/31 14:55:13]             seg_len : 1
[01/31 14:55:13]             valid_mode : True
[01/31 14:55:13]     train :
[01/31 14:55:13]         decode :
[01/31 14:55:13]             name : MRIDecoder
[01/31 14:55:13]         sample :
[01/31 14:55:13]             linspace_sample : True
[01/31 14:55:13]             name : Sampler
[01/31 14:55:13]             num_seg : 8
[01/31 14:55:13]             seg_len : 1
[01/31 14:55:13]             valid_mode : False
[01/31 14:55:13]     valid :
[01/31 14:55:13]         decode :
[01/31 14:55:13]             name : MRIDecoder
[01/31 14:55:13]         sample :
[01/31 14:55:13]             linspace_sample : True
[01/31 14:55:13]             name : Sampler
[01/31 14:55:13]             num_seg : 8
[01/31 14:55:13]             seg_len : 1
[01/31 14:55:13]             valid_mode : False
[01/31 14:55:13] ------------------------------------------------------------
[01/31 14:55:13] epochs : 30
[01/31 14:55:13] log_interval : 20
[01/31 14:55:13] log_level : INFO
[01/31 14:55:13] model_name : TimeSformer_MRI
[01/31 14:55:13] save_interval : 5
W0131 14:55:13.379593 38730 gpu_resources.cc:61] Please NOTE: device: 0, GPU Compute Capability: 7.5, Driver API Version: 11.0, Runtime API Version: 10.2
W0131 14:55:13.384462 38730 gpu_resources.cc:91] device: 0, cuDNN Version: 7.6.

imgs.shape =  [4, 8, 224, 224]
num_views = 224
0
view.shape =  [4, 8, 8, 224]

x.shape =   [4, 1, 8, 8, 224]
224
Traceback (most recent call last):
File "main.py", line 144, in
main()
File "main.py", line 124, in main
test_model(cfg, weights=args.weights, parallel=parallel)
File "/home/yxs/anaconda3/envs/paddle/lib/python3.7/site-packages/decorator.py", line 232, in fun
return caller(func, *(extras + args), **kw)
File "/home/yxs/anaconda3/envs/paddle/lib/python3.7/site-packages/paddle/fluid/dygraph/base.py", line 354, in _decorate_function
return func(*args, **kwargs)
File "/home/yxs/PaddleVideo-develop/paddlevideo/tasks/test.py", line 88, in test_model
outputs = model(data, mode='test')
File "/home/yxs/anaconda3/envs/paddle/lib/python3.7/site-packages/paddle/fluid/dygraph/layers.py", line 930, in call
return self._dygraph_call_func(*inputs, **kwargs)
File "/home/yxs/anaconda3/envs/paddle/lib/python3.7/site-packages/paddle/fluid/dygraph/layers.py", line 915, in _dygraph_call_func
outputs = self.forward(inputs, **kwargs)
File "/home/yxs/PaddleVideo-develop/paddlevideo/modeling/framework/recognizers/base.py", line 53, in forward
return self.test_step(data_batch)
File "/home/yxs/PaddleVideo-develop/paddlevideo/modeling/framework/recognizers/recognizer_transformer_MRI.py", line 79, in test_step
cls_score.append(self.forward_net(view))
File "/home/yxs/PaddleVideo-develop/paddlevideo/modeling/framework/recognizers/recognizer_transformer_MRI.py", line 32, in forward_net
feature = self.backbone(imgs)
File "/home/yxs/anaconda3/envs/paddle/lib/python3.7/site-packages/paddle/fluid/dygraph/layers.py", line 930, in call
return self._dygraph_call_func(inputs, **kwargs)
File "/home/yxs/anaconda3/envs/paddle/lib/python3.7/site-packages/paddle/fluid/dygraph/layers.py", line 915, in _dygraph_call_func
outputs = self.forward(inputs, **kwargs)
File "/home/yxs/PaddleVideo-develop/paddlevideo/modeling/backbones/vit.py", line 466, in forward
x = self.forward_features(x)
File "/home/yxs/PaddleVideo-develop/paddlevideo/modeling/backbones/vit.py", line 400, in forward_features
x, T, W = self.patch_embed(x)  # [BT,nHnW,F]
File "/home/yxs/anaconda3/envs/paddle/lib/python3.7/site-packages/paddle/fluid/dygraph/layers.py", line 930, in call
return self._dygraph_call_func(inputs, **kwargs)
File "/home/yxs/anaconda3/envs/paddle/lib/python3.7/site-packages/paddle/fluid/dygraph/layers.py", line 915, in _dygraph_call_func
outputs = self.forward(inputs, **kwargs)
File "/home/yxs/PaddleVideo-develop/paddlevideo/modeling/backbones/vit.py", line 284, in forward
f"Input image size ({H}{W}) doesn't match model ({self.img_size[0]}{self.img_size[1]})."
AssertionError: Input image size (8224) doesn't match model (224224).

def test_step(self, data_batch):
"""Define how the model is going to infer, from input to output."""
#print("test********************************************")
imgs = data_batch[0]
#print("test's imgs.shape = ", imgs.shape) # [4, 8, 224, 224]：4表示测试时的batch_size
    num_views = imgs.shape[2]     # self.backbone.seg_num
    #print("num_views =", num_views)
    cls_score = self.forward_net(imgs)
    return cls_score
    #cls_score = []
    #for i in range(num_views):
        #print(i)
        #view = imgs[:, :,  i * self.backbone.num_seg:(i + 1) * self.backbone.num_seg]
        #cls_score.append(self.forward_net(view))
    #cls_score = self.average_view(cls_score)
    #return cls_score

注释掉下面的代码即可（已解决）


Incorrect cursor positioning in TMemo on Android

Hi,
on Android using SKIA4Delphi in a TMemo the cursor is not moved at the end of line when Space is entered. This happens only on Android.
SK4D 3.2.0
D11

Hi @Iamjoosy, thank you very much for reporting the issue.
Are you trying to use Right-To-Left?
Is your TMemo's HorzAlign set to "Leading"?
I tested it here and it is working as expected.

Confirmed issue.

Hi @Iamjoosy, this issue was fixed in new version v3.3.0


[AIRFLOW-111] Include queued tasks in scheduler concurrency check

The concurrency argument in dags appears to not be obeyed because the
scheduler does not check the concurrency properly when checking tasks.
The tasks do not run, but this leads to a lot of scheduler churn.
Dear Airflow maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-111

Description

[x] Here are some details about my PR, including screenshots of any UI changes: We now check for queued tasks as well since they will soon run.

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:  TBD

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

cc: @bolkedebruin @plypaul @amaliujia

Codecov Report

Merging #2214 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2214      +/-   ##
==========================================
- Coverage   67.54%   67.54%   -0.01%
==========================================
  Files         142      142
  Lines       10846    10849       +3
==========================================
+ Hits         7326     7328       +2
- Misses       3520     3521       +1

Impacted Files
Coverage Δ

airflow/jobs.py
73.35% <100%> (ø)
:arrow_up:

airflow/models.py
86.89% <100%> (-0.04%)
:arrow_down:

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 c64e876...f02bf80. Read the comment docs.

One nit(tish), rest LGTM


repository not found in the readme.md

Hello, I think the link for the git repository in the readme.md isn't working :
Clonage dans 'software-mentions'...
Username for 'https://github.com': ...
Password for 'https://github.com': ...
remote: Repository not found.
fatal: dépôt 'https://github.com/kermitt2/software-mentions/' non trouvé```

Hello thanks ! Yes, typo, this is the current repository that has to be cloned. Corrected with 5c481b11fae1baadf9f4b9bee3f85ad5c4d75085

Thnak you !


Create NumsNotInArrayLeetcode448.java

this is amazing @avinash38143
thanks for the contribution in my repo and please share in social media and tag me on twitter


Remove signal twitch_ready

In twitch_service.gd signal twitch_ready; no longer exists since commit 506d05c

Its replaced with await TwitchService.setup();

Yes but the signal is still declared.

https://github.com/kanimaru/twitcher/commit/4f0e3967457541da213e7eb0f3b7b210b92b72be Thanks yeah xD forgot


Post-roll ended event

How to catch the event of the end of playing a post-roll?
player.on ('ended', function () {console.log ('Video is now ended');});
сalled twice - first before showing the post-roll, then after the end of the post-roll
https://docs.fluidplayer.com/docs/api/events/#ended

I've noticed this issue as well.
on('ended', function(){})  is called when a VAST pre/post roll finishes or if you click skip. Most of the time if we are using this function it's because we want to do something when the main video ends and not when the preroll ends. I can see how it would be useful to trigger it when the preroll ends too.

Created a ticket for this issue since it's still happening

@Barahten @adamstruve The events were not different for ads and the main video since they are just passing along the HTML5 video player event. As to not mess with the event handlers, I've added additional information to the callback attributes, so you can programatically check what is the source of the event.
You can check the docs here: https://docs.fluidplayer.com/docs/api/events/#additional-information
Please let me know if this fixes this issue

No answer from the reporter. Closing the ticket.


hexo theme dark‘s pull request

Check List
Please read and check followings before submitting a PR.

[x] I want to publish my theme on Hexo official website.

[x] I have read the theme publishing doc.
[x] name is unique.
[x] link URL is correct.
[x] preview URL is correct.
[x] preview URL web site is rendered correctly.
[x] Add a screenshot to source/themes/screenshots.
[x] Screenshot filename is same as value of name.
[x] Screenshot size is 800 * 500.
[x] Screenshot file format is png.

[ ] I want to publish my plugin on Hexo official website.

[ ] I have read the plugin publishing doc.
[ ] name is unique.
[ ] link URL is correct.

[ ] Others (Update, fix, translation, etc...)

Languages:
[ ] en English
[ ] ko Korean
[ ] pt-br Brazilian Portuguese
[ ] ru Russian
[ ] th Thai
[ ] zh-cn simplified Chinese
[ ] zh-tw traditional Chinese

@confuseder Hello, the repository https://github.com/confuseder/hexo-theme-dark cannot be accessed. Would you mind updating the link? Thanks!


global set_required=False overwrites local set_required=True

because of this line: https://github.com/dyve/django-bootstrap3/blob/ae460aa6bc23bb49e8b6b85e12617983a9c162f1/bootstrap3/forms.py#L167 there is no chance to set set_required to True on single forms/fields if the global setting is False. I would expect the global setting to set a default which can be overridden locally.
I'd make a pull request if you can confirm this is not intended behavior.

This settings will probably be gone or at least severely rewritten because of #337. I'd appreciate any insights you have on that issue.

Closing this one, please discuss at #337.


Migrate to new versioned and content APIs

LinkedIn’s Marketing APIs will be versioned from June 2022 and released under a new base path: https://api.linkedin.com/rest/
(https://learn.microsoft.com/en-us/linkedin/marketing/versioning?view=li-lms-2022-10)
Microsoft also published a guide: https://learn.microsoft.com/en-us/linkedin/marketing/integrations/community-management/contentapi-migration-guide

https://learn.microsoft.com/en-us/linkedin/marketing/versioning?view=li-lms-2023-05
Legacy (unversioned) Marketing APIs using the base path https://api.linkedin.com/v2/ will be available until June 30, 2023 when they will be sunset.

There seems to be no activity on this issue and from the 1st of July every application using this linkedin integration will stop working I suppose

I guess this repository is no longer maintained.

Although according to the linkedin developers account dashboard (products tab -> endpoints) the /v2/me has a new versioned version :D /rest/me, there's no versioning information on the authorization documentation page.

I can confirm this, I wrote to Linkedin Support via ZenDesk and had this response :
All oauth token calls are not yet migrated to /rest. You can continue using v2 calls until further notice.
https://learn.microsoft.com/en-us/linkedin/shared/authentication/authorization-code-flow?context=linkedin%2Fmarketing%2Fcontext&tabs=HTTPS1

/v2/me has a new /rest/me version, but the original /v2/me and /v2/clientAwareMemberHandles (used by the LinkedIn auth provider) will not be dismissed.
So I guess no changes are necessary for now.
We'll see in a few days I guess :wink:


Add note clearly indicating that SSO auth does not work in Word for Microsoft Teams (desktop client)

Based on this issue https://github.com/OfficeDev/office-js/issues/3291 there must be a clear note (in RED) indicating that SSO does not work with Word in Microsoft Teams.
When  I am solutioning for clients I heavily rely on proper documentation and notes. For the past month we solution an add-in based on the assumption from the official SSO documents that it works cross platform (Office online, Word Desktop, Microsoft Teams) until we have to find ourselves it does not.

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

ID: cb06c24b-9d11-9cc5-2e98-561601452638
Version Independent ID: abda21d9-6e80-8319-c56f-004658014e3c
Content: Enable single sign-on (SSO) in an Office Add-in - Office Add-ins
Content Source: docs/develop/sso-in-office-add-ins.md
Service: microsoft-365
Sub-service: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

@catmanjan if you ask me, I don't know :) . I am seeking for the same answer as you.

@VelinGeorgiev and @catmanjan , Thanks for bringing this to our attention. I apologize for the poor internal communication in Microsoft about the lack of support for getAccessToken when the Office application is opened with Edit in Teams. I will get the documentation updated to reflect this today.


add static page rails generator

This PR creates the generator requested in  #303
Hope this is helpful!

Not sure if these hound critiques are valid as I largely tried following convention within the project

failed to see new features weren't being added  :(

Hi @whatnotery thank you for contribution but this library is in maintenance mode, which means we will only accept bug fixes/dependencies updates contributions. We have other gems you can contribute to, if you're interested. This post shares some active ones. Thank you!


Docs update

On deployments I mention free commercial and change the styling around coiled to make it more consistent.
In FAQ I remove some things and update some links.

Minor edits, merging in 24 hours if there are no further comments


Add a licence to the project

I'd like to use this plugin within the organisation I work for and to do that it needs a licence attributed to it.
Please add a licence.
Thanks. (Cool plugin by the way)

https://github.com/Vektah/CodeGlance/blob/master/LICENCE

Many thanks.


[FX-677] Remove ForageConstants dependence on StopgapGlobalState

What
This PR is associated with removing ForageConstant.kt's dependence on StopgapGlobalState, part of the remaining cleanup work associated with Android 3.0
ForageConstant.kt's depended on StopgapGlobalState because of BASE_URL. However, BASE_URL is only directly consumed by ForageSDK, which means we make moving the related logic directly into ForageSDK by parsing the sessionToken to extract the baseUrl
Why

Test Plan

✅ and ❌. I added unit tests to ensure surface if any of the EncConfig baseUrls ever become malformed because we are unable to get the compiler's guarantee of non-null values or that it won't throw runtime errors. We had a thoughtful conversation about this below
❌ It's not necessary to manually test these changes as the CI tests will flag if there's an issue with these changes.

How
This can be rolled out once approved!

Current dependencies on/for this PR:

main

PR #126   👈

This stack of pull requests is managed by Graphite.

Do you have thoughts/concerns about the coverage diff CI checks across this stack reporting a bit under 80% (76, 77, ...) – if we're aiming to increase the overall code coverage?

You're getting excited here talking about possibly needing to add more tests haha 🤤
Just to make sure that I am on the same page as you, here is my understanding of the CI diff:

All of these files have 100% coverage:

EncryptionKeyService.kt
MessageStatusService.kt
PaymentMethodService.kt
PaymentService.kt
TokenizeCardService.kt

and ForageSDK has 0% coverage which averages 77% coverage for the diff.
With that as my understanding, my take is that yes it would be awesome to have 80% or more coverage on ForageSDK! I think this may be best done in a follow on PR though. The reason I'd say a follow on PR may be more appropriate is because addin any amount of meaningful coverage to ForageSDK would involve some non-trivial refactors so that ForageSDK and it's methods can be tested at all - right now ForageSDK isn't tested at all.
Let me know what you think!


KazooClient thread-safety and instance reuse

I couldn't immediately find an answer in the docs re: thread-safety and reuse of KazooClient.
I would like to know if an instance of KazooClient is supposed to be short-lived and limited to a single thread or if a shared instance can be used from multiple threads.
In particular, is there any problem with:

instantiate + start() a single instance of KazooClient at the startup of a web application and reusing it everywhere;
stop() and close() said instance at shutdown?

Thanks!

Hi,
It can safely be used across multiple threads, but do not use it across
processes (forks).
Cheers,
On Wed, Sep 6, 2023, 10:37 Jan Van den bosch @.***>
wrote:

I couldn't immediately find an answer in the docs re: thread-safety and
reuse of KazooClient.
I would like to know if an instance of KazooClient is supposed to be
short-lived and limited to a single thread or if a shared instance can be
used from multiple threads.
In particular, is there any problem with:

instantiate + start() a single instance of KazooClient at the
startup of a web application and reusing it everywhere;
stop() and close() said instance at shutdown?

Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/python-zk/kazoo/issues/728, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIFTHW7WQJGDOH3IXGPXV3XZCDEFANCNFSM6AAAAAA4NOM42E
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thanks. So would you recommend using a single KazooClient instance across the entire application? Are there any drawbacks, considerations?

None, we have been doing single kazoo client shared by multiple threads for
years now.
Only advice is make sure you run a little  code on the watchers' thread as
possible (there is only one per KazooClient) since it will be shared.
Create a worker thread and pass it all the events for processing using a
queue.Queue.
Cheers,
On Wed, Sep 6, 2023, 11:19 Jan Van den bosch @.***>
wrote:

Thanks. So would you recommend using a single KazooClient instance across
the entire application? Are there any drawbacks, considerations?
—
Reply to this email directly, view it on GitHub
https://github.com/python-zk/kazoo/issues/728#issuecomment-1708588496,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIFTHS4WPODHYISAQJYRE3XZCIBNANCNFSM6AAAAAA4NOM42E
.
You are receiving this because you commented.Message ID:
@.***>

That's clear, thanks.


percySnapshot fails silently

Right now there's not really a way to know that a call to percySnapshot succeeds in the test run.
I think that a default behaviour of failing when the connection fails would make things easier to debug in general

Hey @rtpg! This is done by design, so tests can be ran without Percy being enabled. There also isn't anything to return from percySnapshot since it's POST'ing DOM over to a different process (which then eventually turns into a screenshot from our API). The results for this isn't known until the tests are finished though, so it wouldn't be possible to fail on diff here either.
Curious to hear more about what you're running into and if we can solve it in a different way

Hey @rtpg! This is done by design, so tests can be ran without Percy being enabled. There also isn't anything to return from percySnapshot since it's POST'ing DOM over to a different process (which then eventually turns into a screenshot from our API). The results for this isn't known until the tests are finished though, so it wouldn't be possible to fail on diff here either.
Curious to hear more about what you're running into and if we can solve it in a different way

Basically I just had the issue of trying to set things up, having things pass despite the percy agent not running, and being a bit confused about why nothing was showing up.
Thinking about it a bit more, I understand the rationale of at least providing a mechanism for silently falling through. But I do think that in a CI build, a failure to connect to the percy agent locally does feel like something we would want to trigger a build failure by default (since it could be an indicator of some issue with the build pipeline).
I 100% understand not failing on a diff, both for the reasons you mentioned and because the "human review of diff" aspect is kinda... the whole point of this, right?

Basically I just had the issue of trying to set things up, having things pass despite the percy agent not running, and being a bit confused about why nothing was showing up.
Thinking about it a bit more, I understand the rationale of at least providing a mechanism for silently falling through. But I do think that in a CI build, a failure to connect to the percy agent locally does feel like something we would want to trigger a build failure by default (since it could be an indicator of some issue with the build pipeline).
I 100% understand not failing on a diff, both for the reasons you mentioned and because the "human review of diff" aspect is kinda... the whole point of this, right?


External config file can not load panorama

Using ?config= no longer seems to be able to load the pano image.
Very simple ex:

test.json:
{
    "autoload": true,
    "panorama": "/images/panorama.jpg",
    "showFullscreenCtrl" : false
}

The config file is located, because the showFullscreenCtrl parameter is interpreted (false and the control does hide, true and it shows) but the actual image never loads, and watching the console shows the error
"Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check http://xhr.spec.whatwg.org/."
at line 72 of pannellum.htm
Using URL parameters

works just fine. Image auto loads. But of course I don't have control over the appearance of the Full Screen control (which, btw, does not seem to work in Chrome v.40) or the h/vaov that I need. The console does report "Resource interpreted as Image but transferred with MIME type text/html", though the image is correctly loaded.

In the JSON, autoload should be autoLoad. Changing this should hopefully fix things for you.
The message about the synchronous XMLHttpRequest is a deprecation warning, which doesn't affect anything.
I just tested in Chromium 40, and the fullscreen control still works for me.
The MIME type text/html warning suggests that your server is misconfigured and claims in the response headers that the image is an HTML document (again this doesn't affect how Pannellum works).