dig | Faceted search engine for domain-specific exploration | Frontend Framework library

I don't really know where the error is, for me, it's still a mystery. But I'm using Laravel 8 to produce a project, it was working perfectly and randomly started to return this error and all projects started to return this error too. I believe it's something with Redis, as I'm using it to store the system cache. When I go to access my endpoint in postman it returns the following error:

my python file in which I work is contained in the following path '/Users/pycar/Documents/Srett/Python/', In this same space I have a folder that contains 8 other folders that all contain a csv that I want to import via panda because it's a database, the problem is that most of the codes found do not work (It says that the file is named 'month' and that the 8 folders are named by the first 8 months of the year then it does not matter what the names of the csv inside.

I would like to make a loop that digs into 'month' and goes into each folder (so january february etc...) and import the csv that is contained inside (with a read.csv).

for a little more visibility tell you that the file my_python is my notebook and that it is in the same folder as month which contains what I gave you

my_python

month-> january -> jan.csv

month-> February -> feb.csv

month-> March -> mar.csv

month-> April -> apr.csv

month-> May -> may.csv

month-> June -> jun.csv

month-> july -> jul.csv

month-> August -> Aug.csv

How can i proceed ?

I have an app which compiles and runs fine in older Macs with Intel processors in physical devices & iOS simulators.

The same app also compiles and runs fine from newer Apple Silicon Mac with M1 processor with physical iPhone devices, but, it refuse to be compiled for iOS simulator.

Without simulator support, debugging turn around time gets gets really long so I am trying to solve this issue. Not to mention Xcode preview feature isn't working either which is annoying.

The first error that I encountered without making any changes (but moved from Intel Mac to M1 Mac) is like below.

building for iOS Simulator, but linking in dylib built for iOS, file '/Users/andy/workspace/app/Pods/GoogleWebRTC/Frameworks/frameworks/WebRTC.framework/WebRTC' for architecture arm64

The Cocoapods library that I am using is GoogleWebRTC, and according to its doc, arm64 should be supported so I am baffled why above error is getting thrown. As I have said before, it compiles fine in real device which I believe is running on arm64.

According to the doc..

This pod contains the WebRTC iOS SDK in binary form. It is a dynamic library that contains the armv7, arm64 and x86_64 slices. Bitcode is not supported. Our currently provided API’s are Objective C only.

I searched online and it appears there appears to be 2 workarounds for this issue.

1. The first one is by adding arm64 to Excluded Architectures
2. The second option is to mark Build Active Architecture Only for Release build.

I don't exactly understand if above are necessary even when I am compiling my app on M1 Mac which is running under arm64 architecture, because the solution seems to be applicable only for for Intel Mac which does not support arm64 simulator, as for Intel Mac, simulators might have been running in x86_64, not with arm64, so solution #1 is not applicable in my case.

When I adapt the second change only, nothing really changes and the same error is thrown.

When I make both changes and tried building, I now get the following 2nd error during build. (not really 100% sure if I solved the 1st error / I might have introduced 2nd error in addition to 1st by adapting two changes)

Could not find module 'Lottie' for target 'x86_64-apple-ios-simulator'; found: arm64, arm64-apple-ios-simulator

The second library that I am using is lottie-ios and I am pulling this in with a swift package manager. I guess what is happening is that because I excluded arm64 in build setting for iOS simulator, Xcode is attempting to run my app in x86_64. However, library is not supported running in x86_64 for some reason, and is throwing an error. I don't have much insights into what dictates whether or not library can run in x86_64 or arm64 so I couldn't dig to investigate this issue.

My weak conclusion is that GoogleWebRTC cannot be compiled to run in iOS simulator with arm64 for some reason (unlike what its doc says), and lottie-ios cannot be compiled to run in iOS simulator with x86_64. So I cannot use them both in this case.

Q1. I want to know what kind of changes I can make to resolve this issue...

The app compiles and runs perfectly in both device & simulator when compiled from Intel Mac. The app compiles and runs fine in device when compiled from Apple Silicon Mac. It is just that app refuse to be compiled and run in iOS simulator from Apple Silicon Mac, and I cannot seem to figure out why.

Q2. If there is no solution available, I want to understand why this is happening in the first place.

I really wish not to buy old Intel Mac again just to make things work in simulator.

I am digging deeper to kubernetes architecture, in all Kubernetes clusters on-premises/Cloud the master nodes a.k.a control planes needs to be Linux kernels but I can't find why?

