Make page fit 100% of screen

Description
Currently, the page does not fit 100% of the screen. Players have to scroll down to see the other parts of the page.
Action items

Make page fit 100% of the screen it is view from.
Take note of the warning banner at the top. The page should still fit 100% even when the banner is removed

B

Hi

@princeibs I'm a frontend and also a blockchain developer. I will love to work on this, I'm very ready to work

@princeibs please let me work on this

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am a Full Stack developer with 6 years of experience in the industry, I am super excited to be able to contribute to Web 3 projects, this to continue paving my way as an Open Source Contributor. I am from Dojo Coding Community
How I plan on tackling this issue
Check CSS for Full Screen Fit:
Ensure the page layout is set to occupy 100% of the screen height, without needing scrolling.
Adjust for Banner Removal:
Make sure the page dynamically adjusts when the top banner is removed, filling the available screen space.
Check for Overflow:
Identify and fix any elements causing unintended overflow that leads to scrolling.
Test Responsiveness:
Verify that the page adapts correctly across different screen sizes and devices.
Ensure Cross-Browser Compatibility:
Test the page in multiple browsers to confirm consistent behavior.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Introduction and how my background can be of use
Hello, i am Dprof-in-tech, an experienced Full Stack Blockchain Developer and  I am excited to contribute my skills to this project in this ODHACK 8. With a strong background in Next.js, TypeScript, JavaScript, React, Node.js, Rust and Cairo, I've honed my technical skills across the blockchain development landscape.
My journey with OnlyDust began at Edition 2, and I've since made 34 contributions across 11 projects. This extensive experience on the platform has allowed me to develop a keen understanding of delivering high-quality solutions under tight deadlines. I bring a unique blend of technical prowess and user-centric design to every project, whether I'm crafting immersive 3D experiences or developing innovative smart contracts.
My track record demonstrates my ability to adapt quickly and contribute effectively to diverse challenges. I'm confident in my capacity to tackle new problems and drive innovation in the blockchain space. As we begin ODHACK 8, I'm eager to leverage my hackathon experience and technical skills to push the boundaries of what's possible in blockchain development.
Below is a link to my OnlyDust public profile.
https://app.onlydust.com/u/Dprof-in-tech
BASIC PAYMENT APP
Hello, i am Dprof-in-tech, an experienced Full Stack Blockchain Developer and  I am excited to contribute my skills to the {project name} project in this ODHACK 8. With a strong background in Next.js, TypeScript, JavaScript, React, Node.js, Rust and Cairo, I've honed my technical skills across the blockchain development landscape.
My journey with OnlyDust began at Edition 2, and I've since made 34 contributions across 11 projects. This extensive experience on the platform has allowed me to develop a keen understanding of delivering high-quality solutions under tight deadlines.
Due to my web2 experience, i am skilled in writing unit tests and have used Jest and Vitest to do this. I would love to contribute to this project by solving this issue.
Below is a link to my OnlyDust public profile.
https://app.onlydust.com/u/Dprof-in-tech
Issue #13
Here is the approach i would use in building a solution to this issue while focusing on writing standard unit tests.

First things first, gotta set up Vitest. It's pretty straightforward:

Now,  I'll go through /src/lib/stellar/* and /src/lib/utils.js, make a list of all the exported functions, and decide which ones are the most important or complex. Those are the ones I'll tackle first.

For each file, I'll make a matching test file right next to it. So like, utils.js gets a utils.test.js buddy.

Writing the actual tests is where the fun begins:

Start simple: just check if the function exists
Test the normal inputs and outputs
Throw some weird stuff at it (empty inputs, huge numbers, etc.)
Make sure it doesn't fall apart when something goes wrong

If a function is calling APIs or doing something I can't easily test, I'll mock that stuff out. No need to actually hit external services for unit tests.

I want to know how much of my code I'm actually testing, so I'll set up coverage:

I'll start with the easy functions and work my way up to the trickier ones. Utilities are super important, so I'll make sure those are rock solid.

To keep things organized, I'll use describe blocks. Group tests for each function, and if a function has different scenarios, I'll nest describe blocks.

Once I've got a decent set of tests, I'll set up GitHub Actions to run them on every commit. No broken code sneaking into main!

Last but not least, I've gotta keep these tests up to date. When I change a function, I update its tests. New function? New tests. And every now and then, I'll go through and clean up the tests to keep them running smooth.

I believe with this approach and your essential code review, id give the perfect solution to this issue.
ISSUE #9
Based on the code provided and the issue described, here's an approach to solve the problem of the SEP-24 deposit/withdraw popup closing prematurely:

Identify the Issue:
The problem occurs in the launchTransferWindowSep24 function, where the event listener is closing the popup immediately upon receiving any message.

Modify the Event Listener: i would modify the event listener to decode the message being returned before closing the pop up.

Implement Error Handling:

Add try-catch blocks to handle potential errors in the event processing.
Log errors for debugging purposes.

Potentially Add User Feedback if needed:

Implement a mechanism to display status updates to the user.
Consider using a toast notification system or updating a status element on the page.

Testing:

Manually test the SEP-24 flow with various scenarios to ensure the popup stays open until the transfer is completed or explicitly aborted.
Add unit tests for the new event handling logic.

Refactor for Reusability:

Consider extracting the SEP-24 window handling logic into a separate function or component for easier maintenance and potential reuse.

Update Documentation where neccessary:

Add comments explaining the new behavior of the event listener.
Update any relevant documentation about the SEP-24 transfer process.

STELLAR CLI
Hello, i am Dprof-in-tech, an experienced Full Stack Blockchain Developer and  I am excited to contribute my skills to the {project name} project in this ODHACK 8. With a strong background in Next.js, TypeScript, JavaScript, React, Node.js, Rust and Cairo, I've honed my technical skills across the blockchain development landscape.
My journey with OnlyDust began at Edition 2, and I've since made 34 contributions across 11 projects. This extensive experience on the platform has allowed me to develop a keen understanding of delivering high-quality solutions under tight deadlines.
Due to my web2 experience, i am skilled in writing Typescript and i  would love to contribute to this project by solving this issue.
Below is a link to my OnlyDust public profile.
https://app.onlydust.com/u/Dprof-in-tech
ISSUE #1155
To solve this issue, i would:
Update TypeScript: I'll install the latest stable version of TypeScript and ensure it's reflected in the project dependencies.
Verify the Version: I’ll confirm that the latest version is installed and working correctly.
Review Changes: I’ll check the release notes for any updates or breaking changes and ensure that our code is compatible with the new version.
Update Configuration: If needed, I’ll adjust the TypeScript configuration file to align with the latest standards and features.
Test Everything: I’ll run a full test of the codebase to catch any issues, making sure our project builds correctly and functions as expected.
Fix and Optimize: If any issues arise due to the upgrade, I’ll resolve them and take advantage of new features to optimize our code where possible.
Commit the Changes: Once everything is tested and working, I’ll commit the updates for future use.
This process will ensure that we’re using the latest version of TypeScript, keeping the project up-to-date and taking advantage of the latest improvements.
STARKNET QUEST
Hello, i am Dprof-in-tech, an experienced Full Stack Blockchain Developer and  I am excited to contribute my skills to the {project name} project in this ODHACK 8. With a strong background in Next.js, TypeScript, JavaScript, React, Node.js, Rust and Cairo, I've honed my technical skills across the blockchain development landscape.
My journey with OnlyDust began at Edition 2, and I've since made 34 contributions across 11 projects. This extensive experience on the platform has allowed me to develop a keen understanding of delivering high-quality solutions under tight deadlines.
Due to my web2 experience, i am skilled in writing unit tests and have used Jest and Vitest to do this. I would love to contribute to this project by solving this issue.
Below is a link to my OnlyDust public profile.
https://app.onlydust.com/u/Dprof-in-tech
Issue #266
To solve this issue, i would :

I’ll create a custom_api folder under the admin directory, with routes for create_custom_api and update_custom_api.
The new task document will be updated to include the api_url and regex fields alongside existing fields like name, description, etc.
I’ll also add these fields to the database schema, ensuring we store them correctly.
The create route will allow creating tasks with the custom_api type, while the update route will handle modifying existing tasks.
Finally, I’ll implement the necessary logic to interact with the database for task creation and updates, making sure the new fields are properly handled.

Once this is done, I’ll run tests to confirm everything is working as expected.
I’ll be sure to follow the guidelines as given and work to tender my solution as soon as possible.
ISSUE #263
To solve this issue, i will:
Here’s the approach I’d take to solve this issue:

Update QuestTaskDocument:
I’ll start by adding the optional api_url and regex fields to the QuestTaskDocument type in src/models.rs if they aren’t already there. These will allow us to store the API URL and regex for custom API tasks.

Create verify_custom_api Route:
I’ll then create a new route, verify_custom_api.rs, under src/endpoints/quests. This route will be responsible for handling custom API verifications.

API Call Logic:
Inside verify_custom_api.rs, I’ll implement logic to call the specified API from the api_url field (e.g., api.carmine.finance). I’ll use a similar approach to the one we used in the verify_balance route, ensuring consistency.

Regex Validation:
After receiving the API response, I’ll validate it using the provided regex field. If the response matches the regex, I’ll mark the task as complete in the database. If not, I’ll return an error indicating the failure.

Task Completion Logic:
Once the regex validation passes, I’ll update the task status in the database to mark it as complete, reusing code from verify_balance to handle this efficiently.

Testing & Validation:
Finally, I’ll ensure that the new functionality is tested thoroughly to confirm it works as expected. I’ll run tests to verify that tasks are correctly marked as complete when the API response matches the regex and that errors are properly handled for invalid responses.

I’ll be sure to follow the guidelines as given and work to tender my solution as soon as possible.
SPEEDRUN-SCAFFOLD-STARK
Hello, i am Dprof-in-tech, an experienced Full Stack Blockchain Developer and  I am excited to contribute my skills to the {project name} project in this ODHACK 8. With a strong background in Next.js, TypeScript, JavaScript, React, Node.js, Rust and Cairo, I've honed my technical skills across the blockchain development landscape.
My journey with OnlyDust began at Edition 2, and I've since made 34 contributions across 11 projects. This extensive experience on the platform has allowed me to develop a keen understanding of delivering high-quality solutions under tight deadlines.
Due to my web2 experience, i am skilled in writing unit tests and have used Jest and Vitest to do this. I would love to contribute to this project by solving this issue.
Below is a link to my OnlyDust public profile.
https://app.onlydust.com/u/Dprof-in-tech
[BUG] Mobile Navbar Window Transparent, Covers Other Menu #283:
I will investigate the mobile navbar styling:
I will inspect the CSS and layout for the mobile version of the navbar. This likely involves looking into z-index values, background colors, or transparency settings that may be causing the navbar to overlap with other menus incorrectly.
I will identify the root cause of the transparency:
I will focus on isolating the CSS responsible for the transparency issue. This could be due to missing background styles, incorrect z-index layers, or conflicting styles with other components.
I will adjust the z-index and background styles:
If the issue is related to the z-index, I will modify the stacking order so that the navbar doesn’t interfere with other elements on the page.
I will also ensure the navbar has the appropriate background color (non-transparent) and padding to make it behave as expected on mobile devices.
I will test across different screen sizes:
I will test the fix on various mobile devices and screen sizes to ensure that the issue is resolved for all users, regardless of their device.
I will capture and report the fix:
Once resolved, I will submit a screenshot showing the correct behavior of the navbar and ensure that no new issues are introduced by the change.
My estimated time of delivery is within a day and i would be sure to follow the rules of contributing to speedrun scaffold stark.
[TEST] Add Unit Tests for useScaffoldEventHistory #293:
I will set up the testing environment using vitest:
Since the project uses vitest for unit testing, I will ensure my environment is properly configured to run the tests as per the guidelines provided in the project.
I will refer to the Vitest documentation for specific syntax requirements, especially for developers familiar with Jest.
I will use @testing-library/react to test the hooks:
I will ensure I import the necessary utilities from @testing-library/react for testing hooks like useScaffoldEventHistory. These utilities will help simulate how the hook is used within components and allow for effective testing of its behavior.
I will mock external dependencies where necessary:
If useScaffoldEventHistory relies on external APIs or other dependencies, I will mock those to isolate the unit being tested. I will ensure that the tests are not dependent on live data or network requests.
I will focus on writing meaningful test cases:
The tests will cover the main functionality of the hook, including edge cases and error handling. This will ensure that any refactoring or future changes to the hook won’t break existing features.
I will also use it.only() to isolate tests for debugging if necessary, but I’ll ensure that all such isolation is removed before submitting the PR.
I will ensure cross-device test compatibility:
I’ll ensure the tests can run across different development environments, so they don’t only work on my device.
I will capture and report code coverage:
After completing the tests, I’ll run coverage reports and aim for a code coverage of 70% or higher for this hook.
I’ll provide a screenshot of the code coverage in the pull request to demonstrate the quality of the test coverage for useScaffoldEventHistory.
GO STARK ME
[feat] Add Dashboard Page #89:
I will create the new /app route:
This will be the dashboard page as specified in the issue. I'll ensure the route is set up within the Next.js project following the standard Next.js routing conventions.
I will confirm that no navbar is included in this page since it's being addressed separately.
I will review the Figma prototype:
I’ll study the provided design on Figma to ensure the dashboard's layout and styling match the expected outcome. I'll take note of the structure and components outlined.
I will add a Funds component:
The Funds component will be responsible for displaying the funds on the dashboard.
For now, I will hardcode some dummy data to visualize how the funds will be displayed. This will help ensure the design elements are functioning correctly.
I will focus solely on design:
At this stage, I will not worry about functionality or data integration. The priority is to get the look and feel of the dashboard page as close to the design as possible, using placeholder content where necessary.
My estimated time of delivery would be within 2 days of being assigned so i can focus on giving a pixel perfect design.
[feat] Add Users Profile Page #92:
I will create the /app/myprofile/{useraddr} route:
This page will represent the user's profile page, and I will ensure that it accepts the user's address (useraddr) as a parameter to identify which profile is being accessed.
I will reference the Figma prototype:
I’ll review the Figma prototype to understand how the profile page should look in terms of layout, font, colors, and component arrangement.
I will develop the page without the navbar:
As with the dashboard, I will not include the navbar here. The focus will be on the core profile design.
I will ensure the page is strictly design-focused:
At this stage, I won’t handle any logic or API integration. I’ll only work on the design and layout based on the prototype, ensuring it’s ready for functionality to be added later.
My estimated time of delivery would be within 2 days of being assigned so i can focus on giving a pixel perfect design.
[feat] Add Users Funds Page #93:
I will set up the /app/myfunds/{useraddr} route:
Similar to the profile page, this page will take the user's address (useraddr) as a parameter and display the user's funds.
I will review the Figma prototype:
I’ll carefully check the Figma design to understand how the funds should be presented on this page. This will guide the visual layout and components.
I will create the UserFunds component:
This component will represent each fund as a card on the page. I'll use dummy data to simulate the funds that a user might have, focusing on the display rather than the actual data source.
I will prioritize design over functionality:
Like the other pages, I will not implement the functionality yet. I’ll ensure the design is solid and that the page is ready for further development.
My estimated time of delivery would be within 2 days of being assigned so i can focus on giving a pixel perfect design.
STARKLUDO
Make page fit 100% of screen #72
Approach for Ensuring the Page Fits 100% of the Screen:
I will begin by analyzing the current layout:
I will inspect the current page layout and identify the elements causing the page to exceed the screen height.
This will involve checking for unnecessary margins, paddings, and any elements that could cause the overflow issue.
I will adjust the CSS for full-screen fit:
I will modify the existing CSS to ensure that the page content fits 100% of the viewport height (vh), without causing scrolling.
This will involve using CSS properties like height: 100vh or min-height: 100vh to make sure the content is restricted to the visible screen size, considering any dynamic content like the banner.
I will account for the warning banner:
I will ensure that the page fits 100% of the screen height, regardless of whether the banner is present or removed.
If the banner is dynamic, I will adjust the layout to handle its presence by ensuring the content below adjusts accordingly (e.g., using calc(100vh - bannerHeight)).
I will test responsiveness across devices:
I will test the page across different screen sizes and devices (desktop, tablet, and mobile) to confirm the layout works consistently without requiring a scroll.
I will also ensure that any fixed or sticky elements (like headers or footers) do not interfere with the content fitting on the screen.
I will optimize the layout for potential future changes:
In case other elements like additional banners or notifications are introduced later, I will ensure that the layout is flexible and adjusts dynamically to fit 100% of the screen, even when new elements are added or removed.
I will test with and without the warning banner:
I will verify that the page adapts smoothly when the warning banner is visible and when it is removed.
I will make sure that when the banner is removed, no additional blank space appears and the rest of the content adjusts seamlessly to fill the screen.
I will submit the PR with screenshots and testing details:
After making the necessary adjustments, I will provide screenshots of the page with and without the banner, showing how the content fits 100% of the screen in both cases.
I will document any additional testing steps required to validate that the fix works across different browsers and screen sizes.
Implement "change dice" on client #70
Approach for Implementing the "Change Dice" Feature on the Client:
I will review the existing code and UI:
First, I will inspect the existing implementation of the toolbox window to understand how the dice display and interaction components are structured.
I will check if there are any placeholder elements for the dice selection feature and identify where the non-functional elements need to be updated.
I will create the dice selection interface:
I will build the UI for selecting a dice, following the design provided in the image (or from the Figma if applicable). This will include:
A list or grid of available dice options, displayed visually for the player to choose from.
Proper styling to ensure it matches the overall project’s theme, with hover and selection states that visually indicate the selected dice.
I will implement the dice selection functionality:
I will add event handlers (e.g., onClick) to each dice option in the list, so that when a player clicks on a dice, it becomes the "active" dice.
This functionality will involve updating the state to reflect the selected dice. I will ensure the selected dice is stored globally (or at an appropriate level) so that it persists through gameplay.
I will sync the selected dice with the current game session:
I will ensure that the dice selected by the player is set as the current dice for all players in the session. This might involve updating or sending the selected dice information to the game state via an API or shared state management system, so that it can be used during gameplay.
I will handle any real-time synchronization needed if multiple players are viewing or interacting with the dice simultaneously.
I will test the dice functionality in gameplay:
I will integrate the newly selected dice into the gameplay logic, ensuring that once a player selects a dice, it becomes the default dice used for rolling during the game.
I will ensure that all players in the game session are able to see and roll the newly selected dice without issues.
I will handle edge cases:
I will address scenarios where a player might try to change the dice mid-game or where no dice is selected initially. I will set sensible defaults or provide warnings where necessary.
I will ensure that any dice-specific rules or limitations are followed (if there are specific game rules governing dice changes).
I will test the functionality across devices and scenarios:
I will test the dice selection across different devices and screen sizes to ensure that the UI is responsive and functional.
I will also perform tests with multiple players to confirm that the selected dice are correctly reflected for all players in real time.
I will submit the PR with a demo:
I will include a short demo video or series of screenshots showing how the player can select a dice and how the selected dice is reflected in the game.
I will include notes on how the new dice functionality is integrated and any steps required to test it during the review process.
STELLAR WALLET
Redesign of Wallets dialogs #51
I will research MetaMask’s new interface system:
I will begin by reviewing MetaMask's official documentation and resources regarding the newly released interface for plugins, ensuring I fully understand the changes and new features.
I will gather insights on MetaMask’s design system, best practices for wallet interactions, and any relevant UI/UX guidelines they have provided for developers.
This will help ensure that the redesigned wallet pop-ups align perfectly with MetaMask’s new interface system.
I will analyze the existing wallet dialog components:
Before starting the redesign, I will thoroughly examine the current implementation of wallet dialogs in the project.
I will identify the areas where changes are required to integrate MetaMask’s new interface system, including potential updates to UI components, state management, and wallet connection logic.
I will also evaluate how these dialogs interact with other parts of the application to avoid any breaking changes.
I will map out the new UI flow:
Based on the information gathered from MetaMask’s documentation and the current design, I will create a visual flow of how the new wallet dialogs will behave.
This will include the key states such as wallet connection, approval, confirmation, transaction details, network switching, and errors.
I will sketch or prototype the changes, ensuring that each dialog follows MetaMask’s new UI patterns, including responsiveness and accessibility.
I will update the dialog components according to MetaMask’s new UI:
I will update the wallet pop-up dialogs to adopt the new MetaMask interface, ensuring they reflect the latest design guidelines for consistency and enhanced user experience.
These updates will include:
Visual redesign of the dialogs (modals), following MetaMask’s new aesthetic guidelines.
Updated buttons, input fields, and pop-up elements, ensuring they look and function as required by the new system.
Ensuring that pop-ups are fully responsive, accessible, and look great in both light and dark modes, if applicable.
I will implement the new MetaMask plugin API (if applicable):
If MetaMask’s new interface system includes updates to the API or connection process, I will update the logic accordingly. This may involve:
Updating the methods used to request wallet connections, transactions, and approvals.
Ensuring that any interactions with the MetaMask wallet follow the new plugin standards for security, notifications, and confirmation flows.
I will handle error states and provide appropriate user feedback as per MetaMask’s recommendations.
I will ensure a seamless user experience:
I will ensure that the redesigned wallet dialogs maintain a smooth and intuitive experience for users. The flow will be optimized for:
Quick wallet connections, minimizing friction for users during transaction approvals.
Clear and concise error handling, where users are given actionable instructions if something goes wrong during a transaction or wallet interaction.
I will ensure the dialogs reflect the same high-level UX found in MetaMask’s own pop-up windows for consistency.
I will conduct cross-browser and device testing:
I will test the redesigned dialogs across multiple browsers and devices (desktop and mobile) to ensure they function properly in all environments, especially considering MetaMask’s heavy use in decentralized applications across different devices.
I will check for potential performance issues, bugs, or any visual glitches that could arise during wallet interactions.
I will gather feedback and iterate:
After the initial implementation, I will present the redesigned dialogs to the team for feedback. I will make sure to capture any areas of improvement and refine the design based on input from stakeholders.
I will also validate the design and functionality with MetaMask's recommended testing scenarios.
I will document and submit the changes:
Once the redesign is complete and tested, I will document the changes made, including any updates to wallet connection logic, new interface elements, and guidance on how the new dialogs behave.
I will submit a comprehensive pull request with details on how the redesign meets MetaMask’s new interface guidelines and attach screenshots or video demonstrations of the updated dialogs in action.
Create Stellar Identity Component #50
Approach for Create Stellar Identity Component (#50):
I will research Stellar and its identity management framework:
I will review Stellar's documentation and explore how identity-related data (such as home address) can be securely managed within a Stellar wallet.
Specifically, I will look into how Stellar recommends handling personal information, encryption methods, and wallet extensions for storing sensitive user data.
I will explore Stellar’s existing standards for user identity management, particularly how wallets interact with on-chain and off-chain data.
I will design a secure structure for storing user identity data:
I will determine the necessary fields to store a user’s identity, starting with the home address, and any other essential identity information the Stellar system may require.
I will implement encryption mechanisms to ensure that the stored identity data (such as home address) is secure and only accessible by the user.
I will use industry-standard encryption techniques, such as AES or RSA, for protecting the data while it is stored in the wallet.
I will build the Stellar Identity component:
I will create a new Stellar Identity Component in the Stellar Wallet that allows users to input and securely store their personal information, including their home address.
The component will:
Provide input fields for users to enter their identity details.
Encrypt the data before storing it in the wallet extension to ensure the user's control over their data.
I will ensure that the identity component is user-friendly and clearly explains to users how their data is being stored securely.
I will implement encrypted storage for user identity data:
I will integrate encrypted storage within the wallet extension to ensure all user identity data is stored securely.
The encryption process will involve:
Ensuring the data is encrypted locally on the user’s device before it is saved.
Leveraging secure storage APIs provided by the wallet extension or browser to handle encrypted data.
Ensuring users can access, update, or delete their stored identity data easily while maintaining encryption security.
I will give users full control over their identity data:
I will implement features that allow users to manage their encrypted identity data in a transparent and intuitive way.
The component will allow users to:
View their stored data (after decrypting it securely).
Update or delete their home address or other identity fields at any time.
Understand through clear UI/UX elements that their data is stored securely and is only accessible by them.
I will integrate with the Stellar Wallet extension:
I will ensure that the Stellar Identity Component is seamlessly integrated with the Stellar Wallet extension so that it can function as part of the user's wallet experience.
I will handle interactions between the Stellar blockchain and encrypted identity storage within the extension, ensuring smooth functionality and security.
This will include making sure that identity data is only handled client-side and is never exposed to external parties without explicit user consent.
I will add validation and security checks:
I will implement strong validation on the input fields to ensure the integrity of the data (e.g., valid address formats).
I will also ensure the encryption and decryption processes are secure, with proper error handling and fallback mechanisms to avoid potential data loss or corruption.
Additionally, I will perform a security audit to ensure there are no vulnerabilities in how the identity data is managed.
I will test the component across multiple devices and environments:
I will ensure that the Stellar Identity Component works consistently across different browsers and devices, testing it on both desktop and mobile environments.
I will simulate various use cases, including adding, editing, and deleting identity data, to ensure a smooth and secure user experience.
I will also conduct stress tests on the encryption mechanism to ensure it handles large datasets and edge cases (e.g., network failures) effectively.
I will gather feedback and refine the component:
After the initial development, I will gather feedback from the team and testers on the functionality and user experience of the component.
Based on the feedback, I will refine the component further, ensuring it meets the highest standards of security, usability, and Stellar wallet integration.
I will document and submit the component:
I will document the Stellar Identity Component thoroughly, outlining the encryption approach, how users can interact with their identity data, and how the data is securely stored and managed.
I will submit a detailed pull request, ensuring that all aspects of the component are clearly explained, including security measures and testing steps.
DERISK
Add informative warning message when the selected lending protocol doesn't use the selected token #190
Approach for Add informative warning message when the selected lending protocol doesn't use the selected token (#190):
I will read and understand the existing code:
I will start by thoroughly going through the Contributor Guidelines and README to understand the project setup and best practices.
Next, I will examine the current implementation of the Streamlit dashboard, specifically focusing on the code around the main chart titled "Liquidable debt and the corresponding supply" located in app.py around line 319.
I will identify how the dashboard processes user input when selecting a lending protocol, collateral tokens, and debt tokens to understand why a KeyError occurs.
I will replicate the issue locally:
I will set up the project by following the instructions in the README and run the dashboard locally to reproduce the error where selecting an incompatible lending protocol and token pair causes the KeyError crash.
This will help me identify the exact point of failure and the conditions that cause the error to arise.
I will implement error handling for unsupported tokens:
Once I understand the failure point, I will introduce error handling in the part of the code where the dashboard checks for the existence of liquidable debt based on the selected lending protocol, collateral token, and debt token.
Instead of letting the program crash with a KeyError, I will write conditional logic that checks if the selected protocol supports the given collateral or debt token.
If the tokens are not supported, I will display a user-friendly and informative warning message:
"No liquidable debt for the <collateral_token> collateral token and the <debt_token> debt token exists on the selected lending protocol."
I will ensure the message includes the actual tokens and protocol the user selected for clarity.
I will ensure the remaining data displays properly:
After showing the warning, I will update the chart to display data for the remaining valid protocols (i.e., protocols that do accept the tokens), so the user still gets useful information despite the mismatch.
I will handle this gracefully to avoid any further crashes or unhandled errors.
I will test the solution:
I will thoroughly test the solution by selecting various combinations of lending protocols and tokens to ensure that the error handling works as expected.
Specifically, I will test:
Supported protocol and token combinations.
Unsupported protocol and token combinations to trigger the warning message.
Scenarios where only the collateral or debt token is invalid.
I will also ensure the chart refreshes and displays data for the remaining protocols in each case.
I will document the changes:
I will update the project documentation to explain the new behavior, including the warning message and how it handles unsupported tokens.
If there is a contributors' guide on error handling or messages, I will ensure my changes align with the project's standards.
I will submit the pull request and provide code coverage:
I will write unit tests to cover the new error-handling logic and the warning message display, ensuring they pass and contribute to the overall code coverage.
I will provide a screenshot of the updated test coverage, ensuring the coverage percentage aligns with the project's requirement (>=70%).
I will create a pull request following the project guidelines, ensuring my branch is rebased on the current master before submitting.
Estimated timeline:
Start Date: Immediately upon assignment.
Estimated Completion Date: 2 days from the start date (ETA: 2 days).
Harmonize colors on the dashboard #186
Approach for Harmonize Colors on the Dashboard (#186):
I will read and understand the current setup:
I will start by reviewing the Contributor Guidelines and README to ensure I follow the project standards and best practices for UI/UX and code consistency.
Then, I will study the current implementation of the Streamlit dashboard located in app.py and its styling logic. This will help me understand how the colors are currently applied across various components, including the main chart, pie charts, and other sections of the dashboard.
I will identify color inconsistencies:
I will run the dashboard locally to visually inspect the color schemes used in different components, such as the main chart (for supply and demand) and the pie charts (for lending protocols).
I will pinpoint specific areas where colors are inconsistent or unclear, such as supply vs. demand, deposit vs. collateral vs. debt, and lending protocols' rank-based color distribution (e.g., Nostra Mainnet not consistently using dark blue in the pie charts).
I will document all the identified color issues that reduce readability and clarity for users.
I will research and define a consistent color scheme:
I will choose a color palette that aligns with the project's existing style guide while also enhancing the dashboard's usability. This palette will include distinct, non-conflicting colors for:
Supply and demand in the main chart (ensuring users can easily distinguish between them).
Individual lending protocols, where colors should remain consistent across charts (e.g., Nostra Mainnet always being represented by dark blue).
Deposit, collateral, and debt, ensuring these roles are clearly differentiated by color to avoid user confusion.
I will ensure the selected colors are easy on the eyes and promote readability in both light and dark modes, keeping accessibility in mind (e.g., color contrast for visually impaired users).
I will harmonize and apply the new color scheme:
I will update the existing color definitions in the code to apply the new harmonized color scheme across all relevant components:
The main chart will be updated to clearly distinguish between supply and demand.
The pie charts will be fixed so that each lending protocol consistently retains its assigned color (e.g., Nostra Mainnet is always dark blue).
Colors will be applied systematically across deposit, collateral, and debt sections, ensuring clarity for users when switching between these views.
I will test the color scheme in both light and dark modes to ensure that it remains visually appealing and functional across different themes.
I will ensure the changes are responsive and test thoroughly:
I will verify that the new color scheme remains consistent and readable on various screen sizes and resolutions. This is crucial since users may access the dashboard from different devices.
I will test the dashboard across multiple browsers and screen sizes to ensure the color harmony holds up across all environments.
I will gather feedback and iterate if necessary:
Before submitting the final solution, I will share the updated color scheme and changes with the team (or stakeholders) to gather feedback. If any suggestions for improvement arise, I will make the necessary adjustments.
I will document the changes:
I will update the documentation to reflect the new color scheme rules and how they are applied throughout the dashboard.
I will include guidance on how future updates to colors should follow the newly established scheme for consistency.
Estimated Timeline:
Start Date: Immediately upon assignment.
Estimated Completion Date: 2 days from the start date (ETA: 2 days).
By implementing this solution, I will ensure that the dashboard's colors are harmonized and consistent, improving the user experience and making the data easier to understand at a glance.
Add informative warning message when a nonexistent loan is selected on the dashboard #184
Approach for Add Informative Warning Message When a Nonexistent Loan is Selected on the Dashboard (#184):
I will review the Contributor Guidelines:
To ensure compliance with project standards, I will carefully read through the Contributor Guidelines and README provided in the project repository. This will help ensure that my approach aligns with the team’s expectations, development processes, and code quality standards.
I will examine the current implementation of the loan details section:
I will focus on the existing implementation of the "Detail of a loan" feature found in the file app.py at line 393.
By running the dashboard locally, I will reproduce the error that occurs when a user inputs a combination of address and protocol that does not match any existing loan. This typically results in an IndexError, which currently crashes the dashboard.
I will implement a check to handle nonexistent loans:
I will add a conditional check within the part of the code responsible for fetching loan data to verify if there is any matching loan for the provided address and protocol.
If no loan exists, I will modify the logic to return an informative warning message rather than allowing the application to crash. The message will read:
"No loan for the user exists on the lending protocol."
This will ensure that the user is notified of the issue in a user-friendly manner without causing a disruption in the dashboard's functionality.
I will ensure the display of the warning is clear and non-intrusive:
I will style the warning message to match the existing design system, ensuring it stands out without overwhelming the user interface.
The message will be displayed near the input fields or within the loan detail section, maintaining consistency with the overall dashboard layout.
I will test the functionality thoroughly:
I will run the dashboard locally and test a variety of valid and invalid address-protocol combinations to ensure that:
For valid combinations, the correct loan details are displayed as expected.
For invalid combinations (i.e., nonexistent loans), the informative warning message is displayed and the dashboard does not crash.
I will also test edge cases, such as empty inputs and partially filled inputs, to ensure that the application handles all scenarios gracefully.
I will ensure the code adheres to project standards:
I will review the code to ensure it is clean, follows the project’s style guide, and adheres to any other specific guidelines mentioned in the Contributor Guidelines.
I will gather feedback and make necessary adjustments:
After implementing the solution, I will submit a pull request for review. Based on feedback from the team or project maintainers, I will make any required adjustments to further improve the solution.
Estimated Timeline:
Start Date: Immediately upon assignment.
Estimated Completion Date: 2 days from the start date (ETA: 2 days).
DIP DUP
Run one of demos' tests with PostgreSQL #1105
Approach for Running One of the Demo's Tests with PostgreSQL (#1105):
I will review the existing integration tests:
I will start by exploring the file test_demos.py, which contains the integration tests that are currently being run using SQLite. This will allow me to identify which test(s) would be most suitable to run on PostgreSQL. I will choose a test that has a clear relationship to database operations, ensuring we effectively test the PostgreSQL-related code.
I will review the PostgreSQL test setup:
To understand how the project uses PostgreSQL in tests, I will review the existing test setup, particularly the run_postgres_container helper function provided by dipdup.test. This function allows the spawning of a temporary PostgreSQL container for running tests.
Additionally, I will reference the test_hasura.py file, which uses this helper function. This will help me understand how to configure and manage PostgreSQL containers within the test suite.
I will modify the selected demo test to run with PostgreSQL:
Once I identify the demo test to be run with PostgreSQL, I will modify it to use the run_postgres_container helper function.
I will update the test setup so that the PostgreSQL database is initialized and the necessary schemas and tables are created before the test execution.
The test teardown will ensure that the temporary PostgreSQL container is stopped and cleaned up after the test run.
I will handle any SQLite-specific code:
If the selected test contains any SQLite-specific code or assumptions, I will refactor it to work with PostgreSQL. This might involve:
Modifying SQL queries or schema definitions to be compatible with PostgreSQL.
Updating database connection configurations within the test.
I will ensure the refactoring does not interfere with the existing SQLite-based tests, preserving compatibility with both databases.
I will run the test locally:
I will first run the modified test locally using PostgreSQL by invoking the run_postgres_container helper function.
I will confirm that the PostgreSQL container is spawned, the test runs successfully, and any issues are resolved.
I will ensure that after the test, the PostgreSQL container is properly cleaned up, preventing resource leaks.
I will confirm compatibility with the rest of the test suite:
After successfully running the test with PostgreSQL, I will rerun the full test suite to ensure that the addition of the PostgreSQL test does not introduce any regressions or interfere with existing tests.
I will submit the changes for review:
Once the test is running successfully on PostgreSQL, I will submit a pull request with the changes.
In the PR, I will explain how I modified the demo test to run on PostgreSQL, how I used the run_postgres_container helper, and any additional setup required for future tests using PostgreSQL.
I will also request feedback from the maintainers regarding the approach and make any necessary adjustments based on their input.
Estimated Timeline:
Start Date: Immediately upon assignment.
Estimated Completion Date: 2 days from the start date (ETA: 2 days).
Method for updating index state #1099
Approach for Updating Index State (#1099):

Review the Current Indexer and State Management
I will begin by reviewing the current architecture of the indexer, particularly how the index state (properties and status) is managed within the application. This will include analyzing how states such as "active", "syncing", and "stopped" are handled.
I will also examine how the application interacts with the DipDupContext and the control API endpoint. Understanding how to modify this context will allow us to implement updates in an efficient manner.
Identify the Properties to be Updated
I will identify the key properties that need to be updated within an index's state, such as:
Index status: Whether it is active, disabled, or completed.
Last indexed block/level: The latest block/level the indexer processed.
New statuses to implement:
Disabled: When the user disables the indexer manually.
Completed: When the index has reached the latest block/level and completed indexing successfully.
Implement update_index Method in DipDupContext
I will add the update_index method to the DipDupContext, allowing updates to be made to the index's state. This method will be responsible for:
Accepting the index name, new status, and any property updates.
Applying the changes to the in-memory state and persisting them to the appropriate data store (e.g., database, cache).
I will ensure that this method is flexible enough to handle updates across various properties of the index, not just the status.
Update the Control API Endpoint
I will modify the control API endpoint to allow users to trigger index updates through the API. This will involve:
Adding a new route, likely named /update_index, that accepts a POST request.
The API request body will include the index name and the updates to apply (e.g., setting the status to disabled or completed).
I will ensure proper validation of incoming requests, confirming the index exists and that the provided properties are valid.
Handle New IndexStatus Members
I will implement the two new members of IndexStatus:
Disabled: This status will indicate that an index has been disabled by a user action. I will update the application logic to ensure the index stops processing when in this state.
Completed: This status will indicate that an index has successfully finished processing up to the latest available level.
For both statuses, I will ensure that:
Disabled: The indexer halts and does not attempt further processing.
Completed: No further indexing occurs unless new blocks/levels are available.
Discuss and Implement Polling for Pseudo-Realtime Updates
I will consult with the team on whether to implement polling as a fallback mechanism when the WebSocket URL is missing. This would enable pseudo-realtime updates where the system periodically checks for new data if WebSockets are unavailable.
If polling is decided as the approach, I will:
Implement a polling mechanism within the indexer, where it checks for new data at configurable intervals.
Ensure this process is efficient and doesn't cause unnecessary load on the system or network.
Test the Implementation
I will create unit and integration tests for the following:
Updating index state: Ensuring the update_index method correctly updates the status and properties.
Control API endpoint: Validating that the API allows index state updates and handles errors (e.g., invalid index or properties).
Disabled and Completed statuses: Ensuring the application behaves correctly when an index is marked as disabled or completed.
Polling (if implemented): Ensuring that the polling mechanism works as intended and provides near-real-time updates when WebSockets are unavailable.
Documentation
I will update the project documentation to include details on how to use the new control API endpoint for updating index states.
I will also document the possible statuses for IndexStatus (active, disabled, completed, etc.), and how the application handles each state.
Submit the Changes for Review
After implementation and testing, I will submit a pull request with the following:
The update_index method in DipDupContext.
The updated control API endpoint for modifying index state.
The new IndexStatus members (disabled and completed).
Any relevant tests and documentation updates.
I will request feedback from the team, make any adjustments as needed, and ensure the implementation aligns with the overall project requirements.
Estimated Timeline
Start Date: Immediately upon assignment.
Estimated Completion Date: 2-3 days from the start date.

STARKNET SCAFFOLD
Hey chief @Oshioke-Salaki ,
I am Dprof-in-tech, an experienced Full Stack Blockchain Developer and I am excited to contribute my skills to the {project name} project in this ODHACK 8. With a strong background in Next.js, TypeScript, JavaScript, React, Node.js, Rust and Cairo, I've honed my technical skills across the blockchain development landscape.
My journey with OnlyDust began at Edition 2, and I've since made 34 contributions across 11 projects. This extensive experience on the platform has allowed me to develop a keen understanding of delivering high-quality solutions under tight deadlines.
Due to my web2 experience, i am skilled in building out pixel perfect UI components. I would love to contribute to this project by solving this issue.
Below is a link to my OnlyDust public profile.
https://app.onlydust.com/u/Dprof-in-tech
Implement A Hamburger Menu Component #8
Approach for Develop a Fully Functional Hamburger Menu Component:
I will analyze the Figma design and project style guide:
I will begin by thoroughly reviewing the Figma design for both light and dark mode to ensure a pixel-perfect implementation.
I will also refer to the project’s existing style guide to maintain consistency in fonts, colors, and other UI elements across the component.
I will set up the Hamburger Menu structure:
I will create the base structure for the Hamburger Menu using React, ensuring that it accommodates the various features outlined (transaction tracker, network switcher, add token, etc.).
I will ensure that each feature is housed inside the pop-up component, making it easy to navigate through the different functionalities.
I will ensure full responsiveness:
I will implement responsive styling using the existing styling framework (e.g., Tailwind CSS) to ensure that the Hamburger Menu adapts to different screen sizes, including mobile, tablet, and desktop.
The menu will include touch-friendly elements for smaller devices, and I will test it across multiple viewports to verify its responsiveness.
I will implement theme support (light/dark mode):
I will incorporate support for both light and dark modes, adhering to the design specifications provided in the Figma file.
I will leverage existing theme switching logic (if any) or add necessary logic to toggle between the two modes within the component.
I will develop the functionality for network switching and other features:
I will integrate network switching within the Hamburger Menu, following the provided logic for handling user interactions. This functionality will allow users to seamlessly switch between networks.
Similarly, I will add other components such as the transaction tracker and the "Add Token" button, ensuring they work as intended and align with the project’s overall design and functionality standards.
I will reuse the existing Connect Button component for consistency:
I will use the Connect Button component as a reference for maintaining consistent styling and behavior within the Hamburger Menu. This will ensure that the new component matches the look and feel of existing UI components.
I will create a sub-route in the preview route for testing:
Once the component is built, I will set up a dedicated sub-route within the /preview path to showcase the various Hamburger Menu variants for easy testing.
This sub-route will allow developers and testers to switch between different states and modes (e.g., network switching, light/dark mode) to verify that each variant works as expected.
I will test the component extensively:
After development, I will thoroughly test the Hamburger Menu across different devices and screen sizes to ensure it is fully responsive and functional.
I will also verify that the component adheres to both light and dark modes and performs all actions (network switcher, transaction tracker, add token, etc.) without any issues.
I will submit the PR with screenshots and notes:
I will include screenshots of the component in both light and dark modes, as well as across different screen sizes, along with any relevant testing notes.
The PR will also contain a description of how to access the sub-route for testing each variant of the Hamburger Menu.
Implement A Settings Component #9
Approach for Develop a Settings Component:
I will begin by reviewing the Figma design and style guide:
I will thoroughly examine the Figma design to understand the layout, color schemes, fonts, and responsiveness required for both light and dark modes.
I will consult the project’s style guide to ensure that the component's UI and UX are consistent with the rest of the application.
I will set up the Settings component structure:
I will create the base structure of the Settings component using React and Tailwind CSS (or the existing CSS framework) to follow the design exactly.
This structure will accommodate settings for language, explorer, and theme options, ensuring a user-friendly layout and navigation.
I will ensure full responsiveness:
Using the project's responsive design strategy, I will make sure the Settings component is fully responsive across mobile, tablet, and desktop screens.
I will use media queries and flexbox/grid layouts to adapt the component's layout and spacing for different screen sizes.
I will implement light and dark modes:
I will integrate light/dark mode support into the Settings component, matching the theme-switching mechanism already established in the project.
This will allow users to toggle between light and dark themes dynamically, with immediate feedback on the component's appearance.
I will add the language, explorer, and theme change functionality:
Language Change: I will implement the ability to switch between different languages, integrating it with the existing i18n or translation setup in the project.
Explorer Selection: I will add functionality to allow users to change the default explorer (e.g., Etherscan, Polygonscan) based on the design.
Theme Switching: I will link the theme switch functionality (light/dark mode) directly to the project’s theme provider or CSS variables, ensuring smooth transitions between themes.
I will reference the Connect Button component for consistency:
I will use the Connect Button component as a styling and functionality reference to ensure the Settings component has consistent behavior and looks similar to the other components within the project.
I will create a sub-route for previewing and testing:
After building the Settings component, I will create a dedicated sub-route under /preview/settings that will showcase the various component states (language, explorer, and theme options).
This will allow the team to easily test each variant of the component to ensure that all functionality and design requirements are met.
I will test the component functionality:
Once the component is complete, I will thoroughly test it across different devices and browsers to verify its responsiveness and correctness in both light and dark modes.
I will ensure that the language switch, explorer selection, and theme switching work as intended without causing any issues in the app.
I will submit the PR with testing details and screenshots:
I will provide a comprehensive set of screenshots that demonstrate the component in different states (light/dark mode, different languages, explorer options).
I will include any necessary documentation on how to test the component, as well as information on how to access the sub-route for previewing each variant.
How I plan on tackling this issue
Approach for Ensuring the Page Fits 100% of the Screen:
I will begin by analyzing the current layout:
I will inspect the current page layout and identify the elements causing the page to exceed the screen height.
This will involve checking for unnecessary margins, paddings, and any elements that could cause the overflow issue.
I will adjust the CSS for full-screen fit:
I will modify the existing CSS to ensure that the page content fits 100% of the viewport height (vh), without causing scrolling.
This will involve using CSS properties like height: 100vh or min-height: 100vh to make sure the content is restricted to the visible screen size, considering any dynamic content like the banner.
I will account for the warning banner:
I will ensure that the page fits 100% of the screen height, regardless of whether the banner is present or removed.
If the banner is dynamic, I will adjust the layout to handle its presence by ensuring the content below adjusts accordingly (e.g., using calc(100vh - bannerHeight)).
I will test responsiveness across devices:
I will test the page across different screen sizes and devices (desktop, tablet, and mobile) to confirm the layout works consistently without requiring a scroll.
I will also ensure that any fixed or sticky elements (like headers or footers) do not interfere with the content fitting on the screen.
I will optimize the layout for potential future changes:
In case other elements like additional banners or notifications are introduced later, I will ensure that the layout is flexible and adjusts dynamically to fit 100% of the screen, even when new elements are added or removed.
I will test with and without the warning banner:
I will verify that the page adapts smoothly when the warning banner is visible and when it is removed.
I will make sure that when the banner is removed, no additional blank space appears and the rest of the content adjusts seamlessly to fill the screen.
I will submit the PR with screenshots and testing details:
After making the necessary adjustments, I will provide screenshots of the page with and without the banner, showing how the content fits 100% of the screen in both cases.
I will document any additional testing steps required to validate that the fix works across different browsers and screen sizes.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Hii! My name is Mario Araya, I’m a Software Developer with 2+ years of experience. I have worked with backend technologies such as Cairo, Java, and C#, as well as frontend development using React, NextJS, and JavaScript/TypeScript. I’ve made contributions to open-source projects, completed a Starknet Bootcamp, exercises on NodeGuardians, finished Starklings, and participated in multiple hackathons. I’m also a member of the Dojo Coding community here in Costa Rica.
How I plan on tackling this issue
Check CSS for Full Screen Fit:
Ensure the layout of the page uses height: 100vh or a similar CSS property to make the page fill 100% of the screen height without requiring scrolling, even when the content is minimal.
Adjust for Banner Removal:
Consider the dynamic removal of the top warning banner. Ensure that when the banner is removed, the page properly readjusts to fill the available screen space by updating the CSS to be responsive and reactive to changes in the page structure.
Check for Overflow:
Identify and fix any elements on the page that may cause overflow, which could lead to unwanted scrolling. This could involve revisiting padding, margins, or specific elements that may be pushing the layout beyond the visible screen area.
Test Responsiveness:
Verify that the page maintains its 100% height on different devices and screen sizes (mobile, tablet, desktop). This will ensure that the page fits the screen properly across all possible viewing environments.
Ensure Cross-Browser Compatibility:
Test the page on various browsers (Chrome, Firefox, Safari, Edge) to make sure the changes work consistently and as expected across different environments.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I have a strong background in front-end web development with a focus on creating responsive and well-structured UI designs using modern CSS and frameworks like React and TypeScript. My experience in working with various layout techniques, including Flexbox and CSS Grid, allows me to create layouts that adjust perfectly to different screen sizes. Additionally, I have dealt with similar issues in the past, where I had to ensure a webpage fits within 100% of the screen without unnecessary scrolling, while also maintaining critical UI components like banners or headers.
By leveraging my skills in CSS layout strategies and responsive design, I can make sure that the page fits 100% of the screen, taking into account different viewports and the presence (or absence) of a warning banner at the top. I am also familiar with tools and techniques to inspect and debug layout issues, ensuring that the solution is optimized for both desktop and mobile screens.
How I plan on tackling this issue
To ensure the page fits 100% of the screen, I would approach the problem as follows:
Inspect the current layout: I would first inspect the page to identify the elements contributing to the issue. This would involve checking the HTML and body elements, as well as any outer containers or sections that might be preventing the page from fitting the viewport.
Adjust CSS properties: To make the page fit the screen, I would:
Ensure that the html and body elements, along with any parent containers, have their height set to 100%.
If using a flex or grid layout, I would make sure the containers are set to display: flex; or display: grid; and use properties like flex-grow: 1; or min-height: 100vh; (viewport height) to fill the entire screen.
Check for any padding or margins causing overflow and adjust or remove them.
Handle the warning banner: I would ensure the page continues to fit 100% of the screen, whether the warning banner is present or not. This can be done by using dynamic height calculations such as calc(100vh - ) to maintain a full-page fit.
Test across devices and screen sizes: I would test the updated layout across different devices and screen resolutions to ensure it behaves as expected. If the page includes dynamic content or other interactive elements, I would ensure that their presence doesn’t affect the 100% fit of the screen.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am a frontend and blockchain developer with experience building applications. i am confident in my ability to tackle new challenges and drive innovation in this ecosystem.
How I plan on tackling this issue
To ensure the page fit 100% of the screen i will imply the following below:

Adjusting CSS Styles:

Set the body and main container height to 100vh to utilize the full viewport height.
Ensure margins and paddings do not cause overflow.

Handling  the Warning Banner:

Use CSS media queries or JavaScript to adjust the layout dynamically based on the presence of the banner, ensuring the page still fits without scrolling when the banner is removed.

Testing Responsiveness:

Test the layout on different screen sizes and resolutions to confirm it consistently fits the viewport.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Please can I be assigned this issue? This is my first time applying in this ecosystem and I’d love to be given the opportunity. I am a full-stack blockchain Developer, and my experience includes html, css, react, JavaScript,TypeScript and solidity and Cairo.
How I plan on tackling this issue
To solve this issue, I’ll take the following steps:
1. I’ll set the main container's height to 100vh and adjust the min-height to accommodate any warning banners if necessary.
2. I’ll use media queries to maintain layout across different screen sizes.
3. I’ll make sure no elements, like warning banners, overlap or push content down.
4. I’ll verify that the full-height functionality works correctly on different browsers and devices.
5. Lastly, I’ll inspect and adjust any margins or paddings that contribute to height issues.
Please assign me, I’m ready to work.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am a Full Stack blockchain Developer with expertise in Next.js, Nest.js, TypeScript, JavaScript, React, Node.js, Three.js, Solidity and rust. My journey with OnlyDust hackathons began at Edition 1, and I've since made 69 contributions across 14 projects. With my extensive experience on the OnlyDust platform (profile:  https://app.onlydust.com/u/Ugo-X), I've honed my skills in delivering quality solutions under pressure.
I bring a unique blend of technical proficiency and user-focused design to every project, whether it's crafting immersive 3D experiences or developing smart contracts. My track record shows I can adapt quickly and contribute effectively to diverse challenges.
As we surf through Edition 8, I'm excited to leverage my skills and hackathon experience to push the boundaries of blockchain development. I'm confident in my ability to tackle new challenges and drive innovation in this space.
How I plan on tackling this issue
I will make the page fit 100% of screen
I will create a custom React hook called useFullPageHeight. This hook will use useState to manage the page height and useEffect to calculate and update it. The calculation will account for the warning banner's presence. I will implement a function to compute the height by subtracting the banner's height from the window's inner height. The hook will add a resize event listener to ensure responsiveness. In the main component, I will apply the calculated height using inline styles. This approach will dynamically adjust the page to fit 100% of the screen, with or without the warning banner, and respond to window resizing.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am a Full Stack Developer and Cairo Developer. I have good experience building web application. I am new to Open Source and want to begin with this project. I am good in React, Typescript, Redux and Context APIs. I can leverage the same to make this a better game for the users.
How I plan on tackling this issue

Checking the structure of the project and understanding the codebase.
Knowing the tech stack required
Finding the area of the problem.
Designing the Figma solution.
Implementing into code.
Testing the code by inspecting in different screen size.
Modify the code when not working as expected.
After successful review, create a pull request.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I would love to work on this issue i contributed previously to this repo and would love to contribute to this issue
How I plan on tackling this issue
i approach this issue correctly and accurately

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am a full stack developer with 3 years experience in HTML, CSS JavaScript, node.js React, Typescript and other libraries and frameworks .
How I plan on tackling this issue
i will love this to be my first contribution on this platform please. firstly I would check if there is any outer element hindering maximum width span if there isn't i will give the identify segment which is affected and style them appropriately by giving a width of 100vw or 100% as styled property.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Fullstack developer
How I plan on tackling this issue
To make page non-scrollable and display all the content at once,I'll simply just ensure it doesnt exceed a height of 100dvh

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I’m a front-end developer with 3 years of experience transitioning to Web3, and I would love to make my first contribution to this project. I'm excited to take on this issue to challenge myself, learn, and contribute to the project's success.
I'm also a member of the Dojo Coding CR community, looking forward to applying my skills in this new space while I grow and contribute to this project.
How I plan on tackling this issue
First, I’ll read through the Contributor Guidelines and README to ensure I understand the project structure, coding standards, and the process I’m following. This will help me align the documentation with the project’s expectations.
I will review the current layout of the page to identify any CSS properties or structural elements that might be causing it to overflow and require scrolling. This includes checking margins, paddings, and any fixed heights that may be limiting the page’s vertical space.
I will modify the CSS to ensure the page utilizes the full height of the viewport. This may involve using properties like height: 100vh for the main container to allow it to take up the entire height of the screen, regardless of the presence of other elements.
I will ensure that the design is responsive. This means verifying that the layout adapts properly across different screen sizes, including desktop, tablet, and mobile views. I will test how the page behaves with various screen resolutions to confirm it maintains a full-screen appearance.
After making these changes, I will test the page both with and without the warning banner at the top. It’s essential to ensure that even if the banner is removed, the page still fits the screen perfectly without requiring any scrolling.
Finally, I will gather feedback from users to ensure the changes meet their expectations and that the user experience is seamless. If further adjustments are needed based on user interactions, I will refine the layout accordingly.
If I run into any problems or questions, I’ll reach out to the maintainers for assistance.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Hi I am a blockchain developer with 3 years experience. Previously contributed to this project and would love to contribute again.
How I plan on tackling this issue
I would have to check the styling and figure out the best way to tackle the issue.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I have experience in front-end development using TypeScript and have worked on responsive design projects. My skills in CSS and layout optimization will help ensure the page fits 100% of the screen across different viewports, while maintaining a good user experience.
How I plan on tackling this issue
I would inspect the page's layout and CSS properties to identify what is causing the overflow. Then, I’d adjust the height and flex properties to ensure the content fits the screen dynamically. I’d test with and without the warning banner to confirm the page remains responsive

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Can I take this? I’ve participated in almost every ODHack, and I already contributed to the StarkLudo project at the last hackathon. I have extensive experience in frontend development. I can handle this task.
How I plan on tackling this issue
My profile on OD: https://app.onlydust.com/u/melnikga

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I’m a Full Stack JavaScript Developer with a passion for creating gamified blockchain projects. Since I started with OnlyDust, I’ve made 18 contributions to different initiatives, which has really helped me sharpen my skills in building engaging and user-friendly experiences. I’m excited to bring this expertise to our current task.
How I plan on tackling this issue
I will first analyze the current layout to identify the elements causing the page to not fit the screen properly. Then, I will modify the CSS styles to ensure the page stretches to 100% height and width, providing a seamless view for players.
I’ll pay special attention to the warning banner at the top of the page. It’s important that even if the banner is removed, the page still maintains a full-screen fit. After making these adjustments, I will test the page on various devices and screen sizes to confirm that it looks great and functions well everywhere.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
have extensive experience in responsive web design, ensuring web applications fit various screen sizes without the need for scrolling. I am skilled in using CSS flexbox and grid layouts, which will allow me to properly adjust page elements to fit 100% of the screen while maintaining the layout, even when dynamic elements like banners are removed. This experience will help ensure the game page is optimized for different devices and screen sizes.
How I plan on tackling this issue
I would begin by adjusting the CSS of the page layout, using flexbox or grid to ensure that the content dynamically scales to fit the height and width of the screen. I would take the warning banner into account and ensure that, even when removed, the page still fits 100% of the screen without requiring scrolling. Finally, I’d test across various screen sizes to ensure the page is fully responsive and retains its usability.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Whew, looks like a ton of applications up there. Working as a Meme-Driven Dev back at Gobblchain, im left kind of feeling like https://imgflip.com/i/94quwj
with my previous experiences in personal projects and hackathons, I can whip up some real solutions—probably with a one-liner or two and a laugh along the way. [it's my first ODHack :)]
How I plan on tackling this issue
mhmm i'll fix it with a couple tweaks:

Slap height: 100vh; on the main container.
Set the banner as position: absolute; top: 0; so it won’t mess with the layout.
Flexbox that main content – one side Ludo, other side sidebar.
Throw in some overflow: auto; for any scrollable areas.
Make it responsive with flex-direction: column; on mobile.
Done and dusted! ezpz

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am a skilled fullstack developer with a wealth of experience in both frontend and backend JavaScript. With a solid foundation in testing,I have mastered frameworks like Mocha, Chai, and Jest to ensure robust, reliable code in every project. In addition to traditional web development, I have a strong background in blockchain technology, with hands-on experience in Solidity for Ethereum-based smart contracts. Moreover, I have delved into the emerging world of StarkNet, working with Cairo, a cutting-edge language tailored for STARKs, making them a versatile developer capable of bridging both traditional and decentralized web applications.
How I plan on tackling this issue
With my wealth of knowledge and experience this will be a super easy implementation, making the page to fit 100% and maintain a constant responsiveness across all screen

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Hello @princeibs I'm a front-end and also a blockchain developer
How I plan on tackling this issue
I will love to work on this

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am a full-stack developer with experience in QA testing and languages like Python, Cairo, Solidity, React, and JavaScript.
How I plan on tackling this issue
Step 1: Set HTML and Body Height
Set the height of the HTML and body elements to 100%:
Step 2: Set Container Height
Set the height of the container element to 100%:

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I have worked on a few web designs before ensuring that they are fully responsive making it so web applications fit various screen sizes perfectly which I think perfectly resonates with this issue.
How I plan on tackling this issue
I will start by modifying the page layout's CSS with flexbox or grid to make the content adaptively fill the screen's height and width. I’ll account for the warning banner to ensure that, even if it’s removed, the page still occupies 100% of the screen without scrolling. Lastly, I'll test the layout on different screen sizes to confirm full responsiveness and usability.
I would love to work on this issue, ETC 1-2 days

My background and how it can be leveraged: *
I'm a full stack developer (Blockchain and React) with 3years experience in react.
With my 3 years react experience I can handle this issue if assigned to me.
How I would approach the problem?
I'll inspect the current jsx/html structure and CSS, identify which elements are causing overflow or underflow, check for any fixed height containers that might be restricting full-height layout.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
hello i am a frontend dev and blockchain developer
please can i work on this issue :)
How I plan on tackling this issue
To ensure the page fit 100% of the screen i will imply the following below:

Adjusting CSS Styles:

Set the body and main container height to 100vh to utilize the full viewport height.

Ensure margins and paddings do not cause overflow.

Handling the Warning Banner:

Use CSS media queries or JavaScript to adjust the layout dynamically based on the presence of the banner, ensuring the page still fits without scrolling when the banner is removed.

Testing Responsiveness:

Test the layout on different screen sizes and resolutions to confirm it consistently fits the viewport.


Only server2 downloaded successfully.

Hi it seems server2 only downloaded successfully for me like to check if anyone is facing this issue too
I am using windows 10, I actually did the same steps as the video however somehow only server2 downloaded successfully I do not have the other 2 vm installed.

I'm experiencing the same issue only on a Mac.

I am experiencing the same with Oracle Linux Server 8.6
[root@kheixi ~]# vagrant global-status
id       name    provider   state   directory
4911877  server2 virtualbox running /root/bin/rhcsa8env
1b25a36  repo    virtualbox running /root/bin/rhcsa8env
The above shows information about all known Vagrant environments
on this machine. This data is cached and may not be completely
up-to-date (use "vagrant global-status --prune" to prune invalid


Long project names mess up layout on mobile screens

Expected Behavior
Project cards for projects with long names have a maximum size of the screen width.
Actual Behavior
Long project names mess up the layout for mobile screen size, because there’s no auto line breaks or some other overflow handling in place to keep the size of the project card at max of the screen width. So the project card extends beyong the page background, and allows for the whole page scroll horizontally.
Steps to Reproduce the Problem

Login and submit a project with a very long name
Search for it on a mobile screen size

Needs some CSS knowledge. I figure it makes sense to still see the full project name (no ellipsis or the like)?

I'm not sure why I can't assign myself to this issue, but I'll pick up this issue this week


Errors of client.chat.sendTextMessage() method

There seems to be some parsing/escaping issues on the .sendTextMessage() method.
if I try to send "hello world" error is caused by quotes.
Unhandled exception:
Evaluation failed: SyntaxError: missing ) after argument list
#0      ExecutionContext._evaluateInternal (package:puppeteer/src/page/execution_context.dart:151:11)
<asynchronous suspension>
#1      ExecutionContext.evaluate (package:puppeteer/src/page/execution_context.dart:76:20)
<asynchronous suspension>
#2      WpClientDesktop.evaluateJs (package:whatsapp_bot_flutter/src/clients/wpclient_desktop.dart:24:22)
<asynchronous suspension>
#3      WppChat.sendTextMessage (package:whatsapp_bot_flutter/src/wpp/wpp_chat.dart:19:12)
<asynchronous suspension>

if I try to send hello world\nnext line error is caused by \n.
Unhandled exception:
Evaluation failed: SyntaxError: Invalid or unexpected token
#0      ExecutionContext._evaluateInternal (package:puppeteer/src/page/execution_context.dart:151:11)
<asynchronous suspension>
#1      ExecutionContext.evaluate (package:puppeteer/src/page/execution_context.dart:76:20)
<asynchronous suspension>
#2      WpClientDesktop.evaluateJs (package:whatsapp_bot_flutter/src/clients/wpclient_desktop.dart:24:22)
<asynchronous suspension>
#3      WppChat.sendTextMessage (package:whatsapp_bot_flutter/src/wpp/wpp_chat.dart:19:12)
<asynchronous suspension>

I am sure there will be more errors down the rabbit hole waiting to be discovered, I tried to debug but since I have no experience with puppeteer, can't do much, do you have any idea to resolve this issue?

ok so I literally just used chatgpt to fix this issue 🤣
This is to fix newlines \n
/// Use [JsParse] extension on data we pass in Javascript string
extension JsParser on dynamic {
  dynamic get jsParse {
    if (this == null) {
      return null;
    } else if (runtimeType == String) {
      return '''"${this.replaceAll("\n", "\\n")}"''';
    } else {
      // return same for now
      return this;
    }
  }

@fenchai23 ok thats great , can you put a PR for the fix

@fenchai23 ok thats great , can you put a PR for the fix

I could but I am not 100% sure this method is the best, I tried a few other characters and it still breaks, so far I haven't got the time to properly debug, but it should at least be able to handle quotes and backslash.
I will see if I can find a better solution.

@fenchai23 fixed in https://github.com/rohitsangwan01/whatsapp_bot_flutter/pull/13
new update available : https://pub.dev/packages/whatsapp_bot_flutter


How to create custom GroupAttributes

I wanted to use MarkupAttributes to allow me to overcome a limitation of PropertyDrawers.
I have multiple properties like this:
public SomeClass PropertyA
public SomeClass PropertyB
public SomeClass PropertyC

I want to divide them into several groups like this:
[MyAwesomeGroup("Category A")] public SomeClass PropertyA
[MyAwesomeGroup("Category B")] public SomeClass PropertyB
[MyAwesomeGroup("Category A")]public SomeClass PropertyC

I want to create a custom drawer that creates a single(!) editor for each group (so in this example even though I have 3 properties, I end up with 2 editors).
Is this possible with MarkupAttributes? It looks comparable to the TitleGroup-Attribute.
Is there any information how to extend your system with custom attributes?

What do you mean by two editors? You mean PropertyA and PropertyC should have the exact same value?

No, but if possible I'd like to execute the editor code per group only once.
To be more specific: I would like to draw a button for each group that opens a popup menu (comparable to the way the EventTrigger editor from the Unity UI works)

There is no easy way to make your own group type. If it is a very specific editor - one off thing - I think writing it as usual is the way. You could use MarkupGUI class to create MarkupAttribute style grouping in this custom inspector.
There is also a way to add custom things to the inspector before, after or instead of any property https://github.com/gasgiant/Markup-Attributes#custom-marked-up-inspectors
You could do something like this
[TitleGroup("Category A")]
public SomeClass PropertyA
public SomeClass PropertyC

[TitleGroup("Category B")]
public SomeClass PropertyB

and then make a custom MarkedUpEditor that would manually add buttons after, say, properties C and B. But, obviously, you would have to add a button to each group you create manually.

But this would not prevent the properties from being drawn in the editor.
If I could add something to the wishlist for this library it would be make it possible to add custom attributes. I assume that this is rather difficult, but it would allow to write really clean things that (so far) only Odin is capable of (and Odin cannot be included in custom AssetStore products)

Could you, please, elaborate on what you mean by a custom attribute here? Or maybe point to Odin documentation for an example.
Do you mean like a TitleGroup modification that adds a button below it or something more complex?


I can't get site.Params.background or anything in config.yaml parameters

Question

I can't get site.Params.background or anything in config.yaml parameters. I tried to do  for background and disabling newsletter  but both are not working.  I think it cannot read config.yaml. How can I fix it?

Make sure you don't have both config.yaml and config.toml files. If you point me to your repository, I can take a look.

Yes, I did  and done. Thank you.


it is weird when open goneovim after click icon on Mac

it is normal that i open if from command line. but after i open it from icon, it show only a black screen with nothing.
ON:
Macbook air M1

After digging, I find that after create a link from the nvim execution file to the directory "/usr/local/bin", the application can be opened. BUT some other errors happened.

Finnally, i fix this by creating a link "~/.zshenv" to "~/.zshrc", since vim gui does not load zshrc.

Hi
Sorry for the late reply. And I am glad to hear that you have solved the problem.
When goneovim is launched from the application icon on MacOS, it uses a shell program defined by the $SHELL environment variable to set environment variables in the application that can be exported in terminal mode.
(ref: https://github.com/akiyosi/goneovim/blob/master/editor/editor.go#L517-L545)
This process allows goneovim to call the nvim.
I think your solution is the correct one.


Update entitlement-management-overview.md

@marcelodiiorio : Thanks for your contribution! The author(s) have been notified to review your proposed change.


trouble starting project

Not sure if I have configured things correctly,
But my assets/stylesheets directory has not added the foundation library.
The foundation_and_overrides.scss file does not have any of the includes either.
https://github.com/Davey-Wright/foundation-test/tree/master/app/assets/stylesheets
Am i doing something wrong here? I have followed the steps exactly as instructed, but am having no luck with adding foundation to rails.

Same issue with me. Trying out foundation the first time with Rails 5.2 and followed the README but it doesn't work. Also, there are no import statements of 'motion-ui' in the foundation_and_overrides.scss file.


:seedling: convert Webhook check to probes

What kind of change does this PR introduce?
feature

[x] PR title follows the guidelines defined in our pull request documentation

What is the new behavior (if this is a feature change)?**
This PR converts the Webhook check to probes

[x] Tests for the changes have been added (for bug fixes/features)

Which issue(s) this PR fixes
NONE
Does this PR introduce a user-facing change?
NONE

@spencerschrock @laurentsimon I have rewritten so it no longer has the hasWebhooks probe and uses OutcomeNotApplicable instead. PTAL


No. of emails sent per minute/hour

What is the maximum limit allowed per minute/hour for sending emails using Email communication service? By default, For all developers, the limits are 30 mails sent per minute and 100 mails sent per hour.

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

ID: d037be51-56fb-789d-9559-c03083d4bc6f
Version Independent ID: 30445a61-0ae0-789d-744f-f09b4f502eda
Content: Email client library overview for Azure Communication Services - An Azure Communication Services concept article
Content Source: articles/communication-services/concepts/email/sdk-features.md
Service: azure-communication-services
GitHub Login: @bashan-git
Microsoft Alias: bashan

@anilvem1
Thanks for your feedback! We will investigate and update as appropriate.


Rails 5 deprecation warning.

Using alias_method_chain is deprecated in Rails 5.

This is the full deprecation message I see:

DEPRECATION WARNING: alias_method_chain is deprecated. Please, use Module#prepend instead. From module, you can access the original method using super. (called from <top (required)> at /Users/roryokane/path/to/backend/config/application.rb:8)

The message is annoying because it is printed when running any rails command – not just rails server or rails console, which have a lot of output of their own, but even rails routes and rails middleware, whose only function is to output something. The deprecation message clutters up the output, especially when wrapped to fit the terminal window:
$ rails middleware
DEPRECATION WARNING: alias_method_chain is deprecated. Please, use Module#prepen
d instead. From module, you can access the original method using super. (called
from <top (required)> at /Users/roryokane/longer/path/to/backend/config/applicat
ion.rb:8)
use Rack::Sendfile
use Rack::Cors
use ActionDispatch::Static
…
use Rack::Head
use Rack::ConditionalGet
use Rack::ETag

Another bad thing about the deprecation message is that it doesn’t identify which included gem is the cause – the referenced line in my app is just Bundler.require(*Rails.groups). It took quite some searching to figure out that this gem was the culprit. The poor wording of the error message is not this gem’s fault, but it still provides a bad user experience.

Link: @kevintyll’s pull request “Eliminate Rails 5 deprecation warning.” fixes this issue.


Unable to run containers with MountFlags=shared and selinux

Description

Steps to reproduce the issue:

boot coreos-alpha (or beta) node
mkdir /etc/systemd/system/docker.service.d
echo '[Service] MountFlags=shared' > /etc/systemd/system/docker.service.d/mountflags.conf
systemctl daemon-reload
systemctl restart docker

$ docker run -it alpine sh
docker: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "exec: \"sh\": executable file not found in $PATH".

Describe the results you received:
Unable to run any containers.
Describe the results you expected:
Able to run a container
Additional information you deem important (e.g. issue happens only occasionally):
I suspect it has something to do with selinux and containerd split, this worked with docker 1.11.2
Output of docker version:
Client:
 Version:      1.13.1
 API version:  1.26
 Go version:   go1.7.3
 Git commit:   092cba3
 Built:        Wed Mar  1 23:26:07 2017
 OS/Arch:      linux/amd64

Server:
 Version:      1.13.1
 API version:  1.26 (minimum version 1.12)
 Go version:   go1.7.3
 Git commit:   092cba3
 Built:        Wed Mar  1 23:26:07 2017
 OS/Arch:      linux/amd64
 Experimental: false

Output of docker info:
Containers: 21
 Running: 0
 Paused: 0
 Stopped: 21
Images: 4
Server Version: 1.13.1
Storage Driver: overlay
 Backing Filesystem: extfs
 Supports d_type: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: aa8187dbd3b7ad67d8e5e3a15115d3eef43a7ed1
runc version: 9df8b306d01f59d3a8029be411de015b7304dd8f
init version: N/A (expected: 949e6facb77383876aeff8a6944dde66b3089574)
Security Options:
 seccomp
  Profile: default
 selinux
Kernel Version: 4.10.1-coreos
Operating System: Container Linux by CoreOS 1339.0.0 (Ladybug)
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 1.466 GiB
Name: c43
ID: Y4YJ:URUJ:6TD2:O6HK:KMWW:JGK5:5Q4D:WI2D:F7AU:JK4A:RWKI:PL6Y
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

Additional environment details (AWS, VirtualBox, physical, etc.):
Reproducible with https://github.com/coreos/coreos-vagrant

Hmm, the official docker packages (ie for ubuntu/debian/ec) uses the default mount flags, which would be shared.
It sounds like this is likely an issue with coreos's build of docker.

I suggest reporting this with CoreOS, as this looks to be specific to their configuration. I'll go ahead and close this issue, but feel free to continue the conversation 👍

@kylebyerly-hp did you report this to CoreOS? if so, can you post the link here? i want to keep track

@kylebyerly-hp do you have a solution or workaround? I'm facing the same issue.

@kylebyerly-hp Hit the same issue in docker 18.09.5  Current docs say set MountFlags=shared but this does not work.

For docker 18.09 and up make sure to not specify any MountFlags; see https://docs.docker.com/engine/release-notes/#18091


Encoding file index error.

Fix an index error that wasn't found the other day in the pair coding session.

@AESilky That fixed the problem. Thank you!


Regression - Multiple Search Dropdown clears search on selection

Hi everyone -
I hope all is well.
I'm facing an issue where the Multiple Search Selection dropdown clears the search after an item is selected. See below for an example:
https://camo.githubusercontent.com/6c62ec71f34fd76cea9db1ee86b43c5871c41732/687474703a2f2f672e7265636f726469742e636f2f4f71716e5a44485235752e676966
According to #1954 this issue was resolved (see here), but it appears there was a regression. When I type "Ma" and select it clears the dropdown search selection. It looks like this is working on the core Semanatic-UI page, but not on the React version.
Best,
Andrew

Any thoughts or potential direction on how to resolve this? I can take a crack at a PR if it's a simple fix. @levithomason @creedmangrum

Hi @AndrewCi I actually haven't been following this. I'm still using a version where this was working. I'm a bit busy now, but in the next couple days I might be able to take a look. Maybe @levithomason could help out though. My fix that i proposed wasn't originally added as it was fixed from another PR.

Hi creed - thanks for getting back to me. What version are you using? If I could identify I might consider moving to that version as a stopgap.

@AndrewCi @creedmangrum it's not a regression it's a fix that was done in<EMAIL_ADDRESS>(#3317) to align the behavior between click and Enter (#2162) & SUI behavior.
To keep previous behavior when searchQuery is kept you can handle searchQuery manually, I made a CodeSandbox: https://codesandbox.io/s/goofy-platform-5mol3?file=/example.js
Please let me know if it works for you 👍

@AndrewCi @creedmangrum it's not a regression it's a fix that was done in<EMAIL_ADDRESS>(#3317) to align the behavior between click and Enter (#2162) & SUI behavior.
To keep previous behavior when searchQuery is kept you can handle searchQuery manually, I made a CodeSandbox: https://codesandbox.io/s/goofy-platform-5mol3?file=/example.js
Please let me know if it works for you 👍

@layershifter thank you for the response. This works 90%. The only difference between your fix and the standard Semantic UI behavior is that when a user selects a response based on a search query the typed text still appears. For example, if you type in "me" in your example two options appear. In your example when an option is selected "me" still appears in the dropdown; however, in the standard Semantic UI this "me" input is cleared upon selection with the drop down values still loaded.
Any thoughts? I was playing around with the available props and couldn't get the behavior to line up 1:1.

I updated the CodeSandbox to match that behavior: https://codesandbox.io/s/goofy-platform-5mol3?file=/example.js. Is that what you would like to archive?
IMO, it's very confusing especially from accessibility POV as user doesn't about his input 🤔

@layershifter awesome work thank you so much! This was exactly the behavior I expected and it matches the behavior from the base Semantic UI library. I actually think it's better from a usability perspective - since the results are already loaded upon search you eliminate the need for a user to have to backspace to clear their original search if they have searching for multiple keywords. For example, if I type in "me" which loads 2 results and then I want to search for "cat" I need to backspace twice to clear "me", with this currently iteration you eliminate that backspace step.