A linter that handle directives into go.mod.

Recommended.

linters:
  enable:
    - gomoddirectives

  settings:
    gomoddirectives:
      # Allow local `replace` directives.
      # Default: false
      replace-local: true
      
      # List of allowed `replace` directives.
      # Default: []
      replace-allow-list:
        - launchpad.net/gocheck
      
      # Allow to not explain why the version has been retracted in the `retract` directives.
      # Default: false
      retract-allow-no-explanation: true
      
      # Forbid the use of the `exclude` directives.
      # Default: false
      exclude-forbidden: true
  
      # Forbid the use of the `ignore` directives (go >= 1.25).
      # Default: false
      ignore-forbidden: true
  
      # Forbid the use of the `toolchain` directive.
      # Default: false
      toolchain-forbidden: true
  
      # Defines a pattern to validate `toolchain` directive.
      # Default: '' (no match)
      toolchain-pattern: 'go1\.22\.\d+$'
  
      # Forbid the use of the `tool` directives.
      # Default: false
      tool-forbidden: true
  
      # Forbid the use of the `godebug` directive.
      # Default: false
      go-debug-forbidden: true
  
      # Defines a pattern to validate `go` minimum version directive.
      # Default: '' (no match)
      go-version-pattern: '1\.\d+(\.0)?$'

gomoddirectives [flags]

Flags:
  -exclude
        Forbid the use of exclude directives
  -godebug
        Forbid the use of godebug directives
  -goversion string
        Pattern to validate go min version directive
  -h    Show this help.
  -ignore
        Forbid the use of ignore directives
  -list value
        List of allowed replace directives
  -local
        Allow local replace directives
  -retract-no-explanation
        Allow to use retract directives without explanation
  -tool
        Forbid the use of tool directives
  -toolchain
        Forbid the use of toolchain directive
  -toolchain-pattern string
        Pattern to validate toolchain directive

• Force explanation for retract directives.

module example.com/foo

go 1.22

require (
	github.com/ldez/grignotin v0.4.1
)

retract (
    v1.0.0 // Explanation
)

• Ban all replace directives.
• Allow only local replace directives.
• Allow only some replace directives.
• Detect duplicated replace directives.
• Detect identical replace directives.

module example.com/foo

go 1.22

require (
	github.com/ldez/grignotin v0.4.1
)

replace github.com/ldez/grignotin => ../grignotin/

• Ban all exclude directives.

module example.com/foo

go 1.22

require (
	github.com/ldez/grignotin v0.4.1
)

exclude (
    golang.org/x/crypto v1.4.5
    golang.org/x/text v1.6.7
)

• Ban all ignore directives.

module example.com/foo

go 1.25

require (
	github.com/ldez/grignotin v0.4.1
)

ignore (
    ./foo/bar/path
    foo/bar
)

• Ban all tool directives.

module example.com/foo

go 1.24

tool (
    example.com/module/cmd/a
    example.com/module/cmd/b
)

• Ban toolchain directive.
• Use a regular expression to constraint the Go minimum version.

module example.com/foo

go 1.22

toolchain go1.23.3

• Ban godebug directive.

module example.com/foo

go 1.22

godebug default=go1.21
godebug (
    panicnil=1
    asynctimerchan=0
)

• Use a regular expression to constraint the Go minimum version.

module example.com/foo

go 1.22.0

This project was bootstrapped with Create React App.

In the project directory, you can run:

Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.

The page will reload when you make changes.
You may also see any lint errors in the console.

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting

This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size

This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app

This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration

This section has moved here: https://facebook.github.io/create-react-app/docs/deployment

This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify

Los libros son una fuente de conocimiento que sin importar cuánto tiempo transcurra, siempre serán de gran utilidad para todos nosotros. Por ello, en este repositorio me he encargado de coleccionar varios libros en formato PDF sobre aquellas tecnologías o áreas de interés para que así mejores tus habilidades como programador o aprendas sobre ese tema que tantos ánimos has tenido.

• Python
• JavaScript
• C++
• C
• Java
• Consejos
• ¡Y mucho más!

Más abajo encontrarás mis redes sociales donde a través de éstas, podrás comunicarte conmigo directamente y así indicarme aquellas bibliografías o temas de interés que te gustaría que agregase en futuras actualizaciones al repositorio.

Lo mejor de la programación es que hay muchas personas dispuestas en ayudar a quienes lo necesite y yo admito que me encanta ser una de esas personas que tanto ayuda. Así que, te dejo mis enlaces a redes sociales que utilizo con mayor frecuencia y no tengas miedo de preguntarme, que más allá de un profesor, soy un amigo que le encanta el café y las galletas ☕

• Faceboook
• Twitter

Hay muchas formas de apoyar este proyecto (compartiéndolo con tus amigos, haciendo retweet, realizando alguna donación, entre otros). Mi más grande satisfacción es saber que con esta iniciativa, estaré ayudando a muchas personas en mejorar su educación en este mundo tan amplio como lo es la programación.

• PayPal

RAW Viewer is a desktop app which allows you to quickly cull your photos. You can view, rate, manage, and delete all your RAW photos straight out of camera without requiring conversion or importing, allowing you to get to editing your best photos as fast as possible. This application focuses on ease of use and speed, removing all the lag your culling workflow.

All ratings are saved directly to the RAW file, so when you are done culling, you can import the remaining photos into Lightroom (or any other software) and all the ratings will show up.

Maybe you are under the impression that viewing RAW photos in your favorite program is already fast? Or maybe you’ve been told that RAW photos are really hard to work with and slow is just the nature of RAW photos? Well, RAW viewer is here to tell you that all of that is a lie and culling your photos can be fast!

You can get the latest Windows and MacOS versions here: https://github.com/catdad/raw-viewer/releases/latest

This is a self-contained portable app. Unzip the download and run Raw Viewer.exe.

If you no longer wish to use this app, you can just delete the folder where you unzipped it — but don’t worry, all your photos as well as their ratings will stay right where you left them.

This is a self-contained portable app. Unzip the download and run Raw Viewer.

The first time you run it, it will fail to verify the app and show a message saying “Raw Viewer can’t be opened because it is from an unidentified developer”. If this happens, open System Preferences > Security & Privacy. There, you will see a message at the bottom saying “Raw Viewer was blocked from opening because it is not from an identified developer” with an “Open Anyway” button next to it. Click that button and now you will able to run the app. You will only need to do this once on your computer.

If you are a developer and know more about how to sign the application or wish to sponsor this effort, please let me know at issue #191.

If you no longer wish to use this app, you can just delete the folder where you unzipped it — but don’t worry, all your photos as well as their ratings will stay right where you left them.

Linux support is not quite there yet. If you would like to help, please see this issue.

BiSCoT is a tool that aims to improve the contiguity of scaffolds and contigs generated after a Bionano scaffolding. It looks for enzymatic labelling sites on contigs. If two distinct contigs share labels, BiSCoT merges them at the last shared site.

Biorxiv preprint : link

In case of troubles when using or installing the software, please open up an issue by clicking here.

BiSCoT comes in the form of a Python3 script with some Python and software dependencies. In order to run it correctly, you will need :

• Python 3 (tested with Python 3.6)
• the Biopython and Argparse python modules (both installed automatically with BiSCoT)
• the BLAT aligner if you plan on using the aggressive scaffolding mode that is based on shared labels and sequence similarity (BiSCoT was tested with the v36 version of BLAT)

BiSCoT is available on PyPI and can be installed with the following command:

pip install biscot

BiSCoT was designed to improve a prior Bionano scaffolding so it needs a few files generated during this step :

• one CMAP file (–cmap-ref argument) describing the positions of enzymatic labelling sites on the reference genome (filename usually looks like this *.cut_CTTAAG_GCTCTTC_0kb_0labels_NGS_contigs_HYBRID_Export_r.cmap in the case of a double hybrid scaffolding)
• one CMAP file per enzyme (–cmap-1 and –cmap-2 arguments) describing the positions of enzymatic labelling sites on the contigs (filenames usually look like this : E_CTTAAG_Q_NGScontigs_A_HYBRID_q.cmap for DLE1 and E_GCTCTTC_Q_NGScontigs_A_HYBRID_q.cmap for BspQI)
• a KEY file (–key argument) describing the names of the contig maps related to their FASTA file header names (filename usually looks like this *.cut_CTTAAG_GCTCTTC_0kb_0labels_key.txt)
• one XMAP file per enzyme (–xmap-1 and –xmap-2 arguments) describing the alignments of contig labels on the anchor (filename usually looks like this E_CTTAAG_Q_NGScontigs_A_HYBRID.xmap for DLE1 and E_GCTCTTC_Q_NGScontigs_A_HYBRID.xmap for BspQI)
• the contigs FASTA file (–contigs argument) that was used for the scaffolding

A typical execution of BiSCoT should look like this :

# Execute BiSCoT
biscot.py --cmap-ref cmap_reference.cmap \\
    --cmap-1 cmap_dle.cmap \\
    --cmap-2 cmap_bspqi.cmap \\
    --xmap-1 xmap_dle.xmap \\
    --xmap-2 xmap_bspqi.xmap \\
    --key key.txt \\
    --contigs contigs.fasta \\
    --output biscot

If everything went fine, a biscot directory should have been created. Inside, you will find two output files :

• a scaffolds.fasta containing the new scaffolds
• a scaffolds.agp file containing the changes made to contigs

If you would like to change the name/path of the output directory, you can do so with the --output argument.

• --xmap-2enz argument is used to provide the final XMAP file containing the mappings of labels of both enzymes. This argument is useful (and recommended) to ensure that no mapping has been missed inside one of the individual XMAP file. Usually, this file’s name looks like this: *.cut_CTTAAG_GCTCTTC_0kb_0labels_NGS_contigs_HYBRID_Export.xmap_sorted.xmap.
• --only-confirmed-pos argument is used so that only mappings contained in the --xmap-2enz file are retained. Indeed, by using one XMAP file per enzyme, contigs can be placed two times in the final assembly. This ensures that contigs are only placed one time and that created scaffolds are validated by both enzymes.
• --aggressive enables the sequence similarity scaffolding. In a first phase, BiSCoT will search similarities between contigs based on label mappings. If this parameter is set, BiSCoT will search for sequence similarity to close gaps created by the first step.

Created by L375 (@Lowie375), with contributions & support from Nao (@naoei), Irisu, and @alazymeme

Gyromina is entirely open source and licensed under the MIT license

Info Pages – Commands – Changelog – Invite Link – Development Server

Gyromina is a multipurpose Discord bot, made to be a fun and functional addition to any Discord server.

Gyromina contains an assortment of features, including a random colour and number generator, a unit converter, a library of minigames, a custom poll creator, miscellaneous fun commands, and more!

• Follow this link: https://discord.com/api/oauth2/authorize?client_id=490590334758420481&permissions=412317248576&scope=bot%20applications.commands
• Choose a server to add Gyromina to
• Make sure all requested permissions are enabled
  • Critical: Send Messages, View Channels, Read Message History, Add Reactions, Attach Files, Embed Links
  • Highly recommended: Send Messages in Threads, Use External Emojis, Manage Messages
• Toggle any configuration options as desired
• You’re good to go! Have fun!

• Discord bot token
• Discord server + channel access

• Fork/download source code + npm install in terminal
• Configure environment variables (>=1.2.0 = v10 configuration)
• Run using your native runtime/debugger/host and you’re good to go!

Please see the “If you are reporting a bug” section of docs/CONTRIBUTING.md for bug-reporting protocol.

Gyromina’s changelog can be found at https://l375.weebly.com/gyro-log.

The community Code of Conduct can be found under docs/CODE_OF_CONDUCT.md.

Contributions to Gyromina are always welcome! I don’t always have time on my hands to keep things running smoothly, so any help in doing that is greatly appreciated.

Please see docs/CONTRIBUTING.md for contribution information and general style notes, and docs/CODE_OF_CONDUCT.md for the community code of conduct.

• 💻 L375 – @Lowie375
• 💻 Nao – @naoei
• 💻 Irisu
• 💾 alazymeme – @alazymeme

Created by L375 (@Lowie375), with contributions & support from Nao (@naoei), Irisu, and @alazymeme

Gyromina is entirely open source and licensed under the MIT license

Info Pages – Commands – Changelog – Invite Link – Development Server

Gyromina is a multipurpose Discord bot, made to be a fun and functional addition to any Discord server.

Gyromina contains an assortment of features, including a random colour and number generator, a unit converter, a library of minigames, a custom poll creator, miscellaneous fun commands, and more!

• Follow this link: https://discord.com/api/oauth2/authorize?client_id=490590334758420481&permissions=412317248576&scope=bot%20applications.commands
• Choose a server to add Gyromina to
• Make sure all requested permissions are enabled
  • Critical: Send Messages, View Channels, Read Message History, Add Reactions, Attach Files, Embed Links
  • Highly recommended: Send Messages in Threads, Use External Emojis, Manage Messages
• Toggle any configuration options as desired
• You’re good to go! Have fun!

• Discord bot token
• Discord server + channel access

• Fork/download source code + npm install in terminal
• Configure environment variables (>=1.2.0 = v10 configuration)
• Run using your native runtime/debugger/host and you’re good to go!

Please see the “If you are reporting a bug” section of docs/CONTRIBUTING.md for bug-reporting protocol.

Gyromina’s changelog can be found at https://l375.weebly.com/gyro-log.

The community Code of Conduct can be found under docs/CODE_OF_CONDUCT.md.

Contributions to Gyromina are always welcome! I don’t always have time on my hands to keep things running smoothly, so any help in doing that is greatly appreciated.

Please see docs/CONTRIBUTING.md for contribution information and general style notes, and docs/CODE_OF_CONDUCT.md for the community code of conduct.

• 💻 L375 – @Lowie375
• 💻 Nao – @naoei
• 💻 Irisu
• 💾 alazymeme – @alazymeme

Two types of headers are used:

• indicators
• scores

Install the extension with pip:

pip install flask-sustainable
# Or
pip install git+https://github.com/av1m/flask-sustainable.git

💡 The code is available in example.py file

import flask
from flask_sustainable import Sustainable
from flask_sustainable.indicator import PerfCPU, PerfRAM, PerfTime

app = flask.Flask(__name__)
sustainable = Sustainable(app)  # Invoke Sustainable().init_app(app)
sustainable.add_indicators(PerfTime(), PerfCPU(), PerfRAM)

@app.route("https://github.com/")
def helloWorld():
    return "Hello, World!"

Then, try with cURL or Postman (or any other HTTP client):

$ curl http://localhost:5000/ -I -H "Perf: Perf-Time,Perf-CPU Perf-RAM"

Perf-Time: 0.76592
Perf-RAM: 0.12114
Perf-CPU: 0.97900

Use python3 or python command (depending on your configuration) There is a Makefile for helping with development.

1. Clone this project

git clone https://github.com/av1m/flask-sustainable.git
cd flask-sustainable

2. Run make command

make install

1. Run a sample; a server is running on port 5000

python example.py

Everything has been installed and configured correctly! 🎊 Once you modify the code, you can run make format and make test commands to check the code style and test coverage (through make coverage).

To find out all the available commands, you can use make help :

help              Display callable targets.
test              Run all tests.
coverage          Run all tests and generate coverage report.
requirements      Install requirements.
install           Install package.
run               Run a example script.
format            Format code.

A simple set of tests is included in tests/. To run, simply invoke make test or pytest. You can also run a coverage report with make coverage.

This project is compatible with Python 3.6 and up. It has been tested on Python 3.6, 3.7, 3.8, 3.9, and 3.10

The Github Actions is not compatible with Python 3.6 because there is no setup.py file.

This project is licensed under the MIT License.

Dynamically create and destroy servers

This package can help you start and stop servers when you need them. The prime use case is to spin up extra working servers that can help you process the workload on queues.

You can think of this as a sort of PHP based version of Kubernetes that has 5% of its features, but covers that 80% use case. For most PHP and Laravel developers, this package will also be easier to learn and use.

Typically, on your hosting provider, you would prepare a server snapshot, that will be used as a template when starting new servers.

After the package is configured, spinning up an extra servers is as easy as:

// typically, in a service provider

use Laravel\Horizon\WaitTimeCalculator;
use Spatie\DynamicServers\Facades\DynamicServers;
use Spatie\DynamicServers\Support\DynamicServersManager;

/*
 * The package will call the closure passed 
 * to `determineServerCount` every minute
 */
DynamicServers::determineServerCount(function(DynamicServersManager $servers) {
   /*
    * First, we'll calculate the number of servers needed. 
    * 
    * In this example, we will take a look at Horizon's 
    * reported waiting time. Of course, in your project you can 
    * calculate the number of servers needed however you want.    
    */
    $waitTimeInMinutes = app(WaitTimeCalculator::class)->calculate('default');
    $numberOfServersNeeded = round($waitTimeInMinutes / 10);

   /*
    * Next, we will pass the number of servers needed to the `ensure` method.
    * 
    * If there currently are less that that number of servers available,
    * the package will start new ones.
    * 
    * If there are currently more than that number of servers running,
    *  the package will stop a few servers.
    */
    $servers->ensure($numberOfServersNeeded);
});

Out of the box, the package supports UpCloud. You can create your own server provider to add support for your favourite hosting service.

We invest a lot of resources into creating best in class open source packages. You can support us by buying one of our paid products.

We highly appreciate you sending us a postcard from your hometown, mentioning which of our package(s) you are using. You’ll find our address on our contact page. We publish all received postcards on our virtual postcard wall.

All documentation is available on our documentation site.

composer test

Please see CHANGELOG for more information on what has changed recently.

Please see CONTRIBUTING for details.

Please review our security policy on how to report security vulnerabilities.

• Rias Van der Veken
• Freek Van der herten
• All Contributors

This idea behind this package was… spawned 🥁 by streams and a blog post by Jason McCreary on Spawning workers based on queue workload.

The MIT License (MIT). Please see License File for more information.

A PowerShell script with a CMD wrapper to easily switch between audio devices on Windows, utilizing nircmd.exe. Perfect for use with keyboard macro keys, or devices like a Stream Deck.

• Quickly toggle between two audio devices.
• Includes a CMD wrapper for seamless integration with macro systems or hotkey setups.
• Uses nircmd.exe for reliable audio device switching.
• Customizable to match your setup.

• Windows operating system.
• PowerShell 5.1 or later.
• nircmd.exe (provided in the repository).
• Renamed audio devices in Windows to match the script variables.

1. Clone the repository or download the files directly:

   git clone https://github.com/r0r0sec/AudioDeviceChanger.git

2. Navigate to the directory where the files are located:

   cd AudioDeviceChanger

For the script to work, your audio device names in Windows must match the values set in the script. To rename your audio devices:

1. Go to Settings → System → Sound → Output.
2. Click on your desired audio device and rename it, for example:
   • Headphones
   • Speakers
3. Update the script variables values in AudioDeviceChanger.ps1 if you use different names:

   # Update these values in the script
   $AudioDevice_1 = "YourDevice1Name"
   $AudioDevice_2 = "YourDevice2Name"

1. Open PowerShell in the script’s directory.
2. Run the script or right-click “Run with PowerShell”:

   .\AudioDeviceChanger.ps1

3. The script will toggle between the two configured audio devices.

1. Open a CMD interface in the script’s directory.
2. Run the script or just double-click the file:

   PSWrapper.cmd

3. The script will toggle between the two configured audio devices.

The PSWrapper.cmd file allows you to execute the script silently in the background, ideal for hotkeys or integration with devices like a Stream Deck.
In order to have the script run in the background, you can use the provided nircmd.exe and integrate it with the following command:

1. Right-click the Stream Deck system tray icon “Configure Stream Deck”
2. Add a new key from the Navigation “System” -> “Open”
3. Paste the following command under “App / File:”

"..\AudioDeviceChanger\nircmd-x64\nircmd.exe" exec hide "..\AudioDeviceChanger\PSWrapper.cmd"

This will execute the script without bringing up any visible windows, ensuring a seamless user experience.

Contributions are welcome! Please submit a pull request or open an issue if you have ideas for improvements or encounter any bugs.

This project uses NirCmd, a freeware utility developed by NirSoft. NirCmd is licensed as freeware and can be freely distributed as long as no modifications are made to the original files.

For more information and to download the utility, visit: https://www.nirsoft.net/utils/nircmd.html.

Note: The NirCmd files included in this project have not been modified in any way.

• Thanks to NirSoft for the fantastic nircmd.exe utility.