MBP | A management platform for IoT environments and applications

Running Android Instrumented Tests, the gradle task :app:connectedDebugAndroidTest now prints a red WARNING after a successful test run:

I have an issue regarding the synchronisation of different agents.

So I have a shared context with a BaseAgent class as the tutorial suggested for the case where we have more than 1 agent type in the same context. Then I have 4 more agent classes which are children of the Base Agent Class. For each of them I have the necessary serialisable agent packages and in my model class I also have specific package receivers and providers for each one of them.

All those agents are sharing a discrete spatial projection of the form:

I recently had a catastrophic hard drive failure and I had not pushed all of my recent commits to a remote repository (I have learned my lesson). Fortunately I did have a copy of most of my latest work.

I recreated my local environment (I thought correctly but maybe not) and attempted to start the project with the files. When I run "pipenv shell" the env appears to activate and running "git branch" does show the two branches. However when I ran "python manage.py migrate" I received the following error:

I am able to access the private member variable of the class shown in below code directly using an object instance (pointer to object). As per my understanding private members should not be accessible. Can someone please help to explain the reason behind this behaviour ?

You will need to download fonts.zip and extract it in the same folder as the code for the examples to run.

The purpose of this code is to generate random text, render and save text as image. The code accepts letters and numbers which are the populations of letters and numbers respectively to generate text from. It also accepts character_frequency which determines how many instances of each character will be generated. Then generates a long string, and split it to random size substrings stored in TextGenerator.dataset attribute which results from TextGenerator.initialize_dataset.

Ex: for letters = 'abc', numbers = '123', character frequency = 3, 'aaabbbccc111222333' is generated, shuffled, and split to random size substrings ex: ['a312c', '1b1', 'bba32c3a2c'].

Then each word will be rendered and saved as image which results from TextGenerator.save_images which is the subject of this question.

There is executor parameter which will be concurrent.futures.ThreadPoolExecutor and concurrent.futures.ProcessPoolExecutor passed to TextGenerator in the examples shown below for demonstration purposes.

What is the issue?

The more character_frequency is increased, the longer the dataset stored in TextGenerator.dataset will be however, it shouldn't affect performance. What actually happens: the more character_frequency, the more time TextGenerator.save_images requires to finish with concurrent.futures.ProcessPoolExecutor. On the other hand, with everything remaining the same, and passing concurrent.futures.ThreadPoolExecutor instead, time required is constant, and is not affected by character_frequency.

I'm getting this error after trying to test my api on Postman.

employeemanager its a MySQL database.

Here is my model

Trying to install Python 3.10.0 on MacOS 11.6 (Intel) with pyenv 2.1.0 (from homebrew) fails with:

For argument's sake, let's say that a browser allows 4GB of memory in WebAssembly applications. Ignoring compression and other data-storage considerations, if a user had a 3GB local csv file, we could query that data entirely in-memory using webassembly (or javascript, of course). For example, if the user's data was of the following format:

Then in a few lines of code we could do a basic algorithm to filter to ID=2, i.e., the SQL equivalent of SELECT * FROM table WHERE id=2.

Now, my question is whether it's possible in any browser (and possibly with experimental flags and/or certain user preferences selected) such that a query could be done on a file that would not fit in memory, even if properly compressed. For example, in this blog post, a ~500GB file is loaded and then queried. I know that the 500GB of data is not loaded entirely in memory, and there's probably a column-oriented data structure so that only certain columns need to be read, but either way the OS has access to the file system and so files much larger than available memory can be used.

Is this possible to do in any way within a webassembly browser application? If so, what would be an outline of how it could be done? I know this question might require some research, so when it's available for a bounty I can add a 500-point bounty to it to encourage answers. (Note that the underlying language being used is C++-compiled-to-wasm, but I don't think that should matter for this question.)

I suppose one possibility might be along the lines of something like: https://rreverser.com/webassembly-shell-with-a-real-filesystem-access-in-a-browser/.

I wrote a screensaver in Swift.

Although I had set the macOS Deployment Target to macOS 10.13, it failed to run on an x86_64 Mid 2010 Mac Pro running macOS High Sierra 10.13.6.

Meanwhile, it runs fine on my arm64 2020 MBP M1 with macOS Big Sur 11.5.2, and on an x86_64 2019 MacBook Air with macOS Catalina 10.15.6.

The screensaver installs fine on all machines, but on the machine running High Sierra it says that the screensaver is not compatible.

The error message shown is as follows ("vibe" is the name of the screensaver that I made. So anyone else running across this same problem will see a similar message but with the name of their own screensaver in place of that of course):

You cannot use the vibe screen saver with this version of macOS.

Please contact the vendor to get a newer version of the screen saver.

I am wondering if there is a way to automatically figure out if there are any APIs or other features that my code is using which were not available in macOS 10.13. And also I am wondering if it is usual that you can build for a given macOS Deployment Target and then when you try to run the program on a machine that is within the range that should be supported, the program will not run after all. I had thought that there would be a build time error to build for a macOS Deployment Target if the built program will not run on it.

I am using Xcode 12.5.1 running on my MBP M1, macOS 11.5.2, and as mentioned I am building for macOS Deployment Target set to macOS 10.13. The screensaver runs fine on both Intel with macOS 10.15 and ARM with macOS 11.5. I am using Swift Language Version Swift 5.