Tag: WebDev

I registered a for a developer account on https://jackhenry.dev/portal/, however when creating a Test User for a banno plugin, I get the following error: "There was a problem generating your test user". Am I missing a step? According to the instructions I'm following, the user should be created after clicking the Generate user button. Any ideas to troubleshoot further (tried clearing cache, login/logout, coming back later, etc.). Screen shot of the error

I am currently using IntelliJ IDEA to run Kotlin Notebooks to learn Kotlin. Unfortunately, even for extremely simple and easily tracable code, IntelliJ will only show about 50% of the printed lines (though the lines being skipped are repeatable). Toggling between Run in Separate Process and Run in IDE Process doesn't do much except sometimes change the lines that the IDE does show. Furthermore, as shown, it sometimes recognizes the new line that is added by println and sometimes it skips it too. Lastly, I am using the default settings, and installed everything via the IntelliJ installer with an Unlimited Student License on a M4 MacBook Pro.

Suppose I have a procedure like this: procedure DoSomething; asm .PARAMS 11 // This will auto-generate "push rbp + sub rsp,$60 + mov rbp,rsp" // ... end; Suppose I need to return from it in the middle of things. Like "if CheckFailed then Exit;". How do I do this correctly? Obviosly, the simple ret will not work correctly. I can hard-code it as: lea rsp,[rbp+$60] pop rbp ret Is there a better way? I mean: what is the purpose of .PARAMS, if I can just write push/pop directly? And if .PARAMS is necessary/required, how do I know the offset for the lea rsp,[rbp+???] instruction?

After upgrading to Compose Multiplatform 1.10.0 (beta), my preview annotations from JetBrains no longer resolve. I previously used: import org.jetbrains.compose.ui.tooling.preview.Preview After updating, I get errors like: Unresolved reference: Preview or the IDE no longer recognizes the preview annotation in commonMain.

After upgrading to Compose Multiplatform 1.10.0 (beta), my project no longer resolves compose.runtime. I previously had dependencies like: implementation(compose.runtime) implementation(compose.foundation) implementation(compose.material3) implementation(compose.ui) implementation(compose.components.resources) implementation(compose.components.uiToolingPreview) After updating, I get errors like: Unresolved reference: runtime and Could not resolve compose.runtime Nothing else in the project changed.

I am building a Node.js/Express backend using TypeScript, Prisma, and PostgreSQL (Supabase) and encountering a weird issue where this.prismaClient.user.findUnique throws an Invalid invocation error. If I comment out findUnique, the subsequent this.prismaClient.user.create throws the exact same error. It seems like the Prisma Client instance is not behaving correctly inside my Repository class. The Error Log: PrismaClientKnownRequestError: Invalid `this.prismaClient.user.findUnique()` invocation in D:\PixelMatch\backend\src\modules\auth\repositories\user.repository.prisma.ts:13:47 10 } 11 12 async findByEmail(email: string): Promise<User | null> { → 13 const user = await this.prismaClient.user.findUnique( ... code: 'ECONNREFUSED', clientVersion: '7.3.0' Note:

new_test_working.py # Pipeline: # 1) CDA XML + client XSL -> XHTML (saved) # 2) XHTML + mapper XSL -> XSL-FO (saved) # 3) (optional) FOP -> PDF Your post appears to contain code that is not properly formatted as code. Please indent all code by 4 spaces using the code toolbar button or the CTRL+K keyboard shortcut. For more editing help, click the [?] toolbar icon. <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format"> <!-- Footer parameters from Python --> <xsl:param name="patientName" select="''"/> <xsl:param name="dob" select="''"/> <xsl:param name="dateOfVisit" select="''"/> <xsl:output method="xml" indent="yes" encoding="UTF-8"/> <!-- ===

version: '1.33.1' python version: 3.11.13 os: ubuntu 22.04.5 I use .extend() to append new rows to an existing dataframe whose .n_chunks('all') is all 1, after .extend() called and new row appended, checking .n_chunks('all'), some of the dataframe columns n_chunk becomes 2 instead of 1. My understanding is that extend will make sure the new row copied to the original dataframe's memory location as one according to polars documentation. Is this expected behavior? DataFrame.extend(): Extend the memory backed by this DataFrame with the values from other. Different from vstack which adds the chunks from other to the chunks of this DataFrame,

Confusion with how a pointer relocation works when the pointer belongs to a struct (and not just exactly that. Also if the presence of a struct alters in any way the straightforwardness of relocation). How to manually calculate the relocation. I have a question not solved from the lecturers on a technical-research presentation. They wanted to mimic ld (crafting their own linker/loader) to produce a PIE. Slide where they explain the issue (translated. Literal): Relocations in .data.rel are not as easy to calculate (figure out) when there are structs (C structs) ("when there are structs" == "when structs are present in the code").       If the entire section is rebased (== resolved address base), fields that are already well calculated are broken To this day we do not know how ld calculates this correctly We don't care for now, how it does &

I want to create a column that labels each row as belonging to a group based on the date in one of the other columns. I want to be able to set the time window that define groupings, eg within 1 week or 2 weeks of each-other. The starting point is the first date and groups run forwards in time from there. The data looks like this (the values column doesn't matter here) dates <- c("2025-01-19", "2025-01-19", "2025-01-20", "2025-02-12", "2025-02-13", "2025-04-12", "2025-04-12", "2025-05-01", "2025-05-28", "2025-05-29") dates <- as.Date(dates) values <- sample(1:10) df <- data.frame(dates, values) df So you would order the rows by the dates column. Next I would want to set my date window threshold to define the groups, eg 14 days: