[RFP]: Introducing Flexible Pswap Rewards for vesting

Proposal Due Date
08/01/2024
Proposal Overview
The proposal for revising vesting PSWAP tokens to allow stakers to sell a portion of their pending rewards on a secondary market at a discount offers several potential benefits to the SORA ecosystem:
Liquidity Enhancement: By enabling stakers to sell a portion of their pending vesting rewards on a secondary market, the proposal increases liquidity for PSWAP tokens. This liquidity can improve price stability and trading volume on the secondary market, making PSWAP tokens more attractive to investors and traders.
Flexible Reward Distribution: The proposal allows stakers to have greater flexibility in managing their vesting rewards. Instead of waiting for the full vesting period to receive their rewards, stakers can choose to monetize a portion of their rewards immediately by selling them on the secondary market, providing them with access to liquidity when needed.
Market Efficiency: Allowing stakers to sell their pending vesting rewards on a secondary market creates an additional avenue for price discovery and market efficiency. It incentivizes market participants to actively trade PSWAP tokens, leading to more efficient price formation and a more liquid trading environment.
Yield Generation: Users who hold vesting PSWAP tokens but do not wish to sell them on the secondary market can choose to loan out their tokens back to the Polkaswap platform in exchange for a yield. This provides an opportunity for users to earn additional income on their holdings while contributing to the liquidity of the PSWAP token market.
Integration with SORA Ecosystem: The proposal can seamlessly integrate with the broader SORA ecosystem, leveraging its interoperability features and decentralized finance (DeFi) capabilities. PSWAP tokens serve as a utility token within the ecosystem, enabling users to participate in governance, liquidity provision, and other activities.
Incentive Alignment: By allowing stakers to sell a portion of their pending vesting rewards, the proposal aligns the incentives of stakers with the broader goals of the SORA ecosystem. Stakers can benefit from immediate liquidity while still contributing to the security and stability of the network through their continued participation in staking.
Overall, the proposal for revising vesting PSWAP tokens to enable stakers to sell a portion of their pending rewards on a secondary market and loan out their tokens for yield provides benefits such as liquidity enhancement, flexible reward distribution, market efficiency, yield generation, integration with the SORA ecosystem, and incentive alignment.
Proposal Goals
The goal of the proposal to revise vesting PSWAP tokens to allow stakers to sell a portion or all  of their pending rewards on a secondary market or loan out their tokens for yield is multifaceted and addresses several key objectives:
Enhanced Liquidity: One of the primary goals is to increase liquidity for PSWAP tokens by providing stakers with the option to sell a portion of their pending vesting rewards on a secondary market. This addresses the problem of limited liquidity in the PSWAP token market, making it easier for investors and traders to buy and sell PSWAP tokens at fair prices. This also creates more incentives for participants to provide more liquidity.
Flexible Reward Management: The proposal aims to give stakers greater flexibility in managing their vesting rewards. Instead of being locked into a fixed vesting schedule, stakers can choose to monetize a portion of their rewards immediately by selling them on the secondary market. This solves the problem of illiquidity associated with traditional vesting schedules, where stakers may have to wait for an extended period to access their rewards.
Market Efficiency: By allowing stakers to sell their pending vesting rewards on a secondary market, the proposal promotes market efficiency and price discovery for PSWAP tokens. It incentivizes active trading and participation in the PSWAP token market, leading to more accurate price formation and a more liquid trading environment.
Yield Generation: Another goal of the proposal is to provide stakers with an opportunity to earn additional income on their holdings by loaning out their tokens for yield. This addresses the problem of idle assets by allowing stakers to put their PSWAP tokens to work and earn a return on their investment, thereby maximizing the value of their holdings.
Integration with DeFi Ecosystem: The proposal aims to integrate PSWAP tokens into the broader decentralized finance (DeFi) ecosystem by enabling yield-generating opportunities such as lending. This aligns with the broader goals of the SORA ecosystem to facilitate decentralized financial services and empower users to participate in various DeFi activities.
Overall, the goal of the proposal is to enhance the liquidity, flexibility, and utility of PSWAP tokens while promoting market efficiency, yield generation, and integration with the broader DeFi ecosystem within the SORA ecosystem. By addressing these objectives, the proposal aims to improve the overall user experience and ecosystem dynamics surrounding PSWAP tokens.
Scope of Work
Smart Contract Development:
Develop smart contracts to facilitate the sale of pending vesting rewards on a secondary market and the loaning out of PSWAP tokens for yield.
Implement functionality for stakers to lock their pending vesting rewards and issue tradable tokens representing their vested and tradable portion.
Integrate lending protocols or develop custom lending contracts to enable users to loan out their PSWAP tokens and earn yield.
Protocol Design and Development: Design the protocol for managing vesting rewards, including mechanisms for calculating vested amounts, issuing tradable tokens, and updating vesting schedules.
Develop protocols for trading pending vesting rewards on a secondary market, including order matching, settlement, and custody mechanisms.
Implement lending protocols or integrate with existing DeFi lending platforms to enable users to loan out their PSWAP tokens and earn yield.
User Interface Enhancements: Update the user interface of the staking platform to provide stakers with options to manage their vesting rewards, including selling a portion on a secondary market and loaning out tokens for yield.
Design intuitive interfaces for buyers on the secondary market to purchase pending vesting rewards and for lenders to provide liquidity by loaning out PSWAP tokens.
Ensure seamless integration with the existing user interface of the SORA ecosystem to provide a cohesive user experience.
Security and Risk Management:
Conduct comprehensive security audits of smart contracts, protocols, and user interfaces to identify and mitigate potential vulnerabilities and security risks.
Implement risk management mechanisms to safeguard users' funds and protect against potential exploits or attacks on the platform.
Develop emergency protocols and procedures to respond to security incidents or unforeseen events effectively.
Regulatory Compliance and Legal Considerations:
Conduct legal research and analysis to ensure compliance with relevant laws and regulations governing securities trading, lending activities, and financial services.
Develop compliance frameworks and risk management policies to address regulatory requirements and mitigate legal risks associated with trading and lending PSWAP tokens.
Obtain necessary licenses or approvals from regulatory authorities to operate as a trading platform and lending platform and offer financial services to users.
Community Engagement and Education: Engage with the community to gather feedback, address concerns, and promote awareness of the new features and opportunities available for managing vesting rewards.
Provide educational resources, tutorials, and documentation to help users understand how to buy, sell, and loan PSWAP tokens and navigate the new features seamlessly.
Foster a vibrant and engaged community of stakers, traders, lenders, and developers to support the growth and adoption of the new features within the SORA ecosystem.
Market Adoption and Integration: Develop marketing strategies and campaigns to promote the new features and attract users to participate in trading and lending PSWAP tokens.
Integrate the new features seamlessly with existing components of the SORA ecosystem, including the staking platform, wallet, and other DeFi protocols.
Collaborate with other projects and platforms within the Polkadot ecosystem to leverage synergies and expand the reach of the new features.
Overall, implementing the proposal to revise vesting PSWAP tokens to enable stakers to sell a portion of their pending rewards on a secondary market or loan out their tokens for yield requires a coordinated effort involving smart contract developers, protocol engineers, user interface designers, security professionals, legal experts, community managers, and marketing specialists. It also requires thorough testing, compliance with regulatory requirements, and ongoing education and engagement with the community to ensure the successful integration of the new features into the SORA ecosystem.
Current Roadblocks and Barriers to Success
While the proposal to revise vesting PSWAP tokens to enable stakers to sell a portion or all of their pending rewards or loan out their tokens for yield offers numerous benefits, there are several considerations and potential challenges to be mindful of:
Market Impact: Allowing stakers to sell a portion or all  of their pending rewards on a secondary market will not create downward pressure on the price of PSWAP tokens, especially if there is a significant influx of sell orders. To sell rewards which are not yet vested you will be transferring or selling the ownership of  credited  tokens to another wallet (for vesting) which will NOT create a sell pressure on PSWAP. So in market impact there is no barriers or difficulties.
Risk Management: Facilitating the sale and lending of PSWAP tokens introduces additional risk factors, including counterparty risk, market volatility, and liquidity constraints. Proper risk management mechanisms must be implemented to protect users' funds and ensure the stability of the platform.
Regulatory Compliance: Trading and lending activities involving PSWAP tokens may be subject to regulatory scrutiny and compliance requirements in different jurisdictions. It's essential to navigate regulatory challenges effectively and ensure compliance with relevant laws and regulations to avoid legal risks and regulatory enforcement actions.
Security and Trust: The security of the platform and the integrity of smart contracts and protocols are paramount. Any vulnerabilities or exploits could result in financial losses for users and damage to the reputation of the SORA ecosystem. Robust security measures and continuous monitoring are necessary to maintain trust and confidence in the platform.
User Education and Support: Providing clear and comprehensive guidance to users on how to participate in selling and lending activities is crucial. Users need to understand the risks, benefits, and procedures involved in managing their vesting rewards effectively. Ongoing support and education are essential to ensure a positive user experience and minimize errors or misunderstandings.
Liquidity Management: Managing liquidity on the secondary market and lending platform is essential to ensure smooth trading and lending operations. Adequate liquidity provision, order matching mechanisms, and risk controls are necessary to maintain a healthy and efficient market and prevent liquidity shortages or price manipulation.
Community Engagement: Building and maintaining community trust and engagement is vital for the success of the proposal. Transparent communication, responsiveness to feedback, and inclusive decision-making processes can foster a supportive and collaborative community ecosystem that contributes to the long-term success of the platform.
Evaluation Metrics and Criteria
Technical Implementation:
Smart Contracts: All necessary smart contracts for facilitating the sale and lending of PSWAP tokens are developed, audited, and deployed on the blockchain.
Protocol Development: The protocol for managing vesting rewards, trading on the secondary market, and lending activities is designed, implemented, and tested for efficiency, security, and reliability.
User Interface: The user interface of the staking platform and other relevant components is updated to provide users with options to manage their vesting rewards, including selling and lending activities.
Regulatory Compliance: Compliance Framework: A comprehensive regulatory compliance framework is established, addressing legal requirements for trading, lending, and financial services involving PSWAP tokens.
Licenses and Approvals: Necessary licenses or approvals from regulatory authorities are obtained, ensuring compliance with applicable laws and regulations governing securities trading and financial activities.
Security and Risk Management: Security Audits: Smart contracts, protocols, and user interfaces undergo thorough security audits to identify and mitigate potential vulnerabilities and security risks.
Risk Management Mechanisms: Robust risk management mechanisms are implemented to protect users' funds and ensure the stability and security of the platform, including measures for addressing counterparty risk, market volatility, and liquidity constraints.
User Education and Support: Educational Resources: Comprehensive educational resources, tutorials, and documentation are provided to help users understand how to participate in selling and lending activities effectively and manage their vesting rewards.
Customer Support: Adequate customer support channels are established to address user inquiries, provide assistance, and resolve issues related to selling and lending activities.
Liquidity Provision: Market Depth: Adequate liquidity is provided on the secondary market and lending platform to ensure smooth trading and lending operations, with mechanisms in place to manage liquidity shortages and prevent market manipulation.
Incentive Mechanisms: Strategies to incentivize liquidity provision and active participation in selling and lending activities are implemented to encourage market participation and ensure a vibrant ecosystem.
Community Engagement: Community Outreach: Transparent communication and engagement with the community are maintained throughout the implementation process, with regular updates, feedback mechanisms, and opportunities for community input.
Adoption and Integration: The proposal is successfully integrated into the broader SORA ecosystem, with seamless interoperability with existing components and collaboration with other projects and platforms within the ecosystem.
Once these criteria are met, the proposal to revise vesting PSWAP tokens to enable selling and lending activities can be considered "done" and successfully integrated into the SORA ecosystem.
Submission Requirements
Alignment with Proposal Objectives: The submission should clearly demonstrate how it aligns with the objectives outlined in the proposal for revising vesting PSWAP tokens. It should address the goals of enhancing liquidity, providing flexible reward management options, promoting market efficiency, enabling yield generation, and integrating with the broader SORA ecosystem.
Technical Feasibility: The submission should provide a detailed technical plan for implementing the proposed changes to the vesting PSWAP token system. It should demonstrate a clear understanding of the technical requirements and challenges involved and outline a feasible roadmap for implementation.
Regulatory Compliance: The submission should address regulatory considerations and compliance requirements associated with the proposed changes. It should outline plans for navigating regulatory challenges effectively and ensuring compliance with relevant laws and regulations governing trading, lending, and financial services involving PSWAP tokens.
Security and Risk Management: The submission should prioritize security and risk management, with plans for implementing robust security measures and risk management mechanisms to protect users' funds and ensure the stability and security of the platform. It should address potential vulnerabilities and security risks associated with the proposed changes.
User Experience and Support: The submission should prioritize user experience and provide plans for enhancing the user interface, providing educational resources, and offering customer support to help users understand and navigate the changes effectively. It should ensure a positive user experience and minimize errors or misunderstandings.
Liquidity Provision: The submission should address plans for managing liquidity on the secondary market and lending platform to ensure smooth trading and lending operations. It should outline strategies for incentivizing liquidity provision and preventing liquidity shortages or market manipulation.
Community Engagement: The submission should demonstrate a commitment to community engagement and participation, with plans for transparent communication, feedback mechanisms, and opportunities for community input throughout the implementation process. It should foster a supportive and collaborative community ecosystem that contributes to the success of the proposed changes.
By fulfilling these criteria, we will be  paving the way for the successful implementation of the proposed changes to the vesting PSWAP token system within the SORA ecosystem.
Submission Method
Blockchain: Mainnet
Project Due Date
09/12/2024
Budget Amount
This is at the discretion of the development team.

It would be a good idea to build fees into this tool that are charged directly to the PSWAP to speed up its burn.
Also, it would be great if a secondary market for PSWAP was organized through NFT minting, which would also allow you to move your vested PSWAP between your accounts without selling.


mert fails if dev contains empty lines

tuning fails if either source or target side of the development set contains empty lines
this can happen if any line of the original set is actually empty, or contains only xml tags (wchi are removed in the tuning phase
possible solutions:

insert the removal of such "empty" lines in the preprocessing step;
insert the removal of such "empty" lines directly in mert-moses.pl

In both case, the removal has to be done considering source and target together in order to keep sentence alignment.

other ideas?

To me, solution 2 is the best one because it solves a "bug" of the mert tuning, and has minimal or no impact on the rest of the system
if you agree on option 2, i volunteer to fix the bug.

100% with you on that.
Just please notice: because the problem is also in the master/develop branch, please implement the fix in the develop branch and then marge from develop to features/neural_decoder (the branch I'm assuming you actually want the fix into).
In this way we will have both branches (develop and features/neural_decoder) fixed, without interfering with the actual state of the branches.
Thanks Nicola!


Animate the paid checkmark when paying expense

Details

We want to also animate the checkmark when paying expense.
Fixed Issues

$ https://github.com/Expensify/App/issues/48036
PROPOSAL: https://github.com/Expensify/App/issues/48036#issuecomment-2326224712
Tests

Same as QA Steps

[x] Verify that no errors appear in the JS console

Offline tests

Same as QA Steps
QA Steps

Open your policy expense chat
Submit a request. Approve if needed.
Pay the money request
Verify the pay button animates (as shown https://github.com/Expensify/App/issues/48036#issuecomment-2316711777)

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/user-attachments/assets/a2824f15-2311-43f1-b302-b2c602d78e7f

Android: mWeb Chrome

https://github.com/user-attachments/assets/2916782e-e846-42eb-a5b9-2e617513a8ca

iOS: Native

https://github.com/user-attachments/assets/b810b0e4-79b5-40ad-b482-a0ad4195b242

iOS: mWeb Safari

https://github.com/user-attachments/assets/d871fc79-d12f-4aca-be50-f3a3749862cb

MacOS: Chrome / Safari

https://github.com/user-attachments/assets/f30883bd-6ecb-46d4-b927-82177b64005e

MacOS: Desktop

https://github.com/user-attachments/assets/86cbc9f5-c5e9-42c1-b6ae-57e7274a20f2

Done

Done.
It's quite different though because looks like on the GIF, there are 2 preview messages, 1 fades out, 1 fades in, while in the component, we reuse 1 text only.
https://github.com/user-attachments/assets/3486aa3c-0c31-415f-bbb8-6580a604f61c

The recording in the original post looks pretty good. Would be cool to delay the checkmark animation about 300ms to ensure it catches the attention a bit more.

The recording in the original post looks pretty good. Would be cool to delay the checkmark animation about 300ms to ensure it catches the attention a bit more.

@roryabraham @dubielzyk-expensify Checkmark Delay 300ms + (Fade replaced with) Bounce (using withSpring)
https://github.com/user-attachments/assets/0fd44ac4-04c3-47fc-b356-e591d81c88f5
Shorter bounce duration (200ms)
https://github.com/user-attachments/assets/c739bdff-caac-435e-958b-b059bd38c84e

Lovely! I am digging the shorter duration version more I think.

Same! I am loving the 200ms bounce checkmark.

Great, pushed the update

🚀 Deployed to staging by https://github.com/roryabraham in version: 9.0.40-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Drop future install-requirement

The future requirement has only been used for the basestring type, which was vendored into _utils.py in df9bd7316f and isn't actually necessary.
By stripping out the future requirement, ffmpeg-python no longer has any install-requirements, making installation less error-prone in certain cases.
Fixes #228 and #130.

Hmm, actually the builtins module comes from future as well and is referenced in several places, so this PR is a bit larger than expected. I'll probably hold off on merging it until others get a chance to  try it and comment in case it breaks anything.
Python2+Python3 cross-compatibility can sure be annoying/finnicky, but Python 2 will be going away soon (for better or worse).

Just for reference, the project I'm using without future: https://github.com/poetaster/harbour-clipper


update nvim-lsp-installer entry

Checklist:

[x] The plugin is specifically build for Neovim.
[x] The lines end with a .. This is to conform to awesome-list linting and requirements.
[x] It's not already on the list.
[x] It supports treesitter syntax if it's a colorscheme.

Thanks for the PR!


Backport: Node Template - 'Location' on the UI does not get updated when you edit and save an AWS node template

Backport of rancher/rancher#19396

➤ David Nuzik commented:
Version: v2.2.3-rc1
I confirmed this is now working as expected. When I change the region for my aws template this is updated in the UI now including other locations in the same region (us-west-2a, us-west-2b, etc)
I also tried with a digitalocean template and the location will update for that template as well.


chore: add arch diagrams - 3.1

Closing this until we know the slug of the jump start solution in the Cloud Console. that will determine the file names.

/gcbrun

/gcbrun


[Question]: Reliability of the APIs in use

First of all, let me tell you I admire the effort you've put into digging through Next.js internals and putting next-extra together. Kudos! 🙇
The libraries make use of staticGenerationAsyncStorage and requestAsyncStorage. Both are undocumented by the Next.js team and imported from paths that seem to be for internal use only.
Could you tell me your take on their reliability/stability? Any insights you can give me would be useful. Thanks!

Hey @typeofweb,
Thanks, I appreciate your support!
For the stability, since the majority of APIs that are exposed from the package use these storages, and I made read-only access to them, it makes it stable enough.
For the reliability, NextJs is nearly based on these storages for building requests and end responses for everything. If they want to make changes to it, it's going to be a major level release, which makes the incoming changes predictable.
These APIs are not documented for obvious reasons. I am not a Vercel insider nor in the NextJs developer team, but I highly recommend you read the NextJs source code itself to know where and how these storages are being used.
Here are some APIs that everybody uses and in underlying code, the staticGenerationAsyncStorage and requestAsyncStorage are being used.
import { headers, cookies } from 'next/headers';
import { redirect, permanentRedirect } from 'next/navigation';

For now, I only made for support for Next 14, and this package is NOT going to work in Next 15.

Hi @shahradelahi ! what do you mean by it's NOT going to work in Next 15 ? you don't plan to support Next 15 ?

Hi @Neodark7,
I'll make support for both Next 14 and Next 15, but the Next 15 is not stable yet. What I said before was for those who are using the canary version of Next 15.


[Bug]: UI Jank in the 'For you' screen

Is there an existing issue for this?

[X] I have searched the existing issues

Is there a StackOverflow question about this issue?

[X] I have searched StackOverflow

What happened?
Whenever the InterestsSelection is visible in the 'For you' screen, scrolling back to the InterestsSelection always janks heavily. Even the side scrolling of TopicSelection janks.
https://user-images.githubusercontent.com/5493586/168229747-17eafc4c-cc53-494e-92b5-894bc877cf9d.mp4
I'm observing this on Pixel 4a device.
Relevant logcat output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I believe this is expected on debug builds. More about that here: https://developer.android.com/jetpack/compose/performance#build-release
Are you able to reproduce the same behavior on a release build?


potential enhancement

The current Chatify only works on code. I think it would be more useful to make Chatify work on notes and even videos. It doesn't have to be embedded in Jupyter Notebook, a chatbot like the automatic customer service we saw on various applications including shopping websites would also be helpful. In that way, whatever question we have, we can directly open the chatbot and ask questions.

Thanks @wangshaonan!  Copying some comments from slack for our records:
the %%explain syntax is an iPython “magic” command.  those work by “hijacking” the contents of code cells and passing them to the relevant functions (specified wherever the magic command is defined/registered).  the way chatify works is that the contents of the code cell gets sent to the language model, along with a pre-defined prompt that depends on what you select in the chatify menus.
unfortunately there’s no built-in way of running magic commands on markdown cells, which is where those notes are defined.  it’d be nice to support markdown cells, though!  and support for other media, like videos, images, etc., would be neat too.  feel free to open an issue to request new features-- that way you can describe exactly what you’re thinking, and get credit for contributing your ideas to the project!  https://github.com/ContextLab/chatify/issues
i do suspect that it is possible to support those things, but i think it’d require (a) some hacking to change how those markdown cells are rendered and (b) some thinking about how the implementation would work.  for example:

how would chatify get triggered from markdown cells?  e.g., suppose the markdown cell contains the %%explain command on top.  does that mean it should be treated as a call to chatify?  if so, how should the notebook render that cell and/or respond?
should there be an “escape sequence”?  e.g., you can include a comment in front of the %%explain magic command in a code cell to prevent it from executing that magic command.  and since %%explain isn’t valid Python (except as a magic command), there’s no loss of function when its used to invoke chatify.  (it just uses the “magic command” infrastructure that is already in place.). but in markdown cells, it’s perfectly “valid” to include %%explain at the top of a cell.  How could you distinguish when the user intends to call chatify, versus if they just want the text “%%explain” to appear at the top of the cell, and get rendered as markdown?  (this is probably why iPython notebooks don’t support magic commands in markdown cells by default.)

one could also imagine creating a new magic command that works like %%explain, but instead of sending the text of the current code cell (where the magic command is called), it could instead read in the current notebook and returns the content of one or more other cells, potentially including markdown cells.  how should the syntax for that command work?  maybe something like: if you follow an %%explain command with a non-negative integer, it sends the contents of that cell instead of the current cell (where the current cell is the default if no cell ID is specified)?
videos are an interesting case too.  videos are displayed via iPython widgets, which are called in code cells.  technically you can already “explain” those cells using chatify.  however, chatify interprets those cells as code rather than trying to guess at what the code does on an arbitrarily deep level (e.g., by following links, actually running the code, etc.).  one could imagine hard-coding in some tweaks, e.g. if the only code a cell contains is a call to an ipython widget displaying a video, maybe there could be an additional tab that comes up that enables you do do something related to the content of that video (e.g., answering questions about the video’s transcript, etc.).  we’d need to then figure out what to do if multiple videos are embedded in a single code cell (e.g., do you then get multiple extra “video” tabs?).  and maybe it’d be good to support other types of media too, like interactive demos, embedded web pages, audio, animations, etc.
anyways, cool idea!


Dependency Tree is missing

The Swift Package Manager can show you a Dependency-Tree. But that works only on packages directly, not on projects. So you can never see a Dependency-Tree for your project.
If this tool could build a Depdency-Tree for your project, that would be fantastic.
I build a script for that, but having it in your tool would be better, especially since I don't have your experience and am not 100% sure if that's 100% resistent against edge-cases:
if [[ $1 == "" ]]; then
  echo "Missing build dir as 1st parameter"
  exit 1
fi

if [[ $2 == "" ]]; then
  echo "Missing project dir as 2nd parameter"
  exit 1
fi

BUILD_DIR=$1
PROJECT_DIR=$2

echo "Build dependencies tree"
cd "$BUILD_DIR/../../SourcePackages/checkouts"
exportFile="$PROJECT_DIR/dependencies-tree.md"
echo "# Dependencies trees for each Swift-Package" > "$exportFile"
echo "" >> "$exportFile"
echo "Build date: $(date '+%Y-%d-%m %a %H:%M:%S %Z')" >> "$exportFile"
echo "" >> "$exportFile"
for directory in */; do
  echo "Tree for $directory"
  echo "" >> "$exportFile"
  echo "## Tree for $directory" >> "$exportFile"
  pushd $directory
  swift package show-dependencies >> "$exportFile"
  echo "" >> "$exportFile"
  echo "" >> "$exportFile"
  popd
done

Hey @JD-CSTx, thanks for the idea! I think this new CLI tool is exactly what you are looking for.

Hey @JD-CSTx, thanks for the idea! I think this new CLI tool is exactly what you are looking for.

Thanks, but I need a compact overview, which the swift package manager already delivers in an ideal format.
The output of that tool looks horribly confusing.

Gotcha @JD-CSTx!
In my opinion this functionality does not fit 100% into this tool because 1. the main purpose is to get a file which lists all packages and 2. it just relies on files/directories instead of executing other CLI commands. However, it should be very easy for you to make your own tool with the logic of your bash script.


Carousel

This is ready to go, I made a few changes to make the titles not be cut off on mobile but at a certain point the longer titles overrun the header on the smallest screens. The liberal use of !important is due to importing the CSS from the React Carousel after loading the scss so I had to use important to get specificity.

Try to get this as close to the live site as possible. Remove the underline on hover. We could try to make the text subtly change color on hover using CSS transitions.


WebGL extensions

Hello, I think it is better to add a supported tables for WebGL extensions.
As you know, there is some of feature specified as extension in WebGL.
This is example,

GL_EXT_draw_buffers   the specification to use multiple render targets
EXT_blend_minmax        the specification to use minimum or maximum function in blending

The list of extensions information can be found in this article.
https://www.khronos.org/registry/webgl/extensions/

http://webglstats.com/ has some stats on extensions.
Shared Resources is one I'm particularly interested in:
Spec: https://www.khronos.org/registry/webgl/extensions/WEBGL_shared_resources/
Chrome: https://www.chromestatus.com/features/5486563022602240
Edge: https://developer.microsoft.com/en-us/microsoft-edge/platform/status/webglsharedresources
FireFox: ?
WebKit: ?

That would be very good stat to have.
webglstats.com hasn't updated since Feb 2016, which is nearly a year for now. Stats do get outdated there, and WebGL is progressing. Especially soon with WebGL 2, there are many webgl related stats could be tested.


benchmark failed to run due to argument number checking

Compiled with the latest commit:
commit 7111be49dd54cba44faa2bc6fbb46bff1b553517 (HEAD -> master, origin/master, origin/HEAD)
Author: ouguoyu<EMAIL_ADDRESS>Date:   Sun Jan 16 20:30:28 2022 +0800

    [fix] do not include opencv2/opencv2.hpp in unittest/benchmark

run the benchmark:
/home/zz/work/github/ppl.cv/deps/benchmark/src/benchmark_register.cc:313: Args: Check `ArgsCnt() == -1 || ArgsCnt() == static_cast<int>(args.size())' failed.
zsh: abort (core dumped)  ./pplcv_benchmark

my environment:
Linux x64

The call stack shows the copymakeborder_benchmark cause this crash
BENCHMARK_TEMPLATE(BM_Copymakeborder_ppl_x86, float, c1, ppl::cv::BORDER_TYPE_CONSTANT)->Args({320, 240, 320, 240})->Args({640, 480})->Args({1280, 720})->Args({1920, 1080})->Args({3840, 2160});

@ouonline Let me make an PR to fix those issues about compilation and run failures.


development branch required

The undocumented 'dev' branch at the moment is ahb-uri-updates. This is of course extremely confusing. We should merge this into the development branch.

Done


Update Shipment Document

Coverage increased (+0.05%) to 73.774% when pulling c22d067085f37648dc65b5c16cf1cdd473d9f576 on jackyrusly:dev into e933c0a24dbe37af748d11b3a3655086d7b0538f on danliris:dev.


[SPARK-35061][BUILD] Upgrade pycodestyle from 2.6.0 to 2.7.0

What changes were proposed in this pull request?
This PR bumps up the version of pycodestyle from 2.6.0 to 2.7.0 released a month ago.
Why are the changes needed?
2.7.0 includes three major fixes below (see https://readthedocs.org/projects/pycodestyle/downloads/pdf/latest/):

Fix physical checks (such as W191) at end of file. PR #961.
Add --indent-size option (defaulting to 4). PR #970.
W605: fix escaped crlf false positive on windows. PR #976

The first and third ones could be useful for dev to detect the styles.
Does this PR introduce any user-facing change?
No, dev-only.
How was this patch tested?
Manually tested locally.

Test build #137328 has started for PR 32160 at commit a9f9893.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41908/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41908/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41908/

Test build #137328 has finished for PR 32160 at commit a9f9893.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/137328/

Test build #137343 has started for PR 32160 at commit fe07e5c.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41922/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41922/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41922/

Test build #137343 has finished for PR 32160 at commit fe07e5c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/137343/

Thank you @dongjoon-hyun !


Yarn android

Description
first create clean project by:
npx react-native@latest init test
then run:
yarn
yarn start
run ios very well but when run android fails on line:
Task :app:checkDebugAarMetadata
Steps to reproduce
npx react-native@latest init test
yarn
yarn start
React Native Version
0.74
Affected Platforms
Runtime - Android, Build - MacOS
Areas
Other (please specify)
Output of npx react-native info
...
System:
  OS: macOS 14.5
  CPU: (12) arm64 Apple M2 Max
  Memory: 98.33 MB / 32.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 21.7.3
    path: ~/.nvm/versions/node/v21.7.3/bin/node
  Yarn:
    version: 1.22.19
    path: ~/.nvm/versions/node/v21.7.3/bin/yarn
  npm:
    version: 10.5.0
    path: ~/.nvm/versions/node/v21.7.3/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.2
      - iOS 17.2
      - macOS 14.2
      - tvOS 17.2
      - visionOS 1.0
      - watchOS 10.2
  Android SDK:
    API Levels:
      - "31"
      - "33"
      - "34"
    Build Tools:
      - 23.0.3
      - 30.0.3
      - 33.0.1
      - 34.0.0
      - 35.0.0
    System Images:
      - android-31 | ARM 64 v8a
      - android-34 | ARM 64 v8a
      - android-34 | Google APIs ARM 64 v8a
    Android NDK: Not Found
IDEs:
  Android Studio: Not Found
  Xcode:
    version: 15.2/15C500b
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.8
    path: /Users/ar.zarinia/.sdkman/candidates/java/current/bin/javac
  Ruby:
    version: 3.3.0
    path: /opt/homebrew/opt/ruby/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.74.0
    wanted: 0.74.0
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: Not found
  newArchEnabled: false
...

Stacktrace or Logs
> Task :gradle-plugin:checkKotlinGradlePluginConfigurationErrors
> Task :gradle-plugin:pluginDescriptors
> Task :gradle-plugin:processResources
> Task :gradle-plugin:compileKotlin
> Task :gradle-plugin:compileJava NO-SOURCE
> Task :gradle-plugin:classes
> Task :gradle-plugin:jar
> Task :app:checkKotlinGradlePluginConfigurationErrors
> Task :app:generateCodegenSchemaFromJavaScript SKIPPED
> Task :app:generateCodegenArtifactsFromSchema SKIPPED
> Task :app:generatePackageList
> Task :app:preBuild
> Task :app:preDebugBuild
> Task :app:generateDebugBuildConfig
> Task :app:checkDebugAarMetadata

Reproducer

Screenshots and Videos
No response

Closing as you provided no information on which failure you had.
I believe this is a duplicate of https://github.com/facebook/react-native/issues/44177


Android Messenger Google Fi Support

After upgrading my account to use Google Fi v2 Messages, Franz has stopped allowing me to log in. I know this is a beta, but just wanted to provide some info. I have attempted to create a custom recipe with a different URL, but I get the same issue
Service
Android Messages/ google fi
Additional Information
Steps to reproduce:
Add andoid messages
Instead of signing in with QR code, click get started
Sign into you google account
Expected:
Get redirected to https://messages.google.com/web/u/2/conversations
Actual
You get redirected to the login UI again.
Console errors

Uncaught (in promise) Error: Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project. (Attempt: 1)
    at Object._.zz (m=b:1794)
    at m=b:2762
    at Array.<anonymous> (m=b:1932)
    at PA (m=b:1927)
    at _.Ms.<anonymous> (m=b:1929)
    at _.Ms._.aa.uE (m=b:983)
    at _.Ms._.aa.dispatchEvent (m=b:981)
    at zta (m=b:1010)
    at Ata (m=b:1012)
    at _.Ms.Pc (m=b:1011)

Looking at the console

See #512 for a working recipe for this.


Bug in static code analysis / Community Store

I don't know whether i'm doing something wrong or this is a bug actually.
Given the scenario:
File: custom/plugins//src/Resources/administration/src//index.js
The file has the following content:
const { Component } = Shopware; Component.override('somecomponent', { ... });
When trying to upload the Plug-In to the community store, I get the following error message regarding this file:
"Shopware" does not exist. Change its name or declare it so that its usage doesn't result in a "ReferenceError".
Well, according to the documentation:
"...The admin core framework of shopware from src/core/ should always be accessed via the global available Shopware object and not via static imports. ..."
For me that means, that the code is correct.
When I change:
const { Component } = Shopware;
to
"import { Component } from 'src/core/shopware';"
the code analysis after uploading the Plug-In works just fine.
But as the documentation stated, import the Compontent from src/core/shopware is not the way to go.
Looks like the static code analysis tool is not able to handle global objects? there is no way for me to publish the plugin other than using a "wrong method" (import from src/core/shopware).
I hope this is understandable, if not, feel free to reply and ask questions.

Hey,
I have disabled the rule. Should be away with a new scan. Next time please write an email to<EMAIL_ADDRESS>cause it not related to the product :blush:


Local timezone error while running 1_operations_problems.ipynb in Binder

I tried running the SIIP Example notebooks in the binder. However, I encounter an error when PowerModels tries to activate Memento. Specifically the error is as follows
ERROR: LoadError: InitError: Failed to find local time zone
Stacktrace:
 [1] error(::String) at ./error.jl:33
 [2] localzone() at /srv/julia/pkg/packages/TimeZones/cAGJs/src/local.jl:154
 [3] DefaultFormatter at /srv/julia/pkg/packages/Memento/oMnS1/src/formatters.jl:35 [inlined]
 [4] config!(::Memento.Logger, ::String; fmt::String, levels::Dict{AbstractString,Int64}, colorized::Bool, recursive::Bool, substitute::Bool, propagate::Bool) at /srv/julia/pkg/packages/Memento/oMnS1/src/config.jl:39
 [5] config! at /srv/julia/pkg/packages/Memento/oMnS1/src/config.jl:36 [inlined]
 [6] #config!#72 at /srv/julia/pkg/packages/Memento/oMnS1/src/config.jl:28 [inlined]
 [7] config! at /srv/julia/pkg/packages/Memento/oMnS1/src/config.jl:28 [inlined]
 [8] #config!#71 at /srv/julia/pkg/packages/Memento/oMnS1/src/config.jl:25 [inlined]
 [9] config! at /srv/julia/pkg/packages/Memento/oMnS1/src/config.jl:25 [inlined]
 [10] __init__() at /srv/julia/pkg/packages/Memento/oMnS1/src/Memento.jl:64
 [11] _include_from_serialized(::String, ::Array{Any,1}) at ./loading.jl:697
 [12] _require_search_from_serialized(::Base.PkgId, ::String) at ./loading.jl:781
 [13] _require(::Base.PkgId) at ./loading.jl:1006
 [14] require(::Base.PkgId) at ./loading.jl:927
 [15] require(::Module, ::Symbol) at ./loading.jl:922
 [16] include(::Module, ::String) at ./Base.jl:377
 [17] top-level scope at none:2
 [18] eval at ./boot.jl:331 [inlined]
 [19] eval(::Expr) at ./client.jl:449
 [20] top-level scope at ./none:3
during initialization of module Memento
in expression starting at /srv/julia/pkg/packages/PowerModels/72tBz/src/PowerModels.jl:6

I don't get this error when I try to run the same notebook locally from the terminal. I understand that PowerModels is not a part of SIIP, so consequently, I apologize if this is not the correct place for the issue.

@k1nshuk thanks for letting me know. This is the perfect forum for this comment/issue. I've addressed by setting up binder to install the tzdata info. You can give it another try. It seems to be working for me.

68fa9cda4336b75fd6b8606cea6f4c15486359ef closes


About development workflows

Hi - this module looks great for bootstrapping a project from scratch, but how well does it scale with the project itself? For instance, how can I add instance / class methods without touching at the generated files?
It would be great if it could generate base classes and let higher level classes to be edited. For instance User (can be edited) -› BaseUser (generated)

It can definitely be used in very large projects. However, I will say that I created this project for my personal use and as I've needed to I made changes to the generators, so it's not as extensible as it would be if my true original intent was to make it totally reusable. I'm happy to make changes though if people find it useful.
I don't think supporting user-provided base classes is an option. For the *Instance classes, they are instantiated by Sequelize and have a Sequelize defined base classes. For *Pojo classes, they are specifically made to separate data and functionality so they can be safely sent over the wire (to/from json).
Sequelize does support injecting custom methods and properties into the *Instance classes (both the static models and the instances) and I do that for some helper methods. I would not be too difficult to support some kind of source file(s) that provided a template for methods to inject and then include those in the generated code. To do this I would specify a file format and upon generation look for, parse, and include methods from this file.
Another option is I could allow for an optional extensions object to provided to the initialize() method and then mix any class and instance methods/properties from this object into each of the models/instances. That would probably be easier for me and the user.
Comments? What specific type of functionality are you looking to add?
Also note that in my personal use, I have a lot of utility methods that I use to wrap the Sequelize methods. I generally prefer to do this rather then add them directly to the Sequelize models/instances to keep things separate and also because I do want to keep some separation between my custom code and sequelize-auto-ts (since I now know that some other people use it--thank you!).
When I get to writing up real documentation for sequelize-auto-ts (sorry, personal project, will get to it some time), I'll also include the utility methods I wrote up as extras.

Thank you for your reply.
Yeah I understand that POJOs need to stay as pure as possible - however in my personal experience, I like to enrich a lot both Instance (invoice.computePrice() or user.getFullname()) and Static classes (Invoice.findUnpaidForUser(user: UserInstance)).
If I understand you correctly, if I don't want to edit the generated files, I would need here to have a UserHelper and UsersHelper or UserStaticHelper).
Using as you say an "extension" file could also do the trick, but I find that much less OO...

I wasn't saying to create *Helper* classes. I'm saying that's an option, but usually better for more generic things, not specific to one instance type. When I have time I'll look into a way to allow custom extensions.


Row count by default in the Dataset view

I have a lot of requests for a simple count of rows in a table after import.
To solve for this:

I usually just reverse sort by cartodb_id as below, but that's a hack.
I can write a COUNT() query in SQL, but that's unnecessary work on the part of the user.

We should just display a row count at the top of the table view by default, easy, clean, like in the old old 1.0.0 version. #oldschoolRules

cc @chriswhong because we chatted about this. Kind of related to this backlog issue 	jorgeas80/cartodb#1045
Please and thank you :dancer:

+1 this was often asked for at Socrata but nobody listened... it is a
standard feedback to know how many rows were returned when querying...
I would say put it in the sql tab in the same place the error messages go
as a success message
On Apr 21, 2015 12:44 PM, "Aurelia Moser"<EMAIL_ADDRESS>wrote:

I have a lot of requests for a simple count of rows in a table after
import.
To solve for this:

I usually just reverse sort by cartodb_id as below, but that's a
hack.
I can write a COUNT() query in SQL, but that's unnecessary work on
the part of the user. [image: soylent]
https://cloud.githubusercontent.com/assets/1559703/7257471/f732ec24-e823-11e4-9090-12b97f0f64aa.jpeg
We should just display a row count at the top of the table view by default,
easy, clean, like in the old old 1.0.0 version. #oldschoolRules

cc @chriswhong https://github.com/chriswhong because we chatted about
this
Please and thank you [image: :dancer:]
—
Reply to this email directly or view it on GitHub
https://github.com/CartoDB/cartodb/issues/3312.

+1 on this. I'm working on some concepts for the upcoming editor. Imagine you can open something like this with a click

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.


feat(client-debugger): Prototype Visualizing Summary Tree for Client Debugger

Description
https://dev.azure.com/fluidframework/internal/_workitems/edit/3577/
This PR works closely with https://github.com/microsoft/FluidFramework/pull/14770 which generates types for visual summary tree for the Fluid DevTools.

/azp run Build - client packages

In the visual example, there are a lot of instances of the text "undefined". We should probably denote what those values are somewhere and/or omit them when undefined.

/azp run Build - client packages

/azp run Build - client packages


move google-api-services-x and datastore-v1-proto-client to google-cloud-bom

Last time we restructured google-cloud-java/pom we google-cloud-bom/pom, we moved protobuf and grpc dependencies to bom. According to discussion with @vam-google, google-api-services-x and datastore-v1-proto-client are equivalent to these libraries in the sense of dependencies so moving them to bom as well.

PTAL

Hmm this seems slightly different... the api-* packages are generated with a completely different system and are released independently from our project.


filesize(): Filename contains null byte b2-backblaze laravel 10

I am trying to upload file on backblaze b2 using this script,in laravel 10
$extension = $file->getClientOriginalExtension();
        $name = uniqid() . '.' . $extension;

        $header = [

            'Content-Type' => 'application/pdf',
            'Content-Disposition' => 'inline; filename="' . $file . '"'
        ];
        Storage::disk('b2')->put( $name, file_get_contents($file));

but its throwing the error "filesize(): Filename contains null byte",

is this fix?


Add support for wildcards in day and month inputs

The latest version of the design system, introduces support for date inputs that allow an 'X' to be used in place of an exact date.
This change implements that functionality but does so in a more-restrictive way; users won't have free reign over the pattern but
can optionally have 'X' added to it by supplying wildcards: true as an argument.
Should this be more flexible? Is it even necessary? These special 'dates' will need to be intercepted before Rails tries to parse them anyway, perhaps this should be left as an exercise for the developer 🤔

I personally never came across those X dates to be honest, but don't think are very user friendly.
We've implemented some alternatives to this problem where the user might not know the exact date.
Here are some examples.
We have a service where a user can enter an approximate date if they want or if they don't remember the exact date.
We just indicate so in a hint text as well as to reinforce this, we have a check box they can select "This is not the exact date" (we really do nothing different in terms of calculations if they select this check box, but serves us for analytics purposes, to know how many of the dates users enter are exact vs. approximate).

In this service, an X date will not work as we still need to do calculations on dates to estimate the rehabilitation period and date the caution or conviction become spent.
Of course, being an approximate date, will give approximate results, but the user is aware of this and we tell them in the results page as well (the check box is handy for that).
And in another service we use a different approach, in particular for DOB where if they do not know the DOB of a person they can select a check box that reveals a little input to enter either a year, or approx. age:

These are just some examples of a different approach to the problem.


json_annotation dependency upgrade?

I know the full upgrade to null safety may be difficult due to build_runner, but is it possible to partially upgrade by upgrading for json_annotation ^4.0.1? It's helpful with the freezed lib upgrade.
Thank you very much for the awesome package.

json_annotation 4.x.x is written using nullsafety, so it won't be compatible with the current version of flutter_flavorizr.


Build docker image failed  when i Use latest version Docker file

 => [go-builder  2/13] RUN set -eux; apk add --no-cache ca-certificates build-base;                                                                                31.0s
 => [go-builder  3/13] RUN apk add git                                                                                5.4s
 => [go-builder  4/13] WORKDIR /code                                                                                0.0s
 => [go-builder  5/13] COPY . /code/                                                                                0.1s
 => [go-builder  6/13] ADD https://github.com/CosmWasm/wasmvm/releases/download/v1.0.0/libwasmvm_muslc.aarch64.a /lib/libwasmvm_muslc.aarch64.a                                                                                0.2s
 => [go-builder  7/13] ADD https://github.com/CosmWasm/wasmvm/releases/download/v1.0.0/libwasmvm_muslc.x86_64.a /lib/libwasmvm_muslc.x86_64.a                                                                                0.2s
 => [go-builder  8/13] RUN sha256sum /lib/libwasmvm_muslc.aarch64.a | grep 7d2239e9f25e96d0d4daba982ce92367aacf0cbd95d2facb8442268f2b1cc1fc                                                                                0.6s
 => [go-builder  9/13] RUN sha256sum /lib/libwasmvm_muslc.x86_64.a | grep f6282df732a13dec836cda1f399dd874b1e3163504dbd9607c6af915b2740479                                                                                0.5s
 => [go-builder 10/13] RUN cp /lib/libwasmvm_muslc.$(uname -m).a /lib/libwasmvm_muslc.a                                                                                0.3s
 => ERROR [go-builder 11/13] RUN LEDGER_ENABLED=false BUILD_TAGS=muslc LINK_STATICALLY=true make build                                                                                0.2s
------
 > [go-builder 11/13] RUN LEDGER_ENABLED=false BUILD_TAGS=muslc LINK_STATICALLY=true make build:
#21 0.169 make: *** No rule to make target 'build'.  Stop.
------
executor failed running [/bin/sh -c LEDGER_ENABLED=false BUILD_TAGS=muslc LINK_STATICALLY=true make build]: exit code: 2

docker build . -t test/juno:20220810

This problem has been the solution.Thanks


Mamba

added mamba implementation
adapted implementation to modalities interface
added tests for mamba classes

Additional type hints / annotations would be helpful.

We added the missing type hints


AsyncTests & Engine Refactor

-Refactor to moved duplicated code in AsyncXXXLike traits to AsyncTests.scala.
-Removed simpleClassName parameter of Engine.
-Refactored to make engine private[scalatest] instance of TestRegistration and fixture.TestRegistration.

@cla-bot[bot] check


New version: PostgreSQL.PostgreSQL.14 version 14.12-1

Created by 🥟 Dumplings.
Microsoft Reviewers: Open in CodeFlow

Manual Validation ended with:

10:52:52 AM:
2024-05-28 10:52:48.619 [CORE] DeliveryOptimization error: 0x80190193, extended error: 0x00000000 10:52:52 AM:
2024-05-28 10:52:48.876 [FAIL] C:__w\1\s\external\pkg\src\AppInstallerCommonCore\DODownloader.cpp(289)\WindowsPackageManager.dll!00007FFD8725F180: (caller: 00007FFD8725FACC) Exception(1) tid(d8) 80190193 Forbidden (403). 10:52:52 AM:
2024-05-28 10:52:50.209 [CORE] Download request failed. Returned status: 403 10:52:52 AM:
2024-05-28 10:52:50.209 [FAIL] C:__w\1\s\external\pkg\src\AppInstallerCommonCore\Downloader.cpp(148)\WindowsPackageManager.dll!00007FFD872591E2: (caller: 00007FFD8725AA19) Exception(2) tid(d8) 80190193 Forbidden (403). 10:52:52 AM:
2024-05-28 10:52:50.211 [CLI ] Failed to download, waiting a bit and retry. Url: https://get.enterprisedb.com/postgresql/postgresql-14.12-1-windows-x64.exe 10:52:52 AM:
2024-05-28 10:52:51.799 [CORE] DeliveryOptimization error: 0x80190193, extended error: 0x00000000 10:52:52 AM:
2024-05-28 10:52:51.799 [FAIL] C:__w\1\s\external\pkg\src\AppInstallerCommonCore\DODownloader.cpp(289)\WindowsPackageManager.dll!00007FFD8725F180: (caller: 00007FFD8725FACC) Exception(3) tid(d8) 80190193 Forbidden (403). 10:52:52 AM:
2024-05-28 10:52:52.069 [CORE] Download request failed. Returned status: 403 10:52:52 AM:
2024-05-28 10:52:52.069 [FAIL] C:__w\1\s\external\pkg\src\AppInstallerCommonCore\Downloader.cpp(148)\WindowsPackageManager.dll!00007FFD872591E2: (caller: 00007FFD8725AA19) Exception(4) tid(d8) 80190193 Forbidden (403).

(Automated response - build 881.)

@wingetbot run

Manual Validation ended with:

3:08:11 PM:
2024-05-28 15:08:08.673 [CORE] DeliveryOptimization error: 0x80190193, extended error: 0x00000000 3:08:11 PM:
2024-05-28 15:08:08.674 [FAIL] C:__w\1\s\external\pkg\src\AppInstallerCommonCore\DODownloader.cpp(289)\WindowsPackageManager.dll!00007FFD8713F180: (caller: 00007FFD8713FACC) Exception(1) tid(29a8) 80190193 Forbidden (403). 3:08:11 PM:
2024-05-28 15:08:09.599 [CORE] Download request failed. Returned status: 403 3:08:11 PM:
2024-05-28 15:08:09.599 [FAIL] C:__w\1\s\external\pkg\src\AppInstallerCommonCore\Downloader.cpp(148)\WindowsPackageManager.dll!00007FFD871391E2: (caller: 00007FFD8713AA19) Exception(2) tid(29a8) 80190193 Forbidden (403). 3:08:11 PM:
2024-05-28 15:08:09.602 [CLI ] Failed to download, waiting a bit and retry. Url: https://get.enterprisedb.com/postgresql/postgresql-14.12-1-windows-x64.exe 3:08:11 PM:
2024-05-28 15:08:10.759 [CORE] DeliveryOptimization error: 0x80190193, extended error: 0x00000000 3:08:11 PM:
2024-05-28 15:08:10.759 [FAIL] C:__w\1\s\external\pkg\src\AppInstallerCommonCore\DODownloader.cpp(289)\WindowsPackageManager.dll!00007FFD8713F180: (caller: 00007FFD8713FACC) Exception(3) tid(29a8) 80190193 Forbidden (403). 3:08:11 PM:
2024-05-28 15:08:10.955 [CORE] Download request failed. Returned status: 403 3:08:11 PM:
2024-05-28 15:08:10.956 [FAIL] C:__w\1\s\external\pkg\src\AppInstallerCommonCore\Downloader.cpp(148)\WindowsPackageManager.dll!00007FFD871391E2: (caller: 00007FFD8713AA19) Exception(4) tid(29a8) 80190193 Forbidden (403).

(Automated response - build 881.)

Manual Validation ended with:

... Forbidden (403) ... Returned status: 403 ... Forbidden (403) ... Forbidden (403) ... Returned status: 403 ... Forbidden (403).

(Automated response - build 881.)

Just got the same output. These work in the browser, so it's likely a user-agent block. And what's strange is the first ~30 MB are downloaded before the 403 error occurs. Usually I'd expect the 403 to happen before any downloading happens.

Manual Validation ended with:

... Forbidden (403) ... Returned status: 403 ... Forbidden (403) ... Forbidden (403) ... Returned status: 403 ... Forbidden (403).

(Automated response - build 881.)

Just got the same output. These work in the browser, so it's likely a user-agent block. And what's strange is the first ~30 MB are downloaded before the 403 error occurs. Usually I'd expect the 403 to happen before any downloading happens.

The server seems to have a strict rate limit. At least for me the installer can be downloaded directly in PowerShell without specifying any user agent.


[CT-2997] Ability to test incremental models

Description
We should allow folks to add unit tests to incremental models
Acceptance criteria

Ability to test incremental models in both full refresh and incremental mode
Ability to specify the current status of an incremental model to test the incremental behavior
Ability to test the incremental behavior of models using incremental strategy that requires partitioning (e.g. insert overwrite in BigQuery)

A "current_actual" could define the current state of the model we're incrementing on, testing whether the incrementing works as expected.

@gshank please pull Ability to test the incremental behavior of models using incremental strategy that requires partitioning (e.g. insert overwrite in BigQuery) out into a separate ticket

2x2 = 4 acceptance tests for us to write as part of implementation:

{{ is_incremental() }} : True + False
{{ this }} fixture: provided or not

Here's how i'm imagining the spec for this:
unit-tests:
 - model: my_model
   tests:
    - name: test_name
      given:
      - input: this
         rows: ...


Add preemptible option for gcp deployment

The terraform resource for gke https://www.terraform.io/docs/providers/google/r/container_cluster.html has support for preemptible nodes

Fixed by

https://github.com/Quansight/qhub-terraform-modules/pull/13
https://github.com/Quansight/qhub-terraform-modules/pull/17


[WIP] SharePoint.UI.Responsive.v2

Note : "edit link" redirect user to navigation manager now  (fix SharePoint/PnP-Tools/issues/82)

Thx @Laul0 - We'll do quick double checking that everything is fine and get this processed soon. Thanks for your contributions to this. Super valuable.


[Key Vault] Resolve mindependency check failure

Due to an updated cryptography requirement for azure-identity KV packages are failing mindependency checks. azure-identity is only a dev requirement, so this is an effort to resolve the issue by bumping azure-keyvault-keys's cryptography dev requirement only (still requiring only 2.1.4 to install the package).

@mccoyp I have another PR  #20391 that attempts addressing this as well! @xiafu-msft raised an issue and I just haven't responded yet until my prospective fix checks out.

Oh nice, thank you! I figured this might not work (it evidently didn't), but your solution makes sense. I'll close this and give my thumbs-up to that PR!


support for acl's

For full linux backups, support of acl (such as set with the setfacl command) would be convenient

Duplicate of #25.

Thanks for raising this issue, it is indeed a duplicate so I'm closing this issue. You can subscribe to #25 if you'd like to be notified of the process.


feature shenyu-plugin:add shenyu-plugin-logging-huawei-lts

Fixes #4829

Make sure that:

[x] You have read the contribution guidelines.
[x] You submit test cases (unit or integration tests) that back your changes.
[x] Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #4812 (271f3b5) into master (92966fd) will decrease coverage by 0.18%.
The diff coverage is 76.84%.

@@             Coverage Diff              @@
##             master    #4812      +/-   ##
============================================
- Coverage     65.29%   65.12%   -0.18%
- Complexity     8184     8194      +10
============================================
  Files          1138     1144       +6
  Lines         33476    33654     +178
  Branches       2975     2994      +19
============================================
+ Hits          21858    21917      +59
- Misses         9893     9989      +96
- Partials       1725     1748      +23

Impacted Files
Coverage Δ

...ugin/huawei/lts/config/HuaweiLogCollectConfig.java
72.52% <72.52%> (ø)

...n/huawei/lts/client/HuaweiLtsLogCollectClient.java
76.92% <76.92%> (ø)

...in/huawei/lts/collector/HuaweiLtsLogCollector.java
80.00% <80.00%> (ø)

...ava/org/apache/shenyu/common/enums/PluginEnum.java
100.00% <100.00%> (ø)

...enyu/plugin/huawei/lts/LoggingHuaweiLtsPlugin.java
100.00% <100.00%> (ø)

...lts/handler/LoggingHuaweiLtsPluginDataHandler.java
100.00% <100.00%> (ø)

...uawei/lts/LoggingHuaweiLtsPluginConfiguration.java
100.00% <100.00%> (ø)

... and 25 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

pls add data.  -> ./db/upgrade/2.5.1-upgrade-2.6.0-*.sql

pls add data. -> ./db/upgrade/2.5.1-upgrade-2.6.0-*.sql @xcsnx
ok


Fix node dashboard on OKE

Pull Request
Required Fields
:mag_right: What kind of change is it?

fix

:dart: What has been changed and why do we need it?

Change instance variable selector

Optional Fields
:heavy_check_mark: Which issue(s) this PR fixes?

#37

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Correct link for getting started with Flutter dev

closes https://github.com/atsign-foundation/docs.atsign.com/issues/172
- How I did it

Updated the link to the correct one

- How to verify it

Open the link and check the page it leads to

- Description for the changelog
Changed the link to the correct one.

Hi @igniti0n , this issue was resolved in a separate pr. We appreciate the contribution though! If you would like to help with anything else, feel free to scroll through our issue list.


Data lake gen 2 SDK

I am currently using the Data Lake Gen2 SDK package which is currently under preview. I wrote a console application to see how to use the package and things work as expected for me. But when I write the same code and upload it to run on Azure Data Factory I get this error
"System.IO.FileLoadException: Could not load file or assembly 'System.Diagnostics.DiagnosticSource, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'System.Diagnostics.DiagnosticSource, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'
at Azure.Core.Pipeline.ClientDiagnostics..ctor(String clientNamespace, Boolean isActivityEnabled)
at Azure.Storage.Files.DataLake.DataLakeFileSystemClient..ctor(Uri fileSystemUri, HttpPipelinePolicy authentication, DataLakeClientOptions options)
at ..GetDataLakeDirectoryClient() ".
I am not really sure why this issue is coming up when I try to execute my Custom Activity in Azure Data Factory.

@hruday94 Since the issue is not a feedback on the doc in reference, I would recommend you to create a thread on the forums - MSDN or stack overflow.
Once you post your issue on forums, it will have visibility across the community which is a better suited audience for such types of issues.
Please create a Forum thread and post it's link here and tag me so that we can track that thread. We would love to work with you on the issue on the forums.
I will now proceed to close this issue. Feel free to comment if you have any other queries.


Final data prepper qa testing

Need to test full trip functionality with data prepper integration

Related to #98


add additional fitbit endpoints for SPO2 and skin temp

new webapis were added last year:

https://dev.fitbit.com/build/reference/web-api/spo2/
https://dev.fitbit.com/build/reference/web-api/temperature/

added SPO2 (daily summary) and skintemp (daily).  the code is available in the branch for now, i'll merge it in when i can add the spo2 intraday.
The bigquery schema for the SPO2 (daily summary) looks like this:

and the skinTemp looks like this:

k

SPO2 intraday requires specific approval for the application.  see https://dev.fitbit.com/build/reference/web-api/intraday/


Provide a ServiceRegistration#tryUnregister() method that returns a boolean instead of throwing an exception

Currently the most annoying part when working with ServiceRegistration is its behavior to throw an IllegalStateException when it has already unregistered and I always wondered what code should do with it, for sure my intend is to unregister it, so if it is already unregistered, fine than I'm a bit late at the party but what should I do then?
So I almost always see some code like this where ServiceRegistration#unregister is used:
try {
   reference.unregister();
} catch(IllegalArgumentException e) {
 //already unregistered...
}

Using Exceptions to report state is bad and for this I'd like to propose a new (maybe default implemented) method like this:
/**
 * Try to unregister the service and return the result of this to the caller.
 *
 * @return true if the {@link ServiceRegistration} was unregistered as a result of this call, false otherwise.
 */
default boolean tryUnregister() {
	try {
		unregister();
		return true;
	} catch(IllegalStateException ise) {
		return false;
	}
}

so just in case someone can/want/should do anything useful one can simply do:
if (!reference.tryUnregister()) {
  logger.warn("OH NO !!!);
}

Call: We should survey the use of throwing IllegalStateException in the framework API and make recommendations to elide that for the "closing" methods. (removeListener, ungetService, unregister).

Note that removing IllegalStateException from org.osgi.framework.ServiceObjects.ungetService(S) simply replaces the exception with an IllegalArgumentException because on the stopped context all service objects would already be cleaned up so there is no way for the framework to tell if the passed in object was provided by the ServiceObjects or not.  Should the implementation avoid the IllegalArgumentException if the context is no longer valid also?

Note that removing IllegalStateException from org.osgi.framework.ServiceObjects.ungetService(S) simply replaces the exception with an IllegalArgumentException because on the stopped context all service objects would already be cleaned up so there is no way for the framework to tell if the passed in object was provided by the ServiceObjects or not. Should the implementation avoid the IllegalArgumentException if the context is no longer valid also?

I would say yes. The whole purpose of this is to allow to clean up at any time, if the serivce registration is already cleaned up anyways there is no point in throwing any exception (except e.g. if passing null is forbidden or similar) as the actual goal is already archived.

I agree, one possible implementation is to simply return quick, as soon as it is detected that the context is no longer valid with no exception.  My original implementation let the method continue but then it detected that there was no object found to remove from the internal references.  There should be no need even to do that check since invalid contexts will already have all their used services released.


Bazel build failed in foreign_cc

Bug Template
Title: Bazel build failed in foreign_cc
Description:
With latest tree, and with bazel 0.21.0,   when "bazel build //souce/...", I got
bazel build //source/exe:envoy-static
WARNING: The following rc files are no longer being read, please transfer their contents or import their path into one of the standard rc files:
/home/qiwzhang/github/envoyproxy/envoy/tools/bazel.rc
ERROR: /home/qiwzhang/.cache/bazel/_bazel_qiwzhang/85114b85e3290f3d9d9a93c62b41d7d0/external/envoy/bazel/foreign_cc/BUILD:86:1: in cmake_external rule @envoy//bazel/foreign_cc:yaml:
Traceback (most recent call last):
File "/home/qiwzhang/.cache/bazel/_bazel_qiwzhang/85114b85e3290f3d9d9a93c62b41d7d0/external/envoy/bazel/foreign_cc/BUILD", line 86
cmake_external(name = 'yaml')
File "/home/qiwzhang/.cache/bazel/_bazel_qiwzhang/85114b85e3290f3d9d9a93c62b41d7d0/external/rules_foreign_cc/tools/build_defs/cmake.bzl", line 47, in _cmake_external
cc_external_rule_impl(ctx, attrs)
File "/home/qiwzhang/.cache/bazel/_bazel_qiwzhang/85114b85e3290f3d9d9a93c62b41d7d0/external/foreign_cc_impl/framework.bzl", line 209, in cc_external_rule_impl
_define_out_cc_info(ctx, attrs, inputs, outputs)
File "/home/qiwzhang/.cache/bazel/_bazel_qiwzhang/85114b85e3290f3d9d9a93c62b41d7d0/external/foreign_cc_impl/framework.bzl", line 627, in _define_out_cc_info
cc_common.create_compilation_context(ctx = ctx, headers = depset([outpu...]), <2 more arguments>)
unexpected keyword 'ctx', for call to method create_compilation_context(headers = unbound, system_includes = unbound, includes = unbound, quote_includes = unbound, defines = unbound) of 'cc_common'
ERROR: Analysis of target '//source/exe:envoy-static' failed; build aborted: Analysis of target '@envoy//bazel/foreign_cc:yaml' failed; build aborted
INFO: Elapsed time: 1.483s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (213 packages loaded, 4783 targets configured)
Fetching @com_github_gperftools_gperftools; Patching repository
Fetching @com_github_nghttp2_nghttp2; fetching
Fetching @com_github_c_ares_c_ares; fetching
Fetching @com_github_circonus_labs_libcircllhist; fetching
Fetching @boringssl; fetching
Fetching @com_github_madler_zlib; fetching
BTW,  I also tried with bazel 0.23.0. Same issue
Any clues?

Did you try bazel clean --expunge? 0.21 doesn't work with latest, but 0.22 or 0.23 should work and they are tested in CI.

Thanks.   It works now after "bazel clean --expunge"


LastUserActionTime property has been dropped

[Enter feedback here]
the older Get-MailboxStatistics cmdlet used to support the LastUserActionTime property. the only way to now surface that I am aware of is to use Export-MailboxDiagnosticsLog that is badly documented and I believe it should have been kept as a selectable property in this new EXO cmdlet.
I used to be able to use a simple :
Get-MailboxStatistics -Identity ‘USER-UPN’  | Select LastUserActionTime
but now with the new V2 Get-EXOMailboxstatistics cmdlet this no longer works
Get-EXOMailboxStatistics -Identity ‘USER-UPN’  | Select LastUserActionTime

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

ID: 68aa3776-5347-6299-e566-33f018a2e96c
Version Independent ID: 9feff981-1e32-11f6-2417-062e09ddaa3a
Content: Get-EXOMailboxStatistics (exchange)
Content Source: exchange/exchange-ps/exchange/Get-EXOMailboxStatistics.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

And the whole consistency across ps cmdlets of related properties LastUserInteractionTime or LastUserActionTime reporting really needs improving. As it is quite inconsistent. And the meaning of the various Last.... terms could really also do with documentation that explains and actually says what they mean and what they do not indicate as well. So that articles like these 3 do not all come to different assumptions and suggestions of 'best' practice.
https://petri.com/exchange-online-exposes-new-mailbox-activity-data
https://www.michev.info/Blog/Post/2408/new-properties-added-to-get-mailboxstatistics-output
https://gallery.technet.microsoft.com/office/Export-Office-365-Users-05819ea5

@officedocsbot assign @yogkumgit

Hi @TheBigBear, thank you for your feedback.
The Exchange Online PowerShell V2 module is currently in Preview. If you have any feedback, concerns, or are facing any issues with the EXO V2 module, contact us at exocmdletpreview[at]service[dot]microsoft[dot]com (email address intentionally obscured to help prevent spam).
When you report an issue, be sure to include the log files in your email message.
To generate the log files, replace  with the output folder you want, and run the following command:
Connect-ExchangeOnline -EnableErrorReporting -LogDirectoryPath  -LogLevel All

@dariomws  Thank you very much for the contribution and sharing this explanation. @TheBigBear
Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

Just to close the loop on this since it is linked in web searches, we can specify -Properties LastUserActionTime to get the LastUserActionTime. So in your example, you can use this to retrieve this property:
Get-EXOMailboxStatistics -Identity 'USER-UPN' -Properties LastUserActionTime | Select LastUserActionTime


Unable to launch browser in Windows

I'm using Granted version 0.1.11 on Windows 10. When I assume a role (not logged into AWS), my browser opens and requests for permissions just fine. However, every time afterwards I have been unable to get a browser window to pop when I assume different roles. The logs indicate that I can switch roles ([Build-Account](us-west-2) session credentials will expire...), but nothing happens. I've tried launching through both Chrome and Edge browsers, and have verified that the paths are set correctly in my settings (granted settings).

Hi @eigBabcock
To confirm you are running assume -c <profile-name>
Do you get a URL in the terminal to open in the browser or does nothing happen at all?


esm.sh import with pinned version results in an error

https://esm.sh/#docs Ctrl+F "Pinning Build Version"
It's preferred to pin the esm.sh build version (in addition to the npm package version) so deno.lock doesn't get out of sync. With a pinned esm.sh URL such as this:
export { type Filter, matchFilter, nip13 } from<EMAIL_ADDRESS>
we get the following error:
Task npm deno run -A scripts/npm.ts
[dnt] Transforming...
[dnt] Running npm install...
npm ERR! code EINVALIDPACKAGENAME
npm ERR! Invalid package name "v114/nostr-tools" of package<EMAIL_ADDRESS>name can only contain URL-friendly characters.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/alex/.npm/_logs/2023-04-17T01_00_58_188Z-debug-0.log
error: Uncaught (in promise) Error: npm install failed with exit code 1
        throw new Error(
              ^
    at runCommand (https://deno.land/x/dnt@0.34.0/lib/utils.ts:57:15)
    at async build (https://deno.land/x/dnt@0.34.0/mod.ts:210:5)
    at async file:///home/alex/Projects/strfry-policies/scripts/npm.ts:5:1

Removing the pin works perfectly, so this is a problem with the way esm.sh URLs are handled:
export { type Filter, matchFilter, nip13 } from<EMAIL_ADDRESS>// this works (notice no v114)

Using ?pin=114 at the end of the URL (instead of as a path in the URL) works as a workaround.

@hansSchall would you be able to open a new issue? It's easy for stuff to get lost in old closed issues and the fix here might be unrelated.


Port mariadb-operator

Port mariadb-operator, adding the following files:

config.json
manifests.min.yaml
mariadb-secret.yaml
mariadb-yaml (seed CR)
context.json

Update default k8s version to 1.29.2
Change the namespace config in acto/constant.py to default (need help)

@PAN-Ziyue Is this PR ready for review?

@PAN-Ziyue Is this PR ready for review?

Sorry for my late response.
This PR is ready for review, but I have several concerns to discuss with you.
Can only deploy mariadb-operator in default namespace
During manully deploying mariadb-operator, I found that mariadb-operator can only run in the default namespace.
Or it will warn an rbac error like:
User "system:serviceaccount:acto-namespace:mariadb-operator-cert-controller-cert-controller" cannot list resource "mutatingwebhookconfigurations" in API group "admissionregistration.k8s.io" at the cluster scope

To fix this problem, I tried to set "namespace": "default" option in config.json.
The option takes effect during deploying the CRs.
However the namespace fell back to acto-namespace when analyzing the seed custom resouce.
I am not sure whether it is an intended behavior.
I fix it with an adhoc solution to set CONST.ACTO_NAMESPACE="default".
Segfault when running the SSA tool
During porting, the SSA tool panics. That's the reason why I cannot run acto in white-box mode.
I tested 2 cases: mariadb-operator and the existing redis-ot-container-kit-operator.
Each of them crashed at different places.
However I cannot catch the root cause in a short time.
Maybe the SSA tool can be further examined.

I see, the operator deployment YAML files probably need some changes to support arbitrary namespace.
One of the dependencies of the SSA library is deprecated, so it is currently not usable.

I see, the operator deployment YAML files probably need some changes to support arbitrary namespace.

Could you suggest which manifest fields need reviewing or modification?

I assume that you generated the YAML files using HELM chart? When you generate the helm chart, you should be able to specify a flag for namespace (--create-namespace and -n). If you did not specify the flag, default namespace is used.

Thanks for your time and response.
Sorry I did not generate the YAML files using HELM chart. But I did export the YAML files from mariadb-operator's helm chart release directly.
I plan to review the issue using helm chart w/ flags as you suggested. But I may not be available these days. I apologize for my delayed response in advance.


To address the formatting errors in the blog, new author Image and change in the Linkedin URL.

Description
It will address the formatting error in the blog. Make sure the author image is in right resolution and proper Linkedin url is displayed in the website.
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

@pajuric @natebower @nateynateynate @krisfreedain -
Today, my published blog encountered several formatting glitches, including numbering discrepancies, misformatted code snippets, extraneous characters, and hyperlink errors. Additionally, the author's image failed to display correctly on the website, and the LinkedIn URL did not direct to my profile. I've rectified these issues and submitted a pull request.
Your prompt review and approval are greatly appreciated, as the blog is already public, it might cause inconvenience to the readers and they may raise concerns.

@krisfreedain , Thanks for merging the new commits however the new commits is not reflecting in the blog website. Does it take time?


Enable fetcher to filter for correct HAB target

This PR allows the firmware fetcher to (optionally) filter entries in the log to ensure that only those targeting a particular device are returned.

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

Comparison is base (872770b) 60.00% compared to head (7796d93) 60.83%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #22      +/-   ##
==========================================
+ Coverage   60.00%   60.83%   +0.83%
==========================================
  Files           2        2
  Lines         235      240       +5
==========================================
+ Hits          141      146       +5
  Misses         65       65
  Partials       29       29

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


Correct build errors

The latest version of the plugin does not build correctly using Flutter version higher than 3.3.0,
this pull proposes a fix for the problem
RaisedButton and ClipRRect Parsers removed and correct

RaisedButton has been deprecated for a long time, it doesn't make sense to have a parser for it and encourage the community to use it.
borderRadius returns the BorderRadiusGeometry widget that must resolve to BorderRadius before having access to the borders' radius properties

@dengyin2000 when this version will be available?


UI updates

I think these are ready to merge in.
Can test using panel serve satgpt-chatbot.ipynb
"Search for Sentinel images over Seattle, WA in May/ June 2023 and load datacube."
No spyndex plotting features yet.

Note app.py is now broken but these should be very minor changes to get working again. I think I just changed a couple things about the item/ date handling.


"Error requesting.." immediately after install (solved)

I just installed and despite no error during installation, the integration was erroring immediately.
It was throwing '429' errors
Error requesting <homeassistant.components.solaredge.coordinator.SolarEdgeDetailsDataService object at 0x7fc2d176ee70> data: 429, message='', url='https://monitoringapi.solaredge.com/site/{redacted}/details?api_key={redacted}'
During setup, I left the last optional field empty. I then noticed in the failing query string that it had defaulted to looking for data since 2017 which is correct based on my installation date.
I re-ran the integration configuration and added a more usable date into the optional field (I figured the last 5 years of data would be sufficient and just went with 01012020) and then the integration started to work.
Not sure whether the errors were due to timing out trying to grab so much data, or just spurious connectivity errors.

I think this has to do with the limited amount of data which can be received from the api. My starting date is just 4 years ago so I did not reach the limit.
I will look at it and add a minimum value for the installation date.


Docs.MS Release Updates for azure-template

Update docs metadata and targeting for release of azure-template

Docs Build status updates of commit 884d95d:
:clock10: Full build: the average full build time is 77 min(s) 31 sec(s), this is based on the last 107 build(s) for this repository.

Docs Build status updates of commit 884d95d:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-autogen/overview/ManagedGroups.yml
:warning:Warning
View (azure-node-latest)
Details

ci-configs/packages-preview.json
:white_check_mark:Succeeded

docs-ref-services/template-readme-pre.md
:white_check_mark:Succeeded
View (azure-node-latest) View (azure-node-preview) View (azure-node-legacy)

docs-ref-autogen/overview/ManagedGroups.yml

[Warning-DuplicateUids] Uid(azure.nodejs.sdk.landingpage.services.managedapplications) has already been defined in docs-ref-autogen/overview/ManagedApplications.yml.

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


Sorting causes segfault

Version: db1b212
Minimal setup to reproduce:
use core::cmp::Ordering;
use flecs_ecs::prelude::*;

#[derive(Component)]
struct Foo(u8);

fn foo_cmp(_: Entity, a: &&Foo, _: Entity, b: &&Foo) -> i32 {
    match a.0.cmp(&b.0) {
        Ordering::Less => -1,
        Ordering::Greater => 1,
        Ordering::Equal => 0,
    }
}

fn main() {
    let mut world = World::new();

    world.entity().set(Foo(0));
    world.entity().set(Foo(1));

    system!("foo_sort", world, &Foo)
        .kind::<flecs::pipeline::OnStore>()
        .order_by::<&Foo>(foo_cmp)
        .each(|_| {});

    world.progress();
}

tldr of discord conversation, it's because &T is passed in the order_by function instead of just T, which changes the function signature to &&T which causes the segfault. Need to patch this issue.


The ability that a talent affects

Is it possible to extract the ability that a talent affects? Such as whether a talent affects Q, W, E, or passive, etc.
Thanks for the parser. Used it today for the first time and it's very handy.

I'll look into.

It is done.  The AbilityType will be Q, W, E, Heroic, Z, Trait, Active, or Passive. Basically it should be the same as the Talents section in hero collection.
Be on the lookout for incorrect values, as this is quite hard to get.

Thanks a ton. Just in case, have you considered the case of talents that enhance multiple skills?

Not possible.  They show up as Passive, like for Malfurion's Level 16 `Nature's Balance'.


Add support for HTS to Ledger BOLOS App for Hedera

Use explicit_bzero over memset
Use _nothrow variants of crypto functions
Add support for token transfers and token associate transactions
Remove warnings from build

cc @SimiHunjan @cacampbell

Add support for token mint and burn

PR now requires an update to Hedera services to add support for expected_decimals to TokenMint and TokenBurn
See https://github.com/hashgraph/hedera-improvement-proposal/pull/387/files for more details


js kongress munich

 (@jskongress #jskongress) - <2020.04.15-16> - ,  - <2019.10.15> - <cfp link[https://sessionize.com/js-kongress-2020]> - <JavaScript, scaling, Massive Platforms, Data-Driven Architectures, Modern APIs>

thanks, I've included the change on the master


is this project still necessary ?

according to eslint https://github.com/eslint/eslint#what-about-ecmascript-6-support, they fully support es6/es2015 ... is babel-eslint still necessary ?

Yeah, it's still necessary if you want to lint babel with any newer transforms that babel supports - anything >es2015. If you are only using es6 then you don't need to use it but other people may be using other features that eslint by itself won't support yet - examples: decorators, async/await, etc.
Recent article by @nzakas explains it http://www.smashingmagazine.com/2015/09/eslint-the-next-generation-javascript-linter/#custom-parsers.

Yeah, my bad, forgot that babel also transpile es7/es2016 stuff.


Rest API - Trigger events for "/connections"

Integrate #540 with events in rest API.

This will be done as part of #551 .


Added detailed error messages to improve ease of use.

Rust compiler puts a lot of effort into great error messages and I really appreciate them. I'm only going to be a ndarray noob once, so I'm taking this oppotunity to make it easier for other noobs.
This is to close: https://github.com/bluss/ndarray/issues/449
Please let me know your thoughts? If you're happy I'll add in a few more tests to try and hit most of the error messages.

Better error messages are great, but this solution increases the size and overhead of the ShapeError struct dramatically, so it can't be merged.


perf(ngStyleDirective): use $watchCollection

This re-commits https://github.com/angular/angular.js/commit/4c8d8ad5083d9dd17c0b8480339d5f95943f1b71 which was reverted (with tests added).  This is possible now because of 189461f9bf6fda18ddbd16c42f2e959cf939c3da, although note that change is currently causing #15905 so maybe we should hold off on merging this one for now?
FYI @gdi2290

:+1: for waiting until #15905 is resolved.

Interestingly, there's no test for normal literal bindings:
  it('should support binding for object literals', inject(function($rootScope, $compile) {
    element = $compile('

')($rootScope);
    $rootScope.$digest();
    expect(parseInt(element.css('height') + 0, 10)).toEqual(0); // height could be '' or '0px'
    $rootScope.$apply('heightStr = "40px"');
    expect(element.css('height')).toBe('40px');

    $rootScope.$apply('heightStr = "100px"');
    expect(element.css('height')).toBe('100px');
  }));

@Narretz I've added a commit with that test. Also changed to 1.7 because this depends on 189461f9bf6fda18ddbd16c42f2e959cf939c3da which is going to be reverted in 1.6 (#15958).

I think this can go into 1.7 now @gkalpak?

Note: this will break cases where people are relying on a value being an object and automatically invoking .toString() such as {color: obj} where obj.toString() is stateful.  This can be fixed by changing the expression to {color: obj.toString()}. Should add a breaking change notice for this.

I've updated the commit message with a "BREAKING CHANGE" message and changed the "Closes #" to this PR. Look good?

Should there be a test for the case that is described in the BC notice?

A test verifying that styles don't get re-applied when an object sub-property changes? Could...

Just because we are setting an expectation for this behavior

I've added a test. The other option is verifying that ng-style="x" invokes $watchCollection(x)...?

LGTM

nice

A tiny change with potentially big gains :smiley:
(It also took some serious poking around the $parse service - kudos to @jbedard 💯)