Password recovery

A bit embarrassed to post this, but I have forgotten my password. Nowhere can I find a password recovery process. Searching the issues I see mention of a recovery process but I cannot find any thing in the UI
Help?

There is a Forgotten your password? link on the login form.

@willpower232  thanks. Found the password recovery feature. But when I try use it I get the msg "We're sorry, but something went wrong. If you are the application owner check the logs for more information."
I have no idea where to find the logs to check what the issue is. Hoping you can assist

You'll have to look at the logs but the most likely cause of this problem is not configuring the smtp details in postal.yml so it can't send emails https://github.com/postalhq/postal/blob/2595481b266199d8e29347dea2764f2c10202805/config/postal.defaults.yml#L104-L110

Sorry opening this thread again,
If you forgot your password and reset password showing "We're sorry, but something went wrong. If you are the application owner check the logs for more information."
Then follow the below steps.

Login to Server

RUN postal stop
(WORNING IT WILL SHUT DOWN YOUR POSTAL SMTP)

RUN postal make-user

Enter New Admin Information | Make sure your not using same email that have first/other admin email

Once finish entering all the information RUN postal start

Login to your website using newly create admin

Thanks!

Just an FYI, you should not need to stop Postal in order to run make-user again, there should be no issue in keeping Postal running.
If you aren't able to reset your password, I direct your attention to my previously final message on the matter above https://github.com/postalserver/postal/issues/1231#issuecomment-720376655


RFC: Update OSTEP prerequisites

Problem:
The prerequisites listed for OSTEP do not reflect the background knowledge needed for the course.
Duration:
1 month
Background:
The current listed prerequisites are "algorithms, familiarity with C is useful".
I took all of Core Theory before returning to OSTEP, but I found that none of the material from the algorithms courses was necessary to understand the course. I know real-world operating systems make heavy use of data structures and algorithms, but that's not the case in OSTEP. The lectures and homework assignments treat operating system concepts very generally, and the projects (where those concepts get applied) do not require any algorithms knowledge to complete them.
I recommend removing algorithms from the list of prerequisites. One advantage would be that students could now move through the OSSU curriculum from top to bottom as listed instead of jumping around between Core Systems and Core Theory. It might also make it easier for students to finish Core Systems sooner, as an integrated unit. One disadvantage I can think of is that the algorithms sequence might provide additional coding maturity needed before tackling OSTEP.
On the other hand, OSTEP has other prerequisites that aren't listed on the OSSU page. The OSTEP instructor explicitly states some of them in one of the early lectures: he assumes that students have taken a course on x86 architecture, are comfortable reading (but not necessarily writing) x86 assembly, and have some experience using systems programming tools like Makefiles, gcc flags, linker scripts for ld, and the objcopy and objdump utilities. I think it's possible for students to get by if they've taken Nand2Tetris, but familiarity with the above prerequisites would certainly make the course much easier.
The course also assumes deep knowledge of C, which is not reflected in the phrase "familiarity with C is useful". For example, the instructor identifies the initial-utilities project (where you implement shell utilities like grep, cat, zip, and unzip) as an indicator of a student's readiness to take the course; he even recommends that students (at UWisconsin, where the course was originally taught) who take longer than 60 minutes to complete it should schedule an appointment with him if they want to continue in the course.
Overall, my solutions to the assignments required C features like #pragma directives, bit-field structs (and bitmasks and bitwise arithmetic in general), POSIX threads and locks, function-like macros, function pointers, extern/inline/static keywords, C preprocessor directives in assembly files, etc. Students are expected to identify some C standards (e.g., that signed integer overflow is undefined behavior while unsigned integer overflow is defined and just wraps around back to zero). None of these were covered in the course or book (except for threads and locks, but the assignments assumed experience using them before the lectures or book discussed their implementations). They also weren't covered in CS 50. I found most of these features in the "advanced" chapters of C books I had read before taking this class, and I don't believe I would have been able to finish the course if I didn't already have a good amount of experience in C.
That said, it's definitely not my intention to say that OSTEP is a poor course for OSSU. It's still the best online OS course I've seen so far (and much easier than Hack the Kernel), with a complete set of lectures, a free textbook, and complete assignments (though admittedly, the tests are occasionally buggy and the assignments repo isn't maintained).
But I do believe the listed prerequisites should reflect the additional knowledge the course requires, especially since that knowledge isn't provided by other courses in OSSU, so I would recommend adding language identifying these prerequisites. One obvious drawback is that acquiring the required knowledge might add to the time it takes for OSSU students to complete the curriculum, but I think that's outweighed by the advantage of being frank with students up-front about the prereqs. I think that once students have met those prereqs, OSTEP should be about as challenging as any other OSSU course; without them, it becomes overwhelmingly difficult. (To my knowledge, only one other OSSU student has completed the OSTEP course, compared to the dozens who have completed Nand2Tetris.)
One last note: I definitely agree that OSSU shouldn't add courses to the curriculum just to teach a specific language, but I don't think the prerequisites should link students to hackr.io either. That might be great for other languages, but I think C is sort of unique due to its many pitfalls and the ease with which one can introduce serious bugs and security vulnerabilities in C code. I've found errors and insecure coding practices in the C tutorials listed on hackr.io as well as websites like GeeksforGeeks and TutorialsPoint. I recommend either removing the link altogether, or alternatively, pointing it to a list of recommended C resources that we know are (relatively) good/safe.
Proposal:

Remove algorithms from the prerequisites for OSTEP.
Add Nand2Tetris as a prerequisite.
Add the phrase "familiarity with x86 architecture and assembly is useful".
Replace the phrase "familiarity with C is useful" with something that more accurately reflects the depth of C knowledge required for the course, e.g. "advanced C required" or "extensive experience in C required".
Remove the link to hackr.io from the prerequisites.

After these changes, the prerequisite list might look something like this: "Nand2Tetris, extensive C experience; familiarity with x86 assembly is useful".
Alternatives:

Instead of adding the x86 prereq, OSSU could add a link to a short course or resource on x86 architecture/assembly to fill in the missing knowledge after Nand2Tetris.
Instead of just removing the hackr.io link, it could be replaced with a link to (good/safe) C resources, perhaps a section in extras/readings.md.

If either of these alternatives is preferred, I'd be happy to contribute the resources that I found useful for OSTEP.

I disagree with the proposal, but completely agree with the general, overall ideas. The proposal will lead to even more confusion, and complaints. Learners will ask "how am I supposed to meet these prerequisites? They are not covered by the curriculum". Or "Am I supposed to learn all these other things before I can even take this course? How long would that take? Why does it say 12 weeks then?" and so on... I can't remember how many hundreds of "prerequisites" questions I must have answered. Obviously they are not going to find these RFCs and read them.
So it's not really this proposal's fault, it's the format we have itself that's the problem. The main issue with the "Prerequisites" column in the whole curriculum is that it's very short and creates a lot more confusion than it helps. I'd like us to do away with that column altogether and replace them with "course context" pages. @hanjiexi suggested this to me some time ago (I can't even find them on Github anymore). I can provide long, detailed explanations for many, if not most, courses.
OSTEP is probably the one course that requires detailed contextual explanation the most, out of all courses. I see learners just waltz in to this course all willy-nilly, like it's any other online course, and go like "oh look it's the first project! OK let's go!" then running into so many issues, wasting a lot of time and suffering pain. THIS COURSE IS NOT NORMAL. It's an exceptionally hard topic. Moreover, some of the tools and knowledge required is near impenetrable: you mentioned how hard it is to find a decent C learning resource, or learn all the "dark arts" and technical details for low-level code. Not to mention that it's basically cobbled together from bits and pieces here and there. We still don't have any idea how to do or test some of the projects, because the author does not maintain them. (Also for some reason, along with CS50 and Nand2Tetris, this course seems to attract people from all over the internet who never heard of OSSU before, or did any of the prior courses, to our Discord.)
As such, OSTEP would be the perfect starting candidate to take a crack at creating course context pages.
I think the best solution would be like this: @palladian1 write a long article, explaining all the details you listed here. I think you already have most of the relevant material written down. It should start by saying that this course is unlike others. It would have all the relevant information, with links to resources. You can say "this is the best we think there is" or "this is the best we could find/recommend so far". It can include a realistic discussion of how long it would take to learn all these things properly, and maybe suggest that there is no shame in just reading the textbook and doing the textbook homeworks and moving on, with the projects being more difficult and time consuming optionals, linking to your xv-annotated. You can mention the great benefits of doing the projects, and that the "prerequisites" are significantly lower if one decides not to do the projects.
Then we replace the "prerequisites" with a link to that article, which can be a Markdown file in a folder, like contexts. This can begin the slow phasing out of "prerequisites" and the phasing-in of "course context pages". Sorry if this feels like hijacking the issue and creating a lot more work for you, but I think this is the best choice. If we're gonna do it, let's do it properly.

I like the alternative proposal by @spamegg1 better overall!
My original proposal was trying to address the problem that the current OSSU curriculum doesn't fully prepare students for OSTEP; the biggest barrier is the C knowledge, but there's also a gap between OSSU's intro systems course (Nand2Tetris) and a systems course like CS:APP that covers all the other prereqs besides C that OSTEP expects students to know. But a "course context" page would let us explain that in more detail, plus we could add links to resources there. We could even host our own version of the OSTEP projects like @spamegg1 and I have been working on, with improved documentation and guides to running the tests on machines besides the UWisconsin lab computers.
I'd be super happy to start working on a "course context" page with all the notes and resources I've collected so far!
I do disagree on two points:
First, I actually don't think OSTEP is much harder than other OSSU courses, if the prerequisites have been met. At first, I found myself struggling with the x86-specific details, looking up hardware specs in old Intel manuals to try to make sense of what was happening in the code. I had to read manpages for objcopy and objdump, read Makefile tutorials... it was a lot to learn, and that was just the beginning in order to then be able to understand the actual topics being taught in the course.
But my opinion changed completely when I found the CS:APP course: it turns out that every single one of those aspects I had struggled with were taught there, in a really clear way. It made me realize that the real problem isn't that OSTEP is impossible because you're expected to figure out x86 assembly function call conventions on your own; the problem is just that OSTEP expects you to have already taken a systems course like CS:APP that would have taught you that. I really wish I'd found CS:APP earlier; that would have saved me so much time. In retrospect, taking OSTEP right after Nand2Tetris without CS:APP in between them feels kind of like if someone tried to take Algorithms right after Py4E; yeah, you can probably figure it out, but it's gonna be a struggle. But once I found the right resources to learn the prereqs, the rest of OSTEP didn't really feel any harder than, say, Programming Languages, Nand2Tetris Part 2, or the Algorithms courses.
There is a caveat: the poorly-documented and unmaintained projects did cause some additional frustration when I couldn't figure out how to run the tests, or when the tests were buggy. But I think @spamegg1 and I have more or less ironed out most of the big issues there, at least for Linux systems. We could document that in a course context page, but we will have to figure out how to run them on Windows and macOS as other students take the course. Still, while it is annoying, I don't think it's too bad -- after all, the Programming Languages courses have similar issues with SML/Emacs in PL A and Ruby versions in PL C, and I definitely had my fair share of problems running the Nand2Tetris tests on Linux. So I think we can handle that either in the course context page or as problems arise,
Second, I disagree about skipping the projects. The course uses the projects as its primary assignments for a reason: the homework questions are just short "reading comprehension"-type questions, similar to the questions that pop up in the middle of videos on Coursera or edX. Many of them are simple demos for you to just watch. I'm a big fan of learning by doing, so I think it's important for OSSU courses to include programming exercises. I think doing OSTEP without projects is comparable to doing the multiple-choice questions in Algorithms without the programming exercises, or doing the in-video questions in How to Code or Programming Languages without any of the problem bank questions or homeworks. Plus, the ability to see the actual implementation of a simple Unix-like OS in xv6 is, for me, a big attraction of the course.
In addition, although I do agree that skipping the projects would shorten the time required, I don't think it's that big of a difference. It would remove some of the prerequisites like Makefiles and some of the x86-specific details (at the expense of losing the opportunity to understand how paging, context switches, interrupts, locks, etc. are implemented). But I think the biggest time sink by far is getting the required C knowledge, and that's actually just as important for the course as it is for the projects: without knowing C well, the vast majority of the material would be inaccessible. So I don't think removing the projects cuts down on the prereqs by much; if students have indeed learned enough C to understand the code examples in the lectures, then it wouldn't cut down on the time by much more than the normal amount of time it takes to do any assignment.
Completing the prereqs will take significant time, mostly spent learning C. Since this is the only course in the curriculum that requires C (although Computer Graphics requires C++), I think we can definitely expect that students in a time crunch (or students who aren't particularly interested in systems development) might decide not to do the projects, or might even skip OSTEP altogether, and I agree -- there's no shame in that.
The difference in my mind is that by affirmatively recommending the projects, the official OSSU curriculum will still meet the CS 2013 guidelines, especially for the Core-Tier2 hours, which I don't believe would be met with the homeworks alone. Then students can make their own decision about whether to stick with the official curriculum to meet the CS 2013 guidelines, or to cut out some parts of it.

Alright, I think those are good points.
I've probably built up the difficulty too much in my head, and the course should be easier with our contributions and your roadmap through the projects. That is true.
I still think the book and homework alone cover the curriculum requirements, but I might have to do a deeper look into it. If the projects are doable and not too time consuming, there is no need to fight over this point.
Taking your disagreements as valid, could you make an accompanying pull request @palladian1 ? If you put fixes #926 in the title, Github will automatically pick it up and link it to this issue. It can give a better idea to other commenters. No rush, take your time.

@palladian1 will be offline for a few days, but worked very quickly and very hard to provide me with an early draft of the context page. I think it looks great. Here it is for other commenters to see:

Context page early draft (click to expand)

Operating Systems: Three Easy Pieces
First, we should be frank: it's really hard to find a good self-contained online course on operating systems. OSTEP is the best course we've found so far, but it does have some issues.
This is the first course in the OSSU curriculum for which you'll need to learn some prerequisites on your own before starting it, in addition to the courses that come before it in the curriculum. You might also run into some issues running the scripts for homework demos and for testing your solutions to the projects (although we hope we've solved most of those by now).
What this means for you is that if you're under a significant time crunch, or you're just not all that interested in systems programming and OS development, there's no shame in skipping this course and coming back to it later. You could also do only a part of the course (e.g. you might choose to skip the homework and/or projects).
That said, if you're able to commit the time required for the prerequisites, we believe the reward is well worth the effort: this course is exciting, interesting, and quite useful for other fields of computer science and programming. One big
attraction of this course is the opportunity to see a simplified but fully-functional Unix-like operating system in action and understand the concepts and design decisions that went into it as well as the low-level implementation details.
In order to satisfy OSSU's curricular guidelines, you should either watch all the lecture videos or read chapters 1 through 47 in the textbook (don't worry, the chapters are usually just a few pages long) as well as finish the projects listed below. We also strongly encourage you to do the homework exercises as they're assigned on the course website or in the book chapters; think of these like the "check-your-understanding" questions that pop up in the middle of lecture videos on sites like Coursera or edX.
Prerequisites
This class requires a lot of experience programming in C. You should finish one of the C books listed in the resources below before starting this course; if you try to learn C at the same time as the course material, you're likely to feel overwhelmed. If you haven't used C before, you should expect to spend a lot of time on this; it's hard to predict how long it might take for each person, but a rough estimate might be 8-10 hours per week for 3-5 weeks. You can always learn C alongside another OSSU course or even redo the exercises for other courses in C to gain practice with it.
You should also finish both parts of Nand2Tetris before starting this course. OSTEP focuses on the real-world x86 and x86_64 architectures, so you'll have to fill in some gaps in order to translate the concepts you learned in Nand2Tetris to a new architecture. You can do that with the x86 resources below, but note that they all assume you know C, so learn that first. This should take around 6-8 hours in total.
Course Links

Course website
Book
Lecture videos
Homework
Homework repo
Projects
xv6

Roadmap
This course was originally taught as CS 537 at the University of Wisconsin by the author of the OSTEP textbook, so the projects are assigned in the course according to the best times to give UWisconsin students access to on-campus resources like recitation sections and office hours. That means they don't match up perfectly with the material being covered at that time in the lectures or textbook chapters. We recommend doing the course in the following order instead.

Read chapters 1 and 2 of the OSTEP textbook or watch the first half (the introduction) of lecture 1.
Do the initial-utilities project; it's intended as a litmus test for you to make sure you're comfortable enough with C before taking this class. You can watch discussion 1 for help. If it takes you more than 2 hours to write the code (not counting the discussion time and any time spent debugging), you should consider spending more time learning C before moving on in the course. (If you want more practice, you can do initial-reverse too, but it's not required.)
Watch lectures 1 through 5 or read chapters 3 through 24 of the OSTEP textbook. We recommend doing the homework assignments as they come up in the course calendar or book chapters.
Watch discussion 3 or reread chapter 5, then do the processes-shell project.
Read the annotated guide to xv6 linked in the resources section below, starting from the beginning and stopping after the System Calls: Processes section.
Watch discussion 2, then do the initial-xv6 project.
Watch discussion 5, then do the scheduling-xv6-lottery project.
Watch discussion 7, then do the vm-xv6-intro project.
Watch lectures 6 through 9 (and optionally, the review lecture) or read chapters 25 through 34; again, you're encouraged to do the homework.
Watch discussion 10, then do the concurency-xv6-threads project.
Watch discussions 11 and 12, then do the concurrency-mapreduce project.
Watch lectures through 14 (and optionally, the second review lecture) or read chapters 35 through 47; remember to do the homework along with the lectures or chapters.
Do the filesystems-checker project.

Running the Projects
This course was originally taught as CS 537 at the University of Wisconsin by the author of the OSTEP textbook, which means that the homework and projects were written with those students as a target audience and designed to be run on UWisconsin lab computers with specific software versions pre-installed for students. We hope this section fixes that so you can run them on other computers, but we haven't tested this on every computer, so if you run into other issues, let us know on the Discord channel and we'll try to help out.
In order to run the homework and projects on Linux or macOS, you'll need to have all of the following programs installed:

gcc
gas
ld
gdb
make
objcopy
objdump
dd
python
perl
gawk
expect
git

You will also need to install qemu, but we recommend using the patched version provided by the xv6 authors; see this link for details.
On macOS, you'll need to install a cross-compiler gcc suite capable of producing x86 ELF binaries; see the link above for details as well.
On Windows, you can use a Linux virtual machine for the homework and projects. Some of these packages are not yet supported on Apple M1 computers, and virtual machine software has not yet been ported to the new processor architecture; some students have used a VPS to do the homework and projects instead.
Next, clone the ostep-homework and ostep-projects repositories:
git clone https://github.com/remzi-arpacidusseau/ostep-homework/
git clone https://github.com/remzi-arpacidduseau/ostep-projects/
cd ostep-projects

You'll have to clone the xv6-public repository into the directory for each xv6-related OSTEP project. You could use the same copy for all the projects, but we recommend using separate copies to avoid previous projects causing bugs for later ones. Run the following commands in each of the initial-xv6, scheduling-xv6-lottery, vm-xv6-intro, concurrency-xv6-threads, and filesystems-checker directories.
mkdir src
git clone https://github.com/mit-pdos/xv6-public src

Resources
C
Please don't try to learn C from sites like GeeksforGeeks, TutorialsPoint, or Hackr.io (we're not even gonna link to them here). Those are great resources for other languages, but C has way too many pitfalls, and C tutorials online are often filled with dangerous errors and bad coding practices. We looked at many C resources for the recommendations below and unfortunately found many bad or unsafe ones; we'll only include the best ones here, so look no further!
We recommend learning C by working through (the entirety of) Jens Gustedt's Modern C, which is freely available online. This book is relatively short and will bring you up to speed on the C language itself as well as modern coding practices for it. Make sure to do all the exercises in the footnotes!
While the book above is our default recommendation, we also recommend K.N. King's C Programming: A Modern Approach as a second, more beginner-friendly option. It has some disadvantages: it's much longer (almost
850 pages), it's not available for free (and copies can be hard to find), and it's not quite as recent as Modern C (but still relevant nonetheless). That said, it has more exercises if you want extra practice, and the Q&A sections at the end of each chapter are filled with pearls of C wisdom and answers to C FAQs. It also covers almost the entirety of the C language and standard library, so it doubles as a reference book.
CS 50 doesn't quite cover enough C for OSTEP, but if you've already taken CS 50,
you can supplement it with the books above.
Additional (optional) resources include:

CS 50 Manual Pages: a great reference for looking up C library functions; most functions include both the usual manual as well as a beginner-friendly "less comfortable" option (just note that the "less comfortable" version uses string as an alias for char *.)
comp.lang.c FAQs: answers to all of your questions about C minutiae.
cdecl: a tool to translate C gibberish into English.
C track on exercism.io: additional practice exercises.
Secure Coding Practices in C and C++: if you want to understand why other C resources are so unsafe.
The C Programming Language: the original book on C by its creators. Too outdated for OSTEP, but a good read if you manage to find a copy.

x86 Architecture and Assembly Language
Nand2Tetris has already introduced most of the concepts you'll need to understand systems and computer architectures, so now you just need to port that knowledge to the real-world (32-bit) x86 architecture.
The easiest way to do that is by watching a subset of the lectures from the Computer Systems: A Programmer's Perspective course (or reading the matching chapters in the textbook of the same name). The lectures you'll need are:

Machine-Level Programming I: Basics
Machine-Level Programming II: Control
Machine-Level Programming III: Procedures
Machine-Level Programming IV: Data
Machine-Level Programming V: Advanced Topics
Linking

Additional (optional) resources include:

CPU Registers x86: good for looking up specific registers.
PC Assembly Language: a short book on x86 assembly.
GCC Inline Assembly HOWTO: a guide to writing assembly code inside a C program.
Intel 80386 Programmer's Reference Manual: the official (and huge) resourcefrom Intel.

xv6
You don't need to read anything about xv6 until after you start OSTEP; in fact, we recommend holding off on the xv6-related projects until you've finished the entire section on virtualization. After that, you'll need a guide to walk you through the source code.
The xv6 authors provide a book that you can read alongside the source code. There's also a handy line-numbered PDF version of the
code with an index to see exactly where each function or constant gets used.
However, that book glosses over a lot of the details in the code that you might find challenging, including the advanced C features used, the x86 architecture- specific instructions, and the concurrency aspects (if you haven't finished that section of OSTEP before starting the xv6 projects). To solve this problem, we provide an annotated guide to xv6 that goes over the entire xv6 code and analyzes it line-by-line with explanations of the C features, hardware specs, and x86 conventions used. That means it's longer than the official xv6 book, so you don't have to read all of it (and you can probably skip the optional sections unless you care about device drivers), but you can use it as a reference if you're scratching your head about some part of the code.
Miscellaneous
You'll need a general sense of how Makefiles work in order to use the Makefile for xv6. This tutorial covers much more than you need; just read the "Getting Started" and "Targets" sections and come back to the rest later if you need to look something up (but you shouldn't have to).
Additional (optional) resources include:

GCC Command Options: a guide to command-line flags for the GNU C compiler gcc.
Linker Scripts: a guide to writing scripts for the GNU linker ld.
OSDev Wiki: a great resource for all kinds of OS concepts and implementation details.
Linux Kernel Development: if you want to apply your xv6 knowledge toward contributing to the Linux kernel, this is a great read after OSTEP.

This looks like a well reasoned deep dive that should assist students in being successful in the course. I like the idea of having this as a linked page in the repo, which gives future students the ability to make pull requests as needed.
A breadcrumb for other readers of this RFC: the CS:APP course that palladian1 refers to as very helpful above is the same as the Computer Systems: A Programmer's Perspective course/textbook in the context draft.

The context draft is great!
Suggestion regarding the “Running the projects” section. Right now, the draft provides some guidance for running projects on a Mac or PC, with a mention that some students use VMs. Have you considered primarily recommending a cloud VM (such as GCP Compute Engine or AWS EC2)? Along with the recommendation, a setup script could be provided to configure and install necessary dependencies.
The benefit: students will start with similar environments. This mimics the original college course where students were provided with preconfigured VMs.  I assume this eliminates issues and questions related to unique setups.
The 2 downsides: cost (although It should be less than $10 a month); those unfamiliar with cloud computing concepts may have difficulties (although some simple guides could help).

For C: The instructor's website lists this book for learning C.

@riceeatingmachine It's included in the draft under Resources/C/Additional(optional) resources. @palladian1 and I discussed it for a while, and we anticipated a lot of people mentioning K&R like you just did :) K&R is highly revered for obvious historical reasons (some people get upset if it's not the default recommendation) but it's old and outdated, not free and it can be hard to find a copy. We noticed there are too many options, and the "best resource" debate can go on forever, so we decided to reduce the options to two: one great free resource, and one arguably best non-free resource. (This idea is similar to how the curriculum had "Learn You a Haskell For a Great Good!" and "Haskell Programming from First Principles" back in the day.)

Srivastava's C In Depth (Amazon, Goodreads) has great reviews too and costs 1/20th as much as KN King.

I had an idea. There are 3 courses in Advanced Systems:

Digital circuits
Computer Architecture
Computer Organization

Digital circus covers:
   How to efficiently and reliably encode information using bits     The basics of digital signaling, combinational logic, CMOS technologies     The principles of sequential logic and finite state machines     Performance measures and design tradeoffs
Computer Architecture covers:
   Instruction Set Architectures: datapaths and FSMs, programmable datapaths, the von Neumann model, storage, ALU instructions, constant operands, memory access, branches, jumps.       Assembly Language: from assembly language to binary, symbols and labels, instruction macros.     Models of Computation: computability, universality, uncomputable functions.     Compilers: interpretation vs. compilation, compiling expressions, compiling statements, compiler frontend, optimization and code generation.     Procedures and Stacks: procedural abstraction, activation records and stacks, stack frame organization, compiling a procedure, stack detective.     Building the Beta: circuit building blocks, ALU instructions, load and store, jumps and branches, exceptions.     The Memory Hierarchy: memory technologies, hierarchical memory systems, the locality principle and caching, direct-mapped caches, block size, cache conflicts, associative caches, write strategies.     Labs: simple assembly programming, Quicksort procedure, designing the 32-bit Beta processor.
Computer Organization covers:
     Pipelined Beta: pipelined execution of instructions, data and control hazards, resolving hazards using bypassing, stalling and speculation.
    Virtual Memory: extending the memory hierarchy, paging using hierarchical page maps and look-aside buffers, contexts and context switching, integrating virtual memories with caches.
    Operating Systems: processes, interrupts, time sharing, supervisor calls.
    Devices and Interrupts: device handlers asynchronous I/O, stalling supervisor calls, scheduling, interrupt latencies, weak and strong priority systems.
    Processes, Synchronization and Deadlock: inter-process communication, bounded buffer problem, semaphores for precedence and mutual exclusion, semaphore implementation, dealing with deadlock.
    Interconnect: the truth about wires, point-to-point vs. shared interconnect, communication topologies.
    Parallel Processing: instruction-, data- and thread-level parallelism, Amdahl’s Law, cache coherency.
    Labs: optimizing your Beta design for size and speed, emulating instructions, extending a simple time-sharing operating system.

This stuff is covered by a book called Computer Organization and Design (much of) which I read last year. We could replace these courses with that book (I haven't read CS:APP but I think it would overlap as well).
We can replace these courses by either of these books and make that a prerequisite for OSTEP.

If we add a C book to the curriculum, it can be listed as a pre-requisite to the Compiler's course, which mentions:

An optional course project is to write a complete compiler for COOL, the Classroom Object Oriented Language. COOL has the essential features of a realistic programming language, but is small and simple enough that it can be implemented in a few thousand lines of code. Students who choose to do the project can implement it in either C++ or Java.

Since it as an advance and elective course, I presume people taking it will want to the final project. If you know C then using C++ should not be so hard (I presume).

There are 3 courses in Advanced Systems... We could replace these courses with that book... and make that a prerequisite for OSTEP

This seems like a bigger discussion (replacing multiple courses with a textbook). Great contribution to point out another book that may suit as prerequisite preparation for OSTEP. I'd suggest keeping that separate from replacing other courses in the curriculum (a topic that could become its own RFC).

If we add a C book to the curriculum, it can be listed as a pre-requisite to the Compilers course, which mentions: An optional course project... implement it in either C++ or Java.

I'm wary of listing a C textbook as prerequisite because there is a project that students can do in a related language.

@palladian1
Lots of great comments on this RFC. Can you open a pull request with the changes you've envisioned, incorporating any changes you feel are right based on the feedback above?
My hypothesis is that it will be more maintainable to have a single context page, that is meant to provide context for any course that needs it, with only the single entry for OSTEP in it. When later contributors wish to add context for another class, they can add an entry in that one file. (An alternate approach would be a folder for context files, and each course gets its own context file). Either way, I recommend against creating empty entries/files for the other courses in the curriculum (which would be a maintenance headache when a course in the curriculum changed).

I'd suggest keeping that separate from replacing other courses in the curriculum (a topic that could become its own RFC).

I don't mind making the RFC but I'm haven't taken the 3 advanced courses yet to do a full comparison.

It's been many months since a PR based on the discussions here was invited. And there is now another RFC around the idea of adding context to courses (including OSTEP). https://github.com/ossu/computer-science/issues/976
In light of those facts, I'm closing this issue.


Image search feature is not available in mobile view default theme

Bug report
Title
Image search feature is not available in mobile view default theme
Issue Description
Image search feature is not available in mobile view default theme
Preconditions
1. framework Version- master

Steps to reproduce
1. step1- mobile view, check the search bar image icon

Actual result

fixed


400 error on making transactions

Currently attempting to make offchain transactions results in a 400 error with the message [{"message":"","code":"EON_NUMBER_OUT_OF_SYNC"}]

fixed in 292adca7e5122933eaf818ca99ffc0ae918e6211


Encodable not implemented for [T; 64] or ()

What would you want () for?

Sometimes it's useful to say "don't serialize anything" in generic code.

I really don't think we should be moving towards Encodable being a public trait to be implemented for random things, its consensus::encode, not Writable. If a client wants to encode something, they can Write it. As it is the generic Encodable implementations make introducing bugs much too easy.

Closing because after discussion in #264 I think this is the wrong direction to take these traits.


No need to wait after Wire.requestFrom()

When the Wire.requestFrom() returns, the I2C transaction has completely finished and the received data is waiting in a buffer in the Wire library.
There is no need to wait for something after a call to Wire.requestFrom().
The function wait() in the file "arduino-px4flow-i2c/PX4Flow/PX4Flow.cpp" is not needed.
You can write your code like this:
  // request 22 bytes from the module
  Wire.requestFrom(PX4FLOW_ADDRESS, 22);

  // read the data
  frame.frame_count = read16();
  ...

or something like this:
  // request 22 bytes from the module
  Wire.requestFrom(PX4FLOW_ADDRESS, 22);

  if (wire.available() != 22) {
      return false;
  }

  // read the data
  frame.frame_count = read16();
  ...

Also draining the buffer (removing any remaining data) is not needed. The Wire library uses packets of data and starts with a cleared buffer before doing a I2C transaction.
There was a bug in the library for the SAMD processors that a buffer was not cleared, but that bug has been solved a year and a half ago.

Thanks for your message. However I don't have access to a PX4Flow anymore and don't really maintain this project. If you have time to prepare a pull request with the changes, I'd be happy to merge it.


Relationships Page

Get this page working. Accessed in the notebook from the More menu. There is already a placeholder page. See Strabo Spot 1 for functionality. No forms assets used for this page.

@nicolasmroberts Need a mockup or do we just want it like SS1?


Making chatbox messages more readable (UI - enhancement)

Is your feature request related to a problem? Please describe.
Problem: In the chatbox, it's challenging sometimes to differentiate between my message and the other person's message as both have the same message box color - rgb(0, 180, 216). (cyan-blue kinda color)
We see most of the chat applications having a contrast of message box color so that it is easier to differentiate between my message and other participant's message.
Describe the solution you'd like
Solution: Let's have a different color of message box of my message in the chat section, so that it get's easier for the user to differentiate between my messages and other participant's messages.
Motivation
Many chat applications like Whatsapp, telegram, messenger, etc. follow this UX principle.
Are you willing to contribute to this issue? [Yes/No]
Yes, I am willing to contribute to this issue.
Describe alternatives you've considered
Open to suggestions ✌
Additional context
See this screenshot:
Better readability:

I'am gssoc participant
I would like to work on this issue. I will submit before due date with fantastic work.

Hi @amaan-ahmad, Thank you so much for taking out time to create this issue 🚀
Yes, Please go forward to work on this issue, I am assigning this issue to you 🔥.
(Might be a little challenging) Only for the user who is sending the message, we want to interchange the positions of Avatar and the message box when he will post his message.
eg: 👇

Keep Contributing 🙌

Hey, @lakshita15  thank you for showing interest 🚀
We appreciate🙏 your dedication and efforts towards our project, but according to our contributing guidelines, Issues are assigned on the First Come First Serve basis.
Thank you😊, and Sorry for the inconvenience caused 🙌

@lakshita15  before you get into the code part please share Figma/XD design like what exactly you are going to plan.

Hey @Nishant127 , I'll try this one changing the position. Hopefully will succeed in this✌
Kindly assign this issue to me.
Thanks.

@Nishant127
Have a look, I did it!
Actually, I stored the name of user in local storage whenever they create/join the room.
and then compare it with data.name in ChatMessage.js as needed to do CSS-in-JS styling.
Pretty easy. ✌

@Nishant127
As discussed, I have created PR #82 for this issue.
Kindly add the GSSOC21 label to this issue and assign it to me.
Thanks 😊

@amaan-ahmad Well done bro 🚀🔥.
I have assigned you the issue. You can go ahead now.

Great Work 🚀

Thank you for Contributing 🙌
Thanks 🔥


Empty state cart

PR Description 📜
@trishanu-init
[BUG]: update empty state of cart #65

Fixes #65 <your_issue_number>

Type of Change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update

How Has This Been Tested?

go to /cart route

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have added README.md in my folder

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

@trishanu-init
please check this and merge it


Cannot change share preferences

I chose to share a file, chose the copy to clipboard method, tried to paste it and ask that was copied was the file path. I went back to select a different share method to get the actual file. I could no longer choose a method. If I clicked share it would immediately copy to clipboard. I don't see app preferences or anything to change this.

If you want this to be fixed, you should report it to the original app https://github.com/jonan/ForkHub. This app is just a copy.


🐛 BUG: [D1] No option to delete/update row if there's no primary key column in a table (Cloudflare Dashboard)

Which Cloudflare product(s) does this pertain to?
D1
What version of Wrangler are you using?
-
What operating system are you using?
Web Browser (Cloudflare Dashboard)
Describe the Bug
There's no option for delete/update row (the triple dot) if there's no primary key column in a table.

I don't know if it's intentional/limitation since there's no primary key, so the dashboard doesn't know which row to delete/update.
And honestly, I don't think this is the right place to report it, since (maybe) it has nothing to do with Wrangler CLI. But hopefully it can be seen by the D1 team or moved to the correct place 😊.

Hey @DevinWinata - thanks for reporting this.
It's intentional (for now, anyway), if there's no primary key we can still delete using ROW ID, but I haven't implemented that yet.


How to deploy Next.js with Express and external Babel?

It is my first application with Next.js and I am facing problems to deploy the project to Heroku.
I am using Express server and a external .babelrc file.

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior
No errors building/running project in Heroku.
Current Behavior
I am running yarn build and then git init / add / commit / push in .next/dist folder and copying package.json into it too.
Context
This is my scripts from package.json:
"scripts": {
    "start": "NODE_ENV=production node server/server.js",
    "dev": "nodemon -w server server/server.js --exec babel-node",
    "build": "next build && babel server -d .next/dist/server",
    "lint": "eslint --fix components lib pages server **/*.js",
    "snyk": "snyk test",
    "heroku-postbuild": "next build && babel server -d .next/dist/server"
  }

next.config.js:
module.exports = {
  webpack: (config, { dev }) => {
    // For the development version, we'll use React.
    // Because, it support react hot loading and so on.
    if (dev) {
      return config;
    }

    config.resolve.alias = {
      react: 'inferno-compat',
      'react-dom': 'inferno-compat'
    };
    return config;
  }
};

And the .babelrc:
{
  "presets": [
    [
      "next/babel",
      {
        "preset-env": {
          "modules": "commonjs"
        }
      }
    ]
  ],
  "env": {
    "development": {
      "plugins": ["inline-dotenv"]
    },
    "production": {
      "plugins": ["transform-inline-environment-variables"]
    }
  }
}

Your Environment

Tech
Version

next
6.0.1

node
9.5.0

@babe/*
^7

Please, I need some help...

I'm not sure what the issue is here.

I am running yarn build and then git init / add / commit / push in .next/dist folder and copying package.json into it too.

This sounds like a weird thing to do.
Also you're building your custom server to .next/dist and then starting it from server/server.js.

I have changed the start script to point to .next/dist .. Heroku is getting 'request timeout'..

@timneutkens So how can we write custom server, that uses bundled version of next. Or do you expect us to put entire repository contents + node_modules (from which we need only express and next, but polluted with webpack, babel, react, etc. due to "next build") into the production servers?

@ElvenMonky read this issue: https://github.com/zeit/next.js/issues/4496


ClearPass Policy Manager

Name of the app
clearpasspolicymanager
Integration
The technology that your app integrates with.

About
The app will provide a set of actions for integrating with ClearPass Policy Manager

Repo created at: https://github.com/splunk-soar-connectors/clearpasspolicymanager


Demux Service on the Backend

I think https://github.com/EOSIO/demux-js is great for listening the blockchain for rate events and store them on the MongoDB

Closing in favor of https://github.com/eoscostarica/eosrate/issues/59


README.md link typo fixed

Fixed the markdown typo of the HabHub Tracker link in the README.md file

Habhub has been shutdown so the readme should probably be edited more.

Yeah... this needs to be updated now habhub has gone...
tracker.habhub.org just redirects to sondehub!


some apps closed after systemctl suspend

Hyprland Version
0.29.1
Bug or Regression?
Bug
Description
Hello,
after a systemctl suspend some apps are closed and some things don't work properly anymore: I can't open the foot terminal via keyboard shortcut anymore.
Can see the behavior on both my computers. Both with openSUSE Tumbleweed.
Closed programs include: telegram-desktop, dolphin, teamviewer and openSCAD.
Übrigens habe ich den PC am 19.September um ca. 16:00 Uhr schlafen gelegt und am 20.September ca. 6:00 Uhr aufgeweckt. Es sind aber auch Einträge um 20:56 Uhr in dmesg. Is that normal?
dmesg.txt
BR,
Michael
How to reproduce
Lock pc via systemctl suspend and wake it up.
Crash reports, logs, images, videos
No response

das wurde in der -git version behoben


Bug: TransactionRequest QR unreadble issue.

TransactionRequest QR code seems to be unreadable. Currently, TransactionRequest QR renders with Version 40.

@evias Please note it.

sorry, this is fixed in 0.5.0 :+1:


Version 1.2

Here I made a part of the method run, when the client connects a welcome message will be shown

i will continue with the other part of the method run


fix: Add BackendLBPolicy to experimental kustomization

Kustomization does not install this new CRD because it is not on the list of resources.

What type of PR is this?

/kind bug
What this PR does / why we need it:
Fixes installation of experimental CRDs using kustomization.
Which issue(s) this PR fixes:

Does this PR introduce a user-facing change?:

NONE

/lgtm


VDD is detected under device manager but not under display settings.

same problem

u install win 10 drivers?

no, I have Windows 11 Version 22H2

Weird but when I install the non-HDR version, both show up but HDR option is not available.

Iv got this issue as well.

I encountered the same issue, the reason is that I am using Windows 10 but installed the latest version 23.12.2. Installing version <IP_ADDRESS> works fine.
By the way, like @seabird12345 mentioned, after installing the correct version, version 23.12.2 devices can be used normally. Maybe the latest version just lacks an activation step for the devices???

I am having the same issue on Win10. I installed beta 24.8.6 as it looked like a unified win10/11 hdr/nonhdr driver. I get a device is not working properly, Code 31, and the driver in Device Manager says "Virtual Display with HDR Properties".
I tried to install <IP_ADDRESS>, and the driver name does not include HDR, and the adapter in Device Manager looks okay, but there is nothing new showing in the Windows Display settings. Restarted computer, restarted device, nothing.

If people can try with the latest beta and provide logs where possible, this would help us diagnose the issue, most likely an issue with windows itself. But without direct access to logs its hard to diagnose
You can enable logging by toggling logging in vdd_settings.xml. Please do this before installing the driver to prevent needing to restart the device or driver

same issue with Win11

same issue with Win11, although i'm now receiving the below error

Did you try the beta

yep & its now working. Thanks !


Mention env vars in the provider config docs

Signing a CLA requires tedious sign-off from our legal team that I've not got time to bother with, so I guess this won't be merged.

Resolved by #29.


Get current version from package.json

Currently, we manually update the version string in the cli when I remember https://github.com/doug-wade/tybalt/pull/296/files#diff-fde3c020439d16b612facc24e7dc713eb3db8482b286e2cc787a5cae8fdc5367R10
This makes the version string less effective for users, since it may be out-of-date. Instead, let's parse package.json and get the version field.

@doug-wade could you assign this to @givtaj ? It makes searching for unassigned issues a lot easier :smile_cat: .

@Ashvith10 I don't think so -- I think they would have to participate in the issue for me to be able to assign them. I'm not 💯 about that, it's just they don't appear in the combo box.
Also, they haven't responded to the pr feedback yet, so if you have a changeset where the tests pass, I'd certainly take it.


kra pod edit should render compose and then use the launch api

kra pod edit uses a json object that is only available in this api.
while its a good format in isolation, its just weird in context of having originally used compose or run to launch a pod and then edit it in a totally different format.
ideally we want a way to render a namespace or pod as canonical compose.
i.e do not just store the compose file, since we also support run and technically still k8s.
also we might change the syntax slightly over time, and the original compose wouldnt even work anymore.
editing a namespace this way will always be non ideal because a later kra up from local compose file will just undo it,
so i suggest adding a taint to a namespace. that is the user gets a warning before applying. (see also #18)
in an ideal future, we keep all diffs as log, so we can even show the diff, but probably not yet.

if i can make a wish, i'd like it to work this way:
kra edit <tab>
shows namespaces and then pods below that
kra edit myapp
renders the compose for the entire namespace
kra edit myapp/nginx
only one pod


Added code for creating '_clean' version of preprocessed data

As the title suggests, this PR aims to "complete" the preprocessing script by creating a _clean version of the preprocessed data by copying only the final cropped/registered files (and the intermediate ones generated during preprocessing), something that has been done in the preprocessing scripts for mp2rage and model_seg_sci projects.
Most of the added code has been modified from scripts in those repositories, see for e.g. model_seg_sci project's preprocessing.
The updated code should output a data_preprocessed_clean folder which has the following structure:

 Output folder structure

With this the preprocessing pipeline can be run again, and the data_processed_clean folder could be used as it is for training.

out of curiosity, what is the difference between:
│   │       │   │       ├── sub-001_ses-02_FLAIR_seg-lesion.json
│   │       │   │       └── sub-001_ses-02_FLAIR_seg-lesion.nii.gz

and
│   │       │   │       ├── sub-001_ses-02_FLAIR_lesion-manual-rater*.json
│   │       │   │       ├── sub-001_ses-02_FLAIR_lesion-manual-rater*.nii.gz

That's the consensus GT (ie the GT from the senior expert) that the challenge data already had. They initially named it just as "ground truth" as seen here, and we also stuck with it while BIDSifying the data.


508 full compliance

Follows on #152 - we need full compliance for the official vizzy release.

No more errors 👍


Add context menu for the show list

Add a context menu for the show list.
Some options might be open, remove, update

Added remove selected and update.  Adding open didn't seem like much of a shortcut if you can just double click.


use one portManager for all agents

@irisdingbj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
eb8e691d5e2ce50d1b3c86aaa793e6a52a0f8e6e
link
/test istio-integ-local-tests

prow/istio-unit-tests.sh
eb8e691d5e2ce50d1b3c86aaa793e6a52a0f8e6e
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@irisdingbj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
eb8e691d5e2ce50d1b3c86aaa793e6a52a0f8e6e
link
/test istio-unit-tests

prow/istio-integ-local-tests.sh
f675b3abb46072513784d2fce7cf912aae77f761
link
/test istio-integ-local-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@irisdingbj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
f675b3abb46072513784d2fce7cf912aae77f761
link
/test istio-integ-local-tests

prow/istio-unit-tests.sh
f675b3abb46072513784d2fce7cf912aae77f761
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

https://github.com/istio/istio/issues/10023

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: irisdingbj, nmittler
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pkg/OWNERS [nmittler]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


search(:node) does not contain the ipaddress

Here are two scripts.
One creates a machine:
require 'chef/provisioning/docker_driver'
machine "dummy" do
    tag "dummy"
    converge true
    machine_options({ docker_options: {
        base_image: { name: 'baseimage', repository: 'phusion/baseimage', tag: '0.9.17' },
        command: '/sbin/my_init'} })
end

The other searches for it:
require 'chef/provisioning/docker_driver'
search(:node, "tags:*dummy*").map do |node|
    p node.ipaddress
end

When I run these scripts with bundle and this Gemfile:
gem 'chef-provisioning-docker'

The second script works fine.
When I try and run against the master git HEAD version :
gem 'chef-provisioning-docker', :path => '../chef-provisioning-docker'

I get the following error:
ERROR: Undefined method or attribute `ipaddress' on `node'

Here is a bypass which uses docker inspect to get the ipaddress if it is not set:
class Chef::Resource::Machine
    def running_on? kind
        kind == ENV['CHEF_DRIVER'].sub(/::.*$/, "").to_sym
    end
    def get_docker_ip_address name
        JSON.parse(`docker inspect #{name}`).first["NetworkSettings"]["IPAddress"]
    end
    alias :old_search :search
    def search what, query
        result = old_search what, query
        if what == :node and running_on? :docker
            result.map! do |node|
                node.default["ipaddress"] = get_docker_ip_address(node.name) if node["ipaddress"] == nil
                node
            end
        end
        return result
    end
end

Hm, there are no much changes between 0.7 and master.
I personally have ipaddress among node attributes when running CPD. Though, I use forked version of my own without changes introduced by 07753c4520d3364124dbdca434cd102e471b8bb4 .


Version 0.1 - unminified code still available?

At https://gist.github.com/adkatrit/9337610 , one can get a sigma.min.js, which claims to be Version: 0.1.
Is the unminified version 0.1 still available somehwere?

 Why do you need it exactly?

My job involves reviewing requests to use and distribute open source software in our company's products. I have a request from one of our development teams for using https://gist.github.com/adkatrit/9337610 , so I am trying to find the repository and original version of this code, and not just a gist

@sgustafsson I think you find it on the deprecated-v0.1 branch here. This is really outdated code however, but I guess this is none of my business :).


Deprecate resolving configuration without attributes

Fixes https://github.com/gradle/gradle/issues/13736

Here's a sample in the documentation that suggests creating configuration without attributes: https://docs.gradle.org/current/userguide/implementing_gradle_plugins.html#providing_default_dependencies_for_plugins


Add zfp as a supported CompressedImage format

Public-Facing Changes

zfp is documented as a valid format for CompressedImage messages. The schema docs describe the constraints (header required, data must be 2D)

Closing this. Not currently planning to add zfp as a compressed image format sibling to png and jpeg. We might re-visit this in the future as a new field for generic compression of the image data or additional parts of a string on top of the format field that is meant to have well-known compressed image formats.


Level 9+ subcategories scope and management

As discussed, I think that maintenance (GitHub), publication (WMO Codes Registry) and validation (Broker) of the subcategories shall apply to core data only. Subcategories associated with recommended data are not in scope.
If we are in agreement, then we should clearly document this.
However, there are use cases where a particular domain might want to define subcategories for certain types of recommended data, e.g. NWP highly-recommended,  and we should consider options for supporting the normalization of these codes in a feasible manner.

We should also reconsider this statement in the Readme: "
9 | earth-system-discipline-subcategory | As proposed by domain experts and further approved by INFCOM"

TT-WISMD 2023-02-15:

what level of governance/approval recommended need?  Is INFCOM approval too heavy?  Fast track?  Pull requests?
chicken/egg problem (cannot block new centre-id from being locked out of topic hierarchy)
how do we deal with lower level topic hierarchies not defined in core (beyond level 9)?  Are they discarded?

Numerous questions and clarifications on architecture of participation.
cc @efucile @golfvert

what level of governance/approval recommended need?  Is INFCOM approval too heavy?  Fast track?  Pull requests?

I'd go for "Fast track". We need some form of formal approval. So Pull requests, probably not. But not to heavy so not INFCOM.
Considering the kind of things I approved on the fast track approach, seems OK to me.

how do we deal with lower level topic hierarchies not defined in core (beyond level 9)?  Are they discarded?

At the moment, the subscription on the French GB ends with #. Typically  origin/a/wis2/swe/smhi/data/core/weather/surface-based-observations/# So, everything below will go through. If we want to keep control on the topic hierarchy (and enforce the control of topics) then, the non compliant topics should be discarded at the GB level.
If we do that, the GBs will need to "import" the topics when approved and check that. What will be the policy for enforcing the discard?
Say we have version 1.0. New version 1.1 is approved and then .2, .3,... what is the best way to allow some coexistence but not forever? Allowing 2 versions ? 3 versions ?

centre-id

I am confused with this... Is it centre or center? -id or _id? I don't recall having the final decision on that one.

TT-WISMD 2023-05-10:

recommendation data can be categorized accordingly
+1 for reuse FT workflow (May/November)


Split long line [phab:D1493]

Created by salguarnieri at 2017-04-05 15:55:52:
Line length limit is 100, split a long line.

schroederc commented inline (context lost during migration) at 2017-04-05 15:59:14:
google-java-format should have caught this.  Has it been run over the file?

salguarnieri wrote at 2017-04-05 16:03:10:

run google-java-format

salguarnieri commented inline (context lost during migration) at 2017-04-05 16:03:18:
Doubtful? I just ran it though.

schroederc accepted this revision at 2017-04-05 22:35:09

salguarnieri closed via commit 856fb193495777868f8fd39590c0902052a616d0 at 2017-04-05 22:39:12


[Leaderboard] rank and score reversion

Describe the bug
Rank and score reversion
Screenshots
12hrs ago

and now

Username: NoobJeffy
Server name (all applicable): Atlas
Logs:
I don't think it need a log, but i will provide if needed

Closed, ticket is no longer in effect.


"From existing code" creates incorrect paths

I imported existing code using the "From existing code" template, and the TypeScript projects wouldn't build.
The initial code was in "C:\temp\sample", and I created the new project at "C:\temp\FromExistingCode1". The items were still all left in the "sample" folder, and the project has a setting <ProjectHome>..\sample\</ProjectHome>, which seems to work for the Solution Explorer (as the files all resolved to the "sample" folder still. the items appear to be relative to this project home, e.g.
  <ItemGroup>
    <Content Include="package.json" />
    <Content Include="readme.md" />
    <Content Include="src\client\page.tsx" />
    <Content Include="src\client\tsconfig.json" />
etc..

However on trying to build I get the error: tsc(0,0): error TS5058: Build:The specified path does not exist: 'c:\temp\FromExistingCode1\src\client\tsconfig.json. As can be seen, its resolving the item relative to the project file, not the  setting.

I'm seeing the same thing.

I had two projects where one did this and the other did not.  The difference in the nsproj files was the additional  tags below.
true
CommonJS
true
Removing this solved my issue.
In case anyone is using 'from existing code' to debug jest.

change the environment as required


Newly generated pipeline fails with ImportError: cannot import name 'OAuth2ClientCredentials'

A freshly generated pipeline with:
dlt-init-openapi affinity --url https://raw.githubusercontent.com/planet-a-ventures/affinity-node/refs/heads/main/openapi/2024-11-18.json --global-limit 2

yields
Traceback (most recent call last):
  File "/Users/joscha/dev/dlt-test/affinity_pipeline/affinity_pipeline.py", line 3, in <module>
    from affinity import affinity_source
  File "/Users/joscha/dev/dlt-test/affinity_pipeline/affinity/__init__.py", line 5, in <module>
    from rest_api import rest_api_source
  File "/Users/joscha/dev/dlt-test/affinity_pipeline/rest_api/__init__.py", line 39, in <module>
    from .config_setup import (
  File "/Users/joscha/dev/dlt-test/affinity_pipeline/rest_api/config_setup.py", line 47, in <module>
    from dlt.sources.helpers.rest_client.auth import (
ImportError: cannot import name 'OAuth2ClientCredentials' from 'dlt.sources.helpers.rest_client.auth' (/Users/joscha/dev/dlt-test/.devenv/state/venv/lib/python3.11/site-packages/dlt/sources/helpers/rest_client/auth.py)

on running the pipeline. Possibly related to an outdated dlt version?

Upgrading dlt is not as straightforward as hoped: https://github.com/dlt-hub/dlt-init-openapi/issues/127#issuecomment-2488306248


How to render data.

How do I render the json data.

https://github.com/codex-team/editor.js/issues/676#issuecomment-479778254


Add SequentialMessageTransformer

The new class chains together multiple MessageTransformer implementations.  This is an example of the Composite Pattern (https://en.wikipedia.org/wiki/Composite_pattern).
A class implementing the MessageTransformer interface has to define a method called transform that takes a Message as input and returns a (presumably modified) Message.  We will likely have many MessageTransformer classes, each defining some specific behavior.  For example, the JSoupCleanMessageTransformer uses JSoup to remove potentially dangerous HTML tags from a Message's text field.
This new class, SequentialMessageTransformer, makes it possible to combine multiple individual MessageTransformer implementations.  It stores a list of MessageTransformer "delegates" and when it receives a Message to transform, it passes that message through each of its stored delegates.  For example, you'll see in the testTransformTextSequenceOfThree unit test that a SequentialMessageTransformer that stores a list of three delegates will take an input Message (message0 in the code) and pass it to the first delegate, and then take the output of that, and pass it to the second, and the output of that to the third, and return the output of the third as it's final result.
The advantage of this kind of setup is that we can sort of mix-and-match message transformation behaviors, and to test them all independently.  For instance, Kingsley is going to create a transformer for replacing image URLs with HTML markup that displays the image.  So we can then use SequentialMessageTransformer to store a JSoupCleanMessageTransformer and that new one so that when a Message needs to be displayed, we can remove all of its problematic HTML tags AND turns its image URLs into images, and then display it.

Is this a PR that anyone can review or would you prefer if Adel reviewed it?

@iramsharieff06 Anyone can review :-)

I updated the description at the top of this PR with a fuller discussion of what's going on here.  Let me know if that helps.


Web - Request money details are missing if money requested in offline mode

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:
Action Performed:

go to offline
go to an chat
click on request money
enter money and request money
go to transaction thread

Expected Result:
should show request money details
Actual Result:
request money details are missing
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/de8ee21c-7ee2-466a-b73b-086cdaac65bb
https://github.com/Expensify/App/assets/93399543/44efb2f2-9a33-4107-abc3-d60153ed1083
Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1693201810929339
View all open jobs on GitHub

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

BTW @yuwenmemon this seems to be happening in dev only

@luacmartins right now it's reproducible in staging

Yeah I can see this on staging

I'm pretty sure this is coming from https://github.com/Expensify/App/pull/25429 cc @vitHoracek @rushatgabhane @grgia

Hmmm... Can't seem to figure out why 🤔

Can you check if this fixes it https://github.com/Expensify/App/pull/26118?

I should be able to look at this tomorrow morning.
cc @alitoshmatov might also be able to look

Ah yep, this will be fixed by https://github.com/Expensify/App/pull/26118

Fix has been CP'd to staging. Closing


Update CompendiumDirectory to Foundry VTT 0.7.9

Which class should be updated?
CompendiumDirectory
For which version should the class be updated?
Foundry VTT 0.7.9

Taking this.

Fixed by #298.