Module for seeding the Debt Syndicate’s Discourse instances with Collectives, User Groups, Wikis, Settings, and anything else we need to bend Discourse to our purposes.

If you need to make a new endpoint accessible in the discourse-node-api you may mask the request by using the auth<METHOD> functions exposed by the DiscourseApi instance until your PR in the discourse-node-api is merged and available for use.

Any unhandled error will kill the script, so handle them early if you expect them.

Discourse API docs are here. The docs are kinda bad though, so the best thing to do is use Wireshark and sniff an API call after making it manually through the front-end and mimicking that through the Discourse API. Most endpoints work using the same exact route that the front-end uses. If it doesn’t, try putting .json on the end of the route. More information about reverse-engineering the API here. The main pain-point of the documentation is that almost none of the interesting properties that are editable in a PUT or POST are documented, so the best thing to do really is to figure it out through reverse engineering and not waste your time with the documentation unless you’re going to contribute to them (maybe once we have time we’ll do that and make the Discourse API docs real nice to use).

Open a PR, get it reviewed and approved by a maintainer and once it is merged the CI will seed staging once a maintainer removes the CI hold. 🎊

This script requires a couple secrets to work.
Really only two of these is a secret but 🤷‍♀️.
These all have defaults in the script but you’ll need to update the API key and the SSO secret.
See step 2, below.

2. Generate an API key for the system user (Admin Dashboard -> Users -> system -> generate API key)
3. Copy secrets.sample to secrets.<env>.js and fill in the correct values.
4. Upload the secrets file to tdc-secure S3 bucket ensuring public access is OFF. Only the CI policy will have access to this file.
5. Create a job in the CI workflow for the environment, mirroring how the other environments have it. Note that seed.sh takes a single variable of the environment which should match the <env> part of the secrets.<env>.js from before
6. Restrict that job to a specific branch.
7. Push that branch and release the hold in Circle CI for that build.
8. Success!

AWS EC2 Spot Instance Termination Notices for NodeJs

Install with npm:

npm install --save ec2-spot-notification

import {SpotNotifier as spot} from "ec2-spot-notification";

spot.once("termination", date => {
    console.log("termination", date);
});
spot.once("termination-cancelled", date => {
    console.log("termination-cancelled", date);
});
spot.on("termination-not-detected", error => {
    console.log("termination-not-detected", error);
});
spot.on("instance-termination", error => {
    console.log("instance-termination", error);
});

spot.instanceId()
    .then(id => {
        console.log("instanceId", id);
        spot.start();
    })
    .catch(err => {
        console.error("instanceId", err);
    });

var SpotNotifier = require("ec2-spot-notification").SpotNotifier;
var aws = require("aws-sdk");

var instanceId = null;
var elb = new aws.ELB();

SpotNotifier.on("termination", function (date) {
    console.log("Aws termination detected", date.toString());

    elb.deregisterInstancesFromLoadBalancer({
        Instances: [{InstanceId: instanceId}],
        LoadBalancerName: "Nutcracker"
    }, function (err, data) {
        if (err)
            console.error("deregisterInstancesFromLoadBalancer", err);
        else {
            console.log("deregisterInstancesFromLoadBalancer", data);
            SpotNotifier.stop();
        }
    });

});
SpotNotifier.on("termination-cancelled", function (date) {
    console.log("Aws termination cancelled for %s, restarting notifier", date.toString());

    SpotNotifier.start();
    elb.registerInstancesWithLoadBalancer({
        Instances: [{InstanceId: instanceId}],
        LoadBalancerName: "Nutcracker"
    }, function (err, data) {
        if (err)
            console.error("deregisterInstancesFromLoadBalancer", err);
        else {
            console.log("deregisterInstancesFromLoadBalancer", data);
        }
    });

});
SpotNotifier.instanceId()
    .then(function (iId) {
        console.log("Aws Spot Notification instanceId", iId);
        instanceId = iId;
        SpotNotifier.start();
    })
    .catch(function (err) {
        console.error("Aws Spot Notification instanceId", err);
    });

