InPact AI

[somber girder]

wlc

[fringe cedar]

@somber girder You are now level 18! :confetti_ball:

[fair prairie]

is the trending_niches table supposed to be automatically created... because the schema for it is not provided

[fringe cedar]

@fair prairie You are now level 3! :confetti_ball:

[somber girder]

The sql.txt file has been updated. As part of this update, some tables were removed because they were causing issues during execution. The problems occurred due to the tables not being created in the correct order, which causes for table not found error

you can create table your own

[turbid edge]

yes, the tables are not being created in the correct order. ......the tables need to be arranged based on the errors. After facing many errors, my setup finally worked as well

[fringe cedar]

@turbid edge You are now level 9! :confetti_ball:

[astral oriole]

@bold goblet why isnt inpactAI hosted on the web yet?

we can atleast host it and let the users join the waitlist , same as Devr.ai

[somber girder]

hey @astral oriole as the inpactAi is not an active project or not actively maintaining and have a lot of bugs to fix. So, it results, not hosted

[astral oriole]

Yeahh, but why wasnt this project taken up for gsoc25. the idea is really great

[somber girder]

sorry, not aware of that, don't know

[astral oriole]

@bold goblet ??

[fair prairie]

Thnx.. it worked

also I found some more tables that were not getting created during the onboarding

[somber girder]

wlc

[somber girder]

yes

[fair prairie]

essentially none of the tables were getting created for the entire onboarding

[somber girder]

hmm

initially that was inside the sql.txt file but later on they were got removed

[fair prairie]

so can I add it as an issue then?

[somber girder]

no, bcz there were bunch of them so adding them cause the same issue "table not found"

[fair prairie]

but wouldn't providing them in sql.txt of the file and then asking to copy paste them on sql editor in supabase....wouldn't it help for local setup?

[somber girder]

then you need to test each and every table and then add them in order so that other don't face this error

[fair prairie]

oh

[turbid edge]

Hi @bold goblet
I’ve created a PR for the UI changes . PR Link : https://github.com/AOSSIE-Org/InPactAI/pull/287

Kindly review it and let me know if any improvements are needed

[astral oriole]

@worldly zinc InPactAI wasn’t selected for GSoC ’25. It’s a really strong idea, though it seems like it still has quite a few bugs to work through. Would it make sense to aim for GSoC ’26 instead? I wanted to check if the project is still active or if you’re planning to continue improving it in the future.

[worldly zinc]

@bold goblet , could you comment on this? I think we did have a contributor selected for GSoC in 2025, didn't we? Or am I misremembering?

[brisk sapphire]

@worldly zinc From my opinion there is a contributor name @supple tartan
As i had contributed before in this project i know

[supple tartan]

@worldly zinc sent you a dm

[worldly zinc]

I haven't received it. But I DMed you now.

[unique sand]

I am facing an issue with login and sign-up. If anyone else is facing the same problem, please confirm. If not, kindly guide me on what the issue might be from my side and how I can fix it.

[brisk sapphire]

i think you need to confirm your email on the supabase first

[somber girder]

bcz of your email is not verified on your Supa base

You need to verify your email address during signup. You should have received a confirmation email from Supabase—please open that email and confirm your account to proceed.

or go to Supabase dashboard and authentication -> Providers -> Email

and turn that off Confirm Email

got it, @unique sand

[unique sand]

thank you @somber girder now it's working.

[somber girder]

wlc ❤️

[torn quarry]

@bold goblet I have changed the whole UI of InPactAI Landingpage.
I have made a PR, I have attached the screenshots for reference to look. Please go through it and let me know if I can do some more changes.

https://github.com/AOSSIE-Org/InPactAI/pull/294

[torn quarry]

@worldly zinc If this page is actively accepting prs, please have a look into this sir..
I have attached the SS of the website.

[unique sand]

@worldly zinc i have solved this issue https://github.com/AOSSIE-Org/InPactAI/issues/140 and it's my PR https://github.com/AOSSIE-Org/InPactAI/pull/295

please merge merge my PR

[torn quarry]

Hi there, I am seeing there are lots of problems in the InPactAI some are very much generic and some PRs that resolves the issue but not merged..