How SSL works is well know as it's quite widely used and described well every where. In short - SSL involves

1. Verifying server authenticity by client by verifying the servers X.509 certificate.
2. Then arriving at a symmetric key using diffie-hellman key exchange algorithm.

But I am not sure what happens withsecurity.protocol=SASL_SSL. Clients and Server communication of few technologies like Kafka etc rely on this security protocol as one of the option. Here I am worried about the point 1 above. If i get a wrong broker address (as a trick ) from some one, does SASL_SSL verify the server certificate or not is my question. If it does, then I can be sure that the received broker is not genuine and my application will not publish or subscribe to messages from this server and my data is safe.

Edit 1: Following @steffen-ullrich answer and comments And little more dig, i see below. Looks like the certificate validation is happening when used through chrome and probably its loaded in the cacerts too. So the java code is able to authenticate the server.. so seems ok..

Edit 2: Right the certificates DST and ISRG are preloaded in the JDK 11 cacerts, so the client is able to authenticate the server as commented by Stephen.

I'm looking for anything that can help me deviate string GetRTTIClassName(IntPtr ProcessHandle, IntPtr StructAddress). The function would use another (third-party) app's process handle to get names of structures located at specific addresses in its memory (should there be found any).

All of RTTI questions/documentation I can find relate to it being used in the same application, and have nothing to do with process interop. The only thing close to what I'm looking for is this module in Cheat Engine's source code (which is also how I found out that it's possible in the first place), but it has over a dozen of nested language-specific dependencies, let alone the fact that Lazarus won't let me build it outside of the project context anyway.

If you know of code examples, libraries, documentation on what I've described, or just info on accessing another app's low-level metadata (pardon my French), please share them. If it makes a difference, I'm targeting C#.

Edit: from what I've gathered, the way runtime information is stored depends on the compiler, so I'll mention that the third-party app I'm "exploring" is a MSVC project.

As I understand, I need to:

1. Get address of the structure based on address of its instance;
2. Starting from structure address, navigate through pointers to find its name (possibly "decorated").

I've also found a more readable C# implementation and a bunch of articles on reversing (works for step 2), but I can't seem to find step 1.

I'll update/comment as I find more info, but right now I'm getting a headache just digging into this low-level stuff.

How can I send https request from one deployment to another deployment using AWS lightsail's private domain?

I've created two AWS Lightsail Container deployments using two docker images. I'd like to send https request from one image deployment ("sender") to another image deployment ("receiver"). This works fine when the receiver's public endpoint is enabled. However, I don't want to expose this service to the public but instead route traffic using AWS Lightsail's private domain.

My problem is when I try and send https request from "sender" to the "receiver"'s private domain (.service.local:) I get https://.service.local:52020/tester/status net::ERR_NAME_NOT_RESOLVED on the "sender"'s html page. According to the Lightsail docs (section "Private domain") this should be accessible to my "Lightsail resources in the same AWS Region as your service".

I've found a similar Question & Answer in stackoverflow. I tried this answer using my region but failed because Lightsail container required https while .service.local required http. After creating a Amazon Linux instance, I succeeded making http request but failed to make https request. (screenshot below). In the meantime, Lightsail strictly asks you to use https.

If I force to send http request from https webpage, chrome generates Mixed content: The page at ... was loaded over HTTPS but requested an insecure ... error. I can go around the https problem by using next.js api routes, but this doesn't feel secure because next.js api routes are publicly accessible.

Is there anything that I may be missing here?

Things I've verified:

• The image is up and running and works fine when connecting to it using the public domain
• I'm running both instance and container service in the same region

Thank you in advance.

Some screenshots

• Running dig inside docker's entrypoint script

• Error message when sender sends http request to receiver

In this example, editor is created inside Shadow Root.

https://codepen.io/artemiusgreat/pen/XWMPdWG

The main concern so far is that inline formatting doesn't work when initiated from Toolbar module by clicking Bold or Italic buttons on the panel.

The reason is that window.getSelection always returns empty selection inside the Shadow Root.

The good thing is that it somehow works when inline formatting is initiated from Keyboard module by pressing CTRL+B or CTRL+I.

I'm digging into the code, but if somebody already resolved this I would appreciate some guidance.

I am trying to use the binance_async library, tokio, and futures to make concurrent orders to Binance. (See notes at the end of this question.)
The binance_async functions I'm using return a binance_async::error::Result> type. I am facing the following issue, illustrated in these 2 examples:

1. Say I'm trying to do this: