Consulo – multi-language ide. Project was started in year 2013 by forking IDEA Community Edition.

Main goal – to create an open IDE, where you don’t need to select an IDE for different languages. Instead, provide a standard for language implementation inside the IDE.

If you can’t describe the issue, you can use our forum, or you can read the contributing guide and report the issue at GitHub

JVM	Github Actions
Java 21
Java 22
Java 23
Java 24

First of all, you need these tools:

• Maven 3.9+
• JDK 21+

Then execute from command line:

mvn package

If you want run Consulo from repository

• as a desktop application

   mvn install
  
   mvn consulo:run-desktop-awt-fork -pl consulo:consulo-sandbox-desktop-awt

• as a web application

  first need build web sandbox

  mvn package -am -pl consulo:consulo-sandbox-web
  

  then need start code server (since we used gwt as frontend)

  cd modules/web/web-ui-impl-client
  
  mvn -am vaadin:run-codeserver

  and start web server

  cd modules/web/web-bootstrap
  
  mvn -am jetty:run

• Profiler API link
• Diagram support link
• Web IDE link
• SWT UI link

• Contributing Guide
• Download
• Issues
• Forum
• Discord Channel

YourKit supports open source projects with innovative and intelligent tools for monitoring and profiling Java and .NET applications.

YourKit is the creator of YourKit Java Profiler, YourKit .NET Profiler, and YourKit YouMonitor.

Consulo – multi-language ide. Project was started in year 2013 by forking IDEA Community Edition.

Main goal – to create an open IDE, where you don’t need to select an IDE for different languages. Instead, provide a standard for language implementation inside the IDE.

If you can’t describe the issue, you can use our forum, or you can read the contributing guide and report the issue at GitHub

JVM	Github Actions
Java 21
Java 22
Java 23
Java 24

First of all, you need these tools:

• Maven 3.9+
• JDK 21+

Then execute from command line:

mvn package

If you want run Consulo from repository

• as a desktop application

   mvn install
  
   mvn consulo:run-desktop-awt-fork -pl consulo:consulo-sandbox-desktop-awt

• as a web application

  first need build web sandbox

  mvn package -am -pl consulo:consulo-sandbox-web
  

  then need start code server (since we used gwt as frontend)

  cd modules/web/web-ui-impl-client
  
  mvn -am vaadin:run-codeserver

  and start web server

  cd modules/web/web-bootstrap
  
  mvn -am jetty:run

• Profiler API link
• Diagram support link
• Web IDE link
• SWT UI link

• Contributing Guide
• Download
• Issues
• Forum
• Discord Channel

YourKit supports open source projects with innovative and intelligent tools for monitoring and profiling Java and .NET applications.

YourKit is the creator of YourKit Java Profiler, YourKit .NET Profiler, and YourKit YouMonitor.

New Relic Java agent instrumentation extension for Spring Cloud Gateway.

This use this instrumentation.

1. Download the latest release.
2. In the New Relic Java Agent directory (directory containing newrelic.jar), create a directory named extensions if it doe not already exist.
3. Copy the jars into the extensions directory.

If you make changes to the instrumentation code and need to build the instrumentation jars, follow these steps

1. Set environment variable NEW_RELIC_EXTENSIONS_DIR. Its value should be the directory where you want to build the jars (i.e. the extensions directory of the Java Agent).
2. Build one or all of the jars.
   a. To build one jar, run the command: gradlew moduleName:clean moduleName:install
   b. To build all jars, run the command: gradlew clean install
3. Restart the application

After deployment, you should be able to see parts of your Apache Sling flows showing up in transaction traces.

New Relic has open-sourced this project. This project is provided AS-IS WITHOUT WARRANTY OR DEDICATED SUPPORT. Issues and contributions should be reported to the project here on GitHub.

We encourage you to bring your experiences and questions to the Explorers Hub where our community members collaborate on solutions and new ideas.

We encourage your contributions to improve Salesforce Commerce Cloud for New Relic Browser! Keep in mind when you submit your pull request, you’ll need to sign the CLA via the click-through using CLA-Assistant. You only have to sign the CLA one time per project. If you have any questions, or to execute our corporate CLA, required if your contribution is on behalf of a company, please drop us an email at opensource@newrelic.com.

A note about vulnerabilities

As noted in our security policy, New Relic is committed to the privacy and security of our customers and their data. We believe that providing coordinated disclosure by security researchers and engaging with the security community are important means to achieve our security goals.

If you believe you have found a security vulnerability in this project or any of New Relic’s products or websites, we welcome and greatly appreciate you reporting it to New Relic through HackerOne.

newrelic-java-spring-cloud-gateway is licensed under the Apache 2.0 License.

This repository provides a web-based tool to view dumped SMS and call data from Metasploit in a visually appealing chat-style format. The tool allows users to upload their dumped files securely without storing them in a database.

• Parses dumped SMS and call data from Metasploit.
• Organizes the data in a chat-like interface for easy visualization.
• Supports various message and call attributes such as sender, receiver, timestamp, and message content.
• Customizable styling options to suit your preferences.

1. Clone this repository:

git clone https://github.com/ganiyevuz/metasploit-sms-call-dump-viewer.git
cd metasploit-sms-call-dump-viewer

2. Install the required dependencies:

pip install -r requirements.txt

3. Start the web server:

python manage.py runserver

4. Open your web browser and navigate to http://localhost:8000.

5. Click on the “Upload” button and select your dumped SMS and call data file generated from Metasploit.

6. The tool will parse the data and display it in a chat-style format directly in your browser.

You can customize the appearance of the chat interface by modifying the CSS file (styles.css). Feel free to experiment with different colors, fonts, or layouts to match your preferences.

The tool does not store the uploaded files in a database, ensuring the security and privacy of your data. However, exercise caution while handling sensitive information and ensure that you are complying with relevant privacy laws and regulations.

Please note that using Metasploit or any hacking tools without proper authorization is illegal and unethical. This repository is intended for educational and research purposes only. Always ensure that you have the necessary permissions and abide by the applicable laws and regulations.

This project is licensed under the MIT License.

This repository contains Peripheral Access Crates (PACs) for Nordic’s nRF series of Cortex-M microcontrollers.

All these crates are automatically generated using svd2rust.

For a more user-friendly interface to the peripherals, the nrf-hal crates might be more appropriate.

Please refer to the changelog to see what changed in the last releases.

Every nRF chip has its own PAC, listed below:

Crate	Docs	crates.io	target
nrf51-pac			thumbv6m-none-eabi
nrf52805-pac			thumbv7em-none-eabi
nrf52810-pac			thumbv7em-none-eabi
nrf52811-pac			thumbv7em-none-eabi
nrf52820-pac			thumbv7em-none-eabi
nrf52832-pac			thumbv7em-none-eabihf
nrf52833-pac			thumbv7em-none-eabihf
nrf52840-pac			thumbv7em-none-eabihf
nrf5340-app-pac			thumbv8m.main-none-eabihf
nrf5340-net-pac			thumbv8m.main-none-eabihf
nrf9160-pac			thumbv8m.main-none-eabihf
nrf9120-pac			thumbv8m.main-none-eabihf

* These devices do not have a separate development kit and share the NRF52 DK

** As of 2024-6-28, the Product Specification and the DK Reference Guide have not been published for the nRF9151.

This repository contains Peripheral Access Crates (PACs) for Nordic’s nRF series of Cortex-M microcontrollers.

All these crates are automatically generated using svd2rust.

For a more user-friendly interface to the peripherals, the nrf-hal crates might be more appropriate.

Please refer to the changelog to see what changed in the last releases.

Every nRF chip has its own PAC, listed below:

Crate	Docs	crates.io	target
nrf51-pac			thumbv6m-none-eabi
nrf52805-pac			thumbv7em-none-eabi
nrf52810-pac			thumbv7em-none-eabi
nrf52811-pac			thumbv7em-none-eabi
nrf52820-pac			thumbv7em-none-eabi
nrf52832-pac			thumbv7em-none-eabihf
nrf52833-pac			thumbv7em-none-eabihf
nrf52840-pac			thumbv7em-none-eabihf
nrf5340-app-pac			thumbv8m.main-none-eabihf
nrf5340-net-pac			thumbv8m.main-none-eabihf
nrf9160-pac			thumbv8m.main-none-eabihf
nrf9120-pac			thumbv8m.main-none-eabihf

* These devices do not have a separate development kit and share the NRF52 DK

** As of 2024-6-28, the Product Specification and the DK Reference Guide have not been published for the nRF9151.

Tools for sonifying astronomical data.

This package is currently in the very beginning stages and is under active development to include sonification of time series data, specifically light curves.

Install instructions: https://astronify.readthedocs.io/en/latest/astronify/install.html

Tutorials: https://astronify.readthedocs.io/en/latest/astronify/tutorials.html

If you are a maintainer of the code, refer to the developer documentation (DEVELOPER_DOC.rst file) for guidelines on how to release a new version.

We love contributions! Astronify is open source, built on open source, and we’d love to have you hang out in our community.

Imposter syndrome disclaimer: We want your help. No, really.

There may be a little voice inside your head that is telling you that you’re not ready to be an open source contributor; that your skills aren’t nearly good enough to contribute. What could you possibly offer a project like this one?

We assure you – the little voice in your head is wrong. If you can write code at all, you can contribute code to open source. Contributing to open source projects is a fantastic way to advance one’s coding skills. Writing perfect code isn’t the measure of a good developer (that would disqualify all of us!); it’s trying to create something, making mistakes, and learning from those mistakes. That’s how we all improve, and we are happy to help others learn.

Being an open source contributor doesn’t just mean writing code either. You can help out by writing documentation, tests, or even giving feedback about the project (and yes – that includes giving feedback about the contribution process). Some of these contributions may be the most valuable to the project as a whole, because you’re coming to the project with fresh eyes, so you can see the errors and assumptions that seasoned contributors have glossed over.

Note: This disclaimer was originally written by Adrienne Lowe for a PyCon talk, and was adapted by Astronify based on its use in the README file for the MetPy project.

This project is Copyright (c) Clara Brasseur, Scott Fleming, Jennifer Kotler, Kate Meredith and licensed under the terms of the BSD 3-Clause license. This package is based upon the Astropy package template which is licensed under the BSD 3-clause licence. See the licenses folder for more information.

Useful development environments for software projects.

1. Instruct guix pull to pull code from this channel in addition to the default Guix channel(s) by adding following snippet to your ~/.config/guix/channels.scm:

   (channel
     (name 'tassos-guix)
     (url
      "https://github.com/Tass0sm/guix-develop"))
       

2. Run guix pull. Then you can use the code from this repository by importing the correct modules.

Create a project directory with the following contents.

1. A normal haskell cabal project.
2. manifest.scm

The manifest.scm file looks like this.

(use-modules (tassos-guix develop)
             ...)

(define %source-dir
  (dirname (current-filename)))

(define ghc-graphdoc
  (package
    (name "ghc-graphdoc")
    (version "0.0.1")
    (source
     (local-file %source-dir
                 #:recursive? #t
                 #:select? (git-predicate %source-dir)))
    (build-system haskell-build-system)
    (inputs
     (list ghc-pandoc
           ghc-pandoc-types))
    (home-page "")
    (synopsis "")
    (description "")
    (license license:gpl3+)))

;; The new part:
(de->manifest
 (development-environment
  (package ghc-graphdoc)))

A development-environment extends the concept of a normal development profile for a package defined by package->development-manifest.

1. Activate the development environment profile.

   guix shell
       

2. In that profile, build the program like you would without Guix.

   cabal build
   cabal repl
       

   This lets cabal handle all of the haskell packages. This could change in the future.

1. Disable dependence on Guix packages.
2. Add extra packages into the development environment.
3. Enhance the development environment with extra add-ons which are parameterized by the rest of the development environment. Like an “lsp” add-on which adds the appropriate language server.

Task Manager Slack Command Bot is an innovative Slack bot developed using Python and the FastAPI framework. It empowers your team with seamless task management, code review, and collaboration capabilities, enhancing productivity and team dynamics. The bot integrates seamlessly with Slack’s API set through the Slack Python library, ensuring a smooth and efficient user experience.

Link – https://vimeo.com/849908919

• /do Command:

  • Triggered with /do command followed by a task name (single string).
  • Randomly selects a team member to do the mentioned task. Example – /do conduct-daily-standup.
  • Mention a specific member’s name after /do to assign the task precisely. Example – /do conduct-daily-standup @Will
  • Handles multiple member mentions by randomly picking one for equitable task distribution. Example – /do conduct-daily-standup @Will @Smith @Chris

• /git-review Command:

  • Triggered with /git-review command followed by a Git Pull Request (PR) link.
  • Randomly selects a team member to review the provided Git PR link. Example – /git-review YOUR_GIT_PR_URL
  • Mention a specific member’s name after /git-review to assign the review task precisely. Example – /git-review YOUR_GIT_PR_URL @Tom
  • Handles multiple member mentions by randomly picking one for equitable task distribution. Example – /git-review YOUR_GIT_PR_URL @Tom @Dick @Harry

• /inspect Command:

  • Highlight any valid URL in a Slack channel with the /inspect command.
  • Randomly assigns a team member to inspect the mentioned URL. /inspect YOUR_URL
  • Mention a specific member’s name after /inspect to assign the task precisely. Example – /inspect YOUR_URL @Bruce
  • Handles multiple member mentions by randomly picking one for equitable task distribution. Example – /inspect YOUR_URL @Bruce @Wayne @Joker
  • Most speculated use case: Randomly pick a team mate to take a look at a Slack conversation gaining momentum, adding a fun twist to collaboration.

We are committed to continually expanding the capabilities of the Task Manager Slack Command Bot. Future planned features include:

• Agile Story Pointing: Streamline sprint planning sessions with Agile story pointing, enabling efficient estimation of user stories.
• TBD

1. Clone this repository and navigate to the project directory.
2. Set up the virtual environment using Python’s virtualenv or your preferred method.
3. Install the required dependencies, including FastAPI and the Slack Python library.
4. Create a .env file in the project root directory and add your Slack token and signing secret. Make sure to keep this information secure and do not share it publicly.
5. Customize the bot’s behavior, appearance, and Slack API integration to align with your team’s preferences.
6. Launch the bot using FastAPI and deploy it on your chosen hosting service.
7. Configure your Slack workspace to interact with the Task Manager Slack Command Bot via its Slack API integration.

We welcome and encourage contributions to this open-source project. To contribute, please submit pull requests, suggest new features, or share your ideas to expand the capabilities of the Task Manager Slack Command Bot. Together, we can create a powerful and versatile tool to streamline your team’s workflow and boost productivity.

Let’s build the future of collaborative team experiences! Happy task managing, reviewing, inspecting, and planning! 🚀🔍📈