[somber girder]

yeah, mentor for #1345044736515379210 is not active

you can share SS here

we can help you solving the issues that you are facing

[turbid edge]

Hi mentors,
contributors are actively creating PRs for the project.
I’ve also raised a PR and shared the link above.
Whenever you get time, could you please review it and guide me with your feedback?
Thank you!

[torn quarry]

Actually I have made some changes in the backend, like . prefixes of import statements..
Is it allowed to do so??

[somber girder]

where did you made changes, could you please share SS or PR link here

[torn quarry]

I saw many files had . prefix in importing, eg from .db.db import ____

It is not error but looks very awkward/unorganised.

[fringe cedar]

@torn quarry You are now level 2! :confetti_ball:

[somber girder]

\This is using Python’s relative import system. The . prefix means “from the current package,” so imports like from .db.db import … are intentional and valid.

Relative imports help keep the package self-contained, avoid name collisions with external modules, and make the codebase easier to move or reuse without breaking internal imports.

While it can look a bit awkward—especially when names are repeated—it’s not an error or a sign of broken structure. It’s mainly a trade-off for package safety and modularity.

That said, the structure can always be refined later to reduce deep nesting and improve readability once the architecture stabilizes.

[worldly zinc]

Hi everyone. For various reasons, we won't be able to accept any GSoC proposals for further work on InpactAI this year. However, @supple tartan , who worked on this project last year told me that he is interested in maintaining it and developing it further, even though he won't be able to mentor in GSoC.

But all contributions made to this projects will count and will continue to count in our evaluation of your GSoC proposals.

@supple tartan , please remind me your github username, so that I can give you access to maintain the repo. And, once you have access, please merge your work and please review all the pending PRs.

(cc: @bold goblet )

[fringe cedar]

@worldly zinc You are now level 43! :confetti_ball:

[worldly zinc]

@supple tartan , you have access now. Please go ahead and start maintaining the repo. There are really many pending PRs.

[supple tartan]

Acknowledged @worldly zinc ...will look onto the current project status and will start maintaining it soon

[prime meteor]

so @supple tartan all my contributions will count for other project's right??

[supple tartan]

@prime meteor i belive the organization doesn't explicitly checks a "count" of contributions...but yes your activity inside the organization will be acknowledged

[prime meteor]

That is reassuring

[fringe cedar]

@prime meteor You are now level 3! :confetti_ball:

[shell grotto]

Hi @everyone! I’m a 2nd-year CSE student and I've been working on a secure backend for InPactAI using FastAPI. I’ve recently implemented a robust JWT authentication system with detailed user roles and metadata. My goal is to ensure the platform is both scalable and highly secure for all users. I'd love to discuss the current backend roadmap and see where I can contribute further. Looking forward to connecting with the team!

[modern junco]

Great work on the JWT system. Role-based metadata design is important for scaling securely. I’d be happy to collaborate or help with backend improvements if needed.

[modern junco]

@supple tartan Sir, could you please review this PR when you’re available?
https://github.com/AOSSIE-Org/InPactAI/pull/305

[brisk sapphire]

seems good !!

[modern junco]

Thanks sir , @brisk sapphire

[prime lion]

Yeah looks good to me too

[past adder]

Hey everyone!👋 Hope you all are contributing to this interesting project. Out of my interest and I just contributed a PR.
That is:
Added pagination to all the backend list endpoints so they don’t choke when the data grows. 📈
Basically: added skip and limit parameters, capped the limit at 100, and made sure the response includes the count and metadata.
Took a couple of tweaks after the bot review (fixed the ORDER BY and optimized the count query too).

If you're working on APIs that deal with lists, this pattern might be useful:
https://github.com/AOSSIE-Org/InPactAI/pull/308

Please check it out and review your thoughts. Even couple of words is okay........😇 😇

[fringe cedar]

@past adder You are now level 3! :confetti_ball:

[merry furnace]

Hi guys I could use some help. How can i know what's done and what's remaining in each project? (e.g landing page has been finalized but seo remains so i can contribute that)

[narrow nymph]

@supple tartan
Please check this out

as discussed here
:#announcements message
https://github.com/AOSSIE-Org/InPactAI/pull/304