ubuntu@ip-172-31-2-186:~/ec2-spot-notification$ npm run test-server
instanceId i-05858013e
termination-not-detected 404
termination-not-detected 404
termination-not-detected 404
termination-not-detected 404
termination moment("2017-02-08T12:49:14.000")

Broadcast message from root@ip-172-31-2-186
	(unknown) at 12:49 ...

We welcome contributions of all kinds from anyone.

• Author: Tümay Çeber

MIT License

AWS EC2 Spot Instance Termination Notices for NodeJs

Install with npm:

npm install --save ec2-spot-notification

import {SpotNotifier as spot} from "ec2-spot-notification";

spot.once("termination", date => {
    console.log("termination", date);
});
spot.once("termination-cancelled", date => {
    console.log("termination-cancelled", date);
});
spot.on("termination-not-detected", error => {
    console.log("termination-not-detected", error);
});
spot.on("instance-termination", error => {
    console.log("instance-termination", error);
});

spot.instanceId()
    .then(id => {
        console.log("instanceId", id);
        spot.start();
    })
    .catch(err => {
        console.error("instanceId", err);
    });

var SpotNotifier = require("ec2-spot-notification").SpotNotifier;
var aws = require("aws-sdk");

var instanceId = null;
var elb = new aws.ELB();

SpotNotifier.on("termination", function (date) {
    console.log("Aws termination detected", date.toString());

    elb.deregisterInstancesFromLoadBalancer({
        Instances: [{InstanceId: instanceId}],
        LoadBalancerName: "Nutcracker"
    }, function (err, data) {
        if (err)
            console.error("deregisterInstancesFromLoadBalancer", err);
        else {
            console.log("deregisterInstancesFromLoadBalancer", data);
            SpotNotifier.stop();
        }
    });

});
SpotNotifier.on("termination-cancelled", function (date) {
    console.log("Aws termination cancelled for %s, restarting notifier", date.toString());

    SpotNotifier.start();
    elb.registerInstancesWithLoadBalancer({
        Instances: [{InstanceId: instanceId}],
        LoadBalancerName: "Nutcracker"
    }, function (err, data) {
        if (err)
            console.error("deregisterInstancesFromLoadBalancer", err);
        else {
            console.log("deregisterInstancesFromLoadBalancer", data);
        }
    });

});
SpotNotifier.instanceId()
    .then(function (iId) {
        console.log("Aws Spot Notification instanceId", iId);
        instanceId = iId;
        SpotNotifier.start();
    })
    .catch(function (err) {
        console.error("Aws Spot Notification instanceId", err);
    });

ubuntu@ip-172-31-2-186:~/ec2-spot-notification$ npm run test-server
instanceId i-05858013e
termination-not-detected 404
termination-not-detected 404
termination-not-detected 404
termination-not-detected 404
termination moment("2017-02-08T12:49:14.000")

Broadcast message from root@ip-172-31-2-186
	(unknown) at 12:49 ...

We welcome contributions of all kinds from anyone.

• Author: Tümay Çeber

MIT License

Este trabalho foi desenvolvido com o objetivo de implementar o controle e detecção de colisão de um robô diferencial. Utilizando tecnologias como ROS e Turtlebot-gazebo3.

fonte: ROS

fonte: Turtlebot3

• Instalação do ROS:

Caso seja necessária siga as instruções do Tutorial ROS

• Instalação do Turtlebot3:

Caso seja necessária siga as instruções do Tutorial Turtlebot-Gazebo3

1. Realize o clone deste projeto na pasta do onde foi instalado o turtlebot-gazebo3:

cd ~/[nome do workspace]/src/ && git clone https://github.com/keikomori/turtlebot-gazebo

2. Em seguida, para rodar o simulador Gazebo e a aplicação para controlar o robô, execute o comando:

roslaunch desafio3 controletb3.launch

3. E pronto! Para fazer com que o robô se movimente, insira as coordenadas quando solicitado.

ROS + Python + Linux + Turtlebot-gazebo3

Anderson Rodrigues Pereira

Guilherme Santos da Silva

Tatiany Keiko Mori

⚙️ Simple Step to Step Tutorials for Disassembling / Code Injection & getting Pointer Addresses 🔧

