IP | Country | PORT | ADDED |
---|---|---|---|
50.169.222.243 | us | 80 | 43 minutes ago |
115.22.22.109 | kr | 80 | 43 minutes ago |
50.174.7.152 | us | 80 | 43 minutes ago |
50.171.122.27 | us | 80 | 43 minutes ago |
50.174.7.162 | us | 80 | 43 minutes ago |
47.243.114.192 | hk | 8180 | 43 minutes ago |
72.10.160.91 | ca | 29605 | 43 minutes ago |
218.252.231.17 | hk | 80 | 43 minutes ago |
62.99.138.162 | at | 80 | 43 minutes ago |
50.217.226.41 | us | 80 | 43 minutes ago |
50.174.7.159 | us | 80 | 43 minutes ago |
190.108.84.168 | pe | 4145 | 43 minutes ago |
50.169.37.50 | us | 80 | 43 minutes ago |
50.223.246.238 | us | 80 | 43 minutes ago |
50.223.246.239 | us | 80 | 43 minutes ago |
50.168.72.116 | us | 80 | 43 minutes ago |
72.10.160.174 | ca | 3989 | 43 minutes ago |
72.10.160.173 | ca | 32677 | 43 minutes ago |
159.203.61.169 | ca | 8080 | 43 minutes ago |
209.97.150.167 | us | 3128 | 43 minutes ago |
Simple tool for complete proxy management - purchase, renewal, IP list update, binding change, upload lists. With easy integration into all popular programming languages, PapaProxy API is a great choice for developers looking to optimize their systems.
Quick and easy integration.
Full control and management of proxies via API.
Extensive documentation for a quick start.
Compatible with any programming language that supports HTTP requests.
Ready to improve your product? Explore our API and start integrating today!
And 500+ more programming tools and languages
When working with OpenXML, you may need to parse date values from date-formatted cells in Excel spreadsheets. The date values in OpenXML are represented as numeric values, and you need to convert these numeric values to DateTime objects.
Here's an example using C# and the DocumentFormat.OpenXml
library to parse date values from an Excel spreadsheet:
Install the Open XML SDK:
If you haven't already, install the DocumentFormat.OpenXml
NuGet package:
nuget install DocumentFormat.OpenXml
Write the Parsing Code:
Create a C# script or add the following code to your project:
using System;
using DocumentFormat.OpenXml.Packaging;
using DocumentFormat.OpenXml.Spreadsheet;
class Program
{
static void Main()
{
string filePath = "path/to/your/excelfile.xlsx"; // Replace with the path to your Excel file
// Call the function to parse dates from the Excel file
ParseDatesFromExcel(filePath);
}
static void ParseDatesFromExcel(string filePath)
{
using (SpreadsheetDocument spreadsheetDocument = SpreadsheetDocument.Open(filePath, false))
{
WorkbookPart workbookPart = spreadsheetDocument.WorkbookPart;
SharedStringTablePart sharedStringTablePart = workbookPart.GetPartsOfType().FirstOrDefault();
if (sharedStringTablePart != null)
{
foreach (WorksheetPart worksheetPart in workbookPart.WorksheetParts)
{
foreach (Cell cell in worksheetPart.Worksheet.Descendants())
{
if (cell.DataType != null && cell.DataType.Value == CellValues.SharedString)
{
int sharedStringIndex = int.Parse(cell.InnerText);
string sharedStringValue = sharedStringTablePart.SharedStringTable.Elements().ElementAt(sharedStringIndex).InnerText;
if (DateTime.TryParse(sharedStringValue, out DateTime parsedDate))
{
Console.WriteLine($"Parsed Date: {parsedDate.ToShortDateString()}");
}
else
{
Console.WriteLine("Not a valid date format.");
}
}
else if (cell.CellValue != null)
{
if (DateTime.TryParse(cell.CellValue.Text, out DateTime parsedDate))
{
Console.WriteLine($"Parsed Date: {parsedDate.ToShortDateString()}");
}
else
{
Console.WriteLine("Not a valid date format.");
}
}
}
}
}
}
}
}
|
Replace "path/to/your/excelfile.xlsx"
with the actual path to your Excel file.
Run the Code:
This code uses the SpreadsheetDocument
class from the DocumentFormat.OpenXml.Packaging
namespace to open the Excel file, and it iterates through the cells to parse and print date values. It checks if the cell contains a shared string (string stored in the shared string table) or a direct value. If it's a valid date, it parses and prints it. Adjust the code according to your specific needs and Excel file structure.
To run GUI autotests in GitLab CI\CD using Docker, Selenium, and PyTest, you can follow these steps:
1. Create a .gitlab-ci.yml file in the root directory of your project. This file will define the pipeline and the jobs for your CI\CD process.
2. Configure the pipeline to use the appropriate image for your tests. In this case, you can use a Python image with the required dependencies installed.
3. Define the before_script section to set up the environment for the tests, including installing the necessary packages and downloading the required drivers for Selenium.
4. Define the test job to run the PyTest tests using the Selenium WebDriver.
Here's an example of a .gitlab-ci.yml file:
stages:
- test
variables:
SELENIUM_CHROME_DRIVER: '102.0.5005.62'
SELENIUM_FIREFOX_DRIVER: '0.26.0'
image: python:3.8
cache:
paths:
- .venv
- requirements.txt
before_script:
- apt-get update -qq
- apt-get install -y --no-install-recommends \
build-essential \
wget \
xvfb \
xvfb-run
- pip install --upgrade pip
- pip install --quiet --upgrade pytest
- pip install --quiet selenium
- pip install --quiet webdriver-manager
- wget https://github.com/SeleniumHQ/selenium/releases/download/v${SELENIUM_CHROME_DRIVER}/chromedriver_linux64.zip
- unzip chromedriver_linux64.zip chromedriver
- wget https://github.com/SeleniumHQ/selenium/releases/download/v${SELENIUM_FIREFOX_DRIVER}/geckodriver-v${SELENIUM_FIREFOX_DRIVER}
- mv geckodriver-v${SELENIUM_FIREFOX_DRIVER} geckodriver
test:
stage: test
script:
- pytest tests/
tags:
- selenium
artifacts:
reports:
- html
only:
- master
- merge_requests
This .gitlab-ci.yml file defines a single stage called test that runs the PyTest tests in the tests/ directory. The before_script section installs the necessary dependencies, downloads the Selenium WebDriver for Chrome and Firefox, and sets up the environment for running the tests.
The tags: - selenium line ensures that the job runs on a runner with the selenium tag, which should have the appropriate Selenium WebDriver installed. The artifacts: reports: - html line enables the generation of HTML reports for the test results.
The only: - master - merge_requests line specifies that the tests should be run on every commit to the master branch and on every merge request.
Once you've set up the .gitlab-ci.yml file, commit and push it to your repository. Then, create a new merge request or push to the master branch to trigger the CI\CD pipeline and run the GUI autotests using Docker, Selenium, and PyTest.
To check if a proxy server is working, you can follow these steps:
1. Open your web browser and go to a website that is not blocked by your proxy server.
2. In the address bar, enter the proxy server address and port number in the following format: http://proxy-server-address:port-number
3. Press Enter and wait for the page to load. If the page loads successfully, it means your proxy server is working.
4. If the page does not load or you see an error message, it means your proxy server is not working or is blocked by the website you are trying to access.
Alternatively, you can use online tools like Proxy Checker (https://www.proxychecker.com/) to test your proxy server. These tools will provide you with information on whether your proxy server is working or not.
Before you change your proxy server, you should decide what kind of proxy you would like to install. There are a lot of choices, depending on your needs. Every buyer, when buying a proxy server, is given all the necessary information with the data for access - username and password, port, IP address. Without these data, you can't install and configure the proxy.
Open the browser settings and go to the "Advanced" section. Click on "System" and then, in the window that opens, click on "Open proxy settings for computer". A window will appear in front of you, showing all the current settings. Another way to find out the http proxy is to download and install the SocialKit Proxy Checker utility on your computer.
What else…