CodeX is a team of digital specialists around the world interested in building high-quality open source products on a global market. We are open for young people who want to constantly improve their skills and grow professionally with experiments in cutting-edge technologies.
CodeX is a team of digital specialists around the world interested in building high-quality open source products on a global market. We are open for young people who want to constantly improve their skills and grow professionally with experiments in cutting-edge technologies.
A simple snake game in java .
Using Threads and Java Swing to display the game.
The code is well commented, if you have any questions or want to continue this project feel free to do so 👌
How it looks:
How you can support me:
How to run the project:
Requirements:
Java runtime installed
Alternatively: Docker
How to play the game:
Just download the SnakeGame.jar file
Run it
Start playing with the arrows keys
If you lose, just close it and re-open it (I will add a restart button possibly)
This Utility can search any specified Key/Secret in all KeyVault present in your subscription. The search result than can be exported to an excel file and you can also update the secret directly from the Utility UI.
Light weight : PowerShell based utility.
Secure : Runs on user context and doesn’t collect any telemetry or logs.
Prerequisite
Requires Powershell Core or Powershell 7 and above
Once logged in enter Subscription ID, Secret/Key, Value to be searched & Keyvault Name and click Search
Utility will start searching secret/key in the KeyVault and Result be displayed in the Result Box as shown
Result can be Exported to CSV file and file will be saved on Desktop with the name scanresult.csv
You can select what all keys in the result that needs to be updated with new value and pass the value to the textbox and click update
)
Contributing
This project welcomes contributions and suggestions. Most contributions require you to agree to a
Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us
the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide
a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions
provided by the bot. You will only need to do this once across all repos using our CLA.
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft
trademarks or logos is subject to and must follow
Microsoft’s Trademark & Brand Guidelines.
Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship.
Any use of third-party trademarks or logos are subject to those third-party’s policies.
Procedural Generation of Infinite Voxel Cave Terrain
程序化生成体素洞穴地形
Introduce 简介
This is a Windows-based project for procedurally generating voxel caves. It primarily implements chunk-based data structures, uses noise functions as thresholds for cave and terrain generation, employs OpenGL to render voxel terrain, optimizes performance with voxel face culling and frustum culling, and utilizes multithreading to separate rendering from generation logic, enabling the creation of an infinite voxel cave terrain.
Prerequisites:Java 8 and Node.js. For Java 10+, you’ll need to change the java.version property and jaxb-api as a dependency. See Josh Long’s spring-boot-and-java-10 project on GitHub for more information.
Okta has Authentication and User Management APIs that reduce development time with instant-on, scalable user infrastructure. Okta’s intuitive API and expert support make it easy for developers to authenticate, manage and secure users and roles in any application.
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
Our Standards
Examples of behavior that contributes to a positive environment for our community include:
Demonstrating empathy and kindness toward other people
Being respectful of differing opinions, viewpoints, and experiences
Giving and gracefully accepting constructive feedback
Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
Focusing on what is best not just for us as individuals, but for the overall community
Examples of unacceptable behavior include:
The use of sexualized language or imagery, and sexual attention or advances of any kind
Trolling, insulting or derogatory comments, and personal or political attacks
Public or private harassment
Publishing others’ private information, such as a physical or email address, without their explicit permission
Contacting individual members, contributors, or leaders privately, outside designated community mechanisms, without their explicit permission
Other conduct which could reasonably be considered inappropriate in a professional setting
Enforcement Responsibilities
Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
Scope
This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at github@izanagicraft.com. All complaints will be reviewed and investigated promptly and fairly.
All community leaders are obligated to respect the privacy and security of the reporter of any incident.
Enforcement Guidelines
Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
1. Correction
Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
2. Warning
Community Impact: A violation through a single incident or series of actions.
Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
3. Temporary Ban
Community Impact: A serious violation of community standards, including sustained inappropriate behavior.
Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
4. Permanent Ban
Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
Consequence: A permanent ban from any sort of public interaction within the community.
Quoting the README from Google’s robots.txt parser and matcher repo:
The Robots Exclusion Protocol (REP) is a standard that enables website owners to control which URLs may be accessed by automated clients (i.e. crawlers) through a simple text file with a specific syntax. It’s one of the basic building blocks of the internet as we know it and what allows search engines to operate.
Because the REP was only a de-facto standard for the past 25 years, different implementers implement parsing of robots.txt slightly differently, leading to confusion. This project aims to fix that by releasing the parser that Google uses.
The library is slightly modified (i.e. some internal headers and equivalent symbols) production code used by Googlebot, Google’s crawler, to determine which URLs it may access based on rules provided by webmasters in robots.txt files. The library is released open-source to help developers build tools that better reflect Google’s robots.txt parsing and matching.
Crate robotstxt aims to be a faithful conversion, from C++ to Rust, of Google’s robots.txt parser and matcher.
Testing
$ git clone https://github.com/Folyd/robotstxt
Cloning into 'robotstxt'...
$ cd robotstxt/tests
...
$ mkdir c-build && cd c-build
...
$ cmake ..
...
$ make
...
$ make test
Running tests...
Test project ~/robotstxt/tests/c-build
Start 1: robots-test
1/1 Test #1: robots-test ...................... Passed 0.33 sec
License
The robotstxt parser and matcher Rust library is licensed under the terms of the
Apache license. See LICENSE for more information.
// Get a Presigned URLconstfile=document.getElementById('uploadInput').files[0];const{ result }=awaitkuzzle.query({controller: 's3/upload',action: 'getUrl',uploadDir: 'xen',filename: file.name});// Upload the file directly to S3constaxiosOptions={headers: {'Content-Type': file.type}};awaitaxios.put(result.uploadUrl,file,axiosOptions);// Validate the uploaded fileawaitkuzzle.query({controller: 's3/upload',action: 'validate',fileKey: result.fileKey});
{// File key in S3 bucket"fileKey": "xen/<uuid>-headcrab.png",// Presigned upload URL"uploadUrl": "https://s3.eu-west-3.amazonaws.com/...",// Public file URL after successful upload"fileUrl": "https://s3.eu-west-3.amazonaws.com/...",// TTL in ms for the URL validity and before the uploaded file deletion"ttl": 1200000}
upload:validate
Validate and persist a previsously uploaded file.
Without a call to the action, every file uploaded on a Presigned URL will be deleted after a TTL.
Request format:
{// Kuzzle API params"controller": "s3/upload","action": "validate",// File key in S3 bucket"fileKey": "xen/<uuid>-headcrab.png"}
Response result format:
{// File key in S3 bucket"fileKey": "xen/<uuid>-headcrab.png",// Public file URL after successful upload"fileUrl": "https://s3.eu-west-3.amazonaws.com/..."}
file:getUrl
Returns the public file URL.
Request format:
{// Kuzzle API params"controller": "s3/file","action": "getUrl",// File key in S3 bucket"fileKey": "xen/<uuid>-headcrab.png"}
Response result format:
{// Public file URL after successful upload"fileUrl": "https://s3.eu-west-3.amazonaws.com/..."}
file:delete
Deletes an uploaded file from S3.
Request format:
{// Kuzzle API params"controller": "s3/file","action": "delete","fileKey": "xen/<uuid>-headcrab.png"// File key in S3 bucket}
Configuration
You need to set your AWS access key in the environment: AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY.
Your access key must have the following rights: PutObject and DeleteObject.
Then in your kuzzlerc file, you can change the following configuration variable:
{"plugins": {"s3": {// AWS S3 bucket"bucketName": "your-s3-bucket",// AWS S3 region"region": "eu-west-3",// TTL in ms before Presigned URL expire or the uploaded file is deleted"signedUrlTTL": 1200000,// Redis key prefix"redisPrefix": "s3Plugin/uploads"}}}
AWS S3 Bucket
First you must configure your bucket to allow public access to uploaded files.
Go to the Permissions tab in your bucket configuration and in Bucket Policy add the following statement:
https://github.com/codex-team/codex.docs
