deno.yl (Milehigh-wrld#30)

* Update cj.ai * Update hedera.js * Update hedera.js * Update stripe.js * Update Milehigh-world.js * Update README.md Signed-off-by: Cirrus.logic <[email protected]> * Create deno.yml Signed-off-by: Cirrus.logic <[email protected]> * Create codeql.yml Signed-off-by: Cirrus.logic <[email protected]> * Update license * Update math.py --------- Signed-off-by: Cirrus.logic <[email protected]>
lucentlabz · Aug 21, 2024 · b761f26 · b761f26
1 parent db692ce
commit b761f26
Show file tree

Hide file tree

Showing 9 changed files with 427 additions and 18 deletions.
diff --git a/.github/workflows/codeql.yml b/.github/workflows/codeql.yml
@@ -0,0 +1,93 @@
+# For most projects, this workflow file will not need changing; you simply need
+# to commit it to your repository.
+#
+# You may wish to alter this file to override the set of languages analyzed,
+# or to provide custom queries or build logic.
+#
+# ******** NOTE ********
+# We have attempted to detect the languages in your repository. Please check
+# the `language` matrix defined below to confirm you have the correct set of
+# supported CodeQL languages.
+#
+name: "CodeQL"
+
+on:
+  push:
+    branches: [ "Milehigh.world" ]
+  pull_request:
+    branches: [ "Milehigh.world" ]
+  schedule:
+    - cron: '25 18 * * 1'
+
+jobs:
+  analyze:
+    name: Analyze (${{ matrix.language }})
+    # Runner size impacts CodeQL analysis time. To learn more, please see:
+    #   - https://gh.io/recommended-hardware-resources-for-running-codeql
+    #   - https://gh.io/supported-runners-and-hardware-resources
+    #   - https://gh.io/using-larger-runners (GitHub.com only)
+    # Consider using larger runners or machines with greater resources for possible analysis time improvements.
+    runs-on: ${{ (matrix.language == 'swift' && 'macos-latest') || 'ubuntu-latest' }}
+    timeout-minutes: ${{ (matrix.language == 'swift' && 120) || 360 }}
+    permissions:
+      # required for all workflows
+      security-events: write
+
+      # required to fetch internal or private CodeQL packs
+      packages: read
+
+      # only required for workflows in private repositories
+      actions: read
+      contents: read
+
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+        - language: javascript-typescript
+          build-mode: none
+        # CodeQL supports the following values keywords for 'language': 'c-cpp', 'csharp', 'go', 'java-kotlin', 'javascript-typescript', 'python', 'ruby', 'swift'
+        # Use `c-cpp` to analyze code written in C, C++ or both
+        # Use 'java-kotlin' to analyze code written in Java, Kotlin or both
+        # Use 'javascript-typescript' to analyze code written in JavaScript, TypeScript or both
+        # To learn more about changing the languages that are analyzed or customizing the build mode for your analysis,
+        # see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.
+        # If you are analyzing a compiled language, you can modify the 'build-mode' for that language to customize how
+        # your codebase is analyzed, see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v4
+
+    # Initializes the CodeQL tools for scanning.
+    - name: Initialize CodeQL
+      uses: github/codeql-action/init@v3
+      with:
+        languages: ${{ matrix.language }}
+        build-mode: ${{ matrix.build-mode }}
+        # If you wish to specify custom queries, you can do so here or in a config file.
+        # By default, queries listed here will override any specified in a config file.
+        # Prefix the list here with "+" to use these queries and those in the config file.
+
+        # For more details on CodeQL's query packs, refer to: https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs
+        # queries: security-extended,security-and-quality
+
+    # If the analyze step fails for one of the languages you are analyzing with
+    # "We were unable to automatically build your code", modify the matrix above
+    # to set the build mode to "manual" for that language. Then modify this step
+    # to build your code.
+    # ℹ️ Command-line programs to run using the OS shell.
+    # 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun
+    - if: matrix.build-mode == 'manual'
+      shell: bash
+      run: |
+        echo 'If you are using a "manual" build mode for one or more of the' \
+          'languages you are analyzing, replace this with the commands to build' \
+          'your code, for example:'
+        echo '  make bootstrap'
+        echo '  make release'
+        exit 1
+
+    - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze@v3
+      with:
+        category: "/language:${{matrix.language}}"
diff --git a/.github/workflows/deno.yml b/.github/workflows/deno.yml
@@ -0,0 +1,42 @@
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+
+# This workflow will install Deno then run `deno lint` and `deno test`.
+# For more information see: https://github.com/denoland/setup-deno
+
+name: Deno
+
+on:
+  push:
+    branches: ["Milehigh.world"]
+  pull_request:
+    branches: ["Milehigh.world"]
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Setup repo
+        uses: actions/checkout@v4
+
+      - name: Setup Deno
+        # uses: denoland/setup-deno@v1
+        uses: denoland/setup-deno@61fe2df320078202e33d7d5ad347e7dcfa0e8f31  # v1.1.2
+        with:
+          deno-version: v1.x
+
+      # Uncomment this step to verify the use of 'deno fmt' on each commit.
+      # - name: Verify formatting
+      #   run: deno fmt --check
+
+      - name: Run linter
+        run: deno lint
+
+      - name: Run tests
+        run: deno test -A
diff --git a/Milehigh-world.js b/Milehigh-world.js
@@ -0,0 +1,88 @@
+name: Node.js CI
+on:
+  push:
+    branches: [ "main" ]
+  pull_request:
+    branches: [ "main" ]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        node-version: [14.x, 16.x, 18.x]
+        # See supported Node.js release schedule at https://nodejs.org/en/about/releases/
+
+    steps:
+    - uses: actions/checkout@v4
+    - name: Use Node.js ${{ matrix.node-version }}
+      uses: actions/setup-node@v4
+      with:
+        node-version: ${{ matrix.node-version }}
+        cache: 'npm'
+    - run: npm ci
+    - run: npm run build --if-present
+    - run: npm test)
+
+
+    - name: Setup Node.js environment
+  uses: actions/setup-node@v4.0.2
+  with:
+    # Set always-auth in npmrc.
+    always-auth: # optional, default is false
+    # Version Spec of the version to use. Examples: 12.x, 10.15.1, >=10.15.0.
+    node-version: # optional
+    # File containing the version Spec of the version to use.  Examples: package.json, .nvmrc, .node-version, .tool-versions.
+    node-version-file: # optional
+    # Target architecture for Node to use. Examples: x86, x64. Will use system architecture by default.
+    architecture: # optional
+    # Set this option if you want the action to check for the latest available version that satisfies the version spec.
+    check-latest: # optional
+    # Optional registry to set up for auth. Will set the registry in a project level .npmrc and .yarnrc file, and set up auth to read in from env.NODE_AUTH_TOKEN.
+    registry-url: # optional
+    # Optional scope for authenticating against scoped registries. Will fall back to the repository owner when using the GitHub Packages registry (https://npm.pkg.github.com/).
+    scope: # optional
+    # Used to pull node distributions from node-versions. Since there's a default, this is typically not supplied by the user. When running this action on github.com, the default value is sufficient. When running on GHES, you can pass a personal access token for github.com if you are experiencing rate limiting.
+    token: # optional, default is ${{ github.server_url == 'https://github.com' && github.token || '' }}
+    # Used to specify a package manager for caching in the default directory. Supported values: npm, yarn, pnpm.
+    cache: # optional
+    # Used to specify the path to a dependency file: package-lock.json, yarn.lock, etc. Supports wildcards or a list of file names for caching multiple dependencies.
+    cache-dependency-path: # optional
+             - name: Setup Node.js environment
+- uses: actions/setup-node@v4.0.1
+  with:
+    # Set always-auth in npmrc.
+    always-auth: # optional, default is false
+    # Version Spec of the version to use. Examples: 12.x, 10.15.1, >=10.15.0.
+    node-version: # optional
+    # File containing the version Spec of the version to use.  Examples: package.json, .nvmrc, .node-version, .tool-versions.
+    node-version-file: # optional
+    # Target architecture for Node to use. Examples: x86, x64. Will use system architecture by default.
+    architecture: # optional
+    # Set this option if you want the action to check for the latest available version that satisfies the version spec.
+    check-latest: # optional
+    # Optional registry to set up for auth. Will set the registry in a project level .npmrc and .yarnrc file, and set up auth to read in from env.NODE_AUTH_TOKEN.
+    registry-url: # optional
+    # Optional scope for authenticating against scoped registries. Will fall back to the repository owner when using the GitHub Packages registry (https://npm.pkg.github.com/).
+    scope: # optional
+    # Used to pull node distributions from node-versions. Since there's a default, this is typically not supplied by the user. When running this action on github.com, the default value is sufficient. When running on GHES, you can pass a personal access token for github.com if you are experiencing rate limiting.
+    token: # optional, default is ${{ github.server_url == 'https://github.com' && github.token || '' }}
+    # Used to specify a package manager for caching in the default directory. Supported values: npm, yarn, pnpm.
+    cache: # optional
+    # Used to specify the path to a dependency file: package-lock.json, yarn.lock, etc. Supports wildcards or a list of file names for caching multiple dependencies.
+    cache-dependency-path: #             - name: Cloud Maker Deploy
+  # You may pin to the exact commit or the version.
+  # uses: cloud-maker-ai/github-action-deploy@f86239fb28b589a9898a361b3df1dac5f3d3fc8f
+  uses: cloud-maker-ai/github-action-deploy@v1.0.1
+  with:
+    # Cloud Maker API Token
+    CLOUD_MAKER_TOKEN: 
+    # Cloud Maker Pipeline ID to be deployed
+    CLOUD_MAKER_PIPELINE_ID: 
+    # Cloud Maker Stage ID to be deployed
+    CLOUD_MAKER_STAGE_ID: 
+
+
+
diff --git a/README.md b/README.md
@@ -1,21 +1,37 @@
-milehigh.world
-1. Music Education and Learning:
-Milehigh.world offers a variety of resources to help musicians enhance their skills and knowledge. This includes tutorials, online courses, and workshops on various aspects of music production, songwriting, music theory, and instrument mastery. These resources aim to provide musicians with the tools and techniques to improve their craft and pursue their musical aspirations.
-2.Networking and Collaboration:
-Milehigh.world provides a platform for musicians to connect and collaborate with each other. Through the platform, musicians can find potential collaborators, such as vocalists, producers, instrumentalists, and songwriters. This collaborative environment encourages creativity, allows musicians to explore new genres and styles, and provides opportunities to learn from others.
-4. Community Forums and Discussions:
-Milehigh.world features community forums and discussion boards where musicians can engage in conversations, ask questions, and share their experiences. These forums provide a space for musicians to connect with like-minded individuals, seek advice, and receive feedback on their work. Engaging in these discussions can foster a sense of community and enable knowledge-sharing among musicians.
+<h1/>Milehigh.world<h1/>
+
+<h2/>1. Music Education and Learning:<h2/>
+
+          Milehigh.world offers a variety of resources to help musicians enhance their skills and knowledge. This includes tutorials, online courses, and workshops on various aspects of music production, songwriting, music theory, and instrument mastery. These resources aim to provide musicians with the tools and techniques to improve their craft and pursue their musical aspirations.
+
+2.  Networking and Collaboration:
+
+          Milehigh.world provides a platform for musicians to connect and collaborate with each other. Through the platform, musicians can find potential collaborators, such as vocalists, producers, instrumentalists, and songwriters. This collaborative environment encourages creativity, allows musicians to explore new genres and styles, and provides opportunities to learn from others.
+
+3. Community Forums and Discussions:
+
+         Milehigh.world features community forums and discussion boards where musicians can engage in conversations, ask questions, and share their experiences. These forums provide a space for musicians to connect with like-minded individuals, seek advice, and receive feedback on their work. Engaging in these discussions can foster a sense of community and enable knowledge-sharing among musicians.
+
 5. Industry Insights and Trends:
-The platform offers resources that provide insights into the latest trends and developments in the music industry. These resources cover topics such as music streaming, digital marketing strategies, fan engagement, and monetization. By staying updated on industry trends, musicians can make informed decisions and adapt their strategies to align with the evolving music landscape.
-6.Exclusive Events and Competitions:
-Milehigh.world organizes exclusive events and competitions for its members. These events may include live performances, showcases, talent contests, and more. Participating in these events can provide exposure and networking opportunities for musicians, allowing them to gain visibility within the industry.
-7.Career Development Resources:
-The platform offers resources and guidance on various aspects of career development for musicians. This includes topics such as building a professional brand, creating an online presence, marketing strategies, and networking. These resources aim to help musicians navigate the business side of the music industry and establish a successful career.
-8. Feedback and Critique:
-Milehigh.world provides a platform for musicians to receive feedback and critique on their work. Members can submit their music for review by the community or industry professionals, allowing them to gain constructive feedback and insights to improve their craft. This feedback mechanism can be valuable in honing skills and refining musical compositions.
-9.Music Library and Distribution:
-Milehigh.world has a music library where musicians can showcase their work and make it available for licensing opportunities. This allows musicians to monetize their music and reach a wider audience. The platform also offers distribution services, enabling musicians to release their music on various streaming platforms and digital stores.
-
-These additional features and resources provided by Milehigh.world further enhance the learning and growth opportunities for musicians. They aim to provide a comprehensive ecosystem that supports musicians in their creative journey, facilitates collaboration and networking, and equips them with the knowledge and tools necessary to succeed in the music industry.
+
+         The platform offers resources that provide insights into the latest trends and developments in the music industry. These resources cover topics such as music streaming, digital marketing strategies, fan engagement, and monetization. By staying updated on industry trends, musicians can make informed decisions and adapt their strategies to align with the evolving music landscape.
+
+5.Exclusive Events and Competitions:
+
+        Milehigh.world organizes exclusive events and competitions for its members. These events may include live performances, showcases, talent contests, and more. Participating in these events can provide exposure and networking opportunities for musicians, allowing them to gain visibility within the industry.
+
+6.Career Development Resources:
+
+        The platform offers resources and guidance on various aspects of career development for musicians. This includes topics such as building a professional brand, creating an online presence, marketing strategies, and networking. These resources aim to help musicians navigate the business side of the music industry and establish a successful career.
+
+7. Feedback and Critique:
+
+       Milehigh.world provides a platform for musicians to receive feedback and critique on their work. Members can submit their music for review by the community or industry professionals, allowing them to gain constructive feedback and insights to improve their craft. This feedback mechanism can be valuable in honing skills and refining musical compositions.
+
+8.Music Library and Distribution:
+
+      Milehigh.world has a music library where musicians can showcase their work and make it available for licensing opportunities. This allows musicians to monetize their music and reach a wider audience. The platform also offers distribution services, enabling musicians to release their music on various streaming platforms and digital stores.
+
+          These aditional features and resources provided by Milehigh.world further enhance the learning and growth opportunities for musicians. They aim to provide a comprehensive ecosystem that supports musicians in their creative journey, facilitates collaboration and networking, and equips them with the knowledge and tools necessary to succeed in the music industry.
 
 
diff --git a/cj.ai b/cj.ai
@@ -0,0 +1 @@
+curl -H "Authorization: Bearer <your-personal-access-token>" -X POST https://commissions.api.cj.com/query -d '{ "query": "{ publisherCommissions(forPublishers: [\"999\"], sincePostingDate: \"2018-08-08T00:00:00Z\", beforePostingDate: \"2018-08-09T00:00:00Z\") { count payloadComplete records { actionTrackerName websiteName advertiserName postingDate pubCommissionAmountUsd items { quantity perItemSaleAmountPubCurrency totalCommissionPubCurrency } } } }" }'
diff --git a/hedera.js b/hedera.js
@@ -0,0 +1,33 @@
+import com.hedera.hashgraph.sdk.AccountCreateTransaction;
+import com.hedera.hashgraph.sdk.AccountId;
+import com.hedera.hashgraph.sdk.Hbar;
+import com.hedera.hashgraph.sdk.PrivateKey;
+import com.hedera.hashgraph.sdk.TransactionReceipt;
+import com.hedera.hashgraph.sdk.TransactionResponse;
+import com.hedera.hashgraph.sdk.Client;
+
+public class CreateAccount {
+    public static void main(String[] args) throws Exception {
+        // Initialize the Hedera client
+        Client client = Client.forTestnet(); // or Client.forMainnet()
+        client.setOperator(operatorId, operatorPrivateKey);
+
+        // Generate a new private key for the new account
+        PrivateKey privateKey = PrivateKey.generate();
+
+        // Create the account create transaction
+        AccountCreateTransaction transaction = new AccountCreateTransaction()
+            .setKey(privateKey.getPublicKey())
+            .setInitialBalance(new Hbar(1000));
+
+        // Submit the transaction to a Hedera network
+        TransactionResponse txResponse = transaction⬤
+
+        //Create an account with 1,000 hbar
+AccountCreateTransaction transaction = new AccountCreateTransaction()
+    // The only _required_ property here is `key`
+    .setKey(newKey.getPublicKey())
+    .setInitialBalance(new Hbar(1000));
+
+//Return the key on the account
+Key accountKey = transaction.getKey();
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1 @@
		curl -H "Authorization: Bearer <your-personal-access-token>" -X POST https://commissions.api.cj.com/query -d '{ "query": "{ publisherCommissions(forPublishers: [\"999\"], sincePostingDate: \"2018-08-08T00:00:00Z\", beforePostingDate: \"2018-08-09T00:00:00Z\") { count payloadComplete records { actionTrackerName websiteName advertiserName postingDate pubCommissionAmountUsd items { quantity perItemSaleAmountPubCurrency totalCommissionPubCurrency } } } }" }'