1. Set Value Type All
2. Set Value (ex. (Int 32 = 4 Byte = 32 Bit) 85 or (float/double) 85.5) you search for and press First Scan

3. Change Value in the Process
4. The Changed Value will be red, on the left is the Pointer Address

1. Right Click on Address Record
2. Select Find out what writes to this address
3. Press on Replace

4. Delete the Assembly Code and Press OK

1. Read the Address

2. Check Checkbox Hex and put the Address in it
3. The Address to the Pointer is in this ex. 1002CBA40

1. Select Find out what writes to this address
2. Press on More information

3. The Address to the Pointer is in this ex. 011DC7A0

01168A78 = Address / base pointer (base ptr)

0x18 = Offset

“Tutorial-x86_64.exe” + 2CBA70 = static base address

-> = points to

01168A78 = Value = 2765

01188070 -> 1168A60 + 0x18 = 01168A78

01168A18 -> 01188070 + 0 = 01188070

011681D0 -> 1168A00 + 0x18 = 01168A18

“Tutorial-x86_64.exe” + 2CBA70 -> 11681C0 + 0x10 = 011681D0

1. Right Click on Address Record
2. Select Find out what accesses this address

3. Calculate the Address using the Offset ex. -> (01188070 -> 1168A60 + 0x18 = 01168A78)
   Calculation (hex) : (01168A78 – 18 = 01168A60 = 1168A60)
4. Check Checkbox Hex and put the Address in it (ex. 1168A60)
5. The Address to the Pointer is in this ex. 01188070
6. Repeat Step 1 to 5 until you get the static base Address, in this ex. “Tutorial-x86_64.exe” + 2CBA70

1. Click on Add Address Manually

2. Add Address, if needed with Offsets and click OK

3. The Result should look like this:

1. Click on Add Address Manually

2. Add Address, if needed with Offsets and click OK

3. The Result should look like this:

1. Right Click on Address Record
2. Select Find out what writes to this address
3. Press Show disassembler

4. Click on Tools and select Auto Assemble

5. Click on Template and select Code Injection

6. Click on OK
7. Comment out as an ex. //sub dword ptr [rsi+00000780],01 (value – 1)
8. Write as an ex. add dword ptr [rsi+00000780],01 (value + 1)

9. Press on Execute and then click OK and it’s Done!

Create a filled two-dimensional symmetric nested array according to a provided callback function.

npm install @stdlib/array-base-symmetric-filled2d-by

var filled2dBy = require( '@stdlib/array-base-symmetric-filled2d-by' );

function clbk( idx ) {
    return idx[ 0 ] + idx[ 1 ];
}

var out = filled2dBy( 2, clbk );
// returns [ [ 0, 1 ], [ 1, 2 ] ]

function clbk() {
    this.count += 1;
    return 1;
}

var ctx = {
    'count': 0
};

var out = filled2dBy( 2, clbk, ctx );
// returns [ [ 1, 1 ], [ 1, 1 ] ];

var cnt = ctx.count;
// returns 3

var constantFunction = require( '@stdlib/utils-constant-function' );
var filled2dBy = require( '@stdlib/array-base-symmetric-filled2d-by' );

var out = filled2dBy( 2, constantFunction( 0.0 ) );
// returns [ [ 0.0, 0.0 ], [ 0.0, 0.0 ] ]

out = filled2dBy( 2, constantFunction( 'beep' ) );
// returns [ [ 'beep', 'beep' ], [ 'beep', 'beep' ] ]

out = filled2dBy( 2, constantFunction( null ) );
// returns [ [ null, null ], [ null, null ] ]

out = filled2dBy( 2, constantFunction( true ) );
// returns [ [ true, true ], [ true, true ] ]

function clbk( indices ) {
    return indices[ 0 ] + indices[ 1 ];
}
out = filled2dBy( 3, clbk );
// returns [ [ 0, 1, 2 ], [ 1, 2, 3 ], [ 2, 3, 4 ] ]

An action for interacting with the CurseForge file upload API

name: "Build Release"
on: push
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - { uses: actions/checkout@v2, with: { fetch-depth: 0 } }
      - {
          name: "Set up JDK 17",
          uses: actions/setup-java@v2,
          with: { distribution: "adopt", java-version: "17" },
        }
      - {
          name: "Build with Gradle",
          id: build,
          run: "chmod +x gradlew && ./gradlew build publish",
        }
      - name: "Upload to CurseForge"
        uses: itsmeow/curseforge-upload@v3
        with:
          file_path: "build/libs/examplemod-${{ steps.build.outputs.version }}.jar"
          game_endpoint: "minecraft"
          relations: "fabric-api:requiredDependency"
          game_versions: "Minecraft 1.18:1.18.1,Java 17,Fabric"
          project_id: "0"
          token: "${{ secrets.CF_API_TOKEN }}"

In this example, a file is uploaded with no custom title to project ID 0 in the Minecraft game category, with a dependency on Fabric API and game versions 1.18.1, Java 17, and Fabric loader.

The version in the filepath is not exported by default, so you can add this block to your buildscript to do so (this requires the Ubuntu runner):

exec {
    commandLine "echo", "##[set-output name=version;]${project.version}";
}

Obtain them here: https://www.curseforge.com/account/api-tokens

Add the token to your repository’s secrets tab to use it, found under Settings.

You MUST namespace Minecraft version IDs as there are duplicates in the system for Bukkit.

You can use numerical IDs by making a request to and picking your versions from this API:

https://endpoint.curseforge.com/api/game/versions?token=your_token

Using this method is more efficient request wise, as otherwise the Action will have to search this API before requesting the upload.

Another method is using Inspect Element on the game version check boxes, the value field contains the version ID.

However, this is not always convenient. You can also use names and slugs from that API, for example: “1.12.2” and “Java 8” will be automatically parsed into the proper id.

You may encounter issues with names/slugs that have multiple entries with different game version types. The minecraft endpoint has “1.12” 5 separate times with different game version types for Bukkit, Minecraft 1.12, etc.
To fix this, you can prefix a game version with a Type’s ID, slug, or name. For example “Minecraft 1.12:1.12” would get you ONLY the Minecraft 1.12 version and not the 4 others.

Another example is “java:Java 8”. This filters to anything named “Java 8” with the type matching the slug/name “java”.

You can get a list of game version type IDs from this API:

https://endpoint.curseforge.com/api/game/version-types?token=your_token

An e-commerce website built using React, Redux Toolkit, Tailwind CSS, Toastify, SweetAlert, and a public product API. The main features include product search, filtering by price, a shopping cart, and a checkout page. Additionally, it utilizes a public API for user login functionality.

The project is an e-commerce website that allows users to browse through a collection of products, search for specific items, filter products based on price, add them to a shopping cart, and proceed to checkout. It also features user authentication using a public API.

• Product search
• Price filtering
• Shopping cart
• Checkout page
• User authentication (using a public API)

(https://innovation-private-limited-task.netlify.app/login)

Follow these instructions to get the project up and running on your local machine.

• Node.js and npm installed on your machine

1. Clone the repository:

   git clone https://github.com/svivek19/innovation-private-limited-task.git

2. Navigate to the project directory:
   cd e-commerce-website

3. Install dependencies:
   npm install

Usage
Once you have installed the dependencies, you can start the development server:
~npm start
This will run the application in development mode. Open http://localhost:3000 to view it in your browser.

Contributing
Contributions are welcome! If you’d like to contribute to the project, please follow these steps:

1.Fork the repository
2.Create a new branch (git checkout -b feature/your-feature)
3.Make your changes
4.Commit your changes (git commit -am ‘Add some feature’)
5. Push to the branch (git push origin feature/your-feature)
6. Create a new pull request

Contact
For any questions or inquiries, please feel free to contact me at svivek030503@gmail.com

This Rails gem helps to build a bridge from assets in your ruby gems to Webpack.

1. I had a classic monolith Rails application with Sprockets.
2. I’ve split my Rails app into a few Rails gems and moved my assets into gems.
3. I started migration from Sprockets to Webpack.
4. Webpack didn’t know how to find my assets in Rails gems.

This gem helps to collect paths to assets’ folders in gems and adds some aliases for Webpack to help it to find assets in classic Rails gems.

Gemfile

gem 'gems_assets_webpack_bridge'

$ bundle

Build a bridge between Rails gems and Webpack:

rake gems_assets_webpack_bridge:build

• The Bridge is a JSON file with paths to assets in your gems.
• The Bridge provides additional aliases for Webpack to help it to find assets’ folders in ruby gems.
• Every alias has the following naming: @[UNDERSCORED_GEM_NAME]-[ASSET_TYPE].
• Default asset types are: images, scripts, styles.
• By default the file has name gems-assets-webpack-bridge.json and looks like that:

{
  "@crop_tool-scripts": "/Users/@username/.rvm/gems/ruby-2.4.2/gems/crop_tool/app/assets/javascripts",
  "@crop_tool-styles": "/Users/@username/.rvm/gems/ruby-2.4.2/gems/crop_tool/app/assets/stylesheets",
  "@jquery_ui_rails-images": "/Users/@username/.rvm/gems/ruby-2.3.3@open-cook.ru/gems/jquery-ui-rails-5.0.0/app/assets/images",
  "@jquery_ui_rails-scripts": "/Users/@username/.rvm/gems/ruby-2.3.3@open-cook.ru/gems/jquery-ui-rails-5.0.0/app/assets/javascripts",
  "@jquery_ui_rails-styles": "/Users/@username/.rvm/gems/ruby-2.3.3@open-cook.ru/gems/jquery-ui-rails-5.0.0/app/assets/stylesheets",
  "@log_js-scripts": "/Users/@username/.rvm/gems/ruby-2.4.2/gems/log_js/app/assets/javascripts",
  "@notifications-scripts": "/Users/@username/.rvm/gems/ruby-2.4.2/gems/notifications/app/assets/javascripts",
  "@notifications-styles": "/Users/@username/.rvm/gems/ruby-2.4.2/gems/notifications/app/assets/stylesheets",
}

Now, when you have the bridge file, you can use it in Webpack like this:

webpack.config.js

// This helper-function reads the bridge file and
// adds some additional aliases in `WebPackConfig.resolve.alias`
function addGemsAssetsWebpackBridge (WebPackConfig) {
  const alias = WebPackConfig.resolve.alias
  const bridgeFile = `${rootPath}/gems-assets-webpack-bridge.json`

  var bridgeAlias = JSON.parse(fs.readFileSync(bridgeFile, 'utf8'))
  return Object.assign(alias, bridgeAlias)
}

let WebpackConfig = {
  entry: {
    ...
  },

  output: {
    ...
  },

  resolve : {
    alias: {
      '@vendors': `${rootPath}/assets/vendors`
    }
  }
}

WebPackConfig.resolve.alias = addGemsAssetsWebpackBridge(WebPackConfig)
module.exports = WebPackConfig

After you added the aliases you can use them in your Webpack entries like this:

require('@log_js-scripts/log_js')
require('@notifications-scripts/notifications')
require('@the_comments-scripts/the_comments')

require('@notifications-styles/notifications')
require('@the_comments-styles/the_comments')

You can create a new initializer in your Rails app change options:

config/initializers/gems_assets_webpack_bridge.rb

GemsAssetsWebpackBridge.configure do |config|
  # From a root of your Rails app
  config.bridge_path = '/configs/gems-webpack-bridge.json'

  #  From a root of every Rails gem
  config.assets_types = {
    # Default values
    images: 'app/assets/images',
    scripts: 'app/assets/javascripts',
    styles: 'app/assets/stylesheets',

    # Your custom values
    vendor_select2_images: 'vendors/select2/images',
  }
end

No. Paths will be different for different users. Just add gems-assets-webpack-bridge.json in your .gitignore and run rake gems_asstes_webpack_bridge:build when you need it.

You have to run rake gems_asstes_webpack_bridge:build before every Webpack compilation during deployment. Otherwise Webpack will know nothing about aliases and a compilation won’t work.

The gem is available as open source under the terms of the MIT License.

Bridge image @ pexels.com