Can't install on Linux Mint 20

The following packages have unmet dependencies:
 stonenet : Depends: libc6 (>= 2.34) but 2.31-0ubuntu9.14 is to be installed

So I upgraded to Mint 21 which is based on Ubuntu jammy and now it works. My system upgrade was due anyway, but it would of course be nice if it works on older Ubuntu versions.

Hmmm, yeah I had a similar error at some point, because it turned out I hadn't upgraded to the new debian version yet.
But I've configured a certain version of the rust compiler to be used in stonenet, and that requires a certain version of libc.
I've googled around and apparently I can have the rust compiler link it against musl instead of glibc, which would be done statically. But the problem is that stonet also depends on SQLite 3. And the libsqlite3-0 package on debian is build on glibc, not musl, so then I would also have to bundle sqlite or link to it statically as well.
It can be done, but I don't think it is really worth it to bundle sqlite into stonenet by default for linux.
However, I would be able to add a stonenet-bundled package to the repo maybe...

Ok, I have no problem compiling the bundled packages, but I have to take some time to see how I can have these bundled packages co-exist in the same package repo.

Well if you're going for bundling, you might as well use something like Tauri and have full-fledged cross-platform working bundles. I'm not sure that's the phase of the project now, on the other hand, it would make it a lot easier for a whole bunch of people to install it.

Yeah Tauri has a one problem:
I intend to have a windows installer at some point, but Tauri uses the Wix toolset for that, which can only generate the installer/setup file from a windows machine. And I don't want to bother with windows every time I release a new version. :p Right now I am already building a .exe file from my debian installation everytime.
But I have already successfully set up the bundled builds. I still need to test them on a system with an older libc version or something.  And I also need to figure out how I can configure my package repo to have both 'type' of packages in it.

Alright, packages that have libsqlite3 and musl (an alternative for libc) statically linked are now available when using this apt line:
deb http://get.stonenet.org/debian stable bundled

Which should work for older systems. Next up: nix packages.

Alright, packages that have libsqlite3 and musl (an alternative for libc) statically linked are now available when using this apt line:
deb http://get.stonenet.org/debian stable bundled

Which should work for older systems. Next up: nix packages.


Add YouTubers

https://github.com/JoseDeFreitas/awesome-youtubers
"Watch videos and playlists from YouTubers that teach you about technology." In this list, you can find YouTube channels that teach several technology topics, such as programming, design, security, and a lot more. I created this list because I find very often video tutorials much better than documentation. You can learn a lot with the playlists and videos these YouTubes have created.
2 pull requests I've reviewed: #1859 and #1866.
The only issue awesome-lint is throwing is "Missing main list heading". The title is correct, but not using markdown format (# Title) but instead HTML tags (
Title
). This is because I want the header to be centered, and I couldn't do it without HTML. I've already seen lists that have also a centered title. This is not a big issue though. If you want me to set the title to markdown code instead of HTML I can do it without problems, it's just a styling issue.
By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Pull request and list requirements
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions.
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ add Swift
❌ Adding Swift
❌ Added Swift

Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

Your entry should be added at the bottom of the appropriate category.
The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
The default branch should be named main, not master.
Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.

✅ awesome-swift
✅ awesome-web-typography
❌ awesome-Swift
❌ AwesomeWebTypography

The heading title of your list should be in title case format: # Awesome Name of List.

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ # AwesomeSwift

Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything.
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.

Has an appropriate license.

We strongly recommend the CC0 license, but any Creative Commons license will work.

Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=master&template=cc0-1.0 (replace <user> and <repo> accordingly).

A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
Place a file named license or LICENSE in the repo root with the license text.
Do not add the license name or text to the readme. GitHub already shows the license name at the top of the repo.
To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't use hard-wrapping.
Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.
Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

unicorn

@JoseDeFreitas it seems like you didn't read the guidlines carefully enough. Did you review at least two other repositories?
I like that you also have lists in other languages, are those linked from the main list?

@wernerkrauss hello! I've read the guidelines carefully. I've reviewed two pull requests: #1859 and #1866 as I said in the main comment of this pull request. I've also reviewed another two pull requests but didn't include them because I got no response.
The lists from other languages follow the same rules as the main list, but they're apart because English should be the first language (and I think all awesome lists are mainly English.) As this is a wide topic, I created that "other-languages" folder, but the main is in the README file. THank you for your comment and I'm glad you liked the other languages 😁.

I'm pretty sure I'm going to check out a lot of channels from this list! This list really has a lot of effort put in, and the only thing I can do for the review is just nitpicking.
I ran awesome-lint on the repo, and it came up with this linter error:
✖ Linting

  readme.md:1:1
  ✖  1:1  Missing main list heading  remark-lint:awesome-heading

  1 error

If it doesn't bother the other contributors, I think this can be disabled. (https://github.com/sindresorhus/awesome-lint#special-comments)
Also, from the "Game Development" section, I wouldn't omit the channel Molly Racket where the Handmade Hero series is created. :D

You can add  at the beginning to disable this linter warning and keep the centered title formatting:
✖ Linting

  readme.md:1:1
  ✖  1:1  Missing main list heading  remark-lint:awesome-heading

  1 error

Also, I wouldn't omit the creator of the Handmade Hero Youtube series from "Game Development". :D

@balintkissdev Hello! That's weird. I've seen some lists with a heading like mine's so I decided to write mine that way. I just added that flag to my file so that the error can be omitted. The heading is well-formatted but I guess awesome-lint doesn't lint HTML code. Thank you for letting me know! Also, thank you for recommending that channel; I'm going to check it out 😉

Tweet: https://twitter.com/awesome__re/status/1347988356139913216

Tweet: https://twitter.com/awesome__re/status/1347988356139913216


Feature: Keyboard shortcuts for adding, substracting, start/stop

To add keyboard shortcuts for adding, substracting time, start/stop.

I'm considering enter for start, stop, continue.


Add error message for incorrectly ordered clause in sql

Add error message for incorrectly ordered clause in sql
Add unit tests to verify

This PR has:

[x] been self-reviewed.
[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)
[ ] added documentation for new or modified features or behaviors.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[x] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[ ] been tested in a test Druid cluster.

Thanks for the PR! Can you please update the description to be more descriptive?


建议将删除变得简单些

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

你这 issue 简单得我都不知道你期望改成什么样 : |


Color support in the logging library

Consider adding color support to the logging library.

This issue has been moved to dart-lang/logging#8.


NFTikets

Staging Link
https://nftikets-bromagift.vercel.app/
Grant category
Please select one or more of the:

[ ] Open source maintenance
[#] Developer tools / services
[ ] Educational material

Description
Nftikets is an event ticket minting platform that allows users to create, purchase and mint tickets for any of their events as NFTs. Using our Widgets, API, and SDKs, event hosts will be able to integrate this feature on their websites with few lines of code.
Problem Statement

Tickets to offline events can be duplicated without authorization
Tickets to online events are difficult to access by people from other locations due to barriers in payments
Event organizers constantly need to redirect users to the purchase page of the platform where their events are hosted.
Verifying tickets online is hard for platforms like Eventbrite and takes a lot of time per user.

Target audience

Event organizers looking to sell tickets to a global audience without avoiding payment portal issues.

## Evidence for the need
Proposed solution

Low cost of producing tickets: you can mint 100 tickets with low gas fees
Borderless way to purchase tickets
Zero paper ticketing (very ecological)
Easy integration on event owner website, with very few lines of code.
Tickets can be purchased on telegram by your community without even visiting the website (Ease)
Swift ticket verification API: The event owner can verify a ticket by inputting the wallet address only

Impact

This will help reduce paper ticketing for offline events.
Enable borderless events from anywhere in the world
Improve event ticketing using NFTs
Store individual tickets as NFTs

In what ways does this benefit the broader Flow developer ecosystem?

Increase use case for the ecosystem
More users interating with the flow blockchain

Milestones and funding

Note: You can leave the USD proposal empty / "TBD". Please consider adoption and/or maintenance milestones at the end of your project.

Milestone
Deliverables
Timeline
Risks
USD proposal

1 - MVP
Functional website that allows users to mint event ticket and smart contract
3 weeks
-
8000

2- BETA
Developer Portal with Docs for integrating our API's
8 weeks
-
15750

3. Launch
400 events
3 weeks
-
4600

4. Maintenance
Resolving issuing and fixing bugs
2 months
-
2600

Team

Name
Role
Bio
Contact

Godwin Jimmy
Product Mangager
As a Product Manager, I have managed the development and deployment of various blockchain applications some of which are: Plutoswap (DEX), Dantown (https://www.dantownms.com/), Social Stack (https://www.socialstack.co), Cyrus NFT (https://www.cyruspahlavi.com/), Zoo NFT  (https://zoolabs.io/).
<EMAIL_ADDRESS>

David Esser
Advisor(Product)
Chief Product Officer at Minterestt, Serial entrepreneur building blockchain, defi, internet, mobile, and IoT applications Specialties: -- Product Management for enterprise blockchain, internet, and mobile applications.-- Strategy and implementation for complex technology products.-- Building & leading extremely capable teams of technologists to deliver amazing quality and productivity results
<EMAIL_ADDRESS>

Victor Ogbonna
Lead Frontend
A frontend engineer with 3 years experience in javascript, react, next, web3.js and threejs.
<EMAIL_ADDRESS>

Ayolehi Lurogho
UI/UX Designer
UI/UX design with 4 years of experience in design and have worked on a series of projects cutting across payments gateways and Defi products.
<EMAIL_ADDRESS>

Gift Elenwo
intern Frontend
A computer science graduate with 6 months of experience in javascript and react
<EMAIL_ADDRESS>

Juliet Babatunde
Content Developer
Content Developer and Copyright with 2 years experience.
<EMAIL_ADDRESS>

thanks for the submission @Jimmygodwin - how would this compare to https://floats.city ?

Hello Alex
For Float, event owners have the option of creating their events and must force users back to float to claim this event ticket, However, for Nftikets we give the event owner the ability to create this event on our platform after which they make these tickets available for their users on telegram, Twitter and discord. With our code snippets, anyone can easily create and share an event without having a vest knowledge of web3 and without having to educate their buyers on how to claim tickets
Nftikets is built on a series of users behavior research and I can tell you for a fact their complexity will lead to a high bounce rate, unlike the other platforms Nftikets will give users the web 2 feeling in a web3 environment, which means they may not even have to understand web3 to use our service.
For the event owners, our SDKs/API gives them the luxury of integrating their NFT's on their own websites or social media making it a worthwhile user experience for their customers.

got it! and a few more questions that came up:

Can you provide a clearer definition of your target audience (who are the organizer, ticket holders) and use cases you want to focus on solving?
What types of ticketing would be supported  (eg membership, single use, etc)
What are the properties each ticket would have (eg metadata, state)?

Okay,

Currently our research and build is targeted at servicing organizers of tech events globally (online and offline events), here is a brief on our user profile

Targeted User

User Type:  Event Host/Organizers
Event Type: Tech Event
Event Specifics: Web 2/web 3 events
Event Channel: Online/Offline
example: South South Blockchain Conference ( https://ssblockchaincon.com/ ) we are already in talks with this conference and they will be glad to use our ticketing system.

Why Target this audience

it is niche market
It is Easy to understand and adopt
Value from the product (Financially: it cost about $250 - $350 to print 100 copies of colored tickets ,and Ecological)
Longterm value for event tickets
Maintain Attendees attention beyond event (Membership tickets)

Use Case

Event Ticketing

Types of Tickets we support

Single
membership
Partnership (Donations)

Properties/Meta Data

Single ticket

Event name
Host name
Event description
Ticket number
image/pdf

An Example
{
"title": "Single Ticket Metadata",
"type": "object",
"properties": {
"event name": {
"type": "string",
"description": "Nftikets Global NFT events"
},
"host name": {
"type": "string",
"description": "Nftikets Global NFT events"
},
"event description": {
"type": "string",
"description": "Welcome to the NFTikets global Nfts event"
},
"ticket number": {
"type": "int",
"description": "3092039"
},
"image": {
"type": "string",
"description": "image URL."
}
}
}

Membership ticket

Event name
Host name
Event description
Ticket type (membership)
Ticket number
image/pdf

An Example
{
"title": "Single Ticket Metadata",
"type": "object",
"properties": {
"event name": {
"type": "string",
"description": "Nftikets Global NFT events"
},
"host name": {
"type": "string",
"description": "Nftikets Global NFT events"
},
"event description": {
"type": "string",
"description": "Welcome to the NFTikets global Nfts event"
},
"ticket type": {
"type": "string",
"description": "Membership"
},
"ticket number": {
"type": "int",
"description": "3092039"
},
"image": {
"type": "string",
"description": "image URL."
}
}
}

Partnership tickets(Donations)

Event name
Host name
Event description
Ticket type (membership)
Ticket number
image/pdf

An Example
{
"title": "Single Ticket Metadata",
"type": "object",
"properties": {
"event name": {
"type": "string",
"description": "Nftikets Global NFT events"
},
"host name": {
"type": "string",
"description": "Nftikets Global NFT events"
},
"event description": {
"type": "string",
"description": "Welcome to the NFTikets global Nfts event"
},
"ticket type": {
"type": "string",
"description": "Donation"
},
"ticket number": {
"type": "int",
"description": "3092039"
},
"image": {
"type": "string",
"description": "image URL."
}
}
}

thanks @Jimmygodwin
cc @albeethekid @srinjoyc

hey @Jimmygodwin, we're excited to let you know that we've accepted your grant application! 🙌
I'll follow up with you via email with next steps.

Hello @alxflw that is exciting news! I have received the mail I will follow up on it immediately.


document table enhancement

#23120

[x] Fixed issue on clicking (x) button on dropdown filter
[x] Added 3 characters delay into input fields
[x] Added sort direction
[x] Document Type - Sentence Case

/gcbrun

Temporary Url for review: https://documents-ui-dev--pr-72-rthu6m96.web.app


webgpu: uniforms, makeBindGroup/Layout, non-square tiles

To see the logs from the Cloud Build CI, please join either
our discussion
or announcement mailing list.

This change is

Sorry this patch has gotten kind of big. PTAL


React tutorial: Exercise

In this exercise, I consolidate my knowledge about React, components, props, states, and hooks, by following React tutorial.

👍


BUG: unicode

Description
Fixes the bug that generated an outage in mainnet due to a contract with unicode characters.
closes #698
Checklist

[ ] Linked to Github Issue
[ ] Unit tests added
[ ] Integration tests added.
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

Codecov Report

Merging #705 (4fae723) into main (ec11683) will increase coverage by 0.13%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #705      +/-   ##
==========================================
+ Coverage   91.97%   92.11%   +0.13%
==========================================
  Files          52       52
  Lines       11341    11339       -2
==========================================
+ Hits        10431    10445      +14
+ Misses        910      894      -16

Impacted Files
Coverage Δ

...re/contract_address/deprecated_contract_address.rs
93.71% <100.00%> (+7.59%)
:arrow_up:


Fix mispelling

@ziquanmiao - thank you for reporting this! we've updated the page you mentioned to fix the typo.


Moves the Cut Geometry and Style WMS Layers controls

From the top right to bottom center.
Also changes the button in Symbolize Shapefile to the Push style.

On macOS it is most common for controls to be toward the top of a view rather than at the bottom. Why were these controls moved to below the map view?


Rename fix

Oops, sorry! accidentally opened this because github always provides this as the first option.
I will close this.


healthsites-architecure

#888

Some considerations:

https://wiki.openstreetmap.org/wiki/API_usage_policy
https://wiki.openstreetmap.org/wiki/Import/Guidelines
https://wiki.openstreetmap.org/wiki/Automated_Edits_code_of_conduct

To avoid having your access blocked, please discuss your requirement with system administrators either via their wiki pages or on the IRC channel prior to starting.

https://wiki.openstreetmap.org/wiki/System_Administrators

[ ] TODO Tim to contact Grant Slater to socialise

[ ] Step 1 - Prerequisites
[ ] Step 2 - Community Buy-in
[ ] Step 3 - License approval @markherringer for this we should open a ticket that on the upload form for new sites the uploader must give consent that the data will be published under OSM license and that they they have the authority to do so.
[ ] Step 4 - Documentation @markherringer Task for you
[ ] Step 5 - Import Review - @markherringer please check with Grant if this would apply to us
[ ] Step 6 - Uploading - @markherringer same comment as above

Edits code of conduct
In general we will not be making batch changes / automated changes to the OSM data behind HS. When a user edits a single record we will push that straight to OSM. We should include as statement in out compliance wiki page saying that we will agree to abide with the CoC.

Step 2
Review how we will track changes. Perhaps we can use osmcha (https://osmcha.mapbox.com) to cross reference each change to a change in HS.IO.
Alternatively we need a way to propagate HS changeset ids through OSM and back to HS


Older version on TestFlight than on App Store

Hi,
this is not an issue, more a question. I'm a little bit confused about the notification I received this morning from TestFlight. There's a new beta version 0.7.9 available. But I saw the version on App Store is 1.1!
What is the newer one?
Sorry I don't know how to change the label. 😏
Best wishes
getwet

Hello
I am not 100% sure as i dont do the apple release / testflight myself.
however i think 0.7.9 is the internal version numbering used on github.
Where as 1.1 seems to be another version number running on the app store. (probably just the second version ever released there)


Don't show loading indicator between iterations when loop is on

Sample use-case: gif-like looped/autoplayed videos with no controls - the loading indicator isn't needed and disrupts the seamless infinite loop.
http://www.annenbergdl.org/tutorials/diy-series/how-to-make-a-cinemagraph/#advanced-cinemagraph-video

@celloexpressions Is this still an issue?

Closing this issue since no answer has been posted in more than 2 weeks. If you'd like to reopen this, let us know. Thanks!

Sorry about the slow response.
Yes, this is still an issue on some videos, although testing with a few, there is no loading indicator between iterations on others. Both I'm testing with are .mp4 only and fairly small, so not sure what the distinguishing factor is.


[DO NOT MERGE] Only add a reaction if we haven't yet

Fixes #492
This now mimics the GitHub behavior: reacting twice removes the first, reacting once... adds it, obviously.

This now totally no-ops, but wanted to add the addition of the delegate. Talked with Ryan and he'll take a look at this soon 👍


Coverage decreases while no code is changed

Describe the bug
A clear and concise description of the bug.
I am developing a package manager pdm which provides a script runner, just like pipenv run or poetry run.  But when I tried to apply it to my other project, I noticed a significant decrease in the testing coverage: https://github.com/frostming/marko/pull/46, because I didn't change a line of the Python code, just changed the way how to invoke the testing to pdm run. pdm run will call a subprocess running pytest --cov marko tests, with the __pypackages__/<major.minor>/lib injected into PYTHONPATH.
Any help is appreciated.

I don't understand what you are doing, or what you are seeing.  How can I help?

I put all lib files under __pypackages__/<major.minor>/lib, when running the tests, the path will be inserted into sys.path, the directory is like this:
foo
    __pypackages__
        3.8
            lib
                bottle
    foo/
    tests/

The configuration is
[coverage:run]
branch = True
parallel = True
source = foo/
omit =
    foo/cli.py

[coverage:report]
# Regexes for lines to exclude from consideration
exclude_lines =
    # Have to re-enable the standard pragma
    pragma: no cover

    # Don't complain about missing debug-only code:
    def __repr__

    # Don't complain if tests don't hit defensive assertion code:
    raise AssertionError
    raise NotImplementedError
    # Don't complain if non-runnable code isn't run:
    if __name__ == .__main__.:

Then I saw the coverage decreased by 13% compared with the old venv manner.


Bug: "Where does your code run?" answer is ignored by @eslint/config@latest

Environment
Node version: 21.7.3
npm version: 10.5.0
Operating System: Darwin 23.4.0
What parser are you using?
Default (Espree)
What did you do?

Create empty folder. Run npm init inside, all default answers.

Execute npm init @eslint/config@latest. Answer as follows:

✔ How would you like to use ESLint? · style
✔ What type of modules does your project use? · esm
✔ Which framework does your project use? · none
✔ Does your project use TypeScript? · javascript

Answer to the question "Where does your code run?" is ignored and eslint/config proceeds as if "browser" answer was given.
What did you expect to happen?
✔ Where does your code run? · node

What actually happened?
✔ Where does your code run? · browser

Link to Minimal Reproducible Example
http://example.com
Participation

[ ] I am willing to submit a pull request for this issue.

Additional comments
Reproducible 100%. Previous answers don't matter. Pressing "a", "i" or spacebar during that question prompt are ignored - nothing changes in UI.

Duplicate of https://github.com/eslint/create-config/issues/74

please note it's a multi-selection.


Crafting doesn't work

Crafting doesn't work. The Recipe below, doesn't make the "Ice Boots"

Instead of including air in the craft, try removing B from the shape.
shape:
  - "   "
  - "A A"
  - "A A"


Pub failures with bad snapshot reporting

Also see issue #20802...
http://build.chromium.org/p/client.dart/builders/pub-mac-be/builds/11237/steps/pub and pkg  tests failures/logs/stdio
For now these tests are marked as failing.

This issue has been moved to dart-lang/pub#1242.


GitHub actions

I am cleaning up the GitHub actions for this repository. Done so far:

Eliminated the lint action (can be done at the command line or from RStudio admin easily, if needed, and not vital)
Updated R-CMD-check, pr-commands and test-coverage
Attempted to get pkgdown succeeding

I struggle with the covrpage section in the pkgdown action, and more particularly with {git2r} that seems incorrectly installed. If I understand it well, this section updates the test covering report in the pkgdown web site, is this correct? The "codecov" badge on the README page already gives access to a detailed and interactive report of the same data. Also, this seems to be more "technical" information that most end-users do not need. I feel that the coverage report page in the "articles" section of the website should not be there. Would it make sense to just delete this covrpage section in the pkgdown action?
One more stuff: what is the reason for recompiling from sources {Matrix} and {lme4} in the R-CMD-check and pr-commands actions? Is it still needed? These GitHub actions take much longer than they should if this is not required (any more).

The recompiling one related to some mixed versions or something along those lines a while back that was causing the whole thing to fail. Installing from source was the only way I could figure out to fix it. Totally fine to change if you want.
I'm also totally fine deleting the covrpage section. That was put in by a PR from a collaborator and I was never super sold on it but he had contributed other meaningful pieces and felt strongly about it so I went with it.


Configure Prettier in project

Add Prettier to the project to format

Add Pretier
Configure Pretier
Add command npm run format to format the whole project

Hey @rohitt-gupta, could this issue be assigned to me please


Add ReceiveMessages

ReceiveMessages would implement Stream<Item = M>, created by calling ActorContext.receive_many.

Blocked on #354.

Blocked on #354.

Currently don't see the benefit over while let Ok(message) = ctx.receive_next().await { /* ... */ }. Might be worth reconsidering once the Stream trait becomes a bit more useful in std lib.


Dot in pathname

When using dots in pathname the routes don't get included in the generated swagger. Is there any specific reason for this?
Example
import swagger from "@elysiajs/swagger"
import Elysia from "elysia"

const app = new Elysia()
  .use(swagger())
  .get("/test", () => "Hello World")
  .get("/test.2", () => "Hello World 2")
  .group("/v1.2", (app) => app.get("/test", () => ({ status: "ok" })))
  .listen(3001)

Routes with dot in the path are not included

EDIT
So it seems like if i set excludeStaticFile: false, it does indeed include my paths with dots since the filterPaths in utils considers any path with a dot as a static file.

Hey 👋
Here is the incriminate line
https://github.com/elysiajs/elysia-swagger/blob/main/src%2Futils.ts#L333
Don't really know if there is a better way to detect static files? Check only in the last route param ?


fix(amplify-graphql-docs-generator): Support scalar returns in statements

Fixes #264
Statement generator generated invalid graphql statements when an operation had scalar type as return by adding an empty body around the statement. Updated code to conditionally add body.
If the graphql schema had an mutation
deletePodcast(input: DeletePodcastInput!): String

the statement generator used to generate
mutation DeletePodcast($input: DeletePodcastInput!) {
  deletePodcast(input: $input) {
  }
}

which is not valid graphql. With this update the generated statement looks like
mutation DeletePodcast($input: DeletePodcastInput!) {
  deletePodcast(input: $input)
}

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This PR has the version bumps as well. Is that intentional?

Nope, re-based it


Add TickTick extension.

Description
Add TickTick extension.
Type of change

New extension

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I checked that extension's icon has size of 512x512

Hi @pernielsentikaer, thank you for your review.
I add the new "Next 7 Days Tasks"  command as you suggest.
For other suggestions, due to the TickTick app apple script support limit, I can't implement it right now, maybe develop in the future.

Hi @viduycheung 👋
What a banger for the first contribution 💪 Everything works and errors is gracefully handled, well done 🥇
A few comments:

It would be cool if the results from the search also was grouped by date like the command.
Add “Next 7 Days” command
Add a “Create Task” command — not sure if it's even possible

Not all of above have to be in this PR if you just want it shipped, but would add a lot of value.
Request a new review when you are ready, feel free to contact me here or at Slack if you have any questions.

Hi @pernielsentikaer, thank you for your review.
I add the new "Next 7 Days Tasks"  command as you suggest.
For other suggestions, due to the TickTick app apple script support limit, I can't implement it right now, maybe develop in the future.

Hi @viduycheung 👋
Thanks for the update, that's an excellent update! 💪
Comments:

In both command, do you have access to the category they are in, so it looks like when searching

Could you add a space between the emoji and the text easy, or is it just as good as it gets?

We're pretty close to merging 🥇

All issue has been fixed ✌

Hello, @viduycheung I've been using your extension and was wondering if it was possible to pull a filtered list of tasks? I was unable to find any documentation on the apple script support.
Thank you

Hello, @viduycheung I've been using your extension and was wondering if it was possible to pull a filtered list of tasks? I was unable to find any documentation on the apple script support. Thank you

Hi, this extension future limit by TickTick macOS App Applescript support right now 🙈, maybe implement in the future~


Correctly use const_panic feature in this crate

Indirect the checking of size through a function that is evaluated in this crate, not in the crate that is invoking the macro. This ensures that the declared const_panic feature is correctly evaluated as a feature of this crate, not the consuming crate.
Fixes #3

@Daniel-Aaron-Bloom can you confirm this implements what you intended in #2?


feat(spinner): add pending actions to state

Resolves #69
You can test it while transfering tokens!

Noticed same issue as with account creation toasts. Will fix it soon! :)


Unable to reassign factory attribute defined as a sequence

Description
I'm trying to write a simple test that validates the presence of an email attribute defined as a sequence in the factory, but the assignment fails and the email attribute retains its value.
Reproduction Steps
I have a factory that uses a sequence to set the email attribute on a user:
FactoryBot.define do
  factory :user do
    first_name { 'John' }
    last_name { 'Doe' }
    sequence(:email) { |n|<EMAIL_ADDRESS>}
    password { 'password' }
  end
end

I can't assign email to a new value in my test:
require 'test_helper'
describe User do
  subject { build :user }

  it "must be a valid object" do
    _(subject).must_be :valid?
  end

  it "requires an email address" do
    subject.email = nil
    _(subject).wont_be :valid?
  end
end

Expected behavior
Within the test, I expect the value of subject.email to be nil when the assertion is evaluated.
Actual behavior
The value of subject.email is still the value assigned by the factory upon build (e.g<EMAIL_ADDRESS>when the assertion is evaluated. In a pry session, I see something similar to this:
> subject.email
#<EMAIL_ADDRESS>> subject.email = nil
# nil
> subject.email
#<EMAIL_ADDRESS>
System configuration
factory_bot version:  5.1.2
rails version:  <IP_ADDRESS>
ruby version: 2.4.9

Hm, that doesn't ring any bells for me. Once the object is built, I can't think of any reason why factory_bot would affect how later attributes get assigned. Can you provide a reproduction script in this format: https://github.com/thoughtbot/factory_bot/blob/master/.github/REPRODUCTION_SCRIPT.rb

I'm going to close this for now, since it is not something I can reproduce. But we can reopen it if you are able to provide a reproduction script. Thank you!

Turns out someone overrode the writer method (def email=(value)) that had a guard clause in it for empty? values.


Add DOI and citation.cff

Once we get a DOI for the manuscript (preprint or ECML submission), add this to

[ ] readme
[ ] CITATION.cff file

Don't count on the DOI for the paper. IIRC neither openreview.net NOR PMLR attribute DOIs or run a service for this.

OK, thanks.
We could still add the link to the paper (if accepted), and/or also put it on a preprint server at a later stage.

sounds like a plan!


Automatically fill in treasure options for a scenario

It would be nice if we didn't have to manually type in the treasure number and name for each scenario.  I understand you might not want to spoil yourself, but maybe you could take the treasure data from https://github.com/dmungin/gloomhaven-scenario-tree-ng/blob/master/src/assets/scenarios.json

That's true. I don't like the treasure managment too. When I find some time I will take care about it.

If I can be of assistance again on this one by cataloging the info, let me know.

It will be part of the new scenario management in 1.4.4


Inquiry on Real-Time Grasp Prediction Methodology

I recently came across your work, and I must commend you on the groundbreaking results and the innovative approach your team has adopted. The videos showcasing real-time grasp prediction were particularly inspiring.
Would you be willing to share more insights or any advice on replicating such real-time grasp prediction capabilities?

Thanks for your interest! We make the video by simply deploying our method with a realsense d435i camera. The grasp detection process is the same as that in the demo.


Selectors occassionally cut into reference axis

I've included pictures of that case below. I moved the selectors up in the second photo, is that a good positioning?

Also, I feel like the chart title is a little too small now, should we bump it up a bit?

@daterdots


Select All command does not work when in text fields in Property Panel

When you are in the property panel and you need to select all text in a field, the Select All command does not function/does not select all text.

For mac, current work around is to use Shift+Command+Arrow Key direction that you want to select all from cursor.

There were a few Electron regressions. Please verify if this behavior got fixed with the latest Camunda Modeler release (v1.2.2).

Fixed with new Electron version.


feat:Add a gallery section in the home page

I would like to work on this issue under JWOC

I would like to work on this issue under JWOC.plz assign it me.

Hi @codervivek5 , since @AtriSukul1508 is working on this issue, do you want to take up new issues?

Hi @codervivek5 , since @AtriSukul1508 is working on this issue, do you want to take up new issues?

yes I want...

Great, let me open new issues for you


Updates from C3DIS

Based on going through these tutorials as C3DIS we found some issues that need to be updated.  For future reference:
xarray notebook: sst_ts_rolling = sst_ts.rolling(time=24, center=True).mean()
Landsat8 notebook:  band1 = da.sel(band=1).drop('band').persist()
(other wise hvplot sees the 'band' coord and interprets it as RGB)
gmet_ensemble notebook: ax = pcp_ann_max_ts.plot.line(x='time', add_legend=False)
is more readable (and faster!)

Hi @jmunroe!
Thanks for the feedback here.
I understand you've forked the repo for your tutorial. Did you make the suggested change on your repo? Would it be possible to open one or several PRs for them?
And also, as you mention Landsat8 notebook, did you run into the issue described in #12?


Geolocator.requestPermission() never returns in Android 5.0 (API 21)

🐛 Bug Report

Geolocator.requestPermission() never returns in Android 5.0 (API 21).
Expected behavior
It could always return LocationPermission.always as Android 5.1 (API 22) and below does not require explicit location permission request.
Reproduction steps

Run your app in an Android 5.0 emulator or physical device. I did not test for Android 5.1 or other versions below, but it will probably have the same behavior.

Run the following code:

final permissionStatus = await Geolocator.requestPermission();
print('This line is never reached');

Configuration
Version:
geolocator: ^6.1.8+1
flutter 1.22.4
Platform:

[ ] :iphone: iOS
[X] :robot: Android

hello danil, you can see my issue? I think it's a similar case, but i haven't received help yet . tkx!

@danilocubos, I have just released version 6.1.9 of the geolocator plugin which includes the fix you provided in #611.
Thank you very much for your contribution, it is much appreciated.
@robertoalvesneto can you test if this also solves your problem? If not, please follow up in #584 and I will get back to you.

@mvanbeusekom It didn't solve my problem. But my problem is the same in #585, i'm  following

Thank you from japan!


Close date is only there for some cards on main feed

Current behavior
On beta this is what it looks like... and on dev it seems no cards have close date.

Expected/desired behavior
Every card should have that little radial lifetime indicator and "Closes [date]"

closed as complete


encodeHex not taking letters

MongoDB Object Id's not able to be encoded.
I tried using MongoDB Object Ids but they fail. I am using the latest version (2.0.4) (i upgraded from 2.0.3 to see if it would fix it). I am using encodeHex() but letters make it fail.

The following code from the readme fails:
use Hashids\Hashids;

$hashids = new Hashids();

$id = $hashids->encodeHex('507f1f77bcf86cd799439011'); // y42LW46J9luq3Xq9XMly
$hex = $hashids->decodeHex($id); // 507f1f77bcf86cd799439011

In encodeHex() here is the print_r before it gets sent to encode
Array ( [0] => 3.6998189572018E+14 [1] => 4.0114822182094E+14 )
It gets terminated here:
foreach ($numbers as $number) {
            $isNumber = ctype_digit((string) $number);

            if (!$isNumber) {
                return $ret;
            }
        }

Where the return $ret is.

Hmm, we have a test for the line you say fail:
https://github.com/ivanakimov/hashids.php/blob/587d2624fd9c2d4cc153cfb8afe28f23152dffa6/tests/HashidsTest.php#L210
As for Mongo IDs, I suggest you take a look at this issue.


fix timeout issue with Dalli::Client#get_multi_yielder

Fix Dalli::Client#get_multi_yielder so it doesn't timeout as long as
data is immediately available for reading.  We were seeing spurious
timeout errors such as:
memcache-host:11211 failed (count: 0) RuntimeError: External timeout

when doing large (100+ item) multi-get operations.  This fixes the problem.

I investigated the above unit test failure (failover::timeouts#test_0001_not lead to corrupt sockets, in test/test_failover.rb), and determined that my code changes are not to blame.  Even without my code changes, I observe the test failure sporadically when repeatedly running the unit tests.  In an effort to shed some light on why the failure is occurring, I added instrumentation to test/test_failover.rb, as shown by the following diff:
--- a/test/test_failover.rb
+++ b/test/test_failover.rb
@@ -6,6 +6,7 @@ describe 'failover' do
     it 'not lead to corrupt sockets' do
       memcached_persistent do |dc|
         value = {:test => "123"}
+        x = nil
         begin
           Timeout.timeout 0.01 do
             start_time = Time.now
@@ -14,10 +15,18 @@ describe 'failover' do
             end
             flunk("Did not timeout in #{Time.now - start_time}")
           end
-        rescue Timeout::Error
+        rescue Timeout::Error => e
+          x = e
         end

-        assert_equal(value, dc.get("test_123"))
+        dc_get_result = dc.get("test_123")
+        puts '--- start stack trace ---'
+        puts x.backtrace
+        puts '--- end stack trace ---'
+        puts '--- value: -->' + value.to_s + '<-- ---'
+        puts '--- dc_get_result (class: ' + dc_get_result.class.to_s +
+            '): -->' + dc_get_result.to_s + '<-- ---'
+        assert_equal(value, dc_get_result)
       end
     end
   end

With the above instrumentation added, here is output from a run in which the failure occurred (without the code changes in my pull request):
vagrant@devdemia:~/code/dalli$ rake
/home/vagrant/.rbenv/versions/2.0.0-p643/bin/ruby -w -I"lib:test" -I"/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/rake-10.4.2/lib" "/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/rake-10.4.2/lib/rake/rake_test_loader.rb" "test/**/test_*.rb"
malloc_limit=100000000 (8000000)
heap_min_slots=1000000 (10000)
Testing with Rails 4.2.1
Using kgio socket IO
Run options: --seed 15771

# Running:

Found memcached 1.4.14 in PATH
.......--- start stack trace ---
/home/vagrant/code/dalli/lib/dalli/server.rb:542:in `write'
/home/vagrant/code/dalli/lib/dalli/server.rb:279:in `block in set'
/home/vagrant/code/dalli/lib/dalli/server.rb:463:in `guard_max_value'
/home/vagrant/code/dalli/lib/dalli/server.rb:277:in `set'
/home/vagrant/code/dalli/lib/dalli/server.rb:63:in `request'
/home/vagrant/code/dalli/lib/dalli/options.rb:18:in `block in request'
/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/2.0.0/monitor.rb:211:in `mon_synchronize'
/home/vagrant/code/dalli/lib/dalli/options.rb:17:in `request'
/home/vagrant/code/dalli/lib/dalli/client.rb:333:in `perform'
/home/vagrant/code/dalli/lib/dalli/client.rb:107:in `set'
/home/vagrant/code/dalli/test/test_failover.rb:14:in `block (6 levels) in <top (required)>'
/home/vagrant/code/dalli/test/test_failover.rb:13:in `times'
/home/vagrant/code/dalli/test/test_failover.rb:13:in `block (5 levels) in <top (required)>'
/home/vagrant/code/dalli/test/test_failover.rb:11:in `block (4 levels) in <top (required)>'
/home/vagrant/code/dalli/test/memcached_mock.rb:83:in `memcached_persistent'
/home/vagrant/code/dalli/test/test_failover.rb:7:in `block (3 levels) in <top (required)>'
/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/minitest-5.6.1/lib/minitest/test.rb:108:in `block (3 levels) in run'
/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/minitest-5.6.1/lib/minitest/test.rb:205:in `capture_exceptions'
/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/minitest-5.6.1/lib/minitest/test.rb:105:in `block (2 levels) in run'
/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/minitest-5.6.1/lib/minitest/test.rb:256:in `time_it'
/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/minitest-5.6.1/lib/minitest/test.rb:104:in `block in run'
/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/minitest-5.6.1/lib/minitest.rb:332:in `on_signal'
/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/minitest-5.6.1/lib/minitest/test.rb:276:in `with_info_handler'
/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/minitest-5.6.1/lib/minitest/test.rb:103:in `run'
/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/minitest-5.6.1/lib/minitest.rb:779:in `run_one_method'
/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/minitest-5.6.1/lib/minitest.rb:306:in `run_one_method'
/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/minitest-5.6.1/lib/minitest.rb:294:in `block (2 levels) in run'
/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/minitest-5.6.1/lib/minitest.rb:293:in `each'
/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/minitest-5.6.1/lib/minitest.rb:293:in `block in run'
/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/minitest-5.6.1/lib/minitest.rb:332:in `on_signal'
/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/minitest-5.6.1/lib/minitest.rb:319:in `with_info_handler'
/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/minitest-5.6.1/lib/minitest.rb:292:in `run'
/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/minitest-5.6.1/lib/minitest.rb:155:in `block in __run'
/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/minitest-5.6.1/lib/minitest.rb:155:in `map'
/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/minitest-5.6.1/lib/minitest.rb:155:in `__run'
/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/minitest-5.6.1/lib/minitest.rb:129:in `run'
/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/minitest-5.6.1/lib/minitest.rb:56:in `block in autorun'
--- end stack trace ---
--- value: -->{:test=>"123"}<-- ---
--- dc_get_result (class: TrueClass): -->true<-- ---
F............................E, [2015-05-06T19:02:40.150814 #7541] ERROR -- : DalliError: No server available
E, [2015-05-06T19:02:40.169524 #7541] ERROR -- : DalliError: No server available
E, [2015-05-06T19:02:40.171060 #7541] ERROR -- : DalliError: No server available
E, [2015-05-06T19:02:40.171821 #7541] ERROR -- : DalliError: No server available
E, [2015-05-06T19:02:40.172294 #7541] ERROR -- : DalliError: No server available
E, [2015-05-06T19:02:40.172759 #7541] ERROR -- : DalliError: No server available
E, [2015-05-06T19:02:40.173252 #7541] ERROR -- : DalliError: No server available
E, [2015-05-06T19:02:40.173765 #7541] ERROR -- : DalliError: No server available
E, [2015-05-06T19:02:40.174517 #7541] ERROR -- : DalliError: No server available
E, [2015-05-06T19:02:40.174993 #7541] ERROR -- : DalliError: No server available
...........................................................................................

Fabulous run in 15.275113s, 8.3142 runs/s, 958.7491 assertions/s.

  1) Failure:
failover::timeouts#test_0001_not lead to corrupt sockets [/home/vagrant/code/dalli/test/test_failover.rb:29]:
Expected: {:test=>"123"}
  Actual: true

127 runs, 14645 assertions, 1 failures, 0 errors, 0 skips
rake aborted!
Command failed with status (1): [ruby -w -I"lib:test" -I"/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/rake-10.4.2/lib" "/home/vagrant/.rbenv/versions/2.0.0-p643/lib/ruby/gems/2.0.0/gems/rake-10.4.2/lib/rake/rake_test_loader.rb" "test/**/test_*.rb" ]

Tasks: TOP => default => test
(See full trace by running task with --trace)
vagrant@devdemia:~/code/dalli$

I hope this helps.  Could the problem be related to the following?
http://headius.blogspot.com/2008/02/rubys-threadraise-threadkill-timeoutrb.html
I'm not a Ruby expert, but it appears that the issues the article mentions may be relevant.


[MB-9288] Steel Cable Prime Simulator in Office App

Description
The office app already has multiple views depending on the roles available, so add a prime simulator role and a simple view of available moves, showing user based auth to the Prime API
Reviewer Notes
This is totally a proof of concept and ugly with no tests. I've only tested this using devlocal auth.
See the demo link here: https://office-milmove-pr-7404.mymove.sandbox.truss.coffee
Setup

Start the app locally with some test data
Visit the office app
Create a new Prime Simulator user
See the list of available moves

Code Review Verification Steps

[ ] If the change is risky, it has been tested in experimental before merging.
[ ] Code follows the guidelines for Logging
[ ] The requirements listed in Querying the Database Safely have been satisfied.
Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

Warnings

:warning:
This PR does not include changes to storybook, even though it affects component code.

:warning:
This PR does not include changes to unit tests, even though it affects app code.

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against b5bc79bce9b8b9081536929d11d45a6298940faf

I will have to rebase this onto the default branch here because there are conflicts to the migrations_manifest.txt. I propose we try to get this merged in ASAP @ahobson. What do you think?

I will have to rebase this onto the default branch here because there are conflicts to the migrations_manifest.txt. I propose we try to get this merged in ASAP @ahobson. What do you think?

Thank you so much for jumping on this. I'm sorry I didn't consider a better migration strategy when I started. If it's feasible to get it in sooner rather than later, I think it would help us a lot.
Should I transition this from a draft PR?

awesome. yes @ahobson I completely forgot this was still in Draft. lol thank you. yeah let's transition away from Draft for now.


Small optimizations for summary stats method

Get user once at beginning of method
Simplify query statements

@gzurowski I did some refactor when splitting the endpoints. Can you update after I merge here https://github.com/ResearchHub/researchhub-backend/pull/1768


feat: adds support to dotenv 4 to Collision 5

Why can't people just use the 4.x branch with Laravel 7?

Ok - we don't support Laravel 7 on Collision 5. ✅
Thanks @owenvoke for your work on this, sorry for wasting your precious time.

No problem at all, @nunomaduro. 👌 Laravel 8 will be out soonish anyway. 😋


remove reference to FleetResourcePreview feature

remove reference to FleetResourcePreview feature, no longer required

@serbrech double-checking with you that this change is OK?

@shashankbarsin - can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

LGTM. we already stopped requiring the feature to be registered when we announced Public Preview, so this in now an unnecessary step.

#sign-off

#sign-off


abnormal metopic suture morphology MP:0003842 - synonym/term label change?

abnormal metopic suture morphology MP:0003842
ADD NEW SYNONYM: abnormal median frontal suture morphology
(SOURCE: https://radiopaedia.org/articles/metopic-suture)
CORRECT EXISTING SYNONYM: abnormal intrafrontal suture morphology should be corrected to abnormal interfrontal suture morphology (see GO:0060364)
NOTE: In mice and rats, the posterior frontal (PF) suture, situated between the frontal bones, is analogous to the human metopic suture; the anterior landmark for the PF suture is the jugum limitans; the posterior landmark for the PF suture is the bregma
SOURCE: PMID:15882577
QUESTION:
A persistent frontal suture is referred to as a "metopic suture" (https://en.wikipedia.or/wiki/Frontal_suture, HP:0005556).
Should the primary term label for "abnormal metopic suture morphology" MP:0003842 be changed to "abnormal frontal suture morphology" using metopic suture as a related synonym for frontal suture?
GO, UBERON and MA use frontal suture; HP, MP, and VT use metopic suture.

I think the line in the HP definition is an error. See http://austinpublishinggroup.com/anatomy/fulltext/Anatomy-v3-id1049.php a persistent unfused suture is referred to as 'metopism'. The literature consistently refers to the normal suture as a metopic suture.

Sue, I think you are right. See also, http://austinpublishinggroup.com/anatomy/fulltext/Anatomy-v3-id1049.php, in humans, "the metopic suture generally fuses between 1 and 8 years of life. If it remains after that time it is known as metopism"

Left the primary term label as is: abnormal metopic suture morphology MP:0003842.
Added new synonym (abnormal median frontal suture morphology) and changed 'intrafrontal" to 'interfrontal' in existing synonym.
Amended definition to reflect that, in mice and rats, the posterior frontal (PF) suture is analogous to the human metopic suture.


Add in HTML (Mason) code beautifier

Description
Mason::Tidy beautifies Mason code. Could you add in a hook to atom-beautify. Basically the same as perltidy just a call to masontidy.
Expected Results
HTML (Mason) code would be beautified.

I am guessing this is Mason: http://www.masonhq.com/
I am guessing this is Mason::Tidy: https://code.google.com/archive/p/masontidy/

This might already be supported by Pretty Diff, which you can test out at http://prettydiff.com/?m=beautify

Just tried some mason code in prettydiff, did not work.

Pretty Diff does not appear to work with this syntax, so a new beautifier would need to be added.


Add documentation, fix build, upgrade deps, vendor pelias spatial server

Fixes #18
Fixes #3
This is very, very rough, but it's what I was able to get done in a few hours.

This doesn't cover the remote-index configuration, but it should be enough to get people up and running.

There's a bit more information in #3 on which downloads you want for WOF data and where to get them. I'll try and include that in a follow-up PR at some point.


Grammarly support

So uh, spell checker is pretty good but grammarly is better, is it possible to replace it?
Might be quite complicated but a really cool feature.

Grammarly is not open source nor does it have a public API so this is most likely not possible.

Well, obviously it's been a while since anyone mentioned this, so... Doesn't look like it's going to happen. If someone sees this and thinks they have more info about how to accomplish this, please make an issue on the plugins repo.


PageTransitionType Error

PageTransitionType is not being recognized

just add this import:
import 'package:page_transition/page_transition.dart';`


Webpack-native parallelism to obviate the need for the (unmaintained?) parallel-webpack package

Feature request
Per the webpack documentation , the package parallel-webpack is recommended to optimize multiple compilations. However, this package is increasingly outdated (it's not even specified for webpack 5). It would be good to have such functionality as a part of webpack itself, without relying on an outside project (that may itself be abandoned) to offer such support.
What is the expected behavior?
Webpack-native parallelism
What is motivation or use case for adding/changing the behavior?
The recommended package no longer appears to be actively maintained
How should this be implemented in your opinion?
I am not a lawyer, but the license of parallel-webpack suggests it might be possible to fork it directly.
Are you willing to work on this yourself?
not at this time
Related issue
https://github.com/trivago/parallel-webpack/issues/107

Feel free to send a PR to remove it from docs, now we are focused on cache (it already works very good), the next goal is parallelism

@alexander-akait I'm working on that PR now. I see that the only other utility mentioned in the docs in this context is webpack-contrib/cache-loader - which is actually explicitly deprecated already. I will remove that as well in the PR.
What I won't remove is the reference to cache-loader in the following code, as this appears to be used to build the site and I'm not sure what effect that might have:
https://github.com/webpack/webpack.js.org/blob/cd9568f0ec189cde5a9115302874f22e31d4c434/src/utilities/constants.mjs#L18

cache-loader is deprecated and should be not used

Thanks for updating docs!

Wait, this issue only tracked the removal of the reference to the unmaintained plugin and not the new development?

Let's keep open native parallelism is good idea

bump

bump

Bumpity bump

Is there an alternative to parallel-webpack? I have 38 packages being built in parallel and this is relevant for me to upgrade to webpack 5. Now these packages are built in 3 minutes. If you build in series with thread-loader connected, it takes 15 minutes and this is critical.

Sorry, no alternative, which things are slow


[BUG] Problems with llm/litellm or api key?

Description
I am trying to build my project and did set it up, as suggested, using the command 'crewai create crew my_project'. I do run this commend in crewAI repo folder.                                                                                After setting up my project, my_project folder contains subfolders: tests, src and files: myproject.toml, README.md and uv.lock. In src folder, I do have inside of it, again, my_project folder, with subfolders: tools, config and files crew.py and main.py.
The first question: this folder structure is a bit different from  the one shown in  https://docs.crewai.com/installation, is it a critical issue?  Note that also, in the process of setting my project, I selected following options from rundown menus: 6. (other) -> 5. (azure), and 13. (azure/gpt-4o-mini). Answering to the open to set OPENAI_API_KEY, I set it up in .env file.
The second question: if I selected Azure, should not it be set the AZURE_OPENAI_KEY, instead?                                           After setting all agents and tasks, I did try to run crewAI from my project folder, like 'crewai run'. I've got the lines: 'Running the Crew', 'Using CPython 3.11.10 interpreter at: /anaconda/envs/crewai311/bin/python', [0/218] Installing wheels.. I'Creating virtual environment at: .venv, Built my_project @ file....... Then warnings:                                                                   warning: Failed to hardlink files; falling back to full copy. This may lead to degraded performance.
If the cache and target directories are on different filesystems, hardlinking may not be supported.
If this is intentional, set export UV_LINK_MODE=copy or use --link-mode=copy to suppress this warning.
Installed 218 packages in 4m 24s. Not sure how to react to the warning promptly.                                                                   Then, crewai attempted to  load by Agents  and Tasks, and repeated the same loading two more times, each time with the same failure notice shown below.
Again, why there is a reference to openai.com, while it should be azure_openAI instance?? Any suggestion on how to fix this problem?  Thank you for your help!
Steps to Reproduce
It is demonstrated above
Expected behavior
tba
Screenshots/Code snippets
no screenshots
Operating System
Ubuntu 20.04
Python Version
3.11
crewAI Version
0.76.2
crewAI Tools Version
0.13.2
Virtual Environment
Conda
Evidence
2024-10-24 18:40:02,339 -<PHONE_NUMBER>02656 - llm.py-llm:161 - ERROR: LiteLLM call failed: litellm.AuthenticationError: AuthenticationError: OpenAIException - Error code: 401 - {'error': {'message': 'Incorrect API key provided: b***********************2d13. You can find your API key at https://platform.openai.com/account/api-keys.', 'type': 'invalid_request_error', 'param': None, 'code': 'invalid_api_key'}}.
Traceback (most recent call last):
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/xxxxx/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/litellm/llms/OpenAI/openai.py", line 854, in completion
    raise e
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/xxxxxProjects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/litellm/llms/OpenAI/openai.py", line 790, in completion
    self.make_sync_openai_chat_completion_request(
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/xxxxx/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/litellm/llms/OpenAI/openai.py", line 649, in make_sync_openai_chat_completion_request
    raise e
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/xxxxx/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/litellm/llms/OpenAI/openai.py", line 631, in make_sync_openai_chat_completion_request
    raw_response = openai_client.chat.completions.with_raw_response.create(
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/xxxxxx/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/openai/_legacy_response.py", line 356, in wrapped
    return cast(LegacyAPIResponse[R], func(*args, **kwargs))
                                      ^^^^^^^^^^^^^^^^^^^^^
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/xxxxxx/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/openai/_utils/_utils.py", line 274, in wrapper
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/xxxxx/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/openai/resources/chat/completions.py", line 815, in create
    return self._post(
           ^^^^^^^^^^^
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/xxxxxx/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/openai/_base_client.py", line 1277, in post
    return cast(ResponseT, self.request(cast_to, opts, stream=stream, stream_cls=stream_cls))
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/xxxxx/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/openai/_base_client.py", line 954, in request
    return self._request(
           ^^^^^^^^^^^^^^
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/xxxxx/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/openai/_base_client.py", line 1058, in _request
    raise self._make_status_error_from_response(err.response) from None
openai.AuthenticationError: Error code: 401 - {'error': {'message': 'Incorrect API key provided: bbac2b33********************2d13. You can find your API key at https://platform.openai.com/account/api-keys.', 'type': 'invalid_request_error', 'param': None, 'code': 'invalid_api_key'}}

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/xxxxx/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/litellm/main.py", line 1597, in completion
    raise e
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/xxxxx/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/litellm/main.py", line 1570, in completion
    response = openai_chat_completions.completion(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/81737/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/litellm/llms/OpenAI/openai.py", line 864, in completion
    raise OpenAIError(
litellm.llms.OpenAI.openai.OpenAIError: Error code: 401 - {'error': {'message': 'Incorrect API key provided: b********************2d13. You can find your API key at https://platform.openai.com/account/api-keys.', 'type': 'invalid_request_error', 'param': None, 'code': 'invalid_api_key'}}

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/xxxxxx/Projects/AIAgents/crewAI/py_course/.venv/bin/run_crew", line 10, in <module>
    sys.exit(run())
             ^^^^^
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/xxxxxxProjects/AIAgents/crewAI/py_course/src/py_course/main.py", line 17, in run
    PyCourseCrew().crew().kickoff(inputs=inputs)
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/xxxxxx/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/crewai/crew.py", line 494, in kickoff
    result = self._run_sequential_process()
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/xxxxxx/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/crewai/crew.py", line 598, in _run_sequential_process
    return self._execute_tasks(self.tasks)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/xxxxx/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/crewai/crew.py", line 696, in _execute_tasks
    task_output = task.execute_sync(
                  ^^^^^^^^^^^^^^^^^^
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/xxxxx/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/crewai/task.py", line 191, in execute_sync
    return self._execute_core(agent, context, tools)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/xxxxxProjects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/crewai/task.py", line 247, in _execute_core
    result = agent.execute_task(
             ^^^^^^^^^^^^^^^^^^^
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/crewai/agent.py", line 249, in execute_task
    result = self.execute_task(task, context, tools)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/crewai/agent.py", line 249, in execute_task
    result = self.execute_task(task, context, tools)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/crewai/agent.py", line 248, in execute_task
    raise e
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/crewai/agent.py", line 237, in execute_task
    result = self.agent_executor.invoke(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/crewai/agents/crew_agent_executor.py", line 93, in invoke
    formatted_answer = self._invoke_loop()
                       ^^^^^^^^^^^^^^^^^^^
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/crewai/agents/crew_agent_executor.py", line 175, in _invoke_loop
    raise e
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/crewai/agents/crew_agent_executor.py", line 115, in _invoke_loop
    answer = self.llm.call(
             ^^^^^^^^^^^^^^
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/crewai/llm.py", line 155, in call
    response = litellm.completion(**params)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/litellm/utils.py", line 1013, in wrapper
    raise e
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/litellm/utils.py", line 903, in wrapper
    result = original_function(*args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/litellm/main.py", line 3009, in completion
    raise exception_type(
          ^^^^^^^^^^^^^^^
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/81737/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/litellm/litellm_core_utils/exception_mapping_utils.py", line 2116, in exception_type
    raise e
  File "/mnt/batch/tasks/shared/LS_root/mounts/clusters/work-cpu/code/Users/81737/Projects/AIAgents/crewAI/py_course/.venv/lib/python3.11/site-packages/litellm/litellm_core_utils/exception_mapping_utils.py", line 343, in exception_type
    raise AuthenticationError(
litellm.exceptions.AuthenticationError: litellm.AuthenticationError: AuthenticationError: OpenAIException - Error code: 401 - {'error': {'message': 'Incorrect API key provided: b********************2d13. You can find your API key at https://platform.openai.com/account/api-keys.', 'type': 'invalid_request_error', 'param': None, 'code': 'invalid_api_key'}}
An error occurred while running the crew: Command '['uv', 'run', 'run_crew']' returned non-zero exit status 1.

Possible Solution
?
Additional context
Running the Crew
Using CPython 3.11.10 interpreter at: /anaconda/envs/crewai311/bin/python
Creating virtual environment at: .venv
Built py-course @ file:///mnt/batch/tasks/shared/LS_root/mounts/clusters/rashid-cpu/code/Users/81737/Projects/AIAgents/crewAI/py_course
░░░░░░░░░░░░░░░░░░░░ [0/218] Installing wheels...                                                                                warning: Failed to hardlink files; falling back to full copy. This may lead to degraded performance.
If the cache and target directories are on different filesystems, hardlinking may not be supported.
If this is intentional, set export UV_LINK_MODE=copy or use --link-mode=copy to suppress this warning.
Installed 218 packages in 4m 24s

Bro, cna you stop pushing updates every 5 hours? I cannot debug it

Hmm, I am curious, how do I push the updates like that??

Crewai calls llm based on litellm. You can first check whether your token format can be used normally in litellm.

Thanks for the tip. Any hints on how I could do that?
Note that I even have those llm complants if I run crewai using your example  in https://docs.crewai.com/quickstart:
Resolved 224 packages in 1ms
Audited 218 packages in 14ms
(crewai311) azureuser@compute-cpu:~/cloudfiles/code/Users/8xxxxx/Projects/AIAgents/crewAI/py_course$ crewai run
Running the Crew
Agent: AI LLMs Senior Data Researcher
Task: Conduct a thorough research about AI LLMs Make sure you find any interesting and relevant information given the current year is 2024.
2024-10-25 13:06:36,290 -<PHONE_NUMBER>15616 - llm.py-llm:161 - ERROR: LiteLLM call failed: litellm.AuthenticationError: AuthenticationError: OpenAIException - Error code: 401 - {'error': {'message': 'Incorrect API key provided: bbac2b33********************2d13. You can find your API key at https://platform.openai.com/account/api-keys.', 'type': 'invalid_request_error', 'param': None, 'code': 'invalid_api_key'}}
Agent: AI LLMs Senior Data Researcher
Task: Conduct a thorough research about AI LLMs Make sure you find any interesting and relevant information given the current year is 2024.
2024-10-25 13:06:36,355 -<PHONE_NUMBER>15616 - llm.py-llm:161 - ERROR: LiteLLM call failed: litellm.AuthenticationError: AuthenticationError: OpenAIException - Error code: 401 - {'error': {'message': 'Incorrect API key provided: bbac2b33********************2d13. You can find your API key at https://platform.openai.com/account/api-keys.', 'type': 'invalid_request_error', 'param': None, 'code': 'invalid_api_key'}}
My API key (AZURE_OPENAI_API_KEY) I use regularly in my many other (non-crewai) projects just fine. I do not work with OpenAPI, as it is not permitted in my organization due to security reasons.
So, how to fix this problem?
Please also note that I did run 'crew install' just before this output, as I have replaced my yaml files, and both main.py and crew.py  to match the crew original ones I was getting when I had created a new crew project.

#1386

from crewai import LLM

llm = LLM(
              model = "<model>",
              base_url = "<url>"
              api_version = "<version>",
              api_key = "<key>",
              azure=True,
)

Does this work for you?

I am not sure where or how to use your recipe.                                                                                I do work with yaml files for agents and tasks, and two steering files,  main.py and crew.py.  My main.py contains these lines:  #!/usr/bin/env python
import sys
from py_course.crew import PyCourseCrew
This main file is intended to be a way for you to run your
crew locally, so refrain from adding unnecessary logic into this file.
Replace with inputs you want to test with, it will automatically
interpolate any tasks and agents information
def run():
"""
Run the crew.
"""
inputs = {
'topic': 'AI LLMs'
}
PyCourseCrew().crew().kickoff(inputs=inputs)
def train():
"""
Train the crew for a given number of iterations.
"""
inputs = {
"topic": "AI LLMs"
}
try:
PyCourseCrew().crew().train(n_iterations=int(sys.argv[1]), filename=sys.argv[2], inputs=inputs)
except Exception as e:
    raise Exception(f"An error occurred while training the crew: {e}")

Your posting, I guess, related to llm settings, but how that settings fit into the latest https://docs.crewai.com/installation framework?
Am I missing something important?

Any ideas or hints?

In crew.py, the above can be passed as parameters to llm.

Hi @ulrmehdi
When you select Other > 5 > 13 it should ask you to enter a Key name which you should enter AZURE_OPENAI_KEY.

Hi, thanks, but I know it and used it to set up exactly this way. I just need a working example of the main.py which would incorporate two agents and, using litellm, would allow me build my project/process. I did set up yaml files for ageints and tasks, I just need to coordinate using them in a proper way with litellm, or from my Azure OpeAI Chat gpt-4o-mini  deployment. Also, as I look at the CrewAI examples, the poetry system is used to  manage LLMs, is it necessarily need to be poetry? I am reluctant to bring up too many extra frameworks  to complicate a project.  Thanks!

you can close

I have figured out everything related to this problem, and my project solution works as expected.

@theCyberTech , how to define the parameters for llm , i tried having decoding_method as sampling , but getting errors , when i define top_k,top_p?


Improve comments for memory and stream API usage

To prevent further error like #5004

Jenkins, test this please

Jenkins CI test (for commit 61578b302afad7d3da96557acc570edfdbeca237, target branch master) succeeded!


docs: set site_url to fix broken 404 page on RTD

Summary of Changes
The 404 page was previously not properly rendered on Read the Docs (RTD). This PR overrides the build commands of RTD. While this makes the 404 page work properly, it also removes the RTD flyout to select a version. For now, however, we deem the 404 page as more essential.
Once https://github.com/readthedocs/readthedocs.org/issues/8529 is done, we can use the default build again to make everything work as expected.

:tada: This PR is included in version 0.1.0 :tada:
The release is available on:

v0.1.0
GitHub release

Your semantic-release bot :package::rocket:


Fix the birthday format bug on some Android devices

The app crashed on my Android phone with European birth date format in some of my contacts.

what exactly does this change? could you add an comment saying
// handle european '2012-12-01' -> '2012-12-01'

with example strings for the scenario you encountered.

The application has crashed once it met contact with the birthdate in format '26.02.1969'. As I understand the code only handles the date in the US format. Unfortunately, my fix to the code is not 100% complete since it still crashed on some devices.
Here is the screenshot of the error that I've got on one of the devices. I think it's still connected with the date format and string handling.

seems related to the loadContactsFrom function at https://github.com/rt2zz/react-native-contacts/blob/master/android/src/main/java/com/rt2zz/reactnativecontacts/ContactsProvider.java#L263
could read the function and see if it's erroring out there? I'll add your international date format to the test app.

I don't you can skip if it fails, you could probably wrap in a try catch and handle the error. I'll be looking into this issue after adding an example to the project.


Commenting on the PR with the workflow run that closed the PR

Current dependencies on/for this PR:

main

PR #1568   👈

This comment was auto-generated by Graphite.


Add stacking to images

Per our discussion on Discord, this PR allows images to be stacked by extending the ImageColumn.
I added all the additional methods at the end of ImageColumn to make it easier to review, but if you prefer to change the order let me know.
As for areas for improvement and future ideas:

You will also see that I'm using the existing logic to only display images that return a path and then I add that to the $imageCount which I then use to calculate the remaining images. This works, however, if one or more images within the set limit() don't have an image, then the column could potentially not "fill up" the column with other available images.

In other words, if the limit is set to 4, and say there are 8 potential users.avatar, if the users 3 & 4 dont have avatars, then the stack will only show 2 images and then it will say +6 as the remaining. This is correct so it's not a bug, BUT ideally, we would continue to look through the remaining 4 images to see if there were 2 additional images so that we can show 4 images in the column.
Not sure how big of a deal this is, but I didn't want to hold back on this initial PR to figure it out.

It might be nice to be able to add a z-index to the images on hover so they come to the front.
It might also be neat to be able hover over the remaining count to show a window of the remaining images plus a field like name
Right now when you hover over the row the row has it hover state color. The ring-color doesn't update to match this unfortunately. We'd have to add tailwind's group to the row class to enable this, but not sure if you want to do that or not.

Alright, let me know what changes need to be made!

I'm seeing an error with SpatieMediaLibraryImageColumn. Do I need to update that class to include the $image = null argument? Or is there a better way to fix that? Would this be a breaking change for other packages that extend the ImageColumn?

I updated the logic for pending feature 1 to now filter images without paths so it will now show the available images up to limit, assuming they exist.

I need to rework this a bit. Just realized I've only been working with square pictures and the css is going to stretch things on non square pictures.

Ok fixed the cropping. However, I'm unsure why there is/was a wrapping div with overflow-hidden. I don't think that object-cover/object-center require the wrapping div do they? Maybe it's a fallback for browser compatibility?

Here's some initial feedback from me:

This should target 3.x. I really do not want to have to merge all of these changes in by hand when the time comes, and also v3 includes much better handling of column relationships and JSON (retrieving column values from nested relationships etc), so it should provide a better baseline.
We don't need separator(), we should support a JSON array of image paths by default, and then optionally a relationship. The first example in the docs should be with a JSON array, relationship support can be implied from the other examples / the existing "Column Relationships" docs.
There should only be 1 call to getImages() in the view, so the logic isn\t executed more than once. Preferably, we return the paths directly from that method, so we don't need getImagesWithPath().
Support will need to be added to the SpatieMediaLibraryImageColumn so that it is able to return more than one image.

That all sounds good and I'll work on those changes for v3. However, since there's no ETA on v3, and I already had a functioning stacked image column plug-in ready to go, are you opposed to me just releasing that now to benefit the community. Might also help those that won't be able update to v3 right away.

You can do whatever you wish - I just don't want to have to maintain it across two versions

@danharrin Here's the next update per your comments:

I've reworked the code and the docs as you suggested regarding supporting a JSON array by default and removing separator(). Relationships work as well: ImageColumn::make('images.path')
I've fixed the multiple calls to getImages()
I've merged support for defaultImageUrl(). This works really nicely in that if you are working with multiple images and a model doesn't have any images at all, it'll can show this default image.
Regarding not stacking images if stacked() isn't used, I've update the blade conditional to check if there are multiple images or just a single image instead of whether or not stacked() is used. If it's an array then it will display multiple images with a space-x-1 gap between them. If you add stacked() then they will stack on top with a default of -space-x-1. You can further customize this by using overlap() to tell how much overlap you want.
The only thing not included in PR is support for SpatieMediaLibraryImageColumn. I thought it'd be better to get this part nailed down and then apply this to Spatie. After you give your feedback on these changes I'll get started on that.

Thanks!


Correcting Layout for Sponsor section

Issue #641
@mariobehling @championswimmer Please review and merge
Before

After

Current coverage is 46.77% (diff: 100%)

Merging #645 into development will increase coverage by 0.56%

@@           development       #645   diff @@
=============================================
  Files                6          6
  Lines              580        573     -7
  Methods             58         58
  Messages             0          0
  Branches            98         93     -5
=============================================
  Hits               268        268
+ Misses             312        305     -7
  Partials             0          0

Powered by Codecov. Last update cf74c27...62bcddb

if we are using same sizes for all, can we add a header for each section (Platinum, Gold, like that) of sponsors ?
It should be easily visible (not tooltips) which tier a sponsor belongs to. They pay money for that only.

@championswimmer Tooltip is only to avoid confusing UI. We can add names too by removing tooltip later. Please merge this.


How to resize image slider

HI,
Sorry if this has been covered, can't seem to find the answer.  In the demo version the size of each image is 774px, but I can't seem to find where I can adjust the sizing of the image?
Thank you in advance for your help and thanks for a great responsive slider.

Hello,
Slippry uses whatever content it gets, it won't resize the image sizes. The only thing it does is resize the slider responsively according to the image proportions.
Just upload the image in a size big enough for the biggest screens and don't worry. If you want to do some next level responsive images you may want to take a look at using http://caniuse.com/#feat=srcset within Slippry.
All the best,
I hope this helps!


[2.7.0] Tilesets of by one pixel after resizing

The red, yellow and green horizontal lines belong to adjacent tiles in the tileset.  I can stop resizing at a point where the glitch is present or at a point where it is not.
This happens to every tile. I'm just showing you the ones where it's easy to see.
Some rounding error maybe?

Far more likely the same issue as you get with texture atlases when frames are packed too tightly.
How are you scaling the game though? because just changing the browser window won't do that automatically.

this.game.scale.scaleMode = Phaser.ScaleManager.SHOW_ALL;
this.game.scale.setResizeCallback(this.reflow,this);

this.reflow() keeps the same native width and adapts the height to match the window aspect ratio like this:
this.game.scale.setGameSize(this.game.width,this.game.width*window.screen.height/window.screen.width);

This is the tileset image:

There is no padding as you can see, though it never caused any bleeding before.

That's because it never rendered it with WebGL before! What do you reckon @pjbaron ?

I have seen this effect when developing the Beam renderer for Lazer but only when using point sprites (GL_POINT with a texture applied).  It is visible in the 'point tile' demo for instance.  I was not able to track it down in that, but will give it another go for this new tile renderer (which uses GL_TRIANGLE_STRIP so I am surprised to encounter it again).
@noidexe I have grabbed a copy of your tileset to experiment with from your message, can you please confirm that your tilesize is 42x42 (e.g. you didn't share a rescaled or modified version of your original tiles)?

@pjbaron It is indeed 42x42. Here's the exact file that is on master right now https://www.dropbox.com/s/lk7v3cbwvil4q61/bgtiles.png?dl=0

Hi @noidexe I have just tried to recreate this in a very simple example but can't get the lines to appear.
Could you please try the attached example (it's in the standard Phaser "examples" format, though I used your code mentioned above to resize dynamically as the window changes size) and let me know if you are able to cause it to happen?
cheers,
Pete
tiles bug test.zip

This is surely a result of texture bleeding, it's the exact same symptoms: http://rotorz.com/tilesystem/guide?ref=e3d107d9-e4cc-4c08-aa2b-2b555abac30a

Could be, but strange that I cannot recreate in a simple example.

Rich found the magic numbers, in my example use:
function reflow() {
game.scale.setGameSize(800, 334.883);
}
generates lines on my system.
I'll play around with rounding and the shader but it probably is bleeding.

Ok, so I tried both round and floor on source texture (UV) coordinates but neither fixed the lines.    Let me know if it works for you!

This is using freshly a freshly built phaser.js from the latest dev and the lines stay no matter how I resize the window. Sure enough disabling antialias fixes it here and on my game.
I found this before creating the issue, while I googling to see if there was some error on how I created my image assets. Not sure if it'll be of any help.

Thanks for the reference, I did try applying the half-pixel correction they talk about there however with this code:
var uvl = (t.sx + 0.5) * iTextureWide;
var uvt = (t.sy + 0.5) * iTextureHigh;
We get this output:

As you can see, it fixes the lines on top, but adds lines underneath instead.

Ok, that appears to work for this example, but for others with flipped tiles it causes problems (vertical lines at the edges when the tile is horizontally flipped).
I need to experiment with the code, applying the correction at the last stage is not the best way to handle this, it should go into the glBatch buffer much earlier in the process.
Thanks for the link!

Ok, that change is now in dev branch.  Please report any other effects it might have - I've skimmed through the example projects and they look ok.

The visual glith is gone, but the game freezes when I try to switch to a different game state. It only happens when switching from the game state with the tilemap to any other.

I believe Rich is currently working in the dev branch.  Please raise a new issue for this new bug if it continues after today.  It's great to hear the image is clean now, thanks for your help in finding the cause of that problem!

Yeah I'm changing things like mad at the moment. Give it time to settle down before trying again.

Yeah I imagined it could've been that. I cherry picked your last commit(@pjbaron) ignoring the three added by Rich and everything worked fine. Thanks for the amazing work you're doing :)


Update DG Use Case

Resolves https://github.com/AY2324S2-CS2103T-T17-3/tp/issues/42

Might want to follow the following structure for each use case:

System
Use case
Actor
MSS
Extensions

For some use cases, some sections are currently missing.
Eg, UC01, Actor section is missing. UC03, System section is missing.
Other than that, LGTM!

@jjchee77 thanks, fixed

Might wanna add horizontal lines to separate each use case for better readability.
Sorry for not pointing out that earlier!
I think <br/> works.

LGTM!


[doc] Development stages: "Active" stage?

https://docs.opentitan.org/doc/project/development_stages/#life-stages mentions an "Active" stage.
"The final life stage is Signed Off. At this point, a design is frozen and not expected to be updated. There are exceptions if post-signoff bugs are found, in which case the stage returns to Active and the version number is not updated."
However, there's no such stage mentioned in the document. Should "Active" be replaced with "Development" (L1)?
@sjgitty

Yep, let me fix that, thanks


{Compute} Adopt track2 SDK, azure-mgmt-servicebus==6.0.0

Description

Here are main changes for Servicebus migration to track2:

LRO operations are renamed to begin_xxx_xxx, for example in track1, the name is delete; while in track2, the name is `begin_delete.
For generic update of LRO, set setter_name to begin_create_or_update.
In track2, SDK parameters are not flattened, so we need pass object parameter instead of flattened parameters to SDK.
In track2, use HttpResponseError instead of CloudError.
In track2, add the --config-name parameter for the migration operation . Its default value is $default.
Fix some tests due to changes in track2.
Run live tests and re-record tests.

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

@BigCat20196 great progress, thank you!

I run live test for this PR.
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=863247&view=results

@v-Ajnava Could you have a look at this PR? It upgrades Python SDK version.

The results look good. https://clitestresultstac.blob.core.windows.net/20210427-042651-649458/servicebus.report.parallel.html

hi @qwordy, what's status of this PR? seems CI passed

hi @qwordy, what's status of this PR? seems CI passed

Code owner review required. No response yet. We can merge it.

/azp run


New itertool: window

How about adding a sliding window itertool?
There are multiple implementations that trade off on things like memory consumption/speed/etc, but here's a version that's worked fine for me
from collections import deque

def window(seq, n=2):
    it = iter(seq)
    win = deque((next(it, None) for _ in xrange(n)), maxlen=n)
    yield win
    append = win.append
    for e in it:
        append(e)
        yield win

Fixed in #63. Thanks!