specify | bite sized node.js testing | Runtime Evironment library

I'm attempting to write a scraper that will download attachments from an outlook account when I specify the path to folder to download from. I have working code but the folder locations are hardcoded as below:-

I sort of need help here, honestly not sure where I went wrong, here is the full code. I am sort of new, just trying to bring back the mention user and the reason back in a message instead of doing anything with this information.

I’d be grateful for suggestions as to how to remap letters in strings in a map-specified way.

Suppose, for instance, I want to change all As to Bs, all Bs to Ds, and all Ds to Fs. If I do it like this, it doesn’t do what I want since it applies the transformations successively:

I would like to prevent a turtle from visiting a patch it has visited before. I'm developing the code, but this error appears: error: "a patch cannot access a variable of a turtle without specifying which turtle".

I'm pretty sure it's another syntax error. But, I am not able to find this error. I tried to simplify the code to make it easier for you guys to help me. Any kind of help is welcome.

I'm trying to docerize my NodeJS API together with a MySQL image. Before the initial run, I want to run Sequelize migrations and seeds to have the tables up and ready to be served.

Here's my docker-compose.yaml:

I'm trying to display data from firebase in an antd table using hooks. I created a mini version of this application with a simple bootstrap design pulling the data from firebase with:

I'm trying to figure out what the best option to solving this problem. I have an frontend application that will cater for both normal user and different company users. I want the normal user to only see the email and password fields while the company user see their respective IDP without seeing other company's IDPs.

At first, I was thinking of using a custom policy to achieve this. Basically I'll have a custom claim in the outputclaims that will specify the domain and inside my orchestration I'll have a precondition if it doesn't exist then use email and password step and skip everything but if it exist, then skip the email and password and match it to an idp selection step (if domain == companyX) use CompanyX's IDP (GSuite) or (if domain == companyY) use CompanyY's Idp (AAD). So when the company users gets to the selection page they can only see their IDP and not the others. I'm not sure how scalable that would be though.

The second option I thought was to have one ROPC policy for the normal users and use another policy for IDP selection but this time passing a domain_hint when user attempts to login in. The reason why I would go with ROPC on this option is to give user consistent user experience, normal user sees fields on the page while company user sees a single IDP button that directly sign through the domain_hint directly (Sign-Direct). Essentially having all the UI controlled by me instead of azure.

Example:

• domain_hint=CompanyX - I would have a TechnicalProfile with the domain CompanyX (GSuite)
• domain_hint=CompanyY - I would have a TechnicalProfile with the domain CompanyX (AAD)

Now this approach seem to be more intuitive but now my concern is that since ROPC uses Authorization Flow which contains refresh token while the Idp selection flow uses OpenIdConnect which doesn't contain refresh token (or at least managed by AzureB2C) it would screw up how I manage my tokens.

Is there a better way to implement this situation?

I feel like I'm missing something or I'm misinterpreting something.

I have three .snappy.parquet files stored in an s3 bucket, I tried to use pandas.read_parquet() but it only work when I specify one single parquet file, e.g: df = pandas.read_parquet("s3://bucketname/xxx.snappy.parquet"), but if I don't specify the filename df = pandas.read_parquet("s3://bucketname"), this won't work and it gave me error: Seek before start of file.

I did a lot of reading, then I found this page

it suggests that we can use pyarrow to read multiple parquet files, so here's what I tried:

I have an Aurora Serverless instance which has data loaded across 3 tables (mixture of standard and jsonb data types). We currently use traditional views where some of the deeply nested elements are surfaced along with other columns for aggregations and such.

We have two materialized views that we'd like to send to Redshift. Both the Aurora Postgres and Redshift are in Glue Catalog and while I can see Postgres views as a selectable table, the crawler does not pick up the materialized views.

Currently exploring two options to get the data to redshift.

1. Output to parquet and use copy to load
2. Point the Materialized view to jdbc sink specifying redshift.

Wanted recommendations on what might be most efficient approach if anyone has done a similar use case.

Questions:

1. In option 1, would I be able to handle incremental loads?
2. Is bookmarking supported for JDBC (Aurora Postgres) to JDBC (Redshift) transactions even if through Glue?
3. Is there a better way (other than the options I am considering) to move the data from Aurora Postgres Serverless (10.14) to Redshift.

Thanks in advance for any guidance provided.