bogus | Fake library for Ruby | Mock library

I am trying to generate 3000 fake records in C# with condition that each 1000 items will have same time stamp(update_time) in UTC milliseconds, then next 1000 will have same time stamp in UTC milliseconds. how to achieve that?

This question was previously posted as SO#67861846. But someone (non-moderator) marked it as a duplicate and closed it. It is NOT a duplicate as claimed: getResponseCode WAS indeed called but the result was no help (always 200 even for an invalid host). So, I try again...

The Question

My app regularly downloads files from a server using HttpUrlConnection(). Brief code example below:

I am trying to access a SQL database from my PHP code. I am currently using XAMPP 8.0.6 with PHP 8.0.6. This is also not working on a machine with PHP 7.4.19 and the relevant extensions installed.

Installed drivers / extensions:

• sql-srv: php_sqlsrv_80_ts_x64.dll
• sql-pdo: php_pdo_sqlsrv_80_ts_x64.dll
• OBDC drivers: 10.0.19041.1

The sqlsrv and sql-pdo are placed correctly in the php.ini. Connecting to the database using the OBDC gui, I get a successful connection.

The code that I am trying to get data from the database with is:

I built a Varnish VMOD that defines an object, which is instantiated in vcl_init and is always kept in memory, and used in individual requests.

My configuration is split up in several VCL files, that get loaded from a "master" VCL depending on some request parameters.

The master VCL also instantiates the object in question, which I want to use in another VCL. The reason why I don't instantiate the object in the same VCL I use it in, is that I have another VCL that defines some ACL-restricted routes to update the object from a data source.

E.g. master.vcl:

I am trying to setup our Rails project to use rspec. But I am getting 'No examples found' when I run rspec. How can I get rspec to run the example(s)?

I am just using the command rspec with any options or settings.

Rails: 6.0.3.4 Ruby: 2.7.2

My spec file is in the spec/requests folder and has the following content

Out of sheer curiosity I would like to know how this quoting dilemma can be fixed. I already solved the issue by circumnavigating it (I added [vcodec!*=av01] to the -f argument and simply removed the --exec part entirely). Otherwise it only worked, when there were no spaces or minus signs in the --exec argument. The culprit line is the last and the issue is at the end with the --exec argument. You can ignore the rest.

Thanks for your help on the road to enlightenment! ;-)

Often I work on Spring Boot Java applications (built with Gradle or Maven) that make network calls to external services (e.g. to external REST-like APIs). When running automated (JUnit) tests, I do not want these calls to happen, even by accident. Calling a real endpoint (even a "dev" environment one designed for testing) could affect external state, cause needless server workload, or unintentionally reveal information to the endpoint. It might also cause the test to inadvertently depend on that external resource being up, leading to build failures if the resource ever goes down while building the project, or when building the project offline.

What should typically happen with these calls is that they should either be mocked out to do nothing or should point to a service on the same machine (e.g. a WireMock endpoint on localhost spun up by the test, or a local Docker container spun up by the test using Testcontainers).

What I tend to in these situations is create a test-specific bean definition profile that overrides all HTTP endpoints with something obviously bogus that is guaranteed not to route somewhere, e.g. http://example.invalid/bookSearch. That way, if a developer misses mocking out or changing the endpoint in a test, it won't call a real one and trigger real side effects.

However, this approach is potentially error prone, and oversights in the implementation or with future changes could cause network calls to still be made. Examples include:

1. A new endpoint could be added by a developer without remembering to or knowing that they needed to override the test route
2. An endpoint could be missed being overridden in the first place
3. A third party library could be making a request that the developer didn't know about or wasn't accounted for

This is mostly a concern with Spring integration tests that spin up some or all of the environment (e.g. using @SpringBootTest or @ExtendWith(SpringExtension.class)). However, this could conceivably apply to a unit test if a component used something as a non-required constructor argument that connected to the network, or if a developer passed in a real network-connecting component where they should have used a mock or something connecting to localhost.

It occurs to me that there might be a more bullet-proof solution to this scenario. For instance, perhaps there is a way to tell the JVM or its underlying HTTP/FTP/etc. libraries to block all external network traffic.

Is there a way to prevent nonlocal network access in Java Spring Boot JUnit tests, or otherwise provide a guarantee that external network endpoints will not be called?

In my Rails app users can create their own email templates. I need to validate that only certain placeholders can be used, like to:

I'm learning Dart, and I'd like to have a method similar to let in Kotlin.

I'd like to use it as: