Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat: platform agnostic analyzer library #98

Open
wants to merge 102 commits into
base: main
Choose a base branch
from
Open

Conversation

amindadgar
Copy link
Member

Refactored the whole analyzer to be platform agnostic and be a library

+ Added different heatmaps analytics (for now the replier is implemented)
+ updated utils, removing unnecessary ones and updating method names.
+ added schema for heatmaps data.
+ updated the previous heatmaps to a heatmaps_old name so we could still run analyzer using that. (depricated)
+ commented the `RnDAOAnalyzer` in __init__ but will get it back later with a better name.
moving neo4j utils into its right directory.
+ added author_id filtering too.
it supports both type of emitter and receiver of reply
using the analytics_hourly for all vector analytics.
+ couple of small updates on analyzer config custom analytics.
+ updated heatmaps utils class
- the raw analytics of heatmaps is still todo.
and aligning it with its test case.
the analytics should've been giving each engaged user id.
+ fixed: in raw analytics the test cases had some problem (were aligning other users activity in output)
+ fixed: the ActivityType typo fixed.
HeatMapModel is deprecated, will be removed in future.
+ also, updated raw analytics to output a dict rather than python object, so we could later save them in db easily.
+ in order to keep the changes at minimum at possible we're using the previous heatmaps output data schema.
+ but still we're platform agnostic.
+ we needed to update raw data in old test cases to the new format.
+ ignoring the self-interactions now.
+ updated discord analyzer configurations based on discussions.
+ removing the heatmaps_old as was no longer needed.
this is because for now we know the analyzer won't work so we need to skip a couple of test cases.
amindadgar and others added 28 commits July 1, 2024 11:07
this will help us to run the CI faster but just for one test case, have to bring docker-entrypoint.sh back to default version after
…form-agnositc

Feat/92 Update analyzer to be platform agnostic!
…form-agnostic

Feat/77 graph analytics platform agnostic
Now the analyzer will accept `platform_id`, `resources`, `period`, `action`, and `window` as input
the function setup_analyzer was deleted and no longer needed.
As we're moving the analyzer to be a library, we're trying to wrap up all the codes in one package.
on test cases rabbitMQ is becoming down and it is always making some test cases to fail.
the AMQP connection is being closed for no specific reason.
It isn't needed anymore as we're not producing mock graphs.
In first try we tried commenting it out but still it was producing lint errors, so we're removing it as it is also no longer needed.
Copy link

coderabbitai bot commented Jul 4, 2024

Important

Review skipped

More than 25% of the files skipped due to max files limit. The review is being skipped to prevent a low-quality review.

93 files out of 238 files are above the max files limit of 50. Please upgrade to Pro plan to get higher limits.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@amindadgar amindadgar requested a review from cyri113 July 4, 2024 09:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants